===== git log ====
commit 895183d5a2eceabcfdd81daff87ecab1159c32c6
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Wed Sep 16 07:15:41 2020 +0000

    doc: Added release 8.2 notes
    
    Updates: #1485
    
    Change-Id: Ia42666051df1624444ea203bf8b7c876cf78b592
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 85ff28ace3901a5a54d8de42d33ab2f9ac528ed8
Author: Srijan Sivakumar <ssivakum@redhat.com>
Date:   Tue Sep 1 12:48:48 2020 +0530

    Events: Fixing coverity issues.
    
    Fixing resource leak reported by coverity scan.
    
    CID: 1431237
    
    Change-Id: I2bed106b3dc4296c50d80542ee678d32c6928c25
    Updates: #1060
    Signed-off-by: Srijan Sivakumar <ssivakum@redhat.com>
    (cherry picked from commit ebc0253269d8a538239dd0b99d42f56ea320b0f0)

commit 93d48622d9ddb96f07a8590312c2885e11751436
Author: srijan-sivakumar <ssivakum@redhat.com>
Date:   Sat Jul 18 05:59:09 2020 +0530

    Events: Socket creation after getaddrinfo and IPv4 and IPv6 packet capture
    
    Issue: Currently, the socket creation is done
    prior to getaddrinfo function being invoked. This
    can cause mismatch in the protocol and address
    families of the created socket and the result
    of the getaddrinfo api. Also, the glustereventsd
    UDP server by default only captures IPv4 packets
    hence IPv6 packets are not even captured.
    
    Code Changes:
    1. Modified the socket creation in such a way that
    the parameters taken in are dependent upon the
    result of the getaddrinfo function.
    2. Created a subclass for adding address family
    in glustereventsd.py for both AF_INET and AF_INET6.
    3. Modified addresses in the eventsapiconf.py.in
    
    Reasoning behind the approach:
    1. If we are using getaddrinfo function then
    socket creation should happen only after we
    check if we received back valid addresses.
    Hence socket creation should come after the call
    to getaddrinfo
    2. The listening server which pushes the events
    to the webhook has to listen for both IPv4
    and IPv6 messages as we would not be sure as to
    what address family is picked in _gf_event.
    
    Fixes: #1377
    Change-Id: I568dcd1a977c8832f0fef981e1f81cac7043c760
    Signed-off-by: srijan-sivakumar <ssivakum@redhat.com>
    (cherry picked from commit 7c309928591deb8d0188793677958226ac03897a)

commit b4cc0988d5e9a5bf354dd4c2cb254ce52546facb
Author: nik-redhat <nladha@redhat.com>
Date:   Thu Sep 10 14:55:35 2020 +0530

    glusterd: readdir-ahead off by default
    
    Changing the default value of readdir-ahead to
    off, but it can be enabled/disabled later on if with
    gluster vol set <volname> performance.readdir-ahead enabel/disable
    command.
    
    Updates: #1472
    
    Change-Id: Idb3e16e8be98d7a811fc8e5d09906919ef50fbab
    Signed-off-by: nik-redhat <nladha@redhat.com>
    (cherry picked from commit 84a4cf76219b6187fc625740d1a1ebbe40e9f22c)

commit 68db6b60f621d371c4059a7ee728ebb267854708
Author: nik-redhat <nladha@redhat.com>
Date:   Wed Aug 26 15:08:56 2020 +0530

    glusterd: cksum mismatch on upgrading to latest gluster
    
    Issue:
    In gluster versions less than 7, the checksums were calculated
    whether or not the quota is enabled or not, and that cksum value
    was also getting stored in the quota.cksum file. But, from gluster
    7 version onwards cksum was calculated only if the quota is enabled.
    Due to this, the cksums in quota.cksum files differ after upgrading.
    
    Fix:
    Added a check to see if the OP_VERSION is less than 7 then, follow
    the previous method otherwise, move as per the latest changes for
    cksum calculation.
    
    This changes for the cksum calculation was done in
    this commit : https://github.com/gluster/glusterfs/commit/3b5eb592f5
    
    Updates: #1332
    
    Change-Id: I7a95e5e5f4d4be4983fb7816225bf9187856c003
    Signed-off-by: nik-redhat <nladha@redhat.com>
    (cherry picked from commit 865cca1190e233381f975ff36118f46e29477dcf)
    Signed-off-by: nik-redhat <nladha@redhat.com>

commit a5d9edce9b59ee00d2a4027fafba126e82e2fcfd
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Sep 4 14:49:50 2020 +0200

    open-behind: implement create fop
    
    Open behind didn't implement create fop. This caused that files created
    were not accounted for the number of open fd's. This could cause future
    opens to be delayed when they shouldn't.
    
    This patch implements the create fop. It also fixes a problem when
    destroying the stack: when frame->local was not NULL, STACK_DESTROY()
    tried to mem_put() it, which is not correct.
    
    Fixes: #1440
    Change-Id: Ic982bad07d4af30b915d7eb1fbcef7a847a45869
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 473453c4e2b1b6fc94edbce438dd9a3c0ea58c67
Author: Amar Tumballi <amar@kadalu.io>
Date:   Tue Aug 18 14:08:20 2020 +0530

    tests: provide an option to mark tests as 'flaky'
    
    * also add some time gap in other tests to see if we get things properly
    * create a directory 'tests/000/', which can host any tests, which are flaky.
    * move all the tests mentioned in the issue to above directory.
    * as the above dir gets tested first, all flaky tests would be reported quickly.
    * change `run-tests.sh` to continue tests even if flaky tests fail.
    
    Reference: gluster/project-infrastructure#72
    Updates: #1000
    Change-Id: Ifdafa38d083ebd80f7ae3cbbc9aa3b68b6d21d0e
    Signed-off-by: Amar Tumballi <amar@kadalu.io>
    (cherry picked from 097db13c11390174c5b9f11aa0fd87eca1735871)

commit 635dcf82505efcdeaf01c4e0450a157b533099ba
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Sep 1 11:36:42 2020 +0530

    libglusterfs: fix dict leak
    
    Problem:
    gf_rev_dns_lookup_cached() allocated struct dnscache->dict if it was null
    but the freeing was left to the caller.
    
    Fix:
    Moved dict allocation and freeing into corresponding init and fini
    routines so that its easier for the caller to avoid such leaks.
    
    Updates: #1000
    Change-Id: I90d6a6f85ca2dd4fe0ab461177aaa9ac9c1fbcf9
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    (cherry picked from commit 079f7a7d8a2bd85070c1da4dde2452ca82a1cdbb)

commit f9b8462ba212e0fd572efdf6ade03f4d5c53d11e
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Tue Aug 25 12:31:20 2020 +0000

    doc: Updated release 8.1 notes
    
    Updates: #1318
    
    Change-Id: I87787a1aaf59302ad045ed6d2562920e17654678
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit ab40a26dcd9ce8b676f482bf751e57024e227e89
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Sat Aug 22 17:23:25 2020 +0000

    doc: Added release 8.1 notes
    
    Updates: #1318
    
    Change-Id: I14d589bd9af85bdd4ae02902e41d4c5f7d930358
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit f120311737cf681c36423d8551e2e218509cd5f7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Aug 19 11:14:25 2020 +0530

    afr: add null check for thin-arbiter gfid.
    
    Problem:
    Lookup/creation of thin-arbiter ID file happens in background during
    mounting. On new volumes, if the  ID file creation is in progress, and a
    FOP fails on data brick, a post-op (xattrop) is attemtped on TA. Since
    the TA file's gfid is null at this point, the ASSERT checks in protocol/
    client causes a crash.
    
    Fix:
    Given that we decided to do Lookup/creation of thin-arbiter in
    background, fail the other AFR FOPS on TA if the ID file's gfid is null
    instead of winding it down to protocol/client.
    
    Also remove afr_changelog_thin_arbiter_post_op() which seems to be dead
    code.
    
    Updates: #763
    Change-Id: I70dc666faf55cc5c8f7cf8e7d36085e4fa399c4d
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    (cherry picked from commit f9b5074394e3d2f3b6728aab97230ba620879426)

commit 4398db9d70f34e9a8af88fe3de564a906db7b182
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Aug 19 23:27:38 2020 +0200

    open-behind: fix call_frame leak
    
    When an open was delayed, a copy of the frame was created because the
    current frame was used to unwind the "fake" open. When the open was
    actually sent, the frame was correctly destroyed. However if the file
    was closed before needing to send the open, the frame was not destroyed.
    
    This patch correctly destroys the frame in all cases.
    
    Change-Id: I8c00fc7f15545c240e8151305d9e4cf06d653926
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
    Fixes: #1440

commit e173c5b0ee32c210a7d36f03f1847c42218a62e5
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Jul 27 18:08:00 2020 +0530

    posix: Implement a janitor thread to close fd
    
    Problem: In the commit fb20713b380e1df8d7f9e9df96563be2f9144fd6 we use
             syntask to close fd but we have found the patch is reducing the
             performance
    
    Solution: Use janitor thread to close fd's and save the pfd ctx into
              ctx janitor list and also save the posix_xlator into pfd object to
              avoid the race condition during cleanup in brick_mux environment
    
    Change-Id: Ifb3d18a854b267333a3a9e39845bfefb83fbc092
    Fixes: #1396
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    (cherry picked from commit 41b9616435cbdf671805856e487e373060c9455b)

commit 05060c9664153beb392206ae05a498d4d4178f5f
Author: Leonid Ishimnikov <lishim@fastmail.com>
Date:   Thu Aug 13 15:37:50 2020 -0400

    glusterd: dump SSL error stack on disconnect
    
    Problem:  When a non-SSL connection is attempted on an SSL-enabled
              management port, unrelated peers are subsequently disconnected
              from the node with a misleading error message.
    Cause:    A non-SSL client causes OpenSSL to push a wrong version error
              into its thread-local error stack, but this error is never
              cleared, and it lingers in the stack until the thread is used
              by another SSL session, and a certain condition requires the error
              stack to be examined, at which time the old error is discovered and
              the connection is terminated.
    Solution: Log and clear the error stack upon terminating the connection.
    
    Change-Id: I82f3a723285df24dafc88850ae4fca65b69f6ae4
    Fixes: #1418
    Signed-off-by: Leonid Ishimnikov <lishim@fastmail.com>
    (cherry picked from commit bb5801d1480314e09b4203d2525bd01aada5c683)

commit c5fc58c8cb01753e2fed173c76aea1e9cc333862
Author: Vinayakswami Hariharmath <vharihar@redhat.com>
Date:   Thu Aug 6 14:39:59 2020 +0530

    features/shard: optimization over shard lookup in case of prealloc
    
    Assume that we are preallocating a VM of size 1TB with a shard
    block size of 64MB then there will be ~16k shards.
    
    This creation happens in 2 steps shard_fallocate() path i.e
    
    1. lookup for the shards if any already present and
    2. mknod over those shards do not exist.
    
    But in case of fresh creation, we dont have to lookup for all
    shards which are not present as the the file size will be 0.
    Through this, we can save lookup on all shards which are not
    present. This optimization is quite useful in the case of
    preallocating big vm.
    
    Also if the file is already present and the call is to
    extend it to bigger size then we need not to lookup for non-
    existent shards. Just lookup preexisting shards, populate
    the inodes and issue mknod on extended size.
    
    Fixes: #1425
    Change-Id: I60036fe8302c696e0ca80ff11ab0ef5bcdbd7880
    Signed-off-by: Vinayakswami Hariharmath <vharihar@redhat.com>
    (cherry picked from commit 2ede911d07c6dc07a0f729526ab590ace77341ae)

commit 8ef4b79162a0409023b10a15561c84606e0b3ae0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon May 4 14:30:57 2020 +0530

    extras: Modify group 'virt' to include network-related options
    
    This is needed to work around an issue seen where vms running on
    online hosts are getting killed when a different host is rebooted
    in ovirt-gluster hyperconverged environments. Actual RCA is quite
    lengthy and documented in the github issue. Please refer to it
    for more details.
    
    Change-Id: Ic25b5f50144ad42458e5c847e1e7e191032396c1
    Fixes: #1217
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    (cherry picked from commit 5391f16fc4aa00f75af2a4c2707768370ace5f6c)

commit 7b372cdeed876e68293620c25c6821324068fb54
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Jul 23 11:07:32 2020 +0530

    cluster/ec: Remove stale entries from indices/xattrop folder
    
    Problem:
    If a gfid is present in indices/xattrop folder while
    the file/dir is actaully healthy and all the xattrs are healthy,
    it causes lot of lookups by shd on an entry which does not need
    to be healed.
    This whole process eats up lot of CPU usage without doing meaningful
    work.
    
    Solution:
    Set trusted.ec.dirty xattr of the entry so that actual heal process
    happens and at the end of it, during unset of dirty, gfid enrty from
    indices/xattrop will be removed.
    
    Change-Id: Ib1b9377d8dda384bba49523e9ff6ba9f0699cc1b
    Fixes: #1385
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    (cherry picked from commit ba1b0a471dec968633f89c7f790b099fb4ad700d)

commit 7ff51badda5cbcbaa17f729d1e4ab715c462396a
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sat Aug 1 09:28:47 2020 +0530

    glusterd: Increase buffer length to save multiple hostnames in peer file
    
    Problem: At the time of handling friend update request glusterd updates peer
             file and if DNS has returned multiple hostnames for the same IP, glusterd
             saves all hostnames in peer file.In commit 1fa089e7a2b180e0bdcc1e7e09a63934a2a0c0ef
             We changed the approach to save all key value pairs in single shot.
             In case of a buffer is not having space to store the hostnames glusterd
             writes partial hostname in peer file.
    
    Solution: To avoid the failure increase the buffer length
    
    Change-Id: Iee969d165333e9c5ba69431d474c541b8f12d442
    Fixes: #1407
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    (cherry picked from commit 6e8e73a06d71382f8f6e3cd83fe72692d19e66ba)

commit 4be26c88732f55b38da171c86334eddbdaac5c14
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue May 19 16:13:01 2020 +0100

    geo-rep: Fix corner case in rename on mkdir during hybrid crawl
    
    Problem:
    The issue is being hit during hybrid mode while handling rename on slave.
    In this special case the rename is recorded as mkdir and geo-rep process it
    by resolving the path form backend.
    
    While resolving the backend path during this special handling one corner case is not considered.
    
    <snip>
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 118, in worker
        res = getattr(self.obj, rmeth)(*in_data[2:])
      File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 588, in entry_ops
        src_entry = get_slv_dir_path(slv_host, slv_volume, gfid)
      File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 710, in get_slv_dir_path
        dir_entry = os.path.join(pfx, pargfid, basename)
      File "/usr/lib64/python2.7/posixpath.py", line 75, in join
        if b.startswith('/'):
    AttributeError: 'int' object has no attribute 'startswith'
    
    In pyhthon3:
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
      File "/usr/lib64/python3.8/posixpath.py", line 90, in join
        genericpath._check_arg_types('join', a, *p)
      File "/usr/lib64/python3.8/genericpath.py", line 152, in _check_arg_types
        raise TypeError(f'{funcname}() argument must be str, bytes, or '
    TypeError: join() argument must be str, bytes, or os.PathLike object, not 'int'
    </snip>
    
    Backport of:
      >Ptach link: https://review.gluster.org/#/c/glusterfs/+/24468/
      >Change-Id: I8b926899c60ad8c4ffc886d57028ba70fd21e332
      >Fixes: #1250
      >Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
    
    Change-Id: I8b926899c60ad8c4ffc886d57028ba70fd21e332
    Fixes: #1250
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
    
    (cherry picked from commit 27f5c8ba844e9da54fc1304df4ffe015a3bbb9bd)
    
    Change-Id: I171eb9ad4e30f49cfe86cb258918682d3c0f5af9

commit 269ece312c9fd890c74c46e79de70efe1720752c
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Jul 2 18:08:52 2020 +0200

    cluster/ec: Improve detection of new heals
    
    When EC successfully healed a directory it assumed that maybe other
    entries inside that directory could have been created, which could
    require additional heal cycles. For this reason, when the heal happened
    as part of one index heal iteration, it triggered a new iteration.
    
    The problem happened when the directory was healthy, so no new entries
    were added, but its index entry was not removed for some reason. In
    this case self-heal started and endless loop healing the same directory
    continuously, cause high CPU utilization.
    
    This patch improves detection of new files added to the heal index so
    that a new index heal iteration is only triggered if there is new work
    to do.
    
    Change-Id: I2355742b85fbfa6de758bccc5d2e1a283c82b53f
    Fixes: #1354
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 19dc7b37fc9f6d6037958e5dd3c0c6a4a993e2af
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 12 11:07:10 2019 +0530

    features/shard: Convert shard block indices to uint64
    
    This patch fixes a crash in FOPs that operate on really large sharded
    files where number of participant shards could sometimes exceed
    signed int32 max.
    
    The patch also adds GF_ASSERTs to ensure that number of participating
    shards is always greater than 0 for files that do have more than one
    shard.
    
    Change-Id: I354de58796f350eb1aa42fcdf8092ca2e69ccbb6
    Fixes: #1348
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    (cherry picked from commit cdf01cc47eb2efb427b5855732d9607eec2abc8a)

commit 96e7ff7396a8e18ca69d5198be0a8d29bcc37129
Author: Vinayakswami Hariharmath <vharihar@redhat.com>
Date:   Wed Jun 3 18:58:56 2020 +0530

    features/shard: Use fd lookup post file open
    
    Issue:
    When a process has the open fd and the same file is
    unlinked in middle of the operations, then file based
    lookup fails with ENOENT or stale file
    
    Solution:
    When the file already open and fd is available, use fstat
    to get the file attributes
    
    Change-Id: I0e83aee9f11b616dcfe13769ebfcda6742e4e0f4
    Fixes: #1281
    Signed-off-by: Vinayakswami Hariharmath <vharihar@redhat.com>
    (cherry picked from commit 71dd19f710b81136f318b3a95ae430971198ee70)

commit 6b10b33f8a9bce054fec980583cc597f5a438bb5
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jul 2 02:07:56 2020 +0530

    Issue with gf_fill_iatt_for_dirent
    
    In "gf_fill_iatt_for_dirent()", while calculating inode_path for loc,
    the inode should be of parent's. Instead it is loc.inode which results in error
     and eventually lookup/readdirp fails.
    
    This patch fixes the same.
    
    Change-Id: Ied086234a4634e8cb13520521ac547c87b3c76b5
    Fixes: #1351
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    (cherry picked from commit ab8308333aaf033e07dbbdf2f69f9313a7e311f3)

commit e8aedcd40f9f24e5b821e1539275e40ebfccca94
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 29 14:24:53 2020 +0530

    cluster/afr: Delay post-op for fsync
    
    Problem:
    AFR doesn't delay post-op for fsync fop. For fsync heavy workloads
    this leads to un-necessary fxattrop/finodelk for every fsync leading
    to bad performance.
    
    Fix:
    Have delayed post-op for fsync. Add special flag in xdata to indicate
    that afr shouldn't delay post-op in cases where either the
    process will terminate or graph-switch would happen. Otherwise it leads
    to un-necessary heals when the graph-switch/process-termination
    happens before delayed-post-op completes.
    
    Fixes: #1253
    Change-Id: I531940d13269a111c49e0510d49514dc169f4577
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 30b95ff9cdec72d9089f4882dafca447ae3174f1
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 2 15:52:15 2020 -0400

    api: libgfapi symbol versions break LTO in Fedora rawhide/f33
    
    The way symbol versions are implemented is incompatible with gcc-10 and LTO.
    
    Fedora provenpackager Jeff Law (law [at] redhat.com) writes in the
    Fedora dist-git glusterfs.spec:
      This package uses top level ASM constructs which are incompatible with LTO.
      Top level ASMs are often used to implement symbol versioning. gcc-10
      introduces a new mechanism for symbol versioning which works with LTO.
      Converting packages to use that mechanism instead of toplevel ASMs is
      recommended.
    
    In particular, note that the version of gluster in Fedora rawhide/f33 is
    glusterfs-8.0RC0. Once this fix is merged it will be necessary to backport
    it to the release-8 branch.
    
    At the time that gfapi symbol versions were first implemented we copied
    the GNU libc (glibc) symbol version implementation following Uli Drepper's
    symbol versioning HOWTO.
    
    Now gcc-10 has a symver attribute that can be used instead. (Maybe it
    has been there all along?)
    
    Both the original implemenation and this implemenation yield the same
    symbol versions. This can be seen by running
      `nm -D --with-symbol-versions libgfapi.so`
    on the libgfapi.so built before and after applying this fix.
    
    Change-Id: I05fda580afacfff1bfc07be810dd1afc08a92fb8
    Fixes: #1352
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 2e1e4168ab6b6b3ebe9e3dfb227fb7631e5c1aa4
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Sun Jul 5 03:17:04 2020 +0000

    doc: Updated release 8.0 notes
    
    Updates: #1180
    
    Change-Id: I6e5c85f2714896704949d9a99b06eefdde15d633
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 49e3a380055f955303ed6d847aedf1ef61ef71d5
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri May 22 13:25:26 2020 +0530

    features/shard: Aggregate file size, block-count before unwinding removexattr
    
    Posix translator returns pre and postbufs in the dict in {F}REMOVEXATTR fops.
    These iatts are further cached at layers like md-cache.
    Shard translator, in its current state, simply returns these values without
    updating the aggregated file size and block-count.
    
    This patch fixes this problem.
    
    Change-Id: I4b2dd41ede472c5829af80a67401ec5a6376d872
    Fixes: #1243
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    (cherry picked from commit 32519525108a2ac6bcc64ad931dc8048d33d64de)

commit d79e85e4ffa52c40babec777578f98706e334209
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 11 06:46:56 2020 -0400

    packaging: refactor to align with common practices
    
    Apparently some sdditional Obsoletes: are required
    
    Change-Id: I919ae5a0fcc6f720e3eab4784af36977b9eef044
    Fixes: #1126
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 0a97167f850c2fa5ac8f9952f35933fddada3140
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu May 14 06:47:17 2020 -0400

    packaging: refactor to align with common practices
    
    The claim that Fedora package guidelines do not require this
    scheme is a non-argument. Not only do they not require it, they
    don't prohibit it either. (And you can't prove a negative. It's
    a specious argument.)
    
    Change-Id: I7748c7531d52dedd71b3a7f5df049742258a6aba
    Fixes: #1126
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 80e088be4470d86e5c63750f611a39e487a591b3
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue May 12 23:54:54 2020 +0200

    open-behind: rewrite of internal logic
    
    There was a critical flaw in the previous implementation of open-behind.
    
    When an open is done in the background, it's necessary to take a
    reference on the fd_t object because once we "fake" the open answer,
    the fd could be destroyed. However as long as there's a reference,
    the release function won't be called. So, if the application closes
    the file descriptor without having actually opened it, there will
    always remain at least 1 reference, causing a leak.
    
    To avoid this problem, the previous implementation didn't take a
    reference on the fd_t, so there were races where the fd could be
    destroyed while it was still in use.
    
    To fix this, I've implemented a new xlator cbk that gets called from
    fuse when the application closes a file descriptor.
    
    The whole logic of handling background opens have been simplified and
    it's more efficient now. Only if the fop needs to be delayed until an
    open completes, a stub is created. Otherwise no memory allocations are
    needed.
    
    Correctly handling the close request while the open is still pending
    has added a bit of complexity, but overall normal operation is simpler.
    
    Change-Id: I6376a5491368e0e1c283cc452849032636261592
    Fixes: #1225
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 6872b75caf7a7bc945dba73c381236f344548728
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri May 15 11:29:36 2020 +0530

    features/shard: Aggregate size, block-count in iatt before unwinding setxattr
    
    Posix translator returns pre and postbufs in the dict in {F}SETXATTR fops.
    These iatts are further cached at layers like md-cache.
    Shard translator, in its current state, simply returns these values without
    updating the aggregated file size and block-count.
    
    This patch fixes this problem.
    
    Change-Id: I4da0eceb4235b91546df79270bcc0af8cd64e9ea
    Fixes: #1243
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    (cherry picked from commit 29ec66c6ab77e2d6893c6e213a3d1fb148702c99)

commit 215cf1728e029d062b21b712b6c5356b3bf73794
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed May 27 20:50:46 2020 +0530

    afr: more quorum checks in lookup and new entry marking
    
    Problem: See github issue for details.
    
    Fix:
    -In lookup if the entry exists in 2 out of 3 bricks, don't fail the
    lookup with ENOENT just because there is an entrylk on the parent.
    Consider quorum before deciding.
    
    -If entry FOP does not succeed on quorum no. of bricks, do not perform
    new entry mark.
    
    Fixes: #1303
    Change-Id: I56df8c89ad53b29fa450c7930a7b7ccec9f4a6c5
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    (cherry picked from commit c4a6748f25d2c1ab3ebcf89952278ebf94c8d371)

commit 8c1008646ec7e62b33d92184358eb455f7e44350
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Jun 12 00:06:36 2020 +0200

    locks: prevent deletion of locked entries
    
    To keep consistency inside transactions started by locking an entry or
    an inode, this change delays the removal of entries that are currently
    locked by one or more clients. Once all locks are released, the removal
    is processed.
    
    It has also been improved the detection of stale inodes in the locking
    code of EC.
    
    Fixes: #990
    Change-Id: Ic8ba23d9480f80c7f74e7a310bf8a15922320fd5
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 3e8c565504aa9f61f0e362072170e8d8e974c2c7
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu May 21 15:18:59 2020 +0530

    cluster/afr: Prioritize ENOSPC over other errors
    
    Problem:
    In a replicate/arbiter volume if file creations or writes fails on
    quorum number of bricks and on one brick it is due to ENOSPC and
    on other brick it fails for a different reason, it may fail with
    errors other than ENOSPC in some cases.
    
    Fix:
    Prioritize ENOSPC over other lesser priority errors and do not set
    op_errno in posix_gfid_set if op_ret is 0 to avoid receiving any
    error_no which can be misinterpreted by __afr_dir_write_finalize().
    
    Also removing the function afr_has_arbiter_fop_cbk_quorum() which
    might consider a successful reply form a single brick as quorum
    success in some cases, whereas we always need fop to be successful
    on quorum number of bricks in arbiter configuration.
    
    Change-Id: I106e267f8b9451f681022f1cccb410d9bc824c08
    Fixes: #1254
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    (cherry picked from commit fa63b45ca5edf172b1b89b28b5db3c5129cc57b6)

commit 18bd1bdaa6ea5d589b21865769d6183e4e201006
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Apr 17 12:10:05 2020 +0200

    md-cache: fix several NULL dereferences
    
    This patch includes the following CID from Coverity Scan:
    
      * 1425196
      * 1425197
      * 1425198
      * 1425199
      * 1525200
    
    Change-Id: Iddcfea449d3dd56d4dfcc39f4c3c608518e611e4
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
    Updates: #1060
    (cherry picked from commit b53ba17dbfd2d18c10e2c308b8899d36726ab440)

commit 9399faa68968bc2aaff7390580cb072f2926c8ed
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Thu Apr 23 14:32:02 2020 +0000

    doc: Added release 8.0 notes
    
    Updates: #1180
    
    Change-Id: If3ff097e299261f2b647d5faa85d268b0a86908c
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 67cd2b1ab5c9a8db637506b9a6be57fc79672c99
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Apr 30 11:19:01 2020 +0200

    syncop: improve scaling and implement more tools
    
    The current scaling of the syncop thread pool is not working properly
    and can leave some tasks in the run queue more time than necessary
    when the maximum number of threads is not reached.
    
    This patch provides a better scaling condition to react faster to
    pending work.
    
    Condition variables and sleep in the context of a synctask have also
    been implemented. Their purpose is to replace regular condition
    variables and sleeps that block synctask threads and prevent other
    tasks to be executed.
    
    The new features have been applied to several places in glusterd.
    
    Change-Id: Ic50b7c73c104f9e41f08101a357d30b95efccfbf
    Fixes: #1116
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 49713a7ea1d30613a8810b85eca8ab35f6e9fa8a
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu May 28 08:26:47 2020 -0400

    common-ha: ganesha-ha.sh bad test for {rhel,centos} for pcs options
    
    bash [[ ... =~ ... ]] built-in returns _0_ when the regex matches,
    not 1, thus the sense of the test is backwards and never correctly
    detects rhel or centos.
    
    master commit: eaf126f4b06a842977c1932ce699c4d76421a4b2
    
    Change-Id: Ic9e60aae4ea38aff8f13979080995e60621a68fe
    Fixes: #1269
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 1572f98486bf3204b5d2d89da880b92e26734c3c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 6 17:36:20 2020 +0530

    tests: skip tests on absence of reflink in xfs
    
    Fixes: #1223
    Change-Id: I36cb72d920ffd77405051546615c5262c392daef
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    (cherry picked from commit b85f01abab658d1d704cd6caf84dd64eddafbff7)

commit 2ae5b28030b08348ec5e4c08ada8600943db0366
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri May 8 23:01:04 2020 +0200

    fuse: occasional logging for fuse device 'weird' write errors
    
    This change is a followup to
    I510158843e4b1d482bdc496c2e97b1860dc1ba93.
    
    In referred change we pushed log messages about 'weird'
    write errors to fuse device out of sight, by reporting
    them at Debug loglevel instead of Error (where
    'weird' means errno is not POSIX compliant but having
    meaningful semantics for FUSE protocol).
    
    This solved the issue of spurious error reporting.
    And so far so good: these messages don't indicate
    an error condition by themselves. However, when they
    come in high repetitions, that indicates a suboptimal
    condition which should be reported.[1]
    
    Therefore now we shall emit a Warning if a certain
    errno occurs a certain number of times[2] as the
    outcome of a write to the fuse device.
    
    ___
    [1] typically ENOENTs and ENOTDIRs accumulate
    when glusterfs' inode invalidation lags behind
    the kernel's internal inode garbage collection
    (in this case above errnos mean that the inode
    which we requested to be invalidated is not found
    in kernel). This can be mitigated with the
    invalidate-limit command line / mount option,
    cf. bz#1732717.
    
    [2] 256, as of the current implementation.
    
    Change-Id: I8cc7fe104da43a88875f93b0db49d5677cc16045
    Updates: #1000
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    (cherry picked from commit c1baf3c68b87584aea5389af958326f6ed01d7ec)

commit 984a8dd8fa3e371fa1336730d6dc0041ceef877c
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue May 5 18:17:49 2020 +0530

    cluster/ec: Return correct error code and log message
    
    In case of readdir was send with an FD on which opendir
    was failed, this FD will be useless and we return it with error.
    For now, we are returning it with EINVAL without logging any
    message in log file.
    
    Return a correct error code and also log the message to improve thing to debug.
    
    fixes: #1220
    Change-Id: Iaf035254b9c5aa52fa43ace72d328be622b06169
    (cherry picked from commit af70cb5eedd80207cd184e69f2a4fb252b72d070)

commit 1c8af2522458e3763302ec408fe1832dff150efa
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Apr 10 14:30:57 2020 +0530

    afr: event gen changes
    
    The general idea of the changes is to prevent resetting event generation
    to zero in the inode ctx, since event gen is something that should
    follow 'causal order'.
    
    Change #1:
    For a read txn, in inode refresh cbk, if event_generation is
    found zero, we are failing the read fop. This is not needed
    because change in event gen is only a marker for the next inode refresh to
    happen and should not be taken into account by the current read txn.
    
    Change #2:
    The event gen being zero above can happen if there is a racing lookup,
    which resets even get (in afr_lookup_done) if there are non zero afr
    xattrs. The resetting is done only to trigger an inode refresh and a
    possible client side heal on the next lookup. That can be acheived by
    setting the need_refresh flag in the inode ctx. So replaced all
    occurences of resetting even gen to zero with a call to
    afr_inode_need_refresh_set().
    
    Change #3:
    In both lookup and discover path, we are doing an inode refresh which is
    not required since all 3 essentially do the same thing- update the inode
    ctx with the good/bad copies from the brick replies. Inode refresh also
    triggers background heals, but I think it is okay to do it when we call
    refresh during the read and write txns and not in the lookup path.
    
    The .ts which relied on inode refresh in lookup path to trigger heals are
    now changed to do read txn so that inode refresh and the heal happens.
    
    Change-Id: Iebf39a9be6ffd7ffd6e4046c96b0fa78ade6c5ec
    Fixes: #1179
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reported-by: Erik Jacobson <erik.jacobson at hpe.com>
    (cherry picked from commit f0fcd909ad4535b60c9208d4804ebe6afe421a09)

commit f949c3e13e42d52fd5c230fc2f2607d327aad9d1
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Fri Apr 17 13:26:50 2020 +0000

    Update rfc.sh for release-8
    
    updates: #1180
    
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 0e94dbb81154edcc7d1182527663a7340fbeab01
Author: Barak Sason Rofman <sason922@gmail.com>
Date:   Sun Apr 12 18:19:41 2020 +0300

    dht - Remove "tier" code (part 1)
    
    This patch is removing some of the "tier" code in dht xlator, as it is no longer
    being used.
    Not all of the not-needed code is removed at once, so reviewing is easier.
    Follow up patches removing additional unused code will follow.
    
    This is based in the work done in https://review.gluster.org/#/c/glusterfs/+/23935/
    
    Change-Id: I3cb6a0c5d8f14afcd87cf021ef8f74b91c0f908a
    updates: #1097
    Signed-off-by: Barak Sason Rofman <bsaonro@redhat.com>

commit 39f4a03cbaa7b3b93a3750258607cbd91b9d4b9d
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Apr 10 13:45:50 2020 +0530

    tests: Fix for spurious failure for some test cases
    
    Problem: Sometimes test case is failing at the time of creating files
             on mount point after mounting the volume
    
    Solution: After started the volume need to wait to make sure all
              bricks instances are completely started so put a online_brick_count
              check after just started the volume
    
    Change-Id: I5020e7e417539377277ca00189f9c51d2cf877a6
    Fixes: #1162
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit f507c20bd11565c329d103075a15da11dba461d5
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Mon Mar 30 11:09:39 2020 +0200

    md-cache: avoid clearing cache when not necessary
    
    mdc_inode_xatt_set() blindly cleared current cache when dict was not
    NULL, even if there was no xattr requested.
    
    This patch fixes this by only calling mdc_inode_xatt_set() when we have
    explicitly requested something to cache.
    
    Change-Id: Idc91a4693f1ff39f7059acde26682ccc361b947d
    Fixes: #1140
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 453861088dfabde2c41bec674bed2a6886b4ed37
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Dec 25 22:56:12 2019 +0530

    posix: fix GF_VALIDATE_OR_GOTO(this->name, this, out)
    
    Remove GF_VALIDATE_OR_GOTO(this->name, this, out) when this
    is passed as an argument and is checked for NULL in the caller
    itself.
    
    GF_VALIDATE_OR_GOTO(this->name, this, out) is modified to use
    xlator name instead of this->name as we are still verifying
    whether this is NULL.
    
    updates: #1000
    
    Change-Id: Ide3180da29d0d4a35b2c5b9a7604fdf2ff4a9ffb
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit d0cb5cbaff22ec5fcb685a327d6d54e5ae8d87f2
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Apr 9 13:08:23 2020 +0530

    test: tests/bugs/rpc/bug-847624.t is crashed
    
    Problem: glusterfs(GNFS) is crashing at the time of handling
             Pollerr event in rpcsvc_drc_client_unref.GNFS is crashed
             because ref was 0 at the time of unref and ref was taken
             while Pollin event successfully handled.
    
    Solution: Convert drc_client ref to atomic ref to avoid the crash
    
    Change-Id: Ia4c054f2f388032a5cd99597d0cfa18b003ca690
    Fixes: #1038
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 0407d10f147862eb1c7854aed3adfbc3e1503c5d
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Fri Apr 10 11:13:12 2020 +0300

    tests: do not truncate file offsets and sizes to 32-bit
    
    Do not truncate file offsets and sizes to 32-bit to
    prevent tests from spurious failures on >2Gb files.
    
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
    
    Change-Id: I2a77ea5f9f415249b23035eecf07129f19194ac2
    Fixes: #1161

commit 0abdd69636c42ec410a0615763f5c2ca4dca8f75
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 14 07:59:22 2020 -0400

    common-ha: cluster status shows "FAILOVER" when actually HEALTHY
    
    pacemaker devs change the format of the ouput of `pcs status`
    
    Expected to find a line in the format:
    
    Online: ....
    
    but now it's
    
      * Online: ...
    
    And the `grep -E "^Online:" no longer finds the list of nodes that
    are online.
    
    Change-Id: If2aa1e7b53c766c625d7b4cc222a83ea2c0bd72d
    Fixes: #1169
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 43ed6fa34b259b568ae1442b65a5004a894a2654
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Thu Apr 9 13:51:22 2020 +0000

    tests: Fix spurious failure of worm.t
    
    When the output of date command is a single digit
    number it is preceded by zero which is getting
    considered as an octal number. Removing the leading
    zero from the number solved the problem.
    
    Fixes: #1156
    
    Change-Id: Iac4fa20607c0bb90d94dd8ff157ef6b60932c560
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 0644fce4e52cd738f7ebb5e0596481a256fed3da
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Fri Apr 10 10:47:17 2020 +0300

    mgmt/glusterd: use stat() syscall wrapper
    
    Found with 0-symbol-check.t:
    
    ./tests/basic/0symbol-check.t ..
    1..2
    ./xlators/mgmt/glusterd/src/.libs/glusterd_la-glusterd-volume-set.o should call sys_stat, not stat
    ok   1 [     40/  41011] <  40> 'find . -name *.o -exec ./tests/basic/symbol-check.sh {} \;'
    not ok   2 [     11/      1] <  42> '[ ! -e ./.symbol-check-errors ]' -> ''
    Failed 1/2 subtests
    
    Change-Id: I8962f487cd88738a1f7a962049d513712687088c
    Fixes: #1160
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>

commit d357863f4fc5be09b96ef3b359100d741efc0b4f
Author: Barak Sason Rofman <sason922@gmail.com>
Date:   Sun Apr 12 13:50:33 2020 +0300

    test: Fix test "bug-1064148" to pass in mux
    
    Parts of the test weren't designed to run in mux mode, this is now fixed
    
    Change-Id: I428c2fcce6d047e324ca5dcaef677ee1794e3dfe
    updates: #1154
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit cd77bddacb4eefb8c447c82220780626b878c3f0
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Apr 9 21:55:46 2020 +0530

    tests: Fix spurious failure of tests/bugs/glusterd/serialize-shd-manager-glusterd-restart.t
    
    Problem: Sometime volume status is failed after restart glusterd
             in one cluster node
    
    Solution: Wait to finish glusterd handshake on down cluster node
    
    Change-Id: Ib23ca41c943caf2903c61ebf42dc437c1b9d6054
    Fixes: #1158
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a57980e37416994b99b20d19a495527fb49c0372
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Thu Apr 9 01:59:03 2020 +0530

    protocol/server: Fix coverity issue RESOURCE_LEAK
    
    Handle case of arg not freed
    CID: 1422174
    
    Updates: #1060
    Change-Id: Ibd03908a3ea8369035c2b7f6e024b3e5be48f436
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 82db4f23d201b1078129d083370563f68251d897
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Tue Jan 14 08:26:12 2020 +0530

    Adding basic glusterfind test case
    
    This test case includes all the basic glusterfind scenarios.
    
    fixes: #1044
    Change-Id: I6021443729e35769fe855c5cc41bb3fbc6365ef0
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 18f70e806bcef5a3680462a4dbb7061e5eceee1c
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Apr 6 21:58:03 2020 +0530

    posix: Avoid dict_del logs in posix_is_layout_stale while key is NULL
    
    Problem: The key "GF_PREOP_PARENT_KEY" has been populated by dht and
             for non-distribute volume like 1x3 key is not populated so
             posix_is_layout stale throw a message while a file is created
    
    Solution: To avoid a log put a condition before delete a key
    
    Change-Id: I813ee7960633e7f9f5e9ad2f42f288053d9eb71f
    Fixes: #1150
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 9115dd39e953953495d48c6d6f24f44828f8bd5f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 7 16:05:16 2020 +0530

    mount/fuse: Wait for 'mount' child to exit before dying
    
    Problem:
    tests/bugs/protocol/bug-1433815-auth-allow.t fails
    sometimes because of stale mount. This stale mount
    comes into picture when parent process dies without
    waiting for the child process which mounts fuse fs
    to die
    
    Fix:
    Wait for mounting child process to die before dying.
    
    Fixes: #1152
    Change-Id: I8baee8720e88614fdb762ea822d5877973eef8dc
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 4398f68dada29418d2ec68ec538ec1378108221a
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Fri Mar 27 11:13:29 2020 +0530

    [geo-rep] Merging multiple import into single import
    
    Geo-replication has a large number of repeated imports as shown below:
    ```
    from syncdutils import set_term_handler, finalize, lf
    from syncdutils import log_raise_exception, FreeObject, escape
    ```
    
    There imports can be clubbed together as shown below:
    ``
    from syncdutils import (set_term_handler, finalize, lf,
                            log_raise_exception, FreeObject, escape)
    ```
    
    Fixes: #1105
    Change-Id: I59a48dd57a70fc851d93150b85e736ce41e8b793
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit 6917f52e6a9fd65f30f81302f3b84c734950810d
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Wed Jan 15 12:02:05 2020 +0200

    dht - fixing a permission update issue
    
    When bringing back a downed brick and performing lookup from the client
    side, the permission on said brick aren't updated on the first lookup,
    but only on the second.
    
    This patch modifies permission update logic so the first lookup will
    trigger a permission update on the downed brick.
    
    LIMITATIONS OF THE PATCH:
    As the choice of source depends on whether the directory has layout or not.
    Even the directories on the newly added brick will have layout xattr[zeroed], but the same is not true for a root directory.
    Hence, in case in the entire cluster only the newly added bricks are up [and others are down], then any change in permission during this time will be overwritten by the older permissions when the cluster is restarted.
    
    fixes: #999
    Change-Id: Ieb70246d41e59f9cae9f70bc203627a433dfbd33
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit ae8867fcfa5b14008a1c9a29674e971f502e1a61
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 7 20:55:19 2020 +0530

    tests: Fix spurious failure of tests/bugs/snapshot/bug-1111041.t
    
    Test should wait for process down notification to be received
    by glusterd.
    
    Fixes: #1153
    Change-Id: I9162b58a92c1a909ca98097f14c0714f9086bdd1
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 55914f968d907ed747774da15285b42653afda61
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Apr 6 12:36:44 2020 +0530

    gfapi: Suspend synctasks instead of blocking them
    
    There are certain conditions which blocks the current
    execution thread (like waiting on mutex lock or condition
    variable or I/O response). In such cases, if it is a
    synctask thread, we should suspend the task instead
    of blocking it (like done in SYNCOP using synctask_yield)
    
    This is to avoid deadlock like the one mentioned below -
    
    1) synctaskA sets fs->migration_in_progress to 1 and
       does I/O (LOOKUP)
    2) Other synctask threads wait for fs->migration_in_progress
      to be reset to 0 by synctaskA and hence blocked
    3) but synctaskA cannot resume as all synctask threads are blocked
       on (2).
    
    Note: this same approach is already used by few other components
    like syncbarrier etc.
    
    Change-Id: If90f870d663bb242c702a5b86ac52eeda67c6f0d
    Fixes: #1146
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit e1ad1483e0e82d70fcc32311b7842bc9a77c04aa
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Apr 2 13:03:35 2020 +0530

    cluster/afr: Removing unsupported options from code base to improve coverage
    
    Support for gluster volume heal <volname> info healed/heal-failed
    was removed by commit bb02cfb56ae08f56df4452c2b948fa962ae1212b in
    release-3.6. cli parser will display the usage message in all the
    supported versions whenever these clis are run, leading to some
    dead code in the latest branches. Since support for these clis
    were removed long back, this should not give any backward
    compatibility issues as well. Hence removing the dead code from
    the code base which will lead to better code coverage by the
    regression runs as well.
    
    Updates: #1052
    Change-Id: I0c2b061469caf233c06d9699b0d159ce48e240b9
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit f2d90013aaa4652dbcc1e6e3d62a0d31ada89d5d
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Dec 19 08:32:19 2019 +0530

    Posix: Optimize posix code to improve file creation
    
    Problem: Before executing a fop in POSIX xlator it builds an internal
             path based on GFID.To validate the path it call's (l)stat
             system call and while .glusterfs is heavily loaded kernel takes
             time to lookup inode and due to that performance drops
    
    Solution: In this patch we followed two ways to improve the performance.
              1) Keep open fd specific to first level directory(gfid[0])
                 in .glusterfs, it would force to kernel keep the inodes
                 from all those files in cache. In case of memory pressure
                 kernel won't uncache first level inodes. We need to open
                 256 fd's per brick to access the entry faster.
              2) Use at based call's to access relative path to reduce
                 path based lookup time.
    
    Note: To verify the patch we have executed kernel untar 100 times on 6
          different clients after enabling metadata group-cache and some
          other option.We were getting more than 20 percent improvement in
          kenel untar after applying the patch.
    
    Credits: Xavi Hernandez <xhernandez@redhat.com>
    Change-Id: I1643e6b01ed669b2bb148d02f4e6a8e08da45343
    updates: #891
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 28299f7852229be333102e08aae9b7fd4ad3338a
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Apr 1 13:31:50 2020 +0530

    cluster/ec: Add test for reset-brick command
    
    Following tests are done -
    
    1 - After finishing reset-brick all the bricks should be up.
    2 - Heal should be completed.
    3 - Check number of entries present on brick which was reset.
    
    Change-Id: I9314bed180293a99d400d94bb8cc7ece999da29e
    Updates: #1144

commit c61171ea24873b492d0100e376365db59235d321
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Apr 3 12:34:07 2020 -0700

    mgmt/glusterd: Reduce log level of repetitive log
    
    Noticed that the following message repeats quite a bit in log files when
    an external monitoring tool queries gluster for list of volumes
    periodically:
    
    "Received get vol req"
    
    As there's not much value in having this log message at log level INFO,
    changing the log level to DEBUG to make glusterd.log a bit quieter.
    
    Change-Id: I4e791fc65b9a4f813d295e7b2b6a05f3c0782e69
    Updates: #1000
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 945b0a12b7a47039260330e02b89919c2cefb8d2
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Apr 3 15:25:44 2020 +0530

    fuse: Add error-logs to debug bug-1433815-auth-allow.t failures
    
    Fixes: #1149
    Change-Id: I38483fc7d76d7fe0ac9fb649669a46bdf9c82234
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 208b6d7b1a4d98e62d4bfa3b342bb78ade078799
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Mar 31 11:25:51 2020 -0400

    storage/posix: log the ENOENT errors in posix_pstat
    
    Change-Id: I93f11dae6e4939ab79b0481ead2a4f7bb3085b70
    Fixes: #1142
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 77889c34b6f169dfc3257e2b566afa2f4bad1697
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Mar 27 23:56:15 2020 +0100

    write-behind: fix data corruption
    
    There was a bug in write-behind that allowed a previous completed write
    to overwrite the overlapping region of data from a future write.
    
    Suppose we want to send three writes (W1, W2 and W3). W1 and W2 are
    sequential, and W3 writes at the same offset of W2:
    
        W2.offset = W3.offset = W1.offset + W1.size
    
    Both W1 and W2 are sent in parallel. W3 is only sent after W2 completes.
    So W3 should *always* overwrite the overlapping part of W2.
    
    Suppose write-behind processes the requests from 2 concurrent threads:
    
        Thread 1                    Thread 2
    
        <received W1>
                                    <received W2>
        wb_enqueue_tempted(W1)
        /* W1 is assigned gen X */
                                    wb_enqueue_tempted(W2)
                                    /* W2 is assigned gen X */
    
                                    wb_process_queue()
                                      __wb_preprocess_winds()
                                        /* W1 and W2 are sequential and all
                                         * other requisites are met to merge
                                         * both requests. */
                                        __wb_collapse_small_writes(W1, W2)
                                        __wb_fulfill_request(W2)
    
                                      __wb_pick_unwinds() -> W2
                                      /* In this case, since the request is
                                       * already fulfilled, wb_inode->gen
                                       * is not updated. */
    
                                    wb_do_unwinds()
                                      STACK_UNWIND(W2)
    
                                    /* The application has received the
                                     * result of W2, so it can send W3. */
                                    <received W3>
    
                                    wb_enqueue_tempted(W3)
                                    /* W3 is assigned gen X */
    
                                    wb_process_queue()
                                      /* Here we have W1 (which contains
                                       * the conflicting W2) and W3 with
                                       * same gen, so they are interpreted
                                       * as concurrent writes that do not
                                       * conflict. */
                                      __wb_pick_winds() -> W3
    
                                    wb_do_winds()
                                      STACK_WIND(W3)
    
        wb_process_queue()
          /* Eventually W1 will be
           * ready to be sent */
          __wb_pick_winds() -> W1
          __wb_pick_unwinds() -> W1
            /* Here wb_inode->gen is
             * incremented. */
    
        wb_do_unwinds()
          STACK_UNWIND(W1)
    
        wb_do_winds()
          STACK_WIND(W1)
    
    So, as we can see, W3 is sent before W1, which shouldn't happen.
    
    The problem is that wb_inode->gen is only incremented for requests that
    have not been fulfilled but, after a merge, the request is marked as
    fulfilled even though it has not been sent to the brick. This allows
    that future requests are assigned to the same generation, which could
    be internally reordered.
    
    Solution:
    
    Increment wb_inode->gen before any unwind, even if it's for a fulfilled
    request.
    
    Special thanks to Stefan Ring for writing a reproducer that has been
    crucial to identify the issue.
    
    Change-Id: Id4ab0f294a09aca9a863ecaeef8856474662ab45
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
    Fixes: #884

commit f55c45537435cc2a1412c80a6c922db63ce65965
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Apr 2 15:30:28 2020 +0530

    features/utime: Don't access frame after stack-wind
    
    Problem:
    frame is accessed after stack-wind. This can lead to crash
    if the cbk frees the frame.
    
    Fix:
    Use new frame for the wind instead.
    
    Updates: #832
    Change-Id: I64754609f1114b0bbd4d1336fa81a56f2cca6e03
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit a7d7ec066e56ac03bf252c26beb20fdc2c3b6772
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Mar 26 10:46:16 2020 +0000

    snap_scheduler: python3 compatibility and new test case
    
    Problem:
    "snap_scheduler.py init" command failing with the below traceback:
    
    [root@dhcp43-104 ~]# snap_scheduler.py init
    Traceback (most recent call last):
      File "/usr/sbin/snap_scheduler.py", line 941, in <module>
        sys.exit(main(sys.argv[1:]))
      File "/usr/sbin/snap_scheduler.py", line 851, in main
        initLogger()
      File "/usr/sbin/snap_scheduler.py", line 153, in initLogger
        logfile = os.path.join(process.stdout.read()[:-1], SCRIPT_NAME + ".log")
      File "/usr/lib64/python3.6/posixpath.py", line 94, in join
        genericpath._check_arg_types('join', a, *p)
      File "/usr/lib64/python3.6/genericpath.py", line 151, in _check_arg_types
        raise TypeError("Can't mix strings and bytes in path components") from None
    TypeError: Can't mix strings and bytes in path components
    
    Solution:
    
    Added the 'universal_newlines' flag to Popen to support backward compatibility.
    
    Added a basic test for snapshot scheduler.
    
    Change-Id: I78e8fabd866fd96638747ecd21d292f5ca074a4e
    Fixes: #1134
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 80dd8cceab3b860bf1bc2945c8e2d8d0b3913e48
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Mar 31 16:45:35 2020 +0530

    rpc: Make ssl log more useful
    
    Currently, ssl_setup_connection_params throws 4 messages for every
    rpc connection that irritates a user while reading the logs. The same
    info we can print in a single log with peerinfo to make it more
    useful.ssl_setup_connection_params try to load dh_param even user
    has not configured it and if a dh_param file is not available it throws
    a failure message.To avoid the message load dh_param only while the user
    has configured it.
    
    Change-Id: I9ddb57f86a3fa3e519180cb5d88828e59fe0e487
    Fixes: #1141
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 2d5ba449e9200b16184b1e7fc84cabd015f1f779
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 24 13:00:19 2018 +0530

    afr: mark pending xattrs as a part of metadata heal
    
    ...if pending xattrs are zero for all children.
    
    Problem:
    If there are no pending xattrs and a metadata heal needs to be
    performed, it can be possible that we end up with xattrs inadvertendly
    deleted from all bricks, as explained in the  BZ.
    
    Fix:
    After picking one among the sources as the good copy, mark pending xattrs on
    all sources to blame the sinks. Now even if this metadata heal fails midway,
    a subsequent heal will still choose one of the valid sources that it
    picked previously.
    
    Fixes: #1067
    Change-Id: If1b050b70b0ad911e162c04db4d89b263e2b8d7b
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 6ef82683064a87c434bd67e2004935281e4c04cc
Author: l17zhou <cynthia.zhou@nokia-sbell.com>
Date:   Tue Dec 3 07:43:35 2019 +0200

    add clean local after grant lock
    
    found by flock test, without correct ref number of fd,
    lock will not be correctly released.
    
    Fixes: bz#1779089
    Change-Id: I3e466b17c852eb219c8778e43af8ad670a8449cc
    Signed-off-by: l17zhou <cynthia.zhou@nokia-sbell.com>

commit 936f8b2fc666a2c18b16bee7ab14da6dd7bfd5f2
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Mon Mar 30 14:08:09 2020 +0530

    Marker: Logically deadcode found by coverity
    
    Have removed the deadcode found by the coverity id:1356503
    
    Change-Id: Ieaa41e864538fb82dc967b4a214d4db09e267098
    Updates: #1060
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit e589d8de66d3325da8fbbbe44d1a5bd6335e08ab
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Mar 4 09:17:26 2020 +0530

    core[brick_mux]: brick crashed when creating and deleting volumes over time
    
    Problem: In brick_mux environment, while volumes are created/stopped in a loop
             after running a long time the main brick is crashed.The brick is crashed
             because the main brick process was not cleaned up memory for all objects
             at the time of detaching a volume.
             Below are the objects that are missed at the time of detaching a volume
             1) xlator object for a brick graph
             2) local_pool for posix_lock xlator
             3) rpc object cleanup at quota xlator
             4) inode leak at brick xlator
    
    Solution: To avoid the crash resolve all leak at the time of detaching a brick
    Change-Id: Ibb6e46c5fba22b9441a88cbaf6b3278823235913
    updates: #977
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit cc43ac8651de9aa508b01cb259b43c02d89b2afc
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Mar 23 11:47:10 2020 +0530

    features/shard: Fix crash during shards cleanup in error cases
    
    A crash is seen during a reattempt to clean up shards in background
    upon remount. And this happens even on remount (which means a remount
    is no workaround for the crash).
    
    In such a situation, the in-memory base inode object will not be
    existent (new process, non-existent base shard).
    So local->resolver_base_inode will be NULL.
    
    In the event of an error (in this case, of space running out), the
    process would crash at the time of logging the error in the following line -
    
            gf_msg(this->name, GF_LOG_ERROR, local->op_errno, SHARD_MSG_FOP_FAILED,
                   "failed to delete shards of %s",
                   uuid_utoa(local->resolver_base_inode->gfid));
    
    Fixed that by using local->base_gfid as the source of gfid when
    local->resolver_base_inode is NULL.
    
    Change-Id: I0b49f2b58becd0d8874b3d4b14ff8d92a89d02d5
    Fixes: #1127
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit c375f25b3e305cef2ab020866a10f26a7fbf1957
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Mar 16 11:39:56 2020 +0530

    dht: gf_defrag_process_dir is called even if gf_defrag_fix_layout has failed
    
    Currently even though gf_defrag_fix_layout fails with ENOENT or ESTALE, a
    subsequent call is made to gf_defrag_process_dir leading to rebalance failure.
    
    fixes: #1102
    Change-Id: Ib0c309fd78e89a000fed3feb4bbe2c5b48e61478
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 7ee3c9a42fc7584d90da6158ef7510551a915b2b
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Mar 17 15:42:59 2020 +0000

    worm-xlator: fix newly introduced coverity issue
    
    This patch fixes CID: 1420405
    
    updates: #1060
    
    Change-Id: I0524e999fa1d36ed5a713eabf65482c04ad43a1a
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit fb20713b380e1df8d7f9e9df96563be2f9144fd6
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Mar 12 21:12:13 2020 +0530

    Posix: Use simple approach to close fd
    
    Problem: posix_release(dir) functions add the fd's into a ctx->janitor_fds
             and janitor thread closes the fd's.In brick_mux environment it is
             difficult to handle race condition in janitor threads because brick
             spawns a single janitor thread for all bricks.
    
    Solution: Use synctask to execute posix_release(dir) functions instead of
              using background a thread to close fds.
    
    Credits: Pranith Karampuri <pkarampu@redhat.com>
    Change-Id: Iffb031f0695a7da83d5a2f6bac8863dad225317e
    Fixes: bz#1811631
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 5410cc35ea09b1932c8eae4933fbf84f462e61ea
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Mar 16 15:17:23 2020 +0000

    geo-rep: descriptive message when worker crashes due to EIO
    
    With this patch now you can notice log if it is due to EIO:
    
    [2020-03-16 16:24:48.293837] E [syncdutils(worker /bricks/brick1/mbr3):348:log_raise_exception] <top>: Getting "Input/Output error" is most likely due to a. Brick is down or b. Split brain issue.
    [2020-03-16 16:24:48.293915] E [syncdutils(worker /bricks/brick1/mbr3):352:log_raise_exception] <top>: This is expected as per design to keep the consistency of the file system. Once the above issue is resolved geo-rep would automatically proceed further.
    
    Change-Id: Ie33f2440bc96089731ce12afa8dab91d9550a7ca
    Fixes: #1104
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 476139c962c298b2d00a3d42b90632fc25401526
Author: David Spisla <david.spisla@iternity.com>
Date:   Tue Feb 25 10:57:36 2020 +0100

    WORM-Xlator: Initial write of a file succeeds if auto-commit-period 0
    
    If worm-file-level enabled and auto-commit-period 0 an initial write
    of a file (e.g. $ echo test >> file1.txt) would lead to an zero byte
    file because the WORM xlator immediately WORMed the file when it was
    created.
    
    To avoid this we move the setting of trusted.worm_file from
    worm_create_cbk to worm_release . This means that this xattr will set
    when the filehandle is closed and all initial WRITE FOPs succeed.
    
    Finally we also perform gf_worm_state_transition in worm_release to
    ensure that the file will be immediately WORMed after the file handle
    was closed.
    
    Change-Id: I5d02e18975b646ca1a27ed41d836e9d0dc333204
    Fixes: bz#1808421
    Signed-off-by: David Spisla <david.spisla@iternity.com>

commit b30f76980fc5d01b569d9409b68d24d809444ff8
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Sun Mar 8 18:36:45 2020 +0100

    open-behind: fix missing fd reference
    
    Open behind was not keeping any reference on fd's pending to be
    opened. This makes it possible that a concurrent close and en entry
    fop (unlink, rename, ...) caused destruction of the fd while it
    was still being used.
    
    Change-Id: Ie9e992902cf2cd7be4af1f8b4e57af9bd6afd8e9
    Fixes: bz#1810934
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 2e3e7a2309368376855ffac28620ad56f2c6b7b5
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Feb 21 18:13:57 2020 +0530

    tests: fix afr-lock-heal-* failure
    
    When brick-mux is enabled:
    
    i)brick statedumps seem to be listing the same lock information multiple times.
    While that is getting fixed, make changes to the .ts to check for unique values.
    
    ii)detecting a brick as online via brick_up_status() seems to be taking
    longer time when delaygen is enabled. Hence bump up PROCESS_UP_TIMEOUT to
    90 for afr-lock-heal-advanced.t
    
    Updates: #1042
    Change-Id: Ife76008f7a99dd1f1fe5791a32577366baaab4b3
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit b164a74884becef281b57ef93428bb740e3e342e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 4 18:42:33 2020 +0530

    cluster/afr: Fixes for halo
    
    Current implementation assumes that ping-event will come after connect event
    but that may not be the case in the cases where after socket connection fds
    need to be re-opened which would consume more time. So handle any order of the
    ping/child-up events.
    
    fixes: bz#1800583
    Change-Id: I6bcdc0caa503bdc039ef2b4739fbf4afae121f05
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit eb916c057036db8289b41265797e5dce066d1512
Author: Amar Tumballi <amar@kadalu.io>
Date:   Wed Mar 4 00:46:08 2020 +0530

    utime: resolve an issue of permission denied logs
    
    In case where uid is not set to be 0, there are possible errors
    from acl xlator. So, set `uid = 0;` with pid indicating this is
    set from UTIME activity.
    
    The message "E [MSGID: 148002] [utime.c:146:gf_utime_set_mdata_setxattr_cbk] 0-dev_SNIP_data-utime: dict set of key for set-ctime-mdata failed [Permission denied]" repeated 2 times between [2019-12-19 21:27:55.042634] and [2019-12-19 21:27:55.047887]
    
    Change-Id: Ieadf329835a40a13ac0bf908dac776e66954466c
    Fixes: #832
    Signed-off-by: Amar Tumballi <amar@kadalu.io>

commit 2668e9f1892dbe898e41e3a14701258d78cb8f46
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Mar 10 15:05:08 2020 +0530

    cli: display the error while probing the localhost
    
    With bc6e206c6, we regressed in displaying the error
    message when a user tries to probe localhost. With
    this change, we display "probe on localhost not needed"
    message to the user.
    
    credits: Sachin Prabhu <sprabhu@redhat.com>
    
    fixes: bz#1810042
    
    Change-Id: Ibf82b5a658c371c08290a0b4f655e5ac5f436c06
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 75691851391694d27ad5dcb797df8d4a82fd9e2d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Mar 10 21:06:20 2020 +0530

    glusterd/snapshot: Add a warning message when a volume config changes
    
    While changing a volume configuration, there is a chance that the
    brick layout on the disk might be changed. If snapshot is present
    on such volumes that will effects it's working. So this patch adds
    a warning message if snapshot is present while a volume config change
    happen.
    
    Change-Id: I7256863fef734841fce0bc9ad94d5d201b1813d5
    Fixes: bz#1812144
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 131d24d0c06ca82015256b98695421e09d27304a
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Sun Mar 8 17:27:47 2020 +0200

    dht - selfheal code cleaning
    
    1 - Converted methods to static
    2 - Removed unused code
    
    Change-Id: I49db3e28116da1c3c9ff0a33dcce7281bc3856f7
    updates: bz#1193929
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit f90866a092f0df6e312be25807bf2118e163407d
Author: Arjun Sharma <arjsharm@redhat.com>
Date:   Wed Mar 11 11:37:48 2020 +0530

    Updating create-ganesha-config script:
    
    Adding the Security_Label parameter for labelled nfs
    
    Change-Id: I26d332bc30c767093cfa5d6e63a3b0268fc8a60b
    Fixes: bz#1812353
    Signed-off-by: Arjun Sharma <arjsharm@redhat.com>

commit 6c492274e923df1083b61bd46453e11171761632
Author: l17zhou <cynthia.zhou@nokia-sbell.com>
Date:   Fri Mar 6 03:54:02 2020 +0200

    protocol/client: fallback to anonymous fd for fsync
    
    Change-Id: I32f801206ce7fbd05aa693f44c2f140304f2e275
    Fixes: bz#1810842

commit c12a7d9bdc3887c4ed43f76a3c7886727a62d0bc
Author: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>
Date:   Wed Oct 30 12:42:16 2019 +0530

    Posix: structs re-aligned and manual padding added
    
    All the structs present inside xlators/storage/posix have been re-aligned
    into memory efficient way. Manual padding has been added to remove
    compile time padding. This manual padding is for development and
    debugging benefits. It lets to use -Wpadded option and raise warnings
    from the remaining structs where compile time padding happens.
    
    Change-Id: Ie72c02810803eae29fca435c71aa131a1315b8a8
    Updates: bz#1754448
    Signed-off-by: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>

commit 547fa5bbe5b3438d981de50ac5b2497683a4d9e2
Author: yatipadia <ypadia@redhat.com>
Date:   Tue Dec 31 14:47:03 2019 +0530

    mgmt/glusterd: Adding validation for statedump path
    
    Description of problem:
    server.statedump-path is the path where statedumps are stored,
    by default it is /var/run/gluster. And can be set to any valid
    directory path. It was observed that server.statedump-path was
    also accepting file, non-existent file and non-existent paths
    as well. And statedump command was successful even when
    statedumps with all the invalid paths.
    a. A file
    b. A non-existent path
    
    Solution:
    Added a validation function in gluster-volume-set.c which will
    allow volume set to success if it's a valid directory
    and in all other cases, volume set should fail.
    
    Fixes: bz#1787122
    
    Change-Id: Ia66e2b3d35f23efc5444c829928779a79d827b42
    Signed-off-by: yatipadia <ypadia@redhat.com>
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 3a9254d4ed5452c6da4401abd9626db6345629b7
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Sun Feb 9 15:09:30 2020 +0200

    dht/rebalance - fixing failure occurace due to rebalance stop
    
    Probelm description:
    When topping rebalance, the following error messages appear in the
    rebalance log file:
    [2020-01-28 14:31:42.452070] W [dht-rebalance.c:3447:gf_defrag_process_dir] 0-distrep-dht: Found error from gf_defrag_get_entry
    [2020-01-28 14:31:42.452764] E [MSGID: 109111] [dht-rebalance.c:3971:gf_defrag_fix_layout] 0-distrep-dht: gf_defrag_process_dir failed for directory: /0/1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30/31
    [2020-01-28 14:31:42.453498] E [MSGID: 109016] [dht-rebalance.c:3906:gf_defrag_fix_layout] 0-distrep-dht: Fix layout failed for /0/1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/26/27/28/29/30
    
    In order to avoid seing these error messages, a modification to the
    error handling mechanism has been made.
    In addition, several log messages had been added in order to improve debugging efficiency
    
    fixes: bz#1800956
    Change-Id: Ifc82dae79ab3da9fe22ee25088a2a6b855afcfcf
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit 3e059ec1216535a7866bcb8c3d6dc3cc8047b940
Author: yatipadia <ypadia@redhat.com>
Date:   Wed Dec 11 15:58:46 2019 +0530

    xlator/dht-helper: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: Iab35ac89b7d7fb6fb0074fc61b11bf679c517c9d
    Signed-off-by: yatipadia <ypadia@redhat.com>
    Signed-off-by: yatip <ypadia@redhat.com>

commit 48245df36c5dec40779355a36d7bb7689f9efe6d
Author: yatip <ypadia@redhat.com>
Date:   Mon Feb 3 17:36:00 2020 +0530

    protocol/client: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: I76a09cfd283bb4ec5c4358536da66547aaf0de31
    Signed-off-by: yatip <ypadia@redhat.com>

commit 1291667e26516d02e548207ba3df84c456a36b35
Author: yatip <ypadia@redhat.com>
Date:   Thu Feb 27 18:48:16 2020 +0530

    protocol/server-helpers: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: Ic7b38b646fa0932f7c1562467866137c4567e1f1
    Signed-off-by: yatip <ypadia@redhat.com>

commit f9249c6d79ef654ec2a8e87efc202ce1df642e31
Author: yatip <ypadia@redhat.com>
Date:   Thu Feb 27 14:34:56 2020 +0530

    protocol/server-rpc-fops_v2: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: I01146bcd06bca44faeca29da48fab1ee3fc51e00
    Signed-off-by: yatip <ypadia@redhat.com>

commit 1b0e1cfd7dcede3c4075094b6e14ef9af384a7ec
Author: yatip <ypadia@redhat.com>
Date:   Thu Feb 20 14:14:43 2020 +0530

    protocol/server: structure logging
    
    Convert all gf_msg() to gf_smsg()
    
    Updates: #657
    Change-Id: Ic54b03f05e2766c87f50df0b3a66803b5519fad9
    Signed-off-by: yatip <ypadia@redhat.com>

commit d0ac63e462a71c267436d0bbc8fa638c39b9c69f
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Sun Mar 1 19:49:04 2020 +0100

    cluster/afr: fix race when bricks come up
    
    The was a problem when self-heal was sending lookups at the same time
    that one of the bricks was coming up. In this case there was a chance
    that the number of 'up' bricks changes in the middle of sending the
    requests to subvolumes which caused a discrepancy in the expected
    number of replies and the actual number of sent requests.
    
    This discrepancy caused that AFR continued executing requests before
    all requests were complete. Eventually, the frame of the pending
    request was destroyed when the operation terminated, causing a use-
    after-free issue when the answer was finally received.
    
    In theory the same thing could happen in the reverse way, i.e. AFR
    tries to wait for more replies than sent requests, causing a hang.
    
    Change-Id: I7ed6108554ca379d532efb1a29b2de8085410b70
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
    Fixes: bz#1808875

commit 54250605210b91715b3585e2a677870241364ee5
Author: Amar Tumballi <amar@kadalu.io>
Date:   Tue Feb 4 22:46:38 2020 +0530

    github templates: Change to reflect the future workflow
    
    * Issue template changed to remove reference to bugzilla
    * PR template removed.
    
    CONTRIBUTING made .md friendly (will be renamed once we shift review process)
    
    Updates: #824
    Change-Id: Ifd6f93ad9b7be97d8eb950a141fe585d3e5ed021
    Signed-off-by: Amar Tumballi <amar@kadalu.io>

commit b8d6a9bfb5ac1580f8dca06916db626789606f05
Author: yatipadia <ypadia@redhat.com>
Date:   Wed Dec 11 14:29:50 2019 +0530

    xlator/dht-lock: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Change-Id: If540ca921b1cd8ca75b92b3d72eb9eb61bdaaa10
    Updates: #657
    Signed-off-by: yatip <ypadia@redhat.com>

commit 3ba0885b5be42efec01ebd42cc5fbd33dc1b2756
Author: kinsu <vpolakis@gmail.com>
Date:   Thu Sep 19 08:34:32 2019 +0000

    Segmentation fault occurs during truncate
    
    Problem:
    Segmentation fault occurs when bricks are nearly full 100% and in
    parallel truncate of a file is attempted (No space left on device).
    Prerequicite is that performance xlators are activated
    (read-ahead, write-behind etc)
    while stack unwind of the frames following an error responce
    from brick (No space left on device) frame->local includes a memory
    location that is not allocated via mem_get but via calloc.
    The destroyed frame is always ra_truncate_cbk winded from ra_ftruncate
    and the inode ptr is copied to the frame local in the wb_ftruncate.
    
    Fix:
    extra check is added for the pool ptr
    
    Change-Id: Ic5d3bd0ab7011e40b2811c6dece063b256e4d9d1
    Fixes: bz#1797882
    Signed-off-by: kinsu <vpolakis@gmail.com>

commit a0e08901a87700f967c26f146f54e2301f5d0594
Author: Andreas Loibl <andreas.loibl@check24.de>
Date:   Thu Feb 20 14:05:35 2020 +0100

    mount.glusterfs: don't strip / from subdir-mounts
    
    Change-Id: Ib07c31dc6669aa9d9f84a21e6160237290ed9afb
    Fixes: bz#1804786

commit 45e81aae791da9d013aba2286af44826227c05ec
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Tue Nov 19 11:39:22 2019 +0530

    glusterd: Brick process fails to come up with brickmux on
    
    Issue:
    1- In a cluster of 3 Nodes N1, N2, N3. Create 3 volumes vol1,
    vol2, vol3 with 3 bricks (one from each node)
    2- Set cluster.brick-multiplex on
    3- Start all 3 volumes
    4- Check if all bricks on a node are running on same port
    5- Kill N1
    6- Set performance.readdir-ahead for volumes vol1, vol2, vol3
    7- Bring N1 up and check volume status
    8- All bricks processes not running on N1.
    
    Root Cause -
    Since, There is a diff in volfile versions in N1 as compared
    to N2 and N3 therefore glusterd_import_friend_volume() is called.
    glusterd_import_friend_volume() copies the new_volinfo and deletes
    old_volinfo and then calls glusterd_start_bricks().
    glusterd_start_bricks() looks for the volfiles and sends an rpc
    request to glusterfs_handle_attach(). Now, since the volinfo
    has been deleted by glusterd_delete_stale_volume()
    from priv->volumes list before glusterd_start_bricks() and
    glusterd_create_volfiles_and_notify_services() and
    glusterd_list_add_order is called after glusterd_start_bricks(),
    therefore the attach RPC req gets an empty volfile path
    and that causes the brick to crash.
    
    Fix- Call glusterd_list_add_order() and
    glusterd_create_volfiles_and_notify_services before
    glusterd_start_bricks() cal is made in glusterd_import_friend_volume
    
    Change-Id: Idfe0e8710f7eb77ca3ddfa1cabeb45b2987f41aa
    Fixes: bz#1773856
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 672a53d3d30d6932e25d81f64c7fecbdb97d15c4
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Feb 19 12:24:15 2020 +0100

    core: Prevent crash on process termination
    
    A previous patch (ce61da816a) has fixed a use-after-free issue,
    but it doesn't work well when the final cleanup is done at process
    termination because gluster doesn't stop other threads before
    calling exit().
    
    For this reason, the final cleanup is removed to avoid the crash,
    at least until the termination sequence properly stops all gluster
    threads before exiting the program.
    
    Change-Id: Id7cfb4407fcf208e28f03a7c3cdc3ef9c1f3bf9b
    Fixes: bz#1801684
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit b1a18ef5d0ad7317f4c22cd9c765c63634100906
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Feb 12 12:47:57 2020 -0500

    ganesha-ha: updates for pcs-0.10.x (i.e. in Fedora-29 and RHEL-8)
    
    pcs-0.10 has introduced changes options to pcs commands
    
    pcs-0.10.x is in Fedora-29 and later and RHEL-8.
    
    Also some minor cleanup. Namely use bash built-in [[...]] in a few
    more places instead of test(1), i.e. [...], and use correct "==" for
    comparison.
    
    Change-Id: I3fb2fcd71406964c77fdc4f18580ca133f365fd6
    Fixes: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit ee415f38f71bad62368333184fab3b70be524b78
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Feb 7 10:19:57 2020 +0100

    core: fix memory pool management races
    
    Objects allocated from a per-thread memory pool keep a reference to it
    to be able to return the object to the pool when not used anymore. The
    object holding this reference can have a long life cycle that could
    survive a glfs_fini() call.
    
    This means that it's unsafe to destroy memory pools from glfs_fini().
    
    Another side effect of destroying memory pools from glfs_fini() is that
    the TLS variable that points to one of those pools cannot be reset for
    all alive threads.  This means that any attempt to allocate memory from
    those threads will access already free'd memory, which is very
    dangerous.
    
    To fix these issues, mem_pools_fini() doesn't destroy pool lists
    anymore. Only at process termination the pools are destroyed.
    
    Change-Id: Ib189a5510ab6bdac78983c6c65a022e9634b0965
    Fixes: bz#1801684
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit f389b960d4d337e448808728bfaf2aa168cebdac
Author: Rishubh Jain <risjain@redhat.com>
Date:   Sun Aug 18 18:02:57 2019 +0530

    Updating gluster manual.
    
    Adding disperse-data to gluster manual under
    volume create command
    
    Change-Id: Ic9eb47c9e71a1d7a11af9394c615c8e90f8d1d69
    Fixes: bz#1668239
    Signed-off-by: Rishubh Jain <risjain@redhat.com>
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 06453d77d056fbaa393a137ca277a20e38d2f67e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Feb 11 14:34:48 2020 +0530

    afr: prevent spurious entry heals leading to gfid split-brain
    
    Problem:
    In a hyperconverged setup with granular-entry-heal enabled, if a file is
    recreated while one of the bricks is down, and an index heal is triggered
    (with the brick still down), entry-self heal was doing a spurious heal
    with just the 2 good bricks. It was doing a post-op leading to removal
    of the filename from .glusterfs/indices/entry-changes as well as
    erroneous setting of afr xattrs on the parent. When the brick came up,
    the xattrs were cleared, resulting in the renamed file not getting
    healed and leading to gfid split-brain and EIO on the mount.
    
    Fix:
    Proceed with entry heal only when shd can connect to all bricks of the replica,
    just like in data and metadata heal.
    
    fixes: bz#1801624
    Change-Id: I916ae26ad1fabf259bc6362da52d433b7223b17e
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit a7fa54ddea3fe429f143b37e4de06a93b49d776a
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Jan 3 16:54:33 2020 +0530

    cluster/thin-arbiter: Wait for TA connection before ta-file lookup
    
    Problem:
    When we mount a ta volume, as soon as 2 data bricks are connected
    we consider that the mount is done and then send a lookup/create on
    ta file on ta node. However, this connection with ta node might not
    have been completed.
    Due to this delay, ta replica id file will not be created and we
    will see ENOTCONN error in log file if we do lookup.
    
    Solution:
    As we know that this ta node could have a higher latency, we should
    wait for reasonable time for connection to happen before sending
    lookup/create on replica id file.
    
    fixes: bz#1720463
    Change-Id: I36f90865afe617e4e84cee57fec832a16f5dd6cc

commit acbba8e1121205f9512833d1b0fad81b0930f881
Author: yatipadia <ypadia@redhat.com>
Date:   Tue Nov 19 18:59:28 2019 +0530

    libglusterfs-xlator: structure logging
    
    convert all gf_msg() to gf_smsg()
    
    Change-Id: Id542e05faadb8041b472a2298c71fe62730e65fc
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit c048df835e94a8707254d32db93c42f43f31abda
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Wed Dec 18 19:18:40 2019 +0200

    dht - Reducing methods scope
    
    1. Reduced methods scope in the following:
    inode read&write, layout, linkfile, shard
    2. Removed dead code @ dht-linkkile.c:174-228 & dht-shard.c:44
    
    Change-Id: I2d08a10c7b074fccdb0c020845cad60c6ea32db5
    updates: bz#1193929
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit a3c8a6180a53fb96cc090c5552c64088f68ec4dc
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Mar 13 13:00:47 2019 +0530

    cluster/afr: Check for lock on source & sink before doing data heal
    
    Problem:
    In function afr_selfheal_data_block(), we only check for the lock count
    to be equal to or greater than the number of sinks. There can be a case
    where we have 2 source bricks and one sink and the locking is successful
    on only the source brick(s). In this case we continue with the healing
    on sink without having a lock, which is not correct.
    
    Fix:
    Check for lock on atleast source & one sink before starting the data heal.
    
    Change-Id: Iebcb57dcaa4b31831fedfee63d6ca16e9d6c8df8
    fixes: bz#1688115
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 8db8202f716fd24c8c52f8ee5f66e169310dc9b1
Author: Amar Tumballi <amar@kadalu.io>
Date:   Tue Feb 4 23:02:51 2020 +0530

    volgen: make thin-arbiter name unique in 'pending-xattr' option
    
    Thin-arbiter module makes use of 'pending-xattr' name for the translator
    as the filename which gets created in thin-arbiter node. By making this
    unique, we can host single thin-arbiter node for multiple clusters.
    
    Updates: #763
    Change-Id: Ib3c732e7e04e6dba229e71ae3e64f1f3cb6d794d
    Signed-off-by: Amar Tumballi <amar@kadalu.io>

commit d27df94016b5526c18ee964d4a47508326329dda
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 11 15:42:05 2020 +0530

    tests: Fix spurious self-heald.t failure
    
    Problem:
    heal-info code assumes that all indices in xattrop directory
    definitely need heal. There is one corner case.
    The very first xattrop on the file will lead to adding the
    gfid to 'xattrop' index in fop path and in _cbk path it is
    removed because the fop is zero-xattr xattrop in success case.
    These gfids could be read by heal-info and shown as needing heal.
    
    Fix:
    Check the pending flag to see if the file definitely needs or
    not instead of which index is being crawled at the moment.
    
    fixes: bz#1801623
    Change-Id: I79f00dc7366fedbbb25ec4bec838dba3b34c7ad5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 6de80bcd6366778ac34ce58ec496fa08cc02bd0b
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Sat Sep 29 13:15:35 2018 +0530

    feature/changelog: Avoid thread creation if xlator is not enabled
    
    Problem:
    Changelog creates threads even if the changelog is not enabled
    
    Background:
    Changelog xlator broadly does two things
      1. Journalling - Cosumers are geo-rep and glusterfind
      2. Event Notification for registered events like (open, release etc) -
         Consumers are bitrot, geo-rep
    
    The existing option "changelog.changelog" controls journalling and
    there is no option to control event notification and is enabled by
    default. So when bitrot/geo-rep is not enabled on the volume, threads
    and resources(rpc and rbuf) related to event notifications consumes
    resources and cpu cycle which is unnecessary.
    
    Solution:
    The solution is to have two different options as below.
     1. changelog-notification : Event notifications
     2. changelog : Journalling
    
    This patch introduces the option "changelog-notification" which is
    not exposed to user. When either bitrot or changelog (journalling)
    is enabled, it internally enbales 'changelog-notification'. But
    once the 'changelog-notification' is enabled, it will not be disabled
    for the life time of the brick process even after bitrot and changelog
    is disabled. As of now, rpc resource cleanup has lot of races and is
    difficult to cleanup cleanly. If allowed, it leads to memory leaks
    and crashes on enable/disable of bitrot or changelog (journal) in a
    loop. Hence to be safer, the event notification is not disabled within
    lifetime of process once enabled.
    
    Change-Id: Ifd00286e0966049e8eb9f21567fe407cf11bb02a
    Updates: #475
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit f1e62e1578ee07802827121722d90c1ec4b811a6
Author: yatipadia <ypadia@redhat.com>
Date:   Sat Nov 23 14:03:41 2019 +0530

    libglusterfs-options: structure logging
    
    convert all gf_msg() to gf_smsg()
    
    Change-Id: I8f1ff462b9c8012ed676c51450930a65ac403bf3
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit c87817495b3c5c36dcca9d157e9313b7d3195eed
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Dec 27 12:06:19 2019 +0530

    dht: Fix stale-layout and create issue
    
    Problem: With lookup-optimize set to on by default, a client with
    stale-layout can create a new file on a wrong subvol. This will lead to
    possible duplicate files if two different clients attempt to create the
    same file with two different layouts.
    
    Solution: Send in-memory layout to be cross checked at posix before
    commiting a "create". In case of a mismatch, sync the client layout with
    that of the server and attempt the create fop one more time.
    
    test: Manual, testcase(attached)
    
    fixes: bz#1786679
    Change-Id: Ife0941f105113f1c572f4363cbcee65e0dd9bd6a
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 8fad76650bd85463708f59d2518f5b764ae4c702
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Feb 3 18:10:17 2020 +0530

    bitrot: Make number of signer threads configurable
    
    The number of signing process threads (glfs_brpobj)
    is set to 4 by default. The recommendation is to set
    it to number of cores available. This patch makes it
    configurable as follows
    
    gluster vol bitrot <volname> signer-threads <count>
    
    fixes: bz#1797869
    Change-Id: Ia883b3e5e34e0bc8d095243508d320c9c9c58adc
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 2dbbdc92be205d12901ce2770570bbcb17040838
Author: yatipadia <ypadia@redhat.com>
Date:   Fri Nov 22 19:00:00 2019 +0530

    libglusterfs-event-epoll: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Change-Id: Idf5bfc826b0c9f1a2674eea2a2e6164f30806b00
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit 228d27d7bd731aa37a26fe637ebcde4322463bb5
Author: yatipadia <ypadia@redhat.com>
Date:   Tue Nov 5 21:44:54 2019 +0530

    glusterfsd: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Change-Id: I1cd6a5ac6f4361195d5d925efb2cc194045d0bba
    Updates: #657
    Signed-off-by: yatip <ypadia@redhat.com>

commit 5864b450b62da45487050b4cd8215343f9b73606
Author: yatip <ypadia@redhat.com>
Date:   Thu Jan 30 18:59:54 2020 +0530

    protocol/client-rpc-fops: structure logging
    
    convert all gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: Ia9d4fb17579af6586bc13d69ec7990c6cf220aac
    Signed-off-by: yatip <ypadia@redhat.com>

commit f121b156cca43148595229e07a9c5a5a4561627c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 1 15:44:15 2019 +0530

    configure: add an option to build with tcmalloc library
    
    With this patch, one can now use '--enable-tcmalloc' while running
    configure, and they can see that their glusterfs is linked with
    libtcmalloc.
    
    [atumball@local build]$ ldd /usr/local/sbin/glusterfs | grep tcmalloc
    	libtcmalloc.so.4 => /lib64/libtcmalloc.so.4 (0x00007feec0b87000)
    
    Once we establish a standard performance number with and without this option,
    we will see how to make it default.
    
    Updates: #237
    Change-Id: I3377f57bfe4e17f101a212e1914a6d3c1687d528
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 4e9fc11b0659957e76565f6557ad1079c51d6832
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 4 14:43:35 2020 +0530

    protocol/client: Maintain connection to brick status
    
    Problem:
    The current version of the code depends on the non-zero-port information to
    propagate ping event from brick to parent layers. But as and when connection
    succeeds, port is set to zero in rpc layer.So ping event is never propagated to
    parent layers. Halo doesn't work without this.
    
    Fix:
    Remember the status of connection in 'private' structure and use that to decide
    to propagate ping event to parent xlator.
    
    fixes: bz#1797934
    Change-Id: Ia578ba9fb3813953d2068dbba5c982ab27cc3429
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 2b35572e1f30c37bbbbec8f63060ae2eeaf61b32
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jan 21 10:16:29 2020 +0200

    dht-hashfn.c: ensure we do not try to calculate hash on NULL path
    
    For some reason, dht_selfheal_layout_alloc_start() sends a NULL
    loc->path string to dht_hash_compute().
    Until we understand why it happens, we should strive not to crash
    on a strlen of a NULL pointer.
    
    Change-Id: I8c2a22602cfccba9af85f432a1841556f6978450
    updates: bz#1793378
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c4b5cfbfa82de0aa16e9557f5b3fcf3dc186c740
Author: yatipadia <ypadia@redhat.com>
Date:   Tue Dec 10 17:10:44 2019 +0530

    xlator/dht-selfheal: structure logging
    
    Convert gf_msg() to gf_smsg()
    
    Change-Id: Ic72f2513e641cfcbe074933cb2697ee9fc05a766
    Updates: #657
    Signed-off-by: yatip <ypadia@redhat.com>

commit ec2c7ddd6739afacc871a5df4c348b4c58cf153e
Author: yatipadia <ypadia@redhat.com>
Date:   Wed Dec 11 19:54:45 2019 +0530

    xlator/bit-rot: structure logging
    
    convert all gf_msg() to gf_smsg()
    
    Change-Id: Ifa45b5089f83ddfcf69132bb8d9c0dc6d012464b
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit ff69d2d52b88d87c6fba923ec9241f78528cee12
Author: yatip <ypadia@redhat.com>
Date:   Fri Jan 17 15:00:12 2020 +0530

    xlator/snapview: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: I2dd09a205c11d1c05abc7106e67802d2aa3bca79
    Signed-off-by: yatip <ypadia@redhat.com>

commit c0dce4603cb5dadc91245697f233736c41faec81
Author: yatipadia <ypadia@redhat.com>
Date:   Sun Nov 17 12:35:20 2019 +0530

    libglusterfs/common-utils: structure logging
    
    changes all the gf_msg() to gf_smgs()
    
    Change-Id: I3524bbd8f8070df2f2c888ea9b0fb7db1ee44453
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit 21684787fff47b25abf1ea06283bb4844114d429
Author: yatip <ypadia@redhat.com>
Date:   Thu Jan 16 12:54:43 2020 +0530

    xlator/dht-linkfile: structure logging
    
    convert all gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: I9104ba8a8102f04d031a208abb06b6cf8ea8fd13
    Signed-off-by: yatip <ypadia@redhat.com>

commit 180302d33aab1522dbe8903f3b12c4ca95e474f4
Author: yatip <ypadia@redhat.com>
Date:   Wed Jan 29 18:02:05 2020 +0530

    protocol/client: structure logging
    
    convert all gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: I69b228d7c7a8bc6263f9bd33710e880678d8c017
    Signed-off-by: yatip <ypadia@redhat.com>

commit 6df9dbf2edd7958981aa8bf9f0f8b3a9750bc635
Author: yatip <ypadia@redhat.com>
Date:   Fri Jan 24 20:58:06 2020 +0530

    protocol/client-handshake: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: Iee07228cfc3a9a9cd10e89ae9eb918681b072585
    Signed-off-by: yatip <ypadia@redhat.com>

commit 8b006854a58ea751f450f89de2b28b323c2c5c90
Author: yatip <ypadia@redhat.com>
Date:   Fri Jan 24 19:01:15 2020 +0530

    protocol/client-rpc-fops_v2: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: Ib45f121f583c2af09bfddb23391f73a117e63213
    Signed-off-by: yatip <ypadia@redhat.com>

commit a144cd20745a03f025920ab81265e150e11b3a0a
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Sun Dec 22 22:52:30 2019 +0530

    ec: change error message for heal commands for disperse volume
    
    Currently when we issue a heal statistics or similar commands
    for disperse volume, it fails with message "Volume is not of
    type replicate." Adding message "this command is supported for
    volumes of type replicate" to reflect supportability and better
    understanding of heal functionality for disperse volumes.
    
    fixes: bz#1785998
    Change-Id: I9688a9fdf427cb6f657cfd5b8db2f76a6c56f6e2
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 34347876bb525e1af19bccafbb753a14b358d3aa
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Jan 31 15:27:46 2020 +0000

    libgfapi: fix resource leak
    
    This patch fixes resource leak in glfs-fops.c.
    CID : 1403873 : Resource leak
    
    updates: bz#789278
    
    Change-Id: I589d4d65d2b074801f7b4b0afd7dc4607d79420e
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit c1c2afd920ab6135ffcd0e1ecb25e71449037c9e
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Dec 4 17:06:18 2019 +0530

    Improve logging in EC, client and lock translator
    
    Change-Id: I98af8672a25ff9fd9dba91a2e1384719f9155255
    Fixes: bz#1779760

commit 06eb3d0b8488d12a92ea21b92727497c585bae4b
Author: Harpreet Kaur <hlalwani@redhat.com>
Date:   Mon Jan 7 16:38:25 2019 +0530

    geo-rep: Fix for "Transport End Point not connected" issue
    
    problem: Geo-rep gsyncd process mounts the master and slave volume
             on master nodes and slave nodes respectively and starts
             the sync. But it doesn't wait for the mount to be in ready
             state to accept I/O. The gluster mount is considered to be
             ready when all the distribute sub-volumes is up. If the all
             the distribute subvolumes are not up, it can cause ENOTCONN
             error, when lookup on file comes and file is on the subvol
             that is down.
    
    solution: Added a Virtual Xattr "dht.subvol.status" which returns "1"
              if all subvols are up and "0" if all subvols are not up.
              Geo-rep then uses this virtual xattr after a fresh mount, to
              check whether all subvols are up or not and then starts the
              I/O.
    
    fixes: bz#1664335
    Change-Id: If3ad01d728b1372da7c08ccbe75a45bdc1ab2a91
    Signed-off-by: Harpreet Kaur <hlalwani@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 12bea344e4cc4fe2101aa7efb8a97606d69aa80f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jan 22 14:37:04 2020 -0500

    build: glusterfs-ganesha pkg requires python3-policycoreutils on rhel8
    
    glusterfs-ganesha pkg requires policycoreutils-python-utils on rhel8,
    not policycoreutils-python
    
    Also needs nfs-ganesha-selinux on recent fedora and rhel/centos 8
    
    Change-Id: Ia97b4dabdc098fb76e3f60e8b48ea4191e677136
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 7cac693bba33cbba35a6d0bbe98d8ad5551d2134
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Thu Nov 14 09:24:26 2019 +0530

    tests: fix test failures for nfsnobody user and group
    
    'nfsnobody' user and group is merged with
    'nobody' user and group in RHEL8.
    
    Tests are modified to use appropriate user and group.
    
    BUG: 1756900
    Change-Id: I59863da2262283b00b1cb417d3652ebe29a36407
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit 7dc4122b84c93cfa6355002fa651a806706e4990
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Thu Jan 2 12:05:12 2020 +0530

    afr: restore timestamp of files during metadata heal
    
    For files: During metadata heal, we restore timestamps
    only for non-regular (char, block etc.) files.
    Extenting it for regular files as timestamp is updated
    via touch command also
    
    fixes: bz#1787274
    Change-Id: I26fe4fb6dff679422ba4698a7f828bf62ca7ca18
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 22b8564e781d2113327a0dc17dd4414a6386f2e1
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Sun Jan 19 17:54:51 2020 +0800

    snapview: fix memory leak
    
    Setting frame->local = local immediately after mem_get0.
    In this case, SVC_STACK_UNWIND will take of freeing the memory.
    
    Change-Id: If6433be0e14ed0f4ab4127f70a8875f81bb3e6b8
    updates: bz#789278
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit 92bf7634d67a574dba6d7e77501d605d7f33acc3
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jan 14 17:11:15 2020 +0200

    server.c: fix Coverity issue 1405844 (memory - illegal access)
    
    We can use memcpy() instead of strncpy() as both are strings that are
    37 bytes (GF_UUID_BUF_SIZE) long.
    
    fixes: CID#1405844
    Change-Id: Ic74e8817cd790c13e29f3e6be8f18f2bfff77115
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit be673d9d093d977f4f38f2dba3f422c796db37b7
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Jan 22 15:50:27 2020 +0200

    multiple files: ensure nfs_svc functions are available
    
    When gNFS is disabled in build time, we have to ensure
    taht the .stop(), .start() and other functions of the nfs_svc
    are not called, otherwise we'd crash.
    In addition, #ifdef more code that is gNFS related.
    
    updates: bz#1793995
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I5081f1670c04ca306aeaab7208829b0f2f149a42

commit f6421dff22a6ddaf14134f6894deae219948c89d
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Jan 21 21:09:56 2020 +0530

    server: Mount fails after reboot 1/3 gluster nodes
    
    Problem: At the time of coming up one server node(1x3) after reboot
    client is unmounted.The client is unmounted because a client
    is getting AUTH_FAILED event and client call fini for the graph.The
    client is getting AUTH_FAILED because brick is not attached with a
    graph at that moment
    
    Solution: To avoid the unmounting the client graph throw ENOENT error
              from server in case if brick is not attached with server at
              the time of authenticate clients.
    
    Credits: Xavi Hernandez <xhernandez@redhat.com>
    Change-Id: Ie6fbd73cbcf23a35d8db8841b3b6036e87682f5e
    Fixes: bz#1793852
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit d8e685a96170a433dde93a6bc6fb8c07babb01a5
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Oct 21 20:56:23 2019 +0300

    posix-entry-ops.c/posix.h: improve GFID_NULL_CHECK_AND_GOTO macro
    
    The macro already fetches from the dictionary the gfid-req variable.
    Instead of throwing it away, keep it and in 2 cases,
    re-use it later.
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Id6d42535132805ab69e7e3b802c140b90f2f8958

commit 18549de12bcfafe4ac30fc2e11ad7a3f3c216b38
Author: Xi Jinyu <xijinyu@cmss.chinamobile.com>
Date:   Tue Jan 14 22:29:06 2020 -0500

    Fix possible resource leaks.
    
    xlators/features/quota/src/quota.c quota_log_usage function.
    The quota_log_helper() function applies memory
    for path through inode_path(), should be GF_FREE().
    
    fixes: bz#1792707
    Change-Id: I33143bdf272bf10837061df4a1b7b2fc146162d5
    Signed-off-by: Xi Jinyu <xijinyu@cmss.chinamobile.com>

commit 61737898e84d30e02117baa7431f89cafff27f56
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Wed Dec 4 18:48:23 2019 +0200

    cli - removing fetch of unnecessary items.
    
    Somem methods dict_get...(...) values and then not use them anywhere.
    Removed found occurrences.
    
    fixes: #753
    
    Change-Id: Iaeb8f4cec18f76078f6b2f4e4bd6f9795a3467bc
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit 44602465081ea5fb38255ad68d3ed8e987190d1f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Jan 12 16:33:54 2020 +0200

    dictionary: remove the 'extra_free' parameter
    
    This parameter may have been used in the past, but is no longer
    needed. Removing it and the few locations it was actually referenced.
    This allows to remove an extra memdup as well, that was not needed
    in the 1st place in server_setvolume() and unserialize_rsp_direntp()
    functions.
    
    A followup separate patch will remove extra_stdfree parmeter
    from the dictionary structure.
    
    Change-Id: Ica0ff0a330672373aaa60e808b7e76ec489a0fe3
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 3aa0928623393aa9c296abf32d4726d02a454207
Author: Amar Tumballi <amar@kadalu.io>
Date:   Mon Jan 13 13:07:47 2020 +0530

    pkg-version: fix warning due to wrong check.
    
    using '==' operator is bash specific, and was giving
    warnings like below when we ran `./autogen.sh`
    
    ```
    build-aux/pkg-version: 26: [: x8dev: unexpected operator
    build-aux/pkg-version: 49: [: x384.git22c2725bb: unexpected operator
    ```
    
    This was not seen where 'sh' is linked to 'bash'.
    
    Updates: bz#1193929
    Change-Id: Ied0d6707dd8b5d78756f302b6319b6ef75143018
    Signed-off-by: Amar Tumballi <amar@kadalu.io>

commit 3043fc54b0bdcf87fce13dcd9c56d0dd30e1c5b2
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Thu Jan 16 10:00:41 2020 +0800

    glusterd: fix use after free
    
    updates: bz#789278
    Change-Id: I652d8d4428cf6ce61b712a66d309e78030a5f911
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit c7b546326092d060bf84b7c578a4f21bc679674a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jan 14 16:55:32 2020 +0200

    name.c: fix Coverity issues 1412332/3 - strcat into uninitialized value
    
    Check limit to 108 bytes before strcpy().
    
    fixes: CID#1412332
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I8b26b1e1d2daca98ff36db531539bec0a405769c

commit 485212e858bddd97573a3b2b811357b0d822005a
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Jan 17 11:03:46 2020 +0000

    geo-rep: Fix ssh-port validation
    
    If non-standard ssh-port is used, Geo-rep can be configured to use ssh port
    by using config option, the value should be in allowed port range and non negative.
    
    At present it can accept negative value and outside allowed port range which is incorrect.
    
    Many Linux kernels use the port range 32768 to 61000.
    IANA suggests it should be in the range 1 to 2^16 - 1, so keeping the same.
    
    $ gluster volume geo-replication master 127.0.0.1::slave config ssh-port -22
    geo-replication config updated successfully
    $ gluster volume geo-replication master 127.0.0.1::slave config ssh-port 22222222
    geo-replication config updated successfully
    
    This patch fixes the above issue and have added few validations around this
    in test cases.
    
    Change-Id: I9875ab3f00d7257370fbac6f5ed4356d2fed3f3c
    Fixes: bz#1792276
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 6c48f1649d0916ae237fec08f007c8efb6d53e4e
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue Jan 14 13:28:47 2020 +0100

    events: fix IPv6 memory corruption
    
    When an event was generated and the target host was resolved to an IPv6
    address, there was a memory overflow when that address was copied to a
    fixed IPv4 structure (IPv6 addresses are longer than IPv4 ones).
    
    This fix correctly handles IPv4 and IPv6 addresses returned by
    getaddrinfo()
    
    Change-Id: I5864a0c6e6f1b405bd85988529570140cf23b250
    Fixes: bz#1790870
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 71231a6a009ea34ea80da9b36d761f3764043de5
Author: Michael Scherer <misc@fedoraproject.org>
Date:   Thu Jan 16 11:21:09 2020 +0100

    Be explicit on this being a python3 script
    
    While the script seems to work on both python3 and python2, this
    break the build of rawhide RPM who requires script to be either
    using python2 or python3.
    
    Since python2 is going to be deprecated, I guess we should aim for
    python3.
    
    Change-Id: Ic6322ad47772d708b60b96652a1122ee4a54141d
    Fixes: bz#1791682
    Signed-off-by: Michael Scherer <misc@fedoraproject.org>

commit 43d58660772da0b8f25fb89ece19851391bf999f
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Dec 10 11:43:30 2019 +0530

    protocol/client: Fix a log entry
    
    It has been a while since we removed lock healing logic from protocol
    client. So no need to mention that we healed locks after fd reopen.
    
    Change-Id: I24bd3f9e9f2942e306714b2cb83c229ae57c60ae
    Fixes: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit d5fef2a50cf4e3458e800d59021a97c0b5fc39db
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Dec 9 23:17:16 2019 +0200

    dht-hashfn.c: remove a strlen()
    
    We already have the length of the name, or when we munge it,
    we can return the length of it instead of strlen() again.
    
    Also, reduce a bit the code under the lock.
    
    Change-Id: I0141b0725ed1a4134d8d9f81ed1187b551b038b5
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 9969d1dc2a3e815b161ce8a3dc5d08f84cfe011f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Dec 9 21:28:00 2019 +0200

    multiple xlators: reduce key length
    
    In many cases, we were freely allocating long keys with no need.
    Smaller char arrays are just fine almost anywhere, so just went ahead
    and looked where they we can use smaller ones.
    
    In some cases, annotated the functions as static and the prefixes
    passed as const as it was easier to read and understand.
    
    Where relevant, converted the dict functions to use known key length.
    
    Change-Id: I882ab33ea20d90b63278336cd1370c09ffdab7f2
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit dc5b2d3c181020da1644106e5b17f77a4f3e53df
Author: yatipadia <ypadia@redhat.com>
Date:   Wed Dec 4 12:09:12 2019 +0530

    xlator/changelog: structure logging
    
    convert all gf_msg() to gf_smsg()
    
    Change-Id: I2303aeaa0775b663e2ea5741166a457cd747d2ac
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>
    Signed-off-by: yatip <ypadia@redhat.com>

commit 830a3dc46438b1cf18bcd35cca05c164e77180f1
Author: yatipadia <ypadia@redhat.com>
Date:   Mon Nov 25 19:57:09 2019 +0530

    api-glfs-fops: structure logging
    
    Convert gf_msg() to gf_smsg()
    
    Change-Id: Iceb40d60a75106c7b4b0a2487b611f7376bccc46
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit d73872e764214f8071c8915536a75bdac1e5e685
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Tue Jan 14 10:51:06 2020 +0530

    tools/glusterfind: Remove an extra argument
    
    fixes: bz#1790748
    Change-Id: I1cb12c975142794139456d0f8e99fbdbb03c53a1
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 6b5068f3404c072b94e18854aab8e99d3ce54350
Author: yatipadia <ypadia@redhat.com>
Date:   Thu Dec 12 16:17:22 2019 +0530

    xlator/bit-rot-stub-helpers: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Change-Id: Id03b6a2f6817101650ea6eeffb10e91c09e6ef80
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit 8bfcae18c080c856a7218b0df9e403e2cdb59355
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Fri Jan 10 13:44:53 2020 +0300

    xlators/storage: remove duplicated includes
    
    Do not include ftw.h twice.
    
    Change-Id: Id9e8d1813aafd890940adcd6883d90fa1b4beaf9
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
    Updates: bz#1193929

commit 7dcbf096087cb6b939149c6f14ea2c3b2ab861e4
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Thu Jan 9 16:17:57 2020 +0300

    xlators/storage: prefer HAVE_xxx to host C library predefines
    
    Rely on configure-time HAVE_SET_FSID instead of predefined
    linux and __GLIBC__, in the same way as fusermount.c does.
    
    Change-Id: If81f821014bbf3fdc43950670e316b4d178b4cac
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
    Updates: bz#1193929

commit a73baf4e50fd8468f726179d89ba90364c5b8329
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Oct 23 22:38:59 2019 +0300

    dict: use the free_pair's key presence or NULL as a sign of use.
    
    Instead of using a boolean parameter, we can use the key variable.
    If it's NULL, the pair is not used and can be used.
    Otherwise, it's in use - don't use.
    
    It saves this annoying boolean, which causes the compiler
    (or us explicitly) to pad with additional bytes the dict struct.
    
    Change-Id: I89f52db57f35b3ef8acf57b7de2cee37f5d18e06
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 905db496aa622e421d807222dcc488488da9dbfe
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Dec 31 09:11:08 2019 +0200

    socket.c/name.c: minor changes
    
    - Move functions to static
    - Remove redundant checks
    - Use dict_get_...sizen() where applicable
    - Remove unused variables.
    - Moved some code to be executed only if relevant.
    
    ~3% object size reduction.
    
    Change-Id: Id9b8414e0a17442f1dac10ba77014d565756c935
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c73adc852a6f94844bab9cf541838934dd8d45d4
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Dec 31 15:11:42 2019 +0200

    rpc-transport: minor changes
    
    - Removed dead code
    - Remove redundant checks
    - Changed dict functions to use dict_..._sizen() functions.
    
    Change-Id: If00aaa90eef4078effd5b7fed2294f872e001b0a
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 9189ed3201f1da89f16595d685b67a71e075d5be
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Jan 10 08:24:35 2020 +0200

    glusterd-volgen.c: fix to disable property when gNFS disabled.
    
    The code was not ifdef'ed properly when gNFS was not enabled.
    Strangely, I could not reproduce the failure on my system (Fedora 31),
    but it was reproduced elsehwere and the fix was verified to correct it.
    The failure:
    gluster volume create testvol replica 3 127.0.0.2:/tests/brick{1..3} force
    gluster v set testvol write-behind off
    grep -rne write-behind /var/lib/glusterd/vols/testvol/trusted-testvol.tcp-fuse.vol
    
    The last grep was supposed to come out empty.
    
    The issue was that perfxl_option_handler may not have been called when it should
    have been.
    
    Change-Id: Ie9f8ec87dabeef6624527c2266ddf9af01ca7373
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 33c3cbe71b67f523538b04334f1ef962953281ed
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Jan 10 14:28:35 2020 +0000

    glusterfind: python3 compatibility
    
    Problem:
    While we delete gluster volume the hook script 'S57glusterfind-delete-post.py'
    is failed to execute and error message can be observed in glusterd log.
    
    Traceback:
      File "/var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post", line 69, in <module>
        main()
      File "/var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post", line 39, in main
        glusterfind_dir = os.path.join(get_glusterd_workdir(), "glusterfind")
      File "/usr/lib64/python3.7/posixpath.py", line 94, in join
        genericpath._check_arg_types('join', a, *p)
      File "/usr/lib64/python3.7/genericpath.py", line 155, in _check_arg_types
        raise TypeError("Can't mix strings and bytes in path components") from None
    TypeError: Can't mix strings and bytes in path components
    
    Solution:
    
    Added the 'universal_newlines' flag to Popen to support backward compatibility.
    
    Change-Id: Ie5655b11b55535c5ad2338108d0448e6fdaacf4f
    Fixes: bz#1789478
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 45894c39a4d05ed1f6a6f1bdbeafb5fe74ef29c3
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Jan 10 16:48:14 2020 +0530

    glusterfind: Fix py2/py3 issues
    
    1. In dictionary values(), returns list in py2 and not in py3.
       So explicitly convert it into list.
    2. xattr module returns values in bytes. So explicitly convert
       them to str to work both with py2 and py3
    
    fixes: bz#1789439
    Change-Id: I27a639cda4f7a4ece9744a97c3d16e247906bd94
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 497d9f7d51443f4f463ca00f4fdddc42c6464e0f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jan 7 12:57:29 2020 +0200

    dht-rename.c: fix Coverity issues 1397018/7 - strcat into uninitialized value
    
    initialize both src and dst if they were not initialized already.
    
    fixes: CID#1397018
    Change-Id: Ic91954423953e8bf24eaa11fc2798c554f304d28
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 00c090b093c147a95bfb8fce93f08303993e1995
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Dec 20 14:14:32 2019 +0100

    multiple: fix bad type cast
    
    When using inode_ctx_get() or inode_ctx_set(), a 'uint64_t *' is expected.
    In many cases, the value to retrieve or store is a pointer, which will be
    of smaller size in some architectures (for example 32-bits). In this case,
    directly passing the address of the pointer casted to an 'uint64_t *' is
    wrong and can cause memory corruption.
    
    Change-Id: Iae616da9dda528df6743fa2f65ae5cff5ad23258
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
    Fixes: bz#1785611

commit 1166df1920dd9b2bd5fce53ab49d27117db40238
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jan 7 19:43:05 2020 +0100

    fuse: degrade logging of write failure to fuse device
    
    Problem:
    
    FUSE uses failures of communicating with /dev/fuse with various
    errnos to indicate in-kernel conditions to userspace. Some of these
    shouldn't be handled as an application error. Also the standard
    POSIX errno description should not be shown as they are misleading
    in this context.
    
    Solution:
    
    When writing to the fuse device, the caller of the respective
    convenience routine can mask those errnos which don't qualify to
    be an error for the application in that context, so then those
    shall be reported at DEBUG level.
    
    The possible non-standard errnos are reported with their
    POSIX name instead of their description to avoid confusion.
    (Eg. for ENOENT we don't log "no such file or directory",
    we log indeed literal "ENOENT".)
    
    Change-Id: I510158843e4b1d482bdc496c2e97b1860dc1ba93
    updates: bz#1193929
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 8d55951efe744f6da36f5b61c5be5a8bd77dc426
Author: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>
Date:   Fri Oct 25 11:28:00 2019 +0530

    leases: re-alignment of structures
    
    All the structs present inside xlators/features/leases have been
    re-aligned into memory efficient way. Changes are made in such a way
    that every members are 8 byte aligned and no padding is left out in
    the 8 byte line. Manual padding has been added to remove compile time
    padding (which happens at the end of the struct). This manual padding
    is for development and debugging benefits. It lets to use -Wpadded
    option and raise warnings from the remaining structs where compile time
    padding happens.
    
    Change-Id: I083d2de80e24f363c97adadcba64825e213050fc
    Updates: bz#1754448
    Signed-off-by: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>

commit b49f5e217fe958517464a84d0cc4b766d99fc42b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Jan 7 15:32:13 2020 +0530

    glusterd: increase the StartLimitBurst
    
    Based on https://bugzilla.redhat.com/show_bug.cgi?id=1782200#c6
    increasing the limit.
    
    fixes: bz#1782200
    
    Change-Id: Ia885c7bdb2a90f0946c5268da894f6a4da5a69b7
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 144972bbddc4071600a1cc0380a997ada05c013d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jan 3 09:59:29 2020 +0530

    afr: expose cluster.optimistic-change-log to CLI.
    
    This volume option was not made avaialble to `gluster volume set` CLI.
    
    Reported-by: epolakis(https://github.com/kinsu) in
    https://github.com/gluster/glusterfs/issues/781
    
    fixes: bz#1787554
    Change-Id: I7141bdd4e53ee99e22b354edde8d023bfc0b2cd7
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 10b0d19513100c3f7edf00936ea5ec06fc3f80a5
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Sun Jan 5 12:11:07 2020 +0200

    cli - fixing a coverity issue
    
    Removed unused variable.
    
    fixes: CID#1412106
    updates: bz#789278
    
    Change-Id: I1d4e1c1625cecf882d51e9cf4f5290383f63d405
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit 50ca15e14e287f366576f257d715318d2514d7fa
Author: He Min <hemin@cmss.chinamobile.com>
Date:   Thu Jan 2 14:26:22 2020 +0800

    mgmt/glusterd: Correct the log path of valgrind.
    
    Problem: Currently enabling run-with-valgrind will cause the gnfs and quota to
    fail to start. The phenomenon is as follows.
    ------------------------------------------------------------------------------
    NFS Server on localhost                     2049      0          N       48406
    Quota Daemon on localhost                   N/A       N/A        N       48428
    ------------------------------------------------------------------------------
    
    Solution: The cause of the above phenomenon is that the log path of valgrind is
    set incorrectly. Gnfs and quota can start with valgrind normally after correcting
    the log path.
    
    Updates: #788
    Change-Id: Ib91408c08522ff66afff908fbff3fce4b93ea770
    Signed-off-by: He Min <hemin@cmss.chinamobile.com>

commit 26fe6106762f6aea910d477d1c37e645797884e1
Author: yatipadia <ypadia@redhat.com>
Date:   Tue Dec 17 12:55:02 2019 +0530

    xlator/performance/io-threads: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Change-Id: I35c6f62c346a75ecb22cd3a4346ad4dc48f09a91
    Updates: #657

commit 7f98c105a3a8e2a9f4e9c75451a94115e270405e
Author: yatipadia <ypadia@redhat.com>
Date:   Wed Dec 18 17:25:51 2019 +0530

    xlator/io-cache: structure logging
    
    Convert all gf_msg() to gf_smsg()
    
    Updates: #657
    
    Change-Id: I72215b2518df78174dda8a7bc8de6f21fe1ba10f
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit f72e2b00a13709717a6c7e0ff95d4c7a8f58b020
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Dec 1 13:57:28 2019 +0200

    posix-metadata.c: try to getxattr in one call.
    
    Another location where instead of 2 sys calls we strive to get the
    xattr in a single call, by guesstimating the required size
    And avoid (or try to) not to first read the xattr len,
    then another call to actually fetch. Instead, use a sane size
    (256 bytes - worth checking if it makes sense or by default
    use a larger size), and see if we can fetch it.
    If we fail, we'll read the size and re-fetch.
    
    Such changes are needed elsewhere too (see
    https://github.com/gluster/glusterfs/issues/720 )
    
    Change-Id: I466cea9d8b12fc45f6b37d202b1294ca28cd1fdd
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit f66bd85af09397300ad434655fc68861f48c2e3c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jan 2 07:46:23 2020 -0500

    cli: duplicate defns of cli_default_conn_timeout and cli_ten_minutes_timeout
    
    Winter is coming. So is gcc-10.
    
    Compiling with gcc-10-20191219 snapshot reveals dupe defns of
    cli_default_conn_timeout and cli_ten_minutes_timeout in
    .../cli/src/cli.[ch] due to missing extern decl.
    
    There are many changes coming in gcc-10 described in
    https://gcc.gnu.org/gcc-10/changes.html
    
    compiling cli.c with gcc-9 we see:
       ...
            .quad   .LC88
            .comm   cli_ten_minutes_timeout,4,4
            .comm   cli_default_conn_timeout,4,4
            .text
       .Letext0:
       ...
    
    and with gcc-10:
       ...
            .quad   .LC88
            .globl  cli_ten_minutes_timeout
            .bss
            .align 4
            .type   cli_ten_minutes_timeout, @object
            .size   cli_ten_minutes_timeout, 4
       cli_ten_minutes_timeout:
            .zero   4
            .globl  cli_default_conn_timeout
            .align 4
            .type   cli_default_conn_timeout, @object
            .size   cli_default_conn_timeout, 4
       cli_default_conn_timeout:
            .zero   4
            .text
       .Letext0:
       ...
    
    which is reflected in the .o file as (gcc-9):
    ...
    0000000000000004 C cli_ten_minutes_timeout
    0000000000000004 C cli_default_conn_timeout
    ...
    
    and (gcc-10):
    ...
    0000000000000020 B cli_ten_minutes_timeout
    0000000000000024 B cli_default_conn_timeout
    ...
    
    See nm(1) and ld(1) for a description C (common) and B (BSS) and how
    they are treated by the linker.
    
    Note: there is still a small chance that gcc-10 will land in Fedora-32,
    despite 31 Dec. 2019 having been the deadline for that to happen.
    
    Change-Id: I54ea485736a4910254eeb21222ad263721cdef3c
    Fixes: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 063bfe949eb11b33424bd67dd4225bb430ceaae7
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Mon Jan 6 10:11:32 2020 +0800

    lock: fix Coverity CID 1412107
    
    To avoid memory leak.
    
    Change-Id: Ib802be310fe989223afd623d3e5a9c9016d4fd38
    updates: bz#789278
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit f805eb110081783690d29ffe2d80405a9ba6191c
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Tue Dec 24 13:02:21 2019 +0530

    [geo-rep] Improving help message in schedule_georep.py.in
    
    SLAVE positional argument doesn't provide a clear
    picture of what it is when compared to mastervol and slavevol
    in schedule_georep.py.in. It would be better if we change it to
    something like "Slave hostame (<username>@SLAVEHOST or SLAVEHOST)"
    
    Present:
    ----------
    positional arguments:
      mastervol            Master Volume Name
      SLAVE                SLAVEHOST or root@SLAVEHOST or user@SLAVEHOST
      slavevol             Slave Volume Name
    
    Suggested:
    -----------
    positional arguments:
      mastervol            Master Volume Name
      SLAVE                Slave hostname (<username>@SLAVEHOST or SLAVEHOST)
      slavevol             Slave Volume Name
    
    fixes: bz#1786276
    
    Change-Id: I73d52247997d623f77d55e51cbb6eccc08eb95ff
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit 59ed165a60a58db62a67a9d9fbe75d8338e5ddeb
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Wed Jul 31 11:34:19 2019 +0530

    geo-rep: Note section is required for ignore_deletes
    
    There exists a window of 15 sec, where the deletes are picked up
    by history crawl when the ignore_deletes is set to true.
    And it eventually deletes the file/s from slave which is/are not
    supposed to be deleted. Though it is working as per design, a
    note regarding this is needed.
    
    Added a warning message indicating the same.
    Also logged info when the worker restarts after ignore-deletes
    option set.
    
    fixes: bz#1708603
    Change-Id: I103be882fac18b4cef935efa355f5037a396f7c1
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 1e56e7acc3ced4f49d4494556bf6c86cd017b4ea
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Dec 10 10:56:55 2019 +0200

    posix: improve posix_{set_gfid2path_xattr|remove_gfid2path_xattr} funcs
    
    1. Move them to posix-entry-ops.c and make them static.
    2. Remove useless 'val' parameter allocation and snprintf() in
    posix_set_gfid2path_xattr(), as it was identical to pgfid_bname.
    
    Change-Id: I41f3946c6c42aee9d7cf1150e21b442438fbcce2
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 5cfd4553d163b96c9c409db68264d1b6af2fe49e
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Dec 29 17:35:13 2019 +0200

    afr: simplify afr_has_quorum()
    
    1. Perform AFR_COUNT() once, in afr_has_quorum() and pass the result
    to afr_lookup_has_quorum()
    2. Simplify afr_lookup_has_quorum() - pass less parameters to it.
    (Via the change in item 1 above).
    3. Make afr_is_add_replica_mount_lookup_on_root() static function.
    4. Remove dead code - afr_decide_heal_info() which was not used.
    
    Change-Id: If9168cd01e22788a0e60b91e315787d2aa60e97b
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 51c4002030da6b1a11f6e8f48bf117084b1da34d
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Dec 26 09:29:00 2019 +0200

    Remove some compiler warnings when not compiling gNFS
    
    As a follow up to https://review.gluster.org/#/c/glusterfs/+/23799/
    When compiling without gNFS, there were some 'unused' warnings by
    the compiler. This patch fixes them.
    
    Change-Id: I621562261f53950e821a450e0e7da304d00ae557
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit e40d0c399333e1ef62ff104b5cd35d8a5baa75f4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Dec 25 21:56:32 2019 +0530

    glusterd: deafult options after volume reset
    
    Problem: default option itransport.address-family is disappered
    in volume info output after a volume reset.
    
    Cause: with 3.8.0 onwards volume option transport.address-family
    has default value, any volume which is created will have this
    option set. So, volume info will show this in its output. But,
    with reset volume, this option is not handled.
    
    Solution: In glusterd_enable_default_options(), we should add this
    option along with other default options. This function is called
    by glusterd_options_reset() with volume reset command.
    
    fixes: bz#1786478
    
    Change-Id: I58f7aa24cf01f308c4efe6cae748cc3bc8b99b1d
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 7555ebc629774b95a878678f8ab0946c3bcf2f32
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Fri Dec 27 13:35:33 2019 +0300

    cli, libglusterfs: rely on libpthread static initializers
    
    cli-cmd.c: drop cli_cmd_cond_init() because static mutex and
    condition variable are initialized with PTHREAD_xxx_INITIALIZERs.
    
    syncop-utils.c: since assignment PTHREAD_xxx_INITIALIZERs are
    never failed, a few overengineered bits may be simplified.
    
    Change-Id: Ic4d250a1697047386989f73f058b0abc8b55627b
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
    Updates: bz#1193929

commit 33453ec69af1070dd5e15dd99c14ebb43c4e88c2
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Dec 27 21:30:21 2019 +0200

    posix-inode-fd-ops.c: fix a compiler warning - real_path may be NULL
    
    Fixes the following:
    posix-inode-fd-ops.c: In function ‘posix_common_removexattr’:
    ../../../../libglusterfs/src/glusterfs/logging.h:231:9: warning: ‘%s’ directive argument is null [-Wformat-overflow=]
      231 |         _gf_msg(dom, __FILE__, __FUNCTION__, __LINE__, level, errnum, 0,       \
          |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      232 |                 msgid, ##fmt);                                                 \
          |                 ~~~~~~~~~~~~~
    posix-inode-fd-ops.c:4401:13: note: in expansion of macro ‘gf_msg’
     4401 |             gf_msg(this->name, GF_LOG_WARNING, errno, P_MSG_FDSTAT_FAILED,
          |             ^~~~~~
    posix-inode-fd-ops.c:4402:47: note: format string is defined here
     4402 |                    "fdstat operaton failed on %s", real_path);
          |                                               ^~
    
    Change-Id: I3f2278d3a05a569dde257d66f44a8655491b4013
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit ec3df84dcfd7ccda0a18fa75e3b425c090209adf
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Thu Nov 14 12:37:24 2019 +0530

    features/changelog: Optimization in changelog
    
    Problem: Currently changelog is written in one directory, which over
    time, results in very large changelog files.
    
    Solution: Seperate directory under the changelogs directory
    is created on daily basis following the format year/month/day.
    
    Updates: #154
    Change-Id: I1cdabe33728a0ba1f298c8908bd8c323b1871bda
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit ca3e5905ac02fb9c373ac3de10b44f061d04cd6f
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Sun Oct 20 22:01:01 2019 +0530

    posix: Avoid diskpace error in case of overwriting the data
    
    Problem: Sometime fops like posix_writev, posix_fallocate, posix_zerofile
             failed and throw error ENOSPC if storage.reserve threshold limit
             has reached even fops is overwriting the data
    
    Solution: Retry the fops in case of overwrite if diskspace check
              is failed
    
    Credits: kinsu <vpolakis@gmail.com>
    Change-Id: I987d73bcf47ed1bb27878df40c39751296e95fe8
    Updates: #745
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit e21a5a1b1edc5f0ddea54be3dd10869de517b9e6
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Dec 29 11:03:40 2019 +0200

    posix-entry-ops.c: remove some tier related code
    
    Remove TIER_LINKFILE_GFID related code from posix
    
    Tier xlator was removed, but there are some code related to it scattered
    around in DHT and Posix xlators. Remove some of it.
    
    Change-Id: I3a878b31ed4a045ed419f936aa1d567ded1a273f
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 42f484dcecd9942611396d9bd2ad3a39019b0e1f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Dec 18 13:16:39 2019 +0530

    mgmt/brick-mux: Avoid sending two response when attach is failed.
    
    We were sending two response back to glusterd when an attach is
    failed. One from the handler function glusterfs_handle_attach and
    another from rpcsvc_check_and_reply_error. It was causing problems
    like ref leaks, transport disconnect etc.
    
    Change-Id: I3bb5b59959530760b568d52becb519499b3dcd2b
    updates: bz#1785143
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 745f6534c514010cc69e2306e1621e9d14ff5dba
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Thu Dec 26 13:50:20 2019 +0300

    transport/socket: destroy notify mutex and condition variable
    
    Change-Id: Id74f829dc5c6a30d19e3c3ef42bcb938afc0d8e4
    Updates: bz#1430623
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>

commit 9937b9857472c346c071c3850b032ae9237721e5
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Thu Dec 26 14:22:56 2019 +0300

    socket: fix typos and drop unused members/options
    
    Consistently fix 'configued' -> 'configured' typo, remove useless
    members from 'socket_private_t' and unused 'transport.socket.lowlat'
    option. Adjust tests as well.
    
    Change-Id: I285be196457763aec16b184acd26b90623074dec
    Updates: bz#1193929
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>

commit f2a86ddf9331cd7387c44ba03307adac43575fc4
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Dec 27 13:26:04 2019 +0000

    extras: enable log rotation for USS logs
    
    Added logrotate support for user serviceable snapshot's logs.
    
    Change-Id: Ic920eaa8ab5e44daf5937a027c6913d7bb26d517
    Fixes: bz#1786722
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 7656aec3b9ef60592c8cf251dfb5cdb6088cd328
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Thu Dec 26 15:25:35 2019 +0300

    Avoid buffer overwrite due to uuid_utoa() misuse
    
    Code like:
    
    f(..., uuid_utoa(x), uuid_utoa(y));
    
    is not valid (causes undefined behaviour) because uuid_utoa()
    uses the only static thread-local buffer which will be overwritten
    by the subsequent call. All such cases should be converted to use
    uuid_utoa_r() with explicitly specified buffer.
    
    Change-Id: I5e72bab806d96a9dd1707c28ed69ca033b9c8d6c
    Updates: bz#1193929
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>

commit f5aafeffed3a5363ff200e9300dec5855f680d9c
Author: yatipadia <ypadia@redhat.com>
Date:   Thu Dec 12 14:40:03 2019 +0530

    xlator/bit-rot-stub: structure logging
    
    convert gf_msg() to gf_smsg()
    
    Change-Id: I3072ba4305b720bea053688d140660d7d5c2d267
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit 77c48f77a9e7bfa202f9a211bacd7e7a9f88ae6b
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Dec 19 11:58:54 2019 +0100

    timer: fix event destruction race
    
    In current timer implementation, each event has an absolute time at which
    it will be fired. When the first timer of the queue has not elapsed yet,
    a pthread_cond_timedwait() is used to wait until the expected time.
    
    Apparently that's fine. However the time passed to that function was a
    pointer to the timespec structure contained in the event itself. This is
    problematic because of how pthread_cond_timedwait() works internally.
    
    Simplifying a bit, pthread_cond_timedwait() basically queues itself as a
    waiter for the given condition variable and releases the mutex. Then it
    does the timed wait using the passed value.
    
    With that in mind, the follwing case is possible:
    
       Timer Thread                            Other Thread
       ------------                            ------------
    
    					   gf_timer_call_cancel()
       pthread_mutex_lock()                    |
                                               + pthread_mutex_lock()
       event = current_event()                 |
       pthread_cond_timedwait(&event->at)      |
       + pthread_mutex_unlock()                |
       |                                       + remove_event()
       |                                       + destroy_event()
       + timed_wait(&event->at)
    
    As we can see, the time is used after it has been destroyed, which means
    we have a use-after-free problem.
    
    This patch fixes the problem by copying the time to a local variable
    before calling pthread_cond_timedwait()
    
    Change-Id: I0f4e8eded24fe3a1276dc75c6cf093bae973d26b
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
    Fixes: bz#1785208

commit 6350695dccfafdd6ab22be3509ade549a34db98b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Dec 24 13:53:16 2019 +0530

    Revert "store.c: remove a sys_stat() call - just open the file"
    
    This reverts commit da735ad9b58b76d27c580a9feb63f14b2cc0669d.
    
    This commit is changing the behaviour of glusterd during its
    initialization. The removed piece of code checks whether the
    file mentioned in the path exists or not, if not it returns
    -1. This return value is considered for the sub sequent
    operations. By removing this code, we always return 0 and
    some part of the code will not be executed in the following
    code path.
    
    glusterd_options_init() -> glusterd_store_retrieve_options() ->
    gf_store_handle_retrieve()
    
    In glusterd_options_init(), we are not executing any code
    if the ret value is 0.
    
        ret = glusterd_store_retrieve_options(this);
        if (ret == 0) {
            goto out;
        }
    
    as we are not executing any code if the return value is 0,
    we are unable to enable the brick-multiplex feature using
    volume set.
    
    fixes: bz#1786459
    Change-Id: I4f52b7b2ea8adb8df5087bb96927e9bb7db5b491

commit 28d87d5d833f2de320169aa766feaccc0bd98262
Author: Barak Sason <bsasonro@redhat.com>
Date:   Thu Oct 24 16:28:31 2019 +0300

    libglusterfs/logger - code cleaning
    
    Fixes: bz#1765186
    
    1 - Removed code duplication of 'log_levles' array
    2 - Declared all static methods at the begining of the .c file
    3 - Removed unused structs that existed in the .c file
    
    Change-Id: I37330cb133fc65deac69b7ca60779f70501c24ea
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit e879ff1d4a3a0d795da2575406414eaeb28975f4
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Dec 3 15:28:13 2019 +0200

    md-cache.c: move cache-swift-metadata to off by default
    
    This causes mdc_xattr_list_populate() NOT to add "user.swift.metadata"
    as an xattr in the list of attrs we look at in some paths of the code.
    
    This is documented @
    https://github.com/gluster/glusterfs/issues/775
    
    Change-Id: Ie3d676c74a2f333beeacc302e253efe9f9942d1a
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit da735ad9b58b76d27c580a9feb63f14b2cc0669d
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Nov 25 15:45:27 2019 +0200

    store.c: remove a sys_stat() call - just open the file
    
    I don't see the value on performing a sys_stat() on a path
    instead of just trying to open the file.
    
    Change-Id: Ib3f88d8c45aea091eafea17c4be02e2acdb713f1
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 82ba1cb8ec8cdbc02ad69a2ab4c6cf569503ab34
Author: yatipadia <ypadia@redhat.com>
Date:   Mon Nov 4 21:04:45 2019 +0530

    afr_inode/xlator: structure logging
    
    convert gf_msg() into gf_smsg()
    
    Change-Id: I8f5b7bbb9caa78902b06f67257502b67adab7405
    Updates: #657
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit 3389bc58ea9773a66ed4bc7bd96b93dc1c97e4cc
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Nov 20 22:31:48 2019 +0530

    tests/fuse/bug-965974.t: turn off md-cache, to fix failure of the test
    
    Imagine the following set of operations:
    1. touch $M0/file
    2. ln $M0/file $M0/file.lnk
    3. rm $M1/file
    4. wait for md-cache-timeout
    5. stat $M0/file.lnk $M0/file
    
    stat on $M0/file in step 5 succeeds when md-cache-timeout is non-zero
    even though it was removed from $M1. The reason is
    1. fuse-bridge on $M0 would resolve both file and file.lnk to same
       inode. This inode i1 is cached in md-cache.
    2. After md-cache-timeout lookup on $M0/file.lnk would be sent to
       backend. This lookup will be successful as file.lnk is present on
       backend and would refresh the md-cache.
    3. The lookup on $M0/file sent within md-cache-timeout after lookup on
       $M0/file.lnk would be sent with i1. Since i1 was refreshed by
       lookup on $M0/file.lnk, the cache is deemed valid and md-cache
       responds lookup on $M0/file as success
    
    To fix this failure we can either:
    1. remove lookup on $M0/file.lnk, so that lookup on $M0/file is
       actually sent to backend.
    2. turn off md-cache
    
    This patch chooses option 2.
    
    credits: Csaba Henk <csaba@redhat.com>
    
    Change-Id: I352c2acd377fe10c4bdf3b6e53c1de86a4e544c7
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1756900

commit d8adc66b79de3f21672884539a65327614e0c6bb
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Thu Dec 5 16:57:28 2019 +0300

    glfsheal: install as architecture-dependent binary helper
    
    Since glfsheal is a binary helper which is not intented to be
    invoked directly, install it under %{libexecdir}/glusterfs rather
    than %{sbindir}, adjust invocation from CLI code and RPM spec.
    
    Credits: Ravishankar N <ravishankar@redhat.com>.
    Fixes: bz#1780190
    
    Change-Id: I4b41892d96b89c24a332470ac8c1e82f6795159a
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>

commit bc6e206c6d29234a0b167b142d20c62ffd529f15
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Oct 28 21:29:50 2019 +0200

    cli-rpc-ops.c: cleanups
    
    1. Move functions and structs to static
    2. Use dictionary functions with fixed key length.
    3. Reduce key length when not needed.
    4. Use const char* for some messages.
    5. Use fixed strings for some logs which is repeated in the code.
    6. Remove redundant checks. Specifically, cli_to_glusterd() does
    NULL checks already, so no need to do it before calling it.
    7. Aligned some messages - not sure why they were cut over several
    lines, but it made grep on the code harder.
    8. Move dictionary fetching of values closer to where they are
    actually used.
    
    Overall, object size is ~4 smaller, hopefully without functional changes.
    
    There's more that can be done, but as this is a very long (>10K lines)
    file, I think it's enough for one change.
    Specifically, some functions fetch values from the dictionary
    without using it - this is a bit of a waste.
    Filed https://github.com/gluster/glusterfs/issues/753 about it.
    
    Change-Id: I31f88d94ab25398e00aef2ea84a8c4af9383b75b
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 8c6a19783e149dda1ab9143f48badfa617478e6e
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Tue Nov 5 15:54:29 2019 +0200

    glusterd: refactoring long method
    
    - Refactored set_fuse_mount_options(...) in order to shorten it.
    - Removed dead code and moved some method to it's apropriate
    location.
    - Converted loggin in set_fuse_mount_options(...) to structured logs
    
    fixes: bz#1768896
    Change-Id: If865833d4c60d517da202871978691ef21235fe4
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit a7eeab9b497724cdc4de5a82b880ba824a9d8358
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Dec 16 12:52:41 2019 +0000

     test: fix non-root test case for geo-rep
    
    Problem:
    On a freshly installed system non-root geo-rep test case gets blocked.
    
    Solution:
    
    On a freshly installed system, the remote key need to be accepted automatically by ssh-copy-id.
    
    Credits: M. Scherer <mscherer@redhat.com>
    
    Change-Id: I5077f99a6681660f7e3e84c25ef216f521b7c29c
    Fixes: bz#1779742
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 194e4216c8e30612f96f8f3712fdb3f1c96b3a08
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Dec 3 12:57:13 2019 +0200

    [RFC]#ifdef gNFS related code if we are not compiling gNFS
    
    If we are not compiling gNFS (--enable-gnfs is not given in the
    ./configure script params), there is little point in compiling code
    that is related to it.
    
    This patch tries to eliminate it.
    My hope (and it's not clear from the code ) is that I did not break
    the NFS Ganesha support as well.
    
    Other than that, tried to compile with and without anad it looks sane.
    
    Change-Id: I8d6c98066b9fceab4ec10fc6f5e81ab069e853bd
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 6f6b253deed134c5fee37e1e3d2fd44b18e1db6e
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Dec 17 15:52:30 2019 +0530

    glusterd: unlink the file after killing the process
    
    In glusterd_proc_stop(), after killing the pid
    we should remove the pidfile.
    
    fixes: bz#1784375
    
    Change-Id: Ib6367aed590932c884b0f6f892fc40542aa19686
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 8537d5bda5fa5d52840e24884eaa3f2bcfcd6bd9
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Dec 12 08:12:44 2019 +0200

    call-stub.c: remove redundant validation
    
    GF_VALIDATE_OR_GOTO("call-stub", frame, out) is removed.
    It's not needed, since we are testing via the creation of a stub,
    in stub_new() that frame is not NULL.
    
    Removed all redundant checks, which saves  >10% in object size.
    
    Change-Id: If4ce3a3dc506a5e65e98b59fa51b1fdd389a85ba
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit f6e2958543246d547f1c3c3b3b080d435b4c9296
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Sat Nov 30 15:25:11 2019 +0530

    [Cli] Removing old log rotate command.
    
    The old command for log rotate is still present removing
    it completely. Also adding testcase to test the
    log rotate command with both the old as well as the new command
    and fixing testcase which use the old syntax to use the new
    one.
    
    Code to be removed:
    1. In cli-cmd-volume.c from struct cli_cmd volume_cmds[]:
    {"volume log rotate <VOLNAME> [BRICK]", cli_cmd_log_rotate_cbk,
     "rotate the log file for corresponding volume/brick"
     " NOTE: This is an old syntax, will be deprecated from next release."},
    
    2. In cli-cmd-volume.c from cli_cmd_log_rotate_cbk():
     ||(strcmp("rotate", words[2]) == 0)))
    
    3. In cli-cmd-parser.c from cli_cmd_log_rotate_parse()
    if (strcmp("rotate", words[2]) == 0)
       volname = (char *)words[3];
    else
    
    fixes: bz#1750387
    Change-Id: I56e4d295044e8d5fd1fc0d848bc87e135e9e32b4
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit ff7865be148d5f4f22861fe93710c0b97d24f81f
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Tue Nov 26 12:36:16 2019 +0200

    DHT - Reduce methods scope (dht-common.c)
    
    Methods that should have been static were defined as global, and the
    other way around.
    This patch fixes the issue in order to enforce encapsulation.
    
    updates: bz#1776757
    
    Change-Id: I3eb5781849c5e597c1dd347e03f356c00db62a39
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit 49f524def676e62e0f0cfb8a674bc28923c28f13
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Oct 22 15:41:41 2019 +0300

    dht-common.h/dht-helper.c: exctract the LOCK() from DHT_UPDATE_TIME
    
    Currently, the code (and only place) that is using this macro is
    in dht_inode_ctx_time_update() where it is called 3 times in a row,
    which is essentially 3 cycles of LOCK/UNLOCK on the same lock.
    
    Instead, extract the LOCK()/UNLOCK() part of the macro
    and wrap those calls with it.
    
    Change-Id: I6312b985e3d97517857b55f342440accc4063db6
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 5ab835004371f2165d1c3f335aa0fd777c9f8c20
Author: Andrew Miloradovsky <andrew@interpretmath.pw>
Date:   Mon Dec 2 17:36:48 2019 +0300

    rpc: define xdr_sizeof regardless of whether IPv6 is the default
    
    Change-Id: I4f20f376d82b28e1c572c0fd0b6cd38e97b133da
    Fixes: bz#1780260

commit b202e0e01d0eb8085eb8006dfa77b7b4b06978e6
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Dec 11 18:21:14 2019 +0100

    socket: fix error handling
    
    When __socket_proto_state_machine() detected a problem in the size of
    the request or it couldn't allocate an iobuf of the requested size, it
    returned -ENOMEM (-12). However the caller was expecting only -1 in
    case of error. For this reason the error passes undetected initially,
    adding back the socket to the epoll object. On further processing,
    however, the error is finally detected and the connection terminated.
    Meanwhile, another thread could receive a poll_in event from the same
    connection, which could cause races with the connection destruction.
    When this happened, the process crashed.
    
    To fix this, all error detection conditions have been hardened to be
    more strict on what is valid and what not. Also, we don't return
    -ENOMEM anymore. We always return -1 in case of error.
    
    An additional change has been done to prevent destruction of the
    transport object while it may still be needed.
    
    Change-Id: I6e59cd81cbf670f7adfdde942625d4e6c3fbc82d
    Fixes: bz#1782495
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit d7e049160a9dea988ded5816491c2234d40ab6b3
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Nov 7 15:18:30 2019 +0530

    afr: make heal info lockless
    
    Changes in locks xlator:
    Added support for per-domain inodelk count requests.
    Caller needs to set GLUSTERFS_MULTIPLE_DOM_LK_CNT_REQUESTS key in the
    dict and then set each key with name
    'GLUSTERFS_INODELK_DOM_PREFIX:<domain name>'.
    In the response dict, the xlator will send the per domain count as
    values for each of these keys.
    
    Changes in AFR:
    Replaced afr_selfheal_locked_inspect() with afr_lockless_inspect(). Logic has
    been added to make the latter behave same as the former, thus not
    breaking the current heal info output behaviour.
    
    fixes: bz#1774011
    Change-Id: Ie9e83c162aa77f44a39c2ba7115de558120ada4d
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 9e79604518dcf75a9f88a2444c177e97fd13067c
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Tue Dec 3 13:53:34 2019 +0800

    contributors: map domain names for CMSS
    
    updates: bz#1193929
    Change-Id: Iaf1e1e3f787855ede1e94101ec0364084e534d61
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit 86f54c6f82eae33f4070705678fc3b0ff6b7e3d5
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Mon Dec 2 13:20:02 2019 +0800

    fuse: add missing unlock
    
    updates: bz#1193929
    Change-Id: I50f75f730ea6970e99347fcee661ce9dc8477725
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit 8030f9c0f092170ceb50cedf59b9c330022825b7
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Dec 10 08:35:23 2019 +0530

    rpc: event_slot_alloc converted infinite loop after reach slot_used to 1024
    
    Problem: In the commit faf5ac13c4ee00a05e9451bf8da3be2a9043bbf2 missed one
             condition to come out from the loop so after reach the slot_used to
             1024 loop has become infinite loop
    
    Solution: Correct the code path to avoid the infinite loop
    
    Change-Id: Ia02a109571f0d8cc9902c32db3e9b9282ee5c1db
    Fixes: bz#1781440
    Credits: Xavi Hernandez <xhernandez@redhat.com>
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit f8f4efef77c177900923f5b29ddb707fb3f07720
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Sun Dec 1 12:26:53 2019 +0200

    afr/self-heald - Missing error logs
    
    As a follow up on https://review.gluster.org/#/c/glusterfs/+/23749/,
    adding error logging for the entire method.
    In addition, converted logging to structured logging in the method.
    
    Fixes: bz#1778457
    Change-Id: I1f412159e6849d6f6ddbde53ec4a85ad709bbdf4
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit ba407a67fc0895c970c327361110a960af254401
Author: Anoop C S <anoopcs@redhat.com>
Date:   Fri Nov 22 17:36:55 2019 +0530

    extras/hooks: Remove smb.conf parameter allowing guest access
    
    Change-Id: I88f494f16153d27ab6e2f2faf4d557e075671b10
    Fixes: bz#1775612
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 990d9fb3973cc3d3e211f0b4eebd8e909efd8028
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Tue Dec 3 12:13:16 2019 +0200

    cloudsync - fixing a coverity issue
    
    A negative value was being passed where it shouldn't have been passed
    to. Modified code so only a positive value will be passed.
    
    fixes: CID#1274209
    Change-Id: I5452ddded77664fdd8b5c975af6bc77806a7ffb1
    updates: bz#789278

commit 400cf809ed24ffb506fed6edd510643be406e3ea
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Nov 18 05:24:33 2019 -0500

    ctime: Fix ctime inconsisteny with utimensat
    
    Problem:
    When touch is used to create a file, the ctime is not matching
    atime and mtime which ideally should match. There is a difference
    in nano seconds.
    
    Cause:
    When touch is used modify atime or mtime to current time (UTIME_NOW),
    the current time is taken from kernel. The ctime gets updated to current
    time when atime or mtime is updated. But the current time to update
    ctime is taken from utime xlator. Hence the difference in nano seconds.
    
    Fix:
    When utimesat uses UTIME_NOW, use the current time from kernel.
    
    fixes: bz#1773530
    Change-Id: I9ccfa47dcd39df23396852b4216f1773c49250ce
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit d30c0b5fa4dba283587cb77a95a79b395cad8e1b
Author: Andrew Miloradovsky <andrew@interpretmath.pw>
Date:   Mon Dec 2 13:23:16 2019 +0300

    git-ignore .dirstamp
    
    Change-Id: I8a0191252c017bda9e9d42f9622504698bf6e7da
    Fixes: bz#1776892

commit 75205f901c06f39fdd41ebd13303e0a70a460041
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Dec 3 10:29:37 2019 +0530

    cluster/dht: Add comments to code
    
    Change-Id: Ieb7531af19ae89fb8a8387e81663c7f157b10c02
    Updates: bz#1765421
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 99044a5cedcff9a9eec40a07ecb32bd66271cd02
Author: HuangShujun <549702281@qq.com>
Date:   Thu Dec 5 10:07:10 2019 +0200

    To fix readdir-ahead memory leak
    
    Glusterfs client process has memory leak if create serveral files under one folder, and delete the folder.
    According to statedump, the ref counts of readdir-ahead is bigger than zero in the inode table. Readdir-ahead get parent inode by inode_parent in rda_mark_inode_dirty when each rda_writev_cbk,the inode ref count of parent folder will be increased in inode_parent, but readdir-ahead do not unref it later.
    The correction is unref the parent inode at the end of rda_mark_inode_dirty
    
    Fixes: bz#1779055
    Signed-off-by: HuangShujun <549702281@qq.com>
    
    Change-Id: Iee68ab1089cbc2fbc4185b93720fb1f66ee89524

commit b20b60027c7212d7ecba96a7d75b5f5cbcc08989
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Sep 6 14:47:04 2019 +0530

    cluster/ec: Scripts to find and reset files which can be healed.
    
    gfid_needing_heal_parallel.sh - Finds out if a file is healable or not.
    
    correct_pending_heals.sh - Makes necessary changes in xattrs to enable
    heal for those files which could be healed.
    
    fixes: #723
    Change-Id: I38177888df0fda9486343ee546dc02836b06a5fc

commit ff53751b37656d6a530c5a347bb1aa84649fff6d
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Oct 22 19:03:13 2019 +0530

    core: fix spelling mistakes
    
    fixes: bz#1728554
    
    credits: Patrick Matthäi <pmatthaei@debian.org>
    
    Change-Id: Id08dabf54a529dbb86666b544b1f0859aab75aac
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 3199f8759ebfcc31ce158201c3c25d9a738479f8
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date:   Wed Dec 4 15:46:16 2019 +0300

    core: avoid NULL pointer dereference
    
    Since low-level __gf_xxx allocation function may be called before
    ctx is initialized, add extra check for NULL where appropriate.
    
    Fixes: bz#1776784
    Change-Id: I3127fa4b93f8e3e5846106aadcfed1baa27ac43f
    Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>

commit dc757b2c97f5917885db76c62fa4fb429ae7b9ab
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Nov 26 17:03:44 2019 +0530

    glusterd: set xaatrs after checking the brick order
    
    Problem: When volume creation fails complaining about
    the bricks from same hosts for replica volumes, the
    bricks can't be re-used to create any volume without
    using force at the end. It says, brick is already part
    of a volume.
    
    Reason: When volume create opeartion issued, we set
    xattrs on the bricks. If the transaction fails in later
    checks, the xattrs will remain on the brick. When the
    brick is re-used, by looking at the xattrs, glusterd
    thinks it is already part of volume.
    
    Solution: Check the brick order for replica and disperse
    volumes before setting the xattrs.
    
    fixes: bz#1776801
    
    Change-Id: I44a971b37f520e5a20dc9fad6520286d315063b9
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 6015ab7d8b37388e836f36a315af54f019839d91
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Nov 25 16:35:42 2019 +0530

    glusterd: start glusterd automatically on abnormal shutdown
    
    If glusterd crashes or goes down abnormally, systemd should
    automatically bring the glusterd up.
    
    With this change, systemd brings glusterd up for atmost 3 times
    within time period of 1 hour. If the limit exceeds, we have to
    start the glusterd manually and reset the failure count using
    systemctl reset-failed.
    
    credits: John Strunk <jstrunk@redhat.com>
    
    fixes: bz#1776264
    
    Change-Id: I312d243652fb13ba028814a2ea615b67e3b10b6a
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit d29b8e62a186770d26bf7daf3437d899ae00a0da
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Tue Dec 3 13:39:47 2019 +0800

    glusterd-store: fix Coverity CID 1407767
    
    To avoid memory leak.
    
    updates: bz#789278
    Change-Id: I321c65a66c9ac372d059aa3ca89a989c6089979e
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit c65c0a72f4f1597ffa8bc0f8a8dc83abedf3e099
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Nov 29 17:07:14 2019 +0530

    MAINTAINERS: add Xie Changlong and Amar Tumballi as peers for gNFS
    
    * Change status of gNFS from Deprecated to Odd Fixes
    
    More discussion on this @ thread in gluster-devel:
    https://lists.gluster.org/pipermail/gluster-devel/2019-November/056685.html
    
    Change-Id: I119f588f3ad07fa55764ee7cf7db42905e19ee1b
    Updates: bz#1193929
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 8483753514393239ba46e11c3a83e7ebff4cc3f4
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Thu Nov 21 12:56:34 2019 +0530

    man/gluster: Add volume top command to gluster man page
    
    Change-Id: Ib74607d2b2e5a1a0316221f1176a7dcccea632d4
    Fixes: bz#1774866
    Signed-off-by: Vishal Pandey <vpandey@redhat.com>

commit b35f8addc6b582a2498dfae546fbb942964c66b3
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Nov 3 15:21:05 2019 +0200

    glusterd-op-sm.c (and others) - improve glusterd_op_stage_set_volume()
    
    Multiple changes to the function in the hope to make it somewhat faster.
    1. Checking for key length against constant strings before calling
    strcmp() to save some calls.
    2. Verifying if a match was already made against the key to reduce
    yet more checks.
    3. Alignment of error message when they can fit on less lines - just
    makes 'grep' on the code for error messages easier and it's more
    readable.
    4. Multiple functions where call _gd_get_vmep() one by one.
    Instead, extracted it to be callable (it was static) and re-used
    its result, instead of calling it again and again.
    5. Removed some unneeded include statement.
    6. Removed redundant null checks.
    
    Hopefully, no functional changes.
    
    Change-Id: Id281224e49adeca6757f96653b4cb13c7c9ba8c9
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 1bfb0a750c6fcd0bbf4d68a1890704f0aefe6337
Author: Amar Tumballi <amar@kadalu.io>
Date:   Sun Nov 17 11:00:50 2019 +0530

    debug/io-stats: add an option to set volume-id
    
    'volume-id' is good to have for a graph for uniquely identifying it.
    Add it to graph->volume_id while generating volfile itself.
    
    This can be further used in many other places.
    
    Updates: #763
    Change-Id: I80516d62d28a284e8ff4707841570ced97a37e73
    Signed-off-by: Amar Tumballi <amar@kadalu.io>

commit 7c1e383876ad15ec6fc93d412311662f42390a11
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Nov 28 10:31:11 2019 +0530

    MAINTAINERS: Add Nithya to past contributors section
    
    Change-Id: I18195a61314946930db669fcf72703a7a18f43a1
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    updates: bz#1193929

commit 1e5cc2754d88089be48e68cf70e0e59d6b4c99ca
Author: Barak Sason Rofman <bsasonro@redhat.com>
Date:   Sun Nov 24 18:16:54 2019 +0200

    cluster/afr - coverity issue fix
    
    Added a log for a failure in order to avoid "unused variable" coverity
    issue.
    
    fixes: CID#1274209
    
    Change-Id: Ibc6b0ab4bdff482096e42e88fd4c8c7eadfeeadb
    Updates: bz#789278
    Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>

commit 3a8969b852a70bc05887c764474039279ceb23ff
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Nov 28 07:19:13 2019 +0000

    Revert "afr: make heal info lockless"
    
    This reverts commit fce5f68bc72d448490a0d41be494ac54a9181b3c.
    I merged the wrong patch by mistake! Hence reverting it.
    
    updates: bz#1774011
    Change-Id: Id7d6ed1d727efc02467c8a9aea3374331261ebd5

commit fce5f68bc72d448490a0d41be494ac54a9181b3c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Nov 7 15:18:30 2019 +0530

    afr: make heal info lockless
    
    Changes in locks xlator:
    Added support for per-domain inodelk count requests.
    Caller needs to set GLUSTERFS_MULTIPLE_DOM_LK_CNT_REQUESTS key in the
    dict and then set each key with name
    'GLUSTERFS_INODELK_DOM_PREFIX:<domain name>'.
    In the response dict, the xlator will send the per domain count as
    values for each of these keys.
    
    Changes in AFR:
    Replaced afr_selfheal_locked_inspect() with afr_lockless_inspect(). Logic has
    been added to make the latter behave same as the former, thus not
    breaking the current heal info output behaviour.
    
    fixes: bz#1774011
    Change-Id: I9ae08ce768b39aeb6ee230207b5b7fa744176952
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 8424df172339d3b2b65bc022e5c8f150f8826dba
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Nov 5 20:37:38 2019 +0200

    common-utils.c: add gf_strn2boolean() function
    
    The function takes a string and its length and based on it
    returns if it's a boolean. It's identical in functionality
    to gf_string2boolean only with far less string comparisons since
    it takes into account the length of the string.
    
    dict_get_str_boolean() has been converted to use it.
    
    Other cases of gf_string2boolean() across the code base can be
    converted as well, but more importantly, they should be converted
    from dict_get_str() and then calling to gf_string2boolean to
    simply call dict_get_str_boolean(), which would take care of this
    for them.
    
    This is therefore a first step in the conversion.
    
    Change-Id: I9ee93abfc676f6e123a3919d8df8c25e8848b799
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 023a565875891b8078d143a25fee9d44de365c88
Author: root <root@dhcp35-62.lab.eng.blr.redhat.com>
Date:   Tue Nov 26 10:30:17 2019 +0530

    Maintainers: Remove Nithya as maintainer/peer
    
    Change-Id: I9512a70622b51416174ff0936f8d02e3c0178e19
    Updates: bz#1193929
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>

commit 87ef6a23dee165b00418a36ad5473f4427928e49
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Nov 25 17:39:07 2019 +0200

    glusterfsd.c: remove sys_lstat() call
    
    get_volfp() in glfs.c doesn't use it, so get_volfp() in glusterfsd.c
    can just open the file without the stat call as well, IMHO.
    
    Change-Id: I3cb5bf12a09b5be42aa2ee4f432f8d351eee5b9e
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d97f78467849eef92559217b48d2158521cbba5f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Nov 25 15:37:46 2019 +0200

    store.c/glusterd-store.c: remove sys_stat calls
    
    Instead of querying for the file size and allocating a char array
    according to its size, let's just use a fixed size.
    Those calls are not really needed, and are either expensive or
    cached anyway. Since we do dynamic allocation/free, let's just use
    a fixed array instead.
    
    I'll see if there are other sys_stat() calls that are not really
    useful and try to eliminate them in separate patches.
    
    Change-Id: I76b40e78a52ab38f613fc0cdef4be60e6253bf20
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d60935d1011e387115e0445629976196f566b3b1
Author: Amar Tumballi <amar@kadalu.io>
Date:   Tue Nov 26 12:53:11 2019 +0530

    pcsvc: fix subnet_mask_v4 check
    
    The check we had for subnet mask validation wasn't checking in
    proper sequence. Corrected the order of calling `inet_pton()` as
    the fix.
    
    Fixes: #765
    Change-Id: I5d31468eb917aa94cbb85f573b37c60023e9daf3
    Signed-off-by: Amar Tumballi <amar@kadalu.io>

commit 337e6d6b7c6612a4ce360c9e4d1a484436cdef57
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Nov 25 21:00:59 2019 +0200

    posix-inode-fd-ops.c: excute sys_fstat() only when needed
    
    It appears that in posix_do_futimes() we may not need to
    unconditionally execute sys_fstat(). Avoid it and use the
    existing stbuf atime and mtime if possible.
    If not, we execute it.
    
    Change-Id: I0bdd471e5c821fcd28f057c75046c673a212d347
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit b7411e36514f2e564b3808679732ad8a5c1d9efd
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Oct 4 23:14:08 2019 +0300

    cli-*: make some structs static to reduce space consumed.
    
    There's a small difference when structs are defined static.
    Whenever possible, define them as such.
    
    Specifically, before:
       text    data     bss     dec     hex filename
        678     216       0     894     37e ./cli/src/cli-cmd-misc.o
     150024    1264      16  151304   24f08 ./cli/src/cli-rpc-ops.o
      71980      64       0   72044   1196c ./cli/src/cli-cmd-parser.o
      66189       4      16   66209   102a1 ./cli/src/cli-xml-output.o
    
    After:
       text	   data	    bss	    dec	    hex	filename
        670	    216	      0	    886	    376	./cli/src/cli-cmd-misc.o
     149848	   1392	     16	 151256	  24ed8	./cli/src/cli-rpc-ops.o
      70346	   1320	      0	  71666	  117f2	./cli/src/cli-cmd-parser.o
      66157	      4	     16	  66177	  10281	./cli/src/cli-xml-output.o
    
    Change-Id: I206bd895290595d79fac7b26eee66f4279b50f92
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit a8d54730bba5050ad53cfa46477e698d565e05b1
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Nov 18 22:20:01 2019 +0200

    glusterfsd-mgmt.c: move INFO log outside a LOCK
    
    In glusterfs_handle_attach() we can:
    1. Move an INFO level to be executed before the LOCK.
    2. Skip the LOCK altogether, if there's no active graph.
    
    I hope it's safe - I've seen that in other functions
    you could look at ctx->active outside of a lock.
    
    Change-Id: I3e1ec5b1430d5fddee46883d468ff4f5bd6ca54b
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit b9181e9212b6916ba1c8a269c1474e7aef144f6a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Nov 4 15:25:27 2019 +0200

    socket.c: minor changes
    
    1. Remove dead code and declarations
    2. Move some dict functions to use more efficient ones.
    3. Use more constants, where possible.
    4. Align messages - easier to grep the code for them.
    5. Aligned structures and adding padding where needed.
    
    Change-Id: Ifc2639afe65a935fab5238d3e4a121b662836d3d
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 9d0a69187fe085c45b99d8f63febbab0206437c3
Author: Amar Tumballi <amarts@gmail.com>
Date:   Thu Oct 17 12:39:02 2019 +0530

    libglusterfs: remove unused gfdb specific files from repo
    
    Updates: bz#1193929
    Change-Id: Idb98394c51917e9b132aeb32facccd112effe672
    Signed-off-by: Amar Tumballi <amarts@gmail.com>

commit cd1872ae49d7bc83403fce6821c102edc4e97796
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Oct 28 21:53:01 2019 +0530

    posix: Improve MAKE_HANDLE_PATH
    
    Pass the maximum buffer (PATH_MAX) to posix_handle_path to
    avoid the posix_handle_path call again.
    
    Change-Id: I7d18313870218dc028c5f7fc94d6ec85a2bdb332
    Updates #761
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 515d1b4577d989fa99f236d9e344a71db7d001a0
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Nov 5 18:05:38 2019 +0200

    glusterd-volgen.c: improve volgen_graph_set_options_generic()
    
    Skip fetching "skip-CLIOT" unconditionally on every
    invocation of volgen_graph_set_options_generic().
    Instead, fetch only if the vme->key matches to it.
    We calculate the length of vme->key (but we would have
    done it anyway in dict_get() later on, so now we can use
    dict_getn() instead and re-use that key length) and check
    if the lengths match before doing a strcmp() between them.
    Lastly, if they match, we actually do the fetch.
    
    Change-Id: I9d9a7104f9e920bf81477128adb5fc87f5d30627
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d1842d97b22419a8b73c2da07caa5f346ee6f7a7
Author: Amar Tumballi <amarts@gmail.com>
Date:   Wed Nov 13 11:12:02 2019 +0530

    extras: fix the remote subvol name in case of thin-arbiter
    
    * Also make sure to provide log-level in systemd file,
      instead of volfile itself.
    
    Updates: bz#1193929
    Change-Id: I45a0b0ff3ebb4b3e095b4eed14b7bdf5816926d0
    Signed-off-by: Amar Tumballi <amarts@gmail.com>

commit b82b1a468edbfd7a25ed3b99cc8c006a3f798cd1
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Oct 25 11:25:06 2019 +0530

    cluster/dht: Add comments to the code
    
    Add comments to the code to explain what is
    being done and why.
    
    Change-Id: I50831d7bd4bb73e75f6cda05fafaeb5a8619baae
    Updates: bz#1765421
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e97f01ac5c9e2774510807728e52e8acc9524a88
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Nov 13 15:39:59 2019 +0530

    afr: fix log flooding
    
    Commit "ccf33e789 - dict.c: remove redundant checks"
    removed some NULL checks in certain dict functions. This caused
    flooding of fuse mount logs when I/O was done on the mount on a replica
    volume:
    
    Message:
    W [dict.c:1478:dict_get_with_refn]
    (-->/usr/local/lib/libglusterfs.so.0(dict_get_uint32+0x4d)
    [0x7ff9121ec963] -->/usr/local/lib/libglusterfs.so.0(dict_get_with_ref+0x90)
    [0x7ff9121eb93f] -->/usr/local/lib/libglusterfs.so.0(+0x229be)
    [0x7ff9121eb9be] ) 0-dict: dict OR key (glusterfs.lk.lkmode) is NULL [Invalid argument]
    
    Fix:
    In the relevant AFR functions, check that dict is not NULL before trying
    to perform operations on it.
    
    See bug description for more details.
    fixes: bz#1772006
    Change-Id: I30c89c0b5d6c80cc86a6047aae70127769412120
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 1e7fc7e540f3f7ca96e16a837d89405901bf03a2
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Nov 13 08:23:09 2019 +0530

    ssl/test: ssl test case is failing when using specific cipher
    
    Problem: On RHEL-8 ssl test case is failing when trying to
             connect with a peer after using the specific cipher.
    
    Solution: If cipher is not supported by openssl on rhel-8 then
              test case is failed.To avoid the issue validate the
              cipher before connecting with peer.
    
    Change-Id: I96d92d3602cf7fd40337126c8305a3f8925faf9b
    Fixes: bz#1756900
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit b6b9a27607132cf1b20c34ba948319b27ebce867
Author: MOHIT AGRAWAL <moagrawa@redhat.com>
Date:   Wed Nov 13 12:42:13 2019 +0000

    Revert "dict.c: remove redundant checks"
    
    This patch floods of dict_log at the time accessing key from dict if
    dict is not valid so revert the patch.
    
    This reverts commit ccf33e789f2cbd202e21340f684e2140d844a129.
    
    Change-Id: I81fa3b080a2f784254b519044ad284858583ec66
    updates: bz#1193929

commit 9a8f8b057415c362485d747c97d4491e80f65a23
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Nov 13 13:48:28 2019 +0530

    geo-rep: Improve debugging
    
    When gsyncd failed with tracebacks during start, it prints
    only exception object but not the error string. This patch
    adds the error string as well.
    
    Earlier:
    "failed with ImportError"
    
    Now:
    "failed with ImportError: No module named _io."
    
    fixes: bz#1771895
    Change-Id: I0d772a250d4c2010a0c35053aa7b165b71f8434e
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit e82cd7654a8c2faf46e1c553c7f8c251dff7002c
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Nov 11 11:25:03 2019 +0530

    cluster/dht: Don't skip entries with invalid stat
    
    Don't strip out entries with invalid stats in
    dht_readdirp_cbk.
    
    Change-Id: I136ab342762d020a3c0f43e51e0090aed2af4120
    Fixes: bz#1769754
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 4702232a1febc5de4ce9156e30552a0da4306eb8
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Wed Nov 13 12:19:54 2019 +0530

    api: Fix documentation path in README
    
    Ref: #84
    Updates: bz#1193929
    Change-Id: If346dbe421d3e301ae035165b2e01ee0a7176d36
    Signed-off-by: Amar Tumballi <amarts@gmail.com>

commit 74592eeb9d7b4dd266c752aaaf8f79b0a519ec4a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Nov 6 09:52:56 2019 +0200

    [WIP]gluster-volgen.c: remove more of JBR and FDL xlators
    
    the JBR and FDL experimental xlators were apparently removed.
    Removed additional leftovers scattered in the code.
    
    Change-Id: I78b6fa5fd9044dc48cdcb1fb094b8c267c2d1323
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 9595ecca3de49fdf37d30b151f5c3e071e0a80d0
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Nov 12 21:53:20 2019 +0530

    geo-rep: Fix py2/py3 compatibility in repce
    
    Geo-rep fails to start on python2 only machine like
    centos6. It fails with "ImportError no module named _io".
    This patch fixes the same.
    
    fixes: bz#1771577
    Change-Id: I8228458a853a230546f9faf29a0e9e0f23b3efec
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 256c5dd228af503ece1aebe1229feac61b55f1d3
Author: Xi Jinyu <xijinyu@cmss.chinamobile.com>
Date:   Tue Nov 12 01:37:40 2019 -0500

    libglusterfs/dict.c: Fix memory leaks.
    
    
    fixes: bz#1771365
    Change-Id: Id31687c4704cbbfea1084f912ed0420c7d1cc1ec
    Signed-off-by: Xi Jinyu <xijinyu@cmss.chinamobile.com>

commit 9f2ad630c877b7b3fb833c89ad85dc10bcf552c4
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Thu Nov 7 17:35:45 2019 +0800

    gluster: check ctx->active
    
    To avoid process "TRANSLATOR INFO" "BARRIER" if graph is not ready,
    also see commit ee630e25.
    
    Updates: bz#1769712
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>
    Change-Id: Ibd446a35962206d3689667cda7e6712d72e4ec2f

commit 45e8ddf6acebaf8c178b432024ab82288b54288f
Author: Amar Tumballi <amarts@gmail.com>
Date:   Fri Oct 25 22:57:04 2019 +0530

    MAINTAINERS: revised the maintainers list after 2 years
    
    The last major change to the file happened 2 years 5 months back.
    For the better health of the project, and to motivate the active
    contributors, and keeping the file up-to-date with who is working
    on what, it is critical for us to keep refreshing the file once
    every 2 years (at least).
    
    This is one such effort.
    
    Highlighted changes:
    
    * Moving both Jeff and Vijay from Maintainers to 'Special Thanks'
      section.
    * Moving Amar and Xavi as Maintainers, and Atin as Peer, mainly
      looking at the activities (patches, reviews, merges) across
      the codebase, and also the contributions in discussions.
    * Moving Shyam and Niels out of Peer list highlighting the 6+
      months of changed priorities.
    
    * Changed Xavi's contact from Datalab's to Red Hat's
    * Changed Amar's contact from Red Hat's to his Personal.
    
    * Removed:
      - Block Device (BD)
      - Experimental (RIO / JBR)
      - Gluster Object
      - Gluster Hadoop Plugin
      - Nagios Monitoring
      - GlusterD2 (and renamed glusterd1 to glusterd)
    
    * Marked 'NFS (gluster-NFS)' component as 'Deprecated / Orphan'
    
    * Moved few people, who stopped major contribution, mainly
      because of changing companies, changing projects inside
      their own company etc, to 'Special Thanks' section.
    
    * Additions:
      - Kotresh added as Peer in Posix
      - Raghavendra Gowdappa added as Peer in FUSE Bridge,
        Maintainer of readdir-ahead
      - Nithya Added as peer in readdir-ahead
      - Hari Gowtham as Peer in Quota, Maintainer in Releases
      - Yaniv Kaul for xxhash
      - Rinku Kothiya added as Peer in releases.
      - Sheetal Pamecha and Shwetha Acharya added as Peers in
        packaging for Debian/Ubuntu and OpenSUSE.
    
    Updates: bz#1193929
    Change-Id: I0d6eccfee4306e26cdbc2b94f43ac493e2c25a61
    Signed-off-by: Amar Tumballi <amarts@gmail.com>

commit e3d97f57c8e25e8b44d3c96b09d69336ff6edb4b
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Nov 6 10:32:04 2019 +0530

    glusterd: Client Handling of Elastic Clusters
    
    Configure the list of gluster servers in the key
    GLUSTERD_BRICK_SERVERS at the time of GETSPEC RPC CALL
    and access the value in client side to update volfile
    serve list so that client would be able to connect
    next volfile server in case of current volfile server
    is down
    
    Updates #741
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    
    Change-Id: I23f36ddb92982bb02ffd83937a8bd8a2c97e8104

commit 50b6806bb2697246bdc1b9ac5ef19af61584e010
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Oct 22 15:06:29 2019 +0530

    cli: display detailed rebalance info
    
    Problem: When one of the node is down in cluster,
    rebalance status is not displaying detailed
    information.
    
    Cause: In glusterd_volume_rebalance_use_rsp_dict()
    we are aggregating rsp from all the nodes into a
    dictionary and sending it to cli for printing. While
    assigning a index to keys we are considering all the
    peers instead of considering only the peers which are
    up. Because of which, index is not reaching till 1.
    while parsing the rsp cli unable to find status-1
    key in dictionary and going out without printing
    any information.
    
    Solution: The simplest fix for this without much
    code change is to continue to look for other keys
    when status-1 key is not found.
    
    fixes: bz#1764119
    
    Change-Id: I0062839933c9706119eb85416256eade97e976dc
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 5304eaa662b263791baf0e5a9bd616446a3919ef
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Oct 28 18:42:41 2019 +0530

    posix: Improve MAKE_HANDLE_GFID_PATH and MAKE_HANDLE_RELPATH
    
    Avoid one function call to set the gfid_path in buffer
    
    Change-Id: If9b95801b05c34d262fac9a275492c794d12bf58
    Updates #748
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 54ed71dba174385ab0d8fa415e09262f6250430c
Author: l17zhou <cynthia.zhou@nokia-sbell.com.cn>
Date:   Mon Nov 4 08:45:52 2019 +0200

    rpc: Cleanup SSL specific data at the time of freeing rpc object
    
    Problem: At the time of cleanup rpc object ssl specific data
             is not freeing so it has become a leak.
    
    Solution: To avoid the leak cleanup ssl specific data at the
              time of cleanup rpc object
    
    Credits: l17zhou <cynthia.zhou@nokia-sbell.com.cn>
    Fixes: bz#1768407
    Change-Id: I37f598673ae2d7a33c75f39eb8843ccc6dffaaf0

commit 35d13c1e55e90f8da7d6edaeeab331a66aaf6bfd
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Sep 27 12:22:23 2019 +0300

    glusterfsd-mgmt: unify read and write tests
    
    1. Both read and write tests required writing first. Either just
    writing (write test) or write and then read (read test).
    So the code is now unified.
    2. There's no reason to read zeros from /dev/zero. Just use a
    CALLOC'ed buffer.
    I don't think we should read and write zeros, but I did not change
    the code yet (I think compression and/or dedup will offset results)
    
    It appears neither read-perf nor write-perf were tested, so added
    basic tests for them.
    
    Change-Id: I24b1f249fa0335ed652a8982e99c0687d940230e
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit ccf33e789f2cbd202e21340f684e2140d844a129
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Oct 9 21:27:54 2019 +0300

    dict.c: remove redundant checks
    
    It removes ~2% of the object size, and did not add meaningful checks
    whatsoever or to readability (IMHO).
    
    Change-Id: I54346c2af47dcab13bd8d5c8ad52fc765e6afad4
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 1de29634e5e74610570fe6f378a994bdf65c34cb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Oct 2 08:13:57 2019 +0300

    iobuf.c, h: minor fixes
    
    - Align structures
    - gf_iobuf_get_pagesize() will now also return the index, reducing the need
    for an additional very similar call.
    - Removal of an inefficient loop I've inadvertently added previously.
    It was harmless, but just inefficient.
    - New pool initialization does not need to be done under lock - no
    one can touch that pool yet, so no need to protect it.
    
    Change-Id: I61c50f2f14fa79edc131e515e9615a9928ee2dca
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 6b05f29808b187ce720c26e226be673b917ae668
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat Sep 21 00:00:07 2019 +0200

    extras: add statedumpparse.rb
    
    By default, the script mangles statedump records
    to JSON, which has two benefits:
    - easier machine processing
    - more friendly with line oriented tools, as one
      line will correspond to one record
    
    '--format=memstat' is also available which displays
    memory allocation types along the size of their allocations.
    
    Change-Id: I1685d3afcea6009fbcfafb33798f85bcd645c82f
    updates: bz#1193929
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 5c05bc7bcfc47dfb5ead3c07fa42311bf88091b6
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Jul 25 08:27:24 2019 +0200

    Improve logging of fusedump creation failure
    
    updates bz#1193929
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Change-Id: I12cbe1d87f60fb497654d0e13e12171940867f76

commit 0fc68040b72fc94dec3874345547e294b9ec1f45
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Oct 23 10:10:12 2019 +0530

    georep: Merge Worker and Agent as a single process
    
    - libgfchangelog is simplified by removing unnecessary API Class
    - Merged Agent logic into Worker instead of running Worker and Agent as
      two separate processes and maintaining RPC between Worker and Agent.
    - Geo-rep command Pause and Resume will continue without any changes.
      But Agent functionality also gets paused with that.
    
    Updates: #755
    Change-Id: Ie2c00fa7dddf21f180f0649e0aaf084d29023c98
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 0ab6c178468b6cce095c54ab62cfa51162d01fcc
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Oct 11 01:21:43 2019 +0300

    cloudsync: remove dead code, unused variable
    
    Minor changes - remove unused functions and unused variables.
    Switch dict functions to use sizen() when relevant.
    
    Change-Id: I737ce04a4beaf4df9b1eea25a90100d315627c14
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit b17a65dc2e3b4eca0ddd3caf46120f35ed4574b2
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Oct 20 09:12:20 2019 +0300

    posix-helpers.c (and others): minor changes to posix_xattr_fill()
    
    posix_xattr_fill() is called from several POSIX functions.
    Made minor changes to it and the functions called from it:
    1. Dict functions to use known lengths (dict_getn() instead of dict_get(), etc.)
    2. Re-ordered some static char[] arrays, to account (hopefully)
    to the frequency of the xattrs usage (based on grep in the code...)
    3. Before strcmp(), check if the strings lengths match.
    4. Removed some dead code.
    
    Hopefully, no functional changes.
    
    Change-Id: I510c0d2785e54ffe0f82c4c449782f2302d63a32
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 6c08e5b0ed2bfdd46064187ba39a30c91913fcd7
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Thu Oct 24 17:40:44 2019 +0530

    scripts: quota_fsck script TypeError: %d format:not dict
    
    Problem: One of the prints in the script have been using
    %i as the format for printing which doesn't work.
    
    Fix: use %s as the format in the place of %i
    
    Fixes: bz#1764129
    Change-Id: I4480ede7bf62906ddedbe5f880a1e89c76946641
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit 93e31716f11cb10d21f6fc59e8cdb6baed50865d
Author: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>
Date:   Fri Oct 18 12:22:13 2019 +0530

    barrier: structs re-alignment
    
    Re-aligned a struct and added manual padding to avoid compile time padding.
    
    Change-Id: I8c6fc67a1b635dc7d8e2522bd4fd8587c09f74e9
    Updates: bz#1754448
    Signed-off-by: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>

commit 28199dc009869858bcea108f116ce10c06358e03
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed May 22 17:36:11 2019 +0300

    dict.c: remove one strlen() done under lock.
    
    It's not needed in some cases, where we can pass the key length.
    
    Change-Id: I2e8ed0b69c50a35f5858bae7c1755a0dfd2c77e5
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 3ab23415804502b1ba89360c55ac3e8143822a0b
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Jul 11 16:52:49 2019 +0530

    cluster/ec: Change handling of heal failure to avoid crash
    
    Problem:
    ec_getxattr_heal_cbk was called with NULL as second argument
    in case heal was failing.
    This function was dereferencing "cookie" argument which caused crash.
    
    Solution:
    Cookie is changed to carry the value that was supposed to be
    stored in fop->data, so even in the case when fop is NULL in error
    case, there won't be any NULL dereference.
    
    Thanks to Xavi for the suggestion about the fix.
    
    Change-Id: I0798000d5cadb17c3c2fbfa1baf77033ffc2bb8c
    fixes: bz#1729085

commit 7a1c912a6b145cbf3b22884a7a6b2dfe16fb5de0
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Oct 31 18:13:16 2019 +0200

    posix-entry-ops.c: pass correct key length in posix_skip_non_linkto_unlink()
    
    As was found out in a different patch, passing a pointer
    to a constant string still calculates the size of the pointer
    and not the string. This is not catastrophic as the dictionary
    is matching not just hashes but key names, but is certainly what
    was intended to be done.
    Instead, pass explicitly the key lenth.
    
    I've looked for additional cases for such an issue and did not
    find them, luckily.
    
    Change-Id: I644a07a77dd541e9cf4886811ab54897e0c9d483
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 13cb14811cdea477780e58ba35493479c7a04a25
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Tue Oct 22 14:34:06 2019 +0530

    tests/shard: fix tests/bugs/shard/unlinks-and-renames.t failure
    
    on rhel8 machine cleanup of shards is not happening properly for a
    sharded file with hard-links. It needs to refresh the hard link count
    to make it successful
    
    The problem occurs when a sharded file with hard-links gets removed.
    When the last link file is removed, all shards need to be cleaned up.
    But in the current code structure shard xlator, instead of sending a lookup
    to get the link count uses stale cache values of inodectx. Therby removing
    the base shard but not the shards present in /.shard directory.
    
    This fix will make sure that it marks in the first unlink's callback that
    the inode ctx needs a refresh so that in the next operation, it will be
    refreshed by looking up the file on-disk.
    
    fixes: bz#1764110
    Change-Id: I81625c7451dabf006c0864d859b1600f3521b648
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 42c1605f42b89520d4d05806d7074e9e93b63640
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Jan 5 19:53:19 2017 +0530

    tools/glusterfind: handle offline bricks
    
    Problem:
    glusterfind is unable to copy remote output file to local node when a
    remove-brick is in progress on the remote node. After copying remote
    files, in the --full output listing path, a "sort -u" command is run on
    the collected files. However, "sort" exits with an error code if it
    finds any file missing.
    
    Solution:
    Maintain a map of (pid, output file) when the node commands are started
    and remove the mapping for the pid for which the command returns an
    error. Use the list of files present in the map for the "sort" command.
    
    Change-Id: Ie6e019037379f4cb163f24b1c65eb382efc2fb3b
    fixes: bz#1410439
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit f306a170e70fe9216dcc8e8bb943cf3704cca7d3
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 25 17:02:30 2019 +0530

    MAINTAINERS: Add Sunny Kumar as co-maintainer of geo-rep
    
    Change-Id: I774710273702f1d093601035435989d3caba449c
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    fixes: bz#1765542

commit f5a14b7aeef2055511de6a9f98e66ce527571ef6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Oct 23 09:19:19 2019 +0530

    MAINTAINERS: Add Sanju & Mohit as glusterd/cli maintainers
    
    Fixes: bz#1764418
    Change-Id: If14c5ce4527844df5251b4b5a720b617815fb1a1
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 593150979399f7f11e580591eab4b032bb0228ac
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Oct 16 13:06:29 2019 +0530

    afr: lock healing changes
    
    Implements lock healing for gluster-block fencing use case.
    
    If mandatory lock is enabled:
    - Add domain lock/unlock to afr_lk fop.
    - Maintain a list of locks to be healed in afr_private_t.
    - Add lock to the list if afr_lk(F_SETLK or F_SETLKW) was sucessful.
    - Remove it from the list during afr_lk(F_UNLCK).
    - On child_down, mark lock as needing heal on that child. If lock is
    lost on quorum no. of bricks, remove it from the list and mark fd bad.
    - For fds marked as bad, fail the subsequent fd based fops.
    - On parent up, traverse the list and heal the locks IFF the client is
    the lk owner and has quorum. (shd does not heal any locks).
    
    updates: #613
    Change-Id: I03c46ceaea30f5e6236d5ec13f71d843d827f1bc
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 9813ff934f43d09ecbd60b9f73c624b04b7dcc77
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Oct 24 17:58:03 2019 +0530

    cluster/afr: Take a copy of xattr-req
    
    Afr adds its own xattrs to the req, so it should take a copy of the
    dictionary to prevent parent xlator re-using the modified xattr-req
    to another subvolume
    
    fixes: bz#1765155
    Change-Id: I268e2dbd1b12323135d369e90a22a8bdde2cf7c2
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit ae6e11982fb7b6e21e2477dae2cecd9f89f50dfc
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Mon Oct 28 17:43:28 2019 +0800

    glusterd/ganesha: fix Coverity CID 1405785
    
    To avoid double free
    
    updates: bz#789278
    
    Change-Id: I15ae54ed696295d4cb015668722e77983b062ccb
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit b6da637929be0bdcdb00bf38fa4c14a8a09209d3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Oct 24 12:24:35 2019 +0530

    gf-event: Handle unix volfile-servers
    
    Problem:
    glfsheal program uses unix-socket-based volfile server.
    volfile server will be the path to socket in this case.
    gf_event expects this to be hostname in all cases. So getaddrinfo
    will fail on the unix-socket path, events won't be sent in this case.
    
    Fix:
    In case of unix sockets, default to localhost
    
    fixes: bz#1765017
    Change-Id: I60d27608792c29d83fb82beb5fde5ef4754bece8
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit f221ba83e11fced96b5a7b506e692358ed278ca2
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Oct 22 16:02:28 2019 +0530

    ssl/test: Change the rsa key length to 2048
    
    On a rhel-8 machine, we need to have a key length
    greater than or eaual to 2048. So changing the values
    to 2048 to pass the test.
    
    Credits: Mohit Agrawal <moagrawal@redhat.com>
    
    Change-Id: I0f21db4d737203d0b2e44e7e61f50ae1279795ad
    Updates: bz#1756900
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit f5811979935ce607391825ac6913a95f588818e3
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Oct 22 18:52:25 2019 +0530

    extras: Cgroup(CPU/Mem) restriction are not working on gluster process
    
    Problem: After Configure the Cgroup(CPU/MEM) limit to a gluster processes
             resource(CPU/MEM) limits are not applicable to the gluster
             processes.Cgroup limits are not applicable because all threads are
             not moved into a newly created cgroup to apply restriction.
    
    Solution: To move a gluster thread to newly created cgroup change the
              condition in script
    
    Change-Id: I8ad81c69200e4ec43a74f6052481551cf835354c
    Fixes: bz#1764208
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit bfebfa9f2ec9dfc5dbf4a68c3518f98364ebc461
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Oct 24 14:40:37 2019 +0530

    test: fix suspicous non-root geo-rep test failures
    
    Export of env variable is required for ssh-copy-id command.
    
    fixes: bz#1765426
    Change-Id: Icaf7a848cb8f4ae9f887d885a8c5bb71f26633b4
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 47465050c43f93294a3be27b4b0b1a3715a2c83d
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Thu Aug 8 11:46:46 2019 +0530

    Worm: xattr update on changing access time of a WORM-Retained file
    
    Retention-period must be updated on changing the access time
    of a worm-retained file. Retention-period must be changed in the
    "trusted.reten-state" xattr
    
    Change-Id: Ieab758a4cf6da3b4bb1d6a3e4f95f400c8a11f1d
    Fixes: bz#1554286

commit 4e9e2cc8f7990ab6deb661c5da98386cd3940d46
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Oct 22 15:11:03 2019 +0530

    Scripts: quota_fsck script KeyError: 'contri_size'
    
    Problem: In a certain code flow, we weren't handling the
    unavailability of the contri value in the dict. Trying to print
    without the value resulted in erroring out.
    
    Fix: Have printed the whole of dictionary as the values will be
    helpful in understanding the state of the file/dir
    
    Fixes: bz#1764129
    Change-Id: I99c538adb712f281ca10e4e0088f404f515b9725
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit faf5ac13c4ee00a05e9451bf8da3be2a9043bbf2
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Oct 3 14:06:52 2019 +0530

    rpc: Synchronize slot allocation code
    
    Problem: Current slot allocation/deallocation code path is not
             synchronized.There are scenario when due to race condition
             in slot allocation/deallocation code path brick is crashed.
    
    Solution: Synchronize slot allocation/deallocation code path to
              avoid the issue
    
    Change-Id: I4fb659a75234218ffa0e5e0bf9308f669f75fc25
    Fixes: bz#1763036
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit fb79786af4b7b6603a084c430b4542f806716dae
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sun Oct 20 01:01:39 2019 +0530

    geo-rep: Fix Permission denied traceback on non root setup
    
    Problem:
    While syncing rename of directory in hybrid crawl, geo-rep
    crashes as below.
    
    Traceback (most recent call last):
      File "/usr/local/libexec/glusterfs/python/syncdaemon/repce.py", line 118, in worker
        res = getattr(self.obj, rmeth)(*in_data[2:])
      File "/usr/local/libexec/glusterfs/python/syncdaemon/resource.py", line 588, in entry_ops
        src_entry = get_slv_dir_path(slv_host, slv_volume, gfid)
      File "/usr/local/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 687, in get_slv_dir_path
        [ENOENT], [ESTALE])
      File "/usr/local/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 546, in errno_wrap
        return call(*arg)
    PermissionError: [Errno 13] Permission denied: '/bricks/brick1/b1/.glusterfs/8e/c0/8ec0fcd4-d50f-4a6e-b473-a7943ab66640'
    
    Cause:
    Conversion of gfid to path for a directory uses readlink on backend
    .glusterfs gfid path. But this fails for non root user with
    permission denied.
    
    Fix:
    Use gfid2path interface to get the path from gfid
    
    Change-Id: I9d40c713a1b32cea95144cbc0f384ada82972222
    fixes: bz#1763439
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 61ba30df8c48586ffac957fa312ef7d244b6cdf0
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Oct 18 20:18:21 2019 +0300

    posix-entry-ops: do not copy when reading xattr
    
    The code is simplified to avoid needless copy as well as simplified
    overall for readability.
    Such changes are needed elsewhere too (see
    https://github.com/gluster/glusterfs/issues/720 )
    
    Few other minor changes here and there, nothing functional.
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I14f9dd2c32a8932bfcc80ebe92c9aa77701095ff

commit d923d3a67d2b306114dec993da7ee9c59d7d5482
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Oct 18 10:46:14 2019 +0300

    posix-helper.c: fix compile warn: ‘timeout’ may be used uninitialized
    
    https://review.gluster.org/#/c/glusterfs/+/23439/ introduced this warning:
    In file included from posix-helpers.c:50:
    posix-helpers.c: In function ‘posix_health_check_thread_proc’:
    ../../../../libglusterfs/src/glusterfs/events.h:31:9: warning: ‘timeout’ may be used uninitialized in this function [-Wmaybe-uninitialized]
       31 |         _gf_event(event, ##fmt);                                               \
          |         ^~~~~~~~~
    posix-helpers.c:2024:9: note: ‘timeout’ was declared here
     2024 |     int timeout;
    
    This patch fixes it, by re-setting the initial value to 0.
    
    Change-Id: I90aee4a1366e21a00f5e138f44247d8c42b0f5ae
    updates: bz#789278
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 105c7c5e7deaf9be29b81dc51f58dd5e5f8bd071
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Oct 16 23:26:03 2019 +0530

    glusterd: display correct rebalance data size after glusterd restart
    
    Problem: After completion of rebalance, if glusterd is restarted,
    rebalance status displays wrong rebalance data size in its output.
    
    Cause: While glusterd restoring the information from /var/lib/glusterd/
    into its memory, glusterd fetches rebalance_data from
    /var/lib/glusterd/vols/volname/node_state.info. This value is
    converted into an integer using atoi(), which is returning
    incorrect value for larger values.
    
    Solution: use sscanf() instead of atoi() to convert string to
    integer(in this case it is unsigned long)
    
    fixes: bz#1762438
    
    Change-Id: Icbdb096919612b4a1d6fb0e315f09d38900abf4e
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit b0ea2d10f7668f1d1076e06ec165230526d8b892
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Wed Oct 16 14:53:22 2019 +0530

    build: var data is saved under $prefix instead of localstatedir
    
    Problem:glusterfind saves var data under $prefix,
    even though the localstatedir is mentioned while installing i.e, when we
    install glusterfs with ./configure --prefix=/path/to/prefix
    --localstatedir=/path/to/var
    
    This happens because, glusterfind stores working dir as,
    working_dir=@GLUSTERFSD_MISCDIR@/glusterfind/
    and in configure.ac, GLUSTERFSD_MISCDIR is defined as:
    GLUSTERFSD_MISCDIR="$(eval echo $prefix)/var/lib/misc/glusterfsd"
    
    Solution: $localstatedir is used instead of $prefix while defining,
    GLUSTERFSD_MISCDIR to avoid such anomaly.
    
    fixes: bz#1489610
    Change-Id: I431a63c14bee23a1aac612a3dcb0431cb29ca4a2
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit f737a745b54c2dffe5e3e3203cea1eecf1c7ecf1
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Sep 13 21:27:44 2019 +0300

    rpc: align structs
    
    squash tens of warnings on padding of structs in afr structures.
    The warnings were found by manually added '-Wpadded' to the GCC
    command line.
    
    Also made relevant structs and definitions static, where it
    was applicable.
    
    Change-Id: Ib71a7e9c6179378f072d796d11172d086c343e53
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 739940667f4d7f32bd676ba1bea6b1f13426ae03
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Oct 16 14:25:47 2019 +0530

    geo-rep: Fix config upgrade on non-participating node
    
    After upgrade, if the config files are of old format, it
    gets migrated to new format. Monitor process migrates it.
    Since monitor doesn't run on nodes where bricks are not
    hosted, it doesn't get migrated there. So this patch fixes
    the config upgrade on nodes which doesn't host bricks.
    This happens during config either on get/set/reset.
    
    Change-Id: Ibade2f2310b0f3affea21a3baa1ae0eb71162cba
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    fixes: bz#1762220

commit 1695ece5d70305b4da03d21c3f721ce6d879e4d4
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Oct 10 21:59:59 2019 +0530

    tests: add tests for  bz#1758878
    
    updates: bz#1193929
    
    Change-Id: I517fa29e57bde970c2c22ebc2de80fec1509cd2d
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 1cb05730763d98f65c28246c8808217e6e9d6948
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Oct 14 10:29:31 2019 +0530

    tests: Fix spurious failure
    
    fixes: bz#1759002
    Change-Id: I4d49e1c2ca9b3c1d74b9dd5a30f1c66983a76529
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 9e7f5346910b337f87c10e7ae39eecf0bd829e01
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Oct 15 16:11:00 2019 +0530

    tests: Specify bs for dd
    
    On some distros default bs is very slow and the test takes
    close to 2 minutes instead of 20 seconds.
    
    fixes: bz#1761769
    Change-Id: If10d595a7ca05f053237f3c5ffbb09c5151eab35
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 06ed7dc11166975b80c35ec56d82a08b8686f6de
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Oct 15 15:29:48 2019 +0530

    tests: Remove hard-coding of lower bound
    
    Problem:
    Total blocks of XFS partition are dependent on XFS parameters used
    for formatting. So hardcoded lower-bound may not be the lower bound
    for different default parameters.
    
    Used blocks are lesser on my machine for a freshly formatted XFS partition
    compared to where the test fails.
    On my machine:
    Filesystem     1024-blocks  Used Available Capacity Mounted on
    /dev/loop0           98980  5472     93508       6% /d/backends/patchy1
    /dev/loop1           98980  5472     93508       6% /d/backends/patchy2
    
    On a machine where this test fails:
    Filesystem     1024-blocks  Used Available Capacity Mounted on
    /dev/loop0           96928  6112     90816       7% /d/backends/patchy1
    /dev/loop1           96928  6112     90816       7% /d/backends/patchy2
    
    Fix:
    Make lower bound 2% less than the brick-blocks available
    
    fixes: bz#1761759
    Change-Id: I974d5e75766f7ff44780a2e4c2a19cd5d1d14a79
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 9314a9fbf487614c736cf6c4c1b93078d37bb9df
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Oct 14 15:42:31 2019 +0530

    dht: Rebalance causing IO Error - File descriptor in bad state
    
    Problem : When a file is migrated, dht attempts to re-open all open
              fds on the new cached subvol. Earlier, if dht had not opened the fd,
              the client xlator would be unable to find the remote fd and would
              fall back to using an anon fd for the fop. That behavior changed with
              https://review.gluster.org/#/c/glusterfs/+/15804, causing fops to fail
              with EBADFD if the fd was not available on the cached subvol.
              The client xlator returns EBADFD if the remote fd is not found but
              dht only checks for EBADF before re-opening fds on the new cached subvol.
    
    Solution: Handle EBADFD at dht code path to avoid the issue
    
    Change-Id: I43c51995cdd48d05b12e4b2889c8dbe2bb2a72d8
    Fixes: bz#1758579

commit e3c3a3bc8805930b11e890baa99fc6e752e733f5
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Sep 18 21:14:40 2019 +0300

    posix-helpers.c: minor changes to posix_fs_health_check
    
    Do not sprintf the path in every invocation.
    Initialize parameters sooner.
    
    Change-Id: I26bfffc5dab6530937a50eee1e7fc4982e9b2a7c
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 03e1c3998f4f3b0ade7a0a84b72693da31a213c8
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Oct 14 18:16:21 2019 +0530

    tests: mark tests/bugs/glusterd/quorum-value-check.t as NFS test
    
    Fixes: bz#1665358
    
    Change-Id: Iea000dd839d4e4dbef45941f97ab3725a2aa1726
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit b55667cfd78c0d940a54a02bc8f47509ad43904b
Author: yatipadia <ypadia@redhat.com>
Date:   Fri Sep 13 13:52:38 2019 +0530

    glusterfsd: fix unused value coverity issues
    
    This patch addresses CID-1398624 and CID-1398631
    
    removed the unused variable brick_name
    
    Change-Id: I4f40bd76cb4c94b28589c2333e29d4623da339d0
    Updates: bz#789278
    Signed-off-by: yati <ypadia@redhat.com>

commit 2f43a1a4b567ec02ec03847b6eaec5ac59e68808
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Oct 10 09:37:24 2019 +0530

    cluster/afr: Add afr_seek to fops table
    
    fixes: bz#1760189
    Change-Id: Iffbf8d6f4c50b8e2de8364658697bdbe96549f5d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit c2279f50178be4408a72c04fbbfd6ccc70c50996
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Mon Sep 23 20:12:21 2019 +0530

    cli: raise error in cli when replica != 2 while ta vol creation
    
    When creating a thin-arbiter volume, if the replica-count
    provided is other than 2, the cli command
    fails(which is the expected behaviour) but it fails
    while transaction is being committed on localhost.
    This, ideally should be handled in cli itself.
    
    Change-Id: I52ecdaf49a7df85670505e4743cdcf3101c71c9f
    Signed-off-by: Vishal Pandey <vpandey@redhat.com>
    Fixes: bz#1754477

commit cdf34880e6788a396c8f02ba7e0263ea09d3676a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Sep 30 20:27:27 2019 +0300

    glusterd-volgen.c: fix setting the key export-dir
    
    The return value of gf_asprintf() was used as the key length,
    and it was stored into ret.
    ret was re-used before the dict function was called, therefore was invalid
    as the real key length and contained a different value.
    
    That was masked by the fact the key length was only used in key hash, so
    while it was incorrect, it was harmless. The hash was consistent and
    the key length was re-calculated anyway in dict_set_lk().
    
    This patch fixes it, so later on we can use the key length also in
    dict_set_lk() to save another strlen() (sent in a different patch).
    
    However, in the course of this patch I've also decided to reduce the
    copy-pasta in this code path and put all NFS options in an array
    and iterate through them. This makes the code shorter and easier to read.
    (It's also more efficient since once an entry was found, there's no
    additional strcmp()'s as the previous code did).
    
    Change-Id: I968ed50a55f3b1a7ad027c72b06e0fa3788eaa9b
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 704961a39ffd019487e36ac6dbd425399cb85cf2
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Oct 4 11:17:44 2019 +0300

    Multiple files: make root gfid a static variable
    
    In many places we use it, compare to it, etc. It could be a static variable,
    as it really doesn't change. I think it's better than initializing to 0
    and then doing gfid[15] = 1 or other tricks.
    
    I think there are additional oppportunuties to make more variables static.
    This is an attempt at an easy one.
    
    Change-Id: I7f23a30a94056d8f043645371ab841cbd0f90d19
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 240eec91c6ab5818c3fa4a9087ba46bbed0e8d2b
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Sep 13 09:20:33 2019 +0300

    afr: align structs
    
    squash >50 warnings on padding of structs in afr structures.
    The warnings were found by manually added '-Wpadded' to the GCC
    command line.
    
    Change-Id: I961fbdeb33715cedf3dd10db8e4f8ef40cd3e867
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d003ff64778b4d729cec417bfe8f56140806b07d
Author: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>
Date:   Mon Sep 23 15:36:16 2019 +0530

    glusterd: Re-alignment of structure attributes in glusterd.
    
    Structures defined in few files of glusterd src have been modified into
    memory efficient manner.
    
    Change-Id: Ie712b41cc74b04d5169bfd2402bff3b9c0d8c95b
    Updates: bz#1754448
    Signed-off-by: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>

commit 1004f959ca3b3697f2759f929ca4c11537f6c488
Author: yatipadia <ypadia@redhat.com>
Date:   Fri Oct 4 18:21:42 2019 +0530

    POSIX/xlators: Unused and unchecked value coverity issue
    
    This patch addresses CID-1274094 and CID-1382354
    
    Problem(1): "ret" was assigned a value which was never used,
    it was overwritten by 0 and hence has no use.
    
    Problem(2): function was called without checking the return value.
    
    Solution(1): Removed the assignment and just called the function
    whose value was being written in ret.
    
    Solution(2): There was no need to check for the return value as at
    the end 0 is returned, so typecasted the return value as void.
    
    Change-Id: Iefd0e9000c466ef2428c754c31370263bf1ca0d0
    updates: bz#789278

commit 332bac01dd15aaad53ba144c80edca551fe58e11
Author: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>
Date:   Thu Sep 12 19:50:35 2019 +0530

    Posix: UNUSED VALUE coverity fix
    
    This patch fixes Coverity issue with CID 1274206
    
    Problem : -1 is assigned to op_ret, but that stored value is overwritten before it can be used.
    
    Fix : Removal of the line that assigns -1 to op_ret which has no significance.
    
    Change-Id: Icb881549ac946003710551c9b9e88b33b6a06239
    Updates: bz#789278
    Signed-off-by: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>

commit 9dd57ff963d4d0dde7f3ad0ff230837ff2f4b1df
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Oct 10 10:50:59 2019 +0530

    performance/open-behind: seek fop should open_and_resume
    
    fixes: bz#1760187
    Change-Id: I4c6ad13194d4fc5c7705e35bf9a27fce504b51f9
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 134fcea8e245fd5033151392b6265d0dcc87a900
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Sep 19 20:22:56 2019 +0530

    performance/read-ahead: update expected offset before unwinding read response
    
    With the current code there is a window of time between unwinding
    response to a read request and internal offset is updated to account
    the read just done. If new sequential read request comes in this time
    window, it is incorrectly identified as non-sequential read.
    
    Fix is to update the file offset to account for a read request before
    sending back the response to it.
    
    Change-Id: Iff0c59c769e1eb15f262257763026657e2d4785d
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1753843

commit 3016bfa40ce33f89fbfffb564184576f08caf3d7
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sun Oct 6 19:05:28 2019 +0530

    cli: fix distCount value
    
    gluster volume info --xml id displaying wrong distCount
    value. This patch addresses it.
    
    fixes: bz#1758878
    
    Change-Id: I64081597e06018361e6524587b433b0c4b2a0260
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 9cfaef0960d206a554035000141935cc0fcf39e5
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Sep 11 17:53:39 2019 +0300

    client xlator: misc. cleanups
    
    - remove dead code
    - move functions to be static
    - move some code that only needs to be executed under if branch
    - remove some dead assignments and redundant checks.
    
    No functional change, I hope.
    
    Change-Id: I93d952408197ecd2fa91c3f812a73c54242342fa
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 0a9ca8162725b2f6b17a4d2e8cc863d27bb8770e
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Oct 9 00:25:42 2019 +0300

    dict.{c,h}: remove the lock from the _data struct
    
    I'm not sure why it was there and I did not see any use for it.
    In the hope I did not miss anything, I removed it.
    
    Change-Id: I02fa2e8e2a598b488fddbff4c7168dc4a41929b2
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 79f69d9b4f3c4fdf77dc77989447b6f1d5d5c658
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Oct 3 15:20:20 2019 +0300

    glusterd-utils.c: attach_brick() - remove dead code
    
    pidfile1 and pidfile2 were not used anywhere.
    Removed the assignment and the variables.
    
    Change-Id: Ic5fe091ba28bb500c370410a63440953048fd0b7
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit eae6f48859b81af32e1570e0b2d7a9033c74ac86
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Oct 5 00:20:49 2019 +0300

    posix-helpers.c: do not copy when reading xattr
    
    The code is simplified to avoid needless copy as well as simplified
    overall for readability.
    Such changes are needed elsewhere too (see
    https://github.com/gluster/glusterfs/issues/720 )
    
    Few other minor changes here and there, nothing functional.
    
    Change-Id: Ia1167849f54d9cacbfe32ddd712dc1699760daf5
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 83173908b3e3a02ebb6eb17963f0889c7ecff987
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Oct 10 20:40:49 2019 +0530

    glusterd: rebalance start should fail when quorum is not met
    
    rebalance start should not succeed if quorum is not met.
    this patch adds a condition to check whether quorum is met
    in pre-validation stage.
    
    fixes: bz#1760467
    Change-Id: Ic7d0d08f69e4bc6d5e7abae713ec1881531c8ad4
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f29e2e640849aee362d847c9994e0a29554dc527
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 9 10:26:39 2019 -0400

    packaging: remove leftover bd cruft in rpm .spec
    
    $subject
    
    Change-Id: Ifd8e3340ae6868ea1fd2d0b53f02b093cc23f2cb
    Fixes: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 31db2360b6076734f9506e17c4d2c93f7b6ee475
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Oct 7 12:27:01 2019 +0530

    Fix spurious failure in bug-1744548-heal-timeout.t
    
    Script was assuming that the heal would have triggered
    by the time test was executed, which may not be the case.
    It can lead to following failures when the race happens:
    
    ...
    18:29:45 not ok  14 [     85/      1] <  26> '[ 331 == 333 ]' -> ''
    ...
    18:29:45 not ok  16 [  10097/      1] <  33> '[ 668 == 666 ]' -> ''
    
    Heal on 3rd brick didn't start completely first time the command was executed.
    So the extra count got added to the next profile info.
    
    Fixed it by depending on cumulative stats and waiting until the count is
    satisfied using EXPECT_WITHIN
    
    fixes: bz#1759002
    Change-Id: I3b410671c902d6b1458a757fa245613cb29d967d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 8d17a94a65ac968b179afa718321105856610e63
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Sep 5 16:14:50 2019 +0530

    cluster/afr: Heal entries when there is a source & no healed_sinks
    
    Problem:
    In a situation where B1 blames B2, B2 blames B1 and B3 doesn't blame
    anything for entry heal, heal will not complete even though we have
    clear source and sinks. This will happen because while doing
    afr_selfheal_find_direction() only the bricks which are blamed by
    non-accused bricks are considered as sinks. Later in
    __afr_selfheal_entry_finalize_source() when it tries to mark all the
    non-sources as sinks it fails to do so because there won't be any
    healed_sinks marked, no witness present and there will be a source.
    
    Fix:
    If there is a source and no healed_sinks, then reset all the locked
    sources to 0 and healed sinks to 1 to do conservative merge.
    
    Change-Id: If40d8bc95d52a52b2730f55bdcf135109b421548
    Fixes: bz#1749322
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 65764a8910e02ed2564f92141f6ee735c39b8172
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Oct 7 16:59:20 2019 +0530

    tests: Fix spurious failure in bug-1134691-afr-lookup-metadata-heal.t
    
    Problem:
    The .t was examining the sink brick's iatt value before the launched
    client-side metadata heal got a chance to complete.
    
    Fix:
    Wait for heal completion.
    
    Fixes: bz#1759081
    Change-Id: I4dd4e3a1cccf35fd18e8cdfea6aa76a726a4763b
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 47dbd753187f69b3835d2e42fdbe7485874c4b3e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat Sep 28 08:53:08 2019 +0530

    afr: support split-brain CLI for replica 3
    
    Ever since we added quorum checks for lookups in afr via commit
    bd44d59741bb8c0f5d7a62c5b1094179dd0ce8a4, the split-brain resolution
    commands would not work for replica 3 because there would be no
    readables for the lookup fop.
    
    The argument was that split-brains do not occur in replica 3 but we do
    see (data/metadata) split-brain cases once in a while which indicate that there are
    a few bugs/corner cases yet to be discovered and fixed.
    
    Fortunately, commit  8016d51a3bbd410b0b927ed66be50a09574b7982 added
    GF_CLIENT_PID_GLFS_HEALD as the pid for all fops made by glfsheal. If we
    leverage this and allow lookups in afr when pid is GF_CLIENT_PID_GLFS_HEALD,
    split-brain resolution commands will work for replica 3 volumes too.
    
    Likewise, the check is added in shard_lookup as well to permit resolving
    split-brains by specifying "/.shard/shard-file.xx" as the file name
    (which previously used to fail with EPERM).
    
    Change-Id: I3c543dea79caf7cfbc1633e9089cb1cdd2538ba9
    Fixes: bz#1756938
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 41752a2f78a3a69fb8e3359906b7132457ca9acc
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Sep 11 14:57:29 2019 +0530

    extras: Enable direct-io options in group virt
    
    Direct-io options are currently enabled in the ovirt-gluster
    installation through cockpit ui whereas all the other optimizations in
    gluster for virt are enabled through the group-virt option using
    'volume-set' command. For the sake of completeness and to avoid any
    confusion, it would be better to set the o-direct gluster options also
    as part of group virt.
    
    Change-Id: Iac4c443c2a8239effeb05a52344e563f1d877916
    Fixes: bz#1758984
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit b3df5abbb7ab4d0f5015da9e4d5ecea79eed9b98
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Sep 19 20:52:46 2019 +0300

    afr: replace afr_frame_return() when possible with direct call
    
    If you are already under lock, just decrement the call count
    directly instead of removing the lock, re-taking the lock
    and decrementing.
    
    Implements https://github.com/gluster/glusterfs/issues/728
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I3fa20b4651fbdb826655c5a03baeed46e99b5487

commit f2404405432cfc7c2369de02f79eee000b9aee13
Author: yatipadia <ypadia@redhat.com>
Date:   Mon Sep 16 14:45:12 2019 +0530

    xlators: fixes logically dead code.
    
    This patch addresses CID-1124388.
    
    Problem: When we reach the "out" section in ra_priv_dump(), if the condition
    (ret && conf) holds true, then the value of "add_section" will always be true.
    So the condition  (add_section == _gf_false) will be a dead code.
    
    Fix:"add_section" has no use in the whole block and was making part of the
    block as logically dead code and hence, removed it.
    
    Change-Id: Id7e0105fc9a5ca5b2c2d098c665e6e32ecc6b62b
    updates: bz#789278
    Signed-off-by: yatipadia <ypadia@redhat.com>

commit da331e1e5a04650d340509b4d4de8f20aea0712d
Author: Amar Tumballi <amarts@gmail.com>
Date:   Tue Oct 1 15:49:18 2019 +0530

    tests: add a pending test case
    
    While merging the protocol handshake fixes (bz#1620580), there was
    a case which was left out. Adding it separately now.
    
    Change-Id: I52133d5fe160b4567400a65e60aac8f7bc20697f
    Updates: bz#1193929
    Signed-off-by: Amar Tumballi <amarts@gmail.com>

commit 9b15867070b0cc241ab165886292ecffc3bc0aed
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Oct 1 17:37:15 2019 +0530

    cluster/dht: Correct fd processing loop
    
    The fd processing loops in the
    dht_migration_complete_check_task and the
    dht_rebalance_inprogress_task functions were unsafe
    and could cause an open to be sent on an already freed
    fd. This has been fixed.
    
    Change-Id: I0a3c7d2fba314089e03dfd704f9dceb134749540
    Fixes: bz#1757399
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 36075d4de78cb562b0e7a8bea85c868251f0e961
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Wed Jan 24 16:06:08 2018 +0800

    rpc: fix missing unref on reconnect
    
    On protocol client connecting to brick, client will firstly contact
    glusterd to get port, then reconnect to glusterfsd. Reconnect cancels
    the reconnect timer and start a new one. However, cancelling the timer
    does not unref rpc ref-ed for it. That leads to refcount leak.
    
    Fix this issue by unref-ing rpc if reconnect timer is canceled.
    
    Change-Id: Ice89dcd93cb283a0c7250c369cc8961d52fb2022
    Fixes: bz#1538900
    BUG: 1538900
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 69aeede2480ff429d1c3c466a79d85fca756b198
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Sep 30 13:14:06 2019 +0530

    ssl: fix RHEL8 regression failure
    
    This tests is failing with
    "SSL routines:SSL_CTX_use_certificate:ee key too small"
    in RHEL8. This change is made according to
    https://access.redhat.com/solutions/4157431
    
    updates: bz#1756900
    
    Change-Id: Ib436372c3bd94bcf7324976337add7da4088b3d5
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 341aab0fbbde0b9867bf8741791afec9354f54d8
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Sep 26 20:07:11 2019 +0530

    glusterd: improve logging
    
    updates: bz#1193929
    
    Change-Id: I5b4a39fbdaa43642a322440d550ca24df815cae9
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 7464ece4b97935b8085ac456a452b697db3bf67e
Author: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>
Date:   Mon Sep 16 11:05:23 2019 +0530

    libgfapi : Dereference after null check - coverity fix
    
    This patch fixes coverity issue with CID 1405581
    
    A pointer 'volname' is being deferenced (by passing it as an argument to strncmp), even when it points to NULL, leading to segmentation fault.
    
    fix : Adding a NULL check condition beforehand and returning NULL
    
    Change-Id: I18685fa1cb251253996051b83b6790a5d5f0aff9
    Updates: bz#789278
    Signed-off-by: Purna Pavan Chandra Aekkaladevi <paekkala@redhat.com>

commit ae729065c0d9cb5411e5c31231b5e293b560d76a
Author: Amar Tumballi <amarts@gmail.com>
Date:   Tue Aug 6 23:20:02 2019 +0300

    protocol/handshake: pass volume-id for extra check
    
    With added check of volume-id during handshake, we can be sure to not
    connect with a brick if this gets re-used in another volume. This
    prevents any accidental issues which can happen with a stale client
    process lurking along.
    
    Also added test case for testing same volume name which would fetch a
    different volfile (ie, different bricks, different type), and a
    different volume name, but same brick.
    
    For reference:
    Currently a client<->server handshake happens in glusterfs through
    protocol/client translator (setvolume) to protocol/server using a
    dictionary which containes many keys. Rejection happens in server
    side if some of the required keys are missing in handshake
    dictionary.
    
    Till now, there was no single unique identifier to validate for a
    client to tell server if it is actually talking to a corresponding
    server. All we look in protocol/client is a key called
    'remote-subvolume', which should match with a subvolume name in server
    volume file, and for any volume with same brick name (can be present
    in same cluster due to recreate), it would be same. This could cause
    major issue, when a client was connected to a given brick, in one
    volume would be connected to another volume's brick if its
    re-created/re-used.
    
    To prevent this behavior, we are now passing along 'volume-id' in
    handshake, which would be preserved for the life of client process,
    which can prevent this accidental connections.
    
    NOTE: This behavior wouldn't be applicable for user-snapshot enabled
    volumes, as snapshotted volume's would have different volume-id.
    
    Fixes: bz#1620580
    Change-Id: Ie98286e94ce95ae09c2135fd6ec7d7c2ca1e8095
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c6df9e962483bac5bfcd8916318b19040387ce81
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Sep 26 17:52:30 2019 +0530

    posix: heketidbstorage bricks go down during PVC creation
    
    Problem: In OCS environment heketidbstorage is detached due
             to health_check thread is failed.Sometime aio_write
             is not successfully finished within default health-check-timeout
             limit and the brick is detached.
    
    Solution: To avoid the issue increase default timeout to 20s
    
    Change-Id: Idff283d5713da571f9d20a6b296274f69c3e5b7b
    Fixes: bz#1755900
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 257bb3d16b30e60116724e9e906f8d3ecddf313e
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Sep 18 16:32:08 2019 +0530

    gfapi: Update the version of 'glfs_h_creat_open'
    
    Change-Id: I43eaa53a7b8d876640d225e011b56192bba57eed
    Fixes: bz#1753569
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 227713229a7bba19426186f1615fd891e4e52bb7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Sep 27 10:52:05 2019 +0530

    tests/shard: Remove dependence on distributed cache
    
    fixes: bz#1756211
    Change-Id: Iee5b37af89ab624c16a45df364806003238280e5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 74e810c602a40d6c316f111cc1333c13bd5aec08
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 10 19:06:54 2019 +0530

    cluster/ec: Implement read-mask feature
    
    fixes: #725
    Change-Id: Iaaefe6f49c8193c476b987b92df6bab3e2f62601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 61f768eddecc52eb1ba44169526dd674864d0aa1
Author: Xavi Hernandez <jahernan@redhat.com>
Date:   Wed Sep 25 11:56:35 2019 +0200

    cluster/ec: prevent filling shd log with "table not found" messages
    
    When self-heal daemon receives an inodelk contention notification, it tries
    to locate the related inode using inode_find() and the inode table owned by
    top-most xlator, which in this case doesn't have any inode table. This causes
    many messages to be logged by inode_find() function because the inode table
    passed is NULL.
    
    This patch prevents this by making sure the inode table is not NULL before
    calling inode_find().
    
    Change-Id: I8d001bd180aaaf1521ba40a536b097fcf70c991f
    Fixes: bz#1755344
    Signed-off-by: Xavi Hernandez <jahernan@redhat.com>

commit 80cb838773f3574f68b1fa821fcb712ada350309
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Tue Feb 12 18:33:44 2019 +0530

    read-ahead/io-cache: turn off by default
    
    We've found perf xlators io-cache and read-ahead not adding any
    performance improvement. At best read-ahead is redundant due to kernel
    read-ahead and at worst io-cache is degrading the performance for
    workloads that doesn't involve re-read. Given that VFS already have
    both these functionalities, this patch makes these two
    translators turned off by default for native fuse mounts.
    
    For non-native fuse mounts like gfapi (NFS-ganesha/samba) we can have
    these xlators on by having custom profiles.
    
    Change-Id: Ie7535788909d4c741844473696f001274dc0bb60
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    fixes: bz#1676479

commit c4d926900dc36f71c04b3f65ceca5150ce0e8c81
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Sep 18 19:11:33 2019 +0530

    posix: Brick is going down unexpectedly
    
    Problem: In brick_mux environment, while multiple volumes are
             created (1-1000) sometimes brick is going down due to
             health_check thread failure
    
    Solution: Ignore EAGAIN error in health_check thread code to
              avoid the issue
    
    Change-Id: Id44c59f8e071a363a14d09d188813a6633855213
    Fixes: bz#1751907
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 0c2d25956b022cb61f0b62873c97b7346ef7c4c3
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Sep 25 19:50:27 2019 +0530

    perf/write-behind: Clear frame->local on conflict error
    
    WB saves the wb_inode in frame->local for the truncate and
    ftruncate fops. This value is not cleared in case of error
    on a conflicting write request. FRAME_DESTROY finds a non-null
    frame->local and tries to free it using mem_put. However,
    wb_inode is allocated using GF_CALLOC, causing the
    process to crash.
    
    credit: vpolakis@gmail.com
    
    Change-Id: I217f61470445775e05145aebe44c814731c1b8c5
    Fixes: bz#1753592
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 41a0f2aa755ec7162facd30209f2fa3f40308766
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Sep 18 16:32:08 2019 +0530

    gfapi: 'glfs_h_creat_open' - new API to create handle and open fd
    
    Right now we have two separate APIs, one
    - 'glfs_h_creat_handle' to create handle & another
    - 'glfs_h_open' to create a glfd to return to application
    
    Having two separate routines can result in access errors
    while trying to create and write into a read-only file.
    
    Since a fd is opened even during file/directory creation,
    introducing a new API to make these two operations atomic i.e,
    which can create both handle & fd and pass them to application
    
    Change-Id: Ibf513fcfcdad175f4d7eb6fa7a61b8feec6d33b5
    Fixes: bz#1753569
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 5677b85a59ec98dbe8c99680308403f56d3ce014
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Sep 24 18:22:13 2019 +0530

    tests : test case for non-root geo-rep setup
    
    Added test case for non-root geo-rep setup.
    
    Change-Id: Ib6ebee79949a9f61bdc5c7b5e11b51b262750e98
    fixes: bz#1717827
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 74bbad1e73b9b024a666bf5e0fc68465ff0afbdd
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Sep 20 13:30:42 2019 +0530

    glusterfs/fuse: Reduce the default lru-limit value
    
    The current lru-limit value still uses memory for
    upto 128K inodes.
    Reduce the default value of lru-limit to 64K.
    
    Change-Id: Ica2dd4f8f5fde45cb5180d8f02c3d86114ac52b3
    Fixes: bz#1753880
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e15ca15d7cd39d913d9276f93d7ffd2dd7b85611
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Fri Aug 16 11:37:40 2019 +0530

    geo-rep: Fix spelling errors
    
    Fixes: bz#1741779
    Change-Id: I708b6b7e6c520dee10445528e6f99ba38e141c25
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit a4900e490c444cf88b202d6925d3ca3a06ad0355
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Sat Sep 21 01:07:30 2019 +0530

    geo-rep : fix sub-command during worker connection
    
    Problem:
    
    Geo-rep session for non-root going faulty.
    
    Solution:
    
    During worker start we do not construct slave url and use 'args.resource_remote'
    which is basically just slave-hostname.
    This works better for root session but fails in non-root session during
    ssh command.
    Using slave url solves this issue.
    
    fixes: bz#1753928
    Change-Id: Ib83552fde77f81c208896494b323514ab37ebf22
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 9fa05e11b802ddd03825bbe54968e0937878f2b7
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Aug 26 11:32:18 2019 +0530

    glusterd/ganesha: fixing resource leak in tear_down_cluster()
    
    CID: 1370947
    Updates: bz#789278
    
    Change-Id: Ib694056430ff0536ed705a0e77e5ace22486891e
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 30d3608c43be119f75da7798d88b94601dedcb29
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Sep 20 09:39:12 2019 +0530

    geo-rep: performance improvement while syncing renames with existing gfid
    
    Problem:
    The bug[1] addresses issue of data inconsistency when handling RENAME with
    existing destination. This fix requires some performance tuning considering
    this issue occurs in heavy rename workload.
    
    Solution:
    If distribution count for master volume is one do not verify op's on
    master and go ahead with rename.
    
    The performance improvement with this patch can only be observed if
    master volume has distribution count one.
    
    [1]. https://bugzilla.redhat.com/show_bug.cgi?id=1694820
    
    fixes: bz#1753857
    Change-Id: I8e9bcd575e7e35f40f9f78b7961c92dee642f47b
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit d654dfa526457dc991ebef66fdecda8f0aac529b
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Sep 20 11:30:45 2019 +0530

    mgmt/glusterd: Fixed typos and reworded logs
    
    Fixed typos and reworded log messages for clarity.
    
    Change-Id: I46f616ce7d3eb993c77a5812e8bc044e5f283354
    Fixes: bz#1753859
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit c7968f601a7cd4f54103f63d8db1f1a268c0ec5b
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Sep 12 15:19:09 2019 +0300

    afr-common.c, afr-self-heal.h: calloc/alloca0 -> malloc/alloca
    
    In 3 cases, there was a memory allocation and zeroing, followed
    directly by populating it with content. Replaced with memory
    allocation that did not zero the memory.
    
    Change-Id: I4fbb5c924fb3a144e415d2368126b784dde760ea
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 1088301998d4feabc4285fc6298c08e19a2a558d
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Wed Jul 10 18:39:51 2019 +0530

    [geo-rep] Improving help message for gluster-mountbroker
    
    The arguments for gluster-mountbroker is missing help="< Some Text>"
    parameter wherever add_argument() is used due to which gluster-mountbroker
    help is missing  a brief description of what the argument does in the help
    of {add,setup,remove} as shown below:
    
    usage: gluster-mountbroker remove [-h] [--volume VOLUME] [--user USER]
    
    optional arguments:
      -h, --help       show this help message and exit
      --volume VOLUME
      --user USER
    usage: gluster-mountbroker add [-h] volume user
    
    positional arguments:
      volume
      user
    
    optional arguments:
      -h, --help  show this help message and exit
    usage: gluster-mountbroker setup [-h] mount_root group
    
    positional arguments:
      mount_root
      group
    
    optional arguments:
      -h, --help  show this help message and exit
    
    fixes: bz#1728683
    
    Change-Id: I7eabcd2c103f01e40160ba35500b0a4e5c9f5e7a
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit d9ad59c0cdda160aaef6995cce387961ce8939ce
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Sep 17 15:35:21 2019 +0530

    posix/ctime: Fix coverity issue
    
    posix-metadata.c: 462 in posix_set_mdata_xattr()
    ...
    460         GF_VALIDATE_OR_GOTO(this->name, time, out);
    461
    >>>     CID 1405665:  Control flow issues  (DEADCODE)
    >>>     Execution cannot reach the expression "flag->atime" inside this
    >>>     statement: "if (update_utime && (flag->...".
    462         if (update_utime && (flag->ctime && !time) && (flag->atime && !u_atime) &&
    
    Change-Id: Id31d81d04ea2785a669eafe0dc1307303cb2271b
    updates: bz#789278
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 962548166aa68fbf4ac8ef6bdc97657be742e1c5
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 27 16:35:05 2019 +0530

    cluster/dht: Handle file truncates during migration
    
    File truncate operations during a migration were not handled properly.
    This has been fixed.
    
    Change-Id: Ic642d257e893641236a4a21ab69fcc7a569dd70a
    Fixes: bz#1745967
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit fc10f370289e32da6753ac9a9a529b60abb16c4d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Sep 16 10:04:26 2019 +0530

    eventsapi: Set IPv4/IPv6 family based on input IP
    
    server.sin_family was set to AF_INET while creating socket connection,
    this was failing if the input address is IPv6(`::1`).
    
    With this patch, sin_family is set by reading the ai_family of
    `getaddrinfo` result.
    
    Fixes: bz#1752330
    Change-Id: I499f957b432842fa989c698f6e5b25b7016084eb
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 304640e55c0f3c6d15f4e230dc6376e4f5020fea
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jul 29 18:30:42 2019 +0530

    ctime/rebalance: Heal ctime xattr on directory during rebalance
    
    After add-brick and rebalance, the ctime xattr is not present
    on rebalanced directories on new brick. This patch fixes the
    same.
    
    Note that ctime still doesn't support consistent time across
    distribute sub-volume.
    
    This patch also fixes the in-memory inconsistency of time attributes
    when metadata is self healed.
    
    Change-Id: Ia20506f1839021bf61d4753191e7dc34b31bb2df
    fixes: bz#1734026
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit bcd71806b4066b413ee8c3e5a252c1866c9a7e97
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Sep 7 11:28:58 2019 +0300

    logging.c: check for log level before checking for args.
    
    In many cases, we will not be logging at all, since the log level
    is irrelevant. In that case, we can just bail out.
    Worth doing this check before the args check, which may not be needed
    in this case.
    
    Change-Id: Ia90a38bb2a49b09bfea5b5abc8b5d0c3bab4e9ac
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 0214c32954fcb9384a074c0cfc9e40252a19852e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Sep 13 15:35:16 2019 +0530

    tests/shd: Mark "tests/basic/volume-scale-shd-mux.t" as bad
    
    This test case is failing in upstream. Marking this test as
    bad for now.
    
    Change-Id: I014c67628c14683c32a3c1dd770b10aaf35ad4cc
    Updates: bz#1752331
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 59f3c790048c9036adb81d56329a66fc3ffb255a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon May 13 12:54:52 2019 +0530

    protocol/client: don't reopen fds on which POSIX locks are held after a reconnect
    
    Bricks cleanup any granted locks after a client disconnects and
    currently these locks are not healed after a reconnect. This means
    post reconnect a competing process could be granted a lock even though
    the first process which was granted locks has not unlocked. By not
    re-opening fds, subsequent operations on such fds will fail forcing
    the application to close the current fd and reopen a new one. This way
    we prevent any silent corruption.
    
    A new option "client.strict-locks" is introduced to control this
    behaviour. This option is set to "off" by default.
    
    Change-Id: Ieed545efea466cb5e8f5a36199aa26380c301b9e
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    updates: bz#1694920

commit 61d438e73857776a1f96a7334f56b132275a587b
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Mon Aug 19 15:27:57 2019 +0530

    libgfapi: return correct errno on invalid volume name
    
    glfs_init when called with volume name prefixed by '/'
    sets errno to 0. Setting errno to EINVAL to resolve the issue.
    Also volname is a parameter to glfs_new.
    Thus, validating volname in glfs_new itself and
    returning EINVAL from that function
    
    fixes: bz#1507896
    
    Change-Id: I0d4d2423e26cc07644d50ec8cce788ecc639203d
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit da76f7bbef4d311775a5f75c96a54785170a1727
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Sep 3 20:52:42 2019 +0530

    core/syncop: Bail out if frame creation fails
    
    There could be cases (either due to insufficient memory or
    corrupted mem-pool) due to which frame creation fails. Bail out
    with error in such cases.
    
    Change-Id: I8cc0a5852f6f04d2bac991e4eb79ecb42577da11
    Fixes: bz#1748448
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 5091a482125eeac3b00915888cf3de775cd3cbbc
Author: Sheetal <spamecha@redhat.com>
Date:   Mon Sep 9 22:56:34 2019 +0530

    api: Cleanup of executable not done
    
    In test tests/bugs/gfapi/bug-1447266/bug-1447266.t
    actual file created is -
    tests/bugs/gfapi/bug-1447266/bug-1447266
    which is not cleaned up later
    
    fixes: bz#1750618
    Change-Id: I93120418e54b95018a7213d106a1f1c990766281
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 6362999974cc4b55c4c42929b22a2f2f53321699
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Aug 20 13:27:24 2019 +0530

    cluster/ec: Mark release only when it is acquired
    
    Problem:
    Mount-1                                Mount-2
    1)Tries to acquire lock on 'dir1'   1)Tries to acquire lock on 'dir1'
    2)Lock is granted on brick-0        2)Lock gets EAGAIN on brick-0 and
    				      leads to blocking lock on brick-0
    3)Gets a lock-contention            3) Doesn't matter what happens on mount-2
      notification, marks lock->release    from here on.
      to true.
    4)New fop comes on 'dir1' which will
      be put in frozen list as lock->release
      is set to true.
    5) Lock acquisition from step-2 fails because
    3 bricks went down in 4+2 setup.
    
    Fop on mount-1 which is put in frozen list will hang because no codepath will
    move it from frozen list to any other list and the lock will not be retried.
    
    Fix:
    Don't set lock->release to true if lock is not acquired at the time of
    lock-contention-notification
    
    fixes: bz#1743573
    Change-Id: Ie6630db8735ccf372cc54b873a3a3aed7a6082b7
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 880e20ca967d0001e0b6d2780bece8b635a090eb
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jul 5 09:09:44 2019 +0530

    tests: revive back volume-scale-shd-mux.t
    
    Fixes: bz#1708929
    Change-Id: I9cc81a9047ff874df752ca5552e00bf033485bd8
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 0e37cdf271a48d3e58c212e95664a2aa34da3940
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Sep 11 14:41:28 2019 +0530

    tests: Fix spurious failure
    
    If heal from next brick starts after the first brick completes heal, then
    opendir on the brick can change atime leading to failure of the test. When
    ctime is disabled it is better to just check mtime to be same after heal.
    
    fixes: bz#1751134
    Change-Id: Ia03e30fd547e6bbe85c1e299845ffa122f3a2692
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 0af88a6c33e8fd57745997afb7c68e4ef6023fbf
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Sep 9 10:01:04 2019 +0530

    glusterd, rpc, glusterfsd: fix coverity defects and put required annotations
    
    1404965 - Null pointer dereference
    1404316 - Program hangs
    1401715 - Program hangs
    1401713 - Program hangs
    
    Updates: bz#789278
    Change-Id: I6e6575daafcb067bc910445f82a9d564f43b75a2
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit ea95631ff47c8048f039faedbc0faa918c4e165a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Sep 5 16:12:39 2019 +0530

    cluster/ec: quorum-count implementation
    
    fixes: #721
    Change-Id: I5333540e3c635ccf441cf1f4696e4c8986e38ea8
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 6bf09ecbe8203d0f8c020e6b0b55202e91e216c9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Sep 7 20:18:01 2019 +0530

    cluster/ec: Fix coverity issues
    
    Fixed the following coverity issue in both flush/fsync
    >>>     CID 1404964:  Null pointer dereferences  (REVERSE_INULL)
    >>>     Null-checking "fd" suggests that it may be null, but it has already
    been dereferenced on all paths leading to the check.
    >>>         if (fd != NULL) {
    >>>           fop->fd = fd_ref(fd);
    >>>             if (fop->fd == NULL) {
    >>>                 gf_msg(this->name, GF_LOG_ERROR, 0,
    >>>                        "Failed to reference a "
    >>>                        "file descriptor.");
    
    fixes bz#1748836
    Change-Id: I19c05d585e23f8fbfbc195d1f3775ec528eed671
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 7b3971ad0152eb1bb89a982333970118a6bd4922
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Sep 4 12:06:34 2019 +0530

    cluster/ec: Fail fsync/flush for files on update size/version failure
    
    Problem:
    If update size/version is not successful on the file, updates on the
    same stripe could lead to data corruptions if the earlier un-aligned
    write is not successful on all the bricks. Application won't have
    any knowledge of this because update size/version happens in the
    background.
    
    Fix:
    Fail fsync/flush on fds that are opened before update-size-version
    went bad.
    
    fixes: bz#1748836
    Change-Id: I9d323eddcda703bd27d55f340c4079d76e06e492
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 6563ffb04d7ba51a89726e7c5bbb85c7dbc685b5
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Sep 2 10:46:10 2019 +0530

    glusterd: IPV6 hostname address is not parsed correctly
    
    Problem: IPV6 hostname address is not parsed correctly in function
             glusterd_check_brick_order
    
    Solution: Update the code to parse hostname address
    
    Change-Id: Ifb2f83f9c6e987b2292070e048e97eeb51b728ab
    Fixes: bz#1747746
    Credits: Amgad Saleh <amgad.saleh@nokia.com>
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 66bf17321655225d1096da4f2b5270f02afd102d
Author: Amar Tumballi <amarts@gmail.com>
Date:   Tue Sep 3 11:32:39 2019 +0530

    rpc/xdr: fixes in Makefile
    
    there is no need to cleanup the .x files.
    
    Fixes: bz#1743094
    Change-Id: I89d8deb3939c83069709c701cb8f1972e3746168
    Signed-off-by: Amar Tumballi <amarts@gmail.com>

commit 43635716e6bd5bd5925fa9194b0853ee919a742d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Jul 5 20:12:59 2019 +0530

    graph/cleanup: Fix race in graph cleanup
    
    We were unconditionally cleaning up the grap when we get
    child_down followed by parent_down. But this is prone to
    race condition when some of the bricks are already disconnected.
    In this case, even before the last child down is executed in the
    client xlator code,we might have freed the graph. Because the
    child_down event is alreadt recevied.
    
    To fix this race, we have introduced a check to see if all client
    xlator have cleared thier reconnect chain, and called the child_down
    for last time.
    
    Change-Id: I7d02813bc366dac733a836e0cd7b14a6fac52042
    fixes: bz#1727329
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit d026f0bcfd301712e4f0671ccf238f43f2e6dd30
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Jul 10 21:44:38 2019 +0530

    afr/lookup: Pass xattr_req in while doing a selfheal in lookup
    
    We were not passing xattr_req when doing a name self heal
    as well as a meta data heal. Because of this, some xdata
    was missing which causes i/o errors
    
    Change-Id: Ibfb1205a7eb0195632dc3820116ffbbb8043545f
    Fixes: bz#1728770
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit f6d6c0f65f7b512724694b3436358e1113cbfccb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 28 19:38:01 2019 +0300

    posix*.c: remove unneeded strlen() calls
    
    In various places, we can re-use knowledge of string length
    or result of snprintf() and such instead of strlen().
    
    Change-Id: I4c9b1decf1169b3f8ac83699a0afbd7c38fad746
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit ee24c0438ce40b0c6faf6581fd4eb162767d8a90
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Aug 30 10:21:33 2019 +0300

    glusterd-store.c: remove of dead code
    
    These functions do not seem to be in use.
    
    Change-Id: Ie76baf2a9727b9ba0e66f234226b1e62788245f2
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit b0dbe11556c17ba6ea0b7d85b741bd4807c81c9c
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Mon Sep 2 18:43:36 2019 +0530

    [Doc] Fixing 404 links in markdown files.
    
    Problem:
    While running markdown-link-checker it was
    observed that there were a large number of
    404 links present in the documentation present
    in the form of markdown files in the project.
    
    This was casued due to the following reasons:
    1. Repos being removed.
    2. Typo in markdown links.
    3. Restructring of directoires.
    
    Solution:
    Fixing all the 404 links present in the project.
    
    fixes: bz#1746810
    Change-Id: I30de745f848fca2e9c92eb7493f74738f0890ed9
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit 724c657995a2e148243eeb78c68b620c6d7714a5
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Sep 4 11:27:30 2019 +0530

    tests: fix spurious failure of bug-1402841.t-mt-dir-scan-race.t
    
    Problem:
    Since commit 600ba94183333c4af9b4a09616690994fd528478, shd starts
    healing as soon as it is toggled from disabled to enabled. This was
    causing the following line in the .t to fail on a 'fast' machine (always
    on my laptop and sometimes on the jenkins slaves).
    
    EXPECT_NOT "^0$" get_pending_heal_count $V0
    
    because by the time shd was disabled, the heal was already completed.
    
    Fix:
    Increase the no. of files to be healed and make it a variable called
    FILE_COUNT, should we need to bump it up further because the machines
    become even faster. Also created pending metadata heals to increase the
    time taken to heal a file.
    
    fixes: bz#1748744
    Change-Id: I5a26b08e45b8c19bce3c01ce67bdcc28ed48198d
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 80b8cfe3f1386606bada97a76a0cad7acdf6b877
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Sun Sep 1 12:01:09 2019 +0530

    rpc: Update address family if it is not provide in cmd-line arguments
    
    Problem: After enabling transport-type to inet6 and passed ipv6
             transport.socket.bind-address in glusterd.vol clients are
             not started.
    
    Solution: Need to update address-family based on remote-address for
              all gluster client process
    
    Change-Id: Iaa3588cd87cebc45231bfd675745c1a457dc9b31
    Fixes: bz#1747746
    Credits: Amgad Saleh <amgad.saleh@nokia.com>
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a498c478109395e7baa9b029c81d5587254bdd89
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Aug 28 11:55:17 2019 +0530

    debug/error-gen: Set count correctly for short-writes
    
    vector count is reduced to 1 but it is not reflected at the time of
    winding the call. This leads to crash when short-writes are done
    using error-gen. Set the correct count to fix the problem.
    
    fixes: bz#1746320
    Change-Id: I037b60b7e321f2f50b71fb52c43c64707cf114ca
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 7273602b8b88229f182e29a1b977b80b02cb0624
Author: Jiri Lunacek <jiri.lunacek@hosting90.cz>
Date:   Tue Aug 6 10:29:34 2019 +0200

    peer_map parameter and fix in state detection when no brick is running on peer
    
    The resource agent assumed that peer names in gluster are identical to short hostname of the machine which is not always the case. This commit adds a parameter to solve this.
    Also resource agent reported brick running on cluster nodes that did not cary any brick of specified volume.
    
    Change-Id: I90aacfc34ac0d00aae3f2abb69cacd7278b886bc
    Fixes: bz#1737778
    Signed-off-by: Jiri Lunacek <jiri.lunacek@hosting90.cz>

commit f81bf47d1c3dcb69ec1f2be6f24f2b7fd9737111
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Aug 29 14:27:12 2019 +0530

    build: Fix libglusterd Makefile target
    
    * Fix libglusterd.la target path in cli/src/Makefile.am
    
    * Like libglusterfs, libgfxdr and libgfrpc, libglusterd is also
      expected to be ready by the time xlators/mgmt/glusterd sources
      are compiled. Therefore this change removes the additional
      mentioning of libglusterd.la target in Makefile.am
    
    Change-Id: I1b787316cfb6cd7487f49e661490b9788a0b80b3
    Updates: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 600ba94183333c4af9b4a09616690994fd528478
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Aug 22 17:27:22 2019 +0530

    afr: wake up index healer threads
    
    ...whenever shd is re-enabled after disabling or there is a change in
    `cluster.heal-timeout`, without needing to restart shd or waiting for the
    current `cluster.heal-timeout` seconds to expire.
    
    See BZ 1743988 for more details.
    
    Change-Id: Ia5ebd7c8e9f5b54cba3199c141fdd1af2f9b9bfe
    fixes: bz#1744548
    Reported-by: Glen Kiessling <glenk1973@hotmail.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 77895e92351a8e6257c2e2aaff431446f865fe0b
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Tue Jul 16 18:43:13 2019 +0530

    build: move arch-dependent files from /usr/share to /usr/libexec
    
    All architecture-dependent data should be placed
    in /usr/libexec, and architecture independent data
    files in /usr/share.
    
    fixes: bz#1387404
    Change-Id: Ie3249cae37c5ee4211309ef55a7a76682e57602f
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit c90dc63ec9eee0f43ba8e489876fdf8b8810bbdc
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Aug 28 09:05:20 2019 +0530

    glusterd: glusterd service is getting timed out on scaled setup
    
    Problem: On a three node cluster with 2000 replica volumes systemctl is getting
             timed out for glusted service.
    
    Solution: Configure TimeoutSec 300 to wait for glusterd startup.
    
    Change-Id: Idb3f3f3e56e6216a0ebd754cbb9e8e37ce9e636d
    Fixes: bz#1746228
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 5a9ca4b99b256222acf200847c6d4e0447b95652
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 27 16:57:14 2019 +0530

    glusterd: Fixed incorrect size argument
    
    An incorrect size argument to snprintf caused
    the glusterd process to crash on startup. This has been
    fixed.
    
    Change-Id: Iddafb5468866d0182cd8239210c92c893e643285
    Fixes: bz#1745965
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit abc472524bc575773ec29c5856f12a29af3af350
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Fri Jul 12 20:23:20 2019 +0530

    build: fix rpmlint warnings in specfile
    
    Fixed following warnings:
    
    glusterfs.spec:286: W: unversioned-explicit-obsoletes %{name}-ufo
    glusterfs.spec:288: W: unversioned-explicit-obsoletes %{name}-rdma
    glusterfs.spec:290: W: unversioned-explicit-obsoletes %{name}-gnfs
    
    fixes: bz#1183054
    Change-Id: I6bc0d3afd34cda1e4a7d74b8006ce3966109638f
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 7926992e65d0a07fdc784a6e45740306d9b4a9f2
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Aug 26 12:38:40 2019 +0530

    glusterd: Unused value coverity fix
    
    CID: 1288765
    updates: bz#789278
    
    Change-Id: Ie6b01f81339769f44d82fd7c32ad0ed1a697c69c
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f0be15cd534b91f88c0239ae850f22c5f2b90c0f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 15 11:26:55 2019 +0530

    glusterd: stop stale bricks during handshaking in brick mux mode
    
    This patch addresses two problems:
    
    1. During friend handshaking, if a volume is imported due to change in
    the version, the old bricks were not stopped which would lead to a
    situation where bricks will run with old volfiles.
    
    2. As part of attaching shd service in glusterd_attach_svc, there might
    be a case that the volume for which we're attempting to attach a shd
    service might become stale and in the process of deletion and hence in
    every retrials (if the rpc connection isn't ready) check for the
    existance of the volume and then only attempt the further attach
    request.
    
    Fixes: bz#1733425
    Change-Id: I6bac6b871f7e31cb5bf277db979289dec196a03e
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 093c66a0af496301e5d28d55f4fe57362cb399d5
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Wed Aug 7 12:53:06 2019 +0530

    glusterd: Add warning and abort in case of failures in migration during remove-brick commit
    
    Problem -
    Currently remove-brick commit goes through even though there were files
    that failed to migrate or were skipped. There is no warning raised to the user.
    Solution-
    Add a check in the remove brick staging phase to verify if the status of the
    rebalnce process is complete but there has been failures or some skipped files
    while migration, In this case user will be given a warning and remove-brick
    commit. User will need to use the force option to remove the bricks.
    
    Fixes: bz#1514683
    Signed-offby- Vishal Pandey <vpandey@redhat.com>
    
    Change-Id: I014d0f0afb4b2fac35ab0de52227f98dbae079d5

commit 30e83561b8dcced2593deb904688177fcd4ff0e0
Author: Barak Sason <bsasonro@redhat.com>
Date:   Tue Aug 20 15:37:16 2019 +0300

    cli - group files to set volume options supports comments
    
    Modified parsing of group files in such a way that line that starts with
    "#" would be treated as comments
    
    Fixes: bz#1423442
    
    Change-Id: Id85ceb49f8f9c920d4ea551f60bd28767279d4be
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 7afea5eeef61d3f29496b15ba54defeb39161588
Author: Barak Sason <bsasonro@redhat.com>
Date:   Sun Aug 18 15:54:11 2019 +0300

    cluster/afr - Unused variables
    
    -Minor change to if-else structure to avoid code duplication.
    -Added logging in case method calls fails
    
    CID: 1394654
    Updates: bz#789278
    
    Change-Id: Ibef4450dc89ddd3bf951303d5b87f503924fd250
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 673f2f90f35e5ea381bd22a43403278f89c957a5
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Oct 16 14:24:29 2017 +0530

    Revert "glusterd: (storhaug) remove ganesha (843e1b0)"
    
    please note as an additional change, macro GLUSTERD_GET_SNAP_DIR
    moved from glusterd-store.c to glusterd-snapshot-utils.h
    
    Change-Id: I811efefc148453fe32e4f0d322e80455447cec71
    updates: #663
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 3fe34c921146a8d11875dc3d904e3a5994eb1cb6
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Oct 16 14:18:31 2017 +0530

    Revert "packaging: (ganesha) remove glusterfs-ganesha subpackage and related files"
    
    Until 3.12, glusterd had an option to setup HA cluster for nfs-ganesha using pacemaker
    and corosync. But later infavour of "Storhaug" Project, this functionality was removed
    from the codebase. Since there is not much development happening towards storhaug,
    it better to keep back old working HA solution for nfs-ganesha with bit improvements.
    
    Planned improvements :
    
    * add an option in nfs-ganesha enable to set ganesha without HA.
    
    * Handle usage of export id's properly in the scripts.
    
    Change-Id: I1d60c8970bfc20035cf674d7b2705dfd4819647e
    updates: #663
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 032862fa3944fc7152140aaa13cdc474ae594a51
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Aug 22 15:51:43 2019 +0530

    posix: log aio_error return codes in posix_fs_health_check
    
    Problem: Sometime brick is going down to health check thread is
             failed without logging error codes return by aio system calls.
             As per aio_error man page it returns a positive error number
             if the asynchronous I/O operation failed.
    
    Solution: log aio_error return codes in error message
    
    Change-Id: I2496b1bc16e602b0fd3ad53e211de11ec8c641ef
    Fixes: bz#1744519
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 5e52f1900b5c61ea429f25fdcf9dfb6c56f550af
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Aug 16 16:07:03 2019 +0530

    geo-rep: Fix the name of changelog archive file
    
    Background:
    The processed changelogs are archived each month in a single tar file.
    The default format is "archive_YYYYMM.tar" which is specified as "%%Y%%m"
    in configuration file.
    
    Problem:
    The created changelog archive file didn't have corresponding year
    and month. It created as "archive_%Y%m.tar" on python2 only systems.
    
    Cause and Fix:
    Geo-rep expects "%Y%m" after the ConfigParser reads it from config file.
    Since it was "%%Y%%m" in config file, geo-rep used to get correct value
    "%Y%m" in python3 and "%%Y%%m" in python2 which is incorrect.
    The fix can be to use "%Y%m" in config file but that fails in python3.
    So the fix is to use "RawConfigParser" in geo-rep and use "%Y%m". This
    works both in python2 and python3.
    
    Change-Id: Ie5b7d2bc04d0d53cd1769e064c2d67aaf95d557c
    fixes: bz#1741890
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit d14d0749340d9cb1ef6fc4b35f2fb3015ed0339d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Aug 20 15:49:40 2019 +0530

    ctime: Fix incorrect realtime passed to frame->root->ctime
    
    On systems that don't support "timespec_get"(e.g., centos6), it
    was using "clock_gettime" with "CLOCK_MONOTONIC" to get unix epoch
    time which is incorrect. This patch introduces "timespec_now_realtime"
    which uses "clock_gettime" with "CLOCK_REALTIME" which fixes
    the issue.
    
    Change-Id: I57be35ce442d7e05319e82112b687eb4f28d7612
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    fixes: bz#1743652

commit 8b9b8abd4878d3116dda1c7d7b9736cda09691b6
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Fri Aug 9 14:19:07 2019 +0800

    nlm: check if nlm4 is initialized in nlm_priv
    
    Otherwise, gnfs will crash in following steps.
    1) gluster v set <VOL> nfs.disable off
    2) gluster v set <VOL> nfs.nlm off
    3) kill -SIGUSR1 <GNFS_PID>
    4) gnfs crash with SIGSEGV as follows:
    nlm_priv (this=this@entry=0x7f1ad00173b0) at nlm4.c:2742
    0x00007f1acf89d29d in nfs_priv (this=0x7f1ad00173b0) at nfs.c:1662
    0x00007f1ae2941085 in gf_proc_dump_single_xlator_info (trav=trav@entry=0x7f1ad00173b0) at statedump.c:502
    0x00007f1ae29410b8 in gf_proc_dump_per_xlator_info (top=top@entry=0x7f1ad00173b0) at statedump.c:519
    
    fixes: bz#1739360
    Change-Id: Ib9b207a4ccb3226dbc2c449b77de348cbc9a3d3c
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit 6edaf694e391d91f42a324da6d3a413d66ae74b9
Author: Barak Sason <bsasonro@redhat.com>
Date:   Sun Aug 18 17:52:04 2019 +0300

    storage/posix - Fixing a coverity issue
    
    Fixed a resource leak of variable 'pfd'
    
    CID: 1400673
    Updates: bz#789278
    
    Change-Id: I78e1e8a89e0604b56e35a75c25d436b35db096c3
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 5ce3ab86a67f99209dd0c533a9bd2a21bd06ef3d
Author: Barak Sason <bsasonro@redhat.com>
Date:   Sun Aug 18 11:02:32 2019 +0300

    features/utime - fixing a coverity issue
    
    -Modified op_errno init value to a non-negative value in order to avoid
    using a negative value where it's not allowed.
    -In the metod "STACK_UNWIND_STRICT" modified 3rd argument in order to
    represnt the correct value to use (changed from -1 to ret).
    
    CID: 1403650
    Updates: bz#789278
    
    Change-Id: I608031d5af13832e05e180e746b1b5280b54f559
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 4c4eae13b474c32661eeae3734627d1a8494cf54
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 21 09:54:21 2019 +0530

    geo-rep: Structured logging new format
    
    Structured logging format changed in the below patch for better
    readability and parsing. This patch changes the Geo-replication logs
    to that format.
    
    https://review.gluster.org/#/c/glusterfs/+/22987/
    
    Before:
    
    ```
    [2019-08-21 04:23:01.13672] I [monitor(monitor):157:monitor] Monitor: \
      starting gsyncd worker<TAB>brick=/bricks/b1<TAB>slave_node=f29.sonne
    ```
    
    After:
    
    ```
    [2019-08-21 04:23:01.13672] I [monitor(monitor):157:monitor] Monitor: \
      starting gsyncd worker [{brick=/bricks/b1}, {slave_node=f29.sonne}]
    ```
    
    Change-Id: I65ec69a2869e2febeedc558f88620399e4a1a6a4
    Updates: #657
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit b960e0103a70b58880b59438b116740af98a4582
Author: yinkui <13965432176@163.com>
Date:   Fri Aug 16 10:15:07 2019 +0800

    gluster-smb:add smb parameter when  access gluster by cifs
    
    Change-Id: I9ff54f2ca6f86bb5b2f4740485a0159e1fd7785f
    Fixes: bz#1741734
    Signed-off-by: yinkui <13965432176@163.com>

commit fb976636d9ffa3be4d2a47c604a7746be06e2247
Author: Barak Sason <bsasonro@redhat.com>
Date:   Thu Aug 15 17:23:17 2019 +0300

    features/cloudsync - fix a coverity issue
    
    All assigns to op_errno in this mehod were to the same vlaue - ENOMEM.
    Removed repeted assignments and assigned as init value.
    This also prevents the problem of sending a negatve value of op_errno to
    CS_STACK_UNWIND method
    
    CID: 1394645 - https://scan6.coverity.com/reports.htm#v44018/p10714/fileInstanceId=92065749&defectInstanceId=28018364&mergedDefectId=1394645
    Updates: bz#789278
    
    Change-Id: If765a9216500a38f9392617aaf06583ce36e3262
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 1c3b280602153481fead83622aa885f6735c094c
Author: Barak Sason <bsasonro@redhat.com>
Date:   Thu Aug 15 11:06:26 2019 +0300

    storage/posix - fixing a coverity issue
    
    CID: 1394644 & 1394639
    Updates: bz#789278
    
    Added logging in case method calls fails
    
    Change-Id: Ib833a5f68d37b98287b84c325637bc688937f647
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 95f71df31dc73d85df722b0e7d3a7eb1e0237e7f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Aug 8 10:05:12 2019 +0530

    ctime: Fix ctime issue with utime family of syscalls
    
    When atime|mtime is updated via utime family of syscalls,
    ctime is not updated. This patch fixes the same.
    
    Change-Id: I7f86d8f8a1e06a332c3449b5bbdbf128c9690f25
    fixes: bz#1738786
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 72fe2bd9ae0ca223d8a320ca124c2837a1571d82
Author: Barak Sason <bsasonro@redhat.com>
Date:   Sun Aug 18 15:36:40 2019 +0300

    api: fixing a coverity issue
    
    Added a null pointer check to avoid seg-fault
    
    CID:1403874
    Updates: bz#789278
    
    Change-Id: Ia8ff992c9f06d79647089f296afe77519fb5af2a
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit b4b683736367d93daad08a5ee6ca95778c07c5a4
Author: Anoop C S <anoopcs@redhat.com>
Date:   Sat Aug 10 10:30:26 2019 +0530

    performance/md-cache: Do not skip caching of null character xattr values
    
    Null character string is a valid xattr value in file system. But for
    those xattrs processed by md-cache, it does not update its entries if
    value is null('\0'). This results in ENODATA when those xattrs are
    queried afterwards via getxattr() causing failures in basic operations
    like create, copy etc in a specially configured Samba setup for Mac OS
    clients.
    
    On the other side snapview-server is internally setting empty string("")
    as value for xattrs received as part of listxattr() and are not intended
    to be cached. Therefore we try to maintain that behaviour using an
    additional dictionary key to prevent updation of entries in getxattr()
    and fgetxattr() callbacks in md-cache.
    
    Credits: Poornima G <pgurusid@redhat.com>
    
    Change-Id: I7859cbad0a06ca6d788420c2a495e658699c6ff7
    Fixes: bz#1726205
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit faaf22bbe899b0f64b0237398a0d8e3c082f9392
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Jul 18 11:43:01 2019 +0800

    features/locks: avoid use after freed of frame for blocked lock
    
    The fop contains blocked lock may use freed frame info when other
    unlock fop has unwind the blocked lock.
    
    Because the blocked lock is added to block list in inode lock(or
    other lock), after that, when out of the inode lock, the fop
    contains the blocked lock should not use it.
    
    Change-Id: Icb309a1cc78380dc982b26d50c18d67e4f2c8915
    fixes: bz#1737291
    Signed-off-by: Kinglong Mee <mijinlong@horiscale.com>

commit bb01111f50f2585429028c408932416d31c6d316
Author: Barak Sason <bsasonro@redhat.com>
Date:   Mon Aug 19 10:34:31 2019 +0300

    libglusterfs - fixing a coverity issue
    
    Fixed resource leak of variable volfile_obj
    
    CID: 1402936
    Updates: bz#789278
    
    Change-Id: I1537187e13693686f4ffca891dc1df287fab7a41
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 2fe243d0561c19009964003aa2ced7c695a46d17
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jul 3 15:08:31 2019 +0530

    logging: Structured logging reference PR
    
    To convert the existing `gf_msg` to `gf_smsg`:
    
    - Define `_STR` of respective Message ID as below(In `*-messages.h`)
    
      #define PC_MSG_REMOTE_OP_FAILED_STR "remote operation failed."
    
    - Change `gf_msg` to use `gf_smsg`. Convert values into fields and
      add any missing fields. Note: `errno` and `error` fields will be
      added automatically to log message in case errnum is specified.
    
      Example:
    
      gf_smsg(
        this->name,                            // Name or log domain
        GF_LOG_WARNING,                        // Log Level
        rsp.op_errno,                          // Error number
        PC_MSG_REMOTE_OP_FAILED,               // Message ID
        "path=%s", local->loc.path,            // Key Value 1
        "gfid=%s", loc_gfid_utoa(&local->loc), // Key Value 2
        NULL                                   // Log End
      );
    
    Key value pairs formatting Help:
    
      gf_slog(
        this->name,                               // Name or log domain
        GF_LOG_WARNING,                           // Log Level
        rsp.op_errno,                             // Error number
        PC_MSG_REMOTE_OP_FAILED,                  // Message ID
        "op=CREATE",                              // Static Key and Value
        "path=%s", local->loc.path,               // Format for Value
        "brick-%d-status=%s", brkidx, brkstatus,  // Use format for key and val
        NULL                                      // Log End
      );
    
    Before:
    
    [2019-07-03 08:16:18.226819] W [MSGID: 114031] [client-rpc-fops_v2.c \
    :2633:client4_0_lookup_cbk] 0-gv3-client-0: remote operation failed. \
    Path: / (00000000-0000-0000-0000-000000000001) [Transport endpoint   \
    is not connected]
    
    After:
    
    [2019-07-29 07:50:15.773765] W [MSGID: 114031]                   \
    [client-rpc-fops_v2.c:2633:client4_0_lookup_cbk] 0-gv1-client-0: \
    remote operation failed. [{path=/f1},                            \
    {gfid=00000000-0000-0000-0000-000000000000},                     \
    {errno=107}, {error=Transport endpoint is not connected}]
    
    To add new `gf_smsg`, Add a Message ID in respective `*-messages.h` file
    and the follow the steps mentioned above.
    
    Change-Id: I4e7d37f27f106ab398e991d931ba2ac7841a44b1
    Updates: #657
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 25cf0d24caa11bdfefe10c93541da07c635d4cfe
Author: Barak Sason <bsasonro@redhat.com>
Date:   Sun Aug 18 17:38:09 2019 +0300

    mount/fuse - Fixing a coverity issue
    
    Fixed resource leak of dict_value and newkey variables
    
    CID: 1398630
    Updates: bz#789278
    
    Change-Id: I589fdc0aecaeb4f446cd29f95bad36ccd7a35beb
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit b1dc7723610325789ba91220ab414e821ec14119
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Aug 16 15:38:49 2019 +0530

    geo-rep: Fix worker connection issue
    
    All the workers connects to primary slave node. It should
    connect to available slave nodes in round robin fashion
    and choose different slave node if the corresponding slave
    node is down. This patch fixes the same.
    
    Thanks Aravinda for the help in root causing this.
    
    Change-Id: I9f8e7744f4adb8a24833cf173681d109710f98cb
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Updates: bz#1737484

commit f138d3fa2237e7fa940ecf17153fd700350c4138
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Jul 16 20:36:57 2019 +0530

    posix: In brick_mux brick is crashed while start/stop volume in loop
    
    Problem: In brick_mux environment sometime brick is crashed while
             volume stop/start in a loop.Brick is crashed in janitor task
             at the time of accessing priv.If posix priv is cleaned up before
             call janitor task then janitor task is crashed.
    
    Solution: To avoid the crash in brick_mux environment introduce a new
              flag janitor_task_stop in posix_private and before send CHILD_DOWN event
              wait for update the flag by janitor_task_done
    
    Change-Id: Id9fa5d183a463b2b682774ab5cb9868357d139a4
    fixes: bz#1730409
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a4d073cda22787552b46b186b898304b438db0c2
Author: Barak Sason <bsasonro@redhat.com>
Date:   Sun Aug 18 12:21:47 2019 +0300

    protocol/client - fixing a coverity issue
    
    Moved null pointer check up in order to avoid seg-fault
    
    CID: 1404258
    Updates: bz#789278
    
    Change-Id: Ib97e05302bfeb8fe38d6ce9870b9740cb576e492
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 0590a1e5dd339af716ed49f0e66f3281ec7a6d0e
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 8 22:23:04 2019 +0300

    client_t.c: removal of dead code.
    
    Change-Id: Id9f5f448db305f3135a1fdca61b1d7ec898c63a4
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c63a1f6ab0f2ff08e0a738f33558a3f8bdd87996
Author: Barak Sason <bsasonro@redhat.com>
Date:   Thu Aug 15 15:54:28 2019 +0300

    storage/posix - Moved pointed validity check in order to avoid possible seg-fault
    
    CID: 1124831
    Updates: bz#789278
    
    Change-Id: Ia6550be3742849809cf3e0a4a39d9d6e77003b35
    Signed-off-by: Barak Sason <bsasonro@redhat.com>

commit 8f1620ad7f5d3d040fee55c5f873349800e2268d
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Aug 19 16:00:24 2019 +0530

    glusterd: ./tests/bugs/glusterd/bug-1595320.t is failing
    
    Problem: sometime ./tests/bugs/glusterd/bug-1595320.t is failing  is
             failing at the time of checking brick_process after sending
             a kill signal to brick process
    
    Solution: Wait sometime after just sending a kill signal to brick
              process to make sure brick process is stopped
    
    Change-Id: Iee9e91284618abfc62a550d47e4f9117785def58
    Fixes: bz#1743200
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit c2b0696f0c2b901b8c34c732c1ba85c364ff2f04
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Sep 7 20:48:59 2018 +0530

    tests/dht: Add a test file for file renames
    
    Test the various combinations of hashed and cached
    subvols for the src and dst.
    
    Change-Id: I41416f9e5f2b7ea1c880d1913fdd6576da1ee868
    fixes: bz#1626543
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit bbab770e2aa527059c6590162d944a90efb459c1
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Aug 19 09:40:48 2019 +0530

    tests: mark bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t as BRICK_MUX_BAD_TEST
    
    Updates: bz#1743069
    Change-Id: I1eea0186ca0c1b1226f4b3d0d7c0e41fc7821cbd
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit c370c70f77079339e2cfb7f284f3a2fb13fd2f97
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Aug 13 18:45:43 2019 +0530

    rpc: glusterd start is failed and throwing an error Address already in use
    
    Problem: Some of the .t are failed due to bind is throwing
             an error EADDRINUSE
    
    Solution: After killing all gluster processes .t is trying
              to start glusterd but somehow if kernel has not cleaned
              up resources(socket) then glusterd startup is failed due to
              bind system call failure.To avoid the issue retries to call
              bind 10 times to execute system call succesfully
    
    Change-Id: Ia5fd6b788f7b211c1508c1b7304fc08a32266629
    Fixes: bz#1743020
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 29cfe643cbcf7826375a3d52ff1865706a35bc38
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 28 22:51:37 2019 +0530

    libglusterfs: remove dependency of rpc
    
    Goal: 'libglusterfs' files shouldn't have any dependency outside of
          the tree, specially the header files, shouldn't have '#include'
          from outside the tree.
    
    Fixes:
    * Had to introduce libglusterd so, methods and structures required
      for only mgmt/glusterd, and cli/ are separated from 'libglusterfs/'
    * Remove rpc/xdr/gen from build, which was used mainly so
      dependency for libglusterfs could be properly satisfied.
    * Move rpcsvc_auth_data to client_t.h, so all dependencies could
      be handled.
    
    Updates: bz#1636297
    Change-Id: I0e80243a5a3f4615e6fac6e1b947ad08a9363fce
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit a24288c5c9da9137eb1d5d487bc7cd11af01b88b
Author: Philip Spencer <pspencer@fields.utoronto.ca>
Date:   Tue May 7 10:19:34 2019 -0400

    mount.glusterfs: make fcache-keep-open option take a value
    
    Fixes: bz#1158130
    Change-Id: Ifdeaed7c9fbe85f7ce421f7c89cbe7265e45f77c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8e9c53ebf16705b9a1db2fc486dc24a5cb244ddd
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Jul 30 17:05:22 2019 +0530

    afr: restore timestamp of parent dir during entry-heal
    
    Fixes: bz#1734370
    Change-Id: I29e338bac62104233a6f80212df8d0fb016affda
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 23673fde22483d1b53d17ca9b7d946330eea8af3
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 6 23:20:02 2019 +0300

    client-handshake.c: minor changes and removal of dead code.
    
    - Removal of quite a bit of dead code.
    - Use dict_set_str_sizen and friends where applicable.
    - Moved some functions to be static and initialize values right away.
    
    Change-Id: Ic25b5da4028198694a0e24796dea375661eb66b9
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d79de9976ea4332aa8f7bba4e27b0f578bb81cf0
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Aug 1 16:20:33 2019 -0400

    posix: don't expect timer wheel to be inited
    
    Adding a timer to timer wheel should be done only after getting the
    timer wheel from the ctx using the function glusterfs_ctx_tw_get(). The
    function inits the wheel if not already done.
    
    Change-Id: I9692f84b822a02a9dc14725b7c11d26a2a634e94
    Updates: #703
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>

commit 6ef9ffea7fee43ea6f59c8c36fd183f90e9c26f8
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jul 25 11:51:32 2019 +0530

    glusterd: create separate logdirs for cluster.rc instances
    
    Create a separate logdir for each host instance created by
    cluster.rc. This makes it easier to determine the files
    belonging to a particular instance.
    
    Change-Id: Ic8321f83f98995412b7d5f095b3d3f0391767a8b
    Fixes: bz#1733042
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 089e53c7f1c32644ce2b37830b678b4c0c7071fc
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Aug 9 14:34:22 2019 +0530

    fuse: Set limit on invalidate queue size
    
    If the glusterfs fuse client process is unable to
    process the invalidate requests quickly enough, the
    number of such requests quickly grows large enough
    to use a significant amount of memory.
    We are now introducing another option to set an upper
    limit on these to prevent runaway memory usage.
    
    Change-Id: Iddfff1ee2de1466223e6717f7abd4b28ed947788
    Fixes: bz#1732717
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 5707f2eb1c6933e70300227a6068b6b50befbb87
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Aug 8 11:32:56 2019 +0530

    cluster/ec: Fix coverity issue.
    
    Change-Id: I727287784a15d89441865de7f438002e4a370250
    fixes: bz#1738763
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 82ebdab2762d347549e7864658b5e20dae8379e1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 25 13:43:37 2019 +0530

    gfapi: provide version for statedump path
    
    Updates: bz#1689097
    Change-Id: I2e3c2a3aef17fda67d04fa9e604ea3f8335a2b0b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 51237eda7c4b3846d08c5d24d1e3fe9b7ffba1d4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Aug 7 12:12:43 2019 +0530

    features/shard: Send correct size when reads are sent beyond file size
    
    Change-Id: I0cebaaf55c09eb1fb77a274268ff564e871b743b
    fixes bz#1738419
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 3cc0113ee436b63f69e16e4e0cd9443f1b3188ec
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Aug 12 11:29:36 2019 +0530

    tests: fix bug-880898.t crash
    
    Problem:
    https://build.gluster.org/job/centos7-regression/7337/consoleFull
    indicates the shd crashing for this .t. On looking at the core, I see
    the crash is at the time of shd init and glusterfs context is null:
    
    (gdb) bt
    (gdb) p ctx
    $2 = (glusterfs_ctx_t *) 0xf00000000
    
    The .t is killing all gluster processes immediately after volume start,
    so it looks like a race between shd coming up and it being killed.
    
    Fix: Kill gluster processes only after they are up and running.
    
    Fixes: bz#1740017
    Change-Id: I7cf589201669bd9f535e968d147015dc99e9a4b6
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 40f476f40b37cc8fcc83618094d357ee643442d8
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Apr 3 14:23:06 2019 +0200

    fuse: rate limit reading from fuse device upon receiving EPERM
    
    Fixes: bz#1644322
    Change-Id: I53e8fa362cd8c7d04fb1c4abb606a9abb642c592
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 8ca15e3c9c72511bbe8a548a1471f8d6a5bfd709
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Jul 25 10:49:10 2019 +0200

    build: stop suppressing "Entering/Leaving direcory..." messages
    
    This is useful information as it allows locating build issues quickly.
    
    The size of the build output increases roughly by half of it, which
    is a tolerable trade-off for better build time diagnostics.
    
    updates bz#1193929
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Change-Id: Id60c03bee558528ae804f037c93457f9d9e738c0

commit b0b57af4050f19fd9b38d48cfa35c119b0ac83f4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Aug 2 12:05:09 2019 +0530

    cluster/ec: Update lock->good_mask on parent fop failure
    
    When discard/truncate performs write fop, it should do so
    after updating lock->good_mask to make sure readv happens
    on the correct mask
    
    fixes bz#1727081
    Change-Id: Idfef0bbcca8860d53707094722e6ba3f81c583b7
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit b1acf275a0779542d0ad1362e926658c037c94d8
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Aug 5 19:00:21 2019 +0530

    geo-rep: Fix Config Get Race
    
    When two threads(sync jobs) in Geo-rep worker calls `gconf.get` and
    `gconf.getr`(realtime) at the sametime, `getr` resets the conf object
    and other one gets None. Thread Lock is introduced to fix the issue.
    
    ```
      File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py",
      line 368, in twrap
        tf(*aargs)
      File "/usr/libexec/glusterfs/python/syncdaemon/master.py", line 1987,
      in syncjob
        po = self.sync_engine(pb, self.log_err)
      File "/usr/libexec/glusterfs/python/syncdaemon/resource.py",
      line 1444, in rsync
        rconf.ssh_ctl_args + \
    AttributeError: 'NoneType' object has no attribute 'split'
    ```
    
    Change-Id: I9c245e5c36338265354e158f5baa32b119eb2da5
    Updates: bz#1737484
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 30e42d14d8d1bec1883f1b7921d01b3117b1eed8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Aug 5 21:16:35 2019 +0530

    rpc/transport: have default listen-port
    
    With release-6, we now can have transport.socket.listen-port parameter
    configurable in glusterd.vol. However the default value wasn't defined
    in the code and this breaks the backward compatibility where if one has
    a modified glusterd.vol file, then post upgrade the same file will be
    retained and the new changes introduced as part of the release wouldn't
    be available in the glusterd.vol. So it's important that for each new
    options introduced in glusterd.vol file backward compatibility is
    guaranteed.
    
    Fixes: bz#1737676
    Change-Id: I776b28bff786320cda299fe673d824024dc9803e
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit e3592d7fab0dc9d3f304d3eda34ba862f2c657a6
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 29 15:20:22 2019 +0530

    cluster/dht: Log hashes in hex
    
    Log layout hash ranges in hex to make it easier
    to compare them to the on disk xattrs.
    
    Change-Id: Ib75c2508bf8e0ab7f5ae26d0443ef02b792b7307
    Fixes: bz#1697293
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 0486821b33b2ece4058a78058f9f3e2f7149d8a7
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Mon Aug 5 11:08:02 2019 +0800

    features/utime: always update ctime at setattr
    
    For the nfs EXCLUSIVE mode create may sets a later time
    to mtime (at verifier), it should not set to ctime for
    storage.ctime does not allowed set ctime to a earlier time.
    
     /* Earlier, mdata was updated only if the existing time is less
      * than the time to be updated. This would fail the scenarios
      * where mtime can be set to any time using the syscall. Hence
      * just updating without comparison. But the ctime is not
      * allowed to changed to older date.
      */
    
    According to kernel's setattr, always set ctime at setattr,
    and doesnot set ctime from mtime at storage.ctime.
    
    Change-Id: I5cfde6cb7f8939da9617506e3dc80bd840e0d749
    fixes: bz#1737288
    Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>

commit 80fa433be6e399311a6bcaa1e074bc1ae65122e2
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Jul 5 14:12:54 2019 +0530

    graph/shd: attach volfile even if ctx->active is NULL
    
    While we receive a graph attach request, if ctx->active is
    not set we used to fail assuming that the initilization has
    not completed yet for the process start.
    
    Since the management connection is established, it will receive
    attach request, even when ctx->active is NULL.
    
    Change-Id: Ied4d1ac63e6d4ced4a9405a78e1ce39f81dfd437
    fixes: bz#1727256
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 8e47ae31e4477dc50eaf7604860ff8e7139ea547
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Jul 4 15:43:05 2019 +0530

    glusterd/shd: Return null proc if process is not running.
    
    We were ruturning first proc entry even if it is not running.
    This was in an assumption that the process could have just
    started and not updated the pidfile.
    
    Now we that we have introduced the states for process state,
    we can take decision based on that.
    
    Change-Id: Ibfc11c966b0db599a8d6a08d8b975233b2bbfb8c
    Fixes: bz#1728766
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 16548f11ab5433223c6d9a7e71f8dc2a925d1e5b
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Jul 31 15:31:34 2019 +0530

    tests/shd: Break down shd mux tests into multiple .t file
    
    Test file tests/basic/shd-mux.t was taking longer than 200
    seconds in some iterations. So this patch is breaking the
    test case to three files
    
    Change-Id: I1430f58798f876edf6368d6f4b8b5a75f0114c31
    Updates: bz#1708929
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 2aeb9fb17087434d87497a85077073ea3bf94869
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jul 30 10:15:42 2019 +0300

    multiple files: reduce minor work under RCU_READ_LOCK
    
    1. Try to unlock faster - in error paths.
    2. Remove memory allocations - do them before the lock.
    
    Change-Id: I1e9ddd80b99de45ad0f557d62a5f28951dfd54c8
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 2dd43d3e5b5305db3a5ecafabdd9cf8e7775ec75
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 1 19:00:56 2019 +0530

    xdr: add code so we have more xdr functions covered
    
    Updates: bz#1693692
    Change-Id: Ia10ccca5e1fed6c4269842ebb4d507662ca0f6a6
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ed7a3793073670e787063c47e55010fc7c963064
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Aug 1 13:37:07 2019 -0400

    storage/posix: set the op_errno to proper errno during gfid set
    
    In posix_gfid_set, the proper error is not captured in one of
    the failure cases.
    
    Change-Id: I1c13f0691a15d6893f1037b3a5fe385a99657e00
    Fixes: bz#1736482
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit c927bc07385b79a4f86c339cd0e0eed361090d9b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 29 11:51:07 2019 +0530

    tests: introduce BRICK_MUX_BAD_TESTS variable
    
    ... to ignore test failures specific to brick mux.
    
    Change-Id: I3114f34f194f18e7fc8c02a117b295f086721226
    updates: bz#1193929
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit d072dc09f5bc6431ba31244cf7e9eba1b6e85229
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Jul 22 15:20:43 2019 +0530

    locks/fencing: Address hang while lock preemption
    
    The fop_wind_count can go negative when fencing is enabled
    on unwind path of the IO leading to hang.
    
    Also changed code so that fop_wind_count needs to be maintained only
    till fencing is enabled on the file.
    
    updates: bz#1717824
    Change-Id: Icd04b42bc16cd3d50eaa581ee57233910194f480
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 84f7794547522463841068063b22fd3a8d8fca2b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jul 31 15:40:55 2019 +0530

    geo-rep: Fix mount broker setup issue
    
    Even the use builtin 'type' command as in patch [1]
    causes issues if argument in question is not part of PATH
    environment variable for that user. This patch fixes the
    same by doing source /etc/profile. This was already being
    used in another part of script.
    
    [1] https://review.gluster.org/23089
    
    Change-Id: Iceb78835967ec6a4350983eec9af28398410c002
    fixes: bz#1734738
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 756f903e2adeaa520c848aa3c0664573cb584d07
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jul 25 12:56:12 2019 +0530

    gfapi: Fix deadlock while processing upcall
    
    As mentioned in bug1733166, there could be potential deadlock
    while processing upcalls depending on how each xlator choose
    to act on it. The right way of fixing such issues
    is to change rpc callback communication process.
    - https://github.com/gluster/glusterfs/issues/697
    
    Till then, making changes in gfapi layer to avoid any I/O
    processing.
    
    Change-Id: I2079e95339e5d761d5060707f4555cfacab95c83
    fixes: bz#1733166
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 00084d5f0c84995d14fb3b626af227f60426e885
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 1 12:13:05 2019 +0530

    lcov: check for zerofill/discard fops on arbiter
    
    Updates: bz#1693692
    Change-Id: I145df4c0d0b0ce738f1d34b02341ec606e38522e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit d68e426263708334945dff69b88218ed71a48033
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Jun 8 01:22:27 2019 +0300

    Multiple files: get trivial stuff done before lock
    
    Initialize a dictionary for example seems to be prefectly fine to be done
    before taking a lock.
    
    Change-Id: Ib29516c4efa8f0e2b526d512beab488fcd16d2e7
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d7e449b0da35a30af876aef1bea1fb096d0c06dc
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jul 29 16:22:10 2019 +0530

    posix/ctime: Fix race during lookup ctime xattr heal
    
    Problem:
    Ctime heals the ctime xattr ("trusted.glusterfs.mdata") in lookup
    if it's not present. In a multi client scenario, there is a race
    which results in updating the ctime xattr to older value.
    
    e.g. Let c1 and c2 be two clients and file1 be the file which
    doesn't have the ctime xattr. Let the ctime of file1 be t1.
    (from backend, ctime heals time attributes from backend when not present).
    
    Now following operations are done on mount
    c1 -> ls -l /mnt/file1  |   c2 -> ls -l /mnt/file1;echo "append" >> /mnt/file1;
    
    The race is that the both c1 and c2 didn't fetch the ctime xattr in lookup,
    so both of them tries to heal ctime to time 't1'. If c2 wins the race and
    appends the file before c1 heals it, it sets the time to 't1' and updates
    it to 't2' (because of append). Now c1 proceeds to heal and sets it to 't1'
    which is incorrect.
    
    Solution:
    Compare the times during heal and only update the larger time. This is the
    general approach used in ctime feature but got missed with healing legacy
    files.
    
    fixes: bz#1734299
    Change-Id: I930bda192c64c3d49d0aed431ce23d3bc57e51b7
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 7124fc6d01aa23e9a218d0ce608242d0ae320193
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 25 11:00:29 2019 +0530

    gfapi: increase function-coverage
    
    * Add few more mgmt functions to the coverage
    * While testing mgmt function, found an issue, where if the
      'glfs_set_volfile_server()' is not called before calling
      'glfs_unset_volfile_server()', unset would cause a crash.
      Null check of few variables fixes the issue, which is handled
      in this patch itself.
    * Added a test for volfile API
    
    Updates: bz#1693692
    Change-Id: Iba151f8da1b64107e2f436ddbfef9da45b1c1588
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit a31fad885c30cbc1bea652349c7d52bac1414c08
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 30 17:12:58 2019 +0530

    tests: heal-info add --xml option for more coverage
    
    Updates: bz#1693692
    Change-Id: I13de7cf4c380b9663e6258e2fd62ce1f180591b4
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 1b19ee85d5eec97b21fbd3fe6d283ec38a23028b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 25 10:55:01 2019 +0530

    error-gen: increase coverage by reducing error-rate
    
    Updates: bz#1693692
    Change-Id: I07371ea1e2613fed6dd9ea67c40cbb3ebcb9387e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 363527ebc4140e99f182770915b72acdcb5c2bdf
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jul 29 15:07:58 2019 +0530

    trace: add more coverage by testing it with glfs-coverage too.
    
    make sure to provide 'log-file' option, so we can see the logs.
    This test does test volgen inserting the trace xlator in server
    graph.
    
    Updates: bz#1693692
    Change-Id: I26c736b04376674b4c094d48060660421e6c983c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 22bd0570c04cb94d1a954b56d11db61790ff20b2
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Jul 30 10:32:39 2019 +0530

    cluster/ec: Create heal task with heal process id
    
    Problem:
    ec_data_undo_pending calls syncop_fxattrop->SYNCOP without
    a frame. In this case SYNCOP gets the frame of the task.
    However, when we create a synctask for heal we provide
    frame as NULL.
    Now, if the read-only feature is ON, it will receive the
    process ID of the shd as 0 and will consider that it as
    not an internal process. This will prevent healing of a
    file with "Read-only file system" error message log.
    
    Solution:
    While launching heal, create a synctask using frame and set
    process id of the SHD which is -6.
    
    Change-Id: I37195399c85de322cbcac75633888922c4e3db4a
    Fixes: bz#1734252

commit 065b10beaae8ea7390c2e3059044313aef8a5fea
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 29 14:08:37 2019 +0530

    cluster/ec: Fix reopen flags to avoid misbehavior
    
    Problem:
    when a file needs to be re-opened O_APPEND and O_EXCL
    flags are not filtered in EC.
    
    - O_APPEND should be filtered because EC doesn't send O_APPEND below EC for
    open to make sure writes happen on the individual fragments instead of at the
    end of the file.
    
    - O_EXCL should be filtered because shd could have created the file so even
    when file exists open should succeed
    
    - O_CREAT should be filtered because open happens with gfid as parameter. So
    open fop will create just the gfid which will lead to problems.
    
    Fix:
    Filter out these two flags in reopen.
    
    Change-Id: Ia280470fcb5188a09caa07bf665a2a94bce23bc4
    Fixes: bz#1733935
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d7001336c38bb9516645bbc0fd07a8c7f1f8b3f8
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Jul 3 10:07:29 2019 +0300

    dict.c: dict_unserialize() can use dict_addn()
    
    Since we know the keylen, we can use dict_addn() instead of dict_add().
    
    Change-Id: Iebe77faa1a20ec132cba5fb85b3d2ea63339181d
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 799edc73c3d4f694c365c6a7c27c9ab8eed5f260
Author: Xiubo Li <xiubli@redhat.com>
Date:   Fri Jul 26 12:34:52 2019 +0800

    event: rename event_XXX with gf_ prefixed
    
    I hit one crash issue when using the libgfapi.
    
    In the libgfapi it will call glfs_poller() --> event_dispatch()
    in file api/src/glfs.c:721, and the event_dispatch() is defined
    by libgluster locally, the problem is the name of event_dispatch()
    is the extremly the same with the one from libevent package form
    the OS.
    
    For example, if a executable program Foo, which will also use and
    link the libevent and the libgfapi at the same time, I can hit the
    crash, like:
    
    kernel: glfs_glfspoll[68486]: segfault at 1c0 ip 00007fef006fd2b8 sp
    00007feeeaffce30 error 4 in libevent-2.0.so.5.1.9[7fef006ed000+46000]
    
    The link for Foo is:
    lib_foo_LADD = -levent $(GFAPI_LIBS)
    It will crash.
    
    This is because the glfs_poller() is calling the event_dispatch() from
    the libevent, not the libglsuter.
    
    The gfapi link info :
    GFAPI_LIBS = -lacl -lgfapi -lglusterfs -lgfrpc -lgfxdr -luuid
    
    If I link Foo like:
    lib_foo_LADD = $(GFAPI_LIBS) -levent
    It will works well without any problem.
    
    And if Foo call one private lib, such as handler_glfs.so, and the
    handler_glfs.so will link the GFAPI_LIBS directly, while the Foo won't
    and it will dlopen(handler_glfs.so), then the crash will be hit everytime.
    
    The link info will be:
    foo_LADD = -levent
    libhandler_glfs_LIBADD = $(GFAPI_LIBS)
    
    I can avoid the crash temporarily by linking the GFAPI_LIBS in Foo too like:
    foo_LADD = $(GFAPI_LIBS) -levent
    libhandler_glfs_LIBADD = $(GFAPI_LIBS)
    
    But this is ugly since the Foo won't use any APIs from the GFAPI_LIBS.
    
    And in some cases when the --as-needed link option is added(on many dists
    it is added as default), then the crash is back again, the above workaround
    won't work.
    
    Fixes: #699
    
    Change-Id: I38f0200b941bd1cff4bf3066fca2fc1f9a5263aa
    Signed-off-by: Xiubo Li <xiubli@redhat.com>

commit 26b9c85861f058a4a8335b28f49410ba061e7c1a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Jul 25 23:36:56 2019 +0300

    glusterd: write voldir once in glusterd-store and don't attempt again.
    
    glusterd_store_brickinfos() is calling per each brick the
    function glusterd_store_brickinfo().
    In it, we call:
    
     ret = glusterd_store_create_brick_dir(volinfo);
    
    However, volinfo is the same for all those bricks - no need to again
    and again call it (which tries to mkdir that dir).
    We can do it once above the loops in glusterd_store_brickinfos()
    
    While at, combine two similar functions that write additional dirs.
    
    Change-Id: I5858cf7783f088ea13a8fa20115118efa816f4cb
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 11d52142f67638209be43007d993dc137412aa42
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jul 18 11:25:31 2019 +0530

    cluster/ec: Always read from good-mask
    
    There are cases where fop->mask may have fop->healing added
    and readv shouldn't be wound on fop->healing. To avoid this
    always wind readv to lock->good_mask
    
    fixes bz#1727081
    Change-Id: I2226ef0229daf5ff315d51e868b980ee48060b87
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 2af877cec513b1fca5a9f27b338117bacd5ab2f1
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jul 9 11:06:49 2019 +0200

    fuse: add missing GF_FREE to fuse_interrupt
    
    Change-Id: Id7e003e4a53d0a0057c1c84e1cd704c80a6cb015
    Fixes: bz#1728047
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit f024178b7cd4f884e23045c77dc4e09b89b98bb7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 25 12:29:15 2019 +0530

    quiesce: add missing fops
    
    Updates: bz#1693692
    Change-Id: I4f005e7168c201709a85db443d643b81e6d3d282
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 84a55090123a7e3124100e5564da8c521c3c22ab
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Tue Jul 23 13:16:04 2019 +0000

    [core] fix return of local in  __nlc_inode_ctx_get
    
    __nlc_inode_ctx_get assigns a value to nlc_pe_p which is never used by
    its parent function or any of the predecessor hence remove the
    assignment and also that function argument as it is not being used
    anywhere.
    
    fixes: bz#1732496
    
    Change-Id: I5b950e1e251bd50a646616da872a4efe9d2ff8c9
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit b01a43586c5abc23a874e5528a063c508f952cbd
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Jul 17 14:50:22 2019 +0200

    cluster/ec: fix EIO error for concurrent writes on sparse files
    
    EC doesn't allow concurrent writes on overlapping areas, they are
    serialized. However non-overlapping writes are serviced in parallel.
    When a write is not aligned, EC first needs to read the entire chunk
    from disk, apply the modified fragment and write it again.
    
    The problem appears on sparse files because a write to an offset
    implicitly creates data on offsets below it (so, in some way, they
    are overlapping). For example, if a file is empty and we read 10 bytes
    from offset 10, read() will return 0 bytes. Now, if we write one byte
    at offset 1M and retry the same read, the system call will return 10
    bytes (all containing 0's).
    
    So if we have two writes, the first one at offset 10 and the second one
    at offset 1M, EC will send both in parallel because they do not overlap.
    However, the first one will try to read missing data from the first chunk
    (i.e. offsets 0 to 9) to recombine the entire chunk and do the final write.
    This read will happen in parallel with the write to 1M. What could happen
    is that half of the bricks process the write before the read, and the
    half do the read before the write. Some bricks will return 10 bytes of
    data while the otherw will return 0 bytes (because the file on the brick
    has not been expanded yet).
    
    When EC tries to recombine the answers from the bricks, it can't, because
    it needs more than half consistent answers to recover the data. So this
    read fails with EIO error. This error is propagated to the parent write,
    which is aborted and EIO is returned to the application.
    
    The issue happened because EC assumed that a write to a given offset
    implies that offsets below it exist.
    
    This fix prevents the read of the chunk from bricks if the current size
    of the file is smaller than the read chunk offset. This size is
    correctly tracked, so this fixes the issue.
    
    Also modifying ec-stripe.t file for Test #13 within it.
    In this patch, if a file size is less than the offset we are writing, we
    fill zeros in head and tail and do not consider it strip cache miss.
    That actually make sense as we know what data that part holds and there is
    no need of reading it from bricks.
    
    Change-Id: Ic342e8c35c555b8534109e9314c9a0710b6225d6
    Fixes: bz#1730715
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit dafab9fd5e4afe0f1cdd8d2e3ce7b4037faf4830
Author: MPLX <mplx+redhat@donotreply.at>
Date:   Thu Jul 18 12:13:09 2019 +0530

    extras/mount-shared-storage.sh: consider options to mount
    
    If different mount options are given to glusterfs in /etc/fstab, it
    was not considered in the script.
    
    Fixes: bz#1690454
    Change-Id: If829b3d6ab79755647626edcb31f38a3716989db
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8a84a2ca7e70c0682d3f0f1f83892914725db59c
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu Jun 27 13:18:32 2019 +0530

    gluster-block: tuning perf options
    
    As per the perf experiment run by Elvir, with NVME devices used for OCP (gluster)
    it was seen that particularly read operations (read/randread) benefited from
    these options.
    
    Change-Id: Ibec4b96afd28e6f7e757b6ef203ccdbc0d9854d5
    Fixes: bz#1727852
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>

commit 70a735b75ac8ca942b212cc1c56441e9387f30e6
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Jul 8 11:34:49 2019 +0530

    core: use more restrictive mode while creating the directories
    
    fixes: bz#1724024
    
    Change-Id: I539fb7248b2cfc037ec29f1413ea648f9ec21ef2
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 2aa731a259ea457c07494e3c3edf6d5f7c02fe77
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jul 22 17:35:21 2019 +0530

    geo-rep: Fix mount broker setup issue
    
    The patch [1] added validation in gverify.sh to check if the gluster
    binary on slave by executing gluster directly on slave.  But for
    non-root users, even though gluster binary is present, path is not
    found when executed via ssh. Hence validate the gluster binary using
    bash builtin 'type' command.
    
    [1] https://review.gluster.org/19224
    
    Change-Id: I93ca62c0c5b1e16263e586ddbbca8407d60ca126
    fixes: bz#1731920
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit f4480d6369098869a5a5f53a39ea0da7f152d227
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jul 22 10:23:56 2019 +0530

    backup-volfile-server: ignore duplicate entries
    
    Erroring out for duplicate entries for backup_volfile_servers would
    cause failures for some script. This option is harmless if it is
    duplicate, we just need to ignore this.
    
    Fixes: bz#1730953
    Change-Id: I950064501a7bb61b90e99f2c079564f9c923d4c1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8f7112264f76306a12eb29fffc458ef4f657689e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 22 20:55:33 2019 +0530

    features/utime: Fix mem_put crash
    
    Problem:
    When frame->local is not null FRAME_DESTROY calls mem_put on it.
    Since the stub is already destroyed in call_resume(), it leads
    to crash
    
    Fix:
    Set frame->local to NULL before calling call_resume()
    
    fixes: bz#1593542
    Change-Id: I0f8adf406f4cefdb89d7624ba7a9d9c2eedfb1de
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 5c20a688fd2408ff8dcc66fd8ebc935e228dd803
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Jun 2 21:14:18 2019 +0300

    (multiple files) use dict_allocate_and_serialize() where applicable.
    
    This function does length, allocation and serialization for you.
    
    Change-Id: I142a259952a2fe83dd719442afaefe4a43a8e55e
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 06e92a2ee437c1a81c815129b1d188af0b4fa84e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 24 13:06:49 2019 +0530

    ctime: Set mdata xattr on legacy files
    
    Problem:
    The files which were created before ctime enabled would not
    have "trusted.glusterfs.mdata"(stores time attributes) xattr.
    Upon fops which modifies either ctime or mtime, the xattr
    gets created with latest ctime, mtime and atime, which is
    incorrect. It should update only the corresponding time
    attribute and rest from backend
    
    Solution:
    Creating xattr with values from brick is not possible as
    each brick of replica set would have different times.
    So create the xattr upon successful lookup if the xattr
    is not created
    
    Note To Reviewers:
    The time attributes used to set xattr is got from successful
    lookup. Instead of sending the whole iatt over the wire via
    setxattr, a structure called mdata_iatt is sent. The mdata_iatt
    contains only time attributes.
    
    Change-Id: I5e535631ddef04195361ae0364336410a2895dd4
    fixes: bz#1593542
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 74f124619a71df9bdc5ae9fbc07bc19db05bc1d2
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Tue Jul 2 15:00:25 2019 +0530

    geo-rep: Test case for upgrading config file
    
    Added test case for the patch
    https://review.gluster.org/#/c/glusterfs/+/22894/4
    
    Also updated if else structure in gsyncdconfig.py to avoid
    repeated occurance of values in new configfile.
    
    fixes: bz#1707731
    Change-Id: If97e1d37ac52dbd17d47be6cb659fc5a3ccab6d7
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 41f72ac9453c24bea85709203948c41c5772edec
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Jul 16 10:31:46 2019 +0530

    dht: log getxattr failure for node-uuid at "DEBUG"
    
    There are two ways to fetch node-uuid information from dht.
    
    1 - #define GF_XATTR_LIST_NODE_UUIDS_KEY "trusted.glusterfs.list-node-uuids"
    This key is used by AFR.
    
    2 - #define GF_REBAL_FIND_LOCAL_SUBVOL "glusterfs.find-local-subvol"
    This key is used for non-afr volume type.
    
    We do two getxattr operations. First on the #1 key followed by on #2 if
    getxattr on #1 key fails.
    
    Since the parent function "dht_init_local_subvols_and_nodeuuids" logs failure,
    moving the log-level to DEBUG in dht_find_local_subvol_cbk.
    
    fixes: bz#1730175
    Change-Id: I4d88244dc26587b111ca5b00d4c00118efdaac14
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 477bbe36dc2a05e00ffb137450fa18a0aba8bf6a
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Jul 11 18:57:13 2019 +0800

    cluster/ec: skip updating ctx->loc again when ec_fix_open/opendir
    
    The ec_manager_open/opendir memsets ctx->loc which causes
    memory/inode leak, and ec_fheal uses ctx->loc out of fd->lock
    that loc_copy may copy bad data when memset it.
    
    This patch skips updating ctx->loc when it is initilizaed.
    With it, ctx->loc is filled once, and never updated.
    
    Change-Id: I3bf5ffce4caf4c1c667f7acaa14b451d37a3550a
    fixes: bz#1729772
    Signed-off-by: Kinglong Mee <mijinlong@horiscale.com>

commit 11de436ba7ef4cc1f583609f2482b1008607d410
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Jul 3 20:47:52 2019 +0300

    logging.c: check for skip_logging() in _gf_slog(), _gf_smsg()
    
    Before processing anything, check if we actually need to do any logging,
    based on the log level.
    
    Change-Id: Iec5b9869831e1bdf22d12becc5e3d3ece87906a7
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 47e9658fd9014d9a4b67718aa9fbbdf11bf93c0e
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Mon Jul 8 21:13:28 2019 +0800

    cluster/ec: inherit healing from lock when it has info
    
    If lock has info, fop should inherit healing mask from it.
    Otherwise, fop cannot inherit right healing when changed_flags is zero.
    
    Change-Id: Ife80c9169d2c555024347a20300b0583f7e8a87f
    fixes: bz#1727081
    Signed-off-by: Kinglong Mee <mijinlong@horiscale.com>

commit 7162c8ad9d404773656b4eb02c8fc17f067e7699
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Jun 5 20:16:40 2019 +0300

    cli: defer create_frame() (and dict creation) to later stages.
    
    Where possible, defer create_frame() - whenever possible, after
    command line verification, for example.
    
    Change-Id: Id6606e90e7ea6190f30b225c4733b229c519bb2f
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 6bf9637a93011298d032332ca93009ba4e377e46
Author: Homma <homma@allworks.co.jp>
Date:   Fri Jul 5 16:10:41 2019 +0530

    system/posix-acl: update ctx only if iatt is non-NULL
    
    We need to safe-guard against possible zero'ing out of iatt
    structure in acl ctx, which can cause many issues.
    
    fixes: bz#1668286
    Change-Id: Ie81a57d7453a6624078de3be8c0845bf4d432773
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 30f54b702a82c45a31aeb58fabe5b79fb62cc37b
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Jul 15 11:51:58 2019 +0530

    tests: Fix bug-1717819-metadata-split-brain-detection.t failure
    
    Problem:
    tests/bugs/replicate/bug-1717819-metadata-split-brain-detection.t fails
    intermittently in test cases #49 & #50, which compare the values of the
    user set xattr values after enabling the heal. We are not waiting for
    the heal to complete before comparing those values, which might lead
    those tests to fail.
    
    Fix:
    Wait till the HEAL-TIMEOUT before comparing the xattr values.
    Also cheking for the shd to come up and the bricks to connect to the shd
    process in another case.
    
    Change-Id: I0e245b328da9df23ce70c5300278fad1c1d9f7ff
    Fixes: bz#1729847
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit ea40178dcc540535e1059a9433f74a30de76f03b
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Apr 20 19:11:33 2019 +0300

    dht-common.h: reorder variables to reduce padding.
    
    Manually added '-Wpadded' to get warnings on padding, and reordered
    structs to reduce most of them.
    
    Change-Id: I0c505fcb3dfef76399ac9d5d33bfb235354532de
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit a263b22904036c04b52b1555239ae841f676a564
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Jul 4 13:21:33 2019 +0200

    core: fix deadlock between statedump and fd_anonymous()
    
    There exists a deadlock between statedump generation and fd_anonymous()
    function because they are acquiring inode table lock and inode lock in
    reverse order.
    
    This patch modifies fd_anonymous() so that it takes inode lock only when
    it's really necessary, avoiding the deadlock.
    
    Change-Id: I24355447f0ea1b39e2546782ad07f0512cc381e7
    Fixes: bz#1727068
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit d509f480b2d85dc86f027edc4c9badf79b5eb62f
Author: Liguang Li <liguang.lee6@gmail.com>
Date:   Fri Jun 21 12:18:58 2019 +0800

    Detach iot_worker to release its resources
    
    When iot_worker terminates, its resources have not been reaped, which
    will consumes lots of memory.
    
    Detach iot_worker to automically release its resources back to the
    system.
    
    fixes: bz#1729107
    Change-Id: I71fabb2940e76ad54dc56b4c41aeeead2644b8bb
    Signed-off-by: Liguang Li <liguang.lee6@gmail.com>

commit b917974ee922d7a2e079692ad7d6f61f900b37b2
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Jul 12 16:28:04 2019 +0530

    glusterd: do not mark skip_locking as true for geo-rep operations
    
    We need to send the commit req to peers in case of geo-rep
    operations even though it is a no volname operation. In commit
    phase peers try to set the txn_opinfo which will fail because
    it is a no volname operation where we don't require a commit
    phase. We mark skip_locking as true for no volname operations,
    but we have to give an exception to geo-rep operations, so that
    they can set txn_opinfo in commit phase.
    
    Please refer to detailed RCA at the bug: 1729463
    
    fixes: bz#1729463
    
    Change-Id: I9f2478b12a281f6e052035c0563c40543493a3fc
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 6d94a332ebafbda598d50efcd64429af563dae30
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jul 10 12:34:34 2019 +0530

    Fix spelling errors
    
    Fixes: bz#1728554
    Change-Id: I88357aed7c14988a12616035c3738c32c09a8f9a
    Signed-off-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 8f37561d665b6a70b2b4bd8afab12affb1805148
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 12 16:12:18 2019 +0530

    ibverbs/rdma: remove from build
    
    We have proposed about this an year ago, and with recent smoke
    failures, it looks like the right time to take such call.
    
    ref: https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    With this, glusterfs-8.0 wouldn't have rdma feature, and would
    allow some modularity changes possible with rpc layer (as we would
    have just 1 transport)
    
    Updates: bz#1635688
    Change-Id: Ia277dca4d4b1f0cffae20819024a52b075b775e5
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8e795617fd6f5193d0d52a336059ce1a28108c0e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 2 16:50:23 2019 -0400

    features/snapview-server: obtain the list of snapshots inside the lock
    
    The current list of snapshots from priv->dirents is obtained outside
    the lock.
    
    Change-Id: I8876ec0a38308da5db058397382fbc82cc7ac177
    Fixes: bz#1726783

commit 3ef02e82f84e20edaa8ad4cbe921108319ec8ba2
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Jun 26 12:19:07 2019 +0530

    cluster/ta: Notify the clients only if there are pending heals
    
    Problem:
    In case of thin arbiter, before index healer starts crawling the
    indices at every heal-timeout interval, even if there is nothing to
    be healed it will send an upcall notification to all the clients to
    release any AFR_TA_DOM_NOTIFY locks that they hold. SHD will wait
    for the upcall to return before proceeding with the heal even though
    there is nothing to be healed. This will also invalidates the cached
    information about the bricks states on the clients which leads to
    extra calls on TA from clients for the next reads & writes if needed.
    This will impact the IO performance.
    
    Fix:
    - Before sending the upcall to the clients, check for any pending heals
    on TA without taking  any locks.
    - If there is nothing marked bad on TA, then continue with the index
    crawl to heal any dirty markings present on the files due to any post-op
    failure.
    - If there is a brick marked as bad on TA, then take the
    AFR_TA_DOM_NOTIFY lock on TA from SHD, get the state on TA and
    continue with the current healing process.
    
    Change-Id: Ieb477bc6cb18bbdfd4e7a0453c5ed79b574ec9d6
    fixes: bz#1724184
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 1a38a6f4853f87ac4e45240579581292290f4f27
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Jun 12 11:57:02 2019 +0530

    cluster/afr: Fix incorrect reporting of gfid & type mismatch
    
    Problems:
    1. When checking for type and gfid mismatch, if the type or gfid
    is unknown because of missing gfid handle and the gfid xattr
    it will be reported as type or gfid mismatch and the heal will
    not complete.
    
    2. If the source selected during entry heal has null gfid the same
    will be sent to afr_lookup_and_heal_gfid(). In this function when
    we try to assign the gfid on the bricks where it does not exist,
    we are considering the same gfid and try to assign that on those
    bricks. This will fail in posix_gfid_set() since the gfid sent
    is null.
    
    Fix:
    If the gfid sent to afr_lookup_and_heal_gfid() is null choose a
    valid gfid before proceeding to assign the gfid on the bricks
    where it is missing.
    
    In afr_selfheal_detect_gfid_and_type_mismatch(), do not report
    type/gfid mismatch if the type/gfid is unknown or not set.
    
    Change-Id: Ia06552e4dc4a9f89cb7f5302833604bd21bbf7da
    fixes: bz#1722507
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 3c1efa0c92445638bbfa57c2e868c79f7d987fc3
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Jun 20 15:50:01 2019 -0700

    Replace usleep() with nanosleep()
    
    As usleep has been obsoleted, changed all invocations of usleep
    to nanosleep. From man 3 usleep:
    
    "4.3BSD, POSIX.1-2001.  POSIX.1-2001 declares this function
     obsolete; use nanosleep(2) instead. POSIX.1-2008 removes the
     specification of usleep()."
    
    Added a helper function gf_nanosleep() to have a single place
    for handling edge cases that might arise from the conversion of
    usleep to nanosleep and allow the sleep to resume with right
    remaining value upon being interrupted.
    
    Fixes: bz#1721686
    
    Change-Id: Ia39ab82c9e0f4669d2c00d4cdf25e38d94ef9f62
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit b82743a5822626e83b233956803421fda9b1c3f9
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Jul 9 16:32:36 2019 -0700

    Remove hadoop related code from the codebase
    
    As Hadoop is no longer supported, dropping code for
    handling Hadoop access.
    
    Fixes: bz#1728417
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Change-Id: I8fcf4faacb364f1c9a8abb0c48faec337087f845

commit ad828d2e0c930b31b870c92fbaeac7a43fee08da
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Thu Jul 4 19:03:34 2019 +0530

    [geo-replication] geo-replication/setup.py missing license details in setup()
    
    geo-replication/setup.py is missing license details in
    setup() and is using string 'syncdaemon' instead
    of using the variable name which has the same value.
    
    Present:
    setup(
        name=name,
        version="",
        description='GlusterFS Geo Replication',
        license='',
        author='Red Hat, Inc.',
        author_email='gluster-devel@gluster.org',
        url='http://www.gluster.org',
        packages=['syncdaemon', ],
        test_suite='nose.collector',
        install_requires=[],
        scripts=[],
        entry_points={},
    )
    
    Changing to:
    setup(
        name=name,
        version="",
        description='GlusterFS Geo Replication',
        license='GPLV2 and LGPLV3+',
        author='Red Hat, Inc.',
        author_email='gluster-devel@gluster.org',
        url='http://www.gluster.org',
        packages=[name, ],
        test_suite='nose.collector',
        install_requires=[],
        scripts=[],
        entry_points={},
    )
    
    fixes: bz#1727107
    
    Change-Id: I742c4c510da55a22256c819da7e2fc9622119f63
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit c2e514c18df8fe1dfe06bc147f94756838f67c41
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun May 5 13:19:31 2019 +0530

    rpc/xdr: include nfs specific files in build only if gNFS is enabled
    
    updates: bz#1193929
    Change-Id: I2b85fd0a04c77815a154f445ec8fb4da37dcbe40
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 670299cf4fc90c1c61032057b6ff570fee7a448e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Jun 24 12:00:20 2019 +0530

    glusterd/svc: update pid of mux volumes from the shd process
    
    For a normal volume, we are updating the pid from a the
    process while we do a daemonization or at the end of the
    init if it is no-daemon mode. Along with updating the pid
    we also lock the file, to make sure that the process is
    running fine.
    
    With brick mux, we were updating the pidfile from gluterd
    after an attach/detach request.
    
    There are two problems with this approach.
    1) We are not holding a pidlock for any file other than parent
       process.
    2) There is a chance for possible race conditions with attach/detach.
       For example, shd start and a volume stop could race. Let's say
       we are starting an shd and it is attached to a volume.
       While we trying to link the pid file to the running process,
       this would have deleted by the thread that doing a volume stop.
    
    Change-Id: I29a00352102877ce09ea3f376ca52affceb5cf1a
    Updates: bz#1722541
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit a94d7433169cbf29b9109c96ac57b99e898e6f17
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Mon Jul 8 15:09:39 2019 +0530

    posix: fix Wformat-overflow warning
    
    warning: ‘%s’ directive argument is null
    
    Change-Id: I2ce9560f98a8310886c31384e40c2e101ad2c719
    updates: bz#1193929
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit d0d77953ed4020a8c7ac87073bd5e6c4743bc961
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Fri Jul 5 16:51:45 2019 +0530

    glusterd: fix packed member address warning
    
    warning: taking address of packed member of
    ‘struct _quota_limits’ may result in an
    unaligned pointer value.
    
    Change-Id: Ib889c99184560f0d24dbcc4fae10b563a2b9b7fd
    updates: bz#1193929
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 4c44c47a40910c70e7d22d2bc6b7c21b88e3296b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 9 19:02:53 2019 +0530

    quick-read: rename cache-invalidation key to avoid redundant keys
    
    With group-metadata-cache group profile settings
    performance.cache-invalidation option when turned on enables both md-cache
    and quick-read xlator's cache-invalidation feature. While the intent of
    the group-metadata-cache is to set md-cache xlator's cache-invalidation
    feature, quick-read xlator also gets affected due to the same. While
    md-cache feature and it's profile existed since release-3.9,
    quick-read cache-invalidation was introduced in release-4 and due to
    this op-version mismatch on any cluster which is >= glusterfs-4 when
    this group profile is applied it breaks backward compatibility with the
    old clients.
    
    The proposed fix here is to rename the key in quick-read to
    'quick-read-cache-invalidation' so that both these features have
    distinct identification. While this brings in by itself a backward
    compatibility challenge where this feature is enabled in an existing
    cluster and when the same is upgraded to a version where this change
    exists, it will lead to an unidentified old key. But as a workaround we
    can always ask users upgrading to release-7 version to turn off this
    option, upgrade the cluster and turn it back on with the new key. This
    needs to be documented once the patch is accepted.
    
    Fixes: bz#1698042
    Change-Id: I30422ba6496208e21191a8d78ad29b2e21078664
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 99d210a704d2e85c95fac5edcf435bd059aad368
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Fri Jul 5 15:16:23 2019 +0800

    gnfs: use strcpy to prevent memory overflow
    
    fixes: bz#1727248
    Change-Id: Iea289032a8feecf2945668d3fb44a6a53089fdea
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit e21544483c25908e9ed142480e9753d646d53605
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Jun 21 14:24:42 2019 +0300

    glusterd.h: align structs
    
    Move some variables around to reduce compiler padding.
    
    Change-Id: I9cd53ce257fb169270c295ac60d58d4a6a950d4f
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit af989db23d1db00e087f2b9d3dfc43b13ef17153
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Jul 3 15:22:38 2019 +0530

    glusterd: Show the correct brick status in get-state
    
    Problem: get-state does not show correct brick status if brick
             status is not Started, it always shows started if any value
             is set brickinfo->status
    
    Solution: Check the value of brickinfo->status to show correct status
              in get-state
    
    Change-Id: I12a79619024c2cf59f338220d144f2f034059b3b
    fixes: bz#1726906
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 7d270d05f835d41e32572501246b50181dc9be56
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Jul 2 15:23:00 2019 +0530

    glusterd: don't log a warning message for tier-enabled key
    
    We are logging a warning message saying unknown-key for
    tier-enabled kay. although the tier xlator is deprecated,
    this key is left behind for handling the peer rejection
    issues in a heterogeneous cluster. We need not to log if
    this key is not found/recognised.
    
    updates: bz#1193929
    
    Change-Id: Ia68661898a618f99a240ca8d8a124ff6a65ebe9d
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 36f6e6df0ff15d0464b869803710adca2b65e8ba
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jun 25 10:51:33 2019 -0400

    features/snapview-server: use the same volfile server for gfapi options
    
    snapview server xlator makes use of "localhost" as the volfile server while
    initing the new glfs instance to talk to a snapshot. While localhost is fine,
    better use the same volfile server that was used to start the snapshot
    daemon containing the snapview-server xlator.
    
    Change-Id: I4485d39b0e3d066f481adc6958ace53ea33237f7
    fixes: bz#1725211
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 532b0fc8b1ace9ad48fdaf643e0b1a34020b6cd8
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jun 21 09:04:19 2019 +0530

    cluster/dht:  Fixed a memleak in dht_rename_cbk
    
    Fixed a memleak in dht_rename_cbk when creating
    a linkto file.
    
    Change-Id: I705adef3cb79e33806520fc2b15558e90e2c211c
    fixes: bz#1722698
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 080827829eabd3cbed1a7feaa37de091834fcbb1
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Mon Jul 1 20:48:31 2019 +0530

    cli: Remove Wformat-truncation compiler warning
    
    This warning is issued due to unhandled output truncation.
    As in the code, truncation is expected, we can remove this
    warning by placing a check on the return value of the function
    and handling it.
    In this way, the warning will not be issued.
    
    Change-Id: I1820b58fe9a7601961c20944b259df322db35057
    updates: bz#1193929
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit cbc234d9ddfb7e2f0089d7ba9d1dd81b0367ba8f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jun 24 19:24:05 2019 +0530

    glusterfs-fops: fix the modularity
    
    glusterfs-fops.h was moved to rpc/xdr to support compound fops.
    (ref: https://review.gluster.org/14032, 2f945b86d3)
    
    This was fine as long as all these header files were in single
    include directory after 'install'. With the move to separate out
    glusterfs specific header files into another directory inside
    /usr/include (ref: https://review.gluster.org/21746, 20ef211cfa),
    glusterfs-fops.h file was not in the proper path when an external
    .c file tried to include any of glusterfs specific .h file (like
    xlator.h).
    
    Now, we have removed compound-fops, with that, none of the enums
    declared in glusterfs-fops.h are actually getting used on wire
    anymore. Hence, it makes sense to get this to libglusterfs/src
    as a single point of definition. With this change, the external
    programs can use glusterfs header files.
    
    also remove some enum definitions which are not used in code
    anymore.
    
    Updates: bz#1636297
    Change-Id: I423c44d3dbe2efc777299c544ece3cb172fc7e44
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c72b3f13452fcd9289230516f67d7c07951a8d5c
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Fri Jun 28 15:32:31 2019 +0530

    Removing one top command from gluster v help
    
    The current help show 2 different top commands
    intead of one single top command which can be
    easily observed when "# gluster v help" command
    is issued. Removing one "volume top <VOLNAME>"
    and clubbing into them into a single command.
    
    Current help:
    volume top <VOLNAME> {open|read|write|opendir|readdir|clear}
    [nfs|brick <brick>] [list-cnt <value>] |
    volume top <VOLNAME> {read-perf|write-perf}
    [bs <size> count <count>] [brick <brick>]
    [list-cnt <value>] - volume top operations
    
    Expected help:
    volume top <VOLNAME> {open|read|write|opendir|readdir|clear}
    [nfs|brick <brick>] [list-cnt <value>] | {read-perf|write-perf}
    [bs <size> count <count>] [brick <brick>] [list-cnt <value>]
    - volume top operations
    
    fixes: bz#1725034
    
    Change-Id: Ifbc4c95f2558286e27dfc5e9667046b80eb1715d
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit a194e4dc78c50605e5178e56976227ccefb8cdb1
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Jun 17 17:54:01 2019 +0530

    core: use multiple servers while mounting a volume using ipv6
    
    According to man page:
    mount -t glusterfs [-o <options>] <server1>,<server2>,
                  <server3>,..<serverN>:/<volname>[/<subdir>] <mount_point>
    
    When we try
    
    mount -t glusterfs 52:54:00:23:5a:b6,52:54:00:a0:be:ed:/ta-vol1 /mnt/ta
    
    we see the below msg in log:
    
    [2019-06-17 11:41:36.085809] I [MSGID: 100030] [glusterfsd.c:2867:main] 0-/usr/local/sbin/glusterfs: Started running /usr/local/sbin/glusterfs version 7dev (args: /usr/local/sbin/glusterfs --process-name fuse --volfile-server=52:54:00:23:5a --volfile-id=/ta-vol1 /mnt/ta)
    
    With this change, we'll able to give multiple volfile servers
    while mounting the volume using ipv6.
    
    After the change, I see the following in log:
    
    [2019-06-17 12:00:21.183658] I [MSGID: 100030] [glusterfsd.c:2867:main] 0-/usr/local/sbin/glusterfs: Started running /usr/local/sbin/glusterfs version 7dev (args: /usr/local/sbin/glusterfs --process-name fuse --volfile-server=52:54:00:23:5a:b6 --volfile-server=52:54:00:a0:be:ed --volfile-id=/ta-vol1 /mnt/ta)
    
    fixes: bz#1719290
    
    credits: Aga <aga_1990@hotmail.com>
    
    Change-Id: Icf89bea3ba15d8374ef428aeb59f2ef55ad544ec
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 6fbf323d5f72db879d733af5ba9c67c7a1bfec63
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jun 27 10:49:30 2019 +0530

    glusterd: fix clang scan defects
    
    Fixes following:
    https://build.gluster.org/job/clang-scan/744/clangScanBuildBugs/browse/report-dd8d31.html#EndPath
    https://build.gluster.org/job/clang-scan/744/clangScanBuildBugs/browse/report-89a1cd.html#EndPath
    
    Updates: bz#1622665
    Change-Id: Ibd201fb2ca54ae7ae3fed8a8d87815358b614349
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 22e2d990dbbea878dba5569cc2d0df33955913b1
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Jun 26 16:23:15 2019 +0200

    rfc.sh: Improve bug identification
    
    When a backport is done and there is more than one bug reference in the
    commit message (normally we include the old bug reference in the commit
    message), old rfc.sh may choose the incorrect bug id.
    
    This patch improves the regular expression to locate the bug id.
    
    Updates: bz#1193929
    Change-Id: Ifaa4e50c0ddba21c16ef0c5a1f6d46c315cf3378
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 9b223b15ab69fce4076de036ee162f36a058bcd2
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Wed Apr 24 13:37:16 2019 +0530

    glusterd/thin-arbiter: Thin-arbiter integration with GD1
    
    gluster volume create <VOLNAME> replica 2 thin-arbiter 1 <host1>:<brick1> <host2>:<brick2>
    <thin-arbiter-host>:<path-to-store-replica-id-file> [force]
    
    The changes have been made in a way that the last brick in the bricks list
    will be treated as the thin-arbiter.
    GD1 will be manipulated to consider replica count to be as 2 and continue creating the
    volume like any other replica 2 volume but since thin-arbiter volumes need ta-brick
    client xlator entries for each subvolume in fuse volfile, volfile generation is
    modified in a way to inject these entries seperately in the volfile for every subvolume.
    
    Few more additions -
    1- Save the volinfo with new fields ta_bricks list and thin_arbiter_count.
    2- Introduce a new option client.ta-brick-port to add remote-port to ta-brick xlator entry
       in fuse volfiles. The option can be set using the following CLI syntax -
       gluster volume set <VOLNAME> client.ta-brick-port <PORTNO.>
    3- Volume Info will contain a Thin-Arbiter-path entry to distinguish
       from other replicate volumes.
    
    Change-Id: Ib434e2313b29716f32476c6c211d282c4ef39406
    Updates #687
    Signed-off-by: Vishal Pandey <vpandey@redhat.com>

commit 29ad22aa9482a69f3fcf04eea762e76602bbe9a0
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Jun 20 18:47:45 2019 +0530

    geo-rep : fix gluster command path for non-root session
    
    Problem:
    gluster command not found.
    
    Cause:
    In Volinfo class we issue command 'gluster vol info' to get information
    about volume like getting brick_root to perform various operation.
    When geo-rep session is configured for non-root user Volinfo class
    fails to issue gluster command due to unavailability of gluster
    binary path for non-root user.
    
    Solution:
    Use config value 'slave-gluster-command-dir'/'gluster-command-dir' to get path
    for gluster command based on caller.
    
    fixes: bz#1722740
    
    Change-Id: I4ec46373da01f5d00ecd160c4e8c6239da8b3859
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit d4a4c4284317f3a51e2edfc218bfd030103f1110
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Jun 26 17:34:23 2019 +0200

    run-tests.sh: stop test on Ctrl-C
    
    When a test is run through 'timeout' command, Ctrl-C becomes useless and
    the test cannot be stopped.
    
    Added '--foreground' option to 'timeout' command that makes it possible
    to use Ctrl-C.
    
    Updates: bz#1193929
    Change-Id: I160984d1aba470e3a4a1135bd5fa57471046f52f
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit efa8477013d98a26283302ecb42d4ba606ce405e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Jun 27 19:17:29 2019 +0530

    graph/shd: Use top down approach while cleaning xlator
    
    We were cleaning xlator from botton to top, which might
    lead to problems when upper xlators trying to access
    the xlator object loaded below.
    
    One such scenario is when fd_unref happens as part of the
    fini call which might lead to calling the releasedir to
    lower xlator. This will lead to invalid mem access
    
    Change-Id: I8a6cb619256fab0b0c01a2d564fc88287c4415a0
    Updates: bz#1716695
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 5d66eafec581fb3209af74595784be8854ca40a4
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Jun 4 19:22:45 2019 +0530

    protocol/client: propagte GF_EVENT_CHILD_PING only for connections to brick
    
    Two reasons:
    * ping responses from glusterd may not be relevant for Halo
      replication. Instead, it might be interested in only knowing whether
      the brick itself is responsive.
    * When a brick is killed, propagating GF_EVENT_CHILD_PING of ping
      response from glusterd results in GF_EVENT_DISCONNECT spuriously
      propagated to parent xlators. These DISCONNECT events are from the
      connections client establishes with glusterd as part of its
      reconnect logic. Without GF_EVENT_CHILD_PING, the last event
      propagated to parent xlators would be the first DISCONNECT event
      from brick and hence subsequent DISCONNECTS to glusterd are not
      propagated as protocol/client prevents same event being propagated
      to parent xlators consecutively. propagating GF_EVENT_CHILD_PING for
      ping responses from glusterd would change the last_sent_event to
      GF_EVENT_CHILD_PING and hence protocol/client cannot prevent
      subsequent DISCONNECT events
    
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1716979
    Change-Id: I50276680c52f05ca9e12149a3094923622d6eaef

commit 7d8be567f2f904fc74d0990ebce2e8afbedab918
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Jun 26 15:58:33 2019 +0530

    posix : add posix_set_ctime() in posix_ftruncate()
    
    Change-Id: I0cb5320fea71306e0283509ae47024f23874b53b
    fixes: bz#1723761
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit e8f8d16fc4b8e5be48f4d7c9ff9d170934ffb7fc
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Jun 24 15:49:04 2019 +0530

    graph/shd: Use glusterfs_graph_deactivate to free the xl rec
    
    We were using glusterfs_graph_fini to free the xl rec from
    glusterfs_process_volfp as well as glusterfs_graph_cleanup.
    
    Instead we can use glusterfs_graph_deactivate, which is does
    fini as well as other common rec free.
    
    Change-Id: Ie4a5f2771e5254aa5ed9f00c3672a6d2cc8e4bc1
    Updates: bz#1716695
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit f782881f825efcd4ab3b74209c1c7aca3796023b
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Wed May 29 16:49:01 2019 +0530

    geo-rep: Upgrading config file to new version
    
    - configuration handling is enhanced with patch
    https://review.gluster.org/#/c/glusterfs/+/18257/
    - hence, the old configurations are not applied when
    Geo-rep session is created in the old version and upgraded.
    
    This patch solves the issue. It,
    - checks if the config file is old.
    - parses required values from old config file and stores in new
      config file, which ensures that configerations are applied on
      upgrade.
    - stores old config file as backup.
    - handles changes in options introduced in
      https://review.gluster.org/#/c/glusterfs/+/18257/
    
    fixes: bz#1707731
    Change-Id: Iad8da6c1e1ae8ecf7c84dfdf8ea3ac6966d8a2a0
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 5cbc87d8b8f1287e81c38b793b8d13b057208c62
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Wed Jun 19 15:08:58 2019 +0530

    posix: modify storage.reserve option to take size and percent
    
    * reverting changes made in
    https://review.gluster.org/#/c/glusterfs/+/21686/
    
    * Now storage.reserve can take value in percent or bytes
    
    fixes: bz#1651445
    Change-Id: Id4826210ec27991c55b17d1fecd90356bff3e036
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 1716a907da1a835b658740f1325033d7ddd44952
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Jun 21 11:28:08 2019 +0200

    core: fix memory allocation issues
    
    Two problems have been identified that caused that gluster's memory
    usage were twice higher than required.
    
    1. An off by 1 error caused that all objects allocated from the memory
       pools were taken from a pool bigger than required. Since each pool
       corresponds to a size equal to a power of two, this was wasting half
       of the available memory.
    
    2. The header information used for accounting on each memory object was
       not taken into consideration when searching for a suitable memory
       pool. It was added later when each individual block was allocated.
       This made this space "invisible" to memory accounting.
    
    Credits: Thanks to Nithya Balachandran for identifying this problem and
             testing this patch.
    
    Fixes: bz#1722802
    Change-Id: I90e27ad795fe51ca11c13080f62207451f6c138c
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit dc1b87fcfef08c9497b0c02b2410c9d18bbc2dba
Author: Michael Adam <obnox@samba.org>
Date:   Thu Jun 20 13:09:37 2019 +0200

    [RFC] change get_real_filename implementation to use ENOATTR instead of ENOENT
    
    get_real_filename is implemented as a virtual extended attribute to help
    Samba implement the case-insensitive but case preserving SMB protocol
    more efficiently. It is implemented as a getxattr call on the parent directory
    with the virtual key of "get_real_filename:<entryname>" by looking for a
    spelling with different case for the provided file/dir name (<entryname>)
    and returning this correct spelling as a result if the entry is found.
    Originally (05aaec645a6262d431486eb5ac7cd702646cfcfb), the
    implementation used the ENOENT errno to return the authoritative answer
    that <entryname> does not exist in any case folding.
    
    Now this implementation is actually a violation or misuse of the defined
    API for the getxattr call which returns ENOENT for the case that the dir
    that the call is made against does not exist and ENOATTR (or the synonym
    ENODATA) for the case that the xattr does not exist.
    
    This was not a problem until the gluster fuse-bridge was changed
    to do map ENOENT to ESTALE in 59629f1da9dca670d5dcc6425f7f89b3e96b46bf,
    after which we the getxattr call for get_real_filename returned an
    ESTALE instead of ENOENT breaking the expectation in Samba.
    
    It is an independent problem that ESTALE should not leak out to user
    space but is intended to trigger retries between fuse and gluster.
    But nevertheless, the semantics seem to be incorrect here and should
    be changed.
    
    This patch changes the implementation of the get_real_filename virtual
    xattr to correctly return ENOATTR instead of ENOENT if the file/directory
    being looked up is not found.
    
    The Samba glusterfs_fuse vfs module which takes advantage of the
    get_real_filename over a fuse mount will receive a corresponding change
    to map ENOATTR to ENOENT. Without this change, it will still work
    correctly, but the performance optimization for nonexisting files is
    lost. On the other hand side, this change removes the distinction
    between the old not-implemented case and the implemented case.
    So Samba changed to treat ENOATTR like ENOENT will not work correctly
    any more against old servers that don't implement get_real_filename.
    I.e. existing files will be reported as non-existing
    
    Change-Id: I971b427ab8410636d5d201157d9af70e0d075b67
    fixes: bz#1722977
    Signed-off-by: Michael Adam <obnox@samba.org>

commit cfc30c15ba54fa91cfa8c62b961553b416bb9ff7
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Jun 6 08:12:34 2019 +0200

    locks: enable notify-contention by default
    
    This patch enables the lock contention notification by default.
    
    Change-Id: I10131b026a7cb09fc7c93e1e6c8549988c1d7751
    Fixes: bz#1717754
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 323389858562f28f16ec2e32e0160140f7d76668
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jun 20 11:19:47 2019 -0400

    statedump: dump the minimum and maximum latency seen by each xlator
    
    Change-Id: Ie9661282694eb9dcfb0d0bc6af512610e02f7347
    fixes: bz#1722598
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit f36086db87aae24c10abde434f081d78b942735e
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue Jun 25 18:00:06 2019 +0200

    glusterd: fix use-after-free of a dict_t
    
    A dict was passed to a function that calls dict_unref() without taking
    any additional reference. Given that the same dict is also used after
    the function returns, this was causing a use-after-free situation.
    
    To fix the issue, we simply take an additional reference before calling
    the function.
    
    Fixes: bz#1723890
    Change-Id: I98c6b76b08fe3fa6224edf281a26e9ba1ffe3017
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 40c18b189f31a87b5c5f9344c4a0ab44cb61ef75
Author: Kinglong Mee <mijinlong@horiscale.com>
Date:   Mon May 13 16:42:01 2019 +0800

    gfapi: set right pargfid according to parent's inode
    
    EC updates parent's inode from loc, when pargfid is not the parent's inode's,
    a warnning message is print, and an error is returned to up xlator.
    
    [ec-helpers.c:400:ec_loc_gfid_check] 0-openfs1-disperse-0: Mismatching GFID's in loc
    
    Change-Id: Ie8036be91f039083a1e3fe17ec235a222df84b97
    fixes: bz#1723280
    Signed-off-by: Kinglong Mee <mijinlong@horiscale.com>

commit d58594d802d617ed81b8f991fd312c224f1f85d4
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Apr 30 15:38:55 2019 -0400

    * core: do not assert in inode_unref if the inode table cleanup has started
    
    There is a good chance that, the inode on which unref came has already been
    zero refed and added to the purge list. This can happen when inode table is
    being destroyed (glfs_fini is something which destroys the inode table).
    
    Consider a directory 'a' which has a file 'b'. Now as part of inode table destruction
    zero refing of inodes does not happen from leaf to the root. It happens in the order
    inodes are present in the list. So, in this example, the dentry of 'b' would have its
    parent set to the inode of 'a'. So if 'a' gets zero refed first (as part of
    inode table cleanup) and then 'b' has to zero refed, then dentry_unset is called on
    the dentry of 'b' and it further goes on to call inode_unref on b's parent which is
    'a'. In this situation, GF_ASSERT would be called as the refcount of 'a' has been
    already set to zero.
    
    So, return the inode (in the function inode_unref without doing anything) if the
    inode table cleanup has already started and inode's refcount is zero.
    
    Change-Id: I91e0a807d5c9ce0daae5a611c38da379fd11076e
    fixes: bz#1722546
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit bee5d7bd8a602184c94c12115c7e30572eb7588c
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Mon Jun 24 20:08:48 2019 +0530

    Adding white spaces to description of set group.
    
    The description of set group is missing spaces which
    leads to the description look like:
    volume set <VOLNAME> group  <GROUP> - This option can be used for
    setting multiple pre-defined volume optionswhere group_name is a
    file under /var/lib/glusterd/groups containing onekey, value pair
    per line
    
    Instead of:
    volume set <VOLNAME> group <GROUP> - This option can be used for
    setting multiple pre-defined volume options where group_name is a
    file under /var/lib/glusterd/groups containing one key value
    pair per line
    
    Fixes: bz#1723455
    
    Change-Id: I4957988c0c1f35f043db3f64089c049193e60e8f
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit a72452fcf90679b28baec12d2769cbaa982bb4e4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 25 11:11:10 2019 +0530

    glusterd: conditionally clear txn_opinfo in stage op
    
    ...otherwise this leads to a crash when volume status is run on a
    heterogeneous mode.
    
    Fixes: bz#1723658
    Change-Id: I0d39f412b2e5e9d3ef0a3462b90b38bb5364b09d
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 2d7b77eb971700c1073db2b74f5877c1ae8293fc
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jun 24 10:57:49 2019 +0530

    glusterd: Can't run rebalance due to long unix socket
    
    Problem: glusterd populate unix socket file name based
             on volname and if volname is lengthy socket
             system call's are failed due to breach maximum length
             is defined in the kernel.
    
    Solution:Convert unix socket name to hash to resolve the issue
    
    Change-Id: I5072e8184013095587537dbfa4767286307fff65
    fixes: bz#1720566
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 390cd44b7d0f894a05750245a87d74a7f814493d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jun 24 18:32:52 2019 +0530

    glusterd: ignore user.* options from compatibility check in brick mux
    
    user.* options are just custom and they don't contribute anything in
    terms of determining the volume compatibility in brick multiplexing
    
    Fixes: bz#1723402
    Change-Id: Ic7e0181ab72993d29cab345cde64ae1340bf4faf
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit a066fd70e579db9099251f1debac02f0a87de4c1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jun 18 11:00:38 2019 +0530

    lcov: add more tests to glfsxmp-coverage
    
    * found a bug with quiesce fallocate() - fixed.
    * found a bug with cloudsync part of code in posix - fixed
    
    updates: bz#1693692
    Change-Id: I4f315ffebb612de072ae08761b8cd0f47714080a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit fa804f13f3c1a2e8701327a3746b979f04ce09dd
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Jun 13 16:22:44 2019 +0300

    glusterd.h: remove unneeded macros or move them to their users.
    
    Some macros were not used, so removed.
    Some macros were quite local, so moved to the respective users.
    Some macros simplified (removed an allocation here and there)
    
    Change-Id: Ifaf1aff15a78f105b1549ab8053378933b35df43
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 283b77805cca3027e333a11c9b00ac611662c9ee
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jun 24 21:08:34 2019 +0530

    test: Fix spurious failures in bug-1040275-brick-uid-reset-on-volume-restart.t
    
    Problem: test case is failing after just starting the volume at the
             time of running stat command on mount point and client is
             getting error transport endpoint is not conencted
    
    Solution: To avoid the error make sure all brick instance should be
              up and mount point should be active
    
    Change-Id: I49553a04d5b13e155ee02f4a1888a07fe3ee2ff5
    fixes: bz#1721590
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 24a3204d7088d11a00e4fa2145e6262f824fe0a9
Author: Dan <dan@d3fy.net>
Date:   Tue Jun 18 09:46:15 2019 +0530

    compat.h: fix a \#pragma poisoning error
    
    Fixes a failure to compile glusterfs with glibc 2.25 (on Gentoo and other systems)
    
    Making all in src
      CC       libglusterfs_la-dict.lo
    In file included from iatt.h:16:0,
                     from common-utils.h:44,
                     from dict.c:20:
    /usr/include/sys/sysmacros.h:57:45: error: attempt to use poisoned "system"
       directly.  If you did not intend to use a system-defined macro\n\
                                                 ^
    make[4]: *** [Makefile:959: libglusterfs_la-dict.lo] Error 1
    
    Fixes: bz#1494654
    Change-Id: I09b910b5772f52e853f87d81f3923eed9a90f7a1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit d1d9c2587f5a985073039db5d15fe9adb0433547
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jun 18 22:15:37 2019 +0530

    glusterd/shd: Change shd logfile to a unique name
    
    With the shd mux changes, shd was havinga a logfile
    with volname of the first started volume.
    
    This was creating a lot confusion, as other volumes data
    is also logging to a logfile which has a different vol name.
    
    With this changes the logfile will be changed to a unique name
    ie "/var/log/glusterfs/glustershd.log". This was the same
    logfile name before the shd mux
    
    Change-Id: I2b94c1f0b2cf3c9493505dddf873687755a46dda
    fixes: bz#1721601
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit aeb4545f35ef2740db36387cb855dcaa6bafb03d
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Fri Jun 14 07:53:06 2019 +0000

    core: replace inet_addr with inet_pton
    
    Fixes warning raised by RPMDiff on the use of inet_addr, which may
    impact Ipv6 support
    
    fixes: bz#1721385
    
    Change-Id: Id2d9afa1747efa64bc79d90dd2566bff54deedeb
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 665d627e865d8cfa6a454c2c79eed9e9a1276865
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Jun 20 20:43:24 2019 +0530

    shd/mux: Fix race between mux_proc unlink and stop
    
    There is a small race window, where we have a shd proc
    without having a connection. That is when we stopped the
    last shd running on a process. The list was removed
    outside of a lock just after stopping the process.
    
    So there is a window where we stopped the process, but
    the shd proc list contains the entry.
    
    Change-Id: Id82a82509e5cd72acac24e8b7b87197626525441
    fixes: bz#1722541
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit e2f2f414f855f9a3da269745ae3db2d27baa7f3d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 20 17:05:49 2019 +0530

    cluster/ec: Prevent double pre-op xattrops
    
    Problem:
    Race:
    Thread-1                                    Thread-2
    1) Does ec_get_size_version() to perform
    pre-op fxattrop as part of write-1
                                               2) Calls ec_set_dirty_flag() in
                                                  ec_get_size_version() for write-2.
    					      This sets dirty[] to 1
    3) Completes executing
    ec_prepare_update_cbk leading to
    ctx->dirty[] = '1'
    					   4) Takes LOCK(inode->lock) to check if there are
    					      any flags and sets dirty-flag because
    				              lock->waiting_flag is 0 now. This leads to
    					      fxattrop to increment on-disk dirty[] to '2'
    
    At the end of the writes the file will be marked for heal even when it doesn't need heal.
    
    Fix:
    Perform ec_set_dirty_flag() and other checks inside LOCK() to prevent dirty[] to be marked
    as '1' in step 2) above
    
    Updates bz#1593224
    Change-Id: Icac2ab39c0b1e7e154387800fbededc561612865
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 2959fbfbb77e2b1b2ccbc90610f8ff9362109ae3
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 13 16:23:21 2019 +0530

    posix/ctime: Fix ctime upgrade issue
    
    Problem:
    On a EC volume, during upgrade from the older version where
    ctime feature is not enabled(or not present) to the newer
    version where the ctime feature is available (enabled default),
    the self heal hangs and doesn't complete.
    
    Cause:
    The ctime feature has both client side code (utime) and
    server side code (posix). The feature is driven from client.
    Only if the client side sets the time in the frame, should
    the server side sets the time attributes in xattr. But posix
    setattr/fseattr was not doing that. When one of the server
    nodes is updated, since ctime is enabled by default, it
    starts setting xattr on setattr/fseattr on the updated node/brick.
    
    On a EC volume the first two updated nodes(bricks) are not a
    problem because there are 4 other bricks with consistent data.
    However once the third brick is updated, the new attribute(mdata xattr)
    will cause an inconsistency on metadata on 3 bricks, which
    prevents the file to be repaired.
    
    Fix:
    Don't create mdata xattr with utimes/utimensat system call.
    Only update if already present.
    
    Change-Id: Ieacedecb8a738bb437283ef3e0f042fd49dc4c8c
    fixes: bz#1720201
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 804de0be6f100ede12f6131d3320cf06a227f191
Author: David Spisla <david.spisla@iternity.com>
Date:   Wed Jun 19 13:07:56 2019 +0200

    WORM-Xlator: Avoid performing fsetxattr if fd is NULL
    
    If worm_create_cbk receives an error (op_ret == -1) fd will be NULL
    and therefore performing fsetxattr would lead to a segfault and the
    brick process crashes. To avoid this we allow setting fsetxattr only
    if op_ret >= 0 . If an error happens we explicitly unwind
    
    Change-Id: Ie7f8a198add93e5cd908eb7029cffc834c3b58a6
    fixes: bz#1717757
    Signed-off-by: David Spisla <david.spisla@iternity.com>

commit 52cf03ee314e46aa990c5b813d83019aabb04d58
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Tue Apr 23 11:03:24 2019 +0800

    ec-heal: check file's gfid when deleting stale name
    
    A name-less lookup does not contain parent's stat,
    It is hard to check the lookuped file is at the right path.
    
    This patch changes to a name lookup, and check file's gfid with
    expected gfid. If the gfid is different, mark it estale.
    
    fixes: bz#1702131
    Change-Id: I2de20b10d680eed1e2fb1d3830b3b3dec4520dbf
    Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>

commit eae5f062ae008eb3b615170a102c715d70aa68e6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jun 20 09:17:36 2019 +0530

    fix template file after clang-format
    
    clang-format gets applied for all the files ending with .c or .h
    but in this case, new-xlator.c was a template file. hence
    change the suffix to reflect the same, also to avoid the
    auto-formatting on template file.
    
    updates: bz#1193929
    Change-Id: I1c00a28f165f34dbe00fd3b6b070d868a56f9157
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 2e11f61029d0b36893c4aa859f99c22b6202ad12
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Jun 19 15:11:59 2019 +0530

    afr/read: Implement latency based read child selection
    
    Network latency is an important factor selecting a read subvolume.
    So this patch is adding two new policy.
    
    1) We measure the latency of a child during a GF_DUMP rpc call.
       Then use this latency to pick a read subvol having the least
       latency.
    
    2) Second one is an hybrid mode where it calculates the effective
       latency by multiplying outstanding pending read request and
       latency, and choose the least one.
    
    Change-Id: Ia49c8a08ab61f7dcdad8b8950aa4d338e7accf97
    fixes: #520
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit bcdb77023e2efbbf06ad576851f0f38a0b8b11ab
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Jun 18 16:43:43 2019 +0530

    posix: fix crash in posix_cs_set_state
    
    Fixes: bz#1721474
    Change-Id: Ic2a53fa3d1e9e23424c6898e0986f80d52c5e3f6
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 1725880dabd2bac8739043c4cb5f9d844557f86e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jun 17 16:49:48 2019 +0530

    encryption/crypt: remove from volume file
    
    The feature is not supported and is moved out of the codebase from
    glusterfs-5.x release. Doesn't make sense to keep the code to
    support it.
    
    For those who want to upgrade from an version supporting it to higher
    version, please do a 'gluster volume reset $VOL encryption reset' and
    then continue with the upgrade process.
    
    updates: bz#1648169
    Change-Id: I8cf822c0d7195940bd37f6af2432a3cac68d44d1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 6f70d4a6377365c352dad07d8eae0b2bd7af6fc6
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Feb 19 12:49:12 2019 +0530

    glusterfind: integrate with gfid2path
    
    Integration with gfid2path helps avoid file-system crawl and saves
    precious time. Extended attributes starting with "trusted.gfid2path."
    are read and the <PGFID>/<BN> values are extracted and the <PGFID> is
    iteratively resolved from the brick backend to arrive at the full path.
    
    Change-Id: I593b02880e3413b77bfceed4a36b00d401f03bc0
    fixes: #529
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 647a1b83fa39a635b01fcba38a330485fcd6afdb
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Jun 12 15:41:27 2019 +0530

    extras/hooks: Install and package newly added post add-brick hook script
    
    https://review.gluster.org/c/glusterfs/+/22834 added a new SELinux hook
    script as a post add-brick operation to label new brick paths. But the
    change failed to install and package new script. Therefore making
    necessary changes to Makefile and spec file to get it installed and
    packaged.
    
    Change-Id: I67b8f4982c2783c34a4bc749fb4387c19a038225
    fixes: bz#1717953
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit b99f6eba2e4d53ba8220034d9b8a4530681ec77e
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Feb 26 15:20:33 2019 +0800

    md-cache: only update generation for inode at upcall and NULL stat
    
    1. For parallel writes from nfs-ganesha, two fops with two generations,
       but the fops reply maybe returned disordered.
    2. The inode md-cache timeout should not increase conf->generation.
    
    With this patch,
    1, Fop only gets generation from inode md-cache or conf, does not increase it.
    2. The generation is increased at upcall invalidate, estal/enoent error
       invalidate, reply with zeroed out stat from write-behind.
    
    Change-Id: I897ecaa143fd18bc024c1948c7d1a6f831fd53da
    Updates: bz#1683594
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit c9097077922647b61570f087d16103f1c7aced99
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jun 18 15:33:29 2019 +0530

    cluster/dht: Strip out dht xattrs
    
    Some internal DHT xattrs were not being
    removed when calling getxattr in pass-through mode.
    This has been fixed.
    
    Change-Id: If7e3dbc7b495db88a566bd560888e3e9c167defa
    fixes: bz#1721435
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit c8f302b7b34b45b2cf340634ed66de899f900c23
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Jun 18 16:25:35 2019 +0530

    geo-rep: Fix permissions for GEOREP_DIR in non-root setup
    
    During mountbroker setup: 'gluster-mountbroker <mountbroker-root> <group>'
    commad to set the permission and group for GEOREP_DIR directory
    (/var/lib/glusterd/geo-replication) fails due to extra argument, which is
    enssential for non-root geo-rep setup.
    
    fixes: bz#1721441
    Change-Id: Ia83442733bf0b29f630e8c9e398097316efca092
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 2d278f0407ab7d29507dc697653b39d72ddee472
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun May 26 11:18:05 2019 +0300

    glusterd-volgen.c: remove BD xlator from the graph
    
    The BD xlator was removed some time ago. Remove it from the graph.
    We can also remove the caps settings - only the BD xlator
    was using it.
    
    Lastly, remove the caps (which only BD was using) and the document
    describing the translator.
    
    Change-Id: Id0adcb2952f4832a5dc6301e726874522e07935d
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit b79222f650f6613758f036c749f5f879a54148a7
Author: SheetalPamecha <spamecha@redhat.com>
Date:   Mon Jun 17 15:42:20 2019 +0530

    core: fedora 30 compiler warnings
    
    warning: ‘%s’ directive argument is null [-Wformat-overflow=]
    
    Change-Id: I69b8d47f0002c58b00d1cc947fac6f1c64e0b295
    updates: bz#1193929
    Signed-off-by: SheetalPamecha <spamecha@redhat.com>

commit 25ad5aca23b257cdd129cd1d4518b048fbba87bb
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jun 17 11:10:42 2019 +0530

    tests: subdir-mount.t is failing for brick_mux regrssion
    
    To avoid the failure wait to run hook script S13create-subdir-mounts.sh
    after executed add-brick command by test case.
    
    Change-Id: I063b6d0f86a550ed0a0527255e4dfbe8f0a8c02e
    fixes: bz#1720993
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 7cc20c1eb09c041b331c4add6c24212fbdcda3b4
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Fri Jan 19 12:18:13 2018 +0100

    core: improve timer accuracy
    
    Also fixed some issues on test ec-1468261.t.
    
    Change-Id: If156f86af986d9eed13cdd1f15c5a7214cd11706
    Updates: bz#1193929
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 513df02b19af14b8b006c5c2e60c2a7447146aa2
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Jun 13 16:28:04 2019 +0530

    glusterd: log error message only when rsp.op_ret is negative
    
    Problem: commit d42221bec9 added a log message based on rsp.op_ret
    check. but while running subdir-mount.t, this message is seen even on
    successful mounts.
    
    Solution: in __server_getspec(), return value of sys_read() is assigned to
    ret, which will be a non-negative number in when sys_read() is success.
    This non-zero value is assigned to rsp.op_ret. We should log an error only
    when rsp.op_ret is negative.
    
    fixes: bz#1718848
    
    Change-Id: Ieef8ba33c2c7b4a97d4aef17543f58e66fd3b341
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 1984fddf10fd3ed8ddedfab45424db9656b271a8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 11 09:52:06 2019 +0530

    glusterd: add GF_TRANSPORT_BOTH_TCP_RDMA in glusterd_get_gfproxy_client_volfile
    
    ... with out which volume creation fails with "volume create: <xyz>: failed:
    Failed to create volume files"
    
    Fixes: bz#1716812
    Change-Id: I2f4c2c6d5290f066b54e1c1db19e25db9937bedb
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 01846e7b9b0b92e4a10f5cbcc921bad90441660d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 13 22:43:47 2019 +0530

    uss: Fix tar issue with ctime and uss enabled
    
    Problem:
    If ctime and uss enabled, tar still complains with 'file
    changed as we read it'
    
    Cause:
    To clear nfs cache (gluster-nfs), the ctime was incremented
    in snap-view client on stat cbk.
    
    Fix:
    The ctime should not be incremented manually. Since gluster-nfs
    is planning to be deprecated, this code is being removed to
    fix the issue.
    
    Change-Id: Iae7f100c20fce880a50b008ba716077350281404
    fixes: bz#1720290
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit b460e58d07fac340b713778f979d23705a8b70ff
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jun 4 05:37:57 2019 +0530

    afr/fini: Free local_pool data during an afr fini
    
    We should free the mem_pool local_pool during an afr_fini.
    Otherwise this will lead to mem leak for shd
    
    Change-Id: I805a34a88077bf7b886c28b403798bf9eeeb1c0b
    Updates: bz#1716695
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 632c10b5e976079d825f8808b5e33ab2e1dda469
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 14 15:00:12 2019 +0530

    cli: don't fail if logging initialize fails
    
    in many cases, gluster's cli can run as non-privileged mode
    (like in geo-rep non-root setup). Just because logging fails
    in cli, lets not fail the overall process. Not much of
    debugging help in CLI logs anyways. Most of the debugging
    happens once the call reaches server (glusterd).
    
    Fixes: bz#1535511
    Change-Id: I9f07c61b8c3acc95ec08230ff539a35dfd0ff9dc
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 1cb32e3df2775dabc57df6931ffce96aece7109e
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Fri May 31 17:21:22 2019 +0530

    geo-rep/gsyncd: name is not freed in one of the cases
    
    CID: 1400730
    updates: bz#789278
    Change-Id: I0f6924050a31d3d2cc0b555f859920e349728e0a
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 82b8458ac6d31c72dc7a2f69df7f50bb1e4b7618
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 14 12:43:45 2019 +0200

    build: always build glusterfs-cli to allow monitoring/managing from clients
    
    Fixes: bz#1720615
    Change-Id: I5071f3255ff615113b36b08cd5326be6e37d907d
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit e7211901e9f987d0efcd7d699c995634fc9f24d6
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 14 17:34:34 2019 +0530

    tests: Add missing NFS test tag to the testfile
    
    $SRC/glusterfs/bugs/nfs/showmount-many-clients.t
    
    Change-Id: I48758cc66fcb55f48c4a8a0a738b06867f6814a1
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Updates: bz#1193929

commit 06ee9e13db03a02b343a5d44cae3c4a5da48bf8a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 14 12:53:15 2019 +0530

    clang-scan: resolve warning
    
    dht-common.c: because there was a 'goto err' before assigning
                  the 'local' variable, there is possibility of NULL
                  dereference. As the check which was done wouldn't
                  ever be true, removed the check.
    
    glusterd-geo-rep.c: a possible path where 'slave_host' could be
                 NULL when it gets passed to strcmp() is found.
                 strcmp() expects a valid string. Add a NULL check.
    
    Updates: bz#1622665
    Change-Id: I64c280bc1beac9a2b109e8fa88f2a5ce8b823c3a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 836c7ec096ebff089482f1e5a25fa55df28b14ea
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 14 22:38:10 2019 +0530

    glfs: add syscall.h after header cleanup
    
    in one of the recent patches, we cleaned-up the unneccesary header
    file includes. In the order of merging the patches, there cropped
    up an compile error.
    
    updates: bz#1193929
    Change-Id: I2ad52aa918f9c698d5273bb293838de6dd50ac31
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 0a6fe8551ac9807a8b6ad62241ec8048cf9f9025
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Jun 9 13:31:31 2019 +0300

    multiple files: another attempt to remove includes
    
    There are many include statements that are not needed.
    A previous more ambitious attempt failed because of *BSD plafrom
    (see https://review.gluster.org/#/c/glusterfs/+/21929/ )
    
    Now trying a more conservative reduction.
    It does not solve all circular deps that we have, but it
    does reduce some of them. There is just too much to handle
    reasonably (dht-common.h includes dht-lock.h which includes
    dht-common.h ...), but it does reduce the overall number of lines
    of include we need to look at in the future to understand and fix
    the mess later one.
    
    Change-Id: I550cd001bdefb8be0fe67632f783c0ef6bee3f9f
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 65e3624091e895ca32cd91468552589f34d17595
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 14 16:11:37 2019 +0530

    eventsapi: Fix Exception class for Python3
    
    Python2 exception provides message attribute for custom exceptions.
    But it is not available in Python3. Add init method for custom exception
    to handle the same.
    
    Original crash(IndexError reported in the bug) was fixed with
    https://review.gluster.org/#/c/glusterfs/+/22294/ But that patch only
    works in Python2 and fails in Python3 since Exception in Python 3
    doesn't have "message" attribute.
    
    Fixes: bz#1573226
    Change-Id: If9117048f9ff0615f5da1880075ec12c0ff4855e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 6eaa561526c340c48b12f0cf149c6c5a2903d751
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 14 10:04:28 2019 +0530

    gfapi: provide an api for setting statedump path
    
    Currently for an application using glfsapi to use glusterfs, when a
    statedump is taken, it uses /var/run/gluster dir to dump info.
    
    There can be concerns as this directory may be owned by some other
    user, and hence it may fail taking statedump. Such applications
    should have an option to use different path.
    
    This patch provides an API to do so.
    
    Updates: bz#1689097
    Change-Id: I8918e002bc823d83614c972b6c738baa04681b23
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 928395eddf4241433effc55e294a7996108da7d8
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Mon Jun 3 15:59:38 2019 +0800

    gnfs: support inode dump
    
    So, we will get more debug info.
    
    fixes: #679
    Change-Id: I3588e204ad25c20b69271c1a4ee17d0d158bd794
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit 675dd98ce0c772b732c7f45a8e51dcf0d64f57fc
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Jun 7 19:33:07 2019 +0530

    upcall: Avoid sending notifications for invalid inodes
    
    For nameless LOOKUPs, server creates a new inode which shall
    remain invalid until the fop is successfully processed post
    which it is linked to the inode table.
    
    But incase if there is an already linked inode for that entry,
    it discards that newly created inode which results in upcall
    notification. This may result in client being bombarded with
    unnecessary upcalls affecting performance if the data set is huge.
    
    This issue can be avoided by looking up and storing the upcall
    context in the original linked inode (if exists), thus saving up on
    those extra callbacks.
    
    Change-Id: I044a1737819bb40d1a049d2f53c0566e746d2a17
    fixes: bz#1718338
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit bc6fd4cfa6ed34de3ffc02e2279fcc713f80f530
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Jun 7 17:20:15 2019 +0530

    gfapi: fix incorrect initialization of upcall syncop arguments
    
    While sending upcall notifications via synctasks, the argument used to
    carry relevant data for these tasks is not initialized properly. This patch
    is to fix the same.
    
    Change-Id: I9fa8f841e71d3c37d3819fbd430382928c07176c
    fixes: bz#1718316
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 4d51b878c9c41e81f965569a4fe19a95a0a42c25
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Mon Jun 3 18:05:24 2019 +0530

    cli: Remove-brick warning seems unnecessary
    
    As force-migration option is disabled by default,
    the warning seems unnessary.
    
    Rephrased the warning to make best sense out of it.
    
    fixes: bz#1712668
    Change-Id: Ia18c3c5e7b3fec808fce2194ca0504a837708822
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 582f91fcad42b6b7da653d2a587d196a7a1e0204
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jun 6 18:33:19 2019 +0530

    extras/hooks: Add SELinux label on new bricks during add-brick
    
    Change-Id: Ifd8ae5eeb91b968cc1a9a9b5d15844c5233d56db
    fixes: bz#1717953
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 3dd03146bb7037ae2ebea0579d0b81be27fdd927
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon May 13 14:32:53 2019 +0530

    geo-rep : fix mountbroker setup
    
    Problem:
    
    Unable to setup mountbroker root directory while creating geo-replication
    session for non-root user.
    
    Casue:
    With patch[1] which defines the max-port for glusterd one extra sapce
    got added in field of 'option max-port'.
    [1]. https://review.gluster.org/#/c/glusterfs/+/21872/
    
    In geo-rep spliting of key-value pair form vol file was done on the
    basis of space so this additional space caused "ValueError: too many values
    to unpack".
    
    Solution:
    Use split so that it can treat consecutive whitespace as a single separator.
    
    Fixes: bz#1709248
    Change-Id: Ia22070a43f95d66d84cb35487f23f9ee58b68c73
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 952cf7e4f4393fcd9cf8c16b013d8f28915c990e
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri May 31 18:40:30 2019 +0200

    libglusterfs: cleanup iovec functions
    
    This patch cleans some iovec code and creates two additional helper
    functions to simplify management of iovec structures.
    
      iov_range_copy(struct iovec *dst, uint32_t dst_count, uint32_t dst_offset,
                     struct iovec *src, uint32_t src_count, uint32_t src_offset,
                     uint32_t size);
    
        This function copies up to 'size' bytes from 'src' at offset
        'src_offset' to 'dst' at 'dst_offset'. It returns the number of
        bytes copied.
    
      iov_skip(struct iovec *iovec, uint32_t count, uint32_t size);
    
        This function removes the initial 'size' bytes from 'iovec' and
        returns the updated number of iovec vectors remaining.
    
    The signature of iov_subset() has also been modified to make it safer
    and easier to use. The new signature is:
    
      iov_subset(struct iovec *src, int src_count, uint32_t start, uint32_t size,
                 struct iovec **dst, int32_t dst_count);
    
        This function creates a new iovec array containing the subset of the
        'src' vector starting at 'start' with size 'size'. The resulting
        array is allocated if '*dst' is NULL, or copied to '*dst' if it fits
        (based on 'dst_count'). It returns the number of iovec vectors used.
    
    A new set of functions to iterate through an iovec array have been
    created. They can be used to simplify the implementation of other
    iovec-based helper functions.
    
    Change-Id: Ia5fe57e388e23392a8d6cdab17670e337cadd587
    Updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit c525fdc6bd79684da196e0fe7ca5630c1bac8f21
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jun 10 09:39:38 2019 +0530

    tests: keep glfsxmp in tests directory
    
    this is critical so all the tests will be contained in the same
    directory, and one can just 'cp -a tests/ <any-location>/' and
    run glusterfs tests.
    
    only 'glfsxmp.c' was an exception as it was just copying the
    file from api example directory. Now moved it to tests.
    
    updates: bz#1193929
    Change-Id: I00359d64be580bffc5b3c3a090968d86c2c6952a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8e5656d950ff7bca21594b47921c6c0bf98eecea
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Jun 10 23:19:44 2019 +0530

    tests: Fix split-brain-favorite-child-policy.t failure
    
    Problem:
    The test case is failing to heal the volume within $HEAL_TIMEOUT @195.
    This is happening because as part of split-brain resolution the file
    gets expunged from the sink and the new entry mark for that file will
    be done on the source bricks as part of impunging. Since the source
    bricks shd-threads failed to get the heal-domain lock, they will wait
    for the heal-timeout of 10 minutes, which is greater than $HEAL_TIMEOUT.
    
    Fix:
    Set the cluster.heal-timeout to 5 seconds to trigger the heal so that
    one of the source brick heals the file within the $HEAL_TIMEOUT.
    
    Change-Id: Ie73c578cc5361c0d617a48ccc86026734d20ba8c
    fixes: bz#1718998
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 1b0b869d91d4e5bedc69922128551602dc4bbc13
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Jun 6 10:59:42 2019 +0530

    Cluster/afr: Don't treat all bricks having metadata pending as split-brain
    
    Problem:
    We currently don't have a roll-back/undoing of post-ops if quorum is not met.
    Though the FOP is still unwound with failure, the xattrs remain on the disk.
    Due to these partial post-ops and partial heals (healing only when 2 bricks
    are up), we can end up in metadata split-brain purely from the afr xattrs
    point of view i.e each brick is blamed by atleast one of the others for
    metadata. These scenarios are hit when there is frequent connect/disconnect
    of the client/shd to the bricks.
    
    Fix:
    Pick a source based on the xattr values. If 2 bricks blame one, the blamed
    one must be treated as sink. If there is no majority, all are sources. Once
    we pick a source, self-heal will then do the heal instead of erroring out
    due to split-brain.
    This patch also adds restriction of all the bricks to be up to perform
    metadata heal to avoid any metadata loss.
    
    Removed the test case tests/bugs/replicate/bug-1468279-source-not-blaming-sinks.t
    as it was doing metadata heal even when only 2 of 3 bricks were up.
    
    Change-Id: I07a9d62f84ceda329dcab1f02a33aeed258dcb09
    fixes: bz#1717819
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 5b35b18be6a04ed4dd69dc71e5fb436c212c15fc
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Jun 10 15:16:48 2019 +0530

    tests: added cleanup for lock files
    
    Problem: useradd fails with: Cannot allocate memory
             useradd: cannot lock /etc/passwd; try again later.
    
    Solution:
    
    Lock files should get automatically removed once "usradd" or "groupadd"
    command finishes. But sometimes we encounter situations (bugs) where
    some of these files may not get properly unlocked after the execution of
    the command. In that case, when we execute useradd next time, it may show
    the error “cannot lock /etc/password” or “unable to lock group file”.
    So, to avoid any such errors, check for any lock files under /etc and
    remove those.
    
    updates: bz#1193929
    
    Change-Id: If6456a271c2bc0717f768d7101a40ce44a9af3d7
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit dc119e9c2f3db6d029ab1c5a81c171180db58192
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Apr 5 12:29:23 2019 +0530

    features/shard: Fix extra unref when inode object is lru'd out and added back
    
    Long tale of double unref! But do read...
    
    In cases where a shard base inode is evicted from lru list while still
    being part of fsync list but added back soon before its unlink, there
    could be an extra inode_unref() leading to premature inode destruction
    leading to crash.
    
    One such specific case is the following -
    
    Consider features.shard-deletion-rate = features.shard-lru-limit = 2.
    This is an oversimplified example but explains the problem clearly.
    
    First, a file is FALLOCATE'd to a size so that number of shards under
    /.shard = 3 > lru-limit.
    Shards 1, 2 and 3 need to be resolved. 1 and 2 are resolved first.
    Resultant lru list:
                                   1 -----> 2
    refs on base inode -          (1)  +   (1) = 2
    3 needs to be resolved. So 1 is lru'd out. Resultant lru list -
    		               2 -----> 3
    refs on base inode -          (1)  +   (1) = 2
    
    Note that 1 is inode_unlink()d but not destroyed because there are
    non-zero refs on it since it is still participating in this ongoing
    FALLOCATE operation.
    
    FALLOCATE is sent on all participant shards. In the cbk, all of them are
    added to fync_list.
    Resulting fsync list -
                                   1 -----> 2 -----> 3 (order doesn't matter)
    refs on base inode -          (1)  +   (1)  +   (1) = 3
    Total refs = 3 + 2 = 5
    
    Now an attempt is made to unlink this file. Background deletion is triggered.
    The first $shard-deletion-rate shards need to be unlinked in the first batch.
    So shards 1 and 2 need to be resolved. inode_resolve fails on 1 but succeeds
    on 2 and so it's moved to tail of list.
    lru list now -
                                  3 -----> 2
    No change in refs.
    
    shard 1 is looked up. In lookup_cbk, it's linked and added back to lru list
    at the cost of evicting shard 3.
    lru list now -
                                  2 -----> 1
    refs on base inode:          (1)  +   (1) = 2
    fsync list now -
                                  1 -----> 2 (again order doesn't matter)
    refs on base inode -         (1)  +   (1) = 2
    Total refs = 2 + 2 = 4
    After eviction, it is found 3 needs fsync. So fsync is wound, yet to be ack'd.
    So it is still inode_link()d.
    
    Now deletion of shards 1 and 2 completes. lru list is empty. Base inode unref'd and
    destroyed.
    In the next batched deletion, 3 needs to be deleted. It is inode_resolve()able.
    It is added back to lru list but base inode passed to __shard_update_shards_inode_list()
    is NULL since the inode is destroyed. But its ctx->inode still contains base inode ptr
    from first addition to lru list for no additional ref on it.
    lru list now -
                                  3
    refs on base inode -         (0)
    Total refs on base inode = 0
    Unlink is sent on 3. It completes. Now since the ctx contains ptr to base_inode and the
    shard is part of lru list, base shard is unref'd leading to a crash.
    
    FIX:
    When shard is readded back to lru list, copy the base inode pointer as is into its inode ctx,
    even if it is NULL. This is needed to prevent double unrefs at the time of deleting it.
    
    Change-Id: I99a44039da2e10a1aad183e84f644d63ca552462
    Updates: bz#1696136
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 4cfc5788af2488d173ac033850370c4f9ed7a05e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Sun Jun 2 01:36:33 2019 +0530

    ec/fini: Fix race between xlator cleanup and on going async fop
    
    Problem:
    While we process a cleanup, there is a chance for a race between
    async operations, for example ec_launch_replace_heal. So this can
    lead to invalid mem access.
    
    Solution:
    Just like we track on going heal fops, we can also track fops like
    ec_launch_replace_heal, so that we can decide when to send a
    PARENT_DOWN request.
    
    Change-Id: I055391c5c6c34d58aef7336847f3b570cb831298
    fixes: bz#1703948
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 9e0de2b634b888dd069e908b7745197d20fe7036
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jun 4 11:13:50 2019 +0530

    xlator/log: Add more logging in xlator_is_cleanup_starting
    
    This patch will add two extra logs for invalid argument
    
    Change-Id: I3950b4f4b9d88b1f1e788ef93d8f09d4bd8d4d8b
    updates: bz#1703948
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 2eaf8e846afd71c30f2a6ff6f863a39b1145b8b6
Author: kshithijiyer <kshithij.ki@gmail.com>
Date:   Wed Jun 5 19:40:29 2019 +0530

    Fixing formatting errors in markdown files
    
    There are a lot of fromatting error is markdown
    files peresent under /doc directiory of the project.
    Fixing formatting errors and sending a patch.
    
    Fixes: bz#1718273
    Change-Id: I08f938088bbaaafddf634f73616ea0dbfe7aedf3
    Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

commit 2ff76fa45c53b8e291cf70c98b28800f3ed5f6fc
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue May 14 10:56:15 2019 -0400

    uss: Ensure that snapshot is deleted before creating a new snapshot
    
    * Also some logging enhancements in snapview-server
    
    Change-Id: I6a7646771cedf4bd1c62806eea69d720bbaf0c83
    fixes: bz#1715921
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit fa32b594d12673698da0c1dab8491db8655b4d50
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Jun 4 11:17:21 2019 +0530

    cluster/replicate: Modify command in unit file to assign port correctly
    
    Problem:
    In unit file of TA process we have been using ta-vol as
    volume id and also ta-vol-server.transport.socket.listen-port=24007
    
    In volume file for TA process we only consider volname
    as "ta" and not as "ta-vol". That's why it was not able to assign
    this port number to ta process as in volume file it will try to
    find server xlator as ta-vol
    
    volume ta-server  <<<<<<<<< not ta-vol-server
     46     type protocol/server
     47     option transport.listen-backlog 10
     48     option transport.socket.keepalive-count 9
     49     option transport.socket.keepalive-interval 2
     50     option transport.socket.keepalive-time 20
     51     option transport.tcp-user-timeout 0
     52     option transport.socket.keepalive 1
     53     option auth.addr./mnt/thin-arbiter.allow *
     54     option auth-path /mnt/thin-arbiter
     55     option transport.address-family inet
     56     option transport-type tcp
     57     subvolumes ta-io-stats
     58 end-volume
    
    Solution:
    Provide "ta" as vol id for the  command which Unit file
    is going to execute.
    
    Also, made changes in setup-thin-arbiter.sh to correctly
    identify the directory of Unit file irrespective of the location from
    where we are executing this script.
    
    Change-Id: Ia7bbccdc0304e7dfaaa732bebb726fba731d1d33
    fixes: bz#1716766
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit ecafe78378209ea28201624fca262bfdbd425365
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 6 13:19:29 2019 +0530

    glusterd: store fips-mode-rchecksum option in the info file
    
    commit 146e4b45d0ce906ae50fd6941a1efafd133897ea enabled
    storage.fips-mode-rchecksum option for all new volumes with op-version
    >=GD_OP_VERSION_7_0 but `gluster vol get $volname
    storage.fips-mode-rchecksum` was displaying it as 'off'. This patch fixes it.
    
    fixes: bz#1717782
    Change-Id: Ie09f89838893c5776a3f60569dfe8d409d1494dd
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit fdc596731ea49af87a1dfdc4f255459e5fda60aa
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jun 6 15:46:15 2019 +0530

    glusterd: Fix typos
    
    Change-Id: I8cf0a153f84ef2d162e6dd03261441d211c07d40
    updates: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 89a34b574ee86b77fbae5295c766471086b9ea8f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 6 12:54:04 2019 +0530

    tests/utils: Fix py2/py3 util python scripts
    
    Following files are fixed.
    
    tests/bugs/distribute/overlap.py
    tests/utils/changelogparser.py
    tests/utils/create-files.py
    tests/utils/gfid-access.py
    tests/utils/libcxattr.py
    
    Change-Id: I3db857cc19e19163d368d913eaec1269fbc37140
    updates: bz#1193929
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit a981e7cc12bb89304e8736d857f23f3a394512d0
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 7 13:55:12 2019 +0530

    tests/quick-read-upcall: mark it bad
    
    Frequent intermittent failures observed.
    ```
    08:59:24 ok  11 [     10/      3] <  36> 'write_to /mnt/glusterfs/0/test.txt test-message1'
    08:59:24 ok  12 [     10/      6] <  37> 'test-message1 cat /mnt/glusterfs/0/test.txt'
    08:59:24 ok  13 [     10/      4] <  38> 'test-message0 cat /mnt/glusterfs/1/test.txt'
    08:59:24 not ok  14 [   3715/      6] <  45> 'test-message1 cat /mnt/glusterfs/1/test.txt' -> 'Got "test-message0" instead of "test-message1"'
    08:59:24 ok  15 [     10/    162] <  47> 'gluster --mode=script --wignore volume set patchy features.cache-invalidation on'
    08:59:24 ok  16 [     10/    148] <  48> 'gluster --mode=script --wignore volume set patchy performance.qr-cache-timeout 15'
    ```
    
    updates: bz#1718191
    Change-Id: Ieb9e5a9a428995ff178f77bc4a5155b8298d3fa0
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit edc2910a8ab3a7d9cfbb19e3f20179c0799c0c1b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 7 13:58:48 2019 +0530

    tests/volume-scale-shd-mux: mark as bad test
    
    The test is giving frequent failures in regression.
    
    Error seen is normally like below:
    
    `09:09:24 not ok  58 [     14/  80343] < 104> '^3$ number_healer_threads_shd patchy_distribute1 __afr_shd_healer_wait' -> 'Got "1" instead of "^3$"'`
    
    updates: bz#1708929
    Change-Id: I240bdcfb76b1f953d75937a53c5dfabba134f282
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 373f045497b3e696ab6492b9c8ea105ffe947b91
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu May 9 14:07:48 2019 +0530

    tests/shd: Add test coverage for shd mux
    
    This patch add more test cases for shd mux test cases
    The test case includes
    1) Createing multiple volumes to check the attach and detach
       of self heal daemon requests.
    2) Make sure the healing happens in all sceanarios
    3) After a volume detach make sure the threads of the detached
       volume is all cleaned.
    4) Repeat all the above tests for ec volume
    5) Node Reboot case
    6) glusterd restart cases
    7) Add-brick/remove brick
    8) Convert a distributed volume to disperse volume
    9) Convert a replicated volume to distributed volume
    
    Change-Id: I7c317ef9d23a45ffd831157e4890d7c83a8fce7b
    fixes: bz#1708929
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 76673e983b7eb849011b3fb4417cf1d5f7147352
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jun 4 15:10:39 2019 +0530

    tests/geo-rep: Add geo-rep cli testcases
    
    Change-Id: Icf93b90bcac022a355d4718220698987dbc91ecf
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    updates: bz#1693692

commit 3949d241e8504b1c5226d0e6f6e06a2a12d8357c
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jun 4 14:51:44 2019 +0530

    cluster/dht: Fix directory perms during selfheal
    
    Fixed a bug in the revalidate code path that wiped out
    directory permissions if no mds subvol was found.
    
    Change-Id: I8b4239ffee7001493c59d4032a2d3062586ea115
    fixes: bz#1716830
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e7aeab3063ac5645136303278b477d7de35266c0
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon May 20 11:11:39 2019 +0530

    across: clang-scan: fix NULL dereferencing warnings
    
    All these checks are done after analyzing clang-scan report produced
    by the CI job @ https://build.gluster.org/job/clang-scan
    
    updates: bz#1622665
    Change-Id: I590305af4ceb779be952974b2a36066ffc4865ca
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit abc4d4cfa01d922c46ebb1abfa5d801ba8c6b5c8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Jun 1 22:43:03 2019 +0530

    lcov: run more fops on translators
    
    Translators covered:
    * playground/template
    * debug/delay-gen
    * debug/error-gen
    * features/namespace
    * features/quiesce
    * meta
    
    updates: bz#1693692
    Change-Id: Ic8fde8efcb309ea492d8e819241f786f7ff467a1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 400b66d568ad18fefcb59949d1f8368d487b9a80
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 8 13:00:51 2019 +0530

    features/shard: Fix block-count accounting upon truncate to lower size
    
    The way delta_blocks is computed in shard is incorrect, when a file
    is truncated to a lower size. The accounting only considers change
    in size of the last of the truncated shards.
    
    FIX:
    
    Get the block-count of each shard just before an unlink at posix in
    xdata.  Their summation plus the change in size of last shard
    (from an actual truncate) is used to compute delta_blocks which is
    used in the xattrop for size update.
    
    Change-Id: I9128a192e9bf8c3c3a959e96b7400879d03d7c53
    fixes: bz#1705884
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit d8bb432eb776f3a8708ed6cacf1c19fca9524d51
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 3 13:25:16 2019 +0530

    tests/geo-rep: Add geo-rep glusterd test cases
    
    1. Add geo-rep fanout test case
    2. Add glusterd geo-rep negative test cases
    3. Add glusterd geo-rep config test cases
    
    Change-Id: I856c087eb3216d8f0ffd1f266deac88e9a4effec
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    updates: bz#1693692

commit 0687befd3332111c7522766aa437ce5166771d0b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 3 14:15:51 2019 +0530

    tests/geo-rep: Remove a rename test case on EC volume
    
    Rename with existing name testcase is occasionaly
    failing on EC volume. Hence commenting the same
    until it's analysed
    
    Change-Id: Icb2ad189b9e4d12101e8f5abcb8a033181360386
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    updates: bz#1193929

commit 823c65940912d7b10bcdd495035dbb23b5c99478
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jun 3 09:49:30 2019 +0530

    glusterd: coverity fix
    
    1401716: Resource leak
    1401714: Dereference before null check
    
    updates: bz#789278
    
    Change-Id: I8fb0b143a1d4b37ee6be7d880d9b5b84ba00bf36
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a36c82375723f51e49c0830d47520392d859c307
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed May 29 12:26:01 2019 +0530

    glusterd/tier: gluster upgrade broken because of tier
    
    Problem: While tier code was removed, the is_tier_enabled
    related to tier wasn't handled for upgrade.
    As this option was missing in the info file, the checksum
    mismatch issue happens during upgrade.
    This results in the peer rejections happening.
    
    Fix: use the op_version check and note down the is_tier_enabled
    always. This way it will be dummy key, but the future upgrades
    will work fine.
    
    NOTE: Just having the key from 3.10 to 7 will cause issues when
    upgraded from 5 to 8 or any such upgrade which skips the version
    where we handle it.
    
    Change-Id: I9951e2b74f16e58e884e746c34dcf53e559c7143
    fixes: bz#1714973
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit 0f29cabac22c48a0895e2b136f3fd48d9577052b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu May 30 15:25:01 2019 +0530

    lcov: improve line coverage
    
    upcall: remove extra variable assignment and use just one
            initialization.
    open-behind: reduce the overall number of lines, in functions
                 not frequently called
    selinux: reduce some lines in init failure cases
    
    updates: bz#1693692
    Change-Id: I7c1de94f2ec76a5bfe1f48a9632879b18e5fbb95
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 899b2170945c6023b0037fed70b19aa3cc680a22
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri May 17 11:04:45 2019 +0530

    across: coverity fixes
    
    * locks/posix.c: key was not freed in one of the cases.
    * locks/common.c: lock was being free'd out of context.
    * nfs/exports: handle case of missing free.
    * protocol/client: handle case of entry not freed.
    * storage/posix: handle possible case of double free
    
    CID: 1398628, 1400731, 1400732, 1400756, 1124796, 1325526
    
    updates: bz#789278
    Change-Id: Ieeaca890288bc4686355f6565f853dc8911344e8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 950726dfc8e3171bef625b563c0c6dbba1ec2928
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Mon Nov 19 22:15:25 2018 +0530

    posix: add storage.reserve-size option
    
    storage.reserve-size option will take size as input
    instead of percentage. If set, priority will be given to
    storage.reserve-size over storage.reserve. Default value
    of this option is 0.
    
    fixes: bz#1651445
    Change-Id: I7a7342c68e436e8bf65bd39c567512ee04abbcea
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 6fd8281ac9af58609979f660ece58c2ed1100e72
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sat Jun 1 18:36:55 2019 +0530

    glusterd: remove trivial conditions
    
    updates: bz#1193929
    
    Change-Id: Ieb5e35d454498bc389972f9f15fe46b640f1b97d
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f8f09178bb890924a8050b466cc2e7a0a30e35a7
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri May 17 19:26:48 2019 +0530

    glusterd: Optimize code to copy dictionary in handshake code path
    
    Problem: While high no. of volumes are configured around 2000
             glusterd has bottleneck during handshake at the time
             of copying dictionary
    
    Solution: To avoid the bottleneck serialize a dictionary instead
              of copying key-value pair one by one
    
    Change-Id: I9fb332f432e4f915bc3af8dcab38bed26bda2b9a
    fixes: bz#1711297
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit fc49927b5fe06380cab309787d2bd62601fa75c4
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri May 31 16:52:04 2019 +0530

    tests/geo-rep: Add tests to cover glusterd geo-rep
    
    Change-Id: Ide59a3fde11b23f654b1ec03d72b4ec53b36a03b
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    updates: bz#1693692

commit c848f7163c5ba6b8a081c0f07a4776f7ff8dfca0
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 14 23:12:44 2019 +0530

    glusterd/shd: Optimize the glustershd manager to send reconfigure
    
    Traditionally all svc manager will execute process stop and then
    followed by start each time when they called. But that is not
    required by shd, because the attach request implemented in the shd
    multiplex has the intelligence to check whether a detach is required
    prior to attaching the graph. So there is no need to send an explicit
    detach request if we are sure that the next call is an attach request
    
    Change-Id: I9157c8dcaffdac038f73286bcf5646a3f1d3d8ec
    fixes: bz#1710054
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit e510f55bed6c26c6b995e7d9f3c35e1e4e482769
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Sat May 11 22:40:22 2019 +0530

    glusterfsd/cleanup: Protect graph object under a lock
    
    While processing a cleanup_and_exit function, we are
    accessing a graph object. But this has not been protected
    under a lock. Because a parallel cleanup of a graph is quite
    possible which might lead to an invalid memory access
    
    Change-Id: Id05ca70d5b57e172b0401d07b6a1f5386c044e79
    fixes: bz#1708926
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit f8b0ba06c4cea428f6eb7730f4430b3564c83da0
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Fri May 17 12:24:50 2019 +0530

    tests/geo-rep: Add EC volume test case
    
    Added geo-rep regression tests with EC volume.
    
    fixes: bz#1650095
    Change-Id: Ifb6e68e0a6103a98fced7f84d3088b8edf33d52f
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 4b8244df9d0851ae82cfef5cce359233af7812c8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri May 31 08:53:58 2019 +0530

    lcov: more coverage to shard, old-protocol, sdfs
    
    updates: bz#1693692
    Change-Id: If4c30572d4501d169bb4b0871c677d974515867c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 5866f5e9b09bc10dfb1631b5636c5b7870fc61ff
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu May 30 23:48:05 2019 +0530

    glusterd/svc: Stop stale process using the glusterd_proc_stop
    
    While restarting a glusterd process, when we have a stale pid
    we were doing a simple kill. Instead we can use glusterd_proc_stop
    Because it has more logging plus force kill in case if there is
    any problem with kill signal handling.
    
    Change-Id: I4a2dadc210a7a65762dd714e809899510622b7ec
    updates: bz#1710054
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit e9ec61c9fc264c813bb9ed06891e2294870a50bc
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed May 22 13:32:23 2019 +0530

    glusterd/svc: glusterd_svcs_stop should call individual wrapper function
    
    glusterd_svcs_stop should call individual wrapper function to stop a
    daemon rather than calling glusterd_svc_stop. For example for shd,
    it should call glusterd_shdsvc_stop instead of calling basic API
    function to stop. Because the individual functions for each daemon
    could be doing some specific operation in their wrapper function.
    
    Change-Id: Ie6d40590251ad470ef3901d1141ab7b22c3498f5
    fixes: bz#1712741
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 4f1b762fb482f2ebddaacfd31a7d43a967fea9e3
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed May 15 07:35:45 2019 +0530

    glusterd: add an op-version check
    
    Problem: "gluster v status" is hung in heterogenous cluster
    when issued from a non-upgraded node.
    
    Cause: commit 34e010d64 fixes the txn-opinfo mem leak
    in op-sm framework by not setting the txn-opinfo if some
    conditions are true. When vol status is issued from a
    non-upgraded node, command is hanging in its upgraded peer
    as the upgraded node setting the txn-opinfo based on new
    conditions where as non-upgraded nodes are following diff
    conditions.
    
    Fix: Add an op-version check, so that all the nodes follow
    same set of conditions to set txn-opinfo.
    
    fixes: bz#1710159
    Change-Id: Ie1f353212c5931ddd1b728d2e6949dfe6225c4ab
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 2855c6247f7c5a2fafe1c403a112c38eca80d020
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 27 19:00:20 2019 +0530

    scripts: Find hung frames given a directory with statedumps
    
    Given a directory with statedumps captured at different times if
    there are any stacks that appear in multiple statedumps, it prints
    them.
    
    Sample output:
    glusterdump.25425.dump  repeats=5  stack=0x7f53642cb968  pid=0      unique=0  lk-owner=
    glusterdump.25427.dump  repeats=5  stack=0x7f85002cb968  pid=0      unique=0  lk-owner=
    glusterdump.25428.dump  repeats=5  stack=0x7f962c2cb968  pid=0      unique=0  lk-owner=
    glusterdump.25428.dump  repeats=2  stack=0x7f962c329f18  pid=60830  unique=0  lk-owner=88f50620967f0000
    glusterdump.25429.dump  repeats=5  stack=0x7f20782cb968  pid=0      unique=0  lk-owner=
    glusterdump.25472.dump  repeats=5  stack=0x7f27ac2cb968  pid=0      unique=0  lk-owner=
    glusterdump.25473.dump  repeats=5  stack=0x7f4fbc2cb9d8  pid=0      unique=0  lk-owner=
    NOTE: stacks with lk-owner=""/lk-owner=0000000000000000/unique=0 may not be hung frames and need further inspection
    
    fixes bz#1714415
    Change-Id: Ib64a3fca63f49df2fafedcd4baa57e9b25411b08
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 14d9c6179715205fb6ac816d4621dd087f5afbb2
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 27 11:43:26 2019 +0530

    stack: Make sure to have unique call-stacks in all cases
    
    At the moment new stack doesn't populate frame->root->unique in all cases. This
    makes it difficult to debug hung frames by examining successive state dumps.
    Fuse and server xlators populate it whenever they can, but other xlators won't
    be able to assign 'unique' when they need to create a new frame/stack because
    they don't know what 'unique' fuse/server xlators already used. What we need is
    for unique to be correct. If a stack with same unique is present in successive
    statedumps, that means the same operation is still in progress. This makes
    'finding hung frames' part of debugging hung frames easier.
    
    fixes bz#1714098
    Change-Id: I3e9a8f6b4111e260106c48a2ac3a41ef29361b9e
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d2576452028db3b817fc5b1f4f924a98bc22c7dc
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue May 28 11:52:46 2019 +0530

    glusterd: coverity fix
    
    1401590: Deadcode
    
    updates: bz#789278
    
    Change-Id: I3aa1d3aa9769e6990f74b6a53e288e788173c5e0
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 002f4736cd470c20f427d8c25916abb4b95c9240
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 29 17:54:45 2019 +0530

    marker: remove some unused functions
    
    After basic analysis, found that these methods were not being
    used at all.
    
    updates: bz#1693692
    Change-Id: If9cfa1ab189e6e7b56230c4e1d8e11f9694a9a65
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 71caf1423fe5f0eed652210f8158c95fc8a10219
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Apr 12 08:16:56 2019 +0530

    tests: add tests for different signal handling
    
    Also some cleanup:
    * old-protocol.t was actually added to make sure we have line-coverage
    * first-test.t should have been removed as per the comment. It doesn't do anything.
    * add statvfs to rpc-coverage so we can cover statvfs in few xlators.
    
    updates: bz#1693692
    Change-Id: Ie8651ce007de484c4abced16b4de765aa5e517be
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit bfe58919c03ea746aa6c7800fe698b15ca8c6ecb
Author: Amgad Saleh <amgad.saleh@nokia.com>
Date:   Thu May 23 20:27:03 2019 -0500

    If bind-address is IPv6 return it successfully
    
    Change-Id: Ibd37b6ea82b781a1a266b95f7596874134f30079
    fixes: bz#1713730
    Signed-off-by: Amgad Saleh <amgad.saleh@nokia.com>

commit 4a5fb52eb1c5387a0fb8bfa1253e5227c7c255e8
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri May 17 18:10:47 2019 +0530

    glusterd: bulkvoldict thread is not handling all volumes
    
    Problem: In commit ac70f66c5805e10b3a1072bd467918730c0aeeb4 I
             missed one condition to populate volume dictionary in
             multiple threads while brick_multiplex is enabled.Due
             to that glusterd is not sending volume dictionary for
             all volumes to peer.
    
    Solution: Update the condition in code as well as update test case
              also to avoid the issue
    
    Change-Id: I06522dbdfee4f7e995d9cc7b7098fdf35340dc52
    fixes: bz#1711250
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a9d76758454bf7d9a8a3f70fc47b732bb9f97d9e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 22 12:23:07 2019 +0530

    tests: Add changelog api tests
    
    updates: bz#1193929
    Change-Id: Iee9aab8140882069165621189741f189fb2cc884
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit e1cc4275583dfd8ae8d0433587f39854c1851794
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Thu May 2 18:33:34 2019 +0530

    glusterd/tier: remove tier related code from glusterd
    
    The handler functions are pointed to dummy functions.
    The switch case handling for tier also have been moved to
    point default case to avoid issues, if reintroduced.
    
    The tier changes in DHT still remain as such.
    
    updates: bz#1693692
    
    Change-Id: I80d80c9a3eb862b4440a36b31ae82b2e9d92e4dc
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit cce775726af28c602d99f73a65439a2564790381
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 21 15:28:10 2019 +0530

    tests: Add history api tests
    
    updates: bz#1193929
    Change-Id: Ic26ab5277f720c734f083150c1c541763dfa64aa
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit a5a9ea6fa440ebbaeb40cf17d33d39fc3fd6b312
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Tue May 7 09:55:08 2019 +0530

    gfapi:add missng api to increase code coverage
    
    add test for async Read/Write combinations
    glfs_read_async/write_async
    glfs_pread_async/pwrite_async
    glfs_readv_async/writev_async
    glfs_preadv_async/pwritev_async
    ftruncate/ftruncate_async
    fsync/fsync_async
    fdatasync/fdatasync_async
    
    Updates: #655
    Change-Id: I12beb97029fd60bce79650a376d8fcd8d383ef16
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 1587a6730ee638d1737b44adbd779d8d2978707d
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Mon Apr 15 14:59:37 2019 +0530

    api/glfsxmp.c: minor fixes
    
    * add more fops: f{get,set,list,remove}xattr(), access(), fstat(), fsetattr(),
    getxattr(), lgetxattr(), llistxattr(), lsetxattr(), fgetxattr()
    * handle some error cases (like volume not found)
    
    Updates: #655
    Change-Id: I3334bdf3090eafd83a54e1be12036ea01b181089
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 5d88111a142b3c37e92bdd36699a04fd054d27f4
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed May 22 17:46:19 2019 +0200

    Fix some "Null pointer dereference" coverity issues
    
    This patch fixes the following CID's:
    
      * 1124829
      * 1274075
      * 1274083
      * 1274128
      * 1274135
      * 1274141
      * 1274143
      * 1274197
      * 1274205
      * 1274210
      * 1274211
      * 1288801
      * 1398629
    
    Change-Id: Ia7c86cfab3245b20777ffa296e1a59748040f558
    Updates: bz#789278
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 4c85456e38b9cc2d9698decca15a21e0cb7961a9
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu May 9 11:07:18 2019 +0200

    cluster/ec: honor contention notifications for partially acquired locks
    
    EC was ignoring lock contention notifications received while a lock was
    being acquired. When a lock is partially acquired (some bricks have
    granted the lock but some others not yet) we can receive notifications
    from acquired bricks, which should be honored, since we may not receive
    more notifications after that.
    
    Since EC was ignoring them, once the lock was acquired, it was not
    released until the eager-lock timeout, causing unnecessary delays on
    other clients.
    
    This fix takes into consideration the notifications received before
    having completed the full lock acquisition. After that, the lock will
    be releaed as soon as possible.
    
    Fixes: bz#1708156
    Change-Id: I2a306dbdb29fb557dcab7788a258bd75d826cc12
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit f6c0b59725615da10435c40fec0f26dae542de74
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 21 10:58:44 2019 +0530

    tests: Fix spurious failures in ta-write-on-bad-brick.t
    
    Problem:
    afr_child_up_status_meta works only when LOOKUP on $M0 is successful.
    There are cases where quorum is not met and LOOKUP fails on $M0 which
    leads to failures similar to:
    grep: /mnt/glusterfs/0/.meta/graphs/active/patchy-replicate-0/private: Transport endpoint is not connected
    This was happening once in a while based on attribute-timeout and
    md-cache not serving the lookup.
    
    Fix:
    Find child-up status based on statedump instead. Also changed mount
    options to include --entry-timeout=0 and --attribute-timeout=0
    
    updates bz#1193929
    Change-Id: Ic0de72c3006d7399a5feb3e4d10d4748949b2ab3
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 0b83b8af60916dcdb850f15da7e7b406809dd1d5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 6 15:27:44 2019 +0530

    tests: Test openfd heal doesn't truncate files
    
    fixes bz#1706603
    Change-Id: I0bfd30f787f157b7a54f71088f767ccfd7621208
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 2a31a7130dd866eed5848caaf9588e6461aca836
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri May 17 14:27:58 2019 +0530

    glusterd: coverity fix
    
    CID: 1401345 - Unused value
    
    updates: bz#789278
    
    Change-Id: I6b8f2611151ce0174042384b7632019c312ebae3
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 38f23ad8333faa2dd0d8ab23104aad4824fbe4a3
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Thu May 9 10:43:01 2019 +0530

    geo-rep: Geo-rep help text issue
    
    Modified Geo-rep help text for better sanity.
    
    fixes: bz#1652887
    
    Change-Id: I40ef7ef709eaecf0125ab4b4a7517e2c5d1ef4a0
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 3b5eb592f543e15e16996ba83182635a4e07ab74
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue May 7 13:33:30 2019 +0300

    glusterd-utils.c: skip checksum when possible.
    
    We only need to calculate and write the checksum in case of
    !is_quota_conf .
    
    Align the code in accordance.
    Also, use a smaller buffer (to write few chars).
    
    Change-Id: I40c83ce10447df77ff9975d314d768ec2c0087c2
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit e1d2ce02135819898f166de9d9903404eb812046
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue May 21 16:51:09 2019 +0530

    cli:  Fixed typos
    
    Change-Id: I14957c5161f31d5dfc6cf56f8d7ccf4d39372f39
    fixes: bz#1711820
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 93156e203c2f51d8a4047889a4c769564b8107b1
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Fri May 17 18:33:11 2019 +0800

    inode: fix wrong loop count in __inode_ctx_free
    
    Avoid serious memory leak
    
    fixes: bz#1711240
    Change-Id: Ic61a8fdd0e941e136c98376a87b5a77fa8c22316
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit 3b36543be48e68d20b4df1a8a5ed1c264158af74
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon May 20 15:23:42 2019 +0530

    cluster/dht: Lookup all files when processing directory
    
    A rebalance process currently only looks up files
    that it is supposed to migrate. This could cause issues
    when lookup-optimize is enabled as the dir layout can be
    updated with the commit hash before all files are looked up.
    This is expecially problematic of one of the rebalance processes
    fails to complete as clients will try to access files whose
    linkto files might not have been created.
    Each process will now lookup every file in the directory it is
    processing.
    Pros: Less likely that files will be inaccessible.
    Cons: More lookup requests sent to the bricks and a potential
    performance hit.
    Note: this does not handle races such as when a layout is updated on disk
    just as the create fop is sent by the client.
    
    Change-Id: I22b55846effc08d3b827c3af9335229335f67fb8
    fixes: bz#1711764
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 2bb1807879493cb77ec9b5088485d88f13b84828
Author: Susant Palai <spalai@redhat.com>
Date:   Tue May 21 16:17:09 2019 +0530

    lock: check null value of dict to avoid log flooding
    
    updates: bz#1712322
    Change-Id: I120a1d23506f9ebcf88c7ea2f2eff4978a61cf4a
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 43ade7abac6c1d648ef337ace92194d36c8894a4
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 21 17:15:07 2019 +0530

    ec/fini: Fix race with ec_fini and ec_notify
    
    During a graph cleanup, we first sent a PARENT_DOWN and wait for
    a child down to ultimately free the xlator and the graph.
    
    In the ec xlator, we cleanup the threads when we get a PARENT_DOWN event.
    But a racing event like CHILD_UP or event xl_op may trigger healing threads
    after threads cleanup.
    
    So there is a chance that the threads might access a freed private variabe
    
    Change-Id: I252d10181bb67b95900c903d479de707a8489532
    fixes: bz#1703948
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 72a83c71cc506e3a4d775b622717052c93f5242f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue May 21 11:20:01 2019 +0530

    tests/quick-read-with-upcall.t: increase the timeout
    
    Running with 2 second sleep at this place caused failures like:
    `not ok  14 [   2014/      7] <  41> 'test-message1 cat /mnt/glusterfs/1/test.txt' -> 'Got "test-message0" instead of "test-message1"'`
    
    in few runs in 100 iterations. But when increased to higher than sleep 3,
    have not seen any failures in 100 runs.
    
    While I don't know the exact reasons for the behavior yet, looks like this
    increase in wait helps to pass the regression without failures.
    
    updates: bz#1693692
    Change-Id: I0610b79bea53e36de3eea6c11234b7fc9dfd6232
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c8ba4c5f6f0bac4f9bdc7d6dec217deecbeb717a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri May 17 23:03:35 2019 +0530

    afr/frame: Destroy frame after afr_selfheal_entry_granular
    
    In function "afr_selfheal_entry_granular", after completing the
    heal we are not destroying the frame. This will lead to crash.
    when we execute statedump operation, where it tried to access
    xlator object. If this xlator object is freed as part of the
    graph destroy this will lead to an invalid memory access
    
    Change-Id: I0a5e78e704ef257c3ac0087eab2c310e78fbe36d
    fixes: bz#1708926
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 2f50486f431b37f4a16541911f50f2042049b0e6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue May 21 01:37:47 2019 +0000

    Revert "rpc: implement reconnect back-off strategy"
    
    This reverts commit 59841f7e1ff0511b04884015441a181a56d07bea.
    
    This revert is done as a 'possible' fix for frequent regression
    failures, which are random in nature too (ie, different tests fails
    in different runs).
    
    Why exactly this patch? Because this patch seemed like most probable
    candidate which got merged in last 15days, and after which regressions
    are failing more often.
    
    Updates: bz#1711827
    Change-Id: I35333162fcd4064f9609525ca93c666053c6d959

commit 836e5b6b76ee74a486b6d41c4a2d3de91e4ad2c1
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu May 16 18:37:48 2019 +0530

    tests: change usleep() to sleep()
    
    While running a test case the following warning messages are seen
    on the display. To avoid suh warnings changing usleep() to sleep().
    
    warning: usleep is deprecated, and will be removed in near future!
    warning: use "sleep 0.25" instead...
    
    updates: bz#1193929
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
    
    Change-Id: I48b79ede1c70b101f654635dd4cc83e50ea55b73

commit 7ead11711181104b23c004e0cd5e9e3c3c981a4f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Apr 5 10:30:23 2019 +0530

    features/shard: Fix crash during background shard deletion in a specific case
    
    Consider the following case -
    1. A file gets FALLOCATE'd such that > "shard-lru-limit" number of
       shards are created.
    2. And then it is deleted after that.
    
    The unique thing about FALLOCATE is that unlike WRITE, all of the
    participant shards are resolved and created and fallocated in a single
    batch. This means, in this case, after the first "shard-lru-limit"
    number of shards are resolved and added to lru list, as part of
    resolution of the remaining shards, some of the existing shards in lru
    list will need to be evicted. So these evicted shards will be
    inode_unlink()d as part of eviction. Now once the fop gets to the actual
    FALLOCATE stage, the lru'd-out shards get added to fsync list.
    
    2 things to note at this point:
    i. the lru'd out shards are only part of fsync list, so each holds 1 ref
       on base shard
    ii. and the more recently used shards are part of both fsync and lru list.
        So each of these shards holds 2 refs on base inode  - one for being
        part of fsync list, and the other for being part of lru list.
    
    FALLOCATE completes successfully and then this very file is deleted, and
    background shard deletion launched. Here's where the ref counts get mismatched.
    First as part of inode_resolve()s during the deletion, the lru'd-out inodes
    return NULL, because they are inode_unlink()'d by now. So these inodes need to
    be freshly looked up. But as part of linking them in lookup_cbk (precisely in
    shard_link_block_inode()), inode_link() returns the lru'd-out inode object.
    And its inode ctx is still valid and ctx->base_inode valid from the last
    time it was added to list.
    
    But shard_common_lookup_shards_cbk() passes NULL in the place of base_pointer
    to __shard_update_shards_inode_list(). This means, as part of adding the lru'd out
    inode back to lru list, base inode is not ref'd since its NULL.
    
    Whereas post unlinking this shard, during shard_unlink_block_inode(),
    ctx->base_inode is accessible and is unref'd because the shard was found to be part
    of LRU list, although the matching ref didn't occur. This at some point leads to
    base_inode refcount becoming 0 and it getting destroyed and released back while some
    of its associated shards are continuing to be unlinked in parallel and the client crashes
    whenever it is accessed next.
    
    Fix is to pass base shard correctly, if available, in shard_link_block_inode().
    
    Also, the patch fixes the ret value check in tests/bugs/shard/shard-fallocate.c
    
    Change-Id: Ibd0bc4c6952367608e10701473cbad3947d7559f
    Updates: bz#1696136
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 40b7121afbd3969706acb8198cf660a710583e70
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 14 11:05:45 2019 +0530

    geo-rep: Convert gfid conflict resolutiong logs into debug
    
    The gfid conflict resolution code path is not supposed
    to hit in generic code path. But few of the heavy rename
    workload (BUG: 1694820) makes it a generic case. So
    logging the entries to be fixed as INFO floods the log
    in these particular workloads. Hence convert them to DEBUG.
    
    fixes: bz#1709653
    Change-Id: I4d5e102b87be5fe5b54f78f329e588882d72b9d9
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit f0d3690e8916cfb5e10a0df2e9721a0fd079bfce
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 8 11:26:06 2019 +0530

    geo-rep: Fix sync hang with tarssh
    
    Problem:
    Geo-rep sync hangs when tarssh is used as sync
    engine at heavy workload.
    
    Analysis and Root cause:
    It's found out that the tar process was hung.
    When debugged further, it's found out that stderr
    buffer of tar process on master was full i.e., 64k.
    When the buffer was copied to a file from /proc/pid/fd/2,
    the hang is resolved.
    
    This can happen when files picked by tar process
    to sync doesn't exist on master anymore. If this count
    increases around 1k, the stderr buffer is filled up.
    
    Fix:
    The tar process is executed using Popen with stderr as PIPE.
    The final execution is something like below.
    
    tar | ssh <args> root@slave tar --overwrite -xf - -C <path>
    
    It was waiting on ssh process first using communicate() and then tar.
    Note that communicate() reads stdout and stderr. So when stderr of tar
    process is filled up, there is no one to read until untar via ssh is
    completed. This can't happen and leads to deadlock.
    Hence we should be waiting on both process parallely, so that stderr is
    read on both processes.
    
    Change-Id: I609c7cc5c07e210c504771115b4d551a2e891adf
    fixes: bz#1707728
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit e2adc9dc66dc46519007790ecd7dd57642dff0fd
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Apr 29 13:22:32 2019 +0530

    ec/shd: Cleanup self heal daemon resources during ec fini
    
    We were not properly cleaning self-heal daemon resources
    during ec fini. With shd multiplexing, it is absolutely
    necessary to cleanup all the resources during ec fini.
    
    Change-Id: Iae4f1bce7d8c2e1da51ac568700a51088f3cc7f2
    fixes: bz#1703948
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 59841f7e1ff0511b04884015441a181a56d07bea
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Fri Jan 19 12:18:13 2018 +0100

    rpc: implement reconnect back-off strategy
    
    When a connection failure happens, gluster tries to reconnect every 3
    seconds. In some cases the failure is spurious, so a delay of 3 seconds
    could be unnecessarily long.
    
    This patch implements a back-off strategy that tries a reconnect as soon
    as 1 tenth of a second. If this fails, the time is doubled until it's
    around 3 seconds. After that, the reconnect is attempted every 3 seconds
    as before.
    
    Change-Id: Icb3fbe20d618f50cbbb599dce542b4e871c22149
    Updates: bz#1193929
    Signed-off-by: Xavier Hernandez <xhernandez@redhat.com>

commit da4601d536da761ce908a2461a0930857f99f171
Author: Anoop C S <anoopcs@redhat.com>
Date:   Fri May 10 12:21:31 2019 +0530

    libglusterfs: Remove decompunder helper routines from symbol export
    
    decompounder and related sources were removed via the following commits:
    
    https://review.gluster.org/#/c/glusterfs/+/22627/
    https://review.gluster.org/#/c/glusterfs/+/22629/
    
    Therefore taking out symbol exports for those removed routines.
    
    Change-Id: I2ef99a318de1e4b512cabd2fa923225c5b79b1e5
    updates: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 8e1d53f14730ac1b1ca0ce9d9a0ccb32578fd4fb
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu May 9 10:08:25 2019 +0530

    core: Capture process memory usage at the time of call gf_msg_nomem
    
    Problem: All gluster processes call gf_mgm_nomem while calloc/malloc/realloc
             throw an error but the message does not capture current memory usage of
             gluster process
    
    Solution: Call getrusage to capture current memory usage of gluster
              process
    
    Change-Id: I2e0319da1f33b177fa042fdc9e7268068576c9c3
    fixes: bz#1708051
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit af4d9131c8d09907853ee2f6e30b2a9bd80f3c84
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 23 12:41:32 2019 +0530

    cli: Validate invalid slave url
    
    This patch validates the invalid slave url
    in cli itself and throws appropriate error.
    
    fixes: bz#1098991
    Change-Id: I278e2a04a4d619d2c2d1db0dd56ab5bdf7e7f469
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit b4db967224db3b16bc1d749fc2cb6f795363362d
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Thu May 9 14:37:22 2019 +0530

    glusterd: Add gluster volume stop operation to glusterd_validate_quorum()
    
    ISSUE: gluster volume stop succeeds even if quorum is not met.
    
    Fix: Add GD_OP_STOP_VOLUME to gluster_validate_quorum in
    glusterd_mgmt_v3_pre_validate ().
    
    Since the volume stop command has been ported from synctask to mgmt_v3,
    the quorum check was missed out.
    
    Change-Id: I7a634ad89ec2e286ea262d7952061efad5360042
    fixes: bz#1690753
    Signed-off-by: Vishal Pandey <vpandey@redhat.com>

commit 5b7ab2e1699f35a0a14211a4e85805d95bcadb62
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu May 9 14:43:06 2019 +0530

    tests: fix bug-1319374.c compile warnings.
    
    I was looking at a downstream failure of bug-1319374-THIS-crash.t when I
    saw the compiler was throwing a warning while running the test:
    
    tests/bugs/gfapi/bug-1319374.c:17:61: warning: implicit declaration of function ‘strerror’; did you mean ‘perror’? [-Wimplicit-function-declaration]
             fprintf(stderr, "\nglfs_new: returned NULL (%s)\n", strerror(errno));
                                                                 ^~~~~~~~
                                                                 perror
    
    So I compiled the .c with -Wall and saw a lot many more warnings, all
    due of a missing header. This patch fixes it.
    
    fixes: bz#1708163
    Change-Id: I8b6dd8e1404178a3d99b2d92d01f4575f5203e58
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit b475551c66b86863cc93ebdfa6daeeab67bdbd9e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon May 6 23:35:08 2019 +0530

    shd/glusterd: Serialize shd manager to prevent race condition
    
    At the time of a glusterd restart, while doing a handshake
    there is a possibility that multiple shd manager might get
    executed. Because of this, there is a chance that multiple
    shd get spawned during a glusterd restart
    
    Change-Id: Ie20798441e07d7d7a93b7d38dfb924cea178a920
    fixes: bz#1707081
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 9ab2747da78061882f6734df4b265bce11adaef1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Apr 9 09:44:33 2019 +0530

    afr: thin-arbiter lock release fixes
    
    - pass fop state instead of afr local to
    afr_ta_dom_lock_check_and_release()
    
    - avoid afr_lock_release_synctask() being called simultaneosuly from
    notify code path and transaction (post-op) code path due to races.
    
    - Check if the post-op on TA is valid based on event_gen checks.
    
    - Invalidate in-memory information when we get TA child down.
    
    Note: Thi patch addresses some pending review comments of commit
    053b1309dc8fbc05fcde5223e734da9f694cf5cc
    (https://review.gluster.org/#/c/glusterfs/+/20095/)
    
    fixes: bz#1698449
    Change-Id: I2ccd7e1b53362f9f3fed8680aecb23b5011eb18c
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 13d09055f7b266a934960f8db9572ec8fd2f6dfa
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed May 8 12:13:59 2019 +0530

    glusterd: fix inconsistent global option output in volume get
    
    volume get all all | grep <key> & volume get <volname> all | grep <key>
    dumps two different output value for cluster.brick-multiplex and
    cluster.server-quorum-ratio
    
    Fixes: bz#1707700
    Change-Id: Id131734e0502aa514b84768cf67fce3c22364eae
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 6a73800b45952a823d808f4efb01d40a6d1257f4
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu May 2 18:06:13 2019 +0300

    glusterd: reduce some work in glusterd-utils.c
    
    Similar to https://review.gluster.org/#/c/glusterfs/+/22652/ ,
    reduce some of the work by using smaller buffers and less
    conversion of parameters when snprintf()'ing them.
    
    On the way, remove some clang warnings, mainly on dead assignment.
    
    Change-Id: Ie51e6d6f14df6b2ccbebba314cf937af08839741
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit aee9e3d27f56e4c0c2f981f20b15189eb7ffce51
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Fri Jan 19 12:18:13 2018 +0100

    tests: improve and fix some test scripts
    
    Change-Id: Iceefe22af754096c599dc570d4894d14fce4deae
    Updates: bz#1193929
    Signed-off-by: Xavier Hernandez <xhernandez@redhat.com>

commit 84b7cc57df065e2d8c0ac88b179aab3614ec814a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 8 10:56:31 2019 +0530

    geo-rep: Fix sync-method config
    
    Problem:
    When 'use_tarssh' is set to true, it exits with successful
    message but the default 'rsync' was used as sync-engine.
    The new config 'sync-method' is not allowed to set from cli.
    
    Analysis and Fix:
    The 'use_tarssh' config is deprecated with new
    config framework and 'sync-method' is the new
    config to choose sync-method i.e. tarssh or rsync.
    This patch fixes the 'sync-method' config. The allowed
    values are tarssh and rsync.
    
    Change-Id: I0edb0319cad0455b29e49f2f08a64ce324735e84
    fixes: bz#1707686
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 288cffd1ab7180cccfcdea36d0c469b9fa52108f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 8 14:10:05 2019 +0530

    tests/geo-rep: Fix arequal checksum comparison
    
    The arequal checkusm comparison was always returning
    as successful, eventhough, if it was not. Fixed the same.
    
    Change-Id: I5083da25c0954126e452d06311d2d376f8540555
    fixes: bz#1707742
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit d42221bec9ebb87df0c10b8e99edde60729250e3
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed May 8 07:58:27 2019 +0530

    glusterd: improve logging in __server_getspec()
    
    updates: bz#1193929
    
    Change-Id: Idad745d5869c92e6bed71842f14bc1a3362ca4bd
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 40983d802f41033a29d4f21d2996e9bda31a91c1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed May 8 04:51:27 2019 -0400

    afr: log before attempting data self-heal.
    
    I was working on a blog about troubleshooting AFR issues and I wanted to copy
    the messages logged by self-heal for my blog. I then realized that AFR-v2 is not
    logging *before* attempting data heal while it logs it for metadata and entry
    heals.
    
    I [MSGID: 108026] [afr-self-heal-entry.c:883:afr_selfheal_entry_do]
    0-testvol-replicate-0: performing entry selfheal on
    d120c0cf-6e87-454b-965b-0d83a4c752bb
    I [MSGID: 108026] [afr-self-heal-common.c:1741:afr_log_selfheal]
    0-testvol-replicate-0: Completed entry selfheal on
    d120c0cf-6e87-454b-965b-0d83a4c752bb. sources=[0] 2  sinks=1
    I [MSGID: 108026] [afr-self-heal-common.c:1741:afr_log_selfheal]
    0-testvol-replicate-0: Completed data selfheal on
    a9b5f183-21eb-4fb3-a342-287d3a7dddc5. sources=[0] 2  sinks=1
    I [MSGID: 108026] [afr-self-heal-metadata.c:52:__afr_selfheal_metadata_do]
    0-testvol-replicate-0: performing metadata selfheal on
    a9b5f183-21eb-4fb3-a342-287d3a7dddc5
    I [MSGID: 108026] [afr-self-heal-common.c:1741:afr_log_selfheal]
    0-testvol-replicate-0: Completed metadata selfheal on
    a9b5f183-21eb-4fb3-a342-287d3a7dddc5. sources=[0] 2  sinks=1
    
    Adding it in this patch. Now there is a 'performing' and a corresponding
    'Completed' message for every type of heal.
    
    fixes: bz#1707746
    Change-Id: I0b954cf1e17b48280aefa76640b5119b92133d61
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 87ba764b2e46cf4782820990f6e4252c8fb59a16
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 1 10:57:58 2019 +0530

    tests: enhance the auth.allow test to validate all failures of 'login' module
    
    now the enhanced test covers most of the code in auth.login and auth.addr module.
    
    updates: bz#1693692
    Change-Id: I1f43c7dc414e2e4d443a93e9a37051359fd46ea4
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 5c9ec08d36b825cd8abd0489dc5f77488dbfbc8b
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue May 7 13:35:47 2019 +0530

    geo-rep: fix incorrectly formatted authorized_keys
    
    There are two ways for creating secret pem pub file during geo-rep
    setup.
    1. gluster-georep-sshkey generate
    2. gluster system:: execute gsec_create
    
    Below patch solves this problem for `gluster-georep-sshkey generate`
    method.
    Patch link: https://review.gluster.org/#/c/glusterfs/+/22246/
    
    This patch is added to support old way of creating secret pem pub file
    `gluster system:: execute gsec_create`.
    
    Problem:  While Geo-rep setup when creating an ssh authorized_keys
              the geo-rep setup inserts an extra space before the "ssh-rsa" label.
              This gets flagged by an enterprise customer's security scan as a
              security violation.
    Solution: Remove extra space while creating secret key.
    
    fixes: bz#1679401
    Change-Id: I92ba7e25aaa5123dae9ebe2f3c68d14315aa5f0e
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 1fa089e7a2b180e0bdcc1e7e09a63934a2a0c0ef
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Apr 28 22:05:44 2019 +0300

    glusterd/store: store all key-values in one shot
    
    Instead of saving each key-value separately, which is slow (
    especially as we fflush() after each!), store them all as one
    string and write all together.
    
    Implements https://github.com/gluster/glusterfs/issues/629
    
    Change-Id: Ie77a272446b0b6785584b710a4fdd9c613dd9578
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat,.com>

commit aa52259de7b50625b754ce9fb5c0f38e22d79dd6
Author: root <root@localhost.localdomain>
Date:   Sun Apr 7 19:31:17 2019 +0530

    dht: Custom xattrs are not healed in case of add-brick
    
    Problem: If any custom xattrs are set on the directory before
             add a brick, xattrs are not healed on the directory
             after adding a brick.
    
    Solution: xattr are not healed because dht_selfheal_dir_mkdir_lookup_cbk
              checks the value of MDS and if MDS value is not negative
              selfheal code path does not take reference of MDS xattrs.Change the
              condition to take reference of MDS xattr so that custom xattrs are
              populated on newly added brick
    
    Updates: bz#1702299
    Change-Id: Id14beedb98cce6928055f294e1594b22132e811c
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit bbb87ee8a433949eea8b3a2f0bef152ead37ccd7
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Tue Apr 23 15:55:22 2019 +0000

    afr : fix Coverity CID 1398627
    
    Fixed coverity error, "Unchecked return value (CHECKED_RETURN)".
    Checking return value & logging error message if afr_set_pending_dict
    fails.
    
    updates: bz#789278
    
    Change-Id: Iab7da6b4f3cd0622b95b8e1c412b007a330467e5
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 291e5ec2a09a145ebb0f4c3ef0b78d616786532f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 6 15:57:16 2019 +0530

    libglusterfs: Fix compilation when --disable-mempool is used
    
    updates bz#1193929
    Change-Id: I245c065b209bcce5db939b6a0a934ba6fd393b47
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 6454132342c0b549365d92bcf3572ecd914f7fa8
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 3 10:14:48 2019 +0530

    performance/write-behind: remove request from wip list in wb_writev_cbk
    
    There is a race in the way O_DIRECT writes are handled. Assume two
    overlapping write requests w1 and w2.
    
    * w1 is issued and is in wb_inode->wip queue as the response is still
      pending from bricks. Also wb_request_unref in wb_do_winds is not yet
      invoked.
    
           list_for_each_entry_safe (req, tmp, tasks, winds) {
    		list_del_init (&req->winds);
    
                    if (req->op_ret == -1) {
    			call_unwind_error_keep_stub (req->stub, req->op_ret,
    		                                     req->op_errno);
                    } else {
                            call_resume_keep_stub (req->stub);
    		}
    
                    wb_request_unref (req);
            }
    
    * w2 is issued and wb_process_queue is invoked. w2 is not picked up
      for winding as w1 is still in wb_inode->wip. w1 is added to todo
      list and wb_writev for w2 returns.
    
    * response to w1 is received and invokes wb_request_unref. Assume
      wb_request_unref in wb_do_winds (see point 1) is not invoked
      yet. Since there is one more refcount, wb_request_unref in
      wb_writev_cbk of w1 doesn't remove w1 from wip.
    
    * wb_process_queue is invoked as part of wb_writev_cbk of w1. But, it
      fails to wind w2 as w1 is still in wip.
    
    * wb_requet_unref is invoked on w1 as part of wb_do_winds. w1 is
      removed from all queues including w1.
    
    * After this point there is no invocation of wb_process_queue unless
      new request is issued from application causing w2 to be hung till
      the next request.
    
    This bug is similar to bz 1626780 and bz 1379655.
    
    Change-Id: Iaa47437613591699d4c8ad18bc0b32de6affcc31
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1705865

commit ecd1292eaea8873298357ab2d903110f713f7185
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Feb 27 15:48:42 2019 +0200

    mem-pool.{c|h}: minor changes
    
    1. Removed some code that was not needed. It did not really do anything.
    2. CALLOC -> MALLOC in one place.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I4419161e1bb636158e32b5d33044b06f1eef2449

commit aff76bc71c1910128b04bb151817606a020ef575
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Apr 30 14:06:03 2019 -0400

    tests: delete the snapshots and the volume after the tests
    
    In uss.t multiple snapshots are taken and after all the tests
    things are left for the cleanup () function to get removed.
    Instead of that, delete the snapshots and the volume once all
    the tests are over so that cleanup operation becomes relatively
    a light operation.
    
    Change-Id: I2342740bbb185cd6c9a450eb3b4f5cbbba78974c
    fixes: bz#1704888
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit db9c31fcf57024abfdc7b35825409166f17d5aac
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Apr 12 07:55:04 2019 +0530

    tests: validate volfile grammar - strings in volfile
    
    * libglusterfs/graph-print: remove unused code
    
    updates: bz#1693692
    Change-Id: Iae81bb6a3af5911c3da07ab8f1d8f58f27e06905
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e0dadeb3242a10827c6142f609c87d860b3ce546
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon May 6 10:35:23 2019 +0530

    glusterd: coverity fix
    
    CID: 1382403 (CHECKED_RETURN)
    
    Updates: bz#789278
    Change-Id: I4c57b93fd3d14c524ff8519ed876f029834de306
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 0d85c6abf5002ff88f17a5292cdde45847154d25
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Apr 25 18:20:25 2019 +0800

    cluster/ec: fix shd healer wait timeout
    
    Right now, the timeout is written by hard code,
    fix it by using heal-timeout.
    
    fixes: bz#1703020
    Change-Id: I0d154e7807f9dba7efc3896805559bbfaa7af2ad
    Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>

commit e18e98659dd2b41eb59cf593fd625f1821a20abf
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri May 3 10:50:40 2019 +0530

    features/shard: Fix integer overflow in block count accounting
    
    ... by holding delta_blocks in 64-bit int as opposed to 32-bit int.
    
    Change-Id: I2c1ddab17457f45e27428575ad16fa678fd6c0eb
    updates: bz#1705884
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit b2d7644435b92bd2468bbaaef7451a64e08c08bd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri May 3 09:18:31 2019 +0200

    glusterd: prevent use-after-free in glusterd_op_ac_send_brick_op()
    
    Coverity reported that GF_FREE(req_ctx) could be called 2x on req_ctx.
    
    Change-Id: I9120686e5920de8c27688e10de0db6aa26292064
    CID: 1401115
    Updates: bz#789278
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 920a9fe5cb5769470d31f5676ccb55dcdbd3a939
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun May 5 21:17:24 2019 +0530

    cluster/ec: Reopen shouldn't happen with O_TRUNC
    
    Problem:
    Doing re-open with O_TRUNC will truncate the fragment even when it is not
    needed needing extra heals
    
    Fix:
    At the time of re-open don't use O_TRUNC.
    
    fixes bz#1706603
    Change-Id: Idc6408968efaad897b95a5a52481c66e843d3fb8
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 0d83a087ddf0fb6b843150c7b801bb10f6fd98db
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed May 1 15:45:09 2019 +0300

    glusterd-utils.c: reduce work in glusterd_add_volume_to_dict()
    
    1. Use small arrays, 32 or 64 bytes should suffice.
    2. Do not repeat the pattern of
    snprintf '%s.%d', prefix, count
    over and over.
    
    Change-Id: Ief6de78b766d9a07acb6256fc4830f4f3cfba7c9
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 91c19c50a3c7b336177dda186500568be43626b8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 25 12:00:52 2019 +0530

    glusterd: Fix coverity defects & put coverity annotations
    
    Along with fixing few defect, put the required annotations for the defects which
    are marked ignore/false positive/intentional as per the coverity defect sheet.
    This should avoid the per component graph showing many defects as open in the
    coverity glusterfs web page.
    
    Updates: bz#789278
    Change-Id: I19461dc3603a3bd8f88866a1ab3db43d783af8e4
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 60d6e90bd0565f8d56641ff97dd90348894ac870
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Apr 25 19:02:39 2019 +0530

    tests/cli: add .t file to increase line coverage in cli
    
    updates: bz#1693692
    
    Change-Id: Ib188c5fddea8c762e89ff15aa83b08c35cdb21e1
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 31411a771f9eea4b65e9dd49f213d021bde51bfe
Author: rishubhjain <rishubhjain47@gmail.com>
Date:   Thu Apr 25 18:44:44 2019 +0530

    tests: add .t files to increase cli code coverage
    
    different volume profile sub options are added in the test.
    
    Change-Id: I93100c37f51afc10870e60b91fcd86e7859e734a
    updates: bz#1693692
    Signed-off-by: rishubhjain <rishubhjain47@gmail.com>

commit bff877b6e0004076ba3d7d4fac3912e8ad9d676d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 16 20:54:24 2019 +0530

    tests: Add changelog snapshot testcase
    
    Add testcase to test snapshot creation
    while I/O is happening with changelog
    enabled.
    
    updates: bz#1193929
    Change-Id: Ice4cb596286c583ed7308484d65902007a48396c
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit ac70f66c5805e10b3a1072bd467918730c0aeeb4
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Apr 29 18:48:36 2019 +0530

    glusterd: Fix bulkvoldict thread logic in brick multiplexing
    
    Problem: Currently glusterd spawn bulkvoldict in brick_mux
             environment while no. of volumes are less than configured
             glusterd.vol_count_per_thread
    
    Solution: Correct the logic to spawn bulkvoldict thread
              1) Calculate endindex only while total thread is non zero
              2) Update end index correctly to pass index for bulkvoldict
                 thread
    
    Fixes: bz#1704252
    Change-Id: I1def847fbdd6a605e7687bfc4e42b706bf0eb70b
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit cfd838c27cc88acd431549f2b8ed515c9ce3e55f
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Apr 29 11:36:16 2019 +0530

    cloudsync/plugin: coverity fixes
    
    CID 1401087:  Null pointer dereferences  (REVERSE_INULL)
    CID 1401088:  Null pointer dereferences  (FORWARD_NULL)
    
    Change-Id: I71bf67af80e1b22bcd2eb997b01a1a5ef0b4d80b
    Updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit e6721e1426b116af7460111e8dddd432aea504a2
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Apr 22 21:34:19 2019 +0300

    options.c,h: minor changes to GF_OPTION_RECONF
    
    Minor code changes (less variables and if statements)
    and use dict_get_strn(), since all options are fixed strings.
    
    Similar changes could be done to GF_OPTION_INIT() as well.
    
    Change-Id: I4a523f67183f4c4852a3d4de5e3cac52df68d3cf
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 5ba81308d58b26f8baff17b44c235d68f88d5f19
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Apr 24 22:29:55 2019 +0530

    libglusterfs: remove compound-fop helper functions
    
    updates: bz#1693692
    Change-Id: If69702990af273be1f38855ba56b3b89fabff167
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit d23e918d954e985b13295ba00353e4f47759e59e
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Fri Jan 19 12:18:13 2018 +0100

    storage/posix: fix fresh file detection delay
    
    Current implementation made it possible to consider that a file was not
    fresh even if it was created less than a second ago. This patch fixes
    the way in which the delay is computed to ensure that at least one
    second has elapsed.
    
    Change-Id: I05f7b99e7e8dd97e31f7ebaaec6c39eecf98b00f
    Updates: bz#1193929
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 45b19d569e9f61410e4a700950e3cf4d7e6838f1
Author: Sheetal Pamecha <spamecha@redhat.com>
Date:   Thu Apr 25 14:46:37 2019 +0530

    nl-cache:add test to increase code coverage
    
    Change-Id: Ie0a5c522dfa0123ca45f9decf5015d39b92cb0f3
    updates: bz#1693692
    Signed-off-by: Sheetal Pamecha <spamecha@redhat.com>

commit 48d160756813875cf1889b4ce96493d25f96c726
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Apr 20 11:55:12 2019 +0530

    protocol: remove compound fop
    
    Compound fops are kept on wire as a backward compatibility with
    older AFR modules. The AFR module used beyond 4.x releases are
    not using compound fops. Hence removing the compound fop in the
    protocol code.
    
    Note that, compound-fops was already an 'option' in AFR, and
    completely removed since 4.1.x releases.
    
    So, point to note is, with this change, we have 2 ways to upgrade
    when clients of 3.x series are present.
    
    i) set 'use-compound-fops' option to 'false' on any volume which
       is of replica type. And then upgrade the servers.
    
    ii) Do a two step upgrade. First from current version (which will
        already be EOL if it's using compound) to a 4.1..6.x version,
        and then an upgrade to 7.x.
    
    Consider the overall code which we are removing for the option
    seems quite high, I believe it is worth it.
    
    updates: bz#1693692
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Change-Id: I0a8876d0367a15e1410ec845f251d5d3097ee593

commit 88418f400507fba109971f169ce0a2c4243a31c9
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Apr 24 22:23:36 2019 +0530

    performance/decompounder: remove the translator as the feature is not used anymore
    
    updates: bz#1693692
    Change-Id: Id5932b11e115ca6da1c2bfff7ae1460787109e06
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 5d866c13efdcdeddf184f012aa88a652e90ff22e
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Apr 26 22:28:53 2019 +0530

    glusterd: define dumpops in the xlator_api of glusterd
    
    Problem: statedump is not capturing information related to glusterd
    
    Solution: statdump is not capturing glusterd info because
    trav->dumpops is null in gf_proc_dump_single_xlator_info ()
    where trav is glusterd xlator object. trav->dumpops is null
    because we missed to define dumpops in xlator_api of glusterd.
    defining dumpops in xlator_api of glusterd fixes the issue.
    
    fixes: bz#1703629
    Change-Id: If85429ecb1ef580aced8d5b88d09fc15258bfc4c
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit e10946dbfe18204d3e4a50e218ac3dbdab82a3a9
Author: Anuradha Talur <atalur@commvault.com>
Date:   Wed Apr 24 12:35:08 2019 -0700

    cloudsync: Fix bug in cloudsync-fops-c.py
    
    In some of the fops generated by generator.py, xdata request
    was not being wound to the child xlator correctly.
    
    This was happening because when though the logic in
    cloudsync-fops-c.py was correct, generator.py was generating
    a resultant code that omits this logic.
    
    Made changes in cloudsync-fops-c.py so that correct code is
    produced.
    
    Change-Id: I6f25bdb36ede06fd03be32c04087a75639d79150
    updates: bz#1642168
    Signed-off-by: Anuradha Talur <atalur@commvault.com>

commit 68138b00ca0d093304a903544d13d0010e7ffcc1
Author: Anuradha Talur <atalur@commvault.com>
Date:   Fri Nov 30 11:23:07 2018 -0800

    cloudsync/cvlt: Cloudsync plugin for commvault store
    
    Change-Id: Icbe53e78e9c4f6699c7a26a806ef4b14b39f5019
    updates: bz#1642168
    Signed-off-by: Anuradha Talur <atalur@commvault.com>

commit 13e1fe6dbd39ef88cadce1590b5d4c45b67387cb
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Apr 26 08:47:12 2019 +0530

    glusterd: coverity fixes
    
    1400775 - USE_AFTER_FREE
    1400742 - Missing Unlock
    1400736 - CHECKED_RETURN
    1398470 - Missing Unlock
    
    Missing unlock is the tricky one, we have had annotation added, but
    coverity still continued to complaint. Added pthread_mutex_unlock to
    clean up the lock before destroying it to see if it makes coverity
    happy.
    
    Updates: bz#789278
    Change-Id: I1d892612a17f805144d96c1b15004a85a1639414
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 146e4b45d0ce906ae50fd6941a1efafd133897ea
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Apr 23 18:05:36 2019 +0530

    glusterd: enable fips-mode-rchecksum for new volumes
    
    ...during volume create if the cluster op-version is >=GD_OP_VERSION_7_0.
    
    This option itself was introduced in GD_OP_VERSION_4_0_0 via commit 6daa65356.
    We missed enabling it by default for new volume creates in that commit.
    If we are to do it now safely, we need to use op version
    GD_OP_VERSION_7_0 and target it for release-7.
    
    fixes: bz#1702303
    Change-Id: I7c6d4a8abe0816367e7069cb5cad01744f04858f
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 6434e8687572fabd5e9092652ff36e35f868b67b
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Thu Jul 9 15:56:28 2015 +0530

    tools/glusterfind : validate session name
    
    Validate a session name(during create) for the following:
    1. minimum 2 character length.
    2. Maximum 256 characters.
    3. No special characters apart from underscore, hyphen allowed.
    
    Also, validate volume(expect, while using glusterfind list).
    
    Change-Id: I1b1e64e218f93d0a531d3cf69fc2ce7e2ed11d01
    BUG: 1241494
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>

commit e7e89c9ec8b56ad5a442ad105c0b05e674a591cd
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Apr 2 12:38:09 2019 +0530

    geo-rep: Fix rename with existing destination with same gfid
    
    Problem:
       Geo-rep fails to sync the rename properly if destination exists.
    It results in source to be remained on slave causing more number of
    files on slave. Also heavy rename workload like logrotate caused
    lot of ESTALE errors
    
    Cause:
       Geo-rep fails to sync rename if destination exists if creation
    of source file also falls into single batch of changelogs being
    processed. This is because, after fixing problematic gfids verifying
    from master, while re-processing original entries, CREATE also was
    re-processed causing more files on slave and rename to be failed.
    
    Solution:
       Entries need to be removed from retrial list after fixing
    problematic gfids on slave so that it's not re-created again on slave.
       Also treat ESTALE as EEXIST so that the error is properly handled
    verifying the op on master volume.
    
    Change-Id: I50cf289e06b997adddff0552bf2466d9201dd1f9
    fixes: bz#1694820
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit a9143223c515b82f6382f1372dfbdc0439dba198
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 1 11:14:56 2019 +0530

    features/locks: error-out {inode,entry}lk fops with all-zero lk-owner
    
    Problem:
    Sometimes we find that developers forget to assign lk-owner for an
    inodelk/entrylk/lk before writing code to wind these fops. locks
    xlator at the moment allows this operation. This leads to multiple
    threads in the same client being able to get locks on the inode
    because lk-owner is same and transport is same. So isolation
    with locks can't be achieved.
    
    Fix:
    Disallow locks with lk-owner zero.
    
    fixes bz#1624701
    Change-Id: I1aadcfbaaa4d49308f7c819505857e201809b3bc
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit edeb0d6e616cf4750ea9f6b6245631de8db233cf
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Apr 25 14:12:28 2019 +0530

    man/gluster: remove tier information from gluster manual page
    
    fixes: bz#1702952
    Change-Id: I650a3695d702c03dc60660ff197676c6d536a2ea
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit de11b4a476b297129065bc7477229e57643ac196
Author: Anuradha Talur <atalur@commvault.com>
Date:   Wed Apr 24 12:06:23 2019 -0700

    cloudsync: Make readdirp return stat info of all the dirents
    
    This change got missed while the initial changes were sent.
    Should have been a part of :
    	https://review.gluster.org/#/c/glusterfs/+/21757/
    
    Gist of the change:
    	Function that fills in stat info for dirents is
    invoked in readdirp in posix when cloudsync populates xdata
    request with GF_CS_OBJECT_STATUS.
    
    Change-Id: Ide0c4e80afb74cd2120f74ba934ed40123152d69
    updates: bz#1642168
    Signed-off-by: Anuradha Talur <atalur@commvault.com>

commit 2b86da69df423a90b76932bd32b7a17bd5ac2add
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Apr 22 19:50:19 2019 +0530

    tier/cli: remove tier code to increase code coverage in cli
    
    Change-Id: I56cc09243dab23b3be86a7faac45001dda77181f
    updates: bz#1693692
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit c827682e4df44ec6aaae3780c325568fb43053ff
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Apr 24 22:02:51 2019 +0530

    glusterd: coverity fixes
    
    Addresses the following:
    
    * CID 1124776:  Resource leaks  (RESOURCE_LEAK) - Variable "aa" going out
    of scope leaks the storage it points to in glusterd-volgen.c
    
    * Bunch of CHECKED_RETURN defects in the callers of synctask_barrier_init
    
    * CID 1400755:  Error handling issues  (CHECKED_RETURN) - Calling
    "gf_is_service_running" without checking return value in
    xlators/mgmt/glusterd/src/glusterd-shd-svc.c: 671 in
    glusterd_shdsvc_stop()
    
    * CID 1400745:  Memory - illegal accesses  (USE_AFTER_FREE) - Dereferencing
    freed pointer "volinfo" in /xlators/mgmt/glusterd/src/glusterd-shd-svc.c: 460 in glusterd_shdsvc_start()
    
    * CID 1400742:  Program hangs  (LOCK) - adding annotation to fix this
    false positive
    
    Updates: bz#789278
    Change-Id: I02f16e7eeb8c5cf72f7d0b29d00df4f03b3718b3
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 647e2d3a9fbe36f2fbf062feda53b7cb6aa4830b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Mar 11 12:16:50 2019 -0400

    features/bit-rot: Unconditionally sign the files during oneshot crawl
    
    Currently bit-rot feature has an issue with disabling and reenabling it
    on the same volume. Consider enabling bit-rot detection which goes on to
    crawl and sign all the files present in the volume. Then some files are
    modified and the bit-rot daemon goes on to sign the modified files with
    the correct signature. Now, disable bit-rot feature. While, signing and
    scrubbing are not happening, previous checksums of the files continue to
    exist as extended attributes. Now, if some files with checksum xattrs get
    modified, they are not signed with new signature as the feature is off.
    
    At this point, if the feature is enabled again, the bit rot daemon will
    go and sign those files which does not have any bit-rot specific xattrs
    (i.e. those files which were created after bit-rot was disabled). Whereas
    the files with bit-rot xattrs wont get signed with proper new checksum.
    At this point if scrubber runs, it finds the on disk checksum and the actual
    checksum of the file to be different (because the file got modified) and
    marks the file as corrupted.
    
    FIX:
    
    The fix is to unconditionally sign the files when the bit-rot daemon
    comes up (instead of skipping the files with bit-rot xattrs).
    
    Change-Id: Iadfb47dd39f7e2e77f22d549a4a07a385284f4f5
    fixes: bz#1700078
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 8d51cb05d9745643f2dfaa6ef35938db9d2d47f6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Apr 13 11:19:20 2019 +0530

    build-aux/pkg-version: provide option for depth=1
    
    Change-Id: I385063b757ae71db70f22a2f7c94e6abeedff426
    updates: bz#1701337
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 3db4f4ed6dec55316e7167eaddd9ddf0af875185
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Mar 8 14:13:32 2019 +0200

    logging.c/h: aggressively remove sprintfs()
    
    Try to reduce the number of sprintf() and string copies until we finally
    log a log line.
    
    Specifically, do not sprintf separately the timestr string and
    do not sprintf/strcpy the appmsgstr separately - just stick it with
    the header.
    Hoping I did not leak anything or changed the log line formatting.
    
    Also, allocate 4K (GF_LOG_BACKTRACE_SIZE) of memory
    dynamically for trace output -
    only if trace was actually requested (previously, it was
    unconditionally)
    
    In addition, some minor code formatting (unrelated to the above).
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Id2ccc85f9213a2b1c6eaa4a2f58ce043eac1824f

commit 1ccc62d11287e8ffd091123517f7988a4e7f1935
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Apr 10 14:28:55 2019 +0530

    cluster/dht: Refactor dht lookup functions
    
    Part 2: Modify dht_revalidate_cbk to call
    dht_selfheal_directory instead of separate calls
    to heal attrs and xattrs.
    
    Change-Id: Id41ac6c4220c2c35484812bbfc6157fc3c86b142
    updates: bz#1590385
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e0a6941af6ed352911698012ada895d1296b549e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 23 10:45:25 2019 +0530

    geo-rep: Fix entries and metadata counters in geo-rep status
    
    Entries counter was incremented twice and decremented only
    once. And entries count was being used in place of metadata
    entries. This patch fixes both of them.
    
    fixes: bz#1512093
    Change-Id: I5601a5fe8d25c9d65b72eb529171e7117ebbb67f
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 1b9b0c2db9b54cddf817bde95a43894a91440b35
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Mon Apr 1 17:04:01 2019 +0530

    tests/geo-rep: Add pause and resume test case for geo-rep
    
    Added pause and resume test case for geo-rep
    
    fixes: bz#1696077
    Change-Id: Ib6fcc1926c3be1263bca1235194f737b895c8333
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 7d2c1abd25353ae4f1fe86f6d851b9a0cc93d2f6
Author: rishubhjain <rishubhjain47@gmail.com>
Date:   Mon Apr 22 20:48:02 2019 +0530

    tests: add .t files to increase cli code coverage
    
    Tests added for gluster volume top and profile
    with and without xml output
    
    Change-Id: I66aa6390b53ca448014059a3d27dc72e405216d2
    updates: bz#1693692
    Signed-off-by: rishubhjain <rishubhjain47@gmail.com>

commit 15ba102feba723b7707ab5efbd614e3da2c59555
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Apr 22 18:10:05 2019 +0530

    tests: add .t file to increase cli code coverage
    
    updates: bz#1693692
    
    Change-Id: I848e622d7b8562e864f0e208aafdc21d9cb757d3
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 2d39572821306496c96797f4d122f8200aae4585
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 19 11:34:37 2019 +0530

    ctime: Fix log repeated logging during open
    
    The log "posix set mdata failed, No ctime" logged repeatedly
    after the fix [1]. Those could be internal fops. This patch
    fixes the same.
    
    [1] https://review.gluster.org/22540
    
    fixes: bz#1701457
    Change-Id: I42799a90b976982cedb0ca11fa224d555eb05650
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit d8eadde7d498939c746ea8ddd9dc70a1029b4070
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue Mar 5 18:58:20 2019 +0100

    core: avoid dynamic TLS allocation when possible
    
    Some interdependencies between logging and memory management functions
    make it impossible to use the logging framework before initializing
    memory subsystem because they both depend on Thread Local Storage
    allocated through pthread_key_create() during initialization.
    
    This causes a crash when we try to log something very early in the
    initialization phase.
    
    To prevent this, several dynamically allocated TLS structures have
    been replaced by static TLS reserved at compile time using '__thread'
    keyword. This also reduces the number of error sources, making
    initialization simpler.
    
    Updates: bz#1193929
    Change-Id: I8ea2e072411e30790d50084b6b7e909c7bb01d50
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 87ae36774a0e5a8af9330cf651d93f5cc84cb515
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Apr 23 13:03:28 2019 +0530

    glusterd/shd: Keep a ref on volinfo until attach rpc execute cbk
    
    When svc attach execute for multiplexing a daemon, we have to keep
    a ref on volinfo until it finish the execution. Because, if the attach
    is an aysnc call, then a parallel volume delete can lead to free the
    volinfo
    
    Change-Id: Ibc02b89557baaed2f63db63d7fb1a7480444ae0d
    fixes: bz#1702185
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 17992b69ccc729d59241ceff2aa480d1976e02fc
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Apr 1 09:03:12 2019 -0400

    build: conditional rpcbind for gnfs in glusterd.service
    
    Don't Require: rpcbind in glusterd.service when gnfs isn't built
    
    Also add .../gluster-ta-volume.service to .gitignore
    
    See https://github.com/gluster/glusterfs/issues/647
    
    Change-Id: I4d90cf66b12c378c0a9aace89a3a4bbf3784c284
    Fixes: #647
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 4f0db1373be93e05b6fc451d2f07514704d3c4ca
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Apr 12 17:54:44 2019 +0200

    cluster/ec: fix fd reopen
    
    Currently EC tries to reopen fd's that have been opened while a brick
    was down. This is done as part of regular write operations, just after
    having acquired the locks, and it's sent as a sub-fop of the main write
    fop.
    
    There were two problems:
    
    1. The reopen was attempted on all UP bricks, even if a previous lock
    didn't succeed. This is incorrect because most probably the open will
    fail.
    
    2. If reopen is sent and fails, the error is propagated to the main
    operation, causing it to fail when it shouldn't.
    
    To fix this, we only attempt reopens on bricks where the current fop
    owns a lock, and we prevent any error to be propagated to the main
    fop.
    
    To implement this behaviour an argument used to indicate the minimum
    number of required answers has overloaded to also include some flags. To
    make the change consistent, it has been necessary to rename the
    argument, which means that a lot of files have been changed. However
    there are no functional changes.
    
    This change has also uncovered a problem in discard code, which didn't
    correctely process requests of small sizes because no real discard fop
    was being processed, only a write of 0's on some region. In this case
    some fields of the fop remained uninitialized or with incorrect values.
    To fix this, a new function has been created to simulate success on a
    fop and it's used in the discard case.
    
    Thanks to Pranith for providing a test script that has also detected an
    issue in this patch. This patch includes a small modification of this
    script to force data to be written into bricks before stopping them.
    
    Change-Id: If272343873369186c2fb8f43c1d9c52c3ea304ec
    Fixes: bz#1699866
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 132f03a0b77980b25a8b499ad1fe1e4ab2aee40e
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Apr 22 21:18:30 2019 +0530

    core: fix hang issue in __gf_free
    
    Currently GF_ASSERT is done under mem_accounting lock at some places.
    On a GF_ASSERT failure, gf_msg_callingfn is called which calls gf_malloc
    internally and it takes the same mem_accounting lock leading to deadlock.
    
    This is a temporary fix to avoid any hang issue in master.
    https://review.gluster.org/#/c/glusterfs/+/22589/ is being worked on
    in the mean while so that GF_ASSERT can be used under mem_accounting
    lock.
    
    Change-Id: I6d67f23979e7edd2695bdc6aab2997dae4a4060a
    updates: bz#1700865
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit a0814b96828505441fbb7f1801e751d98f5a1cc0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 17 00:16:49 2019 +0530

    features/sdfs: Assign unique lk-owner for entrylk fop
    
    sdfs is supposed to serialize entry fops by doing entrylk, but all the locks
    are being done with all-zero lk-owner. In essence sdfs doesn't achieve its goal
    of mutual exclusion when conflicting operations are executed by same client
    because two locks on same entry with same all-zero-owner will get locks.
    
    Fixed this up by assigning lk-owner before taking entrylk
    
    updates bz#1624701
    Change-Id: Ifabfc998c9f1724915d38e90ed8287e05797d769
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d9bfccc8425befa5d13058b5f5352598a2085161
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 17 13:58:21 2019 +0530

    cluster/afr: Set lk-owner before inodelk/entrylk/lk
    
    Updates: bz#1624701
    Change-Id: I7152c28ad85925abccdcc4cd6de8cb2a2b847a51
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 119b4e6371f20d20b74ba854d463f827de0609c2
Author: rishubhjain <rishubhjain47@gmail.com>
Date:   Mon Apr 8 20:20:12 2019 +0530

    GlusterD:Checking for null value to void explicit dereferencing of null pointer
    
    Before calling strtok_r a check for null pointer is necessary to avoid
    dereferencing of null pointer
    
    CID:1398617
    CID:1274074
    
    Change-Id: I34956c6e04af1faa22d550e6474909ecd36f5d6c
    updates: bz#789278
    Signed-off-by: rishubhjain <rishubhjain47@gmail.com>

commit b0fce72477d56eeca616ab089756eab4f4b4bf8e
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Apr 12 13:40:59 2019 +0200

    core: handle memory accounting correctly
    
    When a translator stops, memory accounting for that translator is not
    destroyed (because there could remain memory allocated that references
    it), but mutexes that coordinate updates of memory accounting were
    destroyed. This caused incorrect memory accounting and even crashes in
    debug mode.
    
    This patch also fixes some other things:
    
    * Reduce the number of atomic operations needed to manage memory
      accounting.
    * Correctly account memory when realloc() is used.
    * Merge two critical sections into one.
    * Cleaned the code a bit.
    
    Change-Id: Id5eaee7338729b9bc52c931815ca3ff1e5a7dcc8
    Updates: bz#1659334
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 02a7a9ef1c0703990d6333b8b800a36da04c9f3e
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Apr 17 08:58:57 2019 +0200

    features/locks: fix coverity issues
    
    This patch fixes the following NULL dereferences identified by Coverity:
    
      * CID 1398619
      * CID 1398621
      * CID 1398623
      * CID 1398625
      * CID 1398626
    
    Change-Id: Id6af0d7cba0bb3346005376bc27180e8476255a4
    Updates: bz#789278
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 1ad201a9fd6748d7ef49fb073fcfe8c6858d557d
Author: Milan Zink <mzink@redhat.com>
Date:   Mon Feb 5 15:04:37 2018 +0100

    extras/hooks: syntactical errors in SELinux hooks, scipt logic improved
    
    Fixes: bz#1542072
    Change-Id: Ia5fa1df81bbaec3a84653d136a331c76b457f42c
    Signed-off-by: Milan Zink <zeten30@gmail.com>

commit e97aa3b36627a821af164ab292259b320993495c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 16 17:20:34 2019 +0530

    glusterd: fix loading ctime in client graph logic
    
    Commit efbf8ab wasn't handling all the scenarios of toggling ctime
    option correctly and more over a ! had completely tossed up the logic.
    
    Fixes: bz#1697907
    Change-Id: If12e2f69045e59878992ee2cd0518cc0eabcce0d
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 785f3276d2e325a991b64aed66a326ea95fffef3
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 16 22:14:47 2019 +0530

    Revert "features/locks: error-out {inode,entry}lk fops with all-zero lk-owner"
    
    This reverts commit 3883887427a7f2dc458a9773e05f7c8ce8e62301 as it has
    broken sdfs-sanity.t.
    
    Updates: bz#1624701
    Change-Id: Icb2b0d6bfcce4d556f1cd0f11695c03ffc138736
    Signed-off-by: Atin Mukherjee  <amukherj@redhat.com>

commit b922793588ad23a9b12ce65abd29e8f45ac87998
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Apr 15 14:09:34 2019 -0400

    features/bit-rot-stub: clean the mutex after cancelling the signer thread
    
    When bit-rot feature is disabled, the signer thread from the bit-rot-stub
    xlator (the thread which performs the setxattr of the signature on to the
    disk) is cancelled. But, if the cancelled signer thread had already held
    the mutex (&priv->lock) which it uses to monitor the queue of files to
    be signed, then the mutex is never released. This creates problems in
    future when the feature is enabled again. Both the new instance of the
    signer thread and the regular thread which enqueues the files to be
    signed will be blocked on this mutex.
    
    So, as part of cancelling the signer thread, unlock the mutex associated
    with it as well using pthread_cleanup_push and pthread_cleanup_pop.
    
    Change-Id: Ib761910caed90b268e69794ddeb108165487af40
    updates: bz#1700078
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit e5ff6cc397e7a23dff4024efb6806cb004a89ee6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 16 08:46:21 2019 +0530

    glusterd: fix op-version of glusterd.vol_count_per_thread
    
    It was hardcoded and with a wrong value.
    
    Fixes: bz#1699339
    Change-Id: Ibabe2424a0d35e172a9259bd8849c9bb7cebff1e
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit b3a6d4e32ec5826ce4e389030b99d7b08274ed29
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 16 14:19:47 2019 +0530

    tests: Heal should fail when read/write fails
    
    updates: bz#1699866
    Change-Id: I7ccd1fc5fc134eeb6d443c755962a20819320d48
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 3883887427a7f2dc458a9773e05f7c8ce8e62301
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 1 11:14:56 2019 +0530

    features/locks: error-out {inode,entry}lk fops with all-zero lk-owner
    
    Problem:
    Sometimes we find that developers forget to assign lk-owner for an
    inodelk/entrylk/lk before writing code to wind these fops. locks
    xlator at the moment allows this operation. This leads to multiple
    threads in the same client being able to get locks on the inode
    because lk-owner is same and transport is same. So isolation
    with locks can't be achieved.
    
    Fix:
    Disallow locks with lk-owner zero.
    
    fixes bz#1624701
    Change-Id: I1c816280cffd150ebb392e3dcd4d21007cdd767f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 26a19d9da3ab5604db02d4ca02ce868fb57193a4
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Mar 29 11:48:32 2019 +0530

    glusterd: Optimize glusterd handshaking code path
    
    Problem: At the time of handshaking glusterd populate volume
             data in a dictionary.While no. of volumes are configured
             more than 1500 glusterd takes more than 10 min to generated
             the data.Due to taking more time rpc request times out and
             rpc start bailing of call frames.
    
    Solution: To optimize the code done below changes
              1) Spawn multiple threads to populate volumes data in bulk
                 in separate dictionary and introduce an option
                 glusterd.brick-dict-thread-count to configure no. of threads
                 to populate volume data.
              2) Populate tier data only while volume type is tier
              3) Compare snap data only while snap_count is non zero
    
    Fixes: bz#1699339
    Change-Id: I38dc71970c049217f9d1a06fc0aaf4c26eab18f5
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit f316c8b797283818bd800569771870a4b9bf1310
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Apr 12 19:55:10 2019 +0530

    libgfchangelog : use find_library to locate shared library
    
    Issue:
    
    libgfchangelog.so: cannot open shared object file
    
    Due to hardcoded shared library name runtime loader looks for particular version of
    a shared library.
    
    Solution:
    
    Using find_library to locate shared library at runtime solves this issue.
    
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 323, in main
        func(args)
      File "/usr/libexec/glusterfs/python/syncdaemon/subcmds.py", line 82, in subcmd_worker
        local.service_loop(remote)
      File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 1261, in service_loop
        changelog_agent.init()
      File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 233, in __call__
        return self.ins(self.meth, *a)
      File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 215, in __call__
        raise res
    OSError: libgfchangelog.so: cannot open shared object file: No such file or directory
    
    Change-Id: I3dd013d701ed1cd99ba7ef20d1898f343e1db8f5
    fixes: bz#1699394
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit c27eee869f319fa2afbce31f1ab332d381015256
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Apr 5 12:33:55 2019 +0530

    shd/mux: Fix coverity issues introduced by shd mux patch
    
    CID 1400475:  Null pointer dereferences  (FORWARD_NULL)
    CID 1400474:  Null pointer dereferences  (FORWARD_NULL)
    CID 1400471:  Code maintainability issues  (UNUSED_VALUE)
    CID 1400470:  Null pointer dereferences  (FORWARD_NULL)
    CID 1400469:  Memory - illegal accesses  (USE_AFTER_FREE)
    CID 1400467:  Code maintainability issues  (UNUSED_VALUE)
    
    Change-Id: I0ca1c733be335c6e5844f44850f8066626ac40d4
    updates: bz#789278
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 8239efc76b56f1f4ce16bab263f7b355d8205820
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Apr 4 15:31:56 2019 +0530

    cluster/afr: Remove local from owners_list on failure of lock-acquisition
    
    When eager-lock lock acquisition fails because of say network failures, the
    local is not being removed from owners_list, this leads to accumulation of
    waiting frames and the application will hang because the waiting frames are
    under the assumption that another transaction is in the process of acquiring
    lock because owner-list is not empty. Handled this case as well in this patch.
    Added asserts to make it easier to find these problems in future.
    
    fixes bz#1696599
    Change-Id: I3101393265e9827755725b1f2d94a93d8709e923
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 798aadbe51a9a02dd98a0f861cc239ecf7c8ed57
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Apr 4 09:56:11 2019 +0530

    core: Log level changes do not effect on running client process
    
    Problem: commit c34e4161f3cb6539ec83a9020f3d27eb4759a975 set log-level
             per xlator during reconfigure only for a brick process not for
             the client process.
    
    Solution: 1) Change per xlator log-level only if brick_mux is enabled.To make sure
                 about brick multiplex introudce a flag brick_mux at ctx->cmd_args.
    
    Note: There are two other changes done with this patch
          1) Ignore client-log-level option to attach a brick with
             already running brick if brick_mux is enabled
          2) Add a log to print pid of the running process to make easier
             debugging
    
    Change-Id: I39e85de778e150d0685cd9a79425ce8b4783f9c9
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
    Fixes: bz#1696046

commit a67929e18a39d5c79a4a7e2b78015523626a367e
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Mar 25 19:07:16 2019 +0200

    graph.c: remove extra gettimeofday() - reuse the graph dob.
    
    It was written just before fill_void() call.
    
    Note that there was a possible overflow if the hostname was too long
    (unrelated to this patch), but it is now also fixed, as we use a smaller buffer
    for the hostname. This, in turn, forces us to check if gethostname() failed
    and add explicitly the terminating null to it.
    
    Change-Id: I45fbc0a8e105f1247f3cbf61befac06fabbaea06
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c56f102da21c5b69e656a055aaf736281596284d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 9 18:23:05 2019 +0530

    posix/ctime: Fix stat(time attributes) inconsistency during readdirp
    
    Problem:
       Creation of tar file on gluster volume throws warning
    'file changed as we read it'
    
    Cause:
       During readdirp, for few of the files whose inode is not
    present, time attributes were served from backend. This caused
    the ctime of few files to be different between before readdir
    and after readdir by tar.
    
    Solution:
      If ctime feature is enabled and inode is not present, don't
    serve the time attributes from backend file, serve it from xattr.
    
    fixes: bz#1698078
    Change-Id: I427ef865f97399475faf5aa6ca495f7e317603ae
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit bcd1207fcd8e7cc278971e16a781bca3c1606969
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 1 10:33:37 2019 +0530

    marker-quota: remove dead code
    
    also make minor changes for signature (int -> void) where return value
    was not checked anywhere.
    
    updates: bz#1693692
    Change-Id: Iff117712eb65e0b6b8b441a779202a117fcdf1fb
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit b777d83001d8006420b6c7d2d88fe68950aa7e00
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Apr 11 20:38:53 2019 +0530

    core: Brick is not able to detach successfully in brick_mux environment
    
    Problem: In brick_mux environment, while volumes are stopped in a
             loop bricks are not detached successfully. Brick's are not
             detached because xprtrefcnt has not become 0 for detached brick.
             At the time of initiating brick detach process server_notify
             saves xprtrefcnt on detach brick and once counter has become
             0 then server_rpc_notify spawn a server_graph_janitor_threads
             for cleanup brick resources.xprtrefcnt has not become 0 because
             socket framework is not working due to assigning 0 as a fd for socket.
             In commit dc25d2c1eeace91669052e3cecc083896e7329b2
             there was a change in changelog fini to close htime_fd if htime_fd is not
             negative, by default htime_fd is 0 so it close 0 also.
    
    Solution: Initialize htime_fd to -1 after just allocate changelog_priv
              by GF_CALLOC
    
    Fixes: bz#1699025
    Change-Id: I5f7ca62a0eb1c0510c3e9b880d6ab8af8d736a25
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit e87423a826aa4d17c8638b829da7813e41e1a2fd
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Apr 9 20:51:21 2019 +0300

    glusterd-volgen.c: skip fetching some vol settings in a bricks loop.
    
    The values are per volume, and are not going to change
    while processing its bricks, as far as I can understand the code.
    Fetch them and store them outside the loop.
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I2bc263f92f9141ea26a9dfb8265225f38307cbac

commit c261eb6c1fa41b6a0eadabbb3a2f64dc194ec254
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Feb 27 16:02:43 2019 -0800

    Replace memdup() with gf_memdup()
    
    memdup() and gf_memdup() have the same implementation. Removed one API
    as the presence of both can be confusing.
    
    Change-Id: I562130c668457e13e4288e592792872d2e49887e
    updates: bz#1193929
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 0e1223491e964096384edfae5032ed0d50d028ad
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Fri Apr 12 11:35:55 2019 +0800

    ec: fix truncate lock to cover the write in tuncate clean
    
    ec_truncate_clean does writing under the lock granted for truncate,
    but the lock is calculated by ec_adjust_offset_up, so that,
    the write in ec_truncate_clean is out of lock.
    
    Updates: bz#1699189
    Change-Id: Idbe1fd48d26afe49c36b77db9f12e0907f5a4134
    Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>

commit 3140f7d8663da3879be7974e40407d817c570e90
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Apr 11 12:12:12 2019 +0530

    tests/dht: Test that lookups are sent post brick up
    
    Change-Id: I3556793c5e9d58cc6a08644b41dc5740fab2610b
    updates: bz#1628194
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 2589658c7cd967d977fc4f8541379ee2f40eb2fa
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Mar 18 11:57:28 2019 +0530

    cluster/afr: Thin-arbiter SHD fixes
    
    This patch address post-merge review comments for commit
    5784a00f997212d34bd52b2303e20c097240d91c
    
    Change-Id: I7ed954664a2ae8e1091d23ee3ceb9c66e83bfeac
    fixes: bz#1697930
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit a1ce2910522335c2fffaebd941c4aaf861ef04fa
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Apr 8 19:18:51 2019 +0530

    test: Change glustershd_pid update in .t file
    
    Problem: bug-1650403.t && bug-858215.t are throwing error
             at the time of access glustershd pidfile
    
    Solution: Use ps command to findout glustershd pid
    
    Change-Id: I3477345b6220aa039e012e674cba21d741e9abab
    fixes: bz#1697486
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit d08144b64642bf05fdee538b2992278a012737d4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Apr 11 18:13:31 2019 +0530

    glusterd: display an error when rebalance start is failed
    
    fixes: bz#1699176
    credits: Hari Gowtham <hgowtham@redhat.com>
    
    Change-Id: I59134336febf0dc4043483f2f413ac83e3bc79f5
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit cec63a35289e5ee3f3bae8d318350e3f5082325c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Apr 3 16:49:19 2019 +0530

    tests: make sure to traverse all of meta dir
    
    Just to make all files will be listed, which means we have max code-coverage
    
    updates: bz#1693692
    Change-Id: I11d36ac2f4d6d4fb91223aacd423ad23242eb454
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 7108913337f24d3d7a39d919a29872fe50072cf4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Apr 8 18:54:46 2019 +0530

    glusterd: remove glusterd_check_volume_exists() call
    
    As the same functionality is covered in glusterd_volinfo_find
    
    Updates: bz#1193929
    Change-Id: I2308c5fa9b2ca9edaa95f172d0bd914103808c36
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 35dd17e222fe172866e15824e5ac9d242382178c
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Apr 9 13:56:24 2019 +0530

    glusterd: provide a way to detach failed node
    
    When a gluster node in trusted storage pool has failed
    due to hardware issues, volume delete operation fails
    saying "Not all peers are up" and peer detach for failed
    node fails saying "Brick(s) with peer <peer_ip> exists
    in cluster".
    
    The idea here is to use either replace-brick or remove-brick
    command to remove all the bricks hosted by failed node and
    then re-attempting the peer detach. This change adds this
    trick in peer detach error message.
    
    fixes: bz#1697866
    
    Change-Id: I0c58887479d31db603ad8d6535ea9d547880ccc8
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 4bae0b170d5b4fafe4327b8263c1895316ba3696
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 8 12:14:34 2019 +0200

    core: only log seek errors if SEEK_HOLE/SEEK_DATA is available
    
    On RHEL-6 there is no support for SEEK_HOLE/SEEK_DATA and this causes
    the POSIX xlator to return errno=EINVAL. Because of this, the rpc-server
    xlator will log all 'failed' seek attempts. When applications call
    seek() often, the brick logs can grow very quickly and fill up the
    disks.
    
    Messages that get logged are like
    [server-rpc-fops.c:2091:server_seek_cbk] 0-vol01-server: 4947: SEEK-2 (53920aee-062c-4598-aa50-2b4d7821b204), client: worker.example.com-7808-2019/02/08-18:04:57:903430-vol01-client-0-0-0, error-xlator: vol01-posix [Invalid argument]
    
    The problem can be reproduced by running a Gluster Server on RHEL-6,
    with a client running on RHEL-7. The client should execute an
    application that calls lseek() with SEEK_HOLE/SEEK_DATA.
    
    Change-Id: I7b6c16f8e0ba1a183e845cfdb8d5a3f8caeab138
    Fixes: bz#1697316
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 0496523d3c1ac874eeecbb0ecb6516d88438d3c9
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Apr 1 14:44:20 2019 +0530

    client/fini: return fini after rpc cleanup
    
    There is a race condition in rpc_transport later
    and client fini.
    
    Sequence of events to happen the race condition
    1) When we want to destroy a graph, we send a parent down
       event first
    2) Once parent down received on a client xlator, we will
       initiates a rpc disconnect
    3) This will in turn generates a child down event.
    4) When we process child down, we first do fini for
       Every xlator
    5) On successful return of fini, we delete the graph
    
    Here after the step 5, there is a chance that the fini
    on client might not be finished. Because an rpc_tranpsort
    ref can race with the above sequence.
    
    So we have to wait till all rpc's are successfully freed
    before returning the fini from client
    
    Change-Id: I20145662d71fb837e448a4d3210d1fcb2855f2d4
    fixes: bz#1659708
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit d82640511f51a79db6dabea8599c805028fefafb
Author: Anuradha Talur <atalur@commvault.com>
Date:   Thu Nov 29 12:54:21 2018 -0800

    features/cloudsync : Added some new functions
    
    This patch contains the following changes:
    1) Store ID info will now be stored in the inode ctx
    2) Added new readv type where read is made directly
       from the remote store. This choice is made by
       volume set operation.
    3) cs_forget() was missing. Added it.
    
    Change-Id: Ie3232b3d7ffb5313a03f011b0553b19793eedfa2
    fixes: bz#1642168
    Signed-off-by: Anuradha Talur <atalur@commvault.com>

commit 734e6a7e389ea309d5528133ed5bd19064799f13
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Apr 4 22:28:51 2019 +0200

    tests: correctly check open fd's when gfid is missing
    
    The helper funcion get_fd_count() returns how many open fd's has a given
    gfid on a brick. It could happen that the brick doesn't have information
    about that inode because it has not been previously accessed.
    
    Before this patch, the function returned "" when the inode was not
    present. This caused basic/ec/ec-fix-openfd.t test to fail because it
    was expecting '0' as the result.
    
    This patch forces get_fd_count() to return '0' when the gfid is not
    present in the state dump.
    
    Change-Id: I848b57744e96656bf81fbb7b126a5faf44e535eb
    updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit dc06e4c408187afcc58ebd72386490ad1e58de03
Author: Anuradha Talur <atalur@commvault.com>
Date:   Tue Nov 20 13:15:26 2018 -0800

    storage/posix: changes with respect to cloudsync
    
    Main changes include logic to update iatt buf
    with file size from extended attributes in posix
    rather than having this logic in cloudsync xlator.
    
    Change-Id: I44f5f8df7a01e496372557fe2f4eff368dbdaa33
    fixes: bz#1642168
    Signed-off-by: Anuradha Talur <atalur@commvault.com>

commit d837b4518c3148752b2eb4d55d22f22c57aa96c2
Author: Anuradha Talur <atalur@commvault.com>
Date:   Mon Nov 19 17:57:18 2018 -0800

    mgmt/glusterd: Make changes related to cloudsync xlator
    
    1) The placement of cloudsync xlator has been changed
    to make it shard xlator's child. If cloudsync has to
    work with shard in the graph, it needs to be child of shard.
    
    Change-Id: Ib55424fdcb7ce8edae9f19b8a6e3d3ba86c1f0c4
    fixes: bz#1642168
    Signed-off-by: Anuradha Talur <atalur@commvault.com>

commit 22e848f88e2cb9510e82fb4875c182240fff3303
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Mar 29 08:30:49 2019 +0530

    protocol: add an option to force using old-protocol
    
    As protocol implements every fop, and in general a large part of
    the codebase. Considering our regression is run mostly in 1 machine,
    there was no way of forcing the client to use old protocol (while new
    one is available). With this patch, a new 'testing' option is provided
    which forces client to use old protocol if found.
    
    This should help increase the code coverage by at least 10k lines overall.
    
    updates: bz#1693692
    Change-Id: Ie45256f7dea250671b689c72b4b6f25037cef948
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 398b53adb281e459281f74a9f96a12ee48da7daa
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Apr 4 23:57:20 2019 +0200

    ec: increase line coverage of ec
    
    Test ec-cpu-extensions.t has been modified so that it uses a bigger
    matrix. This makes use of more functions from ec-code-c.c. Changing
    read-policy to round-robin increases even more the functions used,
    reaching 100% of line and function coverage for this file.
    
    Change-Id: I26e4d33269cbd67f5d76d862f4cf1e69285e85e1
    updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit eeacb402ac465a1981b7b53b9796fa65a40bdde2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Mar 29 00:10:15 2019 +0530

    tests: add a tests for trace xlator
    
    this test alone covers most of code of trace xlator
    
    updates: bz#1693692
    Change-Id: I287c72ee89bd1c02d992b020d5644e8dac0b77ab
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 064aad721c249d63fb89686b32e5d15de50e2f8c
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Apr 5 09:17:02 2019 +0530

    build: glusterfs build is failing on RHEL-6
    
    Problem: glusterfs build is throwing error undefined
             reference to `dlclose' on RHEL 6
    
    Solution: Add LIB_DL link in Makefile.am to resolve the same
    
    Fixes: bz#1696512
    Change-Id: I58019ca9e29d569d8e6df282b8ab178ad540843b
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit efbf8abcc3bc729a90d4a7b57dc515f1df8a5863
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 9 14:58:29 2019 +0530

    glusterd: load ctime in the client graph only if it's not turned off
    
    Considering ctime is a client side feature, we can't blindly load ctime
    xlator into the client graph if it's explicitly turned off, that'd
    result into backward compatibility issue where an old client can't mount
    a volume configured on a server which is having ctime feature.
    
    Fixes: bz#1697907
    Change-Id: I6ae7b96d056073aa6746de9a449cf319786d45cc
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit ae097b8ad5c160aed43d82187b623f053adf11b4
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Apr 5 08:59:35 2019 +0300

    glusterd-volgen.c: skip fetching skip-CLIOT in a loop.
    
    Its value is not going to change within the loop, as far as I can
    understand the code.
    Fetch and store it outside the loop.
    
    Change-Id: I6327c23212dceec6006349421ef185495892dd8a
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 4bd4b0a9437189cef439833a0ed70005db9f8409
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Apr 3 08:27:05 2019 +0530

    glusterd: remove redundant glusterd_check_volume_exists () calls
    
    A pattern of following was found in multiple places where both
    glusterd_check_volume_exists and glusterd_volinfo_find do the same job.
    We just need one of them not both. In a scaled environment having many
    volumes this is a bottleneck to iterate over the volume list to find a
    volume twice!
    
        exists = glusterd_check_volume_exists(volname);
        ret = glusterd_volinfo_find(volname, &volinfo);
        if ((ret) || (!exists)) {
    
    Credits: ykaul@redhat.com for finding this out
    
    Updates: bz#1193929
    Change-Id: Ie116fe5c93e261a2bddd267c28ccb20a2884a36f
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 4f6749aa308152dc6350632991a6ae11b8467fb1
Author: rishubhjain <rishubhjain47@gmail.com>
Date:   Sat Mar 30 15:46:38 2019 +0530

    GlusterD: Resolves the issue of referencing memory after it has been freed
    
    Setting the pointer to NULL after GF_FREE() and checking the pointer value
    before calling GF_FREE() to avoid referencing memory after its has been freed
    
    CID: 1398622
    
    Change-Id: Iba0d8879abccf5923a69132a207d53bb94551417
    updates: bz#789278
    Signed-off-by: rishubhjain <rishubhjain47@gmail.com>

commit 66b32363b203a21c41fa4988b55ca91f99d07d6b
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Mar 25 15:56:56 2019 +0530

    cluster/dht: refactor dht lookup functions
    
    Part 1:  refactor the dht_lookup_dir_cbk
    and dht_selfheal_directory functions.
    Added a simple dht selfheal directory test
    
    Change-Id: I1410c26359e3c14b396adbe751937a52bd2fcff9
    updates: bz#1590385
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 443cb74587c251fecbcdfa119a3620ff01131a36
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Apr 4 12:23:11 2019 +0530

    cluster/afr: Invalidate inode on change of split-brain-choice
    
    When split-brain choice is changed from one brick to another
    brick, inode-invalidate is not called so readv call is served
    from cache leading to failures in split-brain-resolution.t.
    Fixed it by calling inode_invaldate() when this happens.
    
    updates bz#1193929
    Change-Id: I2624614eec38c0303f3e1dc55dfae3d4b864218b
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 0e067fa663dcfdafa093c4a5fa8bdc47eb57cbe0
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Apr 2 16:21:51 2019 -0400

    tests/bitrot: enable self-heal daemon before accessing the files
    
    For testing the recovery of bad (or corrupted files) in a dispersed
    volume, first enable self-heal daemon and let heal happen.
    
    In bitrot feature, if a file becomes corrupted, the solution recommended
    is to remove that file directly from the backend and then allowing heal
    to happen. Hence turn on self-heal daemon and allow the heal to happen
    after removing corrupted copy from the backend.
    
    Change-Id: I7186110398ec1aee7e5727b9d1aac9a01db4d831
    fixes: bz#1695327
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit da47caf2405c08c9abafc4a55525a8b2c2dd5bb8
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Mar 18 12:54:54 2019 +0530

    cluster/ec: Fix handling of heal info cases without locks
    
    When we use heal info command, it takes lot of time as in
    some cases it takes lock on entries to find out if the
    entry actually needs heal or not.
    
    There are some cases where we can avoid these locks and
    can conclude if the entry needs heal or not.
    
    1 - We do a lookup (without lock) on an entry, which we found in
    .glusterfs/indices/xattrop, and find that lock count is
    zero. Now if the file contains dirty bit set on all or any
    brick, we can say that this entry needs heal.
    
    2 - If the lock count is one and dirty is greater than 1,
    then it also means that some fop had left the dirty bit set
    which made the dirty count of current fop (which has taken lock)
    more than one. At this point also we can definitely say that
    this entry needs heal.
    
    This patch is modifying code to take into consideration above two
    points.
    It is also changing code to not to call ec_heal_inspect if ec_heal_do
    was called from client side heal. Client side heal triggeres heal
    only when it is sure that it requires heal.
    
    [We have changed the code to not to call heal for lookup]
    
    updates bz#1689799
    Change-Id: I7f09f0ecd12f65a353297aefd57026fd2bebdf9c
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 1a59cf8c6354ad970edc96f7b74a834672ab2df6
Author: Anuradha Talur <atalur@commvault.com>
Date:   Thu Oct 25 17:23:10 2018 -0400

    libglusterfs: define macros needed for cloudsync
    
    Change-Id: Iec5ce7f17fbf899f881a58cd20c4c967e3b71668
    fixes: bz#1642168
    Signed-off-by: Anuradha Talur <atalur@commvault.com>

commit d8233cbe529e22f920ea0485ed55d99384642155
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 28 22:07:34 2019 +0530

    sdfs: enable pass-through
    
    we have 'sdfs-sanity.t' which covers at least 90% of the functions
    and 70% of lines in the translator. But the recent changes to
    disable it due to performance impact made even the test to not
    consider the translator.
    
    updates: bz#1693692
    Change-Id: I0ebcb307c4ab48a6e59ded27bf39f72ce2304ebc
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 024cafea8965086267645be0eae86bcdf5a5d106
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 28 09:36:33 2019 -0400

    rpclib: slow floating point math and libm
    
    In release-6 rpc/rpc-lib (libgfrpc) added the function
    get_rightmost_set_bit() which calls log2(3), a call that takes
    a floating point parameter.
    
    It's used thusly:
        right_most_unset_bit = get_rightmost_set_bit(...);
    
    (So is it really the right-most unset bit, or the right-most set bit?)
    
    It's unclear to me whether this is in the data path or not. If it is,
    it's rather scary to think about integer-to-float conversions and slow
    calls to libm functions in the data path.
    
    gcc and clang have __builtin_ctz() which returns the same result as
    get_rightmost_set_bit(), and does it substantially faster. Approx
    20M iterations of get_rightmost_set_bit() took ~33sec of wall clock
    time on my devel machine, while 20M iterations of __builtin_ctz()
    took < 9sec; get_rightmost_set_bit() is 3x slower than __builtin_ctz().
    
    And as a side benefit, we can again eliminate the need to link libgfrpc
    with libm.
    
    Change-Id: If9e7e80874577c52223f8125b385fc930de20699
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit cada4b432e9373c3ff8423a23c41a455aba4fc4a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Mar 20 18:10:57 2019 +0200

    changelog: remove unused code.
    
    Seems to be unused.
    
    Change-Id: I75eed9641dd030a1fbb1b942a9d818f10a7e1437
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit e3ef34cc33772e1f05a6a3dbaad2352f6561e5f0
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 1 09:55:54 2019 +0530

    posix-acl: remove default functions, and use library fn instead
    
    this works as a better solution, as we reuse more functions from library.
    
    Also just do write/read on a file when acl is enabled, so we can see
    improvement in code coverage.
    
    updates: bz#1693692
    Change-Id: If3359260c8ec2cf4fcf148fb4b95fdecc922c252
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ec1b84300fe267dd12c1e42e7e91905db935f1e2
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Mar 22 10:40:45 2019 +0530

    transport/socket: log shutdown msg occasionally
    
    Change-Id: If3fc0884e7e2f45de2d278b98693b7a473220a5f
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1691616

commit 0a827c1da96302661202e46ea43b6e2526a7ac87
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 1 11:53:57 2019 +0530

    cluster/afr: Send inodelk/entrylk with non-zero lk-owner
    
    Found missing assignment of lk-owner for an inodelk/entrylk before winding
    the fops. locks xlator at the moment allows this operation. This leads to
    multiple threads in the same client being able to get locks on the inode
    because lk-owner is same and transport is same. So isolation with locks can't
    be achieved. To fix it, we need locks xlator change which will disallow
    null-lk-owner based inodelk/entrylk/lk. To achieve that we need to first
    fix all the places which do this mistake.
    
    updates bz#1624701
    Change-Id: Ic3431da3f451a1414f1f4fdcfc4cf41e555f69dd
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d0d3e10d44366c68fc153e48b229e72a4aa26e61
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 2 10:45:15 2019 +0530

    logging: Fix GF_LOG_OCCASSIONALLY API
    
    GF_LOG_OCCASSIONALLY doesn't log on the first instance rather at every
    42nd iterations which isn't effective as in some cases we might not have
    the code flow hitting the same log for as many as 42 times and we'd end
    up suppressing the log.
    
    Fixes: bz#1694925
    Change-Id: Iee293281d25a652b64df111d59b13de4efce06fa
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit dfa255ae7f2dab4fb3d84c67a0452c5b32455877
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Mar 29 00:05:47 2019 +0530

    tests: add statedump to playground
    
    It helps in increased code coverage of playground.
    
    updates: bz#1693692
    Change-Id: I81bcf30be1450948a6360d8915f06b973387a560
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit bc3694d7cfc868a2ed6344ea123faf19fce28d13
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Feb 25 10:05:32 2019 +0530

    mgmt/shd: Implement multiplexing in self heal daemon
    
    Problem:
    
    Shd daemon is per node, which means they create a graph
    with all volumes on it. While this is a great for utilizing
    resources, it is so good in terms of performance and managebility.
    
    Because self-heal daemons doesn't have capability to automatically
    reconfigure their graphs. So each time when any configurations
    changes happens to the volumes(replicate/disperse), we need to restart
    shd to bring the changes into the graph.
    
    Because of this all on going heal for all other volumes has to be
    stopped in the middle, and need to restart all over again.
    
    Solution:
    
    This changes makes shd as a per volume daemon, so that the graph
    will be generated for each volumes.
    
    When we want to start/reconfigure shd for a volume, we first search
    for an existing shd running on the node, if there is none, we will
    start a new process. If already a daemon is running for shd, then
    we will simply detach a graph for a volume and reatach the updated
    graph for the volume. This won't touch any of the on going operations
    for any other volumes on the shd daemon.
    
    Example of an shd graph when it is per volume
    
                               graph
                         -----------------------
                         |     debug-iostat    |
                         -----------------------
                        /         |             \
                       /          |              \
                  ---------    ---------      ----------
                  | AFR-1 |    | AFR-2 |      |  AFR-3 |
                  --------     ---------      ----------
    
    A running shd daemon with 3 volumes will be like-->
    
                               graph
                         -----------------------
                         |     debug-iostat    |
                         -----------------------
                        /           |           \
                       /            |            \
                  ------------   ------------  ------------
                  | volume-1 |   | volume-2 |  | volume-3 |
                  ------------   ------------  ------------
    
    Change-Id: Idcb2698be3eeb95beaac47125565c93370afbd99
    fixes: bz#1659708
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 92ae26ae8039847e38c738ef98835a14be9d4296
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 28 17:55:54 2019 +0530

    protocol/client: Do not fallback to anon-fd if fd is not open
    
    If an open comes on a file when a brick is down and after the brick comes up,
    a fop comes on the fd, client xlator would still wind the fop on anon-fd
    leading to wrong behavior of the fops in some cases.
    
    Example:
    If lk fop is issued on the fd just after the brick is up in the scenario above,
    lk fop will be sent on anon-fd instead of failing it on that client xlator.
    This lock will never be freed upon close of the fd as flush on anon-fd is
    invalid and is not wound below server xlator.
    
    As a fix, failing the fop unless the fd has FALLBACK_TO_ANON_FD flag.
    
    Change-Id: I77692d056660b2858e323bdabdfe0a381807cccc
    fixes bz#1390914
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 500bd0014128e6727e83b6cb77e8ac94304b8f4a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 7 17:02:36 2019 +0530

    afr: thin-arbiter read txn fixes
    
    - Fixes afr_ta_read_txn() to handle inode refresh failures.
    code-path.
    - Fixes a double free issue of dict.
    
    Note: This patch address post-merge review comments for commit
    69532c141be160b3fea03c1579ae4ac13018dcdf
    
    fixes: bz#1686398
    Change-Id: Id5299b45b68569d47df6b73755918237a1592cb4
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit c3fb394137769429a296a41160be8284e10d1412
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Mar 13 08:51:31 2019 +0530

    mount.glusterfs: change the error message
    
    In scenarios where a mount fails before creating log file, doesn't
    make sense to give message to 'check log file'. See below:
    
    ```
    ERROR: failed to create logfile "/var/log/glusterfs/mnt.log" (No space left on device)
    ERROR: failed to open logfile /var/log/glusterfs/mnt.log
    Mount failed. Please check the log file for more details.
    ```
    
    Fixes: bz#1688068
    Change-Id: I1d837caa4f9bc9f1a37780783e95007e01ae4e3f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 4a03a71c6171f6e8382664d9d29857d06ef37741
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Mar 28 14:59:00 2019 +0530

    gfapi: Unblock epoll thread for upcall processing
    
    With commit#ad35193,we have made changes to offload
    processing upcall notifications to synctask so as not
    to block epoll threads. However seems like the issue wasnt
    fully addressed.
    
    In "glfs_cbk_upcall_data" -> "synctask_new1" after creating synctask
    if there is no callback defined, the thread waits on synctask_join
    till the syncfn is finished. So that way even with those changes,
    epoll threads are blocked till the upcalls are processed.
    
    Hence the right fix now is to define a callback function for that
    synctask "glfs_cbk_upcall_syncop" so as to unblock epoll/notify threads
    completely and the upcall processing can happen in parallel by synctask
    threads.
    
    Change-Id: I4d8645e3588fab2c3ca534e0112773aaab68a5dd
    fixes: bz#1693575
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 877af725b3e35b548d6d7aeec5adb21721d8bf8b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Mar 28 07:17:16 2019 -0400

    geo-rep: Fix syncing multiple rename of symlink
    
    Problem:
    Geo-rep fails to sync rename of symlink if it's
    renamed multiple times if creation and rename
    happened successively
    
    Worker crash at slave:
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/repce.py",  in worker
        res = getattr(self.obj, rmeth)(*in_data[2:])
      File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", in entry_ops
        [ESTALE, EINVAL, EBUSY])
      File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", in errno_wrap
        return call(*arg)
      File "/usr/libexec/glusterfs/python/syncdaemon/libcxattr.py", in lsetxattr
        cls.raise_oserr()
      File "/usr/libexec/glusterfs/python/syncdaemon/libcxattr.py", in raise_oserr
        raise OSError(errn, os.strerror(errn))
    OSError: [Errno 12] Cannot allocate memory
    
    Geo-rep Behaviour:
    1. SYMLINK doesn't record target path in changelog.
       So while syncing SYMLINK, readlink is done on
       master to get target path.
    
    2. Geo-rep will create destination if source is not
       present while syncing RENAME. Hence while syncing
       RENAME of SYMLINK, target path is collected from
       destination.
    
    Cause:
    If symlink is created and renamed multiple times, creation of
    symlink is ignored, as it's no longer present on master at
    that path. While symlink is renamed multiple times at master,
    when syncing first RENAME of SYMLINK, both source and destination
    is not present, hence target path is not known.  In this case,
    while creating destination directly at slave,  regular file
    attributes were encoded into blob instead of symlink,
    causing failure in gfid-access translator while decoding
    blob.
    
    Solution:
    While syncing of RENAME of SYMLINK, when target is not known
    and when src and destination is not present on the master,
    don't create destination. Ignore the rename. It's ok to ignore.
    If it's unliked, it's fine.  If it's renamed to something else,
    it will be synced then.
    
    Change-Id: Ibdfa495513b7c05b5370ab0b89c69a6802338d87
    fixes: bz#1693648
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 6ae36418834ddcd9f68fe7ef9b09b077cdf68ca3
Author: Poornima G <pgurusid@redhat.com>
Date:   Sun Mar 24 09:40:50 2019 +0530

    client-rpc: Fix the payload being sent on the wire
    
    The fops allocate 3 kind of payload(buffer) in the client xlator:
    - fop payload, this is the buffer allocated by the write and put fop
    - rsphdr paylod, this is the buffer required by the reply cbk of
      some fops like lookup, readdir.
    - rsp_paylod, this is the buffer required by the reply cbk of fops like
      readv etc.
    
    Currently, in the lookup and readdir fop the rsphdr is sent as payload,
    hence the allocated rsphdr buffer is also sent on the wire, increasing
    the bandwidth consumption on the wire.
    
    With this patch, the issue is fixed.
    
    Fixes: bz#1692093
    Change-Id: Ie8158921f4db319e60ad5f52d851fa5c9d4a269b
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 108e4f3481225f98c12f7c283e1ef0388863cf8b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 28 11:03:34 2019 +0530

    rpc: Remove duplicate code
    
    rpc_clnt_disable() and rpc_clnt_disconnect() have same code.
    Removed rpc_clnt_disconnect() and moved calls to rpc_clnt_disconnect()
    to rpc_clnt_disable()
    
    updates bz#1193929
    Change-Id: I965f57cc1d5af36d266810125558b6f5e5f279d4
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit a7110486d048fa379f33ae4e0ba94b5ef3560489
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Tue Mar 26 10:08:00 2019 +0800

    glusterd: fix potential locking issue on peer probe
    
    There are two cases to restart brick, one is when glusterd starts or
    quorum is met, another is when new peers are joined and quorum is
    changes. In the later case, sync_lock is not taken, and may cause lock
    corruption.
    
    Change-Id: I0844e7a631350f5ee00bdacb613602bffffcdf9f
    fixes: bz#1692612
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit c574984e19d59e351372eacce0ce11fb36e96dd4
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Mar 26 13:20:13 2019 +0530

    geo-rep: fix integer config validation
    
    ssh-port validation is mentioned as `validation=int` in template
    `gsyncd.conf`, but not handled this during geo-rep config set.
    
    Fixes: bz#1692666
    Change-Id: I3f19d9b471b0a3327e4d094dfbefcc58ed2c34f6
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 313dcefe7a62bd16cd794040df068f9bec9c6927
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Nov 28 11:22:52 2018 +0530

    cluster/ec: Don't enqueue an entry if it is already healing
    
    Problem:
    1 - heal-wait-qlength is by default 128. If shd is disabled
    and we need to heal files, client side heal is needed.
    If we access these files that will trigger the heal.
    However, it has been observed that a file will be enqueued
    multiple times in the heal wait queue, which in turn causes
    queue to be filled and prevent other files to be enqueued.
    
    2 - While a file is going through healing and a write fop from
    mount comes on that file, it sends write on all the bricks including
    healing one. At the end it updates version and size on all the
    bricks. However, it does not unset dirty flag on all the bricks,
    even if this write fop was successful on all the bricks.
    After healing completion this dirty flag remain set and never
    gets cleaned up if SHD is disabled.
    
    Solution:
    1 - If an entry is already in queue or going through heal process,
    don't enqueue next client side request to heal the same file.
    
    2 - Unset dirty on all the bricks at the end if fop has succeeded on
    all the bricks even if some of the bricks are going through heal.
    
    Change-Id: Ia61ffe230c6502ce6cb934425d55e2f40dd1a727
    updates: bz#1593224
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 8016d51a3bbd410b0b927ed66be50a09574b7982
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Mar 15 19:31:03 2019 +0530

    afr: add client-pid to all gf_event() calls
    
    client-pid for glustershd is GF_CLIENT_PID_SELF_HEALD
    client-pid for glfsheal is GF_CLIENT_PID_GLFS_HEALD
    
    updates: bz#1689250
    Change-Id: Ib3a863af160ff48c822a5e6b0c27c575c9887470
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 08d502c3b05c6f7831bb4cc764bd458b405a99b1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 14 18:41:11 2019 +0530

    gfapi: add function to set client-pid
    
    This api offers the ability to set the pid of a client to a particular
    value, identical to how gluster fuse clients provide the --client-pid
    option. This is an internal API to be used by gluster processes only. See
    https://lists.gluster.org/pipermail/gluster-devel/2019-March/055925.html
    for more details. Currently glfsheal is the only proposed consumer.
    
    updates: bz#1689250
    Change-Id: I0620be2127d79d69cdd57cffb29bba44e6e5da1f
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit a87038229e26723406e48035519f0e6dfea4e45c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 21 01:21:13 2019 -0400

    build: link libgfrpc with MATH_LIB (libm, -lm)
    
    tl;dnr: libgfrpc.so calls log2(3) from libm; it should be explicitly
    linked with -lm
    
    the autoconf/automake/libtool stack is more or less forgiving on
    different distributions. On forgiving systems libtool will semi-
    magically link with implicit dependencies. But on Ubuntu, which
    seems to be tending toward being less forgiving, the link of libgfrpc
    will fail with an unresolved referencee to log2(3).
    
    Change-Id: I9fae09ddb81e49004fbea4d7d83b95fb64a484b0
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit c9408e1bbfc4e2a85080bc6410bd2c9cdf259534
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Mar 21 19:51:30 2019 +0200

    mem-pool: remove dead code.
    
    Change-Id: I3bbda719027b45e1289db2e6a718627141bcbdc8
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 263dc982264f0ef646dbd4977254b39928ae6410
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 25 14:06:25 2019 +0530

    cluster/afr: Remove un-used variables related to pump
    
    updates bz#1193929
    Change-Id: I01b60d644f517c00a1bcc127bf9a8ed90b6eb7a0
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 34e010d64905b7387de57840d3fb16a326853c9b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Mar 18 16:08:04 2019 +0530

    glusterd: fix txn-id mem leak
    
    This commit ensures the following:
    1. Don't send commit op request to the remote nodes when gluster v
    status all is executed as for the status all transaction the local
    commit gets the name of the volumes and remote commit ops are
    technically a no-op. So no need for additional rpc requests.
    2. In op state machine flow, if the transaction is in staged state and
    op_info.skip_locking is true, then no need to set the txn id in the
    priv->glusterd_txn_opinfo dictionary which never gets freed.
    
    Fixes: bz#1691164
    Change-Id: Ib6a9300ea29633f501abac2ba53fb72ff648c822
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 4acf03d304e88ca3d10d3d7076208f1462228bbb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Mar 19 16:45:06 2019 +0200

    Multiple files: remove HAVE_BD_XLATOR related code.
    
    The BD translator was removed some time ago,
    (in commit a907e468e724c32b9833ce59806fc215c7122d63).
    This completes the work.
    
    Compile-tested only!
    updates: bz#1635688
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I999df52e479a72d3cc9523f22f9056de17eb559c

commit 1f94395c356748c0f51c76d5de3be5f6cf603547
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Mar 21 09:57:10 2019 +0530

    inode: fix unused vars
    
    Commit 6d6a3b2 introduced some unused vars. This patch defines them
    within #ifdef DEBUG
    
    Fixes: bz#1580315
    Change-Id: I8a332b00c3ffb66689b4b6480c490b9436c17d63
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit a7c746577249af6326907e280843e1f4c0231bb0
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Mar 19 22:51:14 2019 +0530

    fuse : fix high sev coverity issue
    
    This patch fixed coverity issue in fuse-bridge.c.
    
    CID : 1398630 : Resource leak
    CID : 1399757 : Uninitialized pointer read
    
    updates: bz#789278
    
    Change-Id: I69f8591400ee56a5d215eeac443a8e3d7777db27
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 8aff9cc5c6277ef7dacfb89f1392b7c2eda9b825
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Mar 20 13:05:44 2019 +0200

    server.c: fix Coverity CID 1399758
    
    1399758 Dereference before null check
    
    It was introduced @ commit 67f48bfcc16a38052e6c9ae7c25e69b03b8ae008
    
    
    updates: bz#789278
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I1424b008b240691fe2a8924e31c708d0fb4f362d

commit f2f07591b2de9ba45bbc3eb4f601d1e9a327190b
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Feb 26 18:04:18 2019 +0530

    rpc/transport: Missing a ref on dict while creating transport object
    
    while creating rpc_tranpsort object, we store a dictionary without
    taking a ref on dict but it does an unref during the cleaning of the
    transport object.
    
    So the rpc layer expect the caller to take a ref on the dictionary
    before passing dict to rpc layer. This leads to a lot of confusion
    across the code base and leads to ref leaks.
    
    Semantically, this is not correct. It is the rpc layer responsibility
    to take a ref when storing it, and free during the cleanup.
    
    I'm listing down the total issues or leaks across the code base because
    of this confusion. These issues are currently present in the upstream
    master.
    
    1) changelog_rpc_client_init
    
    2) quota_enforcer_init
    
    3) rpcsvc_create_listeners : when there are two transport, like tcp,rdma.
    
    4) quotad_aggregator_init
    
    5) glusterd: init
    
    6) nfs3_init_state
    
    7) server: init
    
    8) client:init
    
    This patch does the cleanup according to the semantics.
    
    Change-Id: I46373af9630373eb375ee6de0e6f2bbe2a677425
    updates: bz#1659708
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 6d6a3b298ee81c6c7d93941365852c1bdb42c3c1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Mar 13 09:42:33 2019 +0530

    inode: don't dump the whole table to CLI
    
    dumping the whole inode table detail to screen doesn't solve any
    purpose. We should be getting only toplevel details on CLI, and then
    if one wants to debug further, then they need to get to 'statedump'
    to get full details.
    
    Fixes: bz#1580315
    Change-Id: Iaf3de94602f9c76832c3c918ffe2ad13c0b0e448
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 7413d0c0c20243764858ef817c5e2b42791ff302
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Mar 18 11:16:49 2019 +0200

    glusterd-locks: misc. changes.
    
    Move to use dict_*n() functions, where it made sense.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ie9c4b2021d2229ea9a815cc75e9eb8c3945c109e

commit 06fa261207f0f0625c52fa977b96e5875e9a91e0
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Mar 14 10:55:52 2019 +0530

    socket/ssl: fix crl handling
    
    Problem:
    Just setting the path to the CRL directory in socket_init() wasn't working.
    
    Solution:
    Need to use special API to retrieve and set X509_VERIFY_PARAM and set
    the CRL checking flags explicitly.
    Also, setting the CRL checking flags is a big pain, since the connection
    is declared as failed if any CRL isn't found in the designated file or
    directory. A comment has been added to the code appropriately.
    
    Change-Id: I8a8ed2ddaf4b5eb974387d2f7b1a85c1ca39fe79
    fixes: bz#1687326
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 43092dfd25295aba9d2426a82ea4027e08a7a2c5
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Mon Mar 18 20:47:54 2019 +0800

    cluster-syncop: avoid duplicate unlock of inodelk/entrylk
    
    When using ec, there are many messages at brick log as,
    
    [inodelk.c:514:__inode_unlock_lock] 0-test-locks:  Matching lock not found for unlock 0-9223372036854775807, lo=68e040a84b7f0000 on 0x7f208c006f78
    [MSGID: 115053] [server-rpc-fops_v2.c:280:server4_inodelk_cbk] 0-test-server: 2557439: INODELK <gfid:df4e41be-723f-4289-b7af-b4272b3e880c> (df4e41be-723f-4289-b7af-b4272b3e880c), client: CTX_ID:67d4a7f3-605a-4965-89a5-31309d62d1fa-GRAPH_ID:0-PID:1659-HOST:openfs-node2-PC_NAME:test-client-1-RECON_NO:-28, error-xlator: test-locks [Invalid argument]
    
    Change-Id: Ib164d29ebb071f620a4ca9679c4345ef7c88512a
    Updates: bz#1689920
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 4d98b55eadf46beb35de88e6584c694ec75cd49d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 26 14:27:33 2019 +0530

    mount/fuse: Fix spelling mistake
    
    updates bz#1193929
    Change-Id: I55ffa8f086ad9570f2526d91c196d7de9ffe6add
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 240e1d6821fbb779c3dd73f6f0225d755a5b7cc6
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Mar 14 20:06:54 2019 +0530

    geo-rep: IPv6 support
    
    `address_family=inet6` needs to be added while mounting master and
    slave volumes in gverify script.
    
    New option introduced to gluster cli(`--inet6`) which will be used
    internally by geo-rep while calling `gluster volume info
    --remote-host=<ipv6>`.
    
    Fixes: bz#1688833
    Change-Id: I1e0d42cae07158df043e64a2f991882d8c897837
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 3f3da526333b91c787b2388319cb16297b4d8cc3
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Wed Mar 13 21:13:38 2019 +0800

    shard: fix crash caused by using null inode
    
    Change-Id: I156bf962223304e586b83a36be59a0ca74589b43
    Updates: bz#1688287
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 63159cdb5374f458d7d2bffec24d4720ffc96d6c
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Mar 8 10:42:12 2019 +0530

    cluster/afr : TA: Return actual error code in case of failure
    
    In afr_ta_post_op_do, we were sending EIO for every failure.
    However, the original error code should be sent.
    
    Change-Id: I9fdc15dac00d758baf8e6f14db244f526481a63a
    updates: bz#1686711
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit f5987d38f216a3142dfe45f03bf66ff4827d9b55
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 11 14:04:39 2019 +0530

    storage/posix: Remove nr_files usage
    
    nr_files is supposed to represent the number of files opened in posix.
    Present logic doesn't seem to handle anon-fds because of which the
    counts would always be wrong.
    
    I don't remember anyone using this value in debugging any problem probably
    because we always have 'ls -l /proc/<pid>/fd' which not only prints the
    fds that are active but also prints their paths. It also handles directories
    and anon-fds which actually opened the file. So removing this code
    instead of fixing the buggy logic to have the nr_files.
    
    fixes bz#1688106
    Change-Id: Ibf8713fdfdc1ef094e08e6818152637206a54040
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 08a9f198d576bbae3596536bbd2c4d34dadd1a93
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Mar 13 12:56:58 2019 +0530

    tests/bug-844688.t: test bug-844688.t is failing on master
    
    Test case bug-844688.t is failing quite frequently on master.
    This test check for the existence of call_stack, frame creation
    time.
    
    But there is a chance that at a point in time, the stack count
    might become zero. So doing the check in EXPECT_WITHIN make
    more sense.
    
    Change-Id: Id2ede7f6fdcb5f016f52c5c0557ce6ac510d4e96
    updates: bz#1688116
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 67f48bfcc16a38052e6c9ae7c25e69b03b8ae008
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Mar 12 13:27:34 2019 +0530

    glusterfsd: Brick is getting crash at the time of startup
    
    Problem: Brick is getting crash because graph was not activated
             at the time of accessing server_conf
    
    Solution: To avoid the crash check ctx->active before processing
              a request
    
    Change-Id: Ib112e0eace19189e45f430abdac5511c026bed47
    fixes: bz#1687705
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a395395e7fa16e12b3c3d9f9ba2a7bdbf4b50d74
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Mar 13 13:05:59 2019 +0530

    test: Fix a missing a '$' symbol
    
    While checking a test case using EXPECT_WITHIN, the
    argument is actually missing a '$' symbol to denote
    the token as a variable in bash
    
    Change-Id: I5b9150acdea000b29e94cfb01d975c77f5ece3e5
    fixes: bz#1688116
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit a9d04541fd0f0018d196c08b0f0091a19649cb93
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Mar 12 18:00:37 2019 +0530

    dht: NULL check before setting error flag
    
    Function dht_common_mark_mdsxattr blindly setting value for
    an integer pointer without validating it. In fact there are
    two callers of this function that passes NULL value to the
    same pointer which leads to a crash.
    
    Change-Id: Id94ffe216f6a21f007b3291bff0b1e1c1989075c
    fixes: bz#1687811
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 66986594a9023c49e61b32769b7e6b260b600626
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Mar 1 13:41:24 2019 +0530

    glusterfsd: Multiple shd processes are spawned on brick_mux environment
    
    Problem: Multiple shd processes are spawned while starting volumes
             in the loop on brick_mux environment.glusterd spawn a process
             based on a pidfile and shd daemon is taking some time to
             update pid in pidfile due to that glusterd is not able to
             get shd pid
    
    Solution: Commit cd249f4cb783f8d79e79468c455732669e835a4f changed
              the code to update pidfile in parent for any gluster daemon
              after getting the status of forking child in parent.To resolve
              the same correct the condition update pidfile in parent only
              for glusterd and for rest of the daemon pidfile is updated in
              child
    
    Change-Id: Ifd14797fa949562594a285ec82d58384ad717e81
    fixes: bz#1684404
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 3e36060b13a86ea4e39fb717dc7f59aacd47bf4f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Feb 27 22:05:51 2019 +0200

    io-threads.c: Potentially skip a lock.
    
    Before going into the lock, verify stub_cnt != 0.
    Otherwise, let's skip this code.
    
    Unrelated, switch a CALLOC to MALLOC, as we
    initialize all members right away. This allocation
    is done also under lock, so also should help a bit.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ie2fe6adff41ae4969abff95eff945b54e1a01d32

commit 48ca0c05df4cee66cf8d07e19ee2267fc9ba920b
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Mar 7 22:26:49 2019 +0530

    cluster/afr: Send truncate on arbiter brick from SHD
    
    Problem:
    In an arbiter volume configuration SHD will not send any writes onto the arbiter
    brick even if there is data pending marker for the arbiter brick. If we have a
    arbiter setup on the geo-rep master and there are data pending markers for the files
    on arbiter brick, SHD will not mark any data changelog during healing. While syncing
    the data from master to slave, if the arbiter-brick is considered as ACTIVE, then
    there is a chance that slave will miss out some data. If the arbiter brick is being
    newly added or replaced there is a chance of slave missing all the data during sync.
    
    Fix:
    If there is data pending marker for the arbiter brick, send truncate on the arbiter
    brick during heal, so that it will record truncate as the data transaction in changelog.
    
    Change-Id: I3242ba6cea6da495c418ef860d9c3359c5459dec
    fixes: bz#1686568
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 32824af10a8daa7239157af3326769c4a6b8f72f
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Mar 8 11:12:29 2019 +0530

    glusterd: change the op-version
    
    as commit 073444 is backported to release-5.4 branch, op-version
    for this change should 5.4 instead of 6.
    
    fixes: bz#1685120
    
    Change-Id: Id504b9a1446125cea7c6a32117ccc44f28e73aa7
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit ca9bef7f1538beb570fcb190ff94f86f0b8ba38a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jan 30 14:24:14 2019 +0530

    rpm: add thin-arbiter package
    
    Discussion on thin arbiter volume -
    https://github.com/gluster/glusterfs/issues/352#issuecomment-350981148
    
    Main idea of having this rpm package is to deploy thin-arbiter
    without glusterd and other commands on a node, and all we need
    on that tie-breaker node is to run a single glusterfs command.
    Also note that, no other glusterfs installation needs
    thin-arbiter.so.
    
    Make sure RPM contains sample vol file, which can work by default,
    and a script to configure that volfile, along with translator image.
    
    Change-Id: Ibace758373d8a991b6a19b2ecc60c93b2f8fc489
    updates: bz#1674389
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit ac58cc27fb70461c76dac1187cb99bb59709e665
Author: Michael Scherer <misc@redhat.com>
Date:   Thu Mar 7 11:58:23 2019 +0100

    Remove Nigel as requested by him
    
    Change-Id: I0be4038790b56f67d75a61bb8b346d9b4e0d8cce
    updates: bz#1686371
    Signed-off-by: Michael Scherer <misc@redhat.com>

commit e9bfe11475c715e431d005087a0fa0fb66aef033
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Mar 5 08:39:16 2019 +0530

    dict: handle STR_OLD data type in xdr conversions
    
    Currently a dict conversion on wire for 3.x protocol happens using
    `dict_unserialize()`, which sets the type of data as STR_OLD. But the
    new protocol doesn't send it over the wire as its not considered as a
    valid format in new processes.
    
    But considering we deal with old and new protocol when we do a rolling
    upgrade, it will allow us to get all the information properly with new
    protocol.
    
    Credits: Krutika Dhananjay
    
    Fixes: bz#1684385
    Change-Id: I165c0021fb195b399790b9cf14a7416ae75ec84f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit a858dd1c310ee25b2fcd7aefc3a6caabe8560d4f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 7 08:00:47 2019 -0500

    packaging: remove unnecessary ldconfig in scriptlets
    
    see https://src.fedoraproject.org/rpms/glusterfs/pull-request/5
    
    Reported-By: Igor Gnatenko
    
    Change-Id: I914f36290e96a387cdd64ee633e75c2940ec1e56
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 2a0f905c905de4ad1e74bf4c7998adf087756785
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Feb 21 16:17:44 2019 +0530

    cluster/afr: Add quorum checks to open & opendir fops
    
    Problem:
    Currently even if open & opendir fails on quorum number of bricks,
    but succeeds on atleast one brick, it will result in success. This leads
    to inconsistency in the behaviour with other operations following the
    open, which has quorum checks.
    
    Fix:
    Add quorum checks to open & opendir fops to avoid inconsistency.
    
    Change-Id: If8fcb82072a6dc45ea6d4a6754b79763215eba2a
    fixes: bz#1634664
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 91f98e03ab654f212323d385bfc6fa3c0f2e4110
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Thu Mar 7 16:35:33 2019 +0530

    performance/readdir-ahead: fix deadlock
    
    This deadlock happens while processing dentry corresponding to current
    directory (.) in rda_fill_readdirp. In this case following order is
    followed:
    
    LOCK(directory_fd_ctx->lock);
      rda_inode_ctx_get_iatt -> LOCK(directory_inode->lock);
    
    However, in rda_mark_inode_dirty following lock order is followed:
    LOCK(directory_inode->lock);
      LOCK(directory_fd_ctx->lock);
    
    these two codepaths when executed concurrently resulted in a deadlock.
    
    Current patch fixes this by removing locking directory inode and
    fd-ctx in rda_fill_readdirp. This is fine as directory inode's stat
    won't change due to writes to files within directory.
    
    Change-Id: Ic93a67a0dac8229bb0d79582e526a512e6f2569c
    fixes: bz#1674412
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Fixes:bz#1674412

commit ab9b928873024bbc44c941d2ded1b7371f443dd6
Author: David Spisla <david.spisla@iternity.com>
Date:   Wed Mar 6 12:21:18 2019 +0100

    WORM-Xlator: Maybe integer overflow when computing new atime
    
    The structs worm_reten_state_t and read_only_priv_t from read-only.h are
    using uint64_t values to store periods of retention and autocommmit.
    This seems to be dangerous since in worm-helper.c the function
    worm_set_state computes in line 97:
    
    stbuf->ia_atime = time(NULL) + retention_state->ret_period;
    
    stbuf->ia_atime is using int64_t because of the settings of struct
    iattr. So if there is a very very high retention period stored, there
    is maybe an integer overflow.
    
    What can be the solution? Using int64_t instead if uint64_t may reduce
    the probability of the occurance.
    
    Change-Id: Id1e86c6b20edd53f171c4cfcb528804ba7881f65
    fixes: bz#1685944
    Signed-off-by: David Spisla <david.spisla@iternity.com>

commit 30c6e354b054879dcdadc726cdf5b9a38630f1bb
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Mar 4 10:11:15 2019 -0500

    packaging: s390x has RDMA support
    
    Since around fedora27, and in RHEL7 since July 2016.
    
    Reported-By: Dan Horák <dan@danny.cz>
    
    Change-Id: Idad29425495f9c69bfd84b53b009a607abb418f0
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 073444b693b7a91c42963512e0fdafb57ad46670
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Mar 4 16:53:01 2019 +0530

    core: make compute_cksum function op_version compatible
    
    Problem: commit 5a152a changed the mechansim of computing the
    checksum. In heterogeneous cluster, peers are running into
    rejected state because we have different cksum computation
    mechansims in upgraded and non-upgraded nodes.
    
    Solution: add a check for op-version so that all the nodes
    in the cluster follow the same mechanism for computing the
    cksum.
    
    Change-Id: I1508f000e8c9895588b6011b8b6cc0eda7102193
    fixes: bz#1685120
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 27f6375df009c8c4798b72aeafce79456007d21f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Mar 4 13:39:18 2019 +0530

    eventsapi: Fix error while handling GlusterCmdException
    
    `GlusterCmdException` was wrongly accessed instead of accessing
    `GlusterCmdException.message`.
    
    Fixes: bz#1685027
    Change-Id: I35ec1b05726050bfd8761e05ad9b9e47917dc0c6
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 6b99558be6872bb5ba5fe8133696ca856617b184
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Feb 27 23:15:58 2019 +0530

    leases: Do not process internal fops
    
    fops marked internal are used to maintain data integrity
    and ideally do not intervene with application client leases.
    Hence it seems safe to ignore them by lease xlator.
    
    Change-Id: I887b6f2da7ec0081442cc4b572a7a9e110f79eb2
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 9374484917466dff4688d96ff7faa0de1c804a6c
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Mar 5 13:39:46 2019 +0530

    glusterd: glusterd memory leak while running "gluster v profile" in a loop
    
    Problem: glusterd has memory leak while running "gluster v profile"
             in a loop
    
    Solution: Resolve leak code path to avoid leak
    
    Change-Id: Id608703ff6d0ad34ed8f921a5d25544e24cfadcd
    fixes: bz#1685414
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit f5c3b1727f55ffaa3dcdb3c3a09b968ebb45dbb2
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Feb 20 15:52:55 2019 +0530

    io-threads: Prioritize fops with NO_ROOT_SQUASH pid
    
    There was 30% regression observed in mkdir path with commit
    b139bc58eb504adf5ef81658896c9283ae21f390. On analysis it is found
    that io-threads xlator deprioritzes fops with all -ve pid.
    
    Some context in to the no-root-squash pid requirement:
    DHT xlator does some of the internal fops with root privileges. This is
    needed so that operations like layout healing should not be abandoned
    because a non root user is operating.  If root-squash option is enabled
    the layout set operation looses its root privilege as server xlator
    converts the uid and pid to random numbers. Hence, the above mentioned
    commit converted pid to GF_CLIENT_PID_NO_ROOT_SQUASH to continue fops
    as root.
    
    Combining the above I am proposing not to deprioritize fops with
    no-root-squash pid.
    
    Change-Id: I54d056c01b25729304a77f9242fbaff39c5672ba
    fixes: bz#1676430
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 82bedd01fd36d0b631367fab3e2cc4ca0b259378
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Feb 27 22:44:10 2019 +0530

    afr: mark changelog_fsync as internal
    
    As afr_changelog_fsync is used for internal operations, use
    GLUSTERFS_INTERNAL_FOP_KEY so that lease xlator can avoid treating
    it as conflicting fop and recall lease.
    
    Change-Id: I52cdc161002e840199d24439231a8bfa4f98b1b6
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit da10bbb060ca4dffc14f80ef67e34bd5ccd8cd6a
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Thu Feb 14 10:49:58 2019 +0000

    core: fix volume heal to avoid "invalid argument"
    
    This patch avoids printing of "invalid argument" unless
    loglevel is set to GF_LOG_DEBUG.
    
    fixes : bz#1654021
    
    Change-Id: I0e3d43bc627526f696b12921081342ca9b4a5f84
    fixes: bz#1654021
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 35ac5ae13fcf517cedc58005e258142c2e4620ab
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Feb 14 02:01:38 2019 +0100

    fuse lock interrupt: fix flock_interrupt.t
    
    updates: bz#1193929
    Change-Id: I347de62755100cd69e3cf341434767ae23fd1ba4
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 2b51b89f0f67ba1f7655cadb3fab9b4d3766faa6
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Fri Jan 18 11:00:56 2019 +0800

    quotad: fix passing GF_DATA_TYPE_STR_OLD dict data to v4 protocol
    
    quotad prints many logs as,
    
    [glusterfs3.h:752:dict_to_xdr] 0-dict: key 'trusted.glusterfs.quota.size' is not sent on wire [Invalid argument]
    [glusterfs3.h:752:dict_to_xdr] 0-dict: key 'volume-uuid' is not sent on wire [Invalid argument]
    
    For quota, there is a deamon named quotad which has a rpcsvc_program
    quotad_aggregator_prog that only supports v3 right now.
    
    Quotad has two actors (LOOKUP,GETLIMIT) that contains a dict in request,
    quotad just decodes the dict by dict_unserialize, those dict dates's type
    is GF_DATA_TYPE_STR_OLD, which type is not supported at glusterfs v4.
    
    Change-Id: Ib649d7a2e3c68c32dc26bc0f88923a0ba967ebd7
    Updates: bz#1596787
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 16b4936696c8b602243513fbde0b20a1e8417432
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Feb 27 13:38:33 2019 -0800

    mgmt/glusterd: Fix a memory leak when peer detach fails
    
    Dictionary object is not being unref'd when an error happens
    in __glusterd_handle_cli_deprobe(). This patch addresses that problem.
    
    Change-Id: I11e1f92d06dc9edd1260845256f435ea31ef1a87
    fixes: bz#1683816
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 2e9d3ab12df363ac5cdcbef693a5802c0066d7b4
Author: Arjun Sharma <arjsharm@redhat.com>
Date:   Thu Feb 21 18:09:50 2019 +0530

    Updating the glfs_setattr and glfs_fsetattr public APIs to use glfs_stat
    
    Change-Id: I0e86c8222c88b4c71087ec287ba81f8353d70822
    updates: #389
    Signed-off-by: Arjun <arjsharm@redhat.com>

commit 5cddd4d758014fe116d9c130632eada2ecded88c
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Feb 26 21:48:21 2019 +0530

    glusterd: remove experimental xlator options from glusterd-volume-set.c
    
    experimental xlators have been removed from the codebase. But we
    missed to remove the options related to experimental xlators from
    the codebase. This patch removes those options.
    
    fixes: bz#1683352
    Change-Id: I3fa7e14c6cd8ebde5cebc8d2b0cb2409bf37c1ae
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 30f358bb6b69b8c31da550608a4996a84e8b420b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Feb 25 12:32:21 2019 +0100

    build: do not install service related files when building --without-server
    
    It seems that glusterfs-6 disables building the server (./configure
    --without-server) on el6 and hence the installed but unpackaged files
    should not get installed in the first place.
    
    Change-Id: I7bea08202dd59ac309de8bc861da920ed3600bc6
    Fixes: bz#1680587
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 5feeed24f1e1fe2891e1418df23bacf0cfb991e6
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Feb 22 09:25:26 2019 -0500

    glusterfind: revert shebangs to #!/usr/bin/python3
    
    Using #!/usr/bin/env python is illegal in Fedora and RHEL packaging.
    (Debian and SUSE packaging will complain about it too but don't
    enforce it like Fedora packaging does. Yet.)
    
    We went through a giant exercise fixing these once already.
    
    The python needs to be python2/python3 clean. There is a build
    scriptlet that converts the shebangs back to /usr/bin/python on rhel7.
    
    Change-Id: If208a2557f7e5d727cda98c27905e249cf485d5b
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit fb4df03f3a9fd94a163265757a2c13bc8105476a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Feb 16 10:24:28 2019 +0200

    leases-internal.c: minor reduction of work under lock.
    
    Minor changes to reduce work done under a lock.
    Changed few CALLOC() to MALLOC(), and moved some
    time(NULL) outside the lock.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I4683d0d6e0b653a6adefff87b43ae717fd46843a

commit cd68f7b88b9a2c9a4e4ff9fca61517384e54130a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Feb 21 11:25:55 2019 +0530

    eventsapi: Fix Python3 compatibility issues
    
    - Fixed Relative import and non-package import related issues.
    - socketserver import issues fix
    - Renamed installed directory name to `gfevents` from `events`(To
      avoid any issues with other global libs)
    
    Fixes: bz#1679406
    Change-Id: I3dc38bc92b23387a6dfbcc0ab8283178235bf756
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit b2081cd8856a725c89c4d97b1399c589780b467a
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Feb 20 14:49:24 2019 +0530

    fuse : fix memory leak
    
    This patch fixes memory leak reported by ASan.
    
    Tracebacks:
    
    ERROR: LeakSanitizer: detected memory leaks
    
    Direct leak of 712 byte(s) in 1 object(s) allocated from:
        #0 0x7f35139dc848 in __interceptor_malloc (/lib64/libasan.so.5+0xef848)
        #1 0x7f35136efb29 in __gf_malloc ../libglusterfs/src/mem-pool.c:136
        #2 0x7f3510591ce9 in fuse_thread_proc ../xlators/mount/fuse/src/fuse-bridge.c:5929
        #3 0x7f351336d58d in start_thread (/lib64/libpthread.so.0+0x858d)
    
    SUMMARY: AddressSanitizer: 712 byte(s) leaked in 1 allocation(s).
    
    updates: bz#1633930
    Change-Id: Ie5b4da6b338d8e5fc770c5b2da1238e3462468ac
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 2236c8d3a1e9191d3505e6c1b14022a221aeeb7d
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Feb 21 10:51:13 2019 +0530

    geo-rep : fix incorrectly formatted authorized_keys
    
    Problem :  While Geo-rep setup when creating an ssh authorized_keys
               the geo-rep setup inserts an extra space before the "ssh-rsa" label.
               This gets flagged by an enterprise customer's security scan as a
               security violation.
    
    Solution: Remove extra space in GSYNCD_CMD & TAR_CMD.
    
    Change-Id: I956f938faef0e0883703bbc337b1dc2770e4a921
    fixes: bz#1679401
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit b235a56394c09bb1d7308a620053dbe098d15967
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Feb 22 15:17:48 2019 +0100

    build: include gluster/__init__.* files for python packaging
    
    The gluster/__init__.py file was originaly part of the glupy
    installation. This file is required to have the python-gluster package
    function correctly, it is expected to provide the 'gluster' namespace
    for other python packages (like from the libgfapi-python project).
    
    Because glupy does not exist anymore, this file is now added to in a new
    extras/python directory.
    
    Change-Id: I14fe959778ee3344d7d54ba342c7928a4d8080a2
    Fixes: c3fcff9ccbfcec1be242fd5cf210c9995586b078
    Fixes: 8293d21280fd6ddfc9bb54068cf87794fc6be207
    Updates: bz#1642810
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit d3608bd26cbc3e47fc0e60e85bd9f66515e050b1
Author: Sahina Bose <sabose@redhat.com>
Date:   Mon Feb 11 11:07:49 2019 +0530

    packaging: Obsoleting glusterfs-gnfs for upgrade
    
    fixes: bz#1672711
    Change-Id: Iad7194e788a8eeecd617614e9f8a1fe3264a384d
    Signed-off-by: Sahina Bose <sabose@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit fe67a230483eb3f379d65f166fd239086bd095a9
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Feb 19 14:07:43 2019 +0530

    glusterd: fix get-state leak
    
    Updates: bz#1193929
    Change-Id: I95897fd4d3102b4fa2b8b2864116b1bf24491cf9
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 15423e14f16dd1a15ee5e5cbbdbdd370e57ed59f
Author: David Spisla <david.spisla@iternity.com>
Date:   Tue Feb 19 14:56:11 2019 +0100

    md-cache: Adapt integer data types to avoid integer overflow
    
    The "struct iatt" in iatt.h is using int64_t types for storing
    the atime, mtime and ctime. Therefore the struct 'struct md_cache' in
    md-cache.c should also use this types to avoid an integer overflow.
    
    This can happen e.g. if someone uses a very high default-retention-period
    in the WORM-Xlator.
    
    Change-Id: I605268d300ab622b9c8ab30e459dc00d9340aad1
    fixes: bz#1678726
    Signed-off-by: David Spisla <david.spisla@iternity.com>

commit 09394856e1197db4933e7e814589a3340eb739cd
Author: hujianfei <hujianfei@cmss.chinamobile.com>
Date:   Fri Feb 15 04:07:46 2019 -0500

    glusterfsd: Do not process PROFILE_NFS_INFO if graph is not ready
    
    Otherwise, gnfs will crash in following situation.
    Also see commit 2f9e555f.
    
    Reproducible Steps:
    1. kill gnfs process
    2. service glusterd restart;gluster volume profile [vol] info nfs
    
    dump trace info:
    /lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0xc2)[0x7fcf5cb6a872]
    /lib64/libglusterfs.so.0(gf_print_trace+0x324)[0x7fcf5cb743a4]
    /lib64/libc.so.6(+0x35670)[0x7fcf5b1d5670]
    /usr/sbin/glusterfs(glusterfs_handle_nfs_profile+0x114)[0x7fcf5d066474]
    /lib64/libglusterfs.so.0(synctask_wrap+0x12)[0x7fcf5cba1502]
    /lib64/libc.so.6(+0x47110)[0x7fcf5b1e7110]
    
    Fixes: bz#1677559
    
    Change-Id: Id68edb3e4646c39544e0b4c90b5e0a9083b37b0d
    Signed-off-by: hujianfei <hujianfei@cmss.chinamobile.com>

commit 93e2576953316fdb37bb59b98bea755e799cc421
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Feb 14 08:53:58 2019 +0200

    upcall: some modifications to reduce work under lock
    
    1. Reduced the number of times we call time(). This may affect accuracy
    of access time and so on - please review carefully. I think the resolution is OK'ish.
    2. Removed dead code.
    3. Changed from CALLOC() to MALLOC() where it made sense.
    4. Moved some bits of work outside of a lock.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I9fb8ca5d79b0e9126c1eb07e1a1ab5dbd8bf3f79

commit 862e6409cb6929e1eb235a9156fbf6cbc4719236
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Feb 4 14:17:16 2019 +0530

    glusterd: adding a comment for code readability
    
    Adding a comment in the source code, so that anyone reading
    the code will understand the changes done by d4fa29 better.
    
    fixes: bz#1654270
    
    Change-Id: I75aff4243420c434c47d69a4b310f77bf161bb29
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 6175cb10cd5f59f3c7ae4100bc78f359b68ca3e9
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Tue Feb 19 08:04:52 2019 +0530

    performance/write-behind: handle call-stub leaks
    
    Change-Id: I7be9a5f48dcad1b136c479c58b1dca1e0488166d
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Fixes: bz#1674406

commit 64cc4458918e8c8bfdeb114da0a6501b2b98491a
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Wed Feb 13 17:08:14 2019 +0530

    performance/write-behind: fix use-after-free in readdirp
    
    Two issues were found:
    1. in wb_readdirp_cbk, inode should unrefed after wb_inode is
    unlocked. Otherwise, inode and hence the context wb_inode can be freed
    by the type we try to unlock wb_inode
    2. wb_readdirp_mark_end iterates over a list of wb_inodes of children
    of a directory. But inodes could've been freed and hence the list
    might be corrupted. To fix take a reference on inode before adding it
    to invalidate_list of parent.
    
    Change-Id: I911b0e0b2060f7f41ded0b05db11af6f9b7c09c5
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Updates: bz#1674406

commit eacc48b96b818ab2d15ed9d3a9a21818feed2826
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Jan 24 12:14:48 2019 +0530

    cli : fix mem leak during cli_cmd_volume_gsync_set_cbk
    
    This patch fixes mem-leak due to excessive use of gf_asprintf
    to form dynamic growing string.
    
    Problem: each call to asprintf/vsprintf for extending existing string causes
             a memory leak, because the blob at the original address of existing
             string is not freed and a new location is generated by asprintf.
    
    Tracebacks:
        #2 0x7fdf191b8b3b in gf_vasprintf ../libglusterfs/src/mem-pool.c:236
        #3 0x7fdf191b8d0a in gf_asprintf ../libglusterfs/src/mem-pool.c:256
        #4 0x420cd3 in cli_cmd_volume_gsync_set_cbk ../cli/src/cli-cmd-volume.c:2576
    
    SUMMARY: AddressSanitizer: 255 byte(s) leaked in 3 allocation(s).
    ....
    SUMMARY: AddressSanitizer: 431 byte(s) leaked in 4 allocation(s).
    ....
    SUMMARY: AddressSanitizer: 449 byte(s) leaked in 4 allocation(s).
    ....
    SUMMARY: AddressSanitizer: 397 byte(s) leaked in 4 allocation(s).
    ....
    SUMMARY: AddressSanitizer: 160 byte(s) leaked in 2 allocation(s).
    ....
    
    updates: bz#1633930
    Change-Id: I7e8902f0ed23e640dc17e3dcbdab7ae0579d2dc6
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 8acca65e72f7724d23c18f44693a269d95a664c5
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Feb 14 17:48:26 2019 +0530

    tests/dht:   Remove hardcoded brick paths
    
    The tests assumed that the file is created on a
    particular brick.This need not be the case
    in all scenarios and has been removed.
    
    Change-Id: Id420f43d7f72d983a7c6f16ea8fed273d46c4824
    updates: bz#1672480
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit dddcf52020004d98f688ebef968de51d76cbf9a6
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Jan 24 18:44:06 2019 +0100

    core: implement a global thread pool
    
    This patch implements a thread pool that is wait-free for adding jobs to
    the queue and uses a very small locked region to get jobs. This makes it
    possible to decrease contention drastically. It's based on wfcqueue
    structure provided by urcu library.
    
    It automatically enables more threads when load demands it, and stops
    them when not needed. There's a maximum number of threads that can be
    used. This value can be configured.
    
    Depending on the workload, the maximum number of threads plays an
    important role. So it needs to be configured for optimal performance.
    Currently the thread pool doesn't self adjust the maximum for the
    workload, so this configuration needs to be changed manually.
    
    For this reason, the global thread pool has been made optional, so that
    volumes can still use the thread pool provided by io-threads.
    
    To enable it for bricks, the following option needs to be set:
    
       config.global-threading = on
    
    This option has no effect if bricks are already running. A restart is
    required to activate it. It's recommended to also enable the following
    option when running bricks with the global thread pool:
    
       performance.iot-pass-through = on
    
    To enable it for a FUSE mount point, the option '--global-threading'
    must be added to the mount command. To change it, an umount and remount
    is needed. It's recommended to disable the following option when using
    global threading on a mount point:
    
       performance.client-io-threads = off
    
    To enable it for services managed by glusterd, glusterd needs to be
    started with option '--global-threading'. In this case all daemons, like
    self-heal, will be using the global thread pool.
    
    Currently it can only be enabled for bricks, FUSE mounts and glusterd
    services.
    
    The maximum number of threads for clients and bricks can be configured
    using the following options:
    
       config.client-threads
       config.brick-threads
    
    These options can be applied online and its effect is immediate most of
    the times. If one of them is set to 0, the maximum number of threads
    will be calcutated as #cores * 2.
    
    Some distributions use a very old userspace-rcu library (version 0.7)
    for this reason, some header files from version 0.10 have been copied
    into contrib/userspace-rcu and are used if the detected version is 0.7
    or older.
    
    An additional change has been made to io-threads to prevent that threads
    are started when iot-pass-through is set.
    
    Change-Id: I09d19e246b9e6d53c6247b29dfca6af6ee00a24b
    updates: #532
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit ec273a46820ba17f46488c082c65cd1aa6739be3
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Feb 12 11:17:37 2019 +0200

    auth-cache.c: minor reduction of work under lock.
    
    Minor change to reduce work done under a lock.
    Also, remove unused variable (unrelated to the above).
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I1dfb55823c3db7c638d8a34288423bd1faa37c32

commit 8e2e11ff0fbbd86ef7f3ed2dab30572c27bdfa83
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Feb 12 11:25:04 2019 +0200

    server.c: use dict_() funcs with key length.
    
    Changed to use the dict_() funcs which take the key length.
    This happens to also reduce work under the lock in one case as well.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I958fcc29e95286fe3c74178cae3f01a8b2db26f2

commit 776ba851c6ee6c265253d44cf1d6e4e3d4a21772
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Feb 15 14:20:07 2019 +0530

    socket: socket event handlers now return void
    
    Problem:
    Returning any value from socket event handlers to the event sub-system
    doesn't make sense since event sub-system cannot handle socket
    sub-system errors.
    
    Solution:
    Change return type of all socket event handlers to 'void'
    
    Change-Id: I70dc2c57f12b7ea2fae41120f71aa0d7fe0b2b6f
    Fixes: bz#1651246
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit fc133767e5ed705f246547cdfa5b7a2db5dcd53f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Feb 12 11:19:26 2019 +0200

    md-cache.c: minor reduction of work under lock.
    
    Take the time before taking the lock, not under lock.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I6cd05d8556a9bcc015e1be53f6ba46854e52a380

commit 86a9b5db918c05f2986837d6a00093755540e51e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 13 13:10:34 2019 +0530

    protocol/server: Use SERVER_REQ_SET_ERROR correctly for dicts
    
    Removed op_errno based SERVER_REQ_SET_ERROR() calls which was
    dead-code. xdr_to_dict() calls have this check which is used
    in 4.0 version of xdr-to-dict.
    
    fixes bz#1676797
    Change-Id: I6f56907c85576f1263a6ec04ed7e37f723b01ac3
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 6fbeb89e869a2a669698405c3d479052e090f4b7
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Feb 12 11:05:58 2019 +0200

    dht-shared.c: minor reduction of work under lock.
    
    Minor changes to reduce work done under a lock.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ia58adfb5125129e5d1f3bbf2202f38520fdbc29f

commit 2856e001b5a31887eb1b78e5b0932204f128f04b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Feb 11 14:03:50 2019 -0500

    storage/posix: print the actual file path
    
    posix converts incoming operations on files to operations on
    corresponding gfid handles. While this in itself is not a problem,
    logging of those gfid handles in place of actual file paths can
    create confusions during debugging. The best way would be to
    print both the actual file (recieved as an argument) for path
    based operations and the gfid handle associated with it.
    
    Change-Id: I408c36ca6456f2e3981b93151c19ef7f60085ad6
    fixes: bz#1675076
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit e2ccf87e5cc4da13833276282df544844f0cf1c2
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 13 14:56:17 2019 +0530

    Fix compilation for fops-sanity.c
    
    Without this patch the following error is seen:
    ....
    warning: implicit declaration of function ‘makedev’ [-Wimplicit-function-declaration]
         ret = mknod("cspecial", S_IFCHR | S_IRWXU | S_IRWXG, makedev(2, 3));
                                                              ^~~~~~~
    /usr/bin/ld: /tmp/ccIVwT46.o: in function `path_based_fops':
    /home/pk/workspace/gerrit-repo/tests/basic/fops-sanity.c:478:
    undefined reference to `makedev'
    ....
    
    updates bz#1676797
    Change-Id: I8a17c38fdfd458dd2dc75f4c7e2bf20ce555a042
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit e685e81fc5db25cd9cd7757fbede42b359e325cc
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Feb 13 16:00:27 2019 +0100

    docs: fix typo in Developer Guide Readme
    
    updates: bz#1193929
    Change-Id: I3e13e5a2d7347cf2a4e3717e93b5e97325e2de97
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 110006bbcd5bb3e814b4cfe7d74cb41891ac3b0c
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Feb 6 09:58:55 2019 +0530

    cluster/dht: Request linkto xattrs in dht_rmdir opendir
    
    If parallel-readdir is enabled, the rda xlator is loaded
    below dht in the graph and proactively lists and caches
    entries when an opendir is performed. dht_rmdir checks if
    the directory being deleted contains stale linkto files by
    performing a readdirp on its child subvols. However, as
    the entries are actually read in during the opendir operation
    which does not request the linkto xattr,no linkto xattrs are
    present for the entries causing dht to incorrectly identify
    them as data files and fail the rmdir operation with ENOTEMPTY.
    DHT now always adds the linkto xattr in the list of xattrs
    requested in the opendir.
    
    Change-Id: I0711198e66c59146282eb8b88084170bedfb4018
    fixes: bz#1672851
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit d6e7ad2911ba8ae246c3a3ec62f04a712beca517
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Tue Jan 8 16:38:45 2019 +0800

    dht: fix double extra unref of inode at heal path
    
    The loc_wipe is done in the _out_ section, inode_unref(loc.parent) here
    casues a double extra unref of loc.parent.
    
    Change-Id: I2dc809328d3d34bf7b02c7df9a4f97788af511e6
    updates: bz#1651439
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit b0f1d782fc45313fce4e1c0e74127401d5342d05
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Feb 12 13:58:54 2019 +0530

    cluster/dht: Fix lookup selfheal and rmdir race
    
    A race between the lookup selfheal and rmdir can cause
    directories to be healed only on non-hashed subvols.
    This can prevent the directory from being listed from
    the mount point and in turn causes rm -rf to fail with
    ENOTEMPTY.
    Fix: Update the layout information correctly and reduce
    the call count only after processing the response.
    
    Change-Id: I812779aaf3d7bcf24aab1cb158cb6ed50d212451
    fixes: bz#1676400
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 8a90d346b9d3f69ff11241feb0011c90a8e57e30
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Feb 9 13:23:06 2019 +0530

    inode: make critical section smaller
    
    do all the 'static' tasks outside of locked region.
    
    * hash_dentry() and hash_gfid() are now called outside locked region.
    * remove extra __dentry_hash exported in libglusterfs.sym
    * avoid checks in locked functions, if the check is done in calling
      function.
    * implement dentry_destroy(), which handles freeing of dentry separately,
      from that of dentry_unset (which takes care of separating dentry from
      inode, and table)
    
    Updates: bz#1670031
    Change-Id: I584213e0748464bb427fbdef3c4ab6615d7d5eb0
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit f251bf672dc8ce340c58d806a19cbd47e3a72ba9
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Feb 13 10:20:29 2019 +0530

    tests/dht: Stop volume before unmounting bricks
    
    The bricks are loopback devices. Unmounting them is done
    before the cleanup and leads to "target is busy" messages.
    
    Change-Id: Ia808c2c9580273e1bf0595ecf53c210847c44577
    fixes: bz#1676736
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 73d22d982b965f81a1fde2400b6d432242be0db5
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Feb 13 10:08:34 2019 +0530

    rfc.sh: fix the missing rebase issue
    
    When we decided to use clang-format for coding-style, and not bother
    about local `check-patch.pl`, we had commented out coding style check
    method in `./rfc.sh`.  While it was intended and valid, we missed to
    see one major issue with that. `git fetch` command, which fetched
    latest code of the project, was inside the check_patches method, which
    also got missed.
    
    Even though we had an explicit 'rebase_orgin' method, it did nothing
    because the git fetch was not done before this. Now, calling an explicit
    git fetch, and removing dead code of check patches, as we are all fine
    with coding-style changes in last 4+ months.
    
    updates: bz#1193929
    Change-Id: I3779096a527b93e780858ada8d988fdcdd6e2928
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 017721e5cad5b8a5b498a06e54098ea920d5bc96
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Jan 3 17:44:18 2019 +0530

    afr/shd: Cleanup self heal daemon resources during afr fini
    
    We were not properly cleaning self-heal daemon resources
    during afr fini. This patch will clean the same.
    
    Change-Id: I597860be6f781b195449e695d871b8667a418d5a
    updates: bz#1659708
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit cccf41f254c601c249d064315592941375570f88
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Tue Feb 12 09:11:34 2019 +0530

    performance/md-cache: change the op-version of "global-cache-invalidation"
    
    Since release-6 is not done yet, this option can be introduced with
    GD_OP_VERSION_6_0.
    
    Change-Id: I8a0867e5b8b23d0d485704a2fc7a3efc4a90f637
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    updates: bz#1664934

commit 34e6028e4ceaff5ceb1165317a3a90d02e0da4ac
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Jan 23 21:55:01 2019 +0530

    clnt/rpc: ref leak during disconnect.
    
    During disconnect cleanup, we are not cancelling reconnect
    timer, which causes a ref leak each time when a disconnect
    happen.
    
    Change-Id: I9d05d1f368d080e04836bf6a0bb018bf8f7b5b8a
    updates: bz#1659708
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit ecd1b4f700ea7a32cc4b46c633f88db7901ff320
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Feb 9 13:00:21 2019 +0530

    fuse: reflect the actual default for lru-limit option
    
    in both `--help` text and man page
    
    updates: bz#1193929
    Change-Id: I9aa9367c6863ac8e2403255280697c9e6be26cf0
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 2b5aa4489de2017a03bcb6ec8986286f0c76a670
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Fri Feb 8 09:51:17 2019 +0530

    performance/md-cache: introduce an option to control invalidation of inodes
    
    Explicit invalidation by calling inode_invalidate is necessary when
    same (meta)data is shared/access across multiple mounts. Without an
    explicit inode_invalidate call, caches in the mount which didn't
    witness writes wouldn't be aware of changes as writes wouldn't have
    passed through them. However, if (meta)data is not shared, all
    relevant I/O goes through the cache of single mount and hence is
    coherent with (meta)data on bricks always. So, explicit inode
    invalidation can be disabled for this case which gives a huge
    performance boost for workloads that write data and then immediately
    read the data they just wrote. Note that otherwise, local writes
    (which pass through the cache) will change ctime and cause unnecessary
    invalidations.
    
    The name of the option that controls this behavior is
    "performance.global-cache-invalidation". This option is global and it
    purges caches both in glusterfs and kernel stack for native FUSE
    mounts. For non-native FUSE mounts, it purges cache only from
    glusterfs stack. This option is effective only when
    performance.stat-prefetch is on.
    
    Note that there is a similar option "performance.cache-invalidation",
    but the scope of that option is limited to quick-read and md-cache.
    
    Change-Id: I462bb4b65ff9aae1f6ba76f50b1f2f94fb10323b
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    updates: bz#1664934

commit 59ce06a73f15897acf5c712ac5073650c1b505bf
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Feb 9 13:13:47 2019 +0530

    inode: create inode outside locked region
    
    Only linking of inode to the table, and inserting it in
    a list needs to be in locked region.
    
    Updates: bz#1670031
    Change-Id: I6ea7e956b80cf2765c2233d761909c4bf9c7253c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 261147620a43aa415b7e8f11d51a89557846b1c4
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Fri Feb 8 17:39:49 2019 +0530

    mount/fuse: fix bug related to --auto-invalidation in mount script
    
    When "auto-invalidation" option was not specified for mount script,
    glusterfs cmdline ended with "--auto-invalidation=" option. This patch
    fixes that bug in mount script.
    
    Thanks to Amar for reporting it.
    
    Change-Id: Ie5cd4c6ffb3ac644d9d2b032035f914a935d05a8
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    updates: bz#1664934

commit 12af2067a82e37079e76723d3e25ba1c72ca078a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 7 14:45:39 2019 +0530

    glusterd: improve logging
    
    glusterd_resolve_all_bricks failure log should highlight the brick
    identifier.
    
    Updates: bz#1193929
    Change-Id: I035b4650ef6a14bb1e1221d3bad1c40f9d43dbdd
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit ddcb3c7438472072daa6fbe3f3b87067b6d7bc54
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Feb 5 20:44:28 2019 -0500

    api: Update all future API versions to rel-6
    
    As release 6 is branched, all future APIs now become 6.0
    
    This change implements the same.
    
    Change-Id: I6db368b4dc8585278ec11d4a411adcd04635de53
    Updates: bz#1193929
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 539c3027d47959eb37e280807b731d3e37e8ac33
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue Feb 5 16:57:52 2019 +0100

    fuse: correctly handle setxattr values
    
    The setxattr function receives a pointer to raw data, which may not be
    null-terminated. When this data needs to be interpreted as a string, an
    explicit null termination needs to be added before using the value.
    
    Change-Id: Id110f9b215b22786da5782adec9449ce38d0d563
    updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 208c368cc7e6f8124bf65ecefdbc5f4304b4f484
Author: Nigel Babu <nigelb@redhat.com>
Date:   Mon Jan 21 12:17:04 2019 +0530

    Bump up timeout for tests on AWS
    
    Fixes: bz#1672727
    Change-Id: I2b9be45f199f6436b858536c6f49be85902217f0
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit bdb8d7b9f6e2c53db5de43a6b4c8f8c2ab3f6d69
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Feb 5 20:14:07 2019 -0500

    glusterd: Update op-version for release 7
    
    Change-Id: I0f3978d7e603e6e767dc7aa2a23ef35b1f2b43f7
    Updates: bz#1193929
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 90922d20f55e26b23bfab0fbc4e179e305c38037
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Feb 4 15:07:14 2019 +0530

    glusterd: get-state command should not fail if any brick is gone bad
    
    Problem: get-state command will error out, if any of the underlying
    brick(s) of volume(s) in the cluster go bad.
    
    It is expected that get-state command should not error out, but
    should generate an output successfully.
    
    Solution: In glusterd_get_state(), a statfs call is made on the
    brick path for every bricks of the volumes to calculate the total
    and free memory available. If any of statfs call fails on any
    brick, we should not error out and should report total memory and free
    memory of that brick as 0.
    
    This patch also handles a statfs failure scenario in
    glusterd_store_retrieve_bricks().
    
    fixes: bz#1672205
    
    Change-Id: Ia9e8a1d8843b65949d72fd6809bd21d39b31ad83
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit a9b51f2d1fd3a8be6496b62b989b6838b542936b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Feb 1 12:24:14 2019 +0530

    geo-rep: Fix configparser import issue
    
    'configparser' is backported to python2 and can
    be installed using pip (pip install configparser).
    So trying to import 'configparser' first and later
    'ConfigParser' can cause issues w.r.t unicode strings.
    
    Always try importing 'ConfigParser' first and then
    'configparser'. This solves python2/python3 compat
    issues.
    
    Change-Id: I2a87c3fc46476296b8cb547338f35723518751cc
    fixes: bz#1671637
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit f87a3e840306052a120529ea5a190240179078c1
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Mon Jan 21 11:16:09 2019 +0000

    cli: Added the group option for volume set
    
    gluster volume set <VOLUME> group <GROUP> is used for setting multiple
    pre-defined volume options, but this was undocumented. This patch doc-
    ments this feature.
    
    fixes: bz#1243991
    
    Change-Id: Id346cf2537f85179caff32479f09555ce2e72e76
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit ec05f3a21f44e1fd5e089b7a0fffd5265b67cdfc
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Dec 17 14:16:21 2018 +0530

    glusterd: manage upgrade to current master
    
    Scenarios tested:
    
    * Upgrade the node when there are stripe / tiering and regular
    type of volumes are present.
      - All volumes are started fine (as the change was not on brick volfile)
      - For tier, the functionality may not even work, as changetimerecorder
        is not present.
      - 'gluster volume info' properly shows as 'NOT SUPPORTED' for stripe and
        tier type of volume.
    
    * Upgrade in a rolling upgrade scenario, where an old version is
    able to connect to higher master.
      - on a normal volume, if the volfile-server was new, the newer client
        volfiles needed to have utime xlator conditionally.
      - with this one change, all other changes seem to work fine.
    
    Change-Id: Ib2d3b69dafa02b2c695a735b13c1aa70aba07cb8
    updates: bz#1635688
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit da5ae3afcd1b16bb0f2f9bffc1878b17b75429ed
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jan 29 09:47:32 2019 +0530

    cluster/dht: Do not use gfid-req in fresh lookup
    
    Fuse sets a random gfid-req value for a fresh lookup. Posix
    lookup will set this gfid on entries with missing gfids causing
    a GFID mismatch for directories.
    DHT will now ignore the Fuse provided gfid-req and use the GFID
    returned from other subvols to heal the missing gfid.
    
    Change-Id: I5f541978808f246ba4542564251e341ec490db14
    fixes: bz#1670259
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 23e530a135fc419fba401448290f8b1809e23f53
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Mon Dec 10 13:45:34 2018 +0530

    glusterfind: python2 to python3 compat
    
    Made necessary modifications to ensure python3 compatibilty.
    
    fixes: bz#1658116
    Change-Id: I5cf1d0447eaf3c44eb444245d1f67aadd60705c3
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit a229ee1c8cdf8e0ac1abaeb60cabe6ab08f60546
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Tue Jan 29 08:05:07 2019 +0530

    mount/fuse: expose auto-invalidation as a mount option
    
    Auto invalidation is necessary when same (meta)data is shared/access
    across multiple mounts. However, if (meta)data is not shared, all
    relevant I/O goes through the cache of single mount and hence is
    coherent with (meta)data on bricks always. So, fuse-auto-invalidation
    can be disabled for this case which gives a huge performance boost for
    workloads that write data and then immediately read the data they just
    wrote.
    
    From glusterfs --help,
    
    <snip>
          --auto-invalidation[=BOOL]   controls whether fuse-kernel can
                                 auto-invalidate attribute, dentry and page-cache.
                                 Disable this only if same files/directories are
                                 not accessed across two different mounts
                                 concurrently [default: "on"]
    </snip>
    
    Details on how disabling auto-invalidation helped to reduce pgbench
    init times can be found at [1]. Time taken for pgbench init of scale
    8000 was 8340s. That will be an improvement of 86% (59280s vs 8340s)
    with auto-invalidations turned off along with other
    optimizations. Just disabling auto-invalidation contributed 56%
    improvement by reducing the total time taken by 33260s.
    
    [1] https://www.spinics.net/lists/gluster-devel/msg25907.html
    
    Change-Id: I0ed730dba9064bd9c576ad1800170a21e100e1ce
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    updates: bz#1664934

commit 4674678951a1315975d66016fb55c49100b7819f
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Jan 24 18:31:10 2019 +0100

    core: make gf_thread_create() easier to use
    
    This patch creates a specific function to set the thread name using a
    string format and a variable argument list, like printf().
    
    This function is used to set the thread name from gf_thread_create(),
    which now accepts a variable argument list to create the full name. It's
    not necessary anymore to use a local array to build the name of the
    thread. This is done automatically.
    
    Change-Id: Idd8d01fd462c227359b96e98699f8c6d962dc17c
    Updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 6b98735956c599ea621fa560b201fb7de6c36cac
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Dec 21 14:31:15 2018 +0530

    cluster/thin-arbiter: Consider thin-arbiter before marking new entry changelog
    
    If a fop to create an entry fails on one of the data brick,
    we mark the pending changelog on the entry on brick for which
    it was successful. This is done as part of post op phase to
    make sure that entry gets healed even if it gets renamed to
    some other path where its parent was not marked as bad.
    
    As it happens as part of post op, we should consider thin-arbiter
    to check if the brick, which was successful, is the good brick or not.
    This will avoide split brain and other issues.
    
    Change-Id: I12686675be98f02f70a5186b3ed748c541514d53
    updates: bz#1662264
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 7eda6fe62d4e47937afc2ba71b4fd858399bca05
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jan 28 11:55:17 2019 +0530

    cluster/dht: Remove internal permission bits
    
    Rebalance sets the sgid and t bits on a file
    that is being migrated. These permissions are
    not removed in dht_readdirp_cbk when listing files
    causing them to show up on the mountpoint.
    We now remove these permissions if a non-linkto
    file has the linkto xattr set.
    
    Change-Id: I5c69b2ecfe2df804fe50faea903b242d01729596
    fixes: bz#1669937
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 62a61c548d85d8c894907d7c43ef66c009a4757d
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Jan 31 11:30:27 2019 +0530

    core: move "dict is NULL" logs to DEBUG log level
    
    Too many logs get printed if dict_ref() and dict_unref() are passed NULL
    pointer.
    
    fixes: bz#1671213
    Change-Id: I18afd849d64318f68baa7b549ee310dac0e1e786
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 2fb445babdd621b71676e40804fe98e95fc9084d
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Jan 31 08:13:58 2019 +0100

    syncop: remove unnecessary call to gf_backtrace_save()
    
    A call to gf_backtrace_save() was done on each context switch of a
    synctask. The backtrace is generated writing to the filesystem, so it
    can have an important impact on latency.
    
    The generated backtrace was not used anywhere, so it's been removed.
    
    Change-Id: I399a93b932c5b6e981c696c72c3e1ef44710ba52
    Updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 8bc33a2d90df6439e7636aadbefdd9041f9698c3
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Sat Sep 29 13:15:35 2018 +0530

    feature/bitrot: Avoid thread creation if xlator is not enabled
    
    Problem: Avoid thread creation for bitrot-stub
             for a volume if feature is not enabled
    
    Solution: Before thread creation check the flag if feature
              is enabled
    
    Updates: #475
    Change-Id: I2c6cc35bba142d4b418cc986ada588e558512c8e
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit b41cdeb638f9f9ec2fef13ec95c216faf52a9df9
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jan 28 21:28:45 2019 +0530

    core: heketi-cli is throwing error "target is busy"
    
    Problem: When rpc-transport-disconnect happens, server_connection_cleanup_flush_cbk()
             is supposed to call rpc_transport_unref() after open-files on
             that transport are flushed per transport.But open-fd-count is
             maintained in bound_xl->fd_count, which can be incremented/decremented
             cumulatively in server_connection_cleanup() by all transport
             disconnect paths. So instead of rpc_transport_unref() happening
             per transport, it ends up doing it only once after all the files
             on all the transports for the brick are flushed leading to
             rpc-leaks.
    
    Solution: To avoid races maintain fd_cnt at client instead of maintaining
              on brick
    
    Credits: Pranith Kumar Karampuri
    Change-Id: I6e8ea37a61f82d9aefb227c5b3ab57a7a36850e6
    fixes: bz#1668190
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 09db11b0c020bc79d493c6d7e7ea4f3beb000c68
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Jan 29 11:51:16 2019 +0530

    readdir-ahead: do not zero-out iatt in fop cbk
    
    ...when ctime is zero. ia_type and ia_gfid always need to be non-zero
    for things to work correctly.
    
    Problem:
    Commit c9bde3021202f1d5c5a2d19ac05a510fc1f788ac zeroed out the iatt
    buffer in the cbks of modification fops before unwinding if the ctime in
    the buffer was zero. This was causing the fops to fail: noticeable when
    AFR's 'consistent-metadata' option was enabled. (AFR zeros out the ctime
    when the option is set. See commit
    4c4624c9bad2edf27128cb122c64f15d7d63bbc8).
    
    Fixes:
    -Do not zero out the ia_type and ia_gfid of the iatt buff under any
    circumstance.
    -Also, fixed _rda_inode_ctx_update_iatts() to always update these values from
    the incoming buf when ctime is zero. Otherwise we end up with zero
    ia_type and ia_gfid the first time the function is called *and* the
    incoming buf has ctime set to zero.
    
    fixes: bz#1670253
    Reported-By:Michael Hanselmann <public@hansmi.ch>
    Change-Id: Ib72228892d42c3513c19fc6dfb543f2aa3489eca
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 4aee035cd2a32750326b83b5fe08af7c8abab284
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jan 29 03:16:16 2019 -0500

    api: bad GFAPI_4.1.6 block
    
    missing global: line, tabs not spaces
    
    Change-Id: Icdbc23b4e4cd608da1d764e81757201c4b1269a6
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 829337ed3971a53086f1562d826e79d4f3e3ed39
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jan 28 18:30:24 2019 +0530

    features/sdfs: disable by default
    
    With the feature enabled, some of the performance testing results,
    specially those which create millions of small files, got approximately
    4x regression compared to version before enabling this.
    
    On master without this patch:  765 creates/sec
    On master with this patch   : 3380 creates/sec
    
    Also there seems to be regression caused by this in 'ls -l' workload.
    
    On master without this patch:  3030 files/sec
    On master with this patch   : 16610 files/sec
    
    This is a feature added to handle multiple clients parallely operating
    (specially those which race for file creates with same name) on a single
    namespace/directory. Considering that is < 3% of Gluster's usecase right
    now, it makes sense to disable the feature by default, so we don't
    penalize the default users who doesn't bother about this usecase.
    Also note that the client side translators, specially, distribute,
    replicate and disperse already handle the issue upto 99.5% of the cases
    without SDFS, so it makes sense to keep the feature disabled by default.
    
    Credits: Shyamsunder <srangana@redhat.com> for running the tests and
    getting the numbers.
    
    Change-Id: Iec49ce1d82e621e9db25eb633fcb1d932e74f4fc
    Updates: bz#1670031
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c7d1aee76d5713d1f337ab1c831c0ed74e4676e1
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Dec 27 18:56:16 2018 +0200

    Multiple files: reduce work while under lock.
    
    Mostly, unlock before logging.
    In some cases, moved different code that was not needed
    to be under lock (for example, taking time, or malloc'ing)
    to be executed before taking the lock.
    
    Note: logging might be slightly less accurate in order, since it may
    not be done now under the lock, so order of logs is racy. I think
    it's a reasonable compromise.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I2438710016afc9f4f62a176ef1a0d3ed793b4f89

commit f747d55a7fd364e2b9a74fe40360ab3cb7b11537
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Tue Jan 8 16:17:06 2019 +0800

    socket: fix issue on concurrent handle of a socket
    
    Found an issue on concurrent invoke of event handler to the same socket
    fd, causing memory corruption. This issue arises after applying commit
    "socket: Remove redundant in_lock in incoming message handling" that
    removes priv->in_lock to serialize socket read.
    
    The following call sequence describes how concurrent socket event handle
    happens.
       thread 1                    thread 2                thread 3
    epoll_wait() return
    (slot->in_handler is 0)  call select_on_epoll()
                             and epoll_ctl() on fd
                                                        epoll_wait() return
    slot->in_handler++
    (slot->in_handler is 1)
                                                        slot->in_handler++
                                                        (slot->in_handler is 2)
    call handler()                                      call handler()
    
    Fix this issue by skip invoke of handler if there is already a handler
    inprogress.
    
    Change-Id: I437126ac772debcadb00993a948919c931cd607b
    updates: bz#1467614
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 72922c1fd69191b220f79905a23395c3a87f86ce
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jan 24 14:14:39 2019 +0530

    features/shard: Ref shard inode while adding to fsync list
    
    PROBLEM:
    
    Lot of the earlier changes in the management of shards in lru, fsync
    lists assumed that if a given shard exists in fsync list, it must be
    part of lru list as well. This was found to be not true.
    
    Consider this - a file is FALLOCATE'd to a size which would make the
    number of participant shards to be greater than the lru list size.
    In this case, some of the resolved shards that are to participate in
    this fop will be evicted from lru list to give way to the rest of the
    shards. And once FALLOCATE completes, these shards are added to fsync
    list but without a ref. After the fop completes, these shard inodes
    are unref'd and destroyed while their inode ctxs are still part of
    fsync list. Now when an FSYNC is called on the base file and the
    fsync-list traversed, the client crashes due to illegal memory access.
    
    FIX:
    
    Hold a ref on the shard inode when adding to fsync list as well.
    And unref under following conditions:
    1. when the shard is evicted from lru list
    2. when the base file is fsync'd
    3. when the shards are deleted.
    
    Change-Id: Iab460667d091b8388322f59b6cb27ce69299b1b2
    fixes: bz#1669077
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 99b3ab0cf3d3389a2ff89c29cfff906cd36693a3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jan 11 11:57:07 2019 +0530

    tests: run nfs tests only if --enable-gnfs is provided
    
    Fixes: bz#1665358
    Change-Id: Idbf88ec3ac683733b32c313377eeb72f2819bf0d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 06061aaa447f03e2522483d02525619ebc9854db
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jan 24 12:14:11 2019 +0530

    afr/self-heal:Fix wrong type checking
    
    gf_dirent struct has d_type variable which should check
    with DT_DIR istead of IA_IFDIR or IA_IFDIR has to compare
    with entry->d_stat.ia_type
    
    Change-Id: Idf1059ce2a590734bc5b6adaad73604d9a708804
    updates: bz#1653359
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 04f84756e1baa5eff4560339700f82970eaa5d80
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Jan 22 12:57:50 2019 +0530

    core: heketi-cli is throwing error "target is busy"
    
    Problem: At the time of deleting block hosting volume
             through heketi-cli , it is throwing an error "target is busy".
             cli is throwing an error because brick is not detached successfully
             and brick is not detached due to race condition to cleanp xprt
             associated with detached brick
    
    Solution: To avoid xprt specifc race condition introduce an atomic flag
              on rpc_transport
    
    Change-Id: Id4ff1fe8375a63be71fb3343f455190a1b8bb6d4
    fixes: bz#1668190
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 9de432847cd699457623de84f76f7598aecd61e3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jan 22 13:30:34 2019 +0530

    tests/bug-brick-mux-restart: add extra information
    
    so that we can understand more about process memory and thread consumptions
    With this, we will also be able to understand more about the process details
    with brick-mux.
    
    updates: bz#1193929
    Change-Id: I147a3e3814fc37dfb635217d0a0f0184fae0994f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 990d6a99d41111ea18481db55566a96c2fc4dad4
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jan 16 20:24:06 2019 +0530

    core: move logs which are only developer relevant to DEBUG level
    
    We had only changed the log level to DEBUG in release branch earlier.
    But considering 90%+ of our deployments happen in same env, we can look
    at these specific logs on need basis. With this change, the master
    branch will be easier to debug with lesser logs.
    
    Change-Id: I4157a7ec7d5ec9c2948b2bbc1e4cb8317f28d6b8
    Updates: bz#1666833
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit cf12a446f86169d0954e68dad36a7763cb178a0e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Jan 21 17:01:33 2019 +0530

    performance/readdir-ahead: Fix deadlock in readdir ahead.
    
    This patch fixes a lock contention in reaadir-ahead xlator.
    
    There are two issues, one is the processing of "." ".."
    entry while holding an fd_ctx lock. The other one is destroying
    the stack inside a fd_ctx lock.
    
    Change-Id: Id0bf83a3d9fea6b40015b8d167525c59c6cfa25e
    updates: bz#1659708
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit d193ed84ae2886d89b899e02e9642e61bdab462a
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Mon Dec 31 10:55:21 2018 +0530

    tools/glusterfind: option to display only files/directories
    
    Updated full find to filter for files and directories.
    --full --type f  lists only the files,
    --full --type d lists only the directories,
    --full (by default) lists both files and directories.
    
    fixes: #579
    Change-Id: If2c91a21a131667d5de34635c1846013e8fa20b7
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 86d4eac6c6f2d774a579ef134f6526f75504c46e
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Jan 22 18:01:40 2019 +0530

    posix: Change data type to dump nr_files to statedump
    
    Problem: In commit 2261e444a47ffffb5d64305efceee1d5a734cd75
             wrong data type of nr_files was changed to dump
             nr_files to statedump so build is failing on 32bit
             environment
    
    Solution: Change data type to avoid errors
    
    Change-Id: Ifb4b19feda6e0e56d110b23351e7a0efd5bfa29b
    fixes: bz#1657607
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 832f60d41d9a392e77e5b81e7a44a97003b7541f
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jan 22 16:07:52 2019 +0530

    rpc: Fix double free
    
    The value rsp.xdata.xdata_val was being freed twice. It was assigned
    to dict->extra_stdfree, dict_destroy would free it and also there was
    an explicit free. Getting rid of explicit free in this patch.
    
    Change-Id: Ia9c73454bec3970b33f154fa754398bf3b045645
    fixes: bz#1668268
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit b6c417785e54620331ae35d6971fe8bef98b4619
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Jan 22 12:10:59 2019 +0530

    rpc: use address-family option from vol file
    
    This patch helps enable IPv6 connections in the cluster.
    The default address-family is IPv4 without using this option explicitly.
    
    When address-family is set to "inet6" in the /etc/glusterfs/glusterd.vol
    file, the mount command-line also needs to have
    -o xlator-option="transport.address-family=inet6" added to it.
    
    This option also gets added to the brick command-line.
    Snapshot and gfapi use-cases should also use this option to pass in the
    inet6 address-family.
    
    Change-Id: I97db91021af27bacb6d7578e33ea4817f66d7270
    fixes: bz#1635863
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 67bc3775685198b9ab10c1f2a0d957b157bb4acd
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Fri Nov 30 17:23:57 2018 +0530

    afr: not resolve splitbrains when copies are of same size
    
    Automatic Splitbrain with size as policy must
    not resolve splitbrains when the copies are of same size.
    Determining if the sizes of copies are same and
    returning -1 in that case.
    
    updates: bz#1655052
    
    Change-Id: I3d8e8b4d7962b070ed16c3ee02a1e5a926fd5eab
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit cd5714554627fe90ee2c77685cb410a8fb25eceb
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Thu Jan 3 17:57:38 2019 +0800

    socket: don't pass return value from protocol handler to event handler
    
    Event handler handles socket level error only, while protocol handler
    handles in protocol level error. If protocol handler decides to
    disconnect on error in any case, it should call disconnect instead of
    return an error back to event handler.
    
    Change-Id: I9375be98cc52cb969085333f3c7229a91207d1bd
    updates: bz#1666143
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 4d9935a4db67be0237db5fc6a2b51086635571f6
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Sat Dec 29 16:26:58 2018 +0800

    socket: fix issue when socket read return with EAGAIN
    
    In the case socket read returns EAGAIN, positive value about remaining
    vector to send is returned. This return value will be passed all the way
    back to event handler, making it complains.
    
    [2018-12-29 08:02:25.603199] T [socket.c:1640:__socket_read_simple_payload] 0-test-client-0-extra.0: partial read on non-blocking socket.
    [2018-12-29 08:02:25.603201] T [rpc-clnt.c:654:rpc_clnt_reply_init] 0-test-client-2-extra.1: received rpc message (RPC XID: 0xfa6 Program: GlusterFS 4.x v1, ProgVers: 400, Proc: 12) from rpc-transport (test-client-2-extra.1)
    [2018-12-29 08:02:25.603207] T [socket.c:3129:socket_event_handler] 0-test-client-0-extra.0: (sock:32) socket_event_poll_in returned 1
    
    Formerly, in socket_proto_state_machine, return value of socket_readv is
    used to check if message is all read-in. In this commit, it is checked
    whether size of bytes indicated in header are all read in. In this way,
    only 0 and -1 will be returned from socket_proto_state_machine(),
    indicating whether there is error in the underlying socket.
    
    Change-Id: I8be0d178b049f0720d738a03aec41c4b375d2972
    updates: bz#1666143
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 3c556353cd1dde0593096c9e9e11b877403971f0
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Jan 18 17:26:36 2019 +0530

    locks/fencing: Add a security knob for fencing
    
    There is a low level security issue with fencing since one client
    can preempt another client's lock.
    
    This patch does not completely eliminate the issue of a client
    misbehaving, but certainly it adds a security layer for default use cases
    that does not need fencing.
    
    Change-Id: I55cd15f2ed1ae0f2556e3d27a2ef4bc10fdada1c
    updates: #466
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 4f58d35f064e5fba3a02b7be8b2525ebe2114254
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jan 21 15:15:51 2019 +0530

    cluster/dht: Delete invalid linkto files in rmdir
    
    rm -rf <dir> fails on dirs which contain linkto files
    that point to themselves because dht incorrectly thought
    that they were cached files after looking them up.
    The fix now treats them as invalid linkto files
    and deletes them.
    
    Change-Id: I376c72a5309714ee339c74485e02cfb4e29be643
    fixes: bz#1667804
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 4deeab02e3d15bd266f24d0f7b28f0e5401fa950
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jan 21 17:53:12 2019 +0530

    glusterd: Avoid dict_leak in __glusterd_handle_cli_uuid_get function
    
    Change-Id: Iefe08b136044495f6fa2b092c9e8c833efee1400
    fixes: bz#1667905
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 2a8a66d58ad7ad28d32de42bd3423d7aa3917e3b
Author: Xiubo Li <xiubli@redhat.com>
Date:   Sun Jan 13 17:30:11 2019 +0800

    common-utils: make vector a const parameter
    
    To avoid the warning and preparing for adding writesame support.
    
    Updates: #617
    Change-Id: I0710b1e4c240368a9bf52968bddc6e250ae2028d
    Signed-off-by: Xiubo Li <xiubli@redhat.com>

commit 5903111ad21cb937258c0fda24ea7dec466347b4
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jan 21 09:12:30 2019 +0530

    glusterd: Resolve memory leak in get-state command
    
    In gluster get-state volumeoptions command there was some amount of leak
    observed. This fix resolves the identified leaks.
    
    Change-Id: Ibde5743d1136fa72c531d48bb1b0b5da0c0b82a1
    fixes: bz#1667779
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 11aaecccad03d5803dc7be63c3e36af75da8126d
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Mon Jan 7 15:19:18 2019 +0530

    posix: fix coverity issue
    
    Logically dead code
    
    CID: 1398468
    Updates: bz#789278
    
    Change-Id: I8713a0c51777eb64e617d00ab72fd1db4994b6ab
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit cd16967a77d04a8d0c5d5c3ab5346ccdd1df89cb
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Fri Nov 30 19:49:59 2018 +0530

    afr: Splitbrain with size as policy must not resolve for directory
    
    In automatic Splitbrain resolution when favorite child policy
    is set as size, split brain resolution must not work for
    directories.
    
    Currently, if a directory is in split brain with both copies
    having same size, the source is selected arbitrarily
    and healed.
    
    fixes: bz#1655050
    Change-Id: I5739498639c17c89874cc577362e543adab55f5d
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 55b40dfbb2551b1507d532a03bdf199acb37bf6a
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Mon Jan 14 13:24:20 2019 +0000

    cli: Added a welcome and help message
    
    When gluster command is fired without any arguments it just shows the
    prompt, so added a welcome message and info to get help.
    
    fixes: bz#1535528
    
    Change-Id: I627b66b67443716e9270025c1e47b98b6facba13
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit c5bb929b367121f2610f74630882254da7fd882a
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Fri Jan 18 10:38:14 2019 +0800

    quotad: fix wrong memory free
    
    1. cli_req.dict.dict_val,
       It must be freed no metter operation error or success.
       Fix it as lookup "alloca" memory before decode.
    
    2. args.xdata.xdata_val,
       It is allocated by "alloca", free is unneeded.
    
    3. qd_nameless_lookup,
       It olny needs gfid, a gfs3_lookup_req argument is unneeded.
    
    Change-Id: I746dddf7f3d1465b1885af2644afe0bcf0a5665b
    fixes: bz#1656682
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 0687b0beb5cc58d5aac9e203f0feebcd7e9eea03
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Tue Jan 1 21:06:05 2019 +0530

    core: Feature added to accept CidrIp in auth.allow
    
    Added functionality to gluster volume set auth.allow command to
    accept CIDR IP addresses. Modified few functions to isolate cidr
    feature so that it prevents other gluster commands such as peer
    probe to use cidr format ip. The functions are modified in such
    a way that they have an option to enable accepting of cidr
    format for other gluster commands if required in furture.
    
    updates: bz#1138841
    
    Change-Id: Ie6734002a7078f1820e5df42d404411cce945e8b
    Credits: Mohit Agrawal
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit ebaf09a2a329517936232510e117debc3795e80b
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Nov 30 15:04:17 2018 +0530

    lock: Add fencing support
    
    design reference: https://review.gluster.org/#/c/glusterfs-specs/+/21925/
    
    This patch adds the lock preempt support.
    
    Note: The current model stores lock enforcement information as separate
    xattr on disk. There is another effort going in parallel to store this
    in stat(x) of the file. This patch is self sufficient to add fencing
    support. Based on the availability of the stat(x) support either I will
    rebase this patch or we can modify the necessary bits post merging this
    patch.
    
    Change-Id: If4a42f3e0afaee1f66cdb0360ad4e0c005b5b017
    updates: #466
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 11cf73bc4173c13a9de54ea8d816eb72d8b01f48
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Jan 14 11:48:55 2019 +0530

    geo-rep : fix rename sync on hybrid crawl
    
    Problem: When geo-rep is configured as hybrid crawl
             directory renames are not synced to the slave.
    
    Solution: Rename sync of directory was failing due to incorrect
              destination path calculation.
              During check for existence on slave we miscalculated
              realpath. <host:brickpath/dir>.
    
    Change-Id: I23f1ea60e86a917598fe869d5d24f8da654d8a0a
    fixes: bz#1665826
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 0301a66bda44582e3a48519f2a5d365b0c38090d
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Sat Dec 29 15:51:13 2018 +0800

    socket: fix issue when socket write return with EAGAIN
    
    In the case socket write return with EAGAIN, the remaining vector count
    is return all way back to event handler, making followup pollin event to
    skip handling and dispatch loop complains about failure. Even thought
    temporary write failure is not an error.
    
    [2018-12-29 07:31:41.772310] E [MSGID: 101191] [event-epoll.c:674:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler
    
    Change-Id: Idf03d120b5f7619eda19720a583cbcc3e7da2504
    updates: bz#1666143
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 22778ca88977fa061c468ca257aec74d4e7d09f4
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Thu Dec 27 14:13:48 2018 +0800

    socket: fix counting of socket total_bytes_read and total_bytes_write
    
    Change-Id: If35d0dbae963facf00ab6bcf07c6e4d1706ed982
    updates: bz#1666143
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 98550952bef0d84677706e75ff53a41dc8c90dec
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Dec 7 14:36:45 2018 +0530

    core: Resolve memory leak for brick
    
    Problem: Some functions are not freeing memory allocated by
             xdr_to_genric so it has become leak
    
    Solution: Call free to avoid leak
    
    Change-Id: I3524fe2831d1511d378a032f21467edae3850314
    fixes: bz#1656682
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 213f31bf9e72eee57a6579b66e259af8e59e9c67
Author: Arjun <arjsharm@redhat.com>
Date:   Tue Dec 4 11:02:37 2018 +0530

    gfapi : making glfs_setattr/glfs_fsetattr as public
    
    Initially glfs_fsetattr and glfs_setattr, both functions accepted iatt as arguements
    but now they accept stat and later in the function the stat is being converted to iatt
    so that it can be passed to syncop_fsetattr/syncop_setattr.
    
    Change-Id: I41a9e0124785a32ca19ef4d492c5ed5002e66ede
    updates: #389
    Signed-off-by: Arjun Sharma <arjsharm@redhat.com>

commit 2261e444a47ffffb5d64305efceee1d5a734cd75
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Dec 10 11:14:04 2018 +0530

    posix: Convert several posix_private members to gf_atomic
    
    Change-Id: I629698d8ddf6f15428880bdc1501d36bc37b8ebb
    fixes: bz#1657607
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit f578cdad23d8a8428a7012f777f4987507f19ea4
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Sat Jan 12 11:17:23 2019 +0530

    core: glusterd/add-brick-and-validate-replicated-volume-options.t is crash
    
    Problem: Sometime brick is getting crash at the time of handling
             pmap signin request
    
    Solution: glusterfs_mgmt_pamp_signin is using same frame to send
              pmap signin request so to avoid crash send signin request
              on separate frame
    
    Change-Id: I443f854171ec4372e8d5f84bdc576c468e92c493
    fixes: bz#1665656
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 211521f039bb5c883ef444577b5962bad9e18be1
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Nov 30 16:07:39 2018 +0530

    core: Resolve dict_leak at the time of destroying graph
    
    Problem: In gluster code some of the places it call's get_new_dict
             to create a dictionary without taking reference so at the time
             of dict_unref it has become a leak
    
    Solution: To resolve the same call dict_new instead of get_new_dict
    
    updates bz#1650403
    Change-Id: I3ccbbf5af07079a4fa09aad2cd0458c8625b2f06
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 8216ed2171789c8b6c6dc1e44cc171c89b1c063d
Author: Xiubo Li <xiubli@redhat.com>
Date:   Fri Jan 4 15:22:24 2019 +0800

    cluster/afr: fix zerofill transaction.start
    
    This maybe one mistake when coding.
    
    Fixes: bz#1665332
    Change-Id: Ia8f8dadf4a71579240ff9950b141ca528bd342b3
    Signed-off-by: Xiubo Li <xiubli@redhat.com>

commit 741f652769bc074fe85da1485e0e16df6e6766f1
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Jan 10 16:17:39 2019 +0530

    glusterd: fix crash
    
    Problem: running "gluster get-state glusterd odir /get-state"
    resulted in glusterd crash.
    
    Cause: In the above command output directory has been specified
    without "/" at the end. If "/" is not given at the end, "/" will
    be added to path using "strcat", so the added character "/" is
    not having memory allocated. When tried to free, glusterd will
    crash as"/" has no memory allocated.
    
    Solution: Instead of concatenating "/" to output directory, add
    it to output filename.
    
    Change-Id: I5dc00a71e46fbef4d07fe99ae23b36fb60dec1c2
    fixes: bz#1665038
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit ed2d1ad8266b09e4a71ffd193be3cf85467f4f06
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Jan 10 23:00:49 2019 -0800

    features/index: Correct incorrect definition in header
    
    s/QUIESCE/INDEX/
    
    fixes: bz#1665363
    
    Change-Id: I6dc4fde682cedeaa10d870267b8909af1a9449c0
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 01779e6c6c2c876a9e137d51ee1ce6a8062ea893
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Mon Dec 17 11:23:59 2018 +0530

    fix 32-bit-build-smoke warnings
    
    fixes: bz#1622665
    
    Change-Id: I777d67b1b62c284c62a02277238ad7538eef001e
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit c0c2022e7d7097e96270a74f37813eda0c4e6339
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 28 18:53:15 2018 +0530

    features/shard: Fix launch of multiple synctasks for background deletion
    
    PROBLEM:
    
    When multiple sharded files are deleted in quick succession, multiple
    issues were observed:
    1. misleading logs corresponding to a sharded file where while one log
       message said the shards corresponding to the file were deleted
       successfully, this was followed by multiple logs suggesting the very
       same operation failed. This was because of multiple synctasks
       attempting to clean up shards of the same file and only one of them
       succeeding (the one that gets ENTRYLK successfully), and the rest of
       them logging failure.
    
    2. multiple synctasks to do background deletion would be launched, one
       for each deleted file but all of them could readdir entries from
       .remove_me at the same time could potentially contend for ENTRYLK on
       .shard for each of the entry names. This is undesirable and wasteful.
    
    FIX:
    Background deletion will now follow a state machine. In the event that
    there are multiple attempts to launch synctask for background deletion,
    one for each file deleted, only the first task is launched. And if while
    this task is doing the cleanup, more attempts are made to delete other
    files, the state of the synctask is adjusted so that it restarts the
    crawl even after reaching end-of-directory to pick up any files it may
    have missed in the previous iteration.
    
    This patch also fixes uninitialized lk-owner during syncop_entrylk()
    which was leading to multiple background deletion synctasks entering
    the critical section at the same time and leading to illegal memory access
    of base inode in the second syntcask after it was destroyed post shard deletion
    by the first synctask.
    
    Change-Id: Ib33773d27fb4be463c7a8a5a6a4b63689705324e
    updates: bz#1662368
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 18bbb0f5b5bf6c96f764b7949df8a0a136b931ce
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Dec 28 17:45:58 2018 +0530

    configure: fix the duplicate CFLAGS options
    
    updates: bz#1193929
    Change-Id: I403878719a3f81fb2ea951a951f84880fb54f3cc
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 5a152a7a70f771d951af713ab9701bcbc651e7e2
Author: Varsha Rao <varao@redhat.com>
Date:   Wed Jan 9 15:10:37 2019 +0530

    libglusterfs/common-utils.c: Fix buffer size for checksum computation
    
    Problem: When quorum count option is updated, the change is not reflected in
    the nfs-server.vol file. This is because in get_checksum_for_file(), when the
    last part of the file read has size less than buffer size, the read buffer
    stores old data value along with correct data value.
    
    Solution: Pass the bytes read instead of fixed buffer size, for calculating
    checksum.
    
    Change-Id: I4b641607c8a262961b3f3da0028a54e08c3f8589
    fixes: bz#1657744
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 8c1eda9b5a19861be7e02f89cefae942c624d677
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Wed Jan 9 14:09:03 2019 +0800

    doc: fix wrong description of localtime-logging in manpages
    
    -L is the short option of --log-level, not --localtime-logging,
    and also, --localtime-logging does not contain an argument.
    
    Change-Id: I7e1163cb88b84ab5faecd0a65a1f7257e731d2a7
    updates: bz#1664551
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit aa85b54c6fa329f05ec24c1e98c59b2f993bf32b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Nov 27 11:47:12 2018 +0530

    extras/systemd: Remove socket activated syslog.target and add documentation keys
    
    Adopting patch provided by Patrick Matthäi <pmatthaei@debian.org> at:
    
    https://bugzilla.redhat.com/attachment.cgi?id=1470751
    
    fixes: bz#1560561
    Change-Id: I363a049c743c65823e6c4f153cbe20b47fcb64fb
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 1e28c54c5ec8d84ec8a22493161314010992918e
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Jan 2 16:25:35 2019 +0530

    core: brick process is crashed at the time of spawn thread
    
    Problem: brick is getting crashed at the time of calling
             pthread_detach after just call gf_thread_create.If
             sufficient resources are not available on the system
             pthread_create returns EAGAIN (non-negative) but the
             caller function expects negative error code in case of failure
    
    Solution: Change the condition in caller function to avoid the crash
    
    Change-Id: Ifeaa49f809957eb6c33aa9792f5af1b55566756d
    fixes: bz#1662906

commit fa7ae128706062afefcb0a3117527b8bef21f396
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Jan 10 11:08:49 2019 -0800

    performance/md-cache: Fix a crash when statfs caching is enabled
    
    mem_put() in STACK_UNWIND_STRICT causes a crash if frame->local is not null
    as md-cache obtains local from CALLOC.
    
    Changed two occurrences of STACK_UNWIND_STRICT to MDC_STACK_UNWIND as
    the latter macro does not rely on STACK_UNWIND_STRICT for cleaning up
    frame->local.
    
    fixes: bz#1632503
    Change-Id: I1b3edcb9372a164ef73119e99a49e747765d7166
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 99ac5a83805e46659124acfefbc05c9b6dda1a1b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jan 10 17:12:53 2019 +0530

    tests: increase the timeout for distribute bug 1117851.t
    
    The test is in borderline of 200seconds, and many a times, randomly
    takes little more time, and fails the whole regression. Better to keep
    timeout high, so we don't 'randomly' fail regression tests.
    
    updates: bz#1193929
    Change-Id: Ib0d3a9f7a75ee44446ec6da5e0510cccf83eecaa
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 77669043e290cb6a4c82dded96286370cf5c7db0
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Jan 8 16:35:35 2019 +0530

    afr : fix memory leak
    
    This patch fixes memory leak reported by ASan.
    
    The fix was first merged by
    https://review.gluster.org/#/c/glusterfs/+/21805.
    
    But later change was reverted due to this patch
    https://review.gluster.org/#/c/glusterfs/+/21178/.
    
    updates: bz#1633930
    
    Change-Id: I1febe121e0be33a637397a0b54d6b78391692b0d
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit f091c5570efd5c754c40d40336bad8183a3e16e0
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Thu Dec 27 19:18:35 2018 +0530

    cluster/afr: Disable client side heals in AFR by default.
    
    With this changeset, default value for the AFR client side
    heal volume option is set to "off"
    
    fixes: bz#1663102
    Change-Id: Ie4016932339c4896487e3e7cb5caca68739b7ba2
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit d1231f00dc176bb9f4583b0a69b81f7e16a74eb5
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Jan 9 16:57:21 2019 +0530

    dht: Add NULL check for stbuf in dht_rmdir_lookup_cbk
    
    Change-Id: I2ced288113a369cc6497a77ac1871007df434da4
    fixes: bz#1664647
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit c45050fcdf749706dcaa74c86f43493cdbf254d4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 21 20:51:03 2018 +0530

    features/locks: Dump connection_id even for posix locks
    
    ... in statedump for a better debugging experience.
    
    BEFORE:
    
    posixlk.posixlk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0,
    pid = 13635, owner=2dd2c3a11706dc8c, client=0x7f159012b000,
    connection-id=(null), granted at 2018-12-31 14:20:42
    
    connection-id is null above.
    
    AFTER:
    
    posixlk.posixlk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0,
    pid = 10977, owner=b485e33df21bdaa2, client=0x7fa24c01ab90,
    connection-id=CTX_ID:68e12340-eed2-4386-bf5e-1f43cf8693d9-GRAPH_ID:0-
    PID:10901-HOST:dhcp35-215.lab.eng.blr.redhat.com-PC_NAME:patchy-client-0-
    RECON_NO:-0, granted at 2018-12-31 14:33:50
    
    Change-Id: I4608994bacabb558a3be8c1634ee6b1d2d3022e2
    fixes: bz#1662679
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit d54f5cdfbca7af2da2139fb76af1f1e416a6d848
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jan 2 18:20:07 2019 +0530

    timer-wheel: run the timer function outside of locked region
    
    Surprizingly this also reduced 80% CPU overhead 'perf record' tool reported
    in posix_spin_lock in a brick-mux test volume initialization process.
    
    updates: bz#1193929
    Change-Id: I4e1df60d6fd094105c312df39f1527d3f07bed68
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit aa28fe32364e39981981d18c784e7f396d56153f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 28 07:27:11 2018 +0530

    features/shard: Assign fop id during background deletion to prevent excessive logging
    
    ... of the kind
    
    "[2018-12-26 05:22:44.195019] E [MSGID: 133010]
    [shard.c:2253:shard_common_lookup_shards_cbk] 0-volume1-shard: Lookup
    on shard 785 failed. Base file gfid = cd938e64-bf06-476f-a5d4-d580a0d37416
    [No such file or directory]"
    
    shard_common_lookup_shards_cbk() has a specific check to ignore ENOENT error without
    logging them during specific fops. But because background deletion is done in a new
    frame (with local->fop being GF_FOP_NULL), the ENOENT check is skipped and the
    absence of shards gets logged everytime.
    
    To fix this, local->fop is initialized to GF_FOP_UNLINK during background deletion.
    
    Change-Id: I0ca8d3b3bfbcd354b4a555eee520eb0479bcda35
    updates: bz#1662368
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 37653efdc7681d1b0f255054ec2f9c9ddd4c8b14
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jan 4 07:04:50 2019 +0000

    Revert "iobuf: Get rid of pre allocated iobuf_pool and use per thread mem pool"
    
    This reverts commit b87c397091bac6a4a6dec4e45a7671fad4a11770.
    
    There seems to be some performance regression with the patch and hence recommended to have it reverted.
    
    Updates: #325
    Change-Id: Id85d6203173a44fad6cf51d39b3e96f37afcec09

commit 054c7ea91603acfcb01db8455b25dda7e5e831b2
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jan 7 13:58:01 2019 -0500

    features/bit-rot: do not send version and signature keys in dict
    
    In lookup, if the file has been marked as bad, then bit-rot-stub
    was sending the version and signature xattr values as well in the
    response dictinary. This is not needed. Only bad file marker has
    to be sent.
    
    Change-Id: Id59c02e9857577c60849fd28ef657f71e0b15207
    fixes: bz#1664122
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 86f5d75c70a5fa6f1790b17d12d56fd8b37b9ddd
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Nov 16 23:26:35 2018 +0530

    performance/io-threads: Improve debuggability in statedump
    
    statedump from io-threads lacked information to understand the number of
    running threads & number of requests in each priority queue. This patch
    addresses that.
    
    Sample statedump output w/ this patch:
    
    current_high_priority_threads=7
    current_normal_priority_threads=9
    current_low_priority_threads=0
    current_least_priority_threads=0
    fast_priority_queue_length=32
    normal_priority_queue_length=45
    
    Also, changed the wording for least priority queue in
    iot_get_pri_meaning().
    
    Change-Id: Ic5f6391a15cc28884383f5185fce1cb52e0d10a5
    fixes: bz#1664124
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 1a3c2a48e7cd44f2cc8b7b5384321d289aedab8e
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Dec 20 15:28:37 2018 -0500

    gfapi: update returned/callback pre/post attributes to glfs_stat
    
    Change-Id: Ie0fe971e694101aa011d66aa496d0644669c2c5a
    Updates: #389
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit c31f1c232a6673c4e3fc3188e15ae0e708a54613
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Nov 21 09:43:23 2018 -0500

    gfapi: new api glfs_statx as linux's statx
    
    Change-Id: I44dd6ceef0954ae7fc13f920e84d81bbd3f6a774
    Updates: #389
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit f99f51ca87fd8703947df985901cbce37bc6c818
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Thu Jan 3 17:07:27 2019 +0800

    glfs-fops.c: fix the bad string length for snprintf
    
    Snprintf reserves one byte for the ending '\0'.
    A NAME_MAX bytes d_name is truncated to NAME_MAX - 1 bytes.
    
    Change-Id: Ic884d18cee24360e55ddb896dc587b0b74ef97fe
    updates: bz#1193929
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit a9b0003c717087ff168bc143c70559162e53e0d5
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Dec 25 13:29:15 2018 -0500

    leases: Reset lease_ctx->timer post deletion
    
    To avoid use_after_free, reset lease_ctx->timer back to NULL
    after the structure has been freed.
    
    Change-Id: Icd213ec809b8af934afdb519c335a4680a1d6cdc
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 8b4822d457cd62c1525b6fbaac8668c79f3951c0
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Dec 20 16:58:34 2018 +0800

    rpc-clnt: reduce transport connect log for EINPROGRESS
    
    quotad and ganesha.nfsd prints many logs as,
    
    [rpc-clnt.c:1739:rpc_clnt_submit ] 0-<VOLUME_NAME>-quota: error returned while attempting to connect to host: (null), port 0
    
    Change-Id: Ic0c815400619e4a87a772a51b19822920228c1ef
    Updates: bz#1596787
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 4a15ea1fd36390fa247dc2e429f14dc8fd621c49
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 2 18:42:19 2019 +0530

    rpcsvc: Don't expect dictionary values to be available
    
    When reconfigure happens, string values from one dictionary
    are directly set in another dictionary. This can lead to
    invalid memory when the first dictionary is freed up.
    So do dict_set_dynstr_with_alloc instead of dict_set_str
    
    updates bz#1650403
    Change-Id: Id53236467521cfdeb07e7178d87ba6cf88d17003
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 95ec7391d8db26b933e542694add2b419dddf89f
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Jan 4 15:49:53 2019 +0530

    glusterd: rebalance status should display information of localhost
    
    Problem:
    https://review.gluster.org/#/c/glusterfs/+/21762/ has migrated
    rebalance commands from op-sm framework to mgmt v3 framework.
    
    In a heterogenous cluster, if rebalance commands follow op-sm
    framework, localhost information is not displayed in the
    output of "gluster v rebalance <volname> status".
    
    Cause:
    Previously without https://review.gluster.org/#/c/glusterfs/+/21762/
    rebalance commands were following op-sm framework.
    In glusterd_volume_rebalance_use_rsp_dict() current_index variable
    keeps track of number/count of peers in trusted storage pool.
    In op-sm, glusterd_volume_rebalance_use_rsp_dict() will be called
    only for the peers. So the current index should start from 2
    assuming local host as node 1.
    
    With the above patch, rebalance commands are following mgmt v3
    framework. In mgmt v3, glusterd_volume_rebalance_use_rsp_dict()
    is called for all nodes. For localhost it is called from
    brick-op function and for peers it is called from brick-op
    call back function. So the current index value should start
    from 1.
    
    https://review.gluster.org/#/c/glusterfs/+/21762/ has changed the
    value of current index to 1. Because of this, In heterogenous cluster,
    local host's information is overwritten by one of the peers information.
    And rebalance status will not display localhost's information in
    the output.
    
    Solution: assign a value to current index based on a op-version
    check.
    
    Change-Id: I2dfba1f007e908cf160acc4a4a5d8ef672572e4d
    fixes: bz#1663243
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f6d0141b47ac36f6d2b100252241ed64bc92f913
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jan 3 10:52:22 2019 +0530

    extras: Add readdir-ahead to samba group command
    
    Change-Id: I310f014a9ab8416d9833f5711ff902da1457f415
    updates: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 0d4535c8db7b4be3fcee685d12f6974f7af89810
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Jan 3 19:09:36 2019 +0530

    glusterd: aggregate rsp from peers for profile command
    
    When we run profile info command, it should display statistics
    of all the bricks of the volume. To display information of bricks
    which are hosted on peers, we need to aggregate the response from
    peers.
    
    For profile info command, all the statistics will be added into
    the dictionary in brick-op phase. To aggregate the information from
    peers, we need to call glusterd_syncop_aggr_rsp_dict() in brick-op
    call back function.
    
    fixes: bz#1663223
    
    Change-Id: I5f5890c3d01974747f829128ab74be6071f4aa30
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 44f3382328b3bd12d3bbcdbfc408660eecf4befc
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Fri Dec 28 16:08:50 2018 +0800

    glusterd: fix memory leak in handshake
    
    Add missing unref to req_dict to fix memory leak in handle of
    handshake.
    
    Change-Id: I0d8573fc3668c1a0ccc9030e3a096bbe20ed5c36
    fixes: bz#1663077
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit d4fa2906b8e8a6de34c8e7b33b998fbc63f54cb1
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Jan 2 12:29:53 2019 +0530

    glusterd: kill the process without releasing the cleanup mutex lock
    
    Problem:
    glusterd acquires a cleanup mutex lock before it starts
    cleanup process, so that any other thread which tries to acquire
    lock on any resource will be blocked on cleanup mutex lock.
    
    We don't want any thread to try to acquire any resource, once
    the cleanup is started. because other threads might try to acquire
    lock on resources which are already freed by the thread which is
    going though the cleanup phase.
    
    previously we were releasing the cleanup mutex lock before the
    process exit. As we are releasing the cleanup mutex lock, before
    the process can exit some other thread which is blocked on
    cleanup mutex lock is acquiring the cleanup mutex lock and
    trying to acquire some resources which are already freed as a
    part of cleanup. This is leading glusterd to crash.
    
    Solution: We should exit the process without releasing the
    cleanup mutex lock.
    
    Change-Id: Ibae1c62260f141019017f7a547519a5d38dc2bb6
    fixes: bz#1654270
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit d9a8ccd354df6db94477bf9ecb09735194523665
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Dec 26 15:24:49 2018 +0530

    gfapi: nit cleanup related to releasing fs->mutex lock
    
    This is follow-up patch to the comment received for
     - https://review.gluster.org/#/c/glusterfs/+/21882
    
    We need not hold the fs->mutex lock to log error message.
    
    Change-Id: I29d2ea2e6cfecc3dd94982bd48f4bc9f11cc3aac
    fixes: bz#1660577
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 1ea203d6b6960621c6b445db42d6254c726df321
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Dec 28 13:04:36 2018 +0530

    libgfapi : fix coverity issue
    
    This patch fixes coverity issue in api/src/glfs-fops.c.
    
    CID: 1389247, 1389296, 1389369, 1389392.
    All coverity defects are of type Mixing enum types (MIXED_ENUMS).
    
    updates: bz#789278
    
    Change-Id: I007bb317ed5f0b8ddaf94a93b3a4d02b1e74cb8d
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 7a84e705ed0b96f479a0fc52fa734e0367bb2af2
Author: Harpreet Kaur <hlalwani@redhat.com>
Date:   Thu Dec 27 20:20:56 2018 +0530

    posix: buffer_size_warning coverity fix
    
    Defect: CID 1398469- Calling strncpy with a maximum size argument
    of 4096 bytes on destination array key of size 4096 bytes might
    leave the destination string unterminated.
    
    Fix: Using snprintf instead of strncpy.
    
    updates: bz#789278
    
    Change-Id: I4fdcd0cbf3af8b2ded94603d92d1ceb4112284c4
    Signed-off-by: Harpreet Kaur <hlalwani@redhat.com>

commit 63088d8225df025e03a0ea0a0d8fdc3e8e9b9b08
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Dec 28 09:56:20 2018 +0530

    multiple-files: clang-scan fixes
    
    updates: bz#1622665
    Change-Id: I9f3a75ed9be3d90f37843a140563c356830ef945
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 3ce7b5dbf069e7bf09c3470753c21efe03339291
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Nov 15 22:05:32 2018 +0200

    libglusterfs/src/mem-types.h: remove unused common enums from mem-types.h
    
    They were not used at all, just taking space.
    I've also marked all those that are not common really, but used
    in just one place - they probably should move there (in follow-up
    patches)
    
    As a test, I've removed from the stripe xlator unused private
    enums and moved one that was in the common list, but only
    used in the stripe code, to be a private enum.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    Change-Id: I1158dc1d259f1fd3f69904336c46c9d83cea799f

commit 36883e160e07466929c2fe7d6050403751d25a49
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Sep 28 23:20:28 2018 +0530

    configure: add a message about asan option
    
    This added hint helps to get ASan logs for the daemon processes, with
    this one can start using asan for regression tests.
    
    updates: bz#1633930
    Change-Id: I3b39892d45d29ae514dad8ab10f65703c02003f1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit a12bdfa72af9cc8df21d25b580058b49f3aa154a
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Thu Dec 13 17:59:20 2018 +0530

    glusterd: NULL pointer dereferencing clang fix
    
    Added ternary operator to avoid this issue
    
    Updates: bz#1622665
    
    Change-Id: I163d0628304a0d61249d1d97a4a3d3bee4ba4927
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit cd29723ab1a572fd9c2ceb3414b11d654cb9a08a
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Fri Dec 21 03:59:16 2018 +0530

    mgmt/glusterd: fix clang warning
    
    Attempt to free rsp.dict.dict_val twice
    
    Change-Id: I5dbc50430f59ca8d0c739b0fbe95d71981852889
    Updates: bz#1622665
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit a12cadc1377ef51ad52defd1da91bf8f599e5786
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 18 14:38:22 2018 +0530

    cluster/afr: Refactor internal locking code to allow multiple inodelks
    
    For implementing copy_file_range fop, AFR needs to perform two inodelks in the
    same transaction. This patch brings in the necessary structure to make it
    easier to do so.
    
    Entry-locks in AFR were already taking multiple entry-locks on different inodes
    with the respective basenames. This patch extends the logic in inodelks to use
    the same lockee_t structure. This lead to removal of quite a lot of duplicate
    code present in afr-lk-common.c as both the locks are doing same things except
    'winding' part.
    
    updates: #536
    Change-Id: Ibfce7e3f260bb27b18645152ec680c33866fe0ae
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 8d38c5b7337e44ad9f282966c0aa2e99bd7da506
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Fri Dec 28 10:44:32 2018 +0530

    rpc/rpc-lib: fix coverity issue
    
    Defect: Code can never be reached because of the
    condition queue_index > 1024 cannot be true.
    
    CID: 1398471 Logically dead code
    updates: bz#789278
    
    Change-Id: I367cda7e734f6d774900a58d8664cffcab69126f
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit de1fb17ac392427605ead87690f30f1a488f66a7
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Dec 28 08:38:24 2018 +0530

    rpc : fix coverity in rpc/rpc-lib/src/rpcsvc.c
    
    This patch fixes newly introduced coverity.
    
    CID: 1398472: Dereference before null check.
    updates: bz#789278
    
    Change-Id: Ie9b13084097de8f24b138acd7608c3e15b3bba9c
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 89f1ebef957813f1262603ea5ec82539edb1ecad
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Dec 27 13:21:57 2018 +0100

    barrier: replace boolean-switch statement with if/else
    
    Squash some ugly warnings, and make the code a little bit simpler by
    removing some unneeded goto jumps.
    
    On Ubuntu 16.04 the following warnings were reported by Amudhan:
    
          CC	   barrier.lo
        barrier.c: In function ‘notify’:
        barrier.c:499:33: warning: switch condition has boolean value [-Wswitch-bool]
                                 switch (past) {
                                         ^
        barrier.c: In function ‘reconfigure’:
        barrier.c:565:25: warning: switch condition has boolean value [-Wswitch-bool]
                         switch (past) {
                                 ^
    
    Change-Id: Ifb6b75058dff8c789b729c76530a1358d391f4d1
    Updates: bz#1193929
    Reported-by: Amudhan P <amudhan83@gmail.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit a6dc153e47f9025b09e8aae14ca6ba96fa20a23e
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Dec 27 14:54:28 2018 +0530

    glusterd: coverity fixes
    
    This patch addresses coverity issues with CID 1398470 and 1398475
    
    1398470 - Missing unlock - False positive, Added a annotation to
                               make coverity happy
    1398475 - Unused value
    
    Change-Id: I1bb3df0b716690fad8fc52c393c8b2b6c41f7860
    updates: bz#789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit b5a8a91c1d86f30cb669ca469b83c99b2e9dafcb
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Oct 23 18:03:45 2018 +0530

    cluster/ta: Check number/type of locks held on ta file
    
    Change-Id: Iec47856ce2819e7d7d38a60279602e53ba45858d
    updates: bz#1624332
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit a11c5c66321dd8411373a68cc163c981c7d083df
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Dec 26 11:40:26 2018 +0530

    core: Fixed typos in nl-cache and logging-guidelines.md
    
    Replaced "recieve" with "receive".
    
    Change-Id: I58a3d3d4a0093df4743de9fae4d8ff152d4b216c
    fixes: bz#1662089
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit a3d12d340abc0fb8cfa4d2faffbd59a1e5ba5718
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Dec 6 19:25:06 2018 +0530

    cluster/dht: refactor dht_lookup_cbk
    
    Rearrange the dht_lookup_cbk code to make
    it easier to understand.
    Corrected a message in dht_linkfile_create_lookup_cbk
    
    Change-Id: Id41db9ef901732f0410f1c007807362c630218ff
    fixes: bz#1590385
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit a1e7acc93a416fec6b87cc5601a9922759156771
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 21 09:58:16 2018 +0530

    socket: Remove redundant in_lock in incoming message handling
    
    A given epoll thread can handle only one incoming (POLLIN) request.
    And until the socket is rearmed for listening, it is guaranteed that
    there won't be any new incoming requests. As a result, the priv->in_lock
    which guards the socket proto state machine seems redundant.
    
    This patch removes priv->in_lock.
    
    Change-Id: I26b6ddd852aba8c10385833b85ffd2e53e46cb8c
    updates: bz#1467614
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit c3d23b06ce6bda906bdfb9bc8909bf30016c9995
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Dec 20 02:41:17 2018 +0530

    cli: fix memory leak
    
    This patch fixes memory leak in cli/src/cli.c.
    
    Change-Id: I4956c4180b34d4a9e3e6e60eeafba8cb2031896e
    updates: bz#1633930
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit d64fdf867fef36422ab84f2918f5d925597bc7d4
Author: Harpreet Kaur <hlalwani@redhat.com>
Date:   Fri Dec 14 13:12:26 2018 +0530

    posix: stack-buffer-overflow reported by asan
    
    This patch fixes buffer overflow in
    $SRC/xlators/storage/posix/src/posix-inode-fd-ops.c
    Memory access at offset 432 overflows "md5_checksum" variable.
    SUMMARY: AddressSanitizer: stack-buffer-overflow (/lib64/libasan.so.5+0xb825a)
    
    updates: bz#1633930
    
    Change-Id: I46010a09161d02cdf0c69679a334ec1d3d49cffb
    Signed-off-by: Harpreet Kaur <hlalwani@redhat.com>

commit 8fe3c6107a2b431d7cc0b8cfaeeb7941cf9590f9
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Dec 18 22:07:55 2018 +0530

    gfapi: Access fs->oldvolfile under mutex lock
    
    In some cases (for eg., when there are multiple
    RPC_CLNT_CONNECT notifications), multiple threads may fetch
    volfile and try to update it in 'fs' object simultaneously.
    Hence protect those variables' access under fs->mutex lock.
    
    Change-Id: Idaee9548560db32d83f4c04ebb1f375fee7864a9
    fixes: bz#1660577
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 233c909077fb1971e8813240a6161edc30c1e77b
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Dec 21 23:50:00 2018 +0530

    meta : fix coverity issue
    
    This patch fixes coverity issue possible null dereference.
    
    Change-Id: I93c0847c3d93b29a1e001ed044a63e908c670167
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 730ab84586b73e8677537ed90b78fabf5dde3b48
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Dec 20 16:41:37 2018 +0530

    tests: Brick is getting OOM in ./tests/bugs/core/bug-1432542-mpx-restart-crash.t
    
    This test "tests/bugs/core/bug-1432542-mpx-restart-crash.t" case creates 20 2x3
    volumes after enabling brick_mux.At the time of creating last volume brick is getting
    OOM because brick consumption has increased from previous consumption due to these patches
    https://review.gluster.org/#/c/glusterfs/+/19997/,
    https://review.gluster.org/#/c/glusterfs/+/20362/
    
    To avoid OOM reduce NUM_VOLS to 15 so that brick consumption has reduced
    
    Change-Id: Ib98b47a3db6b990ff22c7e57396d51e7fef5c7e8
    fixes: bz#1661214
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 0c7425d431b90c9c5c087511b34150e30dbe028a
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Dec 19 08:14:44 2018 +0530

    rpc: Use adaptive mutex in rpcsvc_program_register
    
    Adaptive mutexes are used to protect critical/shared data items that
    are held for short periods.It provides a balance between spin locks
    and traditional mutex.We have observed after use adaptive mutex in
    rpcsvc_program_register got some improvement.
    
    Change-Id: I7905744b32516ac4e4ca3c83c2e8e5e306093add
    fixes: bz#1660701

commit f2c2c906c0a81d24b14832974994604ea4569e0d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Dec 19 10:25:44 2018 +0530

    all: handle string-overflow warnings of coverity
    
    updates: bz#789278
    Change-Id: I7de800b90a614e3666e965b0cafc70026a844b2d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e1f92176a8d372e99386c0f007d6a38c0a54ca5b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Dec 19 09:45:42 2018 +0530

    all: handle USE_AFTER_FREE warnings
    
    * we shouldn't be using 'local' after DHT_STACK_UNWIND() as it frees
    the content of local. Add a 'goto out' or similar logic to handle
    the situation.
    
    * fix possible overlook of unref(dict), instead of unref(xdata).
    
    * make coverity happy by re-ordering unref in meta-defaults.
    
    * gfid-access: re-order dictionary allocation so we don't have to
      do a extra unref.
    
    * other obvious errors reported.
    
    updates: bz#789278
    Change-Id: If05961ee946b0c4868df19861d7e4a927a2a2489
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8cde14a537f0112400744d518ed196eb8fa232f2
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Dec 19 17:57:58 2018 +0530

    tests: Fix zero-flag.t script
    
    The default value of shard-block-size was changed from 4MB
    to 64MB sometime back. The script "fallocate"s a 6MB file
    and expects it to have 1 shard under .shard. This worked when
    the shard-block-size was 4MB. With the default value now at 64MB,
    file "file1" won't have any shards under .shard and the stat on the
    1st shard's path fails with ENOENT.
    
    Changed the script to explicitly set shard-block-size to 4MB.
    
    Change-Id: I7f1785922287d16d74c95fa57cbbe12e6e66e4f7
    fixes: bz#1656264
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 2af8fca492f3e1152177641b5e6ab9ea59ec0acd
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Aug 16 16:36:08 2018 +0530

    posix: use synctask for janitor
    
    With brick mux, the number of threads increases as the number of
    bricks increases. As an initiative to reduce the number of
    threads in brick mux scenario, replacing janitor thread to use
    synctask infra.
    
    Now close() and closedir() handle by separate janitor
    thread which is linked with glusterfs_ctx.
    
    Updates #475
    Change-Id: I0c4aaf728125ab7264442fde59f3d08542785f73
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit e3ec41af9a9f4d906dd7b512b3f4f91a6f338f4b
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Mon Dec 17 19:55:20 2018 +0530

    rdma: fix possible buffer overflow
    
    used snprintf instead of sprintf and if the source string is bigger
    than destination then logged a warning message.
    
    clang warning: ‘%s’ directive writing up to 1024 bytes into a region
    of size 108.
    
    updates: bz#1622665
    
    Change-Id: Ia5e7c53d35d8178dd2c75708698599fe8bded5de
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 9662504d45f3e285772f5188a7edf7ae3665cc6a
Author: karthik-us <ksubrahm@redhat.com>
Date:   Tue Dec 4 11:19:27 2018 +0530

    cluster/afr: Allow lookup on root if it is from ADD_REPLICA_MOUNT
    
    Problem: When trying to convert a plain distribute volume to replica-3
    or arbiter type it is failing with ENOTCONN error as the lookup on
    the root will fail as there is no quorum.
    
    Fix: Allow lookup on root if it is coming from the ADD_REPLICA_MOUNT
    which is used while adding bricks to a volume. It will try to set the
    pending xattrs for the newly added bricks to allow the heal to happen
    in the right direction and avoid data loss scenarios.
    
    Note: This fix will solve the problem of type conversion only in the
    case where the volume was mounted at least once. The conversion of
    non mounted volumes will still fail since the dht selfheal tries to
    set the directory layout will fail as they do that with the PID
    GF_CLIENT_PID_NO_ROOT_SQUASH set in the frame->root.
    
    Change-Id: Ic511939981dad118cc946754341318b164954b3b
    fixes: bz#1655854
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit b87c397091bac6a4a6dec4e45a7671fad4a11770
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Nov 21 12:09:39 2018 +0530

    iobuf: Get rid of pre allocated iobuf_pool and use per thread mem pool
    
    The current implementation of iobuf_pool has two problems:
    - prealloc of 12.5MB memory, this limits the scale factor of the gluster
      processes due to RAM requirements
    - lock contention, as the current implementation has one global
      iobuf_pool lock. Credits for debugging and addressing the same goes to
      Krutika Dhananjay <kdhananj@redhat.com>. Issue: #410
    
    Hence changing the iobuf implementation to use per thread mem pool.
    This may theoritically appear to cause perf dip as there is no preallocation.
    But per thread mem pool will not have significant perf impact as the last
    allocated memory is kept alive for subsequent allocs, for some time.
    The worst case would be if iobufs requested are of random sizes each time.
    The best case is, if we get iobuf request of the same size. From the perf
    tests, this patch did not seem to cause any perf decrease.
    
    Note that, with this patch, the rdma performance is going to degrade
    drastically. In one of the previous patchsets we had fixes to not
    degrade rdma perf, but rdma is not supported and also not tested [1].
    Hence the decision was to not have code in rdma that is not tested
    and not supported.
    
    [1] https://lists.gluster.org/pipermail/gluster-users.old/2018-July/034400.html
    
    Updates: #325
    Change-Id: Ic2ef3bd498f9250dea25f25ba0c01fde19584b27
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit d50f22e6ae410fdcde573b6015b97dc1573bbb7e
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Fri Oct 12 10:03:31 2018 +0530

    performance/io-cache: update pages with write data
    
    Currently io-cache invalidate pages falling in the range of write. But
    instead it can update pages with same data so that reads can make use
    of the cache.
    
    credits: Xavi Hernandez <xhernandez@redhat.com>
    
    Change-Id: I932bd3da97ddfd464187f3009b1013eb334f00a7
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    updates: bz#1659869

commit 51ff065b8b9d2117688053cddb29186e3135c4a1
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Fri Dec 14 11:27:33 2018 +0530

    performance/ob: make open-behind as a child of quick-read
    
    With read-after-open being set to yes by default, if open-behind sees
    any reads, it'll do an open on backend (and hence flush/release
    later). This means with the current order of quick-read and
    open-behind, open-behind sees all reads and hence also does open
    bringing down performance for small file reads.
    
    Since for small files, reads are absorbed by quick-read, if quick-read
    is made a parent of open-behind, ob doesn't witness any reads. For
    read-only workloads, this means ob doen't do any opens (even with
    read-after-open yes and use-anonymous-fd no).
    
    Change-Id: I138a42b006d104cff43ee6f07829e39c36f6f234
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Fixes: bz#1659327

commit f9859218da827eac5b2102673e7a89497228e672
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Dec 14 19:18:20 2018 +0200

    xlators/cluster/afr/src/afr-self-heal-common.c: remove a variable array.
    
    Added '-Wvla' and saw this - gcc doesn't like variable arrays.
    There are plenty of others in the EC code, but this seems OK to remove:
    there is no use for the array members (I hope - that was from reading
    the code).
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I350f4520e52b86c8bbcd60eea1b27ef99cd119aa

commit f9220c89ae848c72df8232163d5a990283f15f5a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Dec 17 09:17:44 2018 +0530

    glusterd: define max-port to 60999
    
    As glusterd scans through all the ports in its defined range, with RHEL
    7.3 onwards any port beyond 60999 isn't within the ephemeral port range
    and following AVC denial message is seen.
    
    type=AVC msg=audit(1471946614.154:109): avc:  denied  { name_bind } for
    pid=2302 comm="glusterd" src=61000 scontext=system_u:system_r:glusterd_t:s0
    tcontext=system_u:object_r:ephemeral_port_t:s0 tclass=tcp_socket
    
    Fix is to define the max port range to 60999 in glusterd.vol file. The
    port range can be tweaked through a reconfigure of this configuration
    file though.
    
    Fixes: bz#1659857
    Change-Id: I60fd4a421d8509b8dca4ca13b73999ae33965f72
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 0b4b111fbd80a5d400a07d61e2b99f230f9be76f
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Nov 30 16:16:55 2018 +0530

    glusterd: migrating rebalance commands to mgmt_v3 framework
    
    Current rebalance commands use the op_state machine framework.
    Porting it to use the mgmt_v3 framework.
    
    Change-Id: I6faf4a6335c2e2f3d54bbde79908a7749e4613e7
    fixes: bz#1655827
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 9ff080382cb8c8aab561f4131c3f631e33670338
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Nov 21 10:01:08 2018 +0530

    mem-pool: Add api to mem_get based on requested size
    
    Currently mem-pool implementation provides api to get from the
    mem pool based on the struct type. This is to retain api
    compatibility with the old implementation of mem pool. Internally
    in the mem pool structure there is a mapping from struct to size
    based pools.
    
    In this patch, we are adding new APIs to fetch memory from mem pool,
    given a size.
    
    Change-Id: Ib220ee45ebd134a7be8f6482db5a592dbb7b9211
    Updates: #325
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 822779332e193471a6caa3199f0f618d2aa2c900
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Dec 17 14:07:27 2018 +0530

    geo-rep : fix slave volume read-only option
    
    Problem: When separate ssh key is given for non root user setting slave volume
             read-only option results in failure.
    
    Solution: Check for extra param in case separate key is given for non-root user
              and take action accordingly.
    
    Change-Id: Iafe9a2aa6b86cde1dcd7d63771048a6ae33c2cde
    fixes: bz#1659971
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit c228f0c2d94c028619088c07b66f88488f7c3335
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Dec 2 15:35:09 2018 +0530

    Don't depend on string options to be valid always
    
    updates bz#1650403
    Change-Id: Ib5a11e691599ce4bd93c1ed5aca6060592893961
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit bdcb2d8497d77ff28cb031ae3992eb7ea0c90486
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Dec 3 11:23:20 2018 -0500

    features/snapview-client: access priv->path inside lock
    
    To handle the race condition of a fop or a function accessing priv->path
    and a reconfigure changing priv->path (because entry point directory
    changed), the private structure's path is guarded by the lock.
    
    updates bz#1650403
    Change-Id: I61c539da06d68d38eafcf2155699c7702f31323e
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 403c69d35827b6cbb430e97a797c318cca81e86e
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Sep 13 16:03:23 2018 +0300

    AFR xlator: use dict_{setn|getn|deln|get_int32n|set_int32n|set_strn}
    
    In a previous patch (https://review.gluster.org/20769) we've
    added the key length to be passed to dict_* funcs, to remove the need
    to strlen() it. This patch moves some xlators to use it.
    
    - In some cases, moved strlen() of the key length outside of locks,
    which is usually a good thing. Please verify it's safe to do so.
    - In some cases, created a prefix for the keys, replacing something like
    "%d-%d" with a "%s" in snprintf(). Not sure it adds value, but improves
    readability.
    
    Please review carefully.
    
    Compile-tested only!
    
    Change-Id: I04f2a1eb2ecfc3283d849d150d10d088ae7aa7f1
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit f0c46df09fe542d6a365adc0c544ba460598501c
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Dec 12 12:10:44 2018 +0530

    selinux/glusterd : add "features.selinux" to glusterd-volume-set.c
    
    Fixes: bz#1659868
    Change-Id: I38675ba4d47c8ba7f94cfb4734692683ddb3dcfd
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 152907d438bf8bb571e43ec278ec7b01da2431a6
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 5 17:27:07 2018 +0530

    cluster/afr: Fix mem leak reported by ASAN
    
    Traceback:
    
    Direct leak of 765 byte(s) in 9 object(s) allocated from:
        #0 0x7ffb9cad2c48 in malloc (/lib64/libasan.so.5+0xeec48)
        #1 0x7ffb9c5f8949 in __gf_malloc ./libglusterfs/src/mem-pool.c:136
        #2 0x7ffb9c5f91bb in gf_vasprintf ./libglusterfs/src/mem-pool.c:236
        #3 0x7ffb9c5f938a in gf_asprintf ./libglusterfs/src/mem-pool.c:256
        #4 0x7ffb826714ab in afr_get_heal_info ./xlators/cluster/afr/src/afr-common.c:6204
        #5 0x7ffb825765e5 in afr_handle_heal_xattrs ./xlators/cluster/afr/src/afr-inode-read.c:1481
        #6 0x7ffb825765e5 in afr_getxattr ./xlators/cluster/afr/src/afr-inode-read.c:1571
        #7 0x7ffb9c635af7 in syncop_getxattr ./libglusterfs/src/syncop.c:1680
        #8 0x406c78 in glfsh_process_entries ./heal/src/glfs-heal.c:810
        #9 0x408555 in glfsh_crawl_directory ./heal/src/glfs-heal.c:898
        #10 0x408cc0 in glfsh_print_pending_heals_type ./heal/src/glfs-heal.c:970
        #11 0x408fc5 in glfsh_print_pending_heals ./heal/src/glfs-heal.c:1012
        #12 0x409546 in glfsh_gather_heal_info ./heal/src/glfs-heal.c:1154
        #13 0x403e96 in main ./heal/src/glfs-heal.c:1745
        #14 0x7ffb99bc411a in __libc_start_main ../csu/libc-start.c:308
    
    The dictionary is referenced by caller to print the status.
    So set it as dynstr, the last unref of dictionary will free it.
    
    updates: bz#1633930
    Change-Id: Ib5a7cb891e6f7d90560859aaf6239e52ff5477d0
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit b40bb5394dbe5b391d8218d71d672d7e1820e5d3
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Dec 14 16:57:01 2018 -0500

    dht: Fix clang warnings in dht-common.c
    
    Change-Id: I0894d62edd68e13d123aaa5ca1827b98283f0d3e
    Updates: bz#1622665
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit eb77d69be528580ca6e4c109762b862114beca87
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Oct 22 00:59:05 2018 +0200

    fuse: SETLKW interrupt
    
    Use the (f)getxattr based clearlocks interface to
    interrupt a pending lock request.
    
    updates: #465
    Change-Id: I4e91a4d8791fc688fed400a02de4c53487e61be2
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit d49b41e817d592c1904b6f01716df6546dad3ebe
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Oct 16 16:31:49 2018 +0530

    fuse: add --lru-limit option
    
    The inode LRU mechanism is moot in fuse xlator (ie. there is no
    limit for the LRU list), as fuse inodes are referenced from
    kernel context, and thus they can only be dropped on request of
    the kernel. This might results in a high number of passive
    inodes which are useless for the glusterfs client, causing a
    significant memory overhead.
    
    This change tries to remedy this by extending the LRU semantics
    and allowing to set a finite limit on the fuse inode LRU.
    
    A brief history of problem:
    
    When gluster's inode table was designed, fuse didn't have any
    'invalidate' method, which means, userspace application could
    never ask kernel to send a 'forget()' fop, instead had to wait
    for kernel to send it based on kernel's parameters. Inode table
    remembers the number of times kernel has cached the inode based
    on the 'nlookup' parameter. And 'nlookup' field is not used by
    no other entry points (like server-protocol, gfapi etc).
    
    Hence the inode_table of fuse module always has to have lru-limit
    as '0', which means no limit. GlusterFS always had to keep all
    inodes in memory as kernel would have had a reference to it.
    Again, the reason for this is, kernel's glusterfs inode reference
    was pointer of 'inode_t' structure in glusterfs. As it is a
    pointer, we could never free it (to prevent segfault, or memory
    corruption).
    
    Solution:
    
    In the inode table, handle the prune case of inodes with 'nlookup'
    differently, and call a 'invalidator' method, which in this case is
    fuse_invalidate(), and it sends the request to kernel for getting
    the forget request.
    
    When the kernel sends the forget, it means, it has dropped all
    the reference to the inode, and it will send the forget with the
    'nlookup' parameter too. We just need to make sure to reduce the
    'nlookup' value we have when we get forget. That automatically
    cause the relevant prune to happen.
    
    Credits: Csaba Henk, Xavier Hernandez, Raghavendra Gowdappa, Nithya B
    
    fixes: bz#1560969
    Change-Id: Ifee0737b23b12b1426c224ec5b8f591f487d83a2
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit fc74ef85e0780e0a265275df00e4d0d4a2d05eab
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Dec 14 16:42:26 2018 +0530

    performance/rda:  Fixed dict_t memory leak
    
    Removed all references to dict_t xdata_from_req which is
    allocated but not used anywhere. It is also not cleaned up
    and hence causes a memory leak.
    
    Change-Id: I2edb857696191e872ad12a12efc36999626bacc7
    fixes: bz#1659432
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 5ec271c316ec6538130d25148179721c595dd5a2
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Fri Nov 23 01:58:44 2018 +0530

    glusterfsd: Fix coverity issue
    
    Problem reported: value assigned to a variable is never used
    
    Fixes CID : 1274230
    
    updates: bz#789278
    
    Change-Id: I7afcb411876dea81c6820c5b31ae0a2896f9ca15
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit a6a5f7aa6f05d21db7e8b4fbc39f2c6f843aac39
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Dec 6 15:05:20 2018 +0530

    extras: New group volume set command for Samba integration
    
     # gluster volume set <VOLNAME> group samba
    
    List of volume set options from group-samba are aimed at improving the below
    workloads which consumes time and network hops in SMB world:
    
    * Listing of large directories
    * Negative lookups during creation of files
    
    Caching the necessary metadata required for these workloads saves us time and
    network hops. On the other side we have to ensure correctness(avoiding stale
    cache) in caching(via md-cache) with the help of cache invalidation in an
    environment where multiple client access is expected.
    
    Change-Id: Icdd2d8e5eb290e12bc509105418c668f432f4eae
    fixes: bz#1656771
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 930d8b706136e2aaa1f3d173f79e1a4970e65561
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Dec 6 16:13:46 2018 +0100

    locks: handle "clear locks" xattr in fgetxattr too
    
    The lock clearing procedure was kicked in only in
    getxattr context. We need it to work the same way
    if it's triggered via fgetxattr (as is the case
    with interrupt handling).
    
    Also cleaned up the instrumentation a bit (more logs,
    proper management of allocated data).
    
    updates: #465
    Change-Id: Icfca26ee181da3b8e15ca3fcf61cd5702e2730c8
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit e3d01793a3ef1307240fdc7d7f0d12be1488b921
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Dec 2 23:19:46 2018 +0200

    Multiple posix related files: several modifications
    
    Just looked at posix.c and related code and performed
    some changes and cleanups. The only important one is #3 below,
    but surely the others (#2 and #4) need careful review.
    Changes to other files are as they were related to code paths
    in posix.c.
    
    I'll send a separate patch for other posix related files.
    
    Main changes:
    1. Proper initializtion for parameters, where it made sense.
    2. Logged outside the lock in several places.
    3. Moved from CALLOC to MALLOC where it made sense.
    4. Aligned structures.
    5. moved dictionary functions to use _sizen where possible.
    (dict_get() -> dict_get_sizen() for example)
    
    Compile-tested only!
    
    Change-Id: Ia84699fb495e06d095339c91c1ba770d1393bb6c
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 2421453bf38469a8c0861f205bdee37e771aa39f
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Mon Dec 10 18:02:19 2018 +0530

    cli: variable-length array declaration clang fix
    
    Problem: Declared variable-length array can have zero size
    
    Added a goto statement to address this issue.
    
    Updates: bz#1622665
    
    Change-Id: Ibf80643490367a5f7e50f66f87e4296380be45de
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 64d800940e67b75d51f536816ee92bae59d6f850
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Thu Dec 13 11:14:10 2018 +0530

    cluster/ec: NULL pointer deferencing clang fix
    
    Removing VALIDATE_OR_GOTO check on "this"
    
    Change-Id: I154deaca5302b41c1cafd87077de880dd03ec613
    Updates: bz#1622665
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit bfe2b5e1530efd364af7a175c8a1c89bc4cab0bb
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Dec 12 16:45:09 2018 -0500

    clang: Fix various missing checks for empty list
    
    When using list_for_each_entry(_safe) functions, care needs
    to be taken that the list passed in are not empty, as these
    functions are not empty list safe.
    
    clag scan reported various points where this this pattern
    could be caught, and this patch fixes the same.
    
    Additionally the following changes are present in this patch,
    - Added an explicit op_ret setting in error case in the
    macro MAKE_INODE_HANDLE to address another clang issue reported
    - Minor refactoring of some functions in quota code, to address
    possible allocation failures in certain functions (which in turn
    cause possible empty lists to be passed around)
    
    Change-Id: I1e761a8d218708f714effb56fa643df2a3ea2cc7
    Updates: bz#1622665
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 8293d21280fd6ddfc9bb54068cf87794fc6be207
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Dec 6 12:29:25 2018 +0530

    all: remove code which is not being considered in build
    
    These xlators are now removed from build as per discussion/announcement
    done at https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    * move rot-13 to playground, as it is used only as demo
      purpose, and is documented in many places.
    
    * Removed code of below xlators:
      - cluster/stripe
      - cluster/tier
      - features/changetimerecorder
      - features/glupy
      - performance/symlink-cache
      - encryption/crypt
      - storage/bd
      - experimental/posix2
      - experimental/dht2
      - experimental/fdl
      - experimental/jbr
    
    updates: bz#1635688
    Change-Id: I1d2d63c32535e149bc8dcb2daa76236c707996e8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit af7e957b4954bd84b8f7df6bfbd59c939092ead2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Dec 6 16:24:52 2018 +0530

    xlator: make 'xlator_api' mandatory
    
    * Remove the options to load old symbol.
    * keep only 'xlator_api' symbol from being exported using xlator.sym
    * add xlator_api to all the xlators where its missing
    
    NOTE: This covers all the xlators which has at least a test case
    to validate its loading. If there is a translator, which doesn't
    have any test, then we should probably remove that from codebase.
    
    fixes: #164
    Change-Id: Ibcdc8c9844cda6b4463d907a15813745d14c1ebb
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 088e2cbb5ee3f3e766b7e4021e2d86d0c5187de0
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Dec 11 16:20:58 2018 +0530

    symlink-cache: remove from the build
    
    symlink-cache was written as an experiment to reduce the load
    on 'build' systems, which keep doing symlink resolution to get
    the proper header files. But since last 6+ years, there was no
    way to add it to the volfile using gluster cli, and hence was
    not supported anymore. As it is not maintained, and as announced
    on [1], we are planning to remove it from the build system.
    
    [1]- https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    updates: bz#1635688
    Change-Id: Iaa25069bceed04cf65f79a4b4a02c05cee848eb5
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit fb917bf10b4783d5c669e81a5be1f902ca48cb84
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Nov 23 09:39:43 2018 +0530

    [geo-rep]: Worker still ACTIVE after killing bricks
    
    Problem: In changelog xlator after destroying listener it call's
             unlink to delete changelog socket file but socket file
             reference is not cleaned up from process memory
    
    Solution: 1) To cleanup reference completely from process memory
                 serialize transport cleanup for changelog and then
                 unlink socket file
              2) Brick xlator will notify GF_EVENT_PARENT_DOWN to next
                 xlator only after cleanup all xprts
    
    Test: To test the same run below steps
          1) Setup some volume and enable brick mux
          2) kill anyone brick with gf_attach
          3) check changelog socket for specific to killed brick
             in lsof, it should cleanup completely
    
    fixes: bz#1600145
    
    Change-Id: Iba06cbf77d8a87b34a60fce50f6d8c0d427fa491
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 52d3f82db2f032eae1b60ffa2f283109858ce3df
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Dec 11 15:32:03 2018 +0530

    afr: some minor itable related cleanups
    
    - this->itable always needs to be allocated, hence move it outside
    afr_selfheal_daemon_init().
    - Invoke afr_selfheal_daemon_init() only for self-heal daemon case.
    - remove redundant itable allocation in afr_discover().
    - destroy itable in fini.
    
    Updates bz#1193929
    Change-Id: Ib28b50b607386f5a5aa7d2f743c8b506ccb10eae
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 607bbd935f102602810fdeb61079b85ecb58a118
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Nov 21 14:33:53 2018 +0530

    rpc: Resolve memory leak in mgmt_pmap_signout_cbk
    
    Problem: At the time of submit signout request to mgmt
             rpc_clnt_mgmt_pmap_signout create a frame but in cbk
             frame is not destroyed
    
    Solution: cleanup frame in mgmt_pmap_signout_cbk to avoid leak
    
    Change-Id: I9961cacb2e02c8023c4c99e22e299b8729c2b09f
    fixes: bz#1658045
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit c9d117d54aea1d775e0eef1881892d11fa12811e
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Dec 12 09:23:11 2018 +0530

    core: move invalid port logs to DEBUG log level
    
    Stop spamming "invalid port" logs in case sysadmin has reserved a large
    number of ports.
    
    Change-Id: I244ef7693560cc404b36cadc6b05d92ec0e908d3
    fixes: bz#1656517
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 7dadea15c58eb92e5f5727190bf9446dd6fe7a3c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Nov 6 15:27:31 2018 -0500

    copy_file_range support in GlusterFS
    
        * libglusterfs changes to add new fop
    
        * Fuse changes:
          - Changes in fuse bridge xlator to receive and send responses
    
        * posix changes to perform the op on the backend filesystem
    
        * protocol and rpc changes for sending and receiving the fop
    
        * gfapi changes for performing the fop
    
        * tools: glfs-copy-file-range tool for testing copy_file_range fop
    
          - Although, copy_file_range support has been added to the upstream
    	    fuse kernel module, no release has been made yet of a kernel
            which contains the support. It is expected to come in the
            upcoming release of linux-4.20
    
            So, as of now, executing copy_file_range fop on a fused based
            filesystem results in fuse kernel module sending read on the
    	    source fd and write on the destination fd.
    
    	    Therefore a small gfapi based tool has been written to be able
            test the copy_file_range fop. This tool is similar (in functionality)
    	    to the example program given in copy_file_range man page.
    
    	    So, running regular copy_file_range on a fuse mount point and
    	    running gfapi based glfs-copy-file-range tool gives some idea about
    	    how fast, the copy_file_range (or reflink) can be.
    
    	    On the local machine this was the result obtained.
    
    	    mount -t glusterfs workstation:new /mnt/glusterfs
    	    [root@workstation ~]# cd /mnt/glusterfs/
    	    [root@workstation glusterfs]# ls
    	    file
    	    [root@workstation glusterfs]# cd
    	    [root@workstation ~]# time /tmp/a.out /mnt/glusterfs/file /mnt/glusterfs/new
    	    real  0m6.495s
    	    user  0m0.000s
    	    sys   0m1.439s
    	    [root@workstation ~]# time glfs-copy-file-range $(hostname) new /tmp/glfs.log /file /rrr
    	    OPEN_SRC: opening /file is success
    	    OPEN_DST: opening /rrr is success
    	    FSTAT_SRC: fstat on /rrr is success
    	    copy_file_range successful
    
            real  0m0.309s
            user  0m0.039s
            sys   0m0.017s
    
            This tool needs following arguments
             1) hostname
             2) volume name
             3) log file path
             4) source file path (relative to the gluster volume root)
             5) destination file path (relative to the gluster volume root)
    
            "glfs-copy-file-range <hostname> <volume> <log file path> <source> <destination>"
    
          - Added a testcase as well to run glfs-copy-file-range tool
    
        * io-stats changes to capture the fop for profiling
    
        * NOTE:
    
          - Added conditional check to see whether the copy_file_range syscall
            is available or not. If not, then return ENOSYS.
    
          - Added conditional check for kernel minor version in fuse_kernel.h
            and fuse-bridge while referring to copy_file_range. And the kernel
            minor version is kept as it is. i.e. 24. Increment it in future
            when there is a kernel release which contains the support for
            copy_file_range fop in fuse kernel module.
    
        * The document which contains a writeup on this enhancement can be found at
          https://docs.google.com/document/d/1BSILbXr_knynNwxSyyu503JoTz5QFM_4suNIh2WwrSc/edit
    
    Change-Id: I280069c814dd21ce6ec3be00a884fc24ab692367
    updates: #536
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 5c723ade196600030ee84621384cceb10fff64d8
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Dec 10 18:13:19 2018 +0530

    cluster/afr: Do not update read_subvol in inode_ctx after rename/link fop
    
    Since rename/link fops on a file will not change any data in it, it should
    not update the read_subvol values in the inode_ctx, which interprets the
    data & metadata readable subvols for that file. The old read_subvol values
    should be retained even after the rename/link operations.
    
    Change-Id: I068044a426823a566f5bea8aa063cd689199d6dd
    fixes: bz#1657783
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 3e3d83ee359c8bc8a8694865e0a8af869b2b8f33
Author: Harpreet Kaur <hlalwani@redhat.com>
Date:   Tue Dec 11 15:07:56 2018 +0530

    tools: stack-buffer-overflow reported by asan
    
    This patch fixes buffer overflow in $SRC/tools/setgfid2path/src/main.c
    Memory access at offset 196 overflows "pgfid" variable
    SUMMARY: AddressSanitizer: stack-buffer-overflow (/lib64/libasan.so.5+0x4e935)
    
    updates: bz#1633930
    
    Change-Id: Ib508c57e96c46b628f63c511437b853b39ae7955
    Signed-off-by: Harpreet Kaur <hlalwani@redhat.com>

commit e41fee7ba316655cdaafb9234a1590051f82db11
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Thu Dec 6 15:04:55 2018 +0530

    afr: Resource leak coverity fixes
    
    Problem reported by Coverity: Leak of memory or pointers to
    system resources.
    Deallocate the memory pointed to by xattr_serz as the memory
    reference is not stored anywhere.
    
    Fixes CID: 1124760, 124787, 1382418
    
    Change-Id: Ib9c2ef28c52e2d43de2552cfd959a98b26272bc1
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit 08adbfb5d2edf9dc01ecc2cf2ca5eccb320b8721
Author: rishubhjain <rishubhjain47@gmail.com>
Date:   Mon Dec 10 13:04:13 2018 -0500

    write-behind/bit-rot: fix identifier
    
    Rename the identifiers, bit-rot-server to bit-rot in bit-rot.c & write-ahead to
    write-behind in write-behind.c to ensure GD2 understands the options
    
    Change-Id: Id271ae97de2e54f4e30174482c4e1fb6afc728d3
    Fixes: #164
    Signed-off-by: rishubhjain <rishubhjain47@gmail.com>

commit f50251daeece85d6ada79b1d1f6697d4fac59ad4
Author: Harpreet Kaur <hlalwani@redhat.com>
Date:   Mon Dec 10 16:14:54 2018 +0530

    nfs: memory leak issue reported by asan
    
    This patch fixes Direct leaks in exports.c
    Leaks are happening in exp_file_parse
    SUMMARY: AddressSanitizer: 5120 byte(s) leaked in 20 allocation(s).
    SUMMARY: AddressSanitizer: 512 byte(s) leaked in 4 allocation(s).
    
    Updates: bz#1633930
    
    Change-Id: Ib4474f8f6c65d737ed54ed35b4234410d1fd673e
    Signed-off-by: Harpreet Kaur <hlalwani@redhat.com>

commit 8b3a1b19fbd73545cb86029ee34033d87190bca5
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Dec 5 20:37:53 2018 +0530

    encryption: remove crypt xlator from build
    
    Based on the proposal to remove few features as they are not
    actively maintained [1], removing crypt translator from the build.
    
    [1] - https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    Crypt xlator helped in on-disk / at-rest encryption of data. But
    currently as there are no maintainers for this, planning to remove
    it from master codebase. We are planning to host these experimental/
    tech-preview xlators in another repository, so people who want to
    contribute can still use the bits.
    
    updates: bz#1635688
    
    Change-Id: I7f2453907a595c34f635a88c49aab0845369c6e7
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e82bcc33ed2d5cd54d3f918397f31818089299ad
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Nov 26 14:40:00 2018 +0530

    posix: posix_health_check_thread_proc crash due to priv is NULL
    
    Problem: posix_fini sends a cancellation request to health_check
             thread and cleanup priv without ensuring health_check thread
             is running
    
    Solution: Make health_check && disk_space thread joinable and call
              gf_thread_cleanup_xint to wait unless thread is not finished
    
    Change-Id: I4d37b08138766881dab0922a47ed68a2c3411f13
    fixes: bz#1636570
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 2b7b6ff28fa92335613d0b5715acd552cfcfd759
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Dec 7 12:35:20 2018 +0530

    glusterd: Resolve memory leak in some glusterd functions
    
    Problem: Functions allocate memory for req structure but after submit
             request they missed to cleanup memory
    
    Solution: After submit request cleanup allocated mmeory
    
    Change-Id: I8f995787ed8986b882f008ccd588670b5d4139f5
    updates: bz#1633930
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 74c72d0dd9a47b842f4247d939b64089a6fb8e43
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Dec 7 10:53:44 2018 +0530

    cli : fix memory leak in cli-cmd-volume.c
    
    This patch fixes ememory leak reported by ASan.
    
    Tracebacks:
    Direct leak of 84 byte(s) in 1 object(s) allocated from:
        #0 0x7f71ea107848 in __interceptor_malloc (/lib64/libasan.so.5+0xef848)
        #1 0x7f71e9e2ac49 in __gf_malloc ./libglusterfs/src/mem-pool.c:136
        #2 0x7f71e9e2b4bb in gf_vasprintf ./libglusterfs/src/mem-pool.c:236
        #3 0x7f71e9e2b68a in gf_asprintf ./libglusterfs/src/mem-pool.c:256
        #4 0x41e8ec in cli_cmd_bitrot_cbk ./cli/src/cli-cmd-volume.c:1847
        #5 0x410b39 in cli_cmd_process ./cli/src/cli-cmd.c:137
        #6 0x40fe9d in cli_batch ./cli/src/input.c:29
        #7 0x7f71e989558d in start_thread (/lib64/libpthread.so.0+0x858d)
    
    updates: bz#1633930
    Change-Id: I8977e45add742e67047291f398f0ee79eb09afe4
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 6e92171117c73d7a8901800299446a131e54b597
Author: Harpreet Kaur <hlalwani@redhat.com>
Date:   Wed Nov 28 14:06:36 2018 +0530

    geo-rep: Make slave volume read-only (by default)
    
    Added a command to set "features.read-only" option
    to a default value "on" for slave volume.
    Changes are made in:
    $SRC//extras/hook-scripts/S56glusterd-geo-rep-create-post.sh
    for root geo-rep and
    $SRC/geo-replication/src/set_geo_rep_pem_keys.sh
    for non-root geo-rep.
    
    Fixes: bz#1654187
    
    Change-Id: I15beeae3506f3f6b1dcba0a5c50b6344fd468c7c
    Signed-off-by: Harpreet Kaur <hlalwani@redhat.com>

commit 916df2c12b19ac84b7806d31226d7f832ca7e2bb
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Dec 6 23:14:57 2018 +0530

    glusterd: fix get_mux_limit_per_process to read default value
    
    get_mux_limit_per_process () reads the global option dictionary and in
    case it doesn't find out a key, assumes that
    cluster.max-bricks-per-process option isn't configured however the
    default value should be picked up in such case.
    
    Change-Id: I35dd8da084adbf59793d58557e818d8e6c17f9f3
    Fixes: bz#1656951
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 9ee330aaf0831bc04e2ed72c05be0701571b5294
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Thu Dec 6 13:24:40 2018 +0530

    performance/readdir-ahead: update stats from prefetched dentries
    
    stats from prefetched dentries should be invalidated only if the
    files pointed to those dentries were written in the window of
    prefetching. Otherwise its safe to use these stats.
    
    Change-Id: I9ea5aeea4c75dfa03387fca32c626cb4e693290d
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Fixes: bz#1656348

commit 40a9e53a44e887658fade3f03afc018e82b941b9
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Dec 6 15:09:26 2018 +0530

    New xlator option to control enable/disable of xlators in Gd2
    
    Since glusterd2 don't maintain the xlator option details in code, it
    directly reads the xlators options table from `*.so` files. To support
    enable and disable of xlator new option added to the option table with
    the name same as xlator name itself.
    
    This change will not affect the functionality with glusterd1.
    
    Change-Id: I23d9e537f3f422de72ddb353484466d3519de0c1
    updates: #302
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit f168db1da76775f11026c922a51a718b54abc4c9
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Dec 6 22:02:28 2018 +0530

    cli: fix memory leak in cli rpc ops
    
    Problem: In some of the cli fops dict_allocate_and_serialize
             allocate memory for req structure but after submit
             request it missed to cleanup memory fo req.dict.dict_val
    
    Solution: Call GF_FREE for req.dict.dict_val after submit
              cli request
    
    Change-Id: I76c6b3082fa0be21dc595f87701550a318734ea5
    updates: bz#1633930
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 4bdabc49d034ab2b76e4861a6e10ae41deb86d5e
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Wed Dec 5 19:18:17 2018 +0530

    cli: fix a memory leak reported by ASan.
    
    Fixed a leak in cli_cmd_volume_remove_brick_cbk.
    SUMMARY: AddressSanitizer: 1152 byte(s) leaked in 8 allocation(s)
    
    updates: bz#1633930
    
    Credits: Mohit Agrawal
    Change-Id: Idb59c3880329fde59c415c84d7f0bb09ae879a1a
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 36e1175df6f404aad89b8a802d4f603ebaa3515b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 5 12:55:14 2018 +0530

    cli: Fix mem-leaks reported by ASAN
    
    Tracebacks:
    
    Direct leak of 96 byte(s) in 1 object(s) allocated from:
     #0 0x7f3acf9eac48 in malloc (/lib64/libasan.so.5+0xeec48)
     #1 0x7f3acf510949 in __gf_malloc ./libglusterfs/src/mem-pool.c:136
     #2 0x7f3acf5111bb in gf_vasprintf ./libglusterfs/src/mem-pool.c:236
     #3 0x7f3acf51138a in gf_asprintf ./libglusterfs/src/mem-pool.c:256
     #4 0x421611 in cli_cmd_volume_set_cbk ./cli/src/cli-cmd-volume.c:868
     #5 0x410599 in cli_cmd_process ./cli/src/cli-cmd.c:135
     #6 0x40f90d in cli_batch ./cli/src/input.c:29
     #7 0x7f3acd78c593 in start_thread pthread_create.c:463
    
    Direct leak of 73 byte(s) in 1 object(s) allocated from:
     #0 0x7f3acf9eac48 in malloc (/lib64/libasan.so.5+0xeec48)
     #1 0x7f3acf510949 in __gf_malloc ./libglusterfs/src/mem-pool.c:136
     #2 0x421519 in gf_strndup ../../libglusterfs/src/mem-pool.h:167
     #3 0x421519 in gf_strdup ../../libglusterfs/src/mem-pool.h:184
     #4 0x421519 in cli_cmd_volume_set_cbk cli/src/cli-cmd-volume.c:859
     #5 0x410599 in cli_cmd_process cli/src/cli-cmd.c:135
     #6 0x40f90d in cli_batch cli/src/input.c:29
     #7 0x7f3acd78c593 in start_thread pthread_create.c:463
    
    Change-Id: I3312751c1e3178672360a678fe15b1f7f1054b22
    updates: bz#1633930
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 340e58f9b3bcdfe4314da65e592dcd5c2daf6fd9
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Nov 28 10:05:39 2018 +0530

    all: add xlator_api to many translators
    
    Fixes: #164
    Change-Id: I93ad6f0232a1dc534df099059f69951e1339086f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 7ea5f438f60df9aa16027030f2b24f31bc07524b
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Tue Dec 4 19:27:27 2018 +0530

    cli: memory leak issue reported by asan
    
    This patch fixes dict leak in cli_cmd_volume_stop_cbk.
    SUMMARY: AddressSanitizer: 640 byte(s) leaked in 4 allocation(s)
    
    Credits: Mohit Agrawal
    Change-Id: If14983b8588e68d16d6bbb04b87e2f06fb97023d
    fixes: bz#1633930
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit 20ef211cfa5b5fcc437484a879fdc5d4c66bbaf5
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Nov 29 14:08:06 2018 -0500

    libglusterfs: Move devel headers under glusterfs directory
    
    libglusterfs devel package headers are referenced in code using
    include semantics for a program, this while it works can be better
    especially when dealing with out of tree xlator builds or in
    general out of tree devel package usage.
    
    Towards this, the following changes are done,
    - moved all devel headers under a glusterfs directory
    - Included these headers using system header notation <> in all
    code outside of libglusterfs
    - Included these headers using own program notation "" within
    libglusterfs
    
    This change although big, is just moving around the headers and
    making it correct when including these headers from other sources.
    
    This helps us correctly include libglusterfs includes without
    namespace conflicts.
    
    Change-Id: Id2a98854e671a7ee5d73be44da5ba1a74252423b
    Updates: bz#1193929
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit ad446dabb88439ba83e2092021b09894351e8e71
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Mon Dec 3 19:02:32 2018 +0800

    protocol/server: support server.all-squash
    
    We still use gnfs on our side, so do a little work to support
    server.all-squash. Just like server.root-squash, it's also a
    volume wide option. Also see bz#1285126
    
    $ gluster volume set <VOLNAME> server.all-squash on
    
    Note: If you enable server.root-squash and server.all-squash
    at the same time, only server.all-squash works. Please refer
    to following table
    
    +---------------+-----------------+---------------------------+
    |               |all_squash       | no_all_squash             |
    +-------------------------------------------------------------+
    |               |                 |anonuid/anongid for root   |
    |root_squash    |anonuid/anongid  |useruid/usergid for no-root|
    +-------------------------------------------------------------+
    |no_root_squash |anonuid/anongid  |useruid/usergid            |
    +-------------------------------------------------------------+
    
    Updates bz#1285126
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>
    Signed-off-by: Xue Chuanyu <xuechuanyu@cmss.chinamobile.com>
    Change-Id: Iea043318fe6e9a75fa92b396737985062a26b47e

commit 7f7716f8194e06754d0417f27bcc40638c9f9f83
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Dec 5 12:33:48 2018 +0530

    cli: fix memory leak in cli/src/cli-rpc-ops.c
    
    This Patch fixes memory leak reported by ASan.
    Leaks are in gf_cli_status_cbk as a result of allocatating memory
    using gf_asprintf in loop.
    
    SUMMARY: AddressSanitizer: 535 byte(s) leaked in 7 allocation(s).
    
    Change-Id: If2fd76c7c1ea6fc44baca295050800074f9d1323
    updates: bz#1633930
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit d4723bdd30f0955ca68fec8c01bc87229c6a24c0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Nov 20 12:32:32 2018 +0530

    glusterd: glusterd to regenerate volfiles when GD_OP_VERSION_MAX changes
    
    While glusterd has an infra to allow post install of spec to bring it up
    in the interim upgrade mode to allow all the volfiles to be regenerated
    with the latest executable, in container world the same methodology is
    not followed as container image always point to the specific gluster rpm
    and gluster rpm doesn't go through an upgrade process.
    
    This fix does the following:
    1. If glusterd.upgrade file doesn't exist, regenerate the volfiles
    2. If maximum-operating-version read from glusterd.upgrade doesn't match
    with GD_OP_VERSION_MAX, glusterd detects it to be a version where new
    options are introduced and regenerate the volfiles.
    
    Tests done:
    
    1. Bring up glusterd, check if glusterd.upgrade file has been created
    with GD_OP_VERSION_MAX value.
    2. Post 1, restart glusterd and check glusterd hasn't regenerated the
    volfiles as there's is no change in the GD_OP_VERSION_MAX vs the
    op_version read from the file.
    3. Bump up the GD_OP_VERSION_MAX in the code by 1 and post compilation
    restart glusterd where the volfiles should be again regenerated.
    
    Note: The old way of having volfiles regenerated during an rpm upgrade
    is kept as it is for now but eventually this can be sunset later.
    
    Change-Id: I75b49a1601c71e99f6a6bc360dd12dd03a96414b
    Fixes: bz#1651463
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit afc3006b46bf9d6eb05e39af68bcd81041761a9c
Author: Harpreet kaur <hlalwani@redhat.com>
Date:   Tue Dec 4 18:09:49 2018 +0530

    cli: memory leak issue reported by asan
    
    This patch fixes Indirect leaks in cli-cmd-volume.c
    Leaks are happening in cli_cmd_quota_cbk and
    cli_cmd_quota_handle_list_all.
    SUMMARY: AddressSanitizer: 1152 byte(s) leaked in 8 allocation(s)
    
    Updates: bz#1633930
    
    Change-Id: Ia6c0306e88bd81f74d1220303ead8095fbcf5623
    Signed-off-by: Harpreet kaur <hlalwani@redhat.com>

commit 382ad46bbcb79344285d5cb1fe3ce85f83317c44
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Dec 4 05:01:54 2018 -0500

    tests/geo-rep: Mask failure of geo-rep arbiter test
    
    Comment out the particular test which is failing
    arbitrarily. Also changed the code to differentiate
    error cases. There could be some race because of
    which it's failing arbitrarily. This will be debugged
    and fixed in separate patch.
    
    Change-Id: I925df6421737d7a9abd9446a9d85029b4285ad2c
    updates: bz#1193929
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 5a8a06bc9d84c188d18b60e4bf0a97963572f065
Author: Chris Holcombe <xfactor973@gmail.com>
Date:   Thu Nov 29 10:26:44 2018 -0800

    debug/io-stats: Fix json output
    
    Summary: The json being output by the io-stats debug xlator
    quotes the numbers. This is not necessary and makes parsing
    in strongly typed languages more difficult.
    
    Change-Id: I3ac13700e2c52dbdc29d0bcdd39896d7871f36fe
    fixes: bz#1654521
    Signed-off-by: Chris Holcombe <xfactor973@gmail.com>

commit 65dc176e7c3e3d598605b75f06b796fd0ade2c7e
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Fri Nov 30 22:01:53 2018 +0530

    rpc-transport/socket: NULL pointer dereferencing clang fix
    
    Problem: res->ai_addr could be NULL
    
    Added a check to address this issue
    
    Change-Id: Iac88a8d6dc1f009836554448afbc228df93decd6
    Updates: bz#1622665
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 785106e13864b84f35ca3394518d05d69a4e755f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Nov 25 11:22:30 2018 +0200

    xlators/mgmt/glusterd/src/glusterd-volgen.c: use dict_ new functions
    
    In a previous patch (https://review.gluster.org/20769) we've
    added the key length to be passed to dict_* funcs, to remove the need
    to strlen() it. This patches makes use of these functions over
    this whole file.
    
    Please review carefully, as there are many many changes there.
    
    Compile-tested only!
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I2e1ee340300ec330936c31becda6bfe1b6533281

commit 9c06057bae91440aabb1a1a69e5315b56454e1a2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Dec 5 10:52:30 2018 +0530

    tests: Mark tests/bugs/shard/zero-flag.t bad
    
    Change-Id: I2f4ca470c6666584e0feb129ab712f06772a86c2
    Updates: bz#1656264
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 239c67d49d0f9bec10212122513172e523b9abce
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Dec 4 19:19:58 2018 +0530

    glusterd: set cluster.max-bricks-per-process to 250
    
    Commit 6821cec changed this default from 0 to 250 in the option table,
    however the same wasn't done in the global option table.
    
    Change-Id: I6075f2ebc51e839510d6492fb62e706deb2d845b
    Fixes: bz#1652118
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 040a1dbcf6d954dc5965ead40d560a3107f2e3aa
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Nov 28 12:39:31 2018 +0530

    extras: Add group-distributed-virt for single-brick ovirt-gluster use-case
    
    Change-Id: I930011327332b7ba30cc76f614efaf5932eb4f3d
    fixes: bz#1654138
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit f80d9be732042477fc08ceb5873cd903002d7d1a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Nov 7 10:27:15 2018 +0200

    libglusterfs/src/iobuf.c: small refactor to re-use code.
    
    No functional changes (I hope).
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ifbec21c18a6dbe27c5271db156bff4d30ca85dbf

commit f479f4618923ca497d499dcaa533d19a2403e0b5
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Dec 4 00:18:42 2018 +0530

    cli: fix memory leak in cli-cmd-system.c
    
    This patch fixes memory leak reported by ASan.
    
    SUMMARY: AddressSanitizer: 384 byte(s) leaked in 2 allocation(s).
    
    updates: bz#1633930
    Change-Id: I93ebddcfeea3d51547e00775db2c9d99f5dfafea
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 82987486a9c9145caa6ce9ff31506ba2563a4a97
Author: Eli Schwartz <eschwartz@archlinux.org>
Date:   Tue Dec 4 11:38:48 2018 -0500

    configure.ac: fix option to stop automake aborting on pointless error
    
    glusterfs does not follow the GNU coding standards and therefore must
    use the "foreign" strictness. Without this, autoreconf -fi would fail to
    execute successfully because automake returned non-zero.
    
    This change ensures that people using autoreconf, the GNU preferred
    invocation method for the autotools build system, can successfully set
    up the build.
    
    Remove the pointless --foreign argument from the autogen.sh invocation
    of automake. Not only is configure.ac the preferred way to define such
    options (rather than handwritten, piecemeal invocations of every tool in
    the autotools toolchain), it was never needed in the autogen.sh as that
    script provides no error handling at all and always (incorrectly)
    returns successfully as long as autotools itself is installed (no matter
    how broken glusterfs itself is).
    
    Change-Id: Ib0246d5368a54594f517a322465cffb9a85c1b49
    fixes: bz#1656100
    Signed-off-by: Eli Schwartz <eschwartz@archlinux.org>

commit 9b770760d94b1fc39ade01df35dd3bcf317a71ed
Author: Milan Zink <mzink@redhat.com>
Date:   Tue Jan 16 13:48:49 2018 +0100

    Do not blindly add volume share section to smb.conf
    
    With this change, by default GlusterFS volume share section will
    no longer be added to smb.conf for client access unless user.cifs
    or user.smb volume set options are enabled. This also fixes the
    hook script to check for presence of all configuration possibilities
    for those volume set options like 'enable' or 'on'.
    
    Change-Id: Ibecf7fffb4507d7255d963c3b1482afb0d0db984
    Signed-off-by: Milan Zink <mzink@redhat.com>
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Fixes: bz#1575836

commit e48678567a5fb01166a065f9e192b80e721e4181
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Nov 8 18:50:18 2018 +0530

    glusterd: migrating profile commands to mgmt_v3 framework
    
    Current profile commands use the op_state machine framework.
    Porting it to use the mgmt_v3 framework.
    
    The following tests were performed on the patch:
    case 1:
    1. On a 3 node cluster, created and started 3 volumes
    2. Mounted all the three volumes and wrote some data
    3. Started profile operation for all the volumes
    4. Ran "gluster v status" from N1,
           "gluster v profile <volname1> info" form N2,
           "gluster v profile <volname2> info" from N3 simultaneously in a
       loop for around 10000 times
    5. Didn't find any cores generated.
    
    case 2:
    1. Repeat the steps 1,2 and 3 from case 1.
    2. Ran "gluster v status" from N1,
           "gluster v profile <volname1> info" form N2(terminal 1),
           "gluster v profile <volname2> info" from N2(terminal 2)
       simultaneously in a loop.
    3. No cores were generated.
    
    fixes: bz#1654181
    Change-Id: I83044cf5aee3970ef94066c89fcc41783ed468a6
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 8e8f4bf3fa16d3790a5eb74b8f07b904024ee9d8
Author: Harpreet Kaur Lalwani <hlalwani@redhat.com>
Date:   Wed Nov 21 16:13:36 2018 +0530

    cli: "usage()" and "--help" for gluster cli
    
    Added a usage message which will be shown when a user enters an
    "unrecognized word" or an "unrecognized command" on the cli.
    Also added a "--help" option for gluster cli.
    
    fixes: bz#1535495
    
    Change-Id: Ibcfb3d1c84daa1054e09c5cdfa6a5dab19f534a6
    Signed-off-by: Harpreet Kaur Lalwani <hlalwani@redhat.com>

commit 54ebd47e4154c8b37680b2bac43775fc92ced153
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sat Nov 17 13:14:24 2018 +0530

    geo-rep: Fix syncing of files with non-ascii filenames
    
    Problem:
      Creation of files/directories with non-ascii names fails
      to sync to the slave. It crashes with below traceback on
      slave.
      ...
      File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/repce.py", line 118, in worker
        res = getattr(self.obj, rmeth)(*in_data[2:])
      File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/resource.py", line 709, in entry_ops
        [ESTALE, EINVAL, EBUSY])
      File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/syncdutils.py", line 546, in errno_wrap
        return call(*arg)
      File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/libcxattr.py", line 83, in lsetxattr
        cls.raise_oserr()
      File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/libcxattr.py", line 38, in raise_oserr
        raise OSError(errn, os.strerror(errn))
      OSError: [Errno 12] Cannot allocate memory
    
    Cause:
      The length calculation arguments passed to blob creation was done before encoding. Hence
      was failing in gfid-access layer.
    
    Fix:
      It appears that the calculating lenght properly fixes this issue. But it will cause
      issues in other places in 'python2' and not in 'python3'. So encoding and decoding
      each required string to make geo-rep compatible with both 'python2' and 'python3'
      is a nightmare and is not fool proof. Hence kept 'python2' code as is with out
      encode/decode and applied encode/decode only to 'python3'
    
    Added non-ascii filename tests to regression
    
    fixes: bz#1650893
    Change-Id: I35cfaf848e07b1a0b5cb93c01b98b472f08271a6
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 748e993d1f30197c533933ddae889b317ccd00d3
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Nov 27 11:43:04 2018 +0530

    rpc: bump up server.event-threads
    
    Problem:
    A single event-thread causes performance issues in the system.
    
    Solution:
    Bump up event-threads to 2 to make the system more performant.
    This helps in making the system more responsive and helps avoid the
    ping-timer-expiry problem as well. However, setting the event-threads
    to 2 is not the only thing required to avoid ping-timer-expiry issues.
    
    Change-Id: Idb0fd49e078db3bd5085dd083b0cdc77b59ddb00
    fixes: bz#1653277
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit b3d88a0904131f6851f4185e43f815ecc3353ab5
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Nov 28 14:14:00 2018 +0530

    io-cache: xdata needs to be passed for readv operations
    
    io-cache xlator has been skipping xdata references when the
    date needs to be read into page cache. This patch fixes the same.
    
    Note: similar changes may be needed for other fops as well
    which are handled by io-cache.
    
    Change-Id: I28d73d4ba471d13eb55d0fd0b5197d222df77a2a
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 9fc6cf898bcb7dc0f3f671e734678616722d0721
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Dec 3 11:51:52 2018 -0500

    rpc: check if fini is there before calling it
    
    The rpc_transport_t structure is allocated and filled in the
    rpc_transport_load function. If filling the fileds of the rpc
    structure fails, then in the failure handling the structure is
    freed by rpc_transport_cleanup. There, it unconditionally calls
    fini. But, if the failure handling was invoked because of any
    failure in between the allocation of rpc_transport_t and filling
    the transport->fini (including the failure to fill fini ()), then
    rpc_transport_cleanup can lead to a segfault.
    
    Change-Id: I8be9b84cd6b19933c559c9736198a6e440373f68
    fixes: bz#1654917
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 2bb0e89e4bb113a93c6e786446a140cd99261af8
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Nov 28 16:13:58 2018 +0530

    glusterd: perform rcu_read_lock/unlock() under cleanup_lock mutex
    
    Problem: glusterd should not try to acquire locks on any resources,
    when it already received a SIGTERM and cleanup is started. Otherwise
    we might hit segfault, since the thread which is going through
    cleanup path will be freeing up the resouces and some other thread
    might be trying to acquire locks on freed resources.
    
    Solution: perform rcu_read_lock/unlock() under cleanup_lock mutex.
    
    fixes: bz#1654270
    Change-Id: I87a97cfe4f272f74f246d688660934638911ce54
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 220722b426f4014abdca0c719b2ca4e3aefeecc4
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Nov 30 17:46:59 2018 +0530

    cli : Memeory leak fix reported by ASAN
    
    This patch fixes memory leak in cli-rpc-ops.c.
    
    Functions: gf_cli_create_volume_cbk, gf_cli_delete_volume_cbk,
               gf_cli_start_volume_cbk, gf_cli_remove_tier_brick_cbk,
               gf_cli_list_volume_cbk.
    
    updates: bz#1633930
    
    Change-Id: I68a650fb972db18c90e6581a960eae3018f32d40
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 46c15ea8fa98bb3d92580b192f03863c2e2a2d9c
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Nov 29 19:55:39 2018 +0530

    server: Resolve memory leak path in server_init
    
    Problem: 1) server_init does not cleanup allocate resources
                while it is failed before return error
             2) dict leak at the time of graph destroying
    
    Solution: 1) free resources in case of server_init is failed
              2) Take dict_ref of graph xlator before destroying
                 the graph to avoid leak
    
    Change-Id: I9e31e156b9ed6bebe622745a8be0e470774e3d15
    fixes: bz#1654917
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit f77fb6d568616592ab25501c402c140d15235ca9
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Nov 29 12:04:45 2018 -0500

    features/bitrot: compare the signature with proper length
    
    * The scrubber was comparing the checksum of the file that it
      calculated (by reading the file) with the on disk signature
      (stored via xattr) wrongly. It was using strlen to calculate
      the signature, while the actual length of the signature is
      given by the brick. Just use the actual length that the brick
      provides instead of trying to calculate the signature length via
      strlen API.
    
    * In posix, gfid2path was using the same string that contains the
      list of all the xattrs of file to save the value of the gfid2path
      xattr as well. This causes confusion when gfid2path xattr is queried
      by scrubber for getting the actual path of a corrupted file. Use
      separate string to fetch the value of the xattr instead of the string
      that contains the list of xattrs.
    
    Change-Id: I2d664ab524d2b312233476cb35863dde3122e9a9
    fixes: bz#1654805
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 4d58730c0cd6ab5db39aec8a15276f7bd3371b04
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Sep 28 17:00:00 2018 +0530

    afr: assign gfid during name heal when no 'source' is present.
    
    Problem:
    If parent dir is in split-brain or has dirty xattrs set, and the file
    has gfid missing on one of the bricks, then name heal won't assign the
    gfid.
    
    Fix:
    Use the brick we select the gfid from as the 'source'.
    
    Note: Problem was found while trying to debug a split-brain issue on
    Cynthia Zhou's setup.
    
    updates: bz#1637249
    Change-Id: Id088d4f0fb017aa35122de426654194e581ed742
    Reported-by: Cynthia Zhou <cynthia.zhou@nokia-sbell.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 4364093869f59ed2af3f7d10d5a72df490eac9a9
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Nov 20 14:11:08 2018 +0530

    doc: Add brick mux thread reduction design doc in developer guide
    
    Change-Id: I5309efb5826d4385eadea29c1cf973f504eef9e5
    Updates: #475
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 080aa5b9e9d998552e23f7c33aed3afb0ca93c34
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Nov 28 12:45:41 2018 +0530

    leases: Do not conflict with internal fops
    
    Internal fops (with frame->root->pid < 0) are used to heal
    or move data and maintains data integrity. That is they do not
    modify client data which holds the lease. Hence no need to recall
    Lease for such fops.
    
    Note: Like for locks, we would need rebalance and self-heal
    daemon process to heal lease state as well.
    
    Change-Id: I8988693fef8d00e17c19dcc842e2238f9eb5ab48
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit b56bf714c1f22212700db50c057e4e47b99be739
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Nov 23 12:14:59 2018 +0200

    rpc *.h fles: align structs
    
    Make an effort to slightly better align the structures.
    
    Change-Id: I6f80a451f2ffbf15adfb986cedc24c2799787b49
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 99c72652f81ca5ea212adbb5a555e12a4de94491
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Nov 29 19:22:40 2018 +0530

    nfs : set ctx for every inode looked up nfs3_fh_resolve_inode_lookup_cbk()
    
    The inode ctx for nfs xlator is set with help nfs_fix_generation.
    But currently gnfs is crashing because inode_ctx is becoming null
    nfs3_resolve_inode_hard() is used to perform a lookup on entire
    path and looks like function is missing to set the ctx for inode.
    This patch will set ctx for the inode which it looked on.
    
    Change-Id: I464fa7f78df1bae990ebe97de8ccf6d5fb74fc9f
    fixes: bz#1651439
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 7c0cb6eebd37ced16bb3b4410404be12e8c892b5
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Mon Oct 15 12:41:17 2018 +0530

    cli: memory leak issue reported by asan
    
    This patch fixes Indirect leaks in tests/bugs/heal-symlinks.t.
    Leaks are happening in cli_cmd_volume_heal_cbk.
    SUMMARY: AddressSanitizer: 640 byte(s) leaked in 4 allocation(s).
    
    Updates: bz#1633930
    
    Change-Id: I970b4229630fdaf01aec66581c1287beef7560a3
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit 0b54c92a22c89fd1d8e03cad2dfb70a5b73ee12a
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Nov 30 11:58:57 2018 -0500

    clang: Fix io-stats.c NULL pointer issue reported by clang
    
    The issue pertains to checking if conf is NULL in BUMP_FOP
    but not providing that safety in io_stats_release when using
    conf to lock and bump nr_opens.
    
    This is now corrected to check if conf is non-NULL before
    attempting the lock and bump nr_opens.
    
    Tested with local clang analyzer to ensure this fixes the
    problem.
    
    Change-Id: Iffd6a97c2060d0a6930a8dc5914b1956c192cab1
    Updates: bz#1622665
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 0566ecc878adc5a5aba2c3210485087a9a67da59
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Nov 30 16:39:32 2018 +0530

    cli : Memeory leak fix reported by ASAN
    
    This patch fixes memory leak in cli-rpc-ops.c.
    All leaks are happening in gf_cli_remove_brick_cbk.
    
    SUMMARY: AddressSanitizer: 2944 byte(s) leaked in 22 allocation(s).
    
    updates: bz#1633930
    
    Change-Id: I1e58d538eb9135f1aadcdb54d10b72f55e8a53d1
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 98a672f5046620f5fc751ea803e0dfa0bf4e18d3
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Nov 29 22:27:59 2018 +0200

    Multiple xlator .h files: remove unused private gf_* memory types.
    
    It seems there were quite a few unused enums (that in turn
    cause unndeeded memory allocation) in some xlators.
    I've removed them, hopefully not causing any damage.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I8252bd763dc1506e2d922496d896cd2fc0886ea7

commit e74d997f0d7eeb91fe6b5f0f0c3969bf4ac53f9f
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Nov 29 15:37:23 2018 -0500

    clang: Fix clang warnings in snapview-server.c
    
    The warning by clang is due to the fact that we check for
    frame->root to be NULL, but in stack unwind, we ignore the
    same.
    
    If frame is non-NULL then frame->root is non-NULL as frame
    creation ensures this. Further, across the code we do not
    check both frame and frame->root for validity.
    
    Hence to fix these clang issues, removing the check for
    frame->root in the various functions.
    
    NOTE: Initially clang reported 14 issues in the file, but
    post commit 6eabefe6 the number reduced to 4, unsure why as
    that commit does not address this issue.
    
    Change-Id: I04b63f2d006a1f95773aae9f904b4bd3d5118e62
    Updates: bz#1622665
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 95e380eca19b9f0d03a53429535f15556e5724ad
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Wed Oct 31 16:10:58 2018 +0530

    rpcsvc: provide each request handler thread its own queue
    
    A single global per program queue is contended by all request handler
    threads and event threads. This can lead to high contention. So,
    reduce the contention by providing each request handler thread its own
    private queue.
    
    Thanks to "Manoj Pillai"<mpillai@redhat.com> for the idea of pairing a
    single queue with a fixed request-handler-thread and event-thread,
    which brought down the performance regression due to overhead of
    queuing significantly.
    
    Thanks to "Xavi Hernandez"<xhernandez@redhat.com> for discussion on
    how to communicate the event-thread death to request-handler-thread.
    
    Thanks to "Karan Sandha"<ksandha@redhat.com> for voluntarily running
    the perf benchmarks to qualify that performance regression introduced
    by ping-timer-fixes is fixed with this patch and patiently running
    many iterations of regression tests while RCAing the issue.
    
    Thanks to "Milind Changire"<mchangir@redhat.com> for patiently running
    the many iterations of perf benchmarking tests while RCAing the
    regression caused by ping-timer-expiry fixes.
    
    Change-Id: I578c3fc67713f4234bd3abbec5d3fbba19059ea5
    Fixes: bz#1644629
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>

commit f0232d07f7e6543b56830be28f6e80f9085e6241
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Nov 27 11:19:59 2018 -0500

    core: ctx calls naked calloc()
    
    liblglusterfs provides wrapper functions MALLOC/__gf_default_malloc,
    CALLOC/__gf_default_calloc, and REALLOC/__gf_default_realloc for those
    few places outside of mempool.c that need to call malloc/calloc/realloc
    directly.
    
    Notable exceptions are "contrib" code, e.g. rbtree and timer-wheel,
    and perhaps parsers generated by yacc+lex. But even parsers can be
    fixed to at least call the wrappers mentioned above, if not our own
    allocators.
    
    Change-Id: Ib8069815eba9b6c04c3adaf59727ec8d8795c4d1
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 18b6d7ce7d490e807815270918a17a4b392a829d
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Fri Nov 16 16:27:17 2018 +0530

    libglusterfs: rename macros roof and floor to not conflict with math.h
    
    Change-Id: I666eeb63ebd000711b3f793b948d4e0c04b1a242
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Updates: bz#1644629

commit 9f9f46ff2d30ff87a6a4f8c2af491ea1aa92fbb2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Nov 27 14:24:15 2018 -0500

    glusterd: volume-ops calls naked malloc
    
    libglusterfs provides wrapper functions MALLOC/__gf_default_malloc,
    CALLOC/__gf_default_calloc, and REALLOC/__gf_default_realloc for those
    few places outside of mempool.c that need to call malloc/calloc/realloc
    directly.
    
    Notable exceptions are "contrib" code, e.g. rbtree and timer-wheel,
    and perhaps parsers generated by yacc+lex. But even parsers can be
    fixed to at least call the wrappers mentioned above, if not our own
    allocators
    
    Change-Id: Ie6156307b6d2183be9c9aff153afb7598974f4e4
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 3566903e03f90e262483a5d53a6c85f0b16ece3a
Author: Harpreet Kaur <hlalwani@redhat.com>
Date:   Tue Nov 27 12:17:38 2018 +0530

    tests/geo-rep: Add Arbiter volume test case
    
    Added geo-rep regression tests with Arbiter volume.
    
    Fixes: bz#1653565
    
    Change-Id: Id99523c1f1d3d301fbe871aa0641d9ae4ed7b8d7
    Signed-off-by: Harpreet Kaur <hlalwani@redhat.com>

commit bbf1b9090b6b51292afab4af4479ef2d4ca61265
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Nov 25 11:01:01 2018 +0530

    posix: fix memory leak
    
    Direct leak of 609960 byte(s) in 4485 object(s) allocated from:
        #0 0x7f0d719bea50 in __interceptor_calloc (/lib64/libasan.so.5+0xefa50)
        #1 0x7f0d716dc08f in __gf_calloc ../../../libglusterfs/src/mem-pool.c:111
        #2 0x7f0d5d41d9b2 in __posix_get_mdata_xattr ../../../../../xlators/storage/posix/src/posix-metadata.c:240
        #3 0x7f0d5d41dd6b in posix_get_mdata_xattr ../../../../../xlators/storage/posix/src/posix-metadata.c:317
        #4 0x7f0d5d39e855 in posix_fdstat ../../../../../xlators/storage/posix/src/posix-helpers.c:685
        #5 0x7f0d5d3d65ec in posix_create ../../../../../xlators/storage/posix/src/posix-entry-ops.c:2173
    
    Direct leak of 609960 byte(s) in 4485 object(s) allocated from:
        #0 0x7f0d719bea50 in __interceptor_calloc (/lib64/libasan.so.5+0xefa50)
        #1 0x7f0d716dc08f in __gf_calloc ../../../libglusterfs/src/mem-pool.c:111
        #2 0x7f0d5d41ced2 in posix_set_mdata_xattr ../../../../../xlators/storage/posix/src/posix-metadata.c:359
        #3 0x7f0d5d41e70f in posix_set_ctime ../../../../../xlators/storage/posix/src/posix-metadata.c:616
        #4 0x7f0d5d3d662c in posix_create ../../../../../xlators/storage/posix/src/posix-entry-ops.c:2181
    
    We were freeing only the first context in inode during forget, and not the second.
    
    updates: bz#1633930
    Change-Id: Ib61b4453aa3d2039d6ce660f52ef45390539b9db
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 6d69a663497ba2bb90b42eae8384cc57d6e4b283
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue Nov 27 12:21:01 2018 +0100

    mem-pool: minor fix and clarification
    
    A comment has been added to pool_destructor() function to explain why
    locks are not needed there. Also, the initialization of 'poison' field
    has been moved inside a locked region for further safety and clarity.
    
    Change-Id: Idbf23bda7f9228d60c644a1bea4b6c2cfc582090
    updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 0a3540293bf2f4e96d79ca0d1baa168712472279
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Fri Nov 23 17:28:07 2018 +0530

    geo-rep: Geo-rep help text issue
    
    Modified Geo-rep help text for better sanity.
    
    Change-Id: I48f4d0fd60c1ffcde753b37416e0c73afd0b5702
    fixes: bz#1652887
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit a52d2d704318a930b0a2eb6d92701499fa97e52e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Nov 22 09:58:52 2018 +0530

    glusterd: perform store operation in cleanup lock
    
    All glusterd store operation and cleanup thread should work under a
    critical section to avoid any partial store write.
    
    Change-Id: I4f12e738f597a1f925c87ea2f42565dcf9ecdb9d
    Fixes: bz#1652430
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit c7eb1883bea6e72a72908b2e2966d4893d47db16
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Nov 23 12:23:05 2018 +0530

    glusterd : fix high sev coverity issue
    
    This patch fixes CID : 1174824 : RESOURCE_LEAK
    
    Change-Id: I59d2d6ebc1fa3d7ebe0b97c7dbe3c5539128522a
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 01f3358501672e7c0fa8ae1f749f060af29bcd69
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Nov 25 12:04:50 2018 +0200

    libglusterfs/src/dict.c : consistent initialization of parameters.
    
    Some were assigned NULL, for no good reason, some were assigned proper
    initial value. Made them all consistent, as much as possible, to be
    assigned reasonable initial values.
    No expected functional changes (and I also assume the compiler
    already did most of this work behind the scenes anyway, so no
    performance implications either).
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I2bc0d4f2221124b5f9ef6150c86b7259074e7013

commit b2a50989822c135c2e4cb84ad7ad400957a49d10
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Nov 13 12:53:17 2018 +0100

    build: add option to compile with ThreadSanitizer
    
    ThreadSanitizer is a debugging tool that can detect threads that race
    for data modifications. These races can result in data corruption and
    are difficult to track and fix.
    
    Change-Id: Ibbdaf17c811e30e79cd5bdcf9cd9ff2d0cdb2abb
    URL: https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual
    Reported-by: Yaniv Kaul <ykaul@redhat.com>
    Fixes: #543
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit fc9889d0373c323aab0d93f8ca31d2d8151bd041
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Oct 26 17:51:38 2018 +0530

    glfsheal: add a '--nolog' flag
    
    ....and if set, change the log level to GF_LOG_NONE. This is useful for
    monitoring applications which invoke the heal info set of commands once
    every minute, leading to un-necessary glfsheal* logs in
    /var/log/glusterfs/. For example, we can now run
    
    `gluster volume heal <VOLNAME> info --nolog`
    `gluster volume heal <VOLNAME> info split-brain --nolog` etc.
    
    The default log level is still retained at GF_LOG_INFO.
    
    The patch also changes glfsheal internally to accept '--xml' instead of 'xml'.
    Note: The --nolog flag is *not* displayed in the help anywhere, for the
    sake of consistency in how the other flags are not displayed anywhere in
    the help.
    
    fixes: bz#1643519
    Change-Id: Ia08b6aa6e4a0548379db7e313dd4411ebc66f206
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit b346c84ad5f090c3d99dc1cb80f24ca10747a085
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Aug 31 14:20:23 2018 +0530

    cluster/afr: Add test for thin-arbiter feature
    
    Test : Check success/failure of write fop while
    different bricks/ta process are down.
    
    Change-Id: I3c376935df93ebf1f794c964bd19bc1280d91c59
    updates: bz#1624332
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit a2829d1151cabd13764e271a07568b9c90261a76
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Aug 3 17:43:28 2018 +0530

    coding-standard: memset before string functions similar to sprintf/snprintf etc
    
    String functions like sprintf/snprintf/vprintf etc terminates the string with a
    null character. This makes meset redundant and also incurs some performance
    penalty.
    
    Also added a comment about using GF_MALLOC instead of GF_CALLOC for allocating
    buffer for strings, targeted by such functions.
    
    Fixes: bz#1193929
    Change-Id: I4f40d4fd5342b70983936119606c6c9f352c303c
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit c97938e0508d991f44fd6a02216ecae120bfcac8
Author: root <Shwetha Acharya>
Date:   Fri Nov 23 19:30:01 2018 +0530

    geo-rep: add no-verify and ssh-port options for create command
    
    Added the missing options and their description.
    
    fixes: bz#1652911
    Change-Id: Id9135953bc6d32e645f004e1c77449899ca3d67c
    Signed-off-by: root <Shwetha Acharya>

commit 31f85a4c7b20d9e594109f933f97127ba43029a8
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Nov 7 18:54:23 2018 +0100

    libglusterfs: fix memory corruption caused by per-thread mem pools
    
    There was a race in the per-thread memory pool management that could lead
    to memory corruption. The race appeared when the following sequence of
    events happened:
    
    1. Thread T1 allocated a memory object O1 from its own private pool P1
    2. T1 terminates and P1 is marked to be destroyed
    3. The mem-sweeper thread is woken up and scans all private pools
    4. It detects that P1 needs to be destroyed and starts releasing the
       objects from hot and cold lists.
    5. Thread T2 releases O1
    6. O1 is added to the hot list of P1
    
    The problem happens because steps 4 and 6 are protected by diferent locks,
    so they can run concurrently. This means that both T1 and T2 are modifying
    the same list at the same time, potentially causing corruption.
    
    This patch fixes the problem using the following approach:
    
    1. When an object is released, it's only returned to the hot list of the
       corresponding memory pool if it's not marked to be destroyed. Otherwise
       the memory is released to the system.
    2. Object release and mem-sweeper thread synchronize access to the deletion
       mark of the memory pool to prevent simultaneous access to the list.
    
    Some other minor adjustments are made to reduce the lengths of the locked
    regions.
    
    Fixes: bz#1651165
    Change-Id: I63be3893f92096e57f54a6150e0461340084ddde
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit b2776b1ec1ad845ba568c4439bca3b57cc4d2592
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Nov 20 12:36:55 2018 +0530

    geo-rep: Fix permissions with non-root setup
    
    Problem:
    In non-root fail-over/fail-back(FO/FB), when slave is
    promoted as master, the session goes to 'Faulty'
    
    Cause:
    The command 'gluster-mountbroker <mountbroker-root> <group>'
    is run as a pre-requisite on slave in non-root setup.
    It modifies the permission and group of following required
    directories and files recursively
    
      [1] /var/lib/glusterd/geo-replication
      [2] /var/log/glusterfs/geo-replication-slaves
    
    In a normal setup, this is executed on slave node and hence
    doing it recursively is not an issue on [1]. But when original
    master becomes slave in non-root during FO/FB, it contains
    ssh public keys and modifying permissions on them causes
    geo-rep to fail with incorrect permissions.
    
    Fix:
    Don't do permission change recursively. Fix permissions for
    required files.
    
    fixes: bz#1651498
    Change-Id: I68a744644842e3b00abc26c95c06f123aa78361d
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit ad35193718a99494ab1b852ca4cbdf054f73de88
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Sun Nov 18 23:38:08 2018 +0530

    gfapi: Offload callback notifications to synctask
    
    Upcall notifications are received from server via epoll
    and same thread is used to forward these notifications
    to the application. This may lead to deadlock and hang
    in the following scenario.
    
    Consider if as part of handling these callbacks,
    application has to do some operations which involve
    sending I/Os to gfapi stack which inturn have to wait for
    epoll threads to receive repsonse. Thus this may lead to
    deadlock if all the epoll threads are waiting to complete
    these callback notifications.
    
    To address it, instead of using epoll thread itself,
    make use of synctask to send those notificaitons to the
    application.
    
    Change-Id: If614e0d09246e4279b9d1f40d883a32a39c8fd90
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 0967f3dd0d73263c843d76e1837aa78c3fbf14c1
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Nov 23 11:31:38 2018 +0530

    coverity: Fix coverity issues
    
    This patch fixes coverity
    CID : 1356537
      https://scan6.coverity.com/reports.htm#v42907/p10714/fileInstanceId=87389108&defectInstanceId=26791927&mergedDefectId=1356537
    CID : 1395666
      https://scan6.coverity.com/reports.htm#v42907/p10714/fileInstanceId=87389187&defectInstanceId=26791932&mergedDefectId=1395666
    CID : 1351707
      https://scan6.coverity.com/reports.htm#v42907/p10714/fileInstanceId=87389027&defectInstanceId=26791973&mergedDefectId=1351707
    CID : 1396910
      https://scan6.coverity.com/reports.htm#v42907/p10714/fileInstanceId=87389027&defectInstanceId=26791973&mergedDefectId=13596910
    
    Change-Id: I8094981a741f4d61b083c05a98df23dcf5b022a2
    updates: bz#789278
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 6821cec47e2b7d37b1cda90a89bff12b2ac026ec
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Nov 21 07:49:07 2018 +0530

    glusterd: make max-bricks-per-process default value to 250
    
    Change-Id: Ia2c6a10e2b76a4aa8bd4ea97e5ce33bdc813942e
    Fixes: bz#1652118
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 2097f5ef15c809ed4d8465c9fb26916c6d661bce
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Nov 19 15:13:02 2018 +0530

    glusterd: volume status should not show NFS daemon
    
    With commit 8ad159b2a7, bz#1511339 got reintroduced.
    
    fixes: bz#1511339
    
    Change-Id: I1e34c1fc60c6dda04af25d123f1ca40964cadb7a
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 988bbd966d4332f5b1074aea7e5467a6399bac83
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Nov 23 12:38:44 2018 +0530

    meta/coverity: Fix coverity in meta xlator
    
    CID : 1356536 Macro compares unsigned to 0
      https://scan6.coverity.com/reports.htm#v42907/p10714/fileInstanceId=87389645&defectInstanceId=26791929&mergedDefectId=1356536
    CID : 1356535 Macro compares unsigned to 0
      https://scan6.coverity.com/reports.htm#v42907/p10714/fileInstanceId=87389645&defectInstanceId=26791926&mergedDefectId=1356535
    
    Change-Id: Icb1c9035589fa871c7223f767adbe0dfa672a9b4
    updates: bz#789278
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 424978302c7d5d0e03e54a6284c250e951ca694d
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Nov 22 21:41:37 2018 +0530

    Coverity fix for calling risky function - fscanf
    
    fscanf with %s reads a word, there is no restriction on the length
    of that word, and the caller is required to pass a sufficiently
    large buffer for storing thw word. If the input word exceeds the
    buffer size, it will cause buffer overflow.
    
    To fix this, use fscanf with width parameter. Width specifies
    the maximum number of characters to be read in the current reading
    operation.
    
    Change-Id: If250abf5eb637b9fc2a79047e3599f83254cd4e5
    updates: bz#1193929
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit a0fdc9202ca37dccab937e166c8ee696d049e08f
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Nov 23 10:37:40 2018 +0100

    core: create a constant for default network timeout
    
    A new constant named GF_NETWORK_TIMEOUT has been defined and all
    references to the hard-coded timeout of 42 seconds have been
    replaced with this constant.
    
    Change-Id: Id30f5ce4f1230f9288d9e300538624bcf1a6da27
    fixes: bz#1652852
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 7e691da0d37745e12d2f3e132545db82f05ea8f6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 16 11:18:27 2018 +0530

    features/changelog: Fix dictionary-leak
    
    rpcsvc_transport_unix_options_build() allocates the dictionary and sets
    it in the options variable, there is no need to allocate it before passing
    to the function in changelog_rpc_server_init()
    
    updates bz#1650403
    Change-Id: I5b4caedba6bda706dee723a2be34c3981bf971fb
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit c0983c3532e2da04c8c8f63df2717c154e0724db
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Nov 21 11:45:23 2018 +0530

    dht: fix buffer overflow
    
    CID: 1382461
    
    Change-Id: I25b5edf7fd5fdaa52079d0348ebb7f5de9f11503
    updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit da81c9938ec77401738999cf52ebf2fef695ba4d
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Nov 22 09:56:55 2018 +0530

    rpc: stop log flooding about ENODATA
    
    Problem:
    Logs are being flooded with ENODATA errors.
    This log was introduced via https://review.gluster.org/c/glusterfs/+/21481
    
    Solution:
    Add a flag to remember that ENODATA error was logged for a
    socket/transport
    
    Change-Id: I54c10b87e46c2592339cc8b966333b8d08331750
    fixes: bz#1650389
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 12285e76e8f93ef6f6aa2611869bd1f40955dc9e
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Nov 21 19:02:42 2018 +0530

    core: Resolve memory leak at the time of graph init
    
    Problem: In the commit 751b14f2bfd40e08ad395ccd98c6eb0a41ac4e91
             one code path is missed to avoid leak at the time
             of calling graph init
    
    Solution: Before destroying graph call xlator fini to avoid leak for
              server-side xlators those call init during graph init
    
    Credit: Pranith Kumar Karampuri
    fixes: bz#1651431
    
    Change-Id: I6e7cff0d792ab9d954524b28667e94f2d9ec19a2
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 429843eb9e3685d11479c58b8bc6416889a01ee3
Author: Shwetha Acharya <sacharya@gmail.com>
Date:   Wed Nov 21 12:24:00 2018 +0530

    geo-rep: validate the config checkpoint date format
    
    Added a strlen check to ensure that the format is (Y-m-d H:M:S).
    
    Change-Id: I8844aaa33418d43ffe2320c4a05eb1eddd306903
    updates: bz#1651584
    Signed-off-by: Shwetha Acharya <sacharya@gmail.com>

commit ada43dc22d158dcc8998bb35497f885951b52159
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Thu Nov 15 15:24:22 2018 +0530

    protocol/client: unchecked return value
    
    Problem: In client_process_response_v2, value returned from
    function client_post_common_dict is not checked for errors
    before being used.
    
    Solution: Added a check condition to resolve the issue.
    
    CID: 1390020
    
    Change-Id: I4d297f33c8dd332ae5f6f21667a4871133b2b570
    updates: bz#789278
    Signed-off-by: Shwetha Acharya <sacharya@redhat.com>

commit 650b5c5271abeb0eef59ac1ebb0ea3c8c37023ab
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Oct 31 16:31:35 2018 -0400

    snapview-server: close the gfapi handle present in a forgotten inode
    
    Currently, the snapdaemon can reach the lru limit of the inode table
    and start sending forgets on the inodes that are least recently used.
    snapview-server maintains the mapping between the domain of the
    snapdaemon and the gfapi instance which it uses to access the snapshots
    via a handle that is stored in the inode context of snapdaemon's inode.
    The handle is glfs_h_object structure which itself points to the actual
    inode present in the gfapi world.
    
    But, when snapview-server receives forget on a inode, it deleted the
    inode context without actually closing the handle it had obtained to
    map the inode from snapdaemon to the inode in gfapi world.
    
    So, this change makes sure that, the handle is closed as part of the
    inode forget. And this closure of the handle will result in gfapi
    world receiving forget and unref on its corresponding inode. But
    care must be taken to ensure before the closure to ensure that
    the gfapi instance from which the handle came from, is still valid
    and not destroyed. Otherwise, sending a forget downward to the gfapi
    world might result in the access of freed pointers. Hence, the
    snapview-server xlator first checks whether that gfapi instance is
    still there or not and then proceeds with closure of the handle.
    
    Change-Id: Ia7bb45112d0c651cc95f2e54d33d925dbd6955b0
    fixes: bz#1646728
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 751b14f2bfd40e08ad395ccd98c6eb0a41ac4e91
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Nov 16 09:25:02 2018 +0530

    core: Resolve memory leak at the time of graph init
    
    Problem: Memory leak when graph init fails as during volfile
             exchange between brick and glusterd
    
    Solution: Fix the error code path in glusterfs_graph_init
    
    Change-Id: If62bee61283fccb7fd60abc6ea217cfac12358fa
    fixes: bz#1651431
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit fbfceb9f2ee240737b329de8aa5b13562f99fddb
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Tue Oct 23 14:18:40 2018 +0530

    glusterfsd: NULL pointer dereferencing clang fix
    
    Added a check to avoid clang warning
    
    Updates: bz#1622665
    
    Change-Id: If9ae4e4f2ae13c85dad0e87d8dd6930dde74bbda
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit 4e0fab473a4ef8792e332efc83456bf63b540435
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Mon Nov 19 10:26:54 2018 +0530

    core: Retrieving the value of "client.ssl" option, before SSL is set up, fails
    
    Added a default value "off" for (client|server).ssl
    
    fixes: bz#1651059
    Change-Id: I3d9c80093ac471d9d770fbd6c67f945491cf726e
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 5231d3d165135f7aae8716069c67788555332136
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Nov 16 12:32:22 2018 +0200

    libglusterfs/src/common-utils.h: faster mem_0filled() function
    
    based on the amusing discussion @ https://rusty.ozlabs.org/?p=560
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I1cac54067eb44801b216d5620fc5ee2c89befdd0

commit bdf8d8684fa4814cf055350db38f53618c5de6ae
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Nov 16 12:46:49 2018 -0500

    core: fix strncpy, coverity annotation
    
    For added fun, coverity is not smart enough to detect that the
    strncpy() is safe, and for extra laughs, using coverity annotations
    doesn't do anything either; but we're adding them anyway, along
    with marking the BUFFER_SIZE_WARNINGS as false positives on
    scan.coverity.com.
    
    Change-Id: If7fa157eca565842109f32fee0399ac183b19ec7
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 60689bd26f0c9cb9e761f2cf8c5f2b90e39884eb
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Nov 16 11:25:16 2018 +0530

    features/locks: Move logging outside of a locked region
    
    In pl_metalk(), logging was being done in a synchronized region.
    Moving the log out of the synchronized region to avoid other threads
    from being blocked on the lock.
    
    Thanks to Yaniv Kaul for pointing this out.
    
    Change-Id: I0cb39fb23ae7c798ca9c42c390500491aa8e622b
    updates: bz#1644758
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 5664c58089127ba5214a7d922eed1aa1b4932402
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Nov 9 17:06:22 2018 +0530

    cluster/dht: sync brick root perms on add brick
    
    If a single brick is added to the volume and the
    newly added brick is the first to respond to a
    dht_revalidate call, its stbuf will not be merged
    into local->stbuf as the brick does not yet have
    a layout. The is_permission_different check therefore
    fails to detect that an attr heal is required as it
    only considers the stbuf values from existing bricks.
    To fix this, merge all stbuf values into local->stbuf
    and use local->prebuf to store the correct directory
    attributes.
    
    Change-Id: Ic9e8b04a1ab9ed1248b6b056e3450bbafe32e1bc
    fixes: bz#1648298
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 5af9799ab7c6185a852c48ef6b8655d294a50d2d
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Aug 30 14:48:51 2018 +0530

    cli : fix coverity issue in cli-xml-output.c
    
    This patch fixes 1124659, 1241480 and 1274196.
    
    Change-Id: Ib89f53b8e34fcc47184d08ad57f2ee32fd00d78c
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit b4faa9e7a25bdf0582f8b0fd69aa1381c307a61e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Nov 15 13:18:36 2018 +0530

    glusterd/mux: Optimize brick disconnect handler code
    
    Removed unnecessary iteration during brick disconnect
    handler when multiplex is enabled.
    
    Change-Id: I62dd3337b7e7da085da5d76aaae206e0b0edff9f
    fixes: bz#1650115
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit c2e758b54d8a3f778e3e63db0000bb8b63de9b25
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Oct 29 14:41:26 2018 +0530

    lease: Treat unlk request as noop if lease not found
    
    When the glusterfs server recalls the lease, it expects
    client to flush data and unlock the lease. If not it sets
    a timer (starting from the time it sends RECALL request) and post
    timeout, it revokes it.
    
    Here we could have a race where in client did send UNLK
    lease request but because of network delay it may have reached
    after server revokes it. To handle such situations, treat
    such requests as noop and return sucesss.
    
    Change-Id: I166402d10273f4f115ff04030ecbc14676a01663
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit b7aec05aa965202ab73120acf0da4c32fe0cf16c
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Sun Nov 11 22:53:07 2018 +0530

    leases: Fix incorrect inode_ref/unrefs
    
    From testing & code-reading, found couple of places where
    we incorrectly unref the inode resulting in use_after_free
    crash or ref leaks. This patch addresses couple of them.
    
    a) When we try to grant the very first lease for a inode,
    inode_ref is taken in __add_lease. This ref should be active
    till all the leases granted to that inode are released (i.e,
    till lease_cnt > 0). In addition even after lease_cnt becomes '0',
    the inode should be active till all the blocked fops are resumed.
    
    Hence release this ref, after resuming all those fops. To avoid
    granting new leases while resuming those fops, defined a new boolean
    (blocked_fops_resuming) to flag it in the lease_ctx.
    
    b) 'new_lease_inode' which creates new lease_inode_entry and
    takes ref on inode, is used while adding that entry to
    client_list and recall_list.
    
    Use its counter function '__destroy_lease_inode' which does unref
    while removing those entries from those lists.
    
    c) inode ref is also taken when added to timer->data. Unref the same
    after processing timer->data.
    
    Change-Id: Ie77c78ff4a971e0d9a66178597fb34faf39205fb
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 04be5463b20ababc29942fa967017e763d0ae2af
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Sat Nov 10 05:55:29 2018 -0500

    gfapi: Send fop_attr dict as part of syncop_open
    
    Leaseid (stored in thread locals) is sent to server via xdata.
    This dict variable is set but not passed as argument in glfs_h_open().
    Fixed the same.
    
    Change-Id: Idd2f8a0ec184b4b6b1ad1e6e5d75df551c36a96d
    updates: bz#1648768
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 818e60ac9269c49396480a151c049042af5b2929
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Nov 13 08:12:06 2018 +0530

    glusterd: fix Resource leak coverity issue
    
    Problem: In commit bcf1e8b07491b48c5372924dbbbad5b8391c6d81 code
             was missed to free path return by function search_brick_path_from_proc
    
    This patch fixes CID:
    1396668: Resource leak
    
    Change-Id: I4888c071c1058023c7e138a8bcb94ec97305fadf
    fixes: bz#1646892
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 8204c072ee80c5901ac38e66e346a2ba7da31892
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Wed Nov 14 16:28:03 2018 +0530

    cli: cluster.server-quorum-type help text is missing
    
    Added a default value "none" and additional description.
    
    Change-Id: I3a5c06f8ec1e502fc399860e4b5cb835102cd71d
    Updates: bz#1608512
    Signed-off-by: Shwetha Acharya <sacharya@redhat.com>

commit fda594875c4cdb2a22e27aa13f5c66bee032ccb5
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Nov 9 02:29:52 2018 -0500

    afr: open_ftruncate_cbk should read fd from local->cont.open struct
    
    afr_open stores the fd as part of its local->cont.open struct
    but when it calls ftruncate (if open flags contain O_TRUNC), the
    corresponding cbk function (afr_ open_ftruncate_cbk) is
    incorrectly referencing uninitialized local->fd. This patch fixes
    the same.
    
    Change-Id: Icbdedbd1b8cfea11d8f41b6e5c4cb4b44d989aba
    updates: bz#1648687
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 4a4ba1f2eb0be2da9e88560246730af87788295f
Author: Kaleb S. KEITHLE <kkeithle@redhat.com>
Date:   Fri Nov 9 09:45:05 2018 -0500

    core: fix strncpy warnings
    
    Since gcc-8.2.x (fedora-28 or so) gcc has been emitting warnings
    about buggy use of strncpy.
    
    Most uses that gcc warns about in our sources are exactly backwards;
    the 'limit' or len is the strlen/size of the _source param_, giving
    exactly zero protection against overruns. (Which was, after all, one
    of the points of using strncpy in the first place.)
    
    IOW, many warnings are about uses that look approximately like this:
        ...
        char dest[8];
        char src[] = "this is a string longer than eight chars";
        ...
        strncpy (dest, src, sizeof(src)); /* boom */
        ...
    
    The len/limit should be sizeof(dest).
    
    Note: the above example has a definite over-run. In our source the
    overrun is typically only theoretical (but possibly exploitable.)
    
    Also strncpy doesn't null-terminate on truncation; snprintf does; prefer
    snprintf over strncpy.
    
    Mildly surprising that coverity doesn't warn/isn't warning about this.
    
    Change-Id: I022d5c6346a751e181ad44d9a099531c1172626e
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLE <kkeithle@redhat.com>

commit 76906af9d70fc784de728a70e3dbda62dece5e10
Author: Kaleb S. KEITHLE <kkeithle@redhat.com>
Date:   Fri Nov 9 11:27:11 2018 -0500

    core: fix strncpy warnings
    
    Since gcc-8.2.x (fedora-28 or so) gcc has been emitting warnings
    about buggy use of strncpy.
    
    e.g.
      warning: ‘strncpy’ output truncated before terminating nul
      copying as many bytes from a string as its length
    and
      warning: ‘strncpy’ specified bound depends on the length of the
      source argument
    
    Since we're copying string fragments and explicitly null terminating
    use memcpy to silence the warning
    
    Change-Id: I413d84b5f4157f15c99e9af3e154ce594d5bcdc1
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 8a5adc811637b147e6e42d952498bc99e3d670bb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Nov 8 08:25:00 2018 +0200

    rpc/rpc-lib/src/rpc-clnt.c: unlock sooner, if we fail to connect.
    
    Previously, we did not go to unlock the mutex if we failed
    to connect. This patch fixes it.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I0fcca066a2601dba6bc3e9eb8b3c9fc757ffe4db

commit 013c8295d7cd7f5ad52bcf2585936ed320b8bbc7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Nov 14 15:26:30 2018 +0530

    glusterfsd: Make io-stats xlator search position independent
    
    Problem:
    glusterfsd notify trigger for profile info command expects
    decompounder xlator to have the name of the brick and its
    immediate child to be io-stats xlator. In GD2 decompounder
    xlator doesn't exist, so this is preventing io-stats xlator
    from receiving the profile info collection notification.
    
    Fix:
    search for io-stats xlator below server xlator till the first
    instance is found and send notification for it.
    
    fixes bz#1649709
    Change-Id: I92a1d9019bbd5546050ab43d50d571c444e027ed
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 4c17065a02fb32acda32aac64da93ea5d326a7d5
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Nov 13 12:13:03 2018 +0530

    posix: Fix null pointer dererfence
    
    CID: 1124799 1214618
    
    Change-Id: Iff05180983fe9600be0a2ce015a137e4efb8f533
    updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 3e20df8674d489fba707079e2b5a58347a3b3928
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Nov 8 12:27:07 2018 +0530

    feature/shard: Fix coverity issue - Use after free
    
    CID: 1325524
    
    Change-Id: Ic713285bd9e76d8e4dc1815aa471087d279008b5
    updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 142b840fe14c3b4281a0eaeede918c3e121de84b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Nov 13 10:56:05 2018 +0530

    glusterd/snapshot: copy-paste typo
    
    Change-Id: Ice3663084b2d0a0a10d75ad68fe5fe494f928250
    updates: bz#1193929
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f1a826e1b38d5ecaf9470c61198c4d4362b4c29a
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Nov 8 14:47:27 2018 +0530

    features/ctime: Fix Coverity issue
    
    CID : 1394632 Dereference after null check
    
    Change-Id: If0bef48b070935854e9d2988393dba07c9001cd2
    updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 54a5f0a07817098134219aea9414b029013927f3
Author: Prashanth Pai <ppai@redhat.com>
Date:   Sat Oct 27 16:32:05 2018 +0530

    glusterfsd: Make each multiplexed brick sign in
    
    NOTE: This change will be consumed by brick mux implementation of
    glusterd2 only. No corresponsing change in glusterd1 has been made.
    
    When a multiplexed brick process is shutting down, it sends sign out
    requests to glusterd for all bricks that it contains. However, sign in
    request is only sent for a single brick. Consequently, glusterd has to
    use some tricky means to repopulate pmap registry with information of
    multiplexed bricks during glusterd restart.
    
    This change makes each multiplexed brick send a sign in request to
    glusterd2 which ensures that glusterd2 can easily repopulate pmap
    registry with port information.
    
    As a bonus, sign in request will now also contain PID of the brick
    sending the request so that glusterd2 can rely on this instead of
    having to read/manage brick pidfiles.
    
    Change-Id: I409501515bd9a28ee7a960faca080e97cabe5858
    updates: bz#1193929
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit 28b4096fe484f545ae578dcef040a69acf6205cd
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Sat Sep 29 11:32:17 2018 +0800

    md-cache: request ACLs related xattrs when mode change
    
    If glusterfs client changes mode, ACLs related xattrs may changed too.
    
    Change-Id: Ifa5bff1f77ab7b176e54da4607ea9c1e66fc5588
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 9ce088e947d0867ded1bd969d9b22624a59f178b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Nov 9 12:44:20 2018 +0530

    glusterd: don't call svcs_reconfigure for all volumes during op-version bump up
    
    With having large number of volumes in a configuration having
    svcs_reconfigure () called for every volumes makes cluster.op-version bump up to
    time out. Instead call svcs_reconfigure () only once.
    
    Change-Id: Ic6a133d77113c992a4dbeaf7f5663b7ffcbb0ae9
    Fixes: bz#1648237
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 96ae7dd2262a3ac72aea14c69f7404a8f8435a5c
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Nov 8 14:14:04 2018 +0530

    quiesce : fix coverity issue
    
    This patch fixes 1388996 : Dereference null return value
    
    updates: bz#789278
    
    Change-Id: I9351ae43736efd2f9abe4e1888dba89b6b3e1fe3
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit f68f9106087a3dc4e6da88a09285ac723096d7e9
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Nov 7 06:31:19 2018 -0800

    features/changelog: Avoid a potential null dereference
    
    Addresses CID 1396292
    
    Change-Id: I9141502a12fb3e18c04d07c79da87a5ebb2cfc23
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit bcf1e8b07491b48c5372924dbbbad5b8391c6d81
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Nov 6 16:23:51 2018 +0530

    core: Portmap entries showing stale brick entries when bricks are down
    
    Problem: pmap is showing stale brick entries after down the brick
             because of glusterd_brick_rpc_notify call gf_is_service_running
             before call pmap_registry_remove to ensure about brick instance.
    
    Solutiom: 1) Change the condition in gf_is_pid_running to ensure about
                 process existence, use open instead of access to achieve
                 the same
              2) Call search_brick_path_from_proc in __glusterd_brick_rpc_notify
                 along with gf_is_service_running
    
    Change-Id: Ia663ac61c01fdee6c12f47c0300cdf93f19b6a19
    fixes: bz#1646892
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit e134ef2493e8517a6f341416c11230c2bb5bcd6c
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Nov 8 07:50:48 2018 +0200

    rpc-clnt*: several code changes to reduce conn lock times
    
    Assorted code refactoring to reduce lock contention.
    Also, took the opportunity to reorder structs more properly.
    Removed dead code.
    
    Hopefully, no functional changes.
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I5de6124ad071fd5e2c31832364d602b5f6d6fe28

commit cac2dba48bf8029b2b0421850fcc4598e33569f6
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Oct 21 03:55:04 2018 +0300

    libglusterfs multiple files: remove dead initilization
    
    Per newer GCC releases and clang-scan, some trivial
    dead initialization (values that were set but were never
    read) were removed.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ia9959b2ff87d2e9cb46864e68ffe7dccb984db34

commit db28fc7a35b784a4ca6a361961081f93e968cfcb
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Nov 8 16:03:23 2018 +0530

    cli: avoid unnecessary strtail for geo rep config.
    
    Found while looking at this function for another patch.
    
    Compile Tested Only!
    
    Updates bz#1193929
    Change-Id: I46a9e95bf4d6609bc122edf86418659369258abe
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit cefdd02776d204744a13215029f1c3fe024283e4
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Nov 2 09:08:42 2018 +0530

    ctime: Enable ctime feature by default
    
    This patch does following.
    
    1. Enable ctime feature by default.
    
    2. Earlier, to enable the ctime feature, two options
       needed to be enabled
         a. gluster vol set <volname> utime on
         b. gluster vol set <volname> ctime on
    
       This is inconvenient from the usability point of
       view.  Hence changed it to following single option
    
         a. gluster vol set <volname> ctime on
    
    fixes: bz#1624724
    Change-Id: I04af0e5de1ea6126c58a06ba8a26e22f9f06344e
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 185106a574646bdc2d4ec50756c52db61ad14d98
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Nov 6 21:35:36 2018 +0530

    cli: add a warning/confirmation message in peer detach code path
    
    On a multi node cluster if one of the node is detached which had active
    clients mounted through the same server address, this can cause all the
    clients to loose any volfile changes. This is due to the lack of infra
    in glusterd to let client know the list of IPs and attempt to connect to
    other active nodes as failback. Such framework does exist in GD2 but not
    in GD1.
    
    This patch ensures to take a preventive measure to have a warning
    message thrown to user to ensure all such connected clients are
    remounted through a different IP.
    
    Change-Id: I740b01868abbd75bf0a609cfaf00114d4d78aa96
    Fixes: bz#1647074
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 6d4cd8ce6c0d88d331ffed97c51d3061a3900561
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Nov 8 10:21:29 2018 +0800

    gfapi: fix bad dict setting of lease-id
    
    lease_id is a 16 bits opaque data, copying it by gf_strdup is wrong.
    
    Invalid read of size 2
       at 0x483FA2F: memmove (vg_replace_strmem.c:1270)
       by 0xE2EF6FB: ??? (in /usr/lib64/libtirpc.so.3.0.0)
       by 0xE2EE047: xdr_opaque (in /usr/lib64/libtirpc.so.3.0.0)
       by 0x107A97DC: xdr_gfx_value (glusterfs4-xdr.c:207)
       by 0x107A98C0: xdr_gfx_dict_pair (glusterfs4-xdr.c:321)
       by 0xE2EF35E: xdr_array (in /usr/lib64/libtirpc.so.3.0.0)
       by 0x107A9A89: xdr_gfx_dict (glusterfs4-xdr.c:335)
       by 0x107AA97B: xdr_gfx_write_req (glusterfs4-xdr.c:897)
       by 0x107A181E: xdr_serialize_generic (xdr-generic.c:25)
       by 0x231044A2: client_submit_request (client.c:205)
       by 0x2314D3C1: client4_0_writev (client-rpc-fops_v2.c:3863)
       by 0x230FD5FA: client_writev (client.c:956)
     Address 0xad659e18 is 72 bytes inside a block of size 73 alloc'd
       at 0x483880B: malloc (vg_replace_malloc.c:299)
       by 0x106BA7EC: __gf_malloc (mem-pool.c:136)
       by 0x1064521E: gf_strndup (mem-pool.h:166)
       by 0x1064521E: gf_strdup (mem-pool.h:183)
       by 0x1064521E: get_fop_attr_thrd_key (glfs.c:627)
       by 0x1064D8E9: glfs_pwritev@@GFAPI_3.4.0 (glfs-fops.c:1154)
       by 0x10610C0C: glusterfs_write2 (handle.c:2092)
       by 0x54D30C: mdcache_write2 (mdcache_file.c:647)
       by 0x48A3FC: nfs4_write (nfs4_op_write.c:459)
       by 0x48A44D: nfs4_op_write (nfs4_op_write.c:487)
       by 0x4634F5: nfs4_Compound (nfs4_Compound.c:947)
       by 0x460155: nfs_rpc_process_request (nfs_worker_thread.c:1329)
       by 0x4608A3: nfs_rpc_valid_NFS (nfs_worker_thread.c:1539)
       by 0x488F12F: svc_vc_decode (svc_vc.c:825)
    
    Updates bz#1647651
    Change-Id: Ib9fff55c897bc43c15036a869888e763df133757
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit bdb4ca184913c82ccf9552298f5d5b597794f2aa
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Nov 6 19:44:16 2018 +0530

    glusterd: allow shared-storage to use bricks under glusterd working directory
    
    With commit 44e4db, we are not allowing user to create a volume
    using glusterd's working directory as a brick or any sub directory
    under glusterd's working directory as a brick.This has broken
    shared-storage since the volume "gluster-shared-storage" is
    created using the bricks under glusterd's working directory.
    
    With this patch, we let the "gluster-shared-storage" volume
    to use bricks under glusterd's working directory.
    
    fixes: bz#1647029
    Change-Id: Ifcbcf4576eea12cf46f199dea287b29bd3ec3bfd
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 3056419608d5e1835d41612e09b56511d0f9a101
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Nov 7 15:17:55 2018 -0500

    coverity: ignore tainted access reported in gf_free
    
    Earlier commit had the annotation incorrect, and also did not
    wrap the sanitization in a separate function. (see commit 39a1db1)
    
    The issues are corrected in this patch, and also a coverity
    stand alone run has been tested to ensure the annotations are
    respected by coverity.
    
    Change-Id: I4a93b6981e2ff4bba9a29e590b17da248931c8ae
    Updates: bz#789278
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit a907e468e724c32b9833ce59806fc215c7122d63
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Aug 10 15:57:50 2018 +0530

    bd: remove from the build
    
    Based on the proposal to remove few features as they are not
    actively maintained [1], removed BD (block device) translator
    from the build.
    
    [1] - https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    Updates: bz#1635688
    Change-Id: Ia96db406c58a7aef355dde6bc33523bb2492b1a9
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8f82c1165871e43de945ba0ed3fdaaf0d68aeef3
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Nov 6 10:12:10 2018 -0800

    features/locks:Use pthread_mutex_unlock() instead of pthread_mutex_lock()
    
    Fixes CID 1396581
    
    Change-Id: Ic04091b5783a75d8e1e605a9c1c28b77fea048d3
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit c3fcff9ccbfcec1be242fd5cf210c9995586b078
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 3 17:13:09 2018 +0530

    glupy: remove from the build
    
    Based on the proposal to remove few features as they are not
    actively maintained [1], removing 'glupy' translator from the
    build.
    
    [1] https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    This patch aims at clearing the translator from build and tests.
    A followup is needed to remove the code from repository.
    
    Updates: bz#1642810
    Change-Id: I41d0c1956330c3bbca62c540ccf9ab01bbf3a092
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e78682bb7c2e40b7f818efdcd56aca459b9dbb03
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Nov 2 10:39:58 2018 +0530

    xlators/experimental: remove from the build
    
    Based on the proposal to remove few features as they are not
    actively maintained [1], removing all experimental translators
    from the build.
    
    [1] https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    Note that as followup patch, there would be a patch to remove the code.
    
    Updates: bz#1635688
    Change-Id: I8ebc256517feb37fc7580104e8bebe27d047f959
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ee630e250fdc0081ae58c078ee5f5500561984df
Author: Hu Jianfei <hujianfei@cmss.chinamobile.com>
Date:   Tue Nov 6 06:47:08 2018 -0500

    glusterfsd: Do not process GLUSTERD_NODE_STATUS if graph is not ready
    
    Otherwise, gnfs will crash if we try to get nfs clients status in
    following situation. Also see commit 2f9e555f.
    
    Reproducible Steps:
    1. systemctl restart glusterd; gluster volume status rep
    2. systemctl restart glusterd; gluster volume status rep nfs clients
    
    step 1 works ok, but step 2 will lead localhost gnfs crash with
    certain probability.
    
    /lib64/libglusterfs.so.0(+0x270f0)[0x7effb6c7b0f0]
    /lib64/libglusterfs.so.0(gf_print_trace+0x334)[0x7effb6c854a4]
    /lib64/libc.so.6(+0x35270)[0x7effb52e7270]
    /usr/sbin/glusterfs(glusterfs_handle_node_status+0x155)[0x7effb7196905]
    /lib64/libglusterfs.so.0(+0x63f40)[0x7effb6cb7f40]
    /lib64/libc.so.6(+0x46d40)[0x7effb52f8d40]
    
    Updates: bz#1646869
    
    Change-Id: Ia4cb009f821d32b2d18ba48d3467cc81a4b07747
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>
    Signed-off-by: Hu Jianfei <hujianfei@cmss.chinamobile.com>

commit d945c44c6289eadcda805f728fcc638586658c37
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Nov 6 21:27:33 2018 +0530

    cluster/afr: s/uuid_is_null/gf_uuid_is_null
    
    Updates bz#1193929
    Change-Id: I1b312dabffac7e101df8ce15557527fd28a2c61f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d76611fbba18d3120ac59f8f127981d0c950962a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Nov 6 18:18:30 2018 +0200

    libglusterfs/src/iobuf.c: don't forget to unlock a mutex
    
    commit ed83a4ee7b73e6b04694d1ac11ed25d2983ac943 changed locking
    order and forgot to unlock in a negative path (when index was -1).
    Coverity caught it (thanks!) as  CID 1396581:  Program hangs  (LOCK)
    
    Note: I'm unlocking before logging the failure. I think it's the right
    order - logging can take a while (especially if your disk is slow).
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I82ac241edf1d511bf6807cf9c46c538ab9f4acc4

commit bab025b08e63afd28cba6a3e2c5e18474904dcd3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Nov 6 15:58:45 2018 +0530

    tests/interrupt.t: remove 'stripe' volume type
    
    Merged the patch which introduced this testcase after the
    'remove stripe' patch got merged, and hence the confusion.
    
    Updates: bz#1193929
    Change-Id: Ia08552debb111292caf14e51ea6a27334fe5c788
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 9777662406319422450989db104d5a588e52104d
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Mon Oct 15 15:41:23 2018 +0800

    md-cache: new option "cache-glusterfs-acl" for virtual glusterfs ACLs
    
    Change-Id: I020ab08dba48f13cf7b8908e96280f1e92e9b9db
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 5f19d8231cedf72af554d6f5e9c2636b1586ec16
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Sat Sep 29 11:54:07 2018 +0800

    md-cache: request cached xattrs at getxattr/fgetxattr
    
    Change-Id: I8e3ad961164815683776850e3a5fd4f510003690
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 7be4f21f257f23d8e4f2fd57aefa8736cae4cdbf
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Sat Sep 29 11:45:11 2018 +0800

    md-cache: extends xa_time when previous attributes equals cached attributes
    
    Some operations like read/write only update iatt and ia_time,
    without any operion request xattrs from glusterfsd,
    the xa_time is timeout before ia_time always.
    
    This patch updates xa_time when update ia_ttime.
    
    Change-Id: I77e3984f38c1c4dbebfde9729b8117fbacde9674
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 93e9b4c167f582234e08e2608fc844bdf02fd507
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Mon Oct 15 16:15:17 2018 +0800

    md-cache: remove xattr setting after new file created
    
    Fops of creating file does not request cached xattrs,
    the xattr in reply is not cached xattrs.
    
    Change-Id: Iab2db686e92466e72cfee8ac494e851d797c10b3
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 40318205bfcf75c6eee1c4c18f103260a77a7886
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Nov 5 11:28:46 2018 +0530

    glusterd: initialise caps inside #ifdef HAVE_BD_XLATOR block
    
    Note: The problem is seen when we disable bd xlator.
    
    Problem: When we create a volume, volume info file is having
    caps value as 15 in nodes which hosts bricks for that volume.
    Remainig nodes in cluster are not having caps field. When
    glusterd is restarted, peers are going into rejected state,
    because of this mismacth in configuration files.
    
    Cause: In glusterd_op_create_volume(), we initialise caps
    value as 15 in the beginning. Later, we check whether brick
    belongs to the same node or not. If brick doesn't belong to
    the same node, caps value will be set to 0. If brick belongs
    to the same node, we will change the caps value inside
    
    Solution: If brick doesn't belongs to the same node,caps is
    set to 0 and if brick belongs to same brick caps value is
    changed inside #ifdef HAVE_BD_XLATOR block. So, to have the
    consistency across the cluster, we need to initialise caps
    value inside #ifdef HAVE_BD_XLATOR block, only when brick
    belongs to the same node.
    
    fixes: bz#1645986
    Change-Id: I2648f420b21d6e69e7c38b0f4736d41e0f15a7f5
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit eb75b04fe15b8b7c0fadbafe9b2ed0c8ce87def8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Sep 20 23:19:39 2018 +0530

    doc: add a new contributor 'hints' guide
    
    Keeping this in glusterfs Repo for glusterfs specific improvements.
    There would be a link to this page, and some more similar pages from
    docs.gluster.org
    
    updates: bz#1193929
    Change-Id: Ie98670cc32e62951f1b1880b1ae39f5cc2b45329
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c2c70552188ee1b15bb748b4f2272062505c7696
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Nov 2 09:23:42 2018 +0530

    lock: Do not allow meta-lock count to be more than one
    
    In the current scheme of glusterfs where lock migration is
    experimental, (ideally) the rebalance process which is migrating
    the file should request for a metalock. Hence, the metalock count
    should not be more than one for an inode. In future, if there is a
    need for meta-lock from other clients, this patch can be reverted.
    
    Since pl_metalk is called as part of setxattr operation, any client
    process(non-rebalance) residing outside trusted network can exhaust
    memory of the server node by issuing setxattr repetitively on the
    metalock key. The current patch makes sure that more than
    one metalock cannot be granted on an inode.
    
    Fixes CVE-2018-14660
    
    updates: bz#1644758
    Change-Id: Ie1e697766388718804a9551bc58351808fe71069
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 4c6b063463ae48b3509ff8e66cd391f8637a86af
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Aug 21 12:44:54 2018 +0200

    fuse: diagnostic FLUSH interrupt
    
    We add dummy interrupt handling for the FLUSH
    fuse message. It can be enabled by the
    "--fuse-flush-handle-interrupt" hidden command line
    option, or "-ofuse-flush-handle-interrupt=yes"
    mount option.
    
    It serves no other than diagnostic & demonstational
    purposes -- to exercise the interrupt handling framework
    a bit and to give an usage example.
    
    Documentation is also provided that showcases interrupt
    handling via FLUSH.
    
    Change-Id: I522f1e798501d06b74ac3592a5f73c1ab0590c60
    updates: #465
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit bceb9f25671e65cb2f0987a84370055e7c36900f
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Aug 9 11:46:33 2018 +0200

    fuse: interrupt handling framework
    
    - add sub-framework to send timed responses to kernel
    - add interrupt handler queue
    - implement INTERRUPT
    
    fuse_interrupt looks up handlers for interrupted messages
    in the queue. If found, it invokes the handler function.
    Else responds with EAGAIN with a delay.
    
    See spec at
    
    https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/filesystems/fuse.txt?h=v4.17#n148
    
    and explanation in comments.
    
    Change-Id: I1a79d3679b31f36e14b4ac8f60b7f2c1ea2badfb
    updates: #465
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 258db7178663305c26aa0068d4f72159ff0bc3ba
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Nov 4 16:17:27 2018 +0200

    libglusterfs/src/iobuf.c: where possible, pass the index parameter
    
    Don't 'calculate' again where it can be passed.
    If possible, do not perform under lock.
    
    Also remove some NULL checks, assuming they were done by the callers.
    Left a remark for each such change.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ia5c2851506da3388cb2d4445334c58881e2c4416

commit ed83a4ee7b73e6b04694d1ac11ed25d2983ac943
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Nov 4 13:47:25 2018 +0200

    libglusterfs/src/iobuf.c: take the pool lock once in new pool
    
    When creating a new pool, take the pool lock once and create
    all arenas, instead of taking and releasing for each arena.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I7daa39de960e47e66a32ecab724cf3a61ccdc01b

commit ba52abc6931baecb73d690b289f8feb32205424f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Nov 4 11:00:11 2018 +0200

    libglusterfs/src/iobuf.c: remove some if statements
    
    Small code refactoring to remove some if statements
    in several functions. No functional changes expected.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: If9f8d5d53c9688fb994b6d690aea66f65fa01c55

commit d2b745319334a1025b9e47f55928033b8d1c7c46
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Nov 2 10:39:18 2018 +0530

    logging: create parent dir if not available
    
    As glusterfs logging uses different directory than /var/log
    (ie, /var/log/glusterfs), there is a chance it may not be
    present when starting glusterfs. Create parent dir if it
    doesn't exist.
    
    Updates: bz#1193929
    Change-Id: I8d6f7e5a608ba53258b14617f5d103d1e98b95c1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 3c6cf9a4a1b46cab2dc53c1ee0afca0fe993102e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Nov 5 11:46:41 2018 +0530

    geo-rep: Fix traceback with symlink metadata sync
    
    While syncing metadata, 'os.chmod', 'os.chown',
    'os.utime' should be used without de-reference.
    But python supports only 'os.chown' without
    de-reference. That's mostly because Linux
    doesn't support 'chmod' on symlink file itself
    but it does support 'chown'.
    
    So while syncing metadata ops, if it's symlink
    we should only sync 'chown' and not do 'chmod'
    and 'utime'. It will lead to tracebacks with
    errors like EROFS, EPERM, ACCESS, ENOENT.
    All the three errors (EPERM, ACCESS, ENOENT)
    were handled except EROFS. But the way it was
    handled was not fool proof. The operation is
    tried and failure was handled based on the errors.
    All the errors with symlink file for 'chown',
    'utime' had to be passed to safe errors list of
    'errno_wrap'. This patch handles it better by
    avoiding 'chmod' and 'utime' if it's symlink
    file.
    
    fixes: bz#1646104
    Change-Id: Ic354206455cdc7ab2a87d741d81f4efe1f19d77d
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 74e8328d3f6901d6ba38a313965fe910c8411324
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Nov 1 07:25:25 2018 +0530

    all: fix the format string exceptions
    
    Currently, there are possibilities in few places, where a user-controlled
    (like filename, program parameter etc) string can be passed as 'fmt' for
    printf(), which can lead to segfault, if the user's string contains '%s',
    '%d' in it.
    
    While fixing it, makes sense to make the explicit check for such issues
    across the codebase, by making the format call properly.
    
    Fixes: CVE-2018-14661
    
    Fixes: bz#1644763
    Change-Id: Ib547293f2d9eb618594cbff0df3b9c800e88bde4
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 2effe3b0d3fa51fc627c970353de2e326bcf1ef2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Nov 1 07:16:32 2018 +0530

    protocol: remove the option 'verify-volfile-checksum'
    
    'getspec' operation is not used between 'client' and 'server' ever since
    we have off-loaded volfile management to glusterd, ie, at least 7 years.
    
    No reason to keep the dead code! The removed option had no meaning,
    as glusterd didn't provide a way to set (or unset) this option. So,
    no regression should be observed from any of the existing glusterfs
    deployment, supported or unsupported.
    
    Updates: CVE-2018-14653
    
    Updates: bz#1644756
    Change-Id: I4a2e0f673c5bcd4644976a61dbd2d37003a428eb
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 5441fb4196a94d238377c427f400fe5e28ae5d46
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Nov 1 07:02:11 2018 +0530

    server: don't allow '/' in basename
    
    Server stack needs to have all the sort of validation, assuming
    clients can be compromized. It is possible for a compromized
    client to send basenames with paths with '/', and with that
    create files without permission on server. By sanitizing the basename,
    and not allowing anything other than actual directory as the parent
    for any entry creation, we can mitigate the effects of clients
    not able to exploit the server.
    
    Fixes: CVE-2018-14651
    
    Fixes: bz#1644755
    Change-Id: I5dc0da0da2713452ff2b65ac2ddbccf1a267dc20
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit acb208221bfe3ac897d8eb4fbe18fa6c8aa9286e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Nov 1 07:21:41 2018 +0530

    io-stats: prevent taking file dump on server side
    
    By allowing clients taking dump in a file on brick process, we are
    allowing compromised clients to create io-stats dumps on server,
    which can exhaust all the available inodes.
    
    Fixes: CVE-2018-14659
    
    Fixes: bz#1644757
    Change-Id: I32bfde9d4fe646d819a45e627805b928cae2e1ca
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 49f1b76f471f0845a2c7edf69f5629226f73ad27
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Sat Nov 3 23:09:40 2018 +0530

    glusterd : fix high sev coverity issue
    
    This patch fixes CID : 1174824 : RESOURCE_LEAK
    
    updates: bz#789278
    
    Change-Id: I2a4f8b508995de112fa16e1094e44ecd4b625312
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit bd1a8fc74ac9322384daab94bf5736cae15ecbfe
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Nov 1 21:31:41 2018 +0530

    index: prevent arbitrary file creation outside entry-changes folder
    
    Problem:
    A compromised client can set arbitrary values for the GF_XATTROP_ENTRY_IN_KEY
    and GF_XATTROP_ENTRY_OUT_KEY during xattrop fop. These values are
    consumed by index as a filename to be created/deleted according to the key.
    Thus it is possible to create/delete random files even outside the gluster
    volume boundary.
    
    Fix:
    Index expects the filename to be a basename, i.e. it must not contain any
    pathname components like "/" or "../". Enforce this.
    
    Fixes: CVE-2018-14654
    
    Fixes: bz#1644760
    Change-Id: I35f2a39257b5917d17283d0a4f575b92f783f143
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 643c9d049de970d27b2bfa806c4d47ea6eabefe6
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Oct 16 15:34:20 2018 -0400

    features/snapview-server: change gf_log instances to gf_msg
    
    Change-Id: Ib8bdf210a896423abcd7413dd4896d424ac0f561
    fixes: bz#1626610
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 029a7e5c1908f53cc4411a8d6cbf6a4e2b207879
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Oct 18 17:46:26 2018 +0800

    dht: fix use after free in dht_rmdir_readdirp_cbk
    
    The frame is freed when linkfile exist in dht_rmdir_is_subvol_empty(),
    the following message use the freed local.
    
    Change-Id: I41191e8bd477f031a2444d5f15e578dc4f086e6b
    Updates: bz#1640489
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit aad1e56286c35237decb106434596fb7f081ee53
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Nov 3 12:13:29 2018 +0530

    glusterd: coverity fixes
    
    Addresses CIDs : 1124769, 1124852, 1124864, 1134024, 1229876, 1382382
    
    Also addressed a spurious failure in
    tests/bugs/glusterd/df-results-post-replace-brick-operations.t to ensure
    post replace brick operation and before triggering 'df' from mount,
    client has connection to the newly replaced bricks.
    
    Change-Id: Ie5d7e02f89400a661491d7fc2a120d6f6a83a1cc
    Updates: bz#789278
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 91cb12be96fb543ee9c0b47bfa8792786286aff7
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Oct 30 20:22:41 2018 +0530

    posix : fix coverity issues in posix-entry-ops.c
    
    This patch fixes CID:
     1. 1389762 : Explicit null dereferenced
     2. 1390462 : Argument cannot be negative
     3. 1124552 : Explicit null dereferenced
     4. 1356522 : Argument cannot be negative
    
    updates: bz#789278
    Change-Id: I1262f3b4b61a6e65bb34884f46df9a24b8dd03f1
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit a665120d77072cfc8daca88d717055132a178be1
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Sep 26 00:30:26 2018 +0530

    glusterd : fix high coverity issues glusterd-store.c
    
    This patch fixes CID 1224305, 1202395, 1202394, 1174824, 1174825, 1174826
    and 1202397.
    
    All issues are of RESOURCE_LEAK type.
    
    Change-Id: Ie9944d5bdd0bd2788afdb1b6bb329aa3c44b90d0
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 36e2ec3c88eba7a1bcd8aa6f64e4672349ff1d0c
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Oct 18 19:42:48 2018 +0800

    md-cache: removexattr must be send to glusterfsd
    
    Change-Id: I53a583ec14bce65e8914bc496123dee3abe61f6c
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit c2a543ec947ac56f882a9c0a890f49c63dedeaff
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 17 23:03:04 2018 +0530

    xlator: add generic option parsing framework
    
    As an example, and also as an enhancement, added 'log-level'
    as a default option to every translator (glusterfs already
    support infrastructure to handle xl->loglevel).
    
    Corresponding infrastructure to add per xlator log-level
    is not present in glusterd volume-set. Plan is to get it
    sorted out in later patches or in GD2.
    
    * Why this is needed? - Mainly because we need to only add
    different log-level to some xlator to debug few things in a
    production system, while not changing overall log-level. This
    helps in better debug-ability.
    
    Updates: bz#1193929
    
    Change-Id: Ia4098ce39197cd423345b3d31fe8315481681ab8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 55a6ba56bea9ec0d3316c005300c514ea3ab0e54
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 3 17:00:24 2018 +0530

    tiering: remove the translator from build and glusterd
    
    Based on the proposal to remove few features as they are not
    actively maintained [1], removing tier translator from the
    build. Also make sure there are no regression tests involving
    tiering feature are present.
    
    [1] https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    Change-Id: I2c177f711f9b54b7b24e1a13525ff3132bd9a9c5
    updates: bz#1642807
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 6e8f7bb6ab457cfee42e405243cf4db82a9a56b8
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Oct 30 16:36:50 2018 +0530

    glusterd: set fsid while performing replace brick
    
    While performing the replace-brick operation, we should set
    fsid value to the new brick.
    
    fixes: bz#1637196
    
    Change-Id: I9e9a4962fc0c2f5dff43e4ac11767814a0c0beaf
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 5d0c8e8ec9b68352cf53f8e430897096e2caf477
Author: Varsha Rao <varao@redhat.com>
Date:   Mon Oct 29 09:53:27 2018 +0530

    posix: Fix coverity issue
    
    This patch fixes the unchecked return value, coverity issue.
    CID: 1391412
    
    Change-Id: If85f4afdf8c6d37602c62fbf4d7c730e18be81e7
    updates: bz#789278
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 00a5e2a5112971e4d3dca8419f24d878b4199d37
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Oct 30 10:56:52 2018 +0530

    posix/ctime: Avoid log flood in posix_update_utime_in_mdata
    
    posix_update_utime_in_mdata() unconditionally logs an error if
    consistent time attributes features is not enabled. This log
    does not add any value, prints an incorrect errno & floods
    the log file. Hence nuking this log message in this patch.
    
    fixes: bz#1644129
    Change-Id: I9a1f9e7ada3366d2830f18d81f16a1461040092e
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit d3ec5f5a089edb68206b5d4a469358867340d4f7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Nov 1 07:08:29 2018 +0530

    glusterd-handshake: prevent a buffer overflow
    
    as key size in xdr can be anything, it can be bigger than the
    'NAME_MAX' allowed in the structure, which can allow for service denial
    attacks.
    
    Fixes: CVE-2018-14653
    
    Fixes: bz#1644756
    Change-Id: I2dc5e99af27ddf44c12c94b07e51adb8674cce80
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 7fac81aeab5805fb2bd719d7489636633bb5e32a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Oct 29 14:16:20 2018 +0530

    mem-pool: change the values to 64bits
    
    total_allocs of certain type of variables can be 4billion in a
    single day depending on load. So, 32 bits for that is not enough.
    
    Also, size_t is good variable size for one allocation, but the
    sum of allocations, should be 64bits to make sure we don't
    overflow the variable.
    
    Updates: bz#1639599
    Change-Id: If3b19687f94425e913a0201ae5d73661eda51f06
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 7150c51ad75ccba22045a35fc31e5037612d1ad4
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Oct 31 12:26:43 2018 +0100

    cluster/ec: prevent infinite loop in self-heal full
    
    There was a problem in commit 7f81067 that caused infinite loop when
    full heal was triggered.
    
    The previous commit was made to prevent self-heal to go idle after a
    replace brick operation. One of the changes consisted on setting a
    flag to force an immediate scan of the dirty directory if a heal on
    a directory succeeded (assuming it could have generated newer entries).
    
    However that change was causing an issue with a full self-heal, since
    every time an already healed directory was checked and it returned
    suceessfully, it was also setting the flag, forcing self-heal to start
    over again.
    
    This patch fixes this issue by only setting the flag if the heal is not
    full. It's assumed that a full self-heal will already traverse all
    entries automatically, so there's no need to force a new scan later.
    
    Change-Id: Id12dbfc04e622b18183e796cc6cc87ccc30a6d55
    fixes: bz#1636631
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit d2d3c37fa8efca74e375b8a0dc7fa720c3b84dcc
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Thu Oct 4 16:09:08 2018 +0530

    cluster/dht: NULL pointer dereferencing clang fix
    
    Dereferencing NUll pointers this,local and stbuf.
    
    1.Replaced this->name with "dht".
    2.Removed GF_VALIDATE_OR_GOTO.
    3.Removed the check for "stbuf" and "this".
    
    Updates: bz#1622665
    
    Change-Id: Id2fb2270d5ec37b76fa2aae1f1c8dca72dcc728a
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit 9be6bf3d90e3783b3ba559c93d41b933f8d53f03
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Oct 17 15:18:34 2018 +0530

    cluster/ec: Change log level to DEBUG for lookup combine
    
    As lookup is not a locked fop, we can not trust the
    data received in this to be same.
    
    Changing the log level to DEBUG in case lookup finds any
    difference.
    
    Change-Id: I39499c44688a2455c7c6c69a798762d045d21b39
    updates: bz#1640066
    BUG: 1640066
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit fdb34014f1a16f7bf022353881e5a213538e96b2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Oct 25 12:37:42 2018 +0530

    tests: brick-mux-fd-cleanup.t should be under core directory
    
    Fixes: bz#1637934
    Change-Id: I5f95beab62bd2bdde3bbee94c308b0ad03e94379
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 733139551322e49e7e5617356cf96e30780d2749
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 3 15:30:10 2018 +0530

    stripe: remove the translator from build and glusterd
    
    Based on the proposal to remove few features as they are not
    actively maintained [1], removing stripe translator from the
    build. Also make sure there are no regression tests involving
    stripe translator.
    
    [1] https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html
    
    Note that this patch aims at removing the translator from build, and
    a followup patch is needed to remove the code from repository.
    
    Updates: bz#1364707
    Change-Id: I235b305338f138e29e9f30cba65bc0dadbebbbd5
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 19775e0445411cca9ddd9d294fd54d0b6fbe6a03
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 26 03:45:46 2018 -0400

    geo-rep: Add more intelligence to automatic error handling
    
    Geo-rep's automatic error handling does gfid conflict
    resolution. But if there are ENOENT errors because the
    parent is not synced to slave, it doesn' handle them.
    This patch adds the intelligence to create missing
    parent directories on slave. It can create the missing
    directories upto the depth of 10.
    
    fixes: bz#1643402
    Change-Id: Ic97ed1fa5899c087e404d559e04f7963ed7bb54c
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 5987b3388126a3c5e77481913cbaa4142117d19a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Oct 29 18:23:17 2018 +0530

    geo-rep/scripts: Fix traceback in gluster-mountbroker
    
    When 'gluster-mountbroker status' was issued, it
    crashes in a corner case with 'str object has not
    attribute get'. Fixed the same.
    
    fixes: bz#1643929
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Change-Id: Iaf1a937ed0136b3b2058230c75fa89a215d8a5eb

commit 33e96100e17e9a293db6d63d9d5449d6c2d69376
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Oct 29 17:55:28 2018 +0530

    georep: python2 to python3 compat - scheduler
    
    1. scheduler - Popen
    2. syncdutils - corner case on failure
    
    fixes: bz#1643932
    Change-Id: I65af97a244a8790e976acedc2728db6ebbf2ae10
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 6cc573631df28eb357ffb006d1dbfe1bfd60aeba
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Oct 30 12:35:59 2018 +0530

    core: Use GF_ATOMIC ops to update inode->nlookup
    
    fixes: bz#1644164
    
    Change-Id: I0ac5aff565b3a30d5ff25ec5a3f20e0bda424a5d
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit bae584148761ad98cd3d5c380f8cea1ff83aa8c3
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Oct 29 18:08:28 2018 +0530

    cliutils: python2 to python3 compat
    
    Make Popen py2 and py3 compatiable
    
    fixes: bz#1643935
    Change-Id: Ife34cb38024dcdc0420436e7d76fd208223f9d86
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 0c835893fdce59872103253985d152f4592eea89
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Tue Oct 23 12:57:45 2018 +0530

    rpc-transport/socket: NULL pointer dereferencing clang fix
    
    Problem: ctx and res can be NULL.
    
    Solution: introduced a VALIDATE_OR_GOTO statement, hence removed
    the null check for ctx; added a check for res.
    
    Updates: bz#1622665
    
    Change-Id: Ifee4c73e260530ab44c0a34c5ff5568f38f92c94
    Signed-off-by: Shwetha Acharya <sacharya@redhat.com>

commit d7fa1a85b1d5213128ec1f58d1e22af2495b9a3e
Author: Harpreet Kaur Lalwani <hlalwani@redhat.com>
Date:   Thu Oct 25 18:48:22 2018 +0530

    core: auth.ssl-allow has no option description
    
    Added a description for auth.ssl-allow
    
    Change-Id: I50cd7c738007c3d7a1b333dae62dbb5e46a7ee67
    fixes: bz#1643349
    Signed-off-by: Harpreet Kaur Lalwani <hlalwani@redhat.com>

commit 0857d837d0f9350c91f57e1096683b5abf973dcb
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Oct 26 09:28:59 2018 -0400

    build/packaging: el-X (x > 7) isms
    
    lvm2(-devel) 2.03.00 no longer has liblvm2app.so. (I expect a
    similar change in fedora-30 before too much longer, but for
    now fedora-30 still has lvm2 and lvm2-devel 2.02.181
    
    rpcgen has been removed from glibc-common and unbundled rpcgen
    is now required.
    
    And I guess nobody has ever built rpms with '--without bd' or we
    would have discovered the attempted inclusion of .../storage/bd.so
    in the rpm when it hadn't actually been built.
    
    Change-Id: I71e26c3d06af5d329ae89cc249a4ad88664ddf53
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 0f817c7795f115fb67b0973ce0965bcd3de8d196
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Oct 12 22:23:17 2018 +0530

    server-protocol: set the frame type to TYPE_FOP
    
    This will allow proper printing of exact 'fop' type to be logged in
    string, not number, during backtraces.
    
    Considering this was not done on brick processes, we have no easy
    way to glance and understand which fops were pending.
    
    What gets changed:
    
    After a crash, most of the core-dumps logged were of the form:
    ```
    pending frames:
    frame : type(0) op(18)
    frame : type(0) op(18)
    frame : type(0) op(28)
    ```
    would change to
    ```
    pending frames:
    frame : type(1) op(SETXATTR)
    frame : type(1) op(SETXATTR)
    frame : type(1) op(READDIR)
    ```
    
    updates: bz#1639599
    Change-Id: I0e3d2a8dee9cfde7ed0112a948f5213f546efb80
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ff18121945bff394f3234e9f1a9d61ac97d4d493
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Oct 25 03:23:56 2018 -0400

    geo-rep: Fix issue in gfid-conflict-resolution
    
    Problem:
    During gfid-conflict-resolution, geo-rep crashes
    with 'ValueError: list.remove(x): x not in list'
    
    Cause and Analysis:
    During gfid-conflict-resolution, the entry blob is
    passed back to master along with additional
    information to verify it's integrity. If everything
    looks fine, the entry creation is ignored and is
    deleted from the original list.  But it is crashing
    during removal of entry from the list saying entry
    not in list. The reason is that the stat information
    in the entry blob was modified and sent back to
    master if present.
    
    Fix:
    Send back the correct stat information for
    gfid-conflict-resolution.
    
    fixes: bz#1642865
    Change-Id: I47a6aa60b2a495465aa9314eebcb4085f0b1c4fd
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 196a2258ac33b6369efbf8979d5246e203dddbf2
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Oct 25 13:05:13 2018 +0530

    transport: log socket closures more verbose
    
    Problem:
    Intentional and unintentional socket closures cannot be identified
    
    Solution:
    Log intentional socket closures with at least INFO log level
    
    Change-Id: Ic02c882b16ab2193e57f8c3e6c3a82c4fe0f6875
    fixes: bz#1642800
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit c66ea8566d18230ce20b55640b25a06f6f56ec7d
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Tue Oct 23 18:23:53 2018 +0530

    posix: Null pointer dereferencing clang fix
    
    Added a check for "top"
    
    Updates: bz#1622665
    
    Change-Id: I354fdc7150b2f1eb452702ddb653e2d6ed609c10
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit bf5bfa5f2fcd1a73078c289aeac715bd82c366ed
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Oct 25 19:48:37 2018 +0530

    statedump: fix clang null dereference error
    
    ctx->active can be null, and is checked elsewhere in the
    same function. In another case, where 'ctx->active' gets
    dereferenced, it needs to be validated before the loop
    is hit.
    
    Updates: bz#1622665
    Change-Id: I4ec917e96c0756586fc7a74c76848bb9589a0293
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ace454cf407753625acc2d4d090cb529bd13b183
Author: root <root@rhs-srv-17.storage-dev.lab.eng.bos.redhat.com>
Date:   Thu Oct 25 05:47:23 2018 -0400

    afr/lease: Read child nodes from lease structure
    
    For lease operation, we allocate and store child nodes
    data in lease structure. Use the same in afr_lease_cbk()
    while checking for the quorum.
    
    Change-Id: If1fdd5a0798888afd39ad3df57d96487baf9d1e6
    updates: #350
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 0e7929ef0272a95e5d24a23f15de3a0bb88a094c
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Oct 25 14:03:07 2018 +0530

    glusterd: raise default transport.listen-backlog
    
    Problem:
    data center setups with large number of bricks with replication
    causes a flood of connections from bricks and self-heal daemons
    to glusterd causing connections to be dropped due to insufficient
    listener socket backlog queue length
    
    Solution:
    raise default value of transport.listen-backlog to 1024
    
    Change-Id: I879e4161a88f1e30875046dff232499a8e2e6c51
    fixes: bz#1642850
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 053b1309dc8fbc05fcde5223e734da9f694cf5cc
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Sep 23 16:59:58 2018 +0530

    afr: thin-arbiter 2 domain locking and in-memory state
    
    2 domain locking + xattrop for write-txn failures:
    --------------------------------------------------
    - A post-op wound on TA takes AFR_TA_DOM_NOTIFY range lock and
    AFR_TA_DOM_MODIFY full lock, does xattrop on TA and releases
    AFR_TA_DOM_MODIFY lock and stores in-memory which brick is bad.
    
    - All further write txn failures are handled based on this in-memory
    value without querying the TA.
    
    - When shd heals the files, it does so by requesting full lock on
    AFR_TA_DOM_NOTIFY domain. Client uses this as a cue (via upcall),
    releases AFR_TA_DOM_NOTIFY range lock and invalidates its in-memory
    notion of which brick is bad. The next write txn failure is wound on TA
    to again update the in-memory state.
    
    - Any incomplete write txns before the AFR_TA_DOM_NOTIFY upcall release
    request is got is completed before the lock is released.
    
    - Any write txns got after the release request are maintained in a ta_waitq.
    
    - After the release is complete, the ta_waitq elements are spliced to a
    separate queue which is then processed one by one.
    
    - For fops that come in parallel when the in-memory bad brick is still
    unknown, only one is wound to TA on wire. The other ones are maintained
    in a ta_onwireq which is then processed after we get the response from
    TA.
    
    Change-Id: I32c7b61a61776663601ab0040e2f0767eca1fd64
    updates: bz#1579788
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit aae1c402b74fd02ed2f6473b896f108d82aef8e3
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Oct 3 23:58:37 2018 +0530

    glusterd: ensure volinfo->caps is set to correct value.
    
    With the commit febf5ed4848, during the volume create op,
    we are setting volinfo->caps to 0, only if any of the bricks
    belong to the same node and brickinfo->vg[0] is null.
    Previously, we used to set volinfo->caps to 0, when
    either brick doesn't belong to the same node or brickinfo->vg[0]
    is null.
    
    With this patch, we set volinfo->caps to 0, when either brick
    doesn't belong to the same node or brickinfo->vg[0] is null.
    (as we do earlier without commit febf5ed4848).
    
    fixes: bz#1635820
    Change-Id: I00a97415786b775fb088ac45566ad52b402f1a49
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit c5d285b173f253be19458a6ba4470671978ab698
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Oct 24 15:23:34 2018 +0530

    posix : fix coverity issues in posix-inode-fd-ops.c
    
    This patch fixes CID: 1356526 and 1382369 : Argument cannot be negative
    
    Change-Id: I1aab5be2d217479db9f67a26b62854a0b38c1747
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 0ca6773eaf5aeb507ebc72d2c2f61902eeff414c
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Oct 8 19:33:58 2018 +0530

    tests: correction in tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t
    
    Patch https://review.gluster.org/#/c/glusterfs/+/19135/ has
    optimised glusterd test cases by clubbing the similar test
    cases into a single test case.
    
    https://review.gluster.org/#/c/glusterfs/+/19135/15/tests/bugs/glusterd/bug-1293414-import-brickinfo-uuid.t
    test case has been deleted and added as a part of
    tests/bugs/glusterd/optimized-basic-testcases-in-cluster.t
    
    In the original test case, we create a volume with two bricks,
    each on a separate node(N1 & N2). From another node in cluster(N3),
    we try to detach a node which is hosting bricks. It fails.
    
    In the new test, we created volume with single brick on N1.
    and from another node in cluster, we tried to detach N1. we
    expect peer detach to fail, but peer detach was success as
    the node is hosting all the bricks of volume.
    
    Now, changing the new test case to cover the original test case scenario.
    
    Please refer https://bugzilla.redhat.com/show_bug.cgi?id=1642597#c1 to
    understand why the new test case is not failing in centos-regression.
    
    fixes: bz#1642597
    
    Change-Id: Ifda12b5677143095f263fbb97a6808573f513234
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 06bad119b8c773a34cd2942d665112fbf7799788
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Tue Oct 9 11:34:08 2018 +0530

    features/namespace: NULL pointer deferencing clang fix
    
    Removed VALIDATE_OR_GOTO check on "this"
    
    Updates: bz#1622665
    
    Change-Id: Ie0d74525901ebf9daa1a5e788a035db6dc5d8c06
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 8d2a684ba102c5b2f558ac9bee819500da94421e
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Oct 24 18:09:09 2018 +0530

    geo-rep : fix high sev coverity isuue
    
    This patch fixes CID: 1382374: USE_AFTER_FREE.
    
    Change-Id: If408f52ee291312fb83095126ebd6bb79ae95e26
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit ee1982b083c06ddaebfc4b6da8a0827f3b7c24a9
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Oct 16 14:06:10 2018 +0530

    shard : fix coverity issue in shard.c
    
    This patch fixes CID:
    1394664 : CHECKED_RETURN
    1356534 : Macro compares unsigned to 0 (NO_EFFECT)
    1356532 : Macro compares unsigned to 0 (NO_EFFECT)
    
    updates: bz#789278
    
    Change-Id: I04d64fd8c007627611710dc56109b76eeb59333a
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit e15a5a5cc67fa3323722353bb4ccca0ea41aa594
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Wed Oct 24 18:11:13 2018 +0530

    cluster/ec : Prevent volume create without redundant brick
    
    Problem:
    EC volumes can be created without any redundant brick.
    
    Solution:
    Updated the conditional check to avoid volume create without
    redundant brick.
    
    fixes: bz#1642448
    Change-Id: I0cb334b1b9378d67fcb8abf793dbe312c3179c0b
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit 87613d265a1a394d785daeed569b384cd74c6574
Author: Han Han <hhan@redhat.com>
Date:   Mon Oct 15 09:53:06 2018 +0800

    mount.glusterfs: A more explicit check to avoid identical mounts
    
    Change check condition from
    "[[:space:]+]${mount_point}[[:space:]+]fuse" to
    "[[:space:]+]${mount_point}[[:space:]+]fuse.glusterfs". Fix false
    postive check result for mount points of other FUSEes, such as "fuse.sshfs".
    
    Change-Id: I13898b50a651a8f5ecc3a94d01b3b5de37ec4cbc
    fixes: bz#1640026
    Signed-off-by: Han Han <hhan@redhat.com>

commit cf5b13896d65b6916634976a3a5f61ddeefbc19c
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Oct 22 21:16:53 2018 +0530

    leases:Mark the fop conflicting if lease_id not set
    
    Glusterfs leases expects lease_id to be set and sent
    for each fop to determine conflict resolution with the
    existing lease.
    Incase if not set (most likely if there is an older
    client in a mixed cluster), it makes sense to consider
    it as conflicitng fop and recall the lease.
    
    Also fixed the return status check for __remove_lease(),
    wherein non-negative value is considered as success case.
    
    Change-Id: I5bcfba4f7c71a5af7cdedeb03436d0b818e85783
    updates: #350
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 63a8d72736aec13ae90eb1a425ffd2078e5236ad
Author: Arjun <arjsharm@redhat.com>
Date:   Mon Oct 22 13:08:53 2018 +0530

    src/glusterd-snapshot-utils.c: dereferencing the snap_vol before freeing it
    
    The patch fixes CID: 1325520
    
    Change-Id: Ic7d3fac6adabe96d1d44f13b57d6dc67da0476d1
    updates: bz#789278
    Signed-off-by: Arjun <arjsharm@redhat.com>

commit c34e4161f3cb6539ec83a9020f3d27eb4759a975
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Oct 18 14:06:04 2018 +0530

    glusterfs: During reconfigure set log-level per xlator level
    
    Problem: In brick_mux environment, while a user has enabled brick-log-level
             for anyone volume, it automatically enables for other volumes
             also those are attached with same brick.
    
    Solution: A log-level option is automatically enabled for other volumes
              because log-level saved in glusterfsd_ctx and ctx is common for
              volumes those are attached with same brick. To resolve it
              set log level for all children xlator's at the time of the graph
              reconfigure at io-stat xlator.
    
    Change-Id: Id9a6efa05d286e0bea2d47f49292d084e7bb2fcf
    fixes: bz#1640495
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 1be6703b1005bf572cea70f2254d7b5a8ed02351
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sun Oct 7 17:44:19 2018 +0530

    glusterd: set integer instead of string
    
    dict_get_str_boolean expects a integer, so we need
    to set all the boolean variables as integers to
    avoid log messages like below:
    
    [2018-09-10 03:55:19.236387] I [dict.c:2838:dict_get_str_boolean] (-->/usr/local/lib/libgfrpc.so.0(rpc_clnt_reconnect+0xc2) [0x7ff7a83d0452] -->/usr/local/lib/glusterfs/4.2dev/rpc-transport/socket.so(+0x65b0) [0x7ff7a06cf5b0] -->/usr/local/lib/libglusterfs.so.0(dict_get_str_boolean+0xcf) [0x7ff7a85fc58f] ) 0-dict: key transport.socket.ignore-enoent, integer type asked, has string type [Invalid argument]
    
    This patch addresses all such instances in glusterd.
    
    Change-Id: I7e1979fcf381363943f4d09b94c3901c403727da
    updates: bz#1193929
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 68299b244372b1668c1708bff15a239649226dee
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sun Oct 14 19:54:48 2018 +0530

    cli: Fix heap-buffer-overflow issue reported by ASAN
    
    GF_MALLOC was being used to allocate memory which is
    not initialized. strcat is used on it which could
    result in buffer overflow if it contains garbage before
    '\0'. So changed it to GF_CALLOC.
    
    Traceback:
    
    ==23427==ERROR: AddressSanitizer: heap-buffer-overflow ...
    WRITE of size 5 at 0x6080000083fe thread T3
     #0 0x7fb60966991c in __interceptor_strcat ...
     #1 0x48adc0 in config_parse ...
     #2 0x48cde8 in cli_cmd_gsync_set_parse ...
    ...
    
    Updates: bz#1633930
    Change-Id: I3710f011d8139984b1898265d84d150c9bdc962b
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit f73b4476b15f9d6d3dc3c8e20c9742aacd857f9f
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Oct 18 17:15:58 2018 +0530

    cluster/afr : Check for UP bricks before starting heal
    
    Problem:
    Currently for replica volume, even if only one brick is UP
    SHD will keep crawling index entries even if it can not
    heal anything.
    
    In thin-arbiter volume which is also a replica 2 volume,
    this causes inode lock contention which in turn sends
    upcall to all the clients to release notify locks, even
    if it can not do anything for healing.
    
    This will slow down the client performance and kills the
    purpose of keeping in memory information about bad brick.
    
    Solution: Before starting heal or even crawling, check if
    sufficient number of children are UP and available to check
    and heal entries.
    
    Change-Id: I011c9da3b37cae275f791affd56b8f1c1ac9255d
    updates: bz#1640581
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit bd4d8b182662e08cccc57efa1616651df448b445
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Oct 23 11:50:37 2018 +0530

    glusterd: improve logging for stage_deleted flag
    
    Change-Id: I5f0667a47ddd24cb00949c875c19f3d1dbd8d603
    fixes: bz#1605077
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 874ce6ef6e33f1493c888760714503ac992b708d
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Mon Oct 8 15:58:17 2018 +0530

    rpc/rpc-lib: Uninitialized argument value of a function
    
    trav->saved_at.tv_sec is not initialized.
    
    Calling "list_empty" function before initializing "trav".
    
    Updates: bz#1622665
    
    Change-Id: Ib5c2703a07a9c56ccd115001aca500f7a23c4a2e
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit 4634bb05cc82526e5c55e60746ae5d167f28bea0
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Sat Sep 29 11:02:58 2018 +0800

    md-cache: request cached xattrs at stat/fstat
    
    Ganesha always operate file by filehandle, and translates to
    glusterfs's stat/fstat many time.
    
    Change-Id: Idd0dc33c31131331ac948754c8b7f898777c31d3
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 3dea105556130abd4da0fd3f8f2c523ac52398d1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Oct 21 17:32:52 2018 +0530

    tests: check for shd up status in bug-1637802-arbiter-stale-data-heal-lock.t
    
    Problem:
    https://review.gluster.org/#/c/glusterfs/+/21427/ seems to be failing
    this .t spuriously. On checking one of the failure logs, I see:
    
    22:05:44 Launching heal operation to perform index self heal on volume patchy has been unsuccessful:
    22:05:44 Self-heal daemon is not running. Check self-heal daemon log file.
    22:05:44 not ok 20 , LINENUM:38
    
    In glusterd log:
    [2018-10-18 22:05:44.298832] E [MSGID: 106301] [glusterd-syncop.c:1352:gd_stage_op_phase] 0-management: Staging of operation 'Volume Heal' failed on localhost : Self-heal daemon is not running. Check self-heal daemon log file
    
    But the tests which preceed this check whether via a statedump if the shd is
    conected to the bricks, and they have succeeded and even started
    healing. From glustershd.log:
    
    [2018-10-18 22:05:40.975268] I [MSGID: 108026] [afr-self-heal-common.c:1732:afr_log_selfheal] 0-patchy-replicate-0: Completed data selfheal on 3b83d2dd-4cf2-4ea3-a33e-4275be40f440. sources=[0] 1  sinks=2
    
    So the only reason I can see launching heal via cli failing is a race where
    shd has been spawned but glusterd has not yet updated in-memory that it is up,
    and hence failing the CLI.
    
    Fix:
    Check for shd up status before launching heal via CLI
    
    Change-Id: Ic88abf14ad3d51c89cb438db601fae4df179e8f4
    fixes: bz#1641344
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 9eab065769d4b4fd41821232746fb8f1235bead4
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Sat Sep 29 11:58:42 2018 +0800

    posix: fill glusterfs.posix.* acl xattrs at dict
    
    Change-Id: I0730a037f96c4386c72ecf2f61c71ec17ffbc1b0
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 826e03db0903abab852bda37d6d77f3dd0f83cc6
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Oct 18 19:35:40 2018 +0800

    md-cache: fix dict leak of cached xattr
    
    Change-Id: I52f8e13e68528ba9679537ffdddf58ec08f9fd0c
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 92c22abb440ba8f8025441b16f3811b05927a16d
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Thu Oct 18 17:30:09 2018 +0530

    xlators: some high severity coverity fixes
    
    Fixes: 124759 1288787
    
    Change-Id: Ib8999242fc3ea5f4ea80246659899d2d4f06c506
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit ac9976f0c52306f4f2d9b11dcf6a830d1ec2e445
Author: Varsha Rao <varao@redhat.com>
Date:   Thu Oct 18 12:03:37 2018 +0530

    performance/write-behind: Fix NULL dereference issue
    
    This patches fixes the following coverity issues:
    CID: 1396101, 1396102 - Dereference null return value.
    
    Change-Id: I7ec783a61c06a1378863e974ff6e0baae418aec2
    updates: bz#789278
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit e1a9c23b83b8d46bf44a7a9952da0c61c8a46c79
Author: Arjun Sharma <arjsharm@redhat.com>
Date:   Mon Oct 15 17:37:36 2018 +0530

    protocol/server: added check for positve value in server-handshake.c
    
    This patch fixes CID 1124651
    
    Change-Id: I6f33954f08cfdd7cb4236f9a81ec7980f81d19e7
    updates: bz#789278
    Signed-off-by: Arjun <arjsharm@redhat.com>

commit c5f5ce2a9b1c085209cae21a7e1df5f60bc1a7da
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Thu Oct 18 14:15:40 2018 +0530

    rdma: coverity fixes
    
    Fixes CID: 1382442 1382415 1382379 1382355
    
    Change-Id: Ia712e37cb5a6db452d3178386394f87f83b85d38
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit 59629f1da9dca670d5dcc6425f7f89b3e96b46bf
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Thu Oct 18 18:25:46 2018 +0530

    mount/fuse: return ESTALE instead of ENOENT on all inode based operations
    
    This patch is continuation of commit
    fb4b914ce84bc83a5f418719c5ba7c25689a9251. This patch extends that
    logic to all inode based operations and not just open(dir).
    
    <snip>
    
    mount/fuse: never fail open(dir) with ENOENT
    
    open(dir) being an operation on inode should never fail with
    ENOENT. If gfid is not present, the appropriate error is ESTALE. This
    will enable kernel to retry open after a revalidate lookup.
    
    </snip>
    
    Change-Id: I6313f520827e9af725485631cb6a9d9718243bc4
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1627620

commit 0819a9af02cc76b5549c822d5c088e2c740a60d7
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Tue Sep 25 16:58:24 2018 +0530

    cluster/ec: NULL pointer deferencing clang fix
    
    Removing VALIDATE_OR_GOTO check on "this"
    
    Updates: bz#1622665
    
    Change-Id: Ic7cffbb697da814f835d0ad46e25256da6afb406
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 15c99765e0597b835d92560fc926067313848c88
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Oct 17 14:26:14 2018 +0530

    storage/posix: Do not fail entry creation fops if gfid handle already exists
    
    PROBLEM:
    tests/bugs/shard/bug-1251824.t fails occasionally with EIO due to gfid
    mismatch across replicas on the same shard when dd is executed.
    
    CAUSE:
    Turns out this is due to a race between posix_mknod() and posix_lookup().
    
    posix mknod does 3 operations, among other things:
    1. creation of the entry itself under its parent directory
    2. setting the gfid xattr on the file, and
    3. creating the gfid link under .glusterfs.
    
    Consider a case where the thread doing posix_mknod() (initiated by shard)
    has executed steps 1 and 2 and is on its way to executing 3. And a
    parallel LOOKUP from another thread on noting that loc->inode->gfid is NULL,
    tries to perform gfid_heal where it attempts to create the gfid link
    under .glusterfs and succeeds.  As a result, posix_gfid_set() through
    MKNOD (step 3) fails with EEXIST.
    
    In the older code, MKNOD under such conditions was NOT being treated
    as a failure. But commit e37ee6d changes this behavior by failing MKNOD,
    causing the entry creation to be undone in posix_mknod() (it's another
    matter that the stale gfid handle gets left behind if lookup has gone
    ahead and gfid-healed it).
    All of this happens on only one replica while on the other MKNOD succeeds.
    
    Now if a parallel write causes shard translator to send another MKNOD
    of the same shard (shortly after AFR releases entrylk from the first
    MKNOD), the file is created on the other replica too, although with a
    new gfid (since "gfid-req" that is passed now is a new UUID. This leads
    to a gfid-mismatch across the replicas.
    
    FIX:
    The solution is to not fail MKNOD (or any other entry fop for that matter
    that does posix_gfid_set()) if the .glusterfs link creation fails with EEXIST.
    
    Change-Id: I84a5e54d214b6c47ed85671a880bb1c767a29f4d
    fixes: bz#1638453
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 273c895747d073d43a1e8617218d4bfd2cf13f18
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Oct 17 13:08:59 2018 +0530

    ctr: fix coverity issue in changetimerecorder.c
    
    This patch fixes CID:
    1396179: Read from pointer after free
    1396178: Use after free
    
    Change-Id: I47a2e4aa257e0c4dbdf2e1fd2e0748902764463f
    fixes: bz#789278
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 145e180517054626d07892219fdee689b703c218
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Oct 17 15:40:04 2018 +0530

    shard : fix newly introduced coverity
    
    This patch fixes CID: 1396177: NULL dereference.
    
    updates: bz#789278
    
    Change-Id: Ic5d302a5e32d375acf8adc412763ab94e6dabc3d
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 219cd649fdbd7bfd6c2268a0a4f66bcc15918e31
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Oct 17 18:48:19 2018 +0530

    debug/io-stats: io stats filenames contain garbage
    
    As dict_unserialize does not null terminate the value,
    using snprintf adds garbage characters to the buffer
    used to create the filename.
    The code also used this->name in the filename which
    will be the same for all bricks for a volume. The
    files were thus overwritten if a node contained
    multiple bricks for a volume. The code now uses
    the conf->unique instead if available.
    
    Change-Id: I2c72534b32634b87961d3b3f7d53c5f2ca2c068c
    fixes: bz#1640165
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 6257276d9de3f15643f159b2ec627a67c84fc23d
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Fri Oct 12 10:31:04 2018 +0530

    api: fill out attribute information if not valid
    
    translators like readdir-ahead selectively retain entry information of
    iatt (gfid and type) when rest of the iatt is invalidated (for write
    invalidating ia_size, (m)(c)times etc). Fuse-bridge uses this
    information and sends only entry information in readdirplus
    response. However such option doesn't exist in gfapi. This patch
    modifies gfapi to populate the stat by forcing an extra lookup.
    
    Thanks to Shyamsundar Ranganathan <srangana@redhat.com> and Prashanth
    Pai <ppai@redhat.com> for tests.
    
    Change-Id: Ieb5f8fc76359c327627b7d8420aaf20810e53000
    Fixes: bz#1630804
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 24dbcfb6ebaab021e2db4f63bd66f3b06192bc89
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Sat Sep 29 12:10:46 2018 +0800

    posix: return more xattrs at getxattr/fgetxattr when client request
    
    Change-Id: I37ac6186b3631979d2503d1b185a61b8094dbd0d
    Updates: bz#1634220
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 573253d250972dad60ec28cd101f9facd82a0fe2
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Oct 16 16:45:34 2018 +0530

    nfs : fix coverity issue in nfs3.c
    
    This patch fixes CID 1274073.
    
    updates: bz#789278
    
    Change-Id: I34146bfdfe19bae4592062e710a89ab07b2c5c07
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit a9c232319f28376f88ac624ac132413ec408b784
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Oct 16 14:48:00 2018 +0530

    trash : fix high sev coverity issue in trash.c
    
    This patch fixes CID 1288790: RESOURCE_LEAK.
    
    updates: bz#789278
    
    Change-Id: I34bb410f1d3027e2d4c21044e87e319360344e04
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 0402a13914084219db3a6f6867117b8757112b24
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Oct 8 19:22:53 2018 +0530

    glusterfsd: fix the asan leak message
    
    Fixes below trace of ASan:
    
    Direct leak of 130 byte(s) in 1 object(s) allocated from:
        #0 0x7fa794bb5850 in malloc (/lib64/libasan.so.4+0xde850)
        #1 0x7fa7944e5de9 in __gf_malloc ../../../libglusterfs/src/mem-pool.c:136
        #2 0x40b85c in gf_strndup ../../../libglusterfs/src/mem-pool.h:166
        #3 0x40b85c in gf_strdup ../../../libglusterfs/src/mem-pool.h:183
        #4 0x40b85c in parse_opts ../../../glusterfsd/src/glusterfsd.c:1049
        #5 0x7fa792a98720 in argp_parse (/lib64/libc.so.6+0x101720)
        #6 0x40d89f in parse_cmdline ../../../glusterfsd/src/glusterfsd.c:2041
        #7 0x406d07 in main ../../../glusterfsd/src/glusterfsd.c:2625
    
    
    updates: bz#1633930
    Change-Id: I394b3fc24b7a994c1b03635cb5e973e7290491d3
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 46689e34b920147cb7222d166e7b85ef8f105b60
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Oct 14 02:15:40 2018 +0300

    servers-helpers.c: reduce clang warnings on dead initialization.
    
    Assign a value to a parameter on its definition.
    Removes tens of clang warnings.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I828bacb4033111af6162772a554cc5c6b2820169

commit 39a1db1402bea36cb5727a5041440f10bf4660e9
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Oct 15 20:45:18 2018 -0400

    coverity: ignore tainted access reported in gf_free
    
    Coverity reports tainted pointer access in _gf_free if the pointer passed in
    was used by any IO related function by the caller. The taint within gf_free
    is a false positive, as the tainted region is from the passed in pointer
    till its allocated lenght, and not for contents before the pointer (i.e
    the GF_MEM_HEADER_SIZE bytes before the passed in pointer), as that is
    exclusively handled by the gf_alloc family of functions.
    
    CID: 1228602, 1292646, 1292647, 1292648, 1292649, 1383192, 1383195, 1389691
    
    Should additionally fix,
    CID: 1292650, 1292651, 1357874, 1382373, 1382404, 1382407
    
    Change-Id: I48c5a4028e7b0224c432bbc30f8c29408c2a466b
    Updates: bz#789278
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit f179d09326c519abb1868de79598719b93219544
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Oct 15 20:50:26 2018 -0400

    glusterfsd: Fix coverity issues around unused values
    
    This patch fixes,
    CID: 1274064, 1274232
    
    The fix is to not add into the return dict the throughput
    and time values on error computing the same. The pattern
    applied is the same as when an error occurs during adding
    either the throughput or the time value to the dict.
    
    Change-Id: I33e21e75efbc691f18b818934ef3bf70dd075097
    Updates: bz#789278
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit f50625e7b08814e8e1d06a733e9b3516e9cea5e2
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Oct 9 15:57:31 2018 +0800

    libgfapi: Send path with "." for the root when loc.parent is set
    
    fixes: bz#1582516
    Change-Id: Ia9649d7c3c0930dfec656d364cf6e9a98c774dd2
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit a303cd1acc3c9ff475fe5ece643de4cbea1c1a51
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Oct 10 21:37:07 2018 +0530

    gfapi: Bug fixes in leases processing code-path
    
    This patch fixes below issues in gfapi lease code-path
    * 'glfs_setfsleasid' should allow NULL input to be
       able to reset leaseid
    * Applications should be allowed to (un)register for
      upcall notifications of type GLFS_EVENT_LEASE_RECALL
    * APIs added to read contents of GLFS_EVENT_LEASE_RECALL
      argument which is of type "struct glfs_upcall_lease"
    
    Change-Id: I3320ddf235cc82fad561e13b9457ebd64db6c76b
    updates: #350
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 593bbb28d95d1ebf11aa6f4d1f256529ed2dba88
Author: Milind Changire <mchangir@redhat.com>
Date:   Sat Oct 13 10:15:42 2018 +0530

    libglusterfs: fix sys_socket coverity issue
    
    CID 1396081:  Control flow issues  (UNREACHABLE)
    
    Change-Id: Ifad303853224cb9abc91c1083bb1529f4c13b1d3
    updates: bz#789278
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 98f68cf115a30a101d3be2252ecbe1391720ed88
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Oct 13 00:56:42 2018 +0300

    Multiple xlators: perform gettimeofday() not under lock
    
    While it may slightly reduce accuracy, I think it's better to
    acquire the time outside a lock and then memcpy the value while
    under lock.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ic8fb94a56c4fa2d3b13e59767e13646fb39342ba

commit fd70a7d790710da01a8ddd56785a28ab54e07550
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Oct 10 01:25:41 2018 +0530

    mount : fix high sev coverity issues in mount3.c
    
    This patch fixes CID 1395067, 1388767 and 1395068.
    
    updates: bz#789278
    
    Change-Id: Ie92252281bf559dd29fab462e121445ff4d3b865
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 386f1d7926e4497fc2a905367ade2e3f6972eba7
Author: Raghavendra Gowdappa <rgowdapp@redhat.com>
Date:   Thu Oct 11 16:22:28 2018 +0530

    cluster/dht: fixes to unlinking invalid linkto file
    
    If unlinking of an invalid linkto file failed in lookup-everywhere
    codepath, lookup was failed with EIO. The rational as per the comment
    was,
    
    <snip>
    
    /* When dht_lookup_everywhere is performed, one cached
      *and one hashed file was found and hashed file does
      *not point to the above mentioned cached node. So it
      *was considered as stale and an unlink was performed.
      *But unlink fails. So may be rebalance is in progress.
      *now ideally we have two data-files. One obtained during
      *lookup_everywhere and one where unlink-failed. So
      *at this point in time we cannot decide which one to
      *choose because there are chances of first cached
      *file is truncated after rebalance and if it is chosen
      *as cached node, application will fail. So return EIO.
    */
    
    </snip>
    
    However, this reasoning is only valid when
    * op_errno is EBUSY, indicating rebalance is in progress
    * op_errno is ENOTCONN as wecannot determine what was the status of
      file on brick.
    
    Hence this patch doesn't fail lookup unless unlink fails with an
    either EBUSY or ENOTCONN
    
    Change-Id: Ife55f3d97fe557f3db05beae0c2d786df31e8e55
    Fixes: bz#1635145
    Signed-off-by: Raghavendra Gowdappa <rgowdapp@redhat.com>

commit 7152ace0b3586289be068f09e2c20cf0a8d2d166
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Oct 15 08:26:32 2018 -0400

    core: libuuid-devel breakage
    
    The #include "uuid.h" left over from using .../contrib/uuid is debatably
    incorrect now that we use the "system header" file /usr/include/uuid/uuid.h
    from libuuid-devel.
    
    Unfortunately this is complicated by things like FreeBSD having its own
    /usr/include/uuid.h, and the e2fsprogs-libuuid uuid.h in installed - as
    most third-party packages in FreeBSD are - in /usr/local as
    /usr/local/include/uuid/uuid.h
    
    With a system header file it should at least be #include <uuid.h>, and
    even better as #include <uuid/uuid.h>, much like the way <sys/types.h>
    and <net/if.h> are included. Using #include <uuid/uuid.h> guarantees
    not getting the /usr/include/uuid.h on FreeBSD, but clang/cc knows to
    find "system" header files like this in /usr/local/include; with or
    without the -I/... from uuid.pc. Also using #include "uuid.h" leaves
    the compiler free to find a uuid.h from any -I option it might be passed.
    (Fortunately we don't have any at this time.)
    
    As we now require libuuid-devel or e2fsprogs-libuuid and configure will
    exit with an error if the uuid.pc file doesn't exist, the HAVE_LIBUUID
    (including the #elif FreeBSD) tests in compat-uuid.h are redundant. We
    are guaranteed to have it, so testing for it is a bit silly IMO. It may
    also break building third party configure scripts if they omit defining
    it. (Just how hard do we want to make things for third party developers?)
    
    Change-Id: I7317f63c806281a5d27de7d3b2208d86965545e1
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit e627977617dd765f6b58a70882c6acda6c6aab6e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Oct 5 11:32:21 2018 +0530

    features/shard: Hold a ref on base inode when adding a shard to lru list
    
    In __shard_update_shards_inode_list(), previously shard translator
    was not holding a ref on the base inode whenever a shard was added to
    the lru list. But if the base shard is forgotten and destroyed either
    by fuse due to memory pressure or due to the file being deleted at some
    point by a different client with this client still containing stale
    shards in its lru list, the client would crash at the time of locking
    lru_base_inode->lock owing to illegal memory access.
    
    So now the base shard is ref'd into the inode ctx of every shard that
    is added to lru list until it gets lru'd out.
    
    The patch also handles the case where none of the shards associated
    with a file that is about to be deleted are part of the LRU list and
    where an unlink at the beginning of the operation destroys the base
    inode (because there are no refkeepers) and hence all of the shards
    that are about to be deleted will be resolved without the existence
    of a base shard in-memory. This, if not handled properly, could lead
    to a crash.
    
    Change-Id: Ic15ca41444dd04684a9458bd4a526b1d3e160499
    updates: bz#1605056
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 76cc1ea613e038ced4bc6ae26233cb0681b63be5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Sep 28 13:03:38 2018 +0530

    libglusterfs/dict: Add sizeof()-1 variants of dict functions
    
    One needs to be very careful about giving same key for the key and
    SLEN(key) arguments in dict_xxxn() functions. Writing macros that
    would take care of passing the SLEN(key) would help reduce this
    burden on the developer and reviewer.
    
    updates: bz#1193929
    Change-Id: I312c479b919826570b47ae2c219c53e2f9b2ddef
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit c962e2cbd73e78f31e690f7b1f8456616006c543
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 12 14:25:00 2018 +0530

    glusterd/geo-rep: Fix memory corruption
    
    Problem and Analysis:
    The length of canonical format of uuid is 36 but
    'GF_UUID_BUF_SIZE 50' was being used everywhere.
    glusterd/geo-rep code was earlier using strncpy,
    but recently changes to memcpy with the drive
    to avoid strncpys. This leads to memory corruption
    and glusterd is crashing without a core with geo-rep
    creation with ASAN build.
    
    Fix:
    'GF_UUID_BUF_SIZE 37' (+ 1 for NULL byte)
    And change geo-rep to use UUID_CANONICAL_FORM_LEN
    instead
    
    Updates: bz#1633930
    Change-Id: Ibd347d542b92e64a96ce06780cda643557233bc7
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit ac074e03437faf6f2f0897e6d9e7249ac0599b64
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Oct 11 23:39:13 2018 +0530

    cli: Fix memory leaks reported by ASAN
    
    This patch addresses memory leaks other than
    'gf_cli_rsp' response structure.
    
    Updates: bz#1633930
    Change-Id: Idc5940dca623e33bc01004a9324bc435fc60b006
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit f6789462610ab5bae029cb114fa27453a54c8f9c
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Oct 11 12:20:10 2018 +0530

    libglusterfs : fix newly introduced coverity defect
    
    CID: 1396060
    updates: bz#789278
    
    Change-Id: Ia25aa9a4ca7505e747aa92bb3ae81415da7d19d1
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 7bf95631b52bd05b06122180f8bd4aa62c70b1a9
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Oct 10 10:31:18 2018 +0530

    core: glusterfsd keeping fd open in index xlator
    
    Problem: At the time of processing GF_EVENT_PARENT_DOWN
             at brick xlator, it forwards the event to next xlator
             only while xlator ensures no stub is in progress.
             At io-thread xlator it decreases stub_cnt before the process
             a stub and notify EVENT to next xlator
    
    Solution: Introduce a new counter to save stub_cnt and decrease
              the counter after process the stub completely at io-thread
              xlator.
              To avoid brick crash at the time of call xlator_mem_cleanup
              move only brick xlator if detach brick name has found in
              the graph
    
    Note: Thanks to pranith for sharing a simple reproducer to
          reproduce the same
    
    fixes bz#1637934
    Change-Id: I1a694a001f7a5417e8771e3adf92c518969b6baa
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 777412c5e8a1e8613061fef31bd8a60d4cd54b6e
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Thu Oct 11 04:00:08 2018 +0530

    libglusterfs: fix log message in options.c
    
    This patch fixes https://github.com/gluster/glusterfs/issues/519
    
    Credits: "Fabian Wannenmacher <@wanneut>"
    
    Updates: bz#1193929
    
    Change-Id: If8d60c3379093a868ad6ba8c2ad86a4b99d35f2c
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 09baa5d7fb91d1f50976807f1da0f7bbf177fa00
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Oct 11 12:12:38 2018 +0530

    features/locks: Fix Coverity issues
    
    CID:
    1395812 Explicit null dereferenced
    1356542 Dereference null return value
    
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=86261835&defectInstanceId=26407100&mergedDefectId=1395812
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=86261835&defectInstanceId=26407215&mergedDefectId=1356542
    
    Change-Id: I2c20972a8080fa7a70b88eab0688b9cf734bbf24
    updates: bz#789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit b2e592a4a9beb0ef3f8986e3ff3a630981bcad1f
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Oct 11 17:36:43 2018 +0530

    snapshot : fix high sev coverity on snapview-server.c
    
    This patch fixes CID 1325525 (double free).
    
    updates: bz#789278
    
    Change-Id: I26a5f428dde83dd7708815f06830decf4068b94c
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 67624335f5d2ca9c8b0c7d1630e7186cb5cdd6d6
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Tue Oct 9 12:07:11 2018 +0530

    performance/nl-cache: clang fix
    
    Argument with 'nonnull' attribute passed null.
    
    Adding a check to avoid the issue.
    
    Updates: bz#1622665
    
    Change-Id: I1d3a166e154a51da59bebb93a49f5174e593c98e
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit 16704e575cfece60ed3d4ad413aaefabcae0474b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Oct 11 12:51:03 2018 +0530

    cli: Fix memory leaks reported by ASAN
    
    'gf_cli_rsp' structure has 'op_errstr' and 'dict.dict_val'
    which could get allocated by xdr and should be freed. This
    patch takes care of all instances of the same.
    
    Updates: bz#1633930
    Change-Id: I2a5d129ffe85cfca743c89edb45b658f3ce688cb
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 33eefcec0ad2df3d6aac0ac225b64c61d42e56ef
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Wed Oct 10 12:29:21 2018 +0530

    mgmt/glusterd: clang fix
    
    Argument with 'nonnull' attribute passed null.
    
    Added checks to avoid the issues.
    
    Updates: bz#1622665
    
    Change-Id: I0dba1185cee5baba3c124d687560a06fe182381e
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit 522dcab94ae9938c072cf50062b507cedafdc011
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Mon Oct 1 12:39:48 2018 +0530

    mgmt/glusterd: NULL pointer dereferencing clang fix
    
    Problem: dereferencing of this->name; volinfo and xl
    can be null.
    
    Solution: Replaced this->name with apropriate names in few places,
    added a null check to avoid dereferencing of volinfo,
    and introduced a goto out statement, such that null pointer value is
    not passed to the function volgen_xlator_link when xl becomes NULL.
    
    Updates: bz#1622665
    
    Change-Id: I77616bd23f58328cb6dbe681914a028991d49abb
    Signed-off-by: Shwetha Acharya <sacharya@redhat.com>

commit 62faf7d37bd8b6be6657b1e3b61f92eac5b84653
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Oct 11 15:16:41 2018 +0530

    socket: use accept4/paccept for nonblocking socket
    
    This reduces the no. of syscalls on Linux systems from 2, accept(2) and
    fcntl(2) for setting O_NONBLOCK, to a single accept4(2).  On NetBSD, we
    have paccept(2) that does the same, if we leave signal masking aside.
    
    Added sys_accept which accepts an extra flags argument than accept(2).
    This would opportunistically use accept4/paccept as available.  It would
    fallback to accept(2) and fcntl(2) otherwise.
    
    While at this, the patch sets FD_CLOEXEC flag on the accepted socket fd.
    
    BUG: 1236272
    Change-Id: I41e43fd3e36d6dabb07e578a1cea7f45b7b4e37f
    fixes: bz#1236272
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 807ec72d740a4548c250cc660c89fc59d2f191d6
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Thu Oct 11 11:27:44 2018 +0530

    performance/write-behind: NULL pointer passed to a nonnull parameter
    
    Problem: wb_directory_inode->lock can be null.
    
    Solution: added a condition, if(!wb_directory_inode->lock.spinlock)
    to address the issue (checked one of the attributes of union lock
    to ensure that union is not null).
    
    Updates: bz#1622665
    Change-Id: I0749ee16aa2c23f51d4b4c7b0979d494bcd4d90e
    Signed-off-by: Shwetha Acharya <sacharya@redhat.com>

commit 23e96fd93c021d4647b940a47df2250fe9159a3b
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Oct 9 15:17:57 2018 +0530

    socket: set FD_CLOEXEC on all sockets
    
    For more information, see http://udrepper.livejournal.com/20407.html
    
    BUG: 1236272
    Change-Id: I25a645c10bdbe733a81d53cb714eb036251f8129
    fixes: bz#1236272
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 4511435fd353b98551be17d02e1d91e8896164ed
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 24 10:31:23 2018 +0530

    README: add a section for giving hints on testing
    
    Change-Id: I1529494504c38172f56759c0f06231864e32df24
    updates: bz#1193929
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 46b970f64a797aa67b9cdb3704e24b8392398191
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Oct 10 13:46:22 2018 +0530

    cluster/dht : Fix coverity issue
    
    To check if the gfid is null or not
    we should use function gf_uuid_is_null
    
    CID: 1382364
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=86243257&defectInstanceId=26374360&mergedDefectId=1382364
    
    Change-Id: I81944b823c9ee6e6dcc9695f64f7e5966e0d7030
    updates: bz#789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 27d3d481bd66c30aaa9e30040aadee7325e9995e
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Wed Sep 19 03:35:38 2018 -0400

    gfapi: fix crash of using uninitialized fs->ctx
    
    0  0x00007fb3db3a2ee4 in pub_glfs_fini (fs=0x7f8977d63f00) at glfs.c:1236
    1  0x00007fb3db3a2065 in pub_glfs_new (volname=0x7f80de4d4d40 "openfs1")
        at glfs.c:784
    2  0x00007fb3db5cf089 in glusterfs_get_fs (params=...,
        up_ops=up_ops@entry=0x7fb3ca643130)
        at /usr/src/debug/nfs-ganesha/src/FSAL/FSAL_GLUSTER/export.c:889
    3  0x00007fb3db5cf99a in glusterfs_create_export (
        fsal_hdl=0x7fb3db7e2490 <GlusterFS+112>, parse_node=0x7fb3ca6387d0,
        err_type=<optimized out>, up_ops=0x7fb3ca643130)
        at /usr/src/debug/nfs-ganesha/src/FSAL/FSAL_GLUSTER/export.c:1011
    4  0x00007fb3e11c485f in mdcache_fsal_create_export (
        sub_fsal=0x7fb3db7e2490 <GlusterFS+112>,
        parse_node=parse_node@entry=0x7fb3ca6387d0,
        err_type=err_type@entry=0x7fb3c0bef140, super_up_ops=<optimized out>)
        at /usr/src/debug/nfs-ganesha/src/FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_main.c:281
    
    (gdb) p errno
    $1 = 12
    
    Change-Id: I3dd5b84b52962ceb0b5d4f9b4f475bf4aa724292
    updates: bz#1626313
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 196b32423af9a5088056fe10ea22d01494670931
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Oct 10 12:18:55 2018 +0530

    afr: prevent winding inodelks twice for arbiter volumes
    
    Problem:
    In an arbiter volume, if there is a pending data heal of a file only on
    arbiter brick, self-heal takes inodelks twice due to a code-bug but unlocks
    it only once, leaving behind a stale lock on the brick. This causes
    the next write to the file to hang.
    
    Fix:
    Fix the code-bug to take lock only once. This bug was introduced master
    with commit eb472d82a083883335bc494b87ea175ac43471ff
    
    Thanks to  Pranith Kumar K <pkarampu@redhat.com> for finding the RCA.
    
    fixes: bz#1637802
    Change-Id: I15ad969e10a6a3c4bd255e2948b6be6dcddc61e1
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 4da0d93f8703c7247fece9d9fb471742e6fd7c33
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Thu Oct 4 14:22:23 2018 +0530

    libglusterfs: NULL pointer dereferencing clang fix
    
    Avoided NULL pointer dereferencing by doing GF_VALIDATE_OR_GOTO for rvec
    
    Updates: bz#1622665
    
    Change-Id: I650e0203796dd705d79060f9506fc6c559b30f56
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit 6472b43cfdb7454f1c1f1faf57ff13643d62fad7
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Oct 9 19:40:31 2018 +0530

    locks : fix coverity issue
    
    This patch fixes CID 1356544 and 1356539.
    Both are of type NULL_RETURNS.
    
    Change-Id: I2ef7c3ff9929c4d85b79fff00e835ebee3ff3ce0
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 0f2113cb0c3f9dff028fb45a62ec2d1d82b4cb66
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Sep 25 03:40:44 2018 -0400

    socket: clear return value if error is going to be handled in event thread
    
    Change-Id: Ibce94f282b0aafaa1ca60ab927a469b70595e81f
    updates: bz#1626313
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 2d96ce8faa277809c0c94aca54320483889f577d
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue Sep 25 13:22:47 2018 +0200

    all: fix warnings on non 64-bits architectures
    
    When compiling in other architectures there appear many warnings. Some
    of them are actual problems that prevent gluster to work correctly on
    those architectures.
    
    Change-Id: Icdc7107a2bc2da662903c51910beddb84bdf03c0
    fixes: bz#1632717
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 0cda00f08d3d620be89830bad9d0e252648388e9
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Sep 25 03:42:47 2018 -0400

    logging: fix file handle leak when calls glfs_set_logging more times
    
    Closes the log file and reopens it to prevent leakage of file handles.
    
    Change-Id: Idfaa479961bb0088004d0d5558bdb0eb32cff632
    updates: bz#1626313
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 21c6b3e5ab47b615f0b18a27ce74285490f43a7a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Oct 7 20:39:22 2018 +0300

    libglusterfs/src/logging.c: reduce the use of strings
    
    I did not see a good reason to copy the temp strings str1 and str2
    into msg string, and just used str1 (sprintf'ed str2 into it first).
    Hope it makes logging somewhat faster, but I also hope there's more
    room for improvement for faster logging.
    
    Renamed str1 to logline and str2 to msg for better readability.
    
    Also, remove dead assignment in _gf_msg() (clang complained).
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I19457d705c0b043937d96a4db35d087bb8e9b35a

commit eb5382f9475900ec95cfd52278f46553dbde18a6
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Sep 5 15:30:25 2018 -0400

    features/snapview-client: replace gf_log with gf_msg
    
    Change-Id: I87f01d86f50eb2fca21febb0ea3e77fbd152eb93
    updates: bz#1626610
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 07072898bec59189e1cec991fb179d04ac485a7a
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Oct 4 19:17:56 2018 +0530

    cloudsync: coverity fix
    
    CID: 1394649 1394657
    Issue: Explicit null dereferenced
    
    Change-Id: Ic1040ffa5548e1ecd49cfdc9a8716be445cbdf0f
    Updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 3fa73bfdb5183cb8077d43c3c219c3fd9e9a1b65
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Oct 8 13:21:38 2018 +0530

    cli: memory leak issues reported by asan
    
    With this fix, a run on 'rpc-coverage.t' passes properly.
    This should help to get started with other fixes soon!
    
    Change-Id: I257ae4e28b9974998a451d3b490cc18c02650ba2
    updates: bz#1633930
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8d4c5e022bba1b99786ce13f407c27024beccc23
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Oct 9 12:43:32 2018 +0530

    cliutils :  python2 to python3 compat
    
    This patch fixes import issue in cliutils.
    
    Provided solution is to use relative import.
    
    Change-Id: I14c9a0b528ef52e7c91f6b17b569c68c2ced8912
    updates: #411
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 73bb13e7bc45f5f5ce73302312f2094de1fee9a3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Sep 28 11:10:46 2018 +0530

    extras: Script to collect system-stats
    
    For debugging performance issues we found that this script is very
    useful.  Script collects the stats of vmstat/iostat/top/sar to get
    metrics about memory/disk/cpu/network respectively at the configured
    interval. It is very important to collect all these metrics at the
    same time so that they can be correlated easily, so made this into a
    script
    
    fixes bz#1633926
    Change-Id: Iea52e55179b21c505953722c8898293fe92cb8de
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 667026f506d71bc5e5e740477bdc546f08c413ee
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Wed Sep 26 05:39:47 2018 -0400

    syncop: check syncenv status before pthread_cond_timedwait() to avoid 600s timeout
    
    If a syncenv_task starts after syncenv_destroy, the syncenv_task enters
    a 600s timeout cond timedwait, and syncenv_destroy must waits it timeout.
    
    Change-Id: I972a2b231e50cbebd3c71707800e58033e40c29d
    updates: bz#1626313
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 3108fb24e72ab3f60ef0aa9cf3ffd8a3a33ce424
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Oct 8 21:35:04 2018 +0530

    rpc: coverity fixes
    
    CID: [1] 1394646 Unchecked return value from library
    CID: [2] 1394633 Unused value
    CID:     1382443 Sleeping while holding a lock [This is intentional]
    
    [1] https://scan6.coverity.com/reports.htm#v40014/p10714/fileInstanceId=86159112&defectInstanceId=26360786&mergedDefectId=1394646
    [2] https://scan6.coverity.com/reports.htm#v40014/p10714/fileInstanceId=86159365&defectInstanceId=26360919&mergedDefectId=1394633
    
    Change-Id: I03086f7a9672c9f50a2bc44cdbce0006c887357b
    updates: bz#789278
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit b5f75e337c19d4fed85d4dcf15cf47f02fea5f6a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sat Oct 6 09:20:24 2018 +0530

    events: python2 to python3 compat
    
    1. Fix imports
    2. Use universal_newlines flag in Popen
    3. encode msg used in 'sendto'
    
    Updates: #411
    Change-Id: Ieacdc2ba86953ff3a2e9d9b9a97157e8e0e36836
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit fb6e8d0d0ca21b16d331fa69da9b9dadf6c5c35d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Oct 3 00:45:09 2018 -0400

    georep: python2 to python3 compat - syscalls
    
    1. ctypes/syscalls
        A) arguments is expected to be encoded
        B) Raw conversion of return value from bytearray into string
    2. struct pack/unpack - Raw converstion of string to bytearray
    3. basestring -> str
    
    Updates: #411
    Change-Id: I80f939adcdec0ed0022c87c0b76d057ad5559e5a
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 860a990811c5364bc2de04ca07096cde312ff209
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Oct 5 13:28:03 2018 -0400

    packaging: remove RHEL5-isms from glusterfs.spec(.in)
    
    CentOS5 too
    
    It's been a couple of years since we stopped doing anything with
    RHEL/CentOS 5
    
    Change-Id: I83e78fa84b93fa5baddaf3fab92736d692a9bbca
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 5bc4594dabc08fd4de1940c044946e33037f2ac7
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Oct 2 08:54:28 2018 +0530

    core: glusterfsd keeping fd open in index xlator
    
    Problem: Current resource cleanup sequence is not
             perfect while brick mux is enabled
    
    Solution: 1) Destroying xprt after cleanup all fd associated
                 with a client
              2) Before call fini for brick xlators ensure no stub
                 should be running on a brick
    
    Change-Id: I86195785e428f57d3ef0da3e4061021fafacd435
    fixes: bz#1631357
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 31b6308c646a84c5064d2fb31dc45363a71b131a
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sun Oct 7 14:22:06 2018 +0530

    cli: Resource leak coverity fix
    
    This patch fixes CID 1175017.
    
    Change-Id: I4968c35489aeb5bfa0461b2edf2a0d73b7f03c14
    updates: bz#789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 82b7f8d77974bd2133705cce0d9188756dab3563
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Oct 5 01:38:15 2018 +0530

    changetimerecorder : fix coverity issue
    
    This patch fixes CID : 1124725
    Issue : Resource leak
    
    updates: bz#789278
    
    Change-Id: I2afe65875fa393fd2d2f90b6f7cf7f6782dabf89
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 1d392e2970fb5b1d2f8cf2904e7b7e5d32a21882
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Mon Oct 1 17:02:09 2018 +0530

    features/bit-rot: NULL pointer deferencing clang fix
    
    Problem: local could be NULL
    
    Added condition checks to address this issue
    
    Updates: bz#1622665
    
    Change-Id: I7be7dacc5386a77441385240b43f22d85074b69d
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 6a6709489525e2c438a3ec1974771247bc2e07d4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sun Oct 7 15:47:13 2018 +0530

    tests: add get-state command to test
    
    When geo-replication session is running, run
    "gluster get-state" command to test.
    
    https://review.gluster.org/#/c/glusterfs/+/20461/
    patch fixes glusterd crash, when we run get-state
    command with geo-rep session configured.
    Adding the test now.
    
    Fixes: bz#1598345
    Change-Id: I56283fba2c782f83669923ddfa4af3400255fed6
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 76bd93c7b889deafd4d5e1e9387714a6c1918ac7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 17 17:17:54 2018 +0530

    xlators/experimental: move template files to '.c.in' type
    
    This is critical because we shouldn't be applying the automated
    coding standard (clang-format) tool on these files.
    
    This patchset is done by below steps:
    
    * clang-format -i ${filename}
    
    This creates syntax errors. Fix them using below two commands:
    * sed -i -e 's/ @/@/g' ${filename}
    * sed -i -e 's/,@/, @/g' ${filename}
    
    With this, these files are having minimum changes requried to
    compile, and is as close to the coding standard as possible.
    
    * git rename ${filename} ${filename}.in
    
    Updates: bz#1564149
    Change-Id: Icf90f7f81d6fa4400be4826e094fdff8e64508d0
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c1f04098227c17bbebe286871c75524c80eb8b3a
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Oct 4 19:20:30 2018 +0530

    cli : coverity fix in cli-rl.c
    
    This patch fixes CID 1395248.
    Issue : Resource leak
    
    updates: bz#789278
    
    Change-Id: I2fd4e36ac2c2a034e56883436abfc5199b095026
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 07cb6a486502fa0f7ea141e7600ec67015383546
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Oct 3 20:40:12 2018 +0530

    dht: coverity fixes
    
    CID: 1356541 Issue: Dereference null return value
    CID: 1382411 Issue: Dereference after null check
    CID: 1391409 Issue: Unchecked return value
    
    Change-Id: Id3d4feb4e88df424003cc8e8a1540e77bbe030e3
    Updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit f87d1a1e3374596bc5ee9dad2aee8d12db657da5
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Oct 5 01:14:34 2018 +0530

    libglusterfs : fix coverity issue in stack.c
    
    This patch fixes CID : 1395323.
    Issue : Uninitialized scalar variable (UNINIT)
    
    updates: bz#789278
    
    Change-Id: Id9567ca2ff9b5a36b9014afa70cc5795fe67161d
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 3be7116d39ff767a24e5206de584a3c5f3afe8ef
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Mon Sep 24 14:53:18 2018 +0530

    features/compress: NULL pointer dereferencing clang fix
    
    Added a Label "err" to avoid NULL pointer dereferencing
    
    Updates: bz#1622665
    
    Change-Id: I7ec02a9cbbc482c2cf77f66e5692e86cd251cd53
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit 2066466dadf658dcf7226267ada50faaa103b7f3
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Oct 4 16:40:08 2018 +0530

    cloudsync: coverity fix
    
    CID: 1394631 1394634 1394643  1394645 1394652 1394655  1394661 1394666
         1394669 1394670 1394671
    
    Issue:  Argument cannot be negative
    
    Change-Id: Id4a9b1adcc271374971e788f161d91e8c9ac442f
    Updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit a6128d64ec4c25eba002941ae68a9e9a72805704
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Oct 3 21:09:15 2018 +0530

    libglusterfs: coverity fix
    
    CID: 1395829 Issue: Uninitialized pointer read
    
    Change-Id: I2e03d7b2a2f28f4a46408402ae03beba0f4c8308
    Updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 4f7729748ee7d79e41dec9682a4fbbb2378ed5ac
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Oct 1 14:09:03 2018 -0400

    dht: volume_options 'options' collision with nfs-ganesha's 'options'
    
    When dht was converted to xlator_api, the variable 'options' was not
    changed to dht_options, the same as was done to all the other xlators
    that were converted to xlator_api.
    
    Thus the reference to 'options' in dht.c is not resolved until runtime,
    and the RTlinker's search path starts with symbols in the executable,
    i.e. ganesha.nfsd's 'options'. (Which is obviously not the right one.)
    
    The unused extern references to 'options' (now dht_options) in nufa.c
    and switch.c is curious.
    
    Change-Id: Idf4a5d5fbd39aadfa5a4b529bceea65a3cbdf8f3
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit dbafe63ea5602db3ad65a3e4fba15b6ee97776ce
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Oct 4 10:31:45 2018 +0200

    Reduce execution time of bug-1559004-EMLINK-handling.t
    
    This patch reduces the execution time of bug-1559004-EMLINK-handling.t
    from ~14 minutes to ~90 seconds. To do so, it creates some fake hard
    links directly on the brick instead of creating them through the
    volume.
    
    Change-Id: I9715ff1a4eba47574c733d4f28e68f42f56a7d3f
    updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 83a89296a3d12a3fc2a643c0630be5ce659204ea
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Oct 1 17:30:19 2018 -0400

    mgmt/glusterd: use proper path to the volfile
    
    Till now, glusterd was generating the volfile path for the snapshot
    volume's bricks like this.
    
    /snaps/<snap name>/<brick volfile>
    
    But in reality, the path to the brick volfile for a snapshot volume is
    
    /snaps/<snap name>/<snap volume name>/<brick volfile>
    
    The above workaround was used to distinguish between a mount command used
    to mount the snapshot volume, and a brick of the snapshot volume, so that
    based on what is actually happening, glusterd can return the proper volfile
    (client volfile for the former and the brick volfile for the latter). But,
    this was causing problems for snapshot restore when brick multiplexing is
    enabled. Because, with brick multiplexing, it tries to find the volfile
    and sends GETSPEC rpc call to glusterd using the 2nd style of path i.e.
    
    /snaps/<snap name>/<snap volume name>/<brick volfile>
    
    So, when the snapshot brick (which is multiplexed) sends a GETSPEC rpc
    request to glusterd for obtaining the brick volume file, glusterd was
    returning the client volume file of the snapshot volume instead of the
    brick volume file.
    
    Change-Id: I28b2dfa5d9b379fe943db92c2fdfea879a6a594e
    fixes: bz#1635050
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 6b58e8426a36bc544c06a599311999bf89ad04f2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Oct 3 16:34:54 2018 +0530

    glusterd: ignore RPC events when glusterd is shutting down
    
    When glusterd receives a SIGTERM while it receives RPC
    connect/disconnect/destroy events, the thread might lead to a crash
    while accessing rcu_read_lock () as the clean up thread might have
    already freed up the resources. This is more observable when glusterd
    comes up with upgrade mode = on during upgrade process.
    
    The solution is to ignore these events if glusterd is already in the
    middle of cleanup_and_exit ().
    
    Fixes: bz#1635593
    Change-Id: I12831d31c2f689d4deb038b83b9421bd5cce26d9
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 0153fcfcbd0e442824ec9bc19122a253512e98ea
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Mon Sep 24 16:44:45 2018 +0530

    mgmt/glusterd: NULL pointer dereferencing clang fix
    
    Added checks to avoid NULL pointer dereferencing
    
    Updates: bz#1622665
    
    Change-Id: I745c1f3ba4df0e486ce99301843f9f13d01c00e0
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit 04a98cd88e9e9eb9f7bc6c174671d82ece666fbf
Author: shujun10086 <shujun.huang@nokia-sbell.com>
Date:   Tue Oct 2 08:37:17 2018 +0000

    cli: fix glusterd memory leak cause by "gluster v status volume_name"
    
    If use this command every some seconds for example 15s to check gluster brick
    status, the glusterd will use about 1G memory in a year. free the value of rsp
    in gf_cli_status_cbk. glusterd allocate the value of rsp and send it to cli, but
    cli do not free the value, that cause glusterd memory leak.
    
    fixes: bz#1635480
    Change-Id: I3f19cd0d4b791ae1b35f9664b3a668b1579f1178
    Signed-off-by: shujun10086 <shujun.huang@nokia-sbell.com>

commit fa091f07841dac48fff1fa505b88f7b7edea9edc
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Tue Sep 25 16:45:48 2018 +0530

    mgmt/glusterd: NULL pointer deferencing clang fix
    
    Changed this->name to "glusterd"
    
    Updates: bz#1622665
    
    Change-Id: Ic8ce428cefd6a5cecf5547769d8b13f530065c56
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit 8a4b6f079b516e939fd55c4014dfcbd20142462f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Sep 30 16:54:03 2018 +0200

    python: remove shebangs of non-main scripts and make others executable
    
    Some of the scripts that have a #!/usr/bin/python3 shebang do not have a
    main() like function. These scripts will not get executed but only
    imported. They do not need the shebang.
    
    A few others are not installed with 'make install', but do have a main()
    like function. These scripts are expected to be used by developers for
    different tasks (mostly code generation). Marking these scripts
    executable to make it easier to identify them.
    
    Change-Id: I73541471deb7e0830766b804786244e73dfe4221
    Updates: #411
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit c96778b354ea82943442aab158adbb854ca43a52
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Sep 23 23:53:39 2018 +0530

    rpc: make binding to port 0 as the default if no option is provided
    
    Right now, if no option is provided, the default port is assumed,
    which is 24007. Ideally, for 'glusterfsd' processes, it is better
    to not assume there are any ports given, so it can start listening
    on any port which is available.
    
    This helps us to cleanup the dependencies on glusterd from glusterfsd
    at the moment. No changes would be done to glusterd code, but making
    the right defaults helps to make glusterfsd more independent process
    later.
    
    NOTE: This patch is a reduced version of below set of patches:
     * https://review.gluster.org/14613/ &
     * https://review.gluster.org/14670/ &
     * https://review.gluster.org/14671/
    
    Credits: Prasanna Kumar Kalever <pkalever@redhat.com>
    
    updates: bz#1343926
    Change-Id: Ib874e10505e7366dc56ba754458252b67052e653
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ff00ce1d55e34ec77e93e742533928edf653e2d2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Sep 28 06:11:52 2018 -0400

    georep: python2 to python3 compat - pickle
    
    Handle py2 and py3 compatibility for pickling and unpickling.
    Geo-rep pickles and unpickles reading sys.stdin and sys.stdout streams.
    py2 and py3 compatibility expects the streams to be opened in binary
    mode but the sys.stdout objects are different in python2
    and python3
    
    python2:
    >>> type(sys.stdout)
    <type 'file'>
    
    python3:
    >>> type(sys.stdout)
    <class '_io.TextIOWrapper'>
    
    So in order to access binary stream, using sys.stdin.buffer in python3
    
    Updates: #411
    Change-Id: I1a633ccdddff5baf0cf05a8b493add39ddf75bd7
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit d06bbb617ee9449759cd069141a085c313524298
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Sep 28 05:52:36 2018 -0400

    georep: python2 and python3 compat - bytes-str
    
    1. Fix fdopen used for pid file
    2. Fix sha256 checksum calculation
    
    Updates: #411
    Change-Id: Ic173d104a73822c29aca260ba6de872cd8d23f86
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit f7a81f4be38bd3e1859268d09306918fa303a82c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Sep 28 07:48:13 2018 -0400

    georep: python2 to python3 compatibility-mount write
    
    python3 expects byte string for os.write. This works
    for both py2 and py3. Fixed the same for geo-rep
    mount testing code path.
    
    Updates: #411
    Change-Id: I2dfedcb0869457707bcca4d2847ef0d52bff1987
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit bf27b8257dba9a0826a3732bc1c763b6f6122a8c
Author: Raghavendra Manjunath <raghavendra@redhat.com>
Date:   Wed Sep 12 10:24:23 2018 -0400

    MAINTAINERS: Add Sunny Kumar as a peer for snapshots
    
    Change-Id: I691a56125143fb60735073595d8c5e43273c9bc1
    fixes: bz#1634102
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit f054b511057ada37790bfb518c70d6631ed11d93
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sun Sep 23 16:42:54 2018 +0530

    cli: handle negative scenarios
    
    When control flow reaches negative case code block, we added
    "goto out" statement without assigning ret to -1.
    
    This patch assigns return value to -1, before going to the lable "out".
    
    Change-Id: I6db651a3c9ca285ade9ee1ca23d0abe6b36fda3a
    updates: bz#1193929
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 1c0facf59a85b1256a52e7a99b30743283a4c9cf
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Sep 26 02:58:10 2018 +0530

    index : fix coverity issues in index.c
    
    This patch fixes CID 1356508 and 1356577.
    
    Change-Id: I09bc5398fbf6ee49fc066b42aaedf1170df39df8
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 1f2aa9acb78f6d004c0ea36f9827087484871344
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Sep 28 10:46:46 2018 +0200

    fuse: prevent error message "can't shift that many"
    
    On systems where /bin/sh is not Bash, running plain mount.glusterfs
    gives the unhelpful error "can't shift that many".
    
    The argument parsing can be a little improved. Adding a check for the
    number of arguments, minimal two (Gluster ip:/volume, and mountpoint),
    but possibly more (-o, -v etc.).
    
    With the additional check, running 'mount.glusterfs -h' now shows the
    following messags:
    
        Usage: /sbin/mount.glusterfs <server>:<volume/subdir> <mountpoint> -o<options>
        Options:
        man 8 mount.glusterfs
        To display the version number of the mount helper: /sbin/mount.glusterfs -V
    
    Change-Id: I50e3ade0c6217fab4155f35ad8cb35d99d52e133
    Fixes: bz#1564890
    Reported-by: Alexander Zimmermann <alexander.zimmermann96@gmail.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit baeb5fb5cad8ec7158cd7afb36aa7476f081aee7
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Sep 20 18:45:14 2018 +0530

    glusterd: fix coverity issues
    
    This patch fixes CID 1274175, 1175018.
    
    1274175: Buffer size warning
    1175018: Resource leak
    
    Change-Id: Id18960c249447b8dae35de3ad92bc570e62ddb09
    updates: bz#789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit d00a2a1b398346bbdc5ac9b3ba4b09fb1ce1e699
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Sep 28 13:47:33 2018 -0400

    mdcache: Fix asan reported potential heap buffer overflow
    
    The char pointer mdc_xattr_str in function mdc_xattr_list_populate
    is malloc'd and doing a strcat into a malloc'd region can
    overflow content allocated based on prior contents of the
    memory region.
    
    Added a NULL terimation to the malloc'd region to prevent
    the overflow, and treat it as an empty string.
    
    Change-Id: If0decab669551581230a8ede4c44c319ff04bac9
    Updates: bz#1633930
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 7cf6688e9bb8384b383745751758d747a940ca3f
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Sep 26 21:54:06 2018 +0530

    libglusterfs : fix coverity issue in store.c
    
    This patch fixes CID 1395102 and 1395103.
    
    Change-Id: Ia6093dc6a04dce3f523e015cf1d6d4c6bfccc1f6
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 5b91555a583da1ad7918c3fb16a2d92be1a19e9c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Sep 24 14:12:45 2018 -0400

    python3: assume python3 unless building _packages_ on sys without py3
    
    The jenkins release-new job runs on a CentOS 7 box, which does not
    have python3. As a result it runs (autogen.sh and) configure before
    producing the dist tar file, converting all the python3 shebangs to
    python2 shebangs in the dist tar file.
    
    Then when that tar file is "carried" to, e.g. Fedora koji build
    system to build packages, the shebangs are incorrect, despite having
    originally been correct in the git repo.
    
    Change-Id: I5154baba3f6d29d3c4823bafc2b57abecbf90e5b
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 4756e27bbcd8ccc11180843ad23b833e8a5cf22c
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Sep 18 07:58:58 2018 -0400

    rpc: failed requests immediately if rpc connection is down
    
    In the case glfs_fini is ongoing, some cache xlators like readdir-ahead,
    continues to submit requests. Current rpc submit code ignores
    connection status and queues these internally generated requests. These
    requests then got cleaned up after inode table has been destroyed,
    causing crash.
    
    Change-Id: Ife6b17d8592a054f7a7f310c79d07af005087017
    updates: bz#1626313
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 406aa9809cf7e841f3f5e32fbab0097d4779dca3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 10 19:28:12 2018 +0530

    monitoring: create dump dir if it doesn't exist
    
    Fixes: bz#1624006
    
    Change-Id: Ie78be72e2492cd02c1376852bb90f1e6661d9bea
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit f1e9b878ce2067db83a0baa5f384eda87287719d
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Sep 25 23:36:48 2018 +0530

    glusterd: make sure that brickinfo->uuid is not null
    
    Problem: After an upgrade from the version where shared-brick-count
    option is not present to a version which introduced this option
    causes issue at the mount point i.e, size of the volume at mount
    point will be reduced by shared-brick-count value times.
    
    Cause: shared-brick-count is equal to the number of bricks that
    are sharing the file system. gd_set_shared_brick_count() calculates
    the shared-brick-count value based on uuid of the node and fsid of
    the brick. https://review.gluster.org/#/c/glusterfs/+/19484 handles
    setting of fsid properly during an upgrade path. This patch assumed
    that when the code path is reached, brickinfo->uuid is non-null.
    But brickinfo->uuid is null for all the bricks, as the uuid is null
    https://review.gluster.org/#/c/glusterfs/+/19484 couldn't reached the
    code path to set the fsid for bricks. So, we had fsid as 0 for all
    bricks, which resulted in gd_set_shared_brick_count() to calculate
    shared-brick-count in a wrong way. i.e, the logic written in
    gd_set_shared_brick_count() didn't work as expected since fsid is 0.
    
    Solution: Before control reaches the code path written by
    https://review.gluster.org/#/c/glusterfs/+/19484,
    adding a check for whether brickinfo->uuid is null and
    if brickinfo->uuid is having null value, calling
    glusterd_resolve_brick will set the brickinfo->uuid to a
    proper value. When we have proper uuid, fsid for the bricks
    will be set properly and shared-brick-count value will be
    caluculated correctly.
    
    Please take a look at the bug https://bugzilla.redhat.com/show_bug.cgi?id=1632889
    for complete RCA
    
    Steps followed to test the fix:
    1. Created a 2 node cluster, the cluster is running with binary
    which doesn't have shared-brick-count option
    2. Created a 2x(2+1) volume and started it
    3. Mouted the volume, checked size of volume using df
    4. Upgrade to a version where shared-brick-count is introduced
    (upgraded the nodes one by one i.e, stop the glusterd, upgrade the node
    and start the glusterd).
    5. after upgrading both the nodes, bumped up the cluster.op-version
    6. At mount point, df shows the correct size for volume.
    
    fixes: bz#1632889
    Change-Id: Ib9f078aafb15e899a01086eae113270657ea916b
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 6b273c1644595472d17f08c891aab62cebecbcbe
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Sep 18 07:38:48 2018 -0400

    libgfapi: fix use after freed of clnt when dispatching events
    
    Avoid dispatching events to mgmt after freed,
    unreference mgmt after the event_dispatch_destroy.
    
    Change-Id: I5b762b37901de70a955661df0aff95bf055ba4ea
    updates: bz#1626313
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 341ba81448e869ae388b4b37556e47f6bf7413a5
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Sep 23 11:04:22 2018 +0300

    Quota related files: use dict_{setn|getn|deln|get_int32n|set_int32n|set_strn}
    
    In a previous patch (https://review.gluster.org/20769) we've
    added the key length to be passed to dict_* funcs, to remove the need
    to strlen() it. This patch moves some code to use it.
    
    Please review carefully.
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: If4f425a9827be7c36ccfbb9761006ae824a818c6

commit 064b24900e1f5e3ba3087f7c6a0249613ebed61f
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Mon Sep 24 16:37:51 2018 +0530

    cluster/ec: variable-length array (VLA) declaration clang fix
    
    Problem: variable-length array size becomes zero
    
    Modified array size to size+1 while declaring
    
    Updates: bz#1622665
    
    Change-Id: I98ee8447c87f37c36c49f50058292e8c1757a1f9
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 5ad31b5b17fa220c9b26b6df730e127c76448ac5
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Mon Sep 24 15:12:25 2018 +0530

    features/locks: NULL pointer deferencing clang fix
    
    Added checks to avoid NULL pointer dereferencing
    
    Updates: bz#1622665
    
    Change-Id: I8e441c2931f406a6012e418127550bdf454a599a
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit 65aed1070cc2e44959cf3a0fbfde635de7e03103
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Sep 24 21:18:30 2018 +0530

    georep: python3 compatibility (Popen)
    
    The file objects for python3 by default is opened
    in binary mode where as in python2 it's opened
    as text by default.
    
    The geo-rep code parses the output of Popen assuming
    it as text, hence used the 'universal_newlines' flag
    which provides backward compatibility for the same.
    
    Change-Id: I371a03b6348af9666164cb2e8b93d47475431ad9
    Updates: #411
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 89636be4c73b12de2e11c75d8e59527bb243f147
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Sep 3 09:07:58 2018 -0400

    ctime: Provide noatime option
    
    Most of the applications are {c|m}time dependant
    and very few are atime dependant. So provide noatime
    option to not update atime when ctime feature is
    enabled.
    
    Also this option has to be enabled with ctime
    feature to avoid unnecessary self heal. Since
    AFR/EC reads data from single subvolume, atime
    is only updated in one subvolume triggering self
    heal.
    
    updates: bz#1593538
    Change-Id: I085fb33c882296545345f5df194cde7b6cbc337e
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit c006434c4f6d5762e826bd2ecc414b6d332d66c9
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Aug 20 17:54:32 2018 +0530

    nfs : fix coverity issues
    
    Fixes 1388608 and 1274073.
    
    updates: bz#789278
    Change-Id: Ibe2b948ae3b02feb938caffe81b2e484b4c7b221
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 62164ac0d242a271f19b0e0bb352af5f7df082ce
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Sep 24 20:43:54 2018 +0530

    georep: Fix python3 compatibility (configparser)
    
    '%' needs special handling in config and also removed
    duplicate misspelled 'changelog-archive-format' config.
    
    Updates: #411
    Change-Id: I33621a62bdf5f781ee62e6cedec0c2df3f5d70cf
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 173e89a6506bc8c727ce6d8e5ac84b59ad2e21de
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Sep 24 20:56:21 2018 +0530

    georep: Fix python3 compatibility (os.pipe)
    
    'os.pipe' returns pair of file descriptors
    which are non-inheritable by child processes.
    But geo-rep uses te inheritable nature of
    pipe fds to communicate between parent and
    child processes. Hence wrote a compatiable
    pipe routine which works well both with python2
    and python3 with inheritable nature.
    
    Updates: #411
    Change-Id: I869d7a52eeecdecf3851d44ed400e69b32a612d9
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 8f207feb260bc6112d5085859b43efc8378a4c5f
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Sep 24 13:21:58 2018 -0700

    features/marker: Avoid passing structures as parameters to functions
    
    Fixes CIDs: 1388779,1390242,1390057
    
    The patch does the following:
    
    1. Changes the prototype of mq_inspect_file_xattr() and mq_xattr_state()
    to have a parameter of struct iatt * instead of struct iatt.
    2. Remove unneeded struct iatt parameter from
    mq_inspect_directory_xattr()
    
    Change-Id: I1f6eabda042f0fe56d8c9bca010302f5e518dbe4
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit f1b2455b9d01bae8c4652fc3583a60ff7000410e
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Sep 21 16:03:22 2018 +0530

    glusterd: fix coverity issues
    
    This patch addreeses CID 1124812, 11248123, 1124833,
    and 1351706
    
    1. We have a null check after GF_ASSERT. GF_ASSERT does
    a null check and fails if it is null. So removing the
    redundant null checks.
    
    2. Added a log message to avoid unused value coverity issue
    
    Change-Id: Ib0d6dad8f40474afc8e5e60a531d37247cc8a081
    updates: bz#789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 31dcbb61487ac82b5ae61435add98b0fd1d5e8cc
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Mon Sep 24 15:03:18 2018 +0530

    mgmt/glusterd: NULL pointer dereferencing clang fix
    
    Added a condition check to resolve the issue
    
    Change-Id: I1954e91f7487c052caf5cf98c954d204242f0af9
    Updates: bz#1622665
    Signed-off-by: Shwetha Acharya <sacharya@redhat.com>

commit 5a3d87fd1239500873c31d38838706b64dbb1b91
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Sep 24 14:50:24 2018 +0530

    cluster/ec: Fix failure of tests/basic/ec/ec-1468261.t
    
    Problem:
    In this test we are relying on eager-lock time
    duration of 1 second to delay the post op + unlock phase
    of an entry fop so that in this 1 second we can kill 2
    bricks and dirty on directory could be set.
    
    Solution:
    To fix this issue, we should set the others.eager-lock
    option to "ON" explicitly in the beginning of this test.
    
    Change-Id: I19bbb9c15d7bdf96a96b20587c618192d0b740ef
    fixes bz#1632161
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit b64d08b56f5e76a6d337d6f6c81baec8a0ed7500
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Sep 14 13:42:20 2018 -0400

    api: old and new versioned symbols must appear in each section of gfapi.map
    
    It's probably not clear in .../doc/developer-guide/gfapi-symbol-versions.md
    that this is necessary, but it is.
    
    Change-Id: I0a8a74e3ecf474c93583f5ebc97507c4277542b0
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 607b91747574bb912477df5dd11c4e31cde4c0bf
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Sep 17 12:18:13 2018 +0530

    dht: Coverity fixes
    
    CID: 1274236 Issue: Logically dead code (op_errno will never be -1)
    CID: 1351652 Issue: Dereference after null check.
    (local->fd is dereferenced anyway and it should not be NULL ever for
    dht_readdirp_cbk.)
    
    Change-Id: Ied9c5f5b72536be1ca944237165acdc62b792e58
    updates: bz#789278
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 48a06e0eaff8b613c3e05d8168e8faff838b727f
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Sep 24 17:53:35 2018 +0530

    glusterfind: add logs to identify parsing phases
    
    Add logs to idenitfy start and finish of changelog parsing phases.
    
    Change-Id: Id250231f2af7829f887401d30ac98875ae1ae793
    fixes: bz#1632236
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 81ea27c82c30282dd1fb7d67458aa874b33f6797
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Sep 21 21:51:46 2018 +0200

    Update database profile group
    
    Some performance testing has revealed that pgbench performs 3x better
    when these options are set:
    
    performance.client-io-threads=on
    performance.open-behind=on
    performance.read-after-open=yes
    server.event-threads=4
    client.event-threads=4
    
    Change-Id: I36ce389f893a8af13aac5f8285104d749b73d098
    fixes: bz#1631886
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 257f71ea0ca30ddac2a202bb250df6bfa652751b
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Sep 24 15:26:01 2018 +0530

    geo-rep : fix log message in master.py
    
    This patch fixes spell mistake in log message.
    
    Change-Id: I84779c64aef6698cbc1a60ae1a82533e8a6a6e3d
    updates: bz#1193929
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 8297b909ab88e5ddb591cfb5aff0f06d14bd90cc
Author: Nigel Babu <nigelb@redhat.com>
Date:   Fri Sep 14 19:06:41 2018 +0530

    python3: Fix python3 compatibility
    
    Updates: #411
    Change-Id: I7c1eaa92cd4ac05c3667b760e0db2cddcfbbaed8
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit b7732b9c069179aaa71a3463400fa438d1769f6c
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Sep 21 12:45:12 2018 +0530

    glusterd: reduce length allocated to name
    
    In glusterd_proc_ and glusterd_svc_ structures name is having
    length of PATH_MAX, allocating NAME_MAX will be sufficient.
    
    Change-Id: I637ba00e1a80ca6a1ecc0c2dbf180c4633c1ca5b
    updates: bz#1193929
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 28bc9e4bf74fd31a9620478b0a0ed482798b5915
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Sep 21 11:55:12 2018 +0530

    glusterd: fix resource leak coverity issues
    
    This patch addresses CID 1288098,1370948 and 1382454
    
    key_fixed is allocated with memory but missed to free it.
    
    updates: bz#789278
    Change-Id: Iea805c668ba89759313f9e21b328757e570be97b
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 27402fcb27a7e9ea32a6a04fdc21b59af6320bb4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Sep 20 11:37:36 2018 +0530

    glusterd: fix coverity issues in glusterd-locks.c
    
    This patch addresses CID 1395254, CID 1382436.
    
    We are allocating memory to mgmt_lock_timer and key_dup. while doing
    GF_VALIDATE_OR_GOTO for mgmt_lock_timer_xl or  mgmt_lock_timer_ctx,
    if it is null going to out without freeing the memory. This patch
    will fix the issues.
    
    updates: bz#789278
    Change-Id: Ic6bfb2052982b16373f90cbbc53d2b2da052c01f
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f72f18b3bf7f9535827a059a5090476b3141723f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Sep 21 12:11:40 2018 +0530

    glusterd: don't wait for blockers flag for stop volume
    
    With commit 4f6ae8 even though the overall transaction time for gluster
    volume stop can be reduced, but based on testing it can't be guaranteed
    that the transaction can finish in 3 minutes before the unlock timer
    gets kicked in. The ground problem to this is the command serialization
    which atomic field 'blockers' does for volume stop operation.
    
    This patch removes that dependency for volume stop not to wait for
    blockers.
    
    Change-Id: Ifaf120115dc7ed21cf21e65e25c4ec7c61ab8258
    Fixes: bz#1631128
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 9d8f5a34c1ff4ae512f80fe9651508ae201c273e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Sep 20 10:14:26 2018 +0530

    afr: fix incorrect reporting of directory split-brain
    
    Problem:
    When a directory has dirty xattrs due to failed post-ops or when
    replace/reset brick is performed, AFR does a conservative merge as
    expected, but heal-info reports it as split-brain because there are no
    clear sources.
    
    Fix:
    Modify pending flag to contain information about pending heals and
    split-brains. For directories, if spit-brain flag is not set,just show
    them as needing heal and not being in split-brain.
    
    Fixes: bz#1626994
    Change-Id: I09ef821f6887c87d315ae99e6b1de05103cd9383
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit d901308a06c38fa53a3b07ed1641522a3248378d
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Sep 18 14:51:10 2018 +0530

    glusterfsd/mgmt : Check for NULL after creating frame
    
    CID: 1382390
    
    https://scan6.coverity.com/reports.htm#v42607/p10714fileInstanceId=85472585&defectInstanceId=26074725&mergedDefectId=1382390
    
    Change-Id: Iade073a5e72f29ad5e8f372955869bc287eb9793
    updates: bz#789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 30bfd1eb411fd762c36b77693da7ea6d73ea31c1
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Tue Sep 18 16:34:07 2018 +0530

    ctr: NULL pointer dereferencing clang fix
    
    Replaced this->name with "ctr"
    
    Updates: bz#1622665
    
    Change-Id: I49af42a5d77c98ffb34224c8800757b8986012ea
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit bbcec1a1caf95aad581083e7131feda04295f299
Author: Shwetha Acharya <sacharya@redhat.com>
Date:   Tue Sep 18 15:40:29 2018 +0530

    nfs/server: NULL pointer dereferencing clang fix
    
    Added some condition checks in nfs3.c and nlm4.c
    Updates: bz#1622665
    Change-Id: Ia10b8fff14f651df1360c9bb79d4476b282f54b5
    Signed-off-by: Shwetha Acharya <sacharya@redhat.com>

commit 2fd9d62691056b9f0601dbc2bf6f42626b015d07
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Sep 21 00:40:46 2018 +0530

    block : fix coverity in bd.c
    
    This patch fixes CID 1288097, 1128921, and 1128918
    all of type RESOURCE_LEAK.
    
    Change-Id: If39be19c6310eab9880de6f0bebb4f38604a40b2
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit ece878fac815db5a1ea4d0078a48a05dbcc0c276
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 18 12:15:57 2018 +0530

    cluster/afr: Make data eager-lock decision based on number of locks
    
    For both Virt and block workloads the file is opened multiple times
    leading to dynamically setting eager-lock to off for the workload.
    Instead of depending on the number-of-open-fds, if we change the
    logic to depend on number of inodelks, then it will give better
    performance than the earlier logic. When there is an eager-lock
    and number of inodelks is more than 1 we know that there is a
    conflicting lock, so depend on that information to decide whether
    to keep the current transaction go through delayed-post-op or not.
    
    Locks xlator doesn't have implementation to query number of locks in
    fxattrop in releases older than 3.10 so to keep things backward
    compatible in 3.12, data transactions will use new logic where as
    fxattrop transactions will use old logic. I am planning to send one
    more patch which makes metadata domain locks also depend on
    inodelk-count
    
    Profile info for a dd of 500MB to a file with another fd opened
    on the file using exec 250>filename
    
    Without this patch:
     0.14      67.41 us      16.72 us    3870.82 us  892 FINODELK
     0.59     279.87 us      95.71 us    2085.89 us  898 FXATTROP
     3.46     366.43 us      81.75 us    6952.79 us 4000 WRITE
    95.79  148733.99 us   50568.12 us  919127.86 us  273 FSYNC
    
    With this patch:
     0.00      51.01 us      38.07 us      80.16 us    4 FINODELK
     0.00     235.43 us     235.43 us     235.43 us    1 TRUNCATE
     0.00     125.07 us      56.80 us     193.33 us    2 GETXATTR
     0.00     135.86 us      62.13 us     209.59 us    2  INODELK
     0.00     197.88 us     155.39 us     253.90 us    4 FXATTROP
     0.00     450.59 us     394.28 us     506.89 us    2  XATTROP
     0.00      56.96 us      19.06 us     406.59 us   23    FLUSH
    37.81  273648.93 us      48.43 us 6017657.05 us   44   LOOKUP
    62.18    4951.86 us      93.80 us 1143154.75 us 3999    WRITE
    
    postgresql benchmark performance changed from ~1130 TPS to ~2300TPS
    randio fio job inside Ovirt based VM went from ~600IOPs to ~2000IOPS
    
    fixes bz#1630368
    Change-Id: If7f7388d2f08cf7f17ca517a4ea222560661dc36
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 3de6ba0cd369d1be957d25f96a0e460c9dd004a2
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Sep 19 15:49:27 2018 +0530

    extras: Add new options to group "virt"
    
    In some of the recent performance tests on gluster-as-vm-image-store
    use-case, it has been observed that sometimes the lone fuse thread can
    hit near-100% CPU utilization and become a performance bottleneck.
    Enabling client-io-threads (in addition to bumping up epoll threads on
    server and client side) has shown to be helpful in getting around this
    bottleneck and pushing more IOPs.
    
    Change-Id: I231db309de0e37c79cd44f5666da4cd776fefa04
    fixes: bz#1630798
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit b139bc58eb504adf5ef81658896c9283ae21f390
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Sep 3 15:49:02 2018 +0530

    dht: Operate internal fops with negative pid
    
    With root-squash on, all root credentials are converted to a
    random uid, gid(65535). And ideally this does not carry the necessary
    permission bits to carry out the operation. But posix-acl will allow
    operations from this inode as long as its ctx has the ngroup information
    and ngroup has the owner group information.
    
    The problem we ran into recently was somehow posix-acl xlator did not
    cache the ngroup info and some of the dht internal fops(layout setxattr)
    failed with root-squash enabled.
    
    DHT internal fops now use a negative pid to pretend that the operation
    is from an internal client so posix-acl allows them to pass
    
    Change-Id: I5bb8d068389bf4c94629d668a16015a95ccb53ab
    fixes: bz#1624796
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 5e8fd8b465761e6ab09187abd56ce9930652866b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Sep 19 18:38:01 2018 +0530

    tests: fix test case failure
    
    tests/bugs/glusterd/bug-1595320.t is failing in downstream.
    In downstream repo, enabling the brick multiplexing made
    interactive, so it will throw an prompt for the user input.
    As no input is provided during the test case execution, the
    test is failing.
    
    Using macro CLI instead of using gluster command, will
    bypass the interacive commands. so replacing the gluster
    command with CLI macro will address the issue.
    
    Change-Id: I6b39052d8e415a8ed08de7c80a91dadce155146a
    updates: bz#1193929
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 649e4378ad8e3a08f24322ea7c44a3903a6a6ce4
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Tue Sep 18 12:31:02 2018 +0530

    Quota: NULL pointer dereferencing clang Fix
    
    Added ternary operator to avoid NULL pointer dereferencing
    
    Updates: bz#1622665
    
    Change-Id: I903ec1973fd4bb6473d16e2680bd86ac3a20e093
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit 65bd1e2f94781bea5ad6eeb5b4d9f9f614660085
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Sep 18 17:09:28 2018 +0530

    storage/posix: Check if fd->inode is NULL before using it
    
    CID: 1395473, 1395472
    
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=85588219&defectInstanceId=26115956&mergedDefectId=1395472
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=85588219&defectInstanceId=26115961&mergedDefectId=1395473
    
    Change-Id: I2c3cc350e0ac156616df6f568ba28dbfa68064bf
    updates: bz#789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 5784a00f997212d34bd52b2303e20c097240d91c
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed May 30 15:27:52 2018 +0530

    cluster/afr: Use 2 domain locking in SHD for thin-arbiter
    
    With this change when SHD starts the index crawl it requests
    all the clients to release the AFR_TA_DOM_NOTIFY lock so that
    clients will know the in memory state is no more valid and
    any new operations needs to query the thin-arbiter if required.
    
    When SHD completes healing all the files without any failure, it
    will again take the AFR_TA_DOM_NOTIFY lock and gets the xattrs on
    TA to see whether there are any new failures happened by that time.
    If there are new failures marked on TA, SHD will start the crawl
    immediately to heal those failures as well. If there are no new
    failures, then SHD will take the AFR_TA_DOM_MODIFY lock and unsets
    the xattrs on TA, so that both the data bricks will be considered
    as good there after.
    
    Change-Id: I037b89a0823648f314580ba0716d877bd5ddb1f1
    fixes: bz#1579788
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 4f6ae853ffa9d06446407f389aaef61ac0b3b424
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Sep 19 14:32:22 2018 +0530

    glusterd: Use GF_ATOMIC to update 'blockers' counter at glusterd_conf
    
    Problem:
    Currently in glusterd code uses sync_lock/sync_unlock to update blockers
    counter which could add delays to the overall transaction phase
    escpecially when there's a batch of volume stop operations processed by
    glusterd in brick multiplexing mode.
    
    Solution: Use GF_ATOMIC to update blocker counter to ensure unnecessary
    context switching can be avoided.
    
    Change-Id: Ie13177dfee2af66687ae7cf5c67405c152853990
    Fixes: bz#1631128
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 6a49bce014ac546582cf2409fd9933115406c808
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Sep 19 19:49:51 2018 +0530

    glusterd: fix crash
    
    When huge number of volumes are created, glusterd crash is seen.
    With the core dump, got to know that mgmt_lock_timer became NULL.
    Adding a null check for the same, need to explore about the root
    cause.
    
    updates: bz#1630922
    Change-Id: I0770063fcbbbf4b24bef29e94b857b20bdfb5b85
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit b4eedcb4e432d2c2a5411e6cba1dedafba8e3c50
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Sep 17 16:56:48 2018 +0530

    geo-rep : fix coverity issues in glusterd-geo-rep.c
    
    This patch fixes CID 1210979, 1214614, 1292650, 1357874, 1382404.
    
    1. overflowed or a truncated value : call to sys_read has been reduced
       to 'sizeof(buf) -1' and after operation buf is properly terminated.
    
    2. tainted_data_argument : truncation due to cast operation on operand :
       resulted form call to strtol: chaged data type from pid_t to long.
    
    3. tainted_data_argument : call to fgets is reduced by 2 to make space
       for the '\n' and '\0'.
    
    updates: bz#789278
    Change-Id: Ib883501205c85007771213071c8e182286eb0bc0
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 0a92d5be1c783d6ff0acaab016d8a1d9477b7cbf
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Sep 18 12:07:29 2018 +0530

    glusterd: Improve logging in gd_mgmt_v3_unlock_timer_cbk
    
    Change-Id: I3335e7df3256d97c2211b64cfcaac9a016723471
    Updates: bz#1193929
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit ed071577e426744c08600f50e52cbf766c27868c
Author: Iraj Jamali <ijamali@redhat.com>
Date:   Tue Sep 18 15:40:45 2018 +0530

    libglusterfs: NULL pointer dereferencing clang fix
    
    Problem: trav could be NULL.
    
    Solution: Adding a check to avoid clang error.
    
    Updates: bz#1622665
    
    Change-Id: If26be82edea5e33c2356cea3769496f1cbd3774c
    Signed-off-by: Iraj Jamali <ijamali@redhat.com>

commit dc2c632d525cd23914bdc468ef6cf4335559867f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Sep 6 15:09:42 2018 +0530

    cluster/afr: Batch writes in same lock even when multiple fds are open
    
    Problem:
    When eager-lock is disabled because of multiple-fds opened and app
    writes come on conflicting regions, the number of locks grows very
    fast leading to all the CPU being spent just in locking and unlocking
    by traversing huge queues in locks xlator for granting locks.
    
    Fix:
    Reduce the number of locks in transit by bundling the writes in the
    same lock and disable delayed piggy-pack when we learn that multiple
    fds are open on the file. This will reduce the size of queues in the
    locks xlator.  This also reduces the number of network calls like
    inodelk/fxattrop.
    
    Please note that this problem can still happen if eager-lock is
    disabled as the writes will not be bundled in the same lock.
    
    fixes bz#1625961
    Change-Id: I8fd1cf229aed54ce5abd4e6226351a039924dd91
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d4770602e044424ff5a4a7ac666bf5a90490ec9b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 17 14:25:16 2018 +0530

    dht: utilize the framework to pass-through xlator tasks
    
    Also fixes the issue caused due to not converting back the fn function
    to after getting its address. We wanted the value of the field, not
    the address of the pt_fop field.
    
    With this patch, DHT will always be started in pass-through
    mode if the number of subvols is just 1.
    
    Fixes some tests to make sure DHT is in full config (ie, subvols > 1).
      - increased timeout of brick-mux test as it was bordering on 300 seconds.
      - Also change the volume type to supported 'replica 3' from 'replica 2'.
      - also no DHT tests should assume presence of DHT when there is
        just 1 brick in volume
    
    Credits: Nithya B <nbalacha@redhat.com>
    
    fixes: #405
    Change-Id: I8e55239ce58d6ac6ae1901e2e384be1ecbd33d6e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 1e02ab9eb3af7b6ce49b154e6b9070d01a8bbb67
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Mar 9 14:29:37 2017 +0530

    extras/devel-tools: script to strace processes
    
    Script to strace processes at high priority.
    Script should be run at high priority, like nice value of -19, to help
    get a trace of a run-away process consuming high CPU.
    
    eg.
    $ nice -n -19 ./strace-brick.sh glusterfsd 50
    
    will strace glusterfsd processes for 60 seconds which are consuming a
    minimum of 50% CPU.
    
    Change-Id: I6374054c7342b19122a3588d982388199f955930
    BUG: 1427397
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit a7a7d3bd1c4e5f4cd88a57a183229e185a07c730
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 17 11:57:22 2018 +0530

    logrotate: utilize the new 'maxsize' option
    
    Since logrotate 3.8.x version, a new option 'maxsize' is supported,
    which helps in rotating the logs before the specified time if the
    size exceeds maxsize limit. This should help in reducing the
    overflow of gluster logs.
    
    Updates: bz#1193929
    Change-Id: Id33c34d72f1931e7996893de9338db667e1e900d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 86f1aa94c15c6c2a95a96155e8d6e4ab953b3a50
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Aug 30 09:29:49 2017 +0530

    extras/devel-tools: script to resolve backtraces
    
    print-backtrace.sh
    script to resolve backtraces
    
    Change-Id: I24688ae5160cc706d9f4794521d17290bef6765b
    BUG: 1486532
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit d2b42668e779c31eb421f8b93be695d5eab65e6f
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Sep 18 14:19:11 2018 +0530

    tests/dht: Uncomment cleanup steps
    
    I had forgotten to uncomment the cleanup
    steps for file-create.t. Fixed.
    
    Change-Id: Id702b99b8e09f56b7333491a477828b4a37b2687
    updates: bz#1628194
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 02f2ac094819447f40a6762035406a7c7dad000e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Sep 6 10:46:43 2018 +0530

    tests: fixes to bug-1015990-rep.t
    
    - check that the shd is connected to brick before running statistics command
    - remove sleep statements
    - remove unneeded ($count-$value==0) test when it is known that both values will
      be same
    
    Fixes: bz#1625850
    Change-Id: Ifcd4887f0238031e5bca803cd9bfdb75a6e6c01b
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 07088d95e450f847722e5decbfa5da18a0dbd9de
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Sep 17 14:16:09 2018 +0530

    posix: Fix exporting default value for `export-statfs-size`
    
    No default value was specified for `export-statfs-size` in posix
    option table. Glusterd2 sets default value as `off` since the
    option type is `bool`. Posix treats `export-statfs-size=on` if
    not specified in volfile(That means default value is `on`)
    
    This patch sets default value as `on`
    
    Change-Id: I5c6341183be9b62a78fdbc94621220f9284e1382
    updates: #302
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit b977b44dd0adfcd7a3b432844260de4b8d1c4adf
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Sep 14 03:42:26 2018 -0400

    geo-rep: Fix issues related config set
    
    1. '--ignore-mising-args' option for rsync is not
       being used even though the rsync version is
       greater than 3.1.0. Fixed the same.
    
    2. '--existing' option for rsync is also not being
       used. Fixed the same.
    
    3. geo-rep config fails to set rsync-options as the
       value contains '--'. Interestingly, python argsparse
       treats the value with '--' (e.g., --ignore-missing-args)
       as option. But when passed with something like
       --value=--ignore-missing-args, it succeeds. Fixed the
       same.
    
    Change-Id: Iaeb838acaff1c2920fee9c7f920c99edce13a0a1
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    fixes: bz#1629561

commit 484f417da945cf83afdbf136bb4817311862a8d2
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Sep 11 14:19:42 2018 +0530

    glusterd: acquire lock to update volinfo structure
    
    Problem: With commit cb0339f92, we are using a separate syntask
    for restart_bricks. There can be a situation where two threads
    are accessing the same volinfo structure at the same time and
    updating volinfo structure. This can lead volinfo to have
    inconsistent values and assertion failures because of unexpected
    values.
    
    Solution: While updating the volinfo structure, acquire a
    store_volinfo_lock, and release the lock only when the thread
    completed its critical section part.
    
    Fixes: bz#1627610
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
    
    Change-Id: I545e4e2368e3285d8f7aa28081ff4448abb72f5d

commit d345ac09548dbb486c1619a27cb70149b3ca962a
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Thu Sep 6 18:17:14 2018 +0800

    event: get time by clock_gettime as pthread_cond_timedwait using
    
    Debug information shows time() has a delay between seconds increase,
    get the right time by clock_gettime as pthread_cond_timedwait using.
    
                             ret = pthread_cond_timedwait (&event_pool->cond,
                                                           &event_pool->mutex,
                                                           &sleep_till);
    +                         gf_msg ("epoll", GF_LOG_INFO, 0,
    +                                 LG_MSG_EXITED_EPOLL_THREAD,
    +                                 "pthread_cond_timedwait %lu %p return %d (active %d:%d)",
    +                                 sleep_till.tv_sec, event_pool, ret,
    +                                 event_pool->activethreadcount, threadcount);
                     }
             }
             pthread_mutex_unlock (&event_pool->mutex);
    
    [2018-09-06 18:33:57.000879] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.000916] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.000931] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.000945] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.000957] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.000970] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.000983] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.000997] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.001010] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.001022] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.001034] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.001060] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230037 0x1f48e60 return 110 (active 5:4)
    [2018-09-06 18:33:57.003085] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230038 0x1f48e60 return 0 (active 4:4)
    [2018-09-06 18:33:57.014142] I [event.c:284:event_dispatch_destroy] 0-epoll: pthread_cond_timedwait 1536230038 0x1f48e60 return 0 (active 3:4)
    
    Change-Id: I735249eee9a6f8284392b69e501479ac163b8409
    fixes: bz#1626313
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit f2137d4c84c035ed320f959dc39e07c6a1516afb
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Fri Sep 14 10:27:56 2018 +0530

    protocol/server: NULL pointer dereferencing clang fix
    
    Problem: Access to field fop_length results in null pointer dereferencing.
    
    Solution: Added condition checks fix the issue.
    
    Change-Id: Id408e3ac62ea9574f0cd9aecce5434add09eb7d0
    Updates: bz#1622665
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit f7f281900b3c87e3626d79bd9599c905faaf11ed
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Tue Sep 11 23:00:14 2018 +0530

    glusterd: NULL pointer dereferencing clang Fix
    
    Added ternary operator to avoid NULL pointer dereferencing
    
    Updates: bz#1622665
    
    Change-Id: I855f6caf720b28af1564898d75c6c965bcc58c5c
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit bdfe87d56b21766cf7fe9f73890d1d3336158982
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Sep 11 16:53:29 2018 +0530

    glusterd : fix coverity issue in glusterd-store.c
    
    This patch fixes CID 1124356: Unchecked return value (CHECKED_RETURN)
    
    updates: bz#789278
    Change-Id: I81f4637f19b81f820a2deb70cc7f84b79fe70236
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit fb836edec5f0bd805c302497d78fa85937d9d4dc
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Sep 12 18:19:09 2018 +0530

    tests/dht: Add tests for file create
    
    Test dht file creates
    
    Change-Id: I7aba710f4911432bd3b86834efecae8f01e4052f
    updates: bz#1628194
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 2b157eb97117511c5a47f2227aab81bff90cf32f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Sep 10 09:02:33 2018 -0400

    packaging: glusterfs.spec(.in) cleanup
    
    Someone (not me) once alphabetized all the %package, %files, and etc.
    sections, with a comment to keep them alphabetized. Move cloudsync
    sections to their correct locations in the spec.
    
    Also reorder testing and playground within %files section, keep testing
    %dirs together.
    
    Change-Id: I79e2e7a82d20275fd61d018880bcb5913c8f75f3
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit b4504eadd839dc93dda46f3a5284858ae4c83bfc
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Sep 14 12:06:28 2018 -0400

    gfapi: Cleanup alias file
    
    2 extra symbols were in the alias file, that are not exported
    this is cleaned up with this patch.
    
    Change-Id: I1ab54b9fb6b0d455884fbbfd89820c60bb861e6f
    Updates: bz#1193929
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 956b4ad214b46b1a1c89e5c120754081561aa930
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Sep 11 11:42:19 2018 +0300

    libglusterfs/src/dict.c : use xxhash64 for hashing.
    
    As part of a larger effort to consolidate hash functions
    and use a faster, with less collissions, I've moved to use
    xxhash as the hashing function for the dictionary.
    
    Note: I'm using only 32 bits of the hashes, as the hash field
    is currently a 32 bit variable. There's room (since the struct
    is not packed) to move to use a 64bit variable. Donno how it'll
    affect performance.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ie244efd1368234e54dd5957ee1ae5bebd7d9409a

commit 76cb1e761d18482512d907679d279d7f61902dde
Author: Anoop C S <anoopcs@redhat.com>
Date:   Sun Sep 9 11:39:47 2018 +0530

    extras/hooks: General improvements to S30samba-start.sh
    
    Based on https://review.gluster.org/c/glusterfs/+/19204 from
    Milan Zink <mzink@redhat.com>
    
    Change-Id: I61f62407a62475a74a6cc046c24748a31c66e6cd
    Updates: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 9f49f0b5901e29b8f0761c0e2631cd1c1d969a51
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Sep 13 15:44:15 2018 +0200

    socket: set 42 as default tpc-user-timeout
    
    The 'tcp-user-timeout' option is define in the 'socket' module, but it's
    configured in 'protocol/server' and 'protocol/client', which are the
    parents of the 'socket' module.
    
    However, current options management logic only takes into consideration
    default values specified in the 'socket' module itself, ignoring values
    defined in the owner xlator.
    
    This patch simply sets the default value of tcp-user-timeout in the
    'socket' module so that server and client use the expected value.
    
    Change-Id: Ib8ad7c4ac6aac725b01a78f8c3d10cf4063d2ee6
    fixes: bz#1628605
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 0b3f08cd50f76af537aa4bce2f09602a4834b0fc
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Sep 13 12:50:30 2018 -0400

    glusterd: Update op-version from 4.2 to 5.0
    
    Post changing the max op-version to 4.2, after release
    4.1 branching, the decision was to go with increasing
    release numbers. Thus this needs to change to 5.0.
    
    This commit addresses the above change.
    
    Fixes: bz#1628664
    Change-Id: Ifcc0c6da90fdd51e4eceea40749511110a432cce
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit f15e948da3881b61a8b546af7c64340db87d3cf7
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 11 14:17:02 2018 -0400

    build: cleanup xlator link, --no-undefined, libuuid
    
    While attempting to build a (pre-)5.0 of glusterfs on Ubuntu
    bionic and cosmic, it became apparent that there are some gremlins
    hiding in the combination of the xlator export-symbols, the newish
    addition of -Wl,--no-undefined, and the new switch to libuuid from
    the old contrib/uuid.
    
    Note: even though Fedora 28 (and later) and Ubuntu bionic (and
    later) have the same nominal version of libtool, the Fedora version
    appears to do a better job of recursing through dependencies to
    determine the libraries to link with.
    
    Examination of the build logs showed that despite appearing to work
    on Fedora, not all xlators and shared libs were linked with -Wl,
    --no-undefined, and -luuid. And in the case of the gnfs xlator, it
    was not only not linked with -Wl,--no-undefined but alsos not linked
    with -lgfxdr and -lgfrpc.
    
    Added GF_XLATOR_LDFLAGS, similar to GF_XLATOR_DEFAULT_LDFLAGS.
    GF_XLATOR_DEFAULT_LDFLAGS is for xlators that export/expose the
    default or common set of symbols. GF_XLATOR_LDFLAGS is for those
    remaining xlators that export/expose non-default symbols, e.g. dht
    and glupy. This removes the need in the future to add things like
    $(UUID_LIBS) to every xlator's Makefile.am. Just add it to
    GF_XLATOR_LDFLAGS and GF_XLATOR_DEFAULT_LDFLAGS in configure.ac
    and you're done.
    
    This patch was tested on Fedora 28 (build, rpmbuild), Fedora
    Rawhide/30 (rpmbuild), RHEL8 (rpmbuild), CentOS7 (rpmbuild), Fedora
    koji --scratch build for f30/rawhide, and a Launchpad build for
    Ubuntu cosmic/18.10.
    
    Change-Id: Ieca104fa5c5d3c094e701c8ca4a73754dd0292b0
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit d9475b8d06ca184b5305575e5f04490604f8ca2c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Sep 12 18:35:59 2018 +0530

    template files: revert clang
    
    Change-Id: If3925191d23afe83cbbdbc3cf0554c0a9c76d043
    updates: bz#1564149
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e16868dede6455cab644805af6fe1ac312775e13
Author: Gluster Ant <bugzilla-bot@gluster.org>
Date:   Wed Sep 12 17:52:45 2018 +0530

    Land part 2 of clang-format changes
    
    Change-Id: Ia84cc24c8924e6d22d02ac15f611c10e26db99b4
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit 45a71c0548b6fd2c757aa2e7b7671a1411948894
Author: Gluster Ant <bugzilla-bot@gluster.org>
Date:   Wed Sep 12 17:22:48 2018 +0530

    Land clang-format changes
    
    Change-Id: I6f5d8140a06f3c1b2d196849299f8d483028d33b

commit be77dbbda692792335a8e9e7c02e0c281f003c40
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Aug 22 12:31:48 2018 +0530

    clang-format: add the config file
    
    Also update the required documents and scripts to enable clang-format
    
    Change-Id: I73aae6db06c2f732a1779d59a73bc05e28beafba
    updates: bz#1564149
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit bc4201b4c23eee0e3d09a6760b449a0011677cd5
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Sep 11 16:09:55 2018 +0530

    doc: make developer-index.md as README
    
    This helps to traverse the docs well as README.md is rendered
    by default in github pages, and would help to provide better indexed
    document for new users.
    
    updates: bz#1193929
    Change-Id: I4130dfd16aed924ecab17f96326cedb86892d6a6
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 65db3e596e456e11f524160261bf87a9ebe9fa00
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Sep 7 11:39:39 2018 +0530

    dht: Use snprintf instead of strncpy
    
    The recent changes to use malloc instead
    of calloc left the new_name and new_path
    non-null terminated. We now use snprintf
    instead of strncpy to fix this.
    
    Change-Id: I1a31701ca9447efde38921be0ba2c73cde2e7976
    fixes: bz#1626346
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 763eb83dcbaf6a319fc2346fc696ab079e425ee3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 20 10:34:28 2018 +0530

    doc: add coding-standard and commit-msg link in README
    
    Having the links in README makes people follow it if they browse
    through github.
    
    Updates: bz#1193929
    Change-Id: I580332a41d9b52858aa9796a74a563ff57a60b4b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 343f5a1ee0567363fc30a06f83e3e77aec0d2b2e
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Sep 11 10:31:27 2018 +0530

    mount/fuse: convert ENOENT to ESTALE in open(dir)_resume
    
    This patch is continuation of commit
    fb4b914ce84bc83a5f418719c5ba7c25689a9251.
    
    <snip>
    mount/fuse: never fail open(dir) with ENOENT
    
        open(dir) being an operation on inode should never fail with
        ENOENT. If gfid is not present, the appropriate error is
        ESTALE. This will enable kernel to retry open after a revalidate
        lookup.
    </snip>
    
    Earlier commit failed to fix codepath where error response is sent
    back on gfid resolution failures in fuse_open(dir)_resume. Current
    patch completes that work
    
    Change-Id: Ia07e3cece404811703c8cfbac9b402ca5fe98c1e
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    updates: bz#1627620

commit 8ac8f359b24c8583eb1a15b9926929770b869db8
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Sep 10 17:04:30 2018 +0300

    mgmt xlators: store boolean fields using integer
    
    Surprisingly, there is not set_boolean() as there is a get_boolean()
    In fact, it is stored as an INT dictionary type.
    
    In some occasions it was stored using a string, and this caused
    errors such as:
    key gfproxy-server, integer type asked, has string type [Invalid argument]
    
    I've fixed what I saw in some logs, I'm sure there are more.
    The CORRECT fix is to create a boolean set and use it, but this
    requires a bit more work. I'll see if I can do it later on.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I45fd0c7a0824b2f42b8ce510296c9dfa4f32ad66

commit 170e848b940615eb9f366211d7a79cc3033902cb
Author: Harpreet Lalwani <hlalwani@redhat.com>
Date:   Mon Sep 10 11:37:35 2018 +0530

    glusterd: NULL pointer dereferencing clang fix
    
    problem: NULL point dereferencing
    
    solution: Adding a conditional statement before and then dereferencing it.
    
    Updates: bz#1622665
    
    Change-Id: I562ca90aebf2a4882cfea10114a90364d9ef1996
    Signed-off-by: Harpreet Lalwani <hlalwani@redhat.com>

commit 5afff66b254e2c86eee287b5233e5a5305ad0788
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Sep 10 09:21:27 2018 -0400

    misc: fix misc. shebangs
    
    * One #!/usr/bin/env python and three #!/usr/bin/python were overlooked
      in all the other python fixups. Ugh.
    
    * Two new python files missed the memo about #!/usr/bin/python3.
    
    * One #!/usr/bin/env bash.
      Various distribution packaging policies have strong wording about
      the use of #!/usr/bin/env ...
    
      Note: this patch does not change the use of #!/usr/bin/env bash in
      the two files extras/{clang-checker.sh,check_goto.pl} as these are
      not included in any packages. (Although I'm not actually sure why
      anyone would ever use '/usr/bin/env {sh,bash}' as I'm not aware of
      any version-specific differences like there are with, e.g., python.)
    
    * One #!/usr/bin/bash.
      On Fedora and CentOS > 6, /bin is a symlink to /usr/bin, so it
      makes little difference. But Debian & Ubuntu still have separate
      /bin and /usr/bin; and sh and bash are in /bin, not /usr/bin.
      (Historically, in BSD and SYSV Unix it was /bin/sh.)
    
      Note: Fedora and CentOS package build runs a script that converts
      all /bin/sh and /bin/bash to /usr/bin/sh and /usr/bin/bash.
    
    Change-Id: I9171265829af78dd0cd7622c22b56d22179ff8a3
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 0e399b9e4623a68eb681f8c3c5c45e05048a96e8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Aug 10 01:32:22 2018 +0200

    rpm: add "--with asan" build option
    
    RHEL-6 does not have libasan, enabling the "--with asan" option is a
    no-op there.
    
    RHEL-7 has an earlier version of libasan, and that does not have the
    __asan_init symbol. Test for __asan_report_error in confiure.as instead.
    
    Change-Id: I6322e832c5cfbd7d750f5c32c84c28771674ced6
    Updates: #492
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit ee79077c0d19ddf97caea22cc001b6f4f9b0829c
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Sep 6 16:15:01 2018 +0530

    storage/posix: Fix coverity issue - Unchecked return value
    
    Fixes CID: 1388886
    
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=85287446&defectInstanceId=25997291&mergedDefectId=1388886
    
    Change-Id: Ic4e558bba7e15d213c07bc31affb2e175ace5502
    updates: bz#789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 5537a8f050a07d8f1c32138d787331d61695ce38
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Sep 8 19:53:07 2018 +0530

    performance/write-behind: remove the request from wip queue in wb_fulfill_request
    
    The bug is very similar to bz 1379655 and the fix too very similar to
    commit a8b2a981881221925bb5edfe7bb65b25ad855c04.
    
    Before this patch, a request is removed from wip queue only when ref
    count of request hits 0. Though, wb_fulfill_request does an unref,
    it need not be the last unref and hence the request may survive in
    wip queue till the last unref. Let,
    
    T1: the time at which wb_fulfill_request is invoked
    T2: the time at which last unref is done on request
    
    Let's consider a case of T2 > T1. In the time window between T1 and
    T2, any other request (waiter) conflicting with request in liability
    queue (blocker - basically a write which has been lied) is blocked
    from winding. If T2 happens to be when wb_do_unwinds is invoked, no
    further processing of request list happens and "waiter" would get
    blocked forever. An example imaginary sequence of events is given
    below:
    
    1. A write request w1 is picked up for winding in __wb_pick_winds
       and w1 is moved to wip queue. Let's call this
       invocation of wb_process_queue by wb_writev as PQ1. Note w1 is not
       unwound.
    
    2. A dependent write (w2) hits write-behind and is unwound followed by
       a flush (f1) request. Since the liability queue
       of inode is not empty, w2 and f1 are not picked for unwinding. Let's call
       the invocation of wb_process_queue by wb_flush as PQ2. Note that
       invocation of wb_process_queue by w2 doesn't wind w2 instead
       unwinds it after which we hit PQ2
    
    3. PQ2 continues and picks w1 for fulfilling and invokes
       wb_fulfill. As part of successful wb_fulfill_cbk,
       wb_fulfill_request (w1) is invoked. But, w1 is not freed (and hence
       not removed from wip queue) as w1 is not unwound _yet_ and a
       ref remains (PQ1 has not invoked wb_do_unwinds _yet_).
    
    4. wb_fulfill_cbk (triggered by PQ2) invokes a wb_process_queue (let's
       say PQ3). w2 is not picked up for winding in PQ3 as w1 is still in wip
       queue. At this time, PQ2 and PQ3 are complete.
    
    5. PQ1 continues, unwinds w1 and does last unref on w1 and w1 is freed
       (and removed from wip queue). Since PQ1 didn't invoke
       wb_fulfill on any other write requests, there won't be any future
       codepaths that would invoke wb_process_queue and w2 is stuck
       forever. This will prevent f2 too and hence close syscall is hung
    
    With this fix, w1 is removed from liability queue in step 3 above and
    PQ3 winds w2 in step 4 (as there are no requests conflicting with w2
    in liability queue during execution of PQ3). Once w2 is complete, f1
    is resumed.
    
    Change-Id: Ia972fad0858dc4abccdc1227cb4d880f85b3b89b
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1626787

commit f0bacb2a51fbb3cd6645ee94d83e0a01549852dc
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Sep 10 15:07:43 2018 +0530

    cli: Add warning message while converting to replica 2 configuration
    
    Currently while creating replica 2 volume we display a warning message
    of ending up in split-brain. But while converting an existing volume
    from other configuration to replica 2 by add-brick or remove-brick
    operations we do not show any such messages.
    With this fix in add-brick and remove-brick cases also we will display
    the same warning message and prompt for confirmation if the configuration
    changes to replica 2.
    
    Change-Id: Ifc4ed6994a087d2403894f4e743c4eb41633276b
    fixes: bz#1627044
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 23fa1feaf0a3ab482628ab5b7b950d27e57fb46d
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Sep 10 16:35:25 2018 +0530

    mgmt/glusterd : Fix coverity issue
    
    CID: 727146, 727066
    
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=85393035&defectInstanceId=26034751&mergedDefectId=727146
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=85392913&defectInstanceId=26034571&mergedDefectId=727066
    
    updates: bz#789278
    
    Change-Id: Ieaef33829ec88e68690dabce4ea21d2e61dad9f6
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 3114c4a10672a70c8964c8cfce2ca0cc1e835a9f
Author: Sheetal Pamecha <sheetal.pamecha08@gmail.com>
Date:   Mon Sep 10 11:01:38 2018 +0530

    glusterd: NULL pointer dereferencing clang fix
    
    Added ternary operator to avoid NULL pointer dereferencing
    
    Updates: bz#1622665
    
    Change-Id: I4b970176b6b555c2eda1da2848c493e45b1e4217
    Signed-off-by: Sheetal Pamecha <sheetal.pamecha08@gmail.com>

commit 5384787d41d33916521fdda194875a306f406eeb
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Sep 7 14:00:59 2018 -0400

    features/snapview-server: remove the ret variable
    
    Used only once to store the return value of a function.
    
    Change-Id: Ib2b9db847b5f652ce46f220297d9c7c3503eaea2
    fixes: #230
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit a9f3ef105f4c686608609ad473fe4968c15f10c9
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 20 10:33:58 2018 +0530

    doc: add details on how the commit should be structured
    
    Detailing how the commit message should be is very important for imposing
    some structure, and good practises. Also it helps new developers to do the
    right things.
    
    This is mostly copied from the OpenStack commit message reference, as it
    was overlapping with most of the things we follow in GlusterFS. Made
    minor changes to make it suitable for Gluster project.
    
    Updates: bz#1193929
    Change-Id: I4dcd7ff366edfc6c1727a287f32bcf7270c86b11
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 77958023ffb26f1b848fd1ab1ea36f730bc1efce
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Sep 5 09:10:39 2018 +0530

    rfc.sh: use 'git log -n1' instead of 'git show'
    
    This is required mainly because if we use any format in a
    documentation, and it has strings which are looking for commit
    msg format (like fixes: bz...) in document, that too will be
    considered in checks, even though it is not part of commit msg.
    
    By using git log -n1, we would only check the content of commit
    msg.
    
    Updates: bz#1193929
    Change-Id: I498590de6d3daa6be7bcbee1f083ef3fa6ecc96f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 515074156db5492b22ee8db58e0b91caeed8f60c
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Sep 7 14:10:37 2018 +0530

    cluster/dht: Create a linkto file if required
    
    Using the dht_filter_loc_subvol_key to create
    files on specific subvols did not create a linkto
    file. This can make the file inaccessible as
    lookup-optimize is now enabled by default.
    
    Change-Id: I78add5a31887378a479cb9c746b91678876b0dbe
    fixes: bz#1626394
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 05e64dab56c4560cbeaacd5089d6e16f6eb295d2
Author: Anoop C S <anoopcs@redhat.com>
Date:   Fri Sep 7 13:50:47 2018 +0530

    build: Make building of glupy more obvious
    
    Yet again glupy..!!
    
    Core changes:
    * Provide --disable-glupy(instead of --enable-glupy) since we try to
      build it by default.
    * AC_SUBST macro is considered/executed even if it is inside an if
      condition. As a result GLUPY_SUBDIR was always substituted which in
      turn would make compilation enter glupy/ translator sources in absence
      of python{2/3}-devel and fails.
    
    Miscellaneous changes:
    * Remove an explicit echo for printing PYTHON version.
    * Replace hard coded python version in warning message displayed in
      absence of python{2/3}-devel.
    * Redirect pushd and popd output to /dev/null
    
    Change-Id: If1ba30a12a8bda5763ef528787fccb2f7946b136
    Updates: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit cfecc7b3dfdba3488ea8c69d6f8892fd6a56e038
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 10 11:38:26 2018 +0530

    posix: fix the duplicate macro definitions
    
    the macro 'PATH_SET_TIMESPEC_OR_TIMEVAL' is defined in posix.h,
    which seems to be good place for it
    
    updates: bz#1193929
    
    Change-Id: I521a2a6efeb26891c24637a5f06b1d90c00b1135
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 3d6ba0d1d445433315daa2f37f2366e235fce441
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jul 27 15:19:46 2018 +0530

    cluster/dht: optimize readdir for 1xn vols
    
    Skip the hashed subvol check for volumes with
    distribute count of 1.
    
    Change-Id: I5703508b54a17c49a217c8a8e09884980705953a
    fixes: bz#1608175
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit b92d5c616e93e28b1c39bbed7cc78361e0b5d691
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 10 11:14:09 2018 +0530

    ec-heal: remove a duplicate definition of alloca0
    
    the same macro is defined in common-utils.h, which seems to be
    much better place for the same.
    
    Updates: bz#1193929
    
    Change-Id: I409b719c291102136500b955e5827a550142ed96
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 7593e05ad38aa63ee7fd6d1c8be815d00874ae2d
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 23:36:51 2018 +0300

    xlators/cluster/dht/src/tier-common.c:move to GF_MALLOC() instead of GF_CALLOC() when
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    Change-Id: I7d38a7d576f6777976fe86e5351a8d95caddbb9c
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 42bc6ef4c70eda1d8d6011d52399b778f0f2b70f
Author: Omar Kohl <omarkohl@gmail.com>
Date:   Thu Sep 6 13:57:33 2018 +0200

    Modify log message 'DH ciphers are disabled' from ERROR to INFO
    
    Per the latest comment in bz#1398237 this message is confusing for users
    because it suggests an error where none exists.
    
    Fixes: bz#1626319
    
    Change-Id: I2f05999da157b11e225bf3d95edb597e964f9923
    Signed-off-by: Omar Kohl <omarkohl@gmail.com>

commit 15d2b3cf8595de176b47f97ed92b4f8653af2e60
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sun Sep 9 22:54:08 2018 +0530

    glusterd: Fix unused value coverity fix
    
    Commit 09198e203e has introduced a new coverity with ID 1395635.
    keylen variable is assigned to some value but stored value is
    overwritten before it is used. This patch addresses the issue.
    
    updates: bz#789278
    Change-Id: Ice290dcb9d703cd2131b0f0803436660e670e10a
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 09198e203ece6925791a8a3a6121c5f808e4e873
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Sep 3 13:55:01 2018 +0300

    Some (mgmt) xlators: use dict_{setn|getn|deln|get_int32n|set_int32n|set_strn}
    
    In a previous patch (https://review.gluster.org/20769) we've
    added the key length to be passed to dict_* funcs, to remove the need
    to strlen() it. This patch moves some xlators to use it.
    
    - It also adds dict_get_int32n which was missing.
    - It also reduces the size of some key variables.
    They were set to 1024b or PATH_MAX, where sometimes 64 bytes were
    really enough.
    
    Please review carefully:
    1. That I did not reduce some the size of the key variables too much.
    2. That I did not mix up some keys.
    
    Compile-tested only!
    
    Change-Id: Ic729baf179f40e8d02bc2350491d4bb9b6934266
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 44e4db05a953a6f231c62225b462470cacb16bd4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Sep 3 16:26:56 2018 +0530

    glusterd: avoid using glusterd's working directory as a brick
    
    Adding checks for avoiding glusterd's working directory used as
    a brick for volume creation.
    
    fixes: bz#853601
    Change-Id: I4b16a05f752e92216aa628f542a4fdbf59b3c669
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit a880d6f6aa7a2979df8aa32b58f716ef0c578d3f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 20:41:20 2018 +0300

    multiple xlators (mgmt): strncpy()->sprintf(), reduce strlen()'s
    
    xlators/mgmt/glusterd/src/glusterd-geo-rep.c
    xlators/mgmt/glusterd/src/glusterd-handshake.c
    xlators/mgmt/glusterd/src/glusterd-sm.c
    xlators/mgmt/glusterd/src/glusterd-store.c
    xlators/mgmt/glusterd/src/glusterd-utils.c
    xlators/mgmt/glusterd/src/glusterd-volgen.c
    xlators/mgmt/glusterd/src/glusterd-volume-ops.c
    xlators/mgmt/glusterd/src/glusterd.c
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf(). Try to ensure output is not
    truncated.
    
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN (sizeof() ) for const strings.
    
    Compile-tested only!
    
    Change-Id: Ib5d001857236f43e41c4a51b5f48e1a33110aaeb
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit df697c68f6e1d676ae101e18b19f69e7241dc84a
Author: Shwetha K Acharya <sacharya@redhat.com>
Date:   Fri Sep 7 11:20:49 2018 +0530

    glusterd-sm: NULL pointer dereferencing clang fix
    
    Problem: new_event could be NULL.
    
    Solution: Added a goto statement to address this issue.
    
    Updates: bz#1193929
    Change-Id: Id3ce28fc53ad2cc8b9fcb63f7774568d31073b9e
    Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>

commit 82640b7109ef83ed6cc5054c81d076aa3398d249
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Aug 31 12:25:32 2018 +0530

    cluster/dht:  Rework the debug xattr to get hashed subvol
    
    The earlier implementation required the file to already exist
    when trying to get the hashed subvol. The reworked implementation
    allows a user to get the hashed subvol for any filename, whether
    it exists or not.
    
    Usage: getfattr -n "dht.file.hashed-subvol.<filename>" <parent dir>
    
    Eg:To get the hashed subvol for file-1 inside dir-1
    
    getfattr -n "dht.file.hashed-subvol.file-1" /mnt/gluster/dir1
    
    credit: rgowdapp@redhat.com
    
    Change-Id: Iae20bd5f56d387ef48c1c0a4ffa9f692866bf739
    fixes: bz#1624244
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 527dffeb699e5ac857a798d462a3fba4aed3c5a5
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Sep 6 11:20:32 2018 +0530

    cluster/ec: Don't update trusted.ec.version if fop succeeds
    
    If a fop has succeeded on all the bricks and trying to release
    the lock, there is no need to update the version for the
    file/entry. All it will do is to increase the version from
    x to x+1 on all the bricks.
    
    If this update (x to x+1) fails on some brick, this will indicate
    that the entry is unhealthy while in realty everything is fine
    with the entry.
    
    Avoiding this update will help to not to send one xattrop
    at the end of the fops. Which will decrease the chances
    of entries being in unhealthy state and also improve the
    performance.
    
    Change-Id: Id9fca6bd2991425db6ed7d1f36af27027accb636
    fixes: bz#1623759
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 18543fec0da8d0459501fb96f8efb019190bf223
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Sep 3 14:01:23 2018 +0530

    cluster/ec: Improve logging for some critical error messages
    
    Change-Id: I037e52a3467467b81a1ba5416317870864060d4d
    updates: bz#1615703
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit c8100dfe65e04cf818b7535fbec658667b9d5dbb
Author: sanoj-unnikrishnan <sunnikri@redhat.com>
Date:   Wed Aug 29 14:45:50 2018 +0530

    Quota: Fix for clang issues
    
    Updates: bz#1193929
    Change-Id: I549f741fbf97ee3fa2d63edacee5b705ef37c49a
    Signed-off-by: sanoj-unnikrishnan <sunnikri@redhat.com>

commit f6a7f6e8124327509559170faa9a4dce6fad9731
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 23:36:28 2018 +0300

    xlators/cluster/dht/src/dht-common.c :move to GF_MALLOC() instead of GF_CALLOC() when
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    Please review carefully, especially for string allocation, with the
    terminating NULL string (added another byte to ensure it's there).
    
    Only compile-tested!
    
    Change-Id: Ia5e4f50dfb0c29809c2019fcfd8079507813249e
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 50e8b0c335ba4f18987a32e8268ee31498323beb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:41:21 2018 +0300

    glusterfsd/src/glusterfsd.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Iaed86fcc909022c5158c3e08a9106b1110b9df0a

commit ce17a3a66dd15f09d1bf5404f7f3dee860ca6f8c
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 20:39:16 2018 +0300

    multiple xlators: strncpy()->sprintf(), reduce strlen()'s
    
    xlators/cluster/afr/src/afr-common.c
    xlators/cluster/dht/src/dht-common.c
    xlators/cluster/dht/src/dht-rebalance.c
    xlators/cluster/stripe/src/stripe-helpers.c
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf().
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN (sizeof() ) for const strings.
    
    Compile-tested only!
    
    Change-Id: Icdf79dd3d9f9ff120e4720ff2b8bd016df575c38
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 21e78061a24a094067fb267b77c4ffaae7e762f3
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Sep 5 04:30:35 2018 -0400

    multiple: Fix python2 to python3 compat
    
    Change-Id: Iac241166d7a35dc7cc6cf07850f9f1bce38fe207
    Updates: #411
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit bc6b6f6a168804f22bbb44081f89e938fbfcec60
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 30 10:54:54 2018 +0300

    libglusterfs/src/dict.c: remove memcpy(), gf_asprintf -> asprintf
    
    1. We don't need a temp. string to strotol(), we can use data->data.
    2. We don't need the gf_asprintf, when a regular asprintf would do.
    3. No need to CALLOC the data, can MALLOC, since
    we are going to populate most of the fields anyway.
    4. Removed is_const member - it was not used.
    5. Turned is_static to a gf_boolean_t
    6. Turned another get_mem0 to get_mem (in dict_set_lk() func)
    7. Remove dict_set_ptr - was exactly the same as dict_set_static_ptr
     (apart from the 'static' bit) and no one was using it.
    8. Removed is_static from the dictionary object. Did not seem to be
    very useful.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I7b1f6320867b154be4a94033819407f7e51cf38c

commit e6a826a97def94458d6e02101c5bbb2b13833374
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:18:31 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-log-ops.c : reduce size or re-scope message variable
    
    The the error and/or message variable was either:
    - Reduced in size - from 2048 bytes to 64 bytes, for example.
    or
    - Changed in scope - defined in a smaller scope.
    
    Compile-tested only!
    
    Change-Id: Ib8617db6c3646954c0225d12b904d668bf0f7046
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 4bafcc97e812acc854dfc436ade35df0308d5a3e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Sep 5 19:03:08 2018 +0530

    posix: disable open/read/write on special files
    
    In the file system, the responsibility w.r.to the block and char device
    files is related to only support for 'creating' them (using mknod(2)).
    
    Once the device files are created, the read/write syscalls for the specific
    devices are handled by the device driver registered for the specific major
    number, and depending on the minor number, it knows where to read from.
    Hence, we are at risk of reading contents from devices which are handled
    by the host kernel on server nodes.
    
    By disabling open/read/write on the device file, we would be safe with
    the bypass one can achieve from client side (using gfapi)
    
    Fixes: bz#1625096
    
    Change-Id: I48c776b0af1cbd2a5240862826d3d8918601e47f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 889040e20d86da14aab372203ebaa91dda5db6f2
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Sep 5 18:16:37 2018 +0530

    cluster/dht: Initialise pointers to null
    
    Use calloc in dht_layouts_init so to as to
    prevent dht_init from attempting to free
    invalid memory in case of failure.
    
    There are other ways to do this (set first failure
    to null and break there when cleaning up) but
    I prefer having all pointers initialized to null.
    This is a one time operation so it should not be
    too expensive.
    
    Change-Id: Ie22246047448f1cae971d48fa5aaf2efcaeb42c0
    fixes: bz#1625643
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 2b95d2c0be20a62279bbfebc17457004aca0988f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:42:45 2018 +0300

    cli/src/cli-cmd-parser.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ic1531afbf614823628cc8d70bae782d4db7ec033

commit 3ee5f7ee34e1768a0b15c6acc54481c2372f9c92
Author: Raghavendra Manjunath <raghavendr@redhat.com>
Date:   Thu Aug 23 22:24:25 2018 -0400

    features/uss: Use xxh64 to generate gfid instead of md5sum
    
    * This is to ensure FIPS support
    * Also changed the signature of svs_uuid_generate to
      get xlator argument
    * Added xxh64 wrapper functions in common-utils to
      generate gfid using xxh64
      - Those wrapper functions can be used by other xlators
        as well to generate gfids using xxh64. But as of now
        snapview-server is going to be the only consumer.
    
    Change-Id: Ide66573125dd74122430cccc4c4dc2a376d642a2
    Updates: #230
    Signed-off-by: Raghavendra Manjunath <raghavendra@redhat.com>
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 9716ce88b3a1faf135a6badc02d94249898059dd
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 24 15:42:28 2018 +0530

    io-stats: dump io-stats info in /var/run/gluster
    
    It wouldn't make sense to allow iostats file to be written in
    *any* directory. While the formating makes sure we try to append
    io-stats-name for the file, so overwriting existing file is slim,
    but in any case it makes sense to restrict dumping to one directory.
    
    Below are the sample commands, and files created for the corresponding
    values:
    
     $ setfattr -n trusted.io-stats-dump -v file-for-dump $M0
    
    In this case, the file would be in /var/run/gluster/file-for-dump
    
     $ setfattr -n trusted.io-stats-dump -v /dir1/dir2/file-for-dump $M0
    
    In this case, then the dump file is in /var/run/gluster/dir1-dir2-file-for-dump
    
    Note that the value passed for this virtual xattr would be treated as a
    file, and even if the value has '/' in it, it would be changed to '-'
    for sanity.
    
    Fixes: bz#1625106
    
    Change-Id: Id9ae6a40a190b8937c51662e6e1c2a0f6c86a0e0
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 35f86ce46240c4f9c216bbc29164ce441cfca1e7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 24 13:56:56 2018 +0530

    protocol: don't use alloca
    
    current implementation of alloca can cause issues when strings larger
    than the allocated buffer is passed to the xdr. Hence it makes sense
    to allow XDR decode functions to deal with memory allocations, which
    we can free later.
    
    Fixes: bz#1625097
    
    Change-Id: I3a05553f5702de9575c244649ca0e5ac9abaac94
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 9ae986f18c0f251cba6bbc23eae2150a8ce0417e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 9 13:00:01 2018 +0530

    server-protocol: don't allow '../' path in 'name'
    
    This will prevent any arbitrary file creation through glusterfs
    by modifying the client bits.
    
    Also check for the similar flaw inside posix too, so we prevent any
    changes in layers in-between.
    
    Fixes: bz#1625095
    
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Change-Id: Id9fe0ef6e86459e8ed85ab947d977f058c5ae06e

commit cc3271ebf3aacdbbc77fdd527375af78ab12ea8d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 24 13:25:12 2018 +0530

    dict: handle negative key/value length while unserialize
    
    Fixes: bz#1625089
    Change-Id: Ie56df0da46c242846a1ba51ccb9e011af118b119
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 69532c141be160b3fea03c1579ae4ac13018dcdf
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 31 10:32:20 2018 +0530

    afr: thin-arbiter read txn changes
    
    If both data bricks are up, read subvol will be based on read_subvols.
    
    If only one data brick is up:
    - First qeury the data-brick that is up. If it blames the other brick,
    allow the reads.
    
    - If if doesn't, query the TA to obtain the source of truth.
    
    TODO: See if in-memory state can be maintained for read txns (BZ 1624358).
    
    updates: bz#1579788
    Change-Id: I61eec35592af3a1aaf9f90846d9a358b2e4b2fcc
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 560bd8671f2f9ae17530ad1d23a209dc95d41f82
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Aug 17 09:38:39 2018 +0530

    New flag to glusterfsd binary to print libexec dir
    
    New CLI option for `glusterfsd` binary to get the path of
    libexec directory. This helps glusterd2 to detect the
    installed path of `gsyncd` and other binaries.
    
    Usage: `glusterfsd --print-libexecdir`
    
    Updates: bz#1193929
    Change-Id: I8c1a74afd9acec7ee7bd3deabed9d9f20fe3fb5f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 0590678d05473d40c8107be8cf5a66879f9d196f
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Aug 30 16:09:04 2018 +0530

    cli : fix coverity issue in cli-cmd-parser.c
    
    This patch fixes 1175017 and 1382401.
    
    This patch fixes resource leak by validating brick_count is valid or
    not. If brick_count is not valid we are coming out in "cli_cmd_bricks_parse"
    without allocating memory to "brick_str" which is eventually pointed by bricks.
    
    Change-Id: I8ed0f29495379ec49484c5c4069865db3653506f
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 33128ef59a05f2c31c0f51919c5dd7746cebd6ef
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Sep 4 21:05:11 2018 +0530

    core: switch to python3
    
    Commit af0d5a9b5375a5cd87ac10b429e2b9934718ce5b changes
    python2 -> python3. This patch fixes a small issue introduced
    by it.
    
    Change-Id: Ib23c73683f570e8891f41476b661f37c89635fb5
    updates: #411
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 4d198e33ba2ff5b550e8095af3c8d0b76c18bc2f
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Sep 4 14:13:18 2018 +0530

    glusterd : fix some coverity issues in glusterd-store.c
    
    This patch fixes CID 1382346, 1274190 and 1382403.
    
    Change-Id: I1968e686587719e74bd70fa1542c20bccc04a7f9
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 8612a1ca192333c2b760455661647d83bed2fd92
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Aug 29 00:18:32 2018 +0530

    glusterd: Fix Buffer size issues
    
    This patch fixes buffer size issue 1138522.
    
    Change-Id: Ia12fc8f34f75704f8ed3efae2022c4fd67a8c76c
    updates: bz#789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 13298d2b3893edb5d147ea3bcb9902ee5be4b3ad
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 24 17:14:31 2018 +0530

    posix: remove not supported get/set content
    
    getting and setting a file's content using extended
    attribute worked great as a GET/PUT alternative when
    an object storage is supported on top of Gluster. But
    it needs application changes, and also, it skips some
    caching layers. It is not used over years, and not
    supported any more. Remove the dead code.
    
    Fixes: bz#1625102
    
    Change-Id: Ide3b3f1f644f6ca58558bbe45561f346f96b95b7
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c25eee58c933a1ada8f5550377081c765ef24213
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 27 23:50:05 2018 +0530

    xlators: add classification flag to some
    
    Add classification to those translators which has `xlator_api_t`
    already defined and used.
    
    Updates: #430
    Change-Id: I9d2772cb2c4ed4ab06aaa546500cf3b7d00bddac
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit a105b25915a2b9c900957c71443e0be2ef5fa9ec
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 27 23:11:51 2018 +0530

    classification: provide infra to start labelling features/components
    
    `doc/xlator-classification.md` talks about the reasoning and expectations
    
    Reviewers are expected to check the 'category' of new
    option / translator added in the codebase, and make sure the flag
    is always properly set. It helps to keep the 'expectation' proper
    on the codebase.
    
    updates: #430
    Change-Id: I2bfc9934a5f6eed77fcc3e20364046242decc82c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 53e6e621408bca1e053caa2f93af84788edb2dfa
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Sep 3 11:35:31 2018 +0530

    IO cache : fix coverity issue in page.c
    
    This patch fixes CID 1382439 and 1382412.
    
    Change-Id: I8696623c168ba76ae2ecac7c9582b4e50437bc53
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 8b913eb752be422a362329d02dfb5c76754ad151
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Aug 19 08:08:23 2018 +0300

    {dht-rebalance|glusterd-geo-rep|glusterd-utils|nfs|bd}.c: no dict_del before dict_set
    
    There is no need to remove an item before re-setting it.
    
    Compile-tested only!
    
    Change-Id: I2869aec9ebf474859127b8b38d284246e6097e84
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 5276e8f27e3021d5da3d3055caed6f9a1d964c93
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:36:28 2018 +0300

    multiple files: calloc -> malloc
    
    xlators/cluster/stripe/src/stripe-helpers.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    xlators/cluster/dht/src/tier.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    xlators/cluster/dht/src/dht-layout.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    xlators/cluster/dht/src/dht-helper.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    xlators/cluster/dht/src/dht-common.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    xlators/cluster/afr/src/afr.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    xlators/cluster/afr/src/afr-inode-read.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    tests/bugs/replicate/bug-1250170-fsync.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    tests/basic/gfapi/gfapi-async-calls-test.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    tests/basic/ec/ec-fast-fgetxattr.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    rpc/xdr/src/glusterfs3.h: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    rpc/rpc-transport/socket/src/socket.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    rpc/rpc-lib/src/rpc-clnt.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    extras/geo-rep/gsync-sync-gfid.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    cli/src/cli-xml-output.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    cli/src/cli-rpc-ops.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    cli/src/cli-cmd-volume.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    cli/src/cli-cmd-system.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    cli/src/cli-cmd-snapshot.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    cli/src/cli-cmd-peer.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    cli/src/cli-cmd-global.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Original-Author: Yaniv Kaul <ykaul@redhat.com>
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    
    Change-Id: I16274dca4078a1d06ae09a0daf027d734b631ac2

commit 81cbbfd1d870bea49b8aafe7bebb9e8251190918
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Aug 4 09:51:26 2018 +0300

    Multiple files: calloc -> malloc
    
    xlators/storage/posix/src/posix-inode-fd-ops.c:
    xlators/storage/posix/src/posix-helpers.c:
    xlators/storage/bd/src/bd.c:
    xlators/protocol/client/src/client-lk.c:
    xlators/performance/quick-read/src/quick-read.c:
    xlators/performance/io-cache/src/page.c
    xlators/nfs/server/src/nfs3-helpers.c
    xlators/nfs/server/src/nfs-fops.c
    xlators/nfs/server/src/mount3udp_svc.c
    xlators/nfs/server/src/mount3.c
    xlators/mount/fuse/src/fuse-helpers.c
    xlators/mount/fuse/src/fuse-bridge.c
    xlators/mgmt/glusterd/src/glusterd-utils.c
    xlators/mgmt/glusterd/src/glusterd-syncop.h
    xlators/mgmt/glusterd/src/glusterd-snapshot.c
    xlators/mgmt/glusterd/src/glusterd-rpc-ops.c
    xlators/mgmt/glusterd/src/glusterd-replace-brick.c
    xlators/mgmt/glusterd/src/glusterd-op-sm.c
    xlators/mgmt/glusterd/src/glusterd-mgmt.c
    xlators/meta/src/subvolumes-dir.c
    xlators/meta/src/graph-dir.c
    xlators/features/trash/src/trash.c
    xlators/features/shard/src/shard.h
    xlators/features/shard/src/shard.c
    xlators/features/marker/src/marker-quota.c
    xlators/features/locks/src/common.c
    xlators/features/leases/src/leases-internal.c
    xlators/features/gfid-access/src/gfid-access.c
    xlators/features/cloudsync/src/cloudsync-plugins/src/cloudsyncs3/src/libcloudsyncs3.c
    xlators/features/bit-rot/src/bitd/bit-rot.c
    xlators/features/bit-rot/src/bitd/bit-rot-scrub.c
    bxlators/encryption/crypt/src/metadata.c
    xlators/encryption/crypt/src/crypt.c
    xlators/performance/md-cache/src/md-cache.c:
    
    Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    .. and allocate memory as much as needed.
    
    xlators/nfs/server/src/mount3.c :
    
    Don't blindly allocate PATH_MAX, but strlen() the string and allocate
    appropriately.
    Also, align error messges.
    
    updates: bz#1193929
    Original-Author: Yaniv Kaul <ykaul@redhat.com>
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    Change-Id: Ibda6f33dd180b7f7694f20a12af1e9576fe197f5

commit 4cfbdfd0c851e4a5c6f4303a9141f34f8887b376
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Aug 7 23:57:28 2018 +0530

    geo-rep : fix coverity issues in glusterd-geo-rep.c
    
    This patch fixes RESOURCE_LEAK at line number 1344, 2088, 4819, 1347,
    2092, 1608, 1612, 2284, 3837.
    
    It also fixes FORWARD_NULL at line number 2955.
    
    CID : 1175012, 1175014, 1210989, 1223042, 1223043, 1382381, 1382429,
    1389120, 1389474, 1390452, 1356512.
    
    Change-Id: I7de239944eb61073d208ecf3899999a1ea0c8e43
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 6d5d3d1d095a7df2b49b56246021d302a4b7d695
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 23:35:58 2018 +0300

    xlators/cluster/afr/src/afr-inode-read.c: move to GF_MALLOC() instead of GF_CALLOC() when
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    Change-Id: Ief156de98769fea852553044a398a309e831754b
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 13deb311b2a48170489bb4f7cfd7def982281fd4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Aug 31 20:42:21 2018 +0530

    glusterd: fail volume stop operation if brick detach fails
    
    While sending a detach request for a brick in brick multiplexing mode,
    in any situation if the brick isn't connected, glusterd will fail to
    detach the brick but due to the missing error code handling, glusterd
    will mark the volume as stopped.
    
    Fix is to handle the return code of send_attach_req in
    glusterd_volume_stop_glusterfs ()
    
    Change-Id: I886202969c96eec3620f74cd7027652d6287f4be
    Fixes: bz#1624440
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit f29689783d970cba804505d7c778c905b2ba1992
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Aug 27 12:40:16 2018 +0530

    cluster/afr: Delegate name-heal when possible
    
    Problem:
    When name-self-heal is triggered on the mount, it blocks
    lookup until name-self-heal completes. But that can lead
    to hangs when lot of clients are accessing a directory which
    needs name heal and all of them trigger heals waiting
    for other clients to complete heal.
    
    Fix:
    When a name-heal is needed but quorum number of names have the
    file and pending xattrs exist on the parent, then better to
    delegate the heal to SHD which will be completed as part of
    entry-heal of the parent directory. We could also do the same
    for quorum-number of names not present but we don't have
    any known use-case where this is a frequent occurrence so
    not changing that part at the moment. When there is a gfid
    mismatch or missing gfid it is important to complete the heal
    so that next rename doesn't assume everything is fine and
    perform a rename etc
    
    fixes bz#1622821
    Change-Id: I8b002c85dffc6eb6f2833e742684a233daefeb2c
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit af0d5a9b5375a5cd87ac10b429e2b9934718ce5b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 29 11:09:27 2018 -0400

    core: python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/,
        https://review.gluster.org/#/c/20207/,
        https://review.gluster.org/#/c/20227/,
        https://review.gluster.org/#/c/20307/,
        https://review.gluster.org/#/c/20320/,
        https://review.gluster.org/#/c/20332/,
        https://review.gluster.org/#/c/20364/,
        https://review.gluster.org/#/c/20441/, and
        https://review.gluster.org/#/c/20484
    
    shebangs changed from /usr/bin/python2 to /usr/bin/python3.
    (Reminder, various distribution packaging guidelines require use
    of explicit python version and don't allow '#!/usr/bin/env python',
    regardless of how handy that idiom may be.)
    
    glusterfs.spec(.in) package python{2,3}-gluster and python2 or
    python3 dependencies as appropriate.
    
    configure(.ac):
    + test for and use python2 or python3 as appropriate. If build
      machine has python2 and python3, use python3. Override by
      setting PYTHON=/usr/bin/python2 when running configure.
    + PYTHONDEV_CPPFLAGS from python[23]-config --includes is a
      better match to the original python sysconfig.get_python_inc().
      All those other extraneous flags breaks the build.
    + Only change the shebangs once. Changing them over and over
      again, e.g., during a `make glusterrpms` in extras/LinuxRPM
      just sends make (is it really make that's looping?) into an
      infinite loop. If you figure out why, let me know.
    + Oldest python2 is python2.6 on CentOS 6 and Debian 8 (Jessie).
      Everything else has 2.7 or 3.x
    + logic from https://review.gluster.org/c/glusterfs/+/21050, which
      needs to be removed/merged after that patch is merged.
    
    Builds on CentOS 6, CentOS 7, Fedora 28, Fedora rawhide, and the
    mysterious RHEL > 7.
    
    Change-Id: Idae21d3b6f58b32372e1daa0d234e491e563198f
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit eda69f2e327f5f65d14190eed1821a0f45b2f914
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 28 12:00:33 2018 +0530

    cluster/dht: In rename, unlink after creating linkto file
    
    The linkto file creation for the dst was done in parallel with
    the unlink of the old src linkto. If these operations reached
    the brick out of order, we end up with a dst linkto file without
    a .glusterfs handle.
    
    Fixed by the unlinking only after the linkto file creation has
    completed.
    
    Change-Id: I4246f7655f5bc180f5ded7fd34d263b7828a8110
    fixes: bz#1621981
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 35aa67001c8fac99b040fbc61f36ef4f1b1590ac
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Aug 21 06:09:44 2018 -0400

    libgfchangelog: Fix changelog history API
    
    Problem:
    If requested start time and end time doesn't fall into
    first HTIME file, then history API fails even though
    continuous changelogs are avaiable for the requested range
    in other HTIME files. This is induced by changelog disable
    and enable which creates fresh HTIME index file.
    
    Cause and Analysis:
    Each HTIME index file represents the availability of
    continuous changelogs. If changelog is disabled and enabled,
    a new HTIME index file is created represents non availability
    of continuous changelogs. So as long as the requested start
    and end falls into single HTIME index file and not across,
    history API should succeed.
    
    But History API checks for the changelogs only in first
    HTIME index file and errors out if not available.
    
    Fix:
    Check in all HTIME index files for availability of continuous
    changelogs for requested change.
    
    fixes: bz#1622549
    Change-Id: I80eeceb5afbd1b89f86a9dc4c320e161907d3559
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 052849983e51a061d7fb2c3ffd74fa78bb257084
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 20:43:07 2018 +0300

    Various files: strncpy()->sprintf(), reduce strlen()'s
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf(). Check for truncated output
    where applicable.
    
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN (sizeof() ) for const strings.
    
    Compile-tested only!
    
    Change-Id: I54e80d4f4a80e98d3775e376efe05c51af0b29eb
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 67cfacaa9d5ce31240a4d39e81b2984a57ac8865
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Aug 30 15:08:02 2018 +0530

    cluster/ec: Fix Coverity issue
    
    Fix following coverity issues-
    
    CID:
    1382378
    1382459
    
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=85091670&defectInstanceId=25915064&mergedDefectId=1382459
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=85091670&defectInstanceId=25915063&mergedDefectId=1382378
    
    Problem:
    ASSERT_LOCAL(this, healer) function is supposed to get the local healer
    so that we can take advantage of it while healing and reading data.
    
    However, we are not using healer->local anywhere.
    Also, this is not as useful in context of EC as it is in AFR.
    In EC we have to raed fragments from 4 bricks to heal a bad
    fragment on other brick.
    
    Change-Id: Iea8ce127ea02cc84e3823cb2be82a47872217b33
    updates: bz#789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 19436f2e5fa6dc7f33b7d32d170d3c18f5fdd0d4
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Jul 27 14:53:30 2018 +0530

    thin arbiter: set notify-contention option to yes
    
    If this option is "ON' and if there is a lock contention for
    a file from 2 clients/self-heal daemon, an up call will
    be sent to all the clients holding that locks. Clients
    can handle this notification and may release the locks
    at the right time asap.
    
    If this option is ON, we get "instant" lock contention
    notification on client side.
    
    In next version of thin arbiter,  we need to implement
    lock contention notification handling and two domain
    locking to synchronize update/access of xattrs of thin arbiter
    replica id file. This option is an efficient way to find
    out lock contention. In this case it is also helping to
    implement two domain locking for replica id file.
    
    Change-Id: I69883898d52feb425dfceb31cf12fa2157aaa314
    fixes bz#1609207
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit cd1051789361bd07e248baf1bf0fbbe479cd4ae1
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 20:29:17 2018 +0300

    NFS server (mount3.c, nfs-inodes.c): strncpy()->sprintf(), reduce strlen()'s
    
    xlators/nfs/server/src/mount3.c
    xlators/nfs/server/src/nfs-inodes.c
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf().
    
    Compile-tested only!
    
    Change-Id: Ibe74ccdb67434e9a10fc1f21c0b4cd5e4b8cb589
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit a1d61242baed1c2078707c401632719e756fcacb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 19:25:11 2018 +0300

    changetimerecoder xlator: strncpy()->sprintf(), reduce strlen()'s
    
    xlators/features/changetimerecorder/src/changetimerecorder.c
    xlators/features/changetimerecorder/src/ctr-helper.h
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf(). Check for output truncation
    where applicable.
    
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN (sizeof() ) for const strings.
    
    Compile-tested only!
    
    Change-Id: I2dd5629183222da8c9251af43b8b29aacf12a20a
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 7772315bd7d82d5f06f008dfe767f1e597a41b23
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 20:42:53 2018 +0300

    multiple xlators (storage/posix): strncpy()->sprintf(), reduce strlen()'s
    
    xlators/storage/posix/src/posix-gfid-path.c
    xlators/storage/posix/src/posix-handle.c
    xlators/storage/posix/src/posix-helpers.c
    xlators/storage/posix/src/posix-inode-fd-ops.c
    xlators/storage/posix/src/posix.h
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf().
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN (sizeof() ) for const strings.
    
    Compile-tested only!
    
    Change-Id: I056939f111a4ec6bc8ebd539ebcaf9eb67da6c95
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit dc6e6b71f87f6f89bb0b69816e92779595d716bd
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 19:23:01 2018 +0300

    changelog xlator: strncpy()->sprintf(), reduce strlen()'s
    
    xlators/features/changelog/lib/src/gf-changelog-journal-handler.c
    xlators/features/changelog/lib/src/gf-changelog.c
    xlators/features/changelog/src/changelog-helpers.c
    xlators/features/changelog/src/changelog-misc.h
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf(). Where possible, ensure there's
    no truncation of the output.
    
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN (sizeof() ) for const strings.
    - switch a strncpy to a memcpy.
    
    Compile-tested only!
    
    Change-Id: Ia7a52bce0b243613ad910192ec163c93d944e077
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 058d215174b93b3aa14be99073979f45642e519e
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 20:32:01 2018 +0300

    multiple xlators: move from strlen() to sizeof()
    
    xlators/performance/nl-cache/src/nl-cache.c
    xlators/performance/md-cache/src/md-cache.c
    xlators/protocol/server/src/authenticate.c
    xlators/storage/bd/src/bd-helper.c
    
    For const strings, just do compile time size calc instead of runtime.
    
    Compile-tested only!
    
    Change-Id: I9b98940a38d85321a69436a1871930da367b918a
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d6d729b0609957c0382749c30da507dda77561b7
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 19:33:16 2018 +0300

    xlators: move from strlen() to sizeof()
    
    xlators/features/index/src/index.c
    xlators/features/shard/src/shard.c
    xlators/features/upcall/src/upcall-internal.c
    xlators/mgmt/glusterd/src/glusterd-bitrot.c
    xlators/mgmt/glusterd/src/glusterd-locks.c
    xlators/mgmt/glusterd/src/glusterd-mountbroker.c
    xlators/mgmt/glusterd/src/glusterd-op-sm.c
    
    For const strings, just do compile time size calc instead of runtime.
    
    Compile-tested only!
    
    Change-Id: I995b2b89f14454b3855a4cd0ca90b3f01d5e080f
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 437455c1608a0c644d14798551c77e9513ba9901
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Aug 30 17:32:55 2018 +0530

    crypt : fix coverity issues in crypt.c
    
    This patch fixes CID 1356527, 1356528, 1356529, 1356530, 1395251.
    
    Change-Id: Ibdbc56a3221bff3535f02a9e73b57fcbe35c3fbd
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 4b5e3c347cfb80e4749f1963e25d1dd93563f784
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 19:20:25 2018 +0300

    bit-rot xlator: strncpy()->sprintf(), reduce strlen()'s
    
    xlators/features/bit-rot/src/bitd/bit-rot-scrub-status.c
    xlators/features/bit-rot/src/stub/bit-rot-stub-helpers.c
    xlators/features/bit-rot/src/stub/bit-rot-stub.c
    xlators/features/bit-rot/src/stub/bit-rot-stub.h
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf(). Ensure sprintf() results do not
    truncate.
    
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN or sizeof() for const strings.
    - move ret from int32 to int.
    
    Compile-tested only!
    
    Change-Id: Ib9b923c45d2d59ac15a105410e8160b252061018
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 4996a229f3d09cbb6ed3b9dcdf1d527f36803919
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Aug 13 12:18:51 2018 +0530

    libglusterfs : fix coverity issues in common-utils.c
    
    Fixes CID 1351691, 1351678, 1274192, 1274117, 1124845.
    
    Change-Id: I65805524de85fb2186260288641390458a719499
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 25c405ac688787ea3f03ca4d427f2b00544dbbd0
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Aug 27 21:25:47 2018 +0300

    xlators/cluster/dht/src/dht-common.c: simplify some if statements
    
    Use goto when some vars are not set to simplify long if statements.
    Please review logic has not changed!
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I45ea2e906d0ccb468af5e1fa65db008edb00d734

commit 3ff3b5823bed9d43d2966c1a3b45f26631d15897
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Aug 27 23:45:15 2018 +0300

    libglusterfs/src/dict.c: fix to handle key=NULL.
    
    We don't want to strlen NULL strings.
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Id795998693ba410dbd80df962d48956a9e4164c4

commit d3b1456c52f7dc4f21cdae2855092fda6b96af4a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Aug 28 00:01:26 2018 +0530

    clang-scan: fix multiple issues
    
    * Buffer overflow issue in glusterfsd
    * Null argument passed to function expecting non-null (event-epoll)
    * Make sure the op_ret value is set in macro (posix)
    
    Updates: bz#1622665
    
    Change-Id: I32b378fc40a5e3ee800c0dfbc13335d44c9db9ac
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 6a2f83caad7ff882e3a8da5fdec4be8ceccbfdc2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Aug 27 18:19:58 2018 +0530

    coverity: multiple fixes
    
    CID: 1390477, 1124827
    
    updates: bz#789278
    Change-Id: I41060d131aec6e58e7267ac8531b29a70f8c4359
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 33f53e88c31394ef5b0b927cd11f8b349647b435
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Aug 30 16:31:39 2018 +0530

    cli : fix coverity issue in cli-cmd-volume.c
    
    This patch fixes 1389756.
    
    Change-Id: I72d4f618368545a5dcee0ca59fe87ba6137ab4a1
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit a654ae2442899348aae136365786dc44a9f502ca
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Aug 27 16:11:03 2018 +0530

    nfs-server : fix few coverity issues in mount3.c
    
    This patch fixes 1388767 and 1389057.
    
    Change-Id: Id4ee7c3cd72e46112315f6dccb08e76788b40d27
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 38b69225f56271503f0ac2c72c646990e8559624
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Aug 27 13:48:23 2018 +0530

    libglusterfs/gfdb_data_store: handle a range-overflow condition
    
    As the value read from the file is not checked for the range,
    and the same value is directly used to allocate, and read further
    values, it can cause major issues.
    
    CID: 1351699
    
    updates: bz#789278
    Change-Id: I7ff4c1791343861ebf98d1c615b52af54cb2485e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 459ea3e78136ee74b71ae00b448245de7148cdfe
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Aug 30 09:47:18 2018 +0530

    rpc: log fuse unique ID along with gluster XID
    
    for better traceability between fuse requests and gluster requests a
    mapping needs to be established in the logs between the two IDs
    
    BUG: 1623408
    Change-Id: I0ef82fe69c1ad7d0ce9e3ac4f35cd82aa6e9bca9
    fixes: bz#1623408
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit a38f9cb7a6c9a25ceef9a0638add39dfd2b0c0d9
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Aug 29 01:39:28 2018 +0530

    glusterd : fix some coverity issues in glusterd-syncop.c
    
    This patch fixes CID 1382344, 1124655 and 1325537.
    
    Change-Id: I2412d6b88483e32a5de1baebb3823a985b2dcfb0
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 44e40404ed1223ba9ccb879373da38efd5ba403c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Aug 9 15:52:19 2018 +0200

    build: add --enable-asan configure options
    
    Introduce a `./configure --enable-asan` to build with
    `-fsanitize=address -fno-omit-frame-pointer` options. This uses the
    libasan.so shared library, so that needs to be available.
    
    While running builds with the ASAN options, several linker issues
    surfaced and these have been addressed with this change as well.
    Building with --enable-asan has been tested on Fedora 28.
    
    Change-Id: I428a9da70dd8f7d0056cfbe5c398619a571469b2
    Updates: #492
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit d27e8870c1882b1abfffefaf7b40bc7f2a1ec05f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Aug 24 17:24:15 2018 +0300

    libglusterfs/src/dict.c: allocate memory accurately.
    
    I suspect we've allocated and then set to '\0' an
    additional byte for no reason: gf_asprintf() allocates
    enough inc. the terminating null; data->len took that
    additional byte into account; memcpy() it back
    took care of that terminating null byte as well.
    
    Also, unrelated, implemented str_to_data() via
    strn_to_data().
    
    Compile-tested only!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I32c90e12974f51a0fbc0cfaebf9bd0fd722adc11

commit f29e46f97737d9e2d154ba0e99c5ffb1d03eaa57
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Aug 29 14:24:29 2018 +0530

    IO cache : fix coverity issues in io-cache.c
    
    This patch fixes CID 1382361, 1124714 and 1382432.
    
    Change-Id: I0407f35ee44ec6e4522de46092658223d0c8ee6a
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit cbe133c832fd9907619a1231aa3d9dda1330ae74
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Aug 24 20:59:30 2018 +0300

    multiple files: remove unndeeded memset()
    
    This is a squash of multiple commits:
    
    contrib/fuse-lib/misc.c: remove unneeded memset()
    
    All flock variables are properly set, no need to memset it.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I8e0512c5a88daadb0e587f545fdb9b32ca8858a2
    
    libglusterfs/src/{client_t|fd|inode|stack}.c: remove some memset()
    
    I don't think there's a need for any of them.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I2be9ccc3a5cb5da51a92af73488cdabd1c527f59
    
    libglusterfs/src/xlator.c: remove unneeded memset()
    
    All xl->mem_acct members are properly set,
    no need to memset it.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I7f264cd47e7a06255a3f3943c583de77ae8e3147
    
    xlators/cluster/afr/src/afr-self-heal-common.c: remove unneeded memset()
    
    Since we are going over the whole array anyway, initialize it
    properly, to either 1 or 0.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ied4210388976b6a7a2e91cc3de334534d6fef201
    
    xlators/cluster/dht/src/dht-common.c: remove unneeded memset()
    
    Since we are going over the whole array anyway it is initialized
    properly.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Idc436d2bd0563b6582908d7cbebf9dbc66a42c9a
    
    xlators/cluster/ec/src/ec-helpers.c: remove unneeded memset()
    
    Since we are going over the whole array anyway it is initialized
    properly.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I81bf971f7fcecb4599e807d37f426f55711978fa
    
    xlators/mgmt/glusterd/src/glusterd-volgen.c: remove some memset()
    
    I don't think there's a need for any of them.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I476ea59ba53546b5153c269692cd5383da81ce2d
    
    xlators/mgmt/glusterd/src/glusterd-geo-rep.c: read() in 4K blocks
    
    The current 1K seems small. 4K is usually better (in Linux).
    
    Also remove a memset() that I don't think is needed between reads.
    
    Only compile-tested!
    
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I5fb7950c92d282948376db14919ad12e589eac2b
    
    xlators/storage/posix/src/posix-{gfid-path|inode-fd-ops}.c: remove memset()
    before sys_*xattr() functions.
    
    I don't see a reason to memset the array sent to the functions
    sys_llistxattr(), sys_lgetxattr(), sys_lgetxattr(), sys_flistxattr(),
    sys_fgetxattr().
    
    (Note: it's unclear to me why we are calling sys_*txattr() functions with
    XATTR_VAL_BUF_SIZE-1 size instead of XATTR_VAL_BUF_SIZE ).
    
    Only compile-tested!
    
    Change-Id: Ief2103b56ba6c71e40ed343a93684eef6b771346
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 789a5a3d3cbad9c594fd2a94924ec0a2040c27ad
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Aug 28 11:03:47 2018 +0530

    glusterd: Fix coverity issues
    
    This patch fixes CID's 1395250, 1395252
    1395250 - Unintialized variable
    1395252 - Out of bounds access
    
    updates: bz#789278
    
    Change-Id: Icf646364b14d48fa2bd82ea78ca5cdb5c684355f
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 2a7ce9ecc919e390208bc3449f6c5fa320b7efe4
Author: karthik-us <ksubrahm@redhat.com>
Date:   Tue Aug 28 12:51:00 2018 +0530

    cluster/afr: Coverity fixes in afr
    
    Fixes the deadcode issue in "afr-common.c" and
    null pointer dereference isse in "afr-dir-read.c".
    
    CIDs: 1395160, 1389018
    
    Scan details:
    https://scan6.coverity.com/reports.htm#v42418/p10714/fileInstanceId=85017760&defectInstanceId=25877740&mergedDefectId=1395160
    https://scan6.coverity.com/reports.htm#v42418/p10714/fileInstanceId=85017734&defectInstanceId=25877951&mergedDefectId=1389018
    
    Change-Id: I65dff57305aa3ae43544be5353f801d761193e97
    updates: bz#789278
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 8d171374cbbbdd88c8714198903b317bd132e1e2
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 19:18:17 2018 +0300

    multiple files: move from strlen() to sizeof()
    
    {glusterfsd|glusterfsd-mgmt|quota-common-utils|xlator|tier|stripe}.c
    tools/setgfid2path/src/main.c
    xlators/cluster/afr/src/afr-inode-read.c
    {glusterfs-acl|glusterfs}.h
    
    For const strings, just do compile time size calc instead of runtime.
    
    Compile-tested only!
    
    Change-Id: I303684b1ff29b05c10126fb1057f507e404ced07
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 60ef38482cc8d61711ecc48159cf6c036b1522a8
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Aug 28 09:06:56 2018 +0530

    cli: dereferencing null coverity fix
    
    CID: 1124489
    
    https://scan6.coverity.com/reports.htm#v42375/p10714/fileInstanceId=85018660&defectInstanceId=25877775&mergedDefectId=577602
    
    updates: bz#789278
    Change-Id: I0ebfbc52ecd5e3b70574df5f286116f872514cc6
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 043932a4d81c38d88487c2709eceaf8d5b91be35
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Aug 28 11:34:40 2018 +0530

    snapshot : fixed coverity issue in glusterd-snapshot.c
    
    This patch fixes CID 1395253 and indentation.
    
    Change-Id: Iffcd992d3d49765c7e47b864724f83c7c5d57579
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit ccaad48f51d4e8d3de001dc3907df68c69f8792b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Aug 27 11:46:33 2018 +0530

    cluster/afr: Delegate metadata heal with pending xattrs to SHD
    
    Problem:
    When metadata-self-heal is triggered on the mount, it blocks
    lookup until metadata-self-heal completes. But that can lead
    to hangs when lot of clients are accessing a directory which
    needs metadata heal and all of them trigger heals waiting
    for other clients to complete heal.
    
    Fix:
    Only when the heal is needed but the pending xattrs are not set,
    trigger metadata heal that could block lookup. This is the only
    case where different clients may give different metadata to the
    clients without heals, which should be avoided.
    
    Updates bz#1622821
    Change-Id: I6089e9fda0770a83fb287941b229c882711f4e66
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 37f77b124283c3252ef00935628ff30b3e5696e6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Aug 27 09:26:43 2018 +0530

    playground: fix coverity issue
    
    CID: 1395161
    
    Updates: bz#789278
    Change-Id: I6cc5c488a8aa12d312c34e6535786fd4debcb24c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit df4beaf9a45a52d913cdf991d070e73e6bbcaf6f
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Aug 27 17:31:28 2018 +0530

    libglusterfs : fix coverity in store.c
    
    This patch fixes CID 1395103 and 1395102.
    
    Change-Id: I8c9fad85f254a55697b0bad185dcdd02be64f682
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit dcacaf15ec361a6f8bf79037ff47c2a8759b7170
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Aug 7 19:02:48 2018 +0530

    snapshot : fix few coverity issues in glusterd-snapshot-utils.c
    
    This patch fixes CID 1210987 and 1351650.
    
    Change-Id: Ic85bc6048651146a79fe68add19dcc095738a517
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit b76a84be697074e4132120200320671d87f815ae
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Aug 17 22:29:05 2018 +0300

    libglusterfs/src/dict.{c,h}: Introduce dict_setn, dict_addn, dict_addn and others.
    
    They all take as a parameter the key length, instead of strlen() it.
    In most cases, we know the key length, we just never bothered to save and pass it along.
    (We most likely sprintf'ed it earlier and the return value could have been used).
    
    A more interesting addition is dict_set_nstrn() [horrible name. Ideas are welcome].
    It accepts both the string length and the key length and avoids strlen() both.
    Some of it can be calculated on compile-time, btw.
    For example:
    dict_set_str (dict, "key", "all");
    Should become:
    dict_set_nstrn (dict, "key", sizeof ("key"), "all", sizeof ("all"));
    
    Compile-tested only!
    
    Change-Id: Ic2667f445f6c2e22e279505f5ad435788b4b668c
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c416327b31d4a5dad619007c13c3e9a06e3cd398
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Aug 17 14:02:35 2018 +0300

    libglusterfs/src/dict.c: perform hash calc not under lock.
    
    If possible, perform the key hash calculation not under
    the dictionary lock.
    
    Compile-tested only!
    
    Change-Id: I88b6ed4eff6660d8334bc08ca4eebf61960e3ca1
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 161afaf0851bb1765cd033395f70b5b59c7352d0
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Fri Aug 24 16:51:54 2018 +0300

    dict.c: fix indention
    
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    
    Change-Id: I3f210ae236f778fd0e8e7a17d01da21f65cb4e4b

commit c0a4ce316dcdfee918073479eb197a2f9f5684e5
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Aug 26 16:46:55 2018 -0700

    features/namespace: Fix a probable null dereference
    
    Addresses CID: 1388656
    
    Change-Id: I614c29e993dd112ee02c5bffe8c737deb225c1f9
    Updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit ddaa43e6a27ee650bbf8fd6ee731276c98042a67
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Aug 22 12:03:04 2018 -0700

    cluster/ec: Prevent a possible out-of-bounds read
    
    Addresses CID 1370939
    
    In ec_code_x64_epilog(), there is a possibility of reading from an
    incorrect index of ec_code_x64_regmap array
    
    Change-Id: Ib8a228bbe13631188343634b2bde5919cdaab5a4
    Updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 1b499e9dfe63ce051a071cacc19e3161b7a32636
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Aug 27 12:18:21 2018 +0530

    glusterd: glusterd_brick_start shouldn't cleanup pidfile if only_connect is true
    
    Problem: Sometime glusterd cleanup pidfile even brick is started
             and cli shows volume status "N/A"
    
    Solution: Update the condition in glusterd_brick_start to avoid
              pidfile cleanup in case if only_connect flag is true
    
    Fixes: bz#1622422
    Change-Id: I8decb34597126b848e3a44d957e138833dd97350
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a03f31290674d1a446e9551aabb1e306fc9064a8
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jul 31 20:50:30 2018 +0300

    dict.c: do not strlen if not needed.
    
    Use the output of sprintf().
    
    Also, constify and initialize parameters properly.
    
    Only compile-tested!
    
    Change-Id: I33870afbe14bc1292fb08115e878d48c00a43bee
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 98714f503768db9a2ee442a544702c801a31ae6d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Aug 24 07:16:18 2018 -0400

    geo-rep: Make automatic gfid conflict resolution optional
    
    Autmatic gfid conflict resolution needs to be disabled
    during failover/failback as it might lead to data loss
    in the following scenario.
    
    1. Master went down without syncing directory "dir1" to slave.
    2. When slave is failed over to master, if a new file
       is written inside "dir1", creating dir1 again if not
       present, "dir1" ends up with different gfid on original
       slave.
    3. When original master is up and failed back, due to
       automatic gfid conflict resolution, "dir1" present in
       original master is deleted losing all files and only
       new file created on original slave is restored.
    
    Hence during failover/failback, automatic gfid conflict
    resolution should be disabled. So in these cases, appropriate
    decision is taken.
    
    fixes: bz#1622076
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Change-Id: I433616f5d3e13d4b6eb675475bd554ca34928573

commit f74181f85ab953b1f08eae358784e4b102b773b9
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Aug 23 14:24:56 2018 +0530

    feature/shard: Fix Coverity issue
    
    Fix following coverity issues-
    
    CID:
    1394660
    1394668
    1394667
    1389008
    1389434
    
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=84880983&defectInstanceId=25821108&mergedDefectId=1389008
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=84880983&defectInstanceId=25821101&mergedDefectId=1389434
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=84880983&defectInstanceId=25821001&mergedDefectId=1394660
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=84880983&defectInstanceId=25821010&mergedDefectId=1394667
    https://scan6.coverity.com/reports.htm#v42607/p10714/fileInstanceId=84880983&defectInstanceId=25821017&mergedDefectId=1394668
    
    Change-Id: I08f09649dbe758ba0d367ae5330b48b18784dec3
    updates: bz#789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 7f89cff0cdc63c4b6734bd2e3c56ee0e70957813
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Tue Aug 7 09:30:37 2018 +0800

    posix-acl: skip acl_permits check when the owner setting GF_POSIX_ACL_xxxx
    
    Change-Id: Iaeea470d040587027f37e0760ae27c4fc205a189
    fixes: bz#1613098
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 30e46a9b3cef868e5c781044c99c3d5b066d4760
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Fri Aug 24 10:44:59 2018 +0530

    ctr: skip ctr xlator init if ctr is not enabled
    
    Problem: If ctr xlator is not required it consumes
             resources unnecessarily
    
    Solution: Call ctr xlator init only while feature is enabled
    
    Fixes: bz#1524323
    
    Change-Id: I378113a390a286be20c4ade1b1bac170a8ef1b14
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 57da742b13c85b5671be2638d7c9d1d31c5c93bb
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Sat Aug 25 15:07:02 2018 +0530

    cli : fix coverity cli-rl.c
    
    This fixes new coverity issue introduced by commit 5acb74d7da.
    
    Fixes 1395188.
    
    Change-Id: I629e5f214150672e309abb2fc58f55f1f58d8fb7
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit d34455a2d2d267c545c25ad7fa710ae2677d5afb
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Aug 14 14:00:41 2018 -0400

    tests: Preserve tarball of tests when they timeout
    
    When tests timeout, the timeout command sends TERM
    signal to the command being executed. In the case of run-tests.sh
    it invokes prove, which further invokes perl and finally the test
    is run using bash. The TERM signal does not seem to be reachnig
    the end bash that is actually executing the tests, and hence
    when any test is terminated due to a timeout, the cleanup routine
    in include.rc does not get a chance to run and preserve the
    tarball.
    
    Further, cleanup invokes tarball generation, but is invoked at
    the beginning and end of every test, and at times in beteween
    as well. This caused way too many tarballs in case we decide to
    preserve the same whenever generated by cleanup.
    
    This patch hence moves the tarball generation to run-tests.sh
    instead, and further stores them named <test>-iteration-<n>.tar
    and also prints tarball name generated and stored per iteration.
    
    This should help relate failed runs to the tarball iteration #
    and to look at relevant logs.
    
    Further the patch also provides a -p option to run-tests.sh for
    unit testing purposes, where running a test in a loop without the
    option will generate as many tarballs, and using the option will
    reduce this to preserving the last tarball, saving space in
    smaller unit test setups.
    
    Fixes: bz#1614062
    Change-Id: I0aee76c89df0691cf4d0c1fcd4c04dffe0d7c896
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 43f037f6b10c5b1da1b56bc4e2ae4c4ae5c475ec
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Aug 24 09:42:12 2018 -0700

    mgmt/glusterd: Coverity fixes in glusterd-utils.c
    
    Addresses the following CIDs:
    
    1388821: Unchecked return value from sys_lremovexattr() in
    glusterd_check_and_set_brick_xattr()
    1370957: Unused return value in glusterd_volume_tier_use_rsp_dict()
    1370950: Memory leak in glusterd_get_global_options_for_all_vols()
    1370946: Redundant gf_strdup() leading to a memory leak in
    glusterd_get_global_options_for_all_vols()
    
    Change-Id: I2ab58207bc43b40f004ee18463430a141126bf94
    Updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 0e5ff35f1e328a61a85cf0e04ba125a6c72b4069
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Aug 22 18:49:49 2018 -0700

    storage/posix: Coverity fixes in posix-handle.c
    
    Addresses the following CIDs:
    
    1370938: Out of bounds write in posix_make_ancestryfromgfid()
    1351642: UnChecked return value from sys_stat() in posix_handle_init()
    
    Change-Id: I3483ebcd798793ce6c504e92b4ea203bcf99fc0e
    Updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 14ee864f8b573d1bccf4f586450947ba4aa690a9
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 18:56:24 2018 +0300

    multiple files: move from strlen() to sizeof()
    
    {ec-heal|ec-combine|ec-helpers|ec-inode-read}.c
    
    For const strings, just do compile time size calc instead of runtime.
    
    Compile-tested only!
    
    Change-Id: If92ba0a7a20f64b898d01c6e3b6708190ca93e04
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 7e229cf1d5d4c0600f0763dac3acacb1b950fc3b
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 18:32:53 2018 +0300

    extras/geo-rep/gsync-sync-gfid.c: move from strlen() to sizeof()
    
    For const strings, just do compile-time size calc instead of runtime.
    
    Compile-tested only!
    
    Change-Id: I89470016389a4ecb3bed35a1c9e684f5fae79997
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit a2c562eb4046ce88c8c2f2d250b0079942e7f10a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 18:31:03 2018 +0300

    {mount-common|fusermount|mount_darwin|umountd}.c: strncpy()->sprintf(), reduce strlen()'s
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf().
    
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from strlen to SLEN (sizeof() ) for const strings.
    
    Compile-tested only!
    
    Change-Id: I369209b36d8356c3fe00d32f8bf56e74cf9963db
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 938849a417727c85f1925dde641b3c6c54c71275
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 18:25:33 2018 +0300

    {cli-cmd-parser|cli-rpc-ops||cli-xml-output}.c: strncpy()->sprintf(), reduce strlen()'s
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf().
    
    Also:
    - save the result of strlen() and re-use it when possible.
    - move from GF_CALLOC() to GF_MALLOC() for the strings.
    - move from strlen to sizeof() for const strings.
    
    Compile-tested only!
    
    Change-Id: I3cf49c5401ee100a5db6a4954c3d699ec1814c17
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 036327d9e963c84a5222f8d1c7598ab36ad46a4b
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 18:21:25 2018 +0300

    glfs-fops.c, glfs.c: strncpy() -> sprintf(), reduce strlen()'s
    
    strncpy may not be very efficient for short strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, use snprintf().
    
    Also, save the result of strlen() and re-use it when possible.
    
    Compile-tested only!
    
    Change-Id: I4ecfb359cf0efaafeab245a8138f526b21613231
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 5acb74d7daee0fc5c501a82e604ec2abdb3cf88a
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Aug 10 00:57:09 2018 +0530

    cli : fix few coverity in cli
    
    This patch fixes DEADCODE and FORWARD_NULL.
    
    CID : 1124495, 1124380, 1124381
    
    Change-Id: I79992e396dbcb1bfe6cd0614d49a8da3f67d648d
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 3cb5b63a0a78048f8d09e59ab5d79bc2f659ed17
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Aug 23 16:11:25 2018 -0700

    debug/error-gen: Prevent a possible null dereference
    
    Addresses CID: 1124492
    
    Change-Id: I92f807b5e45537e68c318bcbf54ccaa23d18b0dd
    Updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 9c49927e64b238cb077ae26c4e77bfe5bfc6a6bd
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Thu Aug 23 18:22:09 2018 +0530

    block : fix few coverity issue
    
    Fixes 1128923, 1134020 and 1370936.
    
    updates: bz#789278
    
    Change-Id: I2cadc09ffd0814a9390ba068006fa56704d3820d
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 52efadc48684a800ab93eac6d2d92f8f34495e53
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Aug 12 17:28:07 2018 -0700

    features/cloudsync: Fix various resource leaks
    
    Addresses CID: 1394648, 1394653
    
    Change-Id: Ie75d4a268bba090faa5c3fe0e87f0e5cef3ff773
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 74475e878da1f9770ee7402a809eb911d846a2a7
Author: Shwetha Acharya <shwetha174@gmail.com>
Date:   Fri Aug 3 15:51:36 2018 +0530

    stripe: FORWARD_NULL coverity fix
    
    Problem: frame could be NULL.
    
    Solution: Added condition checks to avoid NULL pointer dereferencing.
    
    CID: 1124478, 1124501, 1124504, 1124510
    
    BUG: 789278
    Change-Id: I5c81d912102a7e672386db3fdb820f883d08666f
    Signed-off-by: Shwetha Acharya <shwetha174@gmail.com>

commit 94a532464d1149dc1574e2e4b5484d35415bde5b
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Mon Aug 20 21:06:37 2018 +0530

    locks: coverity fixes
    
    Fixes CID: 1356583 1356582 1356581 1356580
    
    Add logs and also replace gf_log with gf_msg_debug.
    
    Change-Id: I348dc94f7a52034542d29096c12a2cf60aabe97f
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit 8c4b20bc0b9d491bee1efb1a18d87852020f045d
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Tue Aug 21 13:00:48 2018 +0530

    marker: fix for coverity issues
    
    Fixes CID: 1325591 1356503 1325540 1351704
    
    Change-Id: I325b1184baa81402eaa009cb36ab95e5de812f6c
    updates: bz#789278
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit f75823f6fcb8aa3116f712ed69fbf4b35d4c3bdd
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 23 09:21:02 2018 +0300

    libglusterfs/src/iobuf.c: remove memset(), CALLOC -> MALLOC
    
    I'm not sure I see the need for those memset(), I've removed them.
    There's at least one easy to convert CALLOC to MALLOC - converted.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ia019775ad5255190f5d02d948ea27db7f563387d

commit 2785d2fdf710fcd323bef2d1cbbf17fe823a289f
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Aug 22 15:04:52 2018 -0400

    dht/switch: Fix coverity issues
    
    CID: 1124779: dup_childs not freed in an err path
    CID: 1382398: option_string leaked
    CID: 1382389: memcpy may cause string overflow
      Also, fixed up NULL termination for the string
    Potential use after free (or double free in this case) as below,
    (link split into multiple lines)
    https://download.gluster.org/pub/gluster/glusterfs/static-analysis/
      master/glusterfs-coverity/2018-08-22-0ebaa9c6/html/
      1/427switch.c.html#error
    
    Change-Id: I76681af6a8091666918a3d5dff30a152a7b97905
    Updates: bz#789278
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit f191bb7bc1abd250bdf0a5a6972ce95fcbd3314b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Jun 8 09:54:00 2018 -0400

        features/snapview-server: validate the fs instance before doing fop there
    
        PROBLEM:
        ========
    
        USS design depends on snapview-server translator communicating with each
        individual snapshot via gfapi. So, the snapview-server xlator maintains
        the glfs instance (thus the snapshot) to which a inode belongs to by
        storing it inside the inode context.
    
        Suppose, a file from a snapshot is opened by a application, and the fd
        is still valid from application's point of view (i.e. application has
        not yet closed fd). Now, if the snapshot to which the opened file
        belongs to is deleted, then the glfs_t instance corresponding to the
        snapshot is destroyed by snapview-server as part of snap deletion.
        But now, if the application does IO on the fd it has kept open, then
        snapview server tries to send that request to the corresponding snap
        via glfs instance for that snapshot stored in the inode context for
        the file on which the application is sending the fop. And this results
        in freed up glfs_t pointer being accessed and causes a segfault.
    
        FIX:
        ===
    
        For fd based operations, check whether the glfs instance that the inode
        contains in its context, is still valid or not.
    
        For non fd based operations, usually lookup should guarantee that. But
        if the file was already looked up, and the client accessing the snap data
        (either NFS, or native glusterfs fuse) does not bother to send a lookup
        and directly sends a path based fop, then that path based fop should
        ensure that the fs instance is valid.
    
    Change-Id: I881be15ec46ecb51aa844d7fd41d5630f0d644fb
    updates: bz#1602070
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 11a9f9f0dcca58446f306ef2060a345348ed91c1
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 13 14:52:09 2018 -0700

    mgmt/glusterd: Fix resource leak & unused value issues in glusterd-volume-ops.c
    
    Addresses CID: 1274132, 1325534
    
    Change-Id: I176612ef5baf5618d543838a5f32db7dcd7002c3
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 370f05546eeedab394ca0d333a6ca6637757f1e3
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Aug 21 09:44:15 2018 +0530

    performance/write-behind: fix fulfill and readdirp race
    
    Current invalidation of stats in wb_readdirp_cbk is prone to races. As
    the deleted comment explains,
    
    <snip>
        We cannot guarantee integrity of entry->d_stat as there are cached
        writes. The stat is most likely stale as it doesn't account the cached
        writes. However, checking for non-empty liability list here is not a
        fool-proof solution as there can be races like,
          1. readdirp is successful on posix
          2. sync of cached write is successful on posix
          3. write-behind received sync response and removed the request from
             liability queue
          4. readdirp response is processed at write-behind.
    
        In the above scenario, stat for the file is sent back in readdirp
        response but it is stale.
    </snip>
    
    The fix is to mark readdirp sessions (tracked in this patch by
    non-zero value of "readdirps" on parent inode) and if fulfill
    completes when one or more readdirp sessions are in progress, mark the
    inode so that wb_readdirp_cbk doesn't send iatts for that in inode in
    readdirp response. Note that wb_readdirp_cbk already checks for
    presence of a non-empty liability queue and invalidates iatt. Since
    the only way a liability queue can shrink is by fulfilling requests in
    liability queue, wb_fulfill_cbk indicates wb_readdirp_cbk that a
    potential race could've happened b/w readdirp and fulfill.
    
    Change-Id: I12d167bf450648baa64be1cbe1ca0fddf5379521
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    updates: bz#1512691

commit 59e560248771d3b95517a3e12c174e9acbf39585
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Aug 23 12:12:36 2018 +0530

    glusterd: glusterd_brick_start shouldn't try to bring up brick if only_connect is true
    
    With the latest refactoring in glusterd_brick_start () function in case
    we run into a situation where is_gf_service_running () return a valid
    pid which is running but doesn't belong to a gluster process, even in
    case of only_connect flag passed as gf_true we'd end up trying to start
    a brick which would cause a deadlock in brick multiplexing as both
    glusterd_restart_bricks () and glusterd_do_volume_quorum_action () would
    cause context switching with each other for the same brick. The
    following bt shows the same:
    
    (gdb) t a a bt
    
    Thread 8 (Thread 0x7fcced48a700 (LWP 11959)):
        srch_vol=srch_vol@entry=0xbe0410, comp_vol=comp_vol@entry=0xc03680,
        brickinfo=brickinfo@entry=0xc14ef0) at glusterd-utils.c:5834
        brickinfo=0xc14ef0, volinfo=0xc03680, conf=<optimized out>)
        at glusterd-utils.c:5902
        brickinfo=brickinfo@entry=0xc14ef0, wait=wait@entry=_gf_false,
        only_connect=only_connect@entry=_gf_true) at glusterd-utils.c:6251
        volinfo=0xc03680, meets_quorum=_gf_true) at glusterd-server-quorum.c:402
        at glusterd-server-quorum.c:443
        iov=iov@entry=0x7fcce0004040, count=count@entry=1,
        myframe=myframe@entry=0x7fcce00023a0) at glusterd-rpc-ops.c:542
        iov=0x7fcce0004040, count=1, myframe=0x7fcce00023a0,
        fn=0x7fccf12403d0 <__glusterd_friend_add_cbk>) at glusterd-rpc-ops.c:223
    ---Type <return> to continue, or q <return> to quit---
        at rpc-transport.c:538
    
    Thread 7 (Thread 0x7fccedc8b700 (LWP 11958)):
    
    Thread 6 (Thread 0x7fccf1d67700 (LWP 11877)):
        brickinfo=brickinfo@entry=0xc14ef0) at glusterd-utils.c:5834
        at glusterd-utils.c:6251
    
    Thread 5 (Thread 0x7fccf2568700 (LWP 11876)):
    
    Thread 4 (Thread 0x7fccf2d69700 (LWP 11875)):
    
    Thread 3 (Thread 0x7fccf356a700 (LWP 11874)):
    
    Thread 2 (Thread 0x7fccf3d6b700 (LWP 11873)):
    ---Type <return> to continue, or q <return> to quit---
    
    Thread 1 (Thread 0x7fccf68a8780 (LWP 11872)):
    
    Fix:
    
    The solution is to ensure we don't restart bricks if only_connect is
    true and just ensure that the brick is attempted to be connected.
    
    Test:
    
    Simulated a code change to ensure gf_is_service_running () always return
    to true to hit the scenario.
    
    Change-Id: Iec184e6c9e8aabef931d310f931f4d7a580f0f48
    Fixes: bz#1620544
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 2b0ae216ba7b27f490ccf5f6af978707e6f39d05
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:19:55 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-utils.c : re-scope message variable
    
    The the error message variable changed in scope - defined in a smaller scope.
    
    Compile-tested only!
    
    Change-Id: I16dda11c30099b0e448b8e44a300f153727ce8da
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit da22e8b1ce657280babbe077b53313058822085c
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:20:32 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-volume-ops.c : reduce size of message variable
    
    Size of error message variable reduced from 2048 bytes to 64 bytes or
    128 bytes.
    
    Compile-tested only!
    
    Change-Id: I393ba03969a6e71ccb0ce382d0e0546192897312
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit bc97ae8d9065d9fa7bbcad43e7eef5cc01761bc1
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:19:32 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-snapshot-utils.c : declare err_str as const char
    
    declare err_str as const char and intialize it at the time of declaration.
    
    Compile-tested only!
    
    Change-Id: If07e1130e819ce042905a2d0be650cd7afc2b558
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit df03b2facb4b894834b7865c31cf484768561877
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:18:46 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-replace-brick.c : reduce size of message variable
    
    Size of error message variable reduced from 2048 bytes to 256 bytes.
    
    Compile-tested only!
    
    Change-Id: Ifc0f6af2256bcbec77102767ba651d5d55f8c906
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit cbee5397881ae9eff8fec5bf514233587919f68e
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:20:19 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-volgen.c : reduce size of message variable
    
    Size of error message variable reduced from 4096 bytes to 128 bytes.
    
    Compile-tested only!
    
    Change-Id: I08c87502be791e68ab767ed96657ac89ee77fae0
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit cd95c072f4bc13c5c920aae359e8e9b84725ea2c
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 23:34:52 2018 +0300

    rpc/rpc-lib/src/rpc-clnt-ping.c:move to GF_MALLOC() instead of GF_CALLOC() when
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    Change-Id: Ifb30412ddf1bfa509f52e0454454929b266e5658
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 4d3be307293b63c74398dfa715e9920cf356f083
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Aug 21 22:16:07 2018 -0700

    mgmt/glusterd: Fix memory leaks in glusterd-handler.c
    
    Addresses the following CIDs:
    
    1370941: Unconditional memory leak in glusterd_print_snapinfo_by_vol()
    1370943: Memory leak when opendir fails for output directory in
    glusterd_get_state()
    
    Change-Id: I9536841629e1ffe1fed79a8e57d266a0e953e5af
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 5ab6e2ce11cad6034f4209ffc63c110951fd647a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 23:31:47 2018 +0300

    cli/src/cli-cmd-parser.c:move to GF_MALLOC() instead of GF_CALLOC() when
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    Change-Id: I01c67fd535ea4a2b8fa7cb4d89bff52642dc009a
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit dad85784e74493158a186536d6c13183c83fc658
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 21 20:57:52 2018 +0530

    storage/posix: Increment trusted.pgfid in posix_mknod
    
    The value of trusted.pgfid.xx was always set to 1
    in posix_mknod. This is incorrect if posix_mknod
    calls posix_create_link_if_gfid_exists.
    
    Change-Id: Ibe87ca6f155846b9a7c7abbfb1eb8b6a99a5eb68
    fixes: bz#1619720
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 9ec821f9e67848b3527f6b7dc776cb9ba440610b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Aug 16 17:28:54 2018 +0530

    afr: common thin-arbiter functions
    
    ...that can be used by client and self-heal daemon, namely:
    
    afr_ta_post_op_lock()
    afr_ta_post_op_unlock()
    
    Note: These are not yet consumed. They will be used in the write txn
    changes patch which will introduce 2 domain locking.
    
    updates: bz#1579788
    Change-Id: I636d50f8fde00736665060e8f9ee4510d5f38795
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 94cac2562ff32104d2cd6325396e55cae16ec743
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:19:03 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-rpc-ops.c : re-scope message variable
    
    The error and/or message variable was changed in scope:
    defined in a smaller scope.
    
    Compile-tested only!
    
    Change-Id: I5e46a1992ad35a996aa8ee58da28606ac018ab8e
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit bc61ee44a3f8a9bf0490605f62ec27fcd6a5b8d0
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Aug 22 02:05:59 2018 -0400

    glusterfind: Fix problems in python2 -> python3 compat
    
    1. Import configparser module correctly
    2. Fix issues with urllib usage
    
    Updates: #411
    Change-Id: I060af29f1ebac3a5e2aeeee2720b7372d4c31697
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 2ccade56483a5e511b8f8089c7f3b27080484b76
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:18:15 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-handshake.c : reduce size or re-scope message variable
    
    The the error and/or message variable was either:
    - Reduced in size - from 2048 bytes to 64 bytes, for example.
    or
    - Changed in scope - defined in a smaller scope.
    
    Compile-tested only!
    
    Change-Id: I9c609415667844ee034b7eb2b67bdbc19d38819d
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 8171d9d5a2a8129eaa984d8ed5a9397767bea463
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:18:00 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-handler.c : reduce size or re-scope message variable
    
    The the error and/or message variable was either:
    - Reduced in size - from 2048 bytes to 64 bytes, for example.
    or
    - Changed in scope - defined in a smaller scope.
    
    Compile-tested only!
    
    Change-Id: Iebb92a56d9d0ca53c80d75866bcb7848e08cf6b2
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 14b4c22f2f49d6816b247d59cc75d8ddbe842b49
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:17:42 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-geo-rep.c : reduce size of message variable
    
    Size of error message variable reduced from 2048 bytes to 64 bytes.
    
    Compile-tested only!
    
    Change-Id: I65abd9c4f23a64ac9cda5373aff4119458addbc8
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit b18221b582faca8e5ef1229bffe3b5ca17e4be11
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:17:21 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-brick-ops.c : reduce size or re-scope message variable
    
    The the error and/or message variable was either:
    - Reduced in size - from 2048 bytes to 64 bytes, for example.
    or
    - Changed in scope - defined in a smaller scope.
    
    Compile-tested only!
    
    Change-Id: Ib74e5f8f4c2978f670d4708e9382e97edf5df0a7
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 6dbf510f3c764d17c5b3967de05fdfb33c9dca93
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:17:01 2018 +0300

    xlators/mgmt/glusterd/src/glusterd-bitrot.c : reduce size of message variable
    
    Size of error message variable reduced from 2048 bytes to 256 bytes.
    
    Compile-tested only!
    
    Change-Id: Ib536451d9b562f932132b99c4eff21fc4f2775bc
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 33e7137a483a5abea8295b4d604edc6989241c12
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Aug 21 15:07:16 2018 -0700

    features/changelog: Fix a file handle leak in htime_create()
    
    In a few error scenarios, ht_file_hd was not being cleaned up.
    Addresses CID: 1325549
    
    Change-Id: If9b4388aa700303c1eebbf1410dc35d18c4637df
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit a777df08ec8100a8d9067faf14b1058f09cf862a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Aug 3 15:23:45 2018 +0530

    snapview/server: Set uid,gid,and groups for gfapi call
    
    Before calling gfapi from snapd, we need to set uid, gid
    and groups in the context. This is required to do the
    validation from posix acl xlator.
    
    Change-Id: I181bea2570a69554ff363bf5a52478ff0363ea47
    fixes: bz#1614168
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 9d2083f2ce37e1f04f5df6040ab493ab98a6f6aa
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Aug 21 22:43:22 2018 -0700

    mgmt/glusterd: Fix resource leaks in glusterd-handshake.c
    
    Addresses the following CIDs:
    
    1124768: fd leak in __server_getspec() if spec_fd happens to be 0
    1202400: Memory leak in get_snap_volname_and_volinfo()
    1214622: Memory leak in glusterd_create_missed_snap()
    1214623: Memory leak in an error path of __server_get_volume_info()
    
    Change-Id: I33910b4125d25205e76e0d13cf0256d47bd8fc3c
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 70181c8b4215e34dfff35fc4918d0e9b5256f32d
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Aug 21 14:51:11 2018 -0700

    features/leases: Initialize op_errno in leases_open()
    
    Addresses CID: 1356483 by getting rid of an unessential assignment for
    op_errno
    
    Change-Id: I2327ac17b2875b4dd5f79b76be59e2c8e570b031
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 101723cc466a069e5e19b31378305255522f7e84
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Aug 21 23:33:58 2018 -0700

    mgmt/glusterd: Fix memory leaks in glusterd-op-sm.c
    
    Addresses the following CIDs:
    
    - 1124704: Removed an unessential variable that caused a memory
    leak in glusterd_op_set_volume(). Nuked an unnecessary log message upon
    error as well since failure logging is being done in the caller
    
    - 1124772: Memory leak in an error path of
    glusterd_op_ac_send_brick_op()
    
    - 1175021: Removed an unessential variable that caused a memory leak in
    glusterd_op_build_payload()
    
    Also addressed a memory leak in an error path of
    glusterd_dict_set_volid()
    
    Change-Id: I060effbbcebe9d58b91f606175080ede517ba239
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 8096542c1cd3250593a0aa4c2dd32aa409f21723
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Sat Aug 18 22:46:12 2018 +0530

    crypt: fix coverity issues
    
    Fixes CID: 130760 130759
    
    Change-Id: I40efebd712a3bd769cb1fbc54409f1b0b35eb7b4
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit ab27d4288997acc1b6c6bdd55a3387644eea6ecd
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Aug 22 02:08:40 2018 +0530

    snapshot : fix snapshot status failure due to symlink problem
    
    Problems : 1. Snapshot status for individual snapshots were failing after OS
                  upgrade from RHEL6 to RHEL7.
               2. Post upgrade snapshot creation of cloned volume was failing.
    
    Root Cause :  When OS upgrade is from RHEL6 to RHEL7 there is difference in
                  symlink (/var/run)  between these two versions.
                  Basically when (/var/run) is symlinked to /run, mount command
                  resolves path and mounts it. But at the same time call to
                  those functions fails who depends on absolute path.
                  (like strcmp in glusterd_get_mnt_entry_info)
    
    Solution : Resolve the input path to absolute path before calling these
               functions.
    
    Test : Tested on same setup where issue was reported. After this
           patch snapshot issues are completely resolved.
    
    Change-Id: I5ba57998cea614c6072709f52f42a57562018844
    fixes: bz#1619843
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit faf736cb3043ade5b2ad3267c45d2ba0bce53b52
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Aug 21 21:53:35 2018 -0400

    coverity: Multiple coverity fixes for issues with HIGH severity
    
    glfs-fops.c
    1391414 Uninitialized pointer read
    List head needed initialization
    
    glusterfsd-mgmt.c
    graph.c
    1382431 Buffer not null terminated
    1382417 Dereference before null check
    1382347 Buffer not null terminated
    Cleaned usage of volfile_checksum member of gf_volfile_t struct
    across the code base.
    
    glusterd-tier.c
    1382426 Resource leak
    1370955 Dereference before null check
    The function fixed needs more work, but with tier almost being
    deprecated, addressed some parts of the reported coverity issues
    as appropriate.
    
    Tested using the following test cases:
    ./tests/basic/tier/new-tier-cmds.t
    ./tests/basic/tier/tier.t
    ./tests/basic/tier/bug-1214222-directories_missing_after_attach_tier.t
    ./tests/basic/tier/tier_lookup_heal.t
    ./tests/basic/tier/tier-heald.t
    ./tests/basic/tier/tier-snapshot.t
    ./tests/features/glfs-lease.t
    
    Change-Id: I396f1c34bb112bb22d2745ed279e1a4850cac4af
    Updates: bz#789278
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 37cb48e5919a2eac2525245ce7a8185e17f514f2
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:40:57 2018 +0300

    libglusterfs/src/common-utils.c:  Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I579f5b405bf410aac5ab0452231124d354f94ed1

commit a2112bd6fa2e4851cd982a691165f76f0c90d977
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 29 23:40:53 2018 +0530

    xlators/playground: fix the template files with latest requirements
    
    * Make use of xlator_api
    * Make use of gf_msg()
    * Make use of mem-pool
    * Add a sample metrics dump function
    * Provide an dummy option, which can be initialized, and reconfigured
    * Add a test case to make sure template xlator is built and used
      with default fops
    * Make a change in rpc-coverage to run without lock tests.
    
    Updates: bz#1193929
    Change-Id: I377dd67b656f440f9bc7c0098e21c0c1934e9096
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit bfba1d3602b20895956767c668e86390f16cb782
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:40:29 2018 +0300

    libglusterfs/src/graph.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Icd990423a5e6048e76922668aab67422f4bc1867

commit 443aa8e582f0dd5c4df916c0240eee3c0b56fe3f
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jul 31 20:49:52 2018 +0300

    dict.c: align dictionary structures
    
    Change-Id: Ib7250b3ff11a7ab98b578c0663dc1817624b8df1
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 183aca0e20a2cf2923a2f56352ffa2cefb49afcc
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 23:32:39 2018 +0300

    libglusterfs/src/quota-common-utils.c:move to GF_MALLOC() instead of GF_CALLOC() when
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    Change-Id: Ie2a634d768904636160582189a5f0390668b37bb
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 12510ece4f45a54452224c048abdce4af97b68cb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:40:17 2018 +0300

    libglusterfs/src/rbthash.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Ied400a500e36373d725f9480c5ebbe0a851f7c40

commit 7674ea878e934a072c5f40eafc78f7886b24808c
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:40:44 2018 +0300

    libglusterfs/src/dict.c:  Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: Iea9098b9ec0a82a866fbc5836514b1b317daefa1

commit 54e5fae2bbea0086c7dd7951bb8776c3672fedf4
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 21:41:10 2018 +0300

    libglusterfs/src/client_t.c: Move to GF_MALLOC() instead of GF_CALLOC() when possible
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    In some cases, also changed allocation size to be sizeof some
    struct or type instead of a pointer - easier to read.
    In some cases, removed redundant strlen() calls by saving the result
    into a variable.
    
    1. Only done for the straightforward cases. There's room for improvement.
    2. Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I58d2604ef684f94ea782fdbb1b1462fc7be53a9e

commit ec8174353af31def3d715b1a5a38207d92b3c6fa
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Aug 21 23:30:03 2018 +0300

    api/src/glfs.c: move to GF_MALLOC() instead of GF_CALLOC()
    
    It doesn't make sense to calloc (allocate and clear) memory
    when the code right away fills that memory with data.
    It may be optimized by the compiler, or have a microscopic
    performance improvement.
    
    Please review carefully, especially for string allocation, with the
    terminating NULL string.
    
    Only compile-tested!
    
    Change-Id: Ieeb86ff5d99176250f57c0a28c215c709b83fc80
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 0ebaa9c66347a78c3dce649e833143832114343a
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Sun Aug 19 01:38:53 2018 +0530

    protocol: coverity fixes
    
    Fixes CID: 1389388 1389320 1274113 1388881 1388623 1124801 1124795
    
    Change-Id: Ia72abc0560c959b0298f42e25abdfc5523755569
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit 0f86ed9f8be0666bb49252daa24b2db6aa174199
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Aug 20 15:28:16 2018 +0200

    Fix physical memory detection on NetBSD
    
    NetBSD has two sysctl for physical memory detection: hw.physmem and
    hw.physmem64. Only the later is 64-bit proof, and it has been
    available for years.
    
    That fix is important because it cause recent glusterfs to refuse
    mounting fileystems when there is too much RAM, with an error loading
    the quick-read xlator
    [quick-read.c:838:check_cache_size_ok] 0-gfs-quick-read:
      Cache size 134217728 is greater than the max size of 0
    
    Change-Id: I957a1ff1d7018fe2f9d47384a28708e6cbdf710a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Fixes: bz#1619475

commit fcd0c24abfccfe8d1faf64269a113596577355a8
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Aug 9 11:14:11 2018 +0530

    cluster/dht: coverity fixes
    
    Fixes 1133997, 1370910, 1382387, 1382444,
    1394635
    
    Change-Id: Ie63ad47abd5519b9b9536da26b61ed4c9eaf2c75
    updates: bz#789278
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 2ea2d68776e21f4bfa8d13fc79b7a7ef0818ad0b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 20 14:10:52 2018 -0700

    features/sdfs: Minor improvements
    
    Addresses:
    
    CID 1389688: Prevent op_errno from being -ve in sdfs_rename()
    CID 1389286: Check for retval from loc_copy() to avoid logically dead
    code
    
    and
    
    Initializes op_errno to ENOMEM in sdfs_link()
    
    Change-Id: I12e17a98faa5887da94a33ba9ca775e8e0fef359
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 0eac8026f880bf8bf7e05530de16a06ba3e8a40c
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Aug 20 16:38:41 2018 +0530

    Revert "performance/write-behind: better invalidation in readdirp"
    
    This reverts commit 4d3c62e71f3250f10aa0344085a5ec2d45458d5c.
    
    Traversing all children of a directory in wb_readdirp caused
    significant performance regression. Hence reverting this patch
    
    Change-Id: I6c3b6cee2dd2aca41d49fe55ecdc6262e7cc5f34
    updates: bz#1512691
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit cb210f83455e2f659e734dfa09ff7602b5b75201
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Aug 15 19:34:31 2018 +0530

    glusterd: fix gcc warnings
    
    ...and also changed char array initialization to from {0,} to "".
    
    gcc version 8.1.1 20180712 (Red Hat 8.1.1-5) (GCC) on Fedora 28.
    
    Sample warnings:
    glusterd-utils.c:7234:41: warning: ‘.hostname’ directive output may be truncated writing 9 bytes into a region of size between 1 and 1024 [-Wformat-truncation=]
             snprintf (key, sizeof (key), "%s.hostname", base_key);
                                             ^~~~~~~~~
    glusterd-utils.c:7234:9: note: ‘snprintf’ output between 10 and 1033 bytes into a destination of size 1024
             snprintf (key, sizeof (key), "%s.hostname", base_key);
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    glusterd-snapshot.c:3090:65: warning: ‘/’ directive output may be truncated writing 1 byte into a region of size between 0 and 4095 [-Wformat-truncation=]
                     snprintf (snap_path, sizeof (snap_path) - 1, "%s/%s",
                                                                     ^
    glusterd-snapshot.c:3090:17: note: ‘snprintf’ output between 2 and 4351 bytes into a destination of size 4095
                     snprintf (snap_path, sizeof (snap_path) - 1, "%s/%s",
                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                               snap_mount_dir, snap_vol->snapshot->snapname);
                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    glusterd-statedump.c:28:45: warning: ‘%s’ directive output may be truncated writing up to 4095 bytes into a region of size 144 [-Wformat-truncation=]
             snprintf (subkey, sizeof (subkey), "%s%d", key, index);
                                                 ^~     ~~~
    glusterd-statedump.c:28:9: note: ‘snprintf’ output between 2 and 4107 bytes into a destination of size 144
             snprintf (subkey, sizeof (subkey), "%s%d", key, index);
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    updates: bz#1193929
    Change-Id: Ic721f27b28d1221c124b570e81c55528f5b7f3cd
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 6fa531c57c633827283fba6a3cdaa1c68976ccb7
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Tue Aug 7 15:28:13 2018 +0530

    xlators: protocol: Fix deferencing pointer after free coverity issues
    
    The pointer of type struct iobuf * is getting dereferenced after
    getting freed by iobuf_unref function. Therefore, move this function
    after all the dereferences of this pointer type.
    Also, it is useful coding standard to have iobuf_unref just after
    iobref_add. So, move iobref_add too.
    
    Occurences found using Coccinelle script:
    @@
    identifier rsphdr_iobuf;
    expression E;
    identifier func;
    @@
    *iobuf_unref(rsphdr_iobuf);
    ...
    *E = func(rsphdr_iobuf);
    
    Fixes CID: 1390517, 1390278, 1388666, 1356588, 1356587 at [1].
    and also some more occurences which were found using the above script but not
    caught by Coverity.
    [1]. https://scan6.coverity.com/reports.htm#v42388/p10714/fileInstanceId=84384920&defectInstanceId=25600709&mergedDefectId=1388666
    
    Change-Id: I579e9d12698f14e9e24bc926c6efef16bac5c06c
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit 2348b8ae6ce02f83069d01478a31bb2498cc6183
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 16 14:15:27 2018 +0300

    glusterfsd/src/glusterfsd.c : reduce size or re-scope message variable
    
    The the error and/or message variable was either:
    - Reduced in size - from 2048 bytes to 64 bytes, for example.
    or
    - Changed in scope - defined in a smaller scope.
    
    Compile-tested only!
    
    Change-Id: I20b9fb3407a74ba96fcbc7f05fcab534ff562c09
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit f2fbe364ee166416d484cd75ffa7f181f131a446
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Aug 20 14:06:51 2018 +0530

    jbr : fix coverity issue in jbr.c
    
    This fixes CID 1395069.
    
    Change-Id: I0d2fa8fb04adf035c358841f43dea64f6aa8a1d8
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit da7c26ff1bb879c6a9489c1dc42c7a3400c9be20
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Fri Jul 27 14:52:21 2018 +0800

    gfapi: Use inode_forget in case of unlink/rename objects
    
    After unlink/rename, the nonexistent inode should be remove from inode table,
    that's better than put to lru list.
    
    Change-Id: I5a40df188f3f42a2c864cfb4404b22b288fdcc12
    fixes: bz#1612750
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 690ca8207269919e89341a9a49a3cff0e56e344b
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Aug 20 16:01:47 2018 -0400

    cli: Fix invalid access of option_str variable
    
    In function cli_cmd_volume_statedump_options_parse if
    the wordcount of arguments is exactly 3, then option_str
    would remain NULL, and hence the function will generate
    a segmentation fault on the strstr check in its body.
    
    This can be triggered when we run the command,
    `gluster volume statedump <volname>`
    
    The fix is to check if option_str is non-NULL before use
    and also to pass in a duplicated empty string to the dict
    key "options" when this is NULL.
    
    Fixes: bz#1619423
    Change-Id: Ic029ab60b64890d92c7a0876a638929495d3aa59
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit a0fb796c233f30cbbde56768f7073e954e02dfcb
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Jul 31 19:03:05 2018 +0530

    geo-rep : fix few coverity issues in procdiggy.c
    
    This patch fixes BAD_FREE at line number 75,105 and
    UNUSED_VALUE at line number 108.
    
    CID : 1274068
    scan detail at [1].
    [1] https://scan6.coverity.com/reports.htm#v42401/p10714/fileInstanceId=84384726&defectInstanceId=25600457&mergedDefectId=727233
    
    Change-Id: I8dff42546204bf78c178c9dcaba534888c5354e9
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit a3a3b8ec67fa1609e06b1d919675e3df74d531e5
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Mon Aug 20 15:40:06 2018 +0530

    write-behind: coverity fixes
    
    Fixes CID: 1124360 1291740 1370918
    
    Change-Id: I008c7ade8f9809d040f42f6d3e9af70fff2f3dc6
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit bb7d3fbfe14c81c5bd4c0132ce4e300b887f8e76
Author: karthik-us <ksubrahm@redhat.com>
Date:   Fri Aug 3 16:37:00 2018 +0530

    cluster/afr: Fix bug-1586020-mark-dirty-for-entry-txn-on-quorum-failure.t
    
    Problem:
    In line #13 of the test case, it checks whether the file is present
    on first 2 bricks or not. If it is not present on even one of the bricks
    it will break the loop and checks for the dirty marking on the parent
    on the 3rd brick and checks for file not present on the 1st and 2nd
    bricks. The below scenario can happen in this case:
    - File gets created on 1st and 3rd bricks
    - In line #13 it sees file is not present on both 1st & 2nd bricks and
      breaks the loop
    - In line #51 test fails because the file will be present on the 1st brick
    - In line #53 test will fail because the file creation was not failed on
      quorum bricks and dirty marking will not be there on the parent on 3rd
      brick
    
    Fix:
    Don't break from the loop if file is present on either brick 1 or brick 2.
    
    Change-Id: I918068165e4b9124c1de86cfb373801b5b432bd9
    fixes: bz#1612054
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 13c508525786df225251b43da5d567e812dd57eb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Tue Jul 31 07:22:49 2018 +0300

    dict.c: ensure hash is done in the right place.
    
    The hash should be done outside of locks, whenever is possible.
    
    
    Change-Id: I4f8f7455702e0489a57105cf79668c7fca90e1c0
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 73c1d19584c30c4635fc8fa15bfd51cedddab5e0
Author: Shwetha Acharya <shwetha174@gmail.com>
Date:   Fri Aug 3 15:12:45 2018 +0530

    marker: FORWARD_NULL coverity fix
    
    Problem:
    Coverity false positive.
    
    Solution:
    Added a comment to ignore the false positive.
    
    CID: 1325591
    
    BUG: 789278
    Change-Id: I95037efd12c059efcfc04f3c4c13f60c530150b4
    Signed-off-by: Shwetha Acharya <shwetha174@gmail.com>

commit 22a5ecf6906a24883b953c5b4ae37bc30be40dba
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Sat Aug 18 23:36:00 2018 +0530

    quota: coverity fixes
    
    Fixes CID: 1325638 1288766 1124357
    
    Change-Id: I425f857d0d549da2dfaa6a6e6b8440cb14c21121
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit e37ee6d509aa98587d55f9ea73bc831c10761eaa
Author: karthik-us <ksubrahm@redhat.com>
Date:   Fri Aug 3 15:55:18 2018 +0530

    posix: Delete the entry if gfid link creation fails
    
    Problem:
    If the gfid link file inside .glusterfs is not present for a file,
    the operations which are dependent on the gfid will fail,
    complaining the link file does not exists inside .glusterfs.
    
    Fix:
    If the link file creation fails, fail the entry creation operation
    and delete the original file.
    
    Change-Id: Id767511de2da46b1f45aea45cb68b98d965ac96d
    fixes: bz#1612037
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 788cda4cd36574092bef1449ecda579163d06776
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Sat Aug 18 00:06:58 2018 +0530

    glusterd: fix some coverity issues
    
    Fixes CID: 1241481 1241482 1274079 1274118 1274121  1274131 1274198
    1274214 1274220 1274224 1394663 1394641 382454 1382453 1382449 1288095
    
    Link: https://scan6.coverity.com/reports.htm#v42388/p10714/fileInstanceId=84772667&defectInstanceId=25770661&mergedDefectId=744716
    
    Change-Id: Idaf434186231c8b0fff4b27c57fa23636a89c8a7
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit 21199aaeb272da4b7857351bb2aa51f36c7e22cd
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sun Aug 19 13:53:15 2018 -0400

    geo-rep: Cleanup unwanted code
    
    Cleanup the Active/Passive logging code
    which is redundant. With new status infra
    implmented, this is redundant as every
    status switch is logged by status infra.
    
    fixes: bz#1619027
    Change-Id: I0a6644cb998f3520e62a5189f21e4d66acc0e7c5
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 9d426f3522422e7499f747801b1894164a4b1589
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Wed Aug 8 22:28:39 2018 +0300

    libglusterfs/src/common-utils.c: strncpy -> sprintf, remove dead code.
    
    strncpy may not be very efficient for sort strings copied into
    a large buffer: If the length of src is less than n,
    strncpy() writes additional null bytes to dest to ensure
    that a total of n bytes are written.
    
    Instead, do a quick calc to see how much we really need and use
    snprintf() to copy as much.
    
    Also, move from CALLOC to MALLOC, as we are writing to this newly
    allocated memory right away and add terminating null.
    
    Lastly, removed some dead code. I did the same optimization as above
    to it, only to find out no one is using it.
    
    Compile-tested only!
    
    Change-Id: Ib91b9a73c3d74c511fd067446b1bf6c2e1802687
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit d7f97cef9099e8904d296df5cc9a221d295cfb35
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Aug 4 16:24:18 2018 +0300

    libguestfs/src/mem-pool.h: switch from calloc() to malloc()
    
    If we are going to overwrite that allocated memory, why bother zero'ing it?
    
    Only compile-tested!
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I9c9d2d8d5ab3e706c747feb1920ecd417807f7fd

commit e924d76b125d50447535681e4525485379d45eeb
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Aug 16 08:16:54 2018 +0530

    gnfs: fix gcc warnings
    
    gcc version 8.1.1 20180712 (Red Hat 8.1.1-5) (GCC) on Fedora 28.
    
    Sample warnings:
    1)
    nfs3.c:292:54: warning: ‘%s’ directive output may be truncated writing up to 255 bytes into a region of size between 143 and 250 [-Wformat-truncation=]
                             snprintf (buf, sizeof (buf), "(%s) %s : %s",    \
                                                          ^~~~~~~~~~~~~~
    nfs3.c:295:35:
                                       gfid);                                \
                                       ~~~~
    2)
    nlm4.c:145:54: warning: ‘%s’ directive output may be truncated writing up to 255 bytes into a region of size between 143 and 250 [-Wformat-truncation=]
                             snprintf (buf, sizeof (buf), "(%s) %s : %s",    \
                                                          ^~~~~~~~~~~~~~
    nlm4.c:148:35:
                                       gfid);                                \
                                       ~~~~
    acl3.c:128:54: warning: ‘%s’ directive output may be truncated writing up to 255 bytes into a region of size between 143 and 250 [-Wformat-truncation=]
                             snprintf (buf, sizeof (buf), "(%s) %s : %s",    \
                                                          ^~~~~~~~~~~~~~
    acl3.c:131:35:
                                       gfid);                                \
                                       ~~~~
    
    updates: bz#1193929
    Change-Id: I760b8176e48f1f4628a1a98afa54a7994bdf13e9
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 4814140a539f4685bf439b456381751ee84be8fa
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Aug 16 17:04:22 2018 +0530

    snapshot/handshake: store description after strdup
    
    problem:
    During a handshake, when we import a friend data
    snap description variable was just referenced to
    dictionary value.
    
    Solution:
    snap description should have a separate memory allocated
    through gf_strdup
    
    Change-Id: I94da0c57919e1228919231d1563a001362b100b8
    fixes: bz#1618004
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 8549ba1a3de8bba7c80ea24121fb095cd756c64e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Sat Aug 18 19:40:46 2018 +0530

    snapshot:Fix wrong dictionary key in snapshot cleanup code
    
    Snapshot was designed to support multiple volume snapshot,
    hence the volume name keys are labelled with volume count.
    So the volume key should have a volume count appended with
    key
    
    Change-Id: I044d73fc86db0e662dc914669aecfb82a6476fb5
    fixes: bz#1618004
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit e7afbfb1cf65da96f3b57427b1bb61b2ebde5bba
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 13 15:52:51 2018 -0700

    mgmt/glusterd: Code cleanup in glusterd-volgen.c
    
    This patch does the following:
    
    1. Addresses CID: 1124815,124816,1124833,1291724,1325535,1325536,1357858
      - by adding some null checks
      - by handling return values from functions
      - by using an appropriate buffer length in strncpy
    
    2. Cleans up some commented code
    
    Change-Id: I5a7079f34e3e460d5a6267734c3bc84bf4ad72f5
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 5ad8b6779db0ffacf876e254621ee7111f7f82b0
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Sat Aug 18 01:25:34 2018 +0530

    snapshot:Fail snapshot creation if an empty description provided
    
    Snapshot description should have a valid string. Creating a
    snapshot with null value will cause reading from info file
    to fail with a null exception
    
    Change-Id: I9f84154b8e3e7ffefa5438807b3bb9b4e0d964ca
    updates: bz#1618004
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit fab6944206bf44e2260f20a9d5f1e785f933e705
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Aug 18 11:39:03 2018 +0530

    coverity: libglusterfs issues
    
    CID: 1391415, 1274122, 1274201, 1382408, 1382437, 1389436
         1288798, 1288106, 1288110
    
    updates: bz#789278
    Change-Id: I48c7a50f22f5f4580310040c66463d9f7dd26204
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 23e2a420f90c4d39386a0c0c2a8bea0e376ab070
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Jul 30 20:43:24 2018 +0300

    dict.c: copy-pasta fix (dict -> data)
    
    Change-Id: Ifda14a1cc01e0fa99ff20d710eccb43296e22955
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c9bde3021202f1d5c5a2d19ac05a510fc1f788ac
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 17 16:40:04 2017 +0530

    performance/readdir-ahead: keep stats of cached dentries in sync with modifications
    
    PROBLEM:
    
    Stats of dentries that are readdirp'd ahead can become stale due to
    fops like writes, truncate etc that modify the file pointed by
    dentries. When a readdir is finally wound at offset corresponding to
    these entries, the iatts that are returned to the application come
    from readdir-ahead's cache, which are stale by now. This problem gets
    further aggravated when caching translators/modules cache and continue
    to serve this stale information.
    
    FIX:
    
    * Store the iatt in context of the inode pointed by dentry.
    * Whenever the inode pointed by dentry undergoes modification, in cbk
      of modification fop, update the iatt stored in inode-ctx to reflect
      the modification.
    * When serving a readdirp response from application, update iatts of
      dentries with the iatts stored in the context of inodes pointed by
      these dentries.
    * Some fops don't have valid iatts in their responses. For eg., write
      response whose data is still cached in write-behind will have zeroed
      out stat. In this case keep only ia_type and ia_gfid and reset rest
      of the iatt members to zero.
      - fuse-bridge in this case just sends "entry" information back to
        kernel and attr is not sent.
      - gfapi sets entry->inode to NULL and zeroes out the entire stat
    * There is one tiny race between the entry creation and a readdirp on
      its parent dir, which could cause the inode-ctx setting and inode
      ctx reading to happen on two different inode objects. To prevent
      this, when entry->inode doesn't eqaul to linked_inode,
      - fuse-bridge is made to send only "entry" information without
        attributes
      - gfapi sets entry->inode to NULL and zeroes out the entire stat.
    
    Change-Id: Ia27ff49a61922e88c73a1547ad8aacc9968a69df
    BUG: 1390050
    Updates: bz#1390050
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 045d70a5450daa85aa5564b6e9f93065c342ab12
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Aug 14 15:36:00 2018 -0700

    debug/error-gen: Fix null deref and out of bounds read issues
    
    Addresses CID: 1124492, 1124700, 1124701
    
    Change-Id: If9916df1b0a4e67ad74fe0f6ea6f2544598ddacb
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 41e768f65bf63c9da22f7125e1eeb77d9c775352
Author: Bhumika Goyal <bgoyal@redhat.com>
Date:   Thu Aug 16 21:32:21 2018 +0530

    block xlator: fix some coverity issues
    
    Fixes CID: 1128916, 1128917, 1128919, 1192875
    
    Change-Id: I5276b7db4a9650e70c335e25b9b4609a887233c0
    updates: bz#789278
    Signed-off-by: Bhumika Goyal <bgoyal@redhat.com>

commit d975305ab1c764582bf63bc6f526a2739e2b34eb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Aug 14 11:49:50 2018 +0530

    tests: Add thin-arbiter.rc for writing tests for thin-arbiter
    
    fixes bz#1615789
    Change-Id: I1f42e78fec5ddaf2a425dc4b82c9a20472aa146d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit dc25d2c1eeace91669052e3cecc083896e7329b2
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 13 00:15:59 2018 -0700

    features/changelog: close htime_fd in fini()
    
    Addresses CID: 1325549
    
    Change-Id: Ib041c7c288db6810b2e13a05a19ee894a47c9b05
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 522352d4b123d66f7d0b57c287ed7367deba0f31
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 13 12:20:07 2018 -0700

    features/changelog: Fix missing unlocks
    
    Addresses CID 1210981
    
    Change-Id: Icd325588ae0639e09d924fdde171931dedd06ca6
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 0058f6df0d2bd1dedc453585e6c4076df7b51fde
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Jul 19 08:37:15 2018 -0400

    doc: Add details around xlator categories
    
    Updates: bz#1193929
    Change-Id: I6446bbdd8025f333a3e855032c0c7709bf4ae4cd
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 8f437f6c06587c3465764d1ec4b7f81d60a94eae
Author: Shwetha Acharya <shwetha174@gmail.com>
Date:   Mon Jul 30 10:15:34 2018 +0530

    locks: FORWARD_NULL coverity fix
    
    Problem:
    "dst" could be NULL.
    
    Solution:
    Added a condition check to avoid NULL pointer dereferencing.
    
    BUG: 789278
    
    Change-Id: I13ccf3234eda50a197f5fdfaf35b247589302582
    Signed-off-by: Shwetha Acharya <shwetha174@gmail.com>

commit bae16c498599d4bf1dddca03bf56fa53c73d251a
Author: Shwetha Acharya <shwetha174@gmail.com>
Date:   Sat Jul 28 18:54:47 2018 +0530

    posix: FORWARD_NULL coverity fix
    
    Problem:
    filler could be null.
    
    Solution:
    Modified the condition check to avoid NULL pointer dereferencing.
    
    BUG: 789278
    Change-Id: I0c3e29ede3c226295a9860ddcb3b432832c381dd
    Signed-off-by: Shwetha Acharya <shwetha174@gmail.com>

commit 1909f2ca01efcd467164a2d7ed684cdc6e1437de
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Aug 10 02:39:55 2018 +0530

    nfs-server-mount : fix coverity issues in mount3.c
    
    Fixes CID 1389033, 1388767, 1288782.
    
    Change-Id: I244f88b2ca8487f8926da45d886982558ad45c7a
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit db16111e9f948069fc89d6653b6bd92f31808e65
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Aug 14 14:41:16 2018 +0530

    meta : fix coverity in meta-helpers.c
    
    This fixes CID 1214627 and 1257625.
    
    updates: bz#789278
    
    Change-Id: I6eb1ccf7b498948d1c41ff830e65437ef818cd55
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit d17cccd520700eea30a7ed8b49eaf26f34e37ac2
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 13 11:33:47 2018 -0700

    features/acl: Fix a possible null dereference
    
    Addresses CID 1370952
    
    Change-Id: I1f157dbede32e74e38aed8a1a162e38107f2628d
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit fa16371475a115213390cd84d38cec75032f24d4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Aug 16 10:03:22 2018 +0530

    glusterd: coverity defects fix introduced by commit 1f3bfe7
    
    Commit 1f3bfe7 stripped down the total size of certain path related variables
    in glusterd_brickinfo_t which considered couple of new coverity defects.
    
    Fix the following:
    CID : 1394969 Destination buffer too small
    CID : 1394968 Out-of-bounds access
    
    Change-Id: Ibc30eac4680cc6c83bd89d248f1435cb6a3d1b75
    updates: bz#789278
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 0f0551565874498242348fbe413017d844715814
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Aug 15 01:59:04 2018 +0530

    statedump : fix coverity issues
    
    Comparing an array to null is not useful, the test will always evaluate as true.
    
    Fixes CID 1325566 and 1389371.
    
    updates: bz#789278
    
    Change-Id: Id51f84cc62767a432de1d12851ae2669c1596a94
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit c0b5eab4c0bb95236c18ba5c7f596e44d7ec49e1
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Aug 15 02:27:53 2018 +0530

    jbr : fix coverity issues in jbr
    
    This patch fixes CID 1357875 and 1357869.
    
    Change-Id: Ief88523e5ad92a2c884ff1b85cd613992bba0dad
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 0b450b8b35cf8f03d51eeb5b0941832cde636993
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jul 31 12:33:49 2018 +0530

    glusterd: ignore importing volume which is undergoing a delete operation
    
    Problem explanation:
    
    Assuming in a 3 nodes cluster, if N1 originates a delete operation and
    while N1's commit phase completes, either glusterd service of N2 or N3
    gets disconnected from N1 (before completing the commit phase), N1 will
    attempt to end up importing the volume which is in-flight for a delete
    in other nodes as a fresh resulting into an incorrect configuration
    state.
    
    Fix:
    
    Mark a volume as stage deleted once a volume delete operation passes
    it's staging phase and reset this flag during unlock phase. Now during
    this intermediate phase if the same volume gets imported to other peers,
    it shouldn't considered to be recreated.
    
    An automated .t is quite tough to implement with the current infra.
    
    Test Case:
    
    1. Keep creating and deleting volumes in a loop on a 3 node cluster
    2. Simulate n/w failure between the peers (ifdown followed by ifup)
    3. Check if output of 'gluster v list | wc -l' is same across all 3
    nodes during 1 & 2.
    
    Change-Id: Ifdd5dc39699120258d7fdd42fe2deb9de25c6246
    Fixes: bz#1605077
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit fa2f092709a6a2d91213cb3410fc5b5109d84646
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jul 30 17:15:35 2018 +0200

    build: use standard PKG_CHECK_MODULES for libxml2 availability
    
    In case the development parts of libxml2 are not installed, it was
    required to re-run ./autogen.sh to cleanup the cached values for the
    check. This is not nice towards users. By using the standard
    PKG_CHECK_MODULES for libxml-2.0 the results of the check are not cached
    and will be probed again when running ./configure.
    
    Change-Id: I3c4586e5555a521be5d4fb61bdb873ae0317311a
    Fixes: bz#1599219
    Reported-by: Sachidananda Urs <surs@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 90b102fa0361523a706a25c85b56ee6f536f6277
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Aug 14 14:03:16 2018 +0530

    trash : fix coverity issues in trash.c
    
    This patch fixes CID : 1382380 and 1382428.
    
    Change-Id: Ice3c8f5c2d97a0b541665bff744f32fbea9e294f
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 4bc20f6d3163933e49eb95cff698266e908133e1
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Mon Aug 6 22:00:00 2018 +0530

    libglusterfs: FORWARD_NULL coverity fix
    
    Fixing FORWARD_NULL coverify errors in libglusterfs.
    
    CID: 1391407, 1391410
    
    BUG: 789278
    Change-Id: I3d20523005e4418759c8a72620edff7c977d2d00
    updates: bz#789278
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit fc233b8f6989fba02f77e0b0a5adbce1166bd7fe
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Mon Aug 6 20:49:12 2018 +0530

    cluster/ec: FORWARD_NULL coverity fix
    
    Fixing FORWARD_NULL coverify errors with EC.
    
    CID: 1394650
    
    BUG: 789278
    Change-Id: I52c99dac3483ca31a86cd7e3a959d4010b195f32
    updates: bz#789278
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit 0ef74dbd70cce5462b289f6f0cfb05082db00ff5
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Aug 10 02:20:01 2018 +0530

    uss : fix coverity issues
    
    This patch fixes coverity issuse in snapview-server.c
    
    CID : 1274119, 1325525
    
    Scan details at [1].
    
    [1]. https://scan6.coverity.com/reports.htm#v42401/p10714/fileInstanceId=84476369&defectInstanceId=25631967&mergedDefectId=778645
    
    Change-Id: I825f09eabf84a2262a079c1f920a673727c5792b
    updates: bz#789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit e35424da737e50c8ba5cfc12bb2052b2d5ad69ce
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Aug 10 14:54:56 2018 +0530

    tests: Increase timeout to 30 minutes to handle lcov slowness
    
    This script on a normal setup takes 15 minutes. With lcov it needs
    to be increased. Considering we did 1.5X of the default $run_timeout
    in run-tests.sh, I am doing the same for this script.
    
    fixes bz#1614718
    Change-Id: Ia571b33ff13deb8cbd8e48561769e876aa0b1aff
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 9297e1950f76270e99c76970f57810e01e305a3b
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Jul 30 20:16:21 2018 -0400

    contrib: Remove gf_mkostemp copied from GLibC
    
    gf_mkostemp is borrowed from GLibC a long time back,
    we now have mkostemp or mkstemp alternatives with all
    distributions and versions that we care for.
    
    As a result removing this from the contrib directory
    and modifying the one instance that is still using the
    same.
    
    This is part of code cleanup as we cleaned up coverity
    SECUR_TEMP errors.
    
    Updates: bz#1193929
    
    Change-Id: I1ad7863043cdb0845c53748f5a0522e767079130
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 82e5acd6b30aabccb0a1e157dc633591c4919a3e
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Aug 13 15:11:15 2018 -0400

    tests: Fix spurious failures in stats-dump.t test
    
    The test fails to grep and find queue_size, in a brick stats
    dump, having succesfully found aggr.* values in the same.
    
    The troubleshot is that, the writer thread in io-stats, that
    dumps this in a particular interval, truncates the file just before
    the grep attempts to read the contents, and hence the failure.
    
    The fix is to stop the dumper thread, and then wait for a couple
    of seconds and then check the output, so that the thread writer
    does not interfere with the test.
    
    Fixes: bz#1615582
    Change-Id: I29f95488a2ad693abe1dd525b1d87a9d1eee29a2
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit e765dfa0704bed07eaf003c007d9ab192cdd8aa4
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Aug 14 11:44:54 2018 -0700

    performance/md-cache: Use bitwise AND instead of logical AND
    
    Addresses CID: 1394640
    
    Change-Id: I1139222301569d17760df74624acd301594063b9
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 4fe662be4143629e405b1718836be6c990fcebbb
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sat Jul 21 12:05:30 2018 +0300

    contrib/xxhash: update to latest xxHash (0.6.5)
    
    Update to latest xxHash, which is supposed to faster with small keys.
    
    Specifically, updated to 3064d42e7d74b0921bdd1818395d9cb37bb8976a,
    which is a bit higher than 0.6.5.
    
    Compiled hopefully with namespace (XXH_NAMESPACE=GF_),
    which allows to use XXH() funcs with no fear they'll 'leak'
    from our library.
    
    Only compile tested!
    
    xxhsum is modified to display messages which was conflicting
    with regression tests (TAP harness). So modified the
    gfid2path_fuse.t and gfid2path_nfs.t to adhere to that.
    
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>
    
    Change-Id: I35cea5cc93f338c1023ac2c9bc6d7d13225a967b

commit 4d1ea415f5346b24c13810aab18a24256fb2b41a
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Aug 14 18:59:47 2018 +0530

    mountbroker : fix coverity issue in glusterd-mountbroker.c
    
    Fixes CID : 1124789
    
    updates: bz#789278
    
    Change-Id: I61c70f05e6377d7ddc8961556274714dd356a117
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 767109f5cf2ebe5cecc4e93d990c43255ffe6a12
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Aug 12 18:40:25 2018 -0700

    features/changelog: Fix a resource leak
    
    Fixes CID 1382359
    
    Change-Id: Iaafbdb9a45496091327e3dc9092e09148fa9a5c5
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 89545e745e4075845c18078be67a31dea93a4e88
Author: Mark Mielke <mark.mielke@gmail.com>
Date:   Mon Aug 13 23:54:34 2018 -0400

    Bash integration script should namespace variables
    
    In the original submitted script, it looks like there was effort
    put into namespacing all global variables. However a few mistakes
    remained.
    
    GLUSTER_TOP_SUBOPTIONSx were defined, but TOP_SUBOPTIONSx were
    referenced. This was likely an unrecognized defect in the
    original code submission? These are now corrected to refer to
    GLUSTER_TOP_SUBOPTIONSx.
    
    FINAL_LIST, LIST, and TOP were leaked into all Bash shells and
    used by the command completion functions. The most problematic
    of these was TOP, which was declared with "-i" making it an
    integer. This cause other code which used TOP to define a path
    to fail like this:
    
        $ bash
        $ TOP=/abc
        bash: /abc: syntax error: operand expected (error token is "/abc")
    
    These are now qualified as GLUSTER_FINAL_LIST, GLUSTER_LIST, and
    GLUSTER_TOP to reduce impact on scripts that might choose to use
    these extremely common variable names.
    
    Change-Id: Ic96eda8efd1f3238bbade6c6ddb69118e8d82158
    Fixes: bz#1425325
    Signed-off-by: Mark Mielke <mark.mielke@gmail.com>

commit 1f3bfe7b5d437ae3ecd202e0e224a62dbc98b133
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 20 14:27:57 2018 +0530

    glusterd: fix gcc7 warnings
    
        [sh]$ gcc --version
        gcc (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5)
    
    Warnings were of the type below:
    
    xlators/mgmt/glusterd/src/glusterd-store.c:3285:33:
    warning: ‘/options’ directive output may be truncated writing 8 bytes into a region of size between 1 and 4096 [-Wformat-truncation=]
             snprintf (path, len, "%s/options", conf->workdir);
                                     ^~~~~~~~
    xlators/mgmt/glusterd/src/glusterd-store.c:1280:39:
    warning: ‘/snaps/’ directive output may be truncated writing 7 bytes into a region of size between 1 and 4096 [-Wformat-truncation=]
             snprintf (snap_fpath, len, "%s/snaps/%s/%s", priv->workdir,
                                           ^~~~~~~
    
    * Also changed some places where there was issues with key size
    * Made sure all the 'char buf[SOMESIZE] = {0,};' are changed to 'char buf[SOMESIZE] = "";`
      - In the files I changed
    
    * Also edited coding standard to reflect that.
    
    updates: bz#1193929
    Change-Id: I04c652624ac63199cea2077e46b3a5def37c3689
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit d339f87a6fadf7bc4d680a657ddc404247e14c47
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Aug 12 18:02:17 2018 -0700

    mgmt/glusterd: Fix possible use after free in glusterd_op_ac_commit_op()
    
    Fixes CID 1391418
    
    Change-Id: I60ce6cd3b2528369f4dc1be81c0c15a1a806982a
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 2189dedb565c6e36740b0168e57337636e25ef36
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Aug 12 17:37:10 2018 -0700

    mgmt/glusterd: Fix buffer length to prevent a memory overrun
    
    Fixes CID 1394647, 1394658
    
    Change-Id: I30cf6e793919a08e0a3fe10622351b8316d7767c
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit c41592c79c612237cd10acbfa4a59b85dcce402b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Aug 10 15:49:17 2018 +0530

    glusterd: remove the unused databuf in rebalance structure
    
    While it is a one line fix, it allows a significant unwanted memory
    being allocated for defrag structure.
    
    Updates: bz#1193929
    Change-Id: Idda70d1d3dc0e7be56c35e872aa6edfaf752290d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit d46632247cbbeefb4798512e4426943f9768ecbf
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Aug 2 21:48:34 2018 +0530

    features/shard: Fix crash and test case in RENAME fop
    
    Setting the refresh flag in inode ctx in shard_rename_src_cbk()
    is applicable only when the dst file exists and is sharded and
    has a hard link > 1 at the time of rename.
    
    But this piece of code is exercised even when dst doesn't exist.
    In this case, the mount crashes because local->int_inodelk.loc.inode
    is NULL.
    
    Change-Id: Iaf85a5ee3dff8b01a76e11972f10f2bb9dcbd407
    Updates: bz#1611692
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 76fcdc2a18311ece1ba0d2a191c9d3261637d41c
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Aug 13 22:17:17 2018 +0530

    cluster/dht: Fixed rebalanced files
    
    An error caused skipped files to be counted as
    rebalanced files.
    
    Change-Id: I02333f099fb8b73ba953f41a2922021a1e4da7be
    fixes: bz#1615474
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e49c95ddfbaddb865e836a520e1d9070bbeec5e4
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Aug 6 15:02:58 2018 +0530

    cluster/dht: fix inode ref management in dht_heal_path
    
    In dht_heal_path, the inodes are created & looked up from top to down.
    
    If the path is "a/b/c", then lookup will be done on a, then b and so
    on. Here is a rough snippet of the function "dht_heal_path".
    
    <snippet>
    if (bname) {						ref_count
    	- loc.inode = create/grep inode    		  1
    	- syncop_lookup (loc.inode)
    	- linked_inode = inode_link (loc.inode)		  2
    	/*clean up current loc*/
    	- loc_wipe(&loc)				  1
    	/*set up parent and bname for next child */
    	- loc.parent = inode
    	- bname = next_child_name
    }
    out:
    	- inode_ref (linked_inode)			  2
    	- loc_wipe (&loc) 				  1
    </snippet>
    
    The problem with the above code is if _bname_ is empty ie the chain lookup is
    done, then for the next iteration we populate loc.parent anyway. Now that
    bname is empty, the loc_wipe is done in the _out_ section as well. Since, the
    loc.parent was set to the previous inode, we lose a ref unwantedly. Now a
    dht_local_wipe as part of the DHT_STACK_UNWIND takes away the last ref leading
    to inode_destroy.
    
    This problenm is observed currently with nfs-ganesha with the nameless lookup.
    Post the inode_purge, gfapi does not get the new inode to link and hence, it links
    the inode it sent in the lookup fop, which does not have any dht related context
    (layout) leading to "invalid argument error" in lookup path done parallely with tar
    operation.
    
    test done in the following way:
     - create two nfs client connected with two different nfs servers.
     - run untar on one client and run lookup continuously on the other.
     - Prior to this patch, invalid arguement was seen which is fixed with
       the current patch.
    
    Change-Id: Ifb90c178a2f3c16604068c7da8fa562b877f5c61
    fixes: bz#1610256
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit c43a52dd105f73d322124c56a901e084233f9630
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 13 00:06:05 2018 -0700

    mgmt/glusterd: Fix a memory leak in volgen
    
    Fixes CID 1325557
    
    Change-Id: I5e33ae19ddf4c44a49a2b3b3dea0c739bc96d3a7
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit b2b6ab8eff317f6a507ab23897ea6cd5c718d99a
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Thu Aug 2 16:02:33 2018 +0300

    All: remove memset() before sprintf()
    
    It's not needed.
    There's a good chance the compiler is smart enough to remove it
    anyway, but it can't hurt - I hope.
    
    Compile-tested only!
    
    Change-Id: Id7c054e146ba630227affa591007803f3046416b
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 32c8f70f49c0e287c53998e37867f00fa775377b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 13 13:06:20 2018 -0700

    error-gen, locks: Fix a typo in comments
    
    s/coverty/coverity/
    
    Change-Id: Iac7c13176162eace4247dd3236373aa76d906380
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit e4015ece284ad3f5de8a1632984594480533e0a0
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Aug 13 16:29:49 2018 +0530

    tests: Fix for gfid-mismatch-resolution-with-fav-child-policy.t failure
    
    This test was retried once on build
    https://build.gluster.org/job/regression-on-demand-multiplex/174/
    (logs for the first try is not available with this build)
    Test case was failing in line #47 where it was was checking for the
    heal count to be 0. Line #51 had passed that means file got the gfid
    split brain resolved, and both the bricks had same gfids.
    At line #54 it again failed which checks for the md5sum on both the
    bricks. At this point the md5sum of the brick where the file got
    impunged had the md5sum same as the newly created empty file. This
    means the data heal has not happened for the file.
    At line #64 enabling granular-entry-heal faild, but without the logs
    it is not possible to debug this issue.
    
    Change-Id: I56d854dbb9e188cafedfd24a9d463603ae79bd06
    fixes: bz#1615331
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 58d2c13c7996d6d192cc792eca372538673f808e
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Aug 12 18:33:11 2018 -0700

    libglusterfs: Fix a resource leak in graph.c
    
    Fixes CID 1382367
    
    Change-Id: I02678fc71716ab0046ea2ef437c6594a8a34a4fc
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit d3b0af8e64df14ff310044f35387c9de4d36df0a
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Jul 26 00:51:33 2018 +0530

    cloudsync: fix -Werror=format-truncation error on gcc8
    
    Here is the gcc8 warning:
    
    libcloudsyncs3.c: In function ‘aws_download_s3’:
    libcloudsyncs3.c:480:48: error: ‘%s’ directive output may be
    truncated writing up to 4095 bytes into a region of size
    1015 [-Werror=format-truncation=]
    snprintf(buf, sizeof(buf), "https://%s/%s", priv->hostname, resource);
    libcloudsyncs3.c:480:9: note: ‘snprintf’ output 10 or more bytes
    (assuming 4105) into a destination of size 1024
    snprintf(buf, sizeof(buf), "https://%s/%s", priv->hostname, resource);
    
    Memleak:
    
    It fixes a memleak as well where sign_req in fn: aws_form_request was
    not freed. Adjusted the calloc size for sign_req as well to match with
    the demand.
    
    Test:
    
    Have tested the local cloudsync regression test to validate the changes.
    Smoke validation will be sufficient for the gcc8 warning fixes.
    
    Fixes: bz#1609126
    Change-Id: I1c537b30168f2e0b54862344a951843e86b0b488
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 885c56b6f3c43cea0b27345f47f5522b42ebf278
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Aug 8 10:30:31 2018 +0530

    tests: fix brick check orders
    
    fix brick checks for validating-server-quorum.t & quorum-validation.t
    ...and make brick_up_status_1 function more generic.
    
    Also fix a timing issue in
    bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t
    
    Change-Id: I797ef4cec5b160aafa979bae7151b1e99fcb48ac
    Updates: bz#1603063
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 68be932b53daa27be7504bc49ac4c8ba33b5a733
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Aug 3 10:20:08 2018 +0530

    posix: Mark 'shared-brick-count' as settable
    
    updates: #302
    Change-Id: I9c1b9c9751c21866b074ac5d3ef15a58ae7aa707
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit c72b21dc0f34ed9a46afbf299127c3d7f6b66c78
Author: Nigel Babu <nigelb@redhat.com>
Date:   Wed Aug 8 15:22:05 2018 +0530

    Fix a grammar error in the logs
    
    Change-Id: Ie4fe18d5094c051fa20de71f7fc841085cc6aaee
    Fixes: bz#1614142
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit bd35aa2aa34c9bd2269aa225f83a404a58b81a21
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Aug 6 19:40:30 2018 -0400

    coverity: last of the secure temp fixes
    
    Coverity ignore directive is not working if the comment is
    split across lines (or has an empty line at the end.
    
    This can be seen in this report:
    https://download.gluster.org/pub/gluster/glusterfs/static-analysis
      /master/glusterfs-coverity/2018-08-06-b982e09f/html/1
      /384glusterfsd-mgmt.c.html#error
    
    In other places the same pattern has avoided coverity from
    flagging off the same call, except here.
    
    Updates: bz#789278
    
    Change-Id: Ic35ff0fc91d0a42904630728ef7c18215aa277f3
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 93c9062ccdf6a5b0461e2ea10ebe8d54d364a243
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sun Aug 12 15:33:29 2018 +0530

    tests/quick-read/bug-846240.t: fix a wrong test
    
    Earlier this test did following things on M0 and M1 mounted on same
    volume:
    1 create file  M0/testfile
    2 open an fd on M0/testfile
    3 remove the file from M1, M1/testfile
    4 echo "data" >> M0/testfile
    
    The test expects appending data to M0/testfile to fail. However,
    redirector ">>" creates a file if it doesn't exist. So, the only
    reason test succeeded was due to lookup succeeding due to stale stat
    in md-cache. This hypothesis is verified by two experiments:
    * Add a sleep of 10 seconds before append operation. md-cache cache
      expires and lookup fails followed by creation of file and hence append
      succeeds to new file.
    * set md-cache timeout to 600 seconds and test never fails even with
      sleep 10 before append operation. Reason is stale stat in md-cache
      survives sleep 10.
    
    So, the spurious nature of failure was dependent on whether lookup is
    done when stat is present in md-cache or not.
    
    The actual test should've been to write to the fd opened in step 2
    above. I've changed the test accordingly. Note that this patch also
    remounts M0 after initial file creation as open-behind disables
    opening-behind on witnessing a setattr on the inode and touch involves
    a setattr. On remount, create operation is not done and hence file is
    opened-behind.
    
    Change-Id: I739f255e0a62ff0024f0824dad3539974955df99
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1615096

commit fcf7ac887147e2f96a93165480c70364ee89a870
Author: karthik-us <ksubrahm@redhat.com>
Date:   Fri Aug 10 15:37:15 2018 +0530

    cluster/afr: Fix bug-1433571-undo-pending-only-on-up-bricks.t
    
    Problem:
    The test case was checking for the entry pending marker reset
    on the root after performing client side lookup at line #60-63.
    But sometimes the entry heal was not getting completed immediately.
    
    Fix:
    Wait for the entry heal to complete before checking the changelog.
    
    Change-Id: I42fde21b04a126ab044ce58373a996d72f125d96
    fixes: bz#1614730
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit f88636abcb300c3a6b3cc579fa93da6d6b4107a7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Aug 12 11:43:36 2018 +0530

    tests: potential fixes to bugs/replicate/bug-1408712.t
    
    See BZ for details.
    
    Change-Id: I2cc2064f14d80271ebcc21747103ce4cee848cbf
    fixes: bz#1615078
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit b1f416a87b9822a9677626e8a234e594c4e96a78
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Aug 13 12:03:07 2018 +0530

    tests: fix replace-brick-self-heal.t failure
    
    Please see BZ for details.
    
    Change-Id: Id9273432874bc6a452ac96b2b8c7a61ea6c5b98d
    Fixes: bz#1615239
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit febee007bb1a99d65300630c2a98cbb642b1c8dc
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Jul 31 14:52:51 2018 +0530

    gfapi : Handle the path == "" glfs_resolve_at
    
    Currently there is no check for path = "" in glfs_resolve_at.
    So if application sends an empty path, then the function resolves
    into the parent inode which is incorrect. Plus modified possible
    of "path" with "origpath" in the same function.
    
    Change-Id: Ie5ff9ce4b771607b7dbb3fe00704fe670421792a
    fixes: bz#1610236
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit cde1d393992f9b44954e0e790b3963fe4fa47e92
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Aug 11 19:18:32 2018 +0530

    performance/quick-read: handle rollover of generation counter
    
    Change-Id: I37a6e0efda430b70d03dd431c35bef23b3d16361
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit 212075b662820a2794f170d11b3a66734e00d6c3
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Aug 12 15:25:21 2018 +0530

    tests: fix tests/bugs/shard/configure-lru-limit.t
    
    Check for the bricks to be up before attempting to mount.
    
    Change-Id: I1224908137016df3007f4467aa9760967ce0694d
    Fixes: bz#1615092
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit bec64909c1ca10f4b393bcc07a9698030ffdb95b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 10 12:44:48 2018 +0530

    tests: potential fixes for tests/basic/afr/add-brick-self-heal.t
    
    Please see bug description for details.
    
    Change-Id: Ieb6bce6d1d5c4c31f1878dd1a1c3d007d8ff81d5
    fixes: bz#1614654
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 0250d32f759dc553e28eca85fa3c18e7c22fd8f0
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Aug 10 08:14:14 2018 -0400

    geo-rep: Fix deadlock during worker start
    
    Analysis:
    Monitor process spawns monitor threads (one per brick).
    Each monitor thread, forks worker and agent processes.
    Each monitor thread, while intializing, updates the
    monitor status file. It is synchronized using flock.
    The race is that, some thread can fork worker while
    other thread opened the status file resulting in
    holding the reference of fd in worker process.
    
    Cause:
    flock gets unlocked either by specifically unlocking it
    or by closing all duplicate fds referring to the file.
    The code was relying on fd close, hence a reference
    in worker/agent process by fork could cause the deadlock.
    
    Fix:
    1. flock is unlocked specifically.
    2. Also made sure to update status file in approriate places so that
    the reference is not leaked to worker/agent process.
    
    With this fix, both the deadlock and possible fd
    leaks is solved.
    
    fixes: bz#1614799
    Change-Id: I0d1ce93072dab07d0dbcc7e779287368cd9f093d
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 29d5557854703f61a4aa1fc53d6b49de9a99fe9d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Aug 10 09:12:05 2018 +0530

    glusterd: compare friend data within mutex
    
    During friend handshake if the glusterd receives more than one friend
    updates, it might very well become possible that two threads would end
    up working on two different volinfo references and glusterd might end up
    updating the store with a old volinfo reference. While debugging
    glusterd crash from validating-server-quorum.t test file from the
    line-coverage regression the same was observed.
    
    Solution is to run glusterd_compare_friend_data under a mutex.
    
    Test:
    
    As the crash was more visible in the line-coverage run (given lcov does
    some instrumentation and exposes the races), 6 manual lcov runs were
    triggered starting from https://build.gluster.org/job/line-coverage/443
    to https://build.gluster.org/job/line-coverage/449/ and no crash was
    observed from validating-server-quorum.t
    
    Change-Id: I86fce473a76fd24742d51bf17a685d28b90a8941
    Fixes: bz#1603063
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 48b93c292c0069da9ac2fe77e66d08a1cdeacfdc
Author: ShyamsundarR <srangana@redhat.com>
Date:   Sat Aug 11 13:21:36 2018 -0400

    tests: Fix cleanup routine for some mux tests
    
    Some of the mux tests, set a trap to catch test exit and
    call cleanup. This will cause cleanup to be invoked twice
    in case the test times out, or even otherwise, as include.rc
    also sets a trap to cleanup on exit (TERM and others).
    
    This leads to the tarballs generated on failures for these
    tests to be empty and does not aid debugging.
    
    This patch corrects this pattern across the tests to the
    more standard cleanup at the end.
    
    Fixes: bz#1615037
    Change-Id: Ib83aeb09fac2aa591b390b9fb9e1f605bfef9a8b
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 488dcc17b76b1b46c13ccd269b7a092c014a4d94
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Aug 10 12:46:20 2018 +0530

    Make sure EXPECT_WITHIN executes the statement multiple times
    
    When we pass a command to be executed in EXPECT_WITHIN and we use ``
    the value is passed by value, so if the first execution gives a result
    that is different from the expected value, EXPECT_WITHIN test will
    fail because the command will not be re-evaluated. Changed the
    expression with `` to a function. Added sleep(3) in afr.c for
    reconfigure to both RC and re-test after the change.
    
    fixes bz#1614662
    Change-Id: I3bc8a75b996729261aa48067f6ed8da9c6273b13
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit bd8fc26a278697c30537d879ea5402db7ebab577
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Sat Aug 4 12:05:03 2018 +0530

    glusterd: Compare volume_id before start/attach a brick
    
    Problem: After reboot a node brick is not coming up because
             fsid comparison is failed before start a brick
    
    Solution: Instead of comparing fsid compare volume_id to
              resolve the same because fsid is changed after
              reboot a node but volume_id persist as a xattr
              on brick_root path at the time of creating a volume.
    
    Change-Id: Ic289aab1b4ebfd83bbcae8438fee26ae61a0fff4
    fixes: bz#1612418
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit a6900e829484435c5bd5d8efe38490cab54ac442
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Wed Aug 8 08:17:28 2018 +0530

    core: Update condition in get_xlator_by_name_or_type
    
    Problem: Sometimes client connection is failed after throwing
             error "cleanup flag is set for xlator Try again later".
             The situation comes only after get a detach request but
             the brick stack is not completely detached and at the same time
             the client initiates a connection with brick
    
    Solution: To resolve the same check cleanup_starting flag in get
              xlator_by_name_or_type, this function call by server_setvolume
              to attach a client with brick.
    
    Change-Id: I3720e42642fe495dd05211e2ed2cb976db9e231b
    fixes: bz#1614124
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 7d4849499663a42ed81e1f9ebc95c82fc70dc4c3
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Aug 3 20:50:43 2018 +0530

    tests: kill_brick should wait for brick status to become offline
    
    Change-Id: I52e8eec7f334af37de433c444f4ddfc876fa56cc
    Fixes: bz#1614088
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 69c557ad8468f9e32090cbef78512f82a98f7043
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Aug 8 18:29:01 2018 -0400

    tests: Add ability to preserve older tarball for retried tests
    
    When a test is retried, the cleanup directives overwrite the
    older tarball with the latest one, thus losing the logs from
    the failed run.
    
    This patch changes run-tests.sh to rename the older tarball
    when retrying a test, thus preserving the same.
    
    The tarball is renamed using a time stamp and optionally a
    trailing sequence number, in case the test fails within the
    very second. Although the sequence # is not strictly required
    as we retry only once, it provides a defence for any future
    enhancements to the same.
    
    Fixes: bz#1614062
    Change-Id: I9afe486b0b6f6a26f2ad0642e38bc0ba15b3ecc9
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 22d5540f5618ea0726a5eab1252163c48124cc06
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Aug 8 15:26:42 2018 +0530

    tests: Set heal-timeout to 5 seconds
    
    Shd keeps doing heals in a loop until it heals at least one entry in the
    previous run. A heal is termed successful only if it heals both metadata and
    entry/data heal i.e. the entry needs to be completely healed by just that healer.
    
    In tests/basic/afr/granular-esh/replace-brick.t test, brick-0 is old and brick-1
    is new. After replace-brick only root-gfid will be present in brick-0's index
    1) shd-thread corresponding to brick-0 does metadata heal, this creates
    root-gfid in brick-0's 'dirty' index.
    2) Both healer threads corresponding to brick-0 and brick-1 now try to heal
    root-gfid and brick-1 gets the heal-domain lock. brick-0's shd-thread will
    experience a failure and it goes back to waiting for 10 minutes
    (cluster.heal-timeout).
    3) When brick-1's healer-thread completes healing root-gfid it creates 5 files
    which create indices in brick-0, so until brick-0 doesn't trigger one more
    heal, heal won't happen. $HEAL_TIMEOUT is set at 120 seconds, which is lesser
    than cluster.heal-timeout, so decreasing this to 5 seconds so that the next
    heal is triggered which will do the heals.
    
    fixes bz#1613807
    Change-Id: I881133fc28880d8615fbc4558a0dfa0dc63d7798
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 511af2e786f5e881bc4c53287407235dd6fe2704
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Jul 26 07:09:40 2018 -0400

    tests: Increase timeout for mpx restart crash test
    
    In lcov based regression testing environments, all tests take
    more time than what occurs in centos7 regressions. Possibly
    due to code instrumentation for lcov purposes.
    
    Due to this the test, bug-1432542-mpx-restart-crash.t constantly
    times out. This patch increases the timeout for the same to enable
    lcov tests to pass on a more regular basis.
    
    It was also noted by Nithya that the test at times generated an
    OOM kill on the regression machines. In order to reduce runtime
    memory foot print of the tests, FUSE mounts are unmounted as
    soon as the required test is complete.
    
    Fixes: bz#1608568
    
    Change-Id: I37f8d4b45807a69c52c7c7df4923c0fc33fab4e4
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit bb9b8f61501cc633e585593de4d9f2fe5494d5ce
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Aug 7 10:25:49 2018 +0530

    glusterd: more stricter checks of if brick is running in multiplex mode
    
    While gf_attach () utility can help in detaching a brick instance from
    the brick process which the kill_brick () function in tests/volume.rc
    uses it has a caveat which is as follows:
    1. It doesn't ensure the respective brick is marked as stopped which
    glusterd does from glusterd_brick_stop
    2. Sometimes if kill_brick () is executed just after a brick stack is
    up, the mgmt_rpc_notify () can take some time before marking
    priv->connected to 1 and before it if kill_brick () is executed, brick
    will fail to initiate the pmap_signout which would inturn cleans up the
    pidfile.
    
    To avoid such possibilities, a more stricter check on if a brick is
    running or not in brick multiplexing has been brought in now where it
    not only checks for its pid's existance but checks if the respective
    process has the brick instance associated with it before checking for
    brick's status.
    
    Change-Id: I98b92df949076663b9686add7aab4ec2f24ad5ab
    Fixes: bz#1595320
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 12ce1848f55686cfae0b03f532279938722c0963
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Aug 2 07:30:46 2018 -0400

    tests/bitrot: Fix tests/bitrot/bug-1373520.t
    
    The test was failing with brick-mux enabled
    intermittently. As the test depends on lookup
    to recover file via heal, it's advisable to
    disable all perf xlators. Hence doing the same.
    
    fixes: bz#1611566
    Change-Id: Ib7705e7951d53c435b8e390298164d73c6d71745
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 9e03c5fc66550909611eacda056d257254191972
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Aug 3 14:43:30 2018 +0530

    MAINTAINERS: Add Xavier Hernandez as peer for shard xlator
    
    Shard module never had a peer, although Pranith reviewed most
    of the patches. Over the past few months, Xavier has reviewed
    shard patches - both big and small - and also found some great
    bugs in his reviews of some complex patches. Proposing that we
    add him as peer for shard translator.
    
    Change-Id: I29487052673f3738340764aa63bdd7586fb28def
    fixes: bz#1612017
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 0e821f9d10939495181484588f200300b70dfcc2
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Aug 6 13:55:08 2018 -0400

    tests: Add timeout option to run-tests.sh
    
    Added a '-t' timeout option to run-tests.sh, to be able to
    set this to higher than the default 200 in case of lcov
    based tests, as those take more time due to instrumentations
    added by lcov.
    
    Change-Id: Ibaf70e881bfa94f35e822124bcf9849b309e7cc1
    Updates: bz#1608564
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit b982e09f01cf6423e8f5ae9601047fff13bb4f94
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Jul 10 08:34:48 2018 +0530

    performance/quick-read: don't update with stale data after invalidation
    
    Once invalidated, make sure that only ops incident after invalidation
    update the cache. This makes sure that ops before invalidation don't
    repopulate cache with stale data. This patch also uses an internal
    counter instead of frame->root->unique for keeping track of
    generations.
    
    Change-Id: I6b38b141985283bd54b287775f3ec67b88bf6cb8
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit 871ea43ef0d5e1c76903cdda63ccf2a8764a9615
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Aug 2 10:17:28 2018 +0530

    tests: fix online_brick_count function
    
    online_brick_count should discard Bitrot and Scrubber daemon.
    
    Change-Id: I301373ccdbeec1d1a5e6c6b137f48ed997f22556
    Fixes: bz#1611103
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit e47a320508661d8f33a7b583cf7f6999070d37de
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Aug 2 22:55:35 2018 +0200

    posix: prevent crash when SEEK_DATA/HOLE is not supported
    
    Instead of not defining the 'seek' fop when it's not supported on the
    compilation platform, we simply return EINVAL when it's used.
    
    Fixes: bz#1611834
    Change-Id: I253666d8910c5e2fffa3a3ba37085e5c1c058a8e
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 60fbef9a0b6057e87f3a4fbdcb3270bd65b649c1
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Aug 3 19:06:27 2018 +0530

    Revert "performance/readdir-ahead: Invalidate cached dentries if they're modified while in cache"
    
    This reverts commit 7131de81f72dda0ef685ed60d0887c6e14289b8c.
    
    With the latest master, I created a single brick volume and some files
    inside it.
    
    [root@rhgs313-6 ~]# umount -f /mnt/fuse1; mount -t glusterfs -s
    192.168.122.6:/thunder /mnt/fuse1; ls -l /mnt/fuse1/; echo "Trying
    again"; ls -l /mnt/fuse1
    umount: /mnt/fuse1: not mounted
    total 0
    ----------. 0 root root 0 Jan  1  1970 file-1
    ----------. 0 root root 0 Jan  1  1970 file-2
    ----------. 0 root root 0 Jan  1  1970 file-3
    ----------. 0 root root 0 Jan  1  1970 file-4
    ----------. 0 root root 0 Jan  1  1970 file-5
    d---------. 0 root root 0 Jan  1  1970 subdir
    Trying again
    total 3
    -rw-r--r--. 1 root root 33 Aug  3 14:06 file-1
    -rw-r--r--. 1 root root 33 Aug  3 14:06 file-2
    -rw-r--r--. 1 root root 33 Aug  3 14:06 file-3
    -rw-r--r--. 1 root root 33 Aug  3 14:06 file-4
    -rw-r--r--. 1 root root 33 Aug  3 14:06 file-5
    d---------. 0 root root  0 Jan  1  1970 subdir
    [root@rhgs313-6 ~]#
    
    Conversation can be followed on gluster-devel on thread with subj:
    tests/bugs/distribute/bug-1122443.t - spurious failure. git-bisected
    pointed this patch as culprit.
    
    Change-Id: I1eb46f6c196f44fde8ce991840a0e724e6f50862
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1390050

commit 7959147cfa75b3dd0320090e2173bb90930788e7
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sun Jul 1 06:43:51 2018 +0530

    performance/ob: stringent synchronization between rename/unlink and open
    
    Issue 1:
    ========
    open all pending fds before resuming rename and unlink
    
    currently ob uses fd_lookup to find out the opened-behind. But,
    fd_lookup gives the recent fd opened on the inode, but the oldest
    fd(s) (there can be multiple fds opened-behind when the very first
    opens on an inode are issued in parallel) are the candidates for fds
    with pending opens on backend. So, this patch explictily tracks the
    opened-behind fds on an inode and opens them before resuming rename or
    unlink.
    
    similar code changes are also done for setattr and setxattr to make
    sure pending opens are complete before permission change.
    
    This patch also adds a check for an open-in-progress to
    ob_get_wind_fd. If there is already an open-in-progress,
    ob_get_wind_fd won't return an anonymous fd as a result. This is done
    to make sure that rename/unlink/setattr/setxattr don't race with an
    operation like readv/fstat on an anonymous fd already in progress.
    
    Issue 2:
    ========
    once renamed/unlinked, don't open-behind any future opens on the same
    inode.
    
    Issue 3:
    ========
    Don't use anonymous fds by default. Note that rename/unlink can race
    with a read/fd on anonymous fds and these operations can fail with
    ESTALE. So, for better consistency in default mode, don't use
    anonymous fds. If performance is needed with tradeoff of consistency,
    one can switch on the option "use-anonymous-fd"
    
    Change-Id: Iaf130db71ce61ac37269f422e348a45f6ae6e82c
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit 93d7f3f2da52b6fb513ad2ff91c5bd0589d1482b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Aug 1 15:09:08 2018 +0530

    glusterd: Bricks of a normal volumes should not attach to gluster_shared_storage bricks
    
    Problem: In a brick multiplexing environment, Bricks of a normal volume
    created by user are getting attached to the bricks of a volume
    "gluster_shared_storage" which is created by enabling the
    enable-shared-storage option. Mounting gluster_shared_storage
    has strict authentication checks. when we attach bricks of a normal
    volume to bricks of gluster_shared_storage, mounting the normal
    volume created by user will fail due to strict authentication checks.
    
    Solution: We should not attach bricks of a normal volume to brick
    process of gluster_shared_storage volume and vice versa.
    
    fixes: bz#1610726
    Change-Id: If1b5a2a02675789a2915ba480fb48c145449163d
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 60f1aeb08df80501caf6b17543592de02d61381f
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Jul 30 14:09:14 2018 -0400

    coverity: Fix remaining SECURE_TEMP issues reported
    
    Two pending SECURE_TEMP issues still exist in the coverity
    reports, these are fixed by this patch.
    
    In both instances (where functions actually seem to be
    duplicates of each other) the need was for a FILE * and
    not an fd. Applied the same pattern in both places as in
    other parts of the code where mkstemp was used and later
    a FILE * was created from the resulting fd for use.
    
    Coverity report: https://download.gluster.org/pub/gluster/
      glusterfs/static-analysis/master/glusterfs-coverity/
      2018-07-30-4d3c62e7/html/
    
    Issues numbered: 382, 383 (named SECURE_TEMP)
    
    Further added tmpfile to the blacklist, so that future code
    changes do not add the same, into symbol-check.sh.
    
    Also corrected shellcheck errors in symbol-check.sh as a
    result of updating the same.
    
    Updates: bz#789278
    
    Change-Id: I1d572a16ca5b5df2f597aeaa5f454fad34c8296e
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 9e96d646537fd060ca932291aaa0c4a3ce942b67
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jul 31 10:27:03 2018 -0400

    geo-rep/hook-script: Fix ssh/scp options
    
    Always use ssh and scp with "-oPasswordAuthentication=no"
    and "-oStrictHostKeyChecking=no" options. It might hang
    the post script otherwise leading geo-rep setup failure
    
    Also increased geo-rep timeout. Occasionally, it's taking
    more time to reach Active/Passive status. Especially, the
    first start after create.
    
    fixes: bz#1610405
    Change-Id: I9560d64dbe0edf5db73446a9fc97dda19b88d233
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 74b63639e81a4e674600993cfbec619c61857c35
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Jul 14 18:17:47 2018 +0530

    performance/open-behind: don't use anonymous fds for reads by default
    
    anonymous fds interfere with working of read-ahead as read-ahead won't
    be able to store its cache in fd. Also, as seen in bz 1455872,
    anonymous fds also affect performance of large file sequential reads
    as the cost of opening fd for each read on brick stack is
    significant. So, have a proper fd which enables read-ahead to store
    its cache and brick stack to reuse the fd during reads.
    
    With this change test
    tests/bugs/snapshot/bug-1167580-set-proper-uid-and-gid-during-nfs-access.t
    fails consistently. The failure can also be seen with open-behind
    off. bz 1611532 has been filed to track the issue with test. Thanks to
    Rafi <rkavunga@redhat.com> for assistance provided in debugging test
    failure.
    
    Change-Id: Ifa52d8ff017f115e83247f3396b9d27f0295ce3f
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1455872

commit 47cbe34db67be7bfbf925b3d76bb25d48b9ed680
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jun 28 05:55:09 2018 +0530

    performance/md-cache: update cache only from fops issued after previous invalidation
    
    Invalidations are triggered mainly by two codepaths - upcall and
    write-behind unwinding a cached write with zeroed out stat. For the
    case of upcall, following race can happen:
    * stat s1 is fetched from brick
    * invalidation is detected on brick
    * invalidation is propagated to md-cache and cache is invalidated
    * s1 updates md-cache with a stale state
    
    For the case of write-behind, imagine following sequence of operations,
    * A stat s1 was issued from application thread t1 when size of file
      was s1
    * stat s1 completes on brick stack, but yet to reach md-cache
    * A write w1 from application thread t2 extends file to size s2 is
      cached in write-behind and response is unwound with zeroed out stat
    * md-cache while handling write-cbk, invalidates cache
    * md-cache receives response for s1, updates cache with stale stat
      with size of s1 overwriting invalidation state
    
    Fix is to remember when s1 was incident on md-cache and update cache
    with results of s1 only if the it was incident after invalidation of
    cache.
    
    This patch identified some bugs in regression tests which is tracked
    in https://bugzilla.redhat.com/show_bug.cgi?id=1608158. As a stop gap
    measure I am marking following tests as bad
            basic/afr/split-brain-resolution.t
            bugs/bug-1368312.t
            bugs/replicate/bug-1238398-split-brain-resolution.t
            bugs/replicate/bug-1417522-block-split-brain-resolution.t
            bugs/replicate/bug-1438255-do-not-mark-self-accusing-xattrs.t
    
    Change-Id: Ia4bb9dd36494944e2d91e9e71a79b5a3974a8c77
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit 45b023aac0cafa93a43a078c7bc94c8f5b8c3cb7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 20 10:33:00 2018 +0530

    coding-standard: add points on structure padding
    
    This is a recommendation for users, and reviewers can take a point from this.
    
    Updates: bz#1193929
    Change-Id: Idcd778e42a886fd79b549da4927149a07573a20b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit bca47bd4015ead34ac3e380b5839ba32fd701b88
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sun Jul 22 11:37:24 2018 +0530

    performance/write-behind: synchronize rename with cached writes on src
    
    rename response contains a postbuf stat of src-inode. Since md-cache
    caches stat in rename codepath too, we've to make sure stat accounts
    any cached writes in write-behind. So, we make sure rename is resumed
    only after any cached writes are committed to backend.
    
    Change-Id: Ic9f2adf8edd0b58ebaf661f3a8d0ca086bc63111
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit fe5d8d3643c2bc2fdb95b0351b26fb286cf778b7
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jul 26 21:47:24 2018 +0530

    socket: Remove code duplication
    
    While I was reading code, I saw that socket_submit_request()
    and socket_submit_reply() are identical except for @a_byte and
    the source of @msg object being different.
    
    This patch moves all of the common code to a new function with
    the differing vars passed as parameters by the callers.
    
    Change-Id: I7a62ae72f10c34dc8de01b250d89a77ec5ab490d
    fixes: bz#1608991
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit e91bffad97da117f2c4eb8db45ab7874e59addf5
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 20 11:04:01 2018 +0530

    doc: keep just one copy of a coredump analysis
    
    Keeping two copies of the files means, one would be out-of-date soon,
    and users would always be confused about which one is the source of
    truth.
    
    Updates: bz#1193929
    Change-Id: I568149732fdb9d282ccd583640eee9b9056963fd
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit f354af3a56604c61e09e29c13fe8fb632c1013a8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jul 29 12:28:43 2018 +0200

    rpm: do not build glusterfs-resource-agents on el6
    
    glusterfs-resource-agents depends on glusterfs-server and this is not
    available on el6 with the current Gluster releases. It is not possible
    to install glusterfs-resource-agents on el6 without running into
    dependency problems, so do not build the sub-packae at all.
    
    Change-Id: Ibe08ad3a1b7882559b4e445603d0508b9282b755
    Fixes: bz#1609551
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 4d3c62e71f3250f10aa0344085a5ec2d45458d5c
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Jun 27 14:51:37 2018 +0530

    performance/write-behind: better invalidation in readdirp
    
    Current invalidation of stats in wb_readdirp_cbk is prone to races. As
    the deleted comment explains,
    
    <snip>
    We cannot guarantee integrity of entry->d_stat as there are cached
    writes. The stat is most likely stale as it doesn't account the cached
    writes. However, checking for non-empty liability list here is not a
    fool-proof solution as there can be races like,
      1. readdirp is successful on posix
      2. sync of cached write is successful on posix
      3. write-behind received sync response and removed the request from
         liability queue
      4. readdirp response is processed at write-behind.
    
    In the above scenario, stat for the file is sent back in readdirp
    response but it is stale.
    </snip>
    
    Change-Id: I6ce170985cc6ce3df2382ec038dd5415beefded5
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit 379d4279601f694465cc7eaffcb737410d5d9e31
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jul 27 08:45:48 2018 +0000

    build: remove bundled arg-standalone
    
    libargp or argp-standalone is available on all commonly used
    distributions. There is no need to bundle an unmaintained version of
    argp-standalone in this repository anymore.
    
    FreeBSD places the argp.h file in /usr/local/include when
    argp-standalone is installed. This path is not added to CPPFLAGS by
    default, so thats done in configure.ac as well.
    
    Change-Id: I384a53ab0a008ec9d48fd83afeaf8fbc197e91ee
    Fixes: bz#1609337
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 7131de81f72dda0ef685ed60d0887c6e14289b8c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 17 16:40:04 2017 +0530

    performance/readdir-ahead: Invalidate cached dentries if they're modified while in cache
    
    PROBLEM:
    
    Entries that are readdirp'd ahead can undergo modification in terms
    of writes, truncates which could modify their iatts. When a readdir
    is finally wound at offset corresponding to these entries, the iatts
    that are returned to the application come from readdir-ahead's cache,
    which are stale by now. This problem gets further aggravated when caching
    translators/modules cache and continue to serve this stale information.
    
    FIX:
    
    Whenever a dentry undergoes modification, in the cbk of the modification fop,
    a "dirty" flag (default 0) is set in its inode ctx. When it's time for
    readdir-ahead to serve these entries, it will read the inode ctx and check
    if the entry is "dirty", and if it is, set the entry's attrs to all zeroes,
    as an indicator to fuse, md-cache etc not to cache these attributes.
    
    Also there is one tiny race between the entry creation and a readdirp on its
    parent dir, which could cause the inode-ctx setting and inode ctx reading to
    happen on two different inode objects. To prevent this, fuse-bridge is made to
    drop entries for which dentry->inode is not the same as linked inode,
    in readdirp cbk.
    
    Change-Id: If7396507632b5268442ca580473d5155fee9cbef
    BUG: 1390050
    Updates: bz#1390050
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 2e0744570fe1f6148e0c7b1c1a5bf98cc4eaf990
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Fri Jul 27 08:42:00 2018 +0800

    rpc: fix return value in rpc destroy
    
    Change-Id: I73a113e2d40f508fd53b273a990a2371692c87bf
    fixes: bz#1607689
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit e7c87f757c9dbf2492c22f8b5a4c9700e126af31
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Mon Jul 23 16:07:59 2018 +0800

    rpc: add missing free of rpc->dnscache
    
    Change-Id: I3fa97b99bf23459cf548205d75d2cc7936b2310e
    fixes: bz#1607689
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 75300258c42aeb29350ac55beb3360ca208454b5
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Mon Jul 23 15:27:41 2018 +0800

    libgfapi: fix memory leak on old volume files
    
    Fix missing free of fs->oldvolfile. This patch uses standard
    calloc/realloc to allocate memory for vol file. As by the time fs struct
    is destroyed, the THIS->ctx is already gone, that causes invalid memory
    access.
    
    Change-Id: I72ae19c76eb16e61f077714f7e52405fee721997
    fixes: bz#1607689
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit a6b5ec5cb5e2fb429b51c0d2b064fbd96c9de80c
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Mon Jul 23 18:15:58 2018 +0800

    libgfapi: add missing unref of mgmt client in glfs_fini
    
    Change-Id: I89cdf14cb9d822eaf7c01cf0b0220b423eb5b705
    fixes: bz#1607689
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 7f7296d1f52f1b4308551fafad4eb22e3855b382
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jul 23 11:35:16 2018 +0200

    build: remove uuid from contrib/
    
    Bundling libuuid is not needed anymore, all current distributions
    provide it now.
    
    Some OS's provide their own uuid_*() functions in libc. These may not be
    fully compatible with libuuid.so found on Linux systems. In that case,
    either e2fsprogs-libuuid can be installed, or support for the native
    uuid_*() functions can be added to libglusterfs/src/compat-uuid.h.
    
    Change-Id: Icfa48caea81307a3bca549364969c2038911942b
    Fixes: bz#1607319
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 35cfc01fa2e395111f7d629f00dc06eecf35a709
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 26 13:07:04 2018 +0000

    build: rename event.h to gf-event.h
    
    Newer FreeBSD versions (noticed with 10.3-RELEASE) provide a event.h
    file that on occasion gets included instead of the libglusterfs file.
    When this happens, 'struct event_pool' will not be defined and building
    will fail with errors like:
    
        autoscale-threads.c:18:55: error: incomplete definition of type 'struct event_pool'
                int                      thread_count   = pool->eventthreadcount;
                                                          ~~~~^
        autoscale-threads.c:17:16: note: forward declaration of 'struct event_pool'
                struct event_pool       *pool           = ctx->event_pool;
                       ^
    
    This problem is caused by 'pkg-config --cflags uuid' that adds
    /usr/local/include to the GF_CPPFLAGS. The use of libuuid is preferred
    so that the contrib/uuid/ directory can be removed.
    
    By renaming event.h to gf-event.h there is no conflict between the
    different event.h files anymore and compiling on FreeBSD works without
    issues.
    
    Change-Id: Ie69f6b8a4f8f8e9630d39a86693eb74674f0f763
    Updates: bz#1607319
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 405c6e8a8a64f29b37c154091e1677ef67440e73
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Jul 26 13:32:52 2018 -0400

    stack: Reduce stack usage for local variables to store tmpfile names
    
    This patch moves stack based PATH_MAX allocations for tmpfile
    names, to heap allocated names instead. Reducing the impact on
    stack space used and accruing benefits thereof.
    
    Change-Id: I646d9cb091018de6768b3523902788fa2ba14d96
    Updates: bz#1193929
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 46a2cbfb73f7fade3426fd07c5830e9fac82883c
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Jul 24 20:23:14 2018 -0400

    coverity: Ignore most of SECURE_TEMP issues
    
    mkstemp as per the Linux man page, uses 0600 as the permission
    bits when creating the file. This is hence safe and a Coverity
    warning that should be ignored.
    
    Further, we are mostly a multi-threaded program in all our daemons
    and cannot set and unset umask at will in a multi-threaded
    program, to address the coverity issue.
    
    This change attempts to nudge coverity to ignore this warning,
    using the pattern,
    /* coverity[EVENT_TAG_NAME] ... */
    <line of code that has the issue>
    
    This commit is an experiment, if post merge the next coverity
    report ignores these errors, the above pattern (as found using
    an internet search) works and can be applied to certain other
    warnings as well.
    
    Change-Id: I73a184ce1a54dd9e66542952b1190a74438c826a
    Updates: bz#789278
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 1739f7e0b2af6245d54b130e87d805944e9f7e63
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Jan 29 13:35:34 2018 +0530

    rpc: merge ssl infra with epoll infra
    
    Patch attempts to use the epoll infra for handling SSL connections
    as well instead of the socket_poller() thread func.
    This essentially makes priv->own_thread flag redundant.
    
    SSL_connect()/SSL_accept() is now non-blocking which has done away
    with the localised poll() in ssl_do(). So, ssl_do() has been updated
    appropriately.
    
    own_thread and coincidently socket_poller() thread for SSL processing
    is now deprecated.
    
    Change-Id: I1ce54c06ddb643c16baa143598e7e4fbf16bae0a
    fixes: bz#1561332
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 9400b6f2c8aa219a493961e0ab9770b7f12e80d2
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Jul 12 13:29:48 2018 +0530

    glusterd: Add multiple checks before attach/start a brick
    
    Problem: In brick mux scenario sometime glusterd is not able
             to start/attach a brick and gluster v status shows
             brick is already running
    
    Solution:
              1) To make sure brick is running check brick_path in
                 /proc/<pid>/fd , if a brick is consumed by the brick
                 process it means brick stack is come up otherwise not
              2) Before start/attach a brick check if a brick is mounted
                 or not
              3) At the time of printing volume status check brick is
                 consumed by any brick process
    
    Test:  To test the same followed procedure
           1) Setup brick mux environment on a vm
           2) Put a breaking point in gdb in function posix_health_check_thread_proc
              at the time of notify GF_EVENT_CHILD_DOWN event
           3) unmount anyone brick path forcefully
           4) check gluster v status it will show N/A for the brick
           5) Try to start volume with force option, glusterd throw
              message "No device available for mount brick"
           6) Mount the brick_root path
           7) Try to start volume with force option
           8) down brick is started successfully
    
    Change-Id: I91898dad21d082ebddd12aa0d1f7f0ed012bdf69
    fixes: bz#1595320
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 2836e158f38eb9ed070de88b64a3a8758cd2d4c0
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Jul 26 13:01:04 2018 +0530

    maintainers: change in glusto ownership
    
    As the project has matured, Vijay and Akarsha have stepped up
    significantly. Nigel is stepping down to peer now that there are capable
    people who will be actively focusing on Glusto.
    
    Shwetha is no longer actively contributing and has therefore agreed to
    step down from peer.
    
    Change-Id: I089eb02857d2ea353e811cb8bdf71edda96fa041
    Fixes: bz#1608684

commit 4913f372fc486065a0fc4eeb53f5730aa9980cdf
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Jul 25 16:45:54 2018 -0400

    sdfs: Fix missing NULL option list tremination
    
    Option list for volume_options in sdfs was not NULL
    terminated. This resulted in a crash when running in
    lcov based builds.
    
    This is rectified by this patch.
    
    fixes: bz#1608566
    
    Change-Id: I5d8730f1ae963ed6adf21d970e4921c5d5d92f62
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 48d0fdaa2b92008c6e907aee9e5382c0bcc3e1c5
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jul 24 14:40:51 2018 -0400

    georep: fix hard-coded paths in gsyncd.conf.in
    
    This is part of the reason why we use autoconf (i.e. configure).
    For an ordinary clone+autogen.sh+configure SBIN_DIR is
    /usr/local/sbin; for an rpm or dpkg build it will be /usr/sbin.
    
    I wonder how many more are lurking in our sources? /usr/libexec is
    one that frequently bites us on  Debian and Ubuntu, which don't have
    /usr/libexec. (But it's all Linux, right?)
    
    See https://bugzilla.redhat.com/show_bug.cgi?id=1601532
    
    Reported-by: lohmaier+rhbz@gmail.com
    Change-Id: I6523894416cc06236ea1f99529efd36e957bd98e
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit abd7b1393294d29eef6913e7f93ab76040c90428
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Jul 24 14:48:35 2018 +0530

    rpc: rpc_clnt_connection_cleanup is crashed due to double free
    
    Problem: gfapi client is getting crashed in rpc_clnt_connection_cleanup
             at the time of destroying saved_frames
    
    Solution: gfapi client is getting crashed because saved_frame ptr is
              already freed in rpc_clnt_destroy.To avoid the same update
              code in rpc_clnt_destroy
    
    Change-Id: Id8cce102b49f26cfd86ef88257032ed98f43192b
    fixes: bz#1607783
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit 8ad159b2a7e302320a24d1d4f5d0b90302e0f25b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Jul 24 14:27:02 2018 +0530

    glusterd: Coverity issues with type FORWARD_NULL
    
    This patch fixes coverity issues 102, 103, 112 and 119 from [1]
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-07-23-5fa004f3/html/
    
    Updates: bz#789278
    
    Change-Id: I99762eb0bcbd974a5250434777db63520f2ce2e6
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 59401e705b9432345f3b449b50cfa4095ce2169a
Author: Oshank Kumar <okumar@redhat.com>
Date:   Tue Jul 24 16:26:18 2018 +0530

    glusterd: Deadcode Coverity issue
    
    This patch will fix coverity issue 74 from [1].
    
    we are updating ret value line number 5011, and
    immediately checking whether ret is having non
    zero value at line number 5013.If ret is 0, then
    only we continue to execute and we can reach line
    number 5036. By the time we reach 5036, ret value
    is always 0. So this block of code is redundant
    here and removing it.
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-07-23-5fa004f3/html/
    
    Updates: bz#789278
    
    Change-Id: Ia6e8ba2936e350f0d29a9151ab786622f5e750db
    Signed-off-by: Oshank Kumar <okumar@redhat.com>

commit 5fa004f3c4924dd6d83aecd5f33fc58badbe9305
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Jul 20 10:52:22 2018 +0530

    features/shard: Make lru limit of inode list configurable
    
    Currently this lru limit is hard-coded to 16384. This patch makes it
    configurable to make it easier to hit the lru limit and enable testing
    of different cases that arise when the limit is reached.
    
    The option is features.shard-lru-limit. It is by design allowed to
    be configured only in init() but not in reconfigure(). This is to avoid
    all the complexity associated with eviction of least recently used shards
    when the list is shrunk.
    
    Change-Id: Ifdcc2099f634314fafe8444e2d676e192e89e295
    updates: bz#1605056
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit e0df887ba044ce92e9a2822be9261d0f712b02bd
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Jul 21 04:27:12 2018 -0700

    storage/posix: Avoid log flood in posix_set_parent_ctime()
    
    posix_set_parent_ctime() unconditionally logs an error if consistent
    time attributes is not enabled. This log does not add any value, prints
    an incorrect errno & floods the log file.
    
    Hence nuking this log message in this patch.
    
    Change-Id: I82a78f2f8ce5ab518f8cdf6d9086a97049712f75
    fixes: bz#1607049
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit d05d4c61e784d08e87aed5b924504004f53b4fad
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Jul 17 15:56:35 2018 +0530

    geo-rep : fix possible crash
    
    Problem : In 'glusterd_verify_slave' while tokenizing error message
              we call 'strtok_r' and store return value in 'tmp' which
              can be NULL. We are passing this 'tmp' as 1st argument to
              'strcmp' which will lead to segmentation fault.
    Solution : before calling 'strcmp' we should NULL check 'tmp'.
    
    Change-Id: Ifd3864b904afe6cd09d9e5a4b55c6d0578e22b9d
    fixes: bz#1602121
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit fd8f712f31227ebfc3ecca63a7a3a5c3f15727d9
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 14 13:33:09 2017 -0400

    core (named threads): flood of -Wformat-truncation warnings with gcc-7.1
    
    Starting in Fedora 26 which has gcc-7.1.x, -Wformat-trunction is enabled
    with -Wformat, resulting in a flood of new warnings. This many warnings
    is a concern because it makes it hard(er) to see other warnings that
    should be addressed.
    
    An example is at
    https://kojipkgs.fedoraproject.org//packages/glusterfs/3.12.0/1.fc28/data/logs/x86_64/build.log
    
    For more info see https://review.gluster.org/#/c/18267/
    
    I can't find much (or good) documentation on the heuristics the
    compiler uses for this warning. In the case of printing integer types
    it appears it looks at the available space in the destination and the
    range of values for the variable and/or its type.
    
    To address the specific question about why 0x3ff versus 0xfff to mask
    the value, either would suffice to hint to the compiler that the
    printed value will fit in three characters. But the loop is from
    0...1023 (or 0...0x3ff if you prefer) so I chose that as a more
    "accurate" mask to use as it exactly matches the range of values of
    the loop.
    
    Fixes: bz#1492847
    Change-Id: I6e309ba42159841131d8241bfc0566ef09e00aa9

commit 621138ce763eda8270d0a4f6d7209fd50ada8787
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Jul 16 17:03:17 2018 +0300

    All: run codespell on the code and fix issues.
    
    Please review, it's not always just the comments that were fixed.
    I've had to revert of course all calls to creat() that were changed
    to create() ...
    
    Only compile-tested!
    
    Change-Id: I7d02e82d9766e272a7fd9cc68e51901d69e5aab5
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c0e76377d0fc47aa66f35ea70a4793731ebbd40c
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Fri Jun 1 12:21:18 2018 +0530

    quota: new volume set option to track of quota in GD2
    
    quota enable as volume set needs a new option to keep track of it.
    
    Bugzilla ID:1600812
    
    Change-Id: Ib8d770936bafe859f80e717409bd861760090e59
    fixes: bz#1600812
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit 8d7be4ac0cf5ace9de3f340f411f1aed21f96414
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sun Jul 15 15:03:40 2018 -0400

    geo-rep: Fix issues with gfid conflict handling
    
    1. MKDIR/RMDIR is recorded on all bricks. So if
       one brick succeeds creating it, other bricks
       should ignore it. But this was not happening.
       The fix rename of directories in hybrid crawl,
       was trying to rename the directory to itself
       and in the process crashing with ENOENT if the
       directory is removed.
    
    2. If file is created, deleted and a directory is
       created with same name, it was failing to sync.
       Again the issue is around the fix for rename
       of directories in hybrid crawl. Fixed the same.
    
       If the same case was done with hardlink present
       for the file, it was failing. This patch fixes
       that too.
    
    fixes: bz#1598884
    Change-Id: I6f3bca44e194e415a3d4de3b9d03cc8976439284
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit ea4964df6f173b17eaf4e9048f55cfe969907663
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Sun Jul 15 12:20:04 2018 +0300

    glusterd-quota.c: fix coverity warning (BAD_COMPARE)
    
    See https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-07-13-1718f9c6/html/1/6glusterd-quota.c.html#error
    Only compile tested!
    
    Change-Id: Ief42f9fcdb02ad001bd39c4a6e27e7fa86fd2496
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 1ee1666df5a5f30075536c6816582bbdad229f27
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Jul 14 18:01:30 2018 +0530

    performance/read-ahead: stricter adherence to force-atime-update
    
    Throwaway read-ahead cache in fstat only if force-atime-update is
    set. Note that fstat flushes read-ahead cache only for atime
    consistency. However if atime consistency is needed user is required
    to set force-atime-update which updates atime on backend fs even
    though application reads are served from read-ahead cache. So, if user
    has not set force-atime-update, atime won't be accurate and there is
    no point in flushing read-ahead cache in fstats. mounts
    requiring atime consistency have to mandatorily set
    force-atime-update.
    
    Also note that normally kernel interspers reads with fstat. So,
    read-ahead is not effective as fstats flush read-ahead-cache. Instead
    it regresses performance due to wasted network reads. It is
    recommended to turn off read-ahead if applications require atime
    consistency.
    
    This patch is aimed at applications which don't require atime
    consistency. Without atime consistency required, read-ahead cache is
    effective and increases performance of sequential reads.
    
    Change-Id: I122bbc410cee96661823f9c4b934383495c18446
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1601166

commit 1dd71ff8addf93dcde66a4e84916e90dbf3cad07
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Jul 5 15:55:48 2018 +0530

    extras: Remove the prot_filter.py code
    
    This code was meant to work with the protection xlator which was removed
    in Nov 2016. Unfortunately, this file remained and should be removed as
    well.
    
    Change-Id: Ia6daa06542ebc8c6fb935c352cc19924f3bb3d8a
    Fixes: bz#1598390
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit 9ab218be5e69b9f71fe4eea9ca8d114b78cafd25
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat Jul 14 10:05:41 2018 +0530

    posix: check before removing stale symlink
    
    BZ 1564071 complains of directories with missing gfid symlinks and
    corresponding "Found stale gfid handle" messages in the logs. Hence
    add a check to see if the symlink points to an actual directory before
    removing it.
    
    Note: Removing stale symlinks was added via commit
    3e9a9c029fac359477fb26d9cc7803749ba038b2
    
    Change-Id: I5d91fab8e5f3a621a9ecad4a1f9c898a3c2d346a
    Updates: bz#1564071
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 730542a5d8c3d9be2202d3c26e9ff5c9404e3fe2
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Jul 18 22:09:19 2018 +0530

    cluster/dht: Set loc->gfid before healing attr
    
    AFR takes inodelks when setting attrs. The loc->gfid
    and loc->inode->gfid were both null when dht_dir_attr_heal
    was called during a fresh lookup of an existing directory.
    As the gfid is null, client_pre_inodelk asserts in the gfid
    check.
    We now set the loc->gfid before calling dht_dir_attr_heal.
    
    Change-Id: I457f5a73fd301d97a03ca032587e73d4803298ac
    fixes: bz#1602866
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit ec0d7d77de3e4bd485a4fa2e53c9137e25c71ce7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Jul 17 20:35:42 2018 +0530

    afr: switch lk_owner only when pre-op succeeds
    
    Problem:
    In a disk full scenario, we take a failure path in afr_transaction_perform_fop()
    and go to unlock phase. But we change the lk-owner before that, causing unlock
    to fail. When mount issues another fop that takes locks on that file, it hangs.
    
    Fix:
    Change lk-owner only when we are about to perform the fop phase.
    Also fix the same issue for arbiters when afr_txn_arbitrate_fop() fails the fop.
    
    Also removed the DISK_SPACE_CHECK_AND_GOTO in posix_xattrop. Otherwise truncate
    to zero will fail pre-op phase with ENOSPC when the user is actually trying to
    freee up space.
    
    Change-Id: Ic4c8a596b4cdf4a7fc189bf00b561113cf114353
    fixes: bz#1602236
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit a75a419d39cd2e2907bcc6eed5b9a4a30a8a3f4d
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Jul 16 15:59:36 2018 +0530

    glusterd: memory leak in get-state
    
    Problem: gluster get-state command is leaking the memory when
    geo-replication session is configured.
    
    Cause: In glusterd_print_gsync_status(), we are trying to get
    reference to the keys of gsync_dict. The references to keys of
    gsync_dict are stored status_vols[i]. status_vols[i] are
    allocated with a memory of size of gf_gsync_status_t.
    
    Solution: Need not to use a array of pointers(status_vals), using
    a pointer to hold the reference to a key of gsync_dict is sufficient.
    
    Followed the below steps for testing:
    1. Configured geo-rep session
    2. Ran gluster get-state command for 1000 times.
    
    Without this patch, glusterd's memory was increasing significantly
    (around 22000KB per 1000 times), with this patch it reduced (1500KB
    per 1000 times)
    
    fixes: bz#1601423
    Change-Id: I361f5525d71f821bb345419ccfdc20ca288ca292
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit e4f6d887527a37eed34eea0fb9a3d68957a44e34
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jul 17 07:32:31 2018 -0400

    build/core: location of xattr.h
    
    starting with libattr-devel-2.4.48-1 in Fedora 28 <attr/xattr.h> has
    been removed from the package.
    
    On Fedora, RHEL/CentOS, and SUSE, the glibc-headers package has provided
    a near identical file, <sys/xattr.h>, in all the releases that we care
    about.
    
    On Debian, libc6-dev provides <sys/xattr.h> all the way back to 8/Jessie
    and presumably all Ubuntu derivatives since then.
    
    Note that on Debian the sys headers are installed in
    /usr/include/$DEB_HOST_GNU_TYPE/sys/...
    
    Change-Id: Id07c4b225bdaa6556bd54772604e75b8f346fb60
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit c63979fdd8589483f242a8f450a130d269e907ed
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Mon Jul 16 16:39:02 2018 +0800

    dht: remove useless argument from dht_iatt_merge
    
    The last using of the subvol argument has been removed at 4e1ec35ef4f7
    ("core: fill 'ia_ino' from 'ia_gfid' in 'storage/posix' ......")
    7 years ago (2011-06-16).
    
    Change-Id: I9788d79e2e40cc153cf2960e28c7c1c1033dc8f7
    fixes: bz#1601683
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 6857d80a50823f5bd1be495edf6899d9bcba9f20
Author: dkhandel <dkhandel@localhost.localdomain>
Date:   Mon Jul 9 19:46:40 2018 +0530

    Add the tab space in the list of BROKEN_TESTS environment variable
    
    Fixes: bz#1598325
    
    Change-Id: I4c14514d33288fd33cca903853c6d5e4f70bd441
    Signed-off-by: Deepshikha Khandelwal <dkhandel@redhat.com>

commit de02b57442117c5410df8186c87abe5965a6bb5f
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Jul 16 15:23:52 2018 +0530

    dht: delete tier related internal xattr in dht_getxattr_cbk
    
    Use dict_del instead of GF_REMOVE_INTERNAL_XATTR.
    
    For problem and fix related information see here -
    https://review.gluster.org/20450.
    
    This patch have some modification as requested by reviewers on already
    merged patch :  https://review.gluster.org/20450.
    
    Change-Id: I50c263e3411354bb9c1e028b64b9ebfd755dfe37
    fixes: bz#1597563
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit b9a5d85d15ed82477a2491e55d6322e3d0d3d29a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Jul 15 19:42:55 2018 +0530

    run-tests.sh: provide option to write 'failure' output to a file
    
    Change-Id: I42f5e0f3513ba758a09b1a7330e49fc3c8fc218e
    updates: bz#1600963
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 19e646f0b6a781334cf1e29c23dd400d790b3be2
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Thu Jul 12 14:02:03 2018 +0530

    core: dereference check on the variables in glusterfs_handle_brick_status
    
    problem: In a race condition, the active->first which is supposed to be filled
    is NULL and trying to dereference it crashs.
    
    back trace:
    Core was generated by `/usr/sbin/glusterfsd -s bxts470192.eu.rabonet.com --volfile-id prod_xvavol.bxts'.
    Program terminated with signal 11, Segmentation fault.
    1029            any = active->first;
    (gdb) bt
    
    Change-Id: Ia6291865319a9456b8b01a5251be2679c4985b7c
    fixes: bz#1600451
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit 475826671a4bce7dada95e04cd9466d431e444e5
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Jul 9 13:32:26 2018 +0300

    tier: Move time string formatting
    
    There is no need to format the time, unless ret is true.
    
    I don't think there's a reason to allocate memory for
    those struct and char array unless we are formatting
    either (But I'm not sure what the code convention is - are we
    ok with 'local' variable declarations?)
    
    Only compile-tested.
    
    Change-Id: I9feb09871943764bd76bdfc9ac6ca506f329aac1
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit c02a25515aba085c7dfa2033f830760e7458301d
Author: Yaniv Kaul <ykaul@redhat.com>
Date:   Mon Jul 16 11:25:41 2018 +0300

    glusterd-store: fix coverity warning
    
    The same variable 'len' was used both in the macros and the functions.
    (Introduced as part of commit 6dc5dfef819cad69d6d4b4c1c305efa74236ad84 ?)
    
    Change-Id: If434999d6470067f8a1e501c8e132561e8cd81ef
    updates: bz#1193929
    Signed-off-by: Yaniv Kaul <ykaul@redhat.com>

commit 42cf8a5f9218fd9e644d901dc53108daa183be5c
Author: Nigel Babu <nigelb@redhat.com>
Date:   Mon Jul 16 15:06:00 2018 +0530

    testing: Fix the build environment
    
    The build environment for FB is vastly different from us. This change
    will match the config to what we use for our regression testing
    
    Change-Id: Ib3584a02dbffb75892f2cbeebcbf51cc3aff3eb6
    Fixes: bz#1601390
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit 762dff25c46e3be3b0e72bbdb63670edd5e96f17
Author: karthik-us <ksubrahm@redhat.com>
Date:   Tue Jun 5 15:57:16 2018 +0530

    cluster/afr: Mark dirty for entry transactions for quorum failures
    
    Problem:
    If an entry creation transaction fails on quprum number of bricks
    it might end up setting the pending changelogs on the file itself
    on the brick where it got created. But the parent does not have
    any entry pending marker set. This will lead to the entry not
    getting healed by the self heal daemon automatically.
    
    Fix:
    For entry transactions mark dirty on the parent if it fails on
    quorum number of bricks, so that the heal can do conservative
    merge and entry gets healed by shd.
    
    Change-Id: I56448932dd409b3ddb095e2ae32e037b6157a607
    fixes: bz#1586020
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 7dd08a4dd056f8b721d56012769cf299cd1afb53
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Jul 3 13:58:23 2018 +0530

    dht: delete tier related internal xattr in dht_getxattr_cbk
    
    Problem :  Hot and Cold tier brick changelogs report rsync failure
    
    Solution : georep session is failing to sync directory
               from master volume to slave volume due to lot
               of changelog retries, solution would be to ignore tier
               related internal xattrs trusted.tier.fix.layout.complete and
               trusted.tier.tier-dht.commithash in dht_getxattr_cbk.
    
    Change-Id: I3530ffe7c4157584b439486f33ecd82ed8d66aee
    fixes: bz#1597563
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 6c2deb080aa2df73d3cb2a5f330208d30e9c6759
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 13 14:45:31 2018 +0530

    logging: check for fmts not being NULL
    
    this fix is just a review of possible SIGSEGV issues in line 714
    as per crash report at the bug:
    
    ```
    08:35:25 Program terminated with signal 11, Segmentation fault.
    08:35:25 #0  0x00007f4ebb491c5c in gf_time_fmt (dst=0x7f4eb1ff9a90 "", sz_dst=256, utime=1531470915, fmt=0)
    at /home/jenkins/root/workspace/centos7-regression/libglusterfs/src/common-utils.h:714
    ```
    
    fixes: bz#1600878
    Change-Id: I160c391f8ac1a3456e59103d293b24e0e3fae718
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c688bc0197940f47bd180e2c2ab9740e3e14b71c
Author: Vitaly Lipatov <lav@etersoft.ru>
Date:   Thu Jul 12 22:02:18 2018 +0300

    add check if no matching password record was found with getpwuid_r(uid)
    
    Change-Id: Iae712828ee656008faf5fe2bc4e6f96fa12ea4cb
    fixes: bz#1600687
    Signed-off-by: Vitaly Lipatov <lav@etersoft.ru>

commit 1718f9c6cb3bc856265ff996babef97119a716bd
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Tue Jul 10 14:21:35 2018 +0530

    glusterd: To find a compatible brick ignore diagnostics.brick-log-level option
    
    Problem: glusterd start a volume as a separate process instead of
             attaching with the already running process if volume option has
             different brick-log-level. There is no functionality impact on a brick
             if the option has different brick-log-level so glusterd
             should attach a brick with the already running process.
    
    Solution: Ignore brick-log-level option in unsafe_option
    
    BUG: 1599628
    Change-Id: I72638ff2026fcd9332bc38e1144b1ef4a708820b
    fixes: bz#1599628
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit e8cf52f5107af00b5dcbde3bff22a394efba5372
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 13 13:52:12 2018 +0530

    tests/geo-rep: increase the timeout
    
    since some time, geo-rep tests were in the border of 180-190 seconds to
    complete. As actual test timeout is 200 seconds by default, giving
    these tests some buffer time to complete properly.
    
    updates: bz#1193929
    Change-Id: I9f501a02b52585dff7d0473824bdbb229e124278
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e2c9d0d182bf8e16fc5277bb32118d13e6065d9a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jul 2 13:29:53 2018 -0400

    tests/geo-rep: Add rsnapshot and hardlink rename test case
    
    1. rsnapshot creates a I/O pattern which involves
       create, rename, symlink, hardlink in specific
       order.
    
    2. Hardlink rename on master with source unlinked use case
    
    fixes: bz#1597540
    Change-Id: Iedade47e5bf9905424a974df6ec33bc6f6695082
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit d2fb898e9d0ce4c18e189f598416eaa58ab68d5b
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Tue May 22 14:43:12 2018 +0530

    Quota: Fix crawling of files
    
    Problem: Running "find ." does not crawl files. It goes over the
    directories and lists all dentries with getdents system call.
    Hence the files are not looked up.
    
    Solution:
    explicitly triggerr stat on files with find . -exec stat {} \;
    since crawl can take slightly longer, updating timeout in test case
    
    Change-Id: If3c1fba2ed8e300c9cc08c1b5c1ba93cb8e4d6b6
    fixes: bz#1533000
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>

commit 271510b09d0613887f983b1e3dad5c55cdc6cd07
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sat Jul 7 08:58:08 2018 -0400

    geo-rep/scheduler: Fix EBUSY trace back
    
    Fix the trace back during temporary mount
    cleanup. Temporary mount is done to touch
    the root required for checkpoint to complete.
    
    fixes: bz#1598977
    Change-Id: I97fea538e92c4ef0747747e981ef98499504e336
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit fc8046894e688b0cb6185f6f32cdb6df942bb490
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jul 12 04:31:01 2018 -0400

    geo-rep: Fix symlink rename syncing issue
    
    Problem:
       Geo-rep sometimes fails to sync the rename of symlink
    if the I/O is as follows
    
      1. touch file1
      2. ln -s "./file1" sym_400
      3. mv sym_400 renamed_sym_400
      4. mkdir sym_400
    
     The file 'renamed_sym_400' failed to sync to slave
    
    Cause:
      Assume there are three distribute subvolume (brick1, brick2, brick3).
      The changelogs are recorded as follows for above I/O pattern.
      Note that the MKDIR is recorded on all bricks.
    
      1. brick1:
         -------
    
         CREATE file1
         SYMLINK sym_400
         RENAME sym_400 renamed_sym_400
         MKDIR sym_400
    
      2. brick2:
         -------
    
         MKDIR sym_400
    
      3. brick3:
         -------
    
         MKDIR sym_400
    
      The operations on 'brick1' should be processed sequentially. But
      since MKDIR is recorded on all the bricks, The brick 'brick2/brick3'
      processed MKDIR first before 'brick1' causing out of order syncing
      and created directory sym_400 first.
    
      Now 'brick1' processed it's changelog.
    
         CREATE file1 -> succeeds
         SYMLINK sym_400 -> No longer present in master. Ignored
         RENAME sym_400 renamed_sym_400
                While processing RENAME, if source('sym_400') doesn't
                present, destination('renamed_sym_400') is created. But
                geo-rep stats the name 'sym_400' to confirm source file's
                presence. In this race, since source name 'sym_400' is
                present as directory, it doesn't create destination.
                Hence RENAME is ignored.
    
    Fix:
      The fix is not rely only on stat of source name during RENAME.
      It should stat the name and if the name is present, gfid should
      be same. Only then it can conclude the presence of source.
    
    fixes: bz#1600405
    Change-Id: I9fbec4f13ca6a182798a7f81b356fe2003aff969
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 970ea7a91946be6a8c941b0ebafd34fdb7ca4f44
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jul 9 10:01:06 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/,
        https://review.gluster.org/#/c/20207/,
        https://review.gluster.org/#/c/20227/,
        https://review.gluster.org/#/c/20307/,
        https://review.gluster.org/#/c/20320/,
        https://review.gluster.org/#/c/20332/,
        https://review.gluster.org/#/c/20364/, and
        https://review.gluster.org/#/c/20441/
    
    Fixes some overlooked string.join()s:
    + AFAICT extras/profiler/glusterfs-profiler, extras/prot_filter.py,
    extras/rebalance.py, and extras/volfilter.py would only manifest at
    runtime.
    + xlators/experimental/fdl/src/gen_recon.py is a build-time error when
    using python3 during the build, thus was not noticed previously when
    building with python2.
    + extras/create_new_xlator/generate_xlator.py seems to be example code
    and does not affect the build or runtime AFAICT
    
    Note: Fedora packaging guidelines and SUSE rpmlint require explicit
    shebangs; popular practices like #!/usr/bin/env python and #!/usr/bin/python
    are not allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, has_key, idioms, map, numliterals, raise,
    set_literal, types, urllib, and zip have already been applied. Also
    version agnostic imports for urllib, cpickle, socketserver, _thread,
    queue, etc., suggested by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, imports2, input, intern,
    itertools, metaclass, methodattrs, ne, next, nonzero, operator, paren,
    raw_input, reduce, reload, renames, repr, standarderror, sys_exc, throw,
    tuple_params, xreadlines.
    
    Change-Id: Ia1fe2958d136f4303e30f7e7e86b6fe7d7b52c81
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit b32ad78516a4edf59a4e9c3ef266e3d69f616b83
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Jul 3 16:03:35 2018 +0530

    snapshot : remove stale entry
    
            During snap delete after removing brick-path we should remove
            snap-path too i.e. /var/run/gluster/snaps/<snap-name>.
    
            During snap deactivate also we should remove snap-path.
    
    Change-Id: Ib80b5d8844d6479d31beafa732e5671b0322248b
    fixes: bz#1597662
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit e893eb1b23f62477e98e409eaf96941beeb27177
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jul 10 20:56:08 2018 +0530

    glusterd: _is_prefix should handle 0-length paths
    
    If one of the paths given to _is_prefix is 0-length, then it is not a
    prefix of the other. Hence, _is_prefix should return false.
    
    Change-Id: I54aa577a64a58940ec91872d0d74dc19cff9106d
    fixes: bz#1599783
    Signed-off-by: Kaushal M <kaushal@redhat.com>

commit 2e18269a80f5f0f0d8d28813aaf216cdb4477a9a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jul 10 21:33:41 2018 +0530

    glusterd: log improvements on brick creation validation
    
    Added few log entries in glusterd_is_brickpath_available ().
    
    Change-Id: I8b758578f9db90d2974f7c79126c50ad3a001d71
    Updates: bz#1193929
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 69f77d28c3ecacba77fbae2f789b5110641347f3
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Jun 27 14:59:40 2018 +0530

    md-cache: Do not invalidate cache post set/remove xattr
    
    Since setxattr and removexattr fops cbk do not carry poststat,
    the stat cache was being invalidated in setxatr/remoxattr cbk.
    Hence the further lookup wouldn't be served from cache.
    To prevent this invalidation, md-cache is modified to get
    the poststat in set/removexattr_cbk in dict.
    
    Co-authored with Xavi Hernandez.
    
    Change-Id: I6b946be2d20b807e2578825743c25ba5927a60b4
    fixes: bz#1586018
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit af6c6429f9743f287baaad68f8e3d56ed7390d1b
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Jul 6 16:10:40 2018 +0530

    server: Set ssl-allow option in options table and rename ID
    
    This change explicitly adds 'ssl-allow' options to the server xlator's
    options table so that glusterd2 can see it as a settable option. This
    change also marks 'auth.allow' and 'auth.reject' options as a settable.
    
    Glusterd2 doesn't maintain a separate volume options table. Glusterd2
    dynamically loads shared objects of xlators to read their option table
    and other information. Glusterd2 reads 'xlator_api_t' if available. If
    that's not available, it falls back to reading just the options table
    directly.
    
    In glusterd2, volume set operations are performed by users on keys of
    the format <xlator>.<option-name>. Glusterd2 uses xlator name set in
    'xlator_api_t.identifier'. If that's not present it will use the shared
    object's file name as xlator name. Hence, it is important for
    'xlator_api_t.identifier' to be set properly, and in this case, the
    proper value is "server". This name shall be used by users as prefix
    while setting volume options implemented in server xlator. The name will
    also be used in volfile.
    
    A user in glusterd2 can authorize a client over TLS as follows:
    
    $ glustercli volume set <volname> server.ssl-allow <client1-CN>[,<clientN-CN>]
    
    gd2 References:
    https://github.com/gluster/glusterd2/issues/971
    https://github.com/gluster/glusterd2/issues/214
    https://github.com/gluster/glusterd2/pull/967
    
    Updates: bz#1193929
    Change-Id: I59ef58acb8d51917e6365a83be03e79ae7c5ad17
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit e57cbae0bcc3d8649b869eda5ec20f3c6a6d34f0
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu May 31 12:29:35 2018 +0530

    dht: Inconsistent permission for directories after brick stop/start
    
    Problem: Inconsistent access permissions on directories after
             bringing back the down sub-volumes, in case of directories dht_setattr
             first wind a call on MDS once call is finished on MDS then wind a call
             on NON-MDS.At the time of revalidating dht just compare the uid/gid with
             stbuf uid/gid and if anyone differs set a flag to heal the same.
    
    Solution: Add a condition to compare permission also in dht_revalidate_cbk
              to set a flag to call dht_dir_attr_heal.
    
    BUG: 1584517
    Change-Id: I3e039607148005015b5d93364536158380d4c5aa
    fixes: bz#1584517
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit e31c7a7c0c1ea3f6e931935226fb976a92779ba7
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Thu Jul 5 15:02:06 2018 +0530

    changelog: fix br-state-check.t crash for brick_mux
    
    Problem: br-state-check.t is getting crash
    
    Solution: Check condition in rpcsvc_request_create
              before allocate memory from rxpool
    
    BUG: 1597776
    Change-Id: I4fde1ade6073f603c32453f1840395db9a9155b7
    fixes: bz#1597776
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit f4497ee445213650df3509f2d0b682a6455d7305
Author: Josiah <josiahp@gmail.com>
Date:   Fri Jun 29 14:14:36 2018 -0500

    Update mount-shared-storage.sh to automatically include all enabled glusterfs mounts in fstab
    
    Currently the mount-shared-storage.sh script requires manual entry of each volume and mount point. There is a TODO item from Bug 1452527 to automatically pull the list of glusterfs mounts from the /etc/fstab file, validate that they are mounted, or attempt to mount them. This is to complete that TODO item.
    
    The extras/mount-shared-storage.sh file has been updated to read only active glusterfs mounts from the /etc/fstab file, verify if they are mounted, and attemt to mount them if they are not. It will exit with a status 0 if successfully mounted or status 1 if any of the mounts fail.
    
    This method will allow the standard method of mounts in /etc/fstab to be utilized and will ensure they are monted following system reboots.
    
    This can be tested by creating a volume, mounting it using the /etc/fstab method, and rebooting the server. Output will be similar to this:
    Jun 29 19:09:38 localhost systemd[1]: Starting Mount glusterfs sharedstorage...
    Jun 29 19:09:43 localhost mount-shared-storage.sh[4096]: /mnt/mount1 has been mounted
    Jun 29 19:09:48 localhost mount-shared-storage.sh[4096]: /mnt/mount2 has been mounted
    Jun 29 19:09:48 localhost systemd[1]: Started Mount glusterfs sharedstorage.
    
    Multiple fixes based on code review suggestions and spellcheck
    
    Removed spaces in grep for glusterfs as tabs are valid as well
    
    Added tab as an IFS field separator for the lines read from /etc/fstab
    
    Increased sleep time to 10 seconds before mount validation
    
    Changed mount check to use “mountpoint -q”
    
    Change-Id: Ib90c99ced8f7aefc8dbe87340afc73a28f6195e7
    fixes: bz#1596789
    Signed-off-by: Josiah <josiahp@gmail.com>

commit 6dc5dfef819cad69d6d4b4c1c305efa74236ad84
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Jul 6 20:23:35 2018 +0200

    Fix compile warnings
    
    This patch fixes compile warnings that appear with newer compilers. The
    solution applied is only to remove the warnings, but it doesn't always
    solve the problem in the best way. It assumes that the problem will never
    happen, as the previous code assumed.
    
    Change-Id: I6e8470d6c2e2dbd3bd7d324b5fd2f92ffdc3d6ec
    updates: bz#1193929
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 03f1f5bdc46076178f1afdf8e2a76c5b973fe11f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jul 6 12:28:53 2018 +0530

    cluster/afr: Prevent execution of code after call_count decrementing
    
    Problem:
    When call_count is decremented by one thread, another thread can
    go ahead with the operation leading to undefined behavior for the
    thread executing statements after decrementing call count.
    
    Fix:
    Do the operations necessary before decrementing call count.
    
    fixes bz#1598663
    Change-Id: Icc90cd92ac16e5fbdfe534d9f0a61312943393fe
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 886ee4dfacdbdff68f7cf5d4938fdf1c81b98e03
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Jul 6 23:26:41 2018 +0200

    posix: Do not log ENXIO errors for seek fop
    
    When lseek is used with SEEK_DATA and SEEK_HOLE, it's expected that the
    last operation fails with ENXIO when offset is beyond the end of file.
    In this case it doesn't make sense to report this as an error log message.
    
    This patch reports ENXIO failure messages for seek fops in debug level
    instead of error level.
    
    Change-Id: I62a4f61f99b0e4d7ea6a2cdcd40afe15072794ac
    fixes: bz#1598926
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit c30283fd2786dc24b6adf5aff8d39e24730b1a11
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Jul 5 14:44:04 2018 -0400

    io-stats: Terminate dump thread when dump interval is set to 0
    
    _ios_dump_thread is not terminated by the function
    _ios_destroy_dump_thread when the diagnostic interval is set
    to 0 (which means disable auto dumping).
    
    During reconfigure, if the value changes from 0 to another
    then the thread is started, but on reconfiguring this to 0
    the thread is not being terminated.
    
    Further, if the value is changed from 0 to X to 0 to Y, where
    X and Y are 2 arbitrary duration numbers, the reconfigure
    code ends up starting one more thread (for each change from
    0 to a valid interval).
    
    This patch fixes the same by terminating the thread when the
    value changes from non-zero to 0.
    
    NOTE: It would seem nicer to use conf->dump_thread and check
    its value for thread presence etc. but there is no documented
    invalid value for the same, and hence an invalid check is not
    feasible, thus introducing a new running bool to determine the
    same.
    
    Fixes: bz#1598548
    Change-Id: I3e7d2ce8f033879542932ac730d57bfcaf14af73
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 16f02433df9e37e28783309060f469d2e50024ee
Author: Mohit Agrawal <moagrawal@redhat.com>
Date:   Mon Jul 9 14:22:27 2018 +0530

    core: Increase SCRIPT_TIMEOUT for bug-1432542-mpx-restart-crash.t
    
    BUG: 1599250
    Change-Id: I27bda2a0764580289e7154766e13a0c358cba3a8
    fixes: bz#1599250
    Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>

commit fc06ba7d3583d19b58a21e1022494416e2bfe64f
Author: Nigel Babu <nigelb@redhat.com>
Date:   Tue Jul 3 11:58:26 2018 +0530

    contrib: Remove contrib/ipaddr-py entirely.
    
    This module is no longer being used.
    Fixes: bz#1597512
    
    Change-Id: Ie5faf55c5961d9d7b5082c9c257351af712c41d7
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit 55d1b0531a0b322a1b851fc921fd6fdf25d26331
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jul 2 08:18:54 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/,
        https://review.gluster.org/#/c/20207/,
        https://review.gluster.org/#/c/20227/,
        https://review.gluster.org/#/c/20307/,
        https://review.gluster.org/#/c/20320/,
        https://review.gluster.org/#/c/20332/, and
        https://review.gluster.org/#/c/20364/
    
    Fixes glupy.py python2isms, iteritems -> items, and some overlooked
    print() in georep/peer_mountbroker.in
    
    Note: Fedora packaging guidelines and SUSE rpmlint require explicit
    shebangs; popular practices like #!/usr/bin/env python and #!/usr/bin/python
    are not allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, has_key, idioms, map, numliterals, raise,
    set_literal, types, urllib, and zip have already been applied. Also
    version agnostic imports for urllib, cpickle, socketserver, _thread,
    queue, etc., suggested by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, imports2, input, intern,
    itertools, metaclass, methodattrs, ne, next, nonzero, operator, paren,
    raw_input, reduce, reload, renames, repr, standarderror, sys_exc, throw,
    tuple_params, xreadlines.
    
    Change-Id: Idda031c1ec975417c79323aea33e7b694e752b2a
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit dab12ce093628860bf43c3e0c7eaf9099cf7a78f
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sat Jun 30 19:51:34 2018 +0530

    glusterfs: Brick process is crash at the time of call server_first_lookup
    
    Problem: Brick process is getting crash while executing test case
             tests/bugs/core/bug-1432542-mpx-restart-crash.t
    
    Solution: At the time of initiating connection with brick process by
              client brick process call server_setvolume.If cleanup thread
              has set cleanup_starting flag after check flag by server_setvolume
              then a brick process can crash at the time of calling lookup
              on brick root.To avoid crash check cleanup_starting
              flag before just call server_first_lookup
    
    BUG: 1597627
    Change-Id: I12542c124c76429184df34a04c1eae1a30052ca7
    fixes: bz#1597627
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Note: To test the patch executing test case
          tests/bugs/core/bug-1432542-mpx-restart-crash.t in a loop
          around 100 times

commit 10b0d7300336fbe97bf2341b46203d50958ee5a1
Author: dkhandel <dkhandel@localhost.localdomain>
Date:   Fri Jul 6 11:38:35 2018 +0530

    Replace the BROKEN_TESTS environment variable value
    
    In distributed-testing framework for regression, the value
    of BROKEN_TESTS environment variable needs to be replaced.
    This list of broken tests is different from what we have
    marked as a bad test in our test suites.
    
    Fixes: bz#1598325
    Change-Id: I6a3ca5d9500170201ecaafcd5a96d9df3e46a851
    Signed-off-by: Deepshikha Khandelwal <dkhandel@redhat.com>

commit 340500cc9533cfe9ccae08f049502aefa7534b4c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 3 11:47:31 2018 +0530

    checkpatch.pl: fix the perl warning
    
    Used to get the below warning:
    `
    Running coding guidelines check ...
    Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/^(\+.*(?:do|\))){ <-- HERE / at ./build-aux/checkpatch.pl line 3102.
    `
    
    But as per the recommendation in perl document, we should escape the braces.
    
    While this check should be removed from the codebase when we get the 'codingstandard' automated scripts, we can keep the code warning free at least till then.
    
    updates: bz#1193929
    Change-Id: I236a428174b5d16ca41baa03e96bc7aa26177b5b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 99a1e816ceae107694fa14d755cec91e159f0a2d
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Jul 4 14:45:51 2018 +0530

    glusterd: Fix glusterd crash
    
    Problem: gluster get-state command is crashing glusterd process, when
    geo-replication session is configured.
    
    Cause: Crash is happening due to the double free of memory. In
    glusterd_print_gsync_status_by_vol we are calling dict_unref(), which
    will free all the keys and values in the dictionary. Before calling
    dict_unref(), glusterd_print_gsync_status_by_vol is calling
    glusterd_print_gsync_status(). glusterd_print_gsync_status is freeing
    up values in the dictionary and again when dict_unref() is called, it
    tries to free up the values which are already freed.
    
    Solution: Remove the code which will free the memory in
    glusterd_print_gsync_status function.
    
    Fixes: bz#1598345
    Change-Id: Id3d8aae109f377b462bbbdb96a8e3c5f6b0be752
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 06cdc956096440eebf9984312af7db6f842578fc
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Jul 1 22:47:46 2018 +0530

    protocol/client: handle the fdctx_destroy properly with different versions
    
    while adding the new version of RPC, this part was not handled properly
    
    Updates: bz#1193929
    Change-Id: If4cc4c2db075221b9ed731bacb7cc035f7007c5b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 1d97e06da0225d2097335ae4cdf933f909683bac
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 3 14:14:59 2018 +0530

    glusterd: show brick online after port registration even in brick-mux
    
    Problem:
    With brick-mux even before brick attach is complete on the bricks
    glusterd marks them as online. This can lead to a race where
    scripts that check if the bricks are online to assume that the
    brick is online before it is completely online.
    
    Fix:
    Wait for the callback from the brick before marking the port
    as registered so that volume status will show the correct status
    of the brick.
    
    fixes bz#1597568
    Change-Id: Icd3dc62506af0cf75195e96746695db823312051
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit c6f93e422855f656d3a86461a8458f37ad0103eb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 3 20:38:23 2018 +0530

    cluster/afr: Make sure lk-owner is assigned at the time of lock
    
    Problem:
    In the new eager-lock implementation lk-owner is assigned after the
    'local' is added to the eager-lock list, so there exists a possibility
    of lock being sent even before lk-owner is assigned.
    
    Fix:
    Make sure to assign lk-owner before adding local to eager-lock list
    
    fixes bz#1597805
    Change-Id: I26d1b7bcf3e8b22531f1dc0b952cae2d92889ef2
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit c80075466ddbf25766dbf805cd5161c736190b3e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jul 2 17:21:21 2018 +0530

    stack.h: fix the pass_through logic
    
    while fixing the coverity issues, we made a minor mistake in the
    pass through logic in STACK_WIND macro.
    
    Also, with this patch, made the code common to reduce possible
    future errors creeping in due to missing one place update.
    
    updates: bz#1193929
    Change-Id: I6fcfd156d63b0a7e6208819872e565eacf774150
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 524c869976c837c2ef13b5ef50020e7769188e4d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 2 20:48:22 2018 +0530

    glusterd: Introduce daemon-log-level cluster wide option
    
    This option, applicable to the node level daemons can be very helpful in
    controlling the log level of these services. Please note any daemon
    which is started prior to setting the specific value of this option (if
    not INFO) will need to go through a restart to have this change into
    effect.
    
    Change-Id: I7f6d2620bab2b094c737f5cc816bc093e9c9c4c9
    fixes: bz#1597473
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 362762b35635b6fb5cbd7c394c63c08973ec3993
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 2 16:47:30 2018 +0530

    glusterd: start the services after all the bricks are up
    
    glusterd_svcs_manager () should be called post starting all the volumes
    at one go.
    
    Change-Id: I838cc50c29f3930a483aa9671958cdc186904030
    Fixes: bz#1597247
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit ce69fb659657a6d7ca9f5b44bab282533e3bfd26
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 2 10:39:56 2018 +0530

    afr,ec: Print if the subvolume is up in statedump
    
    fixes bz#1597156
    Change-Id: I323eb9190e40b12df216698dcdba74a6d336beeb
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit a585425aad5f07a406da26ba38c59fa0e5ad3036
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jun 28 15:47:04 2018 +0530

    cli: change volume create syntax of arbiter volume
    
    fixes: bz#1596524
    updates: gluster/glusterd2#515
    Change-Id: I8a46fa2fd1fd2b0e9fbcecd3bb18d348aed9c6a9
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 451fd20fc8be25d8b99d5e8dfcdb43eaa3f94c72
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jun 26 10:40:08 2018 +0530

    storage/posix: Add warning logs on failure
    
    posix_readdirp_fill will fail to update the iatt
    information if posix_handle_path fails.
    There is currently no log message to indicate this making
    debugging difficult.
    
    Change-Id: I6bce360ea7d1696501637433f80e02794fe1368f
    updates: bz#1564071
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 2f9e555f79ce69668950693ed2e09cfafd2b7ec1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jun 29 11:30:37 2018 +0530

    glusterfsd: Do not process GLUSTERD_BRICK_XLATOR_OP if graph is not ready
    
    Problem:
    If glustershd gets restarted by glusterd due to node reboot/volume start force/
    or any thing that changes shd graph (add/remove brick), and index heal
    is launched via CLI, there can be a chance that shd receives this IPC
    before the graph is fully active. Thus when it accesses
    glusterfsd_ctx->active, it crashes.
    
    Fix:
    Since glusterd does not really wait for the daemons it spawned to be
    fully initialized and can send the request as soon as rpc initialization has
    succeeded, we just handle it at shd. If glusterfs_graph_activate() is
    not yet done in shd but glusterd sends GD_OP_HEAL_VOLUME to shd,
    we fail the request.
    
    Change-Id: If6cc07bc5455c4ba03458a36c28b63664496b17d
    fixes: bz#1596513
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 957e2963cfd960caa49edc0e6aba738167b33ec5
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 27 08:26:44 2018 -0400

    tests/geo-rep: Add symlink rename test case
    
    Added a test case of symlink rename and directory
    creation with the name same as original symlink
    file. Also fixed few other issues in geo-rep.rc
    
    fixes: bz#1595726
    Change-Id: I8e6acd3e742f3a0104cd37b87d1c0e0c902679b5
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit b3c2116d99a5c049e4ee0f88f35440258b49496e
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jun 22 10:42:42 2018 +0530

    cluster/dht: Do not try to use up the readdirp buffer
    
    DHT attempts to use up the entire buffer in readdirp before
    unwinding in an attempt to reduce the number of calls.
    However, this has 2 disadvantages:
    1. This can cause a stack overflow when parallel readdir
    is enabled. If the buffer only has a little space,rda can send back
    only one or two entries. If those entries are stripped out by
    dht_readdirp_cbk (linkto files for example) it will once again
    wind down to rda in an attempt to fill the buffer before unwinding to FUSE.
    This process can continue for several iterations, causing the stack
    to grow and eventually overflow, causing the process to crash.
    2. If parallel readdir is disabled, dht could send readdirp
    calls with small buffers to the bricks, thus increasing the
    number of network calls.
    
    We are therefore reverting to the existing behaviour.
    Please note, this only mitigates the stack overflow, it does
    not prevent it from happening. This is still possible if
    a subvol has thousands of linkto files for instance.
    
    Change-Id: I291bc181c5249762d0c4fe27fa4fc2631166adf5
    fixes: bz#1593548
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit c0e66dddcd8964871e0d574f927684ee7e3c4904
Author: Varsha Rao <varao@redhat.com>
Date:   Thu Jun 28 14:28:27 2018 +0530

    xlators/meta: Fix resource_leak
    
    Free priv to fix the resource_leak coverity issue.
    
    Change-Id: Id116bd2f72332d2f665c25c9ae27241286ac570f
    updates: bz#789278
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 25c1c6e9a2aebd1d5bd96b9b67cf9f7dbaa5bb9e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jun 28 10:42:56 2018 +0530

    extras/group : add database workload profile
    
    Running DB workload patterns with all perf xlators enabled as default has
    resulted into some inconsistency issues. Based on the internal testing done by
    Elko Kuric (ekuric@redhat.com) there're certain set of perf xlators which need
    to be turned off to get these types of workload supported by Gluster.
    
    The proposal is to leverage group profile infrastructure to group together all
    those tunables at one place so that users just need to apply the profile to the
    volume to use it for the data base workload.
    
    Credits : Elko Kuric (ekuric@redhat.com)
    
    Change-Id: I8a50e915278ad4085b9aaa3f160a33af7c0b0444
    fixes: bz#1596020
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 762ed20a50aea81dcc905c511cc836ea2ea3a1c3
Author: Varsha Rao <varao@redhat.com>
Date:   Thu Jun 28 15:31:36 2018 +0530

    xlators/features/barrier: Fix RESOURCE_LEAK
    
    Free priv to fix the resource_leak coverity issue.
    
    Change-Id: I1f93f54d7d59eddb0b9523ac2b67ef0b279122bd
    updates: bz#789278
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit e9f3097aad47c679a66991b5cfcb590f0840f5d7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Jun 26 20:46:07 2018 +0530

    tests: remove tarissue.t from BAD_TEST
    
    BZ 1337791 marked this .t as bad based on the tar version being a likely
    suspect. Undoing this to check as it passes on the latest jenkins slaves.
    
    Change-Id: Ia581064a9c620351d3fe7aeef95d2644337952e1
    fixes: bz#1595492
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reported-by: Yaniv Kaul <ykaul@redhat.com>

commit 4c9b59d4997a38929967dc858b6db9e97b860f1d
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Tue Jun 26 17:39:34 2018 +0800

    performance/md-cache: Fix issue on lock being used before init.
    
    lock is used in mdc_xattr_list_populate(), but got init after call. Fix
    this issue by moving initing lock ahead.
    
    Change-Id: I94b08303a8ba74b1e9388f700587a00b7ae3fd78
    fixes: bz#1595174
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 3099d3e6ba81d3e1abf37385b13aabf5837b9c5e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 26 15:58:02 2018 +0530

    storage/posix: Fix posix_symlinks_match()
    
    1) snprintf into linkname_expected should happen with PATH_MAX
    2) comparison should happen with linkname_actual with complete
       string linkname_expected
    
    fixes bz#1595190
    Change-Id: Ic3b3c362dc6c69c046b9a13e031989be47ecff14
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d6cd792af722c795df48eae68806add4c33e18f5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Feb 29 11:49:01 2016 +0100

    tests: check for the availability of netstat
    
    bug-924726.t calls netstat, and tests fail in case netstat is not
    available.
    
    BUG: 1312832
    Change-Id: I3393778e148504326a468744d8a97d28932feed1
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 1f42bdc61dff4fbbb27724134732bc0d931edda5
Author: Thomas Hindoe Paaboel Andersen <phomes@gmail.com>
Date:   Sat Jun 16 08:24:00 2018 +0200

    cloudsync: avoid null pointer deref in error paths
    
    In the case of OOM we would end up dereferencing priv in
    the out label of aws_init(). A similar deref would happen
    if a null priv is passed to aws_reconfigure().
    
    Change-Id: I57c80aad2b52ecb1eda86a0077ed6b46816e5dea
    fixes: bz#1592141
    Signed-off-by: Thomas Hindoe Paaboel Andersen <phomes@gmail.com>

commit 1ced279c2e8ea0b4d1290da629e05c480a18f888
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Fri Jun 8 10:59:56 2018 +0800

    nfs: add missing rpcsvc_program_unregister_rpcbind6
    
    Otherwise, event if nfs.register-with-portmap is disabled, we could
    also use ipv6 to mount nfs through portmap.
    
    Change-Id: I7546e03d942dfaf2252d57e17be9c1cca986a715
    fixes: bz#1593651
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit f9f1d26f93d10c41c40f13ccf9b751acb03f43bd
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 28 03:05:26 2018 -0400

    cluster/dht: Fix rename journal in changelog
    
    With patch [1], renames are journalled only
    on cached subvolume. The dht sends the special
    key on the cached subvolume so that the changelog
    journals the rename. With single distribute
    sub-volume, the key is not being set. This patch
    fixes the same.
    
    [1] https://review.gluster.org/10410
    
    fixes: bz#1583018
    Change-Id: Ic2e35b40535916fa506a714f257ba325e22d0961
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 69b8ade6168d1b5a96323e3b656273375d2aff7b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jun 22 06:19:53 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/,
        https://review.gluster.org/#/c/20207/,
        https://review.gluster.org/#/c/20227/,
        https://review.gluster.org/#/c/20307/,
        https://review.gluster.org/#/c/20320/, and
        https://review.gluster.org/#/c/20332/
    
    This patch fixes the remaining comma white space (ws_comma) as suggested
    by the 2to3 utility. (Earlier attempts to fix all ws_comma in one
    patch did not pass centos regression, hence multiple patches to identify
    the change that causes the failure.)
    
    Note: Fedora packaging guidelines and SUSE rpmlint require explicit
    shebangs; popular practices like #!/usr/bin/env python and #!/usr/bin/python
    are not allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, has_key, idioms, map, numliterals, raise,
    set_literal, types, urllib, and zip have already been applied. Also
    version agnostic imports for urllib, cpickle, socketserver, _thread,
    queue, etc., suggested by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, imports2, input, intern,
    itertools, metaclass, methodattrs, ne, next, nonzero, operator, paren,
    raw_input, reduce, reload, renames, repr, standarderror, sys_exc, throw,
    tuple_params, xreadlines.
    
    Change-Id: If5aca67084a7b1c06966fed35fb35e8bb2f7d67c
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 8a7e70a221778cd54c8bda9d6c2a522511d36ed1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 7 04:11:25 2018 -0400

    geo-rep: Fix geo-rep for older versions of unshare
    
    Geo-rep mounts are private to worker. It uses
    mount namespace using unshare command to achieve
    the same. Well, the unshare command has to support
    '--propagation' option. So geo-rep breaks on the
    systems with older unshare version. The patch
    makes it fall back to lazy umount behaviour if
    the unshare does not support propagation option.
    
    fixes: bz#1589782
    Change-Id: Ia614f068aede288d63ac62fea4461b1865066054
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 4b7707382bc763f089e14334c2b7f3139e186c1f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jun 20 11:38:59 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/,
        https://review.gluster.org/#/c/20207/,
        https://review.gluster.org/#/c/20227/,
        https://review.gluster.org/#/c/20307/, and
        https://review.gluster.org/#/c/20320/
    
    This patch fixes more selected comma white space (ws_comma) as suggested
    by the 2to3 utility. (Earlier attempts to fix all ws_comma in one
    patch did not pass centos regression, hence multiple patches to identify
    the change that causes the failure.)
    
    Note: Fedora packaging guidelines and SUSE rpmlint require explicit
    shebangs; popular practices like #!/usr/bin/env python and #!/usr/bin/python
    are not allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, has_key, idioms, map, numliterals, raise,
    set_literal, types, urllib, and zip have already been applied. Also
    version agnostic imports for urllib, cpickle, socketserver, _thread,
    queue, etc., suggested by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, imports2, input, intern,
    itertools, metaclass, methodattrs, ne, next, nonzero, operator, paren,
    raw_input, reduce, reload, renames, repr, standarderror, sys_exc, throw,
    tuple_params, xreadlines.
    
    Change-Id: I6e5a2408fa1fc81e00e66d6e4a7f9f6fa1d1ed15
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit fe9b72485697a035b3dbb11b83048dd31de5863e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jun 19 10:56:37 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/,
        https://review.gluster.org/#/c/20207/,
        https://review.gluster.org/#/c/20227/, and
        https://review.gluster.org/#/c/20307/
    
    This patch fixes more selected comma white space (ws_comma) as suggested
    by the 2to3 utility.
    
    Note: Fedora packaging guidelines and SUSE rpmlint require explicit
    shebangs, so popular practices like #!/usr/bin/env python and
    or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, has_key, idioms, map, numliterals, raise,
    set_literal, types, urllib, and zip have already been applied. Also
    version agnostic imports for urllib, cpickle, socketserver, _thread,
    queue, etc., suggested by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, imports2, input, intern,
    itertools, metaclass, methodattrs, ne, next, nonzero, operator, paren,
    raw_input, reduce, reload, renames, repr, standarderror, sys_exc, throw,
    tuple_params, xreadlines.
    
    Change-Id: I60932030813484803f73733a9b2b7b23c7a843fd
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 2bab841316025c402b97c877ccc4ee9188c929e0
Author: John Mulligan <jmulligan@redhat.com>
Date:   Wed Jun 20 13:36:13 2018 -0400

    fuse: avoid using the which command
    
    In mount.glusterfs avoid using the which tool as it may not exist
    on minimal system installs. Use the "command -v" builtin as
    it is expected to be more portable.
    Remove a extra semicolon while we're at it.
    
    Change-Id: Ib682ed4955d5bad1beb94b65d10f4c44e9490767
    fixes: bz#1593351
    Signed-off-by: John Mulligan <jmulligan@redhat.com>

commit 869637e8d227dbab5530d01c8d8eeeee329288b4
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Jun 21 10:57:26 2018 +0530

    Add Vijay and Akarsha as peers
    
    Change-Id: I5298af937199aa5c6908aefcd968b2441b5e23d5
    Fixes: bz#1593562
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit a2b65d01f5feb68a3bf56399c7815e5f0a73101f
Author: Michael Adam <obnox@samba.org>
Date:   Tue May 29 11:56:13 2018 +0200

    client: remove the "connecting" state - it's not used
    
    The "connecting" state is not used anywhere really.
    It's only being set and printed. So remove it.
    
    Change-Id: I11fc8b0bdcda5a812d065543aa447d39957d3b38
    fixes: bz#1583583
    Signed-off-by: Michael Adam <obnox@samba.org>

commit 13b5ab49ac8f700eab0f32011e0d42b789ab00ab
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jun 12 19:49:52 2018 +0530

    cluster/dht:  refactor dht_lookup
    
    The dht lookup code is getting difficult to maintain
    due to its size. Refactoring the code will make it
    easier to modify it in future.
    
    Change-Id: Ic7cb5bf4f018504dfaa7f0d48cf42ab0aa34abdd
    updates: bz#1590385
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 234d611160840899bcfd5ab1c17a6253673d38ed
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Jun 20 16:13:00 2018 +0530

    glusterfs: access trusted peer group via remote-host command
    
    Problem: In SSL environment the user is able to access volume
             via remote-host command without adding node in a trusted pool
    
    Solution: Change the list of rpc program in glusterd.c at the
              time of initialization while SSL is enabled
    
    BUG: 1593232
    Change-Id: I987e433b639e68ad17b77b6452df1e22dbe0f199
    fixes: bz#1593232
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 0751039eadb23b8658423477aa81964b339b4f5e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 12 15:47:00 2018 +0530

    features/shard: Perform shards deletion in the background
    
    A synctask is created that would scan the indices from
    .shard/.remove_me, to delete the shards associated with the
    gfid corresponding to the index bname and the rate of deletion
    is controlled by the option features.shard-deletion-rate whose
    default value is 100.
    The task is launched on two accounts:
    1. when shard receives its first-ever lookup on the volume
    2. when a rename or unlink deleted an inode
    
    Change-Id: Ia83117230c9dd7d0d9cae05235644f8475e97bc3
    updates: bz#1568521
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit cc2f2e7bfef6ca47e740c5ee6b4665ec2880f860
Author: dkhandel <dkhandel@localhost.localdomain>
Date:   Tue Jun 19 14:20:26 2018 +0530

    Distributed-testing: Call the correct class i.e. GeneralXMLRPCServer
    
    fixes: bz#1586342
    Change-Id: I7a062d49f2a49ca4848ffd0b8d1e39c8b6b99815
    Signed-off-by: Deepshikha Khandelwal <dkhandel@redhat.com>

commit c097a7894d458e33a41f6db6092677108ef30fec
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 18 13:40:33 2018 -0400

    ctime: Fix self heal of symlink in EC volume
    
    Since IEEE Std 1003.1-2001 does not require any
    association of file times with symbolic links,
    there is no requirement that file times be
    updated by readlink() states [1].
    
    stat on symlink file was generating a readlink
    fop on one of the subvolumes of ec set which
    in turn updates atime on that subvolume. This
    causes mdata xattr to be different across ec
    set and hence self heal fails. So based on [1],
    atime is no longer updated by readlink fop.
    
    [1] http://pubs.opengroup.org/onlinepubs/009695399/functions/readlink.html
    
    fixes: bz#1592509
    Change-Id: I08bd3ca3bdb222bd18160b1aa58fc2f7630c8083
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 841991130c94e3fcf4076917be6da9ce90406932
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 14 01:08:35 2018 -0400

    posix/ctime: Fix differential ctime duing entry operations
    
    We should not be relying on backend file's time attributes
    to load the initial ctime time attribute structure. This
    is incorrect as each replica set would have witnessed the
    file creation at different times.
    
    For new file creation, ctime, atime and mtime should be
    same, hence initiate the ctime structure with the time
    from the frame. But for the files which were created
    before ctime feature is enabled, this is not accurate
    but still fine as the times would get eventually accurate.
    
    fixes: bz#1592275
    Change-Id: I206a469c83ee7b26da2fe096ae7bf8ff5986ad67
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 7a084b1c42bd1ccbf7e9d816e4a7ed79008a4572
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jun 14 12:37:52 2018 +0530

    cluster/dht: Minor code cleanup
    
    Removed extra variable.
    
    Change-Id: If43c47f6630454aeadab357a36d061ec0b53cdb5
    updates: bz#1590385
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit f816a6e838f8c52f1b8317ae6f1a4103f9267ba6
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 18 09:17:26 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/,
        https://review.gluster.org/#/c/20207/, and
        https://review.gluster.org/#/c/20227/
    
    This patch fixes selected comma white space (ws_comma) as suggested
    by the 2to3 utility.
    
    Note: Fedora packaging guidelines and SUSE rpmlint require explicit
    shebangs, so popular practices like #!/usr/bin/env python and
    or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, has_key, idioms, map, numliterals, raise,
    set_literal, types, urllib, and zip have already been applied. Also
    version agnostic imports for urllib, cpickle, socketserver, _thread,
    queue, etc., suggested by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, imports2, input, intern,
    itertools, metaclass, methodattrs, ne, next, nonzero, operator, paren,
    raw_input, reduce, reload, renames, repr, standarderror, sys_exc, throw,
    tuple_params, xreadlines.
    
    Change-Id: I691d7f86279572642902650ed1c24840e3c4b781
    Updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 64d21769eef85e2588cbe9481a389dc4d68a3cb1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Dec 17 13:38:39 2017 +0100

    tests/vagrant: install additional dependencies
    
    The Vagrant box that is used by ./run-tests-in-vagrant.sh does not have
    all recent dependencies installed. By using 'dnf builddep' to install
    the BuildRequires from the generated .spec file, most future problems
    should be prevented.
    
    The tests/basic/afr/split-brain-favorite-child-policy.t script uses the
    'bc' command. This it a run-time dependency for the test, and will not
    be found with 'dnf builddep'.
    
    Change-Id: Ifdbfc4af2997ea27815126766cc093947ddf523f
    BUG: 1526780
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit eb472d82a083883335bc494b87ea175ac43471ff
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 14 12:59:06 2018 +0530

    afr: heal gfids when file is not present on all bricks
    
    commit 20fa80057eb430fd72b4fa31b9b65598b8ec1265 introduced a regression
    wherein if a file is present in only 1 brick of replica *and* doesn't
    have a gfid associated with it, it doesn't get healed upon the next
    lookup from the client. Fix it.
    
    Change-Id: I7d1111dcb45b1b8b8340a7d02558f05df70aa599
    fixes: bz#1591193
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 0f13eed0c1fa74cefed486538b02e0c8a8708456
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu May 17 08:23:33 2018 +0530

    afr: don't update readables if inode refresh failed on all children
    
    Problem:
    If inode refresh failed on all children of afr due to ENOENT (say file
    migrated by dht), it resets the readables to zero. Any inflight txn which
    then later comes on the inode fails with EIO because no readable
    children present for the inode.
    
    Fix:
    Don't update readables when inode refresh fails on *all* children of
    afr. In that way any inflight txns will either proceed with its own inode
    refresh if needed and fail it with the right errno or use the old value
    of readables and continue with the txn.
    
    Also, add quorum checks to the beginning of afr_transaction(). Otherwise, we
    seem to be winding the lock and checking for quorum only in pre-op pahse.
    
    Note: This should ideally fix BZ 1329505 since the stop gap fix for
    it is has been reverted at https://review.gluster.org/#/c/20028.
    
    Change-Id: Ia638c092d8d12dc27afb3cdad133394845061319
    updates: bz#1584483
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 67de708df134cc9f2edf408f2dd9a7ed1a1ef817
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Jun 15 17:01:38 2018 +0530

    performance/quick-read: provide an invalidation based on ctime
    
    Quick-read by default uses mtime to identify changes to file
    data. However there are applications like rsync which explicitly set
    mtime making it unreliable for the purpose of identifying change in
    file content. Since ctime also changes when content of a file changes
    and it cannot be set explicitly, it becomes suitable for identifying
    staleness of cached data. This option makes quick-read to prefer ctime
    over mtime to validate its cache. However, using ctime can result in
    false positives as ctime changes with just attribute changes like
    permission without changes to file data. So, use this option only when
    mtime is not reliable.
    
    credits to Kotresh Hiremath Ravishankar <khiremat@redhat.com> for
    suggestion on using ctime instead of mtime.
    
    Change-Id: Ib3ae39a3252b2876c8ffe81f471d02a87190e9b9
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1591621

commit ce8290db83427535b532c6df72ef07fae89407eb
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 11 03:12:10 2018 -0400

    tests: Enable geo-rep test cases
    
    Fixes: bz#1537602
    Change-Id: I12314262aaa80f8b7818170112529bf62ab93d3f
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 7005b1a336e483ec150c2f924a618dcfe197db0b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jun 12 09:51:44 2018 +0200

    gcron: create the lockfile if it is missing
    
    The lockfile for the job may not exist yet. If that is the case, it
    should be created upon the first time it is accessed.
    
    Change-Id: I4da2b3ecdb79cc63ed82cc7bfa026c8f08d4d043
    Fixes: bz#1590193
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 3808d8d46ad2fab3f30c2c98283a13fc7170d495
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 11 03:06:25 2018 -0400

    tests: Increase timeout for geo-rep testcases
    
    Change-Id: I11715c23fddc1dd218a3ab88a55f1d6355dcfd43
    Updates: bz#1537602
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 26b52694feb04c98e6c9436bcd4e23e1687f0237
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jun 12 09:49:09 2018 +0200

    gcron: catch OSError as well as IOError
    
    In case os.open() fails because the file does not exist, an OSError is
    raised. To prevent the script to abort uncleanly, catch the OSError in
    addition to the IOError.
    
    Change-Id: I48e5b23e17d63639cc33db51b4229249a9887880
    Fixes: bz#1590193
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 6ac82e8306dba6639bb5d4ea5193d5a262ade589
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jun 6 11:57:18 2018 +0200

    MAINTAINERS: remove me from NFS maintainers
    
    My role at Red Hat changed a little and I do not have the time to look
    into gNFS anymore. If needed, I am still around to assist, but the
    initial contacts should be the active maintainers and peers.
    
    Change-Id: I3cbae3c5cbd413abb6f95be238efc685c493c392
    Updates: bz#1193929
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 8353bc096117e446f08c4970b3f7f55d4aa3356c
Author: dkhandel <dkhandel@localhost.localdomain>
Date:   Mon Jun 11 12:49:41 2018 +0530

    Add a command-line argument option to use specific address family
    
    This commit adds option to pass command-line argument to use any of IPv4 or IPv6 address family.
    Also it clean all the logs in the /tmp before running the distributed-test-runner.py
    
    fixes: bz#1586342
    Change-Id: Ie55021389d454a7e3631359cbd6a1504b6661317
    Signed-off-by: dkhandel <dkhandel@redhat.com>

commit 337f5815a4fa9a961c72b249e1d6b1c6907e961d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jun 14 14:46:24 2018 +0530

    protocol/client: Remove code duplication
    
    client_submit_vec_request() which is used by WRITEV, and PUT
    and client_submit_request() used by the rest of the fops have
    almost similar code. However, there have been some more checks
    - such as whether setvolume was successful or not, and one more
    that is send-gid-specific - that have been missed out in the vectored
    version of the function.
    
    This patch fixes this code duplication.
    
    Change-Id: I363a28eeead6219cb1009dc831538153e8bd7d40
    fixes: bz#1591580
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 10581852dfc36eb6ead0784cb2e984cd39ae2b10
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Jun 14 19:58:54 2018 +0530

    glusterd: removing the unnecessary glusterd message
    
    Fixes: bz#1589253
    Change-Id: I5510250a3d094e19e471b3ee47bf13ea9ee8aff5
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 52435b914e8e0e17b47d8679d86e2949d46c9228
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Jun 8 09:43:40 2018 -0400

    features/snapview-server: properly go through the list of snapshots
    
    The comparison code to check whether a glfs instance is valid
    (i.e. whether it corresponds to one in the list of current snapshots)
    was not correct and was not comparing all the snapshots
    
    Change-Id: I87c58edb47bd9ebbb91d805e45df2c4baf2c8118
    fixes: bz#1589842
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 2a3090028abc2bf76991c97b117d9a301de10344
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Jun 13 11:44:55 2018 +0530

    gfapi : Coverity Fixes
    
    *** CID 1391419:  Control flow issues  (DEADCODE)
    glusterfs/api/src/glfs-fops.c: 5224 in glfs_recall_lease_upcall()
    
    *** CID 1391414:  Memory - illegal accesses  (UNINIT)
    glusterfs/glusterfs/api/src/glfs-fops.c: 5137 in glfs_recall_lease_fd()
    
    Fixes: #789278
    Change-Id: Ie16103e7e321724d3cf1bdcb815c2e2467b9a366
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 6ef91480f9e75f63100585bfd19694deb0c2457b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jun 13 12:17:28 2018 +0530

    storage/posix: Handle ENOSPC correctly in zero_fill
    
    Change-Id: Icc521d86cc510f88b67d334b346095713899087a
    fixes: bz#1590710
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 87f392e7fa22c059a95ff58f1653a285afc0f27a
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Jun 8 19:39:58 2018 +0530

    glusterd: Fix for shd not coming up
    
    Problem: After creating and starting n(n is large) distribute-replicated
    volumes using a script, if we create and start (n+1)th distribute-replicate
    volume manually self heal daemon is down.
    
    Solution: In glusterd_proc_stop after giving SIGTERM signal if the
    process is still running, we are giving a SIGKILL. As SIGKILL will
    not perform any cleanup process, we need to remove the pidfile.
    
    Fixes: bz#1589253
    Change-Id: I7c114334eec74c8d0f21b3e45cf7db6b8ef28af1
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 8e63ca9bba888df0965f0beeed51a5336e6cb8cd
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 11 10:55:42 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/,
        https://review.gluster.org/#/c/20104/,
        https://review.gluster.org/#/c/20162/,
        https://review.gluster.org/#/c/20185/, and
        https://review.gluster.org/#/c/20207/
    
    This patch changes uses of has_key() as suggested by the 2to3 utility.
    
    Note: Fedora packaging guidelines require explicit shebangs, so popular
    practices like #!/usr/bin/env python and #!/usr/bin/python are not
    allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, idioms, numliterals, set_literal, types, urllib,
    zip, map, and raise have already been applied. Also version agnostic
    imports for urllib, cpickle, socketserver, _thread, queue, etc., suggested
    by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, imports2, input, intern,
    itertools, metaclass, methodattrs, ne, next, nonzero, operator, paren,
    raw_input, reduce, reload, renames, repr, standarderror, sys_exc, throw,
    tuple_params, xreadlines.
    
    Updates: #411
    
    Change-Id: I79bda20f1583a0a1bb0320667498f4c137de93b3
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 81701e4d92ae7b1d97e5bc955703719f2e9e773a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jun 13 12:26:55 2018 +0530

    storage/posix: Fix excessive logging in WRITE fop path
    
    I was running some write-intensive tests on my volume, and in a matter
    of 2 hrs, the 50GB space in my root partition was exhausted. On inspecting
    further, figured that excessive logging in bricks was the cause -
    specifically in posix write when posix_check_internal_writes() does
    dict_get() without a NULL-check on xdata.
    
    Change-Id: I89de57a3a90ca5c375e5b9477801a9e5ff018bbf
    fixes: bz#1590655
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit c30aca6a5b25223e36b4ea812af544e348952138
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Mar 29 17:21:32 2018 +0530

    features/shard: Introducing ".shard/.remove_me" for atomic shard deletion (part 1)
    
    PROBLEM:
    Shards are deleted synchronously when a sharded file is unlinked or
    when a sharded file participating as the dst in a rename() is going to
    be replaced. The problem with this approach is it makes the operation
    really slow, sometimes causing the application to time out, especially
    with large files.
    
    SOLUTION:
    To make this operation atomic, we introduce a ".remove_me" directory.
    Now renames and unlinks will simply involve two steps:
    1. creating an empty file under .remove_me named after the gfid of the file
    participating in unlink/rename
    2. carrying out the actual rename/unlink
    A synctask is created (more on that in part 2) to scan this directory
    after every unlink/rename operation (or upon a volume mount) and clean
    up all shards associated with it. All of this happens in the background.
    The task takes care to delete the shards associated with the gfid in
    .remove_me only if this gfid doesn't exist in backend, ensuring that the
    file was successfully renamed/unlinked and its shards can be discarded now
    safely.
    
    Change-Id: Ia1d238b721a3e99f951a73abbe199e4245f51a3a
    updates: bz#1568521
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 5702ff3012f6b97f6b497b5c2e89e8700caf8bc1
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Jun 6 12:57:50 2018 +0530

    cluster/dht: Refactor rebalance code
    
    Created init and cleanup functions for certain
    functionality in order to improve readability.
    Removed unused code.
    
    Change-Id: Ia6a2f4ab64923b6ea8e10487227fb5621eec1488
    updates: bz#1586363
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 9647f0c64bfb0af2e4354998d1be672f7101a358
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sat Jun 2 01:38:10 2018 +0530

    glusterd: Coverity Fixes
    
    Fixes: #789278
    Change-Id: I633704fab49992cac6ee9e05bc368f7da360d09e
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit e00d6ba4ad0a0d92907363b56e241b4f515b4dca
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon May 7 17:18:06 2018 +0530

    cluster/dht: Leverage MDS subvol for dht_removexattr also
    
    Problem: In a distributed volume situation can be arise when custom
             extended attributed are not removed from all bricks after
             stop/start or added newly brick.
    
    Solution: To resolve the same use MDS subvol for remove xattr also
    
    BUG: 1575587
    Change-Id: I7701e0d3833e3064274cb269f26061bff9b71f50
    fixes: bz#1575587
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit e86c58b473fe0573f99017ab609bf5e947b6baa4
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon May 21 09:04:57 2018 -0400

    api: cleanup headers
    
    fix inconsistent use in headers of:
      struct glfs and glfs_t
      struct glfs_fd and glfs_fd_t
      struct glfs_object and glfs_object_t
    
    add typedefs to headers for various struct glfs_foos, and use them, e.g.:
      struct glfs_upcall and glfs_upcall_t
    
    fix inconsistent type naming for 'enum glfs_lock_mode_t'. (All other
    enum decls are 'enum glfs_foo' not 'enum_glfs_foo_t'), and add
    typedefs for all enums, and use them.
    
    style, replace tabs with spaces and follow return value style, i.e.:
      int
      pub_glfs_foo()
    instead of:
      int pub_glfs_foo()
    
    Update copyright dates, substantial new work has been done since 2012
    
    Change-Id: I0a9654486ea132efde7977b655799fb37887b1d5
    Updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit fd5b48ea0afd907deb08604415bee14ab65f378b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 11 13:03:58 2018 +0530

    protocol/server: Fix xdata leak in seek fop
    
    Change-Id: I6125283ed22c04564f0b77bb7a50579a83e02eb0
    fixes: bz#1589691
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 319aa4b0754d1f3859b180f9a416be20143d4ec1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 11 02:52:16 2018 -0400

    geo-rep: Fix problems in python2 -> python3 compat
    
    1. Import configparser module correctly
    2. Import thread module correctly
    
    Updates: #411
    Change-Id: I522453d23c256b694fa58d285f413b8c4dd6595c
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit ee75c5abc41f43aa79b5e758e43f70a92672d3a2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 7 12:27:23 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/, and
        https://review.gluster.org/#/c/20104/
        https://review.gluster.org/#/c/20162/
    
    This patch changes uses of map() and raise(), and a few cases of print()
    that were overlooked in the prior patch that fixed print.
    
    Note: Fedora packaging guidelines require explicit shebangs, so popular
    practices like #!/usr/bin/env python and #!/usr/bin/python are not
    allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, idioms, numliterals, set_literal, types, urllib,
    zip, map, and raise have already been applied. Also version agnostic
    imports for urllib, cpickle, socketserver, _thread, queue, etc., suggested
     by Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, intern, itertools, metaclass,
    methodattrs, ne, next, nonzero, operator, paren, raw_input, reduce,
    reload, renames, repr, standarderror, sys_exc, throw, tuple_params,
    xreadlines.
    
    Change-Id: Id62ea491e4ab5dd390075c5c6d9d889cf6f9da27
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit d788cc59b1cd4278ca0b8b2d9f6fe93f80550af3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jun 5 09:49:23 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/,
        https://review.gluster.org/#/c/19952/, and
        https://review.gluster.org/#/c/20104/
    
    This patch changes uses of xrange() to range(), as suggested by the
    python 2to3 utility. https://www.geeksforgeeks.org/range-vs-xrange-python/
    In Python 3, there is no xrange , but the range function behaves like
    xrange in Python 2. (My concern is that range() in python2 may behave
    differently until we "throw the switch" to switch to python3.)
    
    Note: Fedora packaging guidelines require explicit shebangs, so
    popular practices like #!/usr/bin/env python and #!/usr/bin/python
    are not allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, idioms, numliterals, set_literal, types, urllib,
    and zip have already been applied. Also version agnostic imports for
    urllib, cpickle, socketserver, _thread, queue, etc., suggested by
    Aravinda in https://review.gluster.org/#/c/19767/1
    
    Note: these 2to3 fixes report no changes are necessary: asserts, buffer,
    exec, execfile, exitfunc, filter, getcwdu, intern, itertools, metaclass,
    methodattrs, ne, next, nonzero, operator, paren, raw_input, reduce,
    reload, renames, repr, standarderror, sys_exc, throw, tuple_params,
    xreadlines.
    
    Change-Id: I16ae9f4e3a4fd02a0623fb6f9fdb7aaf65f2a8a9
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit fe71ee74fd327f61aedc858699a953a0fe2cd8d4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sat Jun 2 16:36:22 2018 +0530

    glusterd: gluster v status is showing wrong status for glustershd
    
    When we restart the bricks, connect and disconnect events happen
    for glustershd. glusterd use two threads to handle disconnect and
    connects events from glustershd. When we restart the bricks we'll
    get both disconnect and connect events. So both the threads will
    compete for the big lock.
    
    We want disconnect event to finish before connect event. But If
    connect thread gets the big lock first, it sets svc->online to
    true, and then disconnect thread will et svc->online to false.
    So, glustershd will be disconnected from glusterd and wrong status
    is shown.
    
    After killing shd, glusterd sleeps for 1 second. To avoid the problem,
    If glusterd releses the lock before sleep and acquires it after sleep,
    disconnect thread will get a chance to handle the
    glusterd_svc_common_rpc_notify before other thread completes connect
    event.
    
    Change-Id: Ie82e823fdfc936feb7c0ae10599297b050ee9986
    fixes: bz#1585391
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 07ede8d44372eb30cedd21acf87ab605229c39ea
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu May 31 23:00:28 2018 -0700

    mgmt/glusterd: Cleanup dead code
    
    updates: bz#789278
    
    Change-Id: Id67ab681317eb0a69874400a40e3b249dfc7a7db
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 7cdcd9b022180ee279f6408f7daaa882a8266f3a
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 30 08:15:29 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/,
        https://review.gluster.org/#/c/19871/, and
        https://review.gluster.org/#/c/19952/
    
    This patch adds version agnostic imports for urllib, cpickle,
    socketserver, _thread, queue, etc., suggested by Aravinda in
    https://review.gluster.org/#/c/19767/1
    
    Note: Fedora packaging guidelines require explicit shebangs, so
    popular practices like #!/usr/bin/env python and #!/usr/bin/python
    are not allowed; they must be #!/usr/bin/python2 or #!/usr/bin/python3
    
    Note: Selected small fixes from 2to3 utility. Specifically apply,
    basestring, funcattrs, idioms, numliterals, set_literal, types, urllib,
    and zip have already been applied.
    
    Note: these 2to3 fixes report no changes are necessary: exec, execfile,
    exitfunc, filter, getcwdu, intern, itertools, metaclass, methodattrs, ne,
    next, nonzero, operator, paren, raw_input, reduce, reload, renames, repr,
    standarderror, sys_exc, throw, tuple_params, xreadlines.
    
    Change-Id: I8d393064a1837874d8b4bc87c8ce05c679664642
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 3894f4262d53d1c1c593a78b21d72ba1103c86cd
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sun Jun 3 11:24:18 2018 +0530

    rpc/clnt: Don't let consumers manage "connected" state
    
    The state management of "connected" in rpc is ad-hoc as far as the
    responsibility goes. Note that there is nothing wrong with
    functionality itself. rpc layer manages this state in disconnect
    codepath and has exposed an api to manage this one from
    consumers. Note that rpc layer never sets "connected" to true by
    itself, which forces the consumers to use this api to get a working
    rpc connection. The situation is best captured from a comment in code
    from Jeff Darcy in glusterfsd/src/gf-attach.c:
    
    -/*
    - * In a sane world, the generic RPC layer would be capable of tracking
    - * connection status by itself, with no help from us.  It might invoke our
    - * callback if we had registered one, but only to provide information.  Sadly,
    - * we don't live in that world.  Instead, the callback *must* exist and *must*
    - * call rpc_clnt_{set,unset}_connected, because that's the only way those
    - * fields get set (with RPC both above and below us on the stack).  If we don't
    - * do that, then rpc_clnt_submit doesn't think we're connected even when we
    - * are.  It calls the socket code to reconnect, but the socket code tracks this
    - * stuff in a sane way so it knows we're connected and returns EINPROGRESS.
    - * Then we're stuck, connected but unable to use the connection.  To make it
    - * work, we define and register this trivial callback.
    - */
    
    Also, consumers of rpc know about state of connection only through the
    notifications sent by rpc-clnt. So, consumers don't have any extra
    information to manage the state and hence letting them manage the
    state is counter intuitive. This patch cleans that up and instead
    moves the responsibility of state management of rpc layer into
    itself.
    
    Change-Id: I31e641a60795fc480ca753917f4b2579f1e05094
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1585585

commit a6f0e7a4f1ca203762cae2ed5e426b52124c74dc
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Jun 1 01:48:31 2018 -0400

    posix/ctime: Fix fops racing in updating mtime/atime
    
    In distributed systems, there could be races with fops
    updating mtime/atime which could result in different
    mtime/atime for same file. So updating them only if
    time is greater than the existing makes sure, only
    the highest time is retained. If the mtime/atime
    update comes from the explicit utime syscall, it is
    allowed to set to previous time.
    
    Thanks Xavi for helping in rooting the issue.
    
    fixes: bz#1584981
    Change-Id: If1230a75b96d7f9a828795189fcc699049e7826e
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 2c1131e5868e46cfc806fb3a1cb63a5e554b4d6c
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed May 30 15:09:29 2018 +0530

    dht: Delete MDS internal xattr from dict in dht_getxattr_cbk
    
    Problem: At the time of fetching xattr to heal xattr by afr
             it is not able to fetch xattr because posix_getxattr
             has a check to ignore if xattr name is MDS
    
    Solution: To ignore same xattr update a check in dht_getxattr_cbk
              instead of having a check in posix_getxattr
    
    BUG: 1584098
    Change-Id: I86cd2b2ee08488cb6c12f407694219d57c5361dc
    fixes: bz#1584098
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit e3563f6dfda6c3f44ecff52ac22738ff74413ae1
Author: Levi Baber <baber@iastate.edu>
Date:   Thu May 31 15:17:26 2018 -0500

    changed 'sometime' messsages to 'some time'
    
    Change-Id: I0936229fc84c011db7791218bb566c971fdea174
    fixes: bz#1584864
    Signed-off-by: Levi Baber <baber@iastate.edu>

commit b21f742f96d46b4adfa87281dd9a2e48fea8d031
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu May 31 17:11:01 2018 -0700

    features/shard: Fix missing unlock in shard_fsync_shards_cbk()
    
    updates: bz#789278
    
    Change-Id: I745a98e957cf3c6ba69247fcf6b58dd05cf59c3c
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit adb1168f4e06ba19ab0f138b43e289d179ce5d45
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu May 31 15:11:54 2018 -0700

    call-stub: Add a missing break
    
    updates: bz#789278
    
    Change-Id: Id411e69505209c08f33bb77948ee81936dfaef79
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit 74529cf1a133115adedbb2bdeaa0a9e90b773320
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu May 31 16:57:02 2018 +0530

    libgfchangelog: Remove duplicate includedir definition for changelog.h
    
    includedir for changelog.h is already defined in Makefile.am under libglusterfs/src
    since it was moved from xlators/features/changelog/lib/src. Therefore removing the
    duplicate definition.
    
    Change-Id: Iaff2e02fca45715820caa35b41efc2f6b656203a
    updates: bz#1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit be086493c07e190763048f66cdc057bdc61ada00
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu May 31 14:17:39 2018 -0700

    performance/io-cache: fix a missing unlock
    
    Fixes: bz789278
    
    Change-Id: If8ca1fef8a10f1e7270390b61121f8a20a76b1d0
    updates: bz#789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>

commit f1f2bfd7c966c6d1efc5c0397caf056cd38ddbbc
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue May 15 09:22:26 2018 +0530

    glusterd: address test failures with brick mux enabled
    
    This patch addresses following:
    1. On volume stop, for the last brick, pmap_registry_remove () is
    invoked by glusterd.
    2. If a brick process is sigkilled, remove all the associated brick
    instances from the portmap.
    3. Bump up PROCESS_UP_TIMEOUT to 45.
    4. gf_attach to kill a brick takes more time in mux (which is an
    issue that needs a fix), but in the interim, give br-state-check.t
    more time to complete (there are 2 kill_bricks, each taking 120
    seconds, and the test usually passes in 30 odd seconds, hence bumping
    this up to 350 seconds)
    5. The test bug-1559004-EMLINK-handling.t is taking ~950 seconds at
    times on master without mux, in mux cases, when it fails, it is almost
    at the last iteration, hence bumping the timeout for this test case
    to reduce regression error rates
    
    Updates: bz#1577672
    Change-Id: I1922675e112baca4c125c4c094eaa42a11e34e67
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 430e4872db43447c8a15b638760d23c188257139
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 30 09:34:44 2018 +0530

    protocol/client: Don't send fops till SETVOLUME is complete
    
    An earlier commit set conf->connected just after rpc layer sends
    RPC_CLNT_CONNECT event. However, success of socket level connection
    connection doesn't indicate brick stack is ready to receive fops, as
    an handshake has to be done b/w client and server after
    RPC_CLNT_CONNECT event. Any fop sent to brick in the window between,
    * protocol/client receiving RPC_CLNT_CONNECT event
    * protocol/client receiving a successful setvolume response
    
    can end up accessing an uninitialized brick stack. So, set
    conf->connected only after a successful SETVOLUME.
    
    Change-Id: I139a03d2da6b0d95a0d68391fcf54b00e749decf
    fixes: bz#1583937
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 6d569e27c203c4d7abdd14112b1f5f6bac8c94ad
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed May 30 09:36:34 2018 +0530

    cluster:dht: Corrected ret code check
    
    syncop functions return -op_errno.
    
    Change-Id: Ifdb1bd1d1d11972b4306a2336e6737d6236a2fb1
    fixes: bz#1580238
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 202d27c5309f2b5a2c4cda4af2e9a1ec85e1e9ad
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 2 08:48:32 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/ and
        https://review.gluster.org/#/c/19871/
    
    Selected small fixes from 2to3 utility. Specifically apply, basestring,
    funcattrs, idioms, numliterals, set_literal, types, urllib, zip
    
    Note: these 2to3 fixes report no changes are necessary: exec, execfile,
    exitfunc, filter, getcwdu, intern, itertools, metaclass, methodattrs, ne,
    next, nonzero, operator, paren, raw_input, reduce, reload, renames, repr,
    standarderror, sys_exc, throw, tuple_params, xreadlines.
    
    Any 2to3 fixes not in the above two lists have more extensive changes
    which will follow in separate patches.
    
    most unicode changes suggested by 2to3 will need to be applied at the
    same time as changing the shebangs from python2 to python3. Prashanth
    notes that unicode strings in py2 need 'u' prefix; unicode strings in
    py3 3.0, 3.1, and 3.2 a 'u' prefix will throw an error, but in py3 3.3+
    it is legal (or just ignored). All Linux dists we care about have 3.3
    or later so we can leave 'u' prefixes on unicode strings.
    
    Change-Id: I49bba2f328b0ee24b9a8115a7183be979981563e
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 7e72af7657973d508c179922bd29257ff8402bcd
Author: hari gowtham <hgowtham@redhat.com>
Date:   Fri May 18 15:05:37 2018 +0530

    Core: The lock contention on gf_client_dump_inodes_to_dict
    
    Problem: For a distributed replicated volume, in the inode status
    command the lock on gf_client_dump_inodes_to_dict is held by the
    first brickop. while this is being processed, if the second brickop
    comes. It fails to get the lock and the whole brick op fails.
    
    Fix: Instead of using a TRY_LOCK which errors out if the lock is busy,
    Use LOCK which will wait till the lock is acquired.
    
    Change-Id: I768a0a1b60f28c4f7f94549e18ee3765b69cc528
    fixes: bz#1579769
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit 62990c30fcec37f643b7631070de8baba276f0ba
Author: Susant Palai <spalai@redhat.com>
Date:   Tue May 22 19:55:27 2018 +0530

    cloudsync: Adding s3 plugin for cloudsync
    
    This is a plugin which provides an interface to retrive files from amazon-s3
    which are archived in to s3.
    
    Users need to give the above information for cloudsync to retrieve the file
    from s3.
    
    TODO:
    1- A separate commit in to developer-guide will detail about the usage
    of this plugin in more detail.
    2- Need to create target file in aws-bucket with "gfid" names. Helps avoiding
    name collisions.
    
    Change-Id: I2e4a586f4e3f86164de9178e37673a07f317e7d9
    Updates: #387
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit cb4e0fa2cbd25ef4ab5b65c6a76a6aea90c0f835
Author: Susant Palai <spalai@redhat.com>
Date:   Mon May 14 11:13:23 2018 +0530

    feature/cloudsync: Dev guide to write a Cloudsync Plugin
    
    Updates: #387
    Change-Id: I50ef84e5e67a648384394dfad003884d25a4c746
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 95e735b71b077d1ad7fd8c5a7152176968cc6588
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue May 22 15:48:16 2018 +0530

    thin-arbiter : Provide scripts and service file to start thin-arbiter process
    
    1 - setup-thin-arbiter.sh
    To setup directory path for thin-arbiter. This is the path where replica id
    file will be placed and used by TA process.
    By default it will be /mnt/thin-arbiter. It is better to use default path
    and once set it should not be changed.
    
    2 - gluster-ta-volume.service
    This is the Unit file used by systemd to start and keep the thin-arbiter
    process running.
    
    3 - thin-arbiter.vol
    This is the default volume file for thin-arbiter. It will be used to start
    thin-arbiter process. This should not be modified by user except the
    directory path which can be modified using [1].
    
    Change-Id: I68f2164f24adfa326c1d1a7a98c6ac4ff04ed553
    fixes: bz#1579786
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 052fce3f31d856fce10e07eda5f5c49ad3390d3a
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue May 29 14:57:44 2018 +0530

    dht: Excessive 'dict is null' logs in dht_revalidate_cbk
    
    Problem: In case of error(ESTALE/ENOENT) dht_revalidate_cbk
             throws "dict is null" error because xattr is not available
    
    Solution: To avoid the logs update condition in dht_revalidate_cbk
              and dht_lookup_dir_cbk
    
    BUG: 1583565
    Change-Id: Ife6b3eeb6d91bf24403ed3100e237bb5d15b4357
    fixes: bz#1583565
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit df838299a8a1732cff9972c9f2377e9c2a4844a0
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 25 12:27:43 2018 +0530

    performance/open-behind: open pending fds before permission change
    
    setattr, posix-acl and selinux changes on a file can revoke permission
    to open the file after permission changes. To prevent that, make sure
    the pending fd is opened before winding down setattr or setxattr (for
    posix-acl and selinux) calls.
    
    Change-Id: Ib0b91795d286072e445190f9a1b3b1e9cd363282
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    fixes: bz#1405147

commit c8a3e8ed1cce774a63b60b2e793b6742920b8cd1
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Thu Jan 11 12:24:35 2018 +0530

    Quota fsck script
    
    script can be used to for 3 purposes
    1) Extract marker xattr from the  backend with a crawl (for analysis)
    2) Report anomalies in accounting by comparing stat based accounting
    with marker translator's accounting
    3) Fix anomalies in the FS by marking the anamolous directories dirty
    and having them heal in a bottom up fashion over the directory tree.
    
    Change-Id: Ib4d4a6d1886d7332c80d5a93f7afccaa0f52ab58
    fixes: #390
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit 3780f6c2515c34f8705eb0fe25291bb97e73f354
Author: Milind Changire <mchangir@redhat.com>
Date:   Sat May 26 12:36:04 2018 +0530

    rpc: conditionally cleanup event slot
    
    Problem:
    socket_server_event_handler() may call rpc_transport_unref() for a
    socket which may fail registration with the event sub-system.
    This causes an assert to fail in event_unregister_epoll_common()
    
    Solution:
    Conditionally cleanup event slot only if slot index >= 0
    
    Change-Id: I6ca7c133712e894adc335c7763879691b7e4b213
    fixes: bz#1582704
    BUG: 1582704
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 493f5aff9d66a83deb7cf3b3527d0d836fbd12ec
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 25 08:50:19 2018 +0530

    performance/read-ahead: throwaway read-ahead cache of all fds on writes on any fd
    
    This is to make sure applications that read and write on different fds
    of the same file work.
    
    This patch also fixes two other issues:
    1. while iterating over the list of open fds on an inode, initialize
    tmp_file to 0 for each iteration before fd_ctx_get to make sure we
    don't carry over the history from previous iterations.
    2. remove flushing of cache in flush and fsync as by themselves, they
    don't modify the data
    
    Change-Id: Ib9959eb73702a3ebbf90badccaa16b2608050eff
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit d44d531db1045df7b810567b2441e9f6bcc6a5dd
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 25 08:16:41 2018 +0530

    Revert "performance/write-behind: fix flush stuck by former failed writes"
    
    This reverts commit 9340b3c7a6c8556d6f1d4046de0dbd1946a64963.
    
    operations/writes across different fds of the same file cannot be
    considered as independent. For eg., man 2 fsync states,
    
    <man 2 fsync>
    
    fsync()  transfers  ("flushes")  all  modified  in-core  data of
    (i.e., modified buffer cache pages for) the file referred to by the
    file descriptor fd to the disk device
    
    </man>
    
    This means fsync is an operation on file and fd is just a way to reach
    file. So, it has to sync writes done on other fds too. Patch
    9340b3c7a6c, prevents this.
    
    The problem fixed by patch 9340b3c7a6c - a flush on an fd is hung on a
    failed write (held in cache for retrying) on a different fd - is
    solved in this patch by making sure __wb_request_waiting_on considers
    failed writes on any fd as dependent on flush/fsync on any fd (not
    just the fd on which writes happened) opened on the same file. This
    means failed writes on any fd are either synced or thrown away on
    witnessing flush/fsync on any fd of the same file.
    
    Change-Id: Iee748cebb6d2a5b32f9328aff2b5b7cbf6c52c05
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: bz#1512691

commit c54702a34aa1feb86e2f5f2b1b238966a52ae37b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Apr 17 18:10:01 2018 +0530

    glusterd: glusterd is releasing the locks before timeout
    
    Problem: We introduced lock timer in mgmt v3, which will realease
    the lock after 3 minutes from command execution. Some commands related
    to heal/profile will take more time to execute. For these comands
    timeout is set to 10 minutes. As the lock timer is set to 3 minutes
    glusterd is releasing the lock after 3 minutes. That means locks are
    released before the command is completed its execution.
    
    Solution: Pass a timeout parameter from cli to glusterd, when there
    is a change in default timeout value(i.e, default timeout value can
    be changed through command line or for the commands related to profile/heal
    we will change the default timeout value to 10 minutes.) glusterd will
    set the lock timer timeout according to the timeout value passed.
    
    Change-Id: I7b7a9a4f95ed44aca39ef9d9907f546bca99c69d
    fixes: bz#1577731
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit c772f84e2b7925d0bb294877db3f68bd7cdfb1a3
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Nov 1 11:54:27 2016 +0530

    performance/quick-read: Use generation numbers to avoid updating the cache with stale data
    
    Thanks to Pranith for the example. Following is the race we are trying
    to solve with this patch.
    
    1) We have a file with content 'abc'
    2) lookup and writev which replaces 'abc' with 'def' comes. Lookup
       fetches abc but yet to update the cache, and then immediately
       writev is wound which zeros out the cache. Now lookup_cbk updates
       the buffer with 'abc' even though on disk it is 'def'. Now writev
       completes and returns to application.
    3) application does a readv which will be fetched from quick-read as
       'abc'.
    
    Change-Id: I9a9cab9c99652aa6d17230a4fe4dc034ec502b1b
    BUG: 1390050
    Updates: bz#1390050
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 47440dd83592438840d3b2eb27f71403f6fba7b3
Author: Susant Palai <spalai@redhat.com>
Date:   Mon May 21 11:51:47 2018 +0530

    cluster/dht: Increase failure count for lookup failure in remove-brick op
    
    An entry from readdirp might get renamed just before migration leading to
    lookup failures. For such lookup failure, remove-brick process does not
    see any increment in failure count. Though there is a warning message
    after remove-brick commit for the user to check in the decommissioned brick
    for any files those are not migrated, it's better to increase the failure count
    so that user can check in the decommissioned bricks for files before commit.
    
    Note: This can result in false negative cases for rm -rf interaction with
    remove-brick op, where remove-brick shows non-zero failed count, but the
    entry was actually deleted by user.
    
    Fixes :bz#1580269
    Change-Id: Icd1047ab9edc1d5bfc231a1f417a7801c424917c
    fixes: bz#1580269
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 3d38e4e47f129bdb36c3fbbd481dabe4ba4413d6
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri May 25 08:55:11 2018 -0400

    libgfapi: Fix lookup on root
    
    Lookup on root was sending "/" as the path.
    This will break the basename calculation in
    loc_copy and hence lookup on root was failing
    if the loc_copy was involved in the stack.
    
    With ctime, a first lookup on root initiates
    a metadata self heal because of ctime xattr
    not being same on all afr subvolumes. This
    results in loc_copy and hence the failure
    of lookup.
    
    Fix would be to send path with "." for the root.
    
    fixes: bz#1582516
    Change-Id: Iafe4b99f249a4f5034ad34c1d30590de0e35aa0d
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 7d92af4eac386001b46b8f1a98e8ccb95ca1a225
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Feb 16 11:29:12 2018 +0100

    tests: run-tests-in-vagrant.sh should return test status
    
    The ./run-tests-in-vagrant.sh script does not return the correct exit
    status. Even if the tests in the Vagrant VM fail, the script returns
    success. This throws off the expectations that any regular testers (or
    CI) have.
    
    BUG: 1546103
    Change-Id: I7f00903f9fe4ef3be8ba80db0f9aa8d412502b86
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 2343d2ca474f5f695add09f8c039078b378c3985
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu May 17 15:55:44 2018 +0530

    feature/locks: Unwind response based on clinet version
    
    Change-Id: I6fc7755cca0d6f61cb775363618036228925842c
    fixes: bz#1570538
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 1a2b33ac4e21fbe8658031fff8c92f5b4bb1e4af
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon May 21 16:18:53 2018 +0530

    glusterd: memory leak in geo-rep status
    
    Fixes: bz#1580352
    
    Change-Id: I9648e73090f5a2edbac663a6fb49acdb702cdc49
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 78fa818458ba75c12467768069c917d29b4422de
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 25 17:21:58 2018 +0530

    tests/bug-1543279: mark it as bad
    
    There seems to be races which are not fixed by commit
    9704d203f0. Though the test itself is not bad, it is failing very
    frequently. So, till the issue is fixed, marking this test as bad.
    
    updates: bz#1543279
    
    Change-Id: I4a5869da1586178914ffb9563414879e6beab183
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 5055ba5170603cdb2a7f2a884013e49fe36ada5c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 16 13:49:44 2018 +0530

    add COMMITMENT file as part of GPL cure
    
    This is part of more broader commitment Red Hat along with
    IBM, Google, and Facebook did in November 2017.
    
    More on this can be found in the blog @
    https://www.redhat.com/en/blog/fostering-greater-open-source-development &
    https://www.redhat.com/en/about/gplv3-enforcement-statement
    
    fixes: bz#1569345
    Change-Id: Ia78023540ab587ebe14048a67413029be309413d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit dcccfeb887d777ef77e35271a451f70c7c5222d6
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 23 11:25:26 2018 -0400

    api: missing __THROW on pub function decls
    
    missing __THROW on pub function decls needed for C++
    
    Change-Id: Ia0ff09d311741e4cdc8ef171e07bbd56c24b9260
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 4ae7f0714b809cfebb64f6e5b5a70664e17a7a56
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri May 18 20:03:32 2018 +0530

    changelog: fix br-state-check.t failure for brick_mux
    
    Problem: Sometime br-state-check.t crash while runnning
             for brick multiplex and command in test case is
             taking 2 minutes for detach a brick
    
    Solution: Update code in changelog xlator specific to wait
              on all connection before cleanup rpc threads and
              cleanup rpc object only in non brick mux scenario
    
    BUG: 1577672
    Change-Id: I16e257c1e127744a815000b87bd8b7b8d9c51e1b
    fixes: bz#1577672
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 44d62baed46a41752b5379bc4095c0a8e20de32f
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu May 24 11:02:53 2018 +0530

    Fix a test case that can fail for certain builds
    
    If certain builds have readdir-ahead disabled by default, the
    test case fails, as it asumes readdir-ahead is enabled by
    default. Hence explicitly enabling readdir-ahead.
    
    Change-Id: Ib5bef266707c2c557aeb2cf2ffbf4d0c92025c46
    fixes: bz#1582051
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit e9e3699456e738635685c9f42d1c4206c6177510
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 22 00:34:48 2018 -0400

    posix/ctime: Fix updating mtime to older time
    
    With ctime feature enabled, the mtime is not
    updated when it's set to time older than the
    existing one. Fixed the same. But the ctime
    is not allowed to change to older dates.
    
    fixes: bz#1581035
    Change-Id: If520922df42d6ce084c8df3046c138f8367164e5
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit fc17daf2e6d665262ba12e6f6aab91678f124ab8
Author: Susant Palai <spalai@redhat.com>
Date:   Fri May 18 12:20:08 2018 +0530

    core: make glfs_iobuf_copy() consumable for general purpose.
    
    Currently plugins for cloudsync will be using it to write back data
    downloaded from remote store/cloud.
    
    Change-Id: I59f10bebed21b19568c94cbf29e3d536d5570749
    Updates: #387
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 9cc4ed624edb368d77d6bb7a5dfae1a79746e523
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 21 12:57:45 2018 -0400

    posix/ctime: Fix gfid heal on first lookup
    
    With ctime feature enabled, the gfid is
    not healing on first lookup. The fresh
    file logic depends on ctime and it was
    fetching from backend instead of xattr
    with ctime feature enabled. Fixed the
    same.
    
    Also fixed a possible hang with inode lock
    
    Change-Id: I020875c0462b284d6fa0e68304a422fa3d6a3e73
    fixes: bz#1580532
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit de9b8c06b89b6129154693f048985554ccc5a7e7
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon May 21 14:51:44 2018 -0400

    storage/posix: use proper FOP for unwinding readdir(p)
    
    As of now, even for readdirp, posix is unwinding with readdir
    signature.
    
    Change-Id: I6440c8a253c5d78bbcc97043e4e6e208e3d47cd1
    fixes: bz#1581345
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit ab18f27bff1bbeeaad3cce8177175dbf6f4c7228
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 21 12:57:45 2018 -0400

    posix/ctime: Fix atime update for hardlink
    
    With ctime feature enabled, atime is not
    being updated for a hardlink when the file
    is accessed.
    
    e.g., touch -a <hardlink_file> fails to
    update atime. This patch fixes the same.
    
    fixes: bz#1580529
    Change-Id: I2201c88d502d0070300a1f5023af1b36951284ec
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 52fe35609d99821ebab003c93ca6e63aae243f95
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon May 21 11:04:45 2018 +0530

    cluster/dht: Fix rebalance log msg
    
    Corrected the name of the xattr and fixed
    the code to log an error only if op_errno
    is not ENODATA or ENOATTR.
    
    Change-Id: I42c5b1d838eec586ac7bed2471eb1d27ff09a9ea
    fixes: bz#1580238
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 1a4a900589b35faec28f67c7c26004a240bf6a6c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Apr 13 12:03:48 2018 +0530

    sdfs: enable by default
    
    also provide an option for pass-through to enable/disable xlator
    
    fixes: #421
    Change-Id: Ie30a91ad09620db62ab07b797e23123fd1200d1f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 18cbdeb529c2e7b60733fbbb9bf9bab2d5fd238c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 15 13:33:16 2018 -0400

    ctime: Fix updating ctime in rename and unlink
    
    1. Successful rename was not updating ctime.
       Fixed the same.
    2. Successful unlink when link count is more than 1
       was not updating ctime. Fixed the same.
    3. Copy ctime and flags during frame copy.
    
    fixes: bz#1580020
    Change-Id: Ied47275a36aea60254b2add7a59128a9c83b3645
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit ead98973da9aed805fca7b6382c1e94e2ea3dbf1
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue May 22 19:15:19 2018 +0530

    features/sdfs: implement readdirp
    
    Since readdirp acts as a batched lookup for all dentries it reads, it
    has to synchronize with any entry operation within the directory being
    read.
    
    Change-Id: I923a6ebd21856dbaa5fa5db4a26a29b7b29b3159
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    fixes: #421

commit 2d5b179d1a545f5b7ae8b1b2274769691dd3468f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu May 17 05:28:24 2018 -0400

    rpc: Don't reset auth_value in disconnect
    
    The auth_value was being reset to AUTH_GLUSTERFS_v2
    during rpc disconnect. It shoud not be reset. The
    disconnect during portmap request can race with
    handshake. If handshake happens first and
    disconnect later, auth_value would set to default
    value and it never sets back to actual auth_value
    
    fixes: bz#1579276
    Change-Id: Ib46c9e01a97f6defb3fd1e0423fdb4b899b4a361
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 676aae1ef168cb7ecad4eecd71b079a5d4995247
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue May 15 11:37:16 2018 +0200

    cluster/ec: Fix pre-op xattrop management
    
    Multiple pre-op xattrop can be simultaneously being processed. On the cbk
    it was checked if the fop was waiting for some specific data (like size and
    version) and, if so, it was assumed that this answer should contain that
    data.
    
    This is not true, since a fop can be waiting for some data, but it may come
    from the xattrop of another fop.
    
    This patch differentiates between needing some information and providing it.
    
    This is related to parallel writes. Disabling them fixed the problem, but
    also prevented concurrent reads. A change has been made so that disabling
    parallel writes still allows parallel reads.
    
    Fixes: bz#1578325
    Change-Id: I74772ad6b80b7b37805da93d5ec3ae099e96b041
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 92839c5a4a6c87973e4f6f2f96b359e9c2a0f5c0
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed May 23 10:16:37 2018 -0400

    test: Marking test case bug-1309462.t as bad
    
    Details in the bug
    
    Updates: bz#1581735
    
    Change-Id: Id984e10b60daf274d5510e3ccbf7abf0cb19f368
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 3ec6ae1c1fb103df077f44b18604e768fea00ddc
Author: Susant Palai <spalai@redhat.com>
Date:   Thu May 3 17:41:16 2018 +0530

    features/cloudsync: Make plugins configurable
    
    This patch brings the configuration option for plugins.
    
    For new plugins, an entry has to be created in to cs_plugin structure e.g.
    struct cs_plugin plugins[] = {
            {
              .name = "amazons3",
              .library = "libamazons3.so",
              .description = "amazon s3 store."
            },
    
            {.name = NULL},
    };
    
    Library field describes the name of the shared library for the plugin.
    
    To configure plugin type "feature.cloudsync-storetype" option need
    to be set to the remote-store type. e.g.
    
    gluster volume set VOLNAME cloudsync-storetype amazons3. This should be same
    as the ".name" field in cs_plugin structure.
    
    cs_init will pick this up in run time to load the plugin.
    
    Change-Id: I2cec10b206f71ac4e71d472631a3a5badf278b59
    fixes: bz#1576842
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 985a1d15db910e012ddc1dcdc2e333cc28a9968b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri May 18 15:38:29 2018 +0530

    afr: fix bug-1363721.t failure
    
    Problem:
    In the .t, when the only good brick was brought down, writes on the fd were
    still succeeding on the bad bricks. The inflight split-brain check was
    marking the write as failure but since the write succeeded on all the
    bad bricks, afr_txn_nothing_failed() was set to true and we were
    unwinding writev with success to DHT and then catching the failure in
    post-op in the background.
    
    Fix:
    Don't wind the FOP phase if the write_subvol (which is populated with readable
    subvols obtained in pre-op cbk) does not have at least 1 good brick which was up
    when the transaction started.
    
    Note: This fix is not related to brick muliplexing. I ran the .t
    10 times with this fix and brick-mux enabled without any failures.
    
    Change-Id: I915c9c366aa32cd342b1565827ca2d83cb02ae85
    updates: bz#1577672
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 7f67ddcc5c31a84a6fc296c64a0b904ff963e814
Author: Gergo Huszty <gergo.huszty@nokia.com>
Date:   Wed May 16 13:28:21 2018 +0000

    Fix for memory-leak in crypt xlator
    
    Crypt xlator occasionaly uses local storage in it's call frame.
    These frames are managed with common macroes, which does not take
    care about cleaning up such local storages. The fix is similar to
    the other xlators' solution. A crypt specific macro handles the
    cleaning of the local storage when it is allocated.
    
    Change-Id: Ibb5b91551fbe70905e9c8c688d999fe702433e35
    fixes: bz#1564419
    Signed-off-by: Gergo Huszty <gergo.huszty@nokia.com>

commit ad478b6ccb66b20f2e97d50f9ec79cfcdc4368ba
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 8 21:19:56 2018 +0200

    posix: use the ctime framework to handle setattr ctime payload
    
    Work on #208 having been been merged, we have obtained
    means to associate arbitrary ctimes with files, so
    we can handle setattr ctime payload with proper semantics.
    
    Updates: #435
    Change-Id: I7302a3ee2574ca9bba605c7a8586c16c452f82c1
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 89e1a4e5720509c096ff6860c1a8c483e0019278
Author: Prashanth Pai <ppai@redhat.com>
Date:   Thu May 10 18:25:56 2018 +0530

    build: Disallow unresolved symbol references
    
    In the past, it was often[1] forgotten for xlators to be linked against
    the symbols they refer to. This often caused glusterd2 to fail while
    loading xlator's shared object (.so) file.
    
    This change adds "--no-undefined" as a linker flag which causes the
    linker to treat unresolved symbol references as an error and hence fail
    linking.
    
    [1]:
    https://review.gluster.org/#/c/19912/
    https://review.gluster.org/#/c/19664/
    https://review.gluster.org/#/c/19056/
    https://review.gluster.org/#/c/17659/
    https://bugzilla.redhat.com/show_bug.cgi?id=1532238
    
    Bonus:
    Added cloudsync and utime xlator's generated source files to .gitignore
    
    Updates: bz#1193929
    Change-Id: I9604a4a87b7313a5fa43bda5fdb37dfa7ef8facd
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit c2cf3f686f3ea0efd936d2eafc404fc9d2e0acc7
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri May 4 12:25:48 2018 -0400

    make posix return errors when gfid2path key is absent
    
    Change-Id: I3a8d452d00560dac5e0b7ff0b1835d1f20a59f91
    updates: bz#1570962
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 7588be808db3fcfda337971990f02d2ebccba3d7
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue May 8 10:35:35 2018 +0530

    extras/create_new_xl : Fix the tool to accomodate the xl structure changes
    
    Change-Id: I3524e62b0ed873c0763ca38f80fcd53b22ee79d1
    fixes: bz#1577744
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit c925962b91c67c8cd2391df7dd0251e0cbf66648
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed May 16 18:15:02 2018 +0530

    cluster/dht: Remove EIO from dht_inode_missing
    
    Removed EIO from the list of errnos that triggered
    a migrate check task.
    
    Change-Id: I7f89c7a16056421588f1af2377cebe6affddcb47
    fixes: bz#1578823
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 7022bcf7691eca5d890629cb4322e37f6e4e5434
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed May 16 11:00:32 2018 +0530

    readdir-ahead: Fix an issue with parallel-readdir and readdir-optimize
    
    Issue: When parallel-readdir is enabled, readdir-optimize automatically
    stops working because of a bug in rda_opendir.
    
    RCA: In rda_opendir, the xattrs that indicate readdir-optimize or not
    is sent in xdata. This xdata is sent to all the readdirp prefetch
    calls. A dict_ref is taken on xdata and kept in rda_opendir to be
    used by rda_fill_fd, but dht_opendir deletes some elements in xdata
    after calling rda_opendir. Hence dict_ref is not a right choice here,
    dict_copy needs to used.
    
    Change-Id: Ie7cc7ceb03117dd4179ef7905647f2f123f94966
    fixes: bz#1578650
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 7ac79fb033824605dd5145975a16aeb155172185
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 9 00:56:11 2018 +0530

    client/protocol: fix the log level for removexattr_cbk
    
    noticed that server protocol actually logs all the errors for
    removexattr as INFO, instead of WARNING like client, and hence,
    doesn't create a confusion in user.
    
    updates: bz#1576418
    Change-Id: Ia6681e9ee433fda3c77a4509906c78333396e339
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 9ead9a66900b15387b4b7588ff5c1300810d5eba
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 16 14:12:21 2018 +0530

    statedump: Prevent duplicate statedump for master and active
    
    Csaba found that statedump of fusemount has two instances of
    each of the mem-accounting information. On debugging, I realized
    that statedump is called for both ctx->master and ctx->active.
    Since ctx->active is a sub-graph of ctx->master, there are duplicate
    entries. Fixed this part to prevent duplication in this patch.
    
    fixes bz#1578721
    BUG: 1578721
    Change-Id: I5a63b4f5933d4d720ac010c58e6dee3b27067d42
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit f631ceb79e822bb5c3bbbaa2ad3a28a3f32e4251
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sun May 13 21:03:12 2018 +0530

    cli: Fix for gluster volume info --xml
    
    Problem: gluster volume info --xml is showing same uuid to all
    the bricks of a tier volume.
    
    Solution: While iterating over hot/cold bricks of a tier volume, use
    correct iterator.
    
    Fixes: bz#1577627
    Change-Id: Icf6a9c2a10b9da453abc262a57b7884d6638e3ed
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 8e2289b1e76ac777b71897dc709d9651341bd241
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sun May 13 12:01:01 2018 +0530

    glusterfs: Resolve brick crashes at the time of inode_unref
    
    Problem: Sometimes brick process is getting crash at the time
             of calling inode_unref in fd_destroy
    
    Solution: Brick process is getting crash because inode is already
              free by xlator_mem_cleanup call by server_rpc_notify.To
              resolve the same move code specific to call transport_unref
              in last in free_state.
    
    BUG: 1577574
    Change-Id: Ia517c230d68af4e929b6b753e4c374a26c39dc1a
    fixes: bz#1577574
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 829f32c61c364323bab494cf9dab880aad4be463
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 9 01:10:29 2018 -0400

    geo-rep/scheduler: Fix crash
    
    Fix crash where session_name is referenced
    before assignment. Well, this is a corner
    case where the geo-rep session exists and
    the status output doesn't show any rows.
    This might happen when glusterd is down
    or when the system is in inconsistent state
    w.r.t glusterd.
    
    fixes: bz#1576179
    Change-Id: Iec1557e01b35068041b4b3c1aacee2bfa0e05873
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 57632e3c1a33187d1d23f101f83cd8759142acac
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 7 06:35:25 2018 -0400

    glusterd/geo-rep: Fix glusterd crash
    
    Using strdump instead of gf_strdup crashes
    during free if mempool is being used.
    gf_free checks the magic number in the
    header which will not be taken care if
    strdup is used.
    
    fixes: bz#1576392
    Change-Id: Iab36496554b838a036af9d863e3f5fd07fd9780e
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 1ef9270c0990e93712c211516ccc47c3bb27674b
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue May 8 11:42:33 2018 +0530

    Glusterfsd: brick crash during get-state
    
    The xprt's dereferencing wasn't checked before using it for the
    strcmp, which caused the segfault and crashed the brick process.
    
    fix: Check every deferenced variable before using it.
    
    Change-Id: I7f705d1c88a124e8219bb877156fadb17ecf11c3
    fixes: bz#1575864
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit 021b60858c562cd51dbeec8c00a61243c7189df2
Author: Varsha Rao <varao@redhat.com>
Date:   Wed Mar 21 16:29:04 2018 +0530

    libglusterfs/stack: Fix coverity issue
    
    Fix ARRAY_VS_SINGLETON coverity issue.
    
    Change-Id: I9e70be026e80011dfc8fb0f06c4563895eb6daf4
    fixes: bz#1558574
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 08dcb1c2bf02bba313d3bfc8fbc1c8ea63296321
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu May 10 16:54:44 2018 +0530

    dht: Excessive 'dict is null' logs in dht_discover_complete
    
    Problem: In Geo-Rep setup excessive "dict is null" logs in
             dht_discover_complete while xattr is NULL
    
    Solution: To avoid the logs update a condition in dht_discover_complete
    
    BUG: 1576767
    Change-Id: Ic7aad712d9b6d69b85b76e4fdf2881adb0512237
    fixes: bz#1576767
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit b4ce5e090dee2afc9ed0c86456a54f76a2bb6563
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon May 7 14:52:44 2018 -0400

    gfapi: various broken symbol versions
    
    lots of breakage in symbol versions:
      symbols added in 4.1 incorrectly, and
      symbols added in 4.1 but labeled 4.0.0, and
      symbols added in 3.13 incorrectly
    
    Not noticed until someone tried to build 3.13.2 on FreeBSD 11.1,
    despite the fact that we build on FreeBSD 10.3 IIRC, somehow the
    3.13 errors aren't a build error there.
    
    Note: in rereading the Ulrich Drepper write-up I noticed that when
    a symbol version is changed, you are supposed to leave the old
    symbol in its original section in addition to adding it to its new
    section. Adding back those symbols to their original sections.
    
    Reported-by: Roman Serbski <mefystofel@gmail.com>
    
    Change-Id: I9a883546d08e0847f7228d8ea5943bc54275b319
    fixes: bz#1575716
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit e471c2a781f8e15e43fc6662d0a6430bd104bc34
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue May 8 10:55:53 2018 +0530

    features/cloudsync: Remove multiple definition in Makefile.am
    
    CLOUDSYNC_SRC is defined twice in the same Makefile.am which generates
    the following warning:
    
    xlators/features/cloudsync/src/Makefile.am:9: warning: CLOUDSYNC_SRC multiply defined in condition TRUE ...
    xlators/features/cloudsync/src/Makefile.am:5: ... 'CLOUDSYNC_SRC' previously defined here
    
    Therefore removing the duplicate definition.
    
    Change-Id: I00c3e2f3d64ad45e4080c2c82766516cd3e2bf63
    fixes: bz#1193929
    BUG: 1193929
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 2b2410acb4cca0554ee710ca32bfa58ce49d3204
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 9 07:06:38 2018 -0400

    core: FreeBSD has pthread_set_name_np() (versus pthread_setname_np())
    
    And has had it since at least FreeBSD 9.0
    
    Reported-by: Roman Serbski <mefystofel@gmail.com>
    
    Change-Id: I52cfde7f2f7a82d0e66465ac392ed7e201e1653b
    updates: bz#1193929
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 8d1335af8024e3622eaab31520cc2b8a70c0f212
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Tue May 8 11:41:11 2018 +0530

    Quota: Turn on ssl for crawler clients if needed
    
    Problem: Quota uses per brick client generated by
    glusterd_generate_client_per_brick_volfile to crawl the
    individual bricks. These clients were not being configured
    with ssl if volume has client.ssl turned on.
    
    Solution: turn on client.ssl if the volume has client.ssl
    option set to on.
    
    Change-Id: Id3a13d5110c4376d734480c42da1ce6844cc8240
    fixes: bz#1575858
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>

commit 2d3b44641dc7820043eae37572292b7b3cc26625
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri May 4 10:34:13 2018 +0530

    cluster/dht:  Debug virtual xattrs for dht
    
    Provide a virtual xattr with which to query
    the hashed subvol for a file.
    
    Change-Id: Ic7abd031f875da4b9084841ea7c25d6c8a851992
    fixes: bz#1574421
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit d3e3b11d38b927cf849d2d7a20460650963fd438
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue May 8 13:34:35 2018 +0530

    cluster/dht: Debug logs in dht_readdir(p)_cbk
    
    Additional log messages to help debug issues
    with file listings.
    
    Change-Id: Iccd07498ba01d597c0c40f026f4177dd06d7e901
    fixes: bz#1575887
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 52d9b8bcd5b0aee750a22d53b46c804d608d8bba
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Apr 17 23:05:54 2018 +0530

    protocol/server: don't assume there would be a volfile id
    
    Earlier glusterfs never had an assumption someone would start it with
    right arguments, and brick processes would be spawned by a management
    layer. It just assume the role based on the volfile. Other than
    volfile, no other arguments should be technically mandatory for
    working of glusterfs. With this patch, that assumption holds true.
    
    Updates: github issue # 352
    
    A note on why this particular issue for this basic sanity?
    
    As per the design of thin-arbiter/tie-breaker, it can be started
    independently on any machine, without need of glusterd. So, similar
    to 'glusterd', we should be able to spawn a process with any translator
    without options/volume id etc.
    
    fixes: bz#1569399
    Change-Id: I5c0650fe0bfde35ad94ccba60e63f6cdcd1ae5ff
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ed5a09e4aea7f64f9a43698955e24285a936f0c0
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue May 8 14:52:04 2018 +0530

    dht: Avoid dict log flooding for internal MDS xattr
    
    Problem: Before populate MDS internal xattr first dht checks if MDS is
             present in xattr or not.If xattr dictionary is NULL dict_get
             log the message either dict or key is NULL
    
    Solution: Before call dict_get check xattr, if it is NULL then no
              need to call dict_get.
    
    BUG: 1575910
    Change-Id: I81604ec5945b85eba14b42f4583d06ec713028f4
    fixes: bz#1575910
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 38fa8b983b42c7970cd5583e9b10a385a60b89dc
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon May 7 14:51:06 2018 -0400

    glusterd: Update op-version for master
    
    Updated the op-version on master to the next release
    op-version, for any future options appearing on master.
    
    Fixes: bz#1575742
    Change-Id: I861d489573360e6679c6f5ffe127835ea71f2dda
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit f8b6795b23aa23cc8e4af9159e6dd0dafc8b983b
Author: Michael Adam <obnox@samba.org>
Date:   Sun May 6 14:53:08 2018 +0200

    heal: improve output of heal info
    
    The output of "gluster volume heal <volume> info" is clobbered with
    extra new lines when messages "- Possibly undergoing heal" or " - Is in
    split-brain" are printed for listed files.
    
    This patch fixes the output by removing the extra new lines.
    
    Bug: 1575381
    
    Change-Id: Ifb614e0fb7c85f7af3a799958d3645a2bff2b53a
    fixes: bz#1575381
    Signed-off-by: Michael Adam <obnox@samba.org>

commit 4b046827b99480e0cfabeaa75e593db13445176e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Apr 13 10:28:01 2018 +0530

    fuse: make sure the send lookup on root instead of getattr()
    
    This change was done in https://review.gluster.org/16945. While the
    changes added there were required, it was not necessary to remove the
    getattr part. As fuse's lookup on root(/) comes as getattr only, this
    change is very much required.
    
    The previous fix for this bug was to add the check for revalidation in
    lookup when it was sent on root. But I had removed the part where
    getattr is coming on root. The removing was not requried to fix the
    issue then. Added back this part of the code, to make sure we have
    proper validation of root inode in many places like acl, etc.
    
    updates: bz#1437780
    Change-Id: I859c4ee1a3f407465cbf19f8934530848424ff50
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 4da244caccd38a77de5428b6954f565219ef0719
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Apr 6 01:53:45 2018 +0530

    glusterd: handling brick termination in brick-mux
    
    Problem: There's a race between the glusterfs_handle_terminate()
    response sent to glusterd from last brick of the process and the
    socket disconnect event that encounters after the brick process
    got killed.
    
    Solution: When it is a last brick for the brick process, instead of
    sending GLUSTERD_BRICK_TERMINATE to brick process, glusterd will
    kill the process (same as we do it in case of non brick multiplecing).
    
    The test case is added for https://bugzilla.redhat.com/show_bug.cgi?id=1549996
    
    Change-Id: If94958cd7649ea48d09d6af7803a0f9437a85503
    fixes: bz#1545048
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 23c1385b5f6f6103e820d15ecfe1df31940fdb45
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 7 01:23:46 2018 -0400

    geo-rep: Fix upgrade issue
    
    Cause and Analysis:
    The last synced changelog for entry operations is
    marked in current version to avoid re-processing
    of already processed entry operations in a batch
    during crash/restart of geo-rep. This was not
    present in previous versoins.
    
    The marker is maintained in the dictionary with the
    key 'last_synced_entry' and dictionary is persisted
    into status file. So upgrading to current version in
    which the marker is present was failing with KeyError.
    
    Solution:
    Load the dictionary with default keys first which
    contains all the keys including latest ones and then
    load the values from status file instead of doing
    otherwise.
    
    fixes: bz#1575490
    Change-Id: Ic654e6f9a3c97f616761f1362f890352a2186fb4
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 5e356e3f470779433bfe6b0b368676062842b367
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Feb 8 17:12:41 2018 +0530

    cluster/dht: fixes to parallel renames to same destination codepath
    
    Test case:
     # while true; do uuid="`uuidgen`"; echo "some data" > "test$uuid"; mv
       "test$uuid" "test" -f || break; echo "done:$uuid"; done
    
     This script was run in parallel from multiple mountpoints
    
    Along the course of getting the above usecase working, many issues
    were found:
    
    Issue 1:
    =======
    consider a case of rename (src, dst). We can encounter a situation
    where,
    * dst is a file present at the time of lookup
    * dst is removed by the time rename fop reaches glusterfs
    
    In this scenario, acquring inodelk on dst fails with ESTALE resulting
    in failure of rename. However, as per POSIX irrespective of whether
    dst is present or not, rename should be successful. Acquiring entrylk
    provides synchronization even in races like this.
    
    Algorithm:
    1. Take inodelks on src and dst (if dst is present) on respective
       cached subvols. These inodelks are done to preserve backward
       compatibility with older clients, so that synchronization is
       preserved when a volume is mounted by clients of different
       versions. Once relevant older versions (3.10, 3.12, 3.13) reach
       EOL, this code can be removed.
    2. Ignore ENOENT/ESTALE errors of inodelk on dst.
    3. protect namespace of src and dst. To protect namespace of a file,
       take inodelk on parent on hashed subvol, then take entrylk on the
       same subvol on parent with basename of file. inodelk on parent is
       done to guard against changes to parent layout so that hashed
       subvol won't change during rename.
    4. <rest of rename continues>
    5. unlock all locks
    
    Issue 2:
    ========
    linkfile creation in lookup codepath can race with a rename. Imagine
    the following scenario:
    * lookup finds a data-file with gfid - gfid-dst - without a
      corresponding linkto file on hashed-subvol. It decides to create
      linkto file with gfid - gfid-dst.
        - Note that some codepaths of dht-rename deletes linkto file of
          dst as first step. So, a lookup racing with an in-progress
          rename can easily run into this situation.
    * a rename (src-path:gfid-src, dst-path:gfid-dst) renames data-file
      and hence gfid of data-file changes to gfid-src with path dst-path.
    * lookup proceeds and creates linkto file - dst-path - with gfid -
      dst-gfid - on hashed-subvol.
    * rename tries to create a linkto file dst-path with src-gfid on
      hashed-subvol, but it fails with EEXIST. But EEXIST is ignored
      during linkto file creation.
    
    Now we've ended with dst-path having different gfids - dst-gfid on
    linkto file and src-gfid on data file. Future lookups on dst-path will
    always fail with ESTALE, due to differing gfids.
    
    The fix is to synchronize linkfile creation in lookup path with rename
    using the same mechanism of protecting namespace explained in solution
    of Issue 1. Once locks are acquired, before proceeding with linkfile
    creation, we check whether conditions for linkto file creation are
    still valid. If not, we skip linkto file creation.
    
    Issue 3:
    ========
    gfid of dst-path can change by the time locks are acquired. This
    means, either another rename overwrote dst-path or dst-path was
    deleted and recreated by a different client. When this happens,
    cached-subvol for dst can change. If rename proceeds with old-gfid and
    old-cached subvol, we'll end up in inconsistent state(s) like dst-path
    with different gfids on different subvols, more than one data-file
    being present etc.
    
    Fix is to do the lookup with a new inode after protecting namespace of
    dst. Post lookup, we've to compare gfids and correct local state
    appropriately to be in sync with backend.
    
    Issue 4:
    ========
    During revalidate lookup, if following a linkto file doesn't lead to a
    valid data-file, local->cached-subvol was not reset to NULL. This
    means we would be operating on a stale state which can lead to
    inconsistency. As a fix, reset it to NULL before proceeding with
    lookup everywhere.
    
    Issue 5:
    ========
    Stale dentries left out in inode table on brick resulted in failures
    of link fop even though the file/dentry didn't exist on backend fs. A
    patch is submitted to fix this issue. Please check the dependency tree
    of current patch on gerrit for details
    
    In short, we fix the problem by not blindly trusting the
    inode-table. Instead we validate whether dentry is present by doing
    lookup on backend fs.
    
    Change-Id: I832e5c47d232f90c4edb1fafc512bf19bebde165
    updates: bz#1543279
    BUG: 1543279
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 01a7d27bbaf12618fde56ca05cf9c953445493f3
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Mar 16 12:16:43 2018 +0530

    cluster/dht: log error only if layout healing is required
    
    selfhealing of directory is invoked on two conditions:
    1. no layout on disk or layout has some anomalies (holes/overlaps)
    2. mds xattr is not set on the directory
    
    When dht_selfheal_directory is called with a correct layout just to
    set mds xattr, we see error msgs complaining about "not able to form
    layout on directory", which is misleading as the layout is
    correct. So, log this msg only if layout has anomalies.
    
    Change-Id: I4af25246fc3a2450c2426e9902d1a5b372eab125
    updates: bz#1543279
    BUG: 1543279
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 33131131469e18d3ebbdc6ce741c2984dc77b290
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Mar 21 13:09:01 2018 +0530

    extras/hooks: Do not blindly remove volume share from smb.conf
    
    When Gluster volumes are shared via Samba, any extra smb.conf parameter
    setting done by administrator to those shares are lost during restart
    of the volume. Instead of removing the whole share completely from
    smb.conf(via hook scripts during volume stop) it is better to make it
    temporarily unavailable to end-users till the volume is started again.
    Therefore we make use of a smb.conf parameter named 'available'[1] to
    achieve the above intend.
    
    [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
    
    Change-Id: I68a9055b50791f6ffd3b95a3c13d858a75fa6530
    fixes: bz#1558921
    BUG: 1558921
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit a6490fe02174d344f4ed81fa3bc6c0b5933f4faf
Author: Thomas Hindoe Paaboel Andersen <phomes@gmail.com>
Date:   Sat May 5 20:23:32 2018 +0200

    gfapi: acutally avoid recall callback when closed
    
    Due to missing curly braces we end up calling the callback
    function even when state is GLFD_CLOSE. This patch adds the
    curly braces so both the log and actual callback is skipped.
    
      Introduced in 19568 in commit b04066721bf4a240f61b83bd87bbb27437c5fe4f
    
    Change-Id: I0b15cfe222841cfcb12f17723284acb3838d64d7
    fixes: bz#1575294
    Signed-off-by: Thomas Hindoe Paaboel Andersen <phomes@gmail.com>

commit 9e739aef97bedfd30e401575ffb6a67e53eec16f
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Apr 30 19:34:34 2018 +0530

    glusterd: Fix for memory leak in volume tier status command
    
    Fixes: bz#1573220
    Change-Id: Ia60f40fa4f1e525cae6f571a24e5385ba1e004c0
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 17e3f617086da785a3678d7cfa8f68ebd1497023
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sat May 5 00:05:09 2018 -0400

    glusterd/ctime: Provide option to enable/disable ctime feature
    
    Updates: #208
    Change-Id: If6f52b9b1b5b823ad64faeed662e96ceb848c54c
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 99cba93daadd29967d26621d1deee842d94483a8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 23 04:44:40 2018 -0400

    glusterd/utime: glusterd utime changes
    
    Load utime xlator in the client side just after (below)
    performance xlators.
    
    Updates: #208
    Change-Id: Ie15f156943fa8e7dac7050e5479c906da747b568
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 487aaafacac8af16c08eb44fe9bf178768d372fa
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 30 04:43:58 2018 -0400

    utime: ctime client side xlator
    
    The client side utime xlator does two things.
    
    1. Update unix epoch time in frame->root->ctime
    2. Update the frame->root->flags based on the fop
       which indicates time attributes that should be
       updated for the parent/entry.
    
    Credits: Rafi KC <rkavunga@redhat.com>
    Updates: #208
    Change-Id: I9cad297040c70798a0a8468a080eb4aeff73138d
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit f8fe0771f0b450713595a7d298ed5a758cf2ce3e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 2 08:31:25 2018 -0400

    posix/ctime: posix hook to set ctime xattr in relevant fops
    
    This patch uses the ctime posix APIs to set consistent
    time across replica on disk. It also stores the time
    attributes in the inode context.
    
    Credits: Rafi KC <rkavunga@redhat.com>
    Updates: #208
    Change-Id: I1a8d74d1e251f1d6d142f066fc99258025c0bcdd
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 9a854a98af69c1b7e06aa01dff7ea3271ebd574c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 23 04:22:09 2018 -0400

    posix/ctime: posix hooks to get consistent time xattr
    
    This patch uses the ctime posix APIs to get consistent
    time across replica. The time attributes are got from
    from inode context or from on disk if not found and
    merged with iatt to be returned.
    
    Credits: Rafi KC <rkavunga@redhat.com>
    Updates: #208
    Change-Id: Id737038ce52468f1f5ebc8a42cbf9c6ffbd63850
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 3e24848f1e568ed3307683a9786f33d1ee15209b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Nov 3 09:57:08 2017 -0400

    posix: APIs in posix to get and set time attributes
    
    This is part of the effort to provide consistent time
    across distribute and replica set for time attributes
    (ctime, atime, mtime) of the object. This patch contains
    the APIs to set and get the attributes from on disk
    and in inode context.
    
    Credits: Rafi KC <rkavunga@redhat.com>
    Updates: #208
    Change-Id: I5d3cba53eef90ac252cb8299c0da42ebab3bde9f
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 80262e2984b44609e9f572cf11dbc24fb6aea4cc
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Apr 27 15:36:04 2018 +0530

    tests: Add lease test case
    
    Updates: #350
    Change-Id: Iee78ab4baf48c481de1e13ff2b0393bc106b7d0e
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 0adede47479b4bdc27a4512763ed221280f6d694
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jul 20 16:12:31 2015 +0530

    afr: Add lease() fop
    
    Change-Id: Ied047dd5ee44e9d5a5d3db214826f7df30332ef9
    updates: #350
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 1322274eefe6dec09050bfadcecc29fc1e79cd1b
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu May 3 13:35:04 2018 +0200

    mount,fuse: make fuse dumping available as mount option
    
    Updates: bz#1193929
    Change-Id: I4dd4d0e607f89650ebb74b893b911b554472826d
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 2ac79ed8048753dfd2494d3a4d3b0e9411673e3a
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu May 3 10:22:18 2018 +0200

    fuse: add support for kernel writeback cache
    
    - Added kernel-writeback-cache command line and xlator
      option for requesting utilisation of the writeback
      cache of the kernel in FUSE_INIT (see [1]).
    - Added attr-times-granularity command line and xlator
      option via which granularity of the {a,m,c}time in
      stat (attr) data that we support can be indicated to
      kernel. This is a means to avoid divergence of the
      attr times between kernel and userspace that could
      occur with writeback-cache, while still maintaining
      maximum time precision the FUSE server is capable of
      (see [2]).
    - Handling FATTR_CTIME flag in FUSE_SETATTR that
      indicates presence of ctime in setattr payload.
      Currently we cannot associate arbitrary ctimes to
      files on backend, so we just touch them to update
      their ctimes to current time. Having ctimes in setattr
      payload is also a side effect of writeback cache
      (see [3] and [4]).
    
    [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4d99ff8,
         "fuse: Turn writeback cache on"
    [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e27c9d3,
         "fuse: fuse: add time_gran to INIT_OUT"
    [3]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1e18bda,
         "fuse: add .write_inode"
    [4]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab9e13f,
         "fuse: allow ctime flushing to userspace"
    
    Updates: #435
    Change-Id: Id174c8e0c815c4456c35f8c53e41a6a507d91855
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 15866ac9773e89cd9e017e7d3bf8aa01a87edfd8
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Apr 27 15:22:50 2018 +0530

    feature/leases : fixing bugs found while testing glfs_test.t
    
    Change-Id: Iee8f431601ecda184108a079f665e05902b0f78b
    updates: #350
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit b04066721bf4a240f61b83bd87bbb27437c5fe4f
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Apr 27 15:12:08 2018 +0530

    gfapi : RECALL_LEASE implementation
    
    Right now there are two types of upcalls
    * poll method
    * registering callback
    
    But callback can be registered per fs and same callback fn shall be used
    for any lease recall with object handle as argument as done for cache
    invalidation.
    
    TODO: RECALL LEASE for each glfd (for future reference)
     (may be needed fo Samba as they do not deal with
      object handles.
    
        In case of RECALL_LEASE, we could associate separate
         cbk function for each glfd either by
           - extending pub_glfs_lease to accept new args (recall_cbk_fn, cookie)
           - or by defining new API "glfs_register_recall_cbk_fn (glfd, recall_cbk_fn, cookie)
           . In such cases, flag it and instead of calling below upcall functions, define
            a new one to go through the glfd list and invoke each of theirs recall_cbk_fn.
    
    Plus added following as well
    * passed lease id to dict in required arguments
    * added flag check in pub_glfs_open
    
    Updates: #350
    Change-Id: I07a971f0f26ec6aae0b9f9a5613504317dee153b
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit b42a048d3a76c7f377399f18d30f0a8a930f9d05
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Apr 20 14:54:33 2018 -0400

    features/bitrot: print the path of the corrupted objects
    
    Currently "gluster volume bitrot <volume name> scrub status"
    gives the list of the corrupted objects (files as of now).
    But only the gfids of those corrupted objects are seen and
    one has to do getfattr, find etc operations to get the actual
    path of those objects for removal etc.
    
    This change makes an attempt to print the path of those files
    as much as possible.
    
    * Try to get the path using the on disk gfid2path xattr.
    
    * If the above operation fails, then go for in memory path
    (provided that the object has its dentry
    properly created and linked in the inode table of the brick where
    the corrupted object is present) So the gfid to path resolution is
    a soft resolution, i.e. based on the inode and dentry cache in the
    brick's memory. If the path cannot be obtained via inode table also,
    then only gfid is printed.
    
    Change-Id: Ie9a30307f43a49a2a9225821803c7d40d231de68
    fixes: bz#1570962
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit bef654f48c14bfd7ce20702edff41052f6f54bdc
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu May 3 12:15:52 2018 -0400

    use awk to get a specific line from the output instead of cut
    
    cut -d$'\n' is not separating the xattrs shown as part of getfattr output.
    Hence use awk to get the nth line of getfattr output for nth iteration
    in the for loop.
    
    Change-Id: I1a96cd3f72f4f407f9a783375f78d9a69d5d3885
    fixes: bz#1574606
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 3aead2facfdb0dc580a4bd0556e63bb46b19b01b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jan 18 19:02:07 2018 +0530

    glusterd: enable self-heal in daemons
    
    ..like rebalance, quota and tier because that seems to be the consensus
    (see BZ).
    
    Change-Id: I912336a12f4e33ea4ec55f804df403fab0dc89fc
    BUG: 1536024
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit e2ee5cb2ad9f207d43bcacc4bb5dc460aac5df00
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Apr 23 16:03:42 2018 +0530

    glusterfsd: initiate pmap_signout for all detach brick requests
    
    In glusterfs_handle_terminate all bricks getting detached need to
    initiate a pmap_signout.
    
    Change-Id: Iacbd6fcd49215fe6a5210df7dfed1260fde9179a
    Fixes: bz#1570011
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit af132df34c6e7d74af0947ce3ef391546907f028
Author: Thomas Hindoe Paaboel Andersen <phomes@gmail.com>
Date:   Thu May 3 00:58:02 2018 +0200

    cli/snapshot: ignore errors for snapshot status for ALL/VOL
    
    Currently errors are reported for snapshot status of type ALL and VOL.
    The intention was to ignore those, but the code gets it wrong.
    
    The original condition for ignoring ALL/VOL was removed in
       Bug 1096610
       Change-Id Ifc0ac31d2a9f91e136e87f3b51a629df7dba94e8
    
    And the current logic introduced in
       Bug 789278
       Change-Id I985cea1ef787d239b2632d5a7f467070846f92e4
    
    Change-Id: Ic02ea98fb23b1149264e91b41f2fc2ca916d405f
    Fixes: bz#1574259
    Signed-off-by: Thomas Hindoe Paaboel Andersen <phomes@gmail.com>

commit c63b278947dbc134e08331a097cf2041cf98c545
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Feb 26 11:33:06 2018 +0530

    cli/glusterd: Add warning message in cli for user to check
    
    force-migration config for remove-brick operation.
    
    The cli will take input from the user before starting "remove-brick"
    start operation. The message/confirmation looks like the following:
    
    <Running remove-brick with cluster.force-migration enabled can result
    in data corruption. It is safer to disable this option so that files
    that receive writes during migration are not migrated. Files that are
    not migrated can then be manually copied after the remove-brick commit
    operation. Do you want to continue with your current
    cluster.force-migration settings? (y/n)>
    
    And also question for COMMIT_FORCE is changed.
    
    Fixes: bz#1572586
    Change-Id: Ifdb6b108a646f50339dd196d6e65962864635139
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit f46047ea0f36084f4456887673552a01b926382d
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Apr 24 09:43:09 2018 +0530

    posix: Avoid changelog retries for geo-rep
    
    Problem: georep is slowdown to migrate directory
             from master volume to slave volume due to lot
             of changelog retries
    
    Solution: Update the condition in posix_getxattr to
              ignore MDS_INTERNAL_XATTR as it(posix) ignored
              other internal xattrs
    
    BUG: 1571069
    Change-Id: I4d91ec73e5b1ca1cb3ecf0825ab9f49e261da70e
    fixes: bz#1571069
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 47d2f7296b81fe7d8647e629b782c44bbc9f9678
Author: Ji-Hyeon Gim <potatogim@gluesys.com>
Date:   Thu Feb 1 15:14:42 2018 +0900

    doc: updates Language Bindings for libgfapi-perl and gogfapi
    
    The libgfapi-perl provides declarations and linkage for the Gluster
    gfapi C library with FFI for many Perl mongers
    
    In addition, gogfapi URI link is replaced with GitHub because Forge is
    dead.
    
    Change-Id: I773e78beb201b48ca3fde0dc72d04b64dc9697d6
    Signed-off-by: Ji-Hyeon Gim <potatogim@potatogim.net>
    Updates: #447

commit cfa4ff1417aba42f0dff3fe9d8e17acdaae4ffb2
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Sat May 13 02:45:49 2017 +0200

    Don't use hardcoded /sbin, /usr/bin etc. paths. Fixes #1450546
    
    Instead, rely on programs to be in PATH, as gluster already
    does in many places across its code base.
    
    Change-Id: Id21152fe42f5b67205d8f1571b0656c4d5f74246
    BUG: 1450546
    Signed-off-by: Niklas Hambuechen <mail@nh2.me>

commit 86a0a7e562f4f1c2f5e68c10a917aeaf1d984365
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu May 3 09:34:39 2018 +0530

    cluster/dht: unwind if dht_selfheal_dir_mkdir returns an error
    
    If dht_selfheal_dir_mkdir returns an error, cbk passed to
    dht_selfheal_directory is not invoked. So, Current codepath leaves an
    unwound frame resulting in a hung fop forever.
    
    Change-Id: I422308b8a34a074301ca46b029ffe676f5e0f66c
    fixes: bz#1574305
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 112048652ab00d9650053396c1b28a49d1853783
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Apr 25 16:48:56 2018 +0530

    protocol/server : unwind as per op version
    
    Change-Id: Id6717640ac14881b490e512c4682e45ffffa7f5b
    fixes: bz#1570538
    BUG: 1570538
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 11b747bcec316aad77c68451346e092f33b2f218
Author: Varsha Rao <varao@redhat.com>
Date:   Fri Apr 13 16:16:43 2018 +0530

    glusterd/geo-rep: Fix UNUSED_VALUE coverity issue
    
    The return value of glusterd_get_local_brickpaths is unused so add
    goto statement. As it is reinitialized outside the if block. Also
    change the if condition to check the failure case, when return value
    is -1 and path_list is NULL.
    
    Change-Id: I6b47d7751263f704bd69a6452a7e71bfcf226d49
    updates: bz#789278
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 4e7b423d3c3137c3f83b71b36279e1a544154833
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Apr 13 09:13:16 2018 -0400

    core/various: python3 compat, prepare for python2 -> python3
    
    see https://review.gluster.org/#/c/19788/
    
    use print fn from __future__
    
    Change-Id: If5075d8d9ca9641058fbc71df8a52aa35804cda4
    updates: #411
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 9da91172538a2a95fba609c93e199db159fd1938
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Fri Apr 20 17:26:12 2018 +0530

    block-profile: enable cluster.eager-lock in block-profile
    
    Eager-lock gave 2.5X perf improvement. On top of that with batching
    fix in tcmu-runner and client-io-threads we are seeing close to 3X perf
    improvement. But we don't want to include that in the default profile
    option but enable it on a case by case basis. So not adding
    client-io-threads option.
    
    BUG: 1573119
    Fixes: bz#1573119
    Change-Id: Ida53c3ef9a041a73b65fdd06158ac082da437206
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>

commit 2fd93ccd19d247f27a33d3777dcdac80728a25db
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Apr 30 11:12:34 2018 +0530

    glusterd: Fix for memory leak in get-state detail
    
    Fixes: bz#1573066
    Change-Id: I76fe3bdde7351736b32eb3d6c4cc5f8f276257ed
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit e2fda098112803bf651c4795952376cb8c1ad204
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Apr 27 16:40:02 2018 +0530

    dht: gf_defrag_settle_hash should ignore ENOENT and ESTALE error
    
    Problem: A directory deletion can happen just before gf_defrag_settle_hash
    which internally does a setxattr operation on a directory.
    
    Solution: Ignore ENOENT and ESTALE errors
    
    Fixes: bz#1572581
    Change-Id: I2f91809f3b5e02976c4c3a5a596406a8b2f8f6f2
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 1bf8a8addb61d30177f0d10cec64a9dfcd0add92
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Apr 26 00:58:12 2018 +0530

    cluster/afr: shd changes for thin arbiter
    
    Updates #352
    
    Change-Id: I1bbb3c652ba33cec6aa37f3700370674077fb17d
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit ef89e1b5bb77706b1910a45640b11a4341c78d6a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Apr 2 13:58:23 2018 +0530

    afr: initial changes for thin arbiter
    
    1. Create thin arbiter index file during mount.
    2. Set pending marker in thin arbiter id file in case of failure.
    
    Change-Id: I269eb8d069f0323f1fc616175e5e5eb7b91d5f82
    updates: #352
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 7c6d15af7da4cea510fc2844115730656900e117
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Mar 17 13:16:59 2018 +0530

    server/resolver: don't trust inode-table for RESOLVE_NOT
    
    There have been known races between fops which add a dentry (like
    lookup, create, mknod etc) and fops that remove a dentry (like rename,
    unlink, rmdir etc) due to which stale dentries are left out in inode
    table even though the dentry doesn't exist on backend. For eg.,
    consider a lookup (parent/bname) and unlink (parent/bname) racing in
    the following order:
    
    * lookup hits storage/posix and finds that dentry exists
    * unlink removes the dentry on storage/posix
    * unlink reaches protocol/server where the dentry (parent/bname) is
      unlinked from the inode
    * lookup reaches protocol/server and creates a dentry (parent/bname)
      on the inode
    
    Now we've a stale dentry (parent/bname) associated with the inode in
    itable. This situation is bad for fops like link, create etc which
    invoke resolver with type RESOLVE_NOT. These fops fail with EEXIST
    even though there is no such dentry on backend fs. This issue can be
    solved in two ways:
    
    * Enable "dentry fop serializer" xlator [1].
      # gluster volume set features.sdfs on
    
    * Make sure resolver does a lookup on backend when it finds a dentry
      in itable and validates the state of itable.
       - If a dentry is not found, unlink those stale dentries from itable
         and continue with fop
       - If dentry is found, fail the fop with EEXIST
    
    This patch implements second solution as sdfs is not enabled by
    default in brick xlator stack. Once sdfs is enabled by default, this
    patch can be reverted.
    
    [1] https://github.com/gluster/glusterfs/issues/397
    
    Change-Id: Ia8bb0cf97f97cb0e72639bce8aadb0f6d3f4a34a
    updates: bz#1543279
    BUG: 1543279
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit aa981531458a6d6e279f9a9a26f7c61b24cc14ab
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Apr 26 12:38:23 2018 +0530

    libglusterfs: Capture the dict response in syncop_xattrop_cbk
    
    Problem:
    Currently it is not possible to capture the xattrs values which
    are set on the bricks by calling syncop_(f)xattrop, because the
    response dict is not being assigned to any of the dictionaries.
    
    Fix:
    In the xattrop callback capture the response dict and send it
    back to the caller if it is requested.
    
    Change-Id: I9de9bcd97d6008091c9b060bcca3676cb9ae8ef9
    fixes: bz#1572076
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 69c35dbb4b3b92c60cbce8dff58e9d1399820b0d
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Feb 1 12:18:38 2018 +0530

    feature/thin-arbiter: Implement thin-arbiter translator
    
    Updates #352
    
    Change-Id: I3d8caa6479dc8e48bec62a09b056971bb061f0cf
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 6912441543192a366f264b61d97d50faf3815a28
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Apr 23 19:21:20 2018 +0530

    performance/md-cache: purge cache on ENOENT/ESTALE errors
    
    If not, next lookup could be served from cache and can be success,
    which is wrong. This can affect retry logic of VFS when it receives an
    ESTALE.
    
    Change-Id: Iad8e564d666aa4172823343f19a60c11e4416ef6
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Fixes: bz#1566303

commit 971b386fb575f0a216983ea6cad09c42f9b0fb2f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Apr 13 08:52:06 2018 +0530

    cluster/afr: Keep child-up until ping-event
    
    Problem:
    If we have 2 bricks, brick-A and brick-B with brick-A within halo-max-latency
    and brick-B more than halo-max-latency. If we set both halo-min, halo-max replicas
    as '1'. In this case, brick-A comes online and then ping-latency will be updated for it.
    When brick-B comes online, we have 2 up-bricks, so the code tries to find the brick with
    worst latency to mark it down. Since Brick-B just came online it always had '0' latency
    so brick-B used to be marked offline and Brick-B would eventually be the one to be
    online even when brick-A is more suited.
    
    Fix:
    Consider latency of just-up child as HALO_MAX_LATENCY so that worst-child until
    ping-latency is found as the just-up brick. Also keep ping-latency as -1 until
    child-up during initialization.
    
    BUG: 1567881
    fixes bz#1567881
    Change-Id: I148262fe505468190f0eb99225d0f6d57cdb6f04
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 93464ffd6dcbe2a2f91c0e35f933f814f523e9be
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 23 21:04:58 2018 +0530

    libglusterfs/syncop: Handle barrier_{init/destroy} in error cases
    
    BUG: 1568521
    updates: bz#1568521
    Change-Id: I53e60cfcaa7f8edfa5eca47307fa99f10ee64505
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit afadc4d6f4cd52651c2849bc8337fc66ce8c72e6
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Apr 17 22:14:20 2018 +0530

    features/shard: Add option to barrier parallel lookup and unlink of shards
    
    Also move the common parallel unlink callback for GF_FOP_TRUNCATE and
    GF_FOP_FTRUNCATE into a separate function.
    
    Change-Id: Ib0f90a5f62abdfa89cda7bef9f3ff99f349ec332
    updates: bz#1568521
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 62437c99618551d531103023883b5cabcca20fa6
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Apr 17 15:37:05 2018 +0530

    cluster/dht: Fix dht_rename lock order
    
    Fixed dht_order_rename_lock to use the same inodelk ordering
    as that of the dht selfheal locks (dictionary order of
    lock subvolumes).
    
    Change-Id: Ia3f8353b33ea2fd3bc1ba7e8e777dda6c1d33e0d
    fixes: bz#1568348
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit bca55ab1bfcd2889f8387ba8bcab27766e1b94ac
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Apr 2 12:20:47 2018 +0530

    server/auth: add option for strict authentication
    
    When this option is enabled, we will check for a matching
    username and password, if not found then the connection will
    be rejected. This also does a checksum validation of volfile
    
    The option is invalid when SSL/TLS is in use, at which point
    the SSL/TLS certificate user name is used to validate and
    hence authorize the right user. This expects TLS allow rules
    to be setup correctly rather than the default *.
    
    This option is not settable, as a result this cannot be enabled
    for volumes using the CLI. This is used with the shared storage
    volume, to restrict access to the same in non-SSL/TLS environments
    to the gluster peers only.
    
    Tested:
      ./tests/bugs/protocol/bug-1321578.t
      ./tests/features/ssl-authz.t
      - Ran tests on volumes with and without strict auth
        checking (as brick vol file needed to be edited to test,
        or rather to enable the option)
      - Ran tests on volumes to ensure existing mounts are
        disconnected when we enable strict checking
    
    Change-Id: I2ac4f0cfa5b59cc789cc5a265358389b04556b59
    fixes: bz#1568844
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 3dbb6b5d6093357ed430fba4cc17ac2d8eb99b32
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Mar 26 20:27:34 2018 +0530

    shared storage: Prevent mounting shared storage from non-trusted client
    
    gluster shared storage is a volume used for internal storage for
    various features including ganesha, geo-rep, snapshot.
    
    So this volume should not be exposed to the client, as it is
    a special volume for internal use.
    
    This fix wont't generate non trusted volfile for shared storage volume.
    
    Change-Id: I8ffe30ae99ec05196d75466210b84db311611a4c
    fixes: bz#1568844
    BUG: 1568844
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 408a6d07ababde234ddeafe16687aacd2b810b42
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Apr 20 12:16:32 2018 +0530

    server: fix unresolved symbols by moving them to libglusterfs
    
    Problem: glusterd2 build is failed due to undefined symbol
             (xlator_mem_cleanup , glusterfsd_ctx) in server.so
    
    Solution: To resolve the same done below two changes
              1) Move xlator_mem_cleanup code from glusterfsd-mgmt.c
                 to xlator.c to be part of libglusterfs.so
              2) replace glusterfsd_ctx to this->ctx because symbol
                 glusterfsd_ctx is not part of server.so
    
    BUG: 1544090
    Change-Id: Ie5e6fba9ed458931d08eb0948d450aa962424ae5
    fixes: bz#1544090
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit ab42a3551eba623e11a942bf44d41dd393bfee9b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Apr 19 17:13:17 2018 +0530

    cluster/afr: Need heal-timeout to be configured as low as 5 seconds
    
    In Halo replication, there are pending heals more often than not.
    It makes sense to give users the capability to configure it as low
    as 5 seconds.
    
    BUG: 1569489
    fixes bz#1569489
    Change-Id: I451c1975827f66398b903f659c981ef3121d5376
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 3e8425b5643326e16ce283109edc5f516e21d7f7
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Apr 18 15:18:43 2018 -0400

    features/bitrot: show the corresponding brick for the corrupted objects
    
    Currently with "gluster volume bitrot <volume name> scrub status" command
    the corrupted objects of a node are shown. But to what brick that corrupted
    object belongs to is not shown. Showing the brick of the corrupted object
    will help in situations where a node hosts multiple bricks of a volume.
    
    Change-Id: I7fbdea1e0072b9d3487eb10757468bc02d24df21
    fixes: bz#1569198
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>

commit ef8f9ad76a5a1c9495a77e7e83b7fd05a9a7e757
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Apr 18 15:08:55 2018 +0530

    eventsapi: Handle Unicode string during signing
    
    Python 2.7 HMAC does not support Unicode strings. Secret is read
    from file so it is possible that glustereventsd reads the content
    as Unicode. This patch converts the secret to `str` type before
    generating HMAC signature.
    
    Fixes: bz#1568820
    Change-Id: I7daa64499ac4ca02544405af26ac8af4b6b0bd95
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 9e7082b756058fe04d79c046fbd6dcbfa75a1716
Author: Prashanth Pai <ppai@redhat.com>
Date:   Thu Apr 19 12:50:20 2018 +0530

    Make glusterfsd binary print statedump & xlator dir
    
    The glusterd2 needs following options, some of which are provided by
    gluster CLI today:
    
    --print-xlatordir
    --print-statedumpdir
    --print-logdir
    
    However, the CLI package need not be present on the machine running
    glusterd2. This change adds the above CLI options to glusterfsd binary
    which glusterd2 depends on.
    
    Reverts 9a1ae47c8d60836ae0628a04a153f28c1085c0e8
    
    Related changes:
    https://review.gluster.org/#/c/19882/
    https://github.com/gluster/glusterd2/pull/663
    
    Updates: bz#1193929
    Change-Id: I18c123b0d3350d2bd4f2400783e3b94e402a4e29
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit 0043c63f70776444f69667a4ef9596217ecb42b7
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Mar 12 19:43:15 2018 +0530

    gluster: Sometimes Brick process is crashed at the time of stopping brick
    
    Problem: Sometimes brick process is getting crashed at the time
             of stop brick while brick mux is enabled.
    
    Solution: Brick process was getting crashed because of rpc connection
              was not cleaning properly while brick mux is enabled.In this patch
              after sending GF_EVENT_CLEANUP notification to xlator(server)
              waits for all rpc client connection destroy for specific xlator.Once rpc
              connections are destroyed in server_rpc_notify for all associated client
              for that brick then call xlator_mem_cleanup for for brick xlator as well as
              all child xlators.To avoid races at the time of cleanup introduce
              two new flags at each xlator cleanup_starting, call_cleanup.
    
    BUG: 1544090
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    
    Note: Run all test-cases in separate build (https://review.gluster.org/#/c/19700/)
          with same patch after enable brick mux forcefully, all test cases are
          passed.
    
    Change-Id: Ic4ab9c128df282d146cf1135640281fcb31997bf
    updates: bz#1544090

commit be26b0da2f1a7fe336400de6a1c016716983bd38
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Apr 11 17:38:26 2018 +0530

    glusterd: volume inode/fd status broken with brick mux
    
    Problem:
    The values for inode/fd was populated from the ctx received
    from the server xlator.
    Without brickmux, every brick from a volume belonged to a
    single brick from the volume.
    So searching the server and populating it worked.
    
    With brickmux, a number of bricks can be confined to a single
    process. These bricks can be from different volumes too (if
    we use the max-bricks-per-process option).
    If they are from different volumes, using the server xlator
    to populate causes problem.
    
    Fix:
    Use the brick to validate and populate the inode/fd status.
    
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    
    Change-Id: I2543fa5397ea095f8338b518460037bba3dfdbfd
    fixes: bz#1566067

commit 054cecc30676017f83a18847734d9fe0fcb8ea72
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Mar 28 12:09:27 2018 +0530

    features/shard: Make operations on internal directories generic
    
    Change-Id: Iea7ad2102220c6d415909f8caef84167ce2d6818
    updates: bz#1568521
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 87bcdd9465b140e0b9d33dadf3384e28b7b6ed9f
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Apr 11 23:14:02 2018 +0530

    fuse: do fd_resolve in fuse_getattr if fd is received
    
    problem: With the current code, post graph switch the old fd is received for
    fuse_getattr and since it is associated with old inode, it does not
    have the inode ctx across xlators in new graph. Hence, dht
    errored out saying "no layout" for fstat call. Hence the EINVAL.
    
    Solution: if fd is passed, init and resolve fd to carry on getattr
    
    test case:
    - Created a single brick distributed volume
    - Started untar
    - Added a new-brick
    
    Without this fix, untar used to abort with ERROR.
    
    Change-Id: I5805c463fb9a04ba5c24829b768127097ff8b9f9
    fixes: bz#1566207
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit d9cf6d25a4719c4f6fb4d88325f08e49fca18e6b
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Apr 16 11:26:40 2018 +0530

    glusterd: update listen-backlog value to 1024
    
    Update default value of listen-backlog to 1024 to reflect the changes in
    socket.c
    
    This keeps the actual implementation in socket.c and the help text in
    glusterd-volume-set.c consistent
    
    Change-Id: If04c9e0bb5afb55edcc7ca57bbc10922b85b7075
    fixes: bz#1564600
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit a7525c507eb682d317dafaa7d06ba59b2c50048d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Apr 13 00:16:22 2018 +0530

    cluster/afr: Make sure latency-arg is passed to afr
    
    xlator_notify doesn't pass the extra arguments that come in the
    input function, so XLATOR_NOTIFY macro should be used instead
    to pass the extra arguments to the function.
    
    BUG: 1567881
    fixes bz#1567881
    Change-Id: Ic15b6c446638cbacf3149693147a754219037c47
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 52d1b36e3738b7117c5ecf0a83ceba1438fad68a
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Thu Apr 12 23:31:37 2018 +0200

    libglusterfs: fix comparison of a NULL dict with a non-NULL dict
    
    Function are_dicts_equal() had a bug when the first argument was NULL and
    the second one wasn't NULL. In this case it incorrectly returned that the
    dicts were different when they could be equal.
    
    Fixes: bz#1566732
    Change-Id: I0fc245c2e7d1395865a76405dbd05e5d34db3273
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 9a1ae47c8d60836ae0628a04a153f28c1085c0e8
Author: Prashanth Pai <ppai@redhat.com>
Date:   Mon Apr 16 11:55:02 2018 +0530

    Add CLI option to print XLATORDIR
    
    glusterfs gets the path to xlator dir from a compile time flag named
    XLATORDIR which gets passed through a -D flag to GCC. This path is
    used to find and load xlator shared objects.
    
    The XLATORDIR path isn't easily accessible to glusterd2. Glusterd2
    currently uses the following command (hack) to get value of XLATORDIR:
    
    $ strings -d `which glusterfsd` | awk '/glusterfs/*/xlator$/'
    
    This change introduces "print-xlatordir" CLI option to expose
    XLATORDIR. The option is intentionally not documented.
    
    Updates: bz#1193929
    Change-Id: Ic7247457600f11cd8d68eb3d0ad2526fdfda0b02
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit 7b0781a45bba826a790aa4d5a125693ac2be28ab
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Apr 16 15:38:34 2018 +0530

    afr: fixes to afr-eager locking
    
    1. If pre-op fails on all bricks,set lock->release to true in
    afr_handle_lock_acquire_failure so that the GF_ASSERT in afr_unlock() does not
    crash.
    
    2. Added a missing 'return' after handling pre-op failure in
    afr_transaction_perform_fop(), fixing a use-after-free issue.
    
    Change-Id: If0627a9124cb5d6405037cab3f17f8325eed2d83
    fixes: bz#1561129
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit e96695de4354fb58775d5baa50f07651c0592f0f
Author: Nigel Babu <nigelb@redhat.com>
Date:   Wed Apr 18 10:37:46 2018 +0530

    Revert "storage/posix: add pgfid in readdirp if needed"
    
    This reverts commit d206fab73f6815c927a84171ee9361c9b31557b1.
    
    Change-Id: I5b43fdcf916bc844437c9d60f6957bc40936e3c2
    Updates: bz#1560319
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit b2f94254cdba07658efb9052ba585ca83d7f1cfe
Author: Xie Changlong <xiechanglong@cmss.chinamobile.com>
Date:   Tue Apr 10 10:26:01 2018 +0800

    build: exclude '--with-previous-options' to prevent infinite loop
    
    Reproducible Steps:
    1. cd glusterfs/; rm -rf *; git reset --hard #clean repo
    2. cd extras/LinuxRPM/; ./make_glusterrpms #it's ok here
    3. ./make_glusterrpms #infinite loop
    4. cd ../../; make distclean #infinite loop
    
    Change-Id: I162953d4576cedea7c6f6c631a77163a5cca023e
    updates: #439
    Signed-off-by: Xie Changlong <xiechanglong@cmss.chinamobile.com>

commit 7438f1f2a103a64e2349ad3ba9401cf115ca9de1
Author: Nigel Babu <nigelb@redhat.com>
Date:   Mon Apr 16 09:20:42 2018 +0530

    maintainers: promote Deepshikha to maintainer
    
    Deepshikha has been doing excellent work across the CI system. She is
    now ready to co-maintain the Continuous Integration module and be
    responsible for the CI ecosystem in its entirety.
    
    Fixes: bz#1567880
    Change-Id: If204301d26731f93b2dccfe8b6571ee748a47b26
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit 4892349e775ae121d8829251613c399300076f33
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat Apr 14 08:22:48 2018 +0200

    fuse: retire statvfs tweak
    
    fuse xlator used to override the  filesystem
    block size of the storage backend to indicate
    its preferences. Now we retire this tweak and
    pass on what we get from the backend.
    
    This fixes the anomaly reported in the referred
    BUG. For more background, see the following email,
    which was sent out to gluster-devel and gluster-users
    mailing lists to gauge if anyone sees any use of
    this tweak:
    
    http://lists.gluster.org/pipermail/gluster-devel/2018-March/054660.html
    http://lists.gluster.org/pipermail/gluster-users/2018-March/033775.html
    
    Noone vetoed the removal of it but it got endorsement:
    
    http://lists.gluster.org/pipermail/gluster-devel/2018-March/054686.html
    
    BUG: 1523219
    Change-Id: I3b7111d3037a1b91a288c1589f407b2c48d81bfa
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit a723362d87a81da5d97cc879cc1d24a48351ca84
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 13 10:52:14 2018 -0400

    geo-rep: Fix syncing of symlink
    
    Problem:
    If symlink is created on master pointing
    to current directory (e.g symlink -> ".") with
    non root uid or gid, geo-rep worker crashes
    with ENOTSUP.
    
    Cause:
    Geo-rep creates the symlink on slave and
    fixes the uid and gid using chown cmd.
    os.chown dereferences the symlink which is
    pointing to ".gfid" which is not supported.
    Note that geo-rep operates on aux-gfid-mount
    (e.g. "/mnt/.gfid/<gfid-of-symlink-file>").
    
    Solution:
    The uid or gid change is acutally on symlink
    file. So use os.lchown, i.e, don't deference.
    
    BUG: 1567209
    Change-Id: I63575fc589d71f987bef1d350c030987738c78ad
    updates: bz#1567209
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit c3e1a2e861045a99b9148a0ba5d60777d86f861d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 12 13:41:29 2018 +0530

    extras: Disable choose-local in groups virt and gluster-block
    
    Change-Id: Icba68406d86623195d59d6ee668e0850c037c63a
    fixes: bz#1566386
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 31da3f1d8513b10d0449a1855fbad5060bd6191d
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Apr 9 11:26:05 2018 +0530

    rpc: set listen-backlog to high value
    
    Problem:
    On node reboot, when glusterd starts volumes rapidly, there's a flood of
    connections from the bricks to glusterd and from the self-heal daemons
    to the bricks. This causes SYN Flooding and dropped connections when the
    listen-backlog is not enough to hold the pending connections to
    compensate for the rate at which connections are accepted by the RPC
    layer.
    
    Solution:
    Increase the listen-backlog value to 1024. This is a partial solution.
    Part of the solution is to rearm the listener socket early for quicker
    accept() of connections.
    See commit 6964640a977cb10c0c95a94e03c229918fa6eca8 (change 19833)
    
    Change-Id: I62283d1f4990dd43839f9a6932cf8a36effd632c
    fixes: bz#1564600
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 1f0765242a689980265c472646c64473a92d94c0
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Apr 6 16:06:51 2018 +0530

    cluster/dht: Handle file migrations when brick down
    
    The decision as to which node would migrate a file
    was based on the gfid of the file. Files were divided
    among the nodes for the replica/disperse set. However,
    if a brick was down when rebalance started, the nodeuuids
    would be saved as NULL and a set of files would not be migrated.
    
    Now, if the nodeuuid is NULL, the first non-null entry in
    the set is the node responsible for migrating the file.
    
    Change-Id: I72554c107792c7d534e0f25640654b6f8417d373
    fixes: bz#1564198
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 29024cfdd5f131c7e3085cbddf9bd1cf60359960
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Mar 28 10:14:39 2018 -0400

    core/build/various: python3 compat, prepare for python2 -> python3
    
    Note 1) we're not supposed to be using #!/usr/bin/env python, see
    https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#Shebang_lines
    
    Note 2) we're also not supposed to be using "!/usr/bin/python,
    see https://fedoraproject.org/wiki/Changes/Avoid_usr_bin_python_in_RPM_Build#Quick_Opt-Out
    
    The previous patch (https://review.gluster.org/19767) tried to do too
    much in one patch, so it was abandoned.
    
    This patch does two things:
    1) minor cleanup of configure(.ac) to explicitly use python2
    2) change all the shebang lines to #!/usr/bin/python2 and add them
    where they were missing based on warnings emitted during rpmbuild.
    
    In a follow-up patch python2 will eventually be changed to python3.
    
    Before that python2-isms (e.g. print, string.join(), etc.) need to be
    converted to python3. Some of those can be rewritten in version agnostic
    python. E.g. print statements become print() with "from __future_ import
    print_function". The python 2to3 utility will be used for some of those.
    Also Aravinda has given guidance in the comments to the first patch for
    changes.
    
    updates: #411
    Change-Id: I471730962b2526022115a1fc33629fb078b74338
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit c4251edec654b4e0127577e004923d9729bc323d
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Apr 5 21:41:44 2018 +0530

    cluster/dht: Wind open to all subvols
    
    dht_opendir should wind the open to all subvols
    whether or not local->subvols is set. This is
    because dht_readdirp winds the calls to all subvols.
    
    Change-Id: I67a96b06dad14a08967c3721301e88555aa01017
    updates: bz#1564198
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 909e2cdf06fbd7b4161fff402fc6ef7b5e189c21
Author: Varsha Rao <varao@redhat.com>
Date:   Fri Mar 16 14:23:25 2018 +0530

    xlators/performance: Add pass-through option
    
    Add pass-through option in performance traslators. Set the option in
    GF_OPTION_INIT() and GF_OPTION_RECONF()
    
    Updates: #304
    
    Change-Id: If1537450147d154905831e36f7162a32866d7ad6
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 0002c36666c9b043a330ee08533a87fe7fd16491
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Mar 26 12:55:12 2018 +0530

    posix: reserve option behavior is not correct while using fallocate
    
    Problem: storage.reserve option is not working correctly while
             disk space is allocate throguh fallocate
    
    Solution: In posix_disk_space_check_thread_proc after every 5 sec interval
              it calls posix_disk_space_check to monitor disk space and set the
              flag in posix priv.In 5 sec timestamp user can create big file with
              fallocate that can reach posix reserve limit and no error is shown on
              terminal even limit has reached.
              To resolve the same call posix_disk_space for every fallocate fop
              instead to call by a thread after 5 second
    
    BUG: 1560411
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Change-Id: I39ba9390e2e6d084eedbf3bcf45cd6d708591577

commit d206fab73f6815c927a84171ee9361c9b31557b1
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Mon Apr 9 08:33:51 2018 -0400

    storage/posix: add pgfid in readdirp if needed
    
    Change-Id: I6745428fd9d4e402bf2cad52cee8ab46b7fd822f
    fixes: bz#1560319
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 25b8139c74ae3127905a86dd5f834c39746ad8d7
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Mar 16 10:15:52 2018 +0530

    posix: check file state before continuing with fops
    
    In context of Cloudsync:
    
     In scenarios where a data modification fop e.g. a write landed in
    POSIX thinking that the file is local, while the file was actually
    remote, can be dangerous. Ofcourse we don’t want to take inodelk
    for every read/write operation to check the archival status or
    coordinate with an upload or a  download of a file. To avoid inodelk,
    we will check the status of the file in POSIX it self, before we
    resume the fop. This helps us avoiding any races mentioned above.
    Now e.g. if a write reached POSIX for a file which was actually remote,
    it can check the status of the file and will get to know that the file
    is remote.  It can error out with this status “remote” and cloudsync
    xlator will retry the same operation, once it finished downloading the
    file.
    
    This patch includes the setxattr changes to do the post processing of
    upload i.e. truncate and setting the remote xattr
    "trusted.glusterfs.cs.remote" to indicate the file is REMOTE
    
    Each file will have no xattr if the file is LOCAL, one remote xattr if
    the file is REMOTE and a combination of REMOTE and DOWNLOADING xattr if
    the file is getting downloaded. There is healing logic of these xattrs
    to recover from crash inconsitencies.
    
    Fixes: #387
    Change-Id: Ie93c2d41aa8d6a798a39bdbef9d1669f057e5fdb
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 13c8bf60155b5ab09d60d4a04f2b0d38014e5fca
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Apr 4 10:03:18 2018 +0530

    cluster/dht: act as passthrough for renames on single child DHT
    
    Various synchronization present in dht_rename while handling
    directories and files is necessary only if we have more than only one
    child.
    
    Change-Id: Ie21ad419125504ca2f391b1ae2e5c1d166fee247
    fixes: bz#1563511
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 48623a33a0ef38f6c99208b0580954d7d7c80e76
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Mar 9 20:07:19 2018 +0530

    experimental/cloudsync: Download xlator for archival feature
    
    spec-files:
    https://review.gluster.org/#/c/18854/
    
    Overview:
    * Cloudsync maintains three file states in it's inode-ctx i.e
      1 - LOCAL,
      2 - REMOTE,
      3 - DOWNLOADING.
    
    * A data modifying fop is allowed only if the state is LOCAL.
      If the state is REMOTE or DOWNLOADING, client will download
      or wait for the download to finish initiated by other client.
    
    * Multiple download and upload from different clients are synchronized
      by inodelk.
    
    * In POSIX a state check is done (part of different commit)before
      allowing the fop to continue. If the state is remote/downloading the
      fop is unwound with EREMOTE. The client will then download the file
      and continue with the fop again.
    
    * Basic Algo for fop (let's say write fop):
      - If LOCAL -> resume fop
      - If REMOTE ->
    	- INODELK
    	- STAT (this gets state and heal the state if needed)
    	- DOWNLOAD
    	- resume fop
    
    Note:
    * Developers will need to write plugins for download, based on the
    remote store they choose. In phase-1, support will be added for
    one remote store per volume. In future, more options for multiple
    remote stores will be explored.
    
    TODOs:
     - Implement stat/lookup/readdirp to return size info from xattr
     - Make plugins configurable
     - Implement unlink fop
     - Add metrics collection
     - Add sharding support
    
    Design Contributions:
    Aravinda V K <avishwan@redhat.com>
    Amar Tumballi <amarts@redhat.com>
    Ram Ankireddypalle <areddy@commvault.com>
    Susant Palai <spalai@redhat.com>
    
    updates: #387
    Change-Id: Iddf711ee7ab4e946ae3e472ff62791a7b85e6d4b
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit f946d98a95249c8d906323e6419ec8538467d2ab
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Mar 13 06:50:48 2018 -0400

    quota: allow writes when with EINVAL on pgfid isnot exist
    
    NFS client gets "Invalid argument" when writing file through nfs-ganesha.
    
    1. With quota disabled;
    nfs client mount nfs-ganesha share, and do 'll' in the testing directory.
    
    2. Enable quota;
    getfattr: Removing leading '/' from absolute path names
    trusted.gfid=0xe2edaac0eca8420ebbbcba7e56bbd240
    trusted.gfid2path.b3250af8fa558e66=0x39663134343566662d653530332d343831352d396635312d3236633565366332633137642f7465737466696c653932
    trusted.glusterfs.quota.9f1445ff-e503-4815-9f51-26c5e6c2c17d.contri.3=0x00000000000002000000000000000001
    
    Notice: testfile92 without trusted.pgfid xattr.
    
    3. restart glusterfs volume by "gluster volume stop/start gvtest"
    4. echo somedata > testfile92
    5. ll testfile92
    -rw-r--r-- 1 root root    0 Mar  6 21:43 testfile92
    
    BUG: 1560319
    Change-Id: Iaa4dd1e891c99069fb85b7b11bb0482cbf2303b1
    fixes: bz#1560319
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 6964640a977cb10c0c95a94e03c229918fa6eca8
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Apr 6 23:19:07 2018 +0530

    rpc: rearm listener socket early
    
    Problem:
    On node reboot, when glusterd starts volumes, a setup with a large
    number of bricks might cause SYN Flooding and connections to be dropped
    if the connections are not accepted quickly enough.
    
    Solution:
    accept() the connection and rearm the listener socket early to receive
    more connection requests as soon as possible.
    
    Change-Id: Ibed421e50284c3f7a8fcdb4de7ac86cf53d4b74e
    fixes: bz#1564600
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit bb12f2109a01856e8184e13cf984210d20155b13
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 21 18:06:54 2018 +0530

    features/index: Choose different base file on EMLINK error
    
    Change-Id: I4648816af908539efdc2528608aa2ebf7f0d0e2f
    fixes: bz#1559004
    BUG: 1559004
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit a1ca39df0b5127376a7df55c3ccebddef993f6fd
Author: Varsha Rao <varao@redhat.com>
Date:   Thu Apr 5 11:26:12 2018 +0530

    doc: Update the admin guide link
    
    Update the existing admin guide link as it is incorrect.
    
    Change-Id: I05669192623aeac287dfa9002caa0f390ea79499
    Updates: bz#1193929
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 351572de9f08ba378d14552538763acec8917e53
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Apr 5 12:09:56 2018 +0530

    cluster/ec: Turn ON the stripe-cache option by default
    
    Change-Id: I0a290396c30c635b13ee73004d20259efb76a954
    fixes: bz#1563945
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 87c51a17a4a9d787db0ee8ed5f81e0250d2e643e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 5 14:50:45 2018 -0400

    gfapi: fix a couple of minor issues
    
    duplicatation of exported functions in gfapi.map. Only the newest one
    is needed. Both the legacy and current symbols are exported.
    
    glfs_io_cbk34 typedef should not be in a public header file. The old
    application was compiled with the original glfs_io_cbk. Outside of
    libgfapi, nothing now uses/needs this old typedef, move it into the
    C file that needs it.
    
    Similarly glfs_realpath34() decl should not be in glfs.h. Period. Old
    applications were compiled with the then glfs_realpath() decl and
    linked with glfs_realpath@@GFAPI_3_4.0. New applications should only
    call glfs_realpath() and it will be linked to the new/current
    glfs_realpath().
    
    Change-Id: Icd5b0c9e9b68f0c133f14447b09ace35f33dbab2
    fixes: bz#1564235
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit ed51b60c6b33024885d9876b23cb6554055e49a1
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Apr 1 22:10:30 2018 +0530

    glusterd: show brick online after port registration
    
    gluster-block project needs a dependency check to see if all the bricks
    are online before bringing up the relevant gluster-block services. While
    the patch https://review.gluster.org/#/c/19785/ attempts to write the
    script but brick should be only marked as online only when the
    pmap_signin is completed.
    
    While this is perfectly fine for non brick multiplexing, but with brick
    multiplexing this patch still doesn't eliminate the race completely as
    the attach_req call is asynchrnous and glusterd immediately marks the
    port as registerd.
    
    Change-Id: I81db54b88f7315e1b24e0234beebe00de6429f9d
    Fixes: bz#1563273
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit d9ceaf3203ffafb4bfe4693b47df1259abbd167a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Mar 27 20:54:25 2018 +0530

    afr: add quorum checks in pre-op
    
    Problem:
    We seem to be winding the FOP if pre-op did not succeed on quorum bricks
    and then failing the FOP with EROFS since the fop did not meet quorum.
    This essentially masks the actual error due to which pre-op failed. (See
    BZ).
    
    Fix:
    Skip FOP phase if pre-op quorum is not met and go to post-op.
    
    Fixes: 1561129
    
    Change-Id: Ie58a41e8fa1ad79aa06093706e96db8eef61b6d9
    fixes: bz#1561129
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit d70529701f09f89c7e4f578446d55de31497361d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Mar 27 16:53:33 2018 +0530

    glusterd: mark port_registered to true for all running bricks with brick mux
    
    glusterd maintains a boolean flag 'port_registered' which is used to determine
    if a brick has completed its portmap sign in process. This flag is (re)set in
    pmap_sigin and pmap_signout events. In case of brick multiplexing this flag is
    the identifier to determine if the very first brick with which the process is
    spawned up has completed its sign in process. However in case of glusterd
    restart when a brick is already identified as running, glusterd does a
    pmap_registry_bind to ensure its portmap table is updated but this flag isn't
    which is fine in case of non brick multiplex case but causes an issue if
    the very first brick which came as part of process is replaced and then
    the subsequent brick attach will fail. One of the way to validate this
    is to create and start a volume, remove the first brick and then
    add-brick a new one. Add-brick operation will take a very long time and
    post that the volume status will show all other brick status apart from
    the new brick as down.
    
    Solution is to set brickinfo->port_registered to true for all the
    running bricks when brick multiplexing is enabled.
    
    Change-Id: Ib0662d99d0fa66b1538947fd96b43f1cbc04e4ff
    Fixes: bz#1560957
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 1dfd17216ddd11d85842380f4afbb9267bd597c6
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Mar 26 13:39:55 2018 +0530

    features/changelog: Update option levels
    
    Options levels for Changelog Xlator
    
    Change-Id: Idd246717e38096c44258a990a0939f82e5fc9654
    Updates: #430
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 09ff538b68cfcfe6b9f222c76ce653bcfecc8b57
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Mar 16 20:54:15 2018 +0530

    cluster/dht: enable lookup-optimize by default
    
    Lookup-optimize has been shown to improve create
    performance. The code has been in the project for several
    years and is considered stable.
    
    Enabling this by default in order to test this in the
    upstream regression runs.
    
    Change-Id: Iab792979ee34f0af4713931e0b5b399c23f65313
    updates: bz#1557435
    BUG: 1557435
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit c7e03a2caae5a776ec55443f15489de8195b9817
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Apr 1 10:10:41 2018 +0530

    glusterd: fix txn_opinfo memory leak
    
    For transactions where there's no volname involved (eg : gluster v
    status), the originator node initiates with staging phase and what that
    means in op-sm there's no unlock event triggered which resulted into a
    txn_opinfo dictionary leak.
    
    Credits : cynthia.zhou@nokia-sbell.com
    
    Change-Id: I92fffbc2e8e1b010f489060f461be78aa2b86615
    Fixes: bz#1550339
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 089351f3d80d37cf2d46f05211191bef5232c12c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 3 21:28:37 2018 +0530

    glusterd: honour localtime-logging for all the daemons
    
    Change-Id: I97a70d29365b0a454241ac5f5cae56d93eefd73a
    Fixes: bz#1563334
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 277d3058a1b9fdd345b6712d84eb9fd9453dd9d6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 29 21:28:33 2018 +0530

    cluster/afr: Prevent ping-event handling on shd
    
    On shd, we shouldn't treat any brick down based
    on latency, otherwise self-heal will never happen
    
    fixes: bz#1562717
    Change-Id: Ica07fcc4fae91a6bfd9c9a670e2be464704d94b7
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 64376e107733e129497cd200a69725c489e9b286
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Apr 2 20:30:16 2018 +0530

    glusterd: setting mgmt_v3_timer->timer to NULL after deleting mgmt_v3_timer
    
    We are setting mgmt_v3_timer->timer to NULL after mgmt_v3_timer is deleted
    which is unnecessary. So removing the statement.
    
    This issue is caught while running glusterd with ASAN.
    
    Change-Id: Ied1f91590a2c64ec1af36d4de9c3febd6cf94bb9
    Fixes: bz#1562907
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f8d1148b7c5eb77558d279967146048f48fa392e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Apr 2 12:09:44 2018 +0530

    mount/fuse: Set default fuse reader thread count to 1
    
    Updates #412
    
    Change-Id: Ida53d8b630feabb856a3551fa888f92382ade768
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 9b8de6421e550f7dc106953d43e0af60fca9be89
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Mar 30 00:14:19 2018 +0200

    ocf: use glusterd-workdir for finding volume status files
    
    The volume status files are located in the glusterd-workdir, not under
    /etc (sysconfdir).
    
    BUG: 1234873
    Change-Id: Id7f7c83261bb4b5ac2fc104dcd6cb198d6a930aa
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 3e3ca8307ee773e0348549a3204478cac3c46f70
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Mar 28 09:01:05 2018 -0400

    build: revert configure --without-ipv6-default behaviour
    
    patch https://review.gluster.org/19692 breaks gluster on systems with
    IPv6 enabled but don't have IPv6 reverse DNS. Also it defaulted to
    enabling ipv6-default regardless of whether --with-ipv6-default or
    --without-ipv6-default were specified in the options to configure.
    (Also the patch was merged without review.)
    
    Prefer libtirpc over glibc rpc.
    
    On newer linux with tirpc and without glibc rpc use tirpc (obviously)
    
    on less new linux with both tirpc and glibc rpc default to use tirpc,
    unless --without-tirpc is specified, in which case use glibc rpc
    
    On less new linux without tirpc fall back to glib rpc (obviously)
    
    ipv6-default requires libtirpc. It is off by default. It must be
    explicitly enabled with --with-ipv6-default. If --with-ipv6-default is
    specified, but tirpc is not available, disable it and issue a warning
    
    Change-Id: Ib96a230fafb83ec83a71948fe55af1215a7a6ffa
    BUG: 1562052
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit d0fbe01f96012b568b96b9e3b374a27ce26734a0
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Mar 26 13:20:17 2018 +0530

    cluster/dht: Update dht option levels
    
    Set the levels for DHT options based on
    https://review.gluster.org/#/c/19466/
    
    Change-Id: I51b31a706a0b9517404e83224c89de145fd5d7e1
    updates: #430
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 08fadcc2a706342e4eee79dc7d9b48ba01fcb312
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 9 15:11:00 2018 +0530

    mount/fuse: Add support for multi-threaded fuse readers
    
    Usage: Use 'reader-thread-count=<NUM>' as command line option to
    set the thread count at the time of mounting the volume.
    
    Next task is to make these threads auto-scale based on the load,
    instead of having the user remount the volume everytime to change
    the thread count.
    
    Updates #412
    
    Change-Id: I94aa1505e5ae6a133683d473e0e4e0edd139b76b
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 25690197a6af67669346892c36cca471805b9305
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Mar 29 18:23:13 2018 +0530

    cluster/dht: Update layout in inode only on success
    
    With lookup-optimize enabled, gf_defrag_settle_hash in rebalance
    sometimes flips the on-disk layout on volume root post the
    migration of all files in the directory.
    
    This is sometimes seen when attempting to fix the layout of a
    directory multiple times before calling gf_defrag_settle_hash.
    dht_fix_layout_of_directory generates a new layout in memory but
    updates it in the inode ctx before it is set on disk. The layout
    may be different the second time around due to
    dht_selfheal_layout_maximize_overlap. If the layout is then not
    written to the disk, the inode now contains the wrong layout.
    gf_defrag_settle_hash does not check the correctness of the layout
    in the inode before updating the commit-hash and writing it to the
    disk thus changing the layout of the directory.
    
    Change-Id: Ie1407d92982518f2a0c40ec70ad370b34a87b4d4
    updates: bz#1557435
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 3f9851db49ca6ac7a969817964a6ad216b10fd6f
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Mar 29 10:48:32 2018 +0000

    Revert "glusterd: handling brick termination in brick-mux"
    
    This reverts commit a60fc2ddc03134fb23c5ed5c0bcb195e1649416b.
    
    This commit was causing multiple tests to time out when brick
    multiplexing is enabled. With further debugging, it's found that even
    though the volume stop transaction is converted into mgmt_v3 to allow
    the remote nodes to follow the synctask framework to process the command,
    there are other callers of glusterd_brick_stop () which are not synctask
    based.
    Change-Id: I7aee687abc6bfeaa70c7447031f55ed4ccd64693
    updates: bz#1545048

commit c87bd439ef12adc70dc580e75304121c3cd38e9a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 22 17:55:15 2018 +0530

    afr: add new value for read-hash-mode volume option
    
    Updates: #363
    
    This new value (3) will try to wind read requests to the child of AFR
    having the least amount of pending requests in its queue.
    
    Change-Id: If6bda2aac9bf7aec3fc39622f78659313c4b6508
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 89577d8b0ad7bd1ee2cec2f0e047591b1cd0f7b8
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Wed Mar 28 11:34:49 2018 +0200

    cluster/ec: send list-node-uuids request to all subvolumes
    
    The xattr trusted.glusterfs.list-node-uuids was only sent to a single
    subvolume. This was returning null uuids from the other subvolumes as
    if they were down.
    
    This fix forces that xattr to be requested from all subvolumes.
    
    Change-Id: If62eb39a6857258923ba625e153d4ad79018ea2f
    fixes: bz#1561406
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit caa76bf8d4dadb2fb8372ba82084e854e2518630
Author: Michael Scherer <misc@redhat.com>
Date:   Fri Oct 27 09:50:20 2017 +0200

    Fix gluster(8) formatting
    
    Looking at the man page show that "Snapshot command" wasn't aligned
    with the other section titles.
    
    Change-Id: I24bdb2e3728e03862fee57710cfe34b0607fe09a
    BUG: 1507230
    Signed-off-by: Michael Scherer <misc@redhat.com>

commit 8e7c83e80d726d10073675af85a2e74831088915
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Mar 27 14:59:59 2018 -0400

    glusterd: changing the op-version of volume stop mgmt v3
    
    log message describe the actual test
    
    Change-Id: I1ea7300a6b186032a65236492d6d2a6eef0ab983
    fixes: bz#1560441
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 20fb08d5258f2324433dd465257bcd65e8fe12c2
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Wed Mar 18 11:02:18 2015 -0700

    rpc: update tirpc registration to "force" unregister old mapping before re-registering
    
    > Reviewed-on: https://review.gluster.org/16849
    > Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    
    Change-Id: I05ed6b7c715a71e5819fbe8116e7c3146010f836
    BUG: 1521030
    Signed-off-by: Kevin Vigor <kvigor@fb.com>
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 3b578daaec3937f6ea0ae8173ed92437fa53c732
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Fri Nov 10 11:57:31 2017 +0800

    rpc: simplify parameters when a saved frame is forced to unwind
    
    When a saved frame is to be forced unwind, there is no need to pass an
    empty iovector without any data pointed to.
    
    Change-Id: I6e858fb38644326e22239b83272b15db656035e5
    BUG: 1523122
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit f7d6d8579c4f741744a781d338850835765ed171
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Fri Aug 25 15:15:46 2017 +0800

    rpc: fix incorrect return value when xdr decode fails
    
    xdr_replymsg is called to decode reply message, and it returns failure
    if the message is corrupted. However, retrieving return value from
    the global errno is 0 even xdr_replymsg fails.
    
    Fix this issue by simply returning a negative value if call to
    xdr_replymsg fails.
    
    Change-Id: I2b9a1dc97652fbb6cf6568ea617f120713784a55
    BUG: 1523122
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit a60fc2ddc03134fb23c5ed5c0bcb195e1649416b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Feb 21 12:46:25 2018 +0530

    glusterd: handling brick termination in brick-mux
    
    Problem: There's a race between the last glusterfs_handle_terminate()
    response sent to glusterd and the kill that happens immediately if the
    terminated brick is the last brick.
    
    Solution: When it is a last brick for the brick process, instead of glusterfsd
    killing itself, glusterd will kill the process in case of brick multiplexing.
    And also changing gf_attach utility accordingly.
    
    Change-Id: I386c19ca592536daa71294a13d9fc89a26d7e8c0
    fixes: bz#1545048
    BUG: 1545048
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 95601229b8318f015a19d7eff89f73853b684a49
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Mar 26 10:56:51 2018 +0530

    cluster/dht: ENOSPC will not fail rebalance
    
    ENOSPC returned by a file migration is no longer
    considered a rebalance failure.
    
    Change-Id: I21cf3a8acdc827bc478e138d6cb5db649d53a28c
    fixes: bz#1553598
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 04ede2e1635d664ea18e266544bffc569ae69bb8
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Fri Feb 23 15:26:20 2018 +0530

    Quota: heal directory on newly added bricks when quota limit is reached
    
    Problem: if a lookup is done on a newly added brick for a path on which limit
    has been reached, the lookup fails to heal the directory tree due to quota.
    
    Solution: Tag the lookup as an internal fop and ignore it in quota.
    Since marking internal fop does not usually give enough contextual information.
    Introducing new flags to pass the contextual info.
    
    Adding dict_check_flag and dict_set_flag to aid flag operations.
    A flag is a single bit in a bit array (currently limited to 256 bits).
    
    Change-Id: Ifb6a68bcaffedd425dd0f01f7db24edd5394c095
    fixes: bz#1505355
    BUG: 1505355
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>

commit 7d95a6ff7182e67be8a49f59dbedb892da4a6ae8
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Mar 14 10:27:57 2018 +0530

    quick-read: Provide statistics to the monitor
    
    Updates: #425
    
    Change-Id: Iea5198821f4eabc46bc63529afa4a92d4b4c2be0
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit ab8d18945b4db61a5aa7435a18c29deaf861d46a
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Mar 27 11:01:27 2018 +0530

    glusterd: changing the op-version of volume stop mgmt v3
    
    Change-Id: Iefc5a00d36436b23181871fa365f27b8d90cff0a
    fixes: bz#1560441
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 25fc63912023919e4eaea918810bcb91ee07db46
Author: Vishal Pandey <vpandey@redhat.com>
Date:   Mon Mar 26 12:05:25 2018 +0530

    glfs heal binary change to accomodate socket file arguments
    
    Change-Id: I755d6552decd015aec7859ad2cf99c76c8bee9dc
    fixes: bz#1558380
    BUG: 1558380
    Signed-off-by: Vishal Pandey <vpandey@redhat.com>

commit 9c047f4cae22121b2382551ab56a694665603fd7
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Mar 26 13:18:07 2018 +0530

    glusterd: Implementing volume stop in mgmt v3
    
    Change-Id: I8f9c594cf56331d54eb4884335699744685ef20d
    fixes: bz#1560441
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit a6116794281a6046e05bc87ab7fb39410dfc6a9f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Mar 26 19:25:30 2018 +0530

    tests: fix nl-cache.t failure
    
    commit fef9293 changed network.inode-lru-limit from 50000 to 200000 in
    nl-cache group profile but the test wasn't changed to reflect it
    accordingly.
    
    Change-Id: Ibb5fb0a387f160f6b726246b161a9a7b33135755
    fixes: bz#1560589
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit de0e7efead9be4a6070bcc64e36870b63a991517
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 26 18:30:50 2018 +0530

    .testignore: remove the group profile files
    
    Change-Id: I6619827f1bf6fe9bd974537af6169164b19a0aa5
    fixes: bz#1560393
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 6611aa8203d60bf8e5e8772a31b09ae63f3996f3
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Fri Sep 8 02:40:01 2017 +0200

    glusterfind: Log remote stderr on `node_cmd` error. Fixes #1559130
    
    The problem of lost stderr was introduced in
    commit feea851fad4f89b48bfe89fe3b75250cc7bd6501.
    
    Change-Id: Ic98f9bc9682ae3bd9c3ebea3855667fc8ba2843d
    BUG: 1559130
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>

commit 52c63dafd297163067b8ccb26c864271e6bb11ac
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Mar 26 09:42:37 2018 +0530

    md-cache: fix ./tests/basic/md-cache/bug-1418249.t
    
    inode table size is currently set to 200000. Hence the need of change in
    testcase which was expecting the old value 50000.
    
    Change-Id: I8e44b1d0a2da1e8100bebd25f48bb36e2897b4f8
    fixes: bz#1560393
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit fef929342ec33c388074ad47b81725d73cde6597
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Mar 20 12:15:51 2018 +0530

    extras/group: Change the server inode table size when upcall is on
    
    By default server inode table size is 16K, when upcall is enabled,
    there is going to be too many forgets sent on inodes as the brick can
    hold only 16K inodes in memory, so we increased this to 50K. This is
    still less than the client inode table size. We have seen performance
    improvement when server inode table size is set to 200000(almost as
    client inode table size). Hence changing the value to 200000.
    
    Increasing this increases the memory consumption by <1MB.
    
    BUG: 1559235
    Change-Id: I931db965cd34bf33094328541bd5a633b3357805
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit e043938e2895e4072a3c60b4a0063ef66d34f7b3
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Mar 13 17:51:29 2018 +0530

    nl-cache: Provide statistics to the monitor
    
    Updates: #429
    
    Change-Id: Ic2e64422055f1838d5d453643c739ef1e9319cfe
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit bf671adddf7eef96bc89986cb079d96c5c3b11c8
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Mar 13 17:38:19 2018 +0530

    md-cache: Provide statistics to the monitor
    
    Updates: #427
    
    Change-Id: Ib1f45016ac75d7bc2755db0dd4b68ce1d95d26c3
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit bc04046f0e0c686ef965c2b4ba23cfcab4e1e15b
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Thu Aug 31 16:49:40 2017 +0530

    features/quota: Add new fields to translator options for GD2
    
    alert-time, soft timeout, hard timeout, default soft limit
    and deem-statfs will be settable through volume set command.
    hence marked as settable.
    Other options are used only via quota commands.
    
    Updates #302
    
    Change-Id: I02d258cc3aa7fe58ccbadd59441cce64cfd9ba6e
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>

commit d978ff0e3a0c365c794f069aa56364454b241f12
Author: James Le Cuirot <chewi@gentoo.org>
Date:   Fri Mar 9 23:06:43 2018 +0000

    build: Fix misleading TIRPC result in configure summary
    
    Requesting ipv6-default even if you explicitly disable libtirpc will
    then implicitly enable libtirpc because that is required. That is fine
    but the configure summary should not then show TIRPC as disabled when
    it is not.
    
    The result has also been made clearer by stating that TIRPC is
    "missing" when it has been tried but not found.
    
    BUG: 1553938
    Change-Id: I945bd6859aaf3defa682b0d05ee34a9827b9c45f
    Signed-off-by: James Le Cuirot <chewi@gentoo.org>

commit d121b97f9ad1fdca36f1e79a934e09a9d3066866
Author: James Le Cuirot <chewi@gentoo.org>
Date:   Fri Mar 9 22:39:41 2018 +0000

    build: Fix configure --without-ipv6-default behaviour
    
    The current behaviour disables ipv6-default when no switch is given at
    all but otherwise checks if libtirpc was requested, regardless of
    whether you have given --with-ipv6-default or --without-ipv6-default.
    
    I believe the intention was to enable when libtirpc is requested by
    default but otherwise respect the switch given.
    
    This is important because ipv6-default breaks Gluster for systems that
    have IPv6 disabled.
    
    BUG: 1553926
    Change-Id: I76b91ae2699574b2e5b777453732bb5cbd79bbca
    Signed-off-by: James Le Cuirot <chewi@gentoo.org>

commit 0a08afbb9a2278c7bc71df11c709c14adab68d57
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Wed Mar 21 18:54:24 2018 +0100

    libgfchangelog: Correct the log message
    
    Provide correct error message for changelog end time check
    Updated error message to print "wrong result for end".
    
    Original patch by Keith Schincke <kschinck@redhat.com>
    from https://review.gluster.org/#/c/8121/
    
    Change-Id: Ia3458cbac7784bfc71c05da67391a3f8259f18f0
    BUG: 1559126
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>

commit 0056feaa21489910fa4ef18668602e1f0967ea6c
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Sat May 13 18:54:36 2017 +0200

    python: Remove all uses of find_library. Fixes #1450593
    
    `find_library()` doesn't consider LD_LIBRARY_PATH on Python < 3.6.
    
    Change-Id: Iee26085cb5d14061001f19f032c2664d69a378a8
    BUG: 1450593
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>

commit aaa4e373f3c7093fa13d0882a034f35aba2761a1
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Sun Dec 31 17:46:40 2017 +0100

    glusterfind: Show C function when raising ChangelogException
    
    Fixes: #432
    
    Change-Id: I9ab031e098aff717e619d9deb6410281b96de14a
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>

commit a69e8a664adb3a9255f44522facf04c041f6dec6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Feb 14 04:11:24 2018 +0530

    rfc.sh: provide a unified way to update bugs or github issues ID
    
    Change-Id: Ie78d87b31512da6201ae26f3d391fa3f8e5b68d1
    fixes: bz#1545891
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 5b46d55660807860f7b6711754c700474c0b7d2a
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Mar 14 13:39:26 2018 +0100

    client: make fuse direct I/O strategies explicit
    
    So far the --direct-io-mode option has been presented
    as of being Boolean valued. That is however not exact,
    as a third behavior is chosen if the option is not
    specified.
    
    We accept now the "auto" value as an explicit choice
    for the default heuristics, and indicate in the
    descriptions of the option (which occur in commandline
    help and in the gluterfs / mount.glusterfs man pages)
    that auto is the default.
    
    The default heuristics was briefly described in the
    commandline help. We are getting rid of that, because:
    - it's not the right place to provide such details;
    - there is no guarantee of keeping the current heuristics
      so it might go out of sync with reality;
    - that is already the case to some degree, because the
      description did not take into account that the default
      heuristics varies between platforms (on Mac, it's just
      "off"), and that xlators can also prescribe direct I/O
      for the file of their choice (see change
      I3fe3312cd96baa4eecfe1247ab7255b4f455f049).
    
    Change-Id: Ia83479c0c67fe66b7fc2e0e8db5b7792d9f44b28
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 286871f550b9356025f964ca8af85aabf083f01d
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Mar 21 21:57:50 2018 +0530

    rpcsvc: enable ownthread feature for glusterfs4_0_fop_prog
    
    Ownthread feature needs enabling for glusterfs4_0_fop_prog
    
    Change-Id: Idce63eb094ae0fdfcddbd52d0dee25aa0e074926
    BUG: 1559075
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit ba87963b7622e31cacb4348af817c777d1c443ab
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Fri Nov 3 18:53:54 2017 +0100

    socket: Improve error logging when loading SSL files fails
    
    * Say which file had the problem
    * Dump openssl error stack
    
    Fixes gluster/glusterfs#431.
    
    Change-Id: I66e9a0ae7758e9d7d8a5f19cc8ff898f01f2b491
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>

commit b5f307fa5e7241dd000f0eeac27cc4638a5bccf8
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Tue Mar 20 10:57:13 2018 +0100

    cluster/ec: fix SHD crash for null gfid's
    
    When the self-heal daemon is doing a full sweep it uses readdirp to
    get extra stat information from each file. This information is
    obtained in two steps by the posix xlator: first the directory is
    read to get the entries and then each entry is stated to get additional
    info. Between these two steps, it's possible that the file is removed
    by the user, so we'll get an error, leaving stat info empty.
    
    EC's heal daemon was using the gfid blindly, causing an assert failure
    when protocol/client was trying to encode the gfid.
    
    To fix the problem a check has been added. If we detect a null gfid, we
    simply ignore it and continue healing.
    
    Change-Id: I2e4acdcecd0b6951055e50d1c37d686a2186a228
    BUG: 1558016
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 448dec703d603a150dc1f1cc231c8389ab2fb2ea
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 19 15:26:40 2018 +0530

    cluster/afr: Switch to active-fd-count for open-fd checks
    
    BUG: 1557932
    Change-Id: I3783e41b3812267bc10c0d05d062a31396ce135b
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 2da6650dfa402143c7b9ea0e67bbda79d0475ddd
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 19 15:12:14 2018 +0530

    storage/posix: Add active-fd-count option in gluster
    
    Problem:
    when dd happens on sharded replicate volume all the writes on shards happen
    through anon-fd. When the writes don't come quick enough, old anon-fd closes
    and new fd gets created to serve the new writes. open-fd-count is decremented
    only after the fd is closed as part of fd_destroy(). So even when one fd is on
    the way to be closed a new fd will be created and during this short period it
    appears as though there are multiple fds opened on the file. AFR thinks another
    application opened the same file and switches off eager-lock leading to
    extra latency.
    
    Fix:
    Have a different option called active-fd whose life cycle starts at
    fd_bind() and ends just before fd_destroy()
    
    BUG: 1557932
    Change-Id: I2e221f6030feeedf29fbb3bd6554673b8a5b9c94
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit ade6262cb63b96834dce101a4a237c0c8128077e
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Nov 28 18:18:12 2017 +0530

    cluster/ec: Add test cases for stripe-cache option
    
    Change-Id: I1508a336a7a927b389a19815ef57001cdf29b109
    BUG: 1558074
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 2a326ad32ecb3f90379ef8f3c14c8d14dc64a3b7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 19 12:09:18 2018 +0530

    features/shard: Do list_del_init() while list memory is valid
    
    Problem:
    shard_post_lookup_fsync_handler() goes over the list of inode-ctx that need to
    be fsynced and in cbk it removes each of the inode-ctx from the list. When the
    first member of list is removed it tries to modifies list head's memory with
    the latest next/prev and when this happens, there is no guarantee that the
    list-head which is from stack memory of shard_post_lookup_fsync_handler() is
    valid.
    
    Fix:
    Do list_del_init() in the loop before winding fsync.
    
    BUG: 1557876
    Change-Id: If429d3634219e1a435bd0da0ed985c646c59c2ca
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit ccd7825334f294918f895768fbebf825084f2e5d
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Mar 12 11:47:30 2018 +0530

    georep : Pause/Resume of geo-replication with wrong user
    
    While performing pause/resume on geo-replication with wrong user
    (other user then you setup), always returns success. Which further
    leads to snapshot creation failure as it is detecting active
    geo-replication session.
    
    Change-Id: I6e96e8dd3e861348b057475387f0093cb903ae88
    BUG: 1550936
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit cf06dd544004701ef43fa81c5b7a95353d5c1d65
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Mar 14 09:37:52 2018 +0530

    glusterd: TLS verification fails while using intermediate CA
    
    Problem: TLS verification fails while using intermediate CA
             if mgmt SSL is enabled.
    
    Solution: There are two main issue of TLS verification failing
              1) not calling ssl_api to set cert_depth
              2) The current code does not allow to set certificate depth
                 while MGMT SSL is enabled.
              After apply this patch to set certificate depth user
              need to set parameter option transport.socket.ssl-cert-depth <depth>
              in /var/lib/glusterd/secure_acccess instead to set in
              /etc/glusterfs/glusterd.vol. At the time of set secure_mgmt in ctx
              we will check the value of cert-depth and save the value of cert-depth
              in ctx.If user does not provide any value in cert-depth in that case
              it will consider default value is 1
    
    BUG: 1555154
    Change-Id: I89e9a9e1026e37efb5c20f9ec62b1989ef644f35
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit de52876407040a8cae9656ede9f66084d4cb45ac
Author: Sven Fischer <sven@fischer-abc.de>
Date:   Sat Mar 17 23:30:38 2018 +0100

    cleanup: xlator_t structure's 'client_latency' variable is not used
    
      - Removed unused struct member and its one time usage.
      - cleaned up wrong white space
    
    member 'client_latency' was not used otherwise since it was added by
    
    commit 07cc8679cdf3b29680f4f105d0222da168d8bfc1
    Author: Kevin Vigor <kvigor@fb.com>
    Date:   Tue Mar 21 08:23:25 2017 -0700
    
        Halo Replication feature for AFR translator
    
    Change-Id: Ibb0ea828d4090bbe8897f6af326b317884162a00
    BUG: 1495153
    Signed-off-by: Sven Fischer <sven@fischer-abc.de>

commit 97233b3f69595a7d7a3da3a80a6911b8b4985881
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Thu Mar 15 10:27:55 2018 +0530

    glusterd: glusterd crash in gd_mgmt_v3_unlock_timer_cbk
    
    Memory cleanup of same pointer twice inside gd_mgmt_v3_unlock_timer_cbk
    causing glusterd to crash.
    
    Change-Id: I9147241d995780619474047b1010317a89b9965a
    BUG: 1550339

commit 346714305f9de30d5f78494091770c1555c601bb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 31 16:41:14 2018 +0530

    cluster/afr: Make AFR eager-locking similar to EC
    
    Problem:
    1) Afr's eager-lock only works for data transactions.
    2) When there are conflicting writes, write with conflicting region initiates
    unlock of eager-lock leading to extra pre-ops and post-ops on the file. When
    eager-lock goes off, it leads to extra fsyncs for random-write workload in afr.
    
    Solution (that is modeled after EC):
    In EC, when there is a conflicting write, it waits for the current write to
    complete before it winds the conflicted write. This leads to better utilization
    of network and disk, because we will not be doing extra xattrops and FSYNCs and
    inodelk/unlock. Moved fd based counters to inode based counters.
    
    I tried to model the solution based on EC's locking, but it is not similar to
    AFR because we had to keep backward compatibility.
    
    Lifecycle of lock:
    ==================
    First transaction is added to inode->owners list and an inodelk will be sent on
    the wire. All the next transactions will be put in inode->waiters list until
    the first transaction completes inodelk and [f]xattrop completely.  Once
    [f]xattrop also completes, all the requests in the inode->waiters list are
    checked if it conflict with any of the existing locks which are in
    inode->owners list and if not are added to inode->owners list and resumed with
    doing transaction. When these transactions complete fop phase they will be
    moved to inode->post_op list and resume the transactions that were paused
    because of conflicts. Post-op and unlock will not be issued on the wire until
    that is the last transaction on that inode. Last transaction when it has to
    perform post-op can choose to sleep for deyed-post-op-secs value. During that
    time if any other transaction comes, it will wake up the sleeping transaction
    and takes over the ownership of the lock and the cycle continues. If the
    dealyed-post-op-secs expire, then the timer thread will wakeup the sleeping
    transaction and it will set lock->release to true and starts doing post-op and
    then unlock. During this time if any other transactions come, they will be put
    in inode->frozen list. Once the previous unlock comes it will move the frozen
    list to waiters list and moves the first element from this waiters-list to
    owners-list and attempts the lock and the cycle continues. This is the general
    idea.  There is logic at the time of dealying and at the time of new
    transaction or in flush fop to wakeup existing sleeping transactions or
    choosing whether to delay a transaction etc, which is subjected to change based
    on future enhancements etc.
    
    Fixes: #418
    BUG: 1549606
    Change-Id: I88b570bbcf332a27c82d2767dfa82472f60055dc
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit f32f85c4e6c8128643e1f88fe981a63680e79fe0
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Mar 13 14:03:20 2018 +0530

    cluster/ec: Change default read policy to gfid-hash
    
    Problem:
    Whenever we read data from file over NFS, NFS reads
    more data then requested and caches it. Based on the
    stat information it makes sure that the cached/pre-read
    data is valid or not.
    
    Consider 4 + 2 EC volume and all the bricks are on
    differnt nodes.
    
    In EC, with round-robin read policy, reads are sent on
    different set of data bricks. This way, it balances the
    read fops to go on all the bricks and avoid heating UP
    (overloading) same set of bricks.
    
    Due to small difference in clock speed, it is possible
    that we get minor difference for atime, mtime or ctime
    for different bricks. That might cause a different stat
    returned to NFS based on which NFS will discard
    cached/pre-read data which is actually not changed and
    could be used.
    
    Solution:
    Change read policy for EC as gfid-hash. That will force
    all the read to go to same set of bricks.
    
    Change-Id: I825441cc519e94bf3dc3aa0bd4cb7c6ae6392c84
    BUG: 1554743
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit a4e34af38d3a58c24862890fe5f4c075d0635e8c
Author: Varsha Rao <varao@redhat.com>
Date:   Thu Mar 8 11:08:34 2018 +0530

    tests/basic/namespace: Fix the namespace test failure
    
    In the jenkins regression test brick multiplexing is enabled by
    is_brick_mx_enabled function and not by setting cluster.brick-multiplex
    option. Hence check the count of bricks and its logs, this fixes the
    failure.
    
    Change-Id: Ibb2ed8fbffd3765f283da741689304a5579d447c
    BUG: 1555167
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 7f81067f4522f973e98aa5abbb4d2028da2a2e6f
Author: Xavi Hernandez <jahernan@redhat.com>
Date:   Wed Feb 21 17:47:37 2018 +0100

    cluster/ec: avoid delays in self-heal
    
    Self-heal creates a thread per brick to sweep the index looking for
    files that need to be healed. These threads are started before the
    volume comes online, so nothing is done but waiting for the next
    sweep. This happens once per minute.
    
    When a replace brick command is executed, the new graph is loaded and
    all index sweeper threads started. When all bricks have reported, a
    getxattr request is sent to the root directory of the volume. This
    causes a heal on it (because the new brick doesn't have good data),
    and marks its contents as pending to be healed. This is done by the
    index sweeper thread on the next round, one minute later.
    
    This patch solves this problem by waking all index sweeper threads
    after a successful check on the root directory.
    
    Additionally, the index sweep thread scans the index directory
    sequentially, but it might happen that after healing a directory entry
    more index entries are created but skipped by the current directory
    scan. This causes the remaining entries to be processed on the next
    round, one minute later. The same can happen in the next round, so
    the heal is running in bursts and taking a lot to finish, specially
    on volumes with many directory levels.
    
    This patch solves this problem by immediately restarting the index
    sweep if a directory has been healed.
    
    Change-Id: I58d9ab6ef17b30f704dc322e1d3d53b904e5f30e
    BUG: 1547662
    Signed-off-by: Xavi Hernandez <jahernan@redhat.com>

commit fe52fc33d00eafe7d52ffff1b2dab846374f1d4a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Mar 13 16:39:44 2018 +0530

    tests/bug-1110262.t: fix a race condition
    
    This test does:
    
    1. mount a volume
    2. kill a brick in the volume
    3. mkdir (/somedir)
    
    In my local tests and in [1], I see that mkdir in step 3 fails because
    there is no dht-layout on root directory.
    
    The reason I think is by the time first lookup on "/" hit dht, a brick
    was killed as per step 2. This means layout was not healed for "/" and
    since this is a new volume, no layout is present on it. Note that the
    first lookup done on "/" by fuse-bridge is not synchronized with
    parent process of daemonized glusterfs mount completing. IOW, by the
    time glusterfs cmd executed there is no guarantee that lookup on "/"
    is complete. So, if step 2 races ahead of fuse_first_lookup on "/", we
    end up with an invalid dht-layout on "/" resulting in failures.
    
    Doint an operation like ls makes sure that lookup on "/" is completed
    before we kill a brick
    
    Change-Id: Ie0c4e442c4c629fad6f7ae850437e3d63fe4bea9
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1543279

commit c64fa1496517ba57e5a4dc4573ce5abf73ea03a0
Author: Sven Fischer <sven@fischer-abc.de>
Date:   Mon Mar 12 23:00:28 2018 +0100

    run-tests.sh: added dependency check for netstat
    
    Because bug-924726.t depends on netstat, tests failed before. This got resolved
    by adding respective check to run-tests.sh.
    
    Enabled respective test again.
    
    Change-Id: I70c9bff03379ed9ee8cd95842c3501dfb50b8e86
    BUG: 1312830
    Signed-off-by: Sven Fischer <sven@fischer-abc.de>

commit a96c7e748fccfa796a712b6aac92206212915cdc
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Mar 9 13:03:40 2018 +0530

    cluster/dht:  Skipped files are not treated as errors
    
    For skipped files, use a return value of 1 to prevent
    error messages being logged.
    
    Change-Id: I18de31ac1a64d4460e88dea7826c3ba03c895861
    BUG: 1553598
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 0c3d984287d91d3fe1ffeef297252d912c08a410
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Mar 9 16:17:38 2018 +0530

    rpcsvc: correct event-thread scaling
    
    Problem:
    Auto thread count derived from the number of attachs and detachs
    was reset to 1 when server_reconfigure() was called.
    
    Solution:
    Avoid auto-thread-count reset to 1.
    
    Change-Id: Ic00e86adb81ba3c828e354a6ccb638209ae58b3e
    BUG: 1547888
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit ece3f0f669dd5497f49c6169634b59b307d6e18b
Author: ShyamsundarR <srangana@redhat.com>
Date:   Sat Mar 10 23:08:04 2018 -0500

    protocol: Fix 4.0 client, parsing older iatt in dict
    
    In a mixed mode cluster involving 4.0 and older 3.x bricks, if
    clients are newer, then the iatt encoded in the dictionary can be
    of the older iatt format, which a newer client will map incorrectly
    to the newer structure.
    
    This causes failures in FOPs that depend on this iatt for some
    functionality (seen in mkdir operations failing as EIO, when DHT
    hits its internal setxattr call).
    
    The fix provided is to convert the iatt in the dict, based on which
    RPC version is used to communicate with the server.
    
    IOW, this is the reverse of change in commit "b966c7790e"
    
    Tested using a mixed mode cluster (i.e bricks in 3.12 and 4.0 versions)
    and a mixed set of clients, 3.12 and 4.0 clients.
    
    There is no regression test provided, as this needs a mixed mode cluster
    to test and validate.
    
    Change-Id: I454e54651ca836b9f7c28f45f51d5956106aefa9
    BUG: 1554053
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit b966c7790e35de353ae09ee48d4e2f55e0117f7e
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Mar 9 16:51:57 2018 -0500

    protocol: Added iatt conversion to older format
    
    Added iatt conversion to an older format, when dealing with
    older RPC versions. This enables iatt structure conformance
    when dealing with older clients.
    
    This helps fix rolling upgrade from 3.x versions to 4.0 version
    of gluster by sending the right iatt in the dictionary when DHT
    requests the same.
    
    Change-Id: Ieaf925f81f8c7798a8fba1e90a59fa9dec82856c
    BUG: 1544699
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 157e55fe43ba13f04452aa11f42200b279fb4f7a
Author: Xavi Hernandez <xhernandez@redhat.com>
Date:   Fri Mar 9 22:48:33 2018 +0100

    protocol/client: fix memory corruption
    
    There was an issue when some accesses to saved_fds list were
    protected by the wrong mutex (lock instead of fd_lock).
    
    Additionally, the retrieval of fdctx from fd's context and any
    checks done on it have also been protected by fd_lock to avoid
    fdctx to become outdated just after retrieving it.
    
    Change-Id: If2910508bcb7d1ff23debb30291391f00903a6fe
    BUG: 1553129
    Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>

commit 940f870f4716f9cd32c68db95aa326a0ae87bf03
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Feb 13 06:24:18 2018 +0530

    core: provide infra to make any xlator pass-through
    
    updates: #304
    
    Change-Id: If6a13d2e56b195390a386d720103a882e077f66c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit b2613c9eed6b9d840bc88105dadf282488e6cd64
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Feb 26 13:55:19 2018 +0530

    tests: don't kill the process directly with KILL signal
    
    Instead send the SIGTERM (default, 15) first, and at the end
    send SIGKILL. If SIGKILL is sent directly, we miss many tests
    like valgrind, lcov etc., not able to process the information
    properly.
    
    BUG: 1549000
    Change-Id: I664de12ee7dbf47eb98b8141004cd51f6006b314
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 2a1adc5c9317d2ca78c9f4b890c46f7b3facd146
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Mar 6 21:59:44 2018 +0530

    hooks: fix workdir in S13create-subdir-mounts.sh
    
    Change-Id: Id3eff498091ad9fa4651e93b66903426e76776d6
    BUG: 1549915
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit bd2c45fe3180fe36b042d5eabd348b6eaeb8d3e2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Feb 14 12:15:53 2018 +0530

    glusterd: volume get fixes for client-io-threads & quorum-type
    
    1. If a replica volume created on glusterfs-3.8 was upgraded to
    glusterfs-3.12, `gluster vol get volname client-io-threads` displayed
    'on' even though it wasn't and the xlator wasn't loaded on
    the client-graph. This was due to removing certain checks in
    glusterd_get_default_val_for_volopt as a part of commit
    47604fad4c2a3951077e41e0c007ceb979bb2c24. Fix it.
    
    2. Also, as a part of op-version bump-up, client-io-threads was being
    loaded on the clients  during volfile regeneration. Prevent it.
    
    3. AFR assumes quorum-type to be auto in newly created replic 3 (odd
    replica in general) volumes but `gluster vol get quorum-type` displays
    'none'. Fix it.
    
    Change-Id: I19e586361ed1065c70fb378533d3b4dac1095df9
    BUG: 1545056
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 685d4409f9405a527c87b41d1d89f798729d30f4
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Nov 3 11:49:42 2017 +0530

    hooks: add a script to stat the subdirs in add-brick
    
    The subdirectories are expected to be present for a subdir
    mount to be successful. If not, the client_handshake()
    itself fails to succeed. When a volume is about to get
    mounted first time, this is easier to handle, as if the
    directory is not present in one brick, then its mostly
    not present in any other brick. In case of add-brick,
    the directory is not present in new brick, and there is
    no chance of healing it from the subdirectory mount, as
    in those clients, the subdir itself will be 'root' ('/')
    of the filesystem. Hence we need a volume mount to heal
    the directory before connections can succeed.
    
    This patch does take care of that by healing the directories
    which are expected to be mounted as subdirectories from the
    volume level mount point.
    
    Change-Id: I2c2ac7b7567fe209aaa720006d09b68584d0dd14
    BUG: 1549915
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 51d34907986fba09a560aa18238944811fc47b6a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 2 12:37:42 2018 +0530

    cluster/afr: Remove unused code paths
    
    Removed
    1) afr-v1 self-heal locks related code which is not used anymore
    2) transaction has some data types that are not needed, so removed them
    3) Never used lock tracing available in afr as gluster's network tracing does
    the job. So removed that as well.
    4) Changelog is always enabled and afr is always used with locks, so
    __changelog_enabled, afr_lock_server_count etc functions can be deleted.
    5) transaction.fop/done/resume always call the same functions, so no need
    to have these variables.
    
    BUG: 1549606
    Change-Id: I370c146fec2892d40e674d232a5d7256e003c7f1
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 4511b45bf4d13581cd74c4b87495eda6d54ec5be
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Thu Mar 1 14:44:34 2018 +0530

    glusterd : memory leak in mgmt_v3 lock functionality
    
    In order to take care of stale lock issue, a timer was intrduced
    in mgmt_v3 lock. This timer is not freeing the memory due to
    which this leak got introduced
    
    With this fix now memory cleanup in locking is handled properly
    
    Change-Id: I2e1ce3ebba3520f7660321f3d97554080e4e22f4
    BUG: 1550339
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>

commit 9be043159a514db68b336c6aea49613f3125c5e0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 2 10:13:20 2018 +0530

    cluster/afr: Remove compound-fops usage in afr
    
    We are not seeing much improvement with this change. So removing the
    feature so that it doesn't need to be maintained anymore.
    
    Fixes: #414
    Change-Id: Ic7969b151544daf2547bd262a9fa03f575626411
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit e8446ef31234b44f29bb9a77081023927ef1404d
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 20:48:14 2018 +0530

    nl-cache: Fix coverity issue RESOURCE_LEAK
    
    Change-Id: Ic552f31853e1886b8c76d45c8c66251f1fd6f97f
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 5689a3c2d68cbe6286a4426559f06e210c17bbf4
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 20:46:21 2018 +0530

    nl-cache: Fix coverity issue RETURN_LOCAL
    
    Change-Id: Ic6fbd34aad2a5ae5e27d833300bcd1284cb98c24
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 7f9c56dd38018d65f2902212c1f80171ac7218b1
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Mar 5 13:02:09 2018 +0100

    fuse: enable proper "fgetattr"-like semantics
    
    GETATTR FUSE message can carry a file handle
    reference in which case it serves as a hint
    for the FUSE server that the stat data is
    preferably acquired in context of the given
    filehandle (which we call '"fgetattr"-like
    semantics').
    
    So far FUSE ignored the GETTATTR provided
    filehandle and grabbed a file handle
    heuristically. This caused confusion in the
    caching layers, which has been tracked down
    as one of the reasons of referred BUG.
    
    As of the BUG, this is just a partial fix.
    
    BUG: 1512691
    Change-Id: I67eebbf5407ca725ed111fbda4181ead10d03f6d
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 2bb17551a597b382d77bb5ebc2671b45565cd542
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Mar 2 17:04:49 2018 -0500

    build: address linkage issues
    
    We have the following undefined symbol error from protocol/server.so:
    
      glusterfs_mgmt_pmap_signout
      glusterfs_autoscale_threads
    
    See https://review.gluster.org/19225 (bz#1532238)
    and https://review.gluster.org/19657 (bz#1550895)
    
    (why are there two different bzs for the same bug?)
    
    IMO this is a cleaner solution. I.e. moving the above two functions
    to libgfrpc (.../rpc/rpc-lib/...)
    
    I would also, for (foolish) consistency sake, like to see
    glusterfs_mgmt_pmap_signin() moved from glusterfsd to libgfrpc as
    well.
    
    This works on f28/rawhide, with its new, more restrictive run-time
    link semantics. The smoke and regression tests on earlier fedora and
    centos will confirm that it works on those platforms too.
    
    Change-Id: I9cfbd1cc15e7ebd9fc31b56ac791287fa2c584de
    BUG: 1550895
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 2347debbaf229707b1d957d67cefbe999cbd52d4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Dec 6 16:55:33 2017 +0530

    features/shard: Upon FSYNC from upper layers, wind fsync on all changed shards
    
    Change-Id: Ib74354f57a18569762ad45a51f182822a2537421
    BUG: 1468483
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 259448385c8017448d1da203979bf1e86126be64
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 21:42:06 2018 +0530

    quick-read: Fix coverity issue CHECKED_RETURN
    
    Change-Id: I989e8fe28c86f67b7e54692c01ae3ed6e729aa16
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 220a687f9f589083cd9d1dbd490ab7060ee59ef1
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 21:54:36 2018 +0530

    upcall: Fix coverity issues NEGATIVE_RETURNS
    
    Change-Id: I7d2e733192127ff4ae00ba718562b031f45b72b9
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit f5fc2a3188255f557987af749e0ec13961ea1f40
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 21:47:45 2018 +0530

    io-cache: Fix coverity issue NEGATIVE_RETURNS
    
    Change-Id: I811225ad20e3bd9f05820212e6a843f05d96b246
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 0ec482b5d5b8e4db993f90df70a4c985a426b411
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Mar 2 10:04:52 2018 -0500

    build: fix typo, spelling mistake
    
    transistional -> transitional
    
    Change-Id: I1eb7e063288384458c305afea6d6c46a358701ff
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 1369f313d113c5aca90849e92902ce2142a0e3ed
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 21:23:53 2018 +0530

    libglusterfs: Fix coverity issue FORWARD_NULL
    
    Change-Id: I1402046edb232ca9d23346db82a0cfd041c91e70
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit fecb0fc748806d4e6d61bcbef976acf473e55c82
Author: Anoop C S <anoopcs@redhat.com>
Date:   Fri Mar 2 10:32:17 2018 +0530

    protocol/server: Insert dummy clnt-lk-version to avoid upgrade failure
    
    This is required as we check for 'clnt-lk-version' in SETVOLUME callback
    with older clients in place against newer servers. Change is similar to
    what we have done via https://review.gluster.org/#/c/19560/.
    
    Change-Id: If333c20cf9503f40687ec926c44c7e50222c05b5
    BUG: 1544699
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit fc35d400cba928de610b90adb5854dd1594fcd4a
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Mar 1 17:34:05 2018 +0530

    libglusterfs: Fix volume_options_t struct
    
    The volume_options_t struct was modified and a new member was introduced
    in the middle of the struct. This caused GD2 to crash when it tried to
    read the volume options. The new member has been moved to the end of the
    struct to correct this.
    
    And a note has been added to notify developers on how to modify this
    struct, and the xlator_api_t struct.
    
    Updates: gluster/glusterfs#302
    
    Change-Id: I2e9899ec10516be29c7e9d574da53be8ec17a99e
    Signed-off-by: Kaushal M <kaushal@redhat.com>

commit 7e7fd3595e3ee7e260df4566edf5e1ac95fddd82
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 20:45:02 2018 +0530

    md-cache: Fix coverity issue FORWARD_NULL
    
    Change-Id: I6ace846c412d898c0bc024b5d2081b11a223372f
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 11b3bbd649e15645c916c202d1e521d141f5130b
Author: karthik-us <ksubrahm@redhat.com>
Date:   Fri Feb 23 15:12:19 2018 +0530

    cluster/afr: Make afr_fsync a transaction
    
    Change-Id: I713401feb96393f668efb074f2d5b870d19e6fda
    BUG: 1548361
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit a42137eee3c9e340ac9c82ebacca14eeb4b9d912
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Feb 15 16:12:12 2018 +0530

    features/shard: Fix shard inode refcount when it's part of priv->lru_list.
    
    For as long as a shard's inode is in priv->lru_list, it should have a non-zero
    ref-count. This patch achieves it by taking a ref on the inode when it
    is added to lru list. When it's time for the inode to be evicted
    from the lru list, a corresponding unref is done.
    
    Change-Id: I289ffb41e7be5df7489c989bc1bbf53377433c86
    BUG: 1468483
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit e7b79c59590c203c65f7ac8548b30d068c232d33
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 28 17:58:31 2018 +0530

    cluster/afr: Fix dict-leak in pre-op
    
    At the time of pre-op, pre_op_xdata is populted with the xattrs we get from the
    disk and at the time of post-op it gets over-written without unreffing the
    previous value stored leading to a leak.
    This is a regression we missed in
    https://review.gluster.org/#/q/ba149bac92d169ae2256dbc75202dc9e5d06538e
    
    BUG: 1550078
    Change-Id: I0456f9ad6f77ce6248b747964a037193af3a3da7
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit e2766c32631d27519e688ebec48c408b36e3cc79
Author: Varsha Rao <varao@redhat.com>
Date:   Tue Feb 27 15:58:56 2018 +0530

    perfomance/io-threads: Add option to disable client disconnect feature
    
    > Add options to disable new features
    > Commit ID: c071992e8d
    > https://review.gluster.org/#/c/18291/
    > By Michael Goulet <mgoulet@fb.com>
    
    This patch is required to forward port io-threads namespace patch.
    Updates: #401
    
    Change-Id: Ice477fdf4b8934f9fac0b4a2f6c93db97429a586
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 07372c3729578cd8580209eac3ea7a981efeba3e
Author: Varsha Rao <varao@redhat.com>
Date:   Tue Feb 27 11:33:30 2018 +0530

    tests/basic/namespace: Check if brick multiplex is enabled
    
    This patch fixes the namespace test failure when brick multiplexing is enabled.
    By changing the log file name, when brick multiplexing is enabled. As only one
    log file generated for all bricks.
    
    Change-Id: Ide941946e5e1b2676e7139e1b5bf6b93b93c0815
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 5196bfa6e633475a3f5b8d413e2d1e7c870b28f2
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 19 20:36:05 2018 +0530

    io-cache: Fix coverity issue
    
    Coverity issue : FORWARD_NULL
    fd is assigned within a condition, but the fd is used even outside
    the condition.
    
    Change-Id: I6548d605d8a8acc6a25f1657f9fb75586d513042
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit bb4343fb1a66cf20b6ee8ef3937cd3852d5082c2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Feb 12 08:45:25 2018 -0500

    libglusterfs: move compat RPC/XDR #defines to eliminate warnings
    
    Building with libtirpc (versus legacy glibc rpc) results in many
    warnings about xdr macros that are redefined in libtirpc headers
    because of the way compat.h and glusterfs.h are usually #included.
    
    And these xdr macros in libglusterfs/src/compat.h - which were copied
    from legacy glibc's rpc headers - are different than the same-name macros
    in libtirpc. I haven't checked to see that any of the macros are
    expanded (incorrectly) between the definition in compat.h and the
    redefinition in tirpc/rpc/xdr.h; the risk seems pretty minimal. Regardless
    it seems better, from a truth-and-beauty perspective to not have the
    old, incorrect definitions in the first place.
    
    Not to mention that any file that #includes compat.h and not glusterfs.h
    does not need these xdr macro definitions at all. They're really only
    needed when using really old glibc rpc, which would only be evident if
    including glusterfs.h and/or glusterfs-fops.h. (Which by the way, nothing
    currently #includes glusterfs-fops.h by itself. And maybe nothing ever
    should?)
    
    Change-Id: Ic11e4407d6ab7c498a8745a99379cbf4788a24e8
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 745e522c3a04b59c3c5846850fe22f66001d5ba3
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Feb 2 15:43:47 2018 +0530

    options: framework for options levels
    
    Framework in order to classify options.
    
    Updates gluster/glusterfs#302
    
    Change-Id: I3dd6ae27bd0eb8e0065ffca75838c801e4f3ac91
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 7c3cc485054e4ede1efb358552135b432fb7047a
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sat Feb 10 12:25:15 2018 +0530

    glusterfsd: Memleak in glusterfsd process while  brick mux is on
    
    Problem: At the time of stopping the volume while brick multiplex is
             enabled memory is not cleanup from all server side xlators.
    
    Solution: To cleanup memory for all server side xlators call fini
              in glusterfs_handle_terminate after send GF_EVENT_CLEANUP
              notification to top xlator.
    
    BUG: 1544090
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    
    Note: Run all test-cases in separate build (https://review.gluster.org/19574)
          with same patch after enable brick mux forcefully, all test cases are
          passed.
    
    Change-Id: Ia10dc7f2605aa50f2b90b3fe4eb380ba9299e2fc

commit 430bff7dc330eec9447423e95f2cae49744a79c3
Author: Varsha Rao <varao@redhat.com>
Date:   Mon Feb 26 12:55:06 2018 +0530

    performance/io-threads: nuke everything from a client when it disconnects
    
    > io-threads: nuke everything from a client when it disconnects
    > Commit ID: 4d8268d760
    > https://review.gluster.org/#/c/18254/
    > By Jeff Darcy <jdarcy@fb.com>
    
    This patch is required to forward port io-threads namespace patch.
    Updates: #401
    
    Change-Id: I13d3a74862eea3d01e8dbc8736987c3dae6e8b2a
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 8e21ea3e4f66c27fca796b51f77e4a0231211ff4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Feb 26 15:58:13 2018 +0530

    features/shard: Leverage block_num info in inode-ctx in read callback
    
    ... instead of adding this information in fd_ctx in call path and
    retrieving it again in the callback.
    
    Change-Id: Ibbddbbe85baadb7e24aacf5ec8a1250d493d7800
    BUG: 1468483
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 15afb4cf9f792686e09c0b1ef864c0c02a26ac0d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Feb 26 15:22:58 2018 +0530

    features/shard: Pass the correct block-num to store in inode ctx
    
    Change-Id: Icf3a5d0598a081adb7d234a60bd15250a5ce1532
    BUG: 1468483
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 4a8255f772c8e98ccf6cae731d4d665363c3ed81
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Feb 9 10:33:30 2018 +0530

    write-behind: Make aggregate size configurable
    
    Currently the aggregate size is by default 128K (page size).
    From performance perspective small number of large writes is faster
    than large number of small writes, especially in EC volumes. But identifying
    the right aggregate size depends on multiple factors like the memcpy overhead,
    network overhead etc. On local machine, combining 128k writes to 1M writes for
    EC volumes yielded 30% improvement.
    
    As a part of this patch, aggregate size is just made configurable and page_size
    is modified accordingly.
    
    Raghavendra Gowdappa had suggested that, while aggregating writes we should get
    rid of memcpy of large write size, and instead add the pointer to existinf vector,
    will be doing it as a part of another patch. Also, in EC volumes, the vectors are
    merged into one vector, so even if we save memcopy in write_behind, EC would anyways
    do memcopy for merging vectors into one vector.
    
    Updates: #364
    
    Change-Id: Ib67294b8577bea14dde1c84cd271012ecea99f09
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 7d641313f46789ec0a7ba0cc04f504724c780855
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Feb 26 15:14:18 2018 +0530

    rpcsvc: scale rpcsvc_request_handler threads
    
    Scale rpcsvc_request_handler threads to match the scaling of event
    handler threads.
    
    Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1467614#c51
    for a discussion about why we need multi-threaded rpcsvc request
    handlers.
    
    Change-Id: Ib6838fb8b928e15602a3d36fd66b7ba08999430b
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit a1e59bc8fd220b4cba038e2db2630665ba871b50
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Feb 20 11:34:09 2018 +0530

    md-cache: Modify options to be gd2 compatible
    
    Change-Id: I79d51fee8ec5d2d237de7dd21c2d28c18cfd7ce8
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 55d804a62e5c01a566d96a414d649b93bc12345c
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Feb 20 11:38:44 2018 +0530

    nl-cache: Change the options to be gd2 compatible
    
    Change-Id: Ib9d233df41b85c845643e3e6eb2d680e01859a43
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 32f5bc795046fad2fc5dcdafafcf1e8c3df7d7a3
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Feb 8 13:44:38 2018 +0530

    cluster/dht: store the 'reaction' on failures per lock
    
    Currently its passed in dht_blocking_inode(entry)lk, which would be a
    global value for all the locks passed in the argument. This would
    be a limitation for cases where we want to ignore failures on only few
    locks and fail for others.
    
    Change-Id: I02cfbcaafb593ad8140c0e5af725c866b630fb6b
    BUG: 1543279
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit cfbc524239b1d3bc417849e68379c81e83fd56d9
Author: Varsha Rao <varao@redhat.com>
Date:   Wed Feb 21 23:03:48 2018 +0530

    performance/io-threads: Add threads to priority based stagnant queues
    
    > performance/io-threads: Add watchdog to cover up a possible thread leak
    > Commit ID: 8b6804f75c
    > https://review.gluster.org/#/c/18239/
    > By Shreyas Siravara <sshreyas@fb.com>
    
    This patch is required to forward port io-threads namespace patch.
    Updates: #401
    
    Change-Id: Id057c34a2abb9fc6dfb4afcd5c7bbbfe5693bbb8
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit efbfd17dfc73c4e6055adeffc65be1697f094168
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Feb 19 09:44:29 2018 +0530

    cluster/dht: Handle single dht child in dht_lookup
    
    This patch limits itself to only handling the case
    where no file (data or linkto) exists on the subvol.
    
    Additional cases to be handled:
    1. A linkto file was found on the only child subvol. This currently
    calls dht_lookup_everywhere which eventually deletes it. It can be
    deleted directly as it will not be pointing to a valid subvol.
    2. Directory lookups - locking might be unnecessary in some cases.
    
    Change-Id: I940ba34531f2aaee1d36fd9ca45ecfd46be662a4
    BUG: 1546620
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 475286ec7f9fbaea6b10a549119730f89e282cec
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Feb 20 20:08:11 2018 +0530

    cluster/dht: Ignore ENODATA from getxattr for posix acls
    
    dht_migrate_file no longer prints an error if getxattr for
    posix acls fails with ENODATA/ENOATTR.
    
    Change-Id: Id9ecf6852cb5294c1c154b28d609889ea3420e1c
    BUG: 1546954
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e4ca0b3df379c553e220f929f0203175bd536b61
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Feb 12 03:11:04 2018 -0500

    geo-rep: Remove lazy umount and use mount namespaces
    
    Lazy umounting the master volume by worker causes
    issues with rsync's usage of getcwd. Henc removing
    the lazy umount and using private mount namespace
    for the same. On the slave, the lazy umount is
    retained as we can't use private namespace in non
    root geo-rep setup.
    
    Change-Id: I403375c02cb3cc7d257a5f72bbdb5118b4c8779a
    BUG: 1546129
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 961370d995400b68afe520207593b8cc59846448
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Feb 20 20:31:39 2018 +0530

    cluster/dht: Fixed a typo
    
    Replaced "then" with "than"
    
    Change-Id: I73090e8c1a639befd7c5458e8d63bd173248bc7d
    BUG: 1547128
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 09ff6c686ac95a87cd200bd54cc01943981d9928
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Feb 20 18:37:56 2018 +0530

    glusterd: compare uuid instead of hostname while finding compatible brick
    
    If the above is not done, bricks created with different IP/hostname will
    not be compatible with brick multiplexing.
    
    Change-Id: I508eb59b0632df4b48466cca411c7ec6cc6bd577
    BUG: 1547068
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit d0e7177416be3005b3f092addf0bba4dd9dc7a2d
Author: Varsha Rao <varao@redhat.com>
Date:   Mon Feb 12 10:37:15 2018 +0530

    xlators/features/namespace: Add namespace xlator and link into brick graph
    
    The following release-3.8-fb branch patch is upstreamed:
    > features/namespace: Add namespace xlator and link into brick graph
    > Commit ID: dbd30776f26e
    > https://review.gluster.org/#/c/18041/
    > By Michael Goulet <mgoulet@fb.com>
    
    Changes in this patch:
    Removes extra config.h and namespace.h file in namespace.c
    Adds default_getspec_cbk to libglusterfs.sym
    Rename dict_for_each to dict_foreach_inline
    Remove fd.h header file stack.h
    Add test case for truncate, open and symlink
    
    This patch is required to forward port io-threads namespace patch.
    Updates: #401
    
    Change-Id: Ib88c95b89eecee9b8957df8a4c8712c899c761d1
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 49e57efa515f12013da9f5293846aff17ac48f7d
Author: Nigel Babu <nigelb@redhat.com>
Date:   Wed Feb 21 08:57:54 2018 +0530

    tests: Set timeout of 300 for self-heal.t
    
    There are a few tests that take more time on regression nodes
    
    Change-Id: If126d5ebd422cd6d99125db040e74f0d104af7bc
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit e3e7cdbde5463ff6d20af52329a784ca629c6aef
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sun Feb 18 08:14:35 2018 +0530

    Revert "glusterfsd: Memleak in glusterfsd process while  brick mux is on"
    
    There are still remain some code paths where cleanup is required while
    brick mux is on.I will upload a new patch after resolve all code paths.
    
    This reverts commit b313d97faa766443a7f8128b6e19f3d2f1b267dd.
    
    BUG: 1544090
    Change-Id: I26ef1d29061092bd9a409c8933d5488e968ed90e
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 8d9961e63786cf8a9bb9e2f4140ab9a77f1ccbe3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jan 31 16:38:34 2018 +0100

    build: add --without-server option
    
    With Gluster 4.0 we will not provide the server components for EL6 and
    older. At one point Gluster 4.x will get GlusterD2, which requires
    Golang tools in the distribution. EL6 does not contain these at the
    moment.
    
    With this change, it is possible to `./configure --without-server` which
    prevents building glusterd and the xlators for the bricks. Building RPMs
    can pass `--without server` and the glusterfs-server sub-package will
    not be created.
    
    Change-Id: I97f5ccf9f2c76e60d9af83915fc59fae57ad6d25
    BUG: 1074947
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 134c539e79f96691622ed15debaeace2071c6937
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Jan 25 08:53:21 2018 +0530

    socket: options update for GD2
    
    All socket options update for GD2
    
    Change-Id: I227c16965e92018a5ab5aacd9c2617fb2735268c
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 6daa6535692b2c68b493636a9bbfdcbc475b3d80
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Feb 11 06:54:35 2018 +0530

    posix/afr: handle backward compatibility for rchecksum fop
    
    Added a volume option 'fips-mode-rchecksum' tied to op version 4.
    If not set, rchecksum fop will use MD5 instead of SHA256.
    
    updates: #230
    Change-Id: Id8ea1303777e6450852c0bc25503cda341a6aec2
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit e80c10d5e6fb97e132ff7f1c2846629fb5ad915f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jan 30 18:48:33 2018 +0530

    metrics: set latency min value during xlator init
    
    otherwise, the very first metrics will have all the min as 0.
    
    also no need to print pending-fops if it is 0.
    
    Updates #168
    
    Change-Id: I233de6c92b1a73977bb468ba211ac6ec3c05298f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 664b946496368f625b5a15646b5aa791078055ef
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Feb 9 09:27:03 2018 +0530

    Fetch backup volfile servers from glusterd2
    
    Clients will request for a list of volfile servers from glusterd2 by
    setting a (optional) flag in GETSPEC RPC call. glusterd2 will check for
    the presence of this flag and accordingly return a list of glusterd2
    servers in GETSPEC RPC reply. Currently, this list of servers returned
    only contains servers which have bricks belonging to the volume.
    
    See:
    https://github.com/gluster/glusterd2/issues/382
    https://github.com/gluster/glusterfs/issues/351
    
    Updates #351
    Change-Id: I0eee3d0bf25a87627e562380ef73063926a16b81
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit b313d97faa766443a7f8128b6e19f3d2f1b267dd
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sat Feb 10 12:25:15 2018 +0530

    glusterfsd: Memleak in glusterfsd process while  brick mux is on
    
    Problem: At the time of stopping the volume while brick multiplex is
             enabled memory is not cleanup from all server side xlators.
    
    Solution: To cleanup memory for all server side xlators call fini
              in glusterfs_handle_terminate after send GF_EVENT_CLEANUP
              notification to top xlator.
    
    BUG: 1544090
    Change-Id: Ifa1525e25b697371276158705026b421b4f81140
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 9d0d1fdd091d754149242fd4389b964695aacf13
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jan 18 23:24:04 2018 +0530

    tests: bring option of per test timeout
    
    This uses 'timeout' command with 300 seconds default. Right now,
    there is just 1 test which takes more than that in a properly
    setup machine.
    
    Ideally best case is set the default to something like 30 seconds,
    and if a test is supposed to take more than that, owner should add
    a timeout line to test knowingly. That way, it makes test writers
    think about a time limit too.
    
    Change-Id: I747005ce1f208aeb2ecbf899e8feea487ecd21a0
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit c096bec4ec3f3ac33cc0787c60978944792e074e
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Feb 13 12:23:39 2018 +0530

    protcol/client: Insert dummy clnt-lk-version to avoid upgrade failure
    
    With https://review.gluster.org/#/c/12363/ being merged, we no longer
    send client's lk-version to server side and the corresponding check on
    server is also removed. But when clients are upgraded prior to servers,
    the check for lk-version at server side fails and is reported back to
    clients resulting in disconnection.
    
    Since we don't have lock-recovery (lk-version and grace-timeout) logic
    anymore in code base our best bet would be to add client's default
    lk-version i.e, 1, into the dictionary just to make server side check
    pass and continue with remaining SETVOLUME operations.
    
    Change-Id: I441b67bd271d1e9ba9a7c08703e651c7a6bd945b
    BUG: 1544699
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 7a4ca270af19124a262f93fafc367e3635da3c0b
Author: Sheena Artrip <sheenobu@fb.com>
Date:   Tue Feb 13 14:59:07 2018 -0800

    rpc: Adds rpcbind6 programs to libgfrpc symbols
    
    Building with --with-default-ipv6 causes shared
    components of gluster calling the rpcbind6 functions
    to fail. Adding the symbols in the list is all that is
    necessary. Building without ipv6 keeps the same behavior.
    
    No test cases as this is a build-specific fix.
    
    Change-Id: I248d3291bf17326b07d152d9b79cdcfaf9068f0d
    BUG: 1544961
    Signed-off-by: Sheena Artrip <sheenobu@fb.com>

commit 37a13e16532d2757ee489bb8195dfd6c567f2ca1
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Feb 13 08:06:24 2018 +0530

    glusterd: fix tier-enabled flag op-version check
    
    tier-enabled flag in volinfo structure was introduced in 3.10, however
    while writing this value to the glusterd store was done with a wrong
    op-version check which results into volume checksum failure during upgrades.
    
    Change-Id: I4330d0c4594eee19cba42e2cdf49a63f106627d4
    BUG: 1544600
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit adb266baa16f807745102ba925aa8a1028f8580a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Feb 13 09:09:39 2018 +0530

    libglusterfs/syncop: Add syncop_entrylk
    
    Change-Id: Idd86b9f0fa144c2316ab6276e2def28b696ae18a
    BUG: 1543279
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit e67cd078c5fea1026838d5197f8773c82e29425c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Feb 12 07:48:20 2018 +0530

    tests: fix spurious test failure
    
    In bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t
    check for peer count after starting glusterd instance on node 2
    
    Change-Id: I3f92013719d94b6d92fb5db25efef1fb4b41d510
    BUG: 1540607
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 35da87e24132e38feeca8234757ee9d6d1fa40ff
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Feb 13 06:33:53 2018 +0530

    posix: fix the syncop_writev() arguments
    
    Due to merging https://review.gluster.org/#/c/19131 before
    https://review.gluster.org/18804 the build started failing.
    
    Fixing with this patch.
    
    Change-Id: Ia1eedf481a0f6d25f1357ee56d6bbb7a7e9d9793
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 87fd65f1ef1c64b1e32a6da47865a4a28f1e508e
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jan 16 14:24:28 2018 +0530

    Posix: Implement put fop
    
    Updates #353
    Change-Id: I1410222529ff42a810d62825bd6eebe8913fad1e
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 384562b294e9a7847403961e878a4daa0fff33eb
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Feb 1 11:20:37 2018 +0800

    gfapi: return pre/post attributes at callback for glfs api
    
    Updates: #389
    Change-Id: Ic71632722effe4b8855d5de3e65688efd9afe1e3
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 248152767b0599986bbb6bb35fc27197f6be6964
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Feb 1 10:13:07 2018 +0800

    gfapi: return pre/post attributes from glfs_ftruncate
    
    Updates: #389
    Change-Id: I8faea0828921fb17f05f7321c3cb01747373f21e
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 09943beb499617212f2985ca8ea9ecd1ed1b470e
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Thu Jan 18 15:51:18 2018 +0800

    gfapi: return pre/post attributes from glfs_fsync/fdatasync
    
    Updates: #389
    Change-Id: I4153df72d5eeecefa7579170899db4c340128bea
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit d01f7244e9d9f7e3ef84e0ba7b48ef1b1b09d809
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Mon Feb 12 15:13:49 2018 +0800

    gfapi: return pre/post attributes from glfs_pread/pwrite
    
    As nfs-ganesha, a wcc data contains pre/post attributes is return
    in read/write rpc reply. nfs-ganesha get those attributes by
    two getattr between the real read/write right now.
    
    But, gluster has return pre/post attributes from glusterfsd,
    those attributes are skipped in syncop/gfapi, if gfapi return them,
    the upper user (nfs-ganesha) can use them directly without any
    duplicate getattr.
    
    Updates: #389
    Change-Id: I7b643ae4241cfe2aeb17063de00192d81674024a
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit bfb66cc535ce473afa7e330800d2d2c38afe42c9
Author: Poornima G <pgurusid@redhat.com>
Date:   Sat Nov 18 15:51:43 2017 +0530

    io-threads: Implement put fop
    
    Updates #353
    Change-Id: I8a30b53a52618c6a6c740d2c67b19e5322ce4ddb
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 535fd517c6b188732f9d69c0301dd78c3dc3d09c
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Jan 4 10:35:29 2018 +0530

    glusterd: optimization of test cases
    
    To reduce the overall time taken by the every regression job for all glusterd test cases,
    avoiding some duplicate tests by clubbing similar test cases into one.
    
    real time taken for all regression jobs of glusterd without this patch is 1959 seconds,
    with this patch it is 1059 seconds.
    
    Look at the below document for your reference.
    https://docs.google.com/document/d/1u8o4-wocrsuPDI8BwuBU6yi_x4xA_pf2qSrFY6WEQpo/edit?usp=sharing
    
    Change-Id: Ib14c61ace97e62c3abce47230dd40598640fe9cb
    BUG: 1530905
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 446ddbf1b10ce835e0e40790bc997ec6ac53766a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Feb 9 21:02:09 2018 +0530

    glusterd/snapshot : fix the compare snap logic
    
    In one of the case in commit cb0339f there's one particular case where
    after removing the old snap it wasn't writing the new snap version and
    this resulted into one of the test to fail spuriously.
    
    Change-Id: I3e83435fb62d6bba3bbe227e40decc6ce37ea77b
    BUG: 1540607
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit a9df2ac27e6db97b2cdd77305e6f9e86fdd512cf
Author: Nigel Babu <nigelb@redhat.com>
Date:   Tue Feb 6 16:29:33 2018 +0530

    maintainers: Switch up glusto ownership
    
    Shwetha is stepping down from maintainer to peer and Nigel is stepping
    up to be co-maintainer along with Jonathan.
    
    Change-Id: If1b54936bf1be27673448dda5eff5695da1e8f5f

commit cb0339f9229fc5c05d7ef4cfcc4ca9c4569f3755
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 8 09:09:00 2018 +0530

    glusterd: import volumes in separate synctask
    
    With brick multiplexing, to attach a brick to an existing brick process
    the prerequisite is to have the compatible brick to finish it's
    initialization and portmap sign in and hence the thread might have to go
    to a sleep and context switch the synctask to allow the brick process to
    communicate with glusterd. In normal code path, this works fine as
    glusterd_restart_bricks () is launched through a separate synctask.
    
    In case there's a mismatch of the volume when glusterd restarts,
    glusterd_import_friend_volume is invoked and then it tries to call
    glusterd_start_bricks () from the main thread which eventually may land
    into the similar situation. Now since this is not done through a
    separate synctask, the 1st brick will never be able to get its turn to
    finish all of its handshaking and as a consequence to it, all the bricks
    will fail to get attached to it.
    
    Solution : Execute import volume and glusterd restart bricks in separate
    synctask. Importing snaps had to be also done through synctask as
    there's a dependency of the parent volume need to be available for the
    importing snap functionality to work.
    
    Change-Id: I290b244d456afcc9b913ab30be4af040d340428c
    BUG: 1540607
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 2a004fbcc9296ee055b1957d1812552848ae7a0d
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Thu Feb 1 14:53:48 2018 +0800

    libgfapi: Remove need_lookup from readdirp
    
    The inode_set_need_lookup is removed from fuse_readdirp_cbk at
    http://lists.gluster.org/pipermail/gluster-devel/2017-August/053505.html
    https://review.gluster.org/#/c/17985/
    
    Remove the same logical from glfd_entry_refresh too.
    
    Change-Id: Ic0d7b59d4d4ed8315bf4c5e87e8e1133bcf95401
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 04dfa27c6feb39f1e3785ec3d753b3ed1fb21aba
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Feb 6 14:27:00 2018 +0530

    build: Exempt env.rc during `make clean`
    
    It is desirable to keep env.rc after `make clean` is executed so that
    tests can be run following the next `make` without configuring one
    more time.
    
    Change-Id: I5f3ebaea878fd5124af8eae3cb7f8a619d16eac2
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 2584ef1b00660d3ea202838a3200bc0dab04420c
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Thu Feb 1 15:18:45 2018 +0800

    libgfapi: skip nameless lookup if stat is NULL
    
    Change-Id: If0ad17be2f7d7f88df25966aaf67af963ff4fc41
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit aa4372bf427152f671de52fc6e02b93ca09f22c7
Author: Varsha Rao <varao@redhat.com>
Date:   Tue Feb 6 18:56:45 2018 +0530

    performance/io-threads: expose io-thread queue depths
    
    The following release-3.8-fb branch patch is upstreamed:
    
    > io-stats: Expose io-thread queue depths
    > Commit ID: 69509ee7d2
    > https://review.gluster.org/#/c/18143/
    > By Shreyas Siravara <sshreyas@fb.com>
    
    Changes in this patch:
    - Replace iot_pri_t with gf_fop_pri_t
    - Replace IOT_PRI_{HI, LO, NORMAL, MAX, LEAST} with
      GF_FOP_PRI_{HI, LO, NORMAL, MAX, LEAST}
    - Use dict_unref() instead of dict_destroy()
    
    This patch is required to forward port io-threads namespace patch.
    Updates: #401
    Change-Id: I1b47a63185a441a30fbc423ca1015df7b36c2518
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 5e751b4c05375aa8b0f217ca73629d7d43faccf6
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Feb 7 20:55:47 2018 +0530

    tests/dht: Non-root can delete stale linkto files
    
    Test to check that non-root users can delete stale
    linkto files
    
    Change-Id: Ic9bc76bc485cab839927af60cfce78a058eee2e4
    BUG: 1542318
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 3fb1df7870e03c9dea1f4a46c22774006a20fea1
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Feb 6 15:20:16 2018 +0530

    cluster/dht: Unlink linkto files as root
    
    Non-privileged users cannot delete linkto
    files. However the failure to unlink a stale linkto
    causes DHT to fail the lookup with EIO and hence
    prevent access to the file.
    
    Change-Id: Id295362d41e52263790694602f36f1219f0646a2
    BUG: 1542318
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 3f824314f6367206681152c7523bacbfb30fa945
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Feb 5 13:39:22 2018 +0530

    cluster/dht: Cleanup on fallocate failure
    
    It looks like fallocate leaves a non-empty
    file behind in case of some failures. We now
    truncate the file to 0 bytes on failure in
    __dht_rebalance_create_dst_file.
    
    Change-Id: Ia4ad7b94bb3624a301fcc87d9e36c4dc751edb59
    BUG: 1541916
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit e7ee4d8949b015a1421d4d97b763ccb4dcfc6eb1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Feb 4 10:04:29 2018 +0530

    glusterd/store: handle the case of fsid being set to 0
    
    Generally this would happen when a system gets upgraded from an
    version which doesn't have fsid details, to a version with fsid
    values. Without this change, after upgrade, people would see reduced
    'df ' output, causing lot of confusions.
    
    Debugging Credits: Nithya B <nbalacha@redhat.com>
    
    Change-Id: Id718127ddfb69553b32770b25021290bd0e7c49a
    BUG: 1517260
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ec2c95f310fdd30531b04f85840860aae2c8dff4
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jan 25 14:12:45 2018 +0530

    build: Remove unwanted autoconf messages for libtirpc
    
    AC_MSG_RESULT is normally used when it is preceded by AC_MSG_CHECKING
    during explicit checking of certain requirements. With PKG_CHECK_MODULES
    being used for checking the presence of libtirpc itself generates the
    following message:
    
    checking for TIRPC... yes
    
    Change-Id: I3f088a45ef2ced6f6fd9e1524e758c812deecb8f
    BUG: 1536186
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 1edb79b9b4e94083c03055ddba805f51e0349992
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Thu Feb 1 16:06:32 2018 +0100

    cluster/afr: remove unnecessary child_up initialization
    
    The child_up array was initialized with all elements being -1 to
    allow afr_notify() to differentiate down bricks from bricks that
    haven't reported yet. With current implementation this is not needed
    anymore and it was causing unexpected results when other parts of
    the code considered that if child_up[i] != 0, it meant that it was up.
    
    Change-Id: I2a9d712ee64c512f24bd5cd3a48dcb37e3139472
    BUG: 1541038
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit fe87f3e34fc1c983731a8b84968d49db2b96c824
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Feb 2 18:32:32 2018 +0530

    cluster/dht: Fixed a leak in inode_ref
    
    Introduced by commit d9f773ba719397c128
    
    Change-Id: I3f3103a5a80daed7562ace72e5aa53b77e74fb94
    BUG: 1541264
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 545a7ce6762a1b3a7b989b43a9d18b5b1b299df0
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Jan 18 13:06:12 2018 +0530

    cluster/dht: avoid overwriting client writes during migration
    
    For more details on this issue see
    https://github.com/gluster/glusterfs/issues/308
    
    Solution:
    This is a restrictive solution where a file will not be migrated
    if a client writes to it during the migration. This does not
    check if the writes from the rebalance and the client actually
    do overlap.
    
    If dht_writev_cbk finds that the file is being migrated (PHASE1)
    it will set an xattr on the destination file indicating the file
    was updated by a non-rebalance client.
    Rebalance checks if any other client has written to the dst file
    and aborts the file migration if it finds the xattr.
    
    updates gluster/glusterfs#308
    
    Change-Id: I73aec28bc9dbb8da57c7425ec88c6b6af0fbc9dd
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit d9f773ba719397c12860f494a8cd38109e4b2fe3
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Feb 2 12:35:16 2018 +0530

    cluster/dht: Fixed leak in dht_populate_inode_for_dentry
    
    Fixed an issue in dht_populate_inode_for_dentry where a layout is
    set in the inode without checking if it is already set. This overwrites
    the value each time without freeing the already existing layout.
    
    Change-Id: I651bf539a0b82b4ddc4c355890c16a8e91f5f1fd
    BUG: 1541264
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 641e5be8d1bcbb5161487eeb84229eed5ee5c31b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Feb 1 22:56:09 2018 +0530

    sdfs: crash fixes
    
    * from the patch which got tested in experimental branch, there
      was a code cleanup involved, which missed setting of a local
      variable, which led to crash immediately after enabling the
      feature.
    * added a sanity test case to validate all the fops of sdfs.
    
    Updates: #397
    
    Change-Id: I7e0bebfc195c344620577cb16c1afc5f4e7d2d92
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 0e6e8216823c2d9dafb81aae0f6ee3497c23d140
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Jan 28 13:50:47 2018 +0530

    afr: don't treat all cases all bricks being blamed as split-brain
    
    Problem:
    We currently don't have a roll-back/undoing of post-ops if quorum is not
    met. Though the FOP is still unwound with failure, the xattrs remain on
    the disk.  Due to these partial post-ops and partial heals (healing only when
    2 bricks are up), we can end up in split-brain purely from the afr
    xattrs point of view i.e each brick is blamed by atleast one of the
    others. These scenarios are hit when there is frequent
    connect/disconnect of the client/shd to the bricks while I/O or heal
    are in progress.
    
    Fix:
    Instead of undoing the post-op, pick a source based on the xattr values.
    If 2 bricks blame one, the blamed one must be treated as sink.
    If there is no majority, all are sources. Once we pick a source,
    self-heal will then do the heal instead of erroring out due to
    split-brain.
    
    Change-Id: I3d0224b883eb0945785ade0e9697a1c828aec0ae
    BUG: 1539358
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit d663b9a323f34919da3f35bfc221a0aa91d9ab94
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jan 18 10:31:38 2018 +0530

    protocol: utilize the version 4 xdr
    
    updates #384
    
    Change-Id: Id80bf470988dbecc69779de9eb64088559cb1f6a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit ce9055449477dd59f29de213d140c60b03e465eb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 31 22:10:46 2018 +0530

    cluster/ec: Do lock conflict check correctly for wait-list
    
    Problem:
    ec_link_has_lock_conflict() is traversing over only owner_list
    but the function is also getting called with wait_list.
    
    Fix:
    Modify ec_link_has_lock_conflict() to traverse lists correctly.
    Updated the callers to reflect the changes.
    
    BUG: 1540669
    Change-Id: Ibd7ea10f4498e7c2761f9a6faac6d5cb7d750c91
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 55c759000491683aba6bb247dd913ba1c5b52836
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Jan 11 16:14:41 2018 +0530

    protocol/auth: options update for GD2
    
    addr and login options update for GD2
    
    Change-Id: I3bb9a2ad368326036c2e7f6bd48b624bdd053051
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 5452943a3691d64a3fc76d1db96b1602b8f2c398
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Sat Jan 27 00:58:25 2018 +0530

    bitrot : improved cli report after bitrot operatoin
    
    Improved cli report post bitrot opertaion as previously it was
    showing output "volume bitrot: success" for all the sucessfull
    bitrot operations (enable, disable or scrub options).
    
    Change-Id: I0857e99f3956221a51cfd1b29a90e1038b90570f
    BUG: 1539166
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 440a048f24b006c80af3d7bcd0a1f13fe3459d87
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Jan 30 20:59:23 2018 +0530

    afr: capture the correct errno in post-op quorum check
    
    If the post-op phase of txn did not meet quorm checks, use that errno to
    unwind the FOP rather than blindly setting ENOTCONN.
    
    Change-Id: I0cb0c8771ec75a45f9a25ad4cd8601103deddf0c
    BUG: 1506140
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 85f1d5444735c34ec8da23dc014ed99b6706577c
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Mon Jan 29 16:07:50 2018 +0800

    statedump: sanity check of mem_acct and rec for xlator
    
    With memory accounting is disabled, glusterfs crash when doing statedump at,
    
    0  0x00007fe24cff543a in gf_proc_dump_xlator_mem_info_only_in_use (xl=0x7fe23e44dc00) at statedump.c:269
    1  0x00007fe24cff6310 in gf_proc_dump_oldgraph_xlator_info (top=0x7fe23e44dc00) at statedump.c:530
    2  0x00007fe24cff7114 in gf_proc_dump_info (signum=10, ctx=0x7fe24ac0e000) at statedump.c:845
    3  0x00007fe24d4d4bab in glusterfs_sigwaiter (arg=0x7ffc6c080750) at glusterfsd.c:2109
    4  0x00007fe24bbd5dc5 in start_thread () from /lib64/libpthread.so.0
    5  0x00007fe24b51a73d in clone () from /lib64/libc.so.6
    
    (gdb) p xl->mem_acct
    $1 = (struct mem_acct *) 0x0
    (gdb) p xl->mem_acct->rec
    $2 = 0x10
    
    Change-Id: I10858170431311833ae01224d51c66caaad5e9a3
    BUG: 1539603
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 542af5714d761e787276111ca8bf7a5c69afb721
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jan 16 14:14:39 2018 +0530

    protocol: Implement put fop
    
    Updates #353
    Change-Id: I755b9208690be76935d763688fa414521eba3a40
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit bb34b07fd2ec5e6c3eed4fe0cdf33479dbf5127b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jan 29 10:23:52 2018 +0530

    glusterd: optimize glusterd import volumes code path
    
    In case there's a version mismatch detected for one of the volumes
    glusterd was ending up with updating all the volumes which is a
    overkill.
    
    Change-Id: I6df792db391ce3a1697cfa9260f7dbc3f59aa62d
    BUG: 1539510
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 4475150a5792743a016801dc72573416389810d1
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jan 30 16:47:34 2018 +0100

    tests: fix tests/bugs/fuse/bug-858215.t
    
    Change-Id: Ifbf5e628ccb9a0ecb285f5884a41e70d935316bd
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit f9e6be05bc94449b41b04ab8571a8d1cb4858eeb
Author: Milan Zink <mzink@redhat.com>
Date:   Wed Jan 10 13:04:42 2018 +0100

    extras/hooks: Fix S10selinux-label-brick.sh hook script
    
    * script was failng due to syntax error
    * shellcheck issues fixed
    * improved performance: semanage & restorecon is being run on unique path
    
    Change-Id: I58b357d9fd37586004a2a518f7a5d1c5c9ddd7e3
    BUG: 1533342
    Signed-off-by: Milan Zink <zeten30@gmail.com>

commit b114303ef914dd90d7cc2cc86fad51127846c6f2
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Jan 30 14:39:57 2018 -0500

    glusterd: Update op-version for master
    
    Updated the op-version on master to the next release
    op-version, for any future options appearing on master.
    
    Change-Id: I2ef6f8874c638ade1d97477bdd8ffa1bd1a9f952
    BUG: 1540338
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 6baa79b17337bb9fd8aa95e4f8c743ab4111aa75
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jan 22 11:08:48 2018 +0100

    doc: describe how to contribute when a GitHub Pull-Request is made
    
    Every now and then new contributors create a GitHub Pull-Request. We do
    not use those for accepting changes, and almost never check for new PRs.
    Redirecting contributors can be done automatically, just like we do when
    users create a GitHub Issue.
    
    Note that the bulk of the description comes from gluster-block. Just
    like most Gerrit maintained projects, it uses 'git review' and not a
    custom ./rfc.sh. New contributors that are familiar with Gerrit, will
    prefer the 'git review' approach over ./rfc.sh (which we want to
    deprecate or at least have it use 'git review' too).
    
    Change-Id: Ide36cbd80fdaaf238ea35ae5932a0cd21fc41f36
    Updates: #381
    URL: https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit ff127dec90b80ac7d609087594ee5466acf76390
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Jan 30 12:51:36 2018 +0530

    build: Add new glusterfs4 source files to gitignore
    
    Change-Id: I4e6439d0f1ab55528c0f7e23c437c7b62628b8e4
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit ab068bcc9ef362cf25b3883bbf316a440373817e
Author: Milan Zink <mzink@redhat.com>
Date:   Thu Jan 11 11:43:40 2018 +0100

    Fix disabled-quota-root-xattr-heal.sh hook script
    
    Fixing all shellchek warnings and POSIX incomapatibilities
    
    Change-Id: I35772bfcf7344c6ed9bd2a7db300c8f58bd3b243
    BUG: 1500649
    Signed-off-by: Milan Zink <zeten30@gmail.com>

commit c142d26e44436d805e476f2d13ac8726052a59c4
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Jan 25 10:03:09 2018 +0530

    rpc: Showing some unusual timer error logs during brick stop
    
    Solution: Update msg condition in gf_timer_call_after function
              to avoid the message
    
    BUG: 1538427
    Change-Id: I849e8e052a8259cf977fd5e7ff3aeba52f9b5f27
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 016165c4110b2bd5bba5c64b7a3d09e9bc4928c2
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Jan 26 16:07:59 2018 +0530

    tests: merge stdout and stderr output
    
    Add -m argument to 'prove' command-line.
    
    Fix xxhsum.c debugging output to keep 'prove' happy.
    
    Change-Id: I03485d5f5e43ae4ce454a275ec98bc18384ed00c
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit d25b6065469eb978d40450b5aebcf5711fb50205
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jan 26 15:34:43 2018 +0530

    quiesce, gfproxy: Implement failover across multiple gfproxy nodes
    
    Updates: #242
    Change-Id: I767e574a26e922760a7130bd209c178d74e8cf69
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 9bbee1c2bc91d194d7470dfe2351b7d8c7abe102
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Thu Jan 25 06:52:32 2018 -0800

    core: add some examples of site.h usage
    
    Change-Id: I6ce574a593eda8f3a6b2fc8969b5edf7c250b61c
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>

commit 3e78ea991b213422fc423ff94994e1eb295569c7
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Oct 15 15:04:34 2015 +0530

    protocol: Remove lock recovery logic from client and server
    
    Change-Id: I27f5e1e34fe3eac96c7dd88e90753fb5d3d14550
    BUG: 1272030
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 596143a286079338c30c8abc4b862f8d6ddddb3a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jan 29 12:42:51 2018 +0530

    geo-rep: Remove unused working directory check in gsyncd
    
    To append the default config file path, gsyncd calls gluster
    command to get the workdir path and constructs config file path.
    This is not required now since the Config management in Geo-replication
    is changed with patch 18257(Issue #73)
    
    BUG: 1539545
    Change-Id: Ia7eb39e36ed59ece4de65ea7ec71a0f615e338bb
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 5d3c90d14839fc134580a4ff944d68f3ff3c605a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Jan 23 15:56:45 2018 +0530

    geo-rep: Detailed JSON output for config
    
    JSON output of `config-get` command now returns in the following
    format
    
        {
            "name": CONFIG_NAME,
            "value": CONFIG_VALUE,
            "default_value": DEFAULT_VALUE,  # Only if modified == true
            "configurable": true|false,
            "modified": true|false
        }
    
    Change-Id: I6193de48cd33655df7ecef5a0d83d7cb147089cf
    Fixes: #361
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit c3647b747af88e40334e927dafdbf88154b308f0
Author: Jan Engelhardt <jengelh@inai.de>
Date:   Thu Dec 14 19:43:43 2017 +0100

    build: restore ability to control verbosity settings
    
    `make V=1` is broken — no commands are printed whatsoever. At the
    same time, `make V=0` *also* is broken in that no summary lines
    ("CC  foo.o") are printed, either. Kill the annoying hardcoded
    --quiet in configure.ac, since it seems to override everything that
    automake offers.
    
    Change-Id: I377c0e0469619a33586afb4a93dde6d241e7bc21
    Fixes: #381
    BUG: 1539023
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    [ndevos: silence rpc/xdr/gen rpgcen]

commit 1a519f4bf960c6aafecfb189e8ec8b153abcf6ce
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Jan 10 15:01:59 2018 +0530

    gfapi : New APIs have been added to use lease feature in gluster
    
    Following APIs glfs_h_lease(), glfs_lease() added, so that gfapi applications
    can set and get lease which enables more efficient client side caching.
    
    Updates: #350
    Change-Id: Iede85be9af1d4df969b890d0937ed0afa4ca6596
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit cd66e4edae84033f426820e359927272ad4ae641
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 23 14:06:10 2018 +0530

    debug/io-stats: io-stats options for GD2
    
    Updates #302
    
    Change-Id: I8e7ff391cec88ea76f63ffe05b7404bdb31eaf8e
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 6b4432388c112457aa11270736c593664c2f0bc6
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 23 12:12:14 2018 +0530

    features/shard: shard options for GD2.
    
    Updates #302
    
    Change-Id: Ife21440ffcf5805ce5858360dc94a456ead891e5
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 3cad44e8a7a0c481f3d1311b18aa854e4b33a1fb
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jan 25 10:39:19 2018 -0500

    build: use libtirpc by default, even if ipv6 is not the default
    
    Another error snuck in with Change-Id I86f847dfd, or more
    accurately I think, with Change-Id: Ic47065e9c2...
    
    All libs, not just libgfrpc, need to be linked with libtirpc,
    especially on systems that still have xdr functions in (g)libc
    where you will get a mixture of calls to libtirpc functions
    and glibc functions, with catastrophic results.
    
    BUG: 1536186
    Change-Id: I97dc39c7844f44c36fe210aa813480c219e1e415
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit ae7d5d26ffe38b3be6b9a9bc1883075491c1c709
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jan 24 12:56:14 2018 -0500

    packaging: python-ctypes only in RHEL <= 7
    
    And we don't need multiple BuildRequires: python-ctypes for sub-packages
    when it's (already) set for the base package.
    
    Change-Id: I71a2d750f338d360d5f716b1f0c4814e4e617b04
    BUG: 1538258
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit b7844629bb4b46c11a1e6de9a383fd46b597c648
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jan 23 08:23:11 2018 +0530

    glusterd: add profile_enabled flag in get-state
    
    Change-Id: I09f348ed7ae6cd481f8c4d8b4f65f2f2f6aad84e
    BUG: 1537364
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 9d708a3739c8201d23f996c413d6b08f8b13dd90
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jan 22 09:49:34 2018 +0530

    glusterd: process pmap sign in only when port is marked as free
    
    Because of some crazy race in volume start code path because of friend
    handshaking with volumes with quorum enabled we might end up into a situation
    where glusterd would start a brick and get a disconnect and then immediately try
    to start the same brick instance based on another friend update request. And
    then if for the very first brick even if the process doesn't come up at the end
    sign in event gets sent and we end up having two duplicate portmap entries for
    the same brick. Since in brick start we mark the previous port as free, its
    better to consider a sign in request as no op if the corresponding port type is
    marked as free.
    
    Change-Id: I995c348c7b6988956d24b06bf3f09ab64280fc32
    BUG: 1537362
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 7631b22a5960363518ad13da8661c76a1ffec253
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jan 24 11:41:39 2018 +0100

    build: use libtirpc by default, even if ipv6 is not the default
    
    An error sneaked in with Change-Id I86f847dfd. The check for requiring
    libtirpc-devel should be done regardless of the ipv6-default. Even if
    IPv6 is not the default, libtirpc-devel should be used unless it is
    explicitly requested by a --without option.
    
    libtirpc can not be used on EL6 and EL7 yet. The EL7 version does not
    provide xdr_sizeof(), in addition to that, EL6 does not have
    xdr_uint32_t() and xdr_uint64_t().
    
    BUG: 1536186
    Change-Id: I4a8292de2eddad16137df5998334133fc1e11261
    Fixes: 0c57232ae07f48bd6483bfe88a182f832377ef52
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit cb98b495a90da1fda452f118275f52053e8305e9
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jan 23 15:03:33 2018 +0530

    cluster/dht: Skip '..' for the volume root dir
    
    dht_populate_inode_for_dentry tries to update the layout
    for the '..' entry when listing the root of the volume.
    This entry does not correspond to an entry in the volume
    and therefore does not have a gfid or a layout on disk,
    causing layout processing to fail.
    
    Change-Id: I2b7470e1c5e20d87b5545160697f24d041045140
    BUG: 1537457
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 0c57232ae07f48bd6483bfe88a182f832377ef52
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jan 18 15:24:00 2018 -0500

    build: glibc has removed rpc headers and rpcgen in Fedora28, use libtirpc
    
    Other Linux distributions are doing the same; some others have already
    done so.
    
    Switch to libtirpc(-devel) and unbundled rpcgen packages. For now
    rpcgen is still provided by the glibc-rpcgen RPM, but rpcsvc-proto's
    rpcgen subpackage is available now but will not be used until
    glibc-rpcgen is retired. (note, rpcsvc-proto's rpcgen is just named
    rpcgen-...rpm. I.e. not rpcsvc-proto-rpcgen.) Right now either one
    will satisfy the BuildRequires: rpcgen.
    
    Also, when a .spec file has
      BuildRequires: foo-devel
    it is not necessary to also have:
      BuildRequires: foo
    or even:
      BuildRequires: foo foo-devel
    
    The foo-devel package has a dependency on foo, which will install foo
    automatically. It's usually also not necessary to have a corresponding
      Requires: foo
    as the rpmbuild process will also automatically determine the
    install-time dependencies.
    
    And other minor glusterfs.spec.in cleanup of ipv6-default, including
    sorting the argument definitions because the comment says "keep them
    sorted" (Though nobody appears to have ever sorted them in the first
    place.)
    
    Change-Id: I86f847dfda0fef83e22c6e8b761342d652a2d9ba
    BUG: 1536186
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 78868033bc208bdb681266d0129e66f5627295a2
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Mon Jan 22 14:38:17 2018 +0530

    dentry fop serializer: added new server side xlator for dentry fop serialization
    
    Problems addressed by this xlator :
    
    [1]. To prevent race between parallel mkdir,mkdir and lookup etc.
    
    Fops like mkdir/create, lookup, rename, unlink, link that happen on a
    particular dentry must be serialized to ensure atomicity.
    
    Another possible case can be a fresh lookup to find existance of a path
    whose gfid is not set yet. Further, storage/posix employs a ctime based
    heuristic 'is_fresh_file' (interval time is less than 1 second of current
    time) to check fresh-ness of file. With serialization of these two fops
    (lookup & mkdir), we eliminate the race altogether.
    
    [2]. Staleness of dentries
    
    This causes exponential increase in traversal time for any inode in the
    subtree of the directory pointed by stale dentry.
    
    Cause :  Stale dentry is created because of following two operations:
    
          a. dentry creation due to inode_link, done during operations like
             lookup, mkdir, create, mknod, symlink, create and
          b. dentry unlinking due to various operations like rmdir, rename,
             unlink.
    
           The reason is __inode_link uses __is_dentry_cyclic, which explores
           all possible path to avoid cyclic link formation during inode
           linkage. __is_dentry_cyclic explores stale-dentry(ies) and its
           all ancestors which is increases traversing time exponentially.
    
    Implementation : To acheive this all fops on dentry must take entry locks
    before they proceed, once they have acquired locks, they perform the fop
    and then release the lock.
    
    Some documentation from email conversation:
    [1] http://www.gluster.org/pipermail/gluster-devel/2015-December/047314.html
    
    [2] http://www.gluster.org/pipermail/gluster-devel/2015-August/046428.html
    
    With this patch, the feature is optional, enable it by running:
    
     `gluster volume set $volname features.sdfs enable`
    
    Also the feature is tested for a month without issues in the
    experiemental branch for all the regression.
    
    Change-Id: I6e80ba3cabfa6facd5dda63bd482b9bf18b6b79b
    Fixes: #397
    BUG: 1304962
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 5cbe21b1ddf6eae4782afa33ce841fc4aa195974
Author: Nigel Babu <nigelb@redhat.com>
Date:   Tue Jan 23 20:46:25 2018 +0530

    tests: Disable geo-rep tests
    
    These tests are prone to issues at the moment that need further
    debugging and fixing.
    
    BUG: 1537602
    Change-Id: Ic59ca620925c6f43948b8a751eaddb571b791969
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit 93f21655e1584c7369aa74f3072de0dc1a3e8119
Author: Nigel Babu <nigelb@redhat.com>
Date:   Mon Jan 22 08:36:36 2018 +0530

    libglusterfs: Reset errno before call
    
    This was causing Gluster to return a failure when testing on Centos7.
    
    BUG: 1536913
    Change-Id: Idb90baef05058123a7f69e94a51dd79abd371815
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit a35f158f1cbe142a1f65bfc5f3c7584ec3e7bab0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jan 9 11:37:59 2018 +0530

    features/error-gen: update volume options for GD2
    
    Updates #302
    
    Change-Id: I8d04bb4f46b1e53a8d176a75da2382fdbf0cfc6f
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 7c9b62cfff34d1ac4c8fa0822b18e51c15e6db81
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Nov 30 12:52:30 2017 +0530

    geo-rep: Support for using Volinfo from Conf file
    
    Once Geo-replication is started, it runs Gluster commands to get Volume
    info from Master and Slave. With this patch, Georep can get Volume info
    from Conf file if `--use-gconf-volinfo` argument is specified to monitor
    
    Create a config(Or add to the config if exists) with following fields
    
        [vars]
        master-bricks=NODEID:HOSTNAME:PATH,..
        slave-bricks=NODEID:HOSTNAME,..
        master-volume-id=
        slave-volume-id=
        master-replica-count=
        master-disperse_count=
    
    Note: Exising Geo-replication is not affected since this is activated
    only when `--use-gconf-volinfo` is passed while spawning `gsyncd
    monitor`
    
    Tiering support is not yet added since Tiering + Glusterd2 is still
    under discussion.
    
    Fixes: #396
    Change-Id: I281baccbad03686c00f6488a8511dd6db0edc57a
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 8efa3ee675a991410c6aa27dce40d4dd441d0935
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat Jan 6 02:53:15 2018 +0100

    performance/read-ahead: volume option fixes for GD2
    
    Updates #302
    
    Change-Id: I842ab746502bc4ff3b312ee19f397a6177edc6f7
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 0c1eb282aad1a8b210b2f77efe57a3c35c4bee70
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Jan 19 03:54:02 2018 -0500

    protocol/server: Fix "auth-path" in options table
    
    Options set will crash the brick with glusterd2.
    glusterd used to set "auth-path" during volfile
    generation. With glusterd2, it should come from
    options table.
    
    Updates: #302
    Change-Id: Ie41a17779c185b87ace7e0bce0d0ba594b415a75
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit b1abe3c1baa5c132d32f7c6eedf3f9255534ed37
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat Jan 6 02:53:45 2018 +0100

    performance/write-behind: volume option fixes for GD2
    
    Updates #302
    
    Change-Id: I2ade3dc4aef4da619c5b64058872594f0f1e004f
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit ec3df9e65a3a2e1005cd4d50d06a8819fd3ab5f6
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Jan 19 14:35:18 2016 +0530

    libgfapi: Add new api for supporting mandatory-locks
    
    The current API for byte-range locks [glfs_posix_lock()] doesn't
    allow applications to specify whether it is advisory or mandatory
    type locks. This particular change is to introduce an extended
    byte-range lock API with an additional argument for including
    the byte-range lock mode to be one among advisory(default) or
    mandatory. Patch also includes a gfapi test case which make use
    of this new api to acquire mandatory locks.
    
    Ref: https://github.com/gluster/glusterfs-specs/blob/master/done/GlusterFS%203.8/Mandatory%20Locks.md
    
    Change-Id: Ia09042c755d891895d96da857321abc4ce03e20c
    Updates #393
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 10d74166f17fa44c06bd1357e0a4b0b052265425
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Fri Sep 1 15:04:09 2017 +0530

    cluster/ec : EC options for GD2
    
    Updates #302
    
    Change-Id: I31b4648f7b1a394fceece5cba8120c579c66edd9
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit e3b217155b489fc1d6fd29c221a986b894f391db
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jan 18 22:59:00 2018 -0500

    geo-rep: Improve geo-rep pre-validation logs
    
    Geo-rep runs gverify.sh which does pre-validation.
    As part of it, master and slave volume is mounted
    to verify the size. If for some reason, the mount
    fails, the error message does not point out the
    mount log file location. Also both master and
    slave mount logs are same.
    
    Patch does following improvements.
    
    1. Master and slave mount logs are separated and
       error message points the log file to be looked for.
    2. The log location is changed to /var/log/glusterfs/geo-replication
       instead of /var/log/glusterfs/geo-replication-slaves
    3. The log file name is changed to "gverify-mastermnt.log" and
       "gverify-slavemnt.log" for master and slave mount respectively
    
    Fixes: #395
    Change-Id: Ia644ec0afebbdaae92e01adf03c635e5f8866a02
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 24bf7715140586675f8d2036f4d589bc255c16dc
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jan 9 17:26:44 2018 +0530

    md-cache: Implement dynamic configuration of xattr list for caching
    
    Currently, the list of xattrs that md-cache can cache is hard coded
    in the md-cache.c file, this necessiates code change and rebuild
    everytime a new xattr needs to be added to md-cache xattr cache
    list.
    
    With this patch, the user will be able to configure a comma
    seperated list of xattrs to be cached by md-cache
    
    Updates #297
    
    Change-Id: Ie35ed607d17182d53f6bb6e6c6563ac52bc3132e
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 303cc2b54797bc5371be742543ccb289010c92f2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Dec 22 13:12:42 2017 +0530

    protocol: make on-wire-change of protocol using new XDR definition.
    
    With this patchset, some major things are changed in XDR, mainly:
    
    * Naming: Instead of gfs3/gfs4 settle for gfx_ for xdr structures
    * add iattx as a separate structure, and add conversion methods
    * the *_rsp structure is now changed, and is also reduced in number
      (ie, no need for different strucutes if it is similar to other response).
    * use proper XDR methods for sending dict on wire.
    
    Also, with the change of xdr structure, there are changes needed
    outside of xlator protocol layer to handle these properly. Mainly
    because the abstraction was broken to support 0-copy RDMA with payload
    for write and read FOP. This made transport layer know about the xdr
    payload, hence with the change of xdr payload structure, transport layer
    needed to know about the change.
    
    Updates #384
    
    Change-Id: I1448fbe9deab0a1b06cb8351f2f37488cefe461f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 9eefff096fd9b54120e4347b6b00f10a6c502cf4
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Jan 10 14:54:30 2018 +0530

    gfapi : added glfs_setfsleaseid() for setting lease id
    
    A new function glfs_setfsleaseid() added in gfapi. Currently lock owner
    is saved in the thread context. Similarly the leaseid attribute can be
    saved using glfs_setfsleaseid().
    
    Updates: #350
    Change-Id: I55966cca01d0f2649c32b87bd255568c3ffd1262
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit a40a87ec3b226ae86a6ed8f4af25b45965a20cad
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jan 18 14:21:57 2018 +0530

    afr: add quorum checks in post-op
    
    afr relies on pending changelog xattrs to identify source and sinks and the
    setting of these xattrs happen in post-op. So if post-op fails, we need to
    unwind the write txn with a failure.
    
    Change-Id: I0f019ac03890108324ee7672883d774918b20be1
    BUG: 1506140
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit e2323cc387562b3b65ee4e57b73a223182c48abf
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jan 4 19:39:05 2018 +0530

    readdir-ahead: Cleanup the xattr request code
    
    Updates #297
    
    Change-Id: Ia0c697583751290a455da3cd1894e0c5685d1bd8
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit efc30e60e233164bd4fe7fc903a7c5f718b0448b
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jan 9 10:32:16 2018 +0530

    upcall: Allow md-cache to specify invalidations on xattr with wildcard
    
    Currently, md-cache sends a list of xattrs, it is inttrested in recieving
    invalidations for. But, it cannot specify any wildcard in the xattr names
    Eg: user.* - invalidate on updating any xattr with user. prefix.
    
    This patch, enable upcall to honor wildcard in the xattr key names
    
    Updates: #297
    
    Change-Id: I98caf0ed72f11ef10770bf2067d4428880e0a03a
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 890078423b4b720dd124f07c975e834695bcc915
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jan 18 05:43:56 2018 +0000

    geo-rep: Validate availability of gluster binary on slave
    
    1. Adds validation to check if gluster binary is available on slave
    2. Add a simple geo-rep setup test case to verify whether setup is fine.
       It's named in such a way that it runs first.
    
    BUG: 1532591
    Change-Id: Ie777e55ae13db8fa97d4e32464ad82269ee5fd07
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit dc70cf124c1625a0ada4b25cb0e055f5b6895036
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 2 21:17:09 2018 +0530

    features/locks: volume option fixes for GD2
    
    Updates #302
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Change-Id: I1667fc32b7a31562b289fcab878d94be202407e4

commit 8fc9c6a8fc7c73b2b4c65a8ddbe988bca10e89b6
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jan 4 19:38:05 2018 +0530

    posix: In getxattr, honor the wildcard '*'
    
    Currently, the posix_xattr_fill performas a sys_getxattr
    on all the keys requested, there are requirements where
    the keys could contain a wildcard, in which case sys_getxattr
    would return ENODATA, eg: if the xattr requested is user.*
    all the xattrs with prefix user. should be returned, with their
    values.
    
    This patch, changes posix_xattr_fill, to honor wildcard in the keys
    requested.
    
    Updates #297
    
    Change-Id: I3d52da2957ac386fca3c156e26ff4cdf0b2c79a9
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 84c5c540b26c8f3dcb9845344dd48df063e57845
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Jan 17 17:30:06 2018 +0530

    cluster/afr: Adding option to take full file lock
    
    Problem:
    In replica 3 volumes there is a possibilities of ending up in split
    brain scenario, when multiple clients writing data on the same file
    at non overlapping regions in parallel.
    
    Scenario:
    - Initially all the copies are good and all the clients gets the value
      of data readables as all good.
    - Client C0 performs write W1 which fails on brick B0 and succeeds on
      other two bricks.
    - C1 performs write W2 which fails on B1 and succeeds on other two bricks.
    - C2 performs write W3 which fails on B2 and succeeds on other two bricks.
    - All the 3 writes above happen in parallel and fall on different ranges
      so afr takes granular locks and all the writes are performed in parallel.
      Since each client had data-readables as good, it does not see
      file going into split-brain in the in_flight_split_brain check, hence
      performs the post-op marking the pending xattrs. Now all the bricks
      are being blamed by each other, ending up in split-brain.
    
    Fix:
    Have an option to take either full lock or range lock on files while
    doing data transactions, to prevent the possibility of ending up in
    split brains. With this change, by default the files will take full
    lock while doing IO. If you want to make use of the old range lock
    change the value of "cluster.full-lock" to "no".
    
    Change-Id: I7893fa33005328ed63daa2f7c35eeed7c5218962
    BUG: 1535438
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit badf662b1521ed6158f42a6ac11024ae80d99ecc
Author: krad <krad@fb.com>
Date:   Tue Dec 5 13:53:27 2017 -0800

    distributed-tests: Framework for running tests on a worker cluster
    
    Summary: This framework helps distribute running of unit tests on a cluster of machines.
    
    Test Plan: Run tests on fb cluster
    
    Reviewers: sshreyas, jdarcy
    
    Change-Id: If309f504d9aa959cc8b01c85bff3b5503a890ff1
    updates #374
    Signed-off-by: krad <krad@fb.com>

commit bee06ccd7b80e3f5804f0c7c7c56936fed6d2b4e
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Jan 17 18:03:11 2018 +0530

    selinux-xlator : validate dict before calling dict_rename_key()
    
    Change-Id: I71da3b64e5e8c82e8842e119b2b05da3e2ace550
    BUG: 1535772
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit 2db7872d5251d98d47c262ff269776bfae2d4fb9
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Aug 7 11:24:46 2017 +0530

    md-cache: Serve nameless lookup from cache
    
    Updates #232
    Change-Id: I97e92312a53a50c2d1660bf8d657201fc05a76eb
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit c2fa8a94342b0cfbce9393f513099b8751711eae
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jan 8 09:55:37 2018 +0530

    fix features/leases: volume option fixes for GD2
    
    Updates #302
    
    Change-Id: I31091765b5bfd118fc5370b3515128f0e84e360f
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 80a6a2357c0c0351691c450c40de820efce7ff6f
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Oct 25 17:00:36 2017 +0530

    readdir-ahead: Add parallel-readdir option in readdir-ahead
    
    parallel-readdir option is defined as belonging to readdir-ahead
    in glusterd-volume-set.c, but was not defined in options of
    readdir-ahead, fixing the same.
    
    Change-Id: I97cc88b38ab99ade5f066519ca1cb9bfed03a7da
    BUG: 1506197
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit e6feebbb52c0833928d2acd51dd631d7ce5f2ecd
Author: Varsha Rao <varao@redhat.com>
Date:   Mon Jan 15 14:20:51 2018 +0530

    performance/io-threads: Fix checked_return coverity error
    
    Change the return type of set_stack_size function to integer and also
    check the return value of pthread_attr_init(). This fixes the
    Checked_Return coverity issue.
    
    Change-Id: I270b8bd168b09f0b071437c117e4e23b01398534
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 00751d5abebd538cafdee885cd7b63bb06b20f66
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jan 17 03:54:24 2018 -0500

    features/bit-rot: Fix default value for scrub-throttle
    
    Updates #302
    Change-Id: Ifc23d5f8b5bc78b95f7c9d92d6df37a9168102f7
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit ce5832cf0350855da485479a48598eb962e58abd
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jan 17 19:16:15 2018 +0530

    make sure geo-rep tests run first
    
    as we run regression with a 'sort' function, geo-rep thus becomes last test to run.
    instead, make sure it is the first test by changing the name of directory, and thus
    any setup failures would be noticed much earlier.
    
    Change-Id: I9e8d81824274900be42c4c49c752a1602497fa31
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 75b063d76d78b5d1e0e53a1be37dc5ad9200f7b2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Nov 7 00:07:12 2017 +0530

    rpc/*: auth-header changes
    
    Introduce another authentication header which can now send more data.
    This is useful because this data can be common for all the fops, and
    we don't need to change all the signatures.
    
    As part of this, made rpc-clnt.c little more modular to support multiple
    authentication structures.
    
    stack.h changes are placeholder for the ctime etc, can be moved later
    based on need.
    
    updates #384
    
    Change-Id: I6111c13cfd2ec92e2b4e9295896bf62a8a33b2c7
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e3a191a0d3ea0706f4827ebdb6e5161623f2c5f1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jan 9 16:03:15 2018 +0530

    dict: add another type to handle backward compatibility
    
    This new type helps to avoid excessive logs. It should be
    set only in case of
     * volume graph building (graph.y)
     * dict unserialize
       (happens once a dictionary is received on wire in old protocol)
    
    All other dict set and get should have proper check and warning
    logs if there is a mismatch.
    
    updates #220
    
    Change-Id: I1cccb304a877aa80c07aaac95f10f5005e35b9c5
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 6f877d04d6b1b9e0e10904c1a9da9e671bccb290
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jan 8 11:22:58 2018 +0530

    features/bit-rot: fix volume options for GD2
    
    Updates #302
    
    Change-Id: I8809f269b93253bce049fdbf28a7f44e85a2b9e7
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 1b2a3a417f62a7b2aa15918d7be449c243d96b94
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jan 16 00:37:45 2018 +0100

    fuse: write out reverse notification to fuse dump
    
    BUG: 1534602
    Change-Id: Ide42cf9cffe462d0cc46272b327c2a05999f09ba
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit 9404b0de3fd8ab5adc3a531d4cb37b56e1e3908f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jan 5 13:51:18 2018 +0530

    core: fix some of the dict_{get,set} with proper APIs
    
    updates #220
    
    Change-Id: I6e25dbb69b2c7021e00073e8f025d212db7de0be
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 7ba7a4b27d124f4ee16fe4776a4670cd5b0160c4
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Jun 15 14:42:19 2016 +0200

    locks: added inodelk/entrylk contention upcall notifications
    
    The locks xlator now is able to send a contention notification to
    the current owner of the lock.
    
    This is only a notification that can be used to improve performance
    of some client side operations that might benefit from extended
    duration of lock ownership. Nothing is done if the lock owner decides
    to ignore the message and to not release the lock. For forced
    release of acquired resources, leases must be used.
    
    Change-Id: I7f1ad32a0b4b445505b09908a050080ad848f8e0
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>

commit 3e9a9c029fac359477fb26d9cc7803749ba038b2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Dec 28 16:02:59 2017 +0530

    posix: delete stale gfid handles in nameless lookup
    
    ..in order for self-heal of symlinks to work properly (see BZ for
    details).
    
    Change-Id: I9a011d00b07a690446f7fd3589e96f840e8b7501
    BUG: 1529488
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 5442fb502b360406f8de9787828da2339790da88
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Thu Jan 11 23:02:49 2018 +0530

    tests: EC test fails with brick mux enabled
    
    Problem:
    With brick mux enabled get_fd_count count was returning
    wrong value due to parsing issue.
    
    Solution:
    Updated the code to fix parsing problem.
    
    BUG: 1533594
    Change-Id: I5d7ff6843b4760f866c4a5aab2f13ff7380f248e
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit c494445c886e16ddc6a960b9074a68fe9621ee09
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jan 12 10:51:44 2018 +0530

    storage/posix: Set f_bfree to 0 if brick full
    
    Return 0 free blocks if the brick is full or
    has less than the reserved limit.
    
    Change-Id: I2c5feda0303d0f4abe5af22fac903011792b2dc8
    BUG: 1533736
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 0f653fe4fb3a654af65fda736fa23cf0ec9f741c
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Tue Jan 9 16:58:22 2018 +0800

    performance/readdir-ahead: fix cache usage update issue
    
    Use atomic operation to modify cache-size to protect it from concurrent
    modification.
    
    Change-Id: Ie73cdd4abbaf0232b1db4ac856c01d24603890ad
    BUG: 1533804
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit ba149bac92d169ae2256dbc75202dc9e5d06538e
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Dec 18 16:46:39 2017 +0530

    cluster/afr: Fixing the flaws in arbiter becoming source patch
    
    Problem:
    Setting the write_subvol value to read_subvol in case of metadata
    transaction during pre-op (commit 19f9bcff4aada589d4321356c2670ed283f02c03)
    might lead to the original problem of arbiter becoming source.
    
    Scenario:
    1) All bricks are up and good
    2) 2 writes w1 and w2 are in progress in parallel
    3) ctx->read_subvol is good for all the subvolumes
    4) w1 succeeds on brick0 and fails on brick1, yet to do post-op on
       the disk
    5) read/lookup comes on the same file and refreshes read_subvols back
       to all good
    6) metadata transaction happens which makes ctx->write_subvol to be
       assigned with ctx->read_subvol which is all good
    7) w2 succeeds on brick1 and fails on brick0 and this will update the
       brick in reverse order leading to arbiter becoming source
    
    Fix:
    Instead of setting the ctx->write_subvol to ctx->read_subvol in the
    pre-op statge, if there is a metadata transaction, check in the
    function __afr_set_in_flight_sb_status() if it is a data/metadata
    transaction. Use the value of ctx->write_subvol if it is a data
    transactions and ctx->read_subvol value for other transactions.
    
    With this patch we assign the value of ctx->write_subvol in the
    afr_transaction_perform_fop() with the on disk value, instead of
    assigning it in the afr_changelog_pre_op() with the in memory value.
    
    Change-Id: Id2025a7e965f0578af35b1abaac793b019c43cc4
    BUG: 1482064
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit e9358bc4d275602529a4a0167ebaa053db3a0e1b
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Jan 10 09:09:24 2018 +0530

    perf/io-cache: Update options for gd2
    
    Update io-cache options for GD2
    
    Updates gluster/glusterfs#302
    
    Change-Id: I7fabf912d1e3cd024989404526db0a29644768c7
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit b8e6f962c6f60fa49ae2844c431e6a6101a3df26
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Jan 12 15:29:51 2018 +0530

    cluster/ec Mark ./tests/basic/ec/heal-info.t as bad test
    
    Change-Id: I7369fdd7510cc7ebf051cc621fc83764ba9591f3
    BUG: 1533815
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit cf37aa990797e520945491134e1e5af4e2107711
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jan 5 10:22:45 2018 -0500

    rpc: use export map to minimize exported symbols in libgf{rpc,xdr}.so
    
    Without an export map (at link time) libgrpc and libgfxdr export over
    150 and 450 symbols each, respectively. Many are not used by anything
    else. (Unclear what the unused symbols are, some may be simple
    sloppiness, e.g. not declaring functions static that should be. Others
    may be intra-library calls that can't be static but aren't part of the
    API, per se.)
    
    By linking with an export map the number of exported symbols is
    reduced to ~60 and ~250 respectively.
    
    This parallels the similar change made to libglusterfs recently
    and the older changes to the xlators to minimize the symbols that
    are visible (exported) from the .so.
    
    And I don't know, do we want to go all the way to symbol versions?
    For these libs? And for libglusterfs?
    
    fixes gluster/glusterfs#392
    
    Change-Id: I9cdc3eee10e5f1408d7e7f2f29fad597c97e4003
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit b8a319db3dc37e452a27c5fb2efd7668ff81743c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jan 12 10:07:28 2018 +0530

    tests: check volume status for shd being up
    
    so that glusterd is also aware that shd is up and running.
    
    While not reproducible locally, on the jenkins slaves, 'gluster vol heal patchy'
    fails with "Self-heal daemon is not running. Check self-heal daemon log file.",
    while infact the afr_child_up_status_in_shd() checks before that passed. In the
    shd log also, I see the shd being up and connected to at least one brick before
    the heal is launched.
    
    Change-Id: Id3801fa4ab56a70b1f0bd6a7e240f69bea74a5fc
    BUG: 1515163
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit f0bcb7c511b5ced0564ae27c6a2296434a4f348e
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Jan 10 08:33:23 2018 +0530

    cluster/dht: Update options for gd2
    
    Update DHT options for GD2
    
    Updates gluster/glusterfs#302
    
    Change-Id: Ia597fe364e97edd7bcf72d89f4ccdd50713a8837
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 0e4fdfbc4fec55cdc3eb6e0e27408682afe22696
Author: Anoop C S <anoopcs@redhat.com>
Date:   Mon Jan 8 17:32:05 2018 +0530

    build: Link libgfrpc within rpc-transport shared libraries
    
    Now with https://review.gluster.org/#/c/19056/ merged, we perform
    dlopen() with RTLD_LOCAL so that every shared library is expected to
    be explicitly linked against other required libraries.
    
    "undefined symbol ..." was seen while trying to access GlusterFS volumes
    via NFS-Ganesha/Samba using libgfapi resulting in an unusable state.
    
    This is a follow-up patch to https://review.gluster.org/#/c/17659/
    to make sure that we link libgfrpc too while making socket and rdma
    rpc-transport shared libraries.
    
    Change-Id: I9943cdc449c257ded3cb9f9f2becdd5784d1d82d
    BUG: 1532238
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit a601db69c771ab0d541815d2dd46183892e554c9
Author: Varsha Rao <varao@redhat.com>
Date:   Sun Jan 7 12:33:21 2018 +0530

    cluster/dht: Change datatype of search_unhashed variable
    
    Variable search_unhashed is of type boolean, change it to integer type.
    This fixes the warning increment of a boolean expression.
    
    BUG: 1531987
    
    Change-Id: Ibf153f6a9ad704da38bff346b6a21a71323ed9bb
    Signed-off-by: Varsha Rao <varao@redhat.com>

commit 6ad4c7ff050de6faa267e42a09ba35b8641f15db
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jan 4 22:07:54 2018 +0530

    glusterd: get-state memory leak fix
    
    Change-Id: Ic4fcf2087f295d3dade944efb8fd08f7e2d7d516
    BUG: 1531149
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 5c22aed3f076544f3d6d276093b51225d5851b2e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 8 11:53:17 2018 +0530

    tests: Use /dev/urandom instead of /dev/random for dd
    
    If there's not enough entropy in the system then reading /dev/random would take
    a significant time since it would take a long time for the /dev/random buffers
    to get full as is desired in this dd run.
    Milind found that this test file takes almost a 1000 seconds or more to pass
    instead of just a minute because of this.
    
    BUG: 1431955
    Change-Id: I9145b17f77f09d0ab71816ae249c69b8fe14c1a5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 013e06bf99ee1e0e374d140bef5ddc92d62b4418
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Jan 5 15:29:13 2018 +0100

    glusterd: fix up volume option flags
    
    In glusterd volfile generation code options should be ornamented
    with the VOLOPT_FLAG_* flags. However, some are ornamented with
    OPT_FLAG_* flags (which are to be used in xlator context).
    
    The impact is: the OPT_FLAG_* that occurs is OPT_FLAG_CLIENT_OPT,
    which has the same value as VOLOPT_FLAG_XLATOR_OPT, so what was
    meant is "option affects clients" and what was there means
    "option enables/disables xlators". Because of this semantic
    shift, op version might be incorrectly calculated for volumes
    and clients. (At this point it's a theoretical possibility.
    Actual occurrence might depend on connecting client & server
    versions; it's also possible that there exists a proof of
    concept scenario but it's irrealistic.)
    
    This commit eliminates the OPT_FLAG_* occurrences from glusterd code,
    and replaces them with the appropriate VOLOPT_FLAG_* flags.
    
    Change-Id: Ia4e6fbac738d5a8d889c0f5561c4dea6783250b1
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit edf8224ab41c262098d18897337e9a809b480f12
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Jan 6 20:00:04 2018 +0530

    dict: fix VALIDATE_DATA_AND_LOG call
    
    Couple of instances doesn't pass enough number of parameters to the
    function resulting compilation to fail.
    
    Updates #203
    
    Change-Id: Id8caa6fe7fc611645ad7ff11d81a2462e4ec6bab
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 9b12157fea5ac054106ed14f9d91cdb8bad665c7
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Jan 5 11:17:46 2018 +0530

    Revert "rpc: merge ssl infra with epoll infra"
    
    This reverts commit 56e5fdae74845dfec0ff7ad0c8fee77695d36ad5.
    
    Change-Id: Ia62cee5440bbe8e23f5da9cff692d792091d544a
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 515a832de0e761639b1d076a59bf918070ec3130
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jan 5 11:35:26 2018 +0530

    libglusterfs: Include key name in data type validation
    
    Printing the key name makes it easier for developers
    to figure out which keys have dict data type mismatches.
    
    Updates #337
    
    Change-Id: I21d9a22488a4c5e5a8d991ca2d53f1e3039f7685
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 92430596d697381d5f49ff69eb24d9ff3e291da8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Dec 27 16:14:30 2017 +0530

    dict: add more types for values
    
    Added 2 more types which are present in gluster codebase, mainly
    IATT and UUID.
    
    Updates #203
    
    Change-Id: Ib6d6d6aefb88c3494fbf93dcbe08d9979484968f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 01caa839ebda29c2fe209c4767626f2f49ea3e71
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Jan 3 14:29:51 2018 +0530

    glusterd: connect to an existing brick process when qourum status is NOT_APPLICABLE_QUORUM
    
    First of all, this patch reverts commit 635c1c3 as the same is causing a
    regression with bricks not coming up on time when a node is rebooted.
    This patch tries to fix the problem in a different way by just trying to
    connect to an existing running brick when quorum status is not
    applicable.
    
    Change-Id: I0efb5901832824b1c15dcac529bffac85173e097
    BUG: 1509845
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 60a992e69a7cf5a588f5139709d325125d6f04fb
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Aug 11 04:55:18 2017 -0400

    tests: Enable geo-rep test cases
    
    This patch re-enables the geo-rep test cases.
    Along with it does following optimizations.
    
    1. Use EXPECT_WITHIN instead of sleep
    2. Clean up geo-rep ssh key after test
    3. Changes to gverify.sh and S56glusterd-geo-rep-create-post.sh
       to use the given ssh identity file for geo-rep create
    4. Make gluster-command-dir configurable and introduce
       slave-gluster-command-dir which points the parent directory
       of gluster binaries in master and slave respectively.
    
    Change-Id: Ia7696278d9dd3ba04224dcd7c3564088ca970b04
    BUG: 1480491
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 78d67da17356b48cf1d5a6595764650d5b200ba7
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Thu Mar 23 12:50:41 2017 +0530

    cluster/ec: OpenFD heal implementation for EC
    
    Existing EC code doesn't try to heal the OpenFD to
    avoid unnecessary healing of the data later.
    
    Fix implements the healing of open FDs before
    carrying out file operations on them by making an
    attempt to open the FDs on required up nodes.
    
    BUG: 1431955
    Change-Id: Ib696f59c41ffd8d5678a484b23a00bb02764ed15
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit fa903173540df5b82c295a8f7b24848098e49a41
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jan 4 12:24:48 2018 +0530

    cli: Fixed a use_after_free
    
    gf_event in cli_cmd_volume_create_cbk was accessing
    memory that had already been freed.
    
    Change-Id: I447c939fa9b31e18819a62c3b356c14cca390787
    BUG: 1530910
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 2632738aea79e61fda0381d3ac1c0a4a4560d32d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 2 20:53:27 2018 +0530

    debug/delay-gen: volume option fixes for GD2
    
    Updates #302
    Change-Id: I2c7ab85364337d0bc00428e0001ddc4038e08174
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 2170e661d005948c3ae568cd8035513dc9187e40
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 2 21:08:08 2018 +0530

    performance/io-threads: volume option fixes for GD2
    
    Updates #302
    Change-Id: I7145e46ed649f8e69118f164709f7131b7e580be
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 0e0fb43d322ade2e1187ea7e4389bf65c66a6ad7
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jan 2 20:26:31 2018 +0530

    glusterd: Nullify pmap entry for bricks belonging to same port
    
    Commit 30e0b86 tried to address all the stale port issues glusterd had
    in case of a brick is abruptly killed. For brick multiplexing case
    because of a bug the portmap entry was not getting removed. This patch
    addresses the same.
    
    Change-Id: Ib020b967a9b92f1abae9cab9492f0cacec59aaa1
    BUG: 1530281
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit c8012aaf48179227055a0543e8169630183a39d1
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Dec 28 11:23:29 2017 +0530

    cluster/dht: Use percentages for space check
    
    With heterogenous bricks now being supported in DHT
    we could run into issues where files are not migrated
    even though there is sufficient space in newly added bricks
    which just happen to be considerably smaller than older
    bricks. Using percentages instead of absolute available
    space for space checks can mitigate that to some extent.
    
    Marking bug-1247563.t as that used to depend on the easier
    code to prevent a file from migrating. This will be removed
    once we find a way to force a file migration failure.
    
    Change-Id: I3452520511f304dbf5af86f0632f654a92fcb647
    BUG: 1529440
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 26f00e5eeb3e5c37d3323c0fce87893a3b41bb5b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Dec 27 12:33:16 2017 -0500

    libglusterfs: export minimum necessary symbols
    
    minimize risk of symbol collisions in global namespace.
    
    see https://review.gluster.org/#/c/5697/ which Amar has
    resurrected.
    
    This is a strawman proposal to use an export-list to
    only export the necessary symbols from libglusterfs. I suppose
    some of this could be fixed by smarter use of static in the
    function definitions.
    
    It's a bit scary to see some of the names we expose. And then
    there are the names we use in the reserved namespace.
    
    One step short of going all the way to symbol versions
    
    fixes gluster/glusterfs#382
    
    Change-Id: Ifb848dfc655ef735dd27c73b7729e1188eb817f1
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 14dbd5da1cae64e6d4d2c69966e19844d090ce98
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Fri Dec 29 15:49:13 2017 +0100

    glusterfind: Speed up gfid lookup 100x by using an SQL index
    
    Fixes #1529883.
    
    This fixes some bits of `glusterfind`'s horrible performance,
    making it 100x faster.
    
    Until now, glusterfind was, for each line in each CHANGELOG.* file,
    linearly reading the entire contents of the sqlite database in
    4096-bytes-sized pread64() syscalls when executing the
    
      SELECT COUNT(1) FROM %s WHERE 1=1 AND gfid = ?
    
    query through the code path:
    
      get_changes()
        parse_changelog_to_db()
          when_data_meta()
            gfidpath_exists()
              _exists()
    
    In a quick benchmark on my laptop, doing one such `SELECT` query
    took ~75ms on a 10MB-sized sqlite DB, while doing the same query
    with an index took < 1ms.
    
    Change-Id: I8e7fe60f1f45a06c102f56b54d2ead9e0377794e
    BUG: 1529883
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>

commit 9fd17c1c3c44944ea280c4c15bad0d49b298b8a9
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 25 19:19:53 2017 +0530

    posix: Introduce flags for validity of iatt members
    
    v1 of the patch started off as adding new fields to iatt that can be
    filled up using statx but the discussions were more around introducing
    masks to check the validity of different fields from a RIO perspective.
    To that extent, I have dropped the statx call in this version and
    introduced a 64 bit mask for existing fields. The masks I have defined
    are similar with the statx() flags' masks.
    
    I have *not* changed iatt_to_stat() to use the macros IATT_TYPE_VALID,
    IATT_GFID_VALID etc before blindly copying from struct iatt to struct.
    
    Also fixed warnings in xlators because of atime/mtime/ctime seconds
    field change from uint32_t to int64_t.
    
    Change-Id: I4ac614f1e8d5c8246fc99d5bc2d2a23e7941512b
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit cc425b0de57d574f6e68b6ef5edfdf99cd8353af
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Dec 28 18:42:16 2017 +0530

    mgmt/glusterd: Adding validation for setting quorum-count
    
    In a replicated volume it was allowing to set the quorum-count value
    between the range [1 - 2147483647]. This patch adds validation for
    allowing only maximum of replica_count number of quorum-count value
    to be set on a volume.
    
    Change-Id: I13952f3c6cf498c9f2b91161503fc0fba9d94898
    BUG: 1529515
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit e126368f6b5231fb2acf307fbd8e343e52d61885
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Dec 27 23:15:37 2017 +0530

    snapshot : after brick reset/replace snapshot creation fails
    
    Problem : after brick reset/replace snapshot creation fails
    
    Solution : During brick reset/replace when we validate and aggrigate
               dictionary data from another node it was rewriting
               'mount_dir' value to NULL which is critical for snapshot
               creation.
    
    Change-Id: Iabefbfcef7d8ac4cbd2a241e821c0e51492c093e
    BUG: 1512451
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit d3cfd8dc8f7b774a8b081098f11237ebfa60156e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 24 23:20:27 2017 +0530

    quiesce: add fallocate and seek fops
    
    quiesce is useful in a gfproxy setup where if gfproxy machine goes
    down the fop would be replayed. Hence only added the fops which is
    supported by fuse layer to start with. With this patch, no behavior
    change is added (ie, volfile change etc). Just making sure to have
    the translator up-to-date so that if required we can consume it.
    
    Updates #242
    
    Change-Id: Id3bf204f2ccd42c3ac8f88d85836ecb855703e02
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit ab3664210420e45568e938d87d0d522521cefd47
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Dec 28 15:17:34 2017 +0530

    geo-rep: Log message improvements
    
    BUG: 1529480
    Change-Id: If4775ed9886990c0e1bcf4e44c7dfef95cc4f0c3
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 33c39e5dce3bc941d8e26c98d91f8ddab9505b73
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Dec 28 14:04:50 2017 +0530

    eventsapi: JWT signing without external dependency
    
    Added support for JWT signing without using python-jwt since it is not
    available in all the distributions.
    
    BUG: 1529463
    Change-Id: I95699055442fbf9da15249f5defe8a8b287010f1
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 3f0405f3ee81e05666116720c4f136403f778188
Author: Yi Wang <wangyi@storswift.com>
Date:   Tue Dec 26 01:17:04 2017 +0800

    rpc-transport/rdma: Fix coverity issues in rdma transport
    
    Issues:
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-12-25-0bc22bef/cov-errors.txt
    
    Resolved:
    [1] rdma.c:128 var_deref_op: Dereferencing null pointer "post".
    [2] rdma.c:677: Potentially overflowing expression
    [3] rdma.c:4250: freed_arg: "rpc_transport_unref" frees "peer->trans".
    [4] rdma.c:4644: var_deref_op: Dereferencing null pointer "rdma_ctx".
    [5] rdma.c:4945: cond_false: Condition "rdma_ctx != NULL", taking false branch.
    
    Change-Id: Iec38f118d645df4131739da412a6c741ebbd2f85
    BUG: 789278
    Signed-off-by: Yi Wang <wangyi@storswift.com>

commit 98bbc3c94244b6bc9fd18b698ad26e2c867ca63e
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Sat Dec 23 23:18:14 2017 -0500

    rpc: fix use after freed of clnt after rpc transport clenup
    
    If the transport object is freed in rpc_transport_unref,
    a notify of RPC_TRANSPORT_CLEANUP is push to rpc_clnt_notify,
    where the rpc_clnt(contains conn) is freed.
    
    After that, using of conn after rpc_transport_unref is use after freed.
    
    Change-Id: I5cac8a8e7ced7c1079930080a12abf02d46667d5
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit c6aad575171d4749d1ef2b5fc7c9fd7c32c1c59f
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Dec 19 22:35:53 2017 +0530

    Use RTLD_LOCAL for symbol resolution
    
    RTLD_LOCAL is the default value for symbol visibility flag of dlopen()
    in Linux and NetBSD. Using it avoids conflicts during symbol resolution.
    
    This also allows us to detect xlators that have not been explicitly
    linked with libraries that they use. This used to go unnoticed
    when RTLD_GLOBAL was being used.
    
    BUG: 1193929
    Change-Id: I50db6ea14ffdee96596060c4d6bf71cd3c432f7b
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit ee26765bdff77a4aa23efd0a8936d4306ec61c4b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Dec 25 14:34:16 2017 +0100

    tests/vagrant: add a --help option to the script
    
    Change-Id: I89913375fedb6a7617873b09039de72bf1773c68
    BUG: 1526780
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 73823181dd0ffa51761c30eefbc2f43888ffe044
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Dec 22 15:52:46 2017 +0530

    Set log path correctly when clients use UDS
    
    When a libgapi client passes a path to Unix socket file as the "host"
    parameter to glfs_set_volfile_server() and doesn't explicitly specify
    a log file, the default log file path being generated was invalid.
    
    Example:
    ERROR: failed to create logfile "/var/log/glusterfs//tmp/gd2/
    w1/run/glusterd2.socket-test-10368.log" (No such file or directory)
    
    With this fix, it is set to:
    /var/log/glusterfs/tmp-gd2-w1-run-glusterd2.socket-test-31869.log
    
    Change-Id: Ibb4b58382c72eab0d104543781e0e966ebf4c47f
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit b868d6077c14e3653fdaddcb856ab2bf6ceb9c00
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Dec 19 16:10:11 2017 +0530

    dict: support better on-wire transfer
    
    This patch brings data type awareness to dictionary,
    and also makes sure valid data is properly sent to the
    other side of the wire using XDR.
    
    Next step is to allow people to add more data types
    (for example, Bool, UUID, iatt etc), and then make
    it part of every fop signature in wire.
    
    Fixes #203
    
    Change-Id: Ie0eee2db847bea2bf7dad80dec89ce3e7c5917c1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 9a47978877a5415dbbac94b93b4b30d055349681
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Dec 25 14:40:16 2017 +0100

    rpm: Fedora 28 has renamed pyxattr
    
    Change-Id: Ifa60b394986b9c107792a7c2a4baa335d44dc6f7
    BUG: 1528975
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 85a389cfced2c299faa37b6f930c2cd0ca8c72b9
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jul 14 15:18:19 2017 +0530

    cluster/dht: Add migration checks to dht_(f)xattrop
    
    The dht_(f)xattrop implementation did not implement
    migration phase1/phase2 checks which could cause issues
    with rebalance on sharded volumes.
    This does not solve the issue where fops may reach the target
    out of order.
    
    Change-Id: I2416fc35115e60659e35b4b717fd51f20746586c
    BUG: 1471031
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit f13023862edc868d4da87609412341aecd041ed8
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Wed Nov 29 17:36:55 2017 +0800

    protocol/client: reduce lock contention
    
    Current use of a per-client mutex to protect fdctx introduces lock
    contentions when there are dozens of file operations active.
    
    Use finer grain spinlock to reduce contention, and put retrieving
    fdctx out of lock.
    
    Change-Id: Iea3e2eb481e76a5d73a582ba81529180c5b88248
    BUG: 1519598
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 0bc22bef7f3c24663aadfb3548b348aa121e3047
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Dec 22 12:02:09 2017 +0530

    performance/write-behind: fix bug while handling short writes
    
    The variabled "fulfilled" in wb_fulfill_short_write is not reset to 0
    while handling every member of the list.
    
    This has some interesting consequences:
    
    * If we break from the loop while processing last member of the list
      head->winds, req is reset to head as the list is a circular
      one. However, head is already fulfilled and can potentially be
      freed. So, we end up adding a freed request to wb_inode->todo
      list. This is the RCA for the crash tracked by the bug associated
      with this patch (Note that we saw "holder" which is freed in todo
      list).
    
    * If we break from the loop while processing any of the last but one
      member of the list head->winds, req is set to next member in the
      list, skipping the current request, even though it is not entirely
      synced. This can lead to data corruption.
    
    The fix is very simple and we've to change the code to make sure
    "fulfilled" reflects whether the current request is fulfilled or not
    and it doesn't carry history of previous requests in the list.
    
    Change-Id: Ia3d6988175a51c9e08efdb521a7b7938b01f93c8
    BUG: 1528558
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit f4734305783ce3aa10721bf2731923f6aa39252b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Dec 22 11:34:22 2017 +0530

    xlator.h: move options and other variables to the top of structure
    
    This helps external applications which wants to consume xlator_api
    to read only fields (and not functions) using dlopen() to write
    smaller structures/objects and still achieve their requirements.
    One such example is GD2 project.
    
    Updates #168
    
    Change-Id: I8737939c8c72f6572ee1514201e9f9f8e4f37b40
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 41120aa8bab4ca4496bb37b8986434be404ae255
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Wed Dec 13 17:27:42 2017 +0100

    cluster/ec: Fix possible shift overflow
    
    A coverity scan has revelaed a potential shift overflow while scanning
    the bitmap of available subvolumes. The actual overflow cannot happen,
    but I've changed to test used to control the limit to make it explicit.
    
    Change-Id: Ieb55f010bbca68a1d86a93e47822f7c709a26e83
    BUG: 789278
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 3fd961d08588bd1ec31f8cfc72201dfa1a4e85d6
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 20 15:24:11 2017 +0530

    fips/geo-rep: Replace MD5 with SHA256
    
    MD5 is not fips compliant. Hence replacing
    with SHA256.
    
    NOTE:
    The hash is used to form the ctl_path for the ssh connection.
    The length of ctl_path for ssh connection should not be > 108.
    ssh fails with ctl_path too long if it is so. But when rsync
    is piped to ssh, it is not taking > 90. rsync is failing with
    error number 12. Hence using first 32 bytes of hash. Hash
    collision doesn't matter as only one sock file is created
    per directory.
    
    Change-Id: I58aeb32a80b5422f6ac0188cf33fbecccbf08ae7
    Updates: #230
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit c96a1338fe8139d07a0aa1bc40f0843d033f0324
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Dec 6 07:59:53 2017 +0530

    cluster/ec: Change [f]getxattr to parallel-dispatch-one
    
    At the moment in EC, [f]getxattr operations wait to acquire a lock
    while other operations are in progress even when it is in the same mount with a
    lock on the file/directory. This happens because [f]getxattr operations
    follow the model where the operation is wound on 'k' of the bricks and are
    matched to make sure the data returned is same on all of them. This consistency
    check requires that no other operations are on-going while [f]getxattr
    operations are wound to the bricks. We can perform [f]getxattr in
    another way as well, where we find the good_mask from the lock that is already
    granted and wind the operation on any one of the good bricks and unwind the
    answer after adjusting size/blocks to the parent xlator. Since we are taking
    into account good_mask, the reply we get will either be before or after a
    possible on-going operation. Using this method, the operation doesn't need to
    depend on completion of on-going operations which could be taking long time (In
    case of some slow disks and writes are in progress etc). Thus we reduce the
    time to serve [f]getxattr requests.
    
    I changed [f]getxattr to dispatch-one and added extra logic in
    ec_link_has_lock_conflict() to not have any conflicts for fops with
    EC_MINIMUM_ONE as fop->minimum to achieve the effect described above.
    Modified scripts to make sure READ fop is received in EC to trigger heals.
    
    Updates gluster/glusterfs#368
    Change-Id: I3b4ebf89181c336b7b8d5471b0454f016cdaf296
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 85d321b21c0e982866fd2c83b91b71de458dd043
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Dec 17 13:08:47 2017 +0100

    tests/vagrant: configure with --enable-gnfs so tests can use NFS
    
    gNFS has been deprecated a while ago, but the ./run-tests-in-vagrant.sh
    script has not been adapted to enable it. This causes the tests to fail
    the first time a Gluster Volume is mounted over NFSv3.
    
    Change-Id: Ifeec0ca964680ff61b956a5592a76eeee8ac3b85
    BUG: 1526780
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 8564311e8bb5971823c6b32aa5c9620d80c7cabd
Author: Kamal Mohanan <kmohanan@redhat.com>
Date:   Tue Dec 12 17:17:37 2017 +0530

    cluster/ec: Add default value for the redundancy option
    
    Updates #302
    
    Change-Id: Ifccc6a64c2b2a3b3a0133e6c8042cdf61a0838ce
    Signed-off-by: Kamal Mohanan <kmohanan@redhat.com>

commit 1d32720335ffd8835c4a7b3164fe9aa9028f77a5
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Dec 19 07:21:07 2017 -0500

    rchecksum/fips: Replace MD5 usage to enable fips support
    
    rchecksum uses MD5 which is not fips compliant. Hence
    using sha256 for the same.
    
    Updates: #230
    Change-Id: I7fad016fcc2a9900395d0da919cf5ba996ec5278
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 4a06f851dcad6bdd730f3d2e12bd8f26709f27fe
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Dec 20 13:30:39 2017 +0530

    snapshot: fix several coverity issues in glusterd-snapshot.c
    
    This patch fixes issues 157, 426, 428, 431, 432, 437,439, 482 from [1].
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-12-13-e255385a/html/
    
    Change-Id: Iff9df12bd9802db29434155badb1beda045aba5b
    BUG: 789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 8ad87e4fa5803718746e0e7315e8c9f1a37952c0
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Thu Nov 2 10:11:43 2017 +0100

    cli: Fixed coverity issue in cli-cmd-system.c
    
    This patch adds a missing check of the return value of strtok_r()
    and returns an error if it's NULL.
    
    It also fixes a couple of leaks.
    
    Change-Id: Ib15d6f843516e44c3bd8790a2e3ad936e357f6d4
    BUG: 789278
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 7d81a49a0479b4b98a639b5e50ec2ea4fa8a1314
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 31 15:23:56 2017 +0530

    stripe, quiesce: volume option fixes
    
    Updates: #302
    
    Change-Id: I8f84260ba007f2afc7fe3b7c15c06069942ad6d1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 4fdcf4cccd467c9678bd23a613f43e1f1ac24c07
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Fri Dec 1 15:23:52 2017 +0530

    leases: Fix coverity issues
    
    - dead code removal
    - check return value for thread creation.
    - fix resource leak
    
    Change-Id: I58d4247bab503fa419bc83c36fc59801a1c41f5e
    BUG: 789278
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>

commit 5aca4cf569f19d235662c4fbaa04df21e5fd46c2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Dec 19 00:05:05 2017 -0500

    fips: Replace md5sum usage to enable fips support
    
    md5sum is not fips compliant. Using xxhash64 instead of
    md5sum for socket file generation in glusterd and
    changelog to enable fips support.
    
    NOTE: md5sum is 128 bit hash. xxhash used is 64 bit.
    
    Updates: #230
    Change-Id: I1bf2ea05905b9151cd29fa951f903685ab0dc84c
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 7ff0ba71d50a324b0099ea85c2a0873dcede779f
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Mon Dec 18 04:09:39 2017 -0500

    posix: fix use after freed by calling STACK_UNWIND_STRICT after error cleanup
    
    xdata is freed when calling STACK_UNWIND_STRICT, so that,
    posix_gfid_unset uses xdata after freed.
    
    Change-Id: Id0ff2da3d6d9be204e50d9fb37ba57558936c85c
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit d341f20230b9921391aff22337eaf9be82f44d88
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 11 16:14:03 2017 +0530

    feature/bitrot: remove internal xattrs from lookup cbk
    
    Problem:
    afr requests all xattrs in lookup via the list-xattr key. If bitrot is
    enabled and later disabled, or if the bitrot xattrs were present due to
    an older version of bitrot which used to create the xattrs without
    enabling the feature, the xattrs (trusted.bit-rot.version in particular)
    was not getting filtered and ended up reaching the client stack. AFR, on
    noticing different values of the xattr across bricks of the replica,
    started triggering spurious metadata heals.
    
    Fix:
    Filter all internal xattrs in bitrot xlator before unwinding lookup,
    (f)getxattr.
    
    Thanks to Kotresh for the help in RCA'ing.
    
    Change-Id: I5bc70e4b901359c3daefc67b8e4fa6ddb47f046c
    BUG: 1524365
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 42b8df4704c93b35c8b536074df87065ca8eb5c4
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Dec 13 18:26:36 2017 +0530

    snapshot: Fix several coverity issues in glusterd-snapshot-utils.c
    
    This patch fixes issues 622, 627, 630, 484, 32, 33 and 34 from [1]
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I4c7ac2b2725474d73643367b38f8bf33eaddd8da
    BUG: 789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit e65f394a6ad7a417e2d0ccb39f45fe4fe26db008
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Nov 28 13:03:30 2017 +0530

    protocol/server: add dump_metrics method
    
    As 'xlator_api' export is a requirement to add dump_metrics, use it
    
    Updates #168
    
    Change-Id: Iaba8bb9151ef35038b0ff48bb26e8399d67aa039
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 238ebd4db6b399eba221516912cab0726949a3c9
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Fri Dec 15 12:37:06 2017 +0100

    glusterd: Fix buffer overflow in glusterd_get_volopt_content
    
    The size of the description of each option in gluster has become
    greater than the hardcoded maximum size, causing a buffer overflow
    when requesting a list of all options.
    
    This patch uses dynamic memory to store all the information.
    
    Change-Id: I115cb9b55fc440434638bf468a50db055cdf271d
    BUG: 1526402
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 62ca4aec69b206723f809ce79bb501fa7bf46249
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Nov 13 12:55:06 2017 +0530

    dht: Fill first_up_subvol before use in dht_opendir
    
    Reported by: Sam McLeod
    
    Change-Id: Ic8f9b46b173796afd70aff1042834b03ac3e80b2
    BUG: 1512437
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 415e0bcc80b350fc75f325b490560f44ba419b20
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Tue Dec 12 22:31:53 2017 +0100

    all: Simplify component message id's definition
    
    This patch creates a new way of defining message id's that is easier
    and less error prone because it doesn't require so many manual changes
    each time a new component is defined or a new message created.
    
    Change-Id: I71ba8af9ac068f5add7e74f316a2478bc991c67b
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit bafe0c14f5743cb084a89595860e4ba33baf900c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Feb 21 21:35:12 2017 +0100

    logging: free the strdup'd filename and ident on gf_log_fini()
    
    Every time glfs_set_logging() is called, the strings containing the
    filename and the identity of the logfile leaks. Both should be free'd
    before a new gf_strdup() is done and in gf_log_fini().
    
    In addition to the free'ing of the filename, the code has been adapted
    to use sys_open() and fdopen() so that unneeded closes and re-opening of
    the filedescriptor are prevented.
    
    Change-Id: I63e3e757ac990a4db419206dfad141ab68dbfa06
    BUG: 1443145
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 2d0a763677b1f4e9938a1a1a2587883b2262aaf6
Author: Richard Wareing <rwareing@fb.com>
Date:   Tue Nov 10 18:04:00 2015 -0800

    storage/posix: Fix crash in posix_make_ancestryfromgfid
    
    Summary:
    - Log an OOPS and bail when *parent is null just before going into
      posix_resolve code path (to avoid crash)
    
    > Reviewed-on: https://review.gluster.org/17969
    > Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    
    Change-Id: I6140ef6fdb711748dad1c66d929aca36328bc574
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 8b8fea1a801f837a75307f4cd8e79e808760cb0b
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Dec 12 13:16:52 2017 +0530

    features/changelog: changelog threads are not cleaned properly after receive GF_EVENT_CLEANUP
    
    Problem: changelog threads are not cleaned properly after receive
             GF_EVENT_CLEANUP while brick mux is enabled
    
    Solution: change changelog notify code path to cleanup threads
              properly
    
    BUG: 1524816
    Change-Id: I007f4e14e3d557707df738faf222b78c793d5ab5
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit e255385ae4f4c8a883b3fb96baceba4b143828da
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Nov 10 20:33:20 2017 +0100

    write-behind: Allow trickling-writes to be configurable
    
    This is the undisputed/trivial part of Shreyas' patch
    he attached to https://bugzilla.redhat.com/1364740 (of
    which the current bug is a clone).
    
    We need more evaluation for the page_size and window_size
    bits before taking them on.
    
    Change-Id: Iaa0b9a69d35e522b77a52a09acef47460e8ae3e9
    BUG: 1428060
    Co-authored-by: Shreyas Siravara <sshreyas@fb.com>
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit c26cadd31dfa128c4ec6883f69d654813f351018
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jun 30 12:52:21 2017 +0530

    quick-read: Integrate quick read with upcall and increase cache time
    
    Fixes : #261
    Co-author: Subha sree Mohankumar <smohanku@redhat.com>
    Change-Id: Ie9dd94e86459123663b9b200d92940625ef68eab
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 429f2436b33793136836042ccc43ce4cfd7f89f3
Author: Sachin Prabhu <sprabhu@redhat.com>
Date:   Fri Dec 8 15:24:26 2017 +0530

    quick-read: Discard cache for fallocate, zerofill and discard ops
    
    The fallocate, zerofill and discard modify file data on the server thus
    rendering stale any cache held by the xlator on the client.
    
    BUG: 1524252
    Change-Id: I432146c6390a0cd5869420c373f598da43915f3f
    Signed-off-by: Sachin Prabhu <sprabhu@redhat.com>

commit 56e5fdae74845dfec0ff7ad0c8fee77695d36ad5
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Dec 11 14:41:57 2017 +0530

    rpc: merge ssl infra with epoll infra
    
    Patch attempts to use the epoll infra for handling SSL connections
    as well instead of the socket_poller() thread func.
    This essentially makes priv->own_thread flag redundant.
    
    SSL_connect()/SSL_accept() is now non-blocking which has done away
    with the localised poll() in ssl_do(). So, ssl_do() has been updated
    appropriately.
    
    own_thread and coincidently socket_poller() thread for SSL processing
    is now deprecated.
    
    Added a timeout to test whether seal-heal daemon is up and running
    as per Ravi's suggestion.
    
    Change-Id: If2b5d7b4fd19e321cb289e08d49a718d2161aafe
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit e016bcaf8171373cbc327faf42a6b2f2c5449b0e
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Dec 7 10:32:05 2017 +0530

    glusterd : Fix glusterd mem leaks
    
    Problem:   glusterd eats a huge amount of meory during volume set/stop/start.
    
    Solution:  At the time of compare graph topology create a graph and populate
               key values in the dictionary, after finished graph comparison we
               do destroy the new graph.At the time of construct graph we don't take
               any reference and for server xlators we do take reference in
               server_setvolume so in glusterd we do take reference after prepare
               a new graph while we do create a graph to compare graph topology.
    
    BUG: 1520245
    Change-Id: I573133d57771b7dc431a04422c5001a06b7dda9a
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit d95db5505a9cb923e61ccd23d28b45ceb07b716f
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Thu Sep 7 15:34:58 2017 -0700

    md-cache: Cache statfs calls
    
    Summary:
    - This gives md-cache to cache statfs calls
    - You can turn it on or off via 'gluster vol set groot performance.md-cache-statfs <on|off>'
    
    Change-Id: I664579e3c19fb9a6cd9d7b3a0eae061f70f4def4
    BUG: 1523295
    Signature: t1:4652632:1488581841:111cc01efe83c71f1e98d075abb10589c4574705
    Reviewed-on: https://review.gluster.org/18228
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit 430484c92ab5a6234958d1143e0bb14aeb0cd1c0
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Oct 20 12:39:29 2017 +0530

    glusterfs: Use gcc builtin ATOMIC operator to increase/decreate refcount.
    
    Problem: In glusterfs code base we call mutex_lock/unlock to take
             reference/dereference for a object.Sometime it could be
             reason for lock contention also.
    
    Solution: There is no need to use mutex to increase/decrease ref
              counter, instead of using mutex use gcc builtin ATOMIC
              operation.
    
    Test:   I have not observed yet how much performance gain after apply
            this patch specific to glusterfs but i have tested same
            with below small program(mutex and atomic both) and
            get good difference.
    
    static int numOuterLoops;
    static void *
    threadFunc(void *arg)
    {
        int j;
    
        for (j = 0; j < numOuterLoops; j++) {
                __atomic_add_fetch (&glob, 1,__ATOMIC_ACQ_REL);
        }
        return NULL;
    }
    
    int
    main(int argc, char *argv[])
    {
        int opt, s, j;
        int numThreads;
        pthread_t *thread;
        int verbose;
        int64_t n = 0;
    
        if (argc < 2 ) {
         printf(" Please provide 2 args Num of threads && Outer Loop\n");
         exit (-1);
        }
        numThreads = atoi(argv[1]);
        numOuterLoops = atoi (argv[2]);
    
        if (1) {
            printf("\tthreads: %d; outer loops: %d;\n",
                    numThreads, numOuterLoops);
        }
    
        thread = calloc(numThreads, sizeof(pthread_t));
        if (thread == NULL) {
            printf ("calloc error so exit\n");
            exit (-1);
        }
    
        __atomic_store (&glob, &n, __ATOMIC_RELEASE);
        for (j = 0; j < numThreads; j++) {
            s = pthread_create(&thread[j], NULL, threadFunc, NULL);
            if (s != 0) {
                printf ("pthread_create failed so exit\n");
                exit (-1);
            }
        }
    
        for (j = 0; j < numThreads; j++) {
            s = pthread_join(thread[j], NULL);
            if (s != 0) {
                printf ("pthread_join failed so exit\n");
                exit (-1);
            }
        }
        printf("glob value is %ld\n",__atomic_load_n (&glob,__ATOMIC_RELAXED));
    
        exit(0);
    }
    
       time ./thr_count 800 800000
       threads: 800; outer loops: 800000;
       glob value is 640000000
    
    real	1m10.288s
    user	0m57.269s
    sys	3m31.565s
    
    time ./thr_count_atomic 800 800000
         threads: 800; outer loops: 800000;
    glob value is 640000000
    
    real	0m20.313s
    user	1m20.558s
    sys	0m0.028
    
    Change-Id: Ie5030a52ea264875e002e108dd4b207b15ab7cc7
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 8483ed87165c1695b513e223549d33d2d63891d9
Author: Yi Wang <wangyi@storswift.com>
Date:   Wed Dec 6 12:51:49 2017 +0800

    rpc-transport/rdma: Add a mutex for the list of RDMA Memory Region(MR) access
    
    Problem: gf_rdma_device_t->all_mr is a __gf_rdma_arena_mr(includes MR content)
    	 kind of list in the rdma rpc-transport. The rdma rpc-transport will
    	 add/delete items to the list when MRs register, deregister, and free.
    	 Because gf_rdma_device_t->all_mr is used by different threads
    	 and it is not mutex protected, rdma transport maybe access obsolete
    	 items in it.
    
    Solution: Add a mutex protection for the gf_rdma_device_t->all_mr.
    
    Change-Id: I2b7de0f7aa516b90bb6f3c6aae3aadd23b243900
    BUG: 1522651
    Signed-off-by: Yi Wang <wangyi@storswift.com>

commit f9b6174a7f5eb6475ca9780b062bfb3ff1132b2d
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Mon Apr 10 12:36:21 2017 -0700

    posix: Add option to disable nftw() based deletes when purging the landfill directory
    
    Summary:
    - We may have found an issue where certain directories were being moved into .landfill and then being quickly purged via nftw().
    - We would like to have an emergency option to disable these purges.
    
    > Reviewed-on: https://review.gluster.org/18253
    > Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    
    Fixes #371
    
    Change-Id: I90b54c535930c1ca2925a928728199b6b80eadd9
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit b59e62e27cc59fa59d0f89aae2ddf115c939aa71
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Dec 7 04:46:08 2017 -0500

    geo-rep: Cleanup stale unprocessed xsync changelogs
    
    Fixes: #376
    
    Change-Id: Ib92920c716c7d27e1eeb4bc4ebaf3efb48e0694d
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit c7a3e0ba9fa68503917e694e2595ee4e97d4e608
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Mar 8 14:45:15 2017 +0530

    cluster/dht: fix memory leaks in rebalance
    
    From code reading it was found that in gf_defrag_process_dir, GF_FREE
    was called directly on dir_dfmeta->equeue leading to leaks of memory for
    list of entries read from all the local subvols in case of a failure.
    
    This patch frees the entries read from all the local subvols.
    
    Change-Id: If5e8f557372a8fc2af86628b401e8de1b54986a1
    BUG: 1430305
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 70b6be35dd299b47ce53b0de18386e5a458eb96a
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Sep 28 19:26:37 2017 +0530

    perf/open-behind: update options for gd2
    
    Updates: #302
    
    Change-Id: I12e5bc6d9e1fcd285299818a7f7e8f1622deefcb
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 6021331f4095813614d184f67fc6a0c08b8e8837
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Aug 31 15:07:10 2017 +0530

    trash/selinux : update volume option table in xlator
    
    Add new options defined by https://review.gluster.org/18059 to trash and selinux
    
    Updates #302
    
    Change-Id: I31064f26d2b244a2923baa4bb948a6e8ab7b0d1a
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>

commit aeff5def7e11de418d55f996926cbd5818c0494d
Author: Richard Wareing <rwareing@fb.com>
Date:   Wed Apr 6 17:06:43 2016 -0700

    debug/io-stats: Adding stat for weighted & unweighted average latency
    
    Summary:
    - Our current approach to measuring "average fop latency" is badly
      flawed in that it doesn't weight the FOPs correctly according to how
      many occurred in the time interval.  This makes Statisticians very
      sad.  This patch adds an internally computed weighted average
      latency which will be far more efficient to display via ODS, as well
      as having the benefit of not being complete nonsense.
    
    Reviewers: kvigor, dph, sshreyas
    
    Reviewed By: sshreyas
    
    Change-Id: Ie3618f279b545610b7ed1a8482243fcc8dc53217
    BUG: 1523353
    Reviewed-on: https://review.gluster.org/18192
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Signed-off-by: Ana M. Neri <amnerip@fb.com>

commit 52915ee818e8a6d0f052d8a2deeadd8ff7bd85dc
Author: Ankit raj <anraj@redhat.com>
Date:   Fri Apr 21 11:50:35 2017 +0530

    dht: Send an event when disks get full
    
    Send an event if DHT determines that a subvol is getting
    full or running out of inodes.
    
    Change-Id: Ie026f4ee1832b5df1e80b16cb949b2cc31a25d6f
    Bug: 1440659
    Signed-off-by: Ankit raj <anraj@redhat.com>
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 1926cada4a7acf48aa7cbf5ef8bb8942ae10b522
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Thu Dec 7 08:00:16 2017 -0800

    nfs: Reference count export items
    
    Export items are used in the auth cache and need to be reference
    counted to avoid use-after free bugs.
    
    Change-Id: I5cdcdc1cc6abad26c7077d66a14f263da07678ac
    BUG: 1522847
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit 742a4eed244833761697646044f20675d1411292
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Wed Dec 6 07:41:19 2017 -0800

    nfs: Enable multi-core epoll support in gNFSd
    
    Change-Id: Ie8a7b1ba04b0e83f5ec7a09f9d181fe59be479ca
    BUG: 1522847
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit 5a29779aceec59069511cec7eff9b314e819eacc
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Thu Sep 7 16:36:29 2017 -0700

    storage/posix: Add limit to number of hard links
    
    Summary:
    Too may hard links blow up btrfs by exceeding max xattr size (recordign
    pgfid for each hardlink). Add a limit to prevent this explosion.
    
    > Reviewed-on: https://review.gluster.org/18232
    > Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    Fixes gluster/glusterfs#370
    Signed-off-by: ShyamsundarR <srangana@redhat.com>
    Change-Id: I614a247834fb8f2b2743c0c67d11cefafff0dbaa

commit 97a97bab57873083d5b49f636fd0ccbe94a310e3
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Wed Apr 5 13:23:13 2017 -0700

    glusterd: Allow volume stop to succeed if certain processes are already dead
    
    Summary:
    - Sometimes a the process that glusterd is trying to kill is already dead.
    - In that case, if it can't find the pid, it should just continue on and not fail the entire operation.
    
    Change-Id: Ic96952a8d31927446f648830ede6ccd82512663f
    BUG: 1522968
    Reviewed-on: https://review.gluster.org/18234
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Signed-off-by: Ana M. Neri <amnerip@fb.com>

commit faa06328fe58ca85cc3c1c849d293df81efdb9c4
Author: Richard Wareing <rwareing@fb.com>
Date:   Wed Jul 1 18:44:07 2015 -0700

    Fix management client deadlock
    
    Ping notify is a NOOP for management daemons
    
    Reviewers: sshreyas
    
    Reviewed By: sshreyas
    
    FB-commit-id: ec30b68
    
    Change-Id: I8e121aaaa3ad268e5df057e03aa4b37a403c9ea0
    BUG: 1522968
    Signed-off-by: Kevin Vigor <kvigor@fb.com>
    Reviewed-on: https://review.gluster.org/16858
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>

commit d9e9e76188b839447de1d7bdf415a820f13b971b
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Nov 30 18:39:58 2017 +0530

    features/read-only: Coverity fixes
    
    Warning            File          Function
    NEGATIVE_RETURNS   worm.c        worm_writev
    RESOURCE_LEAK      worm.c        init
    		   read-only.c   init
    
    Note: COPY_PASTE_ERROR in worm_setattr & worm_fsetattr are false alarms.
    
    Change-Id: Iba1b0c18137a8797d7d04502acc87f0b307e1a1c
    BUG: 789278
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 47d01546a1826dc14a8331ea8700015f1cfdc4db
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Dec 6 14:23:06 2017 +0530

    core/memacct: save allocs in mem_acct_rec list
    
    With configure --enable-debug, add all object allocations
    to a list in the corresponding mem_acct_rec. This
    allows us to see all objects of a particular type
    and allows for additional debugging in case of memory
    leaks.
    
    This is not compiled in by default and must be explicitly
    enabled. It is intended to be used by developers.
    
    Change-Id: I7cf2dbeadecf994423d7e7591e85f18d2575cce8
    BUG: 1522662
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 36ce4c614a3391043a3417aa061d0aa16e60b2d3
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Dec 6 18:05:24 2017 +0530

    glusterd: Free up svc->conn on volume delete
    
    Daemons like snapd, tierd and gfproxyd are maintained on per volume
    basis and on a volume delete we should destroy the rpc connection
    established for them.
    
    Change-Id: Id1440e39da07b990fdb9b207df18da04b1ca8014
    BUG: 1522775
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 47d7e7441fc2887fd63705c1309e5636df2bdcf4
Author: Richard Wareing <rwareing@fb.com>
Date:   Fri Oct 17 18:35:56 2014 -0700

    Fixes gNFSd gf_update_latency crashes
    
    Summary:
    - Per title, does a bounds check on the frame->op and bails from the
      function if it's invalid preventing the crash
    
    Test Plan: Prove tests
    
    Reviewers: dph, jackl
    
    Reviewed By: jackl
    
    FB-commit-id: e67cc15
    
    Change-Id: If1a5a9c0630573d4a6615050a9114ccf532551c7
    BUG: 1522847
    Signed-off-by: Kevin Vigor <kvigor@fb.com>
    Reviewed-on: https://review.gluster.org/16847
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>

commit f6aa6141d035f488cd6275ac8fc447face231107
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Wed Dec 6 09:20:41 2017 -0800

    rpc: Fix format warnings when using IPV6_DEFAULT
    
    Change-Id: I22e622212f30defe6f2af1a67d7b48a88d37a097
    BUG: 1520974
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit b5184d6e75b884f98c8aea37d1604f0a244b31cc
Author: Max Rijevski <moox@fb.com>
Date:   Thu Apr 7 13:11:20 2016 -0700

    performance/io-threads: Reduce the number of timing calls in iot_worker
    
    Summary:
    - Reduce the amount of unnecessary timing calls
    in iot_worker servicing.
    - The current logic is unnecessarily accurate and
    hurts performance for many small FOPS.
    
    Change-Id: I6db4f1ad9a48d9d474bb251a2204969061021954
    BUG: 1522950
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-on: http://review.gluster.org/16081
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kevin Vigor <kvigor@fb.com>

commit 4eb49de567c5e9f4559bfb05a6174ac8020b03ad
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Tue Dec 5 12:54:04 2017 +0800

    gfapi: fix issue when glfs_set_logging is called concurrently
    
    glfs_set_logging changes THIS->ctx without lock, during initialization
    THIS refers to global_xlator. Concurrently changing it could result in
    global_xlator.ctx being some fs->ctx. After that fs->ctx is destroyed,
    global_xlator.ctx refers to an invalid pointer and that causes crash in
    sbusequent access.
    
    Change-Id: I6682173811799bafd525d9ab371874f3803baa0e
    BUG: 1521213
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 28202631fecbc3b20a55cfc5fa339663db37e955
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Tue Dec 5 12:45:46 2017 +0800

    libglusterfs: specify ctx in gf_log_set_loglevel
    
    specify ctx in gf_log_set_loglevel, instead of getting it from a thread
    specific variable.
    
    Change-Id: I498f826e8e32231235a6b0005026a27c327727fd
    BUG: 1521213
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit c502ca166473f4f0e027f3475924d8dc4e486bd3
Author: ShyamsundarR <srangana@redhat.com>
Date:   Wed Dec 6 11:32:00 2017 -0500

    dht/crypt/tier: Fix use of booleans as integers
    
    BUG: 1520974
    Change-Id: I19ea40c888e88a7a4ac271168ed1820c2075be93
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 820a91a219bbeb65f84d963db3fd79e261f194ad
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Tue May 24 10:51:23 2016 -0700

    nfs: Check if FQDN is authorized before unmounting clients
    
    Summary:
    - We have a thread that checks if connected clients are "still" authorized for a mount.
    - This thread is currently only checking the IP (regression from the 3.4 -> 3.6 rebase, perhaps).
    - This diff adds code toe check the IP *and* the FQDN before unmounting the client.
    
    Test Plan: Tested on devserver, auth prove tests.
    
    Reviewers: rwareing, kvigor
    
    Reviewed By: kvigor
    
    Change-Id: I441a4436d8df064d2f09a2539acb780ab53943f6
    BUG: 1522847
    Reviewed-on: https://review.gluster.org/18193
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Signed-off-by: Siri Uppalapati <siri@fb.com>

commit 7f2e67d40d1006e88fda86eb04699c15db3440ee
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 11 15:08:49 2017 +0530

    metrics: provide options to dump metrics from xlators
    
    * Introduce xlator methods to allow dumping of metrics
    * Separate options to get the metrics dumped in a path
    
    Updates #168
    
    Change-Id: I7df80df33b71d6f449f03c2332665b4a45f6ddf2
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 349a55c5ef5c3a5aaee37b547b545df94fc10faf
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Wed Dec 6 09:42:27 2017 -0800

    xdr: Fix build errors due to missing xdr symbol when building against TIRPC
    
    Change-Id: Ic52045f5dd19e551612242450b8982f42ff327e9
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit 3fa4510fdb5d6858b788f64c069299b133edef0e
Author: Nigel Babu <nigelb@redhat.com>
Date:   Wed Dec 6 20:16:09 2017 +0530

    Revert "run-tests.sh: provide retry count option"
    
    This change was actually causing failures to be reported as passing.
    
    This reverts commit 4e798113229eab68e9e02364bb094a4ab8274c65.
    
    Change-Id: I02b06e7f2af03419d922de8ad7e6948ae8cb8d06

commit e5e0d223ada35d6bdb1790054fcbf34273b7949c
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Tue Dec 5 07:43:40 2017 -0800

    features/quota: Fix brick crash in quota unlink callback
    
    Change-Id: Iad16d7b2102376380eb0f6918111249af370aaeb
    BUG: 1521014
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit c2e4990a204aeaec3105f97bdfa7b48a571fa1fa
Author: Kevin Vigor <kvigor@fb.com>
Date:   Fri Jan 6 13:19:35 2017 -0800

    tests: Fix prove test bug-1292020.t
    
    dd is doing a statfs and failing with ENOSPC instead of writign and
    getting EDQUOTA. Make either error a success in this test.
    
    > Signed-off-by: Kevin Vigor <kvigor@fb.com>
    > Reviewed-on: http://review.gluster.org/16352
    BUG: 1521116
    Signed-off-by: ShyamsundarR <srangana@redhat.com>
    Change-Id: I9f580d9e4a4dd293df55a1d954f86a9862fcae7b

commit efad78260379f0ca836e8a2327b97dd620acd098
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Aug 22 13:44:52 2017 +0530

    rio/everywhere: add icreate/namelink fop
    
    icreate creates inode, while namelink links the basename to it's
    parent gfid.
    
    For now mkdir is the primary user of these fops. Better distribution is
    acheived by creating the inode on ,(say) mds1 and linking the basename to it's
    parent gfid on mds2. The inode serves readdirp, stat etc.
    
    More details about the fops are present at:
    https://review.gluster.org/#/c/13395/3/design/DHT2/DHT2_Icreate_Namelink_Notes.md
    
    This backport of three patches from experimental branch.
    1- https://review.gluster.org/#/c/18085/
    2- https://review.gluster.org/#/c/18086/
    3- https://review.gluster.org/#/c/18094/
    
    Updates gluster/glusterfs#243
    Change-Id: I1bd3d5a441a3cfab1acfeb52f15c6c867d362592
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit ee20190a3a6e36b97c4914e0fa486017e72b0375
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Tue Dec 5 06:51:24 2017 -0800

    cluster/dht: Fix build error due to switch statement on a boolean
    
    Change-Id: Idf672b435e389baada732f609398404479306909
    BUG: 1520974

commit 69da9aa3c784ff3d28671d097395e3f6c7542a65
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Tue Dec 5 07:53:25 2017 -0800

    rfc.sh: Update rfc.sh to use a custom origin via an env variable
    
    Change-Id: I9efc6a7fbcbefad0c476cf69096b659485ed8906
    BUG: 1521013
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit 1889e2b42917a996cef6958ee3880344028d9d9a
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Dec 5 11:03:42 2017 +0530

    cluster/ec: Fix bugs in stripe-cache feature
    
    1 - This patch fixes a bug in ec_update_stripe()
    that prevented some stripes to be updated after a write.
    
    2 - This patch also include code modification for the
    case in which a file does not exist and we write on
    unaligned offset and user size, the last stripe on
    which "end" will fall should also be cached.
    
    Change-Id: I069cb4be1c8d59c206e3b35a6991e1fbdbc9b474
    BUG: 1520758
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 4e798113229eab68e9e02364bb094a4ab8274c65
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Dec 1 08:33:50 2017 -0500

    run-tests.sh: provide retry count option
    
    and default it to 5.
    
    With this change, if any test fails due to timing issues (because of
    slower/faster VM etc), there is a retry logic which gets triggered.
    Many times, if a test successfully fails more than 5 times, there may
    be a genuine issue with it, one should take a serious look at the
    failing test.
    
    Change-Id: Ia88e3293fd2724b0f9f09d8bc026560792fc1578
    BUG: 1517961
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit dc1258bfe46d30059119a3294285a114ec2bcd36
Author: Poornima G <pgurusid@redhat.com>
Date:   Sat Nov 18 15:19:13 2017 +0530

    libglusterfs:  Add put fop
    
    Problem: It had been a longtime request to implement put fop
    in gluster. put fop in gluster may not have the exact sementics
    of HTTP PUT, but can be easily extended to do so. The subsequent
    patches, will contain more semantics on the put fop and its
    guarentees.
    
    Why compound fop framework is not used for put?
    Compound fop framework currently doesn't allow compounding of
    entry fop and inode fops, i.e. fops on multiple inodes cannot be
    combined in compound fop.
    
    Updates #353
    Change-Id: Idb7891b3e056d46d570bb7e31bad1b6a28656ada
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 8a0b115b20cfa2dd3c5a9e22a8244c9c2f03e17b
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Nov 28 18:51:00 2017 -0500

    posix: Reorganize posix xlator to prepare for reuse with rio
    
    1. Split out entry and inode/fd based FOPs into
    separate files from posix.c
    2. Split out common routines (init, fini, reconf,
    and such) into its own file, from posix.c
    3. Retain just the method assignments in posix.c
    (such that posix2 for RIO can assign its own methods in
    the future for entry operations and such)
    4. Based on the split in (1) and (2) split out
    posix-handle.h into 2 files, such that macros that are
    needed for inode ops are in one and rest are in the other
    
    If the split is done as above, posix2 can compile with
    its own entry ops, and hence not compile, the entry ops
    as split in (1) above.
    
    The split described in (4) can again help posix2 to
    define its own macros to make entry and inode handles,
    thus not impact existing POSIX xlator code.
    
    Noted problems
    - There are path references in certain cases where
    quota is used (in the xattr FOPs), and thus will fail
    on reuse in posix2, this needs to be handled when we
    get there.
    - posix_init does set root GFID on the brick root,
    and this is incorrect for posix2, again will need
    handling later when posix2 evolves based on this
    code (other init checks seem fine on current inspection)
    
    Merge of experimental branch patches with the following
    gerrit change-IDs
    > Change-Id: I965ce6dffe70a62c697f790f3438559520e0af20
    > Change-Id: I089a4d9cf470c2f9c121611e8ef18dea92b2be70
    > Change-Id: I2cec103f6ba8f3084443f3066bcc70b2f5ecb49a
    
    Fixes gluster/glusterfs#327
    
    Change-Id: I0ccfa78559a7c5a68f5e861e144cf856f5c9e19c
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 09cb795587772b60ba102f4369ab3f4501cdc01a
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Thu Nov 2 15:09:37 2017 +0530

    storage/posix : options to override umask
    
    Options "create-mask" and "create-directory-mask" are added to
    remove the mode bits set on a file or directory when its created.
    Default value of these options is 0777.
    
    Options "force-create-mode" and "force-create-directory" sets
    the default permission for a file or directory irrespective of
    the clients umask.
    Default value of these options is 0000.
    
    Command to set option:
    volume set <volume name> storage.<option-name> <value>
    
    The valid value range from 0000 to 0777.
    
    Updates #301
    
    Change-Id: Ia33d13f2117202ca55a056c747ccc3674eb8bae1
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 59d1cc720f52357f7a6f20bb630febc6a622c99c
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Sep 19 09:44:55 2017 +0530

    cluster/dht: populate inode in dentry for single subvolume dht
    
    ... in readdirp response if dentry points to a directory inode. This
    is a special case where the entire layout is stored in one single
    subvolume and hence no need for lookup to construct the layout
    
    Change-Id: I44fd951e2393ec9dac2af120469be47081a32185
    BUG: 1492625
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit e785faead91f74dce7c832848f2e8f3f43bd0be5
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Sep 18 16:01:34 2017 +0530

    cluster/dht: don't overfill the buffer in readdir(p)
    
    Superflous dentries that cannot be fit in the buffer size provided by
    kernel are thrown away by fuse-bridge. This means,
    
    * the next readdir(p) seen by readdir-ahead would have an offset of a
    dentry returned in a previous readdir(p) response. When readdir-ahead
    detects non-monotonic offset it turns itself off which can result in
    poor readdir performance.
    
    * readdirp can be cpu-intensive on brick and there is no point to read
     all those dentries just to be thrown away by fuse-bridge.
    
    So, the best strategy would be to fill the buffer optimally - neither
    overfill nor underfill.
    
    Change-Id: Idb3d85dd4c08fdc4526b2df801d49e69e439ba84
    BUG: 1492625
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 5eea1756016c55e4138d582e34d0069744772f72
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Mon Nov 20 14:06:56 2017 +0530

    glusterd:buffer_size_warning coverity fixes
    
    Fixes Issues :15,17,18,19,24,38
    
    Change-Id: Ib09d319308e4ef7dfbdd5e49e16064d4f55a54f9
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 185917c7a621ce0971e883b35221895ef235ca18
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Nov 28 11:26:10 2017 +0530

    posix: Convert posix_fs_health_check asynchrnously to save timestamp
    
    Problem: Sometime posix_fs_health_check thread is blocked on write/read
             call while backend device deleted abruptly.
    
    Solution: To resolve it convert code to update timestamp asynchrnously.
    
    BUG: 1501132
    Change-Id: Id68ea6a572bf68fbf437e1d9be5221b63d47ff9c
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 48e3ae7482a7c70dc130dc7f8198636a87649d54
Author: hari gowtham <hgowtham@redhat.com>
Date:   Fri Nov 24 11:47:01 2017 +0530

    Tier: Stop tierd for detach start
    
    Problem: tierd was stopped only after detach commit
    This makes the detach take a longer time. The detach
    demotes the files to the cold brick and if the promotion
    frequency is hit, then the tierd starts to promote files to
    hot tier again.
    
    Fix: stop tierd after detach start so the files get
    demoted faster.
    
    Note: the is_tier_enabled was not maintained properly.
    That has been fixed too. some code clean up has been done.
    
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    
    Change-Id: I532f7410cea04fbb960105483810ea3560ca149b
    BUG: 1446381

commit 5529659dec7607bf9b94ea2195672ae553458785
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Nov 29 18:24:23 2017 +0530

    tests: Fix a broken test case
    
    Issue: When using statedump command to take statedump of the
    gfapi process, we specify the following things:
    
    $gluster volume statedump <volname> client <host>:<pid>
       pid: Pid of the gfapi application
       host: This should be the IP/hostname as seen by the glusterd,
             the gfapi application is connected to.
    
    In this test case, if gfapi application is running locally,
    and is connected to $H1 glusterd, the <host> need not be $H1.
    <host> could be localhost, 127.0.0.1, 127.1.1.1 etc. based on
    the configuration of the system. Hence use netstat to find the
    right <host> value.
    
    Change-Id: I6efb9d1ccaf9c6841a9ab7c9ebfecafc03c0bc5e
    BUG: 1517961
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 757d4a5a5fc0a3c2f6c450d228525b7a87fe3172
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Nov 30 19:09:42 2017 +0530

    dht: coverity fix in dht-rebalance.c
    
    Fixed UNUSED_VALUE warning in dht_migrate_file.
    Issue ID: 526
    From: http://download.gluster.org/pub/gluster/glusterfs/
    static-analysis/master/glusterfs-coverity/2017-11-30-eb013e4c
    
    Change-Id: I37395e8ce7088742501424fcce918f0ee8ab4f3d
    BUG: 789278
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit aba2b775bd4bd5528fcefcceb02fd70d858ec2d5
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Wed Oct 25 11:42:37 2017 +0800

    libglusterfs: use rwlock for fdtable
    
    To resolve a fd from client requests, need to take a mutex lock for the
    fdtable to do the lookup. When a client is busy doing read and write,
    the mutex lock could introduce contention. Therefore, use rwlock instead
    of mutex to reduce the contention.
    
    Change-Id: Ic833aed738a178a7ea1abafed7eb13814989d28c
    BUG: 1518582
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 7ae126dcd967a953a64102a96de8e0678331e548
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Nov 27 15:07:05 2017 +0530

    heal: Fix coverity scan dead-code report
    
    Got following kind of scan issues:
    
    *** CID 1382469:    (DEADCODE)
    /heal/src/glfs-heal.c: 1749 in main()
    1744                             break;
    1745             case GF_SHD_OP_SBRAIN_HEAL_FROM_BRICK:
    1746                     ret = glfsh_heal_from_brick (fs, top_subvol, &rootloc,
    1747                                                  hostname, path, file);
    1748                     break;
    >>>     CID 1382469:    (DEADCODE)
    >>>     Execution cannot reach this statement: "case GF_SHD_OP_INVALID:".
    
    Change-Id: I184da785893cb3e281b21f2d4fcdd2e5452102e6
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit eb013e4c180014238c95d58f67246ff19b40c437
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Nov 29 11:23:40 2017 +0530

    tests: fix for bug-1260185-donot-allow-detach-commit-unnecessarily.t failure
    
    problem: detach commit was issues before detach start was completed.
    
    fix: wait for detach start to finish and then detach commit.
    
    Change-Id: I639962be6de6dbd1512f0a5617050d1e6872eac8
    BUG: 1517961
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit 5b4b25c697f93d3dfe352013a442f2ec73fd3b8b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Nov 28 14:44:46 2017 +0530

    xlator: provide a xlator_api_t structure to include all exported options
    
    each translator from now on can have just 1 symbol exported called
    'xlator_api', which has all the required fields in it.
    
    Updates: #164
    
    Change-Id: I48d54f5ec59fee842b1d55877e3ac5e9ec9b6bdd
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 3460b8cfc550f272bdae588e8929b75b105ab06b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Nov 27 01:28:38 2017 -0500

    geo-rep: Fix access-mount geo-rep config
    
    Fix access-mount and slave-access-mount
    configs.
    
    Change-Id: Ib586677755e76a51b9f20093e441b72789b4fecc
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    BUG: 1517633

commit 98cf45970ec3c147d65c98da01727c6b4e0dce4f
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Nov 29 12:03:48 2017 +0530

    posix: Change GD_OP_VERSION to 3_13_0 from 3_12_0 for storage.reserve
    
    Problem: Change GD_OP_VERSION to 3_13_0 from 3_12_0 for option storage.reserve
    
    Solution: Actually feature was merged in 3.13.0 branch so GD_OP_VERSION needs
             to change from 3_12_0 to 3_13_0
    
    BUG: 1518508
    Change-Id: I5856ab3447b465879ec068cecb0933b91dd697f9
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 8d31f537a896ff6d70808d90a9b98a1fdb82f42a
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Nov 29 15:01:23 2017 +0530

    cluster/ec: Modify OP_VERSION to 4.0.0 for stripe cache option
    
    Change-Id: I991eaeb979497a1bf056b5871284274f959f36f2
    BUG: 1471753
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit bd63d164eabba59596f991c2aa7b66b43ed732a8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Nov 29 13:17:37 2017 +0530

    glusterd: revert coverity fix for freeing key_dup
    
    key_dup can't be freed here as the same is referenced at the
    gd_mgmt_v3_unlock_timer_cbk.
    
    Change-Id: I85667f98c82d1acebcce59137dfc0dd1ca93b4eb
    BUG: 789278
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit f74112b1298ed9f227e1a0784b1eabbfc9ab4d31
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Nov 29 12:03:48 2017 +0530

    posix: Change GD_OP_VERSION to 3_13_0 from 3_12_0 for storage.reserve
    
    Problem: Change GD_OP_VERSION to 3_13_0 from 3_12_0 for option storage.reserve
    
    Solution: Actually feature was merged in 3.13.0 branch so GD_OP_VERSION needs
             to change from 3_12_0 to 3_13_0
    
    BUG: 1518508
    Change-Id: I3890a3e921847d896465ce456fee003efaeb0c61
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 61e738db03b4592c36891ac0f17b321eb7692141
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Nov 3 09:55:53 2017 +0530

    posix: Fix coverity issues in several posix functions
    
    Fixes issues 528, 763, 778, 792, 793, 86, 28, 29, 30, 39, 42, 769, 783,
                 794, 795 from the report at [1].
    
    [1]: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Note: Apart from coverity resolve other issues
          in posix_get(f)xattr more cleaner way.
    
    BUG: 789278
    Change-Id: If0737492198481ad7a8d75a3801c862fd61b8c6e
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 9af6fb54d81b992b9ebaf5dd56aed34fd7dba032
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Nov 27 09:50:32 2017 +0530

    cluster-syncop: Address comments in 3ad68df725ac32f83b5ea7c0976e2327e7037c8c
    
    Change-Id: I325f718c6c440076c9d9dcd5ad1a0c6bde5393b1
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 01aa87e20490769f1a45f724b6985f6a90ca2b13
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Oct 10 18:52:57 2017 +0530

    features/bitrot: Add default value for stub export option
    
    Updates #302
    
    Change-Id: Ife78e15ad6300f09a820cbc25f43f214dc5e611d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e05d8eb96b9f06c39660caa9a613d6064f46f3f2
Author: Nigel Babu <nigelb@redhat.com>
Date:   Wed Nov 29 12:45:15 2017 +0530

    tests: Renable basic/afr/split-brain-favorite-child-policy.t
    
    This test was failing due to an infra issue. The infra issue is now
    fixed.
    
    BUG: 1517961
    Change-Id: I09dfab9c0a3ebe73c738222e6269d9e35c85eddb
    Signed-off-by: Nigel Babu <nigelb@redhat.com>

commit 8c4aa6a51ff441574f1620fc96dea5737e4e9878
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Oct 10 18:58:35 2017 +0530

    features/changelog: Add default values for options
    
    Updates #302
    
    Change-Id: I806e42b658114b242b787491400332299dbdbf77
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit cff6cf5e01a4c643e63dae5b45b2f4eb8239664f
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Aug 31 15:49:51 2017 +0530

    quick-read: redefine options
    
    Updates: #302
    
    Change-Id: If25996a080d69e9ac819ca771a5774ccdab6e1ce
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 2155f9926a749486f7e0a64bc6687886efa8171e
Author: James Le Cuirot <chewi@gentoo.org>
Date:   Mon Nov 20 20:56:34 2017 +0000

    build: Use pkg-config to get libtirpc flags
    
    This benefits cross-compiling and other exotic setups.
    
    Change-Id: Id9f168728d96264ccab23d2e618fa2b4003455a3
    Signed-off-by: James Le Cuirot <chewi@gentoo.org>

commit 718e2f2c6cf1f5e8fe8b299f686153495e7e784c
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Nov 7 22:21:22 2017 -0500

    gfapi: avoid nameless lookup when inode_find success
    
    Ganesha calls pub_glfs_h_create_from_handle always with stat != NULL,
    for inode_find success, a nameless lookup seems unnecessary.
    
    Change-Id: I1242deefe8ff4af15a98cc3af7824233e24d62ad
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>

commit 858fae39936e5aee5ea4e3816a10ba310d04cf61
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Nov 27 23:56:50 2017 +0530

    tests: mark currently failing regression tests as known issues
    
    Change-Id: If6c36dc6c395730dfb17b5b4df6f24629d904926
    BUG: 1517961
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 04fb94c99160ae1c6dea02624fefd47eb48da810
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Aug 14 10:15:45 2017 +0530

    rpc: Eliminate conn->lock contention by using more granular locks
    
    rpc_clnt_submit() acquires conn->lock  before call to
    rpc_transport_submit_request() and subsequent queuing of frame into
    saved_frames list. However, as part of handling RPC_TRANSPORT_MSG_RECEIVED
    and RPC_TRANSPORT_MSG_SENT notifications in rpc_clnt_notify(), conn->lock
    is again used to atomically update conn->last_received and conn->last_sent
    event timestamps.
    
    So when conn->lock is acquired as part of submitting a request,
    a parallel POLLIN notification gets blocked at rpc layer until the request
    submission completes and the lock is released.
    
    To get around this, this patch call clock_gettime (instead to call gettimeofday)
    to update event timestamps in conn->last_received and conn->last_sent and to
    call clock_gettime don't need to call mutex_lock because it (clock_gettime)
    is thread safe call.
    
    Note: Run fio on vm after apply the patch, iops is improved after apply
          the patch.
    
    Change-Id: I347b5031d61c426b276bc5e07136a7172645d763
    BUG: 1467614
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 0805771ad3e676224760a8bbfe7a265d0e132a7e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Nov 28 11:49:12 2017 +0530

    tests: fix bug-1432542-mpx-restart-crash.t spurious failure
    
    Change-Id: Ied1215bfec0ccf2ec8ee55a0aaf618517b67bd55
    BUG: 1517961
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit bdd7ad3787beebcf55340f7ebb495d42002516d2
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Wed Nov 22 15:12:26 2017 +0530

    cluster/ec: EC DISCARD doesn't punch hole properly
    
    Problem:
    DISCARD operation on EC volume was punching hole of lesser
    size than the specified size in some cases.
    
    Solution:
    EC was not handling punch hole for tail part in some cases.
    Updated the code to handle it appropriately.
    
    BUG: 1516206
    Change-Id: If3e69e417c3e5034afee04e78f5f78855e65f932
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit c471636264040d84e0f21f5a26f61746aa65975a
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Wed Nov 22 11:10:32 2017 +0100

    cluster/ec: Prevent self-heal to work after PARENT_DOWN
    
    When the volume is being stopped, PARENT_DOWN event is received.
    This instructs EC to wait until all pending operations are completed
    before declaring itself down. However heal operations are ignored
    and allowed to continue even after having said it was down.
    
    This may cause unexpected results and crashes.
    
    To solve this, heal operations are considered exactly equal as any
    other operation and EC won't propagate PARENT_DOWN until all
    operations, including healing, are complete. To avoid big delays
    if this happens in the middle of a big heal, a check has been
    added to quit current heal if shutdown is detected.
    
    Change-Id: I26645e236ebd115eb22c7ad4972461111a2d2034
    BUG: 1515266
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit eba88aed7d2813bfccd1455d4148c4f25d9d0e48
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Oct 10 15:55:38 2017 +0530

    protocol/client: Update xlator options table
    
    Updates #302
    
    Change-Id: Ia78e5d8f7b9ee6410965296808ad316c3cfb1d61
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 2708e492d7bfb95433939fadfb4a8c33640ebc9d
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Nov 27 00:18:03 2017 +0530

    cli: commands are missing in man page
    
    adding missed commands to gluster manual page.
    
    Change-Id: I2e5eb1b3929241275ee7a046c5e3d45a5aa5c4a2
    BUG: 1517554
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 0fa39220603233dc0030eeedfc7f05947c35da7c
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Mon Nov 13 13:47:53 2017 +0530

    snapshot : snapshot creation failed after brick reset/replace
    
    Problem : snapshot creation was failing after brick reset/replace
    
    Fix : changed code to set mount_dir value in rsp_dict during prerequisites
          phase i.e glusterd_brick_op_prerequisites call and removed form prevalidate
          phase.
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
    
    Change-Id: Ief5d0fafe882a7eb1a7da8535b7c7ce6f011604c
    BUG: 1512451

commit 9fa848353b0b177d68c4dcb03723a8cfe43159f3
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Nov 27 22:18:33 2017 +0530

    tests: Spurious failure multiplex-limit-issue-151.t
    
    A timing issue caused the remove-brick commit to fail.
    Replaced 'remove-brick commit' with 'remove-brick force'.
    
    Change-Id: I69144b2f7be34095dbd3a7d182e0bf01b27fb0a4
    BUG: 1517904
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit f7861e2a26e25de9714aece286c1e969765ff383
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Nov 24 17:54:35 2017 +0530

    afr: volume option fixes for GD2
    
    This patch takes care of volume options exposed via the CLI.
    
    Updates #302
    
    Change-Id: I6fd1645604928f6b9700e2425af4147cc6446a3a
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 8a478e2280a6102caa189cf3b1645e767a305d48
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Aug 31 16:00:53 2017 +0530

    features/read-only: Redefine the options for read-only and worm
    
    With https://review.gluster.org/18059 introducing new fields into the
    volume_option structure, this change takes care of the changes required
    at the read-only and worm side.
    
    Updates #302
    
    Change-Id: Ie9d38eed6739a8ef229c462448532354e275af7c
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 7df8ba088c68e10905b613de95f9f6df40d14825
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Oct 10 17:38:52 2017 +0530

    features/index: Update xlator options table
    
    Updates #302
    
    Change-Id: I2bc99394d89e94ae6aeee9de8d85a3d09991fad9
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 493545657bd122ba63d77553873c7f433fb74d04
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Nov 24 12:11:16 2017 +0530

    geo-rep: Fix slave side custom config issue
    
    Slave gsyncd will not use session config files, Slave configs are
    stored in Master config file itself and sent as argument to slave
    gsyncd.
    
    With this patch, gconf default values are overwritten if argument
    name starts with "slave-"
    
    Change-Id: Iebc51f52232c0cd30b29199f03015f97b70ce537
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1517068

commit 683b15a6a2e6c0efbb45db3fd97b9cf08c4f7194
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Nov 27 04:42:54 2017 +0530

    tests/basic/inode-leak.t: mark as known issue
    
    Mainly because the tests are consistently taking more than
    20mins for each runs.
    
    One of the samples from a regression run:
    
    > /tests/basic/inode-leak.t  -  1643 second
    
    Change-Id: If11572203c702f64847794f6d578a6dc19a0dee8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit a3f4b71c1f54eac885b5625b2387027be91e5a2a
Author: Prashant D <pdhange@redhat.com>
Date:   Wed Nov 8 22:09:42 2017 +1100

    extras/devel-tools: Fix print-backtrace script
    
    Problem:
    If cpio version is less 2.11 then cpio command failing with
    unrecognised option --directory.
    
    Solution:
    Check the cpio version and run rpm2cpio/cpio with or without
    -D or --directory option.
    
    Fixes : #359
    Change-Id: Ibd440207231807dab1b58291ab661857094f1a4a
    BUG: 1510874
    Signed-off-by: Prashant D <pdhange@redhat.com>

commit f3a8953e6a72631dc29958e996388ffed2f5940a
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Nov 16 09:47:00 2017 +0100

    libglusterfs: fix the call_stack_set_group() function
    
    - call_stack_set_group() will take the ownership of passed
      buffer from caller;
    - to indicate the change, its signature is changed from
      including the buffer directly to take a pointer to it;
    - either the content of the buffer is copied to the
      groups_small embedded buffer of the call stack, or
      the buffer is set as groups_large member of the call
      stack;
    - the groups member of the call stack is set to,
      respectively, groups_small or groups_large, according
      to the memory management conventions of the call stack;
    - the buffer address is overwritten with junk to effectively
      prevent the caller from using it further on.
    
    Also move call_stack_set_group to stack.c from stack.h
    to prevent "defined but not used [-Wunused-function]"
    warnings (not using it anymore in call_stack_alloc_group()
    implementation, which saved us from this so far).
    
    protocol/server: refactor gid_resolve()
    
    In gid_resolve there are two cases:
    either the gid_cache_lookup() call returns
    a value or not. The result is caputured in
    the agl variable, and throughout the function,
    each particular stage of the implementation
    comes with an agl and a no-agl variant.
    
    In most cases this is explicitly indicated
    via an
    
       if (agl) {
          ...
       } else {
          ...
       }
    
    but some of this branching are expressed via
    goto constructs (obfuscating the fact we stated
    above, that is, each particular stage having
    an agl/no-agl variant).
    
    In the current refactor, we bring the agl
    conditional to the top, and present the
    agl/non-agl implementations sequentially.
    
    Also we take the opportunity to clean up and
    fix the agl case:
    - remove the spurious
        gl.gl_list = agl->gl_list;
      setting, as gl is not used in the agl caae
    - populate the group list of call stack from
      agl, fixing thus referred BUG.
    
    Also fixes BUG: 1513920
    
    Change-Id: I61f4574ba21969f7661b9ff0c9dce202b874025d
    BUG: 1513928
    Signed-off-by: Csaba Henk <csaba@redhat.com>

commit d395387f601c9fb57a5fd9f19385b4de3c870de8
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Nov 23 15:28:07 2017 +0530

    geo-rep: JSON output for status and config
    
    For Glusterd2 integration, JSON output of status and config
    is very useful from gsyncd
    
    Fixes: #361
    Change-Id: I53c61f19033ad4ac601ea49469e4e7c7c8e9af3d
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit cd27e0ffb8afd69c1df28c38808c49a3af8cc75d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Oct 22 20:54:23 2017 +0200

    xdr: comply with RFC4506
    
    Change-Id: I03098a54b8d37f6201129007cf31b31d97c30a23
    BUG: 1336889
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e365fb683d81cd7ba0105384ac3b3b3a4885fd8f
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Nov 21 15:00:42 2017 +0530

    storage/posix: Update xlator options table
    
    Updates #302
    
    Change-Id: Ib8100c69267202266a7f03d0d632d45afb61d946
    Signed-off-by: Kaushal M <kaushal@redhat.com>

commit 2559d959df1a5dec10b0b80ba5ac0ec292014d8e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Nov 13 07:03:36 2017 +0530

    afr: coverity fixes
    
    1.afr_discover_do: COPY_PASTE_ERROR
    2.afr_fav_child_reset_sink_xattrs_cbk: REVERSE_INULL
    3.afr_fop_lock_proceed: UNUSED_VALUE
    4.afr_local_init: CHECKED_RETURN
    5.afr_set_split_brain_choice: REVERSE_INULL
    6.__afr_inode_write_finalize: FORWARD_NULL
    7.afr_refresh_heal_done: REVERSE_INULL
    8.afr_xl_op:UNUSED_VALUE
    9.afr_changelog_populate_xdata: DEADCODE
    10.set_afr_pending_xattrs_option: RESOURCE_LEAK
    
    Note:
    RESOURCE_LEAK complaints about afr_fgetxattr_pathinfo_cbk,
    afr_getxattr_list_node_uuids_cbk and afr_getxattr_pathinfo_cbk seem to
    be false alarms.
    
    Change-Id: Ia4ca1478b5e2922084732d14c1e7b1b03ad5ac45
    BUG: 789278
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit e19f5c34a5bef2f5d097ee359100c3fd43fd310a
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Tue Nov 14 16:45:07 2017 +0100

    cluster/ec: Remove unneded tests
    
    To reduce regression test execution time, some of the EC tests
    have been removed to save time. These tests were only doing the
    same than other existing tests but with different volume
    configurations.
    
    I keep ec-3-1.t, ec-4-1.t, ec-5-2.t and ec-6-2.t because they
    cover all the combinations of the most important cases:
    
    * Configurations with redundancy 1 and redundancy > 1
    * Configurations with #fragments = power of 2 and not a power of 2
    
    Change-Id: I0b1d15b50428b605c6a1c96df12d8054556b1f23
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit e5b871690176aec23255952b656389f335acbafa
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Nov 15 15:54:51 2017 +0530

    tier: coverity fixes in tier.c
    
    fixes coverity issues:
    127, 83, 312, 314, 48, and 506
    
    from https://download.gluster.org/pub/gluster/glusterfs/static-analysis
    /master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: Ifb206a8758790faf96619bcc9961dcf169aaad25
    BUG: 789278
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit df2d9d26c876d0360ee6cfc46f2187bfcc7da6e7
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Oct 6 15:13:02 2017 +0530

    cluster/dht: Serialize mds update code path with lookup unwind in selfheal
    
    Problem: Sometime test case ./tests/bugs/bug-1371806_1.t is failing on
             centos due to race condition between fresh lookup and setxattr fop.
    
    Solution: In selfheal code path we do save mds on inode_ctx, it was not
              serialize with lookup unwind. Due to this behavior after lookup
              unwind if mds is not saved on inode_ctx and if any subsequent
              setxattr fop call it has failed with ENOENT because
              no mds has found on inode ctx.To resolve it save mds on
              inode ctx has been serialize with lookup unwind.
    
    BUG: 1498966
    Change-Id: I8d4bb40a6cbf0cec35d181ec0095cc7142b02e29
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 50a480701f4bf6885d3811e245a47d99661695d8
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Nov 22 17:03:11 2017 +0530

    rpc-lib: coverity fixes
    
    Scan URL:
    https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-11-10-0f524f07/html/
    
    ID: 9                            (BAD_SHIFT)
    ID: 58                           (CHECKED_RETURN)
    ID: 98                           (DEAD_CODE)
    ID: 249, 250, 251, 252           (MIXED_ENUMS)
    ID: 289, 297                     (NULL_RETURNS)
    ID: 609, 613, 622, 644, 653, 655 (UNUSED_VALUE)
    ID: 432                          (RESOURCE_LEAK)
    
    Change-Id: I2349877214dd38b789e08b74be05539f09b751b9
    BUG: 789278
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 8d53be68d8fb4272f0c88fef0a00dad452b941de
Author: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
Date:   Thu Aug 25 16:35:27 2016 +0530

    tests : add a test to check if there is an inode leak
    
    This test check if there is inode leak in bricks.
    
    lru_size for mount is expected to be zero. active_size for mount
    is expected to be 1 which is of root.
    
    Change-Id: I18762b4255af411f1b55c0be98451c8ef1b35478
    BUG: 1370116
    Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>

commit aee2a1d2136f505eae180b258374ca8812a6f4fb
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Oct 24 18:35:20 2017 +0530

    cluster/dht: make rebalance use truncate incase
    
    ..
    the brick file system does not support fallocate.
    
    Change-Id: Id76cda2d8bb3b223b779e5e7a34f17c8bfa6283c
    BUG: 1488103
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit c913a6e6fcd9ebd962955ba5d51f518b2875eba3
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Mon Nov 20 10:51:09 2017 +0100

    features/locks: Fix memory leaks
    
    Change-Id: Ic1d2e17a7d14389b6734d1b88bd28c0a2907bbd6
    BUG: 1515161
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 77e3bc671aab2fda68ada53f38ec368b20675f59
Author: karthik-us <ksubrahm@redhat.com>
Date:   Tue Nov 21 19:01:36 2017 +0530

    cluster/afr: Print heal info summary output in stream fashion
    
    Problem:
    The heal info summary was printing the output at the end after
    crawling for pending heal entries completes on all the bricks.
    
    Fix:
    Printing the output immediately after the crawl on individual brick
    completes, so that it won't give the impression of CLI being hung.
    
    Change-Id: Ieaf5718736a7ee6837bac02bd30a95836e605dab
    BUG: 1506104
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 038d8f994d66eeb79734c03ecd631a12d5433221
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 11 18:58:04 2017 +0530

    libglusterfs: Handle FS errors gracefully
    
    Problem:
    FS sometimes doesn't give the expected return values. We need our common
    functions to guard against this.
    Example BUG: https://bugzilla.redhat.com/show_bug.cgi?id=864401
    
    Fix:
    When the return value is not as per specification, change the return value
    to -1 and errno to EIO
    
    BUG: 1469487
    Change-Id: I14739ab2e5ae225b1a91438b87f8928af56f2934
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 4ad64ffe8664cc0b964586af6efcf53cc619b68a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 17 07:20:21 2017 +0530

    ec: Use tiebreaker_inodelk where necessary
    
    When there are big directories or files that need to be healed,
    other shds are stuck on getting lock on self-heal domain for these
    directories/files. If there is a tie-breaker logic, other shds
    can heal some other files/directories while 1 of the shds is healing
    the big file/directory.
    
    Before this patch:
    96.67  4890.64 us 12.89 us 646115887.30us 340869 INODELK
    After this patch:
    40.76  42.35 us   15.09 us 6546.50us 438478 INODELK
    
    Fixes gluster/glusterfs#354
    Change-Id: Ia995b5576b44f770c064090705c78459e543cc64
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 3ad68df725ac32f83b5ea7c0976e2327e7037c8c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 17 07:12:42 2017 +0530

    cluster-syncop: Implement tiebreaker inodelk/entrylk
    
    In this implementation, inodelk/entrylk will be tried for the subvols
    given with trylock. In this attempt if all locks are obtained, then
    inodelk is successful, otherwise, if it gets success on the first
    available subvolume, then it will go for blocking lock, where as other
    subvolumes will not try and this acts as tie-breaker.
    
    Updates gluster/glusterfs#354
    Change-Id: Ia2521b9ccb81a42bd6104ab21f610f761ba2b801
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 373cdd6e76076b9e6a7028d3edfbef59d015e8a5
Author: James Le Cuirot <chewi@gentoo.org>
Date:   Mon Nov 20 20:44:45 2017 +0000

    build: Allow libtirpc to be explicitly requested
    
    Some distributions like Gentoo no longer include the RPC stuff in
    their glibc packages.
    
    Change-Id: Ic47065e9c2f5a0ccd860df9d7185eff59990ff10
    Signed-off-by: James Le Cuirot <chewi@gentoo.org>

commit 521626a952a0259b7cf4a1b43205b954d0252fbc
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Nov 2 13:26:01 2017 +0530

    cli: Fix coverity errors for cli-rpc-ops.c
    
    Fixes issues 147, 168, 169, 219, 715, 718, 766, 768, 772, 774, 776, 782,
    790 from the report at [1].
    
    Also, fixed some other possible static checker errors as well.
    
    [1]: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    BUG: 789278
    Change-Id: I985cea1ef787d239b2632d5a7f467070846f92e4
    Signed-off-by: Kaushal M <kaushal@redhat.com>

commit 7e20d03d37f2f0bc2da92174c914d55ab386f119
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Nov 20 17:55:35 2017 +0530

    cluster/dht: Coverity fixes for dht-rebalance.c
    
    Warning		Functions
    DEADCODE	gf_defrag_handle_migrate_error
    		gf_defrag_get_entry
    		gf_defrag_process_dir
    		gf_defrag_start_crawl
    		dht_migrate_file
    
    UNUSED_VALUE	migrate_special_files
    		dht_migrate_file
    
    FORWARD_NULL	gf_tier_do_fix_layout
    
    Change-Id: I6f408585b83a267581a4273dae7c22b8993163d5
    BUG: 789278
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit a81c0c2b9abdcb8ad73d0a226b53120d84082a09
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Nov 17 10:35:26 2017 +0530

    protocol/server: use common function to reduce duplicate code
    
    Change-Id: Ifad0a88245fa6fdbf4c43d813b47c314d2c50435
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 3840883a925fb98f2fda2975a57292e6562ceec4
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Nov 14 17:02:52 2017 +0100

    Disable gfid2path by default on NetBSD
    
    NetBSD storage of extended attributes for UFS1 badly scales when
    the list of extended attributes names rises.  gfid2path can add as
    many extended attributes names as we have files, hence we keep it
    disabled for performance sake.
    
    Change-Id: Id77b5f5ceb4d5eba1b3362b4b9fc693450ffbc2b
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    BUG: 1129939

commit 7100c0ec023dd1a4f779b8e6bee0cfbf2bef53b2
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Nov 3 15:41:34 2017 +0530

    timer: Fix possible race during cleanup
    
    As mentioned in bug1509189, there is a possible race
    between gf_timer_cancel(), gf_timer_proc() and
    gf_timer_registry_destroy() leading to use_after_free.
    
    Problem:
    
    1) gf_timer_proc() is called, locks reg, and gets an event.
    It unlocks reg, and calls the callback.
    
    2) Meanwhile gf_timer_registry_destroy() is called, and removes
    reg from ctx, and joins on gf_timer_proc().
    
    3) gf_timer_call_cancel() is called on the event being
    processed.  It cannot find reg (since it's been removed from reg),
    so it frees event.
    
    4) the callback returns into gf_timer_proc(), and it tries to free
    event, but it's already free, so double free.
    
    Solution:
    The fix is to bail out in gf_timer_cancel() when registry
    is not found. The logic behind this is that, gf_timer_cancel()
    is called only on any existing event. That means there was a valid
    registry earlier while creating that event. And the only reason
    we cannot find that registry now is that it must have got set to
    NULL when context cleanup is started.
    Since gf_timer_proc() takes care of releasing all the remaining
    events active on that registry, it seems safe to bail out
    in gf_timer_cancel().
    
    Change-Id: Ia9b088533141c3bb335eff2fe06b52d1575bb34f
    BUG: 1509189
    Reported-by: Daniel Gryniewicz <dang@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit b6da32e527f0ba28773a9adf39b1dd55953f9dc4
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Mon Nov 20 00:08:40 2017 +0530

    rpc/rpc-transport: dead code coverity fix
    
    issue: Execution cannot reach this statement: "iobuf_unref(iobuf);"
    
    function: gf_rdma_do_reads
    
    fix: removed the statement and the corresponding 'if' block
    
    Change-Id: Ia21b872996dbc8e0a66c8c28dd90b367d3c9aadd
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit c6e87387978e4b389d4e514d698279b87e60b20d
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Wed Nov 15 15:17:00 2017 +0530

    libglusterfs:checked return coverity fix
    
    Problem:Calling "gf_thread_create" without checking return value.
    
    Fix:The return value is saved and checked if gf_thread_create fails.
    
    Change-Id: Ibdaac1c90a1a8369e92ade50825598b041063da8
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit b8e80c2abfa84cd75172e7fb748a2b3114a60eba
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Sun Nov 19 23:53:28 2017 +0530

    cluster/dht: dead code coverity fix
    
    issue: Execution cannot reach this statement: "call_stub_destroy(stub);"
    
    function: dht_mkdir_hashed_cbk
    
    fix: removed the statement and the corresponding 'if' condition block.
    
    Change-Id: I3e31056ee489ede6864e51a8e666edc7da3c175f
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit aaef7e0d214b94a798b727af125006d07335b53c
Author: cholcombe973 <cholcombe973@review.gluster.org>
Date:   Wed Nov 15 19:28:05 2017 +0000

    Revert "debug/io-stats: Append stats for each interval in the same file"
    
    This reverts commit fc73ae5f81ef5926e3dc2311db116250d0f2a321.
    See bug: https://bugzilla.redhat.com/show_bug.cgi?id=1513692
    
    Change-Id: I00d5989b042d4e345621c596d5370d324948557f
    Bug: 1513692
    Signed-off-by: Chris Holcombe <xfactor973@gmail.com>

commit dbd94d5bee93ca9ad4f485147b90b4ccf8a3b61e
Author: Vishal Pandey <vishpandey2014@gmail.com>
Date:   Thu Nov 2 19:16:26 2017 +0530

    features/worm: new config option to manage deletion of Worm files.
    
    Add a new configuration option worm-files-deletable to
     file-level Worm in order to control behaviour of Worm files upon deletion.
    
    Steps to Test:
    1. Add all the configuration options to a volume to activate file-level-worm
    2. Option features.worm-files-deletable is set to 1 by default.
    3. Create a new file and wait for the retention time to expire.
    4. After retention time expires, do an truncate, rename, unlink, link
       or write to send the file in Worm state.
    5. After that do `rm -f filename`.
    6. The file is successfully removed.
    7. Repeat from step 2 by setting features.worm-files-deletable 0.
       This time deletion should not be successful.
    
    Change-Id: Ibc89861ee296e065330b93a9f9606be5da40af31
    BUG: 1508898
    Signed-off-by: Vishal Pandey <vishpandey2014@gmail.com>

commit c810ea1e2ba5c15b11808e2bd378e95c428b7f96
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Apr 4 07:13:09 2016 -0400

    rpc : Change the way client uuid is built
    
    Problem:
    Today the main users of client uuid are protocol layers, locks, leases.
    Protocol layers requires each client uuid to be unique, even across
    connects and disconnects. Locks and leases on the server side also use
    the same client uid which changes across file migrations. Which makes the graph
    switch and file migration tedious for locks and leases.
    
    file migration across bricks becomes difficult as client uuid for the same
    client, is different on the other brick.
    
    The exact set of issues exists for leases as well.
    
    Solution would be to introduce a constant in the client-uid string which
    the locks and leases can use to identify the owner client across bricks.
    
    Client uuid currently:
    %s(ctx uuid)-%s(protocol client name)-%d(graph id)%s(setvolume count/reconnect count)
    
    Proposed Client uuid:
    "CTX_ID:%s-GRAPH_ID:%d-PID:%d-HOST:%s-PC_NAME:%s-RECON_NO:%s"
    -  CTX_ID: This is will be constant per client.
    -  GRAPH_ID, PID, HOST, PC_NAME(protocol client name), RECON_NO(setvolume count)
    remains the same.
    
    Change-Id: Ia81d57a9693207cd325d7b26aee4593fcbd6482c
    BUG: 1369028
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 1c7041fd6b4be82415866dc19b9b2a5b41bd1396
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Tue Nov 14 20:12:37 2017 +0530

    features/marker: coverity fix
    
    issue: Calling "mq_inode_ctx_get" without checking return value
    
    function: marker_rename_unwind
    
    fix: typecasted the return value of function to void
    
    Change-Id: I552b1d76df434dfc3d9c2273ec63ccc4b9f960f2
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit 09debb4d4a5b7229ca128b549bce22d8820da7e9
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Nov 17 12:06:53 2017 +0530

    cluster/dht: Don't set ACLs on linkto file
    
    The trusted.SGI_ACL_FILE appears to set posix
    ACLs on the linkto file that is a target of
    file migration. This can mess up file permissions
    and cause linkto identification to fail.
    Now we remove all ACL xattrs from the results of
    the listxattr call on the source before setting them
    on the target.
    
    Change-Id: I56802dbaed783a16e3fb90f59f4ce849f8a4a9b4
    BUG: 1514329
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit bd44d59741bb8c0f5d7a62c5b1094179dd0ce8a4
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Aug 16 18:01:17 2017 +0530

    afr: add checks for allowing lookups
    
    Problem:
    In an arbiter volume, lookup was being served from one of the sink
    bricks (source brick was down). shard uses the iatt values from lookup cbk
    to calculate the size and block count, which in this case were incorrect
    values. shard_local_t->last_block was thus initialised to -1, resulting
    in an infinite while loop in shard_common_resolve_shards().
    
    Fix:
    Use client quorum logic to allow or fail the lookups from afr if there
    are no readable subvolumes. So in replica-3 or arbiter vols, if there is
    no good copy or if quorum is not met, fail lookup with ENOTCONN.
    
    With this fix, we are also removing support for quorum-reads xlator
    option. So if quorum is not met, neither read nor write txns are allowed
    and we fail the fop with ENOTCONN.
    
    Change-Id: Ic65c00c24f77ece007328b421494eee62a505fa0
    BUG: 1467250
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 19f9bcff4aada589d4321356c2670ed283f02c03
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Aug 16 17:26:48 2017 +0530

    cluster/afr: Fix for arbiter becoming source
    
    Problem:
    When eager-lock is on, and two writes happen in parallel on a FD
    we were observing the following behaviour:
    - First write fails on one data brick
    - Since the post-op is not yet happened, the inode refresh will get
      both the data bricks as readable and set it in the inode context
    - In flight split brain check see both the data bricks as readable
      and allows the second write
    - Second write fails on the other data brick
    - Now the post-op happens and marks both the data bricks as bad and
      arbiter will become source for healing
    
    Fix:
    Adding one more variable called write_suvol in inode context and it
    will have the in memory representation of the writable subvols. Inode
    refresh will not update this value and its lifetime is pre-op through
    unlock in the afr transaction. Initially the pre-op will set this
    value same as read_subvol in inode context and then in the in flight
    split brain check we will use this value instead of read_subvol.
    After all the checks we will update the value of this and set the
    read_subvol same as this to avoid having incorrect value in that.
    
    Change-Id: I2ef6904524ab91af861d59690974bbc529ab1af3
    BUG: 1482064
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit d71b53d2487ef93fc8a362ecc9fb735222e713e4
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Tue Nov 14 14:39:43 2017 +0530

    features/changetimerecorder:unused value coverity fix
    
    Problem : Overwritting the value of ret in extract_db_params.
    
    Fix : The value is used in out.
    
    Change-Id: Ib7bee999c6f19e0c83ef47deab61835977162bd5
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit d1d9a03a06bead6d62becb1e563765222fbcb1bb
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu Nov 2 17:23:05 2017 +0530

    tier/glusterd: coverity issues in glusterd-tier.c
    
    Coverity issues fixed in this patch:
    254, 256, 295, 791, 546
    
    from: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/
    master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I44b7d307a3434040125d8b1d6fb18221f30f678d
    BUG: 789278
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit 1d18ec3f04d1e27309471daadea345cf25534b5e
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Aug 31 15:06:19 2017 +0530

    Upcall: Add new GD2 fields to upcall xlator options
    
    Add new fields used by GD2 to the upcall xlator options.
    
    Updates #302
    
    Change-Id: Ia684648aa06312ca9649f00af17575162adb4996
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit aaebac4a5e60b564350f8579c7ebafd06e9a7ca6
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu Aug 31 16:47:48 2017 +0530

    features/changetimerecorder: xlators opts improvement for GD2
    
    Updates: #302
    
    Change-Id: Ib401eb6fa187ab2498de8b5cdf4686e388192208
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit 6815c0ce3045fb4f57268081fa0afeb9567f2453
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Oct 10 17:53:24 2017 +0530

    protocol/server: Update xlator options table
    
    Updates #302
    
    Change-Id: Ifb604914a5d8b5c47ea2de0c026043b71a783387
    Signed-off-by: Kaushal M <kaushal@redhat.com>

commit 0447eb4b6df3bac8b8f43a58ded6083c89866957
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Aug 31 15:13:26 2017 +0530

    features/changelog: xlators opts improvement for GD2
    
    Updates: #302
    
    Change-Id: Ibbf0f99d4b81a5e9a5ccee1889214b74f083a7db
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 0161b393c61608cb4ecdf20daff3a1490b3e8ff9
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Aug 31 15:03:50 2017 +0530

    barrier: redefine the options
    
    With https://review.gluster.org/18059 introducing new fields into the
    volume_option structure, this change takes care of the changes required
    at the barrier side.
    
    Updates #302
    
    Change-Id: If991df10b130c762a44883668a00e49943a508f8
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 2bfe2cec0c0832b703f0da472ad6584f9d8898e2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Aug 31 07:06:28 2017 -0400

    feature/bitrot: stub xlators opts for GD2
    
    Updates #302
    Change-Id: I320eabf0c83295e90a312316a8373ccf5bf91dc4
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit dd80e9e33bc42d11c6cba375bca2ee9a2db9776c
Author: Pranith Kumar <pkarampu@redhat.com>
Date:   Thu Nov 2 16:19:17 2017 +0530

    features/index: initialize the options properly
    
    watchlists should not over-write values gathered in previous invocation.
    
    Change-Id: I5634930d20e720ad6509b03a64360d7320800565
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 336e2d5350012829e08cc55c25a76fb426e888a0
Author: Ji-Hyeon Gim <potatogim@gluesys.com>
Date:   Wed Nov 15 20:51:07 2017 +0900

    mailmap: add mailmap entry for potatogim
    
    Change-Id: I2dd0dbb1949a8cab0a40e08f39182366a8a44990
    Signed-off-by: Ji-Hyeon Gim <potatogim@gluesys.com>

commit 3cda1da32e84240a7e9597cf0cc76b3cb1497882
Author: Ji-Hyeon Gim <potatogim@gluesys.com>
Date:   Wed Nov 15 18:17:20 2017 +0900

    who-wrote-glusterfs: add an alias for potatogim@potatogim.net
    
    Change-Id: Ieb3d1910f0284bd951089c197abc569ae95e5bcd
    Signed-off-by: Ji-Hyeon Gim <potatogim@gluesys.com>

commit 0284bd630baa376b00d334d6339272c896960473
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu Nov 2 18:13:17 2017 +0530

    tier: coverity fix for tier-common.c
    
    fix for the coverity id:
    258, 162
    
    Change-Id: I35ba21e37e186b7c1ce54faf5b24f48858e6fc70
    BUG: 789278
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit 3bf2ba3fb4910a4e9ba6ea7850f3737c9c285fe8
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Tue Nov 14 16:50:49 2017 +0530

    fuse-lib: checked_return coverity fix
    
    issue: Calling "chdir" without checking return value
    
    function: gf_fuse_unmount_daemon
    
    fix: typecasted return value of function to void.
    
    Change-Id: I5f06fbe886a35c2d4c9f763eeb01771e9451f232
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit 3a0d9584e772191336854b140fadd3b124714012
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Nov 8 09:29:49 2017 +0530

    glusterd: Fix coverity issues in handshake module
    
    This patch fixes coveruty issues 737,738,172,188,728,198,235,35.
    
    Change-Id: I632ddc5edbfb03bc81ce27f02886b8e262c1d946
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit a0b3d6534b5c4e84742ee9962a49a02009c637cd
Author: Ji-Hyeon Gim <potatogim@gluesys.com>
Date:   Wed Nov 15 18:13:18 2017 +0900

    who-wrote-glusterfs: add gluesys.com to domain-map
    
    Change-Id: Idfc62026ca50aaf8767f093b4daefd7119564a1f
    Signed-off-by: Ji-Hyeon Gim <potatogim@gluesys.com>

commit 959f5267fa8592d75dda9a3892378c48c55eee35
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Nov 10 14:47:31 2017 +0530

    dict: Fix several coverity issues in dict
    
    This patch fixes issues 230,592,593,110,63 from [1]
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Note: Resolve FORWARD_NULL coverity issue in glusterfs_ctx_new is
          also fixed with this patch.
    
    BUG: 789278
    Change-Id: Ic4199a144a14cc9ead7366fb1c9699197141bc86
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit c46618973a22875bca4ac8835cc71bb8f3aeaa65
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Thu Nov 9 15:15:37 2017 +0530

    glusterd: Fix coverity issues in glusterd-handler.c
    
    Fixes get-state CLI related coverity issues 477, 511, 515, 523,
    526 and 527 from the report at [1]
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: Ieb6f64c9035b4d9338d9515de003d607b7a4e9bc
    BUG: 789278
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>

commit f65ad580cf81b4853fa496b628f3dfd9d7b66ee9
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Oct 12 11:31:34 2017 +0530

    features/changelog: Structured logging support
    
    Structured logging infra is available in logging library with
    issue #240. Log messages with dynamic content are identified and
    converted to structured logging format(`gf_msg` to `gf_smsg` and
    `gf_log` to `gf_slog`)
    
    BUG: 1501054
    Change-Id: I5fccc354730c07cb9ae444d0b959d1d72bd9be49
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 53e28cc98c4cda61dc0d1f8ce8dcf3d77dcacb15
Author: Kamal Mohanan <kmohanan@redhat.com>
Date:   Fri Nov 3 12:24:32 2017 +0530

    xlators/features/trash: STRING_OVERFLOW Coverity fixes in trash.c
    
    Replaced strcpy, strcat with strncpy, strncat calls.
    
    Change-Id: Ibf46a2b5ae4a0dd1632be46d6fe3597f6ace7a41
    BUG: 789278
    Signed-off-by: Kamal Mohanan <kmohanan@redhat.com>

commit 306344a1cc1d2569a00b9f1926a944a7790a9222
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Oct 13 16:53:51 2017 +0530

    libglusterfs/options: Add new member 'setkey' to xlator options
    
    The 'setkey' will be used as the key by GD2 when setting the option
    during volgen. 'setkey' also supports using varstrings.
    
    This is mainly to be used for options, which use a different key for
    'volume set' and in volfiles. For eg. the 'auth.*' options of
    protocol/server.
    
    The protocol/server xlator has been updated to make use of this for the
    auth.allow and auth.reject options.
    
    Updates #302
    
    Change-Id: I1fd2fd69625c9db48595bd3f494c221625255169
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 5f5d166e89367dc0d72fa02ca4e8ca2d28a06cdd
Author: Vishal Pandey <vishpandey2014@gmail.com>
Date:   Tue Nov 14 14:33:19 2017 +0530

    eventsapi: glustereventsd hardcodes working-directory
    
    Issue:
    Glusterevents daemon hardcodes glusterd working directory
     even though it can be changed later in .vol file
     which causes breaks in the code.
    
    Fix: Use python subprocess module to get the working directory
    of gluster daemon in eventsapiconf.py.in.
    
    Change-Id: I5e92185604f8c8aeb77dabdc00f9ea0f8e92c88d
    BUG: 1512455
    Signed-off-by: Vishal Pandey <vishpandey2014@gmail.com>

commit a5b5cbb99eb946cdc9ad08b2d321005def13f0a1
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Tue Nov 14 20:32:59 2017 +0530

    glusterd: checked_return coverity fix
    
    function: glusterd_store_retrieve_options
    
    issue: Calling "gf_store_iter_destroy" without checking return value
    
    fix: typecasted the return value of the function to void
    
    Change-Id: I6dc4f4308b1eca8d6ee85834a1530ff356c73898
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit 705ec055040268f876d04fe5743a6ce4738d6e02
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 21 12:56:14 2017 +0530

    geo-rep: Refactoring Config and Arguments parsing
    
    - Fixed Python pep8 issues
    - Removed dead code
    - Rewritten configuration management
    - Rewritten Arguments/subcommands handling
    - Added Args upgrade to accommodate all these changes without changing
      glusterd code
    - use of md5 removed, which was used to hash the brick path for workdir
    
    Both Master and Slave nodes will have subdir for session in the
    format "<mastervol>_<primary_slave_host>_<slavevol>
    
      $GLUSTER_LOGDIR/geo-replication/<mastervol>_<primary_slave_host>_<slavevol>
      $GLUSTER_LOGDIR/geo-replication-slaves/<mastervol>_<primary_slave_host>_<slavevol>
    
    Log file paths renamed since session info is available with directory
    name itself.
    
      $LOG_DIR_MASTER/
          - gsyncd.log - Gsyncd, Worker monitor logs
          - mnt-<brick-path>.log - Aux mount logs, mounted by each worker
          - changes-<brick-path>.log - Changelog related logs(One per brick)
    
      $LOG_DIR_SLAVE/
          - gsyncd.log - Slave Gsyncd logs
          - mnt-<master-node>-<master-brick-path>.log - Aux mount logs,
            mounted for each connection from master-node:master-brick
          - mnt-mbr-<master-node>-<master-brick-path>.log - Same as above,
            but mountbroker setup
    
    Fixes: #73
    Change-Id: I2ec2a21e4e2a92fd92899d026e8543725276f021
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit da825da9501bcb51656e82cda3c21a2ef592c5e2
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Tue Nov 14 10:53:47 2017 +0100

    cluster/ec: Fix op-version for disperse.other-eager-lock
    
    The op-version used for the new option was wrong. It has been set
    to 3.13.0.
    
    Change-Id: I88fbd7834e4a8018c8906303e734c251e90be8cf
    BUG: 1502610
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 49afb70f78027f63f4b4a66967e104b109f2f3b9
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Tue Nov 14 14:24:21 2017 +0530

    cluster: dead_code coverity fix
    
    function: stripe_entry_self_heal
    
    issue: Execution cannot reach this statement: "dict_unref(xdata);"
    
    fix: removed the 'if' condition and the corresponding actions because if the execution reaches this statement, then the value of xdata will always be NULL
    
    Change-Id: Iebc825339e2e1236b92bed39d81a1a9aba10164e
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit 1cee2719d36e1ca8cd646c9ce94679014c5a28a4
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Tue Nov 14 13:59:14 2017 +0530

    glusterd: dead_code coverity fix
    
    issue: Execution cannot reach this statement: "rsp.op_errno = gf_errno_to_...".
    
    function:__server_event_notify
    
    fix: removed the if statement and the corresponding actions. Also, the variable was not being used anywhere else, so removed its declaration as well
    
    Change-Id: I85259e276c482cc9c98b1a829426bcec7412ce3f
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit 6e2ce37341e5d600d8fd5648b39eec0dbdbe45ad
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Nov 13 05:27:50 2017 -0500

    geo-rep: Fix data sync issue during hardlink, rename
    
    Problem:
    The data is not getting synced if master witnessed
    IO as below.
    
    1. echo "test_data" > f1
    2. ln f1 f2
    3. mv f2 f3
    4. unlink f1
    
    On master, 'f3' exists with data "test_data" but on
    slave, only f3 exists with zero byte file without
    backend gfid link.
    
    Cause:
    On master, since 'f2' no longer exists, the hardlink
    is skipped during processing. Later, on trying to sync
    rename, since source ('f2') doesn't exist, dst ('f3')
    is created with same gfid. But in this use case, it
    succeeds but backend gfid would not have linked as 'f1'
    exists with the same gfid. So, rsync would fail with
    ENOENT as backend gfid is not linked with 'f3' and 'f1'
    is unlinked.
    
    Fix:
    On processing rename, if src doesn't exist on slave,
    don't blindly create dst with same gfid. The gfid
    needs to be checked, if it exists, hardlink needs
    to be created instead of mknod.
    
    Thanks Aravinda for helping in RCA :)
    
    Change-Id: I5af4f99798ed1bcb297598a4bc796b701d1e0130
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    BUG: 1512483
    Reporter: dimitri.ars@gmail.com

commit fa29170d768e77c6bedf220f09fe90aa1819cc99
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Nov 1 23:44:02 2017 +0530

    glusterd: DEADCODE coverity fix
    
    Problem: execution cannot enter into if block since the condition
    !address is always false.
    
    Fix: removing if block solves it.
    
    Change-Id: I47b4beca7bdc095900b46e3f5a5cb9629aa2a4d7
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 3f8d118e48f11f448f35aca0c48ad40e0fd34f5b
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Tue Nov 7 13:45:03 2017 +0100

    libglusterfs/atomic: Improved atomic support
    
    This patch solves a detection problem in configure.ac that prevented
    that compilation detects builtin __atomic or __sync functions.
    
    It also adds more atomic types and support for other atomic functions.
    
    An special case has been added to support 64-bit atomics on 32-bit
    systems. The solution is to fallback to the mutex solution only for
    64-bit atomics, but smaller atomic types will still take advantage
    of builtins if available.
    
    Change-Id: I6b9afc7cd6e66b28a33278715583552872278801
    BUG: 1510397
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 87d5fb2ca50ab2812eabc7373216c45a5b4d16df
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Mon Nov 13 16:48:26 2017 +0530

    glusterd: dead code coverity fix
    
    function: glusterd_volume_rebalance_use_rsp_dict
    
    problem: Execution cannot reach this statement: "goto out;"
    
    fix: removed the condition 'if(!ctx_dict)' and the corresponding action 'goto out;' because it will never be executed.
         reason: if the execution reaches this condition, then the value of '!ctx_dict' will always be false otherwise the execution will reach the 'out'
    	     label, skipping the execution of this conditional statement.
    
    html link of issue: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-11-10-0f524f07/html/1/99glusterd-utils.c.html#error
    
    Change-Id: I7ab6b2386bb01c54edd872f9f83bb8d2a4cd499f
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit 27e5fbf6eeeb2402a625a20c966324dea3d6a876
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Mon Nov 13 21:28:51 2017 +0530

    glusterd: checked_return coverity fix
    
    issue: Calling "recursive_rmdir" without checking return value
    
    fix: typecasted return value of function 'recursive_rmdir' to void
    
    Change-Id: Ie95c2a2c503bb247afa69823d0043c3af5e036e8
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit e3c938e01f1f71cda54ad278c20f41caa1340adc
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Mon Nov 13 15:03:05 2017 +0530

    glusterd: buffer_size_warning coverity fix
    
    function: glusterd_import_volinfo
    
    problem: Calling strncpy with a maximum size argument of 256 bytes on destination array "new_volinfo->parent_volname" of size 256 bytes might leave the destination string unterminated.
    
    fix: The third argument of strncpy specifies the number of characters to be copied from the source string to the destination string. To make sure that the final string in destination is always null terminated, we copy 1 less character than the total capacity of the destination array and the last element of the array will be filled by '/0' automatically by the strncpy function.
    
    html link of issue: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-11-10-0f524f07/html/1/39glusterd-utils.c.html#error
    
    Change-Id: I76b0d10e6a932b0885531c9be3c4f4ce7239f3e1
    BUG: 789278
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit f6ab03d27cf394f8429b4c77cef0602547f6fd67
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Sat Nov 11 01:12:02 2017 +0530

    libglusterfs/gfdb:coverity issue fix
    
    Coverity Id:719,748,761
    
    problem : The value of "ret" is overwritten in init_db and
    add_conection_node
    
    Change-Id: Iade8ca8d61c5e25e8c311b1375219f5f61d51bc3
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 6343b16f53c2563c238a5b42e0e256d7091a7100
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Sat Nov 11 00:12:10 2017 +0530

    libglusterfs:UNUSED VALUE coverity fix
    
    Problem : Overwriting previous write to "ret" with value "EVENT_SEND_OK"
    before itr can be used.
    
    Fix: The value of ret is used in out.
    
    Change-Id: I2cdb32e441c85c94de30de89a7a4121fd54d1acd
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 4ded7d84ccd4a5391788a66029bf5c2424f6e08a
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Nov 7 13:05:56 2017 +0530

    debug/io-stats: Coverity fix in io-stats
    
    Coverity ID: 539
    Coverity ID: 542
    Coverity ID: 365
    Coverity ID: 366
    Coverity ID: 502
    Coverity ID: 76
    
    Change-Id: I0369856e8958e167a43065801096432b8855c114
    BUG: 789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 7d00abbf57f93cc2e6064d9bc94facbb961335c7
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Nov 8 16:15:43 2017 +0530

    features/libgfchangelog: Fix coverity issues
    
    Error: DEADCODE:
    xlators/features/changelog/lib/src/gf-changelog-journal-handler.c:524:
    dead_error_begin: Execution cannot reach this statement: "default:".
    
    Error: DEADCODE:
    xlators/features/changelog/lib/src/gf-history-changelog.c:984:
    dead_error_line: Execution cannot reach the expression "to" inside
    this statement: "if (!from || !to)
      ret = -1;".
    
    Error: REVERSE_INULL:
    xlators/features/changelog/lib/src/gf-changelog-journal-handler.c:678:
    check_after_deref: Null-checking "entry" suggests that it may be null,
    but it has already been dereferenced on all paths leading to the
    check.
    
    Error: STACK_USE:
    xlators/features/changelog/lib/src/gf-changelog-journal-handler.c:275:
    stack_use_local_overflow: Local variable "ascii" uses 12288 bytes of
    stack space, which exceeds the maximum single use of 10000 bytes.
    
    Error: STACK_USE:
    xlators/features/changelog/lib/src/gf-changelog-journal-handler.c:167:
    stack_use_local_overflow: Local variable "ascii" uses 12288 bytes of
    stack space, which exceeds the maximum single use of 10000 bytes.
    
    Error: STRING_NULL:
    xlators/features/changelog/lib/src/gf-changelog-journal-handler.c:589:9:
    string_null_sink_parm_call: Passing parameter "from_path" to "open"
    which expects a null-terminated string.
    
    Error: UNUSED_VALUE:
    xlators/features/changelog/lib/src/gf-history-changelog.c:628:
    assigned_value: Assigning value "-1" to "ret" here, but that stored
    value is overwritten before it can be used.
    
    Error: STRING_NULL:
    xlators/features/changelog/lib/src/gf-history-changelog.c:518:
    string_null_argument: Function "sys_pread" does not terminate string
    "*ccd->changelog".
    
    BUG: 789278
    Change-Id: I1414ec6d4a118ce0c14df4dbe50995c85fe3ecf7
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 2c066c4c365e77421d1009851144efae0b028628
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Sep 27 11:37:28 2017 +0530

    extras: scripts to control CPU/MEMORY for any gluster daemon during runtime
    
    Problem: Sometime gluster daemons like glustershd can consume a lot of cpu and/
    or memory if there is a large amount of data/ entries to be healed.
    
    Solution: Until we have some form of throttling/ QoS mechanisms built into
    gluster, we can use control groups for regulating cpu and memory of any gluster
    daemon using control-cpu-load.sh and control-mem.sh scripts respectively.
    
    Test:    To test the control-cpu-load.sh script follow below procedure:
             1) Setup distribute replica environment
             2) Selfheal daemon off
             3) Down one node from replica nodes
             4) Create millions of files from mount point
             5) Start down node
             6) Check cpu usage for shd process in top command
             7) Run script after provide shd pid with CPU quota value
             8) Check again cpu usage for shd process in top command
    
    Note: control-mem.sh script can cap the memory usage of the process to the set
    limit, beyond which the process gets blocked. It resumes either when the memory
    usage comes down or if the limit is increased.
    
    BUG: 1496335
    Change-Id: Id73c36b73ca600fa9f7905d84053d1e8633c996f
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 05f9c13f4d69e4113f5a851f4097ef35ba3f33b2
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Oct 25 12:42:23 2017 +0530

    cluster/afr: Print heal info split-brain output in stream fashion
    
    Problem:
    When we trigger the heal info split-brain command the o/p is not
    streamed as it is received, but dumped at the end for all the bricks
    together. This gives a perception that the command is hung.
    
    Fix:
    When we get a split brain entry while crawling throught the pending
    heal entries, flush that immediately so that it prints the output
    in a stream fashion and doesn't look like the cli is hung.
    
    Change-Id: I7547e86b83202d66616749b8b31d4d0dff0abf07
    BUG: 1506104
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 76a83f98b78a0bdf29bbb0f8e4c9ab74dae52be4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Nov 9 22:42:22 2017 +0530

    tests: fix bug-1483058-replace-brick-quorum-validation.t spurious failure
    
    Change-Id: I04c35305bfb663eabbf715eee78695adfd4a2d20
    BUG: 1511310
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 781bc5bd68824cae4456855823be17f43b5ae683
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Oct 17 11:28:43 2017 -0400

    glusterd: Validate changelog on geo-rep volume
    
    If geo-rep is configured on volume, don't allow
    to disable changelog.
    
    Change-Id: I7d1ba8b2939c8fe6ee6c59fb923d9aa1bdab553c
    BUG: 1503227
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit e5c33ca37f05d92312768976b1dbd359a213a4b3
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Nov 2 00:17:42 2017 +0530

    glusterd: PW.INCLUDE_RECURSION coverity fix
    
    This patch fixes coverity issue 421
    
    Problem: #include file "glusterd-utils.h" includes itself,
    glusterd-utils.h -> glusterd-peer-utils.h -> glusterd-utils.h
    
    Fix: include of glusterd-utils.h into glusterd-peer-utils.c instead
    of glusterd-peer-utils.h.
    
    Change-Id: I164732dfb1f64636577765124ddc5361ff0f1cc5
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit cd249f4cb783f8d79e79468c455732669e835a4f
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Nov 7 17:24:24 2017 +0530

    glusterfsd: making parent process to write pidfile while forking
    
    Issue: pid is written into glusterd.pid by child process instead of
    parent process while forking.
    
    Fix: After fork returns child pid to parent process, it falls under
    default case of switch statement, call glusterfs_pidfile_update()
    in default case instead of postfork label.
    
    Change-Id: I41b616c140592bf117601bc451dfd8b934a5b640
    BUG: 1509340
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 230ccb3f8ff6d2c94474e2221d9e4e7b834e8fcf
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Nov 10 13:31:28 2017 +0530

    glusterd: few coverity fixes in glusterd-handler.c
    
    This patch fixes coverity issues 695,555,263
    
    Change-Id: I3577cbc793b6652b24cc719037db2bdd5e27f196
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 371bb8e0290ed5f26e5959225782b84c300f0a81
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Sat Nov 4 23:14:37 2017 +0530

    mgmt/glusterd  glusterd coverity fixes
    
    Coverity ID: 498
    Coverity ID: 756
    Coverity ID: 764
    Coverity ID: 553
    Coverity ID: 562
    Coverity ID: 765
    Coverity ID: 731
    Coverity ID: 545
    Coverity ID: 781
    
    Change-Id: I5922db462ba3f71397ae097d7e56739c335114d3
    BUG: 789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit a87abbd42e8b02deabbdfe290b16ed0d2f2e4c45
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Sep 18 14:07:31 2017 +0530

    cluster/ec: Keep last written strip in in-memory cache
    
    Problem:
    Consider an EC volume with configuration  4 + 2.
    The stripe size for this would be 512 * 4 = 2048.
    That means, 2048 bytes of user data stored in one
    stripe. Let's say 2048 + 512 = 2560 bytes are
    already written on this volume. 512 Bytes would
    be in second stripe. Now, if there are sequential
    writes with offset 2560 and of size 1 Byte, we have
    to read the whole stripe, encode it with 1 Byte and
    then again have to write it back. Next, write with
    offset 2561 and size of 1 Byte will again
    READ-MODIFY-WRITE the whole stripe. This is causing
    bad performance because of lots of READ request
    travelling over the network.
    
    There are some tools and scenario's where such kind
    of load is coming and users are not aware of that.
    Example: fio and zip
    
    Solution:
    One possible solution to deal with this issue is to
    keep last stripe in memory. This way, we need not to
    read it again and we can save READ fop going over the
    network. Considering the above example, we have to
    keep last 2048 bytes (maximum) in memory per file.
    
    Change-Id: I3f95e6fc3ff81953646d374c445a40c6886b0b85
    BUG: 1471753
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 83558c69736878d2554ba77af3a6e27574da9447
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Nov 3 11:15:52 2017 +0530

    rpc: Fix several coverity issues in rpc/socket code
    
    This patch fixes issues 287,289,286,809,690,276,401,402,403 from [1]
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    BUG: 789278
    Change-Id: I2716d07fbdab59f779c2852bde07756b0e9a4ddc
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 0f524f0710229a7f8de3a4e1e6a2790d40f67a8e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Sep 21 18:11:15 2017 -0400

    geo-rep: Fix rename of directory in hybrid crawl
    
    In hybrid crawl, renames and unlink can't be
    synced but directory renames can be detected.
    While syncing the directory on slave, if the
    gfid already exists, it should be rename.
    Hence if directory gfid already exists, rename
    it.
    
    Change-Id: Ibf9f99e76a3e02795a3c2befd8cac48a5c365bb6
    BUG: 1499566
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 0fc1c562d8b8d09ec2b59bc525ec5635a21a4561
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Nov 8 06:08:02 2017 -0500

    features/bitrot: Fix coverity issues
    
    1. br_update_scrub_finish_time:  BUFFER_SIZE_WARNING
    2. br_read_bad_object_dir     :  DEADCODE
    3. bit-rot.c: init            :  RESOURCE_LEAK
    4. br_stub_fsetxattr          :  STACK_USE
    5. br_stub_setxattr           :  STACK_USE
    6. bit-rot-stub.c: init       :  BUFFER_SIZE_WARNING
    
    Change-Id: Ie620f431bd7548fedae2152aa756ccdcd89ddf89
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    BUG: 789278

commit 2899a4f125735636fe7cd8db73c0b8a13289df9b
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Wed Nov 8 16:18:56 2017 +0530

    quota: fixes issue in quota.conf when setting large number of limits
    
    Problem: It was not possible to configure more than 7712 quota limits.
    This was because a stack buffer of size 131072 was used to read from
    quota.conf file. In the new format of quota.conf file each gfid entry
    takes 17bytes (16byte gfid + 1 byte type). So, the buf_size was not a
    multiple of gfid entry size and as per code this was considered as
    corruption.
    
    Solution: make buf size multiple of gfid entry size
    
    Change-Id: Id036225505a47a4f6fa515a572ee7b0c958f30ed
    BUG: 1510940
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>

commit 046c7e3199fca715592762e271e6061ac99b0c4b
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Nov 9 13:15:51 2017 +0530

    glusterd: display gluster volume status, when quorum type is server
    
    Problem: when server-quorum-type is server, after restarting glusterd
    in the node which is up, gluster volume status is giving incorrect
    information.
    
    Fix: check whether server is blank, before adding other keys into the
    dictionary.
    
    Change-Id: I926ebdffab330ccef844f23f6d6556e137914047
    BUG: 1511339
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 8b57378e5596f287a7b9d106dd6fb56a624b42ee
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Nov 7 16:09:37 2017 +0530

    mount/fuse: use fstat in getattr implementation if any opened fd is available
    
    The restriction of using fds opened by the same Pid means fds cannot
    be shared across threads of multithreaded application. Note that fops
    from kernel have different Pid for different threads. Imagine
    following sequence of operations:
    
    * Turn off performance.open-behind
    * Thread t1 opens an fd - fd1 - on file "file". Let's assume nodeid of
      "file" is "nodeid-file".
    * Thread t2 does RENAME ("newfile", "file"). Let's assume nodeid of
      "newfile" as "nodeid-newfile".
    * t2 proceeds to do fstat (fd1)
    
    The above set of operations can sometimes result in ESTALE/ENOENT
    errors. RENAME overwrites "file" with "newfile" changing its nodeid
    from "nodeid-file" to "nodeid-newfile" and post RENAME, "nodeid-file" is
    removed from the backend. If fstat carries nodeid-file as argument,
    which can happen if lookup has not refreshed the nodeid of "file" and
    since t2 doesn't have an fd opened, fuse_getattr_resume uses STAT
    which will fail as "nodeid-file" no longer exists.
    
    Since the above set of operations and sharing of fds across
    multiple threads are valid, this is a bug.
    
    The fix is to use any fd opened on the inode. In this specific example
    fuse_getattr_resume will find fd1 and winds down the call as fstat
    (fd1) which won't fail.
    
    Cross-checked with "Miklos Szeredi" <mszeredi.at.redhat.dot.com> for
    any security issues with this solution and he approves the solution.
    
    Thanks to "Miklos Szeredi" <mszeredi.at.redhat.dot.com> for all the
    pointers and discussions.
    
    Change-Id: I88dd29b3607cd2594eee9d72a1637b5346c8d49c
    BUG: 1510401
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 52add0a289b8433547c5443b0dfd76e157275b10
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Oct 12 11:31:34 2017 +0530

    features/libgfchangelog: Structured logging support
    
    Structured logging infra is available in logging library with
    issue #240. Log messages with dynamic content are identified and
    converted to structured logging format(`gf_msg` to `gf_smsg` and
    `gf_log` to `gf_slog`)
    
    BUG: 1501054
    Change-Id: I99b35396455a634f5267eb1379d481ea981e5494
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 0821a57bd2e7518d1c8df2d4403a2dfbb8ee5b6b
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Fri Nov 3 02:42:23 2017 +0530

    Coverity Issue: PW.INCLUDE_RECURSION in several files
    
    Coverity ID: 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417,
    418, 419, 423, 424, 425, 426, 427, 428, 429, 436, 437, 438, 439,
    440, 441, 442, 443
    
    Issue: Event include_recursion
    
    Removed redundant, recursive includes from the files.
    
    Change-Id: I920776b1fa089a2d4917ca722d0075a9239911a7
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit 9eea263043e86ebd79ae72cc79ce4c22f336f958
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Nov 3 16:54:55 2017 +0530

    snapshot: fix coverity issue 'UNREACHABLE'
    
    Problem : In glusterd-snapshot-utils.c:2778 code path is unreachable as it was
              intended for n-way replication snapshot support.
    
    Fix : Removed code now, will revert back this change in future once we support
          n-way replication in snapshot.
    
    This patch fixes coverity issue 687 from [1].
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I163f318e62a7e84d211d9930dedee6587d37b2a0
    BUG: 789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 2d258d818a05ef1b7456ee6cec263605af24deba
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Tue Oct 24 16:10:23 2017 +0530

    Quota: Adding man page for quota
    
    Change-Id: I95365c443705f56561cc10138318eb96db3b941e
    BUG: 1505660
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>

commit 635c1c3691a102aa658cf1219fa41ca30dd134ba
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Nov 6 13:23:32 2017 +0530

    glusterd: restart the brick if qorum status is NOT_APPLICABLE_QUORUM
    
    If a volume is not having server quorum enabled and in a trusted storage
    pool all the glusterd instances from other peers are down, on restarting
    glusterd the brick start trigger doesn't happen resulting into the
    brick not coming up.
    
    Change-Id: If1458e03b50a113f1653db553bb2350d11577539
    BUG: 1509845
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 7403bddb58fc0db369d47671b8d4ca4cf221b4bc
Author: Vishal Pandey <vishpandey2014@gmail.com>
Date:   Tue Sep 26 11:55:25 2017 +0530

    glusterd: Coverity Issue FORWARD_NULL fix
    
    Problems: According to Coverity Issue ID 207
    issues are as follows-
    
    a-) Dereferencing "this" pointer without checking if it points to NULL.
    b-) The IF condition on line 1750 should check
        if any *one* of dict, this or peerinfo is NULL
        and not *all*.
    
    Fix:
    Replace the && operator with || to check if any *one* of
    this, dict or peerinfo is NULL and then execute out label.
    
    Change-Id: I40057d6cade71d3862c8e491bf4137cf25dda327
    BUG: 789278
    Signed-off-by: Vishal Pandey <vishpandey2014@gmail.com>

commit 175f6cc76038920feb27aa76f2401765c1d8cefd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Nov 6 17:54:30 2017 +0530

    features/shard: Coverity fixes
    
    This patch fixes coverity issues 242 and 453.
    
    Change-Id: If18f40539dccc7c2fcdcf8ef9b6fa3efbb3e462f
    BUG: 789278
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 32d67a77c5d0b117659ffec2fff75717f9770568
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Nov 6 22:06:46 2017 +0530

    cli: Fix coverity issues in cli.c
    
    This patch fixes coverity issue 536
    
    BUG: 789278
    Change-Id: I9fe7b324a3ab1f16b4ee4e63818f93ef71d3405a
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 63eb488298d48059a746384110f3d9a11d0aaa71
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Sat Nov 4 23:37:18 2017 +0530

    protocol/server : Coverity Fixes
    
    Coverity ID: 802
    Coverity ID: 741
    Coverity ID: 808
    
    Change-Id: If1b3196f0d1ba850c349c65f1626e41dcf42b6b6
    BUG: 789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 551be95ef75182e3dc5ccd3f5ef4e1601ecca605
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Nov 7 17:35:32 2017 +0530

    snapshot : fix coverity issue in glusterd-snapshot.c
    
    This patch fixes coverity issue 87 from [1].
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I5c9c67b4dd43ebf1a5a83532cbd06178000da145
    BUG: 789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 684d62276af37c260671024ce17cb281f493b289
Author: Andrea Bolognani <abologna@redhat.com>
Date:   Wed Oct 25 17:16:14 2017 +0200

    *.pc: Fix include path in Cflags
    
    The include path in glusterfs-api.pc looks like
    
      -I${includedir}/glusterfs
    
    However, client code will include the glusterfs headers using
    
      #include <glusterfs/api/glfs.h>
    
    rather than
    
      #include <api/glfs.h>
    
    which makes the "/glusterfs" part entirely unnecessary.
    
    More importantly, on some platforms such as FreeBSD, the header files
    for glusterfs will be installed in /usr/local/include, which is *not*
    part of the compiler's default include path, so compilation will fail
    with something like
    
      fatal error: 'glusterfs/api/glfs.h' file not found
      #include <glusterfs/api/glfs.h>
               ^~~~~~~~~~~~~~~~~~~~~~
    
    The fix is to simply drop the extra "/glusterfs". The same change
    is applied to other *.pc files as well, althought I haven't actually
    tested those.
    
    A test program (gfapi-load-volfile) and the glfsxmp example
    application were using the wrong include paths, so they had to be
    fixed as well.
    
    Change-Id: I9a16de47fee7ab9c12d1cb823bbe061a69352670
    BUG: 1508947
    Signed-off-by: Andrea Bolognani <abologna@redhat.com>

commit b79f29694165a65666d4177619d57b54641e4255
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Sep 12 23:01:46 2017 +0530

    xlator: add more metrics per fops
    
    Make sure to handle these counters in STACK_WIND/UNWIND macro, and
    keep the counters as part of xlator_t structure itself, to provide
    infra to monitoring.
    
    Updates #137
    
    Change-Id: Ib54d45e2321c2b095dac5810c37e6cdffe1f71b7
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit d109c7b79e15ab1940cd083636e867b1d4ed204e
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Oct 31 13:05:36 2017 +0530

    cluster/ec: UNUSED_VALUE coverity fix
    
    Problem: Return values are not used.
    
    Solution: Removed the unused values.
    
    BUG: 789278
    Change-Id: Ica2b95bb659dfc7ec5346de0996b9d2fcd340f8d
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit 96f6eb508821d20d4cc440de9da47af13ab49413
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Nov 3 15:30:51 2017 +0530

    snapshot: lvm cleanup during snapshot remove
    
    Problem : During snapshot remove lvm cleanup was skipped for deactivated
              snapshots by assuming that its mount point is not present.
    
    Fix : Do no skip lvm cleanup by checking active mount point.
    
    Change-Id: I856d2d647c75db8b37b7f430277daef6eb7580a8
    BUG: 1509254
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit ea6b6461f34332cede200cdbcba299f1de69ba12
Author: Vishal Pandey <vishpandey2014@gmail.com>
Date:   Mon Sep 25 12:14:33 2017 +0530

    features/changelog: Coverity Error Check Return
    
    If condition to check error in lseek wrapper sys_lseek.
    
    Change-Id: Ic96ddbb0898146bbfae11acc86818d6604e5eb98
    BUG: 789278
    Signed-off-by: Vishal Pandey <vishpandey2014@gmail.com>

commit 098c8031823d79096c9a8e240d36415aed178930
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Fri Nov 3 22:59:42 2017 +0530

    rpc/rpc-transport/: MISSING_BREAK in name.c
    
    Coverity ID: 286, 287, 288, 289, 290
    
    Issue: Event unterminated_case:	The case for value "27" is not
    terminated by a 'break' statement.
    
    Added Fall through in comment between switch cases.
    
    Change-Id: I9e3f205c05ac22a85a87423ef690fc18891eaece
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit a98173f51b8e90c3a0c85293375db124e853d39a
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Oct 31 12:46:53 2017 +0530

    cluster/ec: REVERSE_INULL coverity fix
    
    Problem: fop could be NULL.
    
    Solution: Check has been added to verify fop.
    
    BUG: 789278
    Change-Id: I7e8d2c1bdd8960c609aa485f180688a95606ebf7
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit b236fa1adbee104ec91b892d9a8d9ce29d5a546d
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Sat Nov 4 20:44:04 2017 +0530

    snapview: Coverity Fixes
    
    Coverity ID: 259
    Coverity ID: 163
    
    Change-Id: I7f7753b870715e1176826fb8dfbe81119750d113
    BUG: 789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 8df155bf0ff10574adbf06cc9383916a1ff4c932
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Sat Nov 4 19:48:48 2017 +0530

    cluster/dht: Check for NULL local before using it
    
    Coverity ID: 261
    Coverity ID: 257
    
    Check if local is NULL or not
    
    Change-Id: I570f87f32e1347f891c6a02ee5641fcc5a262a96
    BUG: 789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 6c8e6d0e97342dd2881d7a3f3d03aaaad44502f2
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Nov 2 17:20:29 2017 +0530

    gfapi: Fix several coverity issues in glfs-fops.c
    
    This patch fixes coverity issues 176
    
    [1] : https://download.gluster.org/pub/gluster/glusterfs/static-analysis/
    master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I473323db27218ac784b8eae773a1efe911fcfec0
    BUG: 789278
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 0e01963615a5ef510bbb806280f7590c16a2af4c
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Oct 31 15:29:30 2017 +0530

    cluster/ec: NEGATIVE_RETURNS coverity fix
    
    Problem: Source could be negative.
    
    Solution: Check has been added to verify the same.
    
    BUG: 789278
    Change-Id: I8cca6297327e7923b25949c20ec8d1a711207a76
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit 54bf1a9d46eeb5c4582977eb2bc1d4fbd4f9dd91
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Mon Nov 6 06:02:24 2017 -0800

    libglusterfs: fix (some) silliness in timer.c
    
    This addresses two issues. First is that we currently keep
    traversing the timer list even when it's no longer possible for
    us to find a timer that's ready to fire. Second is that we sleep
    a full second even when the next timer is due sooner.
    
    Change-Id: I178a460d0176dbb45f972c62ee94c6df66d92ca5
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>

commit 4b18826de7fda26b66ca3123a28830a9c8d72ec4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Nov 7 16:20:27 2017 +0530

    tests: fix spurious failure in bug-1345727-bricks-stop-on-no-quorum-validation.t
    
    Add peer_count check before checking for brick status
    
    Change-Id: I0179ec29729ab6bbc3571eb6ffd631b7b0d15f7c
    BUG: 1510415
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit f7d78e3cd3628559d0b20745bf085abf97b18160
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Oct 31 15:14:52 2017 +0530

    cluster/ec: FORWARD_NULL coverity fix
    
    Problem: xattr could be NULL.
    
    Solution: Added check to verify the same.
    
    BUG: 789278
    Change-Id: Ie013f5655f4621434e5023dd76cef44b976adc68
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit e3d5587a267106fc7fa728f29a12dc199a539202
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Thu Nov 2 09:01:48 2017 +0100

    cli: Fix several coverity issues in cli-cmd-parser.c
    
    This patch fixes coverity issues 115, 191, 274, 462, 463, 508, 588,
    612, 614, 618 and 698 from [1].
    
    Also removed the need for some relatively big arrays as local variables
    of some functions.
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I4f435dbdbedc1b6de067084cce3050b620b28391
    BUG: 789278
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit c3d7974e2be68f0fac8f54c9557d0f868e6be6c8
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Nov 7 14:00:44 2017 +0530

    protocol/server: Add an argument to rpcsvc_program_register
    
    Because of the conflicts between changes [1] and [2], a new argument
    was missed from the caller of rpcsvc_program_register.
    
    [1] : Id0a2da3632516dc1a5560dde2b151b2e5f0be8e5
    [2] : I45c3dcdbf39ec90ba39d914432d13a2ace00a5ee
    
    Change-Id: If53f755727f1bb23e0b9fb45ebf25fbc80d770a2
    BUG: 1510324
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 66d8a70c36f874debf6a460573f3b384fe19a2a3
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Thu Nov 2 17:52:08 2017 +0530

    xlators/mgmt/glusterd/: Coverity Issue MISSING_BREAK in glusterd_op_stage_rebalance
    
    Coverity ID: 297, 298
    
    Issue: Event unterminated_case
    
    Added Fall through in comment.
    
    Change-Id: Ied742e64d9741cc974906921dcca80f0b738b7d6
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit e4240431b033d1f0c351d3d874c248126ca6cadc
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Oct 10 17:13:25 2017 +0530

    rpc: bring a new protocol version
    
    * xdr: add gfid to on wire format for fsetattr/rchecksum
    * as it is change in on wire XDR format, needed backward
      compatible RPC programs.
    
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 827334
    Change-Id: Id0a2da3632516dc1a5560dde2b151b2e5f0be8e5

commit 56aef68530b3bab27730aa62e4fbc513d3dba65f
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 8 23:11:10 2017 +0530

    cli: correct rebalance status elapsed check
    
    Check that elapsed time has crossed 10 mins for at least
    one rebalance process before displaying the estimates.
    
    Change-Id: Ib357a6f0d0125a178e94ede1e31514fdc6ce3593
    BUG: 1479528
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 9a526c4faff0f96b2025dde252e3a622c1d6d188
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Mon Nov 6 15:14:24 2017 +0530

    xlators/client-rpc-fops: Fix Coverity Issues
    
    Coverity Id: 803, 804 from [1]
    
    Problem:
    USE_AFTER_FREE code at client3_3_lookup: 3371
    USE_AFTER_FREE at client3_3_readdir: 5562
    
    Solution:
    Postponed iobuf_unref(rsp_iobuf) to a location after
    all dereferences of rsp_iobuf
    
    [1]:https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I34f90d72b1248e5526ff1d2b3273cdab619cf4f8
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit 6707eddaa5d7fdce16d39c19963911868a2c7fee
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Oct 19 11:49:42 2017 +0530

    rpc: optimize fop program lookup
    
    Ensure that the fop program is the first in the program list
    so that there's minimum amount of time spent to search the
    program for the most frequently needed use case.
    
    Change-Id: I45c3dcdbf39ec90ba39d914432d13a2ace00a5ee
    BUG: 1509647
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit ed5e7b48f9255a57e0a691c102a207eb2445e8b7
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Fri Nov 3 00:02:15 2017 +0530

    xlators/mgmt/glusterd/: DEADCODE in client_graph_set_rda_options
    
    Coverity ID: 137
    
    Issue: Event dead_error_begin:	Execution cannot reach this statement:
    "set_graph_errstr(graph, "in...".
    
    Assigned return value of gf_string2bytesize_uint64 () to ret.
    
    Change-Id: Ibef1b1398b233f6442b23282f5ca205c1869a8ee
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit 125fc934e7f4c669f67e5eec5b0e3dae3a2b6d72
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 25 16:44:06 2017 +0530

    stack: change gettimeofday() to clock_gettime()
    
    For achieving the above, needed below changes too.
    
    * more sanity into how 'frame->op' is assigned.
    * infra to have 'stats' as separate section in 'xlator_t' structure
    
    Updates #137
    
    Change-Id: I36679bf9577f3ed00a695b4e7d92870dcb3db8e1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit e86d71b7b4653ddd66db7f3a16074e46ed24848f
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Oct 18 10:10:38 2017 +0530

    rpc: make actor search parallel
    
    Problem:
    On a service request, the actor is searched using an exclusive mutex
    lock which is not really necessary since most of the time the actor
    list is going to be searched and not modified.
    
    Solution:
    Use a read-write lock instead of a mutex lock.
    Only modify operations on a service need to be done under a write-lock
    which grants exclusive access to the code.
    
    Change-Id: Ia227351b3f794bd8eee70c7a76d833cc716ab113
    BUG: 1509644
    Signed-off-by: Milind Changire <mchangir@redhat.com>

commit 8aace739fd1aa1b3c1f57d08f86a6180d98f1ef1
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Thu Nov 2 17:05:31 2017 +0530

    rpc/rpc-transport/rdma/: Coverity Issue MISSING_BREAK
    
    Issue: Event unterminated_case:	The case for value "27" is not
    terminated by a 'break' statement.
    
    Function: gf_rdma_get_transport_identifiers, gf_rdma_server_get_local_sockaddr
    
    Added Fall through in comment after case AF_INET_SDP.
    
    Change-Id: Ia30d0143a63a63af2b4b1d9b02551b9260444f35
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit e994c47e3b84f0509e380190ca3487f9036858d8
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Fri Nov 3 00:38:17 2017 +0530

    xlators/client-rpc-fops: Fix Coverity Issues
    
    Coverity Id: 557,175,177,184,711,182,180,181,178 from [1]
    
    Problem:
    Unreachable code at client3_3_fgetxattr: 4771
    Unreachable code at client3_3_fxattrop: 5087
    Unreachable code at client3_3_getxattr: 4890
    Unreachable code at client3_3_lookup: 3412
    Unreachable code at client3_3_readdir: 5604
    Unreachable code at client3_3_readdirp: 5704
    Unreachable code at client3_3_xattrop: 4982
    NULL checking deref ptr at client3_3_compound: 6045
    Unused Value for op_errno at client3_3_getxattr: 4859
    
    Solution:
    Removed The Unreachable Dead Code
    Removed NULL Check of dereferenced pointer
    Removed assignment of op_errno which is overwritten
    later
    
    [1]:https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: Ie26a026dd1475c892faf00dd844bf38092e0a780
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit 2891f993ac1cee6198661682039cf499a0824f2e
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Thu Nov 2 14:57:28 2017 +0530

    server-helpers: Coverity Fix CONSTANT_EXPRESSION_RESULT in serialize_rsp_direntp
    
    Issue : "trav->dict.dict_len > 4294967295U" is always false regardless of the values
    of its operands. .But dict_serialized_length can return < 0 when error happens.
    
    Solution : Remove the comparison which always turns out to be false and add a new
    condition for error checking.
    
    Fix : The if-condition was renewed.
    
    Coverity-Id: 108 from [1]
    
    [1]: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I9956b6ca7c4bf7444f19aadd3b32fceac011a44e
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit af8604d5e9826df57aee7aba235d2e77a7e7f8fb
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Sat Nov 4 19:20:35 2017 +0530

    cluster/dht: Check for NULL before using variable
    
    Coverity ID: 245
    Check statvfs received as cbk before using it
    
    Coverity ID: 228
    Check NULL loc before freeing it.
    
    Change-Id: I1b153ed5e7b81bcf7033bf710808e95908dcfef4
    BUG: 789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit f461d75b226a5bc6c088280e43a96f9b54f33af5
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Nov 3 11:53:12 2017 +0530

    glusterd: Fix few coverity errors
    
    Fixes issues 810, 248, 491, 499, 85, 786, 811, 43, and 44
    from the report at [1].
    
    [1]: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    BUG: 789278
    Change-Id: I27ebae2ffb2256b8eef0757d768cc46e5a942e9f
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit 0f10b1a5caa78d723b3e8b879d1de162730913ce
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Nov 3 13:45:12 2017 -0400

    glusterd: Changed default op-version for some options
    
    As 3.13 is branched at a point that includes the features
    that are changed with this commit, their minimum supported
    op-versions should also change to 3.13.
    
    Change-Id: I7ef8eccc13a16f93939c1edbff9508d1e167c5e4
    BUG: 1509412
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 1160ded99bf5fcd00bd0230dfc41336af1efbe6b
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Nov 3 15:59:00 2017 +0530

    cluster/ec: Remove possibility of NULL deref
    
    Coverity ID: 237
    
    Problem: In ec_check_status we are trying to deref fop->answer
    which could be NULL.
    
    Solution: Check Null condition before using this pointer.
    
    Change-Id: I4f9a73dc2f062ca9c62b4c4baf0a6fcadade88f2
    BUG: 789278
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 0dcd5b2feeeec7c29bd2454d6ad950d094d02b0f
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Mon Oct 16 13:57:59 2017 +0200

    cluster/ec: create eager-lock option for non-regular files
    
    A new option is added to allow independent configuration of eager
    locking for regular files and non-regular files.
    
    Change-Id: I8f80e46d36d8551011132b15c0fac549b7fb1c60
    BUG: 1502610
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 337b5580aa8872a69631f8af17e1add7bb2a901d
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Thu Nov 2 15:23:22 2017 +0530

    xlators/bd-helper: Coverity Fix CHECKED_RETURN in bd_do_ioctl_zerofill
    
    Problem: bd_do_ioctl_zerofill is called and return value is unchecked
    
    Fix: Check the returned value and goto skip if the returned value < 0
    which means its an error.
    
    Coverity Id: 67 from [1]
    
    [1]: https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I398873cefaca03f9cd188fa0f4ccba1378a60ed9
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit 498f8b8c26173a04cf085fbfa56cdb719b46b33c
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Nov 1 19:00:09 2017 +0530

    glusterd: coverity fixes
    
    This patch fixes coverity issue 780, 88, 692, 747, 357
    
    Change-Id: I44b0fe9119853a6d2210507c7247e168d7c3ae0a
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 782f6a5d6035ed282ffe4b3e1d38bfa4c771aca9
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Fri Nov 3 00:41:24 2017 +0530

    xlators/performance/io-cache/: DEADCODE in ioc_open_cbk
    
    Coverity ID: 173
    
    Issue: Event dead_error_line: Execution cannot reach this statement:
    "fd_ctx_set(fd, this, 1UL);".
    
    Removed if block as "weight == 0U" cannot be true, so if block will
    never execute. Also removed weight variable because it is unused.
    
    Change-Id: I4f028df29bfde91167fb15befa99b1fe1892adc6
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit 55071ba2ce8e8c978d938bde0a1fcb16cea695c6
Author: ShyamsundarR <srangana@redhat.com>
Date:   Thu Nov 2 12:35:53 2017 -0400

    doc: Updating MAINTAINERS to reflect gNFS maintainership
    
    Facebook has offered to take up maintaining gNFS going
    forward. This change reflects the same in the MAINTAINERS
    file.
    
    Change-Id: I58dde9c833a9465d6e563f1355e4725021f5055c
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 2ef2b600b98d029983bc2eb3b173d0bd201916b4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Nov 1 12:14:36 2017 +0530

    glusterd/mgmt: coverity fixes
    
    This patch fixes coverity issues 179, 59.
    
    Problem: control flow won't enter into if block as volname is always
    NULL and return value of function synctask_barrier_init is unchecked.
    
    Fix: remove condition checking which is always resulting in false,
    and removing if block which is always unreachable. As a result of
    removal of condition checking volname became a unused variable,
    so remove declaration of volname.
    
    assign return valur of synctask_barrier_init to ret, if it nonzero
    value goto out.
    
    Change-Id: I870aeb020034e97a761e9314f7ace7573f7c520c
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit bf5c5841c443a8da5b8f73c27b2ed83420f2303e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 18 23:03:32 2017 +0530

    global options: add a sample option to handle
    
    Fixes #303
    
    Change-Id: Icdaa804711c43c65b9684f2649437aae1b5c1ed5
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit cf62283467d7dd30b89b80717f1fbc24670cb44b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Sep 12 22:07:10 2017 +0530

    Add framework for global xlator in graph
    
    Updates #303
    
    Change-Id: Id0b9050c93ea87532dc80b4fda650c5663d285bd
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 9424a9fcc9f670766b7557230648e57123edd600
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Thu Nov 2 10:36:36 2017 +0100

    cli: Fix several coverity issues in cli-cmd-volume.c
    
    This patch fixes issues 133, 486, 487 and 691 from [1]
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I1a6ca4870ac105ea4c634fc18293229a56ab8596
    BUG: 789278
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 8e973d3ab96d290a32ae3fdbdd1cf867b7060483
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Tue Oct 31 09:56:11 2017 -0700

    core: make gf_boolean_t a C99 bool instead of an enum
    
    This reduces the space used from four bytes to one, and allows
    new code to use familiar C99 types/values interoperably with our
    old cruft. It does *not* change current declarations or code;
    that will be left for a separate - much larger - patch.
    
    Updates: #80
    
    Change-Id: I5baedd17d3fb05b38f0d8b8bb9dd62824475842e
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>

commit 917f84b01ff4c485ce548f0daa3d3d51dc81c195
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Thu Nov 2 09:37:44 2017 +0100

    cli: Fixed coverity issue in cli-cmd-snapshot.c
    
    This patch fixes issue 132 from [1].
    
    [1] https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-10-30-9aa574a5/html/
    
    Change-Id: I50952614e7edb6dbb1ec70383f1dc58ce1738c2f
    BUG: 789278
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit 89dc54f50c9f800ca4446ea8fe736e4860588845
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 1 16:58:27 2017 +0530

    cli: gluster help changes
    
    gluster cli help now shows only the top level
    help commands. gluster <component> help will now show
    help commands for <component>.
    
    Change-Id: I263f53a0870d80ef4cfaad455fdaa47e2ac4423b
    BUG: 1474768
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit f9eedcad0127705c685e8b192726e46b170f00d1
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Nov 1 17:36:10 2017 +0530

    glusterd: UNUSED VALUE coverity fix
    
    ret is overwritten before it is used, adding a line for checking
    its value solves it.
    
    Change-Id: I4ac4ad33bc236d9294da64b19d16b3bc9bb8807b
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 84f4f68bfafd3f7fc14a1e83e0272579e5cc1519
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Oct 31 17:09:45 2017 +0530

    heal: Fix coverity errors
    
    Change-Id: Idbebfc2e4cfa739a87ccaabbc6e2088362b6bbc1
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit ac0d539f84f12871695c4e0aa2f0f7867d6ecb77
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Nov 2 01:40:00 2017 +0530

    glusterd: PW.INCLUDE_RECURSION coverity fix
    
    Problem: #include file "glusterd.h" includes itself,
    glusterd.h -> glusterd-pmap.h -> glusterd.h
    
    Fix: remove inclusion statement
    
    Change-Id: I28f2043a73a50ae2c7b670e2dece4a3f3fffbcd6
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 3e10ac08c5273980c3a144f681f9a96dffcbcb77
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Thu Nov 2 00:39:28 2017 +0530

    glusterd/pmap: UNUSED VALUE coverity fix
    
    Problem: port value is assigned to p, which is overwritten before
    using it.
    
    Fix: remaoval of assignment line.
    
    Change-Id: If007167f37b0325c7bfe12f8e9075ca68524e40a
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 5424c63fe146e42cfc9be45b0b9830bcc948b7aa
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 14 13:43:58 2017 -0400

    xlator/tier: flood of -Wformat-truncation warnings with gcc-7.1
    
    Starting in Fedora 26 which has gcc-7.1.x, -Wformat-trunction is enabled
    with -Wformat, resulting in a flood of new warnings. This many warnings
    is a concern because it makes it hard(er) to see other warnings that
    should be addressed.
    
    An example is at
    https://kojipkgs.fedoraproject.org//packages/glusterfs/3.12.0/1.fc28/data/logs/x86_64/build.log
    
    For more info see https://review.gluster.org/#/c/18267/
    
    Change-Id: Id7ef8e0dedd28ada55f72c03d91facbe1c9888bd
    BUG: 1492849
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 4a53ed72478c3ce788e295223d45cb578949241e
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Wed Jun 8 11:53:59 2016 -0700

    nfs: Fix crash bug when mnt3_resolve_subdir_cbk() fails
    
    Summary:
    When mnt3_resolve_subdir_cbk() fails (this can happen when racing
    operations), authorized_path is sometimes NULL. We try to run strlen()
    on this path and as a result we crash. This diff fixes that by checking
    if path is NULL before dereferencing it.
    
    Test Plan: Run with patch and observe that there is no crash. Prove test
    for auth code.
    
    BUG: 1365683
    Change-Id: I2e2bdfdc61ae906788611e151d2c753b79b312df
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>

commit f6983f825f10f1795118ca140fd32e9c280bb5a4
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Oct 31 15:36:02 2017 +0530

    cluster/ec: FORWARD_NULL coverity fix
    
    Problem: frame could be NULL.
    
    Solution: Added check to verify frame.
    
    BUG: 789278
    Change-Id: I55a64c936ae71ec8587a3f9dfa0fdee5d0ea5213
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit afa8df9ee249fac2a20f3d367dcadcee1451184e
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Oct 31 12:37:37 2017 +0530

    cluster/ec: FORWARD_NULL coverity fix
    
    Problem: cbk could be NULL.
    
    Solution: Assigned appropriate value to cbk.
    
    BUG: 789278
    Change-Id: I2e4bba9a54f965c6a7bccf0b0cb6c5f75399f6e6
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit 82be66ef8e9e3127d41a4c843daf74c1d8aec4aa
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Oct 26 14:26:30 2017 +0530

    glusterd: fix brick restart parallelism
    
    glusterd's brick restart logic is not always sequential as there is
    atleast three different ways how the bricks are restarted.
    1. through friend-sm and glusterd_spawn_daemons ()
    2. through friend-sm and handling volume quorum action
    3. through friend handshaking when there is a mimatch on quorum on
    friend import.
    
    In a brick multiplexing setup, glusterd ended up trying to spawn the
    same brick process couple of times as almost in fraction of milliseconds
    two threads hit glusterd_brick_start () because of which glusterd didn't
    have any choice of rejecting any one of them as for both the case brick
    start criteria met.
    
    As a solution, it'd be better to control this madness by two different
    flags, one is a boolean called start_triggered which indicates a brick
    start has been triggered and it continues to be true till a brick dies
    or killed, the second is a mutex lock to ensure for a particular brick
    we don't end up getting into glusterd_brick_start () more than once at
    same point of time.
    
    Change-Id: I292f1e58d6971e111725e1baea1fe98b890b43e2
    BUG: 1506513
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit bb7fd73ce4245f54517de1f378a9471f6c8bb454
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Oct 31 14:56:40 2017 +0530

    cluster/ec: MISSING_BREAK coverity fix
    
    Problem: switch case syntax issue.
    
    Solution: syntax fixed.
    
    BUG: 789278
    Change-Id: I76da72c3ab6ffc5db671686a71d6a596beaf496e
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit fd397e59d8856e4d5f1ccbec1baaedb71623951e
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Tue Oct 31 11:24:04 2017 +0530

    snapshot: fix coverity issue 'DEADCODE'
    
    Problem : Unreachable code at glusterd-snapshot.c:6718
              Unreachable code at glusterd-snapshot.c:7352
    
    FIx : Remove unreachable code
    
    At glusterd-snapshot.c:6718 in if condition the value of "snap" must be "NULL"
    to call glusterd_snap_remove() which is not possible here.
    
    Change-Id: Id865bde7c1474a9b9ed11c0ed614676b4e2443c6
    BUG: 789278
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 08000e3ab7effa2f09ba3f0334285c7ef7d2daab
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Oct 25 12:21:12 2017 +0530

    extras/hooks: Honour all input arguments to scripts
    
    Some of the hook scripts were not honouring the arguments with which
    they are invoked during various volume operations. So make sure that
    we consider everything while parsing the command line arguments to
    avoid following warnings:
    
    . . .
    ame: unrecognized option '--first=no'
    ame: unrecognized option '--version=1'
    ame: unrecognized option '--volume-op=start'
    . . .
    
    Change-Id: I5b08e5e7f32908c8509e97098a042096b507783e
    BUG: 1503983
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 0fb8acaa6ff80c43e46deac0ce66b29ae0df0ca4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Oct 30 15:55:32 2017 +0530

    glusterd: delete source brick only once in reset-brick commit force
    
    While stopping the brick which is to be reset and replaced delete_brick
    flag was passed as true which resulted glusterd to free up to source
    brick before the actual operation. This results commit force to fail
    failing to find the source brickinfo.
    
    Change-Id: I1aa7508eff7cc9c9b5d6f5163f3bb92736d6df44
    BUG: 1507466
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 1d92d5173b1c9e5cda60fe5c5a237fc4b82df030
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Mon Sep 25 01:03:09 2017 +0530

    Xlators/features: Coverity Issue "NEGATIVE_RETURNS" in worm_truncate,worm_ftruncate,worm_link,worn_unlink and worm_rename.
    
    Issue :Event negative_returns: 	"op_errno" is passed to a parameter
    that cannot be negative.
    
    Fix : In functions worm_link,worm_unlink,worm_truncate,worm_ftruncate
    and worm_rename, added an condition to check the whether value
    of "op_errno" is negative or not.If the value is negative, then
    it is set to EROFS.
    
    Change-Id: Ie65601b6cc9799f587cc574408281dab50a58afb
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit f4805ca6cf67d1d8394b14f21eceb2d9592ba228
Author: Rishabh Dave <rishabhddave@gmail.com>
Date:   Sun Oct 15 18:41:10 2017 +0530

    snapshot/scheduler: handle the exception when SELinux is absent
    
    When SELinux is absent on an given system, snapshot_scheduler.py raises
    an exception; handle it and report it in the log.
    
    Change-Id: I21bc179e090d34f8061063e6d662521ee5046cce
    BUG: 1502253
    Signed-off-by: Rishabh Dave <rishabhddave@gmail.com>

commit c0e77f643930499966554cd849a40580e4ff68f9
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Sep 22 16:43:39 2017 +0530

    gfapi: Register/Unregister Upcall events' callback
    
    Polling continuously for upcall events is not optimal.
    Hence new APIs have been added to allow applications to
    register and unregister upcall events it is interested in
    along with callback function to be invoked in case of any
    such upcalls sent by backend server.
    
    @TODO: Make changes in upcall xlator so that events are
    sent to only those clients which either registered callbacks
    or started polling. Shall be addressed in separate patch.
    
    Updates: #315
    
    Change-Id: I40473fd5cf689172ff2d7bb2869756b7fd5bc761
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 4216869c724cf19c12d63c0580de88e9427e6467
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Oct 17 12:50:48 2017 +0530

    eventsapi: HTTPS support for Webhooks
    
    First it tries to call URL with verify=True without specifying the cert
    path, it succeeds if a webhook is HTTP or HTTPS with CA trusted
    certificates(for example https://github..).
    
    If above call fails with SSL error then it tries to get the server
    certificate and calls URL again. If call fails with SSL error even after
    using the certificate, then verification will be disabled and logged in
    the log file.
    
    All other errors will be catched and logged as usual.
    
    BUG: 1506903
    Change-Id: I86a3390ed48b75dffdc7848022af23a1e1d7f076
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 30e0b86aae00430823f2523c6efa3c4ebbf0a478
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Oct 17 21:32:44 2017 +0530

    glusterd: clean up portmap on brick disconnect
    
    GlusterD's portmap entry for a brick is cleaned up when a PMAP_SIGNOUT event is
    initiated by the brick process at the shutdown. But if the brick process crashes
    or gets killed through SIGKILL then this event is not initiated and glusterd
    ends up with a stale port. Since GlusterD's portmap traversal happens both ways,
    forward for allocation and backward for registry search, there is a possibility
    that glusterd might end up running with a stale port for a brick which
    eventually will end up with clients to fail to connect to the bricks.
    
    Solution is to clean up the port entry in case the process is down as
    part of the brick disconnect event. Although with this the handling
    PMAP_SIGNOUT event becomes redundant in most of the cases, but this is
    the safeguard method to avoid glusterd getting into the stale port
    issues.
    
    Change-Id: I04c5be6d11e772ee4de16caf56dbb37d5c944303
    BUG: 1503246
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 15fe99995b8650a677b097028bc14d61a5dd5e1b
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Fri Oct 27 16:04:46 2017 +0530

    glusterd: persist brickinfo's port change into glusterd's store
    
    Problem:
    Consider a case where node reboot is performed and prior to reboot
    brick was listening to 49153. Post reboot glusterd assigned 49152
    to brick and started the brick process but the new port was never
    persisted. Now when glusterd restarts glusterd always read the port
    from its persisted store i.e 49153 however pmap signin happens with
    the correct port i.e 49152.
    
    Fix:
    Make sure when glusterd_brick_start is called, glusterd_store_volinfo is
    eventually invoked.
    
    Change-Id: Ic0efbd48c51d39729ed951a42922d0e59f7115a1
    BUG: 1506589
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>

commit 4edea128916eb76ec94fde90407eb70af6493337
Author: Vishal Pandey <vishpandey2014@gmail.com>
Date:   Tue Oct 24 14:26:45 2017 +0530

    write once read many: file appendable in worm state
    
    Issue:
    A new file is appendable even when file level worm is 1.
    
    Fix:
    Do a state transition in writev function in worm.c file.
    
    Steps To Test:
    1- Activate file level worm.
    2- Create a new file.
    3- Leave file dormant for auto commit period.
    4- Try and append some content to the file.
    5- check the file if new content has been appended or not.
    6- check if file has been transitioned to Worm Retention state.
    
    Change-Id: I52d50ad888cb0c39ad54be9352ccb07d48b8d71a
    BUG: 1505807
    Signed-off-by: Vishal Pandey <vishpandey2014@gmail.com>

commit 933ec57ccda2c1ba5ce6f207313c3b6802e67ca3
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Oct 18 16:43:16 2017 +0530

    cluster/afr: Honor default timeout of 5min for analyzing split-brain files
    
    Problem:
    After setting split-brain-choice option to analyze the file to resolve
    the split brain using the command
    "setfattr -n replica.split-brain-choice -v "choiceX" <path-to-file>"
    should allow to access the file from mount for default timeout of 5mins.
    But the timeout was not honored and was able to access the file even after
    the timeout.
    
    Fix:
    Call the inode_invalidate() in afr_set_split_brain_choice_cbk() so that
    it will triger the cache invalidate after resetting the timer and the
    split brain choice. So the next calls to access the file will fail with EIO.
    
    Change-Id: I698cb833676b22ff3e4c6daf8b883a0958f51a64
    BUG: 1503519
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit a320f2021ee4dcab85483dbe10d85e797bd6b3b4
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sat Jul 15 17:55:14 2017 +0530

    posix:  Ignore disk space reserve check for internal FOPS
    
    Problem: Currently disk space reserve check is applicable for internal FOP
             also it needs to be ignore for internal FOP.
    
    Solution: Update the DISK_SPACE_CHECK_AND_GOTO macro at posix component.
              Macro will call only while key "GLUSTERFS_INTERNAL_FOP_KEY"
              exists in xdata.
    
    BUG: 1506083
    Change-Id: I2b0840bbf4fa14bc247855b024ca136773d68d16
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit ae9b006f23b1408ff548348440369d056becdc1d
Author: Günther Deschner <gd@samba.org>
Date:   Tue Jul 25 11:54:09 2017 +0200

    md-cache: Add additional samba and macOS specific EAs to mdcache
    
    Samba ships with a server implementation of the Apple Create Context
    extension (AAPL) as negotiated by all modern Apple clients. With the
    support of the AAPL extension, Apple clients will integrate better with
    Samba servers. The AAPL implementation itself is contained in the Samba
    vfs_fruit(8) module which has to be activated in Samba. This vfs_fruit
    module also provides support for macOS alternate data streams which will
    be represented in EAs. Two standard data streams ("AFP_AfpInfo" and
    "AFP_Resource") will be stored in the following EAs:
    
    * user.org.netatalk.Metadata
    * user.org.netatalk.ResourceFork
    
    For all other data streams, vfs_fruit relies on another Samba vfs
    module, vfs_streams_xattr(8), to handle these. Although configurable, by
    default the vfs_streams_xattr module will build EA keynames with a
    "user.DosStream." prefix. Please note that we have to deal with only one
    known prefix key, as macOS will happily compose EA keynames like:
    
    * user.DosStream.com.apple.diskimages.fsck:$DATA
    * user.DosStream.com.apple.diskimages.recentcksum:$DATA
    * user.DosStream.com.apple.metadata:kMDItemWhereFroms:$DATA
    * user.DosStream.com.apple.quarantine:$DATA
    * etc.
    
    Caching of vfs_fruit specific EAs is crucial for SMB performance and is
    controlled with the same configuration option
    "performance.cache-samba-metadata".
    
    Guenther
    
    Change-Id: Ia7aa341234dc13e1c0057f3d658b7ef711b5d31e
    BUG: 1499933
    Signed-off-by: Guenther Deschner <gd@samba.org>

commit 62dbefde4bc5c8d9dcfb10f3be5d349db341bb30
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Oct 23 12:42:32 2017 +0530

    tests: Update tier CLI in .t files
    
    Update .t tier tests to use the new tier CLI.
    
    Change-Id: I0e7f1769071108d8266fc86378c4466bcaf96e7d
    BUG: 1505253
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit 39ac511a5d6dbc141bb3e1d8b4b4b8922c71b5a4
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Oct 19 13:40:35 2017 +0530

    extras/hooks: Fix getopt usage
    
    `getopt` does not have an optional argument as '-name'. It should
    be either '-n' or '--name'(see man getopt(1)). This wrong usage
    resulted in setting the script name as 'ame' instead of $PROGNAME
    in most of the hook-scripts.
    
    Additionally the following line from DESCRIPTION given for `getopt`
    shell command expects short options for almost every kind of usage
    mentioned in SYNOPSIS:
    
    . . .
    If  no  '-o'  or '--options' option is found in the first part, the
    first parameter of the second part is used as the short options string.
    . . .
    
    Refer http://man7.org/linux/man-pages/man1/getopt.1.html for more
    clarity on its usage.
    
    Change-Id: I95baf5fa8c99025e66b2d83656dd838d4f6048ce
    BUG: 1503983
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 9aa574a51b84717c1f3949ed2e28a49e49840a93
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Oct 22 12:41:38 2017 +0530

    protocol/client: handle the subdir handshake properly for add-brick
    
    There should be different way we handle handshake in case of subdir
    mount for the first time, and in case of subsequent graph changes.
    
    Change-Id: I2a7ba836433bb0a0f4a861809e2bb0d7fbc4da54
    BUG: 1505323
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 786343abca3474ff01aa1017210112d97cbc4843
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Sep 4 16:57:25 2017 +0530

    cluster/afr: Fail open on split-brain
    
    Problem:
    Append on a file with split-brain succeeds. Open is intercepted by open-behind,
    when write comes on the file, open-behind does open+write. Open succeeds
    because afr doesn't fail it. Then write succeeds because write-behind
    intercepts it. Flush is also intercepted by write-behind, so the application
    never gets to know that the write failed.
    
    Fix:
    Fail open on split-brain, so that when open-behind does open+write open fails
    which leads to write failure. Application will know about this failure.
    
    Change-Id: I4bff1c747c97bb2925d6987f4ced5f1ce75dbc15
    BUG: 1294051
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 0bb928264a9fb100dc927687eed6ad4d22675950
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Oct 25 14:36:35 2017 +0200

    Make sure attach_brick return a proper error code
    
    Coverity warn about "Using uninitialized value "ret".", which is
    indeed the case. If we can't attach after 15 tries, attach_brick
    return uninitiliazed return code, which is likely hard to trigger,
    but bad.
    
    I use -1 to follow the UNIX convetion, but there is no specific error
    code tested by code.
    
    Change-Id: I43ad60d25ab169f9cea0db600805ced7f77c37ba
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>

commit 63160cb952fe7716a3313ce5ee32f890fe4d7a0c
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Wed Jun 14 16:28:40 2017 +0530

    cluster/ec: Implement DISCARD FOP for EC
    
    Updates #254
    
    This code change implements DISCARD FOP support for
    EC.
    
    BUG: 1461018
    Change-Id: I09a9cb2aa9d91ec27add4f422dc9074af5b8b2db
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit 2ade36cd98ea0f5bd2a8f619a19c20438318afaf
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Oct 23 21:17:52 2017 +0200

    protocol/server: fix the comparision logic in case of subdir mount
    
    without the fix, the stat entry on a file would return inode==1 for
    many files, in case of subdir mount
    
    This happened with the confusion of return value of 'gf_uuid_compare()',
    it is more like strcmp, instead of a gf_boolean return value, and hence
    resulted in the bug.
    
    Change-Id: I31b8cbd95eaa3af5ff916a969458e8e4020c86bb
    BUG: 1505527
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit a39f5d62f737d7a3241f2adaff064b8d92f0d3ea
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Tue Oct 24 11:47:46 2017 +0530

    cli: volume status command is missing in man page
    
    Problem: volume status command is missing gluster manual page.
    
    Fix: Adding volume status command to manual page.
    
    Change-Id: Ifef18ff3721bc85636a9e7707c50bee2bf9d4a9b
    BUG: 1505663
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit a8e16c81e3d14b577ac738574e19a16543df419e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jun 25 16:34:01 2017 +0530

    cluster/ec: Allow parallel writes in EC if possible
    
    Problem:
    Ec at the moment sends one modification fop after another, so if some of
    the disks become slow, for a while then the wait time for the writes that
    are waiting in the queue becomes really bad.
    
    Fix:
    Allow parallel writes when possible. For this we need to make 3 changes.
    1) Each fop now has range parameters they will be updating.
    2) Xattrop is changed to handle parallel xattrop requests where some
       would be modifying just dirty xattr.
    3) Fops that refer to size now take locks and update the locks.
    
    Fixes #251
    Change-Id: Ibc3c15372f91bbd6fb617f0d99399b3149fa64b2
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 1260ee53b1674234e6f083563bdcd258e46a6faa
Author: Kevin Vigor <kvigor@fb.com>
Date:   Fri Apr 28 16:44:29 2017 -0700

    gluster: IPv6 single stack support
    
    Summary:
    - This diff changes all locations in the code to prefer inet6 family
      instead of inet.  This will allow change GlusterFS to operate
      via IPv6 instead of IPv4 for all internal operations while still
      being able to serve (FUSE or NFS) clients via IPv4.
    - The changes apply to NFS as well.
    - This diff ports D1892990, D1897341 & D1896522 to the 3.8 branch.
    
    Test Plan: Prove tests!
    
    Reviewers: dph, rwareing
    
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    
    Change-Id: I34fdaaeb33c194782255625e00616faf75d60c33
    BUG: 1406898
    Reviewed-on-3.8-fb: http://review.gluster.org/16059
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    Tested-by: Shreyas Siravara <sshreyas@fb.com>

commit 738c38f0efa7b4d4dab0cf23d00589d68e4eb88d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Oct 23 06:46:49 2017 -0400

    libgfchangelog: Fix possible null pointer dereference
    
    If pthread_attr_init fails, gf_msg uses this->name
    where 'this' is not initialized yet. This patch fixes
    the same.
    
    Change-Id: Ie004cbe1015a0d62fc3b5512e8954c5606eeeb5f
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    BUG: 1505325

commit 2b3b3edee2d849b4aee314048987dc995d9679a1
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Wed Aug 16 14:04:45 2017 +0530

    snapshot: Issue with other processes accessing the mounted brick
    
    Added code for unmount of activated snapshot brick during snapshot
    deactivation process which make sense as mount point for deactivated
    bricks should not exist.
    
    Removed code for mounting newly created snapshot, as newly created
    snapshots should not mount until it is activated.
    
    Added code for mount point creation and snapshot mount during snapshot
    activation.
    
    Added validation during glusterd init for mounting only those snapshot
    whose status is either STARTED or RESTORED.
    
    During snapshot restore, mount point for stopped snap should exist as
    it is required to set extended attribute.
    
    During handshake, after getting updates from friend mount point for
    activated snapshot should exist and should not for deactivated
    snapshot.
    
    While getting snap status we should show relevent information for
    deactivated snapshots, after this pathch 'gluster snap status' command
    will show output like-
    
    Snap Name : snap1
    Snap UUID : snap-uuid
    
    	Brick Path        :   server1:/run/gluster/snaps/snap-vol-name/brick
    	Volume Group      :   N/A (Deactivated Snapshot)
    	Brick Running     :   No
    	Brick PID         :   N/A
    	Data Percentage   :   N/A
    	LV Size           :   N/A
    
    Fixes: #276
    
    Change-Id: I65783488e35fac43632615ce1b8ff7b8e84834dc
    BUG: 1482023
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>

commit 87bd25b64ae34cce95e87e724acfeab4c13d60a4
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Oct 18 08:06:24 2017 +0530

    glusterfsd: Dereferencing the null pointer
    
    Problem: When control reaches to out, one of (iobref, iobuf, frame) can
    be null.for iobref, iobuf iobref_unref() and iobuf_unref() functions
    are called respectively, which are using GF_VALIDATE_OR_GOTO(), so
    there won't be null pointer dereference. But for frame without null
    checking STACK_DESTROY(frame->root) is called causing null pointer
    dereference.
    
    Fix: adding a line for null checking, the function
    STACK_DESTROY(frame->root) is called only when frame is not null.
    
    Change-Id: I3a6684c11fb7b694b81d6ad4fec3bced5562ad88
    BUG: 1503394
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 087703fae449b725ebd82bc3cd65763a016fb098
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Oct 11 13:29:13 2017 +0530

    extras/hooks: Fix errors reported via shellcheck utility
    
    Change-Id: I217c6b2a39955f1709bb3452b00d33c2dcb60faa
    BUG: 1500649
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit f0650fef60ca557ea1c60458f705ac9b52854b39
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Oct 18 06:23:56 2017 -0400

    doc: Add missing option for bitrot scrub-frequency
    
    The option 'hourly' is supported for 'scrub-frequency'
    but man page was not reflecting it. Fixed the same.
    
    Change-Id: Ida0929c805f6f5332c5dcd94cda9ecf2f4eee20e
    BUG: 1503510
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit c0b08f10ed07bfe06309e31a7fff85cadb733ce2
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Wed Oct 18 11:40:59 2017 +0530

    glusterd: documenting server.allow-insecure
    
    problem: "server.allow-insecure" is invisible in gluster volume set
    help.
    
    Fix: "server.allow-insecure" is defined as NO_DOC type, chainging
    it to DOC type solve the problem.
    
    Change-Id: I327f1e4c1684ff846deb8b7df07d4d8a09073274
    BUG: 1503424
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 77271e9c1efab628d00bc66803be923f451c0bfa
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Oct 10 14:45:03 2017 +0530

    gfproxyd: Let glusterd manage gfproxy daemon
    
    Updates: #242
    BUG: 1428063
    Change-Id: Iaaf2edf99b2ecc75f6d30762c752a6d445c1c826
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit e848410ab6d13871be6b57101788ea5183efe75c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Oct 13 11:46:38 2017 +0530

    stack.h: make sure 'oldgroups' is never null
    
    If 'oldgroups' is null, it can lead to a crash.
    
    Change-Id: I7a4f71256b07dc0ca3b988cad3694c21b150c99e
    BUG: 789278
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 614904fa7a31bf6f69074238b7e710a20e05e1bb
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Thu Oct 5 23:44:46 2017 +0530

    glusterd : introduce timer in mgmt_v3_lock
    
    Problem:
    In a multinode environment, if two of the op-sm transactions
    are initiated on one of the receiver nodes at the same time,
    there might be a possibility that glusterd  may end up in
    stale lock.
    
    Solution:
    During mgmt_v3_lock a registration is made to  gf_timer_call_after
    which release the lock after certain period of time
    
    Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
    BUG: 1499004
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>

commit 05b9dce1b503ab10efdb79a870b07d982cb5a823
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Oct 13 20:15:55 2017 +0530

    gfapi: update symbol version of glfd_set_lk_owner to 3.10.7
    
    To be able to backport the API glfd_set_lk_owner() to
    existing stable (3.10, 3.12) releases, change its symbol
    version to 3.10.7 (upcoming 3.10 release).
    
    Also sticking to the norms of the gfapi library, changing
    the routine name to glfs_fd_set_lkowner()
    
    BUG: 1499641
    Change-Id: I43d002a24f493770a3daa774dbda2b7ea6d49e37
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit 4f3c680ed8350496e18de127064be816388dafdd
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Oct 17 10:57:13 2017 +0530

    worm/read-only: Add sentinel NULL key to options
    
    BUG: 1193929
    Change-Id: Ibfee382362826556e2e760f9b946c83445d6a08e
    Signed-off-by: Prashanth Pai <ppai@redhat.com>

commit fb4b914ce84bc83a5f418719c5ba7c25689a9251
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Oct 13 20:00:47 2017 +0530

    mount/fuse: never fail open(dir) with ENOENT
    
    open(dir) being an operation on inode should never fail with
    ENOENT. If gfid is not present, the appropriate error is ESTALE. This
    will enable kernel to retry open after a revalidate lookup.
    
    Change-Id: I8d07d2ebb5a0da6c3ea478317442cb42f1797a4b
    BUG: 1500269
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 019a55e708375d2b1e576fcc948a691bcdc5c749
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Oct 10 11:29:04 2017 +0530

    Revert "mount/fuse: report ESTALE as ENOENT"
    
    This reverts commit 26d16b90ec7f8acbe07e56e8fe1baf9c9fa1519e.
    
    Consider rename (index.new, store.idx) and open (store.idx) being
    executed in parallel. When we break down operations following sequence
    is possible.
    
    * lookup (store.idx) - as part of open(store.idx) returns gfid1 as the
      result.
    * rename (index.new, store.idx) changes gfid of store.idx to
      gfid2. Note that gfid2 was the nodeid of index.new. Since rename is
      successful, gfid2 is associated with store.idx.
    * open (store.idx) resumes and issues open fop to glusterfs with
      gfid1. open in glusterfs fails as gfid1 doesn't exist and the error
      returned by glusterfs to kernel-fuse is ENOENT.
    * kernel passes back the same error to application as a result to
      open.
    
    This error could've been prevented if kernel retries open with
    gfid2. Interestingly kernel do retry open when it receives ESTALE
    error. Even though failure to find gfid resulted in ESTALE error,
    commit 26d16b90ec7f8acb converted that error to ENOENT while sending
    an error reply to kernel. This prevented kernel from retrying open
    resulting in error.
    
    Change-Id: I2e752ca60dd8af1b989dd1d29c7b002ee58440b4
    BUG: 1500269
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>

commit 09f6ae2111779c085fd108436cbc56615ef5f3df
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Thu Jun 29 07:00:41 2017 -0700

    project: update coding standard
    
    Change-Id: I1d389c8d97ec1491be675bea2ff90898f1209861
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>

commit 206120126d455417a81a48ae473d49be337e9463
Author: Zhang Huan <zhanghuan@open-fs.com>
Date:   Tue Sep 5 11:36:25 2017 +0800

    cluster/dht: fix crash when deleting directories
    
    In DHT, after locks on all subvolumes are acquired, it would perform the
    following steps sequentially,
    1. send remove dir on all other subvolumes except the hashed one in a loop;
    2. wait for all pending rmdir to be done
    3. remove dir on the hashed subvolume
    
    The problem is that in step 1 there is a check to skip hashed subvolume
    in the loop. If the last subvolume to check is actually the
    hashed one, and step 3 is quickly done before the last and hashed
    subvolume is checked, by accessing shared context data be destroyed in
    step 3, would cause a crash.
    
    Fix by saving shared data in a local variable to access later in the
    loop.
    
    Change-Id: I8db7cf7cb262d74efcb58eb00f02ea37df4be4e2
    BUG: 1490642
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>

commit 117c4560dcd5c7499c17a0bc8e62c62ac39745e1
Author: Kamal Mohanan <kmohanan@redhat.com>
Date:   Mon Sep 25 11:36:54 2017 +0530

    cluster/ec: Coverity Fix UNUSED_VALUE in ec_create_name
    
    Problem: The value returned by cluster_mkdir is assigned to ret at
    ec-heal.c:1076. But this value is overwritten before it can be
    used.
    
    Solution: The return value of cluster_mkdir is ignored. It is not
    assigned to ret.
    
    Change-Id: Iee6b8d8b04e0bd800dd30d2c24cab755b9e63443
    BUG: 789278
    Signed-off-by: Kamal Mohanan <kmohanan@redhat.com>

commit d88be3bc29dbd1eaa393802f3c98e188fe5287c8
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Jul 31 12:45:21 2017 +0530

    cluster/ec: Improve heal info command to handle obvious cases
    
    Problem:
    1 - If a brick is down and we see an index entry in
    .glusterfs/indices, we should show it in heal info
    output as it most certainly needs heal.
    
    2 - The first problem is also not getting handled after
    ec_heal_inspect. Even if in ec_heal_inspect, lookup will
    mark need_heal as true, we don't handle it properly in
    ec_get_heal_info and continue with locked inspect which
    takes lot of time.
    
    Solution:
    1 - In first case we need not to do any further invstigation.
    As soon as we see that a brick is down, we should say that
    this index entry needs heal for sure.
    
    2 - In second case, if we have need_heal as _gf_true after
    ec_heal_inspect, we should show it as heal requires.
    
    Change-Id: Ibe7f9d7602cc0b382ba53bddaf75a2a2c3326aa6
    BUG: 1476668
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>

commit 067f38063e13fc75d4e3f7adf93441d15099c557
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Oct 12 14:31:14 2017 +0530

    mount/fuse : Fix parsing of vol_id for snapshot volume
    
    For supporting sub-dir mount, we changed the volid. Which means anything
    after a '/' in volume_id will be considered as sub-dir path.
    
    But snapshot volume has vol_id stracture of /snaps/<volname>/<snapname>
    which has to be considered as during the parsing.
    
    Note 1: sub-dir mount is not supported on snapshot volume
    Note 2: With sub-dir mount changes brick based mount for quota cannot be
            executed via mount command. It has to be a direct call via glusterfs
    
    Change-Id: I0d824de0236b803db8a918f683dabb0cb523cb04
    BUG: 1501235
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>

commit 68d80f44a3a33050241b025476c8e171018f0edf
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 4 14:22:05 2017 -0400

    packaging: manual systemctl daemon reload required after install
    
    Use the %systemd_{post,preun,postun_with_restart} macros provided.
    
    Previous fix failed to build on koji Fedora 27 and 28 despite building
    successfully in on Fedora 2x and CentOS 6 in jenkins and Fedora 25 and
    26 in koji (but with late warnings emitted at the end of the build.)
    
    Examination of the scriptlets (e.g. `rpm -qp --scripts glusterfs-server.rpm`)
    revealed some ugliness that is addressed by the using %{nil} lines instead
    of " ;"
    
    After this, builds on CentOS 6, and old Fedora 27 rawhide, and koji f27 worked
    without warnings or errors about macro recursion. Visual inspection of the
    scripts appears correct. Fresh installs on CentOS 6 and Fedora 27 rawhide worked.
    Updates from glusterfs-3.12.1 worked.
    
    Reported-by: Sam McLeod <rhbugs@auto.smcleod.net>
    
    Change-Id: I84e9dbc6ccd17cdfc2f7c025bdbf61e92523da79
    BUG: 1495384
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit dd47c8ae6cfc9f704418cbad3e11f6aff67c4079
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Oct 10 15:50:33 2017 +0200

    md-cache: free "struct mdc_conf" in fini()
    
    Change-Id: Ia3a9b0152b7e36ded584150733e8392be458125c
    BUG: 1443145
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 9f7bd36edf3f0a9c634db019d28335f4320ad41e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Oct 10 13:51:46 2017 +0200

    gfapi: free xlator_cmdline_option_t when set through glfs_set_xlator_option()
    
    Change-Id: I10c323477534fd50d29460cf71c246378659fca5
    BUG: 1443145
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit a413c6353dbfff5221ea020ff8e1475d5ee17a81
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Oct 10 13:23:50 2017 +0200

    build: make it possible to build cleanly 2x in a row
    
    'make clean' does not cleanup everything, and some of the files get
    cleaned too eagerly. Several files are being packaged in a 'make dist'
    tarball, that get rebuild each time anyway.
    
    Specifically, this change prevents
     - libglusterfs/src/generator.pyc from laying around
     - keeping rpc/xdr/gen/*.x symlinks
     - modifying tests/basic/{fuse,gfapi}/Makefile each run
     - including tests/env.rc and events/src/eventtypes.py in the tarball
    
    Change-Id: I774dd1abf3a9d3b6a89b938cf6ee7d7792c59a82
    BUG: 1501317
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit c64fd0d4b0ef313bb44aae68a376ec0c9ee8657a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Oct 10 10:27:01 2017 -0400

    geo-rep: Filter out volume-mark xattr
    
    The volume-mark xattr, maintained at brick root
    of slave volume is specific to geo-replication
    and should be filtered out for all other clients.
    It should also be filtered out from list getxattr
    from all mounts including geo-rep mount as it
    might cause rsync to read and set.
    
    Change-Id: If9eb5a3af18051083c853e70d93b2819e8eea222
    BUG: 1500433
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 6cad2cd12b26e944d547b0a1c1a6b049c58f5d30
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Oct 12 18:59:15 2017 +0530

    Disable failing NetBSD tests
    
    BUG: 1501390
    Change-Id: I9a04c094783ec33e617baeae3d0e0cbedb1d6c3b

commit 7bf30b0e371ad1170cd0773fe5db335683428777
Author: Kamal Mohanan <kmohanan@redhat.com>
Date:   Fri Sep 22 11:33:47 2017 +0530

    xlators/debug/trace: Coverity Fix BUFFER_SIZE in reconfigure
    
    Problem: strncpy was being called with a source string of length
    equal to the size argument at lines 3110 and 3114.
    
    Solution: Calculate the size argument from the size of the
    destination argument.
    
    Change-Id: I1fed6f8f47c5512b9489bfb3297e7a9911eacbc8
    BUG: 789278
    Signed-off-by: Kamal Mohanan <kmohanan@redhat.com>

commit add7116efa1f31e86f9c00c72c71872b1161370f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Sep 18 14:34:54 2017 +0530

    eventsapi: Add JWT signing support
    
    New argument added to accept secret to generate JWT token. This patch
    does not affect the backward compatibility.
    
    Usage:
    
        gluster-eventsapi webhook-add <url> [-t <TOKEN>] \
            [-s SECRET]
    
    With `--token` argument, Token header will be added as is.
    
        Authorization: Bearer <TOKEN>
    
    In case of shared secret, Gluster will generate JWT token using the
    secret and then add it to Authorization header.
    
        Authorization: Bearer <GENERATED_TOKEN>
    
    Secret/Token can be updated using `webhook-mod` command.
    
    Generated token will include the following payload,
    
        {
           "iss": "gluster",
           "exp": EXPIRY_TIME,
           "sub": EVENT_TYPE,
           "iat": EVENT_TIME
         }
    
    Where: iss - Issuer, exp - Expiry Time, sub - Event Type
           used as Subject, iat - Event Time used as Issue Time
    
    BUG: 1496363
    Change-Id: Ib6b6fab23fb212d7f5e9bbc9e1416a9e9813ab1b
    Signed-off-by: Aravinda VK <avishwan@redhat.com>

commit 3dce15e10c263e8e071b26046568e0a171a3153d
Author: Xavier Hernandez <jahernan@redhat.com>
Date:   Fri Oct 6 10:39:58 2017 +0200

    cluster/ec: add functions for stripe alignment
    
    This patch removes old functions to align offsets and sizes
    to stripe size boundaries and adds new ones to offer more
    possibilities.
    
    The new functions are:
    
     * ec_adjust_offset_down()
         Aligns a given offset to a multiple of the stripe size
         equal or smaller than the initial one. It returns the
         size of the gap between the aligned offset and the given
         one.
    
     * ec_adjust_offset_up()
         Aligns a given offset to a multiple of the stripe size
         equal or greater than the initial one. It returns the
         size of the skipped region between the given offset and
         the aligned one. If an overflow happens, the returned
         valid has negative sign (but correct value) and the
         offset is set to the maximum value (not aligned).
    
     * ec_adjust_size_down()
         Aligns the given size to a multiple of the stripe size
         equal or smaller than the initial one. It returns the
         size of the missed region between the aligned size and
         the given one.
    
     * ec_adjust_size_up()
         Aligns the given size to a multiple of the stripe size
         equal or greater than the initial one. It returns the
         size of the gap between the given size and the aligned
         one. If an overflow happens, the returned value has
         negative sign (but correct value) and the size is set
         to the maximum value (not aligned).
    
    These functions have been defined in ec-helpers.h as static
    inline since they are very small and compilers can optimize
    them (specially the 'scale' argument).
    
    Change-Id: I4c91009ad02f76c73772034dfde27ee1c78a80d7
    Signed-off-by: Xavier Hernandez <jahernan@redhat.com>

commit c22cec3928be6924fb1026ef969cae897efbd76d
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Oct 4 14:34:48 2017 +0530

    gfapi: set lkowner in glfd
    
    We need a provision to be able to set lkowner (which is
    used to distinguish locks maintained by server) in gfapi.
    Since the same lk_owner need to be used to be able to
    flush the lock while closing the fd, store the lkowner
    in the glfd structure itself.
    
    A new API has been added to be able to set lkowner in glfd.
    
    Change-Id: I67591d6b9a89c20b9617d52616513ff9e6c06b47
    BUG: 1499641
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>

commit a3767c4ceb527cb0f52b95650c841964cf7faec9
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 11 17:33:20 2017 +0530

    protocol-auth: use the proper validation method
    
    Currently, server protocol's init and glusterd's option
    validation methods are different, causing an issue. They
    should be same for having consistent behavior
    
    Updates #175
    
    Change-Id: Ibbf9a18c7192b2d77f9b7675ae7da9b8d2fe5de4
    Signed-off-by: Amar Tumballi <amarts@redhat.com>

commit 9422446d72bc054962d72ace9912ecb885946d49
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Sat Oct 7 03:33:40 2017 +0530

    glusterd:Marking all the brick status as stopped when a process goes down in brick multiplexing
    
    In brick multiplexing environment, if a brick process goes down
    i.e., if we kill it with SIGKILL, the status of the brick for which
    the process came up for the first time is only changing to stopped.
    all other brick statuses are remain started. This is happening because
    the process was killed abruptly using SIGKILL signal and signal
    handler wasn't invoked and further cleanup wasn't triggered.
    
    When we try to start a volume using force, it shows error saying
    "Request timed out", since all the brickinfo->status are still in
    started state, we're waiting for one of the brick process to come up
    which never going to happen since the brick process was killed.
    
    To resolve this, In the disconnect event, We are checking all the
    processes that whether the brick which got disconnected belongs the
    process. Once we get the process we are calling a function named
    glusterd_mark_bricks_stopped_by_proc() and sending brick_proc_t object as
    an argument.
    
    From the glusterd_brick_proc_t we can get all the bricks attached
    to that process. but these are duplicated ones. To get the original
    brickinfo we are reading volinfo from brick. In volinfo we will have
    original brickinfo copies. We are changing brickinfo->status to
    stopped for all the bricks.
    
    Change-Id: Ifb9054b3ee081ef56b39b2903ae686984fe827e7
    BUG: 1499509
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit f18a47ee7e6e06c9a9a8893aef7957f23a18de53
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Oct 10 08:25:19 2017 -0400

    geo-rep: Fix passive brick's last sync time
    
    Passive brick's stime was not updated to the
    status file immediately after updating the brick
    root. As a result the last sync time was showing
    '0' until it finishes first crawl if passive
    worker becomes active after restart. Fix is to
    update the status file immediately after upgrading
    the brick root.
    
    Change-Id: I248339497303bad20b7f5a1d42ab44a1fe6bca99
    BUG: 1500346
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 34d52445a9058310d7512c9bcc8c01e709aac1ef
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 6 23:45:49 2017 -0400

    geo-rep: Add EINTR to retry list while doing readlink
    
    Worker occasionally crashed with EINTR on readlink.
    This is not persistent and is transient. Worker restart
    invovles re-processing of few entries in changenlogs.
    So adding EINTR to retry list to avoid worker restart.
    
    Change-Id: Iefe641437b5d5be583f079fc2a7a8443bcd19f9d
    BUG: 1499393
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit b56bdb34dafd1a87c5bbb2c9a75d1a088d82b1f4
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 6 22:42:43 2017 -0400

    geo-rep: Add ENODATA to retry list on gfid getxattr
    
    During xsync crawl, worker occasionally crashed
    with ENODATA on getting gfid from backend. This
    is not persistent and is transient. Worker restart
    invovles re-processing of few entries in changenlogs.
    So adding ENODATA to retry list to avoid worker
    restart.
    
    Change-Id: Ib78d1e925c0a83c78746f28f7c79792a327dfd3e
    BUG: 1499391
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 3edf926a1bda43879c09694cf3904c214c94c9dc
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Oct 10 05:54:04 2017 -0400

    geo-rep: Fix status transition
    
    The status transition is as below which is
    wrong.
    
    Created->Initializing->Active->Active/Passive->Stopped
    
    As soon as the monitor spawns the worker, the state
    is changed from 'Initializing' to 'Active' and then to
    'Active/Passive' based on whether worker gets the lock
    or not. This is wrong and it should directly tranistion
    as below.
    
    Created->Initializing->Active/Passive->Stopped
    
    Change-Id: Ibf5ca5c4fdf168c403c6da01db60b93f0604aae7
    BUG: 1500284
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 6060b113f0f49fe9654fe03fc79576e591ed8a43
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Oct 10 15:39:30 2017 +0200

    rpc: free conn->name in rpc_clnt_destroy()
    
    Change-Id: Idf99908aa48718a7faf7f0bbc647a679ec548282
    BUG: 1443145
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit ec39ca32d942d49fd701156174abbba0b73bce2f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Oct 9 18:58:09 2017 +0200

    rpc: free registered callback programs
    
    Change-Id: I8c6f6b642f025d1faf74015b8f7aaecd7ebfd4d5
    BUG: 1443145
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit 6628b9426918010d203a7de19e3e187eeb077b0d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Oct 9 17:56:56 2017 +0200

    dht: free memory allocated in dht_init() and dht_init_subvolumes()
    
    When glfs_fini() is called, DHT fails to free all memory allocations
    which result in a considerable leak.
    
    Change-Id: I37c6de5c93ca4516266dbe8288b4a416f5589901
    BUG: 1443145
    Signed-off-by: Niels de Vos <ndevos@redhat.com>

commit dc3cd44add80fb56fae2492cb8ad264be04f46fc
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Fri Sep 22 16:13:44 2017 +0530

    xlator/debug :coverity Issue BUFFER_SIZE
    
    Issue :Calling strncpy with a source string whose length (2 chars)
    is greater than or equal to the size argument (2) will fail to
    null-terminate "trace_fop_names[i].name".
    
    Solution : The size argument is obtained from
    sizeof(trace_fop_names[i].name).
    
    Change-Id: I99fad2693054f3af84d78da34c61258233d3049a
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 3afbe4201d864d2e886509f5633468aa344fa444
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 6 06:02:56 2017 -0400

    geo-rep: Add ENOTSUP error to retry list
    
    os.listdir gives ENOTSUP on gfid path occasionally
    which is not persistant. Adding it to retry list
    to avoid worker to crash if it's transient error.
    
    Change-Id: Ic795dd1f02a27c9e5d901e20722ee32451838feb
    BUG: 1499180
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit c4a608799a577a4f38139f6bb8a47da8efb0fec3
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jul 21 16:38:14 2017 +0530

    cluster/dht: Don't store the entire uuid for subvols
    
    Comparing the uuid string of the local node against that stored in the
    local_subvol information is inefficient, especially as it is
    done for every file to be migrated. The code has now been changed
    to set the value of info to 1 if the nodeuuid is that of the node
    making the comparison so this becomes an integer comparison.
    
    Change-Id: I7491d59caad3b71dbf5facc94dcde0cd53962775
    BUG: 1451434
    Signed-off-by: N Balachandran <nbalacha@redhat.com>

commit d4eb4ef28073fc8f5430802d9de9344e551711bb
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Tue Aug 8 12:09:25 2017 +0530

    gfproxy: Introduce new server-side daemon called GFProxy
    
    Summmary:
    Adds a new server-side daemon called gfproxyd & a new FUSE client
    called gfproxy-client
    
    Updates: #242
    BUG: 1428063
    Change-Id: I83210098d3a381922bc64fed1110ae1b76e6519f
    Tested-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-by: Kevin Vigor <kvigor@fb.com>
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>

commit 7a179f55c7e7f7ce32b9938f91c8706133340157
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 18 18:39:01 2017 +0530

    cluster/ec: Handle parallel get_size_version
    
    Updates #251
    Change-Id: I6244014dbc90af3239d63d75a064ae22ec12a054
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit d561282633801bf3254c057188b7f18c7c6fe7c6
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Oct 9 14:10:52 2017 +0530

    test: Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case
    
    Problem: Test case ./tests/bugs/bug-1371806_1.t is failing.
    
    Solution: Mark test case ./tests/bugs/bug-1371806_1.t as a bad test case.
    
    BUG: 1499663
    Change-Id: Icb3f41d23dcc74cce6fde05ca343c158d5f58cdd
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 452b9124f452d6c73f72da577a98f17502b1ed2c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Oct 3 18:41:11 2017 +0530

    glusterd : fix client io-threads option for replicate volumes
    
    Problem:
    Commit ff075a3d6f9b142911d25c27fd209838782bfff0 disabled loading
    client-io-threads for replicate volumes (it was set to on by default in
    commit e068c1997314046658dd502e9118dab32decf879) due to performance
    issues but in doing so, inadvertently failed to load the xlator even if
    the user explicitly enabled the option using the volume set command.
    This was despite returning returning sucess for the volume set.
    
    Fix:
    Modify the check in perfxl_option_handler() and add checks in volume
    create/add-brick/remove-brick code paths, tying it all to
    GD_OP_VERSION_3_12_2.
    
    Change-Id: Ib612973a999a7da818cc926f5c2601b1f0794fcf
    BUG: 1498570
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 20fa80057eb430fd72b4fa31b9b65598b8ec1265
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Sep 20 12:16:06 2017 +0530

    afr: heal gfid as a part of entry heal
    
    Problem:
    If a brick crashes after an entry (file or dir) is created but before
    gfid is assigned, the good bricks will have pending entry heal xattrs
    but the heal won't complete because afr_selfheal_recreate_entry() tries
    to create the entry again and it fails with EEXIST.
    
    Fix:
    We could have fixed posx_mknod/mkdir etc to assign the gfid if the file
    already exists but the right thing to do seems to be to trigger a lookup
    on the bad brick and let it heal the gfid instead of winding an
    mknod/mkdir in the first place.
    
    Change-Id: I82f76665a7541f1893ef8d847b78af6466aff1ff
    BUG: 1493415
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 938addeb7ec634e431c2c8c0a768a2a9ed056c0d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 6 05:33:31 2017 -0400

    geo-rep/scheduler: Add validation for session existence
    
    Added validation to check for session existence
    to give out proper error message out.
    
    Change-Id: I13c5f6ef29c1395cff092a14e1bd2c197a39f058
    BUG: 1499159
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 12cfc1983fa1521d6da94ad488145182cf97db2c
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Fri Apr 28 18:09:01 2017 +0530

    cluster/ec: Improve performance with xattrop update
    
    Existing EC code updates the xattr on the subvolume
    in a sequential pattern resulting in very poor performance.
    
    With this fix EC now updates the xattr on the subvolume
    in parallel which improves the xattr update performance.
    
    BUG: 1445663
    Change-Id: I3fc40d66db0b88875ca96a9fa01002ba386c0486
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>

commit deea16e59564575d5f211f4fb8e4e5597e570ad1
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Mon Sep 25 14:58:13 2017 +0530

    xlator/cluster/afr:coverity Issue "UNUSED_VALUE" in afr_get_split_brain_status
    
    Issue: Event value_overwrite:Overwriting previous write to "ret"
    with value "-1".
    
    Fix : An "If" condition is added to check the value of "ret".
    
    Change-Id: I7b6bd4f20f73fa85eb8a5169644e275c7b56af51
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 601b6547f2c53651b88a0560a41d702db06c0d1c
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Jun 27 17:17:56 2016 +0530

    storage/posix: Adding implementation for posix_do_futimes
    
    Adding the implementation for the posix_do_futimes function which is
    not complete in the current implementation and giving the ENOSYS error.
    
    Change-Id: I9cfc95a7ea293b0a2df8efd4ac80d0120b3120e4
    BUG: 1350406
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit b887915bd30ac98bbc64c6dcac73605cd96855ca
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Mon Sep 25 12:52:47 2017 +0530

    Coverity issue fix: IDENTICAL_BRANCHES
    
    issue: The same code is executed when the condition "ret" is true or false, because the code in the if-then branch and after the if statement is identical. Should the if statement be removed?
    
    function: glusterd_print_gsync_status_by_vol
    
    Change-Id: Iedad05cbafd9598443b524778056f7740e4f12a5
    BUG: 789278
    fix: removed the 'if' block because the value of ret will be returned in any case
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit fabee9d6816077d0f44a7d82c0b35aef60771711
Author: Kartik_Burmee <kburmee@redhat.com>
Date:   Mon Sep 25 15:49:36 2017 +0530

    Coverity issue fix: checked return
    
    issue:Calling "client_submit_request" without checking return value (as is done elsewhere 52 out of 58 times).
    
    function: client_fdctx_destroy
    
    Change-Id: I66a295dd114fc20f04eb1aca9a5b274df53be090
    BUG: 789278
    fix: typecasted function return value using void
    Signed-off-by: Kartik_Burmee <kburmee@redhat.com>

commit 9b4de61a136b8e5ba7bf0e48690cdb1292d0dee8
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri May 12 21:12:47 2017 +0530

    cluster/dht : User xattrs are not healed after brick stop/start
    
    Problem: In a distributed volume custom extended attribute value for a directory
             does not display correct value after stop/start or added newly brick.
             If any extended(acl) attribute value is set for a directory after stop/added
             the brick the attribute(user|acl|quota) value is not updated on brick
             after start the brick.
    
    Solution: First store hashed subvol or subvol(has internal xattr) on inode ctx and
              consider it as a MDS subvol.At the time of update custom xattr
              (user,quota,acl, selinux) on directory first check the mds from
              inode ctx, if mds is not present on inode ctx then throw EINVAL error
              to application otherwise set xattr on MDS subvol with internal xattr
              value of -1 and then try to update the attribute on other non MDS
              volumes also.If mds subvol is down in that case throw an
              error "Transport endpoint is not connected". In dht_dir_lookup_cbk|
              dht_revalidate_cbk|dht_discover_complete call dht_call_dir_xattr_heal
              to heal custom extended attribute.
              In case of gnfs server if hashed subvol has not found based on
              loc then wind a call on all subvol to update xattr.
    
    Fix:    1) Save MDS subvol on inode ctx
            2) Check if mds subvol is present on inode ctx
            3) If mds subvol is down then call unwind with error ENOTCONN and if it is up
               then set new xattr "GF_DHT_XATTR_MDS" to -1 and wind a call on other
               subvol.
            4) If setxattr fop is successful on non-mds subvol then increment the value of
               internal xattr to +1
            5) At the time of directory_lookup check the value of new xattr GF_DHT_XATTR_MDS
            6) If value is not 0 in dht_lookup_dir_cbk(other cbk) functions then call heal
               function to heal user xattr
            7) syncop_setxattr on hashed_subvol to reset the value of xattr to 0
               if heal is successful on all subvol.
    
    Test : To reproduce the issue followed below steps
           1) Create a distributed volume and create mount point
           2) Create some directory from mount point mkdir tmp{1..5}
           3) Kill any one brick from the volume
           4) Set extended attribute from mount point on directory
              setfattr -n user.foo -v "abc" ./tmp{1..5}
              It will throw error " Transport End point is not connected "
              for those hashed subvol is down
           5) Start volume with force option to start brick process
           6) Execute getfattr command on mount point for directory
           7) Check extended attribute on brick
              getfattr -n user.foo <volume-location>/tmp{1..5}
              It shows correct value for directories for those
              xattr fop were executed successfully.
    
    Note: The patch will resolve xattr healing problem only for fuse mount
          not for nfs mount.
    
    BUG: 1371806
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    
    Change-Id: I4eb137eace24a8cb796712b742f1d177a65343d5

commit d9cd579a38abb507726ecece8ae4447077709747
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 14 14:31:26 2017 -0400

    xlator/bitrot: flood of -Wformat-truncation warnings with gcc-7.1
    
    Starting in Fedora 26 which has gcc-7.1.x, -Wformat-trunction is enabled
    with -Wformat, resulting in a flood of new warnings. This many warnings
    is a concern because it makes it hard(er) to see other warnings that
    should be addressed.
    
    An example is at
    https://kojipkgs.fedoraproject.org//packages/glusterfs/3.12.0/1.fc28/data/logs/x86_64/build.log
    
    For more info see https://review.gluster.org/#/c/18267/
    
    Change-Id: I7792d94da1e8109f3aaa857a94be40f2d2402684
    BUG: 1492851
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit d1f15cdeb609a1b720a04a502f7a63b2d3922f41
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Oct 25 19:57:02 2016 +0530

    cli/afr: gluster volume heal info "healed" command output is not appropriate
    
    Problem: "gluster volume heal info [healed] [heal-failed]" command
              output on terminal is not appropriate in case of down any volume.
    
    Solution: To make message more appropriate change the condition
              in function "gd_syncop_mgmt_brick_op".
    
    Test : To verify the fix followed below procedure
           1) Create 2*3 distribute replicate volume
           2) set self-heal daemon off
           3) kill two bricks (3, 6)
           4) create some file on mount point
           5) bring brick 3,6 up
           6) kill other two brick (2 and 4)
           7) make self heal daemon on
           8) run "gluster v heal <vol-name>"
    
    Note: After apply the patch options (healed | heal-failed) will deprecate
          from command line.
    BUG: 1388509
    Change-Id: I229c320c9caeb2525c76b78b44a53a64b088545a
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>

commit 1c0d3ac5c5f9774a0f25f5282d54177af02f984e
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Thu Sep 21 14:07:16 2017 +0530

    xlators/io-stats: Coverity Fix CHECKED_RETURN in resolve_group_name
    
    Issue: Calling "getgrgid_r(gid, &grp, grp_buf, grp_buf_len, &grp_result)"
    without checking return value. This library function may fail and return
    an error code
    
    Solution: getgrgrid_r returns zero when the operation is successful
    and a non-zero error code if there's some error in the operation
    
    Fix: Checked for the return value and redirected to error if the
    return value was non-zero
    
    Change-Id: I0d082c6d57c6148b9830bc020140946c06d6f800
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit fe5fc91ab9b74b525d4979e09ce13766b3180381
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Fri Sep 22 18:17:03 2017 +0530

    glusterd/snapshot: Buffer Size Warning
    
    new_brickinfo->mnt_opts is allocated memory using calloc. So it is
    already zeroed out at allocation. we need not to add null character
    at the end. we pass one less than maximum size to the strncpy to make
    sure that destination string is terminated.
    
    Change-Id: I463dddd2171fb39a509bb75ffcc074d5b1cf7d62
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit faf5939307cafe262ee2135621e1d3e173087e06
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Oct 2 10:44:59 2017 -0400

    packaging: manual systemctl daemon reload required after install
    
    Use the %systemd_{post,preun,postun_with_restart} macros provided
    
    I tried both install and update from 3.10.x and did not receive
    any warnings about needing daemon reload
    
    Reported-by: Sam McLeod <rhbugs@auto.smcleod.net>
    
    Change-Id: Ibb33a748fc4226864019765b59d1a154b7297bae
    BUG: 1495384
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 1e2d6537875d16b783e3c50ada7ee61487c6d796
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Aug 11 15:43:58 2017 +0530

    cluster/afr: Make choose-local "reconfigurable"
    
    With this change, enabling choose-local (which means its state makes
    transition from "off" to "on") will be effective after the first
    gfid-lookup on "/" since volume-set was executed.
    
    Change-Id: Ibab292ba705d993b475cd0303fb3318211fb2500
    BUG: 1480525
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 306164fb4121e814b61e9b5685319f889f6b7547
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Thu Sep 21 18:12:59 2017 +0530

    libglusterfs: Coverity Fix CONSTANT_EXPRESSION_RESULT in gf_string2int64
    
    Issue : "l <= 9223372036854775807L" is always true regardless of the values
    of its operands. This occurs as the logical operand of "if".
    
    Solution : Remove the comparison which always turns out to be true
    
    Fix : The if-condition was removed and the body inside the same was retained.
    
    Change-Id: Iba94d7f4f2dee85a180d10cdb7f7235b406cc400
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit 8154e044e1b920b10d632d8c1e6d36007927b267
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Fri Sep 22 19:34:12 2017 +0530

    glusterfsd: Coverity Issue "MISSING_BREAK" in parse_opts
    
    Issue:Event unterminated_case: 	The case for value
    "ARGP_LOCALTIME_LOGGING_KEY" is not terminated by a
    'break' statement.
    
    Solution: A break statement is added in the fallthrough case.
    
    Change-Id: Ie44d1a291afaa0e9fb9ef2aa45368b9401a8bb82
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 687908a364efcfb5ed69ff3dd0a8ef5b1551e88e
Author: Akarsha Rai <akrai@redhat.com>
Date:   Tue Sep 26 06:09:28 2017 -0400

    cluster/ec: FORWARD_NULL coverity fix
    
    Problem: ctx pointer could be NULL
    
    Solution: Updated the code to verify ctx pointer
    
    BUG: 789278
    Change-Id: I25e07a07c6ebe2f630c99ba3aa9a61656fbaa981
    Signed-off-by: Akarsha Rai <akrai@redhat.com>

commit e994fbc825b0ce48bbe0c23d034e821502359912
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Sat Sep 23 02:28:34 2017 +0530

    libglusterfs: Coverity Issue NEGATIVE_RETURNS
    
    Issue: Event negative_return_fn: Function "dup(handle->fd)" returns a
    negative number. Event negative_returns: "dup(handle->fd)" is passed
    to a parameter that cannot be negative.
    
    With this change value of dup(handle->fd) is stored in duped_fd & if
    condition checks the value of duped_fd is non-negative.
    
    Change-Id: I563d717108016d740ffa64fbe0929eb1e08c8f33
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit 9af20af096a14c6297ca8f89697f2a9e4e83bd8f
Author: Akarsha Rai <akrai@redhat.com>
Date:   Thu Sep 28 07:18:56 2017 -0400

    core: Verify pool pointer before destroying it
    
    Problem: Current code is not checking whether the pool pointer is null or not.
    
    Solution: Updated the code to verify pool pointer.
    
    Bug: 1496675
    Change-Id: Ie1f2de4e4204fde15d2b1e3a966ea4c9e7b41534
    Signed-off-by: Akarsha Rai <akrai@redhat.com>

commit e348b4df9bfd80be5c521bc4c76faf2693e90692
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Thu Sep 21 20:19:44 2017 +0530

    cli: fix Coverity warning DEADCODE in gf_cli_attach_tier()
    
    Issue : At condition "ret", the value of "ret" must be equal to 0.
    The condition "ret" cannot be true since the value is always 0.
    Hence, the execution cannot reach the statement "goto out"
    
    Solution : The never-true if-condition and its body has to be removed
    
    Fix : The always false if-condition and the dead code under this
    if-condition was removed.
    
    Change-Id: I5c038b8ec9abf9b2f06dcfd981904b9dca1a0094
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit d01a674077f2411ecde7bd6037efbfcf6faa65ba
Author: Mohammed Azhar Padariyakam <mpadariy@redhat.com>
Date:   Thu Sep 21 20:55:05 2017 +0530

    protocol/client: Coverity Fix IDENTICAL_BRANCHES in client3_3_flush_cbk
    
    Issue : The same code is executed when the condition "ret < 0" is true
    or false, because the code in the if-then branch and after the if
    statement is identical.
    
    Solution : Remove the if-condition whose output does not alter the
    program flow of control
    
    Fix : The identical branching condition was removed.
    
    Change-Id: Iae40f068e5a03946273e1091886ba7011460fcc8
    BUG: 789278
    Signed-off-by: Mohammed Azhar Padariyakam <mpadariy@redhat.com>

commit eebeb504578e774eef6e762326baadaab014b9ae
Author: Akarsha Rai <akrai@redhat.com>
Date:   Tue Sep 26 06:44:15 2017 -0400

    cluster/ec: FORWARD_NULL coverity fix
    
    Problem:
    cbk could be NULL.
    
    Solution:
    Returning NULL when memory is not allocated
    for cbk.
    
    BUG: 789278
    Change-Id: Iea9128e0f3b95100deca560f690f9baaae226abf
    Signed-off-by: Akarsha Rai <akrai@redhat.com>

commit 703728dd6f0431ba82821794ca6e9e8b43b35811
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Mon Sep 25 14:52:24 2017 +0530

    xlators/protocol/server: Coverity Issue in server_setvolume()
    
    Issue: Event result_independent_of_operands: "rsp->dict.dict_len > 4294967295U
    /* 2147483647 * 2U + 1U */" is always false regardless of the values of its
    operands. This occurs as the logical operand of "if".
    
    Fix: removed if block as the if condition is always false and statement inside
    block never executes.
    
    Change-Id: Ieaa968d6fbc9477428b4658ef725ace0db9b810a
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit 2c124b5256bac5830d81552bfb4412620aa6cfb0
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Sep 25 17:29:25 2017 +0530

    stack.h:PW.INCLUDE_RECURSION
    
    The headerfile globals.h is recursively adding itself.
    ( globals.h -> xlator.h -> stack.h -> globals.h).
    We are finding the source files which are including the header
    file globals.h and removing the inclusion line.
    
    I used git grep -l stack.h | xargs git grep globals.h --
    to find out the files and removed the header file from all files
    except libglusterfs/src/xlator.h and libglusterfs/src/Makefile.am
    
    When I try to remove header file from libglusterfs/src/xlator.h
    I'm getting some errors. In libglusterfs/src/Makefile.am it is
    required for building RPMs.
    
    Change-Id: I537218c09ade6d7ea51717768b26563a247daf60
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit e4784f26bf9739853379ec13d0f921ddfb954475
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu Sep 28 15:43:30 2017 +0530

    Posix: fix additional inode ref
    
    Problem: In the iteration, the inode is being ref-ed twice and
    unref-ed once. this leads to ref leak.
    
    Fix: assign the parent to the inode instead of referencing it.
    
    Change-Id: Ib154b12d38ad68220f8f5288bbc50081beccc2b9
    BUG: 1496379
    Signed-off-by: hari gowtham <hgowtham@redhat.com>

commit a2039f3e97049806ca0847a84cc9030e31f4d008
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Fri Sep 22 19:09:34 2017 +0530

    rpc/rpc-transport/socket/: Coverity Issue MISSING_BREAK
    
    Issue: Event unterminated_case:	The case for value "AF_INET_SDP"
    is not terminated by a 'break' statement.
    
    Function: socket_server_get_local_sockaddr
    
    Added Fall through in comment after case AF_INET_SDP.
    
    Change-Id: I5340cde2257be33ff13c53cee6ccdb33df7d2c88
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit 8daaac1481adc919cb80c6f3d98bc5b3f0b829f5
Author: Kamal Mohanan <kmohanan@redhat.com>
Date:   Mon Sep 25 12:07:03 2017 +0530

    dht: fix a coverity error of type - UNREACHABLE
    
    Problem: Unreachable assignment statement at dht-rebalance.c:1040
    
    Fix: Delete line dht-rebalance.c:1040.
    
    The goto statements at lines 1037 and 1031 are also deleted since
    both branches of the if statement finally go to the same
    immediately-following label anyway.
    
    Change-Id: I5f47ea99244cae2a0a9f2aec7284faadf2ea286a
    BUG: 789278
    Signed-off-by: Kamal Mohanan <kmohanan@redhat.com>

commit 3a423437e35fa46befa28fa030cef26d6663e507
Author: Akarsha Rai <akrai@redhat.com>
Date:   Tue Sep 26 04:58:19 2017 -0400

    cluster/ec: FORWARD_NULL coverity fix
    
    Problem: Pool pointer could be NULL while destroying it.
    
    Solution: Verifying pointer before destroying it.
    
    BUG: 789278
    Change-Id: I497d1310aa47cb749a4c992aa961bd4dfa23ee48
    Signed-off-by: Akarsha Rai <akrai@redhat.com>

commit 165827e3812942f8a9bd96880bc316820a297821
Author: Akarsha Rai <akrai@redhat.com>
Date:   Tue Sep 26 08:51:04 2017 -0400

    protocol: UNINIT coverity fix
    
    Problem: Coverity issue due uninitialized variable.
    
    Solution: Initialized the variable appropriately.
    
    Bug: 789278
    Change-Id: I6e9356bbcd8fa97006b605ee162458d4a2eb5887
    Signed-off-by: Akarsha Rai <akrai@redhat.com>

commit 77f89a2ebac1c19c4f22f33aba536bbe7e19e665
Author: Kamal Mohanan <kmohanan@redhat.com>
Date:   Mon Sep 25 12:50:43 2017 +0530

    libglusterfs: fix a coverity error of type - PW.INCLUDE_RECURSION
    
    Problem: xlator.h which is included at inode.h:32 includes itself.
    
    Solution: Delete the include statement.
    
    Change-Id: I304bbef5293a2fef0584773a1f8e61e838d7cbf1
    BUG: 789278
    Signed-off-by: Kamal Mohanan <kmohanan@redhat.com>

commit 572b4bf889d903dcaed49a57a75270a763dc259d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Sep 22 12:50:43 2017 +0530

    features/locks: Maintain separation of lock->client_pid, flock->l_pid
    
    Problem:
    grant_blocked_locks() constructs flock from lock. Locks xlator uses
    frame->root->pid interchangeably flock->l_pid. With gNFS frame->root->pid
    (which translates to lock->client_pid) is not same as flock->l_pid, this leads
    to lk's cbk returning flock with l_pid from lock->client_pid instead of input
    flock->l_pid. This triggers EC's error code path leading to failure of lk call,
    because the response' flock->l_pid is different from request's flock->l_pid.
    
    Fix:
    Maintain separation of lock->client_pid, flock->l_pid. Always unwind with
    flock with correct pid.
    
    BUG: 1472961
    Change-Id: Ifab35c458662cf0082b902f37782f8c5321d823d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>

commit 24637d54dcbc06de8a7de17c75b9291fcfcfbc84
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Sep 26 14:03:52 2017 +0530

    afr: don't check for file size in afr_mark_source_sinks_if_file_empty
    
    ... for AFR_METADATA_TRANSACTION and just mark source and sinks if
    metadata is the same.
    
    Change-Id: I69e55d3c842c7636e3538d1b57bc4deca67bed05
    BUG: 1491670
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>

commit 13d2af4ffeb3b968a3c4675247513d429972d31d
Author: Akarsha Rai <akrai@redhat.com>
Date:   Mon Sep 25 08:36:36 2017 -0400

    glusterd: FORWARD_NULL coverity fix
    
    Problem:
    Pointer used to print xlator name could be NULL.
    
    Solution:
    Updated the code to use xlator name as appropriate.
    
    BUG: 789278
    Change-Id: I26927ef1f33f362e17c104684d7f722a643c7f97
    Signed-off-by: Akarsha Rai <akrai@redhat.com>

commit a2bbf75d04e8173c2156a001538564d141a26d4a
Author: Girjesh Rajoria <grajoria@redhat.com>
Date:   Sat Sep 23 02:00:56 2017 +0530

    Coverity Issue Fix: IDENTICAL_BRANCHES
    
    Issue: Event identical_branches: The same code is executed when the condition "ret" is true or false, because the code in the if-then branch and after the if statement is identical.
    
    Function: glusterd_print_gsync_status_by_vol
    
    Fix: removed if and goto statement.
    
    Change-Id: I966d793c9f3b65487acfb07083a4039caf593105
    BUG: 789278
    Signed-off-by: Girjesh Rajoria <grajoria@redhat.com>

commit 467f1f3c3037efac0497d50510247e62605c3f3a
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Sep 25 15:53:24 2017 +0530

    Posix: Unused value
    
    In line number 5179 we are storing -1 into op_ret variable. Before
    we use the value we are overwriting the same variable in line
    number 5339. So we are removing the value assigning statement.
    
    Change-Id: I8c6dae9f6b0f9f1e3c09d0744d451b9296d12db8
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit b269089a33bd1348d34c861817c3f673206b6a18
Author: Sanju Rakonde <srakonde@redhat.com>
Date:   Mon Sep 25 12:34:05 2017 +0530

    Glusterfsd: Unreachable statements
    
    Issue: Event unreachable at line number 1111 in glusterfsd/src/glusterfsd.c
    
    There was a statement in outer if block after the break statement.
    Ideally the break statement should be inside the inner if block so
    that the statement will not become unreachable. I put the break
    inside the inner if block.
    
    Change-Id: Id4917305333e1638f35b3f2fb59ac42e62a12d02
    BUG: 789278
    Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

commit 83d2bf8815bb4d79349659a7d5b9df822acd5430
Author: Subha sree Mohankumar <smohanku@redhat.com>
Date:   Mon Sep 25 11:49:16 2017 +0530

    Coverity Issue Fix : CHECKED_RETURN
    
    Issue :Event check_return: Calling "ec_dict_set_number" without checking return value.
    
    Fix : Type casted the return value of the function "ec_dict_set_number" to void.
    
    Change-Id: Id97034f9b1b8591536d63dca680ca7c7a9c4fcc3
    BUG: 789278
    Signed-off-by: Subha sree Mohankumar <smohanku@redhat.com>

commit 490f27c44f0a4feb8c52fc31f28163310690e0a1
Author: Kamal Mohanan <kmohanan@redhat.com>
Date:   Mon Sep 25 10:57:21 2017 +0530

    Fix a coverity error of checker type: CHECKED_RETURN
    
    Problem: dht_frame_return was being called without checking the
    return value.
    
    Solution: Typecast the value returned by the function to void.
    
    Change-Id: Idfc6a7ed467d1c8f5f8d09ec26d9059f3d23b760
    BUG: 789278
    Signed-off-by: Kamal Mohanan <kmohanan@redhat.com>

commit 8855ebcfecde2a21e0a9ba725e9738708e03904a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Sep 25 23:34:55 2017 -0400

    geo-rep/scheduler: Fix '--no-color' help msg
    
    Change-Id: I0f51558083e0b11a6563b8a2ef62ec07fe2a9ca9
    BUG: 1495436
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 1719cffa911c5287715abfdb991bc8862f0c994e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Sep 14 11:29:15 2017 +0530

    afr: auto-resolve split-brains for zero-byte files
    
    Problems:
    As described in BZ 1491670, renaming hardlinks can result in data/mdata
    split-brain of the DHT link-to files (T files) without any mismatch of
    data and metadata.
    
    As described in BZ 1486063, for a zero-byte file with only dirty bits
    set, arbiter brick will likely be chosen as the source brick.
    
    Fix:
    For zero byte files in split-brain, pick first brick as
    a) data source if file size is zero on all bricks.
    b) metadata source if metadata is the same on all bricks
    
    In arbiter case, if file size is zero on all bricks and there are no
    pending afr xattrs, pick 1st brick as data source.
    
    Change-Id: I0270a9a2f97c3b21087e280bb890159b43975e04
    BUG: 1491670
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reported-by: Rahul Hinduja <rhinduja@redhat.com>
    Reported-by: Mabi <mabi@protonmail.ch>

commit 898f0b7ce31ddf8ec02e572c5d22eff2e4205b4c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Sep 21 14:05:35 2017 +0530

    glusterd: retrieve uuid under mutex lock
    
    In a multi node cluster, if one of the glusterd instance goes down and
    comes back, then there might be a race situation where glusterd needs to
    retrieve its uuid (glusterd_retrieve_uuid) and at the same time as part of
    receiving a friend handshake from other peer, glusterd iterates over the volume
    information recieved from remote node and checks for if a brick is local or not
    by calling MY_UUID which in turn calls glusterd_retrieve_uuid. And the
    same applies for glusterd_store_global_info () function too. This
    could end up in a situation where for the same node glusterd ends up
    generating two UUID files in /var/lib/glusterd. Following is the log
    snippet which confirms the above:
    
    [2017-09-01 03:09:24.458030] I [glusterd.c:146:glusterd_uuid_init] 0-management: retrieved UUID: fd46a495-7e33-468f-88f6-63c815fac640  // thread 1 retrieve uuid from glusterd.info
    [2017-09-01 03:09:24.458034] E [glusterd-store.c:2109:glusterd_retrieve_uuid] 0-: No previous uuid is present
    //thread 2 can not retrieve uuid, because in thread1 the file pointer has already become eof.
    [2017-09-01 03:09:24.458041] E [glusterd-store.c:2117:glusterd_retrieve_uuid] 0-: Returning -1
    [2017-09-01 03:09:24.458076] I [glusterd.c:176:glusterd_uuid_generate_save] 0-management: generated UUID: 190bb292-a296-4125-96da-42b247511cc4
    [2017-09-01 03:09:24.458129] E [store.c:367:gf_store_save_value] 0-: Able to store key: UUID,value: 190bb292-a296-4125-96da-42b247511cc4
    
    Fix is to retrieve the uuid under mutex lock.
    
    Credits : cynthia.zhou@nokia-sbell.com
    
    Change-Id: Ib9a5e159c3febf2aef13aa5e38f0a51fe409dadb
    BUG: 1493967
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>

commit 956d43d6e89d40ee683547003b876f1f456f03b6
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 7 18:48:34 2017 +0530

    mount/fuse: Make event-history feature configurable
    
    ... and disable it by default.
    
    This is because having it disabled seems to improve performance.
    This could be due to the lock contention by the different epoll threads
    on the circular buff lock in the fop cbks just before writing their response
    to /dev/fuse.
    
    Just to provide some data - wrt ovirt-gluster hyperconverged
    environment, I saw an increase in IOPs by 12K with event-history
    disabled for randrom read workload.
    
    Usage:
    mount -t glusterfs -o event-history=on $HOSTNAME:$VOLNAME $MOUNTPOINT
    OR
    glusterfs --event-history=on --volfile-server=$HOSTNAME --volfile-id=$VOLNAME $MOUNTPOINT
    
    Change-Id: Ia533788d309c78688a315dc8cd04d30fad9e9485
    BUG: 1467614
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>

commit f449e53df7c07301b495b4ff688d165026dfd2d0
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Sep 21 12:09:12 2017 +0530

    cli: Bypass the confirmation question creating replica 2 volume with force
    
    When a replica 2 volume is created with the force option,
    remove the warning message with the confirmation question,
    whether they want to continue or not and Succeed the
    volume creation.
    
    Change-Id: I4f3306659fa4cbf53dd8d45269a32d19ce86ac88
    BUG: 1493893
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit db3fe245a9e8812829eae7d143e49d0bfdfef9a7
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Sep 19 15:34:04 2017 +0530

    libglusterfs: Fix openSUSE build error
    
    GlusterFS failed during make on openSUSE Tumbleweed with the following
    error:
    
    Making all in fdl
    Making all in src
      CC       logdump.o
      CC       recon.o
      CC       fdl.lo
      CC       librecon.o
      CC       libfdl.o
      CCLD     gf_logdump
      CCLD     gf_recon
    /usr/lib64/gcc/x86_64-suse-linux/7/../../../../lib64/libfl.so: undefined reference to `yylex'
    collect2: error: ld returned 1 exit status
    make[5]: *** [Makefile:618: gf_logdump] Error 1
    make[5]: *** Waiting for unfinished jobs....
    /usr/lib64/gcc/x86_64-suse-linux/7/../../../../lib64/libfl.so: undefined reference to `yylex'
    collect2: error: ld returned 1 exit status
    
    Reading through autoconf manual[1](see AC_PROG_LEX) reveals that LEXLIB
    is automatically set to appropriate value for the system. The reference
    to LEXLIB in automake file caused the above mentioned error on openSUSE.
    In particular, we do not bother about LEXLIB hereafter.
    
    [1] https://www.gnu.org/software/autoconf/manual/autoconf.html#Particular-Programs
    
    Change-Id: I9bfce80c9654b2e3bfb393b08c25e8ad3d79e449
    BUG: 1493133
    Signed-off-by: Anoop C S <anoopcs@redhat.com>

commit 3bbb4fe4b33dc3a3ed068ed2284077f2a4d8265a
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Sep 20 18:30:21 2017 +0530

    cluster/afr: Sending subvol up/down events when subvol comes up or goes down
    
    Change-Id: I6580351b245d5f868e9ddc6a4eb4dd6afa3bb6ec
    BUG: 1493539
    Signed-off-by: karthik-us <ksubrahm@redhat.com>

commit 6b30347f65c9590fa1b636e4aed0471dc8eeff07
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Sat Sep 2 09:49:06 2017 -0400

    cluster/ec: fix for BAD_SHIFT, follow-up patch
    
    Address comments to https://review.gluster.org/18067, (Change-Id
    I86e15d12939c610c99f5f96c551bb870df20f4b4)
    
    Which was posted as an RFC as an example of a possible alternative
    fix to https://review.gluster.org/17860 (Change-Id
    I28a3bdd4a357526dba0cf84c262919c05cfa173e)
    
    An alternative fix that preserved the unsignedness of the indexes
    throughout, obviating the need to check its value before using it to
    shift. (shift by negative number is undefined, as is shift by more
    bits than in the type.)
    
    BUG: 1474309
    Change-Id: I46fe9cec140d3397463780748f6876251acb06dd
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>

commit 60ff231644862c0d9351352febdda7b2dfdde994
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Aug 7 15:19:47 2017 +0530

    fuse/readdirp: Remove need_lookup from fuse_readdirp_cbk
    
    background: Various xlators used to populate their ctx, on
    an explicit lookup. That means without a lookup, the translator will have
    either null or stale data to function. E.g. dht would depend on lookup to
    create linkto files on the correct node/hashed subvol, afr would rely on
    this lookup to heal pending data/metadata etc.
    
    So to complete above actions a lookup used to be issued on files,
    even their inode was populated on a readdirp_cbk. This was done
    by setting the need_lookup flag on all the files those were read
    on readdirp fop.
    
    We tried a small test on "ACL client". For listing 50k files on root
    itself, it took around 50seconds with readdirp enabled while
    the same operation took 5-6 seconds with readdirp disabled. Both the
    times md-cache was enabled.
    
    We observed that on the 1st test case (readdirp enabled), post readdirp
    a getxattr is done. The number of getxattr depends on the number of acl
    xattrs (I saw requests on these two: system.posix_acl_default,
    system.posix_acl_access). Since need_lookup flag is set, during fuse_resolve
    a nameless lookup is executed on the inode(getxattr being inode operation,
    hence the nameless lookup). Since md-cache does not serve nameless lookup,
    a network hop is needed for each file, costing the time.
    
    With readdirp disabled, the getxattrs are served from md-cache itself(note:
    we are discussing the 2nd attempt of ls -l use case).
    
    _Current affairs around need of lookup for a file to populate it's ctx_:
    
    For the xlators on client stack we discussed quite extensively about the need
    for a lookup fop post readdirp in all three cluster translators - afr, EC and
    dht. EC and dht don't really need a nameless lookup post readdirp. For afr too,
    the need for lookup was negated with patch (http://review.gluster.org/6010 - AFRV2),
    where  afr added a function called afr_inode_refresh() which does a lookup and
    populates its inode context in case a FOP came to AFR without a lookup being issued
    prior to it.
    
    We ran a thread on gluster-devel asking for feedback on the need of explicit lookup
    post readdirp. For responses refer [1]. Refer [2] for discussions happened on gerrit.
    After gathering inputs from [1] and [2], it looks like there is no xlator in
    current state that requires an explicit lookup post readdirp to function properly.
    
    * A separate similar patch will be sent for gfapi/nfs/nfs-ganesha.
    
    Note: Only file's inode is built with readdirp.
    
    [1] http://lists.gluster.org/pipermail/gluster-devel/2017-August/053505.html
    [2] https://review.gluster.org/#/c/17985/
    
    Change-Id: Ie1d68ce7bea5e1f8a1fab9a62217f478322554f5
    BUG: 1492996
    Signed-off-by: Susant Palai <spalai@redhat.com>

commit 23649f9ab73448737ee5d9509502f96e4775dca3
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Sep 19 09:39:31 2017 +0530

    eventsapi: Fix issue with CLIENT_CONNECT event
    
    A mismatch in event format causing below error in events.log when
    it detects CLIENT_CONNECT event.
    
        [2017-09-19 09:35:06,785] WARNING [glustereventsd - 46:handle] -
        Unable to parse Event 1505793906 97
        client_uid=f241-16363-2017/09/19-04:05:06:747558-gv1-client-
        0-0-0;client_identifier=192.168.122.208:49150;server_identifier=
        192.168.122.208:49152;brick_path=/bricks/b1,subdir_mount=(null)
    
    BUG: 1492968
    Change-Id: Ie6d507725a7e6b54fca44651f9c5e66eca2be244
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/18322
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit dafffa7b8fdfd29edf6e92c31d74dd7abc8f4d6c
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Sep 18 11:48:43 2017 +0530

    Tests: disabling the check for volume client-list
    
    The client-list command is broken for brick-multiplexed.
    Disabling it until the fix is in so that the regression test
    can be resumed for the other test cases.
    
    Change-Id: Idcb5a09db0eb46fbe71c215109b5c55924cc1209
    BUG: 1492542
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/18308
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 7f70d38b66ce755f848ff0197814457a28b321df
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Sep 7 19:14:23 2017 +0530

    glusterd: disallow replace brick for dist only volumes
    
    Allowing replace-brick on dist only volumes will lead to data loss. This
    patch blocks replace brick commit force to fail if a volume is dist
    only.
    
    Also removing tests/basic/pump.t as its of no use as per the discussion
    in
    http://lists.gluster.org/pipermail/gluster-devel/2017-September/053652.html
    
    Change-Id: Iabb0c16f865f3fc361b64a19bfcf0c0fbb5c2682
    BUG: 1489432
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/18226
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f6775423d7fbe71fe35e6154388e77aae2e264ad
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Sep 15 19:01:53 2017 +0530

    events : Add brick list in EVENT_VOLUME_CREATE
    
    Change-Id: Ibf87ae5ca57f9d27c036f329a30c8f81b51c52bf
    BUG: 1492109
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/18306
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 00a4dc058a0573d18e9c1bd3692fecee151a9285
Author: luneo7 <luneo7@gmail.com>
Date:   Wed Aug 23 15:25:57 2017 -0300

    features/worm: Adding check to newloc when doing rename
    
    Problem: Since rename didn't check if newloc exists and it's
    retention state it was possible to rename a new file that wasn't
    in retention over a existing file that was in read-only state.
    
    Change-Id: I63c6bbabb7bb456ebedf201cc77b878ffda62229
    BUG: 1484490
    Signed-off-by: luneo7 <luneo7@gmail.com>
    Reviewed-on: https://review.gluster.org/18104
    Tested-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Karthik U S <ksubrahm@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit dabfc3116ae59b331f967c090c0c51eb3f0355fd
Author: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
Date:   Wed Aug 10 13:44:19 2016 +0530

    heal: New feature heal info summary to list the status of brick and count of entries to be healed
    
    Command output:
    Brick 192.168.2.8:/brick/1
    Status: Connected
    Total Number of entries: 363
    Number of entries in heal pending: 362
    Number of entries in split-brain: 0
    Number of entries possibly healing: 1
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <healInfo>
        <bricks>
          <brick hostUuid="9105dd4b-eca8-4fdb-85b2-b81cdf77eda3">
            <name>192.168.2.8:/brick/1</name>
            <status>Connected</status>
            <totalNumberOfEntries>363</numberOfEntries>
            <numberOfEntriesInHealPending>362</numberOfEntriesInHealPending>
            <numberOfEntriesInSplitBrain>0</numberOfEntriesInSplitBrain>
            <numberOfEntriesPossiblyHealing>1</numberOfEntriesPossiblyHealing>
          </brick>
        </bricks>
      </healInfo>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
    </cliOutput>
    
    Change-Id: I40cb6f77a14131c9e41b292f4901b41a228863d7
    BUG: 1261463
    Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
    Reviewed-on: https://review.gluster.org/12154
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Karthik U S <ksubrahm@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 60ff7a3ef012ffca4072406f3361d14775fbf20d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 14 09:24:59 2017 -0400

    rpc-transport/socket: tab -> spaces cleanup
    
    tired of review comments about use of tabs when the whole file uses tabs
    
    Change-Id: I4f822a53f47886da04282f9c3fb84d81a7b3f8d0
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18286
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e9acd3130374ce5d512b784310a729734e6655a5
Author: Michael Scherer <misc@redhat.com>
Date:   Fri Sep 8 18:45:12 2017 +0200

    Fix use-after-free in gf_rdma_do_reads
    
    If iobref_new can't allocate a ref, we free the iobuf, and
    then go to the cleanup part of the function, that will
    run iobuf_unref a 2nd time, which trigger a warning with
    coverity.
    
    Change-Id: Ie9cf7a5d5f98244a390e44e1403c614199eb650c
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/18245
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 777ad8f6a17d11e4582cf11d332a1a4d4c0c706f
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Wed Jul 19 18:40:38 2017 +0530

    Heal root xattr correctly upon an add-brick operation
    
    When an add-brick is performed the root path xattr is healed using a hook
    script. For a volume in stopped state, the hook script is triggered in post
    op of add-brick. Otherwise, if the volume is in started state the hook script
    is started on a subsequent volume start. The script unlinks itself after
    execution.
    The issue is that current hook script does not work when you have multiple
    volumes in stopped state. A hook script meant for volume1 can get trigerred
    during start of volume2.
    
    Fix: create separate hook script links for individual volumes.
    
    Bug: 1472609
    Change-Id: If5f056509505fdbbbf73d3363e9966047ae6a3d3
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Reviewed-on: https://review.gluster.org/17824
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e4a59b384f5bbaaeb937a53cef64f4e388f85153
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Sep 8 18:04:50 2017 +0530

    features/shard: Change default shard-block-size to 64MB
    
    Change-Id: I55fa87e07136cff10b0d725ee24dd3151016e64e
    BUG: 1489823
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/18243
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2ec0dfe76780a8f82f4f6f8b7b3fdfd54203b616
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Sep 12 14:53:41 2017 +0200

    glusterd: fix invalid memory reference returned
    
    Change-Id: I0823c7b33060b48040c1d86ad346a5f6e15bc190
    BUG: 1490897
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/18263
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>

commit 0643510e9852059b465e99f4ea255a3d3aeb9e86
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 12 15:34:15 2017 -0400

    rpc: TLSv1_2_method() is deprecated in OpenSSL-1.1
    
    Fedora 26 has OpenSSL-1.1. Compile-time warnings indicate
    that TLSv1_2_method() is now deprecated. As per the SSL man page:
    
      TLS_method(), TLS_server_method(), TLS_client_method()
        These are the general-purpose version-flexible SSL/TLS methods.
        The actual protocol version used will be negotiated to the highest
        version mutually supported by the client and the server. The
        supported protocols are SSLv3, TLSv1, TLSv1.1 and TLSv1.2.
        Applications should use these methods, and avoid the version-
        specific methods described below.
      ...
      TLSv1_2_method(), ...
      ...
    
    Note that OpenSSL-1.1 is the version of OpenSSL; Fedora 25 and RHEL 7.3
    and other distributions (still) have OpenSSL-1.0.
    
    TLS versions are orthogonal to the OpenSSL version.  TLS_method() is the
    new — in OpenSSL-1.1 — version flexible function intended to replace the
    TLSv1_2_method() function in OpenSSL-1.0 and the older (?), insecure
    TLSv23_method(). (OpenSSL-1.0 does not have TLS_method())
    
    Change-Id: I190363ccffe7c25606ea2cf30a6b9ff1ec186057
    BUG: 1491025
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18268
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 3edb0c293450432abbb8d405d1bc3f6e852b604b
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Sep 13 14:04:52 2017 +0530

    protocol/server: Remove duplicate dict_get_str
    
    dict_get_str() for auth-path has been already done once within switch
    case for RPCSVC_EVENT_DISCONNECT inside server_rpc_notify(). Therefore
    this change removes the needless dict_get_str.
    
    Change-Id: Ifeb3db828328df08a1f1612a8ad8e0babace1d16
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/18272
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ecc5b30289be1a63e2616733a022b3a9a35f12b7
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jun 21 12:56:14 2017 +0530

    socket: Use granular mutex locks during pollin and pollout event processing
    
    ... instead of one global lock. This is because pollin and pollout
    processing code operate on mutually exclusive members of
    socket_private_t. Keeping this in mind, this patch introduces
    the more granular priv->in_lock and priv->out_lock locks.
    
    For pollerr, which modifies both priv->incoming and priv->ioq, both
    locks need to be taken.
    
    Change-Id: Id7aeb608dc7755551b6b404470d5d80709c81960
    BUG: 1467614
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17687
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c6c526010fa4b9d9628e445036e8f84b00bfb9a8
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Sep 6 14:46:20 2017 +0200

    Fix the type of len, a warning is triggered
    
    clang show this warning on FreeBSD:
    
      posix.c:133:17: warning: comparison of unsigned expression < 0
      is always false [-Wtautological-compare]
    
    A closer look on the code show that sys_readlink is returning a ssize_t,
    not a size_t, who is unsigned.
    
    Change-Id: Idb6a440ea44cc2168b0dd85f791c7955caa67c8c
    BUG: 1488909
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/18220
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 91cd0ed2a444f868c4cc46a42363d0044294da93
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Sep 6 12:11:09 2017 +0200

    Fix the conditional
    
    Clang complain about it on FreeBSD
    
       In file included from xlators/performance/nl-cache/src/nl-cache-helper.c:11:
       In file included from xlators/performance/nl-cache/src/nl-cache.h:14:
       xlators/performance/nl-cache/src/nl-cache-mem-types.h:12:9: warning: '__NL_CACHe_MEM_TYPES_H__' is used as a header guard here, followed by #define of a different macro [-Wheader-guard]
       #ifndef __NL_CACHe_MEM_TYPES_H__
    
    Change-Id: I4327c7dacf10f2690bd33bf2b37dbb7d9b52bdd5
    BUG: 1488840
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/18216
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 30712dc7d300fb6bffd45f29d9e9ddd83468f38a
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Sep 6 11:44:06 2017 +0200

    Do not declare the variable timeout_ms if TCP_USER_TIMEOUT is not defined
    
    Trying to fix the build on FreeBSD, -Wunused-variable trigger this warning.
    
    Change-Id: I318121829ac6a609fe9c606aead257827c7748b1
    BUG: 1488829
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/18215
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 07c11798ed219c7d8484d4c1f4729cd83cd4a09e
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Sep 6 14:35:39 2017 +0200

    Fix clang/gcc warning -Wformat-extra-args
    
        umountd.c:59:61: warning: data argument not
        used by format string [-Wformat-extra-args]
        "Cannot access %s\n", path, strerror (errno));
    
    Change-Id: If1622d5b806ce6795ad2f84f2f2874227811dd96
    BUG: 1488906
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/18219
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit eb2f1ab4cd2f4805117c590d2f020b36ea778c7e
Author: Michael Scherer <misc@redhat.com>
Date:   Fri Sep 1 14:09:06 2017 +0100

    Use the new URL for the docs
    
    Change-Id: I0ef5c3980aed24a9fa2dda673f8293771ce81808
    BUG: 1487644
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/18182
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Nigel Babu <nigelb@redhat.com>
    Tested-by: Nigel Babu <nigelb@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b2902477414e5801f00a94b72cf0d0395297aa47
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 23 08:27:06 2017 +0200

    libglusterfs: fix run.c demo mode
    
    run.c can be compiled into a standalone object file
    or a demo program with the appropriate defines for
    development purposes. This functionality was broken.
    
    We fix it and also clean it up:
    - call it "demo mode" not "test mode" as tests should
      come with verification of the results of the invocation
      which is not being done
    - add comments to the source explaining the feature
    - provide more comprehensive output in the demo program
    
    This change does not affect standard compilation and
    usage of run.c functionality.
    
    BUG: 1454590
    Change-Id: I1ea618e3262bf6a4d9f79f6b59209438d5163244
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17363
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 84f8fb81d73b87463092eb082a5cc6a4055103f4
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Sep 5 23:58:15 2017 -0400

    mount/fuse: Include sub-directory in source argument for mount()
    
    With this, mount of a sub-directory 'foo' gets listed in /proc/mounts as:
    
    <hostname>:<volname>/foo on /mnt/glusterfs type fuse.glusterfs (rw,relatime...)
    
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    BUG: 1488913
    Change-Id: Ib1e1ac3741bf66e1a912d792f2948b748931f2b0
    Reviewed-on: https://review.gluster.org/18210
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 6826905213eb7e9bc8728e8269864f066ce0e23a
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Sep 6 11:02:01 2017 +0200

    Fix warning on FreeBSD, show by -Wformat-extra-args
    
    The warning is specific to FreeBSD, since both Linux and NetBSD
    do trigger a different codepath.
    
    Change-Id: I3d2b374b6a39804942af076d7e0d130a76f869a2
    BUG: 1488808
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/18214
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 47188e9eac59de416a5c86c7ec7540ed6aaa1c98
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Sep 5 15:18:58 2017 +0530

    dht: add FOP check to dht_file_setattr_cbk
    
    Problem:
    bug-797171.7 loaded error-gen xlator on the brick which sent EBADF for a
    non fd-based fop, namely setattr. This caused
    dht_check_and_open_fd_on_subvol_task() to crash as local->fd was NULL.
    
    Fix:
    Call dht_check_and_open_fd_on_subvol_task() from dht_file_setattr_cbk
    only for dht_fsetattr and not dht_setattr or dht_setattr2
    
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Change-Id: Iab4999e213bf2065804f3f8237e470ad454e3c99
    BUG: 1488399
    Reviewed-on: https://review.gluster.org/18208
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit ecef90aa414a4dcb0a0d520be2334f03d06a4451
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Aug 21 15:41:42 2017 +0530

    Command to identify client process
    
    command: gluster volume status <volname/all> client-list
    
    output:
    Client connections for volume v1
    Name                                                       count
    -----                                                     ------
    fuse                                                           2
    tierd                                                          1
    
    total clients for volume v1 : 3
    -----------------------------------------------------------------
    
    Client connections for volume v2
    Name                                                       count
    -----                                                     ------
    tierd                                                          1
    fuse.gsync                                                     1
    
    total clients for volume v2 : 2
    -----------------------------------------------------------------
    
    Updates: #178
    Change-Id: I0ff2579d6adf57cc0d3bd0161a2ec6ac6c4747c0
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/18095
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit b1b49997574eeb7c6a42e6e8257c81ac8d2d7578
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Aug 29 15:07:53 2017 +0530

    event/epoll: don't call handler for events received after a pollerr
    
    we register socket with EPOLLONESHOT, which means it has to be
    explicitly added back through epoll_ctl to receive more
    events. Normally we do this once the handler completes processing of
    current event. But event_select_on_epoll is one asynchronous codepath
    where socket can be added back for polling while an event on the same
    socket is being processed. event_select_on_epoll has a check whether
    an event is being processed in the form of slot->in_handler. But this
    check is not sufficient enough to prevent parallel events as
    slot->in_handler is not atomically incremented with respect to
    reception of the event. This means following imaginary sequence of
    events can happen:
    
    * epoll_wait returns with a POLLERR - say POLLERR1 - on a socket
      (sock1) associated with slot s1. socket_event_handle_pollerr is yet
      to be invoked.
    * an event_select_on called from __socket_ioq_churn which was called
      in request/reply/msg submission codepath (as opposed to
      __socket_ioq_churn called as part of POLLOUT handling - we cannot
      receive a POLLOUT due to EPOLLONESHOT) adds back sock1 for polling.
    * since sock1 was added back for polling in step 2 and our polling is
      level-triggered, another thread picks up another POLLERR event - say
      POLLERR2. socket_event_handler is invoked as part of processing
      POLLERR2 and it completes execution setting priv->sock to -1.
    * event_unregister_epoll called as part of __socket_reset due to
      POLLERR1 would receive fd as -1 resulting in assert failure.
    
    Also, since the first pollerr event has done rpc_transport_unref,
    subsequent parallel events (not just pollerr, but other events too)
    could be acting on a freed up transport too.
    
    Change-Id: I5db755068e7890ec755b59f7a35a57da110339eb
    BUG: 1486134
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/18129
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>

commit e50fc8f4e7eb51386f47bea9e6ca8d8490c09003
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 5 13:30:53 2017 +0530

    features/shard: Increment counts in locks
    
    Problem:
    Because create_count/eexist_count are incremented without locks, all the shards may not
    be created because call_count will be lesser than what it needs to be. This can lead
    to crash in shard_common_inode_write_do() because inode on which we want to do
    fd_anonymous() is NULL
    
    Fix:
    Increment the counts in frame->lock
    
    Change-Id: Ibc87dcb1021e9f4ac2929f662da07aa7662ab0d6
    BUG: 1488354
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/18203
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 91430817ce5bcbeabf057e9c978485728a85fb2b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 5 21:42:26 2017 +0530

    features/shard: Return aggregated size in stbuf of LINK fop
    
    Change-Id: I42df7679d63fec9b4c03b8dbc66c5625f097fac0
    BUG: 1488546
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/18209
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit b1352d0974328b367afa7360e9523585efb7178d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Aug 23 18:18:24 2017 +0200

    arbiter: return ENOSYS for 'non readable' FOPs
    
    AFR marks the arbiter as 'non readable'. This has been introduced with
    commit 8ab87137 (afr: do not set arbiter as a readable subvol in inode
    context). arbiter_readv() should not get called anymore, so it could be
    removed. However, it is a good defensive approach to have all the inode
    read FOPs that can not be handled by the arbiter to return ENOSYS.
    
    Change-Id: I6ea41680832859bd6790dc8d7440ee98d38205fc
    BUG: 1484722
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/18103
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c0406501f0b4295a9917d31574baa2e462a18799
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Sat Sep 2 06:50:50 2017 -0400

    scripts: mount.glusterfs contains non-portable bashisms
    
    Debian's default shell is dash, i.e. /bin/sh -> dash, which doesn't
    support bash extensions
    
    Reported-by: "Michael Lundkvist" <brels.debian@solske.net>
    Reported-by: pmatthaei@debian.org
    Debian BZ: 873878
    
    Change-Id: I33003183b9bc6459cae28c565125e6b2bd1eaa47
    BUG: 1487830
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18184
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit d692f167662300ffad8d3ed44672182130025c75
Author: Sunny Kumar <sunkumar@redhat.com>
Date:   Fri Aug 18 14:56:46 2017 +0530

    snapshot: clang compile warning
    
    Warning type: NO_EFFECT
    xlators/mgmt/glusterd/src/glusterd-snapshot.c:4004 : warning: comparison of
    constant -1 with expression of type 'gf_boolean_t' (aka 'enum _gf_boolean')
    is always false.
    
    solution : "timestamp" was formerly declared as gf_boolean_t, now changed to
                int.
    
    Change-Id: Ie461537f06fe2971e2b09a428a22331808c41a13
    BUG: 1335251
    Signed-off-by: Sunny Kumar <sunkumar@redhat.com>
    Reviewed-on: https://review.gluster.org/18062
    Tested-by: Sunny Kumar
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 37e16afa4853dcb5df6d6d0c91a6afd960c3a901
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat Sep 2 20:24:00 2017 +0530

    afr: discover/lookup heal fixes
    
    Addresses review comments in commit 468ca877807625817b72921d1e9585036687b640
    
    Change-Id: I04b1bd3b00abfd6758798d6272954e36a24249a9
    BUG: 1473636
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/18187
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8ebabb801cf976396f8756b8f620aad6e03fbc11
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Sat Sep 2 09:09:02 2017 -0400

    glusterd: spelling errors reported by Debian maintainer
    
    Reported-by: "Patrick Matthäi" <pmatthaei@debian.org>
    
    Change-Id: I0dd6b7d88ddf3c98e8083b75f8dd848babcfd30a
    BUG: 1487840
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18185
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 3737ed53caad69ddb0f5b3db2e3498c2d7df2dff
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Aug 18 17:12:05 2017 +0200

    mempool: fix code when GF_DISABLE_MEMPOOL is defined
    
    Problem: Run-time crash is observed when attempting to memset() a zero
    length buffer.
    
    Solution: When GF_DISABLE_MEMPOOL is set, mem_get() gets translated to a
    GF_MALLOC(). The size of the allocation does not need to relate to the
    available (but uninitialized) global memory pools. It is fine to
    allocate the exact amount of memory that was configured when the
    mem-pool was created.
    
    Change-Id: Iea0bff974bb771623a34d7a940e10cb0db0f90e1
    BUG: 1481199
    Reported-by: Milind Changire <mchangir@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/18034
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d7ccdb33c2e84bab25bf0898866104f8a85b4217
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Wed Aug 30 17:54:09 2017 +0800

    gfapi: adds a glfs_mem_header for exported memory
    
    glfs_free releases different types of data depends on memory type.
    Drop the depends of memory type of memory accounting,
    new macro GLFS_CALLOC/GLFS_MALLOC/GLFS_REALLOC/GLFS_FREE are added
    to support assign release function dynamically, it adds a separate
    memory header named glfs_mem_header for gfapi.
    
    Updates: #312
    Change-Id: Ie608e5227cbaa05d3f4681a515e83a50d5b17c3f
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/18092
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 75223c0a1b3c7bd65bb0c59449ed1fb0663cfdd3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 20 15:24:33 2017 +0530

    debug/delay-gen: Implement delay-generation feature
    
    Background:
    I was working on a customer issue where the disks were responding some times
    after seconds. It was becoming very difficult to recreate the issues in our
    labs, so had to come up with this feature.
    
    Requirements:
    We need an xlator which can delay x% of ops for y micro seconds.
    We should be able to enable delays for specific fops.
    
    This feature is modeled after error-gen. Most of the logic
    is borrowed from that xlator. This is a minimum implementation
    of the feature which satisfied the requirements I had. May be
    in future with more requirements and understanding of the problem
    further we can improve upon this implementation.
    
    Here are the commands and what they do:
    Enable delay-gen: (This is similar to how err-gen is enabled on the brick side)
    - gluster volume set <volname> delay-gen posix
    
    Set the percentage of fops that need to be delayed
    - gluster volume set <volname> delay-gen.delay-percentage 50
    Default is 10%
    
    Set the delay in micro seconds
    - gluster volume set <volname> delay-gen.delay-duration 500000
    Default is 100000
    
    Set comma separated fops to be delayed
    - gluster v set r2 delay-gen.enable read,write
    Default is all fops.
    
    Fixes #257
    Change-Id: Ib547bd39cc024c9cdb63754d21e3aa62fc9d6473
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17591
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d594900dbca92c356152be65fce16f77c402117c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 18 18:05:54 2017 +0530

    afr: check validity of afr_reply
    
    ...in various self-heal code paths.
    
    Originally found by Pranith in __afr_selfheal_name_impunge ()
    
    Also change __afr_selfheal_assign_gfid() to send lookup only on those
    bricks that don't have a gfid matching that of the source.
    
    Change-Id: I70a2ccd750a2af92c5fc36e0eefb2b6125404b4a
    BUG: 1482923
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/18065
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 24b95089a18a6a40e7703cb344e92025d67f3086
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Aug 30 11:25:29 2017 +0530

    rpc: destroy transport after client_t
    
    Problem:
    1. Ref counting increment on the client_t object is done in
       rpcsvc_request_init() which is incorrect.
    2. Ref not taken when delegating to grace_time_handler()
    
    Solution:
    1. Only fop requests which require processing down the graph via
       stack 'frames' now ref count the request in get_frame_from_request()
    2. Take ref on client_t object in server_rpc_notify() but avoid
       dropping in RPCSVC_EVENT_TRANSPORT_DESRTROY. Drop the ref
       unconditionally when exiting out of grace_time_handler().
       Also, avoid dropping ref on client_t in
       RPCSVC_EVENT_TRANSPORT_DESTROY when ref mangement as been
       delegated to grace_time_handler()
    
    Change-Id: Ic16246bebc7ea4490545b26564658f4b081675e4
    BUG: 1481600
    Reported-by: Raghavendra G <rgowdapp@redhat.com>
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/17982
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit a4c43ba9374b8f75a48d38a032353a0c7d311a73
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Aug 11 12:16:12 2017 +0530

    cluster/dht:  Log files skipped by rebalance
    
    There was no easy way to find out which files were
    skipped during a rebalance.
    Rebalance now logs a message for every skipped file
    using msgid 109126, making it easier to find
    all files that were skipped.
    
    Change-Id: I2cac7db7285e2f82354251f3ea4094827b0daf3e
    BUG: 1480445
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/18021
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: hari gowtham <hari.gowtham005@gmail.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9420022df0962b1fa4f3ea3774249be81bc945cc
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 29 21:12:51 2017 +0530

    cluster/dht: Aggregate xattrs only for dirs in dht_discover_cbk
    
    If dht_discover finds data files on more than one subvol,
    racing calls to dht_discover_cbk could end up calling
    dht_aggregate_xattr which could delete dictionary data
    that is being accessed by higher layer translators.
    Fixed to call dht_aggregate_xattr only for directories and
    consider only the first file to be found.
    
    Change-Id: I4f3d2a405ec735d4f1bb33a04b7255eb2d179f8a
    BUG: 1484709
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/18137
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b3c068ccd9125ffdfb6fbb3d2728f16ff8dda2eb
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Aug 29 00:17:03 2017 +0200

    mem-pool: count allocations done per user-pool
    
    Count the active allocations per 'struct mem_pool'. These are the
    objects that the calling component allocated and free'd in the memory
    pool for this specific type. Having this count in the statedump will
    make it easy to find memory leaks.
    
    Updates: #307
    Change-Id: I797fabab86f104e49338c00e449a7d0b0d270004
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/18074
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 3b5f4de6926780b34570731ad34992a4735dd410
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Aug 28 19:33:30 2017 +0530

    gluster-block: strict-o-direct should be on
    
    tcmu-runner is not going to open block with O_SYNC anymore
    so writes have a chance of getting cached in write-behind
    when that happens, there is a chance that on failover some
    data could be stuck in cache and be lost.
    
    BUG: 1485962
    Change-Id: If9835d914821dfc4ff432dc96775677a55d2918f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/18120
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit bf7b0b60b1710b19561a2f7c79c3be4d09842b2c
Author: Iblis Lin <iblis@hs.ntnu.edu.tw>
Date:   Mon Jul 31 11:25:07 2017 +0800

    posix: fix incorrect xattr list handling on FreeBSD
    
    Change-Id: I5be157259f0b665640aaa1eda68063bb19fd7b3d
    BUG: 1484246
    Signed-off-by: Pellaeon Lin <nfsmwlin@gmail.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/17917
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 3ec63650bb7fd874a5013e7be4a2def3b519c9b2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Aug 1 07:51:44 2017 -0400

    feature/posix: Enabled gfid2path by default
    
    Enable gfid2path feature by default. The basic
    performance tests are carried out and it doesn't
    show significant depreciation. The results are
    updated in issue.
    
    Updates: #139
    Change-Id: I5f1949a608d0827018ef9d548d5d69f3bb7744fd
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17950
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit ea8c9af0b4a91ef927bbeee9afdfa7d1cea6369f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Aug 29 00:16:22 2017 +0200

    mem-pool: track glusterfs_ctx_t in struct mem_pool
    
    In order to generate statedumps per glusterfs_ctx_t, it is needed to
    place all the memory pools in a structure that the context can reach.
    The 'struct mem_pool' has been extended with a 'list_head owner' that is
    linked with the glusterfs_ctx_t->mempool_list.
    
    All callers of mem_pool_new() have been updated to pass the current
    glusterfs_ctx_t along. This context is needed to add the new memory pool
    to the list and for grabbing the ctx->lock while updating the
    glusterfs_ctx_t->mempool_list.
    
    Updates: #307
    Change-Id: Ia9384424d8d1630ef3efc9d5d523bf739c356c6e
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/18075
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 83990996736c72f3131f66df35ea7bf2b3d3b5fa
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Aug 16 20:17:19 2017 +0530

    libglusterfs: Add new fields to volume_options struct
    
    The new fields are required to enable equivalent volume set and volgen
    features, and some more additional features in GD2. GD2 does not use a
    hard-coded volume options map like GD1, but builds such by reading the
    options tables directly from the xlators.
    
    The new fields being introduced into the volume options struct include
    the following,
    - op-version - version(s) the option was introduced in
    - deprecated - version(s) the option was deprecated in
    - flags - flags for the option (settable, client, global, force, doc etc.)
    - tags - descriptive tags that apply to this option, can be used to
    group options
    - validate_fn - custom option validation function
    
    Enums for currently available flags have also been defined. To avoid a
    naming clashes, the flag enums in GD1 have been renamed.
    
    Updates #302
    
    Change-Id: Ic7e08aef9e051beb47e8dc17d7f7be211aed308a
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: https://review.gluster.org/18059
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 3563a48af96b37453774afc08787d3e449c3f0f9
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 23 11:37:40 2017 -0400

    packaging: /run and /var/run; prefer /run
    
    Fedora packaging guidelines say to use /run. On newer Fedora and
    el7 /var/run is a symlink to ../run (i.e. /run). /run is a tmpfs
    file system that is mounted earlier than /var might be.
    
    See https://bugzilla.redhat.com/show_bug.cgi?id=1476794
    
    Change-Id: I9631d5aa854d7bc4f4dc0c9cac1a3cb19ea516f2
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18102
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>

commit 553ac4cc6da5c6cbc1e6c6f87dc3cdfd935c0880
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Aug 18 11:24:44 2017 -0400

    cluster/ec: coverity, fix for BAD_SHIFT
    
    This is how I would like to see this fixed.
    
    passes (eliminates the warning in) coverity.
    
    The use of uintptr_t as a bitmask is a problem IMO, especially on
    32-bit clients.
    
    Change-Id: I86e15d12939c610c99f5f96c551bb870df20f4b4
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18067
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 2645e730b79b44fc035170657e43bb52f3e855c5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Aug 4 16:29:51 2017 +0200

    mem-pool: add tracking of mem_pool that requested the allocation
    
    This renames the current 'struct mem_pool' to 'struct mem_pool_shared'.
    The mem_pool_shared is globally allocated and not specific for
    particular objects.
    
    A new 'struct mem_pool' gets allocated when mem_pool_new() is called. It
    points to the mem_pool_shared that handles the actual allocation
    requests. The 'struct mem_pool' is only used for accounting of the
    objects that the caller requested and free'd.
    
    All of these changes will be used to collect all the memory pools a
    glusterfs_ctx_t is consuming, so that statedumps can be collected per
    context.
    
    Updates: #307
    Change-Id: I6355d3f0251c928e0bbfc71be3431307c6f3a3da
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/18073
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit c96cb9fc28e4358c5d7246ce77b676113a63ce85
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Aug 6 17:21:51 2017 +0200

    statedump: add support for dumping basic mem-pool info
    
    With all the new 'struct mem_pool' infrastructure in place, it is now
    possible to fetch details about the memory pools that a glusterfs_ctx_t
    uses.
    
    This only captures the information from 'struct mem_pool', and not from
    the global 'struct mem_pool_shared' or the pool_sweeper thread. The
    current details help with detecting memory leaks.
    
    Updates: #307
    Change-Id: Idbc5ba136df50863e1e380b448061509896f2c23
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/18076
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 414d3e92fc56f08e320a3aa65b6b18e65b384551
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Aug 24 13:39:07 2017 +0530

    perf/qr: Use a ref-ed data to extract content
    
    qr_content_extract used dict_get to get the value of
    the GF_CONTENT_KEY key. dict_get does not ref the data
    before returning it so QR could be acting on freed memory
    if another thread deletes the key before then.
    This patch also fixes a race in dict_get_with_ref.
    
    Fix: Use dict_get_with_ref to retrieve the file contents.
    
    Change-Id: Ib1a7a70bb92eed7e70747ec530e0b3edc53127ec
    BUG: 1484709
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/18115
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ea48cae5df118d9b901e7d79cd8726b6f38d65a0
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Aug 24 12:35:03 2017 +0530

    Revert "rpc: disable client on disconnection from rebalance"
    
    This reverts commit 5b14c11d3cae38bc66006b02217ede485ae30dea.
    
    BUG: 1484225
    Change-Id: I3269d3fc64de3f3cc6f670ea564a87d7725e10fd
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/18113
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a894d44427649e99d4344a241dc2f9d584a9a691
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Aug 24 12:39:47 2017 +0530

    glusterd: disable rpc_clnt_t after relalance process disconnection
    
    Problem:
    glusterd continues to connect to rebalance process even after
    the socket connection has disconnected.
    
    Solution:
    rpc_clnt_disable() disables the rpc_clnt_t object and disarms
    all relevant timers and drops refs to the rpc_clnt_t object
    and the transport as well.
    
    Change-Id: I981d6f1cc0087037f1927062c2770a4d5026a619
    BUG: 1484225
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/18114
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 470fcc266215b48ddea65e9e641c4a750d6358db
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Fri Aug 18 19:46:47 2017 +0530

    glusterd: glusterd fails to start if peers file has blank line
    
    Problem:
    On start of glusterd service, glusterd fetch data from store, while
    parsing data from store if peers file consists of blank line glusterd
    fails to start.
    
    Fix:
    With this fix while parsing peers file glusterd will skip blank lines
    if it contains any.
    
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    
    Change-Id: I53cd65a54de5f57baef292b2118b70ffb7f99388
    BUG: 1482906
    Reviewed-on: https://review.gluster.org/18066
    Tested-by: Gaurav Yadav <gyadav@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit e893962deaabab8e934813f8a0443a8f94e009f2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Aug 8 10:12:14 2017 -0400

    geo-rep: Fix syncing of hardlink of symlink
    
    Problem:
    If there is a hardlink to a symlink on master
    and if the symlink file is deleted on master,
    geo-rep fails to sync the hardlink.
    
    Typical Usecase:
    It's easily hit with rsnapshot use case where
    it uses hardlinks.
    
    Example Reproducer:
    Setup geo-replication between master and slave
    volume and in master mount point, do the following.
    
     1. mkdir /tmp/symlinkbug
     2. ln -f -s /does/not/exist /tmp/symlinkbug/a_symlink
     3. rsync -a /tmp/symlinkbug ./
     4. cp -al symlinkbug symlinkbug.0
     5. ln -f -s /does/not/exist2 /tmp/symlinkbug/a_symlink
     6. rsync -a /tmp/symlinkbug ./
     7. cp -al symlinkbug symlinkbug.1
    
    Cause:
    If the source was not present while syncing hardlink,
    it was always packing the blob as regular file.
    
    Fix:
    If the source was not present while syncing hardlink,
    pack the blob based on the mode.
    
    Change-Id: Iaa12d6f99de47b18e0650e7c4eb455f23f8390f2
    BUG: 1432046
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reported-by: Christian Lohmaier <lohmaier+rhbz@gmail.com>
    Reviewed-on: https://review.gluster.org/18011
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit ee3d9ac7f2db3a4aa9186e08b5a1db62c3270188
Author: Prashanth Pai <ppai@redhat.com>
Date:   Wed Aug 9 16:34:39 2017 +0530

    glusterd: do not create .glusterfs/indices
    
    glusterd shouldn't concern itself with creating directories specific to
    certain xlators.
    
    The index xlator will now proceed creating './glusterfs/indices' dir
    only if the parent '.glusterfs' directory exists, which still fixes the
    original problem reported i.e 'volume start force' command shouldn't
    create brick path if it doesn't exist (BUG 1457202)
    
    This reverts most of the changes done by the commit
    b58a15948fb3fc37b6c0b70171482f50ed957f42
    
    Change-Id: I7fc52ad64dce220e336c218fb4d85933ca2e61c0
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: https://review.gluster.org/18003
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d165ffd7a5e19fa6d0c2f36be9b47280e3df8443
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Aug 17 17:04:35 2017 +0530

    Add Deepshika as Continuous Integration peer
    
    Change-Id: I49df7cd49dc2e73ab3f9c797cf8d5bf39372902a
    BUG: 1484215
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: https://review.gluster.org/18091
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Michael Scherer <misc@fedoraproject.org>

commit 5b14c11d3cae38bc66006b02217ede485ae30dea
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Aug 23 10:10:13 2017 +0530

    rpc: disable client on disconnection from rebalance
    
    Problem:
    glusterd rpc code path attempts to reconnect to rebalance process
    via the reconnect timer even after the rebalance process disconnection
    
    Solution:
    Set the clnt->disabled flag to 1 to avoid reconnection and cause
    the clnt object to be unref'd
    
    Change-Id: I4e38eaef45d2fdea86d25e9dff9f1af0cd29cf66
    BUG: 1484225
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/18093
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2c1ddc55d1de154e072710fee18652977c832fa9
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Aug 22 10:21:48 2017 -0400

    packaging: use rdma-core(-devel) instead of ibverbs, rdmacm
    
    Also disable rdma on armv7hl.
    
    Starting in Fedora 26 the rdma-core package replaces various
    (lib)ibverbs and (lib)rdmacm packages.
    
    Also apparently rdma never actually worked (even if ibverbs and
    rdmacm packages were built) for armv7hl. The new rdma-core excludes
    armv7hl.
    
    See https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WJHXQ3G6H7UMVERDCMUXBYDJTFABTGW3/
    and https://bugzilla.redhat.com/show_bug.cgi?id=1483278
    
    Even though rdma-core dates back to Fedora 26 this only makes the
    switch to rdma-core effective with Fedora 27 and later; rdma-core has
    Provides: (and Obsoletes:) for all the ibverbs and rdmacm packages
    which is why we haven't noticed this before now.
    
    Change-Id: I3cd4f2becb465569b2c8e5514d28c9adff534d26
    BUG: 1483995
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18088
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5f3ff9b33c286b30f2c6d2fadf53757b9f48859e
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Fri Aug 18 23:06:13 2017 +0530

    glusterd: replace-brick executing successfully when quorum does not met
    
    Problem:
    replace-brick command on a setup where quorum does not met executing
    successfully.
    
    Fix:
    With the fix glusterd is validating whether server is in quorum or not
    during replace-brick staging
    
    Change-Id: I8017154bb62bdcc6c6490e720ecfe9cde090c161
    BUG: 1483058
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/18068
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 96b33b4b278391ca8a7755cf274931d4f1808cb5
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Aug 16 12:58:52 2017 +0530

    cluster/dht: Reorder dir operations in gf_defrag_fix_layout
    
    Earlier, rebalance performed a fix-layout on a directory
    before healing its subdirectories. If there were a lot of
    subdirs, it could take a while before all subdirs were
    created on the newly added bricks. As dht_readdirp only lists
    dirs from their hashed subvol, those dirs which hashed to
    the newly added bricks but were not yet created on them were
    not listed.
    
    Now, the child dirs are listed and processed before the layout
    of the parent is fixed. This introduces a change in behaviour
    where files in subdirs are migrated before those in parent
    directories.
    
    Credit: Shyam <srangana@redhat.com>
    Github issue: #239
    
    Change-Id: I8ae7f24a510754cd8d1b31e5d608bcf1928599e2
    BUG: 1248393
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/18045
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 01abf7ee37702407403afcf9aa6c9019a0316e1d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Aug 17 10:54:02 2017 +0530

    glusterd: disallow volume specific options to be set with all as volume name
    
    All the .validate_fn defined in volume map entry table refers to volinfo
    object. And if we end up in trying to set a volume level option cluster
    wide glusterd results into a crash.
    
    Change-Id: I7c877aee0ff5c8c1d8c95662fdc8c8923355ae7b
    BUG: 1482344
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/18052
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 3998c28324c8907b9b3ade75c98a6a0e4591f23b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Aug 10 18:31:55 2017 +0530

    glusterd: introduce max-port range
    
    glusterd.vol file always had an option (commented out) to indicate the
    base-port to start the portmapper allocation. This patch brings in the
    max-port configuration where one can limit the range of ports which
    gluster can be allowed to bind.
    
    Fixes: #305
    Change-Id: Id7a864f818227b9530a07e13d605138edacd9aa9
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/18016
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>

commit 204d52a4b6c13d16132f67ee94f823fa23c11538
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Aug 11 10:20:14 2017 +0530

    glusterd: improve op-version error message
    
    In case of a heterogeneous cluster if an admin sets a volume option
    which is higher than the current op-version the current error message
    only displays the version number of the new tunable. Better use
    experience is to dump the supported op-version in the error message as
    well.
    
    Change-Id: Ib42dadc574a401f79364178cb41ad21fb0b4432b
    BUG: 1328994
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/18020
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Joe Julian <me@joejulian.name>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 9b11b90d30285942113bb1e2d2a662337a75511c
Author: Ryan Ding <ryan.ding@open-fs.com>
Date:   Wed Nov 16 10:52:34 2016 +0800

    glusterd: Fix the debug and error-gen turned on issue
    
    Problem:
    When enabling one of the debug or the error-gen xlator, both of
    them will be turned on together.
    The problem is that when adding debug xlators into the graph, its
    on/off status is ignored to be checked.
    
    Fix:
    When adding a debug xlator, check its status and skip those with
    a value of "off".
    
    Change-Id: Ifa79314ff337b60ee941cfb0308c1ccbe42d027f
    BUG: 1395492
    Signed-off-by: Zhang Huan <zhanghuan@open-fs.com>
    Reviewed-on: https://review.gluster.org/15849
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit def09c4fbb2805618715c5a125ddf482d7e53de3
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Jul 25 18:07:05 2017 +0530

    Infra to indentify process
    
    Problem: currently we can't identify which process is running and
    how many instances of it are available.
    
    Fix: name the process when its spawned and send it to the server
    and save it in the client_t
    
    The processes that abide by this change from this patch are:
    1) fuse mount,
    2) rebalance,
    3) selfheal,
    4) tier,
    5) quota,
    6) snapshot,
    7) brick.
    8) gfapi (by default. gfapi.<processname> if processname is found)
    
    Note: fuse gets a process name as native-fuse-client by default.
    If the user gives a name for the fuse and spawns it, it will be of
    this type --process-name native-fuse-client.<name_specified>.
    This can be made use by the process like aux mount done by quota,
    geo-rep, etc by adding another option in the aux mount " -o
    process-name=gsync_mount"
    
    Updates: #178
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Change-Id: Ie4d02257216839338043737691753bab9a974d5e
    Reviewed-on: https://review.gluster.org/17957
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 468ca877807625817b72921d1e9585036687b640
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jul 21 15:21:20 2017 +0530

    afr: heal metadata in discover code path
    
    During graph switch, if fuse sends nameless (gfid) lookups, afr takes
    the discover code path to serve it. If there are pending metadata heals,
    they do not happen unless an inode refresh happens as a part of
    discover (which is not guaranteed to happen always).
    
    This patch fixes it by attempting metadata heal as a part of discover,
    just like how it is done in lookup code path.
    
    Also removed creating superfluous  heal frames when launching heal.
    
    Change-Id: I49868649361ebe5d70b6ea150f4686169b6c3070
    BUG: 1473636
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17850
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Karthik U S <ksubrahm@redhat.com>

commit d396d358d4f0cfe87693179cfd13eb2a84ce62c2
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Aug 11 17:50:52 2017 +0530

    uss/svc: Send the first lookup to the normal graph
    
    When parent inode is not looked up before, the inode type
    won't be set. In this scenario we should send the lookup
    to the normal graph first.
    
    Change-Id: I5d3e53f5c1c33a17be32204f3114749d9b1e6db8
    BUG: 1480591
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/18028
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 811c7ba470a6488570485ec7401e565b8ab1be47
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Aug 10 13:13:39 2017 -0400

    packaging: /run and /var/run; prefer /run
    
    Fedora packaging guidelines say to use /run. On newer Fedora and
    el7 /var/run is a symlink to ../run (i.e. /run). /run is a tmpfs
    file system that is mounted earlier than /var might be.
    
    See https://bugzilla.redhat.com/show_bug.cgi?id=1476794
    
    Change-Id: I08d948a43c7698bebd26c88a673a7f77c2d317ca
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/18017
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 220d406ad13d840e950eef001a2b36f87570058d
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Wed Mar 2 17:42:07 2016 +0530

    glusterd: Gluster should keep PID file in correct location
    
    Currently Gluster keeps process pid information of all the daemons
    and brick processes in Gluster configuration file directory
    (ie., /var/lib/glusterd/*).
    
    These pid files should be seperate from configuration files.
    Deletion of the configuration file directory might result into serious problems.
    Also, /var/run/gluster is the default placeholder directory for pid files.
    
    So, with this fix Gluster will keep all process pid information of all
    processes in /var/run/gluster/* directory.
    
    Change-Id: Idb09e3fccb6a7355fbac1df31082637c8d7ab5b4
    BUG: 1258561
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: https://review.gluster.org/13580
    Tested-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit cfdcdd1b1fea3f30d9131dd36afab6efeef2bee0
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Aug 10 12:56:32 2017 +0530

    mgmt/glusterd: Provide more information in command message
    
    Problem:
    When more than one bricks are present on the same node,
    while creating a volume, we get a warning message that
    the setup is not optimal. We need to add more information
    in this error/warning.
    
    Solution:
    Add following line in current message.
    Bricks should be on different nodes to have best fault
    tolerant configuration.
    
    Change-Id: Ica72bd6e68dff7e41c37617f3b775a981fa40c69
    BUG: 1480099
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/18014
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 6a0112e2c101a5ccf39124e45020f22c7716da5c
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jul 27 14:20:31 2017 +0530

    protocol/server: Fix Wint-in-bool-context compiler warning
    
    Following warning is shown when compiled with gcc v7:
    
    server-helpers.c: In function ‘auth_set_username_passwd’:
    server-helpers.c:1282:65: warning: ?: using integer constants in boolean context [-Wint-in-bool-context]
    				ret = !((strcmp (data_to_str (passwd_data),
    				       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    						    password))?0: -1);
    						    ~~~~~~~~~~~~^~~~~
     CCLD server.la
    
    Previously we used to have integers being used in context where boolean
    values were intended with ternay oprations and it was hard to understand
    the logic. This change simplifies the logic so that it avoids the warning
    too.
    
    Change-Id: Ie533cf34f829b9fcfeb79f3d519a0ac3cb7f2ab8
    Updates: #259
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/17895
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 071559cb4745669c87198128ab73d7af2017e9bd
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jul 27 14:15:22 2017 +0530

    contrib/fuse-lib: Fix compiler warning within switch case
    
    Following warning is shown when compiled with gcc v7:
    
    mount.c: In function ‘gf_fuse_unmount_daemon’:
    mount.c:98:22: warning: statement will never be executed [-Wswitch-unreachable]
    		char c = 0;
    		     ^
     CCLD fuse.la
    
    We just need to move the relevant declaration statements to that switch
    case where it is valid and is being used.
    
    Change-Id: I8e50cc7cfcfc3bc88218cd69abbf516c08ee1648
    Updates: #259
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/17878
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 747a08d34e2a1e94d7fce68a3577370288bb1955
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 8 22:33:24 2017 +0530

    cluster/dht: EBADF handling for fremovexattr and fsetxattr
    
    Add EBADF handling for dht_fremovexattr and dht_fsetxattr.
    
    Change-Id: Ide0d5812dae79655d2565157e5baabcd753b4309
    BUG: 1476665
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17999
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c13d69babc228a2932994962d6ea8afe2cdd620a
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Aug 8 14:36:17 2017 +0530

    glusterd: Block brick attach request till the brick's ctx is set
    
    Problem: In multiplexing setup in a container environment we hit a race
    where before the first brick finishes its handshake with glusterd, the
    subsequent attach requests went through and they actually failed and
    glusterd has no mechanism to realize it. This resulted into all the such
    bricks not to be active resulting into clients not able to connect.
    
    Solution: Introduce a new flag port_registered in glusterd_brickinfo
              to make sure about pmap_signin finish before the subsequent
              attach bricks can be processed.
    
    Test:     To reproduce the issue followed below steps
              1) Create 100 volumes on 3 nodes(1x3) in CNS environment
              2) Enable brick multiplexing
              3) Reboot one container
              4) Run below command
                 for v in ‛gluster v list‛
                 do
                   glfsheal $v | grep -i "transport"
                 done
              After apply the patch command should not fail.
    
    Note:   A big thanks to Atin for suggest the fix.
    
    BUG: 1478710
    Change-Id: I8e1bd6132122b3a5b0dd49606cea564122f2609b
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17984
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit c63aa2239bc682739328e0aa6cbcb3279a72a8e2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Aug 7 12:14:23 2017 +0530

    posix: add null gfid checks
    
    ...in file/dir creation and lookup codepaths. The check is relaxed for
    fops coming from trash xlator at the moment until trash has client side
    logic to send the create fops with gfid-req.
    
    Also fixed the missing trash pid assignment in creates sent by trash
    xlator. Without this, truncated files won't be moved to .trashcan.
    
    Change-Id: Ieddd7f0634850e7c7010e4fbb4ad1eead35888c8
    BUG: 1478297
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17975
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit cdca1cb26a0aba390c6d8485c0d6d95e22ffc8bd
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Aug 4 14:46:38 2017 +0530

    cluster/dht: Check for open fd only on EBADF
    
    DHT fd based fops used to check if the fd was open
    on the cached subvol before winding the call. However,
    this introduced a performance regression of about
    30% for reads.
    
    This check was introduced to handle cases where files
    were migrated while IOs were happening. As this is not
    the common case, dht will now check if the fd is
    open on the cached subvol only if the call fails
    with EBADF.
    
    This will prevent a performance hit where a rebalance
    is not running.
    
    Change-Id: I2035a858d63c3fcd22bb634055bbb0ad01686808
    BUG: 1476665
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17976
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 111d6bda9259126b0429113c9b8ba479958a4398
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Aug 7 23:47:00 2017 +0530

    nfs : add NULL check for call state in nfs3_call_state_wipe
    
    Refcounting added for nfs call state in https://review.gluster.org/17696.
    This is based on assumption that call state won't NULL when it is freed.
    But currently gluster nfs server is crashing in different scenarios at
    nfs3_getattr() with following bt
    
    #0  0x00007ff1cfea9205 in _gf_ref_put (ref=ref@entry=0x0) at refcount.c:36
    #1  0x00007ff1c1997455 in nfs3_call_state_wipe (cs=cs@entry=0x0) at nfs3.c:559
    #2  0x00007ff1c1998931 in nfs3_getattr (req=req@entry=0x7ff1bc0b26d0, fh=fh@entry=0x7ff1c2f76ae0) at nfs3.c:962
    #3  0x00007ff1c1998c8a in nfs3svc_getattr (req=0x7ff1bc0b26d0) at nfs3.c:987
    #4  0x00007ff1cfbfd8c5 in rpcsvc_handle_rpc_call (svc=0x7ff1bc03e500, trans=trans@entry=0x7ff1bc0c8020, msg=<optimized out>) at rpcsvc.c:695
    #5  0x00007ff1cfbfdaab in rpcsvc_notify (trans=0x7ff1bc0c8020, mydata=<optimized out>, event=<optimized out>, data=<optimized out>) at rpcsvc.c:789
    #6  0x00007ff1cfbff9e3 in rpc_transport_notify (this=this@entry=0x7ff1bc0c8020, event=event@entry=RPC_TRANSPORT_MSG_RECEIVED, data=data@entry=0x7ff1bc0038d0)
        at rpc-transport.c:538
    #7  0x00007ff1c4a2e3d6 in socket_event_poll_in (this=this@entry=0x7ff1bc0c8020, notify_handled=<optimized out>) at socket.c:2306
    #8  0x00007ff1c4a3097c in socket_event_handler (fd=21, idx=9, gen=19, data=0x7ff1bc0c8020, poll_in=1, poll_out=0, poll_err=0) at socket.c:2458
    #9  0x00007ff1cfe950f6 in event_dispatch_epoll_handler (event=0x7ff1c2f76e80, event_pool=0x5618154d5ee0) at event-epoll.c:572
    #10 event_dispatch_epoll_worker (data=0x56181551cbd0) at event-epoll.c:648
    #11 0x00007ff1cec99e25 in start_thread () from /lib64/libpthread.so.0
    #12 0x00007ff1ce56634d in clone () from /lib64/libc.so.6
    
    This patch add previous NULL check move from __nfs3_call_state_wipe() to nfs3_call_state_wipe()
    
    Change-Id: I2d73632f4be23f14d8467be3d908b09b3a2d87ea
    BUG: 1479030
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/17989
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit bead74a6e085001225bc0704bad1a5db36dd75a1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 4 16:23:46 2017 +0530

    afr: Prevent null gfids in self-heal entry re-creation
    
    Change-Id: I5acb8bd0a19fc4e764d61e349bb690b5236ee610
    BUG: 1478297
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17981
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Karthik U S <ksubrahm@redhat.com>

commit e11296f8e52b7e3b13d21b41d4fa34baea878edf
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Aug 3 17:43:22 2017 +0530

    gfapi: Duplicate the buffer sent in setxattr calls
    
    Issue:
    The caller of glfs_setxattr sends a buffer to set as the value.
    We create a dict in which the pointer to the value is set.
    Underlying layers like md-cache take a ref on this dict to store
    the value for a longer time. But the moment setxattr is complete,
    the caller of glfs_setxattr can free the value memory.
    
    Solution:
    memcpy the setxattr value to the gluster buffer.
    
    Change-Id: I58753fe702e8b7d0f6c4f058714c65d0ad5d7a0a
    BUG: 1477488
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17967
    Reviewed-by: soumya k <skoduri@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ebc8237d8c445af208446c937f31aa311d1efb2c
Author: SonaArora <aarorasona@gmail.com>
Date:   Wed Jul 26 17:43:45 2017 +0530

    read-only : currently read-only doesn't implement fallocate
    
    PROBLEM STATEMENT: read-only should block fallocate call if its enabled,
    else pass to next xlator. Implemented this functionality in read-only.
    
    BUG: 1475300
    Change-Id: I57c51eb4f1519ba75d7291eba49554e6ed4a25eb
    Signed-off-by: SonaArora <aarorasona@gmail.com>
    Reviewed-on: https://review.gluster.org/17879
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Karthik U S <ksubrahm@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Karthik U S <ksubrahm@redhat.com>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 42c057a6d1a03dd2825a278393acb15d52220c8d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jul 31 23:38:20 2017 +0530

    posix: add sanity checks for removing the gfid symlink for directories
    
    ...during mkdir and rmdir. Otherwise, during entry self-heal, the
    directory could be left out without a .glusterfs symlink causing fops like
    opendir, readdir to fail.  The only chance the missing symlink will be
    created is when a fresh lookup comes on it.
    
    Change-Id: I2e1cf1bce8962ea80187edd8f6d73e0a09cf9f8e
    BUG: 1477169
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17945
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 6d1068ddb35be19df36210c9fcaa7ce97e2a376a
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Aug 4 08:52:31 2017 +0530

    Revert "cluster/dht: Check for open fd only on EBADF"
    
    This reverts commit 91c9f4a19fde4894576b398252c77f730832a26a.
    This patch needs to be reworked.
    
    Change-Id: I4c24f647c2b1abc68fc4e9fe6eb810418e2033aa
    BUG: 1476665
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17970
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2e7daeffef05c6100cbcc39f1be62935711db3eb
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Mon Jul 31 10:51:21 2017 +0530

    glusterd: Add geo-replication session details to get-state output
    
    This commit adds support to the get-state CLI to capture details
    on geo-replication session as obtained in
    `gluster volume geo-replication status detail` in its output.
    
    Fixes: #291
    Change-Id: I2fbcba70bfdaf439522637234805545194777ed4
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17941
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shubhendu Tripathi <shtripat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 590ae48c65a60c93c2e5407e3f663cef3daacc55
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jul 19 23:08:05 2017 +0530

    glusterfsd: allow subdir mount
    
    Changes:
    
    1. Take subdir mount option in client (mount.gluster / glusterfsd)
    2. Pass the subdir mount to server-handshake (from client-handshake)
    3. Handle subdir-mount dir's lookup in server-first-lookup and handle
       all fops resolution accordingly with proper gfid of subdir
    4. Change the auth/addr module to handle the multiple subdir entries
       in option, and valid parsing.
    
    How to use the feature:
    
    `# mount -t glusterfs $hostname:/$volname/$subdir /$mount_point`
    Or
    `# mount -t glusterfs $hostname:/$volname -osubdir_mount=$subdir /$mount_point`
    
    Option can be set like:
    
    `# gluster volume set <volname> auth.allow "/subdir1(192.168.1.*),/(192.168.10.*),/subdir2(192.168.8.*)"`
    
    Updates #175
    
    Change-Id: I7ea57f76ddbe6c3862cfe02e13f89e8a39719e11
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/17141
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f68887999e89d894c3125e3b26517221ad1543fc
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Aug 1 08:04:48 2017 -0400

    logging: localtime logging, cmdline, volume set option
    
    Despite the fact that appliances generally use UTC, some
    users really want log entries in localtime.
    
    fixes gluster/glusterfs#272
    
    feature page: https://review.gluster.org/17807
    
    Change-Id: I5fbf2c3eedd9eb128fb3f851dd67b2f4081c8bba
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16911
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit c7e5741f938e24b85976bf78ea7d84984a4e1e61
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Aug 1 01:38:00 2017 +0200

    tests: don't use hard coded value for glusterd workdir
    
    A number of test referred to /var/lib/glusterd,
    they were adjusted to use "$GLUSTERD_WORKDIR".
    
    (This has significance for proper test runs on non-Linux
    platforms -- see the following #define in glusterfs.h:
    
      #ifdef GF_LINUX_HOST_OS
      #define GLUSTERD_DEFAULT_WORKDIR DATADIR "/lib/glusterd"
      #else
      #define GLUSTERD_DEFAULT_WORKDIR DATADIR "/db/glusterd"
      #endif
    
    Ie. the glusterd workdir will typically be /var/db/glusterd
    instead of /var/lib/glusterd on non-Linux platforms.)
    
    BUG: 1476957
    Change-Id: I69ce3e1bb7a0c14ea85b60adbf8205f9aca46cd5
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17937
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit f17eefb6d9a91cfccc3bef3aa3ba08a9128b046e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jul 31 12:22:46 2017 -0400

    packaging: /var/lib/glusterd/options should be %config(noreplace)
    
    /var/lib/glusterd/options is where cluster.enabled-shared-storage is
    persisted. If the file is removed as part of an uninstall/reinstall
    or update then the state of shared storage could be lost.
    
    Change-Id: Ie18c3d883df71c1857fd6996d9c03ab247580b70
    BUG: 1476861
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17930
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 21aa6170151a19c0b9349374e97b517e9adb25f6
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon Dec 19 11:23:38 2016 +0530

    tests: Minor fix in error condition
    
    Change-Id: I2dcc8d88234d2ce92dd8506c61cb84ab253decab
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: https://review.gluster.org/16191
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>

commit 5c433f8f5834a4cae62d0375bfdb273242630f01
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Jul 21 12:14:25 2017 +0530

    tests/gfapi : add test case for nameless lookups in glfs_resolve_component()
    
    Plus address pending comment to add check for entry "" in glfs_resolve_component()
    
    Change-Id: I6063f776ce1cd76cb4c1b1f621b064f3dcc91e5c
    BUG: 1460514
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/17844
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 0cc24da2fd79dd8680b771475d2192db0b63e7de
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Aug 2 07:22:13 2017 +0530

    extras: Turn eager-lock off for gluster-block
    
    With the current implementation of eager-lock FINODELK is taking so much
    time that cassandra workload times out and errors out. AFR eager-locking
    needs to be changed similar to EC eager-locking to make things work
    as expected. In the interim, it is better to turn it off
    
    This is how the profile looks if eager-lock is turned on:
          0.35     628.26 us      64.00 us  129882.00 us          42278    FXATTROP
         17.45   16500.54 us     212.00 us  375829.00 us          79568       WRITE
         81.76  209862.12 us      15.00 us 1992486.00 us          29318    FINODELK
    
    This is how profile looks if eager-lock is turned off:
          1.87     283.71 us      65.00 us  298970.00 us          68346    FXATTROP
          6.33     199.04 us      13.00 us  373428.00 us         330524    FINODELK
         10.37    3151.47 us      53.00 us 1528484.00 us          34172       FSYNC
         81.31    5110.45 us     270.00 us 1519722.00 us         165244       WRITE
    
    BUG: 1477404
    Change-Id: I98026b1ecf30002ddac01be76f375c2e8c0b7838
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17954
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 1ae3747608797445c4a59569f93edc331e3626b0
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jul 31 09:48:09 2017 -0400

    scripts: invalid test(1) in extras/S32gluster_enable_shared_storage.sh
    
    test(1) man pages says -eq is for INTEGER compares, and = is for
    string compares.
    
    Also note the comment that -a and -o are ambiguous and to use
     test && test or test || test instead.
    
    This bug has existed since 2015! (yikes)
    
    Found while testing localtime logging and running glusterd in the
    foreground.
    
    Change-Id: Ia544f7295e247b981504d085ebc4c533ab60ba84
    BUG: 1476785
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17925
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit ab4ffdac9dec1867f2d9b33242179cf2b347319d
Author: Günther Deschner <gd@samba.org>
Date:   Fri Jul 28 13:38:16 2017 +0200

    md-cache: avoid checking the xattr value buffer with string functions.
    
    xattrs may very well contain binary, non-text data with leading 0
    values. Using strcmp for checking empty values is not the appropriate
    thing to do: In the best case, it might treat a binary xattr value
    starting with 0 from being cached (and hence also from being reported
    back with xattr). In the worst case, we might read beyond the end
    of a data blob that does contain any zero byte.
    
    We fix this by checking the length of the data blob and checking
    the first byte against 0 if the length is one.
    
    Signed-off-by: Guenther Deschner <gd@samba.org>
    Pair-Programmed-With: Michael Adam <obnox@samba.org>
    Change-Id: If723c465a630b8a37b6be58782a2724df7ac6b11
    BUG: 1476324
    Reviewed-on: https://review.gluster.org/17910
    Reviewed-by: Michael Adam <obnox@samba.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Poornima G <pgurusid@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e5db980504bc4ace037ea806ad89a1ca897150d5
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Jan 23 16:38:00 2017 +0530

    tier: separation of attach-tier from add-brick
    
    PROBLEM: Both attach tier and add brick have the same RPC
    and set of code. This becomes a hurdle while tring to implement
    add brick on a tiered volume.
    
    FIX: This patch separates the add brick and attach tier
    giving them separate RPCs.
    
    Change-Id: Iec57e972be968a9ff00b15b507e56a4f6dc398a2
    BUG: 1376326
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/15503
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 3023c4bd7651d4503830c36676cd08864e315cdf
Author: Michael Adam <obnox@samba.org>
Date:   Tue Jun 13 14:44:39 2017 +0200

    glusterd: streamline logic flow in glusterd_validate_quorum()
    
    Make an earlier exit when the volume is not of server quorum.
    Thereby it spares the actual quorum calculation in this case.
    This also increases the overall readability of the function.
    
    The patch is best seen with the --patience diff option to
    understand what it does (e.g. "git show --patience").
    
    Change-Id: Ifce50bc3f73d79d3d6226473661a83696d65149a
    BUG: 1476719
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: https://review.gluster.org/17924
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ed0a3acfccbbfc96f417d8dba880e3d070bb0043
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Jul 27 16:33:12 2017 +0530

    cluster/dht: Handle wrong rebalance status reporting
    
    Change-Id: Id91ef35f890055cd42b9a94462f92297c77f1fff
    Bug: 1475282
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17868
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit c7cc5049fc8965836926a6f1b3a3270ad1aa566d
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Jul 26 17:12:03 2017 +0530

    cluster/dht: rebalance min-free-disk fix
    
    To calculate available space on a subvolume we used to do
    the following in __dht_check_free_space.
    
    post_availspace = (dst_statfs.f_bavail * dst_statfs.f_frsize) - stbuf->ia_size
    
    Now to subtracting the file size from available space is tricky here.
    Sometime available space will be lesser than the file size and since all the
    participating members in calculation are unsigned int, the result is a large
    number (integer overflow).
    
    Solution: We do not need to subtract the file size from the space available,
    since fallocate would have reserved file size space already.
    
    Change-Id: I4f724358c44b9911933742ff3ff8d55b3dfda1cb
    BUG: 1475282
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17876
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 45c973576d6356dbe4da897e9f0528eac7529d48
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jul 25 09:25:53 2017 +0200

    nfs: use "/" as subdir for volume mounts
    
    For cases where subdir mounting is checked, it makes it much easier to
    return a subdir of "/" in case no subdir is passed. This reduces the
    number of corner cases where permissions are checked for subdir mounts,
    but not for volume mounts (or the other way around).
    
    The problem was identified by WebNFS mounting a volume, which got denied
    after commit e3f48fa2. Handling this would require an exception for
    non-subdir mounts, or make non-subdir mounts equal to subdir mounts.
    This change takes the 2nd approach.
    
    Change-Id: I0d810ae90b267a2cc3eac8d55368a0f1b0787f6a
    Fixes: e3f48fa2 ("nfs: add permission checking for mounting over WebNFS")
    BUG: 1468291
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17898
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 18cb1a87bb7c88657b499b22894b81f1f694b6ad
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Wed Jul 26 11:56:04 2017 -0700

    error-gen: fix randomness
    
    This generates errors in a truly random distribution, including streaks
    and dry spells, instead of just setting a constant interval between
    errors.  It also supports very small error probabilities, down to 1ppm
    instead of 1%.  Also cleaned up some bad logic in the "random-failure"
    case.
    
    Change-Id: I17b058c4b86b0aa17dd5706250e6d44f242fcd9d
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17886
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 91c9f4a19fde4894576b398252c77f730832a26a
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 31 12:32:59 2017 +0530

    cluster/dht: Check for open fd only on EBADF
    
    DHT fd based fops will now check if the fd is
    open on the cached subvol only if the call fails
    with EBADF.
    
    This will improve performance for scenarios where
    a rebalance is not running which would be most of
    the time.
    
    Change-Id: Idfaeb8927af769c6110d07a165a0fe2307369239
    BUG: 1476665
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17922
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 12906467f0f8df2edc07ea8412c0c6be6fae11b3
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Jul 28 15:18:29 2017 +0530

    ec/cluster: Update failure of fop on a brick properly
    
    Problem:
    In case of truncate, if writev or open fails on a brick,
    in some cases it does not mark the failure onlock->good_mask.
    This causes the update of size and version on all the bricks
    even if it has failed on one of the brick. That ultimately
    causes a data corruption.
    
    Solution:
    In callback of such writev and open calls, mark fop->good
    for parent too.
    
    Thanks Pranith Kumar K <pkarampu@redhat.com> for finding the
    root cause.
    
    Change-Id: I8a1da2888bff53b91a0d362b8c44fcdf658e7466
    BUG: 1476205
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/17906
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 96b179850d618c99d185ce7bfed5fe96e6cde919
Author: Michael Adam <obnox@samba.org>
Date:   Tue Jun 13 10:16:27 2017 +0200

    glusterd: improve intuitivity of check in glusterd_get_quorum_cluster_counts
    
    More intuitive to check for ret == 0 than !ret here...
    
    Change-Id: I8177a0bc8f266331187f5f2eeefea8a25cfcb30a
    Signed-off-by: Michael Adam <obnox@samba.org>
    BUG: 1476410
    Reviewed-on: https://review.gluster.org/17912
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e83ec8a65d0ef1a565ca66fa70d146b12ba1402a
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Thu Jul 27 09:03:40 2017 -0700

    glusterd: fix misleadingly named GF_FOR_EACH_ENTRY_IN_DIR
    
    What it really does is skip irrelevant entries like . and .. until
    we're at an entry we might actually care about.  Renamed to
    GF_SKIP_IRRELEVANT_ENTRIES accordingly.
    
    Change-Id: If0464451a8243c29c0a93b4c6f0f0eda2fade44c
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17901
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 1bc3cd9bd59e3826fd14fc239322f039d7a814da
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jul 26 16:17:03 2017 +0200

    changelog: add mem-pool initialization
    
    With recent changes to the mem-pool initialization,
    mem_pools_init_early() and mem_pools_init_late() need to be called
    before mem_get() is usable.
    
    This change has been tested manually with the included test from
    xlators/features/changelog/lib/examples/c/get-changes.c.
    
    Change-Id: I139563c4ff78a566cef2ff7e3da2ee10306def92
    BUG: 1475255
    Reported-by: Kotresh HR <khiremat@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17900
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 5fe8555800cbc9818e7c976f63499795a378cd8d
Author: Günther Deschner <gd@samba.org>
Date:   Wed Jul 26 18:10:33 2017 +0200

    md-cache: Use correct xattr keynames for virtual glusterfs ACLs.
    
    The "glusterfs.posix_acl." prefix does not catch the glusterfs posix acl
    xattr keynames which are
    
    	* "glusterfs.posix.acl" and
    	* "glusterfs.posix.default_acl"
    
    Using the GF_POSIX_ACL_ACCESS and GF_POSIX_ACL_DEFAULT defines directly
    is the savest option.
    
    Guenther
    
    Change-Id: I5aba64b26b6cbec850ea02316dd9f069400e857f
    BUG: 1476295
    Signed-off-by: Guenther Deschner <gd@samba.org>
    Reviewed-on: https://review.gluster.org/17909
    Reviewed-by: Michael Adam <obnox@samba.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit de69fb7ac819c7e92d132a5ead12ea317ef1ec20
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jul 27 07:32:36 2017 -0400

    geo-rep: Convert gfid mismatch logs to structured logging
    
    Convert the logs related to entry failures fix
    due to gfid mismatch logs into structured logging
    format
    
    Change-Id: I9bce950c5339b48d3ec8b84bddee38b0473b7634
    Updates: #246
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17896
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 1ae254ddcf397b101d291342272e13af25b0b1a1
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jul 20 17:08:12 2017 +0530

    tools/setgfid2path: Tool to set GFID to Path xattr in brick backend
    
    Once storage/gfid2path feature is enabled using `gluster volume set
    <volname> storage.gfid2path enable`, it starts recording the gfid2path
    xattr on each files. But this feature will not add xattr to the existing
    files.
    
    This tool accepts the file path as argument and sets the necessary xattr
    required for this feature.
    
    Change-Id: I75ad82c86ce482950645e687ff2e33b413fa53da
    Updates: #139
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17839
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b5fa5ae05f73e03023db37e43fb203267b719160
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jul 26 16:16:11 2017 +0200

    mem-pool: track and verify initialization state
    
    It is possible that pthread_getspecific() returns a non-NULL value in
    case the pthread_key_t is not initialized. The behaviour for
    pthread_getspecific() is not defined in this case. This can happen when
    applications use mem-pools from libglusterfs.so, but did not call
    mem_pools_init_early().
    
    By tracking the status of the mem-pools initialization, it is now
    possible to prevent calling pthread_getspecific() in case the
    pthread_key_t is not initialized. In future, we might want to exend this
    more to faciliate debugging.
    
    Reported-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Change-Id: I6255419fe05792dc78b1eaff55bc008fc5ff3933
    Fixes: 1e8e62640 ("mem-pool: initialize pthread_key_t pool_key in mem_pool_init_early()")
    BUG: 1475255
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17899
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d685e4238fafba8f58bf01174c79cb5ca35203e5
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jul 26 08:09:31 2017 -0400

    geo-rep: Fix syncing of self healed hardlinks
    
    Problem:
    In a distribute replicate volume, if the hardlinks
    are created when a subvolume is down, it gets
    healed from other subvolume when it comes up.
    If this subvolume becomes ACTIVE in geo-rep
    there are chances that those hardlinks won't
    be synced to slave.
    
    Cause:
    AFR can't detect hardlinks during self heal.
    It just create those files using mknod and
    the same is recorded in changelog. Geo-rep
    processes these mknod and ignores it as
    it finds gfid already on slave.
    
    Solution:
    Geo-rep should process the mknod as link
    if the gfid already exists on slave.
    
    Change-Id: I2f721b462b38a74c60e1df261662db4b99b32057
    BUG: 1475308
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17880
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit ab2558a3e7a1b2de2d63a3812ab4ed58d10d8619
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sun Jul 16 15:16:56 2017 -0400

    storage/posix: Add virtual xattr to fetch path from gfid
    
    The gfid2path infra stores the "pargfid/bname" as on xattr
    value for each non directory entry. Hardlinks would have a
    separate xattr. This xattr key is internal and is not
    exposed to applications.  A virtual xattr is exposed for
    the applications to fetch the path from gfid.
    
    Internal xattr:
    trusted.gfid2path.<xxhash>
    
    Virtual xattr:
    glusterfs.gfidtopath
    
    getfattr -h -n glusterfs.gfidtopath /<aux-mnt>/.gfid/<gfid>
    
    If there are hardlinks, it returns all the paths separated
    by ':'.
    
    A volume set option is introduced to change the delimiter
    to required string of max length 7.
    
    gluster vol set gfid2path-separator ":::"
    
    Updates: #139
    Change-Id: Ie3b0c3fd8bd5333c4a27410011e608333918c02a
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17785
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 1477fa442a733d7b1a5ea74884cac8f29fbe7e6a
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Tue Jul 18 16:23:18 2017 +0530

    glusterd : glusterd fails to start when  peer's network interface is down
    
    Problem:
    glusterd fails to start on nodes where glusterd tries to come up even
    before network is up.
    
    Fix:
    On startup glusterd tries to resolve brick path which is based on
    hostname/ip, but in the above scenario when network interface is not
    up, glusterd is not able to resolve the brick path using ip_address or
    hostname With this fix glusterd will use UUID to resolve brick path.
    
    Change-Id: Icfa7b2652417135530479d0aa4e2a82b0476f710
    BUG: 1472267
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/17813
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit fc0fce2c8f0f4c9ca373fdc754cab6359c9fcdcb
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Jul 27 09:25:32 2017 +0530

    changetimerecorder: Brick process crashed at ctr xlator in notify function
    
    Problem: Sometime brick process is getting crash in notify function at the
             time of cleanup db connection while brick mux is enabled.
    
    Solution: In changetimerrecorder (ctr) notify function after cleanup
              db connection set to db_conn to NULL to avoid reuse the same
              db connection again.
    
    Note: Below is the backtrace pattern showing by brick process
          #0  0x00007ff98a30c1f7 in raise () from /lib64/libc.so.6
          #1  0x00007ff98a30d8e8 in abort () from /lib64/libc.so.6
          #2  0x00007ff98a34bf47 in __libc_message () from /lib64/libc.so.6
          #3  0x00007ff98a351b54 in malloc_printerr () from /lib64/libc.so.6
          #4  0x00007ff98a3537aa in _int_free () from /lib64/libc.so.6
          #5  0x00007ff97d95e311 in gf_sql_connection_fini (sql_connection=sql_connection@entry=0x7ff8e8496b50) at gfdb_sqlite3.c:42
          #6  0x00007ff97d95e38a in gf_sqlite3_fini (db_conn=0x7ff92ca04470) at gfdb_sqlite3.c:507
          #7  0x00007ff97d957156 in fini_db (_conn_node=0x7ff92ca04470) at gfdb_data_store.c:326
          #8  0x00007ff97db78679 in notify (this=0x7ff92c5b3670, event=9, data=0x7ff92c5b5a00) at changetimerecorder.c:2178
          #9  0x00007ff98bca0dc2 in xlator_notify (xl=0x7ff92c5b3670, event=event@entry=9, data=data@entry=0x7ff92c5b5a00) at xlator.c:549
          #10 0x00007ff98bd3ac12 in default_notify (this=this@entry=0x7ff92c5b5a00, event=9, data=data@entry=0x7ff92c5b6d50) at defaults.c:3139
    
    BUG: 1475632
    Change-Id: Idd4bfdb4629c4799ac477ade81228065212683fb
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17888
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit cec5036f7e99ae265bb5e0e7f3df30166466eb2c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 27 14:11:27 2017 +0200

    libglusterfs: the global_xlator should have valid cbks
    
    There is a case where Gluster/NFS needs to resolve a path outside of the
    nfs-xlator itself. While resolving the path to fetch the GFID for
    creating the NFS-filehandle, gfapi may set an inode-ctx through
    glfs_resolve_at(). This inode-ctx is linked with the global_xlator.
    
    Because the global_xlator does not have any cbks, loc_wipe() will cause
    a segfault when it calls inode_unref() and xl->cbks->forget(). It is
    assumed that all xlators have a cbks symbol, otherwise loading of the
    xlator will fail. The global_xlator is not loaded in the same way, so
    there is no failure noticed when the instance is created. By adding an
    empty `struct xlator_cbks`, the global_xlator behaves similat to other
    xlators that do not implement all callbacks.
    
    I would have preferred to keep the inode-ctx setting through
    glfs_resolve_at() contained within Gluster/NFS. Unfortunately
    Gluster/NFS also uses the inode-ctx, and is not prepared to see the
    values that glfs_resolve_at() stores there.
    
    This problem is not easily reproducible because it involves mounting
    over WebNFS (like Solaris 10 can do). The segfault will also not be
    immediate, unless the following is done:
    
    1. create a subdir on a volume
    2. mount the volume/subdir over WebNFS
    3. unmount the volume/subdir
    4. mount the root of the volume
    5. delete the subdir on the volume -> segfault of Gluster/NFS
    
    Change-Id: I2bd71d033e97edc07ba93b2d4ada558f65d68999
    BUG: 1468291
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17897
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit de2158296f3afd253e10386acb2e2bd471e2b3ca
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Jul 26 16:47:16 2017 +0530

    build: Add stamp-h2 to gitignore
    
    Recent change https://review.gluster.org/17206 which adds site.h to
    sources results in the generation of another timestamp file named
    'stamp-h2'. This change adds 'stamp-h2' also to gitignore.
    
    Change-Id: I2592a283ec13e99b547b38c8b374874e50d5e3c1
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/17877
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit abfbc3eb821e144ddbfdc5d7da401557b52beaf1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 26 20:27:08 2017 +0530

    group-gluster-block: Set default shard-block-size to 64MB
    
    With 4MB shard size I/O slows down more because of the extra
    inodelk/xattrops in replicate. So increasing it to 64MB which
    gave better performance than 4MB.
    
    To simulate writes on a preallocated VM-image, fallocate the file and then do
    dd with notrunc
    do "fallocate -l 1GB" then "dd if=/dev/zero of=file-1GB bs=1MB count=1024 conv=notrunc"
    
    These are the results on my laptop for dd:
    With 4MB:
          1.84    1357.37 us      19.00 us   12431.00 us           1188    FINODELK
          2.45     255.08 us      58.00 us    4038.00 us           8428       WRITE
         95.69   78967.76 us      30.00 us 20324240.00 us           1063    FXATTROP
    
    With 64MB:
          0.13      59.36 us      15.00 us     814.00 us            657    FINODELK
          6.02     225.53 us      69.00 us    6556.00 us           8205       WRITE
         93.82  103015.12 us      32.00 us 13046368.00 us            280    FXATTROP
    
    BUG: 1475605
    Change-Id: I4ed5441409df639e38c731ba0d140fe92902f25f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17887
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 16e8d03c7e4afa4c0e186f8ea50389fc3735e879
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Tue Jul 25 17:40:49 2017 -0700

    glusterd: make peerfile parsing more robust
    
    Differential Revision: https://phabricator.intern.facebook.com/D5498639
    
    Change-Id: I3184ed8f3dadbdcffd46f4ade855fa93131efa82
    BUG: 1462969
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17885
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit b90e12134af85635199750967c326761d6c06e86
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri May 17 12:52:32 2013 +0530

    performance/io-cache: update inode contexts of each entry in readdirplus
    
    io-cache stores read-cache in inode which is currently created only in
    lookup. But, with readdirplus and md-cache absorbing lookups, io-cache
    need not receive a lookup before a fop like readv.
    
    Change-Id: I6eba995b0a90d4d5055a4aef0489707b852da1b8
    BUG: 1474180
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/5029
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 302aaeeddc64cd31997a4965b81ba772cd1b36c6
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Jul 25 11:43:37 2017 +0530

    cluster/dht: change log level to debug for thread activity
    
      Every time all the thread sleeps or wakes up, we log a message
    about that event. Sometime this can be noisy where the number of
    files eligible to be migrated are placed far away from each other.
    
    Moving the logs to DEBUG.
    
    Change-Id: I4dc2cc9fdf4f42d4001754532a5bc4aeb3f0f959
    BUG: 1474639
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17866
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 40d71d6a201d618e52555a062ac1a429d36ca9ca
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jul 22 16:36:42 2017 +0200

    gfapi: mark glfs_ipc() for internal use only
    
    The 3.7 version of glfs_ipc() has never been used by external
    applications. There is little use for internal xlator communication that
    is triggered from outside of core GlusterFS executables. This function
    has now been removed from libgfapi.so.
    
    For Gluster 4.0 a new variation for glfs_ipc() has been added. The
    function expects dict_t parameters, which are currently not available
    for external applications. There is no sense in providing glfs_ipc() for
    non-core GlusterFS executables. Therefore, glfs_ipc() has been marked as
    private, and the declaration is now in the glfs-internal.h header.
    
    The Python test case (tests/features/ipctest.py) is not correct and will
    be re-written in C to prevent portability issues. This test is currently
    disabled (commit d26f0bac149d495fa93710c3f7b6b63c36cb8387).
    
    Change-Id: Idbfe35570d34d45ce8b6b43084627a552ac21f59
    Fixes: #269
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17854
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit c136024613c697fec87aaff3a070862b92c57977
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Jul 26 12:46:42 2017 +0530

    cli: error out incomplete CLI commands
    
    cli_cmd_bricks_parse () & cli_cmd_volume_remove_brick_parse () were not
    handling the the error cases where the command is incomplete with
    missing brick details which could lead to glusterd crashes.
    
    Credit : george.lian@nokia.com
    
    Change-Id: Ia6303457a2aa279465aa75d4e1cfcc948893d5de
    BUG: 1396327
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17870
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 555990188ae7fabd4ca36c07ddaa92a39dccc813
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 24 19:47:07 2017 +0530

    glusterd: highlight arbiter brick in get-state
    
    Fixes: #278
    Change-Id: I1af5255127457a70e6362a2c20c53ee533e27c29
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17864
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Shubhendu Tripathi <shtripat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e21c915679244ddc1fae886e52badf02b4d95efc
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 24 18:27:39 2017 +0530

    cluster/dht: Fix negative rebalance estimates
    
    The calculation of the rebalance estimates will start
    after the rebalance operation has been running for 10
    minutes. This patch also changes the cli rebalance status
    code to use unsigned variables for the time calculations.
    
    Change-Id: Ic76f517c59ad938a407f1cf5e3b9add571690a6c
    BUG: 1457985
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17863
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 24ab0ef44a1646223b59e33d0109d8424f8eddd0
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jul 25 14:28:00 2017 +0530

    cluster/dht: Update size processed for non-migrated files
    
    The size of non-migrated files was not added to the
    size_processed causing incorrect rebalance estimate
    calculations. This has been fixed.
    
    Change-Id: I9f338c44da22b856e9fdc6dc558f732ae9a22f15
    BUG: 1467209
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17867
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6e41b17d855cf680efb93414083cf1490007d3ce
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jul 21 12:06:20 2017 +0200

    glusterd: fix compile warning in glusterd_volinfo_copy_brickinfo()
    
    gcc 7 (default in Fedora 26) complains about the following:
    
        glusterd-utils.c: In function ‘glusterd_volinfo_copy_brickinfo’:
        glusterd-utils.c:4279:54: warning: comparison between pointer and zero character constant [-Wpointer-compare]
                                 if (old_brickinfo->real_path == '\0') {
                                                              ^~
        glusterd-utils.c:4279:29: note: did you mean to dereference the pointer?
                                 if (old_brickinfo->real_path == '\0') {
                                     ^
    
    Comparing a char* with a char is not correct in any case. Instead,
    compare it to NULL and the char[0] with '\0'.
    
    Change-Id: Ie5b925cd200416a1e2fa035046005f421994e641
    Updates: #259
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17847
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit eb266ade1e2da5739ed66495755ec2784a5bf74b
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sat Jul 15 17:55:14 2017 +0530

    posix: Needs to reserve disk space to prevent the brick from getting full
    
    Problem: Currently there is no option available at posix xlator to save the
             disk from getting full
    
    Solution: Introduce a new option storage.reserve at posix xlator to
              configure disk threshold.posix xlator spawn a thread to update the
              disk space status in posix private structure and same flag is checked
              by every posix fop before start operation.If flag value is 1 then
              it sets op_errno to ENOSPC and goto out from the fop.
    
    BUG: 1471366
    Change-Id: I98287cd409860f4c754fc69a332e0521bfb1b67e
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17780
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 7140858c3816c89d22d81ddfaa1d270db5dfd622
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Jul 21 15:48:23 2017 +0530

    rpc: prevent logging null client [Invalid argument]
    
    The following log entry is observed during volume operations such
    as volume create:
    
    [2017-07-20 05:13:43.213797] E [client_t.c:321:gf_client_ref]
    (-->/usr/local/lib/libgfrpc.so.0(rpcsvc_request_create+0x1a4) [0x7f987f66cd20]
    -->/usr/local/lib/libgfrpc.so.0(rpcsvc_request_init+0xd0) [0x7f987f66ca23]
    -->/usr/local/lib/libglusterfs.so.0(gf_client_ref+0x56) [0x7f987f91cbd5] )
    0-client_t: null client [Invalid argument]
    
    Change-Id: I49ba753e8d1a828bb275b0ccb1a181706774f387
    BUG: 1193929
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: https://review.gluster.org/17848
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8c3e766fe0a473734e8eca0f70d0318a2b909e2e
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 24 17:48:47 2017 +0530

    cluster/dht: Correct iterator for decommissioned bricks
    
    Corrected the iterator for looping over the list of
    decommissioned bricks while checking if the new target
    determined because of min-free-disk values has been
    decommissioned.
    
    Change-Id: Iee778547eb7370a8069e954b5d629fcedf54e59b
    BUG: 1474318
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17861
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8dcf91660e0bd10eb75ef25a29ca02ec51c81be4
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Sun Jul 23 22:07:34 2017 +0530

    glusterd: Add option to get all volume options through get-state CLI
    
    This commit makes the get-state CLI capable to returning the values
    for all volume options for all volumes. This is similar to what you
    get when you issue a `gluster volume get <volname> all` command.
    
    This is the new usage for the get-state CLI:
    
     # gluster get-state [<daemon>] [[odir </path/to/output/dir/>] \
    [file <filename>]] [detail|volumeoptions]
    
    Fixes: #277
    Change-Id: Ice52d936a5a389c6fa0ba5ab32416a65cdfde46d
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17858
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 669868d23eaeba42809fca7be134137c607d64ed
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jul 19 16:14:59 2017 +0530

    storage/posix: Use the ret value of posix_gfid_heal()
    
    ... to make the change in commit acf8cfdf truly useful.
    
    Without this, a race between entry creation fops and lookup
    at posix layer can cause lookups to fail with ENODATA, as
    opposed to ENOENT.
    
    Change-Id: I44a226872283a25f1f4812f03f68921c5eb335bb
    BUG: 1472758
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17821
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1431786305055e0fe90e012e03278f504a2d8d14
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 24 17:54:07 2017 +0530

    glusterd: add rebal estimates time in get-state
    
    Fixes: #279
    Change-Id: If62fa59042604c9450749d3012c7a962ed0eb374
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17862
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit febf5ed4848ad705a34413353559482417c61467
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 23 13:10:56 2017 +0530

    posix: option to handle the shared bricks for statvfs()
    
    Currently 'storage/posix' xlator has an option called option
    `export-statfs-size no`, which exports zero as values for few
    fields in `struct statvfs`. In a case of backend brick shared
    between multiple brick processes, the values of these variables
    should be `field_value / number-of-bricks-at-node`. This way,
    even the issue of 'min-free-disk' etc at different layers would
    also be handled properly when the statfs() sys call is made.
    
    Fixes #241
    
    Change-Id: I2e320e1fdcc819ab9173277ef3498201432c275f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/17618
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 0b3fec6924cad5c9f38941550ab4106972efa5cc
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 24 11:31:56 2017 +0530

    extras: Disable remote-dio in gluster-block profile
    
    gluster-block file is opened with O_DIRECT but because block-profile has
    remote-dio enabled, it is leading to high latency for fsync which leads to
    failures in cassandra. Disabling remote-dio fixed this issue. We need to change
    remote-dio to disabled in gluster-block.
    
    BUG: 1474190
    Change-Id: Ifd845ea9cbdcc08dd6073faca6082682af376ca3
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17856
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 96eece8abbb9c06f0b91f37e718ac9e337a3f714
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jul 10 10:31:27 2017 -0400

    posix/gfid2path: Block access to gfid2path xattr via mount
    
    gfid2path xattr is an internal xattr and should not be
    allowed to modify by other applications via gluster
    mount. This patch blocks the same.
    
    Updates: #139
    Change-Id: Id2cb29797ee1bd77e0e0d2203a47469fd7203355
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17744
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 668df4e7e452aa26f0e0fbd15691fab0edc83014
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Jul 20 02:54:30 2017 +0530

    tests: replace brick failure shouldn't corrupt volfiles
    
    This is a test to present the known issue. It will be skipped as it has
    the known issue marker.
    
    Change-Id: Id6fa5d323abe0bc76a58cd92cb8e52fcde41b49b
    BUG: 1473026
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: https://review.gluster.org/17828
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ed6efab247b48c2c543a59c6d7adc30848d4a821
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 20 16:59:32 2017 +0200

    libglusterfs: prevent compile warnings with roof() and floor()
    
    gcc 7 (default in Fedora 26) complains about the roof() and floor()
    macros:
    
        stripe.c: In function 'stripe_truncate':
        stripe.c:701:49: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
             tmp_offset = roof(offset, fctx->stripe_size *
        ../../../../libglusterfs/src/common-utils.h:55:35: note: in definition of macro 'roof'
         #define roof(a,b) ((((a)+(b)-1)/((b)?(b):1))*(b))
                                           ^
        stripe.c:704:50: warning: '*' in boolean context, suggest '&&' instead [-Wint-in-bool-context]
             tmp_offset = floor(offset, fctx->stripe_size *
        ../../../../libglusterfs/src/common-utils.h:56:28: note: in definition of macro 'floor'
         #define floor(a,b) (((a)/((b)?(b):1))*(b))
                                    ^
    
    The calculations done in stripe_truncate() look safe enough, but gcc
    does not seem to like the passing the int/size_t to the `((b)?(b):1)`
    compact if-statement, so use `b != 0` for the test.
    
    Change-Id: If9fa4b8e86ba4b2ace61b1e05a5c28050fe4a7d3
    Updates: #259
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17842
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6b89b8cee79aa54ded4c34d3209c54ed674b1364
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 20 02:20:29 2017 +0530

    crypt: fix evaluation of args to macro
    
    GCC 7 warns about the following
    
    crypt.c:3685:31: warning: ?: using integer constants in boolean context,
    the expression will always evaluate to ‘true’ [-Wint-in-bool-context]
            local->op_ret < 0 ? -1 : 0,
    ../../../../libglusterfs/src/stack.h:342:36: note: in definition of
    macro ‘STACK_UNWIND_STRICT’
                             } else if (op_ret == 0) {
    \
                                        ^~~~~~
    }
    
    This is because args to pre-processor are lazily evaluated and operator
    precedence for == is higher than ?:
    
    Change-Id: I2c2ffb08bc3731ad0e17796047e01cb10771dbcf
    Updates: #259
    Reported-by: Raghavendra Talur <rtalur@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17827
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 4a85a221c92f422dedde62832e6cd6e66cae2722
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 18 15:47:13 2017 +0530

    run-tests.sh: log failed tests at the end
    
    Two benefits:
    
    1. People who subscribe to emails on regression failures
       (like maintainers@gluster.org), can see the list of failed tests
       in the email itself, instead of clicking on the link and checking
       for failures.
    
    2. When we visit the regression console, instead of scrolling to the
       exact position to see which tests failed, we can just press 'End'
       and would be able to check failures.
    
    Change-Id: Ibb4ac9575c5d32bae9c40c31fb53c9488b94421a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/17843
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 88af8d7ac515fcde1b8dc096afe6dbe7ab40d6ea
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 19 13:40:35 2017 -0400

    geo-rep: Handle possible entry failures gracefully
    
    Updates: #246
    
    Change-Id: If0ce83fe8dd3068bfb671f398b2e82ac831288d0
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17577
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 890ae2a1b2ce72d22657e7463405e59bee1e298a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jul 19 13:53:27 2017 +0200

    nfs: improve error handling for WebNFS mount permissions
    
    In case nfs3_funge_webnfs_zerolen_fh() returns an error, the
    nfs3_call_state_t structure will not get initialized. This means that
    calling `nfs3_call_state_wipe (cs)` will result in a segmentation fault
    after commit daed52b8eb that makes nfs3_call_state_t refcounted.
    
    Change-Id: I4c300aedf132a7fea95756dd278ff87d67722478
    BUG: 1468291
    Fixes: e3f48fa2 ("nfs: add permission checking for mounting over WebNFS")
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17822
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit df85ed48e5e94449cdcc77de3b86e10ccea49f1e
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jul 3 14:51:21 2017 +0530

    tools/glusterfind: Fix encoding to encode only space,newline and percent chars
    
    libgfchangelog was encoding path using spec rfc3986, but encoding only
    required for SPACE, NEWLINE and PERCENT chars since the NEWLINE char is
    used as record separator and SPACE as field separator in the parsed
    changelogs output.
    
    Changed the encoding function to encode only SPACE, NEWLINE and PERCENT chars
    
    BUG: 1451724
    Change-Id: Ic1dea824d23493dedcf3db45f353f90572f4e046
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17788
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>

commit 08ee8541cfc9096a7f1cb40db7d7df763256d535
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Jul 7 10:49:23 2017 +0530

    rpc: include current second in timed out frame cleanup
    
    Problem:
    frames which time out at current second are missed out
    
    Solution:
    change test to include frames timing out at current second
    i.e. timeout <= current.tv_sec
    instead of
    timeout < current.tv_sec
    
    Change-Id: I459d47856ade2b657a0289e49f7f63da29186d6e
    BUG: 1468433
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/17722
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e01783d871fbbf5a598d3bbf984ea98bafa5c10f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jul 3 14:51:21 2017 +0530

    geo-rep: Fix changelog encoding to encode only space and newline
    
    libgfchangelog was encoding path using spec rfc3986, but encoding only
    required for SPACE and NEWLINE chars since the NEWLINE char is used as
    record separator and SPACE as field separator in the parsed changelogs
    output.
    
    Changed the encoding function to encode only SPACE and NEWLINE.
    
    BUG: 1451724
    Change-Id: I1936efad31788a9e636f912c832ed7d7efea4fe2
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17787
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 5353389faf77bb2edb54e785c3d8aca323188dad
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jul 3 14:51:21 2017 +0530

    features/libgfchangelog: Fix encoding to encode only space and newline
    
    libgfchangelog was encoding path using spec rfc3986, but encoding only
    required for SPACE and NEWLINE chars since the NEWLINE char is used as
    record separator and SPACE as field separator in the parsed changelogs
    output.
    
    Changed the encoding function to encode only SPACE and NEWLINE.
    
    BUG: 1451724
    Change-Id: I4305459aab9e710517dd3eb065f0024503064b77
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17674
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 7517ee8a5795a85c1a877992c213199b0fd85517
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Jun 20 21:28:20 2017 +0530

    MAINTAINERS: Changes for Maintainers 2.0
    
    Updates MAINTAINERS to be in sync with [1]. More details on Maintainers
    2.0 can be found at [2].
    
    [1] https://goo.gl/CcvP5K
    [2] https://hackmd.io/s/SkwiZd4qe
    
    Change-Id: I069ee8eb78ec4f5272052f3ba902eb29f0fdb64b
    BUG: 1463365
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: https://review.gluster.org/17583
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>

commit d095c02eb9796ca2ec2a24931c28f057c403f834
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jul 20 18:11:14 2017 +0530

    glusterd: fix brick start race
    
    Problem:
    
    Another race where glusterd was restarted glusterd_brick_start () is called
    multiple times due to friend handshaking and in one instance when one of the
    brick was attempted to be attached to the existing brick process,
    send_attach_req failed as the first brick itself was still not up and then we
    did a synlock_unlock () followed by a sleep of 1 sec, before the same thread
    woke up, another thread tried to start the same brick process and then it
    assumed that it has to start a fresh brick process.
    
    Solution:
    
    1. If brick is in starting phase (brickinfo->status ==
    GF_BRICK_STARTING), no need for a reattempt to
    start the brick.
    2. While initiating attach_req set brickinfo->status to
    GF_BRICK_STARTING
    
    Change-Id: Ib007b6199ec36fdab4214a1d37f99d7f65ef64da
    BUG: 1465559
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17840
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit fdc431063f33cf4f5572771742e5502565f2a3ca
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Jul 19 21:44:55 2017 +0530

    cluster/dht: Fixed crash in dht_rmdir_is_subvol_empty
    
    The local->call_cnt was being accessed and updated inside
    the loop where the entries were being processed and the calls
    were being wound.
    This could end up in a scenario where the local->call_cnt became
    0 before the processing was complete causing the crash when the
    next entry was being processed.
    
    Change-Id: I930f61f1a1d1948f90d4e58e80b7d6680cf27f2f
    BUG: 1472949
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17825
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 8a09d78076cf506f0750cccd63cc983496473cf3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 13 13:44:19 2017 +0200

    mem-pool: free objects from pools on mem_pools_fini()
    
    When using a minimal gfapi application that only initializes a small
    graph (sink, shard and meta xlators) the following memory leaks are
    reported by Valgrind:
    
      HEAP SUMMARY:
          in use at exit: 322,976 bytes in 75 blocks
        total heap usage: 684 allocs, 609 frees, 2,092,116 bytes allocated
    
    With this change, the mem-pools are cleaned up on calling of
    mem_pools_fini() and the objects in the pool are free'd.
    
      HEAP SUMMARY:
          in use at exit: 315,265 bytes in 58 blocks
        total heap usage: 684 allocs, 626 frees, 2,092,079 bytes allocated
    
    This information was gathered with `./run-xlator.sh features/shard` that
    comes with `gfapi-load-volfile` from gluster-debug-tools.
    
    While working on the free'ing of the per_thread_pool_list_t structures,
    it became apparent that GF_CALLOC() in mem_get_pool_list() gets
    redirected to a standard calloc() without prepending the Gluster
    specific memory header. This is because mem_pools_init() gets called
    before THIS->ctx is valid, so it is not possible to check if memory
    accounting is enabled or not. Because of this, the GF_CALLOC() call in
    mem_get_pool_list() has been replaced by CALLOC() to prevent potential
    mismatches between the allocation/free'ing of per_thread_pool_list_t
    structures.
    
    Change-Id: Id6f558816f399b0c613d74df36deac2300b6dd98
    BUG: 1470170
    URL: https://github.com/gluster/gluster-debug-tools
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17768
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 1e8e6264033669332d4cfa117faf678d7631a7b1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jul 14 18:35:10 2017 +0200

    mem-pool: initialize pthread_key_t pool_key in mem_pool_init_early()
    
    It is not possible to call pthread_key_delete for the pool_key that is
    intialized in the constructor for the memory pools. This makes it
    difficult to do a full cleanup of all the resources in mem_pools_fini().
    For this, the initialization of pool_key should be moved to
    mem_pool_init().
    
    However, the glusterfsd binary has a rather complex initialization
    procedure. The memory pools need to get initialized partially to get
    mem_get() functionality working. But, the pool_sweeper thread can get
    killed in case it is started before glusterfsd deamonizes.
    
    In order to solve this, mem_pools_init() is split into two pieces:
    1. mem_pools_init_early() for initializing the basic structures
    2. mem_pools_init_late() to start the pool_sweeper thread
    
    With the split of mem_pools_init(), and placing the pthread_key_create()
    in mem_pools_init_early(), it is now possible to correctly cleanup the
    pool_key with pthread_key_delete() in mem_pools_fini().
    
    It seems that there was no memory pool initialization in the CLI. This
    has been added as well now. Without it, the CLI will not be able to call
    mem_get() successfully which results in a hang of the process.
    
    Change-Id: I1de0153dfe600fd79eac7468cc070e4bd35e71dd
    BUG: 1470170
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17779
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit acdbdaeba222e9ffeae077485681e5101c48d107
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Tue Jul 18 21:33:45 2017 +0530

    glusterd: Set default value for cluster.max-bricks-per-process to 0
    
    When brick-multiplexing is enabled, and
    "cluster.max-bricks-per-process" isn't explicitly set, multiplexing
    happens without any limit set. But the default value set for that
    tunable is 1, which is confusing. This commit sets the default
    value to 0, and prevents the user from being able to set this value
    to 1 when brick-multiplexing is enbaled. The default value of 0
    denotes that brick-multiplexing can happen without any limit on the
    number of bricks per process.
    
    Change-Id: I4647f7bf5837d520075dc5c19a6e75bc1bba258b
    BUG: 1472417
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17819
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 33db9aff1deaa028f30516e49fdb1e8d6e31bb73
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Jul 18 11:36:19 2017 +0530

    libglusterfs: Name threads on creation
    
    Set names to threads on creation for easier
    debugging.
    
    Output of top -H -p <PID-OF-GLUSTERFSD>
    Before:
    19773 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19774 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19775 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19776 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19777 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19778 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19779 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19780 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19781 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19782 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19783 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19784 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19785 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.01 glusterfsd
    19786 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.01 glusterfsd
    19787 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.01 glusterfsd
    19789 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19790 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    25178 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
     5398 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
     7881 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    
    After:
    19773 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19774 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glustertimer
    19775 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterfsd
    19776 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glustermemsweep
    19777 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glustersproc0
    19778 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glustersproc1
    19779 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterepoll0
    19780 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusteridxwrker
    19781 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusteriotwr0
    19782 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterbrssign
    19783 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterbrswrker
    19784 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterclogecon
    19785 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.01 glusterclogd0
    19786 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.01 glusterclogd1
    19787 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.01 glusterclogd2
    19789 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterposixjan
    19790 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterposixfsy
    25178 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterepoll1
     5398 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterepoll2
     7881 root      20   0 1301.3m  12.6m   8.4m S  0.0  0.1   0:00.00 glusterposixhc
    
    Change-Id: Id5f333755c1ba168a2ffaa4fce6e71c375e10703
    BUG: 1254002
    Updates: #271
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: https://review.gluster.org/11926
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5ccf0922208c368873120e235be0fd2975a589c1
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Apr 24 17:44:11 2015 +0530

    doc: beginner's guide to syncop framework
    
    Change-Id: I1f4517e1952d5b82ce679ebd2544b7403b1d37d8
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: https://review.gluster.org/10365
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 63d46236592c9e3c2fef05fd60d1c39548e57a8d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 18 15:23:12 2017 +0530

    common-utils: Remove fop_enum_to_string, get_fop_int
    
    Implementation of these two functions becomes easier by using gf_fop_list[]
    array. So implemented that and removed usage of these functions.
    
    BUG: 1472250
    Change-Id: I8a592913f9eeb02d965708bcf28a637588ed4988
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17812
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit f3b487a510965469963e860726059b28d67b3914
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 18 15:25:48 2017 +0530

    extras: Change Makefile generation in generate_xlator.py
    
    Makefile generation should include default LD_FLAGS and also include rpc
    related paths in include path
    
    Change-Id: I45e1c97b96f08bbfe4663384f4873726febef9f6
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17811
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 657d78dbad118e511e1fca8b1badb9f8ae7a6f60
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Jun 7 15:56:13 2017 +0530

    cluster/afr: GFID split-brain resolution with existing CLI
    
    Problem:
    Currently there is no way for the admin from CLI to resolve gfid
    split-brain based on some policy like choice of the brick, mtime
    or size.
    
    Fix:
    With the existing CLI options based on size, mtime, and choice of
    brick, we do lookup on the parent for the specified file. As
    part of the lookup, if we find gfid mismatch, we resolve them
    based on the policy and return. If the file is not in gfid split-
    brain, then we check for the data and metadata split-brain in the
    getxattr code path, and resolve if any.
    
    This will work provided absolute path to the file with the CLI
    and not with gfid of the file. Hence the source-brick policy
    without any file path will also not resolve the gfid split-brain
    since it uses the gfid of the files. But it can resolve any other
    type of split-brains and skip the gfid mismatch resolution with
    the usual error message.
    
    Reverting the change https://review.gluster.org/17290. This patch
    resolves the issue.
    
    Fixes gluster/glusterfs#135
    
    Change-Id: Iaeba6fc32f184a34255d03be87cda02773130a09
    BUG: 1459530
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: https://review.gluster.org/17485
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ae14513eb82929662b11e4c304877030a7d685cd
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Tue Jul 18 11:36:19 2017 +0530

    cluster/ec: Test script failing with brick multiplexing enabled
    
    Problem:
    Killing the bricks(using kill signal) in test scripts will
    result in test failures with brick multiplexing enabled.
    
    Solution:
    Updated the script to use kill_brick function to bring down
    the bricks.
    
    BUG: 1472094
    Change-Id: Ibbf1fdc1be660ad3cd93e95af2838c0aae0181af
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/17809
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 43d55c5afb1a9f731d806f7893923ac999b9ef6c
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Jul 10 20:43:39 2017 +0530

    rfc.sh: make alignment check compulsory
    
    Earlier, it was not reported if a function call had arguments on next
    line and the args were not aligned to opening bracket. With this change,
    it is a check that is displayed in output.
    
    I have not analyzed what all --strict brings in. If it is found to be
    more restrictive than required, we may choose to promote this *one* CHK
    to WARN and stop using --strict.
    
    Sample:
    
    CHECK: Alignment should match open parenthesis
    +                ret = gf_asprintf (&footer,
    +                                " [%s]", strerror(errnum));
    
    total: 0 warnings, 1 checks, 8 lines checked
    
    Change-Id: I48834087efcae872b69746ba962b0bb1c130b5cd
    BUG: 1469179
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: https://review.gluster.org/17737
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: ankitraj
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Sonal Arora <sarora@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit d26f0bac149d495fa93710c3f7b6b63c36cb8387
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jul 17 11:40:33 2017 +0200

    tests: disable IPC test-case
    
    The IPC test-case is not correct, and can cause segfaults or hangs. The
    ipctest.py script calls glfs_ipc() with the `glfs_t` structure, but
    should do so with a `glfs_fd_t`.
    
    In addition, the test-case is written in a way that we do not suggest to
    use libgfapi. Python scripts are encouraged to use the bindings from the
    libgfapi-python project. It would be better to rewrite the test in C so
    that there is type-checking while compiling and no additional issues
    with portability (see `LD_PRELOAD` note in the `.t` file).
    
    Change-Id: Icb52b5b1585fbee98f2c694547c31df0aa2ba70b
    Updates: #269
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17786
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 2e72b24707f1886833db0b09e48b3f48b8d68d37
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Apr 25 10:43:07 2017 +0530

    program/GF-DUMP: Shield ping processing from traffic to Glusterfs
    Program
    
    Since poller thread bears the brunt of execution till the request is
    handed over to io-threads, poller thread experiencies lock
    contention(s) in the control flow till io-threads, which slows it
    down. This delay invariably affects reading ping requests from network
    and responding to them, resulting in increased ping latencies, which
    sometimes results in a ping-timer-expiry on client leading to
    disconnect of transport. So, this patch aims to free up poller thread
    from executing code of Glusterfs Program. We do this by making
    
    * Glusterfs Program registering itself asking rpcsvc to execute its
      actors in its own threads.
    * GF-DUMP Program registering itself asking rpcsvc to _NOT_ execute
      its actors in its own threads. Otherwise program's ownthreads become
      bottleneck in processing ping traffic. This means that poller thread
      reads a ping packet, invokes its actor and hands the response msg to
      transport queue.
    
    Change-Id: I526268c10bdd5ef93f322a4f95385137550a6a49
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1421938
    Reviewed-on: https://review.gluster.org/17105
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 3b069f4d7e2140c1cad8c875a4397a1c90f99551
Author: Prashanth Pai <ppai@redhat.com>
Date:   Wed Jul 12 12:44:45 2017 +0530

    Update .gitignore
    
    Change-Id: Ica39edaf4388502d2f40c6daa5b4d65abda3bab1
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: https://review.gluster.org/17754
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: ankitraj
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 11eb8ba870457337c6067284dde4277e09764c0a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 12 09:18:02 2017 +0530

    storage/posix: Don't allow gfid/volume-id xattr to be removed
    
    Problem:
    Bulk xattr removal doesn't check if the xattrs that are coming in xdata
    have gfid/volume-id xattrs, so there is potential for bulkremovexattr
    removing gfid/volume-id.
    I also observed that bulkremovexattr is not available for fremovexattr.
    
    Fix:
    Do proper checks in bulk removexattr to remove gfid/volume-id.
    Refactor [f]removexattr to reduce the differences.
    
    BUG: 1470489
    Change-Id: Ia845b31846a149500111c0996646e648f72cdce6
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17765
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit b14f26a869c056fb9951e481ae20f3887edb743d
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Mon Jul 17 17:38:48 2017 +0530

    glusterd: Add description field to global options for brick-mux
    
    Currently the "cluster.brick-multiplex" and
    "cluster.max-bricks-per-process" options do not show anything in
    the description field when gluster volume set help is called. This
    commit adds the description fields for these 2 options.
    
    Change-Id: I3d162c61fa2774dd994f046e305d457f0fd43192
    BUG: 1471790
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17790
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 58a15ae04e597d6ab353f00a3ee72260c0b6f802
Author: Prashanth Pai <ppai@redhat.com>
Date:   Wed Jul 12 12:59:35 2017 +0530

    socket: call init_openssl_mt() in init() and add cleanup
    
    init_openssl_mt() wasn't explicitly invoked and was run implicitly before
    dlopen() returned as it was tagged as __attribute__ ((constructor)). This
    function used to call GF_CALLOC() which wasn't available or initialized
    when socket.so is dlopen()ed by an external program. The program used to
    crash with SIGSEGV as follows:
    
    0x00007ffff5efe1ad in __gf_calloc (nmemb=41, size=40, type=158, typestr=0x7ffff63eb3d6 "gf_sock_mt_lock_array")
    at mem-pool.c:109
    0x00007ffff63e6acf in init_openssl_mt () at socket.c:4016
    0x00007ffff7de90da in call_init.part () from /lib64/ld-linux-x86-64.so.2
    0x00007ffff7de91eb in _dl_init () from /lib64/ld-linux-x86-64.so.2
    0x00007ffff7dedde1 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2
    0x00007ffff7de8f84 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
    0x00007ffff7ded339 in _dl_open () from /lib64/ld-linux-x86-64.so.2
    
    This change moves call to init_openssl_mt() from being a constructor function
    to the init() function and introduces fini_openssl_mt() which cleans up
    resources (called in destructor).
    
    BUG: 1193929
    Change-Id: Iab690897ec34e24c33f6b43f8d8d9f8fd75ac607
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: https://review.gluster.org/17753
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 4c410a46ef58512ba751db8750910a6d09ec3696
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Jun 30 17:11:46 2017 +0530

    systemd/glusterfssharedstorage : remove dependency for var-run-gluster-shared_storage
    
    Currently the script used by glusterfssharedstorage have dependency over
    var-run-gluster-shared_storage. But this service will be present only if
    node has rebooted. Also in reboot scenario , there is a chance that this
    service can be executed before creating var-run-gluster-shared_storage.
    In that case glusterfssharedstorage will get succeed even without mounting
    the shared storage
    
    Also the type of glusterfssharedstorage changed to "forking" so that it can
    be active(instead of dead) after the successful start.
    
    Change-Id: I1c02cc64946e534d845aa7ec7b72644bbe4d26f9
    BUG: 1452527
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/17658
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit cc8bf4bb291870e3d98d25f1e2d08856be889d8d
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Sun Jul 9 23:16:39 2017 -0400

    quota: fix a crash by using bad regfile inode as parent
    
    0  0x00007f1482f1f1d7 in raise () from /lib64/libc.so.6
    1  0x00007f1482f208c8 in abort () from /lib64/libc.so.6
    2  0x00007f1482f18146 in __assert_fail_base () from /lib64/libc.so.6
    3  0x00007f1482f181f2 in __assert_fail () from /lib64/libc.so.6
    4  0x00007f148484986a in __inode_link (inode=inode@entry=0x7f14742404d4,
       parent=parent@entry=0x7f14742404d4,
       name=name@entry=0x7f1460001c48 "testfile5308",
       iatt=iatt@entry=0x7f1460001bc8) at inode.c:954
    5  0x00007f1484849969 in inode_link (inode=0x7f14742404d4,
       parent=parent@entry=0x7f14742404d4,
       name=name@entry=0x7f1460001c48 "testfile5308",
       iatt=iatt@entry=0x7f1460001bc8) at inode.c:1060
    6  0x00007f147591b895 in quota_build_ancestry_cbk (
       frame=frame@entry=0x7f1482315e80, cookie=<optimized out>,
       this=0x7f147000e910, op_ret=op_ret@entry=6904, op_errno=op_errno@entry=0,
       entries=entries@entry=0x7f1474731c00, xdata=xdata@entry=0x0) at quota.c:779
    7  0x00007f1475b2f505 in marker_build_ancestry_cbk (frame=0x7f1482315988,
       cookie=<optimized out>, this=<optimized out>, op_ret=<optimized out>,
       op_errno=<optimized out>, entries=0x7f1474731c00, xdata=0x0)
       at marker.c:3055
    8  0x00007f14848b9cd9 in default_readdirp_cbk (
       frame=frame@entry=0x7f1482315b30, cookie=<optimized out>,
       this=<optimized out>, op_ret=op_ret@entry=6904, op_errno=op_errno@entry=0,
       entries=entries@entry=0x7f1474731c00, xdata=xdata@entry=0x0)
       at defaults.c:1403
    9  0x00007f1475f68132 in pl_readdirp_cbk (frame=0x7f1482315dac,
       cookie=<optimized out>, this=<optimized out>, op_ret=6904, op_errno=0,
       entries=0x7f1474731c00, xdata=0x0) at posix.c:2700
    10 0x00007f1476e26819 in posix_readdirp (frame=0x7f1482315f54,
       this=<optimized out>, fd=<optimized out>, size=<optimized out>,
       off=<optimized out>, dict=<optimized out>) at posix.c:6282
    11 0x00007f1475f6599a in pl_readdirp (frame=0x7f1482315dac,
       this=0x7f147000a200, fd=0x7f1484b5106c, size=0, offset=0,
       xdata=0x7f1481ab4f34) at posix.c:2711
    12 0x00007f14848ce954 in default_readdirp_resume (frame=0x7f1482315b30,
       this=0x7f147000b690, fd=0x7f1484b5106c, size=0, off=0,
       xdata=0x7f1481ab4f34) at defaults.c:2019
    13 0x00007f148485c92d in call_resume (stub=0x7f1481b65710) at call-stub.c:2508
    14 0x00007f1475d54743 in iot_worker (data=0x7f147004e7d0) at io-threads.c:210
    15 0x00007f148369cdc5 in start_thread () from /lib64/libpthread.so.0
    16 0x00007f1482fe173d in clone () from /lib64/libc.so.6
    
    Change-Id: I740dc691e7be1bc2a9ae3a0cb14bbf566ea77bc5
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17730
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 6ed8518cfa352f53b84a511f3618b50ba4a42853
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jul 14 13:17:48 2017 +0200

    mem-pool: remove references to unused ctx->mempool_list
    
    Only the old (removed) implementation of mem-pools provided access to
    the ctx->mempool_list to faciliate state-dumps. The usage of the
    mempool_list has been disabled with "#if defined(OLD_MEM_POOLS)", but a
    few occurences were missed.
    
    Change-Id: I912fb63830efc06247eb0c6551d198271ee57a86
    BUG: 1470170
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17778
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2b290b50457ce2bd37f18d516c665abc1e96d2d6
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 13 11:35:50 2017 -0400

    packaging: various directories not owned by any package
    
    e.g. /usr/libexec/glusterfs or /usr/lib64/glusterfs/$NV/xlator
    
    Change-Id: Ibccb8d27b6ad3d6c335e5bbf39aec03b4fe5c8dd
    BUG: 1470768
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17770
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5ee383fed9f6408d303aa539dda071275021f8e4
Author: Danny Couture <couture.danny@gmail.com>
Date:   Wed Jul 5 09:55:17 2017 -0400

    fuse: memory leak fixes
    
    Fix fuse ctx memory leak in case an error occurs and the cleanup path
    is different than usual. Also fix a memory leak in logging if
    eh_save_history() fails.
    
    Change-Id: I7ec967c807b0ed91184e5b958be70702215c46c9
    BUG: 1470220
    Signed-off-by: Danny Couture <couture.danny@gmail.com>
    Reviewed-on: https://review.gluster.org/17759
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e648a291b02298d2f1063cedaad9a58614ebe0ad
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 13 08:10:27 2017 -0400

    core: miscellaneous cleanup
    
    clean up things that I tripped over doing other changes.
    
    1) fix mishmash of random spacing in struct decls in glusterfs.h.
    Not technically a problem, just ugly to look at.
    
    2) replace open-coded strings constants with existing #define
    constants. A disaster waiting to happen.
    
    3) Use sys_access() instead of sys_stat() or sys_lstat() to test
    simple existence of file. Why copy dozens of bytes from kernel to
    user space that aren't going to be used by anything? There are
    probably more instances like these.
    
    Change-Id: I28089bef4cc93d5e4e4213045fb1a2649d110f82
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17769
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d2650feb4bfadf3fb0cdb90236bc78c33b5ea451
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Wed Jul 5 16:41:38 2017 +0530

    cluster/ec: Non-disruptive upgrade on EC volume fails
    
    Problem:
    Enabling optimistic changelog on EC volume was not
    handling node down scenarios appropriately resulting
    in volume data inaccessibility.
    
    Solution:
    Update dirty xattr appropriately on good bricks whenever
    nodes are down. This would fix the metadata information
    as part of heal and thus ensures data accessibility.
    
    BUG: 1468261
    Change-Id: I08b0d28df386d9b2b49c3de84b4aac1c729ac057
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/17703
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 77c1ed5fd299914e91ff034d78ef6e3600b9151c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jul 6 19:49:47 2017 +0530

    afr: mark non sources as sinks in metadata heal
    
    Problem:
    In a 3 way replica, when the source brick does not have pending xattrs
    for the sinks, but the 2 sinks blame each other, metadata heal was not
    happpening because we were not setting all non-sources as sinks.
    
    Fix: Mark all non-sources as sinks, like it is done in data and entry
    heal.
    
    Change-Id: I534978940f5087302e307fcc810a48ffe898ce08
    BUG: 1468279
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17717
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 61db7125a5b8db0bd4dd09b423bb54415c8bd484
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Jul 13 12:23:13 2017 +0530

    posix: brick process crash after stop the volume while brick mux is on
    
    Problem: sometime brick process is getting crash after stop the volume
             while brick mux is enabled and no. of volumes are high
    
    Solution: In posix notify at the time close mount_lock dir , dir handle
              needs to set NULL to avoid the reuse of same dir handle.
    
    BUG: 1470533
    Change-Id: Ifd41c20b3c597317851f91049a7c801949840b16
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17767
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit f367671d451ae0fc3e178d26cae1880d59eb6ebd
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jul 6 16:40:07 2017 +0530

    cluster/ec: Get size of file in EC [f]xattrop
    
    Problem:
    For allowing parallel writes we shouldn't depend on ia_size to be same for
    all the bricks in each write_cbk(). But we need to make sure backend size
    is correct on all the bricks and no crashes/manual modifications happened.
    
    Fix:
    At the time of get_size_version() we do 1 check to make sure size of the file
    is same across the bricks. From then on the FOPs will give the status of the
    fop, so we rely on this information to keep which bricks are good/bad.
    
    Updates #251
    Change-Id: I1df645347e2e9f2e09cfa4411b6cc305d7f4e4e5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17741
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 73b2b7fe57069eb85485465fb92c52a97d4d411c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jul 6 16:39:37 2017 +0530

    storage/posix: Handle [f]xattrop xdata
    
    Updates #251
    Change-Id: I13d89c3b5dc39aa0a232a70be8ec6b64394cfa6e
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17740
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 0d75e39834d4880dce0cb3c79bef4b70bb32874d
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Jul 12 12:01:40 2017 +0530

    cluster/rebalance: Fix hardlink migration failures
    
    A brief about how hardlink migration works:
      - Different hardlinks (to the same file) may hash to different bricks,
    but their cached subvol will be same. Rebalance picks up the first hardlink,
    calculates it's  hash(call it TARGET) and set the hashed subvolume as an xattr
    on the data file.
      - Now all the hardlinks those come after this will fetch that xattr and will
    create linkto files on TARGET (all linkto files for the hardlinks will be hardlink
    to each other on TARGET).
      - When number of hardlinks on source is equal to the number of hardlinks on
    TARGET, the data migration will happen.
    
    RACE:1
      Since rebalance is multi-threaded, the first lookup (which decides where the TARGET
    subvol should be), can be called by two hardlink migration parallely and they may end
    up creating linkto files on two different TARGET subvols. Hence, hardlinks won't be
    migrated.
    
    Fix: Rely on the xattr response of lookup inside gf_defrag_handle_hardlink since it
    is executed under synclock.
    
    RACE:2
      The linkto files on TARGET can be created by other clients also if they are doing
    lookup on the hardlinks.  Consider a scenario where you have 100 hardlinks.  When
    rebalance is migrating 99th hardlink, as a result of continuous lookups from other
    client, linkcount on TARGET is equal to source linkcount. Rebalance will migrate data
    on the 99th hardlink itself. On 100th hardlink migration, hardlink will have TARGET as
    cached subvolume. If it's hash is also the same, then a migration will be triggered from
    TARGET to TARGET leading to data loss.
    
    Fix: Make sure before the final data migration, source is not same as destination.
    
    RACE:3
      Since a hardlink can be migrating to a non-hashed subvolume, a lookup from other
    client or even the rebalance it self, might delete the linkto file on TARGET leading
    to hardlinks never getting migrated.
    
    This will be addressed in a different patch in future.
    
    Change-Id: If0f6852f0e662384ee3875a2ac9d19ac4a6cea98
    BUG: 1469964
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17755
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a4a417e29c5b2d63e6bf5efae4f0ccf30a39647f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jul 10 11:45:31 2017 +0200

    gfapi: prevent mem-pool leak in case glfs_new_fs() fails
    
    Commit 7039243e187 adds a call to mem_pools_init() so that the memory
    pool cleanup thread ("sweeper") is started. However, now it is possible
    that users of gfapi can not cleanup this thread because glfs_new() can
    return NULL, but the sweeper is still running.
    
    In case glfs_fs_new() fails, mem_pools_fini() needs to be called as
    well. This seems more correct than calling mem_pools_init() after
    glfs_fs_new(), and this makes using memory pools possible *really* early
    in the gfapi initialization.
    
    Change-Id: I1f2fb25cc33e227b3c33ce9d1b03f67bc27e981a
    Fixes: 7039243e187 ("gfapi: add mem_pools_init and mem_pools_fini calls")
    BUG: 1468863
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17734
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 9ab249130a5dd442044e787f1e171e7a17839906
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 6 10:19:54 2017 -0500

    features/read-only: Allow internal clients to r/w
    
    If the "read-only" volume option is set, it would
    make the volume "read-only". But it also makes it
    read-only to gluster internal clients such as
    gsyncd, self heal, bitd, rebalance etc. In which
    case, all the internal operations would fail. This
    patch allows internal clients to read and write
    when "read-only" option is set.
    
    Change-Id: I8110e8d9eac8def403bb29f235000ddc79eaa433
    BUG: 1430608
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/16855
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Karthik U S <ksubrahm@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 09f9c6c1c9c565d54c257e58c46004326ec1c495
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Tue Jul 4 11:18:16 2017 +0530

    gluster man page: Add remote-host and script mode in gluster man page
    
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Change-Id: I2d9b9f09d72d713e34ccb9516387c5982b830115
    BUG: 1467277
    Reviewed-on: https://review.gluster.org/17685
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit bd71ca4fdf2554dd22c0db70af132a11b966ef38
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 10 15:45:04 2017 +0530

    cluster/dht: Clear clean_dst flag on target change
    
    If the target of a file migration was changed because
    of min-free-disk limits, the dst_fd was closed but the
    clean_dst flag was not set to false. If the file could
    not be created on the new target for some reason, the
    ftruncate call to clean up the dst was sent on the now
    invalid fd causing the process to deadlock.
    
    Change-Id: I5bfa80f519b04567413d84229cf62d143c6e2f04
    BUG: 1469029
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17735
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit f7a450c17fee7e43c544473366220887f0534ed7
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 10 09:38:54 2017 +0530

    cluster/dht: Fix fd check race
    
    There is a another race between the cached subvol
    being updated in the inode_ctx and the fd being opened on
    the target.
    
    1. fop1 -> fd1 -> subvol0
    2. file migrated from subvol0 to subvol1 and cached_subvol
       changed to subvol1 in inode_ctx
    3. fop2 -> fd1 -> subvol1 [takes new cached subvol]
    4. fop2 -> checks fd ctx (fd not open on subvol1) -> opens fd1 on subvol1
    5. fop1 -> checks fd ctx (fd not open on subvol0)
       -> tries to open fd1 on subvol0 -> fails with "No such file on directory".
    
    Fix:
    If dht_fd_open_on_dst fails with ENOENT or ESTALE, wind to old subvol
    and let the phase1/phase2 checks handle it.
    
    Change-Id: I34f8011574a8b72e3bcfe03b0cc4f024b352f225
    BUG: 1465075
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17731
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a62b16b72b03f2b7c25c24ea9ac5968453a92009
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 29 05:45:34 2017 -0400

    storage/posix: New gfid2path infra
    
    With this infra, a new xattr is stored on each entry
    creation as below.
    
    trusted.gfid2path.<xxhash> = <pargfid>/<basename>
    
    If there are hardlinks, multiple xattrs would be present.
    
    Fops which are impacted:
    create, mknod, link, symlink, rename, unlink
    
    Option to enable:
    gluster vol set <VOLNAME> storage.gfid2path on
    
    Updates: #139
    Change-Id: I369974cd16703c45ee87f82e6c2ff5a987a6cc6a
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17488
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 9156a743aa76c955d18c9bfcb7c1a38ba00da890
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 3 13:13:35 2017 +0530

    cluster/dht: Use size to calculate estimates
    
    The earlier approach of using the number of files
    to determine when the rebalance would complete did
    not work well when file sizes differed widely.
    
    The new approach now gets the total data size and
    uses that information to determine how long
    the rebalance is expected to take.
    
    Change-Id: I84e80a0893efab72ff06130e4596fa71c9c8c868
    BUG: 1467209
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17668
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b0d8afa2d2861f1191c4139e9aa9d4ba67e83135
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jul 7 02:46:26 2017 +0530

    tests: fix stats-dump.t failure
    
    Since https://review.gluster.org/#/c/17452, the statistics are appended
    to the same file instead of overwritten over the previous stats. This
    was causing the .t to fail since it checks for only the presence of a
    non zero aggr.fop.write.count assuming the latest statistics will
    overwrite the previous ones.
    
    Fix it by checking for that the latest value of aggr.fop.write.count is
    non zero.
    
    Change-Id: I858011f343966a5d1c19d66dcc64b8cd26315df7
    BUG: 1468432
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17721
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit f28b5d1007644749761fd374d951b72ace2e203e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jul 6 14:25:09 2017 +0530

    extras: Enable stat-prefetch in virt profile
    
    In the internal testing that was done, stat-prefetch did help
    reduce the number of stats coming from qemu hitting the disk,
    and thereby improved performance.
    
    Change-Id: Icf1ce62ecf4e96b97e1946a77b30434157a7786a
    BUG: 1468191
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17713
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f2f3d74c835b68ad9ec63ec112870829a823a1fb
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Jul 6 13:26:42 2017 +0530

    mgtm/core : use sha hash function for volfile check
    
    We are storing the entire volfile and using this to check
    volfile change. With brick multiplexing there will be lot
    of graphs per process which will increase the memory foot
    print of the process. So instead of storing the entire
    graph we could use sha256 and we can compare the hash to
    see whether volfile change happened or not.
    
    Also with Brick multiplexing, the direct comparison of vol
    file is not correct. There are two problems.
    
    Problem 1:
    
    We are currently storing one single graph (the last
    updated volfile) whereas, what we need is the entire
    graph with all atttached bricks.
    
    If we fix this issue, we have second problem
    
    Problem 2:
    With multiplexing we have a graph that contains multiple
    bricks. But what we are checking as part of the reconfigure
    is, comparing the entire graph with one single graph,
    which will always fail.
    
    Solution:
    We create list in glusterfs_ctx_t that stores sha256 hash
    of individual brick graphs. When a graph changes happens
    we compare the stored hash and the current hash. If the
    hash matches, then no need for reconfigure. Otherwise we
    first do the reconfigure and then update the hash.
    
    For now, gfapi has not changed this way. Meaning when gfapi
    volfile fetch or reconfigure happens, we still store the
    entire graph and compare, each memory.
    
    This is fine, because libgfapi will not load brick graphs.
    But changing the libgfapi will make the code similar in
    both glusterfsd-mgmt and api. Also it helps to reduce some
    memory.
    
    Change-Id: I9df917a771a52b95622ab8f63af34ec390163a77
    BUG: 1467986
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17709
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 9e8ee31e643b7fbf7d46092c395ea27aaeb82f6b
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Fri Jun 2 10:12:12 2017 +0530

    glusterd: Introduce option to limit no. of muxed bricks per process
    
    This commit introduces a new global option that can be set to limit
    the number of multiplexed bricks in one process.
    
    Usage:
    `# gluster volume set all cluster.max-bricks-per-process <value>`
    
    If this option is not set then multiplexing will happen for now
    with no limitations set; i.e. a brick process will have as many
    bricks multiplexed to it as possible. In other words the current
    multiplexing behaviour won't change if this option isn't set to
    any value.
    
    This commit also introduces a brick process instance that contains
    information about brick processes, like the number of bricks
    handled by the process (which is 1 in non-multiplexing cases), list
    of bricks, and port number which also serves as an unique identifier
    for each brick process instance. The brick process list is
    maintained in 'glusterd_conf_t'.
    
    Updates: #151
    Change-Id: Ib987d14ab0a4f6034dac01b73a4b2839f7b0b695
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17469
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit e304f48fa262e5cdbe181fb3fee5dfb9c893108c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 6 17:04:17 2017 +0200

    nfs: add permission checking for mounting over WebNFS
    
    Solaris 10 uses WebNFS and not the MOUNT protocol. All permission checks
    for allowing/denying clients to mount are done through the MNT handlers.
    These handlers will not give out a filehandle to the NFS-client when
    mounting is denied. This prevents clients from successful mounting.
    However, over WebNFS a well known 'root-filehandle' is used directly
    with the NFSv3 protocol.
    
    When WebNFS was used, no permission checks (the "nfs.export-dir" option)
    were applied. Now the WebNFS mount-handler in Gluster/NFS calls the
    mnt3_parse_dir_exports() function that takes care of the permission
    checking.
    
    BUG: 1468291
    Change-Id: Ic9dfd092473ba9c1c7b5fa38401cf9c0aa8395bb
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17718
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b81997264f079983fa02bd5fa2b3715224942b00
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jul 4 20:11:11 2017 +0200

    nfs/nlm: keep track of the call-state and frame for notifications
    
    When blocking locks are used, a new frame is allocated that is used to
    send the notification to the client once once the lock becomes
    available. In all other cases, the frame that contains the request from
    the client will be used for the reply.
    
    Because there was no way to track the different clients with their
    requests (captured in the call-state), the call-state could be free'd
    before the notification was sent to the client. This caused a
    use-after-free of the call-state and could trigger segfaults of the
    Gluster/NFS server or incorrect replies on (un)lock requests.
    
    By introducing a nlm4_notify_args structure, the call-state and frame
    can be tracked better. This prevents the possibility of segfaulting when
    the call-state is used after being free'd.
    
    BUG: 1467313
    Change-Id: I285d2bc552f509e5145653b7a50afcff827cd612
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17700
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 01bfdd4d1759423681d311da33f4ac2346ace445
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jul 3 16:24:53 2017 +0200

    nfs/nlm: use refcounting for nfs3_call_state_t
    
    In order to track down a potential use-after-free of the
    nfs3_call_state_t structure in the NLM component, add reference counting
    where teh structure is used. This should prevent premature free'ing of
    the structure.
    
    Change-Id: Ib1f13b0463ab1e012b7b49a623c91f0f3e73e1fb
    BUG: 1467313
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17699
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit fafe1491ead527ba1024c521013aa90d2ee2b355
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jun 21 16:25:33 2017 +0200

    nfs/nlm: handle reconnect for non-NLM4_LOCK requests
    
    When a reply on an NLM-procedure gets stuck, the NFS-client will resend
    the request. This can happen through a re-connect in case the connection
    was terminated (long delay in the reply on the initial request). Once
    that happens, not all NLM-procedures are handled correctly.
    
    Testing this is difficult and time-consuming. There still may be
    problems with certain operations, but this definitely makes it behave
    much better than before.
    
    The problem occured due to a problem in EC, change-id I18a782903ba
    addressed the root cause.
    
    Change-Id: I23b385568e27232951fa3fbd7198a0e5d775a8c2
    BUG: 1467313
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17698
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 26241777bf59c7d64c582ce09e557bc2dc97dabb
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Jul 3 16:37:01 2017 +0530

    uss/svc: fix double free on xdata dictionary
    
    we were taking unref on wrong dictionary which results
    in wrong memory access.
    
    Change-Id: Ic25a6c209ecd72c9056dfcb79fabcfc650dd3c1e
    BUG: 1467513
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17691
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 70a5dfdea4980dea5da5b5008a16fd155a3adf34
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Jul 3 12:45:38 2017 +0530

    svc: send revalidate lookup on special dir
    
    .snaps directory is a virtual direcotory, that doesn't
    exist on the backend. Even though it is a special dentry,
    it doesn't have a dedicated inode. So the inode number is
    always random. Which means it will get different inode
    number when reboot happens on snapd process.
    
    Now with windows client the show-direcotry feature requires
    a lookup on the .snpas direcoty post readdirp on root.
    If the snapd restarted after a lookup, then subsequent lookup
    will fail, because linked inode will be stale.
    
    This patch will do a revalidate lookup with a new inode.
    
    Change-Id: If97c07ecb307cefe7c86be8ebd05e28cbf678d1f
    BUG: 1467513
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17690
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ecd92d42bbd9249aa637b1ad3000aa242308cb04
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Jun 30 20:17:20 2017 +0530

    svs:implement CHILD UP notify in snapview-server
    
    protocol/server expects a child up event to successfully
    configure the graph. In the actual brick graph, posix is
    the one who decide to initiate the notification to the parent
    that the child is up.
    
    But in snapd graph there is no posix, hence the child up
    notification was missing.
    
    Ideally each xlator should initiate the child up event whenever
    it see's that this is the last child xlator.
    
    Change-Id: Icccdb9fe920c265cadaf9f91c040a0831b4b78fc
    BUG: 1467513
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17689
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 028d82b8a2434cb6d5ad707500f6dea2125ea2fa
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Fri Jul 7 07:49:45 2017 -0700

    gfapi+libglusterfs: fix mem_pools_fini without mem_pools_init case
    
    The change consists of two parts: make sure it doesn't happen (in
    glfs.c), and make it harmless if it does (in mem-pool.c).
    
    Change-Id: Icb7dda7a45dd3d1ade2ee3991bb6a22c8ec88424
    BUG: 1468863
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17728
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 0ae38df6403942a2438404d46a6e05b503db3485
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Jul 4 16:18:20 2017 +0530

    cluster/ec : Don't try to heal when no sink is UP
    
    Problem:
    4 + 2 EC volume configuration.
    If untar of linux is going on and we kill a brick,
    indices will be created for the files/dir which need
    to be healed. ec_shd_index_sweep spawns threads to
    scan these entries and start heal. If in the middle
    of this we kill one more brick, we end up in a
    situation where we can not heal an entry as there
    are only "ec->fragment" number of bricks are UP.
    However, the scan will be continued and it will
    trigger the heal for those entries.
    
    Solution:
    When a heal is triggered for an entry, check if it
    *CAN* be healed or not. If not come out with ENOTCONN.
    
    Change-Id: I305be7701c289f36bd7bde22491b71074771424f
    BUG: 1464359
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/17692
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 45517ad2439118cebef63390b82a5e94c5b83ee8
Author: Nigel Babu <nigelb@redhat.com>
Date:   Fri Jul 7 11:06:37 2017 +0530

    tests: Disable basic/stats-dump.t
    
    Disabling this test right now so that master is green again. This patch
    https://review.gluster.org/#/c/17721/ will actually fix the test. This
    patch will make master green again unblocking other patches to land onto
    master.
    
    Change-Id: I77d177ce92eb6edcf5326b27a0f7fdbefdec007b
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    BUG: 1468432
    Reviewed-on: https://review.gluster.org/17723

commit e14ea3f5c37475e12a3b7fb7bd3165b0a4e77c51
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Jul 5 17:48:37 2017 +0200

    groups: don't allocate auxiliary gid list on stack
    
    When glusterfs wants to retrieve the list of auxiliary gids
    of a user, it typically allocates a sufficiently big gid_t
    array on stack and calls getgrouplist(3) with it. However,
    "sufficiently big" means to be of maximum supported gid list
    size, which in GlusterFS is GF_MAX_AUX_GROUPS = 64k.
    That means a 64k * sizeof(gid_t) = 256k allocation, which is
    big enough to overflow the stack in certain cases.
    
    A further observation is that stack allocation of the gid list
    brings no gain, as in all cases the content of the gid list
    eventually gets copied over to a heap allocated buffer.
    
    So we add a convenience wrapper of getgrouplist to libglusterfs
    called gf_getgrouplist which calls getgrouplist with a sufficiently
    big heap allocated buffer (it takes care of the allocation too).
    We are porting all the getgrouplist invocations to gf_getgrouplist
    and thus eliminate the huge stack allocation.
    
    BUG: 1464327
    Change-Id: Icea76d0d74dcf2f87d26cb299acc771ca3b32d2b
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17706
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit fc73ae5f81ef5926e3dc2311db116250d0f2a321
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Jun 2 15:42:39 2017 +0530

    debug/io-stats: Append stats for each interval in the same file
    
    ... instead of overwriting stats from the previous interval.
    This is so that consumers of this feature do not have to be worried
    about monitoring when each 'ios-dump-interval' has passed and back up
    the resultant stats file well before the next interval has expired.
    
    Change-Id: Ide897237bf4d38e5d759f09911f7d9c817019edf
    BUG: 1458197
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17452
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit e9a482f94e748ea12e73ddd2e275bad9aa314b4c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 30 17:54:34 2017 +0200

    nfs/nlm: unref fds in nlm_client_free()
    
    When a nlm_clnt is getting free'd, the FDs associated with this client
    should be unref'd as well.
    
    Change-Id: Ifa4ea4b7ed45a454413cfc0c820f2516c534a9aa
    BUG: 1467313
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17697
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit daed52b8ebcac7ef36f11e944f83826f46593867
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 23 10:01:27 2017 +0200

    nfs: make nfs3_call_state_t refcounted
    
    There is no refcounting done of the nfs3_call_state_t structure, which
    seems to result in use-after-free problems in the NLM part of
    Gluster/NFS. The structure is initialized with two different functions,
    it is easier to have a single place to do this.
    
    The Gluster/NFS part will not use the refcounting, for now. This is
    being added to make the NLM code more stable. nfs3_call_state_wipe()
    will behave as before for Gluster/NFS, but cleanup is triggered through
    the refcounting now. This prevents major changes to the stable part of
    the NFS-server, and makes it possible to improve the NLM component
    separately.
    
    Change-Id: I2e15bcf12af74e8a46c2727e4a160e9444d29ece
    BUG: 1467313
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17696
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit c7efdb834772ddd8f6b07214d3eb2d26425cb79b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Jul 5 14:58:50 2017 +0530

    cli/xml: fix return handling
    
    The return code of xmlTextWriter* APIs says it returns either the bytes
    written (may be 0 because of buffering) or -1 in case of error. Now if the
    volume of the xml data payload is not huge then most of the time the
    data to be written gets buffered, however when this grows sometimes this
    APIs will return the total number of bytes written and then it becomes
    absolutely mandatory that every such call is followed by
    XML_RET_CHECK_AND_GOTO otherwise we may end up returning a non zero ret
    code which would result into the overall xml generation to fail.
    
    Change-Id: I02ee7076e1d8c26cf654d3dc3e77b1eb17cbdab0
    BUG: 1467841
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17702
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>

commit eb96dd45f8e583c6bad84bf32ca17e2bb01dd38f
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue May 9 19:40:21 2017 +0200

    cluster/ec: correctly handle end of file for seek
    
    When a SEEK_HOLE was issued near to the end of file, sometimes an
    offset beyond the end of file was returned. Another problem was that
    using some offsets greater than the end of file returned successfully
    instead of failing with ENXIO.
    
    Change-Id: I238d2884ba02fd19a78116b0f8f8e8d6338fb3f5
    BUG: 1449348
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/17228
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit b25bf64f3a3520a96ad557daa4903c0ceba96d72
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jul 4 08:46:06 2017 -0400

    geo-rep: Fix entry failure because parent dir doesn't exist
    
    In a distributed volume on master, it can so happen that
    the RMDIR followed by MKDIR is recorded in changelog on
    a particular subvolume with same gfid and pargfid/bname
    but not on all subvolumes as below.
    
    E 61c67a2e-07f2-45a9-95cf-d8f16a5e9c36 RMDIR \
    9cc51be8-91c3-4ef4-8ae3-17596fcfed40%2Ffedora2
    E 61c67a2e-07f2-45a9-95cf-d8f16a5e9c36 MKDIR 16877 0 0 \
    9cc51be8-91c3-4ef4-8ae3-17596fcfed40%2Ffedora2
    
    While processing this changelog, geo-rep thinks RMDIR is
    successful and does recursive rmdir on slave. But in the
    master the directory still exists. This could lead to
    data discrepancy between master and slave.
    
    Cause:
    RMDIR-MKDIR pair gets recorded so in changelog when the
    directory removal is successful on cached subvolume and
    failed in one of hashed subvol for some reason
    (may be down). In this case, the directory is re-created
    on cached subvol which gets recorded as MKDIR again in
    changelog.
    
    Solution:
    So while processing RMDIR geo-replication should stat on
    master with gfid and should not delete it if it's present.
    
    Change-Id: If5da1d6462eb4d9ebe2e88b3a70cc454411a133e
    BUG: 1467718
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17695
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 7039243e187e1acc086812b038d4da71389dc507
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 29 14:07:51 2017 -0400

    gfapi: add mem_pools_init and mem_pools_fini calls
    
    These are both needed because GFAPI clients are a bit unique.  They can
    be long-running, so they can potentially benefit from the memory
    reclamation that mem_pools_init will enable.  On the other hand, they
    might completely tear down their Gluster environment well before the
    process exits, so they need mem_pools_fini as well.
    
    Our main and auxiliary daemons do need mem_pools_init but don't need to
    call it themselves because that's handled for them in glusterfsd.c right
    after they daemonize.  They don't need mem_pools_fini, because the only
    place they could *safely* call it is right before exit and then it won't
    do them any good.  Transient processes (e.g. gf_attach) don't benefit
    from either because, well, they're transient.  They'll be gone before
    memory reclamation matters.
    
    Change-Id: I611cf77d8b408b3ecfc00664e8da294edde9e57a
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17666
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit a14475fa835289f956af652b6b73ddaeffd4bf18
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jun 30 09:05:51 2017 -0400

    core: assorted typos and spelling mistakes from Debian lintian
    
    Plus minor readability improvements.
    
    Reported-by: pmatthaei@debian.org
    
    Change-Id: I5393819a2fc9f240a19811143bb57b127df717cf
    BUG: 1466785
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17660
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 89faa4661d1ef66a9f8fe3b79e26bf4505ab6c61
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Jun 12 16:30:20 2017 +0530

    posix: Avoid one extra call of l(get|list)xattr call after use buffer in posix_getxattr
    
    Problem: In posix xlator posix_(f)getxattr is calling system call(sys_lgetxattr)
             two times to fetch the xattr value.
    
    Solution: After use the extra buffer for first time calling we can avoid second
              attempt of system call(sys_lgetxattr) calling in posix_getxattr for most
              of the xattrs.
    
    BUG: 1460659
    Change-Id: I0d8da776c5bc86653d874a4629a73bbf65c621b8
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17520
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kinglong Mee

commit 97a08698058962a4ddc783008c92ee94f08740a9
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Jun 30 15:52:53 2017 +0530

    Link against missed libraries to resolve symbols
    
    When external programs perform a dlopen("..so", RTLD_LAZY|RTLD_LOCAL)
    on some shared objects like xlators, it can fail with dlerror set to
    error string "undefined symbol <some-type>".
    
    This was observed for the following shared objects: fuse.so, quota.so,
    quotad.so, server.so, libgfrpc.so and socket.so
    
    P.S: This was found while running a go program which fetches the list
    of xlator options (volume_option_t) from xlator's shared object.
    
    BUG: 1193929
    Change-Id: I7b958409cf11fb67c2be32a3f85a96fb1260236b
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: https://review.gluster.org/17659
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 5a67bc07db128782024ccb7c8ec3a35a8542e540
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Fri Jun 30 07:07:16 2017 -0700

    libglusterfs: add mem_pools_fini
    
    This also makes mem_pools_init and mem_pools_fini re-callable, so GFAPI
    can go through infinite init/fini cycles if they want to.  Not saying
    that's a good idea, but at least it's safe.
    
    Change-Id: I617913410bcff54568b802cb653f48bdd533bd65
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17662
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit b4db625d0ccb4fdc6537ed9f6e8ebeaffd1c4873
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Jun 25 21:50:09 2017 +0530

    glfsheal: prevent background self-heals
    
    Problem:
    For a file in gfid split-brain, the parent directory ('/' during
    testing) was detected as possibly undergoing heal instead of split-brain
    in `heal-info` output. Also, it was not being displayed in `info
    split-brain` output for the same reason. The problem was that when `glfsheal`
    was run, lookup on '/' triggered a background self-heal due to which processing
    of '/' during `heal info` failed to acquire locks with errno=EAGAIN.
    
    Fix:
    Set background-self-heal-count to zero while launching glfsheal.
    
    Change-Id: I153a7c75af71f213a4eefacf504a0f9806c528a5
    BUG: 1318895
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/13772
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit fd231ba48a8938d52f00682aa172a8dab0df639e
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Thu Jun 29 10:25:54 2017 -0700

    tests: disable crypt.t
    
    This has been nuking just about everything.  Kill it with fire.
    
    Change-Id: I5e6e2e4d1568f118298fcf109077db001f87040d
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17652
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 0be8e038d9bf90be94f3e3a7d6ea5bee88da9ecb
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Thu Jun 29 06:50:56 2017 -0700

    multiple: fix struct/typedef inconsistencies
    
    The most common pattern, both in our code and elsewhere, is this:
    
       struct _xyz {
          ...
       };
       typedef struct _xyz xyz_t;
    
    These exceptions - especially call_frame/call_stack - have been slowing
    down code navigation for years.  By converging on a single pattern,
    navigating from xyz_t in code to the actual definition of struct _xyz
    (i.e. without having to visit the typedef first) might even be
    automatable.
    
    Change-Id: I0e5dd1f51f98e000173c62ef4ddc5b21d9ec44ed
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17650
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 50d72373fadf1174918e754e31bae3806aa4c214
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Thu Jun 29 15:39:35 2017 +0530

    Scripts to identify quota accouting issues
    
    The patch contains 2 scripts:
    
    log_accounting.sh does a du -h on the FS hierarchy and a quota list
    on the hierarchy and interleaves the two output. We can then identify
    which directory(s) in FS has caused the accounting to go bad and try
    to investigate what fops happened on those directories. We can also
    limit the set of directories on which we need to set dirty xattr to
    correct accounting.
    xattr_analysis.py reads all the xattr of a brick and dumps it a human
    readable form to ease debugging.
    
    Change-Id: I2155561d10c08dc3ab9e8b09dbd258f0592b4d33
    BUG: 1466188
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Reviewed-on: https://review.gluster.org/17649
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 292b4e42fdc023e307fde35e189285040d4b9cdd
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 28 05:09:12 2017 -0400

    contrib/xxhash: Add xxhash library
    
    xxhash is a faster non-cryptographic hash.
    https://github.com/Cyan4973/xxHash
    
    Release Taken: "xxHash v0.6.2"
    --------------
    
    Files added:
      contrib/xxhash/xxhash.c
      contrib/xxhash/xxhash.h
      contrib/xxhash/xxhsum.c
    
    Modifications to source:
    ------------------------
    Following functions and data types got 'GF_' prefix
    as below to avoid any form of name collisions in future.
    
        ---- Functions ----
        GF_XXH_versionNumber
        GF_XXH32
        GF_XXH32_createState
        GF_XXH32_freeState
        GF_XXH32_copyState
        GF_XXH32_reset
        GF_XXH32_update
        GF_XXH32_digest
        GF_XXH32_canonicalFromHash
        GF_XXH32_hashFromCanonical
        GF_XXH64
        GF_XXH64_createState
        GF_XXH64_freeState
        GF_XXH64_copyState
        GF_XXH64_reset
        GF_XXH64_update
        GF_XXH64_digest
        GF_XXH64_canonicalFromHash
        GF_XXH64_hashFromCanonical
    
        ---- Data Types ----
        GF_XXH_errorcode
        GF_XXH32_state_t*
        GF_XXH32_canonical_t*
        GF_XXH32_hash_t
        GF_XXH64_state_t*
        GF_XXH64_canonical_t*
        GF_XXH64_hash_t
    
    It is linked with libglusterfs.so. A wrapper
    funtion is also added for the easy usage in
    common-utils.c.
    
    xxhash can be used for the all the usecases where
    a faster non-cryptographic hash is required.
    gfid to path infra would be using this for now.
    
    NOTE:
    ----
    The gluster coding guidelines check is ignored
    as maintaining it further would be difficult.
    
    Updates: #253
    Change-Id: Ib143f90d91d4ee99864a10246d5983e92900173b
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17641
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit d95535bae2d200c2210feac7568b1fdbf6f545a9
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Jun 26 18:20:23 2017 +0530

    tools/glusterfind: unquote DELETE path before further processing
    
    Problem:
    DELETE path is quoted before it reaches glusterfind. This wasn't handled
    in the glusterfind code leading to double quoting of path separator
    '%2F' to '%252F' i.e. the '%' character in '%2F' itself was quoted to
    '%25'
    
    Solution:
    unquote the the deleted path before further processing
    
    Change-Id: I2dfbbd7792dc0f9da5c8e02093b0f1c031ff344a
    BUG: 1465024
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/17629
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 97defef2375b911c7b6a3924c242ba8ef4593686
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jun 28 09:10:53 2017 +0530

    features/shard: Remove ctx from LRU in shard_forget
    
    Problem:
    There is a race when the following two commands are executed on the mount in
    parallel from two different terminals on a sharded volume,
    which leads to use-after-free.
    
    Terminal-1:
    while true; do dd if=/dev/zero of=file1 bs=1M count=4; done
    
    Terminal-2:
    while true; do cat file1 > /dev/null; done
    
    In the normal case this is the life-cycle of a shard-inode
    1) Shard is added to LRU when it is first looked-up
    2) For every operation on the shard it is moved up in LRU
    3) When "unlink of the shard"/"LRU limit is hit" happens it is removed from LRU
    
    But we are seeing a race where the inode stays in Shard LRU even after it is
    forgotten which leads to Use-after-free and then some memory-corruptions.
    
    These are the steps:
    1) Shard is added to LRU when it is first looked-up
    2) For every operation on the shard it is moved up in LRU
    
    Reader-handler                                    Truncate-handler
    1) Reader handler needs shard-x to be read.     1) Truncate has just deleted shard-x
    2) In shard_common_resolve_shards(), it does
       inode_resolve() and that leads to
       a hit in LRU, so it is going to call
    __shard_update_shards_inode_list() to move the
       inode to top of LRU
    						2) shard-x gets unlinked from the itable
    						   and inode_forget(inode, 0) is called
    						   to make sure the inode can be purged
    						   upon last unref
    3) when __shard_update_shards_inode_list() is
       called it finds that the inode is not in LRU
       so it adds it back to the LRU-list
    
    Both these operations complete and call inode_unref(shard-x) which leads to the inode
    getting freed and forgotten, even when it is in Shard LRU list. When more inodes are
    added to LRU, use-after-free will happen and it leads to undefined behaviors.
    
    Fix:
    I see that the inode can be removed from LRU even by the protocol layers like gfapi/gNFS
    when LRU limit is reached. So it is better to add a check in shard_forget() to remove itself
    from LRU list if it exists.
    
    BUG: 1466037
    Change-Id: Ia79c0c5c9d5febc56c41ddb12b5daf03e5281638
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17644
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 56da27cf5dc6ef54c7fa5282dedd6700d35a0ab0
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jun 29 10:52:37 2017 +0530

    cluster:dht Fix crash in dht_rename_lock_cbk
    
    Use a local variable to store the call count
    in the STACK_WIND for loop. Using frame->local
    is dangerous as it could be freed while the loop
    is still being processed
    
    Change-Id: Ie65cdcfb7868509b4a83bc2a5b5d6304eabfbc8e
    BUG: 1466110
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17645
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit c0f1db29a2d8b3eb1311ad60c2935da0aff7ab70
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 14 13:31:42 2017 +0530

    logging: Support for Structured logging format
    
    Wrapper for `gf_log` and `gf_msg` to add support for
    structured logging format.
    
    Two new wrappers available `gf_slog` and `gf_smsg`
    
    Example 1: All static details
    
        gf_slog ("cli", GF_LOG_INFO, "Volume Set",
                 "name=gv1",
                 "option=changelog.changelog",
                 "value=on",
                 NULL);
    
        gf_smsg ("cli", GF_LOG_INFO, 0, MSGID_VOLUME_SET,
                 "Volume Set",
                 "name=gv1",
                 "option=changelog.changelog",
                 "value=on",
                 NULL);
    
    Example 2: Using Format chars in key values
    
        gf_slog ("cli", GF_LOG_INFO, "Volume Set",
                 "name=%s", volume_name,
                 "option=%s", option_name,
                 "value=%s", option_value,
                 NULL);
    
        gf_smsg ("cli", GF_LOG_INFO, 0, MSGID_VOLUME_SET,
                 "Volume Set",
                 "name=%s", volume_name,
                 "option=%s", option_name,
                 "value=%s", option_value,
                 NULL);
    
    Formats as,
    
        <EVENT><TAB><KEY1=VALUE1><TAB><KEY2=VALUE2>...
    
    Example:
    
        Volume Set	name=gv1	option=changelog.changelog	value=on
    
    Updates: #240
    Change-Id: I871727be16a39f681d41f363daa0029b8066fb52
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17543
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit e9c5b61861299add8bf4b61382611cda68ebb68c
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Tue Jun 27 07:21:28 2017 -0700

    libglusterfs: fix disable-mempool
    
    Change-Id: I55f707ae1e7c3ad7fc0545f7aa657584cead58f9
    BUG: 1465214
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17636
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ji-Hyeon Gim
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 91db0d47ca267aecfc6124a3f337a4e2f2c9f1e2
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jun 26 21:12:56 2017 +0530

    cluster/dht: Check if fd is opened on dst subvol
    
    If an fd is opened on a file, the file is migrated
    and the cached subvol is updated in the inode_ctx
    before an fd based fop is sent, the fop is sent to
    the dst subvol on which the fd is not opened.
    This causes the FOP to fail with EBADF.
    
    Now, every fd based fop will check to see that the fd
    has been opened on the dst subvol before winding it down.
    
    Change-Id: Id92ef5eb7a5b5226688e2d2868b15e383f5f240e
    BUG: 1465075
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17630
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 630d3d8c8466228e1764c1c0962b9db40548fffb
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Jun 22 17:06:40 2017 +0530

    ec: Increase notification in all the cases
    
    Problem:
    "gluster v heal <volname> info" is taking
    long time to respond when a brick is down.
    
    RCA:
    Heal info command does virtual mount.
    EC wait for 10 seconds, before sending UP call to upper xlator,
    to get notification (DOWN or UP) from all the bricks.
    
    Currently, we are increasing ec->xl_notify_count based on
    the current status of the brick. So, if a DOWN event notification
    has come and brick is already down, we are not increasing
    ec->xl_notify_count in ec_handle_down.
    
    Solution:
    Handle DOWN even as notification irrespective of what
    is the current status of brick.
    
    Change-Id: I0acac0db7ec7622d4c0584692e88ad52f45a910f
    BUG: 1464091
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/17606
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 24d09edf4b13d72a8707c801939921de0d32d4dd
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 27 21:09:49 2017 +0530

    glusterd: mark brickinfo to started on successful attach
    
    brickinfo's port & status should be filled up only when attach brick is
    successful.
    
    Change-Id: I68b181be37cb94d176f0f4692e8d9dac5493181c
    BUG: 1465559
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17640
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 68cb9356d19cba5da7f8a719baca47d34e1740b7
Author: Ji-Hyeon Gim <potatogim@gluesys.com>
Date:   Tue Jun 6 11:18:57 2017 +0900

    libglusterfs: build failed with GF_DISABLE_MEMPOOL
    
    When we build GlusterFS with GF_DISBLE_MEMPOOL, it is failed due to macro
    condition in mem-pool.c:mem_get().
    
    Change-Id: I03fe804f93d761ea3bfdc3b20f0253a03350a68f
    BUG: 1465214
    Signed-off-by: Ji-Hyeon Gim <potatogim@potatogim.net>
    Reviewed-on: https://review.gluster.org/17633
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Ji-Hyeon Gim
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b71059960f8c67d9a058244d2a1c748be4fe1323
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Jun 22 16:57:04 2017 +0530

    glusterd: brick process fails to restart after gluster pod failure
    
    Problem: In container environment sometime after delete gluster pod
             and created new gluster pod brick process doesn't seem
             to come up.
    
    Solution: On the basis of logs it seems glusterd is trying to attach
              with non glusterfs process.Change the code of function
              glusterd_get_sock_from_brick_pid to fetch socketpath from argument
              of running brick process.
    
    BUG: 1464072
    Change-Id: Ida6af00066341b683bbb4440d7a0d8042581656a
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17601
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 4700c5be55b0e567755b4c8a1a91f33d29c06e6b
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Jun 21 17:52:45 2017 +0530

    cluster/rebalance: Use GF_XATTR_LIST_NODE_UUIDS_KEY to figure out local subvols.
    
    Afr has introduced a new key GF_XATTR_LIST_NODE_UUIDS_KEY,
    through which rebalance will figure out its local subvolumes.(Reference
    bugid=1463250)
    
    key: GF_XATTR_NODE_UUID_KEY will continue to serve it's old
    purpose of returning the first afr chiild.
    
    test: prove tests/basic/distribute/rebal-all-nodes-migrate.t
    
    Change-Id: I4d602feda2a05b29d2210c712a07a4ac6b8bc112
    BUG: 1463648
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17595
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit d66fb14a952729caf51c8328448a548c4d198082
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jun 22 15:56:28 2017 +0530

    cluster/dht: rebalance gets file count periodically
    
    The rebalance used to get the file count in the beginning
    and not update it. This caused estimates to fail
    if the number changed during the rebalance.
    
    The rebalance now updates the file count periodically.
    
    Change-Id: I1667ee69e8a1d7d6bc6bc2f060fad7f989d19ed4
    BUG: 1464110
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17607
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 0c0bc42ddfef4f05b50c3d1510e93ef3ec292a56
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Wed Jun 21 16:37:09 2017 +0530

    cluster/ec: Node uuid xattr support update for EC
    
    Problem:
    The change in EC to return list of node uuids for
    GF_XATTR_NODE_UUID_KEY was causing problems with
    geo-rep.
    
    Fix:
    This patch will allow to get the single node uuid
    as it was doing before with the key
    "GF_XATTR_NODE_UUID_KEY", and will also allow to get
    the list of node uuids by using a new key
    "GF_XATTR_LIST_NODE_UUIDS_KEY". This will solve
    the problem with geo-rep and any other features which
    were depending on this.
    
    BUG: 1462790
    Change-Id: I2d9214a9658d4a41a3d6de08600884d2bda5f3eb
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/17594
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b27e60a0cbdb42755cd7d4ee3c7e62b57d5881ba
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu May 18 14:53:47 2017 +0530

    gfapi: Enhance testscript for glfs_xreaddirplus
    
    Enhance the script testing glfs_xreaddirplus functionality
    and also measure the performance difference when compared to
    using the older method.
    
    Change-Id: I590d07c850994afab0a02eb5dccb8342224aa6b7
    BUG: 1442950
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: https://review.gluster.org/17329
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 237648780336d41cd6d820c337b38dd13f4d9e72
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu May 18 11:22:16 2017 +0530

    dht/hardlink : Remove stale linkto file incase of failure
    
    This is a similar issue fixed for rename in https://review.gluster.org/#/c/16016/
    For hardlinks, if cached and hashed subvolumes are different, then it will first
    create linkto file in hashed using root permission, but actually hardlink creation
    fails with EACESS and stale linkto file is never removed.All the followup hardlink
    calls with file name will result ESTALE because linktofile creation fails with EEXIST
    and follow up lookup on linkto file returns gfid-mismatching(old linkto file) and
    finally fails with ESTALE
    
    Steps to produce :
    (From link/00.t test from posix-testsuite)
    Steps executed in script
     * create a file "abc" using root
     * change the ownership of file to a non root user
     * create hardlink "link" for "abc" using a non root user, it fails with EACESS
     * delete "abc"
     * create directory "abc" using root
     * again try to create hadrlink "link" for "abc" using non root user, fails with ESTALE
    
    Also tried to fix other bugs in dht_linkfile_create_cbk() and posix_lookup.
    
    Thanks Susant for the help in debugging the issue and suggestion for this patch.
    
    Change-Id: I7a5a1899d3fd1fdb13578b37f9d52a084492e35d
    BUG: 1452084
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/17331
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b2522297dd1e8b444a75b9cf177b2e6f6dffa05e
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Thu Jun 15 11:39:56 2017 +0530

    doc: Update GlusterFS README
    
    Reorganizing GlusterFS README contents.
    
    BUG: 1461648
    Change-Id: I3696e41963c536679d04934930d491f425ffe1ad
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/17550
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b224f4253b7d3de3077ee35c8bdc20618eae4b7c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jun 20 06:26:18 2017 -0400

    feature/changelog: Fix buffer overflow crash
    
    The buffer used to hold the basename  was hard coded
    to the size of NAME_MAX(255). It might lead to buffer
    overflow crashes when the basename which is sent
    is more than NAME_MAX length. Fixed the same.
    
    Change-Id: I6c1cad3ccaeb8c55549b1d3c5f96a198f65ba2b7
    BUG: 1463178
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17579
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 3183ca1bdee9cb0af22c017e3c610add8ff2b405
Author: Hendrik Visage <hvjunk@gmail.com>
Date:   Fri May 19 12:21:37 2017 +0530

    scripts/shared_storage : systemd helper scripts to mount shared storage post reboot
    
    Reported-by: Hendrik Visage <hvjunk@gmail.com>
    Change-Id: Ibcff56b00f45c8af54c1ae04974267c2180f5f63
    BUG: 1452527
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/17339
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a052b413242783f39cb3312a6a02bdd025b10f0c
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Sun Jun 11 07:33:52 2017 +0530

    gfapi : Resolve "." and ".." only for named lookups
    
    The patch https://review.gluster.org/#/c/17177 resolves "." and ".."
    to corrosponding inodes and names before sending the request to the
    backend server. But this will only work if inode and its parent is
    linked properly. Incase of nameless lookup(applications like ganesha)
    the inode of parent can be NULL(only gfid is send). So this patch will
    resolve "." and ".." only if proper parent is available
    
    Change-Id: I4c50258b0d896dabf000a547ab180b57df308a0b
    BUG: 1460514
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/17502
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 475ec9928ef96b63a0bfa859a9ae68709275033c
Author: karthik-us <ksubrahm@redhat.com>
Date:   Mon Jun 19 19:54:36 2017 +0530

    cluster/afr: Returning single and list of node uuids from AFR
    
    Problem:
    The change in afr to return list of node uuids was causing problems
    with geo-rep.
    
    Fix:
    This patch will allow to get the single node uuid as it was doing
    before with the key "GF_XATTR_NODE_UUID_KEY", and will also allow
    to get the list of node uuids by using a new key
    "GF_XATTR_LIST_NODE_UUIDS_KEY". This will solve the problem with
    geo-rep and any other feature which were depending on this.
    
    Change-Id: I09885dac6dfca127be94b708470c8c2941356f9a
    BUG: 1462790
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: https://review.gluster.org/17576
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ee9a2f01adb6c089f4579c5e0b7f5eed335dd0df
Author: AnkitRaj <anraj@redhat.com>
Date:   Mon Jun 5 14:11:43 2017 +0530

    dht: passing the errno as an argument to gf_msg
    
    There are many calls in gf_msg where errno
    is needed to pass as an argument instead of
    strerrno(error)
    
    Change-Id: I15048a5e0b41f9752a2023afe8470eca6f2cd383
    Bug: 1454701
    Signed-off-by: AnkitRaj <anraj@redhat.com>
    Reviewed-on: https://review.gluster.org/17464
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Karthik U S <ksubrahm@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 426c2908aee4addd36d925ee93e56c9b2688ec1b
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jun 19 11:50:28 2017 +0530

    cluster/dht: Additional checks for rebalance estimates
    
    The rebalance estimates calculation was not handling
    calculations correctly when no files had been processed,
    i.e., when rate_lookedup was 0.
    
    Now, the estimated time is set to 0 in such scenarios as
    there is no way for rebalance to figure out how long the
    process will take to complete without knowing the rate at
    which the files are being processed.
    
    Change-Id: I7b6378e297e1ba139852bcb2239adf2477336b5b
    BUG: 1457985
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17564
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 0a8dac38ac4415ea770fb36b34e3c494e8713e6e
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jun 15 18:09:36 2017 +0530

    geo-rep: Structured log support
    
    Changed all log messages to structured log format
    
    Change-Id: Idae25f8b4ad0bbae38f4362cbda7bbf51ce7607b
    Updates: #240
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17551
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 52d0886cfbcdfd69fa0cac0a6d51cd8811d8c6d7
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Sun Jun 18 23:10:57 2017 +0530

    glusterd.service (systemd), shows "Active failed" when gd in stop state
    
    While doing cleanupandexit glusterd was handling the signal SIGTERM which
    is clean exit but systemd treats it as failure being a non-zero value.
    
    With this fix dependency "SuccessExitStatus " has been added
    in glusterd.service which takes care of service stop properly.
    
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    
    Change-Id: Ie5216722632a245f787fd69bfbbf8d0f0068bccb
    BUG: 1462200
    Reviewed-on: https://review.gluster.org/17559
    Tested-by: Gaurav Yadav <gyadav@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 61924b98a61108a7ec453fb7f1fc5487d1386e56
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jun 19 13:45:55 2017 +0530

    posix: Revert modifying op_errno in __posix_fd_ctx_get
    
    https://review.gluster.org/#/c/17414/ converted ENOENT to EBADFD because
    ENOENT is not a valid error for fd based operations, but this apparently
    breaks dht rebalance behaviour (see comments in the backport 17517. So
    reverting that part of the change.
    
    Change-Id: Idcf5c65a47b096a3766cf7f20ca938d988572052
    BUG: 1456582
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17565
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 3011af67734ac1ef0e73775dc265483f2c5dea91
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Jun 16 18:39:08 2017 +0530

    tools/glusterfind: initialize variable 'end'
    
    Problem:
    syntax error due to uninitialized variable 'end'
    
    Solution:
    set end = -1
    
    Change-Id: Ia8b500e9dd5304d0832e5f594abca0b5b2ab357e
    BUG: 1462241
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/17557
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 45ebcf7009f549f022c36b4d537eeac62ecfd020
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 12 22:06:18 2017 +0530

    cluster/afr: Implement quorum for lk fop
    
    Problem:
    At the moment when we have replica 3 or arbiter setup, even when
    lk succeeds on just one brick we give success to application which
    is wrong
    
    Fix:
    Consider quorum-number of successes as success when quorum is enabled.
    
    BUG: 1461792
    Change-Id: I5789e6eb5defb68f8a0eb9cd594d316f5cdebaea
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17524
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit b58a15948fb3fc37b6c0b70171482f50ed957f42
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 15 15:36:07 2017 +0530

    index: Do not proceed with init if brick is not mounted
    
    ..or else when a volume start force is given, we end up creating
    /brick-path/.glusterfs/indices folder and various subdirs under it and
    eventually starting the brick process.
    
    As a part of this patch, glusterd_get_index_basepath() is added in
    glusterd, who will then use it to create the basepath during
    volume-create, add-brick, replace-brick and reset-brick. It also uses this
    function to set the 'index-base' xlator option for the index translator.
    
    Change-Id: Id018cf3cb6f1e2e35b5c4cf438d1e939025cb0fc
    BUG: 1457202
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17426
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 26ca39ccf0caf0d55c88b05396883dd10ab66dc4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 13 23:35:40 2017 +0530

    cluster/ec: lk shouldn't be a transaction
    
    Problem:
    When application sends a blocking lock, the lk fop actually waits under
    inodelk.  This can lead to a dead-lock.
    1) Let's say app-1 takes exculsive-fcntl-lock on the file
    2) app-2 attempts an exclusive-fcntl-lock on the file which goes to blocking
       stage note: app-2 is blocked inside transaction which holds an inode-lock
    3) app-1 tries to perform write which needs inode-lock so it gets blocked on
       app-2 to unlock inodelk and app-2 is blocked on app-1 to unlock fcntl-lock
    
    Fix:
    Correct way to fix this issue and make fcntl locks perform well would be to
    introduce
    2-phase locking for fcntl lock:
    1) Implement a try-lock phase where locks xlator will not merge lk call with
       existing calls until a commit-lock phase.
    2) If in try-lock phase we get quorum number of success without any EAGAIN
       error, then send a commit-lock which will merge locks.
    3) In case there are any errors, unlock should just delete the lock-object
       which was tried earlier and shouldn't touch the committed locks.
    
    Unfortunately this is a sizeable feature and need to be thought through for any
    corner cases.  Until then remove transaction from lk call.
    
    BUG: 1455049
    Change-Id: I18a782903ba0eb43f1e6526fb0cf8c626c460159
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17542
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit f0fb166078d59cab2a33583591b6448326247c40
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 15 08:31:06 2017 -0400

    feature/bitrot: Fix ondemand scrub
    
    The flag which keeps tracks of whether the scrub
    frequency is changed from previous value should
    not be considered for on-demand scrubbing. It
    should be considered only for 'scrub-frequency'
    where it should not be re-scheduled if it is
    set to same value again. But in case ondemand
    scrub, it should start the scrub immediately
    no matter what the scrub-frequency.
    
    Reproducer:
    1. Enable bitrot
    2. Set scrub-throttle
    3. Set ondemand scrub
    Make sure glusterd is not restarted while doing
    below steps
    
    Change-Id: Ice5feaece7fff1579fb009d1a59d2b8292e23e0b
    BUG: 1461845
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17552
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit b9fb7ea63d6120faaeb75ffa0cafbc0ab0e4a619
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri May 26 15:56:59 2017 +0530

    debug/io-stats: Provide option to select stats output format
    
    ... as opposed to hardcoding it to "json" always.
    
    Change-Id: I5e79473a514373145ad764f24bb6219a6983a4c6
    BUG: 1458197
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17451
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 79efd0081fc5e24f6878d87a6dd8eb5253693d8f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jun 12 08:18:30 2017 -0400

    .testignore: if a file doesn't change any code/behavior, add it here
    
    So, the regression tests won't run if the changes in the patch is for
    only files belonging to this file. Helps in reducing the load on overall
    regression framework.
    
    Credits: Nigel Babu <nigelb@redhat.com>
    
    Change-Id: Icaa351b19cdcbe5af9a64c03b90f530aab297ee1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/17522
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit cd67c34e64e2c85a7d0abbce43a1db269a12be19
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jun 15 11:31:39 2017 +0530

    glusterd: fix crash on statedump when no volumes are started
    
    pmap object is created when glusterd allocates a port for the very first
    time, however before that if someone tries to take statedump glusterd
    will crash.
    
    Solution : Add a NULL check before accessing pmap reference.
    
    Change-Id: I206b02e07a4717e68af2c6bf05fac55119353de8
    BUG: 1461655
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17549
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b1a6297ec323bfda27068b9579d2848cd8f48b0d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Jun 13 14:40:09 2017 +0530

    geo-rep: Added metrics related to Sync Time
    
    In Geo-rep, Sync jobs can be configured using, `config sync-jobs 3`. This
    patch adds following information related to the sync job(Rsync/Tarssh)
    
    Example output:
    
        [2017-06-13 09:09:32.532181] I [master(/bricks/b1):1713:syncjob] Syncer: \
            Sync Time Taken (Job:2 Files:5484 ReturnCode:0): 4.8774 secs
    
    Change-Id: Ifceb96d4b8d14e00fd1290c0aeff60d64b4d7f37
    BUG: 1455179
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17531
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit c5b81783d5532a3b3a2bd1948bd1c9bfa4a023e1
Author: Michael Adam <obnox@samba.org>
Date:   Tue Jun 13 10:06:57 2017 +0200

    glusterd: fix quorum calculation if percentage is not specified correctly
    
    There was an extra "ratio = _gf_true".
    
    - In case the ratio was specified correctly
      in the volfile, this is redundant.
    - In case the ratio was specified, but not parseable
      into a precentage, this is wrong and would
      lead to a quorum count of 0 instead of falling
      back to the default of 50% + 1.
    
    This patch removes the extra setting of "ratio".
    
    Change-Id: I2bd57ebf1b8989e905481a2b6285a1f422942f72
    BUG: 1461129
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: https://review.gluster.org/17538
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ca97c98cc633e3b82a65291969d8bd8f8d8d5d3e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Jun 11 15:43:58 2017 -0400

    dht: reduce duplicate code in tier migrate
    
    Updates #234
    
    Change-Id: I016f6d4f1e5ad2ea56a611c1bffbd189f10650db
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/17525
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c0d4081cf4b90a4316b786cc53263a7c56fdb344
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jun 12 11:17:01 2017 +0530

    Revert "glusterd: disallow rebalance & remove-brick on a sharded volume"
    
    This reverts commit 8375b3d70d5c6268c6770b42a18b2e1bc09e411e.
    
    Now that some of the users have confirmed rebalance works fine without
    causing corruption of VMs, time to revert the CLI restriction.
    
    Change-Id: I45493fcbb1f25fd0fff27b2b3526c42642ccb464
    BUG: 1460585
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17506
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 778ad0e2bbfe60db32df460590e0c3596fdf1aa5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jun 12 11:05:27 2017 +0530

    geo-rep: Fix string format issue caused due to #17489
    
    With Patch #17489, values from Geo-rep config always represented
    as Unicode string, which is not compatible with rest of the code.
    
    Changed the format with this patch to fix the issue.
    
    BUG: 1459620
    Change-Id: I935fca0d24f02e90757f688f92ef73fad9f9b8e1
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17503
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 7674584fa53944a4e982e217798f31a3d1ef313b
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri May 26 15:45:57 2017 +0530

    nl-cache: Fix a possible crash and stale cache
    
    Issue1:
    Consider the followinf sequence of operations:
       ...
       nlc_ctx = nlc_ctx_get (inode i1)
       ....... -> nlc_clear_cache (i1) gets called as a part of nlc_invalidate
                                       or any other callers
                  ...
                  GF_FREE (ii nlc_ctx)
       LOCK (nlc_ctx->lock);  ->  This will result in crash as the ctx
                                  got freed in nlc_clear_cache.
    
    Issue2:
       lookup on dir1/file1 result in ENOENT
       add cache to dir1 at time T1
       ....
       CHILD_DOWN at T2
       lookup on dir1/file2 result in ENOENT
       add cache to dir1, but the cache time is still T1
       lookup on dir1/file2 - should have been served from cache
                              but the cache time is T1 < T2, hence
                              cache is considered as invalid.
    So, after CHILD_DOWN the right thing would be to clear the cache
    and restart caching on that inode.
    
    Solution:
    Do not free nlc_ctx in nlc_clear_cache, but only in inode_forget()
    The fix for both issue1 and 2 is interleaved hence sending it as
    single patch.
    
    Change-Id: I83d8ed36c049a93567c6d7e63d045dc14ccbb397
    BUG: 1458539
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17453
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 05b2fbd077cadc409994762e346ef94f4904545b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jun 12 15:09:10 2017 +0530

    ec: fix ec-data-heal.t failure
    
    With brick mux enabled, this test was constantly failing. Further it was
    found that the the test does a series of killing a particular brick and
    bringing it up in cmdline where as just starting the volume with force
    would suffice.
    
    Change-Id: Iee491d0777eaa28dca5c78f92d4b400fcc897fd2
    BUG: 1460638
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/17508
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e97c32ee9913969a726f8a8286cf714f907729d6
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jun 12 10:59:04 2017 +0530

    readdir-ahead: Fix duplicate listing and cache size calculation
    
    Issue:
    If a opendir is followed by a closedir without readdir, though
    the prefetched entries were freed, the freed size was not accounted
    in priv->rda_cache_size. Thus the cache limit will exceed if there
    are multiple opendir followed by closedir.
    
    Fix:
    Fix the pric->rda_cache_size calculation. Also have removed the
    inode_ctx_size. Each perf xlator has its own cache limit that
    it works with. Also the inode_ctx size can change, if a forget/
    invalidate or any other factor triggers the inode_ctx size.
    
    Change-Id: I9707ec558076ce046e58a55989ec9513c70ea029
    BUG: 1431908
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17504
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit dbdf56ae3f87fc2765ad9cb528c1cfbadfde96ec
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Jun 6 12:27:28 2017 +0530

    tools/glusterfind: add --end-time option
    
    Add optional --end-time argument to be used with --since-time
    when using the "query" command.
    
    "start" and "end" times are passed in the command-line to
    changelog.py only if --full has not been specified on command-line.
    -1 is passed to changelog.py as end time if user has not supplied
    --end-time on command-line.
    
    brickfind.py:
    Remove unused "start" command-line argument.
    
    Also:
    Minor indentation changes to keep flake8-2.7 happy.
    
    Change-Id: I063ef5459916f711503881ade5c4fc32374edad0
    BUG: 1453151
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/17439
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 64588d4f6d69ce6e9b82335d12fa6c42794c38fa
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Jun 6 23:43:54 2017 +0530

    tools/glusterfind: add --field-separator option
    
    Problem:
    Default field separator is a space character.
    This gets in the way if the file name itself has embedded spaces.
    
    Solution:
    Add --field-separator option to "pre" and "query" commands.
    The field separator string will be used to separate strings in the
    output lines that get written to the output file.
    
    eg.
    old output:
    NEW file1.txt
    RENAME file2 Copy.txt file3.txt
    
    with --field-separator as "==="
    new output:
    NEW===file1.txt
    RENAME===file2 Copy.txt===file3.txt
    
    Change-Id: I71e878fed58ba1113d97044ac9f6404ee66227c7
    BUG: 1453151
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/17481
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 33b426aa9f62f6c8abb2b537b7a784c5b8090fb3
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jun 8 11:06:32 2017 +0530

    md-cache: Fix the dump of stat inode in .meta and statedump
    
    Change-Id: If61ed5e4462e98d18a1370734a0bcee1ed94d82d
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17491
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 38780ff2d0717cd800a49072879a664b04385fd1
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jun 9 11:31:19 2017 +0530

    nl-cache: add group volume set option for ease of use
    
    Change-Id: Id03643a9598da53051a01ca09e1d2a62bc195ab6
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17495
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 801697cc08928660a8087d08122a3aed622f6790
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jun 9 17:10:00 2017 +0530

    glusterd: log stale rpc disconnects occasionally
    
    There might be situations where if a brick process is killed through
    SIGKILL (not SIGTERM) when brick mux is enabled glusterd will continue to
    receive disconnect events from the stale rpc which might flood the
    glusterd log. Fix is to use GF_LOG_OCCASIONALLY.
    
    Change-Id: I95a10c8be2346614e0a3458f98d9f99aab34800a
    BUG: 1460225
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17499
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 5b82f173ba337b2fe06846c2a0e5f35d1ff53357
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Jun 8 13:04:42 2017 +0530

    glusterfsd: Deletion of brick dir throw emerg msgs after stop volume
    
    Problem: Deletion of brick directories throw emerg messages after stop
             volume while brick mux is enabled.
    
    Solution: Modify the posix health check monitor thread code to
              handled correctly.
    
    BUG: 1459781
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    
    Change-Id: I2d22a84f9a98b0da261e5fb7850ba1368f3601d7
    Reviewed-on: https://review.gluster.org/17492
    Tested-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d95aa04e482ebe4306df721fe0aa3697a0426a85
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Jun 2 16:28:40 2017 +0530

    gfapi: change root lookup from nameless to named lookup
    
    Problem:
    
    During component resolve we do lookup on root based on
    root gfid. If we are doing nameless lookup, then md-cache
    won't be able to serve those lookup.
    
    Solution:
    
    With this patch, we covert nameless lookup to named lookup
    on root.
    
    Credits: Poornima G <pgurusid@redhat.com>
    
    Change-Id: Ie64141936fd294d8969c39e3bd4dbc73ee375c6b
    BUG: 1458768
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17465
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 149db390fd89beee1e8a3d946d4224ba2a9b4711
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jun 2 10:05:33 2017 +0530

    upcall: Update the access time in missing cases
    
    Issue: In fops like rename, link, unlink etc, the parent
    dirrs' client access time was not being updated. And in fops like
    create, link, symlink etc. the new file/dirs' client access time was
    not updated.
    
    Solution: Update the client access time for both parent and new entry.
    
    Change-Id: Id9f63583216ae857f6251dca15797ac66fa85430
    BUG: 1458127
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17450
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 68f2192df570b5ee615d440c2e0c88d49a75a34f
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jun 8 22:19:17 2017 +0530

    posix-acl: Whitelist virtual ACL xattrs
    
    Similar to system.posix_acl_* xattrs, all users should get
    permission to be able to read glusterfs.posix.acl* xattrs too.
    
    Change-Id: I1fc2b67c8a12113910e4ec57cd114e4baefe0d38
    BUG: 1459971
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: https://review.gluster.org/17493
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 66b8462719bee337db85abc5b2ed8657b71f073c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 30 18:01:26 2017 +0530

    debug/trace: Implement seek fop
    
    Change-Id: Idd1b92201348a76a6145b38799a3a46cab730540
    BUG: 1458193
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17437
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 0a20e56d07de3e467e09da885a6b71cdc165de17
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon May 29 16:00:24 2017 +0530

    protocol/server: make listen backlog value as configurable
    
    problem:
    
    When we call listen from protocol/server, we are giving a
    hard coded valie of 10 if it is not manually given.
    With multiplexing, especially when glusterd restarts all
    clients may try to connect to the server at a time.
    Which will result in overflowing the queue, and kernel
    will complain about the errors.
    
    Solution:
    
    This patch will introduce a volume set command to make backlog
    value as a configurable. This patch also changes the default
    values for backlog from 10 to 128. This changes is only applicable
    for sockets listening from protocol.
    
    Example:
    
    gluster volume set <volname> transport.listen-backlog 1024
    
    Note: 1 Brick has to be restarted to get this value in effect
          2 This changes won't be reflected in glusterd, or other
            xlators which calls listen. If you need, you have to
            add this option to the volfile.
    
    Change-Id: I0c5a2bbf28b5db612f9979e7560e05dd82b41477
    BUG: 1456405
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17411
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 513984ad90531c53fcb7d6f0d581f198a6afcf93
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Jun 6 17:59:59 2017 +0530

    geo-rep: Fix ConfigInterface Template issue
    
    ConfigParser uses string Template to substitute the dynamic values
    for config. For some of the configurations, Geo-rep worker will
    not restart. Due to this conf object may have non string values.
    
    If val is not string in Template(val), then it fails with
    "TypeError: expected string or buffer"
    
    BUG: 1459620
    Change-Id: I25b8bbc1df42f6f29e9563a55b3e27a228321c44
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17489
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 0a07cffbf363e35e9617e5d4ef605f26ede06f05
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Jun 6 13:44:06 2017 +0530

    glusterfsd: Sometime brick process is crashed after enable brick mux
    
    Problem: glusterfsd is getting Segfault while running bug-1432542-mpx-restart-crash.t
             in a loop in while brick mux is enabled.
    
    Solution: Change the index_worker code as well as notify code in index.c
              to cleanup index_worker thread appropriately.
    
    BUG: 1459402
    Change-Id: Id036664dc34309dd3f6e54746fc2724182cb074f
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17471
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit bae51359b4a3a7a9c16424b43eb5ad14f0fcad53
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 6 17:45:51 2017 +0530

    glusterd: fix glusterd crash from glusterd_op_ac_rcvd_brick_op_acc
    
    In out label, before checking ev_ctx->rsp_dict we should first check if
    ev_ctx is not NULL
    
    Change-Id: I28f4f1ee9070617a0e6a23a43af8c5756f96a47e
    BUG: 1452956
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17478
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit c9860430a77f20ddfec532819542bb1d0187c06e
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jun 1 22:13:41 2017 +0530

    cluster/dht: Include dirs in rebalance estimates
    
    Empty directories were not being considered while
    calculating rebalance estimates leading to negative
    time-left values being displayed as part of the
    rebalance status.
    
    Change-Id: I48d41d702e72db30af10e6b87b628baa605afa98
    BUG: 1457985
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17448
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 88c67b72b1d5843d11ce7cba27dd242bd0c23c6a
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Apr 3 12:46:29 2017 +0530

    cluster/ec: Update xattr and heal size properly
    
    Problem-1 : Recursive healing of same file is happening
    when IO is going on even after data heal completes.
    
    Solution:
    RCA: At the end of the write, when ec_update_size_version
    gets called, we send it only on good bricks and not
    on healing brick. Due to this, xattr on healing brick
    will always remain out of sync and when the background
    heal check source and sink, it finds this brick to be
    healed and start healing from scratch. That involve
    ftruncate and writing all of the data again.
    
    To solve this, send xattrop on all the good bricks as
    well as healing bricks.
    
    Problem-2: The above fix exposes the data corruption
    during heal. If the write on a file is going on and
    heal finishes, we find that the file gets corrupted.
    
    RCA:
    The real problem happens in ec_rebuild_data(). Here we receive the
    'size' argument which contains the real file size at the time of
    starting self-heal and it's assigned to heal->total_size.
    
    After that, a sequence of calls to ec_sync_heal_block() are done. Each
    call ends up calling ec_manager_heal_block(), which does the actual work
    of healing a block.
    
    First a lock on the inode is taken in state EC_STATE_INIT using
    ec_heal_inodelk(). When the lock is acquired, ec_heal_lock_cbk() is
    called. This function calls ec_set_inode_size() to store the real size
    of the inode (it uses heal->total_size).
    
    The next step is to read the block to be healed. This is done using a
    regular ec_readv(). One of the things this call does is to trim the
    returned size if the file is smaller than the requested size.
    
    In our case, when we read the last block of a file whose size was = 512
    mod 1024 at the time of starting self-heal, ec_readv() will return only
    the first 512 bytes, not the whole 1024 bytes.
    
    This isn't a problem since the following ec_writev() sent from the heal
    code only attempts to write the amount of data read, so it shouldn't
    modify the remaining 512 bytes.
    
    However ec_writev() also checks the file size. If we are writing the
    last block of the file (determined by the size stored on the inode that
    we have set to heal->total_size), any data beyond the (imposed) end of
    file will be cleared with 0's. This causes the 512 bytes after the
    heal->total_size to be cleared. Since the file was written after heal
    started, the these bytes contained data, so the block written to the
    damaged brick will be incorrect.
    
    Solution:
    Align heal->total_size to a multiple of the stripe size.
    
    Thanks "Xavier Hernandez" <xhernandez@datalab.es>
    to find out the root cause and to fix the issue.
    
    Change-Id: I6c9f37b3ff9dd7f5dc1858ad6f9845c05b4e204e
    BUG: 1428673
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/16985
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 4dba0d5f8d9ac13504087f553d7c730060f0f9c7
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Jun 4 20:19:19 2017 +0530

    cli: add 'all' option in gluster v get cli usage
    
    Change-Id: If216b13b7f9072f875eb2c5019d3b50b8bf3313e
    BUG: 1458582
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17460
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit 7b58ec260152bdcf840ac622dbb883ce8b593f63
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jun 1 22:05:51 2017 +0530

    glusterd: fix brick start race
    
    This commit tries to handle a race where we might end up trying to spawn
    the brick process twice with two different set of ports resulting into
    glusterd portmapper having the same brick entry in two different ports
    which will result into clients to fail connect to bricks because of
    incorrect ports been communicated back by glusterd.
    
    In glusterd_brick_start () checking brickinfo->status flag to identify
    whether a brick has been started by glusterd or not is not sufficient as
    there might be cases where while glusterd restarts
    glusterd_restart_bricks () will be called through glusterd_spawn_daemons
    () in synctask and immediately glusterd_do_volume_quorum_action () with
    server-side-quorum set to on will again try to start the brick and in
    case if the RPC_CLNT_CONNECT event for the same brick  hasn't been processed by
    glusterd by that time, brickinfo->status will still be marked as
    GF_BRICK_STOPPED resulting into a reattempt to start the brick with a different
    port and that would result portmap go for a toss and resulting clients to fetch
    incorrect port.
    
    Fix would be to introduce another enum value called GF_BRICK_STARTING in
    brickinfo->status which will be set when a brick start is attempted by
    glusterd and will be set to started through RPC_CLNT_CONNECT event. For
    brick multiplexing, on attach brick request given the brickinfo->status
    flag is marked to started directly this value will not have any effect.
    Also this patch removes started_here flag as it looks to be redundant as
    brickinfo->status.
    
    Change-Id: I9dda1a9a531b67734a6e8c7619677867b520dcb2
    BUG: 1457981
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17447
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d7105ba1652e548d9ba893e05f3d1fa29e8ee3b1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue May 30 14:27:16 2017 +0530

    core: add more information on dictionary usage
    
    when you take the 'statedump', it shows the output like below
    
    -----
    [dict]
    max-number-of-dict-pairs=13
    total-pairs-used=41613
    total-dict-used=12629
    average-pairs-per-dict=3
    ------
    
    Updates #220
    
    Change-Id: I71a7eda3a3cd23edf4483234f22f983923bbb081
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/4035
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit a9d3d0438ef93beb6ec3f895923db4418c0ab3df
Author: AnkitRaj <anraj@redhat.com>
Date:   Mon May 29 14:12:21 2017 +0530

    dht: for many operation directory/file path is (null) in brick log
    
    There are few operations on mount point which results to
    (null) error for path on brick log. This should be corrected with
    correct path.
    
    Change-Id: I5acf2ead5196594c76a2e526aafbfc128ece433e
    BUG: 1456361
    Signed-off-by: ankitraj <anraj@redhat.com>
    Reviewed-on: https://review.gluster.org/17407
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: ankitraj
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9aa81c15a429dc2817f0149a33b6a9e88ead8110
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 1 14:20:03 2017 +0530

    afr: update errno check in afr_inode_refresh_do
    
    Addresses review comment in https://review.gluster.org/#/c/17413
    
    Change-Id: Ic247729e5e92a5bb0148543764e0b30790444004
    BUG: 1456582
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17436
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 324e81d6fea324d512431a2604086326b8848e9b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu May 25 07:28:07 2017 -0400

    geo-rep: Fix meta data sync on symlink
    
    chmod doesn't support 'no dereference' option.
    It always deference the symlink. But 'chown'
    does support metadata changes on symlink itself,
    which was not taken care while syncing. This
    patch fixes the same.
    
    Change-Id: Ic9985f4e39d15b5a9deb379841bcfb2c263d3e6c
    BUG: 1455559
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17389
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit be28cbc5f8d3a78f6968b0307d001a5c0f0d8b31
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 1 07:05:42 2017 -0400

    extras/hookscripts: non-portable shell syntax
    
    use of "function" is not portable to other shells
    
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Change-Id: I13a0482b387cc3b7a7a57df424e673850603da37
    BUG: 1457812
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17443
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 07fd39479bdd6502f7781894be06eb66aaa8ef10
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 1 06:56:22 2017 -0400

    core: fix spelling errors
    
    fixes for various minor spelling errors and typos
    
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Change-Id: Ic1be36f82e3d822bbdc9559878bd79520fc0fcd5
    BUG: 1457808
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17442
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 244daeb77b159c96fd7ecaac7eb1bea7b4bac23a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue May 30 17:48:41 2017 +0530

    dict: add a simple hash comparision of keys before strcmp for performance
    
    Updates #220
    
    Change-Id: I03b1d2fac2dfcdd21bdf4e4fff19d49425699931
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/6450
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 6b36b162f45c4dfeb5eac21e3d77a27216e089bc
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Tue May 30 18:09:01 2017 +0530

    glusterd: Fix regression wrt add-brick on replica count change
    
    tests/bugs/glusterd/bug-1406411-fail-add-brick-on-replica-count-change.t
    was failing on centos machines with brick multiplexing enabled.
    This is because detaching individual bricks manually from the
    backend like it is done in the regression test framework by
    'kill_brick', fails to send a RPC_CLNT_DISCONNECT to glusterd when
    multiplexing is enabled. This causes the add-brick command to not
    fail when one of the bricks are killed using kill_brick in the
    regression test framework. To fix this, set the brick status to
    GF_BRICK_STOPPED on the glusterd end during portmap signout. This
    commit also sets the brick status in glusterd_brick_stop() function
    so that the brick status is correctly set to 'stopped' even when the
    function is called independently for individual bricks.
    
    Change-Id: I4d6f7b579069d0cfa53cb2b0cff78876e1f31594
    BUG: 1456898
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17422
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit dba55ae364a2772904bb68a6bd0ea87289ee1470
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu May 25 21:43:42 2017 +0530

    glusterfs: Not able to mount running volume after enable brick mux and stopped any volume
    
    Problem: After enabled brick mux if any volume has down and then try ot run mount
             with running volume , mount command is hung.
    
    Solution: After enable brick mux server has shared one data structure server_conf
              for all associated subvolumes.After down any subvolume in some
              ungraceful manner (remove brick directory) posix xlator sends
              GF_EVENT_CHILD_DOWN event to parent xlatros and server notify
              updates the child_up to false in server_conf.When client is trying
              to communicate with server through mount it checks conf->child_up
              and it is FALSE so it throws message "translator are not yet ready".
              From this patch updated structure server_conf to save child_up status
              for xlator wise. Another improtant correction from this patch is
              cleanup threads from server side xlators after stop the volume.
    
    BUG: 1453977
    Change-Id: Ic54da3f01881b7c9429ce92cc569236eb1d43e0d
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17356
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit de92c363c95d16966dbcc9d8763fd4448dd84d13
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon May 29 21:38:14 2017 +0530

    posix: use the correct op_errno
    
    Problem:
    If readdir/fstat was performed on a directory that was removed,
    posix_fd_ctx_get() fails with ENOENT but we incorrectly use the ret
    value (-1 in this case) as op_errno, logging "Operation not permitted"
    messages in the brick logs. Also in case of fstat, the -1 op_errno was
    also propagated to the client via stack unwind, causing the message to
    appear in protocol/client logs as well.
    
    Fix:
    Use the right op_errno in readdir, fstat and writev. Also, if
    posix_fd_ctx_get() failed with ENOENT, convert it into EBADF because
    ENOENT is not a valid error for an fd operation.
    
    Change-Id: Ie43c0789d5040ec73b7cf885d015a183b8c64d70
    BUG: 1456582
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17414
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b9406e210717621bc672a63c1cbd1b0183834056
Author: Sakshi <sabansal@redhat.com>
Date:   Mon Jan 23 12:11:49 2017 +0530

    cluster/dht: Make optimal usage of buffer provided with readdir(p)
    
    dht_readdirp must unwind with list of entries only after
    the entire buffer requested by kernel is filled to avoid
    extra syscalls occuring when returning partially filled
    buffer. Also wind readdir call to next subvol on reaching
    EOD for directory on that subvol to avoid extra network call.
    
    Change-Id: If2e1a2722f813d95457c7542bff25fef56c7a041
    BUG: 1356453
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/12271
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>

commit 57b0a4a374a604079f37a9d9d9fffb09a718c010
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue May 30 15:50:25 2017 +0530

    tier: port value missing on cli parsing
    
    problem: as tier didn't have a port all the values regarding
    the port were removed. but the cli needs a port value to parse and
    print the status.
    
    fix: fake the port value with a zero.
    
    Change-Id: I6491f6c441f7cfddbdaa724fcbe7c30e348aa765
    BUG: 1452006
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/17419
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit feaea7fa541b81a4988b8f394037bfedb5017f4c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon May 29 21:56:12 2017 +0530

    afr: add errno to afr_inode_refresh_done()
    
    Problem:
    When parellel `rm -rf`s were being done from cifs clients, opendir might
    fail on some replicas with ENOENT. DHT ignores partial opendir failures
    in dht_fd_cbk() and winds readdirs on those replicas. Afr inode refresh
    (as a part of readdirp read_txn) sees in its fd context that the state
    of the fds is *not* AFR_FD_OPENED and bails out to
    afr_inode_refresh_done() without doing a refresh. When this happens, the
    errno is set as EIO due to lack of readable subvols, logging split-brain
    messages in the logs.
    
    Fix:
    Introduce an errno argument to afr_inode_refresh_do() to bail out with
    the right error value when inode refresh is not performed.
    
    Change-Id: I075707fbb73fd93a923b77b923a96aac79e847f9
    BUG: 1456582
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17413
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d9978c3b2be3eefc4cd19b61cf99fa20dab77a0d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Apr 18 12:40:36 2017 +0530

    fuse-bridge: cleanup first_lookup()
    
    use syncop_lookup instead of synchronising stack_wind/unwind again.
    
    Updates #175
    
    Change-Id: Iad4a181d8601235a999039979bfb7ec688675520
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/17075
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6b6162f7ff93bccef0e615cb490e881168827e1d
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon May 29 15:21:39 2017 +0530

    perf/ioc: Fix race causing crash when accessing freed page
    
    ioc_inode_wakeup does not lock the ioc_inode for the duration
    of the operation, leaving a window where ioc_prune could find
    a NULL waitq and hence free the page which ioc_inode_wakeup later
    tries to access.
    
    Thanks to Mohit for the analysis.
    
    credit: moagrawa@redhat.com
    
    Change-Id: I54b064857e2694826d0c03b23f8014e3984a3330
    BUG: 1456385
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17410
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ec86167d09bcbb763e31b73fb3d688efaa5444d7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue May 30 10:18:04 2017 +0530

    nl-cache: Remove null check validation for frame->local in lookup cbk
    
    For nameless lookups, nl-cache does not init frame local, so the cbk
    throws up messages like these flooding the logs, especially whenenver
    gfid lookup on '/' is done (i.e. loc.path="/" and loc.gfid=1).
    
    [2017-05-30 04:35:31.628443] E [nl-cache.c:201:nlc_lookup_cbk]
    (-->/usr/lib64/glusterfs/3.8.4/xlator/performance/io-cache.so(+0x3d81)
    [0x7f0883005d81]
    -->/usr/lib64/glusterfs/3.8.4/xlator/performance/quick-read.so(+0x3127)
    [0x7f0882dfb127]
    -->/usr/lib64/glusterfs/3.8.4/xlator/performance/nl-cache.so(+0x4cd3)
    [0x7f08829e0cd3] ) 0-distrep-nl-cache: invalid argument: local [Invalid
    argument]
    
    Fixed it.
    
    Change-Id: I21cb44a9d2a324617e43f46fed83c9a0942d3a0b
    BUG: 1456653
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17417
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f618c7e606caaf8371aea4a02b352c987b3b1a40
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue May 30 13:10:50 2017 +0530

    scripts: prevent a script warning if rfc.sh does not find a backport
    
    When running ./rfc.sh on a branch to post release notes (not a backport
    from master), then the following script warning is displayed:
    
       ./rfc.sh: line 97: [: =: unary operator expected
    
    In case the used variables are not set, they are not handled as empty
    strings. Placing the variables inside "${qoutes}" prevents this warning.
    
    BUG: 1428047
    Change-Id: Ie171d6f66b47401d6ea4e78aa3ed2bd0c6fce9ce
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17418
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 1b1f871ca41b08671ebb327dba464aeb6c82e776
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Apr 25 18:32:45 2017 +0530

    cluster/dht: fix on demand migration files from client
    
        On demand migration of files i.e. migration done by clients
        triggered by a setfattr was broken.
    
        Dependency on defrag led to crash when migration was triggered from
        client.
    
        Note: This functionality is not available for tiered volumes. Migration
        from tier served client will fail with ENOTSUP.
    
        usage (But refer to the steps mentioned below to avoid any issues) :
        setfattr -n "trusted.distribute.migrate-data" -v "1" <filename>
    
        The purpose of fixing the on-demand client migration was to give a
        workaround where the user has lots of empty directories compared to
        files and want to do a remove-brick process.
    
        Here are the steps to trigger file migration for remove-brick process from
        client. (This is highly recommended to follow below steps as is)
    
        Let's say it is a replica volume and user want to remove a replica pair
        named brick1 and brick2. (Make sure healing is completed before you run
        these steps)
    
        Step-1: Start remove-brick process
         - gluster v remove-brick <volname> brick1 brick2 start
        Step-2: Kill the rebalance daemon
         - ps aux | grep glusterfs | grep rebalance\/ | awk '{print $2}' | xargs kill
        Step-3: Do a fresh mount as mentioned here
         -  glusterfs -s ${localhostname} --volfile-id rebalance/$volume-name /tmp/mount/point
        Step-4: Go to one of the bricks (among brick1 and brick2)
         - cd <brick1 path>
        Step-5: Run the following command.
         - find . -not \( -path ./.glusterfs -prune \) -type f -not -perm 01000 -exec bash -c 'setfattr -n "distribute.fix.layout" -v "1" ${mountpoint}/$(dirname '{}')' \; -exec  setfattr -n "trusted.distribute.migrate-data" -v "1" ${mountpoint}/'{}' \;
    
        This command will ignore the linkto files and empty directories. Do a fix-layout of
        the parent directory. And trigger a migration operation on the files.
    
        Step-6: Once this process is completed do "remove-brick force"
         - gluster v remove-brick <volname> brick1 brick2 force
    
        Note: Use the above script only when there are large number of empty directories.
        Since the script does a crawl on the brick side directly and avoids directories those
        are empty, the time spent on fixing layout on those directories are eliminated(even if the script
        does not do fix-layout on empty directories, post remove-brick a fresh layout will be built
        for the directory, hence not affecting application continuity).
    
        Detailing the expectation for hardlink migartion with this patch:
            Hardlink is migrated only for remove-brick process. It is highly essential
        to have a new mount(step-3) for the hardlink migration to happen. Why?:
        setfattr operation is an inode based operation. Since, we are doing setfattr from
        fuse mount here, inode_path will try to build path from the linked dentries to the inode.
        For a file without hardlinks the path construction will be correct. But for hardlinks,
        the inode will have multiple dentries linked.
    
                Without fresh mount, inode_path will always get the most recently linked dentry.
        e.g. if there are three hardlinks named dir1/link1, dir2/link2, dir3/link3, on a client
        where these hardlinks are looked up, inode_path will always return the path dir3/link3
        if dir3/link3 was looked up most recently. Hence, we won't be able to create linkto
        files for all other hardlinks on destination (read gf_defrag_handle_hardlink for more details
        on hardlink migration).
    
                With a fresh mount, the lookup and setfattr become serialized. e.g. link2 won't be
        looked up until link1 is looked up and migrated. Hence, inode_path will always have the correct
        path, in this case link1 dentry is picked up(as this is the most recently looked up inode) and
        the path is built right.
    
        Note: If you run the above script on an existing mount(all entries looked up), hard links may
        not be migrated, but there should not be any other issue. Please raise a bug, if you find any
        issue.
    
        Tests: Manual
    
    
    Change-Id: I9854cdd4955d9e24494f348fb29ba856ea7ac50a
    BUG: 1450975
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17115
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 0a8b2db2d2c3993b25272a65fecad0d3d2866607
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu May 18 14:15:39 2017 +0530

    Tier: removing port allocated for tier
    
    Problem: Tier has a port which it doesn't use.
    
    Fix: Remove the port getting allocated for tier.
    
    Change-Id: If0fe393fc335d9f622a063787e0a3c6db9b7a50c
    BUG: 1452006
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/17328
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 2168729011a0e835a8bdbde9cae7aaddd78a414d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon May 29 16:19:40 2017 +0530

    socket/reconfigure: reconfigure should be done on new dict
    
    In socket reconfigure, reconfigurations are doing with old
    dict values. It should be with new reconfigured dict values
    
    Change-Id: Iac5ad4382fe630806af14c99bb7950a288756a87
    BUG: 1456405
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17412
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ff1a1694112f141991e24284b90f568506aaca41
Author: Michael Scherer <misc@redhat.com>
Date:   Fri Feb 24 22:32:06 2017 +0100

    nfs/netgroups: do not free the same file twice
    
    Coverity warn about a code path where 'file' is freed twice. And reading
    the code, I also found that 'line' shouldn't be freed using GF_FREE
    since it was allocated by getline.
    
    Also call _ng_deinit_parsers() in the success case, preventing leaking
    two 'struct parser' upon multiple calls to ng_file_parse().
    
    Change-Id: I05d71fdbf3b48a25d35e7a56a4c245ceb2dd6ed9
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    [ndevos: add _ng_deinit_parsers() cleanup suggested by Nithya]
    Reviewed-on: https://review.gluster.org/16759
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit de3368a53d9b2d8e035fe070c011a1b78d34559a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 10 02:04:42 2017 -0400

    geo-rep: Log time taken to sync entries
    
    With each batch having the type and count of
    each fop helps to know the kind of I/O.
    Having time taken to sync entry ops, metadata
    ops and data ops gives us good understanding
    into where the more time is being spent.
    This patch does the same.
    
    Change-Id: Ib52a0f9ede905f28a468b68bdf6d23e4b043f3e3
    BUG: 1455179
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17066
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 6908e962f6293d38f0ee65c088247a66f2832e4a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 22 08:47:07 2017 -0400

    features/bitrot: Fix glusterfsd crash
    
    With object versioning being optional, it can
    so happen the bitrot stub context is not always
    set. When it's not found, it's initialized. But
    was not being assigned to use in the local
    function. This was leading for brick crash.
    Fixed the same.
    
    Change-Id: I0dab6435cdfe16a8c7f6a31ffec1a370822597a8
    BUG: 1454317
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17357
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 6544347166054f9b2ed10cdc8fe9025852ea3257
Author: Ji-Hyeon Gim <potatogim@gluesys.com>
Date:   Fri May 5 18:06:25 2017 +0900

    libglusterfs: updates old comment for 'arena_size'
    
    the comment (libglusterfs/src/iobuf.h:88-90) for 'arena_size' field
    in 'struct iobuf_arena' is not valid anymore. According to line 190 in
    __iobuf_arena_alloc() no longer follows that equation.
    
    Change-Id: I68558164b309123cf19093e2da89bc156df294fd
    BUG: 1455831
    Signed-off-by: Ji-Hyeon Gim <potatogim@gluesys.com>
    Reviewed-on: https://review.gluster.org/17393
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit bea02e26a3967a6e679e30fbb77ecfeff1e71f37
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 24 22:30:29 2017 +0530

    features/shard: Handle offset in appending writes
    
    When a file is opened with append, all writes are appended at the end of file
    irrespective of the offset given in the write syscall. This needs to be
    considered in shard size update function and also for choosing which shard to
    write to.
    
    At the moment shard piggybacks on queuing from write-behind
    xlator for ordering of the operations. So if write-behind is disabled and
    two parallel appending-writes come both of which can increase the file size
    beyond shard-size the file will be corrupted.
    
    BUG: 1455301
    Change-Id: I9007e6a39098ab0b5d5386367bd07eb5f89cb09e
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17387
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 3ca5ae2f3bff2371042b607b8e8a218bf316b48c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri May 19 21:04:53 2017 +0530

    glusterfsd: process attach and detach request inside lock
    
    With brick multiplexing, there is a high possibility that attach and
    detach requests might be parallely processed and to avoid a concurrent
    update to the same graph list, a mutex lock is required.
    
    Credits : Rafi (rkavunga@redhat.com) for the RCA of this issue
    
    Change-Id: Ic8e6d1708655c8a143c5a3690968dfa572a32a9c
    BUG: 1454865
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17374
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 23930326e0378edace9c8c41e8ae95931a2f68ba
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Mon May 22 23:25:47 2017 +0530

    libglusterfs : Fix crash in glusterd while peer probing
    
    glusterd crashes when port is being set explcitly to a
    range which is outside greater than short data type range.
    Eg. sysctl net.ipv4.ip_local_reserved_ports="49152-49156"
    In above case glusterd crashes while parsing the port.
    
    With this fix glusterd will be able to handle port range
    between INT_MIN to INT_MAX
    
    Change-Id: I7c75ee67937b0e3384502973d96b1c36c89e0fe1
    BUG: 1454418
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/17359
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 90df37558d488f9a794f62ed74ec6d72879ed895
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 24 03:17:33 2017 -0400

    features/dht: Initialize local hashed_subvol
    
    Self heal directory code path doesn't always
    have local->hashed_subvol populated. Populating
    the same which otherwise would fail the self
    heal.
    
    Change-Id: I03b64709fd7a68e28f9e7438243e817c53c6ef5d
    BUG: 1455104
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17381
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b1fbc695a63801a3a2c62738fd6660388123724a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon May 22 20:23:06 2017 +0530

    glusterd: ignore incorrect uuid validation if uuid_str is empty
    
    If uuid_str is not filled up in dictionary (when glusterd bit is old),
    we shouldn't be additional validation with peer uuid otherwise the
    handshake request will fail.
    
    Refer :
    http://lists.gluster.org/pipermail/gluster-users/2017-May/031187.html
    Credits : pawan@platform.sh
    
    Change-Id: I2c30bf0490c31d1418b31d555e7758696e79409f
    BUG: 1454375
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17358
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 0bcf9143f500dd519c887af2b6948e2d332b3bfd
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 23 11:47:18 2017 -0400

    geo-rep: Make changelog-batch-size configurable
    
    Changelog batch size is set to 727040 bytes which
    is the size of all the changelogs in a single batch.
    It's based on few tests which approximately processes
    5K entries. But it might vary on different machines.
    Making it configurable gives more control on the
    frequency of stime updates. This patch does the same.
    
    Change-Id: I9a5ebb3d92c1327dded0e0a712c43a5a9046c1b0
    BUG: 1454872
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17376
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit a8624b8b13a1f4222e4d3e33fa5836d7b45369bc
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Tue May 23 19:32:24 2017 +0530

    glusterd: Eliminate race in brick compatibility checking stage
    
    In https://review.gluster.org/17307/, while looking for compatible
    bricks for multiplexing, it is checked if the brick pidfile exists
    before checking if the corresponding brick process is running.
    
    However checking if the brick process is running just after
    checking if the pidfile exists isn't enough since there might be
    race conditions where the pidfile has been created but hasn't
    been updated with a pid value yet. This commit solves that by
    making sure that we wait iteratively till the pid value is updated
    as well.
    
    Change-Id: Ib7a158f95566486f7c1f84b6357c9b89e4c797ae
    BUG: 1451248
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17375
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 461888bb63b2409f8245c7766aa799ca22f734e6
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 9 19:26:40 2017 +0200

    fuse: implement "-oauto_unmount"
    
    libfuse has an auto_unmount option which,
    if enabled, ensures that the file system
    is unmounted at FUSE server termination
    by running a separate monitor process
    that performs the unmount when that
    occurs. (This feature would probably
    better be called "robust auto-unmount",
    as FUSE servers usually do try to unmount
    their file systems upon termination,
    it's just this mechanism is not crash
    resilient.)
    
    This change implements that option and
    behavior for glusterfs.
    
    Note that "auto unmount" (robust or not) is
    a leaky abstraction, as the kernel cannot
    guarantee that at the path where the FUSE
    fs is mounted is actually the toplevel mount
    at the time of the umount(2) call, for
    multiple reasons, among others, see:
    
      fuse-devel: "fuse: feasible to distinguish between umount and abort?"
      http://fuse.996288.n3.nabble.com/fuse-feasible-to-distinguish-between-umount-and-abort-tt14358.html
      https://github.com/libfuse/libfuse/issues/122
    
    Updates #153
    
    Change-Id: Ia4432580c9fd2c156d9c73c3a44f4bfd42437599
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17230
    Tested-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 98db583e9b2e7aa8e095a75a6bb5f42b0d65ae79
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 9 19:23:18 2017 +0200

    libglusterfs: extract some functionality to functions
    
    - code in run.c to close all file descriptors,
      except for specified ones is extracted to
    
        int close_fds_except (int *fdv, size_t count);
    
    - tokenizing and editing a string that consists
      of comma-separated tokens (as done eg. in
      mount_param_to_flag() of contrib/fuse/mount.c
      is abstacted into the following API:
    
        char *token_iter_init (char *str, char sep, token_iter_t *tit);
        gf_boolean_t next_token (char **tokenp, token_iter_t *tit);
        void drop_token (char *token, token_iter_t *tit);
    
    Updates #153
    
    Change-Id: I7cb5bda38f680f08882e2a7ef84f9142ffaa54eb
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17229
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 02979e4663ea9e8a925f785f206d1dba02f253c4
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Dec 2 15:04:49 2016 +0530

    geo-rep: Rsync tunables for performance improvements
    
    Flag: --ignore-missing-args
    This Rsync flag reduces sync failures if the source file is
    unlinked but present in --files-from list. This reduces
    Rsync retries in Geo-rep and improves the performance
    
    Flag: --existing
    Rsync in Geo-rep never creates target files. Using RPC Geo-rep creates
    entry in Slave and rsync --inplace used to prevent creating temporary file
    and rename.(To avoid different GFID in Slave). If the entry is missing in
    Slave then Geo-rep Rsync gets Permission denied errors when it tries to
    create file with name as GFID inside .gfid dir.(Geo-rep rsync syncs data
    using GFIDS with aux-gfid-mount)
    
    To disable these flags,
    
        gluster volume geo-replication <session> config \
            rsync-opt-ignore-missing-args false
        gluster volume geo-replication <session> config \
            rsync-opt-existing false
    
    Thanks Kotresh for finding these awesome tunables.
    
    BUG: 1400924
    Change-Id: I6a84fb86a589bf6edc8dfd1086456a84b05a64fc
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/16010
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit acf8cc3a2283d209337ba9f5da6b03396daac359
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Wed May 17 14:35:41 2017 +0530

    cluster/ec: Implement FALLOCATE FOP for EC
    
    FALLOCATE file operations is not implemented in the
    existing EC code. This change set implements it
    for EC.
    
    BUG: 1448293
    Change-Id: Id9ed914db984c327c16878a5b2304a0ea461b623
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/15200
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8dc63c8824fc1a00c873c16e8a16a14fca7c8cca
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Sun May 21 12:31:29 2017 +0530

    glusterd : volume profile command on one of the node crashes glusterd
    
    When volume profile command is issued on one of the node glusterd
    crashes. Its a race condition which may hit when profile command and
    status command is being executed from node A and node B respectively.
    While doing so event GD_OP_STATE_BRICK_OP_SENT/GD_OP_STATE_BRICK_COMMITTED
    is being triggered. As handling of event is not thread safe, hence context
    got modify and glusterd crashes.
    
    With the fix now we are validating the context before using it.
    
    Change-Id: Ic07c3cdc5644677b0e40ff0fac6fcca834158913
    BUG: 1452956
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/17350
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 284cd8851bfe60984d2f11b5c52fe3204ff43b06
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue May 16 19:25:20 2017 +0530

    nl-cache: In case of nameless operations do not cache
    
    Issue:
    In nameless lookup/other fops, parent inode will be NULL, when we try
    to add the cache to the NULL inode, it causes a crash.
    
    Hence handle the scenario of nameless fops, and do not cache/serve
    the nameless fops.
    
    Change-Id: I3b90f882ac89e6aaf3419db89e6f890797f37700
    BUG: 1451588
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17316
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e43b40296956d132c70ffa3aa07b0078733b39d4
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri May 19 11:09:13 2017 +0530

    rda, glusterd: Change the max of rda-cache-limit to INFINITY
    
    Issue:
    The max value of rda-cache-limit is 1GB before this patch.
    When parallel-readdir is enabled, there will be many instances of
    readdir-ahead, hence the rda-cache-limit depends on the number of
    instances. Eg: On a volume with distribute count 4, rda-cache-limit
    when parallel-readdir is enabled, will be 4GB instead of 1GB.
    Consider a followinf sequence of operations:
    - Enable parallel readdir
    - Set rda-cache-limit to lets say 3GB
    - Disable parallel-readdir, this results in one instance of readdir-ahead
      and the rda-cache-limit will be back to 1GB, but the current value is 3GB
      and hence the mount will stop working as 3GB > max 1GB.
    
    Solution:
    To fix this, we can limit the cache to 1GB even when parallel-readdir
    is enabled. But there is no necessity to limit the cache to 1GB, it
    can be increased if the system has enough resources. Hence getting rid
    of the rda-cache-limit max value is more apt. If we just change the
    rda-cache-limit max to INFINITY, we will render older(<3.11) clients
    broken, when the rda-cache-limit is set to > 1GB (as the older clients
    still expect a value < 1GB). To safely change the max value of
    rda-cache-limit to INFINITY, add a check in glusted to verify all
    the clients are > 3.11 if the value exceeds 1GB.
    
    Change-Id: Id0cdda3b053287b659c7bf511b13db2e45b92032
    BUG: 1446516
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17338
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 17784aaa311494e4538c616f02bf95477ae781bc
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri May 19 15:22:12 2017 +0530

    cluster/dht: Fix crash in dht_selfheal_dir_setattr
    
    Use a local variable to store the call cnt used in the
    for loop for the STACK_WIND so as not to access local
    which may be freed by STACK_UNWIND after all fops return.
    
    Change-Id: I24f49b6dbd29a2b706e388e2f6d5196c0f80afc5
    BUG: 1452102
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17343
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 30ed04dc49305f3c0f87ff6010f2fdeb816fbdcc
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu May 18 15:49:27 2017 -0400

    cluster/afr: Remove debug logs in fix_quorum_options()
    
    Change-Id: Id019b0c6425849eece8a9aba7acec9a521dfb10b
    BUG: 1452378
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: https://review.gluster.org/17335
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 13e7b3b354a252ad4065f7b2f0f805c40a3c5d18
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Tue May 16 15:07:21 2017 +0530

    glusterd: Don't spawn new glusterfsds on node reboot with brick-mux
    
    With brick multiplexing enabled, upon a node reboot new bricks were
    not being attached to the first spawned brick process even though
    there wasn't any compatibility issues.
    
    The reason for this is that upon glusterd restart after a node
    reboot, since brick services aren't running, glusterd starts the
    bricks in a "no-wait" mode. So after a brick process is spawned for
    the first brick, there isn't enough time for the corresponding pid
    file to get populated with a value before the compatibilty check is
    made for the next brick.
    
    This commit solves this by iteratively waiting for the pidfile to be
    populated in the brick compatibility comparison stage before checking
    if the brick process is alive.
    
    Change-Id: Ibd1f8e54c63e4bb04162143c9d70f09918a44aa4
    BUG: 1451248
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17307
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2d5da5ae6013d17e5121b1e0bbdf021590533d07
Author: Susant Palai <spalai@redhat.com>
Date:   Tue May 16 07:00:31 2017 +0530

    cluster/dht: initialize throttle option "normal" to same in init and reconfigure
    
    Normal value were different in dht_init and dht_reconfigure.
    Initialization/reconfigure of throttle option are carved out to a separate function
    (dht_configure_throttle) now. Normal value will be "2".
    
    Change-Id: Ie323eae019af41d6bef0a136e3d284dc82bab9a1
    BUG: 1451162
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17303
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 0a50167c0a8f950f5a1c76442b6c9abea466200d
Author: karthik-us <ksubrahm@redhat.com>
Date:   Wed Apr 19 18:04:46 2017 +0530

    cluster/afr: Return the list of node_uuids for the subvolume
    
    Problem:
    AFR was returning the node uuid of the first node for every file if
    the replica set was healthy, which was resulting in only one node
    migrating all the files.
    
    Fix:
    With this patch AFR returns the list of node_uuids to the upper layer,
    so that they can decide on which node to migrate which files, resulting
    in improved performance. Ordering of node uuids will be maintained based
    on the ordering of the bricks. If a brick is down, then the node uuid
    for that will be set to all zeros.
    
    Change-Id: I73ee0f9898ae473584fdf487a2980d7a6db22f31
    BUG: 1366817
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: https://review.gluster.org/17084
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit bcc34ce05c1be76dae42838d55c15d3af5f80e48
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Fri May 12 09:23:47 2017 +0200

    cluster/ec: return all node uuids from all subvolumes
    
    EC was retuning the UUID of the brick with smaller value. This had
    the side effect of not evenly balancing the load between bricks on
    rebalance operations.
    
    This patch modifies the common functions that combine multiple subvolume
    values into a single result to take into account the subvolume order
    and, optionally, other subvolumes that could be damaged.
    
    This makes easier to add future features where brick order is important.
    It also makes possible to easily identify the originating brick of each
    answer, in case some brick will have an special meaning in the future.
    
    Change-Id: Iee0a4da710b41224a6dc8e13fa8dcddb36c73a2f
    BUG: 1366817
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/17297
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit be14d189360d09f8e10e6b75326df6d1db306467
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Tue May 9 12:13:37 2017 +0800

    glusterd: remove useless options from glusterd's volume set table
    
    	These options will cause brick's log complains:
    _log_if_unknown_option] 0-patchy-quota: option 'timeout' is not recognized
    _log_if_unknown_option] 0-patchy-server: option 'ping-timeout' is not recognized
    
    Change-Id: Ida2add13f792736a4e52bfaf38d1169309283a3f
    BUG: 1449008
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17213
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 2592fa0409d5215473b84012c69ac34d0270ef08
Author: hari gowtham <hgowtham@redhat.com>
Date:   Fri Apr 28 00:09:50 2017 +0530

    Tier/cli: detach status xml output
    
    Problem: detach status xml output was broken because
    of the wrong argument. The status_op sent to verify
    whether it is a tier status command was as false.
    
    Fix: the argument being passed was changed from false
    to true.
    
    Change-Id: I8cdd4dd972d6bfbb61c1182cbf4097767f83c7c5
    BUG: 1446362
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/17131
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit b23bd3dbc2c153171d0bb1205e6804afe022a55f
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed May 10 21:26:28 2017 +0530

    cluster/dht: Rebalance on all nodes should migrate files
    
    Problem:
    Rebalance compares the node-uuid of a file against its own
    to and migrates a file only if they match. However, the
    current behaviour in both AFR and EC is to return
    the node-uuid of the first brick in a replica set for all
    files. This means a single node ends up migrating all
    the files if the first brick of every replica set is on the
    same node.
    
    Fix:
    AFR and EC will return all node-uuids for the replica set.
    The rebalance process will divide the files to be migrated
    among all the nodes by hashing the gfid of the file and
    using that value to select a node to perform the migration.
    This patch makes the required DHT and tiering changes.
    
    Some tests in rebal-all-nodes-migrate.t will need to be
    uncommented once the AFR and EC changes are merged.
    
    Change-Id: I5ce41600f5ba0e244ddfd986e2ba8fa23329ff0c
    BUG: 1366817
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17239
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 6f7d55c9d58797beaf8d5393c03a5a545bed8bec
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue May 16 10:26:25 2017 +0530

    cluster/dht: Fix crash in dht rmdir
    
    Using local->call_cnt to check STACK_WINDs can
    cause dht_rmdir_do to be called erroneously if
    dht_rmdir_readdirp_cbk unwinds before we check if
    local->call_cnt is zero in dht_rmdir_opendir_cbk.
    This can cause frame corruptions and crashes.
    
    Thanks to Shyam (srangana@redhat.com) for the
    analysis.
    
    Change-Id: I5362cf78f97f21b3fade0b9e94d492002a8d4a11
    BUG: 1451083
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17305
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 9d70343977aa870004c836a800a5cec11647b409
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon May 1 12:39:56 2017 -0400

    contrib/timerwheel: bad 32-bit, use builtin fls(), fix copyright
    
    It's bad form to remove other people's copyright and license when you
    copy their source for your own use.
    
    Defining BITS_PER_LONG as 64 is incorrect on 32-bit platforms.
    
    The mismatch between the unsigned long of the timer and the int
    param to fls() means on 64-bit platforms that any bits set in the
    high 32-bits of the the timer are lost/ignored.
    
    gf_tw_find_last_bit() is meant to find the last bit in an array of
    longs. It's overkill for gluster's timerwheel  where we only ever pass
    a single long; replacing it with a direct call to fls() which is
    renamed to gf_tw_fls()
    
    The timer routines are slightly modified from the kernel timer
    functions that first appeared circa 2.6.x in .../kernel/timer.c
    AFAICT.
    
    find_last_bit() comes from the (linux) kernel (.../lib/find_bit.c
    in 4.x kernels, .../lib/find_last_bit.c in 3.x kernels) but as noted
    above, it is removed with this patch.
    
    __fls() comes from the linux kernel (.../include/asm-generic/
    bitops/{__fls.h,builtin-__fls.h}
    
    Restoring/updating the copyright and license to the version from
    the 4.x kernel find_bit.c. (timer.c does not have a license, __fls.h
    and builtin-__fls.h do not have a copyright or license, but the whole
    kernel is licensed under GPLv2 anyway.)
    
    Change-Id: I2d2defccf1ccc74f55d99e94212747a36a1dff35
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17146
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 93c850dd2a513fab75408df9634ad3c970a0e859
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed May 10 10:03:08 2017 +0530

    afr: propagate correct errno for fop failures in arbiter
    
    Problem:
    If quorum is not met in fop cbk, arbiter sends an ENOTCONN error to the
    upper xlators. In a VM workload with sharding enabled, this was leading
    to the VM pausing when replace-brick was performed as described in the BZ.
    
    Fix:
    Move the fop cbk arbitration logic to afr_handle_quorum() because in
    normal replica volumes, that is the function that has the quorum and
    errno checks in the fop cbk path before doing a post-op.
    
    Thanks to Pranith for suggesting this approach.
    
    Change-Id: Ie6315db30c5e36326b71b90a01da824109e86796
    BUG: 1449610
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17235
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 64f41b962b643b966e376a10a16671c569bf6299
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri May 12 10:27:28 2017 +0530

    nl-cache: Remove the max limit for nl-cache-limit and nl-cache-timeout
    
    The max limit is better unset when arbitrary. Otherwise in the future
    if max has to be changed, it can break backward compatility.
    
    Change-Id: I4337a3789a2d0d5cc8e2bf687a22536c97608461
    BUG: 1442569
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17261
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ba0fc77947c9e873350b58a0e3e93ab51cc56b37
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon May 15 10:15:20 2017 +0530

    afr: gfid-mismatch-resolution-with-fav-child-policy.t to bad tests
    
    gfid-mismatch-resolution-with-fav-child-policy.t  does a `TEST ls
    $M0/f3` (line #170) to trigger healing of a file in gfid split-brain in
    a rep-3 volume. But the code to trigger name heal of gfid split-brain
    file is not yet there. The test is passing due a lookup/ stat on $M0
    which triggers a background entry self heal (which has the code to heal
    gfid split-brain files) which may or may not complete the heal before
    line 170. If it doesn't, lookup on f3 is failing with EIO.
    
    Add the .t to bad tests until Karthik's patch for CLI based gfid
    split-brain resolution fixes name heal also.
    
    Change-Id: Iba6e9d81db386bc406aff1ecb6a18851f09bf7c0
    BUG: 1450730
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17290
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 710cd0ae8f2dd0495ab483df050720b5c862688d
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Sat May 13 10:06:50 2017 +0530

    socket: Avoid flooding of error message in case of SSL
    
    Problem: socket poller is throwing Input/Output messages during volume operation
    
    Solution: Update the code in socket_connect function before call
              socket_spwan.
    
    BUG: 1450559
    Change-Id: I5f275fe7a4b730b16d7b0a0407e76288b07ceaef
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17280
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit cb6837d03658c1005475d4040fa95504b3fd84d0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun May 14 12:34:15 2017 +0530

    brick mux: Detach brick on posix health check failure
    
    With brick mux enabled, we'd need to detach a particular brick if the
    underlying backend has gone bad. This patch addresses the same.
    
    Change-Id: Icfd469c7407cd2d21d02e4906375ec770afeacc3
    BUG: 1450630
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17287
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 250cdb3005691b809cee5f30846c459408a6fea9
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 20 11:13:55 2017 -0400

    rpc: add more document on programs and actors
    
    Also give hints on where to look for relevant structures.
    
    Fixes #140
    
    Change-Id: If29f67fb6fd39379045fe774559934fb13cbede8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/16925
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 86ad032949cb80b6ba3df9dc8268243529d4eb84
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue May 9 21:05:50 2017 +0530

    glusterfsd: send PARENT_UP on brick attach
    
    With brick multiplexing being enabled, if a brick is instance attached to a
    process then a PARENT_UP event is needed so that it reaches right till
    posix layer and then from posix CHILD_UP event is sent back to all the
    children.
    
    Change-Id: Ic341086adb3bbbde0342af518e1b273dd2f669b9
    BUG: 1447389
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17225
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 269e2ccf45ddc662d8373eb887ae6cef96e2ef37
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed May 3 17:19:57 2017 +0530

    gfapi: fix handling of dot and double dot in path
    
    This patch is to handle "." and ".." in file path. Which means
    this special dentry names will be resolved before sending fops
    on the path.
    
    Change-Id: I5e92f6d1ad1412bf432eb2488e53fb7731edb013
    BUG: 1447266
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17177
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 642f3e290ade6a5a7087816a5cf633083ef9f608
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 9 16:11:52 2017 +0530

    tests/gfapi:Adding testcase to check handling of "." and ".."
    
    Adding a testcase to check the proper handling of "." and ".."
    in gfapi path.
    The patch which fix the issue is https://review.gluster.org/#/c/17177
    
    Change-Id: I5c9cceade30f7d8a3b451b5f34f1cf9815729c4a
    BUG: 1447266
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17216
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit ef61a79f33ca43a9548b9076bb152e6421416f78
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 10 16:26:35 2017 +0530

    extras: Provide group set for gluster-block workloads
    
    For gluster-block workloads I/O is always with o-direct so it doesn't
    benefit by any of the perf xlators so disabling all of them to save
    on memory.
    performance.quick-read=off
    performance.read-ahead=off
    performance.io-cache=off
    performance.stat-prefetch=off
    performance.write-behind=off
    performance.open-behind=off
    performance.readdir-ahead=off
    
    We want the I/O on the file to be with o-direct
    network.remote-dio=enable
    
    Options that are proven to give good performance with
    VM workloads which is very similar to gluster-block
    cluster.eager-lock=enable
    cluster.quorum-type=auto
    cluster.data-self-heal-algorithm=full
    cluster.locking-scheme=granular
    cluster.shd-max-threads=8
    cluster.shd-wait-qlength=10000
    features.shard=on
    
    It is better to turn off things we are not using
    user.cifs=off
    
    It is better to have allow-insecure to be on so that
    ports that are > 1024 in tcmu-runner are allowed.
    server.allow-insecure=on
    
    Change-Id: I9a21c824fa42242f02b57569feedd03d9b6f9439
    BUG: 1450010
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/17254
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 9dc37dd8aa57bea5b86ac4f2a44e31106aeb58ad
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Tue Feb 3 10:48:49 2015 +0530

    glusterd: coverity fix for string overflow
    
    coverity CID: 1124852
    
    Change-Id: Ifb04ad36b0652474007d2768737722231a5c1df0
    BUG: 789278
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: https://review.gluster.org/9539
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 3fc67c062b379562b8b121d5eed042a58cbb0b26
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Dec 16 18:55:28 2016 +0530

    cluster/tier: Don't update cached subvol
    
    tier_readdirp_cbk updates the cached subvol to
    the hot tier if it finds a linkto file.
    However, if no lookup has been sent to the hot tier,
    lower layers will not have updated the inode-ctx causing
    later fops to fail.
    
    Change-Id: Ib8a5e58a6e7fd7750cf6a0ea85da611aa24c7512
    BUG: 1402406
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/16163
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@gmail.com>
    Tested-by: Dan Lambright <dlambrig@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 71cb7f3eb4fb706aab7f83906592942a2ff2e924
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 13 13:02:23 2017 +0100

    nfs/nlm: remove lock request from the list after cancel
    
    Once an NLM client cancels a lock request, it should be removed from the
    list. The list can also be cleaned of unneeded entries once the client
    does not have any outstanding lock/share requests/granted.
    
    Change-Id: I2f2b666b627dcb52cddc6d5b95856e420b2b2e26
    BUG: 1381970
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17188
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 6897ba5c51b29c05b270c447adb1a34cb8e61911
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 20 14:15:31 2017 +0100

    nfs/nlm: free the nlm_client upon RPC_DISCONNECT
    
    When an NLM client disconnects, it should be removed from the list and
    free'd.
    
    Change-Id: Ib427c896bfcdc547a3aee42a652578ffd076e2ad
    BUG: 1381970
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17189
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit cea8b702506ff914deadd056f4b7dd20a3ca7670
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 5 15:21:30 2017 +0530

    event/epoll: Add back socket for polling of events immediately after
                 reading the entire rpc message from the wire
    
    Currently socket is added back for future events after higher layers
    (rpc, xlators etc) have processed the message. If message processing
    involves signficant delay (as in writev replies processed by Erasure
    Coding), performance takes hit. Hence this patch modifies
    transport/socket to add back the socket for polling of events
    immediately after reading the entire rpc message, but before
    notification to higher layers.
    
    credits: Thanks to "Kotresh Hiremath Ravishankar"
             <khiremat@redhat.com> for assitance in fixing a regression in
             bitrot caused by this patch.
    
    Change-Id: I04b6b9d0b51a1cfb86ecac3c3d87a5f388cf5800
    BUG: 1448364
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/15036
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 333474e0d6efe1a2b3a9ecffc9bdff3e49325910
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Tue May 9 20:57:34 2017 +0800

    libglusterfs: fix race condition in client_ctx_set
    
    	follow procedures:
    	1.thread1 client_ctx_get return NULL
    	2.thread 2 client_ctx_set ctx1 ok
    	3.thread1 client_ctx_set ctx2 ok
    
    	thread1 use ctx1, thread2 use ctx2 and ctx1 will leak
    
    Change-Id: I990b02905edd1b3179323ada56888f852d20f538
    BUG: 1449232
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17219
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ccfa06767f1282d9a3783e37555515a63cc62e69
Author: Ji-Hyeon Gim <potatogim@potatogim.net>
Date:   Thu May 11 18:05:21 2017 +0900

    rpc: fix a routine to destory RDMA qp(queue-pair)
    
    Problem: If an error has occured with rdma_create_id() in gf_rdma_connect(),
             process will jump to the 'unlock' label and then call gf_rdma_teardown()
             which call __gf_rdma_teardown().
             Presently, __gf_rdma_teardown() checks InifiniBand QP with peer->cm_id->qp!
             Unfortunately, cm_id is not allocated and will be crushed in this situation :)
    
    Solution: If 'this->private->peer->cm_id' member is null, do not check
              'this->private->peer->cm_id->qp'.
    
    Change-Id: Ie321b8cf175ef4f1bdd9733d73840f03ddff8c3b
    BUG: 1449495
    Signed-off-by: Ji-Hyeon Gim <potatogim@potatogim.net>
    Reviewed-on: https://review.gluster.org/17249
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Ji-Hyeon Gim
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 1a8fa910ccba7aa941f673302c1ddbd7bd818e39
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue May 9 02:31:39 2017 +0530

    afr: send the correct iatt values in fsync cbk
    
    Problem:
    afr unwinds the fsync fop with an iatt buffer from one of its children
    on whom fsync was successful. But that child might not be a valid read
    subvolume for that inode because of pending heals or because it happens
    to be the arbiter brick etc. Thus we end up sending the wrong iatt to
    mdcache which will in turn serve it to the application on a subsequent
    stat call as reported in the BZ.
    
    Fix:
    Pick a child on whom the fsync was successful *and* that is readable as
    indicated in the inode context.
    
    Change-Id: Ie8647289219cebe02dde4727e19a729b3353ebcf
    BUG: 1449329
    RCA'ed-by: Miklós Fokin <miklos.fokin@appeartv.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17227
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 74383e3ec6f8244b3de9bf14016452498c1ddcf0
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Mon Apr 24 22:00:17 2017 +0530

    glusterd: Make reset-brick work correctly if brick-mux is on
    
    Reset brick currently kills of the corresponding brick process.
    However, with brick multiplexing enabled, stopping the brick
    process would render all bricks attached to it unavailable. To
    handle this correctly, we need to make sure that the brick process
    is terminated only if brick-multiplexing is disabled. Otherwise,
    we should send the GLUSTERD_BRICK_TERMINATE rpc to the respective
    brick process to detach the brick that is to be reset.
    
    Change-Id: I69002d66ffe6ec36ef48af09b66c522c6d35ac58
    BUG: 1446172
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17128
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit d5865881de5653a0e810093a9867ab3962d00f67
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 10 15:44:33 2017 +0530

    tests/lock_revocation: mark as bad
    
    The test is failing in master. see gluster-devel for more details.
    
    Change-Id: I7a589ad2c54bd55d62f4e66fdf8037c19fc123ea
    BUG: 1448364
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/17234
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ed27add635263eafb581e5dd1599478d82f0f28a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon May 8 21:10:50 2017 +0530

    features/changelog: Add xattr as special type in changelog entry
    
    When both SETATTR and SETXATTR fops are happening on gfid within the
    rollover time then, SETXATTR were not logged.
    In Which case we will miss the xattr fop in slave.
    
    This patch will be fix the same
    
    Change-Id: Ia75538ad1fd2797dbcf90d20dfa89f756009243d
    BUG: 1448914
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17205
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 27b04b6c487e789074eb10c93be0f7d4f58fa945
Author: Michael Scherer <misc@redhat.com>
Date:   Fri May 5 16:01:36 2017 +0200

    Fix 'flush' type, coverity warning
    
    As getchar returna a int, (which is 4 bytes on most
    common platforms, and at least 2 bytes), and char being often
    1 byte, the conversion would lose information, hence
    the warning.
    
    Change-Id: I5b0b39c636ff49ef5c15d51a7f798e21635eca06
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/17193
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 9df83b504a01e86d3b73af6c40df0c94cd2cd97a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri May 5 14:30:49 2017 +0530

    features/shard: Set size in inode ctx before size update for truncate too
    
    Change-Id: I7e984bb0f50c7d42764c0648e697d94d6c768dc7
    BUG: 1448299
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17184
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 9bfb74a39954a7e63bfd762c816efc7e64b9df65
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 13 14:46:17 2017 +0100

    nfs/nlm: log the caller_name if nlm_client_t can be found
    
    In order to help tracking possible misbehaving clients down, log the
    'caller_name' (hostname of the NFS client) that does not have a matching
    nlm_client_t structure.
    
    Change-Id: Ib514a78d1809719a3d0274acc31ee632727d746d
    BUG: 1381970
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17186
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit e997d752ba08f80b1b00d2c0035874befafe5200
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 13 14:02:45 2017 +0100

    nfs/nlm: ignore notify when there is no matching rpc request
    
    In certain (unclear) occasions it seems to happen that there are
    notifications sent to the Gluster/NFS NLM service, but no call-state can
    be found. Instead of segfaulting, log an error but keep on running.
    
    Change-Id: I0f186e56e46a86ca40314d230c1cc7719c61f0b5
    BUG: 1381970
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17185
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d8ee72b9227fecf6e8bc89ed25e059acb240fdb8
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Mon May 8 12:55:49 2017 -0400

    build: add site.h as a place to put environment-specific defines
    
    Most people consume Gluster in one of two ways:
    
     * From packages provided by their OS/distribution vendor
    
     * By building themselves from source
    
    For the first group it doesn't matter whether configuration is done in
    a configure script, via command-line options to that configure script,
    or in a header file.  All of these end up as edits to some file under
    the packager's control, which is then run through their tools and
    process (e.g. rpmbuild) to create the packages that users will
    install.
    
    For the second group, convenience matters.  Such users might not even
    have a script wrapped around the configure process, and editing one
    line in a header file is a lot easier than editing several in the
    configure script.  This also prevents a messy profusion of configure
    options, dozens of which might need to be added to support a single
    such user's preferences.  This comes back around as greater simplicity
    for packagers as well.
    
    This patch defines site.h as the header file for options and
    parameters that someone building the code for themselves might want to
    tweak.  The project can ship one version to reflect the developers'
    guess at the best defaults for most users, and sophisticated users
    with unusual needs can override many options at once just by
    maintaining their own version of that file.  Everybody wins.  Further
    guidelines for how to determine whether an option should go in
    configure.ac or site.h are explained within site.h itself.
    
    Fixes #201
    
    Change-Id: I5b8fb518d42450737423c4c1f43ebeb3130b4ff6
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17206
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 57bfff95c87396207e1c7de64f2db1f0730ad84d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue May 9 14:02:41 2017 +0530

    afr: fixes to quorum-type in afr_priv_dump()
    
    Include the 'none' option as well in the output. This fixes the bug in
    commit 335555d256d444f4952ce239168f72b393370f01.
    Also added a test-case.
    
    This is a
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    
    Change-Id: I479a14ae69ecae5a03e85e73ed50c19b483df603
    BUG: 1448804
    Reviewed-on: https://review.gluster.org/17215
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e71119e942eb016ba5a11c3f986715f16da10b82
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Nov 10 10:56:26 2016 +0530

    mount/fuse: Handle racing notify on more than one graph properly
    
    Make sure that we always use latest graph as a candidate for
    active-subvol.
    
    Change-Id: Ie37c818366f28ba6b1570d65a9eb17697d38a6c5
    BUG: 1448364
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/17200
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 284451110add7b95c6ddaa2d2aa21fc7528e4f2b
Author: AnkitRaj <anraj@redhat.com>
Date:   Mon May 8 17:52:33 2017 +0530

    dht:Spacing issue in fix-layout o/p
    
    There is a spacing issue in the status output of
    the rebalance fix-layout operations. If the local
    host name is big then we will have spacing issue.
    
    Change-Id: I2fcc4fd382723fb7e93cb4d4dad03dae682cc1a8
    BUG: 1437748
    Signed-off-by: AnkitRaj <anraj@redhat.com>
    Reviewed-on: https://review.gluster.org/17203
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: ankitraj
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 4b03314e14c0395cc6c51692fd563f92f5b6f282
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Apr 25 08:28:25 2017 -0400

    libglusterfs: include sys/time.h avoid compiling error on MacOSX
    
    Change-Id: I3d30bacc3d5d085220dd85a3919207deef8bd1dd
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17114
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 0f552c509f5a12bda6b7b160a82a9322986655c6
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Thu May 4 09:01:37 2017 +0800

    libglusterfs/graph: fix potential endless loop in options validate work
    
    Change-Id: Icb71ded6051afe44e07480e0499d2a39f05fac71
    BUG: 1447826
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17171
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 2ff39c5cbea6fbda0d7a442f55e6dc2a72efb171
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Apr 11 15:58:47 2014 +0530

    performance/read-ahead: prevent stale data being returned to application.
    
    Assume that fd is shared by two application threads/processes.
    
    T0 read is triggered from app-thread t1 and read call passes through
       write-behind.
    T1 app-thread t2 issues a write. The page on which read from t1 is
       waiting is marked stale
    T2 write-behind caches write and indicates to application as write
       complete.
    T3 app-thread t2 issues read to same region. Since, there is already a
       page for that region (created as part of read at T0), this read
       request waits on that page to be filled (though it is stale, which
       is a bug).
    T4 read (triggered at T0) completes from brick (with write still
       pending). Now both read requests from t1 and t2 are served this data
       (though data is stale from app-thread t2's perspective - which is a
       bug)
    T5 write is flushed to brick by write-behind.
    
    Fix is to not to serve data from a stale page, but instead initiate a
    fresh read to back-end.
    
    Change-Id: Id6af733464fa41bb4e81fd29c7451c73d06453fb
    BUG: 1414242
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/7447
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit af226d250bcced782d19412bd7de1ca32834c8eb
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Apr 5 09:52:39 2017 +0200

    cluster/ec: fix incorrect answer check in seek fop
    
    A bad check in the answer of a seek request caused a segmentation
    fault when seek reported an error.
    
    Change-Id: Ifb25ae8bf7cc4019d46171c431f7b09b376960e8
    BUG: 1439068
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/16998
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 4f4ad03e0c4739d3fe1b0640ab8b4e1ffc985374
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue May 9 07:05:18 2017 +0530

    posix: Send SIGKILL in 2nd attempt
    
    Commit 21c7f7ba changed the signal from SIGKILL to SIGTERM for the 2nd
    attempt to terminate the brick process if SIGTERM fails. This patch
    fixes this problem.
    
    Change-Id: I856df607b7109a215f2a2a4827ba3ea42d8a9729
    BUG: 1444596
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17208
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 21c7f7baccfaf644805e63682e5a7d2a9864a1e6
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon May 8 19:29:22 2017 +0530

    glusterd: socketfile & pidfile related fixes for brick multiplexing feature
    
    Problem: While brick-muliplexing is on after restarting glusterd, CLI is
             not showing pid of all brick processes in all volumes.
    
    Solution: While brick-mux is on all local brick process communicated through one
              UNIX socket but as per current code (glusterd_brick_start) it is trying
              to communicate with separate UNIX socket for each volume which is populated
              based on brick-name and vol-name.Because of multiplexing design only one
              UNIX socket is opened so it is throwing poller error and not able to
              fetch correct status of brick process through cli process.
              To resolve the problem write a new function glusterd_set_socket_filepath_for_mux
              that will call by glusterd_brick_start to validate about the existence of socketpath.
              To avoid the continuous EPOLLERR erros in  logs update socket_connect code.
    
    Test:     To reproduce the issue followed below steps
              1) Create two distributed volumes(dist1 and dist2)
              2) Set cluster.brick-multiplex is on
              3) kill glusterd
              4) run command gluster v status
              After apply the patch it shows correct pid for all volumes
    
    BUG: 1444596
    Change-Id: I5d10af69dea0d0ca19511f43870f34295a54a4d2
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/17101
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 18e07cf01f975c80152e5469fb4e4274f08dc636
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Fri Apr 28 05:46:50 2017 -0400

    cli: fix build error with --disable-xml-output
    
    ./configure --disable-xml-output --disable-georeplication
    make
    
    Making all in src
      CC       cli.o
    In file included from cli.c:42:0:
    cli.h:440:24: error: unknown type name ‘xmlTextWriterPtr’
     cli_xml_output_common (xmlTextWriterPtr writer, int op_ret, int op_errno,
                            ^
    cli.h:443:26: error: unknown type name ‘xmlTextWriterPtr’
     cli_xml_snapshot_delete (xmlTextWriterPtr writer, xmlDocPtr doc, dict_t *dict,
                              ^
    cli.h:443:51: error: unknown type name ‘xmlDocPtr’
     cli_xml_snapshot_delete (xmlTextWriterPtr writer, xmlDocPtr doc, dict_t *dict,
                                                       ^
    make[1]: *** [cli.o] Error 1
    make: *** [all-recursive] Error 1
    
    Change-Id: I36c2dfc11f89d774b62dfe6f50b156826bed5b66
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17136
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 0d8923d6d70af702730a43a536a5d0b25b4061dc
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Apr 25 17:01:09 2017 +0200

    libglusterfs: stop special casing "cache-size" in size_t validation
    
    The original situation was as follows:
    
    The function that validates xlator options indicating a size,
    xlator_option_validate_sizet(), handles the case when the name
    of the option is "cache-size" in a special way.
    
    - Xlator options (things of type volume_option_t) has a
      min and max attribute of type double.
    - An xlator option is endowed with a gluster specific type (not
      C type). An instance of an xlator option goes through a validation
      process by a type specific validator function (which are collected
      in option.c).
    - Validators of numeric types - size being one of them - make use the
      min and max attributes to perform a range check, except in one case:
      if an option is defined with min = max = 0, then this option will be
      exempt of range checking. (Note: the volume_option_t definition
      features the following comments along the min, max fields:
    
       double                  min;  /* 0 means no range */
       double                  max;  /* 0 means no range */
    
      which is slightly misleading as it lets one to conclude that
      zeroing min or max buys exemption from low or high boundary check,
      which is not true -- only *both* being zero buys exemption.)
    - Besides this, the validator for options of size type,
      xlator_option_validate_sizet() special cases options
      named "cache-size" so that only min is enforced. (The only consequence
      of a value exceeding max is that glusterd logs a warning about it, but
      the cli user who makes such a setting gets no feedback on it.)
    - This was introduced because a hard coded limit is not useful for
      io-cache and quick-read. They rather use a runtime calculated
      upper limit. (See changes
      I7dd4d8c53051b89a293696abf1ee8dc237e39a20
      I9c744b5ace10604d5a814e6218ca0d83c796db80
      about the last two points.)
    - As an unintended consequence, the upper limit check of
      cache-size of write-behind, for which a conventional hard coded limit
      is specified, is defeated.
    
    What we do about it:
    
    - Remove the special casing clause for cache-size in
      xlator_option_validate_sizet. Thus the general range
      check policy (as described above) will apply to
      cache-size too.
    - To implement a lower bound only check by the validator
      for cache-size of io-cache and quick-read, change the
      max attribute of these options to INFINITY.
    
    The only behavioral difference is the omission of the warnings
    about cache-size of io-cache and quick-read exceeding the former max
    values. (They were rather heuristic anyway.)
    
    BUG: 1445609
    Change-Id: I0bd8bd391fa7d926f76e214a2178833fe4673b4a
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17125
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 52c28c0c04722a9ffaa7c39c49ffebdf0a5c75e1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 13 16:05:02 2017 +0100

    nfs/nlm: unref rpc-client after nlm4svc_send_granted()
    
    nlm4svc_send_granted() uses the rpc_clnt by getting it from the
    call-state structure. It is safer to unref the rpc_clnt after the
    function is done with it.
    
    Change-Id: I7cb7c4297801463d21259c58b50d7df7c57aec5e
    BUG: 1381970
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17187
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 68b4db2ac37af3283580b74eef5d405c9370b0c0
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Fri Apr 28 06:12:56 2017 +0800

    debug/error-gen: Don't need to convert error string to int in every fop
    
    Every fop in xlator error-gen will call function error_gen,
    which will call function conv_error to convert pvt->error_no to int.
    But actually the function could only be called in init and reconfigure
    
    Change-Id: I96c9780574f369fc58eed10fea9d50c4cd7d4e8a
    BUG: 1446412
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17132
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 5b8e9261f1e8aab1a3475578d56d54037459a5e6
Author: Michael Scherer <misc@redhat.com>
Date:   Fri May 5 17:20:14 2017 +0200

    Remove uneeded gotos, as it jump to the next line
    
    Found by coverity
    Signed-off-by: Michael Scherer <misc@redhat.com>
    
    Change-Id: I1fef09a427d18bbeb9af0bf4f5c82c77aa3c0d3d
    BUG: 789278
    Reviewed-on: https://review.gluster.org/17195
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 3d35e21ffb15713237116d85711e9cd1dda1688a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed May 3 12:17:30 2017 +0530

    glusterd: cleanup pidfile on pmap signout
    
    This patch ensures
    1. brick pidfile is cleaned up on pmap signout
    2. pmap signout evemt is sent for all the bricks when a brick process
    shuts down.
    
    Change-Id: I7606a60775b484651d4b9743b6037b40323931a2
    BUG: 1444596
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17168
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 335555d256d444f4952ce239168f72b393370f01
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri May 5 22:19:36 2017 +0530

    afr: include quorum type and count when dumping afr priv
    
    Dump the client quorum type ('auto' or 'fixed'). If it is 'fixed', also dump
    the quorum-count. This information will be available in the client
    statedump and in
    /<fuse_mount>/.meta/graphs/active/testvol-replicate-X/private.
    
    Change-Id: Idbd6e2acbd622d4e6cfabf511e649a6da0e42384
    BUG: 1448804
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/17196
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2ae4b4058691b324535d802f4e6d24cce89a10e5
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Wed Mar 22 15:02:12 2017 +0530

    Fixes quota aux mount failure
    
    The aux mount is created on the first limit/remove_limit/list command
    and it remains until volume is stopped / deleted / (quota is disabled)
    , where we do a lazy unmount. If the process is uncleanly terminated,
    then the mount entry remains and we get (Transport disconnected) error
    on subsequent attempts to run quota list/limit-usage/remove commands.
    
    Second issue, There is also a risk of inadvertent rm -rf on the
    /var/run/gluster causing data loss for the user. Ideally, /var/run is
    a temp path for application use and should not cause any data loss to
    persistent storage.
    
    Solution:
    1) unmount the aux mount after each use.
    2) clean stale mount before mounting, if any.
    
    One caveat with doing mount/unmount on each command is that we cannot
    use same mount point for both list and limit commands.
    The reason for this is that list command needs mount to be accessible
    in cli after response from glusterd, So it could be unmounted by a
    limit command if executed in parallel (had we used same mount point)
    Hence we use separate mount points for list and limit commands.
    
    Change-Id: I4f9e39da2ac2b65941399bffb6440db8a6ba59d0
    BUG: 1433906
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Reviewed-on: https://review.gluster.org/16938
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 21115ae8b80c1ae0afe8427423ca5ecde40f0027
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu May 4 20:56:43 2017 +0530

    snapview-server : Refresh the snapshot list during each reconnect
    
    Currently we are refreshing the snapshot list either when there is
    a request from glusterd or the very first initialization. But if
    anything changed after when glusterd is down then there is no
    mechanism to refresh the snashot dentries.
    
    This patch will refresh snapshot list during each reconnect
    
    Change-Id: I3ed655572d777f60d57dd479d190f75553591267
    BUG: 1448150
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/17178
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 67598f538efb24a9e5ac561b294a05e707e15761
Author: N Balachandran <nbalacha@redhat.com>
Date:   Sat May 6 20:01:16 2017 +0530

    cluster/dht: Fix ret check
    
    Fixed an incorrect return code check in the rebalance
    code.
    
    Change-Id: I60804ff121cec7a2f0419e2ee70dd22ea7533c0c
    BUG: 1448640
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17197
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e0aaaccefdfda345b981b86dea23b2ffa52e9377
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Sun May 7 17:29:26 2017 +0800

    rpc: use GF_ATOMIC_INC to generate rpc_clnt's callid
    
    Change-Id: I57ad970411db1ccd3d2c56c504c7da9cc221051f
    BUG: 1448692
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17198
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 2502162502009d4be75e67e49d71f3f38aaa7595
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu May 4 15:49:59 2017 +0530

    Tier: Watermark check for hi and low value being equal
    
    Problem: Both low and hi watermark can be set to same value
    as the check missed the case for being equal.
    
    Fix: Add the check to both the hi and low values being equal
    along with the low value being higher than hi value.
    
    Change-Id: Ia235163aeefdcb2a059e2e58a5cfd8fb7f1a4c64
    BUG: 1447960
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/17175
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1538b7296cc0a3150f33190f97dc99c9ca126322
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 16:40:12 2017 +0100

    Fix ressources leak on error path
    
    Coverty found a path where blk_fop is not freed, thus
    leaking memory. The main cause is because we are using the
    wrong variable for errors.
    
    I do not think this is leaking anything in
    practice, since the error condition seems quite rare, but
    fixing this should remove around 15 coverty warning.
    
    Change-Id: Ida0ea59f501f0a21bd1d8119aa1a299ce655add8
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16715
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit fe83a4ae84dd4345d6e958219d5a1dc59ecb039d
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Fri Mar 31 00:42:46 2017 +0800

    coreutils: use coreutils instead of duplicate code
    
    Change-Id: I0e442331d2bbb22ec18c37af87ab2a8852737c43
    BUG: 1448265
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/16975
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit fa10c8a3528b95dc575bfedd30bcd68cc2dff25b
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed May 3 18:39:14 2017 +0530

    gfapi: Fix few severe coverity issues
    
    From https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-05-03-6484558c/html/
    fixes coverity#189, 248, 250, 488, 546
    
    Change-Id: I7c4aa5bf6c367344602748dfd736de27f341cca2
    BUG: 789278
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: https://review.gluster.org/17161
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit de80a9153e3b681d8b83aa6164c94e2829b9cf49
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu May 4 12:15:09 2017 +0530

    rpc: Remove accidental IPV6 changes
    
    They snuck in with the HALO patch (07cc8679c)
    
    Change-Id: I8ced6cbb0b49554fc9d348c453d4d5da00f981f6
    BUG: 1447953
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: https://review.gluster.org/17174
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 93ecfcddbfc6bdc77a720f55dbd51fc256961d68
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu May 4 12:26:26 2017 +0200

    build: 'make cscope' requires generated .c and .h XDR files
    
    When running 'make cscope' on a clean configured tree (before building
    anything), it fails because of missing files unders rpc/xdr/src/. These
    files are symlinked from generated files in the rpc/xdr/gen/ directory.
    In order to create the symlinks for 'make cscope', a target needs to
    specify how these symlinks are created.
    
    Change-Id: I473c90e10d915ee438425cf0f806c0531b9f582a
    BUG: 1447966
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17176
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 8375b3d70d5c6268c6770b42a18b2e1bc09e411e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed May 3 16:42:22 2017 +0530

    glusterd: disallow rebalance & remove-brick on a sharded volume
    
    Change-Id: Idfbdbc61ca18054fdbf7556f74e195a63cd8a554
    BUG: 1447630
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17160
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b3229ed1071b8e45b0717abef0adf1c17c9df81c
Author: Michael Scherer <misc@redhat.com>
Date:   Wed May 3 16:54:46 2017 +0200

    Remove double free
    
    Since there is already GF_FREE (value) near the out label, this
    one is uneeded. Found by coverity.
    
    Change-Id: Ib4a4e1a6af186e14fc75e7578c79beb58de053ec
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/17165
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 9f930646eeed12a243d083c91acb59fbe7004074
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Wed May 3 18:33:40 2017 +0800

    fd: We should use dict_set_uint64 to store fd->pid
    
    Change-Id: I136372b9929d3ecf243649b6945571a67bfd80eb
    BUG: 1447828
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17172
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit d7cb404d9f75253b86b7a9263cab56ec853c5c94
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 22:47:02 2017 +0100

    Refactor the code for posix_handle_pair
    
    It was no longer compiling on Darwin, and triggered a cppcheck
    error:
    
      [xlators/storage/posix/src/posix-helpers.c:1097]: (error) Invalid number of character '{' when these macros are defined: 'GF_DARWIN_HOST_OS'.
    
    Change-Id: I986609cc6cfc13ddea0ed35d7776736171f40a41
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16729
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 7c98143c7928f4ec936c90f0125b2a2aaf8f5174
Author: Michael Scherer <misc@redhat.com>
Date:   Thu Feb 23 22:57:42 2017 +0100

    mgmt: Fix null pointer deref
    
    since "this" can be NULL, we should skip this
    validation, there is another call to GF_VALIDATE_OR_GOTO
    in the following lines. Found by cppcheck.
    
    Change-Id: I329f50b986a9eaf3315e09f851080ab41bea57c0
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16742
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5c68937ef943a5ed8179cb19fef833f2be790588
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 17:19:33 2017 +0100

    Fix wrong operators
    
    Coverty rightfully note that if we verify that
    A =! C or A != B, it will always be true.
    
    In one case, that prevent healing from continuing. In the other,
    that trigger useless logs. Fixing this bug also show that
    ENOSPC shouldn't abort the rebalance operation, as seen during
    the review of the first patch on
    https://review.gluster.org/#/c/16676/1/xlators/cluster/dht/src/dht-rebalance.c
    
    Change-Id: I93c4df43b880b211da202a7e49cef6b1ce7ab68f
    BUG: 1424817
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16676
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 7178c299d727e98370835ba3dde41f91f087e724
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Wed May 3 17:51:57 2017 +0800

    server: fd should be refed before put into fdtable
    
    	If a network error occurs after we put a fd to fdtable,
    fds in fdtable will be cleaned up by do_fd_cleanup which will
    unref the fd and release the fd if the fd hasn't be refed by user.
    
    Change-Id: Idbad0fafd005c59398518190845fe137cbf95c60
    BUG: 1447609
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17158
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 4f7ef3020edcc75cdeb22d8da8a1484f9db77ac9
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed May 3 10:51:16 2017 +0530

    rpc: fix transport add/remove race on port probing
    
    Problem:
    Spurious __gf_free() assertion failures seen all over the place with
    header->magic being overwritten when running port probing tests with
    'nmap'
    
    Solution:
    Fix sequence of:
    1. add accept()ed socket connection fd to epoll set
    2. add newly created rpc_transport_t object in RPCSVC service list
    
    Correct sequence is #2 followed by #1.
    
    Reason:
    Adding new fd returned by accept() to epoll set causes an epoll_wait()
    to return immediately with a POLLIN event. This races ahead to a readv()
    which returms with errno:104 (Connection reset by peer) during port
    probing using 'nmap'. The error is then handled by POLLERR code to
    remove the new transport object from RPCSVC service list and later
    unref and destroy the rpc transport object.
    socket_server_event_handler() then catches up with registering the
    unref'd/destroyed rpc transport object. This is later manifest as
    assertion failures in __gf_free() with the header->magic field botched
    due to invalid address references.
    All this does not result in a Segmentation Fault since the address
    space continues to be mapped into the process and pages still being
    referenced elsewhere.
    
    As a further note:
    This race happens only in accept() codepath. Only in this codepath,
    the notify will be referring to two transports:
    1, listener transport and
    2. newly accepted transport
    All other notify refer to only one transport i.e., the transport/socket
    on which the event is received. Since epoll is ONE_SHOT another event won't
    arrive on the same socket till the current event is processed. However, in
    the accept() codepath, the current event - ACCEPT - and the new event -
    POLLIN/POLLER - arrive on two different sockets:
    1. ACCEPT on listener socket and
    2. POLLIN/POLLERR on newly registered socket.
    Also, note that these two events are handled different thread contexts.
    
    Cleanup:
    Critical section in socket_server_event_handler() has been removed.
    Instead, an additional ref on new_trans has been used to avoid ref/unref
    race when notifying RPCSVC.
    
    Change-Id: I4417924bc9e6277d24bd1a1c5bcb7445bcb226a3
    BUG: 1438966
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/17139
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Oleksandr Natalenko <oleksandr@natalenko.name>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 6484558c7502e5afe1c96081dbe329ca5d9cb7e2
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Mar 16 21:37:22 2016 +0530

    SELinux : implementation of SELinux translator
    
    The patch implement a part of SELinux translator to support setting
    SELinux contexts on files in a glusterfs volume.
    
    URL: https://github.com/gluster/glusterfs-specs/blob/master/accepted/SELinux-client-support.md
    
    Change-Id: Id8916bd8e064ccf74ba86225ead95f86dc5a1a25
    BUG: 1318100
    Fixes : #55
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/13762
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333@gmail.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 41000cd0b57a81c4ace4a1d3da0fcc352a11f146
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Apr 21 16:30:20 2017 +0530

    gfapi/handleops: Introducing glfs_xreaddirplus_r() fop for handleops
    
    Its known that readdirplus operation fetches stat as well for each of the
    dirents. But often applications may need extra information, like for eg.,
    NFS-Ganesha which operates on handles needs handles for each of those
    dirents returned. So this would require extra calls to the backend, in this
    case LOOKUP (which is very expensive operation) resulting in very low
    readdir performance.
    
    To address that introducing this new API using which applications can
    make request for any extra information to be returned as part of
    readdirplus response.
    
    Currently this new api returns stat and handles as demanded by application.
    The synopsis of the API is noted in glfs.h.
    
    @todo:
    * Enhance test script using this new API
    
    Below were the perf results on single brick volume with and without
    these changes -
    
    Dataset used -
    10*100 directories and each directory containing 100 empty files.
    
    I used NFS-Ganesha application to test these changes -
    >for i in {1..5}; do systemctl restart nfs-ganesha; sleep 10; mount -t nfs -o vers=4 localhost:/brick_vol /mnt; cd /mnt; echo "ITERATION$i"; date; find . > tmp-nfs.log; date; cd /; umount /mnt; sleep 2; done;
    
    Without these changes -
    ITERATION1
    Mon Mar 20 17:22:26 IST 2017
    Mon Mar 20 17:23:18 IST 2017
    ITERATION2
    Mon Mar 20 17:23:39 IST 2017
    Mon Mar 20 17:24:28 IST 2017
    ITERATION3
    Mon Mar 20 17:24:49 IST 2017
    Mon Mar 20 17:25:36 IST 2017
    ITERATION4
    Mon Mar 20 17:30:57 IST 2017
    Mon Mar 20 17:31:37 IST 2017
    ITERATION5
    Mon Mar 20 17:31:57 IST 2017
    Mon Mar 20 17:32:40 IST 2017
    [root@dhcp35-197 /]#
    
    On an average ~46.2 sec
    
    With these changes applied -
    ITERATION1
    Mon Mar 20 17:35:03 IST 2017
    Mon Mar 20 17:35:15 IST 2017
    ITERATION2
    Mon Mar 20 17:35:36 IST 2017
    Mon Mar 20 17:35:46 IST 2017
    ITERATION3
    Mon Mar 20 17:36:06 IST 2017
    Mon Mar 20 17:36:17 IST 2017
    ITERATION4
    Mon Mar 20 17:41:38 IST 2017
    Mon Mar 20 17:41:49 IST 2017
    ITERATION5
    Mon Mar 20 17:42:10 IST 2017
    Mon Mar 20 17:42:20 IST 2017
    
    On an average ~10.8 sec
    
    Updates #174
    BUG: 1442950
    Change-Id: I0f74f74dc62085ca4c4a23c38e3edc84bd850876
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: https://review.gluster.org/15663
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 316e3300cfaa646b7fa45fcc7f57b81c7bb15a0e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue May 2 11:46:11 2017 +0530

    glusterd: skip nfs svc reconfigure if nfs xlator is not installed
    
    With 83abcba, nfs svc is not (re)started or stopped if NFS so file is
    not installed. However the same check was missing in nfs svc reconfigure
    which was causing all volume set command to fail.
    
    Change-Id: Ie87b5dba44ac59e890cbd60f85944f8e685ad52b
    BUG: 1326219
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17149
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d7e9dcfad228f385ad64526b1f06b55e98b06964
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Apr 21 18:36:58 2017 +0200

    nl-cache: free nlc_conf_t in fini()
    
    The (xlator_t*)->private structure in negative-lookup-cache is allocated
    in the init() function of the xlator, but never free'd. Valgrind
    detected this as:
    
        656 bytes in 1 blocks are definitely lost in loss record X of Y
           at 0x..+ calloc (/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc/vg_replace_malloc.c:711)
           by 0x.. __gf_calloc (/usr/src/debug/glusterfs-3.11dev/libglusterfs/src/mem-pool.c:117)
           by 0x.. init (/usr/src/debug/glusterfs-3.11dev/xlators/performance/nl-cache/src/nl-cache.c:669)
           by 0x.. __xlator_init (/usr/src/debug/glusterfs-3.11dev/libglusterfs/src/xlator.c:472)
           by 0x.. xlator_init (/usr/src/debug/glusterfs-3.11dev/libglusterfs/src/xlator.c:498)
           by 0x.. glusterfs_graph_init (/usr/src/debug/glusterfs-3.11dev/libglusterfs/src/graph.c:321)
           by 0x.. glusterfs_graph_activate (/usr/src/debug/glusterfs-3.11dev/libglusterfs/src/graph.c:693)
           by 0x.. glfs_process_volfp (/usr/src/debug/glusterfs-3.11dev/api/src/glfs-mgmt.c:79)
           by 0x.. glfs_volumes_init (/usr/src/debug/glusterfs-3.11dev/api/src/glfs.c:160)
           by 0x.. glfs_init_common (/usr/src/debug/glusterfs-3.11dev/api/src/glfs.c:868)
           by 0x.. glfs_init@@GFAPI_3.4.0 (/usr/src/debug/glusterfs-3.11dev/api/src/glfs.c:913)
           by 0x.. main (/root/gluster-debug/gfapi-load-volfile/gfapi-load-volfile.c:54)
    
    When the xlators is unloaded, it should free the resources it allocated.
    This can easily be done in the fini() function.
    
    Change-Id: I079e78cc207145bc542e2282fc4cf2bb4dadc28a
    BUG: 1442569
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17143
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 8b4e7cb692f1f6e7612bc2c4565e2a834e530a3a
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Fri Apr 28 05:45:16 2017 -0400

    api: fix typo of glfs_upcall_get_event
    
    glfs_upcall_inode_get_event is not exist.
    
    Change-Id: I27bd7eb9bf99d3289ae12fe31405d3b46855152d
    BUG: 1447116
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17135
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 07cc8679cdf3b29680f4f105d0222da168d8bfc1
Author: Kevin Vigor <kvigor@fb.com>
Date:   Tue Mar 21 08:23:25 2017 -0700

    Halo Replication feature for AFR translator
    
    Summary:
    Halo Geo-replication is a feature which allows Gluster or NFS clients to write
    locally to their region (as defined by a latency "halo" or threshold if you
    like), and have their writes asynchronously propagate from their origin to the
    rest of the cluster.  Clients can also write synchronously to the cluster
    simply by specifying a halo-latency which is very large (e.g. 10seconds) which
    will include all bricks.
    
    In other words, it allows clients to decide at mount time if they desire
    synchronous or asynchronous IO into a cluster and the cluster can support both
    of these modes to any number of clients simultaneously.
    
    There are a few new volume options due to this feature:
      halo-shd-latency:  The threshold below which self-heal daemons will
      consider children (bricks) connected.
    
      halo-nfsd-latency: The threshold below which NFS daemons will consider
      children (bricks) connected.
    
      halo-latency: The threshold below which all other clients will
      consider children (bricks) connected.
    
      halo-min-replicas: The minimum number of replicas which are to
      be enforced regardless of latency specified in the above 3 options.
      If the number of children falls below this threshold the next
      best (chosen by latency) shall be swapped in.
    
    New FUSE mount options:
      halo-latency & halo-min-replicas: As descripted above.
    
    This feature combined with multi-threaded SHD support (D1271745) results in
    some pretty cool geo-replication possibilities.
    
    Operational Notes:
    - Global consistency is gaurenteed for synchronous clients, this is provided by
      the existing entry-locking mechanism.
    - Asynchronous clients on the other hand and merely consistent to their region.
      Writes & deletes will be protected via entry-locks as usual preventing
      concurrent writes into files which are undergoing replication.  Read operations
      on the other hand should never block.
    - Writes are allowed from _any_ region and propagated from the origin to all
      other regions.  The take away from this is care should be taken to ensure
      multiple writers do not write the same files resulting in a gfid split-brain
      which will require resolution via split-brain policies (majority, mtime &
      size).  Recommended method for preventing this is using the nfs-auth feature to
      define which region for each share has RW permissions, tiers not in the origin
      region should have RO perms.
    
    TODO:
    - Synchronous clients (including the SHD) should choose clients from their own
      region as preferred sources for reads.  Most of the plumbing is in place for
      this via the child_latency array.
    - Better GFID split brain handling & better dent type split brain handling
      (i.e. create a trash can and move the offending files into it).
    - Tagging in addition to latency as a means of defining which children you wish
      to synchronously write to
    
    Test Plan:
    - The usual suspects, clang, gcc w/ address sanitizer & valgrind
    - Prove tests
    
    Reviewers: jackl, dph, cjh, meyering
    
    Reviewed By: meyering
    
    Subscribers: ethanr
    
    Differential Revision: https://phabricator.fb.com/D1272053
    
    Tasks: 4117827
    
    Change-Id: I694a9ab429722da538da171ec528406e77b5e6d1
    BUG: 1428061
    Signed-off-by: Kevin Vigor <kvigor@fb.com>
    Reviewed-on: http://review.gluster.org/16099
    Reviewed-on: https://review.gluster.org/16177
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9374338f9c2f126c6608625f750d5ea1f7ef6a06
Author: Shyamsundar Ranganathan <srangana@redhat.com>
Date:   Mon May 1 17:22:34 2017 +0000

    Revert "contrib/timerwheel: probable bug on 32-bit, use __builtin_ffs()"
    
    This reverts commit c92b8347aea8ce78ca3fbc49b88f5adadc98509b.
    
    Commit is not ready for a merge!
    
    Change-Id: I3b3b52f7bfb4781dd42160e2b1059b4cdeb17956
    Reviewed-on: https://review.gluster.org/17147
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c92b8347aea8ce78ca3fbc49b88f5adadc98509b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Sun Apr 30 18:59:17 2017 -0400

    contrib/timerwheel: probable bug on 32-bit, use __builtin_ffs()
    
    Simply always defining BITS_PER_LONG as 64 seems like it's almost
    certainly wrong on 32-bit platforms and could potentially result in
    incorrect results.
    
    fls and, e.g., __builtin_ffs() return the same answer for any given
    input, making it seem like the name fls (find last set) is a misnomer
    and ffs (find first set, starting from the lsb) is the more accurate
    name.
    
    Using __builtin_ffs() causes the compiler (in intel) to emit code
    with the bsf (bit scan forward) insn, which is approx 3x faster than
    the code in ffs(), at least on the machine I tried it on. (Even so,
    it takes 10M+ iterations for the speed difference to be measurable.
    Choosing the "faster" implementation seems like a no-brainer, even
    if there may not be any significant gain by doing so.)
    
    Change-Id: I1616dda1a5b76f208ba737a713877c1673131e33
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17142
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 73fcf3a874b2049da31d01b8363d1ac85c9488c2
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 17 15:50:07 2017 +0530

    core: make the per glusterfs_ctx_t timer-wheel refcounted
    
    xlators can use a 'global' timer-wheel for scheduling events. This
    timer-wheel is managed per glusterfs_ctx_t, but does not need to be
    allocated for every graph. When an xlator wants to use the timer-wheel,
    it will be instanciated on demand, and provided to xlators that request
    it later on.
    
    By adding a reference counter to the glusterfs_ctx_t for the
    timer-wheel, the threads and structures can be cleaned up when the last
    xlator does not have a need for it anymore. In general, the xlators
    request the timer-wheel in init(), and they should return it in fini().
    
    Because the timer-wheel is managed per glusterfs_ctx_t, the functions
    can be added to ctx.c and do not need to live in their very minimal
    tw.[ch] files.
    
    Change-Id: I19d225b39aaa272d9005ba7adc3104c3764f1572
    BUG: 1442788
    Reported-by: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17068
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 859669759f7fa0f2114add13660ce3bf16c77f30
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Jan 2 14:03:18 2014 -0500

    extras/hook-scripts: SELinux brick file context management scripts
    
    The SELinux policy for gluster defines the glusterd_brick_t type to
    support server side SELinux (e.g., server side labels). Add
    convenience hook scripts that users/packagers can install to ensure
    that new bricks are labeled correctly.
    
    The volume create hook script adds a new SELinux file context for
    each brick path and runs a restorecon to label the brick. The
    volume delete hook removes the per-brick SELinux file context.
    
    Change-Id: I5f102db5382d813c4d822ff74e873a7a669b41db
    BUG: 1047975
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/6630
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit c6dd1e68dfe60e747e318a9e28a067e24576fdb6
Author: Jeff Darcy <jdarcy@fb.com>
Date:   Fri Apr 28 14:19:27 2017 -0700

    tests: fix typo
    
    I've been staring at this for ages, and it finally got to me.
    
    Change-Id: I472dc2b2cf3ab175014ed673d73b543aa3e14d14
    Signed-off-by: Jeff Darcy <jdarcy@fb.com>
    Reviewed-on: https://review.gluster.org/17140
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 7a9d6aa5999a71e29c5fa47a0ea7105c6494123a
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jan 17 17:23:52 2017 +0100

    fuse: enhance fusedump to include timestamp and a signature
    
    (Also referred to as "fusedump v2".)
    
    Change-Id: I837944024efd1b9055c2f5f91bd5723ef350e688
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/16422
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ef60a29703f520c5bd06467efc4a0d0a33552a06
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 20 10:17:07 2017 +0530

    mount/fuse: Replace GF_LOG_OCCASIONALLY with gf_log() to report fop failure at all times
    
    Change-Id: Ibd8e1c6172812951092ff6097ba4bed943051b7c
    BUG: 1440051
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17086
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit d51288540241d1f7785bb17bdc0702c0879087a9
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Mar 22 17:14:25 2017 +0530

    cluster/dht: Make rebalance throttle option tuned by number
    
    Current rebalance throttle options: lazy/normal/aggressive may not always be
    sufficient for the purpose of throttling.  In our recent test, we observed for
    certain setups, normal and aggressive modes behaved similarly consuming full
    disk bandwidth. So in cases like this admin should be able to  tune it
    down(or vice versa) depending on the need.
    
    Along with old throttle configurations, thread counts are tuned based on number.
    e.g. gluster v set vol-name cluster-rebal.throttle  5.
    
    Admin can tune up/down between 0 and the number of cores available.
    
    Note: For heterogenous servers, validation will fail on the old server if "number"
    is given for throttle configuration.
    The message looks something like this:
    "volume set: failed: Staging failed on vm2. Error: cluster.rebal-throttle should be {lazy|normal|aggressive}"
    
    Test: Manual test by logging active thread number after reconfiguring throttle option.
    testcase: tests/basic/distribute/throttle-rebal.t
    
    Change-Id: I46e3cde546900307831028b344ecf601fd9b02c3
    BUG: 1438370
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/16980
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 8b2ef5076284e44a87698393c8094c925fa863fa
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Jan 11 16:04:47 2017 +0530

    dht: send lookup on old name inside rename with bname and pargfid
    
    Inside rename, a lookup is done on the source name to make sure that
    the file is there. But we used to do a gfid based lookup and hence,
    even if the source name was renamed to a new name from some other client,
    lookup will be successful as server3_3_lookup will fetch the new path
    based on the gfid.
    
    So even if the source file does not exist any more rename will carry on,
    and as server3_3_link(destination is hashed to a different brick other
    than source cached scenario) also does gfid based resolve, it wont
    detect that the source name does not exist and hardlink creation will be
    successful (since gfid based resolve will get the new dentry).
    
    To solve this problem, do a name based lookup inside rename. So that
    rename will fail right away if the source does not exist.
    
    Change-Id: Ieba8bdd6675088dbf18de90ed4622df043d163bd
    BUG: 1412135
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/16375
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bff6b7b1d75b55bfdc11a6aac613b51bdafee989
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Jan 10 16:11:50 2017 +0530

    cluster/dht: rebalance perf enhancement
    
    Problem: Throttle settings "normal" and "aggressive" for rebalance
    did not have performance difference.
    
    normal mode spawns $(no. of cores - 4)/2 threads and aggressive
    spawns $(no. of cores - 4) threads. Though aggressive mode has twice
    the number of threads compared to that of normal mode, there was no
    performance gain when switched to aggressive mode from normal mode.
    
    RCA:
    During the course of debugging the above problem, we tried assigning
    migration job to migration threads spawned by rebalance, rather than
    synctasks(as there is more overhead associated to manage the task
    queue and threads). This gave us a significant improvement over rebalance
    under synctasks. This patch does not really gurantee that there will be a
    clear performance difference between normal and aggressive mode, but this
    patch certainly maximized the disk utilization for 1GBfiles run.
    
    Results:
    
    Test enviroment:
    Gluster Config:
    Number of Bricks: 2 (one brick per disk(RAID-6 12 disk))
    Bricks:
    Brick1: server1:/brick/test1/1
    Brick2: server2:/brick/test1/1
    Options Reconfigured:
    performance.readdir-ahead: on
    server.event-threads: 4
    client.event-threads: 4
    
    1000 files with 1GB each were created/renamed such that all files will have
    server1 as cached and server2 as hashed, so that all files will be migrated.
    
    Test machines had 24 cores each.
    
    Results  with/without synctask based migration:
    -----------------------------------------------
    
    mode                    normal(10threads)          aggressive(20threads)
    
    timetaken               0:55:30 (h:m:s)            0:56:3 (h:m:s)
    withsynctask
    
    timetaken
    with migrator           0:38:3 (h:m:s)             0:23:41 (h:m:s)
    threads
    
    From above table it can be seen that, there is a clear 2x perf gain between
    rebalance with synctask vs rebalance with migrator threads.
    
    Additionally this patch modifies the code so that caller will have the exact error
    number returned by dht_migrate_file(earlier the errno meaning was overloaded). This
    will help avoiding scenarios where migration failure due to ENOENT, can result in
    rebalance abort/failure.
    
    Change-Id: I8904e2fb147419d4a51c1267be11a08ffd52168e
    BUG: 1420166
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/16427
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4e31840039cfd789c80160b52b4be81517108ca4
Author: Kinglong Mee <mijinlong@open-fs.com>
Date:   Tue Apr 25 08:20:28 2017 -0400

    api: fix two typos of GFAPI_PUBLIC function define
    
    Change-Id: I2f9915b3572c4cbce6748e99a037daba439a187e
    BUG: 1446273
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17112
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 081f9febeec61787ebe81850a081beda17de3047
Author: Prashanth Pai <ppai@redhat.com>
Date:   Thu Apr 27 18:26:02 2017 +0530

    glusterd: Fix removing pmap entry on rpc disconnect
    
    Problem:
    The following line of code intended to remove pmap entry for the
    connection during disconnects:
    
        pmap_registry_remove (this, 0, NULL, GF_PMAP_PORT_NONE, xprt);
    
    However, no pmap entry will have it's type set to GF_PMAP_PORT_NONE
    at any point in time. So a call to pmap_registry_search_by_xprt() in
    pmap_registry_remove() will always fail to find a match.
    
    Fix:
    Optionally ignore pmap entry's type in pmap_registry_search_by_xprt().
    
    BUG: 1193929
    Change-Id: I705f101739ab1647ff52a92820d478354407264a
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: https://review.gluster.org/17129
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 83abcba6b42f94eb5a6495a634d4055362a9d79d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Mar 27 16:09:56 2017 -0400

    build: conditionally build legacy gNFS server and associated sub-packaging
    
    Plus some additional logic in glusterd to ensure gnfs (glusterfs)
    daemons are never started if server/nfs xlator is not installed.
    
    As a service, nfs is still initialized. The glusterfs-gnfs RPM
    may be installed or uninstalled independent of anything else,
    including on a system where gluster is actively running, so the
    existence of the xlator is always tested before trying to start
    gnfs.
    
    Change-Id: I56743ad1cb36a84917226d7d26cb9d015d441e66
    BUG: 1326219
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16958
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit ab88f655e6423f51e2f2fac9265ff4d4f5c3e579
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 27 11:53:24 2017 +0530

    cluster/dht: Pass the correct xdata in fremovexattr fop
    
    Change-Id: Id84bc87e48f435573eba3b24d3fb3c411fd2445d
    BUG: 1440051
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17126
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e624e7fe38a784363c57108c73487d83a7bda562
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jan 3 15:26:30 2017 +0100

    fuse: clean up mount flag processing
    
    In general, when one invokes a mount helper program -- basically
    anything that mounts something based on its command line, so thinking of
    mount(8), mount.<fs-type> or fusermount, but also of FUSE servers in
    general, including glusterfs -- the command line arguments that are to
    affect mount(2) are mapped to a bitmask called the mount flags, which is
    passed to mount(2), so that the kernel can interpret the flag bits and
    adjusts properties of the mount accordingly.
    
    There is a traditional syntax for this mechanism as implemented in
    mount(8): one passes "-ocomma,separated,mount,options" and the
    individual option name strings are mapped to flag bits in mount(8).
    
    FUSE further explores this idea and typically the FUSE server command
    lines allow further option names to be used in the "-ooption,name,list"
    which are then separated from the kernel sanctioned option names (to
    which we'll refer as "system mount options") and are passed to a
    platform specific lower level fuse mount helper interface.
    
    The separation of system mount option names and FUSE specific option
    names is also platform specific, so the general mount interface
    function, which in case of glusterfs is gf_fuse_mount(), should abstract
    this away.
    
    Therefore we change the signature of this function from
    
            int gf_fuse_mount (const char *mountpoint, char *fsname,
                               unsigned long mountflags, char *mnt_param,
                               pid_t *mtab_pid, int status_fd);
    
    to
    
            int gf_fuse_mount (const char *mountpoint, char *fsname,
                               char *mnt_param, pid_t *mtab_pid,
                               int status_fd);
    
    and deal with flag extraction in platform specific mount code. Note that
    the sole purpose of the mountflags argument was to indicate read-only
    mounting. The other system mount option names were expected to reside in
    the comma-separated mnt_param string, but they were not properly
    processed (see the referred BUG). With the new gf_fuse_mount signature
    read-only mounting is to be indicated as a "ro" component in mnt_param.
    
    - For Darwin, which has a dedicated, separate gf_fuse_mount
      implementation, gf_fuse_mount was ignoring mountflags, so only the
      signature had to to be adjusted. However, as bonus, we gain read-only
      support for Darwin, which was missing so far, given that it was
      indicated via the ignored mountflags. Darwin's low level mount helper
      relies on the "ro" component of the option string, which agrees with
      the new calling convention of gf_fuse_mount.
    
    - On Linux, system mount option name handling (apart from the
      distinguished read-only option) used to have the inadvertent side
      effect of adding "nosuid,nodev" as indicated in BUG; since
      Ia89d975d1e27fcfa5ab2036ba546aa8fa0d2d1b0 this side effect is removed,
      but system mount option name handling was left broken (passing system
      mount options other than "ro" fails to mount).
    
    - On other platforms, system mount option name handling is broken
      (expect for the distinguished read-only option).
    
    As of this change, in the general (non-Darwin) implementation of
    gf_fuse_mount we take care of proper separation of system mount names
    and their conversion to mount flags. For Linux, we adopt the conversion
    table from FUSE upstream. For other systems we just provide a best
    effort to support those system mount options which are understood across
    all Unices (nosuid,nodev,noatime,noexec,ro). (This can be improved later
    to provide proper plaform support.)
    
    BUG: 1297182
    Change-Id: I5d10b5df46feba7a02bf5bf1018db69e6b52260a
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/16313
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>

commit ec7a0c7eefacc68532bdc909f05a01eca8b3139d
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Apr 27 14:34:08 2017 +0530

    extras/hooks: Use double quotes while using [..]
    
    This avoids the following warning when first operand is null
    
    [: =: unary operator expected
    
    Change-Id: I5439d8f60a6d9e30e6ba04c16c3de2096a87c38f
    BUG: 1446126
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/17127
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 0e50c4b3ea734456c14e2d7a578463999bd332c3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Apr 26 08:11:56 2017 -0400

    packaging: /var/run/gluster owner gluster:gluster(0775) for statedumps
    
    gfapi has the ability to take statedumps. However, if the application
    using gfapi isn't running with root privs the statedump file can't be
    written to the default location, i.e. /var/run/gluster.
    
    Change-Id: I97d8919ef8b8cd4775e1a206f939a2bf0046786d
    BUG: 1445569
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17122
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit a94b7df7b9308a590ebcac15536d22a386561f10
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Apr 21 19:11:24 2017 +0200

    build: ensure autoconf template expansions resolve variables
    
    Make sure the following autotools managed variables:
    
    GLUSTERFS_LIBEXECDIR
    GLUSTERD_MISCDIR
    GLUSTERD_VOLFILE
    LOCALSTATEDIR
    
    get expanded to literal paths when the configure
    script generates the installed versions of certain
    text files from *.in templates.
    
    This change is partly implemented by restoring some of
    the "eval echo $variable" style forced expansions in
    configure that were removed in
    If5219cadc51ae316f7ba2e2831d739235c77902d.
    
    BUG: 1444228
    Change-Id: I3b31b1259c5101252bbc37861683894e6eae29e6
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17096
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit c6b635d5b2326075549f74d1d81f408f2f7d2d4a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Mar 17 13:14:51 2017 +0530

    libglusterfs/stack.h: reduce duplication of code
    
    * Use STACK_UNWIND_STRICT everywhere.
    * Provide STACK_WIND_COMMON as both STACK_WIND_COOKIE
      and STACK_WIND differ by just 1 line and 1 option.
    
    Updates gluster/glusterfs#137
    
    Change-Id: Ifbb6b9c4702b02f4a02834824f509fd10c78f0ce
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/16915
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit dbfc99236ac6cb143b41b57cecea0598ad1df927
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Mar 9 13:31:44 2017 +0530

    cluster/dht: Document detailing transactions in dht
    
    Change-Id: If69d67ce5dffe966fbc1e4ad834ca110e1e0b745
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Updates: #191
    Reviewed-on: https://review.gluster.org/16876
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 232882ac6f93ebac847715f522a99960bcfb11a6
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Apr 20 02:08:32 2017 -0400

    io-stats: fix some memory leak after fini
    
    Change-Id: Id057b711d7f615c6d2db1ebbca2f17d0afacb2ae
    BUG: 1444023
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17089
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 9f5e59abfbf529b91d699143b0c69c8748ac6253
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 7 06:19:30 2017 -0400

    geo-rep: Fix mount cleanup
    
    On corner cases, mount cleanup might cause
    worker crash. Fixing the same.
    
    Change-Id: I38c0af51d10673765cdb37bc5b17bb37efd043b8
    BUG: 1433506
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17015
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 3579aaaef0027c62bad57952e433e15fa9f1532c
Author: Richard Wareing <rwareing@fb.com>
Date:   Mon Sep 22 17:42:04 2014 -0700

    nfs: Check for null buf, and set op_errno to EIO not 0
    
    Summary:
    - Prevent crashes for the case where "getattr" actually failed and
      returned with a NULL buf, but the op_errno was set to 0.
    - This is a cherry-pick of D1571184
    
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Change-Id: Ia2d6ad7539df714f9420dcf063c7c14e727bb7e3
    BUG: 1428064
    Reviewed-on: http://review.gluster.org/16152
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kevin Vigor <kvigor@fb.com>
    Reviewed-on: https://review.gluster.org/16803
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 63a39c764181e60bc7bd8236996cf9abe353d906
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Fri Feb 26 20:59:00 2016 -0800

    nfs: Tear down transports for requests that arrive before the volume is initialized
    
    Summary:
    - Disconnects RPC transports for requests that cannot be serviced
      because volumes are not ready.
    - This is a cherry-pick of D2991403
    
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Change-Id: I07ff0795b81d25624541ff981b5f2586d078e9a6
    BUG: 1428068
    Reviewed-on: http://review.gluster.org/16154
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kevin Vigor <kvigor@fb.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-on: https://review.gluster.org/16805
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 9e57016757f1fb431dee8196c781b5d15b51cd43
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Apr 20 02:13:27 2017 -0400

    api: free the xattr data after using in glfs_volfile_fetch
    
    Change-Id: I89a7df93039e367301fd70df722c13f1d8b3484b
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17091
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 25f0a7b153b30b2c0e8278b0ce11d1199c3fb006
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Apr 26 10:24:40 2017 +0530

    cluster/dht Remove redundant logs in dht rmdir
    
    Removing redundant logs were introduced in
    https://review.gluster.org/#/c/17065/
    
    Change-Id: I0d6055488b51a13c91d2121e87f653cdb94888b0
    BUG: 1445590
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17118
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 22e942dd201734761f37eaf9b10970e7da9d9a14
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Apr 25 15:04:34 2017 +0530

    nl-cache: Fix the issue in refd_inode counting and prune the cache
    
    Change-Id: I5b9beb8502667bc3876385900bc01b6491348716
    BUG: 1442569
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17110
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4076b73b2f4fb3cca0737974b124f33f76f9c9c1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jan 3 02:35:06 2017 -0500

    feature/dht: Directory synchronization
    
    Design doc: https://review.gluster.org/16876
    
    Directory creation is now synchronized with blocking inodelk of the
    parent on the hashed subvolume followed by the entrylk on the hashed
    subvolume between dht_mkdir, dht_rmdir, dht_rename_dir and lookup
    selfheal mkdir.
    
    To maintain internal consistency of directories across all subvols of
    dht, we need locks. Specifically we are interested in:
    
     1. Consistency of layout of a directory. Only one writer should modify
        the layout at a time. A writer (layout setting during directory heal
        as part of lookup) shouldn't modify the layout while there are
        readers (all other fops like create, mkdir etc., which consume
        layout) and readers shouldn't read the layout while a writer is in
        progress. Readers can read the layout simultaneously. Writer takes
        a WRITE inodelk on the directory (whose layout is being modified)
        across ALL subvols. Reader takes a READ inodelk on the directory
        (whose layout is being read) on ANY subvol.
    
     2. Consistency of directory namespace across subvols. The path and
        associated gfid should be same on all subvols. A gfid should not be
        associated with more than one path on any subvol. All fops that can
        change directory names (mkdir, rmdir, renamedir, directory creation
        phase in lookup-heal) takes an entrylk on hashed subvol of the
        directory.
    
     NOTE1: In point 2 above, since dht takes entrylk on hashed subvol of a
            directory, the transaction itself is a consumer of layout on
            parent directory. So, the transaction is a reader of parent
            layout and does an inodelk on parent directory just like any
            other layout reader. So a mkdir (dir/subdir) would:
    
         > Acquire a READ inodelk on "dir" on any subvol.
         > Acquire an entrylk (dir, "subdir") on hashed subvol of "subdir".
         > creates directory on hashed subvol and possibly on non-hashed subvols.
         > UNLOCK (entrylk)
         > UNLOCK (inodelk)
    
     NOTE2: mkdir fop while setting the layout of the directory being created
            is considered as a reader, but NOT a writer. The reason is for
            a fop which can consume the layout of a directory to come either
            of the following conditions has to be true:
    
         > mkdir syscall from application has to complete. In this case no
           need of synchronization.
         > A lookup issued on the directory racing with mkdir has to complete.
           Since layout setting by a lookup is considered as a writer, only
           one of either mkdir or lookup will set the layout.
    
    Code re-organization:
       All the lock related routines are moved to "dht-lock.c" file.
       New wrapper function is introduced to take blocking inodelk
       followed by entrylk 'dht_protect_namespace'
    
    Updates #191
    Change-Id: I01569094dfbe1852de6f586475be79c1ba965a31
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    BUG: 1443373
    Reviewed-on: https://review.gluster.org/15472
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 1538c98f5e33e0794830d5153f17a96ff28c9914
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Feb 27 18:45:16 2017 -0800

    libglusterfs: accept random volname in glusterfs_graph_prepare()
    
    When the call to glfs_new("volname") passes a name for the volume and it
    does not match the name of the subvolume in the graph, glfs_init() will
    fail. This is easily reproducible by a gfapi program that loads the
    volume from a .vol file, and not from a GlusterD server.
    
    Change-Id: I33e77fbee7d12eaefe7c384fad6aecfa3582ea5a
    BUG: 1425623
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16796
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 0451909e0533d357a45dd427226028e095240dac
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Feb 21 14:35:52 2017 +0100

    debug/sink: add xlator to aid in resource leak debugging
    
    This new xlator does not allocate any resources on init(). This makes it
    a good option to use for debugging xlator releated resources leaks on
    fini().
    
    By putting the sink xlator as single xlator in a .vol file, and loading
    it through gfapi, we can investigate the resource leaks that are
    happening through gfapi (and the Gluster core). By extending the .vol
    file with additional xlators, it is possible to analyze resource leaks
    of single xlators.
    
    Change-Id: Idb5faa861b623dd5b2a988b181e669b0d52c2a0e
    BUG: 1425623
    Fixes: #176
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16806
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit dba51428dc16762a9489249f6d9b2e64c0b8303e
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Apr 24 16:27:23 2017 +0530

    cluster/dht: correct space check for rebalance
    
    With rebalance doing fallocate on destination, we don't need to
    add file size to the "destination available space" to decide whether
    to migrate the file or not.
    
    Notes: Fallocate would have already occupied the file size space on
    destination
    
    Change-Id: If7f6a6654e6257726680cf20d618482a6e9095a6
    BUG: 1441508
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17104
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit db0e5582b118d5bb0c8bb491f46fa2ae0dcfa97e
Author: karthik-us <ksubrahm@redhat.com>
Date:   Tue Mar 14 13:17:11 2017 +0530

    cli: Adding warning message while creating a replica 2 volume
    
    Warn the CLI about ending up in split-brain situation with a
    replica 2 volume. Display arbiter and replica 3 are recommended
    option to avoid this and point to the document on split-brain
    and ways to deal with it.
    
    Change-Id: I7f31f3c74818d440a684b3130bc5ccdc72258f01
    BUG: 1431963
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: https://review.gluster.org/16899
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit fb66df4c4496f19a3800e8efa39c52f77320a2fb
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Apr 20 02:14:28 2017 -0400

    api: fix bad release of dict causes memory leak
    
    Change-Id: Ic7169fd05aff7bf46108e8ac7b1f29688a7f2358
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17092
    Tested-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 6d021a281076cccd05bbf31e3d66670250edfb4a
Author: Jungyeon Yoon <jungyeon.yoon@gmail.com>
Date:   Tue Apr 25 15:23:32 2017 +0900

    remove redundant function definition
    
    function definition is duplicated
    
    erase second sys_ftruncate() definition
    
    No test cases
    
    Change-Id: I3eead1380b527b8b0e480f45b39e0c4bc9b2b92a
    Signed-off-by: Jungyeon Yoon <jungyeon.yoon@gmail.com>
    Reviewed-on: https://review.gluster.org/17106
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d6194de9731ae8f6d97735c7cd5b2434a44c21b5
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Apr 21 19:43:08 2017 +0200

    build: correct bogus date in RPM spec
    
    In the RPM spec changelog there is an entry
    wth the following date:
    
      Wed Feb 7 2017
    
    However, Feb 7 2017 was Tuesday. In this change
    we correct the day of the date.
    
    BUG: 1444941
    Change-Id: I073bfe878e0a21d446a80c2f4ee045facba3e82b
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: https://review.gluster.org/17100
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit bf20b066c233a9fc7c82335a131a7969f356b89b
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Thu Apr 20 12:24:51 2017 +0530

    cluster/ec: Implement self-heal-window_size option
    
    Fix implements the heal window size option for
    EC. This option control the maximum size of
    read/write operation carried out in self-heal
    process.
    
    BUG: 1441491
    Change-Id: I6c0ef65c9ca18b0828f91b319d4f52ac5b77d0d8
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/17098
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f071d2a285ea4802fe8f328f9f275180983fbbba
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Apr 20 07:18:52 2017 -0400

    glusterd/geo-rep: Fix snapshot create in geo-rep setup
    
    glusterd persists geo-rep sessions in glusterd
    info file which is represented by dictionary
    'volinfo->gsync_slaves' in memory. Glusterd also
    maintains in memory active geo-rep sessions in
    dictionary 'volinfo->gsync_active_slaves' whose key
    is "<slave_url>::<slavhost>".
    
    When glusterd is restarted while the geo-rep sessions
    are active, it builds the 'volinfo->gsync_active_slaves'
    from persisted glusterd info file. Since slave volume
    uuid is added to "voinfo->gsync_slaves" with the commit
    "http://review.gluster.org/13111", it builds it with key
    "<slave_url>::<slavehost>:<slavevol_uuid>" which is
    wrong. So during snapshot pre-validation which checks
    whether geo-rep is active or not, it always says it is
    ACTIVE, as geo-rep stop would not deleted this key.
    Fixed the same in this patch.
    
    Change-Id: I185178910b4b8a62e66aba406d88d12fabc5c122
    BUG: 1443977
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17093
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit d60ca8e96bbc16b13f8f3456f30ebeb16d0d1e47
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 20 10:08:02 2017 +0530

    cluster/dht: Pass the req dict instead of NULL in dht_attr2()
    
    This bug was causing VMs to pause during rebalance. When qemu winds
    down a STAT, shard fills the trusted.glusterfs.shard.file-size attribute
    in the req dict which DHT doesn't wind its STAT fop with upon detecting
    the file has undergone migration. As a result shard doesn't find the
    value to this key in the unwind path, causing it to fail the STAT
    with EINVAL.
    
    Also, the same bug exists in other fops too, which is also fixed in
    this patch.
    
    Change-Id: Id7823fd932b4e5a9b8779ebb2b612a399c0ef5f0
    BUG: 1440051
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17085
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 05d9c5a3d684512e97327c8d73988ef7f29e1511
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 20 09:46:46 2017 -0400

    packaging: no firewalld-filesystem before el7.3
    
    Attempting to build on RHEL or CentOS 7.2 will fail because there is
    no firewalld-filesystem RPM. (This probably holds true for older versions
    of Fedora too, although the versions where this would apply are so old
    and so far gone as to be (nearly) meaningless.
    
    The firewalld rpm in 7.3 has a Requires: firewalld-filesystem.
    
    In addition to other things, the firewalld-filesystem rpm provides rpm
    build time macros (a strange place for them actually, there ought to be
    a firewalld-devel subpackage instead).
    
    Florian Festi, one of the Fedora RPM/YUM/DNF devs, strongly suggests
    that even in 7.3 the correct way to get firewalld-filesystem is to use
    BuildRequires: firewalld.
    
    N.B. That someone might try to install 7.3-built RPMs on their 7.2 system
    is beside the point.
    
    Change-Id: Iac8cc74a3345acaaed45af4c14e141b7a1711f84
    BUG: 1443959
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/17094
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1e2f13fa89a5aef64cc9e5a229216820ed6e7556
Author: Kinglong Mee <kinglongmee@gmail.com>
Date:   Thu Apr 20 02:12:42 2017 -0400

    api: free all dynamic memory returned from xdr_to_generic
    
    Change-Id: I01235ffca80683e69e99da09a9fc1a6d3ffdcb65
    Signed-off-by: Kinglong Mee <mijinlong@open-fs.com>
    Reviewed-on: https://review.gluster.org/17090
    Tested-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit b5ebf8adf6127e052ac0dae42051a5f1f791343d
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Mon Apr 17 10:06:20 2017 +0800

    debug/error-gen: Use STACK_WIND_TAIL instead of STACK_WIND
    
    Also remove unnecessary fop cbks, which are no longer necessary.
    
    1.We don't need to call STACK_WIND if we care nothing in cbk stack, so
      I use STACK_WIND_TAIL instead of STACK_WIND without new a frame
    2.Fix several indent problems
    3.Fix return value issues in init and reconfigure
    
    Change-Id: Id57a68fec39b5b47cd4ff77664399ed3ef1d3888
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/17062
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit e5f9ba138571bd18226462c49ff6a55f5c3ed3a4
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Apr 17 15:21:20 2017 +0530

    cluster/dht: rm -rf fails if dir has stale linkto files
    
    rm -rf <dir> fails with ENOENT if dir contains a lot of
    stale linkto files. This is because a single
    readdirp is sent as part of the rmdir which would return
    and delete only as many linkto files on the bricks as would fit
    in one readdirp buffer. Running rm -rf <dir> multiple times
    will eventually delete all the files. The fix sends readdirp
    on each subvol until no more entries are returned.
    
    Change-Id: I447f2d193de4bd8ac16e4541c6b919d22250e39e
    BUG: 1442724
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/17065
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 799a2ff8299db6d6dc75f1533f4bd5a3bb72164d
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Mar 9 18:08:28 2017 +0530

    cluster/afr: GFID split brain resolution with favorite-child-policy
    
    Problem:
    Currently the automatic split brain resolution with favorite child policy
    is not resolving the GFID split brains.
    
    Fix:
    When there is a GFID split brain and the favorite child policy is set to
    size/mtime/ctime/majority, based on the policy decide on the source and
    sinks. Delete the entry from the sinks and recreate it from the source.
    Mark the appropriate pending attributes and resolve the GFID split brain.
    When the heal takes place it will complete the pending heals and reset
    the attributes.
    
    Change-Id: Ie30e5373f94ca6f276745d9c3ad662b8acca6946
    BUG: 1430719
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: https://review.gluster.org/16878
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 98dc1f08c114adea1f4133c12dff0d4c3d75b30d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 20 13:57:27 2017 +0530

    glusterd: set conn->reconnect to null on timer cancellation
    
    Change-Id: Ic48e6652f431daeb0db027660f6c9de16d893f08
    BUG: 1443896
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17088
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 561766e45a323be3d5c521fdb47f68d71cea776e
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Apr 12 15:24:14 2017 +0530

    Implement negative lookup cache
    
    Before creating any file negative lookups(1 in Fuse, 4 in SMB etc.)
    are sent to verify if the file already exists. By serving these
    lookups from the cache when possible, increases the create
    performance by multiple folds in SMB access and some percentage
    in Fuse/NFS access.
    
    Feature page: https://review.gluster.org/#/c/16436
    
    Updates #82
    Change-Id: Ib1c0e7ac7a386f943d84f6398c27f9a03665b2a4
    BUG: 1442569
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16952
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2aeca0ef02733ebd9b7979e4c27585f3ebff53d7
Author: Shyam <srangana@redhat.com>
Date:   Mon Apr 10 11:36:17 2017 -0400

    scripts: Update rfc.sh to prompt for a github issue on RFE commits
    
    If a commit does not contain a bug check with the committer if
    this is an RFE (or such) and prompt to amend the commit with a
    github issue that relates to the change.
    
    Also, give some specifics on what string to add to refer to an
    issue.
    
    This change is meant to encourage committers to add github issues
    and hence will not enforce the same, IOW the check can be ignored
    and code can still be submitted. Reviewers would hence be
    responsible to check for the same.
    
    Change-Id: Id382247a787a96d55be6be554332a1b7ccde6bcd
    BUG: 1428036
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: https://review.gluster.org/17032
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b350bcd6a3db2e92d1baa47a5ec02efd09f76f16
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Apr 17 13:00:54 2017 +0530

    cluster/dht: Skip file migration if the subvol that meets min-free-disk
    criteria happens to be the same subvol containing data-file
    
    Rebalance need to figure out a new subvol in case the hashed subvol
    does not have enough space. In the process of figuring out the new subvol,
    we need to ignore the source subvol, otherwise it will lead to data loss.
    
    Test: Manual
    Ran the following
    sizeof /tmp/1: 1.5GB
    sizeof /brick/1: 16GB
    sizeof /tmp/2: 1.5GB
    <start>
    
    glusterd;  gluster v create test1 vm1:/brick/1 vm1:/tmp/1;
    gluster v start test1;
    mount -t glusterfs vm1:test1 /mnt;
    for i in {1..2000}
    do
    dd if=/dev/zero of=/mnt/file$i bs=1KB count=1 &> /dev/null;
    done
    gluster v add-brick test1 vm1:/tmp/2
    gluster v set test1 min-free-disk 12GB
    gluster v remove-brick test1 vm1:/tmp/1 star
    <end>
    
    file count and data were intact.
    
    Change-Id: Ib8fc8467a3d48a7c12958824c4f0b88e160b86c1
    BUG: 1441508
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17064
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e3d9018f2ddc28548c0aa18960a3a524521c9ad7
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu May 12 16:40:04 2016 -0400

    features/bit-rot-stub: bring in optional versioning
    
    * As of now bit-rot-stub does versioning always. This leads
      lots of getxattr calls being made in lookups. So make
      object versioning optional.
    
    Change-Id: I83713e45ae59fb28004bb3cfa008f2d69edebbfa
    BUG: 1359599
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/14442
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 10dad995c989e9d77c341135d7c48817baba966c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Apr 2 18:08:04 2017 +0530

    afr: don't do a post-op on a brick if op failed
    
    Problem:
    In afr-v2, self-blaming xattrs are not there by design. But if the FOP
    failed on a brick due to an error other than ENOTCONN (or even due to
    ENOTCONN, but we regained connection before postop was wound), we wind
    the post-op also on the failed brick, leading to setting self-blaming
    xattrs on that brick. This can lead to undesired results like healing of
    files in split-brain etc.
    
    Fix:
    If a fop failed on a brick on which pre-op was successful, do not
    perform post-op on it. This also produces the desired effect of not
    resetting the dirty xattr on the brick, which is how it should be
    because if the fop failed on a brick, there is no reason to clear the
    dirty bit which actually serves as an indication of the failure.
    
    Change-Id: I5f1caf4d1b39f36cf8093ccef940118638caa9c4
    BUG: 1438255
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16976
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 43695cfba3bcbb53d7127128e37a724862f65017
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 3 20:13:40 2017 +0530

    api: Fix incorrect strcmp() during fs initialisation
    
    Just chanced upon this while reading graph switch code in
    libgfapi.
    
    Change-Id: Ie62b410c22e6d0768a24187c5d587b6d3fc996bf
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16319
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c1e61fd5dfd118830e896a45d398a2041006d74e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Apr 13 11:38:08 2017 +0530

    worm: add check for internal processes in ftruncate()
    
    The patch fixes the recently seen issues with worm_sh.t test.
    
    RCA:
    
    -
    $ git log --oneline xlators/features/read-only/src/worm.c
    1b01bdc worm: allow Self-heal-Daemon to perform some operations
    c5a4a77 features/worm: Adding implementation for ftruncate
    -
    
    These two patches were merged in reverse order of their submission,
    and hence the check added for internal processes got missed in
    new fop 'ftruncate()'. The worm_sh.t passed the tests as while
    that patch got submitted there was no ftruncate() in worm xlator.
    
    Change-Id: I81a8a45fa2679917a2c859c4f5224a2c3edbc784
    BUG: 1423413
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/17048
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: David Spisla <david.spisla@iternity.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 761e2dc0432d3723e0f8cbb1cf192ad386addb08
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Apr 4 15:50:29 2017 +0530

    gfapi: Fix inode ref leak in anonymous fd I/O APIs
    
    In the APIs to do I/Os using anonymous fd, there
    is a ref taken for inode which hasn't been unreferenced
    post the operation. This shall result in the leak.
    
    Change-Id: I75ea952a6b2df58c385f4f53398e5562f255248d
    BUG: 1438738
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: https://review.gluster.org/16989
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit cc839523364e47dea715cd7241772cd68f05f76c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 17 08:39:30 2017 -0400

    glusterd: Fix snapshot failure in non-root geo-rep setup
    
    Geo-replication session directory name has the form
    '<mastervol>_<slavehost>_<slavevol>'. But in non-root
    geo-replication setup, while preparing geo-replication
    session directory name, glusterd is including 'user@'
    resulting in "<mastervol>_<user@slavehost>_<slavevol>".
    Hence snapshot is failing to copy geo-rep specific
    session files. Fixing the same.
    
    Change-Id: Id214d3186e40997d2827a0bb60d3676ca2552df7
    BUG: 1442760
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17067
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 4c623481986a4697fe7bbb3f553b877d38650422
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 10 10:29:15 2017 +0200

    gfapi: prevent off-by-one buffer overrun in glfs_sysrq()
    
    Coverity found a potential buffer overrun in the strncat() usage for
    logging the help message with glfs_sysrq(). This seems to be an
    off-by-one mistake and should be addressed by reducing the initial size
    of the remainder calculation.
    
    Change-Id: Ide14add1cb28e5200d2c0df6b3a5154999ef3ca9
    BUG: 789278
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17024
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 94196dee1f1b0e22faab69cd9b1b1c70ba3d2f6f
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Apr 13 16:20:29 2017 +0530

    dht: Add readdir-ahead in rebalance graph if parallel-readdir is on
    
    Issue:
    The value of linkto xattr is generally the name of the dht's
    next subvol, this requires that the next subvol of dht is not
    changed for the life time of the volume. But with parallel
    readdir enabled, the readdir-ahead loaded below dht, is optional.
    The linkto xattr for first subvol, when:
    - parallel readdir is enabled : "<volname>-readdir-head-0"
    - plain distribute volume : "<volname>-client-0"
    - distribute replicate volume : "<volname>-afr-0"
    
    The value of linkto xattr is "<volname>-readdir-head-0" when
    parallel readdir is enabled, and is "<volname>-client-0" if
    its disabled. But the dht_lookup takes care of healing if it
    cannot identify which linkto subvol, the xattr points to.
    
    In dht_lookup_cbk, if linkto xattr is found to be "<volname>-client-0"
    and parallel readdir is enabled, then it cannot understand the
    value "<volname>-client-0" as it expects "<volname>-readdir-head-0".
    In that case, dht_lookup_everywhere is issued and then the linkto file
    is unlinked and recreated with the right linkto xattr. The issue is
    when parallel readdir is enabled, mount point accesses the file
    that is currently being migrated. Since rebalance process doesn't
    have parallel-readdir feature, it expects "<volname>-client-0"
    where as mount expects "<volname>-readdir-head-0". Thus at some point
    either the mount or rebalance will fail.
    
    Solution:
    Enable parallel-readdir for rebalance as well and then do not
    allow enabling/disabling parallel-readdir if rebalance is in
    progress.
    
    Change-Id: I241ab966bdd850e667f7768840540546f5289483
    BUG: 1436090
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17056
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a9b5333d7bae6e20ffef07dffcda49eaf9d6823b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Apr 13 12:56:09 2017 +0530

    eventsapi: Fix webhook-test when no schema specified in URL
    
    If no schema specifed like `http` or `https` while testing webhook,
    it was failing with Schema Exception and not communicated the error
    to CLI caller.
    
    With this patch exception is handled and responded back to CLI caller.
    
    BUG: 1441945
    Change-Id: I9be11d36e9f65be873516fef370c327f1cdbc93e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: https://review.gluster.org/17054
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 324509b340ebbab1e1531de9ba0a3ed6f4563753
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 10 06:52:51 2017 -0400

    geo-rep: Remove unlink fop during rmdir
    
    Even though it is known to be 'RMDIR', os.unlink
    was being tried and os.rmdir is issued upon receiving
    EISDIR. It's unnecessary unlink call for 'RMDIR'.
    Fixed the same.
    
    Change-Id: I8dbb680ee2c7f0c32b7799b1ed5351b3621cb42a
    BUG: 1441106
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17041
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit c09f5a28bfd14066f9b8cfca53c7a9d999f1613e
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Mon Apr 10 18:46:42 2017 +0530

    glusterd: Add brick capacity details to get-state CLI output
    
    Change-Id: I53fe180e71d41d56b129254b93bb74014a2cdb43
    BUG: 1431192
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17029
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit d7f0ead43969e755d07ae92c669d63527a58c572
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Apr 14 17:19:47 2017 +0200

    meta: free this->private in fini()
    
    For every graph switch or de-init (includes calling `glfs_fini`) the
    meta_priv_t structure (80 bytes on x86_64) leaks. Because it is
    allocated in the `init()` funtion, it should be free'd in `fini()`.
    
    Change-Id: Ie45a9c9a520d55bebd0eb04c2ac667bc8c1c5acb
    BUG: 1442411
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17061
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 73f66bf422d6184c72c01493920687e880ad8918
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Apr 13 18:26:29 2017 +0200

    rpm: the regression-tests sub-package needs "bc"
    
    split-brain-favorite-child-policy.t runs "bc" for comparing times in
    nanosecond precision. The glusterfs-regression-tests sub-package can be
    used to install environments for testing, but "bc" is not installed.
    This causes test failures.
    
    BUG: 1442145
    Change-Id: Iaf9dcb3a8488dea7162873ee40ae445843a35d04
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17060
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 090c8866eb3ae174be50dec8d9d5ecf978d18a45
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 13 13:20:18 2017 +0530

    glusterd: fix glusterd_wait_for_blockers to go in infinite loop
    
    In send_attach_req () conf->blockers is bumped up before
    rpc_clnt_submit however the same is bumped down twice, one from the
    callback and one from the negative ret handling which can very well be a
    possible case if the rpc submit fails.
    
    Change-Id: Icb820694034cbfcb3d427911e192ac4a0f4540f6
    BUG: 1441910
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17055
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit af218797fa98f2f75594fc9ae595f184682f1a0d
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Apr 13 16:44:44 2017 +0530

    dht: Add missing braces in dht_opendir
    
    Change-Id: I6adce98f52e17953f501bc590ff7189cceac3c31
    BUG: 1431908
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17057
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c2ea4463ab4ce04936a824f7e8c7c133aabe1381
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Apr 11 17:27:17 2017 +0530

    cluster/dht: Make rebalance honor min-free-disk
    
    test:  Manual
    
    created files of size 1K on 2 brick(of size 1GB) setup .
    added a brick of size 16GB.
    set min-free-disk to 12GB(so that first two bricks won't receive any files).
    removed one of the 1st brick of size 1GB.
    
    Logs from test:
    [2017-04-12 08:52:08.196484] W [MSGID: 0] [dht-rebalance.c:895:__dht_check_free_space]
     0-test1-dht: Write will cross min-free-disk for file - /tile32 on subvol - test1-client-1.
    Looking for new subvol.
    
    [2017-04-12 08:52:08.196904] I [MSGID: 0] [dht-rebalance.c:925:__dht_check_free_space]
    0-test1-dht: new target found - test1-client-2 for file - /tile32
    
     - Post migration we have two files. The new destination (/brick/1) has the data file
    [root@vm1 ~]# ll /brick/1/tile32
    -rw-r--r--. 2 root root 0 Apr 12 14:22 /brick/1/tile32
    
     - On the old target the linkto file is there with linkto xattr pointing to /brick/1
    [root@vm1 ~]# ll /tmp/2/tile32
    ---------T. 2 root root 1000 Apr 12 14:22 /tmp/2/tile32
    [root@vm1 ~]# getfattr -m . -de text /tmp/2/tile32
    getfattr: Removing leading '/' from absolute path names
    security.selinux="unconfined_u:object_r:user_tmp_t:s0"
    trusted.gfid="����:Aс�#�/'b2"
    trusted.glusterfs.dht.linkto="test1-client-2"
    
    Marking ./tests/features/worm_sh.t as bad test.
    Reason being, this patch failed on master branch as well and it has nothing
    to do with rebalance/remove-brick.
    
    BUG: 1441508
    Change-Id: I90bae251cda3d957a49cdceda90cd08311a392fb
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/17034
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 94afe2ca98a8ed9effb05901fc89d3b7bb6d0d41
Author: Prashanth Pai <ppai@redhat.com>
Date:   Mon Dec 19 16:28:06 2016 +0530

    glusterd: Propagate EADDRINUSE correctly to parent process
    
    exit()/_exit():
    Only the least significant 8 bits i.e (err & 255) shall be available
    to the waiting parent process on calling _exit() or exit() with an
    integer exit status. If this number is negative, the parent process
    doesn't readily get what it's really looking forward to handle.
    
    For example: EADDRINUSE is 98 and if exit status code is set to -98,
    the waiting parent process shall get 158 (= -98 & 255) as exit status.
    
    BUG: 1193929
    
    Change-Id: Idc6b0f40c2332e087e584b4b40cbf0d29168c9cd
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: https://review.gluster.org/16200
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit b4beaa0505e8b23ac027fb6c995aa259c3f7550a
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Wed Apr 5 18:03:10 2017 +0530

    glusterd: Add client details to get-state output
    
    This commit optionally adds client details corresponding to the
    locally running bricks to the get-state output. Since getting
    the client details involves sending RPC requests to the respective
    local bricks, this is a relatively more costly operation. These
    client details would be added to the get-state output only if the
    get-state command is invoked with the 'detail' option.
    
    This commit therefore also changes the get-state CLI usage. The
    modified usage is as follows:
    
     # gluster get-state [<daemon>] [[odir </path/to/output/dir/>] \
    [file <filename>]] [detail]
    
    Change-Id: I42cd4ef160f9e96d55a08a10d32c8ba44e4cd3d8
    BUG: 1431183
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/17003
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit e536bea09aa0776164716f9a0d480584c0a761f2
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Apr 5 17:13:25 2017 +0530

    cluster/ec : Don't count healing brick as healthy brick
    
    In ec_child_select, we should send fop on healing bricks
    unconditionaly but to check  the number of healthy bricks
    against fragments and minimum count, we should not count
    these healing bricks.
    
    Count bits of fop->mask before adding ealing brick to
    fop->mask
    
    Change-Id: I3fa80bdd5ca34ca070d610116b84154b917c5999
    BUG: 1439527
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/17007
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1b01bdcc8effb9b5342edbe669b9e2b2c36bfc80
Author: David Spisla <david.spisla@iternity.com>
Date:   Fri Feb 17 13:06:44 2017 +0100

    worm: allow Self-heal-Daemon to perform some operations
    
    The Self-Heal-Daemon should be allowed to trigger unlink, link,
    trauncate, rename and write operation. The value of frame->root->pid
    can be used to detect internal (by SHD) operations.
    
    Change-Id: I7526148100bef1e2837d69df5c119dc97d91fffd
    BUG: 1423413
    Signed-off-by: David Spisla <david.spisla@iternity.com>
    Reviewed-on: https://review.gluster.org/16661
    Tested-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 6b8df081b46ac4f485c86a5052fc30472e74bfbb
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Apr 11 12:30:06 2017 +0530

    rpc: add options to manage socket keepalive lifespan
    
    Problem:
    Default values for handling socket timeouts for brick responses are
    insufficient for aggressive applications such as databases.
    
    Solution:
    Add 1:1 gluster options for keepalive, keepalive-idle,
    keepalive-interval and keepalive-timeout as per the socket level options
    available as per tcp(7) man page.
    
    Default values for options are NOT agressive and continue to be values
    which result in default timeout when only the keep alive option is
    turned on.
    
    These options are Linux specific and will not be applicable to the
    *BSDs.
    
    Change-Id: I2a08ecd949ca8ceb3e090d336ad634341e2dbf14
    BUG: 1426059
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/16731
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 1612355327fa5f86078b9dbcf7a38e4e0c63e205
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 11 09:25:48 2017 +0530

    tests: remove tests/bugs/core/bug-1421590-brick-mux-reuse-ports.t
    
    bug-1421590-brick-mux-reuse-ports.t seems to be a bad test to me and here is my
    reasoning:
    
    This test tries to check if the ports are reused or not. When a volume is
    restarted, by the time glusterd tries to allocate a new port to the one of the
    brick processes of the volume there is no guarantee that the older port will be
    allocated given the kernel might take some extra time to free up the port between
    this time frame. From
    https://build.gluster.org/job/regression-test-burn-in/2932/console we can
    clearly see that post restart of the volume, glusterd allocated port 49153 &
    49155 for brick1 & brick2 respectively but the test was expecting the ports to
    be matched with 49155 & 49156 which were allocated before the volume was
    restarted.
    
    Change-Id: Id887bf28445261d4de04fc7502e58057659c9512
    BUG: 1441035
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/17033
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 10a797c26f0e9db33b2b5b89263f6cca3709c002
Author: Kevin Vigor <kvigor@fb.com>
Date:   Tue Mar 29 14:08:38 2016 -0700

    nfs: Fix compiler warning when calling svc_getcaller
    
    Summary:
    When using libtirpc instead of glibc rpc the result needs to be
    cast to (struct sockaddr_in *)
    
    This diff was originally a cherry-pick of D3111554 to 3.8
    
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Change-Id: If4c27dbe6c032f9e278ea08cd3c96a4d07bcc5f9
    BUG: 1428073
    Reviewed-on: http://review.gluster.org/16179
    Tested-by: Shreyas Siravara <sshreyas@fb.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kevin Vigor <kvigor@fb.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-on: https://review.gluster.org/16804
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 78c4e657dc2e122b00f99912819357c85e35d54d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 10 11:02:41 2017 +0200

    gfapi: remove unneeded NULL-check in glfs_fsync_async_common()
    
    Coverity reported that "glfd" has a NULL-check at the end of the
    function, but is used without checking earlier. Because "glfd" is passed
    as parameter to the (internal) function, there is no need to have the
    additional NULL-check.
    
    Change-Id: I1390b2ef250fbf624f0bc2b0eda7b7588942aae9
    BUG: 789278
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17026
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 594a7c6a187cf780bd666e7343c39a2d92fc67ef
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Apr 10 11:04:31 2017 +0530

    features/shard: Initialize local->fop in readv
    
    Change-Id: I9008ca9960df4821636501ae84f93a68f370c67f
    BUG: 1440051
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17014
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fddf202af078f09cf443fe76f8f43ad8eda2b4b6
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Fri Jul 8 19:10:45 2016 +0530

    geo-rep: filter out xtime attribute during getxattr
    
    georep gsyncd's xtime needs to filtered irrespective
    of any process access.
    
    This way, we can avoid (unnecessarily)syncing xtime attribute
    to slave, which may raise permission denied errors.
    
    test case modified to check for xtime xattr only in backend.
    
    Change-Id: I2390b703048d5cc747d91fa2ae884dc55de58669
    BUG: 1353952
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/14880
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c002b3d76486128ba78328b4a96ae0a1d8fe9cd0
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Apr 6 16:36:29 2017 +0530

    glusterd: Add validation for options rda-cache-limit rda-request-size
    
    Currently when prarallel readdir is enabled, setting any junk value
    to rda-cache-limit and rda-request-size succeeds. This is because of
    bug in the special handling of these options.
    
    Fixing the same in this patch
    
    Change-Id: I902cd9ac9134c158ab6f8aea4b001254a03547bd
    BUG: 1439640
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/17008
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b9b32f8363de1895a0cb144b6a641ed61eadade8
Author: AnkitRaj <anraj@redhat.com>
Date:   Fri Mar 31 10:55:41 2017 +0530

    DHT: Spacing issue in fix-layout status output
    
    There is a spacing issue in the status output of the rebalance
    fix-layout operations. If the local host name is big then we will
    have spacing issue.
    To fix this we need to increase the space for node column.
    
    Change-Id: Ic22e8017b55b05680db851a81f9b43c20489db79
    BUG: 1437748
    Signed-off-by: ankit <anraj@redhat.com>
    Signed-off-by: AnkitRaj <anraj@redhat.com>
    Reviewed-on: https://review.gluster.org/16972
    Tested-by: ankitraj
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 88551d8567503b3eba17e54fbe7dd9ee6266c1ab
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 10 10:10:30 2017 +0200

    upcall: correct the cleanup path in init() when GF_CALLOC() fails
    
    Coverity found that "priv" can be NULL when the 1st GF_CALLOC() fails,
    and still is being used with "priv->xattrs" before the functon returns.
    
    While cleaning this up, also removing the log message for out of memory,
    as this is already logged through GF_CALLOC().
    
    BUG: 789278
    Change-Id: I887eaa9136dc25a39c107cd2152b1ba11f9fa925
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17023
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 3594f960a8b5ccf81b6d06c89003f175ddd6a2c8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Apr 6 15:11:00 2017 +0200

    io-stats: use gf_atomic_t instead of partial atomic variables
    
    io-stats should not use the legacy __sync_*() builtin functions for
    doing atomic operations. Instead, it should use the gf_atomic_t type and
    macros for any of the statistics it calculates. This makes sure that the
    behaviour is the same on all architectures.
    
    Also the __sync_*() builtins are being deprecated with __atomic_*()
    functions. The "atomic.h" header will be one of the very few places
    where these builtin functions are used and the feature checking will be
    needed.
    
    While replacing many of the uint64_t types, it seemed that locking
    around some of the statements is not needed anymore (done automatically
    with the GF_ATOMIC_*() macros). This resulted in quite some removal and
    cleanup of those BUMP_*() macros. It seemed appropriate to make these
    macros normal functions and let the compiler decide on inlining them.
    This caused some existing functions to be shuffled around.
    
    Change-Id: I7c4f3df1832eae51debda2b127b943e14546b605
    URL: https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html
    BUG: 1437037
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17009
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit ec0e1176d476ef5765efe7713ce6a57f2f081722
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Apr 7 13:02:08 2017 +0200

    mem-pool: use gf_atomic_t for atomic counters
    
    Reduce the usage of __sync_fetch_and_add() builtins in mem-pool. The new
    gf_atomic_t type can be used instead, so that the architecture and
    compiler specific builtins are hidden from the mem-pool implementation.
    
    BUG: 1437037
    Change-Id: Icbeeb187dd2b835b35f32f54f821ceddfc7b2638
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/17012
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 44b1a68bc9bc1605d208d50fbafae85967085e58
Author: hari gowtham <hgowtham@redhat.com>
Date:   Fri Feb 10 13:00:16 2017 +0530

    TIER/TESTS: improving regression test for tier
    
    The test files that were marked as bad test were checked and
    updated for centos. The tests that had issue were fixed.
    Tests that aren't needed anymore are removed.
    
    REASON:
    
    tests/basic/tier/tier-file-create.t
    This test checks one line after creating a tiered volume (which
    is done in every tier test). So this line is moved along with
    other test in tier and the file is deleted.
    
    tests/bugs/tier/bug-1286974.t
    This bug checks for the tier as a task and tier has been moved
    from a task to service as a part of the tier as a service patch
    https://review.gluster.org/#/c/13365/
    So it is removed from bad tests.
    
    tests/basic/tier/record-metadata-heat.t
    This test had a bug and has been fixed.
    
    tests/basic/tier/bug-1214222-directories_missing_after_attach_tier.t
    tests/basic/tier/fops-during-migration.t
    tests/basic/tier/tier-snapshot.t
    tests/basic/tier/tier_lookup_heal.t
    
    These test seem to work fine on centos now.
    
    Change-Id: I05537f4bbb91584410177ce43543897eff8761a1
    BUG: 1421600
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/16605
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 788def7912c68616849748678574c60a52021e3c
Author: Shyam <srangana@redhat.com>
Date:   Wed Apr 5 14:22:57 2017 -0400

    scripts: Update rfc.sh to check existance of Change-Id in backports
    
    Addition to this script is a no-op on master.
    
    This would need to be backported to active release branches to be
    effective.
    
    This check is not smart proof, in that someone could proceed knowing
    that the Change-Id differs from master, but this is not expected to
    catch that, instead it is to serve more as a reminder that we need
    the same Change-Id across branches.
    
    Contributors not using rfc.sh would not see this, but they are few
    and possibly far in between. Also contributors using gerrit to
    cherry-pick changes will not see this. For both cases a server side
    solution to catch any changes are needed.
    
    There is a possiblilty that we will follow this up with a check
    on the gerrit end and add a comment to the reviews, to aid reviewers
    to quickly check the sanity of the Change-Id when it differs.
    
    Change-Id: I11e371489a4a3cf2ff96d9892256986cd535998b
    BUG: 1428047
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: https://review.gluster.org/17004
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b1764275341884e12ff3186681d6718f98e1096f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 7 05:33:34 2017 -0400

    geo-rep: Fix EBUSY traceback
    
    EBUSY was added to retry list of errno_wrap
    without importing. Fixing the same.
    
    Change-Id: Ide81a9ccc9b948a96265b6890da078b722b45d51
    BUG: 1434018
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/17011
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit c7ba4b2b1a1cca6f217083ff9c1f01f23c9ca171
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Mar 30 14:45:59 2017 +0530

    cli/auth : auth.allow and auth.reject does not accept FQDN/host name
    
    Problem : At the time of set FQDN name to "auth.allow/auth.reject" through
               gluster cli,it does not accept FQDN/host name.
    
    Solution: Condition needs to be update in verify_host_name and gf_auth
               to accept FQDN/host name.
    
    Fix : Change the condition to accept FQDN/host Name.
          To verify the patch followed below procedure
          1) Try to set FQDN name for auth.allow or auth.reject parameter
             gluster v set myvol auth.reject <fqdn name>
             It gives error "fqdn-name" is not a valid internet-address-list
          2) After apply the patch it does not give any error.
          3) To verify auth.allow/reject try to mount volume on some client.
    
    Change-Id: Ieb76cbb93d43323fd29c7ca04efe3790edb4281b
    BUG: 1321578
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/15086
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 656bf04955936319de4b8711debcc9931a7c778e
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Nov 7 12:00:13 2016 +0530

    dht/rebalance: Crawler performance improvement
    
     The job of the crawler in rebalance is to fetch files from each
    local subvolume and push them to migration queue if it is eligible for
    migration. And we do a lookup on the entries received to figure out the
    eligibilty. Since, the lookup done is on a local subvolume we receive
    linkto files and regular files as well. This requires us to do two lookups.
    
    first: do a lookup on the file to figure out whether it is a linkto file
    second: do a lookup on the file to figure out if it should be migrated
    
    Note: The migrator thread also does one lookup for the file before
    migration.
    
    Optimization: Remove the lookup done by the crawler. Offload these task
    to the migrator threads. For linkto file verification get the stat and
    xattr information from readdirp.
    
    So in total we have one lookup instead of three for each entry.
    
    Performance numbers:
    Create two node, two brick setup. Created 100000 files. And started
    rebalance. Since, there is no add-brick, no files will be migrated and
    we will get the crawler performance.
    
    Without patch:
    [root@gprfs039 ~]# grs
                                        Node Rebalanced-files          size
    scanned      failures       skipped               status  run time in
    h:m:s
                                   ---------      -----------   -----------
    -----------   -----------   -----------         ------------
    --------------
                                   localhost                0        0Bytes
    50070             0             0            completed        0:0:48
                                server2                0        0Bytes
    49930             0             0            completed        0:0:44
    volume rebalance: test1: success
    
    Total: 48 seconds
    
    WiththecurrentPatch:
    [root@gprfs039 mnt]# gluster v rebalance test1 status
                                        Node Rebalanced-files          size
    scanned      failures       skipped               status  run time in
    h:m:s
                                   ---------      -----------   -----------
    -----------   -----------   -----------         ------------
    --------------
                                   localhost                0        0Bytes
    50070             0             0            completed        0:0:12
                                server2                0        0Bytes
    49930             0             0            completed        0:0:12
    volume rebalance: test1: success
    
    Total: 12 seconds
    
    That's 4X speed gain. :)
    
    Updates glusterfs#155
    Change-Id: Idc8e5b366e76c54aa40d698876ae62fe1630b6cc
    BUG: 1439571
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/15781
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5512a5723ad22dd099a57c60483eb80e5b2a14c4
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Jan 20 15:29:05 2017 -0500

    tests: track EW_RETRIES for debugging
    
    It can often be useful while debugging to know how many times
    EXPECT_WITHIN had to retry a command before it got the result we were
    looking for.  This patch just adds a variable EW_RETRIES that can be
    inspected to find this info for the last EXPECT_WITHIN.
    
    Change-Id: I1bcb09bb7eb118c3d76c60317ef99e02df6b6ee6
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16451
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 99c8c0b03a3368d81756440ab48091e1f2430a5f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 6 18:10:41 2017 +0530

    features/shard: Fix vm corruption upon fix-layout
    
    shard's writev implementation, as part of identifying
    presence of participant shards that aren't in memory,
    first sends an MKNOD on these shards, and upon EEXIST error,
    looks up the shards before proceeding with the writes.
    
    The VM corruption was caused when the following happened:
    1. DHT had n subvolumes initially.
    2. Upon add-brick + fix-layout, the layout of .shard changed
       although the existing shards under it were yet to be migrated
       to their new hashed subvolumes.
    3. During this time, there were writes on the VM falling in regions
       of the file whose corresponding shards were already existing under
       .shard.
    4. Sharding xl sent MKNOD on these shards, now creating them in their
       new hashed subvolumes although there already exist shard blocks for
       this region with valid data.
    5. All subsequent writes were wound on these newly created copies.
    
    The net outcome is that both copies of the shard didn't have the correct
    data. This caused the affected VMs to be unbootable.
    
    FIX:
    For want of better alternatives in DHT, the fix changes shard fops to do
    a LOOKUP before the MKNOD and upon EEXIST error, perform another lookup.
    
    Change-Id: I8a2e97d91ba3275fbc7174a008c7234fa5295d36
    BUG: 1440051
    RCA'd-by: Raghavendra Gowdappa <rgowdapp@redhat.com>
    Reported-by: Mahdi Adnan <mahdi.adnan@outlook.com>
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/17010
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit ba892262ae7b34b0ba632c0306fcd5addff7d682
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Mar 24 10:16:34 2017 -0400

    fuse-bridge: fuse_getattr(): send root lookup() only in case of failure.
    
    this will make sure we don't fail in any current cases, and also will
    enable the performance better.
    
    Change-Id: Ia421e1913e1b00f0730a004bf7c84bf7e2a62636
    BUG: 1437780
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: https://review.gluster.org/16945
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ef36ac0d1b72ab2c07ed6e0a3116b7265c3c0164
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Feb 27 22:37:00 2017 -0800

    xlator: do not call dlclose() when debugging
    
    Valgrind can not show the symbols if a .so after calling dlclose(). The
    unhelpful ??? in the output gets resolved properly with this change:
    
      ==25170== 344 bytes in 1 blocks are definitely lost in loss record 233 of 324
      ==25170==    at 0x4C29975: calloc (vg_replace_malloc.c:711)
      ==25170==    by 0x52C7C0B: __gf_calloc (mem-pool.c:117)
      ==25170==    by 0x12B0638A: ???
      ==25170==    by 0x528FCE6: __xlator_init (xlator.c:472)
      ==25170==    by 0x528FE16: xlator_init (xlator.c:498)
      ==25170==    by 0x52DA8D6: glusterfs_graph_init (graph.c:321)
      ==25170==    by 0x52DB587: glusterfs_graph_activate (graph.c:695)
      ==25170==    by 0x5046407: glfs_process_volfp (glfs-mgmt.c:79)
      ==25170==    by 0x5043B9E: glfs_volumes_init (glfs.c:281)
      ==25170==    by 0x5044FEC: glfs_init_common (glfs.c:986)
      ==25170==    by 0x50451A7: glfs_init@@GFAPI_3.4.0 (glfs.c:1031)
    
    By not calling dlclose(), the dynamically loaded .so is still available
    upon program exit, and Valgrind is able to resolve the symbols. This
    will add an additional leak, so dlclose() is called for normal builds,
    but skipped when configuring with "./configure --enable-valgrind" or
    passing the "run-with-valgrind" xlator option.
    
    URL: http://valgrind.org/docs/manual/faq.html#faq.unhelpful
    Change-Id: I2044e21b1b8fcce32ad1a817fdd795218f967731
    BUG: 1425623
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16809
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 40e571339b3c19ab2a5b6a93bc46eadf2252d006
Author: Bipin Kunal <bkunal@redhat.com>
Date:   Mon Feb 27 15:23:04 2017 +0530

    nfs: make subdir mounting work for Solaris 10 clients
    
    This fixes the segfault caused by solaris client in Gluster/NFS.
    Volname was not being parsed properly, Instead of volume
    name complete path was being used in nfs_mntpath_to_xlator().
    Fixed it by striping volume name from complete path  in nfs_mntpath_to_xlator().
    
    Modified function name nfs3_funge_solaris_zerolen_fh() to
    nfs3_funge_webnfs_zerolen_fh() as zero-filled filehandle is specific to WebNFS.
    RFC : https://tools.ietf.org/html/rfc2055
    Solaris uses WebNFS, the zero-filled FH is defined in the WebNFS spec.
    
    Logic was even added in fuction nfs3_funge_webnfs_zerolen_fh() to send
    subdir path in function glfs_resolve_at() instead of complete path for
    subdir mount.
    
    Change-Id: I19aae3547b8910e7ed4974ee5385424cab3e834a
    BUG: 1426667
    Signed-off-by: Bipin Kunal <bkunal@redhat.com>
    Reviewed-on: https://review.gluster.org/16770
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e01025973c73e2bd0eda8cfed22b75617305d740
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 4 15:39:46 2017 -0400

    geo-rep: Improve worker log messages
    
    Monitor process expects worker to establish SSH Tunnel to slave node
    and mount master volume locally with in 60 secs and acknowledge monitor
    process by closing feedback fd. If something goes wrong and worker
    does not close feedback fd with in 60 secs, monitor kills the worker.
    But there was no clue in log message about the actual issue. This patch
    adds log and indicates whether the worker is hung during SSH
    or master mount.
    
    Change-Id: Id08a12fa6f3bba1d4fe8036728dbc290e6c14c8c
    BUG: 1261689
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/16997
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit cbcb1d33de8c4bd7250a5c038e8f95456772add1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 20 05:21:59 2017 -0400

    geo-rep: Retry on EBUSY
    
    Do not crash on EBUSY error. Add EBUSY
    retry errno list. Crash only if the error
    persists even after max retries.
    
    Change-Id: Ia067ccc6547731f28f2a315d400705e616cbf662
    BUG: 1434018
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/16924
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c932c0df4b70abaa85354e56efe6f1ce88ce4a38
Author: Michael Scherer <misc@redhat.com>
Date:   Thu Feb 23 21:26:33 2017 +0100

    shared: simplify and fix crash when we run out of memory
    
    Since mem_get0 can return NULL, local->op_ret is gonna
    crash. Found by coverity. And since we only have ENOMEM
    as potential error, we can also simplify the code by avoiding
    using 'local' for that.
    
    Change-Id: I778747b57f520b1a52347c0fc9f27efd7a7c5ca0
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16739
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0f71338e1d7c0b70f4fe3b19c68612fe730d9de2
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Mar 15 10:26:28 2017 +0530

    dht: The xattrs sent in readdirp should be sent in opendir aswell
    
    As readdir-ahead can be loaded as a child of dht, dht has to specify
    the xattrs it is intrested in, as part of opendir call itself.
    
    Change-Id: I012ef96cc143b0cef942df78aa7150d85ec38606
    BUG: 1431908
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16902
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 93e3c9abce1a02ac724afa382751852fa5edf713
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Mar 29 13:44:03 2017 +0200

    libglusterfs: provide standardized atomic operations
    
    The current macros ATOMIC_INCREMENT() and ATOMIC_DECREMENT() expect a
    lock as first argument. There are at least two issues with this
    approach:
    
      1. this lock is unused on architectures that have atomic operations
      2. some structures use a single lock for multiple variables
    
    By defining a gf_atomic_t type, the unused lock can be removed, saving a
    few bytes on modern architectures.
    
    Because the gf_atomic_t type locates the lock for the variable (in case
    of older architectures), each variable is protected the same on all
    architectures. This makes the behaviour across all architectures more
    equal (per variable locking, by a gf_lock_t or compiler optimization).
    
    BUG: 1437037
    Change-Id: Ic164892b06ea676e6a9566f8a98b7faf0efe76d6
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16963
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d6b88e9b8b02813620c3c1a2ea49d58d29062b3e
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Apr 4 20:28:07 2017 +0530

    explicitly specify executor to be bash for tests
    
    We use prove command to run tests. Sometimes tests fail rather strangely
    with error as shown below:
    
    Not a perl script at ./tests/bugs/core/bug-1111557.t line 1.
    ./tests/bugs/core/bug-1111557.t ..
    Dubious, test returned 25 (wstat 6400, 0x1900)
    No subtests run
    
    https://build.gluster.org/job/centos6-regression/3818/consoleFull
    https://build.gluster.org/job/centos6-regression/3819/consoleFull
    https://build.gluster.org/job/centos6-regression/3801/consoleFull
    
    Quote from man page
    
    ``
     "--exec"
           Normally you can just pass a list of Perl tests and the harness
    will know how to execute them.  However, if your tests are not written in Perl
    or if you want all tests invoked exactly the same way, use the "-e",
    or "--exec" switch:
    
            prove --exec '/usr/bin/ruby -w' t/
    ```
    
    Hence, better to comply with recommended practice although it might not
    be the reason for this failure.
    
    Change-Id: If7a0baf20698f8497ef3e8fc422fa67063a4651f
    BUG: 1438858
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: https://review.gluster.org/16996
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Nigel Babu <nigelb@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit c5a4a77848024d2adf8cd4f35d550ba90c174fc7
Author: karthik-us <ksubrahm@redhat.com>
Date:   Tue Apr 4 18:57:32 2017 +0530

    features/worm: Adding implementation for ftruncate
    
    Problem:
    Since the ftruncate fop was not handled in the worm feature, when
    truncate and write was happening on a worm-retained/worm file, it was
    giving the EROFS error but truncating the file, which is not correct.
    
    Change-Id: I1a7e904655210d78bce9e01652ac56f3783b5aed
    BUG: 1438810
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: https://review.gluster.org/16995
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 61f76f318faed395660f5bbcfe39616b39c158f0
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Mar 27 11:38:28 2017 +0530

    reddir-ahead: Fix EOD propagation problem
    
    In readdirp fop, op_errno is overloaded to indicate the EOD detection.
    If op_errno contains ENOENT, then it indicates that there are no
    further entries pending read in the directory. Currently NFS uses the
    ENOENT to identify the EOD.
    
    Issue:
    NFS clients issues a 4K buffer for readdirp, readdir-ahead converts it
    to 128K buffer as its reading ahead. If there are 100 entries in the
    bricks, 128K can get all 100 and store in readdir-ahead, but only 23
    entries that can be fit in 4K will be sent to NFS. Since the whole
    100 entries were read from brick, the op_errno is set to ENOENT, and
    the op_errno is propagated as is when sent to NFS. Hence NFS client
    in reading 23 entries thinks it reached EOD.
    
    Solution:
    Do not propogate ENOENT errno, unless all the entries are read
    from the readdir ahead buffer.
    
    Change-Id: I4f173a77b21ab9e98ae35e291a45b8fc0cde65bd
    BUG: 1436086
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16953
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1063efeb2275039a75eb6fe5e423845e28098df2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 4 07:35:52 2017 -0400

    build: clang has __builtin_popcount() and __builtin_ffs()
    
    Note: Even though gcc(1) will automatically treat ffs() and popcount()
    as built-in, calling them explicitly as __builtin in the source helps
    make it easier to find them. (And if no __builtin_ffs use the one in
    libc.)
    
    Change-Id: Ib74d9b221ff03a01df5ad05907024da1a83a7a88
    BUG: 1438772
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16993
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 6b069086cbee39aec9da77b1831e88fe85258b0f
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Mon Mar 6 12:36:02 2017 +0530

    Fixes Stale auxiliary mount when crawler fails to spawn
    
    The auxiliary mount created for crawling remains if the crawler was not
    successfully spawned due to transport disconnect or other such issues.
    The patch ensures the mount is cleared in those code paths as well.
    
    Change-Id: I659fcc1d1956f8e05a37b75ebe3f3a00c24693e8
    BUG: 1429330
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Reviewed-on: https://review.gluster.org/16853
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333@gmail.com>

commit 7a49a4a6e3e2224afea7a961fbee9a460b9d58a0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Apr 4 12:55:27 2017 +0200

    build: place generated XDR .h and .c files under $(top_builddir)
    
    Change-Id: I0487337223a54a52e73088cb6dd812ce6d47178d
    BUG: 1429696
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16994
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Tested-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b75fa35694af916e0923f10e4f9491c364a4ba79
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 30 14:58:38 2017 +0530

    cluster/dht: Modify local->loc.gfid in thread safe manner
    
    Problem:
    local->loc.gfid in dht_lookup_directory() will be null-gfid for a fresh lookup.
    dht_lookup_dir_cbk() updates local->loc.gfid while in other thread dht_lookup_directory()
    is still winding lookup calls to subvolumes so there is a chance of partial gfid being
    seen by EC.
    
    We saw in 12x(4+2) volume, ec is receiving an loc where the gfid has last 10 bytes matching
    with the gfid of the directory and the first 4 bytes are all-zeros. This is leading to EC
    erroring out the lookup with EINVAL which leads to NFS failing lookup with EIO.
    
    snip from gdb:
    $37 = (dht_local_t *) 0x7fde5de5b3cc
    (gdb) p /x $37->loc.gfid
    $39 = {0x3b, 0x82, 0x10, 0x5e, 0x40, 0x65, 0x43, 0x14, 0xa0, 0xc6, 0x8, 0xf5,
    0x6c, 0x2c, 0xb8, 0x56}
    (gdb) fr 7
    state=<optimized out>) at ec-generic.c:837
    837	                ec_lookup_rebuild(fop->xl->private, fop, cbk);
    (gdb) p /x fop->loc[0].gfid
    $40 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x43, 0x14, 0xa0, 0xc6, 0x8, 0xf5, 0x6c,
    0x2c, 0xb8, 0x56}
    
    snip from log:
    [2017-01-29 03:22:30.132328] W [MSGID: 122019]
    [ec-helpers.c:354:ec_loc_gfid_check] 0-butcher-disperse-4: Mismatching GFID's
    in loc [2017-01-29 03:22:30.132709] W [MSGID: 112199]
    [nfs3-helpers.c:3515:nfs3_log_newfh_res] 0-nfs-nfsv3:
    /linux-4.9.5/Documentation => (XID: b27b9474, MKDIR: NFS: 5(I/O error), POSIX:
    5(Input/output error)), FH: exportid 00000000-0000-0000-0000-000000000000, gfid
    00000000-0000-0000-0000-000000000000, mountid
    00000000-0000-0000-0000-000000000000 [Invalid argument]
    
    Fix:
    update local->loc.gfid in last-call to make sure there are no races.
    
    BUG: 1438411
    Change-Id: Ifcb7e911568c1f1f83123da6ff0cf742b91800a0
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16986
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit cdddb819b964eff0268498e8bfa0e67c77782094
Author: Patrick Matthäi <pmatthaei@debian.org>
Date:   Fri Mar 31 12:27:20 2017 +0200

    build: miscellaneous spelling fixes
    
    Debian builds detected spelling issues with GlusterFS 3.10.1. Instead of
    carrying the patch in the Debian sources, let's include the fixes here
    too.
    
    Change-Id: I38db6adf142f7ec247bffd47aa1e6ff1a0c49e00
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    BUG: 1437853
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16973
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 64fc3505c426d1ff9fc16f065a81556e96ed93b7
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Wed Mar 29 11:40:43 2017 +0800

    protocol: corect parameter state->size in server3_3_writev
    
    Change-Id: I1a3d558670e4320fe8508b5ab97deff9aacca5c7
    BUG: 1436936
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: https://review.gluster.org/16962
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 1c92f83ec041176ad7c42ef83525cda7d3eda3c5
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Thu Mar 16 14:56:39 2017 +0530

    glusterd : Disallow peer detach if snapshot bricks exist on it
    
    Problem :
    - Deploy gluster on 2 nodes, one brick each, one volume replicated
    - Create a snapshot
    - Lose one server
    - Add a replacement peer and new brick with a new IP address
    - replace-brick the missing brick onto the new server
      (wait for replication to finish)
    - peer detach the old server
    - after doing above steps, glusterd fails to restart.
    
    Solution:
      With the fix detach peer will populate an error : "N2 is part of
      existing snapshots. Remove those snapshots before proceeding".
      While doing so we force user to stay with that peer or to delete
      all snapshots.
    
    Change-Id: I3699afb9b2a5f915768b77f885e783bd9b51818c
    BUG: 1322145
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/16907
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4c3aa910e7913c34db24f864a33dfb6d1e0234a4
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Feb 14 17:50:27 2017 +0100

    libglusterfs: add dict_rename_key()
    
    The dict_rename_key() function will be used for converting the
    "security.selinux" xattr to "trusted.gluster.selinux" in the upcoming
    SELinux xlator.
    
    BUG: 1318100
    Change-Id: Ic5d0b9127e2c360d355f02e200a820597e83fa2c
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    [ndevos: split from change Id8916bd8e064ccf74ba86225ead95f86dc5a1a25]
    Reviewed-on: https://review.gluster.org/16616
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit e325479cf222d2f25dbc0a4c6b80bfe5a7f09f43
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Mar 30 14:47:45 2017 +0530

    glusterd: reset pid to -1 if brick is not online
    
    While populating brick details in gluster volume status response payload
    if a brick is not online then pid should be reset back to -1 so that
    volume status output doesn't show up the pid which was not cleaned up
    especially with brick multiplexing where multiple bricks belong to same
    process.
    
    Change-Id: Iba346da9a8cb5b5f5dd38031d4c5ef2097808387
    BUG: 1437494
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16971
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit a7ce0548b7969050644891cd90c0bf134fa1594c
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Mar 20 12:32:33 2017 -0400

    glusterd: hold off volume deletes while still restarting bricks
    
    We need to do this because modifying the volume/brick tree while
    glusterd_restart_bricks is still walking it can lead to segfaults.
    Without waiting we could accidentally "slip in" while attach_brick has
    released big_lock between retries and make such a modification.
    
    Change-Id: I30ccc4efa8d286aae847250f5d4fb28956a74b03
    BUG: 1432542
    Signed-off-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-on: https://review.gluster.org/16927
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ed89f3ef064b6100bb0731f2493d915f6fb141c3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 30 11:45:43 2017 +0200

    build: add copied .x files to .gitignore
    
    The new rpc/xdr/gen/ directiry contains copies of the .x files from
    rpc/xdr/src/. This is needed to generate the headers for the cyclic
    dependency for libglusterfs <-> rpc. These files should never be
    included in the git repository, so adding them to .gitignore.
    
    BUG: 1429696
    Change-Id: Ia9dd104853e2dbde49b368169dc15c465dff0323
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16969
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit dd5ada1f11d76b4c55c7c55d23718617f11a6c12
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 28 19:26:41 2017 +0530

    features/shard: Pass the correct iatt for cache invalidation
    
    This fixes a performance issue with shard which was causing
    the translator to trigger unusually high number of lookups
    for cache invalidation even when there was no modification to
    the file.
    
    In shard_common_stat_cbk(), it is local->prebuf that contains the
    aggregated size and block count as opposed to buf which only holds the
    attributes for the physical copy of base shard. Passing buf for
    inode_ctx invalidation would always set refresh to true since the file
    size in inode ctx contains the aggregated size and would never be same
    as @buf->ia_size. This was leading to every write/read being preceded
    by a lookup on the base shard even when the file underwent no
    modification.
    
    Change-Id: Ib0349291d2d01f3782d6d0bdd90c6db5e0609210
    BUG: 1436739
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16961
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0bd58241143e91b683a3e5c4335aabf9eed537fe
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Mar 20 05:15:25 2017 +0530

    protocol : fix auth-allow regression
    
    One of the brick multiplexing patches (commit 1a95fc3) had some changes
    in gf_auth () & server_setvolume () functions which caused auth-allow
    feature to be broken. mount doesn't succeed even if it's part of the
    auth-allow list. This fix does the following:
    
    1. Reintroduce the peer-info data back in gf_auth () so that fnmatch has
    valid input and it can decide on the result.
    
    2. config-params dict should capture key values pairs for all the bricks
    in case brick multiplexing is on. In case brick multiplexing isn't
    enabled, then config-params should carry attributes from protocol/server
    such that all rpc auth related attributes stay in tact in the
    dictionary.
    
    Change-Id: I007c4c6d78620a896b8858a29459a77de8b52412
    BUG: 1433815
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16920
    Tested-by: Jeff Darcy <jeff@pl.atyp.us>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>

commit 57341d25db8b16e8a1fc7d40f6f56b5200f3547d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Mar 27 08:35:51 2017 -0400

    build: errors generating xdr stubs+headers with `make -j`
    
    Using a makebomb, on f23 at least, blows up when generating the
    xdr headers and stubs. (Works reliably on f25 though, go figure.)
    This change appears to mitigate the race on f23.
    
    BUG: 1429696
    Change-Id: Icca2de035255a7759563bf06d853950dddc5724d
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16954
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 0f98f5c8070904810252c6fc1df23747afa4b1d7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Mar 21 11:02:32 2017 +0530

    syncop:  don't wake task in synctask_wake unless really needed
    
    Problem:
    
    In EC and AFR, we launch synctasks during self-heal.
    
    (i) These tasks usually stackwind a FOP to all its children and call
    synctask_yield() which does a swapcontext to synctask_switchto() and puts the
    task in syncenv's waitq by calling __wait(task). This happends as long as the
    FOP ckbs from all children haven't been received.
    
    (ii) For each FOP cbk, we call synctask_wake() which again does a swapcontext
    to synctask_switchto() which now puts the task in syncenv's runq by calling
    __run(task). When the task runs and the conext switches back to the FOP path,
    it puts the task in waitq because we haven't heard from all children as
    explained in (i).
    
    Thus we are unnecessarily using the swapcontext syscalls to just toggle
    the task back and forth between the waitq and runq.
    
    Fix:
    Store the stackwind count in new variable 'syncbarrier->waitfor' before
    winding the fop. In each cbk when we call synctask_wake(),  perform an actual
    wake only if the cbk count == stackwind count.
    
    Change-Id: Id62d3b6ffed5a8c50f8b79267fb34e9470ba5ed5
    BUG: 1434274
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/16931
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit df189a8644d7a805bb3e278f61983c5ba8619188
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 27 07:19:57 2017 +0530

    syncop: Fix args for makecontext
    
    Passing 64bit arguments to makecontext is not portable and manpage says the following:
    
    <snip>
    On  architectures where int and pointer types are the same size (e.g., x86-32, where
    both types are 32 bits), you may be able to get away with passing pointers as  argu‐
    ments  to makecontext() following argc.  However, doing this is not guaranteed to be
    portable, is undefined according to the standards, and won't work  on  architectures
    where pointers are larger than ints.  Nevertheless, starting with version 2.8, glibc
    makes some changes to makecontext(), to permit this  on  some  64-bit  architectures
    (e.g., x86-64).
    </snip>
    
    Since we do not depend on the arguments, it is better to change makecontext to not
    take any arguments.
    
    BUG: 1434274
    Change-Id: Ic46c9e9faaeb2f78e4efde353ef861466515b1ec
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16951
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 12921693b572f642156d3167d1c92d3449dfc8ec
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Mar 7 18:01:25 2017 +0100

    glusterd: support filesystems with dynamic inode sizes
    
    btrfs and zfs are two filesystems that do not have fixed sizes for
    inodes. Instead of logging an error, skip checking and mark the size as
    "N/A" like other properties that can not be reported.
    
    The error message that was reported by users on the mailinglist shows up
    like:
    
      [glusterd-utils.c:5458:glusterd_add_inode_size_to_dict] 0-management: could not find (null) to getinode size for /dev/vdb (btrfs): (null) package missing?
    
    Change-Id: Ib10b7a3669f2f4221075715d9fd44ce1ffc35324
    Reported-by: Arman Khalatyan <arm2arm@gmail.com>
    URL: http://lists.gluster.org/pipermail/gluster-users/2017-March/030189.html
    BUG: 1433425
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16867
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 16cfe427397d5b8f7a66dfe0b86d9fa5b06de4c1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Mar 20 17:24:37 2017 -0400

    nfs: use pkill on all OS's
    
    'killall' is the only executable that is needed from the psmisc package
    on glusterfs-server installations. NetBSD already uses 'pkill' as
    alternative, this can be used everywhere.
    
    BUG: 1197308
    Change-Id: Ied671a74b735e321f52d99c869627b957aa2bd02
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16928
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b96da537f60d75f896973c9f61007baec42fcf17
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Mar 24 08:32:39 2017 -0400

    build: errors generating xdr stubs+headers with `make -j`
    
    Using a makebomb, on f23 at least, blows up when generating the
    xdr headers and stubs. (Works reliably on f25 though, go figure.)
    This change appears to mitigate the race on f23.
    
    Change-Id: I006066f0e7c3f8b65189f97c70089f3422e3e08b
    BUG: 1429696
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16941
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Anoop C S <anoopcs@redhat.com>

commit f91596e6566c605e70a31a60523d11f78a097c3c
Author: karthik-us <ksubrahm@redhat.com>
Date:   Sat Mar 18 13:44:56 2017 +0530

    cluster/afr: Undo pending xattrs only on the up bricks
    
    Problem:
    While doing conservative merge, even if a brick is down, it will reset
    the pending xattr on that. When that brick comes up, as part of the
    heal, it will consider this brick as the source and removes the entries
    on the other bricks, which leads to data loss.
    
    Fix:
    Undo pending only for the bricks which are up.
    
    Change-Id: I18436fa0bb1faa5f60531b357dea3f6b20446303
    BUG: 1433571
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: https://review.gluster.org/16913
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 6c14e55377cc0080da88c5b997f5f7ea2374393b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Mar 15 17:10:41 2017 +0530

    libglusterfs: Initialize old sigset
    
    ...in gf_thread_create(). Technically, since we pass it as an argument
    to pthread_sigmask, initialization is not needed but doing it as a good
    practice.
    
    Change-Id: Ie069af07cb07c1784f3841e1fc628ca13dfdcef4
    BUG: 1434274
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16929
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 98f602cd64e3f8cc7e4c4a7245e132c0afd7347f
Author: Poornima G <pgurusid@redhat.com>
Date:   Sun Mar 26 07:59:53 2017 +0530

    protocol-client: Initialize the list_head before using
    
    In client3_3_readdir(p)_cbk, in case of error conditions,
    it is possible that the list_head is used before initializing.
    Hence move the initialization before usage.
    
    Change-Id: Ie58902d079fdc58416d17b5fa5f61375decb1c99
    BUG: 1435943
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16948
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 31377765dbbb8d49292c4362837a695adcbc6cb4
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Mar 20 12:31:33 2017 -0400

    core: fix synclocks' handling of "woken" flag
    
    The "woken" flag wasn't being reset when it should have been, leading
    (eventually) to a SEGV when someone tried to folow a synclock's waitq
    to a task structure that had been freed while still on the queue.  See
    the bug report for (far) more detail.
    
    Change-Id: I5cd9ae1bcb831555274108b292181ec2a29b6d95
    BUG: 1434062
    Signed-off-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-on: https://review.gluster.org/16926
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a1d60fe4e9ba46e2f472170e65043f5735af1fd5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Mar 14 15:38:39 2017 +0100

    refcount: correct the return value of GF_REF_PUT()
    
    It is documented that GF_REF_PUT() returns a 0 in case the call resulted
    in free'ing the structure. However the implementations did not have a
    return value, so nothing can actually use it.
    
    Change-Id: Ic57091f5ddd7e0b80929dc335a5b6d37f5fe1b2e
    BUG: 1433405
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16910
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 0cf2963f12a8b540a7042605d8c79f638fdf6cee
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Feb 1 07:50:17 2017 -0500

    packaging: (ganesha) remove glusterfs-ganesha subpackage and related files)
    
    Indiana Jones and the Temple of Ganesha HA, part two.
    
    remove glsuterfs-ganesha subpackage, superceded by storhaug
    
    Change-Id: I42a1fc59159add108d77080b9b130696216aa76d
    BUG: 1418417
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16506
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 843e1b04b554ab887ec656ae7b468bb93ee4e2f7
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Feb 1 06:39:03 2017 -0500

    glusterd: (storhaug) remove ganesha
    
    remove all vestiges of ganesha
    
    The storhaug CLI is used to manage ganesha and Samba. Also any setup
    and teardown of the ganesha HA is initiated using storhaug to preserve
    the proper layering.
    
    Change-Id: I0eec0016a1b7802a36e7b2d92896b86fdf8607d5
    BUG: 1420713
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16504
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f21fd308fcfab6151e7c8f60642d8dfcbec0cc48
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Mar 8 14:44:50 2017 -0500

    build: libgfxdr.so calls GF_FREE(), needs to link with -lglusterfs
    
    The previous change to remove the xdrgen script exposed (or
    created) a recursive build dependency: libglusterfs needs the
    generated headers, and libgfxdr should be linked with libglusterfs
    for GF_FREE/__gf_free.
    
    (Much grumbling about libglusterfs being the kitchen sink of gluster
    elided. This would not be necessary if there were two or more libs,
    a gluster "runtime" library with common gluster code shared by the
    xlators and daemons, and a utility library with things like the
    rbtree, memory allocation, and whatnot.)
    
    So. Link at build time or link at runtime? For truth-and-beauty, link
    with libglusterfs.so at build time. Without truth-and-beauty, don't
    link with libglusterfs and rely on the other things that link with
    libglusterfs to provide resolution of __gf_free().
    
    Truth-and-beauty it is. But how to generate the headers first, then
    build libglusterfs, then come back and build libgfxdr? Autotools is a
    maze of twisty passages, all different. Things that work with gnu
    make on linux don't work with the BSD make. Finally I hit on this
    solution. Add a shadow directory where make only generates the headers,
    then build libglusterfs using the generated headers, and finally build
    libgfxdr and link with libglusterfs.
    
    See original BZ 1330604
    change http://review.gluster.org/14085
    
    Change-Id: Iede8a30e3103176cb8f0b054885f30fcb352492b
    BUG: 1429696
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16873
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 2f560dbc78360f0e7fa76a2dfdabd9c92d13e976
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Mar 15 17:18:54 2017 +0530

    syncop: fix argc count in call to makecontext()
    
    We are only passing one argument (a pointer to struct synctask) to the
    function, so argc must be 1 and not 2.
    
    Change-Id: I4eaadd58a76f32327d8bb3efa9c5c435700d7391
    BUG: 1434274
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16930
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 0c2253942dd0e6176918a7d530e56053a9f26e6d
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Mon Feb 27 15:35:17 2017 +0530

    cluster/ec: Metadata healing fails to update the version
    
    During meatadata heal, we were not updating the version
    though all the inode attributes were in sync.
    
    Updated the code to adjust version when all the inode
    attributes are in sync.
    
    BUG: 1425703
    Change-Id: I6723be3c5f748b286d4efdaf3c71e9d2087c7235
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/16772
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 39e09ad1e0e93f08153688c31433c38529f93716
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Mar 18 16:29:10 2017 +0530

    rpc: bump up conn->cleanup_gen in rpc_clnt_reconnect_cleanup
    
    Commit 086436a introduced generation number (cleanup_gen) to ensure that
    rpc layer doesn't end up cleaning up the connection object if
    application layer has already destroyed it. Bumping up cleanup_gen was
    done only in rpc_clnt_connection_cleanup (). However the same is needed
    in rpc_clnt_reconnect_cleanup () too as with out it if the object gets destroyed
    through the reconnect event in the application layer, rpc layer will
    still end up in trying to delete the object resulting into double free
    and crash.
    
    Peer probing an invalid host/IP was the basic test to catch this issue.
    
    Change-Id: Id5332f3239cb324cead34eb51cf73d426733bd46
    BUG: 1433578
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16914
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit d23790d9e2365a0663ed9452c49835133046d136
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sun Mar 19 17:09:06 2017 +0530

    gfapi: Dump graph upon initilization/switch for better debugging experience
    
    Having this information printed the way FUSE/nfs do would helps immensely with
    debugging experience, especially when a user/customer has added and removed
    bricks a couple of times. It helps in mapping the brick path to its
    corresponding protocol/client translator and in turn all the log messages that
    may be thrown by this protocol/client xlator.
    
    Change-Id: I0784e5fe932326fdbdc56f5a12b6951c7541a8cf
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16919
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>

commit 71e023fcaab0058f32fedc7b6b702040fdd85f46
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Mar 19 22:42:33 2017 +0530

    afr: do not mention split-brain in log message in read_txn
    
    I am seeing a lot of messages in qe/customer logs where read_txn
    complains that file is possibly in split-brain because of no readable
    subvol being found, does inode refresh and then there is no split-brain
    message post the inode refresh. This means that a lookup was not issued
    on the indoe to populate 'readable' or it can mean one brick is source
    for data and the other for metadata, making readable to be zero (because
    readable=intersection of (data,metadata readable) since commit
    7a1c1e290470149696.
    
    Since we anyway log actual split-brains post inode-refresh, move this
    message to DEBUG log level.
    
    Change-Id: Idb88b8ea362515279dc9b246f06b6b646c6d8013
    BUG: 1433838
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16879
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e2a652ca6ba56235e6d64bf7df110afdc5f6ca27
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Mar 17 13:03:57 2017 -0400

    geo-rep: Optionally allow access to mounts
    
    In order to improve debuggability, it is important
    to have access to geo-rep master and slave mounts.
    With the default behaviour, geo-rep lazy unmounts
    the mounts after changing the current working
    directory into the mount point. It also cleans
    up the mount points. So only geo-rep worker has
    the access and it becomes impossible to take the
    client profile info and do any other client statck
    analysis. Hence the following new config is being
    introduced to allow access to mounts.
    
    gluster vol geo-rep <mastervol> <slavehost>::<slavevol> \
    config access_mount true
    
    The default value of 'access_mount' is false.
    
    Change-Id: I53dce4ea86a6ffc979c82f9330e8954327180ca3
    BUG: 1433506
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/16912
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 78222bff29f27fc3b4f500ff2f7bd323c418d09e
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Apr 19 14:01:09 2016 +0530

    TIER: watermark check during low watermark reset
    
    PROBLEM: during a low watermark reset, checking of whether
    the low watermark is lower than hi watermark is not done.
    
    FIX: This patch checks if the hi watermark value is higher
    the default low watermark. Else throws an failure of the reset
    command
    
    Change-Id: I8b49090c6bccce6d45c2e8076ab766047a2a6162
    BUG: 1328342
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/14028
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 870a1d66f56345df38b70baa31ae314e2cde789c
Author: mvignesh@redhat.com <mvignesh@redhat.com>
Date:   Fri Oct 14 19:38:21 2016 +0530

    libglusterfs : update correct message segments in glfs-message-id
    
    Change-Id: I6611c5699303c879e6f5d88549f5101dd6f63e46
    BUG: 1384989
    Signed-off-by: Muthu-vigneshwaran <mvignesh@redhat.com>
    Reviewed-on: https://review.gluster.org/15644
    Tested-by: Muthu Vigneshwaran <muthuvigneshwaran77@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fdabb97d57793084190440b90c75c37761d5720c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 9 12:18:40 2017 -0500

    build/packaging: Debian and Ubuntu don't have /usr/libexec
    
    GLUSTERFS_LIBEXECDIR is effectively hard-coded to /usr/libexec/glusterfs
    in configure(.ac)
    
    Debian-based distributions don't have a /usr/libexec/ directory
    
    This issues is partially mitigated by the use of $libexecdir in
    some of the Makefile.am files, but even so the incorrectly defined
    GLUSTERFS_LIBEXECDIR results in various things such as gsyncd,
    glusterfind, eventsd, etc., trying to invoke other scripts and
    programs from a location that doesn't exist.
    
    And once we correctly define GLUSTERFS_LIBEXECDIR, then we might as
    well use it appropriatedly.
    
    Change-Id: If5219cadc51ae316f7ba2e2831d739235c77902d
    BUG: 1430841
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16880
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Joe Julian <me@joejulian.name>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit fc97b1dc38ad46302d51a988cda18335f88514a2
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 28 15:52:49 2017 +0530

    storage/posix: Use granular mutex locks for pgfid update syscalls
    
    Change-Id: Ie5d635951c483d858dc4be2a90fb24b8b5f4f02d
    BUG: 1421938
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16869
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit eac6dfc314abe4dc50c54bf6c6cc004dfd73d5ac
Author: Kevin Vigor <kvigor@fb.com>
Date:   Thu Dec 15 13:41:14 2016 -0800

    transport: allow OS to assign us a port
    
    Replace complex and slow port selection code with bind(0) which
    already respects privileged ports.
    
    Change-Id: I408a8528e58e1aafcd32eba6a8f1a759e0bf274e
    BUG: 1405628
    Reviewed-on-release-3.8-fb: http://review.gluster.org/16150
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16178
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b3ac24cdd759fb4cd2946329860bcc004f736b23
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Mar 9 09:29:49 2017 +0100

    features/locks: Fix leak of posix_lock_t's client_uid
    
    Change-Id: I3bc14998ed6a8841f77a004c24a456331048a521
    BUG: 1428510
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/16838
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b9e1c911833ca1916055622e5265672d5935d925
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 6 10:34:05 2017 -0500

    performance/write-behind: Honor the client pid set
    
    write-behind xlator does not honor the client pid being
    set. It doesn't pass down the client pid saved in
    'frame->root->pid'. This patch fixes the same.
    
    Change-Id: I838dcf43f56d6d0aa1d2c88811a2b271d9e88d05
    BUG: 1430608
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/16854
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 64442122958011a3e7e73c5d205f37ac0da46736
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Nov 9 16:39:44 2016 +0530

    dht/rebalance: update op_errno for rebalance failures
    
    function "rebalance_task_completion" did not honor returned values other
    than -1 and 1. This led to ignoring errno e.g in the current bug,
    ENOTSUP returned by __is_file_migratable and it returned
    EINVAL(op_errno initialized) to it's caller leading to failure messages
    logged in ERROR level.
    
    Change-Id: I45549fba35c72b278539269b750768fd89e0faf2
    BUG: 1393338
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: https://review.gluster.org/15810
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 90b2b9b29f552fe9ab53de5c4123003522399e6d
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 9 12:49:27 2017 -0500

    glusterfsd+libglusterfs: add null checks during attach
    
    It's possible (though unlikely) that we could get a brick-attach
    request while we're not ready to process it (ctx->active not set yet).
    Add code to guard against this possibility, and return appropriate
    error indicators.
    
    Change-Id: Icb3bc52ce749258a3f03cbbbdf4c2320c5c541a0
    BUG: 1430860
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16883
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 53e2c875cf97df8337f7ddb5124df2fc6dd37bca
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Mar 7 18:36:58 2017 -0500

    glusterd: don't queue attach reqs before connecting
    
    This was causing USS tests to fail.  The underlying problem here is
    that if we try to queue the attach request too soon after starting a
    brick process then the socket code will get an error trying to write
    to the still-unconnected socket.  Its response is to shut down the
    socket, which causes the queued attach requests to be force-unwound.
    There's nothing to retry them, so they effectively never happen and
    those bricks (second and succeeding for a snapshot) never become
    available.
    
    We *do* have a retry loop for attach requests, but currently break out
    as soon as a request is queued - not actually sent.  The fix is to
    modify that loop so it will wait some more if the rpc connection isn't
    even complete yet.  Now we break out only when we have a completed
    connection *and* a queued request.
    
    Change-Id: Ib6be13646f1fa9072b4a944ab5f13e1b29084841
    BUG: 1430148
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16868
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit eb038c19e2c799e35e72eeb500dfb81efc5567e2
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Mar 7 11:53:04 2017 -0500

    glusterfsd: don't quit (in client) on connection failure
    
    Change-Id: I32be91e9db361a45454d6340a4c4ac2d0d7efffc
    BUG: 1430042
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16866
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 6ffce4d698a2c9d61820aa31148671b0653fd4c6
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Feb 28 10:38:19 2017 +0530

    extras/devel-tools: script to resolve bt addresses
    
    Problem:
    STACK_WINDs in a gluster backtrace dumped in a log file are
    undecipherable with only the hex addresses of the location
    leaving us without a clue.
    
    Solution:
    This utility uses the undeciphered lines in the backtrace and the
    associated debuginfo rpm to generate the function name and the file and
    line number associated with the stack frame.
    
    Passing "none" as the debuginfo rpm name will make the script assume
    that you want to resolve against a source install and not a debuginfo
    rpm.
    
    You would need to copy the unresolved lines from the backtrace into a
    file and pass the name of this file to the utility as the input file.
    
    Change-Id: I4d8bc1ae205af37688d03298de49654018bdba9d
    BUG: 1426891
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/16763
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7ddab8fa7b05343e4a110fadc227675479f9e358
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Mar 1 16:38:21 2017 +0100

    Free the mutex even if we can't allocate a inode
    
    Since GF_CHECK_ALLOC may jump to out, with a mutex locked,
    we need to make sure the mutex is unlocked before returning.
    
    Error found by coverity
    
    Change-Id: I81011e18afc90c2c0fd489ceeb78d90ae31e35ba
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16793
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fabce246ae948e8e3060dee4a720cd64ac76fdaf
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Mar 7 14:32:18 2017 +0530

    cluster/ec: Don't mark dirty on entry/meta ops in query-info
    
    We wanted to mark dirty for metadata/entry operations
    whenever query-info is set and info is not yet there because we
    are anyway sending xattrop over the network. But this is causing
    25% regression from 3.8.8 so removing this optimization
    
    Also fixed two small issues that we didn't find in the previous
    patch
    1) reconfigure failure was sending return value 0 for optimistic-changelog
    2) ec->optimistic_changelog was set to true even before OPTION_INIT
    
    BUG: 1408809
    Change-Id: Iabb0b64bd4d3623688790e4b67e5c20b4da977a1
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16865
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ce8d8195dc253a87cceaaeeb1a725090471ae4f8
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Sat Feb 18 00:49:02 2017 +0100

    posix: use nanosecond accuracy when available
    
    Programs that set mtime, such as `rsync -a`, don't work correctly on
    GlusterFS, because it sets the nanoseconds to 000. This creates
    problems for incremental backups, where files get accidentally copied
    again and again.
    
    For example, consider `myfile` on an ext4 system, being copied to a
    GlusterFS volume, with `rsync -a` and then `cp -u` in turn. You'd
    expect that after the first `rsync -a`, `cp -u` agrees that the file
    need not be copied.
    
    BUG: 1422074
    Change-Id: I89c7b6a73e2e06c02851ff76b7e5cdfaa271e985
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>
    Reviewed-on: https://review.gluster.org/16667
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 89c6bedc1c2e978f67ca29f212a357984cd8a2dd
Author: Milind Changire <mchangir@redhat.com>
Date:   Sun Mar 5 21:39:20 2017 +0530

    rpc: avoid logging success on failure
    
    Avoid logging Success in the event of failure especially when errno has
    no meaningful value w.r.t. the failure. In this case the errno is set to
    zero when there's indeed a failure at the RPC level.
    
    Change-Id: If2cc81aa1e590023ed22892dacbef7cac213e591
    BUG: 1426032
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/16730
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c429595b80c23d2e10051cb9f70ed53f771e8f06
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Wed Dec 14 08:24:01 2016 -0800

    tests: Fix tests/bugs/distribute/bug-1161311.t
    
    Summary:
    - Bigger buffer size made rebalance faster and broke the test.
    - We made the file bigger so rebalance takes longer.
    
    BUG: 1428058
    Change-Id: I7acfec5611b28bdae0a9d9fc03eb104659a5563a
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Author:    Shreyas Siravara <sshreyas@fb.com>
    Reviewed-on: https://review.gluster.org/16802
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c618de80696c4572fad9e28f0454e63ebb2ff4ed
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Tue Jan 31 16:14:46 2017 +0530

    glusterd : Fix for replicate and disperse volume option
    
    While setting volume option(disperse-shd-max-threads) for
    replicate volume and volume option(cluster-shd-max-threads)
    for disperse volume, glusterd is not validating volume options
    and setting all the values irrespective of proper validation
    for disperse-shd-max-threads and cluster-shd-max-threads
    
    Change-Id: Ic88815ad49e901e74ffc042170f5caabf7c17a89
    BUG: 1417588
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/16489
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b7ba77ab3ffb641d06223f7af5145d3d670b032a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Feb 27 13:51:09 2017 +0530

    glusterd: disallow increasing replica count for arbiter volumes
    
    Problem: add-brick command to increase replica count in an arbiter
    volume succeeds, causing undesirable effects like the 4th brick being
    loaded with the arbiter xlator, the 3rd one losing the arbiter xlator
    (when the brick process is restarted), arbitration logic in afr going
    for a toss etc.
    
    Fix: Arbiter configuration should always be a replica 3 volume (of
    which 3rd brick is arbiter). Hence disallow increasing replica count for
    arbiter volume configurations.
    
    Change-Id: I9fe4edac880d0f711e6d44324ad5562974e53e51
    BUG: 1429200
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16845
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 804a65f07ea8e2093f781807651d0d07513b2627
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat Mar 4 01:04:10 2017 +0530

    afr: restore atime/mtime for non-regular files
    
    AFR restores atime/mtime only as a part of data heal. For non-regular
    files (dirs, symlinks, char/block/socket files etc) which do not undergo
    data-heal, atime/mtime is not restored.
    
    This patch restores atime/mtime as a part of metadata heal for such
    files.
    
    Change-Id: Id8da885fc93fdf65c2f4bae2af3605b146ac1f16
    BUG: 1429198
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16844
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 78c5c5637104cf79578d0fb9173647c9c3421177
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 2 07:14:14 2017 +0530

    cluster/ec: Introduce optimistic changelog in EC
    
    Problem: Fix to https://bugzilla.redhat.com/show_bug.cgi?id=1316873 has made
    changes to set dirty flag before every update fop, data or metadata, and unset
    it after successful operation. That makes some of the fops very slow such as
    entry operations or metadata operations.
    
    Solution: File data operations are the only operation which take some time and
    setting dirty flag before a fop and unsetting it after serves the purpose as
    probability of failure of a fop is high when the time duration is more. For all
    the other operations, set dirty flag at the end of the fop, if any brick is
    down and need heal.
    
    Providing following option to choose between high performance or better heal
    marking for metadata and entry fops.
    
    Set/Unset dirty flag for every update fop at the start of the fop. If ON, this
    option impacts performance of entry operations or metadata operations as it
    will set dirty flag at the start and unset it at the end of ALL update fop. If
    OFF and all the bricks are good, dirty flag will be set at the start only for
    file fops For metadata and entry fops dirty flag will not be set at the start,
    if all the bricks are good. This does not impact performance for metadata
    operations and entry operation but has a very small window to miss marking
    entry as dirty in case it is required to be healed.
    
    Thanks to Xavi and Ashish for the design
    Picked the .t file from Ashish' patch https://review.gluster.org/16298
    
    BUG: 1408809
    Change-Id: I3ce860063f0e2901e50754dcfc3e4ed22daf819f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16821
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit aaa5b2ec2f0ef1a62047c9ab91d957c7b0a1552a
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 17:09:46 2017 +0100

    Fix bad free
    
    Since rsp.path is assigned a constant string, free would
    operate on a incorrect pointer, with likely bad results.
    
    Found by coverity scan
    
    Change-Id: I4befdd78573daa3c0c3013100f7ae69a2dcae36a
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16716
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 843945aed2a4b99a4fd1492b68b18ee80c5c994c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 28 14:27:51 2017 +0530

    storage/posix: Use more granular mutex locks for atomic writes
    
    Change-Id: I7a5167de77fabf19c5151775b553913a1af5a765
    BUG: 1421938
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16785
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 96c622d8d5129c6a20ca1cc86898327e27a9e758
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Oct 13 18:08:57 2016 +0200

    doc: Added documentation about ec implementation
    
    A new document explaining how ec encoding/decoding is implemented
    has been added to the developer guide.
    
    Change-Id: I344493477bf42b935ed75f7cf0574d54dc1b9509
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/15637
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 99a510d0cd39de283b89921c68350c1a767e852c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Mar 2 15:27:54 2017 +0530

    cluster/dht: Fix crash in "nuke-dir" feature
    
    My patch at https://review.gluster.org/16419 is resulting
    in core dumps everytime I run tests/features/nuke.t.
    
    Turns out dht, upon successfully "nuking" a directory,
    which was initiated through a setxattr, unwinds the operation
    with rmdir fop signature, resulting in readdir-ahead casting
    a struct iatt (preparent) to dict_t, leading to a crash.
    
    Change-Id: If5f50417be9eb93e731b06c79b9bf027e5dd4d55
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16829
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 1c19d1f4cf9a9b2bfa8f4678a2519c50752dc429
Author: Shyam <srangana@redhat.com>
Date:   Wed Mar 1 14:30:14 2017 -0500

    doc: Added a github issue template to redirect to mails or bugzilla
    
    We currently see an increased activity by users filing github issues.
    As we do not use github issues to track or respond to queries, adding
    this template to help redirect users to the right forum.
    
    Change-Id: Ied69af1c42b85e10018bbd83d48f7e6fa3c1f10b
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: https://review.gluster.org/16795
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 351638ba61d2451d97363e71adb9a9ce7d5b9c85
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Thu Aug 4 11:44:53 2016 -0700

    dht/rebalance: Increase maximum read block size from 128 KB to 1 MB
    
    Summary:
    - The maximum block size, `DHT_REBALANCE_BLKSIZE`, is set to 128 KB.
    - As a result, migrating files in the megabytes to gigabytes can take much longer than necessary.
    - Some preliminary results by bumping the blocksize:
    
    With 128 KB:
      [2016-08-04 11:40:19.251167] I [MSGID: 109028] [dht-rebalance.c:2196:gf_defrag_status_get] 0-glusterfs: Rebalance is completed. Time taken is 15.00 secs
      [2016-08-04 11:40:19.251189] I [MSGID: 109028] [dht-rebalance.c:2200:gf_defrag_status_get] 0-glusterfs: Files migrated: 49, size: 2569011200, lookups: 149, failures: 0, skipped: 0
    
    With 1 MB:
      [2016-08-04 11:41:21.093662] I [MSGID: 109028] [dht-rebalance.c:2196:gf_defrag_status_get] 0-glusterfs: Rebalance is completed. Time taken is 7.00 secs
      [2016-08-04 11:41:21.093687] I [MSGID: 109028] [dht-rebalance.c:2200:gf_defrag_status_get] 0-glusterfs: Files migrated: 49, size: 2569011200, lookups: 149, failures: 0, skipped: 0
    
    - This is a cherry-pick of D3670927 to 3.8.
    
    Test Plan: Tested rebalance on devserver.
    
    Reviewed By: dph, rwareing
    
    Change-Id: Ide2edbf87ef9ae2b32a03f189c57b63e2f233fc8
    BUG: 1428055
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-on: https://review.gluster.org/16797
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6a3f2b5d0542464b14b3263ecf31f995717eee8f
Author: Richard Wareing <rwareing@fb.com>
Date:   Fri Jun 3 20:39:36 2016 -0700

    protocol/server: Fix crash bug in unlink flow
    
    Summary: Fixes a crash bug during unlink in server-rpc-fops.c
    
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    
    Change-Id: I049a9863ffd4003742276e0aa9e8d1224488182d
    BUG: 1428093
    Tested-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-on: https://review.gluster.org/16814
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9ed98f23564387c5b436a0c6ec6d4393f970dcb9
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Mar 1 14:35:26 2017 -0800

    glusterd: use sys_lstat instead of lstat
    
    Showed up in 0symbol-check.t while testing something else.  Might as
    well fix it now.
    
    Change-Id: Ic6b8214de6f486187afc4987c5ffbbca02c8997f
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16820
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 3c8b3a322d1ecbf99e4718abede32d739bda491c
Author: Michael Scherer <misc@redhat.com>
Date:   Thu Feb 23 22:29:28 2017 +0100

    Do not use va_end before cli_rl_out, since it use ap
    
    Trigger a cppcheck error
    
    Change-Id: I8919fed47ef562319ac6baff38ed993e7cd54708
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16741
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a2d4c928e93c95dfe2ceff450556f8494d67e654
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Mar 1 12:48:10 2017 +0530

    storage/posix: Set ret value correctly before exiting
    
    Change-Id: I07c3a21c1c0625a517964693351356eead962571
    BUG: 1427404
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16792
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9babd965ba885ca8bea4c58e708a3b9f0d6f076c
Author: Nigel Babu <nigelb@redhat.com>
Date:   Wed Mar 1 07:16:19 2017 +0530

    Return ret as soon as `this` is freed
    
    Omitting this return causes a confusing error message in the next block,
    which is also a case of use after free. This bug was found by Coverity
    scan.
    
    BUG: 789278
    Change-Id: Ifd4932de437e8ae875ff191033ea43cff81b701d
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: https://review.gluster.org/16790
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c78d07fb8efdd5f63284332473852619d5da4244
Author: Niklas Hambüchen <mail@nh2.me>
Date:   Tue Feb 28 14:05:59 2017 +0100

    tests: Fix and enable split-brain-healing mtime check
    
    This test was commented out with the belief that it depended
    on utimensat() support, but in fact it was not necessary because
    `stat -c %Y` only outputs second resolution.
    
    Simply commenting in the test made it fail because it checked
    the values *before* the heal, while intended was to check them
    *after* the heal. This commit fixes that.
    
    Change-Id: I4194ac645b365a1f906a3ac9bcbbdb1f05000e27
    BUG: 1422074
    Signed-off-by: Niklas Hambüchen <mail@nh2.me>
    Reviewed-on: https://review.gluster.org/16789
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niklas Hambüchen

commit 67a35ac54bfd61a920c1919fbde588a04ac3358a
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Feb 23 17:58:46 2017 +0530

    rpc: log more about socket disconnects
    
    Log more about the different paths leading to socket disconnect for ease
    of debugging.
    
    Log via gf_log_callingfn() in __socket_disconnect() at loglevel TRACE if
    socket connection is being torn down.
    
    Change-Id: I1e551c2d685784b5ec747f481179f64d524c0461
    BUG: 1426125
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/16732
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 773f32caf190af4ee48818279b6e6d3c9f2ecc79
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Feb 28 13:13:59 2017 +0530

    rpc/clnt: remove locks while notifying CONNECT/DISCONNECT
    
    Locking during notify was introduced as part of commit
    aa22f24f5db7659387704998ae01520708869873 [1]. The fix was introduced
    to fix out-of-order CONNECT/DISCONNECT events from rpc-clnt to parent
    xlators [2]. However as part of handling DISCONNECT protocol/client
    does unwind saved frames (with failure) waiting for responses. This
    saved_frames_unwind can be a costly operation and hence ideally
    shouldn't be included in the critical section of notifylock, as it
    unnecessarily delays the reconnection to same brick. Also, its not a
    good practise to pass control to other xlators holding a lock as it
    can lead to deadlocks. So, this patch removes locking in rpc-clnt
    while notifying parent xlators.
    
    To fix [2], two changes are present in this patch:
    
    * notify DISCONNECT before cleaning up rpc connection (same as commit
      a6b63e11b7758cf1bfcb6798, patch [3]).
    * protocol/client uses rpc_clnt_cleanup_and_start, which cleans up rpc
      connection and does a start while handling a DISCONNECT event from
      rpc. Note that patch [3] was reverted as rpc_clnt_start called in
      quick_reconnect path of protocol/client didn't invoke connect on
      transport as the connection was not cleaned up _yet_ (as cleanup was
      moved post notification in rpc-clnt). This resulted in clients never
      attempting connect to bricks.
    
    Note that one of the neater ways to fix [2] (without using locks) is
    to introduce generation numbers to map CONNECT and DISCONNECTS across
    epochs and ignore DISCONNECT events if they don't belong to current
    epoch. However, this approach is a bit complex to implement and
    requires time. So, current patch is a hacky stop-gap fix till we come
    up with a more cleaner solution.
    
    [1] http://review.gluster.org/15916
    [2] https://bugzilla.redhat.com/show_bug.cgi?id=1386626
    [3] http://review.gluster.org/15681
    
    Change-Id: I62daeee8bb1430004e28558f6eb133efd4ccf418
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1427012
    Reviewed-on: https://review.gluster.org/16784
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 13201e55299b4229a4481d886b12fd34d76044ac
Author: Nigel Babu <nigelb@redhat.com>
Date:   Tue Feb 28 13:13:36 2017 +0530

    Free brick_hint at the end of the function
    
    Not freeing brick_hint causes a memory leak. This error was reported by
    Coverity.
    
    Change-Id: Ic923f892ea5207848cdd3fa6332a1e52e6c996b8
    BUG: 789278
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: https://review.gluster.org/16782
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit bae7b51d628a3ff4d96be1ec62dca1c8ed008dc8
Author: Michael Scherer <misc@redhat.com>
Date:   Thu Feb 23 20:17:25 2017 +0100

    Use int instead of int8_t for the 3 variables
    
    Since strcmp return a int, and since the spec
    of strcmp do not tell the return value, it
    could return 256 and this would overflow.
    
    Found by Coverity scan.
    (thanks to Stéphane Marcheusin who explained
    the details to me)
    
    Change-Id: I5195e05b44f8b537226e6cee178d95a1ab904e96
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16738
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3e66156cf202c56010bfa0c63db95ef0a5998947
Author: Michael Scherer <misc@redhat.com>
Date:   Tue Feb 28 15:02:18 2017 +0100

    Free arg_save when malloc fail
    
    Warning found by coverity.
    
    Change-Id: Ie755659c33a43a440dadfeb1499a2f6c08e3f625
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16788
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit bbb03ab1a2a9f0acc02f1d252a9bf811ba854bab
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 28 11:45:44 2017 +0530

    tests: Mark tests/bitrot/bug-1373520.t bad until fixed
    
    Change-Id: Ic0b5c93c6365e26a5742184dd9445354c0a57295
    BUG: 1427404
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16780
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 874059dc94a123f78c19ba14bee2d5540c106a9e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 22 09:49:05 2017 +0530

    protocol/client: Add gfid in request for better tcpdumps
    
    It is difficult to match opendir/releasedir or
    open/release calls without gfid associlation to find
    fd-leaks on the bricks. So assigning gfid also in
    the request which was already there in the on-wire
    format.
    
    BUG: 1425676
    Change-Id: Iec908eeaa2f97295d45140a529b7f8fb834a1553
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16706
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 753f6dec4c99fb29d4b386b96b364c5a142ca547
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Feb 27 11:20:14 2017 +0530

    socket: Avoid flooding of SSL messages in case of failure/success
    
    Problem: Avoid flodding of SSL messages in case of failure/success
    
    Solution: 1) Ideally ssl_setup_connection should be call after getting success on
                 connect so update the condition before call socket_spawn in socket_connect.
              2) Change the message type to debug in case of success.
    
    BUG: 1427018
    Change-Id: Icb6101e49304d5fe539609b4afacfb1b50b62f84
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/16767
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bdabf56a92f4962c10b36d804a34aff8518b1cca
Author: Nigel Babu <nigelb@redhat.com>
Date:   Mon Feb 27 11:07:16 2017 +0530

    glusterd: Fix the incorrect check
    
    err_str is an array and is therefore never NULL. This condition would
    always be false.
    
    Change-Id: I31eb3338986a3af584e0feca8ec3e16f738378ec
    BUG: 789278
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: https://review.gluster.org/16766
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 9c310f7c5ee5e32db349a70120ac82523afb2c51
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 18:04:59 2017 +0100

    Remove double free for disk_layout
    
    Since disk_layout is freed after the jump to err, we
    do not need to free it again before the goto.
    
    Found by coverity scan.
    
    Change-Id: Ie0c0262f6b95c51c61a59faefbca70352bf1e604
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16720
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1e3538baab7abc29ac329c78182b62558da56d98
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Mon Feb 20 18:35:01 2017 +0530

    core: Clean up pmap registry up correctly on volume/brick stop
    
    This commit changes the following:
    1. In glusterfs_handle_terminate, send out individual pmap signout
    requests to glusterd for every brick.
    2. Add another parameter to glusterfs_mgmt_pmap_signout function to
    pass the brickname that needs to be removed from the pmap registry.
    3. Make sure pmap_registry_search doesn't break out from the loop
    iterating over the list of bricks per port if the first brick entry
    corresponding to a port is whitespaced out.
    4. Make sure the pmap registry entries are removed for other
    daemons like snapd.
    
    Change-Id: I69949874435b02699e5708dab811777ccb297174
    BUG: 1421590
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/16689
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit dbdfe6c353060b7af7b4250c8d6c30ed0c35783c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Feb 26 23:00:21 2017 +0530

    glusterd: add portmap details in glusterd statedump
    
    glusterd statedump file doesn't have information on the ports and its
    associated brick details. This is quite problematic if any setup ends up
    with stale ports and the only way to find the issue out is to gdb into
    the process which is always not available. This patch attempts to fill
    in this gap.
    
    Change-Id: I26b4fe753d752366ddf865ca3eeae3b4d577d555
    BUG: 1426948
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16764
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit b5c26a462caf97bfc5380c81092f5c331ccaf1ae
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jan 23 17:40:40 2017 +0530

    storage/posix: Execute syscalls in xattrop under different locks
    
    ... and not inode->lock. This is to prevent the epoll thread from
    *potentially* being blocked on this lock in the worst case for
    extended period elsewhere in the brick stack, while the syscalls
    in xattrop are being performed under the same lock by a different
    thread. This could potentially lead to ping-timeout, if the only
    available epoll thread is busy waiting on the inode->lock, thereby
    preventing it from picking up the ping request from the client(s).
    
    Also removed some unused functions.
    
    Change-Id: I2054a06701ecab11aed1c04e80ee57bbe2e52564
    BUG: 1421938
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16462
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8aee74f25cfa9dc676e116e9882723254b0509a9
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Oct 19 15:20:45 2016 +0530

    protocol/mgmt: sending wrong return value during emancipation
    
    A change introduced for moving emancipation after signin process
    cause this regression, where the second signin always return the
    size of process xdr.
    
    This patch will fix the issue.
    
    Change-Id: Ic924c82abe6932a93abe37df1fd2d1285a77ed0a
    BUG: 1386578
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: https://review.gluster.org/15687
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c1fc1fc9cb5a13e6ddf8c9270deb0c7609333540
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 25 15:31:44 2017 +0530

    cluster/ec: Don't trigger data/metadata heal on Lookups
    
    Problem-1
    If Lookup which doesn't take any locks observes version mismatch it can't be
    trusted. If we launch a heal based on this information it will lead to
    self-heals which will affect I/O performance in the cases where Lookup is
    wrong. Considering self-heal-daemon and operations on the inode from client
    which take locks can still trigger heal we can choose to not attempt a heal on
    Lookup.
    
    Problem-2:
    Fixed spurious failure of
    tests/bitrot/bug-1373520.t
    For the issues above, what was happening was that ec_heal_inspect()
    is preventing 'name' heal to happen
    
    Problem-3:
    tests/basic/ec/ec-background-heals.t
    To be honest I don't know what the problem was, while fixing
    the 2 problems above, I made some changes to ec_heal_inspect() and
    ec_need_heal() after which when I tried to recreate the spurious
    failure it just didn't happen even after a long time.
    
    BUG: 1414287
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Change-Id: Ife2535e1d0b267712973673f6d474e288f3c6834
    Reviewed-on: https://review.gluster.org/16468
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>

commit 4638dfc1fee80f9338f2941f3cccb17bec63989a
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Nov 18 10:05:12 2016 -0500

    events: use attribute(format(/printf)) to catch fmt string errors
    
    and statedump too. Also "const char *" (versus just "char *") for the
    fmt param.
    
    Change-Id: Ic63734a673208a2cd49aebccce7659816e6179e3
    BUG: 1399196
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/15881
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit ece5f66a3d05628bb1a74833ae695443e079f80d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 26 20:16:23 2016 -0400

    build: fixes to build 3.9.0rc2 on Debian
    
    Add glustereventsd-Debian(.in) and associated Makefile(.am)
    and configure(.ac) changes
    
    Add UUIDLIBS to fdl's librecon
    
    Change-Id: Ibff821691023704978140eaaff2c6532b74c50fa
    BUG: 1389127
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/15737
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Joe Julian <me@joejulian.name>

commit 7fcc85748c54687a1a29f25db7155beccba9d186
Author: Michael Scherer <misc@redhat.com>
Date:   Fri Feb 24 21:35:38 2017 +0100

    mgmt: Reset conf_fd to default value to avoid double close
    
    Coverity warn of a path where we use sys_close 2 times on the
    same file descriptor, which is likely harmless but could
    cause various hard to debug problems if threads are used
    (since the file descriptor table is shared among all
    threads, we could close a newly opened fd by another thread).
    
    Change-Id: I0524b31dccc0da94c7b87583e2a88ef06e003518
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16758
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit d9172b961b85fc2e5431b2970521709680166fe1
Author: Michael Scherer <misc@redhat.com>
Date:   Fri Feb 24 12:41:45 2017 +0100

    dnt: Add a GF_DEFRAG_CMD_NONE to gf_defrag_type
    
    Coverity complain about enum mismatch since we assign GF_OP_CMD_NONE
    to a variable holding gf_defrag_type.
    
    Change-Id: I63e71f552b3cc752c26c1b8705420f38908e17e6
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16756
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 235ae3528d4e8a914fc208ff05580336c865727c
Author: Michael Scherer <misc@redhat.com>
Date:   Thu Feb 23 21:35:45 2017 +0100

    dnt: Fix crash when showing the error message
    
    Since this is NULL, this->name would crash the
    daemon if a incorrect rebal_entry is passed.
    Found by coverity scan.
    
    Change-Id: Ieddf1ef097d13711ab8ec9cd24e125914d2e7245
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16740
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 730f520a1ee246a5f4a08a321b6f97bdf93536dc
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 17:58:24 2017 +0100

    Free iobuf after using it, not before
    
    Coverity warn of use after free here. I assume that
    under pressure, this might crash the whole process.
    
    Change-Id: I15fb5cfc9b509705e96e4156b739988d816bbef5
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16719
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 66edcc856d89ffa33318443aa8680c9376772c4d
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 17:27:43 2017 +0100

    Reorder the variable initialisation
    
    Found by coverity, since is_hot_tier is assigned to false,
    tier_type was always "hot" rather than "cold", making
    potential debugging likely harder.
    
    Change-Id: I49bce1c184548c5de5c00639e83fc3d2dbed90b2
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16717
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8bb29ed9d0d695c66b3be8a9aedb92d87b0c4054
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 17:34:02 2017 +0100

    Remove deadcode
    
    Found by coverity, ret is already test in the previous 'if'.
    
    Change-Id: Iefb7da07c1144470c2322f44b28f98a5904343b4
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16718
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 04582fa313a4782d7898afb56a0747a5dcca3a92
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 16:31:30 2017 +0100

    Remove unused conditionnal
    
    The code is using a got to jump 1 line further, which is
    a no-op. Found by coverty scan
    
    Change-Id: Ic8698e2f86ebd9472b3104b09920ab7946c3b4fc
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16714
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit fe20afb31bdcd92b9c3d41e11872c75ab863f66e
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 16:21:11 2017 +0100

    Remove deadcode, found by coverty
    
    Since ret value is unchanged since last goto out, this
    code is unreachable.
    
    Change-Id: Iff8618739900b44bad6c4e663a4201d9e14cb457
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16713
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 688abcc90745515f7e143ef8cf1e938239db597c
Author: Nigel Babu <nigelb@redhat.com>
Date:   Mon Feb 20 08:27:51 2017 +0530

    libglusterfs, gfdb, glusterfs: Add missing breaks
    
    A few switches did not have breaks causing fall throughs. Most of them
    have been fixed with fall through comments for those that are
    intentional.
    
    Change-Id: I84c85726b542f38504b50fefab5eba5dbcd27a07
    BUG: 1424894
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: https://review.gluster.org/16677
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit dc15855cea679affd78d28fd94cbea0c108997f0
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Feb 23 15:13:43 2017 +0530

    cli: fix error when HAVE_READLINE is false
    
    When HAVE_READLINE is false, Gluster doesn't compile with -Werror flag.
    This will fix it up so it is possible to compile without having readline
    present
    
    Change-Id: Ia6620b5a372318d10f0e908e3d45f4090f99d118
    BUG: 1426052
    Reviewed-on: https://review.gluster.org/16734
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Nigel Babu <nigelb@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ff2ba49d02dc99b0c3de5712348ae9d588be7ad7
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 11:06:56 2017 +0100

    Filter coverty false positives
    
    Since random is not used for anything cryptographically related,
    it is fine to use it in those instances.
    
    Change-Id: I720172285f60d6bc477c7169c7286fc018ebdf8f
    BUG: 1424764
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16668
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Nigel Babu <nigelb@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit f08f5bfef923259fe6de6d41a0a2b1b9140fc547
Author: Michael Scherer <misc@redhat.com>
Date:   Thu Feb 23 23:24:42 2017 +0100

    Do not call va_end twice in _gf_log_eh
    
    Since va_end is called after the out label,
    we do not need to call it here, as it make va_end undefined,
    and thus could cause problem. And this is a error
    on cppcheck.
    
    Change-Id: I6e96c796bd37fa3cde989996ab93f9a438c0ee74
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16745
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Michael Scherer <misc@fedoraproject.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 62d3a2c3fc4e09fe8d1cb05f228715eede1a265d
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 21:46:14 2017 +0100

    Make sure that buffer is null terminated
    
    Coverity warn about it, and while that's unlikely
    to be a issue in practice, it is rather important
    to not mask more critical problems with false positive.
    
    Change-Id: Ibee1a9c37e216635077f05d5ef5de55ad5e0b051
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16727
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 7baa4bdf3a35f1957a37311477cf765fa4e85445
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Feb 24 10:53:57 2017 +0530

    glusterd : log improvements in glusterd_op_stage_rebalance ()
    
    Include volume names in the respective staging failure error logs in
    rebalance staging
    
    Change-Id: Iaaab12a552930dd5274fbecec78f5735f883ab6b
    BUG: 1426509
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16746
    Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1e2773cf1586b78c71e5b8adc24c6b65f065357c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 17 15:37:18 2016 +0530

    features/shard: Fix EIO error on add-brick
    
    DHT seems to link inode during lookup even before initializing
    inode ctx with layout information, which comes after
    directory healing.
    
    Consider two parallel writes. As part of the first write,
    shard sends lookup on .shard which in its return path would
    cause DHT to link .shard inode. Now at this point, when a
    second write is wound, inode_find() of .shard succeeds and
    as a result of this, shard goes to create the participant
    shards by issuing MKNODs under .shard. Since the layout is
    yet to be initialized, mknod fails in dht call path with EIO,
    leading to VM pauses.
    
    The fix involves shard maintaining a flag to denote whether
    a fresh lookup on .shard completed one network trip. If it
    didn't, all inode_find()s in fop path will be followed by a
    lookup before proceeding with the next stage of the fop.
    
    Big thanks to Raghavendra G and Pranith Kumar K for the RCA
    and subsequent inputs and feedback on the patch.
    
    Change-Id: I9383ec7e3f24b34cd097a1b01ad34e4eeecc621f
    BUG: 1420623
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/14419
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 47da9260c51d5a7b066fa9f982f3bd6aef9c64f3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Feb 22 13:55:00 2017 -0500

    gfapi: OBS build fails in post build analysis
    
    Originally gfapi: create statedump when glusterd requests it
    
    When GlusterD sends the STATEDUMP procedure to the libgfapi client, the
    client checks if it matches the PID that should take the statedump. If
    so, it will do a statedump for the glfs_t that is connected to this mgmt
    connection.
    
    See https://bugzilla.redhat.com/show_bug.cgi?id=1169302#c25 for the
    OpenSuSE Build System post build analysis error.
    
    See Change-Id: I70d6a1f4f19d525377aebc8fa57f51e513b92d84
        https://review.gluster.org/#/c/16415/
    
    Change-Id: I7775f44ce13e20c831e8f1015816a28471d35bb4
    BUG: 1169302
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16722
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c1d197c15a836c0131d4d4559e5fdf7394c97963
Author: Michael Scherer <misc@redhat.com>
Date:   Wed Feb 22 22:08:51 2017 +0100

    nfs: remove include of mount3.h
    
    While there is proper protection against that, coverity
    complain of a loop, and nothing in auth-cache.h use
    a declaration of "mount3.h".
    
    Change-Id: I55885ec12496359170f271ae192e9940a35121e1
    BUG: 789278
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16728
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b584c068c6526853f82ccd2a406c3596d7d56be0
Author: Nigel Babu <nigelb@redhat.com>
Date:   Sat Feb 18 14:02:30 2017 +0530

    libglusterfs, dht, locks, glusterd: Coverity fixes
    
    Fix up use after free bugs and dead code
    
    Change-Id: I8f79ed6b5108926c1fac31c147b5ecba79d10785
    BUG: 1424905
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: https://review.gluster.org/16666
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit afe3a0d2869b706a3d5257f39d6acb9cbe856b87
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 15:18:56 2017 +0100

    Properly verify the return code of fcntl
    
    Coverty scan complain about it, even if in practice, this
    doesn't seems to have much impact.
    
    Change-Id: I513f7d393889625d22dded25ef4c7477f68d1064
    BUG: 1424793
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16671
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Nigel Babu <nigelb@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>

commit a88cb01c78c9a13d2879917b54ead26dce8cc63c
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Feb 22 15:19:20 2017 +0530

    TESTS/TIER: bug-1303028-Rebalance-glusterd-rpc-connection-issue.t
    
    PROBLEM: spurious failure of the test.
    
    CAUSE: the function "rebalance_run_time" calculates the total time
    the tier has been running for. this being a test case, the run time
    of tier can be 0 and when the function adds up zero it results in
    zero. and thus it starts to fail.
    
    FIX: Give it some time for the function to add up the values.
    
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    
    Change-Id: Ie270f3f3c8942081cca85dc49ef8fec76f3a261a
    BUG: 1425743
    Reviewed-on: https://review.gluster.org/16711
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 583e6cfc5bc73c2a79be9d42e89b90a71454596f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Feb 22 14:43:46 2017 +0530

    features/shard: Put onus of choosing the inode to resolve on individual fops
    
    ... as opposed to adding checks in "common" functions to choose the inode
    to resolve based local->fop, which is rather ugly and prone to errors.
    
    Change-Id: Ia46cc59992baa2979516369cb72d8991452c0274
    BUG: 1420623
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16709
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7224adeb20e1db8d3582f8a68f725686fa9beb5b
Author: Shyam <srangana@redhat.com>
Date:   Tue Feb 21 10:51:27 2017 -0500

    tests: Added check for NFS export availability to quota-anon-fd-nfs.t
    
    Change-Id: I15a9441267c18bb1073d14db325c98fa497f2fb7
    BUG: 1425515
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: https://review.gluster.org/16701
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: sanoj-unnikrishnan <sunnikri@redhat.com>

commit 60347526d9611035da0e56d55d4814f51cda9367
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Tue Feb 21 22:35:47 2017 +0530

    glusterd : cluster.brick-multiplex validation is missing while setting it
    
    Currently glusterd allow setting all values  while setting cluster.brick-multiplex
    option. Validation of allowed options is missing.
    
    With this patch glusterd will validate the values given while setting
    cluster.brick-multiplex.
    
    Change-Id: I938fb16b8f5faa9d31326373cd18632b8aa7ebab
    BUG: 1425288
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/16704
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 7b6ee5f2bbe00d68a5dcc6283eca2ed3d821c110
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Nov 16 16:19:14 2016 +0530

    snapshot/scheduler: Set sebool cron_system_cronjob_use_shares to on
    
    Rhel 7.1 onwards, the user has to manually set the
    selinux boolean 'cron_system_cronjob_use_shares' as
    on, if selinux is enabled for snapshot scheduler to
    work.
    
    With this fix, we are automating that bit, in init step
    of snapshot scheduler
    
    Change-Id: I5c1d23c14133c64770e84a77999ce647526f6711
    BUG: 1395643
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: https://review.gluster.org/15857
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 9cdfbdced23cd43b8738636a3ed906c8d4267d67
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Feb 21 18:33:14 2017 +0530

    glusterd: unref brickinfo object on volume stop
    
    If brick multiplexing is enabled, on a volume stop glusterd was not
    unrefing the brickinfo rpc object which lead to a flood of stale rpc
    logs.
    
    Change-Id: I18fedcd6921042ef2e945605466194b7b53fe2f7
    BUG: 1421724
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16699
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit 9f9d1482868e8e1044790c8358893f4421d89692
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Feb 14 11:12:58 2017 +0100

    cluster/ec: Fallback to precompiled code
    
    When dynamic code generation fails for some reason, instead of causing
    a failure in encode/decode, fallback to the precompiled version.
    
    Change-Id: I4f8a97d3033aa5885779722b19c6e611caa4ffea
    BUG: 1421955
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/16614
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 431011098efc5702a2f49fad1975fb956cdc9e00
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Feb 16 20:32:36 2017 +0100

    rpm: replace renamed python-gluster with python2-gluster
    
    When upgrading from < 3.10, the old python-gluster package causes
    conflicts with the newly renamed python2-gluster package.
    
    This can be solved by adding the appropriate Provides and Obsoletes to
    the python2-gluster RPM. Details on renaming packages are listed on the
    Fedora Packaging Guidelines.
    
    Change-Id: Ib143bf69022c45abe2d5e8d31d3375a6b85f75da
    URL: https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages
    BUG: 1414902
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16649
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>

commit 420c2d03543a35f1f5483f200541577f4a606b22
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 16:54:39 2017 +0100

    Fix erronous comparaison of flags
    
    Using a binary 'or' mean that we always send the
    UUID, even when not required.
    
    Found by coverty scan
    
    Change-Id: Ifc4bff6b2f64febd5d2f038538218c2183518fd5
    BUG: 1424815
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16675
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6b42f96d148f0bf36149346196edf5d42bf74941
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 14:51:27 2017 +0100

    Initialize path, since coverty detect a code path where
    we do a free on a unitialized pointer
    (if jbr_get_changelog_dir fail).
    
    Change-Id: Ib68122bb9eddaeb422028f834856a0776ecbb789
    BUG: 1424791
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16670
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Nigel Babu <nigelb@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4a1740d3e8fbccc18772c0fc5f70f2cd7443d51e
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 16:16:00 2017 +0100

    Ressources used by va_start must be freed with va_end
    
    Coverty warn of the defect.
    
    Change-Id: Ie86684520e1d5b41237ab8d3247c24564a1a8639
    BUG: 1424802
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16673
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b4da61c9fc6dd8f800792f0d0db4c5e8e948af4f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Feb 20 09:48:46 2017 +0100

    contributors: map more email addresses and domain names
    
    While checking the statistics for the upcoming release, I noticed some
    new names, emailaddresses and domains. Adding the ones for which the
    mapping is obvious or for which people replied to my request for
    clarification.
    
    Steps to get the more up-to-date statistics (once merged):
    
      $ git checkout master
      $ ./extras/who-wrote-glusterfs/who-wrote-glusterfs.sh v3.9dev..origin/release-3.10
      ...
    
    Change-Id: I4ab85fdbdb53d09a70a659555b8341cf9376167c
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16688
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 37772e8e94400a60aedcd6713b1abedb1eb9ea7f
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 16:38:24 2017 +0100

    Remove the useless goto
    
    ret cannot be 0, since the error code for gf_store_save_value is
    -1. And the label of the goto is just after the goto, so that's
    deadcode.
    
    Change-Id: I227bca41f4d0755891b8e6e0f4cb2ce004615a35
    BUG: 1424809
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16674
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 73defab8be16b73241225bb1c2588a61e3e425d5
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Feb 16 13:05:25 2017 +0530

    marker: Fix inode value in loc, in setxattr fop
    
    On recieving a rename fop, marker_rename() stores the,
    oldloc and newloc in its 'local' struct, once the rename
    is done, the xtime marker(last updated time) is set on
    the file, but sending a setxattr fop. When upcall
    receives the setxattr fop, the loc->inode is NULL and
    it crashes. The loc->inode can be NULL only in one valid
    case, i.e. in rename case where the inode of new loc
    can be NULL. Hence, marker should have filled the inode
    of the new_loc before issuing a setxattr.
    
    marker_rename_cbk was already fixed in a previous commit.
    Fixing marker_rename_done to send valid inode in this commit.
    
    Also in upcall check for NULL inode so that there is no crash.
    
    Change-Id: I3ed2a05118fed3367dfe3251ce4477310cb480d0
    BUG: 1422776
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16633
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 4badd7334d345b1c27f528140e4c28afaf1f32f6
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Feb 15 11:18:31 2017 +0530

    libglusterfs: Fix a crash due to race between inode_ctx_set and inode_ref
    
    Issue:
    Currently inode ref count is gaurded by inode_table->lock, and
    inode_ctx is gauarded by inode->lock. With the new patch [1]
    inode_ref was modified to change the inode_ctx to track the ref
    count per xlator. Thus inode_ref performed under inode_table->lock
    is modifying inode_ctx which has to be modified only under inode->lock
    
    Solution:
    When a inode is created, inode_ctx holder is allocated for all the xlators.
    Hence in case of inode_ctx_set instead of using the first free index in
    inode ctx holder, we can have predecided index for every xlator in the graph.
    
    Credits Pranith K <pkarampu@redhat.com>
    
    [1] http://review.gluster.org/13736
    
    Change-Id: I1bfe111c211fcc4fcd761bba01dc87c4c69b5170
    BUG: 1423373
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16622
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e30af139739e3a6e587d77a9af999035fe20dc37
Author: Mateusz Slupny <mateusz.slupny@appeartv.com>
Date:   Tue Nov 29 12:09:49 2016 +0100

    rpc: fix obvious typo in cleanup code in rpc_clnt_notify
    
    Change-Id: I003e38b238704d3345d46688355bcf3702455ba1
    BUG: 1399593
    Signed-off-by: Mateusz Slupny <mateusz.slupny@appeartv.com>
    [ndevos: rebased after I8ff5d1a32 moved the code around]
    Reviewed-on: https://review.gluster.org/15969
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bcea9e274fc13c56431e1b0553661b4048c206ca
Author: Michael Scherer <misc@redhat.com>
Date:   Sun Feb 19 15:36:27 2017 +0100

    Remove deadcode, found by covertyscan
    
    Since ctx_dict is either assigned to the value of aggr,
    or we goto to out, there is no need for a 2nd goto.
    
    Change-Id: I6c4295c61e6ff412ed7b85421dcae13df8088d7c
    BUG: 1424796
    Signed-off-by: Michael Scherer <misc@redhat.com>
    Reviewed-on: https://review.gluster.org/16672
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 621fedf8aeb3e972db33b3eefa6cbdbef104d6a6
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Jan 10 17:21:56 2017 +0100

    posix: Fix creation of files with S_ISVTX on FreeBSD
    
    On FreeBSD the S_ISVTX flag is completely ignored when creating a
    regular file. Since gluster needs to create files with this flag set,
    specialy for DHT link files, it's necessary to force the flag.
    
    This fix does this by calling fchmod() after creating a file that
    must have this flag set.
    
    Change-Id: I51eecfe4642974df6106b9084a0b144835a4997a
    BUG: 1411228
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/16417
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 3cda64115596f0501bb58209f819655bced22c18
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Feb 17 14:05:25 2017 +0530

    glusterd, readdir-ahead: Fix backward incompatibility
    
    Issue:
    Any opion is spcified in two places: In the options[] of xlator
    itself and glusterd-volume-set.c. The default value of this option
    can be specified in both the places. If its specified only in xlator
    then the volfile generated will not have the option and default value,
    it will be assigned during graph initialization.
    With patch [1] the option rda-request-size was changed from INT to SIZET
    type, and default was changed from 131072 to 128KB, but was specified
    only in the readdir-ahead.c. Thus with this patch alone the volfile
    entry for readdir-ahead looks like:
    volume patchy-readdir-ahead
        type performance/readdir-ahead
        subvolumes patchy-read-ahead
    end-volume
    
    With patch [2], the default of option rda-request-size was specified
    in glusterd-volume-set.c as well(as it was necessary fr parallel readdir).
    With this patch the readdir entry in the volfile will look like:
    volume patchy-readdir-ahead
        type performance/readdir-ahead
        option rda-cache-limit 10MB
        option rda-request-size 128KB
        option parallel-readdir off
        subvolumes patchy-read-ahead
    end-volume
    
    
    Now consider the server has both these patches and client doesn't.
    Server will generate a volfile with entry:
    
    The old clients which thought the option rda-request-size is of type
    INT will now recieve the value 128KB which it willn't understand,
    and hence fail the mount.
    
    The issue is seen only with the combination of [1] and [2].
    
    Solution:
    Instead of specifying 128KB as default in glusterd we specify 131072
    so that the old clients will interpret as INT and new ones as 128KB
    
    Credits: Raghavendra G
    
    Change-Id: I0c269a5890957fd8a38e9a05bdec088645a6688a
    BUG: 1423410
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16657
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 4e0d4b15717da1f6466133158a26927fb91384b8
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Feb 17 09:42:46 2017 -0500

    glusterd: take conn->lock around operations on conn->reconnect
    
    Failure to do this could lead to a race in which a timer would be
    removed twice concurrently, corrupting the timer list (because
    gf_timer_call_cancel has no internal protection against this) and
    possibly causing a crash.
    
    Change-Id: Ic1a8b612d436daec88fd6cee935db0ae81a47d5c
    BUG: 1421721
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16662
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 8e7a8ea818a1cc7fb23b412023a735b3939194f4
Author: Anoop C S <anoopcs@redhat.com>
Date:   Fri Feb 17 12:37:27 2017 +0530

    build: Add gf_attach to glusterfs-server package
    
    Previously gf_attach was listed under glusterfs-fuse sub-package which
    introduced the dependency for glusterfs-api. So as per the discussion
    on gluster-devel[1] moving it to glusterfs-server.
    
    [1] http://lists.gluster.org/pipermail/gluster-devel/2017-February/052111.html
    
    Change-Id: I3d646d7c2e556d8f37e6da67bdedd0738739e01b
    BUG: 1423448
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/16660
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 64637d040d7f63ef6af6588ae17a557ad0229710
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Thu Feb 16 13:02:20 2017 +0530

    glusterd : Fix for error message while removing brick
    
    When remove-brick command is issued to a offline brick, glusterd
    error out the operation with message -: "volume remove-brick start:
    failed: Found stopped brick <hostname>:".
    
    With this fix while removing brick, error message is modified
    to "volume remove-brick start: failed: Found stopped brick
    <brick path>. Use force option to remove the brick"
    
    Change-Id: Id40a02fc38cdb526c4629de262967fe2383febe4
    BUG: 1422624
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/16630
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 9c89eaf85c2ce4fba2551f1a08c358161ab99859
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Feb 17 12:17:18 2017 +0530

    readdir-ahead: Remove unnecessary logging
    
    dict_get_int can return < 0 when key is not found is a valid case.
    Hence no need to log.
    
    Change-Id: If0795b0f178adbb94b10efc563506993f7411962
    BUG: 1423369
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16654
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 932ff80b57846ed77b66776ade575a0b2231183a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Feb 9 15:56:04 2017 +0530

    extras: Add more options to group virt
    
    Apart from some of the option configurations already listed
    in the group-virt.example file, we also recommend that the
    users set certain other options added by this patch for
    VM use-case. This also helps Gluster-oVirt users in configuring
    virt options for new volumes at the click of a button as opposed
    to setting them manually through volume-set command.
    
    Change-Id: I8524e8d8a06bbbb0b9247571706e786410013b41
    BUG: 1418900
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16577
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Sahina Bose <sabose@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b8d827f4e7a289a7d6052e2596064b2f4ceb8d60
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Feb 16 09:58:15 2017 +0100

    build: fix linking of 'gf_logdump' and 'gf_recon'
    
    When linking the 'gf_recon' and 'gf_logdump' binaries on certain OS's
    (Debian?), the following error is returned and compilation aborts:
    
        Making all in src
          CCLD     gf_recon
        Makefile:617: recipe for target 'gf_recon' failed
    
    Furher inspection showed this failure:
    
        /lib/x86_64-linux-gnu/libuuid.so.1: error adding symbols: DSO missing from command line
    
    'gf_recon' and 'gf_logdump' link against libgfapi, and also need to pass the
    additional used libraries on the 'ld' commandline.
    
    Change-Id: I7401023f154dde46443f0186dda8ba749951234c
    Reported-by: chawlanikhil24 (on IRC)
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16639
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit fca31ae5faa15a02e64143b9efb7e19c3b907c2d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 14 20:47:48 2017 +0530

    performance/decompounder: Have terminal value in options[]
    
    Absence of terminal values is leading to buffer-over-flow errors in
    address sanitizer.
    
    BUG: 1422152
    Change-Id: I769c0e4b5bbb3ef2849b8d1097b9def522ae08d9
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16615
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6588204568ab73bf8456ca3b2eccf2ae1182fb95
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 23 14:58:45 2017 +0530

    cluster/afr: Perform new entry mark before creating new entry
    
    There is a chance for the source brick to go down just after
    the new entry is created and before source brick is marked with
    necessary pending markers. If after this any I/O happens then
    new entry will become source and reverse heal will happen.
    To prevent this mark the pending xattrs before creating the new
    entry.
    
    BUG: 1417466
    Change-Id: I233b87e694d32e5d734df5a83b4d2ca711c17503
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16474
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 267578ec0d6b29483a1bd402165ea8c388ad825e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Feb 15 03:44:17 2017 -0500

    geo-rep: Fix xsync crawl
    
    If stime is set to (0, 0) on master brick root, it
    is expected to do complete sync ignoring the stime
    set on sub directories. But while initializing the
    stime variable for comparison, it was initailized
    to (-1, 0) instead of (0, 0). Fixed the same.
    
    The stime is set to (0, 0) with the 'reset-sync-time' option
    while deleting session.
    
    'gluster vol geo-rep master fedora1::slave delete reset-sync-time'
    
    The scenario happens when geo-rep session is deleted as above and
    for some reason the session is re-established with same slave volume
    after deleting data on slave volume.
    
    Change-Id: Ie5bc8f008dead637a09495adeef5577e2b33bc90
    BUG: 1422760
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: https://review.gluster.org/16629
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 8607f22dcd1bc9b84e452ae90102fa9d345ad3db
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Feb 14 12:45:36 2017 +0530

    rpcsvc: Add rpchdr and proghdr to iobref before submitting to transport
    
    Issue:
    When fio is run on multiple clients (each client writes to its own files),
    and meanwhile the clients does a readdirp, thus the client which did
    a readdirp will now recieve the upcalls. In this scenario the client
    disconnects with rpc decode failed error.
    
    RCA:
    Upcall calls rpcsvc_request_submit to submit the request to socket:
    rpcsvc_request_submit currently:
    rpcsvc_request_submit () {
       iobuf = iobuf_new
       iov = iobuf->ptr
       fill iobuf to contain xdrised upcall content - proghdr
       rpcsvc_callback_submit (..iov..)
       ...
       if (iobuf)
           iobuf_unref (iobuf)
    }
    
    rpcsvc_callback_submit (... iov...) {
       ...
       iobuf = iobuf_new
       iov1 = iobuf->ptr
       fill iobuf to contain xdrised rpc header - rpchdr
       msg.rpchdr = iov1
       msg.proghdr = iov
       ...
       rpc_transport_submit_request (msg)
       ...
       if (iobuf)
           iobuf_unref (iobuf)
    }
    
    rpcsvc_callback_submit assumes that once rpc_transport_submit_request()
    returns the msg is written on to socket and thus the buffers(rpchdr, proghdr)
    can be freed, which is not the case. In especially high workload,
    rpc_transport_submit_request() may not be able to write to socket immediately
    and hence adds it to its own queue and returns as successful. Thus, we have
    use after free, for rpchdr and proghdr. Hence the clients gets garbage rpchdr
    and proghdr and thus fails to decode the rpc, resulting in disconnect.
    
    To prevent this, we need to add the rpchdr and proghdr to a iobref and send
    it in msg:
       iobref_add (iobref, iobufs)
       msg.iobref = iobref;
    The socket layer takes a ref on msg.iobref, if it cannot write to socket and
    is adding to the queue. Thus we do not have use after free.
    
    Thank You for discussing, debugging and fixing along:
    Prashanth Pai <ppai@redhat.com>
    Raghavendra G <rgowdapp@redhat.com>
    Rajesh Joseph <rjoseph@redhat.com>
    Kotresh HR <khiremat@redhat.com>
    Mohammed Rafi KC <rkavunga@redhat.com>
    Soumya Koduri <skoduri@redhat.com>
    
    Change-Id: Ifa6bf6f4879141f42b46830a37c1574b21b37275
    BUG: 1421937
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16613
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 028626a86ea409f908783b9007c02877f20be43e
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Feb 13 16:49:06 2017 +0530

    cluster/dht Fix error assignment in dht_*xattr2 functions
    
    Corrected the op_errno assignments and NULL checks in
    the dht_sexattr2 and dht_removexattr2 functions. Earlier,
    they unwound with the default EINVAL op_errno if the
    file had been deleted.
    
    Change-Id: Iaf837a473d769cea40132487a966c7f452990071
    BUG: 1421653
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/16610
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 1820a100b75f6a04c5243653b226e9bd4e0a7ed6
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Fri Feb 10 12:30:51 2017 +0530

    build: git ignore generated executable script gf_attach
    
    Change-Id: I5962270f4a06b0ce2e41331ac3519d6dfa2cc5d9
    BUG: 1421023
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: https://review.gluster.org/16596
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 7e59f937523b8f478216e0704d0ca533ec14b221
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Feb 2 12:10:12 2017 +0000

    build: Fix detection of uuid libs during configure
    
    This change cleans up the current logic for detecting the presence of
    uuid libs and avoids the following warning while executing configure
    script:
    
    . . .
    checking for UUID... yes
    checking uuid.h usability... yes
    checking uuid.h presence... no
    configure: WARNING: uuid.h: accepted by the compiler, rejected by the preprocessor!
    configure: WARNING: uuid.h: proceeding with the compiler's result
    checking for uuid.h... yes
    . . .
    
    Refer the following link for more details:
    https://www.gnu.org/software/autoconf/manual/autoconf.html#Present-But-Cannot-Be-Compiled
    
    Change-Id: Icc6e11097fed7c5a82ebd9d931b4e308f7d666c9
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/16541
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit a6ece44d0bbdecf38252f477b4aa98a76771a328
Author: Sunil Kumar Acharya <sheggodu@redhat.com>
Date:   Thu Feb 9 16:34:54 2017 +0530

    cluster/ec: Change log level of messages to DEBUG
    
    Heal failed or passed should not be logged as info. These can be
    observed from heal info if the heal is happening or not. If we require
    to debug a case where heal is not happening, we can set the level to
    DEBUG.
    
    Change-Id: I062668eadd145ef809b25e818e6bca1094f54cd6
    BUG: 1420619
    Signed-off-by: Sunil Kumar Acharya <sheggodu@redhat.com>
    Reviewed-on: https://review.gluster.org/16580
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>

commit a88ae92de190af0956013780939ba6bdfd509ff8
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Feb 13 16:52:07 2017 +0530

    gNFS: Keep the mountdict as long as the service is active
    
    We initialize and take ref once on mountdict during NFS/MNT3 server
    initialization but seem to be unref'in it for every UMNTALL request.
    This can lead to crash when there are multiple UMNTALL requests
    with >=1 active mount entry(/ies) in the mountlist.
    
    Since we take the ref only once, we should keep the mountdict through
    out the life of the process and dereference it only during unitialization
    of mnt3 service.
    
    Change-Id: I3238a8df09b8972e56dd93fee426d866d40d9959
    BUG: 1421759
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: https://review.gluster.org/16611
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit be44a1bd519af69b21acf682b0908d4d695f868e
Author: Gaurav Yadav <gyadav@redhat.com>
Date:   Mon Feb 13 15:46:24 2017 +0530

    glusterd : Fix for error mesage while detaching peers
    
    When peer is detached from a cluster, an error log is being
    generated in glusterd.log -"Failed to reconfigure all daemon
    services". This log is seen in the originator node where the
    detach is issued.
    
    This happens in two cases.
    Case 1: Detach peer with no volume been created in cluster.
    Case 2: Detach peer after deleting all the volumes which were
    created but never started.
    In any one of the above two cases, in glusterd_check_files_identical()
    GlusterD fails to retrieve nfs-server.vol file from /var/lib/glusterd/nfs
    which gets created only when a volume is in place and and is started.
    
    With this fix both the above cases have been handled by added
    validation to skip reconfigure if there is no volume in started
    state.
    
    Change-Id: I039c0840e3d61ab54575e1e00c6a6a00874d84c0
    BUG: 1421607
    Signed-off-by: Gaurav Yadav <gyadav@redhat.com>
    Reviewed-on: https://review.gluster.org/16607
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 25fc74f9d1f2b1e7bab76485a99f27abadd10b7b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Feb 2 16:41:45 2017 +0530

    protocol/client: Fix double free of client fdctx destroy
    
    This patch fixes the race between fd re-open code and fd release code,
    both of which free the fd context due to a race in certain variable
    checks as explained below:
    
    1. client process (shd in the case of this BZ) sends an opendir to its
    children (client xlators) which send the fop to the bricks to get a valid fd.
    
    2. Client xlator loses connection to the brick. fdctx->remotefd is -1
    
    3. Client re-establishes connection. After handshake, it reopens the dir
    and sets fdctx->remotefd to a valid fd in client3_3_reopendir_cbk().
    
    4. Meanwhile, shd sends a fd unref after it is done with the opendir.
    This triggers a releasedir (since fd->refcount becomes 0).
    
    5. client3_3_releasedir() sees that fdctx-->remotefd is a valid number
    (i.e not -1), sets fdctx->released=1 and calls  client_fdctx_destroy()
    
    6. As a continuation of step3, client_reopen_done() is called by
    client3_3_reopendir_cbk(), which sees that fdctx->released==1 and
    again calls client_fdctx_destroy().
    
    Depending on when step-5 does GF_FREE(fdctx), we may crash at any place in
    step-6 in client3_3_reopendir_cbk() when it tries to access
    fdctx->{whatever}.
    
    Change-Id: Ia50873d11763e084e41d2a1f4d53715438e5e947
    BUG: 1418629
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16521
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c6304c339104b0655473ee928659fdc4fa7cb2d9
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Feb 9 21:12:17 2017 +0530

    cluster/dht: Use int8 instead of string to pass DHT_IATT_IN_XDATA_KEY
    
    It is sufficient to pass an int value as opposed to a "yes" against the
    DHT_IATT_IN_XDATA_KEY key since all posix cares about is whether the
    key is present in the dict or not. Also note that this patch does not
    violate backward compatibility since the handling of the key in posix
    remains untouched.
    
    Change-Id: I2f881494a257488709c8c1d2002f2d124ddcc089
    BUG: 1390050
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: https://review.gluster.org/16591
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3ec11e0d2fbff4e8e8cbda0aac6d7b4603722e48
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Feb 8 15:21:46 2017 -0500

    libglusterfs+changetimerecorder: reduce log noise
    
    The logging about translator options is so verbose that it
    significantly slows down scalability tests - sometimes even to the
    point where it induces timing-related failures.  Quiet, please.
    
    Change-Id: If0766e2a80746bba586e67e6019ff7084d68b425
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16569
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>

commit e02c418ebf2b25cbefc3de83b6fc84215e5917b7
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Feb 9 09:53:51 2017 -0500

    tests: reenable trash.t
    
    Now that the underlying bug has been fixed (by d97e63d0) we can allow
    the test to run again.
    
    Change-Id: If9736d142f414bf9af5481659c2b2673ec797a4b
    BUG: 1420434
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16584
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit f1c6ae24361b1bf39794a34ea35a0202a6b49fa6
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Feb 3 10:51:21 2017 -0500

    glusterd: keep snapshot bricks separate from regular ones
    
    The problem here is that a volume's transport options can change, but
    any snapshots' bricks don't follow along even though they're now
    incompatible (with respect to multiplexing).  This was causing the
    USS+SSL test to fail.  By keeping the snapshot bricks separate
    (though still potentially multiplexed with other snapshot bricks
    including those for other volumes) we can ensure that they remain
    unaffected by changes to their parent volumes.
    
    Also fixed various issues with how the test waits (or more precisely
    didn't) for various events to complete before it continues.
    
    Change-Id: Iab4a8a44fac5760373fac36956a3bcc27cf969da
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16544
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>

commit 421a098d2acfd4b837d4c03ea6f69987c670d3f7
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 9 16:09:08 2017 +0530

    cli: add integer check for timeout option
    
    Change-Id: Ia9f2d343e0a9ad13af1a62abe8946d646d36b3bb
    BUG: 1420697
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16578
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit 0e03336a9362e5717e561f76b0c543e5a197b31b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jan 30 09:54:16 2017 +0530

    afr: all children of AFR must be up to resolve s-brain
    
    Problem:
    The various split-brain resolution policies (favorite-child-policy based,
    CLI based and mount (get/setfattr) based) attempt to resolve split-brain
    even when not all bricks of replica are up. This can be a problem when
    say in a replica 3, the only good copy is down and the other 2 bricks
    are up and blame each other (i.e. split-brain). We end up healing the
    file in such a  case and allow I/O on it.
    
    Fix:
    A decision on whether the file is in split-brain or not must be taken
    only if we are able to examine the afr xattrs of *all* bricks of a given
    replica.
    
    Change-Id: Icddb1268b380005799990f5379ef957d84639ef9
    BUG: 1417522
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: https://review.gluster.org/16476
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 55625293093d485623f3f3d98687cd1e2c594460
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 9 12:56:38 2017 +0530

    glusterd: ignore return code of glusterd_restart_bricks
    
    When GlusterD is restarted on a multi node cluster, while syncing the
    global options from other GlusterD, it checks for quorum and based on
    which it decides whether to stop/start a brick. However we handle the
    return code of this function in which case if we don't want to start any
    bricks the ret will be non zero and we will end up failing the import
    which is incorrect.
    
    Fix is just to ignore the ret code of glusterd_restart_bricks ()
    
    Change-Id: I37766b0bba138d2e61d3c6034bd00e93ba43e553
    BUG: 1420637
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16574
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9385d3409054f21c7b936ad62b9a67728c31d839
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 9 10:13:20 2017 +0530

    glusterd: set default GLUSTERD_QUORUM_RATIO_KEY value to 51
    
    The default value of GLUSTERD_QUORUM_RATIO_KEY is set to 0, while this
    doesn't harm any functionality as the actual quorum calculation logic
    always take the factor that if the key is not set in the dictionary the
    value is considered to be 51 but from an user perspective it gives an
    incorrect output through volume get where quorum-ratio is always shown as
    0 until reconfigured.
    
    Change-Id: I087712fa4736055859f29cc3bdbb3b111cbe7224
    BUG: 1420611
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16572
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 824a48fb5ce20e26ed78b26afd81ec876bc826ec
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 9 10:28:55 2017 +0530

    glusterd: put null check for mod_dict in build_shd_graph
    
    Change-Id: I849f5f7eb5932d2dc2a76f8abc61e41231f9883e
    BUG: 1420614
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16573
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 2199c688b73dfe90868f9469f92e21b0e0795e57
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Feb 8 19:45:46 2017 -0500

    libglusterfs: fix serious leak of xlator_t structures
    
    There's a lot of logic (and some long comments) around how to free
    these structures safely, but then we didn't do it.  Now we do.
    
    Change-Id: I9731ae75c60e99cc43d33d0813a86912db97fd96
    BUG: 1420571
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16570
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 1e4f9c58a1b013f3f27d515d72d1e76e1a53436e
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Feb 8 10:48:55 2017 -0500

    trash: fix problem with trash feature under multiplexing
    
    With multiplexing, the trash translator gets a reconfigure call before
    a notify(CHILD_UP).  In this case, priv->trash_itable was not yet
    initialized, so the reconfigure would get a SEGV.  Moving the itable
    allocation to init seems to fix it, so trash can be reenabled.
    
    Change-Id: I21ac2d7fc66bac1bc4ec70fbc8bae306d73ac565
    BUG: 1420434
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16567
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 9ac193a19b0ca6d6548aeafa5c915b26396f8697
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Feb 8 12:20:55 2017 +0530

    glusterd: glusterd is crashed at the time of stop volume
    
    Problem: glusterd is crashed at the time of stop volume due to
             overflow of pidfile array after build rpm with default options.
    
    Solution: To avoid the crash update the pidfile array size.
    
    Test:    To test the patch followed below procedure
             1) Setup 1*2 environment and start the volume
             2) Stop the volume
             Before apply the patch glusterd is crashed.
    
    Note:  The crash is happened only after build rpm with rpmbuild -ba
           <spec> because _FORTIFY_SOURCE is enabled. This option tries to
           figure out possible overflow scenarios like the bug here and
           crash the process.
    
    BUG: 1420202
    Change-Id: I58a006bc0727843a7ed02a10b4ebd5dca39eae67
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/16560
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c57808c4e36547233d20e31b54c818c8d77fa646
Author: Richard Wareing <rwareing@fb.com>
Date:   Fri Dec 11 21:03:40 2015 -0800

    afr/cluster: Restore data-self-heal-window option
    
    Summary:
    - Fixes a bug where data-self-heal-window was ignored and instead
      hard-coded to 128k
    - Cherry-pick of D2752781
    
    Test Plan:
    - Prove tests
    
    Reviewed By: sshreyas
    
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    
    Change-Id: Ie38456ce9ad90921f7456fe02aaace88393433a9
    BUG: 1404424
    Reviewed-on-release-3.8-fb: http://review.gluster.org/16083
    Tested-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-by: Kevin Vigor <kvigor@fb.com>
    Reviewed-on: https://review.gluster.org/16123
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4a7fd196d4a141f2b693d5b49995733f6ad1776f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Feb 2 10:22:00 2017 -0500

    tests: fix online_brick_count for multiplexing
    
    The number of brick processes no longer matches the number of bricks,
    therefore counting processes doesn't work.  Counting *pidfiles* does.
    Ironically, the fix broke multiplex.t which used this function, so it
    now uses a different function with the old process-counting behavior.
    Also had to fix online_brick_count and kill_node in cluster.rc to be
    consistent with the new reality.
    
    Change-Id: I4e81a6633b93227e10604f53e18a0b802c75cbcc
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16527
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3cbf73225111b2fd04414f1fa0aea33ffedf10b2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Feb 7 09:17:47 2017 -0500

    packaging: python/python2(/python3) cleanup, again
    
    mistake missed in the previous patches
    
    see https://review.gluster.org/#/c/16486/ and
    https://review.gluster.org/#/c/16428/
    
    BUG: 1414902
    Change-Id: Ie0839fa00794986f7f6a742dff70acd242e68735
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16556
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 3c86d946086fda97b38f1a28682840adacbbf800
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 2 13:37:31 2017 +0530

    tests : turn off nfs.disable in bug-1238706-daemons-stop-on-peer-cleanup.t
    
    To validate this test and remove it from the list of bad tests, turn off
    nfs.disable option so that nfs daemon can come up.
    
    Change-Id: I8146c2d7f72ac53cac7e395dbb9e819d729eb6a9
    BUG: 1257792
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16514
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cafdab5e13d74130abab6dca4267778d22d7d7f4
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Feb 1 10:01:26 2017 +0100

    extras/rebalance.py: Fix statvfs for FreeBSD in python
    
    FreeBSD doesn't return the block size in f_bsize as linux does. It
    returns the optimal I/O size, so we need to consider this to avoid
    invalid results. On FreeBSD we take f_frsize as the block size.
    
    Change-Id: I72083d8ae183548439de874c77f1d60d9c2d14a7
    BUG: 1356076
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/16498
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 563cafb5a5e742fc7fd2c175b332f0000c053040
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Jan 24 14:24:47 2017 +0530

    CLI/TIER: removing old tier commands under rebalance
    
    PROBLEM: gluster v rebalance <volname> tier start works even after
    the switch of tier to service framework.
    This lets the user have two tierd for the same volume.
    
    FIX: checking for each process will make the new code hard
    to maintain. So we are removing the support for old commands.
    
    Change-Id: I5b0974b2dbb74f0bee8344b61c7f924300ad73f2
    BUG: 1415590
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/16463
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f2133923b8d8851943c5676b88c5ce67725eabe5
Author: hari gowtham <hgowtham@redhat.com>
Date:   Fri Feb 3 15:55:47 2017 +0530

    Tier: remove warning related to the enum
    
    PROBLEM: In the tier as a service patch the enums for tier (from
    gf1_op_command and gf_defrag_command) are put into a single enum
    gf_defrag_command which causes a warning that will make the build
    fail.
    
    FIX: send both the enum and eliminate the warning.
    
    Change-Id: I899ff622dfb07134e6459aa65f65ea7252765293
    BUG: 1418973
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: https://review.gluster.org/16539
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit a3a38bb9cd2c17bd955489ae87800f398ef10239
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Wed Feb 1 19:15:29 2017 +0530

    Fixes quota list when stale gfid exist in quota.conf
    
    when an rmdir is done, the gfid corresponding to the dir remains
    in quota.conf (if a limit was configured on the dir). The quota
    list should ignore them and print the remaining limits. In case
    the last gfid in quota.conf happened to be stale, the print code
    was getting skipped. Refactored the code to ensure printing happens.
    
    Change-Id: I3ac8e8a7a62d34e1fa8fd2734419459112c71797
    BUG: 1418259
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Reviewed-on: https://review.gluster.org/16507
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333@gmail.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b3188c61d248526a070b1b18df1ea1d181b349d6
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Thu Jan 5 23:58:21 2017 +0530

    socket: GF_REF_PUT should be called outside lock
    
    GF_REF_PUT was called inside lock which can call
    socket_poller_mayday which inturn tries to take the
    same lock. This can lead to deadlock scenario.
    
    BUG: 1410701
    Change-Id: Ib3b161bcfeac810bd3593dc04c10ef984f996b17
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: https://review.gluster.org/16343
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit ddf05f3d1e39cc920251c809e9ba42fe42b2c5f2
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jan 23 22:19:01 2017 +0530

    cluster/dht: Don't update layout in rebalance_task_completion
    
    Updating the layout in the dht inode_ctx in
    rebalance_task_completion after the file is migrated
    is erroneous in case of files with hardlinks.
    This step can be skipped as the layout will be set
    in the syncop_lookup call post the migration in
    dht_migrate_file.
    
    Change-Id: I24ac798a919585d91a117d6a207e6a31b88486c6
    BUG: 1415761
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: https://review.gluster.org/16457
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>

commit 6bd86b7085098c79ee6a50015fe89a8b18608cbf
Author: menakamohan <menaka.m@outlook.com>
Date:   Tue Jan 31 17:14:30 2017 +0530

    Added the missing FOPs in the io-stats xlator
    
    The following FOPs are not implemented in the io-stats xlator.
    1)fentrylk
    2)compound
    3)seek
    4)lease
    5)getactivelk
    6)setactivelk
    
    Added the missing FOPs to the io-stats xlator
    
    Change-Id: I4577f82ec906f1b88327c484cd9a6f356d578125
    BUG: 1416520
    Signed-off-by: menakamohan <menaka.m@outlook.com>
    Reviewed-on: https://review.gluster.org/16490
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit ff075a3d6f9b142911d25c27fd209838782bfff0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Feb 1 15:04:08 2017 +0530

    glusterd : do not load io-threads in client graph for replicate volumes
    
    client.io-threads has been turned on by default from release-3.9 onwards,
    however this has an adverse effects on replicate volumes due to the design
    limitations on replications, till that gets addressed through server side
    replication as a preventive measure it is wiser not to load io-threads in the
    client graph for replicate volumes.
    
    Change-Id: Ibc576d4517da23fcdf55c6f4d17b90152a8817d7
    BUG: 1418014
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16502
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 75c398d396bcd4a50a5bdbe350d2de9d53ebac09
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Feb 1 17:11:46 2017 +0530

    extras: Provide group set for md-cache and invalidation options
    
    To enable the integration of md-cache and invalidation features
    we need to perform 3 volume set options in a specific order.
    In order to ease this for user provide a group volume set option.
    
    Usage: gluster vol set <VOLNAME> group metadata-cache
    
    Change-Id: I9bf0fd4217aa2a1c7ffbdc93e879b10f87addeac
    BUG: 1418249
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16503
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 22f02d8f1dcdf176744ab1536cb23a5fcd291243
Author: Vitaly Lipatov <lav@etersoft.ru>
Date:   Tue Jan 31 21:18:05 2017 +0300

    md-cache: initialize mdc_counter.lock
    
    add missed LOCK_INIT to fix INCREMENT_ATOMIC on
    conf->mdc_counter.lock when pthread_spin_* using
    
    Change-Id: I680bd6f41e3b8a1852ed969bf6794cbf4c1ccdd4
    BUG: 1417913
    Signed-off-by: Vitaly Lipatov <lav@etersoft.ru>
    Reviewed-on: https://review.gluster.org/16515
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b4aac5d334d5102ef3b935a200502cfcd63bd12c
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Feb 2 13:08:04 2017 -0500

    glusterd: double-check brick liveness for remove-brick validation
    
    Same problem as https://review.gluster.org/#/c/16509/ in a different
    place.  Tests detach bricks without glusterd's knowledge, so
    glusterd's internal brick state is out of date and we have to re-check
    (via the brick's pidfile) as well.
    
    BUG: 1385758
    Change-Id: I169538c1c62d72a685a49d57ef65fb6c3db6eab2
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16529
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 1e849f616f6ae2f97ab307abaff69182c87571ca
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Feb 2 11:41:06 2017 -0500

    tests: use kill_brick instead of kill -9
    
    The system actually handles this OK, but with multiplexing the result
    of killing the whole process is not what some tests assumed.
    
    Change-Id: I89ebf0039ab1369f25b0bfec3710ec4c13725915
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16528
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5a57c1592a34ee6632ca1fb38e076dde381d1ae2
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Feb 1 22:00:32 2017 -0500

    socket: retry connect immediately if it fails
    
    Previously we relied on a complex dance of setting flags, shutting
    down the socket, tearing stuff down, getting an event, tearing more
    stuff down, and waiting for a higher-level retry.  What we really
    need, in the case where we're just trying to connect prematurely e.g.
    to a brick that hasn't fully come up yet, is a simple retry of the
    connect(2) call.
    
    This was discovered by observing failures in ec-new-entry.t with
    multiplexing enabled, but probably fixes other random failures as
    well.
    
    Change-Id: Ibedb8942060bccc96b02272a333c3002c9b77d4c
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16510
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit ae47befebeda2de5fd2d706090cbacf4ef60c785
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Oct 14 10:04:07 2016 -0400

    libglusterfs: make memory pools more thread-friendly
    
    Early multiplexing tests revealed *massive* contention on certain
    pools' global locks - especially for dictionaries and secondarily for
    call stubs.  For the thread counts that multiplexing can create, a
    more lock-free solution is clearly needed.  Also, the current mem-pool
    implementation does a poor job releasing memory back to the system,
    artificially inflating memory usage to match whatever the worst case
    was since the process started.  This is bad in general, but especially
    so for multiplexing where there are more pools and a major point of
    the whole exercise is to reduce memory consumption.
    
    The basic ideas for the new design are these
    
      There is one pool, globally, for each power-of-two size range.
      Every attempt to create a new pool within this range will instead
      add a reference to the existing pool.
    
      Instead of adding pools for each translator within each multiplexed
      brick (potentially infinite and quite possibly thousands), we
      allocate one set of size-based pools per *thread* (hundreds at
      worst).
    
      Each per-thread pool is divided into hot and cold lists.  Every
      allocation first attempts to use the hot list, then the cold list.
      When objects are freed, they always go on the hot list.
    
      There is one global "pool sweeper" thread, which periodically
      reclaims everything in each pool's cold list and then "demotes" the
      current hot list to be the new cold list.
    
      For normal allocation activity, only a per-thread lock need be
      taken, and even that only to guard against very rare contention from
      the pool sweeper.  When threads start and stop, a global lock must
      be taken to add them to the pool sweeper's list.  Lock contention is
      therefore extremely low, and the hot/cold lists also provide good
      locality.
    
    A more complete explanation (of a similar earlier design) can be found
    here:
    
     http://www.gluster.org/pipermail/gluster-devel/2016-October/051160.html
    
    Change-Id: I5bc8a1ba57cfb553998f979a498886e0d006e665
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/15645
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 984c470159a68114be2a260412cfefe2c158ab99
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Feb 1 04:04:28 2017 -0500

    extras: glusterfs-mode.el has incorrect FSF address
    
    found by rpmlint on OpenSuSE Build Service
    
    And convert DOS crlf to Unix lf, also found by SuSE rpmlint
    
    Change-Id: I0329e6682333ead21ca1b76a3b00cb863c2af51b
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16500
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 72452e07fcf91627afb6d45b921dfefd2610686f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Feb 1 21:54:30 2017 -0500

    glusterd: double-check whether brick is alive for stats
    
    With multiplexing, our tests detach bricks from their host processes
    without glusterd being involved.  Thus, when we ask glusterd to fetch
    profile info, it will try to fetch from a brick that's actually not
    present any more.  While it can handle the process being dead and its
    RPC connection being closed, it barfs if it gets a negative response
    from a live brick process.  This is not a problem in normal use,
    because the brick can't disappear without glusterd seeing it.  The fix
    is to double check that the brick is actually running, by looking for
    its pidfile which the tests *do* clean up as part of killing a brick.
    
    Change-Id: I098465b175ecf23538bd7207357c752a2bba8f4e
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/16509
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit b0012f81089258dc0b864db4b34afc3205c265df
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Feb 2 15:54:10 2017 +0530

    glusterfsd/gf_attach: Remove unused varibale
    
    Change-Id: I1f2ae36c91bd0880a7f15aa73b7e0f462c7e7952
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: https://review.gluster.org/16517
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit db80efc8d5cc24597de636d8df2e5a9ce81d670d
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Fri Jan 13 13:54:35 2017 +0100

    cluster/ec: fix selinux issues with mmap()
    
    EC uses mmap() to create a memory area for the dynamic code. Since
    the code is created on the fly and executed when needed, this region
    of memory needs to have write and execution privileges.
    
    This combination is not allowed by default by selinux. To solve the
    problem a file is used as a backend storage for the dynamic code and
    it's mapped into two distinct memory regions, one with write access
    and the other one with execution access. This approach is the
    recommended way to create dynamic code by a program in a more secure
    way, and selinux allows it.
    
    Additionally selinux requires that the backend file be stored in a
    directory marked with type bin_t to be able to map it in an executable
    area. To satisfy this condition, GLUSTERFS_LIBEXECDIR has been used.
    
    This fix also changes the error check for mmap(), that was done
    incorrectly (it checked against NULL instead of MAP_FAILED), and it
    also correctly propagates the error codes and makes sure they aren't
    silently ignored.
    
    Change-Id: I71c2f88be4e4d795b6cfff96ab3799c362c54291
    BUG: 1402661
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/16405
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 85d7f1d1ee24ac400d4aa223478727643532693a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Jan 20 16:09:13 2017 +0530

    performance/write-behind: access stub only if available during
    statedump
    
    Change-Id: Ia5dd718458a5e32138012f81f014d13fc6b28be2
    BUG: 1415115
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/16440
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit c8a23cc6cd289dd28deb136bf2550f28e2761ef3
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Oct 27 11:51:47 2016 -0400

    libglusterfs+transport+io-threads: fix 256KB stack abuse
    
    Some functions were allocating 64K booleans, which are (crazily) mapped to
    4-byte ints, for a total of 256KB per call.  Changed to use bitfields instead,
    so usage is now only 8KB per call.  This was the impediment to changing the
    io-threads stack size, so that has been adjusted too.
    
    Change-Id: I8781c4f2c8f2b830f4535e366995fac8dd0a8653
    BUG: 1418095
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/15745
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit d7077bca4b372a056d23416294e729637e9af94e
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Feb 1 15:17:51 2017 +0530

    rpc/socket.c : Bonnie++ hangs during rewrites in ganesha + SSL
    
    Problem: Bonnie++ rewrite operation hangs in ganesha + SSL environment
    
    Solution: Bonnie++ hangs during execution of rewrite operation in
              ganesha + SSL environment.It was hanged due to blocking on poll
              call in ssl_do because no POLLOUT event was getting on socket.
              Socket is not getting POLLOUT event because all other threads
              are waiting to get lock and lock is not released ssl_do
              because it is not getting any event on poll.To correct it
              update the condition in ssl_do as same in getting error
              SSL_ERROR_WANT_READ.
    
    Test:     To test the patch followed below procedure
              1) Setup 2X2 Ganesha + SSL environment.
              2) Run bonnie from 3 nfs client parallely
              3) After run "Rewwrite operation" by bonnie it is hanged.
              4) After apply the patch it is not hanged.
    
    BUG: 1418213
    Change-Id: I5985cbbc4cfdac5d287268d791e31c274abc3c8d
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: https://review.gluster.org/16501
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 12f4db5742b334e2364afeb69a64eeeac4e6c147
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jan 31 04:03:51 2017 -0500

    packaging: python/python2(/python3) cleanup, again
    
    missed a couple things in the previous patch
    
    Change-Id: I0ebd5c431abd9af5e1b680ad52318219edb4bfa7
    BUG: 1414902
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16486
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 7292905c3a3291a98b55b36aed713a10553d7523
Author: Michael Adam <obnox@samba.org>
Date:   Wed Dec 7 07:45:57 2016 +0100

    glusterd: fix compiler warning (unused var) if bd xlator is not enabled
    
    BUG: 1402254
    
    Change-Id: Id4450c5e00e9eb6d63dcdf65b0a13bc535a32d98
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: https://review.gluster.org/16049
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f2ca301bd741e3e3f076cd3f72fcd377bcef2a1a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 26 16:45:51 2017 +0100

    refcount: typecast function for calling on free
    
    All of the functions called to free the refcounted structure are doing a
    typecast from (void*) to their own type taht is being free'd. This
    really is not needed and the refcount interface is made a little simpler
    without the requirement of typecasting.
    
    With this small improvement in the API, all callers are updated too.
    
    Change-Id: I32473b6d1799f62861d4b2d78ea30c09e6c80ab1
    BUG: 1416889
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: https://review.gluster.org/16471
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 1a95fc3036db51b82b6a80952f0908bc2019d24a
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Dec 8 16:24:15 2016 -0500

    core: run many bricks within one glusterfsd process
    
    This patch adds support for multiple brick translator stacks running
    in a single brick server process.  This reduces our per-brick memory usage by
    approximately 3x, and our appetite for TCP ports even more.  It also creates
    potential to avoid process/thread thrashing, and to improve QoS by scheduling
    more carefully across the bricks, but realizing that potential will require
    further work.
    
    Multiplexing is controlled by the "cluster.brick-multiplex" global option.  By
    default it's off, and bricks are started in separate processes as before.  If
    multiplexing is enabled, then *compatible* bricks (mostly those with the same
    transport options) will be started in the same process.
    
    Change-Id: I45059454e51d6f4cbb29a4953359c09a408695cb
    BUG: 1385758
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/14763
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7f7d7a939e46b330a084d974451eee4757ba61b4
Author: Ryan Ding <ryan.ding@open-fs.com>
Date:   Tue Aug 23 17:28:44 2016 +0800

    features/changelog: fix a bug in changelog_rpc_server_destroy
    
    the programe unregister loop never get moved forward, it's a dead loop.
    to resolve it, add progs++ in the loop.
    
    Change-Id: Ib25ded10b3ce808e2fb57b13d767833f24cf01a7
    BUG: 1369393
    Signed-off-by: Ryan Ding <ryan.ding@open-fs.com>
    Reviewed-on: https://review.gluster.org/15292
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2e0dceb6165d0a93581284fa2e0d74abe4ee615b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Dec 2 15:24:46 2016 -0500

    features/bit-rot-stub: use the correct spelling of quarantine for bad objects
                           container
    
    The directory for containing the list of bad objects was named "quanrantine"
    instead of "quarantine"
    
    Change-Id: I8c20381ac637201d9d1a224f5223e8dfbed53f1e
    BUG: 1401571
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: https://review.gluster.org/16027
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit faf43235e0b3308388d0146e65b3982c11661db0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jan 30 13:13:54 2017 +0530

    tests: Mark tests/bitrot/bug-1373520.t bad
    
    Change-Id: Ief8014dd9faa012c7f3c5347f597a155873a8f92
    BUG: 1417540
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16479
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fbe70dcdd7c62ae97e04e09755dcf87d90fcad8b
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Jan 17 18:26:55 2017 +0530

    gNFS : pass proper gfid for nfs_setattr() in nfs3svc_create_cbk()
    
    The nfs3svc_create_cbk() takes "gfid" from inode variable which it
    received, not from inode which it performed linking to nfs_setattr().
    There is possiblity that the inode passed into this function holds
    NULL gfid if there are some parallel operation happening on the same
    file.
    
    Similar issue is mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1413971
    Thanks pranith for proposing the fix
    
    Change-Id: I1a0ff4f02b483416f19f4f064c306c2cad5d9d8b
    BUG: 1413971
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: https://review.gluster.org/16421
    Reviewed-by: soumya k <skoduri@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 355c1955039a39c820880be72fe77d4e74af0967
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Jan 16 15:27:09 2017 +0530

    tools/glusterfind: delete temporary folder
    
    Problem:
    Run specific temporary folder created under
    /usr/var/lib/misc/glusterfsd/glusterfind/<session>/<volume>/
    remains undeleted.
    
    Solution:
    Delete the temporary folder from all nodes.
    
    Change-Id: I0edaf868aebb01b15c489434bbb26fe853351384
    BUG: 1413526
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: https://review.gluster.org/16416
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit f2406fa6155267fa747d9342092ee7709a2531a9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jan 27 16:17:49 2017 +0530

    cluster/ec: Fix cthon failures observed with ec volumes
    
    Since EC already winds one write after other there is no need to align
    application fcntl locks with ec blocks. Also added this locking to be
    done as a transaction to prevent partial upgrade/downgrade of locks
    happening.
    
    BUG: 1410425
    Change-Id: I7ce8955c2174f62b11e5cb16140e30ff0f7c4c31
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: https://review.gluster.org/16445
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 33f8703a12dd97980c43e235546b04dffaf4afa0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jan 23 13:03:06 2017 +0530

    glusterd: regenerate volfiles on op-version bump up
    
    Change-Id: I2fe7a3ebea19492d52253ad5a1fdd67ac95c71c8
    BUG: 1416251
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/16455
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 23a9385953e6b2f05508d9ef85bbbb2200f18fe2
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Jan 27 11:31:40 2017 +0530

    cluster/ec: Change level of messages to DEBUG
    
    Heal failed or passed should not be logged as warning.
    These can be observed from heal info if the heal is
    happening or not. If we require to debug a case where
    heal is not happening, we can set the level to DEBUG.
    
    Change-Id: I347665c8c8b6223bb08a9f3dd5643a10ddc3b93e
    BUG: 1417050
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/16473
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a9f660bc9d2d7c87b3306a35a2088532de000015
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Oct 5 14:59:51 2016 +0530

    glusterd: daemon restart logic should adhere server side quorum
    
    Just like brick processes, other daemon services should also follow the same
    logic of quorum checks to see if a particular service needs to come up if
    glusterd is restarted or the incoming friend add/update request is received
    (in glusterd_restart_bricks () function)
    
    Change-Id: I54a1fbdaa1571cc45eed627181b81463fead47a3
    BUG: 1383893
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: https://review.gluster.org/15626
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit a3b4c70afee89536374f6fa032465cc313437956
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Jan 24 14:18:03 2017 +0530

    performance/write-behind: do __wb_request_unref within locks
    
    Since __wb_request_unref can remove the request from various lists,
    calling it without holding wb_inode->lock results in corruptions when
    other threads simultaneously try to access the lists this request is
    part of.
    
    Thanks to "Nithya Balachandran" <nbalacha@redhat.com> for pointing out
    the bug.
    
    Change-Id: I78fb6433c2e212500d07780f7b45c5a0e2bf9209
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: https://review.gluster.org/16464
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 9e2d7faf598078d12a47512abae6792adbe01aca
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jan 26 10:24:32 2017 +0100

    cluster/ec: mark ec-background-heal.t as bad
    
    Change-Id: I0c54c62cdeb40b983da2392296762471a5474652
    BUG: 1416689
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: https://review.gluster.org/16470
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 07b34dd5c2f2c6eed4669472dd5af1063f4f224b
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Jan 12 14:48:28 2017 +0530

    tests/include : EXPECT_WITHIN takes full time even if expression matches
    
    Problem: For all the tests using get_pending_heal_count, EXPECT_WITHIN
    is taking full time given to it even if the heal count matches with
    expected value.
    
    Solution:
    RC - In most of the tests, to check heal count, wildcards are
    being used. In EXPECT_WITHIN, in if condition, when we use it in
    double quotes (" "), it gives string with wildcards which does not
    match with the output of get_pending_heal_count.
    For example, (0 =~ ^0$).
    So, "while" loop was running for full time and at the end, after
    coming out of loop, in next if condition it was matching with the
    expression without quotes. That is why it was passing.
    
    Remove double quotes in "if condition" in EXPECT_WITHIN and match
    as we are matching it in test_expect_footer.
    
    Change-Id: Ia161594774d05b9b888efb2f7ed1950590d8ac1b
    BUG: 1412549
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: https://review.gluster.org/16382
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit e2525785e026d209845b939b9d02048d3004920d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 6 12:58:02 2017 +0100

    gfapi: create statedump when glusterd requests it
    
    When GlusterD sends the STATEDUMP procedure to the libgfapi client, the
    client checks if it matches the PID that should take the statedump. If
    so, it will do a statedump for the glfs_t that is connected to this mgmt
    connection.
    
    BUG: 1169302
    Change-Id: I70d6a1f4f19d525377aebc8fa57f51e513b92d84
    See-also: http://review.gluster.org/9228
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    [ndevos: separated patch from 9228]
    Reviewed-on: https://review.gluster.org/16415
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 7c6538f6c8f9a015663b4fc57c640a7c451c87f7
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Dec 8 16:08:40 2016 +0530

    Readdir-ahead : Honor readdir-optimise option of dht
    
    Change-Id: I9c5e65b32e316e6a2fc7e1f5c79fce79386b78e2
    BUG: 1401812
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16071
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit f2e7b6800b812e8bbc9bdbcea4c400a1784e31dc
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jan 22 11:44:21 2016 -0500

    glusterd: add a cli command to trigger a statedump on a client
    
    With this, we will be able to trigger statedumps on remote Gluster
    clients, mainly targetted for applications using libgfapi.
    
    Design:
    SIGUSR signal is the most comman way of taking a statedump in Gluster.
    But it cannot be used for libgfapi based processes, as the process
    loading the library might have already consumed SIGUSR signal. Hence
    going by the command way.
    
    One has to issue a Gluster command to initiate a statedump on the
    libgfapi based client. The command takes hostname and PID as an
    argument. All the glusterds in the cluster, check if they are connected
    to the specified hostname, and send an RPC request to all the connected
    clients from that hostname (via the mgmt connection).
    
    URL: http://review.gluster.org/16357
    Change-Id: Icbe4d2f026b32a2c7d5535e1bfb2cdaaff042e91
    BUG: 1169302
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    [ndevos: minor fixes and split patch in smaller pieces]
    Reviewed-on: https://review.gluster.org/9228
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit 4008a48080b9910b9948c35892e762e91198d134
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jan 18 12:51:19 2017 -0500

    packaging: python2 cleanup
    
    Update to current python2 (vs. python3) guidelines.
    
    While doing package review of new python-glusterfs-api we
    were reminded that we should update the glusterfs.spec(.in)
    accordingly.
    
    Change-Id: I67c88f209e803425c5ef70cb8d3e7ffd8e396c7f
    BUG: 1414902
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: https://review.gluster.org/16428
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f245dc568e3c22882e22ddd3e26a4207f5704e3b
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jan 17 17:45:59 2017 +0530

    glusterd, rda: If parallel readdir is enabled, split the cache limit
    
    With patch http://review.gluster.org/#/c/16072/ readdir-ahead can be
    loaded as a child of dht. i.e. there can be more than one instance
    of readdir-ahead in client process. In this case the rda-cache-size
    should be split among all the readdir-ahead instances. Also the
    value of rda-request-size is considered as the minimum cache size
    of any readdir-ahead instance.
    
    Change-Id: Iea2fe6d4c46adc09dd2e9a252332a0fe3005f2b9
    BUG: 1401812
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: https://review.gluster.org/16424
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ac629e574935a8aed6526936bc83b1c6d295ae67
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Dec 26 14:28:22 2016 +0530

    md-cache: Cache security.ima xattrs
    
    From kernel version 3.X or greater, creating of a file
    results in removexattr call on security.ima xattr. But
    this xattr is not set on the file unless IMA feature
    is active. With this patch, removxattr call returns
    ENODATA if it is not found in the cache.
    
    Change-Id: I8136096598a983aebc09901945eba1db1b2f93c9
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/16296
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 578e9b5b5b45245ed044bab066533411e2141db6
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Jan 11 17:19:30 2017 +0530

    cluster/ec: Do not start heal on good file while IO is going on
    
    Problem:
    Write on a file has been slowed down significantly after
    http://review.gluster.org/#/c/13733/
    
    RC : When update fop starts on a file, it sets dirty flag at
    the start and remove it at the end which make an index entry
    in indices/xattrop. During IO, SHD scans this and finds out
    an index and starts heal even if all the fragments are healthy
    and up tp date. This heal takes inodelk for different types of
    heal. If the IO is for long time this will happen in every 60 seconds.
    Due to this extra, unneccessary locking, IO gets slowed down.
    
    Solution:
    Before starting  any  type of heal check if file needs heal or not.
    
    Change-Id: Ib9519a43e7e4b2565d3f3153f9ca0fb92174fe51
    BUG: 1409191
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/16377
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 07b9853ad0c92b341be33a6cd632013c416221c8
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Sep 28 17:20:19 2015 +0530

    features/trash: Create trash directory only when it is enabled
    
    Previously trash directory was being created as part of volume
    start operation. And also the user/admin could not delete this
    directory from volume even if it is not needed. This patch will
    fix the same. From now onwards creation and enforcement on trash
    directory will come into pictrure only when trash translator is
    enabled. Similarly exact same behaviour is reflected on internal-op
    directory inside trash directory.
    
    Change-Id: I3e58316a7b299a691885e458c960438bec2220fb
    BUG: 1264849
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12256
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Anoop C S <anoopcs@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 71913a3058cdf2978fc948304a361748dc8fdbc0
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Dec 6 15:34:39 2016 +0530

    dht/cluster: add logs to fix-layout code path
    
    Currently there is no helpful log in fix-layout code path. Adding
    the logs to be helpful for debugging fix-layout failures.
    
    BUG: 1414782
    Change-Id: I61c29ceedcaa2e235fa7be99866709d6ca6de3ae
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/16040
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 8b6d82e87b189794310293f032f2c9dac8961f55
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jan 9 12:45:36 2017 +0530

    debug/trace: Print entries' iatts in readdirp cbk
    
    Change-Id: Iab2b4fa44b22aad0745e9f9249d8adba0acd7de1
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16432
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 729b494b828712cba9d03395ca081666ae589bb7
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Jan 19 18:20:44 2017 +0530

    cluster/disperse: Do not log fop failed for lockless fops
    
    Problem: Operation failed messages are getting logged
    based on the callbacks of lockless fop's. If a fop does
    not take a lock, it is possible that it will get some
    out of sync xattr, iatts. We can not depend on these
    callback to psay that the fop has failed.
    
    Solution: Print failed messages only for locked fops.
    However, heal would still be triggered.
    
    Change-Id: I4427402c8c944c23f16073613caa03ea788bead3
    BUG: 1414287
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/16435
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4a11b1d8aa79bb6bd26d2a06b3c4c3a9574329d4
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Dec 6 15:53:10 2016 +0530

    ganesha/glusterd : create 'ganesha.conf' symlink for nodes in ganesha cluster
    
    Change-Id: I27503558da176f0b1a1f0953a7e7ebe86976608d
    BUG: 1401877
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/16041
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 2edd75ec8de17da89004859375844f60890a4df0
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Jan 17 15:43:47 2017 +0530

    dht/rebalance Estimate time to complete rebalance
    
    The estimates will be logged to the rebalance log on running
    gluster v rebalance <vol> status
    
    Change-Id: I9d51b139cd4c8dfde1ff2c2050720ae606c13fc6
    BUG: 1396004
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15893
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 7b5b7111c9d9a2a65e4f4d0abf832a88e021c576
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Jan 10 11:21:06 2017 +0100

    cli: keep 'gluster volume status detail' consistent
    
    The output of the command 'gluster volume status <volname> detail' is
    not consistent between operating systems. On linux hosts it shows the
    file system type, the device name, mount options and inode size of each
    brick. However the same command executed on a FreeBSD host doesn't show
    all this information, even for bricks stored on a linux.
    
    Additionally, for hosts other than linux, this information is shown as
    'N/A' many times. This has been fixed to show as much information as it
    can be retrieved from the operating system.
    
    The file contrib/mount/mntent.c has been mostly rewriten because it
    contained many errors that caused mount information to not be retrieved
    on some operating systems.
    
    Change-Id: Icb6e19e8af6ec82255e7792ad71914ef679fc316
    BUG: 1411334
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/16371
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 4e11d50f3f803e685c844da1f168a633c3834fd0
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jan 19 12:23:00 2017 +0530

    gluster: Typos in logs and comments
    
    Replaced 'recieve' with 'receive'.
    
    Change-Id: I4c1c9147db5437feb81e4c83ed074440aaa28e07
    BUG: 1414645
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/16429
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333@gmail.com>
    Tested-by: Manikandan Selvaganesh <manikandancs333@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d93a6691538270aefe7703e8f8d7c822f53528e5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 6 12:49:32 2017 +0100

    gfapi: add API to trigger events for debugging and troubleshooting
    
    Introduce glfs_sysrq() as a generic API for triggering debug and
    troubleshoot events. This interface will be used by the feature to get
    statedumps for applications using libgfapi.
    
    The current events that can be requested through this API are:
     - 'h'elp: log a mesage with all supported events
     - 's'tatedump: trigger a statedump for the passed glfs_t
    
    In future, this API can be used by a CLI to trigger statedumps from
    storage servers. At the moment it is limited to take statedumps, but it
    is extensible to set the log-level, clear caches, force reconnects and
    much more.
    
    BUG: 1169302
    Change-Id: I18858359a3957870cea5139c79efe1365a15a992
    Original-author: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/16414
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 89cf743118ab6554c7f210754e51c4921cbb60c7
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Wed Jan 18 15:56:00 2017 +0530

    Fixes upgrade issue in quota.conf
    
    When an op-version bump up is done the glusterd_store_quota_config
    upgrades the quota conf file, although overwriting the same later
    which leaves out all gfid entries. While this is warranted for
    enable opcode, for upgrade we need to retain gfids. So for upgrade
    opcode, we return once the upgrade is done.
    
    Change-Id: I2b38c6022d74b4a14dc07432651a51cc39ad5120
    BUG: 1414346
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Reviewed-on: http://review.gluster.org/16425
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 6f4811ca9331eee8c00861446f74ebe23626bbf8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jan 17 06:39:25 2017 -0500

    features/changelog: Fix htime xattr during brick crash
    
    The htime file contains the path of all the changelogs
    that is rolloved over till now. It also maintains xattr
    which tracks the latest changelog file rolloved over
    and the number of changelogs. The path and and xattr
    update happens in two different system calls. If the
    brick is crashed between them, the xattr value becomes
    stale and can lead to the failure of gf_history_changelog.
    To identify this, the total number of changelogs is being
    calculated based on htime file size and the record
    length. The above value is used in case of mismatch.
    
    Change-Id: Ia1c3efcfda7b74227805bb2eb933c9bd4305000b
    BUG: 1413967
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/16420
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit e8669dc707ffd60fea34c4b8b04f545a9169d5ee
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jan 9 10:56:13 2017 +0530

    glusterd: bypass add-brick validation with force
    
    Commit c916a2f added a validation to restrict add-brick operation if a
    replica configuration is changed and any of the bricks belonging to the
    volume is down. However we should bypass this validation with a force
    option if users really want to have add-brick to go through at the sake
    of the corner cases of data loss issue.
    
    The original problem of add-brick getting failed when layout is not set
    will still be a problem with a force option as the issue has to be taken
    care in the DHT layer.
    
    Change-Id: I0ed3df91ea712f77674eb8afc6fdfa577f25a7bb
    BUG: 1406411
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/16358
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c9239db7961afd648f1fa3310e5ce9b8281c8ad2
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Mar 15 03:14:16 2016 -0400

    inode: Add per xlator ref count for inode
    
    Debugging inode ref leaks is very difficult as there is no info
    except for the ref count on the inode. Hence this patch is first step
    towards debugging inode ref leaks. With this patch, in the statedump
    we get additional info that tells the ref count taken by each xlator
    on the inode.
    
    Change-Id: I7802f7e7b13c04eb4d41fdf52d5469fd2c2a185a
    BUG: 1325531
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13736
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ff5e91a60887d22934fcb5f8a15dd36019d6e09a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jan 10 15:39:55 2017 -0500

    geo-rep: Separate slave mount logs for each connection
    
    Geo-rep worker mounts the slave volume on the slave
    node. If multiple worker connects to same slave node,
    all workers share the same mount log file. This
    is very difficult to debug as logs are cluttered from
    different mounts. Hence creating separate mount log
    file for each connection from worker. Each connection
    from worker is identified uniquely using 'mastervol uuid',
    'master host', 'master brickpath', 'salve vol'. The log
    file name will be combination of the above.
    
    Change-Id: I67871dc8e8ea5864e2ad55e2a82063be0138bf0c
    BUG: 1412689
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/16384
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 90cb8c49787d41a46e5b86d73bdc515f54aff4c0
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Nov 2 07:22:39 2016 +0100

    fuse: limit fusermount fallback to EPERM cases
    
    There are two mount mechanims for fuse:
    1) Call mount(2) syscall directly -- implemented by fuse_mount_sys
    2) Call out to fusermount(1) helper utilty to do the mount --
       implemented by fuse_mount_fusermount
       [Note: both libfuse and glusterfs ships a variant of this helper
       utility; named, respectively, fusermount and fusermount-glusterfs.
       The two has diverged, and are not compatible at the moment.]
    
    The intended use of 1) is privileged mounting, ie. when root
    is invoking the glusterfs client. (It cannot work for non-privileged
    users as the kernel enforces privilege for mount(2), more precisely,
    caller context needs CAP_SYS_ADMIN, see capabilities(7).)
    
    The intended use of 2) is unprivileged mountig, ie. when
    the glusterfs client is invoked by an unprivileged user.
    The helper utility is a setuid binary, so it can perform
    mount(2) on behalf of the user.
    
    The main mount routine, gf_fuse_mount, calls fuse_mount_sys first,
    and if that fails, tries also with fuse_mount_fusermount. This
    is what we call "fusermount fallback". However, in the light of
    the above remarks about intended use, this logic should apply if
    the fuse_mount_fusermount fails because of a privilege shortage,
    ie. with error "Operation not permitted" (errno EPERM).
    
    So far the fallback was unconditional (masking bugs of
    fuser_mount_sys, as it happens in referred BUG). Now we
    add the "errno == EPERM" condition.
    
    BUG: 1297182
    Change-Id: Ia89d975d1e27fcfa5ab2036ba546aa8fa0d2d1b0
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/15766
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2c03c753fe77dfadb7660ecb39fe0bbb6bad026f
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Dec 8 16:48:55 2016 +0530

    glusterd: Change the volfile to have readdir-ahead as a child
              of dht
    
    As mentioned in feature page http://review.gluster.org/#/c/16090/
    readdir-ahead will be optionally placed below dht.
    
    There are two options:
    1. performance.readdir-ahead
    2. performance.parallel-readdir
    
    If only option is enabled, then readdir ahead is placed at its
    original place as an ancestor of dht. If both the options 1 and 2
    are enabled then readdir ahead is placed as a child of dht.
    
    Also changes have been made to retain the rebalance, quotad,
    snapd vol files to remain unchanged.
    
    Change-Id: I0adf0b476fcbf91251f5a2fee2241786a3d8255a
    BUG: 1401812
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/16072
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit c822e354e16646adf18bbc5123798663faa543b2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jan 6 10:37:54 2017 -0500

    storhaug HA: first step, remove resource agents and setup script
    
    resource agents and setup script(s) are now in storhaug
    
    This is a phased switch-over to storhaug. Ultimately all components
    here should be (re)moved to the storhaug project and its packages.
    But for now some will linger here.
    
    Change-Id: Ied3956972b14b14d8a76e22c583b1fe25869f8e7
    BUG: 1410843
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/16349
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 7b61434257f68749bfceee481fa505de7f945747
Author: Saurabh Badhwar <sbsaurabhbadhwar9@gmail.com>
Date:   Fri Jan 13 12:59:51 2017 +0530

    fuse: Fix a possible resource leak under GF_SOLARIS_HOST_OS
    in fuse-helpers.c
    
    Change-Id: Ie367a6dec2a0d5848631b19ebbe39ceafa954a60
    BUG: 1412918
    Signed-off-by: Saurabh Badhwar <sbsaurabhbadhwar9@gmail.com>
    Reviewed-on: http://review.gluster.org/16395
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3263d1c4f4b7efd1a018c17e1ba4dd9245094f48
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Jul 12 16:40:28 2016 +0530

    tier : Tier as a service
    
    tierd is implemented by separating from rebalance process.
    
    The commands affected:
    
    1) Attach tier will trigger this process instead of old one
    2) tier start and tier start force will also trigger this process.
    3) volume status [tier] will show tier daemon as a process instead
    of task and normal tier status and tier detach status works.
    4) tier stop implemented.
    5) detach tier implemented separately along with new detach tier
    status
    6) volume tier volname status will work using the changes.
    7) volume set works
    
    This patch has separated the tier translator from the legacy
    DHT rebalance code. It now sends the RPCs from the CLI
    to glusterd separate to the DHT rebalance code.
    The daemon is now a service, similar to the snapshot daemon,
    and can be viewed using the volume status command.
    
    The code for the validation and commit phase are the same
    as the earlier tier validation code in DHT rebalance.
    
    The “brickop” phase has been changed so that the status
    command can use this framework.
    
    The service management framework is now used.
    DHT rebalance does not use this framework.
    
    This service framework takes care of :
    
    *) spawning the daemon, killing it and other such processes.
    *) volume set options , which are written on the volfile.
    *) restart and reconfigure functions. Restart is to restart
    the daemon at two points
            1)after gluster goes down and comes up.
            2) to stop detach tier.
    *) reconfigure is used to make immediate volfile changes.
    By doing this, we don’t restart the daemon.
    it has the code to rewrite the volfile for topological
    changes too (which comes into place during add and remove brick).
    
    With this patch the log, pid, and volfile are separated
    and put into respective directories.
    
    Change-Id: I3681d0d66894714b55aa02ca2a30ac000362a399
    BUG: 1313838
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13365
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 514522d12e15e5632a0ff89785618b37dad7f5dd
Author: Michael Adam <obnox@samba.org>
Date:   Wed Dec 7 07:21:41 2016 +0100

    glusterd: remove extra space in error message
    
    BUG: 1402237
    
    Change-Id: Ib6efca655555a92a0542ef6056f3357f390eeb38
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/16048
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit afdd83a9b69573b854e732795c0bcba0a00d6c0f
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Jan 13 12:17:05 2017 +0530

    upcall: Resolve dict leak from up_(f)removexattr in upcall code path
    
    Problem: In up_(f)removexattr() dict_for_key_value() is used to create a
             new dict. This dict is not correctly unref'd and gets leaked.
    
    Solution: To avoid the leak up_(f)removexattr() now also does a
              dict_unref() on the newly created dict.
    
    While reviewing the code in up_(f)setxattr() for a similar problem, it
    was noticed that there is an extra dict created. There is no need for
    this copy, upcall_local_init() can just take the dict that was passed as
    argument to the FOP.
    
    BUG: 1412917
    Change-Id: I5bb9a7d99f5087af11c19ae722de62bdb5ad1498
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/16392
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 2041fb7872fa6672e9164fd2a12aaf80e6ef3ebd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 13 14:31:27 2017 +0100

    rpm: fix glusterfs-server(%postun) scriptlet error
    
    While introducing the usage of the %firewalld_restart macro, the old
    scriplet was not correctly removed. This causes an error to be displayed
    when the RPM gets updated or uninstalled.
    
    Fixes: f99750b4477538cd1f97ce6340e1813202f986e2
    Change-Id: I69091d8e9e3c412dc3cb52246967eac29d2ebc90
    BUG: 1410853
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/16408
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit faa5f166f2bee549ad4aeeb4d73c2856c4d703fb
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Jan 12 11:14:49 2017 +0530

    tests/distribute: remove bug-1063230.t
    
    bug-1063230.t does not add value and has diverged
    from the original BZ it was supposed to test.
    
    Change-Id: I13ae1c68c276233dd53548d1333e3eb4b936785d
    BUG: 1412467
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/16379
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 91ad7fe0ed8e8ce8f5899bb5ebbbbe57ede7dd43
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jan 10 00:30:42 2017 -0500

    geo-rep: Handle directory sync failure as hard error
    
    If directory creation is failed, return immediately before
    further processing. Allowing it to further process will
    fail the entire directory tree syncing to slave. Hence
    master will log and raise exception if it's directory
    failure. Earlier, master used to log the failure and
    proceed.
    
    Change-Id: Iba2a8b5d3d0092e7a9c8a3c2cdf9e6e29c73ddf0
    BUG: 1411607
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/16364
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 27c85d014bb7d03c323e08038d9c6db538d632fb
Author: SonaArora <sarora@redhat.com>
Date:   Fri Jan 6 14:21:56 2017 +0530

    cli/geo-rep: Fix geo-rep status detail
    
    Earlier this command works when master and slave volume args are
    given. Now it works even when no volume args are given (i.e. 'gluster
    volume geo-replication status detail) and also when master volume is given
    (i.e.'gluster volume geo-replication <master-vol> status detail').
    
    BUG: 1410071
    Signed-off-by: SonaArora <sarora@redhat.com>
    Change-Id: I1a39241a4a5d70c20b2326599b3cccd8f1f6dc78
    Reviewed-on: http://review.gluster.org/16347
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 522640be476a3f97dac932f7046f0643ec0ec2f2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Dec 30 14:57:17 2016 +0530

    afr: Avoid resetting event_gen when brick is always down
    
    Problem:
    __afr_set_in_flight_sb_status(), which resets event_gen to zero, is
    called if failed_subvols[i] is non-zero for any brick. But failed_subvols[i]
    is true even if the brick was down *before* the transaction started.
    Hence say if 1 brick is down in  a replica-3, every writev that comes
    will trigger an inode refresh because of this resetting, as seen from
    the no. of FSTATs in the profile info in the BZ.
    
    Fix:
    Reset event gen only if the brick was previously a valid read child and
    the FOP failed on it the first time.
    
    Also `s/afr_inode_read_subvol_reset/afr_inode_event_gen_reset` because
    the function only resets event gen and not the data/metadata readable.
    
    Change-Id: I603ae646cbde96995c35db77916e2ed80b602a91
    BUG: 1409206
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/16309
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 79b3fb6e8d3c9d681917be6e6c9f6ba04eb73f82
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jan 12 08:38:50 2017 +0100

    fuse: fix memory leak in setxattr
    
    If there's some failed check in setxattr of mount/fuse before
    actually starting the operation, a fuse_state_t structure is
    leaked.
    
    This fix correctly releases allocated resources in case of
    error.
    
    Change-Id: I8b1cda67a613c13b6bc38947352e2ccfccf96a1d
    BUG: 1412174
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/16380
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2010eedfe8edbb9842d022b93d6bf2a5226cedc0
Author: Patrick Uiterwijk <patrick@puiterwijk.org>
Date:   Tue Jan 10 23:52:13 2017 +0000

    Make getvolfile.py example pep8 compliant
    
    Change-Id: I7d3c1e871b9fa3859745f4d67acf05f16c7ccf5f
    BUG: 1412002
    Signed-off-by: Patrick Uiterwijk <patrick@puiterwijk.org>
    Reviewed-on: http://review.gluster.org/16372
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b3fbd95233b5f6db6ae0921c4917316175a1d082
Author: Patrick Uiterwijk <patrick@puiterwijk.org>
Date:   Wed Jan 11 00:04:47 2017 +0000

    MAINTAINERS: src.fedoraproject.org is the new location and uses https
    
    Change-Id: I7797ffa3df7a7174a2837a20fd708fa919db537b
    BUG: 1411999
    Signed-off-by: Patrick Uiterwijk <patrick@puiterwijk.org>
    Reviewed-on: http://review.gluster.org/16373
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2e5383266869c13ee27ceaee5b24b686e2415df4
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Wed Dec 28 20:33:54 2016 +0530

    glusterd: Add info on op-version for clients in vol status output
    
    Currently the `gluster volume status <VOLNAME|all> clients` command
    gives us the following information on clients:
    1. Brick name
    2. Client count for each brick
    3. hostname:port for each client
    4. Bytes read and written for each client
    
    There is no information regarding op-version for each client. This
    patch adds that to the output.
    
    Change-Id: Ib2ece93ab00c234162bb92b7c67a7d86f3350a8d
    BUG: 1409078
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/16303
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 84271e12efb783bfc83133329b0fd18aba729c84
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jan 12 14:19:31 2017 +0530

    Upcall: Fix possible memleak when inode_ctx_set fails
    
    In __upcall_inode_ctx_set(), if inode_ctx_set fails we should
    free allocated memory for ctx. This patch takes care of the same.
    
    Change-Id: Iafb42787151a579caf6f396c9b414ea48d16e6b4
    BUG: 1412489
    Reported-by: Nithya Balachandran <nbalacha@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/16381
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 5b24934668adb89e1dcd3888ac19555056508f06
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 10 13:26:02 2017 +0530

    cluster/afr: Do not log of split-brain when there isn't one
    
    * Even on errors like ENOENT, AFR logs split-brain after
      read-txn refresh, introduced by commit a07ddd8f.
      This can be a cause of much panic and confusion and needs to be fixed.
    
    * Also fixed this issue in write-txns.
    
    * Fixed afr read txns to log about split-brain only after knowing that
      there is no split-brain choice configured.
    
    * Removed code duplication
    
    * Fixed incorrect passing of error code in afr_write_txn_refresh_done()
      (the function was passing -0 as errno to gf_msg().
    
    Change-Id: I354f454ce5bf0e5f00bc27916eb597367cb7d927
    BUG: 1411625
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16362
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit bb438d849a4a3941c1a9b525213f695f0a2c961b
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Oct 27 07:30:48 2016 +0200

    feature/dht: undo partially successful dir rename
    
    As with dht, dirs are present on all subvolumes,
    renaming them is a compound operation and thus a
    partial success + partial failure scenario is
    possible, resulting in an inconsistent state.
    
    For purposes of reproduction, such a scenario can
    easily be produced by stopping the volume, edit the
    volfile of a certain subvolume to get at an
    "option read-only on" setting, and then restart
    the volume. Thus those operations that are to make change
    on the affected subvolume will fail with EROFS.
    
    To handle such scenarios, we introduce an in-memory cache
    where we record the return values obtained from the
    subvolumes. At the final stage of the dir rename operation
    we check if it's a partial success/fail situation. If yes,
    then we perform a reverse rename op on those subvolumes
    where the operation succeeded.
    
    Change-Id: I3d05f74f53932cb984a918d252a7309c1009a51d
    BUG: 1412069
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/15739
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit d6bc8da62f1b0d454fa5187687fdbf894403c7ce
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Jan 9 13:10:19 2017 +0100

    libglusterfs: fix statvfs in FreeBSD
    
    FreeBSD interprets statvfs' f_bsize field in a different way than Linux.
    
    This fix modifies the value returned by statvfs() on FreeBSD to match
    the expected value by Gluster.
    
    Change-Id: I930dab6e895671157238146d333e95874ea28a08
    BUG: 1356076
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/16361
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 167f417f73d7877e7b5ea5bf72e66964d463d4b6
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Dec 19 09:14:44 2016 +0530

    dht : file rename operation is successful but log has error File exists
    
    Problem: file rename operation is successful but log has error
             'key:trusted.glusterfs.dht.linkto error:File exists'
    
    Solution: The error comes in log only when file already has set this xattr
              (trusted.glusterfs.dht.linkto) before run rename operation and
              in that case sys_lsetxattr throws this kind of message.
              To avoid the error message in logs update the condition in
              posix_handle_pair.
    
    BUG: 1404905
    Change-Id: Iafd8cb45f9d7f4fe247e297a6ef0af978a8d0b30
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/16185
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c89a065af2adc11d5aca3a4500d2e8c1ea02ed28
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jan 9 09:55:26 2017 +0530

    readdir-ahead : Perform STACK_UNWIND outside of mutex locks
    
    Currently STACK_UNWIND is performnd within ctx->lock.
    If readdir-ahead is loaded as a child of dht, then there
    can be scenarios where the function calling STACK_UNWIND
    becomes re-entrant. Its a good practice to not call
    STACK_WIND/UNWIND within local mutex's
    
    Change-Id: If4e869849d99ce233014a8aad7c4d5eef8dc2e98
    BUG: 1401812
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/16068
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit f99750b4477538cd1f97ce6340e1813202f986e2
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 6 17:16:38 2017 +0100

    rpm: depend on firewalld-filesystem for directory ownership
    
    Also use the %firewalld_reload macro that is provided by the
    firewalld-filesystem package.
    
    BUG: 1410853
    Change-Id: Ibbbc18cc394f8b1e5ba74927effc41c466667479
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/16351
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a988741713752c2ec04a0680224d8fa4d42dc203
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Dec 6 14:43:10 2016 +0530

    dht: At places needed use STACK_WIND_COOKIE
    
    Issue:
    frame has a void * cookie pointer.
    In case of STACK_WIND_COOKIE frame->cookie is assigned
    to what is sent by the caller.
    In case of STACK_WIND frame->cookie is assigned to point
    point to the frame itself.
    
    For ease of coding, at many places, the cookie in the cbk
    is used to get the pointer to the next xl. This is
    inconsistent when STACK_WIND_TAIL comes into picture.
    
    Eg: dht_setxattr () {
        for (i = 0 ; i < conf->subvolume_cnt ; i++) {
           STACK_WIND (..dht_checking_pathinfo_cbk,
                       conf->subvolumes[i] ..);
        }
    
        dht_checking_pathinfo_cbk (...void *cookie...) {
            prev = cookie;
            ...
            for (i = 0; i < conf->subvolume_cnt; i++) {
                if (conf->subvolumes[i] == prev->this) {
                     ...
                }
            }
        }
    
        Consider the below graph:
        dht (parent)
        readdir-ahead  => Doesn't define setxattr and uses STACK_WIND_TAIL
        protocol-client
    
        With this graph, when dht_checking_pathinfo_cbk is called,
        cookie will have frame pointing to protocol-client.
        i.e. prev->this will be protocol-client. But dht was expecting
        it to be readdir-ahead as it has stored in conf->subvolumes[i]
    
    Solution:
        Hence, as a thumb rule, if cbk is using cookie, then we explicitly
        call STACK_WIND_COOKIE.
    
    Change-Id: I83aea1e24c809c5a91a0db7283e908e125471bd4
    BUG: 1401812
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/16039
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit cc55be619830bc64544a1044f05367b8be9421bc
Author: Sunil Kumar H G <sheggodu@redhat.com>
Date:   Fri Dec 30 14:11:15 2016 +0530

    cluster/ec: Fixing log message
    
    Updating the warning message with details to improve
    user understanding.
    
    BUG: 1409202
    Change-Id: I001f8d5c01c97fff1e4e1a3a84b62e17c025c520
    Signed-off-by: Sunil Kumar H G <sheggodu@redhat.com>
    Reviewed-on: http://review.gluster.org/16315
    Tested-by: Sunil Kumar Acharya
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 76fbeafbf56a61768c81f622b354e3c95a00e986
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Mon Dec 19 15:07:14 2016 +0530

    glusterd: Get maximum supported op-version in a cluster
    
    gluster volume get <VOLNAME> cluster.opversion gives us the current
    op-version on which the cluster is operating. There is no command
    that lets the user know the maximum supported op-version that the
    cluster can run on.
    
    This patch adds a new global option cluster.max-op-version, that
    can be used to retrieve the maximum supported op-version in a
    cluster.
    
    Usage:
    	# gluster volume get all cluster.max-op-version
    
    Example output:
    
    Option                                  Value
    ------                                  -----
    cluster.max-op-version                  30900
    
    NOTE: The only way to test this feature for now is to set the
    GD_OP_VERSION_MAX macro to different values (30800 for 3.8,30900
    for 3.9, and so on) and rebuild glusterd. Since the regression test
    framework currently doesn't have support to simulate these tests,
    there are no accompanying regression tests for this feature. It
    should be possible to add tests once glusto comes in and makes it
    easier to run a heterogeneous cluster.
    
    Change-Id: I547480ee5e7912664784643e436feb198b6d16d0
    BUG: 1365822
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/16283
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 3fcd790d9ca01a95026026d64385c52b5476174d
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Dec 26 16:26:49 2016 +0530

    md-cache: Cache updated as a part of invalidate should not update time
    
    Currently when a invalidate happens we update the cache along with
    the cache time. The problem with this is, upcall doesn't update the
    last access time of a client when an invalidation is sent, thus resulting
    in a timewindow where the md-cache has cached, but the upcall is unaware
    and hence upcall will not further invalidate the cache(unless a fop is sent
    from the same client, and upcall updates its database to reflect the same)
    
    Change-Id: Ibceb8d2fc360582752846bbf7fd59697d5424754
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/16295
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 521c55c53bd42bfdcc0919019ee81c81305382a2
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Dec 26 15:16:10 2016 +0530

    performance/write-behind: Add debug messages
    
    Change-Id: I2ea1350fcbe4b6c06dcb8093b28316f734cd3b48
    BUG: 1379655
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/16285
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 83117c71482c9f87a0b6812094cbb22497eb3faa
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jan 6 21:06:23 2017 +0530

    cluster/dht: Incorrect migration checks in fsync
    
    Fixed the order of the migration phase checks
    in dht_fsync_cbk. Phase1 should never be hit if op_ret
    is non zero.
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    
    Change-Id: I9222692e04868bffa93498059440f0aa553c83ec
    BUG: 1410777
    Reviewed-on: http://review.gluster.org/16350
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ee6ae7a6d0649c405e8bf096d4781f74494d5263
Author: Muthu-vigneshwaran <mvignesh@redhat.com>
Date:   Mon Dec 5 21:02:05 2016 +0530

    glusterfs : Removing logically dead code
    
    CID = 1356502
    
    BUG: 789278
    Change-Id: I11a814addc6607902c12aca8f4efec5741cbd7d3
    Signed-off-by: Muthu-vigneshwaran <mvignesh@redhat.com>
    Reviewed-on: http://review.gluster.org/16028
    Tested-by: Muthu Vigneshwaran <muthuvigneshwaran77@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 1278f1957cbb44263c510f351875c968319ea3db
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Jan 4 16:29:49 2017 +0530

    features/uss: Remove redundant dict_unref
    
    In case dict_set_dynstr_with_alloc fails, dict_unref is done
    when exection jumps to label 'out'.
    
    Change-Id: I083386b7f85207348ba0bc353b5d1036ab821a15
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/16321
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9061ccf0a906925f54f853f92ad609d8269232a2
Author: Nigel Babu <nigelb@redhat.com>
Date:   Tue Dec 27 10:56:57 2016 +0530

    tests: Remove rpm test
    
    This is already tested by our smoke test. Testing it again is redundant.
    
    Change-Id: Icae4e8650002cd847dcb7ea76fd0447df7e72816
    BUG: 1408755
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: http://review.gluster.org/16287
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9bed81ada6f91f998e9abd915b18e3f06557cdcb
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Dec 6 07:46:52 2016 +0100

    posix: make sure atime and mtime are set when calling lutimes()
    
    When overwriting an existing file with O_TRUNC, the 'atime' was set to
    0, meaning the Epoch (01-Jan-1970 UTC). However, the 'mtime' gets
    updated correcty.
    
    In case 'atime' or 'mtime' is not passed in the 'struct iatt', the time
    values passed to the systemcall are taken from the current values are
    returned by lstat().
    
    Change-Id: I7021b7161dcd6c9a3e515d98f6d4847533c434b3
    BUG: 1401777
    Reported-by: Eivind Sarto <eivindsarto@gmail.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/16034
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 451ca272d12f2d49522c845d53585520f71525f8
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Jan 5 11:46:20 2017 +0530

    dht/rebalance: remove errno check for failure detection
    
    BUG: 1410355
    Change-Id: I867419ca36a81ef7209e6911a46c1c2c898b8eab
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/16328
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c916a2ffc257b0cfa493410e31b6af28f428c53a
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Jan 5 14:06:21 2017 +0530

    glusterd: Fail add-brick on replica count change, if brick is down
    
    Problem:
    1. Have a replica 2 volume with bricks b1 and b2
    2. Before setting the layout, b1 goes down
    3. Set the layout write some data, which gets populated on b2
    4. b2 goes down then b1 comes up
    5. Add another brick b3, and heal will take place from b1 to b3, which
       basically have no data
    6. Write some data. Both b1 and b3 will mark b2 for pending writes
    7. b1 goes down, and b2 comes up
    8. b2 gets heald from b1. During heal it removes the data which is already
       in b2, considering that as stale data. This leads to data loss.
    
    Solution:
    1. In glusterd stage-op, while adding bricks, check whether the replica
       count is being increased
    2. If yes, then check whether any of the bricks are down at that time
    3. If yes, then fail the add-brick to avoid such data loss
    4. Else continue the normal operation.
    
    This check will work enen when we convert plain distribute volume to replicate
    
    Test:
    1. Create a replica 2 volume
    2. Kill one brick from the volume
    3. Try adding a brick to the volume
    4. It should fail with all bricks are not up error
    5. Cretae a distribute volume and kill one of the brick
    6. Try to convert it to replicate volume, by adding bricks.
    7. This should also fail.
    
    Change-Id: I9c8d2ab104263e4206814c94c19212ab914ed07c
    BUG: 1406411
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: http://review.gluster.org/16330
    Tested-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 395c55483724912821929ff2a793e99fd7bf4e71
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 4 13:37:23 2017 +0530

    cluster/ec: Do lookup on an existing file in link
    
    Problem:
    In link fop lookup is happening on the new fop which doesn't exist so the iatt
    ec serves parent xlators has size as zero which leads to 'cat' giving empty output
    
    Fix:
    Change code so that lookup happens on the existing link instead.
    
    BUG: 1409730
    Change-Id: I70eb02fe0633e61d1d110575589cc2dbe5235d76
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/16320
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 95d07a3d2d68805d93d36a447436e27c48777939
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jan 5 15:36:02 2017 +0530

    ec: Invalidations in disperse volume should not update the stat
    
    Issue:
    In disperse volume, the file is present across bricks, hence the stat
    from one brick doesn't carry the valid size of the file. Therefore
    the upcall from one brick updating the md-cache results in wrong size
    being updated.
    
    Fix:
    If the notification is cache invalidation then, indicate md-cache that
    the attributes is invalid.
    
    BUG: 1410375
    Change-Id: Id89d2283478e70b62b435a8891fffc86d2be8cb2
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/16329
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c6b0adb483c1d0c4922e6d4cb77abfb69d314a8e
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Dec 5 13:01:41 2016 -0500

    libglusterfs: serialize init/reconfigure calls
    
    These functions do not generally "expect" to be called more than once
    in parallel, and many are likely to misbehave in that case (one case
    in DHT already).  Such parallel calls have not generally happened
    because there are only a few places where we call these functions, and
    those have been implicitly serialized until recently.  However, recent
    changes in the epoll layer change that, as does brick multiplexing.
    Therefore, the serialization is now explicit at the init/reconfigure
    level.
    
    It would be sufficient to serialize calls to a particular translator's
    init and reconfigure functions, but that would require per-translator
    locks and a bit more complexity in maintaining/using them.  Since
    there's no clear reason why we would need or want to support a higher
    level of parallelism, the simpler approach of a global lock should
    suffice.
    
    Change-Id: I26296c2826e91dc00b7f0c2061bcc2964ef90c4c
    BUG: 1399134
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/16030
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit f60631904defdaec2f1bae84b3cfd6a3e083cf09
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Dec 6 16:31:51 2016 +0530

    readdir-ahead: Enhance EOD detection logic
    
    Issue:
    Currently end of directory is identified on obtaining a
    readdirp_cbk with op_ret = 0 (i.e. 0 entries fetched in
    readdirp). Thus an extra readdirp is required for every
    directory just to identify EOD. Consider a case of listing
    large number of small directories. The readdirp fops required
    are doubled in that case.
    
    Solution:
    On reaching the EOD, posix sets the op_errno to ENOENT,
    hence along with looking for 'op_ret == 0' we also
    look for 'operrno == ENOENT' ehile checking for EOD condition
    
    Change-Id: I7a5b52e7b98f5dc236c387635fcc651dac0171b3
    BUG: 1401812
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/16042
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit aa053b228e01ab079f86d24f3444b2389895effd
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jan 5 11:28:44 2017 +0530

    eventsapi: Use `getaddrinfo` instead of `gethostbyname`
    
    `gethostbyname` is not thread safe. Use `getaddrinfo` to avoid
    any race or segfault while sending events
    
    BUG: 1410313
    Change-Id: I164af1f8eb72501fb0ed47445e68d896f7c3e908
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/16327
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c455c6030f1f1678ae66752e5e11ea988d062df4
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Dec 22 14:28:27 2016 +0530

    tests: Remove tests/distaf
    
    We will not be using it in the future
    
    BUG: 1408131
    Change-Id: Idebaaadb06786eebc08969ce0cc15a9df4bd9f42
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: http://review.gluster.org/16270
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0b9af18eade6583299b88b4e685b02114db7834a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 3 12:50:54 2017 +0530

    cluster/dht: Do rename cleanup as root
    
    Problem:
    Rename linkfile cleanup is done as non-root which may not have priviliges to do
    the rename so it fails with EACCESS. MKDIR on that name in future will start to
    hole on this subvolume. It is not easy to hit on fuse mounts because vfs takes
    care of the permission checks even before rename fop is wound. But with
    nfs-ganesha mounts it happens.
    
    Fix:
    Do rename cleanup as root
    
    BUG: 1409727
    Change-Id: I414c1eb6dce76b4516a6c940557b249e6c3f22f4
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/16317
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 2f4898de4c3dda7072c02cf2f799d71d349016af
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Dec 28 14:32:12 2016 +0530

    mount/fuse: Fix the place where graph-switch event is logged
    
    Change-Id: I3c8577b87db02a2a6ce6159e7d04cf58a2bda0c1
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16302
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6e4cb07d0df06a8c168394880a18a0ba4034c06b
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Thu Dec 15 09:06:00 2016 -0800

    core: Disable the memory pooler in Gluster via a build flag
    
    Summary:
    Passing --disable-mempool to configure will disable the mempool.
    
    Change-Id: I60d5f70d54de507fe9f4695d7589f7ae1ba4bb0f
    BUG: 1405165
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-on: http://review.gluster.org/16148
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 369fa575a1089b472c39a3843c56f694e1f7ad6f
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Nov 30 17:44:29 2016 -0500

    storage/posix: log the error when locking the export directory fails
    
    posix xlator tries to prevent external unmount of the brick export directory
    by locking it. It locks the export directory by opening it (i.e. doing a opendir).
    
    But if opendir fails it errors out resulting in the brick process going down. The
    error due to which opendir failed is not logged.
    
    Change-Id: I28648382b7f0b88fb1aeb36152e5ab5d812374c9
    BUG: 1401095
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/16018
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 76fff8cb2a164b596ca67e65c99623f5b68361fd
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Dec 29 12:10:00 2016 +0000

    tests: Fix split-brain-favorite-child-policy.t failures
    
    Problem:
    In CentOS-7, the file was receving an extra removexattr(security.ima)
    FOP which changed its ctime, breaking the assumption that a particular brick
    had the latest ctime based on the writevs done in the .t
    
    Fix:
    1. Compare the ctime of both files in the backend and pick the one with
    the latest ctime for the fav-child policy. Also unmount the volume
    before comparing, to avoid any further FOPS on the file that
    can possibly modify the timestamps.
    
    2. Added floating point handling in stat function. Thanks to Pranith for
    the helping debugging the regex.
    
    Change-Id: I06041a0f39a29d2593b867af8685d65c7cd99150
    BUG: 1408757
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/16288
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 11b6a2c9fc5232b58774cab29873406c0fbfef19
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Dec 30 10:33:13 2016 +0530

    cluster/dht: Fix dict_leak in migration check tasks
    
    Fixed a memleak where dict was not being unrefed
    in the dht_migration_complete_check_task and
    dht_rebalance_inprogress_task functions.
    
    Change-Id: I3d42e9a2e5c8596c985bf6431a68fd3905227383
    BUG: 1409186
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/16308
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 6b88186c804b05ac05f0613b9ec290e2373d3bbb
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Dec 27 11:17:29 2016 +0530

    tests: fix tests/bugs/glusterd/bug-913555.t spurious failures
    
    Mainly replaced EXPECT instances with EXPECT_WITHIN
    
    Change-Id: If48f444f6b2ba6713fdc5e31ff3a642092e62ada
    BUG: 1408758
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/16289
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 08056421b886b1ebf1e0eed93d9f6f9b6d017489
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Fri Sep 23 16:35:15 2016 +0530

    glusterd, cli: Get global options through volume get functionality
    
    Currently it is not possible to retrieve values of global options
    by using the 'gluster volume get' functionality if there are no
    volumes present. In order to get the global options one has to use
    'gluster volume get' with a specific volume name. This usage makes
    the illusion as though the option is set only on one volume, which
    is incorrect. When setting the global options, 'gluster volume set'
    provides a way to set them using the volume name as 'all'.
    
    Similarly, retrieving the global options should be made possible by
    using the volume name 'all' with the 'gluster volume get'
    functionality. This patch adds that functionality to 'volume get'
    
    Usage:
    	# gluster volume get all <OPTION/all>
    
    Change-Id: Ic2fdb9eda69d4806d432dae26d117d9660fe6d4e
    BUG: 1378842
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/15563
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 14ae0c6b14c9a32f15cdb3c94edbf08bb2e708b6
Author: Kevin Vigor <kvigor@fb.com>
Date:   Sat Dec 17 08:31:24 2016 -0800

    Repair EC tests for FB environment (/mnt/gvfs is teh sux00r)
    
    Summary:
    
    Don't blindly 'df', target the volume in question.
    
    (this is because FB build environment has a /mnt/gvfs which
    fails df).
    
    Test Plan:
    
    runtests.sh
    
    Reviewers:
    
    Subscribers:
    
    Tasks:
    
    Blame Revision:
    
    Change-Id: Ic2c5883dd102835db64be9594657257e20711ba0
    BUG: 1406878
    Signed-off-by: Kevin Vigor <kvigor@fb.com>
    Reviewed-on-3.8-fb: http://review.gluster.org/16182
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-by: Shreyas Siravara <sshreyas@fb.com>
    Reviewed-on: http://review.gluster.org/16226
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ad785fd8ed7460ed5a2ba571a3d509317a627aba
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Dec 27 16:15:30 2016 +0530

    performance/readdir-ahead: mark two options as NO_DOC
    
    The two options are rda-high-wmark and rda-low-wmark. The impact of
    these two options is yet to be fully understood and hence not
    advertising these options to not run into surprises.
    
    Change-Id: Ia537f4cc342011f0f2f3849ad6b938e247e5622d
    BUG: 1356960
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/16297
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit da5ece887c218a7c572a1c25925a178dbd08d464
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Dec 26 21:08:03 2016 +0530

    cluster/afr: Fix missing name indices due to EEXIST error
    
    PROBLEM:
    Consider a volume with  granular-entry-heal and sharding enabled. When
    a replica is down and a shard is created as part of a write, the name
    index is correctly created under indices/entry-changes/<dot-shard-gfid>.
    Now when a read on the same region triggers another MKNOD, the fop
    fails on the online bricks with EEXIST. By virtue of this being a
    symmetric error, the failed_subvols[] array is reset to all zeroes.
    Because of this, before post-op, the GF_XATTROP_ENTRY_OUT_KEY will be
    set, causing the name index, which was created in the previous MKNOD
    operation, to be wrongly deleted in THIS MKNOD operation.
    
    FIX:
    The ideal fix would have been for a transaction to delete the name
    index ONLY if it knows it is the one that created the index in the first
    place. This would involve gathering information as to whether THIS xattrop
    created the index from individual bricks, aggregating their responses and
    based on the various posisble combinations of responses, decide whether to
    delete the index or not. This is rather complex. Simpler fix would be
    for post-op to examine local->op_ret in the event of no failed_subvols
    to figure out whether to delete the name index or not. This can occasionally
    lead to creation of stale name indices but they won't be affecting the IO path
    or mess with pending changelogs in any way and self-heal in its crawl of
    "entry-changes" directory would take care to delete such indices.
    
    Change-Id: Ic1b5257f4dc9c20cb740a866b9598cf785a1affa
    BUG: 1408712
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16286
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5a7c86e578f5bbd793126a035c30e6b052177a9f
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Dec 23 07:11:13 2016 +0000

    afr: use accused matrix instead of readable matrix for deciding heals
    
    Problem:
    afr_replies_interpret() used the 'readable' matrix to trigger client
    side heals after inode refresh. But for arbiter, readable is always
    zero. So when `dd` is run with a data brick down, spurious data heals
    are are triggered. These heals open an fd, causing eager lock to be
    disabled (open fd count >1) in afr transactions, leading to extra FXATTROPS
    
    Fix:
    Use the accused matrix (derived from interpreting the afr pending
    xattrs) to decide whether we can start heal or not.
    
    Change-Id: Ibbd56c9aed6026de6ec42422e60293702aaf55f9
    BUG: 1408395
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/16277
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 734da9d94566dbf37984b88df787569fd5209ee2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 14 07:03:28 2016 -0500

    glusterd/geo-rep: Fix geo-rep config issue
    
    Problem:
    Geo-replication config commands fail when geo-rep
    status is in 'Created'.
    
    Cause:
    During staging phase of geo-rep config, it checks
    for the existence of 'monitor.pid' file. But the
    pid file gets created only on start of geo-rep.
    Hence it fails.
    
    Fix:
    Do not check for the existence of pid-file during
    staging for config commands. It is not required.
    
    Change-Id: I626d368b249cf0423c7f49b4284465508371f566
    BUG: 1404678
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/16132
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit c20febcb1ffaef3fa29563987e7a3b554aea27b3
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Dec 13 14:26:53 2016 +0530

    dht/rebalance: reverify lookup failures
    
    race: readdirp has read one entry, and doing a lookup on
    that entry, but user might have renamed/removed that entry just
    after readdirp but before lookup.
    
    Since remove-brick is a costly opertaion,will ingore any
    ENOENT/ESTALE failures and move on.
    
    Change-Id: I62c7fa93c0b9b7e764065ad1574b97acf51b5996
    BUG: 1408115
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/15846
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit bc74dc62bb97881c9787f1f6ab67e36dfccaea97
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Dec 20 10:48:45 2016 -0500

    common-ha: add node create new node dirs in shared storage
    
    When adding a node to the ganesha HA cluster, create the directory
    tree in shared storage for the added node and create sets of symlinks
    to match what is/was created for the other nodes.  I.e. in a four
    node cluster the new node needs a set of links to the four existing
    nodes:
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e1 -> e1
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e2 -> e2
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e3 -> e3
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e4 -> e4
    and all the existing nodes need links added for the new node:
     /run/gluster/shared/nfs-ganesha/$e1/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e2/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e3/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e5/nfs/{ganesha,statd}/$new -> new
    
    Likewise when deleting, remove the dir and symlinks.
    
    original change http://review.gluster.org/16036
    
    BUG: 1400613
    Change-Id: I52839046745728d06ab5a07f38081c032093bff6
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/16216
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 96fb35624060565e02e946a970b3e777071bde9c
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Nov 24 14:58:20 2016 +0530

    performance/readdir-ahead: limit cache size
    
    This patch introduces a new option called "rda-cache-limit", which is
    the maximum value the entire readdir-ahead cache can grow into. Since,
    readdir-ahead holds a reference to inode through dentries, this patch
    also accounts memory stored by various xlators in inode contexts.
    
    Change-Id: I84cc0ca812f35e0f9041f8cc71effae53a9e7f99
    BUG: 1356960
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/16137
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 7ee998b9041d594d93a4e2ef369892c185e80def
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Dec 20 07:05:02 2016 +0530

    afr: Ignore event_generation checks post inode refresh for write txns
    
    Before http://review.gluster.org/#/c/15673/, after inode refresh, we
    failed read txns in case of EIO or event_generation being zero. For
    write transactions, the check was only for EIO. 15673 re-factored the
    code to fail both read and write when event_generation=0. This seems to
    have caused a regression as explained in the BZ.
    
    This patch restores that behaviour in afr_txn_refresh_done().
    
    Change-Id: Ib8e116506badce6f58b55827dbe403d95069d744
    BUG: 1406224
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/16205
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit de576c08ef17706d25efecff7b57cc8c0294cf6f
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Dec 20 18:22:02 2016 +0530

    common-ha: Correct the VIP assigned to the new node added
    
    There is a regression introduced with patch#16115. An incorrect
    VIP gets assigned to the new node being added to the cluster.
    This patch fixes the same.
    
    Change-Id: I468c7d16bf7e4efa04692db83b1c5ee58fbb7d5f
    BUG: 1406410
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/16213
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 253c43596b9dcf57832a0369b6c4dc01598bd442
Author: Sanoj Unnikrishnan <sunnikri@redhat.com>
Date:   Sun Dec 18 17:29:47 2016 +0530

    Fixes GlusterFS process crashes on deep directory hierarchy
    
    alloca() calls to recusive function posix_make_ancestryfromgfid
    consumes the entire stack leading to segfault.
    Changed the function to  iterative and reused the same linkname
    buffer across iterations.
    
    Change-Id: If065c8b9f7f85219bdd2d23259a115fe66f5f60d
    BUG: 1405775
    Signed-off-by: Sanoj Unnikrishnan <sunnikri@redhat.com>
    Reviewed-on: http://review.gluster.org/16192
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 97bfea234b1c097e7217181e7e6285fbd553d003
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Dec 20 16:09:10 2016 +0530

    storage/posix: Do not create a directory which already exist
    
    Problem: While brick process starts, it tries to create trashcan
    and internal_op directory with fixed gfids. For the first time
    these directories will not be present. However, stop and start
    of volume again tries to create these directories, which are
    already present.
    This throws a gfid exist warning and EEXIST error in logs.
    
    Solution: Check if the directory exist on brick and gfid of
    this dir and the requested gfid matches or not.
    
    Change-Id: Ie4966a550ed44046e0f2d10e9dbd540182ea97d2
    BUG: 1406348
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/16212
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit af6769675acbbfd780fa2ece8587502d6d579372
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Dec 13 15:28:42 2016 +0530

    socket: socket disconnect should wait for poller thread exit
    
    When SSL is enabled or if "transport.socket.own-thread" option is set
    then socket_poller is run as different thread. Currently during
    disconnect or PARENT_DOWN scenario we don't wait for this thread
    to terminate. PARENT_DOWN will disconnect the socket layer and
    cleanup resources used by socket_poller.
    
    Therefore before disconnect we should wait for poller thread to exit.
    
    Change-Id: I71f984b47d260ffd979102f180a99a0bed29f0d6
    BUG: 1404181
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/16141
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 8b42e1b5688f8600086ecc0e33ac4abf5e7c2772
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Dec 20 10:42:31 2016 +0530

    ganesha/scripts : Prevent removal of entries in ganesha.conf during deletion of a node
    
    Change-Id: Ia6c653eeb9bef7ff4107757f845218c2316db2e4
    BUG: 1406249
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/16209
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 8094e5005fbe9016ae039003bcc617d1172385b3
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Dec 19 12:22:29 2016 +0530

    tests: Fix spurious failure in tests/bugs/replicate/bug-1402730.t
    
    Replace the EXPECT '00000001' with EXPECT_NOT '00000000'. This is
    because occasionally a name-heal is performing new-entry marking on
    'c' causing the pending entry changelog on it to become '00000002'.
    
    Change-Id: I30916e6266534d18899cfa5771c892db8c51ad9a
    BUG: 1405902
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16193
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9509b4619b8a373538b6857a06f1032c46a432fe
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Dec 20 11:51:07 2016 +0530

    client,server: Free xdr-allocated compound req/rsp arrays
    
    Change-Id: I9e1829f4f73f001bba33005032e030f289e8d003
    BUG: 1406252
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16210
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2bb2313656a19ee8efe3cfeda4f2ae90e8e49b62
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 16 21:41:58 2016 +0530

    tests: Fix spurious failure in bug-1402841.t-mt-dir-scan-race.t
    
    Check that shd is up before executing 'volume heal' command
    
    Change-Id: Ib510a5de06d732fd3a738e90fa16376698479897
    BUG: 1405554
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16169
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 5542b404f4a6b5968d52175ea10d694aabf906f1
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 16 12:37:41 2016 +0530

    tests: Move tests/basic/gfapi/bug1291259.t to bad tests list
    
    See thread
    http://www.gluster.org/pipermail/gluster-devel/2016-December/051714.html
    for more information.
    
    Change-Id: I9abe4b0e40499e53c1276a10a6bc192fd0f2cef7
    BUG: 1405301
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16159
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit d0528cf2408533b45383a796d419c49fa96e810b
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Dec 13 11:55:19 2016 +0530

    snapshot: Fix restore rollback to reassign snap volume ids to bricks
    
    Added further checks to ensure we do not go beyond prevalidate
    when trying to restore a snapshot which has a nfs-gansha conf
    file, in a cluster when nfs-ganesha is not enabled
    
    The error message for the particular scenario is:
    "Snapshot(<snapname>) has a nfs-ganesha export conf
    file. cluster.enable-shared-storage and nfs-ganesha
    should be enabled before restoring this snapshot."
    
    Change-Id: I1b87e9907e0a5e162f26ef1ca89fe76e8da8610f
    BUG: 1404118
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/16116
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 136e6c81201daeb49e5ca9b893ae23b3ba5c0bdc
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Tue Mar 15 19:18:35 2016 -0700

    socket: Keepalives should happen on IPv6 as well as IPv4
    
    Summary:
    - Check for AF_INET *and* AF_INET6.
    - This is a cherry-pick of D3057373 to 3.8
    
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Change-Id: I53eb79284eddfee6e13821c6570809f575b96769
    BUG: 1405478
    Reviewed-on: http://review.gluster.org/16167
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e9d8525a0d34130ba2a582109937b8e79eecf6ab
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Thu Dec 15 20:51:30 2016 +0530

    tests: Fix spurious test failure in bug-1316437.t
    
    After sending SIGTERM to gluster process we immediately
    check if process exited. We should wait for some time
    before checking process state.
    
    BUG: 1404573
    Change-Id: Iaba0067f6e880a7fe38e11b9fa0fe9bd103b19e2
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/16162
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit dc549b330cc1337c60f3c3544986bab13d10d4e5
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Dec 6 02:00:11 2016 -0500

    common-ha: add node create new node dirs in shared storage
    
    When adding a node to the ganesha HA cluster, create the directory
    tree in shared storage for the added node and create sets of symlinks
    to match what is/was created for the other nodes.  I.e. in a four
    node cluster the new node needs a set of links to the four existing
    nodes:
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e1 -> e1
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e2 -> e2
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e3 -> e3
     /run/gluster/shared/nfs-ganesha/$new/nfs/{ganesha,statd}/$e4 -> e4
    and all the existing nodes need links added for the new node:
     /run/gluster/shared/nfs-ganesha/$e1/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e2/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e3/nfs/{ganesha,statd}/$new -> new
     /run/gluster/shared/nfs-ganesha/$e5/nfs/{ganesha,statd}/$new -> new
    
    Likewise when deleting, remove the dir and symlinks.
    
    Change-Id: Id2f78f70946f29c3503e1e6db141b66cb431e0ea
    BUG: 1400613
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/16036
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 2d87431c51328e419ae08932589fe81d29ef742b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 16 09:31:41 2016 +0530

    protocol/client: Fix potential mem-leaks
    
    Commit 93eaeb9c93be3232f24e840044d560f9f0e66f71 introduces
    leaks in INODELK callback where a dict is unserialized twice,
    leading to dict leaks.
    
    Change-Id: I219ccb2279f237ebc2e4fc366af4775a461929b8
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16156
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit d2dff6320adc5c58ed8ed68dc1d3209149c29584
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Dec 16 09:53:19 2016 +0530

    Revert "doc: fix gluster man page"
    
    This reverts commit c6fdc2f819b265e018d858232293407835fe2c6c.
    
    Initially I thought gluster --xml taking into the shell prompt is not a
    correct behavior, however if we execute any commands from that prompt we
    get xml output which is the original intention. This patch reverts the
    change and put back --xml option for gluster in man page.
    
    Change-Id: If77d0c0bf27f8cfc799973003c860d9bd8cd6407
    BUG: 1360670
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/16157
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit c6fdc2f819b265e018d858232293407835fe2c6c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Dec 15 21:27:21 2016 +0530

    doc: fix gluster man page
    
    gluster --xml will take into the interactive prompt which is not an
    intended message here.
    
    Change-Id: Iea5b094a1b1b429d211008a3c7459b703c1a0a12
    BUG: 1360670
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/16142
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 209c2d447be874047cb98d86492b03fa807d1832
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Dec 14 22:48:20 2016 +0530

    glfsheal: Explicitly enable self-heal xlator options
    
    Enable data, metadata and entry self-heal as xlator-options so that glfs-heal.c
    can heal split-brain files even if they are disabled on the volume via volume
    set commands.
    
    Change-Id: Ic191a1017131db1ded94d97c932079d7bfd79457
    BUG: 1234054
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11333
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6f4f3d012ccac3088a58c21844b63fdb54a96cd8
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Dec 13 13:40:52 2016 -0500

    common-ha: explicitly set udpu transport for corosync
    
    On RHEL7 corosync uses udpu (udp unicast) by default. On RHEL6 the
    default is (now) udp multi-cast. In network environments that don't
    support udp multi-cast this causes the ever growing lists of
    [TOTEM ] Retruansmit errors.
    
    Always specifying --transport udpu is thus a no-op on RHEL7.
    
    Using the same transport on both RHEL6 and RHEL7 may (or may not
    give similar behavior and performance--it's hard to say.
    
    It remains a mystery why things have always worked on RHEL6 prior to
    now. Further investigation is required to uncover why this is the
    case.
    
    Change-Id: I4d0de97fe4425c47f249beaaf51aeca3e91731fa
    BUG: 1404410
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/16122
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 75ad1dd5ef98053be1fd1e8aa4a1fef1ac32ef3a
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Nov 30 12:54:05 2016 -0500

    cli: Suppress unused but set warnings
    
    GCC has the following complaint during compilation:
    
    ../../../cli/src/cli-rpc-ops.c: In function ‘gf_cli_get_volume_cbk’:
    ../../../cli/src/cli-rpc-ops.c:846:36: warning: variable ‘caps’ set but not used
    [-Wunused-but-set-variable]
             char                      *caps                 = NULL;
    
    Change-Id: Ia378a6c83ba70ae35290802b7b38ad2830c0956c
    BUG: 1402261
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/15982
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit e81fd0b85c8dd3f521e54e32b7da2f99a513f2f2
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Nov 17 18:22:39 2016 +0530

    access_control : address O_TRUNC and O_APPEND flag properly in posix_acl_open
    
    In posix_acl_open, in switch value passed is (flag & O_ACCMODE). The value for
    O_ACCMODE is 0003, so the result will always be less than or equal to 3.
    But value for O_TRUNC is 01000 and O_APPEND is 02000, so it is not right to
    check it in switch case
    
    Change-Id: Ia17db80a6a5f681c35e08e062d384f33ef7e0354
    BUG: 1387241
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15688
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ff2a58d784bc20ccafab8183d82787ceb8ac471b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Dec 12 13:06:15 2016 +0530

    geo-rep: Fix log-rsync-performance config issue
    
    If log-rsync-performance config is not set, gconf.get_realtime
    will return None, Added default value as False if config file
    doesn't have this option set.
    
    BUG: 1393678
    Change-Id: I89016ab480a16179db59913d635d8553beb7e14f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/16102
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 009454de29d6653e07ac090af1c5d233c7150dd4
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Dec 6 12:11:35 2016 +0530

    geo-rep: Use Host UUID to find local Gluster node
    
    To spawn workers for each local brick, Geo-rep was collecting all
    the machine IPs based on hostname and finds based on the connectivity.
    
    With this patch, Geo-rep finds local brick if host UUID matches with
    UUID of the brick from Volume info.
    
    BUG: 1401801
    Change-Id: Ic83c65df89e43cb86346e3ede227aa84d17ffd79
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/16035
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit a0a4163ce6a8dd8bb83b60a4484578fadd02c88f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Dec 8 14:53:04 2016 +0530

    cluster/ec: Fix lk-owner set race in ec_unlock
    
    Problem:
    Rename does two locks. There is a case where when it tries to unlock it sends
    xattrop of the directory with new version, callback of these two xattrops can
    be picked up by two separate epoll threads. Both of them will try to set the
    lk-owner for unlock in parallel on the same frame so one of these unlocks will
    fail because the lk-owner doesn't match.
    
    Fix:
    Specify the lk-owner which will be set on inodelk frame which will not be over
    written by any other thread/operation.
    
    BUG: 1402710
    Change-Id: I666ffc931440dc5253d72df666efe0ef1d73f99a
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/16074
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 212c7600d2070a4414bc89fd7d2c186b5994cd54
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Dec 13 14:38:18 2016 +0530

    upcall: Fix 'use after free' in a log message
    
    There is chance of accessing freed pointer in a log message at TRACE
    level while cleaning up expired client entries.
    
    Change-Id: I06b4dad755df63978ab04ca52442bfd4600d139a
    BUG: 1404168
    Reported-by: Ravishankar N <ravishankar@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/16117
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 9b1c9395a397e337e4a0acac55b935cb1ce094b7
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Dec 12 16:41:23 2016 +0530

    glusterd: Handle volinfo->refcnt properly during volume start command
    
    While running the volume start command, the refcnt of the volume is
    incremented. At the end of the command, the refcnt should also be
    decremented. This is currently not the case.
    
    This patch, makes sure the refcnt is also decremented at the end of the
    volume start command.
    
    Change-Id: I017b5039be5948df41dde6bc89d2955d5d18971f
    BUG: 1403780
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/16108
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 885ecce6e2df6464b388f42c91211ed31e17654d
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Dec 9 12:18:28 2016 +0530

    common-ha: Create portblock RA as part of add/delete-node
    
    When a node is added to or deleted from existing nfs-ganesha cluster,
    we need to create or cleanup portblock RA as well. This patch is
    to address the same. Also we need to adjust the quorum-policy with
    increase/decrease in the number of nodes in the cluster.
    
    Change-Id: I31a896715b9b7fc931009723d1570bf7aa4da9b6
    BUG: 1403130
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/16089
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2b76520ca3e41cbac8f9318dce87e0b8d670c0ee
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Dec 8 22:49:48 2016 +0530

    cluster/afr: Fix per-txn optimistic changelog initialisation
    
    Incorrect initialisation of local->optimistic_change_log was leading
    to skipped pre-op and post-op even when a brick didn't participate in
    the txn because it was down.
    The result - missing granular name index resulting in some entries
    never getting healed.
    
    FIX:
    Initialise local->optimistic_change_log just before pre-op.
    
    Also fixed granular entry heal to create the granular name index in
    pre-op as opposed to post-op. This is to prevent loss of granular
    information when during an entry txn, the good (src) brick goes
    offline before the post-op is done. This would cause self-heal to
    do conservative merge (since dirty xattr is the only information
    available), which when granular-entry-heal is enabled, expects
    granular indices, the lack of which can lead to loss of data in
    the worst case.
    
    Change-Id: Ia3ad716d6fb1821555f02180e86e8711a79f958d
    BUG: 1402730
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16075
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 9c769c6ee1d125b6bab513073767b628b60abeeb
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Oct 31 10:49:09 2016 +0530

    performance/write-behind: Add more fops for checking dependency with
    cached writes
    
    Fops like readdirp, link, fallocate, discard, zerofill return iatt of
    files in their responses. This iatt can be cached by md-cache. Hence
    it is important that write-behind maintains relative ordering of these
    fops with cached writes. Failure to do so, can result in md-cache
    storing stale iatts and returning the same to applications.
    
    Change-Id: Icfe12ad807e42fe9e52a9f63e47ce63f511c6946
    BUG: 1390050
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/15757
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 74322ce58b1c949e11cb0aa72bfded0e34422157
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Dec 9 15:01:40 2016 +0530

    snapshot/ganesha: Copy export.conf, only if ganesha.enable is on.
    
    Status of the volume being exported via nfs ganesha, should be
    checked by checking if ganesha.enable is set or not, rather than
    deciding based on the errno of the stat
    
    Change-Id: Iaff786d9f77a2de1322ce8ccb4b80954f84d3373
    BUG: 1402828
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/16094
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 6c6c9cd284f7aaf9c07c000abc60d71013862afd
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 26 08:56:51 2016 -0400

    build: python site-packages vs. dist-packages
    
    Unlike Fedora and RHEL/CentOS, where python has
    /usr/{lib,lib64}/python2.7/site-packages/...,  Debian-based
    distributions have /usr/lib/python2.7/dist-packages/...
    
    On Debian our python scriptlet to determine this is broken and
    incorrectly returns .../site-packages, not .../dist-packages.
    Furthermore, the automake/autoconf/pkgconfig bits ahead of our
    own scriptlet have already determined the correct location -- all
    we need to do is use it.
    
    This change also slightly reworks the BUILD_PYTHON_INC scriptlet
    to bring it in line with the style/pattern of the other python
    scriptlets provided by autoconf/pkgconfig.
    
    (I do wonder though, why we have two sets of {C,CPP}FLAGS and
    LD_FLAGS - PYTHONDEV_CPPFLAGS and BUILD_PYTHON_INC, and
    PYTHONDEV_LDFLAGS and BUILD_PYTHON_LIB.
    
    They both have very similar values, but, e.g. BUILD_PYTHON_INC
    misses /usr/lib/x86_64-linux-gnu/python2.7 on Debian; even if that
    ommission doesn't seem to be hurting us.)
    
    Change-Id: I309a5c781a1d9aee4d7be2867223781bd2ae18fa
    BUG: 1388861
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15733
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5da9c89db7626cda7c275712773a7e742f45795a
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Tue Dec 6 14:05:35 2016 +0530

    doc: update to readthedocs.io documentation
    
    Update old links to point to appropriate readthedocs.io
    documentation.
    
    BUG: 1401836
    Change-Id: Ib59848feee7e73512230deb0554471df655b8417
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/16038
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 2f0e9ab1ef271132b8b7b1af25e23ac7bb0720c8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Nov 29 16:51:58 2016 +0100

    refcount: return pointer to the structure instead of a counter
    
    There are no real users of the counter. It was thought of a handy tool
    to track and debug refcounting, but it is not used at all. Some parts of
    the code would benefit from a pointer getting returned instead.
    
    BUG: 1399780
    Change-Id: I97e52c48420fed61be942ea27ff4849b803eed12
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15971
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2d012c4558046afd6adb3992ff88f937c5f835e4
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Dec 9 09:50:43 2016 +0530

    syncop: fix conditional wait bug in parallel dir scan
    
    Problem:
    The issue as seen by the user is detailed in the BZ but what is
    happening is if the no. of items in the wait queue == max-qlen,
    syncop_mt_dir_scan() does a pthread_cond_wait until the launched
    synctask workers dequeue the queue. But if for some reason the worker
    fails, the queue is never emptied due to which further invocations of
    syncop_mt_dir_scan() are blocked forever.
    
    Fix: Made some changes to _dir_scan_job_fn
    
    - If a worker encounters error while processing an entry, notify the
      readdir loop in syncop_mt_dir_scan() of the error but continue to process
      other entries in the queue, decrementing the qlen as and when we dequeue
      elements, and ending only when the queue is empty.
    
    - If the readdir loop in syncop_mt_dir_scan() gets an error form the
      worker, stop the readdir+queueing of further entries.
    
    Change-Id: I39ce073e01a68c7ff18a0e9227389245a6f75b88
    BUG: 1402841
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/16073
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 64451d0f25e7cc7aafc1b6589122648281e4310a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Nov 8 12:09:57 2016 +0530

    cluster/dht: Fix memory corruption while accessing regex stored in
    private
    
    If reconfigure is executed parallely (or concurrently with dht_init),
    there are races that can corrupt memory. One such race is modification
    of regexes stored in conf (conf->rsync_regex_valid and
    conf->extra_regex_valid) through dht_init_regex. With change [1],
    reconfigure codepath can get executed parallely (with itself or with
    dht_init) and this fix is needed.
    
    Also, a reconfigure can race with any thread doing dht_layout_search,
    resulting in dht_layout_search accessing regex freed up by reconfigure
    (like in bz 1399134).
    
    [1] http://review.gluster.org/15046
    
    Change-Id: I039422a65374cf0ccbe0073441f0e8c442ebf830
    BUG: 1399134
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/15945
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 58a58e706da73ee751b7cd98c23e6675667fefdb
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Dec 6 13:38:21 2016 +0530

    ganesha/scripts : find export id for already exported volume in S31ganesha-start.sh
    
    Change-Id: Iada90ed215966d3f526fa20aa5359b67f25a6944
    BUG: 1401822
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/16037
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ff2314995b117b33d81beb6de7b043979c676aeb
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Oct 18 16:58:36 2016 +0530

    eventsapi: Log all published events and provide option to disable logging
    
    Log every published event in /var/log/glusterfs/events.log, Disable logging
    using,
    
      gluster-eventsapi config-set disable-events-log true
    
    Also changed "log_level" config name to "log-level"
    
    Change-Id: Ib354be0c4ca999d1ccd01b810d6cd96ebc72bcd4
    BUG: 1386200
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15674
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 41a71b47f75a52f50ad2754cce679407ebade767
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 7 07:36:19 2016 -0500

    glusterd/geo-rep: Fix glusterd crash
    
    Problem:
    glusterd crashes when geo-rep mountbroker setup is
    created if the slave user length is more than
    8 characters.
    
    Cause:
    _POSIX_LOGIN_NAME_MAX is used which is 9 including
    NULL byte.
    
    Analysis:
    While the man page says it sufficient for portability, but
    acutally it's not. Linux allows the creation of username
    upto 32 characters by default where the max length is 256.
    And NetBSD's max is 17.
    
    Linux:
      #getconf LOGIN_NAME_MAX
       256
    NetBSD:
      #getconf LOGIN_NAME_MAX
       17
    
    Fix:
    Use LOGIN_NAME_MAX instead of _POSIX_LOGIN_NAME_MAX
    
    Change-Id: I26b7230433ecbbed6e6914ed39221a478c0266a8
    BUG: 1368138
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/16053
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 369c619f946f9ec1cf86cc83a7dcb11c29f1f0c7
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Dec 6 16:21:41 2016 +0530

    glusterfsd : fix null pointer dereference in glusterfs_handle_barrier
    
    Change-Id: Iab86a3c4970e54c22d3170e68708e0ea432a8ea4
    BUG: 1401921
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/16043
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2b4b928ed350286192b63b10b18f85c669b741f8
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Dec 7 17:27:02 2016 +0530

    tools/glusterfind: avoid deleting keys directory
    
    Problem:
    gluster volume delete mistakenly deletes the .keys directory under
    /var/lib/glusterd/glusterfind.
    
    Solution:
    Check for ".keys" directory and avoid deleting it.
    
    Change-Id: Ia595c8bf3f423c1ad5d6faa183a29598c07a11f9
    BUG: 1402369
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/16052
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a268e2865c21ec8d2b4fed26715e986cfcc66fad
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Nov 10 12:35:30 2016 +0530

    geo-rep: Do not restart workers when log-rsync-performance config change
    
    Geo-rep restarts workers when any of the configurations changed. We
    don't need to restart workers if tunables like log-rsync-performance
    is modified.
    
    With this patch, Geo-rep workers will get new "log-rsync-performance"
    config automatically without restart.
    
    BUG: 1393678
    Change-Id: I40ec253892ea7e70c727fa5d3c540a11e891897b
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15816
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit c4b39198df40535f589c9304fd07b06d948df2f5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 5 13:20:51 2016 +0530

    cluster/afr: Remove backward compatibility for locks with v1
    
    When we have cascading locks with same lk-owner there is a possibility for
    a deadlock to happen. One example is as follows:
    
    self-heal takes a lock in data-domain for big name with 256 chars of "aaaa...a"
    and starts heal in a 3-way replication when brick-0 is offline and healing from
    brick-1 to brick-2 is in progress. So this lock is active on brick-1 and
    brick-2. Now brick-0 comes online and an operation wants to take full lock and
    the lock is granted at brick-0 and it is waiting for lock on brick-1. As part
    of entry healing it takes full locks on all the available bricks and then
    proceeds with healing the entry. Now this lock will start waiting on brick-0
    because some other operation already has a granted lock on it. This leads to a
    deadlock. Operation is waiting for unlock on "aaaa..." by heal where as heal is
    waiting for the operation to unlock on brick-0. Initially I thought this is
    happening because healing is trying to take a lock on all the available bricks
    instead of just the bricks that are participating in heal. But later realized
    that same kind of deadlock can happen if a brick goes down after the heal
    starts but comes back before it completes. So the essential problem is the
    cascading locks with same lk-owner which were added for backward compatibility
    with afr-v1 which can be safely removed now that versions with afr-v1 are
    already EOL. This patch removes the compatibility with v1 which requires
    cascading locks with same lk-owner.
    
    In the next version we can make locking-scheme option a dummy and switch
    completely to v2.
    
    BUG: 1401404
    Change-Id: Ic9afab8260f5ff4dff5329eb0429811bcb879079
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/16024
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a7d7ed90c9272a42168a91f92754d3a4be605da5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Dec 1 09:42:19 2016 +0530

    cluster/afr: Serialize conflicting locks on all subvols
    
    Problem:
    1) When a blocking lock is issued and the parallel lock phase fails
    on all subvolumes with EAGAIN, it is not switching to serialized
    locking phase.
    2) When quorum is enabled and locks fail partially it is better
    to give errno returned by brick rather than the default
    quorum errno.
    
    Fix:
    Handled this error case and changed op_errno to reflect the actual
    errno in case of quorum error.
    
    BUG: 1369077
    Change-Id: Ifac2e4a13686e9fde601873012700966d56a7f31
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15984
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 622787887735d9157feac6cc57745251baca7b78
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Dec 1 15:05:06 2016 +0530

    build: Use %{_datadir} rpm macro in spec file
    
    Change-Id: I18383b2a5f0ff5233d47715c2e91514b6c3f2b7c
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/15985
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 4a9a5362f0b74046b7f161d485b2ffb44c027ead
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Nov 23 16:04:26 2016 +0530

    glusterd/ganesha : handle volume reset properly for ganesha options
    
    The "gluster volume reset" should first unexport the volume and then delete
    export configuration file. Also reset option is not applicable for ganesha.enable
    if volume value is "all".
    This patch also changes the name of create_export_config into manange_export_config
    
    Change-Id: Ie81a49e7d3e39a88bca9fbae5002bfda5cab34af
    BUG: 1397795
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15914
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b214b643d60cfb30c6578a570963ffc8f79073d8
Author: Muthu-vigneshwaran <mvignesh@redhat.com>
Date:   Thu Dec 1 15:59:26 2016 +0530

    glusterd : coverity fix for string overflow
    
    CID : 1357872, 1357873, 1351695
    
    BUG: 789278
    
    Change-Id: I2ee01a6054326f35de621ee7a1f2afd09c5738fe
    Signed-off-by: Muthu-vigneshwaran <mvignesh@redhat.com>
    Reviewed-on: http://review.gluster.org/15989
    Tested-by: Muthu Vigneshwaran
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ca13525a5de8db745878c4cdf89a45b76a9e62c6
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 5 21:14:57 2016 +0530

    afr: fix bug in passing child index in afr_inode_write_fill
    
    Change-Id: I7b70de317a5f15a3bf483ffe40b971143deddc11
    BUG: 1401218
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/16029
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit aa22f24f5db7659387704998ae01520708869873
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Sat Dec 3 01:10:51 2016 +0530

    rpc: fix for race between rpc and protocol/client
    
    It is possible that the notification thread which notifies
    protocol/client layer about the disconnection is put to sleep
    and meanwhile, a fuse thread or a timer thread initiates and
    completes reconnection to the brick. The notification thread
    is then woken up and protocol/client layer updates its flags
    to indicate that network is disconnected. No reconnection is
    initiated because reconnection is rpc-lib layer's responsibility
    and its flags indicate that connection is connected.
    
    Fix: Serialize connect and disconnect notify
    
    Credit: Raghavendra Talur <rtalur@redhat.com>
    Change-Id: I8ff5d1a3283b47f5c26848a42016a40bc34ffc1d
    BUG: 1386626
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15916
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 45f914ec9c7b15ba8e962b8fae3593f06912c1f0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Dec 1 17:28:40 2016 +0530

    extras: Include shard and full-data-heal in virt group
    
    Change-Id: Iea66cb017bd1ab62da9cd65895fa65fc6896108b
    BUG: 1375431
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15995
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c89cb610f51e7a5df5c4b7e9378a7ac8ac513e46
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sat Dec 3 09:09:15 2016 +0530

    afr, client: More mem-leak fixes in COMPOUND fop cbk
    
    Bugs found and fixed:
    1. Use correct subvolume index in pre-op-writev compound cbk
    2. Prevent use-after-free of local->compound_args members in
       compound fops cbk in protocol/client
    3. Fix xdata and xattr leaks in client_process_response
    4. Fix possible leak of xdata in client_pre_writev() in
       test mode.
    5. Free req->compound_req_array.compound_req_array_val as well
       after freeing its members
    6. Free tmp_rsp->flock.lk_owner.lk_owner_val in LK fop.
    
    Change-Id: I15b646d7d4e0e5cd4ea3d2d6452c815cf2eaf68f
    BUG: 1401218
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/16020
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 55ddf8c6b665d0b2ed024b984e871a68b25cffbf
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Dec 2 13:15:20 2016 +0530

    cluster/ec: Check xdata to avoid memory leak
    
    Problem: ec_writev_start calls ec_make_internal_fop_xdata
    to set "yes" in xdata before ec_readv (an internal fop)
    is called for head and tail. Second call to this function
    is overwriting the previous allocated dict_t to "xdata",
    which results in memory leak.
    
    Solution: In ec_make_internal_fop_xdata, check if *xdata
    is NULL or not to avoid overwriting *xdata.
    
    Change-Id: I49b83923e11aff9b92d002e86424c0c2e1f5f74f
    BUG: 1400818
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/16007
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 99458974b7d12bd12d78d4b9a19adfb62d771b5c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Nov 29 16:32:54 2016 +0530

    eventsapi: Push Messages to Webhooks in parallel
    
    With this patch, glustereventsd will maintain one thread per
    webhook. If a webhook is slow, then all the events to that worker
    will be delayed but it will not affect the other webhooks.
    
    Note: Webhook in transit may get missed if glustereventsd reloads due to
    new Webhook addition or due configuration changes.
    
    BUG: 1357754
    Change-Id: I2d11e01c7ac434355bc356ff75396252f51b339b
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15966
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4536f7bdf16f8286d67598eda9a46c029f0c0bf4
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Nov 8 10:32:29 2016 +0530

    dht/md-cache: Filter invalidate if the file is made a linkto file
    
    Upcall as a part of setattr, sends an invalidation and the
    invalidation carries the resulting stat value. When a file
    is converted to linkto files, even then an invalidation
    is set and as a result the mountpoint shows the sticky
    bit in the stat of the file.
    eg: ---------T. 945 root root 0 Nov  8 10:14 hardlink.999
    
    Fix:
    When dht recieves a notification of sticky bit change, it updates
    the flag, to indicate md-cache to send the subsequent lookup.
    
    Change-Id: Ic2fd7a5b196db0754f9b97072e644e6bf69da606
    BUG: 1392713
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15789
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 91e72a0f2e4e51ce20550946578a6d50cbb88e26
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Nov 16 16:50:50 2016 +0530

    geo-rep/eventsapi: Add Master node information in Geo-rep Events
    
    Added Master node information to GEOREP_ACTIVE, GEOREP_PASSIVE, GEOREP_FAULTY
    and GEOREP_CHECKPOINT_COMPLETED events.
    
    EVENT_GEOREP_ACTIVE(master_node and master_node_id are new fields)
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": "GEOREP_ACTIVE",
        "message": {
            "master_volume": MASTER_VOLUME_NAME,
            "master_node": MASTER_NODE,
            "master_node_id": MASTER_NODE_ID,
            "slave_host": SLAVE_HOST,
            "slave_volume": SLAVE_VOLUME,
            "brick_path": BRICK_PATH
        }
    }
    
    EVENT_GEOREP_PASSIVE(master_node and master_node_id are new fields)
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": "GEOREP_PASSIVE",
        "message": {
            "master_volume": MASTER_VOLUME_NAME,
            "master_node": MASTER_NODE,
            "master_node_id": MASTER_NODE_ID,
            "slave_host": SLAVE_HOST,
            "slave_volume": SLAVE_VOLUME,
            "brick_path": BRICK_PATH
        }
    }
    
    EVENT_GEOREP_FAULTY(master_node and master_node_id are new fields)
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": "GEOREP_FAULTY",
        "message": {
            "master_volume": MASTER_VOLUME_NAME,
            "master_node": MASTER_NODE,
            "master_node_id": MASTER_NODE_ID,
            "current_slave_host": CURRENT_SLAVE_HOST,
            "slave_host": SLAVE_HOST,
            "slave_volume": SLAVE_VOLUME,
            "brick_path": BRICK_PATH
        }
    }
    
    EVENT_GEOREP_CHECKPOINT_COMPLETED(master_node and master_node_id are new fields)
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": "GEOREP_CHECKPOINT_COMPLETED",
        "message": {
            "master_volume": MASTER_VOLUME_NAME,
            "master_node": MASTER_NODE,
            "master_node_id": MASTER_NODE_ID,
            "slave_host": SLAVE_HOST,
            "slave_volume": SLAVE_VOLUME,
            "brick_path": BRICK_PATH,
            "checkpoint_time": CHECKPOINT_TIME,
            "checkpoint_completion_time": CHECKPOINT_COMPLETION_TIME
        }
    }
    
    BUG: 1395660
    Change-Id: Ic91af52fa248c8e982e93a06be861dfd69689f34
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15858
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit fb95eb4da6f4fc0b9c69e3b159a2214fe47e6d1d
Author: Mateusz Slupny <mateusz.slupny@appeartv.com>
Date:   Tue Nov 29 12:01:48 2016 +0100

    selfheal: fix memory leak on client side healing queue
    
    Change-Id: I2beaba829710565a3246f7449a5cd21755cf5f7d
    BUG: 1399592
    Signed-off-by: Mateusz Slupny <mateusz.slupny@appeartv.com>
    Reviewed-on: http://review.gluster.org/15968
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit da71bdcf82a8dc71a1170ad3f190702fa49d2838
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Nov 17 15:42:24 2016 +0530

    eventsapi: JSON output and different error codes
    
    JSON outputs are added to all commands, use `--json` to
    get JSON output.
    
    Following error codes are added to differenciate between errors.
    Any other Unknown errors will have return code 1
    
    ERROR_SAME_CONFIG             = 2
    ERROR_ALL_NODES_STATUS_NOT_OK = 3
    ERROR_PARTIAL_SUCCESS         = 4
    ERROR_WEBHOOK_ALREADY_EXISTS  = 5
    ERROR_WEBHOOK_NOT_EXISTS      = 6
    ERROR_INVALID_CONFIG          = 7
    ERROR_WEBHOOK_SYNC_FAILED     = 8
    ERROR_CONFIG_SYNC_FAILED      = 9
    
    Also hidden `node-` commands in the help message.
    
    BUG: 1357753
    Change-Id: I962b5435c8a448b4573059da0eae42f3f93cc97e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15867
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 47e69455d3aede77960fd81a7cf3d6b4a869dbfa
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Nov 22 01:51:19 2016 +0530

    glusterfsd: glusterfs_ctx_defaults_init should not re-initialize ctx->locks
    
    glusterfs_ctx_new already initialize ctx->locks therefore the second
    initialization in glusterfs_ctx_defaults_init does not make sense.
    
    Change-Id: I6027cbd311da8e80585e0f0dcd6916e3bc8dd284
    BUG: 1397419
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15905
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 530453c78146e8ba4f13636e1dec1ea59849c783
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Dec 1 18:18:27 2016 +0530

    cluster/tier: fix op-version for tier-query-limit
    
    Correct the op-version for tier-query-limit option from 3.9.0 to 3.9.1
    
    Change-Id: I3a52a94c2708a97c18377e945d559a51d8025c41
    BUG: 1366648
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15990
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 76eef16d762f500df500de0d3187aff23dc39ac6
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Nov 28 19:18:51 2016 +0530

    ganesha/scripts : avoid incrementing Export Id value for already exported volumes
    
    Currently a volume will unexport when it stops and reexport it during volume start
    using hook script. And also it increments the value for export id for each reexport.
    Since a hook script is called from every node parallely which may led inconsistency
    for export id value.
    
    Change-Id: Ib9f19a3172b2ade29a3b4edc908b3267c68c0b20
    BUG: 1399186
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15948
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 57d59f4be205ae0c7888758366dc0049bdcfe449
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Nov 21 18:08:14 2016 +0530

    dht/rename : Incase of failure remove linkto file properly
    
    Generally linkto file is created using root user. Consider following
    case, a user is trying to rename a file which he is not permitted.
    So the rename fails with EACESS and when rename tries to cleanup the
    linkto file, it fails.
    
    The above issue happens when rename/00.t test executed on nfs-ganesha
    clients :
    Steps executed in script
    * create a file "abc" using root
    * rename the file "abc" to "xyz" using a non root user, it fails with EACESS
    * delete "abc"
    * create directory "abc" using root
    * again try ot rename "abc" to "xyz" using non root user, test hungs here
    which slowly leds to OOM kill of ganesha process
    
    RCA put forwarded by Du for OOM kill of ganesha
    Note that when we hit this bug, we've a scenario of a dentry being
    present as:
        * a linkto file on one subvol
        * a directory on rest of subvols
    
    When a lookup happens on the dentry in such a scenario, the control flow
    goes into an infinite loop of:
    
        dht_lookup_everywhere
        dht_lookup_everywhere_cbk
        dht_lookup_unlink_cbk
        dht_lookup_everywhere_done
        dht_lookup_directory (as local->dir_count > 0)
        dht_lookup_dir_cbk (sets to local->need_selfheal = 1 as the entry is a linkto file on one of the subvol)
        dht_lookup_everywhere (as need_selfheal = 1).
    
    This infinite loop can cause increased consumption of memory due to:
    1) dht_lookup_directory assigns a new layout to local->layout unconditionally
    2)  Most of the functions in this loop do a stack_wind of various fops.
    
    This results in growing of call stack (note that call-stack is destroyed only after lookup response is
    received by fuse - which never happens in this case)
    
    Thanks Du for root causing the oom kill and Sushant for suggesting the fix
    
    Change-Id: I1e16bc14aa685542afbd21188426ecb61fd2689d
    BUG: 1397052
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15894
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bdcc3ac42b6247329578c984403bac1cf8a2c02e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Nov 30 13:00:16 2016 -0500

    common-ha: IPaddr RA is not stopped when pacemaker quorum is list
    
    Ken Gaillot writes:
    The other is pacemaker's no-quorum-policy cluster property. The
    default (which has not changed) is "stop" (stop all resources).
    Other values are "ignore" (act as if quorum was not lost),
    "freeze" (continue running existing resources but don't recover
    resources from unseen nodes) or "suicide" (shut down).
    
    But on my four node cluster
    % pcs property show no-quorum-policy
    Cluster Properties:
    %
    
    i.e. shows nothing.
    
    But:
    % pcs property list --all
    Cluster Properties:
    ...
     no-quorum-policy: stop
    ...
    %
    
    Seems to think it knows about it.
    
    and then
    % pcs property set no-quorum-policy=stop
    % pcs property show no-quorum-policy
    Cluster Properties:
     no-quorum-policy: stop
    %
    
    Which looks rather inconsistent. So we will try explicitly
    setting it to "stop" when there are three or more nodes.
    
    Change-Id: I47fc7ee84fcd6ad52ccb776913511978a8d517b4
    BUG: 1400237
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15981
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6138f4a2fc835bc94aa66543f5aee4f92081f1c7
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Nov 30 19:38:03 2016 +0530

    build: add systemd dependency to the glusterfs sub-package
    
    Problem:
    /bin/systemctl is not available at install time of primary glusterfs
    package.
    
    Solution:
    Add %{?systemd_requires} to the glusterfs sub-package install time
    requirements.
    
    Replace all "Requires: systemd" and "Requires: systemd-units" with
    %{?systemd_requires}. %systemd_requires is defined in
    /usr/lib/rpm/macros.d/macros.systemd
    systemd-units is provided by systemd.
    Add BuildRequires: systemd for the definition of %systemd_requires
    as well.
    
    Change-Id: I980ece7d538ea177ca6b0e70c1c169e6f04c46d4
    BUG: 1399031
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15936
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 331a45942333e27f596b1930f7d459f59850c8a4
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Wed Nov 30 14:35:59 2016 +0530

    glusterd, cli: Fix volume options output format in get-state cli
    
    Currently the get-state cli outputs the volume options in the
    following format:
    
    Volume1.rebalance.skipped: 0
    Volume1.rebalance.lookedup: 0
    Volume1.rebalance.files: 0
    Volume1.rebalance.data: 0Bytes
    [Volume1.options]
    features.barrier: on
    transport.address-family: inet
    performance.readdir-ahead: on
    nfs.disable: on
    
    Volume2.name: tv2
    Volume2.id: 35854708-bb72-45a5-bdbd-77c51e5ebfb9
    Volume2.type: Distribute
    
    This above format is a valid ini file format syntactically, but is
    not very easily parseable. This patch changes the format to look like
    the following and should be more easily parseable:
    
    Volume1.rebalance.skipped: 0
    Volume1.rebalance.lookedup: 0
    Volume1.rebalance.files: 0
    Volume1.rebalance.data: 0Bytes
    Volume1.options.features.barrier: on
    Volume1.options.transport.address-family: inet
    Volume1.options.performance.readdir-ahead: on
    Volume1.options.nfs.disable: on
    
    Volume2.name: tv2
    Volume2.id: 35854708-bb72-45a5-bdbd-77c51e5ebfb9
    Volume2.type: Distribute
    
    Change-Id: I9768b45de288d9817ec669d3a801874eb1914750
    BUG: 1399995
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/15975
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shubhendu Tripathi <shtripat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5bc501fde8d8d81ed4bd12edc306bc2c6fa268e4
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Nov 18 13:07:50 2016 -0500

    common-ha: add cluster HA status to --status output for gdeploy
    
    gdeploy desires a one-liner "health" assessment.
    
    If all the VIP and port block/unblock RAs are located on their
    prefered nodes and 'Started', then the cluster is deemed to be
    good (healthy).
    
    N.B. status originally only checked the "online" nodes obtained
    from `pcs status` but we really want to consider all the configured
    nodes, whether they are online or not.
    
    Also one `pcs status` is enough.
    
    Change-Id: Id0e0380b6982e23763edeb0488843b5363e370b8
    BUG: 1395648
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15882
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 1b2b5be970f78cc32069516fa347d9943dc17d3e
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Nov 28 17:56:35 2016 +0530

    common-HA: Increase timeout for portblock RA of action=unblock
    
    Portblock RA of action type unblock stores the information about
    the client/server IPs connection in tickle_dir folder created in
    the shared storage. In case of node shutdown/reboot there could be
    cases wherein shared_storage may become unavailable for sometime.
    Hence increase the timeout to avoid that resource agent going into
    FAILED state.
    
    Change-Id: I4f98f819895cb164c3a82ba8084c7c11610f35ff
    BUG: 1399154
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/15947
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 182f0d12040dab5081ca645a3f370f65cd68b528
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Nov 29 21:57:37 2016 +0530

    uss: snapd should enable SSL if SSL is enabled on volume
    
    During snapd graph generation we should check if SSL is
    enabled on main volume or not. This is because clients
    will communicate with snapd as if it is communicating to
    a brick.
    
    Change-Id: I0d7fe86c567b297a8528a48faf06161d4c3cb415
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    BUG: 1400013
    Reviewed-on: http://review.gluster.org/15979
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 5b809fa434368b7395b180c41b46bce1a38e0cf9
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Wed Nov 30 15:43:26 2016 +0530

    glusterd: Remove duplicate values for glusterd message macros
    
    Both GD_MSG_BRICK_CLEANUP_SUCCESS and GD_MSG_DAEMON_STATE_REQ_RCVD
    macros are assigned the same value (GLUSTERD_COMP_BASE + 584). Also
    the number of messages should be 588 instead of 587
    
    Change-Id: I015d32435c05ded1b14cd8ba11911af826bc956b
    BUG: 1400026
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/15980
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 955d9700397fda6ada269fc3077116b7756702a5
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Nov 29 12:56:40 2016 +0530

    protocol/server: Fix mem-leaks in compound fops
    
    * Remove spurious 'return' statement.
    * Free up 'compound_rsp_array_val' as well in the end.
    * Remove multiple refs on this_args->xdata.
    
    Change-Id: I212c6dbe4d81b0381c1323d05fdfcc853886b25b
    BUG: 1399578
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15965
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 17d10b42fc4041442e6cd0bfda45944edea498c6
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Nov 22 22:25:42 2016 +0530

    gfapi: glfs_subvol_done should NOT wait for graph migration.
    
    In graph_setup function glfs_subvol_done is called which
    is executed in an epoll thread. glfs_lock waits on other
    thread to finish graph migration. This can lead to dead lock
    if we consume all the epoll threads.
    
    In general any call-back function executed in epoll thread
    should not call any blocking call which waits on a network
    reply either directly or indirectly, e.g. syncop functions
    should not be called in these threads.
    
    As a fix we should not wait for migration in the call-back path.
    
    Change-Id: If96d0689fe1b4d74631e383048cdc30b01690dc2
    BUG: 1397754
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15913
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e34a783557e504f0793f18beb850bcebbb2af7fa
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Nov 22 10:18:50 2016 -0500

    all: remove dead translators
    
    The following have been completely removed from the source tree,
    makefiles, configure script, and RPM specfile.
    
      cluster/afr/pump
      cluster/ha
      cluster/map
      features/filter
      features/mac-compat
      features/path-convertor
      features/protect
    
    Change-Id: I2f966999ac3c180296ff90c1799548fba504f88f
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/15906
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 71dd2e914d4a537bf74e1ec3a24512fc83bacb1d
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Nov 17 16:20:40 2016 +0530

    cluster/dht: A hard link is lost during rebalance + lookup
    
    Problem:  A hard link is lost during rebalance + lookup.Rebalance skip files
              if file has hardlink.In dht_migrate_file __is_file_migratable ()
              function checks if a file has hardlink, if yes file is not migrated
              but if link is created after call this function then link will lost.
    
    Solution: Call __check_file_has_hardlink to check hardlink existence after (S+T) bits
              in migration process ,if file has hardlink then skip the file for
              migrate rebalance process.
    
    BUG: 1396048
    Change-Id: Ia53c07ef42f1128c2eedf959a757e8df517b9d12
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15866
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 77f03db0131c88d607886bb02dd2a4276ab584d4
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Nov 17 10:42:02 2016 -0500

    afr: fix auto-quorum
    
    (1) afr_have_quorum is dead code.  It was copied to afr_has_quorum,
    and everything else uses that, but the original was never deleted
    (until now).
    
    (2) Auto-quorum should be default for any N>2.  Leaving quorum
    disabled is BAD, but apparently deemed acceptable for N=2 because
    there's no real quorum in that case.  For any larger number (including
    arbiter configurations) there is such a thing as real quorum and we
    should use it by default.  Note that for N=3 the answers we get from
    "N % 2" (the old check) and "N > 2" (the new one) are the same.
    
    (3) The special case for even N in afr_has_quorum has been simplified and
    explained more thoroughly in a comment.
    
    Change-Id: I48b33c15093512fecf516b26dcf09afecb7ae33b
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/15873
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1876454d2e7950f25d1e5bb8e2c07ab27d521498
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Nov 17 17:47:29 2016 +0530

    geo-rep: Fix Last synced status column issue during Hybrid Crawl
    
    During Hybrid crawl, Geo-rep maintains stime xattr in subdirectories along
    with the Brick root. This is done to skip directories if Geo-rep crashes
    before Hybrid crawl completes.
    
    Update Last synced status only when stime xattr updated in brick root.
    Status output will mislead if it shows sub directory stime as
    last synced time.
    
    BUG: 1396081
    Change-Id: I5b73aee7ae4a1c1e2d1001d1f55559b9f9efd6e6
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15869
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 570aefeb280e53e98cb5060cf384f1d74379a521
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Nov 21 11:49:35 2016 +0530

    afr: Fix the EIO that can occur in afr_inode_refresh as a result
         of cache invalidation(upcall).
    
    Issue:
    ------
    When a cache invalidation is recieved as a result of changing
    pending xattr, the read_subvol is reset. Consider the below chain
    of execution:
    
    CHILD_DOWN
    ...
    afr_readv
    ...
    afr_inode_refresh
    ...
    afr_inode_read_subvol_reset <- as a result of pending xattr set by
                                   some other client GF_EVENT_UPCALL will
                                   be sent
    afr_refresh_done -> this results in an EIO, as the read subvol was
                        reset by the end of the afr_inode_refresh
    
    Solution:
    ---------
    When GF_EVENT_UPCALL is recieved, instead of resetting read_subvol,
    set a variable need_refresh in inode_ctx, the next time some one
    starts a txn, along with event gen, need_rrefresh also needs to
    be checked.
    
    Change-Id: Ifda21a7a8039b8874215e1afa4bdf20f7d991b58
    BUG: 1396952
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15892
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8943c19a2ef51b6e4fa66cb57211d469fe558579
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Nov 21 19:57:08 2016 +0530

    libglusterfs: Fix a read hang
    
    Issue:
    =====
    In certain cases, there was no unwind of read
    from read-ahead xlator, thus resulting in hang.
    
    RCA:
    ====
    In certain cases, ioc_readv() issues STACK_WIND_TAIL() instead
    of STACK_WIND(). One such case is when inode_ctx for that file
    is not present (can happen if readdirp was called, and populates
    md-cache and serves all the lookups from cache).
    
    Consider the following graph:
    ...
    io-cache (parent)
       |
    readdir-ahead
       |
    read-ahead
    ...
    
    Below is the code snippet of ioc_readv calling STACK_WIND_TAIL:
    ioc_readv()
    {
    ...
     if (!inode_ctx)
       STACK_WIND_TAIL (frame, FIRST_CHILD (frame->this),
                        FIRST_CHILD (frame->this)->fops->readv, fd,
                        size, offset, flags, xdata);
       /* Ideally, this stack_wind should wind to readdir-ahead:readv()
          but it winds to read-ahead:readv(). See below for
          explaination.
        */
    ...
    }
    
    STACK_WIND_TAIL (frame, obj, fn, ...)
    {
      frame->this = obj;
      /* for the above mentioned graph, frame->this will be readdir-ahead
       * frame->this = FIRST_CHILD (frame->this) i.e. readdir-ahead, which
       * is as expected
       */
      ...
      THIS = obj;
      /* THIS will be read-ahead instead of readdir-ahead!, as obj expands
       * to "FIRST_CHILD (frame->this)" and frame->this was pointing
       * to readdir-ahead in the previous statement.
       */
      ...
      fn (frame, obj, params);
      /* fn will call read-ahead:readv() instead of readdir-ahead:readv()!
       * as fn expands to "FIRST_CHILD (frame->this)->fops->readv" and
       * frame->this was pointing ro readdir-ahead in the first statement
       */
      ...
    }
    
    Thus, the readdir-ahead's readv() implementation will be skipped, and
    ra_readv() will be called with frame->this = "readdir-ahead" and
    this = "read-ahead". This can lead to corruption / hang / other problems.
    But in this perticular case, when 'frame->this' and 'this' passed
    to ra_readv() doesn't match, it causes ra_readv() to call ra_readv()
    again!. Thus the logic of read-ahead readv() falls apart and leads to
    hang.
    
    Solution:
    =========
    Modify STACK_WIND_TAIL() as:
    STACK_WIND_TAIL (frame, obj, fn, ...)
    {
      next_xl = obj /* resolve obj as the variables passed in obj macro
                       can be overwritten in the further instrucions */
      next_xl_fn = fn /* resolve fn and store in a tmp variable, before
                         modifying any variables */
      frame->this = next_xl;
      ...
      THIS = next_xl;
      ...
      next_xl_fn (frame, next_xl, params);
      ...
    }
    
    As a part of http://review.gluster.org/15901/ the caller io-cache
    was fixed.
    
    BUG: 1388292
    Change-Id: Ie662ac8f18fa16909376f1e59387bc5b886bd0f9
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15923
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a3e5c0566a7d867d16d80ca28657238ff1008a22
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Nov 28 13:42:33 2016 +0530

    cluster/ec: Healing should not start if only "data" bricks are UP
    
    Problem: In a disperse volume with "K+R" configuration, where
    "K" is the number of data bricks and "R" is the number of redundancy
    bricks (Total number of bricks, N = K+R), if only K bricks are UP,
    we should NOT start heal process. This is because the bricks, which
    are supposed to be healed, are not UP. This will unnecessary
    eat up the resources.
    
    Solution: Check for the number of xl_up_count and only
    if it is greater than ec->fragments (number of data bricks),
    start heal process.
    
    Change-Id: I8579f39cfb47b65ff0f76e623b048bd67b15473b
    BUG: 1399072
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/15937
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 6dfc90fcd36956dcc4f624b3912bfb8e9c95757f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 22 16:48:54 2016 +0530

    cluster/afr: CLI for granular entry heal enablement/disablement
    
    When there are already existing non-granular indices created that are
    yet to be healed, if granular-entry-heal option is toggled from 'off' to
    'on', AFR self-heal whenever it kicks in, will try to look for granular
    indices in 'entry-changes'. Because of the absence of name indices,
    granular entry healing logic will fail to heal these directories, and
    worse yet unset pending extended attributes with the assumption that
    are no entries that need heal.
    
    To get around this, a new CLI is introduced which will invoke glfsheal
    program to figure whether at the time an attempt is made to enable
    granular entry heal, there are pending heals on the volume OR there
    are one or more bricks that are down. If either of them is true, the
    command will be failed with the appropriate error.
    
    New CLI: gluster volume heal <VOL> granular-entry-heal {enable,disable}
    
    Change-Id: I1f4fe8162813b9068e198965d94169fee4adc099
    BUG: 1370410
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15747
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit cc37e5929d1e3ea4eaf4c4576a82066bf131ad05
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Nov 24 08:31:47 2016 +0530

    protocol/server: capture offset in seek
    
    Problem:
    http://review.gluster.org/11482 implemented seek FOP but
    http://review.gluster.org/#/c/14137/ 'undid' the change where we pack
    the offset returned by seek in server xlator before sending it to the client.
    As a result, seek always returns zero to the client for SEEK_HOLE/
    SEEK_DATA.
    
    Fix:
    I think 14137 removed it unintentionally, hence adding it back again.
    
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Change-Id: I67a1f7b53214b043c5291f5704be4a50b698f91c
    BUG: 1398076
    Reviewed-on: http://review.gluster.org/15920
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2e859ee88f285a098a5c02bd2bdc0cd4bbd44d56
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Fri Sep 23 13:57:55 2016 +0530

    gfapi: Fix memory leak in glfs-mgmt
    
    dictionary was not freed after serialization
    
    Change-Id: I495f2f823b0d53a0d858876bde41fde5f0705113
    BUG: 1397177
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15895
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a07ddd8fcc8dcdcf7ccfa61211d258f13b9f9229
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat Nov 26 21:24:01 2016 +0530

    afr: allow I/O when favorite-child-policy is enabled
    
    Problem:
    Currently, I/O on a split-brained file fails even when the
    favorite-child-policy is set until the self-heal is complete.
    
    Fix:
    If a valid 'source' is found using the set favorite-child-policy, inspect
    and reset the afr pending xattrs on the 'sinks' (inside appropriate locks),
    refresh the inode and then proceed with the read or write transaction.
    
    The resetting itself happens in the self-heal code and hence can also
    happen in the client side background-heal or by the shd's index-heal in
    addition to the txn code path explained above. When it happens in via
    heal, we also add checks in undo-pending to not reset the sink xattrs
    again.
    
    Change-Id: Ic8c1317720cb26bd114b6fe6af4e58c73b864626
    BUG: 1386188
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reported-by: Simon Turcotte-Langevin <simon.turcotte-langevin@ubisoft.com>
    Reviewed-on: http://review.gluster.org/15673
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2214501d6045b45dde469c5a476c86b6cf464c34
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 17 21:02:29 2016 +0530

    protocol/server: Print pargfid in logs for rename error
    
    BUG: 1394548
    Change-Id: I42ee627c8cdf54158f083f9019a096ace449e3cc
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15872
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 6be7bd936eb30aa8d2b908061f60e1534e797657
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Nov 7 14:47:34 2016 +0530

    cluster/afr: Fix bugs in [f]inodelk/[f]entrylk
    
    Problems:
    1) Inodelk is not taking quorum into account
    2) finodelk, [f]entrylk are not implemented correctly
    3) By default afr doesn't go for non-blocking parallel locks.
    
    Fix:
    Implemented a common framework which can be used by
    [f]inodelk/[f]entrylk.  Used quorum for the same.
    
    Change-Id: I239f13875a065298630d266941df10cfa3addc85
    BUG: 1369077
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15802
    Tested-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 2fe8ba52108e94268bc816ba79074a96c4538271
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Nov 25 15:54:30 2016 +0530

    cluster/afr: Fix deadlock due to compound fops
    
    When an afr data transaction is eligible for using
    eager-lock, this information is represented in
    local->transaction.eager_lock_on. However, if non-blocking
    inodelk attempt (which is a full lock) fails, AFR falls back
    to blocking locks which are range locks. At this point,
    local->transaction.eager_lock[] per brick is reset but
    local->transaction.eager_lock_on is still true.
    When AFR decides to compound post-op and unlock, it is after
    confirming that the transaction did not use eager lock (well,
    except for a small bug where local->transaction.locks_acquired[]
    is not considered).
    
    But within afr_post_op_unlock_do(), afr again incorrectly sets
    the lock range to full-lock based on local->transaction.eager_lock_on
    value. This is a bug and can lead to deadlock since the locks acquired
    were range locks and a full unlock is being sent leading to unlock failure
    and thereby every other lock request (be it from SHD or other clients or
    glfsheal) getting blocked forever and the user perceives a hang.
    
    FIX:
    Unconditionally rely on the range locks in inodelk object for unlocking
    when using compounded post-op + unlock.
    
    Big thanks to Pranith for helping with the debugging.
    
    Change-Id: Idb4938f90397fb4bd90921f9ae6ea582042e5c67
    BUG: 1398566
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15929
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 3a5169907b44d79e207c35941b1973b1f60d2079
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Nov 24 18:36:28 2016 +0530

    cluster/afr: Handle rpc errors, xdr failures etc with proper NULL checks
    
    Change-Id: Id8ba76ba116d056bc7299dc5ce0980680a5a23f8
    BUG: 1398226
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15924
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e966fcbc2808eb474ccf83290fe488eb2f10c9d1
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Nov 18 15:38:00 2016 +0530

    features/index: Delete granular entry indices of already healed directories during crawl
    
    If granular name indices are already in existence for a volume, and
    before they are healed, granular entry heal be disabled, a crawl on
    indices/xattrop will clear the changelogs on these directories. When
    their corresponding entry-changes indices are crawled subsequently,
    if it is found that the directories don't need heal anymore, the
    granular indices are not cleaned up.
    This patch fixes that problem by ensuring that the zero-xattrop
    also deletes the stale indices at the level of index translator.
    
    Change-Id: Ifbaa6bec2a14e3041addfee4054131babbf4d35e
    BUG: 1370410
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15880
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8df8a2308fcf5efda638f160428158127930d00f
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Nov 22 01:48:26 2016 +0530

    cli: glusterfs_ctx_defaults_init should not re-initialize ctx->locks
    
    glusterfs_ctx_new already initialize ctx->locks therefore the second
    initialization in glusterfs_ctx_defaults_init does not make sense.
    
    Change-Id: I8a44bed13af20e60e8bafb05360e88c0b237056c
    BUG: 1397419
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15904
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 114c50c1a10d649a8b640627f09fd5872828d4ec
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Nov 21 19:57:08 2016 +0530

    io-cache: Fix a read hang
    
    Issue:
    =====
    In certain cases, there was no unwind of read
    from read-ahead xlator, thus resulting in hang.
    
    RCA:
    ====
    In certain cases, ioc_readv() issues STACK_WIND_TAIL() instead
    of STACK_WIND(). One such case is when inode_ctx for that file
    is not present (can happen if readdirp was called, and populates
    md-cache and serves all the lookups from cache).
    
    Consider the following graph:
    ...
    io-cache (parent)
       |
    readdir-ahead
       |
    read-ahead
    ...
    
    Below is the code snippet of ioc_readv calling STACK_WIND_TAIL:
    ioc_readv()
    {
    ...
     if (!inode_ctx)
       STACK_WIND_TAIL (frame, FIRST_CHILD (frame->this),
                        FIRST_CHILD (frame->this)->fops->readv, fd,
                        size, offset, flags, xdata);
       /* Ideally, this stack_wind should wind to readdir-ahead:readv()
          but it winds to read-ahead:readv(). See below for
          explaination.
        */
    ...
    }
    
    STACK_WIND_TAIL (frame, obj, fn, ...)
    {
      frame->this = obj;
      /* for the above mentioned graph, frame->this will be readdir-ahead
       * frame->this = FIRST_CHILD (frame->this) i.e. readdir-ahead, which
       * is as expected
       */
      ...
      THIS = obj;
      /* THIS will be read-ahead instead of readdir-ahead!, as obj expands
       * to "FIRST_CHILD (frame->this)" and frame->this was pointing
       * to readdir-ahead in the previous statement.
       */
      ...
      fn (frame, obj, params);
      /* fn will call read-ahead:readv() instead of readdir-ahead:readv()!
       * as fn expands to "FIRST_CHILD (frame->this)->fops->readv" and
       * frame->this was pointing ro readdir-ahead in the first statement
       */
      ...
    }
    
    Thus, the readdir-ahead's readv() implementation will be skipped, and
    ra_readv() will be called with frame->this = "readdir-ahead" and
    this = "read-ahead". This can lead to corruption / hang / other problems.
    But in this perticular case, when 'frame->this' and 'this' passed
    to ra_readv() doesn't match, it causes ra_readv() to call ra_readv()
    again!. Thus the logic of read-ahead readv() falls apart and leads to
    hang.
    
    Solution:
    =========
    Ideally, STACK_WIND_TAIL() should be modified as:
    STACK_WIND_TAIL (frame, obj, fn, ...)
    {
      next_xl = obj /* resolve obj as the variables passed in obj macro
                       can be overwritten in the further instrucions */
      next_xl_fn = fn /* resolve fn and store in a tmp variable, before
                         modifying any variables */
      frame->this = next_xl;
      ...
      THIS = next_xl;
      ...
      next_xl_fn (frame, next_xl, params);
      ...
    }
    But for this solution, knowing the type of variable 'next_xl_fn' is
    a challenge and is not easy. Hence just modifying all the existing
    callers to pass "FIRST_CHILD (this)" as obj, instead of
    "FIRST_CHILD (frame->this)".
    
    Change-Id: I179ffe3d1f154bc5a1935fd2ee44e912eb0fbb61
    BUG: 1388292
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15901
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 63a4f5da0feb19e47d16aa2d6aa78efaef1c93ca
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Nov 22 19:04:54 2016 +0530

    glusterd: fix few events generation
    
    This patch does the following:
    1. Generate PEER_REJECT event if the peer add request is from an unknown peer
    during peer handshaking.
    2. EVENT_COMPARE_FRIEND_VOLUME_FAILED should be generated based on status code,
    not ret.
    3. Add EVENT_BRICKPATH_RESOLVE_FAILED event in case glusterd fails to resolve
    bricks, this is mainly at restore path.
    4. Remove EVENT_BRICKS_START_FAILED event as we already have
    EVENT_BRICK_START_FAILED
    
    Change-Id: I90e5bc4a331166d0bb3554eb2ec9df2526837a1d
    BUG: 1397424
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15903
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit ecd6da0a754f21909dbbd8189228f5a27a15df3e
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Nov 17 17:07:36 2016 +0530

    geo-rep: Handle ENOENT during unlink
    
    Do not raise traceback if a file/dir not exists during
    unlink or rmdir
    
    BUG: 1396062
    Change-Id: Idd43ca1fa6ae6056c3cd493f0e2f151880a3968c
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15868
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ded44a2627e5421880ffcc798f2838f52faaf322
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Nov 22 06:34:35 2016 +0000

    protocol/server: Remove unused variable
    
    Change-Id: I0d0a786b2d02d4db37c4da6194ee4b4feac31b63
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/15899
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 277008a3a8583ef10cec9e4182960792e56c5c10
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon Nov 14 15:40:32 2016 +0530

    libglusterfs:Now mempool is added to ctx pool list under a lock
    
    mempool is added to ctx pool list without any lock. This can cause undefined
    behaviour in case of multithreaded environment.
    
    Fix: modify the list only under ctx->lock
    
    Change-Id: I7bdbb3db48a899bb0e41427e149b13c0facaedba
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    BUG: 1394719
    Reviewed-on: http://review.gluster.org/15842
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 7b80a0f02fa0c27f5f5e89e69f92678145fd6a7f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Nov 20 18:18:45 2016 +0530

    glusterd: dump volinfo->dict in gluster get-state
    
    Change-Id: I7e60629fb8003c620847fa63441f6b098db59721
    BUG: 1396807
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15889
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Rohan Kanade <rkanade@redhat.com>

commit 25817a8c868b6c1b8149117f13e4216a99e453aa
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 18 13:30:08 2016 +0530

    performance/io-threads: Exit threads in fini() as well
    
    Problem:
    io-threads starts the thread in 'init()' but doesn't clean them up
    on 'fini()'. It relies on PARENT_DOWN to exit threads but there can
    be cases where event before PARENT_UP the graph init code can think
    of issuing fini(). This code path is hit when glfs_init() is called
    on a volume that is in 'stopped' state. It leads to a crash in ganesha
    process, because the io-thread tries to access freed memory.
    
    Fix:
    Ideal fix would be to wait for all fops in io-thread list to be completed on
    PARENT_DOWN, and have fini() do cleanup of threads. Because there is no proper
    documentation about how PARENT_DOWN/fini are supposed to be used,
    we are getting different kinds of sequences in different higher level protocols.
    So for now cleaning up in both PARENT_DOWN and fini(). Fuse doesn't call fini()
    gfapi is not calling PARENT_DOWN in some cases, so for now I don't see
    another way out.
    
    BUG: 1396793
    Change-Id: I9c9154e7d57198dbaff0f30d3ffc25f6d8088aec
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15888
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3e405b546e8b9fe15ae477613474e9cd2d2df4e7
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Nov 8 14:10:49 2016 +0530

    cluster/dht Set layout after mkdir as root
    
    DHT does not set the layout for newly created
    directories as root. This causes EPERM failures
    when a non-root user with insufficient permissions
    creates directories.
    
    credit: srangana@redhat.com for RCA
    
    Change-Id: Ia646e41665ce172c43c5f01d2707455e8eb374ed
    BUG: 1392772
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15794
    Reviewed-by: Susant Palai <spalai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit f7ab6c45963fa0da68acedfb14281cd2456abc68
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Oct 28 15:27:15 2016 +0530

    afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event SOME_DESCENDENT_DOWN/UP
    
    Currently these are few events related to child_up/down:
    GF_EVENT_CHILD_UP :  Issued when any of the protocol client
    connects.
    GF_EVENT_CHILD_MODIFIED : Issued by afr/dht/ec
    GF_EVENT_CHILD_DOWN : Issued when any of the protocol client
    disconnects.
    These events get modified at the dht/afr/ec layers. Here is a
    brief on the same.
    
    DHT:
    - All the subvolumes reported once, and atleast one child came
      up, then GF_EVENT_CHILD_UP is issued
    - connect GF_EVENT_CHILD_UP is issued
    - disconnect GF_EVENT_CHILD_MODIFIED is issued
    - All the subvolumes disconnected, GF_EVENT_CHILD_DOWN is issued
    
    AFR:
    - First subvolume came up, then GF_EVENT_CHILD_UP is issued
    - Subsequent subvolumes coming up, results in GF_EVENT_CHILD_MODIFIED
    - Any of the subvolumes go down, then GF_EVENT_SOME_CHILD_DOWN is issued
    - Last up subvolume goes down, then GF_EVENT_CHILD_DOWN is issued
    
    Until the patch [1] introduced GF_EVENT_SOME_CHILD_UP,
    GF_EVENT_CHILD_MODIFIED was issued by afr/dht when any of the subvolumes
    go up or down.
    
    Now with md-cache changes, there is a necessity to differentiate between
    child up and down. Hence, introducing GF_EVENT_SOME_DESCENDENT_DOWN/UP and
    getting rid of GF_EVENT_CHILD_MODIFIED.
    
    [1] http://review.gluster.org/12573
    
    Change-Id: I704140b6598f7ec705493251d2dbc4191c965a58
    BUG: 1396038
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15764
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 6b2c40d337bd30eea3ce56a71db8864e61a9a411
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Nov 18 13:13:21 2016 +0530

    snapshot/scheduler: Removing dependency of scheduler on eventing
    
    Change-Id: I7de156d8186c32092ec5e9d174d023f4782947c0
    BUG: 1396364
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/15876
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 5310be8838f8db748a698bd3a98f8d00a4114e65
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Oct 18 15:16:17 2016 +0530

    events: Add FMT_WARN for gf_event
    
    Raghavendra G found that posix is trying to print %s
    but passing an int when HEALTH_CHECK fails in posix.
    These are the kind of bugs that should be caught
    at compilation itself.
    Also fixed the problematic gf_event() callers.
    
    BUG: 1386097
    Change-Id: Id7bd6d9a9690237cec3ca1aefa2aac085e8a1270
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15671
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2f70f47979d204d5ee29811f5f5fa61d0a52c3b1
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Oct 28 17:37:39 2016 +0530

    ganesha/scripts : use export id for dbus signals
    
    Currently for add export and update export parameter passed for executing those signal
    is "PATH". This is based on assumption that volume name and PATH will always be same.
    But it is wrong for subdir exports. The only reliable parameter in export configuration
    file is "Export_Id".
    
    Change-Id: Ic63ff44ac7736e14502034b74beaae27292eddf9
    BUG: 1389746
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15751
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 398cc2ce8b09dbff90aadfd483cadee9c90ec527
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 17 13:11:16 2016 +0530

    cli: Print to screen frequently
    
    Problem:
    CLI appears to be hung because XML document is not flushed periodically
    
    Fix:
    Flush the buffer as soon as we print something
    
    BUG: 1395993
    Change-Id: Ic5f61d4c7d29ee162a124a049e60ceb810d6da6d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15863
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 592fd52d5889cf8a46727b3609cdff60e9ef5c00
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Oct 27 22:53:43 2016 +0530

    tools/glusterfind: xml parsing fix for tiered volumes
    
    gluster volume info <vol> --xml for non-tiered volumes have
    'bricks/brick' elements under the 'volInfo/volumes/volume' element.
    However, tiered volumes have a 'bricks/hotBricks/brick' and
    'bricks/coldBricks/brick' elements under the 'volInfo/volumes/volume'
    element.
    
    Fix main.py::get_nodes()
    
    BUG: 1389481
    Change-Id: I2f4465bfa8a55e7fa87917d3ec3e69b05d5241b9
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15746
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit b7ebffbda9ba784ccfae6d1a90766d5310cdaa15
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Oct 26 15:51:17 2016 +0530

    eventsapi: Auto reload Webhooks data when modified
    
    glustereventsd depends on reload signal to reload the
    Webhooks configurations. But if reload signal missed, no
    events will be sent to newly added Webhook.
    
    Added auto reload based on webhooks file mtime. Before pushing
    events to Webhooks, reloads webhooks configurations if previously
    recorded mtime is different than current mtime.
    
    BUG: 1388862
    Change-Id: I83a41d6a52d8fa1d70e88294298f4a5c396d4158
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15731
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 46e5466850311ee69e6ae9a11c2bba2aabadd5de
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Nov 11 12:08:57 2016 +0530

    marker: Fix inode value in loc, in setxattr fop
    
    On recieving a rename fop, marker_rename() stores the,
    oldloc and newloc in its 'local' struct, once the rename
    is done, the xtime marker(last updated time) is set on
    the file, but sending a setxattr fop. When upcall
    receives the setxattr fop, the loc->inode is NULL and
    it crashes. The loc->inode can be NULL only in one valid
    case, i.e. in rename case where the inode of new loc
    can be NULL. Hence, marker should have filled the inode
    of the new_loc before issuing a setxattr.
    
    Change-Id: Id638f678c3daaf4a5c29b970b58929d377ae8977
    BUG: 1394131
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15826
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 35b085ba345cafb2b0ee978a4c4475ab0dcba5a6
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Oct 28 15:21:52 2016 +0530

    cli/rebalance: remove brick status is incorrect
    
    If a remove brick operation is preceded by a fix-layout,
    running remove-brick status on a node which does not
    contain any of the bricks that were removed displays
    fix-layout status.
    
    The defrag_cmd variable was not updated in glusterd
    for the nodes not hosting removed bricks causing the
    status parsing to go wrong. This is now updated.
    Also made minor modifications to the spacing in
    the fix-layout status output.
    
    Change-Id: Ib735ce26be7434cd71b76e4c33d9b0648d0530db
    BUG: 1389697
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15749
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 35e8ecabd7db36431ea93f523095bc21078ecef8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Nov 13 16:43:36 2016 +0530

    system/posix-acl: Log reason for EACCES
    
    It is becoming increasingly difficult to debug the reason why posix-acl decides
    to fail a fop with EACCES. This patch prints a big log everytime such
    a condition occurs giving out the details that may help in finding why the fop
    is errored out.
    
    Change-Id: I2505baaafb5d77ef6c187554ff027df9b20468db
    BUG: 1394548
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15837
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 53a76d6e3bbd597a11778ce252709eaa86ac5125
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Nov 16 18:26:52 2016 +0530

    protocol/client: Fix iobref and iobuf leaks in COMPOUND fop
    
    Change-Id: I408879aa2bbd8ea176fbc0d0eba5567e5df1b2b3
    BUG: 1395687
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15860
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 83311c5bb735508274bb25cc610e929481577f9b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Nov 12 16:47:00 2016 +0530

    protocol/server: Print error-xlator name
    
    Problem:
    At the moment from which xlator the errors are stemming from is a mystery.
    
    Fix:
    With this patch we can find on the server side which xlator first gave
    the errno received by server xlator. I am not yet sure how to get this
    done for client side which has lot of copy_frame()s. May be another
    patch.
    
    Change-Id: Ie13307b965facf2a496123e81ce0bd6756f98ac9
    BUG: 1394548
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15836
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b5387f90f942bfc7cf0f7f969740f8bf1c911b80
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Nov 11 08:06:03 2016 -0500

    common-ha: nfs-grace-monitor timed out unknown error messages
    
    grace_mon_monitor() occasionally returns OCF_ERR_GENERIC, but it
    ought to return OCF_NOT_RUNNING instead.
    
    Change-Id: I3d550e33cc3d0a8dce4333ced72db19b3b2f4f2e
    BUG: 1394224
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15831
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 8a1993b32f476765f9f5c9294e7c3f2ae75198a0
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Oct 25 12:56:05 2016 +0530

    geo-rep/cli: Validate Checkpoint label
    
    Checkpoint command accepts "now" or any other Time
    in "%Y-%m-%d %H:%M:%S" format as label.
    
    Validation added with this patch for the input label. Checkpoint set
    will fail for invalid label.
    
    BUG: 1388401
    Change-Id: I23518c151ab4b294f64cae3b78baaacb3d8f7b82
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15721
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 922af37e33acb59c6f8beca40a9314593b484d1a
Author: Pranith Kumar Karampuri <pkarampu@redhat.com>
Date:   Sun Nov 13 06:53:15 2016 -0700

    Revert "rpc: Fix the race between notification and reconnection"
    
    This reverts commit a6b63e11b7758cf1bfcb67985e25ec02845f0995.
    
    Nithya and Rajesh found that the mount fails sometimes after this patch
    was merged so reverting it.
    
    BUG: 1386626
    Change-Id: I959a5b6c7da61368cf4c67c98193c6e8fdd1755d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15838
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 8313d53accaa22feb14d284fb91245be0a32e16e
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Nov 15 20:40:08 2016 +0530

    cluster/dht: Check for null inode
    
    Check for NULL inode before attempting to
    set dht inode ctx.
    
    Change-Id: I7693c18445f138221d8417df5e95b118cedb818a
    BUG: 1395261
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15847
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 8437b24de36d322d26f707890f25392a098de30e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Nov 14 11:09:31 2016 -0500

    common-ha: remove /etc/corosync/corosync.conf in teardown/cleanup
    
    In newer versions of corosync we observe that after tearing down an
    existing HA cluster, when trying to set up a new cluster, `pcs cluster
    start --all` will fail if corosync believes the nodes are already in
    the cluster based on the presence of, and the contents of
    /etc/corosync/corosync.conf
    
    So we summarily delete it. (An alternative/work-around is to use `pcs
    cluster start --force --all`)
    
    Change-Id: I225f4e35e3b605e860ec4f9537c40ed94ac68625
    BUG: 1394881
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15843
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit a35d63050ec7e745a66c1aef8e1c8eb42d7b67a1
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Nov 8 19:54:11 2016 +0530

    nfs/cli : add warning message while enabling gluster nfs
    
    Change-Id: Ice70003f7295d2d8af9877e1ecf6f3c81422b30c
    BUG: 1376693
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15805
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 7947a6dd63979c7638f60d1a0954d9f78fd7df21
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Nov 10 12:34:48 2016 +0530

    Update copyright content for glusterfs binaries
    
    Change-Id: I2d5de7ae634d55ae32977e337f366586eab449e4
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/15819
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ba7a737b1260bbafe22097bea08814035c8b655d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Sep 27 19:01:48 2016 +0530

    nfs: revalidate lookup converted to fresh lookup
    
    when an inode ctx is missing for a linked inode the revalidate
    lookups are converted to fresh.
    
    This could result in sending ESTALE when the gfid are recreated
    
    We are not able to reproduce the issue with normal setup, most part of
    RCA was done with code reading.
    
    Possible scenario in which  this bug can reproduce,
    Delete a file and recreate a new file with same name, at the same time
    from another client process try to list/or access the file.
    
    In this case the second client may throw an ESTALE error for such files
    
    Thanks to Soumya and Pranith for doing the complete RCA
    
    Change-Id: I73992a65844b09a169cefaaedc0dcfb129d66ea1
    BUG: 1379720
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/15580
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 7874ed245bcc80658547992205f8396f4dd3c76a
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Oct 26 16:31:58 2016 +0530

    glusterfsd: Continuous errors are getting in mount logs while glusterd is down
    
    Problem: when glusterd is down, getting the continuous mgmt_rpc_notify errors
             messages in the volume mount log for every 3 seconds,it will
             consume disk space.
    
    Solution: To reduce the frequency of error messages use GF_LOG_OCCASIONALLY.
    
    BUG: 1388877
    Change-Id: I6cf24c6ddd9ab380afd058bc0ecd556d664332b1
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15732
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 28393888c59873efe912c4634f20f6bce3373588
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Nov 9 13:07:25 2016 +0530

    performance/open-behind: Avoid deadlock in statedump
    
    Problem:
    open-behind is taking fd->lock then inode->lock where as statedump is taking
    inode->lock then fd->lock, so it is leading to deadlock
    
    In open-behind, following code exists:
    void
    ob_fd_free (ob_fd_t *ob_fd)
    {
            loc_wipe (&ob_fd->loc); <<--- this takes (inode->lock)
    .......
    }
    
    int
    ob_wake_cbk (call_frame_t *frame, void *cookie, xlator_t *this,
                 int op_ret, int op_errno, fd_t *fd_ret, dict_t *xdata)
    {
    	.......
            LOCK (&fd->lock); <<---- fd->lock
            {
    	.......
                    __fd_ctx_del (fd, this, NULL);
                    ob_fd_free (ob_fd); <<<---------------
            }
            UNLOCK (&fd->lock);
    .......
    }
    =================================================================
    In statedump this code exists:
    inode_dump (inode_t *inode, char *prefix)
    {
    .......
    	ret = TRY_LOCK(&inode->lock); <<---- inode->lock
    .......
    	fd_ctx_dump (fd, prefix); <<<-----
    .......
    }
    fd_ctx_dump (fd_t *fd, char *prefix)
    {
    .......
            LOCK (&fd->lock); <<<------------------ this takes fd-lock
            {
    .......
    }
    
    Fix:
    Make sure open-behind doesn't call ob_fd_free() inside fd->lock
    
    BUG: 1393259
    Change-Id: I4abdcfc5216270fa1e2b43f7b73445f49e6d6e6e
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15808
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit f2e6cf9d9c578c58cdd348ebcd14dcbfdfbafadd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Nov 8 17:24:41 2016 +0530

    cluster/afr: When failing fop due to lack of quorum, also log error string
    
    Change-Id: I39de2bcfc660f23a4229a885a0e0420ca949ffc9
    BUG: 1392865
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15800
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 68d1480e6056d1be91cde5129a6809642eeee857
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Nov 4 15:56:42 2016 +0530

    upcall: Fix a log level
    
    In upcall_cache_invalidation(), the gfid can be NULL in certain
    valid test cases(eg: entry for ".." in readdirp), hence change
    the log level from WARNING to DEBUG.
    
    Change-Id: Ic90167a0e2076694e9131913114460df7b939b30
    BUG: 1392167
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15777
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3e50e09723e024cd451c5f48a153fef0fe4857c7
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jun 23 12:15:22 2016 +0530

    jbr: Sending rollback from failed fop to fdl
    
    In case of a failed fop, the failure is detected
    by the leader in the jbr-server in two places. First
    during a quorum check of +ve responses when it
    receives responses from all the followers. At this
    point if the fop hasn't been successfully journaled
    at a quorum of followers (as in there is no merit in
    trying the fop in the leader as the quorum will never
    be met), then we fail the fop.
    
    Also if this quorum is met, then the fop is tried on
    the leader, and after the leader completes the fop
    a quorum check similar to the previous one is done
    again, this time including the leaders outcome. If
    quorum is not met, then we fail the fop.
    
    In both these cases, when the fop fails we send a -ve
    ack to the client. With this patch, now we will also
    send a rollback through a GF_FOP_IPC to all the followers(and
    also to the leader in the second case of failure). This
    rollback will contain the index and term number of the
    fop which failed. This will be recorded in the respective
    journals of the bricks and will be used to rollback the
    fop on that brick later.
    
    A subsequent write, and it's respective rollback would
    look something like the following in the journal.
    
    The trusted.jbr.term and trusted.jbr.index present in the
    dict of both the logs, relate them, and the presence of
    "rollback-fop" in the dict of IPC indicates that it is a
    rollback fop, and the value 13(stands for GF_FOP_WRITE)
    indicates what kind of rollback operation it is.
    
    === GF_FOP_WRITE
    fd = <gfid 77f12ea2-ca56-40e3-a46e-ba2308baa035>
    vector = <158 bytes>
    offset = 0 (0x0)
    flags = 32769 (0x8001)
    xdata = dict {
     trusted.jbr.term = 0 <2 bytes>
     trusted.jbr.index = 4 <2 bytes>
    }
    === GF_FOP_IPC
    xdata = dict {
     trusted.jbr.term = 0 <2 bytes>
     trusted.jbr.index = 4 <2 bytes>
     rollback-fop = 13 <3 bytes>
    }
    
    Change-Id: I70b6a143d20697153d58e2f719e34ecd1ed160a5
    BUG: 1349385
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14783
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 3e980c5eff495725e7c01793451bc81fd6f94ad5
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Tue Nov 8 15:08:37 2016 +0530

    build: Update version check for resource-agents on RHEL
    
    With bug1302545[1] and bug1303037[2], portblock resource agent
    is made available as part of resource-agents-3.9.5* package
    on RHEL 6.8 and RHEL 7.3 respectively. This change is to
    update the same in the glusterfs spec.
    
    [1] https://bugzilla.redhat.com/show_bug.cgi?id=1302545
    [2] https://bugzilla.redhat.com/show_bug.cgi?id=1303037
    
    Change-Id: I5917e5f22f07b4121d636b099dd8815847e1338f
    BUG: 1389293
    Author:    Kaleb KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/15803
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e9023083b3a165390a8cc8fc77253f354744e81a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Nov 7 16:06:56 2016 +0530

    features/shard: Fill loc.pargfid too for named lookups on individual shards
    
    On a sharded volume when a brick is replaced while IO is going on, named
    lookup on individual shards as part of read/write was failing with
    ENOENT on the replaced brick, and as a result AFR initiated name heal in
    lookup callback. But since pargfid was empty (which is what this patch
    attempts to fix), the resolution of the shards by protocol/server used
    to fail and the following pattern of logs was seen:
    
    Brick-logs:
    
    [2016-11-08 07:41:49.387127] W [MSGID: 115009]
    [server-resolve.c:566:server_resolve] 0-rep-server: no resolution type
    for (null) (LOOKUP)
    [2016-11-08 07:41:49.387157] E [MSGID: 115050]
    [server-rpc-fops.c:156:server_lookup_cbk] 0-rep-server: 91833: LOOKUP(null)
    (00000000-0000-0000-0000-000000000000/16d47463-ece5-4b33-9c93-470be918c0f6.82)
    ==> (Invalid argument) [Invalid argument]
    
    Client-logs:
    [2016-11-08 07:41:27.497687] W [MSGID: 114031]
    [client-rpc-fops.c:2930:client3_3_lookup_cbk] 2-rep-client-0: remote
    operation failed. Path: (null) (00000000-0000-0000-0000-000000000000)
    [Invalid argument]
    [2016-11-08 07:41:27.497755] W [MSGID: 114031]
    [client-rpc-fops.c:2930:client3_3_lookup_cbk] 2-rep-client-1: remote
    operation failed. Path: (null) (00000000-0000-0000-0000-000000000000)
    [Invalid argument]
    [2016-11-08 07:41:27.498500] W [MSGID: 114031]
    [client-rpc-fops.c:2930:client3_3_lookup_cbk] 2-rep-client-2: remote
    operation failed. Path: (null) (00000000-0000-0000-0000-000000000000)
    [Invalid argument]
    [2016-11-08 07:41:27.499680] E [MSGID: 133010]
    
    Also, this patch makes AFR by itself choose a non-NULL pargfid even if
    its ancestors fail to initialize all pargfid placeholders.
    
    Change-Id: I5f85b303ede135baaf92e87ec8e09941f5ded6c1
    BUG: 1392445
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15788
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 4b2cff614462508eef529c5d128e0974720e3f50
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Aug 30 17:53:09 2016 +0530

    glusterd/quota: upgrade quota.conf file during an upgrade
    
    Problem
    =======
    When quota is enabled on 3.6, it will have quota conf version in quota.conf
    as v1.1. This node gets upgraded to 3.7 but it will still have quota conf
    version as v1.1 until a quota enable/disable/set limit is initiated. When
    this is not initiated and when this node tries to peer probe a node which
    is a fresh install of 3.7 (which will have quota conf version as v1.2), then this
    will result in "Peer rejected" state. This patch fixes the issue.
    
    Solution
    ========
    When an upgrade happens from 3.6 to 3.7, quota.conf file needs
    to be modified as well. With 3.6, in quota.conf the version will be
    v1.1 and it needs to be changed to v1.2 from 3.7. This is because in
    3.7, inode quota feature is introduced. So when an op-version bumpup
    happens quota.conf needs to be upgraded with quota conf version v1.2
    and all the 16 byte uuid needs to be changed to 17 bytes uuid as well.
    
    Previously, when the cluster version is upgraded to 3.7, the quota.conf
    got upgraded as well. But, the upgradation was done only when quota
    enable/disable/set limit is done. With this patch, the upgradation is done
    during a cluster op version bump up as well.
    
    Change-Id: Idb5ba29d3e1ea0e45c85d87c952c75da9e0f99f0
    BUG: 1371539
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/15352
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit e65738818dd22462ec00dda021566654d1c702b1
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Nov 2 19:51:26 2016 +0530

    gfapi: async fops should unref in callbacks
    
    If fd is unref'd at the end of async call then the unref in cbks would
    lead to double unref and possible crash. Removing duplicate unrefs.
    
    Added unref only in failure cases.
    
    A simple test case has been added to test async write case. Need to
    extend the same for other async APIs too.
    
    Details:
    All glfd based calls in libgfapi, except for glfs_open and glfs_close,
    behave in the same way. At the start of the operation, they take a ref
    on glfd and fd. At the end of the operation, they unref it. Async calls
    are a little different as they unref in the cbk function. A successfull
    open call does not unref either the glfd or fd, thereby functioning as a
    reference for a OPEN file object. glfs_close makes a syncop_flush call
    sandwiched between a fd ref and unref(this can be removed, more on this
    below), followed by a call to glfs_mark_glfd_for_deletion which unrefs
    glfd and also calls glfs_fd_destroy as a release function thereby doing
    a unref on fd too.
    
    Functionally, there is no problem with how everything works when as
    described above. However, it is a little non-intuitive that we need to
    perform a fd_unref as a consequence of a implicit fd_ref that happens
    within glfs_resolve_fd. As we perform a GF_REF_GET(glfd) at the start of
    every operation, it would be worthwhile to remove the fd_ref that
    glfs_resovle_fd takes and do away with explicit fd_unref()s at the end
    of every operation. This is the same reason why we don't need the fd_ref
    in glfs_close. This is however not in the scope of this patch.
    
    Change-Id: I86b1d3b2ad846b16ea527d541dc82b5e90b0ba85
    BUG: 1391086
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/15768
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit de7fe24663713fff364cfc2b52b675e3e979ee68
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Thu Nov 3 14:21:28 2016 +0530

    posix-acl: check dictionary before using it
    
    If extended attributes are not present in md-cache it returns NULL as xattr.
    posix acl xlator should check for NULL before using xattr.
    
    If normal and default ACLs are not set on file then md-cache will not contain
    system.posix_acl_access and system.posix_acl_default extended attributes in
    its cache.
    
    Therefore posix_acl_lookup_cbk should check xattr before using it, otherwise
    the logs will get filled with dictionary errors.
    
    Change-Id: Icebf73cf0b313bd3e82ca8cbda63786dd0fa47da
    BUG: 1391387
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15769
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5b453380b15f34c0841f453a02fdabc46ad2f7ef
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Nov 1 20:32:17 2016 +0530

    gfapi/upcall: Fix mismatch in few upcall API SYMVER
    
    There is mismatch in few of the upcall API routine
    definitions and their corresponding symbol version
    declarations. Fixed the same.
    
    Change-Id: I2edfd9546a4c6a9128757f3b68e3ae4edd2c7a79
    BUG: 1344714
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/15760
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit cd9be49f6fe05d424989c0686a7e55a3f3ead27e
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Oct 21 00:08:26 2016 +0530

    xlators/trash : Remove upper limit for trash max file size
    
    Currently file which size exceeds more than 1GB never moved to
    trash directory. This is due to the hard coded check using
    GF_ALLOWED_MAX_FILE_SIZE.
    
    Change-Id: I2ed707bfe1c3114818896bb27a9856b9a164be92
    BUG: 1386766
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15689
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9a2b3fb8b9ff28edafa012dacc5f5f0e4ee1afab
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Oct 20 12:58:16 2016 +0530

    snapshot: Fix the failure to recreate clones with same name
    
    The brick path of snapshot clones contained the clonename,
    thereby failing to create newer clones with the same name
    after the original clone had been deleted.
    
    This fix creates the brick path with the clone's vol id
    instead of the clones name. Hence future clones with the
    same name will not have the namespace clash.
    
    Change-Id: I262712adc576122f051b5d1ce171d020efaefd1a
    BUG: 1387160
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/15683
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 9340b3c7a6c8556d6f1d4046de0dbd1946a64963
Author: Ryan Ding <ryan.ding@open-fs.com>
Date:   Thu Sep 1 15:40:35 2016 +0800

    performance/write-behind: fix flush stuck by former failed writes
    
    the issue is happened in this case:
    assume a file is opened with fd1 and fd2.
    1. some WRITE opto fd1 got error, they were add back to 'todo' queue
       because of those error.
    2. fd2 closed, a FLUSH op is send to write-behind.
    3. FLUSH can not be unwind because it's not a legal waiter for those
       failed write(as func __wb_request_waiting_on() say). and those failed
       WRITE also can not be ended if fd1 is not closed. fd2 stuck in close
       syscall.
    
    to resolve this issue, we can change the way we determine 2 requests is
    'conflict': flush/fsync is not conflict with those write that is not
    belonged to them. so __wb_pick_winds() can wind the FLUSH op.
    
    below is some information when the stuck issue happen:
    glusterdump logs:
    [xlator.performance.write-behind.wb_inode]
    path=/ltp-F9eG0ZSOME/rw-buffered-16436
    inode=0x7fdbe8039b9c
    window_conf=1048576
    window_current=249856
    transit-size=0
    dontsync=0
    
    [.WRITE]
    request-ptr=0x7fdbe8020200
    refcount=1
    wound=no
    generation-number=4
    req->op_ret=-1
    req->op_errno=116
    sync-attempts=3
    sync-in-progress=no
    size=131072
    offset=1220608
    lied=-1
    append=0
    fulfilled=0
    go=0
    
    [.WRITE]
    request-ptr=0x7fdbe8068c30
    refcount=1
    wound=no
    generation-number=5
    req->op_ret=-1
    req->op_errno=116
    sync-attempts=2
    sync-in-progress=no
    size=118784
    offset=1351680
    lied=-1
    append=0
    fulfilled=0
    go=0
    
    [.FLUSH]
    request-ptr=0x7fdbe8021cd0
    refcount=1
    wound=no
    generation-number=6
    req->op_ret=0
    req->op_errno=0
    sync-attempts=0
    
    gdb detail about above 3 requests:
    (gdb) print *((wb_request_t *)0x7fdbe8021cd0)
    $2 = {all = {next = 0x7fdbe803a608, prev = 0x7fdbe8068c30}, todo = {next
    = 0x7fdbe803a618, prev = 0x7fdbe8068c40}, lie = {next = 0x7fdbe8021cf0,
        prev = 0x7fdbe8021cf0}, winds = {next = 0x7fdbe8021d00, prev =
    0x7fdbe8021d00}, unwinds = {next = 0x7fdbe8021d10, prev =
    0x7fdbe8021d10}, wip = {
        next = 0x7fdbe8021d20, prev = 0x7fdbe8021d20}, stub =
    0x7fdbe80224dc, write_size = 0, orig_size = 0, total_size = 0, op_ret =
    0, op_errno = 0,
      refcount = 1, wb_inode = 0x7fdbe803a5f0, fop = GF_FOP_FLUSH, lk_owner
    = {len = 8, data = "W\322T\f\271\367y$", '\000' <repeats 1015 times>},
      iobref = 0x0, gen = 6, fd = 0x7fdbe800f0dc, wind_count = 0, ordering =
    {size = 0, off = 0, append = 0, tempted = 0, lied = 0, fulfilled = 0,
        go = 0}}
    (gdb) print *((wb_request_t *)0x7fdbe8020200)
    $3 = {all = {next = 0x7fdbe8068c30, prev = 0x7fdbe803a608}, todo = {next
    = 0x7fdbe8068c40, prev = 0x7fdbe803a618}, lie = {next = 0x7fdbe8068c50,
        prev = 0x7fdbe803a628}, winds = {next = 0x7fdbe8020230, prev =
    0x7fdbe8020230}, unwinds = {next = 0x7fdbe8020240, prev =
    0x7fdbe8020240}, wip = {
        next = 0x7fdbe8020250, prev = 0x7fdbe8020250}, stub =
    0x7fdbe8062c3c, write_size = 131072, orig_size = 4096, total_size = 0,
    op_ret = -1,
      op_errno = 116, refcount = 1, wb_inode = 0x7fdbe803a5f0, fop =
    GF_FOP_WRITE, lk_owner = {len = 8, data = '\000' <repeats 1023 times>},
      iobref = 0x7fdbe80311a0, gen = 4, fd = 0x7fdbe805c89c, wind_count = 3,
    ordering = {size = 131072, off = 1220608, append = 0, tempted = -1,
        lied = -1, fulfilled = 0, go = 0}}
    (gdb) print *((wb_request_t *)0x7fdbe8068c30)
    $4 = {all = {next = 0x7fdbe8021cd0, prev = 0x7fdbe8020200}, todo = {next
    = 0x7fdbe8021ce0, prev = 0x7fdbe8020210}, lie = {next = 0x7fdbe803a628,
        prev = 0x7fdbe8020220}, winds = {next = 0x7fdbe8068c60, prev =
    0x7fdbe8068c60}, unwinds = {next = 0x7fdbe8068c70, prev =
    0x7fdbe8068c70}, wip = {
        next = 0x7fdbe8068c80, prev = 0x7fdbe8068c80}, stub =
    0x7fdbe806746c, write_size = 118784, orig_size = 4096, total_size = 0,
    op_ret = -1,
      op_errno = 116, refcount = 1, wb_inode = 0x7fdbe803a5f0, fop =
    GF_FOP_WRITE, lk_owner = {len = 8, data = '\000' <repeats 1023 times>},
      iobref = 0x7fdbe8052b10, gen = 5, fd = 0x7fdbe805c89c, wind_count = 2,
    ordering = {size = 118784, off = 1351680, append = 0, tempted = -1,
        lied = -1, fulfilled = 0, go = 0}}
    
    you can see they are all on 'todo' queue, and FLUSH op fd is not the
    same WRITE op fd.
    
    Change-Id: Id687f9cd3b9f281e1a97c83f1ce981ede272b8ab
    BUG: 1372211
    Signed-off-by: Ryan Ding <ryan.ding@open-fs.com>
    Reviewed-on: http://review.gluster.org/15380
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 1e421f75e040ebfce1bb6b36f9c213630807a45c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Oct 27 08:01:44 2016 -0400

    build: incorrect Requires for portblock resource agent
    
    was:
      Requires:    /usr/lib/ocf/resource.d/portblock
    s/b:
      Requires:    /usr/lib/ocf/resource.d/heartbeat/portblock
    or:
      Requires:    resource-agents >= 3.9.6
    
    Note: RHEL6.8 and RHEL7.2 have resource-agents-3.9.5 which does
    not contain the portblock resource agent.
    
    I'm not sure what the point is actually of:
    
      Requires:    /usr/lib/ocf/resource.d/heartbeat/portblock
    
    as it will fail to install on RHEL whether you have the
    resource-agents package installed or not. Hence wrapping it
    in %if ( fedora ).
    
    Change-Id: Ia7d6a475464c7469018678c98fc710a3b3bfc553
    BUG: 1389293
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15743
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ad9957af5ce8d351bebe494ba4fa474fac972c6b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Oct 27 08:28:14 2016 -0400

    tests: fix cleanup in bug-1110262.t
    
    The test wasn't cleaning up the user/group it had created if it
    terminated abnormally.  We have a mechanism (push_trapfunc) to add
    cleanup actions in a way that ensures they'll be run when necessary, so
    I changed the test to use it.  While I was there, I fixed it to use
    kill_brick instead of "ps|grep|kill" because that will be necessary for
    it to pass with brick multiplexing anyway.
    
    Change-Id: Ia515bd2420050f922970d28c5856c55df9b5247b
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/15744
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 29587a91716e1e55bd172d63340c40249fb343c9
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Oct 25 12:44:29 2016 +0530

    glusterd/shared storage: Check for hook-script at staging
    
    Check if S32gluster_enable_shared_storage.sh is present
    at /var/lib/glusterd/hooks/1/set/post/ at staging
    before proceeding with the command. Fail the command
    with the appropriate error message in case it is not
    present.
    
    Change-Id: I84e3912f1cdffb927f8a40d74d52be43ee69388b
    BUG: 1388348
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/15718
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 6ca5d6382f03685b31b12accb095093cf1486603
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Oct 6 13:13:44 2016 +0530

    md-cache: Invalidate cache entry for open() with O_TRUNC
    
    When a file is opened with O_TRUNC flag set, its size gets
    set to '0'. This case needs to be handled in md-cache to
    avoid sending incorrect cached stat.
    
    Change-Id: I95d1f8a6634734898883ede010c3e7b0b7eb97d9
    BUG: 1382266
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/15618
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b87848617b9842e7943f67596a441e4c052c3b81
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Jul 19 16:20:15 2016 +0530

    cluster/tier: break the monolith processing function
    
    Break tier_migrate_using_query_file() into a more manageable
    tier_migrate_link() and helpers.
    
    Change-Id: I5eb2d2cff9e7a2a2da567c3c4c2d53aab195f477
    BUG: 1358296
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/14957
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 3a540cc12f171393751467e2de436311bdf9be6d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 26 06:51:18 2016 +0530

    afr,ec: Heal device files with correct major, minor numbers
    
    Thanks a lot to xiaoping.wu@nokia.com from Nokia for the bug and the
    fix.
    
    BUG: 1384297
    Change-Id: Ie443237e85d34633b5dd30f85eaa2ac34e45754c
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15728
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit feea851fad4f89b48bfe89fe3b75250cc7bd6501
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Oct 17 12:16:36 2016 +0530

    tools/glusterfind: kill remote processes and separate run-time directories
    
    Problem #1:
    Hitting CTRL+C leaves stale processes on remote nodes if glusterfind pre
    has been initiated.
    
    Solution #1:
    Adding "-t -t" to ssh command-line forces pseudo-terminal to be assigned
    to remote process. When local process receives Keyboard Interrupt,
    SIGHUP is immediately conveyed to the remote terminal causing remote
    changelog.py process to terminate immediately.
    
    Problem #2:
    Concurrent glusterfind pre runs are not possible on the same glusterfind
    session in case of a runaway process.
    
    Solution #2:
    glusterfind pre runs now add random directory name to the working
    directory to store and manage temporary database and changelog
    processing.
    If KeyboardInterrupt is received, the function call
    run_cmd_nodes("cleanup", args, tmpfilename=gtmpfilename)
    cleans up the remote run specific directory.
    
    Patch:
    7571380 cli/xml: Fix wrong XML format in volume get command
    broke "gluster volume get <vol> changelog.rollover-time --xml"
    Now fixed function utils.py::get_changelog_rollover_time()
    
    Fixed spurious trailing space getting written if second path is empty in
    main.py::write_output()
    Fixed repetitive changelog processing in changelog.py::get_changes()
    
    Change-Id: Ia8d96e2cd47bf2a64416bece312e67631a1dbf29
    BUG: 1382236
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15609
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 62238f9fb3511dc854651e694bb27b9ebce1e19e
Author: hari <hgowtham@redhat.com>
Date:   Mon Oct 24 16:24:23 2016 +0530

    CLI/TIER: throw warning regarding the removal of the older commands.
    
    The older tier commands for attach tier and detach tier have to be
    removed from code. This patch sends a warning asking to use new
    command as older ones are depricated and will be removed.
    
    Change-Id: Ie1c62947bad6ff106f40331ff6134838a6c72a7a
    BUG: 1388062
    Signed-off-by: hari <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/15713
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 054c294936845b1818d6e9b66514a832904e592e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Oct 21 18:27:45 2016 +0530

    glusterd: use GF_BRICK_STOPPING as intermediate brickinfo->status state
    
    On a volume stop trigger glusterd issues a brick-op to terminate the brick
    process during brick-op phase , however in the commit-op glusterd once again
    tries to kill the same process if it exists and then mark the brickinfo->status
    flag to GF_BRICK_STOPPED. In the former case, if brick is successfully killed
    there is a possibility that GlusterD will receive RPC_CLNT_DISCONNECT from the
    said brick process before even the commit op phase is executed and hence by that
    time brickinfo->status will still be set to GF_BRICK_STARTED.
    
    BRICK_DISCONNECT event should be only sent if a brick has been killed and not
    through a volume stop/remove brick trigger, however due to this trace, this
    event is also sent out on a volume stop.
    
    Fix is to introduce an intermediate state GF_BRICK_STOPPING which can be used to
    mark the brick status at brick op phase of volume stop/remove brick to avoid
    sending spurious BRICK_DISCONNECT events on a volume stop trigger.
    
    Change-Id: Ieed4450e1c988715e0f9958be44faa6b14be81e1
    BUG: 1387652
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15699
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit f4efbf0e3092bd2181f62be1e1f30f202678c866
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Oct 24 13:54:41 2016 +0530

    cluster/dht: Incorrect volname in rebalance events
    
    The rebalance event code was using strtok to parse the
    volume name which is incorrect.
    Reworked the code to get the correct volume name using
    strstr.
    
    Change-Id: Ib5f3305a34e6bf1ecfef677d87c5aff96bdeb0e6
    BUG: 1388010
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15712
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 48a4c4e525665115f7e8c478d3bf51764427378d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Oct 18 12:52:36 2016 +0530

    snapshot: Fix for memory leaks in snapshot code path
    
    Change-Id: Idc2cb16574d166e3c0ee1f7c3a485f1acb19fc8c
    BUG: 1386088
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/15668
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit a6b63e11b7758cf1bfcb67985e25ec02845f0995
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 19 15:50:50 2016 +0530

    rpc: Fix the race between notification and reconnection
    
    Problem:
    There was a hang because unlock on an entry failed with
    ENOTCONN.
    Client thinks the connection is down where as server thinks
    the connection is up.
    
    This is the race we are seeing:
    1) Connection from client to the brick disconnects.
    2) Saved frames unwind is called which unwinds all
       frames that were wound before disconnect.
    3) connection from client to the brick happens and
       setvolume.
    4) Disconnect notification for the connection in 1)
       comes now and calls client_rpc_notify() which
       marks the connection to be offline even when the
       connection is up.
    
    This is happening because I/O can retrigger connection
    before disconnect notification is sent to the higher
    layers in rpc.
    
    Fix:
    Notify the higher layers that a disconnect happened and then
    go ahead with reconnect logic.
    
    For the logs which point to the information above check:
    https://bugzilla.redhat.com/show_bug.cgi?id=1386626#c1
    
    Thanks to Raghavendra G for suggesting the correct fix.
    
    BUG: 1386626
    Change-Id: I3c84ba1f17010bd69049fa88ec5f0ae431f8cda9
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15681
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bca6d0ba54d12d389cfb5c2b37fb8cc12a7e044b
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Sep 28 21:38:57 2016 +0530

    protocol/client: reduce memory usage
    
    readdirp calls use a lot of memory in case
    of a large number of files. The dict->extra_free
    is not used here so free buf immediately.
    
    Change-Id: I097f5dde2df471f5834264152711110a3bdb7e9a
    BUG: 1380249
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15593
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1506c7a98d8d3b31e68d0f214ab331f28ffa9fb5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Oct 18 13:34:57 2016 +0530

    geo-rep: Upgrade conf file only if it is session config
    
    Ignore config upgrade if it is template config file present in
    /var/lib/glusterd/geo-replication/gsyncd_template.conf
    
    BUG: 1386123
    Change-Id: I2cbba3103b6801c16ff57f778a90b9a0bb2467cf
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15669
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 41dc5ee07ffba6d17459757abf13fae9f174e6b6
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Oct 17 15:13:28 2016 +0530

    compound fops: Fix file corruption issue
    
    1. Address of a local variable @args is copied into state->req
    in server3_3_compound (). But even after the function has gone out of
    scope, in server_compound_resume () this pointer is accessed and
    dereferenced. This patch fixes that.
    
    2. Compound fops, by virtue of NOT having a vector sizer (like the one
    writev has), ends up having both the header and the data (in case one of
    its member fops is WRITEV) in the same hdr_iobuf. This buffer was not
    being preserved through the lifetime of the compound fop, causing it to
    be overwritten by a parallel write fop, even when the writev associated
    with the currently executing compound fop is yet to hit the desk, thereby
    corrupting the file's data. This is fixed by associating the hdr_iobuf with
    the iobref so its memory remains valid through the lifetime of the fop.
    
    3. Also fixed a use-after-free bug in protocol/client in compound fops cbk,
    missed by Linux but caught by NetBSD.
    
    Finally, big thanks to Pranith Kumar K and Raghavendra Gowdappa for their
    help in debugging this file corruption issue.
    
    Change-Id: I6d5c04f400ecb687c9403a17a12683a96c2bf122
    BUG: 1378778
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15654
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f31b3213e2a97259faa7dcae2354d2535732068b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Oct 20 16:26:27 2016 +0530

    eventsapi: Fix sending event during volume set help
    
    Event sent when `gluster volume set help` command is run
    with Volume name as "help" and empty options list
    
    With this patch, event sent only when volume set on a real volume
    
    BUG: 1387207
    Change-Id: Ia8785d6108cb86f7d89ecf9ea552df0334b41398
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15685
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit cdc30ed8eacb6772e0dabb863ef51cef794d60dd
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Oct 20 15:05:38 2016 +0530

    geo-rep: Logging improvements
    
    - Redundant log messages removed.
    - Worker and connected slave node details added in "starting worker" log
    - Added log for Monitor state change
    - Added log for Worker status change(Initializing/Active/Passive/Faulty)
    - Added log for Crawl status Change
    - Added log for config set and reset
    - Added log for checkpoint set, reset and completion
    
    BUG: 1359612
    Change-Id: Icc7173ff3c93de4b862bdb1a61760db7eaf14271
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15684
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit ec64ce2e1684003f4e7a20d4372e414bfbddb6fb
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Oct 19 07:27:40 2016 +0530

    rpc/socket.c : Modify socket_poller code in case of ENODATA error code.
    
    Problem:  Continuous warning message(ENODATA) are coming in socket_rwv
              while SSL is enabled.
    
    Solution: To avoid the warning message update one condition in
              socket_poller loop code before break from loop in case
              of error returned by poll functions.
    
    BUG: 1386450
    Change-Id: I19b3a92d4c3ba380738379f5679c1c354f0ab9b1
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15677
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d4b993610c1ee64ab7c2f41cf457e63a3da7f521
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon May 16 15:15:49 2016 +0530

    rpc/socket: Close pipe on disconnection
    
    Encrypted connections create a pipe, which isn't closed when the
    connection disconnects. This leaks fds, and gluster eventually ends up
    in a situation with fd starvation which leads to operation failures.
    
    Change-Id: I144e1f767cec8c6fc1aa46b00cd234129d2a4adc
    BUG: 1336371
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/14356
    Tested-by: MOHIT AGRAWAL <moagrawa@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d7a5ca16911caca03cec1112d4be56a9cda2ee30
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Oct 9 21:36:40 2016 +0530

    performance/io-threads: Exit all threads on PARENT_DOWN
    
    Problem:
    When glfs_fini() is called on a volume where client.io-threads is enabled,
    fini() will free up iothread xl's private structure but there would be some
    threads that are sleeping which would wakeup after the timedwait completes
    leading to accessing already free'd memory.
    
    Fix:
    As part of parent-down, exit all sleeping threads.
    
    BUG: 1381830
    Change-Id: I0bb8d90241112c355fb22ee3fbfd7307f475b339
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15620
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 255cc64375abe2925c7da1e13e45018dad4462df
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sat Oct 22 23:50:02 2016 +0530

    bitrot/cli: Add ondemand scrub event
    
    Following Bitrot Events are added
    
    BITROT_SCRUB_ONDEMAND
    {
         "nodeid": NODEID,
         "ts": TIMESTAMP,
         "event": EVENT_TYPE,
         "message": {
            "name": VOLUME_NAME,
         }
    }
    
    Change-Id: I85e668e254e6f29c447ddb4ad2ce2fc04f98bf3c
    BUG: 1387864
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/15700
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 9565222c3bb17d124e3d62ec0ab987ce45999047
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Oct 19 12:53:35 2016 +0530

    glusterd: conditionally pass uuid for EVENT_PEER_CONNECT
    
    When a new node is probed, on the first RPC_CLNT_CONNECT peerctx->uuid is set to
    NULL as the same is yet to be populated. However the subesquent (dis)connect
    events would be carrying the valid UUIDs.
    
    Solution is not to generate EVENT_PEER_CONNECT on a peer probe trigger as CLI is
    already going to take care of generating the same.
    
    Change-Id: I2f0de054ca09f12013a6afdd8ee158c0307796b9
    BUG: 1386516
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15678
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit ee4c768dafda992ab6bf3787b4efc8b0f330623e
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Oct 18 14:57:47 2016 +0530

    eventsapi/packaging: Fix wrong usage of %post
    
    %postun was used for events package instead of %post. eventsd
    service should be restarted only after install/upgrade and not
    during uninstallation(%postun)
    
    BUG: 1386141
    Change-Id: Iae3eab06d02c5f4134b3de09f040123bed053bb8
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15670
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 8f8e23b0142a21779648802664db5b3d5253e4e0
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Oct 19 23:53:12 2016 +0530

    events: add TIER_START and TIER_START_FORCE events
    
    Add TIER_START and TIER_START_FORCE events
    Conditionally generate DETACH events as per user confirmation.
    
    Change-Id: I205dc14884d707087edce42e8cf4208bd89d31dc
    BUG: 1386247
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15675
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit d73ca4a5bfad1e46dfc4a3a12401d8720b05c298
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Sep 30 12:55:40 2016 +0200

    tests: gfapi/bug1291259.c should only call glfs_free() on success
    
    In case glfs_h_poll_upcall() does not return success, the 'struct
    glfs_upcall' would not have been allocated. A retry will be done and
    glfs_free() is called on the unallocated structure. In case the pointer
    does not point to NULL, glfs_free() will try to free up some random
    area.
    
    Change-Id: I38788d3bf22bbac3924f25edf45cd4a2637fa777
    BUG: 1371540
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15603
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit daea58a51b70f80ab04f115e49f8bf8790b6046a
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Thu Oct 13 17:13:54 2016 +0530

    cli, glusterd: Address issues in get-state cli output
    
    This fixes the following data points:
    1. Volume type
    2. Peer state
    3. List of other hostnames for a peer
    4. Data unit information for rebalance
    
    The following data points are removed:
    1. Mount options and filesystem types for bricks
    2. global-option-version from list of global options
    
    The following data points are added:
    1. Replica Count
    2. Tier type for bricks belonging to hot/cold tier
    
    Change-Id: I5011250e863fdc4929b203cdb345d79b2f16c6a5
    BUG: 1385839
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/15662
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 8d8eded58cd5431a7000a70337444b828cb400d8
Author: Poornima G <pgurusid@redhat.com>
Date:   Sun Sep 4 08:27:47 2016 +0530

    md-cache, afr: Reduce the window of stale read
    
    Problem:
    Consider a replica setup, where one mount writes data to a
    file and the other mount reads the file. In afr, read operations
    are not transaction based, a brick(read subvolume) is chosen as
    a part of lookup or other operations, read is always wound only
    to the read subvolume, even if there was write from a different client
    that failed on this brick. This stale read continues until there is
    a lookup or any write operation from the mount point. Currently, this
    is not a major issue, as a lookup is issued before every read and it will
    switch the read subvolume to a correct one. But with the plan of
    increasing md-cache timeout to 600s, the stale read problem will be
    more pronounced, i.e. stale read can continue for 600s(or more if cascaded
    with readdirp), as there will be no lookups.
    
    Solution:
    Afr doesn't have any built-in solution for stale read(without affecting
    the performance). The solution that came up, was to use upcall. When a file
    on any brick is marked bad for the first time, upcall sends a notification
    to all the clients that had recently accessed the file. The solution has
    2 parts:
    - Identifying when a file is marked bad, on any of the bricks,
      for the first time
    - Client side actions on recieving the notifications
    
    Identifying when a file is marked bad on any of the bricks for the first time:
    -----------------------------------------------------------------------------
    The idea is to track xattrop in upcall. xattrop currently comes with 2 afr
    xattrs - afr dirty bit and afr pending xattrs.
       Dirty xattr is set to 1 before every write, and is unset if write succeeds.
    In certain scenarios, dirty xattr can be 0 and still the file could be bad
    copy. Hence do not track dirty xattr.
       Pending xattr is set on the good copy, indicating the other bricks that have
    bad copy. It is still not as simple as, notifying when any of the pending xattrs
    change. It could lead to flood of notifcations, in case the other brick is
    completely down or consistantly failing. Hence it is important to notify only
    once, the first time a good copy is marked bad.
    
    Client side actions on recieving pending xattr change, notification:
    --------------------------------------------------------------------
    md-cache will invalidate the cache of that file, so that further lookup is
    passed down to afr and hence update the read subvolume. Invalidating only in
    md-cache is not enough, consider the folling oder of opertaions:
    - pending xattr invalidation - invalidate md-cache
    - readdirp on the bad read subvolume - fill md-cache
    - lookup (served from md-cache)
    - read - wound to the old read subvol.
    Hence, along with invalidating md-cache, it is very important to reset the
    read subvolume for that file, in afr.
    
    Design Credit: Anuradha Talur, Ravishankar N
    
    1. xattrop doesn't carry info saying post op/pre op.
    2. Pre xattrop will have 0 value for all pending xattrs,
       the cbk of pre xattrop carries the on-disk xattr value.
       Non zero indicated healing is required.
    3. Post xattrop will have non zero value for any of the
       pending xattrs, if the fop failed on any of the bricks.
    
    Change-Id: I469cbc111714c433984fe1c922be2ef113c25804
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15398
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a482645865af56b8d34a17430649c3c646f3d450
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Sep 26 17:08:31 2016 +0530

    eventsapi: Auto convert Boolean and Int attributes
    
    Before publishing in JSON format, automatically convert the
    attribute to "bool" or "int" if configured.
    
    For example, instead of sending force="1", convert to bool and
    send as force=True
    
    {
        "event": "VOLUME_START",
        "name" : "gv1",
        "force": "1"
    }
    
    Convert to,
    
    {
        "event": "VOLUME_START",
        "name" : "gv1",
        "force": true
    }
    
    BUG: 1379328
    Change-Id: Iabc51fd61abc267a7c8dcf0aeac6b3c722d89649
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15574
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 460016428cf27484c333227f534c2e2f73a37fb1
Author: Milind Changire <mchangir@redhat.com>
Date:   Sat Oct 15 10:49:19 2016 +0530

    cluster/tier: handle fast demotions
    
    Demote files on priority if hi-watermark has been breached and continue
    to demote until the watermark drops below hi-watermark.
    
    Monitor watermark more frequently.
    Trigger demotion as soon as hi-watermark is breached.
    Add cluster.tier-emergency-demote-query-limit option to limit number
    of files returned from the database query for every iteration of
    tier_migrate_using_query_file(). If watermark hasn't dropped below
    hi-watermark during the first iteration, the next iteration will be
    triggered approximately 1 second after tier_demote() returns to the
    main tiering loop.
    Update changetimerecorder xlator to handle query for emergency demote
    mode.
    
    Add tier-ctr-interface.h:
    Move tier and ctr interface specific macros and struct definition from
    libglusterfs/src/gfdb/gfdb_data_store.h to new header
    libglusterfs/src/tier-ctr-interface.h
    
    Change-Id: If56af78c6c81d37529b9b6e65ae606ba5c99a811
    BUG: 1366648
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15158
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 20d2b36f3acc2f27527b7913d2ad939848395aeb
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Oct 3 12:35:39 2016 +0530

    common-ha: Use UpdateExports dbus msg for refresh-config
    
    In nfs-ganesha 2.4, new dbs msg type "UpdateExports" support
    has been added. With this support, the exports can be re-configured
    dynamically without the need to re-export the entries.
    
    Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e
    BUG: 1382258
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/15617
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit fd045aefbd2ea8315f76e6659753ebd1d7b6d801
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Oct 18 12:19:39 2016 +0530

    build: Avoid printing python version to stdout discovered during configure
    
    Change-Id: I1e0d0dd462cd8fa6d3ce40850099e8a019d754de
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/15666
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 5ab0b43ce67d8d131242542a80b6aa6b129ed5ee
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Oct 17 11:58:30 2016 +0200

    gfapi: add glfs_free() to glfs.h
    
    Commit 4721188a154acd9a0a4c096d8d73e97f3bf1b2a9 introduces glfs_free()
    but missed adding the function to the header. The symbol is correctly
    available in the library though. Testcases do not seem to fail when a
    function is missing for the headers...
    
    The glusterfs-3.7.16 packages have been released with the missing
    declaration in the header and symbol-maps. Still, the function is
    available for applications:
    
        $ objdump -T usr/lib64/libgfapi.so.0 | grep -w glfs_free
        0000000000006aa0 g    DF .text	0000000000000035  GFAPI_3.7.16 glfs_free
    
    Change-Id: Ia707ee957f090dbfca028192fcc81a83dfdf4ae0
    BUG: 1344714
    Reported-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15653
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit bac42476a14a16089e7185c7a250dfae43be6106
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Oct 17 16:08:41 2016 +0530

    glusterd: set the brickinfo->port before spawning the bricks
    
    As of now, when glusterd spawns a brick process, post spawning, the brickinfo's
    port is set. The side effect of this is it opens up an window where the
    pmap_signin event can be initiated by the brick to glusterd and glusterd fails
    to update signed_in flag since the brickinfo port is still 0 and the comparison
    of port and brickinfo->port fails.
    
    As a solution, set the brickinfo->port post pmap_registry_alloc and if the brick
    spawn fails reset it to 0. This logic applies for rdma port too.
    
    Change-Id: I00a13d4c6d6809ebd19a972aa13e71ee5eac7e35
    BUG: 1385575
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15655
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 975c5572a8300c81e127c27e677974f49e96bd5d
Author: Ryan Ding <ryan.ding@open-fs.com>
Date:   Wed Aug 24 00:08:12 2016 +0800

    features/read-only: reten_mode is invalid to be free by mem_put()
    
    priv->reten_mode is initialised by option 'retention-mode'. and it
    reference the memory in this->options. so fini() use mem_put to free
    priv->reten_mode will cause a problem.
    there is no need to call mem_put(), so just remove it will be fine.
    
    Change-Id: Iee6f9d1d54df38cba8c9b9100e2824f4f2b18ab4
    BUG: 1369523
    Signed-off-by: Ryan Ding <ryan.ding@open-fs.com>
    Reviewed-on: http://review.gluster.org/15296
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit f5f22d0a84e77162fd5e5afd8e912cef6d8ad320
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 12 12:25:11 2016 -0400

    crypt: changes needed for openssl-1.1 (coming in Fedora 26)
    
    Fedora is poised to update openssl-1.1.0b in/for Fedora 26
    in the next day or so.
    
    But already Fedora koji scratch builds are built against
    openssl-1.1.0b because of the way scratch builds work.
    N.B. that the latest Fedora rawhide (11 October) still ships
    with openssl-1.0.2j.
    
    HMAC_CTX is now an opaque type and instances of it must be
    created and released by calling HMAC_CTX_new() and
    HMAC_CTX_free().
    
    Change-Id: I3a09751d7b0d9fc25fe18aac6527e5431e9ab19a
    BUG: 1384142
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15629
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3830b48b6a46854d6597a36b6f2089ac1e486eb5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Oct 12 23:32:39 2016 +0530

    geo-rep/eventsapi: Additional Events
    
    Added following events
    EVENT_GEOREP_ACTIVE
        {
            "nodeid": NODEID,
            "ts": TIMESTAMP,
            "event": "GEOREP_ACTIVE",
            "message": {
                "master_volume": MASTER_VOLUME_NAME,
                "slave_host": SLAVE_HOST,
                "slave_volume": SLAVE_VOLUME,
                "brick_path": BRICK_PATH
            }
        }
    
    EVENT_GEOREP_PASSIVE
        {
            "nodeid": NODEID,
            "ts": TIMESTAMP,
            "event": "GEOREP_PASSIVE",
            "message": {
                "master_volume": MASTER_VOLUME_NAME,
                "slave_host": SLAVE_HOST,
                "slave_volume": SLAVE_VOLUME,
                "brick_path": BRICK_PATH
            }
        }
    EVENT_GEOREP_CHECKPOINT_COMPLETED
        {
            "nodeid": NODEID,
            "ts": TIMESTAMP,
            "event": "GEOREP_ACTIVE",
            "message": {
                "master_volume": MASTER_VOLUME_NAME,
                "slave_host": SLAVE_HOST,
                "slave_volume": SLAVE_VOLUME,
                "brick_path": BRICK_PATH,
                "checkpoint_time": CHECKPOINT_TIME,
                "checkpoint_completion_time": CHECKPOINT_COMPLETION_TIME
            }
        }
    
    BUG: 1379330
    Change-Id: I90716175868c59dd65c8d202e73e0ede90347b6a
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15630
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Kotresh HR <khiremat@redhat.com>

commit 727f2ebc84b6a3e6db6223ed8f5584d5cbbddbf6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Oct 17 13:20:09 2016 +0200

    trivial: correct some spelling mistakes in comments and logs
    
    BUG: 1385593
    Change-Id: Icfae9e557a284182c6c22e9606fdd641528906f0
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15656
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit b5a7dd5b39845d5e58fdd257b5c2bf801c7c1c8a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Sep 23 21:06:37 2016 +0530

    storage/posix: Fix race in posix_pstat
    
    Problem:
    When one thread is in the process of creating a file/directory
    and the other thread is doing readdirp, there is a chance that
    posix_pstat, creation fops race in the following manner which
    will lead to wrong stat values to be read by parent xlators
    like posix-acl.
    
    Creation fops                           posix_pstat() as part of readdirp
    1) file is created with uid/gid 0/0     1) does stat of the path that
                                               is created just now.
    2) Does chown to set the correct
       uid/gid
    3) Sets the acl/user/internal xattrs
    4) Sets the gfid on the entry and
       completes the creation of the file/dir
                                            2) fills the gfid in the iatt
    
    If unwind of readdirp hits server xlator before creation fop, then
    posix-acl remembers uid/gid of the file to be root/root and fails
    fops like open etc on it.
    
    Fix:
    Reverse the order of filling gfid and filling lstat() values in
    posix_pstat() so that if there is gfid in iatt buffer uid/gid
    are valid.
    
    Change-Id: I46caa7f6da7abfa40a0b1d70e35b88de9c64959c
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15564
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit a8b2a981881221925bb5edfe7bb65b25ad855c04
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Sep 27 16:35:08 2016 +0530

    performance/write-behind: remove the request from liability queue in
    wb_fulfill_request
    
    Before this patch, a request is removed from liability queue only when
    ref count of request hits 0. Though, wb_fulfill_request does an unref,
    it need not be the last unref and hence the request may survive in
    liability queue till the last unref. Let,
    
    T1: the time at which wb_fulfill_request is invoked
    T2: the time at which last unref is done on request
    
    Let's consider a case of T2 > T1. In the time window between T1 and
    T2, any other request (waiter) conflicting with request in liability
    queue (blocker - basically a write which has been lied) is blocked
    from winding. If T2 happens to be when wb_do_unwinds is invoked, no
    further processing of request list happens and "waiter" would get
    blocked forever. An example imaginary sequence of events is given
    below:
    
    1. A write request w1 is picked up for unwinding in __wb_pick_unwinds
       (but unwind is not done _yet_ and hence reference
       remains). However, w1 is moved to liability queue. Let's call this
       invocation of wb_process_queue by wb_writev as PQ1.
    
    2. A flush (f1) request hits write behind. Since the liability queue
       of inode is not empty, f1 is not picked for unwinding. Let's call
       the invocation of wb_process_queue by wb_flush as PQ2.
    
    3. PQ2 continues and picks w1 for fulfilling and invokes
       wb_fulfill. As part of successful wb_fulfill_cbk,
       wb_fulfill_request (w1) is invoked. But, w1 is not freed (and hence
       not removed from liability queue) as w1 is not unwound _yet_ and a
       ref remains (PQ1 has not invoked wb_do_unwinds _yet_).
    
    4. wb_fulfill_cbk (triggered by PQ2) invokes a wb_process_queue (let's
       say PQ3). f1 is not resumed in PQ3 as w1 is still in liability
       queue. At this time, PQ2 and PQ3 are complete.
    
    5. PQ1 continues, unwinds w1 and does last unref on w1 and w1 is freed
       (and removed from liability queue). Since PQ1 didn't invoke
       wb_fulfill on any other write requests, there won't be any future
       codepaths that would invoke wb_process_queue and f1 is stuck
       forever.
    
    With this fix, w1 is removed from liability queue in step 3 above and
    PQ3 resumes f1 in step 4 (as there are no requests conflicting with f1
    in liability queue during execution of PQ3).
    
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1379655
    Change-Id: Idacda1fcd520ac27f30224f8dfe8360dba6ac6cb
    Reviewed-on: http://review.gluster.org/15579
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 91c353001c0acf6b6a4c08181fa9a582ae3f880b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Sep 24 13:18:24 2016 +0530

    glusterd: enable default configurations post upgrade to >= 3.9.0 versions
    
    With 3.8.0 onwards volume options like nfs.disable, transport.address-family
    have some default configuration value. If a volume was created pre upgrade to
    3.8.0 or higher the default options are not set post upgrade. This patch takes
    care of putting the default values in the op-version bump up workflow. However
    these changes will only reflect from 3.9.0 onwards
    
    Change-Id: I9a8d848cd08d87ddcb80dbeac27eaae097d9cbeb
    BUG: 1379223
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15568
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit fbc7d462f85236d416ee4354f2b2d8c55fd40df1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Sep 30 17:16:43 2016 +0530

    cluster/afr: Prevent dict_set() on NULL dict
    
    In afr lookup when NULL dict is received in lookup, afr
    is supposed to set all the xattrs it requires in a new dict
    it creates, but for 'link-count' it is trying to set to the
    dict that is passed in lookup which can be NULL sometimes.
    This is leading to error logs. Fixed the same in this patch.
    
    BUG: 1385104
    Change-Id: I679af89cfc410cbc35557ae0691763a05eb5ed0e
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15646
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 3a97486d7f9d0db51abcb13dcd3bc9db935e3a60
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Oct 14 16:09:08 2016 +0530

    afr: Take full locks in arbiter only for data transactions
    
    Problem:
    Sharding exposed a bug in arbiter config. where `dd` throughput was
    extremely slow. Shard xlator was sending a fxattrop to update the file
    size immediately after a writev. Arbiter was incorrectly over-riding the
    LLONGMAX-1 start offset (for metadata domain locks) for this fxattrop,
    causing the inodelk to be taken on the data domain. And since the
    preceeding writev hadn't released the lock (afr does a 'lazy'
    unlock if write succeeds on all bricks), this degraded to a blocking
    lock causing extra lock/unlock calls and delays.
    
    Fix:
    Modify flock.l_len and flock.l_start to take full locks only for data
    transactions.
    
    Change-Id: I906895da2f2d16813607e6c906cb4defb21d7c3b
    BUG: 1384906
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reported-by: Max Raba <max.raba@comsysto.com>
    Reviewed-on: http://review.gluster.org/15641
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit fc3ff95041581fb0791bd083baa0dd98717e188b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Oct 13 09:58:21 2016 +0200

    gfapi: correct the gfapi.map for glfs_ipc@GFAPI_4_0_0
    
    Commit 85e959052148ec481823d55c8b91cdee36da2b43 introduced an
    inconsistency in gfapi.map. We need to figure out how to handle the
    glfs_ipc() function at one point...
    
    Change-Id: If53ad904318d5a60c14bd8b80685f7a852bf25e5
    BUG: 1370931
    Reported-by: Anoop C S <anoopcs@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15633
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 070145750006c87099f945b4990a4460d814c21f
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Oct 3 10:55:23 2016 +0530

    rpc/socket.c : Modify gf_log message in socket_poller code in case of error
    
    Problem:  In case of SSL after stopping the volume if client(mount point) is
              still trying to write the data on socket then it will throw an EIO
              error on that socket and given this log message is captured at every
              attempt this would flood the log file.
    
    Solution: To reduce the frequency of stored log message use GF_LOG_OCCASIONALLY
              instead of gf_log.
    
    BUG: 1381115
    Change-Id: I66151d153c2cbfb017b3ebc4c52162278c0f537c
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15605
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f0c588e5e6fa1552325a31e0e01704ecf063c7e1
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Oct 4 13:55:53 2016 -0400

    mgmt/glusterd: Cleanup memory leaks in handshake
    
    Thanks to bingxuan.zhang at nokia dot com for the report and patch.
    
    Change-Id: I994f82493fec7827f31592340af5bda83322f878
    BUG: 1377584
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/15612
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit b77cf4d021f26eb3fda81abec10464594324fac2
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Oct 4 14:02:12 2016 -0400

    libglusterfs/client_t: cleanup username and passwd in client_destroy()
    
    Thanks to bingxuan.zhang at nokia dot com for the report and patch.
    
    Change-Id: If2b2151ab4df27d769126860d98770c80bc8a534
    BUG: 1377584
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/15613
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit de07155bfae3c5846797cbb19ee044751cbe6f6e
Author: Oleksandr Natalenko <onatalen@redhat.com>
Date:   Wed Sep 28 14:29:23 2016 +0200

    glusterfsd/main: fix OOM adjustment for older kernels
    
    Milind Changire reported that GlusterFS fails to build on RHEL5
    because linux/oom.h is unavailable.
    
    Milind's initial patch disables OOM adjustment completely
    for those environments that do not have this header. However,
    I'd take another approach that:
    
    1) checks for linux/oom.h in compile-time and defines necessary
    constants if the header is not present;
    2) checks for available OOM API in /proc in run-time and uses it
    accordingly.
    
    This allows OOM to be adjusted properly on RHEL5 (the kernel is pretty new
    to present /proc API for that) as well as RHEL6 (the kernel has many thing
    backported including new /proc API).
    
    Change-Id: I1bc610586872d208430575c149a7d0c54bd82370
    BUG: 1379769
    Signed-off-by: Oleksandr Natalenko <onatalen@redhat.com>
    Reviewed-on: http://review.gluster.org/15587
    Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 0fed7e7f0aad9973900c89434f736797d9ace2bd
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Sep 20 12:32:28 2016 +0530

    cluster/ec: Implement heal info with lock
    
    Problem: Currently heal info command prints all
    the files/directories if the index for the
    file/directory is present in .glusterfs/indices folder.
    After implementing patch http://review.gluster.org/#/c/13733/
    indices of the file which is going through update fop
    will also be present in .glusterfs/indices even
    if the fop is successful on all the brick. At this time
    if heal info command is being used, it will also display this
    file which is actually healthy and does not require any heal.
    
    Solution: Take lock on a file corresponding to the indices
    and inspect xattrs to decide if the file needs heal or not.
    
    Change-Id: I6361e2813ece369be12d02e74816df4eddb81cfa
    BUG: 1366815
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/15543
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 85e959052148ec481823d55c8b91cdee36da2b43
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Sep 13 09:03:56 2016 +0200

    gfapi: warn when glfs_realpath() returned malloc'd memory
    
    glfs_realpath() may return memory allocated with malloc(). Depending on
    the memory allocator that the application uses, calling free() on the
    returned string can cause segmentation faults or other problems.
    
    Functions that allocate memory, need to match the free'ing of the same
    memory allocator and memory accounting. glibc/malloc and jemalloc/free
    do not match together (other allocators could probably trigger these
    problems as well).
    
    Applications need to provide a pre-allocated buffer, or in case
    glfs_realpath() allocates the memory, glfs_free() should be used to free
    it.
    
    Change-Id: I5d721a7425674aa700db8a7a436cbedb95a5927f
    BUG: 1370931
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15332
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2e23c62cc50037c8e61bcd9c04348409e7627181
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Thu Sep 29 13:35:26 2016 +0530

    socket: log the client identifier in ssl connect
    
    Problem: client identifier is not logged in message in ssl_setup_connection
    
    Solutuion: In ssl_setup_connection xl_private is not available in rpc_transport
               so changed to this peerinfo.identifier.
    
    BUG: 1380275
    Change-Id: I05006a3d63e46de8c388298c22faa9a3329eb6f3
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15596
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1bbbf35cb91e5132b8c46dff0681d24371295a4
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Oct 4 10:10:56 2016 +0530

    afr: fix incorrect debug log in selfheal path
    
    1. While looking at glustershd logs in DEBUG log-level, it was found that
    all bricks of the replica were printed as local bricks even though they
    were not. Fixed it.
    
    2. Print the name of the subvol from which the entry was got during
    index crawl.
    
    Change-Id: I08b32e38694c755715e9fe0c0e1dd9212abcfb16
    BUG: 1381421
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15610
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9ab5b52dee5be45458fdb5446d3cbf6a1a5306a6
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Aug 22 12:30:43 2016 +0530

    afr: Implement IPC fop
    
    Currently ipc() is not implemented in afr. md-cache and upcall
    uses ipc to register the list of xattrs, [1] for more details.
    For the ipc op GF_IPC_TARGET_UPCALL, it has to be wound to all
    the replica subvolumes. ipc() is failed when any of the
    subvolumes fails with other than ENOTCONN or all of the subvolumes
    are down.
    
    [1] http://review.gluster.org/#/c/15002/
    
    Change-Id: I0f651330eafda64e4d922043fe53bd0014536247
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15378
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 567dee257e092401cdf0a62d4b89e13c39a0a5aa
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Sep 21 17:43:00 2016 +0530

    eventsapi/geo-rep: Geo-rep will not work without eventsapi rpms
    
    If glusterfs-events rpm is not installed, Geo-replication will
    fail since it imports eventtypes.
    
    Any call to gsyncd will fail with Import error. Glusterd start
    fails since it runs `gsyncd.py --version`
    
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py",
        line 29, in <module>
          from syncdutils import FreeObject, norm, grabpidfile, finalize
      File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py",
        line 28, in <module>
          from events import eventtypes
    ImportError: No module named events
    
    BUG: 1378057
    Change-Id: I1a9bc086c3d52449ec7296cb2f9ceb16cd41a8a4
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15539
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 4721188a154acd9a0a4c096d8d73e97f3bf1b2a9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Aug 6 16:04:48 2016 +0200

    gfapi: redesign the public interface for upcall consumers
    
    The glfs_callback_arg and glfs_callback_inode_arg were allocated by
    gfapi, and expected to be free()'d by the application. However it is not
    reasonable to expect that applications use the same memory allocator to
    as the compiled libgfapi.so. For instance, it is possible that gfapi
    uses glibc malloc/free, and an application like NFS-Ganesha the versions
    from jemalloc. Mismatching of the malloc() and free() functions causes
    segmentation faults at best.
    
    In order to prevent problems like this in the future, the API for
    applications that consume upcalls has been remodeled. Any of the
    structures that gfapi allocates, should be free'd with glfs_free(). The
    members of the structures can not be accessed directly anymore, each
    has its own function to access now.
    
    Correcting the naming of the functions, structures and constants is a
    continuation of commit 2775dc64101ed37c8d9809bf9852dbf0746ee2b6. These
    new improvements not only have correct prefixes for the functions and
    structures, the naming also reflects more to the upcall framework and
    does not use "callback" anymore.
    
    Change-Id: I2b8bd5a0a82036d2abea1a217f5e5975a1d4fe93
    BUG: 1344714
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14701
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 7407266684334203c21e260bb0b3527ca94bb507
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Sep 20 12:50:55 2016 +0530

    ganesha/scripts : modify start hook script for shared storage changes
    
    Change-Id: Ib8dfe41d06ae0756af8f1c110fc774ac16bdc581
    BUG: 1377607
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15535
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit cd072b61841c19ec942871e3f06519d2a938814b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 27 07:51:48 2016 +0530

    tests: Fix races in open-behind.t
    
    Problems:
    1) flush-behind is on by default, so just because write completes doesn't mean
       it will be on the disk, it could still be in write-behind's cache. This
       leads to failure where if you write from one mount and expect it to be there
       on the other mount, sometimes it won't be there.
    2) Sometimes the graph switch is not completing by the time we issue read which
       is leading to opens not being sent on brick leading to failures.
    
    Fixes:
    1) Disable flush-behind
    2) Add new functions to check the new graph is there and connected to bricks
       before 'cat' is executed.
    
    BUG: 1379511
    Change-Id: I0faed684e0dc70cfd2258ce6fdaed655ee915ae6
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15575
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit d27cffab670858d7812bbb458a0833303d009b3b
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Sep 26 14:54:27 2016 +0530

    gfapi: Fix few fd ref leaks
    
    From the code inspection, have observed that there are fd ref
    leaks for few fd-based gfapi fops. 'glfs_resolve_fd' returns
    a fd (either existing or migrated) with an extra ref taken.
    This needs to be unref'ed at the end of the operation.
    
    Change-Id: Id63394e3e7deafb0c8b06444f2ae847248b126db
    BUG: 1379285
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/15573
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 4004e667edc88ac9a8c1e9048da0919ec38be4c2
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Sep 16 13:05:59 2016 +0530

    glusterd: Revert 368e26f454fe35477e46dc698fa6b8c3c608ea8d
    
    The earlier fix prevented rebalance from
    starting even if only a single brick of a
    replica set was down.
    
    Change-Id: I8c9a7d4c1fe33f7749568357462f29796e1b832a
    BUG: 1376671
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15517
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 7a80b6128ad91c1174a79b4fa6a0340dfd0b6d6b
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Sep 13 18:27:45 2016 +0530

    glusterd: "gluster v heal test statistics heal-count replica" output is not correct
    
    Problem :  "gluster v heal test statistcs heal-count replica" does not
                show correct output.
    
    Solution: After update condition (match brick name) in
              _select_hxlator_with_matching_brick, it shows correct output.
    
    BUG: 1325792
    Change-Id: I60cc7c68ea70bce267a747570f91dcddbc1d9016
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15494
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 5afc6aba906a21aee19c2f1baaa7d9eb762ae0ac
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Sep 23 10:47:03 2016 +0530

    afr: Ignore gluster internal (virtual) xattrs in metadata heal check
    
    Problem:
    In arbiter configuration, posix-xlator in the arbiter brick always sets
    the GF_CONTENT_KEY in the response dict with a value 0. If the file size on
    the data bricks is more than quick-read's max-file-size (64kb default),
    those bricks don't set the key. Because of this difference in the no. of dict
    elements, afr triggers metadata heal in lookup code path, in turn
    leading to extra lookups+inodelks.
    
    Fix:
    Changed afr dict comparison logic to ignore all virtual xattrs and the
    on-disk ones that we should not be healing.
    
    Also removed is_virtual_xattr() function. The original callers to this
    function (upcall) don't seem to need it anymore.
    
    Change-Id: I05730bdd39d8fb0b9a49a5fc9c0bb01f0d3bb308
    BUG: 1378684
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15548
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 3bf8f05a8a0eccd723a9478a5c925d099a145a1a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Sep 22 20:04:12 2016 +0530

    glusterd: fix return val in glusterd_op_volume_dict_uuid_to_hostname ()
    
    glusterd_op_volume_dict_uuid_to_hostname () ignores few dict_get_str failures
    but doesn't reset the ret value to 0.
    
    Reproducer steps:
    1. Configure a volume and start it (gNFS has to be disabled)
    2. gluster volume status
    
    An warning log is observed with:
    [MSGID: 106217] [glusterd-op-sm.c:4706:glusterd_op_modify_op_ctx] 0-management:
    Failed uuid to hostname conversion
    [2016-09-22 09:21:38.537533] W [MSGID: 106387]
    [glusterd-op-sm.c:4812:glusterd_op_modify_op_ctx] 0-management: op_ctx
    modification failed
    
    Change-Id: I1d3aa79304d83a9d5db1b7198773d8c2780e24a9
    BUG: 1378492
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15547
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 359b72a57b7c92fc2a11236ac05f5d740db2f540
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Sep 2 12:47:15 2016 +0530

    ec: Implement ipc fop
    
    The ipc will be wound to all the bricks, but for it to be
    successfull, the fop should succeed on minimum number of bricks.
    
    Change-Id: I3f8cb6a349e87bafd0773583def9d4e3765aa140
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15387
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f6a3c541941df6fd19ef57185aca5c4bcec2dec3
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Sep 23 15:16:46 2016 +0530

    afr: Modifications to afr events
    
    Modified afr event message to add a 'type' key as detailed in the BZ.
    Also added events for data and metadata split-brain.
    
    Change-Id: I8156674b4b6a501499fc10fd68e05115fdaef3e4
    BUG: 1378072
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15550
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 85f7a86730db229ce264f43d224465a76202d270
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 22 08:22:50 2016 -0400

    build: python-ctypes no longer exists in Fedora Rawhide
    
    Python packaging in Rawhide has a Virtual Provides of python-ctypes
    but that will be removed soon
    
    Change-Id: I353f7fcbff35dfbfb1a726c7608eef721976453d
    BUG: 1378436
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15546
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 3bfdcdcdfa04a12483a490fb6f766fd6689663a9
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Sep 19 03:58:15 2016 +0200

    fuse: fix fuse dumping for FUSE_WRITE
    
    Data coming with FUSE_WRITE requests are arranged
    with a special alignment, cf. 15d85ff1. fuse_dumper()
    was not aware of this and didn't dump the proper
    reqion for FUSE_WRITE.
    
    BUG: 1377427
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Change-Id: I36255ca3336e95be6e2d256c8199761ddec41869
    Reviewed-on: http://review.gluster.org/15525
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 9d7d81e8058aa89fc24bcc211cfad3618720292d
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Sep 22 10:38:21 2016 +0530

    cluster/dht: remove unnecessary struct member
    
    Removed a structure member that was not used
    from dht_local_t. Skipped some unnecessary checks
    in dht_filter_loc_subvol_key.
    
    Change-Id: I81740b6528e063fb9cf5817e05865ff4d77aa748
    BUG: 1378305
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15542
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a412a4f50d8ca2ae68dbfa93b80757889150ce99
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 20 12:05:23 2016 +0530

    performance/open-behind: Pass O_DIRECT flags for anon fd reads when required
    
    Writes are already passing the correct flags at the time of open().
    
    Also, make io-cache honor direct-io for anon-fds with
    O_DIRECT flag during reads.
    
    Change-Id: I215cb09ef1b607b9f95cabf0ef3065c00edd9e78
    BUG: 1377556
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15537
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 7090cf287847a808d6d0225bc9110f44c3248e12
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Dec 30 16:53:25 2015 +0530

    tier/ctr/sql : Dafault values for sql cache and wal size
    
    Setting default values for sql cache and wal size
    cache : 12500 pages
    wal   : 25000 pages
    1 pages - 4096 bytes
    
    Change-Id: Iae3927e021af2e3f7617d45f84e81de3b7d93f1c
    BUG: 1377864
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/15536
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>

commit c5426a13ad28fb2c6f0ed62404dbe60ea0dfaad2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Sep 19 09:13:09 2016 -0400

    build: rpc/xdr .c and .h files are regenerated unnecessarily
    
    .c and .h files are blindly (re)generated. If you run `make`
    followed by a second `make` or `make install` the subsequent
    `make` will unnecessarily recompile everything because of the
    redundant regeneration of the .c and .h files are now newer
    than the prior builds .o files
    
    Change-Id: I7e477bcdcc20869e144ada7e6d91e7221b8ee71f
    BUG: 1377341
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15530
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>

commit 12ae3c448c8435decdff27643d5785698ac19dff
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Sep 8 11:33:59 2016 +0530

    socket: pollerr event shouldn't trigger socket_connnect_finish
    
    If connect fails with any other error than EINPROGRESS we cannot get
    the error status using getsockopt (... SO_ERROR ... ). Hence we need
    to remember the state of connect and take appropriate action in the
    event_handler for the same.
    
    As an added note, a event can come where poll_err is HUP and we have
    poll_in as well (i.e some status was written to the socket), so for
    such cases we need to finish the connect, process the data and then
    the poll_err as is the case in the current code.
    
    Special thanks to Kaushal M & Raghavendra G for figuring out the issue.
    
    Change-Id: Ic45ad59ff8ab1d0a9d2cab2c924ad940b9d38528
    BUG: 1372356
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/15440
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e9b39527d5dcfba95c4c52a522c8ce1f4512ac21
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Sep 16 17:29:21 2016 +0200

    rpc: increase RPC/XID with each callback
    
    The RPC/XID for callbacks has been hardcoded to GF_UNIVERSAL_ANSWER. In
    Wireshark these RPC-calls are marked as "RPC retransmissions" because of
    the repeating RPC/XID. This is most confusing when verifying the
    callbacks that the upcall framework sends. There is no way to see the
    difference between real retransmissions and new callbacks.
    
    This change was verified by create and removal of files through
    different Gluster clients. The RPC/XID is increased on a per connection
    (or client) base. The expectations of the RPC protocol are met this way.
    
    Change-Id: I2116bec0e294df4046d168d8bcbba011284cd0b2
    BUG: 1377097
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15524
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e38dff5b4e0f0a25db664810fc3617eac44673ce
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 26 17:04:04 2016 -0400

    build: out-of-tree builds generates files in the wrong directory
    
    And minor cleanup of a few of the Makefile.am files while we're
    at it.
    
    Rewrite the make rules to do what xdrgen does. Now we can get rid
    of xdrgen.
    
    Note 1. netbsd6's sed doesn't do -i. Why are we still running
    smoke tests on netbsd6 and not netbsd7? We barely support netbsd7
    as it is.
    
    Note 2. Why is/was libgfxdr.so (.../rpc/xdr/src/...) linked with
    libglusterfs? A cut-and-paste mistake? It has no references to
    symbols in libglusterfs.
    
    Note3. "/#ifndef\|#define\|#endif/" (note the '\'s) is a _basic_
    regex that matches the same lines as the _extended_ regex
    "/#(ifndef|define|endif)/". To match the extended regex sed needs to
    be run with -r on Linux; with -E on *BSD. However NetBSD's and
    FreeBSD's sed helpfully also provide -r for compatibility. Using a
    basic regex avoids having to use a kludge in order to run sed with
    the correct option on OS X.
    
    Note 4. Not copying the bit of xdrgen that inserts copyright/license
    boilerplate. AFAIK it's silly to pretend that machine generated
    files like these can be copyrighted or need license boilerplate.
    The XDR source files have their own copyright and license; and
    their copyrights are bound to be more up to date than old
    boilerplate inserted by a script. From what I've seen of other
    Open Source projects -- e.g. gcc and its C parser files generated
    by yacc and lex -- IIRC they don't bother to add copyright/license
    boilerplate to their generated files.
    
    It appears that it's a long-standing feature of make (SysV, BSD,
    gnu) for out-of-tree builds to helpfully pretend that the source
    files it can find in the VPATH "exist" as if they are in the $cwd.
    rpcgen doesn't work well in this situation and generates files
    with "bad" #include directives.
    
    E.g. if you `rpcgen ../../../../$srcdir/rpc/xdr/src/glusterfs3-xdr.x`,
    you get an #include directive in the generated .c file like this:
    
      ...
      #include "../../../../$srcdir/rpc/xdr/src/glusterfs3-xdr.h"
      ...
    
    which (obviously) results in compile errors on out-of-tree build
    because the (generated) header file doesn't exist at that location.
    Compared to `rpcgen ./glusterfs3-xdr.x` where you get:
    
      ...
      #include "glusterfs3-xdr.h"
      ...
    
    Which is what we need. We have to resort to some Stupid Make Tricks
    like the addition of various .PHONY targets to work around the VPATH
    "help".
    
    Warning: When doing an in-tree build, -I$(top_builddir)/rpc/xdr/...
    looks exactly like -I$(top_srcdir)/rpc/xdr/...  Don't be fooled though.
    And don't delete the -I$(top_builddir)/rpc/xdr/... bits
    
    Change-Id: Iba6ab96b2d0a17c5a7e9f92233993b318858b62e
    BUG: 1330604
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14085
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 09ce988ad6d8e0576f1fc23abf71b43ac4b7514e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Sep 18 08:23:23 2016 +0200

    cli: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    Change-Id: Ib78fed1fab00ba22a90f2148a343170488fa05cf
    BUG: 1369124
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15523
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit ee1e0994994314453897d97fb28d91d50c40f40e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Sat Sep 17 12:15:27 2016 -0400

    cli/cli-rpc-ops: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I844e694c1797f9f6512f75fbe3620f527d1f5203
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15522
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e872917dbf4563703b8f396d7d30f8168ed646cd
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Sep 15 11:20:54 2016 +0530

    dht/events:  Added rebalance events
    
    The rebalance process will now send an event when it is
    complete.
    Also fixed a problem where the run-time was not always
    set causing spurious rebalance failure events to be sent.
    
    Change-Id: Ib445171c78c9560940022bca20c887d31a9bb1ca
    BUG: 1371874
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15501
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 7e18e16f9f62ed95acded0fb3f2a8784087f59c0
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Aug 30 18:36:51 2016 +0530

    ganesha/glusterd : Correct the path for ganesha conf dir in Makefile
    
    The value for ganesha conf dir in Makefile.am is mistakenly entered as
    following :
    DCONFDIR=\"/$(runstatedir)/gluster/shared_storage/nfs-ganesha\"
    
    Here value for runstatedir is seems to "NULL" which results wrong path
    for ganesha configuration directory
    
    Change-Id: I0b7ebd8e2503de0cb79b601553c4405d0d1fd711
    BUG: 1355956
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15355
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit f61222257af36aa157c97016fc40f58e6a436e5e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Sep 16 03:49:20 2016 -0400

    cluster/ec: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I24607fc2082c3424f876f740a88fb7d0173d322d
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15518
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit da2aabe3334a9169b2c64cca317f58af21c2fc35
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 15 22:53:09 2016 -0400

    libglusterfs/mem-pool: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I8885e4d4aa44307c240413ba6f35ecd59ab45444
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15516
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 660ca23dee3a0f1a7128d3777589467b27af514b
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Aug 22 16:03:13 2016 +0530

    cluster/ec: set/unset dirty flag for data/metadata update
    
    Currently, for all the update operations, metadata or data,
    we set the dirty flag at the end of the operation only if
    a brick is down. This leads to delay in healing and in some
    cases not at all.
    In this patch we set (+1) the dirty flag
    at the start of the metadata or data update operations and
    after successfull completion of the fop, we unset (-1) it again.
    
    Change-Id: Ide5668bdec7b937a61c5c840cdc79a967598e1e9
    BUG: 1316873
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13733
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit e3494a0e043f83c39b865419034bd9ab980fd3a6
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 15 12:29:53 2016 -0400

    glusterd/handler: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: Ia2742a44fcf1e16ade1f55287096dbecdb8eb9b7
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15514
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 62d254bf7931d2ed961a5e1d78eac609f671dbbe
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 15 12:27:58 2016 -0400

    xlators/afr: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I4946d460f66d3430bac8910260c0cb1b3e9ff87b
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15513
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 36748550398f5e4a0bcdc603ac70a62453e86979
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 05:57:32 2016 -0400

    protocol/client: fix op_errno handling, was unused variable
    
    see comment in patch set one. Match the general logic flow of the
    other fop-cbks and eliminate the unused variable and its associated
    warning
    
    also see comment in patch set seven, re: correct handling of
    client_process_response(); and the associated BZ
    https://bugzilla.redhat.com/show_bug.cgi?id=1376328
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I7421ba3550770acc5564b7d6aba3290e027591f2
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15482
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 957e40060734f1a0b2d9e3d37c4b0f7961f56b51
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Sep 14 20:12:42 2016 +0530

    events/dht: dht cli events
    
    Adding events for add/remove brick and rebalance
    from the cli.
    
    Change-Id: I4e07cb7224e1b63a2926db055f87a02220c5d043
    BUG: 1371874
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15500
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit a046e4d5bbd2ee756ff6fdb7aa1aca115002b133
Author: Nigel Babu <nigelb@redhat.com>
Date:   Tue Sep 13 15:54:48 2016 +0530

    tests: Kill rpc.statd on tests in Linux as well
    
    The lack of this causes the /var/messages file on Linux test nodes to be filled
    up and cause space issues.
    
    Change-Id: I4c741c34de7f584859d1c62bdfda44a3d79c7ecc
    BUG: 1375526
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: http://review.gluster.org/15485
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 613575ee7140e257d8f0265b719cbfc7c44a0297
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Sep 7 04:19:32 2016 +0530

    storage/posix: Integrate important events with gf_event
    
    BUG: 1371353
    Change-Id: I9346ca16222caf9d97d999751577399ae6aacf72
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15342
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 73c6c2c307c8bcaac51aa94b1af518955f35d1b8
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Sep 13 14:21:29 2016 +0530

    build: add systemd dependency
    
    Installs break with glusterfs getting installed before systemd
    installation. This patch adds a dependency for systemd appropriately
    for Fedora and RHEL platforms for glusterfs-server and glusterfs-events
    packages.
    
    Change-Id: Ica18f82a5e37c7755f0d386ce2ac6c70e8082815
    BUG: 1375181
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15469
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 656873c4c8f5f3b05823c51f20c2a44106662550
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Sep 13 15:38:24 2016 +0530

    eventsapi/packaging: Fix conflict during rpm install
    
    RPM installation fails with following error
    
      Error: Transaction check error:
        file /etc/glusterfs/eventsconfig.json conflicts between attempted
        installs of glusterfs-events-3.10dev-0.51.gitc9271ff.fc24.x86_64
        and glusterfs-server-3.10dev-0.51.gitc9271ff.fc24.x86_64
    
    Changed attributes of eventsconfig.json file as same as other
    config files and excluded this file in server rpm.
    
    BUG: 1375532
    Change-Id: I3708c8fc58448cd5a6ebe611250f10e0658bdd58
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15486
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 7e1ee2efa0b4f5c42a48282204f3d3977ab41fe2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 05:56:25 2016 -0400

    xlators/md-cache: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I5904956b2033993abee0a29ff615e058a52c9ac0
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15481
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 88f842024f018cae3fa39831212ef30c37dcf964
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 05:54:59 2016 -0400

    xlators/glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I7ccaa4f1cc817fa81082cee83e99a2dc7e542e17
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15479
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 9836ab799fbe82dc9b37e4857282b88898ce9517
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 05:58:10 2016 -0400

    xlators/protocol/server: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I087131cd9b5e2abffc6a67d6c61e88fb6784661a
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15483
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 0419ab2820820f1ac93e55dbf3a665824560bade
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 05:53:14 2016 -0400

    xlators/{dht,tier}: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I6feee863927254ae9f59013112bcc297ad09e89b
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15477
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit 71d3c5850d33a60115e561f88072826fd81bc1a0
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 05:55:45 2016 -0400

    xlators/decompounder: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: Ia4d11871838b749d15dd1942d0a93594e90124e0
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15480
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 50c0790bf1c1dca7b4e69546b1f6fe71785ecf2a
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 05:52:09 2016 -0400

    xlators/afr: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I55d4106ac828380f3315f5a21593390905d3ab3a
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15476
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 7982de17f47ab2f8ddc4789a525754a56b26b325
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 13 06:28:26 2016 -0400

    xlators/upcall: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a "pragma leak" where the
    generated rpc/xdr headers have a pair of pragmas that disable these
    warnings. With the warnings disabled, many unused variables have
    crept into the code base.
    
    And 14085 won't pass its own smoke test until all these warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I48c0d9bbf13ccf79975dd7b35d524f6d7428ac52
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15484
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6b30e9bf5a612e105eb7ded0a89ef25fd8530ba5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Sep 8 17:30:37 2016 +0530

    geo-rep: Defunct tar process after sync
    
    After every sync iteration with tarssh mode leaves defunct tar
    process.
    
    Added wait for tar process to prevent this issue.
    
    BUG: 1374286
    Change-Id: I9953239ef601cc1970c814b00074b45eb00f481e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15426
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit c9271ff14d3efa8279cf67907548b3f43970d4fb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Sep 8 05:43:20 2016 +0530

    system/posix-acl: Unwind with NULL xdata on error
    
    In posix-acl when there are errors xdata that comes as part of input is used to
    unwind which can be used as response xdata which may lead to problems as the
    keys in the input will match with keys in the output but the values the
    response xdata may expect can be completely different.
    
    For example, we see that dht sends DHT_IATT_IN_XDATA_KEY in setxattr
    which will be unwound with the same key in the xdata-response which
    dht thinks is valid response and fills stbuf with invalid values
    leading to EIO
    
    BUG: 1374093
    Change-Id: I6b77a1fa1ee99cb62e181e1db2e6fea73f6eaaa3
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15421
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit fc144b5c8dff6bbe71173d24026d0e41863da021
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ibf069935a630cf10a9a829f5a3194621a891b616
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15282
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 543ca6a3f8096c64ac7da9087c47bb86775fd132
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd (handler): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ic4eabed88a363e85dbc4823b250a5a7f2a00a50f
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15265
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 4903dbaffd1c1ee99889a3f21ac83950cc9a1c4e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd (geo-rep): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I2edacd3d0f3924b1be0f0398ba9ac076459c5a61
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15263
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>

commit 57a65381282160f414ce59133007374f14337f9c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    index: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ibbc34782fdbffb7d9deaf454ebe946d04696035e
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15247
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 68fa57534a5e19d15278cd570eec049a06348232
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (snapshot): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I359145d9e726b0fae78cac8003b57c216780cbba
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15278
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 7c5220a138c0add5f245254a555c97b2f1a4df2f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:12:12 2016 -0400

    snapview-server: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I74cf7adf943f71e0de8d8f487db3cd2394ce16e8
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15251
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 5cd7ec1372e119cc037b2182287ca7eb165e9e89
Author: Kaleb S. KEITHLEY <kkeithle@linux.keithley.org>
Date:   Tue Aug 30 09:44:39 2016 -0400

    protocol/client (no 4): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I7edef3c060b798fcb81d881caa04b346cef7a131
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@linux.keithley.org>
    Reviewed-on: http://review.gluster.org/15356
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>

commit 89236bdb61f99682b794278286ca6b319516c446
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:15:18 2016 -0400

    bd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ia242a51ce153ee3a866a4c7f05a1389841b2bb54
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15256
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1afa0bd91fd23b5131ccc1cceb814a061ac99096
Author: hari gowtham <hgowtham@redhat.com>
Date:   Fri Sep 9 12:26:52 2016 +0530

    Tier: failing detach commit on detach failure and in-progress
    
    PROBLEM: if detach status has failed or if it remains in progress
    we allow detach commit to happen. only detach force should
    be allowed.
    
    FIX: check the detach status for failure or inprogress and disallow
    with the apt error message.
    
    Change-Id: Ib97d540fec67717bb55c18d133187c665cf69ef1
    BUG: 1374584
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/15438
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 8ab0b25f4ee7ae207c9796b51b91c7fca6f47779
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (utils): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I3efaad13cc4cbba7853ada20e838b6fe417ca2d6
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15280
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 4404cd54d58d514d1bc8dd9bffb48fe84a86eac8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Sep 7 10:38:41 2016 +0200

    Update maintainers for "QEMU integration"
    
    Prasanna and I are currently doing the majority of development for the
    Gluster driver in QEMU. Bharata mentioned he prefers to get moved to the
    "thank you" section.
    
    Change-Id: I2a11d7a8f3bdc0f06815aa9701ab2b749b4f851a
    URL: https://www.gluster.org/pipermail/gluster-devel/2016-September/050796.html
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15418
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 00d9abd401ed5d6d78e9641ea31fe0e677f34eb9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Sep 5 11:39:10 2016 +0200

    build: move checkpatch.pl to build-aux
    
    There is no need for checkpatch.pl to be in extras/, it is used similar
    to other scripts that are placed in build-aux/.
    
    Change-Id: Id0f4db1666d83dad31687aa7aadae128fc14c016
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15400
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c4e9ec653c946002ab6d4c71ee8e6df056438a04
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Aug 19 10:33:50 2016 +0530

    dht: "replica.split-brain-status" attribute value is not correct
    
    Problem: In a distributed-replicate volume attribute
             "replica.split-brain-status" value does not display split-brain
               condition though directory is in split-brain.
             If directory is in split brain on mutiple replica-pairs
             it does not show full list of replica pairs.
    
    Solution: Update the dht_aggregate code to aggregate the xattr
              value in this specific condition.
    
    Fix:      1) function getChoices returns the choices from split-brain
                 status string.
              2) function add_opt adding the choices to local buffer to
                 store in dictionary
              3) For the key "replica.split-brain-status" function dht_aggregate
                 call dht_aggregate_split_brain_xattr to prepare the list.
    
    Test:     To verify the patch followed below steps
              1) Create a distributed replica volume and create mount point
              2) Stop heal daemon
              3) Touch file and directories on mount point
                 mkdir test{1..5};touch tmp{1..5}
              4) Down brick process on one of the replica set
                 pkill -9 glusterfsd
              5) Change permission of dir on mount point
                 chmod 755 test{1..5}
              6) Restart brick process on node with force option
              7) kill brick process on other node in same replica set
              8) Change permission of dir again on mount point
                 chmod 766 test{1..5}
              9) Reexecute same step from 4-9 on other replica set also
              10) After check heal status on server it will show dir's are
                  in split brain on all replica sets
              11) After check the replica.split-brain-status attr on mount
                  point it will show wrong status of split brain.
              12) After apply the patch the attribute shows correct value.
    
    BUG: 1368312
    Change-Id: Icdfd72005a4aa82337c342762775a3d1761bbe4a
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15201
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 801cd07a4c6ec65ff930b2ae6bb5e405ccd03334
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Aug 17 15:10:04 2016 +0530

    cluster/dht: heal root permission post add-brick
    
    Post add-brick event the new brick will have permission of 755
    by default. If the root directory permission was other than 755,
    that does not get healed to the new brick leading to permission
    errors/inconsistencies.
    
    For choosing source of attr heal we can trust the subvols which
    have layouts with latest ctime(as part of missing directory heal,
    we heal the proper attr). In case none of the subvols have layout,
    return ESTALE to retrigger a fresh lookup.
    
    Note: This patch heals the permission of the root directories only.
    Since, permission healing of directory is not straight forward and
    required intrusive fix, those are not addressed here.
    
    Change-Id: If894e3895d070d46b62d2452e52c1eaafcf56c29
    BUG: 1368012
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/15195
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ed430fc04e57c89d08cfdd1bb5e408c5baf53adf
Author: ankit <anraj@redhat.com>
Date:   Tue Aug 30 12:55:32 2016 +0530

    dht: Proper log message if data migration is skipped
    
    Change-Id: Id0af15a2aec96bdbe675b4c959b56f0fc8e72504
    BUG: 1341948
    Signed-off-by: ankit <anraj@redhat.com>
    Reviewed-on: http://review.gluster.org/15345
    Tested-by: ankitraj
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 0ed0a560097426a0e20eb533f1018b8d6a5c08c0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Sep 11 20:16:33 2016 +0530

    tests: fix bug-963541.t spurious failure
    
    wait for remove brick to complete before attempt for a commit.
    
    Change-Id: I66ea6c48b6a69fe33d79f9d9080b6f2c1462578e
    BUG: 1374993
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15457
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa742fd88e08eeb807dba1cb98402e8813ec6797
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Sep 9 12:40:38 2016 +0530

    eventsapi: Add conditional import for requests library
    
    requests lib is used only during publishing event. gf_event python
    imports utils.py, and indirectly imports requests lib even though
    it is not required while sending event to eventsd.
    
    Moved "import requests" inside the "plugin_webhook" function.
    
    BUG: 1374587
    Change-Id: Ie3c8088b43d4d7952d01352731999bf8519c73c4
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15439
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 36af81ac7cb2d459f9bfc0c436f0038a68f85235
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Aug 8 17:05:10 2016 +0530

    dht: udpate stbuf from servers those have layout
    
    Problem: For healing of uid/gid we check if local->stbuf.ia_ctime is
    lesser than stbuf->ia_ctime (received from brick). If yes then uid/gid
    is updated to local->prebuf(source of healing).
    
    But we merge local->stbuf also form the newly added brick. So if we
    receive response from the newly added brick first and update the
    local->stbuf, then local->prebuf will remain empty since the newly added
    brick will have the latest ctime among all servers. And this can result
    in healing wrong uid/gids to the rest of servers.
    
    Hence, we should update local->stbuf from servers with a layout which
    will ignore merging stbufs from newly added bricks.
    
    Change-Id: If4b64f75a0ea669abdbe9f5a3d1d18ff19374c2f
    BUG: 1365740
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/15126
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5a1abd235d05809bc7a5c4b94ae7bb51add6fc9c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 31 08:33:44 2016 +0530

    eventsapi: Add Init scripts for different distributions
    
    Added init scripts for
    - SysvInit(CentOS 6 or Red Hat 6)
    - rc.d (FreeBSD)
    
    Most of the latest distributions are using systemd. Support to be
    added for other distributions which are not using systemd.
    
    Removed systemctl wrapper functions(start/stop/status) from
    gluster-eventsapi CLI(peer_eventsapi.py). Status and Reload
    re-implemented using pid file check.
    
    Added pid file support for glustereventsd.
    
    Following dependencies removed
    python-flask - Only used for example dashboard. User can install
    if required.
    python-fasteners - Not available for EPEL 6, added custom code using
    fcntl as replacement.
    
    BUG: 1365395
    Change-Id: I26792eae9b11e93304f70b3997cd7d8d03b067f4
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15367
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit f41ec4fcfaa9ca976fddbe9e91aabf840c20111f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 3 17:52:20 2016 +0530

    geo-rep: Use configured log_level for libgfchangelog logs
    
    libgfchangelog was not respecting the log_level configured
    in Geo-replication. With this patch Libgfchangelog log level
    can be configured using `config changelog_log_level TRACE`.
    Default Changelog log level is INFO
    
    BUG: 1363965
    Change-Id: Ida714931129f6a1331b9d0815da77efcb2b898e3
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15078
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 2209f6d49bc8d16beed52b1d145be936d2da941a
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Sep 6 11:13:20 2016 +0530

    cluster/dht: Skip layout overlap maximization on weighted rebalance
    
    dht_selfheal_layout_maximize_overlap () does not consider
    chunk sizes while calculating overlaps. Temporarily
    enabling this operation if only if weighted rebalance is disabled
    or all bricks are the same size.
    
    Change-Id: I5ed16cdff2551b826a1759ca8338921640bfc7b3
    BUG: 1366494
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/15403
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit b86a7de9b5ea9dcd0a630dbe09fce6d9ad0d8944
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Sep 6 18:28:42 2016 +0530

    feature/bitrot: Fix recovery of corrupted hardlink
    
    Problem:
    When a file with hardlink is corrupted in ec volume,
    the recovery steps mentioned was not working.
    Only name and metadata was healing but not the data.
    
    Cause:
    The bad file marker in the inode context is not removed.
    Hence when self heal tries to open the file for data
    healing, it fails with EIO.
    
    Background:
    The bitrot deletes inode context during forget.
    
    Briefly, the recovery steps involves following steps.
       1. Delete the entry marked with bad file xattr
          from backend. Delete all the hardlinks including
          .glusters hardlink as well.
       2. Access the each hardlink of the file including
          original from the mount.
    
    The step 2 will send lookup to the brick where the files
    are deleted from backend and returns with ENOENT. On
    ENOENT, server xlator forgets the inode if there are
    no dentries associated with it. But in case hardlinks,
    the forget won't be called as dentries (other hardlink
    files) are associated with the inode. Hence bitrot stube
    won't delete it's context failing the data self heal.
    
    Fix:
    Bitrot-stub should delete the inode context on getting
    ENOENT during lookup.
    
    Change-Id: Ice6adc18625799e7afd842ab33b3517c2be264c1
    BUG: 1373520
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/15408
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 593b7a83f7408e59ab7b3ef7dfc4fe4096d6e3cd
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Dec 1 11:50:54 2015 +0100

    cluster/ec: Add support for hardware acceleration
    
    This patch implements functionalities for fast encoding/decoding
    using hardware support. Currently optimized x86_64, SSE and AVX is
    added.
    
    Additionally this patch implements a caching mecanism for inverse
    matrices to reduce computation time, as well as a new method for
    computing the inverse that takes quadratic time instead of cubic.
    
    Finally some unnecessary memory copies have been eliminated to
    further increase performance.
    
    Change-Id: I26c75f26fb4201bd22b51335448ea4357235065a
    BUG: 1289922
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/12837
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8a6236e4cfc7bf86e881e5c770a19040a6060ad0
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 10 14:02:09 2016 +0530

    geo-rep: Handle EISDIR error during Unlink
    
    During Rename, If Source and Target has same inode then
    Geo-rep unlinks source. But if source is a directory then
    this will fail with below traceback
    
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 113, in worker
        res = getattr(self.obj, rmeth)(*in_data[2:])
      File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 772,
        in entry_ops
        os.unlink(entry)
    OSError: [Errno 21] Is a directory: '.gfid/12711ebf-7fdc-4f4b-9850-2d75581eb
       452/New folder'
    
    With this patch, if EISDIR, rmdir is tried. Logs error in Slave log in case
    of ENOTEMPTY.
    
    BUG: 1365791
    Change-Id: I099af4192adac5125c0a23988ceb6506f91e987f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15132
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 9db2826cd8dbcc0fb58f5434c21d00ca5c15c491
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Sep 6 12:02:02 2016 +0530

    geo-rep: Fix ESTALE/EINVAL issue during set_{xtime,stime}
    
    Setfattr may get ESTALE/EINVAL if a file is being unlinked.
    To prevent worker crashing, added retry for these error messages.
    
    On second retry it will get ENOENT and that error is handled by
    ignoring.
    
    BUG: 1373373
    Change-Id: Ic660fa13208366d57c8d3d492bbef611475e45b7
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15404
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit c7118a92f52a2fa33ab69f3e3ef1bdabfee847cf
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Sep 7 11:39:39 2016 +0530

    geo-rep: Fix Geo-rep status if monitor.pid file not exists
    
    If monitor.pid file not exists, gsyncd fails with following traceback
    
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py",
      line 201, in main
        main_i()
      File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py",
      line 681, in main_i
        brick_status.print_status(checkpoint_time=checkpoint_time)
      File "/usr/libexec/glusterfs/python/syncdaemon/gsyncdstatus.py",
      line 343, in print_status
        for key, value in self.get_status(checkpoint_time).items():
      File "/usr/libexec/glusterfs/python/syncdaemon/gsyncdstatus.py",
      line 262, in get_status
        with open(self.monitor_pid_file, "r+") as f:
    IOError: [Errno 2] No such file or directory: '/var/lib/glusterd/
      geo-replication/master_node_slave/monitor.pid'
    
    If Georep status command this worker's status will not be displayed
    since not returning expected status output.
    
    BUG: 1373741
    Change-Id: I600a2f5d9617f993d635b9bc6e393108500db5f9
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15416
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit c0f877c0374d97e0bee17aac4850d7655a35e61b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Sep 1 12:35:46 2016 +0530

    geo-rep: Fix logging sync failures
    
    If Rsync/Tar subprocess dies, while logging error Geo-rep fails
    with EBADF while accessing error file. Also worker dies while
    accessing elines before it is set.
    
    BUG: 1372193
    Change-Id: I9cfce116e8aafa4a98654f5190d40a455af8ec95
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15379
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit cd23242b8953040b231f402c334f16520ac8029f
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Sep 5 21:51:19 2016 +0530

    cluster/tier: add tiering events
    
    Add events for:
    * tier attach and detach
    * tier pause and resume
    * tier rising and dropping hi and lo watermarks
    
    Update eventskeygen.py with tiering events.
    Update cli help with:
    * attach: add optional force argument
    * detach: make force available as non-optional argument on its own
    
    Change-Id: I43990d3a8742151a4a7889bafa19cb572fe661bd
    BUG: 1368336
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15232
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 6f182733d943aff5212175c58dd59b2da64b9d8b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Sep 2 10:42:44 2016 +0530

    cli: fix volume status xml generation
    
    While generating xml, if CLI fails in between xml output doesn't get dumped into
    stdout. Fix is to invoke cli_xml_output_vol_status_end () in such failures.
    
    Change-Id: I7cb3097f5ae23092e6d20f68bd75aa190c31ed88
    BUG: 1372553
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15384
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 34278a042f834b84c5d12fc3f45259136808466b
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Sep 8 10:11:01 2016 +0530

    libglusterfs: Fix wrong git repository url
    
    Change-Id: Iecd4cfacd7536cb3cc9a569c8d96e5284f5e2152
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/15423
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 5de500cd0116796ff797099c60d33258bd48ce3c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 31 11:53:06 2016 +0530

    geo-rep: Fix History post process
    
    This patch removes changelogsdb part of post processing since
    not got much performance advantage as expected.
    
    Entry stime and other logging improvements retained.
    
    BUG: 1364420
    Change-Id: Ib99d23f09d96c14bc28225b47d9134260f5551bf
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15371
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 0fd7d0e1c78fdbedfcdb085445c4b0be3c1a97a9
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Sep 7 15:47:14 2016 +0530

    tests: Fix one of the md-cache test cases
    
    Verify if the unlink, rename and other ops are reflected both on
    the current mount and other mounts.
    
    Change-Id: I5a296cdd557194dcf487e65ee4a14bbeaf4be690
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15419
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e1584b1c1df656612f6233ac40ba55f29591b0c3
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Aug 30 14:17:58 2016 +0530

    cluster/ec: Add events for EC translator
    
    This patch will generates events in following
    cases which will be consumed by new event
    framework.
    
    Consider an EC volume with (K+M) configuration
    K = Data bricks
    M = Redundancy bricks
    
    1- EVENT_EC_MIN_BRICKS_NOT_UP -
       When minimum "K" number of bricks, required
       for any ec fop, are not up.
    2- EVENT_EC_MIN_BRICKS_UP
       When minimum "K" number of bricks, required
       for any ec fop, are up.
    
    Change-Id: I0414b8968c39740a171e5aa14b087afd524d574f
    BUG: 1371470
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/15348
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 86e312d872a957afff1e508f13f62c4102dba22d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Sep 1 13:01:22 2016 +0530

    afr: add replication events
    
    Added the following events for the eventing framework:
    
      "EVENT_AFR_QUORUM_MET", --> Sent when quorum is met.
      "EVENT_AFR_QUORUM_FAIL" -->Sent when quorum is lost.
      "EVENT_AFR_SUBVOL_UP" -->Sent when afr witnesses the first up subvolume.
      "EVENT_AFR_SUBVOLS_DOWN"-->Sent when all children of an afr subvol are down.
      "EVENT_AFR_SPLIT_BRAIN" -->Sent when self-heal detects split-brain in heal
    path (not read/write path).
    
    Change-Id: I937c61ca1ce78b5922ade73c7bfa3051df59c513
    BUG: 1371485
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15349
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f20e41aec392a45f860fa7e80ad5ee9d5607a45c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Sep 5 11:15:10 2016 +0530

    eventsapi: Fix Volume Stop and delete prompt issue
    
    During Volume Stop and Delete, event is emitted even if
    prompt answer is No.
    
    Also added "force" details in START and STOP events.
    
    BUG: 1373072
    Change-Id: I986dcff7154b584f6ed44b533d4eeabe82815235
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15399
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit dd4fae6c78dc70cd31fe82ecd8aa85ade93cf17f
Author: ankit <anraj@redhat.com>
Date:   Tue Sep 6 22:08:23 2016 +0530

    typo error on github link
    
    Change-Id: I011356266500315c43e42c2ba88cd6e5246db3a9
    Signed-off-by: ankit <anraj@redhat.com>
    This error was corrected for https://github.com/gluster/glusterfs
    Reviewed-on: http://review.gluster.org/15412
    Tested-by: ankitraj
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 15c790b502ba92caa17f2d1870c3d75d547e6bad
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Aug 30 12:44:04 2016 +0530

    cluster/dht: move layout logs to DEBUG level
    
    Change-Id: Iad96256218be643b272762b5638a3f6837aff28d
    BUG: 1366495
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/15343
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit db3286184a1ab89d3edb9cf4d645a2db724fada0
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue Aug 30 13:40:41 2016 +0530

    protocol-server: generate events
    
    This patch add/generate the events seen from/in the protocol server
    side, which will be consumed by the new eventing framework.
    
    -------------------------------------------------------------------------
    |          event                |            description                |
    |-------------------------------|---------------------------------------|
    | EVENT_CLIENT_CONNECT          |          new client connected         |
    |-------------------------------|---------------------------------------|
    | EVENT_CLIENT_AUTH_REJECT      |     client cannot be authenticated    |
    |-------------------------------|---------------------------------------|
    | EVENT_CLIENT_DISCONNECT       |        client had disconnected        |
    -------------------------------------------------------------------------
    
    Thanks to "Raghavendra Talur" <rtalur@redhat.com> for all the help
    
    Change-Id: I4fda83fae7747507f64d81a7645cc3a8a2fbaeae
    BUG: 1369403
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/15294
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c67386e1e8edcbdf2f8dca06fc7984df2adb1f06
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (server-quorum): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I53961a9ddbba824ea3cfa00abbba20109da5de89
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15276
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 9c057750310b7e296624746bfeb909690320a2b3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Sep 2 09:33:16 2016 -0400

    common-ha: ganesha_mon: line 137: [: too many arguments ]" messages
    
    ensure that there are always valid, non-null arguments to /bin/test
    
    Here there be dragons. Very racy, but if the races lose, they lose
    in a way that's consistent with what we're testing for anyway, namely
    that the ganesha.nfsd process is gone.
    
    Change-Id: I88b770dd874ffa8576711f8009f27122a4fb0130
    BUG: 1363595
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15390
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 6289a0a0f0ec855a1971fdf4954d81645111e2f0
Author: Kaleb S. KEITHLEY <kkeithle@linux.keithley.org>
Date:   Tue Aug 30 09:46:00 2016 -0400

    protocol/client (no 5): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: Ic209b1291927c56f009544eadebdc51ba5f77475
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@linux.keithley.org>
    Reviewed-on: http://review.gluster.org/15357
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 02c828f54a693abf1521aa9b889289b25a463b4f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 29 14:24:48 2016 -0400

    protocol/client (no 2): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I54055b3b1038374b4e21432da48fdaeca2938289
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15339
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 17be5486151a65947bc6cbd2cfaa39fcd0af50a1
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 29 14:22:42 2016 -0400

    protocol/client (no 1): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    BUG: 1369124
    Change-Id: I8a24e3c02144860859d653ab7115895fb3066378
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15338
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 261c035c7d0cd1639cc8bd0ead82c30efcc0e93f
Author: Diogenes Nunez <dnunez@redhat.com>
Date:   Wed Jul 27 11:09:47 2016 -0400

    cluster/tier: Adding compaction option for metadata databases
    
    Problem: As metadata in the database fills up, querying the database
    take a long time. As a result, tier migration slows down.  To
    counteract this, we added a way to enable the compaction methods of
    the underlying database. The goal is to reduce the size of the
    underlying file by eliminating database fragmentation.
    
    NOTE: There is currently a bug where sometimes a brick will
    attempt to activate compaction. This happens even compaction is already
    turned on.
    
    The cause is narrowed down to the compact_mode_switch flipping its value.
    
    Changes: libglusterfs/src/gfdb - Added a gfdb function to compact the
    underlying database, compact_db() This is a no-op if the database has
    no such option.
    
    - Added a compaction function for SQLite3 that does the following
    
    1) Changes the auto_vacuum pragma of the database
    2) Compacts the database according to the type of compaction requested
    
    - Compaction type can be changed by changing the macro
      GF_SQL_COMPACT_DEF to one of the 4 compaction types in
      gfdb_sqlite3.h
    
      It is currently set to GF_SQL_COMPACT_INCR, or incremental
      vacuuming.
    
    xlators/cluster/dht/src - Added the following command-line option to
    enable SQLite3 compaction.
    
    gluster volume set <vol-name> tier-compact <off|on>
    
    - Added the following command-line option to change the frequency the
      hot and cold tier are ordered to compact.
    
    gluster volume set <vol-name> tier-hot-compact-frequency <int>
    gluster volume set <vol-name> tier-cold-compact-frequency <int>
    
    - tier daemon periodically sends the (new)
      GFDB_IPC_CTR_SET_COMPACT_PRAGMA IPC to the CTR xlator. The IPC
      triggers compaction of the database.
    
      The inputs are both gf_boolean_t.
    
      IPC Input:
    
      compact_active: Is compaction currently on for the db.
      compact_mode_switched: Did we flip the compaction switch recently?
    
      IPC Output:
    
      0 if the compaction succeeds.
      Non-zero otherwise.
    
    xlators/features/changetimerecorder/src/ - When the CTR gets the
    compaction IPC, it launches a thread that will perform the
    compaction. The IPC ends after the thread is launched. To avoid extra
    allocations, the parameters are passed using static variables.
    
    Change-Id: I5e1433becb9eeff2afe8dcb4a5798977bf5ba0dd
    Signed-off-by: Diogenes Nunez <dnunez@redhat.com>
    Reviewed-on: http://review.gluster.org/15031
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 6459fc812219551291e4be426ed8ecf2c90813a4
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Sep 2 10:47:13 2016 +0530

    tests: Fix one of the upcall tests
    
    Currently md-cache invalidation feature is enabled by setting
    "performance.cache-invalidation", but this case was sent when
    "features.cache-invalidation" was enabling md-cache invalidation.
    Hence, fix the same.
    
    Change-Id: If044f6208179748a120fbe1d63b676367e707f73
    BUG: 1372584
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15385
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1f1850ae79a836f1de783c990e575a0d29e26dee
Author: Ryan Ding <ryan.ding@open-fs.com>
Date:   Tue Aug 23 17:42:44 2016 +0800

    features/changelog: fix a segment fault in changelog_cleanup_dispatchers
    
    the arg 'count' in changelog_cleanup_dispatchers means the thread count
    to cleanup, so the cleanup loop should start with count-1, not count.
    change the invoke place also.
    
    Change-Id: Ia00853a2e0c5e01e145f60048b1f0ac05f2440ab
    BUG: 1369397
    Signed-off-by: Ryan Ding <ryan.ding@open-fs.com>
    Reviewed-on: http://review.gluster.org/15293
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit befae0b48729894282b5b8b174907e24779c3442
Author: Anuradha Talur <atalur@redhat.com>
Date:   Thu Aug 25 11:46:25 2016 +0530

    afr: Consume compound fops in afr transaction
    
    Change-Id: Ib06ece3cce1b10d28d6d2953da28444f5c2457ad
    BUG: 1290304
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/15014
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 68b23745602e4cc6317d6dce72ed0392d4174972
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Aug 25 11:49:19 2016 +0530

    feature/locks: Implement fops in locks Translator
    
    Implement those fop which were not present in
    locks translator.
    Also make sure to return xdata with the
    entries which were requested for these fops.
    
    Change-Id: I6e7f80e9eb5fba9e34c7034f6bc30557cde20927
    BUG: 1231224
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/11204
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 4ac0cf9c7ba7d98cc21b88aa6d7aa9f7c8884a67
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Aug 30 18:10:16 2016 +0530

    gfapi: Mark tests/basic/gfapi/bug1291259.t bad until it is fixed
    
    Change-Id: Ia0493ce7e71050b3e8a1a1fed2d861cc141a0f94
    BUG: 1371540
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15353
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit c1278de9a5fb6a64455f42b8b17a8d05b74c2420
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Aug 26 14:05:07 2016 +0530

    snapshot/eventsapi: Integrate snapshot events with eventsapi
    
    1. EVENT_SNAPSHOT_CREATED : snapshot_name=snap1 volume_name=test_vol
                                snapshot_uuid=26dd6c52-6021-40b1-a507-001a80401d70
    2. EVENT_SNAPSHOT_CREATE_FAILED : snapshot_name=snap1 volume_name=test_vol
                                      error=Snapshot snap1 already exists
    3. EVENT_SNAPSHOT_ACTIVATED : snapshot_name=snap1
                                  snapshot_uuid=26dd6c52-6021-40b1-a507-001a80401d70
    4. EVENT_SNAPSHOT_ACTIVATE_FAILED: snapshot_name=snap1
                                       error=Snapshot snap1 is already activated.
    5. EVENT_SNAPSHOT_DEACTIVATED : snapshot_name=snap1
                                  snapshot_uuid=26dd6c52-6021-40b1-a507-001a80401d70
    6. EVENT_SNAPSHOT_DEACTIVATE_FAILED : snapshot_name=snap3
                                          error=Snapshot (snap3) does not exist.
    7. EVENT_SNAPSHOT_SOFT_LIMIT_REACHED : volume_name=test_vol
                                      volume_id=2ace2616-5591-4b9b-be2a-38592dda5758
    8. EVENT_SNAPSHOT_HARD_LIMIT_REACHED : volume_name=test_vol
                                      volume_id=2ace2616-5591-4b9b-be2a-38592dda5758
    9. EVENT_SNAPSHOT_RESTORED : snapshot_name=snap1 volume_name=test_vol
                                 snapshot_uuid=3a840ec5-08da-4f2b-850d-1d5539a5d14d
    10. EVENT_SNAPSHOT_RESTORE_FAILED : snapshot_name=snap10
                                        error=Snapshot (snap10) does not exist
    11. EVENT_SNAPSHOT_DELETED : snapshot_name=snap1
                                 snapshot_uuid=d9ff3d4f-f579-4345-a4da-4f9353f0950c
    12. EVENT_SNAPSHOT_DELETE_FAILED : snapshot_name=snap2
                                       error=Snapshot (snap2) does not exist
    13. EVENT_SNAPSHOT_CLONED : clone_uuid=93ba9f06-cb9c-4ace-aa52-2616e7f31022
                                snapshot_name=snap1 clone_name=clone2
    14. EVENT_SNAPSHOT_CLONE_FAILED : snapshot_name=snap1 clone_name=clone2
                                      error=Volume with name:clone2 already exists
    15. EVENT_SNAPSHOT_CONFIG_UPDATED : auto-delete=enable config_type=system_config
                                        config_type=volume_config hard_limit=100
    16. EVENT_SNAPSHOT_CONFIG_UPDATE_FAILED :
                       error=Invalid snap-max-soft-limit 110. Expected range 1 - 100
    17. EVENT_SNAPSHOT_SCHEDULER_INITIALISED : status=Success
    18. EVENT_SNAPSHOT_SCHEDULER_INIT_FAILED
    19. EVENT_SNAPSHOT_SCHEDULER_ENABLED : status=Successfuly Enabled
    20. EVENT_SNAPSHOT_SCHEDULER_ENABLE_FAILED :
                                       error=Snapshot scheduler is already enabled.
    21. EVENT_SNAPSHOT_SCHEDULER_SCHEDULE_ADDED : status=Successfuly added job job1
    22. EVENT_SNAPSHOT_SCHEDULER_SCHEDULE_ADD_FAILED :
                        status=Failed to add job job1 error=The job already exists.
    23. EVENT_SNAPSHOT_SCHEDULER_SCHEDULE_EDITED :
                                                 status=Successfuly edited job job1
    24. EVENT_SNAPSHOT_SCHEDULER_SCHEDULE_EDIT_FAILED :
                                                     status=Failed to edit job job2
                                                     error=The job cannot be found.
    25. EVENT_SNAPSHOT_SCHEDULER_SCHEDULE_DELETED :
                                                status=Successfuly deleted job job1
    26. EVENT_SNAPSHOT_SCHEDULER_SCHEDULE_DELETE_FAILED :
                                                   status=Failed to delete job job1
                                                   error=The job cannot be found.
    27. EVENT_SNAPSHOT_SCHEDULER_DISABLED : status=Successfuly Disabled
    28. EVENT_SNAPSHOT_SCHEDULER_DISABLE_FAILED :
                                       error=Snapshot scheduler is already disabled.
    
    Change-Id: I3479cc3fb7af3c76ded67cf289f99547d0a55d21
    BUG: 1370567
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/15329
    Tested-by: Aravinda VK <avishwan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit ee0d8ca53f685f8f27c93b3d7c808f2a78c1ae43
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Aug 17 20:19:59 2016 +0530

    io-stats: Add stats for upcall notifications
    
    With this patch, there will be additional entries seen in
    the profile info:
    
    UPCALL : Total number of upcall events that were sent from
             the brick(in brick profile), and number of upcall
             notifications recieved by client(in client profile)
    
    Cache invalidation events:
    -------------------------
    CI_IATT : Number of upcalls that were cache invalidation and
             had one of the IATT_UPDATE_FLAGS set. This indicates
             that one of the iatt value was changed.
    
    CI_XATTR : Number of upcalls that were cache invalidation, and
             had one of the UP_XATTR or UP_XATTR_RM set. This indicates
             that an xattr was updated or deleted.
    
    CI_RENAME : Number of upcalls that were cache invalidation,
             resulted by the renaming of a file or directory
    
    CI_UNLINK : Number of upcalls that were cache invalidation,
             resulted by the unlink of a file.
    
    CI_FORGET : Number of upcalls that were cache invalidation,
             resulted by the forget of inode on the server side.
    
    Lease events:
    ------------
    LEASE_RECALL : Number of lease recalls sent by the brick (in
             brick profile), and number of lease recalls recieved
             by client(in client profile)
    
    Note that the sum of CI_IATT, CI_XATTR, CI_RENAME, CI_UNLINK,
    CI_FORGET, LEASE_RECALL may not be equal to UPCALL. This is
    because, each cache invalidation can carry multiple flags.
    Eg:
    - Every CI_XATTR will have CI_IATT
    - Every CI_UNLINK will also increment CI_IATT as link count is an
    iatt attribute.
    
    Also UP_PARENT_DENTRY_FLAGS is currently not accounted for,
    as CI_RENAME and CI_UNLINK will always have the flag
    UP_PARENT_DENTRY_FLAGS
    
    Change-Id: Ieb8cd21dde2c4c7618f12d025a5e5156f9cc0fe9
    BUG: 1371543
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15193
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 054b09eb5f040ccc0adbb86759da403b49544083
Author: Anuradha Talur <atalur@redhat.com>
Date:   Wed Aug 31 15:27:31 2016 +0530

    event: fix gf_event messages for replace/reset brick op
    
    Change-Id: I80ebeeaffd2b228d7d0796c8d08bc2a051c4ccac
    BUG: 1266876
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/15370
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 63d24908e01b24cc21bea584fed4b719fca865f3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Aug 30 02:02:45 2016 +0530

    tests: Fix spurious failures because of wrong shd up function
    
    Fixed the way shd up check is done to prevent self-heal daemon
    not running error when heal full command is executed.
    
    Change-Id: I93c4a0da12316373d62cd4ea74432cd9bf2b090c
    BUG: 1370053
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15341
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>

commit d354ea0a05a3b6a13d227b567a81afdb8ea46abb
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Wed Aug 24 15:19:53 2016 +0530

    geo-rep: add geo-rep events for server side changes
    
    Event Type defined in #15351 to avoid merge conflicts
    
    Add geo-rep events applicable to changes in
    geo-rep session in the server side.
    
    Change-Id: Ia66574d2abccad7fce6a96667efbc7c6c8903fc6
    BUG: 1370445
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/15328
    Tested-by: Aravinda VK <avishwan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 9d8bbbb8f68a0c45bfbb2e891cdbd9b9a1121259
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Aug 25 10:09:20 2016 +0530

    upcall: Mark the clients as accessed on readdirp entries
    
    Currently when a client performs a readdirp it is not stored
    in upcall, as one of the clients that have accessed the files.
    Hence, when any other client modifies the file, the client that
    had performed readdirp will not get any notifications.
    
    Fix this by adding the clients to upcall database when they
    perform readdirp.
    
    Change-Id: I7767f1e26bf1bd1f67702a6d01f8aa64526ccc46
    BUG: 1369430
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15313
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit add85dda0127262164123c6373d55ff2cf9bb14b
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Aug 31 16:07:09 2016 +0530

    tests: disable lock_revocation.t on NetBSD
    
    This has been consistently causing hangs in NetBSD machines. I have not
    been able to debug the issue and we have merge deadline for 3.9. It
    would be better to disable this for now.
    
    Change-Id: I8c63940aa26f78dd9994bb63293a5757835ec52b
    BUG: 1369401
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/15374
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2d3292fd29884b16cac058f937f91cfda197eca6
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Aug 31 10:47:45 2016 +0530

    cli: Fix double unref of dict
    
    Problem: `gluster system:: uuid get` hangs due to double unref of dict.
    
    Fix:
    Remove the unnecessary unref in cli_cmd_uuid_get_cbk(). In the said
    function, if calling proc->fn() is sucessful, the dict is automatically
    unrefed in its cbk as a part of cli_local_wipe(). If calling proc->fn() fails,
    then CLI_STACK_DESTROY() takes care of the unref.
    
    Change-Id: Ib656d200f14a27415b36794a0bdadfe36b0d5306
    BUG: 1371775
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15368
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 513bf9b72fddbd1f69ce4b31b16e0611c84a9378
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Aug 30 18:05:11 2016 +0530

    eventsapi: declare all the identified events at one go
    
    This patch ensures we don't get into merge conflicts
    everytime a single eventing patch is merged which
    changes eventskeygen.py. I've collected all the identified
    events from the patches posted in gerrit for reviews and
    consolidated at one place.
    
    Change-Id: I5a5983d5c8db7c4a223fa02b4f99ec41c6fa9c35
    BUG: 1334044
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15351
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 29a57765d524af8ec0e5bab17e5ff7f47b968342
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 15 13:54:37 2016 +0530

    geo-rep: Alternate command to generate SSH Keys
    
    `gluster system:: execute gsec_create` is used to generate SSH
    Keys in all Master nodes and collect public keys in command initiated
    node. But this tool will not provide details if a peer node is down and
    unable to generate keys.
    
    New command will be introduced to create SSH Keys in all peer nodes.
    
    Usage:
    
        gluster-georep-sshkey generate
        or
        gluster-georep-sshkey generate --no-prefix
    
    Generates two SSH keys(one for gsyncd access and other for tar) in all
    peer nodes and collects the public keys to the local node where it is
    initiated. Adds `command=` prefix to common_secret.pem.pub if `--no-prefix`
    argument is not set.
    
    Shows status as below,
    
    +-----------+-------------+---------------+
    |    NODE   | NODE STATUS | KEYGEN STATUS |
    +-----------+-------------+---------------+
    |    fvm2   |          UP |            OK |
    | localhost |          UP |            OK |
    +-----------+-------------+---------------+
    
    BUG: 1356508
    Change-Id: Ib202811f41f9986694f07d9eedba31db6ed4d18f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14732
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit f7e91cd7f0264894033ee98c44c552fcf5a0506c
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Aug 30 17:19:47 2016 +0530

    extras: Fix failed_tests.py to have the updated regression links
    
    Change-Id: Iee79389d835cae91288fbbe9b2b266ea2ba4b30e
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15350
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 7cbc10037ecc873d60c3a970d00faf2819019525
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Aug 29 16:41:09 2016 +0530

    compound fops: Some fixes to compound fops framework
    
    Change-Id: I808fd5f9f002a35bff94d310c5d61a781e49570b
    BUG: 1360169
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/15010
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit fe929224c47d5c82da5650e9e1041645a8d7f244
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Aug 25 15:43:29 2016 +0530

    md-cache: Process all the cache invalidation flags
    
    Currently, md-cache only processes IATT_UPDATE_FLAGS, UP_XATTR and
    UP_XATTR_RM. We also need to process UP_RENAME_FLAGS, UP_FORGET,
    UP_PARENT_DENTRY_FLAGS and UP_NLINK_FLAGS. Otherwise the files
    unlinked or renamed will not be reflected on other mounts.
    
    Change-Id: Icb8b03da51482c3fc2e2a7292d16d56e11a341d9
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15324
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 065a27948c4e0651f5bdac1703939adf34e5380e
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Aug 23 18:15:22 2016 +0530

    dht, md-cache, upcall: Add invalidation of IATT when the layout changes
    
    Issue:
    dht_layout is built as a part of lookup only. The layout can be
    modified by rebalance process. Since every IO fop is preceded
    by a lookup, there are very less issues of stale layout. But
    with enhancements of aggressive caching of stats in md-cache,
    the lookup will reduce and expose the stale layout issue often.
    
    Solution:
    Since stale layout is already an issue on dht, there is already
    a plan to fix this at the dht layer, but this fix is not currently
    planned for any release. Until this fix comes out, we can have
    a workaround where, the upcall will send a notification to md-cache
    when a layout xattr is changed. As a part of layout change notification
    the existing cache is invalidated and the next lookup will fetch the
    latest layout.
    
    This is not a foolproof solution as the window between the layout change
    and the next lookup(after invalidation of stat), where there will be stale
    layout. But until the final fix comes in, this reduces the stale layout
    window.
    
    Change-Id: Iacf871a38b35880c1fc0bc68fe7ce291265e71d4
    BUG: 1369638
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15300
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 8f053f9d7270f1c6d50c0b3ab5d020503ceeb31a
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jul 11 15:04:55 2016 +0530

    md-cache: Register the list of xattrs with cache-invalidation
    
    Issue:
    md-cache caches a specified list of xattrs, and when cache invalidation
    is enabled, it makes sense to recieve invalidation only when those xattrs
    are modified by other clients. But the current implementation of upcall
    is that, it will send invalidation when any of the on-disk xattrs is modified.
    
    Solution:
    md-cache sends a list of xattrs that it is interested in, to upcall by
    issuing an ipc(). The challenge here is to make sure everytime a brick
    goes offline and comes back up, the ipc() needs to be issued to the
    bricks. Hence ipc() is sent from md-cache every time there is a
    CHILD_UP/CHILD_MODIFIED event.
    
    TODO:
    There will be patches following, in cluster xlators, to implement ipc fop.
    
    Change-Id: I6efcf3df474f5ce6eabd3d6694c00c7bd89bc25d
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15002
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 55c255b27a99f027cb716800f8330f8faa4eb1f5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu May 26 15:52:53 2016 +0530

    geo-rep: Simplify Non root user(mountbroker) Setup
    
    Setting up Non root Geo-replication is troublesome. Lot of steps
    involved like user setup, directory creation, setting up proper
    permissions, editing glusterd.vol file etc.
    
    Introducing `gluster-mountbroker` command, with this tool non root
    user setup steps are(Run the following commands in any one Slave
    node),
    
        gluster-mountbroker setup <MOUNT ROOT> <GROUP>
    
    For example,
    
        gluster-mountbroker setup /var/mountbroker-root geogroup
    
    Add user using,
    
        gluster-mountbroker add <VOLUME> <USER>
    
    For example,
    
        gluster-mountbroker add slavevol geoaccount
    
    Remove user or Volume using,
    
        gluster-mountbroker remove [--volume <VOLUME>] [--user <USER>]
    
    Example,
    
        gluster-mountbroker remove --volume slavevol --user geoaccount
        gluster-mountbroker remove --user geoaccount
        gluster-mountbroker remove --volume slavevol
    
    Check the status of setup using,
    
        gluster-mountbroker status
    
    Once the changes are complete, restart glusterd in all Slave nodes.
    and follow the Geo-rep instructions.
    
    Change-Id: Ied3fa009df6a886b24ddd86d39283fcfcff68c82
    BUG: 1343333
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14544
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit e2b3fd30572ec8ca381540bd6b23b9ef3ae41ac5
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (op-sm): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I6c1474547586b5e43f30545872ec512cdd32dac2
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15269
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit b71ae7d77d7ab1581d266f6435d134958844d0db
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 17 13:46:00 2016 +0530

    eventsapi: Add support for Client side Events
    
    Client side gf_event uses ctx->cmd_args.volfile_server to push
    notifications to the eventsd.
    
    Socket server changed from Unix domain socket to UDP to support
    external events.
    
    Following to be addressed in different patch
    - Port used for eventsd is 24009. Make it configurable
      Already configurable in Server side. Configurable in gf_event API
      is required.
    - Auth Token yet to be added as discussed in
      https://www.gluster.org/pipermail/gluster-devel/2016-August/050324.html
    
    Change-Id: I159acf80b681d10b82d52cfb3ffdf85cb896542d
    BUG: 1367774
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15189
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit c1f5cf0bda47fc34725084ee3988b0efe2dcfc8a
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Aug 30 18:14:45 2016 +0530

    gfapi: Mark tests/basic/gfapi/1093594.t bad until it is fixed
    
    Change-Id: If88efe3db782a6156614af4c650d53b159ade57f
    BUG: 1371541
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15354
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 68cc90552b7109ee8d740decc33d65cfdfe0bf81
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    dht/tiering: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I367a737570dd7d2f6cc25f4bf4299d31bb6826aa
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15242
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 936f8aeac3252951e7fa0cdaa5d260fad3bd5ea0
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd : Introduce reset brick
    
    The command basically allows replace brick with src and
    dst bricks as same.
    
    Usage:
    gluster v reset-brick <volname> <hostname:brick-path> start
    This command kills the brick to be reset. Once this command is run,
    admin can do other manual operations that they need to do,
    like configuring some options for the brick. Once this is done,
    resetting the brick can be continued with the following options.
    
    gluster v reset-brick <vname> <hostname:brick> <hostname:brick> commit {force}
    
    Does the job of resetting the brick. 'force' option should be used
    when the brick already contains volinfo id.
    
    Problem: On doing a disk-replacement of a brick in a replicate volume
    the following 2 scenarios may occur :
    
    a) there is a chance that reads are served from this replaced-disk brick,
    which leads to empty reads. b) potential data loss if next writes succeed
    only on replaced brick, and heal is done to other bricks from this one.
    
    Solution: After disk-replacement, make sure that reset-brick command is
    run for that brick so that pending markers are set for the brick and it
    is not chosen as source for reads and heal. But, as of now replace-brick
    for the same brick-path is not allowed. In order to fix the above
    mentioned problem, same brick-path replace-brick is needed.
    With this patch reset-brick commit {force} will be allowed even when
    source and destination <hostname:brickpath> are identical as long as
    1) destination brick is not alive
    2) source and destination brick have the same brick uuid and path.
    Also, the destination brick after replace-brick will use the same port
    as the source brick.
    
    Change-Id: I440b9e892ffb781ea4b8563688c3f85c7a7c89de
    BUG: 1266876
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12250
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c204f452dfd9907a0d32f35294a0805701a6d993
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:15:22 2016 -0400

    posix: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ibb3057cc072097434350c1dd2139b18610295825
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15257
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit b231acedb8696ef298a405ffedd36dba8a7183be
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Id6f7555e35fd2bc37e8b9f81ac37d5384624501c
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15285
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 253a6b2ae8c4d12c76a89635e89e99f40b9de08d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I4ce4ec8073c1da4ea60bf5488b3f57c91c4cffa6
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15284
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit 55d70915665a73e951acc505a82a1ddee00609c8
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ibe060202efb1f175a4348ff0927a7b44303d96e6
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15283
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 2c13e7e04711ef6da55e7616f064f801a41cc46d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (snapshot-utils): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I5d3372de16a1e03a6391885434ffea84f6a00412
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15277
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 2740279cc66e03572aa3f1f47d18d1d708704d71
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (replace-brick): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I58aede09a2f2c65a438188d7319ad7a61395e7a9
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15274
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit fb6c3540c14690d4e62e0f32cc08a0d744c4b843
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (rebalance): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I136cf4c1d318f98933f3bfed81e2de3da0f56abc
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15273
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 3bfb64d272f6dc83f39f1c7b94f768497435a816
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (peer-utils): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I99e818d71e72aaa2dfb629f00a5245365f582b99
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15270
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 4af92dbe71b2ddbcf989fd8d59d93c17e6879311
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd (hooks): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I401090b0c51c90cf148c75756408c70ccee6a5e6
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15267
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit d27b23576ba584942239b2432c792d4ff398b7fc
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd (handshake): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I25b40c89d883d088e4aaba87ce0bf235a09a27da
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15266
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit d2d6b327e5fff7a47cdd54c61493e7dddd7f557c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd (bitd-svc): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I1a96cd72fce6b109769f11f17b625fe152298888
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15260
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit ec5c0ca6768b33761aa438f9948c4a6daaf4ee3c
Author: ankit <anraj@redhat.com>
Date:   Wed Aug 24 21:34:35 2016 +0530

    rpc: dead code fix
    
    CID: 1357866
    
    Change-Id: I117cfd455b05df8d2bd9c8df4a081ffe4d053d09
    BUG: 789278
    Signed-off-by: ankit <anraj@redhat.com>
    Reviewed-on: http://review.gluster.org/15310
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: ankitraj
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e2e93882b0441c46d63ca78e56331abdd42d80cc
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    core: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Id9bf5732f8c94824769409f7895be9dbe6fbd5fa
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15249
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ae2ddb59381c37d79b4f1ce13028f02e9fffea47
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    core: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I3d8a7a3de35058aa97eab59d3f59208396298b03
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15246
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 4640061a357632258541141163764314993e40ca
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    bit-rot: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I566fcbcae5aec575bfca40975b941c53546d4d97
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15245
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 5751f294fc8c6ea256fc5a842c7a6eef14d35fd3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    afr: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I98e3308a2548ae095048caa99c86edec15b5e782
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15241
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit a4a48b4423a8ff21b39ed231d91cc27f74ff80f6
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd (ganesha): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I8496b0d1158aeac88cdee991e40c5bb1705f1c09
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15262
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b199e81f5e07f89252ecc646546a58f8541b5f9a
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd (store): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I9de669261b91e89a719997b54adeea893f8c3bee
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15264
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b25299b74389bfaef45a3b9034a0cad628c2a342
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:31:28 2016 -0400

    shard: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I3e53f12371b002d7f2fe2e281b63794c7769f823
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15258
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 2a3de9c61745afa786fd961ab70424b8f81a2599
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (quota): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Id1bc618261a73d91847f65cb790109fda9e77c65
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15271
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit 58997a904f2a106d6f2d7629e01f8f69e9918ba7
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Aug 29 12:40:48 2016 +0530

    glusterd: Fix msgid in mountbroker logs
    
    Fix declared but not used msgid in mountbroker
    logs.
    
    Change-Id: I68d331f2741726624f647a8bc437e1ebcddd038f
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    BUG: 1346138
    Reviewed-on: http://review.gluster.org/15333
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ff7eb311877f52a8fc543084317a537d42f496ee
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Aug 24 09:55:32 2016 +0530

    upcall: Add permission change flag to iatt flag
    
    Currently IATT_UPDATE_FLAGS is (UP_NLINK | UP_MODE | UP_OWN | UP_SIZE |
    UP_TIMES | UP_ATIME). But it should also have UP_PERM and permission bits
    are apart of IATT.
    
    This change will have no effect on the existing users as
    IATT_UPDATE_FLAGS is currently used only by md-cache. And the changes in
    md-cache to consume cache invalidation is not part of any release yet.
    
    Change-Id: I7efad44972add152f5f981d733fb8191dc7ef8ef
    BUG: 1369432
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15301
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7f0042dce94edb58c92662d9e4f852ba006d12dc
Author: Ryan Ding <ryan.ding@open-fs.com>
Date:   Wed Aug 24 00:24:30 2016 +0800

    features/upcall: segment fault while join thread reaper_thr in fini()
    
    reaper_thr thread may not be started according to option
    'cache-invalidation', if it's not started, join it in fini will cause a
    segment fault.
    
    Change-Id: I1c145a5feb137767880a08e79f810537283fb6b9
    BUG: 1369524
    Signed-off-by: Ryan Ding <ryan.ding@open-fs.com>
    [ndevos: check .reaper_init_done and make it a boolean]
    Reviewed-on: http://review.gluster.org/15298
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8bb8e3d394d277b6e50ccd2ef6a3e907379371c8
Author: Nigel Babu <nigelb@redhat.com>
Date:   Tue Jul 26 18:55:16 2016 +0530

    Clean up the failed-buids.py script
    
    * Use the Jenkins API instead of looking up every job.
    * Unify the output function with Pystache
    * Mostly follow pep8 guidelines and make the script more pythonic
    
    Change-Id: Ia5e0061638732e293e94b3a8ad9e25a7db65cfa5
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: http://review.gluster.org/15034
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ddcf0183adebe528a3b069358a1f856eeeae5857
Author: Muthu-vigneshwaran <mvignesh@redhat.com>
Date:   Thu Aug 11 17:07:29 2016 +0530

    cli,rpc : Removing logically dead code
    
    CID = 1357865, 1357866
    
    Change-Id: I05eb345e9357d889872d259a600759392b188bb3
    BUG: 789278
    Signed-off-by: Muthu-vigneshwaran <mvignesh@redhat.com>
    Reviewed-on: http://review.gluster.org/15148
    Tested-by: Muthu Vigneshwaran
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit 494d310a78fb423559d520040eebd8f091d3e529
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    core: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I16e55ad7afbddaee0d0e30acf1480e42adf96da4
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15243
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 00ee35093917f57b97b523decee9c58050d35d32
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    rpc: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I20d91091bee0bf8f198a307ebba4b284bc3817ff
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15240
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 589a2c296ba8a778352ea54fd3d0fe02a573f053
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    jbr: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I68c210f3bcc0f7754a89095c0d1408d57d5bd4a2
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15244
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit eaad568af3c11b9fd482f313b44f47e7e71e3362
Author: Poornima G <pgurusid@redhat.com>
Date:   Sun Aug 21 17:14:06 2016 +0530

    io-stats: Add ipc fop for display in the profile info
    
    Change-Id: I959899ac00b3019ed45bd0127c4dc9a27a74bcb9
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15224
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 87303b77ddbdc29a415acc2c73bfaafa9be10609
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Aug 17 17:47:08 2016 +0530

    extras: kill gsyncd before glusterfsd
    
    It's a good practice to kill gsyncd before brick process, else we see
    unnecessary loops and logs of bring up the faulty bricks
    
    Change-Id: I2d2176f2bf5014f3afd622194a8b2d60c86926af
    BUG: 1367771
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/15187
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 14b46be09c98c1ef75f55af34ec762b3e34899f1
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Aug 17 17:31:17 2016 +0530

    extras: kill processes gracefully
    
    Currently all of brick, gsyncd and other glustershd services/processes
    are killed without checking for ongoing tasks such as geo-rep,
    self-heal, rebalance and etc. which may lead to inconsistency after
    the node is brought back.
    
    This patch introduce an option '-g' which ensures whether all the
    gluster processes are ready (not busy) to be terminated before we
    executing 'kill' on them
    
    Usage: ./extras/stop-all-gluster-processes.sh [-g] [-h]
        options:
        -g  Terminate in graceful mode
        -h  Show this message, then exit
    
     eg:
      1. ./extras/stop-all-gluster-processes.sh
      2. ./extras/stop-all-gluster-processes.sh -g
    
    By default, this script executes in force mode, processes are killed
    without checking for ongoing tasks, on specifying '-g' option this
    script works in graceful mode, which returns exitcode if some of gluster
    processes are busy in doing their jobs.
    
    exitcodes include:
       0       No errors/Success
       64      Rebalance is in progress
       65      Self-Heal is in progress
       66      Tier daemon running on this node
       127     option not found
    
    Change-Id: I2f924b2bf9f04a81788d0f5604895a42755b33a1
    BUG: 1367771
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/15188
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f463c4615ba93e2ebe7eb12a2ebc13333ecaa016
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 24 14:02:08 2016 +0530

    packaging/eventsapi: Make Python site-packages variable global
    
    Python site-packages path is assigned when glupy is enabled.
    Eventsapi will not work as expected if glupy is disabled using
    ./configure --disable-glupy.
    
    With this patch, all the Python variables are moved out of glupy
    and used inside it.
    
    systemd services will fail if we import gluster.cliutils python library
    which is installed in /usr/local/lib/python.2.7/site-packages or some
    other location. With this patch, Environment variable is added in
    systemd service file.
    
    BUG: 1369721
    Change-Id: I9416240f03889e3bbcb4cd375e27c784fa9ca277
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15305
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 62f4e41e9eafd2838d2a11989f08b0e7627284b4
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Aug 2 15:33:34 2016 +0000

    gfapi: SSL connection for mgmt connection is not working
    
    Problem: libgfapi does not enable SSL on mgmt connection.
    
    Fix: Enable SSL when it is enabled on mgmt connection is enabled,
    i.e. presence of /var/lib/glusterd/secure-access file
    
    Change-Id: I1ce4935b04e6140aeab819e42076defd580b0727
    BUG: 1362602
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15073
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 70dabd796c04eb6e95fbf83e73219e671cc05dd3
Author: Anuradha Talur <atalur@redhat.com>
Date:   Thu Aug 25 12:19:16 2016 +0530

    tests: change EXPECT_WITHIN timeouts
    
    Use defined HEAL and PROCESS_UP timeouts rather than
    hard code them in self-heald.t.
    
    Change-Id: I21586811904c8417b7208bb643f14dff20dc4832
    BUG: 1370074
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/15316
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6fbaf88ac0f6b377126b847d287ed77e3146ce1c
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Sat Aug 27 20:24:20 2016 +0530

    dht: define GF_IPC_TARGET_UPCALL
    
    In patch http://review.gluster.org/#/c/15225/
    GF_IPC_TARGET_UPCALL was used but not defined,
    because of which build is broken
    
    Hence fixing it here.
    
    Change-Id: I81e1e63cba25a49fd72a8fd7a3b4a445cadae103
    BUG: 1370862
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/15331
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit a5212486efb94583fde62b575508a945cdfb66e2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    cli: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ifc33762cf62259961ceb35ae9ac3cbec7094b703
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15238
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e80ada68059037282a32d296fffed18e01f836a0
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ib37642dc8d35dd1065398fc53c97de65869d5681
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15239
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 75a1f70c2ec8f1b653622400d2c1cb8e5710b4c2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Id3577872ef720787796f7bfe6772734a3b26fef0
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15286
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit f8b51bef8820142264bdca9cfe0d7106fb045c2a
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jul 29 15:03:47 2016 +0530

    md-cache: Fix wrong cache time update for xattrs
    
    In md-cache, the cache has two times:
    1. Time when the stat was last fetched for that inode
    2. Time when the xattrs were last fetched for that inode. This
    time should not be updated when only one of the xattrs is updated.
    If, its updated when one of the cached xattr is changed, it can so
    happen that the other xattrs have past their cache timeout, but are
    still served from cache.
    
    Solution:
    Do not update the xattr cache time, when one of the xattrs being cached
    is changed. With this, we may end up in cache timeout though it was
    updated recently, but it is not a harm. The other way is to have
    timeout for every xattr that is being cached. Its more complicated, and
    may be not worth it, as we have lot of lookup fops, that are overloaded to
    get all the xattrs.
    
    Change-Id: Id77e547f403fc792348f1ea56b468b9260a5a34f
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15045
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b85c648a6b236ca03494cb61b97e2e703be0950c
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jul 18 21:19:34 2016 +0530

    dht: Implement ipc fop
    
    ipc is used by md-cache to communicate the list of xattrs that
    it is caching, to the upcall xlator. Hence implement this in
    dht, such that it winds to all the bricks if the ipc op is
    GF_IPC_MDC_TARGET_UPCALL. The ips should not fail if any of
    the bricks is down, as md-cache will replay the ipc late when
    the brick comes back up.
    
    Change-Id: Ica551a550c04cbb1240c0d211fe831c2e5eb6017
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15225
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3f5273e19af2eaa7bc33c6abaf6b10850f97dcc0
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Aug 25 10:25:24 2016 +0530

    md-cache: Do not use features.cache-invalidation for both md-cache and upcall
    
    Currently, the volume set option features.cache-invalidation enables upcall
    feature on server side and md-cache cache-invalidation on client side.
    There are multiple problems that can arise from this:
    1. The scenario when user wants to, enable upcall for nfs-ganesha setup,
       but do not want to enable md-cache cache-invalidation, as the
       nfs-clients have already cached the metadata and upcall is used to
       to invalidate the nfs-client cache. In this case, users should have
       a way of disabling md-cache invalidation without disabling upcall.
    
    2. Upcall requires a op-version of GD_OP_VERSION_3_7_0, where as
       md-cache invalidation requires an op version of GD_OP_VERSION_3_9_0.
       Consider a setup where the servers are in op-version GD_OP_VERSION_3_7_0,
       and th clients are in op-version GD_OP_VERSION_3_9_0. if there is one
       single volume set option, user can enable this feature in this setup.
       But it can lead to stale xattr cache as the xattr invalidation was
       introduced in upcall only in release 3.8. Hence, we should not be
       able to enable md-cache invalidation, if all the servers and clients
       are not on opversion >= GD_OP_VERSION_3_9_0.
    
    To solve the above mentioned issues, we have seperate volume options
    for enabling md-cache invalidation and upcall. But this can lead to
    issues when user enable md-cache invalidation and forgets to enable
    upcall. Probably in the next release, these can be enables by default.
    
    Change-Id: Ie70eff97fe12fcb623eec8f4f5861ac065bf483e
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15314
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit be93ca2b9f3f1bb5d38b0fd306c19c4b3d0923f7
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:15:14 2016 -0400

    protocol/server: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I5a48055c4b0a4a07dd511ad4f2e9ef823b9c60b2
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15255
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3cc7f6588c281846f8c590553da03dd16f150e8a
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Aug 17 12:55:37 2016 +0530

    md-cache: Add cache hit and miss counters
    
    These counters can be accessed either by .meta interface
    or statedump.
    
    From meta: cat on the private file in md-cache directory.
    Eg: cat /mnt/glusterfs/0/.meta/graphs/active/patchy-md-cache/private
    [performance/md-cache.patchy-md-cache]
    stat_hit_count = 2
    stat_miss_count = 8
    xattr_hit_count = 4
    xattr_miss_count = 3
    nameless_lookup_count = 1
    negative_lookup_count = 0
    stat_invalidations_recieved = 1
    xattr_invalidations_recieved = 1
    
    Change-Id: Ib62a8822f263a9f75858b15832d0119fbe382629
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15185
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 225d8034354a233bbb9f1c6fd86b40562efd0ae9
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    quota: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ic5c1e20468d47ccb5243b8e99f946fd31eb737b8
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15250
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6c283f107b646405936520e2549510115bf2ef64
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Aug 8 17:02:37 2016 +0530

    geo-rep: Post process Data and Meta Changelogs
    
    With this patch, Data and Meta GFIDs are post processed. If Changelog has
    UNLINK entry then remove from Data and Meta GFIDs list(If stat on GFID is
    ENOENT in Master).
    
    While processing Changelogs,
    
    - Collect all the data and meta operations in a temporary database
    - Delete all Data and Meta GFIDs which are already unlinked as per Changelogs
      (unlink only if stat on GFID is ENOENT)
    - Process all Entry operations as usual
    - Process data and meta operations in batch(Fetch from Db in batch)
    - Data sync is again batched based on number of changelogs(Default 1day
      changelogs). Once the sync is complete, Update last Changelog's time as last_synced
      time as usual.
    
    Additionally maintain entry_stime on Brick root, ignore Entry ops if changelog
    suffix time is less than entry_stime. If data stime is more than entry_stime,
    this can happen only when passive worker updates stime by itself by getting
    mount point stime. Use entry_stime = data_stime in this case.
    
    New configurations:
    
    max-rsync-retries - Default Value is 10
    max-data-changelogs-in-batch - Max number of changelogs to be considered in a
    batch for syncing. Default value is 5760(4 changelogs per min * 60 min *
    24 hours)
    max-history-changelogs-in-batch - Max number of history changelogs to be
    processed at once. Default value 86400(4 changelogs per min * 60 min * 24
    hours * 15 days)
    
    BUG: 1364420
    Change-Id: I7b665895bf4806035c2a8573d361257cbadbea17
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15110
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4a3454753f6e4ddc309c8d1cb11a6e4e432c1da6
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Thu Jul 7 20:33:02 2016 +0530

    glusterd/cli: cli to get local state representation from glusterd
    
    Currently there is no existing CLI that can be used to get the
    local state representation of the cluster as maintained in glusterd
    in a readable as well as parseable format.
    
    The CLI added has the following usage:
    
     # gluster get-state [daemon] [odir <path/to/output/dir>] [file <filename>]
    
    This would dump data points that reflect the local state
    representation of the cluster as maintained in glusterd (no other
    daemons are supported as of now) to a file inside the specified
    output directory. The default output directory and filename is
    /var/run/gluster and glusterd_state_<timestamp> respectively. The
    option for specifying the daemon name leaves room to add support for
    other daemons in the future. Following are the data points captured
    as of now to represent the state from the local glusterd pov:
    
     * Peer:
        - Primary hostname
        - uuid
        - state
        - connection status
        - List of hostnames
    
     * Volumes:
        - name, id, transport type, status
        - counts: bricks, snap, subvol, stripe, arbiter, disperse,
     redundancy
        - snapd status
        - quorum status
        - tiering related information
        - rebalance status
        - replace bricks status
        - snapshots
    
     * Bricks:
        - Path, hostname (for all bricks these info will be shown)
        - port, rdma port, status, mount options, filesystem type and
    signed in status for bricks running locally.
    
     * Services:
        - name, online status for initialised services
    
     * Others:
        - Base port, last allocated port
        - op-version
        - MYUUID
    
    Change-Id: I4a45cc5407ab92d8afdbbd2098ece851f7e3d618
    BUG: 1353156
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/14873
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 7d3de1aed87ad9cd519cbc05e744f086760620c4
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Fri Aug 26 13:49:32 2016 +0530

    build: fix eventtypes.h generation
    
    make 'eventtypes.py' as dependent i.e. must build eventtypes.h
    
    Else the consequence will be like:
    error: 'EVENT_CLIENT_GRACE_TIMER_START' undeclared (first use in this function)
    
    Change-Id: I5fe2491d8d1e0c430b307026695d25475250ae79
    BUG: 1370406
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/15327
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 4786150ebe36154ec0762a951612f66f68a7e95c
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Jul 13 11:38:10 2016 +0530

    glusterd/ganesha : create export configuration file in shared storage
    
    This is the second patch which moves export related configuration for
    a volume into shared storage. The main change includes in scripts
    create-export-ganesha.sh, dbus-send.sh and the handling of volume set
    command "ganesha.enable". The manipulation of EXPORT_ID move from
    dbus-send.sh to create-export-ganesha.sh.
    
    In volume set handling following has performed
    
        stage                  |    commit
    ----------------------------------------------------------
    1.) gluster v set <volname> ganesha.enable on
    
     None			   |	create export file
    			   |    in node where cli executed,
    			   |	thne export volume via dbus
    
    2.) gluster v set <volname> ganesha.enable off
    
    unexport volume via dbus   |	remove export file from the
    			   |    shared storage
    -----------------------------------------------------------
    
    More details can be found at http://review.gluster.org/#/c/15105/
    
    Change-Id: Ia8b0e89bc8fff24b0bc5d20a538a89212894a8e4
    BUG: 1355956
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14908
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2f44a979132a43c1cf12ed2b9e9e94dbe1311c9e
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Jul 13 12:09:43 2016 +0530

    ganesha/scripts : Modifying ganesha-ha.sh for share storage related changes
    
    Currently the ganesha related configurations are "scp"ied for operations like
    add, delete, refresh-config in ganesha-ha.sh. This is no more required since
    all the conf files are available in shared storage and every node can directly
    access them from shared storage.
    
    More details can be found at http://review.gluster.org/#/c/15105/
    
    Change-Id: Ic025eb4dc246db61d6fbe969ca60214751fbf3ba
    BUG: 1355956
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14909
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a769be2c0d4227fead7348e769bd1ae49e267971
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Jul 12 17:23:03 2016 +0530

    Revert "glusterd-ganesha : copy ganesha export configuration files during reboot"
    
    This reverts commit f71e2fa49af185779b9f43e146effd122d4e9da0.
    
    Reason:
    As part of sync up node reboot this patch copies ganesha export conf file
    from a source node. This change is no more require if the export files are
    available in shared storage.
    
    Change-Id: Id9c1ae78377bbd7d5d80aa1c14f534e30feaae97
    BUG: 1355956
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14907
    Reviewed-by: soumya k <skoduri@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ca2c94bfcf96c44abb7168a9cb9c99a40e566280
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:02 2016 -0400

    glusterd: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I212abb47d9f35922b3f8253137ebab6841a53eed
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15261
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit b40893d1bb4c626cb89cd86a1ec301459be5f991
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (mgmt): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: Ia98f2934b179145398895600a3f34dbff841c3bd
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15268
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 12a3733fe82cb6e9e9704c80e75fa5efd56c3144
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (quotad-svc): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I186bdee9f7f72251f552a95a0c08a9be9aec7c83
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15272
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 40e6580ec90b249a34e3a99ad53c5861edb15aad
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (rpc-ops): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I65e6f8cdae150a796da485d9840838c4306b623b
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15275
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 6a22b7d856d63159c7e3a7d2a25e5589708b89bf
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (statedump): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I92970f7b7c2a881ba5678dbf1f0bd2bf6c68f4db
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15279
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit eed005649dabc35234cc217b89fbee92aeea0ba9
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 13:22:03 2016 -0400

    glusterd (syncop): fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I40da2a344be3da4bda2370b1ae1eb77dc00b033e
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15281
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 79e9aa5d7a24275f857d2cf23f910f63c53e9d4e
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Jun 27 15:08:25 2016 +0530

    ganesha/scripts : remove 'HA_VOL_SERVER' from the code
    
    The parameter HA_VOL_SERVER introduced intially ganesha-ha.conf to
    specify gluster server from which to mount the shared data volume.
    But after introducing new cli for the same purpose, it become
    unnecessary. The existence of that parameter can lead confussion
    to the users. This patch will remove/replace all the instance of
    HA_VOL_SERVER from the code
    
    Change-Id: I638c61dcd2c21ebdb279bbb141d35bb806bd3ef0
    BUG: 1350371
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14812
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 0343da57b51c8b83ae59743740632ec058a0d333
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Aug 25 22:20:30 2016 +0530

    glusterd: Improve mountbroker logs
    
    When Mountbroker mount fails, it was just returning
    EPERM or EACCESS without logging exact failure.
    This patch improves the logging by logging exact
    failure.
    
    Change-Id: I3cd905f95865153f70dfcc3bf1fa4dd19af16455
    BUG: 1346138
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/15319
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 0b3e4130b576c11156d6327e4cc3c9310a74c143
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Aug 5 09:03:22 2016 +0530

    feature/bitrot: Ondemand scrub option for bitrot
    
    The bitrot scrubber takes 'hourly/daily/biweekly/monthly'
    as the values for 'scrub-frequency'. There is no way
    to schedule the scrubbing when the admin wants it.
    
    Ondemand scrubbing brings in the new option 'ondemand'
    with which the admin can start scrubbing ondemand.
    It starts the scrubbing immediately.
    
    Ondemand scrubbing is successful only if the scrubber
    is in 'Active (Idle)' (waiting for it's next frequency
    cycle to start scrubbing). It is not entertained when
    the scrubber is in 'Paused' or already running.
    
    Here is the command line syntax.
    
    gluster volume bitrot <vol name> scrub ondemand
    
    Change-Id: I84c28904367eed827a7dae8d6a535c14b28e9f4d
    BUG: 1366195
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/15111
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 218c9b033fa44eacbc27d87491abd830548b362e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Aug 17 16:44:55 2016 +0200

    gfapi: do not cache upcalls if the application is not interested
    
    When the volume option 'features.cache-invalidation' is enabled, upcall
    events are sent from the brick process to the client. Even if the client
    is not interested in upcall events itself, md-cache or other xlators may
    benefit from them.
    
    By adding a new 'cache_upcalls' boolean in the 'struct glfs', we can
    enable the caching of upcalls when the application called
    glfs_h_poll_upcall(). NFS-Ganesha sets up a thread for handling upcalls
    in the initialization phase, and calls glfs_h_poll_upcall() before any
    NFS-client accesses the NFS-export.
    
    In the future there will be a more flexible registration API for
    enabling certain kind of upcall events. Until that is available, this
    should work just fine.
    
    Verificatio of this change is not trivial within our current regression
    test framework. The bug report contains a description on how to reliably
    reproduce the problem with the glusterfs-coreutils.
    
    Change-Id: I818595c92db50e6e48f7bfe287ee05103a4a30a2
    BUG: 1368842
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15191
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 76726da0e86077a8f3a59c02a47fcf2e3994218f
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Jul 12 15:44:23 2016 +0530

    glusterd/ganesha : Move ganesha-ha.conf and ganesha.conf to shared storage
    
    Currently all the ganesha related configuration files(ganesha.conf,
    ganesha-ha.conf, export files, etc) is stored locally at /etc/ganesha
    on a every node in ganesha cluster. Usually we end up in two issues by
    doing so :
    * difficult in modifiying ganesha related conf file
    * diffciult to maintain consistency of conf file across ganesha cluster
    To tackle this, we plan to move all the ganesha configuration to shared
    storage. As a first step in this patch ganesha.conf and ganesha-ha.conf
    move to shared storage. Here actual ganesha.conf will resides in shared
    stoarge and symlinks will be created in /etc/ganesha when the option
    "gluster nfs-ganesha enable" is executed and remove those during the
    "disable" part.
    
    Modified prerequisites to done before running globaloption:
    	* enable shared storage
    	* create nfs-ganesha folder in shared storage
    	* create ganesha.conf and ganesha-ha.conf in it
    
    More details can be found at http://review.gluster.org/#/c/15105/
    
    Change-Id: Ifabb6c5db50061f077a03932940190af74e2ca7f
    BUG: 1355956
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14906
    Reviewed-by: soumya k <skoduri@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f013335400d033a9677797377b90b968803135f4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Aug 24 21:01:05 2016 +0530

    cluster/ec: Use locks for opendir
    
    Problem:
    In some cases we see that readdir keeps winding to the brick that doesn't have
    any blocked locks i.e. first brick. This is leading to the client assuming that
    there are no blocking locks on the inode so it won't give away the lock. Other
    clients end up blocked on the lock as if the command hung.
    
    Fix:
    Proper way to fix this issue is to use infra present in
    http://review.gluster.org/14736 This is a stop gap fix where we start taking
    inodelks in opendir which goes to all the bricks, this will detect if there is
    any contention.
    
    BUG: 1346719
    Change-Id: I91109107a26f6535b945ac476338e9f21dc31eb9
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15309
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>

commit 6aeff261a18de1b47553f4d5c6efe5c2e86f60a2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:11:24 2016 -0400

    core: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I866d811e448067405af5b797eb9914c9c5e855cb
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15248
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit e68a8eb6c5846d7386e97b0f0f23b49c5d38a6b5
Author: Muthu-vigneshwaran <mvignesh@redhat.com>
Date:   Mon Aug 22 16:53:59 2016 +0530

    quota: add quota events
    
    The patch targets to capture quota related events which are
    important to be notified.
    
    Change-Id: Iba440d675b11c346faab4c23260899d05296d8a7
    BUG: 1368931
    Signed-off-by: Muthu-vigneshwaran <mvignesh@redhat.com>
    Reviewed-on: http://review.gluster.org/15235
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c68b561f048a02f479819b1c9cb3b5b896db18a6
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 6 12:26:29 2016 +0530

    quotad: fix potential buffer overflows
    
    This converts sprintf to gf_asprintf in following components:                                                                                                          * quotad.c
    * dht
    * afr
    * protocol/client
    * rpc/rpc-lib
    * rpc/rpc-transport
    
    Change-Id: If8a267bab3d91003bdef3a92664077a0136745ee
    BUG: 1332073
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14102
    Tested-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit afabb66f36b75db4d5aee46e694990b63f454133
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:14:33 2016 -0400

    upcall: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I887aa033f00ab67f73c7d7a7f1b3054d43bffc49
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15252
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c85a9ee3198ac63eaa035c8224e514d339bb068b
Author: yanping.gao <yanping.gao@xtaotech.com>
Date:   Wed Aug 24 06:47:49 2016 +0000

    features/locks: fix fdctx leak in locks xlators
    
    Problem:
    Locks xlators is leaking fdctx in pl_release when
    inode_ctx_get return non-zero
    
    Fix:
    This patch fixes fdctx leak in pl_release path
    
    Change-Id: Icd5c5c681b7d890e7971b3b06d4258a51d45097d
    Signed-off-by: Yanping.gao <yanping.gao@xtaotech.com>
    Reviewed-on: http://review.gluster.org/15302
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit c70f4b3af619bcdd08d57147a4ed582bdad98084
Author: Ryan Ding <ryan.ding@open-fs.com>
Date:   Wed Aug 24 00:41:13 2016 +0800

    protocol/server: readlink rsp xdr will fail while readlink got an error
    
    set gfs3_readlink_rsp.path with an empty string while error happen, to
    make xdr_gfs3_readlink_rsp happy. otherwise the original errno will be
    lost, and return an rpc internal errno instead.
    
    Change-Id: I36655b66df8b9f164e5bd21eb17244722c2f5a52
    BUG: 1369530
    Signed-off-by: Ryan Ding <ryan.ding@open-fs.com>
    Reviewed-on: http://review.gluster.org/15299
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 56a79b357e09d91305994fcc0b2d250cb9ac243d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 4 00:41:16 2016 +0530

    cluster/ec: Do multi-threaded self-heal
    
    BUG: 1368451
    Change-Id: I5d6b91d714ad6906dc478a401e614115c89a8fbb
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15083
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1edea9534dfaf95873921a77e40ae73a0d6e4c39
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Aug 22 12:43:19 2016 +0530

    quota/cli: add user driven quota events
    
    This patch targets to capture all the user driven quota related events
    which are important to be notified.
    
    Change-Id: I90c0af434363465e9dbdf6fca65ac220251d8d3c
    BUG: 1368931
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/15230
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit d1aa35c3619847922e092b7dbfb201bceea8fa33
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Aug 18 14:51:44 2016 +0530

    eventsapi: Fix disable-events issue
    
    Events related sources are not loaded in libglusterfs when
    configure is run with --disable-events option. Due to this
    every call of gf_event should be guarded with USE_EVENTS macro.
    
    To prevent this, USE_EVENTS macro was included in events.c
    itself(Patch #15054)
    
    Instead of disabling building entire directory "events", selectively
    disabled the code. So that constants and empty function gf_event is
    exposed. Code will not fail even if gf_event is called when events is
    disabled.
    
    BUG: 1368042
    Change-Id: Ia6abfe9c1e46a7640c4d8ff5ccf0e9c30c87f928
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15198
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 4aa52061a51b97c4f865b402f977b3b43f5471a7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Aug 23 12:51:57 2016 +0530

    arbiter: Fix memleak in arbiter_inode ctx
    
    Problem:
    The iattbuf ptr stored in arbiter's inode context was not freed during inode
    forget.
    
    Fix:
    Change it to a statically allocated value so that we don't have to deal
    with allocating/freeing it.
    
    Change-Id: Id1b73b8aee1fb5c4174d0734bd20e168432b1abd
    BUG: 1369331
    Reported-by: Benjamin Edgar <benedgar8@gmail.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15289
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5ce748ca45c6f2f867819400f50c9cdc12604226
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 8 13:11:29 2016 -0400

    logging: Avoid re-initing log level in io-stats
    
    If log level is already set via api or command line, initialization of
    io-stats xlator overwrites the log level to GF_LOG_INFO. This patch
    prevents re-initialization of log level if already set.
    
    Change-Id: I1f74d94ef8068b95ec696638c0a8b17d8d71aabe
    BUG: 1368882
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reported-by: Colin Lord <clord@redhat.com>
    Reviewed-on: http://review.gluster.org/15112
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 063a234e6265265606425449da1d6c2f97fbf457
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Aug 12 10:22:17 2016 +0530

    glusterd: add async events (part 2)
    
    Change-Id: I7a5687143713c283f0051aac2383f780e3e43646
    BUG: 1360809
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15153
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit 1c4c75c358df745cc73b73bf2ee08e5c5d0b598f
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Aug 17 13:08:41 2016 +0530

    build: add dependency for psmisc for fuse
    
    Add package dependency for psmisc for client package fuse
    for the killall utility. killall is referenced in the gluster
    logrotate config file.
    
    Change-Id: I4cc95fe4aaa52faf8f384b9834654d3d928c252d
    BUG: 1367665
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/15184
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 99e2438a1f42abdac316ae0f92497329733a20f3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 22 12:15:04 2016 -0400

    nfs: fix unused variable warnings/errors
    
    http://review.gluster.org/14085 fixes a/the "leak" - via the
    generated rpc/xdr headers - of pragmas that mask these warnings.
    
    However 14085 won't pass the smoke test until all the warnings are
    fixed.
    
    Change-Id: I0e872a8025c3b1b5e2aa15d8fe66248e2fd96bf1
    BUG: 1369124
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15253
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit efbae0fef5399a8826782b02140f44edaea0dac3
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Apr 12 12:26:54 2016 +0530

    snapshot/cli: Fix snapshot status xml output
    
    snap status --xml errors out if a brick is down and
    doesn't have pid. It is handled in the cli of the snap
    status where "N/A" is displayed in such a scenario.
    Handled the same in xml
    
    snap status <snapname> --xml fails as the writer is
    not initialised for the same. Using GF_SNAP_STATUS_TYPE_ITER
    instead of GF_SNAP_STATUS_TYPE_SNAP for all snap's
    status to differentiate between the two scenarios.
    
    Added testcase volume-snapshot-xml.t to check
    all snapshot commands xml outputs
    
    Change-Id: I99563e8f3e84f1aaeabd865326bb825c44f5c745
    BUG: 1325831
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14018
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 1df4a89de17e44c8c1f9b4794a7b8c2741f2bc2e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jul 27 16:28:44 2016 +0530

    snapshot: Display number of snapshots in volume info
    
    Display number of snapshots in a volume in volume info
    output. This number gets modified, with create, delete,
    and restore operations.
    
    Change-Id: Ic9b7c2b6950980f8ce75ca362998c097ea7c863d
    BUG: 1360693
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/15029
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 413594ed647400f1b39e05d4f1b12ad846e48800
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Aug 16 16:04:37 2016 +0530

    cluster/afr: Give option to do consistent-io
    
    Problem:
    When tiering/rebalance does migrations and afr with 2-way replica is in
    picture, migration can read stale data if the source brick goes down and writes
    to the destination. After this deletion of the file leads to permanent loss of
    data after migration.
    
    Fix:
    Rebalance/tiering should migrate only when the data is definitely not stale. So
    introduce an option in afr called consistent-io which will be enabled in
    migration daemons.
    
    BUG: 1306398
    Change-Id: I750f65091cc70a3ed4bf3c12f83d0949af43920a
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13425
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit eddada59f7ad3cf21463a558a5f62591f4b72c68
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Aug 22 13:59:01 2016 +0530

    tests: fix volfile_server_switch.t spurious failure
    
    1. Unnecessary self probe is removed
    2. After every probe a peer_count check is added to give the test to time finish
    handhake.
    
    Change-Id: Iab52548f8b781e7968250cd98fdbeaf02472970d
    BUG: 1368953
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15231
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c48f99ae6b4cb44415f2451277cd472a26503034
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Aug 18 12:36:37 2016 +0530

    tests: Remove explicit mention of include location
    
    This hopefully fixes the spurious failures with
    
     error: glusterfs/api/glfs.h No such file or directory
    
    build.gluster.org/job/rackspace-regression-2GB-triggered/22897/consoleFull
    
    BUG: 1365489
    Change-Id: Ic3660de810c0daee7284373bbfaed172aba86d69
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15194
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit ca18f4bccd090e98ee5342ca05d3c0f9f94e9e2c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jul 26 16:01:56 2016 +0530

    glusterd: Add async events
    
    As the eventing framework is already in the code, this patch targets to capture
    all the async glusterd events which are important to be notified to the higher
    layers which consume the eventing framework.
    
    I plan to break this work into two different patches where this patch set covers
    the first set of events.
    
    Change-Id: Ie1bd4f6fa84117b26ccb4c75bc4dc68e6ef19134
    BUG: 1360809
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15015
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rohan Kanade <rkanade@redhat.com>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>

commit fcb5b70b1099d0379b40c81f35750df8bb9545a5
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jul 28 21:29:59 2016 +0530

    cluster/afr: Prevent split-brain when bricks are brought off and on in cyclic order
    
    When the bricks are brought offline and then online in cyclic
    order while writes are in progress on a file, thanks to inode
    refresh in write txns, AFR will mostly fail the write attempt
    when the only good copy is offline. However, there is still a
    remote possibility that the file will run into split-brain if
    the brick that has the lone good copy goes offline *after* the
    inode refresh but *before* the write txn completes (I call it
    in-flight split-brain in the patch for ease of reference),
    requiring intervention from admin to resolve the split-brain
    before the IO can resume normally on the file. To get around this,
    the patch does the following things:
    i) retains the dirty xattrs on the file
    ii) avoids marking the last of the good copies as bad (or accused)
        in case it is the one to go down during the course of a write.
    iii) fails that particular write with the appropriate errno.
    
    This way, we still have one good copy left despite the split-brain situation
    which when it is back online, will be chosen as source to do the heal.
    
    Change-Id: I9ca634b026ac830b172bac076437cc3bf1ae7d8a
    BUG: 1363721
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15080
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Oleksandr Natalenko <oleksandr@natalenko.name>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit fad93c16a3fc52171f3f2b024baa5bc8b8749bee
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Aug 19 14:13:51 2016 +0530

    tests/cli: Generate SSL certificates
    
    Generate SSL certificates before enabling
    management encryption to avoid test failure.
    
    Change-Id: Iab23b36703f4653f1d5bb9d14695e4d3fa63ad61
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    BUG: 1368349
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/15202
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit e9573be8fda72092338074687ef71c9b5086b6c8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Aug 17 19:52:29 2016 +0530

    eventsapi: Bitrot events
    
    Following Bitrot Events are added
    
    BITROT_ENABLE/BITROT_DISABLE
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": EVENT_TYPE,
        "message": {
           "name": VOLUME_NAME,
        }
    }
    
    BITROT_SCRUB_THROTTLE/BITROT_SCRUB_FREQ/BITROT_SCRUB
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": EVENT_TYPE,
        "message": {
           "name": VOLUME_NAME,
           "value": OPTION_VALUE
        }
    }
    
    EVENT_BITROT_BAD_FILE
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": EVENT_TYPE,
        "message": {
           "gfid": GFID_OF_FILE,
           "brick": BRICK_ROOT,
           "path":  FILE_PATH_FROM_BRICK_ROOT (if available)
        }
    }
    
    Change-Id: I8c37b0e9db9f4f0f3d05d8f78b5521c7db0e2237
    BUG: 1367815
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/15190
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit c441a0ae5aca1f2977961afecb3236f90eb5b672
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Aug 16 12:14:43 2016 -0400

    core: use <sys/sysmacros.h> for makedev(3), major(3), minor(3)
    
    gnu glibc (libc) in Fedora 26 (rawhide) has turned off "compat" for
    makedev(), major(), and minor(3) decls.
    
    3.8.2 on F26 built with warnings, see:
    https://kojipkgs.fedoraproject.org//packages/glusterfs/3.8.2/1.fc26/data/logs/x86_64/build.log
    
    More recent builds of other packages (namely nfs-ganesha) indicate
    that these warnings would now be errors, and, will be errors when
    3.8.3 is released and built.
    
    Change-Id: I3caa0d05f5de695818753e40e754da8b40d2011c
    BUG: 1367527
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/15182
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4b01d6ea8da137f23a4372df35fcbd5dbec21d09
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Jul 18 15:17:49 2016 +0530

    quota:  change the log level from warning to info
    
    Change-Id: Icac7d87bb6c5ecc813528690e03c821bbe3789b5
    BUG: 1357463
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/14940
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 59186114f9545fda529368ee26c3cd3d88a80751
Author: Anuradha Talur <atalur@redhat.com>
Date:   Tue Aug 9 21:09:11 2016 +0530

    protocol/client: Unserialize xdata even if lookup fails
    
    Problem:
    AFR relies on xdata returned by lookup to determine if
    there are any files that need healing. This info is further
    used to optimize readdirp.
    
    In case of lookups with negative return value, client
    xlator was sending NULL xdata. Due to absence of xdata,
    AFR conservatively assumes that there are files that
    need healing, which is incorrect.
    
    Solution:
    Even in case of unsuccessful lookups, send the xdata received
    by protocol client so that higher xlators can get the info
    that they rely on.
    
    Change-Id: Id3a1023eb536180888eb2c0b39050000b76f7226
    BUG: 1366284
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/15120
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Poornima G <pgurusid@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit dd8d93f24a320805f1f67760b2d3266555acf674
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Tue Aug 16 16:46:41 2016 +0530

    glusterd: Fix volume restart issue upon glusterd restart
    
    http://review.gluster.org/#/c/14758/ introduces a check in
    glusterd_restart_bricks that makes sure that if server quorum is
    enabled and if the glusterd instance has been restarted, the bricks
    do not get started. This prevents bricks which have been brought
    down purposely, say for maintainence, from getting started
    upon a glusterd restart. However this change introduced regression
    for a situation that involves multiple volumes. The bricks from
    the first volume get started, but then for the subsequent volumes
    the bricks do not get started. This patch fixes that by setting
    the value of conf->restart_done to _gf_true only after bricks are
    started correctly for all volumes.
    
    Change-Id: I2c685b43207df2a583ca890ec54dcccf109d22c3
    BUG: 1367478
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/15183
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit a42644198431b37c9fcad2b1ff4f98b4df16c91e
Author: Ekasit Kijsipongse <ekasit.kijsipongse@nectec.or.th>
Date:   Wed Jun 24 16:12:19 2015 +0700

    stripe: Fix wrong pathinfo in striped-replicated volume
    
    Change-Id: I05b3ba6757d5b786daf7cb3a64e6ac6676e9c997
    BUG: 1200914
    Signed-off-by: Ekasit Kijsipongse <ekasit.kijsipongse@nectec.or.th>
    Reviewed-on: http://review.gluster.org/11375
    Tested-by: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 79e006b31a1e6d71f1af02176f8e8acaed7f8cd2
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Aug 2 15:30:27 2016 +0000

    socket: SSL_shutdown should be called before socket shutdown
    
    SSL_shutdown shuts down an active SSL connection. But we
    are calling this after underlying socket is disconnected.
    
    Change-Id: Ia943179d23395f42b942450dbcf26336d4dfc813
    BUG: 1362602
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/15072
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 020c39e8ab657fbf12c102186c14aca24239efd4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Aug 16 10:43:07 2016 +0530

    storage/posix: Log EEXIST failures at DEBUG log-level
    
    Change-Id: I56f160058d2e2751ca75f1f75ea8254a1b8a6bf3
    BUG: 1367258
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15161
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2b0e83e908b3be2043e92a974ba92ae942bff4d1
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Aug 2 14:51:23 2016 +0530

    md-cache: Add logging to increase debuggability
    
    Change-Id: I147d16ec3c20d3372892fdd5f62010e52f82f8bd
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15069
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 206fd324e33127d4c370007f223f8c12ab06b714
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Aug 2 16:17:36 2016 +0530

    logging: Fix per xl log level
    
    Currently per xlator loglevel setting doesn't work, due to the
    flaw in loglevel checking. Fix the same.
    
    Per xlator logging can be set using the below command:
    
    Eg: setfattr -n trusted.glusterfs.patchy-md-cache.set-log-level -v TRACE /mnt/glusterfs/0
    
    Change-Id: I8ff1d15bd5693b6f682d99bee22a4bbb5eee646c
    BUG: 1362520
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15071
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 79b9ad3dfa146ef29ac99bf87d1c31f5a6fe1fef
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Aug 5 12:18:05 2016 +0530

    cluster/afr: Bug fixes in txn codepath
    
    AFR sets transaction.pre_op[] array even before actually doing the
    pre-op on-disk. Therefore, AFR must not only consider the pre_op[] array
    but also the failed_subvols[] information before setting the pre_op_done[]
    flag. This patch fixes that.
    
    Change-Id: I78ccd39106bd4959441821355a82572659e3affb
    BUG: 1363721
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15145
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit db4e26ed71a01e5f760fbc3c7051962426f102c9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Aug 6 16:04:29 2016 +0200

    libglusterfs: add gf_get_mem_type()
    
    gfapi needs to provide a function towards applications to free memory
    that it allocated. Depending on how the application is compiled/linked,
    it could use a different memory allocator than Gluster itself. Therefore
    it is not safe for gfapi to request applications to free memory with
    'standard' free().
    
    Examples for this are Gluster allocated structures with GF_CALLOC() when
    memory accounting is enabled (the default). Some gfapi functions use
    malloc() to allocate memory as a workaround, but the free() from the
    jemalloc implementation should not be combined with the malloc() from
    glibc.
    
    Change-Id: I626cd1a60abf8965f9263290f4045d1f69fc2093
    BUG: 1344714
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15108
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit df6a127b4dbb96dd970d255635ccfeae17a38186
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Aug 10 11:24:19 2016 +0530

    libglusterfs: move alloca0 definition to common-utils
    
    ...and remove their definitons from EC and AFR.
    Also `s/alloca+memset0/alloca0` wherever it is used.
    
    Change-Id: I3b71e596d12a7d8900f5d761af6b98305c8874d5
    BUG: 1366226
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15147
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 5ef32c57f327e1dd4e9d227b9c8fd4b6f6fb4970
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Aug 11 10:10:25 2016 +0000

    glfsheal: print brick name and path even when brick is down
    
    The xml variant of heal info command does not display brick name when
    the brick is down due to a failure to fetch the hostUUID. But the non
    xml variant does. So fixed the xml variant to print the remote_host
    and remote_subvol even when the brick is down.
    
    Change-Id: I16347eb4455b9bcc7a9b0127f8783140b6016578
    BUG: 1366222
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15146
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d7c7f87ee3f442ef24cbffb30df289bb26b20a5d
Author: Muthu-vigneshwaran <mvignesh@redhat.com>
Date:   Fri Aug 5 14:05:36 2016 +0530

    rpc: fixing illegal memory access
    
    CID:1357876
    
    Change-Id: I34eee0bf0367f963ddf6e9d6b28b7d3a9af12c90
    BUG: 789278
    Signed-off-by: Muthu-vigneshwaran <mvignesh@redhat.com>
    Reviewed-on: http://review.gluster.org/15094
    Tested-by: Muthu Vigneshwaran
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3c41525001c49d7ada5f54bb3c97bf82909ee23e
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Aug 9 13:20:26 2016 +0300

    gfapi: add missing glfs_truncate
    
    Change-Id: I80b016090a4d9d86278a0a5144dd58c0cbfe9bb2
    BUG: 1365489
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Signed-off-by: Oleksandr Natalenko <oleksandr@natalenko.name>
    Reviewed-on: http://review.gluster.org/13927
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 87bb8d0400d4ed18dd3954b1d9e5ca6ee0fb9742
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Tue Aug 9 15:53:27 2016 +0530

    glusterd: Convert volume to replica after adding brick self heal is not triggered
    
    Problem:  After add brick to a distribute volume to convert to replica is not
              triggering self heal.
    
    Solution: Modify the condition in brick_graph_add_index to set trusted.afr.dirty
              attribute in xlator.
    
    Test    : To verify the patch followd below steps
              1) Create a single node volume
                 gluster volume create <DIS> <IP:/dist1/brick1>
              2) Start volume and create mount point
                 mount -t glusterfs <IP>:/DIS /mnt
              3) Touch some file and write some data on file
              4) Add another brick along with replica 2
                 gluster volume add-brick DIS replica 2 <IP>:/dist2/brick2
              5) Before apply the patch file size is 0 bytes in mount point.
    
    BUG: 1365455
    Change-Id: Ief0ccbf98ea21b53d0e27edef177db6cabb3397f
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15118
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 09b0ebf75ad2eb76002cd1801ce64f644925af45
Author: Oleksandr Natalenko <oleksandr@natalenko.name>
Date:   Tue Aug 9 14:58:08 2016 +0300

    gfapi: use const qualifier for glfs_*timens()
    
    glfs_*timens() functions have the last argument
    of struct timespec type that is supposed to be
    const. Now using glfs_*timens() in fops, implemented
    on top of FUSE library, leads to compiler-time warning
    about discarding const qualifier.
    
    Introducing const qualifier does not break ABI,
    so let's just fix it.
    
    Change-Id: Iea2a1018de7dce67f67a8229671a5978246de800
    BUG: 1365506
    Signed-off-by: Oleksandr Natalenko <oleksandr@natalenko.name>
    Reviewed-on: http://review.gluster.org/15119
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 30019e51ddefc266c939a61d26d324b7ebf3ad95
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jul 19 15:20:09 2016 +0530

    gfapi: Fix IO error caused when there is consecutive graph switches
    
    This is part 2 of the fix, the part 1 can be found at:
    http://review.gluster.org/#/c/14656/
    
    Problem:
    =======
    Consider a race between, __glfs_active_subvol() and graph_setup().
    Lets say @TIME T1:
    fs->active_subvol = A
    fs->next_subvol = B
    __glfs_active_subvol()                //under lock fs->mutex
    {
      ....
      new_subvol = fs->next_subvol       //which is B
      ....                               //Start migration from A to B
      __glfs_first_lookup(){
         ....
         unlock fs->mutex                //@TIME T2
         network fop
         lock fs->mutex
         ....
      }
      ....                                //migration continue on B
      fs->active_subvol = fs->next_subvol //which is C (explained below)
      ....
    }
    
    @Time T2, lets say in another thread, graph_setup() is called with C,
    note that at T2, fs->mutex is unlocked.
    
    graph_stup(C...)
    {
      lock fs->mutex
      ....
      if (fs->next_subvol)                // which is B
          destroy subvol (fs->next_subvol)
      ....
      fs->next_subvol = C
      ....
      unlock fs->mutex
    }
    
    Thus at the end of this,
    fs->old_subvol = A;
    fs->active_subvol = C;
    fs->next_subvol = NULL;
    which is wrong, as B completed migration, but was destroyed by
    graph_setup, and C never was migrated.
    
    Solution:
    =========
    Any new graph can be in one of the 2 states:
    - Picked for migration, migration in progress (fs->mip_subvol)
    - Not picked so far for migration (fs->next_subvol)
    graph_setup() updates fs->next_subvol only, __glfs_active_subvol()
    moves fs->next_subvol to fs->mip_subvol and fs->next_subvol = NULL
    atomically, and then once the migration is complete, make that the
    fs->active_subvol
    
    Change-Id: Ib6ff0565105c5eedb912a43da4017cd413243612
    BUG: 1343038
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14722
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 567304eaa24c0715f8f5d8ca5c70ac9e2af3d2c8
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Aug 4 16:00:31 2016 +0530

    inode: Adjust lru_size while retiring entries in lru list
    
    As part of inode_table_destroy(), we first retire entries
    in the lru list but the lru_size is not adjusted accordingly.
    This may result in invalid memory reference in inode_table_prune
    if the lru_size > lru_limit.
    
    Change-Id: I29ee3c03b0eaa8a118d06dc0cefba85877daf963
    BUG: 1364026
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/15087
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 76401324af5a5e7dc3acf8d4fbe4884d6c3f0281
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Mar 10 13:45:52 2016 +0530

    georep: tests for logrotate, create+rename, hard-link rename
    
    * log rotate
      eg. with rotate count as 2 and with the following files created
      x.log, x.log.1 and x.log.2, another iteration of logrotate results in
      the following operations to be performed
    
      x.log.2 is renamed to x.log.3
      x.log.1 is renamed to x.log.2
      x.log is renamed to x.log.1
      x.log.3 is deleted
      x.log is created   [possible gfid allocated that belonged to x.log.3]
    
      when a file is created, there's a big possibility that a gfid used
      earlier can be reassigned and reused. This causes RENAME operations
      to fail on slave nodes when logs are replayed, typically on a Georep
      restart.
      A function called logrotate_simulate has been added to tests/geo-rep.rc
      to help simulate this situation. Starting from a clean state,
      logrotate_simulate has to be called 4 times with a rotate count of 2
      to help the logs roll over and cause a delete at the end and a gfid
      reallocation.
      With the bug-fix in place, this test should not cause the Georep
      session to go into a Faulty state.
    
    * create+rename
      On log replay after Georep restart, a create+rename causes an entry
      to be created for the original file, but it cannot be linked to the
      gfid back-end since it is associated with the renamed file before
      the Georep restart.
      A function create_rename simulates the create+rename scenario and
      the function create_rename_ok tests if the dangling entry is present
      at the slave mount.
      With the bug-fix in place, a dangling entry with the original name
      should not be found at the slave mount after logs are replayed after
      a Georep restart.
    
    * hard-link rename
      This case is similar to the create+rename case except that this is
      a case of renaming hard-link to one of its other names.
      A function hardlink_rename has been added to tests/geo-rep.rc which
      simulates the creation and rename of hard-link. After a Georep session
      restart, the test function hardlink_rename_ok should not find the
      source link name on the slave.
      With the bug-fix in place, this test should not fail.
      If changelogs have been enabled on the slave as well, then the logs
      should show an UNLINK entry for the source link name, since a rename
      operation of a hard link to one of its names essentially just drops
      the source name as per the 'mv' command semantics.
    
    Change-Id: I85b196c00cf79a11bada25ef2fe5f1dc5c0c858a
    BUG: 1316389
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/13663
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 949472d7561d3bfd67d8204e433a25dbc8a596cc
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Aug 1 16:59:33 2016 +0530

    features/libgfchangelog: Log failure in gf_histroy_changelog
    
    Add error logs if gf_history_changelog fails. If requested
    changelog range is not available, log the error and exit
    instead of continuing the loop and exiting in readdir
    without logging. Also fixed the duplicate MSGID number in
    'changelog-lib-messages.h'
    
    Change-Id: Icd71b89ae23b48a71380657ba5649029c32fabfd
    BUG: 1362151
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/15064
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit f5fbf46d82e4ea5325e89459c5ad9f753f1ca66b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Aug 1 17:16:50 2016 +0530

    eventsapi: Python library for gf_event
    
    Python library to emit Events from Geo-replication or any other Python apps
    running in storage nodes.
    
    Add $LIBEXEC/glusterfs/events to Python path to use gf_event
    
    gf_event(event_type, **kwargs)
    
    For example,
    
        sys.path.insert(1, "LIBEXECDIR/glusterfs")
        from events.gf_event import gf_event
        from events import eventtypes
    
        gf_event(eventtypes.GEOREP_FAULTY,
                 volname="gv1",
                 slaveuser="root",
                 slavehost="node1",
                 slavevol="gv2")
    
    Errors will be logged in $LOGDIR/glusterfs/events.log
    
    BUG: 1362144
    Change-Id: I2af2bd77f9961975e4387006b9e99e4543e12b57
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15063
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 720b63c24b07ee64e1338db28de602b9abbef0a1
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Thu Mar 17 18:53:13 2016 +0530

    glusterd : skip non directories inside /var/lib/glusterd/vols
    
    Right now glusterd won't come up if vols directory contains an invalid entry.
    Instead of doing that with this change a message will be logged and then skip
    that entry
    
    Change-Id: I665b5c35291b059cf054622da0eec4db44ec5f68
    BUG: 1318591
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13764
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit a432e7bc80dee70a48ccc5f04f5574cdce18a3a5
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Jul 27 15:49:25 2016 +0530

    posix: Do not move and recreate .glusterfs/unlink directory
    
    Problem:
    At the time of start of a volume, it is checked if
    .glusterfs/unlink exist or not. If it does, move it
    to landfill and recreate unlink directory. If a volume
    is mounted and we write data on it till we face ENOSPC,
    restart of that volume fails as it will not be able to
    create unlink dir. mkdir will fail with ENOSPC.
    This will not allow volume to restart.
    
    Solution:
    If .glusterfs/unlink directory exist, don't move it to
    landfill. Delete all the entries inside it.
    
    Change-Id: Icde3fb36012f2f01aeb119a2da042f761203c11f
    BUG: 1360679
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/15030
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 9f22282795e20fd62b22847b92dffd0cde9cca1b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jul 19 12:55:03 2016 +0200

    build: systemd unit should not be marked executable
    
    systemd complains about the unit for GlusterD when it is executable:
    
      Configuration file /usr/lib/systemd/system/glusterd.service is marked executable. Please remove executable permission bits. Proceeding anyway.
    
    The Makefile that installs the unit has some scripted commands. These
    are not needed and standard "*dir" and "*DATA" postfixes for variables
    can be used instead.
    
    The EXTRA_DIST variable is needed for building the 'make dist' tarball
    on systems where there is no systemd. The unit would be missing from the
    tarball if it is not explicitly included.
    
    BUG: 1354489
    Change-Id: I5e72ec201036906b9b2458bc8931ccebf9a8c6b4
    Reported-by: Sergej Pupykin <ml@sergej.pp.ru>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14892
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 7ce77ea61f184d5ddae4bce4ca672fd439089eaf
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Aug 5 13:27:26 2016 +0200

    build: correct date in the %changelog
    
    Building RPMs failed for me because of an incorrect date in the
    %changelog in the .spec. It seems that rpmlint identifies is as well:
    
       $ rpmlint glusterfs.spec
       ... (snipped non critical errors)
       glusterfs.spec: E: specfile-error warning: bogus date in %changelog: Wed Jul 15 2016 Aravinda VK <avishwan@redhat.com>
    
    Changed the date in the .spec to the date of the latest version (v16) of
    the patch that adds eventing (commit 5ed781ecf).
    
    BUG: 1334044
    Change-Id: I5ef5003e227a83479f24103fc67139d7287fbc39
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/15099
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit cf51bc699646359be92969024a52c225e7ee55a1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 5 11:22:18 2016 +0000

    posix: honour fsync flags in posix_do_zerofill
    
    commit 6d994661db96cad43f26d0d1e2fba31dce9a76f5 introduced fallocate +
    FALLOC_FL_ZERO_RANGE to do posix_do_zerofill but did not do an fsync if
    O_SYNC or O_DSYNC fd flags were set. Prashant Pai pointed out performing
    fallocate(2) does not remove the necessity to do fsyncs if durability is
    desired: http://linux-fsdevel.vger.kernel.narkive.com/bDmrAUlh/fallocate-falloc-fl-punch-hole
    
    So fixed it to honour the fd flags.
    
    Change-Id: I27ae90b429185d0af29a5e632c4a8b242075a899
    BUG: 1364449
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15100
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d297d2bdfc4d5ba99c37b22dd1ae0f8e8e92fe7b
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Aug 2 11:59:42 2016 +0530

    meta: fix memory leak in meta xlators
    
    meta xlator is leaking iobuf and iobrefs in read path
    
    This patch fixes memleak in meta_default_read code path
    
    Change-Id: Ieb413267604d9870dbe6e11258fffd279a7bd7cf
    BUG: 1362397
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/15068
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>

commit 5ae0a5d1e92175c28cd5470b890e99ff4eac0673
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jul 29 12:20:11 2016 +0530

    md-cache/upcall: In case of mode bit change invalidate xattr
    
    When the mode bits are changed, the ACL entries also do get affected.
    Currently in upcall, setattr invalidates only the stat info.
    
    With this patch, if mode bits are changed, the upcall will invalidate
    all the xattrs.
    
    Change-Id: Iccda2e1a7440ee845aa5442bf51970f74d9b0862
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/15043
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2650f8b1101a1f345f310475841569feb852bf4b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Aug 4 11:51:27 2016 +0530

    tests: fix spurious failure in tests/bugs/glusterd/bug-1089668.t
    
    Instead of rebalance stop, its always better to wait for rebalance to complete
    as the former doesn't have any purpose.
    
    Change-Id: Ia1bc2a34d937a0a96543bebd257dcda619f12474
    BUG: 1363948
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15085
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 049c91565dddb622b8902ccfeb36c0d414c609e1
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue May 31 16:44:48 2016 +0530

    libglusterfs: fix glusterd statedump crash
    
    commit 3c04a91 removed setting typeStr to NULL if num_allocs is set to 0, this
    has caused this regression. Code has been put back like earlier and to avoid
    statedump printing all the NULL values check is modified to see skip the records
    if num_allocs is 0 instead of total_allocs
    
    Change-Id: Ib8bcc2fba908e88cf52b641c3f6bcba74f5e667c
    BUG: 1359190
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14987
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e4a404342cc1b53b1f16b68938f31d2b12dc9121
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Aug 1 12:11:24 2016 +0530

    xlators/ganesha : Remove the ganesha xlator code entirely from source
    
    ganesha xlator is dummy xlator which introduced as part of cli options.
    But all the ganesha related cli commands are handled from glusterd only.
    There is no point in keeping this xlator. Hence removing the same since
    it does not have any role in NFS-Ganesha intergration with gluster
    
    Change-Id: Id438d2fabd3afe7e91ae26522df8495c8e9e9308
    BUG: 1361999
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/15055
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit e068c1997314046658dd502e9118dab32decf879
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jul 29 21:55:58 2016 +0530

    mgmt/glusterd: Enable client-io-threads by default
    
    BUG: 1361678
    Change-Id: Ic013a772ffc3f8c93673bbee064ff4cc372fe128
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15051
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 3b4c9e525e931a703cc526b3fbe27ee86f2fd70a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Aug 3 12:16:43 2016 +0530

    eventsapi: Geo-replication User driven events
    
    Following Geo-replication Events are added
    
    GEOREP_CREATE/GEOREP_START/GEOREP_STOP/GEOREP_DELETE/GEOREP_PAUSE/GEOREP_RESUME
      {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": EVENT_TYPE,
        "message": {
           "master": MASTER_VOLUME_NAME,
           "slave": SLAVE_DETAILS
         }
      }
    
    GEOREP_CONFIG_SET
      {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": GEOREP_CONFIG_SET,
        "message": {
           "master": MASTER_VOLUME_NAME,
           "slave": SLAVE_DETAILS,
           "option": OPTION_NAME,
           "value": OPTION_VALUE
         }
      }
    
    GEOREP_CONFIG_RESET
      {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": GEOREP_CONFIG_RESET,
        "message": {
           "master": MASTER_VOLUME_NAME,
           "slave": SLAVE_DETAILS,
           "option": OPTION_NAME
         }
      }
    
    BUG: 1363591
    Change-Id: I78c81aabd022ebb042b3eae3c6b5a284a6c2801f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15077
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 67ebde53ea26065d41cacf054fa4337c22de5903
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Aug 2 15:19:00 2016 +0530

    cluster/afr: copy loc before passing to syncop
    
    Problem:
    When io-threads is enabled on the client side, io-threads destroys the
    call-stub in which the loc is stored as soon as the c-stack unwinds.
    Because afr is creating a syncop with the address of loc passed in
    setxattr by the time syncop tries to access it, io-threads would have
    already freed the call-stub. This will lead to crash.
    
    Fix:
    Copy loc to frame->local and use it's address.
    
    BUG: 1361678
    Change-Id: I16987e491e24b0b4e3d868a6968e802e47c77f7a
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/15070
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c3dee6d35326c6495591eb5bbf7f52f64031e2c4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 25 19:09:08 2016 +0530

    glusterd: clean up old port and allocate new one on every restart
    
    GlusterD as of now was blindly assuming that the brick port which was already
    allocated would be available to be reused and that assumption is absolutely
    wrong.
    
    Solution : On first attempt, we thought GlusterD should check if the already
    allocated brick ports are free, if not allocate new port and pass it to the
    daemon. But with that approach there is a possibility that if PMAP_SIGNOUT is
    missed out, the stale port will be given back to the clients where connection
    will keep on failing. Now given the port allocation always start from base_port,
    if everytime a new port has to be allocated for the daemons, the port range will
    still be under control. So this fix tries to clean up old port using
    pmap_registry_remove () if any and then goes for pmap_registry_alloc ()
    
    Change-Id: If54a055d01ab0cbc06589dc1191d8fc52eb2c84f
    BUG: 1221623
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15005
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit ea6a1ebe931e49464eb17205b94f5c87765cf696
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Jul 8 12:30:25 2016 +0530

    commn-HA: Add portblock RA to tickle packets post failover(/back)
    
    Portblock resource-agents are used to send tickle ACKs so as to
    reset the oustanding tcp connections. This can be used to reduce
    the time taken by the NFS clients to reconnect post IP
    failover/failback.
    
    Two new resource agents (nfs_block and nfs_unblock) of type
    ocf:portblock with action block & unblock are created for each
    Virtual-IP (cluster_ip-1). These resource agents along with cluster_ip-1
    RA are grouped in the order of block->IP->unblock and also the entire
    group maintains same colocation rules so that they reside on the same
    node at any given point of time.
    
    The contents of tickle_dir are of the following format -
    * A file is created for each of the VIPs used in the ganesha cluster.
    * Each of those files contain entries about clients connected
      as below:
    SourceIP:port_num       DestinationIP:port_num
    
    Hence when one server failsover, connections of the clients connected
    to other VIPs are not affected.
    
    Note: During testing I observed that tickle ACKs are sent during
    failback but not during failover, though I/O successfully
    resumed post failover.
    
    Also added a dependency on portblock RA for glusterfs-ganesha package
    as it may not be available (as part of resource-agents package) in
    all the distributions.
    
    Change-Id: Icad6169449535f210d9abe302c2a6971a0a96d6f
    BUG: 1354439
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/14878
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit d83105ac8537e8531b9c2210a501734b587ed8d8
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Sat Jul 23 14:33:17 2016 +0530

    gfapi: fix glfs_set_volfile_server doc
    
    Gluster supports volume file fetching over transports tcp and unix only.
    The current glfs_set_volfile_server() doc misleads by mentioning rdma,
    which is removed by this patch.
    
    More about the discussion around @
    http://www.gluster.org/pipermail/gluster-devel/2016-July/050114.html
    
    Change-Id: I08cfe262fb9a82cb341f6adbe93594c8e628b7fe
    BUG: 1359370
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14995
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8e797e6f4b95d759d5a2d6c072401c9eb5fcf68e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Aug 1 11:56:27 2016 +0530

    events: move conditional macro check USE_EVENTS inside gf_events
    
    Change-Id: I88279b11b648e676a4544bbb55c7466fbc55ffa7
    BUG: 1361983
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/15054
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 4429e842236015b51be37f3351d8f8df640744f5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jul 28 15:49:59 2016 +0530

    eventsapi: Auto generate header files during make
    
    $SRC/libglusterfs/src/eventtypes.h and $SRC/events/src/eventtypes.py are
    generated by running `python $SRC/events/eventskeygen.py`
    
    Header files generation step is added to make file itself, Now All new
    events should be added to only to $SRC/events/eventskeygen.py file.
    
    BUG: 1361094
    Change-Id: I384961ef2978ca2d0be37f288b39ac0d834bdf06
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/15035
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 07b95cf8104da42d783d053d0fbb8497399f7d00
Author: root <root@dhcp35-131.lab.eng.blr.redhat.com>
Date:   Tue Jul 5 14:33:15 2016 +0530

    glusterd: Fix memory leak in glusterd (un)lock RPCs
    
    Problem:  At the time of execute "gluster volume profile <vol> info" command
              It does have memory leak in glusterd.
    
    Solution: Modify the code to prevent memory leak in glusterd.
    
    Fix    : 1) Unref dict and free dict_val buffer in glusterd_mgmt_v3_lock_peer and
                glusterd_mgmt_v3_unlock_peers.
    
    Test   : To verify the patch run below loop to generate io traffic
             for (( i=0 ; i<=1000000 ; i++ ));
               do echo "hi Start Line " > file$i;
               cat file$i >> /dev/null;
             done
    
             To verify the improvement in memory leak specific to glusterd run below command
    
             cnt=0;while [ $cnt -le 1000 ]; do
             pmap -x <glusterd-pid> | grep total;
             gluster volume profile distributed info > /dev/null; cnt=`expr $cnt + 1`; done
    
             After apply this patch it will reduce leak significantly.
    
    Change-Id: I52a0ca47adb20bfe4b1848a11df23e5e37c5cea9
    BUG: 1352854
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/14862
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 6a29c76ae629d17d276c96b2e50f0b43e5fdf309
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Jul 7 15:55:07 2016 +0530

    features/ganesha : remove ganesha xlator from client graph
    
    The ganesha introduced in dummy xlator in the client graph, which is used
    for introducing the cli options. When the volume set command "ganesha.enable"
    ran, this xlator will add into client graph but never removed from it. In my
    opinion there is no point in adding the ganesha xlator in the client graph
    
    Change-Id: I926c4b4adf991361aa459679e275cb58246c5294
    BUG: 1349270
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14871
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 9206f5b770bbfc2cf1697f10c1e650cae35272f1
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jul 26 08:49:36 2016 -0400

    io-stats: fix translator names
    
    Change-Id: Icf5afaee8b7c704aecab7f8a8a1df9f1bc9288ce
    BUG: 1360401
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/15016
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 138bea7ea65987ca23f73c1f0c4f8868fd38cdff
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Jul 27 15:32:56 2016 +0530

    gluster man page: Add output option "--xml" to man page of gluster
    
    BUG: 1360670
    Change-Id: Ia167bb5b541a12459f70ab1205bd4ffdab8c7e65
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/15027
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1f4e41e8c2f5f4af4564caba0a08996853f089f4
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Jun 23 12:37:51 2016 +0530

    cluster/tier: dont promote if estimated block consumption > hi watermark
    
    Add test to fail promotion if estimated block consumption grows
    beyond hi watermark.
    
    Skip file migrations until next cycle if tier_get_fs_stat() fails
    in tier_migrate_using_query_file()
    
    Change-Id: Ice04572fa739c09109c4433e65965197482a7beb
    BUG: 1349284
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/14780
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 8ef81bf02c779e7d126a654bde28d319d0fa823d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Mar 31 10:54:10 2015 +0530

    Snapshot/xml:xml output for snapshot clone
    
    Snapshot clone is used to create a regular volume from snapshot.
    Currently snapshot clone is not supporting xml outout.
    
    This change introduce a xml output for snapshot clone command
    
    Change-Id: I417b480d36f9d84ee088004999b041c9619edd50
    BUG: 1207604
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10065
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 6c43efbb6b01726e450b71d274c3b45b56cc7916
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jul 25 19:58:01 2016 +0530

    tests: Fix get_pending_heal_count check in ec
    
    Continuation of http://review.gluster.org/#/c/14985.
    Also renamed tests/bugs/disperse to tests/bugs/ec for a better
    correlation to tests/basic/ec and xlators/cluster/ec
    
    Change-Id: I662b3477c12af8a0b94597769e8f00f354b1168c
    BUG: 1332054
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15006
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 6d994661db96cad43f26d0d1e2fba31dce9a76f5
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jul 28 20:42:45 2016 +0530

    posix: leverage FALLOC_FL_ZERO_RANGE in zerofill fop
    
    posix_zerofill() implements zerofilling of a given (offset,length) by
    doing a writev in a loop followed by an optional fsync on the file.
    fallocate(2) has a FALLOC_FL_ZERO_RANGE flag which does away with all
    this and provides the same result (from a userspace application point of
    view) with a single syscall. This patch attempts the zerofill with the
    latter and falls back to the former if it fails.
    
    Tested using a libgfapi based C program on XFS and observed using gdb that
    posix_zerofill()'s call to fallocate with FALLOC_FL_ZERO_RANGE was a
    success.
    
    Change-Id: I77e9b7de0d59c255f06b0c39c43a276990081727
    BUG: 1361249
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/15037
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit b20b3c68d32f6dba3f7e003f3ad9b86220d9fa25
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jul 28 22:37:38 2016 +0530

    storage/posix: Look for file in "unlink" dir IFF open on real-path fails with ENOENT
    
    PROBLEM:
    In some of our users' setups, open() on the anon fd failed for
    a reason other than ENOENT. But this error code is getting masked
    by a subsequent open() under posix's hidden "unlink" directory, which
    will fail with ENOENT because the gfid handle still exists under .glusterfs.
    And the log message following the two open()s ends up logging ENOENT,
    causing much confusion.
    
    FIX:
    Look for the presence of the file under "unlink" ONLY if the open()
    on the real_path failed with ENOENT.
    
    Change-Id: Ifb674dc7123f79fec9a9ac1ec7bf832f4df17627
    BUG: 1361300
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/15039
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1faf452818fe51fae1f07d17afab910a5e0da0cd
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Jul 22 13:11:15 2016 -0400

    io-threads: distribute work fairly among clients
    
    This is the full "queue of queues" approach where each client gets its
    own queue (per priority) and we round-robin among them.
    
    Change-Id: I73955d1b9bb93f2ff781b48dfe2509009c519ec6
    BUG: 1360402
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/14904
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 25d1bdc094a8408afc074817ec6d63c812c571f9
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jul 21 14:49:55 2016 -0400

    io-threads: remove least-rate-limit option and code
    
    This will be unnecessary, and mostly in the way, as real fairness
    guarantees are implemented.
    
    Change-Id: Ic61ec1c9e9add58385f1a4eafcfe2cc554ceefc8
    BUG: 1360402
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/14989
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: Gluster Build System <jenkins@build.gluster.org>

commit b8e8bfc7e4d3eaf76bb637221bc6392ec10ca54b
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Jul 21 18:17:21 2016 +0530

    dht/rebalance: allocate migrator thread pool dynamically
    
    Problems: The maximum number of migratior threads created was static set
    to "40". And the number of these threads get created in rebalance depends
    on the number of cores user has. If the number of cores exceeds 40, a
    crash or memory corruption can be seen.
    
    Fix: Make the migratior thread pool dynamic.
    
    Change-Id: Ifbdac8a1a396363dd75e2f6bcb454070cfdbf839
    BUG: 1359711
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/15000
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 7e00626b0dcd04b4f38d7cb1a3288ba6740ed9b6
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Jul 19 17:28:14 2016 +0530

    eventsapi: Volume Set and Reset Events
    
    Example of published data for Volume Set:
    
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": "VOLUME_SET",
        "message": {
            "name": VOLUME_NAME,
            "options": [[KEY1, VALUE1], [KEY2, VALUE2],..]
         }
    }
    
    Example of published data for Volume Reset:
    
    {
        "nodeid": NODEID,
        "ts": TIMESTAMP,
        "event": "VOLUME_RESET",
        "message": {
            "name": VOLUME_NAME,
            "option": KEY
         }
    }
    
    BUG: 1358671
    Change-Id: If30cc95396459b2a9993b3412ee6d05d27f6a86a
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14973
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ec6925a379c7bee071df1638bc2751b266cee346
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jul 22 11:40:32 2016 +0530

    snapshot/snapd: Don't display pid when snapd is offline
    
    We were previously reading the pidfile, and displaying
    the pid even if snapd daemon is not running. Now to fix
    it, we re-assign pid value to -1, if snapd is offline.
    
    Change-Id: I4baff8d489fe9380061c52aea006db90fa421cd7
    BUG: 1358244
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14981
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4e1ad2c96ea692e49fb82ce533cdc26818277e8d
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jul 25 10:26:58 2016 +0530

    tests: Fix the spurious failure in libgfapi-fini-hang.t
    
    RCA:
    After running libgfapi-fini-hang, there is a EXPECT_WITHIN which waits
    for PROCESS_UP_TIMEOUT(20s), for the process libgfapi-fini-hang to die.
    Currently EXPECT_WITHIN is returning success even if the process
    libgfapi-fini-hang is alive. This is because "pgrep libgfapi-fini-hang"
    in check_process() is returning 1(no process alive) even if the process
    is alive. Man page of pgrep says "The process name used for matching is
    limited to the 15 characters". Hence changing the name of executable from
    libgfapi-fini-hang to gfapi-hang, so that it falls within the limit.
    
    As explained the failure is not because there was a hang(logs show that
    glfs_set_volfile_server was still executing), but because EXPECT_WITHIN
    was not really waiting. And hence there was a race between the execution
    of the process libgfapi-fini-hang and the kill.
    
    Change-Id: I257715865e0d3e5a14f83d1e235c01899e1cae68
    BUG: 1358594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14997
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>

commit 6e78a0dda9343d75674a12b7e1a1e8e59e17c78c
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Jul 27 14:23:23 2016 +0530

    gfapi: deprecate rdma support for management connections
    
    RDMA transport was never supported for management connection before, but
    glfs_set_volfile_server() allowed rdma transport type due to lack of defense
    code and the glusterfs_mgmt_init() code silently fall back to tcp with out
    any warnings, this gave a chance for assumtions that mgmt connection also
    supports rdma along with tcp and unix.
    
    This patch deprecates the rdma support by warning at its usage.
    
    Change-Id: I0ad99d9851e05ff84ba4b6a3534a984bcc7e2ed7
    BUG: 1360647
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/15026
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit ae4f59f929be36b40c9f8e20804b6bc4564cc7a3
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jul 27 15:58:35 2016 +0530

    tests: Fix tests/bitrot/bug-1244613.t
    
    Wait for gluster nfs to initialize before
    attempting the nfs mount.
    
    Change-Id: I4bd9579ad5368935cf62632a5d612f89fce5979f
    BUG: 1360682
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/15028
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 64ae3907818ad3cdaed1a1454cb44f684c9fcffd
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed May 25 13:54:13 2016 -0400

    cluster/tier:  fix statfs for dht/tiered volumes
    
    Return the correct size of the tiered volume in statfs. It should
    be the size of the cold tier, not the sum of the hot and cold tier,
    because the hot tier is a cache and not an extension of the volume's
    capacity. The number of free blocks, etc is the cold tier's capacity
    subtracted by the sum of utilization on the hot and cold tiers. Note
    if both tiers are part of the same file system this must be accounted
    for as well.
    
    The patch also fixes a pre-existing bug in the DHT/tier
    translators. If statfs was taken on a file, the code only calculated
    free space on the cached subvolume, not all subvolumes in the replica
    group. With the fix, this is corrected, except in the case
    where quota is used with the deem-statfs option set to "on".
    
    Change-Id: I2b8bcb4511edf83f12130960aad0a609fcf8f513
    BUG: 1339689
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/14536
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit dbc8dac5c357a28aeba17894f8b02faa2af2a792
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Aug 14 11:13:54 2015 +0200

    README: improve readability and add a clickable link
    
    It is easier to have a link that can be clicked.
    
    Change-Id: Id0f75b3e68ca358c218e7f1f00769545dab0c058
    BUG: 1193929
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11922
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 98280290cd4a483f72c8c4d614eb826117383e1d
Author: Prashanth Pai <ppai@redhat.com>
Date:   Mon May 30 11:56:17 2016 +0530

    tier: Suppress warning when tiering is disabled
    
    Suppress -Wunused-function compile time warnings when tiering is
    disabled with --disable-tiering.
    
    BUG: 1193929
    Change-Id: I396e03631606ce60a953ed5e124986ae2c803abd
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/14638
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>

commit afd27ad5e957fcb88d8b84711c16e311888b9077
Author: Poornima G <pgurusid@redhat.com>
Date:   Sat Jul 23 19:25:46 2016 +0530

    extras: Change failed_tests.py to generate html output
    
    Running failed-tests.py as a job in jenkins to send the regression
    report periodically to gluster-devel. Hence, clean up some of the
    argument parsing code and add support for html display of the output
    
    Change-Id: Ic6daf87e3fa9b0ef8401d68cbd0010f166ea4961
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14996
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Nigel Babu <nigelb@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit d1e2054974c5933771fe0e5626e2cd04bccc757a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Jul 12 10:07:48 2016 +0530

    afr: some coverity fixes
    
    Thanks to Krutika for a cleaner way to track inode refs in
    afr_set_split_brain_choice().
    
    Change-Id: I2d968d05b815ad764b7e3f8aa9ad95a792b3c1df
    BUG: 1355604
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14895
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a56635c0c44af63672b0a6fadc1a02f98eb6b251
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Sat Jul 23 06:59:09 2016 +0800

    libglusterfs: add "_" to the name of parameter in macro code
    
    Change-Id: I3daf10e2099a36f8ca8df35067ef9206f08fe7ef
    BUG: 1358922
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/14990
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 934cae8781bf04f086f8302ef88542ee6604a576
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Jul 25 09:05:20 2016 -0400

    infra: remove anti-typedef check
    
    Linus's dislike of typedefs is one of his most idiosyncratic positions,
    at odds with the mainstream of software engineering and practice.
    There's no reason that quirk should have been imposed on this project,
    which was done by fiat when we adopted a style checker written for a
    very different audience and environment.
    
    Change-Id: Ic08b0d14a0130ee88c3f60dcac07670d91004c2b
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/15004
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d2bd17e5a53d0ffa375df1a5ad957556be2f2b83
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 6 14:30:08 2016 +0530

    dict: Don't expose get_new_dict/dict_destroy
    
    get_new_dict/dict_destroy is causing confusion where, dict_new/dict_destroy or
    get_new_dict/dict_unref are used instead of dict_new/dict_unref.
    
    Change-Id: I4cc69f5b6711d720823395e20fd624a0c6c1168c
    BUG: 1296043
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13183
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 558a45fa527b01ec81904150532a8b661c06ae8a
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Jun 17 17:52:56 2016 +0530

    cluster/ec: Handle absence of keys in some callback dict
    
    Problem: This issue arises when we do a rolling update
    from 3.7.5 to 3.7.9.
    For 4+2 volume running 3.7.5, if we update 2 nodes
    and after heal completion  kill 2 older nodes, this
    problem can be seen. After update and killing of
    bricks, 2 nodes will return inodelk count key in dict
    while other 2 nodes will not have inodelk count in dict.
    This is also true for get-link-count.
    During dictionary match , ec_dict_compare, this will
    lead to mismatch of answers and the file operation
    on mount point will fail with IO error.
    
    Solution:
    Don't match inode, entry and link count keys while
    comparing two dictionaries. However, while combining the
    data in ec_dict_combine, go through all the dictionaries
    and select the maximum values received in different dicts
    for these keys.
    
    Change-Id: I33546e3619fe8f909286ee48fb0df2009cd3d22f
    BUG: 1347686
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/14761
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit fc2a0f5eb8caae4f4fd0c023619954ed4b6ca760
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Jul 20 15:10:05 2016 +0530

    features/ctr: Check for NULL local
    
    This is a defensive fix to prevent a crash reported
    during a rename operation. This is not reproducible
    under normal circumstances.
    
    This patch also moves ctr-messages.h to the src dir
    of the changetimerecorder xlator.
    
    Change-Id: I46eb926d67bf4c19387c8b26e354c635a5fb284c
    BUG: 1358196
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/14964
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0d3e0da4fea3fa3acaab92a58d0b7c26bae765ff
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Jul 25 16:23:06 2016 +0530

    tests: Moving ./tests/bugs/snapshot/bug-1316437.t to bad test
    
    Moving ./tests/bugs/snapshot/bug-1316437.t to bad test, while mulling
    over the pros and cons of the fix. Will update the bug, as we go.
    Sending this patch to unblock master.
    
    Change-Id: Ia863312913686b4fa0ee0b63da13aedc0439a835
    BUG: 1359717
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/15001
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bb48eb46910085928efbd7fb491c5b2db25bba98
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Jul 22 13:15:58 2016 +0530

    gfapi/upcall: Fix a ref leak
    
    inode_find (used to create the handle) takes a reference
    of the inode. This needs to be un'refernced to avoid leak.
    
    Change-Id: I22f03577a8f1d9608cfc62d57202cfc4c2ba12b3
    BUG: 1358608
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/14984
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>

commit dac9ec0c015e748c0e7909496cdc636831975e0e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jul 22 20:24:51 2016 +0530

    tests: Remove hard coding in get_aux
    
    Change-Id: Ie007d8006a2f2be0187f0c73d46ec6dda2a68a6b
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14988
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b1559c2d1cfcff76df5870563a84cc22c752cc58
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jul 22 07:48:27 2016 +0530

    tests: Fix spurious failures with split-brain-favorite-child-policy.t
    
    Problem:
    It is not guranteed that the self-heal daemon would apply the new option
    as soon as volume set is executed because all the command gurantees is that
    the process is notified of the change in volfile. Shd still needs to fetch
    volfile and reconfigure. If the next volume heal command comes even before
    the reconfigure happens, then the heal won't happen.
    
    Fix:
    Restart shd to make sure it has the option loaded with new value.
    
    BUG: 1358976
    Change-Id: I3ed30ebbec17bd06caa632e79e9412564f431b19
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14978
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c5bf5d98594a4237a72cf0d3c72925d5a5aa0f69
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jul 22 13:58:22 2016 +0530

    tests: Fix pending-heal-count checks
    
    EXPECT_WITHIN takes regular expression to match the count,
    so even when there are say 10 entries to heal, it would
    think that the heal is complete. Fixed checking
    pending heal count with correct regex.
    
    Thanks to Xavi for finding this problem.
    
    Change-Id: Ic593d22468b2b586bfca864962ffa0eda96b1d1f
    BUG: 1332054
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14985
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1c9b229a860908ffc0c0134450c9218bc8079c22
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jul 22 10:25:49 2016 +0530

    tests: Fix timing issue in ec.t
    
    Problem:
    Because of timing issue sometimes the mount is unmounted
    even before the version is updated, this is leading to
    not triggering heals.
    
    Fix:
    One way to fix this would be to increate 'sleep 2' to 'sleep 10'
    but that would slow things down. I changed the way ec learns
    it needs xattr healing so that it triggers heals even when the
    xattrs are not marked correctly.
    
    Change-Id: I1c82041166443ae7079dd99b89ea2ed170233ba3
    BUG: 1359001
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14980
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 89dee8b46e126bc1d7541da90fa60844aa83451e
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jul 21 12:14:27 2016 +0530

    glfs/upcall: entries should be removed under mutex lock
    
    During poll, upcall entries should be removed from the
    upcall_list only under upcall_list_mutex lock. Otherwise
    it could result in the list corruption if there are entries
    being added during poll resulting in memory leak.
    
    Also addressed a probable leak during any failures with upcall
    entry addition.
    
    Change-Id: I468183f961eb6faed9a0a1bcb783705f711641fc
    BUG: 1358608
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/14972
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 637ce9e2e27e9f598a4a6c5a04cd339efaa62076
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 7 11:45:07 2016 +0530

    changelog/rpc: Fix rpc_clnt_t mem leaks
    
    PROBLEM:
       1. Freeing up rpc_clnt object might lead to crashes. Well,
          it was not a necessity to free rpc-clnt object till now
          because all the existing use cases needs to reconnect
          back on disconnects. Hence timer code was not taking
          ref on rpc-clnt object.
    
          Glusterd had some use-cases that led to crash due to
          ping-timer and they fixed only those code paths that
          involve ping-timer.
    
          Now, since changelog has an use-case where rpc-clnt
          need to be freed up, we need to fix timer code to take
          refs
    
       2. In changelog, because of issue 1, only mydata was being
          freed which is incorrect. And there are races where
          rpc-clnt object would access the freed mydata which
          would lead to crashes.
    
          Since changelog xlator resides on brick side and is long
          living process, if multiple libgfchangelog consumers
          register to changelog and disconnect/reconnect mulitple
          times, it would result in leak of 'rpc-clnt' object
          for every connect/disconnect.
    
    SOLUTION:
       1. Handle ref/unref of 'rpc_clnt' structure in timer
          functions properly.
       2. In changelog, unref 'rpc_clnt' in RPC_CLNT_DISCONNECT
          after disabling timers and free mydata on RPC_CLNT_DESTROY.
    
    RPC SETUP IN CHANGELOG:
       1. changelog xlator initiates rpc server say 'changelog_rpc_server'
       2. libgfchangelog initiates one rpc server say 'libgfchangelog_rpc_server'
       3. libgfchangelog initiates rpc client and connects to 'changelog_rpc_server'
       4. In return changelog_rpc_server initiates a rpc client and connects back
          to 'libgfchangelog_rpc_server'
    
    REF/UNREF HANDLING IN TIMER FUNCTIONS:
    Let's say rpc clnt refcount = 1
       1. Take the ref before reigstering callback to timer queue
               >>>>  rpc_clnt_ref (say ref count becomes = 2)
       2. Register a callback to timer say 'callback1'
       3. If register fails:
               >>>> rpc_clnt_unref (ref count = 1)
       4. On timer expiration, 'callback1' gets called. So unref rpc clnt at the end
          in 'callback1'. This is corresponding to ref taken in step 1
               >>>> rpc_clnt_unref (ref count = 1)
       5. The cycle from step-1 to step-4 continues....until timer cancel event happens
       6. timer cancel of say 'callback1'
               If timer cancel fails:
                     Do nothing, Step-4 would have unrefd
               If timer cancel succeeds:
                     >>>> rpc_clnt_unref (ref count = 1)
    
    Change-Id: I91389bc511b8b1a17824941970ee8d2c29a74a09
    BUG: 1316178
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13658
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b76ac27f6fe2a183c350f236e3da16f38189e4a8
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Fri Jul 22 04:09:15 2016 +0800

    core: coverity, NULL potinter check
    
    iobuf_get_page_aligned should check the return pointer
    after calling iobuf_get2.
    
    CID: 1357868
    
    Change-Id: I3aa5b09bce2225aa70cf3c60a6b6f4e4eca1dee6
    BUG: 1358936
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/14976
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 99e1686638c26d1a3bb7d66c8a7fd3d93d07e75d
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Thu Jul 21 21:36:23 2016 -0400

    jbr: coverity, resource leak
    
    Change-Id: I62428808ce52569ff0298b0fcdd07cbaec1621dc
    BUG: 1358944
    CID: 1357871
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/14977
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 370197f6e8413c0c4c13571f1c5b613bfa1e50d5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 21 08:12:04 2016 +0200

    md-cache: fix indention to silence Coverity
    
    Coverity complains about the incorrect indention:
    
        *** CID 1357867:  Control flow issues  (NESTING_INDENT_MISMATCH)
        ...
        2566                     if (conf->mdc_invalidation)
        2567                             ret = mdc_invalidate (this, data);
        >>>     CID 1357867:  Control flow issues  (NESTING_INDENT_MISMATCH)
        >>>     This 'if'  statement is indented to column 25, as if it were nested within the preceding parent statement, but it is not.
        2568                             if (default_notify (this, event, data) != 0)
        2569      	                         ret = -1;
        2570                     break;
        ...
    
    Even when md-cache does not have cache-invalidation on, we need to pass
    the upcall to the next xlator.
    
    Change-Id: I6d2a174eb54e3df270920aae9673b5010c235f25
    CID: 1357867
    BUG: 1211863
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14971
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f4bbe515097e0149c78c1fc1bae9fb90928e7cd8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jul 20 11:36:31 2016 +0530

    tests: Fix spurious failure of br-stub.t
    
    The nfs mount fails occasionally in ./tests/bitrot/br-stub.t.
    The reason being nfs mount is attempted before the gluster
    nfs has come up. It is a race and hence happens occasionally.
    The patch fixes it by waiting for nfs server to come up
    before mount.
    
    Thanks skoduri@redhat.com for root causing it.
    
    Change-Id: I3adbf2363514635785c02b1478733095ad0b74cf
    BUG: 1358114
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14960
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8c47b19fc057f08c47444ef557503e610c707128
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jul 12 15:21:23 2016 +0530

    feature/bitrot: Ignore files with sticky bit set
    
    Scrubber scrubs entries in backend. It is scrubbing files with sticky
    bit as well. This might include linkfiles which should be skipped.  This
    patch adds the check to ignore linkfiles during scrub.
    
    Change-Id: Ic21367b37770d391326c55c659491a1e5a82335b
    BUG: 1355706
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14903
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: NetBSD Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ff49529be352c1d491f22cf0261665e6313beee2
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jul 12 19:46:57 2016 +0530

    extras: fix failed_tests.py to work
    
    The text in the regression console output, now has the following prepended:
    "<span class="timestamp"><b>08:27:48</b> </span>"
    with every line. Hence changing all the instances where the entire line
    was compared, to find the pattern in the line.
    
    Also, another usability change to take centos/netbsd as an argument
    instead of the regression link.
    
    Change-Id: I1648ab90fa6d34bb8b82a0a33401c5a2ecb86426
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14914
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ec72746af0ee94c7b9b96fa7685490b02583f393
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Jul 19 15:41:54 2016 +0530

    eventsapi: Fix make install issue second time
    
    If Symlink file $SBIN/gluster-eventsapi is not deleted,
    make install was failing when run second time(Without uninstall)
    
    With this patch, Symlink deleted before installing new symlink.
    
    BUG: 1357821
    Change-Id: I65e636f7b48ba9e81177f56c720ffc27e1f95fb3
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14954
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 0a8b85e3a8228c399dde807c3ca781a452a1fc90
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jun 17 01:27:31 2016 -0400

    tests: Enable all gfapi test cases
    
    Change-Id: I32bfec4af91348d96dc3e81a9d5c9cad599f821b
    Bug: 1358594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14748
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit dcf75f7dac091cdb8ab0af2e8f2ca30f6272f8d1
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Thu Jul 14 14:25:35 2016 +0530

    glusterd/geo-rep: fix memory  leak and minor fixes
    
    Fix for memory leak and other issues revealed by coverity.
    
    Change-Id: Ib66eaa3a1a086d4b487534cebc56af5e1f9bf576
    BUG: 1356528
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/14925
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit be69510e670cb5ee893399ca1d7e7d2a60a9483c
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jul 20 15:04:01 2016 +0530

    tests: Fix spurious failure of tests/bugs/glusterd/bug-1111041.t
    
    On a faster machine the ps check was returning two pids,
    including the glusterfsd process's pid, right after that,
    process forked. Hence removing that ps, as for the scope
    of this test, verifying the snapd pid from the status
    command itself is enough.
    
    Change-Id: I8bd8fc4ea406d96e3a47f952cfe44560b615dbe6
    BUG: 1358195
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14963
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit d724a87e682cf14a3f2a85888cad5c5db203fb5b
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Jul 15 14:12:31 2016 +0530

    rpc/socket.c : Modify socket code to avoid fd leak in case of socket_poller thread
    
    Update socket code to avoid fd leak in case of socket_poller thread.
    
    Change-Id: Ifa9718fbaf065988a299cda7ba0282dfd6b10a32
    BUG: 1356888
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/14929
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 1f97d7101b3313ce647638310e1028da8dac6785
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Dec 11 05:12:07 2015 -0500

    md-cache: Add cache invalidation support to invalidate the meta data cache
    
    Problem:
    md-cache currently updates its stat in cbks of selected fops.
    The default cache time is 1 second, if this is increasd to reap the
    benefits of caching, we may end up with stale cache for long time,
    as there is no logic yet to notify md-cache of backend changes by
    another client.
    
    Solution:
    Use the existing upcall mechanism to invalidate the cache.
    For this feature to work, "features.cache-invalidation" volume
    option should be enabled.
    
    This patch as is doesn't improve any performance, the benifit of the
    patch is that it provides coherency for stat cache, hence the cache
    timeout can be quite longer which in turn can improve the performance.
    
    Change-Id: I2dbb0afa7b5e4a5a248f910188e0918e02f18692
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/12951
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 1929141da34d36f537e9798e3618e0e3bdc61eb6
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jul 14 12:30:12 2016 +0530

    feature/bitrot: Fix scrub status with sharded volume
    
    Bitrot scrubs each shard entries separately. Scrub
    statistics was counting each shard entry which is
    incorrect. This patch skips the statistics count
    for sharded entries.
    
    Change-Id: I184c315a4bc7f2cccabc506eef083ee926ec26d3
    BUG: 1356851
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14927
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d90307c1b0245e0e6a39044a28819cde520a100c
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Jul 18 11:12:43 2016 +0530

    xlator/trash : append '/' at the end in trash_notify_lookup_cbk
    
    In the notify function in trash xlator, a lookup is performed
    to obtain path of old trash directory. The result usually contains
    path without '/' at the end. The trash xlator maintains expects
    '/' at the end for the values such as 'old trash dir' and
    'new trash dir'. Otherwise certian checks in the code will fail.
    
    Change-Id: I89e02e4b249314fb6536297f959865feee182c83
    BUG: 1357397
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14938
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7bf882ed1757f8b01d18d35ef869ed2cd49f1b2f
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon May 2 19:06:47 2016 +0530

    geo-rep: address potential leak of memory
    
    fix memory leak reported by clang analyzer:
    gsyncd.c:411:17: warning: Potential leak of
                     memory pointed to by 'argv'
                     in main()
    
    
    Change-Id: I179fb1c095cf4d331b5910df6388dc724cb4ac96
    BUG: 1332419
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14151
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 1b228d3d489cada1c3c9f5fdbb882e7dbc25a091
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jul 16 16:36:22 2016 +0200

    build: fix sprintf format for uint64_t in gf_worm_serialize_state()
    
    When building on 32-bit architectures, the following warning gets
    reported:
    
        worm-helper.c: In function 'gf_worm_serialize_state':
        worm-helper.c:219: warning: format '%ld' expects type 'long int', but argument 4 has type 'uint64_t'
        worm-helper.c:219: warning: format '%ld' expects type 'long int', but argument 5 has type 'uint64_t'
    
    The format string "%ld" depend on the architecture. If the type is very
    specific (here unint64_t), the dynamicness of "%ld" is not correct.
    There are macros for these fixed types in <inttypes.h> and even some
    more in "logging.h" from libglusterfs.
    
    BUG: 1198849
    Change-Id: I63eeb9c8e4d7b292ce0c9333938ca365db0823fc
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14934
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 5ed781ecf531b7916e51c174426e222dab717fb8
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu May 5 18:34:41 2016 +0530

    eventsapi: Gluster Eventing Feature implementation
    
    [Depends on http://review.gluster.org/14627]
    
    Design is available in `glusterfs-specs`, A change from the design
    is support of webhook instead of Websockets as discussed in the design
    
    http://review.gluster.org/13115
    
    Since Websocket support depends on REST APIs, I will add Websocket support
    once REST APIs patch gets merged
    
    Usage:
    Run following command to start/stop Eventsapi server in all Peers,
    which will collect the notifications from any Gluster daemon and emits
    to configured client.
    
        gluster-eventsapi start|stop|restart|reload
    
    Status of running services can be checked using,
    
        gluster-eventsapi status
    
    Events listener is a HTTP(S) server which listens to events emited by
    the Gluster. Create a HTTP Server to listen on POST and register that
    URL using,
    
        gluster-eventsapi webhook-add <URL> [--bearer-token <TOKEN>]
    
    For example, if HTTP Server running in `http://192.168.122.188:9000`
    then add that URL using,
    
        gluster-eventsapi webhook-add http://192.168.122.188:9000
    
    If it expects a Token then specify it using `--bearer-token` or `-t`
    
    We can also test Webhook if all peer nodes can send message or not
    using,
    
        gluster-eventsapi webhook-test <URL> [--bearer-token <TOKEN>]
    
    Configurations can be viewed/updated using,
    
        gluster-eventsapi config-get [--name]
        gluster-eventsapi config-set <NAME> <VALUE>
        gluster-eventsapi config-reset <NAME|all>
    
    If any one peer node was down during config-set/reset or webhook
    modifications, Run sync command from good node when a peer node comes
    back. Automatic update is not yet implemented.
    
        gluster-eventsapi sync
    
    Basic Events Client(HTTP Server) is included with the code, Start
    running the client with required port and start listening to the
    events.
    
        /usr/share/glusterfs/scripts/eventsdash.py --port 8080
    
    Default port is 9000, if no port is specified, once it started running
    then configure gluster-eventsapi to send events to that client.
    
    Eventsapi Client can be outside of the Cluster, it can be run event on
    Windows. But only requirement is the client URL should be accessible
    by all peer nodes.(Or ngrok(https://ngrok.com) like tools can be used)
    
    Events implemented with this patch,
    - Volume Create
    - Volume Start
    - Volume Stop
    - Volume Delete
    - Peer Attach
    - Peer Detach
    
    It is easy to add/support more events, since it touches Gluster cmd
    code and to avoid merge conflicts I will add support for more events
    once this patch merges.
    
    BUG: 1334044
    Change-Id: I316827ac9dd1443454df7deffe4f54835f7f6a08
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14248
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 386340967926fa062e2c1eee4784f951846167b3
Author: Muthu-vigneshwaran <mvignesh@redhat.com>
Date:   Mon Jul 18 16:56:38 2016 +0530

    libglusterfs : update correct memory segments in glfs-message-id
    
    Change-Id: I669d6674e21d1524a2934edba8a77b70c77ef0f4
    BUG: 1357490
    Signed-off-by: Muthu-vigneshwaran <mvignesh@redhat.com>
    Reviewed-on: http://review.gluster.org/14942
    Tested-by: Muthu Vigneshwaran
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit a2e5ad1dfec6b989a9e07967297ae6e13061fb93
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Jul 14 11:50:42 2016 -0400

    Update MAINTAINERS
    
    Changes to reflect the current state of maintainers.
    
    Change-Id: Ic3d0b61ef4bf334a7434dcc9d8ef867774306eae
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/14926
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7abed939a7cc61880aed7547f12ace80e6128170
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 18 12:54:38 2016 +0530

    glusterd: search for free port from base_port
    
    When a volume is deleted, the freed up ports are never considered for further
    allocation since pmap_registry_alloc () always starts scanning from last_alloc.
    So in use cases where gluster volumes are frequently created and deleted
    managing ports become nightmare as for every new volume creation ports need to
    be opened up by the admin based on the volume topology.
    
    Solution: Instead of scanning from last_alloc, pmap_registry_alloc () always
    starts from base_port now. What that means is glusterd will always try to find
    out the ports which have been freed from earlier volumes and reallocate them for
    the newer ones. There could be possibilities that when a volume is stopped and
    started back their brick ports are changed which is completely acceptible IMHO.
    
    Change-Id: I99ccc11732b6a75527fcb6abafaf249ed02b3b78
    BUG: 1221623
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14939
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit beeaa074611433d6c650823624569f90025160d3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 27 14:56:04 2016 +0530

    Revert "tests: remove tests for clear-locks"
    
    This reverts commit 0086a55bb7de1ef5dc7a24583f5fc2b560e835fd.
    
    As part of Richard's patch for lock-revocation feature this bug
    is completely fixed (I think at least ;-) ). So bringing these
    back so that we will find out if there are anymore things we need
    to address in this code path.
    
    BUG: 1350867
    Change-Id: If1440fc83b376576ae1a77b1156188a6bf53fe3a
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14817
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 713d7d080df51bf19ce29cf5d682bc006e1c3a19
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Jul 1 15:54:07 2016 +0530

    features/bitrot: Move throttling code to libglusterfs
    
    Since throttling is a separate feature by itself,
    move throttling code to libglusterfs.
    
    Change-Id: If9b99885ceb46e5b1865a4af18b2a2caecf59972
    BUG: 1352019
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14846
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 98b95fc97e896c84de462445c48565a73b2144c2
Author: mvignesh@redhat.com <mvignesh@redhat.com>
Date:   Wed Jul 13 15:30:19 2016 +0530

    quota: corrected minor spelling mistakes in quota src files
    
    Change-Id: I85420ca5f89ce9d576a81be22d8c2003f109b476
    BUG: 1356032
    Signed-off-by: mvignesh@redhat.com <mvignesh@redhat.com>
    Reviewed-on: http://review.gluster.org/14917
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bc0b106f0ae8ecd336c7689917e46bc2685603c8
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jul 15 18:49:32 2016 +0530

    cli/xml: Fix wrong XML format in volume get command
    
    Without this Patch,
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volGetopts>
        <count>258</count>
        <Option>cluster.lookup-unhashed</Option>
        <Value>on</Value>
        <Option>cluster.lookup-optimize</Option>
        <Value>off</Value>
        <Option>cluster.min-free-disk</Option>
        <Value>10%</Value>
        <Option>cluster.min-free-inodes</Option>
        <Value>5%</Value>...
    
    With this patch,
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volGetopts>
        <count>258</count>
        <Opt>
            <Option>cluster.lookup-unhashed</Option>
            <Value>on</Value>
        </Opt>
        <Opt>
            <Option>cluster.lookup-optimize</Option>
            <Value>off</Value>
        </Opt>
        <Opt>
            <Option>cluster.min-free-disk</Option>
            <Value>10%</Value>
        </Opt>
        <Opt>
            <Option>cluster.min-free-inodes</Option>
            <Value>5%</Value>
        </Opt>...
    
    BUG: 1302277
    Change-Id: I6c5a040f659f2244ddcd47c57882b4f300cbe52f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14931
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 561746080b0b7154bfb3bdee20d426cf2ef7db17
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 7 08:51:08 2016 -0400

    core: use readdir(3) with glibc, and associated cleanup
    
    Starting with glibc-2.23 (i.e. what's in Fedora 25), readdir_r(3)
    is marked as deprecated. Specifically the function decl in <dirent.h>
    has the deprecated attribute, and now warnings are thrown during the
    compile on Fedora 25 builds.
    
    The readdir(_r)(3) man page (on Fedora 25 at least) and World+Dog say
    that glibc's readdir(3) is, and always has been, MT-SAFE as long as
    only one thread is accessing the directory object returned by opendir().
    World+Dog also says there is a potential buffer overflow in readdir_r().
    World+Dog suggests that it is preferable to simply use readdir(). There's
    an implication that eventually readdir_r(3) will be removed from glibc.
    POSIX has, apparently deprecated it in the standard, or even removed it
    entirely.
    
    Over and above that, our source near the various uses of readdir(_r)(3)
    has a few unsafe uses of strcpy()+strcat().
    
    (AFAIK nobody has looked at the readdir(3) implemenation in *BSD to see
    if the same is true on those platforms, and we can't be sure of MacOS
    even though we know it's based on *BSD.)
    
    Change-Id: I5481f18ba1eebe7ee177895eecc9a80a71b60568
    BUG: 1356998
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14838
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 73b9ede7e115fab245b0f59d18e4d6cc4d297cec
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Sat Jul 16 21:43:58 2016 -0400

    core: add a basis function to reduce verbose code
    
    Change-Id: Icebe1b865edb317685e93f3ef11d98fd9b2c2e9a
    BUG: 1357226
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/14936
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 939184c6709db1391d38c892e098c20519d746cc
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 18 12:23:29 2016 +0530

    glusterd: fix compilation warning
    
    glusterd-utils.c: In function 'glusterd_handle_replicate_brick_ops':
    glusterd-utils.c:11402:9: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
             if (dict_get_str (THIS->options, "transport.socket.bind-address",
             ^~
    glusterd-utils.c:11406:17: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'if'
                     snprintf (logfile, sizeof (logfile),
    
    Solution : indentation does the magic :)
    
    Change-Id: I887fcba69ba1e952cc635d939e636d69e227f8b8
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14937
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8cbee639520bf4631ce658e2da9b4bc3010d2eaa
Author: Richard Wareing <rwareing@fb.com>
Date:   Fri Nov 20 10:59:00 2015 -0800

    features/locks: Add lock revocation functionality to posix locks translator
    
    Summary:
    - Motivation: Prevents cluster instability by mis-behaving clients
      causing bricks to OOM due to inode/entry lock pile-ups.
    - Adds option to strip clients of entry/inode locks after N seconds
    - Adds option to clear ALL locks should the revocation threshold get hit
    - Adds option to clear all or granted locks should the max-blocked
      threshold get hit (can be used in combination w/ revocation-clear-all).
    - Options are:
        features.locks-revocation-secs <integer; 0 to disable>
        features.locks-revocation-clear-all [on/off]
        features.locks-revocation-max-blocked <integer>
    - Adds monkey-locking option to ignore 1% of unlock requests (dev only)
        features.locks-monkey-unlocking [on/off]
    - Adds logging to indicate revocation event & reason
    
    Test Plan:
    First you will need TWO fuse mounts for this repro.  Call them /mnt/patchy1 & /mnt/patchy2.
    
    1. Enable monkey unlocking on the volume:
    gluster vol set patchy features.locks-monkey-unlocking on
    
    2. From the "patchy1", use DD or some other utility to begin writing to a file,
       eventually the dd will hang due to the dropped unlocked requests.  This now
       simulates the broken client.  Run:
    
    for i in {1..1000};do dd if=/dev/zero of=/mnt/patchy1/testfile bs=1k count=10;done'
    
    ...this will eventually hang as the unlock request has been lost.
    
    3. Goto another window and setup the mount "patchy2" @ /mnt/patchy2, and
       observe that 'echo "hello" >> /mnt/patchy2/testfile" will hang due to the
       inability of the client to take out the required lock.
    
    4. Next, re-start the test this time enabling lock revocation; use a timeout of
       2-5 seconds for testing:
       'gluster vol set patchy features.locks-revocation-secs <2-5>'
    
    5. Wait 2-5 seconds before executing step 3 above this time.  Observe that this
       time the access to the file will succeed, and the writes on patchy1 will
       unblock until they hit another failed unlock request due to
       "monkey-unlocking".
    
    BUG: 1350867
    Change-Id: I814b9f635fec53834a26db634d1300d9a61057d8
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14816
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit f630fb742a603083a6adc610296458bcd2e57062
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jul 14 11:17:40 2016 +0530

    features/index: Move gf_log -> gf_msg
    
    Change-Id: I88e5d69a24309bf9d3cb855950c9a5349bdd3d66
    BUG: 1356504
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14924
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Krutika Dhananjay <kdhananj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Tested-by: Zhou Zhengping <johnzzpcrystal@gmail.com>

commit 3af889f02722f4636d2ea30570de6477e8b5a3a9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jul 16 14:21:47 2016 +0200

    build: correctly format some (s)size_t messages
    
    On 32-bit builds the are are warnings like these:
    
        posix.c:6438: warning: format '%ld' expects type 'long int', but argument 11 has type 'ssize_t'
    
    Instead of using "%l" for (signed) size_t variables, "%z" should be
    used.
    
    BUG: 1198849
    Change-Id: I6f57b5e8ea174dd9e3056aff5da685e497894ccf
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14933
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit eb4ea14dcdf6dc2f741a2ed14150ee6ea83b92ce
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Sat Jul 16 18:02:55 2016 -0400

    io-threads.c: add serveral fops support in io-threads
    
    1.add lease, seek, getactivelk, setactivelk support in io-threads
    2.add several missing function declations in defaults.h, the declation
    of function default_getactivelk_failure_cbk needed by io-threads.c
    
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    
    Change-Id: Ie7a56569b4c29cdc6984d31738b484d2d6d83557
    BUG: 1357210
    Reviewed-on: http://review.gluster.org/14935
    Tested-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3c485cb896837c8e362fd0b094325002ce806ac4
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Jul 13 16:24:31 2016 +0530

    nfs: Reset cs->resolvedhard while resolving an entry
    
    If an entry is not found in the inode table, nfs xlator should be
    resolving it by sending an explicit lookup to the brick process.
    But currently its broken in case of NFS3_LOOKUP fop where in the server
    bails out early resulting in sending pargfid attributes to the client.
    To fix the same reset 'cs->resolvedhard' so that an explicit lookup
    is done for the entry in the resume_fn "nfs3_lookup_resume()".
    
    Change-Id: I999f8bca7ad008526c174d13f69886dc809d9552
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    BUG: 1356068
    Reviewed-on: http://review.gluster.org/14911
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit db4f4f1500372ee9f5a1c8faff5081d2a95652e3
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jul 15 13:15:21 2016 +0530

    packaging: Remove ".py" extension from symlink target
    
    S57glusterfind-delete-post.py* is packaged in
    $LIBEXEC/glusterfs/glusterfind directory, symlink created to
    /var/lib/glusterd/hooks directory
    
    ln -s $(libexecdir)/glusterfs/glusterfind/S57glusterfind-delete-post.py \
    $(DESTDIR)$(GLUSTERD_WORKDIR)/hooks/1/delete/post/S57glusterfind-delete-post.py
    
    ".py" should be removed from symlink target so that build system will
    not try to compile the symlink files and generate .pyc/.pyo files.
    
    BUG: 1356868
    Change-Id: I9155378aa72eb8559ba8af76d91a4985f69f38f9
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14928
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ab56ec1e99cd76d45b52d841e6b0009f94a3268b
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Sun Jul 10 09:10:49 2016 -0400

    rpc: fix several problems in failure handle logic
    
    Once dynstr is set into a dict by function dict_set_dynstr, its free
    operation will be called by this dict when the dict is destroyed.
    
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    
    Change-Id: Idd2bd19a041bcb477e1c897428ca1740fb75c5f3
    BUG: 1354141
    Reviewed-on: http://review.gluster.org/14882
    Tested-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 8d3ef3322aa7fccff842e508a1bfd5be71e18849
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jul 14 13:04:09 2016 +0530

    extras/cliutils: Fixed extra packaging line
    
    cliutils was added in two places, $LIBEXEC and $PYTHON_SITE_PACKAGES
    
    Removed packaging from $LIBEXEC
    
    BUG: 1342356
    Change-Id: Ie51d72b65996d14be2e7cab9a614327bec1e9555
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14923
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 1b998788ece8c8b52657e8b9aae65d3279690c5b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jul 12 00:39:31 2016 +0530

    glusterd: Fix gsyncd upgrade issue
    
    Problem:
        gluster upgrade is not generating new volfiles
    
    Cause:
    During upgrade, "glusterd --xlator-option *.upgrade=on -N"
    is run to generate new volfiles. It is run post 'glusterfs'
    rpm installation. The above command fails during upgrade
    if geo-replication is installed. This is because on
    glusterd start 'gsyncd' binary is called to configure
    geo-replication related stuff. Since 'glusterfs' rpm is
    installed prior to 'geo-rep' rpm, the 'gsyncd' binary
    used to glusterd upgrade command is of old version and
    hence it fails before generating new volfiles.
    
    Solution:
    Don't call geo-replication configure during upgrade/downgrade.
    Geo-replication configuration happens during start of glusterd
    after upgrade.
    
    Change-Id: Id58ea44ead9f69982f86fb68dc5b9ee3f6cd11a1
    BUG: 1355628
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14898
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 4768760d5eb0ee8a0251e7776ed03d130c747164
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Mon Jul 11 07:28:44 2016 -0400

    build: fix noisy compilation warning with current build option Wstrict-prototypes
    
    Change-Id: I50904033aa2beb880dee828849f470ac31048a79
    BUG: 1354221
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/14884
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 19adaad015a8e13206f656eaee135881a2da58eb
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue May 31 13:39:05 2016 +0530

    extras/cliutils: Utils for creating CLI tools for Gluster
    
    Refer README.md for documentation.
    
    BUG: 1342356
    Change-Id: Ic88504177137136bbb4b8b2c304ecc4af9bcfe30
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14627
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d94bf608b16b82f2c8f8588a96459cb746773b32
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jun 23 11:53:36 2016 +0530

    geo-rep: Handle Config parser errors
    
    Python ConfigParser lib has two methods, readfp and read, it should
    be used as follows.
    
        readfp(open("defaults.conf"))
        read("custom.conf")
    
    ConfigParser.read(path) ignores any file errors, which is intentional
    since errors are handled while loading default config.
    
    Geo-rep uses only one config file(Session config in Master side and
    Template config on Slave side) so we should use readfp to avoid
    skipping OS errors.
    
    config.read is retained in case of `--config-set-rx` where glusterd
    creates new template config file.
    
    BUG: 1349273
    Change-Id: I15a14d3743facd7b8c7af0edc70fdefaa43efd04
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14777
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9733c68e878869daec196bf7bca16780eef73f74
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Wed Jun 29 15:36:41 2016 +0530

    gluster v set help does not show ssl options
    
    Problem: "gluster v set help" does not show ssl options.
    
    Solution: Remove NO_DOC option for client.ssl/server.ssl from glusterd_volopt_map.
    
    Change-Id: Iabe982ea56398209bbf30d41260798e5ad7fce7b
    BUG: 1351134
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/14829
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 633d88ea7ef621bcce9a408188bc57858f6ca942
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jul 7 14:33:20 2016 +0530

    features/index: Ignore regular files when examining state of the inode wrt ENTRY_CHANGES
    
    This prevents unnecessary sys_lstat() syscall when xattrop
    is operating on regular files.
    
    Also, to avoid (even) the one-time execution of sys_lstat()
    syscalls on disperse volumes or replicate volumes when granular
    entry self-heal is disabled, we pass a key in afr_selfheal_undo_pending()
    indicating to index that this xattrop is on a granular directory index.
    Index will accordingly decide whether or not to attempt the index state
    initialization.
    
    Change-Id: I616d9a4b3704066f4a2770d3ca307f7dca9122e0
    BUG: 1331323
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14870
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ceac3b4172e7c689941ec3e734eca6c537e69368
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jun 27 15:21:26 2016 +0530

    afr, index: Clean up stale directory and file indices in granular entry sh
    
    Specifically when a directory tree is removed (rm -rf)
    while a brick is down, both the directory index and the
    name indices of the files and subdirs under it will remain.
    Self-heal will need to pick up these and remove them.
    
    Towards this, afr sh will now also crawl indices/entry-changes
    and call an rmdir on the dir if the directory index is stale.
    
    On the brick side, rmdir fop has been implemented for index xl,
    which would delete the directory index and its contents if present
    in a synctask.
    
    Change-Id: I8b527331c2547e6c141db6c57c14055ad1198a7e
    BUG: 1331323
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14832
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f938b3a26ffab9482d5f910ee76d2bb2b370517f
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Wed Jun 29 15:36:06 2016 +0530

    glusterd/geo-rep: Handle empty monitor.status during upgrade
    
    Problem:
    Consider geo-replication is in Stopped state.
    Following which, glusterfs is upgraded (where monitor.status is the new status file).
    
    Now, When geo-replication status command is run,
    empty monitor status file gets created.
    
    Now, if glusterd is restarted, it reads empty monitor status
    and  starts geo-replication session. This is incorrect as session
    was in Stopped state earlier.
    
    Solution:
    If monitor status is empty, error out and avoid
    starting geo-replication session.
    
    Note: if monitor status is empty, geo-rep session is displayed
    as Stopped state.
    
    Change-Id: Ifb3db896e5ed92b927764cf1163503765cb08bb4
    BUG: 1351071
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/14830
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bfbadab0d65f38d2719ceb4d5c9144377db9d4d5
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Mon Jul 11 13:34:28 2016 +0530

    tests: fix rebalance timing issue
    
    With a start and stop rebalance, the stop command may fail
    as by that time the rebalance process may not come up.
    Using the rebalance status commmand to ensure that the rebalance
    process is up before stoping rebalance.
    
    Change-Id: I3d5123cd5dfabde2720428455b257d11b980ce21
    BUG: 1354372
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/14885
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 62f826de85489f47da506e0d20e9ed349278d597
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Jul 8 14:25:35 2016 +0530

    "md-cache: Enable caching of stat fetched from readdirp
    
    Patch http://review.gluster.org/11894 removed readdirp fop for
    md-cache, but there is no mention of exact xlator which was
    failing because of this. As mentioned by Rafi(author of patch 11894)
    tiering and svc doesn't really need this as the inode_ctx is populated
    in readdirp_cbk. Hence reverting this commit.
    This reverts commit c8c9308134ae4ce24c630a1b0ccfcf4e8f9b0fe7.
    
    Change-Id: Ib8d00b3f129596f3a54984f839199175f5c9b55b
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14879
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c341a95bd3e6ae81cf32620950bac33b27c1e033
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Apr 14 12:38:50 2016 -0400

    tests: miscellaneous improvements
    
    This is a combination of three previous low-impact changes, combined to
    reduce patch-pushing burden.
    
    ((( GF_INTERACTIVE )))
    
    To use this, just define GF_INTERACTIVE (value doesn't matter as long as
    the length is non-zero) before running your test.  It replaces the TEST
    alias with one that will prompt you before executing that line.  You can
    answer:
    
      'y' to execute the line
    
      'q' to exit the test immediately
    
      anything else to skip this line and continue
    
    This is particularly useful to inspect state in another window while a
    test is paused, or to do manual experimentation in the (often complex)
    configuration created during a test.
    
    ((( CLEANUP.SH )))
    
    tests: add cleanup.sh
    
    Often, a developer might want to run a test up to some point, then bail
    out and poke around manually.  That leaves state that needs to be
    cleaned up before the next test can run properly.  This patch adds a
    trivial script to invoke that cleanup machinery.
    
    Along the way, code in include.rc to find env.rc was changed to be more
    robust across arbitrarily deep (or shallow) directory hierarchies.
    
    ((( REPLACE EXISTING TAR FILES INSTEAD OF APPENDING )))
    
    We currently use "tar rf" to collect log files from each test.  This
    *appends* the new data to whatever's there already, which has two bad
    effects when a test is run repeatedly.
    
     * Ever-increasing size of the tar file.
    
     * Ever-increasing time to extract logs from the tar file, with each
       copy completely overwriting any previous.
    
    This doesn't seem to be a problem in our regression tests, because the
    entire directory is nuked during package removal and reinstallation.
    However, when running a test repeatedly during a debug session, the
    effects can be quite severe.  This is particularly evident with JBR,
    because the "logs" that get archived include large journal files.
    Certain other translators, such as changelog and CTR, might be prone to
    similar effects.
    
    There's no point to having multiple copies of the logs in each tar file.
    As far as I know, nobody ever takes advantage of that.  Therefore, use
    "tar cf" to overwrite any existing archive instead of appending.  This
    change also handles excluding other .tar files in a portable way.
    
    Change-Id: Iebf77d496a71976c321bbacb49776338a9da586f
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/14874
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit f4757d256e3e00132ef204c01ed61f78f705ad6b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jul 4 17:25:57 2016 +0530

    feature/bitrot: Show whether scrub is in progress/idle
    
    Bitrot scrub status shows whether the scrub is paused
    or active. It doesn't show whether the scrubber is
    actually scrubbing or waiting in the timer wheel
    for the next schedule. This patch shows this status
    with "In Progress" and "Idle" respectively.
    
    Change-Id: I995d8553d1ff166503ae1e7b46282fc3ba961f0b
    BUG: 1352871
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14864
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b2c73cbf423de6201f956f522b7429615c88869d
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Fri Jun 24 06:33:16 2016 +0800

    rpc: invalid argument when function setsockopt sets option TCP_USER_TIMEOUT
    
    If option "transport.tcp-user-timeout" hasn't been setted, glusterd's
    priv->timeout will be -1, which will cause invalid argument when
    set TCP_USER_TIMEOUT.
    
    Change-Id: Ibc16264ceac0e69ab4a217ffa27c549b9fa21df9
    BUG: 1349657
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/14785
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 30ff5b69883537f743e38f060d4d8e229a84863a
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Apr 9 00:40:38 2016 -0400

    cluster/afr: Fix a minor typo in afr-self-heald.c
    
    s/outout/output/
    
    Change-Id: I2aec770cdae513cd4932e5fd56e0267584e44cae
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/13930
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>

commit 693eccd456c4fc7dfadb72069da906544cf19733
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Sun Jun 26 19:56:58 2016 -0400

    libglusterfs: race condition when set ctx->timer in function gf_timer_registry_init
    
    1.fix race conditon when set ctx->timer
    2.use typical list_head operation instead of verbose list's operation
    3.add file "tags" into .gitignore
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    
    Change-Id: I4ec55e41356633cf1399536d202c58e19b309f00
    BUG: 1350191
    Reviewed-on: http://review.gluster.org/14800
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9886d568a7a8839bf3acc81cb1111fa372ac5270
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jul 8 10:46:46 2016 +0530

    rpc/socket: pthread resources are not cleaned up
    
    A socket_connect failure creates a new pthread which
    is not a detached thread. As no pthread_join is called,
    the thread resources are not cleaned up causing a memory leak.
    
    Now, socket_connect creates a detached thread to handle failure.
    
    Change-Id: Idbf25d312f91464ae20c97d501b628bfdec7cf0c
    BUG: 1343374
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/14875
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 84e9fc2fb5fabf9d1e553a420854a306cdb8a168
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Fri Jun 24 09:58:29 2016 +0530

    rpc/socket.c : Modify socket_poller code in case of ENODATA error code.
    
    Problem:  Polling failure errors are coming till volume is not come while
              SSL is enabled.
    
    Solution: To avoid the message update one condition in socket_poller code
              It will not exit from thread in case of received ENODATA from
              ssl_do function.
    
    Change-Id: Ia514e99b279b07b372ee950f4368ac0d9c702d82
    BUG: 1349709
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Reviewed-on: http://review.gluster.org/14786
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ef08924ba7c568605d96af8b1f4ca50ede045204
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jul 7 15:24:05 2016 -0400

    mgmt: remove unused and misleading pmap_signup
    
    We use signin, but not signup.  Having both just introduces confusion.
    The proc number has been retained to avoid changes to the numbering of
    other procs, and the mapping to a name has similarly been retained as a
    placeholder, but the code and structure definitions have been removed.
    
    Change-Id: I60f64f3b5d71ba6ed6862b36a38f90a9c8271c9f
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/14792
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 45f986a20f582c24c71172eb1ff097295c88aebc
Author: Nigel Babu <nigelb@redhat.com>
Date:   Thu Jul 7 14:35:14 2016 +0530

    Update the documentation link in the spec file
    
    BUG: 1303668
    Change-Id: Ifded6a03f437f16a0a1ad2bfb7377d07569a7735
    Signed-off-by: Nigel Babu <nigelb@redhat.com>
    Reviewed-on: http://review.gluster.org/14869
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>

commit 3b61a00f0afc7f84e7685548cbcde3b69172adf0
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Mon Jul 4 12:21:45 2016 +0530

    geo-rep: fix wrong argument to find_library
    
    Argument passed to find_library function is wrong.
    Pass proper argument to find_library.
    
    Note: It still works as default handle is libc.
    
    Change-Id: I4657a3ef9f5249e3eec4a20582856b58168126ce
    BUG: 1352423
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/14852
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit e51beeacf7fcb7359c129c8067cc95dcd2767e39
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Jul 4 18:36:26 2016 +0530

    gfapi: update count when glfs_buf_copy is used
    
    glfs_buf_copy collates all iovecs into a iovec with count=1. If
    gio->count is not updated it will lead to dereferencing of invalid
    address.
    
    Change-Id: I7c58071d5c6515ec6fee3ab36af206fa80cf37c3
    BUG: 1352634
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reported-By: Lindsay Mathieson <lindsay.mathieson@gmail.com>
    Reported-By: Dmitry Melekhov <dm@belkam.com>
    Reported-By: Tom Emerson <TEmerson@cyberitas.com>
    Reviewed-on: http://review.gluster.org/14854
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 8680261cbb7cacdc565feb578d6afd3fac50cec4
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jun 16 12:03:19 2016 +0530

    storage/posix: fix inode leaks
    
    Change-Id: Ibd221ba62af4db17bea5c52d37f5c0ba30b60a7d
    BUG: 1344885
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14739
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 807b9a135d697f175fc9933f1d23fb67b0cc6c7d
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Tue Jun 14 10:52:27 2016 +0530

    glusterd: Don't start bricks if server quorum is not met
    
    Upon glusterd restart if it is observered that the server quorum
    isn't met anymore due to changes to the "server-quorum-ratio"
    global option, the bricks should be stopped if they are running.
    Also if glusterd has been restarted, and if server quorum is not
    applicable for a volume, do not restart the bricks corresponding
    to the volume to make sure that bricks that have been brought
    down purposely, say for maintenance, are not brought up. This
    commit moves this check that was previously inside
    "glusterd_spawn_daemons" to "glusterd_restart_bricks" instead.
    
    Change-Id: I0a44a2e7cad0739ed7d56d2d67ab58058716de6b
    BUG: 1345727
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/14758
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 014e3c67945546a643703223b9d45a90612ecaee
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Jun 29 05:31:03 2016 -0400

    upcall: Invalidation for xattr should also carry a valid stat
    
    xattr modification also impacts the ctime of the file, hence
    include the new stat along with the new xattrs, in the
    invalidation request
    
    Change-Id: Ieaa4382fa62f397f61a995b926013b9207c6e9da
    BUG: 1352671
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14828
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9a9f37440cb07ce2a1130ce39ea0d3461078f3a8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jun 30 11:42:54 2016 +0530

    glusterd: spawn daemons from init() on a single or two node setup
    
    Allow glusterd to spawn the daemons at the time of initialization when peer
    count is less than 2. This is required if user wants to set up a two node
    cluster with out server side quorum and want the bricks to come up on a node
    where the other node is down, however the behaviour will be overriden when
    server side quorum is enabled.
    
    Change-Id: I21118e996655822467eaf329f638eb9a8bf8b7d5
    BUG: 1352277
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14848
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7df1174f7bed2a00631cf17201f5217a053afeb1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 30 14:49:51 2016 +0530

    features/bitrot: Option to set scrub interval to a minute
    
    Bitrot scrub-frequency supports "hourly|daily|weekly|biweekly|monthly".
    But it is painful for testing as minimum  scrub-interval is an hour
    Hence introducing a scrub interval of minute to ease testing.
    It is intentionally not exposed in bitrot command help as it is
    only for testing.
    
    e.g.,
    gluster vol bitrot <volname> scrub-frequency minute
    
    Change-Id: I155a65298d3fad5ae9e529d9c7d4b0d25fa297c0
    BUG: 1351537
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14836
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 427ef5511232614bafcab686ad797cebb6a2d6b5
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jul 1 11:47:48 2016 +0530

    cli: print volume status client output for partial bricks
    
    In cli the response dictionary is parsed assuming all the bricks to be up.
    If in a given cluster one of the node is down client details for the
    bricks hosted by the same node are not available in the dictionary resulting
    into a blank output for 'gluster volume status <volname> clients'
    
    Fix is to ignore the ret value for dict_get for those keys.
    
    Change-Id: If4fb65b8807ea3ac71b3ed1a754ea75f599e3613
    BUG: 1351880
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14842
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 967a77ed4db0e1c0bcc23f132e312b659ce961ef
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon May 9 12:14:37 2016 +0530

    glusterd: search port from last_alloc to base_port
    
    If a brick process is killed ungracefully then GlusterD wouldn't receive a
    PMAP_SIGNOUT event and hence the stale port details wouldn't be removed out.
    
    Now consider the following case:
    1. Create a volume with 1 birck
    2. Start the volume (say brick port allocated is 49152)
    3. Kill the brick process by 'kill -9'
    4. Stop & delete the volume
    5. Recreate the volume and start it. (Now the brick port gets 49153)
    6. Mount the volume
    
    Now in step 6 mount will fail as GlusterD will provide back the stale port
    number given the query starts searching from the base_port.
    
    Solution:
    
    To avoid this, searching for port from last_alloc and coming down to base_port
    should solve the issue.
    
    Change-Id: I9afafd722a7fda0caac4cc892605f4e7c0e48e73
    BUG: 1334270
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14268
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 01d6b17bac704a320bc0549ae063ee7f4bf3748b
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Jun 29 00:25:39 2016 -0400

    md-cache: Cache gluster-samba metadata
    
    Change-Id: I0a95f4897440c5bf6f54612d9c232e015c8bf983
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14824
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 633e6fe265bc2de42dade58dc6a15c285957da76
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Jul 3 15:51:20 2016 +0530

    glusterd: compare uuid instead of hostname address resolution
    
    In glusterd_get_brickinfo () brick's hostname is address resolved. This adds an
    unnecessary latency since it uses calls like getaddrinfo (). Instead given the
    local brick's uuid is already known a comparison of MY_UUID and brickinfo->uuid
    is much more light weight than the previous approach.
    
    On a scale testing where cluster hosting ~400 volumes spanning across 4 nodes,
    if a node goes for a reboot, few of the bricks don't come up. After few days of
    analysis its found that glusterd_pmap_sigin () was taking signficant amount of
    latency and further code walthrough revealed this unnecessary address
    resolution. Applying this fix solves the issue and now all the brick processes
    come up on a node reboot.
    
    Change-Id: I299b8660ce0da6f3f739354f5c637bc356d82133
    BUG: 1352279
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14849
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 8d41243f18c4a9c89028c8fc5e54b7e2b5e4309d
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Feb 10 18:27:38 2016 -0500

    logging: Change log file name for glusterd
    
    log file names are based on:
    
     a. user provided input (through -l switch while starting a gluster process)
     b. mount point paths in the case of native clients
     c. volume/configuration files used for starting a gluster process
     d. volume server used for starting a gluster process
    
    Currently glusterd uses scheme c. to have a log file name that reads as
    
    INSTALL_PREFIX-etc-glusterfs-glusterd.log
    
    Since glusterd has a well known configuration file, it does not make much
    sense to have log file name based on scheme c. This patch changes the name of
    glusterd's log file to "glusterd.log". Hopefully this enables users to identify
    glusterd's log file more easily.
    
    Change-Id: I2d04179c4b9b06271b50eeee3909ee259e8cf547
    BUG: 1348944
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/13426
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 0cd287189e5e9f876022a8c6481195bdc63ce5f8
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Wed Jun 29 12:09:06 2016 +0530

    glusterd: glusterd must store all rebalance related information
    
    Change-Id: I8404b864a405411e3af2fbee46ca20330e656045
    BUG: 1351021
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/14827
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 1b420a3f695a755c6a45b3b74d28c41f7a2d943b
Author: Sakshi <sabansal@redhat.com>
Date:   Thu May 28 11:23:55 2015 +0530

    cli: different status output for rebalance fix-layout
    
    Change-Id: I6ded40a1b1cff5c72e5b61fd353db3d8c688efd8
    BUG: 1225718
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/10956
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d308fb5e152d8c908bf4f5da81f553fbe3d0400a
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri May 6 10:03:53 2016 -0400

    socket: log the client identifier in ssl connect
    
    Change-Id: I4b463ecafb66de16cbe7ed23fae800bb1204f829
    BUG: 1333912
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/14242
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 09caa0c054c85f030c194362cbf3c687b4a56106
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Jun 16 15:55:47 2016 +0530

    libgfapi : free parameters allocated by glfs_set_volfile_server()
    
    This change introduce new function glfs_free_volfile_server
    which frees the variables allocated by glfs_set_volfile_server
    during glfs_fini()
    
    Change-Id: I8b1806c56e3431c33e4e8c17f9e8aa17a28a2f5c
    BUG: 1347249
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14743
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit c4ddfa5b76690db66fb22518d12226e2bf9cb236
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jun 28 14:48:14 2016 -0400

    build: glusterfs.spec(.in) firewalld file doesn't use %{_prefix}
    
    .../firewalld/services/glusterfs.xml in %server files section
    does not use %{_prefix}
    
    Other firewalld files, e.g., in the firewalld.src.rpm file use
    %{_prefix}
    
    N.B. the other 'hardcoded' path, "/sbin/mount.glusterfs" in the
    %files fuse section must remain as is, there is no macro for
    mount utilities to use as there is for, e.g., the %{_sbindir}
    macro for /usr/sbin. This doesn't matter for either RHEL6, where
    /sbin and /usr/sbin are distinct directories, or for Fedora and
    RHEL7, where /sbin is a symlink to /usr/sbin. E.g. see the nfs-
    utils.src.rpm where /sbin/mount.nfs is also 'hardcoded'.
    
    Change-Id: I902f47e3c589526c774d0aceb6fc2815abf86b01
    BUG: 1350793
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14823
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 70fd68d94f768c098b3178c151fa92c5079a8cfd
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Apr 22 16:56:47 2016 +0530

    georep: add reset-sync-time option for session delete
    
    Set the stime xattr at all the brick roots to (0,0) if the argument
    reset-sync-time has been provided on the command-line.
    To avoid testing against directory specific stime, the remote
    stime is assumed to be minus_infinity, if the root directory
    stime is set to (0,0), before the directory scan begins.
    This triggers a full volume resync to slave in the case of a
    geo-rep session recreation with the same master-slave volume
    pair.
    
    Command synopsis:
    gluster volume geo-replication <MASTERVOL> <SLAVE>::<SLAVEVOL> delete \
        [reset-sync-time]
    
    Update gluster cli man page to include new sub-command reset-sync-time.
    
    Change-Id: Ie4ce03b9425ed9bb81eda8681058c0fc6f990948
    BUG: 1311926
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/14051
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 1e60f9746cf7cb8ce34e2b1572410c39b11d7664
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jun 7 16:27:34 2016 +0530

    libglusterfs: Implement API that provides page-aligned iobufs
    
    One of the consumers of a page aligned buffer would be posix's
    readv fop on O_DIRECT fds. Today the way it works is by getting
    a page-aligned buffer through calloc, pread()ing into this buffer
    and then copying its contents into a newly created iobuf's ptr.
    This results in an extra memcpy() which can be avoided if we could
    implement an api that would return an iobuf whose ptr is
    page-aligned. That way the iobuf->ptr can be directly passed to
    sys_pread() as a parameter by posix translator.
    
    Change-Id: I385139bc6ee309fc501034b3af8f7814fab8cd65
    BUG: 1343838
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14672
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 60cc8ddaf6105b89e5ce3222c5c5a014deda6a15
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sun Jun 12 13:02:05 2016 +0530

    libglusterfs/client_t: Dump the 0th client too
    
    Change-Id: I565e81944b6670d26ed1962689dcfd147181b61e
    BUG: 1344885
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14704
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c2d3703ed70d13063d693f135d89538db526ad5c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 28 15:32:17 2016 +0530

    glusterd/cli: coverity fixes
    
    A downstream coverity run has revealed few of the following coverity defects.
    Since the downstream code is a clone of a specific upstream branch the defects
    hold true for the upstream as well.
    
    Defect type: NEGATIVE_RETURNS
    xlators/mgmt/glusterd/src/glusterd-rpc-ops.c:641: negative_returns: "op_errno"
    is passed to a parameter that cannot be negative.
    
    Defect type: BUFFER_SIZE_WARNING
    xlators/mgmt/glusterd/src/glusterd-volume-ops.c:2124: buffer_size_warning:
    Calling strncpy with a maximum size argument of 261 bytes on destination array
    "volinfo->volname" of size 261 bytes might leave the destination string
    unterminated.
    
    Defect type: BUFFER_SIZE_WARNING
    xlators/mgmt/glusterd/src/glusterd-volgen.c:4888: buffer_size_warning: Calling
    strncpy with a maximum size argument of 261 bytes on destination array
    "volinfo->volname" of size 261 bytes might leave the destination string
    unterminated.
    
    Defect type: STRING_OVERFLOW
    xlators/mgmt/glusterd/src/glusterd-volgen.c:3449: string_overflow: You might
    overrun the 256 byte destination string "tmp_volname" by writing 261 bytes from
    "volinfo->volname".
    
    Defect type: BUFFER_SIZE_WARNING
    xlators/mgmt/glusterd/src/glusterd-utils.c:3392: buffer_size_warning: Calling
    strncpy with a maximum size argument of 261 bytes on destination array
    "new_volinfo->volname" of size 261 bytes might leave the destination string
    unterminated.
    
    Defect type: NO_EFFECT
    xlators/mgmt/glusterd/src/glusterd-utils.c:7359: remediation: Was
    "rebal->rebalance_id" formerly declared as a pointer?
    
    Defect type: USE_AFTER_FREE
    xlators/mgmt/glusterd/src/glusterd-utils.c:7115: pass_freed_arg: Passing freed
    pointer "volinfo" as an argument to "glusterd_friend_contains_vol_bricks".
    
    Defect type: DEADCODE
    cli/src/cli-cmd-parser.c:1767: dead_error_begin: Execution cannot reach this
    statement: "ret = -1;".
    
    Change-Id: Ie941bdf31923e2f39618dd94bfae16fdb3ad65f1
    BUG: 789278
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14818
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e5221d288e41d29d89d52f8deab657d2285a852c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 26 18:50:27 2016 +0200

    nfs: allow hostnames with dashes in exports/netgroups files
    
    Hostnames with dashes (like "vagrant-testVM") are not correctly parsed
    when reading the exports/netgroups files. This bacomes obvious when
    running ./run-tests-in-vagrant.sh because it causes
    tests/basic/mount-nfs-auth.t and tests/basic/netgroup_parsing.t to fail.
    
    The regex for hostname (in exports) and the entry and hostname
    (netgroups) parsing does not include the "-" sign, and hence the
    hostnames are splitted at it.
    
    BUG: 1350237
    Change-Id: I38146a283561e1fa386cc841c43fd3b1e30a87ad
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14809
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 10fa1bcce3b73f630dbc3241722c1af9dee4c414
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Jun 27 12:40:17 2016 +0530

    protocol/server: Fix client/server compatibility
    
    The 3.8 client expects a child_up key from the server
    indicating the status of the server translators. This
    key is not being sent by the servers running older
    versions, thereby breaking compatibility.
    
    With this patch we are treating the absence of the said
    key as an indication that the server trying to connect
    to this client is running an older version and hence
    in such a case we are setting conf->child_up as
    _gf_true explicitly. This should suffice in emulating
    the older behavior.
    
    Due to the nature of this bug, requiring two version to
    be reproducible, there are no testcases added for the same.
    
    Change-Id: I29e0a5c63b55380dc9db8e42852d7e95b64a2b2e
    BUG: 1350327
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14811
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>

commit 5205d42ddfb67e22eab7fa54ac9b081bb1f8b1ec
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Mon Jun 27 17:44:28 2016 +0530

    distaf: Modified tier_attach() to get bricks path from available
            bricks in server
    
    Added code to get bricks path from available bricks in
    server in tier_attach()
    Change-Id: I58822f425c6ea8284568d3701807cfcc11f37e3c
    BUG: 1350427
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14814
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: M S Vishwanath Bhat <msvbhat@gmail.com>

commit 763ed1017b0011934ad2414d7396c46e528ea5b3
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed May 25 14:38:31 2016 +0530

    gfapi/handleops: Avoid using glfd during create
    
    To avoid leaking glfd while creating a file using handleops and
    since application shall not be interested in it, use the 'fd'
    object directly which can be un'refed post create.
    
    Change-Id: I119874ffb63fb4aa18f846ba1fdbe77874b66a54
    BUG: 1339553
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14532
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 61d72b3d91f2655b04de4ef29262f738a8cf7369
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Jun 23 12:20:03 2016 +0530

    gfapi : check the value "iovec" in glfs_io_async_cbk only for read
    
    The glfs_io_async_cbk() is called from the cbk of all the async ops
    such as write, read, fsync, ftruncate. In all other cases, expect for
    read the value for "iovec" is NULL. From the code, glfs_io_async_cbk
    checks the value in common routine which may end up in failures.
    
    Thanks Joe Julian for finding issue and suggesting the fix.
    
    Change-Id: I0be0123da68f9d8fbb5d94ede2d45566a9add6a5
    BUG: 1349276
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reported-by: Joe Julian <me@joejulian.name>
    Reviewed-on: http://review.gluster.org/14779
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Joe Julian <me@joejulian.name>

commit a4bdba1ed44ba23d0a25c6192e854b29b45550bb
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Sun Jun 26 23:53:34 2016 +0530

    distaf: Modified get_pathinfo() in lib_utils.py
    
    Modified get_pathinfo() in lib_utils.py
    
    Change-Id: I721d3704ec00c20b9678088d79e52e3eedbe4af5
    BUG: 1350248
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14802
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: M S Vishwanath Bhat <msvbhat@gmail.com>

commit 2ca5388692e70e079c99771d8c66a06bd90d5268
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jun 22 14:52:58 2016 +0530

    features/index: Delete parent dir indices when heal on it is complete
    
    In this patch, the state information about whether a directory
    gfid index is present or not is stored in the inode ctx with
    values IN and NOTIN. This saves index xl the need to perform
    stat() everytime an index_entry_create() is called.
    
    When a brick is restarted these in-memory inode ctx records will
    be gone. So when granular entry heal happens after a brick is restarted,
    and a post-op is done on the parent, if the state gotten from inode ctx
    is UNKNOWN, then index xl does a stat to initialize the state as IN or
    NOTIN. Note that this is a one-time operation for the lifetime of the
    brick. Such a change also helps avoid calling index_del() in
    xattrop_index_action() periodically even when granular self-heal is
    disabled or when the volume type is disperse.
    
    Change-Id: Ib92c17350e6531b91ab81477410fe1e7a5856207
    BUG: 1331323
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14781
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 888de8851e718d8e3117e47fa35cfc075b998f62
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 22 14:57:44 2016 +0530

    glusterd/geo-rep: Add relative path validation to copy file command
    
    Added validation for input file, command fails if input file path is
    relative path pointing outside of GLUSTERD_WORKDIR.
    
    BUG: 1348897
    Change-Id: I329d43ebed69bfe9fe03d6be70dc8c78a605ffc5
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14772
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 04d95b93f1b0011920a15994059c3b17cf04e434
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Mon Jun 27 15:51:38 2016 +0530

    Minor fix in distaf_gluster_config.yml file
    
    Change-Id: Ia0609d54b51eed14db229e0fdc92c4530fb97aff
    BUG: 1350383
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14813
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit d5088c056d5aee1bda2997ad5835379465fed3a1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 7 21:27:10 2016 +0530

    storage/posix: Give correct errno for anon-fd operations
    
    Change-Id: Ia9e61d3baa6881eb7dc03dd8ddb6bfdde5a01958
    BUG: 1343906
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14669
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 0d280e0b7f2042e78b8d94a48d5e3bcc5c13f422
Author: Shwetha Panduranga <spandura@redhat.com>
Date:   Mon Jun 27 02:02:29 2016 +0530

    Adding simple test "running dd from mount".
    
    Change-Id: Icbb799c401e73b51a7e96b86db78e46f6b0d5813
    BUG: 1350258
    Signed-off-by: Shwetha Panduranga <spandura@redhat.com>
    Reviewed-on: http://review.gluster.org/14807
    Tested-by: ShwethaHPanduranga
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 7897e023e60f8cdfa6d7a5ea654214ad186dd033
Author: Shwetha Panduranga <spandura@redhat.com>
Date:   Mon Jun 27 01:49:15 2016 +0530

    Servers in yaml file is list of dicts. Hence iterating through servers to get
    the 'host' of it.
    
    Change-Id: I361aa88ad21ce30fd57f297795c5f7ff60ccfd2a
    BUG: 1350256
    Signed-off-by: Shwetha Panduranga <spandura@redhat.com>
    Reviewed-on: http://review.gluster.org/14805
    Tested-by: ShwethaHPanduranga
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit d2842f1b58ed31a45f9fb69efa4f4c7ae5ffd984
Author: Shwetha Panduranga <spandura@redhat.com>
Date:   Mon Jun 27 02:26:06 2016 +0530

    Modifying gluster_base_class and mount_ops to suit the config file changes made
    
    Change-Id: Ic551724dd27fcc2cc618e8de04110752bf5a8786
    BUG: 1350017
    Signed-off-by: Shwetha Panduranga <spandura@redhat.com>
    Reviewed-on: http://review.gluster.org/14808
    Tested-by: ShwethaHPanduranga
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jonathan Holloway <jholloway@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit eaadde082e460eb3c2d90965d3e85e1766936f16
Author: M S Vishwanath Bhat <msvbhat@gmail.com>
Date:   Sun Jun 26 12:10:30 2016 -0700

    Revert "Modifying gluster_base_class and mount_ops to suit the config file changes made"
    
    This reverts commit 09c0b2f3c2534f365bee5a738d1699af36413a25.
    
    BUG: 1350017
    
    Change-Id: Id1b63c98ad827b87ad0a6beb4c7565c45749b134
    Reviewed-on: http://review.gluster.org/14803
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Tested-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 09c0b2f3c2534f365bee5a738d1699af36413a25
Author: Shwetha Panduranga <spandura@redhat.com>
Date:   Sat Jun 25 02:06:38 2016 +0530

    Modifying gluster_base_class and mount_ops to suit the config file changes made
    
    Change-Id: I61481c029fdbdd9c966867f195b9dc9046550392
    BUG: 1350017
    Signed-off-by: Shwetha Panduranga <spandura@redhat.com>
    Reviewed-on: http://review.gluster.org/14793
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Tested-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 8b53bfab1e86b7c110e5f2bab464678c4c99758a
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Sun Jun 26 23:14:35 2016 +0530

    distaf: Modified volume_ops library
    
    Modified gluster volume ops library modules
    
    Change-Id: I2ef5ca44f3a4a9844aee48f3688e8617dbbb4fcd
    BUG: 1350245
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14801
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: ShwethaHPanduranga
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 931c656d6207645d2a7572cacf674f2b77f411f7
Author: Apeksha D Khakharia <akhakhar@redhat.com>
Date:   Sun Jun 26 14:55:20 2016 +0530

    distaf: Adding samba_ops library
    
    Change-Id: Icc2b1eefe0f27a67e9f0e50edd41b313bd3cc892
    BUG: 1350173
    Signed-off-by: Apeksha D Khakharia <akhakhar@redhat.com>
    Reviewed-on: http://review.gluster.org/14798
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: ShwethaHPanduranga
    Tested-by: ShwethaHPanduranga
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1569b5138e2a482bcd880ca0f5e7b1509a07bea4
Author: Apeksha D Khakharia <akhakhar@redhat.com>
Date:   Sun Jun 26 16:28:52 2016 +0530

    distaf: minor import changes in ganesha.py
    
    Change-Id: I8bcb9056c1087dce54bc3ed6c967dfb444521236
    BUG: 1350188
    Signed-off-by: Apeksha D Khakharia <akhakhar@redhat.com>
    Reviewed-on: http://review.gluster.org/14799
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: ShwethaHPanduranga
    Tested-by: ShwethaHPanduranga
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 453709554c1b870883e34fd11bd9f845fbb53368
Author: Apeksha D Khakharia <akhakhar@redhat.com>
Date:   Fri Jun 24 11:06:17 2016 +0530

    distaf: adding libraries to get server_brick dictionaries
    
    Change-Id: I9046126739a126ee2d40249919e1fe58adf2fa27
    BUG: 1349723
    Signed-off-by: Apeksha D Khakharia <akhakhar@redhat.com>
    Reviewed-on: http://review.gluster.org/14788
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: ShwethaHPanduranga
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: ShwethaHPanduranga

commit 4935dd67443ac52c20dfaee82892f2524c990c71
Author: Apeksha D Khakharia <akhakhar@redhat.com>
Date:   Sun Jun 26 14:10:38 2016 +0530

     distaf: modifications to create volume function
    
    Change-Id: Ifba1bc96f1f620b41fd5c61c345e8ac148e9250a
    BUG: 1350168
    Signed-off-by: Apeksha D Khakharia <akhakhar@redhat.com>
    Reviewed-on: http://review.gluster.org/14797
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: ShwethaHPanduranga
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 2ee48474be32f6ead2f3834677fee89d88348382
Author: Mohit Agrawal <moagrawa@redhat.com>
Date:   Mon Jun 13 12:41:15 2016 +0530

        rpc/socket.c: Modify approach to cleanup threads of socket_poller in socket_spawn.
    
        Problem: Current approach to cleanup threads of socket_poller is not appropriate.
    
        Solution: Enable detach flag at the time of thread creation in socket_spawn.
    
        Fix: Write a new wrapper(gf_create_detach_thread) to create detachable thread
             instead of store thread ids in a queue.
    
        Test: Fix is verfied on gluster process, To test the patch followed below procedure
              Enable the client.ssl and server.ssl option on the volume
              Start the volume and count anon segment in pmap output for glusterd process
              pmap -x <glusterd-pid> | grep "\[ anon \]" | wc -l
              Stop the volume and check again count of anon segment it should not increase.
    
    Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
    Change-Id: Ib8f7ec7504ec8f6f74b45ce6719b6fb47f9fdc37
    BUG: 1336508
    Reviewed-on: http://review.gluster.org/14694
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7a1c1e2904701496968ed14b6d7479fb706c3188
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Feb 5 15:10:06 2016 +0530

    afr:Don't wind reads for files in metadata split-brain
    
    Problem: For a read on  a file in metadata split-brain:
    1.lookup_done resets event_generation to zero.
    2. readv is issued, goes to inode refresh due to mismatching event_gen.
    3. After refresh is successful, we update event_generation, data and
    metdata readable.
    3. We then call afr_read_txn_refresh_done() which in turn calls
    afr_inode_get_readable() but doesn't check for EIO. So afr_readv_wind
    is called with local->readable (which is populated with data_readable),
    thus winding the read to a brick.
    4. Also, further parallel reads that come directly go to the wind path
    because there is no inode_refresh needed.
    
    Fix:
    1.For any afr_read_txn(), readable must be an intersection of data and metadata
    readable.
    2.Check for EIO in afr_read_txn_refresh_done().
    
    Change-Id: I22dd221fdfaf96d7aced2f474e28ed1337d69f0e
    BUG: 1305031
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13389
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit beaa5d104a3eec1b0b87fac648b028f77fc2e80b
Author: Shwetha Panduranga <spandura@redhat.com>
Date:   Mon May 16 15:18:06 2016 +0530

    Adding distaf config file for gluster tests.
    
    Change-Id: Id16bc316a202fa373774f380dfd86903516b80ac
    BUG: 1336373
    Signed-off-by: Shwetha Panduranga <spandura@redhat.com>
    Reviewed-on: http://review.gluster.org/14357
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 59523a782d7ed00b31c8cdf8da74310384272355
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jun 15 16:02:44 2016 +0530

    features/index: Do deletion of name-index in unwind path
    
    Previously the deletion of name index was being done before
    winding the xattrop to posix. This order needs to be changed
    to ensure we don't lose the index in the event the xattrop fails
    in posix xl.
    
    Change-Id: I4aa892b102cbf5269cede041b871064563cb7348
    BUG: 1331323
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14742
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit ec3ea75513347deb95960f49d58fc19478a7ad17
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Jun 23 17:41:09 2016 +0530

    ganesha/scripts : delete nfs-ganesha folder from shared storage during clean up
    
    A directory named "nfs-ganesha" will be created inside shared storage when
    'gluster nfs-ganesha enable' is executed. Similarly this directory should be
    removed when 'gluster nfs-ganesha disable' is executed.
    
    Change-Id: Icc09b32010de07c9809e22aafbb2fd08a5c8252f
    BUG: 1349398
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14782
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 1fdc0db572ce80d6f3a9e71d40ef272c2eb3e7e7
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Wed Jun 22 01:27:25 2016 +0800

    cluster/dht: Wrong type of function's parameter when calling dht_selfheal_dir_xattr_cbk
    
    The second parameter's type is call_frame_t *, and we change
    it to be type xlator_t *, it is exactly what we need in this function.
    
    Change-Id: I6a154edcaa5a11084d837ca925efbfac853d0786
    BUG: 1346551
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/14737
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 16c34b101f604a09a5c735fb39815c59ee4ecbdb
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Jun 23 11:56:10 2016 +0530

    glusterd/ganesha : persist value set by teardown in info file
    
    During teardown, all the volumes exported via NFS-Ganesha will be
    unexported. So all related volume options need to reset. Currently
    this change made using dict_set on volopt dictionary, i.e change
    is only reflected in memory not persisted in the volume info file
    Therefore incase of glusterd restart this data can be lost.
    
    Also this patch fix similar issue in ganesha_manage_export().
    
    Change-Id: Ib843ac30adb28a70e13a9a1df57020ef2f3db8a4
    BUG: 1349270
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14778
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 6680b844c5a31bdb3b0c4c6a831218aecd45fd6c
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Wed May 4 15:12:23 2016 +0530

    distaf: Added bitrot_ops and lib utils
    
    Added library functions for gluster bitrot operations and added
    functions in lib_utils.py which are generic across all components
    
    Change-Id: I877ded038c9f4c1e7aa1a15b035fcd7ebb0da21f
    BUG: 1332885
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Change-Id: I877ded038c9f4c1e7aa1a15b035fcd7ebb0da21f
    Reviewed-on: http://review.gluster.org/14209
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: ShwethaHPanduranga
    Smoke: Gluster Build System <jenkins@build.gluster.org>

commit 6109f0a98f2fd7f7a2ad95c621c492733fe0289f
Author: Apeksha D Khakharia <akhakhar@redhat.com>
Date:   Tue May 24 12:20:59 2016 +0530

    distaf: adding libraries to setup CTDB in gluster
    
    Change-Id: Iad3493794cf05262f182334efc8e517e30698e39
    BUG: 1339541
    Signed-off-by: Apeksha D Khakharia <akhakhar@redhat.com>
    Reviewed-on: http://review.gluster.org/14531
    Reviewed-by: Vivek Das <vdas@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: ShwethaHPanduranga

commit b37c6d9088851b2ef83ce4e28af642892e5fd268
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 22 13:05:10 2016 +0530

    feature/gfid-access: Fix nameless lookup on ".gfid"
    
    Problem:
    In geo-replication, if the data copied from .snaps
    directory to the master, the first set of copy after
    uss is enabled doesn't get sync to slave.
    
    Cause:
    Enabling uss results in graph switch. So when the
    lookup comes on "0x00...0d/gfid1" on new graph,
    ("0x00...0d' being the gfid of virtual directory
     ".gfid"), it fails as gfid-access xlator doesn't
    handle it.
    
    Fix:
    Handle nameless lookup on ".gfid" in gfid-access
    xlator.
    
    Change-Id: I32be0064e8fd58068646dbf662432f4a3da14e77
    BUG: 1348904
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14773
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a6e551122c603ab0cba798e7e2b30d3a15191b68
Author: Samikshan Bairagya <samikshan@gmail.com>
Date:   Tue Mar 29 16:24:07 2016 +0530

    Fix opRet value for volume info --xml call on non-existent volume
    
    The opRet field was being assigned to 0 in the XML output when a
    gluster volume info --xml call is made on a non-existent volume.
    This change assigns a value of -1 to opRet for volume info calls
    for non-existent volumes. Other fields like opErrno and opErrstr
    are also assigned relevant values
    
    Change-Id: I3920c602328f74252c87bb521f5a43d4bdc7d44d
    BUG: 1321836
    Signed-off-by: Samikshan Bairagya <samikshan@gmail.com>
    Reviewed-on: http://review.gluster.org/13843
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: darshan n <dnarayan@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 4797ca3778d82a671716d4913c14f285591ae959
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jun 13 12:00:40 2016 +0530

    geo-rep: Safely handle if unliked GFID not present in data list
    
    If unlinked GFID is not present in data list to be synced then
    Geo-rep worker was crashing with KeyError. Handled KeyError with
    this patch.
    
    BUG: 1345744
    Change-Id: I5a1c9ca4473e32606df2e5c7e26c95faf55d44c0
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14706
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit a4d35ccb8afeefae4d9cdd36ac19b0e97d0d04d0
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Jun 13 12:26:24 2016 +0530

    cluster/dht: initialize cbk before attempting inode-link
    
    Otherwise inode-link failures in selfheal codepath will result in a
    crash.
    
    Change-Id: I9061629ae9d1eb1ac945af5f448d0d8b397a5022
    BUG: 1345748
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14707
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b5c492dfea2d2e2075aa88d7153fba57b06e739d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 16 10:21:53 2016 +0530

    cli: fix crash in arbiter keyword parsing
    
    A negative case like `gluster volume create volname arbiter 3 /bricks{1..3}`
    must not crash. 'arbiter' keyword is valid only for (3 way) replica volumes.
    
    The .t that is added will crash and create a core *without* the fix when
    run but will still pass all TESTs. Since the regression framework fails
    the .t if it creates a core,  we can consider it a valid test 'that
    fails without the fix'.
    
    Change-Id: Ie2d7ced66025ea3617d30f6f823b22401e6d2fde
    BUG: 1346821
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14738
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ae4a410cb411c3f1b5ebac9d49d47e2fc00c9a74
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 16 11:24:30 2016 -0400

    glusterd: unsafe strcat, strncat use in glusterd_op_stage_gsync_create()
    
    SuSE build system post-compile analysis aborts pkg build due to
    unsafe strcat, strncat usage.
    
    Change-Id: I52ac41e1172d0c1e5695a91b9f731cc9e7de4db4
    BUG: 1347354
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14745
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b8ac20e888fbacad9d90cd8f1c6ff8579a5cefe9
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jun 6 06:29:40 2016 -0400

    gfapi: Fix IO error caused when there is consecutive graph switches
    
    Issue:
    Consider a simple situation, where glfs_init() is done, i.e. initial
    graph is up. Now perform 2 volume sets that results in 2 client side
    graph changes. After this perform some IO, the IO fails with ENOTCON.
    The only way to recover this client is i guess another graph switch
    or restart.
    
    What actually is happening from code perspective:
    Initial graph lets say A, followed by 2 consecutive graph switches
    to B and C without any IO those two switches.
    
    - graph_setup (A) as a result of GF_EVENT_CHILD_UP, and
    fs->next_subvol = A
    
    - glfs_init() results in fs->active_subvol = A, fs->next_subvol = NULL
    
    - graph_setup (B) as a result of GF_EVENT_CHILD_UP, and
    fs->next_subvol = B
    
    - graph_setup (C) as a result of GF_EVENT_CHILD_UP, and
    fs->next_subvol = C. It also sees that the previous graph B was never
    set as fs->active_subvol, i.e. no IO or anything happened on B, so
    can safely send GF_EVENT_PARENT_DOWN (by calling glfs_subvol_done(B)).
    This parent down on B, results in child_down(B), which is fine.
    But child_down also triggers graph_setup(B).
    
    - graph_setup(B) as a result of GF_EVENT_CHILD_DOWN, and
    fs->next_subvol = B, and GF_EVENT_PARENT_DOWN on C as explained
    above. This again leads to GF_EVENT_CHILD_DOWN on C.
    
    - graph_setup(C) as a result of GF_EVENT_CHILD_DOWN, and
    fs->next_subvol = C, and GF_EVENT_PARENT_DOWN on B as explained
    above.
    
    Thus both the graphs B and C are disconnected, and hence the ENOTCON
    
    Solution:
    Remove the call to graph_setup() when the event is GF_EVENT_CHILD_DOWN.
    It don't see any reason why graph_setup should be called when there is
    child_down. Not sure what the original reason was, to have graph_setup
    in child_down. git hostory shows the first patch itself had this call.
    
    Change-Id: I9de86555f66cc94a05649ac863b40ed3426ffd4b
    BUG: 1343038
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14656
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c04df79dc453ef5cb7b3a0ca8ba14598da6189ac
Author: Shyam <srangana@redhat.com>
Date:   Fri May 27 14:00:40 2016 -0400

    io-stats: Fix io-stat dump to dump at all levels
    
    Previous commit to fix the bug, where io-stat-dump was overwriting
    the dump file when the client and a brick was on the same host,
    failed to consider the existing behaviour where io-stats can
    help generate closely correlated set of stats across clients
    and bricks, by triggering the dump using the same command.
    
    This was introduced in commit:
    0facb11220aea20a6573b656785922219c9650cf
    
    Further, by limiting the first io-stat to unwind the dump request,
    there is no way to trigger other io-stat xlators in the stack to
    dump their stat information.
    
    This bug hence is being fixed by this commit keeping the
    following in mind,
    - We need to trigger io-stat-dump for all instances in the
    graph when this attr is set
    - We need to write the output to different files, so that
    they do not overwrite each others data
    - We need to prevent this xattr from being set on the path
    that is used to trigger the io-stat-dump information
    
    Change-Id: I31ec380f0d85e10313a9d7b977da0e1ec74638a6
    BUG: 1322825
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/14552
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3b69e25c0f3cf0b958fbd2b8459712ad21239caa
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 8 16:56:26 2016 +0530

    geo-rep: Error message cleanup
    
    If ssh returns 127 that means the remote gsyncd path is wrong
    or push-pem failed during create. Existing error message was
    pointing old documentation.
    
    Change-Id: Ifbbb4a604fc0ae0fd5cb2746df6363bf28cde1e9
    BUG: 1343943
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14673
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit a15bd4ad9f0375549cb3ae2d87cfaba6c5773f40
Author: Apeksha D Khakharia <akhakhar@redhat.com>
Date:   Wed May 18 16:41:30 2016 +0530

    distaf: Added libraries to setup nfs-ganesha in gluster through distaf
    
    Change-Id: Ifc4c6aa76f2fc6fb7a2de06c2fc458b0015c6951
    BUG: 1337160
    Signed-off-by: Apeksha D Khakharia <akhakhar@redhat.com>
    Reviewed-on: http://review.gluster.org/14416
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: M S Vishwanath Bhat <msvbhat@gmail.com>

commit 2808eac9b6d08d1dd9fbafb7e2aeac92f50de0dc
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Tue May 10 17:46:36 2016 +0530

    distaf: Added library functions for gluster tiering operations
    
    Change-Id: I08d77bdc1ca3f804e35b69abe39df2049eb7cf70
    BUG: 1334721
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14283
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: karthick
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 4c08d36e7c6f189499f2340eb529b7f4ceff57f6
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jun 9 16:53:19 2016 +0200

    cluster/dht: Fix unsafe iteration on inode->fd_list
    
    When DHT traverses the inode->fd_list, it does that in an unsafe
    way that can generate races with fd_unref() called from other threads.
    
    This patch fixes this problem taking the inode->lock and adding a
    reference to the fd while it's being used outside of the mutex
    protected region.
    
    A minor change in storage/posix has been done to also access the
    inode->fd_list in a safe way.
    
    Change-Id: I10d469ca6a8f76e950a8c9779ae9c8b70f88ef93
    BUG: 1344340
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/14682
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e740b700975bdb1014ede99c65731095bdf81a72
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 13 11:34:51 2016 -0400

    api: use versioned symbols for minor ABI change
    
    No need to expand the API/ABI. E.g., see how glfs_lookupat
    changed between 3.7.0 and 3.7.4 IIRC
    
    (I originally argued against versioning the library. I wanted
    to just add new functions as they were needed, as was initially
    done for glfs_ipc and glfs_ipc_xd in the master branch for 4.0.
    But others strongly wanted versioning.)
    
    Having made the decision to use versioning, I believe we should
    continue. At least until we have a public decision that we're
    no longer going to use versioning.
    
    Change-Id: I0c3b2c1cbb297ae2b2864b647c224922987d74ad
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14717
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 04828f569eede11e11433bf099dbb7cb39c3f3b9
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Tue Jun 14 15:07:51 2016 +0530

    glusterd/geo-rep: remove unused variables
    
    cleanup - remove unused variables, fix return
    value.
    
    Change-Id: I77b663bdae0ffe7667486f5f4e2355ef9757f960
    BUG: 1346211
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/14728
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d079d6f6ec21955a600feb43e1154cabf18008ff
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Apr 11 17:31:58 2016 +0530

    performance/decompounder: Add graph for decompounder xlator
    
    This xlator will fall below protocol/server.
    This is mandatory xlator without any options.
    
    Observed that the callback for decompounder translator
    was not added which was causing volume start
    to fail.
    Added cbks for decompounder.
    
    Change-Id: I3e16a566376338d9c6d36d6fbc7bf295fda9f3a6
    BUG: 1335019
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13968
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 352758e2f2548a5a66186e8b3179b1e3ee11984c
Author: Anoop C S <anoopcs@redhat.com>
Date:   Mon Jun 13 15:55:39 2016 +0530

    api: Fix a typo in gfapi logging message framework
    
    Change-Id: I8a44a37a73f0c92783aecac8187247db98957070
    BUG: 1202274
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/14709
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit d25237709278f9530c7a3989a37254c628539375
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Jun 11 18:43:42 2016 +0530

    cluster/ec: Unlock stale locks when inodelk/entrylk/lk fails
    
    Thanks to Rafi for hinting a while back that this kind of
    problem he saw once. I didn't think the theory was valid.
    Could have caught it earlier if I had tested his theory.
    
    Change-Id: Iac6ffcdba2950aa6f8cf94f8994adeed6e6a9c9b
    BUG: 1344836
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14703
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Tested-by: mohammed rafi  kc <rkavunga@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>

commit 547563d284e40fc9cdecda4c1ecde372ed1a01c5
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Jun 3 12:44:14 2016 +0530

    glusterd/snapshot: free resource from the owner of memory
    
    We are freeing memory from a function which is not the
    owner of the memory.
    
    Free should happen from the owner of resources.
    
    Change-Id: If8772ba27f9eb65881dcdddde8d7dc431c1c0ee8
    BUG: 1341796
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/14634
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c158742fb52ae1f6d3576c64caf42b67d784a3e3
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Jun 13 15:28:41 2016 +0530

    quota : rectify quota-deem-statfs default settings
    
    Change-Id: I75c47c4a0f0eb898b5e32efe7f0a6a558d7f8007
    BUG: 1345846
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/14708
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit fb013a9db2cc019d36b07644f24e6c15ed39725c
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Jun 13 12:42:47 2016 +0200

    cluster/ec: Fix race in timer cancellation
    
    A race in timer cancellation for delayed unlock could cause a crash
    if the cancelling thread fails to cancel the timer because it has
    already been fired but not executed, and the callback is scheduled
    out of the CPU, delaying it until the thread has released important
    resources needed by the callback.
    
    This patch improves the handling of this case to make it robust.
    
    Change-Id: I5c8a8c6610c5136f71b938aa78b5878ba05238d4
    BUG: 1345855
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/14712
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e0b057cf28abc534f1fc74f4ea921c78a52ab6fe
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jun 9 17:29:26 2016 +0200

    cluster/ec: Fix invalid __fd_unref() call
    
    __fd_unref() doesn't do any cleanup, so it cannot be called to release
    fd references, specially if it's the last reference.
    
    The code has been changed to avoid a call to this function.
    
    In the previous version we always tried to keep the newest fd in the
    ec_lock_t structure. However this is not necessary. We'll always keep
    one reference to an open file on the same inode. It's irrelevant if
    the reference is new or old.
    
    The function __fd_unref() has also been removed from fd.h to avoid being
    used in the future since it's useless as it's defined now.
    
    Change-Id: Ia728777fc8e464758d5ea4d3bf020f0603919039
    BUG: 1344396
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/14683
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 40a7537556a7eb0a7c90ec6e7e2fd4014beae092
Author: karthik-us <ksubrahm@redhat.com>
Date:   Fri Jun 3 01:04:01 2016 +0530

    features/worm: fixed issue with write FOP for normal files
    
    The write FOPs on normal files were being blocked after the recent change.
    It should fail only for the WORM and WORM-Retained files, and should pass
    for a normal file.
    Using auto-commit period to check for dormant files instead of retention period.
    
    Change-Id: I30f82d4de2ea2c59c1eb7b4449ba6a60e568cfd5
    BUG: 1342259
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: http://review.gluster.org/14619
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit 1a348bfaeb9f2a50ec8ce27e5477e9b430c58b3c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed May 25 11:56:56 2016 +0530

    geo-rep: Handle stime/xtime set failures
    
    While setting stime/xtime, if the file or directory is already
    deleted then Geo-rep will crash with ENOENT.
    
    With this patch, Geo-rep will ignores ENOENT since stime/xtime can't
    be applied on a deleted file/directory.
    
    Change-Id: I2d90569e51565f81ae53fcb23323e4f47c9e9672
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1339471
    Reviewed-on: http://review.gluster.org/14529
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit ccb906c8a8139b66130192080020709bfc6d0dc3
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu May 19 10:43:53 2016 -0400

    cluster/tier: fix detach tier error message
    
    Do not refer to obsolete syntax when throwing an error on detach tier.
    Throw a warning if the user tries to commit a detach tier before
    starting (or completing) the decommission process.
    
    Change-Id: I9df28c1b42b8ab1790e1db5c0cd518432146c1d1
    BUG: 1337227
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/14438
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 53cc21c5a5df434039f587644c336bf4f7264f45
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jun 10 14:25:14 2016 +0530

    tests: fix bug-1344407-volume-delete-on-node-down.t
    
    Test was earlier starting the volume which will always make volume delete fail.
    so it was actually not validating BZ 1344407
    
    Change-Id: I6761be16e414bb7b67694ff1a468073bfdd872ac
    BUG: 1344407
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14693
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 8c717491413295a7045ebf9a2b1df630b7cbac76
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jun 1 17:57:41 2016 +0530

    afr: Consider ENOSPC and EDQUOT as symmetric errors
    
    Problem:
    Since commit 8eaa3506ead4f11b81b146a9e56575c79f3aad7b, in replica 3, if a
    brick is down and a create fails on the other 2 brick with EDQUOT, we consider
    it an unsymmetric error and hence do not do post-op. So the dirty xattr
    remains set on the parent dir, leading to conservative merges during heal when
    all bricks are up. i.e. a file deleted on the source might re-appear after heal.
    
    Fix:
    Consider ENOSPC and  EDQUOT as symmetric errors since there is no
    possibility of partial inode or entry modification operations possible when
    quota is enabled. IOW, if quota reports EDQUOT, the no. of bytes written
    (or not written) will be the same on all bricks of the replica.
    Likewise, the entry operation (create, mkdir...) will either succeed or
    not succeed on all bricks.
    
    Change-Id: Iacb1108e9ef4a918e36242fb4a957455133744e9
    BUG: 1341650
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14604
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>

commit 2775dc64101ed37c8d9809bf9852dbf0746ee2b6
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Jun 10 18:23:43 2016 +0530

    libgfapi/upcall : prepend "glfs_" to callback_arg, callback_inode_arg
    
    Change-Id: I371525775db4f6a4d69beb94baaa53d17b16fb41
    BUG: 1344714
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14702
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 3474aa85e399a92d3ee9159a2d066d4bd73611a0
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jun 10 16:33:04 2016 +0530

    tiering/ctr: Fix strcpy coverity
    
    Change-Id: I6cffba3e09a023f105dbf2975cc9a3ae1a965c31
    BUG: 1344686
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14696
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 3bc419d8014877f64e57dc3368b0609396ec0d12
Author: Poornima G <pgurusid@redhat.com>
Date:   Sun Jun 5 00:06:11 2016 -0400

    protocol: Add framework to send transaction id with recall
    
    Issue:
    The upcall(cache invalidation/recall) event is sent from the bricks
    to clients. In AFR/EC setup, it can so happen that all the bricks
    will send the upcall for the same event, and if AFR/EC doesn't filter
    out these duplicate notifications, the logic above cluster xlators
    can fail.
    
    Solution:
    Use transaction id to filter out duplicate notifications.
    
    This patch adds framework for duplicate notifications.
    AFR/EC can build up on this patch for deduping the notifications
    
    Change-Id: I66b08e63b8799bc5932f2b2545376138a5701168
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14647
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a837357c5c7873bf19155e76bf6c251fa799a605
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Jun 9 16:19:37 2016 +0530

    cluster/ec: Pass xdata to dht in case of error
    
    Problem: In case of mkdir failure, dht expects
    error information so that it can act accordingly.
    Aftre adding bricks and re balance, layout gets
    changed. Fop "mkdir" with old layout returns EIO.
    EC gets this error in xdata but does not pass it
    back to dht. In this case dht will not be able to
    take corrective action.
    
    Solution: Return xdata back to dht
    
    Change-Id: I24def8038e6880607689b7b046dc6428f564c6ab
    BUG: 1344277
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/14679
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 5016cc548d4368b1c180459d6fa8ae012bb21d6e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jun 9 18:22:43 2016 +0530

    glusterd: fail volume delete if one of the node is down
    
    Deleting a volume on a cluster where one of the node in the cluster is down is
    buggy since once that node comes back the resync of the same volume will happen.
    Till we bring in the soft delete feature tracked in
    http://review.gluster.org/12963 this is a safe guard to block the volume
    deletion.
    
    Change-Id: I9c13869c4a7e7a947f88842c6dc6f231c0eeda6c
    BUG: 1344407
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14681
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit c62493efadbcf5085bbd65a409eed9391301c154
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Mon Jun 6 14:44:35 2016 +0530

    glusterd/geo-rep: Avoid started status check if same host
    
    After carrying out add-brick, session creation is carried out
    again, to involve new brick in the session. This needs to be done,
    even if the session is in Started state.
    
    While involving slave uuid as part of a session, User is warned
    if session is in Started state. This check needs to be avoided
    if it is same slave host and session creation needs to be proceeded.
    
    Change-Id: Ic73edd5bd9e3ee55da96f5aceec0bafa14d3f3dd
    BUG: 1342979
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/14653
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 79dfe7d197ced45bd3b84f71d5c889e95f4dec1a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jun 7 17:15:56 2016 +0530

    libglusterfs: Negate all but O_DIRECT flag if present on anon fds
    
    This is to prevent any unforeseen problems that might arise due to
    writevs and readvs being wound with @flag parameter containing
    O_TRUNC or O_APPEND especially wrt translators like sharding and ec
    where O_TRUNC write or O_APPEND write on individual shards/fragments
    is not the same as O_TRUNC write or O_APPEND write as expected by the
    application.
    
    Change-Id: I9e5206a6ce2b1b70df61ff23b1c961cf25bf7ff9
    BUG: 1342171
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14665
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 3bd4b1529817d4ce40c2b9654044e6230cbf7233
Author: Bipin Kunal <bkunal@redhat.com>
Date:   Tue Jun 7 18:30:16 2016 +0530

    nfs: build exportlist with multiple groupnodes
    
    The EXPORT procedure of the MOUNT protocol does not correctly create
    structures for the 'groupnodes' in the reply. Each 'groupnode' should be
    a single entry in the 'nfs.rpc-auth-allow' volume option. Because the
    value is handled as a single string, the encoding of the
    groupnode->gr_name fails when the value of the volume option is longer
    than 255 characters.
    
    In the error case, encoding the EXPORTS reply fails, and the waiting
    'showmount' command will not receive a reply and times out.
    
    Splitting the allowed entries and creating a groupnode for each one
    prevents the too long ->gr_name. This is following the structures for
    the EXPORTS reply in the MOUNT protocol more correctly as well. Note
    that the contents of ->gr_name is expected to be server dependent.
    
    Change-Id: Ibbabad581cc9aa00feb80fbbc851a1b10b28383d
    BUG: 1343286
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14667
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: bipin kunal <kunalbipin@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit ab88bad8fe40bd9a9106b02857abfdc51a3284cd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 31 09:05:28 2016 +0530

    tests: Add a test for conservative merge with granular esh
    
    Change-Id: Ib8ada912451bf80b640d25e6e3a824216d055b5b
    BUG: 1332566
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14601
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 51e1028373b4a4082a771001b813d6f19aeacb37
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jun 3 18:22:22 2016 +0530

    afr: afr-pending-xattr fallback check
    
    Commit 6e635284a4411b816d4d860a28262c9e6dc4bd6a introduced a comma
    separated list of values to be used as AFR's pending changelogs. If
    this xlator option is missing in the volfile, fall back to using client
    xlator names for constructing the pending changelog names.
    
    Also, since the aforementioned commit was reverted from 3.7 and 3.8
    branches, introduce GD_OP_VERSION_3_9_0 and change the op-version for this
    feature to GD_OP_VERSION_3_9_0.
    
    Change-Id: I3639b9ab475bd8d9929cc7527d9f4584dee1ad1b
    BUG: 1285152
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14642
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit ea4d4175ab3fc5cc1545ebde4d8d35ba0bf4aa3f
Author: Shyam <srangana@redhat.com>
Date:   Fri Jun 3 14:58:16 2016 -0400

    posix2: Creation of experimental shell for posix2 xlator
    
    DHT2 comes with a new backend on-disk format, that requires
    a new backend storage xlator. This experimental project will
    house the artifacts for the same.
    
    Change-Id: I71a3d60a0415d0c23b2294a02b838810fa8f101f
    BUG: 1338991
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/14646
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8489fe576b6cf148fabcaeee79f298c41858133e
Author: Bipin Kunal <bkunal@redhat.com>
Date:   Tue Jun 7 17:59:27 2016 +0530

    xdr/nfs: free complete groupnode structure
    
    The groupnode->gr_next pointer is not traversed upon free. This is
    currently not a problem, because the pointer is never used. However the
    correct way to free a groupnode should check the ->gr_next pointer and
    free any of the groups that it encounters.
    
    This problem was identified while correcting a problem with the MOUNT
    protocol. The change "nfs: build exportlist with multiple groups" starts
    to use ->gr_next.
    
    Change-Id: I9d04eaf4c65bdb8db136321d60e70789da1739d7
    BUG: 1343286
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14666
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: bipin kunal <kunalbipin@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit bdde0cfa1d5848e59d20c1adc19ee1b687eec66a
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu Jun 4 14:55:17 2015 +0530

    clang-analyzer: adding clang static analysis support
    
    clang static analyzer is a source code analysis tool that
    finds bugs in C, C++.
    
    This patch automates clang analyzes part by integrating
    it with 'make clang-check'
    
    clang-checker.sh: runs clang analyzer with and without the
    HEAD commit, and shows the bugs introduced by HEAD commit (if any)
    
    sample report:
    
    $[ glusterfs ]: make clang-check
    
    ================ Clang analyzer in progress ================
    ...
    
    BASELINE BUGS LIST (before applying patch):
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Out of bound array access --> 3
    Memory leak --> 1
    Unix API --> 24
    Dead increment --> 5
    Dereference of null pointer --> 1995
    Uninitialized argument value --> 2
    All Bugs --> 2872
    Called function pointer is null null dereference --> 4
    Dead initialization --> 49
    Dead assignment --> 691
    Undefined allocation of 0 bytes CERT MEM0 C CWE --> 5
    Argument with nonnull attribute passed null --> 84
    Result of operation is garbage or undefined --> 9
    
    TARGET BUGS LIST (after applying patch):
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Out of bound array access --> 3
    Memory leak --> 1
    Unix API --> 24
    Dead increment --> 5
    Dereference of null pointer --> 1995
    Uninitialized argument value --> 2
    All Bugs --> 2875
    Called function pointer is null null
    dereference --> 4
    Dead initialization --> 49
    Dead assignment --> 694
    Undefined allocation of 0 bytes CERT MEM0 C CWE --> 5
    Argument with nonnull attribute passed null --> 84
    Result of operation is garbage or undefined --> 9
    
    SUMMARY OF CLANG-ANALYZER:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    Extra 3 Bug[s] Introduced in: Dead assignment
    
    Patch Value given by Clang analyzer '-1'
    
    Explore complete results at
    /home/user/work/glusterfs/baseline/results/index.html
    /home/user/work/glusterfs/target/results/index.html
    
    ================= Done with Clang Analysis =================
    
    Change-Id: I512e33cfc02885a111152fbc1832144261dda1da
    BUG: 1228142
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11083
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 093902319ccc3d6bbb954fc40944a9e23aa68344
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Jun 6 18:10:09 2016 +0530

    nfs : store sattr properly in nfs3_setattr() call
    
    nfs3_setattr stores the input arguments in cs->stbuf.
    However, inode/entry resolution code overwrites cs->stbuf
    after a successful resolution, thereby overwriting the
    input arguments with iatt values stored on backend.
    Hence operations like chmod/chown turns out to be a NOP.
    Specifically following are the functions that overwrite
    cs->stbuf:
    
        nfs3_fh_resolve_inode_lookup_cbk
        nfs3_fh_resolve_entry_lookup_cbk
    
    Since we resort to inode resolution only when inode is not
    found in inode table and lru limit guards the number of
    inodes in itable, we run into this issue only when the data
    set is bigger than lru limit of itable.
    
    Fix is to store input arguments in a member other than
    cs->stbuf.
    
    Thanks Du for suggesting the fix
    
    Change-Id: I7caef48839d4f177c3557d7823fc1d35c8294939
    BUG: 1318204
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14657
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit eb1744582d57d0f9fe08275781800c0c3459697f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon May 2 16:51:10 2016 +0530

    core, shard: Make shards inherit main file's O_DIRECT flag if present
    
    If the application opens a file with O_DIRECT, the shards'
    anon fds would also need to inherit the flag. Towards this,
    shard xl would be passing the odirect flag in the @flags parameter
    to the WRITEV fop. This will be used in anon fd resolution
    and subsequent opening by posix xl.
    
    Change-Id: Iddb75c9ed14ce5a8c5d2128ad09b749f46e3b0c2
    BUG: 1342171
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14191
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit eb7ba8984c5e66b57d592f9da606fbdd1133df3b
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Jun 6 10:17:54 2016 +0530

    cluster/ec: Restrict the launch of replace brick heal
    
    Problem: When features.cache-invalidation is ON, a lot of
    ec_notify function gets called which leads to launch of
    too many heals. This leads to no heal completion,
    which causes accumulation of heals.
    
    Solution: ec_launch_replace_heal should not be launch
    for every event. Replace brick will trigger a child up
    event and then only this heal function should be called.
    
    Change-Id: I57b44c6a279d57230daea1d93229be6069245b7d
    BUG: 1342796
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/14649
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 9b4169255224b725e7d3455c63e2f9db33b0f3bf
Author: Dustin Black <dblack@redhat.com>
Date:   Thu Jun 2 16:15:25 2016 -0400

    nfs: fix a typo in the help text for option rpc-auth.addr.reject
    
    Added space to .description
    
    Reported-by: James Shubin <purpleidea@gmail.com>
    Change-Id: Ie4dd8774567ac4d8e1e8ec39aa3ab595d037101a
    BUG: 1005257
    Signed-off-by: Dustin Black <dblack@redhat.com>
    Reviewed-on: http://review.gluster.org/14621
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 04b5fcb82e90250cdeaa6f0e1e4c4debdeb0e3fa
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 3 04:22:27 2016 +0530

    features/shard: Don't modify readv size
    
    For o-direct reads application sends aligned size which needs to be
    sent as is, otherwise o-direct writes where the file-size is not
    aligned fails.
    
    Change-Id: I097418ad92eda6c835d7352a3d2e53ea9d8e2424
    BUG: 1342298
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14623
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 66cc92c25ec2680e50a6b3edda2e027635c380db
Author: Dustin Black <dblack@redhat.com>
Date:   Thu Jun 2 17:01:32 2016 -0400

    Corrected default text for ARGP_FUSE_USE_READDIRP_KEY
    Changed from "off" to "yes" per BZ 1222915
    
    Change-Id: Idffffee621560adb4cc02c1001d1ae21ca11941f
    BUG: 1222915
    Signed-off-by: Dustin Black <dblack@redhat.com>
    Reviewed-on: http://review.gluster.org/14622
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d4b9d7f120b8742e68b2d020b3ed50aa40394a89
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Tue May 24 15:06:27 2016 +0530

    distaf: Added library functions for gluster quota operations
    
    Change-Id: I4968918fc2bf5b67e3415fc7b9beb1b414ca6eb4
    BUG: 1332952
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14210
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: M S Vishwanath Bhat <msvbhat@gmail.com>

commit 04b5886132ee0fe84011033cd2db08285cc75e31
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jun 1 14:40:13 2016 -0400

    common-ha: race/timing issue setting up cluster
    
    The ganesha_grace resource agent can start before the ganesha_mon
    resource agent, with the result that the crm_attribute that
    ganesha_grace expects to find has not been created yet.
    
    This is never (never? Or just so rarely that it has never actually
    been seen during development) seen with four nodes, but with just
    two nodes it's very repeatable.
    
    Note that when long (FQDN) names are used it is not unexpected to
    see Failed Actions in the output of `pcs status`, e.g.:
    
    * nfs-grace_monitor_5000 on node1.fully.qualified.domain.name.com
    'unknown error' (1): call=20, status=complete, exitreason='none',
    last-rc-change='Wed Jun  1 12:32:32 2016', queued=0ms, exec=0ms
    * nfs-grace_monitor_5000 on node2.fully.qualified.domain.name.com
    'unknown error' (1): call=18, status=complete, exitreason='none',
    last-rc-change='Wed Jun  1 12:32:42 2016', queued=0ms, exec=0ms
    
    and as long as all the ganesha_grace_clone and cluster_ip-1
    resource agents are in Started state then this is okay.
    
    Change-Id: I726c9946ceb1ca92872b321612eb0f4c3cc039d8
    BUG: 1341768
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14607
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 124425aef8118116d0bd1daa8269ab2c348b2cb9
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Thu May 19 21:13:04 2016 +0530

    glusterd/geo-rep: upgrade path when slave vol uuid involved
    
    slave volume uuid is involved in identifying a geo-replication
    session.
    
    This patch addresses upgrade path, where existing geo-rep session
    is gracefully upgraded to involve slave volume uuid.
    
    Change-Id: Ib7ff5109b161592f24fc86fc7e93a407655fab86
    BUG: 1337473
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14425
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit b347cf85300193ab83dcfaca63c39a4907fbf730
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Apr 14 16:19:40 2016 +0530

    cluster/ec: Add/Modify description for eager-lock option
    
    This patch provides description for disperse.eager-lock
    option for disperse volume.
    
    It also modifies the description for cluster.eager-lock
    option to indicate that this option is only for replica
    volume.
    
    Change-Id: Ie73298947fcaaa6aaf825978bc2d27ceaff386d2
    BUG: 1327171
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13999
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9e0cdf1d2393d7bdb0eac019e70dce7c5f4f59c9
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jun 2 19:45:03 2016 +0530

    posix, shard: Use page-aligned buffer for o-direct reads
    
    and also make shard_readv_do() pass the correct flags when
    the original fd is opened with O_DIRECT.
    
    Change-Id: Ic2f8ad900743ed3f7cab56948bcf1358d247a311
    BUG: 1342171
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14639
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 42b2c259658b017ec08ecf419c7ea83112779236
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 3 13:07:24 2016 +0530

    geo-rep: Fix volume stop with geo-rep session
    
    The slave volume uuid is appended to slave_url
    which is saved in 'gsync_slaves' dictionary with
    the commit "http://review.gluster.org/13111".
    But the gsyncd expects slave_url with out slave
    volume uuid otherwise it fails which in turn
    fails volume stop with geo-rep. This patch
    fixes the same.
    
    Change-Id: I036f4fce43115ff848daebfe1b2c58765cffab5a
    BUG: 1342420
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14636
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 0556ac5c0ded2eb942096268b8b94f30e9af10e0
Author: Susant Palai <spalai@redhat.com>
Date:   Mon May 9 01:12:17 2016 +0530

    dht : add metalock/unlock
    
    Change-Id: I842a7ea1b286f1b893b200fe647597e7fd0f2105
    BUG: 1331720
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14252
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 19b8c09709c7aeecb84eafb02de797a49a004638
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Apr 22 15:20:39 2016 +0530

    posix/lock: implement meta-lock/unlock functionality
    
    problem : The lock state needs to be protected when rebalance is reading the
    lock state on the source. Otherwise there will be locks left unmigrated.
    Hence, to synchronize incoming lock requests with lock-migration, meta lock
    is needed. Any new lock request will be queued if there is an active meta-lock
    and with sucessful lock migration, will be unwound with EREMOTE, so that
    dht module can wind the request to the correct destination.
    
    On a successful lock migration, "pl_inode->migrated" flag is enabled. Hence,
    any further request would be unwound with EREMOTE and will be redirected to
    new destination.
    
    More details can be found here:
    https://github.com/gluster/glusterfs-specs/blob/master/accepted/Lock-Migration.md
    
    design discussion:
    https://www.gluster.org/pipermail/gluster-devel/2016-January/048088.html
    
    Change-Id: Ief033d5652b5ca4ba6f499110a521cae283d6aba
    BUG: 1331720
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14251
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 03d523504230c336cf585159266e147945f31153
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Jun 1 23:01:37 2016 +0530

    glusterd/snapshot: remove quota related options from snap volfile
    
    enabling inode-quota on a snapshot volume is unnecessary, because
    snapshot is a read-only volume. So we don't need to enforce quota
    on a snapshot volume.
    
    This patch will remove the quota related options from snapshot
    volfile.
    
    Change-Id: Iddabcb83820dac2384924a01d45abe1ef1e95600
    BUG: 1341796
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/14608
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit bc525b01002d7649be0ac28c5761c8ce92b6a658
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jul 20 16:44:32 2015 +0530

    glusterd: volgen and volume set changes for leases
    
    Add leases xlator in volgen and also add corresponding volume set options
    
    Change-Id: Ic5de50cdb87eaf6a833e739bc7e08fecbeca3de3
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/11722
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 851a58733fe9f78b03819080e4a6883c69d41032
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Tue May 24 15:23:43 2016 +0530

    Added timeout value to wait for rebalance to complete and removed older rebalance library file
    
    Change-Id: I89e2e436ec9306a80a87faab6d6e53f547ce4e42
    BUG: 1339166
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14515
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: M S Vishwanath Bhat <msvbhat@gmail.com>

commit 3ae22b61f9aa01f0a97f8f1b3ef75add74c02f7d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 1 12:42:30 2016 +0530

    glusterd/snapshot: Fix snapshot creation with geo-rep
    
    The construction of path to geo-rep session directory
    is broken with the commit "http://review.gluster.org/13111"
    as it saves the slave volume uuid in 'gsync_slaves'
    dictionary. This patch fixes the same.
    
    Change-Id: Ic7fc3c37d368549feb44b3a08d60157ce61227c3
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    BUG: 1341474
    Reviewed-on: http://review.gluster.org/14595
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit e800c00df1474504032ead25a0bcbbc92c1d6fec
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 31 14:00:35 2016 -0400

    build: RHEL7 unpackaged files .../hooks/S57glusterfind-delete-post.{pyc,pyo}
    
    building on Real RHEL7 (versus mock?) results in installed (but
    unpackaged) files found:
    /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post.pyc
    /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post.pyo
    
    The same .spec file on Fedora 23 and RHEL6 does not encounter this
    issue.
    
    (Replacing the RHEL7 /usr/lib/rpm/brp-python-bytecompile file with
    the one from Fedora 23 also makes the problem go away. But we are
    probably not going to get a fixed rpm/rpmbuild soon enough to make
    this go away by itself.)
    
    Change-Id: Ib3db41cf0b7334a41b5174bba0c57e9aeb13407c
    BUG: 1341294
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14590
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 24dd33929bbbc9a72360793048f17bf4e6cec8a3
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Fri May 6 13:04:38 2016 -0400

    libglusterfs (timer): race conditions, illegal mem access, mem leak
    
    While investigating gfapi memory consumption with valgrind, valgrind
    reported several memory access issues.
    
    Also see the timer 'registry' being recreated (shortly) after being
    freed during teardown due to the way it's currently written.
    
    Passing ctx as data to gf_timer_proc() is prone to memory access
    issues if ctx is freed before gf_timer_proc() terminates. (And in
    fact this does happen, at least in valgrind.) gf_timer_proc() doesn't
    need ctx for anything, it only needs ctx->timer, so just pass that.
    
    Nothing ever calls gf_timer_registry_init(). Nothing outside of
    timer.c that is. Making it and gf_timer_proc() static.
    
    Change-Id: Ia28454dda0cf0de2fec94d76441d98c3927a906a
    BUG: 1333925
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14247
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a04eaf366779a0632e5b9cdd6d63de0eb62f7449
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon May 23 14:31:51 2016 +0530

    __inode_ctx_put: fix mem leak on failure
    
    up on failure case __inode_ctx_put need to free the allocated memory
    
    Indirect leak of 104 byte(s) in 1 object(s) allocated from:
        #0 0x496669 in __interceptor_calloc (/usr/local/sbin/glusterfsd+0x496669)
        #1 0x7f8a288522f9 in __gf_calloc libglusterfs/src/mem-pool.c:117
        #2 0x7f8a17235962 in __posix_acl_ctx_get xlators/system/posix-acl/src/posix-acl.c:308
    
    Change-Id: I0ce6da3967c55931a70f77d8551ccf52e4cdfda3
    BUG: 1338733
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14505
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 46c0b791d528bebf1168972a34f7483bfe683ba3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 31 14:49:33 2016 +0530

    cluster/afr: Unwind with xdata in inode-write fops
    
    When there is a failure afr was not unwinding xdata to xlators above.
    xdata need not be NULL on failures. So it is important to send it
    to parent xlators.
    
    Change-Id: Ic36aac10a79fa91121961932dd1920cb1c2c3a4c
    BUG: 1340623
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14567
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit cb8f5e01f639cb6e8715b33bb725210cb0493887
Author: Oleksandr Natalenko <oleksandr@natalenko.name>
Date:   Tue May 17 16:45:44 2016 +0300

    glusterfsd/main: Add ability to set oom_score_adj
    
    Give the administrator a possibility to set oom_score_adj for glusterfs
    process. Applies to Linux only.
    
    Change-Id: Iff13c2f4cb28457871c6ebeff6130bce4a8bf543
    BUG: 1336818
    Signed-off-by: Oleksandr Natalenko <oleksandr@natalenko.name>
    Reviewed-on: http://review.gluster.org/14399
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a89a9d266c439800286f281655d67f4e362dec32
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 31 21:51:22 2016 +0530

    features/index: Exclude gfid-type for '.', '..'
    
    index_get_gfid_type is assuming all names are gfids where as some of these
    entry->d_names can be '.' or '..'
    
    Thanks a lot to Nithya for RC
    
    BUG: 1336630
    Change-Id: I06ad688a5865ab25b4f6c8a91af8c7fb2ed62186
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14589
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit b06a77f3446d622f8159f08508f4d5063ec50339
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu May 19 05:04:13 2016 -0400

    leases: Fix the recall code path
    
    1. Replace frame->op usage with frame->root->op, as frame->op
       is not filled with appropriate value in all cases
    2. Add few log messages
    3. Fix boolean assignment
    
    Change-Id: I340f2200c1fcc4f4ce5a139b0fd22508cb8ac1e3
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14434
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e341d2827800e32997f888668597785178a40626
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 20 01:09:40 2016 +0530

    protocol/client:  Reflect readv/writev changes in filter-O_DIRECT description
    
    Commit 74837896c38bafdd862f164d147b75fcbb619e8f introduced filtering
    of O_DIRECT option even for readv/writev but the option description is not
    updated.
    
    Change-Id: I7c2b69fdb496ca27d1b06a458f2f3eab0d16d417
    BUG: 1322214
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14441
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit be00012e7be55d25870411f3e975db9a8e19c70a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 9 16:54:00 2016 +0530

    features/changelog: Change barrier notification mechanism
    
    The barrier notification mechanism was fd based and 'select'
    was being used. 'select' breaks when number of fds opened
    by brick process exceeds 1024. To avoid this and also
    the maintainance of pipe between notify and 'changelog_rollover',
    the pipe has been replaced with pthread condition signal
    and timed wait mechanism.
    
    Change-Id: I530ea90d9a06953f8b23b4e12d122872ee1925de
    BUG: 1334314
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14272
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit f55a973e581aaa25bbe38be83e007e1b2eaed659
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue May 24 14:33:54 2016 +0530

    snapshot/uss: client-side log is filled with "invalid-argument" error
    
    xdata is used without checking if it is NULL or not.
    
    Change-Id: Ib6ddaab28ec3b430b8d646aada0456d3cc9978cb
    BUG: 1339149
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/14511
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 03880f81dad9fd2a3a07c56a3cfbb994d44819b7
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu May 5 12:42:35 2016 +0530

    features/worm: updating function names & unwinding FOPs with op_errno
    
    - Added gf_worm prefix to some of the functions in worm-helper files so that
      they do not clash with other functions
    - Made the functions in worm.c static
    - Unwinding the FOPs with op_errno instead of using different unwind statements
    - Removed the multiple goto labels (wind & unwind)
    
    Change-Id: I3a2f114061aae4b422df54e91c4b3f702af5d0b0
    BUG: 1333263
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: http://review.gluster.org/14222
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1126ebcf667771267a47ea9749ed5f30a76d0d60
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue May 31 12:29:10 2016 +0530

    cluster/afr adding test case for http://review.gluster.org/#/c/14553/
    
    Change-Id: I23865343021ae65a36f6abc74d6bd594efd9dc7e
    BUG: 1340623
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14561
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 719e9f2228027a85df5c7b7b3e5fb4494bfbf186
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue May 24 18:52:52 2016 +0530

    gfapi/upcall : remove unused variable ret in glfs_h_find_handle
    
    The variable ret is declared in glfs_h_find_handle(), but never used.
    So while compiling following warning message will be printed.
    glfs-handleops.c: In function ‘glfs_h_find_handle’:
    glfs-handleops.c:1813:29: warning: variable ‘ret’ set but not used [-Wunused-but-set-variable]
             int                 ret = -1;
                                 ^
    
    Change-Id: I599b7a4e87184aacd6c937e946defd4e270509c4
    BUG: 1341007
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14524
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit d6442d8f4ac6d892cf5adc55ea5c34dcb01e1f26
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Mon May 30 17:34:24 2016 +0530

    geo-rep: update peers section in gsyncd conf
    
    Problem:
    Once Slave volume uuid is involved as part of a geo-rep session, it is
    possible to create the same geo-rep session with different (slave)host.
    
    But, it reflects default values for geo-rep configuration values originally
    configured for old geo-rep session.
    Reason is, slave host is used while saving config options in gsyncd.conf.
    With new slave host, it is not possible to retrieve those config values.
    
    Solution:
    Remove slave host related information from gsyncd.conf and have only master
    volume and slave volume as part of peers section.
    
    Also, during upgrade from old geo-rep session, update peers section to
    reflect only master volume and slave volume.
    
    Change-Id: I7debf35a09a28d030b706b0c3e5d82c9b0467d0e
    BUG: 1340853
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/14558
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit c3fdf4d973da6ffead7b316e7629f62a6139eb30
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Apr 11 11:07:17 2016 +0530

    cli: Add test for heal info with ssl on
    
    This test has been introduced to check
    if we get proper heal info after enabling
    management SSL.
    
    Change-Id: I9c7721293b18cc10090b8695e49b5f4c8c766c6c
    BUG: 1320388
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13959
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit b5590f1db641a22ea515c9c4760a593d3342ffa0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon May 9 16:53:19 2016 +0530

    storage/posix: Print offset,size and gfid too when readv fails
    
    ... for better debuggability.
    
    Here's a sample log:
    
    [2016-05-31 05:18:34.893951] E [MSGID: 113040] [posix.c:3089:posix_readv]
    0-dis-posix: read failed on gfid=3744d34b-f798-4ce2-b421-cc632a9903bd,
    fd=0x7f8b3c015abc, offset=131072 size=131072 [Invalid argument]
    
    Change-Id: I069c17fecbb01a4a2b5dea1eb482c7f56a191fd3
    BUG: 1341009
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14271
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit c8da5669a15ed6944cceb9d003789ff333754bff
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon May 30 21:01:29 2016 +0200

    fuse: accept the -s option to allow automounting
    
    autofs passes the -s option when mounting. All /sbin/mount.<fs> helpers
    accept this, except mount.glusterfs. Because the helper fails when -s is
    passed accessing the mountpoint through autofs gives the following
    error:
    
      $ ls /lan/storage.lan.example.net/repos
      ls: cannot open directory /lan/storage.lan.example.net/repos: Too many levels of symbolic links
    
    BUG: 1340936
    Change-Id: I84755cdac59e630618cb745c0eb3228cc1e93a1a
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14559
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Oleksandr Natalenko <oleksandr@natalenko.name>

commit 3d75e32d6ada03c979077681ff414d948800f07e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 27 15:47:07 2016 +0530

    cluster/afr: Unwind xdata_rsp even in case of failures
    
    DHT expects GF_PREOP_CHECK_FAILED to be present in xdata_rsp in case of mkdir
    failures because of stale layout. But AFR was unwinding null xdata_rsp in case
    of failures. This was leading to mkdir failures just after remove-brick. Unwind
    the xdata_rsp in case of failures to make sure the response from brick reaches
    dht.
    
    BUG: 1340623
    Change-Id: Idd3f7b95730e8ea987b608e892011ff190e181d1
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14553
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit a45bef14b370fe82d4f3af41a35d2802a359c287
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu May 26 08:25:37 2016 +0530

    tests: Add more tests for granular entry self-heal feature
    
    Change-Id: I6f14e413c538e392c8ee5bf4bf9f283e8ac792b7
    BUG: 1332566
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14542
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 4f4a94a35a24d781f3f0e584a8cb59c019e50d6f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue May 24 14:13:29 2016 +0530

    geo-rep: Handle Worker kill gracefully if worker already died
    
    If Agent dies for any reason, monitor tries to kill Worker also. But
    if worker is also died then kill command raises error ESRCH: No such
    process.
    
    [2016-05-23 16:49:33.903965] I [monitor(monitor):326:monitor] Monitor:
        Changelog Agent died, Aborting Worker(/bricks/brick0/master_brick0)
    [2016-05-23 16:49:33.904535] E [syncdutils(monitor):276:log_raise_exception]
        <top>: FAIL:
    Traceback (most recent call last):
      File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 306 in
      twrap
        tf(*aa)
      File "/usr/libexec/glusterfs/python/syncdaemon/monitor.py", line 393, in
      wmon
         slave_host, master)
      File "/usr/libexec/glusterfs/python/syncdaemon/monitor.py", line 327, in
      monitor
         os.kill(cpid, signal.SIGKILL)
         OSError: [Errno 3] No such process
    
    With this patch, monitor will gracefully handle if worker is already died.
    
    Change-Id: I3ae5f816a3a197343b64540cf46f5453167fb660
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1339472
    Reviewed-on: http://review.gluster.org/14512
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 4c798e87859d826bdf048d93a38830a74aa04752
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 20 10:29:05 2016 +0530

    tests/write-behind: move 1279730.t to BAD tests
    
    There is a race condition which is causing the test to fail. For lack
    of bandwidth I am moving this test to BAD, though clearly there is
    some issue with codebase.
    
    BUG: 1337777
    Change-Id: If4f3eff8a5985f37a4dee65d2df29fa7b6bda7ae
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14443
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit bab6bf418bd2be8210135c32f349a5a8d7d7bb91
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 26 18:45:59 2016 +0530

    cluster/afr: Fix warning about unused variable
    
    BUG: 1336612
    Change-Id: Ife1ce4b11776a303df04321b4a8fc5de745389d6
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14545
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 01d0356ca7aef59d0073121d1cc3ccc8de76e30f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri May 27 16:16:37 2016 +0200

    ganesha: fix the shebang for the copy-export script
    
    BUG: 1340488
    Change-Id: I22061a8b8bc0ea43da91e5b2904a27a674a004be
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14548
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 868058b8e0162318801dc3006401ed28449d9268
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 24 11:37:21 2016 -0400

    core: assorted spelling mistakes reported by Debian
    
    See also
    > Change-Id: I567a4be8f0f31f6285550f243fe802895f6bc43b
    
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    BUG: 1336793
    
    Change-Id: Icb9a6ff94d86663a5bca4ba931d810439c02556e
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14526
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c137f6a7389d7f760e4724f3506180f9cfc0da52
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon May 16 14:55:54 2016 +0530

    jbr/locking: Define path for lock/unlock fops in JBR
    
    lock/unlock fops need to be handled differently than
    other 'regular' fops, so as to avoid chances of deadlock
    in blocking calls. This patch addresses the same in the
    following manner, with a caveat.
    
    1. On receiving the fop if the node is a follower, it
       performs the operation (irrespective of it being
       lock/unlock fop), and returns the result.
    
    2. If the node is a leader it follows the following paths
       for lock and unlock fops:
    
       For lock fops :
       -> It performs the fop on itself. If it is a failure, it
          sends -ve ack to the client. If it is successful, it
          dispatches the fop to the followers.
       -> On receiving responses from the followers, it checks
          for quorum (including the leader's outcome). If
          quorum is met, it sends +ve ack to the client.
       -> If quorum is not met, then it *should* issue a rollback
          to the followers, followed by the rollback on the leader.
          It should then send -ve ack to he client.
    
       For unlock fops:
       -> It dispatches the fop on the followers first.
       -> On receiving responses from the followers, it performs
          the fop on itself. On completion, it checks for quorum
          (including the leader's outcome). If quorum is met, it
          sends +ve ack to the client.
       -> If quorum is not met, then it *should* issue a rollback
          on itslef, followed by the rollback on the followers.
          It should then send -ve ack to he client.
    
    Caveat:
       -> jbr-server does not have a rollback framework yet,
          and hence this patch does not perform the rollbacks as
          discussed in the failure scenarios above. The rollback
          framework will be a different dependent patch.
    
    Change-Id: I26961b27cb85f324c1ffeee80e82ec082ffa4465
    BUG: 1333370
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14226
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 04e3a343512d5f71266d334174afe44a6b8bbcfa
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 24 15:25:19 2016 +0530

    cluster/afr: Attempt name-index purge even on full-heal of directory
    
    Change-Id: Ief71cc68a4fbf8113e15b4254ebcabf7e30f74e2
    BUG: 1339181
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14516
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2f29065ae4715c9c4a9d20c4d15311bebd3ddb0e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon May 2 18:45:44 2016 +0530

    afr: Automagic unsplit-brain by [ctime|mtime|size|majority]
    
    Introduce cluster.favorite-child-policy which when enabled with
    [ctime|mtime|size|majority], automatically heals files that are in
    split-brian.
    
    The majority policy will not pick a source if there is no majority.
    The other three policies pick the first brick with a valid reply and
    non-zero ctime/mtime/size as source.
    
    Change-Id: I3c099a0404082213860f74f2c9b4d207cfaedb76
    BUG: 1328224
    Original-author: Richard Wareing <rwareing@fb.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14026
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit f8f16595d8dd8c8a869630bb77b7fd1b42b97e08
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue May 10 12:13:18 2016 +0530

    jbr: Making fop functions more modular to reuse more code
    
    Putting bigger chunks of re-usable code like leader checks
    and init into functions thereby reducing the size of the
    'fop' call.
    
    Introduced 'perform_local_op' in the 'fop' call, where
    regular functions as of now just call dispatch, but fops
    like 'lk' can do their fop specific operations.
    
    Introduced selective_generate to allow certain functions
    for a particular fop to be generated. The rest of the
    functions can be customised and added in jbr.c
    
    Change-Id: I3754ed68983e763329e14a2faef911428e36e4f0
    BUG: 1336328
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14355
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fb57ac1acb228301edb98f2fe7cf93471363eb4a
Author: hari <hgowtham@redhat.com>
Date:   Mon May 23 12:07:21 2016 +0530

    Glusterd: printing the node details on error message of rebalance
    
    Problem: on the rebalance start with one of the glusterd being
    down among the volume, the error message says only about the
    brick path.
    
    Fix: adding the node details
    
    Change-Id: I5827d3a9a15b0461c9ce3a51c0b16246ca58f335
    BUG: 1337899
    Signed-off-by: hari <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/14495
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit edcc6a4ef4f39d5e3073195d45011e3cdfa7c091
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue May 24 19:14:41 2016 +0530

    snapshot/uss: client log is filled with "invalid argument: inode" error
    
    svc_inode_ctx_get is called even if inode is NULL. We should not call
    this function if inode is NULL
    
    Change-Id: I5c3f17633ca88e5b6f40d4acf14a09e14b7ef62b
    BUG: 1339149
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/14525
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit dca1c08c6384e34403d8b5ad6eaf0931529168ac
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue May 24 15:10:33 2016 +0530

    snapshot/uss: log is filled with gfid is NULL error
    
    In snapview-server if the lookup came on missing entry
    then it does not have proper context to see if it is the
    case of "Stale file handle" or ENOENT. We should not log
    this error in GF_LOG_ERROR level, instead this should be
    a debug log.
    
    Change-Id: I8f7cc0e117e9a6dd9482da2e94a56f2ed731a442
    BUG: 1339149
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/14514
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ce466fa6353394a6ac4ca9922237de77686d64d0
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Fri May 20 15:16:17 2016 +0530

    dht: selfheal should wind mkdir call to subvols with ESTALE error
    
    Change-Id: I7140e50263b5f28b900829592c664fa1d79f3f99
    BUG: 1338634
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/14496
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1a489f8f67a98644e6ebea652dcf96dd7425046e
Author: Susant Palai <spalai@redhat.com>
Date:   Mon May 23 12:09:10 2016 +0530

    dht/rebalance: mark hardlink failures as skipped in rebalance
    
    Since rebalance(not remove-brick) process does not migrate hardlinks
    mark them as skipped rather than failed as it creates confusion for
    the users.
    
    Change-Id: I5d469d10146274f00bb91482d0373c5235a9b8b2
    BUG: 1339071
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14493
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit ac2fa110ea489ca3d1b81e3872731fa1621a6e39
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue May 24 17:42:06 2016 +0530

    gfapi/upcall: Use GF_CALLOC while allocating variables
    
    In 'glfs_h_poll_cache_invalidation', use GF_CALLOC to allocate
    'up_inode_arg' to set memory accounting which is used/referred when
    freeing the same variable in case of any erros.
    
    Change-Id: I365e114fa6d7abb292dacb6fc702128d046df8f8
    BUG: 1339214
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/14521
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 02b2750ecc35f88c3262015b401dda962381f9da
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Jan 20 14:30:08 2016 +0530

    cluster/ec: Use correct log levels
    
    Problem :
    Misleading messages are getting logged in mount logs
    and bricks log.
    "Mismatching xdata" and "Heal failed" are getting logged
    
    Solution :
    Reduce the level of logs from INFO, WARNING and NOTICE
    to DEBUG level wherever applicable OR use fop_log_level
    to get proper log level.
    
    Change-Id: Ia824c71e75ab683d3cb8949e1966ea09c9ccce72
    BUG: 1231224
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13266
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit bfd43dc894fcf2cc64ec73e8ea0a779064c47dd4
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon May 23 11:06:38 2016 +0200

    build: include a dummy config.sub and config.guess in releases
    
    There is no hard requirement for a config.guess and config.sub script in
    the release tarball. By passing --build=... and --host=... to
    ./configure, the scripts are not executed.  When doing local builds, the
    ./autogen.sh script (by running automake) will place a config.guess and
    config.sub script in the root of the source tree. Upon creation of the
    release ('make dist') tarball, the scripts are replaced by dummy copies
    from the build-aux/ directory.
    
    The main advantage to not include these scripts in the repository, is
    that there is no need to track upstream updates for them either.
    
    Change-Id: I5e930988a9e849ec5d0c84d2e30e61f2a9685f45
    BUG: 1223937
    Reported-by: Emmanuel Dreyfus <manu@netbsd.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14503
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 4394291064b68f7c1a8634a00b211154087df1bc
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu May 19 12:57:58 2016 -0400

    common-ha: wait for cluster to elect DC before accessing CIB
    
    access attempts, e.g. `pcs property set stonith-enabled=false`
    will fail (or time out) if attempted "too early", i.e. before
    the cluster has elected its DC.
    
    Change-Id: Ifc0aa7ce652c1da339b9eb8fe17e40e8a09b1096
    BUG: 1336945
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14426
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit db817ff68125f89adba76080e8e93d4a4e72d549
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon May 23 15:30:23 2016 -0400

    common-ha: post fail-back, ganesha.nfsds are not put into NFS-GRACE
    
    A little known, rarely used feature of pacemaker called
    "notification" is used to follow the status of the ganesha.nfsds
    in the cluster. This is done with location constraints and other
    Black Magick.
    
    When a nfsd dies, the ganesha-active attribute is cleared, the
    associated floating IP (VIP) fails over to another node, and the
    ganesha_grace notify method is invoked with post-stop on all the
    nodes where the ganesha.nfsd is still running. The notify methods
    send dbus msgs to put their nfsds into NFS-GRACE, and the nfsds
    perform their grace processing, e.g. taking over locks from the
    failed nfsd.
    
    N.B. Fail-back was originally not planned to be a feature for
    glusterfs-3.7, but we sorta got it for free.
    
    For fail-back, the opposite occurs. The ganesha-active attribute
    is recreated, the floating IP fails back, and the notify method is
    invoked with pre-start on all the nodes where the surviving
    ganesha.nfsds continue to run. The notify methods send dbus msgs
    again to put their nsfds into NFS-GRACE again, and the nfsds clean
    up their locks.
    
    Change-Id: I3fc64afa20ae3a928143d69aa533a8df68dd680e
    BUG: 1338967
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14506
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 86a87a2ec0984f450b36ae6414c2d6d66870af73
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed May 18 14:37:46 2016 +0530

    cluster/afr: Check for required number of entrylks
    
    Problem:
    Parallel rmdir operations on the same directory results in ENOTCONN messages
    eventhough there was no network disconnect.
    
    In blocking entry lock during rmdir, AFR takes 2 set of locks on all its
    children-One (parentdir,name of dir to be deleted), the other (full lock
    on the dir being deleted). We proceed to pre-op stage even if only a single
    lock (but not all the needed locks) was obtained, only to fail it with ENOTCONN
    because afr_locked_nodes_get() returns zero nodes  in afr_changelog_pre_op().
    
    Fix:
    After we get replies for all blocking lock requests, if we don't have
    the minimum number of locks to carry out the FOP, unlock and fail the
    FOP. The op_errno will be that of the last failed reply we got, i.e.
    whatever is set in afr_lock_cbk().
    
    Change-Id: Ibef25e65b468ebb5ea6ae1f5121a5f1201072293
    BUG: 1336381
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14358
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit b01fb8d3bb9772d94073aaa52b2d8210ac4fabb8
Author: Kremmyda, Olia (NSN - GR/Athens) <olympia.kremmyda@nokia.com>
Date:   Sun May 22 21:40:19 2016 +0300

    fuse: unref dict even if fuse_first_lookup fails
    
    In fuse_first_lookup function, "dict_unref (dict)" should be included in
    the out label, in case create_frame returns an empty pointer the dict to
    be unreferenced as well.
    
    
    Bug: 1338544
    Change-Id: Ifb8a3378aec6521c1aa848f818968b6bfdb72089
    Signed-off-by: Olia Kremmyda <olympia.kremmyda@nokia.com>
    Reviewed-on: http://review.gluster.org/14464
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6c936a0da3f5f56dd711169f7eb8d335bbb8cdc7
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu May 19 12:53:09 2016 +0200

    nfs: strip trailing / when clients do subdir mounts
    
    Mounting a volume over NFS with a subdir followed by a / does not work:
    
      # mount -t nfs -o vers=3 storage.example.com:/media/installation/ /mnt
      mount.nfs: an incorrect mount option was specified
    
    In the nfs.log:
    
      [client-rpc-fops.c:2930:client3_3_lookup_cbk] 0-media-client-0: remote operation failed. Path: /installation/ (00000000-0000-0000-0000-000000000000) [Invalid argument]
      [client-rpc-fops.c:2930:client3_3_lookup_cbk] 0-media-client-1: remote operation failed. Path: /installation/ (00000000-0000-0000-0000-000000000000) [Invalid argument]
      [mount3.c:1134:mnt3_resolve_subdir_cbk] 0-nfs: path=/installation/ (Invalid argument) [Invalid argument]
    
    It is not possible to resolve paths with a trailing /. Stripping
    trailing /'s from the subdir to mount is sufficient to make it work
    again.
    
    Change-Id: I4075d4cd351438de58e1ff81f0fb65a1ff076da4
    BUG: 1337597
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14421
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 5cf7a32be8d614e8cd89a01ac06e830cbd693929
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu May 19 14:24:08 2016 -0400

    common-ha: log flooded with Could not map name=xxxx to a UUID
    
    When the cluster is configured with long (FQDN) cluster members
    the log is flooded with "Could not map name=$shortname to a UUID"
    notices, and setting/getting the attribute is failing
    
    Change-Id: I954d8cef7115659cc9c8b23dae75a5a247dc5db7
    BUG: 1337650
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14435
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit e221827c18ad4161a8e54ad67c9128ad234b8c03
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed May 18 12:23:59 2016 +0200

    index: improve compiler warning fix
    
    Commit 137bd83029458ecd461718a891c74cd1afd8f6cb introduced some
    typecasting to work around a compiler warning. It is much cleaner to
    add a -1 value in the enumeration and use that in if-statements.
    
    BUG: 1335232
    Change-Id: I830a565b8d96d7b51ff775e94aa23dd567ffe0d9
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14409
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit beebee772505017ed1ef24197880e1ccd0a2536c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri May 20 11:19:27 2016 +0530

    tests: Add afr/tarissue.t to bad tests
    
    Likey a tar binary bug and nothing to do with gluster but adding to bad
    tests for now.
    
    Change-Id: I5cc419f555fef98de555aabb16033f8fe7dc87d0
    BUG: 1337791
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14446
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7a230e269f297af33de41208479b15ac1a997224
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu May 12 15:06:59 2016 +0530

    features/shard: Get hard-link-count in {unlink,rename}_cbk before deleting shards
    
    Change-Id: I0606b74f11f5412c4d9af44a6505635ed9022c15
    BUG: 1335858
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14334
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit d5e67cd2b2d60166f16337e4441fa50a9e488094
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon May 16 10:55:17 2016 +0530

    tier/cli : printing a warning instead of skipping the node
    
    Problem: skipping the status of the nodes down creates confusion
    to the user as one might see the status as completed for all nodes
    and while performing detach commit, the operation will fail as the
    node is down
    
    Fix: Display a warning message
    
    Note: When the last node is down (as per the peer list) then
    warning message can't be displayed as the total number of peers
    participating in the transaction is considered to be the total count.
    
    Change-Id: Ib7afbd1b26df3378e4d537db06f41f5c105ad86e
    BUG: 1324439
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/14347
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 6837b2793bc3d2cc488aa49491f3f5ff09e925b7
Author: M S Vishwanath Bhat <msvbhat@gmail.com>
Date:   Thu May 19 18:53:35 2016 +0530

    distaf: Adding GlusterBaseClass to distaflibs-gluster
    
    GlusterBaseClass is the base class for gluster related test cases.
    This has setup() method which takes care of creating volumes with
    correct volume type after checking global_mode flags etc. So all tests
    are recommended to use this base class.
    
    The teardown() method is to teardown the setup that test has created.
    Each test case should teardown, any setup it does apart from what is done
    in setup().
    
    The cleanup() method is used internally for cleaning up the volumes when
    there is a change of volume type between the tests.
    
    This patch also makes relevant import path changes.
    
    The changes from tc.nodes[] to tc.servers[] in distaf-core broke few
    tests. This patch fixes them.
    
    Change-Id: I1a8ae20ca7cac13b7d25c587f98c23b430054a57
    BUG: 1333738
    Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Reviewed-on: http://review.gluster.org/14239
    Tested-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Apeksha D khakharia <akhakhar@redhat.com>
    Reviewed-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-by: ShwethaHPanduranga

commit deaf8439fc42435988aae6a7b9ab681cc0d36b09
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue May 3 17:02:17 2016 +0530

    core: Honour mandatory lock flags during lock migration
    
    lk_flags from posix_lock_t structure is the primary key used to
    differentiate locks as either advisory and mandatory type. During
    lock migration this field is not read in getactivelk() call path.
    So in order to copy the exact lock state from source to destination
    it is necessary to include lk_flags within lock_migration_info_t
    structure to maintain accurate state. This change also includes
    minor modifications to setactivelk() call to consider lk_flags
    during lock migration.
    
    Change-Id: I20a7b6b6a0f3bdac5734cce8a2cd2349eceff195
    BUG: 1332501
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/14189
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6a51464cf4704e7d7fcbce8919a5ef386a9cfd53
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 19 16:24:09 2016 +0530

    cluster/afr: Do not inode_link in afr
    
    Race is explained at
    https://bugzilla.redhat.com/show_bug.cgi?id=1337405#c0
    
    This patch also handles performing of self-heal with shd-pid.
    Also performs the healing with this->itable's inode rather than
    main itable.
    
    BUG: 1337405
    Change-Id: Id657a6623b71998b027b1dff6af5bbdf8cab09c9
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14422
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 8a71e498fdcedacd1a32e121b3e081c61ee57a2e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 16 15:05:36 2016 +0530

    cluster/afr: Refresh inode for inode-write fops in need
    
    Problem:
    If a named fresh-lookup is done on an loc and the fop fails on one of the
    bricks or not sent on one of the bricks, but by the time response comes to afr,
    if the brick is up, 'can_interpret' will be set to false in afr_lookup_done(),
    this will lead to inode-ctx for that inode to be not set, this can lead to EIO
    in case of a transaction as it depends on 'readable' array to be available by
    that point.
    
    Fix:
    Refresh inode for inode-write fops for the ctx to be set if it is not already
    done at the time of named fresh-lookup or if the file is in split-brain where
    we need to perform one more refresh before failing the fop to check if the file
    is still in split-brain or not.
    
    BUG: 1336612
    Change-Id: I5c50b62c8de06129b8516039f7c252e5008c47a5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14368
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 61c1b2cee973b11897a37d508910012e616033bc
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Apr 29 17:41:18 2016 +0530

    cli/glusterd: add/remove brick fixes for arbiter volumes
    
    1.Provide a command to convert replica 2 volumes to arbiter volumes.
    Existing self-heal logic will automatically heal the file hierarchy into
    the arbiter brick, the progress of which can be monitored using the
    heal info command.
    
    Syntax: gluster volume add-brick <VOLNAME> replica 3 arbiter 1
    <HOST:arbiter-brick-path>
    
    2. Add checks when removing bricks from arbiter volumes:
    - When converting from arbiter to replica 2 volume, allow only arbiter
      brick to be removed.
    - When converting from arbiter to plain distribute volume, allow only if
      arbiter is one of the bricks that is removed.
    
    3. Some clean-up:
    - Use GD_MSG_DICT_GET_SUCCESS instead of GD_MSG_DICT_GET_FAILED to
    log messages that are not failures.
    - Remove unused variable `brick_list`
    - Move 'brickinfo->group' related functions to glusted-utils.
    
    Change-Id: Ic87b8c7e4d7d3ab03f93e7b9f372b314d80947ce
    BUG: 1318289
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14126
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 6f1a71210ee0a0f3741b5ece3b5240c1e4b5fa6d
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon May 16 08:27:41 2016 -0400

    leases: Do not init the threads when lease is disabled
    
    Change-Id: I08c4caf94bf3dfceba6f7d3cc8945c61d9b12dbc
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14360
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8816d97faca31026c01c8c60241ebddcb855880e
Author: Shwetha Panduranga <spandura@redhat.com>
Date:   Thu May 12 19:31:41 2016 +0530

    Adding proper doc_strings to the functions and
    modifying the existing functions in peer_ops
    
    Change-Id: I819293c3191040232b6c9d30877f11b2857f3931
    BUG: 1335494
    Signed-off-by: Shwetha Panduranga <spandura@redhat.com>
    Reviewed-on: http://review.gluster.org/14308
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Tested-by: M S Vishwanath Bhat <vbhat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 5bd9d42c997695d0c673ae50c1dbb9f4ab23695d
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 17 17:27:37 2016 -0400

    common-ha: stonith-enabled option set error in new pacemaker
    
    Setting the option too early results in an error in newer versions
    of pacemaker. Postpone setting the option in order for it to succeed.
    
    N.B. We do not use a fencing agent. Yes, we know this is not supported.
    
    Change-Id: I86953fdd67e6736294dbd2d0795611837188bd9d
    BUG: 1336945
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14404
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 84924ee0ef7cb557c54a9d467364ded86b34f40d
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue May 17 01:22:37 2016 -0400

    leases: Send "this" as cookie to the timer handler
    
    Issue:
    timer-wheel implementation doesn't set the THIS to point
    to the xlator who registered the timer, before calling
    the handler. Hence referencing to THIS is any timer handler
    will point to the global_xlator.
    
    Fix: This is a bug from the timer wheel, but until that gets
    fixed passing "this" as a cookie to the timer handler.
    
    Change-Id: Ife1be56dc100372f9211e8fc7a885ac717cbcf47
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14370
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8facd588f20ef8305b6f6b53da0f6d54d300093b
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Dec 16 05:45:03 2015 -0500

    upcall: pass dict with xattrs on xattr invalidation
    
    In case of xattr invalidation, return a dict containing
    the updated xattrs.
    
    [ndevos: move chunks to change 12995 and only address the xattrs-dict here]
    
    Change-Id: I8733f06a519a9a0f24be1bb4b2c38c9c9dce0ce2
    BUG: 1211863
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/12996
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: soumya k <skoduri@redhat.com>

commit 005d18a623dc49397e2a83a7fb80607ae0a9aed9
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue May 17 05:47:55 2016 -0400

    leases: Fix failure of RD_lease request in certain scenario
    
    Issue:
    When RW_lease exists for a given lease id and another request for
    RD_lease comes in with the same lease id, it gets rejected.
    
    Fix:
    Allow the RD_lease when RW_lease is present iff its from the
    same lease id.
    
    Change-Id: Id8ad542c649497f5e58f2acf5681c640d9202046
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14374
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 0660aa47b5ea782a5f7051544110cf0da73d598d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 17 06:38:57 2016 +0530

    cluster/afr: If possible give errno received from lower xlators
    
    In case of 3 way replication with quorum enabled with sharding,
    if one bricks is brought down and brought back up sometimes
    fops fail with EROFS because the mknod of shard file fails with
    two good nodes with EEXIST. So even when quorum is not met, it
    makes sense to unwind with the errno returned by lower xlators
    as much as possible.
    
    Change-Id: Iabd91cd7c270f5dfe6cbd18c50e59c299a331552
    BUG: 1336612
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14369
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit b923f8c08f9401e8301ac53c79231051c2d0fb00
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu May 5 13:20:10 2016 +0530

    git-branch-diff: wrapper script for git to visualize backports
    
    This script helps in visualizing backported and missed commits between two
    different branches, tags or commit ranges. In the list of missed commits,
    it will help you identify patches which are posted for reviews on gerrit server.
    
    While backporting commit to another branch only subject of the patch may
    remain unchanged, all others such as commit message,  commit Id, change Id,
    bug Id, may be changed. This script works by taking commit subject as the
    key value for comparing two git branches, which can be local or remote.
    
    Help:
    $ ./extras/git-branch-diff.py --help
        usage: git-branch-diff.py [-h] [-s SOURCE] -t TARGET [-a AUTHOR] [-p PATH]
                                  [-o OPTIONS]
    
        git wrapper to diff local or remote branches/tags/commit-ranges
    
        optional arguments:
         -h, --help            show this help message and exit
         -s SOURCE, --source SOURCE
                               source pattern, it could be a branch, tag or a commit
                               range
         -t TARGET, --target TARGET
                               target pattern, it could be a branch, tag or a commit
                               range
         -a AUTHOR, --author AUTHOR
                               default: git config name/email, to provide multiple
                               specify comma separated values
         -p PATH, --path PATH  show source and target diff w.r.t given path, to
                               provide multiple specify space in between them
         -o OPTIONS, --options OPTIONS
                               add other git options such as --after=<>, --before=<>
                               etc. experts use;
    
    Sample usages:
      $ ./extras/git-branch-diff.py -t origin/release-3.8
      $ ./extras/git-branch-diff.py -s local_branch -t origin/release-3.7
      $ ./extras/git-branch-diff.py -s 4517bf8..e66add8 -t origin/release-3.7
      $ ./extras/git-branch-diff.py -s HEAD..c4efd39 -t origin/release-3.7
      $ ./extras/git-branch-diff.py -t v3.7.11 --author="author@redhat.com"
      $ ./extras/git-branch-diff.py -t v3.7.11 --author="authorX, authorY, authorZ"
      $ ./extras/git-branch-diff.py -t origin/release-3.8 --path="xlators/"
      $ ./extras/git-branch-diff.py -t origin/release-3.8 --path="./xlators ./rpc"
      $ ./extras/git-branch-diff.py -t origin/release-3.6 --author="*"
      $ ./extras/git-branch-diff.py -t origin/release-3.6 --author="All"
      $ ./extras/git-branch-diff.py -t origin/release-3.6 --author="Null"
      $ ./extras/git-branch-diff.py -t v3.7.11 --options "--after=2015-03-01 \
                                                          --before=2016-01-30"
    
    Example output:
    $ ./extras/git-branch-diff.py -t origin/release-3.8 --path="./rpc"
    
    ------------------------------------------------------------
    
    [ ✔ ] Successfully Backported changes:
          {from: remotes/origin/master  to: origin/release-3.8}
    
    [84e90b7] server/protocol: option for dynamic authorization of client permissions
    [5bf6522] rpc: By default set allow-insecure, bind-insecure to on
    [3af9b53] glusterd: try to connect on GF_PMAP_PORT_FOREIGN aswell
    [9442e7b] rpc: fix binding brick issue while bind-insecure is enabled
    [7370633] rpc: assign port only if it is unreserved
    [88a386b] rpc: fix gf_process_reserved_ports
    
    ------------------------------------------------------------
    
    [ ✖ ] Missing patches in origin/release-3.8:
    
    All keys already loaded
    [50ca123] rpc: define client port range (under review)
    [89759de] glusterd: add defence mechanism to avoid brick port clashes (under review)
    
    ------------------------------------------------------------
    
    Note: This script may ignore commits which have altered their commit subjects
    while backporting patches. Also this script doesn't have any intelligence to
    detect squashed commits.
    
    Change-Id: Ieb27e548c1945a208e2f5d390c99cac82d18a665
    BUG: 1336642
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14230
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 57185759ccf4c43cf3143d917f782419625c743e
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon May 16 14:38:24 2016 +0530

    extra/devel-vagrant: accept gluster src location from user
    
    Currently gluster source location is hard-coded in vagrantfile.
    
    Made the source location user configurable and also fixed minor issue
    with peer probe with single node.
    
    Change-Id: I7057a97d7372477ddbf01fbc8db949923dfd86e8
    BUG: 1336354
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/14354
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 58615482ed87ff4b8253081c6ea26471fcf09070
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Fri May 13 13:17:16 2016 +0530

    rpc: change client insecure port ceiling from 65535 to 49151
    
    current port allocation to various processes (clumsy):
    
     1023 - 1       -> client ports range if bind secure is turned on
    49151 - 1024    -> fall back to this, if in above case ports exhaust
    65535 - 1024    -> client port range if bind insecure is on
    49152 - 65535   -> brick port range
    
    now, we have segregated port ranges 0 - 65535 to below 3 ranges
    
     1023 - 1       -> client ports range if bind secure is turned on
    49151 - 1024    -> client port range if bind insecure is on
                       (fall back to this, if in above case ports exhaust)
    49152 - 65535   -> brick port range
    
    so now we have a clean segregation of port mapping
    
    Change-Id: Ie3b4e7703e0bbeabbe0adbdd6c60d9ef78ef7c65
    BUG: 1335776
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14326
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6a6b953d4f999b6db11cc6b62880e810aee9a4c7
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Tue May 17 13:23:28 2016 +0530

    dht: rename takes lock on parent directory if destination exists
    
    For directory rename if destination exists the source directory
    is created as a child of the given destination directory. Since
    the new child directory does not exist take lock on parent of the
    child directory.
    
    Change-Id: I24a34605a2cd65984910643ff5462f35e8fc7e71
    BUG: 1336698
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/14371
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 2df72780e473709128a4f5d7f274a9063b288252
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 17 11:06:07 2016 -0400

    scripts: bash-isms in scripts
    
    Change-Id: I05f8718fb73c16dbb37c1f7460bb7b55cc0ffe97
    BUG: 1336853
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14401
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 138935bf8d4b37e094c08eea7a20efc0553e9694
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 17 09:22:43 2016 -0400

    core: assorted typos and spelling mistakes reported by Debian lintian
    
    Also missing bang (!) in #!/bin/bash in shell scripts.
    
    Change-Id: I567a4be8f0f31f6285550f243fe802895f6bc43b
    BUG: 1336793
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14398
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 5a4f4a945661a8bb24735524e152ccd5b1ba571a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed May 11 18:24:40 2016 +0530

    glusterd: copy real_path from older brickinfo during brick import
    
    In glusterd_import_new_brick () new_brickinfo->real_path will not be populated
    for the first time and hence if the underlying file system is bad for the same
    brick, import will fail resulting in inconsistent configuration data.
    
    Fix is to populate real_path from old brickinfo object.
    
    Also there were many cases where we were unnecessarily calling realpath() and
    that may cause in failure. For eg - if a remove brick is executed with a brick
    whoose underlying file system has crashed, remove-brick fails since realpath()
    call fails. We'd need to call realpath() here as the value is of no use.Hence
    passing construct_realpath as _gf_false in glusterd_volume_brickinfo_get_by_brick ()
    is a must in such cases.
    
    Change-Id: I7ec93871dc9e616f5d565ad5e540b2f1cacaf9dc
    BUG: 1335531
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14306
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a84034a5f7f547790c095950cd8a697c8c7b31ca
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Mon May 9 13:03:52 2016 +0530

    distaf: Added library functions for gluster rebalance operations
    
    Change-Id: I8df9199571dbf9e649d93e50f15cfbf3cea7f2bd
    BUG: 1334208
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14255
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: M S Vishwanath Bhat <vbhat@redhat.com>

commit 7d67d7d7a6c86a2f42d619c8d21e5e1f44a19b5c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri May 13 15:18:22 2016 +0530

    Revert "features/shard: Make o-direct writes work with sharding"
    
    This reverts commit c272c71391cea9db817f4e7e38cfc25a7cff8bd5.
    
    This is for two reasons:
    1) It introduces high fop latencies
    2) Even with the patch, there is no true odirect behavior since the
       workaround in the patch doesn't reduce the caching done in kernel's
       page cache as far as writes on anon fds associated with individual
       shards is concerned.
    
    Change-Id: Iaf411198b56237ca0601deaf17f69ef178d7e769
    BUG: 1335818
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14328
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit eb705e090a4748efd18279ad920b2db295f2075a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon May 16 19:53:44 2016 +0200

    core: correct the if-statment in inode_set_need_lookup()
    
    There does not seem to be an ill side-effect from the incorrect
    if-statement. But we should really stick to the same checks we do
    everywhere.
    
    BUG: 1236009
    Change-Id: If2b787287ac0d87712840b15b8c914e3dc5ffcde
    Reported-by: kinsu <vpolakis@gmail.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14363
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a74f8cf4e7edc2ce9f045317a18dacddf25adb8a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri May 13 11:40:57 2016 +0530

    cluster/distribute: heal layout in discover codepath too
    
    BUG: 1334164
    Change-Id: I4259d88f2b6e4f9d4ad689bc4e438f1db9cfd177
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14365
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 06f92634d9ad8aa5c56d786e5248016c283e5c5b
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 11 17:49:10 2016 +0530

    cluster/distribute: use a linked inode in directory heal codepath
    
    This is needed for following reasons:
    * healing is done in lookup and mkdir codepath where inode is not
      linked _yet_ as normally linking is done in interface layers
      (fuse-bridge, gfapi, nfsv3 etc).
    
    * healing consists of non-lookup fops like inodelk, setattr, setxattr
      etc. All non-lookup fops expect a linked inode.
    
    Change-Id: I1bd8157abbae58431b7f6f6fffee0abfe5225342
    BUG: 1334164
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14295
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>

commit 1a3e4159c8ecda51e0f7bb018e017aa0f9d522b8
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri May 13 13:06:21 2016 -0400

    cluster/tier: downgrade max-cycle-time log message to INFO
    
    The "max cycle time" log message was incorrectly logged as
    an error. Downgrade it to INFO.
    
    Change-Id: Ia7d074423019fa79443bc6ea694148b7b8da455d
    BUG: 1335973
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/14336
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 58c577994b2bf67b6f8d9749d9c7d678edfc9ceb
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue May 10 01:50:08 2016 -0400

    leases: Fix the notify being lost
    
    The notify() implemented doesn't really add any value
    and the EXIT_IF_LEASES_OFF in notify() can cause the
    notifications to be lost if leases if off.
    
    Hence remove the notify definition from leases,
    also fix a log level
    
    Change-Id: I8bf30d26f08034a16a450ed811dcf8ac57d70a94
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14275
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5daa68bbdd698bc3532e71593d024d161d796a64
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Sun May 15 10:51:41 2016 -0400

    common-ha: floating IP (VIP) doesn't fail over when ganesha.nfsd dies
    
    restore mistaken removal of 'attrd_updater delete grace-active' to
    trigger fail-over
    
    original was:
       attrd_updater -D -n grace-active
       sleep
       attrd_updater -D -n ganesha-active
    
    mistake was:
       sleep
       attrd_updater -D -n grace-active
    
    Change-Id: Ifb20ebc673b8d262dfb720e7d5c060fbf0d1639b
    BUG: 1336197
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14343
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 85de0c83392d861ba47c97664ff73fd7f8705a3a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri May 13 09:40:38 2016 +0530

    configure: Prevent glupy installation outside $prefix
    
    glupy was installed in the global path outside the prefix path,
    even if --prefix is passed.
    
    ./configure --prefix=/usr/local
    make install
    
    Expected: ${DESTDIR}${prefix}/lib64/python<VERSION>/site-packages/gluster
    Actual: ${DESTDIR}/usr/lib64/python<VERSION>/site-packages/gluster
    
    prefix was not honoured.
    
    With this patch, glupy will be installed inside the prefix path.
    
    BUG: 1335717
    Change-Id: I810dd8d2d6c403540d4b738f5ab54237c7358bf6
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14315
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 3c8c09dd4dd190aefece9fd308fa82907fcb5b7e
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue May 10 21:10:08 2016 +0530

    tier/detach: Clear tier-fix-layout-complete xattr after migration threads join
    
    Previously we had wrongly placed the clearing tier-fix-layout-complete
    xattr before the joining of migration threads. This would lead to
    situations where failure of clearing the xattr would cause the
    premature death of migration threads.
    
    Now we clear the xattr only after the data movement threads join,
    ensuring that all migration is done.
    
    Change-Id: I829b671efa165ae13dbff7b00707434970b37a09
    BUG: 1334839
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/14285
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Joseph Fernandes
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 53d16409f933110da11338ef26d1fa7b2e921cec
Author: Anuradha Talur <atalur@redhat.com>
Date:   Fri May 13 15:34:06 2016 +0530

    cluster/afr : Do post-op in case of symmetric errors
    
    In afr_changelog_post_op_now(), if there was any error,
    meaning op_ret < 0, post-op was not being done even when
    the errors were symmetric and there were no "failed
    subvols".
    
    Fix:
    When the errors are symmetric, perform post-op.
    
    How was the bug found :
    In a 1 X 3 volume with shard and write behind on
    when writes were done into a file with one brick down,
    the trusted.afr.dirty xattr's value for .shard directory
    would keep increasing as post op was not done but pre-op was.
    This incorrectly showed .shard to be in split-brain.
    
    RCA:
    When WB is on, due to multiple writes being sent on
    offset lying in the same shard, chances are that
    same shard file will be created more than once
    with the second one failing with op_ret < 0
    and op_errno = EEXIST.
    
    As op_ret was negative, afr wouldn't do post-op,
    leading to no decrement of trusted.afr.dirty xattr.
    Thus showing .shard directory to be in split-brain.
    
    Change-Id: I711bdeaa1397244e6a7790e96f0c84501798fc59
    BUG: 1335652
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/14310
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 48608e2ca1c6d681c0c60c71ae41b403554bb71d
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue May 10 12:59:56 2016 +0530

    extras: stop all include glusterfs process as well
    
    currently, extras/stop-all-gluster-processes.sh script handles
    brick processes, node services and geo-rep's gsync process.
    
    from now this script also handles mount processes as well,
    as part of this patch I have reorganized this script
    
    Change-Id: Id62d6fda6dd331bde722ce3d99ec3f09fed55cb0
    BUG: 1334620
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14277
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 137bd83029458ecd461718a891c74cd1afd8f6cb
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri May 13 12:41:39 2016 +0530

    index: Fix compiler warning
    
    Problem:
    ----------------------------
    index.c:420:18: warning: comparison of unsigned enum expression < 0 is
    always false [-Wtautological-compare]
            if (type < 0 || type >= XATTROP_TYPE_END)
                ~~~~ ^ ~
    1 warning generated.
    ----------------------------
    Fix:
    Do a type cast before comparing.
    
    Change-Id: I65911a05de5f8b5634f1e8cf359c38dad7d125aa
    BUG: 1335232
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/14318
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 60d235515e582319474ba7231aad490d19240642
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu May 5 14:19:55 2016 +0530

    glusterfsd: explicitly turn on encryption for volfile fetch
    
    Change-Id: I58e1fe7f5edf0abb5732432291ff677e81429b79
    BUG: 1333317
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/14253
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8299ad374b2b93f123b29e0d411930733a372a04
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri May 13 11:59:55 2016 +0530

    ganesha/scripts : Fixing refresh config in ganesha-ha.sh
    
    The change http://review.gluster.org/#/c/14225/ cause a regression
    for refresh config funtion in ganesha-ha.sh due to a invalid usage
    of awk arguement.
    
    Change-Id: Id5adfb12f99b29bdb3531773cd34bd67cfff8768
    BUG: 1333319
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14325
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 84ec13831a4f02cfa8295c9f23b75bf39dc9be30
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri May 13 01:12:10 2016 +0530

    packaging: %postun libs ldconfig: relative path `1' used to build cache
    
    Remove %post{un} {libs|api} -p /sbin/ldconfig optimization and
    move  /sbin/ldconfig on a separate line.
    
    Change-Id: I8a4c3879afcb7cea08d4b303a2524432d2ffec06
    BUG: 1330583
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/14312
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit a9128cda34b1f696b717ba09fa0ac5a929be8969
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Tue Dec 29 19:22:36 2015 +0530

    glusterd/geo-rep: slave volume uuid to identify a geo-rep session
    
    Problem:
    Currently, it is possible to create multiple geo-rep session from
    the Master host to Slave host(s), where Slave host(s) belonging
    to the same volume.
    
    For example:
    Consider Master Host M1 having volume tv1 and Slave volume tv2,
    which spans across two Slave hosts S1 and S2.
    Currently, it is possible to create geo-rep session from
    M1(tv1) to S1(tv2) as well as from M1(tv1) to S2(tv2).
    
    When the Slave Host is alone modified, it is identified as a new geo-rep
    session (as slave host and slave volume together are identifying
    Slave side).
    
    Also, it is possible to create both root and non-root geo-rep session between
    same Master volume and Slave volume. This should also be avoided.
    
    Solution:
    This multiple geo-rep session creation must be avoided and
    in order to avoid, use Slave volume uuid to identify a Slave.
    This way, we can identify whether a session is already created for
    the same Slave volume and avoid creating again (using different host).
    
    When the session creation is forced in the above scenario, rename
    the existing geo-rep session directory with new Slave Host mentioned.
    
    Change-Id: I9239759cbc0d15dad63c48b8cf62950bb687c7c8
    BUG: 1294813
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13111
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Kotresh HR <khiremat@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 12d1c993660d6ae93b0fd08de9a6d7bb7431e7b0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 11 16:39:59 2016 +0530

    mount/fuse: Log gfid and fd ptr as well when writev/readv fail
    
    Change-Id: Iaed3850171155f2452fc29ebecd350c2da0b55cb
    BUG: 1335091
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14291
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 803069efb9f5c5d809237543044577f1a71a10d3
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed May 11 16:53:10 2016 +0530

    packaging: additional dirs and files in /var/lib/glusterd/
    
    Add directories /var/lib/glusterd/hooks and /var/lib/glusterd/hooks/1
    to the list for server package ownership
    
    Correct spelling for
    /var/lib/glusterd/ss_brick and
    /var/lib/glusterd/snaps
    
    Change-Id: I5dffa1db610ccd7e1db4082977dd53afec4aecba
    BUG: 1326410
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/14294
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 7dc5d73410f0e9f846c593887637001ca43bc4a0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 12 13:55:44 2016 +0530

    cluster/afr: Handle non-zero source in heal-info decision
    
    Problem:
    Spurious entries are reported in heal info when the mount is on second/third
    brick of the replica pair because local-child is given preference in selecting
    source. The code is supposed to suggest the file needs heal if the (source < 0)
    (failure code path), but instead it is written as if any non-zero value
    is considered failure.
    
    Fix:
    Treat +ve source as success case
    
    BUG: 1335429
    Change-Id: I1be7f9defef2ae03be7eec8d7d49bf34adeca82c
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14302
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit c769f5dbcad1492854f9fd7f1baae400d6bfeee9
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed May 11 21:41:02 2016 +0530

    locks: Fix a compile warning to use labs instead of abs
    
    This addresses below compile warning generated -
    
    posix.c:2260:32: warning: absolute value function 'abs' given an argument of type 'off_t' (aka 'long') but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
                    flock->l_len = abs (flock->l_len);
                                   ^
    posix.c:2260:32: note: use function 'labs' instead
                    flock->l_len = abs (flock->l_len);
                                   ^~~
                                   labs
    
    Change-Id: Ifd8c5442de4076a2d4425487eb119ce89097779d
    BUG: 1335231
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/14296
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f7d9814dc16d3a0e1468e7946a9e185cc76246df
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon May 2 19:38:55 2016 +0530

    tier: avoid pthread_join if pthread_create fails
    
    this patch rearrange the code, to add some defence functionality for
    pthread_create(), i.e. only on a success on pthread_create() call
    pthread_join().
    
    Change-Id: I0836bc950a210574cfdc755a666c6ac5df6ab430
    BUG: 1332219
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14152
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit b2222c1e13d3bff17fa04b8f9b4870cefd457fe2
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Dec 7 16:24:15 2015 +0000

    upcall: Add support to invalidate xattrs
    
    When SElinux is used, clients should get a notification that the
    extended attributes have been updated. Other components (like md-cache)
    will be able to use this too.
    
    A big part of the implementation comes from Poornima through the first
    version of http://review.gluster.org/12996.
    
    Also moving the flags from upcall-cache-invalidation.h to the main
    libglusterfs upcall-utils.h file, so that other places can easily use
    them in future.
    
    Change-Id: I525345bed8f22d029524ff19ccaf726a2c905454
    BUG: 1211863
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/12995
    Reviewed-by: soumya k <skoduri@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 163568951746f7a7af181bb8c592404581eced78
Author: M S Vishwanath Bhat <msvbhat@gmail.com>
Date:   Wed May 4 17:08:33 2016 +0530

    distaf: Adding README about distaf gluster tests
    
    This README.md contains information about installing
    the required packages before writing distaf tests.
    
    Also illustrates writing the gluster related test cases.
    
    Change-Id: I6dbdf069fa3adb13edd8af14e95f7676e1c93e9d
    BUG: 1331721
    Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Reviewed-on: http://review.gluster.org/14240
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Jonathan Holloway <jholloway@redhat.com>

commit 3286e31509f20fa6e36d5b393a12eaf7ef3a226e
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon May 9 12:50:39 2016 +0200

    socket: Fix incorrect handling of partial reads
    
    The usage of function local variables in the protocol state
    machine caused an incorrect behaviour when a partial read
    from the socket forced the function to return and restart
    later when more data was available. At this point the local
    variables contained incorrect data.
    
    Change-Id: I4db1f4ef5c46a3d2d7f7c5328e906188c3af49e6
    BUG: 1334285
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/14270
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit b2f09e531029f573772a09572cee0f8e1855481b
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon May 9 21:06:07 2016 +0530

    gfapi: clear loc.gfid when retrying after ESTALE
    
    If an ESTALE is returned as result of a revalidate lookup, it means the
    previous gfid and inode are to be discarded and lookup has to be tried
    as a fresh one. A fresh lookup should not have loc.gfid set. We were
    creating a new inode and passing it down but not clearing loc.gfid.
    This patch fixes that.
    
    Change-Id: Ib192ada0528b5fb5e49b4e2555f2bcab62710e2d
    BUG: 1334444
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/14274
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 3887804d5c477de889b9f1c478be3294d9e852fd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon May 9 09:49:01 2016 +0200

    gfapi: fix compile warning on 32-bit systems
    
    While compiling gfapi on a 32-bit system, I got the following warning:
    
        glfs.c:1114:33: warning: format '%ld' expects argument of type 'long int', but argument 10 has type 'int64_t' [-Wformat=]
                                         gf_msg_trace ("glfs", 0,
                                         ^
    
    Change-Id: Ia910cbd2e1682d54c9ccfbf773c87d29facab7b0
    BUG: 1202274
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14279
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit e3fd1c1b7d9357161fd0ffe05e2617db1b9ffcd7
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 3 14:29:45 2016 +0530

    features/worm: When disabled, worm xl must directly pass fops to its child xl
    
    Change-Id: I56ea46c2743636ef7af5c85469cb2e186eadf21f
    BUG: 1332460
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14182
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 176724cdec7061ead0bd7497bb56d0ac09a668a7
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue May 10 13:03:42 2016 +0530

    libglusterfs/gfapi: set appropriate errno for inode_link failures
    
    We do not seem to be setting errno appropriately in case
    of inode_link failures. This errno may be used by any application
    (for eg., nfs-ganesha) to determine the error encountered. This
    patch addresses the same.
    
    Change-Id: I674f747c73369d0597a9c463e6ea4c85b9091355
    BUG: 1334621
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/14278
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f3699f32fd8d468f757697fdacf4949b8d5312d5
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue May 10 02:35:22 2016 -0400

    client: Fix the message ids
    
    The message id of PC_MSG_GFID_NULL was changed as a part of rebase
    of http://review.gluster.org/#/c/11597. Fixing the same
    
    Change-Id: I773e02fb5695b6b55700046f4a4298ec475f8991
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14276
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 0c73e7050c4d30ace0c39cc9b9634e9c1b448cfb
Author: Prashanth Pai <ppai@redhat.com>
Date:   Wed May 4 16:56:50 2016 +0530

    readdir-ahead: Prefetch xattrs needed by md-cache
    
    Problem:
    Negative cache feature implementation in md-cache requires xattrs
    returned by posix to be intercepted for every call that can possibly
    return xattrs. This includes readdirp(). This is crucial to treat
    missing keys in cache as a case of negative entry (returns ENODATA)
    
    md-cache puts names of xattrs that it wants to cache in xdata and
    passes it down to posix which returns the specified xattrs in the
    callback. This is done in lookup() and readdirp(). Hence, a xattr
    that is cached can be invalidated during readdirp_cbk too.
    
    This is based on the assumption that readdirp() will always return
    all xattrs that md-cache is interested in. However, this is not the
    case when readdirp() call is served from readdir-ahead's cache.
    readdir-ahead xlator will pre-fetch dentries during opendir_cbk
    and readdirp. These internal readdirp() calls made by readdir-ahead
    xlator does not set xdata in it's requests. Hence, no xattrs are
    fetched and stored in it's internal cache.
    
    This causes metadata loss in gluster-swift. md-cache returns ENODATA
    during getxattr() call even though the xattr for that object exists on
    the brick. On receiving ENODATA, gluster-swift will create new metadata
    and do setxattr(). This results in loss of information stored in
    existing xattr.
    
    Fix:
    During opendir, md-cache will communicate to readdir-ahead asking it
    to store the names of xattrs it's interested in so that readdir-ahead
    can fetch those in all subsequent internal readdirp() calls issued by
    it. This stored names of xattrs is invalidated/updated on the next
    real readdirp() call issued by application. This readdirp() call will
    have xdata set correctly by md-cache xlator.
    
    BUG: 1333023
    Change-Id: I32d46f93a99d4ec34c741f3c52b0646d141614f9
    Reviewed-on: http://review.gluster.org/14214
    Tested-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit dc3b3af58281bbf63a2001e0a9a34b20cd251586
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon May 9 11:56:37 2016 +0200

    packaging: resource-agents sub-package needs arch-less requires
    
    The glusterfs-resource-agents package is marked as 'noarch'. It should
    therefor not have a dependency on a specific architecture (is done with
    the _isa macro).
    
    BUG: 1334269
    Change-Id: I3d24c0e4e60e368b22eef97bf3aabe6b020a23a9
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14269
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 731d15a018f3c2451f72c84f4e07aa23c8abc8d2
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Fri May 6 12:07:41 2016 -0400

    packaging: additional dirs and files in /var/lib/glusterd/
    
    Directory /var/lib/glusterd/glusterfind/.keys doesn't need
    to be created, it just needs to be listed in the list of files.
    
    Also, S57glusterfind-delete-post.py under the hooks directory
    is actually a symlink to libexec/glusterfs/glusterfind/...
    so don't list %attr(...) for the symlink
    
    Change-Id: Ia4571a7b5d0cc79c70cc120f7770bf2e6453bc84
    BUG: 1326410
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14243
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f0ade919006b2581ae192f997a8ae5bacc2892af
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu Apr 28 11:48:23 2016 +0530

    heal/xml : xml implementation of heal info and splitbrain info
    
    Current output:
    heal didn't have xml output.
    
    expected output with patch:
    gluster v heal v1 info --xml
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <healInfo>
        <bricks>
          <brick hostUuid="3677edbb-0a6a-415e-b0ee-b846ff93259c">
            <name>10.70.42.183:/home/bricks/b1</name>
            <status>Connected</status>
            <numberOfEntries>0</numberOfEntries>
          </brick>
          <brick hostUuid="3677edbb-0a6a-415e-b0ee-b846ff93259c">
            <name>10.70.42.183:/home/bricks/b2</name>
            <status>Connected</status>
            <numberOfEntries>0</numberOfEntries>
          </brick>
        </bricks>
      </healInfo>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
    </cliOutput>
    
    gluster v heal v1 info split-brain --xml
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <healInfo>
        <bricks>
          <brick hostUuid="3677edbb-0a6a-415e-b0ee-b846ff93259c">
            <name>10.70.42.183:/home/bricks/b1</name>
            <status>Connected</status>
            <numberOfEntries>0</numberOfEntries>
          </brick>
          <brick hostUuid="3677edbb-0a6a-415e-b0ee-b846ff93259c">
            <name>10.70.42.183:/home/bricks/b2</name>
            <status>Connected</status>
            <numberOfEntries>0</numberOfEntries>
          </brick>
        </bricks>
      </healInfo>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
    </cliOutput>
    
    Change-Id: I20ad5eb7950d4721364ab46089e3af515162db82
    BUG: 1331287
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/14100
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit abd27041ebcb3c6ee897ad253fc248e3bb1823e6
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon May 2 16:20:30 2016 +0530

    tier/detach : During detach check if background fixlayout is done
    
    During detach check if background fixlayout is done, if not done ignore
    the case and continue detach.
    
    Change-Id: I5d5cfc0e73d0eb217fdeab54c432dc4af8bc598d
    BUG: 1332136
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/14147
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 4b2b9a971e09b0c17018f4a5dd24fa7d64e94bf5
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Apr 29 12:24:24 2016 -0400

    gfapi: Fix a deadlock caused by graph switch while aio in progress
    
    RCA:
    Currently async nature is achieved by submitting a syncop operation to
    synctask threads. Consider a scenario where the graph switch is triggered,
    the next write fop checks for the next available graph and sets
    fs->migration_in_progess and triggers the migration of fds and other
    things, which can cause some syncop_lookup operation. While this fop (on
    synctask thread) is waiting for syncop_lookup to return, lets say there
    are another 17 write async calls submitted, all these writes are blocked
    waiting for fs->migration_in_progress to be unset, hence all the 16
    synctask threads are blocked waiting for fs->migration_in_progress to be
    unset. Now the syncop_lookup returns, but there are no synctask threads to
    process the lookup_cbk. If this syncop_lookup doesn't return,
    then fs->migration_in_progress can not be unset by the first fop.
    Thus causing a deadlock.
    
    To fix this deadlock, changing all the async APIs to use STACK_WIND,
    instead of syntask to achieve async nature. glfs_preadv_async is already
    implemented using STACK_WIND, now changing all the other async APIs
    also to do the same.
    
    This patch as such will not reduce the performance of async IO, the only
    thing that can affect is that, in case of write, the buf passed by
    application is copied onto iobuf in the same thread wheras before it
    was being copied in synctask thread.
    
    Since, the syncop + graph switch logic (lock across fops) is not a good
    candidate for synctask, changing the async APIs to use STACK_WIND
    
    Change-Id: Idf665cae0a8e27697fbfc5ec8d93a6d6bae3a4f1
    BUG: 1332156
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/14148
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit db610ee85447de413e56b7cee26175fcb6dbb04a
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon Aug 17 11:16:27 2015 +0530

    remove unused variables
    
    Cleaning dead initializations.
    
    Change-Id: I53ae506593cd10441d61df3b2c9249544a7871f7
    BUG: 1254067
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11932
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit ef0db52bc55a51fe5e3856235aed0230b6a188fe
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 3 14:43:20 2016 +0530

    dht:remember locked subvol and send unlock to the same
    
    During locking we send lock request to cached subvol,
    and normally we unlock to the cached subvol
    But with parallel fresh lookup on a directory, there
    is a race window where the cached subvol can change
    and the unlock can go into a different subvol from
    which we took lock.
    
    This will result in a stale lock held on one of the
    subvol.
    
    So we will store the details of subvol which we took the lock
    and will unlock from the same subvol
    
    Change-Id: I47df99491671b10624eb37d1d17e40bacf0b15eb
    BUG: 1311002
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13492
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 9de751eddb89eec3715c1a5dbb36b8b655d3f3a8
Author: M S Vishwanath Bhat <msvbhat@gmail.com>
Date:   Fri Apr 29 20:38:23 2016 +0530

    Adding io_libs to the distaflibs namespace packages
    
    Following the gluster_libs, which was added to distaflibs
    namespace package, this patch also adds io_libs to the same
    namespace package.
    
    Change-Id: Ife62f2dd0c966579546426a9dbc1a71d8c154292
    BUG: 1331423
    Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Reviewed-on: http://review.gluster.org/14119
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jonathan Holloway <jholloway@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit f71e2fa49af185779b9f43e146effd122d4e9da0
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Apr 18 21:34:32 2016 +0530

    glusterd-ganesha : copy ganesha export configuration files during reboot
    
    glusterd creates export conf file for ganesha using hook script during
    volume start and ganesha_manage_export() for volume set command. But this
    routine is not added in glusterd restart scenario.
    Consider the following case, in a three node cluster a volume got exported
    via ganesha while one of the node is offline(glusterd is not running).
    When the node comes back online, that volume is not exported on that node
    due to the above mentioned issue.
    Also I have removed unused variables from glusterd_handle_ganesha_op()
    For this patch to work pcs cluster should running on that be node.
    
    Change-Id: I5b2312c2f3cef962b1f795b9f16c8f0a27f08ee5
    BUG: 1330097
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14063
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit e66add8a304ca610b74ecbbe48cec72dba582340
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 4 19:05:28 2016 +0530

    cluster/afr: Do heals with shd pid
    
    Multi-threaded healing doesn't create synctask with shd pid, this
    leads to healing problems when quota exceeds.
    
    BUG: 1332994
    Change-Id: I80f57c1923756f3298730b8820498127024e1209
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14211
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 74837896c38bafdd862f164d147b75fcbb619e8f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 5 07:59:03 2016 +0530

    protocol/client: Filter o-direct in readv/writev
    
    Change-Id: I519c666b3a7c0db46d47e08a6a7e2dbecc05edf2
    BUG: 1322214
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14215
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 5440bad91026f27399df51856176aef85c1fcf4d
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu May 5 14:52:32 2016 +0530

    NFS-Ganesha : Parse the Export_Id correctly for unexporting volume
    
    Currently export id parsed using "cut -d ' ' -f8" which might endup
    in giving wrong value. In case of multiple space chracter, output
    may differ. In this all those instance will replaced by awk call
    
    Change-Id: I60dea8ce116900da3c1fc9badf898e51183a2ca1
    BUG: 1333319
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/14225
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 3f07e9324d8fa62a6231f387270d8e7559ac71e0
Author: hari <hgowtham@redhat.com>
Date:   Thu Apr 28 19:36:25 2016 +0530

    Tier/glusterd: Resetting the tier status value to not started
    
    Problem: during a volume restart or tier start force, the
    value of tier status is set as started irrespective of the result.
    
    Fix: The appropriate value of status is set during the restart of
    rebalance function.
    
    Change-Id: I6164f0add48542a57dee059e80fa0f9bb036dbef
    BUG: 1315666
    Signed-off-by: hari <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/14106
    Tested-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 0f73da2362d0b045f1c610974b1567d262a12df0
Author: Arthy Loganathan <aloganat@redhat.com>
Date:   Fri Apr 29 17:24:24 2016 +0530

    distaflibs:Added snapshot library functions in distaf
    
    Change-Id: I29407b05b8b76c1d5883172a66b15cf0038cb67e
    BUG: 1332822
    Signed-off-by: Arthy Loganathan <aloganat@redhat.com>
    Reviewed-on: http://review.gluster.org/14115
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: M S Vishwanath Bhat <vbhat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 09966fff2588e41410eabe75003346edd20404ab
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 4 20:16:36 2016 +0530

    cluster/dht: Perform NULL check on xdata before dict_get()
    
    .. to prevent unnecessary logs from gf_msg_callingfn()
    
    Change-Id: I367628fee2f6783ba9ed6f918deabd034df820c9
    BUG: 1333043
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14212
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2326f8c2a775f6536d95e2e4676866f1b5dfc368
Author: Anuradha Talur <atalur@redhat.com>
Date:   Wed May 4 11:55:43 2016 +0530

    heal: Fix incorrect heal info output
    
    Problem:
    In heterogenous clusters, heal info gives incorrect
    outout as "Failed to process entries completely.
    Number of entries so far: 0".
    
    This happens when the getxattr on virtual xattr
    for <brickpath>/.glusterfs/indices/dirty fails
    on older bricks as they do not recognize the xattr.
    
    Fix:
    Ignore that error so that heal info doesn't
    incorrectly report failure.
    
    Change-Id: I0d3541ed0594d67c3c3b8568a89a975a100bf6dd
    BUG: 1332798
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/14199
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 4c4624c9bad2edf27128cb122c64f15d7d63bbc8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Mar 19 11:40:26 2016 +0530

    cluster/afr: Don't let NFS cache stat after writes
    
    Problem:
    Afr does post-ops after write but the stat buffer it unwinds is at the
    time of write, so if nfs client caches this, it will see different
    ctime when it does stat on it after post-op is done. From NFS client's
    perspective it thinks the file is changed. Tar which depends on this
    to be correct keeps giving 'file changed as we read it' warning.
    If Afr instead has to choose to unwind after post-op, eager-lock,
    delayed-post-op will have to be disabled which will lead to bad
    performance for all write usecases.
    
    Fix:
    Don't let client cache stat after write.
    
    Change-Id: Ic6062acc6e5cdd97a9c83c56bd529ec83cee8a23
    BUG: 1302948
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13785
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit e3b2ed938a5dc8a72d1fe3d7ced341646d241ca4
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Feb 12 17:17:30 2016 +0530

    performance/write-behind: guaranteed retry after a short write
    
    * Don't mark the request with a fake EIO after a short write.
    * retry the remaining buffer at least once before unwinding reply to
      application. This way we capture correct error from backend (ENOSPC,
      EDQUOT etc).
    
    Thanks to "Vijaikumar Mallikarjuna"<vmallika@redhat.com> for the test
    script.
    
    Change-Id: I73a18b39b661a7424db1a7855a980469a51da8f9
    BUG: 1292020
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/13438
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 7d431c14bc458e9451e9c737f5879968a7b6a0b9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 4 10:19:23 2016 +0530

    libglusterfs: Fix security prefix comparison
    
    BUG: 1331860
    Change-Id: If35012ee35104848d7d3b21900c7f533d0253cde
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14194
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c3c999776e6607b2e2361aeecc0fd4661d155536
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue May 3 09:29:46 2016 -0400

    protocol/client: fix coding style violations
    
    Commit 45fa52d7 added some massive violations of our 80-column rule.
    This commit fixes them.
    
    Change-Id: I7bb588b99dbbff4f0b9874ef10f200f73ac1b627
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/14192
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>

commit b4dc1a55486e6a7e4ec72ea494709c1e7da25f50
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed May 4 11:21:31 2016 +0530

    tests: assign bug id for br-state-check known issue
    
    Change-Id: I13a1477830a023f40cb62097f04c22cd2d910021
    BUG: 1332473
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/14198
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 622f60c01c586a510a06b10a87dbc612206a5305
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue May 3 15:08:30 2016 +0530

    quota/tests : remove inode-quota-enforcing.t from bad tests
    
    Change-Id: I4aef04cdbef7ecdabfe1dd64784cecf0624e6d8c
    BUG: 1332021
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/14184
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit a1a1ff66eecba2edc523b41652172088b8e08dc9
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue May 3 15:12:08 2016 +0530

    quota/tests : remove quota-ancestry-building.t from bad tests
    
    Change-Id: Iaee0934d8be4e133b43bd390ed029f11cce1a24b
    BUG: 1332020
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/14185
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 89759de7e47d99eb1fca2763931b4f33ac765173
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Apr 27 19:12:19 2016 +0530

    glusterd: add defence mechanism to avoid brick port clashes
    
    Intro:
    Currently glusterd maintain the portmap registry which contains ports that
    are free to use between 49152 - 65535, this registry is initialized
    once, and updated accordingly as an then when glusterd sees they are been
    used.
    
    Glusterd first checks for a port within the portmap registry and gets a FREE
    port marked in it, then checks if that port is currently free using a connect()
    function then passes it to brick process which have to bind on it.
    
    Problem:
    We see that there is a time gap between glusterd checking the port with
    connect() and brick process actually binding on it. In this time gap it could
    be so possible that any process would have occupied this port because of which
    brick will fail to bind and exit.
    
    Case 1:
    To avoid the gluster client process occupying the port supplied by glusterd :
    
    we have separated the client port map range with brick port map range more @
    http://review.gluster.org/#/c/13998/
    
    Case 2: (Handled by this patch)
    To avoid the other foreign process occupying the port supplied by glusterd :
    
    To handle above situation this patch implements a mechanism to return EADDRINUSE
    error code to glusterd, upon which a new port is allocated and try to restart
    the brick process with the newly allocated port.
    
    Note: Incase of glusterd restarts i.e. runner_run_nowait() there is no way to
    handle Case 2, becuase runner_run_nowait() will not wait to get the return/exit
    code of the executed command (brick process). Hence as of now in such case,
    we cannot know with what error the brick has failed to connect.
    
    This patch also fix the runner_end() to perform some cleanup w.r.t
    return values.
    
    Change-Id: Iec52e7f5d87ce938d173f8ef16aa77fd573f2c5e
    BUG: 1322805
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14043
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5ba82c0b9fa043aa4397d6744b079388ea360cc0
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 3 15:30:44 2016 +0530

    tests: Move tests/bitrot/br-state-check.t to bad test
    
    Change-Id: I9a1578ef4aeb8ce559b3af5092544b3023b14f87
    BUG: 1332473
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14186
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 717e66a799b70c9b61ad56ab9d27915e265f9d3d
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue May 3 12:50:51 2016 +0530

    mgmt/glusterd: Fix op-version for mandatory-locking volume set option
    
    The following volume set option will be available with 3.8 release.
    
    locks.mandatory-locking
    
    This one-line change is to fix the wrongly set op-version for the
    above mentioned volume set option.
    
    Change-Id: Icc7d213f917f5f69e2ec84c685b1138ce2f86a90
    BUG: 1332413
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/14180
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 29254449b19697b93ebf376541ea5062b4a99fcb
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 3 14:47:19 2016 +0530

    glusterd/bitrot: Fix bitrot xlator_type
    
    Fix "voltype" value for bitrot in 'glusterd_volopt_map'.
    Routines such as 'gd_is_boolean_option' will use
    the value of "voltype" to load the shared
    library and figure out data type of specific options.
    If the value of "voltype" does not match with
    the actual shared library name, it will break such
    routines.
    
    Change-Id: I36af4bb3e7043cc87dd19aea1985f3167ff82c18
    BUG: 1332465
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14183
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 50ca12326bde53895b7227b12ef4d74a69e2a0f9
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu Apr 14 19:02:19 2016 +0530

    rpc: define client port range
    
    Problem:
    when bind-insecure is 'off', all the clients bind to secure ports,
    if incase all the secure ports exhaust the client will no more bind
    to secure ports and tries gets a random port which is obviously insecure.
    
    we have seen the client obtaining a port number in the range 49152-65535
    which are actually reserved as part of glusterd's pmap_registry for bricks,
    hence this will lead to port clashes between client and brick processes.
    
    Solution:
    If we can define different port ranges for clients incase where secure ports
    exhaust, we can avoid the maximum port clashes with in gluster processes.
    
    Still we are prone to have clashes with other non-gluster processes, but
    the chances being very low in the rhgs Env, but that's a different story
    on its own, which will be handled in upcoming patches.
    
    Change-Id: Ib5ce05991aa1290ccb17f6f04ffd65caf411feaf
    BUG: 1322805
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13998
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 614a048c59d9b22e090acc0f1bdcb8c1be67f97a
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Thu Nov 5 15:09:31 2015 +0530

    glusterd: remove-brick commit should not succeed when migration failed
    
    While remove a brick if the data migration was not successful,
    remove-brick commit should not succeed as this can lead to
    data loss.
    
    Change-Id: I1eac0ef775cc6910ece0e46ebb04051444d54393
    BUG: 1278325
    Signed-off-by: Sakshi Bansal <sabansal@localhost.localdomain>
    Reviewed-on: http://review.gluster.org/12513
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>

commit 7f92a3de16f9ac34a9c215a7bc067dc6d084af14
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon May 2 18:09:12 2016 +0530

    protocol/server: address double free's
    
    Change-Id: Ic8a8fe85cf91c5c7aa93dce872cedbc67464e4ea
    BUG: 1227667
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14150
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit fb77938fc7810dc5ac16b0de9694157cde93635e
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Sat Apr 30 22:01:47 2016 +0530

    gfapi/upcall: Ignore handle create failures
    
    In "glfs_h_poll_cache_invalidation", we need to send upcall only if there
    is a corresponding inode entry in the gfapi inode table for that handle.
    
    That's because the application will have reference to the inode as long as
    it operates on any handle. That means the only case in which we cannot find
    inode is when the application has closed the handle (either as part of unlink
    or for any other purpose). But since it will have no more references and will
    not be interested in any upcall event for that handle, we can safely ignore such
    cases.
    
    Note: This will affect only that particular applicaiton process/local libgfapi
    client.
    
    Change-Id: I9499cd9c284350d4a271e58f2a0966db65a7a61c
    BUG: 1331969
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/14132
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 19264ccb20070798121d2ebfb3a0d2b1fb7a03bb
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon May 2 15:33:13 2016 +0530

    features/bitrot: Fix Compilation Warning!!!
    
    Earlier the lock  was using glusterfs macros
    LOCK/UNLOCK/LOCK_INIT/LOCK_DESTROY. The patch
    http://review.gluster.org/#/c/14140/ used 'pthread_cleanup_push'
    interface for the same lock which was giving "initialization
    discards qualifiers from pointer target type". It's strange that
    the build succeeded in master branch with no warnings but fails for
    the backport http://review.gluster.org/#/c/14140/ in 3.7 branch
    treating this warning as error.
    
    Change-Id: I75c8a65a2bfb1147fe9a84cfd8f09a97c089ae70
    BUG: 1332134
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14146
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 209985e861f4d8a22bfdb457c0e8d7045ab44553
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Apr 28 08:42:40 2016 +0200

    cluster/ec: Fix issues with eager locking
    
    Due to a race in timer cancellation, in some cases it was possible
    to unlock the lock while another concurrent fop that needed it
    continues execution as if it were not released.
    
    This patch also fixes an issue that caused a lock to not be released
    if an error was found while preparing ec_update_size_version().
    
    Change-Id: I1344a3f5ecfc333f05a09e62653838264c9c26b1
    BUG: 1331254
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/14112
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Chen Chen <chenchen@smartquerier.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 77def44d497d090ef3f393b6d9403c1a29dcf993
Author: Prashanth Pai <ppai@redhat.com>
Date:   Wed Apr 27 13:37:07 2016 +0530

    posix: Set correct d_type for readdirp() calls
    
    dirent.d_type can contain the type of the directory entry. The 'd_type'
    struct member in dirent is present in Linux and many BSD flavours.
    However, filling d_type with correct value requires support from the
    underlying filesystem. If not, d_type is set to DT_UNKNOWN. XFS added
    support for d_type as part of their newer version 5 on-disk format.
    However, this requires Linux >= 3.15, xfsprogs >= 3.2.0 and the bricks
    to be formatted using the new format.
    
    This patch enables posix xlator to set d_type to the right value even
    when the underlying filesystem does not support it. d_type can be set
    using information previously fetched by stat() on the dir entry.
    This will aid FUSE applications to leverage d_type to avoid the expense
    of calling lstat() if further actions depend on the type of the file.
    
    Refer `man 3 readdir` and `man 2 getdents`
    
    BUG: 1175711
    Change-Id: Ic5a262fe4c64122726b4fae2d1bea375c559ca04
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/14095
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 70a889489d79c41edfed52fdbdfa6869869906aa
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 1 22:49:57 2016 +0200

    disperse: mark bug-1236065.t as bad_test
    
    tests/bugs/disperse/bug-1236065.t failed several times on different
    Jenkins slaves:
    
    * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20316/console
    * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20320/console
    * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20321/console
    
    BUG: 1332054
    Change-Id: Ie1934f09f843c2089c187e9295288c16c01913d2
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14138
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 4517bf8dd6de310950cc5a612955aa3a2fddb57e
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Feb 4 10:34:33 2015 +0530

    features/locks: Implement mandatory locks
    
    Initial change to fix/enable the mandatory locking support in GlusterFS
    as per the following design:
    
    https://review.gluster.org/#/c/12014/
    
    Accordingly 'locks.mandatory-locking' option is available as part of this
    change which will accept one among the following values:
    
    * off
    * file
    * forced
    * optimal
    
    See design doc for more details
    
    Change-Id: I14c489b3f8af5ebcbfa155a03f0c175e9558ac46
    BUG: 762184
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/9768
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 78c1c6002f0b11afa997a14f8378c04f257ea1c5
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Apr 25 16:02:10 2016 +0530

    cluster/dht: Handle rmdir failure correctly
    
    DHT did not handle rmdir failures on non-hashed subvols
    correctly in a 2x2 dist-rep volume, causing the
    directory do be deleted from the hashed subvol.
    Also fixed an issue where the dht_selfheal_restore
    errcodes were overwriting the rmdir error codes.
    
    Change-Id: If2c6f8dc8ee72e3e6a7e04a04c2108243faca468
    BUG: 1330032
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/14060
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 232b10d68f47eee4c58f0d44891e52026b98d288
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Apr 20 17:53:50 2016 +0530

    cli/bitrot: Unmask scrub statistics
    
    Revert the commit 2a37dbd845348a774f45c4d77cffebc32c749251
    The scrub statistics were masked because of inaccurate
    stats. Now with http://review.gluster.org/#/c/14044/
    it's fixed, hence unmasking it.
    
    Change-Id: Iffff5f48eb8121b617af82ecfb70bec5b2772c23
    BUG: 1329211
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14121
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit db468e4361315a91aaeeaa14ff7e6b448e2c8599
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 29 17:45:31 2016 +0530

    features/bitrot: Introduce scrubber monitor thread
    
    The patch does following changes.
    
     1. Introduce scrubber monitor thread.
     2. Move scrub status related APIs to separate file
        and make part of libbitrot library.
    
    Problem:
         Earlier, each child of the scrubber was maintaining
    the state machine and hence there was no way to track
    the start and end time of scrubbing as each brick has
    it's own start and end time. Also each brick was maintaining
    it's own timer wheel instance. It was also not possible
    to get scrubbed files count per session as we could not
    get last child which finishes scrubbing to reset it to
    zero.
    
    Solution:
        Introduce scrubber monitor thread. It does following.
    
     1. Maintains the scrubber state machine. Earlier each
        child had it's own state machine. Now, only monitor
        maintains on behalf of all it's children.
     2. Maintains the timer wheel instance. Earlier each
        child had it's own timer wheel instance. Now, only
        monitor maintains on behalf of all it's children.
    
    As a result, we can track the scrub statistics easily
    and correctly.
    
    Change-Id: Ic6e34ffa57984bd7a5ee81f4e263342bc1d9b302
    BUG: 1329211
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14044
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 3c01660f63a32e53395e9af13f33ee5439932cdf
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Apr 20 23:49:39 2016 +0530

    glusterd/bitrot: Fix bit-rot scrub status
    
    Few of the dictionary values were not allocated and
    set. This patch allocates them and set.
    
    Change-Id: Ic61c1209b238e45219793fd8bec92235adfbd013
    BUG: 1329211
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/14120
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 60e340481ad5496e920722e8267572fa26cf2822
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon May 2 00:36:30 2016 +0530

    protocol/server: Implementation of compound fop
    
    Change-Id: I981258afa527337dd2ad33eecba7fc8084238e6d
    BUG: 1303829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/14137
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit a15195794c336ed0e272076a128c56b171cae12f
Author: karthik-us <ksubrahm@redhat.com>
Date:   Thu Feb 11 16:31:18 2016 +0530

    WORM/Retention Translator: Implementation of file level WORM
    
    To activate the file level worm feature, the features.read-only and
    features.worm options should be switched "off" on the volume and
    the features.worm-file-level should be switched "on". Both read-only
    and worm or worm-file-level cannot be switched "on" together. The
    files which are created when the worm-file-level option is set on the
    volume will have their own retention profile.
    
    If both worm and worm-file-level are "on" at that time the worm
    which is the volume level worm will have priority over file level
    worm. If worm-file level is switched "off" after some time and the
    read-only option is switched "on" then read-only will have priority.
    
    The current implementation allows the users to manually transmit
    a file to a WORM-Retained state by removing all the write bits of
    the file using the chmod command. The file will have a retention
    profile which contains the state of the file, mode of retention,
    and the default retention time.
    
    The file will be made WORM-Retained for a default of 120 seconds
    during which it will be immutable and undeletable and it sets the
    atime of the file to the time till which it is retained.
    After that period if any fop request comes for that file, will
    make the transition from WORM-Retained state to WORM state, where
    the file will be immutable but deletable and, it will reset
    the atime to the actual atime of the file. If a WORM file needs
    to be made undeletable again, it can be done by using the chmod
    command with all the write bits removed.
    
    There are two modes of retention:
    1. Relax: where the retention time of a WORM-Retained file can be
       increased or decreased.
    2. Enterprise: where the retention time of a WORM-Retained file
       can be increased but not be decreased.
    Whenever a utime change(touch -a, -t, ...)request comes for a
    file it checks the mode of retention before setting the utimes.
    This is done only if the file is WORM-Retained but for a WORM file
    it will change the utimes.
    
    Lazy auto commit:
    Whenever a file gets created it will store the creation time of the
    file or if a file already exists then any of the next unlink, link,
    truncate or rename fops will set the current time as the start time
    in an xattr. The next rename/unlink/truncate/link call will check for the
    auto commit period and if is is expired, then it will automatically do
    the state transition. If it is a normal file then it gets converted
    to WORM-Retained state. If it is a WORM-Retained file and its retention
    period is expired, then it gets converted to WORM state.
    
    Added the volume set options for the WORM translator. It allows the users
    to change the default values of auto-commit-period, default-retention-period,
    retention-mode. To make use of the file-level WORM first we have to set the
    'worm-file' option to 'on'. The files which are created when the worm-file
    option is set on the volume will get WORM-Retained. Other files will work
    as usual and will not be WORMed. The auto-commit-period, retention-mode,
    and the default-retention-period values for the file will be set to the values
    which are set on the volume when the file is created.
    
    Added the tests to check the basic functionalities of the WORM/Retention feature.
    
    Change-Id: I77bd9777f9395a944d76b5cc35a5b48a3c14d148
    BUG: 1326308
    Signed-off-by: karthik-us <ksubrahm@redhat.com>
    Reviewed-on: http://review.gluster.org/13429
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit c804ac76c404acb7277cfb9c0a7159bc33d92ff5
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Apr 25 15:22:23 2016 +0530

    dht/rebalance: add lock migration fop to dht_migrate_file
    
    Change-Id: Id0e7400c8ae950c90d42a3ddf8b558a14959a1f8
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14074
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 88088b8f15fc5feb153511b71558447c09ff68d9
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Apr 19 01:09:10 2016 +0530

    cluster/dht: handle EREMOTE in dht lk/flush
    
    With lock-migration, we need to send requests to destination
    brick post migration. Once, the source brick marks the lock
    structure to be already migrated, the requests will be redirected
    to destination brick by dht_lk2/flush2.
    
    Change-Id: I50b14011c5ab68c34826fb7ba7f8c8d42a68ad97
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/13493
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 3ff1861546e619bb3c9dc155c55df5d6ee1a479e
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Apr 18 17:42:06 2016 +0530

    glusterd: volume set changes for lock migration
    
    Change-Id: I48c6f9cdda47503615ba65882acd5eedf0a70c89
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14024
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 2f4733657b0a8439620b045fcb597838a818487a
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 17 10:23:20 2016 +0530

    posix/lock: add setactivelk () fop
    
    Change-Id: Ic7ad7362ac0e8bb0f8861698767c9ab7da539403
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14014
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 888c29bac041ea45973a4a50acb903143a5ce28c
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 17 10:23:02 2016 +0530

    protocol: add setactivelk () fop
    
    Change-Id: I60fe2d59c454095febce4c0fbef87a2dad9636e4
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14013
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 358b5007dfa400d8b09871de81d079d47c51f6a0
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 17 10:22:30 2016 +0530

    io-threads: add setactivelk () fop
    
    Change-Id: I74225a39348f6bb2fbdd1513676a70019227e45f
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14012
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 30f5e460a814358668425860530e5186570e9530
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 17 10:21:59 2016 +0530

    core: add setactivelk () fop
    
    Change-Id: Ic2ba77a1fdd27801a6e579e04e6c0dd93cd7127b
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14011
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 90a8d15ea9778b5089521767137b14cb52b9a2b3
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 17 10:17:42 2016 +0530

    posix/lock: add getactivelk () fop
    
    Change-Id: I99e41a80854d6f90572df755e14757099ae1236f
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/13995
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 2cca000fcc2adbffbb3f5258c57ae564b9e2d51f
Author: Susant Palai <spalai@redhat.com>
Date:   Sat Apr 30 18:00:44 2016 +0530

    protocol: add getactivelk () fop
    
    Change-Id: Ie38198db990f133fe163ba160cdf647e34f83f4f
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/13994
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit c823603f5aab0a60eb076ea43b869739745d9f21
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 17 10:15:39 2016 +0530

    io-threads: add getactivelk () fop
    
    Change-Id: Iaef97ea02dfc54e1a0f23ab972f58b0687b4709c
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/13993
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit c4efd39d339535856c1a0a6b0fad2783587411c9
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 17 10:14:02 2016 +0530

    core: add getactivelk () fop
    
    Change-Id: Ifd0ff278dcf43da064021f5c25e5dcd34347fcde
    BUG: 1326085
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/13970
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f1f6a0e2b09884151c37434bd512cb1482608218
Author: Susant Palai <spalai@redhat.com>
Date:   Sun May 1 23:23:44 2016 +0530

    quota: mark tests/basic/quota.t as bad_test
    
    tests/basic/quota.t regularly leaves a core behind.
    Some of the failed tests:
    * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16439/consoleFull
    * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16440/console
    
    Change-Id: Iacf42c40f768dd2939994bbb87cc7ef366ee495f
    BUG: 1332045
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14136
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 6631f9eb6740961e50c352dfef7c0a9d779d72f8
Author: Susant Palai <spalai@redhat.com>
Date:   Sun May 1 15:15:12 2016 +0530

    quota: mark inode-quota-enforcing.t as bad_test
    
    tests/basic/inode-quota-enforcing.t regularly leaves a core behind.
    
    Some of the failed tests:
    * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16387/console
    * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16390/console
    
    Change-Id: I6c9c8f3503f033a3a10d585efa2de13caf4ac610
    BUG: 1332021
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14135
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit cf943b71db9188dbd87fbb8f97ca610b7004317d
Author: Susant Palai <spalai@redhat.com>
Date:   Sun May 1 15:03:05 2016 +0530

    quota: mark quota-ancestry-building.t as bad_test
    
    tests/basic/quota-ancestry-building.t regularly fails like this:
    
        ./tests/basic/quota-ancestry-building.t (Wstat: 0 Tests: 34 Failed: 6)
          Failed tests:  14-19
        Files=1, Tests=34, 43 wallclock secs ( 0.05 usr  0.01 sys +  2.28 cusr  2.91 csys =  5.25 CPU)
        Result: FAIL
        ./tests/basic/quota-ancestry-building.t: 2 new core files
        End of test ./tests/basic/quota-ancestry-building.t
    
    Some of the failed tests:
     * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16385/console
     * https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/16386/console
    
    Change-Id: Ibbae908b4f752e195e7a7bdd10b102d7bcec312b
    BUG: 1332020
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14134
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 0ec111a27e4e3b6d694eeea3c5ac62a6bfde27ce
Author: Susant Palai <spalai@redhat.com>
Date:   Sun May 1 13:42:36 2016 +0530

    disperse: mark bug-1304988.t as bad_test
    
    tests/bugs/disperse/bug-1304988.t regularly fails like this:
    
        [07:25:34] Running tests in file ./tests/bugs/disperse/bug-1304988.t
        tar: Removing leading `/' from member names
        ./tests/bugs/disperse/bug-1304988.t ..
        1..9
        ok 1, LINENUM:19
        ok 2, LINENUM:20
        ok 3, LINENUM:21
        ok 4, LINENUM:22
        ok 5, LINENUM:23
        ok 6, LINENUM:24
        Started rename 26042
        ok 7, LINENUM:33
        ok 8, LINENUM:34
        not ok 9 Got "in progress ::" instead of "completed", LINENUM:37
        FAILED COMMAND: completed rebalance_status_field patchy
        rebalance done...
        Failed 1/9 subtests
    
        Test Summary Report
        -------------------
        ./tests/bugs/disperse/bug-1304988.t (Wstat: 0 Tests: 9 Failed: 1)
          Failed test:  9
        Files=1, Tests=9, 374 wallclock secs ( 0.02 usr  0.00 sys + 34.12 cusr 15.33 csys = 49.47 CPU)
        Result: FAIL
        End of test ./tests/bugs/disperse/bug-1304988.t
    
    Some of the failed tests:
     * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20261/console
     * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20262/console
     * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20263/console
    
    Change-Id: I0350a720f57f536d283c088e040680bbbe9f8f34
    BUG: 1332022
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14133
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 65dfbc4fd1c2ebd0189c52673b17b416d4c4d37a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Apr 29 13:42:54 2016 +0530

    tests: Add test cases for add/replace brick with granular entry sh
    
    Most of the tests borrowed from Anuradha's original replace-brick
    and add-brick tests under tests/basic/afr/.
    
    Change-Id: I874c04a6af3223e07aa6099b818ff502b6ba2a15
    BUG: 1269461
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14130
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 45fa52d798298623757867c1936045231f0d0af7
Author: Anuradha Talur <atalur@redhat.com>
Date:   Fri Apr 29 16:12:10 2016 +0530

    protocol/client : Implementation of compound fop
    
    Change-Id: Iade71daf3bc70e60833d693ac55151c9cf691381
    BUG: 1303829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/14114
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 93eaeb9c93be3232f24e840044d560f9f0e66f71
Author: Anuradha Talur <atalur@redhat.com>
Date:   Wed Apr 27 15:32:16 2016 +0530

    protocol/client : Refactoring functions
    
    These changes are made to accommodate compound fops.
    The new functions that are added pack
    the arguments required to perform the fops.
    These will be used both by normal fops and compound ones.
    
    Change-Id: I44d9cef8ff1d33aa2f5661689c8e9386d87b2007
    BUG: 1303829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13963
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0d23f5207337fa54be57939eb8d70fe835d4658b
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Apr 26 06:10:16 2016 +0530

    tier/migrator: Fetch the next query file for the next cycle
    
    Problem: When we spawn promote and demote thread, query files
    are build. And only query file with index 0 is picked for migration
    as the first query file. This may not be suitable for scenarios,
    where the file in the query are too big to move in the first cycle,
    as a result file in the other query files always get missed. We need to
    shuffle so that other query files also get a chance.
    
    Fix: Remember the previous first query file and shift it by one index,
    before the migration starts.
    
    Change-Id: I704947bcf4bab6b20b1179a6d9ae4a15a3d51bd9
    BUG: 1330353
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/14068
    Tested-by: Joseph Fernandes
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 0eb8e055b739112ac8b70073ef6e4e3f57c43e08
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Nov 2 08:55:46 2015 +0530

    afr/index: changes for granular entry self-heal
    
    Implements new indices type ENTRY_CHANGES where other
    xlators can add/delete names.
    
    Change-Id: I01c5568997085e11d22ba36a4376c70b78fb3827
    BUG: 1269461
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12482
    Tested-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9b60198b1a22228f85615e377c9b0cbe1e4f4ce6
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed May 27 12:55:50 2015 +0530

    Leases: Add a server side xlator to handle lease requests
    
    Before this patch, there was an effort to implement leases
    in upcall xlator, these patches by Soumya and me can be
    found @ http://review.gluster.org/#/c/10084/
    
    Change-Id: I926728c7ec690727a8971039b240655882d02059
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/11643
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 3c8922d123471de0c5da499420fcac6b10179786
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jul 9 15:22:43 2015 +0530

    Protocol: Add lease fop
    
    Change-Id: I64c361d3e4ae86d57dc18bb887758d044c861237
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/11597
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 80e3832ec16f69d4184172cfc9afa9e42533e0ef
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Apr 29 13:03:40 2016 +0530

    geo-rep: Fix gluster binary invocation while running as cron
    
    When scheduler script was executed as cron, it was unable to detect
    the Gluster binaries.
    
    BUG: 1331658
    Change-Id: Ic9c533586ed9a472765f69aa2f87d004c46d4340
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14111
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ae9d39890fc9a7bcd696cb441c4f3b2eb9677379
Author: Anuradha Talur <atalur@redhat.com>
Date:   Fri Apr 29 19:42:37 2016 +0530

    libglusterfs : packing functions for compound fops
    
    Any xlator that wants to compound fops together can
    use these apis to get the job done.
    
    Change-Id: Ic40fceafecafe70173fd469060e834314826a92c
    BUG: 1303829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13694
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 87de08fdb404492ee090a15fe75aedc17a5ac0b8
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Feb 1 11:12:00 2016 +0530

    rpc: added structures to support compound fops
    
    Change-Id: Ida81e7b3145fb09afa37353244ff8721a4dc4c6a
    BUG: 1303829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    [ndevos: move definitions around to align with changes for bug 1328502]
    Reviewed-on: http://review.gluster.org/13331
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 84c8cc9c5936a2a7539f343c180f06312c8f6d39
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Oct 14 14:14:51 2015 +0530

    cluster/afr: Entry self-heal performance enhancements
    
    Change-Id: I52da41dff5619492b656c2217f4716a6cdadebe0
    BUG: 1269461
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12442
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f0fb05d2cefae08c143f2bfdef151084f5ddb498
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 26 15:27:43 2016 +0530

    glusterd: persist brickinfo->real_path
    
    Since real_path was not persisted and gets constructed at every glusterd
    restart, glusterd will fail to come up if one of the brick's underlying file
    system is crashed.
    
    Solution is to construct real_path only once and get it persisted.
    
    Change-Id: I97abc30372c1ffbbb2d43b716d7af09172147b47
    BUG: 1330481
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14075
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit b246b07896fefb261c9fb07f3f29f0d03b81b88d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 14 10:59:38 2016 +0530

    dht/afr/client/posix: Fail mkdir without gfid-req
    
    Do not allow directory creations without gfids as
    after the directories are created, operations
    on them fail anyway. So it is better to fail mkdir.
    
    BUG: 1317361
    Change-Id: I8f8e3b38bbded1960b7215bac0432500f7e78038
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13690
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit f8948e2c5ce3154f571c8ae16eb5804560e26590
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Apr 27 16:12:49 2016 +0530

    socket: Reap own-threads
    
    Dead own-threads are reaped periodically (currently every minute). This
    helps avoid memory being leaked, and should help prevent memory
    starvation issues with GlusterD.
    
    Change-Id: Ifb3442a91891b164655bb2aa72210b13cee31599
    BUG: 1331289
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/14101
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 36d025ef6f178ce5d8c6f7fa09e1cf236976b5ea
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Apr 27 19:29:09 2016 +0530

    glusterfsd: fix to return actual exit status on mount process
    
    Problem:
    Currently, we always exit mount process with the pid as the exit number
    which is return value of the waitpid(), it is not the exit value of the
    child process
    
    Solution:
    Extract the actual exit code/status in case if the child terminated normally,
    that is, by calling exit(3) or _exit(2), or by returning from main()
    
    Change-Id: Iefec6e27b5a5a98a22f016e49967978853662e37
    BUG: 1331042
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14094
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c2865e83d414e375443adac0791887c8adf444f2
Author: vmallika <vmallika@redhat.com>
Date:   Sat Apr 2 09:50:11 2016 +0530

    quota/glusterd: enhance quota enable and disable process
    
    Previously quota crawl was done from the single mount point,
    this is very slow process if there are huge number of files exists
    in the volume
    
    This RFE will now spawn crawl process for each brick in the
    volume, and  files are looked in parallel independently for each
    brick. This improves the speed of crawling process for
    entire files-system
    
    This patch also fixes below problem
    * Previously, mountdir was created under '/tmp'.
      If someone tries to cleanup '/tmp'/ directory
      then it is very dangerous that we loose volume data
      So create a mount point under /var/run/gluster/tmp
      instead
    
    * Previously, file-system crawl is performed from all the nodes,
      which is a redundant operation and performance will degrade
      The problem is fixed with this patch
    
    Change-Id: Icabedeb44182139ace9c8106793803122388cab8
    BUG: 1290766
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12952
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 72f048ae1ab893e81abff377a46570b5a12b7561
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu Apr 28 11:42:28 2016 +0530

    glusterd: fix max pmap alloc to GF_PORT_MAX
    
    This patch also mops the port max i.e 65535 hard coding
    
    Change-Id: Ia93656d75ceb4c6c4849f9e0ad1b260d5952d4c6
    BUG: 1331253
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14096
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 2f945b86d30eca3a32f5e8e42fbe692ddf4b55be
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 18 21:47:18 2016 +0200

    rpc: split FOPs enum from glusterfs.h
    
    Moving the enumeration of FOPs and some of the other parts that are
    defining the network protocol to the rpc/xdr/ section. These structures
    need some care when modifications are made, moving them out of the
    common glusterfs.h header helps with that.
    
    The protocol definition structures are generated in a new glusterfs-fops
    header. This file is present in rpc/xdr/src/ and libglusterfs/src/, it
    is a little ugly, but prevents the need to update all Makefile.am files
    with the additional -I option for finding the new header file.
    
    The generation of the .c and .h files from the .x descriptions needed
    small modifications to accommodate these changes. The build/xdrgen
    script was improved slightly for this. The .c and .h files are
    incorrectly in the $(top_srcdir), instead of $(top_builddir). This is
    an existing issue, and bug 1330604 has been filed to get that addressed.
    
    Change-Id: I98fc8cf7e4b631082c7b203b5a0a77111bec1fb9
    BUG: 1328502
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14032
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 40e96c17647b281264783520f8fbdd9056332b4c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Apr 26 16:05:04 2016 +0530

    protocol/client: Use loc->pargfid if loc->parent(->gfid) is not filled
    
    Change-Id: Id73bf635ca94dcf7518b33e529ffca07daeeb1f4
    BUG: 1269461
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/14078
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 04d57237099fefa3a92a0cca4c65e43f39c13379
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 28 08:05:29 2016 -0400

    glusterd: default value of nfs.disable, change from false to true
    
    revert gf_msg -> gf_msg_plain change, i.e. restore gf_msg()
    
    Change-Id: Ibdf9906c8a4bf92ba0969a08bb5a5c01dfd74680
    BUG: 1092414
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14105
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 9423bdeed169076ebedd9af40b52aaac58c9839e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Apr 26 16:59:30 2016 +0530

    gfapi: fill iatt in readdirp_cbk if entry->inode is null
    
    If any of dirent have inode as null in readdirp_cbk, which indicates
    that the stat information is not valid. So for such entries, we send
    explicit lookup to fill the stat information.
    
    Change-Id: I0604bce34583db0bb04b5aae8933766201c6ddad
    BUG: 1330567
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/14079
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit fbb655d90aae42398c51469919dde20138e89d7d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Apr 27 14:50:58 2016 +0200

    build: remove unneeded include <sys/user.h> for FreeBSD
    
    The include <sys/user.h> causes a conflicting definition of an RPC
    'struct pmap':
    
        --- fuse-helpers.lo ---
        In file included from /usr/include/rpc/rpc.h:73:0,
                         from ../../../../libglusterfs/src/glusterfs-fops.h:35,
                         from /usr/home/jenkins/root/workspace/freebsd-smoke/libglusterfs/src/glusterfs.h:32,
                         from /usr/home/jenkins/root/workspace/freebsd-smoke/xlators/mount/fuse/src/fuse-bridge.h:22,
                         from /usr/home/jenkins/root/workspace/freebsd-smoke/xlators/mount/fuse/src/fuse-helpers.c:26:
        /usr/include/rpc/pmap_prot.h:89:8: error: redefinition of 'struct pmap'
         struct pmap {
                ^
        In file included from /usr/include/vm/pmap.h:90:0,
                         from /usr/include/sys/user.h:52,
                         from /usr/home/jenkins/root/workspace/freebsd-smoke/xlators/mount/fuse/src/fuse-helpers.c:19:
        /usr/include/machine/pmap.h:299:8: note: originally defined here
         struct pmap {
                ^
    
    It seems that building on FreeBSD still functions without any additional
    warnings or errors, even when the include is removed.
    
    Change-id I98fc8cf7e4b631082c7b203b5a0a77111bec1fb9 identified this
    issue, and this build-fix is needed for applying I98fc8cf7.
    
    BUG: 1198849
    Change-Id: Ib8241b7dc47eb2c3593d2f8ea1d196178e63d02d
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14093
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6530521700d94834d110424f525b95e40bf68094
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Wed Apr 6 11:18:30 2016 -0400

    common-ha: continuous grace_mon log messages in /var/log/messages
    
    messages are seen on RHEL6.x and RHEL7.1 and earlier versions of
    pacemaker. (And RHEL7.2 with RHEL7.1 pacemaker packages.)
    
    It's not possible to query attrd attributes in the older version,
    only set/update/clear them. The messages come from invalid attempts
    to query the attributes.
    
    However it is possible to query crm attributes. The fix here is to
    create a "shadow" crm attribute for the attrd attribute. Changes are
    made to both, queries are made on the crm attribute.
    
    (Resource Agents "follow" the attrd attribute using constraint locations,
    so we must keep the attrd attribute.)
    
    Change-Id: I84ac1a80673e528d98b67b7d5062e21dcf744d4a
    BUG: 1324509
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13919
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 3af9b53d13a88b93d026d599c9f86f8bb1845b6c
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue Apr 26 18:40:04 2016 +0530

    glusterd: try to connect on GF_PMAP_PORT_FOREIGN aswell
    
    This patch fix couple of things mentioned below:
    
    1. previously we use to try to connect on only GF_PMAP_PORT_FREE
    in the pmap_registry_alloc(), it could happen that some foreign process
    would have freed the port by this time ?, hence it is worth giving a try on
    GF_PMAP_PORT_FOREIGN ports as well instead of wasting them all.
    
    2. fix pmap_registry_remove() to mark the port asGF_PMAP_PORT_FREE
    
    3. added useful comments on gf_pmap_port_type enum members
    
    Change-Id: Id2aa7ad55e76ae3fdece21bed15792525ae33fe1
    BUG: 1322805
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14080
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 1890e5e09203e65b1c64f0f13c213d8944b81b87
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Apr 27 11:41:05 2016 +0000

    Swap order of GF_EVENT_SOME_CHILD_DOWN enum
    
    GF_EVENT_SOME_CHILD_DOWN value seems to be mismatching between master and 3.7.
    Fix the master since 3.7 is a release branch and GF_EVENT_SOME_CHILD_DOWN was
    added newly and hence should be in the end in the enum list.
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    
    Change-Id: I1f758550d6300f6750d1574302096d8e7f493549
    BUG: 1330974
    Reviewed-on: http://review.gluster.org/14092
    Tested-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit b5cfe948cb3569f034da80ac97b5d2f028b3b0e5
Author: Anoop C S <anoopcs@redhat.com>
Date:   Fri Mar 18 10:32:09 2016 +0530

    features/trash: wind mkdir with special pid
    
    Recent changes done w.r.t handling of mkdir calls in posix translator
    resulted in crashing the brick process from trash translator. This was
    due to the changes made in posix translator to return EPERM for every
    mkdir calls without 'gfid-req' set in dictionary. In order to avoid
    gfid mismatches during directory creation from brick side trash
    translator does not set 'gfid-req'. This patch is to have an exemption
    for trash based on a special pid set for those mkdir calls originating
    from trash translator and to reset it in callback.
    
    This patch also includes a small optimization to the existing test case
    for trash feature.
    
    Change-Id: I59f084ac875e54342ecf2bffa6e43ebd84814153
    BUG: 1317361
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/13776
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c4d67a8338b42d6485f49999f310cbb9ed5359c5
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Feb 15 18:16:04 2016 +0530

    libglusterfs: Add debug and trace logs for stack trace
    
    It has become very difficult to identify the xlator which returned
    negative op_ret. Being able to just change the log level and
    visualize the stack is helpful in such cases.
    
    Change-Id: I6545b4802c1ab4d0d230d5e9e036afb2384882e1
    BUG: 1330052
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13448
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 302e218f68ef5edab6b369411d6f06cafea08ce1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Apr 22 11:43:45 2016 +0530

    cluster/afr: Do not fsync when durability is off
    
    BUG: 1329501
    Change-Id: Id402c20f2fa19b22bc402295e03e7a0ea96b0c40
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14048
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 88a386b9c87072787a3b712073cbf19a74b0bd20
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue Apr 26 21:42:23 2016 +0530

    rpc: fix gf_process_reserved_ports
    
    this patch also does minor code cleanups.
    
    Change-Id: I0d005bd0f9baaaae498aa1df4faa6fcb65fa7a6e
    BUG: 1198849
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13997
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 49796290c9772ce49e5a1666cc2f3cc875e59e49
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 26 10:10:05 2016 -0400

    packaging: %postun libs ldconfig: relative path `1' used to build cache
    
    %postun libs isn't 'closed' by the following %postun server on RHEL6
    due to the %ifdef...%endif
    
    But -server has /usr/lib*/libgfdb.so.x, so we should be running
    /sbin/ldconfig! Which conveniently fixes the closing issue.
    
    Change-Id: Icc365eefc5453c40e02b59288a4e8023b82baa7b
    BUG: 1330583
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14081
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 537557da59876536d33cd25a8ef485e7b5fe8849
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Apr 26 14:52:29 2016 +0530

    gfapi: set need_lookup flag on response list
    
    We set need_lookup flag for entries returned by readdirp
    to force lookup. Currently we are setting on the previously
    stored list, rather than response list returned by readdirp.
    
    This patch will iterate over current list returned by readdirp
    and will set need_lookup flag.
    
    Change-Id: Ibd6fcbc188f4c87f40ece7a9dcda27645401c240
    BUG: 1330476
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/14073
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 2a6c6de35130328cfb6f95a6d7794dcb01b4004d
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Apr 26 19:49:34 2016 +0530

    Rename enum _gf_client_pid to _gf_special_pid
    
    Till now _gf_client_pid enum has been used to define special PIDs used
    by glusterfs clients like shd, quotad etc. In order to have this enum
    capable of holding all other special PIDs including the one used by
    trash translator, _gf_client_pid is being renamed to _gf_special_pid.
    
    Change-Id: Id123127771f18aa55d39f335801a54810848d7bc
    BUG: 1330616
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/14083
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 60cf56b1289bbf574a38a7f99f8cacb692f65474
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 18 19:34:26 2016 +0200

    snapshot: svc_stat collides with define from /usr/include/rpc/svc.h
    
    Compiling fails with this error:
    
        snapview-client.c:559:24: error: macro "svc_stat" passed 4 arguments, but takes just 1
                   dict_t *xdata)
                                ^
        snapview-client.c:560:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token
         {
         ^
        snapview-client.c:2412:26: error: ‘svc_stat’ undeclared here (not in a function)
                 .stat          = svc_stat,
                                  ^
    
    svc_* is the common prefix for (SUN)RPC functions provided by system
    headers. svc_stat() seems to be an existing function name. This happens
    because change-id I98fc8cf7e4b631082c7b203b5a0a77111bec1fb9 causes
    <rpc/rpc.h> included through "glusterfs.h". Prepending gf_ for all svc_*
    functions works around the symbol collision.
    
    Change-Id: Idc86b719c48675a5154c54d844c1899d14d46e2a
    BUG: 1328502
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14035
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit a4f84d786b596387aa0d659fb5cc8a933c95c01b
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue Mar 15 06:16:31 2016 -0400

    glusterd: default value of nfs.disable, change from false to true
    
    Next step in eventual deprecation of glusterfs nfs server in favor
    of ganesha.nfsd.
    
    Also replace several open-coded strings with constant.
    
    Change-Id: If52f5e880191a14fd38e69b70a32b0300dd93a50
    BUG: 1092414
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13738
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 3c35329feb4dd479c9e4856ee27fa4b12c708db2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Dec 23 13:49:14 2015 +0530

    afr: propagate child up event after timeout
    
    Problem: During mount, afr waits for response from all its children before
    notifying the parent xlator. In a 1x2 replica volume , if one of the nodes is
    down, the mount will hang for more than a minute until child down is received
    from the client xlator for that node.
    
    Fix:
    When parent up is received by afr, start a 10 second timer. In the timer call
    back, if we receive a successful child up from atleast one brick, propagate the
    event to the parent xlator.
    
    Change-Id: I31e57c8802c1a03a4a5d581ee4ab82f3a9c8799d
    BUG: 1054694
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11113
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 41fef03eb929a08588a4f4ebf4638096a5918a62
Author: Jonathan Holloway <jholloway@redhat.com>
Date:   Mon Apr 11 20:32:26 2016 -0500

    distaflibs: organize distaflibs to use namespace packages
    
    Organized the distaflibs directory tree to accomodate namespace packages.
    
    * Allows multiple distaf library packages to install in single namespace package.
    - Created distaflibs-gluster directory as root for package configs, docs, etc.
    - Created setup.py file to install distaflibs-gluster package into namespace.
    - Created distaflibs-gluster/distaflibs namespace package dir and init.
    - Created distaflibs-gluster/distaflibs/gluster as package dir.
    - Copied distaf gluster library files into package dir.
    
    Requires the distaf package.
    
    distaflibs-gluster installs into /usr/lib/python2.7/site-packages/distaflibs/gluster
    
    Change-Id: I775c4f1526880ea606f35c3616abb9aaf2f3b886
    BUG: 1330346
    Signed-off-by: Jonathan Holloway <jholloway@redhat.com>
    Reviewed-on: http://review.gluster.org/13972
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: M S Vishwanath Bhat <vbhat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 1866836749c2a12ae50abd109429da072ebe05ba
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 12 11:35:38 2016 -0400

    packaging: additional dirs and files in /var/lib/glusterd/
    
    Add the missing /var/lib/glusterd files and dirs found by
    downstream testing. Use a loop to create hook dirs instead
    of open-coding. Merge the %ghost and non-ghost dirs in
    -server %files section for easier maintenance.
    
    Eliminate a benign warning for enabling non-existent
    glusterfsd.{init,service} which is only relevant to Fedora
    builds
    
    Don't reject glusterfs.spec.in changes because of long lines
    
    Change-Id: I5802175d729e0168eea879a2a61626b0b73d77c8
    BUG: 1326410
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13981
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a9b78f1ebe5836c23afebf4e3509f0bb13792865
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Mar 15 12:47:24 2016 +0530

    devel-tools: vagrant setup for creating devel VMs
    
    Created vagrant setup for Gluster developers. The Vagrantfile
    is modifed from the work done by Chris (cblum@redhat.com).
    Ansible structure is taken from test vagrant infra initially
    posted by rtalur.
    
    This vagrant setup can create one or more VM (using libvirt),
    create thinly provisioned LVs, format them with XFS and mount them.
    It will also compile the source from host machine (/work/source) and
    install gluster. It will also do peer probe.
    
    Change-Id: Ie984f661bb5dc9cfc4059643389d3c80b2cae21d
    BUG: 1327976
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/13734
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Raghavendra Talur <rtalur@redhat.com>

commit f93761c547c39fad20f9aa96d4baf2641500b9a0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 26 12:46:18 2016 +0530

    glusterd: fix validation of lower op-version check in volume set
    
    Commit 2d87a98 introduced a validation to fail lowering down the
    cluster.op-version. Commit 2eb8758 actually changed the variable value from
    cluster's op-version to volume's op-version which resulted the logic go for a
    toss.
    
    Change-Id: I70df32b75c3a3fe47dc840c4a655059e5b124bca
    BUG: 1315186
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/14069
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit edeb67a5344389f88a6912460fb0cf2e76a32df3
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Apr 13 12:50:49 2016 +0530

    inode: Always fetch first entry from the inode lists during inode_table_destroy
    
    In inode_table_destroy, we iterate through lru and active lists
    to move the entries to purge list so that they can be destroyed
    during inode_table_prune.
    
    But if used "list_for_each_entry" or "list_for_each_entry_safe"
    to iterate, we could end up accessing the entries which may have
    got moved to different(purge) lists in the process and can result
    in either infinite loop or crash. The safe approach seems to fetch
    the first entry of the list in each iteration till it gets empty.
    
    Change-Id: I24a18881833bd9419c2d8e5e8807bc71ec396479
    BUG: 1326627
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13987
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8590c1cf3c27468177c425c920cab01f52b251e5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Apr 19 15:30:19 2016 +0530

    geo-rep: Fix checkpoint issue in scheduler
    
    If checkpoint is not met, Scheduler script should touch the
    Mount point so that SETATTR will get recorded in every brick
    Changelog. Script was not touching the mount point in each iteration.
    
    BUG: 1328399
    Change-Id: I2718a764fb3e550742c9dcd316724683561ddf18
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14029
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 007dce0c7093a8534dd23340a38a8ce3cf3cd048
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Apr 25 17:16:42 2016 +0530

    storage/posix: change the conflicting msg-id
    
    Change-Id: I11b2ffb73b2358380771921548fa2c51da6ad93f
    BUG: 1323040
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/14062
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 9996f95b28b3782887b7c233cdc0ba686c38b245
Author: Anuradha Talur <atalur@redhat.com>
Date:   Thu Apr 21 17:20:09 2016 +0530

    performance/decompounder: Introducing decompounder xlator
    
    This xlator decompounds the compound fops received,
    and executes them serially.
    
    Change-Id: Ieddcec3c2983dd9ca7919ba9d7ecaa5192a5f489
    BUG: 1303829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13577
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2dc22adbf3361bdab10924943371492cc2817d8a
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Apr 25 14:05:30 2016 -0400

    glusterd: SSL certificate depth volume option is incorrect
    
    Between 3.7.1 and 3.7.2 a typo was introduced changing the string
    ssl-cert-depth to ssl-cetificate-depth. [sic]
    
    rpc/rpc-transport/socket/src/socket.c still expects the string
    ssl-cert-depth.
    
    Also replace a couple errant tabs with spaces.
    
    Change-Id: I0621258470bd831c97008b56123a9dc7029d73f1
    BUG: 1330248
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/14066
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 0a43265f1b10c35506fe82a525aa0fa43af6c0cd
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 4 14:55:20 2016 +0530

    nsr/jbr: Renaming nsr to jbr
    
    As per community consensus, we have decided to rename
    nsr to jbr(Journal-Based-Replication). This is the patch
    to rename the "nsr" code to "jbr"
    
    Change-Id: Id2a9837f2ec4da89afc32438b91a1c302bb4104f
    BUG: 1328043
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13899
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c3353cdc4a3bcea416953af0585a08f33c5d4639
Author: Michael Scherer <misc@redhat.com>
Date:   Mon Apr 25 18:23:48 2016 +0200

    Use pthread_equal to compare threads
    
    The man pages about pthreads are quite clear on the fact that pthread_t
    is supposed to be opaque, and so can't be compared using the equality
    operator.
    
    Change-Id: Id69e166ed73a98668d19a71cd6d9ab9a0429ec38
    BUG: 1330225
    Signed-off-by: Michael Scherer <mscherer@redhat.com>

commit a9ccd0c8ea6989c72073028b296f73a6fcb6b896
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Apr 22 12:07:31 2016 +0530

    tier/dht: check for rebalance completion for EIO error
    
    When an ongoing rebalance completion check task been
    triggered by dht, there is a possibility of a race
    between afr setting subvol as non-readable and dht updates
    the cached subvol. In this window a write can fail with EIO.
    
    Change-Id: I42638e6d4104c0dbe893d1bc73e1366188458c5d
    BUG: 1329503
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/14049
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 61b42d3cdc2962101f5976f89c28de381b3525aa
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Apr 15 05:15:33 2016 -0400

    dht/rebalance: Handle GF_DEFRAG_STOP
    
    Problem: On a rebal stop, the migrator threads don't intimate the
    crawler thread to wake up in case it is waiting on signal from
    migrator thread.
    
    Change-Id: I3cc4be41a4db25f48fee059ebb79a97ee99dcd00
    BUG: 1327507
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/14004
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3021a9ab666e9f1a5116df84e77659aca613e955
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jul 20 14:29:24 2015 +0530

    dht: Add lease() fop
    
    Change-Id: I0bbc2c2ef115c78393f6570815a5b80316e7e4be
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/11720
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ef3d6fd06cf0712774e721eaf1d0b072f54e0b8a
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Apr 20 15:02:16 2016 +0530

    vagrant-test: added more options and centos6 base box
    
    Options added are
    
    1. destroy-now option
    Now you can call run-tests-in-vagrant.sh with --destroy-now option to
    destroy the VM corresponding to the git branch and delete the
    corresponding vagrant dir.
    Usage: run-tests-in-vagrant.sh --destroy-now
    
    2. os option
    With --os option you can specify the os to be used for VM.
    Default is fedora and this patch adds support for centos6.
    Usage: run-tests-in-vagrant.sh --os="centos6"
    
    3. destroy-after-test option
    When specified the VM is deleted right after the tests are executed. If
    the script exited before running tests then the VM is left as is for
    further debugging.
    
    4. verbose option
    Many log messages which were mainly added for initial debugging have
    been removed now. All vagrant and compilation outputs have been redirected to
    /dev/null. To enable these logs please use --verbose option.
    
    5. ssh option
    --ssh option now allows one to ssh into the VM from topdir of source
    code thereby avoiding the hassle of cd'ing into the vagrant dir.
    
    Box added
    
    1. This patch adds a centos6 base box which is currently made available
    at atlas.hashicorp.com. Template files for this box are available
    under tests/vagrant/vagrant-template-centos6 directory. The default box is
    moved under vagrant-template-fedora directory to keep up with the naming
    convention.
    
    Enhancements
    
    This patch also modifies the cpu and memory allocation mechanism for
    the VMs. All the cpus on the host are used and 1/4 of the memory
    available on host is used.
    
    Bug Fixes
    1. Fix CFLAGS not passed to configure error
        If CFLAGS is assigned and then configure is called under sudo, the cflags
        are not passed onto configure.
    
    Change-Id: Iee1811a7d2b77785f6167f4706135a8f584a6bbd
    BUG: 1291537
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/14046
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 19fd9a371fff4ece2c617f1e7194ffcee039f21e
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu Apr 21 14:38:16 2016 +0530

    runner: extract and return actual exit status of child
    
    Intro:
    pid_t waitpid(pid_t pid, int *status, int options);
    
    The waitpid() system call suspends execution of the calling process
    until a child specified by pid  argument has  changed  state.
    
    Here the ret (pid) value is not equal to the exit status of the child process.
    Check manpages for more info on this.
    
    Problem:
    In the current runner framework we always return the pid i.e ret value
    of the waitpid, as said above it is not the exit value of the child process
    
    Solution:
    Extract the actual exit code/status in case if the child terminated normally,
    that is, by calling exit(3) or _exit(2), or by returning from main()
    
    Change-Id: Iffae99a43e540af66917b3745f21ea3c2a5a3c2d
    BUG: 1329129
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/14042
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 760dfb6e8aebc44b419e8943e4e3895591097b8b
Author: vmallika <vmallika@redhat.com>
Date:   Thu Apr 14 17:51:19 2016 +0530

    cli/quota: Sort the list output alphabetically by path
    
    Change-Id: I0b124e119d167817be2ae3eb52ac6c80fc7db5d1
    BUG: 1320716
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/14000
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit fe6c4efcc66bca84aaceb352de38f0b58b70b780
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 18 14:44:18 2016 +0530

    clone/snapshot: Save restored_from_snap for clones
    
    Bricks of cloned volumes are lvm bricks mounted in
    /run/gluster, which on reboot of the node gets
    cleared. Hence, these brick paths need to be recreated
    on glusterd restart and the appropriate lvms are
    mounted.
    
    Change-Id: I6da086288c0dbdcedf3a20fd53f25e3728bea473
    BUG: 1328010
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/14021
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 30b66ef3750ece0fb56e673afaca7948d53511e1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 18 19:24:41 2016 +0200

    build: reduce warnings when building the syscall compatibility layer
    
    For whatever reason my Fedora 23 started to complain loudly when
    compiling syscall.c.
    
    Change-Id: I72d278d6dc9abb77018c2590c113552383b639d1
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14034
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 68034a3f92a779f8fe67525472f450d473769dd3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Apr 19 17:52:26 2016 +0200

    build: remove unused gf_darwin_compat_*xattr() functions
    
    These functions are not implemented or used anywhere, there is no reason
    to have them declared in the compatibility header.
    
    Change-Id: If33ed2cc0be86b9f04f05f3af822758e263f6d53
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/14033
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 13e458cd70ac1943cf68d95a2c6517663626c64a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Apr 23 05:30:08 2016 +0530

    cluster/afr: Fix inode-leak in data self-heal
    
    Thanks to Olia-Kremmyda for finding the bug on github review,
    https://github.com/gluster/glusterfs/commit/b8106d1127f034ffa88b5dd322c23a10e023b9b6
    
    Change-Id: Ib8640ed0c331a635971d5d12052f0959c24f76a2
    BUG: 1329773
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14052
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 62027360a695ff499c0492f1bc37f585ed4576c1
Author: jiffin tony Thottan <jthottan@redhat.com>
Date:   Thu Mar 10 04:03:19 2016 -0800

    Revert "NFS-Ganesha : scripts related changes for supporting multiple export entires for volume"
    
    This reverts change-id I2286af4877f96f4334435818f67beea87efa2b1f.
    While testing, I had found that ganesha-ha.sh is not working as expected. It is
    almost equivalent to rewrite entire thing again
    
    Change-Id: Ia85e50fe8e043e8a2bc6441b7c45dcc726b36672
    BUG: 1275966
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13673
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 3c04a91f5245708d0a148bf01cfdac1d0d59c797
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Apr 24 06:31:14 2016 +0530

    statedump: Prevent (null) typestr to be printed
    
    Problem:
    After the commits: 7e44c783ad731856956929f6614bbe045c26ea3a - lock: use
    spinlock only on multicore systems
    a6aecae2cd8171b8538bfe5d2800bdd157380b85 - nfs: fix lock variable type
    
    we see a lot of "[global.glusterfs - usage-type (null) memusage]" in statedump
    because lock status is not all-zeros after init, and the memcmp to check that
    a datatype is never allocated is invalid.
    
    Fix:
    Changed if a datatype is allocated or not check based on total_allocs. Also
    removed setting typestr to NULL on gf_free even when num_allocs is 0. Because
    even that is leading to 'null' memusage string to be printed in statedump.
    
    BUG: 1329870
    Change-Id: If2b01a557cbdc787625db32e276e06cee3ac46ee
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/14054
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit bfd5c7683708949e87bd40fb0ddb6933021c6912
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon Apr 11 15:28:07 2016 +0530

    qemu-block: mop leftover code
    
    This patch cleans off the code that was leftover by '6860968'
    which basically remove qemu-block from gluster code repo
    
    Also update 'bug-1168803-snapd-option-validation-fix.t'
    which previously used 'features.file-snapshot' for checking
    'volume set' for some reason.
    
    Change-Id: I2c4f28e186b74a4ce55d48c0fa7f3f79ca1901b5
    BUG: 1198849
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13964
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 823bda0f28cba1b0632d99a22cdecaee16c6db56
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Apr 1 15:16:23 2016 +0530

    cluster/distribute: detect stale layouts in entry fops
    
    dht_mkdir ()
    {
          first-hashed-subvol = hashed-subvol for "bname" in in-memory
                                layout of "parent";
          inodelk (SETLKW, parent, "LAYOUT_HEAL_DOMAIN", "can be any
                   subvol, but we choose first-hashed-subvol randomly");
          {
    begin:
                hashed-subvol = hashed-subvol for "bname" in in-memory
                                layout of "parent";
                hash-range = extract hashe-range from layout of "parent";
    
                ret = mkdir (parent/bname, hashed-subvol, hash-range);
                if (ret == "hash-value doesn't fall into layout stored on
                           the brick (this error is returned by posix-mkdir)")
                {
                    refresh_parent_layout ();
                    goto begin;
                }
    
          }
          inodelk (UNLCK, parent, "LAYOUT_HEAL_DOMAIN",
                   "first-hashed-subvol");
    
          proceed with other parts of dht_mkdir;
    }
    
    posix_mkdir (parent/bname, client-hash-range)
    {
    
           disk-hash-range = getxattr (parent, "dht-layout-key");
           if (disk-hash-range != client-hash-range) {
                  fail-with-error ("hash-value doesn't fall into layout
                                    stored on the brick");
                  return 0;
           }
    
           continue-with-posix-mkdir;
    }
    
    Similar changes need to be done for dentry operations like create,
    symlink, link, unlink, rmdir, rename. These will be addressed in
    subsequent patches. This patch addresses only mkdir codepath.
    
    This change breaks stripe tests, as on some striped subvols dht layout
    xattrs are not set for some reason. This results in failure of
    mkdir. Since striped volumes are always created with dht, some tests
    associated with stripe also fail. So, I am making following tests
    changes (since stripe is out of maintainance):
    * modify ./tests/basic/rpc-coverage.t to not to use striped volumes
    * mark all (2) tests in tests/bugs/stripe/ as bad tests
    
    Change-Id: Idd1ae879f24a48303dc743c1bb4d91f89a629e25
    BUG: 1323040
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/13885
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit 8f3ad1e3ede77fa5f8c8d606e18a7e83865a822c
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Mar 11 15:27:30 2016 +0530

    snapshot/quota: Copy quota.cksum during snapshot operations
    
    A volume having a quota.conf file, should always have
    a quota.cksum file too. Based on this above assumption
    modifying glusterd_copy_quota_files() to always copy
    quota.cksum, if quota.conf is present.
    
    This change will be reflected when a snapshot is created,
    restored and cloned.
    
    Change-Id: Ia49dc26eacef32eeb8f7d7d9553c80e304b08779
    BUG: 1316848
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13760
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit a5bd2f2aded44a88edea4001bddba8865a516503
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Feb 23 19:22:45 2016 -0500

    features/crypt: Whitespace Cleanup
    
    Change-Id: Ib7f2ceb3851a3c333e3d58e3e2713fe4d59616b1
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/13502
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit fb55cf6aea208b8f493adc011b3b0a0d734cc8a1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 21 12:01:47 2016 +0530

    features/marker: Fix dict_get errors when key is NULL
    
    Change-Id: I25e497459441334c13af77b3fec83c42a7a92ac4
    BUG: 1319581
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13793
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit f8a6cd1d2715fc13f130b7c76d8aea75de8b5133
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jul 9 15:31:30 2015 +0530

    posix: Add lease() fop
    
    Change-Id: I20007d7ff4536ae8180425c84a1aa7863a6f2447
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/11598
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit ba9c40ab4ee238bb6f5e6e275f339484690bc84e
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jul 9 15:28:59 2015 +0530

    io-threads: Add lease() fop
    
    Change-Id: Ie4921867948d23b8b6c570196e88680cdb5ebfbc
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/11599
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 63918789fbb5f3a2d381e0f960f2dcbaf1b7ff72
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Jul 9 15:06:49 2015 +0530

    core: add lease fop
    
    Change-Id: Ia27d66b1061b0377857827515590eb89b18515c9
    BUG: 1319992
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/11596
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e964dd74fa805124005a5b2cb031ecbc34198b9a
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Apr 18 15:27:01 2016 +0530

    quota : fix null dereference issues in quota
    
    Change-Id: I3805b206077718da26adbeb8b29a53642e00886f
    BUG: 1328696
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/14022
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b6a0780d86e7c6afe7ae0d9a87e6fe5c62b4d792
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 31 14:40:09 2016 +0530

    cluster/afr: Fix spurious entries in heal info
    
    Problem:
    Locking schemes in afr-v1 were locking the directory/file completely during
    self-heal. Newer schemes of locking don't require Full directory, file locking.
    But afr-v2 still has compatibility code to work-well with older clients, where
    in entry-self-heal it takes a lock on a special 256 character name which can't
    be created on the fs. Similarly for data self-heal there used to be a lock on
    (LLONG_MAX-2, 1). Old locking scheme requires heal info to take sh-domain locks
    before examining heal-state.  If it doesn't take sh-domain locks, then there is
    a possibility of heal-info hanging till self-heal completes because of
    compatibility locks.  But the problem with heal-info taking sh-domain locks is
    that if two heal-info or shd, heal-info try to inspect heal state in parallel
    using trylocks on sh-domain, there is a possibility that both of them assuming
    a heal is in progress. This was leading to spurious entries being shown in
    heal-info.
    
    Fix:
    As long as there is afr-v1 way of locking, we can't fix this problem with
    simple solutions.  If we know that the cluster is running newer versions of
    locking schemes, in those cases we can give accurate information in heal-info.
    So introduce a new option called 'locking-scheme' which if it is 'granular'
    will give correct information in heal-info. Not only that, Extra network hops
    for taking compatibility locks, sh-domain locks in heal info will not be
    necessary anymore. Thus it improves performance.
    
    BUG: 1322850
    Change-Id: Ia563c5f096b5922009ff0ec1c42d969d55d827a3
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13873
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit bc89311aff62c78102ab6920077b6782ee99689a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Apr 15 16:37:18 2016 +0530

    geo-rep: Fix hostname mismatch between volinfo and geo-rep status
    
    When Volume was created using IP, Gluster Volume info shows IP address
    But Geo-rep shows hostname if available, So difficult to map the outputs
    of Volume Info and Georep status output.
    
    Schedule Geo-rep script(c#13279) will merge the output of Volume info and
    Geo-rep status to get offline brick nodes information. This script was
    failing since host info shown in Volinfo is different from Georep status.
    Script was showing all nodes as offline.
    
    With this patch Geo-rep gets host info from volinfo->bricks instead of
    getting from hostname. Geo-rep status will now show same hostname/IP which
    was used in Volume Create.
    
    BUG: 1327553
    Change-Id: Ib8e56da29129aa19225504a891f9b870f269ab75
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/14005
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 690715bb3e341f673a71d1dc8b80bb35aa29c75d
Author: hari <hgowtham@redhat.com>
Date:   Wed Apr 6 16:16:47 2016 +0530

    Tier: tier command fails message when any node is down
    
    PROBLEM: the dict doesn't get set on the node if its down.
    so while printing the output on cli we get a ENOENT
    which ends in a tier command failed.
    
    FIX: this patch skips the node that wasn't available
    and carrys on with the next node for both tier status
    and tier detach status.
    
    Change-Id: I718a034b18b109748ec67f3ace56540c50650d23
    BUG: 1324439
    Signed-off-by: hari <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13918
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit abd47f27848c9bb2bf5bc371367c3d41f526ad50
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Wed Apr 13 16:40:40 2016 +0530

    quota: setting 'read-only' option in xdata to instruct DHT to not heal
    
    When quota is enabled the quota enforcer tries to get the size of the
    source directory by sending nameless lookup to quotad. But if the rename
    is successful even on one subvol or the source layout has anomalies then
    this nameless lookup in quotad tries to heal the directory which requires
    a lock on as many subvols as it can. But src is already locked as part of
    rename. For rename to proceed in brick it needs to complete a cluster-wide
    lookup. But cluster-wide lookup in quotad is blocked on locks held by rename,
    hence a deadlock. To avoid this quota sends an option in xdata which instructs
    DHT not to heal.
    
    Change-Id: I792f9322331def0b1f4e16e88deef55d0c9f17f0
    BUG: 1252244
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13988
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 26d16b90ec7f8acbe07e56e8fe1baf9c9fa1519e
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Mar 23 13:47:27 2016 +0530

    mount/fuse: report ESTALE as ENOENT
    
    When the inode/gfid is missing, brick report back as an ESTALE
    error. However, most of the applications don't accept ESTALE as an
    error for a file-system object missing, changing their behaviour.
    
    For eg., rm -rf ignores ENOENT errors during unlink of
    files/directories. But with ESTALE error it doesn't send rmdir on a
    directory if unlink had failed with ESTALE for any of the files or
    directories within it.
    
    Thanks to Ravishankar N <ravishankar@redhat.com>, here is a link as to
    why we split up ENOENT into ESTALE and ENOENT.
    http://review.gluster.org/#/c/6318/
    
    Change-Id: I467df0fdf22734a8ef20c79ac52606410fad04d1
    BUG: 1245065
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/13816
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit c530506845c5e86ab745fd5753620f2ca48d36e5
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Mar 31 09:38:55 2016 +0200

    Build fix: remove undefined -I${rpclibdir}
    
    The variable is not defined anywhere, remove it.
    
    Change-Id: Iaefb349cceb4108ac22c44cd32e5ea3d3c8bc0e5
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    BUG: 1129939
    Reviewed-on: http://review.gluster.org/13867
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b223a674f2c300fecb7043e11f80c8e33309f4d3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Apr 12 11:27:08 2016 +0200

    tests: fix syntax error in 0symbol-check.t
    
    While running the tests, 0symbol-check.t gives the following syntax
    error:
    
        tests/basic/0symbol-check.t: line 25: [: missing `]'
    
    BUG: 1267967
    Change-Id: Iba454387ebdfa75872036ebe168115500c85d0b1
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13976
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 8deedef565df49def75083678f8d1558c7b1f7d3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 17 19:42:00 2016 +0530

    cluster/afr: Fix partial heals in 3-way replication
    
    Problem:
    When there are 2 sources and one sink and if two self-heal daemons
    try to acquire locks at the same time, there is a chance that it
    gets a lock on one source and sink leading partial to heal. This will
    need one more heal from the remaining source to sink for the complete
    self-heal. This is not optimal.
    
    Fix:
    Upgrade non-blocking locks to blocking lock on all the subvolumes, if
    the number of locks acquired is majority and there were eagains.
    
    BUG: 1318751
    Change-Id: Iae10b8d3402756c4164b98cc49876056ff7a61e5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13766
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit d5409aae63a7ac5e5b3ea6cfa16c6250a028291c
Author: Sakshi <sabansal@redhat.com>
Date:   Wed Apr 15 13:28:24 2015 +0530

    libglusterfs: coverity fix
    
    fix missing varargs cleanup
    
    CID 1124856: string overflow
    
    CID 1124656: NULL return
    
    CID 1124374: constant expression
    
    Change-Id: Iead530c599bdfef05a40c68b892215f4e4f02247
    BUG: 789278
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/9630
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1c9c776352c60deeda51be66fda6d44bf06d3796
Author: Zhou Zhengping <johnzzpcrystal@gmail.com>
Date:   Sun Apr 10 23:56:17 2016 +0800

    rpc: check the right variable after gf_strdup
    
    Change-Id: If4628bd37f2c85a070f6c3b3e0583d939100d7ec
    BUG: 1325683
    Signed-off-by: Zhou Zhengping <johnzzpcrystal@gmail.com>
    Reviewed-on: http://review.gluster.org/13934
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 401d591de168fdb648663f01c4c4f8ed60777558
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Wed Apr 13 14:38:11 2016 +0530

    Revert "glusterd: Allocate fresh port on brick (re)start"
    
    This reverts commit 34899d7
    
    Commit 34899d7 introduced a change, where restarting a volume or rebooting
    a node result into fresh allocation of brick port. In production
    environment generally administrator makes firewall configuration for a
    range of ports for a volume. With commit 34899d7, on rebooting of node
    or restarting a volume might result into volume start fail because
    firewall might block fresh allocated port of a brick and also it will be
    difficult in testing because of fresh allocation of port.
    
    Change-Id: I7a90f69e8c267a013dc906b5228ca76e819d84ad
    BUG: 1322805
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/13989
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 4910caece70d5c3e28453174b990d2b764359e9a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 13 21:10:22 2016 +0530

    mgmt/glusterd: Change op-version for max-threads, shd-wait-qlength
    
    Change-Id: I0e2dcacfe0804737d2cff76d2a0ee51a520ccec2
    BUG: 1221737
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13992
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f5383e11291b01b840c9172c4048a676e8bea518
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Apr 11 01:51:38 2016 -0400

    extras: Fix the create_new_xlator tool
    
    It is currently importing a non existing module.
    Remove the same.
    
    Change-Id: I7f4b790ba42d8683575768ec14851932a8cddc43
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13960
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e9d5f8c753ae496ac86188764cdff4eac8b820a7
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Apr 7 01:08:26 2016 -0400

    extras: Enable failed-tests.py to fetch regression summary for more than 30 builds
    
    Credits: Raghavendra Talur
    
    Change-Id: I4a895f57e9ab0e5d28e78c467e5b52d347586706
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13922
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 59aa2e8790a3b70e357463a3b26ee0a10742ecb7
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 12 09:43:13 2016 +0530

    tests: fix regression failure from bug-1322772-real-path-fix-for-snapshot.t
    
    There is no need to unmount the brick as doing so we loose all the xattrs on the
    brick and while restarting glusterd brick doesn't come up
    
    Change-Id: Ic1fa8b72f6cfcad564c62bcef1d022b083263ecc
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13974
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit eb7cbf37df611fc5288eb75c7d46ef44fe7d6bab
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Mon Feb 9 14:28:21 2015 +0530

    glusterfsd: coverity fix
    
    CID 1124846: string overflow
    CID 1124363: checked return value
    CID 1210982: unsigned compare
    
    Change-Id: I5995d98c07750615657668535fcc23ac30b3523b
    BUG: 789278
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/9608
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 05bc8bfd2a11d280fe0aaac6c7ae86ea5ff08164
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu Mar 17 13:50:31 2016 +0530

    glusterd-client: switch volfile server incase existing connection breaks
    
    Problem:
    Currently, say we have 10 Node gluster volume, and mounted it using
    Node 1 (N1) as volfile server and the rest as backup volfile servers
    
    $ mount -t glusterfs -obackup-volfile-servers=<N2>:<N3>:...:<N10> <N1>:/vol /mnt
    
    if N1 goes down we still be able to access the same mount point,
    but the problem is that if we add or remove bricks to the volume
    whoes volfile server is down in our case N1, that info will not be
    passed to client, because connection between glusterfs and glusterd (of N1)
    will be disconnected due to which we cannot store files to the newly
    added bricks until N1 comes back
    
    Solution:
    If N1 goes down iterate through the nodes specified in
    backup-volfile-servers list and try to establish the connection between
    glusterfs and glsuterd, hence we don't really have to wait
    until N1 comes back to store files in newly added bricks that are
    successfully added when N1 was down
    
    Change-Id: I653c9f081a84667630608091bc243ffc3859d5cd
    BUG: 1289916
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13002
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 0facb11220aea20a6573b656785922219c9650cf
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Mar 31 06:29:29 2016 -0400

    io-stats: Fix overwriting of client profile by the bricks
    
    Issue: When the user executes the following command to generate
    the client perf profile, if the client is on the same node as
    bricks, the bricks overwrite the profile info written by clients.
    Also xattr "trusted.io-stats-dump" gets set on the mount point.
    
    setxattr -n trusted.io-stats-dump -v /tmp/iostat.log /mnt/fuse
    
    Fix: Unwind from setxattr, when xattr is 'io-stats-dump'
    
    Change-Id: Iba0e5df2f25f4ba3b1399ac176a3f8a916ff372e
    BUG: 1322825
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13872
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9395b30964ede412ff48e744360b02920daa3a17
Author: Sakshi <sabansal@redhat.com>
Date:   Wed Apr 15 15:30:51 2015 +0530

    glusterd: coverity fix for insecure temporary file
    
    Set umask before creating temporary file
    
    Change-Id: Ia39af63b05ce68f3f3af6585b70d4129a5530269
    BUG: 789278
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/9558
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c6d1b9797dd2850cd0b8be7f17a41db525cbe93d
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Sun Apr 10 10:51:11 2016 -0400

    tests: use trap mechanism to ensure that proper cleanups happen
    
    This actually consists of several parts.
    
      * Added a generic cleanup-scheduling mechanism.  Instead of calling
        "trap ... EXIT" directly, just call "push_trapfunc ..." instead and
        your cleanup function will be called along with any others.
    
      * Converted a few tests to use push_trapfunc.
    
      * Added "push_trapfunc cleanup_lvm" to snapshot.rc to address the
        particular problem that's driving this - snapshot tests not calling
        cleanup_lvm on their own and leaving bad state for the next test.
    
    Change-Id: I548a97a26328390992fc71ee1f03c0463703f9d7
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13933
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 5cbe6baa0258074d5003e6cdfc9997adb006750f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Sun Apr 10 15:31:50 2016 -0400

    dht: extend time for "nuke" test's janitor-cleanup check
    
    The previous check worked out to 50 deletes per second.  That might have
    seemed generous, but NetBSD regression tests were failing because it
    can't hit that figure reliably.
    
    Change-Id: Ifbd8f4547caf53a8a8d11ad586aa8051f77ddc40
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13935
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit e88962f8c49ea1d65fa26703e5c11be3f21af2ba
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 21 23:26:43 2016 +0530

    cluster/afr: Fix witness counting code in src/sink detection
    
    Problem:
    In afr-v1 pre-op, xattrop increments self xattr first then it increments the
    value on rest. In post-op, xattr value is decreased first on rest and at last
    it gets decremented on self. So for a possible operation to be witnessed i.e.
    a fop is seen by the brick it is important to have at least 1 pending op
    because without completing pre-op fop won't come. The other possibility is when
    fop completes but at the time of post-op after decrementing pending counts on
    others just before decrementing its own pending count, the brick dies.
    
    Fix:
    Fix witness detection code in afr_self_heal_find_direction()
    
    BUG: 1322253
    Change-Id: Ia7e76482c0a46e775e269bb96ec1b9490a3ac18f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13811
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit c272c71391cea9db817f4e7e38cfc25a7cff8bd5
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 29 18:36:08 2016 +0530

    features/shard: Make o-direct writes work with sharding
    
    With files opened with o-direct, the expectation is that
    the IO performed on the fds is byte aligned wrt the sector size
    of the underlying device. With files getting sharded, a single
    write from the application could be broken into more than one write
    falling on different shards which _might_ cause the original byte alignment
    property to be lost. To get around this, shard translator will send fsync
    on odirect writes to emulate o-direct-like behavior in the backend.
    
    Change-Id: Ie8a6c004df215df78deff5cf4bcc698b4e17a7ae
    BUG: 1322214
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13846
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit d129d4eea33aae5db24dba17adcb04e9d4829817
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Apr 11 16:07:40 2016 +0530

    glusterd: populate brickinfo->real_path conditionally
    
    glusterd_brickinfo_new_from_brick () is called from multiple places and one of
    them is glusterd_brick_rpc_notify where its very well possible that an
    underlying brick's file system has crashed and a disconnect event has been
    received. In this case glusterd tries to build the brickinfo from the brickid in
    the RPC request, however the same fails as glusterd_brickinfo_new_from_brick ()
    fails from realpath.
    
    Fix is to skip populating real_path if its a disconnect event.
    
    Change-Id: I9d9149c64a9cf2247abb731f219c1b1eef037960
    BUG: 1325841
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13965
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 65575da24088ba4602b94db649be12376b87484f
Author: vmallika <vmallika@redhat.com>
Date:   Mon Apr 11 15:44:16 2016 +0530

    posix_acl: create inode ctx for posix_acl_get
    
    Change-Id: Ibe5b00cd4b5d896133adc61f65094d783c492ed4
    BUG: 1325822
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13961
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e1004679563ef17c460f83098983baf105655712
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Apr 5 15:16:52 2016 +0530

    arbiter: write performance improvement
    
    Problem: The throughput for a 'dd' workload was much less for arbiter
    configuration when compared to normal replica-3 volume. There were 2
    issues:
    
    i)arbiter_writev was using the request dict as response dict while
    unwinding, leading to incorect GLUSTERFS_WRITE_IS_APPEND and
    GLUSTERFS_OPEN_FD_COUNT values (=4), leading to immediate post-ops
    because is_afr_delayed_changelog_post_op_needed() failed due to
    afr_are_multiple_fds_opened() check.
    
    ii) The arbiter code in afr was setting local->transaction.{start and len} =0
    to take full file locks. What this meant was even for simultaenous but
    non-overlapping writevs, afr_transaction_eager_lock_init() was not
    happening because afr_locals_overlap() always stays true. Consequently
    is_afr_delayed_changelog_post_op_needed() failed due to
    local->delayed_post_op not being set.
    
    Fix:
    i) Send appropriate response dict values in arbiter_writev.
    ii) Modify flock params instead of local->transaction.{start and len} to
    take full file locks in the transaction.
    
    Also changed _fill_writev_xdata() in posix to fill rsp_xdata for
    whatever key is requested for.
    
    Change-Id: I1c5fc5e98aba49ade540bb441a022e65b753432a
    BUG: 1324004
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reported-by: Robert Rauch <robert.rauch@gns-systems.de>
    Reported-by: Russel Purinton <russell.purinton@gmail.com>
    Reviewed-on: http://review.gluster.org/13906
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 09c9da3b12da73dd718522fdf7587d3be5a14137
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Apr 8 21:59:53 2016 -0400

    extras: Add namespace for options in group-virt.example
    
    Commit 23ccabbeb7 introduced a new key "disperse.eager-lock" which
    causes a conflict with key "cluster.eager-lock" when option is used
    without the qualifying namespace. group-virt.example which gets
    installed as /var/lib/glusterd/ groups/virt contains options without
    namespace qualifiers. This patch adds the appropriate namespace to all
    options in group-virt.example.
    
    Change-Id: I2c09dd10d44138410d889ddeb805f01c641c6780
    BUG: 1314649
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/13929
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 5ff451beecaf564b4f854b10e63a307e40660c8c
Author: Anuradha Talur <atalur@redhat.com>
Date:   Fri Feb 5 10:45:37 2016 +0530

    libglusterfs: Refactor packing of arguments
    
    Added these changes so that they can be re-used to pack
    arguments required for each fop while populating the
    compound fop structure used by each xlator.
    
    Change-Id: Id9923e10003adafbc16a8bf3fbefa30677847313
    BUG: 1303829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13360
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit be99ddd842025e0cd1a84076ee199cd4554a4575
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Apr 7 21:14:49 2016 +0530

    socket: Don't cleanup encrypted transport in socket_connect()
    
    ..instead cleanup only in socket_poller()
    
    With commit d117466 socket_poller() wasn't launched from socket_connect
    (for encrypted connections), if connect() failed. This was done to
    prevent the socket private data from being double unreffed, from the
    cleanups in both socket_poller() and socket_connect(). This allowed
    future reconnects to happen successfully.
    
    If a socket reconnects is sort of decided by the rpc notify function
    registered. The above change worked with glusterd, as the glusterd rpc
    notify function (glusterd_peer_rpc_notify()) continuously allowed
    reconnects on failure.
    
    mgmt_rpc_notify(), the rpc notify function in glusterfsd, behaves
    differently.
    
    For a DISCONNECT event, if more volfile servers are available or if more
    addresses are available in the dns cache, it allows reconnects. If not
    it terminates the program.
    
    For a CONNECT event, it attempts to do a volfile fetch rpc request. If
    sending this rpc fails, it immediately terminates the program.
    
    One side effect of commit d117466, was that the encrypted socket was
    registered with epoll, unintentionally, on a connect failure.  A weird
    thing happens because of this. The epoll notifier notifies
    mgmt_rpc_notify() of a CONNECT event, instead of a DISCONNECT as
    expected. This causes mgmt_rpc_notify() to attempt an unsuccessful
    volfile fetch rpc request, and terminate.
    (I still don't know why the epoll raises the CONNECT event)
    
    Commit 46bd29e fixed some issues with IPv6 in GlusterFS. This caused
    address resolution in GlusterFS to also request of IPv6 addresses
    (AF_UNSPEC) instead of just IPv4. On most systems, this causes the IPv6
    addresses to be returned first.
    
    GlusterD listens on 0.0.0.0:24007 by default. While this attaches to all
    interfaces, it only listens on IPv4 addresses. GlusterFS daemons and
    bricks are given 'localhost' as the volfile server. This resolves to
    '::1' as the first address.
    
    When using management encryption, the above reasons cause the daemon
    processes to fail to fetch volfiles and terminate.
    
    Solution
    --------
    The solution to this is simple. Instead of cleaning up the encrypted
    socket in socket_connect(), launch socket_poller() and let it cleanup
    the socket instead. This prevents the unintentional registration with
    epoll, and socket_poller() sends the correct events to the rpc notify
    functions, which allows proper reconnects to happen.
    
    Change-Id: Idb0c0a828743cccca51cfdd1aa6458cfa0a9d100
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/13926
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 44fe595664b6c2da6cc6a1a9d1aa195f92c8b601
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 31 21:15:14 2016 +0530

    tests: Fix typo in split-brain-healing.t
    
    Change-Id: Ie4554a13fd60d2b14518cc54e8c464f898970030
    BUG: 1321322
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13875
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 0fa83a3310274845fa9b445d1aed124e9fb43410
Author: M S Vishwanath Bhat <msvbhat@gmail.com>
Date:   Wed Mar 30 17:05:05 2016 +0530

    Adding distaf tests directory structure to tests dir
    
    Since it was decided to have distaf test cases and related
    libraries inside of glusterfs.git, this patch has the basic
    skeleton directory structure and few of the libs.
    
    Please note that, this patch by itself will not enable to
    run any distaf tests right away. The distaf package needs to
    be installed from the github.com/gluster/distaf. Once that
    package is installed, it will put all the libs into respective
    standard location and only then the tests in this patch can be
    executed.
    
    The plan to have distaf_libs packaged or installable using setup.py
    This will enable tests to assume that all the libs are present in
    the standard location.
    
    Change-Id: I925ac0ad7e9cf6164c4380319a1f786b5241c74a
    Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Reviewed-on: http://review.gluster.org/13853
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 6602376e3e9e6d9f4f695475569322b61ccc2411
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 31 17:15:37 2016 -0400

    dht: add "nuke" functionality for efficient server-side deletion
    
    This turns a special xattr into an rmdir with flags set.  When that hits
    the posix translator on the server side, that causes the file/directory
    to be moved into the special "landfill" directory.  From there, the
    posix janitor thread will take care of deleting it entirely on the
    server side - traversing it recursively if necessary.  A couple of
    secondary issues were fixed to make this effective.
    
     * FUSE now ensures that setxattr values are NUL terminated.
    
     * The janitor thread now gets woken up immediately when something is
       placed in 'landfill' instead of only when file descriptors need to be
       closed.
    
     * The default landfill-emptying interval was reduced to 10s.
    
    To use the feature, issue a setxattr something like this:
    
       setfattr -n glusterfs.dht.nuke -v "" /mnt/glusterfs/vol/some_dir
    
    The value doesn't actually matter; the mere receipt of a request with
    this key is sufficient.  Some day it might be useful to allow setting a
    required value as a sort of password, so that only those who know it can
    access the underlying special functionality.
    
    Change-Id: I8a343c2cdb40a76d5a06c707191fb67babb8514f
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13878
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e6c7da3769105f0e6fc8b6627f3b11727a2a216d
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Apr 6 15:47:46 2016 -0400

    tests: fix per-test core detection
    
    Commit 9933c5ab in glusterfs-patch-acceptance-tests broke the code here
    to count cores after each test, with two bad effects:
    
     * Tests continue to run after the job is already guaranteed to fail,
       tying up resources and delaying jobs for other patches.
    
     * Cores aren't detected until the end of the job, long after it might
       have been possible to figure out what was going on at the time the
       process died.
    
    The current check here works for the current code in the other repo, but
    could break if the two repos are changed without coordination again.
    
    Change-Id: Ica9222c3474fddf8e3b40074da2bdfd4dabb79d7
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13921
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 50b93f72f9a3f5bfd1d610801aecb06823adaa63
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Thu Mar 31 15:02:03 2016 +0530

    NFS: new option nfs.rdirplus added
    
    When this option is 'disabled', NFS falls back to standard readdir instead
    of readdirp
    
    Change-Id: Icaaf4da6533bee56160d4a81e42bb60f7d341945
    BUG: 1302948
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13782
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit ecdcd519b9d7b50215072f47e00ce326d1242934
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Apr 4 17:29:38 2016 -0400

    cli: fix double free of options dictionary
    
    In cli_cmd_volume_getopt_cbk and cli_cmd_volume_barrier_cbk, we were
    freeing our options directory, which was incorrect because we had
    already put it in our local structure (via CLI_LOCAL_INIT) and it was
    being freed from there (via CLI_STACK_DESTROY and cli_local_wipe).  This
    was causing mount.t to hang consistently in a vagrant environment, with
    the CLI stuck trying to take a lock on a dictionary that had already
    been freed.  While this made it possible to debug, the same problem
    might be behind some other intermittent regression test failures as
    well.
    
    Change-Id: I70aa7c69f63243f5423d68e2cfaefca81b937aad
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13903
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 7370633b6404bbd3c8238b464bc413689dcccf93
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon Apr 4 16:15:18 2016 +0530

    rpc: assign port only if it is unreserved
    
    Current order:
        assign port;
        check for port;
        if reserved {
            port--;
            continue to i;
        }
        bind();
    
    basically, we are assigning port first then checking if it is reserved
    
    Fix:
        get unreserved port;
        assign port;
        bind();
    
    from now, we get unreserved port first and then assign it
    
    Change-Id: I004580c5215e7c9cae3594af6405b20fcd9fa4ad
    BUG: 1323659
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13900
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6e3b4eae1ae559d16721f765294ab30a270820d0
Author: Sakshi <sabansal@redhat.com>
Date:   Wed Aug 5 16:05:22 2015 +0530

    dht: lock on subvols to prevent rename and lookup selfheal race
    
    This patch addresses two races while renaming directories:
    1) While renaming src to dst, if a lookup selfheal is triggered
    it can recreate src on those subvols where rename was successful.
    This leads to multiple directories (src and dst) having same gfid.
    To avoid this we must take locks on all subvols with src.
    
    2) While renaming if the dst exists and a lookup selfheal is
    triggered it will find anomalies in the dst layout and try to
    heal the stale layout. To avoid this we must take lock on any
    one subvol with dst.
    
    Change-Id: I637f637d3241d9065cd5be59a671c7e7ca3eed53
    BUG: 1252244
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/11880
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 21d8a461ae712539f5a0bf7e6889df29750c5256
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Apr 4 17:23:53 2016 -0400

    tests: improve vagrant usability
    
    The first and most important change is to deal with the fact that
    "localhost" is an IPv6 address in the vagrant box we're using.  This was
    non-obviously behind some of the NFS tests failing to run properly, so
    there's now an Ansible role etc. to make the necessary modifications in
    /etc/hosts.  Also added "-j" to the make command, and changed the
    invocation of "run-tests.sh" so it passes through any arguments instead
    of running all tests every time.
    
    BUG: 1291537
    Change-Id: I5e6125de043c41fdb2866875e999cb1fcd72ba52
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13904
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 34d1c81dc4c730eb0cd2b8fd756b8bffed655e9c
Author: vmallika <vmallika@redhat.com>
Date:   Sat Apr 2 08:57:00 2016 +0530

    marker: optimize mq_update_dirty_inode_task
    
    In function mq_update_dirty_inode_task we do readdirp
    on a dirty directory and for entry we again do
    lookup to fecth the contribution xattr.
    We can fetch this contribution as part of readdirp
    
    Change-Id: I766593c0dba793f1ab3b43625acce1c7d9af8d7f
    BUG: 1320818
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13892
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit cd22b5c1a490444620c1d19ce22672ff1cd478a6
Author: vmallika <vmallika@redhat.com>
Date:   Wed Apr 6 14:09:50 2016 +0530

    marker: do mq_reduce_parent_size_txn in FG for unlink & rmdir
    
    * If a "rm -rf" is performed by a client, we initiate a
      marker background operation mq_reduce_parent_size_txn
      for rmdir and unlink.
    
      mq_reduce_parent_size_txn can fail when updating
      size on the ancestor directories, if these directories
      are removed during the txn as the child-parent association
      removed in the dentry list.
    
      So execute mq_reduce_parent_size_txn in foreground
      and then do the UNWIND for rmdir and unlink FOP
    
    Change-Id: Iefcdced4c6ae0dbd43f92814d0ddcd1e33825864
    BUG: 1322489
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13874
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 1546572b7d46c1aee906608140c843160a529937
Author: vmallika <vmallika@redhat.com>
Date:   Sat Apr 2 12:02:22 2016 +0530

    posix_acl: skip acl_permits for special clients
    
    Change-Id: I3f478b7e4ecab517200f50eb09f65a634c029437
    BUG: 1320818
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13894
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 7927149f71adc49cad92f28f805a8e688534156e
Author: vmallika <vmallika@redhat.com>
Date:   Sun Apr 3 20:35:52 2016 +0530

    quota: check inode limits only when new file/dir is created
    
    When a inode limit is full, writes to any existing file
    fails with disk quota exceed even if usage limit is
    not set or usage limit is not full.
    
    BUG: 1323486
    Change-Id: I9679fe26a2839ade0b1541fa7f0a2b71ac6dcc31
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13911
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit 81955d8aaee8a2c7bf6370970926bc7b403a6efa
Author: vmallika <vmallika@redhat.com>
Date:   Wed Mar 30 20:16:32 2016 +0530

    marker: build_ancestry in marker
    
    * quota-enforcer doesn't execute build_ancestry in the below
      code path
        1) Special client (PID < 0)
        2) unlink
        3) rename within the same directory
        4) link within the same directory
    
        In these cases, marker accounting can fail as parent not found.
        We need to build_ancestry in marker if it doesn't find parent
        during update txn
    
    Change-Id: Idb7a2906500647baa6d183ba859b15e34769029c
    BUG: 1320818
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13857
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit c25f88c953215b1bfc135aeafc43dc00a663206d
Author: Sakshi <sabansal@redhat.com>
Date:   Thu Jul 16 14:31:03 2015 +0530

    dht: lock on subvols to prevent lookup vs rmdir race
    
    There is a possibility that while an rmdir is completed on
    some non-hashed subvol and proceeding to others, a lookup
    selfheal can recreate the same directory on those subvols
    for which the rmdir had succeeded. Now the deletion of the
    parent directory will fail with an ENOTEMPTY.
    
    To fix this take blocking inodelk on the subvols before
    starting rmdir. Selfheal must also take blocking inodelk
    before creating the entry.
    
    Change-Id: I168a195c35ac1230ba7124d3b0ca157755b3df96
    BUG: 1245065
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13528
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 648357ffad482a1bda8915d42df9d5b055dae44f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Apr 1 23:10:51 2016 +0530

    glusterd: fill real_path variable in brickinfo during volume import
    
    Variable "real_path" in brick info was used to store absolute path
    and using this we check the availability of the newly added bricks.
    
    But we were not populating the variable when we import a volume
    from peers. That caused to reset the real_path variable to zero,
    which resulted in validation failure for all new brick creation.
    
    Change-Id: I62be7bf452f0dcdf6aec3a4ec33c2e1fba2951ca
    BUG: 1323287
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13890
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit b198cdd6a47a964a102e8e96dc0de34cd19c2fd5
Author: vmallika <vmallika@redhat.com>
Date:   Sat Apr 2 09:20:45 2016 +0530

    quota/cli: display quota usage on path when limit not set
    
    When a quota limit is not set, 'quota list <path>' should still display
    the usage when a path parameter is specified.
    
    Change-Id: Ida12d9c5e348fbd98db4d68d9324c623cbdd3dea
    BUG: 1323360
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13893
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit d3c77459593255ed2c88094c8477b8a0c9ff9073
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Mar 31 14:58:02 2016 +0530

    glusterd: build realpath post recreate of brick mount for snapshot
    
    Commit a60c39d introduced a new field called real_path in brickinfo to hold the
    realpath() conversion. However at restore path for all snapshots and snapshot
    restored volumes the brickpath gets recreated post restoration of bricks  which
    means the realpath () call will fail here for all the snapshots and cloned
    volumes.
    
    Fix is to store the realpath for snapshots and clones post recreating the brick
    mounts. For normal volume it would be done during retrieving the brick details
    from the store.
    
    Change-Id: Ia34853acddb28bcb7f0f70ca85fabcf73276ef13
    BUG: 1322772
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13869
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit d65419677cf784599d4352d94f626823f895a18b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 17 09:32:17 2016 +0530

    cluster/afr: Use parallel dir scan functionality
    
    BUG: 1221737
    Change-Id: I0ed71a72f0e33bd733723e00a01cf28378c5534e
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13755
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c76a1690bbd909b1c2dd2c495e2a8352d599b14b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 17 09:32:02 2016 +0530

    syncop: Add parallel dir scan functionality
    
    Most of this functionality's ideas are contributed
    by Richard Wareing, in his patch:
    https://bugzilla.redhat.com/show_bug.cgi?id=1221737#c1
    
    VERY BIG thanks to him :-).
    
    After starting porting/testing the patch above, I found a few things we can
    improve in this patch based on the results we got in testing.
    1) We are reading all the indices before we launch self-heals. In some customer
    cases I worked on there were almost 5million files/directories that needed
    heal. With such a big number self-heal daemon will be OOM killed if we go
    this route. So I modified this to launch heals based on a queue length
    limit.
    
    2) We found that for directory hierarchies, multi-threaded self-heal
    patch was not giving better results compared to single-threaded
    self-heal because of the order problems. We improved index xlator to
    give gfid type to make sure that all directories in the indices are
    healed before the files that follow in that iteration of readdir
    output(http://review.gluster.org/13553). In our testing this lead to
    zero errors of self-heals as we were only doing self-heals in parallel
    for files and not directories. I think we can further improve self-heal
    speed for directories by doing name heals in parallel based on similar
    techniques Richard's patch showed. I think the best thing there would be to
    introduce synccond_t infra (pthread_cond_t kind of infra for syncops)
    which I am planning to implement for future releases.
    
    3) Based on 1), 2) and the fact that afr already does retries of the
    indices in a loop I removed retries again in the threads.
    
    4) After the refactor, the changes required to bring in multi-threaded
    self-heal for ec would just be ~10 lines, most of it will be about
    options initialization.
    
    Our tests found that we are able to easily saturate network :-).
    
    High level description of the final feature:
    Traditionally self-heal daemon reads the indices (gfids) that need to be healed
    from the brick and initiates heal one gfid at a time. Goal of this feature is
    to add parallelization to the way we do self-heals in a way we do not regress
    in any case but increase parallelization wherever we can. As part of this following
    knobs are introduced to improve parallelization:
    1) We can launch 'max-jobs' number of heals in parallel.
    2) We can keep reading indices as long as the wait-q for heals doesn't go over
       'max-qlen' passed as arguments to multi-threaded dir_scan.
    
    As a first cut, we always do healing of directories in serial order one at a time
    but for files we launch heals in parallel. In future we can do name-heals of dir
    in parallel, but this is not implemented as of now. Reason for this is mentioned
    already in '2)' above.
    
    AFR/EC can introduce options like max-shd-threads/wait-qlength which can be set
    by users to increase the rate of heals when they want. Please note that the
    options will take effect only for the next crawl.
    
    BUG: 1221737
    Change-Id: I8fc0afc334def87797f6d41e309cefc722a317d2
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13569
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 3394c555171775c6f74c2c556265b044a70a2fa9
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Sat Aug 15 01:29:31 2015 +0530

    glusterd: clean dead initializations
    
    This patch cleans unused variable initialization as well as their declarations
    which are no where used in the code
    
    Change-Id: I784165fc6e91297758079699dd9583d5203b7793
    BUG: 1253831
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11929
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6c76c96ee48f6ad1148e64dbe02f02c7aff4b9ce
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Apr 1 15:33:22 2016 -0400

    fdl: fix "used before set" warnings in librecon
    
    Newer compilers were complaining about this in generated code, because
    cleanup code fragments were being added in the wrong order.
    
    Change-Id: I90ff6eccfa78dc012da6d8fd83443490a3cb276d
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13891
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 83dbdf907d0defec7282d6ec3c2eb8958fea7895
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Mar 30 15:04:39 2016 +0530

    fdl: fix make clean
    
    add fdl/src/librecon.c to CLEANFILES
    
    Change-Id: I91332ddda5b4157483389c32b74d90a6a4e1322a
    BUG: 1322323
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13850
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit aa614a39c4281781cd77052c01f5747f1e5ad05e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Apr 1 11:50:26 2016 +0530

    cli: Make CLI timeout configurable
    
    When number of volumes go high in numbers command like gluster volume status may
    timeout from CLI since it follows a static timeout value of 120 secs.
    
    This patch introduces a flag '--timeout' which can pass a specific time out
    value for a particular command.
    
    Change-Id: I9795b709f27357fe5ee10ba19de8f4c11b63186f
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13882
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 34899d71f21fd2b4c523b68ffb2d7c655c776641
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Mar 31 11:01:53 2016 +0530

    glusterd: Allocate fresh port on brick (re)start
    
    There is no point of using the same port through the entire volume life cycle
    for a particular bricks process since there is no guarantee that the same port
    would be free and no other application wouldn't consume it in between the
    glusterd/volume restart.
    
    We hit a race where on glusterd restart the daemon services start followed by
    brick processes and the time brick process tries to bind with the port which was
    allocated by glusterd before a restart is been already consumed by some other
    client like NFS/SHD/...
    
    Note : This is a short term solution as here we reduce the race window but don't
    eliminate it completely. As a long term solution the port allocation has to be
    done by glusterfsd and the same should be communicated back to glusterd for book
    keeping
    
    Change-Id: Ibbd1e7ca87e51a7cd9cf216b1fe58ef7783aef24
    BUG: 1322805
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13865
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d7001f3606866c1d9bb3cefd2767af56833dd53f
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 31 07:15:42 2016 -0400

    packaging: gluster-ganesha requires pacemaker, etc., on RHEL6
    
    HA packages in RHEL6 are missing dependencies. (RHEL7 versions do.)
    
    Change-Id: I4e80b569ea89f97e8a110aee2f4554175aa0ec8b
    BUG: 1322801
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13870
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 2aee1d44f4125eaf33f9090b55b91b7d0965095d
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 31 17:15:14 2016 -0400

    locks: fix build breakage from missing pl-messages.h
    
    Change-Id: I0f8af57dd96226b1e7a8a39237a82ce1cdd48be6
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13876
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 279c8e42ffe61d2906009a305aec3e218c058d0e
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Fri Apr 1 14:54:48 2016 +0530

    tests: add open-behind.t to bad tests
    
    open-behind.t fails on NetBSD very frequently
    will be disabled until the problem is fixed
    
    Change-Id: I0655e4b0c8b3ad7fc9e2ccfcf679673832ff12a5
    BUG: 1300253
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13884
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 8dfbb6751b2f421fb179ecf6abf803fbe983350e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Mar 30 17:42:44 2016 +0530

    glusterd/syncop: double free of frame stack
    
    If rpc message from glusterd during brick op phase
    fails without sending, then frame was freed from
    the caller function and call back function.
    
    Change-Id: I63cb3be30074e9a074f6895faa25b3d091f5b6a5
    BUG: 1322262
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13854
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b4cbfdac0d35e6896f337b4ae7b75dcf4e714a1a
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 12 14:57:47 2016 +0530

    nsr: Introducing a happy path test case
    
    Write infra for nsr_server to not send a
    CHILD_UP before it gets a CHILD_UP from a
    quorum of it's children. Using the CHILD_UP
    received in the nsr client translator from
    the server, to decide the right time for
    starting the I/Os
    
    Change-Id: I9551638b306bdcbc6bae6aeda00316576ea832fe
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13623
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b2a5eed9b17a82ec4b6366b0107fe2271328c16a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 28 16:31:12 2016 +0530

    cluster/afr: Don't lookup/forget inodes
    
    Problem:
    All inodes that are looked-up are always forgotten without fail in
    afr removing the benefits of them being in lru. This same code can
    cause crashes if between inode_lookup, inode_forget in afr if the
    top xlator does inode_forget(0).
    
    Fix:
    Don't use lookup/forget in afr. No benefits are there at the moment
    for keeping this code. It is impossible to prevent top xlators to
    do inode_forget(0). Found similar instances in ec
    and removed them even though those code paths are not going to
    be executed in any place other than heal-daemon.
    
    BUG: 1321554
    Change-Id: Ia4cb236178f7f129cc898d53f0bbd26f494a2a8d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13834
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>

commit 16a3f0d020d23978b22a07354c25c654c88163a2
Author: Milind Changire <mchangir@redhat.com>
Date:   Sat Nov 28 14:56:02 2015 +0530

    tools/glusterfind: add --full option to query command
    
    The --full option will use brickfind.py to list all files in the volume.
    The output file will contain url-encoded file names prefixed with the
    tag string to indicate that all files should be considered as new.
    The default tag string for the --full option is "NEW". This can be
    changed with the --tag-for-full-find command-line option.
    
    Change-Id: Ic85ba5db062e19df13ae9dc2de8a08eacb5c9792
    BUG: 1286279
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/12779
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 9746ee75865162af1827337f22a553ea0c3ba2ed
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Mar 29 19:06:46 2016 +0530

    features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path'
    
    If 'changelog' is enabled and 'changelog.capture-del-path' option is on
    it calls 'resolve_pargfid_to_path' which modifies 'pargfid' sent by
    caller.  'changelog_unlink' calls this routine directly with
    'loc->pargfid' resulting it being modified and point to root instead of
    actual pargfid. This is a nasty bug and could cause the deletion of
    entry on root directory instead on actual parent when 'loc->path' is
    not present.  Hence this fix to make 'pargfid' a const pointer and
    'resolve_pargfid' to work on copy of pargfid.
    
    Glusterfind session creation enables these options by default to
    capture deleted entry path in changelog.
    
    Thanks Pranith for root causing this.
    
    Change-Id: I1d275a86f91c981b6889bedef93401c039d01d71
    BUG: 1321955
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13845
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit d5b583be1e677637015fabeaac81994f382f14bc
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Mar 29 13:46:07 2016 +0530

    glusterd: scan for open ports only in required range
    
    It does not make sense to keep track of free ports from 0 to base_port
    if we are not going to use them.
    
    glusterd start times without this patch
    2.622
    2.478
    2.455
    2.590
    2.400
    
    glusterd start times with this patch
    1.9
    1.9
    1.9
    2.0
    2.0
    1.8
    
    We save around half a second for every glusterd start.
    
    BUG: 1322237
    Change-Id: I0456689d0afad50dd068f2325ebfca9bdeffe01a
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13841
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit dd02c5af9acb77cddc3bbe1ce9a51b7428b24446
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Mar 29 11:26:39 2016 +0530

    extras: allign glusterd stop response in init script
    
    An echo is missing stop() function which results in bad allignment of glusterd
    stop output
    
    Change-Id: I63ac9571457db90574fb1bfbf4f18ba09d3df1af
    BUG: 1321762
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13839
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 171e365449a1461421c62108bf8e569950d7b3bf
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Mar 30 15:16:35 2016 +0530

    build: git ignore files generated by fdl xlator
    
    Change-Id: I7693624646cfab254c93afc0361b483a72c99841
    BUG: 1322320
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13851
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 773e660de0c45221b53cf2a489f28209145475db
Author: vmallika <vmallika@redhat.com>
Date:   Tue Mar 29 18:34:11 2016 +0530

    server: send lookup on root inode when itable is created
    
     * xlators like quota, marker, posix_acl can cause problems
       if inode-ctx are not created.
       sometime these xlarors may not get lookup on root inode
       with below cases
       1) client may not send lookup on root inode (like NSR leader)
       2) if the xlators on one of the bricks are not up,
          and client sending lookup during this time: brick
          can miss the lookup
       It is always better to make sure that there is one lookup
       on root. So send a first lookup when the inode table is created
    
     * When sending lookup on root, new inode is created, we need to
       use itable->root instead
    
    Change-Id: Iff2eeaa1a89795328833a7761789ef588f11218f
    BUG: 1320818
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13837
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 48a0a38fadf9c5164869a908dcff8a951aa21b4b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Mar 21 16:57:48 2016 +0530

    tools/glusterfind: Handling Unicode file names
    
    Unicode filenames handled cleanly with this patch. Changelog
    files and output files are opened with utf-8 encoding using codecs.open.
    
    urllib.quote_plus and unquote_plus will not handle Unicode so, encode
    Unicode to 8-bit string version before calling unquote. urllib.quote_plus
    requires 8-bit string itself so do not decode to Unicode if we need to use
    quote_plus(when --no-encode=false). Decode to unicode in --no-encode is set.
    
    BUG: 1319717
    Change-Id: If5561c749ab5529445650d322c831eb4da22b65a
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13798
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 7bbcd6fb692dffc628b723eace8cfcfa466e606f
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Feb 17 15:57:02 2016 +0530

    cluster/ec: Rebalance hangs during rename
    
    Problem:
    During the rename of a particular file (ec
    is holding blocking inodelk on the parent
    directory), if the rename of another file
    under the same directory comes. EC does not
    release the lock and goes ahead and renames
    the "new" file with the "already held lock".
    
    That causes rebalance process to be blocked
    on a lock which has been acquired by rename.
    
    Solution:
    While rename fop comes, ec takes blocking inodelk
    on old and new parent of the file. Before releasing,
    every lock held by ec, it waits for some "time" to
    see if that lock can be reused by the next fop.
    If within this "time" some other request comes,
    it releases this lock based on condition
    "lock count > 1"
    
    To get this "lock count" for rename fop, we have
    implemented "pl_rename" in feature/lock. Also,
    on ec side, changed the condition to release the lock
    based on the type of fop and old and new parent
    directories.
    
    Change-Id: I979dbab1185df962e8f305a6074ae1186ffe7db0
    Bug: 1304988
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13460
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 207289621f6c5b75bdb80aa14ddaf72efd5eb9b1
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Mar 28 10:49:43 2016 +0530

    libglusterfs: open cmd_history log file with O_APPEND and O_WRONLY
    
    Commit 8fdfa0c introduced a fix to ensure cmd_history file is log rotated
    properly. However with this fix fdopen() is called with mode "a" on a fd which
    was not opened with O_WRONLY & O_APPEND resulting into a fdopen() failure.
    
    Fix is to open cmd_history.log file with O_CREATE|O_WRONLY|O_APPEND mode
    
    Change-Id: I75ef350560aa6d5435c78c5fd83adfde1a73bfc3
    BUG: 1286959
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13829
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 08d18ef9257067fac510af408665360019566000
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Mar 25 18:48:30 2016 +0530

    afr: add mtime based split-brain resolution to CLI
    
    Extended the CLI to include support for split-brain resolution based on
    mtime. The command syntax is:
    
    $:gluster volume heal <VOLNAME> split-brain latest-mtime <FILE>
    
    where <FILE> can be either the full file name as seen from the root of the
    volume (or) the gfid-string representation of the file.
    
    Change-Id: I7a16f72ff1a4495aa69f43f22758a9404e958b4f
    BUG: 1321322
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13828
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit a28484443f27332c1a87e00e474ca56427a83669
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Mon Mar 28 16:39:24 2016 +0530

    build : fixing dependency issue for glusterfs-ganesha in epel6
    
    glusterfs-ganesha requires "dbus-send" binary, but location of this
    binary is different in epel6 and epel7. For epel6 it is /bin/ and
    epel7 it is /usr/bin/. So the patch will add dependency based on
    package dbus not on the binary dbus-send
    
    Change-Id: I266af7b983791be648749f01a04b38479d6f7c03
    BUG: 1321872
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13842
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 916eb46d434097a8e7905ac3be0f0d9a0b4b3da2
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Fri Mar 4 08:55:09 2016 +0530

    tier/libgfdb: Ordering query results from libgfdb
    
    When querying we will order the query result to get
    the hotest or the coldest files in the queried list
    so that these files are migrated first.
    
    Now here we are giving priority to the write heat(time and counters),
    as it requires complex queries to have a composite
    ordering of write and read + it has it impact on performance.
    
    Change-Id: I2e0415dcfad4218b42c68fc5c2ed8d1f075ce9ea
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/13607
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Joseph Fernandes
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 516db811a3bc1b3e778c383fc18aa5eb56342f77
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Mar 24 20:43:05 2016 +0530

    debug/trace: Print {acm}times as integers
    
    This helps in debugging issues with mtime, ctime etc.
    
    Change-Id: I4a0335f17c6b40e6c627658e91f43989c3efca22
    BUG: 1302948
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13826
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit d0cb21b5e3dd90a851e43bcfac9b1b2edf3db9c2
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 22 16:32:32 2016 +0530

    glusterd: Add a new event to handle multi-net probes
    
    This allows GlusterD to send updates to all other nodes when attaching
    new addresses using multi-net peer probe.
    
    Change-Id: I62846be750ab3721912e7b49656594347ea61723
    BUG: 1320458
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/13817
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit b67e569b3906d99677a1349cb82668f9088cf4eb
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Feb 23 12:51:45 2016 +0530

    tier/dht : Attach tier fix layout to run in background
    
    1. Spawn a thread for background fix-layout for tier process.
    
    2. Once the fix-layout is completed a marker xttr is set on the root of
       volume to mark the completion of the background fixlayout, so that
       even if the tier process is spawned again, fixlayout will not be
       issued, if it was completed last time.
    
    3. Please note that promotion of legacy files will happen eventually as
       the ctr lookup heal in the fixlayout slowly heals the ctr db for legacy
       files OR the ctr lookup heal happend due to a name lookup.
    
    4. When a detach tier is successful in evacuation data from hot tier, we remove
       the marker xattr is removed. So that next attach tier runs the background
       tier fixlayout.
    
    what is remaining ?
    1. Instead of clearing the marker xattr of tiering fix layout at the end of detach start
       clear it during detach commit. But the issue is detach commit is a glusterd operation
       and the volume is not mounted in glusterd.
       The reason we want to do it in detach commit is that if the admin wants to attach the
       same tier again, then a background fixlayout will be triggered, which would not be needed.
    2. Clearing the CTR DB of the cold bricks when there is a detach commit, as it will be having
       entries which will be stale when the volume is used, with ctr off (ctr is switched off only when
       we have detach commit.)
    
    Change-Id: Ibe343572e95865325cd0eef4d0b976b626a3c0c5
    BUG: 1313228
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/13491
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Joseph Fernandes
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 2d0c2a9e15a581950a966841866f1f18a8888440
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 25 06:04:23 2016 +0530

    cluster/afr: Fix read-child selection in entry create fop
    
    When an entry is being created the inode is yet to be linked
    so args must be filled with gfid and ia_type for it to give
    consistent iatt.
    
    Also handle Dht sending fops on inode not yet linked.
    
    BUG: 1302948
    Change-Id: I6969cacb437cad02f66716f3bf8ec004ffe7c691
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13827
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 06d50c1c00fe35c6bc2192a392b8a749984f3efc
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Mar 14 15:10:17 2016 -0400

    storage/posix: send proper iatt attributes for the root inode
    
    * changes in posix to send proper iatt attributes for the root directory
      when ancestry is built. Before posix was filling only the gfid and the
      inode type in the iatt structure keeping rest of the fields zeros. This
      was cached by posix-acl and used to send EACCES when some fops came on
      that object if the uid of the caller is same as the uid of the object on
      the disk.
    
    * getting and setting inode_ctx in function 'posix_acl_ctx_get' is not atomic
      and can lead to memory leak when there are multiple looups for an
      inode at same time. This patch fix this problem
    
    * Linking an inode in posix_build_ancestry, can cause a race in
      posix_acl.
      When parent inode is linked in posix_build_ancestry, and before
      it reaches posix_acl_readdirp_cbkc, reate/lookup can
      come on a leaf-inode, as parent-inode-ctx not yet updated
      in posix_acl_readdirp_cbk, create/lookup can fail
      with EACCESS. So do the inode linking in the quota xlator
    
    Change-Id: I3101eefb65551cc4162c4ff2963be1b73deacd6d
    BUG: 1320818
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/13730
    Tested-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 351ec36e3146b7605334cb658927b447b1dbc796
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Mar 23 11:26:49 2016 +0530

    glfs/heal: Use encrypted connection in shd
    
    When management encryption is enabled, GlusterD
    only allows encrypted connections for port 24007.
    SHD is trying to fetch it's volfile using an
    unencrypted connection.
    
    If /var/lib/glusterd/secure-access is present , i.e.
    if management ssl is enabled, use encrypted connection
    fecth info from glusterd.
    
    Change-Id: Ia41dcde1a69375379409889ec5b3a70cb95a4fd0
    BUG: 1320388
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13815
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1b1fae4b8b351ee768f8fa61c3e5e5debfa2eb15
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Mar 23 15:45:08 2016 +0530

    glfs-mgmt: fix connecting to multiple volfile transports
    
    Problem:
    [
            {"host":"1.2.3.4", "port":"24007", "transport":"tcp"},
            {"host":"/var/run/glusterd.socket", "transport":"unix"}
    ]
    
    Consider the above case where we have two volfile servers, each
    has different transport type, we first try to connect to server1
    which has transport type "tcp" let's say we found that host address
    is invalid, now we pick the next available server2, in our case
    it is of type "unix" and try to connect to it.
    
    but we fail to connect to it even we have right unix path, because
    multiple volfile servers with different transport type is not taken
    care currently.
    
    Solution:
    Every time we receive a  RPC_CLNT_DISCONNECT event in mgmt_rpc_notify,
    we need to check the transport type of the volfile server in the list
    and set the keys "transport.socket.connect-path" or "remote-host"
    accordingly.
    
    Change-Id: I36bec46ef2e92e4642a7d7d64b423d0bc3ab269b
    BUG: 1320489
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13819
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Prasanna Kumar Kalever <pkalever@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit aebd8d69d9c918a55f0619303de6880a4214dc94
Author: Shyam <srangana@redhat.com>
Date:   Mon Feb 8 14:44:32 2016 +0530

    dht2: Creation of experimental shell for dht2
    
    Change-Id: I1aa3ea25f99d36fa2356edaa4c3132386adef303
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/13397
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 91004b046805243e730176a5354ce3092326dde4
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Mar 22 15:51:37 2016 +0530

    debug/io-stats: Disable fop stats dump by default
    
    Even though someone is not interested in seeing the fops statistics in
    client logs under DEBUG level we forcefully dump the same. This is due
    to default dump-interval configured to as 5 seconds. Since can use
    diagnostics.stats-dump-interval volume set option to change the default
    dump-interval its better to disable this huge dumping by default.
    
    Change-Id: Id14a38bcd92e47d75003279567a0f80acac1d86e
    BUG: 1320101
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/13808
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 148ed4fd15b4de78e4d16b9f41836c9a2b003246
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Sat Aug 15 01:06:32 2015 +0530

    glusterd: remove unused large memory/buffer allocations
    
    This patch cleans dead buffer allocations which are never used in the
    code.
    
    Change-Id: I8c55837434fd5bf9dde9fb7b070fdefbf64cf4a3
    BUG: 1253828
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11928
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f14e800cd9bfe34822e1530f71f233bfe4fb04c0
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Sat Mar 19 10:15:24 2016 +0530

    dht: update attr information in refresh layout to avoid
         stale timestamp
    
    Consider the scenario where an mkdir has just created the
    directory but has not healed it yet. A parallel lookup on
    this entry will find anomalies and trigger a selfheal which
    will sample the ctime of the directory after the mkdir phase.
    Meanwhile the mkdir has completed setting the layout and
    updated the ctime. The selfheal then sees the layout to be
    healed and returns with the ctime it got after the mkdir phase
    which has now become stale. However if the lookup happens
    to unwind before the mkdir then the inode associated with
    lookup will get linked in the inode table which has the
    stale ctime. To avoid this selfheal must do an iatt_merge in
    refresh layout to get the latest timestamp irrespective of
    whether it needs to heal the layout or not.
    
    Change-Id: I3634c3978bcc1710705f44b48f3876601682d33e
    BUG: 1302948
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13781
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f2d51d6546976731fed5fd165bf57acac3fb0180
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Mar 10 16:43:08 2016 +0530

    cli: Do not remove whitespace if key is user.* in volume set
    
    setting any user.* option can have multiple words in the key and hence skip the
    process of trimming whitespaces.
    
    Change-Id: Ia295428d7cda55e5470fef668325bea497f2333d
    BUG: 1316499
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13669
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 7fb3abaeae763b99ef387804b46943051ac6cbbc
Author: Poornima G <pgurusid@redhat.com>
Date:   Sat Mar 19 04:38:47 2016 -0400

    gfapi: Fix the crashes caused by global_xlator and THIS
    
    Issue: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10922
    
    The right fix for this is elaborate and intrusive, until it is in place,
    this patch provides a temperory fix. This fix is necessary, as without this
    libgfapi applications like qemu, samba, NFS ganesha are prone to crashes.
    This patch will be reverted completely, once the actual fix gets accepted.
    
    Change-Id: Ic975ab0bb03ba415cdf9bddba1534ba4d2d2820c
    BUG: 1319374
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13784
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit afbdcda3f4d6ffb906976064e0fa6f6b824718c8
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Mar 21 16:38:25 2016 +0530

    extras:add gfid-to-dirname.sh
    
    Add a script that converts the gfid-string of a directory into absolute
    path name w.r.t the brick path.
    
    Example:gfid-to-dirname.sh /home/ravi/bricks/brick1 e9c81321-f009-41b0-a009-cd77888c217e
    Location of the directory corresponding to gfid:e9c81321-f009-41b0-a009-cd77888c217e is /home/ravi/bricks/brick1/d1/d2/d3/d4/d5/d6/d7/
    
    Change-Id: I276ddf9c4f3d11a5b1932286d848b00b5ea1895d
    BUG: 1319706
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13797
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: bipin kunal <kunalbipin@gmail.com>
    Tested-by: bipin kunal <kunalbipin@gmail.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit b6edcbd6948f0252785672fde3db37cec6353d11
Author: Ravishankar N <root@ravi2.(none)>
Date:   Tue Mar 22 12:56:41 2016 +0000

    glusterd/ afr: Fix op-version for background client-side heals
    
    http://review.gluster.org/13207 tied cluster.heal-wait-queue-length to
    GD_OP_VERSION_3_7_9 but the patch will be merged in release-3.7 branch
    (http://review.gluster.org/#/c/13564/) only for 3.7.10.
    Hence change it on master also for uniformity.
    
    Change-Id: Id581695e58b0765f5652016cc2045f05e36b768f
    BUG: 1297172
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13810
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 86501cd36b9784a6c0247326092a50fb44524656
Author: Anoop C S <anoopcs@redhat.com>
Date:   Sun Dec 20 21:47:37 2015 +0530

    features/locks: Remove unneeded function parameter
    
    We use list_del_init() inside __delete_lock()
    to remove a lock from inode's lock list where
    pl_inode_t is not required at all. This patch
    removes pl_inode_t from list of parameters
    required for __delete_lock().
    
    Change-Id: Ic5701bcae231172d4fd7feda1b25752343ee81cf
    BUG: 1293227
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/13033
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1081584d4c2d26e56fea623ecfadd305c6e3d3bc
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Mar 20 18:31:00 2016 +0530

    glusterd/rpc : Discard duplicate Disconnect events
    
    If a peer rpc disconnect event has been already processed, skip the furthers as
    processing them are overheads and sometimes may lead to a crash like due to a
    double free
    
    Change-Id: Iec589ce85daf28fd5b267cb6fc82a4238e0e8adc
    BUG: 1318546
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13790
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 056bce103c31be8416bd3ede93c7258c5b3f8554
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Dec 15 00:19:41 2015 -0500

    extras: Ease creation of new xlators
    
    Add a python generator that creates a template for new xlator.
    
    Co-Authored by Jeff Darcy.
    
    Change-Id: I10820c0483794dcd450656684cf954f7b8f159e0
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13061
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2eb8758bbc88b182bf0e33506b8352cd82c7ec2e
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Sep 4 16:19:01 2013 +0530

    glusterd: Fix connected clients check during 'volume set'
    
    Use the volume's newly calulatedclient-op-version for the connected
    clients check. This prevents rejection of server options of higher
    op-version when clients of lower op-version are connected. Also,
    initialize the variables of the newly calculated volume op-version and
    client-op-version with the current values, instead of the cluster
    op-version.
    
    Change-Id: Ieb36f97c677a5457feba54bef20e154c0456e70e
    BUG: 1004332
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5786
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 68665d0fc4a827e9933b94da8c4a2977b1a5cee6
Author: vmallika <vmallika@redhat.com>
Date:   Wed Mar 16 13:31:10 2016 +0530

    marker: set inode ctx before lookup unwind
    
    When a file is unlinked before it was accounted by the marker,
    then we may see error "ctx for the node ... is NULL" at many places.
    This is actually not an error and can be ignored.
    
    It is better to set the inode ctx before lookup/create is unwind
    back to protocol server
    
    Change-Id: I462b5542951f2fc2964f59af7a31978979dab1de
    BUG: 1318158
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13748
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 8eaa3506ead4f11b81b146a9e56575c79f3aad7b
Author: Anuradha Talur <atalur@redhat.com>
Date:   Tue Feb 23 10:56:51 2016 +0530

    afr : Enable auto heal when replica count increases
    
    This patch is part two change to prevent data loss
    in a replicate volume on doing a add-brick operation.
    
    Problem: After doing add-brick, there is a chance
    that self heal might happen from the newly added
    brick rather than the source brick, leading to data loss.
    
    Solution: Mark pending changelogs on afr children for
    the new afr-child so that heal is performed in the
    correct direction.
    
    Change-Id: I11871e55eef3593aec874f92214a2d97da229b17
    BUG: 1276203
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12454
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 020bc022c342c4c015e29c63399757e36d653a49
Author: Anuradha Talur <atalur@redhat.com>
Date:   Wed Mar 16 10:55:09 2016 +0530

    glusterd / afr : Enable auto heal when replica count increases
    
    In replicate volumes, when a brick is added to a replicate
    group, heal to the new brick should be triggered.
    Also, the new brick should not be considered as source for
    healing till it is up to date.
    
    Previously, extended attributes had to be set manually on
    the bricks for this to happen. This patch is part 1 patch
    to automate this process.
    
    Change-Id: I29958448618372bfde23bf1dac5dd23dba1ad98f
    BUG: 1276203
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12451
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 696fbf9b18078a7ac28080d841f0de2306786b87
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Mar 17 13:37:59 2016 +0530

    glusterd/snapshot: dereferencing null variable resulted in crash
    
    When we add service details into dictionary, snapd is volume
    based service. So the svc variable for snapd will be stored in
    volinfo. But when we trying to add details for snapd node alone
    we use generic function, ie that won't have the svc variable
    initialized.
    
    Change-Id: I7e4abc477e6c520388d696548ffa260a43281827
    BUG: 1318544
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13759
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 9879c4e543e37de753b2650ab6fcd427afb0169d
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Mar 14 16:36:33 2016 +0530

    ganesha: Include a script to generate epoch value
    
    In a NFS-Ganesha HA cluster setup, for NFS clients to recover state
    succesfully post failover, the NFS-servers should start with a unique
    epoch value.
    
    With NFS-Ganesha 2.3, the service accepts an option "EPOCH_EXEC" which
    takes path of the script, generating epoch value. This script is executed before
    starting nfs-ganesha service so that the generated epoch value is used
    while bringing up the service.
    
    This patch includes the script to be used by nfs-ganesha+gluster setup.
    
    The epoch value is computed as follows -
           - first 32-bit contains the now() time
           - rest 32-bit value contains the local glusterd node uuid
    
    Change-Id: I876ea5a3730d7c6b40503e0fec16a4a142c54a36
    BUG: 1317902
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13744
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 942d127fee13653daba49195692c5e8465f1fbff
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 17 13:33:34 2016 -0400

    dht: report constant directory size
    
    Directory size is meaningless.  Every filesystem has its own
    unpredictable way of increasing or decreasing it, based on internal data
    structures and even transient conditions.  Some filesystems (e.g. ext4)
    never decrease it at all.  Others (e.g. btrfs) don't even report it.
    Very few programs look at it, and those that do are broken.
    Unfortunately, one such program is GNU tar, which will complain when it
    sees different values because at different times we got the value from
    different DHT subvolumes.  To avoid such problems, just report a
    constant value.
    
    Change-Id: Id64ce917c75b5f7ff50cb55b6e997f3b3556e7e3
    BUG: 1302948
    Original-author: Shyam <srangana@redhat.com>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13770
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7b8e82f80942b862f30d3fb72c7eecb23fcae226
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Mar 17 22:44:12 2016 +0530

    features/trash: Handle unexpected errors during mkdir
    
    When expected directory hierarchy in not present in trash directory,
    trash translator tries to create it inside the same. Any errors from
    posix other than the expected ones should be handled properly during
    an internal mkdir call and logged accordingly explaining the reason
    for not moving the file to trash directory.
    
    Change-Id: I4e19637138ea4fb92f9301be372ac19542a6aed8
    BUG: 1318757
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/13771
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 857bad73b3313c895c736faa9a5ec71d046a3da7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 16 21:55:35 2016 +0530

    cluster/afr: Enhance the test to be more robust
    
    In some cases of dht, there is code path (dht_lookup_directory) where it sets
    gfid-req before lookup. This leads to successful setting of gfid when there are
    only two subvolumes in distribute. So increased number of replica subvolumes.
    Also increased number of directories.
    
    Change-Id: I17092ce6dc69c7fed6e6b380eb0fc0040f19c06a
    BUG: 1312816
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13754
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Ravishankar N <ravishankar@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3d5bbe93c5793a78ddef015cd18ac4675cd76344
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Mar 16 13:08:23 2016 +0530

    storage/posix: Typo in log message
    
    Fixed missing spaces between some words in a log message.
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    
    Change-Id: I24398e6dd2ab83956827fc905f43cffd7e699c51
    BUG: 1318107
    Reviewed-on: http://review.gluster.org/13747
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d8ec29ae63b2efeed5da3252b4e468e07f9de4a8
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Fri Feb 26 19:34:38 2016 +0530

    changelog: fix typecasting of function
    
    fix compiler error:
    "error: void value not ignored as it ought to be"
    
    while the code tries to typecast return type of
    'LOCK_DESTROY(lock)' to (void)
    
    Change-Id: I38ed47f3a12719c7a4a59388c0d021858d4dfe6d
    BUG: 1312354
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13533
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a6aecae2cd8171b8538bfe5d2800bdd157380b85
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Fri Feb 26 19:28:58 2016 +0530

    nfs: fix lock variable type
    
    variable 'mountlock' should be generic
    since it is used by macros LOCK_* ,
    it can be used spinlock or mutexlock
    
    Change-Id: If558bcf8debd98c4e1a615df0f9f0caec586e39b
    BUG: 1312346
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13532
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7e44c783ad731856956929f6614bbe045c26ea3a
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu Feb 11 23:45:37 2016 +0530

    lock: use spinlock only on multicore systems
    
    Using spinlocks on a single-core system makes usually no meaning,
    since as long as the spinlock polling is blocking the only available
    CPU core, no other thread can run and since no other thread can run,
    the lock won't be unlocked until its time quantum expires and it gets
    de-scheduled. In other words, a spinlock wastes CPU time on those
    systems for no real benefit. If the thread was put to sleep instead,
    another thread could have ran at once, possibly unlocking the lock and
    then allowing the first thread to continue processing, once it woke up
    again.
    
    Change-Id: I0ffc14e26c2e150b564bcb682a576859ab1d1872
    BUG: 1306807
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13432
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fb3d300617d3616e1b901dd5503ff330a542c7be
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Mar 15 11:58:44 2016 +0530

    tests: Self-heald.t spurious failure fix
    
    Problem:
    There is no guarantee that the indices are created by the time
    write is complete because write-behind may not flush the buffers.
    
    Fix:
    Disable flush-behind so that by the time 'echo abc > file' completes,
    indices are created.
    
    Also removed split-brain-healing.t from spurious failures as we are
    not able to recreate it.
    
    BUG: 1306897
    Change-Id: I5c9c735430f1736747c8d7396d2cbf487533f4b5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13434
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit adbce4e9b7dadc226d3de326d98007ed10913919
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Mar 1 15:03:54 2016 -0500

    cluster/tier: add tunable to migrate files based on size
    
    This fix adds a paramater "tier-max_promote_size" to control wether
    a file is migrated or not based on its size. By default the value
    is 0, meaning all files are migrated. If set to a non-zero
    value, files larger than the parameter won't be moved
    in tiered volumes.
    
    Change-Id: Ia6b88e9b2508935bef500d956f9192e59670fe00
    BUG: 1313495
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/13570
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit 8fda324df01b6de9c58a1395263ce9755465b26d
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Mar 13 10:44:12 2016 -0400

    mount/fuse: cleanup an additional inode_ref()
    
    commit ca515db0127 introduced a check in
    fuse_resolve_inode_simple(). This results in an additional
    ref being held on inodes which were obtained through readdirp.
    As a result, the inode table keeps growing and entries remain in
    the active list even after deletion of such inodes.
    
    Change-Id: I780ec5513990d6ef00ea051ec57ff20e4428081e
    BUG: 1317948
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/13689
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 500ad8f3a72053d33120657e8a2e93d844041cf0
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Mar 15 14:21:18 2016 +0530

    md-cache: Cache gluster-swift metadata
    
    BUG: 1317785
    Change-Id: Ie02b8fc294802f8fdf49dee8bf97f1e6177d92bd
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/13735
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>

commit 1249030962a177d077e76d346d66ef6061b818ed
Author: hari <hgowtham@redhat.com>
Date:   Mon Dec 28 16:04:50 2015 +0530

    Cli/tier: separating services from cold bricks in xml
    
    fix: The cold bricks tag included the processes also.
    The patch has removed the processes from being mentioned
    inside the cold brick tag and are mentioned below by
    closing the cold brick tag after the brick count.
    
    Previous output:
            <coldBricks>
              <node>
                <hostname>192.168.1.102</hostname>
                <path>/data/gluster/b3</path>
                <peerid>8c088528-e1aee3b2b40f</peerid>
                <status>1</status>
                <port>49157</port>
                <ports>
                  <tcp>49157</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>1160</pid>
              </node>
              <node>
                <hostname>NFS Server</hostname>
                <path>localhost</path>
                <peerid>8c088528-e1aee3b2b40f</peerid>
                <status>0</status>
                <port>N/A</port>
                <ports>
                  <tcp>N/A</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>-1</pid>
              </node>
            </coldBricks>
    
    Expected output:
            <coldBricks>
              <node>
                <hostname>192.168.1.102</hostname>
                <path>/data/gluster/b3</path>
                <peerid>8c088528-e1aee3b2b40f</peerid>
                <status>1</status>
                <port>49157</port>
                <ports>
                  <tcp>49157</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>1160</pid>
              </node>
            </coldBricks>
            <node>
              <hostname>NFS Server</hostname>
              <path>localhost</path>
              <peerid>8c088528-e1aee3b2b40f</peerid>
              <status>0</status>
              <port>N/A</port>
              <ports>
                <tcp>N/A</tcp>
                <rdma>N/A</rdma>
              </ports>
              <pid>-1</pid>
            </node>
    
    Change-Id: Ieccd017d7b2edb16786323f1a76402f020bdfb0d
    BUG: 1294497
    Signed-off-by: hari <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13101
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 8d8743ebf0eea7e87eef4cabb7ebcef4a602c471
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Mar 11 15:07:48 2016 +0530

    posix: Filter gsyncd stime xattr
    
    Filter gsyncd stime xattr in lookup as well.
    The value of stime would be different among
    replica bricks and EC bricks. AFR and EC
    should not take any action on these as it
    could be different.
    
    Change-Id: If577f6115b36e036af2292ea0eaae93110f006ba
    BUG: 1296496
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13678
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 23ccabbeb7879fd05f415690124bd7b4a74d4d33
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Mar 4 13:05:09 2016 +0530

    cluster/ec: Provide an option to enable/disable eager lock
    
    Problem: If a fop takes lock, and completes its operation,
    it waits for 1 second before releasing the lock. However,
    If ec find any lock contention within this time period,
    it release the lock immediately before time expires. As we
    take lock on first brick, for few operations, like read, it
    might happen that discovery of lock contention might take
    long time and can degrades the performance.
    
    Solution: Provide an option to enable/disable eager lock.
    If eager lock is disabled, lock will be released as soon
    as fop completes.
    
    gluster v set <VOLUME NAME> disperse.eager-lock on
    gluster v set <VOLUME NAME> disperse.eager-lock off
    
    Change-Id: I000985a787eba3c190fdcd5981dfbf04e64af166
    BUG: 1314649
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13605
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit b145cd15ded130078c9f1105e76f35d0886e62d5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 7 11:52:18 2016 +0530

    protocol/server: Do not log ENOENT/ESTALE in fd based fops
    
    When fd-fops come on anon-fds there is a chance to log ENOENT/ESTALE for them.
    Log it as DEBUG.
    
    Change-Id: I8ae53c29d6a66f6a65081c281a9a5c205f53766b
    BUG: 1315168
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13621
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 53d81d9eced2b65c782c77a6f44ef343578eb3c7
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Mar 14 07:41:11 2016 -0400

    ganesha-ha: merge release-3.7 to master for release-3.8
    
    cherry-pick changes from release-3.7 branch to master in preparation
    for 3.8
    
    changes merged/cherry-picked from release-3.7 consist of:
    
    > common-ha: delete virt-IP entry of deleted node
    > commit aee983ff43655771a9102592a284d0b0a29ad89f
    > BUG: 1250601
    >
    > common-ha: concise output for HA status
    > commit d804b17f2fe92b1516f85f03978072c42ddc6f19
    > BUG: 1250628
    >
    > common-ha : refresh-config should print sensible output
    > commit d7adcca24fb9638df2806c01d8ea7e73eec46928
    > BUG: 1254494
    >
    > CommonHA: Avoid scp of the config state to the same host
    > commit 07b31a008b59d6c0b06bd17994de85fc56560b38
    > BUG: 1259225
    >
    > CommonHA: Fix the path of 'systemctl' cmd
    > commit 8e7ca068720fa6fa50e4746e5b17c305f38171e8
    > BUG: 1259225
    >
    > common-ha: refresh-config output includes dbus "method return" msg
    > commit 045cb34238e341d68288893b8f040056e138c04e
    > BUG: 1262881
    >
    > common-ha: distribution neutral location of config files
    > commit 6667478cdba920d2658bba2edc99c8f8cc33e271
    > BUG: 1251821
    >
    > common-ha: Corrected refresh-config output parsing
    > commit 2892bab69cac2d991509fca1279a659bce1ae793
    > BUG: 1254494
    >
    > common-ha: reliable grace using pacemaker notify actions
    > commit e8121c4afb3680f532b450872b5a3ffcb3766a97
    > BUG: 1290865
    >
    > ganesha: Read export_id on each node while performing refresh-config
    > commit e0e633cdce7586af92490730257ed7f0cffcff61
    > BUG: 1309238
    >
    > nfs-ganesha: pcs cluster setup needs '--name' option
    > commit 812e7321d3c56d329526628fe96a8f6fabea75ca
    > BUG: 1314204
    
    Change-Id: I41c19bd369bd9da1092b0677590634a4e9f72813
    BUG: 1317424
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13728
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f032bc6caedd0a53e79888e57c886ba3699d2396
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Mar 3 14:08:39 2016 +0530

    nfs-ganesha: pcs cluster setup needs '--name' option
    
    Even on fedora machines (on f22, f23), pcs cluster setup CLI
    expects '--name' to be provided. This patch addresses the same.
    
    BUG: 1314204
    Change-Id: If23851bfd7fe2f1c200731d66dcb3e744390ff83
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13590
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-on: http://review.gluster.org/13727
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ef1b79a86714e235a7430e2eb95acceb83cfc774
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Feb 17 15:34:44 2016 +0530

    ganesha: Read export_id on each node while performing refresh-config
    
    As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1309238#c1,
    there could be cases which shall result in having different ExportIDs
    for the same volume on each node forming the ganesha cluster.
    
    Hence during refresh-config, it is necessary to read the ExportID on
    each of those nodes and re-export that volume with the same ID.
    
    BUG: 1309238
    Change-Id: Id39b3a0ce2614ee611282ff2bee04cede1fc129d
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13459
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13726
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 5bdfaf98904a339144bf3a237b162e8385b95085
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Wed Mar 9 22:05:18 2016 +0530

    gfapi: preserve glfd state during glfs_dup
    
    Following patch introduced a new state variable in glfd
    to track the current status of the fd.
    http://review.gluster.org/13340/
    
    But this state was not copied in glfd_dup function.
    
    BUG: 1311146
    Change-Id: I283f8944035f6defe491f81e13d7ef28fc440572
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/13666
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Prashanth Pai <ppai@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4d37476f264bdb7e213f302840ac3238dc6d9791
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Mar 8 16:38:34 2016 +0530

    TIER: stopping the tierd when the volume goes down
    
    If there are large number of files to be migrated
    and by this time if the volume goes down, then the tierd
    has to be stopped. But on a huge query file list it keeps
    checking for each file before stopping. If the volume comes
    up before the old tierd dies then due to the
    presence of old tierd new one won't be created. After
    the old one completes the task, it dies and the status
    ends up as failed.
    
    This patch will check if the status is still running and then let
    it continue its work. Else it will stop running the tierd.
    
    Change-Id: I6522a4e2919e84bf502b99b13873795b9274f3cd
    BUG: 1315659
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13646
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 40a24f5ab917863d1549508ae9cf31085955d174
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Dec 14 09:24:57 2015 -0500

    common-ha: reliable grace using pacemaker notify actions
    
    Using *-dead_ip-1 resources to track on which nodes the ganesha.nfsd
    had died was found to be unreliable.
    
    Running `pcs status` in the ganesha_grace monitor action was seen to
    time out during failover; the HA devs opined that it was, generally,
    not a good idea to run `pcs status` in a monitor action in any event.
    They suggested using the notify feature, where the resources on all
    the nodes are notified when a clone resource agent dies.
    
    This change adds a notify action to the ganesha_grace RA. The ganesha_mon
    RA monitors its ganesha.nfsd daemon. While the daemon is running, it
    creates two attributes: ganesha-active and grace-active. When the daemon
    stops for any reason, the attributes are deleted. Deleting the
    ganesha-active attribute triggers the failover of the virtual IP (the
    IPaddr RA) to another node where ganesha.nfsd is still running. The
    ganesha_grace RA monitors the grace-active attribute. When the
    grace-active attibute is deleted, the ganesha_grace RA stops, and will
    not restart. This triggers pacemaker to trigger the notify action in
    the ganesha_grace RAs on the other nodes in the cluster; which send a
    DBUS message to their ganesha.nfsd.
    
    (N.B. grace-active is a bit of a misnomer. while the grace-active
    attribute exists, everything is normal and healthy. Deleting the
    attribute triggers putting the surviving ganesha.nfsds into GRACE.)
    
    To ensure that the remaining/surviving ganesha.nfsds are put into
    NFS-GRACE before the IPaddr (virtual IP) fails over there is a short
    delay (sleep) between deleting the grace-active attribute and the
    ganesha-active attribute. To summarize:
      1. on node 2 ganesha_mon:monitor notices that ganesha.nfsd has died
      2. on node 2 ganesha_mon:monitor deletes its grace-active attribute
      3. on node 2 ganesha_grace:monitor notices that grace-active is gone
         and returns OCF_ERR_GENERIC, a.k.a. new error. When pacemaker
         tries to (re)start ganesha_grace, its start action will return
         OCF_NOT_RUNNING, a.k.a. known error, don't attempt further
         restarts.
      4. on nodes 1, 3, etc., ganesha_grace:notify receives a post-stop
         notification indicating that node 2 is gone, and sends a DBUS
         message to its ganesha.nfsd putting it into NFS-GRACE.
      5. on node 2 ganesha_mon:monitor waits a short period, then deletes
         its ganesha-active attribute. This triggers the IPaddr (virt IP)
         failover according to constraint location rules.
    
    ganesha_nfsd modified to run for the duration, start action is invoked
    to setup the /var/lib/nfs symlink, stop action is invoked to restore it.
    ganesha-ha.sh modified accordingly to create it as a clone resource.
    
    BUG: 1290865
    Change-Id: I1ba24f38fa4338b3aeb17c65645e9f439387ff57
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12964
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-on: http://review.gluster.org/13725

commit 7240923a55eab2fc237d951ec0d89c51676a2aae
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Oct 28 14:50:55 2015 +0530

    common-ha: Corrected refresh-config output parsing
    
    >>>> Sample program with the earlier changes -
    output=$(dbus-send --print-reply --system \
    --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr \
    org.ganesha.nfsd.exportmgr.RemoveExport uint16:5 2>&1\
      | grep -v "^method return")
    ret=$?
    echo "${output}"
    echo $ret
    sleep 1
    output=$(dbus-send --system --dest=org.ganesha.nfsd \
    /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.AddExport \
    string:/usr/etc/ganesha/exports/export.vol3.conf \
    string:"EXPORT(Path=/vol3)" 2>&1  | grep -v "^method return")
    ret=$?
    echo "${output}"
    echo $ret
    
    Output:
    
    1
    
    1
    
    Even if the command was successfully executed, 'grep -v' has
    filtered out the output.
    
    >>>> Sample program with the current changes -
    
    output=$(dbus-send --print-reply --system --dest=org.ganesha.nfsd \
    /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.RemoveExport\
     uint16:5 2>&1)
    ret=$?
    echo "${output}"
    echo $ret
    sleep 1
    output=$(dbus-send --print-reply --system --dest=org.ganesha.nfsd \
    /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.AddExport \
    string:/usr/etc/ganesha/exports/export.vol3.conf \
    string:"EXPORT(Path=/vol3)" 2>&1)
    ret=$?
    echo "${output}"
    echo $ret
    
    Output:
    method return sender=:1.155 -> dest=:1.174 reply_serial=2
    0
    method return sender=:1.155 -> dest=:1.175 reply_serial=2
       string "1 exports added"
    0
    
    BUG: 1254494
    Change-Id: I44fbe32588ec11f087c8b99b2d55ed55ba73727c
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/12439
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13724
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 6d83559ea42644ed39e21c76cef8a1974f3dcab0
Author: Joe Julian <jjulian@io.com>
Date:   Tue Sep 8 09:53:54 2015 -0700

    common-ha: distribution neutral location of config files
    
    work on systems with config files in directories other than
    /etc/sysconfig.
    
    BUG: 1251821
    Change-Id: I009946623b508ba422a4881913455218d8846055
    Signed-off-by: Joe Julian <me@joejulian.name>
    Reviewed-on: http://review.gluster.org/12132
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13723
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 932ef7d760ee7593d337026b2126037105ffe410
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Sep 14 12:32:09 2015 -0400

    common-ha: refresh-config output includes dbus "method return" msg
    
    filter out extraneous text from dbus-send
    
    BUG: 1262881
    Change-Id: I2fec5c0cc8d1db0a12a42ca2d727a4320fd57b30
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12174
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13722
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit bcb3f9ba2b879257192c269ded6d16d29479023a
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Sep 2 14:17:55 2015 +0530

    CommonHA: Fix the path of 'systemctl' cmd
    
    'systemctl' command path should be '/usr/bin/sytemctl'.
    Fixed the typo in the HA-script.
    
    BUG: 1259225
    Change-Id: I0e7fcc1eb74419679d78d4cc61253c6edf23b57b
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/12089
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-on: http://review.gluster.org/13721
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 5154e581ae3424890533bcd71e61e0a6f4a5aa08
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Sep 2 17:15:23 2015 +0530

    CommonHA: Avoid scp of the config state to the same host
    
    During add-node, have seen an issue where in scp doesn't work
    if the source and destination host are same. Fixed the same.
    
    BUG: 1259225
    Change-Id: Ib8fe21b3c95d653c62698310d5390b46a3c6bbf4
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/12091
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-on: http://review.gluster.org/13720
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit dd1201e01f7f3cd86992f57f9b46f476bdb43d8c
Author: Meghana M <mmadhusu@redhat.com>
Date:   Wed Aug 12 14:48:39 2015 +0530

    common-ha : refresh-config should print sensible output
    
    ganesha-ha.sh --refresh-config printed the dbus-send output
    messages as is on the console. Improving the output
    of the operation by redirecting the messages to /var/log/messages
    and by checking the exit code of the command executed.
    
    The behaviour is also changed a litlle by exiting
    when refresh-config fails on any of the nodes.
    We don't want to continue changing config files
    on other nodes when refresh-config has already failed
    on one of the nodes.
    
    BUG: 1254494
    Change-Id: I33a1c0f750695135118b4ad4d5fa038b27bc7fec
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11949
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-on: http://review.gluster.org/13719
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 8a5b697456c6d5b849fff117a8150c319d850a5c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Aug 18 02:51:00 2015 -0400

    common-ha: concise output for HA status
    
    filter out unnecessary detail from the HA status
    
    BUG: 1250628
    Change-Id: I85fb3aaa3dacee2b1c48f46fb7eef6dc255168bc
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11942
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/13718
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 4bf4bab995307a87487abf3cb0808f81bf198ecd
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 5 11:16:34 2015 -0400

    common-ha: delete virt-IP entry of deleted node
    
    Avoid accumulating invalid/defunct virtual IP entries in the HA
    config file.
    
    use correct 'clean' name when adding a node and its virtual IP
    
    Also fix a nit in the sample HA config file
    
    BUG: 1250601
    Change-Id: I0e6a251334e854d0003d5930ca804f972900b624
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11841
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13717
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 64cba025b13aad7fb3020a04930cfa22fbfcb859
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Mar 8 23:05:08 2016 +0530

    cluster/ec: Do not ref dictionary in lookup
    
    Problem:
    1) dict_for_each loops over the elements without any locks, so the members of
       the dictionary can be ref/unrefed while dict_for_each is executed by another
       thread leading to crashes.
    
    Basically with distributed ec + disctributed replicate as cold, hot tiers. tier
    sends a lookup which fails on ec. (By this time dict already contains ec
    xattrs) After this lookup_everywhere code path is hit in tier which triggers
    lookup on each of distribute's hash lookup but fails which leads to the cold,
    hot dht's lookup_everywhere in two parallel epoll threads where in ec when it
    tries to set trusted.ec.version/dirty/size as keys in the dictionary, the older
    values against the same key get erased. While this erasing is going on if the
    thread that is doing lookup on afr's subvolume accesses these keys either in
    dict_copy_with_ref or client xlator trying to serialize, that can either lead
    to crash or hang based on if the spin/mutex lock is called on invalid memory.
    
    2) EC deletes GF_CONTENT_KEY from the dictionary, this may lead to extra reads
       in case of lookup-everwhere for tiered volumes.
    
    Fix:
    Do dict_copy_with_ref() for the lookup-dictionary.
    This is avoiding the problem and is not actually fixing the 1st problem.
    2nd problem will be fixed.
    
    Change-Id: I5427aa14c48cb7572977d4de9a28c5ffff2b4b95
    BUG: 1315560
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13680
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit e04bc451912733ab12bac28e47b4dd892df667d9
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 10 15:53:23 2016 +0530

    afr: Add more checks to check bricks being up
    
    Change-Id: I27f1a1c2f28d129ef7fafc676a8d3d6b82bcf2e4
    BUG: 1316462
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13667
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 1af963dc753d97efb3cbe3e5179a2148c41c9a7d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Mar 11 14:01:31 2016 +0530

    snapshot/cli: Keep the dict keys uniform
    
    snapshot info was using a different dictionary key
    as compared to other snapshot commands. This was
    throwing a recurring error log in cli.log
    
    Change-Id: I9eb9a4541c10a45ec7673a23c89c85a7dce9f3ec
    BUG: 1316819
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13677
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit d9b5fef0333e63db9d3b5077968254e3ea9d2af4
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Feb 23 20:09:52 2016 +0530

    Tier: Avoiding stale entries from causing demotion to stop
    
    When the parent GFID is a stale entry, the lookup on this parent
    fails and this in turn fails the demotion process.
    
    This patch will make the stale entry error to be skipped.
    
    Situation for pargfid to be stale:
    Consider a folder from a tar file. Once the tar file is untared
    the files in the tar-file will start to demote.
    when the demotion is under progress, if we tend to delete
    the actual folder, then the files under it which are
    undergoing demotion will do a lookup on the parent which was
    deleted and become stale entry. This stale entry fails the
    Lookup and this will fail the demotion of the other files(not from
    tar) that are supposed to be demoted.
    
    Change-Id: I3d47c32c4077526d477a25912b0135bab98b23fc
    BUG: 1311178
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13501
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 68b840267ed0f6864e4cf5ba7d842988c0fb3da8
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Mar 11 16:20:01 2016 -0500

    tests: return correct value from run_head_tests when no tests are found
    
    Also added a diff filter to avoid listing deleted tests.  Thanks to
    Raghavendra Talur for the suggestion.
    
    Change-Id: Ied2d552d227b55027211c07db6ee5dc20979596b
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: https://review.gluster.org/13686
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2807e3fc005630213ab7ad251fef13d61c07ac6b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 2 22:09:44 2016 +0530

    cluster/afr: Choose local child as source if possible
    
    It is better to choose local brick as source if possible to prevent
    over the wire read thus saving on bandwidth. Also changed code to not
    attempt data-heal if 'source' is selected as arbiter.
    
    Change-Id: I9a328d0198422280b13a30ab99545370a301dfea
    BUG: 1314150
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13585
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Krutika Dhananjay <kdhananj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 0e048b309b64e574039fc1ebedb971791d43b5e1
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 8 15:44:04 2016 +0530

    features/shard: Implement discard fop
    
    Change-Id: Ia5bd8d36b21a586df6556fbec3474892d5871229
    BUG: 1261841
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13657
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit df7390c9d7db40dcd68cf1020b6248f5105ab8eb
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 10 10:50:59 2016 -0500

    tests: run tests from the most recent commit first
    
    Change-Id: If11f552543bf0f1f0e9756e9f2237b72e44b7aed
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13439
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 805a9c7a40e22f811019f4a854636c30c164525b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Mar 5 21:41:33 2016 +0530

    tests: Use force_umount instead of umount
    
    umount leads to spurious failures with "mount is busy" kind of errors
    at the time of umount. Use 'force_umount' instead.
    
    BUG: 1310171
    Change-Id: I5a5579288f002de14effc00b793143fef86eb828
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13611
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 07a5d9e1e103c8e3ab69283711ee0832d469e145
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Mar 10 14:32:03 2016 +0530

    snapshot: Use svc->manager during glusterd restart
    
    Instead of using svc->start, we should use svc->manager
    as it takes care of initializing svc too, and both starts
    and stops snapd as needed.
    
    Change-Id: I3d3afdf4c4203bee3b790a017b820339fd376af6
    BUG: 1316437
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13665
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit b9dbfcc8f5a34cea02d97c047ebb24e057b146a3
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 10 08:56:33 2016 -0500

    fdl: fix race during initialization
    
    There was a race between fdl_worker starting to run and setting
    this->private in fdl_init.  This should never happen on a
    multiprocessor, since the new thread should start on a different core
    and creating it there should take many times longer than getting from
    pthread_create to the end of fdl_init on the original core.  The only
    way it seems likely is if the new thread is started on the same core
    that's already in fdl_init, and the new thread preempts the old, which
    many would consider broken . . . but there are plenty of broken thread
    implementations and it's hardly surprising that glibc has one.  Still,
    it's a race and it did show up in regression tests a few times, so it
    needs to be fixed.
    
    Change-Id: Ifa5b0ae1ec111860f0d3f55a98aa2b8f2cef84ca
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13674
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2bfdc30e0e7fba6f97d8829b2618a1c5907dc404
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Feb 29 14:43:58 2016 +0530

    protocol client/server: Fix client-server handshake
    
    Problem:
    Currently on a successful connection between protocol
    server and client, the protocol client initiates a
    CHILD_UP event in the client stack. At this point in
    time, only the connection between server and client is
    established, and there is no guarantee that the server
    side stack is ready to serve requests.
    
    It works fine now, as most server side translators are
    not dependent on any other factors, before being able
    to serve requests today and hence they are up by the time
    the client stack translators receive the CHILD_UP (initiated
    by client handshake).
    
    The gap here is exposed when certain server side translators
    like NSR-Server for example, have a couple of protocol clients
    as their child(connecting them to other bricks), and they
    can't really serve requests till a quorum of their children are
    up. Hence these translators should defer sending CHILD_UP
    till they have enough children up, and the same needs to be
    propagated to the client stack translators.
    
    Fix:
    Maintain a child_up variable in both the protocol client
    and protocol server translators. The protocol server should
    update this value based on the CHILD_UP and CHILD_DOWN
    events it receives from the translators below it. On receiving
    such an event it should forward that event to the client.
    The protocol client on receiving such an event should forward
    it up the client stack, thereby letting the client translators
    correctly know that the server is up and ready to serve.
    
    The clients connecting later(long after a server has initialized
    and processed it's CHILD_UP events), will receive a child_up status
    as part of the handshake, and based on the status of the server's
    child_up, can either propagate a CHILD_UP event or defer it.
    
    Change-Id: I0807141e62118d8de9d9cde57a53a607be44a0e0
    BUG: 1312845
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13549
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 537822d7eb7732f2f65300668355b6d7db448f39
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Mar 8 17:22:35 2016 +0530

    Tier: displaying status only one the nodes running tierd
    
    When tier status is given on a cluster where one node doesn't
    have tierd running, the status is shown as not started.
    
    The status of the node without tierd should not be displayed.
    
    This patch will skip if the current node if the status is not
    started
    
    Change-Id: Ibeb39f13133f94a5869b020c5ccd9bd6992323f1
    BUG: 1315666
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13647
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit a007fdf549260d0b146184fa85ca7029560db8c5
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Thu Mar 10 07:51:48 2016 +0530

    glusterd: fixing few memory leak in glusterd
    
    While freeing memory currently glusterd is not freeing correct
    memory. this might result in some serious situation.
    
    With this fix glusterd will free correct memory location.
    
    Change-Id: Ide9c33a2ec5822b560e9e2dfcb6a0b442fc97047
    BUG: 1287517
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/13660
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 6332eb773914ffd92aa78376c11908ddecb99d6e
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Mar 7 09:17:48 2016 -0500

    nsr-server: fix (?) ENODATA problem on FreeBSD
    
    Change-Id: I5f16a04e34a37e1f4cef38d75aff3479429473e3
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13625
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 6df883cef3e69b37a192aae9e979f95b32f8ad41
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 9 16:40:36 2016 +0530

    tests, shard: fallocate tests refactor
    
    Change-Id: I3f275185f4dcb1939e8074851c8f140c5e40b28d
    BUG: 1261841
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13405
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit ed98d128a9413f7b8af328ca27bf4b27514d61e9
Author: vmallika <vmallika@redhat.com>
Date:   Tue Feb 2 14:34:19 2016 +0530

    gluster/uss: change ctime attr of a dir when USS enabled
    
    Consider a testcase:
     mount -t nfs host1:/vol1 /mnt
     ls /mnt
     ls /mnt/.snaps (As expected this fails)
     gluster volume set vol1 features.uss enable
    
    Now `ls /mnt/.snaps` should work, but fails with No such file or
    directory.
    This is because NFS client  and Kernel VFS caches the list of files in a
    directory.
    This cache is updated if there are any changes in the directory attributes.
    
    This patch solves the problem by changing ctime attribute when USS is
    enabled
    
    Change-Id: I48b284100d0589f1c0285782a1302080c15d4e1f
    BUG: 1163416
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9106
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit e0f71288d95469d7ae82473ef273c6ba43250a36
Author: vmallika <vmallika@redhat.com>
Date:   Wed Feb 10 06:39:22 2016 +0530

    uss/gluster: generate gfid for snapshot files from snapname and gfid
    
    If 'a' and 'b' are hardlinks, we need to generate a virtual
    gfid for these files so that the inode number for 'a' and 'b'
    are same.
    
    Generate gfid as below:
    gfid_of_a = MD5(snapname + back_end_gfid(a))
    if '/dir1/a' and '/dir2/b' are hardlinks, then inode number should be
    same for
    all below files:
    /mnt/.snaps/snap1/dir1/a
    /mnt/.snaps/snap1/dir2/b
    /mnt/dir1/.snaps/snap1/a
    /mnt/dir2/.snaps/snap1/b
    
    Change-Id: Ifda793455610e554f3f1e4cbb90d44c02cda4b0f
    BUG: 1171703
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9255
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit ecf6243bc435a00f3dd2495524cd6e48e2d56f72
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Mar 2 15:19:30 2016 +0530

    glusterd: Always copy old brick ports when importing
    
    When an updated volinfo is imported in, the brick ports from the old
    volinfo should be always copied.
    
    Earlier, this was being done only if the old volinfo was stopped and
    new volinfo was started. This could lead to brick ports chaging when the
    following sequence of steps happened.
    - A volume is stopped
    - GlusterD is stopped on a peer
    - The stopped volume is started
    - The stopped GlusterD is started
    This sequence would lead to bricks on the peer with re-started GlusterD
    to get new ports, which could break firewall rules and could prevent
    client access. This sequence could be hit when enabling management
    encryption in a Gluster trusted storage pool.
    
    Change-Id: I808ad478038d12ed2b19752511bdd7aa6f663bfc
    BUG: 1313628
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/13578
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f6e5bc68d294cc67f1e7f4db043d2531d4cfec80
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Feb 8 12:13:54 2016 +0530

    tests: Add mechanism for disabled tests
    
    Requirements:
    Should be able to skip tests from run-tests.sh run.
    Should be granular enough to disable on subset of OSes.
    
    Solution:
    Tests can have special comment lines with some comma separated values
    within them.
    
    Key names used to determine test status are
    G_TESTDEF_TEST_STATUS_CENTOS6
    G_TESTDEF_TEST_STATUS_NETBSD7
    Some examples:
    G_TESTDEF_TEST_STATUS_CENTOS6=BAD_TEST,BUG=123456
    G_TESTDEF_TEST_STATUS_NETBSD7=KNOWN_ISSUE,BUG=4444444
    G_TESTDEF_TEST_STATUS_CENTOS6=BAD_TEST,BUG=123456;555555
    You can change status of test to enabled or delete the line only if all the
    bugs are closed or modified or if the patch fixes it.
    
    Change-Id: Idee21fecaa5837fd4bd06e613f5c07a024f7b0c2
    BUG: 1295704
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13393
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 9e3a0791c0f1f336e55672b24721154bc862456b
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Mar 9 04:05:20 2016 -0500

    fuse: Address the review comments in the backport
    
    Backport @ http://review.gluster.org/#/c/13626/3
    
    Fix a typo error, consolidate the selinux and capability
    check in getxattr and setxattr.
    
    Change-Id: I4303de3d4dd00853169b07577311e03cbb912ed7
    BUG: 1316327
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13653
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8fd5a8e7a3cbcc8e98ddb2ec161ef14cd5a671aa
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Mar 7 15:01:39 2016 -0500

    features/bit-rot-stub: get frame->local before unwinding
    
    In bit-rot-stub, if unlink fails, then it was unwinding
    directly. Then it was trying to cleanup local. But local
    would be NULL, since it was unwinding directly without getting
    the value of frame->local. The NULL cleanup of local was
    causing the brick process to crash.
    
    Change-Id: I8544ba73b2e8dc0c50b1a53ff8027d85588d087b
    BUG: 1315465
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13628
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 15a5f7db3b442e67030309b4a1dc5e33be2fbcb5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Feb 29 14:05:54 2016 +0530

    geo-rep: Fix Entry Creation issue with non root UID/GID
    
    During entry_ops RENAME Geo-rep sends stat info along with the
    recorded info from Changelog. In Slave side if Source file exists
    Geo-rep renames to Target file by calling os.rename. If source file
    does not exists, it tries to create Target file directly using available
    stat info from Master. If UID and GID are different in Master for that
    file then stat info will have different UID/GID during Create. Geo-rep
    gets EACCES when it tries to create a new entry using gfid-access with
    different UID/GID.
    
    With this patch, Entry creation with different UID/GID is split into two
    operations. Create Entry with UID:0 and GID:0 and then set UID/GID.
    
    Change-Id: I4987e3a205d8513c06fa66198cde145a87003a01
    BUG: 1313303
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13542
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit bf03543388c39e4b5162ff5866ba4754fb4fdfc1
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Jan 6 21:23:51 2016 +0530

    geo-rep: hard-link rename issues on changelog replay
    
    Problem:
    LINK + RENAME changelog when replayed after worker restart causes stale
    hard-links to persist since VFS returns success for RENAME if hard-links
    point to same inode.
    
    Solution:
    Worker detects RENAME being issued on hard-links to the same inode and
    unlinks the source file-name. Conditionally rename by verifying that the
    source gfid matches with the on-disk gfid on the slave.
    
    Change-Id: I3ff1c30ef79e77503c8b246d46dab8ac3059ccf2
    BUG: 1296174
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/13189
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 5cb80ac63b17a3c34d4deef1816e1782757687d9
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Sat Mar 5 16:06:18 2016 -0500

    packaging: rpm scriptlet cleanup, handle -p /sbin/ldconfig
    
    The RPM documention indicates that during an rpm install or erase, the
    script(lets): %post, %preun, and %postun (and %pre, %build, %install,
    etc.) are copied to a temp file, and then the temp file is run as a
    (/bin/sh or bash) script.
    
    Unfortunately the documentation is not clear about how rpmbuild and/or
    rpm determine where the end of any scriptlet is when it is copied to
    the file.
    
    Most things in the glusterfs.spec work correctly as is. These are the
    %preun, %post, and %postun scriptlets that are "closed" by a following
    %preun, %post, and %postun, or poetentially another scriptlet, e.g.
    %file.
    
    The ones that don't work correctly (only one actually) are those where
    there is a comment in the spec file before it is closed by another
    scriptlet. Further complicating things is that the type of scriptlet
    affects what rpm does and what `rpm -qp --scripts ...` shows.
    
    The specific one that didn't work was the "%postun libs" scriptlet. It
    is followed by a comment before being "closed" by the %files section (or
    scriptlet). It can be written two ways: "%postun libs\n/sbin/ldconfig"
    or "%postun libs -p /sbin/ldconfig" Either way it's written, `rpm -qp
    --scripts glusterfs-libs...` will include the comment lines between the
    %postun libs line and the following %files line.
    
    But the way rpm executes these depends on how they're written. If
    written as "%postun libs\n/sbin/ldconfig" rpm will simply run
    /sbin/ldconfig with no command line options, i.e.
      execve ("/sbin/ldconfig", [ "/sbin/ldconfig" ], [ ]);
    
    But when written as "%postun libs -p /sbin/ldconfig", it will copy
    the comment lines to a temp file, and pass the temp file name and "1"
     as (command line) parameters, i.e.
      execve ("/sbin/ldconfig", [ "/sbin/ldconfig", "/tmp/tmpXXXXXX", "1" ],
              [ ]);
    
    Which results in ldconfig exiting with an error. (Remember, both ways show
    the comment in `rpm -qp --scripts ...`)
    
    (Note though, that the similar "%postun api -p /sbin/ldconfig" is run
    correctly, because it is "closed" by the following "%postun server"
    scriptlet.)
    
    Finally, through trial and error, it appears that rpm can be tricked with
    a hack, and "closure" of the scriptlet forcedlike this:
    
     %postun libs -p /sbin/ldconfig
    
     %if ( 0%{?_undocumented_hack_closes_scriptlets} )
     %postun
     %endif
    
    in which case ldconfig appears to run correctly. Note also that here too
    the comment will be included in the output of `rpm -qp --scripts ...`
    But that's very ugly hack.
    
    Change-Id: I587a490ddcdf47d01605479bc8ef8b0e439108fb
    BUG: 1315024
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13613
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit c00722ff9d83d131e624f5499da05160d184cfba
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Feb 25 18:27:09 2016 +0530

    features/shard: Return ENOTSUP for unsupported fallocate flags
    
    Basis: http://lists.gnu.org/archive/html/qemu-devel/2016-02/msg05101.html
    
    Change-Id: I5bf80b6e8caed3d7f136fc57e16abfb28869e009
    BUG: 1261841
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13523
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 66d62edd08be5701407e4adcb153a676702ff8b8
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 8 10:21:14 2016 +0530

    tests: Move tier-file-create.t to bad tests
    
    Change-Id: Iaddb244699b0e2647a67a75f257e4c47e0e69e0d
    BUG: 1315560
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13632
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d1d364634dce0c3dcfe9c2efc883c21af0494d0d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 3 23:17:17 2016 +0530

    afr: misc performance improvements
    
    1. In afr_getxattr_cbk, consider the errno value before blindly
    launching an inode refresh and a subsequent retry on other children.
    
    2. We want to accuse small files only when we know for sure that there is no
    IO happening on that inode. Otherwise, the ia_sizes obtained in the
    post-inode-refresh replies may mismatch due to a race between
    inode-refresh and ongoing writes, causing spurious heal launches.
    
    Change-Id: Ife180f4fa5e584808c1077aacdc2423897675d33
    BUG: 1309462
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13595
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit eea4175addff08d010c2f7c6446397561b1cd919
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Feb 18 11:21:12 2016 -0500

    qemu-block: deprecated/defunct, remove from tree
    
    qemu-block xlator is not used by anyone, or so I'm told.
    
    It's also substantially out of date. There's little reason to keep
    it in our sources. (And FedoraProject doesn't like bundled software
    either.)
    
    Change-Id: I1112a5fe5278b7899484eebc2e74fca713346b75
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13629
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 05d3d95afa62ef3271f0fe3c7272e1e19638c448
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jan 21 14:48:34 2016 +0530

    glusterd: volume get should pick options from priv->opts too
    
    As of now volume get was not looking for all the global options maintained in
    option dictionary in glusterd_conf_t. This patch includes the same.
    
    Change-Id: Ib05259a2dcacc4a712cae4217fe4a6553b61da56
    BUG: 1300596
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13272
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4318354aac650c18b4047142e43f3d4cff4310a7
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Mar 8 13:41:58 2016 +0530

    geo-rep: Fix CPU utilization 100% with Popen
    
    Errorstore is maintained by Geo-rep to collect errors from
    the child processes opened using Popen. If Popen.communicate
    is used then it closes stderr. When stderr is not available
    errorstore.tailer() will enter into infinite loop without gap.
    
    With this patch, sleep time added when stderr of Child process
    is already closed.
    
    Change-Id: Ic36aabd6de35b259467d0bab7952468432867a94
    BUG: 1315601
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13637
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 325e62cc01a836058622d6ca8e534c352f954848
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Mar 2 11:40:24 2016 +0530

    rpc: Connect back only if rpc is not disabled
    
    This is to fix regression caused by below patch -
    http://review.gluster.org/#/c/13456/
    
    As discussed over http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/14284,
    patch #13456 caused a regression where in if there are any pending
    rpc invocations, we end up accessing freed object. This patch
    fixes it by allowing reconnect during rpc submit only if rpc
    is not disabled.
    
    Change-Id: I4ef4dd52bd42368bb89129f98bc973e46c6a39f4
    BUG: 1295107
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13592
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 62047c80f541985bf9caa41336f471d95de3ce1c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Dec 9 17:09:42 2015 +0530

    tools/glusterfind: Do not fail cleanup script on volume delete
    
    If glusterfind dir is not present inside GLUSTERD_WORKDIR, then
    cleanup script Post Volume delete was failing. This patch safely
    handles the absence of glusterfind directory in GLUSTERD_WORKDIR
    
    BUG: 1289935
    Change-Id: I9f7e6035e3dc6079927803df942b0f921218c79a
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/12923
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit f44232e6a18a4b79e680ea0b6322269b84fa6813
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Mon Feb 29 15:48:58 2016 +0530

    glusterd:upon re-peer probe glusterd should not return response to CLI two times
    
    If a node N1 and node N2 is part of the cluster and a node N2 try to reprobe
    node N1 when N1 is disconnected by any means (for eg: either server is down
    or glusterd is not running or there is a network outage, or firewall is
    blocking port number 24007 on which glusterd listen, etc.), then glusterd
    trying to send back two responses to CLI resulting into a double free and
    a glusterd crash.
    
    With this fix glusterd  will send response to cli only once and prevent
    glusterd crash.
    
    Note: glusterd was crashing only when user has done first peer probe with
    hostname and re-probe with ip-address or vice-versa.
    
    Change-Id: I92012b147091cf9129f1fbc17834b3f4d7cb46a0
    BUG: 1310677
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/13546
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 5b5f03d2665687ab717f123da1266bcd3a83da0f
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Feb 26 06:42:14 2016 -0500

    fuse: Add a new mount option capability
    
    Originally all security.* xattrs were forbidden if selinux is disabled,
    which was causing Samba's acl_xattr module to not work, as it would
    store the NTACL in security.NTACL. To fix this http://review.gluster.org/#/c/12826/
    was sent, which forbid only security.selinux. This opened up a getxattr
    call on security.capability before every write fop and others.
    
    Capabilities can be used without selinux, hence if selinux is disabled,
    security.capability cannot be forbidden. Hence adding a new mount
    option called capability.
    
    Only when "--capability" or "--selinux" mount option is used,
    security.capability is sent to the brick, else it is forbidden.
    
    Change-Id: I77f60e0fb541deaa416159e45c78dd2ae653105e
    BUG: 1309462
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/13540
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 2d87a981657ee23d00c20813deddeb320e0afa8f
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Mon Mar 7 13:37:31 2016 +0530

    glusterd: avoid setting op-version lower than current cluster op-version
    
    Currently glusterd allow setting a cluster op-version which is lower than
    current cluster op-version. Though command is successful but it does not
    set that lower op-version.
    
    With this fix it will return error message "Required op-version
    (requested op-version) should not be lower than current cluster
    op-version (current cluster op-version)"
    
    Change-Id: Ia5b61858ee22a5a26721ec12ab12ff48e1a40c82
    BUG: 1315186
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/13622
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 9c3fc4344a11f2b6d0a7906d45bc7a684d756839
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Sun Mar 6 08:32:52 2016 -0500

    ganesha: coverity fix in glusterd-ganesha.c
    
    CID 1351698
    
    Allocating buffer of size stat.st_size) to read lines from the file
    without an overrrun feels like a bit of a  hack. While it's extremely
    unlikely that the file would ever be more than a thousand bytes long,
    a) we don't want to use bad patterns (and set bad examples or
    precedents for elsewhere in the source), and b) what if somehow the
    file did become "large." We just don't want to ever risk allocating
    huge amounts of memory by accident.
    
    And all the superfluous logic to copy the resulting string? We have
    gf_strdup() for that.
    
    And a clean coverity. See following gerrit review comments for the URL.
    
    Change-Id: I5860d6995d0eed06667fd2369df6be53ccff6ceb
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13614
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6860968c3adaf2e8c3cb51124bbdfccef74beeb9
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Feb 18 11:21:12 2016 -0500

    qemu-block: deprecated/defunct, remove from tree
    
    qemu-block xlator is not used by anyone, or so I'm told.
    
    It's also substantially out of date. There's little reason to keep
    it in our sources. (And FedoraProject doesn't like bundled software
    either.)
    
    Change-Id: I4aeb2fdfd962ec6d93de6bae126874121272220a
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13473
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 459d0a5e173f9d9f597aec89f81e5377425eb8fb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Feb 25 18:45:20 2016 +0530

    features/index: Get gfid type in readdir
    
    Change-Id: I2a6174e1af70a94a52b0b735fd8504800a7ea173
    BUG: 1313135
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13553
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit fe382917793c00f4cbedeef175707d35cb208f5d
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 3 14:49:04 2016 -0500

    packaging: %post server isn't quiet
    
    firewall-cmd prints out "success" during install
    
    Change-Id: I9b0d3d38170d2fc41fefd6ef555a958c5eeb39aa
    BUG: 1312897
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13596
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 8ab87137c855c9a0551a9100c146e4ca76dbbda2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Feb 29 05:16:50 2016 +0000

    afr: do not set arbiter as a readable subvol in inode context
    
    Problem:
    If afr_lookup_done() or afr_read_subvol_select_by_policy() chooses the
    arbiter brick to serve the stat() data, file size will be reported as
    zero from the mount, despite other data bricks being available. This can
    break programs like tar which use the stat info to decide how much to read.
    
    Fix:
    In the inode-context, mark arbiter as a non-readable subvol for both
    data and metadata.
    
    It it to be noted that by making this fix, we are *not* going to serve
    metadata FOPS anymore from the arbiter brick despite the brick storing
    the metadata. It makes sense to do this because the ever increasing
    over-loaded FOPs (getxattr returning stat data etc.) and compound FOPS
    in gluster will otherwise make it difficult to add checks in code to
    handle corner cases.
    
    Change-Id: Ic60b25d77fd05e0897481b7fcb3716d4f2101001
    BUG: 1310171
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reported-by: Mat Clayton <mat@mixcloud.com>
    Reviewed-on: http://review.gluster.org/13539
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bf80b9005240811d931090afcfee8ca0b02f8212
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Mar 2 11:35:44 2016 +0100

    tests: Fix spurious failure of ec-read-policy.t
    
    Change-Id: I5297e24dd10cbfbcd671fe630ae3e960b9daa8f8
    BUG: 1313775
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/13575
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e6a29ab2947eba3ee12ba3a94d4f04c41a22b5a4
Author: Anuradha Talur <atalur@redhat.com>
Date:   Fri Mar 4 01:41:09 2016 +0530

    Remove replace-brick-self-heal.t from bad-tests
    
    Unable to recreate any failures even after running
    the test for more than an hour in a loop.
    
    Change-Id: Id1c7e60d39bce6b312dbb4ea0975079348bb1649
    BUG: 1314549
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13599
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0b930ea4ed5ee84f0fbbd37b158ced58a06c6660
Author: vmallika <vmallika@redhat.com>
Date:   Tue Mar 1 16:40:35 2016 +0530

    quota: reduce latency for testcase ./tests/bugs/quota/bug-1293601.t
    
    Currently test-case './tests/bugs/quota/bug-1293601.t' runs quota enable
    and disable 10 times each, which take a long time.
    
    This is not a real use-case and it is enough to test once.
    
    Change-Id: Ic282d66438f89721f3c392929047ba42b85ad155
    BUG: 1313300
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13556
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 85b9e8ebb89ecadd30a364853e1e7c706dcce968
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 25 14:42:48 2016 +0530

    glusterd: reject peer probe from a reinstalled node
    
    In a cluster if a node (say N1) goes through a OS reinstallation then probing
    some other node in the cluster from N1 doesn't fail as in
    gd_validate_mgmt_hndsk_req () uuid & hostname checks are done separately but
    there should be one more check where both the conditions should meet.
    
    Steps to create the problem
    - N1 probes N2
    - bring down glusterd instance on N2
    - remove /var/lib/glusterd/* from N2
    - restart glusterd instance on N2
    - execute gluster peer probe N1 from N2
    
    Validations in gd_validate_mgmt_hndsk_req () has been improved to handle this
    special case
    
    Change-Id: I3ba5d8e243bae07a7a6743d01b019e7014d39171
    BUG: 1311874
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13519
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d117466422b2fe97390b9ccc7a3c277e7a64285a
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 1 13:04:03 2016 +0530

    socket: Launch socket_poller only if connect succeeded
    
    For an encrypted connection, sockect_connect() used to launch
    socket_poller() in it's own thread (ON by default), even if the connect
    failed. This would cause two unrefs to be done on the transport, once in
    socket_poller() and once in socket_connect(), causing the transport to
    be freed and cleaned up. This would cause further reconnect attempts
    from failing as the transport wouldn't be available.
    
    By starting socket_poller() only if connect succeeded, this is avoided.
    
    Change-Id: Ie22090dbb1833bdd0f636a76cb3935d766711917
    BUG: 1313206
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/13554
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit fdd8fc6f82e3b47eb47c82335f79552610596913
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Feb 22 08:31:39 2016 -0500

    packaging: gratuitous dependencies on rsyslog-mm{count,jsonparse}
    
    remove unnecessary dependencies.
    
    GlusterFS only ships example config files, and the system may not
    actually be using rsyslog at all. (It may only be RHEL5 that uses
    rsyslog "out of the box.")
    
    Also, several example config files (including gluster-rsyslog-7.2.conf,
    gluster-rsyslog-5.8.conf, logger.conf.example) are already installed in
    /etc/glusterfs/ by `make install` in the extras directory and are
    included in the -server RPM. Installing them (anywhere) in the spec
    file is redundant. Furthermore, a query in the fedora-devel mailing
    list about the preferred location for these files went unanswered.
    
    Change-Id: I07bd6a8714a05e8b91adc03f101032c1593da360
    BUG: 1310437
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13485
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4961f6329128392691d1fce7fb236de05278611d
Author: vmallika <vmallika@redhat.com>
Date:   Thu Mar 3 11:29:56 2016 +0530

    MAINTAINERS: add maintainers for quota
    
    Change-Id: I47faaca0f66b8e566ced72646ee6ff8e7cad90d8
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13586
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6a406b87aa3cd8c086e998fe681197915bd436c2
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Mar 3 16:09:27 2016 +0530

    tier: Fix unused-but-set-variable warning
    
    Change-Id: Ie5eaf1075b1c9c29dd7d85bf7b61b22e1fbce422
    BUG: 1314291
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13591
    Reviewed-by: hari gowtham <hari.gowtham005@gmail.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 15be1c1a00089ad4d9de18f1351c17d067949b61
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Jan 12 16:58:57 2016 +0530

    tests/quota : improving tests for quota
    
    tests/basic/quota.t includes all the basic test that
    needs to be tested for quota. In most of the other
    tests specific to bugs(tests/bugs/quota/*), tests
    such as creating and starting volume, enabling quota,
    setting limit, writing data, doing list have been done
    which is essential to write a individual quota test
    file, but, if the specific bug just needs to test
    *few* particular cases, I have moved those tests
    under tests/basic itself to speedup the regressions.
    
    Basics of inode-quota and it's enforcing, renaming
    with quota are basic tests and is hence moved under
    tests/basic folder.
    
    In other files, I have removed tests which are not
    needed, such as 'pidof glusterd' or checking for
    'gluster volume info' or if there are any test which
    is already being tested under tests/basic and is being
    written again.
    
    Change-Id: Iefd6d9529246d59829cc5bf02687a1861d8462a8
    BUG: 1294826
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/13216
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 133441436875416258bdc1272db91fab73a7065c
Author: hari <hgowtham@redhat.com>
Date:   Fri Feb 19 13:43:48 2016 +0530

    Tier: making detach start fail when brick on hot tier is down
    
    Currently detach tier start happens even when a hot brick is down
    this might lead to data loss.
    
    This patch prevents the detach tier start from being executed
    successfully if a brick in hot tier is down
    
    Change-Id: I3b6047a44bd01b8a6887d41f799f64de6bf075ef
    BUG: 1309999
    Signed-off-by: hari <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13474
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c57805324e8615dee4cbd6a8cc604f517845ac85
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Jun 11 09:15:17 2015 +0530

    MAINTAINERS: Geo-replication maintainer addition
    
    Change-Id: I231e075370c7f883090ecf5792e6f7633773f6c9
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11171
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 92273862decac2282b7f2a9183df3f139e5629a5
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Mar 3 12:24:49 2016 +0530

    glusterd: Avoid ret value of glusterd_resolve_brick in retreive brick path
    
    In glusterd_store_retrieve_bricks() commit a60c39d introduced
    glusterd_resolve_brick () call to resolve all the bricks which is incorrect
    since by the time peerinfo list may not be constructed. The requirement here was
    to get the local brick's uuid populated and match that with MY_UUID.
    
    Fix is to overlook the return code of glusterd_resolve_brick() to ensure that
    the failure in resolving non local bricks are genuine and expected.
    
    Change-Id: I22822ae5b4e96fe4eacd50ea5c41e58061557106
    BUG: 1313901
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13588
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 14609729da9ed8f76be6ff0ce5d6a6b278af6e8d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 1 17:31:11 2016 +0530

    mgmt/glusterd: Show features.shard option in volume-set-help output
    
    Change-Id: If9004c4374b92d058cf56add50a91ecad43a2840
    BUG: 1261773
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13565
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit bc07cb8cc45e79c54e4d411b2e2dd5b2f68bae17
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 1 16:23:22 2016 +0530

    features/shard: Fix NULL-dereference when fsync fails
    
    Change-Id: I4e51961c158c3b5c78791846ca7f0f6cf7fb5c4a
    BUG: 1313293
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13562
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 9b022c3a3f2f774904b5b458ae065425b46cc15d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Feb 27 23:08:06 2016 +0530

    cluster/afr: Don't delete gfid-req from lookup request
    
    Problem:
    Afr does dict_ref of the xattr_req that comes to it and deletes "gfid-req" key.
    Dht uses same dict to send lookup to other subvolumes. So in case of
    directories and more than 1 dht subvolumes, second subvolume till the last
    subvolume won't get a lookup request with "gfid-req". So gfid reset never
    happens on the directories in distributed replicate subvolume for 2nd till last
    subvolumes.
    
    Fix:
    Make a copy of lookup xattr request.
    
    Also fixed replies_wipe possibly resetting gfid to NULL gfid
    
    BUG: 1312816
    Change-Id: Ic16260e5a4664837d069c1dc05b9e96ca05bda88
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13545
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit a25f4e22f8cc68d95468f6873f4f6f0296d4405e
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Sun Feb 28 16:34:50 2016 +0530

    cli/tests: disable tiering on NetBSD
    
    As proposed in the following email:
    
      http://www.gluster.org/pipermail/gluster-devel/2016-February/048464.html
    
    Short version: tiering tests on NetBSD are failing often enough to
    impede other development, and also to cast doubt on whether tiering even
    works on that platform.  The most effective way to satisfy both
    developers' and users' interests is to disable tiering on NetBSD until
    such time as someone becomes available to resolve these problems another
    way.
    
    Change-Id: I7375527c339e2650a7e8e900a0d0572013213544
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13535
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 8210ca1a5c0e78e91c6fab7df7e002e39660b706
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Jan 10 09:19:34 2016 +0530

    afr: Add throttled background client-side heals
    
    If a heal is needed after inode refresh (lookup, read_txn), launch it in
    the background instead of blocking the fop (that triggered refresh) until the
    heal happens.
    
    afr_replies_interpret() is modified such that the heal is
    launched only if atleast one sink brick is up.
    
    Max. no of heals that can happen in parallel is configurable via the
    'background-self-heal-count' volume option. Any number greater than that
    is put in a wait queue whose length is configurable via
    'heal-wait-queue-leng' volume option. If the wait queue is also full,
    further heals will be ignored.
    
    Default values:  background-self-heal-count=8, heal-wait-queue-leng=128
    
    Change-Id: I1d4a52814cdfd43d90591b6d2ad7b6219937ce70
    BUG: 1297172
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13207
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit ea00992d3d52a51b7c8311ad9565bbbb6e395f9d
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Fri Jan 22 17:47:07 2016 +0530

    NFS-Ganesha : scripts related changes for supporting multiple export entires for volume
    
    Previously script such as dbus-send.sh, ganesha-ha.sh can handle only one EXPORT{} block.
    
    Change-Id: I2286af4877f96f4334435818f67beea87efa2b1f
    BUG: 1275966
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13283
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 487b3a65d3cebefac93a30222eb81b0a7465c778
Author: Cedric Buissart <cbuissar@redhat.com>
Date:   Wed Dec 23 17:29:50 2015 +0100

    gluster man page: adding geo-replication chapter
    
    geo-replication options are currently missing from gluster(8) man page.
    
    Change-Id: I5d24de856be264e63d3ff49f9b82346476f20473
    BUG: 1293950
    Signed-off-by: Cedric Buissart <cbuissar@redhat.com>
    Reviewed-on: http://review.gluster.org/13073
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Aravinda VK <avishwan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 87d93fac9fcc4b258b7eb432ac4151cdd043534f
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Jan 29 13:53:07 2016 +0530

    georep: avoid creating multiple entries with same gfid
    
    Problem:
    CREATE + RENAME changelogs replayed by geo-replication cause
    stale old-name entries with same gfid on slave nodes.
    A gfid is a unique key in the file-system and should not be
    assigned to multiple entries.
    
    Solution:
    Create entry on slave only if lstat(gfid) at aux-mount fails.
    This applies to files as well as directories.
    
    Change-Id: Ice3340f4ae1251c2dcef024a2388c4d33b5d4919
    BUG: 1296206
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/13316
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit a35bfdaa6279a981a84e8831d65702496f1e478e
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Tue Feb 9 16:44:03 2016 +0530

    geo-rep: Fix invalid disk size in gverify.sh
    
    Problem:
            Due to the wrong interpretation of disk size, gverify.sh script
    exits in between with error "integer expression expected".
    This error can be observed, only if gverify.sh is run standalone.
    
    Solution:
            Fix the interpretation of disk size.
    
    Also, verify that master and slave's gluster version are same.
    
    Change-Id: Id095dfffd07a93a535a380f617ad215230979870
    BUG: 1305839
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/13407
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 9afe93bee897c8ead507a8dadb0e0fc32ed8abf0
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Feb 15 10:59:29 2016 +0100

    cluster/ec: Fix invalid config check for directories
    
    The trusted.ec.config xattr is not defined for directories. However
    sometimes it could be requested because the inode type of a directory
    can temporarily be IA_INVAL.
    
    Requesting such xattr using the xattrop fop when it doesn't exist,
    returns a config value full of 0's, which is invalid and caused some
    fops to fail.
    
    This patch filters out this case by ignoring config xattr == 0.
    
    Change-Id: Ied51c35b313ea8c3eeae27812f9bae61d3808e92
    BUG: 1293223
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/13446
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b1cb581424305592fac5394a578b307117b22fe7
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Feb 17 15:50:05 2016 +0530

    features/trash: Retain file permissions during truncate
    
    Consider the situation where directory path for a truncated
    file does not exists under trash directory. In this scenario
    after creating the required path we failed to create the
    orginal file with proper permissions. Eventhough we try to
    fetch permissions from local->origpath, it was never filled
    with required value in truncate and ftruncate call paths.
    This change will copy original location to local->origpath
    inside both fop handling functions.
    
    Change-Id: If5930b6d368d08e58f04db999f3f9edb9250bcb9
    BUG: 1309342
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/13461
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2102010edab355ac9882eea41a46edaca8b9d02c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Feb 16 20:22:36 2016 -0500

    features/bitrot: do not remove the quarantine handle in forget
    
    If an object is marked as bad, then an entry is corresponding to the
    bad object is created in the .glusterfs/quarantine directory to help
    scrub status. The entry name is the gfid of the corrupted object.
    The quarantine handle is removed in below 2 cases.
    
    1) When protocol/server revceives the -ve lookup on an entry whose inode
       is there in the inode table (it can happen when the corrupted object
       is deleted directly from the backend for recovery purpose) it sends a
       forget on the inode and bit-rot-stub removes the quarantine handle in
       upon getting the forget.
       refer to the below commit
       f853ed9c61bf65cb39f859470a8ffe8973818868:
       http://review.gluster.org/12743)
    
    2) When bit-rot-stub itself realizes that lookup on a corrupted object
       has failed with ENOENT.
    
    But with step1, there is a problem when the bit-rot-stub receives forget
    due to lru limit exceeding in the inode table. In such cases, though the
    corrupted object is not deleted (either from the mount point or from the
    backend), the handle in the quarantine directory is removed and that object
    is not shown in the bad objects list in the scrub status command.
    
    So it is better to follow only 2nd step (i.e. bit-rot-stub removing the handle
    from the quarantine directory in -ve lookups). Also the handle has to be removed
    when a corrupted object is unlinked from the mount point itself.
    
    Change-Id: Ibc3bbaf4bc8a5f8986085e87b729ab912cbf8cf9
    BUG: 1308961
    Original author: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13472
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 99fde63452d33c3b80997883c91b2ea0f422db5b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Feb 29 15:27:31 2016 +0530

    tests: fix bug-860663.t
    
    Three changes:
    
     * Removed the second round of file creation, which wasn't really
       testing anything useful and was causing spurious failures.  Under the
       conditions we've set up, the rational expectation would be for the
       file-creation helper program to succeed, but the test expected it to
       fail.
    
     * Removed Yet Another Unnecessary Sleep.
    
     * Reduced the number of files from 10K to 1K.  That's more than
       sufficient to test what we're trying to test, and saves significant
       time.
    
    Change-Id: If1c623853745ab42ce7d058d1009bbe1dcc1e985
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/13544
    Reviewed-by: Joseph Fernandes
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit a60c39de31e8258cb56d8db6bd8ec2491a942a4e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jan 19 10:45:22 2016 +0530

    glusterd: use string comparison for realpath checks in glusterd_is_brickpath_available
    
    glusterd_is_brickpath_available () used to call realpath() for checking the
    whether the new brick path matches with the existing ones. The problem with this
    is if the underlying file system is bad for any one of the existing bricks then
    realpath() would fail and we wouldn't allow to create the new brick even if it
    should be allowed.
    
    Fix is to use string comparison with having a new field real_path in brickinfo
    to store the absolute path
    
    Change-Id: I1250ea5345f00fca0f6128056ebd08750d604f0a
    BUG: 1299710
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13258
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1f673d141fb06282583175357348a7a2fc19e604
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Feb 25 21:30:33 2016 +0530

    protocol/client: Don't change op_ret when xdata_rsp is present
    
    Change-Id: Ia69cc420ad7b5766d513ea2715bbca50d8d57132
    BUG: 1312226
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13530
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 69af0676c9e55804338abe26b94138da15385747
Author: hari <hgowtham@redhat.com>
Date:   Thu Feb 18 16:58:28 2016 +0530

    TIER: avoid reset of ctr-enabled during the issue of gluster v reset
    
    Change-Id: I3f5f29378c8c55cc07a83f5fc1506c4d7e9ac09d
    BUG: 1309659
    Signed-off-by: hari <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13470
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: hari gowtham <hari.gowtham005@gmail.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3f78b6b3dc6376945a1b1a7c4af16103901ab746
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jan 22 16:59:53 2016 +0530

    snapshot: Fix parent volinfo corruption in snapshot restore
    
    Remove parent_volinfo irrespective of success or failure
    of glusterd_lvm_snapshot_remove(). This prevents the
    duplication of the volinfo after the execution of
    glusterd_snapshot_restore().
    
    When commit fails on originator node, we don't perform
    commit on the other nodes, as a result we don't have a
    backup of /var/lib/glusterd/vols/<volname> in the
    GLUSTERD_TRASH in other nodes. But in the postvalidate
    we try to restore from GLUSTED_TRASH and end up cleaning
    up /var/lib/glusterd/vols/<volname>. Hence moved
    glusterd_snapshot_backup_vol() from commit to prevalidate,
    so that the backup is always available when a cleanup is
    needed.
    
    Change-Id: Icd471b23faf02bad680b9a1aadc4a0175f7cce8b
    BUG: 1300979
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13282
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 87b19927ed41cfe47579c1c069cb6640fd47a732
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Feb 9 03:37:31 2016 +0000

    cluster/tier: make promotion and demotion independant
    
    Currently a main loop in tiering spawns promotion and demotion threads,
    and does a join to wait for them to complete. When one of the two
    threads takes a long time, the main thread waits for it
    before exiting the join. It may wait so long the scheduled time
    for the other thread is skipped. In the case of demotion, it may be
    a long time before another attempt. This patch fixes that by
    making the promotion and demotion activities independant. A side
    effect of this change is the logic is significantly simplified.
    
    Change-Id: I1196bd4bbfc95e8aa326a9bd4ebf395032369d1c
    BUG: 1306852
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/13433
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 368e26f454fe35477e46dc698fa6b8c3c608ea8d
Author: Sakshi <sabansal@redhat.com>
Date:   Tue May 26 09:53:55 2015 +0530

    glusterd: check if glusterd is started on all nodes and all
              bricks are started before performing rebalance
    
    Change-Id: I458ea9cd86cf35bdb7d758be55f951ae9f3e66f0
    BUG: 1224857
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/10906
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 15602865865386672bcb996dab8259d25b684900
Author: vmallika <vmallika@redhat.com>
Date:   Wed Feb 10 16:27:05 2016 +0530

    quota: heal object-limit on a root dir of a newly added brick
    
    When a new brick is added, xattr trusted.glusterfs.quota.limit-objects
    is not healed on a root directory.
    This patch will fix the problem
    
    Change-Id: I776609ebf4d7822c541b6262e63d465ea3a86db4
    BUG: 1306220
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13422
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 18612a7b2e005d76529f8c2a6149a6506f6daae6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jan 12 10:41:46 2016 +0530

    glusterd: display user.* options in volume get
    
    As of now volume get framework doesn't consider user.* xattrs to be displayed.
    This patch is to include them in volume get output. Please note these options will be
    only shown for a given volume name, 'all' as a volume name wouldn't consider them displaying.
    
    Change-Id: Ifc19e89c612e9254d760deaaef50bc1b4bfe02ce
    BUG: 1297638
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13222
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit dbf0ca53a5704c7f94257fc4223b41865458301a
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Thu Feb 4 16:02:59 2016 +0530

    dht: mkdir must unwind with latest ctime
    
    Currently fops like mkdir used the the ctime it gets
    after creating the directory entry. But setting layout
    also updates the ctime of a directory. Hence DHT must
    get the ctime after the setxattr call and unwind with
    the latest ctime to avoid mismatch in time seen by
    applications like tar.
    
    Change-Id: Iecbbe3aac5244af5da9788b48ccf299ca56b4bae
    BUG: 1302948
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13352
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d136a789258e8f600e536717da156a242d8ed9a5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Dec 2 19:37:55 2015 +0530

    geo-rep: Handling Rsync/Tar errors efficiently
    
    Geo-rep processes Changelogs in Batch, if one file in batch
    fails with rsync error that Changelog file is reprocessed multiple times.
    After MAX_RETRY, it logs all the GFIDs from that batch as Skipped.
    
    This patch addresses following issues,
    1. When Rsync/Tar fails do not parse Changelog again for retry
    2. When Rsync/Tar fails do not replay Entry operations, only retry
       rsync/tar for those GFIDs
    3. Log Error in Rsync/Tar only in the last Retry
    4. Do not log Skipped GFIDs since Rsync/Tar errors are logged for
       only failed files.
    5. Changed Entry failures as Error instead of Warning
    
    BUG: 1287723
    Change-Id: Ie134ce2572693056ab9b9008cd8aa5b5d87f7975
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/12856
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 656a0e64e5f465561ed29297421ec150de32f2a1
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Dec 29 11:20:39 2015 +0530

    geo-rep: Handle ERANGE error during listxattr
    
    llistxattr in Geo-rep is two syscall instead of one
    
    SIZE = llistxattr(PATH, &BUF, 0);
    BUF = create_buf(SIZE);
    _ = llistxattr(PATH, &BUF, SIZE);
    
    So if any new xattrs added just after first call by any other worker,
    second syscall will fail with ERANGE error.
    
    Now Geo-rep sends BUF with large size(256*100) and gets value
    with only one syscall. Raises OSError if fails with ERANGE error
    even after sending large BUF.
    
    Change-Id: I8ade4bbe9a0a8ea908ed9dedcd3f2ff4c6fe6f51
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1294588
    Reviewed-on: http://review.gluster.org/13106
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 1b897c39ba8c0f1bf180316637cc2d87e6920800
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Feb 19 17:08:56 2016 +0530

    tools/glusterfind: New option --no-encode
    
    New option added to skip encoding path in output file. Also handled
    Unicode strings.
    
    File paths can have newline characters, to differentiate between each
    path patch is encoded according to
    RFC3986(https://www.ietf.org/rfc/rfc3986.txt). Due to this consumer
    applications have to decode the path before consuming it. With this
    option Paths are not encoded, can be directly consumed by
    applications.
    
    Unicode encoding is handled automatically
    
    BUG: 1310080
    Change-Id: I83d59831997dbd1264b48e9b1aa732c7dfc700b5
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13477
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit bf2004bc1346890e69292c5177a5d8e002b696e2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jan 14 17:14:25 2016 +0530

    geo-rep: Mask xtime and stime xattrs
    
    Allow access to xtime and stime xattrs only
    to gsyncd client and mask them for the rest.
    
    This is to prevent afr from performing self
    healing on marker xtime and geo-rep stime
    xattr which is not expected as each of which
    gets updated them from backend brick and
    should not be healed.
    
    Change-Id: I24c30f3cfac636a55fd55be989f8db9f8ca10856
    BUG: 1296496
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13242
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 3f9632cd655f43fa66cca981b37cbfb09ab1d352
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Fri Jan 22 16:58:13 2016 +0530

    geo-rep: Handle hardlink in Tiering based volume
    
    Problem:
    Hardlinks are synced as Sticky bit files to Slave in
    a Tiering based volume.
    In a Tiering based volume, cold tier is hashed subvolume
    and geo-rep captures all namespace operations in cold tier.
    
    While syncing a file and its corresponding hardlink, it is
    recorded as MKNOD in cold tier(for both) and
    We end up creating two different files in Slave.
    
    Solution:
    If MKNOD with Sticky bit set is present, record it as LINK.
    This way it will create a HARDLINK if source file exists (on slave),
    else it will create a new file.
    
    This way, Slave can create Hardlink file itself (instead
    of creating a new file) in case of hardlink.
    
    Change-Id: Ic50dc6e64df9ed01799c30539a33daace0abe6d4
    BUG: 1301032
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13281
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit ab77dac7e9187063ac3086551e61d38a1967d337
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Dec 8 16:06:47 2015 +0530

    glusterd: set rpc conn flag in brick connect/disconnect
    
    Change-Id: I1a7b23db8f196616be338baeb8f7f56572a05c90
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12908
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 5a9233ee37a10456a9f8f3c792cab37462f64098
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Feb 25 20:36:11 2016 +0530

    tests/glusterd: Parse the new time format
    
    A recent change in cli changed elapsed time format
    that broke a test.
    
    This patch will fix the issue with parsing.
    
    Change-Id: I9a4a4b28f654cf2ac223e25abfc9df6570607d74
    BUG: 1312036
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13524
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 025eebecefa45c8a3e6eb33fe382dd701ac9c28a
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Jan 18 14:44:46 2016 +0530

    vagrant-test: Provide option to autostart vm on host boot
    
    If the machines are being used as test machines for active development,
    user might want to have them autostart on host boot. You can use -a as
    short option or --autostart as longoption with run-tests-in-vagrant.sh
    to set the autostart flag on the VM. The autostart value is set to off
    by default.
    
    It is done using virsh until vagrant-libvirt supports it in the API.
    
    Change-Id: I5b53ea6d850c991d548dbac0bb8fadd528cabf41
    BUG: 1291537
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13252
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit e991d14a3a2aaf19218cbb5993a94de263769cb4
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Jan 22 12:08:52 2016 +0530

    vagrant-test: Install helper packages
    
    It is useful to have helper packages like gdb, sysstat, valgrind
    installed on the dev machines. The pre-baked box that was merged in
    commit e29bf0b1f102308f114e04421d80696eebfbf6e3 has those packages
    installed.
    
    This patch updates the list of packages installed in the install-pkgs
    role for future reference.
    
    Change-Id: I2ee25d40708a4d29652b5bd40b66e3b1fcd33f0c
    BUG: 1291537
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13458
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit e410c3a0c97a7bfe109badba5b6a5dd094016995
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Jul 10 12:40:24 2015 +0530

    locks: Handle negative values for flock->l_len
    
    As per 'man 3 fcntl',
    "If l_len is positive, the area affected shall start at
    l_start and end at l_start+l_len−1. If l_len is negative,
    the area affected shall start at l_start+l_len and end at
    l_start−1. Locks may start and extend beyond the current
    end of a file, but shall not extend before the beginning
    of the file."
    
    Currently we return EINVAL if l_len is found to be negative.
    Fixed the same as mentioned in the man page.
    
    Change-Id: I493ce202c543185fc4ae7266d1aaf9d7e2a66991
    BUG: 1241104
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11613
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5bfd22123753fb88c1a2ea91ffd4f6767d89f278
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Dec 31 13:53:54 2015 +0530

    inode: Retire the inodes from the lru list in inode_table_destroy
    
    Inodes from the lru list are not moved to purge list unless they
    are retired. Also process the lru list first to unset their parent
    as we need to unset their dentry entries (the ones which may not be
    unset during '__inode_passivate' as they were hashed) which in turn
    shall unref their parent inodes which could be in active list.
    
    These parent inodes when unref'ed may well again fall into lru list
    and if we are at the end of traversing the list, we may miss to
    delete/retire that entry. Hence traverse the lru list till it
    gets empty.
    
    Change-Id: Ib7666e235e9b9644144a7c7933afb5e407e506ca
    BUG: 1295107
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13125
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b7d01547dad88aeebc8cc2dbd68839885615bd66
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Mon Feb 8 12:14:12 2016 +0530

    dht: cleanup dict and free memory in rename code path
    
    Change-Id: I2458e18197bdf7565563a85e9021b5b2850c1825
    BUG: 1303945
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13392
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 77245bcbf02754dec832ca34a9138bade2c9cfa3
Author: Sakshi <sabansal@redhat.com>
Date:   Tue May 5 10:55:56 2015 +0530

    cli: output of rebalance to show run time in proper format
    
    Change-Id: I775f13c8046dd2aeb9d4b86a737dcebb396778b4
    BUG: 1223625
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/10544
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6209e227f86025ff9591d78e69c4758b62271a04
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Thu Jan 7 13:09:58 2016 +0530

    tests: remove-brick commit getting executed before migration has completed
    
    Remove brick commit will fail when it is executed while rebalance is in
    progress. Hence added a rebalance timeout check before remove-brick commit to
    enusre that rebalance has completed.
    
    Change-Id: Ic12f97cbba417ce8cddb35ae973f2bc9bde0fc80
    BUG: 1225716
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13191
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit e38bf1bdeda3c7a89be3193ad62a72b9139358dd
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Wed Dec 9 20:12:17 2015 +0530

    glusterd: fixing few memory leak in glusterd
    
    Current glusterd code base having memory leak. This is because of
    memory allocate by dict_allocate_and_serialize function in
    "gd_syncop_mgmt_v3_lock" and "gd_syncop_mgmt_v3_unlock"
    function is not freeing up meory upon exit.
    
    Fix is to free the memory after exit of the above function.
    
    Thanx Carlos and Roman for finding out the issue and fix.
    
    Change-Id: Id67aa794c84969830ca7ea8c2374f80c64d7a639
    BUG: 1287517
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Signed-off-by: Carlos Chinea <carlos.chinea@nokia.com>
    Signed-off-by: Roman Tereshonkov <roman.tereshonkov@nokia.com>
    Reviewed-on: http://review.gluster.org/12927
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8cf29a4207c162be8e2993ae36f49090851cbbfc
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Feb 16 18:50:23 2016 +0530

    rpc: Fix for rpc_transport_t leak
    
    The transport object needs to get unref'ed when the rpc clnt
    object is getting destroyed. But currently in rpc_clnt_disable()
    we set conn->trans to NULL before it gets unref'ed leading to
    transport object leak.
    
    This change is to fix it by setting conn-tran to NULL only when
    it is being unref'ed.
    
    Change-Id: I79ba34e28ae19eb616035f36bbed1c2f47875b94
    BUG: 1295107
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13456
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit db747eba347e2909f4fb4fc28a67adb8f188586a
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Feb 8 22:33:56 2016 +0530

    gfapi: Use inode_forget in case of handle objects
    
    Currently with gfapi, even if applications release their
    reference on paritular inode entries, those entries never
    get destroyed as they shall always have positive nlookup
    count unless inode_table exceeds lru limit.
    
    Since inodes and their contexts can consume considerable
    amount of memory, applications may end up consuming lot of
    memory and may even get OOM killed.
    
    To avoid that, have considered below approaches (for handle based access)-
    a) Do 'inode_lookup' only if the corresponding inode is created
    for the first time and forget it during close of the handle
    
    This shall not work as multiple handle objects can refer to
    same inode entry and inode_forget from second handle object
    onwards shall result in assert.
    
    b) Do 'inode_lookup' during a handle or fd creation
    
    But this approach shall affect the performance of the fops which
    operate on neither handle nor fd.
    
    c) current approach taken-
    Applications using glfs handle objects hold a reference
    on corresponding inode entries. Hence it is safe to forget
    those inodes and make nlookup count to '0' while trying to
    delete those handle objects. That way the last unref (i.e,
    from the last handle close) shall result in inode_destroy().
    
    Change-Id: Id2c7ab178894a10c0030c143ba71e7813df8d18c
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    BUG: 1295107
    Reviewed-on: http://review.gluster.org/13096
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit dcb13de77d0ac056b588f3eb7414e33afeeb3629
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Feb 23 18:27:09 2016 +0530

    gfapi: Add xlator_cbks fops in gfapi
    
    Change-Id: I1fe5dd757e65206f92e0a867b43b49a3c0f2d4cf
    BUG: 1311124
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13499
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 730ea2ca509a5bea05726090cd1e4cb67f040b7c
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Feb 23 18:10:36 2016 +0530

    libglusterfs: Change log-level to DEBUG for default_* fops()
    
    Change-Id: I7087476bbc00cd23ba65ea119bc0fe8a9bff347d
    BUG: 1311124
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13498
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit f3c48b4a729a56ad6e6d9b2ac0b08ce1ec0f3fc3
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Mon Feb 22 17:20:58 2016 +0530

    gfapi : Avoid double freeing of dict in glfs_*_*getxattr
    
    The dict variable "xattr" is passed to glfs_getxattr_process() and
    glfs_listxattr_process() in glfs_*_*getxattrs(). This variable is
    unrefed by both functions and again in caller function which may
    result in segfault. So it is wrong to call dict_unref() in both
    glfs_*xattr_process functions.
    
    Change-Id: I227f55ebc3169f58910863c04ae536a8d789e80e
    BUG: 1247603
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13483
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit ec6eb8200e41dadc623fd2341a3c5cf8cc71dec7
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Feb 22 11:02:31 2016 -0500

    glusterd: coverity warning in glusted_copy_nfs_ganesha_file()
    
    fix unused return value from snprintf.
    
    Also minor cleanup, including safe handling of truncated output by
    snprintf.
    
    Change-Id: Ibec8c7e6cc4ef07b6535d01a0719359fa3ef8030
    BUG: 1310755
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13486
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 0bc54f3ea7a56040df4a67b8626200b47fa3d779
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Mon Feb 22 16:50:12 2016 +0530

    gfapi : fixing listxattr call for handle ops
    
    Currently listxattr is called as part of glfs_h_getxattrs() when NULL is
    passed to name field, but glfs_h_getxattrs_common() inside it will error
    out if name is NULL. Therefore listxattr is broken for handle ops.
    
    Change-Id: I9ced6e33525e1e1a50298972e4922c954fc2b223
    BUG: 1310620
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13482
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 3ca140f011faa9d92a4b3889607fefa33ae6de76
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Jan 30 08:47:35 2016 +0530

    glusterd: set decommission_is_in_progress flag for inprogress remove-brick op on glusterd restart
    
    While remove brick is in progress, if glusterd is restarted since decommission
    flag is not persisted in the store the same value is not retained back resulting
    in glusterd not blocking remove brick commit when rebalance is already in
    progress.
    
    Change-Id: Ibbf12f3792d65ab1293fad1e368568be141a1cd6
    BUG: 1303269
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13323
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>

commit a67331f3f79e827ffa4f7a547f6898e12407bbf9
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Jan 29 16:24:02 2016 +0530

    glusterd/rebalance: initialize defrag variable after glusterd restart
    
    During reblance restart after glusterd restarted, we are not
    connecting to rebalance process from glusterd, because the
    defrag variable in volinfo will be null.
    
    Initializing the variable will connect the rpc
    
    Change-Id: Id820cad6a3634a9fc976427fbe1c45844d3d4b9b
    BUG: 1303028
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13319
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 1fd7655ab0795e5aa96cdbfb8c522b222734f4f2
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Mar 12 12:09:06 2015 +0530

    Snapshot:wrong logging is used
    
    Change-Id: I56e5f5696fbbb4290f95adb9b68f9e43ed037ed3
    BUG: 1189473
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9861
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 27c09b9357004e5fdb02fdf0c586f3402878db1f
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Jun 30 11:26:54 2014 +0530

    socket: reduce rate of readv failure logs due to disconnect
    
    ... by using GF_LOG_OCCASIONALLY
    
    Change-Id: I779ff32ead13c8bb446a57b5baccf068ae992df1
    BUG: 1114847
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8210
    Tested-by: Atin Mukherjee <amukherj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 663d1a5eed5a8aef6cfad4710e16d21740bf0da8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Feb 11 15:37:08 2016 +0530

    rpc : build_prog_details should iterate program list inside critical section
    
    While I was analyzing a glusterd crash from free_prog_details, a code
    walkthrough detects that we iterate over the rpc svc program list without been
    inside the criticial section. This opens up a possibility of a crash when there
    is a concurrent writer updating the same list. Solution is to read the list
    inside lock.
    
    Change-Id: Ib4b4b0022a9535e139cd3c00574aab23f07aa9d2
    BUG: 1306560
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13428
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 62db11fa017004aa6cb1d91ec6b0117ac3e96a13
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Mon Feb 15 10:48:18 2016 +0530

    glusterd: volume should not start when server quorum is not met
    
    Currently when server quorum is not met then upon executing
     # gluster volume start [force] command its starting the volume.
    
    With this patch if server side quorum is not met then it will
    prevent starting of the volume.
    
    Change-Id: I39734b2dcf8e90c3c68bf2762d8350aecc82cc38
    BUG: 1308402
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/13442
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit f02dc88786afea06e6b064a724803c82a0af90ba
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Fri Feb 5 14:51:10 2016 +0530

    dht: file rename must take blocking inode locks
    
    Currently DHT takes non-blocking locks for file rename.
    Due to this during parallel renames some clients fail
    with EBUSY or ESTALE errors. Hence to avoid application
    discontinuity file rename must take blocking inode locks.
    
    Change-Id: I986e9d08b3be359f20b1a3e1564e049b0f3dffd3
    BUG: 1304966
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13366
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 46bd29e0f2a7fc9278068a06d12066d614f365ec
Author: Nithin D <nithind1988@yahoo.in>
Date:   Sun Nov 15 22:14:43 2015 +0530

    glusterd: Bug fixes for IPv6 support
    
    Problem:
    Glusterd not working using ipv6 transport. The idea is with proper glusterd.vol configuration,
    1. glusterd needs to listen on default port (240007) as IPv6 TCP listner.
    2. Volume creation/deletion/mounting/add-bricks/delete-bricks/peer-probe
       needs to work using ipv6 addresses.
    3. Bricks needs to listen on ipv6 addresses.
    All the above functionality is needed to say that glusterd supports ipv6 transport and this is broken.
    
    Fix:
    When "option transport.address-family inet6" option is present in glusterd.vol
    file, it is made sure that glusterd creates listeners using ipv6 sockets only and also the same information is saved
    inside brick volume files used by glusterfsd brick process when they are starting.
    
    Tests Run:
    Regression tests using ./run-tests.sh
        IPv4: Ran manually till tests/basic/rpm.t .
        IPv6: (Need to add the above mentioned config and also add an entry for "hostname ::1" in /etc/hosts)
            Started failing at ./tests/basic/glusterd/arbiter-volume-probe.t and ran successfully till here
    
    Unit Tests using Ipv6
        peer probe
        add-bricks
        remove-bricks
        create volume
        replace-bricks
        start volume
        stop volume
        delete volume
    
    Change-Id: Iebc96e6cce748b5924ce5da17b0114600ec70a6e
    BUG: 1117886
    Signed-off-by: Nithin D <nithind1988@yahoo.in>
    Reviewed-on: http://review.gluster.org/11988
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 759b63536c676f4b4fa135ea62d74dff021778e4
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Jan 27 12:59:58 2016 +0530

    build: make /var/run/gluster available everywhere
    
    /var/run/gluster was only avialable with glusterfs-server package.
    Move it to primary glusterfs package so that client installations as
    well as server installations can generate state-dump in that directory.
    
    Change-Id: I1cdd2c5118ac657b2dab4f9669c6657484b8c600
    BUG: 1302200
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/13296
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit a47d1bf91bfc8e9dcd35c2d3019e8e98dd4a7f83
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue Feb 16 17:29:31 2016 +0530

    build: fix broken build
    
    fix broken build introduced in
    commit "c458433041aafb48ae6d6e5fcf3e1e737dc3fda3"
    
    issue:
    
    $ make
      CC       libglusterfs_la-y.tab.lo
      gcc: error: ./y.tab.c: No such file or directory
      gcc: fatal error: no input files
      compilation terminated
    
    Change-Id: I9632444e733812d633960b15a4dbc7d299d2f44b
    BUG: 1308900
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/13455
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bfe689d25ecde567a90135b47f31b89d7714aaf4
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Feb 10 15:02:48 2016 +0530

    glusterd/snapshot : Remove stale pmap registry entry
    
    Perform a pmap_registry_remove on a stale registry
    entry from the previous run of snapd, which makes the
    query callback always return the older port number.
    
    Change-Id: I7fc504d2b09d32a9c945ec2c33e0e092a0d186ec
    BUG: 1306193
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13420
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit d7e052ee24b3e09f2e76c2fdb980e33e74d2a855
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jan 22 12:11:18 2016 +0530

    geo-rep: Script to Schedule Geo-replication
    
    This script can be used to run Geo-replication when required. can be
    scheduled using cron job to run Geo-replication.
    
    This script does the following,
      1. Stop Geo-replication if Started
      2. Start Geo-replication
      3. Set Checkpoint
      4. Check the Status and see Checkpoint is Complete.(LOOP)
      5. If checkpoint complete, Stop Geo-replication
    
    Usage:
        python /usr/share/glusterfs/scripts/schedule_georep.py <MASTERVOL> \
                 <SLAVEHOST> <SLAVEVOL>
    
    For example,
        python /usr/share/glusterfs/scripts/schedule_georep.py gv1 fvm1 gv2
    
    To schedule the Geo-replication to run once in a day using cron,
       # Run daily at 08:30pm
       30 20 * * * root python /usr/share/glusterfs/scripts/schedule_georep.py \
          --no-color gv1 fvm1 gv2 >> /var/log/glusterfs/schedule_georep.log 2>&1
    
    BUG: 1300956
    Change-Id: I6b1e2ddbf7fc09ef621499b57ae230fd4dbbd9a6
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13279
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit f4282bd927e2e0d826d62cf1192102382c5697b2
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Dec 14 17:52:37 2015 +0530

    Upcall/cache-invalidation: Use parent stbuf while updating parent entry
    
    For *create*  fops (CREATE, MKDIR, MKNOD), we invalidate the parent
    entry. Hence send parent attributes in the stat field.
    
    Also "UP_PARENT_DENTRY_FLAGS" has to be set only for the fops which shall
    result in two invalidations requests - one for the inode on which fop is
    being performed and another on parent entry.
    
    In case of CREATE/MKDIR/MKNOD fops, there shall be only one invalidation
    request sent, that too on parent inode. We send invalidation directly on
    parent inode's gfid. So there is no necessity to set these flags which
    when set shall endup invalidating the parent's parent entry.
    
    Change-Id: I7514ee08382081e3e060818ede497dbca26987dc
    BUG: 1291259
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/12962
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 888efdf5e0ab7d22c3fc227dc0dbfaec91b1d5d9
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Wed Jan 20 09:31:00 2016 +0530

    glusterfsd: destroy frame after rebalance callback has completed
    
    Rebalance after sending a status notification immediately
    destroys the frame. Now in its callback the frame is corrupted.
    Rebalance crashes when this corrupted frame is accessed. To avoid
    this we must destroy the frame after the callback is completed.
    
    Change-Id: If383017a61f09275256e51c44a1efa28feace87b
    BUG: 1300152
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/13262
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5858b2b1b568f253dbee818d4017f4c0fb642ae4
Author: Prashanth Pai <ppai@redhat.com>
Date:   Thu Feb 11 18:54:41 2016 +0530

    Mark slowest tests in regression test output
    
    Recording of elapsed time is only accurate to the second. This should
    be okay. Some *BSD systems may not have '%N' support in date command.
    
    Change-Id: I81e887c4783b052317922f3a4af37ec3676fb67d
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/13430
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit d4c415776b20e4152d4a706276cb06d833a58baa
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Sat Dec 19 20:27:17 2015 -0500

    all: fixes for clang compile warnings
    
    cli/src/cli-cmd-parser.c (chenk)
    cli/src/cli-xml-output.c (spandit)
    cli/src/cli.c (chenk)
    libglusterfs/src/common-utils.c (vmallika)
    libglusterfs/src/gfdb/gfdb_sqlite3.c (jfernand +1)
    rpc/rpc-transport/socket/src/socket.c (?)
    xlators/cluster/afr/src/afr-transaction.c (?)
    xlators/cluster/dht/src/dht-common.h (srangana +2)
    xlators/cluster/dht/src/dht-selfheal.c (srangana +2)
    xlators/debug/io-stats/src/io-stats.c (R. Wareing)
    xlators/features/barrier/src/barrier.c (vshastry)
    xlators/features/bit-rot/src/bitd/bit-rot-scrub.h (vshankar +1)
    xlators/features/shard/src/shard.c (kdhananj +1)
    xlators/mgmt/glusterd/src/glusterd-ganesha.c (skoduri)
    xlators/mgmt/glusterd/src/glusterd-handler.c (atinmu)
    xlators/mgmt/glusterd/src/glusterd-op-sm.h (atinmu)
    xlators/mgmt/glusterd/src/glusterd-snapshot.c (spandit)
    xlators/mgmt/glusterd/src/glusterd-syncop.c (atinmu)
    xlators/mgmt/glusterd/src/glusterd-volgen.c (atinmu)
    xlators/protocol/client/src/client-messages.h (mselvaga +1)
    xlators/storage/bd/src/bd-helper.c (M. Mohan Kumar)
    xlators/storage/bd/src/bd.c (M. Mohan Kumar)
    xlators/storage/posix/src/posix.c (nbalacha +1)
    
    Change-Id: I85934fbcaf485932136ef3acd206f6ebecde61dd
    BUG: 1293133
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13031
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 62f9659554c07317c9d06251b74171d9eac0917e
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Fri Dec 18 15:21:27 2015 -0500

    all: fix various cppcheck warnings
    
    fixes for various warnings reported by cppcheck
    
    N.B. cppcheck output is in the bugzilla
    
    Change-Id: I33acec127bc4536935fdd8d52a0c490ec54d50b2
    BUG: 1292954
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13006
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 954f2901345f42177033418112c052ed0795b295
Author: vmallika <vmallika@redhat.com>
Date:   Tue Feb 2 12:30:16 2016 +0530

    USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled
    
    If there is a .snaps directory pre-exists and when USS is enabled,
    it should not be listed with 'ls -a'
    
    Change-Id: I1c43e2decc0bbbd3213b190b675e3a32d04b22d3
    BUG: 1303828
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13330
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit bfd8f92490454f261330da34565334ed5decd0e1
Author: N Balachandran <nbalacha@redhat.com>
Date:   Sat Feb 13 10:02:55 2016 +0530

    cluster/dht: Skip subvols if no layout present
    
    Running "rm -rf" on a tiered volume sometimes caused
    the client to crash because dht_readdirp_cbk referenced
    a NULL layout for the hot tier subvol.
    Now, entries are skipped if the layout is NULL. This
    can cause "rm -rf" to fail with ENOTEMPTY rmdir failures.
    
    Change-Id: Idd71a9d0f7ee712899cc7113bbf2cd3dcb25808b
    BUG: 1307208
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13440
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c458433041aafb48ae6d6e5fcf3e1e737dc3fda3
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Feb 8 13:30:49 2016 -0500

    experimental: add fdl (Full Data Logging) translator
    
    NSR needs logging that is different than our existing changelog in
    several ways:
    
     * Full data, not just metadata
    
     * Pre-op, not post-op
    
     * High performance
    
     * Supports the concept of time-bounded "terms"
    
    Others (for example EC) might need the same thing.  This patch adds such
    a translator.  It also adds code to dump the resulting journals, and to replay
    them using syncops, plus (very rudimentary) tests for all of the above.
    
    Change-Id: I29680a1b4e0a9e7d5a8497fef302c46434b86636
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/12450
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit da33097c3d6492e3b468b4347e47c70828fb4320
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jan 18 12:16:31 2016 +0000

    cli/ afr: op_ret for index heal launch
    
    Problem:
    If index heal is launched when some of the bricks are down, glustershd of that
    node sends a -1 op_ret to glusterd which eventually propagates it to the CLI.
    Also, glusterd sometimes sends an err_str and sometimes not (depending on the
    failure happening in the brick-op phase or commit-op phase). So the message that
    gets displayed varies in each case:
    
    "Launching heal operation to perform index self heal on volume testvol has been
    unsuccessful"
                    (OR)
    "Commit failed on <host>. Please check log file for details."
    
    Fix:
    1. Modify afr_xl_op() to return -1 even if index healing of atleast one brick
    fails.
    2. Ignore glusterd's error string in gf_cli_heal_volume_cbk and print a more
    meaningful message.
    
    The patch also fixes a bug in glusterfs_handle_translator_op() where if we
    encounter an error in notify of one xlator, we break out of the loop instead of
    sending the notify to other xlators.
    
    Change-Id: I957f6c4b4d0a45453ffd5488e425cab5a3e0acca
    BUG: 1302291
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13303
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e29bf0b1f102308f114e04421d80696eebfbf6e3
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Jan 18 15:06:18 2016 +0530

    vagrant-test: Use pre-baked box for better perf
    
    Using Fedora cloud base leads to lot of downloading
    time for packages and also it is larger in disk size
    once imported into linux.
    
    Change-Id: I2e878e7cb29a79ade4d6e517075ab523062deb53
    BUG: 1291537
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13251
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 55617ef037695f47ead1c1b753678402e1545f8c
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Dec 10 10:30:32 2015 -0500

    NSR : nsr server code generation patch
    
    The NSR-server with this patch, appoints the first node
    on every replica subvolume, as the leader for that subvolume.
    On receiving a 'write' fop, the leader first checks if there is
    quorum in the replica subvolume to proceeed. In case there isn't
    it fails with EROFS.
    
    If there is quorum, the leader forwards the fop to the
    followers. The followers on receiving the fop, perform the
    operation, and based on the success or failure of the outcome
    send a +ve or a -ve ack to the leader.
    
    The leader after receiving acks from the followers performs a
    quorum check of the acks, to see if it should even try to perform
    the fop. If quorum is not being met, and the leader's outcome
    wouldn't affect quorum, then it would send -ve ack to the client
    without even performing the fop. If quorum is being met, the leader
    will then try the fop on itself, and based on it's outcome perform
    a quorum check of all the acks received (this time, including it's
    own). Based on the result of the quorum check (irrespective of the
    outcome on the leader), a +ve or -ve ack is send back to the client.
    
    Change-Id: I860654b74c53e9b139b37dba43848e5504df6dce
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12705
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 320779d53ae013147d5e2556d2946c73e45734ab
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 10 15:28:39 2016 +0530

    heal: Remove sleep()
    
    I wrote this program from a sample gfapi program which had sleep.
    I am not sure why this sleep was needed. So removing it now.
    
    Changed tests/bugs/replicate/bug-1190069-afr-stale-index-entries.t
    to execute count_sh_entries every second, instead of comparing
    same value over and over.
    
    Change-Id: I7b89d6cab3e50bb7bf4d40a6064f2d8734155bea
    BUG: 1306199
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13421
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 095e2c48271a5248c8711a4e6a34bcb4d44c440e
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Feb 10 17:08:26 2016 +0530

    api: glfs_lseek must return repositioned offset for SEEK_SET, SEEK_CUR flags
    
    On success, glfs_lseek() API is responsible for providing the
    repositioned offset as its return value. But for SEEK_SET and
    SEEK_CUR flags, glfs_lseek() returns -1 on successfully
    repositioning the fd offset. Current change is to set ret to
    0 after glfd->offset is modified correctly so as to return the
    correct offset.
    
    Change-Id: I94d582779a98074cf633289f4b60b3c6a04e4f18
    BUG: 1306264
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/13423
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 444378de64f398c4e19468e83ac31fccc0a94800
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Feb 4 18:24:55 2016 +0530

    cluster/tier : Fixed wrong variable comparison
    
    The wrong variable was being checked to determine
    the watermark value.
    
    Change-Id: If4c97fa70b772187f1fcbdf5193e077cb356a8b1
    BUG: 1303895
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13357
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit e501a7da4c50e2a2049a71119c25ed43b43f3395
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jul 6 00:01:44 2015 +0200

    fuse: add support for SEEK_HOLE and SEEK_DATA through lseek()
    
    The Linux FUSE kernel module has gained support for passing SEEK_HOLE
    and SEEK_DATA on through lseek(). This can greatly improve performance
    when working with sparse files.
    
    Linux FUSE introduced support for lseek() with version 4.5. The commit
    in mainline Linux is 0b5da8db145bfd44266ac964a2636a0cf8d7c286.
    
    URL: http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/14752
    Change-Id: I12496d788e59461a3023ddd30e0ea3179007f77e
    BUG: 1220173
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11474
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b8bd9a6e6e3f50ede4c25dcfc0a05aad53e66c79
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Fri Feb 5 12:17:22 2016 +0530

    quota: Fix incorrect disk usage shown on a tiered volume
    
    When quota is enabled on a tiered volume, incorrect data usage is
    shown, it is because, during the process of migrating files in tiering,
    we are accounting both for the src file and dst file at some point. By the
    time we make the srcfile as a T file, marker has already accounted the
    contri and has updated it's parent and also we are not accounting for the
    truncate operation done, which accounts to incorrect data usage even after
    unlinking the file. The size can increase drastically with multiple promotes
    and demotes since the contri keeps changing and the parent is being updated.
    
    Change-Id: Ie567228786713d7dc257ff374a69ad3be40f9e82
    BUG: 1304970
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/13363
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 88d772c05c45c467bfccebfc51f6a0e0ea9ca287
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Feb 2 04:22:04 2016 +0530

    libgfapi: glfd close is not correctly handled for async fop
    
    There is chance that before the async fop is complete client can send
    a close. libgfapi destroys glfd on close. Therefore it can lead to
    crash or unexpected behaviour when the pening fop reaches libgfapi
    layer. Currently we don't provide any api to cancel these outstanding
    fops neither we check if the glfd is already closed or not.
    
    Therefore as a fix provided refcount for glfd. Each fop (sync or async)
    will take a ref and once the fop is complete it will unref the refcount.
    We should not call the registered callback function if glfd is already
    closed. To achieve this we maintain state of glfd so that we can safely
    take a call if the fd is closed or not.
    
    Change-Id: Ibe71b2225312db3f1be66b244fcf8826c70c357d
    BUG: 1303995
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/13340
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit acfb402414ec4a9ab8c9f9d4fead6b9141c2e934
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Jan 27 14:56:33 2016 +0530

    dht/quota : heal the limit_objects_key xattr needed for inode-quota
    
    Whenever a new brick is added, quota related xattr's
    should be healed but currently, the xattr
    "quota.limit-objects.<suffix>" needed for inode-quota is
    not being healed.
    The patch fixes this issue.
    
    Change-Id: I1e7b229126f7b058642bbc3fb5c109bfd8925325
    BUG: 1302257
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/13299
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 4b725f2576b06a739e159981c6124118e26ccfbd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 21 16:59:15 2015 +0200

    posix: implement seek() FOP
    
    The only lseek() options we need are SEEK_HOLE and SEEK_DATA.
    
    Change-Id: I5d15533c53fd710497f97c3cb4a8ea29fba47271
    BUG: 1220173
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11484
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 32935246bf884760800029cb20627ea94a865cee
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Thu Jan 28 12:35:40 2016 +0530

    cli/quota : quota is not enforcing when limit is set to 0
    
    When limit value is set to 0, quota assumes that limit is not
    set and is not enforcing currently. The patch fixes this issue by
    restricting the user from setting limit value = 0.
    
    Change-Id: I316653165cd9766600f95b5f23e5b8abcc2b41e7
    BUG: 1302554
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/13309
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 5e65701f2660d1be101da81bffea7721d4f9ece0
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Nov 20 16:46:31 2015 +0530

    build: Filter -D_FORTIFY_SOURCE from CFLAGS
    
    We use python-config to get recommended CFLAGS. It provides
    -D_FORTIFY_SOURCE=2 by default that conflicts with our
    --enable-debug option or a developer provided no-optimization option.
    Hence, filter it out from default CFLAGS.
    
    Change-Id: Id80196baeb55415b1ea334e7b17143e56dfbadb3
    BUG: 1283948
    Co-authored-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12707
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b72172f4516ff5627f15168213a54b171463803f
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Mon Feb 1 11:02:37 2016 +0530

    access-control : remove spurious error message from the posix_setxattr_cbk
    
    A check for dictionary is required before calling handling_other_acl_related_xattr()
    in posix_setxattr_cbk(). Otherwise following message will be poped up on every settxattr
    call.
    
    [2016-01-31 17:38:48.027792] I [dict.c:473:dict_get]
     (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/system/posix-acl.so
    (posix_acl_setxattr_cbk+0x26) [0x7f2334c5c166] -->
    /usr/lib/x86_64-linux-gnu/glusterfs/3.7.6/xlator/system/posix-acl.so
    (handling_other_acl_related_xattr+0xb0) [0x7f2334c5c0f0]
    -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(dict_get+0x93)
    [0x7f233c04b0c3] ) 0-dict: !this ||
    key=system.posix_acl_default [Invalid argument]
    
    Change-Id: I93f7e0f764c94dce38bdde95a68341f69a52122d
    BUG: 1303501
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13325
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1f3df9f1e028f6bf978004d7f1d82fe32f6975c9
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Dec 9 14:19:00 2015 -0500

    NSR: nsr client code generation patch
    
    This version of the client checks if the error returned
    is EREMOTE or ENOTCONN, and if not unwnds the error back
    
    In case of a EREMOTE or ENOTCONN error, it retries on
    all the bricks in the replica subgroup, and if the error
    still persists, it waits for a sec before going through the
    same exercise again.
    
    Change-Id: I916bed32f0820f381dd60fdde3d05b71c69a34dc
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12388
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 501a31eadbce8cfe9ec0ed149bafc8fa6460ff9a
Author: vmallika <vmallika@redhat.com>
Date:   Wed Feb 3 14:32:17 2016 +0530

    uss: validate USS option features.snapshot-directory
    
    USS option features.snapshot-directory
       contains only 'alphanum, -, _, .'
       starts with dot (.)
       value cannot exceed 255 characters
    and throws error for any other argument.
    
    Change-Id: Iad64635206ddf5599351020d99aafb3dd9d17bc1
    BUG: 1168819
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9209
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 12fbcd22d80be9cdd7e60341a173741d1d00f711
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Feb 4 12:07:36 2016 +0530

    cluster/ec: Automate heal for replace brick
    
    Problem:
    After a replace brick command, newly added
    brick does not contain data which existed
    on old brick.
    
    Solution:
    Do getxattr after initialization of all the
    bricks. This will trigger heal for brick root
    as soon as it finds the version mismatch on
    newly added brick.
    
    Removing tests from ec-new-entry.t which were
    required to simulate automation of heal after
    replace brick.
    
    Change-Id: I08e3dfa565374097f6c08856325ea77727437e11
    BUG: 1304686
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13353
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit dd8306b2f2e38f5de1386461d7f33ac0b64f2886
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Dec 24 14:29:33 2015 +0530

    performance/open-behind: Fix fdctx dump NULL dereference
    
    Also printing flags correctly in statedump now
    
    Change-Id: Ibfdd74aab5643ecc47d0a88f109d5d1050685f5a
    BUG: 1294051
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13076
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6608b5cc1f9d01261b767c3abae212c6222e6ba6
Author: vmallika <vmallika@redhat.com>
Date:   Tue Dec 29 17:35:30 2015 +0530

    quota: fix quota hook script for add-brick
    
    Hook script should not call any CLI commands
    as this can cause parallel operation problem,
    so remove quota list command from the script
    
    Change-Id: I76a364133403371b172e063abd5f742075b20a2f
    BUG: 1294637
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13110
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit fac8038a9fa80e16b557d91b9e2fec271cfda5fa
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Dec 14 16:25:22 2015 -0500

    NSR: Volgen Support
    
    Allows the user to convert an afr-volume to a nsr-volume
    by using cluster.nsr option in the volume set command
    
    gluster volume set <volname> cluster.nsr <on/off>
    
    Change-Id: Ia1c5aa89d27535f7275d474cf312dc5efb8e222f
    BUG: 1158654
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/12943
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit b28a1d8e54d70deca14efa49da1781e29ce8eb51
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Feb 2 19:28:49 2016 +0530

    Allow builds with older version of URCU
    
    Debian Wheezy, which has urcu-0.6 doesn't ship the pkg-config files for
    urcu. So when I was checking support, I didn't bother testing Wheezy or
    urcu-0.6 as I didn't want to spend time trying to build without
    pkg-config support.
    
    But it turns out that urcu-0.6 supports the APIs being used by GlusterD.
    This patch improves the configure script to manually search and set URCU
    build flags if pkg-config search fails.
    
    Change-Id: I8c2ae748b58e94d89aef61da6fb3c660710a5f3b
    BUG: 1304348
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/13345
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 95597b87e32b8615ca63f8b0b3bb8d488272d95d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jan 22 12:11:40 2016 +0530

    cluster/ec: Never return -ve state
    
    Ec manager shouldn't return -ve states, but it is, fixed that.
    
    Change-Id: I3f97c6ba2dbf9da724e8e1ee9b2c9da73f40013d
    BUG: 1300929
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13278
    Tested-by: Xavier Hernandez <xhernandez@datalab.es>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 39dd62c09cb6f5ac0f7f8c3b054d1187f0131efe
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Feb 3 15:14:13 2016 +0530

    tests: Move self-heald.t to bad tests
    
    Change-Id: I49d8f1b9668029d2b8bd35b366b673d7a08a057f
    BUG: 1304301
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13344
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit aeaba5858f4ec1dbea28450bae33c421c750f64a
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Feb 4 18:18:15 2016 +0530

    tests: Cosmetic changes to make results look better
    
    Change-Id: I39116bdca1db3a02bb018af245055fbf8279671d
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13356
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit c18741aa2f86907c0dcd7c455f905a97e9d20162
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Feb 4 14:32:12 2016 +0530

    tests: Add option to disable exit on failure
    
    By default run-tests.sh will quit after any test
    fails. If the user is interested to run all the
    tests then he/she will have to use the
    -c option.
    
    Change-Id: I99a0aafee280325114205b30ab3fd199978b28bb
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13350
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 6d9a976e53136dd4acc3fb33384035af77dae24c
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 2 19:34:01 2016 +0530

    tests: combine main and main_and_retry into run_tests
    
    run_tests is now aware of retry option and will handle the re-run within
    itself. We don't need main_and_retry and main anymore.
    
    Change-Id: I0f8cad88e29c81588dc0af9f5de78177d0f4e828
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13337
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit fa9f05f8d6a74472b65a887b684448f8d5c3011d
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 2 19:12:41 2016 +0530

    tests: Combine run_all and run_tests
    
    Both the functions perform the same job.
    If no args are given or if args is null string then
    run_tests will act as run_all.
    
    Change-Id: I27284af95fa012b64bba16ac50da8181edfa6336
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13335
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 152832a34b1a03448356298e08d7de36f3a9e992
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 2 18:14:24 2016 +0530

    tests: Make match function simpler
    
    We don't use the dir matching code in run_all.
    It is used in run_tests but it is not generic enough
    and needs work to be fixed.
    
    Rather, making the match function simpler and work for
    only files is easier.
    
    This will help with refactoring of run_all and run_tests.
    
    Change-Id: Ifcd1217480738316736184a51813052ac6a1124e
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13334
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 8ad742de98da284539b8ae772e0990294412da01
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Jan 18 15:57:41 2016 +0530

    Fuse: Add a check for NULL in fuse_itable_dump
    
    Problem: Immediately after starting a disperse volume (2+1)
    kill one brick and just after that try to mount it
    through fuse. This lead to crash.
    
    Our test scripts use process statedumps to determine various things
    like whether they are up, connected to bricks etc. It takes some time
    for an active_subvol to be be associated with fuse even after mount
    process is daemonized. This time is normally a function of completion
    of handshake with bricks. So, if we try to take statedump in this time
    window, fuse wouldn't have an active_subvol associated with it leading
    to this crash.
    
    This happened while executing ec-notify.t, which contains above steps.
    
    Solution: Check priv and  priv->active_subvol for NULL before
    inode_table_dump. If priv->active_subvol is null its perfectly fine to
    skip dumping of inode table as inode table is associated with an
    active_subvol. A Null active_subvol indicates initialization in
    progress and fuse wouldn't even have started reading requests from
    /dev/fuse and hence there wouldn't be any inodes or file system
    activity.
    
    Change-Id: I323a154789edf8182dbd1ac5ec7ae07bf59b2060
    BUG: 1299410
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13253
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit eb362c74db84d95aac07febf0d888bd98b3fb2b9
Author: N Balachandran <nbalacha@redhat.com>
Date:   Sat Feb 6 21:09:29 2016 +0530

    cluster/tier: Create linkfiles to hardlinks correctly
    
    There is a bug in the way hardlinks are handled in tiered volumes. Ideally, the tier linkto files on the cold tier to files that are hardlinks to each other on the hot tier, should themselves be hardlinks of each other. As they are not, they end up being files with the same gfid but different names for the cold tier dht, and end up overwriting the cached-subvol information stored in the dht inode-ctx.
    
    Change-Id: Ic658a316836e6a1729cfea848b7d212674b0edd2
    BUG: 1305277
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13391
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit ff12c4a83bb897501f6e10c1bfe3a69f3dc6cdb9
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jul 1 08:28:07 2015 +0530

    fuse: update fuse_kernel.h to version 23
    
    The following changes were made upstream:
     - add FUSE_WRITEBACK_CACHE
     - add time_gran to fuse_init_out
     - add reserved space to fuse_init_out
     - add FATTR_CTIME
     - add ctime and ctimensec to fuse_setattr_in
     - add FUSE_RENAME2 request
     - add FUSE_NO_OPEN_SUPPORT flag
    
    Including these changes will make it easier to backport support for
    lseek().
    
    Because the fuse_init_out structure changed its size, older versions of
    FUSE would fail initializing. When an older version of FUSE is detected,
    the fuse_init_out structure is reduced to the previous size. This is
    harmless, as the attributes that are not passed, are not used for
    earlier versions anyway.
    
    BUG: 1220173
    Change-Id: I58c74e161638b2d4ce12fc91a206fdc1b96de14d
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    [ndevos: splitted from http://review.gluster.org/11474
             old version fuse_init_out size correction]
    Reviewed-on: http://review.gluster.org/11537
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit c7d2037b8c6293663280a759a2e447d5aef130bd
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Feb 4 14:33:54 2016 +0530

    vagrant-tests: Fix bug when git branch name has a /
    
    It is possible for a git branch to have a / in it.
    
    Source copy from host to VM used relative path on
    the assumption that VM vagrant dir will always be
    three levels down the topdir of repo. This assumption
    breaks when git branch has a / in it.
    
    Of the two solutions to fix it:
    a. Mangle the git branch name to not have a /
    b. Accomodate the possibility of have a / in git branch name.
    
    I have chosen b) because that looks cleaner.
    
    Change-Id: I6b71c31da2f5f7c349d6d6882767768b2534d14f
    BUG: 1291537
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13355
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 2fe4f758f4f32151ef22d644c4de1e58a508fc3e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jan 14 11:11:45 2016 +0530

    glusterd: check quorum on restart bricks
    
    While spawning bricks on a glusterd restart the quorum should be checked and
    brick shouldn't be started if the volume doesn't meet quorum.
    
    Change-Id: I21bf9055bdf38c53c81138cc204ba05a9ff6444f
    BUG: 1298439
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13236
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 0aba36ab99fbf537ba2e5ceddfc950528506011f
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jan 14 09:36:33 2016 +0100

    cluster/ec: Handle non-existent config xattr for non regular files
    
    Since we now try to get the 'trusted.ec.config' xattr for inodes of
    type IA_INVAL (these inodes will be set to some valid type later),
    if that inode corresponds to a non regular file, the xattr won't
    exist and we will handle this as an error when it's not.
    
    This patch solves the problem by only considering errors for inodes
    that are already known to be regular files.
    
    Change-Id: Id72f314e209459236d75cf087fc51e09943756b4
    BUG: 1293223
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/13238
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ashish Pandey <aspandey@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4bde0b3db0e1f8fcbc782e29be2f2eb9e6d4c2fd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jan 25 16:56:05 2016 +0100

    tests: add seek program for testing SEEK_DATA/SEEK_HOLE over FUSE
    
    Note that this only works on Linux kernel 4.5 and newer. The program is
    not run by a test-case because of this.
    
    BUG: 1220173
    Change-Id: Ifdee3c793e33f9d763940130e8d01a61eae5498a
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13291
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c8bbc24a8f3db253d9514210f8505e927bbbe7b0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 21 20:29:07 2015 +0200

    afr: add seek() FOP
    
    seek() is like a read(), copied the same semantics.
    
    Change-Id: I100b741d9bfacb799df318bb081f2497c0664927
    BUG: 1220173
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11483
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 10da9812d83425cb3f2cc8385f94b2a4537d348f
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Jul 1 18:52:42 2015 +0200

    cluster/ec: add seek() FOP
    
    BUG: 1220173
    Change-Id: Iaa23ba81df4ee78ddaab1f96b3d926a563b4bb3d
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/11494
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit cdcd3dc96b412967ba68a56aa2607d86365fbfe6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 21 23:36:12 2015 +0200

    gfapi: add test for glfs_lseek() SEEK_DATA/SEEK_HOLE
    
    Change-Id: I8d0573ed8b2ea5ce976ad140a24be7974dbad0e3
    BUG: 1220173
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11486
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8fdfa0c17cf492f39e675f7502596754f6e5aeb4
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Tue Dec 1 14:23:08 2015 +0530

    libglusterfs: close & open cmd_history.log on log rotate
    
    Post log rotate, cmd_history.log is not refreshed (closed & opened back)
    due to which new commands still land up in the log rotated file.
    
    Fix is to close and open cmd_history.log file upon log rotation
    
    Change-Id: Ie6990c9d55b0afa544bc5c84de3db49ff4b1299b
    BUG: 1286959
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12832
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit f6c5024eb3f37b2c4e5a3bea5136987affb19aa7
Author: Anoop C S <anoopcs@redhat.com>
Date:   Fri Nov 27 10:50:14 2015 +0530

    gfapi: Remove TODO for merging of locks
    
    pub_glfs_posix_lock() currently merge/split locks via
    fd_lk_insert_and_merge(). So removing the same from
    TODO list.
    
    Change-Id: I956fbb3a99ada9616392f934034a94be418195c4
    BUG: 1202274
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/12770
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit 9b71092f3d6cea1cca4804b0588152c79bd34e1d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 21 17:04:29 2015 +0200

    protocol: implement seek() FOP
    
    Network protocol extensions for the seek() FOP. The format is based on
    the SEEK procedure in NFSv4.2.
    
    Change-Id: I060768a8a4b9b1c80f4a24c0f17d630f7f028690
    BUG: 1220173
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11482
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 41beab5444969f235c665042965a650b5a2866e6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Feb 3 17:15:03 2016 +0100

    shard: add seek() FOP as not supported
    
    For getting basic support for SEEK_DATA/SEEK_HOLE, sharding has not been
    implemented. Bug 1301647 has been filed to get this new feature in
    sharding as well.
    
    Because of a premature merge (and revert), this change is re-applying
    everything from commit 2ce3daa94066dcc77cdc6b54a31747b6c7c0c2fc again.
    
    BUG: 1220173
    Change-Id: I0fb2d36c65af5cb2d0a064104b74f7a863ec4ed3
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13347
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bf88dc3d2789b61b4c716b99080218b2507d6170
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jan 26 23:49:24 2016 +0100

    stripe: add seek() FOP as not supported
    
    For getting basic support for SEEK_DATA/SEEK_HOLE, striping has not been
    implemented. Bug 1302149 has been filed to get this new feature in
    stripe as well.
    
    Change-Id: I9cfed795737609120eafe86f9287d79057b14fe2
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13294
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c58f9ce4eefa62ab0ae78d318e443486c4f80a54
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 18 20:35:02 2015 +0100

    upcall: add seek() FOP
    
    Change-Id: Ic86919d28cf639b561114dc1440c6ea4bc6f7307
    BUG: 1220173
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13005
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 5c39f43c13aa652b0db28ca7afea65982bd568cc
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 21 18:32:40 2015 +0200

    gfapi: add support for SEEK_HOLE and SEEK_DATA in glfs_lseek()
    
    Change-Id: I142dde11923244809b03fcca8cd4c2f7d5ff3929
    BUG: 1220173
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11485
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit b609a55be4119c44b19252bd951780a78deb21c9
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Feb 3 18:24:20 2016 +0530

    features/trash: Handle unlink unwind properly
    
    When enabled, trash translator does a rename
    internally for every unlink request and unwinds
    the original unlink call. But this was unwinded
    back with prerparent and postparent as NULL which
    resulted in changing the parent directory
    permissions to 000.
    
    This issue is consistently seen as a failure
    when a non-root user executes vim commands which
    internally tries to perform stat operations (as
    part of swap/backup file creation) on a file
    whose parent directory's permission was modified
    to 000 due to recent unlink for another file
    inside the same directory.
    
    Change-Id: I161a036b37fb815866d50d2d6260ff0ad22d7223
    BUG: 1302307
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/13346
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 453abcb821b712f849f91a2a370a4debff89eed2
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jan 27 15:08:03 2016 +0530

    geo-rep: Fix gsyncd prefix in gsec_create
    
    gsec_create script is generated after running ./configure
    
    libexec dir was formed using $prefix/libexec, but in Debian based
    distributions libexec dir is not present, instead they use lib
    directory to store these scripts.
    
    With this patch, full libexec path is fetched during ./configure.
    
    BUG: 1162905
    Change-Id: I9f47a38e6ab0027c7df6716136fbe0635e95a593
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/13298
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit cf914bbf07e329001fd5a844ef9c2c25d17ed131
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 2 19:24:07 2016 +0530

    tests: always use $@ and in quotes
    
    Change-Id: I318d8b0ea60937f74b3280fa2ad26876ce8c3345
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13336
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit e07fdc4b6d8936089a9ec08aa61f450126b43787
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Jan 29 15:59:24 2016 -0500

    cluster/dht: Cleanup dict in dht_do_rename()
    
    Change-Id: Ib4b3a843e78eccf5b8e0e7776cd0128013a59a3e
    BUG: 1303945
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/13322
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bb1bc854b85ed2e3f51da3a82f56c154ca348e33
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Sat Jan 30 22:35:19 2016 +0100

    fuse: fix inode and dentry leaks
    
    When a readdirp was executed, the nlookup count for each inode of the
    returned entries was incremented. However the kernel does not increment
    the counter for '.' and '..' entries.
    
    This caused kernel to send forgets with a counter smaller than the
    inode's current value. This prevented these inodes to be retired when
    ref count was 0.
    
    Change-Id: I31901af36ab7b4cdc3e6fa2f30a0263a1a2daef8
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/13327
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b8106d1127f034ffa88b5dd322c23a10e023b9b6
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Feb 1 11:46:08 2016 +0530

    cluster/afr: Fix heal-info slow response while IO is in progress
    
    Now heal-info does an open() on the file being examined so that
    the client at some point sees open-fd count being > 1 and releases
    the eager-lock so that heal-info doesn't remain blocked forever
    until IO completes.
    
    Change-Id: Icc478098e2bc7234408728b54d8185102b3540dc
    BUG: 1297695
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13326
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 11202e6c726f79ddf0e461338d7dce158733122e
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Jan 26 17:47:08 2016 +0530

    tier/gfdb : Round-Robin read of query files
    
    1. Each brick on a host will get a separate query file.
    2. While reading query record from these query files we
       read them in a Round-Robin manner.
    3. When an error occurs during migration we rename it to
       query file with an time stamp and .err extension for
       better debugging.
    
    Change-Id: I27c4285d24fd695d2d5cbd9fd7db3879d277ecc8
    BUG: 1302772
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/13293
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: N Balachandran <nbalacha@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 545f4ed2c7195a21210e6a055c27c1b7a115e18c
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Feb 2 22:09:45 2016 +0530

    cluster/tier : Reset watermarks in tier
    
    A node which contains only cold bricks and has detected that
    the high watermark value has been breached on the hot tier will
    never reset the watermark to the correct value. The promotion check
    will thus always fail and no promotions will occur from that node.
    
    Change-Id: I0f0804744cd184c263acbea1ee50cd6010a49ec5
    BUG: 1303895
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13341
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 58a91f36f639de21f6e77d1f43f5eb091ae96fb0
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Jan 22 17:31:48 2016 -0500

    cluster/tier: break out of iterating query file once cycle time ends
    
    When iterating the query file during migration, tiering should
    break out of the loop once cycle time completes. Otherwise it
    may be possible to stay in the loop for a long time. If that
    happens updates to files will become stale and have not impact
    migration.
    
    Change-Id: Ib60cf74bc84e8646e6a0da21ff04954b1b83c414
    BUG: 1301227
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/13284
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit d9e5977b08259580deccad2e0eed3a106094820a
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Feb 1 12:29:40 2016 +0530

    tests: refactor option parsing into a function
    
    Creating a separate function to parse options.
    This is required for subsequent patches where we add
    more options to run-tests.sh.
    
    Created a variable tests to hold the tests list or
    pattern as passing around $@ is not informative.
    
    Change-Id: I032639c07419f5136c604531c5719c13ac4f9fe3
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13328
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 29bd2316b6d4f522e1bd00e3c9a1c97dcc7d80ea
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jan 21 15:03:38 2016 -0500

    fuse: use-after-free fix in fuse-bridge, revisited
    
    Prompted by the email exchange in gluster-devel between Oleksandr
    Natalenko, xavi, and soumyak, I looked at this because the fuse client
    on the longevity cluster has also been suffering from a serious memory
    leak for some time. (longevity cluster is currently running 3.7.6)
    
    The longevity cluster manifests the same kernel notifier loop terminated
    log message the Oleksandr sees, and some sample runs suggest that the
    length passed to the (sys_)write call is unexpectedly and abnormally large.
    
    Basically this fix
      a) uses correct types for len and rv,
      b) copies the len from potentially incorrectly aligned memory (in a
         way that should minimize potential performance issues related to
         accessing unaligned memory.)
      c) changes log level of the kernel notifier loop terminated message
      d) fixes a potential mutex lock/unlock issue
    
    Change-Id: Icedb3525706f59803878bb37ef6b4ffe4a986880
    BUG: 1288857
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13274
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ac3183a5012bfed26fa0aead7f359f5d5b00e23e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 21 17:55:49 2015 +0530

    heal: Have fixed number of fields in heal info output
    
    Sample output:
    ⚡ gluster v heal r2 info
    Brick localhost.localdomain:/home/gfs/r2_0
    /a
    /
    Status: Connected
    Number of entries: 2
    
    Brick localhost.localdomain:/home/gfs/r2_1
    Status: Transport endpoint is not connected
    Number of entries: -
    
    Brick localhost.localdomain:/home/gfs/r2_2
    Status: Connected
    Number of entries: 0
    
    Brick localhost.localdomain:/home/gfs/r2_3
    Status: Connected
    Number of entries: 0
    
    Partial failure will print:
    ...
    <gfid:3efb51cf-5fa5-4bed-817b-afd600e9449e>
    Status: Failed to process entries completely. (Transport endpoint is not connected)
    Number of entries: 372
    ...
    
    BUG: 1297897
    Change-Id: I79131cbf255acd98f11eedafb53246c465f6665d
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13231
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Sahina Bose <sabose@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 959785a885528f66c56e744641c71d1e7e2fadc8
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon Jan 25 01:33:48 2016 +0530

    extras/devel-tool: Added gdb_macros for debugging
    
    provided following functions in the script
    1) print dictionary (dict_t) items
    2) print list members (only address)
    
    Change-Id: I5befb2dcdbf258ab3001ff25212a5862b9cc5321
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/13289
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 4267c14e1be513b6124ef0dca75029494844f711
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Dec 30 16:37:05 2015 +0530

    snapd: Do not persist snapd port
    
    Currently snapd persists the port it uses
    to sign-in with glusterd, without checking
    if that particular port is being used by any
    other process. As a result, it might erroneously
    sign out any other process using the same port.
    
    Hence forcing snapd to ignore the persisted port,
    and using a new one while coming up.
    
    Change-Id: Ibb9ec3762aac445f03d96e85660585be4ab27bcb
    BUG: 1294794
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13118
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit b8a7b648d8f16999b00768d56f029b955c390eb7
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 21 17:51:24 2015 +0200

    syncop: add seek() FOP
    
    Add the new seek() FOP to the syncop framework. gfapi will use this in
    the future.
    
    Change-Id: I0c15153beb27de73d5844b6f692175750fc28f60
    BUG: 1220173
    Singed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11481
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 0b6aba5ef63882e6a798a23de6f8efbb6bea0ea7
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 21 15:51:00 2015 +0200

    core: add seek() FOP
    
    Minimal infrastructure changes for the seek() FOP. This will provide
    SEEK_HOLE and SEEK_DATA functionalities.
    
    BUG: 1220173
    Change-Id: I4b74fce8b0bad2f45291fd2c2b9e243c4f4a1aa9
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11480
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2e69ae03c3c3fcb86e4d5347008834ad1dfb42b4
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jan 24 13:23:19 2016 +0100

    Point users of glusterfs-hadoop to the upstream project
    
    The code we have in glusterfs-hadoop/ is old and should not be used
    anymore. The plugin for Hadoop HCFS is maintained at the
    glusterfs-hadoop project on GitHub:
    
      https://github.com/gluster/glusterfs-hadoop
    
    Removing the old code from the repository, and adding a pointer to the
    projects wiki in the MAINTAINERS file.
    
    Change-Id: Ia86d08fb0c73a3f75b706b1e0793e3d7a0f4984c
    BUG: 1301352
    CC: Jay Vyas <jvyas@redhat.com>
    CC: Bradley Childs <bchilds@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13286
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2fa5f7267801c3bff25f813ff6eb44305e56b0b5
Author: vmallika <vmallika@redhat.com>
Date:   Tue Jan 5 17:50:09 2016 +0530

    glusterd: register rpc notification for unix sockets
    
    Previously only CLI was using unix socket to connect to glusterd,
    and there was no need to register rpc callback notifications.
    Now auxiliary mount process is started with unix socket option.
    
    So we need to register register rpc notifications for unix sockets as
    well.
    
    Change-Id: I985839fc91c5c2674d85a7ec94ae24f47898c22d
    BUG: 1295763
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13174
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 080ddb79d8805253a7f4274606351570faae1add
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Dec 30 10:17:00 2015 +0530

    cluster/ec: Create this->itable in all cases
    
    Problem:
    glfsheal operates based on mount's volfile which doesn't have iamshd flag due
    to which this->itable is NULL, this leads to "inode not found" logs in glfsheal
    logs.
    
    Fix:
    Ec only allocates itable with 10 inodes, so allocating this->itable in all
    cases in init.
    
    Change-Id: I01d3c05e93a17007a4716a2d6f392d2aa306a34b
    BUG: 1294743
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13112
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 786a8b395b09126a1151865c57ec2753a26facbb
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jan 27 17:04:18 2016 +0530

    features / bitrot: Prevent spurious pthread_cond_wait() wakeup
    
    pthread_cond_wait() is prone to spurious wakeups and it's utmost
    necessarry to check a boolean predicate for thread continuation.
    
    See man(3) pthread_cond_wait() for details.
    
    The following is done in bitrot scrubber:
    
        if (list_empty (&fsscrub->scrublist))
           pthread_cond_wait (&fsscrub->cond, &fsscrub->mutex);
    
    followed by:
    
        list_first_entry (&fsscrub->scrublist, ...)
    
    A spurious wakeup from pthread_cond_wait() with the absence of
    list_empty() check causes list_first_entry() to return garbage.
    
    Change-Id: I08786b9686b5503fcad6127e4c2a2cfac4bb7849
    BUG: 1302201
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13302
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit eb5e71c26d780fd5e440893fcc78fa91c36fe0c1
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jan 27 14:55:16 2016 +0530

    snapshot: Decreasing VHD_SIZE to 300M
    
    Decreasing the VHD_SIZE in snapshot.rc, as 1G
    of lvs are not needed for test setups, and
    allocating as much space might not allow the
    tests to be run in some setups
    
    Change-Id: I46ad0e2751301ba9f19f7ac548d41fa4521baa75
    BUG: 1302234
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13297
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit fd16186b403e38763b1d0b39c8c7ce14ffc508ba
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Aug 5 16:02:49 2015 +0530

    glusterd: improve error logs for unsupported clients
    
    Change-Id: I90be46a7b25cc3efd0e61c9a145852e9027f5f64
    BUG: 1302205
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11831
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit eca923349b4cb397b19520e4e391e42b8d6532c2
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jan 8 13:06:27 2016 +0530

    cluster/afr: Move remaining gf_logs to gf_msgs
    
    Change-Id: I48d9e5313bd3ccf9fe26c90a7051a8a174d75c49
    BUG: 1296818
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/13195
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d57bf5bf59c72ef5c791efed885b5f2d80e42a97
Author: Pranith Kumar Karampuri <pkarampu@redhat.com>
Date:   Wed Jan 27 03:25:37 2016 -0800

    Revert "shard: add seek() FOP as not supported"
    
    This reverts commit 2ce3daa94066dcc77cdc6b54a31747b6c7c0c2fc.
    
    Change-Id: Ic00337a69e0a322b14c5cfdf68c06428c5da3a19
    Reviewed-on: http://review.gluster.org/13301
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 2ce3daa94066dcc77cdc6b54a31747b6c7c0c2fc
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 18 21:41:04 2015 +0100

    shard: add seek() FOP as not supported
    
    For getting basic support for SEEK_DATA/SEEK_HOLE, sharding has not been
    implemented. Bug 1301647 has been filed to get this new feature in
    sharding as well.
    
    BUG: 1220173
    Change-Id: I5c272855a21501ac31e1a5f4b68ed7245582c17c
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13290
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit ce2c58d0fab517320059af7cea2e36e5cd246b6e
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Jan 20 22:27:33 2016 +0530

    tier/dht : Default value for demote-freq, max files and mb
    
    Default value for tier-demote-frequency is 3600 sec to avoid
    frequent demotions.
    
    Default value for tier-max-mb is 4000 mb
    
    Default value for tier-max-files is 10000 files
    
    Change-Id: Ie60951c478a7462c425059699ab82511aa13fa0a
    BUG: 1300412
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/13270
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 9ce86c63e349eaafbd923b0b541d75e929ecbae7
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Jan 25 13:27:42 2016 +0530

    cluster/tier: Ignore quota-deem-statfs for watermark calculation
    
    The tier process watermark calculations were incorrect when the
    quota-deem-statfs option was enabled. We now ignore this while
    calculating hot tier usage to determine watermark levels.
    
    Change-Id: I308bc24432e2fa5ad1d5703e80fc391433538bbb
    BUG: 1301473
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13288
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: mohammed rafi  kc <rkavunga@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit f17c2e991e45b83f7d21de1b976b59862ea173ab
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Jan 18 20:50:24 2016 +0100

    NetBSD regression reliability: properly cleanup loopback devices
    
    When a loopback device is configured and we forcibly unmount the
    filesystem containing the backing store, further vnconfig -l will
    complain "vnconfig: VNDIOCGET: Bad file descriptor" causing
    failures.
    
    We fix this by iterating on all loopback devices available in /dev,
    testing for this condition and manually unconfiguring when it
    happens.
    
    BUG: 1129939
    Change-Id: I17b956a8ed28a7767f2d0dda83b93c523d3238c2
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/13204
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit ca4d4a26a553bac9c627bc6e6d6c9fa1f9435297
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Thu Jan 14 15:07:47 2016 +0530

    tests : Modifying crypt xlators unit tests
    
    The "encryption.master-key" should be set before enabling crypt xlators.
    Otherwise glusterfs client process(like gluster-NFS) will crash due to the
    failure in intialising crypt xlator.
    
    You can see the following messages in client log file
    [2016-01-14 08:13:15.740835] E [crypt.c:4298:master_set_master_vol_key]
    0-test1-crypt: FATAL: missing master key
    [2016-01-14 08:13:15.740859] E [MSGID: 101019]
    [xlator.c:429lator_init] 0-test1-crypt: Initialization of volume
    'test1-crypt' failed, review your volfile again
    [2016-01-14 08:13:15.740890] E [MSGID: 101066]
    [graph.c:324:glusterfs_graph_init] 0-test1-crypt: initializing
    translator failed
    [2016-01-14 08:13:15.740904] E [MSGID: 101176]
    [graph.c:670:glusterfs_graph_activate] 0-graph: init failed
    [2016-01-14 08:13:15.741676] W [glusterfsd.c:1231:cleanup_and_exit]
    (-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x307) [0x40d287]
    -->/usr/sbin/glusterfs(glusterfs_process_volfp+0x117) [0x4086c7]
    -->/usr/sbin/glusterfs(cleanup_and_exit+0x4d) [0x407e1d] ) 0-: received
    signum (0), shutting down
    
    Change-Id: I124deda505d128eacb15ca20fbdcd1593cb8eba3
    BUG: 1298520
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/13240
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit a5b352a703574b894e0b7cdbf16bea637dab75e8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jan 3 12:57:29 2016 +0100

    fuse: pass standard mount options to the kernel
    
    Some of the default mount options were made invalid with glusterfs-3.6.
    The /sbin/mount.glusterfs script changed heavily and now requires all
    valid mount options to be listed. Earlier versions (glusterfs-3.5 and
    before) passed all unknown mount options on to fuse.
    
    With this change, all mount options from 'man 8 mount' are explicitly
    included in the /sbin/mount.glusterfs script. Some of the options are
    marked with TODO, these are not commonly used and may require some
    additional support in Gluster/FUSE too.
    
    BUG: 1294809
    Change-Id: Ic312140d7318b54523996bb08772ff065af7eb27
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13166
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit e67712c06b64fb659824b3f79164f2789693acee
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jan 13 16:19:15 2016 +0530

    features/shard: Implement zerofill FOP
    
    Change-Id: Iabb89a502cc560edd7fe3755623c74a2ccb853d5
    BUG: 1261841
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13234
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit ea94b2b8767e0d477a672355d758e0e8393362ee
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 5 15:36:28 2016 +0530

    tests: Fix spurious failure in bug-1221481-allow-fops-on-dir-split-brain.t.
    
    Occasionally, when ls is executed, prior to READDIRP, a STAT is wound on
    the operand directory. And AFR fails STAT with EIO if it is in metadata split-brain
    which "dir" is in the test case in question. As a result, ls also fails with EIO,
    causing test 20 to return negative exit status.
    The fix is in the test script where the parts that cause the dir to go into
    metadata split-brain have been removed. Now "dir" will only have entry
    split-brain.
    
    Change-Id: I4e4e6ba0a2401c7168719cd44e5f4f4bcb8fdd89
    BUG: 1295702
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13172
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit a593921aa0eada17637667938f432875b410139d
Author: vmallika <vmallika@redhat.com>
Date:   Mon Jan 18 23:31:59 2016 +0530

    quota: start aux mount from glusterd with inet address
    
    With below patches, quota aux mount now
    uses unix domain socket to connect to
    glusterd
    http://review.gluster.org/#/c/12645/
    http://review.gluster.org/#/c/12819/
    
    When USS is enabled, snapd protocol client tries to
    connect to glusterd with inet and fails,
    because remote-host option by client process
    is set to UDS file
    
    This patch starts the aux client process from glusterd
    with inet address
    
    Change-Id: I6967043bfd8824658ea39bfd2842591fcc3280fd
    BUG: 1299497
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13255
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 16f6579cb3e1214b1386fb530b8e16c8cbfdef33
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Jan 21 12:41:55 2016 +0530

    protocol/server: Race between server_reconfigure and server_setvolume
    
    During server_reconfigure we authenticate each connected clients
    against the current options. To do this authentication we store
    previous values in a dictionary during the connection establishment
    phase (server_setvolume). If the authentication fails during
    reconfigure then we will disconnect the transport.
    
    Here it introduce a race between server_setvolume and reconfugure.
    If a reconfigure called before doing a setvolume, the transport
    will be disconnected
    
    Change-Id: Icce2c28a171481327a06efd3901f8a5ee67b05ab
    BUG: 1300564
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13271
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>

commit 30ef018c00b0d1be5d590c9518c159a7946d040e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jan 6 13:34:01 2016 +0000

    afr : Check if dict is valid in afr_replies_interpret()
    
    posix_mkdir does not send response xdata. So even though replies are
    valid, the response xdata dict is NULL. Check if dict is non-null in
    afr_replies_interpret before doing dict_get
    
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    
    Change-Id: If543d68d8bfd2433519105839d5be106076cc276
    BUG: 1294053
    Reviewed-on: http://review.gluster.org/13185
    Tested-by: Ravishankar N <ravishankar@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 27a350fe30c03fddb57231a2a60bb3e4c54d9dd4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jan 20 16:35:42 2016 +0530

    tests: Move open-behind.t to bad tests list
    
    Change-Id: I505e6dbd13d7922ac7468507c172764d64256389
    BUG: 1300253
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13268
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6d430b85a39784f96b69368e1a9c8b4be4d0ddb1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jan 13 14:37:30 2016 +0530

    tests: Fix sparse-file-self-heal.t
    
    Psuedo Problem:
    https://build.gluster.org/job/rackspace-regression-2GB-triggered/16682/consoleFull
    
    The 'zeroedfile' disk usage comparision which is failing in this .t file
    fails so only on XFS. The test passes when the backend is on a s̶a̶n̶e̶r̶
    different filesystem like EXT4 or BTRFS. This is due to the speculative
    preallocation in XFS which can reserve different disk space on different
    XFS mounts for the same version and same file operation. See BZ 1277992
    for an example of XFS behaviour.
    
    Fix:
    Don't compare the disk usage of the file on the bricks of the replica:
    instead, check that the disk space consumed is atleast equal to the size
    of the file.
    
    Also remove sparse-file-self-heal.t from is_bad_test()
    
    Change-Id: If43f59549136ebf91f17ff9d958954b3587afe56
    BUG: 1298111
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13233
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>

commit de276bd2452302e2e27b94b7f577c25fc351037d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jan 19 16:22:17 2016 +0530

    snapshot: Return before redundant quorum check
    
    As of today, we don't support creation of snapshot even
    if one brick is down. Hence the older quorum check is
    redundant. Returning after performing the check to
    see if all bricks are up.
    
    BUG: 1299819
    Change-Id: I35661d05a15be0109aaae51b4fe0d5a8ca4333ad
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/13260
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>

commit 67b7752eccd8eae6a91f3bc3ff55d65dcf858dc7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jan 18 12:19:35 2016 +0530

    cli: Add arbiter details to volinfo xml output
    
    The following are added:
    1. "<arbiterCount>1</arbiterCount>" and
    "<coldarbiterCount>1</coldarbiterCount>"
    
    2. "<isArbiter>0</isArbiter>" on the brick info, like so:
    <brick
    uuid="cafa8612-d7d4-4007-beea-72ae7477f3bb">127.0.0.2:/home/ravi/bricks/brick1
    <name>127.0.0.2:/home/ravi/bricks/brick1</name>
    <hostUuid>cafa8612-d7d4-4007-beea-72ae7477f3bb</hostUuid>
    <isArbiter>0</isArbiter>
    </brick>
    
    Also fix a bug in gluster vol info where the abiter brick was shown the
    wrong brick of the cold tier after performing a tier-attach.
    
    Change-Id: Id978325d02b04f1a08856427827320e169169810
    BUG: 1297750
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13229
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c535059299785f7d050482c257f10389c218048b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Oct 29 17:04:38 2015 +0530

    features/shard: Implement fallocate FOP
    
    Change-Id: I6f07074e94b115f6c6c2c59a8a1b58ba44b1c12a
    BUG: 1261841
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13196
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit b95ad51e00d6076d37809bcc50b89fee1cf248ef
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jan 11 12:58:16 2016 +0000

    afr: skip healing data blocks for arbiter
    
    1 ....but still do other parts of data-self-heal like restoring the time
    and undo pending xattrs.
    
    2. Perform undo_pending inside inodelks.
    
    3. If arbiter is the only sink, do these other parts of data-self-heal
    inside a single lock-unlock sequence.
    
    Change-Id: I64c9d5b594375f852bfb73dee02c66a9a67a7176
    BUG: 1286017
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12777
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c862580c66ed7d2a8dc96b9051e5df86e1aae0d0
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jan 14 16:11:27 2016 +0530

    protocol/server: Fix memory corruption during client-table-expand.
    
    gf_client_clienttable_expand frees up old entries after expanding. So,
    cliententry should be reassigned to a free slot in new array of
    cliententries. Earlier it used to point to a slot in oldentries
    resulting in a use-after-free bug.
    
    Thanks to Pranith for the assistance provided.
    
    Change-Id: Iabe40c7df475471a7df7bccb302aef496ded3f1c
    BUG: 1298498
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/13241
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit 7fa96199d669423d8ed2d2271fd603d641e603b8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 8 16:43:15 2016 +0100

    rpm: glusterfs-server requires -api
    
    The glusterfs-server package requires libgfapi.so for the glfs-heal
    binary and possibly other parts.
    
    Also adding %{?_isa} to requirements as described in the Fedora
    Packaging Guidelines for Explicit Requires at
    https://fedoraproject.org/wiki/Packaging:Guidelines#Explicit_Requires
    
    BUG: 1296992
    Change-Id: I96c62876b776d04a7f5d1b1dc34c02302b6ffbe6
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13200
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>

commit a0e690fbdf5681c7cf644271de5cc03bde3fef8f
Author: Michael Adam <obnox@samba.org>
Date:   Mon Jan 4 18:50:38 2016 +0100

    hook-scripts: S29CTDBsetup: clean and fix mount commands and options
    
    This refactors the mount options of S29CTDBstart.sh into one
    variable, removing the superfluous mentioning of 'default'.
    The manual mount command is fixed to:
    - also use the common options, thereby adding
      _netdev,transport=tcp
      (while this does not have an effect for the _netdev
       option, it makes a difference for the transport option),
    - also use the HOSTNAME variable just like the fstab entry,
    - use a "/" in the remote location specification.
    Hence it now behaves identically to the fstab mount.
    
    Change-Id: Ibb7613b1b1278ab13745846baa79268db226ef19
    BUG: 1295520
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/13170
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit a34c406445fc0294de41a8e4706f106a83e136a0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jan 10 13:42:58 2016 +0100

    build: place glupy under $prefix while installing
    
    Regression testing on FreeBSD fails due to this error:
    
      --- install-pyglupyPYTHON ---
       /usr/home/jenkins/root/workspace/freebsd-smoke/install-sh -c -d '/usr/local/lib/python2.7/site-packages/gluster/glupy'
      mkdir: /usr/local/lib/python2.7/site-packages/gluster: Permission denied
      mkdir: /usr/local/lib/python2.7/site-packages/gluster: Permission denied
      *** [install-pyglupyPYTHON] Error code 1
    
    The installation prefix is set to "/build/install" and glupy should be
    placed there as well. The default to "/usr/local" is incorrect.
    
    Change-Id: I166412a271576f2344aecec94c7835f0fe9b1cf3
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13208
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit de2c5297ad9d26c844823bcdbfc0264d8bf7ddd7
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jan 14 09:57:47 2016 -0500

    build: update link for .git/hooks/commit-msg
    
    Add -L option to curl cmd to follow a redirect
    
    Change-Id: I273248d2a610174cc3905b0ffb8f586deb191f5f
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13244

commit 856edc31417dd9459776ee68dff2d59c002eef74
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Jan 10 18:00:58 2016 +0100

    POSIX shell compliance: == operator
    
    POSIX shell uses = and not ==, the later being a bash extension.
    
    BUG: 1129939
    Change-Id: I9d51225de99c1607894211e68808b63100696fef
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/13209
    Reviewed-by: Michael Adam <obnox@samba.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 11f6ad26febad1ae7752c2cb7f2c34b1153cae08
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 25 16:19:59 2015 +0100

    scripts: correct the usage of -perm in backend-cleanup.sh
    
    extras/backend-cleanup.sh uses deprecated find -perm +xxx syntax:
    
      find [...] -perm +01000 [...]
    
    This GNU extension syntax is deprecated and does not work in GNU
    findutils 4.5.11 and later. Please change to find -perm /xxx instead.
    
    The new syntax was introduced in 4.2.25 (October 2005) and should
    therefore be available on any relevant system.
    
    BUG: 1294223
    Change-Id: Ice742957dd24f0ab4f70a8569dff6f2536e9ac1e
    Reported-by: Andreas Metzler <ametzler@bebt.de>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13080
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 7d6e5dad15b7ecf2e8abce468aea9fd84b876052
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Jan 13 11:34:27 2016 +0530

    upcall: free the xdr* allocations
    
    Free the xdr string allocations after decoding the upcall
    cache_invalidation request.
    
    Change-Id: I0ffc64f587d6c8566cba76cf08148f937a735926
    BUG: 1295107
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/13232
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ced0f360e4606ecf66a73ece54553523567f9995
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Dec 31 16:39:21 2015 +0530

    tests: include unistd.h for fdatasync
    
    gcc throws a warning if unistd.h is not included.
    
    
    Change-Id: I37f35f60c84fb6667a503696063a4c9987d8ab2f
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13128
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 1b9174d35dc113f97fd5cec811633853cef269f3
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Jan 11 16:17:29 2016 +0530

    performance/write-behind: fix memory corruption
    
    1. while handling short writes, __wb_fulfill_short_write would've freed
       current request before moving on to next in the list if request is not
       big enough to accomodate completed number of bytes. So, make sure to
       save next member before invoking __wb_fulfill_short_write on current
       request. Also handle the case where request is exactly the size of
       remaining completed number of bytes.
    
    2. When write request is unwound because there is a conflicting failed
       liability, make sure its deleted from tempted list. Otherwise there
       will be two unwinds (one as part handling a failed request in
       wb_do_winds and another in wb_do_unwinds).
    
    Change-Id: Id1b54430796b19b956d24b8d99ab0cdd5140e4f6
    BUG: 1297373
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/13213
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 252fe523e2932e83a98f203f71678f391eee6b22
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jan 12 15:04:46 2016 +0530

    gfapi: send lookup if inode_ctx is not set
    
    During resolving of an entry or inode, if inode ctx
    was not set, we will send a lookup to pupulate inode
    ctx for every xlators
    
    This patch also make sure that inode_ctx will be created
    after every inode_link. We will store inode_ctx value as
    LOOKUP_NEEDED if the inode is liked via readdirp, in all
    other case we will store inode_ctx value as LOOKUP_NOT_NEEDED.
    
    Change-Id: I3a10c298944200fa3862127187ae8988e582d352
    BUG: 1297311
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13226
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit ad8c65612d6d7e32c06fd3aed11b7a9edd514607
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jan 12 12:54:42 2016 +0530

    fuse: send lookup if inode_ctx is not set
    
    During resolving of an entry or inode, if inode ctx
    was not set, we will send a lookup.
    
    This patch also make sure that inode_ctx will be created
    after every inode_link
    
    Change-Id: I4211533ca96a51b89d9f010fc57133470e52dc11
    BUG: 1297311
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13225
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit ca515db012718f2d4998edf682c70ccba29924c6
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Aug 12 14:30:27 2015 +0530

    fuse:sent at least one lookup before actual fop
    
    Fuse shoud sent atleast one lookup for an inode/gfid
    populated via readdirp before actual fop to populate
    inode ctx for xlators
    
    Change-Id: I5c02ed73f892924c9e404d91cbe0633a275accbd
    BUG: 1236032
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11892
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 14f925f5262ecabb2faf8142267c37103413e189
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jan 12 12:04:59 2016 +0530

    nfs: send lookup if inode_ctx is not set
    
    During resolving of an entry or inode, if inode ctx
    was not set, we will send a lookup.
    
    This patch also make sure that inode_ctx will be created
    after every inode_link.
    
    Change-Id: I137a7e2510635ff4ea6d007b671961341f89c949
    BUG: 1297311
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13224
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 3882408103973eac6983c2efdd5af8b1d51f272c
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Dec 21 16:04:20 2015 +0530

    cluster/ec: Get size and config for invalid inode
    
    Problem:
    After creating an inode and before linking it
    to inode table, if there is a request to setattr
    for that file, it fails and leads to crash.
    Before linking inode to inode table ia_type is IA_INVAL
    which will casue have_size and have_config as zero.
    
    Solution:
    Check and get size and config if an inode is invalid
    
    Change-Id: I0c0e564940b1b9f351369a76ab14f6b4aa81f23b
    BUG: 1293223
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/13039
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit e9d20f0e1a17e0ef2f148a9b49d1cf9596cbe609
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jan 12 12:13:15 2016 +0530

    snapview-client: remove check for parent inode type
    
    In lookup call back path, we are checking for parent inode
    type to make sure parent inode was set properly, so that
    next op on the inode can be successfuly completed.
    
    More info can be found at bugid 1297311
    
    Change-Id: Ifb1b17f472f855f9b12088c3dd8328389d895e77
    BUG: 1297311
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13227
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 682b19eec8e0a874f7dc8b0ec04b5d731be928e5
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Jan 9 05:49:24 2016 +0100

    Portability fix: rfc.sh
    
    Function declaration in POSIX shell does not use the 'function' keyword.
    This is bash-specific.
    
    BUG: 1129939
    Change-Id: Ifc2dddd0c0a99d2672aaa3aa1cdf18d0d1e38336
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/13206
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit ae165bd6d7c3a0130984cbd927be318146c7bbdd
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Jan 12 16:38:27 2016 +0530

    tests/quota : fix failing test on auxiliary mount point
    
    In test file tests/bugs/quota/bug-1049323.t, test "EXPECT "0" get_aux"
    fails in Fedora.
    
    In get_aux function we grep for "/var/run/gluster/<volname>" to check
    if auxiliary mount point is created and we return 0 on success else we
    return 1. In fedora, auxiliary mount point is created on
    "/run/gluster/<volname>". So it fails on Fedora.
    
    The patch fixes it by just grepping for "/run/gluster/<volname>".
    
    Change-Id: Icb59395df4a98109eaa8199cbdbdedcd1cbef27a
    BUG: 1297740
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/13228
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 2b2294d2a4ef221fccb6eb9f74e9b7dc233b9f1d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Dec 28 10:26:20 2015 +0100

    scripts: prevent running 'showmount' from the start/post hook script
    
    The 31ganesha-start.sh hook script tries to run 'showmount' to see if
    the volume that is getting started should get exported by NFS-Ganesha.
    It was reported that this caused the 'gluster volume start ...' command
    to hang in case rpcbind is not running.
    
    Instead of running 'showmount', we can use DBus to contact NFS-Ganesha
    directly, and request the available exports. This will immediately fail
    in case NFS-Ganesha is not running.
    
    BUG: 1294446
    Change-Id: I3aba1f86fead67116ca5adb1864a8be626c334fa
    Reported-by: Jeff Darcy <jdarcy@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13098
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 7d4f708b18c1e6c965ebe8c84e14dd69ae4b7859
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Dec 30 16:19:44 2015 +0530

    glusterd: GD_OP_VERSION should not be a released one
    
    performance.resync-failed-syncs-after-fsync was
    introduced after 3.7.6 was released. Hence it should
    use 3_7_7 as op version not 3_7_6.
    
    
    
    Change-Id: If4def1bf0fdc9fa4938ccb78308bec77eeaa2284
    BUG: 1279730
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13117
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2a37dbd845348a774f45c4d77cffebc32c749251
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Dec 29 10:54:55 2015 +0530

    glusterd/cli: mask out inaccurate scrub statistics
    
    Some of the scrub statistics are inaccurate at the moment and would
    successfully fool users at times. It's best to not display these
    stats and stick to what is accurate.
    
    Note that the change is only in the CLI part - glusterd (and brick)
    supplies _all_ available scrub statistics, but CLI just selectively
    sticks to what needs to be displayed.
    
    Change-Id: Ia99f505a2cb10d5406cd37035d082e593f7e9a8c
    BUG: 1285989
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13105
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit a249ea5aa7102a56abf5b320e5fe5351333dd5eb
Author: Michael Adam <obnox@samba.org>
Date:   Mon Jan 4 18:21:51 2016 +0100

    hook-scripts: remove RHS-2.0 reference from S29CTDB scripts
    
    This is old. And such downstream reference should not
    appear in upstream code.
    
    Change-Id: Ifa0664dae0fe5ac913a49afe2fefa43b0112b024
    BUG: 1295505
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/13169
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit c449b7520c6f1ac6ea1bc4119dbbbe9ebb80bf93
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Dec 21 23:13:43 2015 +0530

    glusterd: import/export brickinfo->uuid
    
    Given a two node cluster with node N1 & N2, if a dummy node N3 is peer probed, the
    probed node N3  goes for importing volumes from the probing node (N1), but
    it still doesn't have information about the other node (N2) about its membership
    (since peer update happens post volume updates) and hence fail to update its
    brick's uuid. Post that even though N2 updates N3 about its membership the
    brick's uuid was never generated. Now as a consequence when N3 initiates a
    detach of N2, it checks whether the node to be detached has any bricks
    configured by its respective uuid which is NULL in this case and hence it goes
    ahead and removes the peer which ideally it shouldn't have (refer to
    glusterd_friend_contains_vol_bricks () for the logic)
    
    Fix is to export brick's uuid and import it at the probed node instead of
    resolving it.
    
    Change-Id: I2d88c72175347550a45ab12aff0ae248e56baa87
    BUG: 1293414
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/13047
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit 36fcaf275952202ce3f1e621d3b3a34d58054c99
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Jan 8 10:36:37 2016 +0530

    cluster/dht : Rebalance process crashes due to double fd_unref
    
    The dst_fd was being unrefed twice in case the call
    to __dht_rebalance_create_dst_file failed.
    
    Change-Id: I56c5aff7fa3827887e67936b8aa1ecbd1a08a9e9
    BUG: 1296611
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13193
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 9e7cd9456532caa7b255978b4b435418c04e0db9
Author: James Augustine <jcaugust81@gmail.com>
Date:   Wed Dec 16 14:56:11 2015 -0600

    no-mtab (-n) mount option ignore next mount option
    
    The -n option does not take any arguments. It seems like this shift is
    removing the next option. On my CentOS 7 system, automount calls
    mount.glusterfs with the parameters:
     host:/volume /mountpoint -n -o rw,acl,_netdev
    This causes the -o option to be siliently ignored.
    
    Change-Id: Ice3c877f6ab346b04292e3dfed968d04d15077a5
    BUG: 1297195
    Signed-off-by: James Augustine <jcaugust81@gmail.com>
    Reviewed-on: http://review.gluster.org/12988
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit d5d6918ce7dc9f54496da435af546611dfbe7d5c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Dec 30 14:56:12 2015 +0530

    features/bitrot: add check for corrupted object in f{stat}
    
    Check for corrupted objects is done bt bitrot stub component
    for data operations and such fops are denied processing by
    returning EIO. These checks were not done for operations such
    as get/set extended attribute, stat and the likes - IOW, stub
    only blocked pure data operations.
    
    However, its necessary to have these checks for certain other
    fops, most importantly stat (and fstat). This is due to the
    fact that clients could possibly get stale stat information
    (such as size, {a,c,m}time) resulting in incorrect operation
    of the application that rely on these fields. Note that, the
    data that replication would take care of fetching good (and
    correct) data, but the staleness of stat information could
    lead to data inconsistencies (e.g., rebalance, tier).
    
    Change-Id: I5a22780373b182a13f8d2c4ca6b7d9aa0ffbfca3
    BUG: 1296399
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13120
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1cdea236601ebe872d432ff9ee63833dfac0d5cb
Author: Michael Adam <obnox@samba.org>
Date:   Mon Jan 4 16:45:19 2016 +0100

    hook-scripts: remove outdated comment from C29CTDB start scipt
    
    This script does not change Samba's config any more.
    
    Change-Id: Ie6001f9a49006f95b291e24252dc362f2a7db14c
    BUG: 1295504
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/13168
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit f9caa5ef879c68252583501a5c277a550791d83f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Nov 4 14:55:27 2015 -0500

    extras: add script to analyze regression-test failures
    
    Often a test will fail quite frequently, but not so frequently that it
    will fail twice in a row for the same patch.  This allows it to "fly
    beneath the radar" for quite a long time, slowing project-wide progress
    until somebody crawls through the logs looking for patterns.  This patch
    adds a script to automate some of that process.
    
    Change-Id: Ic74fbf6b0bfa34bffd9cb109fd51db019053e2cc
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/12510
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6019e988a3ec40fb78127dce577be125ac23af98
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Dec 30 21:07:54 2015 +0530

    tests: use SIGKILL in cleanup, not SIGTERM
    
    Sending a SIGTERM to test processes and waiting
    a second for them to gracefully exit before
    sending a SIGKILL seems like a waste of time.
    
    Just send SIGKILL directly.
    
    Change-Id: Icc73b07eae47876ba41955793a8daf77a964a0e0
    BUG: 1294826
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13121
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit eb0d9513ece40c5d4cb7f3bae13874bbfe4fcff8
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Dec 28 10:57:53 2015 -0500

    cluster/tier: allow db queries to be interruptable
    
    A query to the database may take a long time if the database
    has many entries. The tier daemon also sends IPC calls to the
    bricks which can run slowly, espcially in RHEL6. While it is
    possible to track down each such instance, the snapshot
    feature should not be affected by database operations. It requires
    no migration be underway. Therefore it is okay to pause tiering
    at any time except when DHT is moving a file.  This fix implements
    this strategy by monitoring when control passes to DHT to
    migrate a file using the GF_XATTR_FILE_MIGRATE_KEY trigger. If it
    is not, the pause operation is successful.
    
    Change-Id: I21f168b1bd424077ad5f38cf82f794060a1fabf6
    BUG: 1287842
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/13104
    Reviewed-by: Joseph Fernandes
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b9d2a383a265f1552d6bad0a22c92f4e7204dd85
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 30 15:25:30 2015 +0530

    features/bitrot: Fail node-uuid getxattr if file is marked bad
    
    If xattr is node-uuid and the inode is marked bad, fail getxattr
    and fgetxattr with EIO. Returning EIO would result in AFR to
    choose correct node-uuid coresponding to the subvolume where
    the good copy of the file resides.
    
    Change-Id: I45a42ca38f8322d2b10f3c4c48dc504521162b42
    BUG: 1294786
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13116
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 33ca7a7384491bf78f1c905a9085c17415eb1d91
Author: vmallika <vmallika@redhat.com>
Date:   Tue Dec 22 16:32:49 2015 +0530

    quota: handle quota xattr removal when quota is enabled again
    
    When a quota is disable and enabled again before completing
    the cleanup operation, this can remove the new xattrs
    and quota accounting can become wrong
    
    Remove removing the xattr, check if quota enabled again and the
    xattr is new
    
    Change-Id: Idda216f1e7346a9b843dbc112ea3e6faa9c47483
    BUG: 1293601
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13065
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit ea42ffa13c00263a574226626d30749b6b0f3776
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Jan 5 22:16:31 2016 +0530

    performance/write-behind: maintain correct transit size in case of
    short writes.
    
    1. Imagine a write when cache is filled with failed syncs.
    2. This write won't be unwound since cache size has exceeded
    configured limit.
    3. With trickling-writes on by default, the last write request wont be
    considered for winding when there is non zero in-transit size.
    4. There was a bug in accounting of in-transit size when winds
    resulted in short writes. Due to this bug, in-transit size used to be
    non-zero even when there are no syncs in progress.
    5. Due to 3 and 4, current write request won't be wound till there is
    another write or fsync or flush from application. But application
    can't do any other fop till current write request is unwound. This
    resulted in deadlock and hence application would be hung in 'D'
    state.
    
    This patch fixes bug in accounting of in-transit size during short
    writes.
    
    Change-Id: I04ce8bb510efaaed7623cac38d69b32dbc3730ce
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1279730
    Reviewed-on: http://review.gluster.org/13177
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cae9a5b3a1868a8bae25cd1ba9ebb41d698f39e5
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Dec 30 18:15:04 2015 +0530

    vagrant-test: Exit on critical errors
    
    There were quite a few places where exiting the script
    made more sense.
    
    More debug messages have been added.
    
    Move back to top directory after the script is complete.
    
    Change-Id: I2a66ee3a68c41a3acd0b7168c56b801fb5567e5f
    BUG: 1291537
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13175
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Michael Adam <obnox@samba.org>

commit a2119ef0f18d51500f5b496caf8dfd8f192dd490
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jan 5 07:52:25 2016 -0500

    dht: missleading indendentation, gcc-6
    
    gcc-6 now has -Wmisleading-indentation as part of -Wall.
    
    compiling with gcc-6 gives this warning.
    
    ...
    dht-diskusage.c: In function ‘dht_subvol_has_err’:
    dht-diskusage.c:361:33: warning: statement is indented as if it were
    guarded by... [-Wmisleading-indentation]
                                     goto out;
                                     ^~~~
    
    dht-diskusage.c:358:25: note: ...this ‘if’ clause, but it is not
                             if (conf->decommissioned_bricks[i] &&
                             ^~
    ...
    
    Inspection of the source shows that without braces the loop is
    terminated prematurely.
    
    Change-Id: Ica48a8c59ee5d0a206797827d7920259d33b47ec
    BUG: 1295784
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13176
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1e779acec75842b0e8d5a34ac2ea52f9caeff4d1
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Dec 8 16:28:39 2015 +0530

    api: Fix errno being set to EINVAL even on success
    
    BUG: 1289068
    Change-Id: I7905ac70a537f23e1844c097a24eaa6cb762fb82
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/12909
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 45b1bf53da028b92ea7fc3f21a53f2a3cb0d8b0c
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Sat Jan 2 23:34:54 2016 +0530

    tier/create: store TIER_LINKFILE_GFID in xattr dictionary
    
    In tier_create, a new key TIER_LINKFILE_GFID was introduced to
    avoid a race in stale linkfile deletion. Storing this key in
    xattr dictionary instead of using local->params dictionary.
    
    Because local->params dictionary was also used to create the file
    before stale linkfile deletion, that leads posix_create to fail,
    trying to set the added key as extended attributes
    
    Change-Id: I24fecb62b47bee65a1e86103925a67d13304c5df
    BUG: 1290677
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13130
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 57ef73821c8062e1503926751fd72bdad7506c86
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Dec 28 10:13:30 2015 -0500

    cluster/tier: check watermark during migration
    
    Currently we check the watermarks only before a cycle
    begins. We should also check the hot tier's fullness
    against the watermarks during the migration so the watermark
    is not exceeded as files are promoted.
    
    Change-Id: I2ff87a1c308d64fbdca14bbdf55f3ec3007290ae
    BUG: 1293932
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/13103
    Reviewed-by: Joseph Fernandes
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit 50d14b2aec654eaf95a467bc12a8c6fd396cfb0a
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Dec 30 14:55:48 2015 +0530

    cluster/tier: Additional details in error messages
    
    Added file path/gfid when available to the tier log
    messages to make debugging easier.
    
    Change-Id: I22dda329367df2b846dcf254594312c997b66083
    BUG: 1273043
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/13114
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit fa4f583e469c065b4e1fb7ddfadfd14e1e6d62ae
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Dec 29 12:42:30 2015 +0530

    tier/glusterd: tier daemon not updating the status
    
    Tier process is not updating the status when the process killed
    mnually.
    
    Change-Id: Ia5ea903af78ff3582da2242e6058f11c71923fab
    BUG: 1294600
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13107
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 96f4ec28a80c013b71aa723efaa5810d2eacdd7f
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Dec 30 13:23:33 2015 +0530

    wb: remove inline keyword
    
    When compiled with -Werror flag gcc throws the following
    error:
    
    ‘iov_length’ is static but used in inline
    function ‘__wb_modify_write_request’ which is not static.
    Let gcc decide what functions to inline and remove the inline
    keyword.
    
    Change-Id: I6d832596eefcf08306634936e11d2c8d4b8f9ccd
    BUG: 1279730
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/13113

commit e34935e83c1e2fdc20bfe826531bb61276a41de8
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Dec 28 14:32:50 2015 +0530

    Tier : typo in tier help
    
    Change-Id: I75bca55901849cf725e02c782f75ff1e6054fddd
    BUG: 1294448
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/13097
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 4b52e6c0d73937c93464a1db15027796e3ecbd68
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Dec 28 19:31:36 2015 +0530

    tier/create: Dynamically allocate gfid memory
    
    Currently we are storing the memory as a static pointer.
    There is a chance to go that variable in out of scope.
    So we should allocate in Dynamic way.
    
    Change-Id: I096876deb8055ac3a44681599591a0a032bc0c24
    BUG: 1290677
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13102
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 137b11d616c6086b05c32089903a39334999a76e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Dec 23 23:37:54 2015 +0530

    tier/unlink: symlink failed to unlink
    
    during unlink of a file, we will get stat just after
    deleting the file, to see if the file is under migration or not.
    
    but this stat call will fail for symlink if the actual file
    was deleted.
    
    So it is better not to send stat request from client if it is
    a symlink as we are not migrating symlink.
    
    Change-Id: Idc033b24fa3522b5261e579889d2195b43419682
    BUG: 1293963
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13074
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 72e736613169b778daa44e932443aaf2436432d9
Author: vmallika <vmallika@redhat.com>
Date:   Mon Dec 28 17:33:26 2015 +0530

    quota: limit xattr for subdir not healed on newly added bricks
    
    DHT after creating missing directory, tries to heal the
    xattrs. This xattrs operation fails as INTERNAL FOP key was not set
    
    Change-Id: I819d373cf7073da014143d9ada908228ddcd140c
    BUG: 1294479
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/13100
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 4c1b66720121ca97ccfac3e09f93519f2f07ddfd
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Dec 24 15:22:05 2015 +0530

    afr: Fix excessive logging in afr_accuse_smallfiles()
    
    Commit 2b7226f9d3470d8fe4c98c1fddb06e7f641e364d did not check for the
    validity of a dict before doing a dict_get. Fix that.
    
    Change-Id: Ie21f4da19256b17196f242cd8fd5bb76b0a69c1e
    BUG: 1294053
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13077
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e4de816ae126b62906afcc1ce1216500b517e222
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Tue Dec 22 12:05:39 2015 +0530

    cli: should not dereference NULL pointer while printing bitrot scrub status
    
    When user execute bitrot scrub status command and scrubber is
    pending to do scrubbing then value of last_scrub time will be NULL.
    Currently cli is dereferencing NULL pointer in this case, That might
    lead to crash.
    
    Fix is to use proper check condition while printing scrub status.
    
    Change-Id: I3c4be8e25d089451c6ab77b16737c01d0348ee70
    BUG: 1293558
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/13060
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit a370013898585a87657ae41e4f266da5d98cc5d2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 21 12:07:51 2015 +0530

    tests: handle bad objects during lookup/inode_refresh
    
    Change-Id: I1848f0e9243c9376e0deba6738757350fe8b704a
    BUG: 1290965
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13044
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 78305ce9604329250dd4a9f2335587957d71c701
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Nov 24 18:18:01 2015 +0530

    tests: Introduce a Vagrant VM based test environment
    
    This introduces a mechanism using which a developer
    could easily test the Gluster code in a VM environment.
    
    Also, it will help bring uniformity in the environments
    used by various developers.
    
    How to use:
    1. git checkout -b custom-branch-name
    2. Make changes
    3. Execute ./run-tests-in-vagrant.sh
    
    What happens in the background:
    1. A new directory is created:
        tests/vagrant/vagrant-custom-branch-name
    
       It will serve as the Vagrant dir which has the
       Vagrantfile and related ansible playbooks.
    
       The VM is started using Vagrant and provisioned
       using ansible.
    
    2. The source dir is recursively copied over to the
       VM under /home/vagrant/glusterfs.
    
    3. Gluster is source installed in VM.
    
    What happens in the foreground:
    1. run-tests.sh is executed in VM using ssh and output is displayed
       in the same terminal with option to use ctrl-c to interrupt the test
       midway. The VM would still persist and you could ssh into it.
    
    Also, you can checkout a different branch elsewhere and execute
    run-tests-in-vagrant.sh there to get another VM which would
    execute tests on that code.
    
    If you wish to make some changes in the code, you could:
    a. Change the code in host and run the script again to repeat
       the whole process.
    OR
    b. vagrant ssh into the VM and make the changes in the VM.
    
    Co-authored-by: Kaushal M <kaushal@redhat.com>
    Co-authored-by: Michael Adam <obnox@samba.org>
    
    Change-Id: Ic87801172c8b614cdecbdf2a765e1b3370a5faf7
    BUG: 1291537
    Signed-off-by: Michael Adam <obnox@samba.org>
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12753
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 7ab8a1a3f4510a284b1686302624ec4252c95a6f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Dec 23 13:57:14 2015 +0100

    build: use 'make install' to install the hook scripts
    
    The installation should be the same on all distributions, and doing
    manual installation of files in the .spec is very ugly. This change adds
    the rules so that 'make install' places the hook scripts in the right
    location.
    
    Also, the hook script(s) for NFS-Ganesha should be part of the
    glusterfs-ganesha sub-package and got moved there.
    
    BUG: 1174765
    Change-Id: Iba25a7a5112c7d40db4c10ff4a5ac7a5fb4f7c4e
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/13072
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 618f130ed0e653566db34878b36a2db34dcd6723
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Fri Dec 25 08:11:54 2015 -0500

    glusterfs.spec.in: use %global per Fedora pkg guidelines
    
    ref. recent emails in fedora-devel ml
    
    See:
      https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#.25global_preferred_over_.25define
    and the thread beginning at
      https://www.redhat.com/archives/fedora-packaging/2009-May/msg00095.html
    
    Also fix a couple instances of %if ... %else ... %endif indentation
    to be consistent with the rest of the .spec
    
    Change-Id: Iaf7332fd8601d78bc0d8249033cff12a452654bf
    BUG: 1294209
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13079
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 88bf33555371ae01dd297aecf8666d7121309b80
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Dec 11 15:15:53 2015 +0530

    glusterd: correct ret code in glusterd_volume_status_copy_to_op_ctx_dict
    
    This patch is to supress the error log of Failed to aggregate rsp_dict where the
    above function returns a non zero ret which is not required
    
    Change-Id: If331980291bd369690257215333cea175e2042ec
    BUG: 1290734
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12950
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>

commit f624abd6885752eeaa8d07101ff00f52af48de26
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Dec 17 11:13:36 2015 +0530

    glusterd: reduce friend update flood
    
    When in a befriended state, glusterd would broadcast friend updates to
    all other peers whenver a ACC or LOCAL_ACC event occurred.
    
    When a downed glusterd came back up and established connections again,
    this lead to a flood of friend updates to happen on the order of N^2 (N
    is the number of peers in the cluster)
    
    In larger clusters this was problematic, and could lead to very long
    times for the cluster to settle down when a peer came back up. Multiple
    peers coming back up at the same time would compound the problem.
    
    Broadcasting of friend updates doesn't have much use in places other
    that during a peer probe. Instead of broadcasting friend updates on
    connection re-establishment, updates can just be exchanged between the
    peers involved in the connection.
    
    This patch changes the glusterd friend state-machine to send updates
    only to the required peer for ACC or LOCAL_ACC events when in befriended
    state. The number of updates sent now is in the order of N.
    
    For a 10 node cluster, the number of updates reduced by 5 times. When
    creating the 10 node cluster, the updates reduced from ~500 to ~150.
    When a glusterd restarted, the number of exchanges reduced from ~160 to
    ~35.
    
    BUG: 1292749
    Change-Id: Ib6072090c7069b081d018cdaa3dc878819ab1d18
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/12999
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7f61095ddd118d4475df070fbf1f4117bf651ece
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Dec 16 16:18:29 2015 +0530

    Tier: "tier start force" command implementation
    
    The start command doesnt restart the tier deamon if the deamon
    is running at one node. hence to bring up the tierd on the nodes
    where the deamon is down, the force command is implemented.
    It skips the check for tierd running.
    
    Change-Id: I0037d3e5ecfe56637d0da201a97903c435d26436
    BUG: 1292112
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12983
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 430ad405294993ebb16387232281cc5a4f854c75
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Dec 16 21:09:22 2015 +0530

    cluster/dht : Ftruncate on migrating file fails with EINVAL
    
    What:
    If dht_open is called on a migrating file after the inode_ctx is set,
    subsequent FOPs on that fd do not open the fd on the dst subvol.
    This is seen when the open-ftruncate-close sequence is repeatedly
    called on a migrating file.
    A second call to the sequence described above causes dht_truncate_cbk
    to call dht_truncate2 as the dht_inode_ctx was already set by the first
    call. As dht_rebalance_in_progress_check is not called, the fd is not
    opened on the dst subvol.
    On a distributed-replicate volume, this causes AFR to
    open the fd using afr_fix_open, but with the wrong flags, causing
    posix_ftruncate to fail with EINVAL.
    The fix: We require fd specific information to make a decision while
    handling migrating files.
    Set the fd_ctx to indicate the fd has been opened on the dst subvol
    and check if it has been set while processing Phase1/Phase2 checks
    in the FOP callback functions.
    
    Change-Id: I43cdcd8017b4a11e18afdd210469de7cd9a5ef14
    BUG: 1284823
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12985
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit e62c0fe19b113d42db5e0f80fa7cbb82f2f88190
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Fri Dec 18 07:44:45 2015 -0500

    build: export minimum symbols from xlators for correct resolution
    
    Revisiting http://review.gluster.org/#/c/11814/, which unintentionally
    introduced warnings from libtool about the xlator .so names.
    
    According to [1], the -module option must appear in the Makefile.am
    file(s); if -module is defined in a macro, e.g. in configure(.ac),
    then libtool will not recognize that this is a module and will emit a
    warning.
    
    [1]
    http://www.gnu.org/software/automake/manual/automake.html#Libtool-Modules
    
    Change-Id: Ifa5f9327d18d139597791c305aa10cc4410fb078
    BUG: 1248669
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/13003
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 76f1680a2de05420934e131f934f3895fbe50db8
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Dec 7 10:22:05 2015 -0500

    core: add preadv, pwritev, pread, pwrite syscall wrappers
    
    add additional system calls plus pick up a couple missed unwrapped
    system calls that seem to have slipped into the master branch.
    
    Change-Id: If268ccd5e9a139ac3ffd38293c67cd2f62ea5b58
    BUG: 1289258
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12895
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 439de31320315872d988720991e9baaead8712db
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Dec 15 18:29:06 2015 +0530

    ctr/sql: Providing for vol set for sqlcachesize and sqlWALsize and skip recording path
    
    1. Providing vol set option for cache size and wal autocheck point
       so that performance can be tuned.
    2. Removed recording of file path in the db. Trimming database columns.
       Path need not be stored in the db, as PARGFID, GFID, Basename is suffice
       to derive the path during migration.
    
    Change-Id: I2cb590451a6d244bc91fe66c6dbffe2c2059dfb8
    BUG: 1293034
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12972
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 074158e7081ff0118c719aac7cf1bcde92ee8f7d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Dec 22 12:29:32 2015 +0530

    geo-rep: Fix getting subvol count
    
    Tiering doesn't support disperse volume as hot tier,
    hence xml output doesn't give 'hotdisperseCount'.
    Remove the usage of 'hotdisperseCount' in geo-rep
    and return 0 instead.
    
    Change-Id: I736e29257de085a25e38eb02959caad3465ebcda
    BUG: 1292084
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/13062
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vivek
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit d3fd13688f850e58bfa517a4c2d17e8fa4343dcf
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Dec 10 20:13:22 2015 +0530

    tier:delete the linkfile if data file creation fails
    
    If we are creating data file in a hot subvolume
    then we will create a linkfile in cold subvolume.
    Linkfile creation happens first. If linkfile creation
    was successful and data file creation failed, then
    linkfile in cold subvolume will become stale.
    
    This patch will delete the linkfile as well, if data
    file creation fails.
    
    Also this code duplicates dht_create to make tier_create
    
    Change-Id: I377a90dad47f288e9576c7323b23cf694a91a7a3
    BUG: 1290677
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12948
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 3fcead2de7bcdb4e1312f37e7e750abd8d9d9770
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Nov 17 12:57:54 2015 +0530

    performance/write-behind: retry "failed syncs to backend"
    
    1. When sync fails, the cached-write is still preserved unless there
       is a flush/fsync waiting on it.
    
    2. When a sync fails and there is a flush/fsync waiting on the
       cached-write, the cache is thrown away and no further retries will
       be made. In other words flush/fsync act as barriers for all the
       previous writes. The behaviour of fsync acting as a barrier is
       controlled by an option (see below for details). All previous
       writes are either successfully synced to backend or forgotten in
       case of an error. Without such barrier fop (especially flush which
       is issued prior to a close), we end up retrying for ever even after
       fd is closed.
    
    3. If a fop is waiting on cached-write and syncing to backend fails,
       the waiting fop is failed.
    
    4. sync failures when no fop is waiting are ignored and are not
       propagated to application. For eg.,
       a. first attempt of sync of a cached-write w1 fails
       b. second attempt of sync of w1 succeeds
    
       If there are no fops dependent on w1 are issued b/w a and b,
       application won't know about failure encountered in a.
    
    5. The effect of repeated sync failures is that, there will be no
       cache for future writes and they cannot be written behind.
    
    fsync as a barrier and resync of cached writes post fsync failure:
    ==================================================================
    Whether to keep retrying failed syncs post fsync is controlled by an
    option "resync-failed-syncs-after-fsync". By default, this option is
    set to "off".
    
    If sync of "cached-writes issued before fsync" (to backend) fails,
    this option configures whether to retry syncing them after fsync or
    forget them. If set to on, cached-writes are retried till a "flush"
    fop (or a successful sync) on sync failures. fsync itself is failed
    irrespective of the value of this option, when there is a sync failure
    of any cached-writes issued before fsync.
    
    Change-Id: I6097c9257bfb9ee5b15616fbe6a0576ae9af369a
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1279730
    Reviewed-on: http://review.gluster.org/12594

commit d73f5c9eae0f5c8796598fa1930844c15c2c37d4
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Dec 15 19:55:05 2015 +0530

    libgfchangelog: Allocate logbuf_pool in master xlator
    
    The master xlator needs to allocate 'logbuf_pool'
    else 'gf_msg' fails with EINVAL.
    
    Change-Id: I6b2d3450250de7e77126d12b75b0dbc4db414bfb
    BUG: 1292463
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12997
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 105dfa9f562b177a6faf4a0958e6d1b5840cee94
Author: vmallika <vmallika@redhat.com>
Date:   Wed Dec 9 13:13:17 2015 +0530

    quota: fix backward compatibility of new quota volinfo option
    
    quota-version features is implemented for 3.7.6
    please see below patch for more details:
    http://review.gluster.org/#/c/12386
    
    As part of this feature, new volume info option 'quota-version'
    was introduced, this can cause check-sum problem
    when a one of the node in a cluster is upgraded to 3.7.6
    (heterogeneous cluster)
    
    So do a OP_VERSION check when storing this option
    in volume info
    
    Change-Id: Ic5b03a1e3f1236b645a065b1fadee7950307e191
    BUG: 1283178
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12642
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 683c880a02086effc5009a8420289b445ea423f0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Dec 17 17:41:08 2015 +0530

    cluster/afr: Fix data loss due to race between sh and ongoing write
    
    Problem:
    
    When IO is happening on a file and a brick goes down comes back up
    during this time, protocol/client translator attempts reopening of the
    fd on the gfid handle of the file. But if another client renames this
    file while a brick was down && writes were in progress on it, once this
    brick is back up, there can be a race between reopening of the fd and
    entry self-heal replaying the effect of the rename() on the sink brick.
    If the reopening of the fd happens first, the application's writes
    continue to go into the data blocks associated with the gfid.
    Now entry-self-heal deletes 'src' and creates 'dst' file on the sink,
    marking dst as a 'newentry'.  Data self-heal is also completed on 'dst'
    as a result and self-heal terminates. If at this point the application
    is still writing to this fd, all writes on the file after self-heal
    would go into the data blocks associated with this fd, which would be
    lost once the fd is closed. The result - the 'dst' file on the source
    and sink are not the same and there is no pending heal on the file,
    leading to silent corruption on the sink.
    
    Fix:
    
    Leverage http://review.gluster.org/#/c/12816/ to ensure the gfid handle
    path gets saved in .glusterfs/unlink until the fd is closed on the file.
    During this time, when self-heal sends mknod() with gfid of the file,
    do the following:
    link() the gfid handle under .glusterfs/unlink to the new path to be
    created in mknod() and
    rename() the gfid handle to go back under .glusterfs/ab/cd/.
    
    Change-Id: I86ef1f97a76ffe11f32653bb995f575f7648f798
    BUG: 1292379
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/13001
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit aa017dc1527c30fedb4b76cfb6c7601b2ec20c43
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Dec 22 08:50:26 2015 +0530

    tier/snap : Adding tier-snapshot.t to bad test
    
    ./tests/basic/tier/tier-snapshot.t to bad test
    
     On RHEL6 the pause tier mechanism times out due to slow IPC calls
     between the tier daemon and brick process. A workaround may be to
     increase the timeout or improve the speed of RHEL6
    
    Change-Id: I5af6123923416e611672ffe2aaea3f0dd7964dd9
    BUG: 1293523
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/13056
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 4bfbabfdd698e93a1dc1aad5590ed18f10936c55
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 21 10:09:53 2015 +0000

    afr: warn if pending xattrs missing during init()
    
    Since commit 6e635284a4411b816d4d860a28262c9e6dc4bd6a
    (glusterfs-3.7.7), the afr pending xattrs are stored in the volfile and used
    by afr when it initializes. If a cluster is upgraded, prevent afr from loading
    until the op-version has been bumped up to 3.7.7 and the volfiles have been
    regenerated using a volume set command.
    
    Without this fix, AFR will crash when initialzing.
    
    Change-Id: I14249dedb3f2f77cd754d78d8a9a70fdc5fc8c10
    BUG: 1293293
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/13038
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7237f8f0d72743d2522b7db1be928c5016713c59
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Dec 21 14:18:26 2015 +0530

    tier/unlink: open fd for special file for fdstat
    
    DUring unlink of a file, dht request stat to see whether
    the file is under migration or not. But in posix_unlink
    currently we are opening for regular files. so the fdstat
    for special files are failing with EBAD
    
    Change-Id: Ic0678e42e7701c3dffb91d98272e664b0fc646b5
    BUG: 1293256
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/13034
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 3a094f1de03b3da8cdff650c14e46aab87e1905b
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Dec 16 15:28:57 2015 -0500

    cluster/tier: do not block in synctask created from pause tier
    
    We had run sleep() in the pause tier callback. Blocking within
    a synctask is dangerous. The sleep() call does not inform
    the synctask scheduler that a thread is no longer running.
    It therefore believes it is running. If a second synctask already
    exists, it may not be able to run. This occurs if the thread
    limit in the pool has been reached.
    
    Note the pool size only grows when a synctask is created, not
    when it is moved from wait state to run state, as is the case
    when an FOP completes. When the tier is paused during migration,
    synctasks already exist waiting for responses to FOPs to the
    server with high probability.
    
    The fix is to yield() in the RPC callback, which will place
    the synctask into the wait queue and free up a thread for the
    FOP callback. A timer wakes the callback after sufficient
    time has elapsed for the pause to occur.
    
    Change-Id: I6a947ee04c6e5649946cb6d8207ba17263a67fc6
    BUG: 1267950
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12987
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit d2f48214d436be633efb1136ee951b0736935143
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Dec 16 17:16:36 2015 +0530

    tier: Demotion failed if the file was renamed when it was in cold
    
    During migration if the file is present we just open the file
    in hashed subvol. Now if the linkfile present on hashed is just
    linkfile to another subvol, we actually open in hashed subvol.
    
    But subsequent operation will go to linkto subvol ie,
    to non-hashed subvol. This operation will get failed
    since we haven't opened d on non-hashed.
    
    Change-Id: I9753ad3a48f0384c25509612ba76e7e10645add3
    BUG: 1292067
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12980
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 9691ea1b203c82386ececc3c5ea9adad39304d7b
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Dec 15 13:32:29 2015 +0530

    tier/dht : Properly free file descriptors during data migration
    
    While tier migration, free src and dst fd's when create of
    destination or open of source fails.
    
    Change-Id: I62978a669c6c9fbab5fed9df2716b9b2ba00ddf1
    BUG: 1291566
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12969
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit b0e126d0edf10946701c2fd4f0f1cf8c7b07eda1
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Wed Dec 16 18:04:55 2015 +0530

    cli/xml: display correct xml output of tier volume
    
    Currently When hot tier type is distributed-replicate and cold tier
    type is disperse volume then #gluster volume info --xml command is
    not giving its correct output. In case of HOT tier case its displaying
    wrong volume type.
    
    With this fix it will show correct xml output for tier volume
    irrespective of all the type of the volume's.
    
    Change-Id: If1de8d52d1e0ef3d0523163abed37b2b571715e8
    BUG: 1292084
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12982
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit d677e195cb85bef28fcd9e2f45e487c9ea792311
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Dec 17 12:39:30 2015 +0530

    geo-rep: Fix getting subvol number
    
    Fix getting subvol number if the volume
    type is tier. If the volume type was tier,
    the subvol number was calculated incorrectly
    and hence few of workers didn't become ACTIVE
    resulting in files not being replicated from
    corresponding brick. This patch addresses
    the same.
    
    Change-Id: Ic10ad7f09a0fa91b4bf2aa361dea3bd48be74853
    BUG: 1292084
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12994
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2b7226f9d3470d8fe4c98c1fddb06e7f641e364d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat Dec 12 11:49:20 2015 +0530

    afr: handle bad objects during lookup/inode_refresh
    
    If an object (file) is marked bad by bitrot, do not consider the brick
    on which the object is present  as a potential read subvolume for AFR
    irrespective of the pending xattr values.
    
    Also do not consider the brick containing the bad object while
    performing afr_accuse_smallfiles(). Otherwise if the bad object's size
    is bigger, we may end up considering that as the source.
    
    Change-Id: I4abc68e51e5c43c5adfa56e1c00b46db22c88cf7
    BUG: 1290965
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12955
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a99bbccbb5e3087b9b8b687ee2be8887eeac0d08
Author: Anuradha Talur <atalur@redhat.com>
Date:   Wed Dec 9 14:50:41 2015 +0530

    heal : Do not print heal count on ENOTCONN
    
    When a brick is not reachable due to ENOTCONN,
    there are no entries gathered and this information
    should not be printed.
    It is a bug intorduced due to commit
    9c378026e9561595586a817fee0b439e2c863a22, fixing it.
    
    Change-Id: I45559a9560c297854ea6b4177f86e0be30dc6b78
    BUG: 1250803
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12919
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d5a9e765543fd6eec5d522e4f3f062bef97aefed
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 7 18:03:03 2015 +0530

    afr: refresh inode using fstat
    
    For fd based operations (fgetxattr, readv etc.) if an inode refresh is
    required, do so using fstat instead of lookup. This is because the file
    might have been deleted by another client before refresh but posix
    mandates that FOPS using already open fds must still succeed.
    
    Change-Id: Id5f71c3af4892b648eb747f363dffe6208e7ac09
    BUG: 1285230
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12894
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 9644769ea174646eaf18b8a41873f67928be9c8d
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Dec 15 19:30:45 2015 -0500

    cluster/tier: fix tier-max-files bookeeping and help
    
    The option tier-max-files represents the maximum number
    of files trasferred by a node in a gives cycle. Fix help message
    to reflect the "per node" aspect. The code transferred one
    more file per cycle than the given value.
    
    Also change the default values of max file and max bytes to
    very large values, effectively we will not throttle migration
    unless the administrator requests it via CLI.
    
    Change-Id: Ic2949ed3d8c35afe7c9ae4db72195603cfb2e28f
    BUG: 1292671
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12984
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3151194fad1aed3ab340b53aeeb4e8d131538d12
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Dec 9 13:46:17 2015 +0530

    geo-rep: Symlink Rename issue
    
    If ENTRY creation failed for symlink in Slave and symlink
    renamed in Master. If Source not exists to Rename in Slave
    Geo-rep interprets as Create of Target file. Geo-rep sends blob
    of regular file to create symlink instead of sending blob of
    symlink.
    
    With this patch, Geo-rep identifies symlink and sends respective
    blob.
    
    BUG: 1289859
    Change-Id: If9351974d1945141a1d3abb838b7d0de7591e48e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/12917
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Tested-by: Milind Changire <mchangir@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit ce3ff7e328483dffdae6ae2914924bc2380db67e
Author: Michael Adam <obnox@samba.org>
Date:   Fri Dec 11 00:37:13 2015 +0100

    hook-scripts: fix S30Samba scripts on systemd systems
    
    /etc/init.d/smb does not exist on systemd systems.
    Using "service smb <COMMAND>" is the portable way.
    It calls init scripts on sysv systems, and redirects
    to systemctl on systemd systems.
    
    Change-Id: I7146c9998a51d8b170d3321f3477e92704ae7615
    BUG: 1290604
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12945
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 692ccdbd4d11311a1967d62227666d2c473ea233
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Dec 2 04:59:55 2015 -0500

    cluster/dht: Handle failure in getxattr
    
    Problem: Currently even if we have received xattrs from any one of
    the subvolume, we unwind with error in case the last subvol (which
    unwinds) received a negative response.
    
    To handle the case check if any of the subvolume has received
    a response and pass it down.
    
    Change-Id: Ia12a1f9671a6764f7550e6dc223324b1039fcc51
    BUG: 1287539
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12845
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b5de382afa8c5777e455c7a376fc4f1f01d782d1
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Nov 30 19:02:54 2015 +0530

    tier:unlink during migration
    
    files deleted during promotion were not deleting as the
    files are moving from hashed to non-hashed.
    
    On deleting a file that is undergoing promotion,
    the unlink call is not sent to the dst file as the
    hashed subvol == cached subvol. This causes
    the file to reappear once the migration is complete.
    
    This patch also fixes a problem with stale linkfile
    deleting.
    
    Change-Id: I4b02a498218c9d8eeaa4556fa4219e91e7fa71e5
    BUG: 1282390
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12829
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 27c16d6da82876a689dfba53b8d45c3a3a657954
Author: Michael Adam <obnox@samba.org>
Date:   Wed Dec 9 18:57:59 2015 +0100

    hook-scripts: don't let ctdb script change samba config
    
    There are several reasons why the behaviour in
    the hook scripts was bad:
    
    1. A samba installation is clustered or non-clustered.
       That does not change because of the availability
       of the CTDB lock-volume. If the lock-volume is not
       available (and hence CTDB is not available or not
       healthy), then Samba won't be operational. But turning
       it into a non-clustered Samba-installation can in
       the worst case lead to data corruption if clients
       manage to access the same files (on share volumes).
       Hence 'clustering = yes/no' in Samba's config should
       not be touched.
    
       In particular, Samba should not be stopped/started by
       the hook script. If needed, then ctdb will take care
       of it.
    
    2. Changing the idmap configuration is potentially
       dangerous as well. In particular the used tdb2
       backend is legacy nowadays and should not be used
       any more in new installs. (I stems from the times
       when ctdb could not host persistent databases.)
       Changing the idmap can result in loss of access
       to files or in giving access to files where it is
       not intended.
    
    3. The pattern used for detecting need for change is
       fragile. It may or may not play well possible
       manual changes to smb.conf.
    
    This change removes the parts that change the smb.conf
    file and start or stop Samba from the S29CTDB* hook scripts.
    
    Change-Id: I72f7aabafa8f089da4531fca2572a72c22825bcc
    BUG: 1290151
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12930
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 5e36564754e2d83a7666066f4da7f148960a5694
Author: Jiffin Tony Thottan <jthottan@gmail.com>
Date:   Mon Dec 14 15:29:21 2015 +0530

    nfs : Inform client to perform extra GETATTR call for 'T' files
    
    Due to the changes from http://review.gluster.org/#/c/12722/,
    for tier volume the readirp will be send only to cold subvol,
    therefore the resulting list may contain 'T' files. For those
    files, by performing additional getattr call will populate the
    attributes correctly. This check should be based on inode value
    passed from the readdirp(both T files and directory have NULL
    value) and skip directory in the same.
    
    Change-Id: Ieb6724b05301cdbf0a0ef15ad9db51014faa0457
    BUG: 1291212
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12960
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit f853ed9c61bf65cb39f859470a8ffe8973818868
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Nov 25 15:25:26 2015 +0530

    features/bit-rot-stub: delete the link for bad object in quarantine directory
    
    When the bad object is deleted (as of now manually from the backend itself),
    along with its gfid handle, the entry for the bad object in the quarantne
    directory is left as it is (it also can be removed manually though). But the
    next lookup of the object upon not finding it in the backend, sends forget on
    the in-memory inode. If the stale link for the gfid still exists in the
    quarantine directory, bir-rot-stub will unlink the entry in its forget or in
    the next failed lookup on that object with errno being ENOENT.
    
    Change-Id: If84292d3e44707dfa11fa29023b3d9f691b8f0f3
    BUG: 1285241
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/12743
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 4eb7c968a682e59d97efcbc2afa41690dfdd22a2
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Dec 15 14:39:25 2015 +0530

    tier/glusterd: Only positive values for freq-thresholds
    
    Fixed error handling for validation for freq-thresholds
    
    Change-Id: Ibe3a9752ac0b525b0c8c0d6c4b4e4d694bd91b88
    BUG: 1291603
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12970
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 7ba6469eee3118cc4ece905d2538ef778320ae63
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Dec 15 18:48:20 2015 +0530

    cluster/afr: During name heal, propagate EIO only on gfid or type mismatch
    
    When the disk associated with a brick returns EIO during lookup, chances are
    that name heal would return an EIO because one of the syncop_XXX() operations
    as part of it returned an EIO. This is inherently treated by afr_lookup_selfheal_wrap()
    as a split-brain and the lookup is aborted prematurely with EIO even if it
    succeeded on the other replica(s).
    
    Change-Id: Ib9b7f2974bff8e206897bb4f689f0482264c61e5
    BUG: 1291701
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12973
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6e635284a4411b816d4d860a28262c9e6dc4bd6a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Nov 25 09:49:19 2015 +0530

    glusterd/afr: store afr pending xattrs as a volume option
    
    Problem:
    When AFR xlator initialises, it uses the name of the client xlators
    below it for storing the pending changelogs (xattrs). This can be
    problem when some other xlator is loaded in between AFR and the client.
    Though that is a trivial 'traverse-graph-till-the-client-and-use-the-name'
    fix in AFR's init(), there are other issues like when there's no client
    xlator at all when, say, AFR is moved to the server side.
    
    Fix:
    The client xlator names are currenly unique and stored as
    brickinfo->brick_ids. So persist these ids as comma separated values in
    AFR's volume_options and use them as xattr values during init().
    
    Change-Id: Ie761ffeb3373a4c4d85ad05c84a768c4188aa90d
    BUG: 1285152
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12738
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 55f4e8a74e89d61c97e79474c4488ba0bf40a3c1
Author: hari gowtham <hgowtham@redhat.com>
Date:   Fri Dec 4 18:34:36 2015 +0530

    tier/glusterd : making new tier detach command throw warning
    
    For detach tier, the validation was done using the string "detach-tier"
    but the new commands used has the string "tier". Making the string use
    "tier" to compare, creates problem as the tier status and tier detach
    have the keyword "tier". So tier detach and tier status were separated.
    and strtok was used to prevent the condition from passing when the
    volume name has a substring of "tier". (only the second word from the
    string is got and checked if the feature is tier)
    
    Problem: new detach tier command doesnt throw warnings like
    "not a tier volume" or " detach tier not started" respectively
    instead it prints empty output.
    
    Fix: while validate the volume is checked if its a tiered volume
    if yes it is checked if the detach tier is started, else a warning
    is thrown respectively.
    
    Change-Id: I94246d53b18ab0e9406beaf459eaddb7c5b766c2
    BUG: 1288517
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12883
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 6e17fb2097f941798e1d56728fd3d61e525a39a5
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Wed Aug 12 01:09:41 2015 +0530

    glusterd: DEBUG log should not come after resetting client log level
    
    After resetting diagnostics.client-log-level option still DEBUG log is
    logging in scrubber and bitrot log file. After resetting any option
    value of that options goes to default value.
    
    This patch will set the default value of client and brick log level to
    "INFO" log level.
    
    Change-Id: I4cf04754dcf5ddc908dae4d9bdf525cfcd6cc2bd
    BUG: 1252696
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11887
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f870585ca23a6329442d550e325ad81cec0135b8
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Dec 15 12:05:25 2015 +0530

    test: Move tests/bugs/tier/bug-1286974.t to bad test
    
    Moving this bug into bad test as it causes some spurious
    failures
    
    Change-Id: I5fe491858283374e5a061a48c50ac5a02a2941fa
    BUG: 1251592
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12967
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c4f6521dfe6a44cee2f61ae41fc26faaf785372d
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Nov 26 14:35:49 2015 +0530

    storage/posix: Implement .unlink directory
    
    Problem: For EC volume, If a file descriptor is open and
    file has been unlinked, any further write on that fd will
    fail. When a write request comes, EC internally reads some
    blocks using anonymous fd. This read will fail as the file
    has already been unlinked.
    
    Solution: To solve this issue, we are using .unlink directory
    to keep track of unlinked file. If a file is to be unlinked
    while its fd is open, move this to .unlink directory and unlink
    it from .glusterfs and real path. Once all the fd will be closed,
    remove this entry form .unlink directory.
    
    Change-Id: I8344edb0d340bdb883dc46458c16edbc336916b9
    BUG: 1286029
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/12816
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit be438f9aa70cce9d14d72d7cf8ddee89738db36c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Dec 10 18:53:37 2015 +0530

    features/changelog: Remove incorrect error message
    
    During changelog_rollover, the rename error is
    logged even though changelog rollover is successful.
    This got mistakenly added as part of commit
    64e6836ac8fb96f38a859eea0d8525cd9bd2693f
    (http://review.gluster.org/10532). Removing the
    same.
    
    Change-Id: I7ac1a16b41de5a6a4d7e714946585dff3ce0e83b
    BUG: 1290421
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12940
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 22827d51c232c44a8f5ac003529d907d93baf7b0
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Wed Nov 25 17:38:43 2015 +0530

    bitrot: getting correct value of scrub stat's
    
    When user execute bitrot scrub status command then gluster
    is not giving correct value of Number of Scrubbed files,
    Number of Unsigned files, Last completed scrub time,
    Duration of last scrub.
    
    With this patch scrub status will give correct value for
    all the above fields.
    
    Change-Id: Ic966f76d22db5b0c889e6386a1c2219afbda1f49
    BUG: 1285989
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12776
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 0598ca33ec95b4f4c44582c6154c52494b910b3a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Dec 1 15:24:11 2015 +0530

    bitrot: Update 'scrub status' cmd in man page
    
    Update following bitrot status command in man page.
    gluster vol bitrot <volname> scrub status
    
    Change-Id: I86aa123d568711c6b3d655b60cfd901a8d4c3408
    BUG: 1286988
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12834
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 01e271a0f14e590ef41db181699cd630e52f1d04
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Sat Dec 12 15:21:06 2015 +0530

    dht/rebalance: Use seperate return variable for destination cleanup
    
    Use seperate local return variable for destination cleanup,
    without messing with the function return variable.
    
    Change-Id: Iaea9ed2927234fdb888aef7a31ec362090e98196
    BUG: 1290975
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12956
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit b0724fc67d107ecd0c0b281f4be1b8eeef9ba6d3
Author: Michael Adam <obnox@samba.org>
Date:   Mon Nov 30 11:38:15 2015 +0100

    tests:bugs:fuse: add setup.sh and teardown.sh to facilitate manual testing
    
    Change-Id: Ia8fe402663bbdabdc10c18ab42a2063466eb42b6
    BUG: 1286735
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12830
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 8df88683c334c0652770e8e0fcec59dbc8bb5748
Author: Michael Adam <obnox@samba.org>
Date:   Mon Nov 30 10:51:13 2015 +0100

    tests:bugs:fuse: add test for bug #1283103 - selinux mount vs security xattrs
    
    BUG: 1283103
    Change-Id: Ic4485d650275f67eb6b0b8382a92eb829c06e27c
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12827
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit eff14863fb6a6da0ccf8a40343160b09f29ea493
Author: Alex Markelov <alex@markelov.org>
Date:   Sat Oct 31 08:30:08 2015 +0000

    Add support for sparse files to tarssh method
    
    Without '--sparse' option tar will not properly archive sparse file
    and geo-replication will result in non-sparse file on the remote end.
    
    Here is more on how I arrived at this
    http://markelov.org/wiki/index.php/GlusterFS_3.6.1_on_CentOS_6.5:_geo-replication_and_sparse_files_problem
    
    Change-Id: I8d671964a1b48bbb916e4a064571221bf3631494
    BUG: 1276839
    Signed-off-by: Alex Markelov <alex@markelov.org>
    Reviewed-on: http://review.gluster.org/12476
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit ddf5957d3e4e09ed750f68447492796af61f08e4
Author: Anuradha Talur <atalur@redhat.com>
Date:   Tue Dec 8 17:02:23 2015 +0530

    features/index : Prevent logging due to NULL dict
    
    Added a check for non-NULLness of dict before
    performing dict_foreach_match on it.
    
    Change-Id: I77d83559934006425ed33745b8a244b2f5d90cb1
    BUG: 1250803
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12910
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 4fefa3d7dbcdad1e71c74db11113ac1e74b01656
Author: Michael Adam <obnox@samba.org>
Date:   Wed Nov 18 09:01:30 2015 +0100

    fuse: forbid only access to security.selinux xattr if not mounted with 'selinux'
    
    Originally, all selinux.* xattrs were forbidden, causing
    for example Samba's acl_xattr module which uses security.NTACL
    to fail without the 'selinux' mount option, which is confusing
    at least. This change specializes the check to the security.selinux
    attribute, so other selinux.* attributes work with or without the option.
    
    Change-Id: I9d3083123efbf403f20572cfb325a300ce2e90d9
    BUG: 1283103
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12826
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3a01c1b36724ad4c9148540b56a26b3c1799c583
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Dec 8 14:31:30 2015 +0530

    tests, shard: Remove dependency on strict-write-ordering
    
    Change-Id: I00171a77bdefb1c2e7e4610cb0ade5679bdb761f
    BUG: 1289840
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12915
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit fc07e9c90db11bbbadf341d0720a874a8cd1fdc5
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Dec 10 12:33:05 2015 +0530

    tests: Fix arbiter-statfs.t
    
    ..and remove it from bad tests list.
    
    Problem:
    https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/12516/consoleFull
    
    ++ SETUP_LOOP /d/backends/brick1
    ++ '[' 1 '!=' 1 ']'
    ++ backend=/d/backends/brick1
    ++ case ${OSTYPE} in
    +++ awk -F: '/not in use/{print $1; exit}'
    +++ vnconfig -l
    vnconfig: VNDIOCGET: Bad file descriptor
    ++ vnd=
    ++ '[' x = x ']'
    ++ echo 'no more vnd'
    no more vnd
    ++ return 1
    
    Fix:
    TEST the return value of SETUP_LOOP.
    Also added EXIT_EARLY to the test case because there is no point in
    continuing the test when setting the bricks fail.
    
    Change-Id: I933611c41f93ac646f1170b62db656314c801ef1
    BUG: 1290125
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12936
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 02168fdd1b0d63bac758db2f5e4a53b28e459f97
Author: anand <anekkunt@redhat.com>
Date:   Tue Dec 1 14:30:40 2015 +0530

    glusterd: Maintain per transaction op-info object
    
    Issues: Since in op-sm transactions a mix of access to global op-info & per transaction
    op-info objects are used, the correctness of op-info object may go for a toss resulting
    into incorrect response getting passed back to cli
    
    Fix: Use per transaction op-info object
    
    Change-Id: Ice023bace3e137dfd8e7b13bd5b53545a79a203f
    BUG: 1287027
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/12836
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit aeaee78c4ec88f3c00efe22edc796102e03291da
Author: N Balachandran <nbalacha@redhat.com>
Date:   Wed Dec 9 19:36:42 2015 +0530

    tests/tier: spurious failure in rename test
    
    bug-1279376-rename-demoted-file.t fails sometimes
    The fix is based on the assumption that the test
    failed because the demotion happened too quickly.
    
    Change-Id: Ieccc736f387fcf6afaa72fa9918adb6dd34f2c8a
    BUG: 1289845
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12926
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 3949541b21b1d03ab37c7ab39f95581d553251d4
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Dec 9 03:53:45 2015 -0500

    storage/posix: fix dict leak in posix_fgetxattr
    
    Change-Id: I8c53805993570e6f37786dde2103cb884c026791
    BUG: 1285230
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12916
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d57a5a57b8e87caffce94ed497240b37172f4a27
Author: Ravishankar N <root@ravi2.(none)>
Date:   Wed Dec 2 08:20:46 2015 +0000

    glusterd: add pending_node only if hxlator_count is valid
    
    Fixes a regression introduced by commit
    0ef62933649392051e73fe01c028e41baddec489 . See BZ for bug
    description.
    
    Problem:
        To perform GLUSTERD_BRICK_XLATOR_OP, the rpc requires number of xlators (n) the
        op needs to be performed on and the xlator names are populated in dictionary
        with xl-0, xl-1...  xl-n-1 as keys. When Volume heal full is executed, for each
        replica group, glustershd on the local node may or may not be selected to
        perform heal by glusterd.  XLATOR_OP rpc should be sent to the shd running on
        the same node by glusterd only when glustershd on that node is selected at
        least once. This bug occurs when glusterd sends the rpc to local glustershd
        even when it is not selected for any of the replica groups.
    
    Fix:
        Don't send the rpc to local glustershd when it is not selected even once.
    
    Change-Id: I2c8217a8f00f6ad5d0c6a67fa56e476457803e08
    BUG: 1287503
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12843
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit db3ff1e75f6d6cf80967708778f36ae07ddb220a
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Nov 26 14:33:14 2015 +0530

    tier/ctr: Check filename in ctr_lookup for nameless lookup
    
    Check filename in ctr_lookup for nameless lookup
    
    Change-Id: I1ab3f658e3b9fee708f6986d1990f16db920d2fb
    BUG: 1285663
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12760
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit d07983bff768e919fd867c27f8cca9c346e4eca9
Author: Michael Adam <obnox@samba.org>
Date:   Thu Dec 10 01:27:53 2015 +0100

    tests: mark several tests as bad
    
    There are currently several spurious tests.
    We should bundle adding them to the bad test list
    into one patch so that they don't prevent each other's
    regression runs from succeeding...
    
    Failing on Linux:
    =================
    
    tests/basic/afr/split-brain-healing.t:
      https://build.gluster.org/job/rackspace-regression-2GB-triggered/16680/consoleFull
    
    tests/basic/afr/sparse-file-self-heal.t:
      https://build.gluster.org/job/rackspace-regression-2GB-triggered/16682/consoleFull
    
    tests/basic/afr/replace-brick-self-heal.t:
      https://build.gluster.org/job/rackspace-regression-2GB-triggered/16681/consoleFull
    
    tests/bugs/tier/bug-1279376-rename-demoted-file.t:
      https://build.gluster.org/job/rackspace-regression-2GB-triggered/16675/consoleFull
    
    this one thows core:
    tests/bugs/snapshot/bug-1140162-file-snapshot-features-encrypt-opts-validation.t
      https://build.gluster.org/job/rackspace-regression-2GB-triggered/16674/consoleFull
    
    Failing on NetBSD:
    ==================
    
    tests/basic/afr/arbiter-statfs.t:
      https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/12551/consoleFull
    
    tests/features/weighted-rebalance.t:
      https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/12538/consoleFull
    
    Change-Id: I1f48d5631d761b5d3e736bfd918f483bdbd36c5a
    BUG: 1290270
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12933
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit cb41de7c4a7d620dbab645f2b105286b68bde9a9
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Dec 8 19:55:22 2015 +0530

    tier/dht: files are still going to decommissioned subvol
    
    After detach tier start, creates are still going to hot
    tier. Because when creating data files we are not checking for
    decommissioned bricks.
    
    Change-Id: I8e28258d9b2367dcc8ad6e5e91d0e54d92fdf771
    BUG: 1289602
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12914
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit bcc4c12360c1a63bae5b787e519a35c32b48ae83
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Dec 8 18:56:31 2015 +0530

    tier : Spawn promotion or demotion thread depending on local bricks
    
    Spawn Promotion or Demotion depending if there are any Cold or Hot
    bricks present localy.
    IF the local HOT brick list is empty dont spawn demote thread.
    IF the local COLD brick list is empty dont spawn promote thread.
    
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    
    Change-Id: I524730e59414dd156c78ec0bd7a3629212697e6e
    BUG: 1289578
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12912
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 8424674e7046136728e5f43adb19bb1fa5b19f5a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Dec 8 11:06:33 2015 +0530

    tests/bug-924726.t: fix grep pattern to get correct glusterfs pid
    
    Change-Id: Ia2444b1b3e45e3e224bcd59e780a0f38c492f133
    BUG: 1289428
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/12906
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ba73b0a25ecdf1c8476eead8105a8edc8031b31c
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Dec 8 19:06:24 2015 +0530

    tests: fix brick_up_status
    
    The brick_up_status function wasn't correct after the introduction of
    the RDMA port into the `volume status` output.
    
    It has been fixed to use the XML brick status of a specific brick
    instead of normal CLI output.
    
    Change-Id: I5327e1a32b1c6f326bc3def735d0daa9ea320074
    BUG: 1289584
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/12913
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 032e9a8bd923cf6913f0d3998546a2bd589adceb
Author: Michael Adam <obnox@samba.org>
Date:   Wed Dec 9 09:59:40 2015 +0100

    glusterd: fix the build
    
    Fix the build broken in 6e9f88cfd4c80c6af7260e5e6537cb76b6c0
    
    Change-Id: I0c5cedff980688cb47f3f0e9f4968c23d2f507d3
    BUG: 1289869
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12918
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>

commit eb1a6e9f88cfd4c80c6af7260e5e6537cb76b6c0
Author: vmallika <vmallika@redhat.com>
Date:   Fri Dec 4 16:51:18 2015 +0530

    quota: copy quota_version value in func glusterd_volinfo_dup
    
    quota_version is a new variable introduced for
    quota xattr versioning feature.
    
    quota_version was not copied when creating duplicate
    volinfo in function 'glusterd_volinfo_dup'
    so any feature like snapshot/tiering using
    glusterd_volinfo_dup will get the default value
    of quota_version instead of the correct number
    and can cause a problem
    
    Change-Id: I7b0f418002d49aa7210e2e741e65ee5b2593e6a6
    BUG: 1288474
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12881
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 156022b67f5da2ca27a607ee9e7608fdf5e91a20
Author: vmallika <vmallika@redhat.com>
Date:   Thu Dec 3 14:55:36 2015 +0530

    glusterd/quota: quota-version conflict in export/import volinfo
    
    When exporting/importing voinfo during handshake,
    quota conf and quota xattr version were using same key
    'quota-version' and updated wrong values when importing
    quota version values.
    
    Change-Id: If939d6f5bc4851d4114963877be72dda21834f0f
    BUG: 1287996
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12865
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 28da53e26e88f23f8917810ce0177f2628aa7e9a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Dec 1 09:11:01 2015 +0000

    tier/glusterd: Check before starting tier daemon during volume start
    
    We start tier daemon when volume is started without looking into the
    previous status. The problem with that if detach-tier is started
    and then volume force start is actually starting tier daemon.
    
    This is also fixes a problem where tier daemon is not starting
    after detach stop.
    
    Change-Id: I15b56a711e12f0e24f5ab123561258bd448621f7
    BUG: 1286974
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12833
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 848bf0db0dde745e1f3a966db0143b7003bd49b5
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Nov 25 05:07:03 2015 -0500

    posix: fix posix_fgetxattr to return the correct error
    
    posix_fgetxattr used to not updating op_ret
    and op_errno (initialized to -1 and ENOENT respectively)
    on success cases. Hence, it can return ENOENT even if all
    the opertions were sucessful.
    
    Change-Id: I5db3c1821208166a052d734b0be2553d009b8ee4
    BUG: 1285230
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12745
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 988495ef1f8bb737d5edd079dec5635309097a62
Author: vmallika <vmallika@redhat.com>
Date:   Fri Dec 4 12:36:22 2015 +0530

    quota: add 'quota-version' to xlator volume_options structure
    
    Below error is seen in brick log:
    0-vol1-quota: option 'quota-version' is not recognized
    
    So add this option to the volume_options structure of
    marker xlator
    
    Change-Id: I1bd68a537936ee0f9af85dac74f1377f84edb8f4
    BUG: 1283178
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12878
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5fa88405ba1aba2312902255282fc4f6625d18ed
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Dec 8 12:47:42 2015 +0530

    features/shard: Do not update inode-ctx size (again) after xattrop
    
    This is to fix race between parallel writevs that could mess up
    the file size value in inode ctx.
    
    Thanks to Pranith for helping with RCA'ing the issue.
    
    Change-Id: Ief94e0b3bcd87a8e2391fb39af1b99d020abd764
    BUG: 1289447
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12907
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 72334e2209b8b506f00d5d851bfb5fdc3eb38cf4
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Nov 25 00:04:39 2015 +0530

    cli/quota: show used_space,(file,dir) count even when quota limit is not set
    
    Problem:
    As of now quota 'list/list-objects' will list the usage only if limit is
    set for every directory else it will fail with ENOATTR(If inode/inode-quota
    is already configured for the first time).
    
    Feature:
    With the patch we are enhancing this command to list the usage even
    if quota limit is not set but still the user has to configure
    inode/inode-quota for the first time.
    
    Example:
    Consider we have /client/dir and /client1(absolute path from mount point):
    Quota limit is set only on /client. when we try listing /client/dir or /client1,
    it shows "Limit not set".
    
    Fix:
    The patch fixes this by showing "used space" in case of list command and
    shows "file_count" & "dir_count" in case of list-objects command. This works
    fine with xml output as well.
    
    Change-Id: I68b08ec77a583b3c7f39fe4d6b15d3d77adb095a
    BUG: 1284752
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12741
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 06818a0fd69bb0d6daabde73e5c3cc2661a70854
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Dec 7 13:32:57 2015 +0530

    cluster/tier : Fix double free in tier process
    
    The tier process tries to free ipc_ctr_params twice
    if the syncop_ipc call in tier_process_ctr_query fails.
    ipc_ctr_params is freed when ctr_ipc_in_dict is freed.
    But ctr_ipc_out_dict is NULL when syncop_ipc fails, causing
    GF_FREE to be called on a non-NULL ipc_ctr_params ptr again.
    
    Change-Id: Ia15f36dfbcd97be5524588beb7caad5cb79efdb4
    BUG: 1288995
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12890
    Reviewed-by: Joseph Fernandes
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit b1d047caeacbcfac4222759af9d5936b7cfd1d7c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Dec 3 14:54:32 2015 +0530

    glusterd: Disallow peer with existing volumes to be probed in cluster
    
    As of now we do allow peer to get added in the trusted storage pool even if it
    has a volume configured. This is definitely not a supported configuration and
    can lead to issues as we never claim to support merging clusters. A single node
    running a standalone volume can be considered as a cluster.
    
    Change-Id: Id0cf42d6e5f20d6bfdb7ee19d860eee67c7c45be
    BUG: 1287992
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12864
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 05b510bb893761864d3830eb781210445056a6f9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Dec 6 22:05:54 2015 +0530

    mount/fuse: Fix use-after-free crash
    
    fouh->len is accessed after 'node' is freed. Also 'rv' is int where as
    fouh->len is uint32, changed comparison to ssize_t variables.
    
    BUG: 1288857
    Change-Id: Ied43d29e1e52719f9b52fe839cee31ce65711eea
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12886
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 02d54bb750c5ad41b81881ce63dd756582aad543
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Dec 3 15:40:16 2015 +0530

    tier/dht: Fix mem leak from lookup response dict
    
    Fixing memory leak from response dict during a parent
    lookup to get the path.
    
    Change-Id: I60c23d0b25e7f763f0e53c40e71ee053aba6d555
    BUG: 1288019
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12867
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes
    Tested-by: Joseph Fernandes

commit be377d4bed954fc8cdbc515329882c1fd0f7ab37
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Nov 26 12:42:17 2015 +0530

    tier/tier: Ignoring status of already migrated files
    
    Ignore the status of already migrated files and in the
    process don't count.
    
    Change-Id: Idba6402508d51a4285ac96742c6edf797ee51b6a
    BUG: 1276141
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12758
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 976d2902cb191a738853279c8b81ee3721f515b6
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Thu Dec 3 17:41:13 2015 +0530

    glusterd: disable ping timer b/w glusterd and make epoll thread count to 1
    
    Currently glusterd is crashing when enable/disable heal and i/o is in
    progress on the fuse mount.
    
    This is because of by default multi thread epoll in glusterd is 2.
    Workaround is to make epoll thread to 1 and set ping-timeout to 0
    
    Change-Id: Ifbe9b43a361c5409b707539f0ee831c610a5c36b
    BUG: 1288059
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12874
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 875bb10bd261596c43976e67d0660c803ef82301
Author: Patrick Uiterwijk <puiterwijk@redhat.com>
Date:   Mon Aug 18 16:45:21 2014 -0400

    Make rfc.sh show what its actually doing
    
    Change-Id: Ifb9246a2680e5f985871d4209b46dd803979c2e1
    BUG: 1131275
    Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
    Reviewed-on: http://review.gluster.org/8496
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 221b647d17de24d408761a0225d551b07ff8ac65
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Dec 2 17:13:00 2015 -0500

    tests: add bug-924726.t to ignore list
    
    bug-924726.t has had spurious errors in regression tests.
    
    Change-Id: I5514e90909c3ecdd487c0dcf501ebf0952dc4fbb
    BUG: 1287872
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12859
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 96fc7f64da2ef09e82845a7ab97574f511a9aae5
Author: N Balachandran <nbalacha@redhat.com>
Date:   Thu Dec 3 12:52:54 2015 +0530

    cluster/tier: fix loading tier.so into glusterd
    
    glusterd occasionally loads shared libraries of translators. This
    failed for tiering due to a reference to dht_methods which is defined
    as a global variable which is not necessary.
    The global variable has been removed and this is now a member of
    dht_conf and is now initialised in the *_init calls.
    
    Change-Id: Ifa0a21e3962b5cd8d9b927ef1d087d3b25312953
    BUG: 1287842
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12863
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit cae9512d60f5715459ea5883c657c679197982d9
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Tue Dec 1 19:14:08 2015 +0530

    glusterd: stop daemon services upon peer detach correctly
    
    Problem:
    Currently glusterd is stopping all the daemons service upon peer detach.
    If user have multi node cluster and if user want to detach any node
    from the cluster, and detached node having stand alone volume then upon
    detaching glusterd stopping all the daemon's of the detached node,
    which is having running volume.
    
    Fix:
    Upon peer detach it should do peer detach cleanup properly and it should
    stop only those daemon on the node on which it require.
    
    Change-Id: I98b8099166f82e235ded6d02261f59a6511a003b
    BUG: 1287455
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12838
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 93f31189ce8f6e2980a39b02568ed17088e0a667
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Wed Dec 2 14:26:47 2015 +0530

    geo-rep: use cold tier bricks for namespace operations
    
    Problem:
    symlinks are not getting synced to slave in a Tiering based volume.
    
    Solution:
    Now, symlinks are created directly in cold tier bricks( in the backend).
    
    Earlier, cold tier was avoided for namespace operations and only
    hot tier was used while processing changelogs.
    
    Now, cold tier is HASH subvolume in a Tiering volume.
    So, carry out namespace operation only in cold tier subvolume and
    avoid hot tier subvolume to avoid any races.
    
    Earlier, XSYNC was used(and changeloghistory avoided) during initial sync
    in order to avoid race while processing historychangelog in Hot tier.
    This is no longer required as there is no race from Hot tier.
    
    Also, avoid both live and history changelog ENTRY operations from Hot tier to avoid any race with cold tier.
    
    Change-Id: Ia8fbb7ae037f5b6cb683f36c0df5c3fc2894636e
    BUG: 1287519
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/12844
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit e6046ddc62a61f63d3c2ff2fb450c07c0604e801
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Dec 2 21:19:56 2015 +0100

    fuse: pass default SElinux mount options on to the kernel
    
    In order to set default SElinux contexts on a Gluster mount, the
    standard SElinux mount options need to be passed to the kernel. The
    mount(8) manual page lists "context", "fscontext", "defcontext" and
    "rootcontext" as valid options.
    
    BUG: 1287763
    Change-Id: I015fe27e4c6ff36a030e3480b23141aca2d91fc2
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/12858
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>

commit 0d46f1b0519f93165a335bf264661054883b522f
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Nov 9 13:37:53 2015 +0530

    snapshot/clone : Fix tier pause failure for snapshot clone
    
    On a tiered volume, snapshot clone fails while trying to
    pause tier, as we pass volname(snap) to the brick_op_phase module,
    which tries to look for the snap volume amongst regular
    volumes, and obviously doesn't find it and fail.
    
    Well as snapshot volumes are read only volume, and will not
    have tiering daemon acting upon them, there is really no need
    to pause tiereing while taking clone of snapshot volumes. Hence
    removing the code to pause and resume tiering during clone create.
    
    Change-Id: I2266aba589a830a13a806c0d8a56fd8855143ccd
    BUG: 1279327
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12548
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit bdfd087d76cbf6336805c6c55c0e0935dfd29a9d
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Nov 30 16:51:35 2015 +0530

    tier/libgfdb/sql: Correcting logic in sql query for read
    
    Correcting query in the  where clause
    
    from "a & b | c"
    
    to "a & (b | c)"
    
    where "a" is the condition to join the gf_file_tb and gf_flink_tb
    through gfids
    
    "b" is the condition for the write heat
    and "c" is the condition for read heat
    
    Change-Id: I99226d82b0efb68fbef3a40f02b215bb2b4370d6
    BUG: 1286656
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12823
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9c378026e9561595586a817fee0b439e2c863a22
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Nov 23 15:56:28 2015 +0530

    heal : Changed heal info to process all indices directories
    
    Change-Id: Ida863844e14309b6526c1b8434273fbf05c410d2
    BUG: 1250803
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12658
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cb7da0ffba147173bc9e6cd05f0a88a2c1ac9cdc
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Nov 2 17:49:44 2015 +0530

    snapshot: Fix quorum check for clone
    
    snapshot clone was not performing quorum check
    and was just relying on glusterd server quorum.
    
    Wrote glusterd_snap_quorum_check_for_clone(), to
    perform the same. Also moved common quorum check code
    from glusterd_snap_quorum_check_for_create(), to
    glusterd_snap_common_quorum_chk_clone_create() to be
    shared by both
    
    Change-Id: Ib78c709186841780876de8ef7d7c9243b7f67995
    BUG: 1276023
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12490
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit f6142e97c6219d2c1c482a414690020ed1275bdb
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Wed Sep 23 12:21:40 2015 +0530

    geo-rep: geo-rep to handle CAPS based Hostname
    
    Problem:
    geo-replication session creation fails when Hostname
    is having CAPS in it.
    Issue is with the regex pattern which handles only small lettered
    Hostname.
    
    Fix:
    Fix the regex pattern to handle CAPS based hostname as well.
    
    Change-Id: I5c99c102e9706acc2b1fab1e6bf158e68beed373
    BUG: 1265522
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/12216
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2e9376a2f1b992d3649dd1d5a8e844b4c031ef3c
Author: Michael Adam <obnox@samba.org>
Date:   Mon Nov 30 13:35:23 2015 +0100

    extras: fix deprecation warining in checkpatch.pl
    
    Left braces in patterns need to be escaped.
    Otherwise, for perl >= 5.16, we get a warning:
    "Unescaped left brace in regex is deprecated, passed through in regex;"
    This patch fixes the relevant braces.
    
    Hence perl -c ./examples/checkpatch.pl is clean again.
    
    Change-Id: I938c9c262239f53de57d30a2cff7030f22e63dc1
    BUG: 1198849
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/12828
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 905b3d26a794510892f6a9b51139bc9cfd947c02
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Nov 24 10:31:35 2015 +0530

    glusterd:Removing error message in glusterd log during upgrade
    
    when one of the gluster node is upgraded to 3.7 from a lower
    version and a mixed cluster is formed, tier related error
    messages are displayed in the glusterd log which are removed
    
    Change-Id: I8d0fc43ce049990a6a52306317ea1298a0a91390
    BUG: 1282461
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12587
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 189a2302822f20ec9741002ebc9b18ea80c2837f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Nov 25 18:34:29 2015 +0530

    geo-rep: fd close and fcntl issue
    
    When any of the open fd of a file is closed
    on which fcntl lock is taken even though another
    fd of the same file is open on which lock is taken,
    all fcntl locks will be released. This causes both
    replica workers to be ACTIVE sometimes. This patche
    fixes that issue.
    
    Change-Id: I1e203ab0e29442275338276deb56d09e5679329c
    BUG: 1285488
    Original-Author: Aravinda VK <avishwan@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12752
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit eea50e82365770dea56cdddca89cd6d3b8bb7a22
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Sat Nov 28 17:03:41 2015 +0530

    tier/glusterd : Validation for frequency thresholds and record-counters
    
    1) if record-counters is set to off
       check if both the frequency thresholds are non-zero, then pop
       an error message, with volume set failed.
    2) if record-counters is set to on
       check if both the frequency thresholds are zero, then pop
       an note, but volume set is not failed.
    3) If any of the frequency thresholds are set to a non-zero value,
       switch record-counters on, if not already on
    4) If both the frequency thresholds are set to zero,
       switch record-counters off, if not already off
    
    NOTE: In this fix we have
    1) removed unnecessary ctr vol set options.
    2) changed  ctr_hardlink_heal_expire_period to ctr_lookupheal_link_timeout
    
    Change-Id: Ie7ccfd3f6e021056905a79de5a3d8f199312f315
    BUG: 1286346
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12780
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit de9c322dfbe5c4f9da65fbe0eef443440eafbbdc
Author: Cedric Buissart <cbuissar@redhat.com>
Date:   Mon Nov 16 15:32:29 2015 +0100

    glusterd-ganesha xlator parser for ganesha-ha.conf
    
    The current method for parsing ganesha-ha.conf is prone to issues :
    Before the patch :
    - no double quote leads to segfault
       e.g. : HA_CLUSTER_NODES=server1,server2
    - no check for comments.
       e.g. : #HA_CLUSTER_NODES="server1,server2"
          would be used if preceding the real value
    
    This is an attempt to a cleaner parser:
    1- factorization of parsing code, creating 1 dedicated, more generic
    parser
    2- double quote are no longer mandatory
    3- should not segfault
    4- lines are no longer limited to 1024 chars
    
    Resolves RHBZ 1283211
    
    Change-Id: I75f11461fe1b84915d1c5cfe945b47bd81abc2b1
    BUG: 1283211
    Signed-off-by: Cedric Buissart <cbuissar@redhat.com>
    Reviewed-on: http://review.gluster.org/12588
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 86701a0ececa5fdbbe08654516618baadc4555b7
Author: Anoop C S <anoopcs@redhat.com>
Date:   Mon Nov 23 12:20:09 2015 +0530

    build: Remove redundant options from GF_CFLAGS
    
    While configuring, GF_CFLAGS is being populated with redudndant
    options as follows:
    
    Normal mode:
    GF_CFLAGS = -g -O2 -g -O2 -Wformat -Werror=format-security \
                -g -O2 -g -O2 -Wformat -Werror=format-security \
                -Werror=implicit-function-declaration
    Debug mode:
    GF_CFLAGS = -g -O2 -g -O0 -DDEBUG -Wformat -Werror=format-security \
                -g -O2 -g -O0 -DDEBUG -Wformat -Werror=format-security \
                -Werror=implicit-function-declaration
    
    This patch is to remove this redundancy of options.
    
    Change-Id: Idf6f2536c2a8ae24ba257681fbe9dfdb8bfa4f19
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/12714
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b8b050c37004c942b8c565cc66a05e8fa999c1ba
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 1 10:59:41 2015 +0530

    cluster/ec: Create copy of dict for setting internal xattrs
    
    Problem:
    Ec takes a ref of the request xdata and sets trusted.ec.version/algo etc xattrs
    as part of it. But this request xdata could be using same dictionary to do the
    operation on multiple subvolumes, due to which other subvolumes will have
    internal xattrs of ec in it and will be created on subvols where they are not
    supposed to appear.
    
    Fix:
    Take a copy of the request xdata/dict to prevent this from happening.
    
    Most of the debugging work and test script is contributed by Nitya.
    
    BUG: 1286910
    Change-Id: If146435dfb89656158dbed3862a3e9a0cda60581
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12831
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 3c18b186921c51b1a976eea8cd1c19f7113ef74c
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Nov 20 17:50:50 2015 +0530

    defaults: Add 'GF_EVENT_UPCALL' to default_notify
    
    Fix a regression caused by commit#If7d59d
    
    Change-Id: Ib2239b9b0e216302e6c89e21288592d35b8d124b
    BUG: 1283983
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/12708
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit ffe80877a0eb0eaf2540be95b401623c6d7c722f
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Nov 27 12:09:22 2015 +0530

    Upcall: Read gfid from iatt in case of invalid inode
    
    When any file/dir is looked upon for the first time, inode
    created shall be invalid till it gets linked to the inode table.
    In such cases, read the gfid from the iatt structure returned
    as part of such fops for UPCALL processing.
    
    Change-Id: Ie5eb2f3be18c34cf7ef172e126c9db5ef7a8512b
    BUG: 1283983
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/12773
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit f2c52ae206f309ec636a299a76849c843c8ab83d
Author: Anuradha Talur <atalur@redhat.com>
Date:   Thu Nov 12 19:45:10 2015 +0530

    cluster/afr : Readdirp performance enhancement
    
    Things done :
    1) during lookup and inode_refresh as part of read_txn,
    request is sent to detect if heal is required or not.
    
    2) If heal is required, be conservative in setting the
    readdirp entry inodes to NULL, otherwise don't be.
    
    3) Self-heal-daemon now crawls both indices/xattrop
    and indices/dirty directory while healing.
    
    Change-Id: Ic4a4da63fb7e0726eab5f341a200859b29cf7eb7
    BUG: 1250803
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12507
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0441e50959e9305c5bc4d0af0576593f8755730e
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Mon Nov 9 22:09:34 2015 +0530

    quota: vol quota fails when transport.socket.bind-address is set in glusterd
    
    When glusterd is binded to specific IP quota fails, since the server is
    hardcoded to localhost. IP can be assigned in the glusterd part of quota,
    but IP is not populated in cli part. So Quota makes use of glusterfsd's unix
    domain socket transport type.
    
    Change-Id: Ib03332cc203795456ee6087017cea08eed3d7417
    BUG: 1277105
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/12489
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 87845356171afcd07f62f46dd81596e4f71e7935
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Fri Nov 27 11:18:00 2015 +0530

    cli/geo-rep : remove unused code
    
    Change-Id: I8a8e27b4d6c35ea5e57bd0b556fd2c6ab7b496ab
    BUG: 1285968
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12771
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 6c95d17dabf979c51905956409560b6bbdae0eb7
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Nov 26 13:59:30 2015 +0530

    features/shard: Set ctime to 0 in fsync callback
    
    ... to indicate to md-cache that it should not be caching
    file attributes.
    
    Change-Id: Iaef9bf7fec8008ca47d682b4b15984f26421bcd6
    BUG: 1285660
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12759
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6b315b87d80cf681b976d78b444c761fc3a1caa7
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Tue Nov 17 15:11:40 2015 +0530

    dht : changing variable type to avoid overflow
    
    For layout computation we find total size of the cluster
    and store it in an unsigned 32 bit variable. For large
    clusters this value may overflow which leads to wrong
    computations and for some bricks the layout may overflow.
    Hence using unsigned 64 bit to handle large values.
    
    Change-Id: I7c3ba26ea2c4158065ea9e74705a7ede1b6759c7
    BUG: 1282751
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/12597
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a1919e91279a6c691fbd3dd6c0d97e74e78ccf22
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 26 09:58:39 2015 +0530

    features/bit-rot: Fix NULL dereference
    
    Problem:
    By the time br_stub_worker is accessing this->private in it's
    thread, 'init' may not have set 'this->private = priv'. This
    leads to NULL dereference leading to brick crash.
    
    Fix:
    Set this->private before launching these threads.
    
    Change-Id: Ic797eb195fdd0c70d19f28d0b97bc0181fd3dd2f
    BUG: 1285616
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12754
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 0db6d57a184ed79eb3142c42957b1a2415744011
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Thu Nov 26 12:32:10 2015 +0530

    glusterd: glusterfsd to support volfile-server-transport type "unix"
    
    If glusterfsd uses transport type "unix", 'addrstr' can be empty. So,
    it may fail to fetch the trusted volfile in this case. This patch allows
    to fetch volfile even if addrstr is empty.
    
    Change-Id: I831c5cd0b07b90ae843ec63f0fad9241d9407f6b
    BUG: 1279484
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/12757
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 3ef88ec70aefd278155aa485e83a2d7bba8b6663
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Nov 24 20:59:29 2015 +0530

    glusterd/tier: Reset to reconfigured values after detach-tier
    
    After detach-tier commit , we have to reset the option
    reconfigured for tier volume
    
    Change-Id: Iae0210259720d6ac14ccc0cc339dc9f54a0c4571
    BUG: 1285046
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12736
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 8d2594d77127ba7ea07a0d68afca0939e1817e39
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 26 10:27:37 2015 +0530

    cluster/afr: change data self-heal size check for arbiter
    
    Size mismatch should consider that arbiter brick will have zero size file to
    prevent data self-heal to spuriously trigger/assuming need of self-heals.
    
    Change-Id: I179775d604236b9c8abfa360657abbb36abae829
    BUG: 1285634
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12755
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 7d95955cd2b2b8979e66bcf09e792a34a12bd8a3
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Nov 23 11:58:52 2015 +0530

    Tiering: change of error message for "v tier <vname>  detach status"
    
    If the volume was not a tiered volume then empty status was being
    printed instead of an error message.
    
    Change-Id: I13ccb16e1562966976a48d9365ced4c8a124de59
    BUG: 1284357
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12713
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 789803ce16409a1f9ce84c0f9a60e68bd630380e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Nov 25 12:31:25 2015 +0530

    cluster/afr: Remember flags sent by create fop
    
    Problem:
    In create fop, afr doesn't remember the flags. When afr has to perform
    fixing of the fd that needs to be opened on other bricks because the brick
    was down at the time of create, the flags with which it needs to send open
    are not present.
    
    Fix:
    Remember the flags in the fd_ctx.
    
    Thanks to Nitya for showing us the problem in re-open with the flags.
    
    Change-Id: I8ce1eb50c35fc0722cfc25cb4b6d234ef56180e5
    BUG: 1285173
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12739
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 20588e53774f1f16e4e9e25481b785f02231c485
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Nov 25 16:42:20 2015 +0530

    cli: Indicate which brick of the replica is the arbiter
    
    Enhances the cli output for arbiter volumes as requested in the BZ.
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    
    Change-Id: I28cc34d7d19def043d54291cede25a58dbcc5051
    BUG: 1285288
    Reviewed-on: http://review.gluster.org/12747
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit c85c805e980f7981dc7c87d87ef2283931c0be18
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Nov 24 13:45:20 2015 +0530

    glusterd: copy snapshot object during duplication of volfile
    
    When creating duplicate volfile for hot/cold tier, we need to
    copy the snapshot object in to volfile as it requires to generate
    snapshot brick volfile.
    
    Change-Id: I39ccfa20cd1c16ef2801901e3cd3a31c76f8995d
    BUG: 1284789
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12734
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit d81df2628a00f4d608d185f6c00a88b3099ad3bd
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Nov 25 22:52:48 2015 +0530

    tier/test: Fixing tests/basic/tier/legacy-many.t
    
    Change-Id: Icbd83afdeac053aec5b3b8fa19665a2908e87d8e
    BUG: 1285483
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12751
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 9b151f4ddc2636607b15424c94a09f619f2e5cb8
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Sat Nov 21 01:04:21 2015 +0530

    tier/ctr: Correcting rename logic
    
    Problem: When a file with old_file_name and GFID_1 is renamed with a new_file_name
    which already exists and with GFID_2, this is what happens in linux internaly.
       a. "new_file_name" is unlinked for GFID_2
       b. a hardlink "new_file_name" is created to GFID_1
       c. "old_file_name" hardlink is unlinked for GFID_2.
    Well this is all internal to linux, and gluster just issues a rename system call
    at POSIX layer. But CTR Xlator doesn't delete the entries corresponding to the
    "new_file_name" and GFID_2. Thus leaving the stale entry in the DB.
    The following are the implications.
    a. Promotion are tried on these stale entries which will fail and show
    false results in the status of migration,
    b. GFID_2 Files with 2 hardlinks, which will have only one hardlink
    after the rename will not be promoted or demoted as the DB shows 2 entries.
    
    Solution: Delete the older database entry for the replaced hardlink
    
    Change-Id: I4eafa0872253e29ff1f0bec4283bcfc579ecf0e2
    BUG: 1284090
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12711
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 03f731a8b32db7bef7c5e9ffc11c16f670ffe960
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Nov 23 12:05:54 2015 +0530

    glusterd: Change volume start into v3 framework
    
    As part of volume start, if the volume is of tier type
    then we need to start tiering daemon also. But before
    starting tier daemon all the bricks should be started.
    
    So by changing volume start into v3 framework, we can
    do tier start in post validate phase
    
    Change-Id: If921067f4739e6b9a3239fc5717696eaf382c22a
    BUG: 1284372
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12718
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit a56e32e19703c0fbe2cedebcaf5edc8a6307d5a1
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Oct 15 15:01:23 2015 +0530

    tools/glusterfind: add query command to list files
    
    When session information is maintained outside Gluster, there needs to
    be some mechanism to list files starting from a time-stamp. This patch
    implements the feature via the "query" command-line option.
    
    The only caveat is that the first time the query command is run for the
    volume, it will likely report that "historical changelogs are not
    available". This is due to the fact that changelogs had not been turned
    on for the volume so far. So the volume options need to be turned on
    outside glusterfind or the since_time need to be greater than the
    current time when the query command is run for the very first time for
    the volume. The query command turns on the required volume options for
    collecting changelogs.
    
    Change-Id: I6cb7a57a5ecd166210e2eb4deede06d40ccfa996
    BUG: 1272006
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/12362
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 5172bcb757553e05b18208d7726517f1ec4da837
Author: Anuradha Talur <atalur@redhat.com>
Date:   Thu Nov 12 19:41:33 2015 +0530

    features/index : Readdirp performance improvement
    
    Things done :
    Index now maintains two different directories :
    1) for pending xattrs (trusted.afr.volname-client-n,
                           trusted.ec.dirty)
    
    2) for on going xattrs (trusted.afr.dirty)
    
    Based on the xattr, index decides the directory
    to add/del entry in/from.
    
    Change-Id: Ie04c02ea2d862cf80426a871a9a1e80b0773d9fd
    BUG: 1250803
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12468
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 4348a6af89085cbdb41963f828b88deee4a109f1
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Mon Nov 23 17:00:07 2015 +0530

    glusterd/bitrot : Integration of bad files from bitd with scrub status command
    
    Currently scrub status command is not displaying list of all the bad files. All
    the bad files are avaliable in the bitd daemon.
    
    With this patch it will dispaly list of all the bad file's in the scrub
    status command.
    
    Change-Id: If09babafaf5d7cf158fa79119abbf5b986027748
    BUG: 1207627
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12720
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit c93e436527e9d2ceed46b939e18edc40b7018cee
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Nov 23 13:06:25 2015 +0530

    features/shard: Eliminate extra update to postbuf in writev
    
    After an extending write is complete, shard translator updates postbuf
    at two places:
    1. shard_update_file_size_cbk(), and
    2. shard_post_update_size_writev_handler().
    
    This can lead to unexpected behavior if md-cache is part of the client
    stack and caches and serves values returned by shard translator in
    postbuf. This patch eliminates the update to postbuf in
    shard_post_update_size_writev_handler().
    
    Change-Id: I9d107bf57baad66886eebec14aa369b6a3c88c49
    BUG: 1284365
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12717
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 5a06a9eef3f767c850e879ff87c72301e02fe137
Author: vmallika <vmallika@redhat.com>
Date:   Wed Nov 18 17:25:14 2015 +0530

    quota: fix backward compatibility of quota xattr version
    
    quota-version features is implemented for 3.7.6
    please see below patch for more details:
    http://review.gluster.org/#/c/12386
    
    Problem is when quota is already enabled,
    we suffix 0 to contri xattr key. for backward compatibility
    don't add suffix if quota-version is 0
    
    Change-Id: Id7d713b18d989e4e86019969eb511617848127f2
    BUG: 1283567
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12660
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 31f0fd1d401f1a4c007fd44854f99f15aff2346b
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Thu Nov 5 20:22:02 2015 +0530

    afr:vol heal info fails when transport.socket.bind-address is set in glusterd
    
    Problem: If glusterd's bind address is specified using transport.socket.bind- address
    option to a specific IP, the heal command 'gluster volume heal <VOLNAME> info' fails
    with error '<vol_name>: Not able to fetch volfile from glusterd.Volume heal failed.'
    This patch uses Unix domain socket transport type of libglfapi to get the volfile.
    
    Change-Id: Ic4239b339f0246d77f1622c07d5f4708129d30c7
    BUG: 1277997
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/12508
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 74699ddd777f7e862991cf3afad91823d30e5b84
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Nov 10 18:46:28 2015 +0530

    geo-rep: Fix syntax errors in GsyncdError
    
    %s was not replaced by actual values in GsyncdError
    
    BUG: 1279921
    Change-Id: I3c0a10f07383ca72844a46f930b4aa3d3c29f568
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/12566
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f2287d00c7dc9c088860c12191ff760586889dde
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Nov 23 15:58:42 2015 +0530

    marker : fixing memory leak issue in marker
    
    In marker_readdirp_cbk, variable resolvedpath is not properly freed
    and because of which there was a memory leak. The patch fixes it.
    
    Change-Id: I9d80f72e3551aa912369257da3e8e2b261a2067f
    BUG: 1284419
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12719
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 41e900199d7f369862b21b739dd11602d0d7c48d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Nov 16 12:26:00 2015 +0530

    geo-rep: Fix Geo-rep logging to log datetime in GMT/UTC
    
    Geo-rep is logging in Local time, all other Gluster logs are in
    GMT/UTC. It is very difficult to co-relate Geo-rep logs with
    other Gluster logs.
    
    BUG: 1282331
    Change-Id: Ieae8bda7e4788e587cf4595e21e0e772c210cfbb
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/12583
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d47323d0e6f543a8ece04c32b8d77d2785390c3c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Sep 7 14:18:45 2015 +0530

    tools/glusterfind: StrictHostKeyChecking=no for ssh/scp verification
    
    Also do not use scp command in case copy file from local
    node.
    
    Change-Id: Ie78c77eb0252945867173937391b82001f29c3b0
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1260918
    Reviewed-on: http://review.gluster.org/12124
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3b52c71b0ab57a9daaf31bf3dc8563da37927a66
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Nov 4 15:33:22 2015 -0500

    cluster/tier: readdirp to cold tier only
    
    It is possible a file would get migrated in the middle
    of a readdir operation. If there are four subvolumes A,B,C,D,
    and if readdir reads them in order and reaches subvol B,
    then, if a file is moved from D to A, it will not be included
    in the readdir output.
    
    This phenonema has pre-existed in DHT migration but is more
    apparent in tiering.
    
    When a file is moved off the hashed subvolume a T file is created.
    For tiering, we will make the cold subvolume the hashed subvolume.
    This will ensure the creation of a T file. Readdir will not skip T
    files in the tier translator.
    
    Making the cold subvolume the hashed subvolume ensures the T
    files created on promotions or creates will be less likely to
    fill the volume.
    
    Creates still put the data on the hot subvolume.
    
    Change-Id: Ifde557d3d0e94a4570ca9f115adee3db2ee75407
    BUG:  1281598
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12530
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit f12efd1827077292eba08a109d212a25c62476fe
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Nov 17 14:45:30 2015 +0530

    features/bit-rot: scrubber changes for getting the list of bad objects from stub
    
    Change-Id: I62885e4aba4a9b345db3c78c3291d563ff3d3567
    BUG: 1207627
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/12654
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 8805a4c65bf9c725cb26bb6979f3ebd62748138f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Sep 22 16:18:29 2015 +0530

    features/changelog: Capture FXATTROP and XATTROP in changelog
    
    GEO-REP INTEROP WITH SHARD FEATURE
    
    shard xlator updates size of the file using FXATTROP
    or XATTROP. Hence record the same in changelog.
    
    Change-Id: Ie0c21e9326da05ea78dc1ef3fd32a90ef38b4bb9
    BUG: 1265148
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12225
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 26abf56130c37bb47676658c0a0211164f05ed24
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Nov 2 11:43:12 2015 +0530

    features/bit-rot: stub changes for showing bad objects in the status
    
    Change-Id: If905132f6f1df4aebd9ab255e1e8c59902f84fe5
    BUG: 1207627
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/12503
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 7fbc38531acbc39369d3b91ba126fc4147ab89d1
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Mon Nov 9 20:43:17 2015 +0530

    glusterfsd: To support volfile-server-transport type "unix"
    
    glusterfsd fails if the glusterd is bind to specific-IP address.
    This patch helps glusterfsd to get the volfile using Unix domain socket.
    glusterfs -s <unix socket path> --volfile-server-transport unix
              --volfile-id <volume-name> <mount-point>
    The patch checks if the volfile-server-transport is of type "unix",
    If It is then uses rpc_transport_unix_options_build to get the volfile.
    
    Change-Id: I81b881e7ac5a3a4f2ac83c789c385cf547f0d53e
    BUG: 1279484
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/12556
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 097e131481d25e5b1f859f4ea556b8bf56155472
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed Mar 25 18:07:24 2015 +0530

    glusterd: cli command implementation for bitrot scrub status
    
    CLI command  for bitrot scrub status will be :
    
    gluster volume bitrot <volname> scrub status
    
    Above command will show the statistics of bitrot scrubber.
    
    Upon execution of this command it will show some common
    scrubber tunable value of volume <VOLNAME> followed by
    statistics of scrubber statistics of individual nodes.
    
    sample ouput for single node:
    
    Volume name : <VOLNAME>
    
    State of scrub: Active
    
    Scrub frequency: biweekly
    
    Bitrot error log location: /var/log/glusterfs/bitd.log
    
    Scrubber error log location: /var/log/glusterfs/scrub.log
    
    =========================================================
    
    Node name:
    
    Number of Scrubbed files:
    
    Number of Unsigned files:
    
    Last completed scrub time:
    
    Duration of last scrub:
    
    Error count:
    
    =========================================================
    
    This is just infrastructure. list of bad file, last scrub
    time, error count value will be taken care by
    http://review.gluster.org/#/c/12503/  and
    http://review.gluster.org/#/c/12654/ patches.
    
    Change-Id: I3ed3c7057c9d0c894233f4079a7f185d90c202d1
    BUG: 1207627
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10231
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b479e086ddbcb5cde83c11b67d542dbd4f2bd739
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu Nov 19 12:22:19 2015 +0530

    Tiering: Adding space between error meassge for detach-tier
    
    Change-Id: I730cf7fa6fbfb3842d337cd3d7b8394b9c3876d8
    BUG: 1283488
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12657
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 5dd1ecae7519f9d3910962d310356e07902a8fd0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Nov 19 12:00:23 2015 +0530

    core : Use correct path in dlopen for socket.so
    
    This patch fixes the path for socket.so file while loading the so dynamically.
    Also for config.memory-accounting & config.transport voltype is changed to
    glusterd to fix the warning message coming from xlator_volopt_dynload
    
    Change-Id: I0f7964814586f2018d4922b23c683f4e1eb3098e
    BUG: 1283485
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12656
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7b5cd1873e4fc62e6295b5b6c530f1afd4bf4d61
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Nov 17 14:06:20 2015 +0100

    cluster/ec: Mark internal fops appropriately
    
    1) Mark read fops in read-modify-write by EC as internal.
    2) Handle uid/gid set/reset correctly
    
    BUG: 1282761
    Change-Id: I5c1ce0cd6213367eaead5fed33aa2397c4e46df7
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/12599
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit db506cec11cdb2235aac7b6a896b4071bdcc6ae3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Nov 17 14:00:10 2015 +0530

    mgmt/gluster: Handle tier brick volgen
    
    Index xlator watches only some xattrs based on type of volume. i.e.
    disperse/afr. When the volume becomes tiered then index is not adding these
    options in the volfile leading to no maintenance of indices. Thus no
    proactive self-heals. With this fix, we write brick volfiles considering
    the type of volume they belong to.
    
    BUG: 1250803
    Change-Id: Ibe8f2d4ad5cb350306ab7ca0753e0f9a40b96a26
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12595
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 6c3895fd132765a5ad098b9ef35e037be7d116b1
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jul 16 17:05:25 2015 +0530

    tools/glusterfind: Handle Keyboard interrupt
    
    Do not print Python traceback when glusterfind command is interrupted
    
    Change-Id: I67383534f965e410fef7ce09798e9d435ef738ae
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1243812
    Reviewed-on: http://review.gluster.org/11698
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 42def948ac8e5d24278cb000cc8f8906b83a8592
Author: Aravinda VK <avishwan@redhat.com>
Date:   Sun Oct 11 20:26:16 2015 +0530

    geo-rep: Fix FD leak from Active Geo-rep worker
    
    Active worker tries to acquire lock in each iteration. On every successfull
    lock acqusition it was not closing previously opened lock fd.
    
    To see the leak, get the PID of worker,
        ps -ax | grep feedback-fd
        watch ls /proc/$pid/fd
    
    BUG: 1225566
    Change-Id: Ic476c24c306e7ab372c5560fbb80ef39f4fb31af
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/12332
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit a52fd2cb7fa3aaff74461f58f32f4ff0b8e0904d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Aug 4 16:20:13 2015 +0530

    geo-rep: Don't log geo-rep safe errors in mount logs
    
    ENOENT is a safe error for geo-replication in case of
    rm -rf. RMDIR is recorded in changelog of each brick,
    geo-rep processes all changelogs among which one will
    succeed and rest will get ENOENT which can be ignored.
    Similarly ENOENT can also be ignored in case of all
    unlink operation during changelog replay that can
    happen when worker goes down and comes back.
    
    Change-Id: I6756f8f4c3fce7a159751a2bfce891ff16ad31a4
    BUG: 1250009
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11833
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 4b8249a35aba28621ed59155ab27fb5bfa5f113f
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Nov 18 08:30:48 2015 +0530

    afr: Drop compatibility lock for data self-heal
    
    In glusterfs 3.4 and older, AFR did not take locks in self-heal domain
    during data self-heal. So this compat lock in data domain was added to prevent
    older clients from trying to heal a file while an existing self-heal was going
    on by a newer client. But the side effect was that all appending writes (which
    take full locks in data domain) from mounts would be stalled until self-heal
    was complete.
    
    Since glusterfs 3.4 is not supported anymore, remove the compat lock.
    
    Change-Id: I31c8e4d7f3364f769a14eec295154e3c40d9f78e
    BUG: 1283032
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12602
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5bb3c521431cc27b2826acd889bffb2f90ae7f73
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Nov 2 18:52:03 2015 +0530

    glusterd/geo-rep: Adding ssh-port option for geo-rep create
    
    Geo-replication uses default ssh port 22 for setup.
    i.e., to distribute ssh keys to slaves. In container
    environments, custom port number might be used.
    Hence to support custom port number for ssh, option
    is provided in geo-rep create command to take the
    same.
    
    Change-Id: I0fb61959b1c085342b8e4c21ac4e076fba5462f1
    BUG: 1276028
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12504
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit a1e4be4d277c8150657f7b9fd4b72dcdd639523d
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Nov 9 15:49:50 2015 +0530

    cluster/tier: Do not delete linkto file on demotion
    
    The current DHT migration code will always delete the
    src linkto file after migration as dht always moves
     files to the hashed subvol. This is not the case in tiering.
    The lack of linkto files causes rename to fail leaving 2 files
     with the same name but different gfids on the volume.
    Modified to leave the linkto file behind if the source
     volume is the hashed subvolume.
    
    Change-Id: I2b99f7d34b4b719aee6232dc40c6a8f8ba88225d
    BUG: 1279376
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12551
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit cb76371a56eb90a6f2ac126c876d7a2dc203e16c
Author: Anuradha Talur <atalur@redhat.com>
Date:   Wed Oct 21 16:49:49 2015 +0530

    glusterd/afr : Readdirp performance improvement
    
    Add xlator options to index xlator with xattrs that
    it needs to keep track of.
    
    Change-Id: If818673be5e626f77e65cc3a340f8cdd624179c2
    BUG: 1250803
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12467
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e06adccb38f3dc91a4534232237e07589cd07426
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Nov 17 17:01:47 2015 +0530

    cluster/ec: Mark self-heal fops as internal
    
    Change-Id: I8ae7af266d3e00460f0cfdc9389a926e5f2fee36
    BUG: 1282761
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12598
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 92919e7de3d9ceaa70d4103266fc438dd28441cc
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Nov 18 09:31:54 2015 +0530

    build: add libglusterfs/src/defaults.c to .gitignore
    
    defaults.c is auto-generated since commit
    fb2a511493868a9ff0c2926537a4d1d23821ce38. Hence adding it to .gitignore
    to stop git from complaining when switching branches.
    
    Change-Id: I586e20f3fe27124c0dc6ba7d151f957d3662a7d0
    BUG: 1271325
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12603
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 73200eaa8559c770a0ccc6e819cf791564592335
Author: Shyam <srangana@redhat.com>
Date:   Thu Oct 8 13:59:44 2015 -0400

    core: Add experimental xlator directory
    
    Added an experimental xlator directory under ./xlators/
    
    The intent of this directory is presented in the README.md
    that accompanies this commit.
    
    This directory can be disabled from being compiled using,
      - configure --disable-experimental
    
    Change-Id: I047f380c91a082d111432f8bbdbd4d7bdcbaa809
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/12321
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 23440a73bc348bbc3bb43ec397f0639ee45865fc
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Nov 18 11:21:13 2015 +0530

    glusterd.service: Ensure rpcbind is started before glusterd
    
    Having the rpcbind.service under the `After` option only ensures that
    glusterd.service is started after rpcbind.service if both are
    enabled/started at the same time. It doesn't ensure that starting
    glusterd.service will start rpcbind.service.
    
    The systemd.unit(5) man page suggests to use both the `Requires` and
    `After` options to ensure that rpcbind is started before glusterd,
    whenever glusterd is started.
    
    BUG: 1282915
    Change-Id: Iee69965486be08711299aba235f7b00c3e2fe7e9
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/12605
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit dc3aa7524e4974f9d02465e2e5dd6ed9b6d319e1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Nov 12 09:57:19 2015 +0100

    protocol/client: prevent use-after-free of frame->root
    
    A regression failure generated a coredump on the glusterfs-client side:
    
      (gdb) f 0
      #0  0x00007fba6cd76432 in client_submit_request (this=0x7fba68006fc0,
                      req=0x7fba6579aa70, frame=0x7fba5c0058cc,
                      prog=0x7fba6cfb53c0 <clnt3_3_fop_prog>, procnum=41,
                      cbkfn=0x7fba6cd9206d <client3_3_release_cbk>,
                      iobref=0x0, rsphdr=0x0, rsphdr_count=0,
                      rsp_payload=0x0, rsp_payload_count=0, rsp_iobref=0x0,
                      xdrproc=0x7fba79801075 <xdr_gfs3_release_req>) at
      /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/xlators/protocol/client/src/client.c:324
      324                   frame->root->ngrps = ngroups;
      (gdb) l
      319                   gf_msg_debug (this->name, 0, "rpc_clnt_submit failed");
      320           }
      321
      322           if (!conf->send_gids) {
      323                   /* restore previous values */
      324                   frame->root->ngrps = ngroups;
      325                   if (ngroups <= SMALL_GROUP_COUNT)
      326                           frame->root->groups_small[0] = gid;
      327           }
      328
      (gdb) p *frame->root
      Cannot access memory at address 0x64185df000000000
    
    After looking at this in more detail, the flow is like this:
    
      client_submit_request()
        |
        '- rpc_clnt_submit() // on line 314
             |
             '- cbkfn() // = client3_3_release_cbk
                  |
                  :- STACK_DESTROY (frame->root);
             .----'
        .----'
        |
        :- frame->root->ngrps = ngroups; // on line 324
        '
    
    So, there is a use-after-free, and it is not needed to restore the
    previous groups in frame->root.
    
    Change-Id: I9e7d712183692ed92cfc2f75cd3c2781a9db20e2
    BUG: 128128
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/12575
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit f71c08b8d592fa6125fee57fb73f774ce522756c
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Tue Nov 10 13:18:41 2015 +0530

    libgfapi: To support set_volfile-server-transport type "unix"
    
    This patch helps libgfapi to get the volfile using Unix domain socket.
    run the attachment file in the bug to test.
    The patch checks if the glfs_set_volfile_server transport is of type "unix",
    If It is then uses rpc_transport_unix_options_build to get the volfile.
    
    Change-Id: Ifd5d1e7c0d8cc9a906c3c3355b8977141e892a2f
    BUG: 1279739
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/12563
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 7de355b42dc1f8313db3ffc775a0e1708ba85243
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Oct 30 16:09:29 2015 +0530

    geo-rep: Allow setting config remote_gsyncd
    
    Restrictive ssh is not used in containerized environment
    where networking configuration is "net=host". SSH Pem keys
    pushed to the slave without gsyncd path in it. (Patch #12459)
    
    Actual remote_gsyncd path need to be set to actual path of gsyncd.
    With this patch, remote_gsyncd is removed from reserved option list.
    
    Change-Id: Ia2063e4654e378b62b2414bdad21143c86ad1b9a
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1276028
    Reviewed-on: http://review.gluster.org/12472
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 7d35eb5926869ed084295600502a85ce13be506f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Oct 28 17:56:50 2015 +0530

    geo-rep: New Config option for ssh_port
    
    If different port used for SSH instead of 22, Geo-replication
    was failing to establish SSH connection.
    
    ssh_port option can be added using config:ssh_command and
    config:ssh_command_tar, but user has to remember complete
    ssh command used with parameter to add/modify ssh port.
    
    This patch adds new config option for ssh_port,
    
    gluster volume geo-replication <MASTERVOL> <SLAVEHOST::<SLAVEVOL> \
            config ssh_port 52022
    
    Change-Id: I7753a09485f0b1f49d2b2a80b962c720817c96f4
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1276028
    Reviewed-on: http://review.gluster.org/12444
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 0f35b301fcb539dd85a1dae202b3ce532852d4d6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Oct 9 22:31:28 2015 +0530

    tests: spurious failure fix for bug-948686.t
    
    Ensured import volume and volume start doesn't race in volinfo by refcounting
    volinfo.
    
    Change-Id: I7467eccaba9a00fd63ba0121d8157df24d1c00a6
    BUG: 1258714
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12329
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 052bdb5899bb723b6d375c66ab2ceab028adab06
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 21 12:00:03 2015 -0400

    core: use syscall wrappers instead of direct syscalls - regression test
    
    various xlators and other components are invoking system calls
    directly instead of using the libglusterfs/syscall.[ch] wrappers.
    
    If not using the system call wrappers there should be a comment
    in the source explaining why the wrapper isn't used.
    
    Change-Id: Id2207deb81a75e1af6f34bf857e74725f8bb532f
    BUG: 1267967
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12410
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit dcd1ff344d242f64f3a5c579df97a050736e6633
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Sat Nov 14 14:35:26 2015 -0500

    cluster/tier make cache mode default for tiered volumes
    
    The default mode for tiered volumes must be cache. The current
    test mode was for engineering and should ordinarily not be used
    by customers.
    
    Change-Id: I20583f54a9269ce75daade645be18ab8575b0b9b
    BUG: 1282076
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12581
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>

commit 38bfd4e43c42cbf2a8591b546b808c6ec811995f
Author: vmallika <vmallika@redhat.com>
Date:   Mon Nov 9 11:55:15 2015 +0530

    quota: fix spurious failure
    
    Change-Id: I5d18533d66df3175752a73430f680dcdfdb3c12a
    BUG: 1278689
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12546
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit eada31c88f929768df5fa337137b2ffcd57f2e73
Author: jiffin tony thottan <jthottan@redhat.com>
Date:   Mon Nov 16 15:51:01 2015 +0530

    marker : handle variable `ret` properly in marker_unlink_cbk
    
    While compiling new source, the following issue got hit :
    marker.c: In function 'marker_unlink_cbk':
    marker.c:994:29: warning: variable 'ret' set but not used
             int32_t             ret     = 0;
    This patch will fix the same.
    
    Change-Id: I0de60bed3351b3aa1cc80f52d178e447826210e7
    BUG: 1257694
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12584
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b6323c1995223d3566ffca12145c943df3fdc2ed
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Thu Nov 12 13:43:31 2015 +0530

    dht: loc should store proper gfid
    
    Change-Id: Ic1393d44a9ed4aaba23d7c9ddea45977b9dae5e4
    BUG: 1281265
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/12574
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 76f70b9ebff03208c5dcce71e9afe511439dd44c
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Tue Nov 10 10:27:22 2015 +0530

    dht: set proper errno when hashed subvol is not found
    
    Change-Id: I0c4c72e2f5a9f8a7c60ef65251c596b54de89479
    BUG: 1279705
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/12559
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9f2a81c4796c61c42660ff3407ca12ec4f137593
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Nov 16 19:20:22 2015 -0500

    core: use syscall wrappers instead of direct syscalls - tail(2)
    
    tail, as in dog chasing its tail. These are the unwrapped
    syscalls that have crept in (or were missed) in the previous
    patches.
    
    various xlators and other components are invoking system calls
    directly instead of using the libglusterfs/syscall.[ch] wrappers.
    
    If not using the system call wrappers there should be a comment
    in the source explaining why the wrapper isn't used.
    
    Change-Id: I6015f97109c4250a5a049496a214d19835e4ae19
    BUG: 1267967
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12590
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 535c9c117d88498e506103d212403d94e07c9ae1
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Nov 17 08:38:59 2015 +0530

    tier/ctr : MArking ./tests/basic/tier/record-metadata-heat.t as bad
    
    ./tests/basic/tier/record-metadata-heat.t as bad
    
    Change-Id: I92e1f9f3103e557e99af627d25700946fcb0b7a7
    BUG: 1282673
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12591
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 1d0a0d180b34961ce03352283c5cb1f0c1561d88
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Mon Nov 16 10:54:01 2015 -0500

    core: use syscall wrappers instead of direct syscalls - tail
    
    tail, as in dog chasing its tail. These are the unwrapped
    syscalls that have crept in (or were missed) in the previous
    patches.
    
    various xlators and other components are invoking system calls
    directly instead of using the libglusterfs/syscall.[ch] wrappers.
    
    If not using the system call wrappers there should be a comment
    in the source explaining why the wrapper isn't used.
    
    Change-Id: If183487de92fc7cbc47d4c5aa3f3e80eae50b84f
    BUG: 1267967
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12589
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit caae86e6f8b8150ad8663c3173fcd6df3c2e260a
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Nov 5 19:57:51 2015 +0530

    build: fix ecdh.h and dh.h deps
    
    openssl.ecdh.h and openssl/dh.h are not available on all platforms.
    This patch adds check to autoconf and updates relevant source files.
    Add missing #include "config.h" to socket.c to make HAVE_OPENSSL_DH_H
    and HAVE_OPENSSL_ECDH_H macros available.
    
    Definitions for UTIME_OMIT and UTIME_NOW in
    contrib/qemu/util/oslib-posix.c have been selected from
    /usr/include/bits/stat.h on Fedora 22
    
    SSL context options SSL_OP_NO_TICKET and SSL_OP_NO_COMPRESSION are now
    conditionally set by testing their presence.
    
    glusterfs.spec.in file now adds CFLAGS=-DUSE_INSECURE_OPENSSL for
    RHEL < 6 in the %build section.
    
    Change-Id: Ie32a950dad77bb0f09b4ba53edb3e1f3147056f3
    BUG: 1258883
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/12517
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2099cc875a4d20ab1bb12b1c33da16c95968e202
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Oct 1 16:28:58 2015 -0400

    core: use syscall wrappers instead of direct syscalls - libglusterfs
    
    various xlators and other components are invoking system calls
    directly instead of using the libglusterfs/syscall.[ch] wrappers.
    
    If not using the system call wrappers there should be a comment
    in the source explaining why the wrapper isn't used.
    
    Change-Id: Ieeca2d36adbc884e4cfa0026dba40df70310d40b
    BUG: 1267967
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12275
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3f0c70f2d56743707699f6a5b62a1c2c2d5c6f85
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Thu Nov 12 12:28:53 2015 +0530

    afr: replica pair going offline does not require CHILD_MODIFIED event
    
    As a part of CHILD_MODIFIED event DHT forgets the current layout and
    performs fresh lookup. However this is not required when a replica pair
    goes offline as the xattrs can be read from other replica pairs. Hence
    setting different event to handle replica pair going down.
    
    Change-Id: I5ede2a6398e63f34f89f9d3c9bc30598974402e3
    BUG: 1281230
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/12573
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ea7e34f38c97b471fee863fa749e1f0389c4b563
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Jul 14 23:24:55 2015 +0530

    extras/hooks: Fix parsing of args in S30samba-set.sh
    
    Change-Id: I75756f44757a144b0ed229fcc0e29a273fc75886
    BUG: 1242892
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11668
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 6000e1aa344e523aa161427a0b9781e052cd4d97
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu Oct 1 11:05:25 2015 -0400

    cluster/tier: Disallow detach commit when detach in progress
    
    1. Check if detach is running, disallow detach commit if so.
    2. Cleanup shutdown of tier daemon on detach: do not rerun fix-layout,
       do not send incorrect status back to glusterd.
    
    Change-Id: I97202f748773c1176396a4ffd32a4c7fa9b9c1bc
    BUG: 1279637
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12560
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 571cbcf56ef865d64ebdb1621c791fe467501e52
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Nov 9 16:43:21 2015 +0530

    glusterd: brick failed to start
    
    brick volfiles are generated in post validate, if
    it is running version higher than GLUSTER_3_7_5,
    else will be running in syncop.
    
    If the code fall back to syncop, and volume is stopped
    then we were returning the operation with out generating
    volfiles.
    
    Change-Id: I3b16ee29de19c5d34e45d77d6b7e4b665c2a4653
    BUG: 1282322
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12552
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 82e45b87e30ce4ec2ab62c39820951da7a82eddb
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 14 11:13:50 2015 -0400

    build: install and package header files more conventionally
    
    The current way we install and package header files for the -devel
    package is a hack. This patch uses more conventional autoconf, libtool,
    and rpmbuild idioms to package -devel headers and libraries.
    
    Change-Id: I63ffb3460f5c12b6b355493bd00824ac9e5354c5
    BUG: 1271907
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12360
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 8ad921e8d61e8b7b1dcd4aaba5d00aafbb55cf2a
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Fri Nov 13 12:55:17 2015 -0500

    packaging: gfind_missing_files not in geo-rep %if ... %endif conditional
    
    if geo-rep is disabled in the build then the gfind_missing_files
    are erroneously included in the ganesha sub-package
    
    Change-Id: I440df7e8283bcc8a80aa057c1c9d6f8034ca98d2
    BUG: 1281892
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12577
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 92e3bbbad803688a4dbcbab6bcd35867aa055da1
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Mon Oct 12 13:14:08 2015 +0530

    cluster/afr : Remove stale indices
    
    Change-Id: Iba23338a452b49dc9fe6ae7b4ca108ebc377fe42
    BUG: 1270668
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/12336
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d4aaa00d77d7a10748a1ca9af82265ad9ac42598
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Sun Nov 8 15:33:15 2015 +0530

    tier/ctr: Providing option to record or ignore metadata heat
    
    Currently we heat up a file for both data and metadata write.
    Here we provide a ctr xlator option called "ctr-record-metadata-heat"
    were the admin can decide on recording metadata heat i.e heatup a
    file on metadata writes or not.
    Metadata data operation are
    a. setattr: explicit changing of atime/mtime using utimes,
                changing of posix permissions of the file
    b. rename: Renaming a file,
    c. unlink, link: adding or deleting hardlinks
    d. xattrs: setting or removal of xattrs.
    
    NOTE: atime, mtime and ctime change through writev, readv, truncate, mknod
    and create will not be considered here as these fops are data and primary
    metadata fops.
    
    Defaultly "ctr-record-metadata-heat" is off. Admin can
    switch it on using gluster volume set command.
    
    Change-Id: I91157509255dd5cb429cda2b6d4f64582e155e7b
    BUG: 1279166
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12540
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 4af4c1acc7b77d70af1b09964c7cbddb5c797214
Author: Bipin Kunal <bkunal@redhat.com>
Date:   Fri Nov 13 19:19:17 2015 +0530

    docs: move contributor docs to the glusterdocs repository
    
     *  Moved few files to glusterdocs repo
     *  Files were moved in pull requests given below:
        https://github.com/gluster/glusterdocs/pull/60
        https://github.com/gluster/glusterdocs/pull/62
     * This patch removes file from this repo which were
       moved to glusterdocs repo
    
    Change-Id: I6e529911e0be66b261961c44bcdbe361aafa2886
    BUG: 1206539
    Signed-off-by: Bipin Kunal <bkunal@redhat.com>
    Reviewed-on: http://review.gluster.org/12576
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b7b13c73369a3cb237de16d58425b63640c6f33e
Author: Kaleb S KEITHLEY <kkeithle@redhat.com>
Date:   Fri Nov 13 14:07:03 2015 -0500

    build: `make distclean` doesn't clean all it ought to, needs to
    
    Debian builds fail to "build twice in a row" due to left over files
    remaining after running `make distclean`
    
    The main culprits are files created from *.in files during ./configure.
    In particular these are ./glusterfs-api.pc, ./libgfchangelog.pc,
    ./libgfdb.pc, and ./tests/env.rc.
    
    The strange one is contrib/umountd/Makefile{,.in}. While these are
    created by ./configure - for reasons I don't quite fathom, perhaps
    because contrib/umountd is included in EXTRA_DIST - after that
    make and make distclean don't descend into the directory to build or
    clean it (because it's not needed for Linux, and not built.)
    
    Also removing the `find . -name Makefile -exec rm -f {}\;` from the
    gitclean target, it's not needed (redundant) as its prereq distclean
    target will have already removed them.
    
    Change-Id: Ifc45b71d852052ef4b92f356279ce2ba2bbc5bb6
    BUG: 1279836
    Signed-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12579
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Tested-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 869b81fceabf3b9d5508665fc36fa7f98a4d4316
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Nov 11 15:54:10 2015 -0500

    tests: fix spurious error in fops-during-migration-pause.t
    
    The test did not spend long enough time moving the file for the
    pause to occur simultaneously, leading to failure. Solution is
    to elongate that time by increasing the file size.
    
    Change-Id: I1727fa9e3f7a987dfa07dd5da44c68d3f17218d9
    BUG: 1280428
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12570
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit 3dadb0f4eff1cad703be92b17f7c230955e12d67
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Nov 10 22:50:55 2015 +0530

    tier/libgfdb: Extending log level flexibity in libgfdb
    
    Extending log level flexibity to relevant fops and operations
    This is an extension to
    http://review.gluster.org/#/c/12491/
    
    Change-Id: I33b2f7732f89f52569fb99baa692c7e3bb4c7ab1
    BUG: 1277352
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12567
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 9a69ad2c8438b9fbdcb133404a5d205f809bbb5a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Nov 10 09:06:54 2015 +0530

    cluster/ec: fix bug in update_good
    
    Problem:
    Bricks that didn't participate in the fops are considered to be good. This is happening two fold.
    Examples:
    Case-1:
    1) 2+1 volume. 'd1' directory on Brick-0 is bad.
    2) readdir takes locks and lock->good_mask is '7'
    3) readdir does xattrop and fop->mask is '6'.
    4) because fop->expected is '1' lock->good_mask remains '7'
    
    Case-2:
    1) when all the bricks are up, it does lock + xattrop before op and figures out
       all the bricks are good.
    2) By the time second operation starts brick-0 is down. Now lock->good_mask
       will always have the '0' bit set as long as the operations are happening on it.
       because: "lock->good_mask &= ~fop->mask | fop->remaining" fop->mask doesn't
       have '0' th bit.
    3) When it comes time to perform the final xattrop in update_size_version
       brick-0 comes online because of which it gives the same version to brick-0
       as well thinking it has participated in all the transactions till then, even
       when it didn't participate in the transactions.
    
    Fix:
    Case-1's fix: Update lock->good_mask in ec_prepare_update_cbk with latest
    good/bad bricks
    Case-2's fix: Consider non-participating brick as bad.
    
    Change-Id: Ic01a733f8180131ded6a3cc784fcb1960758cf23
    BUG: 1276989
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12561
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit d025d954a5c593ccb0838788e165c36cb3537b25
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Nov 9 20:36:11 2015 +0530

    tier/ctr: ignoring bitrot scrubber fops
    
    We had missed adding  GF_CLIENT_PID_SCRUB to the internal fops
    list of bitrot. Doing that in this fix
    
    Change-Id: I0c7de37e2bf625fb577a32a599a885ee95f5d3bd
    BUG: 1278326
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12555
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit a02cb725c7fd0d8fbc94d7d815fdf5494815ac93
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Oct 26 12:07:16 2015 +0530

    Remove selinux mount option from "man mount.glusterfs"
    
    Gluster doesn't SELinux mount option, so it is removed.
    
    Change-Id: I471ad98a24b5f5d64279c805b3243cb1168dd3d1
    BUG: 1274626
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12422
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0c1cd89b03aa3945d8472ca86a10d05d2a8d8028
Author: Anoop C S <anoopcs@redhat.com>
Date:   Tue Nov 10 16:20:27 2015 +0530

    build: Remove systemtap references from source
    
    We don't actually support systemtap. And so it is confusing
    to have --enable-systemtap configure option in configure.ac.
    This patch removes the systemtap option and corresponding
    references from other files which include INSTALL, spec.in,
    docs etc.
    
    Change-Id: I719c22ca36f41a2faca156f8e41daea44e64b65e
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/12565
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c0522295f42c57565610d186da1400730b6a68d1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Sep 15 16:56:01 2015 +0530

    features/gfid-access: Fix entry creation via setxattr for geo-rep
    
    GEO-REP INTEROP WITH SHARD FEATURE
    
    Problem:
        Geo-replication uses setxattr interface of gfid-access
        xlator to create entries and send explicit setattr
        after entry creation to set uid and gid. But between
        entry creation and setattr, the inode would not be
        linked. Hence operation which accesses inode structure
        during setattr by any the below xlator fails.
    
    Solution:
        Linking inode would seem the obvious solution but,
        gfid-access xlator cannot link inodes and maintain
        it as it would result in same inode pointing
        to two different paths one being virtual .gfid/<gfid>
        path and other being actual path.
    
        The solution is to set uid and gid in frame->root->uid
        and frame->root->gid respectively from which posix
        extracts and sets.
    
    Change-Id: Ic0749ee471432caeb8ded3152a07de6e64d8538d
    BUG: 1265148
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12206
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 4ac2ff18db62db192c49affd8591e846c810667a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Nov 9 13:04:03 2015 +0100

    build: MKDIR_P is not defined for Makefiles, use mkdir_p instead
    
    Change-Id: Id6d5263eb7b1c53e72a7668e716e9cc4e34b82cd
    Reported-by: Milind Changire <mchangir@redhat.com>
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/12553
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 066a45d76021bfda09bdb57108d677eae7eba92b
Author: Shubhendu Tripathi <shtripat@redhat.com>
Date:   Wed Jul 22 16:55:06 2015 +0530

    extras: Exit with SUCCESS if no processes to stop
    
    This script might be executed even when there are no
    valid processes running to be stopped. In this scenario,
    the script should return with SUCCESS
    
    Change-Id: Ia293214a4b5052bc4bef9769f197f7b05c55ffe9
    BUG: 1277533
    Signed-off-by: Shubhendu Tripathi <shtripat@redhat.com>
    Reviewed-on: http://review.gluster.org/11739
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 0d6f054dbbeffa7190cb41746251c6b77be59a53
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Nov 6 17:39:38 2015 +0100

    tests: make mount-nfs-auth.t more stable
    
    mount-nfs-auth.t has a funky way of restarting the Gluster/NFS service.
    It is a little racy and does not always work. Disabling and enabling the
    nfs.disable volume option triggers a restart of the Gluster/NFS service
    too, and is much simpler.
    
    Also adding a little more EXPECT_WITHIN statements to prevent the
    occasional failures.
    
    Change-Id: I6765e9f021abbe995dfac00fbfc67298e2ec769c
    BUG: 1278476
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/12542
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fab69583da8b41b6abdc5f130d107b1887aa2056
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Nov 9 10:19:25 2015 +0530

    snapshot: Remove bug-1275616.t from bad tests
    
    Remove bug-1275616.t from bad tests list as
    commit 466f56a91265ac928759642a866bdc27e850654f
    has fixed the spurious failure.
    
    Change-Id: I0d3d86e4e98e3ca810692835ca0a7f119b759620
    BUG: 1279297
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12544
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6e036c758add503a170cc3134e95fea3e78e89cb
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Oct 29 09:30:15 2015 +0000

    geo-rep: Make restrictive ssh keys optional
    
    In containerized environment where networking
    configuration is "net=host", both host and
    containers use the same IP. The validations
    gsyncd shell and rsync to be the siblings
    fails. Hence, for now, creating restrictive
    ssh keys is made optional as follows.
    
    If the argument 'container' is passed, it
    will create non restrictive ssh keys else
    restrictive ssh keys.
    
    e.g.,
    gluster system:: execute gsec_create container
         Creates non restrictive ssh keys.
    gluster system:: execute gsec_create
         Creates restrictive ssh keys.
    
    Change-Id: Ibed362f64b9b4c9931207f863a2da944c6bd1d66
    BUG: 1276028
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12459
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 2794cb71b96c44033dcd01102039c038956cf7b5
Author: vmallika <vmallika@redhat.com>
Date:   Mon Nov 2 15:39:46 2015 +0530

    marker: do remove xattr only for last link
    
    With unlink, rename, rmdir, contribution xattrs
    are removed. If the file is a last link
    then remove_xattr will fail with ENOENT.
    
    So it better to perform remove_xattr
    only if there are more links to the file
    
    Change-Id: Ifc1e7fda4d310fd87f6f28a635c9ea78b8f3929d
    BUG: 1257694
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12033
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c8c9308134ae4ce24c630a1b0ccfcf4e8f9b0fe7
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Aug 12 14:56:27 2015 +0530

    md-cache: Remove readdirp fop for md-cache
    
    readdirp call will return inode for each entry and
    will share this nodeid with kernal, also md-cache
    will cache this gfid and base name. So when a lookup
    operation is perfromed on such an inode, md-cache
    will wind the call, that prevents populating inode
    ctx for other lower layer xlators.
    
    Change-Id: I43c768703a3cc66d05b1c32909d1a2781001cb49
    BUG: 1236032
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11894
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 529c3bf41f666d1238f71fba0465eaa812322276
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Oct 29 20:39:57 2015 +0530

    gfapi: function exit should use __GLFS_EXIT_FS
    
    glfs api functions must be using __GLFS_EXIT_FS to exit from functions
    
    Change-Id: If6b71d8182f3dffe15a3606f31798904cb67be1b
    BUG: 1263056
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/12462
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 5d1ff7efd6ab3bd29a29922a9ea1e1aaf02544ad
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Oct 30 17:06:58 2015 +0530

    geo-rep: Kill Geo-rep Worker when Agent process dies
    
    When Changelog agent process dies, Geo-replication fails to detect
    and worker will run without respective Changelog agent. Status shows
    Active/Passive without any progress.
    
    With this patch, Worker process gets killed whenever Changelog
    agent dies.
    
    Change-Id: I30b4cc77f924f7e8174b8bfe415ac17f0b3851b4
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1277076
    Reviewed-on: http://review.gluster.org/12485
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit f68c95a429b44afc0197152a7819d17ce1de734c
Author: Anoop C S <anoopcs@redhat.com>
Date:   Wed Oct 14 13:11:37 2015 +0530

    build: Fix autoconf warnings
    
    This patch avoids the following warnings on running autogen script
    
    . . .
    Running autoconf...
    configure.ac:896: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in
    body
    ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
    configure.ac:896: the top level
    . . .
    
    This change uses AC_LINK_IFELSE for checking the atomic built-in function
    support. Since AC_COMPILE_IFELSE checks for syntactical errors only, we need
    to use AC_LINK_IFELSE to achieve the same which is more appropriate.
    
    Reference links:
    [1] https://autotools.io/forwardporting/autoconf.html
    [2] http://www.gnu.org/software/autoconf/manual/autoconf.html#Generating-Sources
    [3] http://www.gnu.org/software/autoconf/manual/autoconf.html#Running-the-Compiler
    
    Change-Id: I4597f2976623496745b66f98bb78a0c9f1b07f79
    BUG: 1198849
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/12351
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 01ed634a490d3ea7c4bbb051a0a9f0512f8f7694
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Oct 15 12:01:14 2015 +0530

    dht: heal directory path if the directory is not present
    
    After a successful nameless lookup if the directory is not
    present on any of the subvol, then we will get the path of
    the directory and will recursively send a named lookp on
    each parent directory.
    
    This will help particularly for the scenarios like add brick
    and attach-tier.
    
    Change-Id: I64c2118a5ab03bbaa59b0dfc62babdf4472a92a3
    BUG: 1272949
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12376
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 68869f02fc540104a18472f348f0a20948989bef
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Oct 28 23:10:00 2015 +0530

    dht: update cached subvolume during readdirp cbk
    
    This reverts commit bb2370514598a99e6ab268af81df57dc16caa2c5.
    
    issue and impact: readdirp_cbk was not resetting the layout for files,
    this causes problem if the files is moved from one cached subvolume
    and if the layout was not proper, then there is chance to fail
    entry fops if the fops executed with out a lookup. Because the
    cached subvolume will not change and the application assumes the
    presence of file in cached subvol. so it fails with ENOENT.
    
    The patch preset the layout information in readdirp cbk
    for each files in the entry. That leaves the problem the commit
    bb2370514598a99e6ab268af81df57dc16caa2c5 try to fix. We will fix the
    problem in a separate patch.
    
    Change-Id: I878ec32f44edde2fb9d4f132d9b1b547cde993d9
    BUG: 1272949
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12449
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit dc8d65381bbead0a00d045b7040e0cd86d80955b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Sep 21 14:51:13 2015 +0530

    geo-rep: Fix syncing chown in xsync crawl
    
    GEO-REP INTEROP WITH SHARD FEATURE
    
    Problem:
        The sequence of entry creation and chown in master
     is recorded as creation of entry with resulted
     user:group in xsync changelog. During sync, entry
     creation is always split into two ops, MKNOD and
     SETATTR. Hence the issue is not being hit otherwise
     it would have failed with EPERM if parent is owned
     by different user. But with shard translator being
     enabled on slave, doing entry creation with MKNOD and
     SETATTR is not allowed, SETATTR fails as it accesses
     inode structure which is not linked.
    
    Solution:
        The sequence of entry creation and chown in master
     should be recorded as MKNOD and SETATTR separately always
     and do entry creation with single op in gfid-access
     xlator. The gfid-access patch will be sent separately.
    
    Change-Id: I93e554bf9342397a7660503f5128e9709f8a0cd8
    BUG: 1265148
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12205
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit a37eb179111b848925928009903cc4a98c0781e3
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Oct 15 19:40:55 2015 +0530

    Revert "fuse: resolve complete path after a graph switch"
    
    This reverts commit d0edb6d555d687f76837515207b9408be0bdd55e.
    The same functionality will be provided in a different patch
    
    Change-Id: I3139478b218fa32e803bb088df585fbbdf94af34
    BUG: 1272949
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12375
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 06630972e786c205a485693f66039cd9bb10dc9d
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Sun Nov 1 10:22:00 2015 -0500

    cluster/tier correct promotion cycle calculation
    
    The tier translator should only choose candidate files for promotion
    from the most recent cycle, not a multiple of the most recent cycles.
    Otherwise user observed behavior can be inconsistent. Remove related
    test in tier.t that is subject to race condition.
    
    Change-Id: I9ad1523cac00f904097ce468efa6ddd515857024
    BUG: 1275524
    Signed-off-by: root <root@rhs-cli-15.gdev.lab.eng.bos.redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12480
    Reviewed-by: Joseph Fernandes
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a88859127fbdebadb2895fb3d28eba3091c17cca
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Sat Nov 7 00:19:48 2015 +0530

    tiering:Message shown in gluster vol tier <volname> status output is incorrect
    
    Change-Id: I15a1a637090f1cc2f200d5c3582317e4aa3cf334
    BUG: 1278927
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/12532
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit bbaf4cdb42dfeee4d342ff4096a4985b68c74e05
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Nov 3 12:08:16 2015 +0530

    tier/ctr: Ignore CTR Lookup heal insert errors
    
    CTR doesnt read from the DB, so to make sure that file records are
    created it does a heal during a lookup. It remembers the decision in
    the inode context cache and retrys periodically. When the volume is
    restarted it looses all the inode cache from the previous time and CTR
    lookup heals tries the heal again, but this time it finds that the records
    are already there from sql and logs this error, and remembers this until the
    volume is restarted or inode is flushed out of inode cache of the brick.
    
    Solution: the log levels should be reduced to trace for this case and
    customers need not see this.
    
    Change-Id: I67b568fb6904f8597e2c6d32894a247c4f500b94
    BUG: 1277352
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12491
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 546bf89c0ca325382a1f819013ee7a1462a8effd
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Nov 6 14:23:07 2015 +0530

    snapshot: Add bug-1275616.t to bad test list
    
    bug-1275616.t fails spuriously in regression tests
    
    Change-Id: Iea01476a9ffd811091865196e1536361d2298ab7
    BUG: 1278418
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12527
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 20a227345d4343a0e2f77ed4a4774f195860c7d5
Author: vmallika <vmallika@redhat.com>
Date:   Fri Nov 6 13:17:26 2015 +0530

    quota: fix for spurious failure
    
    Filed a bug# 1278689.
    For now marking the testcase tests/bugs/quota/bug-1235182.t' bad
    once the bug# 1278689, remove the testcase from bad list
    
    Change-Id: I224f907153d3e5f35834007a40b0050246d8787a
    BUG: 1278689
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12526
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 1d0402b25aa24e2076fb79cbeb4ba3ed3a9f3ede
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Oct 14 00:00:41 2015 +0530

    tier/libgfdb: Replacing ASCII query file with binary
    
    Earlier, when the database was queried we used to save
    all the queried records in an ASCII format in the query file.
    This caused issues like filename having ASCII delimiter and used
    to take a lot of space. The tier.c file also had a lot of parsing code.
    
    Here we changed the format of the query file to binary.
    All the logic of serialization and formating of query record is done
    by libgfdb. Libgfdb provides API,
    gfdb_write_query_record() and gfdb_read_query_record(),
    which the user i.e tier migrator and CTR xlator can use to
    write to and read from query file.
    With this binary format we save on disk space i.e reduce to 50% atleast
    as we are saving GFID's in binary format 16 bytes and not the string format
    which takes 36 bytes + We are not saving path of the file + we are also saving on
    ASCII delimiters.
    
    The on disk format of query record is as follows,
    
    +---------------------------------------------------------------------------+
    | Length of serialized query record |       Serialized Query Record         |
    +---------------------------------------------------------------------------+
                 4 bytes                     Length of serialized query record
                                                          |
                                                          |
         -------------------------------------------------|
         |
         |
         V
       Serialized Query Record Format:
       +---------------------------------------------------------------------------+
       | GFID |  Link count   |  <LINK INFO>  |.....                      | FOOTER |
       +---------------------------------------------------------------------------+
         16 B        4 B         Link Length                                  4 B
                                    |                                          |
                                    |                                          |
       -----------------------------|                                          |
       |                                                                       |
       |                                                                       |
       V                                                                       |
       Each <Link Info> will be serialized as                                  |
       +-----------------------------------------------+                       |
       | PGID | BASE_NAME_LENGTH |      BASE_NAME      |                       |
       +-----------------------------------------------+                       |
         16 B       4 B             BASE_NAME_LENGTH                           |
                                                                               |
                                                                               |
       ------------------------------------------------------------------------|
       |
       |
       V
       FOOTER is a magic number 0xBAADF00D indicating the end of the record.
       This also serves as a serialized schema validator.
    
    Change-Id: I9db7416fd421e118dd44eafab8b535caafe50d5a
    BUG: 1272207
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12354
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit d51a33bae02245f8538c62b564f3fef49820790e
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Nov 6 14:36:37 2015 +0530

    tests/tier : Corrected filename in run-tests.sh
    
    bug-1214222-directories_miising_after_attach_tier.t
    was renamed to bug-1214222-directories_missing_after_attach_tier.t
     but run-tests.sh was not updated.
    
    Change-Id: I64d6475ffb08e3252e56b4083cb0e828ba3584d9
    BUG: 1278709
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12528
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 466f56a91265ac928759642a866bdc27e850654f
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Nov 5 18:19:14 2015 +0530

    snapshot: Making bug-1275616.t more regression failure tolerant
    
    snapshot clone creation fails 'spuriously' on the
    regression setup coz the brick rpc connect for snap3
    in the testcase, happens way after the snap was created.
    
    So adding a EXPECT_WITHIN $PROCESS_UP_TIMEOUT check(read delay)
    to help the cause. But this isn't a 100% guaranteed fix, as on an
    even slower machine, even this check will fail followed by the
    subsequent failures that this patch is trying to fix in the first place
    
    Change-Id: I2f31558b717fd610111f14e451fe444c09f3f254
    BUG: 1278418
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12516
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a193bb3a711177d64d1c70277a70bb220161a293
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Nov 3 18:27:18 2015 -0500

    cluster/tier: fix lookup-unhashed on tiered volumes
    
    During attach tier the commit hash must be copied to the hot tier.
    
    Change-Id: I91b92fd8e98696993433856e1436409b657c439d
    BUG: 1277716
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12498
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit f31e551c5acdb64c6409531417a2490d53009795
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Nov 5 14:59:54 2015 +0530

    tier/ctr: Ignore bitrot related fops
    
    Ignore bitrot related fops since they are internal fops.
    
    Change-Id: I5db8cf4e3fa1b186a6987eed54287bc0e964fbd4
    BUG: 1278326
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12512
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit a176028f2865875c68556f42e7d2c5a697d14046
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu Nov 5 10:04:42 2015 -0500

    xlators/nfs add mount-nfs-auth.t to ignored tests list
    
    mount-nfs-auth.t fails spuriously in regression. After discussion with
    NFS leads agree to put it into ignored list until the problem is solved.
    
    Change-Id: I44efc3332409ef963819f31d1775138d8a04a0f9
    BUG: 1278476
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12521
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 80c046f10207ab3f039210683d3931a2615861f1
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Oct 28 14:00:41 2015 +0100

    cluster/ec: Fix bad management of lock owners
    
    Since the addition of parallel reads patch for ec, a lock can have
    more than one owner at the same time. The list of owners was stored
    inside the 'owner_list' field of each fop.
    
    The problem was with fops that required more than one lock (like
    rename). In this case the same field was used to add the fop to
    more than one list, casing an overwrite of the previous list.
    
    This has been solved moving the 'owner_list' field from ec_fop_data_t
    to ec_lock_link_t structure.
    
    Change-Id: I6042129f09082497b80782b5704a52c35c78f44d
    BUG: 1276031
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/12445
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1918d618a91fe9d9021916d53091173f4ad6b882
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Oct 30 15:56:14 2015 +0530

    mgmt/glusterd: Store arbiter-count and restore it
    
    Problem:
    1) Glusterd doesn't remember about arbiter information of replica volume in
       store.  When glusterd goes down and comes backup, arbiter volumes will
       become replica volumes.
    
    2) Glusterd doesn't import/export arbiter information to/from the other peers.
    
    3) Volume info doesn't show any arbiter count in the output.
    
    Fix:
    1) Persist arbiter information in glusterd-store
    2) Import/Export arbiter information of the volume
    3) Change volume info output to show arbiter count.
    
    Change-Id: I2db81e73d2694b01f7d07b08a17b41ad5a55c361
    BUG: 1276675
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12475
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit dab82c7ba3901cfdf94db0cd69a46ea396cf920a
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Oct 29 12:06:57 2015 +0530

    tier/dht: Ignoring replica for migration counting
    
    We used to count replica files for migration counting even though
    they were ignore for migration as the replica brick didnt have
    the ownership (as per the replication xlator either AFR/EC).
    As a result the number of files migrated would show a wrong count,
    i.e each replicated file would be counted 1 + number of replica.
    
    This patch ignores such cases.
    
    Change-Id: I91aa352ee3b0a5029790653266e9333f3947d0ac
    BUG: 1276141
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12453
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 698038f67c00bd528a7be89a0fccdd52914e01ce
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Tue Nov 3 18:23:56 2015 +0530

    v info for disperse count fails while upgrading
    
    The upgrade from 3.7.5-3 to 3.7.5-5 causes the type and number
    of bricks for the cold tier to be printed wrong.
    
    Change-Id: Ia45b97c35fef88f9c66e15e5bdb93fd30cb342af
    BUG: 1277481
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12495
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit ee0b1a3bf11a4d05696212d91c932ddb7c7091ee
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Jul 28 14:52:00 2015 +0530

    geo-rep: Update last_synced_time in XSync
    
    During XSync crawl, last_synced time in status file was not updated.
    This patch fixes the issue by updating status file when stime xattr
    is updated after Xsync or Changelog Crawl.
    
    Change-Id: I4dc3a2d4c3d8378a939da0868caf1aef4f789599
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1247536
    Reviewed-on: http://review.gluster.org/11771
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 5858fb83e5c3c301023ed214ead9c0ff8cf15c1f
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Fri Oct 30 16:39:16 2015 +0530

    glusterd: move new feature (tiering) enum op to the last of the array
    
    Currently new feature tiering have GD_OP_DETACH_TIER and GD_OP_TIER_MIGRATE
    enum in the middle of the glusterd_op_ enum array. In multi nodes
    cluster when one of the node upgraded from lower version to higher
    version and upon executing command can end up in a mismatch in enum ops
    at the receiver ends causing command execution fail.
    
    Fix is to put every new feature glusterd operation enum code to last of
    the enum array.
    
    Change-Id: I640f811065e8c84add624237aa80fed43fde5967
    BUG: 1276643
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12473
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 10730517a8e51e155c57e22b32c3809d942143df
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Nov 2 15:21:19 2015 +0530

    correction of message displayed after attach tier
    
    the message after attach tier is saying rebalance.
    It is changed according to tiering.
    
    Change-Id: I1834511f86483fa60f404d7defe5be59c025e9d6
    BUG: 1277081
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12488
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 499b43058049572e33b525ac669ef623d476fe41
Author: N Balachandran <nbalacha@redhat.com>
Date:   Fri Oct 30 12:46:22 2015 +0530

    cluster/tier : Files skipped during tier query parsing
    
    The tier query parsing code was using fscanf to read each record.
    As space is a delimiter for fscanf, filenames containing spaces
    caused the parsing to return unexpected values causing various
    issues in the tier process, including crashes due to buffer
     overflows.
    
    Change-Id: Ife602cb7ecb158fccbc2c89e4d2959bd97098a87
    BUG: 1276562
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12469
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 76eaae58654560d5a2cc72f3a2de5934801a27e9
Author: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
Date:   Thu Oct 29 20:40:00 2015 +0530

    glusterd : vol replace-brick fails when transport.socket.bind-address is set in glusterd
    
    Change-Id: Id8c29aa46b526bc003a1d7023714b67805e35a99
    BUG: 1276386
    Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/12461
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 1f74a3efbd0337759878ffff5cd4ee6782ddfe3f
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Oct 28 12:30:34 2015 +0530

    snapshot: Inherit snap-max-hard-limit from original volume
    
    A snapshot should inherit snap-max-hard-limit from the original
    volume while being created and when being restored to, it should
    restore the same.
    
    Similarly a clone taken from a snapshot should inherit
    snap-max-hard-limit from the snapshot.
    
    Change-Id: If8e90e2ffc10e22086b803ac8e2638a16bcec968
    BUG: 1275616
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12437
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 2e56bde3ea952beabd27cdf8a3a10da563a00bcc
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Oct 28 15:18:07 2015 +0530

    snapshot: Don't display snapshot's hard-limit and soft-limit in vol info
    
    The snap-max-hard-limit being displayed in the volume info
    currently is propagated from system's snap-max-hard-limit as
    that is a global option common for all volumes, and hence ends
    up showing the system's snap-max-hard-limit.
    
    We should not be displaying snap-max-hard-limit and
    snap-max-soft-limit in the volume info at all, as these are
    snap config options and should be set and displayed via snap
    config command.
    
    Modified bug-1113476.t to test the same behaviour.
    
    Change-Id: I90891f0cf7fb39fd686787297c7f7cd8c1e7daa1
    BUG: 1276018
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12443
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit af8b450df8dca2b07bcfc6c32f17bc678697e9f2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Nov 2 11:03:26 2015 +0530

    io-stats: fix BSD build failure
    
    Change-Id: Ieb372cb686d32a09c6df31ec849f1b3c52e0e1cd
    BUG: 1277024
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12484
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 56ccc0d2f4a30af9304852effbf2b68694d9f587
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Nov 2 07:56:51 2015 +0530

    tests: Move ec-readdir.t to bad tests
    
    Change-Id: Ie7f6d25cbc617ff347aeb7d77fc0a60924c83f09
    BUG: 1276989
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12481
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit d90b87eed2fa68df5afcebbc54747e96f6d76cfb
Author: vmallika <vmallika@redhat.com>
Date:   Thu Oct 15 12:41:13 2015 +0530

    quota: add version to quota xattrs
    
    When a quota is disable and the clean-up process terminated
    without completely cleaning-up the quota xattrs.
    Now when quota is enabled again, this can mess-up the accounting
    
    A version number is suffixed for all quota xattrs and this version
    number is specific to marker xaltor, i.e when quota xattrs are
    requested by quotad/client marker will remove the version suffix in the
    key before sending the response
    
    Change-Id: I1ca2c11460645edba0f6b68db70d476d8d26e1eb
    BUG: 1272411
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12386
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d3e496cbcd35b9d9b840e328ae109c44f59083ce
Author: Richard Wareing <rwareing@fb.com>
Date:   Tue Jun 23 17:03:11 2015 -0700

    debug/io-stats: Add FOP sampling feature
    
    Summary:
    - Using sampling feature you can record details about every Nth FOP.
      The fields in each sample are: FOP type, hostname, uid, gid, FOP priority,
      port and time taken (latency) to fufill the request.
    - Implemented using a ring buffer which is not (m/c) allocated in the IO path,
      this should make the sampling process pretty cheap.
    - DNS resolution done @ dump time not @ sample time for performance w/
      cache
    - Metrics can be used for both diagnostics, traffic/IO profiling as well
      as P95/P99 calculations
    - To control this feature there are two new volume options:
      diagnostics.fop-sample-interval - The sampling interval, e.g. 1 means
      sample every FOP, 100 means sample every 100th FOP
      diagnostics.fop-sample-buf-size - The size (in bytes) of the ring
      buffer used to store the samples.  In the even more samples
      are collected in the stats dump interval than can be held in this buffer,
      the oldest samples shall be discarded.  Samples are stored in the log
      directory under /var/log/glusterfs/samples.
    - Uses DNS cache written by sshreyas@fb.com (Thank-you!), the DNS cache
      TTL is controlled by the diagnostics.stats-dnscache-ttl-sec option
      and defaults to 24hrs.
    
    Test Plan:
    - Valgrind'd to ensure it's leak free
    - Run prove test(s)
    - Shadow testing on 100+ brick cluster
    
    Change-Id: I9ee14c2fa18486b7efb38e59f70687249d3f96d8
    BUG: 1271310
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/12210
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 846697d91ed56ca3d76f2a78e87e7675f127f21d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jun 3 09:59:30 2015 -0400

    core: fix Ubuntu code audit (cppcheck) results
    
    This change includes an additional fix (forward port) of a fix
    made on the release-3.x branches to address a comment made after
    the original change was merged on the master branch.
    
    * release-3.7
    * Change-Id: Ie15c5919e5bf9b0a1c66e20dc42d80fdfa8bd7f4
    * BZ: 1227808
    *  http://review.gluster.org/11069
    
    Change-Id: I4fc2672ab1a17998b2e40bc43eb6a3e15058a086
    BUG: 1109180
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11067
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d29dd0747dbb2e7383867c97cbbaa8c41851db78
Author: anand <anekkunt@redhat.com>
Date:   Thu Oct 29 21:36:57 2015 +0530

    glusterd: fix info file checksum mismatch during upgrade
    
    issue: probing a new  node(>=3.6)  from 3.5 cluster is moving the peer to rejected state.
    
    fix: Disperse vol support is added from 3.6 release, so write disperse fields (disperse_count=0
    and redundancy_count=0) in vol info file  only if cluster version supported.
    
    Change-Id: I11d5e2e337b9bbaddc8e52ca7295ba481beb1132
    BUG: 1276423
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/12464
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit d1b488fbf9b0b985657297f842819785b7599e5d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Oct 27 09:37:56 2015 +0530

    afr/glusterd: Fix naming issue in tier related changes
    
    changing some of the function names added recently as
    part of the tiering changes.
    
    Change-Id: I238831128ee00cdf83f8a80be937d3528d133099
    BUG: 1275489
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12431
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 5583bac79851d24f0a552478b361049fe63c32b7
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Aug 27 23:26:40 2015 +0530

    snapshot : copying nfs-ganesha export file
    
    While taking snapshot, the export file used by the volume should
    copy to snap directory. So that when restore of snapshot happens,
    the volume can retain all its configuration for exporting via
    nfs-ganesha. The export file is stored at "/etc/ganesha/export" in
    the following format "export.<volname>.conf"
    
    The fix handles given cases in the following manner :
    
    case a: The nfs-ganesha(global) is ON during snapshot and restore.
            i.) Volume was exported during snapshot. When we restore snapshot,
                then volume should be exported back with old configuration file.
            ii.) Volume was unexported during snapshot. When we restore snapshot,
                 then volume should unexported again.
    
    case b: The nfs-ganesha is ON during snapshot and OFF during restore
            Volume was exported during snapshot. When we restore snapshot, the
            conf will be copied to corresponding location and if nfs-ganesha enabled
            again, then volume will be exported.
    
    For the clones, export conf file will created in /etc/ganesha/export and then
    export it via ganesha.
    
    Change-Id: Ideecda15bd4db58e991cf6c8de7bb93f3db6cd20
    BUG: 1257709
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12034
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit e13733ab871f34c54a6fc44059b3343a5c2f992a
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Oct 23 12:10:42 2015 -0400

    cluster/tier enable CTR on attach tier
    
    CTR is currently disabled by default, and must be manually enabled
    for tiering to start. This is an overhead on the administrator and
    easy to overlook. Enable it automatically when a tier is attached.
    
    Change-Id: I0c29de8762faec1bfe6d1376a57eeef3357ad15a
    BUG: 1274847
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12420
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>

commit ee4f6175d1e1e6d6b82631d72c993db5691ad205
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Oct 29 12:29:04 2015 +0530

    nfs : avoid invalid usage of `cs` variable in nfs fops
    
    Due to changes from http://review.gluster.org/#/c/12162/ a path variable
    is added to nfs3_log_common_res() and usually `cs->resolvedloc.path` is
    passed for that. But in certain fop function `cs` may not filled due error
    and when it is logged using nfs3_log_common_res() results in a crash.
    This patch will fix the same.
    
    Change-Id: I5a709818923e7884bd04e329834ee352a1b3a58f
    BUG: 1276243
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12458
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit b191047eb21be0dfc28c7d93db88db46ed1655bd
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Sep 24 12:59:08 2015 +0530

    geo-rep: Handle FXATTROP and XATTROP
    
    GEO-REP INTEROP WITH SHARD FEATURE
    
    If it is FXATTROP or XATTROP in changelog,
    add the gfid to rsync queue.
    
    Change-Id: If68d38d7ed00b70a4618cfcc8e75df3fbadbf724
    BUG: 1265148
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12226
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit c1c5075df463fd298418bf31384b6d92f84d194b
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Oct 16 09:57:22 2015 -0400

    fuse: Avoid redundant lookup on "." and ".."
    credit: R. Gowdappa
    
    Change-Id: I3bc1534e499f2eccd114db69a29c0b2ce82775db
    BUG: 1273315
    Reviewed-on: http://review.gluster.org/12374
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a53c5c8e322e30b865b7c69aa9558474e033c89a
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Aug 26 04:49:29 2015 -0400

    cluster/dht/rebalance: rebalance failure handling
    
    At current state rebalance aborts basically on any failure
    like fix-layout of a directory, readdirp, opendir etc. Unless it is
    not a remove-brick process we can ignore these failures.
    
    Major impact:  Any failure in the gf_defrag_process_dir means there
    are files left unmigrated in the directory.
    
    Fix-layout(setxattr) failure will impact it's child subtree i.e.
    the child subtree will not be rebalanced.
    
    Settle-hash (commit-hash)failure will trigger lookup_everywhere for
    immediate children until the next commit-hash.
    
    Note: Remove-brick opertaion is still sensitive to any kind of failure.
    
    Change-Id: I08ab71909bc832f03cc1517172525376f7aed14a
    BUG: 1257076
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12013
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 33b1e373ee40546e1aeed00d4f5f7bfd6d9fefb9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Oct 26 16:56:25 2015 +0530

    cluster/afr: disable self-heal lock compatibility for arbiter volumes
    
    Problem:
    afrv2 takes locks from infinity-2 to infinity-1 to be compatible with <=3.5.x
    clients. For arbiter volumes this leads to problems as the I/O takes full file
    locks.
    
    Solution:
    Don't be compatible with <=3.5.x clients on arbiter volumes as arbiter volumes
    are introduced in 3.7
    
    Change-Id: I48d6aab2000cab29c0c4acbf0ad356a3fa9e7bab
    BUG: 1275247
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12426
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 36ea43b93b8476595ac22da031bc42a807ccc852
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Oct 1 16:16:52 2015 -0400

    core: use syscall wrappers instead of direct syscalls
    
    various xlators and other components are invoking system calls
    directly instead of using the libglusterfs/syscall.[ch] wrappers.
    
    If not using the system call wrappers there should be a comment
    in the source explaining why the wrapper isn't used.
    
    Change-Id: I8ef94c48728666465abf126c778b70c9e5c00e47
    BUG: 1267967
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12273
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 323e71617fee5020324540776d0d4469577f0afe
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Wed Jul 15 14:19:49 2015 +0530

    cli : 'gluster volume help' output sorted alphabetically
    
    'gluster volume help' output is not sorted alphabetically.
    This makes little harder for the user to search or get to know of
    few gluster volume commands usage just from gluster cli.
    
    Change-Id: I855da2e4748a5c2ff3be319c50fa9548d676ee8a
    BUG: 1242894
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/11663
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>

commit 3066a21caafab6305527991de11c8eb43ec0044c
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Oct 1 16:31:19 2015 -0400

    core: use syscall wrappers instead of direct syscalls - miscellaneous
    
    various xlators and other components are invoking system calls
    directly instead of using the libglusterfs/syscall.[ch] wrappers.
    
    If not using the system call wrappers there should be a comment
    in the source explaining why the wrapper isn't used.
    
    Change-Id: I1f47820534c890a00b452fa61f7438eb2b3f667c
    BUG: 1267967
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12276
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 063d4ead61ee47433793de81a1c77e0ba69e6e07
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Oct 16 13:52:28 2015 -0400

    core: use syscall wrappers instead of direct syscalls -- glusterd
    
    various xlators and other components are invoking system calls
    directly instead of using the libglusterfs/syscall.[ch] wrappers.
    
    If not using the system call wrappers there should be a comment
    in the source explaining why the wrapper isn't used.
    
    Change-Id: I28bf2a5f7730b35914e7ab57fed91e1966b30073
    BUG: 1267967
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12379
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 641b3a9164227db52df1aab05795c90d06b315f2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Oct 21 21:05:46 2015 +0530

    afr: write zeros to sink for non-sparse files
    
    Problem: If a file is created with zeroes ('dd', 'fallocate' etc.) when
    a brick is down, the self-heal does not write the zeroes to the sink
    after it comes up. Consequenty, there is a mismatch in disk-usage
    amongst the bricks of the replica.
    
    Fix: If we definitely know that the file is not sparse, then write the
    zeroes to the sink even if the checksums match.
    
    Change-Id: Ic739b3da5dbf47d99801c0e1743bb13aeb3af864
    BUG: 1272460
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12371
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8e5a7632edd040031e4942134331172805bc8eff
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Oct 20 11:46:10 2015 +0530

    features/shard: Force cache-refresh when lookup/readdirp/stat detect that xattr value has changed
    
    Change-Id: Ia3225a523287f6689b966ba4f893fc1b1fa54817
    BUG: 1272986
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12400
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3c6928f4daa6bd89ffa14049ba44337c049a9c89
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Oct 26 14:19:24 2015 -0400

    cluster/tier do not log error message on lookup heal for files on hot tier
    
    On fix-layout heal files are scanned. Files found are exist on the hot or cold
    subvolume. Those not found in the cold tier would exist on the hot. They
    should not be flagged as an error.
    
    Replace INFO with TRACE for common tier migration logs. Frequent migration
    was growing the log files too quickly.
    
    On migratation failures, do not acrue files towards cycle limit's budget.
    
    Change-Id: Ie832ee07c43bce5477ae81c939d1fe8416a11615
    BUG: 1275383
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12430
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit 2c76c52c337a0a14e19f3385268c543aaa06534d
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Fri Oct 23 13:27:51 2015 +0530

    cluster/ec: update version and size on good bricks
    
    Problem: readdir/readdirp fops calls [f]xattrop with
    fop->good which contain only one brick for these operations.
    That causes xattrop to be failed as it requires at least
    "minimum" number of brick.
    
    Solution: Use lock->good_mask to call xattrop. lock->good_mask
    contain all the good locked bricks on which the previous write
    opearion was successfull.
    
    Change-Id: If1b500391aa6fca6bd863702e030957b694ab499
    BUG: 1274629
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/12419
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c3ed484af54e32c1ef2300cda652604d75dc9d20
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Sep 14 17:09:29 2015 +0530

    glusterd: call glusterd_store_volinfo in bump up op-version
    
    After an upgrade, op-version is expected to be updated through gluster volume
    set. If the new version introduces any feature which changes volinfo structure
    without storing the default values of these new options would result into cksum
    issues.
    
    Change-Id: I57b4667f3403839811735bf66bef29e5200a9241
    BUG: 1262805
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12171
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>

commit 17e95cb81776650a2f68be00298c4f85b41e4242
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Fri Oct 23 11:57:42 2015 +0530

    features/changelog: record mknod if tier-dht linkto is set
    
    This is a series of patches which aims to fix geo-replication
    in a Tiering Volume.
    
    Problem:
    Consider, a file is placed in volume initially and then hot tier is
    attached. During any operation on the file, due to lookup a linkto
    file is created in hot tier.
    
    Now, any namespace operation carried out on the file is recorded in
    both cold and hot tier.
    There is a room for races when both changelogs are replayed.
    
    Solution:
    So, We are going to replay (namespace related)operations
    only in the hot tier.
    
    Why?
    a. If the file is directly placed in Hot tier, all fops will be
    recorded in HOT tier.
    
    b. If  the file is already present in Cold tier, and if any fop is
    carried out, it creates linkto file in Hot tier.
    Now, operations like UNLINK, RENAME are captured in Hot tier(by means of linkto file).
    
    This way, we can get both tier's operation in HOT tier itself.
    
    But, We may miss initial Data sync immediately after creating the
    file as it is only recording MKNOD. So, if MKNOD encountered
    with sticky bit set, queue DATA operation for the corresponding gfid.
    ( This geo-rep related changes are addressed in this patch: http://review.gluster.org/12326/ )
    
    So, If tier-dht linkto is set, we need to record the corresponding
    MKNOD. Earlier this was avoided as it was set as INTERNAL fop.
    (This is addressed here in this patch)
    
    Change-Id: I25514fe3e25f68592a8d6361507f8c8a4fcb70b1
    BUG: 1266875
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/12417
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 66b0caa639a179cfd699616d1fcae01c26ae6425
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Mon Sep 28 16:31:54 2015 +0530

    features/changelog: ignore recording tiering rebalance fops
    
    Recording of tiering rebalance process's fops like Creation
    and Deletion of file must be avoided.
    Ignore the fops using corresponding pid.
    
    Change-Id: Ifdc7765598d04d033f93e6339e9b188f7566cb65
    BUG: 1266875
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/12239
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit d6c7ca9d30ee573dd4620941a5b5dd1a2a4a6e98
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Sep 7 00:24:05 2015 +0530

    tests: Separate logs for each test
    
    Change-Id: Ib286e3d4d7c432dab8073fce582ccbf723eb31d2
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12110
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 92aec1cd091d23056c76e5b625b40c4766475dbb
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Oct 27 11:51:33 2015 +0530

    tier: Typo while setting the wrong value of low/hi watermark
    
    While setting the wrong value of watermark-hi/low the output
    shows "compatiblevalue" whereas it should be "compatible value"
    
    Change-Id: I29c8f9a954928d22e436465f4ebc30bd08640138
    BUG: 1275502
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12432
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit ad876d7a127cf56a3cca11c24ad2b20e1955f82b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Oct 19 16:05:17 2015 -0400

    tests: fix timeout in mount-nfs-auth.t
    
    The mount timeout was too short.  The normal configuration-change path
    (construct graph, call reconfigure) and the auth-refresh path might in
    effect run serially.  Therefore we have to wait for the *sum* of those
    two intervals.  As with all too-short-timeout problems, the result was
    that the test would run fine most of the time.  However, it has caused
    spurious failures on my own patches a half dozen times, and I have a
    half dozen other emails about it nuking other people's as well (most
    often but not always on NetBSD).
    
    The fix, obviously, is to calculate and use the right timeout value for
    NFS mount actions.  Other actions and timeouts have been left alone.
    
    Change-Id: Ic8f013c8c830e33c48bcc6d1b603d6d22a8ba3c5
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/12396
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 8216ecb871c8d74edcc46b7f13d1e1879be25de1
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Sep 24 15:42:14 2015 +0530

    features/shard: Support geo-rep for sharded volume
    
    Approach:
          Shard xlator on slave side is by passed for all the fops
    to geo-rep mount. So each shard on master is considered as a
    separate file for geo-rep and it syncs them separately on to
    slave. The extended attribute in which shard maintains the
    size is also synced from master and shard on slave doesn't
    calculate by itself.
    
    Pre-requisites:
          1. If master is sharded volume, slave also should be sharded.
          2. Slave's shard configurations should be same as master.
          3. Geo-rep config of xattr sync should not be disabled.
    
    All other dependant patches:
          1. http://review.gluster.org/#/c/12205/
          2. http://review.gluster.org/#/c/12206/
          3. http://review.gluster.org/#/c/12225/
          4. http://review.gluster.org/#/c/12226/
    
    Change-Id: I474220d69fa030b1e06a4fa0868c34fabe02efcf
    BUG: 1265148
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12228
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6188b5fcebc56b3d8af1956beeec9988f3e8f268
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Wed Oct 14 11:49:49 2015 +0530

    geo-rep: Avoid cold tier bricks during ENTRY operation
    
    This is a series of patch which aims to fix geo-replication
    in a Tiering Volume.
    
    Problem:
    Consider, a file is placed in volume initially and then hot tier is
    attached. During any operation on the file, due to lookup a linkto
    file is created in hot tier.
    
    Now, any namespace operation carried out on the file is recorded in
    both cold and hot tier.
    There is a room for races when both changelogs are replayed.
    
    Solution:
    So, We are going to replay (namespace related)operations
    only in the hot tier.
    
    Why?
    a. If the file is directly placed in Hot tier , all fops will be
    recorded in HOT tier.
    b. If  the file is already present in Cold tier, and if any fop is
    carried out, it creates linkto file in Hot tier.
    Now, operations like UNLINK, RENAME are captured in Hot
    tier(by means of linkto file).
    
    This way, we can get both tier's operation in HOT tier itself.
    
    Now, once the file is demoted to COLD tier, any namespace operation
    carried out on the cold tier can be avoided as we directly RECORD
    the same in HOT tier.
    
    How?
    1. Check whether the brick is cold tier and skip ENTRY operation.
    2. Also, if it is cold tier brick, use Xsync(which is used during initial run).
       This will help in getting all cold tier bricks changes using File System crawl
       and helps in avoiding races with hot tier brick(which can happen
       if historychangelog used in cold tier brick).
    
    Dependent patches:
    1. http://review.gluster.org/12239
    2. http://review.gluster.org/12326
    
    Change-Id: I7692b1dbb8813a7e253451bca02f8f09a5782dde
    BUG: 1266875
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/12355
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 4f65f894ab1c19618383ba212dc0f0df48675823
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Oct 20 16:27:14 2015 +0530

    mount/fuse: use a queue instead of pipe to communicate with thread
    doing inode/entry invalidations.
    
    Writing to pipe can block if pipe is full. This can lead to deadlocks
    in some situations. Consider following situation:
    
    1. Kernel sends a write on an inode. Client is waiting for a response
       to write from brick.
    2. A lookup happens on behalf of different application/thread on the
       same inode. In response, mdc tries to invalidate the inode.
    3. fuse_invalidate_inode is called. It writes a invalidation request
       to pipe. Another thread which reads from this pipe writes the
       request to /dev/fuse. The invalidate code in fuse-kernel-module,
       tries to acquire lock on all pages for the inode and is blocked as
       a write is in progress on same inode (step 1)
    4. Now, poller thread is blocked in invalidate notification and cannot
       receive any messages from same socket (on which lookup response
       came). But client is expecting a response for write from same
       socket (again step1) and we've a deadlock.
    
    The deadlock can be solved in two ways:
    1. Use a queue (and a conditional variable for notifications) to pass
       invalidation requests from poller to invalidate thread. This is a
       variant of using non-blocking pipe, but doesn't have any limit on the
       amount of data (worst case we run out of memory and error out).
    
    2. Allow events from sockets, immediately after we read one
       rpc-msg. Currently we disallow events till that rpc-msg is read from
       socket, processed and handled by higher layers. That way we won't run
       into these kind of issues. Also, it'll increase parallelism in way of
       reading from sockets.
    
    This patch implements solution 1 above.
    
    Change-Id: I8e8199fd7f4da9eab46a719d9292f35c039967e1
    BUG: 1273387
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/12402

commit ffc39c9d8807464b5c78959bc43dc12b22f5a37b
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Fri Oct 9 20:29:30 2015 +0530

    geo-rep: Add data operation if mknod with tier attribute
    
    This is a series of patches which aims to fix geo-replication
    in a Tiering Volume.
    
    Problem:
    Consider, a file is placed in volume initially and then hot tier is
    attached. During any operation on the file, due to lookup a linkto
    file is created in hot tier.
    
    Now, any namespace operation carried out on the file is recorded in
    both cold and hot tier.
    There is a room for races when both changelogs are replayed.
    
    Solution:
    So, We are going to replay (namespace related)operations
    only in the hot tier.
    
    Why?
    a. If the file is directly placed in Hot tier, all fops will be
    recorded in HOT tier.
    
    b. If  the file is already present in Cold tier, and if any fop is
    carried out, it creates linkto file in Hot tier.
    Now, operations like UNLINK, RENAME are captured in Hot tier(by means of linkto file).
    
    This way, we can get both tier's operation in HOT tier itself.
    
    But, We may miss initial Data sync immediately after creating the
    file as it is only recording MKNOD. So, if MKNOD encountered
    with sticky bit set, queue DATA operation for the corresponding gfid.
    (This is addressed here in this patch)
    
    So, If tier-gfid linkto is set, we need to record the corresponding
    MKNOD. Earlier this was avoided as it was set as INTERNAL fop.
    (This changelog related changes are addressed in the patch:
     - http://review.gluster.org/12417)
    
    Change-Id: I2fa84cfa2b0f86506c3d15d484138ab9651e4f83
    BUG: 1266875
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/12326
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit c7e30933f67f8ab8619ea28bb82e0907a26fe370
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Oct 23 11:19:30 2015 +0530

    afr: wind writes only on subvols where preop succeeded
    
    1. Call local->transaction.wind() only on subvols where pre-op
    succeeded.
    
    2. Update op_errno in afr_changelog_cbk call path. This fixes a bug in
    commit 7945121dda340ec8f25711b2ad3ca70b544de967 where we return EUCLEAN
    to the application if pre-op fails on all bricks.
    
    Change-Id: Iab8776e49a992e7a255314bba542742f7607f3ec
    BUG: 1272362
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12415
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 30653175901204b40b051e510253f09d76b3555b
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Fri Oct 23 12:27:32 2015 +0530

    tier/ctr: Correcting the internal fop calculation
    
    Correcting the internal fop calculation method, as it had wrong logic.
    
    Change-Id: I1d0b40a1e27548147203ddd503794059652ac049
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12418
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit fb2a511493868a9ff0c2926537a4d1d23821ce38
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 6 13:19:01 2015 -0400

    libglusterfs: replace default functions with generated versions
    
    Replacing repetitive code like this with code generated from a more
    compact "canonical" definition carries several advantages.
    
     * Ease the process of adding new fops (e.g. GF_FOP_IPC).
    
     * Ease the process of making global changes to existing fops (e.g.
       adding "xdata").
    
     * Ensure strict consistency between all of the pieces that must be
       compatible with each other, through both kinds of changes.
    
    What we have right now is just a start.  The above benefits will only
    truly be realized when we use the same definitions to generate stubs,
    syncops, and perhaps even parts of gfapi or glupy.
    
    This same infrastructure can also be used to reduce code duplication and
    potential for error in many of our translators.  NSR already uses a
    similar technique, using a few hundred lines of templates to generate a
    few *thousand* lines of code.  The ability to make a global "aspect"
    change (e.g. to quorum checking) in one place instead of seventy has
    already been demonstrated there.
    
    Other candidates for code generation include the AFR/EC transaction
    infrastructure, or stub creation/resumption in io-threads.
    
    Change-Id: If7d59de7a088848b557f5aea00741b4fe19017c1
    BUG: 1271325
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/9411
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 594a03b030577bf0ed6960199e920cc5fa7e7afc
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Oct 20 22:23:17 2015 +0530

    tests/tier:  Move common functions to tier.rc
    
    Move common functions in tier .t files to tier.rc
    
    Change-Id: Ibc312d987be9d93e7cc7fc47d0bf598bb1c944c2
    BUG: 1272319
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12404
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 36974c36fa4231df3f0e9428a9da6d1aa33348ab
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Oct 5 19:52:02 2015 +0000

    cluster/tier: add pause tier for snapshots
    
    Snaps of tiered volumes cannot handle files undergoing migration.
    We implement a helper mechanism to "pause" migration. Any files
    undergoing migration are aborted. Clean up is done to remove
    sticky bits and data at the destination. Migration is restarted
    after snap completes.
    
    For testing an internal switch is added. It is not exposed externally.
    
    gluster volume set vol1 tier-pause [true|false]
    
    Change-Id: Ia85bbf89ac142e9b7e73fcbef98bb9da86097799
    BUG: 1267950
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12304
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 802b24d4d9da09dfb1479eb54bd4a74f678bc97e
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Oct 21 12:12:09 2015 +0530

    Tier/cli: removing warning message for tiering
    
    The warning message for tiering being under experimental staus is removed.
    
    Change-Id: I7d1d535d380b672c70f03ecc0d24a113600ea43f
    BUG: 1273726
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12407
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 9710f58e5874bccb4b328abef80ea226ccf9c798
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Oct 20 15:53:15 2015 +0530

    cluster/dht : op_ret not set correctly in dht_fsync_cbk
    
    local->op_ret was not set correctly in dht_fsync_cbk in case
    of files being migrated
    
    Change-Id: If73ae04368ea0c7f6868c8704dfc2deb2faee753
    BUG: 1273372
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12401
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a7b57f8a0d24d0ed1cd3a8700e52f70181000038
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Oct 19 20:42:56 2015 -0400

    cluster/tier do not abort migration if a single brick is down
    
    When a bricks are down, promotion/demotion should still be possible.
    For example, if an EC brick is down, the other bricks are able to
    recover the data and migrate it.
    
    Change-Id: I8e650c640bce22a3ad23d75c363fbb9fd027d705
    BUG: 1273215
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12397
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit aa2373dab1fe2e5d5554f7cba1b77de621bb2ddf
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Oct 9 22:11:23 2015 +0530

    tests: return success if the last test ends up with core and a bad test
    
    Change-Id: Ie2695ebff8678851edb6b0b6e1de37e1f5ec9077
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12328
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 59401a32de51cdb6c1a5a1208723e89e1a4abd30
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Oct 15 16:08:03 2015 +0530

    snapshot: Fix snapshot clone postvalidate
    
    In glusterd_snapshot_clone_postvalidate(), we were deleting
    snap object and snap vol, by looking up snapname. Hence, it
    was deleting the orignal snapshot from which the clone was
    being created
    
    Instead it should fetch the clonename, the respective
    clone vol, and its corresponding snap object, and delete them.
    
    Also glusterd_snap_remove(), needs to differentiate a clone
    snap object from a snaphsot snap object, as in case of a clone
    snap object, we don't have any persisted data in
    /var/run/gluster/snaps/ and hence is shouldn't try to delete
    anything there.
    
    Change-Id: I02bb22a3898d5720e318a02d6cc32d25f75d317d
    BUG: 1272339
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/12364
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 7945121dda340ec8f25711b2ad3ca70b544de967
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Oct 16 06:23:29 2015 +0530

    afr: do not wind write if pre-op fails on all children
    
    1. When winding the pre-op, transaction.pre_op[i] is set. If the pre-op fails,
    transaction.failed_subvols[i] is set. If if fails on all chidren, we can
    directly proceed to unlock (via afr_changelog_post_op_now) without trying
    to wind the write, fail and then go to unlock.
    
    2. 'fop_subvols' seems to be an unused variable, hence removing it.
    
    Change-Id: I9525628daf48082e979b0093fa0478934495e61f
    BUG: 1272362
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12368
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>

commit cddc75e242140f8485e2377ce4e6dffe23123744
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Sep 8 12:27:50 2015 +0530

    features/snap : cleanup the root loc in statfs
    
    Problem : In svc_statfs function, wipe_loc is getting called on loc
              passed by nfs. This loc is being used by svc_stat which
              throws erro if loc->inode is NULL.
    
    Solution : wipe_loc should be called on local root_loc.
    
    Change-Id: I9cc5ee3b1bd9f352f2362a6d997b7b09051c0f68
    BUG: 1260848
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/12123
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 116430b5e44457bba515a83be26b4b2256c75c38
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Oct 19 09:04:07 2015 -0400

    cluster/tier remove suprious log messages on valid failed migration
    
    On a write to a replica volume, we record in all brick's databases an entry.
    When the tier daemon runs, it will only move the file if it is the true
    owner of the file as defined by the XATTR_NODE_UUID_KEY.
    
    Change-Id: Ib82717f87a3f94f3d0d9f969773de9e88d6aaf22
    BUG: 1273043
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12391
    Reviewed-by: Joseph Fernandes
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 17e00a6787584cfad39aac0cff4dba580da885e6
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Oct 16 14:16:32 2015 -0400

    cluster/tier update man pages for tier feature
    
    Add to gluster man pages instructions for tier commands.
    
    Change-Id: I0918460eeaba22bb6a11238d4f5501fa8e61da88
    BUG: 1272557
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12380
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit 0243085e40d842c59f4d7d59c61701ba416878ec
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Oct 13 17:11:29 2015 +0530

    cluster/tier: Changed tier xattr-name value
    
    Each tier layer (for future stacking implementations)
    must have a unique xattr name. We are currently using
    the name of the tier subvolume excluding the volume name.
    
    Change-Id: Id4adea61dc1c8473fb1d4d7364d1940278c6e129
    BUG: 1259298
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12350
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 0f31ab1ba9bb7dbc47bfa68cbce81ec104d04ac4
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Oct 13 23:25:59 2015 +0530

    cluster/ec : Remove index entries if file/dir does not exist
    
    Problem: During write and rebalance if a brick is down, index
    entries will be created. If the same file gets migrated to
    other subvol by rebalance process, these index entries will
    remain in index directory. During heal, these indices should
    be removed when we get ENOENT or ESTALE for a index.
    
    Solution: Capture correct errno and take appropriate action
    to purge these indices.
    
    Change-Id: I1aad8b99e4df2e139648e3bf971e4cb1c4b38699
    Bug: 1271358
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/12353
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0c02fefaf7d6b54f4d9cae2b1ae1f2b657857625
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Sep 28 16:47:01 2015 +0530

    protocol/server: define the max number of inodes in lru list as a number
    
    * The max number of inodes in the lru list of the inode table was being defined
      in terms of memory units (GF_UNIT_MB) instead of number. And the description
      of the option was also referring to it in memory units instead of number.
    
    Change-Id: I48f07e7d2826406697eb2a13714ab22feae81d89
    BUG: 1266883
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/12242
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bd71446b25aefe066ca18a28d73d777774ab7f87
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Oct 13 15:02:00 2015 +0530

    cluster/dht : Do not migrate files with POSIX locks held
    
    dht_migrate_file does not migrate file locks to the dst file.
    Any locks held on the source file are lost once the migration
    is complete. This issue is magnified in the case of a tier volume
    as file migrations occur more frequently and repeatedly as compared
    to a DHT rebalance.
    
    The fix makes 2 changes:
    1. Before starting the actual migration process, check if there are
     any locks held on the file. If yes, do not migrate the file.
    2. The rebalance process tries to lock on the entire file just before
     moving into the Phase 2 of the file migration. If the lock acquisition
    fails, the file migration does not proceed.
    If the lock is granted, the file migration proceeds.
    
    This still leaves a small window where conflicting locks can be granted to
    different clients. If client1 requests a lock on the src file just after
    it is converted to a linkto file and client2 requests a lock on the dst
    data file, they will both be granted, but all FOPs will be redirected
    to the dst data file. This issue will be taken up in a subsequent patch.
    
    Change-Id: I8c895fc3cced50dd2894259d40a827c7b43d58ac
    BUG: 1271148
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12347
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 816ca94f5dd49f34f395caf501de3c71f0ba113d
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Tue Oct 13 14:40:55 2015 +0530

    libglusterfs: pass buffer size to gf_store_read_and_tokenize function
    
    Previously if user set an option where length of key=value goes beyond
    PATH_MAX (4096) character then tokenzing the option at the time of
    reading configuration file will fail.
    This is because of the we was having restraction in fgets to read maximum
    of PATH_MAX (4096) length of character.
    Consequence of this is when user try to restart glusterd, after setting
    key=value length beyond PATH_MAX (4096) character, glusterd will not restart.
    
    With this fix instead of PATH_MAX, consumer of gf_store_read_and_tokenize
    function will decide the size of the buffer length.
    
    Change-Id: I655a8ce982effdfff8f3e785ea31f543dbe39301
    BUG: 1271150
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12346
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 00eeb153f4ea473c6636147f6c72c04336128198
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Oct 13 14:28:03 2015 +0530

    cli/quota : rm -rf on /<mountpoint>/<dir> is not showing quota header
    
    Currently, when 'gluster v quota <VOLNAME> list' command is issued
    after an rm -rf on /run/gluster/vol/<directory>, quota output header is
    not shown. It is because the list_count was properly calculated with
    'gluster v quota <VOLNAME> remove /path' and not with an rm -rf. The patch
    fixes this issue.
    
    Change-Id: I5266a8b0b9322b7db1b9e1d6b0327065931f4bcb
    BUG: 1269375
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12345
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a2976a2eb8c79cbec1009bec4c420b4874da25bc
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Oct 12 15:03:28 2015 +0530

    cli : freeing the allocated memory
    
    Change-Id: Ibcbad94c091a9c24fe5aff2d7e8bcd9ac88da7bf
    BUG: 1248521
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12337
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit f88d0ade1c09aa1a3cee3713dc851da9552d7ff5
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Thu Sep 24 18:04:23 2015 +0530

    glusterd: disabling enable-shared-storage option should not delete volume
    
    Previously when you create volume with "glusterd_shared_storage" name
    and if user disable enable-shared-storage option then gluster will
    delete the "glusterd_shared_storage" volume.
    
    With this fix gluster will do appropriate validation of
    enable-shared-storage option and it will not delete volume with
    "glusterd_shared_storage" name if it is a user created volume.
    
    Change-Id: I2bd92f938fb3de6ef496a934933bdcea9f251491
    BUG: 1266818
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12232
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fc8df80f157c148cf60500be14c1f6a9aeed8d7b
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Oct 12 17:22:20 2015 +0530

    tier/shd: inline warning when compiled with gcc v.5
    
    Change-Id: I487a26263d6e940eed364a831e99f9b8390bc96a
    BUG: 1226881
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12342
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Tested-by: Anoop C S <anoopcs@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 041d31e90b6000643e8c06a6d82520e3f2cc3b9a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jul 29 14:27:07 2015 +0530

    features/shard: Return ENOTSUP as opposed to ENOTCONN in unimplemented fops
    
    Change-Id: Idba1070b11c5c1de26ef57e6843c93c105b8b8a5
    BUG: 1270694
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12340
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit aa71df19383ac15306374ea4992dd59e20f5a9c5
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Oct 12 13:12:46 2015 +0530

    features/shard: Dump private members and addresses in statedump
    
    Change-Id: I3c5e5bd93288c4c9a2665a26c0d6a76e67ecf914
    BUG: 1270694
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12334
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 79c5a715f9bab49f48876ab4f4bc79d211c0d7f1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Sep 16 16:35:19 2015 +0530

    protocol/client: give preference to loc->gfid over inode->gfid
    
    There are xlators which perform fops even before inode gets linked. Because of
    this loc.gfid is preferred at the time of inodelk/entrylk but by the time
    unlock can happen, inode could be linked with a different gfid than the one in
    loc.gfid (because of the way dht was giving preference) Due to this unlock goes
    on a different inode than the one we sent inodelk on, which leads to hang.
    
    Credits to Pranith for the fix.
    
    Change-Id: I7d162d44852ba876f35aa1bb83e4afdb184d85b9
    BUG: 1266834
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12233
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0ef62933649392051e73fe01c028e41baddec489
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Sep 8 13:04:45 2015 +0530

    tier/shd: make shd commands compatible with tiering
    
    tiering volfiles may contain afr and disperse together
    or multiple time based on configuration. And the
    informations for those configurations are stored in
    tier_info. So most of the volgen code generation
    need to be changed to make compatible with it.
    
    Change-Id: I563d1ca6f281f59090ebd470b7fda1cc4b1b7e1d
    BUG: 1261276
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12135
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d4bd690adae7ce69594c3322d0d7a8e3cb4f7303
Author: vmallika <vmallika@redhat.com>
Date:   Wed Oct 7 15:24:46 2015 +0530

    quota/marker: dir_count accounting is not atomic
    
    Consider below scenario:
    
    Quota enabled on pre-existing data
    Now quota-crawl process will start healing xattrs
    Now if write is performed where healing is not complete, there is a
    possibility that 'update txn' is started before 'create xattr txn', in
    this case dir count can be missed on a dir where quota size xattr is not
    yet created.
    
    Solution is to get size xattr and if xattr is missing, add 1 for
    dir_count, this requires one additional fop if done in marker during
    each update iteration
    Better solution is to us xattrop GF_XATTROP_ADD_ARRAY64_WITH_DEFAULT
    
    Change-Id: Idc8978860a3914e70c98f96effeff52e9a24e6ba
    BUG: 1243798
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11694
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit fdff192b918ca9cd237f3f784c627102377e3661
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Aug 20 12:19:51 2015 +0530

    tier/shd: create shd volfile for tiering
    
    Currently shd graph will only start if it is replicate
    or disperse volume. But in case of tiering, volume type
    will be tier. So we need to start shd if any of the cold
    or hot is compatible with shd volume.
    
    Change-Id: Ic689746ac7d2fc6a9eccdabd8518dc9139829de2
    BUG: 1261276
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11962
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f6618acd4f7642dab19445e35cf2c7fbc8244a5e
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Aug 4 20:38:06 2015 +0530

    tier/ctr: CTR DB named lookup heal of cold tier during attach tier
    
    Heal hardlink in the db for already existing data in the cold
    tier during attach tier. i.e during fix layout do lookup to files
    in the cold tier.
    
    CTR xlator on the  brick/server side does db update/insert of the hardlink on a namelookup.
    Currently the namedlookup is done synchronous to the fixlayout that is
    triggered by attach tier. This is not performant, adding more time to
    fixlayout. The performant approach is record the hardlinks on a compressed
    datastore and then do the namelookup asynchronously later, giving the ctr db
    eventual consistency
    
    Change-Id: I4ffc337fffe7d447804786851a9183a51b5044a9
    BUG: 1252586
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/11828
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 672baab88fb7f32e844cd4be22e0924e4e0e83fc
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Sep 18 00:49:06 2015 -0400

    cluster/tier: add watermarks and policy driver
    
    This fix introduces infrastructure to support different
    policies for promotion and demotion.
    
    Currently the tier feature automatically promotes and demotes
    files periodically based on access. This is good for testing
    but too stringent for most real workloads. It makes it
    difficult to fully utilize a hot tier- data will be demoted
    before it is touched- its unlikely a 100GB hot SSD will have
    all its data touched in a window of time.
    
    A new parameter "mode" allows the user to pick promotion/demotion
    polcies.
    
    The "test mode" will be used for *.t and other general testing.
    This is the current mechanism.
    
    The "cache mode" introduces watermarks. The watermarks
    represent levels of data residing on the hot tier.
    
    "cache mode" policy:
    
    The % the hot tier is full is called P.
    
    Do not promote or demote more than D MB or F files.
    
    A random number [0-100] is called R.
    
    Rules for migration:
    
    if (P < watermark_low) don't demote, always promote.
    
    if (P >= watermark_low) && (P < watermark_hi) demote if R < P; promote if R > P.
    
    if (P > watermark_hi) always demote, don't promote.
    
    gluster volume set {vol} cluster.watermark-hi %
    gluster volume set {vol} cluster.watermark-low %
    gluster volume set {vol} cluster.tier-max-mb {D}
    gluster volume set {vol} cluster.tier-max-files {F}
    gluster volume set {vol} cluster.tier-mode {test|cache}
    
    Change-Id: I157f19667ec95aa1d53406041c1e3b073be127c2
    BUG: 1257911
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12039
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit a4f982be9b21323038704069a56fb2448369d6a0
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Sep 24 14:53:52 2015 +0530

    Porting developer guide to source code repo from glusterdocs project
    
    Change-Id: Ib8d9c668ebb05863918e6ec2b89908f206626f38
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/12227
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Raghavendra Talur <rtalur@redhat.com>

commit bad9539437ca1d69e470159277bbb6b5675cbae3
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Oct 9 12:18:03 2015 -0400

    cluster/tier: fix transpoint endpoint not connected in tier.t (rare)
    
    The script did not cleanly unmount/mount gluster and change the current
    working directory when stopping and starting the volume. Most of the
    time this problem would self-resolve before subsequent tests, but
    very occasionally races would lead to the errors/failures.
    
    Change-Id: I128b913a71e2745512ee81c3d71852311e3b4a1b
    BUG: 1270328
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12327
    Reviewed-by: Joseph Fernandes
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 069661f8497bbe459cb0a195f115d84c2ebd37aa
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 7 18:39:42 2015 +0530

    glusterfsd: Initialize ctx, cmd_args
    
    Change-Id: I9c71ae264665b7bba609c7f86cf42a52a6b47260
    BUG: 1269696
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12311
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fe3c6f0fa2bf8590f4c540fd9561aeeec1243361
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 8 16:23:36 2015 +0530

    cluster/ec: Implement gfid-hash read-policy
    
    Add a policy in ec to performs reads from same bricks as long as they
    are good. Based on the gfid of the file/directory it determines the
    bricks to be considered for reading.
    
    Change-Id: Ic97b5c54c086a28b5e07a330a4fd448551b49376
    BUG: 1261260
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12133
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 47d8d2fc9c88c95dfcae2c5c06e6eb3b1ce03a92
Author: Milind Changire <mchangir@redhat.com>
Date:   Tue Sep 22 18:30:22 2015 +0530

    gfapi: xattr key length check to avoid brick crash
    
    Added check to test if xattr key length > max allowed for OS
    distribution and return:
    EINVAL if xattr name pointer is NULL or 0 length
    ENAMETOOLONG if xattr name length > max allowed for distribution
    
    Typically the VFS does this in the kernel for us.  But since we are
    bypassing the VFS by providing the libgfapi to talk directly to the
    brick process, we need to add such checks.
    
    Change-Id: I610a8440871200ae4640351902b752777a3ec0c2
    BUG: 1263056
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/12207
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 62851271df97c584b43a7b2458d6bccc97dee029
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 29 15:13:37 2015 +0530

    features/shard: Regulate memory consumption by individual shards' inode_t objects
    
    Shard translator will now maintain an lru list of inodes associated with
    individual shards of constant size, and will make sure that at no point the
    number of these inodes will exceed the configured limit.
    This is to keep the memory consumption by the thousands of shards of every large
    file from exploding.
    
    Change-Id: I5e60eea5dcf3130257fb431ca70cfaba53cae7f3
    BUG: 1252263
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12254
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 4ad9bc5faca60528345f1e9c95c22bd8402162c0
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Sep 7 14:46:33 2015 +0530

    tiering/glusterd: keep afr/ec xlators name constant
    
    afr uses the translator name for locking purpose,
    so it is mandatory to keep afr/ec xlators name constant
    across graph change
    
    currently when a tier is attached, afr names are appended
    either with hot or cold. ie that breaks the above
    mentioned constraint.
    
    Change-Id: I3699dcdaa8190bab3ba81cbc01e8fa126d37ba0d
    BUG: 1261276
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12134
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit f6714230e8335f7508fa871dcd9d8af708f15347
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Sep 23 05:01:47 2015 -0400

    feature/quota: Make message-id for quota start from 120000
    
    Change-Id: I2076fcab51f4ecc529dffd89ca6ee9eb99d80f09
    BUG: 1265531
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12218
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9a020d144595ec84a456b929d1d99616013fe5ce
Author: vmallika <vmallika@redhat.com>
Date:   Thu Oct 8 12:37:42 2015 +0530

    quota: fix crash in quota_fallocate
    
    list head was not initialized and brick
    was crashing with fallocate.
    
    This patch fixes the issue
    
    Change-Id: I9757b88eab61054892f0fe3de63af2683cd4fef7
    BUG: 1269754
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12314
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 58d1a9be562630bd1ed8af3e496ca05e087adece
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Fri Sep 18 19:57:54 2015 +0530

    tier/ctr: Solution for db locks for tier migrator and ctr using sqlite version less than 3.7 i.e rhel 6.7
    
    Problem: On RHEL 6.7, we have sqlite version 3.6.2 which doesnt support
    WAL journaling mode, as this journaling mode is only available in sqlite 3.7 and above.
    As a result we cannot have to progreses concurrently accessing sqlite, without
    running into db locks! Well WAL is also need for performace on CTR side.
    
    Solution: This solution is to use CTR db connection for doing queries when WAL mode is
    absent. i,e tier migrator will send sync_op ipc calls to CTR, which in turn will
    do the query and create/update the query file suggested by tier migrator.
    
    Pending: Well this solution will stop the db locks but the performance is still an issue for CTR.
    We are developing an in-Memory Transaction Log (iMeTaL) which will help boost the CTR
    performance by doing in memory udpates on the IO path and later flush the updates to
    the db in a batch/segment flush.
    
    Change-Id: Ie3149643ded159234b5cc6aa6cf93b9022c2f124
    BUG: 1240577
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12191
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Luis Pabon <lpabon@redhat.com>

commit 81d4aa18b3a1cdad0e0e8df43fe4c8c141c06618
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Oct 5 16:17:02 2015 +0530

    gluster v status --xml for a replicated hot tier volume
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volStatus>
        <volumes>
          <volume>
            <volName>tiervol</volName>
            <nodeCount>11</nodeCount>
            <hotBricks>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/b5_2</path>
                <peerid>149ac603-8078-41c5-8f71-7373f2a3016f</peerid>
                <status>1</status>
                <port>49164</port>
                <ports>
                  <tcp>49164</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>8684</pid>
              </node>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/b5_1</path>
                <peerid>149ac603-8078-41c5-8f71-7373f2a3016f</peerid>
                <status>1</status>
                <port>49163</port>
                <ports>
                  <tcp>49163</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>8687</pid>
              </node>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/b4_2</path>
                <peerid>149ac603-8078-41c5-8f71-7373f2a3016f</peerid>
                <status>1</status>
                <port>49162</port>
                <ports>
                  <tcp>49162</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>8699</pid>
              </node>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/b4_1</path>
                <peerid>149ac603-8078-41c5-8f71-7373f2a3016f</peerid>
                <status>1</status>
                <port>49161</port>
                <ports>
                  <tcp>49161</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>8708</pid>
              </node>
            </hotBricks>
            <coldBricks>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/b1_1</path>
                <peerid>149ac603-8078-41c5-8f71-7373f2a3016f</peerid>
                <status>1</status>
                <port>49155</port>
                <ports>
                  <tcp>49155</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>8716</pid>
              </node>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/b1_2</path>
                <peerid>149ac603-8078-41c5-8f71-7373f2a3016f</peerid>
                <status>1</status>
                <port>49156</port>
                <ports>
                  <tcp>49156</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>8724</pid>
              </node>
              <node>
                <hostname>NFS Server</hostname>
                <path>localhost</path>
                <peerid>149ac603-8078-41c5-8f71-7373f2a3016f</peerid>
                <status>1</status>
                <port>2049</port>
                <ports>
                  <tcp>2049</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>8678</pid>
              </node>
            </coldBricks>
            <tasks>
              <task>
                <type>Tier migration</type>
                <id>975bfcfa-077c-4edb-beba-409c2013f637</id>
                <status>1</status>
                <statusStr>in progress</statusStr>
              </task>
            </tasks>
          </volume>
        </volumes>
      </volStatus>
    </cliOutput>
    Change-Id: I69252a36b6e6b2f3cbe5db06e9a716f504a1dba4
    BUG: 1268810
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12302
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit d0edb6d555d687f76837515207b9408be0bdd55e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Oct 5 21:36:14 2015 +0530

    fuse: resolve complete path after a graph switch
    
    If a graph switch has happended as part of a attach-tier,
    then there is a chance to hash fops to newly added brick
    before fix-layout. This causes on going i/o to fail.
    
    This patch will resolve a path, for graph switch by sending
    recursive lookup to the parent directories. Those lookups
    will help to heal the directory.
    
    Change-Id: Ia2bb4b43a21e5cc6875ba1205628744c3f0ce4e5
    BUG: 1263549
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12184
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 722ed512220395af8a707756b49df67afacda795
Author: Richard Wareing <rwareing@fb.com>
Date:   Wed Feb 12 18:37:55 2014 -0800

    xlators: add JSON FOP statistics dumps every N seconds
    
    Summary:
    - Adds a thread to the io-stats translator which dumps out statistics
      every N seconds where N is configurable by an option called
      "diagnostics.stats-dump-interval"
    - Thread cleanly starts/stops when translator is unloaded
    - Updates macros to use "Atomic Builtins" (e.g. intel CPU extentions) to
      use memory barries to update counters vs using locks.  This should
      reduce overhead and prevent any deadlock bugs due to lock contention.
    
    Test Plan:
    - Test on development machine
    - Run prove -v tests/basic/stats-dump.t
    
    Change-Id: If071239d8fdc185e4e8fd527363cc042447a245d
    BUG: 1266476
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/12209
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit ebe40c5047e7501a5bd1747cb4d62277ae0db6e9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 7 17:43:33 2015 +0530

    cluster/afr: Handle stack reset failures
    
    When all the bricks go down in the middle of the self-heal, in AFR_STACK_RESET
    afr_local_init will fail because all the bricks are down. So local will remain
    NULL for the frame. This leads to crashes as this failure is not handled in
    both entry and data self-heals.
    
    Change-Id: I71a02f161f2c4dbfdc8bb7f2a6f32807191ed253
    BUG: 1269470
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12309
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ee944e86866a6556fd4dd98bcd6f1f58c323721f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Oct 6 13:05:57 2015 +0530

    glusterd/add-brick: change add-brick implementation to v3 framework
    
    add-brick commit first happens on local node and followed by peers.
    As part of the commit of local-host glusterd will send the updated
    volfiles to the clients connected to the local-host even before the
    commit of peers happen. If any of the newly added brick was hosted
    by any peer, that brick won't be started when client (connected to
    local-host) try to send fops.
    
    By changing to v3 framework we can send post validate ops
    after commit operation that helps to send volfile fetch request only
    after completing commits on all nodes.
    
    Change-Id: Ib7312e01143326128c010c11fc2ed206f37409ad
    BUG: 1263549
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12237
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit ff5ea98c6c0ffb7398562b418e8e9c422f08691d
Author: vmallika <vmallika@redhat.com>
Date:   Tue Oct 6 18:16:49 2015 +0530

    quota: use copy_frame when creating new frame during quota_check_limit
    
    DHT re-balance, sets frame root PID < 0 and quota_check_limit skips
    enforcement if this PID is less than 0.
    
    When creating new frame for quota_check_limit we need to use
    copy_frame instead of create_frame, so that all auth information
    are copied from original frame.
    
    Change-Id: Ib3b4a3744f8b0d72a8bc32826f6edae836d6faed
    BUG: 1267812
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12265
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b7d2dba8b655f174f810ba0aa9a4770e5cfaa609
Author: hari gowtham <hgowtham@redhat.com>
Date:   Mon Oct 5 17:13:44 2015 +0530

    Tier/cli: number of bricks remains the same in v info --xml
    
    The number of bricks count remains one for the cold type.
    
    Actual result:
    <numberOfBricks>1 x 2 = 2</numberOfBricks>
    
    Expected result:
    <numberOfBricks>3 x 2 = 6</numberOfBricks>
    
    Change-Id: I31480a7808b248ef9ea805cb64f7663d44647ddf
    BUG: 1268822
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12303
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 229b4d8391b5abf8da662d02d9a5ccab37eb6ab5
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Oct 1 04:06:43 2015 -0400

    dht/rebalance: fix layout and dict leaks
    
    Change-Id: Ib3911dfa1f950ff9decbe249ad798e97226dd06d
    BUG: 1266877
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12295
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 84e9a590df0d4ecf6e4b37118bdaf09db9d2740d
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Sun Aug 30 21:24:32 2015 +0530

    cluster/ec : Mark new entry changelog in entry self-heal
    
    Problem :
    When a new entry is created dirty mark xattrs are not
    created this will need full heal to be performed, even
    when there are partial failures.
    
    Solution :
    Marks new entry changelog in self-heal.
    
    PS: Also fixed erasing of dirty markers when no data heal
    is required.
    
    BUG: 1254121
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Change-Id: I156e3d3201afa77efe118e1aaace1d91c90a9613
    Reviewed-on: http://review.gluster.org/11938
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 032ca47a4356a68522f5366a341d78b01ca9864c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Oct 5 15:30:03 2015 +0530

    features/shard: Use the xattr rsp dict to pick shard xattrs in xattrop cbk
    
    The change http://review.gluster.org/#/c/11938/ makes a fix in posix translator
    which would cause sharding to fail fops post xattrop without this patch.
    
    Change-Id: If096965b319f393608b0f763402b9b90acb61492
    BUG: 1268796
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12300
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c62dcfff26082b4c2d23e89f905bd85f865211db
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Oct 5 12:59:18 2015 +0530

    tier/cli : throw a warning when user issues a detach-tier commit/force
               command
    
    Change-Id: Idf7664d509156ce46ef4308ffc07fb556a0aedd2
    BUG: 1268755
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12297
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit e94e1f2b8ae2328da10161f6421ea5c9b1d7277e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Oct 5 14:55:59 2015 +0530

    tests: Move tests/bugs/shard/bug-1245547.t to bad tests list
    
    Change-Id: I389f88cefdeee87b99dcacbac48d2dcc70a97979
    BUG: 1268796
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12299
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 5fb6465f9f1ca9074d2cf4167870661d82d4ecb1
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Oct 5 12:54:34 2015 +0530

    tests: Adding bug-1221481-allow-fops-on-dir-split-brain.t to bad test
    
    Adding bug-1221481-allow-fops-on-dir-split-brain.t to bad test as it
    is failing spuriously. Will be removed after the failure is
    root caused and fixed.
    
    Change-Id: I26b634f01dfa2c60eed21a1286aa83ecaa75fa26
    BUG: 1268790
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12298
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 84e90b756566bc211535a8627ed16d4231110ade
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Fri Aug 21 00:08:23 2015 +0530

    server/protocol: option for dynamic authorization of client permissions
    
    problem:
    assuming gluster volume is already mounted (for gfapi: say client transport
    connection has already established), now if somebody change the volume
    permissions say *.allow | *.reject for a client, gluster should allow/terminate
    the client connection based on the fresh set of volume options immediately,
    but in existing scenario neither we have any option to set this behaviour nor
    we take any action until and unless we remount the volume manually
    
    solution:
    Introduce 'dynamic-auth' option (default: on).
    If 'dynamic-auth' is 'on' gluster will perform dynamic authentication to
    allow/terminate client transport connection immediately in response to
    *.allow | *.reject volume set options, thus if volume permissions have changed
    for a particular client (say client is added to auth.reject list), his
    transport connection to gluster volume will be terminated immediately.
    
    Change-Id: I6243a6db41bf1e0babbf050a8e4f8620732e00d8
    BUG: 1245380
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/12229
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit fc33ed37ffddee9ac90b947a038ab3a93fbcab50
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Sep 10 12:40:17 2015 +0000

    rpc: Remove unused function
    
    Change-Id: I0b96b83ad8d06de9b2f5fc14073b94777885a775
    BUG: 1261927
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/12153
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ba150681993b9d69b65976eca806bae2807dfcb3
Author: Sakshi <sabansal@redhat.com>
Date:   Wed Sep 23 15:16:34 2015 +0530

    glusterd: validate function for replica volume options
    
    Change-Id: I5b4a28db101e9f7e07f4b388c7a2594051c9e8dd
    BUG: 1265479
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/12215
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 7e396d836de8a411213eefc6024a33d89bc560d0
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Sep 30 16:41:19 2015 +0530

    cli/tier : fixes cli crash when user tries "gluster v tier" command
    
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    
    Change-Id: I919d8935c849f9be6b2cb43e8332afb821778d89
    BUG: 1267539
    Reviewed-on: http://review.gluster.org/12258
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 2b963bc22533cacbfc833cf64dd9bfef138db5ee
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Sep 28 02:22:07 2015 -0400

    dht/rebalance: fix mem-leak in migration code path
    
    Change-Id: I37faf983fc02996541f3d96a17cb2a2c2cdb6781
    BUG: 1266877
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12235
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 801b7bd50a51c66e327ad79cdfc131654e069cdc
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Sep 28 13:09:38 2015 +0530

    storage/posix: Reduce number of getxattrs for internal xattrs
    
    Most of the gluster internal xattrs don't exceed 256 bytes. So try
    getxattr with ~256 bytes. If it gives ERANGE then go the old way
    of getxattr with NULL 'buf' to find the length and then getxattr with
    allocated 'buf' to fill the data. This way we reduce lot of getxattrs.
    
    Change-Id: I716d484bc9ba67a81d0cedb5ee3e72a5ba661f6d
    BUG: 1265893
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12240
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 059db0254f5670a34f1a928155c0c7d1cd03b53a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Sep 23 18:56:01 2015 +0530

    glusterd, dht: volume set for use-readdirp in dht
    
    Change-Id: Icab246b1d02808864d878d949fa56f9f889b538a
    BUG: 1265677
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12221
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a0514409356c35cd90a0506ab9fafa7462b21bef
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Sep 9 13:03:37 2015 +0530

    quota : xml output modified to give exact available space in bytes
    
    Currrently, 'gluster v quota <VOLNAME> list' command rounds off the
    available space and shows it to the user. Now, 'gluster v quota
    <VOLNAME> list --xml' command is modified to show the exact available
    space in bytes.
    
    Change-Id: I3772e036a2537c1df12f22cf32dfe4ac7940988f
    BUG: 1261404
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12137
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 7f0bb9ca8281d022e37e1567ae24ce08436d4cd8
Author: vmallika <vmallika@redhat.com>
Date:   Tue Sep 29 15:27:47 2015 +0530

    quota/marker: marker code cleanup
    
    marker is re-factored with syncop approach,
    remove unused old code
    
    Change-Id: I36e670e63b6c166db5e64d3149d2978981e2f7c2
    BUG: 1240581
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11560
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 51a23f4d0ac38982fcde86000819f64a42d39462
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Sep 29 12:31:22 2015 +0530

    tests: Move georep-basic-dr-tarssh.t to bad tests
    
    Geo-rep tests are failing spuriously in few
    regression machines. Hence moving it to bad
    till the issue is root caused and fixed.
    
    Change-Id: I25feb8d9c51e03aa9ac0fe70291dc9e54ad043f9
    BUG: 1227624
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12248
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 28e801cc7776cab357d5e27bc872b2e35e38c134
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Sep 22 15:44:30 2015 -0400

    cluster/tier re-enable tier.t in automatic tests
    
    Re-enable tier.t in automatic tests. Disable check
    for BSD until recurring problem with SQLlite on it is understood.
    
    Change-Id: Ib13b269ab841a59a0a41d8478c8627b180b16c61
    BUG: 1231268
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12208
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ccea4c9d575c4cf46ac93575a1c62be90af5372b
Author: hari gowtham <hgowtham@redhat.com>
Date:   Thu Sep 10 20:15:35 2015 +0530

    Tier/cli: tier related information in volume info xml
    
    gluster v info didnt differentiate the hot bricks and cold bricks
    and other few values
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volInfo>
        <volumes>
          <volume>
            <name>rmbr</name>
            <id>72d223fc-96ba-4f4a-ac6e-0d0bc16ef127</id>
            <status>1</status>
            <statusStr>Started</statusStr>
            <brickCount>3</brickCount>
            <distCount>1</distCount>
            <stripeCount>1</stripeCount>
            <replicaCount>1</replicaCount>
            <disperseCount>0</disperseCount>
            <redundancyCount>0</redundancyCount>
            <type>5</type>
            <typeStr>Tier</typeStr>
            <transport>0</transport>
            <xlators/>
            <bricks>
              <hotBricks>
                <hotBrickType>Distribute</hotBrickType>
                <numberOfBricks>1</numberOfBricks>
                <brick uuid="81">v1:/hb1<name>v1:/hb1</name><hostUuid>81</hostUuid></brick>
              </hotBricks>
              <coldBricks>
                <coldBrickType>Distribute</coldBrickType>
                <numberOfBricks>2</numberOfBricks>
                <brick uuid="81">v1:/br1<name>v1:/br1</name><hostUuid>81</hostUuid></brick>
                <brick uuid="81">v1:/br2<name>v1:/br2</name><hostUuid>81</hostUuid></brick>
                <count>0</count>
              </coldBricks>
            </bricks>
          </volume>
        </volumes>
      </volInfo>
    </cliOutput>
    
    Change-Id: I6e52541bb6d8a6a17e17bfcb42434beaac13db56
    BUG: 1261837
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12158
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 5be6f0339b5ad189868a50b837ae7b8c164a5b25
Author: Anoop C S <anoopcs@redhat.com>
Date:   Sat Sep 12 19:48:06 2015 +0530

    protocol/client: Remove dead code from client_rpc_notify
    
    Normally GF_EVENT_CHILD_UP is dispatched after client
    handshake. But we have some dead code in client_rpc_notify
    which is assumed to do the same on receiving RPC_CLNT_CONNECT.
    This dispatch is based on a condition whether "disable-handshake"
    is enabled or not. Since we require client-handshake everytime
    we have a connect this check for "disable-handshake" is invalid
    and no longer required. Moreover this option is never handled
    in any of the translators.
    
    Change-Id: Ic862d6ac08cd3b18cf231f50140cd00e84e52ca0
    BUG: 1227667
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/12170
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 007bfd963240d7cf80b4f1b5f652cf142bcadb65
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Sep 7 14:29:15 2015 +0530

    gfapi: transport and port are optional for glfs_set_volfile_server
    
    Only server is the required argument for glfs_set_volfile_server
    and both transport and port are optional. When glfs_set_volfile_server
    is invocated multiple times, only on the first invocation we replace
    port 0 with 24007 and transport NULL with "tcp".
    
    Hence, replacing the parameters at the entry function is the right way.
    
    Change-Id: If9f4a5f7fd9038eed140e2f47167a8fd11acc2f6
    BUG: 1260561
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/12114
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ecfa2edd7816abbf8fbbe43c308ddf895849e8e6
Author: vmallika <vmallika@redhat.com>
Date:   Tue Sep 22 12:17:50 2015 +0530

    posix: xattrop 'GF_XATTROP_ADD_ARRAY_WITH_DEFAULT' implementation
    
    Implementation of xattrop type:
    GF_XATTROP_ADD_ARRAY_WITH_DEFAULT
    GF_XATTROP_ADD_ARRAY64_WITH_DEFAULT
    
    These operations are similar to 'GF_XATTROP_ADD_ARRAY',
    except that it adds a default value if xattr is missing
    or its value is zero on disk.
    
    One use-case of this operation is in inode-quota.
    When a new directory is created, its default dir_count
    should be set to 1. So when a xattrop performed setting
    inode-xattrs, it should account initial dir_count
    1 if the xattrs are not present
    
    Here is the usage of this operation
    
    value required in xdata for each key
    struct array {
        int32_t   newvalue_1;
        int32_t   newvalue_2;
        ...
        int32_t   newvalue_n;
        int32_t   default_1;
        int32_t   default_2;
        ...
        int32_t   default_n;
    };
    
    or
    
    struct array {
        int32_t   value_1;
        int32_t   value_2;
        ...
        int32_t   value_n;
    } data[2];
    fill data[0] with new value to add
    fill data[1] with default value
    
    xattrop GF_XATTROP_ADD_ARRAY_WITH_DEFAULT
    for i from 1 to n
    {
        if (xattr (dest_i) is zero or not set in the disk)
            dest_i = newvalue_i + default_i
        else
            dest_i = dest_i + newvalue_i
    }
    
    value in xdata after xattrop is successful
    struct array {
        int32_t   dest_1;
        int32_t   dest_2;
        ...
        int32_t   dest_n;
    };
    
    Change-Id: Ic6a08473e99fd98299a839d4d8416081a7534efd
    BUG: 1243946
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11702
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 7f33579e8a42eb19e92559a6c3acaeb92b6bb184
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Sep 23 21:41:55 2015 +0530

    storage/posix: Prevent extra handle-path
    
    In readdirp_fill we already have the path of the file/directory.
    No need to construct handle-path again. This saves two lstats and
    at least two readlink calls per directory.
    
    Change-Id: I8d1b2afeda3e053265a243d4e9a101192f5f509e
    BUG: 1265893
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/12222
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 0428a0acf7cfeef6a92065eeca2b8904b0f8a132
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Sep 21 16:57:07 2015 +0530

    features/shard: Port log messages to new framework
    
    Change-Id: Iac01e6a89a0d0c37a12a5e47f17f7ced85a31590
    BUG: 1265516
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12217
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1d82db506d1cd5b20d14820d89033de2e4a14210
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jul 31 14:11:15 2015 -0400

    build: export minimum symbols from xlators for correct resolution
    
    We've been lucky that we haven't had any symbol collisions until now.
    Now we have a collision between the snapview-client's svc_lookup() and
    libntirpc's svc_lookup() with nfs-ganesha's FSAL_GLUSTER and libgfapi.
    
    As a short term solution all the snapview-client's FOP methods were
    changed to static scope. See http://review.gluster.org/11805. This
    works in snapview-client because all the FOP methods are defined in
    a single source file. This solution doesn't work for other xlators
    with FOP methods defined in multiple source files.
    
    To address this we link with libtool's '-export-symbols $symbol-file'
    (a wrapper around `ld --version-script ...` --- on linux anyway) and
    only export the minimum required symbols from the xlator sharedlib.
    
    N.B. the libtool man page says that the symbol file should be named
    foo.sym, thus the rename of *.exports to *.sym. While foo.exports
    worked, we will follow the documentation.
    
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    BUG: 1248669
    Change-Id: I1de68b3e3be58ae690d8bfb2168bfc019983627c
    Reviewed-on: http://review.gluster.org/11814
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 84367f0c9106f5a604ac05a02898d4521fa5c832
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Sep 11 14:25:14 2015 +0530

    extras/hookscripts : introducing additional check in S31ganesha-start.sh
    
    New export file with default configuration will be created for a volume
    when it is started again. This patch will create new export file only
    when it is not present. This change is required for scenarios such as
    snapshot restore , node reboot etc.
    
    Change-Id: I34123911f176dcb29d5c016aa097af3a3b2c727b
    BUG: 1261444
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12159
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 98fe4297131361d62d6579d0bde10a8485e4748a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Sep 23 08:27:25 2015 +0530

    heal: remove glfsh_print_brick()
    
    Use glfsh_print_brick_from_xl() instead so that the hostname:brickpath
    displayed when heal info is run is consistent with other gluster cli
    commands like `gluster volume info`.
    
    Change-Id: I30ee3d76d0f68991a25bd678d40ec3bf7e0538c7
    BUG: 1265470
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12212
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>

commit 6838a5b342b40099d09ccdce6af8c6f769cccf39
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 8 18:08:20 2015 +0530

    features/shard: Performance improvements in IO path - Part 2
    
    This is change 2/2 of the performance improvements for sharding.
    
    The changes are with respect to maintaining up-to-date values of
    file attributes in [f]stat, [f]setattr, link, and [f]truncate
    codepaths.
    
    Change-Id: Ia3ce4664fb33be869e4dc76494adbe9c314cc098
    BUG: 1258905
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12138
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 5ad1add883ee54f83a42f0f6d6ae2c6e3f9a543a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Sep 7 14:57:24 2015 +0530

    features/shard: Performance improvements in IO path
    
    This is patch 1/2 of the performance improvement work
    for sharding in the IO path.
    What this patch does:
    Since the primary use-case where sharding is targeted -
    VM store - is a single-writer workload, instead of
    performing lookup on the base file everytime to gather the
    size and block count from the backend in reads, writes and
    truncate, now the size and block count is also cached and
    kept up-to-date after every inode write in the inode ctx.
    
    TO-DO:
    Make changes in rename, link, unlink, [f]setattr and [f]stat
    to keep the relevant iatt members up-to-date in the inode ctx.
    
    Change-Id: Ica87d020dabc3a3dbccec814b26b01d6a629ff4d
    BUG: 1258905
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12126
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 070d93afe63f377539b56ed646b714bb281bd240
Author: Sakshi <sabansal@redhat.com>
Date:   Mon Jun 22 15:52:22 2015 +0530

    glusterfsd : newly added brick receives fops only after it is started
    
    When new bricks are added in the middle of an on-going
    fop like 'rm', the volfile changes without waiting for
    the newly added bricks to get port. Fops are sent to all
    bricks and may fail on some with ENOTCONN as these bricks
    may not have a port yet.
    
    This patch ensures that the volfile change happens only
    after all the bricks have a port.
    
    
    Change-Id: I7ed2413475f80d0cc8849fed33036ade8d75a191
    BUG: 1233151
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/11342
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>

commit 470869a954c17f32a3ba43ccda7442f82c0da6b2
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Sep 1 15:31:02 2015 +0530

    cluster/tier: Handle FOPs on files being migrated
    
    Determine which DHT level is responsible for
    handling fops on a file undergoing migration based
    on the name of the the linkto xattr set on the file
     being migrated and process accordingly.
    
    Change-Id: I82772e39314d4fe7f2ba0dcf22de0c6a374ee139
    BUG: 1254428
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12090
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bdbd092e2caf79a2cfd6cda507af624e9861ae30
Author: Sakshi <sabansal@redhat.com>
Date:   Thu May 28 10:49:36 2015 +0530

    glusterd : check if all bricks are started before performing remove-brick
    
    Change-Id: Ie9e24e037b7a39b239a7badb983504963d664324
    BUG: 1225716
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/10954
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 59557e1c9ca33c997743c0c03cf73c2f470c8bf3
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Wed Sep 9 17:46:16 2015 +0530

    glusterd/utils: glusterd_copy_file does not truncate target file
    
    glusterd_copy_file function copies source file to target. If
    the target file already exists and is bigger than the source
    file then it can cause file corruption.
    
    Target file should be truncated before copying source content.
    
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    
    Change-Id: Ie973f3e9fa06309ded6f69dcde41e1b60b3e028e
    BUG: 1261482
    Reviewed-on: http://review.gluster.org/12141
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 68e8d617eb62a7ec40a1db5f3f60730767a168b6
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Sep 10 16:07:29 2015 +0530

    Tier/cli: Change detach-tier commit force to detach-tier force
    
    Current detach-tier cli command support commit force.
    Deprecating the same to force.
    
    So the new syntax would be:
    
    volume detach-tier <VOLNAME>  <start|stop|status|commit|force>
    
    Change-Id: Ie86dfd72341078c0a1be94767f523730911312ef
    BUG: 1261862
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12151
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit ab667778ed7c5016d32090b98b69b3ef0c528788
Author: vmallika <vmallika@redhat.com>
Date:   Mon Sep 7 12:43:07 2015 +0530

    marker: don't account destination linkto-file during internal migration
    
    During a DHT re-balance operation, quota accounts for the destination.
    Problem of accounting this destination file are:
    1) Migration is an internal operation, 'quota list' shows more usage on the CLI
       and this will come to the normal numbers once the migration is complete
    2) If the usage is close to the limit set, then we can get 'Disk Quota
       Exceeded' errors in the I/O path during file migration
    
    Solution is we should not account of the usage on the destination file
    during migration, at the end of the migration. We need to reduce size of
    the source directory and accounting for the migrated dest file
    
    We assume that there are sufficent disk space in the back-end. DHT
    migrator should make sure that there are sufficient disk space before it
    starts the migration process.
    
    Change-Id: Ie3cfe3e4ab5241c2a127ba0edc599a053d30c3a0
    BUG: 1260545
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12113
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 2ebfc3d0a61ab88bc0e4bad07157f69f618ad54f
Author: hari gowtham <hgowtham@redhat.com>
Date:   Wed Sep 9 19:17:17 2015 +0530

    Tiering: change in status for remove brick and rebalance
    
    when we trigger a detach tier start on a tier vol,
    it shows in the volume status task as "remove brick" instead of "Detach tier"
    
    Status of volume: vol1
    Gluster process                             TCP Port  RDMA Port  Online  Pid
    ------------------------------------------------------------------------------
    Hot Bricks:
    Brick 10.70.42.171:/data/gluster/hbr1       49154     0          Y       25098
    Cold Bricks:
    Brick 10.70.42.171:/data/gluster/p1         49152     0          Y       25101
    Brick 10.70.42.171:/data/gluster/p2         49153     0          Y       25112
    NFS Server on localhost                     N/A       N/A        N       N/A
    
    Task Status of Volume vol1
    ------------------------------------------------------------------------------
    Task                 : Tier migrate
    ID                   : e11d5a3d-b1ae-4c3f-8f95-b28993c60939
    Status               : in progress
    
    Status of volume: vol1
    Gluster process                             TCP Port  RDMA Port  Online  Pid
    ------------------------------------------------------------------------------
    Hot Bricks:
    Brick 10.70.42.171:/data/gluster/hbr1       49154     0          Y       25098
    Cold Bricks:
    Brick 10.70.42.171:/data/gluster/p1         49152     0          Y       25101
    Brick 10.70.42.171:/data/gluster/p2         49153     0          Y       25112
    NFS Server on localhost                     N/A       N/A        N       N/A
    
    Task Status of Volume vol1
    ------------------------------------------------------------------------------
    Task                 : Detach tier
    ID                   : 76d700b1-5bbd-43ed-95fd-1640b2b4af31
    Status               : completed
    
    Change-Id: I4bd3b340d4e700e8afed00e1478b8a8b54dfe2e2
    BUG: 1261837
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12149
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit bc11be7864eb7f22ad6b529e95bac5a2833f5a01
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Sep 10 14:19:06 2015 +0530

    Tier/glusterd: Do not allow attach-tier if remove-brick is not committed
    
    When attaching a tier, if there is a pending remove-brick
    task, then should not allow attach-tier. Since we are not
    supporting add/remove brick on a tiered volume, we won't
    able to commit pending remove-brick after attaching the
    tier
    
    Change-Id: Ib434e2e6bc75f0908762f087ad1ca711e6b62818
    BUG: 1261819
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12148
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 51632e1eec3ff88d19867dc8d266068dd7db432a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Sep 10 11:52:27 2015 +0530

    tier/glusterd: volume status failed after detach start
    
    After triggering detach start on a tiered volume fails.
    This because of brick count was wrongly setting in rebal
    dictionary.
    
    Change-Id: I6a472bf2653a07522416699420161f2fb1746aef
    BUG: 1261757
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12146
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit cb8db8dfce0394e30cb25983a402de7beaa9c63f
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Sep 15 11:07:03 2015 +0530

    Tier/cli: tier related information in volume status command
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volStatus>
        <volumes>
          <volume>
            <volName>v1</volName>
            <nodeCount>5</nodeCount>
            <hotBrick>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/hbr1</path>
                <peerid>137e2a4f-2bde-4a97-b3f3-470a2e092155</peerid>
                <status>1</status>
                <port>49154</port>
                <ports>
                  <tcp>49154</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>6535</pid>
              </node>
            </hotBrick>
            <coldBrick>
              <node>
                <hostname>10.70.42.203</hostname>
                <path>/data/gluster/tier/cb1</path>
                <peerid>137e2a4f-2bde-4a97-b3f3-470a2e092155</peerid>
                <status>1</status>
                <port>49152</port>
                <ports>
                  <tcp>49152</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>6530</pid>
              </node>
            </coldBrick>
            <coldBrick>
              <node>
                <hostname>NFS Server</hostname>
                <path>10.70.42.203</path>
                <peerid>137e2a4f-2bde-4a97-b3f3-470a2e092155</peerid>
                <status>1</status>
                <port>2049</port>
                <ports>
                  <tcp>2049</tcp>
                  <rdma>N/A</rdma>
                </ports>
                <pid>6519</pid>
              </node>
            </coldBrick>
            <tasks>
              <task>
                <type>Rebalance</type>
                <id>8da729f2-f1b2-4f55-9945-472130be93f7</id>
                <status>4</status>
                <statusStr>failed</statusStr>
              </task>
            </tasks>
          </volume>
            <tasks/>
          </volume>
        </volumes>
      </volStatus>
    </cliOutput>
    
    Change-Id: Idfdbce47d03ee2cdbf407c57159fd37a2900ad2c
    BUG: 1263100
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12176
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit bb2370514598a99e6ab268af81df57dc16caa2c5
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jul 21 18:14:22 2015 +0530

    tier/dht: unlink fails after lookup in a directory
    
    unlink fails with invalid argument for files that
    are being present on cold tier, before attaching.
    
    All of the fops will be hashed to hot_tier after
    attach-tier (unless explicitly set the "rule"
    option). Lookups sent to directory, will eventually
    search the directory using readdirp, and will
    populate inode_ctx for the inodes based on the output,
    in respective dht_xlators. So the readdirp will
    populate inodes_ctx for the files (that is already
    present in volume before attaching) in cold-dht
    only because it got the entries from the cold-tier.
    
    So when an unlink comes on such an inode, the lookup
    associated with the unlink will be send as a
    re validate request to cold-tier only, since
    already a lookup was performed on the inode,
    and the new lookup will succeed. So from the
    unlink of dht, it will hash to cold-tier but the
    cached_subvol will be cold, since there is a
    mismatch in hash and cach , it chose hashed
    subvolume and will sent the fop to hot dht,
    and the fops fail with EINVAL from the hot-dht
    since it does not have inode_ctx stored for
    that inode (because, no lookup was performed
    from hot-dht).
    
    Change-Id: Ib7c14a9297a22d615f7a890a060be4809b5a745a
    BUG: 1236032
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11675
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c9d7d1e8975bad63811e32c5289a144b734c9ab2
Author: hari gowtham <hgowtham@redhat.com>
Date:   Tue Sep 15 14:57:24 2015 +0530

    Tiering:Changing error message as detach-tier instead of "remove-brick"
    
    Change-Id: Id93424a08f601a8d7540d96a47ed2b0497d4a631
    BUG: 1263177
    Signed-off-by: hari gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12177
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 2834bdf52c1ed690f74ed05fec5d28ecd05c0624
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Sep 15 16:05:25 2015 +0530

    tier/cli : adding a check for gluster v tier help command
    
    Currently, 'gluster v tier/attach-tier/detach-tier help' command
    shows the usage, and then prints 'Tier command failed'. With this
    patch the error message is removed.
    
    Change-Id: I1679fe3303d73ba6b6fdbb7ee18028062d446f39
    BUG: 1263224
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/12181
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit a9bb3dcb1d22c5bfb527b9b85ad238b0137d3282
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Sep 16 10:26:44 2015 -0400

    cluster/tier do not flag migration error on already migrated file
    
    In some cases a brick will try to migrate a file that has already
    been migrated. This is a legal case, e.g. when both bricks
    are replica pairs.
    
    Change-Id: If2578b947014cbbdfb3c6591db9044d6b1d92774
    BUG: 1263726
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12185
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Joseph Fernandes
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0cf1c851b9fc6b98b5839b32ef7e3ff38d87f3c3
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Tue Sep 15 16:07:32 2015 +0530

    cluster/tier: Fixed a crash in tiering
    
    An incorrect check was causing the arguments to
    the promote thread to be cleared before the thread
    was done with them. This caused the process to crash
    when it tried to dereference a NULL pointer.
    
    Change-Id: I8348309ef4dad33b7f648c7a2c2703487e401269
    BUG: 1263204
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12179
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Joseph Fernandes

commit 22882a9b810c4d5c7a7be0f1fac7069422d08b57
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Sep 14 15:43:31 2015 +0530

    afr: perform replace-brick in a synctask
    
    Problem:
    replace-brick setxattr is not performed inside a synctask. This can lead
    to hangs if the setxattr is executed by epoll thread, as the epoll
    thread will be waiting for replies to come where as epoll thread is the
    thread that needs to epoll_ctl for reading from socket and listen.
    
    Fix:
    Move replace-brick to synctask to prevent epoll thread hang.
    
    This patch is in line with the fix performed in
    http://review.gluster.org/#/c/12163/
    
    Change-Id: I6a71038bb7819f9e98f7098b18a6cee34805868f
    BUG: 1262345
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12169
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 63e3806ba3c4d5f196ad2254f63d85b79602705a
Author: anand <anekkunt@redhat.com>
Date:   Tue Sep 15 12:05:51 2015 +0530

    systemd/spec/glusterd: Adding EnvironmentFile in glusterd systemctrl service file.
    
    Issue: glusterd was not running in debug mode, this is because of
    "systemctrl start glusterd" was not reading configuration from glusterd-sysconfig file.
    
    Fix: Set glusterd-sysconfig file as "EnvironmentFile"  and pass args to glusterd.
    
    Change-Id: I6a032a2e86e5a25c39199ddf953bfbd6590d53b6
    BUG: 1263087
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/12175
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 26917cb3bb476e6b2452405baa5698f7fb01ceda
Author: Akhil Bhansali <bhansaliakhil@gmail.com>
Date:   Thu Sep 10 15:56:21 2015 +0530

    BZ 789278: Coverity bug fixes for logically dead code
    
    Removing the logically dead code as reported by coverity tool run
    on GlusterFS.
    The code changes are removal of logically dead code, hence did not
    run the testcases.
    CIDs Fixed starts from 1292652 to 1292663 in sequence.
    Signed-off-by: Akhil Bhansali <bhansaliakhil@gmail.com>
    
    Change-Id: I05b35f744c89b5e49b6322635c7a0d367ef10abb
    BUG: 789278
    Reviewed-on: http://review.gluster.org/12150
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7b9135045685125d7c94d75f06d762fa1c5ba4b9
Author: Sakshi <sabansal@redhat.com>
Date:   Mon Aug 31 16:06:35 2015 +0530

    dht: reverting changes that takes lock on all subvols to prevent rmdir vs lookup selfheal race
    
    Locking on all subvols before an rmdir is unable to remove all
    directory entries. Hence reverting the patch for now.
    
    Change-Id: I31baf2b2fa2f62c57429cd44f3f229c35eff1939
    BUG: 1245065
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/12125
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit fa08597a004b591afbeb478d0a736ec09066f648
Author: Anuradha Talur <atalur@redhat.com>
Date:   Fri Sep 11 18:43:36 2015 +0530

    afr : get split-brain-status in a synctask
    
    On executing `getfattr -n replica.split-brain-status <file>` on mount,
    there is a possibility that the mount hangs. To avoid this hang,
    fetch the split-brain-status of a file in synctask.
    
    Change-Id: I87b781419ffc63248f915325b845e3233143d385
    BUG: 1262345
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12163
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 2e041639d8e49e2b768dd43c6f702106250e4da9
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Sep 10 11:27:42 2015 +0530

    tier/glusterd : Disable subvol match check during detach tier
    
    For tiering, user does not have authorization to choose
    for bricks to detach, so we don't need to whether subvols
    match for the bricks or not.
    
    Change-Id: I7e777ccc1aa261f652f9b158718fcd55185c7794
    BUG: 1261741
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12145
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 2ec8ea8769e943d3987dd80f8f6937359bcccf34
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Fri Sep 11 22:18:03 2015 +0530

    cluster/dht : Propagate op_errno on failure
    
    Fixed issue where dht_selfheal_layout_lock_cbk does not propagate
    the op_errno.
    
    Change-Id: I0b968339db65d2969e36e64407eeb724cc6516bd
    BUG: 1262438
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12165
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c31ac73cd8e9ca4b872a48667e09019991dea00b
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Sep 11 08:52:44 2015 -0400

    dht/cluster: Avoid crash if local is NULL
    
    This patch addresses crash handling if local is NULL. In addition to that,
    we were not unwinding if no lock is taken in dht_linkfile_create_cbk(create/mknod).
    This patch handles that also.
    
    Change-Id: Ibcff317f10d60e7865fd7ffb9479b3af53c9ef17
    BUG: 1260051
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12160
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 605e47fe69a7e11f09f95699348dfab4bbab03ff
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Sep 9 08:34:08 2015 +0530

    features/shard: Add appropriate NULL checks to prevent excessive logging
    
    Also,
    1) the getxattr() callback must check for the fop return status
       before attempting to delete the internal keys.
    2) the correct dict was not being used in shard_getxattr_cbk(). This
    patch also fixes that issue.
    
    Change-Id: I516a1d98e112b572bcec7d1f1e03e23152567be3
    BUG: 1260637
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12136
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c90c03e9a22d4e21ac7570482255ab42d7ff188e
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu Sep 10 15:25:55 2015 -0400

    cluster/tier fix bug with sql includes introduced by 12031
    
    We accidentally introduced a bug where client translators have a
    dependency on sql. This broke freebsd smoke tests. Fix is to
    abstract from the client those dependencies.
    
    Change-Id: I7152573a489bacc8f32e6eb139f9ff4408288f5b
    BUG: 1260730
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12155
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit c8b23d0135942c6d625e98666a00308e760b7afc
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Sep 11 06:56:47 2015 -0700

    Revert "gluster/tier Remove tier.t from spurious failure list"
    
    This reverts commit 3a6e397bccf7ebaf9528617f5615553670211edf.
    
    Change-Id: I7bed21be205dea14c8b0f462bfb117febec5b1b4
    Reviewed-on: http://review.gluster.org/12164
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0166dca4f268f07dcbf9db7ca971ed16e296e8b7
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Aug 17 15:09:57 2015 +0530

    nfs : logging improvements
    
    NFS log-warning messages logged twice in cbk function. Though,
    the logging messages are not exactly duplicate, instead of
    logging twice, they can be merged to one log message and the
    other log message is removed in cbk functions.
    
    Example:
    (1)
    W [nfs3.c:2075:nfs3svc_write_cbk] 0-nfs: 16f4dce6:
            /f.195 => -1 (Disk quota exceeded)
    (2)
    W [nfs3-helpers.c:3443:nfs3_log_write_res] 0-nfs-nfsv3:
            XID: 16f4dce6, WRITE: NFS: 69(Resource (quota)
            hard limit exceeded), POSIX: 122
            (Disk quota exceeded), count: 0, UNSTABLE,
            wverf: 1381508849
    
    Here, the second message is more elaborative, and is similar
    to (1). Since file name is not present in (2), it is added to (2)
    and then removing all mesages of type (1).
    
    Change-Id: I6028ab17b23948493a065dfad92fe4984548511f
    BUG: 1254146
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11936
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 7f327d3b4f9222995d2ee78862e48ca44c28411c
Author: anand <anekkunt@redhat.com>
Date:   Sat Aug 22 01:09:53 2015 +0530

    firewall/spec: Create glusterfs firewall service if firewalld installed.
    
    It creates glusterfs firewall service during installation.
    
    glusterfs service : It contains all default ports which needs to be opened.
    During installation  glusterfs.xml is copied into firewall service directory(/usr/lib/firewalld/services/).
    
    Note:
    1.For bricks: It opens the 512 ports, if brick is running out side this range(>49664) then admin need to open the port
    for that brick.
    2.By default this service is not enabled in any of zone.
    
    To enable this service(glusterfs) in firewall:
    
    1. Get active zone(s) in node
         firewall-cmd  --get-active-zones
    
    2. Attached this service(glusterfs) to zone(s)
       firewall-cmd  --zone=<zone_name>  --add-service=glusterfs               --To apply runtime
       firewall-cmd  --permanent  --zone=<zone_name>  --add-service=glusterfs  --To apply permanent
    
    Note:
      we can also use firewall-config which gives GUI to configure firewall.
    
    
    
    Change-Id: Id97fe620c560fd10599511d751aed11a99ba4da5
    BUG: 1253967
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/11989
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 22cad7b522f223b47d87df6724f34273306ab7cd
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Sep 4 05:14:05 2015 -0400

    dht/remove-brick: Avoid data loss for hard link migration
    
    Problem: If the hashed subvol of a file has reached cluster.min-free-disk,
    for a create opertaion a linkto file will be created on the hashed and
    the data file will be created on some other brick.
    
    For creation of the linkfile we populate the dictionary with linkto key
    and value as the cached subvol. After successful linkto file creation,
    the linkto-key-value pair is not deleted form the dictionary and hence,
    the data file will also have linkto xattr which points to itself.This looks
    something like this.
    
      client-0                                    client-1
    -------T file                               rwx------file
    linkto.xattr=client-1                       linkto.xattr=client-1
    
    Now coming to the data loss part. Hardlink migration highly depend on this
    linkto xattr on the data file. This value should be the new hashed subvol
    of the first hardlink encountered post fix-layout. But when it tries to
    read the linkto xattr it gets the same target as where it is sitting.
    
    Now the source and destination are same for migration. At the end of
    migration the source file is truncated and deleted, which in this case
    is the destination and also the only data file it self resulting in
    data loss.
    
    Change-Id: I36b1d105752bd9467757ecf3f103b45c666783d6
    BUG: 1260051
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/12105
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b1f851709c30505cac2b63bc49234ae818559d2d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Sep 9 17:25:14 2015 +0530

    features/shard: Do not return non-negative status on failure in writev
    
    Change-Id: I5f65c49484e44a05bb7df53c73869f89ad3392e0
    BUG: 1261399
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12140
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 3a6e397bccf7ebaf9528617f5615553670211edf
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Sep 8 12:26:47 2015 -0400

    gluster/tier Remove tier.t from spurious failure list
    
    The spurious failure was related to database lock contention,
    and was fixed in patch 12031.
    
    Ran tier.t in loop (very many) times successfully to confirm fixed.
    
    Change-Id: Ib7446bcd02c76dea03b4cf273aae0dba27c4ef19
    BUG: 1231268
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/12128
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d55a6fee5cdda8be9dd555b4f3b5c0cc005117ef
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Aug 21 06:45:46 2015 -0400

    cluster/tier: add gluster v tier <vol>
    
    Currently the tier feature piggy backs off the rebalance command
    syntax to obtain status and this is clumsy. Introduce a new
    tier command that can do tier specific operations, starting
    with volume status to display counters.
    
    Old commands:
    gluster volume attach-tier <vol> [replica count] {bricklist..}
    gluster volume detach-tier <vol> {start|stop|commit}
    
    New commands:
    gluster volume tier <vol> attach [replica count] {bricklist} |
                              detach {start|stop|commit} |
                              status
    
    Change-Id: Ic07b3c6260588162de7d34380f8cbd3d8a7f35d3
    BUG: 1255693
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11984
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d35b8b60d7f436c5929dfa8d647f1d41aecfc237
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 2 14:29:17 2015 -0400

    build: Mac OS X build issues, ACLs
    
    Mac OS X doesn't support POSIX ACLs.
    
    Change-Id: I875cd2c0403a0665f1f7572b4d28eb5835958e7f
    BUG: 1238798
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11518
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4cd4a97e8410f0888c6b154a40279c143dc9f549
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 19 01:23:23 2015 -0400

    build: fix build on Mac OS X, gfapi symbol versions
    
    symbol versions for the handle apis are incorrect in glfs-handles.h
    
    Change-Id: I9f239a4e427ea236a6a837a7c7acc980da10ca79
    BUG: 1254850
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11954
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 04b5fe0f6ab32bafeefc30558e259cb47e1b71f3
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Sep 4 19:46:48 2015 +0530

    dht: NULL dereferencing causes crash
    
    If linkfile_create is failed for some reason, then
    we are trying to dereference a null variable
    
    Change-Id: I3c6ff3715821b9b993d1bab7b90167de2861e190
    BUG: 1260147
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/12106
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit ccb52e0cba557a792b9227c86155a2dc8e29f44f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 8 08:22:23 2015 +0530

    features/shard: Filter internal shard xattrs in {get,remove,set}xattr
    
    Change-Id: I40e4a5dbd13d6c3d777e7e01f93dabc83e52b137
    BUG: 1260637
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12121
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 0bd9beabd2facbd2c7fb52e74dc56ecb89abde8e
Author: Paul Stauffer <paulds@horde.com>
Date:   Mon Aug 17 21:00:11 2015 -0700

    bash-completion: Swap order of characters in egrep bracket expression
    
    With glusterfs-cli installed, bash tab completion fails to work and prints an
    error message:
    
        $ gluster volgrep: Invalid range end
        ^C
    
    The problem is caused by the ordering of characters within an egrep bracket
    expression in the "_gluster_completion()" function defined in
    /etc/bash_completion.d/gluster.  The file contains this line:
    
        egrep -ao --color=never "([A-Za-z0-9_-.]+)|[[:space:]]+|." |  \
    
    And egrep is interpreting the "-" character in that bracket expression as
    indicating a range is being requested, "_-." Fortunately, "_" actually comes
    after ".", this range expression is invalid, and egrep throws the error instead
    of silently not doing what was intended.
    
    The fix is simply to swap the positions of "-" and "." in that bracket
    expression:
    
        egrep -ao --color=never "([A-Za-z0-9_.-]+)|[[:space:]]+|." |  \
    
    With this change, bash tab completion works as intended.
    
    Change-Id: Iace2d57a1122b4530987ba6f5f5558b56b094665
    BUG: 1243108
    Signed-off-by: Paul Stauffer <paulds@horde.com>
    Reviewed-on: http://review.gluster.org/11939
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 96af474045c9ba5ab74ca76daa823d91a0a0c610
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Aug 27 17:23:07 2015 +0530

    tier/ctr: Solving DB Lock issue due to write contention from db connections
    
    Problem: The DB on the brick is been accessed by CTR, for write and
    tier migrator, for read and write. The write from tier migrator is reseting
    the heat counters after a cycle. Since we are using sqlite, two connections
    trying to write would cause a db lock contention. As a result CTR used to fail
    to update the db.
    
    Solution: Using the same db connection of CTR for reseting the heat counters.
    1) Introducted a new IPC FOP for CTR
    2) After the query do a ipc syncop to the underlying client xlator associated
       to the brick.
    3) CTR in brick will catch the IPC FOP and cleat the heat counters.
    
    Change-Id: I53306bfc08dcdba479deb4ccc154896521336150
    BUG: 1260730
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/12031
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 9efce73fb31d520706a6d47de4daa4fb3366e6a6
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Fri Sep 4 22:10:55 2015 +0530

    glusterd: Do not allow "detach-tier commit" unnecessarily
    
    Currently when user execute gluster v detach-tier commit command without
    starting detach-tier or without giving force option then gluster will
    success this operation.
    
    Detach-tier commit should not allow without giving "force" optioin.
    
    Change-Id: Id161c288f6f3e0f6b298878a5c35a49fcbd9c6e3
    BUG: 1260185
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/12107
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 55a493f4db6752303ad2a88572e4d75453054bce
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Sep 3 09:49:56 2015 +0530

    afr: Do not wind the full writev payload to arbiter brick
    
    ...because the arbiter xlator just unwinds it without passing it down
    till posix anyway. Instead, send a one-byte vector so that afr write
    transaction works as expected.
    
    Change-Id: I52913ca51dfee0c8472cbadb62c5d39b7badef77
    BUG: 1259572
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12095
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>

commit da882973235c7d2fc2ad20c030dadd327366a58c
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Wed Aug 5 19:30:20 2015 +0530

    xml/tiering: enhance xml output for tiering status related cli commands
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volRebalance>
        <task-id>34f47e29-2193-4a86-9b1e-c7e56bdae3d4</task-id>
        <op>7</op>
        <nodeCount>1</nodeCount>
        <node>
          <nodeName>localhost</nodeName>
          <promotedfiles>0</promotedfiles>
          <demotedfiles>0</demotedfiles>
          <statusStr>in progress</statusStr>
        </node>
      </volRebalance>
    </cliOutput>
    
    Change-Id: I61083f7b9b0b3bd840982b8c5d6ea4b42e27c9b3
    BUG: 1252737
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/11890
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 7b6183c36ebfe020b724c95b018a8cd535e1ecdd
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Sep 7 16:46:48 2015 +0530

    uss : handle `buf` variable properly in svs_glfs_readdir()
    
    The svs_glfs_readdir() is a generic function which is called from
    svs_readdir() and svs_readdirp(). But in svs_readdir 'buf' variable
    is passed as NULL, then glfs_read_readdir() will fail. This patch
    will fix the same.
    
    Change-Id: Id02e4e17e30c85de117db5ddd9f97b578622dff9
    BUG: 1260611
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12117
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 53cd14b75f65ef602c766fce6ab7b8a25ca5b514
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Fri Aug 21 18:18:09 2015 +0530

    glusterd: volume status backward compatibility
    
    volume status message of 3.7 does not display all the brick in a mixed
    cluster(3.6 and 3.7). it displays the bricks in 3.7 and misses bricks
    in 3.6 due to the key difference for ports.
    
    Status of volume: vol1
    Gluster process                             TCP Port  RDMA Port  Online  Pid
    ------------------------------------------------------------------------------
    Brick 10.70.42.171:/data/gluster/tier/cbr2  49153     0          Y       13494
    Brick 10.70.42.203:/data/gluster/tier/cbr2  49154     0          Y       27686
    NFS Server on localhost                     N/A       N/A        N       N/A
    NFS Server on dhcp42-203.lab.eng.blr.redhat
    .com                                        N/A       N/A        N       N/A
    
    Task Status of Volume vol1
    ------------------------------------------------------------------------------
    There are no active volume tasks
    
    Change-Id: Icf0dc01a3d21d0889c43e2868c646a0c7e07ff25
    BUG: 1255694
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/11986
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit dd09c684e0baec6ecde5736a1486f2bc4d3213ef
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Sep 2 12:19:58 2015 +0530

    geo-rep: Fix portability issues with NetBSD
    
    Fixes portability issues in gverify.sh and
    libcxattr.py with NetBSD.
    
    Change-Id: Idfaa6cf3815136e6a2343aab98d979b6ab451bbd
    BUG: 1257847
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12088
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 0e65ee0ceb8827ebac46bc6e714818d321cbd998
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Thu Aug 27 15:12:35 2015 +0530

    man or info page of gluster needs to be updated with self-heal commands
    
    Change-Id: I6f50f88e56d9d9a8f875c7edac28e2a023b65881
    BUG: 1122395
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/12030
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5b49851601ab53450777438268f0732c65795f98
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Sep 2 18:40:32 2015 +0530

    tests: Reorganise cleanup function
    
    Change-Id: Ifbfb4b05230f023c244760a7d57c33c4463ce6d9
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12093
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 378b625698fe01ed2c3a6f4f065a699b2d573947
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Sep 3 12:05:12 2015 +0530

    tests: check free space only on gluster mount
    
    Change-Id: I06de4f555e66fac2594676572c8f8a4ee08f8131
    BUG: 1251346
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12096
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 76233f0cf43125a83b79de3ca5dc742fc9850cce
Author: vmallika <vmallika@redhat.com>
Date:   Tue Sep 1 14:21:43 2015 +0530

    test: fix spurious failure from ./tests/basic/quota-nfs.t
    
    Before checking for the quota usage,
    umount and mount NFS mountpoint to flush the NFS cached data.
    
    This test is fails on NetBSD, so marking the test as bad-test
    
    Change-Id: I1f30f5d9a919b3959c9f158366bd2f47569c8e03
    BUG: 1258766
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12075
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b5fff7326e9203c650eb5d395bc5a338075821f1
Author: Anoop C S <anoopcs@redhat.com>
Date:   Sat Aug 15 10:38:00 2015 +0530

    protocol-client/server: Fix incorrect grace-timeout value in logs
    
    When grace-timer is initialized via server/client init,
    the default or reconfigured value for grace-timeout is
    displayed incorrectly in both server and client logs.
    This is because we use gf_time_fmt() to format this
    grace-timeout value with gf_timefmt_s as the time format
    as shown below:
    
    gf_time_fmt (timestr, sizeof timestr, conf->grace_ts.tv_sec,
                         gf_timefmt_s);
    
    gf_timefmt_s format is a wrapper for %s format specification
    used in strftime library call which populates the number
    of seconds since the Epoch [1970-01-01 00:00:00 +0000 (UTC)].
    But this particular format is dependent on timezone
    [1970-01-01 05:30:00 +0530 (IST)]and thus displayed incorrectly
    in logs.
    
    Example:
    For IST with default grace-timeout value 10, it is displayed
    as -19790 which is calculated as follows,
    1970-01-01 00:00:10 - 1970-01-01 05:30:00 = -19790 seconds.
    
    Change-Id: I1bdf5d12b2167323f86f0ca52a37ffb316b3f0a2
    BUG: 1227667
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/11930
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fe7b37960bbef791d9bed79760b61b1d40ca81cd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 3 15:47:01 2015 +0530

    features/shard: Fix incorrect op_ret in READV
    
    Change-Id: I31ac99b290f82f4b74236c206193f7641c73d4dc
    BUG: 1259651
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12099
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 092cc95ddc7af7d99bb362e790cf52c296c25bb8
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Sun Aug 2 15:17:30 2015 +0100

    cluster/tier: avoid filling /var/run with tiering files
    
    We failed to delete old promote/demote workfiles in /var/run.
    This fix removes the <pid> postfix so there will be only a
    single pair of files.
    
    Change-Id: Ib9aafe7b4a9d4b0c05cf03a94cc1057a423a27d2
    BUG: 1253970
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11931
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit c42a888fe9d69bf942f2e65bf982d848098978b6
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Mon Jun 8 12:33:52 2015 +0530

    afr: Correction to self-heal-daemon documentation
    
    The reference in the documentation is outdated and need path modification
    
    Change-Id: Ia3712b5064b35b85f83d3b920ecba35dd867f6d3
    BUG: 1229127
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11117
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 78e89fb0a70a053e85bba0f68ff4e8841818dd54
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Sep 1 15:54:39 2015 +0530

    afr: Unset dirty xattr after setting pending xattr during post-op
    
    In AFR transaction, in the pre-op, the dirty xattr is set. In the
    post-op, if the transaction fails on one of the bricks, then on the
    healthy brick, the dirty xattr is unset and then the pending xattr (for
    the brick that went down) is set in that order. If the brick crashes
    after unsetting the dirty xattr, we have lost information about a
    pending heal. Hence we need to reverse the order, i.e. set pending xattr
    first followed by unsetting the dirty.
    
    Change-Id: I0b8a872cb4579a1bad602f70c76f09691bd582b2
    BUG: 1258801
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12078
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit d46d571d86c86bd387de323522cfcb8a013f28ad
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 1 12:12:21 2015 -0400

    packaging: incorrect %ghost of .../hooks/1/delete causes install failure
    
    .../hooks/1/delete is not a %ghost by virtue of having actual files
    namely .../post/S57glusterfind-delete-post.py
    
    Change-Id: I544bcfbc898007c79be11e911e6d66e242018740
    BUG: 1258975
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/12080
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit ff1dd9885ff99a9d185f4efe5613c7c5f387d2f0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 29 13:50:09 2015 +0530

    storage/posix: Prevent malformed internal link creations
    
    Change-Id: Ia3408f795dcfac143fe898fc5f4d31d2c6f236c1
    BUG: 1212110
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10999
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 1ad184978892bc7368c5da11c59ec4fad73cb1df
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Sep 1 21:53:10 2015 +0530

    tests: remove arbiter-statfs.t from bad tests
    
    This test case failed due to the G_LOG clobbering NetBSD files which
    have been fixed by http://review.gluster.org/11993. Hence removing it
    from is_bad_test()
    
    Change-Id: I719fa623f397b1d0799c9fe0c00ad7979143e1b2
    BUG: 1256588
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/12057
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 8b7af53cb88ab75c0f15c89ce6867a9c6c8a4e67
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Sun Aug 2 08:25:45 2015 -0400

    build: Fix build on Mac OS X, boolean
    
    bool and true conflict with clang macros in clang on Mac OS X,
    possibly with newer (?) versions of clang on Linux
    
    Change-Id: Ia8c56ae68b4ebffb99b0684ac72d68ec50eaa7fa
    BUG: 1249391
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11816
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4d4c7d5dc54850dcf916083b2b1398d9bfe2bfe6
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Mon Aug 10 18:42:05 2015 +0530

    geo-rep: Update geo-rep status, if monitor process is killed
    
    Problem:
    When the monitor process itself is getting killed, geo-rep session
    still shows as active.
    
    Status command will just pick up the content from the status file
    to show the output. Monitor process is the one which updates the Status file.
    
    When the monitor process itself gets killed, there is no way to update
    the status file. So, geo-rep session status command ends up showing
    last updated Status present in the status file.
    
    Solution:
    While getting the status output, check whether monitor process is running.
    If it is NOT running, update the status as STOPPED.
    
    Change-Id: I86a7ac1746dd8f27eef93658e992ef16f6068d9d
    BUG: 1251980
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/11873
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d713488e47a384814e55b484f9a7e81664021d52
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Aug 31 15:07:49 2015 +0530

    Update to MAINTAINERS
    
    Added new maintainers as per discussion in:
    
    http://www.gluster.org/pipermail/gluster-devel/2015-June/045471.html
    
    Removed maintainers who have not been active in a while.
    
    Change-Id: Ia84bb0e7c65834567ac01112665e7848525488bd
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/11330
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2a568e0c0fd3f23a94cc87bf4c0bd07aaa65d5a5
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Sep 1 11:24:09 2015 +0530

    tests: Remove geo-rep tests from bad tests
    
    Remove 'tests/geo-rep/georep-basic-dr-rsync.t' and
    'tests/geo-rep/georep-basic-dr-tarssh.t' from bad
    tests as it passes on linux machines. It is disabled
    only in NetBSD untill portability issues are fixed.
    (https://bugzilla.redhat.com/show_bug.cgi?id=1257847)
    
    Also add increase sleep timining to let the data
    sync.
    
    Change-Id: Ifc831353a345bcf5605fc4dfba693df891bb6d5b
    BUG: 1227624
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/12072
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 7b390983768e833a8df15b994038155c53d71bdd
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Wed Jul 29 23:47:34 2015 +0530

    logging : GF_LOG_NONE logs always
    
    Shouldn't GF_LOG_NONE mean "Never log this"? If so, it's not being
    tested for and is, instead, treated as a higher priority than
    CRITICAL thus is always logged.
    
    Change-Id: Icad1e02a720a05ff21bd54ebf19c0032e6d5ce03
    BUG: 1246794
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/11797
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 31000d1a62da4e8beafb6f5a7b30ae593479a1ce
Author: Richard Wareing <rwareing@fb.com>
Date:   Thu Aug 27 21:06:37 2015 -0700

    nfs: Fixes "Remote I/O error" mount failures
    
    - Fixes issue where NFS mount fail with "Remove I/O error" after the
      target directory has been deleted and re-created after the gNFSd has
      already cached the inode of the first generation of the target
      directory.
    - The solution is to follow the guidance of the AFR2 comments and
      refresh the inode by deleting it from cache and looking it up
      again.
    
    BUG: 1258196
    Change-Id: I9c7d8bd460ee9e5ea0b5b47d23886b1afcdcd563
    Reported-by: Richard Wareing <rwareing@fb.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/12046
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0773ca67fdb60a142207759fa6c07a69882ce59c
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jul 28 12:11:12 2015 -0400

    all: reduce "inline" usage
    
    There are three kinds of inline functions: plain inline, extern inline,
    and static inline.  All three have been removed from .c files, except
    those in "contrib" which aren't our problem.  Inlines in .h files, which
    are overwhelmingly "static inline" already, have generally been left
    alone.  Over time we should be able to "lower" these into .c files, but
    that has to be done in a case-by-case fashion requiring more manual
    effort.  This part was easy to do automatically without (as far as I can
    tell) any ill effect.
    
    In the process, several pieces of dead code were flagged by the
    compiler, and were removed.
    
    Change-Id: I56a5e614735c9e0a6ee420dab949eac22e25c155
    BUG: 1245331
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/11769
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 038dfe57cf0c5944b0392332dbf5a00bb1208150
Author: Mohamed Ashiq <mliyazud@redhat.com>
Date:   Wed Aug 12 15:21:17 2015 +0530

    libglusterfs:Porting log messages to new framework
    
    Change-Id: I8625b7dc8941720cc7a864b8fddbcc7b4c485fcd
    BUG: 1252836
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/11896
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 99cd07c596f74b1ee8a88c4a43b37eb0921e5fe2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Sep 1 10:53:19 2015 +0530

    tests: add bug-948686.t to bad_tests
    
    bug-948686.t intermittely ends up in a race in GlusterD where one thread deletes
    a stale volume and on a volume start request a start is attempted on the same
    object which might be freed up by the other thread. We are considering to use
    refcounting mechanism while accessing volinfo objects to get rid of this problem
    but that needs a significant amount of time in development. Till then adding
    this test in bad_tests ()
    
    Change-Id: I3ddc025b07c47b17ea75554d5cc809a839365f10
    BUG: 1258714
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12070
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4b5aec8da9be69da077e1fcc7e852d224517ecc0
Author: Brad Hubbard <bhubbard@redhat.com>
Date:   Wed Aug 19 18:56:06 2015 +1000

    glusterd: Return better error messages for probe and detach failures
    
    We handle some specific errors and return good error messages for those, but for
    the default case where the error code is not recognised we just report "unknown
    errno". This patch attempts to at least return the output of strerror to provide
    more informative errors.
    
    BUG: 1257149
    Change-Id: I0027e74e41adac4ab0c0a929c6fff56878bf39c8
    Signed-off-by: Brad Hubbard <bhubbard@redhat.com>
    Reviewed-on: http://review.gluster.org/12021
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 4c6d1c0dc7e5f51c7f3d477fb274517d57289276
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Fri Jul 10 11:27:26 2015 +0530

    posix.c posix-helpers.c: porting new log messages
    
    Change-Id: I0c306d796ff49263d8a6c191b24a41da8a21bd2c
    BUG: 1252695
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/11609
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0baf199b065ee3adcbf36a503ac91737ab39f7e1
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Thu Aug 13 12:53:33 2015 +0530

    performance translators : porting the missing gf_log to gf_msg
    
    Change-Id: I5cc2b4669b164fe09637c86da05d2d94589dd7e4
    BUG: 1253149
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/11906
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9f52d22690b3b0aac0a736eb15fe649fde6286b5
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Aug 24 18:01:19 2015 +0530

    tests : workaround for the spurious failure in mount-nfs-auth.t
    
    Change-Id: I459a0c60743291a2e164a5e0a76a7e2577afdae0
    BUG: 1256352
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/12006
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e012bdc721945fb6d996e3f67881a705ef966026
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Aug 13 13:11:32 2015 +0530

    tests: Fix return value in geo-rep tests
    
    Remove the function 'data_tests' and TEST
    each fop in testcase itself to determine
    the exact test that fails.
    
    Change-Id: Iffc3e2ac3b0fc0c7c64259fcdff8f27b146dcb9b
    BUG: 1227624
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11907
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7566c94633b602156755297493fad1d24d1ba52f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Aug 31 12:43:36 2015 +0530

    features/shard: Fix unlink failure due to non-existent shard(s)
    
    Unlink of a sharded file with holes was leading to EINVAL errors
    because it was being wound on non-existent shards (those blocks that
    fall in the hole region). loc->inode was NULL in these cases and
    dht_unlink used to fail the FOP with EINVAL for failure to fetch
    cached subvol for the inode.
    
    The fix involves winding unlink on only those shards whose corresponding
    inodes exist in memory.
    
    Change-Id: I993ff70cab4b22580c772a9c74fc19ac893a03fc
    BUG: 1258334
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12059
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fb8c9b38d8c42ecaf17df6e28c2a97d2cf13fb14
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Aug 31 09:56:02 2015 +0530

    debug/trace: Print total write size in trace_writev
    
    This is some information I find useful while debugging issues
    in shard translator.
    
    Change-Id: Ic35c34c2f52d27b3617fc722dabe558de2056b67
    BUG: 1258311
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12053
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1e0644031c7ac0fa28f0912e951a9238f7bbe8ab
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Aug 12 14:46:29 2015 +0530

    libgfapi : port missing gf_log's to gf_msg
    
    Change-Id: I0c5320c09b4a5ff1e9df61a86ac7bd47c1bb1bbb
    BUG: 1252807
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11891
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b9c730f3960efd454c8363ee39dc144e4c0dc835
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Thu Aug 27 13:10:18 2015 +0530

    cluster/dht: Don't set posix acls on linkto files
    
    Posix acls on a linkto file change the file's permission
    bits and cause DHT to treat it as a non-linkto file.This
    happens on the migration failure of a file on which posix
     acls were set.
    
    The fix prevents posix acls from being set on a linkto
    file and copies them across only after a file has
    been successfully migrated.
    
    Change-Id: Iccf7ff6fba49fe05d691d9b83bf76a240848b212
    BUG: 1247563
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/12025
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit beb7abe8762ad73de104f0707949a09af847464d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Aug 19 16:54:42 2015 +0530

    features/shard: Fix permission issues
    
    This patch does the following:
    * reverts commit b467af0e99b39ef708420d3f7f6696b0ca618512
    * changes ownership on shards under /.shard to be root:root
    * makes readv, writev, [f]truncate, rename, and unlink fops
      to perform operations on files under /.shard with
      frame->root->{uid,gid} as 0.
    
    This would ensure that a [f]setattr on a sharded file
    does not need to be called on all the shards associated with it.
    
    Change-Id: Idcfb8c0dd354b0baab6b2356d2ab83ce51caa20e
    BUG: 1251824
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11992
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b0e125e937cbf4bb02baaa799ff4968a4d1cb1d0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jul 26 11:19:28 2015 +0530

    cluster/afr: Make [f]xattrop metadata transaction
    
    Problem:
    When xlators above afr do [f]xattrop when one of the bricks is down, after the
    brick comes backup, the metadata is not healed because [f]xattrop is not
    considered a transaction.
    
    Fix:
    Treat [f]xattrop as transaction so that changes done by xlators above afr are
    marked for heal when some of the bricks were down at the time of [f]xattrop.
    
    Change-Id: Iea180f9a456509847c3cd8d5d59a0cdc2712d334
    BUG: 1248887
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11809
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit d304916ddf3d6848787c3a668cc36e3395b32069
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Aug 26 09:27:42 2015 +0530

    features/shard: Fix size update for writes at hole region
    
    Change-Id: Iceccef8f3f466c7ffb9991f8eb248b81e7b80efb
    BUG: 1256580
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/12020
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a5f00c1c29f71bd9135bba38bd0602a1e8ce71b7
Author: vmallika <vmallika@redhat.com>
Date:   Thu Aug 27 21:11:53 2015 +0530

    marker: preserve previous dirty flag during update txn
    
    In case if dir has become dirty because of brick crash,
    this dirty flag on disk was getting reset in the
    next update txn.
    
    This patch now gets the dirty flag before setting the flag
    in the update txn and if this value is dirty, it keeps
    the flag dirty, so that inspect_directory can fix the
    dirty dir
    
    Change-Id: Iab2c343dbe19bd3b291adbfeebe6d9785b6bb9e3
    BUG: 1251454
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/12032
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 5b3d64b734f463da3344218c6a76aadddbf9cde4
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat Aug 29 19:07:55 2015 +0530

    event: remove vestigial mutex_unlock from event_dispatch
    
    This was missed erroneously by self in http://review.gluster.org/12004
    
    BUG: 1242421
    Change-Id: Id6cb156fd584704486e49bc4c4a7bdd44a98679f
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/12044
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 368f96700ec2868367104f9451c3e1bc38c97c95
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Jul 22 17:08:02 2015 +0200

    cluster/ec: Allow read fops to be processed in parallel
    
    Currently ec only sends a single read request at a time for a given
    inode. Since reads do not interfere between them, this patch allows
    multiple concurrent read requests to be sent in parallel.
    
    Change-Id: If853430482a71767823f39ea70ff89797019d46b
    BUG: 1245689
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/11742
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 44e58a9385b0661c7015b317669c01c699ee9a3e
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Jul 15 16:37:37 2015 +0530

    ec : trusted.ec.version xattr of all root directories of all bricks should be same.
    
    Problem:
    After replacing the brick using "replace-brick" command and running "heal
    full", the version of the root directory of the newly added brick is not
    getting healed. heal starts running on the dentries of the root but does not
    run on root directory.
    
    Solution:
    Run heal on root directory.
    
    Change-Id: Ifd42a3fb341b049c895817e892e5b484a5aa6f80
    BUG: 1243382
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/11676
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit fd47635a4ffab621a2357c99cd1edd0482940bd5
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Wed Aug 26 08:28:59 2015 +0530

    gluster/cli: snapshot delete all does not work with xml
    
    Problem: snapshot delete all command fails with --xml option
    Fix: Provided xml support for delete all command
    
    Change-Id: I77cad131473a9160e188c783f442b6a38a37f758
    BUG: 1257533
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/12027
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit 31a36dca20a976b143cc5c970e115d8d36df847a
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Tue Aug 11 18:17:31 2015 +0530

    glusterd: probing a new node, which is part of another cluster should give error
    
    If user try to add node to extant cluster using "gluster peer probe \
    <ip/hostname>" command then command is failing but its not giving
    proper cause of failure.
    
    This fix will take control of proper error message during peer probe
    with already extant cluster.
    
    Change-Id: I4f993e78c0e1b3e061153b984ec5e9b70085aef5
    BUG: 1252448
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11884
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit e55579bdb1d04cca29f3e87427de5f2a5ab5e9b4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 2 16:39:35 2015 +0530

    fd: Do fd_bind on successful open
    
    - fd_unref should decrement fd->inode->fd_count only if it is present in the
    inode's fd list.
    - successful open/opendir should perform fd_bind.
    
    Change-Id: I81dd04f330e2fee86369a6dc7147af44f3d49169
    BUG: 1207735
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11044
    Reviewed-by: Anoop C S <anoopcs@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit dedf2bde88020adbabb80204830878f060fa614c
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Aug 28 14:27:20 2015 +0530

    event-epoll: Use pollers[] to check if event_pool_dispatch was called
    
    BUG: 1242421
    Change-Id: I1a0044653f15d33f89ffe16edc5baba40393dec3
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/12004
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit bd9dd34700de63f96b9fc65125d539b2c16fa6bf
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Aug 26 15:24:39 2015 +0530

    mount/fuse: Log ENODATA as DEBUG in {f}removexattr
    
    Logging ENODATA errors for {f}removexattr at a higher loglevel does not
    add a lot of value and causes a log message flood as per multiple reports.
    
    Added a new cbk, fuse_removexattr_cbk() to be used with removexattr fops.
    ENODATA now gets logged at loglevel DEBUG in fuse_removexattr_cbk(). This also
    prevents more conditional checks in the common fuse_err_cbk() callback.
    
    Change-Id: I1585b4d627e0095022016c47d7fd212018a7194b
    BUG: 1257110
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/12015
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 7a27810aecce6e014100dbbc3c7961d769082c1e
Author: vmallika <vmallika@redhat.com>
Date:   Mon Aug 24 08:07:14 2015 +0530

    cli: on error invoke cli_cmd_broadcast_response function in separate thread
    
    There is a problem in current CLI framework
    CLI holds the lock when processing command.
    When processing quota list command, below sequence of steps executed in the
    same thread and causing deadlock
    
    1) CLI holds the lock
    2) Send rpc_clnt_submit request to quotad for quota usage
    3) If quotad is down, rpc_clnt_submit invokes cbk function with error
    4) cbk function cli_quotad_getlimit_cbk tries to hold lock to broadcast
       the results and hangs, because same thread has already holding the lock
    
    This patch fixes the problem by creating seperate thread for
    broadcasting the result
    
    Change-Id: I53be006eadf6aaf348083d9168535530d70a8ab3
    BUG: 1242819
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11990
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 4ac8ba045215a103cbac825b2b70b571133c8ec4
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Aug 28 10:46:11 2015 +0530

    tests: Mark bug-1238706-daemons-stop-on-peer-cleanup.t as bad
    
    This test fails frequently. Use bug number 1257792 when you
    move this test out of bad_tests.
    
    Change-Id: Ib65f22096dc9af131c4d2f38b59a857c549a674a
    BUG: 1257792
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/12036
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>

commit 6ad05cd4b7995a3791a9e45ce03dc31641e8d78f
Author: vmallika <vmallika@redhat.com>
Date:   Mon Aug 24 13:14:59 2015 +0530

    posix: xattrop 'GF_XATTROP_GET_AND_SET' implementation
    
    GF_XATTROP_GET_AND_SET stores the existing xattr
    value in xdata and sets the new value
    
    xattrop was reusing input xattr dict to set the results
    instead of creating new dict.
    This can be problem for server side xlators as the inout dict
    will have the value changed.
    
    Change-Id: I43369082e1d0090d211381181e9f3b9075b8e771
    BUG: 1251454
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11995
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b883f937cc98d2b659de5c3eb1d12306df19aca3
Author: vmallika <vmallika@redhat.com>
Date:   Thu Aug 20 12:01:57 2015 +0530

    marker: fix log when loc.parent and inode gfid is NULL
    
    This patch does the following
    
    1) Set loc.parent if it is NULL
       Don't log warning in txn if parent is NULL
    2) Don't initiate txn when inode gfid is NULL
    3) optimize invoking dirty txn with status flag
    
    Change-Id: I67dd9e6268014b0b257c136e951e6ded0a2e911f
    BUG: 1251454
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11863
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9e51aa646fdc5840b6fa9b12b35c5cc2af274c3c
Author: Sakshi <sabansal@redhat.com>
Date:   Thu Jul 16 14:31:03 2015 +0530

    dht : lock on subvols to prevent lookup vs rmdir race
    
    There is a possibility that while an rmdir is completed on
    some non-hashed subvol and proceeding to others. A lookup
    selfheal can recreate the same directory on those subvols
    for which the rmdir had succeeded. The fix is to take a
    blocking inodelk on the subvols before starting rmdir.
    Since selfheal requires lock on all subvols, if an rmdir
    is in progess acquiring locks will fail and vice versa.
    
    Change-Id: I841a44758c3b88f5e04d1cb73ad36e0cac9fdabb
    BUG: 1245065
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/11725
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit cf3d6f14ae031ba2f5269cea6dbf80e60d00cce5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jul 16 18:23:36 2015 +0530

    tools/glusterfind: Do not show session corrupted if no status file
    
    When a glusterfind session is created it creates session directories
    in all the nodes which are part of the Volume. But session status
    file only present in initiated node.
    
    Show Session corrupted only if status file exists and invalid content.
    
    Change-Id: I8443c0335b872645b54c0aa77d9893dbe2589c92
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1243838
    Reviewed-on: http://review.gluster.org/11699
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 0c47ef608b22ce719a0238c292cd8550986ad0cd
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Fri Jul 17 15:51:22 2015 +0530

    tools/glusterfind: Prepend prefix in case of delete
    
    In case of delete operation alone, output prefix adding
    was not handled earlier.
    Output prefix is added now.
    
    Change-Id: Ia91444dddbff501b26a864f6185ca4c0aaf4c802
    BUG: 1244144
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/11712
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Milind Changire <mchangir@redhat.com>

commit a26dbb38acdb2ec5fe16068caee189709faae76e
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Aug 12 15:29:31 2015 +0530

    protocol/server : porting missing gf_log's to gf_msg
    
    Change-Id: I8818931fafea3c013551a5de23a9f77c81164841
    BUG: 1252808
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11895
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e883e98998404a9e1ef18516d88520cfe2451b3f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Mar 17 19:57:47 2015 +0530

    snapshot:cleanup snaps during unprobe
    
    When doing an unprobe, the volume that doesnot
    contain any brick of the particular node will be
    deleted. So the snaps associated with that volume
    should also delete
    
    Change-Id: I9f3d23bd11b254ebf7d7722cc1e12455d6b024ff
    BUG: 1203185
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9930
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit c9d462dc8c1250c3f3f42ca149bb062fe690335b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jul 21 09:57:43 2015 +0530

    glusterd: Don't allow remove brick start/commit if glusterd is down of the host of the brick
    
    remove brick stage blindly starts the remove brick operation even if the
    glusterd instance of the node hosting the brick is down. Operationally its
    incorrect and this could result into a inconsistent rebalance status across all
    the nodes as the originator of this command will always have the rebalance
    status to 'DEFRAG_NOT_STARTED', however when the glusterd instance on the other
    nodes comes up, will trigger rebalance and make the status to completed once the
    rebalance is finished.
    
    This patch fixes two things:
    1. Add a validation in remove brick to check whether all the peers hosting the
    bricks to be removed are up.
    
    2. Don't copy volinfo->rebal.dict from stale volinfo during restore as this
    might end up in a incosistent node_state.info file resulting into volume status
    command failure.
    
    Change-Id: Ia4a76865c05037d49eec5e3bbfaf68c1567f1f81
    BUG: 1245045
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11726
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 734e9ed2827c39336e1fab26e2db3ea987976ce1
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Aug 24 12:04:54 2015 +0530

    tests: Fix corruption of files on NetBSD
    
    This is one more attempt to eliminate corruption
    of files by our tests scripts on NetBSD.
    
    Changes done:
    1. Have every local variable with a unique name.
    2. Change date format to match with gluster's.
    3. Pass the parameters to G_LOG without interpretation,
       hence the change from $* to $@.
    
    Change-Id: I833a93555da93179a1b39a9e4e7086216c335c3d
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11993
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit 116e3dd3d7687a785b0d04a8afd11619d85ff4ec
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed May 13 14:48:42 2015 +0530

     glusterd : Display status of Self Heal Daemon for disperse volume
    
     Problem : Status of Self Heal Daemon is not
     displayed in "gluster volume status"
    
     As disperse volumes are self heal compatible,
     show the status of self heal daemon in gluster
     volume status command
    
    Change-Id: I83d3e6a2fd122b171f15cfd76ce8e6b6e00f92e2
    BUG: 1217311
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/10764
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 36349fa250ace6109002dfa41305d9dcd54ce0a9
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Aug 3 17:09:13 2015 +0530

    cluster/afr : Examine data/metadata readable for read-subvol
    During lookup and discover, currently read_subvol is based
    only on data_readable. read_subvol should be decided based
    on both data_readable and metadata_readable.
    
    Credits to Ravishankar N for the logic of afr_first_up_child
    from http://review.gluster.org/10905/ .
    
    Change-Id: I98580b23c278172ee2902be08eeaafb6722e830c
    BUG: 1240244
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11551
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f3c7e6eaa9b14b89c1d58c0edcb5664f28914437
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Aug 4 18:37:47 2015 +0530

    afr: modify afr_txn_nothing_failed()
    
    In an AFR transaction, we need to consider something as failed only if the
    failure (either in the pre-op or the FOP phase) occurs on the bricks on which a
    transaction lock was obtained.
    
    Without this, we would end up considering the transaction as failure even on the
    bricks on which the lock was not obtained, resulting in unnecessary fsyncs
    during the post-op phase of every write transaction for non-appending writes.
    
    Change-Id: Iee79e5d85dc7b4c41459d8bdd04a8454bdaf9a9d
    BUG: 1250170
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11827
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 255b4ba477f5163b59efee1c9f62845eb86067a2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Aug 24 16:20:06 2015 +0530

    tests: add arbiter-statfs.t/tier.t to bad tests
    
    Recent regression links for proof:
    http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/9611/consoleFull
    https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/9616/consoleFull
    https://build.gluster.org/job/rackspace-regression-2GB-triggered/13613/consoleFull
    
    Filed https://bugzilla.redhat.com/show_bug.cgi?id=1256588 for tracking
    arbiter-statfs.t spurious failure and
    https://bugzilla.redhat.com/show_bug.cgi?id=1231268 is going to track tier.t's
    issue.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1231268
    Change-Id: I61dc8f3d3366b2c784e3ce82bd88900f2651cbef
    BUG: 1254127
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/12005
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 90c7c30c3aa9417793ae972b2b9051bc5200e7e4
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Aug 24 03:04:41 2015 -0400

    cluster/dht: avoid mknod on decommissioned brick
    
    Change-Id: I8c39ce38e257758e27e11ccaaff4798138203e0c
    BUG: 1256243
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/11998
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 97bae6371b5e841f03a61d6700033f40afd5cdc7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Aug 17 10:29:19 2015 +0000

    heal: Add check for healing directories in split-brain
    
    1. Healing using  `bigger-file' option does not make much sense for directories,
    hence disallow it and notify the user.
    2. Healing using 'source-brick' option for directories performs a conservative
    merge. Notify the user about it.
    
    Change-Id: I0acff7b438bdb256615ed0f40d45694f37a77dd5
    BUG: 1254167
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11937
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8e0bf30dc40fed45078c702dec750b5e8bbf5734
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Thu Jul 2 18:23:51 2015 +0530

    glusterd: stop all the daemons services on peer detach
    
    Currently glusterd is not stopping all the deamon service on peer detach
    
    With this fix it will do peer detach cleanup properlly and will stop all
    the daemon which was running before peer detach on the node.
    
    Change-Id: Ifed403ed09187e84f2a60bf63135156ad1f15775
    BUG: 1255386
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11509
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit d5e03b7f02f68b3a9aaccf586e1f6ed901224ba7
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jul 30 16:37:45 2015 +0530

    snapshot: Make fops static for correct resolution of symbols
    
    Few of the snapshot fops (like 'svc_lookup') may not get resolved
    while using dynamic loading as there could be other libraries(like libntirpc)
    with same routine names. Making them static to resolve the same.
    
    Change-Id: I6577bf3705864f5583425c94427b4e1025a59bcd
    BUG: 1248669
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11805
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1ead86a8bcbfe4045729466e4b98f765f3c13c8d
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Aug 11 16:00:47 2015 +0530

    libgfapi: adding 'follow' flag to glfs_h_lookupat()
    
    Previously glfs_h_lookupat won't follow the symlink, this patch
    introduces new flag `follow` which will resolve the same. Applications
    linking against the new library will need to use the new glfs_h_lookupat
    API call.
    
    In order to stay compatible with existing binaries that use the previous
    glfs_h_lookupat() function, the old symbol needs to stay available.
    
    Verification that there are two versions of glfs_h_lookupat:
    
      $ objdump -T /usr/lib64/libgfapi.so.0 | grep -w glfs_h_lookupat
      0000000000015070 g    DF .text  000000000000021e  GFAPI_3.7.4 glfs_h_lookupat
      0000000000015290 g    DF .text  0000000000000008 (GFAPI_3.4.2) glfs_h_lookupat
    
    Testing with a binary (based on anonymous_fd_read_write.c from ./tests/)
    that was linked against the old library:
    
      $ objdump -T ./lookupat | grep -w glfs_h_lookupat
      0000000000000000      DF *UND*  0000000000000000  GFAPI_3.4.2 glfs_h_lookupat
    
    Enable debugging for 'ld.so' so that we can check that the GFAPI_3.4.2
    version of the symbol gets loaded:
    
      $ export LD_DEBUG_OUTPUT=lookupat.ld.log LD_DEBUG=all
      $ ./lookupat
      $ grep -w glfs_h_lookupat lookupat.ld.log.2543
      2543:     symbol=glfs_h_lookupat;  lookup in file=./lookupat [0]
      2543:     symbol=glfs_h_lookupat;  lookup in file=/lib64/libgfapi.so.0 [0]
      2543:     binding file ./lookupat [0] to /lib64/libgfapi.so.0 [0]: normal symbol `glfs_h_lookupat' [GFAPI_3.4.2]
    
    Change-Id: I8bf9b1c19a0585f681bc1a7f84aad1ccd0f75f6a
    BUG: 1252410
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11883
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 5044b20a9fbe0f49b7929d2282890a7351df344d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Aug 5 15:56:53 2015 +0530

    snapshot: Fix snapshot info's xml output
    
    Display description field with (null) if
    no description is present for the snapshot, instead
    of removing the field altogether.
    
    Change-Id: I965b08cd6e54eea56c32e2712fab7daa8a663f11
    BUG: 1250387
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11834
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 6cb78f8b7444ad7f216c976700c28a7d59f6b976
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Aug 5 13:49:41 2015 +0530

    snapshot/scheduler: Check if volume exists before adding/editing schedules
    
    Before adding or editing a scheduler, check if the volume name provided
    in the schedule, exists in the cluster or not.
    
    Added return code VOLUME_DOES_NOT_EXIST(17) for the same.
    
    Change-Id: Ia3fe3cc1e1568ddd10f9193bbf40a098f0fe990a
    BUG: 1213349
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11830
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 69942154e197d753580b74cc7f8e6bce470ee673
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Aug 20 14:40:29 2015 +0530

    snapshot: Log deletion of snapshot, during auto-delete
    
    When auto-delete is enabled, and soft-limit is reached,
    on creation of a snapshot, the oldest snapshot for that
    volume is deleted.
    
    Displaying a warning log before deleting the oldest
    snapshot.
    
    Change-Id: I75f0366935966a223b63a4ec5ac13f9fe36c0e82
    BUG: 1255310
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11963
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 6bd770c0314645e5309083b75991b243e54b2838
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Aug 14 18:28:08 2015 +0530

    snapshot/scheduler: Output correction of initialisation
    
    Change-Id: I4a6e00805da7b254b8b08e7bb142960fb6c64923
    BUG: 1218164
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11924
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 036ef63536d749b47b1c719bd92ff382ad75fb8b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Aug 5 17:19:29 2015 +0200

    SSL improvements: do not fail if certificate purpose is set
    
    Since glusterfs shares the same settings for client-side
    and server-side of SSL, we need to ignore any certificate
    usage specification (SSL client vs SSL server), otherwise
    SSL connexions will fail with 'unsupported cerritifcate"
    
    BUG: 1247152
    Change-Id: I7ef60271718d2d894176515aa530ff106127bceb
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/11840
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1626fb105c99ef623be3687f3f48d9247ab9b7c4
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Jun 16 20:35:46 2015 +0530

    dht: block/handle create op falling to decommissioned brick
    
    Problem:
    Post remove-brick start till commit phase, the client layout
    may not be in sync with disk layout because of lack of lookup.
    Hence,a create call may fall on the decommissioned brick.
    
    Solution:
    Will acquire a lock on hashed subvol. So that a fix-layout or
    selfheal can not step on layout while reading the layout.
    
    Even if we read a layout before remove-brick fix-layout and the
    file falls on the decommissioned brick, the file should be
    migrated to a new brick as per the fix-layout.
    
    Change-Id: If84a12ec34f981adb2b9b224e80f535cfe5bf9f2
    BUG: 1232378
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/11260
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit a586b30c1bd968d23562406cefbb76b82a0e236c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Aug 12 15:25:03 2015 +0530

    features/bitrot: Fix scrubber frequency set
    
    When bitrot is configured on multiple volumes
    in a cluster and scrubber-frequency is changed
    for one volume, it is resetting frequency for
    all other volumes w.r.t to its scrubber-frequency.
    This should not happen. Changing scrubber-frequency
    should affect only that volume on which it is set.
    This patch fixes the issue.
    
    Also restricted the logs to the configure volume.
    
    Change-Id: I90d6e864b131e3d8dd4010079a00f924032f2098
    BUG: 1252825
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11897
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit d80537d8e588da57db609332c2d89873e0a368ca
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Aug 13 14:39:58 2015 +0530

    event: add dispatched flag to know if event_dispatch was called
    
    This is important for glusterfs processes that choose to reconfigure
    no. of event-threads (a.k.a epoll worker-threads) before they call
    event_dispatch on the event_pool. glusterd needs this today.
    
    Change-Id: Ia8df3c958545324472262c555ed84b71797f002e
    BUG: 1242421
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/11911
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e4cefd6c5915dd47c6b42098236df3901665f93a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Aug 13 18:33:08 2015 +0530

    afr: launch index heal on local subvols up on a child-up event
    
    Problem:
    When a replica's child goes down and comes up, the index heal is
    triggered only on the child that just came up. This does not serve the
    intended purpose as the list of files that need to be healed
    to this child is actually captured on the other child of the replica.
    
    Fix:
    Launch index-heal on all local children of the replica xlator which just
    received a child up. Note that afr_selfheal_childup() eventually calls
    afr_shd_index_healer() which will not run the heal on non-local
    children.
    
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    
    Change-Id: Ia23e47d197f983c695ec0bcd283e74931119ee55
    BUG: 1253309
    Reviewed-on: http://review.gluster.org/11912
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit aa1b166984657d53e68a2c4cbd16d2e46c12436b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Aug 21 10:54:39 2015 +0530

    tests: remove unwanted tests from volume-snapshot.t
    
    volume-snapshot.t failspuriously because of having additional test cases
    which restarts glusterd and they are really not needed as far as the test
    coverage is concerned. Currently glusterd doesn't have a mechanism to indicate
    that volumes handshaking has been completed or not, due to this even if the peer
    handshaking finishes and all the peers are back to the cluster there could be a
    case where any command which accesses the volume structure might end up in
    corruption as volume handshaking is still in progress. This is because of volume
    list is still not been made URCU protected.
    
    Change-Id: Id8669c22584384f988be5e0a5a0deca7708a277d
    BUG: 1255599
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11972
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b9e87f39386fc9c591c7698357c2899afc255b95
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Thu Jul 30 18:29:41 2015 +0530

    quota :display the size of soft limit percentage
    
    Display the size equivalent to the soft limit percentage
    in gluster v quota <volname> list <path> and
    gluster v quota <volname> list-objects <path> command
    
    Change-Id: I31ee82e9e836068348cf9458dcaf13f043d9fd87
    BUG: 1248521
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11808
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6cb73b4fe798b7bf3aface0aac2a4e6c7c618c0e
Author: Gaurav Kumar Garg <garg.gaurav52@gmail.com>
Date:   Thu Aug 20 16:12:53 2015 +0530

    bitrot: Scrubber log should mark bad file as a ALERT in the scrubber log
    
    If bad file detected by scrubber then scrubber should log that bad
    file as a ALERT message in scrubber log.
    
    Change-Id: I410429e78fd3768655230ac028fa66f7fc24b938
    BUG: 1240218
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11965
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 53e57a62ab4254f131c1d02b70fcb9b97f33306c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jul 1 15:56:58 2015 +0530

    protocol/server: forget the inodes which got ENOENT in lookup
    
    If a looked up object is removed from the backend, then upon getting a
    revalidated lookup on that object ENOENT error is received. protocol/server
    xlator handles it by removing dentry upon which ENOENT is received. But the
    inode associated with it still remains in the inode table, and whoever does
    nameless lookup on the gfid of that object will be able to do it successfully
    despite the object being not present.
    
    For handling this issue, upon getting ENOENT on a looked up entry in revalidate
    lookups, protocol/server should forget the inode as well.
    
    Though removing files directly from the backend is not allowed, in case of
    objects corrupted due to bitrot and marked as bad by scrubber, objects are
    removed directly from the backend in case of replicate volumes, so that the
    object is healed from the good copy. For handling this, the inode of the bad
    object removed from the backend should be forgotten. Otherwise, the inode which
    knows the object it represents is bad, does not allow read/write operations
    happening as part of self-heal.
    
    Change-Id: I23b7a5bef919c98eea684aa1e977e317066cfc71
    BUG: 1238188
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11489
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 4efc8ea17f8452cf5a5f3a504419c1269d332d79
Author: vmallika <vmallika@redhat.com>
Date:   Sun Jul 12 08:49:49 2015 +0530

    quota/marker: fix inode quota with rename
    
    There are three problems with marker-rename which
    is fixed in this patch
    
    Problem 1)
    1) mq_reduce_parent_size is not handling inode-quota contribution
    2) When dest files exists and IO is happening
       Now renaming will overwrite existing file
       mq_reduce_parent_size called on dest file
       with saved contribution, this can be
       a problem is IO is still happening
       contribution might have changed
    
    Problem 2)
    There is a small race between rename and in-progress write
    Consider below scenario
    1) rename FOP invoked on file 'x'
    2) write is still in progress for file 'x'
    3) rename takes a lock on old-parent
    4) write-update txn blocked on old-parent to acquire lock
    5) in rename_cbk, contri xattrs are removed and contribution is deleted and
       lock is released
    6) now write-update txn gets the lock and updates the wrong parent
       as it was holding lock on old parent
       so validate parent once the lock is acquired
    
    Problem 3)
    when a rename operation is performed, a lock is
    held on old parent. This lock is release before
    unwinding the rename operation.
    This can be a problem if there are in-progress
    writes happening during rename, where update txn
    can take a lock and update the old parent
    as inode table is not updated with new parent
    
    Change-Id: Ic3316097c001c33533f98592e8fcf234b1ee2aa2
    BUG: 1240991
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11578
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d290dc62e474cfe4a305f503dff815c73d3f2578
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Aug 13 11:49:57 2015 +0530

    protocol-client/server: Minor logging improvements for better debugging
    
    Adding some log messages to protocol client and server to
    ease the debugging process.
    
    Change-Id: I84a05fcde7189d6e6ad5c37c1bbffb148d123517
    BUG: 1227667
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/11903
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 963ce60e0d5edc418ae3cdc954fca350a5e3a131
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 19 02:43:00 2015 -0400

    libgfapi: non-default symbol version macros are incorrect
    
    default symbol versions are in form glfs_h_lookupat@@GFAPI_2.7.4,
    versus old, non-default versions are in the form glfs_h_lookup@GFAPI_2.4.2
    
    I.e. "@@" versus "@"
    
    Change-Id: I88a6b129558c0b3a6064de7620b3b20425e80bc9
    BUG: 1254863
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11955
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 454bd09b8befc27552591855a8d02a0ad19877d9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jun 18 00:21:59 2015 +0200

    rpm: include required directory for glusterfind
    
    The directory was marked as %ghost, which causes the following
    installation failure:
    
      Error unpacking rpm package glusterfs-server-3.8dev-0.446.git45e13fe.el7.centos.x86_64
      error: unpacking of archive failed on file /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post.py;5581f20e: cpio: open
    
    Also, *all* Python files should be part of the RPM package. This
    includes generated .pyc and .pyo files.
    
    BUG: 1225465
    Change-Id: Iee74905b101912c4a845257742c470c3fe42ce2a
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/11298
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 470a50b1d5017f015a1f3f3ea65a33902a02ffea
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Aug 10 19:10:21 2015 +0530

    features/shard: Ensure shards are owned by the same owner/group as the original file
    
    Change-Id: Id759af8f3ff5fd8bfa9f8121bab25722709d42b7
    BUG: 1251824
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11874
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a4bbb71e91744ed387606dd4eb5bee55cf86b079
Author: N Balachandran <nbalacha@redhat.com>
Date:   Tue Aug 18 13:37:12 2015 +0530

    cluster/tier : Use dht_* versions for xlator_fops
    
    The tier xlator was using the default_* versions
    for some xlator_fops. Changed to use the dht_*
    versions for all xlator_fops
    
    Change-Id: I8252fb3911b8a48a55e9eee42b89bd66bbacf799
    BUG: 1254451
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/11948
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 68fb056c28b15e851bd7797963efad411c848612
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Aug 17 14:15:05 2015 +0530

    tests: Moving ./tests/basic/mount-nfs-auth.t and
     ./tests/geo-rep/georep-basic-dr-rsync.t to bad test
    
    Till the spurious regression failures are fixed, moving
    these tests to bad test so as to unblock the NetBSD regression
    
    Also added ./tests/geo-rep/georep-basic-dr-tarssh.t to bad test.
    
    Change-Id: I8c0cb355a7832a6a794d2d3550d304947e91e936
    BUG: 1254127
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11934
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit a462e1f3146ad1c0e1099bbc4d0f5269a1c02545
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Jul 3 15:27:15 2015 +0530

    tiering/glusterd: start tier daemon during volume start
    
    Tier daemon should always run with tier volume. If volume
    is stopped and started again, we manually need to start
    the tier-daemon, instead this patch will automatically trigger
    tier process along with volume start.
    
    A snapshot restored volume will not have node_state_info,
    so we need to create and store it dynamically
    
    Change-Id: I659387c914bec7a1b6929ee5cb61f7b406402075
    BUG: 1238593
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11525
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 37353199483f2052b50e9d0b35257c27a08f3da4
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Aug 5 16:36:06 2015 +0530

    xml output: Fix non-uniform opErrstr xml output
    
    Display <opErrstr/> in case of no operrstr for
    all xml output of gluster commands.
    
    Change-Id: Ie16f749f90b4642357c562012408c434cd38661f
    BUG: 1245895
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11835
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 289d00369f0ddb78f534735f7d3bf86268adac60
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Fri Aug 7 12:37:52 2015 +0200

    cluster/ec: Fix write size in self-heal
    
    Self-heal was always using a fixed block size to heal a file. This
    was incorrect for dispersed volumes with a number of data bricks not
    being a power of 2.
    
    This patch adjusts the block size to a multiple of the stripe size
    of the volume. It also propagates errors detected during the data
    heal to stop healing the file and not mark it as healed.
    
    Change-Id: I9ee3fde98a9e5d6116fd096ceef88686fd1d28e2
    BUG: 1251446
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/11862
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7641eb8b469a6dd4db6db59d2a5ef4d5a65e1a61
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Aug 5 12:07:48 2015 +0530

    rdma:restore device linked list structure in case of failure
    
    We maintain a linked list strcture to store device information,
    and maintain head in a ctx variable. A new device will be added
    at the beginning of list. But if the device creation failed, then
    we need to adjust the linked list to proper state.
    
    Change-Id: I07cefd3b808d8973a915728b3ba7f2955d29c92a
    BUG: 1250297
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11829
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit fdbff3c4d34296825c2aac023cb07519d922903d
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Jun 25 17:40:18 2015 +0530

    dht: return non NULL xattr,xdata for ret >= 0
    
    Change-Id: I4a3dd8c00894ceeed4af77df2d960f372281a03b
    BUG: 1235989
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/11409
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit db4e3a371c66c400b3cb95d4e7701625bef4ac95
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue Aug 11 13:45:26 2015 +0530

    tests: call cleanup on receiving external signals INT, TERM and HUP
    
    problem:
    when executing testcases manually, some time we may want to terminate the
    testcase execution in between due to various reasons.
    Existing testcase flow has no mechanism to call cleanup before they terminate
    abnormally, hence we endup with volume setups and mount points uncleaned.
    
    Solution:
    This patch traps such kind of abnormal terminations and calls 'cleanup'
    function soon after they are caught and then terminates the testcases
    with appropriate status..
    
    $ ./tests/basic/mount-nfs-auth.t
    1..87
    =========================
    TEST 1 (line 8): glusterd
    ok 1
    RESULT 1: 0
    =========================
    TEST 2 (line 9): pidof glusterd
    ok 2
    RESULT 2: 0
    =========================
    TEST 3 (line 10): gluster -mode=script --wignore volume info
    No volumes present
    ok 3
    RESULT 3: 0
    ^C
    received external signal --INT--, calling 'cleanup' ...
    
    $ glusterd && gluster vol status
    No volumes present
    
    Change-Id: Ia51a850c356e599b8b789cec22b9bb5e87e1548a
    BUG: 1252374
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11882
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 0ad26041fbf65ab36856a0ad178c32e51bf87319
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Aug 5 19:20:04 2015 +0530

    dht/tier :rename fails with EBUSY
    
    When the files was in hot tier and the look up was done already, then
    hashed and cached subvolume will be hot-tier. Once the file is moved
    from hot-tier to cold-tier, then subsequent lookup will send a
    revalidate lookup to hot-tier and it will find out that the file was
    actually moved and there is only link in the cached subvolume. So dht
    will return an ESTALE to fuse. Upon receiving ESTALE for a lookup, fuse
    will create a new inode and sent a fresh lookup. This lookup will be
    successful, and it will locate the file properly. Then fuse try to link
    the inode, but the older inode was already there in inmemory inode cache
    with same gfid and that is also shared with fuse kernal. So inode_link
    will return the older ionode itself. So the subsequent rename fop will
    come to gluster with the older inode. From dht_rename, we will take a
    lock on the inode and after successful inodelk on inode dht will send
    lookup before creating a link. this lookup will again find out that the
    file is a link file, and then dht will think that file is
    migrating/migrated in the mean time, and will send EBUSY.
    
    Change-Id: Ib3a01e5b1d7f64514b04bb6234026d049f082679
    BUG: 1248306
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11768
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 6e055b7d7355cadbbf559ad4bed23872aa1743df
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Aug 11 15:36:26 2015 -0400

    cluster/tier: fix 64 bit issue with sql query using times
    
    We overflowed when converting seconds to usecs in preperation for
    sql queries. The fix uses uint64_t throughout including subexpressions.
    
    Change-Id: I59bdb742197400dede97f54735b52030920b0d19
    BUG: 1231268
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11885
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit fb4955b796ab2f3236e00686ecc99e792f9c0f8b
Author: vmallika <vmallika@redhat.com>
Date:   Fri Aug 7 15:51:53 2015 +0530

    posix: posix_make_ancestryfromgfid shouldn't log ENOENT
    
    posix_make_ancestryfromgfid shouldn't log ENOENT
    and it should set proper op_errno
    
    Change-Id: I8a87f30bc04d33cab06c91c74baa9563a1c7b45d
    BUG: 1251449
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11861
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 15796b3d3efb998bdb5413ac0ad1af1903cae493
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Tue Jul 14 18:23:16 2015 +0530

    cli: changing the assignment to comparison operator on an if statement
    
    CID: 1124702
    
    Change-Id: I6366834224a8176824070150b7f2af76b4d65b7f
    BUG: 789278
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/11665
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit f7668938cd7745d024f3d2884e04cd744d0a69ab
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat Jun 27 11:04:25 2015 +0530

    rpc: add owner xlator argument to rpc_clnt_new
    
    The @owner argument tells RPC layer the xlator that owns
    the connection and to which xlator THIS needs be set during
    network notifications like CONNECT and DISCONNECT.
    
    Code paths that originate from the head of a (volume) graph and use
    STACK_WIND ensure that the RPC local endpoint has the right xlator saved
    in the frame of the call (callback pair). This guarantees that the
    callback is executed in the right xlator context.
    
    The client handshake process which includes fetching of brick ports from
    glusterd, setting lk-version on the brick for the session, don't have
    the correct xlator set in their frames. The problem lies with RPC
    notifications. It doesn't have the provision to set THIS with the xlator
    that is registered with the corresponding RPC programs. e.g,
    RPC_CLNT_CONNECT event received by protocol/client doesn't have THIS set
    to its xlator. This implies, call(-callbacks) originating from this
    thread don't have the right xlator set too.
    
    The fix would be to save the xlator registered with the RPC connection
    during rpc_clnt_new. e.g, protocol/client's xlator would be saved with
    the RPC connection that it 'owns'. RPC notifications such as CONNECT,
    DISCONNECT, etc inherit THIS from the RPC connection's xlator.
    
    Change-Id: I9dea2c35378c511d800ef58f7fa2ea5552f2c409
    BUG: 1235582
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/11436
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 546f66f546a9c9f63c4ee7d3f28fc3a494305263
Author: Sakshi <sabansal@redhat.com>
Date:   Fri Jun 12 19:42:30 2015 +0530

    dht: remove 'null' for directory/file path from brick log for many operations
    
    Change-Id: I39cd2089240c0ad62b749f176847cc5337e57f73
    BUG: 1231264
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/11206
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 830ad21fa8100eb15586eee771274d6d3caf4347
Author: Sakshi <sabansal@redhat.com>
Date:   Wed May 20 17:33:57 2015 +0530

    dht : updating return value for layout set function
    
    Change-Id: I7fd89e00b418391afe0a13c2033919c979cc8bbb
    BUG: 789278
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/10869
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 1d0968d5acd10188d4684bfb1d345c72ccefa75a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Aug 6 16:53:22 2015 +0530

    features/bitrot: Fix rescheduling scrub-frequency
    
    While rescheduling scrub frequency, boot time of
    the brick was considered where it is not required
    and also delta is calculated using unsigned int
    resulting in the loss of fractional part leading to
    wrong scrub frequency. Boot time is completely
    removed and delta calculation is simplified.
    
    Change-Id: If54697389f663afc86408dc8a01a3ea07e00f2dc
    BUG: 1251042
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11853
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit f7e14df044ee5091bc89ad7ad2a7d22092b50be8
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Sat Aug 8 01:53:52 2015 +0530

    tests: Disable trace mode in G_LOG
    
    We run tests in trace mode(set -x) when
    re-running failed tests. G_LOG is a util
    function and it need not be executed in
    trace mode.
    
    Change-Id: I5490bdcacef6856c5501272c8173828c30aaf373
    BUG: 1251592
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11865
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit b5a98df6343da6229b1b102883d8e992cd4a55a5
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Jul 13 18:45:11 2015 +0530

    tier/libgfdb : Setting Freq counters of un-selected files to zero
    
    Change Time Recorder increments the write/read frequency counters
    on a read or write of a file, if the "features.record-counters" is
    "on". It is the responsibility of the tiering migrator to reset
    these counters to zero for un-selected files to reset them to zero
    as frequency counters are function of promotion/Demotion cycles.
    If the counters are not set to zero then,
    
    1) the counters may overflow in the DB
    2) The file may be wrongly promoted or demoted.
    
    This fix will reset the freq counters of un-selected files to zero
    after promotion/demotion frequency.
    
    Change-Id: Ideea2c76a52d421a7e67c37fb0c823f552b3da7a
    BUG: 1242504
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/11648
    Tested-by: Joseph Fernandes
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit e8ea08d9a9ca9e507919c121b3a2e56fd5f580f4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Aug 6 12:19:23 2015 +0530

    features/shard: Fill inode ctx in readdir(p) callback too
    
    The only place where shard translator was initialising inode ctx
    was lookup callback. But if the inodes are created and linked through
    readdirp, shard_lookup() path _may_ not be exercised before FUSE
    winds other fops on them. Since shard translator does an
    inode_ctx_get() first thing in most fops, an uninitialised ctx could
    cause it to fail the operation with ENOMEM.
    
    The solution would be to also initialise inode ctx if it has not been
    done already in readdir(p) callback.
    
    Change-Id: I3e058cd2a29bc6a69a96aaac89165c3251315625
    BUG: 1250855
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11854
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e65160c5bec78e7385eedf3cf02d9cdcb756db0c
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu Aug 6 09:59:35 2015 -0400

    cluster/tier: fix demotion when cold tier is EC
    
    We did not set the gfid in the loc structure in tier demotion. EC
    has a sanity check which fails FOPs when the loc gfid mismatches
    with the file attribute. When the FOP failed demotion was aborted.
    
    Change-Id: I69022c9ccb135b86e1feea93b01801b6a4100509
    BUG: 1251121
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11855
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 06c3cf61249e05ae1212a43d5fc1db57bad5f718
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Jul 22 15:12:36 2015 +0530

    quota : checking for absolute path in quota command
    
    Currently, if absolute path is not entered in
    "gluster volume quota <vol-name> list <path>",
    it just shows the header (Path Hard-limit Soft-limit...)
    instead of showing an error message.
    
    With this patch, it shows an error to enter the absolute path.
    
    Change-Id: I2c3d34bfdc7b924d00b11f8649b73a5069cbc2dc
    BUG: 1245558
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11738
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c0a4171da69537c1947b68014e5fb732b531ecd9
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Mon Jun 29 15:02:52 2015 +0530

    cluster/dht: Reset source file mode bits on migration failure
    
    DHT rebalance uses the sgid and sticky bits to indicate
    that a file is being migrated. These were not removed if
    the file migration failed.
    The fix resets these bits to the original values.
    
    Change-Id: I9801bfc0bd80c0800251ccd66c1c91a51cffd909
    BUG: 1236512
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/11454
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit dace4bbd0fdce567703a1a8d2d74a0a3f166f334
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu May 28 19:26:00 2015 +0530

    tests: New simple geo-rep regression test suite
    
    This is a new simple regression test suite for
    geo-replication. This is written keeping in mind
    the run time for regression test. The existing
    regression test suite is rigorous one and could
    be run nightly. Hence the existing geo-rep tests
    are being removed as part of this.
    
    Also re-enable geo-rep regression with this patch.
    
    Thanks Aravinda for initial template and plan.
    
    Change-Id: If544ac295eaf67ac66e0b071903cc1096e71d437
    BUG: 1227624
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11058
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 64e6836ac8fb96f38a859eea0d8525cd9bd2693f
Author: Anusha Rao <anusha91rao@gmail.com>
Date:   Mon May 4 12:34:09 2015 +0530

    features/changelog: Porting log messages to new logging framework
    
    Change-Id: Ic7f842acca52908fd88e0796dc90b82650405b25
    BUG: 1194640
    Signed-off-by: Anusha Rao <anusha91rao@gmail.com>
    Reviewed-on: http://review.gluster.org/10532
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 0dcdc8d9d797ed43d305fb3e3437c2576305ac46
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 16 17:54:24 2015 +0530

    glusterd: log improvement in glusterd_peer_rpc_notify
    
    If ping time out is enabled glusterd can receive a disconnect event from a peer
    which has been already deleted resulting into a critical log printed. This patch
    ensures that critical message is logged only when its a connect event.
    
    Change-Id: I67d9aa3f60195e08af7dfc8a42683422aaf90a00
    BUG: 1212437
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10272
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7b44b6c16fb538e5f15a255182de4dee781994a0
Author: Raghavendra Bhat <raghavendra@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@redhat.com>
    Reviewed-on: http://review.gluster.org/11449
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 8d7a4f6b0aa8e63e1a0802e22bcebe96e4e7490f
Author: Pamela Ousley <pousley@redhat.com>
Date:   Mon Aug 10 18:38:00 2015 -0400

    cluster/tier: fixed pattern matching error in tier.t
    
    The check_counters function contained "grep -o '[0-9*]'", which
    was in error. This patch corrects it to "grep -o '[0-9]*'".
    
    This fix was necessary to accommodate for double-digit counters.
    
    Change-Id: Idaa09de4403bf66e741176a7377eba264819ca3b
    BUG: 1252121
    Signed-off-by: Pamela Ousley <pousley@redhat.com>
    Reviewed-on: http://review.gluster.org/11877
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit f550efa2879c02dec4c8f6876a94fcfd95b5bf91
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 7 17:32:29 2015 +0530

    tests: add basic/afr/arbiter-statfs.t
    
    This is a test-case for BZ 1251346
    
    Change-Id: Icbde8d17c823a3f2c98056c14a75f0ef5227b848
    BUG: 1251346
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11864
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 0c9e2446f5beffca97d26ea1fe9816319bde525c
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Jul 23 18:02:10 2015 +0530

    Removing 'legacy' directory from glusterfs doc repo
    
    As per http://www.gluster.org/pipermail/gluster-users/2015-July/022918.html.
    
    Change-Id: Ie1473c967a53a34b6e2b4f4653e3e63ae5ea16fa
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/11748
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 6af535cf4d10fa830bb45ba00269649a78094e40
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Aug 10 14:47:17 2015 +0530

    Removing gluster_find doc
    
    This is already ported to https://github.com/gluster/glusterdocs/tree/master/GlusterFS%20Tools
    and no need for duplicate copy.
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    
    Change-Id: Ie7c3c72b3d7f001ddc863e89b4ad933bda4e2816
    BUG: 1206539
    Reviewed-on: http://review.gluster.org/11870
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 8603ac80218d6161416fd0f3cca511ba09aef2c8
Author: N Balachandran <nbalacha@redhat.com>
Date:   Mon Aug 3 13:57:37 2015 +0530

    glusterd/rebalance: trusted rebalance volfile
    
    Creating the client volfiles with GF_CLIENT_OTHER
    overwrites the trusted rebalance volfile and causes rebalance
    to fail if auth.allow is set.
    Now, we always set the value of trusted-client to GF_CLIENT_TRUSTED
    for rebalance volfiles.
    
    Change-Id: I95eb510256d18dfa9048f96a1aeb71cca4811811
    BUG: 1248415
    Signed-off-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/11819
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit c0da330c32312edc4233fe6f660ce8e218638fb5
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jul 20 16:03:40 2015 +0530

    tests: set inode-lru-limit to 1 and check if bit-rot xattrs are wrongy created
    
    This test sets the lru limit of the inode table to 1 and checks if inode forgets
    and resolve cause any problem with bit-rot xattrs (especially bad-file xattr).
    
    Change-Id: I1fa25fa2d31dda8d26e8192562e896e5bddd0381
    BUG: 1244613
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11718
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit cdf238e7c90273beff73617481d19d77fc8014db
Author: Meghana M <mmadhusu@redhat.com>
Date:   Mon Aug 3 03:03:07 2015 +0530

    Set nfs.disable to "on" when global NFS-Ganesha key is enabled
    
    "nfs.disable" gets set to "on" for all the existing volumes,
    when the command "gluster nfs-ganesha enable" is executed.
    When a new volume is created,it gets exported via Gluster-NFS on
    the nodes outside the NFS-Ganesha. To fix this,
    the "nfs.disable" key is set to "on" before starting the volume,
    whenever the global option is set to "enable".
    
    Change-Id: I7ce58928c36eadb8c122cded5bdcea271a0a4ffa
    BUG: 1251857
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11871
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a2e40a318aacfeec01f824c7496567734f9863df
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Aug 6 13:00:18 2015 +0530

    Include documentation url in README for reference
    
    Change-Id: Iaa6b6e3b5fd5c3d145a48501e9a5517ae3c12c34
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/11851
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0dbc4b010d437ed7e865ff9b63744e33b3be921b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sat Aug 8 21:29:55 2015 +0530

    tests: Add consistently failing tests to the "bad tests" list
    
    Change-Id: Ie8f296413e012027bb335c41114cacfcde9f6904
    BUG: 1251674
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11868
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3e05e2c69979119ca63b1ae5b775019d8bd27d31
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jul 30 17:03:50 2015 +0530

    logging: Stop using global xlator for log_buf allocations
    
    This reverts commit 765849ee00f6661c9059122ff2346b03b224745f.
    
    With http://review.gluster.org/#/c/10417/, struct mem_accnt
    is no longer embedded in a xlator_t object, but instead is
    allocated separately. Hence this workaround provided to avoid
    crashes in logging infrastructure is no longer needed
    
    BUG: 1243806
    Change-Id: I1bc006172ebe5e417a5923f8be2f37a6277c5e5d
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11811
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6e8c137fb7deca75817d617d40ebd58bbcae186a
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Aug 6 06:22:38 2015 +0530

    rpc-clnt: Check for transport object during rpc connection cleanup
    
    While doing glfs_fini(), all the xlators are first notified of
    PARENT_DOWN. protocol-client xlator on receving that notification
    does rpc_clnt_disable which disassociates rpc->conn with its
    transport object and does socket shutdown. So any further references
    to conn->trans should not happen during rpc connection cleanup which
    is done mainly as part of epoll event handling of EPOLLERR/EPOLLHUP.
    
    BUG: 1250797
    Change-Id: I7d0346451d40372ad59a6a2326176fbb1e694712
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11845
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 1868be8a5c309da8d516624d4af3b3b97819a9eb
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Aug 5 19:23:01 2015 +0530

    quota : volume-reset shouldn't remove quota-deem-statfs
    
    Volume-reset shouldn't remove quota-deem-statfs, unless
    explicitly specified, when quota is enabled.
    
    1) glusterd_op_stage_reset_volume ()
       'gluster volume set/reset <VOLNAME>' features.quota/
       features.inode-quota' should not be allowed as it is deprecated.
       Setting and resetting quota/inode-quota features should be allowed
       only through 'gluster volume quota <VOLNAME> enable/disable'.
    
    2) glusterd_enable_default_options ()
       Option 'features.quota-deem-statfs' should not be turned off
       with 'gluster volume reset <VOLNAME>', since quota features
       can be set/reset only with 'gluster volume quota <VOLNAME>
       enable/disable'.
    
    But, 'gluster volume set features.quota-deem-statfs'
    can be turned on/off when quota is enabled.
    
    Change-Id: Ib5aa00a4d8c82819c08dfc23e2a86f43ebc436c4
    BUG: 1250582
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11839
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 2a3f0fb035cf677d058a920d2fc1931a18e565ec
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 7 10:10:54 2015 +0530

    afr: Do not wind statfs to arbiter brick
    
    Problem: AFR serves statfs from the brick having the least free space
    available. Since the size to be allocated to the arbiter brick in a 3
    way replica is supposed to be considerably lesser than the other 2
    bricks, statfs will be served from this brick which is incorrect.
    
    Fix: Don't serve statfs from the arbiter brick.
    
    Change-Id: I5af098b9c50626f52cf3d7dbb060bf754c797f05
    BUG: 1251346
    Reported-by: Fredrik Brandt <fredrikb@denlillaplaneten.se>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11857
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 7255febab2c38cc89b71f2519a20d10f53586000
Author: anand <anekkunt@redhat.com>
Date:   Wed May 20 19:52:11 2015 +0530

    glusterd: Stop/restart/notify to daemons(svcs) during reset/set on a volume
    
    problem : Reset/set commands were not working properly. reset command returns
    success but it not sending notification to svcs if corresponding graph modified.
    
    Fix: Whenever reset/set command issued, generate the temp graph and compare
    with original graph and do the fallowing actions
    1.) If both graph are identical nothing to do with svcs.
    2.) If any changes in graph topology restart/stop service by calling
    svc manager.
    3)  If changes in options send notify signal by calling glusterd_fetchspec_notify.
    
    Change-Id: I852c4602eafed1ae6e6a02424814fe3a83e3d4c7
    BUG: 1209329
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10850
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 7298b622ab39c2e78d6d745ae8b6e8413e1d9f1a
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Aug 5 23:42:41 2015 +0200

    cluster/ec: Fix tracking of good bricks
    
    The bitmask of good and bad bricks was kept in the context of the
    corresponding inode or fd. This was problematic when an external
    process (another client or the self-heal process) did heal the
    bricks but no one changed the bitmaks of other clients.
    
    This patch removes the bitmask stored in the context and calculates
    which bricks are healthy after locking them and doing the initial
    xattrop. After that, it's updated using the result of each fop.
    
    Change-Id: I225e31cd219a12af4ca58871d8a4bb6f742b223c
    BUG: 1236065
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/11844
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a3faffb259d5288907fac33a2822a8f61c3e86fe
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Aug 5 19:34:01 2015 +0530

    dht/tiering : create new dictionary during migration
    
    To avoid setting wrong xattr during creating link file
    
    Change-Id: Iad8de3521eae17e510035ed42e3e01933d647096
    BUG: 1250828
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11838
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 20a09f52c98c400051dd99d15a3ced59978f42e4
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Tue Aug 4 18:09:15 2015 +0530

    Updating doc maintainers list
    
    Change-Id: I2064f39d915209679ece48b4484b773dfc8e9778
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/11826
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 548ee04668b310d5e0c2d0e866677173940db78d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jul 23 18:11:23 2015 +0530

    geo-rep: Fix gsyncd failing to start on slave
    
    This is a regression introduced by 2ca6441.
    The memory is freed while the caller expects
    it be not. The patch fixes the same.
    
    Change-Id: I76d95eef15b3f7af365b392f2426c8b0388254fc
    BUG: 1222898
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11751
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 611b2545b012d1c5d0700af6bc1a182f7aa2343a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Aug 5 16:58:01 2015 +0530

    features/shard: Fix excessive logging in readdir(p) callback
    
    On enabling features.shard on a volume which already has few files,
    performing operations on the mount was causing excessive logging of
    messages of the following kind:
    
    [2015-08-05 10:57:48.743352] E [shard.c:232:shard_modify_size_and_block_count]
    2-dis-shard: Failed to get trusted.glusterfs.shard.file-size for
    0b2bd401-c438-4d57-8ae5-8d26105d3396
    
    Turns out this is coming from shard_readdir_cbk() where the shard
    translator unconditionally looks for the xattr
    'trusted.glusterfs.shard.file-size' in every entry's rsp dict and
    logs this error on not finding it. But files that are not sharded
    (i.e., the ones that were created before sharding was enabled on the volume)
    will not (and should not) have this xattr associated with them.
    So these logs are misleading and must be suppressed in readdir(p).
    
    Change-Id: I8d268b4f90a8bf744c7851f1984f5a1b6968fb6a
    BUG: 1250441
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11843
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 98637903bb87812d60ef47bb1bd735503133d53e
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Jul 23 18:16:18 2015 +0530

    Remove upgrade guide doc from glusterfs repo
    
    According to the new workflow defined for glusterfs documentation,
    the upgrade guide is maintained at https://github.com/gluster/glusterdocs
    
    Refer #https://www.mail-archive.com/gluster-users@gluster.org/msg21168.html
    
    Change-Id: I6b04847d0201d362ec054ee245999b6b42e42ea7
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/11750
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 64a5bf3749c67fcc00773a2716d0c7b61b0b4417
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jul 21 18:50:12 2015 +0200

    fuse: add "resolve-gids" mount option to overcome 32-groups limit
    
    Add a --resolve-gids commandline option to the glusterfs binary. This
    option gets set when executing "mount -t glusterfs -o resolve-gids ...".
    
    This option is most useful in combination with the "acl" mount option.
    POSIX ACL permission checking is done on the FUSE-client side to improve
    performance (in addition to the checking on the bricks).
    
    The fuse-bridge reads /proc/$PID/status by default, and this file
    contains maximum 32 groups. Any local (client-side) permission checking
    that requires more than the first 32 groups will fail.
    
    By enabling the "resolve-gids" option, the fuse-bridge will call
    getgrouplist() to retrieve all the groups from the user accessing the
    mountpoint. This is comparable to how "nfs.server-aux-gids" works.
    
    Note that when a user belongs to more than ~93 groups, the volume option
    server.manage-gids needs to be enabled too. Without this option, the
    RPC-layer will need to reduce the number of groups to make them fit in
    the RPC-header.
    
    Change-Id: I7ede90d0e41bcf55755cced5747fa0fb1699edb2
    BUG: 1246275
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11732
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 28fc199d5dc92a69eb2b899bbea23548dc14a39b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Jul 30 13:54:51 2015 +0200

    SSL improvements: ECDH, DH, CRL, and accessible options
    
    - Introduce ssl.dh-param option to specify a file containinf DH parameters.
      If it is provided, EDH ciphers are available.
    
    - Introduce ssl.ec-curve option to specify an elliptic curve name. If
      unspecified, ECDH ciphers are available using the prime256v1 curve.
    
    - Introduce ssl.crl-path option to specify the directory where the
      CRL hash file can be found. Setting to NULL disable CRL checking,
      just like the default.
    
    - Make all ssl.* options accessible through gluster volume set.
    
    - In default cipher list, exclude weak ciphers instead of listing
      the strong ones.
    
    - Enforce server cipher preference.
    
    - introduce RPC_SET_OPT macro to factor repetitive code in glusterd-volgen.c
    
    - Add ssl-ciphers.t test to check all the features touched by this change.
    
    Change-Id: I7bfd433df6bbf176f4a58e770e06bcdbe22a101a
    BUG: 1247152
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/11735
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a0919d638a889f03a5bd804cf4c3a63084680fce
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Jul 23 18:07:08 2015 +0530

    Removing glusterfs features doc from glusterfs repo
    
    According to the new workflow defined for glusterfs documentation,
    the features are maintained at https://github.com/gluster/glusterfs-specs.
    Removing the features dir from the doc repo as per,
    https://www.mail-archive.com/gluster-users@gluster.org/msg21168.html
    
    Change-Id: I2f1219c49ef933f6b89a55f2238787d8565d80b6
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/11749
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 3403370ebeaf16567b79022c6ac48b2e0cd50db5
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Aug 3 13:28:09 2015 +0530

    client, rpc: make ping-timeout configurable for glusterfs clients
    
    Change-Id: Idd94adb0457aaffce7330f56f98cebafa2c4dae8
    BUG: 1249499
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/11818
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 9361e2bf05dc511bcc6b49a67b69dfa231a2cab3
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu Jul 16 15:36:17 2015 +0530

    tools/glusterfind: password prompts for peer nodes on delete
    
    SSH keys getting deleted on local node caused password prompts for peer
    nodes on a delete operation.
    
    This race for session directory cleanup on local node is now addressed
    by avoiding the delete path for local node in node_cmd()
    The session directory tree is deleted anyway in mode_delete()
    
    Change-Id: I51c4baf4f9c1ed3caa319d4163bef343bd621429
    BUG: 1243785
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/11693
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit ed9959b0e2c7f401394fa6359641857180baf1c8
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Jul 23 17:54:34 2015 +0530

    Removing admin guide from glusterfs doc repo
    
    The admin guide is maintained at https://github.com/gluster/glusterdocs.
    The admin guide updates should be against above repo and we should only
    have one copy. This is based on the discussion happened here:
    https://www.mail-archive.com/gluster-users@gluster.org/msg21168.html
    
    Change-Id: If5395e7e8005d3e505d229180ce55d466cb1a1fc
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/11747
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 9e3d87639c38b20304ba2809f3f27440ad712fad
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Jul 30 11:57:45 2015 +0530

    tests: Get more debug info from failed tests
    
    Change-Id: I8e8dd0e4fc6955ce4b1ac9f276362b61ca71f1c5
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11801
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b467b97e4c4546b7f870a3ac624d56c62bfa5cf9
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Jul 30 09:40:24 2015 +0530

    glusterd: fix op-version bump up flow
    
    If a cluster is upgraded from 3.5 to latest version, gluster volume set all
    cluster.op-version <VERSION> will throw an error message back to the user saying
    unlocking failed. This is because of trying to release a volume wise lock in
    unlock phase as the lock was taken cluster wide. The problem surfaced because
    the op-version is updated in commit phase and unlocking works in the v3
    framework where it should have used cluster unlock.
    
    Fix is to decide which lock/unlock is to be followed before invoking lock phase
    
    Change-Id: Iefb271a058431fe336a493c24d240ed833f279c5
    BUG: 1248298
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11798
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit b646aa00bb2558fe82f80ca8a43f187611d288c9
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Mon Aug 3 06:33:01 2015 -0700

    Revert "Add DESTDIR support for pyglupy Makefile"
    
    This reverts commit 871000e3ddb457c9cc5757cd94cfc178e3c1be29.
    
    Change-Id: I05913151d9cb4c50057e5e72859768085041bdc9
    Reviewed-on: http://review.gluster.org/11821
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 871000e3ddb457c9cc5757cd94cfc178e3c1be29
Author: Michael Scherer <misc@redhat.com>
Date:   Fri Jul 31 16:37:41 2015 +0200

    Add DESTDIR support for pyglupy Makefile
    
    Smoke tests run on a new slave on Fedora 22 fail because make install
    try to install the python package in /usr/lib/python2.7 without being
    root, because there is no $DESTDIR support for that part.
    
    Change-Id: Ibed17dd091a96fbdf5536ac66b8c876b33a39cd6
    Signed-off-by: Michael Scherer <mscherer@redhat.com>
    Reviewed-on: http://review.gluster.org/11813
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 4d2ec1d0d6bebcfb19e0c4ecf741ddd29bb28e58
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jul 28 14:37:47 2015 +0530

    geo-rep: Do not crash worker on ESTALE
    
    Handle ESTALE returned by lstat gracefully
    by retrying it. Do not crash the worker.
    
    Change-Id: I2527cd8bd1f7d2428cb4fa3f20782bebaf2df12a
    BUG: 1247529
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11772
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit aa80be0501a6893564b0dd40611cc91ad553ca6c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jul 3 11:34:20 2015 +0530

    glusterd: Do not log failure if glusterd_get_txn_opinfo fails in gluster volume status
    
    The first RPC call of gluster volume status fetches the list of the volume names
    from GlusterD and during that time since no volume name is set in the dictionary
    gluserd_get_txn_opinfo fails resulting into a failure log which is annoying to
    the user considering this command is triggered frequently.
    
    Fix is to have callers log it depending on the need
    
    Change-Id: Ib60a56725208182175513c505c61bcb28148b2d0
    BUG: 1238936
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11520
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 34517651a6c4507e389ffdb9ac83709bb3346a34
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 30 08:23:37 2015 -0400

    build: scripts are not installed with +x bit
    
    scripts listed in Makefile.am as foo_DATA, should be foo_SCRIPTS
    to be installed +x
    
    Change-Id: Ib9b98efcea968c03b574726bdc0d4f76cdfd1dc1
    BUG: 1225018
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11806
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit e7f737e62a9ea9eac730b6ba3ef8739e497e1540
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Mon Jun 1 14:35:57 2015 +0530

    libglusterfs: write error handling when filesystem have no space left
    
    When no space left on filesystem and user want to perform any operation
    which result to change in /var/lib/glusterd/* files then glusterd is
    failing to write on temporary file.
    
    Fix is to handle error when write failed on temporary files due to no
    space left on file system.
    
    Change-Id: I79d595776b42580da35e1282b4a3cd7fe3d14afe
    BUG: 1226829
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11029
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Cedric Buissart

commit 8470ac5e923a5e98cee94f3b04d41488bead0422
Author: vmallika <vmallika@redhat.com>
Date:   Wed Jul 22 14:49:39 2015 +0530

    quota/marker: set log-level to debug for ESTALE/ENOENT for marker txn
    
    For all marker txn, it is possible that while the txn in progress
    file can be removed.
    
    So log all ENOENT/ESTALE error in debug level
    
    Change-Id: I776ba3cda33fe992f9dcc7baede7206c4ce19553
    BUG: 1245544
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11736
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 16bd894480b34e20950af795dc1ebb66d942541a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jul 7 16:27:45 2015 +0530

    rebalance/glusterd: Refactor rebalance volfile
    
    performance xlator loaded in rebalance xlators are dummy
    translators, since all fops are starting with dht level.
    
    Removing the performance xlators from rebalance volfile
    will help to minimize the chance for a graph switch.
    
    The new rebalance xlators will look like->>>
    
                            (io-stats)
                                ||
                                ||
                                ||
                           (----DHT----)
                          //          \\
                         //            \\
                        //              \\
                  (replica-1)  ...   (replica-n)
                  //      \\          //      \\
                 //        \\        //        \\
                //          \\      //          \\
             client       client  client       client
    
    Change-Id: I3808e3b48fd0cb3e60ef386b8ac9fd994e2831e3
    BUG: 1240621
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11565
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 8dc32a93fca3908e1f874393bcd56b89de269e2b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 28 19:15:44 2015 +0530

    tests: reset IFS after changing it
    
    Many thanks to fanghuang.data@yahoo.com for RC and BUG
    https://bugzilla.redhat.com/show_bug.cgi?id=1245425#c0
    
    BUG: 1245425
    Change-Id: I411384ad2b81db9941ac136f4e584a3a965d53f1
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11779
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 65a981e63c5a28ad917cab4a830f9b4e186c114a
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed Jul 29 14:57:44 2015 +0530

    rpc: check for unprivileged port should start at 1024
    
    The current check for unprivileged port starts beyond 1024
    i.e. port > 1024
    The actual check should start at 1024
    i.e. port >= 1024
    
    Change-Id: I78aff3025891e3e78ca6a9a670c89571752157df
    BUG: 1247930
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/11788
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b467af0e99b39ef708420d3f7f6696b0ca618512
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jul 27 12:30:19 2015 +0530

    features/shard: Create /.shard with 0777 permissions (for now)
    
    Change-Id: I4e5692f06a189230825f0aeb6487b103bfb66fe1
    BUG: 1247108
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11791
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit de3023c8b5ded9c82414eec153fc660f568b688e
Author: vmallika <vmallika@redhat.com>
Date:   Wed Jul 22 09:02:39 2015 +0530

    quota: fix parents caching during build ancestry
    
    In build ancestry, we get the list of parents for a file,
    these parents are cached in inode ctx.
    This caching is not happening because posix is not setting
    d_stat information in the leaf node entry
    This patch fixes the issue
    
    Inode-ctx is not updated with new parent when
    rename performed on same directory.
    This patch fixes the issue
    
    There is a possibility of caching stale entries,
    consider below example:
    1) build_ancestry invoked on a file
    2) rename is invoked on the same file
    3) buils_ancestry prepared entries of old parent
    4) rename completed and in cbk old parent is replaced with
           new parent in inode ctx
    5) now build_ancestry cbk adds old parent to inode ctx
    
    In this patch we also remove stale entries in writev and fallocate
    
    Change-Id: Ib1854a41b47b14eb775326588352015c83d034de
    BUG: 1240949
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11574
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3bd335602be27bccad597a9156ecf80344bef88d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Jul 29 16:24:37 2015 +0530

    tests/tier: mark tiering related spurious failures as bad test
    
    Change-Id: I808845e55103821eb5eda4c0650dc55facad01e2
    BUG: 1246229
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11792
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 5a9a903a9a3b1d234dfaf45eb1bad7930a2aafd4
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Thu Jul 23 14:44:04 2015 +0530

    tiering: Error message change for detach-tier non tier volume
    
    Change-Id: Ib350b201df14b105e475426d2ec20ff5da39a8a1
    BUG: 1245935
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>
    Reviewed-on: http://review.gluster.org/11745
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit ea90c92820ee0ca500345863cdfb5009d08b6ca7
Author: Anand Avati <avati@redhat.com>
Date:   Fri Dec 6 17:31:57 2013 -0800

    timer: fix race between gf_timer_call_cancel() and gf_timer_proc()
    
    Change-Id: Ie264d3d591352e4a8ddaa90ae2174d9c552396f1
    BUG: 1243187
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6459
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit f7e898cb33b7702ef7299c73f63d70163144b148
Author: Sakshi <sabansal@redhat.com>
Date:   Thu Apr 30 18:10:26 2015 +0530

    cli : removing extra colon from rebalance status output
    
    Change-Id: I74417471d7d2a86f198037d88dbf7d072c4349c3
    BUG: 1218960
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/10475
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 71641e36734c86ac14c62caf57301e2214712502
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 28 18:38:56 2015 +0530

    features/shard: Fix block size get from xdata
    
    Instead of using dict_get_ptr, dict_get_uint64 was used. If the first byte of
    the value is '\0' then size is returned as 0 because strtoull is used in
    data_to_uint64. This will make it seem like the file is not sharded at all.
    
    BUG: 1247108
    Change-Id: Id1fc291198ac94b20ae645c04a51db78bab51993
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11778
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 62c2e7f8b9211ba149368d26f772f175fe51b43b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Jul 3 16:32:56 2015 +0530

    geo-rep: Fix history failure
    
    Both ACTIVE and PASSIVE workers register to changelog
    at almost same time. When PASSIVE worker becomes ACTIVE,
    the start and end time would be current stime and register_time
    repectively for history API. Hence register_time would be less
    then stime for which history obviously fails. But it will
    be successful for the next restart as new register_time > stime.
    
    Fix is to pass current time as the end time to history call
    instead of the register_time.
    
    Also improvised the logging for ACTIVE/PASSIVE switching.
    
    Change-Id: Idc08b4b55c7a4c575ba44918a98389164ccbee8f
    BUG: 1239044
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11524
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 8f04ec33bc86aa464a5f8b77f9d64e5608cb6f1b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jul 28 16:02:50 2015 -0400

    rpc: fix concurrency bug in gf_authenticate
    
    The basic problem is that gf_authenticate abused global variables to
    pass info through dict_foreach.  This is not thread-safe, but it wasn't
    affecting most people until multi-threaded epoll came along.  Now, if
    two threads get into this code at the same time - and there's nothing to
    prevent it - one of them could free one of the dicts involved while the
    other is still using it.
    
    The fix is to pass this same information using a temporary structure
    instead of globals.  This makes the code smaller and more efficient too.
    
    Change-Id: I72cccc440bb40d5f7ff695250dd014762c7efb73
    BUG: 1247765
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/11780
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d051bd14223d12ca8eaea85f6988ff41e5eef2c3
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jul 28 11:25:55 2015 +0530

    features/shard: (Re)initialize local->call_count before winding lookup
    
    Change-Id: I616409c38b86c0acf1817b3472a1fed73db293f8
    BUG: 1247108
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11770
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2d85abedb2c6fb2a1c89d2074d0cc21d654cce07
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jul 28 06:42:26 2015 -0700

    Revert "Revert "core: avoid crashes in gf_msg dup-detection code""
    
    This reverts commit ca67ac071c56a3bd6f2b2ba3a958f0305db50a3d.
    
    Change-Id: Iba688b524c78b84aaa0992afa5ee8e549603d990
    Reviewed-on: http://review.gluster.org/11777
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 51f48bc9a41a5e2004d9051ff90517b01626b08f
Author: anand <anekkunt@redhat.com>
Date:   Fri Jul 24 15:48:50 2015 +0530

    glusterd: glusterd crash due to race between handshake and snapshot remove threads
    
    Issue : glusterd was crashing due to race between handshake thread and snapshot
    remove
    RCA : Snapshot  thread referring  voinfo and same time volinfo is modified during handshake,
    glusterd was crashing  due to this inconsistent data of volinfo .
    
    Note: Sending commands without checking cluster status may lead to crash
    
    Fix:.Wait for handshake complete/cluster ready before proceeding commands.
    
    Change-Id: Iefd986664bd9dd225f0abf8f85476d6afd206914
    BUG: 1246432
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/11757
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 8d915d196fc591b141bb5267e16453d18dff7955
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Jul 21 18:05:06 2015 +0200

    cluster/ec: Minimize usage of EIO error
    
    Change-Id: I82e245615419c2006a2d1b5e94ff0908d2f5e891
    BUG: 1245276
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/11741
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 4377d1b5424da0596be8591103d13207d84105d1
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 21 15:13:28 2015 +0530

    features/bit-rot-stub: handle REOPEN_WAIT on forgotten inodes
    
    Change-Id: Ia8706ec9b66d78c4e33e7b7faf69f0d113ba68a4
    BUG: 1245981
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11729
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 746f23ce055f7beed20aa4038f61ad5bdd84419f
Author: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
Date:   Tue Jul 14 12:24:21 2015 +0530

    cli : changing the gluster peer probe message
    
    The gluster peer probe command with invalid ips dont report that
    IP's can also be a valid in usage.
    
    Change-Id: I8f58341a2b76369ccf62f88ca0ecd8a9a9529af6
    BUG: 1242742
    Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/11657
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 65e6ab1bfbbec7755f7ae2294cb83334ac65a296
Author: anand <anekkunt@redhat.com>
Date:   Tue Jul 21 15:42:24 2015 +0530

    glusterd: getting txn_id from frame->cookie in op_sm call back
    
    RCA: If rebalance start is triggered from one node and one of other nodes in the cluster goes down simultaneously
    we might end up in a case where callback will use the txn_id from priv->global_txn_id which is always zeros and
    this means injecting an event with an incorrect txn_id will result into op-sm getting stuck.
    
    fix: set txn_id in frame->cookie during sumbit_and_request, so that we can get txn_id in call back
    functions.
    
    Change-Id: I519176c259ea9d37897791a77a7c92eb96d10052
    BUG: 1245142
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/11728
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ca67ac071c56a3bd6f2b2ba3a958f0305db50a3d
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jul 23 12:58:02 2015 +0530

    Revert "core: avoid crashes in gf_msg dup-detection code"
    
    This reverts commit 765849ee00f6661c9059122ff2346b03b224745f.
    
    With http://review.gluster.org/#/c/10417/, struct mem_accnt
    is no longer embedded in a xlator_t object, but instead is
    allocated separately. Hence this workaround provided to avoid
    crashes in logging infrastructure is no longer needed.
    
    Change-Id: I460b62780f570cd9873bad17d9327eefc17a1355
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11746
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b23c4b4e22628ab9ddc0c8341360a53d3f9d658d
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Mon Jun 29 20:41:08 2015 +0530

    changelog: test case for verifying empty changelogs avoided
    
    Test case added to check NO EMPTY changelogs gets
    created over changelog rollover period.
    
    Change-Id: I83323644e1a0c4b920a472e1179606a0fd54d1d9
    BUG: 1237000
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/11460
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 385acc675c512c63f7051d46ad96666ea34cf0b5
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jul 22 15:18:20 2015 +0530

    features/shard: Handle unlink of files with holes appropriately in unlink() and rename().
    
    Change-Id: I25a02386dc95580c2e76a13fdd8e11a0df234d56
    BUG: 1245547
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11737
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit d49b4b1086119873664b77ea7d7f2a5dd8f671ee
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Jul 1 14:47:48 2015 +0530

    glusterd: initialize the daemon services on demand
    
    As of now all the daemon services are initialized at glusterD init path. Since
    socket file path of per node daemon demands the uuid of the node, MY_UUID macro
    is invoked as part of the initialization.
    
    The above flow breaks the usecases where a gluster image is built following a
    template could be Dockerfile, Vagrantfile or any kind of virtualization
    environment. This means bringing instances of this image would have same UUIDs
    for the node resulting in peer probe failure.
    
    Solution is to lazily initialize the services on demand.
    
    Change-Id: If7caa533026c83e98c7c7678bded67085d0bbc1e
    BUG: 1238135
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11488
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit fd296d90168002a475a9899a72a0dd1811f038ee
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jul 23 14:59:19 2015 +0530

    posix,shard: Fill in ia_size and ia_blocks before unwinding (f)setattr
    
    The shard xlator will request for size xattrs in its request and
    posix will perform xattr_fill of requested keys before unwinding
    (f)setattr.
    
    Change-Id: I4ec4779568be6f805724b875b1b4215787112e7f
    BUG: 1246082
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11754
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 7bec717f8850135368609fccf1b1c697af60c546
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jul 23 18:08:34 2015 +0530

    cluster/afr: Fix incorrect logging in read transactions
    
    afr_read_txn_refresh_done() at its entry point can fail for
    reasons like ENOENT/ESTALE but seldom due to EIO, which is something
    _AFR_ would internally generate and not receive in response from
    a child translator. AFR is reporting "split-brain" for _any_
    kind of failure in read txn, of the following kind:
    
    [2015-07-07 18:04:34.787612] E [MSGID: 108008]
    [afr-read-txn.c:76:afr_read_txn_refresh_done] 0-vol3-replicate-3:
    Failing STAT on gfid 18a973c4-73d3-48b8-942c-33a6f1a8e6b4:
    split-brain observed. [Input/output error]
    
    This patch fixes such misleading errors.
    
    To-Do:
    Avoid logging EIO if/when split-brain choice is set.
    Will do that as part of a separate commit.
    
    Change-Id: Ib513c75168f7026118ad5b3f0b35e9dd498cfe1e
    BUG: 1246052
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11756
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9442e7bf80f5c2189140918bb5588868204521ed
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Jun 24 12:21:02 2015 +0530

    rpc: fix binding brick issue while bind-insecure is enabled
    
    problem:
    
    When bind-insecure is turned on (which is the default now), it may happen
    that brick is not able to bind to port assigned by Glusterd for example
    49192-49195...
    
    It seems to occur because the rpc_clnt connections are binding to ports in
    the same range. so brick fails to bind to a port which is already used by
    someone else
    
    solution:
    
    fix for now is to  make rpc_clnt to get port numbers from 65535 in a descending
    order, as a result port clash is minimized
    
    other fixes:
    
    previously rdma binds to port >= 1024 if it cannot find a free port < 1024,
    even when bind insecure was turned off(ref to commit '0e3fd04e'), this patch
    add's a check for bind-insecure in gf_rdma_client_bind function
    
    This patch also re-enable bind-insecure and allow insecure by default which was
    reverted (ref: commit cef1720) previously
    
    Change-Id: Ia1cfa93c5454e2ae0ff57813689b75de282ebd07
    BUG: 1238661
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11512
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e9b86d0b575e8e59f0910874341a4a05574124cf
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Jul 24 11:33:57 2015 +0530

    Adding README for gluster documentation project
    
    Change-Id: I1bcfc14ee3eabeb26a5cea42533c8df5b040f549
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/11753
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit bf8e604e35ff5aafd15dd235bf2b565e8cd65ea5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jul 25 10:28:11 2015 +0200

    logging: client3_3_removexattr_cbk should not log expected ENODATA
    
    Commit 379dbbfd changed the log level of an expected error message from
    GF_LOG_DEBUG to '0'. This causes the message to always get logged. It is
    intended to log the warning when the xattr could not be removed (but
    exists), removing a non-existing xattr is sufficient as debug.
    
    BUG: 1246736
    Change-Id: If11d15d699e8152cc32e0c0c1d65b587c5c48892
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11759
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joe Julian <me@joejulian.name>
    Tested-by: Joe Julian <me@joejulian.name>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 2d2d1fbb201ea81a54d9c9aef28345cb259eb141
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jul 12 12:29:12 2015 +0200

    dict: dict_set_bin() should never free the pointer on error
    
    dict_set_bin() is handling the pointer that it passed inconsistently.
    Depending on the errors that can occur, the pointer passed to the dict
    can be free'd, but there is no guarantee.
    
    It is cleaner to have the caller free the pointer that allocated it and
    dict_set_bin() returned an error. When dict_set_bin() returned success,
    the given pointer will be free'd when dict_unref() calls data_destroy().
    
    Many callers of dict_set_bin() already take care of free'ing the pointer
    on error. The ones that did not, are corrected with this change too.
    
    Change-Id: I39a4f7ebc0cae6d403baba99307d7ce408f25966
    BUG: 1242280
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11638
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 8a4f0de2a6dc5d1a9cbc54bbe9aa25d7e38d4ae7
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jul 18 12:55:39 2015 +0200

    dict: merge static/non-static dict_set_* variations
    
    Copy/pasting complete functions for setting one boolean is rather ugly,
    this can easily be solved with a helper function that gets the boolean
    as an extra parameter.
    
    Also removing dict_set_dynmstr() because there are no callers, and using
    GF_MALLOC() or GF_CALLOC() to allocate memory for strings is much more
    preferred.
    
    And, as Kaleb pointed out, prefixing functions with an underscore '_' is
    reserved for libc internals. Renaming the _dict_*() functions for that
    reason.
    
    Change-Id: I8e681954502f17e59c8f5e8a294d3db238d3e5f3
    BUG: 1232304
    Reported-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11716
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 996926530bc2da34f616d01b8f94c0ed7884aaeb
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jul 19 19:26:02 2015 +0200

    gfapi: remove unused variables in priv_glfs_process_upcall_event()
    
    Compiling on NetBSD shows these trivial warnings:
    
        api/src/glfs-fops.c: In function 'priv_glfs_process_upcall_event':
        api/src/glfs-fops.c:3873:29: warning: unused variable 'object'
        api/src/glfs-fops.c:3869:28: warning: unused variable 'gfid'
    
    BUG: 1202274
    Change-Id: If0101c64da2333b05958838f58761534ef341d62
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11717
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a909ccfa1b4cbf656c4608ef2124347851c492cb
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jul 16 14:52:36 2015 +0530

    rpc,server,glusterd: Init transport list for accepted transport
    
    GlusterD or a brick would crash when encrypted transport was enabled and
    an unencrypted client tried to connect to them. The crash occured when
    GlusterD/server tried to remove the transport from their xprt_list due
    to a DISCONNECT event. But as the client transport's list head wasn't
    inited, the process would crash when list_del was performed.
    
    Initing the client transports list head during acceptence, prevents this
    crash.
    
    Also, an extra check has been added to the GlusterD and Server
    notification handlers for client DISCONNECT events. The handlers will
    now first check if the client transport is a member of any list.
    GlusterD and Server DISCONNECT event handlers could be called without
    the ACCEPT handler, which adds the transport to the list, being called.
    This situation also occurs when an unencrypted client tries to establish
    a connection with an encrypted server.
    
    Change-Id: Icc24a08d60e978aaa1d3322e0cbed680dcbda2b4
    BUG: 1243774
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/11692
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 332cb6a6901c68f0c79070d7103cc7a728ea6d26
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 15 06:16:54 2015 +0530

    cluster/ec: Handle race between unlock-timer, new lock
    
    Problem:
    New lock could come at the time timer is on the way to unlock. This was leading
    to crash in timer thread because thread executing new lock can free up the
    timer_link->fop and then timer thread will try to access structures already
    freed.
    
    Fix:
    If the timer event is fired, set lock->release to true and wait for unlock to
    complete.
    
    Thanks to Xavi and Bhaskar for helping in confirming that this race is the RC.
    Thanks to Kritika for pointing out and explaining how Avati's patch can be used
    to fix this bug.
    
    Change-Id: I45fa5470bbc1f03b5f3d133e26d1e0ab24303378
    BUG: 1243187
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11670
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 94372373ee355e42dfe1660a50315adb4f019d64
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jul 17 16:04:01 2015 +0530

    dht: send lookup even for fd based operations during rebalance
    
    Problem:
    dht_rebalance_inprogress_task() was not sending lookups to the
    destination subvolume for a file undergoing writes during rebalance. Due to
    this, afr was not able to populate the read_subvol and failed the write
    with EIO.
    
    Fix:
    Send lookup for fd based operations as well.
    
    Thanks to Raghavendra G for helping with the RCA.
    
    Change-Id: I638c203abfaa45b29aa5902ffd76e692a8212a19
    BUG: 1244165
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11713
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 175f1737fb6fe9450702556b24bf395bac97cef1
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Apr 13 17:05:44 2015 +0530

    libglusterfs: Even anonymous fds must have fd->flags set
    
    We do not set the same flags to anonymous fd that posix uses to open
    an anonymous fd in the backend. If there are any xlators which rely on
    these flags for their operation they may not work well.
    
    Add proper flags to anonymous fds at the time of their creation and
    refer to them for subsequent operations.
    
    Change-Id: Ia99b7ea7d38839f099c7b4aae3c7ead123bc8c67
    BUG: 1211221
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10219
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bc6110fa37f1d6214d2e8cce367e0b7abd6976c3
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Jul 7 18:37:42 2015 +0530

    quota : validating soft limit percentage.
    
    Change-Id: I14c049c84c468b6415a1de45441b2fed94e8ed4b
    BUG: 1240654
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11566
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 0acd0b45e5ee22eb5bb35c21093136b3b062744f
Author: vmallika <vmallika@redhat.com>
Date:   Fri Jul 17 12:50:59 2015 +0530

    quota/marker: contribution with list_del can cause mem corruption
    
    There is a possibility that contribution is removed twice from list
    during unlink operation (with hard links) or during rename operation
    
    Use list_del_init for a thread safe deltion of member from list
    
    Change-Id: Iff5e0c03cc8f0ed85da0db1739b84b695abf9ea6
    BUG: 1244109
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11706
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 17feb90623750ed003ca7dd0a94a4cf5e20678ae
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Jul 16 16:46:23 2015 +0530

    nfs: log disabled export/netgroups feature as INFO
    
    If export/netgroups feature is disabled for gluster/nfs, then the "nfs.log"
    contains a Warning message which is deceiving for the users. Logging the
    message as Info is sufficient.
    
    Change-Id: I3d07e8bc4f09f3eb32014f5a10390d0484b838cf
    BUG: 1243805
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/11695
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a00c623dc1aa2df7e374d05f8a2ceaf205e854b6
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Jun 25 02:18:42 2015 +0530

    storage/posix: Check xdata for NULL before dict_get
    
    Performing a dict_get on xdata can lead to
    frequent logging if xdata is NULL.
    
    Change-Id: I1666f0cc958c639ccd816e3738dd4a1efebbff82
    BUG: 1235921
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11390
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit b2673ae923f3e4651f4c642a9b88f5d200a25585
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Thu Jul 9 11:37:16 2015 +0530

    glusterd: Porting the left out gf_log_callingfns to new framework
    
    Change-Id: I1b0ad54238895475ddbacc4fffacac8dc6e887fe
    BUG: 1235538
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/11590
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 0ad8bfb028d7916f7940bb48f0df616d164f74de
Author: Shyam <srangana@redhat.com>
Date:   Fri May 22 14:40:50 2015 -0400

    doc: Add documentation for new logging framework
    
    This commit adds a guideline document for using the new message
    logging infrastructure.
    
    Change-Id: Iddc6a2b6f244cc5b51dab4c99d963e89b1a9f478
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/10896
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anusha B.Rao <anusha91rao@gmail.com>
    Tested-by: Anusha B.Rao <anusha91rao@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b21f3b3ce69c6b1b0eb6f8243b5c601c5c4b7cbe
Author: arao <arao@redhat.com>
Date:   Thu Feb 12 10:22:42 2015 +0530

    features/marker: Fixing dereference after null check
    
    CID: 1124494
    The variable was sent as a parameter to the function without the null check,
    hence added a check on null and error log accordingly.
    
    Change-Id: I11a649fc9a1bedad17422aeddb8dd8fa225d404e
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9641
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ee824ccb10e28489907fbf978a2d36b0b2c5dc8c
Author: anand <anekkunt@redhat.com>
Date:   Sat Jun 13 16:46:10 2015 +0530

    glusterd: rebalance support for cluster.rc framework
    
    Issue:Rebalance is failing in cluster framework (any simulated cluster environment in same node ).
    RCA:
      1. we are passing always "localhost" as volfile server for rebalance xlator .
      2. Rebalance daemons are overwriting  unix socket and log files each other.
         (All rebalance processes are creating socket with same name) .
    
    Fix: set vol_file_server, unix socket and log files properly.
    
    Change-Id: I6654461e00c2a164b2f1f1db24a316c4180dd8d5
    BUG: 1231437
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/11210
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 4cdeee511ef8bab977cbb31bc2e8f005fe340ef1
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jul 16 13:56:51 2015 +0530

    cli: Create missing logbuf_pool
    
    Since logbuf_pool was not created via glusterfs_ctx_defaults_init(),
    the following error was present in cli logs repeateadly for each
    and every execution of a gluster command.
    
    E [mem-pool.c:417:mem_get0] (-->/usr/local/lib/libglusterfs.so.0(+0x7e262)
    [0x7fdbc0b1f262] -->/usr/local/lib/libglusterfs.so.0(_gf_msg+0x804)
    [0x7fdbc0ac7844] -->/usr/local/lib/libglusterfs.so.0(mem_get0+0x78)
    [0x7fdbc0af5b48] ) 0-mem-pool: invalid argument [Invalid argument]
    
    This change creates ctx->logbuf_pool via glusterfs_ctx_defaults_init()
    in cli.c so that the above error is no longer logged in cli logs.
    
    Change-Id: I3fcd9cfefa06ddd52e1989b039ff5637372c3235
    BUG: 1243753
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/11691
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 139eb82c2ae0bc56ca12c62b83e6fc774bc88363
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jul 16 19:24:00 2015 +0530

    posix: fix mem-leak in posix xattrop
    
    Change-Id: I1dd70f74a98c5875eb316f3c3e560047f128685b
    BUG: 1243890
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11700
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6b7bdcb02cf39199d3720c2471121d14df64c8ab
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat Jul 11 09:21:27 2015 +0530

    glusterd: use 2 epoll worker threads by default
    
    The no. of epoll worker threads can be configured
    by adding the following option into glusterd.vol.
    
            option event-threads <NUM-OF-EPOLL_WORKERS>
    
    BUG: 1242421
    Change-Id: I2a9e2d81c64beaf54872081f9ce45355cf4dfca7
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/11630
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d94b39a8e6080e51f7281d545f11514829c1265c
Author: vmallika <vmallika@redhat.com>
Date:   Wed Jul 15 15:17:31 2015 +0530

    quota: fix quota test case
    
    Below command is wrong way of executing
    mutilple command with | (pipe)
    
    local cmd="$CLI volume quota $V0 list $QUOTA_PATH | grep $QUOTA_PATH |
    awk '{print \$$FIELD}'"
    $cmd
    This patch fixes the issue
    
    This patch also fixes testcase inode-quota.t, which checking
    quota values in wrongs fields
    
    Change-Id: If28732e6a76ea4bf75560f6496c8f56670915cf9
    BUG: 1229297
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11673
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b5c37403995b9ecfaa949088c3a09495d783bd87
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 14 16:16:00 2015 +0530

    protocol/server: use different dict for resolving
    
    protocol/server has to resolve the inode before continuing with any fop coming
    from the clients. For resolving it, server xlator was using the same dict
    associated with the fop. It causes problems in some situations.
    
    If a directory's inode was forgotten because of lru limit being exceeded, then
    when a create fop comes for an entry within that directory, server tries to
    resolve it. But since the parent directory's inode is not found in the inode
    table, it tries to do a hard resolve by doing a lookup on the parent gfid.
    
    If any xlator below server wants to get some extended attributes whenever
    lookup comes, then they set the new keys in the same dict that came along with
    the create fop. Now, the lookup of the parent succeeds and the create fop
    proceeds with the same dict (with extra keys present). posix xlaror creates
    those xattrs that are present in the dict. Thus the xattrs which were not to
    be present by default are also set as part of create. (Ex: bit-rot related
    xattrs such as bad-file, version and sign xattrs)
    
    Change-Id: I4bdad175a1d7a04a3aa36073667c556d6c260263
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11661
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 431565e35afea5d99931276d3f0599473d088b8a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jun 16 17:59:23 2015 +0530

    features/shard: Use xattrop (as opposed to setxattr) for updates to size xattr
    
    Change-Id: Icd8984976812bb47ae7129426f6c1aa9393b3ab9
    BUG: 1232391
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11467
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 539c11e424ce008579ab5a11da71028ba872a0a7
Author: Anuradha Talur <atalur@redhat.com>
Date:   Tue Jul 7 19:10:26 2015 +0530

    doc: remove deprecated replace-brick commands from gluster man page
    
    Change-Id: Ibdd42bf4b59fe8a9df5bad68fbc498b4496c5e53
    BUG: 1206539
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11567
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 09530dfd822c8c3cc8da20a4600b5d2aec1ebf9d
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Sun May 17 00:26:06 2015 +0530

    features/changelog: fix buffer overrun in changelog-helpers
    
    changelog-helpers.c:1911:17: warning: Size argument is greater than the free
    space in the destination buffer strncat (result, pre_dir_name, PATH_MAX);
                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    changelog-helpers.c:1919:17: warning: Size argument is greater than the free
    space in the destination buffer strncat (result, bname, PATH_MAX);
                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    Change-Id: I60ca7fe762f07cb72fe7b69f0253835becaff7b9
    BUG: 1222238
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/10802
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit e4fa8568478279c1884c54b9a369655ffa559d4a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jul 12 18:37:43 2015 +0530

    cluster/ec: Propogate correct errno in case of failures
    
    - Also remove internal-fop setting in create/mknod etc xattrs.
    
    Rebalance was failing because ec was giving EIO when lock acquiring fails as
    the file/dir doesn't exist. Posix_create/mknod are not setting config xattr
    because internal-fop key is present in dict and setxattr for this fails leading
    to failure in setting rest of xattrs.
    
    Change-Id: Ifb429c8db9df7cd51e4f8ce53fdf1e1b975c9993
    BUG: 1242254
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11639
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 1d50088062f893424f8e63ae8f7786a97494f21b
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Tue Jul 14 14:01:14 2015 +0530

    glusterd: Pass NULL in glusterd_svc_manager in glusterd_restart_bricks
    
    On restarting glusterd quota daemon is not started when  more than one
    volumes are configured and quota is enabled only on 2nd volume.
    This is because of while restarting glusterd it will restart all the bricks.
    During brick restart it will start respective daemon by passing volinfo of
    first volume. Passing volinfo to glusterd_svc_manager will imply daemon
    managers will take action based on the same volume's configuration which
    is incorrect for per node daemons.
    
    Fix is to pass volinfo NULL while restarting bricks.
    
    Change-Id: I2602002a8ba7762fc1eb08123e79fbcf568ecab4
    BUG: 1242875
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11658
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 796062f8d8bec2d6fff5ddac4f529814ec982dfb
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jul 6 11:49:31 2015 +0530

    glusterd: daemons start/stop should be logged in INFO
    
    Change-Id: I81ceba4b7110140aec790659fcac90403c8e3869
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11538
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2ca64411fd134eb03fc8b40dec91e94027ad82b1
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue May 19 17:24:45 2015 +0530

    geo-replication: fix memory leak in gsyncd
    
    1. leak in str2argv() function:
    
    char *strdup(const char *s);
    The strdup() function returns a pointer to a new string which is a
    duplicate of the  string  s. Memory for the new string is obtained
    with malloc(3), and can be freed with free(3).
    
    so when using strdup, user has to take care of freeing the memory
    allocated by strdup library function.
    
    2. leak in main() function:
    
    str2argv() function calls calloc and allocates memory pointed to argv,
    after return from str2argv() memory pointed to argv has to be cleaned
    in main().
    
    This patch is to fix 2 memory leaks mentioned above.
    
    Change-Id: I6bf26101e0460a7324ac7bdb69905839688d4987
    BUG: 1222898
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/10831
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Milind Changire <mchangir@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 7766c0df5509e8acb6768c69d3f5642909781135
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 1 14:25:07 2015 +0530

    cluster/ec: wind readlink on good subvol(s)
    
    BUG: 1232172
    Change-Id: I3a56e487840d86147dd85bf5fbe79b165eae289f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11589
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 84ecb016cd2f1c8853c22e2df7d44d6c7bf32ed7
Author: vmallika <vmallika@redhat.com>
Date:   Tue Jul 7 16:56:12 2015 +0530

    quota: Fix crash in quota enforcer
    
    With multiple hardlinks check_quota_limit is invoked for each parent
    each of this check_limit can invoke validation
    this can cause frame->local to get corrupted during validation.
    
    Testcase tests/bugs/quota/bug-1235182.t fails spuriously with
    this problem
    
    Change-Id: I53adc54b431fb5f43e67a94248102ddaf0d7978f
    BUG: 1238747
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11510
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit e73db5e7fe1dba5a071725ef3480a4a1d5c7bef7
Author: vmallika <vmallika@redhat.com>
Date:   Sun Jul 12 21:03:54 2015 +0530

    quota/marker: fix mem-leak in marker
    
    Free local in error paths
    
    Change-Id: I76f69e7d746af8eedea34354ff5a6bf50234e50e
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11617
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit d51ddfe8f8839ccb419eb2d8a7cf024d3f5fdeeb
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Jul 13 11:59:33 2015 +0530

    features/bitrot: throttle signer
    
    Pass -DDBR_RATE_LIMIT_SIGNER CFLAGS to enable fixed value throttling
    based on TBF to rate limit signer. The following messags is dumped
    in bitd log file that this change introduces.
    
    [
        [Rate Limit Info] "tokens/sec (rate): 131072, maxlimit: 524288"
    ]
    
    Bug: 1242809
    Change-Id: I063e41d4c7bcddd7a940cc175e89536cd4fe2804
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11641
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 34e65c4b3aac3cbe80ec336c367b78b01376a7a3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 13 00:53:20 2015 +0530

    cluster/ec: Prevent data corruptions
    
    - On lock reuse preserve 'healing' bits
    - Don't set ctx->size outside locks in healing code
    - Allow xattrop internal fops also on the fop->mask.
    
    Change-Id: I6b76da5d7ebe367d8f3552cbf9fd18e556f2a171
    BUG: 1232678
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11640
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit c4009f895818a84ed4c3bb8f826e78d17a6a5b3e
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Jul 8 12:42:50 2015 +0530

     ec : Implement check for the cluster.heal-timeout values
          for disperse volume.
    
     Problem : User can set  wrong values for cluster.heal-timeout
          using cli. Any value like string, negative numbers
          or 0 could be set.
    
     Solution : Check the value given by user. It should be numerical,
          non negative and within the range.
    
    Change-Id: I5184ef1a11bb2c225f42ac9ccb1ba680a86cfe09
    BUG: 1239037
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/11573
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 8c39f1487461fb366e6156955f5045ee9f71c1a9
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jul 13 16:16:00 2015 +0530

    rpc-transport: socket_poller fixes for proper working of mgmt encryption
    
    socket_poller, the polling function used by ssl own_thread, had two
    issues which lead to GlusterD crashes when using management encryption
    
    Issue 1
    -------
    socket_poller calls functions which require THIS to be set. But, THIS
    was being set conditionally. Because of this, functions could sometimes
    be called without THIS being set. For example, rpc_transport_notify
    could be called for an accepted client socket without THIS being set, as
    THIS was only set it the transport wasn't yet connected. This would
    cause the process to crash when THIS was accessed by the called
    functions.
    
    To fix this, THIS is being set at the start of socket_poller
    unconditionally.
    
    Issue 2
    -------
    DISCONNECT notify was being sent on the listener transport instead of
    the client transport. The DISCONNECT event was converted to a
    LISTENER_DEAD event in rpcsvc_handle_disconnect, as it could not find
    the listener socket of the listener socket. GlusterD was notified of a
    LISTENER_DEAD event instead of a DISCONNECT and failed to remove the
    client transport from its xprt_list. The transport would subsequently
    be freed, leaving the xprt_list with a corrupted/invalid entry. Later,
    when GlusterD would iterate over the xprt_list to send notifications, it
    would crash when the invalid entry was accessed.
    
    To fix this, DISCONNECT notification in socket_poller is sent on the
    client socket, as it is done in the epoll handler.
    
    Change-Id: I0370b7c6d7eb13de10ebf08d91a4a39dc7d64c7a
    BUG: 1242570
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/11650
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 28d218d7ed00be0e15de29ee3083f184c6c3d1c6
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Jul 13 23:34:17 2015 +0530

    glusterd: Fix failure in replace-brick when src-brick is offline
    
    Change-Id: I0fdb58e15da15c40c3fc9767f2fe4df0ea9d2350
    BUG: 1242609
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11651
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f7b9379a0a03fb1d2df56bbfc8dca06f5f3b8437
Author: Pamela Ousley <pousley@redhat.com>
Date:   Wed Jun 17 15:07:55 2015 -0400

    cluster/tier : fix for logical bugs/timing errors in tier.t
    
    The md5sum fingerprints were not correctly compared after moving
    files between the hot and cold tiers.
    
    This version of tier.t uses a new function, "check_counters", to
    ensure that the number of promotions/demotions is as expected.
    This is intended to avoid spurious timing-related errors that were
    seen with the old script.
    
    Change-Id: I4a0ae7315493bfd307a0f68f21fa3ea33c88b08f
    BUG: 1231268
    Signed-off-by: Pamela Ousley <pousley@redhat.com>
    Reviewed-on: http://review.gluster.org/11285
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit a53482df76ad2527aa7a91b5a10c64d26477d1f2
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat Jul 11 12:27:02 2015 +0530

    rpcsvc: add request's address in log
    
    This helps in identifying the remote endpoint whose request arrived at
    an non-privileged port.
    
    Change-Id: Ie58155e00229cfcbd0ca5221d79e2e90efb3e2b3
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/11631
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 67a53554ed75081612b56a5658fd569dc5aaa785
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri Jun 26 16:33:49 2015 -0400

    cluster/tier: fixes for migration over ec as cold tier
    
    An opendir is done in rebalance. The graph constructed when
    EC is used in tiering may have no local volumes (if
    all the hot volumes are on one node and all the others on
    another node). Previously the opendir only sent fops down
    the local subvolumes for migration. They must be sent down
    both the hot and cold subvolumes for tiering.
    
    When setxattr2() received a NULL subvolume; this dereferenced
    an uninitialized variable.
    
    When a lookup is done during creation of the destination
    file, the xattr dict is "polluted" with virtual xattrs.
    These cause subsequent xattrs in the new file to not be
    written by posix. They are required by EC.
    
    The inode gfid for "entry_loc" in gf_defrag_migrate_single_file()
    was not initialized. This made underlying translators
    think the gfid was 0, and failed migration.
    
    Change-Id: I6ccda8ca8e43485b9b354341bbfcb302496f632c
    BUG: 1236212
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11433
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 890e58f5d4d3db9477e36cac3d16798ffe3b0480
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed Jul 1 17:55:47 2015 +0530

    extra: "enable-shared-storage" key should create shared-storage
    
    Currently while creating shared storage it accept only
    "cluster.enable-shared-storage" key. It should also
    accept "enable-shared-storage" key.
    
    Change-Id: I4c68782f4b7927ec8cd725e411b0b9db17d9c48d
    BUG: 1238224
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11491
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit 14e80e6e5d2d5d4fa568019fbe30cffa52714f87
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jun 30 13:10:46 2015 +0530

    features/bitrot: move inode state just at the last moment
    
    Which was done at half the set expiry time resulting in actual
    IOs incrementing the object version. Now this is done just at
    the last moment with re-notification now cut-shorting into
    checksum calculation without waiting in the timer-wheel.
    
    BUG: 1242317
    Change-Id: If655b77d822ebf7b2a4f65e1b5583dd3609306e7
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11461
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 6beb9ca292a0653d3d082af9d30f519a99569a14
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Fri Jul 10 10:50:40 2015 +0530

    rdma : porting missing gf_log to gf_msg
    
    Change-Id: I036b43007fbcd0e528faab8d44e1a7fc820eaf1f
    BUG: 1242333
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11607
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 608a9f24954c716492d9dd69b1e56e439aa66243
Author: arao <arao@redhat.com>
Date:   Mon Feb 16 16:59:48 2015 +0530

    glusterd: Fixing dereference after null check
    
    CID: 1124557
    Checking for the pointer itself before dereferencing
    it to check for the variable's value it is pointed to.
    
    Change-Id: Idcbb034e4c6d58501697e01e90647b6233a5e5ba
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9661
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 46d4d7ade012f86044135dd4af3101f851484cda
Author: vmallika <vmallika@redhat.com>
Date:   Fri Jul 10 14:37:50 2015 +0530

    features/quota : Fix spurious failure
    
    Problem : Basically, in this test case a file is created
    which exceeds the quota limit. Once the limit is reached
    that file will be deleted. At the same moment we are
    testing inode-quota. It can so happen that before the
    marker updates the information related to deletion of
    file, a new file creation operation comes and sees that
    quota limit is still exceeded.
    
    Solution : Inducing a check to see if marker updation
    completed successfully.
    
    Updated all the test case which has the similar
    machanism and also moved the "usage" function
    to a common place "volume.rc"
    
    Change-Id: I36ddbc5ebbf1b74c9d326a0d1d5f3b32f20a906a
    BUG: 1229297
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11125
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2e44d1580497eb75f325ad3104249a425ddf592a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jun 30 11:22:31 2015 +0530

    ctr:Avoid assertion failure in lookup
    
    in ctr_lookup, the loc variable need not be comes with pargfid,
    though there is a parent for the inode. The same for loc->name
    also. From this patch, we will generate loc->name from loc->path
    
    Change-Id: I24a79554748139504ec09f77930f8208d3805977
    BUG: 1236128
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11459
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit d5246b38e68e80136bfc2a1c570189537b9de1ce
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue Jun 16 18:16:18 2015 +0530

    libglusterfs: delete duplicate code
    
    This patch saves cpu cyles by deleting duplicated code in most frequently
    used functions 'dict_set_static_bin' & 'dict_set_bin'  which is already
    repeated/executed in function 'bin_to_data'
    
    Change-Id: I8e18b3f2b321e06bb6bd5a67e1782cb159182dd2
    BUG: 1232304
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11255
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3a6b3dae15bba00860c3323ff8867c4845b877d6
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Fri Jul 10 23:12:28 2015 +0530

    features/posix : Avoid double free of a variable in posix_setxattr()
    
    The buffer acl_xattr is introduced in posix_setxattr() as part of
    http://review.gluster.org/#/c/11519/. This variable can be freed
    twice in the code path , one in dict_unref() and another by explicit
    GF_FREE() call in the code. This patch avoids the same.
    
    Change-Id: I31c6384e37ab8d8baaed7a53de668c2eb5d82338
    BUG: 1242030
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/11627
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bfbd710b675d61fb3e8eaecd70eca92f806c6d8d
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue Jun 9 15:25:20 2015 +0530

    build: fix gitclean target
    
    $ make gitclean   # deleting unexpected 'Makefile' files
    ...
    
    $ git status
    ...
    
      deleted:    extras/FreeBSD/Makefile
      deleted:    extras/command-completion/Makefile
      deleted:    extras/test/ld-preload-test/Makefile
    
    ...
    
    This change fix to ignore above built-in makefiles while executing
    'gitclean' target
    
    Change-Id: I5365f5a1fe5b36141a6fe7ba27c38a2158f9f3a3
    BUG: 1229639
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11136
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 7f21238bb918a9b6eefcff5d76516a92a9271ae2
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Sat Jul 11 15:47:18 2015 +0530

    access_control : avoid double unrefing of acl variable in its context.
    
    In handling_other_acl_related_xattr(), acl variable is unrefered twice
    after updating the context of access_control translator.So the acl variable
    stored in the inmemory context will become invalid one. When the variable
    accessed again , it will result in brick crash. This patch fixes the same.
    
    Change-Id: Ib95d2e3d67b0fb20d201244a206379d6261aeb23
    BUG: 1242041
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/11632
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 160e539e26ed1e17a0c2cad97dd28cc8cbce9d6d
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Fri Jul 3 15:12:23 2015 +0530

    logging: Fixed incorrect buffer size
    
    An incorrect buffer size passed in to_gf_msg_backtrace
    prevented the callers from being logged.
    
    Change-Id: I86104d6b3f611455308d5b3420dfb6d456070a23
    BUG: 1238952
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/11521
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 35b2cdcb7ac0a623274b6cceac33c0f7fb16873b
Author: vmallika <vmallika@redhat.com>
Date:   Fri Jul 10 16:04:16 2015 +0530

    quota/marker: inspect file/dir invoked without having
    quota xattrs requested
    
    In a lookup and build ancestry quota xattrs are
    not requested, it gives wrong assumption that
    quota xattrs are missing and tries to do
    healing process
    
    Change-Id: I7135101ec0edc72a6310dbb304227eaa3b16cb46
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11616
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 93d8af231927d3476f8a966505a0e7fab7181385
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Jul 10 14:50:29 2015 +0530

    glusterd: Send friend update even for EVENT_RCVD_ACC
    
    In a multi-network cluster, a new peer being probed into the cluster
    will not get all the addresses of the peer that initiated the probe in
    some cases as it doesn't recieve friend updates from other peers in the
    cluster.
    
    This happens when the new peer establishes connection with the other
    peers before the other peers connect to the new peer.
    
    Assuming, F is the initiator peer, O is one of the other peers in the
    cluster and N is the new peer, the following series of events occur on O
    when N establishes the connection first. N is already in the BEFRIENDED
    state on O, and the actions happening will refer the BEFRIENDED state
    table.
    
      EVENT_RCV_FRIEND_REQ -> results in handle_friend_add_req being called
                              which injects a LOCAL_ACC
      EVENT_RCVC_LOCAL_ACC -> results in send_friend_update being called
                              which should have sent an update to N, but O
                              has still not established a connection to N,
                              so the update isn't sent
      EVENT_CONNECTED      -> O now connects to N, this results in O sending a
                              friend_add req to N
      EVENT_RCVD_ACC       -> friend_add_cbk inject this event, but this event
                              results in a NOOP when in BEFRIENDED
    
    As a result this O doesn't recieve all the addresses of F. If the
    cluster contains any volumes with bricks attached to the missing
    addresses of F and O is restarted in this condition, GlusterD will fail
    to start as it wouldn't be able to resolve those bricks.
    
    This commit changes the EVENT_RCVD_ACC action for the BEFRIENDED state
    from a NOOP to send_friend_update. This makes sure that the new peer
    recieves the updates from the other existing peers, irrespective of who
    establishes the connection first, thus solving the problem.
    
    Change-Id: Id807bc3032cf4cb13a5ba83819f2d50c96e76e96
    BUG: 1241882
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/11625
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2992c18c1370ada476223b496e4e970d70cdd359
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Jul 10 11:23:07 2015 +0530

    syncop: Include iatt to 'syncop_link' args
    
    Include iatt to 'syncop_link' args to fetch proper attributes of
    the newly linked inode.
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    
    Change-Id: If6b92961bd7a89add3791ed3a9b494087348b492
    BUG: 1241788
    Reviewed-on: http://review.gluster.org/11611
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 11ac70c8b6aefe3e82b7f1bd3f661206465c3ef8
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jul 10 15:41:18 2015 +0200

    gfapi: correct symbol versioning in glfs-handles.h
    
    Some of the symbol versions exposed to Mac OS X systems are incorrect.
    glfs_h_lookupat() has been exported multiple times, for different
    versions. Seems to be a simple copy/paste error, but we have not spotted
    that during review :-/
    
    The only applications that could be affected by this correcting change,
    would need to have linked against the highest versions of
    glfs_h_lookupat(). Because Mac OS X is not a mainstream client-side
    environment, we do not need to take special precautions for it.
    
    BUG: 1202274
    Change-Id: I9ee909ce0f205faa9f110be2101fc6feae20df41
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11623
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 79106a754d4804074e5c5c6bfe1c388f7d314535
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Jul 8 14:35:45 2015 +0530

    libgfdb/sql: Fixing broken query of find_unchanged
    
    The find_unchanged query should be
    
              "write_heat <= defined_heat" AND "read_heat <= defined_heat"
       and not
              "write_heat <= defined_heat" OR "read_heat <= defined_heat"
    
    Change-Id: Ie82e02aafbb7ea14563007307de3350ea022049a
    BUG: 1240970
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/11577
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Joseph Fernandes
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3524a03a5e264087e33a17ed46425674d58777fc
Author: Meghana M <mmadhusu@redhat.com>
Date:   Fri Jul 10 04:23:31 2015 +0530

    NFS-Ganesha : Add-node does not copy "exports" directory correctly
    
    Add-node logic has to copy the "exports" directory into the
    new node in the same path. There was an error in copying to the correct
    path. Fixing it.
    
    Change-Id: I539d1d525cc5614594b76f2cff1ac93a926712cf
    BUG: 1241895
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11618
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 09b808f008150acb980cdf0cd4f945b57aeb71a0
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Jul 8 09:52:15 2015 -0400

    glusterd: use a real host name (instead of numeric) when we have one
    
    Change-Id: Ie9cc201204d3d613e3e585cab066a07283db902c
    BUG: 1241274
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/11587
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 87bce01f323621c106a7fde221ea406abede41fc
Author: Meghana M <mmadhusu@redhat.com>
Date:   Thu Jul 9 03:34:07 2015 +0530

    NFS-Ganesha : Export fails on RHEL 7.1
    
    We grep for CONFFILE parameter in "/etc/syconfig/ganesha"
    file to find out the path of the ganesha config file.
    In RHEL 7.1, this parameter does not exist in the file and
    we can't find out the ganesha config file. Export
    fails invariably due to this. Changing this pattern to
    a more generic one and default it to "/etc/ganesha/ganesha.conf"
    
    Change-Id: I4ac97b1b5ee4f5a7e448a351b7c6270385dffe61
    BUG: 1241480
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11594
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bcd89d50866080ebd5e4a1af4c3fe64832910f36
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Jul 6 14:47:58 2015 +0530

    features/bitrot: Scrub log improvement
    
    Change-Id: I4937a578185ebacd2558cb8e22f130cd10193188
    BUG: 1240219
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11547
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit c2cd3aeb0d88117f0929a733e9b05aa3e4d392ac
Author: vmallika <vmallika@redhat.com>
Date:   Wed Jul 8 22:22:50 2015 +0530

    quota/marker: fix spurious failure afr-quota-xattr-mdata-heal.t
    
    During quota-update process if inode info is present in size-xattr and
    missing in contri-xattrs, then in function '_mq_get_metadata', we set
    contri-size as zero (on error -2, which means usage info present, but inode info missing).
    With this we are calculating wrong delta and updating the same.
    
    With this patch we are ignoring errors if inode info in xattrs are missing
    
    Change-Id: I7940a0e299b8bb425b5b43746b1f13f775c7fb92
    BUG: 1241153
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11583
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 7f9108fc0a5c9543e18ad52759a3ebdf91900a33
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jul 2 12:22:49 2015 +0530

    quota/marker: use smaller stacksize in synctask for marker updation
    
    Default stacksize that synctask uses is 2M.
    For marker we set it to 16k
    
    Also move market xlator close to io-threads
    to have smaller stack
    
    Change-Id: I8730132a6365cc9e242a3564a1e615d94ef2c651
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11499
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 3d21219cdd53a5b6ef62501b042626133b34e0c1
Author: vmallika <vmallika@redhat.com>
Date:   Mon Jun 29 19:12:28 2015 +0530

    quota/marker: fix mem leak in marker
    
    Problem-1)
    Now the marker accounting happens in background,
    There is a possibility that before completing
    create_xattr_txn another create txn can be initiated
    for the same inode.
    suppose if few 100 txns are initiated
    before completion, this can block all synctask threads
    waiting on a lock and this can also consume lot of memory
    and can take more time to complete the background accounting
    operation.
    
    This patch improves the locking mechanism which
    can improve the performance as well reduce memory
    consumption
    
    Problem-2)
    For every lookup and for all inodes in readdirp
    we were initiating a new txn, this can result
    in more txn pending in synctask queue and
    lead to huge memory consumption. inspect
    file/dir should start a txn only if there
    is some delta
    
    Problem-3)
    When there are multiple write operations on
    same inode and all the synctask threads are busy.
    As we are checking for updation_status
    flag in background, all txn will be move to synctask queue.
    This can increase the mem usage.
    
    Only one txn for inode in a queue will be sufficient,
    so check and set updation falg before moving txn to
    background
    
    Change-Id: Ic42ce00f0a50ce51c7128ba68a1b6a0699a1cd14
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11457
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 7488acff20ef6ff8df76af07547695e0106f32ca
Author: vmallika <vmallika@redhat.com>
Date:   Tue Jul 7 16:03:26 2015 +0530

    quota/marker: set lk_owner when taking lock on parent in rename
    
    Before doing a rename operation marker takes inode lock on the file
    parent,
    here lk_owner is NULL and this can cause accounting problem with
    multiple rename on the same directory
    
    This patch fix the problem by setting lk_owner
    
    Change-Id: Ibb789e39b2833e425d0a5fca85282ff1465206cb
    BUG: 1240598
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11561
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 01b82c66155a8d92893a386d7a314c95e0f0702b
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jul 7 12:52:30 2015 +0530

    glusterd: Fix management encryption issues with GlusterD
    
    Management encryption was enabled incorrectly in GlusterD leading to
    issues of cluster deadlocks. This has been fixed with this commit. The
    fix is in two parts,
    
    1. Correctly enable encrytion for the TCP listener in GlusterD and
    re-enable own-threads for encrypted connections.
      Without this, GlusterD could try to esatblish the blocking SSL
      connects in the epoll thread, for eg. when handling friend updates,
      which could lead to cluster deadlocks.
    
    2. Explicitly enable encryption for outgoing peer connections.
      Without enabling encryption explicitly for outgoing connections was
      causing SSL socket events to be handled in the epoll thread. Some
      events, like disconnects during peer detach, could lead to connection
      attempts to happen in the epoll thread, leading to deadlocks again.
    
    Change-Id: I438c2b43f7b1965c0e04d95c000144118d36272c
    BUG: 1240564
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/11559
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b6a7a44079c724cbf6fb24c7ac83892f551dc5f6
Author: Anoop C S <anoopcs@redhat.com>
Date:   Thu Jul 9 11:06:01 2015 +0530

    features/ctr: Reduce the log-level for ctr-disabled message
    
    Since by default CTR translator is disabled, the following
    log message is being displayed in brick logs.
    
    [ctr-helper.c:256:extract_ctr_options] 0-gfdbdatastore: CTR Xlator is disabled.
    
    Therefore this change is to reduce the log-level to INFO.
    
    Change-Id: I3b82d6b0dc0445286f91490fb497167a36914a2b
    BUG: 1241379
    Signed-off-by: Anoop C S <anoopcs@redhat.com>
    Reviewed-on: http://review.gluster.org/11592
    Reviewed-by: Joseph Fernandes
    Tested-by: Joseph Fernandes
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 3c25f33162c981d18bf78d1fc3536496670959e9
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Jul 8 21:22:53 2015 +0530

    libgfdb/ctr: Fixing rename or update of link
    
    Fixing rename or updating of link in
    1) libgfdb : handling return from updatelink
    2) ctr xlator: correcting freeing of oldbase name in
                   hardlink list in the update link
    
    Change-Id: I1789c492b81876123cd456051a9ae495e876ad46
    BUG: 1241054
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/11584
    Tested-by: Joseph Fernandes
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c134bdd83a781452eff8c3e4abce3da4a997daa8
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Jul 8 12:08:25 2015 +0530

    gfapi: Update loc->inode accordingly in 'glfs_loc_link'
    
    In case if the inode already exits in the cache, inode_link
    returns the pointer to the exiting one instead of using loc->inode.
    This will result in issues if that invalid inodei(loc->inode) is referenced
    further. Fixed the same.
    
    Change-Id: I7d4a06043e4e731c8404532c47d482175dc2c277
    BUG: 1240916
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11572
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit ea7161bca1c9e0c91148fea8895041a08ed24830
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jul 8 10:14:40 2015 -0400

    common-ha: ganesha-ha.sh status tries to read ganesha-ha.conf
    
    status doesn't need to read the config
    
    Change-Id: Id02252abe52820dbc263f4a880bde72a23b121bd
    BUG: 1241133
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11581
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 41266ec75d729c53ab748aa2ac1fa0d0515b97d6
Author: vmallika <vmallika@redhat.com>
Date:   Mon Jul 6 16:18:45 2015 +0530

    quotad: create sock listener only after graph init is complete
    
    If FOPs are received before completing graph initialization,
    FOP path can crash while accessing uninitialized variables
    
    This patch fixes issue by not creating listener until
    graph initialization is complete and hence not receiving
    FOP request
    
    Change-Id: I4771e376410843dff44bfe819329a4632523d266
    BUG: 1240254
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11552
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 9384a824041aeef0e58644cc9fe71dc7fa13eb35
Author: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
Date:   Tue Jun 30 14:47:22 2015 +0530

    libglusterfs removing strerror in logging
    
    Change-Id: I8a0f40834da1151ddaef6139af3782bc076df57e
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/11464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 32207db25eea821dfb1abd033df1013d4b8fc622
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Jul 6 12:15:45 2015 +0530

    snapview-client: Allocate memory using GF_CALLOC
    
    loc->path memory should allocate through
    GF_CALLOC/GF_MALLOC, since it uses GF_FREE
    from loc_wipe.
    
    Change-Id: If3030175dfb07b0e0b6c0a30234857f8a0780035
    BUG: 1240184
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11543
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a6ba145589b626f4254873cd2dffcee37cbbd345
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 8 17:52:11 2015 +0530

    cluster/ec: Don't read from bricks that are healing
    
    BUG: 1232678
    Change-Id: I35503039e4723cf7f33d6797f0ba90dd0aca130b
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11580
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 34b3b00e5531c3992d913a65f60fe35f78b20f08
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jul 8 14:18:19 2015 +0530

    glusterd/snapd: Stop snapd daemon when glusterd is restarting
    
    Stop snapd daemon when glusterd is coming back, if uss
    is disabled, or volume is stopped.
    
    Change-Id: I4313ecaff19de30f3e9ea76881994509402ed5b0
    BUG: 1240952
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11575
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 50a9e209ca58d8690ca9e8f4d3b1fd16ce522b02
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jul 8 17:11:42 2015 +0530

    tests/uss: Wait for process to come up before testing stat
    
    Fix spurious failure where snapd takes a while to come up.
    
    Change-Id: I32931afd4ff78f8d930c70f49b26f08976033d42
    BUG: 1241071
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11579
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8c3cec03e324037ece79f3285fd2fddadce0dd29
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Sun Jul 5 12:57:39 2015 +0530

    snapshot/scheduler: Use /var/run/gluster/shared_storage/snaps/tmp_file
    for writing data into tmp file and then making an atomic rename to
    the required filename.
    
    The reason for using this location is that it adheres to
    the selinux policies.
    
    Also moving the update of the current_scheduler file,
    under the lock so as to avoid multiple writes
    
    Change-Id: I61e62b5daf6f1bce2319f64f7b1dfb8b93726077
    BUG: 1239269
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11535
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 638febc61deb78c30bcecd147f3bc3df3d85e0fe
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jul 2 09:26:44 2015 +0530

    cluster/ec: Remove locks in opendir
    
    With readdir[p] taking locks to figure out which bricks are
    good/bad, no need to take any locks on opendir.
    
    BUG: 1232172
    Change-Id: I4d924aeeaecab23af08c4598548a20d2a44cd849
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11506
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e45f9943e321324988f36eca9dbd4dbd8536b17c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 7 12:40:42 2015 +0530

    cluster/ec: Fix use after free bug
    
    In ec_lock() there is a chance that ec_resume is called on fop even before
    ec_sleep.  This can result in refs == 0 for fop leading to use after free in
    this function when it calls ec_sleep so do ec_sleep at start and ec_resume at
    end of this function.
    
    Change-Id: I879b2667bf71eaa56be1b53b5bdc91b7bb56c650
    BUG: 1240284
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11558
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit afa793ff16b349989ca7c958466eae15d2d003f9
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue May 12 16:36:55 2015 +0530

    libgfapi: Gracefully exit when glfd is invalid
    
    When glfs_* methods operating on glfd are invoked after calling
    glfs_close(), the program segfaults inside __GLFS_ENTRY_VALIDATE_FD
    trying to deference glfd->fd->inode which is invalid.
    
    Also, returning EBADF seemed more specific than EINVAL.
    
    BUG: 1221008
    Change-Id: I13a92dca52da9a300252b69e026581b3a9e931fd
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/10759
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit b1abcf61d927009dfd794316b02d683d0e6d32cc
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Jul 7 12:15:17 2015 +0530

    tests: Fix ./tests/bugs/replicate/bug-1238508-self-heal.t
    
    Test failed @
    http://build.gluster.org/job/rackspace-regression-2GB-triggered/12010/consoleFull
    (Reported by Vijaykumar M)
    
    Fix:
    s/afr_get_pending_heal_count/get_pending_heal_count
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    
    Change-Id: I69c44919ae68e3ebb9a5bc58a8e45a0a96fad62e
    BUG: 1238508
    Reviewed-on: http://review.gluster.org/11556
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 91e1d0dd620941c91794d697a8388cd524d2e3bf
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jul 6 15:05:43 2015 +0530

    glusterd/geo-rep: Fix failure of geo-rep pause
    
    Geo-replication pause fails if one or more of the nodes
    in the master cluster is not part of master volume.
    If the master volume bricks are not part of the node,
    it should be ignored. The check is added to fix the issue.
    
    Change-Id: Iba57d66b6db6919f42a95dd66e6db9ad1b21503b
    BUG: 1240229
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11549
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit df580c4431de6fbf10017b891059583a52a406eb
Author: vmallika <vmallika@redhat.com>
Date:   Fri Jul 3 17:32:04 2015 +0530

    quota: fix mem leak in quota enforcer
    
    Do inode_unref on parent
    
    Change-Id: I21d82eb8716dd73aa2dc291b3ae8506e4fb4ea8b
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11526
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 3e1866aee751a8e7870cdce5b171a9007029e63c
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Jun 16 15:18:50 2015 +0530

    glusterd: Correction in Error message for disperse
     volume create
    
     Problem: If all the bricks are on same server and
     creating "disperse" volume without using "force",
     it throws a failure message mentioning "replicate"
     as volume.
    
     Solution: Adding failure message for disperse volume too
    
    Change-Id: I9e466b1fe9dae8cf556903b1a2c4f0b270159841
    BUG: 1232183
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/11250
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit cd43a3e15ee2d0f551740bf8d15a45f1d1f17e96
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Sun Jul 5 12:21:31 2015 +0530

    glusterd/shared_storage: Use /var/lib/glusterd/ss_brick as shared storage's brick
    
    The brick path we use to create shared storage is
    /var/run/gluster/ss_brick.
    
    The problem with using this brick path is /var/run/gluster
    is a tmpfs and all the brick/shared storage data will be wiped
    off when the node restarts. Hence using /var/lib/glusterd/ss_brick
    as the brick path for shared storage volume as this brick and
    the shared storage volume is internally created by us (albeit on
    user's request), and contains only internal state data and no user data.
    
    Change-Id: I808d1aa3e204a5d2022086d23bdbfdd44a2cfb1c
    BUG: 1218573
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11533
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 87f512655f76e788a5a81c5de66ed55881cb5f82
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 6 14:23:56 2015 +0530

    cluster/ec: Don't read from bad subvols
    
    Change-Id: Ic22813371faca4e8198c9b0b20518e68d275f3c1
    BUG: 1232678
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11531
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 88a719648475a6bf8d83c69a3b63b3d8a9a338cb
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 2 12:44:01 2015 -0400

    build: Mac OS X build issues, configure.ac
    
    Mac has sqlite3, but no sysconf pkgconfig
    
    Change-Id: I516613656ea3877c1a019438352b3ef8b62da1f5
    BUG: 1238796
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11517
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit a95f5651b8e2159eedb2ab87e2253a233d3ecfe7
Author: vmallika <vmallika@redhat.com>
Date:   Fri Jul 3 15:16:57 2015 +0530

    posix: fix mem-leak in posix_get_ancestry error path
    
    Change-Id: I47c8a8f170151f6374fc0420278aedf3ff5443ee
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11522
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 5547db849770ff79a11a8bc1260478c56e4ffa9c
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Jul 6 15:45:45 2015 +0530

    protocol/server: Add null check to gf_client_put
    
    Change-Id: I8bab3cd7387f89743e15e7569f0bc83a7df3c754
    BUG: 1240161
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/11550
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit c9765bcb1557ab1e921080e7de4f3ebac1e424d5
Author: anand <anekkunt@redhat.com>
Date:   Mon Jun 8 00:19:00 2015 +0530

    glusterd: Get the local txn_info based on trans_id in op_sm call backs.
    
    Issue: when two or more transactions are running concurrently in op_sm,
    global op_info might get corrupted.
    
    Fix: Get local txn_info based on trans_id instead of using global txn_info for
    commands (re-balance, profile ) which are using op_sm in originator.
    
    TODO: Handle errors properly in call backs and completely remove the global op_info from
    op_sm.
    
    Change-Id: I9d61388acc125841ddc77e2bd560cb7f17ae0a5a
    BUG: 1229139
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/11120
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 69c48f592afad1eb15a1f355226bda077c2ec1ef
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 6 12:22:20 2015 +0530

    cluster/ec: Remove failed subvols from source/sink computation
    
    Change-Id: Ib0de34c86ee25de361ec821d4015296c514742e0
    BUG: 1240210
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11546
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c6742adc98a9747f5e16c242aaddc28ea991ec5a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 30 23:01:36 2015 +0530

    cluster/ec: Make background healing optional behavior
    
    Provide options to control number of active background heal count and qlen.
    
    Change-Id: Idc2419219d881f47e7d2e9bbc1dcdd999b372033
    BUG: 1237381
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11473
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 214101394bdea4ab57b8704467f450df4adbb8f6
Author: Anuradha Talur <atalur@redhat.com>
Date:   Fri Jul 3 11:35:46 2015 +0530

    cluster/afr : expunge first, impunge next in entry selfheal
    
    When entry self-heals are performed, the files/directories
    that are to be expunged should be removed first and then
    impunge should be done.
    
    Consider the following scenario :
    A volume with 2 bricks : b0 and b1.
    1) With following hierarchy on both bricks:
    olddir
    |__ oldfile
    
    2) Bring down b1 and do 'mv olddir newdir'.
    
    3) Bring up b1 and self-heal.
    
    4) Without patch, during self-heal the events occur in
    following order,
            a) Creation of newdir on the sink brick. Notice that
    gfid of olddir and newdir are same. As a result of which
    gfid-link file in .glusterfs directory still points to olddir
    and not to newdir.
    
            b) Deletion of olddir on the sink brick. As a part of
    this deletion, the gfid link file is also deleted. Now, there
    is no link file pointing to newdir.
    
    5) Files under newdir will not get listed as part of readdir.
    
    To tackle this kind of scenario, an expunge should be done first
    and impunge later; which is the purpose of this patch.
    
    Change-Id: Idc8546f652adf11a13784ff989077cf79986bbd5
    BUG: 1238508
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11498
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 33935401cc548b55afc8ed907e54f72ff3e567b4
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Jun 19 01:41:27 2015 +0530

    geo-rep: Fix fd referenced before assignment
    
    Fix fd reference before assignment in mgmt_lock
    function.
    
    Change-Id: Ie939d4262a59cae0817ae388658a000576ab69b8
    BUG: 1233411
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11318
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit adc704557a141a624fc702f7303b8b81582e1598
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 26 22:36:31 2015 -0400

    tools/glusterfind: RENAME and MODIFY issues
    
    If Modification happens before RENAME, GFID to Path Conversion
    converts it into New Path. Delete Modify Entry and insert again
    So that MODIFY <NEW NAME> comes after RENAME.
    
    Default value of pgfids and basenames changed to "" instead of NULL
    Also fixed RENAME issue of displaying "RENAME <NEW NAME> <NEW NAME>".
    Also fixed RENAME followed by missing MODIFY
    
    Change-Id: I8202f6e6ec33f7bd921e71da38677f2ee2dab87a
    BUG: 1236270
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/11443
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 0fdf6c9db5114c77cd846c71699eb877d41ad6ae
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 2 12:43:09 2015 -0400

    build: Mac OS X build issues, no spinlock, need sys_lgetxattr
    
    use regular locks, use our syscall wrappers in libglusterfs
    
    Change-Id: I7e0d00956366806af041b69b65d1f169aa0d2ae2
    BUG: 1238793
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11515
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 78232678ad45cf8d12b991ea1ff441fbcdc3a601
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 2 12:08:45 2015 -0400

    build: Mac OS X build issues, header guard macros
    
    clang compiler errors
    
    Change-Id: I0aaa9f4353afd34e0e49ccb579b630a768c6c22a
    BUG: 1238788
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11513
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit adcc9495f93db24f9bff08ea21eb86e8905b0f07
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jul 2 12:12:53 2015 -0400

    build: Mac OS X build issues, gfapi symbol versions
    
    fix broken symbol versions
    
    Change-Id: I153b87d80895ddd4718d0a9e51b4c0712b178bd4
    BUG: 1238791
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11514
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 81cb71e9317e380b1d414038223c72643b35e664
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Jun 10 00:08:39 2015 +0530

    access-control : validating context of access control translator
    
    By introduction of new acl conversion from http://review.gluster.org/#/c/9627/,
    an acl can be set using GF_POSIX_ACL_*_KEY xattrs without notifying the
    access-control translator. So evenif an acl is set correctly at the backend, it
    might not work properly because access-control holds wrong acl information in
    its context about that file.
    
    Note : This is a simple workaround. The actual solution consists of three steps:
    1.) Use new acl api's for acl conversion.
    2.) Move the acl conversion part from access-control translator
    3.) Introduces standard acl structures and libaries in access-translator
    for caching, enforcing purposes.
    
    Change-Id: Iacb6b323810ebe82f7f171f20be16429463cbcf0
    BUG: 1229860
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/11144
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit cef17206141be2d4d8d6700afb6701e7f97cacab
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jul 2 05:19:19 2015 -0700

    Revert "rpc: By default set allow-insecure, bind-insecure to on"
    
    This reverts commit 5bf6522562990f7490d9fc226d58f19891bfb7a4.
    
    This patch introduced a regression where client no longer binds to
    privileged port. This is causing lots of regressions. Hence reverting
    this patch for now and will be resent after suitable modifications.
    
    Change-Id: Id697013ca6474e9c192e8f58c8179522fa5d397e
    Reviewed-on: http://review.gluster.org/11507
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2f5355f76a8168bc504cba8237f0825fc181fce8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jul 1 12:06:42 2015 +0530

    libgfchangelog: Fix example programs
    
    Incorporate the new API 'gf_changelog_init'
    introduced in libgfchangelog which should
    be called before 'gf_changelog_register'.
    
    Change-Id: I10a9dd5ff3ecc64fd61dcb6b1aa53739e0bdeedd
    BUG: 1238063
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11479
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8def0f28c908224359a04ec2f658a3ba241c7249
Author: Meghana M <mmadhusu@redhat.com>
Date:   Tue Jun 30 23:47:39 2015 +0530

    NFS-Ganesha : Unexport fails after S31ganesha-start script is run
    
    The dbus-send script extracts the export ID from the export config file.
    It expects the export ID to be written in a particular format. The post-phase
    hook-script created the export file in a different format,and the dbus-send
    never gets the correct export ID because of this.
    Fixing the issue by replacing the write_conf function in the
    S31ganesha-start hook-script.Also, NFS-Ganesha service stops when dbus signal is sent more
    than once on the same export. Consecutive start/stop operations creates problems.
    Fixing all the issues at once.
    
    Change-Id: Ibf639eb3556b1e51dd8dcb0c784a6a7f07badb97
    BUG: 1238054
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11477
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4242857196697d3fcfc0c7a75ede4a666518ea0b
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Jul 1 16:54:55 2015 +0530

    protocol/server: fail setvolume if any of xlators is not initialized yet
    
    We can only start recieving fops only when all xlators in graph are
    initialized.
    
    Change-Id: Id79100bab5878bb2518ed133c1118554fbb35229
    BUG: 1236945
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/11490
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit c1a8ae20bd055227921d199b952582eca4104f67
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Jun 12 15:12:05 2015 +0530

    libgfapi: send explicit lookups on inodes linked in readdirp
    
    If the inode is linked via readdirp, then the consuners of gfapi which are using
    handles (got either in lookup or readdirp) might not send an explicit lookup on
    that object again (ex: NFS, samba, USS). If there is a replicate volume where
    the replicas of the object are not in sync, then readdirp followed by fops might
    lead data being served from the subvolume which is not in sync with latest
    data. And since lookup is needed to trigger self-heal on that object the
    consumers might keep getting wrong data until an explicit lookup is not done.
    
    Fuse handles this situation by sending an explicit lookup by itself (fuse
    xlator) on those inodes which are linked via readdirp, whenever a fop comes on
    that inode.
    
    The same procedure is done in gfapi as well to address this situation.
    
    Thanks to shyam(srangana@redhat.com) for valuable inputs
    
    Change-Id: I64f0591495dddc1dea7f8dc319f2558a7e342871
    BUG: 1236009
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11236
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit e7f2547f89dbcd90cdb3714f63620a36bdc2ef3a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 1 22:32:44 2015 +0530

    libglusterfs: Use GF_CALLOC/GF_FREE instead of CALLOC/FREE
    
    - Also removed numbers for the types as the string form of type is printed in
      statedump now, so the numbers are not needed anymore.
    
    Change-Id: I6e8c15a1dc8cb6187842f96f1d46ec0f26a602b4
    BUG: 1237381
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11495
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fb20db2078dd7fe1a202f8c0c6f8bd7ecc7ff875
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 30 18:45:36 2015 +0530

    cluster/ec: Add throttling in background healing
    
    - 8 parallel heals can happen.
    - 128 heals will wait for their turn
    - Heals will be rejected if 128 heals are already waiting.
    
    Change-Id: I2e99bf064db7bce71838ed9901a59ffd565ac390
    BUG: 1237381
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11471
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit c66026b9bf521172f49ce36a5a7b94fae1bbf267
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 30 22:09:57 2015 +0530

    cluster/ec: Remove dead code
    
    Change-Id: I99d7a038f29cebe823e17a8dda40d335441185bc
    BUG: 1237381
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11472
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit efd49999ee956b0414d062c6493ab02300b21788
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jul 1 11:44:53 2015 +0530

    protocol/server: Correctly reconfigure auth.ssl-allow
    
    auth.ssl-allow wasn't being handled during reconfigure. This prevented
    the ssl-allow list from being live reloaded.
    
    Change-Id: If3435793a5684881b012de77cb254b1847b37810
    BUG: 1238072
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/11487
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1701239a4ef34c1780e2aa9cbc2843626bf61e2f
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Jun 26 11:53:11 2015 +0530

    cluster/dht: use refcount to manage memory used to store migration
    information.
    
    Without refcounting, we might free up memory while other fops are
    still accessing it.
    
    BUG: 1235927
    Change-Id: Ia4fa4a651cd6fe2394a0c20cef83c8d2cbc8750f
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/11418
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit d56b2eecbb7067f11c88d94cc87335040bbad0a3
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Jun 30 19:26:27 2015 +0530

    common-ha: Fix '/var/lib/nfs/statd/state' path creation
    
    '/var/lib/nfs/statd/state' which contains NSM state number
    should be a file instead of directory.
    
    Change-Id: Id008b4f4dd810fe6d6b4d2599cbc0b488010384b
    BUG: 1237174
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11468
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit e9807b8e5799cd5f62fcaa1f228bb470f4bc1157
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Jun 30 11:15:54 2015 +0530

    tiering/quota: failed to match subvolume
    
    quota daemon choose subvolume for a volume using
    volume-id specified in graph. For that it expect
    a subvolume (DHT) to be named as volume-id. But
    tiering translator comes above dht, so it failed to
    match the correct subvolume.
    
    Change-Id: I63d4b63cd8fb2806bc7b2b2f100dbef62202e6da
    BUG: 1236128
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11431
    Reviewed-by: Joseph Fernandes
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 5bf6522562990f7490d9fc226d58f19891bfb7a4
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed Jun 24 12:21:02 2015 +0530

    rpc: By default set allow-insecure, bind-insecure to on
    
    since we now use SSL (Secure Sockets Layer) for the security issues, the patch
    changes the default setting to allow connections/requests from non-privilaged
    ports by setting allow-insecure and bind-insecure to 1
    
    Also added bind functionality for insecure binding which can select from
    available local ports dynamically
    
    BUG: 1232658
    Change-Id: I927e112223f33611452093e38cd846a0b9347e57
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/11039
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 64f36a04d07fc03aeda2ca7921f874ae0db19fa7
Author: Meghana M <mmadhusu@redhat.com>
Date:   Mon Jun 29 06:16:47 2015 +0530

    NFS-Ganesha : Exporting volume fails
    
    Due to a recent fix, the dbus-send.sh looked
    for a .export_added file even before it was
    created. This resulted in the ganesha.enable
    option failing consistently. Fixing it.
    
    Change-Id: I26a68578551b6e38e49a9997e6f6f983fd668971
    BUG: 1236561
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11456
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b7b2b14c1f1ea1d232c5a5d5901c00bd187aa841
Author: Anuradha Talur <atalur@redhat.com>
Date:   Mon Jun 29 13:05:35 2015 +0530

    doc : Steps to analize coredumps generated by regression machines.
    
    Change-Id: Iadd879227a08d0dc0706363e7c6c30a6805e19ff
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11453
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit b343155815716094a70c5428c26ddcb0980a031e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat May 9 07:23:09 2015 +0530

    tests: Add the command being 'TEST'ed in all gluster logs
    
    Appends all commands being run under the test framework into the logs
    with time stamps. Its a hack but I find it very useful to see what
    sections of the logs (across all logs) need to be analysed between
    execution of 2 commands.
    
    Here's a sample output:
    [2015-06-26 13:25:15.866764479]:++++++++++ G_LOG:tests/basic/afr/quorum.t: TEST: 46 ! test_write ++++++++++
    [2015-06-26 13:25:15.872002] I [afr-common.c:1682:afr_local_discovery_cbk] 0-patchy-replicate-0: selecting local read_child patchy-client-1
    [2015-06-26 13:25:15.874559] W [fuse-bridge.c:723:fuse_truncate_cbk] 0-glusterfs-fuse: 81: TRUNCATE() /a => -1 (Read-only file system)
    [2015-06-26 13:25:15.880554623]:++++++++++ G_LOG:tests/basic/afr/quorum.t: TEST: 47 abc cat /mnt/glusterfs/0/b ++++++++++
    [2015-06-26 13:25:15.897767878]:++++++++++ G_LOG:tests/basic/afr/quorum.t: TEST: 48 gluster --mode=script --wignore volume set patchy cluster.quorum-reads on ++++++++++[2015-06-26 13:25:15.994410] I [glusterfsd-mgmt.c:51:mgmt_cbk_spec] 0-mgmt: Volume file changed
    [2015-06-26 13:25:17.098519] I [glusterfsd-mgmt.c:51:mgmt_cbk_spec] 0-mgmt: Volume file changed
    [2015-06-26 13:25:17.099241] I [glusterfsd-mgmt.c:51:mgmt_cbk_spec] 0-mgmt: Volume file changed
    [2015-06-26 13:25:17.099685] I [glusterfsd-mgmt.c:51:mgmt_cbk_spec] 0-mgmt: Volume file changed
    [2015-06-26 13:25:17.100055] I [glusterfsd-mgmt.c:51:mgmt_cbk_spec] 0-mgmt: Volume file changed
    [2015-06-26 13:25:17.105896] W [MSGID: 108003] [afr.c:94:fix_quorum_options] 0-patchy-replicate-0: quorum-type auto overriding quorum-count 2
    [2015-06-26 13:25:17.105936] W [MSGID: 108001] [afr.c:189:reconfigure] 0-patchy-replicate-0: Client-quorum is not met
    [2015-06-26 13:25:17.107438] I [glusterfsd-mgmt.c:1507:mgmt_getspec_cbk] 0-glusterfs: No change in volfile, continuing
    [2015-06-26 13:25:17.108724] I [glusterfsd-mgmt.c:1507:mgmt_getspec_cbk] 0-glusterfs: No change in volfile, continuing
    [2015-06-26 13:25:17.110082] I [glusterfsd-mgmt.c:1507:mgmt_getspec_cbk] 0-glusterfs: No change in volfile, continuing
    [2015-06-26 13:25:17.110599] I [glusterfsd-mgmt.c:1507:mgmt_getspec_cbk] 0-glusterfs: No change in volfile, continuing
    [2015-06-26 13:25:17.109678070]:++++++++++ G_LOG:tests/basic/afr/quorum.t: TEST: 49 1 mount_get_option_value /mnt/glusterfs/0 patchy-replicate-0 quorum-reads ++++++++++
    [2015-06-26 13:25:17.117801] I [afr-common.c:1682:afr_local_discovery_cbk] 0-patchy-replicate-0: selecting local read_child patchy-client-1
    
    Change-Id: Ib51284a0384508350579babaf1ae69cb372e0baa
    BUG: 1233018
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10667
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 7a2fb3694d74ff9ab64d1cbaa113a5428a92269f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jun 1 16:10:40 2015 +0200

    tests: use single-brick volume for mount-nfs-auth.t
    
    When running with the replica-3 volume, the "big_write" test sometimes
    becomes unresponsive. This seems to be an issue (bug 1226941) in the
    RPC/socket-layer, and not related to the NFS test itself.
    
    BUG: 1163543
    Change-Id: I51115e4b68d45f3ef7902b4f7a8535518d09408f
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11085
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 381afd4f480533f212e1f62a0ccfd9dcf7248e17
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jun 23 00:03:05 2015 +0200

    nfs: a unix-domain-socket should not be created as fifo
    
    Change-Id: Ic6a23165df1703b330636a059967c3c674dbde57
    BUG: 1235231
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11355
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7b51bd636fc5e5e1ae48a4e7cba48d0d20878d15
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 31 16:27:44 2015 +0200

    nfs: refcount each auth_cache_entry and related data_t
    
    This makes sure that all the auth_cache_entry structures are only free'd
    when there is no reference to it anymore. When it is free'd, the
    associated data_t from the auth_cache->cache_dict gets unref'd too.
    
    Upon calling auth_cache_purge(), the auth_cache->cache_dict will free
    each auth_cache_entry in a secure way.
    
    Change-Id: If097cc11838e43599040f5414f82b30fc0fd40c6
    BUG: 1226717
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11023
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 67f7562b5cc9e42774d1dc569471f86f61eef040
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 31 14:39:51 2015 +0200

    nfs: add a gf_lock_t for the auth_cache->cache_dict
    
    This is the 1st step towards implementing reference counters for the
    auth_cache_entry structure. Access to the structures should always be
    done atomically, but this can not be guaranteed by the a dict.
    
    Change-Id: Ic165221d72f11832177976c989823d861cf12f01
    BUG: 1226717
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11021
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 5f76ff1beaaf1fd1c85c43a166c289f9094a379b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jun 17 23:33:25 2015 +0200

    build: always include the VERSION file in 'make dist'
    
    Building a 'make dist' tarball from a non-git directory fails to include
    the VERSION file. This subsequently fails to set the version in the
    installation directories (for the xlators) and the RPM packaging can not
    find the correct files.
    
    This change makes sure to include a VERSION file in the 'make dist'
    tarball, no matter from where 'make dist' is run. It mainly addresses
    this use case:
    
       $ git clone ... && cd glusterfs
       $ ./autogen.sh
       $ mkdir /tmp/workdir
       $ cd /tmp/workdir
       $ $OLDPWD/configure
       $ make dist
    
    Change-Id: I3e87b5e16118b68d065fe99790d4b17e0cef9189
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11297
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit fb2f25cfbc26cd61370742d2453db63185194982
Author: Kotresh HR <khiremat@redhat.com>
Date:   Sun Jun 28 13:45:31 2015 +0530

    feature/performace: Fix broken build
    
    Fix the build broken because of patch
    http://review.gluster.org/#/c/9822/
    
    Change-Id: I0ee502c0fad5be87186c80ab4729036f52f85fa3
    BUG: 1194640
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11451
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit b147ebb158c9f516ae2d815aaf1cd270efd5ebcb
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Jun 28 10:15:44 2015 +0200

    Revert "Upcall/gfapi: Return ENOTSUP when upcall feature is disabled"
    
    This reverts commit b68f671b2b8a0aafef8f98145aee7044edaa907d from
    http://review.gluster.org/11196 . The change depends on modifications to
    the cluster xlators, but these are still partially under review.
    
    Dropping this change now, it causes regression tests to fail.
    
    Change-Id: If5ae4a519c9c6312cdb2e2a31acce4b1901f9442
    BUG: 1231132
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11452

commit 049c8eec304d9548fccb127ee8ce82f179bc41b0
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu Jun 25 15:04:18 2015 +0530

    gfapi : symlink resolution for glfs_object
    
    Generally posix expects symlink should be resolved, before performing an
    acl related operation. This patch introduces a new api glfs_h_resolve_symlink()
    which will do the same.
    
    Change-Id: Ieee645154455a732edfb2c28834021bab4248810
    BUG: 1209735
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/11410
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b68f671b2b8a0aafef8f98145aee7044edaa907d
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Jun 12 13:45:09 2015 +0530

    Upcall/gfapi: Return ENOTSUP when upcall feature is disabled
    
    Changes to detect the list of upcall events enabled using GF_FOP_IPC
    and return ENOTSUP to applications in case if they poll for any of
    the events disabled.
    
    Change-Id: Icc748054ef903598288119dbe99b1e337174662a
    BUG: 1231132
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11196
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 58a736111fa1db4f10c6646e81066434260f674f
Author: arao <arao@redhat.com>
Date:   Fri Mar 6 12:33:05 2015 +0530

    afr: Porting messages to new logging framework
         updated
    
    Change-Id: I94ac7b2cb0d43a82cf0eeee21407cff9b575c458
    BUG: 1194640
    Signed-off-by: arao <arao@redhat.com>
    Signed-off-by: Mohamed Ashiq <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/9897
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7a3736b4a46dd07d65e27d892a85299a37fdd9a2
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Fri Jun 26 14:56:53 2015 +0530

    rdma : removing duplicate printing of error string in gf_msg
    
    Change-Id: I206cf80392d430f35558cc11699402c4cef12527
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11426
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 0a24b8f2be5f8b124d76a13f2a4b6cb9058c9a30
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jun 24 20:06:01 2015 +0530

    features/bit-rot-stub: do not allow setxattr and removexattr on bit-rot xattrs
    
    * setxattr and {f}removexattr of versioning, signature and bad-file xattrs are
      returned with error.
    
    Change-Id: Ib423466195d1d8e4c6f80c2906a574e21ed624fb
    BUG: 1210689
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11389
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 15dcfe98caa573e87d898cb66c13ef7187730c6b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue May 26 19:22:14 2015 +0530

    features/bit-rot-stub: deny access to bad objects
    
    * Access to bad objects (especially operations such as open, readv, writev)
      should be denied to prevent applications from getting wrong data.
    
    * Do not allow anyone apart from scrubber to set bad object xattr.
    
    * Do not allow bad object xattr to be removed.
    
    Change-Id: Ia9185a067233a9f26e3d41d41d11d9a4eb0da827
    BUG: 1210689
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11126
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit c2f577c1caea959caf6d3c4b00f7c68c34a26edb
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jun 18 16:31:57 2015 +0530

    quota: Fix statfs values in EC when quota_deem_statfs is enabled
    
    When quota_deem_statfs is enabled, quota sends aggregated statfs values
    In EC we should not multiply statfs values with fragment number
    
    Change-Id: I7ef8ea1598d84b86ba5c5941a2bbe0a6ab43c101
    BUG: 1233162
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11315
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 3741804bec65a33d400af38dcc80700c8a668b81
Author: arao <arao@redhat.com>
Date:   Mon Jun 22 11:10:05 2015 +0530

    Logging: Porting the performance translator
             logs to new logging framework.
    
    Change-Id: Ie6aaf8d30bd4457bb73c48e23e6b1dea27598644
    BUG: 1194640
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9822
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 911e9228f31e89fe5df6e2282ce449b2a94c42b1
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Thu Jun 25 00:57:00 2015 +0530

    glusterd: Porting left out log messages to new framework
    
    Change-Id: I70d40ae3b5f49a21e1b93f82885cd58fa2723647
    BUG: 1235538
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/11388
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 2b9b3ef3b646989bbc0412dca187b3f5fcad3283
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 15:46:01 2015 +0530

    mem-pool,stack,store,syncop,timer/libglusterfs : Porting to a new logging framework
    
    Change-Id: Idd3dcaf7eeea5207b3a5210676ce3df64153197f
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10827
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit f5f5cef19e2afa1e2bcee896269e004353d3180f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jun 22 17:06:07 2015 +0530

    storage/posix: Introduce flag instructing posix to perform prestat, writev and poststat atomically
    
    Change-Id: I9b52ddaed4e306e9a49f39c86450c94bea843a7b
    BUG: 1233617
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11345
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 43aea2da863d94079dbf4dfceabee41a0be67ef7
Author: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
Date:   Thu Jun 25 12:52:57 2015 +0530

    common-utils/libglusterfs : removing strerror to avoid duplicate printing of error message
    
    Change-Id: I0a1c99ae7a2efc657e3465b21dd238e725ae236c
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>
    Reviewed-on: http://review.gluster.org/11400
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 06d5085f8ab222c10df1980ca23919c0e34284a1
Author: Anuradha <atalur@redhat.com>
Date:   Tue Jun 16 15:57:30 2015 +0530

    cluster/afr : truncate all sinks files
    
    Problem : During data self-heal of sparse files,
    sparseness of files is lost.
    
    Cause : Earlier, only files with larger ia_size in sinks
    were being truncated to ia_size of source. This caused
    checksum mismatch of sparse blocks when ia_size of files
    in sinks were lesser than ia_size of source file.
    Leading to unnecessary healing of sparse blocks.
    As a result of which sparseness of files was lost.
    
    Solution : truncate files in all the sinks irrespective of
    their size with respect to the source file. After this change,
    checksum won't mismatch for sparse blocks and heal won't
    be triggered. As a result, sparseness of the files will
    be preserved.
    
    Other fixes in this patch :
    1) in afr_does_size_mismatch(), check for mismatch only
    in sources. Previously, the check was being done for all
    children in a replica.
    
    2) in __afr_selfheal_data_checksums_match(), check checksum
    mismatch only for children with valid responses.
    
    Change-Id: Ifcdb1cdc9b16c4a8a7867aecf9fa94b66e5301c2
    BUG: 1232238
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11252
    Reviewed-by: Prasanna Kumar Kalever
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 0104b5869d89ac58cb13e10417626455c8ba2143
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 25 00:22:41 2015 +0530

    afr: Block fops when file is in split-brain
    
    For directories, block metadata FOPS.
    For non-directories, block data and metadata FOPS.
    Do not block entry FOPS.
    
    Change-Id: Id7f656f4a513b9d33c457dd7f2d58028dbef8e61
    BUG: 1235007
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11371
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit b335fbe14e0afbec3cf50409707f3c8df5d5c01d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 17 15:46:01 2015 -0400

    geo-rep: ignore ESTALE as ENOENT
    
    When DHT can't resolve a File it raises ESTALE, ignore ESTALE errors
    same as ENOENT after retry.
    
    Affected places:
        Xattr.lgetxattr
        os.listdir
        os.link
        Xattr.lsetxattr
        os.chmod
        os.chown
        os.utime
        os.readlink
    
    BUG: 1232912
    Change-Id: I02015f508d901e4a74dd48e1c52423e78eaf1dcd
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/11296
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 257668d97e0fd3f290ac8415c60dfc11510cc786
Author: Meghana M <mmadhusu@redhat.com>
Date:   Fri Jun 26 11:27:18 2015 +0530

    NFS-Ganesha : Automatically export volume after volume restart
    
    The export file was not getting created in the correct
    path. Fixing the path in this patch.
    
    Change-Id: If624266e1a934514868affb712514881d10239dc
    BUG: 1231738
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11432
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 14cf2bbe77fbbaee8ee3211ec841a4f1ef3a8380
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jun 25 19:49:59 2015 +0530

    protocol/server: Include a check to validate xprt->client
    
    rpc_transport entries(xprt) are added to the conf->xprt_list
    during client connection with the server. But the client object is created
    and assigned to that transport object only during GF_HANDSK_SETVOLUME. Hence
    till that period, there could be xprt entries in the xprt_list without client
    associated with it. Added a check to validate the client object during upcall
    notify.
    
    Change-Id: I11e2fcd8b0a67e35302ede478b777b72d1973456
    BUG: 1235542
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11411
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 35d24f0c967130ef8424660b5f6dfd182bb305c1
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jun 25 00:47:19 2015 +0530

    Upcall: Fix an issue with invalidating parent entries
    
    Any directory or file creation should result in cache-invalidation
    requests sent to parent directory. However that is not the case
    currently due to a bug while processing these requests in the
    upcall xlator. We need to do invalidation checks on parent inode.
    
    Fixed the same. Also fixed an issue with null client entries while
    sending upcall notifications.
    
    Change-Id: I3da7c79091291ba36fd8f8ebcfebcd77a192f250
    BUG: 1235542
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/11387
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 875aa01ec80e56d85d0bc6028c6f1417f6ab140f
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Jun 23 16:35:03 2015 -0400

    cluster/tier: stop tier migration after graph switch
    
    On a graph switch, a new xlator and private structures are
    created. The tier migration daemon must stop using the
    old xlator and private structures and begin using the
    new ones. Otherwise, when RPCs arrive (such as counter
    queries from glusterd), the new xlator will be consulted
    but it will not have up to date information. The fix
    detects a graph switch and exits the daemon in this
    case. Typical graph switches for the tier case would
    be turning off performance translators.
    
    Change-Id: Ibfbd4720dc82ea179b77c81b8f534abced21e3c8
    BUG: 1226005
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/11372

commit 26ef697318a7fec5ed82b000e3be4e30cfb16b50
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Sat Jun 20 14:38:12 2015 +0530

    tier/ctr: Ignore creation of T file and Ctr Lookup heal improvememnts
    
    1) Ignore creation of T file in ctr_mknod
    2) Ignore lookup for T file in ctr_lookup
    3) Ctr_lookup:
        a. If the gfid and pgfid in empty dont record
        b. Decreased log level for multiple heal attempts
        c. Inode/File heal happens after an expiry period, which is configurable.
        d. Hardlink heal happens after an expiry period, which is configurable.
    
    Change-Id: Id8eb5092e78beaec22d05f5283645081619e2452
    BUG: 1235269
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/11334
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 254218fa39d9317f759b4bfb4433478586eda0e3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 22 11:39:11 2015 -0400

    common-ha: fix delete-node
    
    N.B. delete-node is a designed to be "disruptive"
    
    surgically delete a node from the config and stop nfs-ganesh on that
    node.
    
    finish the implementation and fix a few minor issues
    
    Change-Id: I964bb72a76ee635b5fc484ec5b541e69eeececcd
    BUG: 1234474
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11353
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 87af7e72d8be95ac0f2ade88f3a9ba16392fd158
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Thu Apr 30 14:28:10 2015 +0530

    ec: Porting messages to new logging framework
    
    Change-Id: Ia05ae750a245a37d48978e5f37b52f4fb0507a8c
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/10465
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit add64f005b0afacb6a7c54abf55f1372a6acea52
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Apr 15 06:32:18 2015 -0400

    MAINTAINERS: add maintainers for tier feature
    
    Tiering
    M: Dan Lambright <dlambrig@redhat.com>
    M: Joseph Fernandes <josferna@redhat.com>
    S: Maintained
    F: xlators/cluster/dht/src/tier.c
    F: xlators/features/changetimerecorder
    F: libglusterfs/src/gfdb
    W: http://www.gluster.org/community/documentation/index.php/Features/data-classification
    
    Change-Id: I4b075a287a556551a2b72273901e1d3176f356aa
    BUG: 1194753
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10251

commit 6d3b289f8b9b30bca390e72b256aa161e3f65eb5
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Jun 25 16:30:40 2015 +0530

     EC : While Healing a file, set the config xattr
    
     Problem : trusted.ec.config attr was missing for the healed file
    
     Solution: Writing trusted.ec.config while healing a file.
    
    Change-Id: I340dd45ff8ab5bc1cd6e9b0cd2b2ded236e5acf0
    BUG: 1235246
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/11407
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 3925f5cf33df85807db812211552fc16c7850d0d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jun 25 00:18:01 2015 +0530

    geo-rep: Fix add user in mountbroker user management
    
    The CLI 'gluster system:: execute mountbroker user <USERNAME> <VOLUMES>'
    to set volumes associated with a user replaces existing user and associated
    volumes upon setting with existing user. This patch fixes it by appending
    the volumes if the user already exists.
    
    It also introduces following CLI to remove volume for a corresponding user.
    
    'gluster system:: execute mountbroker volumedel <USERNAME> <VOLUME>'
    <USERNAME>: username
    <VOLUME>: comman separated list of volumes to delete
    
    If it is the last volume to be deleted associated with the user,
    it will delete the user as well as it doesn't make sense to keep
    only user without volumes associated.
    
    Change-Id: I49f4b9279954d9f5d34aca2dd8a69c6f4b87fd19
    BUG: 1226223
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11385
    Reviewed-by: darshan n <dnarayan@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit aee44fccd450ac53421ebe729223ad1921e5f573
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Jun 22 19:01:39 2015 -0400

    features/changelog: Always log directory rename operations
    
    Directory renames are being ignored as special renames. Special
    renames can happen only on files. Hence always log directory
    rename operations in changelog.
    
    Change-Id: I4fbdb3e02e634a39a8846fb2f7a4c6cc2ba74400
    BUG: 1234286
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/11356
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit b15ba49546172786fb0416dd5a2802f638cacbb2
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Thu Jun 25 16:10:29 2015 +0530

    ganesha: volinfo is not persisted after modifying options
    
    ganesha disables gluster NFS when it is enabled. Gluster NFS
    is disabled by storing nfs.disable as "on" in volinfo of each
    volume in the cluster. But volinfo is not persisted after the
    change.
    
    Due to which wrong info is passed in handshake leading to volume
    checksum mismatch.
    
    Bug: 1235751
    Change-Id: Icd642f5068cc934bb77676fb8ef71b958a7b7384
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/11412
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 264776f7af6dffabc2216cf46fd1885a309f6e62
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jun 26 11:46:45 2015 +0530

    tests: fix basic/afr/replace-brick-self-heal.t failure
    
    Test fails with:
    not ok 28 Got "Binary file (standard input) matches" instead of "qwerty"
    FAILED COMMAND: qwerty get_text_xattr user.test
    /d/backends/patchy1_new/file5.txt
    not ok 29 Got "Binary file (standard input) matches" instead of "qwerty"
    FAILED COMMAND: qwerty get_text_xattr user.test
    /d/backends/patchy0/file5.txt
    Failed 2/29 subtests
    
    Fix:
    Pass -a flag to grep
    
    Change-Id: I69626fbf95a9ff756046363c5627cf98ea3f1df8
    BUG: 1207829
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11416
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8849a9a836af64ec150fb4909d02d5eff1304ade
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jun 25 14:58:50 2015 +0530

    quota: marker accounting goes bad with rename while writing a file
    
    With below test-case, marker accounting becomes bad:
    1) Create a volume with 1 brick
    2) fuse mount
    3) on one terminal write some data
       dd if=/dev/zero of=f1 bs=1M count=500 oflag=sync
    4) on another terminal execute below rename operation while the write is
    still in progress
        for i in {1..50}; do
            ii=`expr $i + 1`;
            mv f$i f$ii;
        done
    
    remove-xattr is already on while doing rename operation,
    we should not be doing again in background when reducing the
    parent size
    
    Change-Id: I969a64bb559e2341315928b55b99203e9ddee3f2
    BUG: 1235195
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11403
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 5485cb1b2e9b68a9746acc08289aaadb2cfe11c4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 15 16:32:06 2015 +0530

    cluster/ec: wind fops on good subvols for access/readdir[p]
    
    Change-Id: I1e629a6adc803c4b7164a5a7a81ee5cb1d0e139c
    BUG: 1232172
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11246
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 4f76b8d11a93cfb74667f6b3051186b86c1ec55b
Author: Anuradha <atalur@redhat.com>
Date:   Fri Jun 5 16:46:39 2015 +0530

    glusterd/ afr : set afr pending xattrs on replace brick
    
    This patch is part one change to prevent data loss
    in a replicate volume on doing a replace-brick commit
    force operation.
    
    Problem: After doing replace-brick commit force, there is a
    chance that self heal happens from the replaced (sink) brick
    rather than the source brick leading to data loss.
    
    Solution: During the commit phase of replace brick, after old
    brick is brought down, create a temporary mount and perform
    setfattr operation (on virtual xattr) indicating AFR to mark
    the replaced brick as sink.
    
    As a part of this change replace-brick command is being changed
    to use mgmt_v3 framework rather than op-state-machine framework.
    
    Many thanks to Krishnan Parthasarathi for helping me out on this.
    
    Change-Id: If0d51b5b3cef5b34d5672d46ea12eaa9d35fd894
    BUG: 1207829
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10076
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c9cbddf3d936f2bf1ac46084a74051096a5ac9a3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 26 09:05:26 2015 +0530

    libglusterfs: Fix build failure
    
    Change-Id: Ie589c866a53c0cfc167e31d1d14a11bf58c8dabf
    BUG: 1207829
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11413

commit 151c0ccf481d8e58581d7848f9aeb0e7704f0208
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 15:11:45 2015 +0530

    graph/libglusterfs : porting to a new logging framework
    
    Change-Id: I57ed5c979c15559443712a61f0b1a61c7f5557d8
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10822
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d3714f252d91f4d1d5df05c4dcc8bc7c2ee75326
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Jun 3 17:10:22 2015 +0530

    tiering/rebalance: tier daemon stopped with out updating status
    
    When a subvol goes down, tier daemon stopped immediately, and
    the status shows as "Progressing".
    
    With this change, with respect to tier xlator, when a subvol
    goes offline it will update the status as failed.
    
    Change-Id: I9f722ed0d35cda8c7fc1a7e75af52222e2d0fdb7
    BUG: 1227803
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11068
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit cd05e036117a27377af8ff4a1cdba09f1de0a8eb
Author: Anuradha <atalur@redhat.com>
Date:   Thu Jun 11 14:58:05 2015 +0530

    cluster/afr : set pending xattrs for replaced brick
    
    This patch is part two change to prevent data loss
    in a replicate volume on doing a replace-brick commit
    force operation.
    
    Problem: After doing replace-brick commit force, there is a
    chance that self heal might happen from the replaced (sink) brick
    rather than the source brick leading to data loss.
    
    Solution: Mark pending changelogs on afr children for
    the replaced afr-child so that heal is performed in the
    correct direction.
    
    Change-Id: Icb9807e49b4c1c4f1dcab115318d9a58ccf95675
    BUG: 1207829
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10448
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit e472e5d279e57cbddd75f81775505810664f29b3
Author: Anoop C S <achiraya@redhat.com>
Date:   Mon Jun 8 18:21:56 2015 +0530

    protocol/client: Properly handle return value in clnt_release_reopen_fd
    
    On account of a lock reacquire failure [in clnt_release_reopen_fd()]
    the return value, on submitting the client request for release of
    reopened fd, is not honoured correctly.
    
    Change-Id: Iff11523b2cc6f284e806855f32a13d8c4432f1c6
    BUG: 1227667
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/11088
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a51d4670ce663b957d91443d313c48b5f44254e3
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jun 16 23:53:32 2015 +0530

    snapshot: Fix terminating slash in brick mount path
    
    glusterd_find_brick_mount_path(), returns mount path,
    with a terminating '/' at the ned of the string in
    cases where the brick dir is a dir in the lvm root dir.
    
    Ignoring the terminating '/' fixes the issue.
    
    Change-Id: Ie7e63d37d48e2e03d541ae0076b8f143b8c9112f
    BUG: 1232430
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11262
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit df77ac5088ebe1a1645489d77bdae77ce6cbc828
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Jun 25 12:07:24 2015 +0530

    features/bitrot: convert pending gf_log() to gf_msg()
    
    Change-Id: Idfd245327b485459ccbda503510b8ca0127bb66c
    BUG: 1231619
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11396
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 913631a0edffaefc0fae73df46f80e19422ebed9
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jun 9 10:02:11 2015 +0530

    features/bitrot: handle scrub states via state machine
    
    A bunch of command line options for scrubber tempted the use of
    state machine to track current state of scrubber under various
    circumstances where the options could be in effect.
    
    Change-Id: Id614bb2e6af30a90d2391ea31ae0a3edeb4e0d69
    BUG: 1231619
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11149
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f1139ca4f8532c35f5f8024610ddc5a412f970e8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 24 20:00:11 2015 +0530

    geo-rep: Fix ssh issue in geo-rep
    
    In geo-rep mountbroker setup, workers fails with
    'Permission Denied' even though the public keys
    are shared to all the slave nodes. The issue
    is with selinux context not being set for .ssh
    and .ssh/authorizedkeys. Doing restorecon on
    these entries to set default selinux security
    context fixes the issue.
    
    Change-Id: I75e16d22f7a168de6c13b0c7571a7ab75761ae0d
    BUG: 1235359
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11383
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: darshan n <dnarayan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 6ab37f0cb4fd8313dab93360a41acbaf422f39b5
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Jun 4 08:50:48 2015 +0530

    features/bitrot: cleanup, v2
    
    This patch uses "cleanup, v1" infrastrcuture to cleanup scrubber
    (data structures, threads, timers, etc..) on brick disconnection.
    Signer is not cleaned up yet: probably would be done as part of
    another patch.
    
    Change-Id: I78a92b8a7f02b2f39078aa9a5a6b101fc499fd70
    BUG: 1231619
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11148
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 367049879e149e2cd3ec3ba96de7f495a30de180
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jun 17 09:35:22 2015 +0530

    Revert "tests/bitrot: Induce delay before invoking bitrot subcommands"
    
    This reverts commit a615f6c078c76791318c2a58efcc8baef18c25db.
    
    Change-Id: I8b014a99686cd4ee07da9d26bca561b420c8bec7
    BUG: 1231617
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11263
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 17b838ce18e0eb9dbfe9a540a3006023b19276e7
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jun 2 21:23:48 2015 +0530

    features/bitrot: cleanup, v1
    
    This is a short series of patches (with other cleanups) aimed at
    cleaning up some of the incorrect assumptions taken in reconfigure()
    leading to crashes when subvolumes are not fully initialized (as
    reported here[1] on gluster-devel@). Furthermore, there is some
    amount of code cleanup to handle disconnection and cleanup up data
    structure (as part of subsequent patch).
    
    [1] http://www.gluster.org/pipermail/gluster-devel/2015-June/045410.html
    
    Change-Id: I68ac4bccfbac4bf02fcc31615bd7d2d191021132
    BUG: 1231617
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11147
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 9b1305e549879e7698c46553bd91c722877d44cb
Author: vmallika <vmallika@redhat.com>
Date:   Wed Jun 24 11:56:30 2015 +0530

    quota/marker: fix mem-leak in marker
    
    When removing contribution xattr, we also need to free
    contribution node in memory.
    Use ref/unref mechanism to handle contribution node memory
    
    local->xdata should be freed in mq_local_unref
    
    There is another huge memory consumption happens
    in function mq_inspect_directory_xattr_task
    where dirty flag is not set.
    
    Change-Id: Ieca3ab4bf410c51259560e778bce4e81b9d888bf
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11361
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a1e32fbcfbfaf6e4c63e140b3b90a80dc748a269
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 15:53:19 2015 +0530

    call-stub,circ-buff,client_t,compat,dict/libglusterfs : Porting to a new logging framework
    
    Change-Id: Ie7d180e0ab2fed1270d66504606d1b2522884020
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10828
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9df8366174d57e3cd948d19efa9cdbadecfc012d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 24 18:30:18 2015 +0530

    geo-rep: Fix glusterd working directory
    
    Mountbroker setup in geo-replication requires
    the script 'set_geo_rep_pem_keys.sh to be
    run manually out of gluster context. Hence
    the ${GLUSTERD_WORKDIR} is never set. So
    getting glusterd working dir using 'gluster
    system:: getwd'.
    
    Change-Id: Ic2fe85e685016b383e38af0ea43c3f0628c16a32
    BUG: 1235292
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11381
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 461c66eb6a5d647fd265b34a8045e54e017446e0
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jun 23 10:38:27 2015 +0530

    geo-rep: Fix toggling of use_meta_volume config
    
    If meta-volume is deleted and use_meta_volume
    is set to false, geo-rep still fails complaining
    meta volume is not mounted. The patch fixes that
    issue.
    
    Change-Id: Iecf732197926bf9ce69112287fccbb1c34e58e6d
    BUG: 1234694
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11358
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit ef374774b8727b2f76915a1f88b26c83c77dde43
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 15:40:30 2015 +0530

    defaults,globals,iobuf,latency,logging,options,xlator/libglusterfs : porting to a new logging framework
    
    Change-Id: If6a55186cddc3d1c4d22e3d56b45358b84feeb49
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10826
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a9b6933ef097d2a81ce21a8aeda2acc569cd1509
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 15:21:46 2015 +0530

    event,parse-utils,quota-common-utils,rbthash/libglusterfs : Porting to new logging framework
    
    Change-Id: I13ae9a97fe442c06cf50fe77c63718ea0858dc4d
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10823
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6853d5091dd52059490e5e548c06faf1306079df
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jun 23 15:40:59 2015 +0530

    glusterd: Store peerinfo after updating hostnames
    
    Change-Id: I1d36ac63de810061d60edb28b6f591ae45d5cd3a
    BUG: 1234842
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/11365
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>

commit 0be38bdb4007c1bcb51545057e6402f6e14922cd
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Jun 17 14:20:14 2015 +0530

    glusterd: fix quorum calculation logic
    
    glusterd_get_quorum_cluster_counts () skips quorum calculation if it finds any
    of its peer in QUORUM_WAITING state. This means if any peer probe has been
    triggered and at the same point of time a transaction has been initiated, it
    might pass through the server quorum check which it should not.
    
    Change-Id: I44eda8905eab3349c9ebf2842e7131d4e758a528
    BUG: 1232686
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11275
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit b5fd1bca37ce612f825295ed03ac0544cf7e0b69
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jun 23 18:28:56 2015 +0530

    geo-rep: Fix geo-rep fanout setup with meta volume
    
    Lock filename was formed with 'master volume id'
    and 'subvol number'. Hence multiple slaves try
    acquiring lock on same file and become PASSIVE
    ending up not syncing data. Using 'slave volume id'
    in lock filename will fix the issue making lock
    file unique across different slaves.
    
    BUG: 1234882
    Change-Id: Ie3590b36ed03e80d74c0cfc1290dd72122a3b4b1
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11367
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 4c751009f668910a734cd400c10e8b3bdd6360a1
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jun 24 08:02:51 2015 +0530

    cluster/afr: Pick gfid from poststat during fresh lookup for read child calculation
    
    Change-Id: I12c1e4f67f4ec4affbe13d7daf871044a8a2a12e
    BUG: 1235216
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11373
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 2f0d36d16c241365760aaa6d857b7a4d438e1042
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Fri Apr 17 17:33:49 2015 +0530

    bit-rot : New logging framework for bit-rot log message
    
    Change-Id: I83c494f2bb60d29495cd643659774d430325af0a
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10297
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 1ff820381b33b65c54d5e7019a670b9dc1cc6844
Author: Meghana M <mmadhusu@redhat.com>
Date:   Fri Jun 19 05:48:05 2015 +0530

    NFS-Ganesha : Implement refresh-config
    
    It is important that we give an automatic way of refreshing the config
    when the user has changed the export file manually.
    Without this, the user will be forced to restart the server.
    Implementing refresh_config by utilizing two other scripts
    that are already in place.
    Making a few changes to make sure that "--help"
    doesn't throw unnecessary error messages.
    
    Change-Id: I6559b89e858526717168ba286e1ff7d9977097c6
    BUG: 1233624
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11331
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 21f2719bf4c43ae6712f41d23de11b5854a019f2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 23 15:40:32 2015 +0530

    glusterd: use mkdir_p for creating rundir
    
    snapdsvc initialization is now dependent on all subsequent directories and
    volfile creations as per commit 2b9efc9.
    
    However this may not hold true correct for all the cases. While importing a
    volume we would need to start the service before the store creation.
    
    To avoid this dependency, use mkdir_p instead of mkdir to create rundir
    
    Change-Id: Ib251043398c40f1b76378e3bc6d0c36c1fe4cca3
    BUG: 1234819
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11364
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 01e42f25ebdc44847e8b1dce02f7fd486b40dbc2
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jun 23 00:25:38 2015 +0530

    Revert "quota/marker: fix mem-leak, free contribution node"
    
    This reverts commit 8ab6608accb62d6320d1fc1fbe651fcafd376270.
    
    This patch is resulting in memory corruption:
    http://build.gluster.org/job/rackspace-regression-2GB-triggered/11193/consoleFull
    
    contribution object might be being used by some other transaction when
    we free it. The correct way to handle this is to have a reference based
    scheme to manage the contribution object.
    
    Change-Id: Idf9993ed8268029073a3e2d699865587f20d9aea
    BUG: 1207735
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/11362
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2b645af1d077957829c8ff6b8ab56353ba3913d6
Author: arao <arao@redhat.com>
Date:   Fri Jun 12 16:35:53 2015 +0530

    dht: Adding log messages to the new logging framework
    
    Change-Id: Ib3bb61c5223f409c23c68100f3fe884918d2dc3f
    BUG: 1194640
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/10021
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Joseph Fernandes
    Tested-by: Joseph Fernandes
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 653d3c1406e372aabcf694bfead2d695f84ee0f8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 28 15:33:18 2015 +0530

    cluster/ec: Do not handle GF_CONTENT_KEY
    
    GF_CONTENT_KEY aggregation requires that the fragments on the bricks belong to
    same data i.e. no operations are modifying the content while lookup is
    performed on it. The only way to know it is to get at least ec->fragments+1
    number of responses and see that two different sets of ec->fragments number of
    fragments give same data. But at the moment we feel that this slows down
    ec-lookup. So removing handling of this for now.
    
    Change-Id: I2da5087f1311d5cdde999062607b143b48c17713
    BUG: 1226279
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11003
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit e8847bd0ba03616bf80f242fda22e104ff2ea0e3
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Wed Jun 17 12:40:06 2015 +0530

     ec: Display correct message after successful heal start
    
     Problem : While launching heal, it shows heal launch
     was unsuccessful. However, internaly it was successfully
     launched.
    
     Solution : Don't reset op_ret to -1 in for loop for
     every brick.
    
    Change-Id: Iff89fdaf6082767ed67523a56430a9e83e6984d3
    BUG: 1203089
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/11267
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit d65a334691fd339b770114a35edd4d14e9db2678
Author: Anoop C S <achiraya@redhat.com>
Date:   Wed Jun 3 11:38:13 2015 +0530

    protocol/client: Remove unused function clnt_mark_fd_bad()
    
    clnt_mark_fd_bad() is no longer used to mark the fd bad. Instead
    we make use of client_mark_fd_bad() to do the same.
    
    Change-Id: I09af892d8c0c5d1cf853ff020e8596c53d9539c0
    BUG: 1227667
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/11063
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit bf3c34f9db793a1b84b7346ac8756098b44cbaff
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Jun 19 13:36:11 2015 +0530

    posix: lstat() failure have to recorded as warning
    
    BUG: 1200364
    Change-Id: Ic9cae46e89e49fede2150f420ca0b1e202d84bbe
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9849
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 142cbe0cfe1f0ff64d081f792e33337977ef5562
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jun 18 12:02:50 2015 +0530

    quota: allow writes when with ENOENT/ESTALE on active fd
    
    We may get ENOENT/ESTALE in case of below scenario
            fd = open file.txt
            unlink file.txt
            write on fd
    Here build_ancestry can fail as the file is removed.
    For now ignore ENOENT/ESTALE on active fd with
    writev and fallocate.
    We need to re-visit this code once we understand
    how other file-system behave in this scenario
    
    Below patch fixes the issue in DHT:
    http://review.gluster.org/#/c/11097
    
    Change-Id: I7be683583b808c280e3ea2ddd036c1558a6d53e5
    BUG: 1188242
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11307
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit bc6d9d679a87dd980afa4a064d6b2f6c49f39cae
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jun 17 15:00:23 2015 +0530

    gluster/shared_storage: Add/Remove shared storage from /etc/fstab during enable/disable
    
    While creating/deleting shared storage volume, add/remove the shared storage
    entry from /etc/fstab, so as to ensure availability of the shared storage,
    even after a node reboot
    
    Change-Id: Ib9edc8fd02c74a677062ca53ffd10be997b056c6
    BUG: 1231876
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11272
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit d9e688e42a9b1e4be221fed9c1c85db0c2ae3664
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jun 17 14:18:32 2015 +0530

    glusterd/mgmt_v3: Print the node info, with failure messages
    
    While reporting multiple failure messages from different
    nodes, print the node ip and the failure stage.
    
    Change-Id: I657d3debf1b509e4a27baf9e4b580f1ee32e3c5f
    BUG: 1205596
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11234
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 2b9efc920762ad93575a44ae41450f78ecdb0d9e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jun 12 17:13:05 2015 +0530

    glusterd/uss/snapshot: Intialise snapdsvc after volfiles are created
    
    snapd svc should be initialised only after all
    relevant volfiles and directories are created.
    
    Change-Id: I96770cfc0b350599cd60ff74f5ecec08145c3105
    BUG: 1231197
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11227
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 41805d75e47f2ce9f71d99e556885db008948fb2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jan 9 08:17:19 2015 +0530

    afr: complete conservative merge even in case of gfid split-brain.
    
    Problem:
    While performing conservative merge, we bail out of the merge if we encounter a
    file with mismatching gfid or type. What this means is all entries that come
    after the mismatching file (during the merge) never get healed, no matter how
    many index heals are done.
    
    Fix:
    Continue with the merging of rest of the entries even if a gfid/type mismatch is
    found, but ensure that post-op does not happen on the parent dir in such a case.
    
    Change-Id: I9bbfccc8906007daa53a0750ddd401dcf83943f8
    BUG: 1180545
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9429
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 79e4c7b2fad6db15863efb4e979525b1bd4862ea
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Jun 5 10:33:11 2015 +0530

    stack: use list_head for managing frames
    
    PROBLEM
    --------
    
    statedump requests that traverse call frames of all call stacks in
    execution may race with a STACK_RESET on a stack.  This could crash the
    corresponding glusterfs process. For e.g, recently we observed this in a
    regression test case tests/basic/afr/sparse-self-heal.t.
    
    FIX
    ---
    
    gf_proc_dump_pending_frames takes a (TRY_LOCK) call_pool->lock before
    iterating through call frames of all call stacks in progress.  With this
    fix, STACK_RESET removes its call frames under the same lock.
    
    Additional info
    ----------------
    
    This fix makes call_stack_t to use struct list_head in place of custom
    doubly-linked list implementation. This makes call_frame_t manipulation
    easier to maintain in the context of STACK_WIND et al.
    
    BUG: 1229658
    Change-Id: I7e43bccd3994cd9184ab982dba3dbc10618f0d94
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/11095
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 6b4add6b3f54b6d3202535a492eaf906d619ad75
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jun 3 16:51:49 2015 +0530

    features/shard: Skip shards resolution if lookup on /.shard returns ENOENT
    
    This change is done in [f]truncate, rename, unlink and readv.
    Also, this patch also makes lookup in shard delete GF_CONTENT_KEY
    as a workaround for the problems with read caching of sparse files
    by quick-read. A proper solution would involve shard_lookup_cbk()
    performing a readv, aggregating and ordering the responses and setting
    it in the xdata before unwinding the response to upper translators, which
    will be done in a separate patch.
    
    Change-Id: Ie12edb9ba8c1fcea38fea0a797916cb2a98fb30c
    BUG: 1223759
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11065
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit c7f309116d8fa62f6b9fd6ff2902e8ce4bfa192d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 19 11:36:25 2015 +0200

    refcount: correct the documentation
    
    The only check that _gf_ref_get() needs is "== 0" for detecting a
    failure. The actual return value is not guaranteed to be the number of
    active refences (they can change in other threads anyway).
    
    BUG: 1163543
    Change-Id: I8801601eab37046f5a5ee0bce5a62606115ca151
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11328
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6674e9e692d3c52e5eb4bf5c44d2d3195e03402b
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jun 17 22:59:17 2015 +0530

    tests/bitrot: Scrub state change tests
    
    Change-Id: Ibb4b503e7d723c86ac381ad3747b1198334bd6ad
    BUG: 1231619
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11290
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4acd9d1bfc2be5179ddb611f61afaaeaa15be2cb
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Jun 17 18:42:06 2015 +0530

    protocol/client : removing duplicate printing in gf_msg
    
    Since the 3rd and 5th argument of gf_msg framework
    prints the error string in case of strerror(),
    5th argument is removed.
    
    Change-Id: Ib1794ea2d4cb5c46a39311f0afcfd7e494540506
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/11280
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a6e412c4fc6036b797226c1b9fa7b1b90856a7f0
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Jun 11 20:19:39 2015 +0530

    features/bitrot: log scrub frequency & throttle values
    
    Change-Id: I56d5236c37a413046b5766320184047a908f2c8d
    BUG: 1231620
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11190
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ea1d2b0045e2c2ad82a2162a58f9fc36f9d07b20
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 31 15:16:41 2015 +0200

    core: add "gf_ref_t" for common refcounting structures
    
    Checks for compiler supported atomic operations comes from client_t.h.
    
    An example usage of this change can be found in adding reference
    counting to "struct auth_cache_entry" in http://review.gluster.org/11023
    
    Basic usage looks like this:
    
       #include "refcount.h"
    
       struct my_struct {
           GF_REF_DECL;
           ... /* more members */
       }
    
       void my_destructor (void *data)
       {
           struct my_struct *my_ptr = (struct my_struct *) data;
    
           ... /* do some more cleanups */
           GF_FREE (my_ptr);
       }
    
       void init_ptr (struct parent *parent)
       {
           struct my_struct *my_ptr = malloc (sizeof (struct my_struct));
    
           GF_REF_INIT (my_ptr, my_destructor); /* refcount is set to 1 */
    
           ... /* my_ptr probably gets added to some parent structure */
           parent_add_ptr (parent, my_ptr);
       }
    
       void do_something (struct parent *parent)
       {
           struct my_struct *my_ptr = NULL;
    
           /* likely need to lock parent, depends on its access pattern */
           my_ptr = parent_remove_first_ptr (parent);
           /* unlock parent */
    
           ... /* do something */
    
           GF_REF_PUT (my_ptr); /* calls my_destructor on refcount = 0 */
       }
    
    URL: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/11202
    Change-Id: Idb98a5861a44c31676108ed8876db12c320912ef
    BUG: 1228157
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11022
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit f460d1c9a2d83b24500c574aabce75438bdc8f9d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jun 19 12:32:51 2015 +0530

    glusterd/shared_storage: Added help description for enable-shared-storage option
    
    Added help description in gluster volume set help for
    cluster.enable-shared-storage option.
    
    Change-Id: I36481d1ca856739e83f0c9c7432ac0cb4131d665
    BUG: 1233544
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11324
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 7a6423bacdcefaedc4645e8c4d70674aaf9a63c4
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Jun 15 15:59:21 2015 +0530

    snapshot: man page modifications
    
    Modified man page to correct snap-max-hard-limit and
    snap-max-soft-limit entries.
    
    Change-Id: Ide3405fc94ea5cf6e19504e6dc158938c1bf135b
    BUG: 1205037
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11229
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 7aaa414c67be460aca3c1c5eed047e3db17bd435
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 26 10:59:45 2015 +0530

    glusterd/tier: configure tier daemon during volume restart
    
    rebalance daemon will be running on every tier volume for
    promoting/demoting the files. When volume/glusterd is restarted,
    then we need to configure the daemon.
    
    Change-Id: Ib565240a70edea2ec8bc1601c52b40c0783491d3
    BUG: 1225330
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10933
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>

commit 2fea88d70b2fb9d479f539509ae930ac6f05eb5c
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 12 14:50:33 2015 +0530

    tier/glusterd: Add description for volume set options
    
    Change-Id: Idc2eed77f8d841b6628183867e84601ce605d610
    BUG: 1215571
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10757
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit e19552c8cc42a3c80aaf43e70f6e29011ad23516
Author: Meghana M <mmadhusu@redhat.com>
Date:   Thu Jun 18 06:39:41 2015 +0530

    common-ha : Fixing add node operation
    
    Resource create for the added node referenced a variable
    new_node that was never passed. This led to a wrong schema
    type in the cib file and hence the added node always ended
    up in failed state. And also, resources were wrongly
    created twice and led to more errors. I have fixed the variable
    name and deleted the repetitive invocation of the recreate-resource
    function.
    
    The new node has to be added to the existing ganesha-ha config
    file for correct behaviour during subsequent add-node operations.
    This edited file has to be copied to all the other cluster nodes.
    I have added a fix for this as well.
    
    Change-Id: Ie55138e2657d22298d89db1c08f2e17930686bd6
    BUG: 1233246
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11316
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8ab6608accb62d6320d1fc1fbe651fcafd376270
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jun 18 14:30:16 2015 +0530

    quota/marker: fix mem-leak, free contribution node
    
    When removing contribution xattr, we also need to free
    contribution node in memory
    
    Change-Id: I5fe97813a8f39e2f00401976046bd280f2eea54d
    BUG: 1207735
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11311
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit c791765bc84b1ba62203b2b9c1e815944a39921c
Author: Sakshi <sabansal@redhat.com>
Date:   Fri Jun 5 13:48:09 2015 +0530

    dht : Error value check before performing rebalance complete
    
    Change-Id: I7a0cd288d16f27b887c7820162efdbe99a039d95
    BUG: 1188242
    Signed-off-by: Sakshi <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/11097
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 8ddf7f2669779cee460f1e008cdb62671cf15a40
Author: anand <anekkunt@redhat.com>
Date:   Wed Jun 17 16:11:48 2015 +0530

    glusterd: Removing sync lock and unlock inside rcu read critical section
    
    Issue : Glsuterd was crashing during peer probe.
    
    RCA :  In glusterd, we are using big lock which is implemented based on sync
    task frame work for thread synchronization, sync task frame work swap the threads
    if there is no worker pool threads available. Due to this rcu lock and rcu unlock
    was happening  in different threads (urcu-bp will not allow this), resulting into
    glusterd crash.
    
    fix : Removing sync lock and unlock inside rcu read critical section, which was left out by
    http://review.gluster.org/#/c/10285/ patch.
    
    Change-Id: Id358dfcc797335bcd3b491c3129017b2caa826eb
    BUG: 1232693
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/11276
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 46bf15e897ee9711835af211c19351a9920d490b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jun 16 09:33:48 2015 -0400

    common-ha: cluster setup issues on RHEL7
    
     * use --name on RHEL7 (later versions of pcs drop --name) we guessed
       wrong and did not get the version that dropped use of --name option
     * more robust config file param parsing for n/v with ""s in the value
       after not sourcing the config file
     * pid file fix. RHEL6 init.d adds -p /var/run/ganesha.nfsd.pid to
       cmdline options. RHEL7 systemd does not, so defaults to
       /var/run/ganesha.pid.
    
    Change-Id: I575aa13c98f05523cca10c55f2c387200bad3f93
    BUG: 1229948
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11257
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4442449f1436e47c84c55c3f0d8f1a8b248db4b6
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jun 18 16:44:55 2015 +0200

    cluster/ec: Avoid parallel executions of the same state machine
    
    In very rare circumstances it was possible that a subfop started
    by another fop could finish fast enough to cause that two or more
    instances of the same state machine be executing at the same time.
    
    Change-Id: I319924a18bd3f88115e751a66f8f4560435e0e0e
    BUG: 1233258
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/11317
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a0e9c7d52dc43d30e1a2bd5567412a61b3c078fa
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 17 17:05:22 2015 +0530

    tools/glusterfind: Fail glusterfind creation if volume is offline
    
    Following two fixes are done.
    
    1. Fail glusterfind session creation if volume is not online
       even before session directories are created. This avoids
       'glusterfind list' to pick the session directories and show
       status as 'Session Corrupted'.
    
    2. Check of '!Started' instead of wether the volume is 'Stopped'.
       It covers all the cases.
    
    Change-Id: I3e9cb384d978ada28f508c07e37d6ceb2272a731
    BUG: 1232729
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11278
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit dda7608736857ac5fb539f2c04a1499999c984ed
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jun 18 16:23:50 2015 +0530

    cluster/dht: Fix Null pointer dereference while logging
    
    Change-Id: I1ea358b83267b0bcdf654ce18fe881fd4a6bf08d
    BUG: 1233139
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/11313
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 81972918a0b0252cfa7feefbb80182fa886a72f8
Author: vmallika <vmallika@redhat.com>
Date:   Wed Jun 17 10:33:13 2015 +0530

    quota: fix double accounting with rename operation
    
    When a rename operation is performed, we are renaming
    the file first and performing remove-xattr when reducing
    the contri size from parents.
    This remove-xattr fails as the file is alreday renamed,
    this failure causes reduce-parent-size to abort resulting
    in double quota accounting
    
    This patch fixes the problem. We don't need to perform remove-xattr
    operation on a file when performing reduce-parent-size txn as this
    will be alreday done before starting reduce-parent-size txn
    
    Change-Id: If86e3dbb0233f6deaaa90bee72cb0ec1689c7325
    BUG: 1232572
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11264
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 26f17994a45210792a4af23fcbc8e1759218f2e8
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jun 17 10:48:03 2015 -0400

    common-ha: cluster HA setup sometimes fails
    
    the "s in the VIP_foo="x.x.x.x" lines are problematic now that the
    config file isn't sourced.
    
    Revised to also handle names containing '-', e.g. host-11, and FQNs,
    e.g. host-11.lab.gluster.org
    
    Change-Id: I1a52afbf398a024cdff851d0c415d8363f699c90
    BUG: 1232001
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11281
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit e9a681fb977f94e2309cb16625102ebb74e5dc77
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Thu Apr 30 16:57:00 2015 +0530

    quota/glusterd: porting to new logging framework
    
    Change-Id: I879a181b6d6b97119a6b4fab90a12b8386635383
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/10473
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>

commit d32b221747cf6742cffaff5a60e16269dffd04cc
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 15:34:43 2015 +0530

    fd,inode/libglusterfs : porting to a new logging framework
    
    Change-Id: I4beba3b50456f802824374b6e3fa8079d72f2c00
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10825
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit daf22a3b59f42c897f345dab74c3852ddf9bddef
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Jun 15 17:20:46 2015 +0530

    glusterd: Fix snapshot of a volume with geo-rep
    
    Problem:
        Snapshot fails for a volume configured with geo-rep
        if geo-rep is created with root user with the following
        syntax.
        gluster vol geo-rep <master_vol> root@<slave_host>::<slave_vol>
    
        It works fine if created with following syntax.
        gluster vol geo-rep <master_vol> <slave_host>::<slave_vol>
    
    Cause:
        Geo-rep maintains persistent dictionary of slave associated
        with master volume. The dictionary saves the slave info
        along with 'root@' as sent from cli.
        Snapshot while constructing the working dir path to copy
        configuration files, constructs using this dictionary.
        But the actual working dir is created with out considering
        'root@'. Hence the issue.
    
    Fix:
        Fix is done at two layers.
        1. Parse and negelect 'root@' in cli itself.
        2. For existing geo-rep sessions and upgrade scenarios,
           parse and neglect 'root@' in snapshot code as well.
    
    Change-Id: If4e04f7f776ef71df4dd1e7e053ef75db98762b2
    BUG: 1231789
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11233
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit ba7d5d914b2c897aef0616f3d95beb4d17bc51a8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Jun 17 14:39:26 2015 +0530

    libgfchangelog: Fix crash in gf_changelog_process
    
    Problem:
        Crash observed in gf_changelog_process and
        gf_changelog_callback_invoker.
    
    Cause:
        Assignments to arguments passed to thread is done
        post thread creation. If the thread created gets
        scheduled before the assignment and access these
        variables, it would crash with segmentation fault.
    
    Solution:
        Assignments to arguments are done prior to the thread
        creation.
    
    Change-Id: I6afc8ccedd050cf4b50b967fef8287a0c834177b
    BUG: 1232666
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11273
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit edc8d7d85c67f49fe6b3deb8868013bf3933f9e7
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Tue May 19 11:45:06 2015 +0530

    libglusterfs: fix uninitialized argument value
    
    common-utils.c:2871:17: warning: Function call argument is an uninitialized
    value gf_log ("glusterfs", GF_LOG_DEBUG, "lower: %d, higher:%d",
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    Change-Id: Iffde527a392afe783908aee12040d555c77c6983
    BUG: 1222769
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/10814
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 515a4c4e08eb9fcd92c9cca693ef9978b8a1b05c
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 15:28:30 2015 +0530

    common-utils/libglusterfs : Porting to a new logging framework
    
    Change-Id: Iee1c083774c988375a7261cfd6d510ed4c574de2
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10824
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 1cc500f48005d8682f39f7c6355170df569c7603
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Jun 13 17:33:14 2015 +0530

    cluster/dht: Prevent use after free bug
    
    Change-Id: I2d1f5bb2dd27f6cea52c059b4ff08ca0fa63b140
    BUG: 1231425
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11209
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 59e1c79ac6953e552fbdc8c627f5dc1d02eeacc8
Author: Hari Gowtham <hgowtham@dhcp35-85.lab.eng.blr.redhat.com>
Date:   Wed May 27 13:17:30 2015 +0530

    Porting new log messages for posix
    
    Change-Id: I29bdeefb755805858e3cb1817b679cb6f9a476a9
    BUG: 1194640
    Signed-off-by: Hari Gowtham <hgowtham@dhcp35-85.lab.eng.blr.redhat.com>
    Reviewed-on: http://review.gluster.org/9893
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1950f30ee77df938a76159f07fe8f8ca3ef14cf8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Jun 3 12:03:05 2015 +0530

    tests: rebalance completed should only check the status for completed
    
    Change-Id: I1abc91cefaf16d1c8351f35e951c26078ef90544
    BUG: 1227590
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11055
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e902df70f8157db4db503b7ec3c2635b08b3dcb2
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue May 19 15:01:08 2015 +0530

    rpc: fix possible deadlock left behind in d448fd1
    
    See http://review.gluster.org/9613 for more details.
    
    Change-Id: I05ac0267b8c6f4e9b354acbbdf5469835455fb10
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/10821
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 1b9a2edf2c18324ae961dd143e9e9685a019087f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 15 15:29:41 2015 -0400

    common-ha: cluster HA setup sometimes fails
    
    the "s in the VIP_foo="x.x.x.x" lines are problematic now that the
    config file isn't sourced.
    
    (A short term work-around is to simply eliminate them.)
    
    Change-Id: I65f375f2d3b8453adb45dc3dbbc7d3fb07cf85d0
    BUG: 1232001
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11237
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4a829e33d9c0d62a710650337406dc25d89cc599
Author: Meghana M <mmadhusu@redhat.com>
Date:   Mon Jun 15 08:43:44 2015 +0000

    NFS-Ganesha: Automatically export vol that was exported before vol restart
    
    Consider a volume that is exported via NFS-Ganesha. Stopping this
    volume will automatically unexport the volume. Starting this volume
    should automatically export it. Although the logic was already there,
    there was a bug in it. Fixing the same by introducing a hook script.
    
    Also with the new CLI options, the hook script S31ganesha-set.sh
    is no longer required. Hence, removing the same.
    Adding a comment to tell the user that one of the CLI
    commands will take a few minutes to complete.
    
    Change-Id: Ibff769ca04fef0c2a129c83fe31fc9c869350e8d
    BUG: 1231738
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11247
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a9f58cd6cfc29a47af868fff29ce3133b9f9efe5
Author: Shreyas Siravara <sshreyas@fb.com>
Date:   Fri Jun 12 13:11:35 2015 -0700

    nfs: Authentication performance improvements
    
    When file operations are sent to the NFS server, authorized filehandles
    are cached using the exportid, mountid, gfid and host as the key to the
    cache. This meant that any file OR directory will always fail on the
    *first* fop to that filehandle since the cache used the gfid as part of
    the key to the cache. However, if an export is authorized, this
    effectively means that ALL subdirectories and files in the export
    directory are authorized per the permissions of the export. This results
    slow times to walking a directory structure over an NFS mount.
    
    Change-Id: Iad811ad7255b454d1712e75a637478401d40791e
    BUG: 1232165
    Signed-off-by: Shreyas Siravara <sshreyas@fb.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11245
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f65490c5d87c4282717b7f28cfcd1fe9380c6154
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Jun 3 10:40:36 2015 +0530

    tests: fix spurious failure in bug-857330/xml.t
    
    get-task-status () used to always return 0 *until and unless* the CLI command
    itself fails which is unlikely. However if the CLI command fails due to some
    reason EXPECT_WITHIN will abort.
    
    Change-Id: Ibe54dcdccc26b3ee003677fc3516cfed98b5c06f
    BUG: 1227590
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11054
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8e81dccfce17db2d388de95b0b009478cc7d0d4d
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Jun 4 10:07:38 2015 +0530

    features/bitrot: fix fd leak in truncate (stub)
    
    The need to perform object versioning in the truncate() code path
    required an fd to reuse existing versioning infrastructure that's
    used by fd based operations (such as writev(), ftruncate(), etc..).
    
    This tempted the use of anonymous fd which was never ever unref()'d
    after use resulting in fd and/or memory leak depending on the code
    path taken. Versioning resulted in a dangling file descriptor left
    open in the filesystem effecting the signing process of a given
    object (no release() would be trigerred, hence no signing would be
    performed). On the other hand, cases where the object need not be
    versioned, the anonymous fd in still ref()'d resulting in memory
    leak (NOTE: there's no "dangling" file descriptor in this case).
    
    Change-Id: I29c3d2af9bbc5cd4b8ddf38954080e3c7a44ba61
    BUG: 1227996
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11077
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 1ac3d28d8dde6360550c80a10d8add572937be16
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Mon Jun 8 13:01:44 2015 +0530

    bitrot/glusterd: gluster volume set command for bitrot should not supported
    
    Currently gluster volume set <VOLNAME> bitrot succeeds. gluster volume
    set command for bitrot is not supported.
    Gluster should only accept gluster volume bitrot <VOLNAME> * commands.
    
    Change-Id: I5ff4b79f202ad018c76188f19d6311aad0d7c166
    BUG: 1229134
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11118
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Atin Mukherjee <amukherj@redhat.com>

commit 476d4070dbdb9d73b36bd04f3eb3d6eda84abe73
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 1 13:34:33 2015 +0530

    storage/posix: Handle MAKE_INODE_HANDLE failures
    
    Change-Id: Ia176ccd4cac82c66ba50e3896fbe72c2da860c20
    BUG: 1212110
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11028
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 70bb8bf65b4cefb503fa94452c200b0b71a06535
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Tue Mar 17 13:16:06 2015 +0530

    ops/glusterd: Porting messages to new logging framework
    
    Change-Id: Iafeb07aabc1781d98f51c6c2627bf3bbdf493153
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9905
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 25f28a9c23b1adf665a982c2f5157bf13361521b
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Fri Mar 13 16:55:17 2015 +0530

    rebalance,store,glusterd/glusterd: porting to new logging framework
    
    Change-Id: I231b79e3414e60fe67cde577dd585cce83c8bfad
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9877
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 60b6e5d2c3442ea0f7f85374d6613cd0dd76604c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed May 27 17:00:36 2015 +0530

    features/bit-rot: check for both inmemory and ondisk staleness
    
    * Let bit-rot stub check both on disk ongoing version, signed version xattrs and
      the in memory flags in the inode and then decide whether the inode is stale or
      not. This information is used by one shot crawler in BitD to decide whether to
      trigger the sign for the object or skip it.
    
      NOTE: The above check should be done only for BitD. For scrubber its still the
            old way of comparing on disk ongoing version with signed version.
    
    * BitD's one shot crawler should not sign zero byte objects if they do not contain
      signature. (Means the object was just created and nothing was written to it).
    
    Change-Id: I6941aefc2981bf79a6aeb476e660f79908e165a8
    BUG: 1224611
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/10947
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 05a17a087ec8d50d1b5341ab1a7fbf18cdabcb92
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Fri Jun 12 19:25:26 2015 +0530

    NFS-Ganesha : Return corect return value
    
    When any of the nodes in the trusted pool is not listed
    in the cluster node list, it receives a wrong return
    value. And commit fails on that host. Fixing the same.
    
    Change-Id: Ib208dae7497800cc48b7f7a77f5e708f6c11e676
    BUG: 1231257
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11205
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5cdbbf34e31758071f597561aa8572cedd56aece
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Mon Jun 15 16:42:21 2015 +0530

    common-ha : Clean up cib state completely
    
    Clean up cluster state on all the machines during tear down.
    
    Change-Id: If9ca65b6ca8790ac97311f33359e28558e90c557
    BUG: 1228415
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11231
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 8e5fa4d025492762db566634b7493148a92f6d05
Author: vmallika <vmallika@redhat.com>
Date:   Mon Jun 15 11:21:12 2015 +0530

    quota: don't log error when disk quota exceeded
    
    When disk quota exceeded, quota enforcer logs
    alert message, so no need to log error message
    as this can fill up the log file
    
    Change-Id: Ia913f47bc0cedb7c0a9c611330ee5124d3bb6c9d
    BUG: 1229609
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/11135
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 379dbbfd683d2b0e1704c098b1f020567328122c
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Apr 6 16:21:43 2015 +0530

    protocol/client : porting log messages to new framework
    
    Change-Id: I9bf2ca08fef969e566a64475d0f7a16d37e66eeb
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/10042
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 554fa0c1315d0b4b78ba35a2d332d7ac0fd07d48
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Fri Jun 5 13:58:28 2015 +0530

    features/bitrot: tuanble object signing waiting time value for bitrot
    
     Currently bitrot using 120 second waiting time for object to be signed
     after all fop's released. This signing waiting time value should be tunable.
    
     Command for changing the signing waiting time will be
     #gluster volume bitrot <VOLNAME> signing-time <waiting time value in second>
    
    Change-Id: I89f3121564c1bbd0825f60aae6147413a2fbd798
    BUG: 1228680
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11105

commit 3fb18451311c34aeced1054472b6f81fc13dd679
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed Jun 10 15:11:39 2015 +0530

    glusterd: subvol_count value for replicate volume should be calculate correctly
    
    glusterd was crashing while trying to remove bricks from replica set
    after shrinking nx3 replica to nx2 replica to nx1 replica.
    
    This is because volinfo->subvol_count is calculating value from old
    replica count value.
    
    Change-Id: I1084a71e29c9cfa1cd85bdb4e82b943b1dc44372
    BUG: 1230121
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11165
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 40795d95697068a0beb52364b97818dc80e49440
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Thu Mar 12 16:55:20 2015 +0530

    handshake,locks,mountbroker,syncop/glusterd:New logging framework
    
    Change-Id: If491a6945b7a0afa10165ff9f9874a244aece36f
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9864
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 2ae034374ce449c54b1b4ae8350401371db1d8d3
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Mon Mar 9 16:59:54 2015 +0530

    glusterd: Porting messages to new logging framework.
    
    Change-Id: I56ced6fca0246c230cc389132c47a0f60472ed0c
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9836
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 79fdd93d1411e8b0f94f6ccb310ca5d05eb04054
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 9 23:11:13 2015 +0530

    tests: test cluster lock in heterogenious cluster
    
    Change-Id: I421f50aeb89213d036b4b40f20a8e0d6bd78d60b
    BUG: 1229825
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11143
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 8720cef1ed642d7cb09e98c41458d19845f24711
Author: Susant Palai <spalai@redhat.com>
Date:   Mon May 25 16:52:10 2015 +0530

    features/quota: port QUOTA messages to new logging framework
    
    Change-Id: I5e3df8860ea35bce14a802391be9b22ad64f1ad4
    BUG: 1075611
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7574
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a367d4c6965e1f0da36f17ab6c5fdbd37925ebdd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 12 12:31:19 2015 +0200

    upcall: prevent busy loop in reaper thread
    
    http://review.gluster.org/10342 introduced a cleanup thread for expired
    client entries. When enabling the 'features.cache-invalidation' volume
    option, the brick process starts to run in a busy-loop. Obviously this
    is not intentional, and a process occupying 100% of the cycles on a CPU
    or core is not wanted.
    
    Change-Id: I453c612d72001f4d8bbecdd5ac07aaed75b43914
    BUG: 1200267
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11198
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cdda561c0a1f4c8050f664a444fe8b88d17e3b10
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Tue Mar 17 18:03:36 2015 +0530

    handler, messages/glusterd: Porting to new logging framework
    
    Change-Id: If67230445678dd895d69f18c9982c3f0fda62dbd
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9910
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 7d8b53d5fc736d340c75e70a69c464b20102bbe7
Author: Milind Changire <mchangir@redhat.com>
Date:   Sat Jun 13 12:31:55 2015 +0530

    tools/glusterfind: print message for good cases
    
    Added messages for printing status of good or default cases
    for 'create', 'list', 'post' and 'delete' commands
    
    Change-Id: Ie983bff7f5a66f118de06c225166ff6bee870438
    BUG: 1230017
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/11208
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1ea9c9a3d59d8c3ddf1e27e2939c136a4ed3c6e8
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Jun 4 22:37:11 2015 +0530

    glusterd: Buffer overflow causing crash for glusterd
    
    Problem: In GLUSTERD_GET_DEFRAG_PROCESS we are using PATH_MAX (4096)
    as the max size of the input for target path, but we have allocated
    NAME_MAX (255) size of buffer for the target.
    
    Now this crash is not seen with source install, but is seen with RPMS.
    The reason is _foritfy_fail. This check happens when _FORTIFY_SOURCE
    flag is enabled. This option tries to figure out possible
    overflow scenarios like the bug here and does crash the process.
    
    Change-Id: I26261be85936d2e94a526fdcaa8d3249f8af11c3
    BUG: 1228093
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/11090
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 6b97f339169dd86a3c3aad9cff9b3da83a40a614
Author: M S Vishwanath Bhat <vbhat@redhat.com>
Date:   Thu Jun 4 17:52:00 2015 +0530

    gverify: Adding StrictHostKeyChecking=no for ssh verification
    
    Before actually checking the compatibility between master and
    slave, gverify checks if there is a passwordless ssh connection
    between master to slave.  So if the entry of the slave was not
    present in 'known_hosts' file in master gverify used to complain
    that passwordless ssh has not been setup. This used to happen
    even if there is a passwordless ssh between master to slave.
    
    This patch fixes the above problem by using StrictHostKeyChecking=no
    while doing ssh to slave.
    
    Change-Id: I953c278e411ad6bc1dd1966ea6d895b05f890492
    BUG: 1228696
    Signed-off-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Reviewed-on: http://review.gluster.org/11106
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit f42be86a10fcd74436da40153d5d84a54d049d49
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 12 17:19:55 2015 +0530

    spec/geo-rep: Add rsync as dependency for georeplication rpm
    
    If rsync is not installed, Geo-rep will go faulty on started.
    Added rsync as dependency for georep rpm
    
    Change-Id: I49614957ccde47645185a65191d6d7baf1cc826c
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1231205
    Reviewed-on: http://review.gluster.org/11201
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b9603a046116e7db29e16e7caed29018bff50f66
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 11 14:44:48 2015 +0530

    cluster/ec: Prevent Null dereference in dht-rename
    
    Change-Id: I3059f3b577f550c92fb77c6b6b44defd0584cd2e
    BUG: 1230647
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11178
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b0edf64f91bf2afefc811c832babe9e3e6bdfbfe
Author: Milind Changire <mchangir@redhat.com>
Date:   Fri Jun 12 12:48:27 2015 +0530

    tools/glusterfind: ignoring deleted files
    
    OSError and IOError exceptions were being thrown if files
    were deleted after session was created and a subsequent
    glusterfind pre was attmepted. glusterfind now detects
    this scenario and safely ignores these changes to the
    file-system. We also avoid recording deleted file paths
    into database in the case where gfid to path resolution
    cannot be performed for deleted files.
    
    Also, we now turn on volume option to capture delete paths.
    
    Change-Id: Iaf3883463f5e64643497bd77229ad80a9b2d5da5
    BUG: 1228111
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/11194
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit e58b55ed9b2e802e6c3e908cbbad71c00f6c5b97
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jun 9 10:44:44 2015 +0530

    features/changelog: Do htime setxattr without XATTR_REPLACE flag
    
    HTIME_KEY marks the last changelog rolled over. The xattr is
    maintained on .glusterfs/changelog/htime/HTIME.TSTAMP file.
    On every rollover of the changelog file, the xattr is updated.
    It is being updated with XATTR_REPLACE flag as xattr gets
    created during changelog enable. But it is once found that
    the xattrs on the file is cleared and is not reproduced later
    on. This patch protects that case, if it happens by setting
    xattr without XATTR_REPLACE flag in failure case.
    
    The reason behind doing this in failure case is not to mask
    the actual cause of xattrs getting cleared. This provides
    the log message if the original issue still exists but the
    consequential effects are fixed.
    
    Also changed the log messages to depict the events happened
    during changelog enable.
    
    Change-Id: I699ed09a03667fd823d01d65c9c360fa7bc0e455
    BUG: 1230015
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/11150
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 6180d36ff30ecbe84c91b66b23734cf4f45249c5
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Fri Mar 20 12:04:32 2015 +0530

    glusterd/geo-rep : porting log messages to a new framework
    
    Change-Id: I1f1b99822c2b301d68eaf392af4bbb475151e2c5
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9952
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 9e72abb08f37db017a83e0114e9cd07fd5151d30
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 10 14:47:21 2015 +0530

    tools/glusterfind: Cleanup session dir after delete
    
    Sessions directories are created in
    /var/lib/glusterd/glusterfind/<SESSION>/<VOLUME>, only <VOLUME>
    dir is created since same session name can exists for two volumes.
    
    Now cleanup is added, <SESSION> dir will be removed if <SESSION>
    contains only one Volume.
    
    Change-Id: I236393659e63eb98342570e0255739f4adea4491
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1230111
    Reviewed-on: http://review.gluster.org/11157
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 57ecbbd6ce5b682a9e69c775ace48588d6535396
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 10 14:14:25 2015 +0530

    geo-rep: Validate use_meta_volume option
    
    Added validation for use_meta_volume option.
    
    Change-Id: I64cd9cb4bf383c7267638cab3837fd0cf89071c7
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1230090
    Reviewed-on: http://review.gluster.org/11156
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit d28b226131d420070fa5cee921a4ad0be9d6446a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed May 27 18:05:35 2015 +0530

    tools/glusterfind: Cleanup glusterfind dir after a volume delete
    
    If `glusterfind delete` command was not run before volume delete, stale
    session directories exists in /var/lib/glusterd/glusterfind directories.
    
    Also shows these sessions in `glusterfind list`
    
    When Volume is deleted, Post hook will be run which cleans up the stale
    session directories
    
    BUG: 1225465
    Change-Id: I54c46c30313e92c1bb4cb07918ed2029b375462c
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10944
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 72a7a6ea78289b2897f9846dc4e111f442dd2788
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Wed Mar 18 15:17:45 2015 +0530

    sm/glusterd: Porting messages to new logging framework
    
    Change-Id: I391d1ac6a7b312461187c2e8c6f14d09a0238950
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9927
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit eeccafc72c95da83abeb51966d7eeeab02190899
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 4 08:21:59 2015 +0530

    features/qemu-block: Add comment about root_inode handling
    
    This is handling the comment on 3.7 backport
    http://review.gluster.com/11047
    
    Change-Id: I253a8e0bfebde63f25c839efd55ed3cc30e6cd9b
    BUG: 1226276
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11076
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>

commit 886f65fabc50c256a7de57fd05281a75bba3cac9
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Tue Feb 3 16:35:33 2015 +0530

    libglusterfs: Fixing insecure temp file coverity issue
    
    Coverity CID: 1124835
    
    Change-Id: I7e87f2b3bad35cf8a9c64c8502de23662d9f677f
    BUG: 789278
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9565
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sakshi Bansal
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>

commit 04791e4d53650eb108890e9ad9a809768a06987b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 1 14:02:58 2015 -0400

    common-ha: handle long node names and node names with '-' and '.' in them
    
    sourcing the /etc/ganesha/ganesha-ha.conf file seemed like a simple
    and elegant solution for reading config params, but bash variable names
    do not allow '-' and '.' in them.
    
    Also fix incorrect path in shared volume mount
    
    Change-Id: I40140e5da0903221efd316de94dce40229263e15
    BUG: 1225572
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11035
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 9eef639e19c01712aaadfffda22aef795bf1dfeb
Author: meghana <mmadhusu@redhat.com>
Date:   Fri Jun 5 02:56:26 2015 +0530

    common-ha : Clean up persistent cib state
    
    Pacemaker saves old configurations in the
    directory, "/var/lib/pacemaker/cib". It's
    good to clean up this directory during teardown so that
    old data doesn't show up the next time.
    
    Change-Id: If0f413ba2da599dd6672b51e60e1d35e674d576b
    BUG: 1228415
    Signed-off-by: meghana <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/11093
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 076e869c65dbe2ef9fa34b05756d23849ae4e852
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 10 15:26:47 2015 +0530

    tools/glusterfind: Fix GFID to Path conversion for dir
    
    For Directories, GFID to Path conversion was fine, but wrong
    filter was used while updating to db.
    
    Change-Id: Id588adbb25ff5fd357f8cc2d5485bd2eb4a52b65
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1230127
    Reviewed-on: http://review.gluster.org/11158
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 07df9b56fd0eb4abf1ef6a45318519c9d7ae08e3
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Thu May 28 11:54:04 2015 +0530

    geo-rep: ignore symlink and harlink errors in geo-rep
    
    Ignore logging in case of symlink and hardlink creation
    errors, as these are safe errors with respect to
    geo-replication.
    
    Change-Id: I3b863fb03ae23dbea907e4dd9477ff85feecad70
    BUG: 1225571
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/10957
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 53e84fe1eec8770936e7fdfb7246925006566f41
Author: Milind Changire <mchangir@redhat.com>
Date:   Thu May 28 11:22:50 2015 +0530

    tools/glusterfind: verifying volume is online
    
    Volume needs to be online (Started) to perform meaningful
    operations i.e. for "create" and "pre". This is now verified.
    
    Change-Id: I207cf1f5e30be0f67a776b866349b59d70a13984
    BUG: 1225564
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/10955
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 46b3fde5437b293d9c0897fe167223b8f4f37c60
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Sat Jun 6 10:28:51 2015 +0530

    tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period
    
    This fixes the ping-pong issue i.e files getting demoted immediately
    after promition, caused by off-sync promotion/demotion processes.
    The solution is do promotion/demotion refering to the system time.
    To have the fix working all the file serving nodes should have
    thier system time synchronized with each other either manually or
    using a NTP Server.
    
    NOTE: The ping-pong issue can re-appear even with this fix, if the admin
    have different promotion freq period and demotion freq period, but this
    would be under the control of the admin.
    
    Change-Id: I1b33a5881d0cac143662ddb48e5b7b653aeb1271
    BUG: 1218717
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/11110
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b1ff2294d2aaf7dd36918837c09a68152adc0637
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu Jun 4 14:00:34 2015 -0400

    cluster/tier: account for reordered layouts
    
    For a tiered volume the cold subvolume is always at a fixed
    position in the graph. DHT's layout array, on the other hand,
    may have the cold subvolume in either the first or second
    index, therefore code cannot make any assumptions. The fix
    searches the layout for the correct position dynamically
    rather than statically.
    
    The bug manifested itself in NFS, in which a newly attached
    subvolume had not received an existing directory. This case
    is a "stale entry" and marked as such in the layout for
    that directory.  The code did not see this, because it
    looked at the wrong index in the layout array.
    
    The fix also adds the check for decomissioned bricks, and
    fixes a problem in detach tier related to starting the
    rebalance process: we never received the right defrag
    command and it did not get directed to the tier translator.
    
    Change-Id: I77cdf9fbb0a777640c98003188565a79be9d0b56
    BUG: 1214289
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11092

commit 9863c8940936989d2ffb3c8ac28431d2b313384d
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Mon Mar 23 11:36:37 2015 +0530

    utils/glusterd: Porting to new logging framwork
    
    Change-Id: Iacb30eb675693bcdb3ef9de8e7f43892c5d79f6d
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9967
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a6c53571a9a7c74d0fa2683b4ba04682bd6a46ad
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Tue Jun 9 17:49:58 2015 +0530

    features/changelog: Avoid setattr fop logging during rename
    
    Problem:
            When a file is renamed and the (renamed)file's Hashing
    falls into a different brick, DHT creates a special file(linkto file)
    in the brick(Hashed subvolume) and carries out setattr operation
    on that file.
    
    Currently, Changelog records this(setattr) operation in Hashed
    subvolume. glusterfind in turn records this operation
    as MODIFY operation.
    
    So, there is a NEW entry in Cached subvolume and MODIFY entry
    in Hashed subvolume for the same file.
    
    Solution:
            Avoid logging setattr operation carried out, by
    marking the operation as internal fop using xdata.
    
    In changelog translator, check whether setattr is set
    as internal fop and skip accordingly.
    
    Change-Id: I21b09afb5a638b88a4ccb822442216680b7b74fd
    BUG: 1230007
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/11137
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 3eafe6a81fecc493e60f3781246daefbf4393602
Author: Sachin Pandit <spandit@redhat.com>
Date:   Thu Jun 4 11:01:38 2015 +0530

    features/marker : Pass along xdata to lower translator
    
    The problem was in marker xlator, where during
    rename a NULL value is passed during STACK_WIND.
    Marker needs to pass the xdata un-modified to next
    translator if marker does not rely on that.
    
    Change-Id: I9e47e504fd241263987645abfed7ca13c0d54a80
    BUG: 1228492
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/11089
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 515feb9885c193255121342540eac07f77b4b580
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jun 9 16:32:37 2015 +0200

    build: improve detection of new OpenSSL features
    
    Building on Mac OS X revealed that the current check for
    CRYPTO_THREADID_set_callback() availability in OpenSSL is not correct.
    
    There also does not seem to be a guarantee that TLSv1_2_method() is
    available when TLS1_2_VERSION is #define'd.
    
    Change-Id: I21508065fc181a1c74bee4fd6d23bb5bdf7cea7a
    BUG: 1222317
    Original-author: Kaleb KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11140
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 71f27128cb9e842fe5b0b9aa05e21fdc8147f52e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jun 9 18:00:57 2015 +0530

    snapshot/scheduler: Reload /etc/cron.d/glusterfs_snap_cron_tasks when shared storage is available
    
    If shared storage is not accessible, create a flag in /var/run/gluster/
    So that when /etc/cron.d/glusterfs_snap_cron_tasks is
    available again, the flag will tell us, to reload
    /etc/cron.d/glusterfs_snap_cron_tasks
    
    Change-Id: I41b19f57ff0b8f7e0b820eaf592b0fdedb0a5d86
    BUG: 1218573
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11139
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit fefc8730e2a87db41d5f79c9853a14cab86715e5
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Jun 4 14:14:14 2015 +0530

    glusterd/tier: glusterd crashed with detach-tier commit force
    
    glusterd crashed when doing "detach-tier commit force" on a
    non-tiered volume.
    
    Change-Id: I884771893bb80bec46ae8642c2cfd7e54ab116a6
    BUG: 1228112
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11081
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 5c00a6c8163cc255e777823b99d516dfb5ef114e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jun 10 10:30:03 2015 +0530

    cluster/ec: Wind unlock fops at all cost
    
    Problem:
    While files are being created if more than redundancy number of bricks
    go down, then unlock for these fops do not go to the bricks. This will
    lead to stale locks leading to hangs.
    
    Fix:
    Wind unlock fops at all costs.
    
    Change-Id: I50a87e8b4d6d2dde5bf7405b82e3aeecd95ad00e
    BUG: 1220348
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11152
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit ec7d0c3de11cbee1470308dcc10ec9f02e7fdfff
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 5 16:38:30 2015 +0200

    logging: log "Stale filehandle" on the client as Debug
    
    There are valid use-cases where a "Stale filehandle" is expected. One of
    these is deleting a file through NFS-Ganesha. When the "filename" is
    deleted, Ganesha will stat the file-handle to update its attributes. The
    file-handle would still be valid in the case where there are hardlinks.
    
    There is no need to log "Stale filehandle" as Warning. It is perfectly
    fine to have this logged as Debug.
    
    Change-Id: Ib9006d95a5d1f7dd394bf5d5994ad70740ad4ab2
    BUG: 1228731
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11107
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 5b05d3e376e984f00528f5bf2f0febd0220ca91f
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jun 9 17:49:23 2015 +0530

    snapshot/scheduler: Check if GCRON_TASKS exists before
    accessing it's mtime
    
    Change-Id: I873c83d21620527b20d7de428d11582c5499d1af
    BUG: 1228613
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11138
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 00f9a61fe8884062c141edd662424625d349a377
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Wed May 27 15:20:59 2015 +0530

    changetimerecorder : Porting to new logging framework
    
    Change-Id: I66e7ccc5e62482c3ecf0aab302568e6c9ecdc05d
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10938
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit 2847b03a38515a625e36d52c7e0a1d37107d72ba
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Tue May 19 14:55:38 2015 +0530

    gfdb/libglusterfs : Porting to a new logging framework
    
    Change-Id: I61874561fdf2c175d2b3eec0c85c25f12dc60552
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/10819
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joseph Fernandes

commit 9374b2ef417104ba51bc03a55ff8c5a521c749f4
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Tue Feb 3 13:05:02 2015 +0530

    glusterd: coverity fix for string overflow
    
    Coverity CID: 1222523
    Coverity CID: 1210990
    Coverity CID: 1229877
    Coverity CID: 1229876
    Coverity CID: 1124855
    
    Change-Id: Iba615724909216f923074cb4585940b919d02166
    BUG: 789278
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/9555
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 9307b943947daa1fe93afdeef5bfae606423b38a
Author: arao <arao@redhat.com>
Date:   Wed Feb 11 16:59:10 2015 +0530

    glusterd: Dereference after null check
    
    CID: 1124588
    CID: 1124589
    CID: 1124590
    CID: 1124591
    Either the null pointer is dereferenced before the null check
    or the check for null is unnecessary
    
    Change-Id: I87c6b09a4b89c33afd402866e6e249fefb1330f0
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9636
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f6a062044a3447bea5bf0fcf21a3f85c00fb6c7d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon May 11 14:43:23 2015 +0530

    tier/volume set: Validate volume set option for tier
    
    Volume set option related to tier volume can only be set
    for tier volume, also currently all volume set i for tier
    option accepts a non-negative integer. This patch validate
    both condition.
    
    Change-Id: I3611af048ff4ab193544058cace8db205ea92336
    BUG: 1216960
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10751
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Joseph Fernandes

commit d835219a30327ede60e4ef28210914ab30bd0712
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jun 4 17:17:13 2015 +0530

    snapshot/scheduler: Handle OSError in os. callbacks
    
    Handle OSError and not IOError in os. callbacks.
    
    Change-Id: I2b5bfb629bacbd2d2e410d96034b4e2c11c4931e
    BUG: 1218060
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11087
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit cd6dc49fb3c4fabf4f1dbc4dcd57db7232939ce3
Author: anand <anekkunt@redhat.com>
Date:   Fri May 22 18:18:11 2015 +0530

    libglusterfs: Enabling the fini()  in cleanup_and_exit()
    
    Problem 1 : glusterd was crashing due to race between clean up thread and rpc event thread.
    
    Scenario:
    As we can observed, X thread is in the process of exiting the process. It has already
    run the exit handlers, which cleanup things that require cleaning up. This includes
    liburcu resources. By the time Y thread  called rcu_bp_register(), the liburcu resources
    have been cleaned up. rcu_bp_register() tries to access these non-existent resources,
    which leads to the segmentation fault.
    
    Note1:
    Crash happen when the process is almost at the point of stopping(exiting), it doesn't have any
    serious impact to functionality apart from creating the core dump file and the log message.
    
    Fix .Do proper clean up before calling exit().
    
    Note2: Other xlator have clean up issues,so only glusterd clean up function invoked.
    
    Note3: This patch also solve the selinux issue.
    
    Problem 2 : glusterd runs as rpm_script_t when it's executed from the rpm scriptlet,files created
    in this context are set as rpm_script_t, so glusterd unable to access these files when it runs
    in glusterd_t context.
    
    Fix: Fini clean up the files while glusterd exiting, so files are recreated by glusterd while
    starting with proper SElinux context label.
    
    Change-Id: Idcfd087f51c18a729bdf44a146f9d294e2fca5e2
    BUG: 1209461
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10894
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ce2488ac2a1a9b7944373676595b0d579e4b75f1
Author: Shyam <srangana@redhat.com>
Date:   Wed Jun 3 14:12:27 2015 -0400

    cluster/dht: Increment op-version for lookup-optimize to 3.7.2
    
    3.7.1 has already shipped, so carrying this configuration option
    at that op-version will break compatibility. As a result bumping
    this to 3.7.2.
    
    Change-Id: I603d82184ec10d0ea3edf550490e960a8523d572
    BUG: 1227894
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/11073
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 5e08bf5b351b13a4ced35a026c3db633e161b237
Author: Shyam <srangana@redhat.com>
Date:   Fri Jun 5 16:37:08 2015 -0400

    doc: Adding documentation for DHT lookup-optimize option
    
    This is intended to be admin facing documentation, with some granular
    details.
    
    Change-Id: I379f8cea5375649fba915e907648e3a71344092d
    BUG: 1228818
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/11109
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit b77c8ddda8e68c1086227b19f9fb5db9bf89b0dc
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jun 4 11:25:35 2015 +0530

    Upcall/cache-invalidation: Ignore fops with frame->root->client not set
    
    Server-side internally generated fops like 'quota/marker' will
    not have any client associated with the frame. Hence we need a
    check for clients to be valid before processing for upcall cache
    invalidation. Also fixed an issue with initializing reaper-thread.
    
    Added a testcase to test the fix.
    
    Change-Id: If7419b98aca383f4b80711c10fef2e0b32498c57
    BUG: 1227204
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10909
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit c51eb694bce443ae7c0584b1545c14254569ae49
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Jun 7 21:32:32 2015 +0200

    Tests portability: umount(8)
    
    1) Avoid hangs on unmounting NFS on NetBSD
    
    NetBSD umount(8) on a NFS mount whose server is gone will wait forever
    because umount(8) calls realpath(3) and tries to access the mount before
    it calls unmount(2). The non-portable, NetBSD-specific umount -R flag
    prevent that behavior.
    
    We therefore introduce UMOUNT_F, defined as "umount -f" on Linux and
    "umount -f -R" on NetBSD to take care of forced unmounts, especially
    in the NFS case.
    
    2) Enforce usage of force_umount wrapper with timeout
    
    Whenever umount is used it should be wrapped in force_umount with
    tiemout handling. That saves us timing issues, and it handles the
    NetBSD NFS case.
    
    3) Cleanup kernel cache flush.
    
    We used (cd $M0 && umount $M0 )	as a portable kernel cache flush
    trick, but it does not flush everything we need on Linux. Introduce
    a drop_cache() shell function that reverts to previously used
    echo 3 > /proc/sys/vm/drop_caches on Linux, and keeps
    (cd $M0 && umount $M0 ) on other systems.
    
    BUG: 1129939
    Change-Id: Iab1f5a023405f1f7270c42b595573702ca1eb6f3
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/11114
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a2a370db6db80e9365d0777701786ce706957f42
Author: Mohamed Ashiq <ashiq333@gmail.com>
Date:   Mon May 18 12:15:07 2015 +0530

    libglusterfs: Introducing new logging message
    
    Change-Id: I137f1b7805895810b8e6f0a70a183782bf472bf5
    BUG: 1194640
    Signed-off-by: Mohamed Ashiq <ashiq333@gmail.com>
    Reviewed-on: http://review.gluster.org/9898
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 31866a490edf5b92886accac67eddf78b291d710
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jun 7 10:24:08 2015 +0530

    cluster/ec: Prevent double unwind
    
    Problem:
    1) ec_access/ec_readlink_/ec_readdir[p] _cbks are trying to recover only from
    ENOTCONN.
    2) When the fop succeeds it unwinds right away. But when its
    ec_fop_manager resumes, if the number of bricks that are up is less than
    ec->fragments, the the state machine will resume with -EC_STATE_REPORT which
    unwinds again. This will lead to crashes.
    
    Fix:
    - If fop fails retry on other subvols, as ESTALE/ENOENT/EBADFD etc are also
    recoverable.
    - unwind success/failure in _cbks
    
    Change-Id: I2cac3c2f9669a4e6160f1ff4abc39f0299303222
    BUG: 1228952
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11111
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7ca78f7a6466a0f2ff19caff526f6560b5275f69
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jun 8 11:36:12 2015 +0530

    cluster/afr: Do not attempt entry self-heal if the last lookup on entry failed on src
    
    Test bug-948686.t was causing shd to dump core due to gfid being NULL.
    This was due to the volume being stopped while index heal's in progress,
    causing afr_selfheal_unlocked_lookup_on() to fail sometimes on the src brick
    with ENOTCONN. And when afr_selfheal_newentry_mark() copies the gfid off the
    src iatt, it essentially copies null gfid. This was causing the assertion
    as part of xattrop in protocol/client to fail.
    
    Change-Id: I237a0d6b1849e4c48d7645a2cc16d9bc1441ef95
    BUG: 1229172
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11119
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f57c2d1ecbd547360137c9d3a36f64349e6e0fba
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu May 14 17:06:25 2015 +0530

    Changing log level to DEBUG in case of ENOENT
    
    Change-Id: I264e47ca679d8b57cd8c80306c07514e826f92d8
    BUG: 1193388
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/10784
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 0dff9120d5e2ca4150491b94fdc01944a710041a
Author: anand <anekkunt@redhat.com>
Date:   Fri Apr 10 16:41:25 2015 +0530

    glusterd: Stop tcp/ip listeners during  glusterd exit
    
    Problem : Because of race between exit thread and rpc thread
    causing the glusterd crash while glusterd exiting/stoping.
    
    Fix : Stop tcp/ip socket listeners in cleanup_and_exit to
    avoid new rpc events.
    
    Change-Id: Ie9280c8c9d7c350a176529375d861432f3de94ac
    BUG: 1209461
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10197
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit f5095fdb7a311d3e019ec1e7a6b21844bb9fba61
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Wed May 20 17:51:29 2015 +0530

    gfid-access: Remove dead increment (dead store)
    
    This patch remove stores to variables that are no longer live.
    
    Change-Id: Ib6acd8c70cbb7ea875c01b7cfd6620ac1d641d36
    BUG: 1223378
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/10841
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit ffe8b4d8149b50df53353bdb85fac1251a85ec2f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 31 21:50:21 2015 +0200

    rpm: add option "--with debug" for rpmbuild/mock
    
    When passing "--with debug" to mock or rpmbuild, the build process will
    add the "--enable-debug" option to ./configure. This makes it easier
    to build RPMs with debugging enabled.
    
    Change-Id: Ie584a4a03525385b337bbf81e5093f2af1b0b780
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11020
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 3373379303afa575c0616482c8ab8c3c4a08cc22
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 4 09:52:51 2015 +0530

    cluster/ec: Don't handle EC_XATTR_DIRTY in response
    
    Problem:
    ec_update_size_version expects all the keys it did xattrop with to come in
    response so that it can set the values again in ec_update_size_version_done.
    But EC_XATTR_DIRTY is not combined so the value won't be present in the
    response. So ctx->post/pre_dirty are not updated in
    ec_update_size_version_done. So these values are still non-zero. When
    ec_unlock_now is called as part of flush's unlock phase it again tries to
    perform same xattrop for EC_XATTR_DIRTY. But ec_update_size_version is not
    expected to be called in unlock phase of flush because ec_flush_size_version
    should have reset everything to zero and unlock is never invoked from
    ec_update_size_version_done for flush/fsync/fsyncdir. This leads to stale lock
    which leads to hang.
    
    Fix:
    EC_XATTR_DIRTY is removed in ex_xattrop_cbk and is never combined with other
    answers. So remove handling of this in the response.
    
    Change-Id: If0ea3efec3235a6e312465d8838585fbe752c7ea
    BUG: 1227654
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11078
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8f12fae9cb9349af2e3eeb338b5d85112655dc29
Author: Anuradha <atalur@redhat.com>
Date:   Fri Jun 5 16:49:14 2015 +0530

    heal : Do not invoke glfs_fini for glfs-heal commands
    
    Change-Id: I2fa6789488c4ecebbed049f46c189441fba48535
    BUG: 1228635
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/11103
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 02ccab9257ab36af281a4a610684a913dfa32d0f
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri May 29 10:40:22 2015 +0530

    glusterd/ afr: remove the readdir-failover option from rebalance process
    
    Remove the "replicate*.readdir-failover=off" xlator option from
    rebalance process' runner arguments because this is the default behaviour in
    afr-v2. i.e. reaaddir failover happens only if it is a new readdir
    (offset=0). 'Continuing'readdirs are always wound on the same child
    where the first readdir had happened and if that child is down, the
    readdir fails.
    
    The option cannot be removed from glusterd_volopt_map because there is a
    chance of ending up in peer rejected state in a heterogenous cluster
    (typical upgrade scenario) due to volinfo checksum mismatch. TODO:come up with
    some warning message to the user for such deprecated options if a volume
    set is attempted.
    
    Change-Id: I6a33dc9fae7cccea8c5fd3d9de40d88d13ad3689
    BUG: 1225328
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10935
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 5441db69f8562a0daa9e6d82aa4279ded0d6e649
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Jun 2 15:01:53 2015 +0530

    rpc: call transport_unref only on non-NULL transport
    
    BUG: 1227583
    Change-Id: Ifac4dd8c633081483e4eba9d7e5a89837b2a453a
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/11041
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit bf3a6dcdf3c8a8a64e7c864b56c4d9be60fca8e6
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jun 3 15:18:08 2015 +0530

    snapshot: Fix finding brick mount path logic
    
    Previously while finding brick mount paths
    of snap volume's bricks, we were taking brick order
    into consideration. This logic fails when a brick is
    removed or a tier is added.
    
    Hence modifying the logic to look for the first
    occurence of the word "brick" in the brick path.
    From there we iterate till we find a '/'. The string
    till the first '/' after we encounter the word brick
    is the brick mount path.
    
    Change-Id: Ic85983c4e975e701cdfd4e13f8e276ac391a3e49
    BUG: 1227646
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11060
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit d2d7afefd861943f26b290d214fb5213d24b6a02
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Jun 3 23:43:55 2015 +0530

    features/marker: Cleanup loc in case of errors
    
    Missing loc_wipe() for error paths in mq_readdir_cbk() can
    cause memory leaks. loc_wipe() is now done for both happy
    and unhappy paths.
    
    Change-Id: I882aa5dcca06e25b56a828767fb2b91a1efaf83b
    BUG: 1227904
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/11074
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit f1c20897cc18fb3b257880e7a098c05eae28fd0f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon May 11 12:36:33 2015 +0530

    uss: Take ref on root inode
    
    If we recieve a statfs call on snap directory, we will redirect
    the call into the root, by creating a new root loc. So it is better to
    take a ref on the root inode.
    (http://review.gluster.org/#/c/10358/5/xlators/features/
    snapview-client/src/snapview-client.c)
    
    Change-Id: I5649addac442d391b2550346b115dec58fed5b86
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10750
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit a615f6c078c76791318c2a58efcc8baef18c25db
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Mon Jun 1 17:48:23 2015 +0530

    tests/bitrot: Induce delay before invoking bitrot subcommands
    
    This is to prevent access to uninitialized variable in reconfigure()
    that's currently getting inititlized on CHILD_UP.
    
    [
        NOTE: This is a temporary fix and would not be needed when BZ
               #1226666 is fixed.
    ]
    
    Change-Id: I8779073fe7f315a380b833ddc248c99958de67d0
    BUG: 1226902
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/11033
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 402589f58cbb350dfedafa83e133664855ed37b2
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu May 14 15:00:59 2015 +0530

    glusterd/shared_storage: Provide a volume set option to create and mount the shared storage
    
    Introducing a global volume set option(cluster.enable-shared-storage)
    which helps create and set-up the shared storage meta volume.
    
    gluster volume set all cluster.enable-shared-storage enable
    
    On enabling this option, the system analyzes the number of peers
    in the cluster, which are currently connected, and chooses three
    such peers(including the node the command is issued from). From these
    peers a volume(gluster_shared_storage) is created. Depending on the
    number of peers available the volume is either a replica 3
    volume(if there are 3 connected peers),  or a replica 2 volume(if there
    are 2 connected peers). "/var/run/gluster/ss_brick" serves as the
    brick path on each node for the shared storage volume. We also mount
    the shared storage at "/var/run/gluster/shared_storage" on all the nodes
    in the cluster as part of enabling this option. If there is only one node
    in the cluster,  or only one node is up then the command will fail
    
    Once the volume is created, and mounted the maintainance of the
    volume like adding-bricks, removing bricks etc., is expected to
    be the onus of the user.
    
    On disabling the option, we provide the user a warning, and on
    affirmation from the user we stop the shared storage volume, and unmount
    it from all the nodes in the cluster.
    
    gluster volume set all cluster.enable-shared-storage disable
    
    Change-Id: Idd92d67b93f444244f99ede9f634ef18d2945dbc
    BUG: 1222013
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10793
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit c2898f040937492c69a603ab3605cbd441e1e1f3
Author: Milind Changire <mchangir@redhat.com>
Date:   Wed May 27 16:50:09 2015 +0530

    tools/glusterfind: verifying volume presence
    
    An invalid volume name passed to "pre", "post" and  "delete"
    operations throws up unfriendly errors. This patch presents
    friendly error messages.
    
    Change-Id: I233809653379b80b34c2e74c0b6f4fe502c8961e
    BUG: 1225424
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/10945
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit b15ee49c94c07ffd3c27384b45840eafd59997d4
Author: nnDarshan <dnarayan@redhat.com>
Date:   Tue May 12 17:57:46 2015 +0530

    snapshot/scheduler: Modified main() function to take arguments.
    
    Modified the main function to take script arguments, so that this
    script can be used as a module by other programs .
    
    Change-Id: I902f0bc7ddfbf0d335cc087f51b1a7af4b7157fc
    BUG: 1220670
    Signed-off-by: n Darshan <dnarayan@redhat.com>
    Reviewed-on: http://review.gluster.org/10760
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 1a0d76fa14ee88ce17e017c3ceb311417870e944
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Thu May 21 17:13:54 2015 +0530

    glusterd: do not show pid of brick in volume status if brick is down.
    
    glusterd is currently showing pid of brick in volume status if brick
    goes down.
    
    It should not show pid of brick if brick is down.
    
    Change-Id: I077100d96de381695b338382808bd8c37bf625c7
    BUG: 1223772
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10877
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 79d8916929f7d5b85a09ae9b75eadf945a3e11fb
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed May 27 14:36:24 2015 +0530

    bitrot/glusterd: scrub option should be disabled once bitrot option is reset
    
    Scrubber options should be disabled from the dictionary if user reset
    bitrot option.
    
    Change-Id: Ic7e390cf88b9b749f0ada8bbd4632f4cc0c4aff9
    BUG: 1220713
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10936
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit e1fb4e9ca7905243b57761ae1edb62a3fed76fc4
Author: Shyam <srangana@redhat.com>
Date:   Wed Jun 3 13:43:39 2015 -0400

    glusterd: Bump op version and max op version for 3.7.2
    
    As 3.7.1 is released, and a DHT configuration option needs higher
    op version, bumping the gluster op-version to 3.7.2 (or 30702).
    
    Change-Id: Iaed9e49b86a195653ddca55994e2c2398b2ee3bc
    BUG:  1227884
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/11070
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2b7ae84a5feb636f0e41d0ab36c04b7f3fbce520
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jun 2 17:58:00 2015 +0530

    features/quota: Fix ref-leak
    
    Change-Id: I0b44b70f07be441e044d9dfc5c2b64bd5b4cac18
    BUG: 1207735
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11045
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit b8b59fea7822f9ab1e10d7a3f730354fe82a6097
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 31 22:29:11 2015 +0200

    nfs: allocate and return the hashkey for the auth_cache_entry
    
    The allocation of the hashkey was never returned to the calling
    function.
    
    Allocating it with alloca() puts it on the stack, returning from the
    function makes the pointer invalid. Functions that are annotated with
    "inline" and call alloca(), will not always be inlined. Returning a
    pointer allocated with alloca() is in those cases not correct. One such
    confirmation was provided by GCC developer Alexandre Oliva:
     - http://gcc.gnu.org/ml/gcc-help/2004-04/msg00158.html
    
    It is more correct to call GF_MALLOC() and GF_FREE() for the hashkey. If
    this would result in preformance hit, we can always think of using
    alloca() again and turn make_hashkey() into a macro (yuck).
    
    Change-Id: Ia86a1f79d33240af4713bfb92f702b0ee6e87eb7
    BUG: 1226714
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/11019
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0209b18fd65f9df5ebd0a8764ebf864d0d392998
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 17 15:26:03 2015 +0200

    build: fix compiling on older distributions
    
    data-tiering is disabled on RHEL-5 because it depends on a too new
    SQLite version.
    
    This change also prevents installing some of files that are used by
    geo-replication, which is also not available on RHEL-5. geo-replication
    depends on a too recent version of Python.
    
    Due to an older version of OpenSSL, some of the newer functions can not
    be used. A fallback to previous functions is done. Unfortunately RHEL-5
    does not seem to have TLSv1.2 support, so only older versions can be
    used.
    
    Change-Id: I672264a673f5432358d2e83b17e2a34efd9fd913
    BUG: 1222317
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10803
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 990cb828a2e9b0d83a767977712305534fac39e2
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu May 21 14:58:26 2015 +0530

    features/shard: Handle symlinks appropriately in fops
    
    (f)stat, unlink and rename must skip doing inode_ctx_get()
    of shard block size on symbolic links.
    
    Change-Id: I68688532164dd2ab491ff5c59b343174f8c4ce7f
    BUG: 1223759
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10995
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit da111ae21429d33179cd11409bc171fae9d55194
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat May 30 10:23:33 2015 +0530

    afr: honour selfheal enable/disable volume set options
    
    afr-v1 had the following volume set options that are used to enable/ disable
    self-heals from happening in AFR xlator when loaded in the client graph:
    cluster.metadata-self-heal
    cluster.data-self-heal
    cluster.entry-self-heal
    
    In afr-v2, these 3 heals can happen from the client if there is an inode
    refresh. This patch allows such heals to proceed only if the corresponding
    volume set options are set to true.
    
    Change-Id: I8d97d6020611152e73a269f3fdb607652c66cc86
    BUG: 1226507
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11012
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9798a24febba9bbf28e97656b81b8a01a1325f68
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri May 29 18:11:01 2015 +0530

    snapshot/scheduler: Return proper error code in case of failure
    
    ENUM                              RETCODE     ERROR
    ----------------------------------------------------------
    INTERNAL_ERROR                    2           Internal Error
    SHARED_STORAGE_DIR_DOESNT_EXIST   3           Shared Storage Dir
                                                  does not exist
    SHARED_STORAGE_NOT_MOUNTED        4           Shared storage is not mounted
    ANOTHER_TRANSACTION_IN_PROGRESS   5           Another transaction is in progress
    INIT_FAILED                       6           Initialisation failed
    SCHEDULING_ALREADY_DISABLED       7           Scheduler is already disabled
    SCHEDULING_ALREADY_ENABLED        8           Scheduler is already enabled
    NODE_NOT_INITIALISED              9           Node not initialised
    ANOTHER_SCHEDULER_ACTIVE          10          Another scheduler is active
    JOB_ALREADY_EXISTS                11          Job already exists
    JOB_NOT_FOUND                     12          Job not found
    INVALID_JOBNAME                   13          Jobname is invalid
    INVALID_VOLNAME                   14          Volname is invalid
    INVALID_SCHEDULE                  15          Schedule is invalid
    INVALID_ARG                       16          Argument is invalid
    
    Change-Id: Ia1da166659099f4c951fcdb4d755529e41167b80
    BUG: 1218055
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/11005
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 9684b90526d03a15d451e341521d7df44adae73e
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Tue May 19 23:27:35 2015 +0530

    cluster/dht: fix incorrect dst subvol info in inode_ctx
    
    Stashing additional information in the inode_ctx to help
    decide whether the migration information is stale, which could
    happen if a file was migrated several times but FOPs only detected
    the P1 migration phase. If no FOP detects the P2 phase, the inode
    ctx1 is never reset.
    We now save the src subvol as well as the dst subvol in the
    inode ctx. The src subvol is the subvol on which the FOP was sent
    when the mig info was set in the inode ctx. This information is
    considered stale if:
    1. The subvol on which the current FOP is sent is the same as
    the dst subvol in the ctx
    2. The subvol on which the current FOP is sent is not the same
    as the src subvol in the ctx
    
    This does not handle the case where the same file might have been
    renamed such that the src subvol is the same but the dst subvol
    is different. However, that is unlikely to happen very often.
    
    Change-Id: I05a2e9b107ee64750c7ca629aee03b03a02ef75f
    BUG: 1142423
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/10834
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit b6eda067d2e2a0b56718ea71522f6c7b06a09f13
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu May 28 16:03:12 2015 +0530

    cluster/dht: pass a destination subvol to fop2 variants to avoid races.
    
    The destination subvol used in the fop2 variants is either stored in
    inode-ctx1 or local->cached_subvol. However, it is not guaranteed that
    a value stored in these locations before invocation of fop2 is still
    present after the invocation as these locations are shared among
    different concurrent operations. So, to preserve the atomicity of
    "check dst-subvol and invoke fop2 variant if dst-subvol found", we
    pass down the dst-subvol to fop2 variant.
    
    This patch also fixes error handling in some fop2 variants.
    
    Change-Id: Icc226228a246d3f223e3463519736c4495b364d2
    BUG: 1142423
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/10943
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit b7842d178a6019bc2c14ecaf18ae5438a46bda29
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sat May 16 21:23:48 2015 +0530

    features/shard: Fix incorrect parameter to get_lowest_block()
    
    Due to get_lowest_block() being a macro, what needs to be passed
    to it is the evaluation of the expression (local->offset - 1), without
    which its substitution can cause junk values to be assigned to
    local->first_block.
    
    This patch also fixes calls to get_highest_block() where if offset and
    size are both equal to zero, it could return negative values.
    
    Change-Id: I3ae918a0a3251ffd9ce8d2294bc5f9b681447627
    BUG: 1200082
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10804
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit e1d9895ba6f7763ba4602094f6516a6ab4a054d4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jun 1 11:55:29 2015 +0530

    libglusterfs: Copy d_len and dict as well into dst dirent
    
    Also, added memory allocation failure checks in light of the
    comments received @
    http://review.gluster.org/#/c/10809/2/libglusterfs/src/gf-dirent.c, and
    http://review.gluster.org/#/c/10809/1/xlators/features/shard/src/shard.c
    
    Change-Id: Ie4092218545c8f4f8a0e6cc1fec6ba37bbbf2620
    BUG: 1226551
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/11026
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9a314fa22667bf5afe56e63e73f4b0f50cd291f6
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jun 2 21:49:13 2015 +0530

    contrib/timer-wheel: fix deadlock in del_timer()
    
    commit eaf3bfa added mod_timers() and successfully screwed up
    del_timer() by incorrectly wrapping it within double lock
    blocks.
    
    del_timer() was included before the above commit for the sake of
    timer API completion, thankfully noone used it till now.
    
    Change-Id: I07a454a216cf09dbb84777a23630e74a1e7f2830
    BUG: 1227449
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/11050
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 29d5bd5fc8a7b24865801de9f2e3f10d55af6e85
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Sun May 31 19:53:41 2015 +0200

    cluster/ec: Fix incorrect check for iatt differences
    
    A previous patch (http://review.gluster.org/10974) introduced a
    bug that caused that some metadata differences could not be
    detected in some circumstances. This could cause that self-heal
    is not triggered and the file not repaired.
    
    We also need to consider all differences for lookup requests, even
    if there isn't any lock. Special handling of differences in lookup
    is already done in lookup specific code.
    
    Change-Id: I3766b0f412b3201ae8a04664349578713572edc6
    BUG: 1225793
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/11018
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 3a94f4c52b56f08c326d3212ca5708e8daf8585b
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Jun 1 16:53:32 2015 +0530

    tiering:static function called from a non static inline function
    
    gcc v5.1.1 throws warning for calling a static function from a
    non-static inline function.
    
    
    <snippet from compiler warning>
      CC       tier.lo
    tier.c:610:15: warning: 'tier_migrate_using_query_file' is static but used in inline function 'tier_migrate_files_using_qfile' which is not static
             ret = tier_migrate_using_query_file ((void *)query_cbk_args);
                   ^
    tier.c:585:47: warning: 'tier_process_brick_cbk' is static but used in inline function 'tier_build_migration_qfile' which is not static
             ret = dict_foreach (args->brick_list, tier_process_brick_cbk,
                                                   ^
    tier.c:565:176: warning: 'demotion_qfile' is static but used in inline function 'tier_build_migration_qfile' which is not static
    tier.c:565:158: warning: 'promotion_qfile' is static but used in inline function 'tier_build_migration_qfile' which is not static
    tier.c:563:58: warning: 'demotion_qfile' is static but used in inline function 'tier_build_migration_qfile' which is not static
    tier.c:563:40: warning: 'promotion_qfile' is static but used in inline function 'tier_build_migration_qfile' which is not static
             ret = remove (GET_QFILE_PATH (is_promotion));
                                            ^
      CCLD     tier.la
    
    </snip>
    
    Change-Id: I46046feeb79ab4e2724b0ba6b02c9ec8b121ff4e
    BUG: 1226881
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/11032
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 62992ac27d729ecc7da500ce42dc46592c13d003
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Jun 1 15:21:00 2015 -0400

    stripe: fix use-after-free
    
    Pretty much a classic case.  STRIPE_STACK_UNWIND frees the "local"
    structure.  In the "virtual xattr" path, used for lock recovery among
    other things, we were calling STRIPE_STACK_UNWIND and then continuing to
    clean up "our" parts of the just-freed structure.  Oops.
    
    Change-Id: Ifa961b89cd21a2893de39a9eea243d184f9eac46
    BUG: 1222317
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/11037
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5a66d1e6186acfb15e9957b5f196659da8f3cf6d
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri May 15 13:37:24 2015 -0400

    cluster/tier: make attach/detach work with new rebalance logic
    
    The new rebalance performance improvements added new
    datastructures which were not initialized in the
    tier case. Function dht_find_local_subvol_cbk() needs
    to accept a list built by lower level DHT translators
    in order to build the local subvolumes list.
    
    Change-Id: Iab03fc8e7fadc22debc08cd5bc781b9e3e270497
    BUG: 1222088
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10795
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 9f29401791ad374015c3d0927b7cf967d66471a6
Author: Shyam <srangana@redhat.com>
Date:   Fri May 15 15:50:42 2015 -0400

    dht: Add lookup-optimize configuration option for DHT
    
    Currently with commit 4eaaf5 a mixed version cluster would
    have issues if lookup-uhashed is set to auto, as older clients
    would fail to validate the layouts if newer clients (i.e 3.7 or
    upwards) create directories. Also, in a mixed version cluster
    rebalance daemon would set commit hash for some subvolumes and
    not for the others.
    
    This commit fixes this problem by moving the enabling of the
    functionality introduced in the above mentioned commit to a
    new dht option. This option also has a op_version of 3_7_1
    thereby preventing it from being set in a mixed version
    cluster. It brings in the following changes,
    - Option can be set only if min version of the cluster is
    3.7.1 or more
    - Rebalance and mkdir update the layout with the commit hashes
    only if this option is set, hence ensuring rebalance works in a
    mixed version cluster, and also directories created by newer
    clients do not cause layout errors when read by older clients
    - This option also supersedes lookup-unhased, to enable the
    optimization for lookups more deterministic and not conflict
    with lookup-unhashed settings.
    
    Option added is cluster.lookup-optimize, which is a boolean.
    
    Usage: # gluster volume set VOLNAME cluster.lookup-optimize on
    
    Change-Id: Ifd1d4ce3f6438fcbcd60ffbfdbfb647355ea1ae0
    BUG:  1222126
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/10797
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2df57ab7dc7b9d7deb0eebad96036149760d607b
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue May 5 18:08:25 2015 +0530

    glusterd/snapshot: Return correct errno in events of failure - PATCH 2
    
    ENUM           RETCODE        ERROR
    -------------------------------------------------------------
    EG_INTRNL      30800          Internal Error
    EG_OPNOTSUP    30801          Gluster Op Not Supported
    EG_ANOTRANS    30802          Another Transaction in Progress
    EG_BRCKDWN     30803          One or more brick is down
    EG_NODEDWN     30804          One or more node is down
    EG_HRDLMT      30805          Hard Limit is reached
    EG_NOVOL       30806          Volume does not exist
    EG_NOSNAP      30807          Snap does not exist
    EG_RBALRUN     30808          Rebalance is running
    EG_VOLRUN      30809          Volume is running
    EG_VOLSTP      30810          Volume is not running
    EG_VOLEXST     30811          Volume exists
    EG_SNAPEXST    30812          Snapshot exists
    EG_ISSNAP      30813          Volume is a snap volume
    EG_GEOREPRUN   30814          Geo-Replication is running
    EG_NOTTHINP    30815          Bricks are not thinly provisioned
    
    Change-Id: I49a170cdfd77df11fe677e09f4e063d99b159275
    BUG: 1212413
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10588
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 59981aeb1cd02dcc534ec43ec4ec5bca5cbbd1fb
Author: Anuradha <atalur@redhat.com>
Date:   Wed May 13 15:29:57 2015 +0530

    cli: Fix incorrect parse logic for volume heal commands
    
    heal-op was being incorrectly set to
    GF_SHD_OP_SBRAIN_HEAL_FROM_BIGGER_FILE.
    
    Change-Id: I4d4461c7737feae30102e82f7788083017485669
    BUG: 1221128
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10771
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>

commit 010da8e41edc510c4c0236a4ec23e9e628faebe7
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Jun 30 14:04:34 2014 -0400

    DHT/permissoin: Let setattr consume stat built from lookup in heal path
    
    setattr call post mkdir(selfheal) ends up using the mode bits
    returned by mkdir,which miss the required suid, sgid and sticky bit.
    Hence, the fix is to use the mode bits from local->stbuf which was used
    to create the missing directories.
    
    Change-Id: I478708c80e28edc6509b784b0ad83952fc074a5b
    BUG: 1110262
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/8208
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit f3a340694fcb195aa8b546578c348b41fb2208d1
Author: Anuradha <atalur@redhat.com>
Date:   Mon May 25 11:07:27 2015 +0530

    features/quota : Do unwind if postbuf is NULL
    
    If postbuf in quota_writev_cbk is NULL directly
    an unwind should be done. Trying to dereference
    it will lead to a crash.
    
    Change-Id: Idba6ce3cd1bbf37ede96c7f17d01007d6c07057a
    BUG: 1221577
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10898
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 751c4583bbaa59ebfe492ab6ecfab3108711f4c5
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu May 7 09:22:04 2015 -0400

    common-ha: fix race between setting grace and virt IP fail-over
    
    Also send stderr output of `pcs resource {create,delete} $node-dead_ip-1`
    to /dev/null to avoid flooding the logs
    
    Change-Id: I29d526429cc4d7521971cd5e2e69bfb64bfc5ca9
    BUG: 1219485
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10646
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>

commit 3f11b8e8ec6d78ebe33636b64130d5d133729f2c
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu May 28 14:00:37 2015 -0400

    cluster/dht: maintain start state of rebalance daemon across graph switch.
    
    When we did a graph switch on a rebalance daemon, a second call
    to gf_degrag_start() was done. This lead to multiple threads
    doing migration. When multiple threads try to move the same
    file there can be deadlocks.
    
    Change-Id: I931ca7fe600022f245e3dccaabb1ad004f732c56
    BUG: 1226005
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10977
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit eeb356584897ff778ffcbacff1c71d35d277b726
Author: Anoop C S <achiraya@redhat.com>
Date:   Fri May 29 16:33:09 2015 +0530

    features/changelog: Remove inline keyword to avoid warnings (gcc v5.1.1)
    
    When compiled with gcc5, following warnings were displayed
    and volume start failed:
    
    changelog-helpers.h:499:1: warning: inline function 'changelog_dispatch_event'
    declared but never defined
     changelog_dispatch_event (xlator_t *, changelog_priv_t *, changelog_event_t *);
    
    gf-changelog-journal-handler.c:692:17: warning: 'list_add_tail' is static but
    used in inline function 'gf_changelog_queue_journal' which is not static
                     list_add_tail (&entry->list, &jnl_proc->entries);
    
    Fix is to remove the keyword from function prototype and
    definitions.
    
    Change-Id: I188b35b7ca087a94d7a48a052b05a6d845e3b74b
    BUG: 1226307
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/11004
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 754df15ece18864adc5297c292c20a846804cbec
Author: vmallika <vmallika@redhat.com>
Date:   Tue Apr 14 10:44:13 2015 +0530

    quota: retry connecting to quotad on ENOTCONN error
    
    Suppose if there are two volumes vol1 and vol2,
    and quota is enabled and limit is set on vol1.
    Now if IO is happening on vol1 and quota is enabled/disabled
    on vol2, quotad gets restarted and client will receive
    ENOTCONN in the IO path of vol1.
    
    This patch will retry connecting to quotad upto 60sec
    in a interval of 5sec (12 retries)
    If not able to connect with 12 retries, then return ENOTCONN
    
    Change-Id: Ie7f5d108633ec68ba9cc3a6a61d79680485193e8
    BUG: 1211220
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit d9efe535c9ee0d01e0718d2bb871067785d33d14
Author: vmallika <vmallika@redhat.com>
Date:   Thu Apr 30 12:35:40 2015 +0530

    features/quota: prevent statfs frame-loss when an error happens during
    ancestry building.
    
    We do quota_build_ancestry in function 'quota_get_limit_dir',
    suppose if quota_build_ancestry fails, then we don't have a
    frame saved to continue the statfs FOP and client can hang.
    
    Change-Id: I92e25c1510d09444b9d4810afdb6b2a69dcd92c0
    BUG: 1178619
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9380
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 43d464326b1158d5b6caa60b2eac5b78f20b5026
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon May 18 18:06:32 2015 +0530

    features/shard: Fix issue with readdir(p) fop
    
    Problem:
    
    When readdir(p) is performed on '/' and ".shard" happens to be
    the last of the entries read in a given iteration of dht_readdir(p)
    (in other words the entry with the highest offset in the dirent list
    sorted in ascending order of d_offs), shard xlator would delete this
    entry as part of handling the call so as to avoid exposing its presence
    to the application. This would cause xlators above (like fuse,
    readdir-ahead etc) to wind the next readdirp as part of the same req
    at an offset which is (now) the highest d_off (post deletion of .shard)
    from the previously unwound list of entries. This offset would be less
    than that of ".shard" and therefore cause /.shard to be read once again.
    If by any chance this happens to be the only entry until end-of-directory,
    shard xlator would delete this entry and unwind with 0 entries, causing the
    xlator(s) above to think there is nothing more to readdir and the fop is
    complete. This would prevent DHT from gathering entries from the rest of
    its subvolumes, causing some entries to disappear.
    
    Fix:
    
    At the level of shard xlator, if ".shard" happens to be the last entry,
    make shard xlator wind another readdirp at offset equal to d_off of
    ".shard". That way, if ".shard" happens to be the only other entry under '/'
    until end-of-directory, DHT would receive an op_ret=0. This would enable it
    to wind readdir(p) on the rest of its subvols and gather the complete picture.
    
    Also, fixed a bug in shard_lookup_cbk() wherein file_size should be fetched
    unconditionally in cbk since it is set unconditionally in the wind path, failing
    which, lookup would be unwound with ia_size and ia_blocks only equal to that of
    the base file.
    
    Change-Id: I6c2bc770f1bcdad51c273c777ae0b42c88c53f61
    BUG: 1222379
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10809
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7023870b28b1eb87fb6eca2904c72e91fdcaf625
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri May 29 13:47:14 2015 -0400

    build: outdated autotools helper config.* files in dist tarfile
    
    Our jenkins release task clones the source, runs ./autogen.sh (where
    config.{guess,sub} come from) and ./configure, before running `make
    dist` to product the release glusterfs-X.Y.Z.tar.gz.
    
    The config.{guess,sub} in the tar file come from the archaic autoconf
    in CentOS 6.3, which is what the glusterfs jenkins is running on.
    
    We should not be shipping the (arbitrary, old) config.{guess,sub} files
    from our jenkins machine.
    
    Change-Id: Ib7643ae2e54d0e25c95f4e93e5dffb22cbe11523
    BUG: 1223937
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11009
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 894a517a12411c4dfbdeda6b9e90df26f5855d2e
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri May 22 00:37:58 2015 +0530

    socket: throttle only connected transport
    
    BUG: 1224016
    Change-Id: I2352c6661ae5aee8cf06e572ec0462b76901d46f
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/10887
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 37cc99fc3a991241df49133902928bd789d95066
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri May 15 14:10:48 2015 +0530

    features/bit-rot-stub: implement mknod fop
    
    With the absence of mknod() fop implementation in bitrot stub,
    further operations that trigger versioning resulted in crashes
    as they expect the inode context to be valid. Therefore, this
    patch implements mknod() following similar simantics to fops
    such as create().
    
    Furthermore, bitrot stub test C program is fixed to stop lying
    and validate obj versions according to the versioning protocol.
    
    Change-Id: If76f252577445d1851d6c13c7e969e864e2183ef
    BUG: 1221914
    Original-Author: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10790
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d76e9b83454786e6845d0cad3c2c0695815fae1b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 27 16:27:25 2015 +0530

    featuress/changelog: On snapshot, notify irrespective of failures
    
    During snapshot, changelog barrier is enabled and a
    explicit rollover of changelog is initiated. During
    rollover of changelog, if any error or changelog is
    empty, the notification was not sent to reconfigure
    and hence snapshot was failing because of timeout.
    This patch addresses it by sending notification
    irrespective of failures and sends error if any
    back to barrier.
    
    Change-Id: I898af624b44555281a9e43c69066077e0e121c17
    BUG: 1225542
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10951
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit ad7bd0865db4653e609bfc08cfc50225c87f3748
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon May 18 19:32:48 2015 +0530

    spec: move file peer_add_secret_pub to server RPM
    
    peer_add_secret_pub was developed as part of geo-replication
    feature. glusterfind has a dependency on the peer_add_secret_pub
    for distributing SSH secrets. The dependency was manifest while
    QA testing glusterfind. peer_add_secret_pub is now moved to the
    server RPM to support glusterfind without creating a dependency
    on the geo-replication RPM
    
    Change-Id: I1345e13fd6d218eb722cd72ca1b9dd04adf4d316
    BUG: 1221544
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/10807
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit f999a8634850db0627c768b12dba0aa84b4ff7b7
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed May 20 14:34:11 2015 +0530

    geo-rep: Ignore ESTALE during unlink/rmdir
    
    during unlink/rmdir of Parent_GFID/Basename, if parent
    directory does not exists. Parent GFID will not get resolved
    and DHT raises ESTALE instead of ENOENT.
    
    Now ESTALE errors ignored during unlink/rmdir
    
    BUG: 1223280
    Change-Id: If275c89fb9fc7d16004550805a4cd65be818540d
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10837
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 457edddbaae62d6956c37b6d1fd45c75ae2c7cff
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri May 29 10:00:13 2015 +0530

    features/bitrot: serialize versioning
    
    Current signing interface (fsetxattr()) had couple of issues:
    
    One, a signing request (by bitrot daemon) is denied if the version
    against which an object is to be signed is unequal to the current
    version of the object (cases where another subsequent modification
    increments the version). Such request(s) are rejected with EINVAL
    sent back to the signer resulting in a bunch of errors (in logs)
    reported by bitrot daemon. Although, the object would be eventaully
    signed with the version matching the current version, the "lagging"
    request should be correctly handled.
    
    Two, more than one signing request could race against each other
    with the object getting signed with a version depending on which
    request ended up last in the race. Although harmless to some extent,
    such a case could end up marking the object's signature as stale
    for infinity (if the object is *never* touched) thereby resulting
    in scrubber skipping the object during verification.
    
    This patch fixes these issues by ordering signing request(s) and
    fixing version comparison checks at the time of signing.
    
    Change-Id: I9fa83dfa3be664ba4db61d7f2edc408f4bde77dd
    BUG: 1221938
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10832
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5863ab43d7f3b045f5b889b98f73687b07b3f0e8
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue May 26 13:01:17 2015 +0530

    geo-rep: Fix Data counter issue in status
    
    ENTRY and META operations executed sequentially, DATA operations
    are handled async, increment happens when a changelog parsed.
    Decrement happens after the sync of all files.
    
    'files_in_batch' was reset multiple times in batch instead of once.
    
    BUG: 1224098
    Change-Id: I87617f2fd5f4d3221a1c9f9d5a8efb0686c42bbe
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10911
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 35f7d213fe7395ba502a8e209b04c2be1ea75928
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 29 16:28:10 2015 +0530

    features/qemu-block: Don't unref root inode
    
    Root inode doesn't participate in ref/unref. Don't do it
    in fini as by the time fini is called itable would be destroyed.
    
    BUG: 1226276
    Change-Id: I704d0a3c0813cb8f6c3f1f7d613c89aca8f4f9ad
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11002
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 90ed7128dfd4d10e65efcc866cfd610ba3b0cc30
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu May 28 16:54:59 2015 +0200

    cluster/ec: Ignore differences in non locked inodes
    
    When ec combines iatt structures from multiple bricks, it checks
    for equality in important fields. This is ok for iatt related to
    inodes involved in the operation that have been locked before
    starting execution. However some fops return iatt information
    from other inodes. For example a rename locks source and destination
    parent directories, but it also returns an iatt from the entry
    itself.
    
    In these cases we ignore differences in some fields to avoid false
    detection of inconsistencies and trigger unnecessary self-heals.
    
    Another issue is solved in this patch that caused that the real
    size of the file stored into the inode context was lost during
    self-heal.
    
    Change-Id: I8b8eca30b2a6c39c7b9bbd3b3b6ba95228fcc041
    BUG: 1225793
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/10974
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System

commit 54b193760ce59569fa5813e64af7753afbf0d500
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 27 15:00:00 2015 -0400

    common-ha: handle long node names and node names with '-' and '.' in them
    
    sourcing the /etc/ganesha/ganesha-ha.conf file seemed like a simple
    and elegant solution for reading config params, but bash variable names
    do not allow '-' and '.' in them.
    
    Change-Id: I0d2e6cb21017472b1e0f764335cf28946cca95f0
    BUG: 1225572
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10952
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 378fa28f2ed397e71d05b5869026e1e23bab9e96
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 29 15:34:09 2015 +0530

    heal: Do not call glfs_fini in final builds
    
    BUG: 1226253
    Change-Id: Id18a7a3a2b9c2cffea6f3d7c8676712fcf9691e5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/11001
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8772ca6c559623e96bbdd40811d8ec25210810fc
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri May 29 11:34:38 2015 -0400

    build: xlators/mgmt/glusterd/src/glusterd-errno.h is not in dist tarball
    
    attempts to build RPMs, e.g. in tree with `make -C extras/LinuxRPM
    glusterrpms` or from a dist tarball produced in tree will fail with:
    
    glusterd-locks.c:19:28: fatal error: glusterd-errno.h: No such file
    or directory compilation terminated
    
    Change-Id: I365dbcd5b7bc3410f4a7752a05f570e4061461d0
    BUG: 1226384
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/11007
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 8edc416f05d48560a387de9e3eb55a3c4087f23f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri May 29 20:19:57 2015 +0530

    tests : fix spurious failure in bug-973073.t
    
    remove_brick_completed needs the same fix as 02c04579
    
    Change-Id: I1a65f9095e4b01e6bb014440fc89696a4eebf8ca
    BUG: 1226367
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/11006
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 8a9328e37b8c63d60583184dc8dab12f85810682
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon May 18 16:26:02 2015 +0200

    build: do not #include "config.h" in each file
    
    Instead of including config.h in each file, and have the additional
    config.h included from the compiler commandline (-include option).
    
    When a .c file tests for a certain #define, and config.h was not
    included, incorrect assumtions were made. With this change, it can not
    happen again.
    
    BUG: 1222319
    Change-Id: I4f9097b8740b81ecfe8b218d52ca50361f74cb64
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10808
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 5d912230a7d4f9979c10ff15da724624bd8e069d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed May 27 11:56:53 2015 +0530

    scripts: Added script stop-all-gluster-processes.sh in rpm
    
    This script was not included as part of rpm. Fixed now
    
    BUG: 1204641
    Change-Id: I5e559b187253cc2f4f8ea7cf8ec56a32802e5ab2
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10931
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 15a28c2b70003434d448a67d66ff722294e816f7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat May 9 23:11:15 2015 +0530

    worm: Let lock, zero xattrop calls succeed
    
    Locks can be taken just to inspect the data as well, so allow them.
    Xattrops are internal fops so we can allow them as well as longs as
    it doesn't change the xattr value, i.e. All-zero xattrop.
    
    Change-Id: Idc06d2043eb472c064db40d811a80058f0bda378
    BUG: 1211123
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10727
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: NetBSD Build System

commit b0fb6eb3071ce45a8964423237577d1d9b9605d9
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 20 09:34:26 2015 -0400

    glusterfs.spec.in: python-gluster should be 'noarch'
    
    Change-Id: Ic4f498ce87a5a7f21b637da1b63a290b9fe89b66
    BUG: 1219954
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10846
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 3fec17dd4535866de61ae3c12cbc590062d08d5d
Author: anand <anekkunt@redhat.com>
Date:   Tue May 19 14:31:23 2015 +0530

    Build: glusterd socket file cleanup to set SElinux context properly.
    
    Issue : glusterd runs as rpm_script_t when it's executed from the rpm scriptlet, socket file
    created in this context is set as rpm_script_t type, glusterd unable to access socket file
    when it runs in glusterd_t context (glusted not cleaning socket file while stoping due to
    some cleanup issues, so cleanup required in rpm install).
    
    Fix: In rpm post upgrade,remove the glusterd.socket file which is created by glusterd in rpm context.
    so that glusterd recreates socket file when it runs in glusterd_t context.
    
    Change-Id: I57041e2e0f9d3e74e12198507a9bd47d09f4a132
    BUG: 1223185
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10815
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 99eaa1a8255105687c78f8dda48c0a60023e1ffc
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Apr 20 10:08:03 2015 +0530

    features/quota : Make "quota-deem-statfs" option "on" by default, when quota is enabled
    
    As of now it is expected from user to set deem-statfs to "on" when
    quota is enabled. Better to turn it "on" by default when quota is enabled.
    
    Change-Id: I85e0b919b1bdb74ac21e256073eebcb55bcb8e2a
    BUG: 1213364
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/10299
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 3eaf21e3cc8cf481226d1ed495d7261b1acbb594
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu May 21 11:55:03 2015 +0530

    geo-rep: Disable xattrs and acls support with tar_ssh
    
    Geo-rep can't sync xattrs and acls with tar over ssh
    for following reasons.
    
    Issue 1: xattrs doesn't sync with tar over ssh.
    
    Reason: untar doesn't respect '--overwrite' option when used along
            with '--xattrs'. So it sends unlink if the file exists on
            destination and re-creates afresh. But all entry operations
            are banned in aux-gfid-mount as it may lead to gfid-mismatch.
            Hence fails with EPERM. This happens only when some xattr is
            set on a file in master volume.
    
    Issue2: acls on directories does not sync with tar over ssh.
    
    Reason: tar tries to opendir ".gfid/<gfid1>" and is not supported
            by gfid-access-translator as readirp can't be handled on
            virtual inodes and hence fails with ENOTSUP where as it syncs
            for files.
    
    Since the issue is with tar commmand it self and nothing could be
    done from gluster side, disabling xattr and acls support with tar
    over ssh option.
    
    Geo-rep can sync xattrs and acls with 'rsync' as the sync engine.
    
    Change-Id: I6821d327e7fe15545adef644869aa2389f79c701
    BUG: 1223642
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10873
    Tested-by: NetBSD Build System
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 4675bffe46d4cd93ad7198167ca4beb9da4e293e
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu May 21 17:00:59 2015 +0530

    geo-rep: Fix acl mounting in mountbroker setup
    
    Add acl option to geo-rep mount specification template
    (georep_mnt_desc_template) for mountbroker setup.
    
    Change-Id: I5b93ebb81bd308fc343c3b9e21c36c78acedcbaa
    BUG: 1223741
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10876
    Tested-by: NetBSD Build System
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 4397d7e72fdff6f01c59b72eebea421f23c1a392
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue May 5 10:58:10 2015 +0530

    glusterd/snapshot: Return correct errno in events of failure - PATCH 1
    
    RETCODE              ERROR
    -------------------------------------------
    30800                Internal Error
    30801                Another Transaction In Progress
    
    Change-Id: Ica7fd2e513b2c28717b6df73cfb2667725dbf057
    BUG: 1212413
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10313
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e6934debda3a67b5666f1aa30b33c5267de49d84
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue May 19 17:04:55 2015 +0530

    Changing log level from Warning to Debug
    
    Change-Id: Ic4306ebb5a58c2ca310e973bb562be1ca3e4885f
    BUG: 1202758
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/10829
    Tested-by: NetBSD Build System
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d67eb34b2a5b5e3cb926ff4c86a163148743829c
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu May 7 17:50:25 2015 +0530

    snapshot/scheduler: Do not enable scheduler if another scheduler is running
    
    Check if another snapshot scheduler is running before
    enabling the scheduler.
    
    Also introducing a hidden option, disable_force
    
    "snapshot_scheduler.py disable_force" will disable the
    cli snapshot scheduler from any node, even though the node
    has not been initialised for the scheduler, as long as the
    shared storage is mounted
    
    This option is hidden, because we don't want to encourage
    users to use all commands from nodes that are not initialised.
    
    Change-Id: I7ad941fbbab834225a36e740c61f8e740813e7c8
    BUG: 1219442
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10641
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit b7f05e64f615a12e6487eab64544b8f92a6037ae
Author: vmallika <vmallika@redhat.com>
Date:   Fri May 22 14:04:31 2015 +0530

    quota: quota.conf backward compatibility fix
    
    In release-3.7 the format of quota.conf is changed.
    There is a backward compatibility issues during upgrade
    1) There can be an issue when peer sync between node-3.6 and node-3.7
    2) If the user sets/removes limit, there is will different format of
       file in node-3.6 and node-3.7
    
    This patch fixes the issue:
    1) restrict the user to execute command quota enable, limit-usage, remove
    2) write quota.conf in older format if op-version is less than 3.6
    
    Change-Id: Ib76f5a0a85394642159607a105cacda743e7d26b
    BUG: 1223739
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10889
    Tested-by: NetBSD Build System
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 19818254fa7d2b227d212e0a62c37846aef3fc24
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed May 13 14:35:47 2015 +0530

    features/bitrot: refactor brick connection logic
    
    Brick connection was bloated (and not implemented efficiently) with
    calls which were not required to be called under lock. This resulted
    in starvation of lock by critical code paths. This eventally did not
    scale when the number of bricks per volume increases (add-brick and
    the likes).
    
    Also, this patch cleans up some of the weird reconnection logic that
    added more to the starvation of resources and cleans up uncontrolled
    growing of log files.
    
    Change-Id: I05e737f2a9742944a4a543327d167de2489236a4
    BUG: 1207134
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/10763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: NetBSD Build System

commit 7bfd49705b8c17e779b88dd33122d2ce213dd1fb
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 12 18:49:15 2015 +0530

    glusterd: function to create duplicate of volinfo should copy subvol_count
    
    when we create duplicate volfile from a existing volfile,
    we are not copying the variable subvol_count to the new
    volfile.
    
    Change-Id: I943aa7fdf1a2ca5bf57522cb2402b6b3165501ac
    BUG: 1215002
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10761
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit 433d1154d36cbb2b0c3218247e656940e1fc40fb
Author: Shyam <srangana@redhat.com>
Date:   Wed May 20 09:47:05 2015 -0400

    glusterd: Bump op version and max op version for 3.7.1
    
    As 3.7 is released, and a DHT configuration option needs higher
    op version, bumping the gluster op-version to 3.7.1 (or 30701).
    
    Change-Id: I9747cf93b41be72e43077ed8e977e21eed99ccc3
    BUG:  1223432
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/10849
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ffc15b7ef0631b571be00cdb7d091cac84e314f5
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri May 15 16:03:00 2015 +0530

    tiering/rebalance: Use separate pid/socket file for tiering
    
    When promotion/demotion daemon starts, it uses the same pidfile
    as rebalance. This patch will introduce a different pid file
    for the same.
    
    Change-Id: Ic484c53f51e00ae6b2d697748a9600b14829e23b
    BUG: 1221970
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10792
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit 05566baee6b5f0b2a3b083def4fe9bbdd0f63551
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue May 19 14:54:32 2015 +0530

    tiering/nfs: duplication of nodes in client graph
    
    When creating client volfiles, xlator tier-dht will
    be loaded for each volume. So for services like nfs
    have one or more volumes . So for each volume in the
    graph a tier-dht xlator will be created. So the graph
    parser will fail because of the redundant node in
    graph.
    
    By this change tier-dht will be renamed as volname-tier-dht
    
    Change-Id: I3c9b9c23ddcb853773a8a02be7fd8a5d09a7f972
    BUG: 1222840
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10820
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 3cb713f2aec3c2191cf8fd2df830b92bf3ad92d4
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed May 13 20:33:45 2015 +0530

    tier: Do not allow detach-tier commands on a non-tiered volume
    
    Change-Id: Ic92d25db68e40ef4a4388ef42affd1b3ee5a7ec6
    BUG: 1221270
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10773
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit f1fb71bbf677be40b7bab997221f832c7fa7527a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed May 13 16:53:22 2015 +0530

    tiering: Correct errors in cli and glusterd
    
    Problem 1:
    
    volume info shows Cold Bricks instead of Tier type
      eg:
    Volume Name: patchy2
    Type: Tier
    Volume ID: 28c25b8d-b8a1-45dc-b4b7-cbd0b344f58f
    Status: Started
    Number of Bricks: 3
    Transport-type: tcp
    Hot Tier :
    Hot Tier Type : Distribute
    Number of Bricks: 1
    Brick1: 10.70.1.35:/home/brick43
    Cold Bricks:
    Cold Tier Type : Distribute
    Number of Bricks: 2
    Brick2: 10.70.1.35:/home/brick19
    Brick3: 10.70.1.35:/home/brick16
    Options Reconfigured:
    
    Problem 2: Detach-tier sending enums of Rebalance
    
       detach-tier has it's own Enum to send with detach-tier command,
    using that enums will make more appropriate.
    
    Problem 3:
    
    Wrongly sets hot_brick count during the dictionary copying for response
    
    Change-Id: Icc054a999a679456881bc70511470d32ff8a86e4
    BUG: 1211264
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10768
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit d133071e7ced1794e09ffe4ef8cb14cf5b9f7e75
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Apr 29 12:00:40 2015 +0530

    glusterd/tiering: Exchange tier info during glusted handshake
    
    Change-Id: Ibc2f8eeb32d3e5dfd6945ca8a6d5f0f80a78ebac
    BUG: 1211264
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10449
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit 19d7b6097393e4bf20f77e96cc4b3dd8f2561513
Author: Günther Deschner <gd@samba.org>
Date:   Thu Apr 16 11:29:00 2015 +0200

    xlators/cluster/dht: Fix Explicit null dereferenced (CID 1291727).
    
    Coverity CID 1291727.
    
    Guenther
    
    Change-Id: I95f01b638f74370f0ef04383f0f9d5799abe31f5
    BUG: 789278
    Signed-off-by: Guenther Deschner <gd@samba.org>
    Reviewed-on: http://review.gluster.org/10300
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6fc12a43f3e20ea24969e5a3c949f7c27d9c1893
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu May 21 19:55:02 2015 +0530

    features/bitrot: reimplement scrubbing frequency
    
    This patch reimplments existing scrub-frequency mechanism used
    to schedule scrubber runs. Existing mechanism uses periodic
    sleeps (waking up periodically on minimum granularity) and
    performing a number of tracking checks based on counters and
    sleep times. This patch does away with all the nifty counters
    and uses timer-wheel to schedule scrub runs.
    
    Scheduling changes are peformed by merely calculating the new
    expiry time and calling mod_timer() [mod_timer_pending() in
    some cases] making the code more debuggable and easier to
    follow. This also introduces "hourly" scrubbing tunable as an
    aid for testing scrubbing during development/testing cycle.
    
    One could also implement on-demand scrubbing with ease: by
    invoking mod_timer() with an expiry of one (1) second, thereby
    scheduling a scrub run the very next second.
    
    Change-Id: I6c7c5f0c6c9f886bf574d88c04cde14b76e60a8b
    BUG: 1224596
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10893
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e878b0bcbaa19e46517e44284685ef99b885117b
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Mon Apr 13 14:24:44 2015 +0530

    cluster/dht: Fix dht_setxattr to follow files under migration
    
    If a file is under migration, any xattrs created on it
    are lost post migration of the file. This is because
    the xattrs are set only on the cached subvol of the source
    and as the source is under migration, it becomes a linkto file
    post migration.
    
    Change-Id: Ib8e233b519cf954e7723c6e26b38fa8f9b8c85c0
    BUG: 1193636
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/10212
    Tested-by: NetBSD Build System
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit eaf3bfa1886928240eda3a83ab1ece3d61f7fd50
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri May 22 11:54:11 2015 +0530

    contrib/timer-wheel: mod_timer() and friends
    
    Couple of timer-wheel api's to modify timer expiry times:
    
      mod_timer()
      mod_timer_pending()
    
    Both the api's perform almost the same job with one minute
    difference: mod_timer_pending() modifies timer expiry only
    if the timer is pending (i.e. being tracked in timer-wheel).
    
    Change-Id: Iae64934854ccfd6b081b849bff998ae3c3021bac
    BUG: 1224596
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10892
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e9290dc0db7bee31cda1cbed1d9eb68d9c404746
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue May 26 21:51:31 2015 +0530

    features/bitrot: stub improvements and fixes
    
    This patch refactors the signing trigger mechanism used by bitrot
    daemon as a "catch up" meachanism to sign files which _missed_
    signing on the last run either due to bitrot being disabled and
    enabled again or if bitrot is enabled for a volume with existing
    data.
    
    Existing implementation relies on overloading writev() to trigger
    signing which just by the looks sounded dangerous and I hated it
    to the core. This change moves all that business to the setxattr
    interface thereby keeping the writev path strictly for client
    IO.
    
    Why not use IPC fop to trigger signing?
    There's a need to access the object's inode to perform various
    maintainance operations. inode is not _directly_ accessible in
    the IPC fop (although, it can be found via inode_grep() for the
    object's GFID - the inode just needs to be pinned in memory,
    which is the case if there's an active fd on the inode). This
    patch relies on good old technique of overloading fsetxattr()
    to do the job instead of using IPC fop.
    
    There are some pretty nice cleanups along the lines of memory
    deallocations, unncessary allocations and redundant ref()ing
    of structures (such as fd's) provided by this patch. All in
    all - much improved code navigation.
    
    Change-Id: Id93fe90b1618802d1a95a5072517dac342b96cb8
    BUG: 1224600
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10942
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bc858473db1e1091b15d3f3d69ac6ba5d20b58e7
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon May 18 17:37:14 2015 +0530

    libgfapi: introduce bit flags for pthread mutex and cond variables
    
    At present stage, the initialization and destroy of conditional
    and mutex variables of glfs struct happen in different places and
    there is no uniform way of destroying these variables incase
    there is a failure when initializing these. The fs mutex and
    conditional variables are getting destroyed from glfs_free_from_ctx().
    However this destroy is not done by a conditional check inside destroy
    function. By introducing bit flags in glfs object, we can make use of the
    same (if there is a failure in initialization) in glfs_fini()
    which is evolving as one and only function to free fs and ctx resources.
    This patch introduce the flags field and set the flags according
    to the initialization flow of the mutex and conditional variables
    of struct glfs members. Without this patch we are compelled to use
    the goto lables and other hacks in init functions to make sure
    the resources are freed if there is an error path.
    
    Change-Id: I86e2719fb7ce437419a05699b4f06c14b02d0e69
    BUG: 1208482
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/10120
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit bc33fe3c1621612788cf2f7928178f314a5f25f1
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu May 21 21:30:54 2015 +0530

    spec: correct the vendor string in spec file
    
    Change-Id: Id19c973092af506582741887d12fe00c85022f15
    BUG: 1198849
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10885
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6678b760e26567aa248d60f69d8f177690cc7071
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat May 23 19:41:56 2015 +0200

    build: do not include rpcgen generated files in "make dist"
    
    The .c and .h files are generated by rpcgen, there is no need to include
    them in the "make dist" tarball.
    
    BUG: 1198849
    Change-Id: Ie6281720e4d485d2b84d98efccfc7053594d1542
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10897
    Tested-by: NetBSD Build System
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 38a5cd8c136640d23288aca0afe19a82e1b320f8
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 20 09:10:38 2015 -0400

    glusterfs.spec.in: move libgf{db,changelog}.pc from -api-devel to -devel
    
    pkgconfig files in the wrong package results in unexpected package
    dependencies
    
    Change-Id: I0551114d09bcc3a7a73e152275175ba6c1bc0da3
    BUG: 1223385
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10843
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4df3ea9ab4d8a1aff98784460983b5f0cb4a9ee9
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 13 19:56:47 2015 +0530

    cluster/dht: Don't rely on linkto xattr to find destination subvol during phase 2 of migration.
    
    linkto xattr on source file cannot be relied to find where the data
    file currently resides. This can happen if there are multiple
    migrations before phase 2 detection by a client. For eg.,
    
    * migration (M1, node1, node2) starts.
    * application writes some data. DHT correctly stores the state in
      inode context that phase-1 of migration is in progress
    * migration M1 completes
    * migration (M2, node2, node3) is triggered and completed
    * application resumes writes to the file. DHT identifies it as phase-2
      of migration. However, linkto xattr on node1 points to node2, but
      the file is on node3. A lookup correctly identifies node3 as cached
      subvol
    
    TBD:
       When we identify phase-2 of a previous migration (say M1), there
       might be a migration in progress - say (M3, node3, node4). In this
       case we need to send writes to both (node3, node4) not just
       node3. Also, the inode state needs to correctly indicate that its in
       phase-1 of migration. I'll send this as a different patch.
    
    Change-Id: I1a861f766258170af2f6c0935468edb6be687b95
    BUG: 1142423
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/10805
    Tested-by: NetBSD Build System

commit 49b428433a03fcf709fdc8c08603b4cf02198e0a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu May 14 03:21:10 2015 +0530

    afr: allow readdir to proceed for directories in split-brain
    
    Problem:
    afr_read_txn() bails out if read_subvol==-1. This meant that for
    directories that were in entry split-brain, FOPS like readdir, access,
    stat etc were not allowed.
    
    Fix:
    Except for getxattr, all other FOPS are wound on the first up child
    of afr.
    
    Change-Id: Iacec8fbb1e75c4d2094baa304f62331c81a6f670
    BUG: 1221481
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10776
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Tested-by: NetBSD Build System

commit 47c604c2d2ccd8fb62c1ad155f63545b87ada851
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu May 21 17:47:33 2015 +0200

    fuse: squash 64-bit inodes in readdirp when enable-ino32 is set
    
    The structures returned by readdirp contain the inode 2x. Only one of
    them was squashed into 32-bits when enable-ino32 is enabled.
    
    Change-Id: I33a6d28fb118bb23971f918ffeb983d7f033106e
    BUG: 1223889
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Cyril Peponnet <cyril@peponnet.fr> [on release-3.5]
    Reviewed-on: http://review.gluster.org/10881
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit ae9604bbdb4f87ee3f6f11adc3ce6cd140620055
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Thu May 14 14:37:25 2015 +0530

    gfapi: zero size issue in glfs_h_acl_set()
    
    When setting the stringified ACLs in the xattr dict through
    pub_glfs_h_setxattrs(), the size of the string is always passed as 0.
    The correct way is to pass the length of the ACL in text form.
    
    While verifying this issues, it seems that posix_pacl_set() should
    return the errno instead of -1. This helps in debugging, otherwise EPERM
    would always be returned on an error.
    
    [ndevos: fix off-by-one strlen() and return errno in posix_pacl_set()]
    Change-Id: Ia7a7fa1f3a7d615a813c703057dc97b09a0bbb34
    BUG: 789278
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10782
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8461bf0b5008a3ddcc7b675caa9aa7c3d6473048
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue May 19 14:48:01 2015 +0530

    glusterd: fix repeated connection to nfssvc failed msgs
    
    ... and disable reconnect timer on rpc_clnt_disconnect.
    
    Root Cause
    ----------
    
    gluster-NFS service wouldn't be started if there are no
    started volumes that have nfs service enabled for them.
    Before this fix we would initiate a connect even when
    the gluster-NFS service wasn't (re)started. Compounding
    that glusterd_conn_disconnect doesn't disable reconnect
    timer. So, it is possible that the reconnect timer was
    in execution when  the timer event was attempted to be
    removed.
    
    Change-Id: Iadcb5cff9eafefa95eaf3a1a9413eeb682d3aaac
    BUG: 1222378
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/10830
    Tested-by: NetBSD Build System
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 37f365843bed87728048da1f56de22290f5cb70f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed May 20 14:33:41 2015 +0530

    glusterd : allocate peerid to store in frame->cookie
    
    commit a1de3b05 was using peerid from the stack and storing it in the
    frame->cookie and in the subsequent callback it was referred. The existance of
    this variable is not guranteed in the cbk since its not dynamically allocated.
    Fix is to dynmacially manage peerid in the frame cookie.
    
    This patch also fixes one problem in gd_sync_task_begin () where unlock is not
    triggered if the cluster is running with lesser than 3.6 op-version resulting into
    commands failing with another transaction is in progress.
    
    Change-Id: I0d22cf663df53ef3769585703944577461061312
    BUG: 1223213
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10842
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 58a687a8e0967393428bc5f93f0d32bbc3792f88
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 13 11:44:49 2015 +0200

    features/shard: Skip block count and size update for directories
    
    Change-Id: Iaa7022c95a8d9c9c471db025ec644e0bcc4eeb29
    BUG: 1221104
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10772
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f92a415dd4fdd34c97fa6af4af528e1b50a4265f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 13 14:25:44 2015 +0200

    protocol/client,server: Move EEXIST logs in mkdir and mknod to DEBUG level
    
    Change-Id: I0481258de8da36cbee7c046f53b20359badaf064
    BUG: 1221889
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10791
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9e1bb640983f72858aeabd793bbb7fc8b5c71b09
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 27 19:03:12 2015 +0530

    cluster/afr: Treat op_ret >= 0 as success in afr_final_errno()
    
    Change-Id: I7ec29428b7f7ef249014f948a5d616bfb8aaf80d
    BUG: 1225491
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10946
    Tested-by: NetBSD Build System
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9a96489e21702bbe7146c9cf6da672917e88864c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed May 27 16:40:52 2015 +0530

    tests: Remove tests from bad tests
    
    All known ec eio issues we know are solved with
    http://review.gluster.com/10852
    So removing these ec tests from bad tests:
    ./tests/basic/ec/ec-5-1.t
    ./tests/basic/ec/ec.t
    
    Removing the following tests because they are one-off failures and the
    logs do not show anything significant.
    ./tests/bugs/replicate/bug-1015990.t
    ./tests/bugs/glusterfs/bug-867253.t
    ./tests/basic/afr/sparse-file-self-heal.t
    
    Removing the following tests as they are fixed by 10918:
    ./tests/basic/ec/quota.t
    ./tests/basic/quota-nfs.t
    ./tests/bugs/quota/bug-1035576.t
    
    BUG: 1165041
    Change-Id: Ie3701d376ef383375f3e9853df26baa617628cdd
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10930
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f7bc35358c27d6260d5d1c4e22f1708d7ab60a98
Author: vmallika <vmallika@redhat.com>
Date:   Wed May 27 16:25:27 2015 +0530

    quota: fix for spurious failure
    
    During ancestry build, loc path was set to invalid
    path. path was set to one of its child instead
    of itself. Because of this quota accounting was
    going wrong
    
    This patch fix the issue
    
    Below mentioned tests removed from bad test list
    as part of patch# 10930
            ./tests/basic/ec/quota.t
            ./tests/basic/quota-nfs.t
            ./tests/bugs/quota/bug-1035576.t
    
    Change-Id: Iaa65b2d968c04c9abcd476d0e9f588cb7fd39294
    BUG: 1223798
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10918
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b7fde604e7fd42e6fc803bf7adfe66b5f441b8bb
Author: Deepak C Shetty <deepakcs@redhat.com>
Date:   Tue May 26 14:33:19 2015 +0530

    tests: Fix typo in ssl-authz.t
    
    Fixes a typo that was incorrectly causing the ssl cipher
    list not to be set properly on the test volume.
    
    Change-Id: I7969988551aa0c76261e41ab2f6247b684dacd49
    Signed-off-by: Deepak C Shetty <deepakcs@redhat.com>
    Reviewed-on: http://review.gluster.org/10914
    Tested-by: NetBSD Build System
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0f55ed9bfdfb6856f5914f99d4e2e2a2dc97f73e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue May 26 15:10:25 2015 +0530

    tests/uss.t: wait for connection to complete before accessing a file in snapshot
    
    Change-Id: I82d0cb378d006777d5a304afe8d5be15e92c7245
    BUG: 1163543
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/10915
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d6fc353afce03095c98d67d377eb7ddf334fd42e
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 27 12:08:54 2015 +0530

    meta: implement fsync(dir)
    
    Change-Id: I707c608a9803fe6ef86860ca5578d4d3f63fd2aa
    BUG: 1225323
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/10929
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 628198deaf0bc3192607a01ccfaa7a605723fa4d
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu May 21 11:17:59 2015 +0530

    tier/tier.t: Fixing tier.t crash in regression runs
    
    1) If the database file exists
       a. Dont try re-creating the db schema
       b. Dont try re-configuring the db.
    
    2) Dont assert in fini_db () when connection is NULL
    
    Change-Id: I15dd103fe7542f70113c1d5e539a99f8cd062be4
    BUG: 1163543
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10870
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3b666b40efbed157e8c5991f29b345d93b28c659
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed May 20 15:17:35 2015 +0200

    cluster/ec: Forced unlock when lock contention is detected
    
    EC uses an eager lock mechanism to optimize multiple read/write
    requests on the same entry or inode. This increases performance
    but can have adverse results when other clients try to access the
    same entry/inode.
    
    To solve this, this patch adds a functionality to detect when this
    happens and force an earlier release to not block other clients.
    
    The method consists on requesting GF_GLUSTERFS_INODELK_COUNT and
    GF_GLUSTERFS_ENTRYLK_COUNT for all fops that take a lock. When this
    count is greater than one, the lock is marked to be released. All
    fops already waiting for this lock will be executed normally before
    releasing the lock, but new requests that also require it will be
    blocked and restarted after the lock has been released and reacquired
    again.
    
    Another problem was that some operations did correctly lock the
    parent of an entry when needed, but got the size and version xattrs
    from the entry instead of the parent.
    
    This patch solves this problem by binding all queries of size and
    version to each lock and replacing all entrylk calls by inodelk ones
    to remove concurrent updates on directory metadata.  This also allows
    rename to correctly update source and destination directories.
    
    Change-Id: I2df0b22bc6f407d49f3cbf0733b0720015bacfbd
    BUG: 1165041
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/10852
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 5513144feb5b062b733d7514adf194429e31666f
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu May 21 18:45:12 2015 +0200

    posix: Do not update unmodified xattr in (f)xattrop
    
    If a (f)xattrop is issued with a value that only contains 0's,
    then we don't modify or create the extended attribute. This
    is useful to avoid ctime modifications when the only purpose
    of the xattrop was to get the current value.
    
    Change-Id: Ia62494e9009962e683c8276783f671da17a8b03a
    BUG: 1211123
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/10886
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d37cb5aee7af8582d0343d2732c153226955945d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 19 20:53:30 2015 +0530

    features/locks: Handle virtual getxattrs in more fops
    
    With this patch getxattr of inodelk/entrylk counts can be requested in
    readv/writev/create/unlink/opendir.
    
    Change-Id: If7430317ad478a3c753eb33bdf89046cb001a904
    BUG: 1165041
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10880
    Tested-by: NetBSD Build System
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit d1ff9dead1f26151f89d154fab8252437601d22f
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri May 22 18:38:23 2015 +0530

    glusterd: Fix conf->generation to stop new peers participating in
    a transaction, while the transaction is in progress.
    
    Every peer gets a generation number, during it's inception.
    This generation number is used to identify the peer throiughout
    it's lifetime. This number is assigned based on the current
    generation number of the system, which is incremented with every
    peer that is added.
    
    The problem arises when we add a peer, and before it gets a rpc_connect
    we begin a transaction. In such a case, the peer gets considered in the
    transaction, but doesn't participate in it coz it isn't connected yet.
    The moment it gets the rpc notification and is connected, it starts
    participating in the transaction and all hell breaks loose.
    
    To resolve it, we should assign the peerinfo a new generation number
    everytime it's connected, so that this number will be greater than the
    generation number that the transaction is acting upon, and even though
    the peer is connected it will not participate in the transaction.
    
    We should also assign the new generation number of the peer to the peerctx,
    so that the framework that searches for peerinfos based on the generation
    number, will still function in the same manner.
    
    Removing ./tests/basic/volume-snapshot-clone.t from bad-tests.
    Also removed the duplicate entry of ./tests/bugs/snapshot/bug-1112559.t
    from bad-tests. Original entry was removed in
    http://review.gluster.org/10840
    
    Change-Id: Ie25e3ecf59b19535b9cded7449e944221fac97a0
    BUG: 1224290
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10895
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 158b047f7949d4fd1682fcb8f0722ddb28785bfa
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon May 25 16:42:50 2015 +0530

    tests: Fix entry-self-heal.t
    
    Because both bricks in the replica pair of patchy are in the same node,
    both full healer threads within the same shd try and fail to acquire
    non-blocking locks when each one gets lock on one of the bricks,
    causing heal to fail occasionally.
    
    Now heals are triggered from the mount as part of inode refresh.
    And because the AFR on the mount graph
    a. does not treat presence of dirty xattrs as something that needs
       a heal (this is true for dirs fool_heal and fool_me) and
    b. does not recursively heal the entire hierarchy of subdirs and their
       entries in one shot (this is true with source_creations_heal/dir1),
    
    index heal is used to heal fool_heal, fool_me and
    source_creations_heal/dir1 wherein only one brick (which is the brick that
    contains the good copy of source_creations_heal/dir_1: brick-1) has all
    the gfids to be healed copied into its indices/xattrop directory.
    
    Change-Id: I46df4188f16d1623f20cc0d7266b3afaeca6c31f
    BUG: 1163543
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10916
    Tested-by: NetBSD Build System
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f59a1431e38ad644b6bdd4adbdf94ff028c9c60d
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed May 20 18:23:58 2015 +0530

    glusterd: fix double-free of rebalance process' rpc object
    
    Change-Id: I0c79c4de47a160b1ecf3a8994eedc02e3f5002a9
    BUG: 1223338
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/10872
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 30c97ce5c9ba03760bdab7c82208065da631efe9
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue May 26 15:36:52 2015 +0530

    tests: remove read-subvol-entry.t from is_bad_test
    
    Change-Id: I81750655d5686709908563e68f40821140397050
    BUG: 1163543
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10917
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cff7e29ebdc369b877319f5643c1d6fa1df4f60a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue May 26 10:40:49 2015 +0530

    tests: add ec/ec.t to is_bad_test
    
    ... to avoid ec.t's spurious regression test failure coming in the way
    of fixes for other independent spurious regression test failures.
    
    Change-Id: Id393be571685ca1e69732c1149c370b6fd0e6d17
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/10907
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 225ff553106396066d68d8c757e5c001f5d9ab15
Author: vmallika <vmallika@redhat.com>
Date:   Mon May 25 13:35:48 2015 +0530

    Quota: fix testcases not to send parallel writes for accurate
    quota enforcement
    
    Currently quota enforcer doesn't consider parallel writes
    and allows quota to exceed limit where there are high rate
    of parallel writes. Bug# 1223658 tracks the issue.
    
    This patch fixes the spurious failures by not sending
    parallel writes.
    Using O_SYNC and O_APPEND flags and block size
    not more that 256k (For higher block size NFS client
    splits the block into 256k chinks and does parallel writes)
    
    Change-Id: I297c164b030cecb87ce5b494c02b09e8b073b276
    BUG: 1223798
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10878
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit b51ee5f8d1f80d66effffc06c1e49099c04014a4
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue May 19 23:09:42 2015 +0530

    tests: arbiter.t fix
    
    Wait for AFR's children to be up in glustershd process before attempting heal.
    
    Also, grep (version 2.21) is detecting statedump files as binary, causing tests
    to succeed incorrectly. Hence adding the -a switch to force it to treat it as a
    text file. Thanks to Vijay Bellur for identifying the issue
    (http://lists.gnu.org/archive/html/bug-grep/2015-05/msg00000.html) and the
    workaround.
    
    Change-Id: Ie3d9591ffaf44baa0cd8c2baa327aed24378e3df
    BUG: 1163543
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10833
    Tested-by: NetBSD Build System
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit dbad74f1e739c6d1f48b8af392c1eee1a7254015
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu May 21 15:43:35 2015 +0530

    tests: data-self-heal.t fix
    
    Use Index heal instead of full heal to heal files because if both bricks are on
    the same node, the 2 full heal threads might compete and fail to acquire the non
    blocking locks and the file might not get healed during the full heal crawl.
    
    Change-Id: I3b9e2de7b0366b4bc40b54314807ef165baad68f
    BUG: 1163543
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10875
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 173c7b542939b95a72f30ba2ce1342af62b73f37
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri May 22 10:08:37 2015 +0530

    tests: add more tests to bad_test for the interim
    
    Change-Id: Icd92f1b999c8cda310053306c63a7445146a55db
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/10888
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 0910bab5e5b957e11f356d525eccccfd36d334f9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 20 23:56:17 2015 +0530

    cluster/ec: Fix use after free crash
    
    ec_heal creates ec_fop_data but doesn't run ec_manager. ec_fop_data_allocate
    adds this fop to ec->pending_fops, because ec_manager is not run on this heal
    fop it is never removed from ec->pending_fops. When it is accessed after free
    it leads to crash. It is better to not to add HEAL fops to ec->pending_fops
    because we don't want graph switch to hang the mount because of a BIG
    file/directory heal.
    
    BUG: 1188145
    Change-Id: I8abdc92f06e0563192300ca4abca3909efcca9c3
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10868
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit a61c788de737f81b9c21b176a26e21a078176ed9
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed May 20 17:49:25 2015 +0530

    tests: Removing tests/bugs/snapshot/bug-1112559.t from test-suite
    
    The fix that introduced this test has been reverted as part of design change.
    Hence removing it from the test-suite
    
    Change-Id: I7acaf387ec3035f736498a437c736fe70970d421
    BUG: 1219738
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10840
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 988db25572b94220a7cc69bcc3040c2a77b8e9a5
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri May 8 09:53:50 2015 +0530

    glusterd: populate errstr if gd_syncop_submit_request fails
    
    Change-Id: Ie4a3edef5d553fc07de53b46f9485c46a4305245
    BUG: 1219732
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10659
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 61cfcf65f0d4ad70fc8a47395c583d4b5bf1efbe
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu May 14 20:07:10 2015 +0200

    cluster/ec: Correctly cleanup delayed locks
    
    When a delayed lock is pending, a graph switch doesn't correctly
    terminate it. This means that the update of version and size xattrs
    is lost, causing EIO errors.
    
    This patch handles GF_EVENT_PARENT_DOWN event to correctly finish
    pending udpdates before completing the graph switch.
    
    Change-Id: I394f3b8d41df8d83cdd36636aeb62330f30a66d5
    BUG: 1188145
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/10787
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8f788528e64c4c13e16f7ad2d9f667a3813e08cc
Author: zhoushicheng <madaozhou@gmail.com>
Date:   Fri Apr 10 12:10:26 2015 +0800

    test: Fix sparse file self heal test
    
    This patch solves problems caused by XFS with speculative preallocation feature on :
    Test EXPECT "1" has_holes $B0/${V0}0/big2bigger would fall when XFS has not freed the preallocated blocks.
    It is caused by XFS speculative preallocation feature. The test would pass if this feature is disabled.
    Speculative preallocation can speed up under linux 3.8(and later).
    Otherwise, the test would pass by dropping cache manually to speed up speculative preallocation.
    
    As in http://review.gluster.org/#/c/10411/, using "( cd $M0 ; umount $M0 )" to drop caches, which is
    better than "echo 3 > /proc/sys/vm/drop_caches".
    
    drop caches operation was added in test:
    tests/basic/afr/sparse-file-self-heal.t
    
    BUG: 1206461
    Change-Id: Ie2c9d1b92fa8307c44498752fdd100eb86f9689c
    Signed-off-by: zhoushicheng <madaozhou@gmail.com>
    Reviewed-on: http://review.gluster.org/10253
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 64d2a5a25b64601958c0f47ec2e6356226f97d4b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 18 14:46:55 2015 +0530

    cluster/ec: Handle lookup failures while op in progress
    
    Change-Id: Ia1834ec23d5de615526d4d4e4d2e32aff155b7f7
    BUG: 1211962
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10806
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 6cbbe121e8d14342a17f38fb9f616a396550fb63
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue May 19 10:01:05 2015 +0530

    tests: Remove bug-976800.t from is_bad_test()
    
    commit d4d9cfc82d7cf77972 has already fixed this test.
    
    Change-Id: I7ecef580af6c7a3b3b786ab583705123475afcb6
    BUG: 1220058
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10813
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ae92b7bba3f5200076cf0a94b5252f0a2672d2a6
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Tue May 19 01:09:05 2015 +0530

    move trash doc to features sub directory
    
    Change-Id: I3ca9a0c8fddc7af516aaf5a6d4a880fb24e3c058
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10810
    Tested-by: NetBSD Build System
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>

commit 7e29c04d278dea6f0fc5ad8e316f9822c61ced03
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun May 10 11:57:15 2015 +0530

    tests: data-self-heal.t-create files from the mount point.
    
    Currently data-self-heal.t creates files directly on the brick and sets
    the trusted.gfid xattr. Later it depends on stat from mount to create
    the .glusterfs/<gfid hard link>. The link creation doesn't seem to be
    happening always. Hence changing the test to create files from the mount
    point before modifying afr xattrs in the backend and triggering heal.
    
    Also disabled all performance translators. With these changes,
    http://review.gluster.org/#/c/10667/ is not failing in data-self-heal.t
    
    Change-Id: I7d054e52b97aeb0bdc2fdf9d70a8cf33318d4310
    BUG: 1218304
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10530
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit b7a72375353d583928d971b64eb9f0674904ba76
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon May 11 03:32:20 2015 +0200

    Tests: avoid hang in br-stub.t
    
    br-stub.t forgot to unmount the NFS mount, leading to the situation
    where cleanup code had to do it after glusterfs daemon were shut
    down. NetBSD has trouble dealing with this situation and may enter
    endless wait for the NFS server to come back.
    
    Fix is simply to unmount before the end og the script
    
    BUG: 1129939
    Change-Id: I972d379172a75f29ad11abc66d700c2d31106194
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10748
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit cfca748fef28170377b868871b0dd980c1f151f6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat May 16 17:57:37 2015 +0200

    tests: write log for glupy.t to the standard log directory
    
    There is (or was) a spurious test in glupy.t for which a separate log
    file was setup. The directory where the log is saved, is not available
    on NetBSD and this causes glupy.t to always fail, without a log.
    
    Instead of hard-coding the path to the log, use "gluster --print-logdir"
    to provide a LOGDIR environment variable. glupy.t now writes the log to
    an existing directory.
    
    BUG: 1163543
    Change-Id: Ifa73198d06fa267856d0da9d25a4380329909124
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10801
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit df12f00851a234b0e892af4b958e606a1fa660ed
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed May 13 11:41:31 2015 +0200

    nfs: Use uuid_clear() instead of memset
    
    Fixes the following incorrect usage:
    
    mount3.c: In function '__mnt3_build_mountid_from_path':
    mount3.c:705:24: warning: 'sizeof' on array function parameter 'mountid' will
    return size of 'unsigned char *' [-Wsizeof-array-argument]
             length = sizeof(mountid);
                            ^
    mount3.c:699:58: note: declared here
     __mnt3_build_mountid_from_path (const char *path, uuid_t mountid)
                                                              ^
    mount3.c: In function '__mnt3_get_mount_id':
    mount3.c:732:24: warning: 'sizeof' on array function parameter 'mountid' will
    return size of 'unsigned char *' [-Wsizeof-array-argument]
             length = sizeof(mountid);
                            ^
    mount3.c:726:46: note: declared here
     __mnt3_get_mount_id (xlator_t *mntxl, uuid_t mountid)
    
    Change-Id: I08f46c5994578fc99a7b61681e808d1115e41d71
    BUG: 1221095
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10765
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 628406f28364f6019261a3bb37335a494ccf8dda
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Fri May 15 14:16:00 2015 -0400

    cluster/tier: load libgfdb.so properly in all cases
    
    We should load libgfdb.so.0, not libgfdb.so
    
    Change-Id: I7a0d64018ccd9893b1685de391e99b5392bd1879
    BUG: 1222092
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10796
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Joseph Fernandes
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b5ceb1a9de9af563b0f91e2a3138fa5a95cad9f6
Author: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Date:   Thu May 14 12:10:01 2015 +0530

    fuse: fix return value check for setuid
    
    setuid() sets the effective user ID of the calling process. If the
    effective UID of the caller is root, the real UID and saved set-user-ID
    are also set. On success, zero is returned.  On error, -1 is returned,
    and errno is set appropriately.
    
    there are cases where setuid() can fail even when the caller is UID 0;
    it is a grave security error to omit checking for a failure return from
    setuid(). if an environment limits the number of processes a user can
    have, setuid() might fail if the target uid already is at the limit.
    
    Fix is to check return value of setuid.
    
    Change-Id: I7aa5ab5e347603c69dc93188417cc4f4c81ffc75
    BUG: 1221490
    Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
    Reviewed-on: http://review.gluster.org/10780
    Reviewed-by: Prasanna Kumar Kalever
    Tested-by: Prasanna Kumar Kalever
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>

commit 503acdb32ca84102d07cd1142eff464152b06690
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 13 16:57:49 2015 +0530

    cluster/ec: Prevent unnecessary self-heals
    
    When a blocking lock is requested, lock request is succeeded even when
    ec->fragment number of locks are acquired successfully in non-blocking locking
    phase. This will lead to fop succeeding only on the bricks where the locks are
    acquired, leading to the necessity of self-heals. To prevent these un-necessary
    self-heals, if the remaining locks fail with EAGAIN in non-blocking lock phase
    try blocking locking phase instead.
    
    Change-Id: I940969e39acc620ccde2a876546cea77f7e130b6
    BUG: 1221145
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10770
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 1cabc769c7b636f89f6f28aaa0d534401a82d4a8
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Thu May 14 19:33:44 2015 +0530

    dht/rebalance : Fixed rebalance failure
    
    The rebalance process determines the local subvols for the
    node it is running on and only acts on files in those subvols.
    If a dist-rep or dist-disperse volume is created on 2 nodes by
    dividing the bricks equally across the nodes, one process might
    determine it has no local_subvols.
    
    When trying to update the commit hash, the function attempts to
    lock all local subvols. On the node with no local_subvols the dht
    inode lock operation fails, in turn causing the rebalance to fail.
    
    In a dist-rep volume with 2 nodes, if brick 0 of each replica
    set is on node1 and brick 1 is on node2, node2 will find that it has
    no local subvols.
    
    Change-Id: I7d73b5b4bf1c822eae6df2e6f79bd6a1606f4d1c
    BUG: 1221696
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/10786
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1d110ec14384292fff67b88150529a513b729c5c
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Thu Apr 23 13:23:55 2015 +0530

    dht : null dereference coverity fix.
    
    CID : 1124521
    
    Change-Id: Ie524935d636195cb6894074095b9b98fe28dbc2c
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/10348
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sakshi Bansal
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit c56c3566feb9bed18fdec42e8e704ea185dce910
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed May 13 15:21:29 2015 +0530

    quota/glusterd: on read call number of byte read should equal to buffer length
    
    glusterd is crashing when user try to set limit-usage on quota. Because
    in the read call number of byte is going to be read is more then buffer
    lenght.
    
    Change-Id: Ie507eb68ebc0d0daa1012baef1bf724e202e3baa
    BUG: 1221025
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10766
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5e61673d6ebedaf5f9a4c9d1cb64f9df8e11db91
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Wed May 13 04:49:15 2015 +0530

    NFS-Ganesha : Disable ACL by default
    
    ACLs need to be disabled by default.
    To enable ACLs, the user has to change the
    export file manually, set Disable_ACL=False
    and run ganesha-ha.sh --refresh-config.
    Changing the default export file to
    accommodate these changes.
    
    Change-Id: If3fe0f237344c594a43ad6fc5d351bd391ae5256
    BUG: 1221131
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/10769
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2b92a5c5efc29b05de88631bc5423ae3eec43812
Author: Anuradha <atalur@redhat.com>
Date:   Tue May 12 12:53:30 2015 +0530

    cluster/afr : Do not copy dict when it is NULL
    
    In afr_lookup_xattr_req_prepare(), dict_copy was
    done even though source dict was NULL.
    
    Change-Id: I85a5d2823ba021e7f78c1ce13402a0f16b08cb51
    BUG: 1220332
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10755
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ef37da74d4a8595cf53cf6dfe680fe080b7c8704
Author: Susant Palai <spalai@redhat.com>
Date:   Tue May 12 12:56:37 2015 +0530

    dht/rebalance: Change log_level to DEBUG
    
    Change-Id: I646367581d8ee8a9e5966ee302b19273a0c780ff
    BUG: 1220329
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/10756
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 38d5fb252a9e4ba5a58e0452c45b7649afcd7003
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Mon May 11 17:43:40 2015 +0530

    rpm: marker xlator should part of the server sub-package
    
    Currently marker translator is part of extra-xlator package. Installing
    only the glusterfs-server package and required dependencies does not
    make it possible to create a volume and starte it. Starting the volume
    will fail. The brick logs compain that type feature/marker is not valid:
    
        W [xlator.c:192:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.0beta1/xlator/features/marker.so: cannot open shared object file: No such file or directory
        E [graph.y:212:volume_type] 0-parser: Volume 'rvstore-marker', line 78: type 'features/marker' is not valid or not found on this machine
    
    Fix is to include the marker translator in the server package. It should
    not be part of extra-xlator package.
    
    Change-Id: I77fe8a0bcf7d6f1dbff62d663e840e9e45805614
    BUG: 1220381
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10752
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e32e5fcb0757cd5cc8bfa04f45bab410f6547feb
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Sat May 9 19:35:31 2015 +0530

    tests: Wait for NFS exports to be ready before mount
    
    Change-Id: Ie71e8c80d6a43dd618c9decb946a459b211295ce
    BUG: 1219846
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10724
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 32e5cdeaa5073437d396c1e7d39c0fe4cbe1ee87
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Apr 23 23:13:50 2015 +0530

    uss : implement statfs fop for snapd
    
    snapview-client and snapview-server doesnot have statfs
    fop implemented
    
    Change-Id: I2cdd4c5784414b0549a01af9a28dbc723b7cdc67
    BUG: 1176837
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10358
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4eaaf5188fe24a4707dc2cf2934525083cf8e64f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed May 7 19:31:30 2014 +0000

    dht: make lookup-unhashed=auto do something actually useful
    
    The key concept here is to determine whether a directory is "clean" by
    comparing its last-known-good topology to the current one for the
    volume.  These are stored as "commit hashes" on the directory and the
    volume root respectively.  The volume's commit hash changes whenever a
    brick is added or removed, and a fix-layout is done.  A directory's
    commit hash changes only when a full rebalance (not just fix-layout)
    is done on it.  If all bricks are present and have a directory
    commit hash that matches the volume commit hash, then we can assume
    that every file is in its "proper" place. Therefore, if we look for
    a file in that proper place and don't find it, we can assume it's not
    on any other subvolume and *safely* skip the global (broadcast to all)
    lookup.
    
    Change-Id: Id6ce4593ba1f7daffa74cfab591cb45960629ae3
    BUG: 1219637
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/7702
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4b7914384e2613e5ec7c618071cb89187ed6f870
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Apr 22 20:07:11 2015 +0530

    cli/tiering: volume info should display details about tier
    
    >> gluster volume info patchy
    
    Volume Name: patchy
    Type: Tier
    Volume ID: 8bf1a1ca-6417-484f-821f-18973a7502a8
    Status: Created
    Number of Bricks: 8
    Transport-type: tcp
    Hot Tier :
    Hot Tier Type : Replicate
    Number of Bricks: 1 x 2 = 2
    Brick1: hostname:/home/brick30
    Brick2: hostname:/home/brick31
    Cold Bricks:
    Cold Tier Type : Disperse
    Number of Bricks: 1 x (4 + 2) = 6
    Brick3: hostname:/home/brick20
    Brick4: hostname:/home/brick21
    Brick5: hostname:/home/brick23
    Brick6: hostname:/home/brick24
    Brick7: hostname:/home/brick25
    Brick8: hostname:/home/brick26
    
    Change-Id: I7b9025af81263ebecd641b4b6897b20db8b67195
    BUG: 1212400
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10339
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7c1415fa591172765ab1e7dc1b049bf162d53788
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed May 6 14:23:34 2015 +0530

    features/bitrot: scrubber should crawl based on the scrubber frequency value
    
    Currently scrubber is crawling all the files continuously. It should
    crawl files based on the scrubber frequency which user have set.
    
    By default scrubber crawling frequency value will be biweekly.
    
    Change-Id: I5762a92c1e700134cfe4283d1f631904adbfe31d
    BUG: 1208131
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10602
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1a27c2edd6d49118a73da2f30deccb4a91bebad2
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Fri May 8 16:36:00 2015 +0530

    CTR/Libgfdb: Log typo fix
    
    Log typo fix for CTR Xlator and Libgfdb
    
    Change-Id: I8d7208b9756199f8dc0a72771a3c953b4fa00f3f
    BUG: 1215896
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10668
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit ddc263e2998a89030a92c9e5ed7d58db81e12b96
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat May 9 21:05:02 2015 +0200

    glupy: remove debug test in libpython runtime search path detection
    
    A configure test was recently added to add libpython runtime search
    path to glupy.so xlator. The vesion committed was a debug test, it
    searched pythonxx and not python to check for failure.
    
    Fix by removing the xx debug test in python's name.
    
    BUG: 1129939
    Change-Id: I7b691be17fc2a2c812f68710869b1a9a85ced84c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10732
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 66f46ab1d119c9d3dda80b163801723761c7af9b
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Apr 22 11:17:08 2015 +0530

    cli/tiering: display hot tier, and cold tier separately
    
    cli commands display the brick information without a way
    to distinguish hot tier, and cold tier.
    
    This patch will change all the cli related output, without
    changing the corresponding xml output.
    
    This patch will change following things
    >> gluster volume info
    Volume Name: patchy
    Type: Tier
    Volume ID: 7745d367-811a-4fe9-a500-d04e7afa94bf
    Status: Created
    Number of Bricks: 3 x 2 = 6
    Transport-type: tcp
    Hot Bricks:
    Brick1: hostname:/home/brick21
    Brick2: hostname:/home/brick20
    Cold Bricks:
    Brick3: hostname:/home/brick19
    Brick4: hostname:/home/brick16
    Brick5: hostname:/home/brick17
    Brick6: hostname:/home/brick18
    
    >>gluster volume status
    
    Status of volume: patchy
    Gluster process                             TCP Port  RDMA Port  Online
    Pid
    ------------------------------------------------------------------------------
    Hot Bricks:
    Brick hostname:/home/brick21              49152     0          Y
    4690
    Brick hostname:/home/brick20              49153     0          Y
    4707
    Cold Bricks:
    Brick hostname:/home/brick19              49154     0          Y
    4724
    Brick hostname:/home/brick16              49155     0          Y
    4741
    Brick hostname:/home/brick17              49156     0          Y
    4758
    Brick hostname:/home/brick18              49157     0          Y
    4775
    NFS Server on localhost                     2049      0          Y
    4793
    
    Task Status of Volume patchy
    ------------------------------------------------------------------------------
    There are no active volume tasks
    
    >>gluster volume status pathy detail
    
    Status of volume: patchy
    Hot Bricks:
    ------------------------------------------------------------------------------
    Brick                : Brick hostname:/home/brick21
    TCP Port             : 49162
    RDMA Port            : 0
    Online               : Y
    Pid                  : 22677
    File System          : ext4
    Device               :
    /dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
    Mount Options        : rw,seclabel,relatime,data=ordered
    Inode Size           : 256
    Disk Space Free      : 127.3GB
    Total Disk Space     : 165.4GB
    Inode Count          : 11026432
    Free Inodes          : 10998043
    ------------------------------------------------------------------------------
    Brick                : Brick hostname:/home/brick20
    TCP Port             : 49161
    RDMA Port            : 0
    Online               : Y
    Pid                  : 22660
    File System          : ext4
    Device               :
    /dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
    Mount Options        : rw,seclabel,relatime,data=ordered
    Inode Size           : 256
    Disk Space Free      : 127.3GB
    Total Disk Space     : 165.4GB
    Inode Count          : 11026432
    Free Inodes          : 10998043
    Cold Bricks:
    ------------------------------------------------------------------------------
    Brick                : Brick hostname:/home/brick19
    TCP Port             : 49157
    RDMA Port            : 0
    Online               : Y
    Pid                  : 22501
    File System          : ext4
    Device               :
    /dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
    Mount Options        : rw,seclabel,relatime,data=ordered
    Inode Size           : 256
    Disk Space Free      : 127.3GB
    Total Disk Space     : 165.4GB
    Inode Count          : 11026432
    Free Inodes          : 10998043
    ------------------------------------------------------------------------------
    Brick                : Brick hostname:/home/brick16
    TCP Port             : 49158
    RDMA Port            : 0
    Online               : Y
    Pid                  : 22518
    File System          : ext4
    Device               :
    /dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
    Mount Options        : rw,seclabel,relatime,data=ordered
    Inode Size           : 256
    Disk Space Free      : 127.3GB
    Total Disk Space     : 165.4GB
    Inode Count          : 11026432
    Free Inodes          : 10998043
    ------------------------------------------------------------------------------
    Brick                : Brick hostname:/home/brick17
    TCP Port             : 49159
    RDMA Port            : 0
    Online               : Y
    Pid                  : 22535
    File System          : ext4
    Device               :
    /dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
    Mount Options        : rw,seclabel,relatime,data=ordered
    Inode Size           : 256
    Disk Space Free      : 127.3GB
    Total Disk Space     : 165.4GB
    Inode Count          : 11026432
    Free Inodes          : 10998043
    ------------------------------------------------------------------------------
    Brick                : Brick hostname:/home/brick18
    TCP Port             : 49160
    RDMA Port            : 0
    Online               : Y
    Pid                  : 22552
    File System          : ext4
    Device               :
    /dev/mapper/luks-cd077c56-42ba-44b1-8195-f214b9bc990c
    Mount Options        : rw,seclabel,relatime,data=ordered
    Inode Size           : 256
    Disk Space Free      : 127.3GB
    Total Disk Space     : 165.4GB
    Inode Count          : 11026432
    Free Inodes          : 10998043
    
    Change-Id: I7d584eb8782129c12876cce2ba8ffba6c0a620bd
    BUG: 1206546
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10328
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e8b50b8bcf2f08750885dead2f95448a5503b955
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Sun May 10 11:36:36 2015 +0530

    test: disable ec-3-1.t, ec-5-1.t, ec-12-4.t bad test cases
    
    These tests are frequently failing regressions now.
    
    Change-Id: I9dd51eb124e1cbabc52d7b083f0bbed55526b57e
    BUG: 1220058
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10743
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 3586581c6edf222daf836c99ce2a1a266dc741f8
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Fri May 8 13:08:22 2015 +0530

    bitrot: Volfile generation should not proceed if node doesn't have any brick.
    
    glusterd crashes when bitrot is enabled on a distributed volume from a node
    which doesn't host a brick.
    
    While generating volfile glusterd should check number of brick on that node. If
    node doesn't have any brick then graph generation for bitrot and scrubber should
    not proceed further.
    
    Change-Id: I2158113e20e93738cde2a22fd73f0ae6b22aae9e
    BUG: 1219784
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10664
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit deb76ef2a97ea51c0cbe329a1fdb636071fda90f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Sat May 9 10:03:42 2015 +0530

    geo-rep: Update Not Started to Created in code and doc
    
    "Not Started" status is now "Created", replaced "Not Started"
    string in code and doc.
    
    Change-Id: If7d606c2cc8156e41291e7eebe9d0da4ad7ac28d
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1219937
    Reviewed-on: http://review.gluster.org/10698
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit b46e65db722c14985db62a1679e0388d217b713b
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Jan 7 12:29:48 2015 +0100

    ec: Fix failures with missing files
    
    When a file does not exist on a brick but it does on others, there
    could be problems trying to access it because there was some loc_t
    structures with null 'pargfid' but 'name' was set. This forced
    inode resolution based on <pargfid>/name instead of <gfid> which
    would be the correct one. To solve this problem, 'name' is always
    set to NULL when 'pargfid' is not present.
    
    Another problem was caused by an incorrect management of errors
    while doing incremental locking. The only allowed error during an
    incremental locking was ENOTCONN, but missing files on a brick can
    be returned as ESTALE. This caused an EIO on the operation.
    
    This patch doesn't care of errors during an incremental locking. At
    the end of the operation it will check if there are enough successfully
    locked bricks to continue or not.
    
    Change-Id: I9360ebf8d819d219cea2d173c09bd37679a6f15a
    BUG: 1176062
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9407
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 73b61d709712692b48a1c9b18b4547410fb9078c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat May 9 19:56:07 2015 +0200

    gfapi: fix compile warning in pub_glfs_h_access()
    
    While compiling libgfapi, the following warning is reported:
    
        Making all in src
          CC       libgfapi_la-glfs-handleops.lo
        In file included from glfs-handleops.c:12:0:
        glfs-handleops.c: In function 'pub_glfs_h_access':
        glfs-internal.h:216:14: warning: 'old_THIS' may be used uninitialized in this function [-Wmaybe-uninitialized]
                 THIS = old_THIS;                                            \
                      ^
        glfs-internal.h:202:36: note: 'old_THIS' was declared here
         #define DECLARE_OLD_THIS xlator_t *old_THIS = NULL
                                            ^
        glfs-handleops.c:1159:2: note: in expansion of macro 'DECLARE_OLD_THIS'
          DECLARE_OLD_THIS;
          ^
          CCLD     libgfapi.la
          CCLD     api.la
    
    The DECLARE_OLD_THIS macro should be done with the declarations of all
    the other variables used in this function. Moving the macro further up
    in the function prevents this warning.
    
    Change-Id: I2bedc1aa074893ae3e2c933abc5a167ab5b55f41
    BUG: 1210934
    Reported-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10728
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a591ba8ce34a8865abe4262dc61e3e53c609a645
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Apr 27 17:18:36 2015 +0530

    glusterd/tiering : cksum mismatch for tiered volume
    
    Once we updated the volinfo from orginator node, the hot
    type was overwritten with volume type.
    
    Then the same dictionary was sent to peer node to perform
    the commit of attach-tier, that will cause hot type to
    replace with volume type, eventually end up in cksum
    mismatch
    
    Change-Id: I402dceb4d672d0b3a7b91a92f52c1057050dbedc
    BUG: 1215660
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Conflicts:
    	xlators/mgmt/glusterd/src/glusterd-brick-ops.c
    Reviewed-on: http://review.gluster.org/10406
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 14f93bce381f0ae077829efc9ccf0831110126b2
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat May 9 21:23:56 2015 +0530

    Disable all bad tests
    
    Change-Id: Ib70330f6b635af563044346fe525e6555c83d0d2
    BUG: 1220058
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10725
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit c085871e3919df2b309b76633e75d5449899437a
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Apr 28 04:40:00 2015 -0400

    core: use reference counting for mem_acct structures
    
    When freeing memory, our memory-accounting code expects to be able to
    dereference from the (previously) allocated block to its owning
    translator.  However, as we have already found once in option
    validation and twice in logging, that translator might itself have
    been freed and the dereference attempt causes on of our daemons to
    crash with SIGSEGV.  This patch attempts to fix that as follows:
    
     * We no longer embed a struct mem_acct directly in a struct xlator,
       but instead allocate it separately.
    
     * Allocated memory blocks now contain a pointer to the mem_acct
       instead of the xlator.
    
     * The mem_acct structure contains a reference count, manipulated in
       both the normal and translator allocate/free code using atomic
       increments and decrements.
    
     * Because it's now a separate structure, we can defer freeing the
       mem_acct until its reference count reaches zero (either way).
    
     * Some unit tests were disabled, because they embedded their own
       copies of the implementation for what they were supposedly testing.
       Life's too short to spend time fixing tests that seem designed to
       impede progress by requiring a certain implementation as well as
       behavior.
    
    Change-Id: Id929b11387927136f78626901729296b6c0d0fd7
    BUG: 1211749
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10417
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 4a15d32643fe149764239eabcf6ba53eb32faf63
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Sat May 9 15:38:51 2015 +0530

    tests: fix bitrot spurious failures
    
    Change-Id: I342b7f8ec9c37cfd8d4cbd4090319330345bed4c
    BUG: 1220016
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10707
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 988e00f83cb74c908471caf6af9cbce05b7f95c9
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat May 9 12:23:10 2015 +0530

    tests: fix bitrot spurious failures
    
    Change-Id: I55bd62480b7ee38cf7b29aeba67b19b0c5bbe2fb
    BUG: 1220016
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10702
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 5faf4801bd6839cec58324a45dec31f977992236
Author: anand <anekkunt@redhat.com>
Date:   Thu May 7 12:23:25 2015 +0530

    glusterd: Invoking daemon reconfigure functions correctly
    
    Problem : Scrub and bitd reconfigure functions were not invoking if
    quota is not enabled.
    
    Reason : In glusterd_svcs_reconfigure, if quota is not enabled then
    it is returning in the middle of the function without calling bitd
    and scrub reconfigure functions.
    
    Fix : If quota is not enable on volume, skip quota reconfigure and
    continue for other daemon reconfigure.
    
    This patch also address the state dump issue for bitd and quotad
    (logs the scrub and bitd info into state dump).
    
    Change-Id: I39ea004b70c95543c08496245be595b3ea044a29
    BUG: 1219355
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10622
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 8812e4f57f2138c159d99432748cf68240241675
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Apr 17 12:00:48 2015 +0530

    cluster/dht: change log level of developer logs to DEBUG
    
    A few log messages in dht directory self heal at log level INFO are useful
    only for developers and these logs tend to casue excessive logs in our
    log files. Hence moving the log level of such logs to DEBUG.
    
    Change-Id: I8a543f4ddeb5c20b2978a0f7b18d8baccc935a54
    BUG: 1217949
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10281
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f1ac02a52f4019e7890ce501af7e825ef703d14d
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Tue May 5 17:03:39 2015 +0530

    geo-rep: rename handling in dht volume(changelog changes)
    
    Background:
    
    Glusterfs changelogs are stored in each brick, which records the changes
    happened in that brick. Georep will run in all the nodes of master and processes
    changelogs "independently".  Processing changelogs is in brick level, but
    all the fops will be replayed on "slave mount" point.
    
    Problem:
    
    With a DHT volume, in changelog "internal fops" are NOT recorded.
    For Rename case, Rename is recorded in "hashed" brick changelog.
    (DHT's internal fops like creating linkto file, unlink is NOT recorded).
    This lead us to inconsistent rename operations.
    
    For example,
    Distribute volume created with Two bricks B1, B2.
    
    //Consider master volume mounted @ /mnt/master and following operations
    executed:
    cd /mnt/master
    touch f1 // f1 falls on B1 Hash
    mv f1 f2 // f2 falls on B2 Hash
    
    // Here, Changelogs are recorded as below:
    @B1
    CREATE f1
    
    @B2
    RENAME f1 f2
    
    Here, race exists between Brick B1 and B2, say B2 will get executed first.
    Source file f1 itself is "NOT PRESENT", so it will go ahead and create
    f2 (Current implementation).
    
    We have this problem When rename falls in another brick and
    file is unlinked in Master.
    
    Similar kind of issue exists in following case too(multiple rename):
    CREATE f1
    RENAME f1 f2
    RENAME f2 f1
    
    Solution:
    
    Instead of carrying out "changelogging" at "HASHED volume",
    carry out  at the "CACHED volume".
    This way we have rename operations carried out where actual files are present.
    
    So,Changelog recorded as :
    @B1
    CREATE f1
    RENAME f1 f2
    
    Note:
    This patch is dependent on dht changes from this patch.
    http://review.gluster.org/10410/
    changelog related changes are separated out for review.
    
    In changelog, xdata passed from DHT is considered as :
    
    1. In case of unlink (internal operation as part of rename), xdata value
    is set , it is considered as RENAME and recorded accordingly.
    2. In case of rename (Hash and Cache different), xdata value is NOT
    set, recording rename operation is SKIPPED.
    
    BUG: 1141379
    Change-Id: Ifca675e6d4ef8c4e3b7ef4a7ec85de8b3a38dc08
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/10220
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit e88837ed0ff68093912c2b8e996c5851c53674ca
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Apr 30 12:28:17 2015 +0530

    tools/glusterfind: GFID to Path conversion using Changelog
    
    Records fop information collected from Changelogs in sqlite database.
    This is only working database, not required after processing.
    
    After post processing, output file is generated by reading these
    database files.
    
    This is applicable only in incremental run, When a changelog is
    parsed, all the details are saved in Db. GFID to Path is converted
    to those files for which information is available in Changelogs.
    
    For all the failed cases, it tries to convert to Path using Pgfid,
    if not found GFID to Path is done using find.
    
    BUG: 1201284
    Change-Id: I53f168860dae15a0149004835e67f97aebd822be
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10463
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2676c402bc47ee89b763393e496a013e82d76e54
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Sat May 2 17:31:07 2015 +0530

    cli/tiering: Enhance cli output for tiering
    
    Fix for handling cli output for attach-tier and
    detach-tier
    
    Change-Id: I4d17f4b09612754fe1b8cec6c2e14927029b9678
    BUG: 1211562
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10284
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e561935d0153f00f2ddacde093c12284affe9538
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Apr 20 14:03:58 2015 +0530

    tools/glusterfind: Partial Find
    
    Enabled by default, if one node fails Glusterfind will not fail
    to return list of files from other nodes. This behavior can be changed
    using --disable-partial
    
    Now session is maintained in each nodes as well as in initiator node.
    Every pre command will pick the status file from respective node and
    start collecting list of changes happened after the status time.
    
    --reset-session-time, new option to force reset the session time.
    Next incremental run will start from this time.
    
    Change-detector argument is removed since Changelog mode is required
    to detect deletes and Renames.
    
    Change-Id: I0b83bc7c0e1b30b13de772b2d21fe968db4ff964
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1201289
    Reviewed-on: http://review.gluster.org/10320
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bbff9e1ef72e2eab63e5d7ecd5dfa36497b642ed
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri May 8 21:03:09 2015 +0530

    features/changelog: Fix buffer overflow in snprintf
    
    Change-Id: Ie7e7c6028c7bffe47e60a2e93827e0e8767a3d66
    BUG: 1219894
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10687
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit 77edf5f7f78d5a551526b0d9bef8e0c0a8f22c1c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Sat May 9 00:26:14 2015 +0530

    geo-rep: Fix corrupt gsyncd output
    
    When gsyncd fails with Python traceback, glusterd fails
    parsing gsyncd output and shows error.
    
    BUG: 1219937
    Change-Id: Ic32fd897c49a5325294a6588351b539c6e124338
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10694
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5fda96d954dd06dbacc6b2851d4ba058ec1295a2
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Sat May 2 19:19:27 2015 +0530

    tiering: Remove unwanted check for tier type volume
    
    Change-Id: I2def61ebf348558e5f6a138265e3329d9a5407a3
    BUG: 1216898
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10494
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit 1162bb36108ab8dba8303b86927a99835b791d79
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Apr 29 13:03:52 2015 +0530

    libgfapi: Store and restore THIS in every API exposed by libgfapi
    
    Storing and restoring THIS:
    When the APIs exposed by libgfapi are called by other xlators like
    snapview server etc. the THIS value is overwritten to contain the
    THIS of libgfapi(viz libgfapi master xlator). Hence using 'THIS'
    in any xlator after calling libgfapi API will lead to issues.
    One such issue was uncovered in snapview and the patch
    http://review.gluster.org/#/c/9469/ was sent to workaround this issue.
    
    Hence, storing and restoring THIS, at the entry and exit of every API
    exposed by libgfapi.
    
    Change-Id: I6f330dde25e7700fb26339d667a7ccd193ec6ba0
    BUG: 1210934
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9797
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0950e6c29fc51ddcc5bb7e1e4187d54ff7c171d2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu May 7 10:58:46 2015 +0530

    tests : workaround fix for volume-snapshot-clone spurious failure
    
    Snippet of the existing test:
    
    TEST kill_glusterd 2;
    TEST $glusterd_2;
    sleep 5
    EXPECT_WITHIN $PROCESS_UP_TIMEOUT 'Started' volinfo_field ${V0}_clone 'Status';
    EXPECT_WITHIN $PROCESS_UP_TIMEOUT 'Started' volinfo_field ${V1}_clone 'Status';
    stop_force_volumes 2
    
    The above EXPECT_WITHINs will not wait as the volumes were never stopped which
    results into immediate trigger of volume stop where handshaking is not
    completed. A workaround would be to check whether handshaking is completed and
    then proceed.
    
    Change-Id: Id3468b56f801212fc8e19ff196bc99e5e2358471
    BUG: 1163543
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10619
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 6601aad8380f0f0ccbd4bb9147d8d3584a88da20
Author: Hari Gowtham <hari.gowtham005@gmail.com>
Date:   Mon Apr 13 16:06:56 2015 +0530

    nfs.c nfs3.c: port log messages to a new framework
    
    Change-Id: I9ddb90d66d3ad3adb2916c0c949834794ee7bdf3
    BUG: 1194640
    Signed-off-by: Hari Gowtham <hari.gowtham005@gmail.com>
    Reviewed-on: http://review.gluster.org/10216
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit c93c433a44770de931f837be179c5ccdba958cad
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Apr 9 15:38:47 2015 +0530

    features/bit-rot-stub: versioning of objects in write/truncate fop instead of open
    
    * This patch brings in the changes where object versioning is done in write and
      truncate fops instead of tracking them in open and create fops. This model
      works for both regular and anonymous fds. It also removes the race associated
      with open calls, create and lookups.
    
      This patch follows the below method for object versioning and notifications:
    
      Before sending writev on the fd, increase the ongoing
      version first. This makes anonymous fd write similar to the regular
      fd write by having the ongoing version increased before doing the
      write.
    
      Do following steps to do versioning:
      1) For anonymous fds set the fd context (so that release is invoked) and add
         the fd context to the list maintained in the inode context.
         For regular fds the above think would have been done in open itself.
      2) Increase the on-disk ongoing version
      3) Increase the in memory ongoing version and mark inode as non-dirty
      3) Once versioning is successfully done send write operation. If
         versioning fails, then fail the write fop.
      5) In writev_cbk mark inode as modified.
    
    Change-Id: I7104391bbe076d8fc49b68745d2ec29a6e92476c
    BUG: 1207979
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/10233
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 680b3bf629f0fef038470baab62c6d6d8f5988ce
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu Apr 16 05:21:16 2015 +0100

    glusterd: add counter support for tiered volumes
    
    This fix adds support to view the number of promoted or demoted
    files from the cli. The mechanism is isolmorphic to checking
    the status of volumes being rebalanced.
    
    gluster volume rebalance <vol> tier status
    
    Change-Id: I1b11ca27355ceec36c488967c23531202030e205
    BUG: 1213063
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10292
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d4d9cfc82d7cf7797227b8b929ba193fbaf389e6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 8 16:18:13 2015 +0530

    tests: Disable flush-behind
    
    Change-Id: Ibbb6b03d2878ef4a049f737662c31e70a68e5755
    BUG: 1219816
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10666
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit aceecc2285ab3e5d3150f0d8c644371213c61b65
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri May 8 20:38:33 2015 +0530

    features/changelog: Fixing compilation issue
    
    This issue introduced due to manual rebase.
    
    Change-Id: I0589f4a0a1270190340f419b8022d6483bcf853d
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1219479
    Reviewed-on: http://review.gluster.org/10685
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 02f9835d24aa07bd4e9fcb39cb7ace343f31924f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Apr 26 14:28:00 2015 +0530

    cluster/ec: Change meaning of trusted.ec.dirty
    
    - With this change, the xattr will represent if the file needs to be healed or
      not. It will have different values for data/entry and metadata changes.
    - inode ref leaks and dict_set_dynstr related leaks fixed
    - Added support for trylock/lock based on heal-cmd execution or not
      in data heal.
    - Made fixes to pass regression runs
    
    Change-Id: I9d8def4c2badde18a76b7898816fecfac113737a
    BUG: 1215265
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10385
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bf8250bcca7f484269f64b6a73f9330d843b320b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri May 8 05:59:15 2015 +0200

    Tests: fix file count in ec-readdir.t
    
    On BSD systems, ls(1) reports dot-files when it is run as root, while
    Linux ls(1) does not do that. In ec-readdir.t, this means the directory
    count is different because of .trashcan directory.
    
    Fix this by using ls $M0/* instead of ls $M0
    
    BUG: 1129939
    Change-Id: Ia337c8a8e68a163ed527c0e4cbe313072ab1672b
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10657
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fc199e1b6f9423b4dc0c9b34bf894ad66ffafabf
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Apr 25 15:58:09 2015 +0530

    cluster/ec: data heal implementation for ec
    
    Data self-heal:
    1) Take inode lock in domain 'this->name:self-heal' on 0-0 range (full file),
       So that no other processes try to do self-heal at the same time.
    2) Take inode lock in domain 'this->name' on 0-0 range (full file),
    3) perform fxattrop+fstat and get the xattrs on all the bricks
    3) Choose the brick with ec->fragment number of same version as source
    4) Truncate sinks
    5) Unlock lock taken in 2)
    5) For each block take full file lock, Read from sources write to the sinks, Unlock
    6) Take full file lock and see if the file is still sane copy i.e. File didn't become unusable while the bricks are offline.
       Update mtime to before healing
    7) xattrop with -ve values of 'dirty' and difference of highest and its own
       version values for version xattr
    8) unlock lock acquired in 6)
    9) unlock lock acquired in 1)
    
    Change-Id: I6f4d42cd5423c767262c9d7bb5ca7767adb3e5fd
    BUG: 1215265
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10384
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 33fdc310700da74a4142dab48d00c4753100904b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Apr 16 09:25:31 2015 +0530

    cluster/ec: metadata/name/entry heal implementation for ec
    
    Metadata self-heal:
    1) Take inode lock in domain 'this->name' on 0-0 range (full file)
    2) perform lookup and get the xattrs on all the bricks
    3) Choose the brick with highest version as source
    4) Setattr uid/gid/permissions
    5) removexattr stale xattrs
    6) Setxattr existing/new xattrs
    7) xattrop with -ve values of 'dirty' and difference of highest and its own
       version values for version xattr
    8) unlock lock acquired in 1)
    
    Entry self-heal:
    1) take directory lock in domain 'this->name:self-heal' on 'NULL' to prevent
       more than one self-heal
    2) we take directory lock in domain 'this->name' on 'NULL'
    3) Perform lookup on version, dirty and remember the values
    4) unlock lock acquired in 2)
    5) readdir on all the bricks and trigger name heals
    6) xattrop with -ve values of 'dirty' and difference of highest and its own
       version values for version xattr
    7) unlock lock acquired in 1)
    
    Name heal:
    1) Take 'name' lock in 'this->name' on 'NULL'
    2) Perform lookup on 'name' and get stat and xattr structures
    3) Build gfid_db where for each gfid we know what subvolumes/bricks have
       a file with 'name'
    4) Delete all the stale files i.e. the file does not exist on more than
       ec->redundancy number of bricks
    5) On all the subvolumes/bricks with missing entry create 'name' with same
       type,gfid,permissions etc.
    6) Unlock lock acquired in 1)
    Known limitation: At the moment with present design, it conservatively
    preserves the 'name' in case it can not decide whether to delete it.  this can
    happen in the following scenario:
    1) we have 3=2+1 (bricks: A, B, C) ec volume and 1 brick is down (Lets say A)
    2) rename d1/f1 -> d2/f2 is performed but the rename is successful only on one
       of the bricks (Lets say B)
    3) Now name self-heal on d1 and d2 would re-create the file on both d1 and d2
       resulting in d1/f1 and d2/f2.
    
    Because we wanted to prevent data loss in the case above, the following
    scenario is not healable, i.e. it needs manual intervention:
    1) we have 3=2+1 (bricks: A, B, C) ec volume and 1 brick is down (Lets say A)
    2) We have two hard links: d1/a, d2/b and another file d3/c even before the
       brick went down
    3) rename d3/c -> d2/b is performed
    4) Now name self-heal on d2/b doesn't heal because d2/b with older gfid will
       not be deleted.  One could think why not delete the link if there is
       more than 1 hardlink, but that leads to similar data loss issue I described
       earlier:
    Scenario:
    1) we have 3=2+1 (bricks: A, B, C) ec volume and 1 brick is down (Lets say A)
    2) We have two hard links: d1/a, d2/b
    3) rename d1/a -> d3/c, d2/b -> d4/d is performed and both the operations are
       successful only on one of the bricks (Lets say B)
    4) Now name self-heal on the 'names' above which can happen in parallel can
       decide to delete the file thinking it has 2 links but after all the
       self-heals do unlinks we are left with data loss.
    
    Change-Id: I3a68218a47bb726bd684604efea63cf11cfd11be
    BUG: 1213358
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10298
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit df919238505a74a9d89b308bbc6d01b797140439
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Wed Apr 29 17:33:43 2015 +0530

    features/changelog: Avoid creation of empty changelogs
    
    An empty changelog when rolled over gets unlinked and indexed with
    a modified path-name in htime file. The modification is "changelog"
    not "CHANGELOG" in basename of the empty changelog file.
    
    Change-Id: I77fd0b48b5c33c245418f5ac7a9756f08ece24d9
    BUG: 1208470
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/9572
    Tested-by: NetBSD Build System
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9c21c5a632ba22a6f46d037bd4fa4d825b24d07f
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Fri May 8 15:18:06 2015 +0530

    tiering: Correction to tiering documentation
    
    1) convert to md format
    2) Add info about ctr and libgfdb
    
    Change-Id: I531d8a0bff8195f759302c5e613c7af2113729eb
    BUG: 1218638
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10665
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit a5d124728640f58fa3f90007c149ad69809b6ca4
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri May 8 11:26:20 2015 +0530

    tests: Marked tests/bugs/snapshot/bug-1112559.t as bad-test
    
    The fix that introduced this test has been reverted as part of design change.
    Hence marking it as a bad test.
    
    Change-Id: I811b6050edbf4bbb40b9ef518604d21d386f6d5c
    BUG: 1219738
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10660
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fd8b8a81c243776b20e6d48993524ee3f1351ca6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue May 5 10:28:15 2015 +0200

    rpm: reduce package dependencies and add -client-xlators
    
    Restructuring the RPM packages in order to reduce the dependencies that
    get installed for glusterfs-api (mainly on request for Qemu hosts).
    
    The dependencies of these packages look roughly like this:
    
      .------------------.
      | glusterfs-server |
      '-------+----------'
              |\
              | \
              |  '---------------+--------------------.
              |                  |                    |
              |                  v                    v
              |         .----------------.     .---------------.
              |         | glusterfs-fuse |     | glusterfs-api |
              |         '--------+-------'     '------+--------'
              |                 /|                   /|
              |                / |                  / |
              |               /  |                 /  |
              |              /   |                /   |
              | .-----------+----=---------------'    |
              |/                 |                    |
              v                  v                    v
        .-----------.         .--------------------------.
        | glusterfs |         | glusterfs-client-xlators |
        '-----------'         '--------------------------'
    
    With this structure, users can install glusterfs-server, glusterfs-fuse
    or glusterfs-api (libgfapi) without getting any unneeded xlators or
    other scripts/binaries.
    
    The "glusterfs" and "glusterfsd" binary (symlinked) is now part of the
    glusterfs-fuse package (moved from glusterfs). This does not make a
    difference for glusterfs-server installations, because a server
    installation always needs the glusterfs-fuse package for doing internal
    mounts.
    
    The advantage is that glusterfs-api does not pull in any executables
    that get into the $PATH. This has caused confusion before when people
    tried to remove the (wrongly assumed) server-only "glusterfsd" binaries.
    
    URL: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10643
    Change-Id: Id03f1a634ea3c62ab7008345be92e01ccf43b1a6
    BUG: 1195947
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10554
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 1a9df097463d41679b87b6cbd4634fc3390fe82c
Author: arao <arao@redhat.com>
Date:   Tue Feb 17 16:53:14 2015 +0530

    dht: Fixing dereference after null check
    
    CID: 1223229
    The 'loc' ptr is not checked before
    dereferencing, which is handled.
    
    Change-Id: Icf668150bde190e6f1b9f58a038099338516efe8
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9666
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 9dcb6e07cf432a047654a3f04a23a438fe969bfb
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon May 4 11:58:23 2015 +0530

    features/bitrot: Scrubber pause/resume
    
    With logical scan/scrub split, pausing filesystem scrubber is an
    override to the thread throttling mechanism, which effectively
    throttles "down" number of scrubber threads to zero. This causes
    scanner to wait until threads are spawned again (when resumed)
    thereby continuing where it left off (since the file tree walk
    stack is effectively preserved when the main scanner thread
    is waiting for scrubbers to consume scanned entries).
    
    The only catch is when scrubber daemon restarts: file tree walk
    stack is lost and scrubbing initiates from root. This is probably
    OK for now (can be changed later to persist parent directory
    information before entering pause state).
    
    Change-Id: I5109a749b7fccd0f5367765078f46e6522dd32a1
    BUG: 1208131
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10521
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 7c0c184be28e0cba08645c7106c6901b444651c9
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Apr 23 16:24:43 2015 +0530

    tiering: Do not allow some operations on tiered volume
    
    Some operations like add-brick,remove-brick,rebalance,
    replace-brick are not supported on tiered volume.
    
    But there is no code level check for this. This patch
    will allow to do the same
    
    Change-Id: I12689f4e902cf0cceaf6f7f29c71057305024977
    BUG: 1205624
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10349
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 9ba8963999bca431ec14a25961a163810cfe1e5b
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Apr 27 21:34:34 2015 +0530

    features/bitrot: Throttle filesystem scrubber
    
    This patch introduces multithreaded filesystem scrubber based
    on throttling option configured for a particular volume. The
    implementation "logically" breaks scanning and scrubbing with
    the number of scrubber threads auto-configured depending upon
    the throttle configuration. Scanning (crawling) is left single
    threaded (per brick) with entries scrubbed in bulk. On reaching
    this "bulk" watermark, scanner waits until entries are scrubbed.
    Bricks for a particular volume have a set of thread(s) assigned
    for scrubbing, with entries for each brick scrubbed in a round
    robin fashion to avoid scrub "stalls" when a brick (out of N
    bricks) is under active scrubbing.
    
    This mechanism helps us implement "pause/resume" with ease: all
    one need to do is to cleanup scrubber threads and let the main
    scanner thread "wait" untill scrubbing is resumed (where the
    scrubber thread(s) are spawned again), therefore continuing
    where we left off (unless we restart the deamons, where crawl
    initiates from root directory again, but I guess that's OK).
    
    [
        NOTE:
    
        Throttling is optional for the signer daemon, without which
        it runs full throttle. However, passing "-DBR_RATE_LIMIT_SIGNER"
        predefined in CFLAGS enables CPU throttling (during checksum
        calculation) thereby avoiding high CPU usage.
    ]
    
    Subsequent patches would introduce CPU throttling during hash
    calculation for scrubber.
    
    Change-Id: I5701dd6cd4dff27ca3144ac5e3798a2216b39d4f
    BUG: 1207020
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10511
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4ccd70b323d4cb929b7b7a88e592fc98fab06198
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Thu May 7 22:48:24 2015 -0400

    Documentation for tiering feature. (WIP)
    
    This is a WIP.
    
    Change-Id: Ia36f77d158a370f77cb866a32308b27e10d39b5e
    BUG: 1218638
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10656
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit d914cd909b9a99d7645b633000940195277bb6ff
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed May 6 18:18:25 2015 +0530

    tiering/cli: while attaching tier to volume cli should ask question
    
    Because of tiering feature is recommended only for testing purpose in
    this release, attaching tier should get a confirmation from the user
    before proceeding with the command.
    
    Change-Id: I141bbb1d0439f0a28eb51d17f7800908e35c75ad
    BUG: 1219032
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10610
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 768b86a269378e66f9378295073740ff6e0cb02e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 5 06:50:46 2015 +0530

    features/shard: Implement [f]truncate fops
    
    To-Do:
    * Make ftruncate work even in the absence of path
    * Aggregate and update ia_blocks appropriately when a file is
      truncated to a lower size.
    
    Change-Id: Ifd24c2f5e80d2c3bc921261f5481251df8948126
    BUG: 1207615
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10631
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit eb8847703b8560a045e7ed0336f895bcceda98ea
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed May 6 10:28:56 2015 +0200

    nfs: allocate the auth_cache->cache_dict on auth_cache_init()
    
    It seems possible that auth_cache->cache_dict is not always allocated
    before it is accessed. Instead of allocating the dict upon the 1st
    access, just create it in auth_cache_init().
    
    Change-Id: I00e60522478b433cb0aae0c1f0948eac544dfd2b
    URL: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10710
    BUG: 1143880
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10600
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: NetBSD Build System

commit 317560cc5544f8ca8286ba5ecedd8236746e9ebf
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu May 7 12:39:05 2015 +0200

    glupy: fix tuntime search path and python module directory layout
    
    1) The glupy.so xlator should embed the runtime search path for
    the python libraries. Unfortunately, python-config does not
    gives the appprioate flags, therefore we need to also use
    pkg-config to obtain them
    
    2) Fix the glupy python module directory layout so that python
    can import the module without problem
    
    That two fixes seems to let glupy.t pass on NetBSD again.
    
    BUG: 1129939
    Change-Id: I397aa726ab8bf7d91fa0d6d870a30910a5f4a5d9
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10616
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 865aa4ebdd71d39f8e8ae59b40d993edb4a62708
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu May 7 20:28:11 2015 +0200

    Restore build on non Linux systems
    
    This change broke the build on NetBSD, FreeBSD, and MacOS X:
    http://review.gluster.org/10526/
    
    We restore the build with two fixes:
    - Use POSIX-compliant sysconf(_SC_NPROCESSORS_ONLN) to get the
      number of processors, instead of Linux specific get_nprocs().
      That let us remove Linux-specific #include <sys/sysinfo.h>
    - Only define MAX() if it is not already defined. NetBSD defines
      it in <sys/param.h> which is already included
    
    BUG: 1129939
    Change-Id: I62341c670598670e47ea2f69ab94864f96588b18
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10652
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 7f950ed3ae4f99542ba4bbabec5fc1a86850a528
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Thu May 7 15:34:06 2015 +0530

    NFS-Ganesha : Improved sed expression in cleanup
    
    The global config file should not be emptied when
    tear down is called. Improving the sed expression
    to delete the ".conf" files only
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    
    Change-Id: Ida3d303f629cb512c02dadacce1ec7e5f07db018
    BUG: 1218854
    Reviewed-on: http://review.gluster.org/10630
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4c6e9c5f8d62444412c86545868cdb5bf6a06b39
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Apr 17 15:00:13 2015 +0530

    features/bit-rot: Token Bucket based throttling
    
    BitRot daemons (signer & scrubber) are disk/cpu hoggers when left
    running full throttle. Checksum calculations (especially SHA family
    of hash routines) can be quite CPU intensive. Moreover periodic
    disk scans performed by scrubber followed by reading data blocks
    for hash calculation (which is also done by signer) generate lot
    of heavy IO request(s). This causes interference with actual client
    operations (be it a regular client or filesystems daemons such as
    self-heal, etc..) and results in degraded system performance.
    
    This patch introduces throttling based on Token Bucket Filtering[1].
    It's a well known algorithm for checking (and ensuring) that data
    transmission conform to defined limits and generally used in packet
    switched networks. Linux control groups (Cgroups) uses a variant[2]
    of this algorithm to provide block device IO throttling (cgroup
    subsys "blkio": blk-iothrottle).
    
    So, why not just live with Cgroups?
    Cgroups is linux specific. We need to have a throttling mechanism
    for other supported UNIXes. Moreover, having our own implementation
    gives much more finer control in terms of tuning it for our needs
    (plus the simplicity of the alogorithm itself).
    
    Ideally, throttling should be a part of server stack (either as a
    separate translator or integrated with io-threads) since that's
    the point of entry for IO request(s) from *all* client(s). That
    way one could selectively throttle IO request(s) based on client
    PIDs (frame->root->pid), e.g., self-heal daemon, bitrot, etc..
    (*actual* clients can run full throttle). This implementation
    avoids that deliberately (there needs to be a much more smarter
    queueing mechanism) and throttles CPU usage for hash calculations.
    
    This patch is just the infrastructure part with no interfaces
    exposed to set various throttling values. The tunable selected
    here (basically hardcoded) avoids 100% CPU usage during hash
    calculation (with some bursts cycles). We'd need much more
    intensive test(s) to assign values for various throttling
    options (lazy/normal/aggressive).
    
    [1] https://en.wikipedia.org/wiki/Token_bucket
    [2] http://en.wikipedia.org/wiki/Token_bucket#Hierarchical_token_bucket
    
    Change-Id: Icc49af80eeab6adb60166d0810e69ef37cfe2fd8
    BUG: 1207020
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10307
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit aa938247e19afa419476fb2d0b7cb2d054c6dd47
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Apr 29 15:52:37 2015 +0200

    Tests: use a portable way to flush kernel cache
    
    On Linux, kernel cache can be flushed using
    echo 3 > /proc/sys/vm/drop_caches
    
    This non-portable approach can be replaced by an on-purpose
    failed attempt to unmount: if the mount point is the current
    directory and umount is called, the kernel will flush inodes
    until it realize it cannot complete the operation because
    root of filesystem is busy:
    ( cd $M0 ; umount $M0 )
    
    Unfortunately this does not flush everything. Entries may
    still be present in the kenrel FUSE cache. Using $GFS to
    mount the filesystem ensure --entry-timeout=0 and clears
    this problem.
    
    Some stall information may also remain in glusterfs caches,
    and that may have to be adressed by appropriate volume option.
    For instance tests/bugs/rpc/bug-954057.t needs to disable
    performance.stat-prefetch. Qtherwise, root's new credentials
    are not evaluated after root-quash is enabled. The test could
    also be done with performance.stat-prefetch enabled using
    various tricks: copying the file to read, creating a hard link
    on it, or just waiting long enough for metadata cache to expire.
    
    BUG: 1129939
    Change-Id: I54929e899d55c04dcd9d947809133549f01fd0e1
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10411
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f93bf09cdb417cf5e09206164a16ad9435285b45
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue May 5 18:20:19 2015 +0530

    geo-rep: Fix Default values in Xml output
    
    Default Values for last_synced, checkpoint_time and
    checkpoint_completion_time was zero instead of 'N/A'
    
    BUG: 1212410
    Change-Id: Ie775508f8dcb9ba6f311946a2039739e4336d9a6
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10580
    Reviewed-by: darshan n <dnarayan@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 394246d5416c3166e8fb3c8f92a5027c86decebd
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Apr 21 23:45:07 2015 +0530

    tools/glusterfind: Rpm install dependencies added
    
    Argparse Python library is available as standard library in Python 2.7
    In rhel, we need to install python-argparse.
    
    Also added pyxattr dependency to the spec file.
    
    Change-Id: Ie50278eddf81e7cbf98d1e8d27e411b46676b432
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1209138
    Reviewed-on: http://review.gluster.org/10321
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3122268c0b7c120eb79aa02a64fbbebd91a17357
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue May 5 14:26:05 2015 +0530

    geo-rep: Fix Rsync hang issue
    
    When rsync is executed using Python subprocess, by default
    stdout of subprocess will be None. With the log rsync performance
    patch stdout is assigned to PIPE. Rsync writes to that PIPE
    whenever it syncs files. If log_rsync_performance is disabled
    then nobody will consume stdout and that gets full. Rsync hangs
    if PIPE is full.
    
    log_rsync_performance option is introduced with patch 10070
    
    With this patch stdout=PIPE only if log_rsync_performance is
    enabled. Also removed -v option from Rsync.
    
    Thanks Venky and Kotresh for RCA.
    
    BUG: 1218552
    Change-Id: I4ebcfb6999358c8e2c147f7964255bd836ed7499
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10556
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9096a79447d4ac72612c86407f35bdb68a4fef88
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Wed May 6 12:13:31 2015 +0530

    NFS-Ganesha: Add-node and delete-node changes in HA implementation
    
    NFS-Ganesha related config files have to be copied over to the new node
    and NFS-Ganesha service has to be started.
    Similary NFS-Ganesha service has to be stopped when a node is
    deleted from the HA cluster.
    
    Change-Id: Ia38e72cac86713fe23b7d1b829a256637a9ca796
    BUG: 1212816
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/10596
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 82684f1efeb1685a1c794c1c875e3ac21f810481
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Feb 12 18:59:35 2015 +0530

    snapshot: Handshake with glusterd is not proper
    
    If a snap is activated or deactivated, when a node is down,
    it is not retrieving the data properly during the handshake
    of glusterd
    
    With this patch, a version check will made when a glusterd
    is started running. If there is a mismach in version, then
    peers will exchange the healed data.
    
    Change-Id: I8bd2a347723db2194d3fa73295878b4dd2e9be5d
    BUG: 1122377
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9664
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a661f7f54cef34aa39894818568a2c1b462e8cbc
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Tue May 5 23:47:58 2015 +0530

    tests: Spurious failure in fop-sanity.t
    
    Modified the calls to open in fops-sanity.c to pass in
    the mode as well if flags includes O_CREAT (as per man page).
    The missing mode randomly caused T files to be created causing DHT
    to treat them as linkto files and fail the fop.
    
    Modified 2 other files where the mode was not being provided.
    
    Change-Id: I047573d43655b4957d0703f7df36238f7e729c1f
    BUG: 1218951
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/10590
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2bd2ccf0fdd5390c1c07cb228048f93e5e516512
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Apr 3 18:03:50 2015 +0200

    stripe: set ENOENT when a READ hits EOF
    
    The NFS-server sets EOF only in the READ reply when op_errno is set to
    ENOENT.  Xlators are expected to set op_errno to ENOENT when EOF is
    reached, op_ret will contain the number of bytes returned by the READ.
    
    When an NFS-client (like VMware ESXi) do a READ that exceeds the size of
    the file, errno should be set to EOF and the return value contains the
    number of bytes that are read (from the requested offset, until the end
    of the file). Not setting EOF on a correct short READ, can result in
    errors on the NFS-client.
    
    This is not an issue with the Linux NFS-client (or VFS). Linux is smart
    enough to not try to read more bytes than the file contains.
    
    BUG: 1209298
    Change-Id: Ib15538744908a6001d729288d3e18a432d19050b
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10142
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 98bd9830da7071eed71c95611da7ef8a5f1cf71e
Author: Susant Palai <spalai@redhat.com>
Date:   Mon May 4 16:43:02 2015 +0530

    dht/rebalance: Throttle rebalance
    
    Throttle value will be "normal" by default. For throttling down,
    a thread will be put in to sleep. And for throttling up,
    gf_defrag_process_dir will wake up the sleeping threads.
    
    Change-Id: I74d530e3effd6e60e6eec81ccc8ff65789fa9c13
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/10526
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 6c578c03f0d44913d264494de5df004544c96271
Author: Anuradha <atalur@redhat.com>
Date:   Thu Apr 30 15:31:13 2015 +0530

    cluster/afr : Prevent inode-evict during split-brain resolution
    
    1) Provided setfattr command to set timeout for split-brain
    choice.
    2) If split-brain inspection/resolution is being done
    from the mount for a file, ref the inode when
    split-brain-choice is set.
    This inode will be unconditionally unref-ed after timeout
    seconds set by the user/default otherwise.
    3) Updated the doc and testcase to reflect the changes.
    
    Change-Id: I15c9037dee28855f21e680e7e3632e1f48dba4e1
    BUG: 1209104
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10134
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d68a2dbb3a4be89a4a45661310ae3f32542df20f
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Mon Apr 13 12:34:26 2015 +0530

    bitrot/glusterd: Bitrot scrub pause/resume should give proper error
    
    bitrot scrubber paused/resume command should give proper error messages if
    scrubber already pause/resume and user again try to perform same
    operation on a volume.
    
    Change-Id: I01ad69c80f03b177535a4e5f1c95ab7709a804b0
    BUG: 1210684
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10209
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 02583099a219ce327aac62af22b486c7b9fcb531
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed May 6 13:10:15 2015 +0530

    glusterd: Use generation number to find peerinfo in RPC notifications
    
    The generation number for each peerinfo object is unique. It can be used
    to find the exact peerinfo object, which is required for peer RPC
    notifications.
    
    Using hostname and uuid matching to find peerinfos can return incorrect
    peerinfos to be returned in certain cases like multi network peer probe.
    This could cause updates to happen to incorrect peerinfos.
    
    Change-Id: Ia0aada8214fd6d43381e5afd282e08d53a277251
    BUG: 1215018
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/10495
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 07e3f407b311c80e3437b1f650cae62f814d995b
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Fri Mar 27 15:20:03 2015 +0530

    glusterd: remove replace brick with data migration support form cli/glusterd
    
    Replace-brick operation with data migration support have been
    deprecated from gluster.
    
    With this fix replace brick command will support only one commad
    
    gluster volume replace-brick <VOLNAME> <SOURCE-BRICK> <NEW-BRICK> {commit force}
    
    Change-Id: Ib81d49e5d8e7eaa4ccb5830cfec2bc081191b43b
    BUG: 1094119
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10101
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 84a0baabfb9aa29348d8b17b7517870d46023ab3
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Apr 9 00:14:50 2015 +0530

    features/changelog: Version support for Changelog Parser
    
    As optional feature, during unlink, full path will be recorded.
    Changelog Version number to be bumped up to 1.2.
    
    With this patch, parser checks the version number before parsing
    and handles accordingly.
    
    Change-Id: Ic1ad98259c39e417029a08e26a1d4b467817e65a
    BUG: 1214561
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10166
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 50063ea7f4182ed30b86f38a716d03464e07b8c6
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Tue Apr 21 17:22:40 2015 +0530

    cluster/ec: add separate versions for data/entry, metadata
    
    Adding 64 bits in "version" key of extended attributes. First 64 bits (Left)
    represents Data version. Last 64 bits (right) represents Meta Data version.
    
    Note: 3.7 and 3.6 version ec can't co-exist with this change because xattrop in
    3.6 will fail with ERANGE as the buffer passed to it will be '8' bytes where as
    the value will be 16 bytes in 3.7. Where as 3.7 version clients can work with
    old version files. For upgrades we need to tell users to complete heals and
    then upgrade
    
    BUG: 1215265
    Change-Id: Ib85114680cb7e75b8371c984d9f7b6401c1ffb93
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/10312
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit b054985d2f7db9ab72759c988db11feb855a1b5e
Author: vmallika <vmallika@redhat.com>
Date:   Thu Apr 30 16:50:47 2015 +0530

    quota/marker: turn off inode quotas by default
    
    inode quota is a new feature implemented in glusterfs-3.7
    if quota is enabled in the older version and is upgraded
    to a new version, we can hit setxattr spike during self-heal
    of inode quotas. So, when a quota is enabled, turn off
    inode-quotas with a xlator option.
    
    With this patch, we still account for inode quotas but only
    when a write operation is performed for a particular file.
    User will be able to query inode quotas once the Inode-quota
    xlator option is enabled.
    
    Change-Id: I52fb28bf7024989ce7bb08ac63a303bf3ec1ec9a
    BUG: 1209430
    Signed-off-by: vmallika <vmallika@redhat.com>
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/10152
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e79edf35178f2558d6afb262444294380b76d740
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Wed May 6 09:58:11 2015 +0530

    NFS-Ganesha : Do not empty global config file when cluster is torn
    
    The global config file will need new blocks to support client lock recovery.
    Current cleanup function empties the entire file. Deleting only "include"
    lines in the config file.
    
    Change-Id: I21f09e30a738d2ba01861ce480ecf906667d887b
    BUG: 1218854
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/10592
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 403a74da5d3287489829c629d42643b8b320ee62
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Mon Apr 20 10:41:47 2015 +0530

    NFS-Ganesha : Locking global options file
    
    Global option gluster features.ganesha enable
    writes into the global 'option' file. The snapshot
    feature also writes into the same file.
    
    To handle concurrent multiple transactions correctly,
    a new lock has to be introduced on this file.
    Every operation using this file needs
    to contest for the new lock type.
    
    Change-Id: Ia8a324d2a466717b39f2700599edd9f345b939a9
    BUG: 1200254
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/10130
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 96871c7ddc39cdb502ebfb6d975fe8859fc3e0e9
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed May 6 16:26:03 2015 +0530

    doc/admin-guide: BitRot command line usage
    
    Change-Id: Ic3c9da566673f4d9b1d0974c5aa15121da087fba
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10607
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit cb11dd91a6cc296e4a3808364077f4eacb810e48
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Fri Apr 24 19:22:44 2015 +0530

    ctr/xlator: Named lookup heal of pre-existing files, before ctr was ON.
    
    Problem: The CTR xlator records file meta (heat/hardlinks)
    into the data. This works fine for files which are created
    after ctr xlator is switched ON. But for files which were
    created before CTR xlator is ON, CTR xlator is not able to
    record either of the meta i.e heat or hardlinks. Thus making
    those files immune to promotions/demotions.
    
    Solution: The solution that is implemented in this patch is
    do ctr-db heal of all those pre-existent files, using named lookup.
    For this purpose we use the inode-xlator context variable option
    in gluster.
    The inode-xlator context variable for ctr xlator will have the
    following,
        a. A Lock for the context variable
        b. A hardlink list: This list represents the successful looked
           up hardlinks.
    These are the scenarios when the hardlink list is updated:
    1) Named-Lookup: Whenever a named lookup happens on a file, in the
       wind path we copy all required hardlink and inode information to
       ctr_db_record structure, which resides in the frame->local variable.
       We dont update the database in wind. During the unwind, we read the
       information from the ctr_db_record and ,
       Check if the inode context variable is created, if not we create it.
       Check if the hard link is there in the hardlink list.
          If its not there we add it to the list and send a update to the
          database using libgfdb.
          Please note: The database transaction can fail(and we ignore) as there
          already might be a record in the db. This update to the db is to heal
          if its not there.
          If its there in the list we ignore it.
    2) Inode Forget: Whenever an inode forget hits we clear the hardlink list in
       the inode context variable and delete the inode context variable.
       Please note: An inode forget may happen for two reason,
       a. when the inode is delete.
       b. the in-memory inode is evicted from the inode table due to cache limits.
    3) create: whenever a create happens we create the inode context variable and
       add the hardlink. The database updation is done as usual by ctr.
    4) link: whenever a hardlink is created for the inode, we create the inode context
       variable, if not present, and add the hardlink to the list.
    5) unlink: whenever a unlink happens we delete the hardlink from the list.
    6) mknod: same as create.
    7) rename: whenever a rename happens we update the hardlink in list. if the hardlink
       was not present for updation, we add the hardlink to the list.
    
    What is pending:
    1) This solution will only work for named lookups.
    2) We dont track afr-self-heal/dht-rebalancer traffic for healing.
    
    Change-Id: Ia4bbaf84128ad6ce8c3ddd70bcfa82894c79585f
    BUG: 1212037
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10370
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 306585d2e57aadc7d15951ab1114d49fd9dbf5aa
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Apr 15 12:15:58 2015 +0530

    nfs : fix for coredump caused by export/netgroup feature in the regression
    
    Change-Id: Idaae234b9e81c40040393e748db1f61363a48ed0
    BUG: 1211913
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/10250
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b03f9699055eed3f1c5d73e36bbe8474a1419304
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Apr 9 16:26:31 2015 +0530

    features/bitrot: Follow xattr naming conventions
    
    Instead of "trusted.glusterfs.bit-rot.*" use "trusted.bit-rot.*"
    
    NOTE:
    With this patch, data on existing volumes would be resigned
    (which should be OK as of now since we do not expect many
    users as of now :-))
    
    Change-Id: I926c7bca266a9c8f2cb35d57c4d0359aa5cecfa0
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10181
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 68bc3c88fc37befe9ef73c8c7f5a2620c94ff4ce
Author: Susant Palai <spalai@redhat.com>
Date:   Tue May 5 18:11:52 2015 +0530

    dht/rebalance: Go to exit if defrag is NULL
    
    Problem: In case a defrag is null, going to out section will crash rebalance.
    
    Change-Id: I8b3ee1ad85dc23ef0e2f2dd6f912d07216bd619f
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/10582
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit ebf068c4ca4cfe7abcf56a816de7561130ffabf7
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sat Apr 25 18:50:46 2015 +0530

    features/shard: Implement readv() fop
    
    Change-Id: I4cc060710482de8633141170dd35f669f01f639b
    BUG: 1207615
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10528
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit fa0ad231745846918b2625d0e1a89c0a5c3c24dc
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Mar 11 14:20:48 2015 +0530

    libgfapi : anonymous fd support
    
    Anonymous fd's are floating fd assigned to a glusterfs client
    without a explicit file open. Here either it will create a new
    anonymous fd or existing anonymous fd in the client stack for
    requested file.The anonymous fd's are mainly used for IO's.
    This patch introduces two api's glfs_h_anonymous_read and
    glfs_h_anonymous_write which performs read and write respectively
    
    Change-Id: Id646f2220e8387b2f8bb244c848dc1db6761444f
    BUG: 1204651
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9971
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a5fc34604aef973606431bf7d873abb91ee03d5a
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Tue May 5 18:19:51 2015 +0530

    Cache-invalidation : set to on/off depending on ganesha.enable value
    
    Multi-Head NFS-Ganesha servers need upcall (cache-invalidation)
    support to notify them in case of any changes to the files in the backend.
    Hence, upcall xlator option "features.cache-invalidation" needs to be enabled
    when ganesha.enable is set to 'on'. Similarly, this feature needs
    to be disabled when ganesha.enable is set to 'off'
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    
    Change-Id: Ifdd1d50e48a2bd2a388f73c0b9e318c6092ac190
    BUG: 1213752
    Reviewed-on: http://review.gluster.org/10581
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 07f12e2830ab705828742ebeca7448462762c2b0
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Apr 23 22:57:39 2015 +0530

    api/libgfapi: Add support for statfs handle
    
    snapd feature require statfs fops and thereby
    handle of statfs
    
    Change-Id: I037ee846aee3971826a73c592e15f1be27796c64
    BUG: 1176837
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10356
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit f037d58f2f103f8b80f3827e049876607e764538
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 5 08:47:38 2015 -0400

    build: gluster-api-devel requires libacl-devel
    
    building libvirt fails
    
    Change-Id: I355879e6c6f56e49c4ee78e1a9763598acacd074
    BUG: 1218625
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10579
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 12069ef095d16668bd3a24daf370d7cdc1386369
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 5 08:48:01 2015 +0530

    cleanup: Unmount all fuse mounts
    
    Change-Id: I851b4bd74b595d739f7bf9eea920d07e31fa5fbc
    BUG: 1202244
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10540
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8965ac78bfd26e7f45c9579894191817afafa15e
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Apr 29 15:35:56 2015 -0400

    guster/dht: tiered volumes may not allow access to files undergoing migration
    
    If a read IO occurs against a file that has reached rebalance
    phase 2, we redirect the IO to the destination. For tiered
    volumes, when we try to reopen the file (on the destination),
    the lower level DHT receives the open call and fails; it does
    not have a "cached subvol". Fix is to "teach" the lower level
    DHT of the new location by sending a locate before the open.
    
    Change-Id: Ia4acb0035ff1da15f6a8f9ed54f43c76e8b98f5f
    BUG: 1214048
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Signed-off-by: root <root@gprfs018.sbu.lab.eng.bos.redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10324
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit dbaaacf720baedc7f94b3acb6a479db394f54f57
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Mon Apr 27 21:18:10 2015 +0530

    geo-rep: rename handling in dht volume
    
    Background:
    
    Glusterfs changelogs are stored in each brick, which records the changes
    happened in that brick. Georep will run in all the nodes of master and
    processes changelogs "independently".
    Processing changelogs is in brick level, but all the fops will be replayed
    on "slave mount" point.
    
    Problem:
    With a DHT volume, in changelog "internal fops" are NOT recorded.
    For Rename case, Rename is recorded in "hashed" brick changelog.
    (DHT's internal fops like creating linkto file, unlink is NOT recorded).
    This lead us to inconsistent rename operations.
    
    For example,
    Distribute volume created with Two bricks B1, B2.
    
    //Consider master volume mounted @ /mnt/master
    and following operations executed:
    cd /mnt/master
    touch f1 // f1 falls on B1 Hash
    mv f1 f2 // f2 falls on B2 Hash
    
    // Here, Changelogs are recorded as below:
    @B1
    CREATE f1
    @B2
    RENAME f1 f2
    
    Here, race exists between Brick B1 and B2, say B2 will get executed first.
    Source file f1 itself is "NOT PRESENT", so it will go ahead and create
    f2 (Current implementation).
    We have this problem When rename falls in another brick and
    file is unlinked in Master.
    
    Similar kind of issue exists in following case too(multiple rename):
    CREATE f1
    RENAME f1 f2
    RENAME f2 f1
    
    Solution:
    
    Instead of carrying out "changelogging" at "HASHED volume",
    carry out  at the "CACHED volume".
    This way we have rename operations carried out where actual files are present.
    So,Changelog recorded as :
    @B1
    CREATE f1
    RENAME f1 f2
    
    credit: sarumuga@redhat.com
    
    PS: Some of the races as the one below are _NOT_ fixed by this patch
    
    * f1 and f2 exist. B1 and B2 are their respective cached subvols. For
    both files hashed-subvol == cached-subvol
    * mv f1 f2 on master.
    * B1 has change-log entry of rename f1 f2
    * rebalance migrates f2 from B1 and B2
    * mv f2 f1 on master.
    * B2 has change-log entry of rename f2 f1
    
    Since changelog entries (rename f1 f2) and (rename f2 f1) are processed
    independently by gsyncds, which of either f1 and f2 survives on slave
    is subject to race. Note that on master its file f1 with name f1 which
    survived. On slave it can be either file f1 with name f1 or file f2
    with name f2 based on who wins the race of processing changelog.
    
    
    Change-Id: Iebc222f582613924c3a7cba37fb6d3e2d8332eda
    BUG: 1141379
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/10410
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a5fe0f594d41e1a11661d9074bb19e9c2e2c4776
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Sun May 3 12:41:40 2015 +0530

    dht/tier/rebalancer: Fix reset of tiering client pid
    
    In the patch http://review.gluster.org/#/c/9657
    the client pid set by tiering migration was getting over-
    written in dht_start_rebalance_task(). Just corrected it
    in dht_setxattr() before calling dht_start_rebalance_task()
    and removed it from dht_start_rebalance_task().
    
    Change-Id: I37cfa111f83a4e5d498042575c93799f60b49870
    BUG: 1217937
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10502
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 1306237c092ee8f927f16cae1b2b430a13e0a34f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Apr 24 15:33:25 2015 +0530

    tiering: Send both attach-tier and tier-start together
    
    After attaching tier, we have to start tier rebalance process.
    This patch is to trigger tier start along with attch-tier.
    
    Change-Id: I39380f95123f0087a82213ef263f9f33adcc5adc
    BUG: 1214222
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10363
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 3bbca6b368782b99b80558841894942f802a44a2
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon May 4 12:38:26 2015 -0400

    glusterd/tiering: disable tiering if cluster runs older gluster versions
    
    Do not allow attach or detach tier to work if any of the nodes
    is running gluster code < 3.7.
    
    Change-Id: Id9af8f4057f6fad9cb703ec7645bc01eccb11fc1
    BUG: 1218287
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10531
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 377505a101eede8943f5a345e11a6901c4f8f420
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Apr 28 16:26:33 2015 -0400

    cluster/tier: don't use hot tier until subvolumes ready
    
    When we attach a tier, the hot tier becomes the hashed
    subvolume. But directories may not yet have been replicated by
    the fix layout process. Hence lookups to those directories
    will fail on the hot subvolume. We should only go to the hashed
    subvolume once the layout has been fixed. This is known if the
    layout for the parent directory does not have an error. If
    there is an error, the cold tier is considered the hashed
    subvolume. The exception to this rules is ENOCON, in which
    case we do not know where the file is and must abort.
    
    Note we may revalidate a lookup for a directory even if the
    inode has not yet been populated by FUSE. This case can
    happen in tiering (where one tier has completed a lookup
    but the other has not, in which case we revalidate one tier
    when we call lookup the second time). Such inodes are
    still invalid and should not be consulted for validation.
    
    Change-Id: Ia2bc62e1d807bd70590bd2a8300496264d73c523
    BUG: 1214289
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10435
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit a197943463d3913707de56e3a1a9ef68bba5901f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue May 5 09:41:23 2015 +0200

    Tests: wworkaround NetBSD failures in cdc.t
    
    The volume reset network.compression operation cause brick processes to
    be restarted. If the volume is already started, a brick process is already
    there and the restart will fail, as the brick TCP port is already in use.
    
    Because the new brick process is not started, the volume is left with
    no brick online, and the volume stop operation will timeout waiting
    for bricks to stop.
    
    Obviosuly we have two bugs here
    - If volume reset network.compression needs to restart the bricks, it
      should first make sure the previous brick process is terminated
    - volume stop should not wait forever for bricks to come back online
    
    This change does not fix the bugs but just makes sure the volume
    is stoped before volume reset network.compression, so that the failure
    oes not happen.
    
    BUG: 1129939
    Change-Id: I9cd5cdc767ef6ee9dd31f2121d672dc3bfdce45f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10553
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 170cc4ea08aa48e69c2df6be5841076c9a119d5a
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Apr 30 13:28:44 2015 +0530

    Upcall: Send stat as part of cache_invalidation notifications
    
    Have added support to send attributes of both entries and
    its parent (include oldparent in case of RENAME fop) in the
    same notification request to avoid multiple rpc requests.
    
    Also, made changes in gfapi to send parent object and its
    attributes changed in a single upcall event.
    
    Change-Id: I92833da3bcec38d65216921c2ce4d10367c32ef1
    BUG: 1200262
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10460
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 08107796c89f5f201b24d689ab6757237c743c0d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Sun Apr 12 17:46:45 2015 +0530

    geo-rep: Minimize rm -rf race in Geo-rep
    
    While doing RMDIR worker gets ENOTEMPTY because same directory will
    have files from other bricks which are not deleted since that worker
    is slow processing. So geo-rep does recursive_delete.
    
    Recursive delete was done using shutil.rmtree. once started, it will
    not check disk_gfid in between. So it ends up deleting the new files
    created by other workers. Also if other worker creates files after one
    worker gets list of files to be deleted, then first worker will again
    get ENOTEMPTY again.
    
    To fix these races, retry is added when it gets ENOTEMPTY/ESTALE/ENODATA.
    And disk_gfid check added for original path for which recursive_delete is
    called. This disk gfid check executed before every Unlink/Rmdir. If disk
    gfid is not matching with GFID from Changelog, that means other worker
    deleted the directory. Even if the subdir/file present, it belongs to
    different parent. Exit without performing further deletes.
    
    Retry on ENOENT during create is ignored, since if CREATE/MKNOD/MKDIR
    failed with ENOENT will not succeed unless parent directory is created
    again.
    
    Rsync errors handling was handling unlinked_gfids_list only for one
    Changelog, but when processed in batch it fails to detect unlinked_gfids
    and retries again. Finally skips the entire Changelogs in that batch.
    Fixed this issue by moving self.unlinked_gfids reset logic before batch
    start and after batch end.
    
    Most of the Geo-rep races with rm -rf is eliminated with this patch,
    but in some cases stale directories left in some bricks and in mount
    point we get ENOTEMPTY.(DHT issue, Error will be logged in Slave log)
    
    BUG: 1211037
    Change-Id: I8716b88e4c741545f526095bf789f7c1e28008cb
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10204
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cfa6c85334fd62175aa114d779873b6790d6db8a
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Mar 11 12:20:38 2015 +0530

    rdma:properly handle iobuf_pool when rdma transport is unloaded
    
    We are registering iobuf_pool with rdma. When rdma transport is
    unloaded, we need to deregister all the buffers registered with
    rdma. Otherwise iobuf_arena destroy will fail.
    
    Also if rdma.so is loaded again, then register iobuf_pool with
    rdma
    
    Change-Id: Ic197721a44ba11dce41e03058e0a73901248c541
    BUG: 1200704
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9854
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit f4679a70d87a4ed1564d82c34742fe2817b33ff7
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 28 10:24:28 2015 -0400

    build: Autogenerated files delivered in dist tarball
    
    Change-Id: I99028fe6ff4547f837b0997543234a9020b75607
    BUG: 1216067
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10429
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ed9e9c3b1867867a828020b8569c0c7ab1d3be24
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Sat Apr 11 01:03:13 2015 +0530

    glusterd: Coverity fix
    
    CID: 1293504 (Calling xlator_set_option without checking return value )
    
    CID: 1293502 (Dereferencing a pointer that might be null xl when calling
                  xlator_set_option)
    
    CID: 1293500 (Assigning value from dict_get_int32(dict, "type", &type)
                  to ret here, but that stored value is overwritten before
                  it can be used.)
    
    Change-Id: I5314fb399480df70bd77bc374e3b573f2efd5710
    BUG: 1093692
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10201
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 466289f75522c7e6662ccfd17cbe2f000667f77e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Apr 30 14:14:14 2015 +0530

    snapshot/scheduler: Use os.path.realpath() for path validation
    
    In order to accomodate systems, where /var/run is a symlink to
    /run, we are using os.path.realpath() for path validations.
    
    Change-Id: I4eae536867ec6c88f92c762b92f5c1966b622bde
    BUG: 1216931
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b7da3d569dfa6d6c27480a74a345cf0e166e3fef
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue May 5 10:07:13 2015 +0530

    doc: AFR arbiter volume usage
    
    Contains information on creation and behaviour of replica 3 arbiter volumes.
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    
    Change-Id: I6af4aa3488649686fdb9b839c733046160e0785b
    BUG: 1199985
    Reviewed-on: http://review.gluster.org/10541
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 9ddea81a3b6f557c899c90ec84ac8463616e0bc5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 5 08:31:39 2015 +0530

    tests: Unmount aux quota mount
    
    Change-Id: Ie4ec40230e6b92d2e694b804a991246050b5fa51
    BUG: 1202244
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10539
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Sachin Pandit <spandit@redhat.com>

commit 98b69412e92742e0638ef8bd76223671386f5a39
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Mar 12 16:07:13 2015 +0530

    geo-rep: Status Enhancements
    
    Discussion in gluster-devel
    http://www.gluster.org/pipermail/gluster-devel/2015-April/044301.html
    
    MASTER NODE - Master Volume Node
    MASTER VOL - Master Volume name
    MASTER BRICK - Master Volume Brick
    SLAVE USER - Slave User to which Geo-rep session is established
    SLAVE - <SLAVE_NODE>::<SLAVE_VOL> used in Geo-rep Create command
    SLAVE NODE - Slave Node to which Master worker is connected
    STATUS - Worker Status(Created, Initializing, Active, Passive, Faulty,
             Paused, Stopped)
    CRAWL STATUS - Crawl type(Hybrid Crawl, History Crawl, Changelog Crawl)
    LAST_SYNCED - Last Synced Time(Local Time in CLI output and UTC in XML output)
    ENTRY - Number of entry Operations pending.(Resets on worker restart)
    DATA - Number of Data operations pending(Resets on worker restart)
    META - Number of Meta operations pending(Resets on worker restart)
    FAILURES - Number of Failures
    CHECKPOINT TIME - Checkpoint set Time(Local Time in CLI output and UTC
                      in XML output)
    CHECKPOINT COMPLETED - Yes/No or N/A
    CHECKPOINT COMPLETION TIME - Checkpoint Completed Time(Local Time in CLI
                                 output and UTC in XML output)
    
    XML output:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    cliOutput>
      geoRep>
          volume>
            name>
            sessions>
              session>
                 session_slave>
                 pair>
                    master_node>
                    master_brick>
                    slave_user>
                    slave/>
                    slave_node>
                    status>
                    crawl_status>
                    entry>
                    data>
                    meta>
                    failures>
                    checkpoint_completed>
                    master_node_uuid>
                    last_synced>
                    checkpoint_time>
                    checkpoint_completion_time>
    
    BUG: 1212410
    Change-Id: I944a6c3c67f1e6d6baf9670b474233bec8f61ea3
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10121
    Tested-by: NetBSD Build System
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e02ac3c28241ff004d6cfbfc03975822146ce5dd
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Apr 10 13:05:02 2015 +0530

    doc/snapshot: doc for snapshot clone
    
    Change-Id: Ie53e6ab780ab67ffe0c4f6d92fe4c0b779cec2c9
    BUG: 1199894
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10187
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit c79e03ecd3cd9f2ffad52fad983b32133d8af787
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 13 11:56:35 2015 +0530

    doc/geo-rep: Doc changes w.r.t common shared gluster meta volume
    
    Change-Id: I71c466537a191caa5c5a4a11e67df384c24c73ef
    BUG: 1210344
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10447
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 41c3c1c1e4ccc425ac2edb31d7fa970ff464ebdd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 5 07:57:10 2015 +0530

    doc: Feature doc for shard translator
    
    Source: https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20
    
    Change-Id: I127685bacb6cf924bb41a3b782ade1460afb91d6
    BUG: 1200082
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10537
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 25e8e74eb7b81ccd114a9833371a3f72d284c48d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Apr 15 22:22:08 2015 +0530

    afr: add arbitration support
    
    Add logic in afr to work in conjunction with the arbiter xlator when a
    replica 3 arbiter volume is created. More specifically, this patch:
    
    * Enables full locks for afr data transaction for such volumes.
    * Removes the upfront marking of pending xattrs at the time of pre-op
      and defer it to post-op. (This is an arbiter independent change and is made for all afr transactions.)
    * After pre-op stage, check if we can proceed with the fop stage without
      ending up in split-brain by examining the changelog xattrs.
    * Unwinds the fop with failure if only one source was available at the
       time of pre-op and the fop happened to fail on particular source brick.
    * Skips data self-heal if arbiter brick is the only source available.
    * Adds the arbiter-count option to the shd graph.
    
    This patch is a part of the arbiter logic implementation for 3 way AFR
    details of which can be found at http://review.gluster.org/#/c/9656/
    
    Change-Id: I9603db9d04de5626eb2f4d8d959ef5b46113561d
    BUG: 1199985
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10258
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6d7428d2018c061ca2791443bd90980f9755ded3
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Thu Mar 5 13:41:10 2015 +0530

    mgmt/glusterd: Porting messages to new logging framework
    
    Change-Id: I25f3536446798ea1cffd6b5dfbb3d2398766fcf3
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9808
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit e6f2472d2434ab43a30720ef4de2e0abc0a3f4ac
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 27 01:20:02 2015 +0530

    libglusterfs: Fix cluster_entrylk retry
    
    Change-Id: I92ff46bae36d39a449d4bbaedc88a322992f65eb
    BUG: 1215265
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10391
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit c8cd488b794d7abb3d37f32a6d8d0a3b365aa46e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Mar 31 23:07:09 2015 +0530

    cluster/ec: Fix dictionary compare function
    
    If both dicts are NULL then equal. If one of the dicts is NULL but the other
    has only ignorable keys then also they are equal. If both dicts are non-null
    then check if for each non-ignorable key, values are same or not.  value_ignore
    function is used to skip comparing values for the keys which must be present in
    both the dictionaries but the value could be different.
    
    geo-rep's stime xattr doesn't need to be present in list xattr but when
    getxattr comes on stime xattr even if there aren't enough responses with the
    xattr we should still give out an answer which is maximum of the stimes
    available.
    
    Change-Id: I8de2ceaa2db785b797f302f585d88e73b154167d
    BUG: 1207712
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10078
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 582b252e3a418ee332cf3d4b1a415520e242b599
Author: Ashish Pandey <aspandey@redhat.com>
Date:   Thu Apr 9 17:27:46 2015 +0530

    cluster/ec: Use fd instead of loc for get_size_version
    
    Change-Id: Ia7d43cb3b222db34ecb0e35424f1766715ed8e6a
    BUG: 1188242
    Signed-off-by: Ashish Pandey <aspandey@redhat.com>
    Reviewed-on: http://review.gluster.org/10176
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2d3bfc6b53974c80c347d1285b6a5a7cd60d7a13
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon May 4 14:19:36 2015 +0530

    snapshot/uss: fix regression failure in bug-1162498.t
    
    .snaps seems to take some time, before it is available based
    on the state of the system. Using EXPECT_WITHIN instead of TEST
    to check the contents of .snaps, hence giving it some time to
    come up.
    
    Change-Id: Iac166500d5a09ba8bab00d994c27a9ad0a01b9c3
    BUG: 1218120
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10518
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 80972fd5923b05f3bddd57c5b98dc5a53e9d1edf
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon May 4 17:49:16 2015 -0400

    tests: fix failures due to not unmounting $M2 (/mnt/glusterfs/2)
    
    Our failure to unmount meant that both mkdir and rmdir would fail in
    cleanup().  Because one of those mkdirs was the last thing cleanup()
    executed, it would fail, so the test would fail, so the entire
    regression run would fail.  The fix has two parts.
    
    (1) Unmount the offending directory.
    
    (2) Make sure cleanup() returns success even if that last mkdir
        failed.
    
    That might keep us from consistently blowing up regression runs on the
    very first tests (basic/afr/data-self-heal.t) that we execute.
    
    Change-Id: I7a9761bd28761a5ee2face3db8112e9c3f6c5dc8
    BUG: 1163543
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10536
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0b14edfc6974161b25a11cd683d164aa337c6122
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Apr 29 08:05:21 2015 +0530

    rpc: Included necessary stats in 'gfs3_cbk_cache_invalidation_req'
    
    To avoid extra network fops, it will benifit clients if the server
    can send the updated stat of the file/dir and of the parent directory
    (including oldparent in case of RENAME fop) while sending
    GF_CBK_CACHE_INVALIDATION upcall event.
    This patch handles rpc protocol changes.
    
    Change-Id: Ic096a61c4d24a8d75a8285be78deb237d7ef9484
    BUG: 1200262
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10452
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 86fb4828f5566e455a12ac2207999120275b61a7
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Apr 22 15:48:52 2015 +0530

    Upcall: Cleanup expired client entries
    
    To cleanup expired client entries (with access_time > 2*CACHE_INVALIDATION_TIMEOUT),
    have
            * defined a global list to contain all the upcall_inode_ctx allocated
            * Every time a upcall_inode_ctx is allocated, it is added to the global list
            * during inode_forget, that upcall_inode_ctx is marked for destroy
            * created a reaper thread which scans through that list
                    * cleans up expired client entries
                    * frees the inode_ctx with destroy_mode set.
    
    Note: This reaper thread is initialized only when features.cache_invalidation option
    is enabled.
    
    Change-Id: Iea2a63eb31b8e08d5709e7e090cf26fd13d01265
    BUG: 1200267
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10342
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit f8bb9ac26aad8c0068bcc45a34ecb4a73cc06e7a
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Apr 22 22:34:41 2015 +0530

    gfapi: Skip and delete the upcall entry if not found
    
    We could run into situations where in gfapi received a upcall
    notification for a file and the file may have got deleted by then.
    Hence, incase of error while trying to create handle from gfid,
    log it, delete the entry and return with CBK_NULL reason.
    
    Change-Id: I191f10f44d6804be07734a6be63a3ca08f455f0e
    BUG: 1213773
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10341
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 21515b3331d8d72011fef79008bcaff8ca43647a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 14 14:42:46 2015 +0530

    feature/changelog: Capture path for deletes
    
    PROBLEM:
    There is no way to get the path of deleted file if we
    have gfid from changelog since the file is already deleted.
    
    SOLUTION:
    Do a recursive readlink on parent gfid in backend .glusterfs
    path to get the complete path in I/O callpath in changelog
    translator and capture it in callback.
    
    The path captured is relative from the brick root. The field
    separator used is '\0'.
    e.g.,
    ......\0<pgfid>/bname\0<relative-path>\0<next-record>
    
    ADDITIONAL REQUIRED CHANGES:
    
    1. The changelog translator option called "changelog.capture-del-path"
       is introduced to enable or disable the capturing of deleted entry
       path.
       e.g.,
       gluster vol set <vol-name> changelog.capture-del-path on/off
    
       If capture-del-path is disabled, '\0' is captured instead of
       relative path.
       e.g.,
       ......\0<pgfid>/bname\0\0\0<next-record>
    
    2. The minor number in the version of changelog is bumped up from v1.1
       to v1.2.
    
    3. If recursive readlink is failed for some reason, it will capture
       \0 in place of <relative path>.
       e.g.,
       ......\0<pgfid>/bname\0\0\0<next-record>
       (same as when caputre-del-path option is disabled)
    
    4. If bname argument passed to "resolve_pargfid_to_path" function
       is NULL and pargfid is ROOT, "." is returned. This is not the
       case with changelog, where bname is always passed. This is
       applicable to other consumers of "resolve_pargfid_to_path"
       routine.
    
    NOTE:
       Changelog parser should consider the above new changes
       and should parse accordingly.
    
    Change-Id: I040ed429b5aa7d391033fc6a540edbf07fc37827
    BUG: 1214561
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10288
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: NetBSD Build System

commit 2aceadae902e6f45e02afa62ee7831479d23b4a5
Author: anand <anekkunt@redhat.com>
Date:   Tue Apr 28 22:42:14 2015 +0530

    glusterd: Enable readdir-ahead by default on new volumes
    
    With gluster-3.7, 'performance.readdir-ahead' will be enabled by default on
    new volumes when the cluster op-version supports it.
    
    Change-Id: I44e76a69e7d1c11e6dfad72c941caf887bb810ee
    BUG: 1216187
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10433
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 6a898e9e294bc4c254bb2c29e0514dbe5a81226c
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon May 4 17:01:18 2015 +0530

    Upcall: Feature doc for Upcall infrastrucutre
    
    Change-Id: I802ba2f13fde6c05da1ed355e340f071e9d20d30
    BUG: 1200262
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10525
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dc0020c72d5c2d20328b89224b149ebb87002277
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 24 17:31:03 2015 +0530

    rpc: Maintain separate xlator pointer in 'rpcsvc_state'
    
    The structure 'rpcsvc_state', which maintains rpc server
    state had no separate pointer to track the translator.
    It was using the mydata pointer itself. So callers were
    forced to send xlator pointer as mydata which is opaque
    (void pointer) by function prototype.
    
    'rpcsvc_register_init' is setting svc->mydata with xlator
    pointer. 'rpcsvc_register_notify' is overwriting svc->mydata
    with mydata pointer. And rpc interprets svc->mydata as
    xlator pointer internally. If someone passes non xlator
    structure pointer to rpcsvc_register_notify as libgfchangelog
    currently does, it might corrupt mydata. So interpreting opaque
    mydata as xlator pointer is incorrect as it is caller's choice
    to send mydata as any type of data to 'rpcsvc_register_notify'.
    
    Maintaining two different pointers in 'rpcsvc_state' for xlator
    and mydata solves the issue.
    
    Change-Id: I7874933fefc68f3fe01d44f92016a8e4e9768378
    BUG: 1215161
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10366
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 9e6b521cc98b3ba099c1713639be9180be5b031f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Apr 28 19:17:40 2015 +0530

    tiering/cli: Check replica count and bricks are proper or not
    
    Right now, attach-tier calls parsing function for add-brick.
    Add-brick does not have any check for brick count and replca
    count compatibility.
    
    Change-Id: I44ec13eadffc003a9ebf8c4eb0193df559933a68
    BUG: 1215122
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10428
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 821b1fdc893c0dd603d4c43a0b31f1ea495a46c9
Author: vmallika <vmallika@redhat.com>
Date:   Wed Apr 15 17:35:07 2015 +0530

    quota: support for inode quota in quota.conf
    
    Currently when quota limit is set, corresponding gfid
    is set in quota.conf. This patch supports storing
    inode-quota limits in quota.conf and also stores
    additional byte for each gfid to differentiate
    between usage quota limit and inode quota limit.
    
    Change-Id: I444d7399407594edd280e640681679a784d4c46a
    BUG: 1202244
    Signed-off-by: vmallika <vmallika@redhat.com>
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/10069
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 40df2ed4d098d4cd2c6abbed23e497ac3e2e5804
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Apr 15 13:30:34 2015 +0530

    glupy: package glupy as a subpackage under gluster namespace
    
    Currently glupy files resides in gluster namespace of python site packages.
    The other projects like libgfapi-python ..etc are evolving and need to share
    the gluster namespace. The current structure makes things difficult as all
    subpackages have its own __init__ files and other files.
    One subpackage can not any more own gluster namespace.
    
    The attempt is to make below structure for gluster namespace so that
    it is more portable and scalable for future use.
    
      <sitepackages>/gluster/
                             |
                             -- __init__.py
                             |
                             |
                             -- glupy
                                     |
                                     -- __init__.py
                                     -- glupy.py
                                     -- ........
                             |
                             |
                             -- gfapi
                                     |
                                      -- __init__.py
                                      -- gfapi.py
                                      -- ........
    
    By above structure clients can import:
    
     >>> from gluster import glupy
     >>> from gluster import gfapi
    
    libgfapi-python project has been moved to this structure via
    
    http://review.gluster.org/#/c/9668/
    
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    
    Change-Id: I54886200ddb6a4153a74d9e187aeca7cad79ef9e
    BUG: 1211900
    Reviewed-on: http://review.gluster.org/10248
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 02223349a0a141d5bd09edcd571a703bb2e5a94d
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 28 18:09:29 2015 +0530

    geo-rep: Fix ignoring geo-rep safe errors
    
    Fix ignoring geo-rep safe errors in fuse layer
    and also ignore logging in client translator
    for mknod. Though it is rare, to happen with
    mknod, it might happen with history crawl on
    overlapping changelogs replay.
    
    Change-Id: I7e145cd1dc53f04d444ad2e68e66e648be448e61
    BUG: 1210562
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10422
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 20353cc323704292753ea6b7b0034362109fef76
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Apr 28 14:40:27 2015 +0530

    tools/glusterfind: New option to pre --regenerate-outfile
    
    When pre command is run twice, it overwrites the outfile.
    Now pre command will fail when executed twice. To force the
    regeneration use --regenerate-outfile
    
    Change-Id: I0cf7a139522812ece4decdfbcba667a05ce5c35e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1207028
    Reviewed-on: http://review.gluster.org/10418
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit da1416051d19d612d131acfde8589bc8658979b5
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Thu Apr 9 15:36:20 2015 +0530

    glusterd: gluster volume status should show status of bitrot and scrubber daemon
    
    Command gluster volume status <VOLNAME> should show the status of bitrot
    and scrubber daemon and its pid information.
    
    Along with displaying bitrot and scrubber daemon information in gluster
    volume status command there should be command to show its individual status
    separately.
    Command to show individual status of bitrot and scrubber daemon will
    following.
    
    command to show only bitd daemon information will be
    gluster volume status <VOLNAME> bitd
    
    command to show only scrubber daemon information
    gluster volume status <VOLNAME> scrub
    
    Change-Id: Id86aae1156c8c599347c98e2a538f294d37376e4
    BUG: 1209752
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10175
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 7759748915485d6c740a7fed831376f298eb90bb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 1 11:01:15 2015 +0530

    tests: Check aux umount is unmounted for quota tests
    
    Change-Id: If57d08f3446755ea41f66ca258efcc8ea5a89063
    BUG: 1217701
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10480
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c7bf5633276ee78e32ff79e5c0815b3f51e39500
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Apr 30 13:25:39 2015 +0530

    dht: Add a null check before freeing dir_dfmeta and tmp_container
    
    Change-Id: Ifbba6f340adfe2b4e3ad07260fbf4a25698ad8df
    BUG: 1217949
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/10459
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 3527c6a7dfe435c3b6b8d89a325ae0603f2c08a1
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Apr 27 15:00:36 2015 +0200

    tier: relax libgfdb required version number
    
    When calling dlopen() for libgfdb, do not specify the library version
    number "libgfdb.so.0.0.1", since libtool will not always create libraries
    or link with that name with the full 3-digit version. For instance on
    NetBSD only up to the 2-digit version is available and "libgfdb.so.0.0.1"
    does not exist.
    
    Instead, just specify "libgfdb.so" and rely on smymlinks installed by
    libtool to find the relevant library.
    
    BUG: 1129939
    Change-Id: I074b1009d3622a122fdaeb4b99658bca3277e211
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10407
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f81deb95db417eeededf7442a30304a880cc8169
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Thu Apr 23 18:44:30 2015 +0530

    features/bitrot: Per volume bitrot translator
    
    Currently whatever bitrot/scrubber tunable value user set for one
    volume that value is considering for all other volumes also.
    Each volume should act on their respective bitrot/scrubber tunable
    value.
    
    For handling bitrot/scrubber tunable value independently with respect
    to all the volume bitrot and scrubber translator should run seperatly
    for each volume.
    
    Change-Id: I1d9379508afe6cfd2f78e3ebf29c829c362d84a9
    BUG: 1170075
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10352
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 7c4d103700f0bbe0c5e134f743a68f370e5600be
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 1 20:12:50 2015 +0530

    tests: Fix spurious failures
    
    - Use REBALANCE_TIMEOUT in EXPECT_WITHIN
    - Use fdatasync to prevent write-behind from giving success
    - Add logfile to glupy
    
    Change-Id: I51ab51644aaa4aa9d49f185e7b8959bb58be966b
    BUG: 1217766
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10487
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cff5db814ee31b556d321f7421cdb3fccc8c629d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Apr 28 18:51:38 2015 +0530

    features/shard: Add "is-directory" checks in stat/fstat
    
    During mount, NFS directly calls stat on the root of the volume
    without sending a lookup on it. This was causing inode_ctx_get_block_size()
    to fail on /. A check is now added in [f]stat which would ensure no action
    is taken by shard xlator when the operation is on a directory.
    
    Change-Id: I81849eeddfdad9f271155442408d95b4a25d7647
    BUG: 1207615
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10427
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5388706e8431114418c0335f24532bf9f8df7588
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun May 3 15:07:56 2015 +0200

    rpm: fix dependency on python-gluster
    
    The glusterfs-extra-xlators tries to install python-glusterfs. This is
    incorrect, the package is called python-gluster.
    
    BUG: 1211848
    Change-Id: Id48a63ebe893c2bab90fab37ea3e32e601fae0fa
    Reported-by: Meni Yakove <myakove@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10508
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dfa3942f67e11ce0bef0975173f63932b0db3143
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Apr 30 11:34:14 2015 +0530

    Upcall: Handle missing fops in the upcall xlator
    
    Change-Id: I968980dc4df458ec427e33503363bbd017e1163e
    BUG: 1200271
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10194
    Tested-by: NetBSD Build System
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit deedac1101c109895c9aff8e7a1171bea16a6d5e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 1 21:51:09 2015 +0530

    tests: Disable flush behind so that file will be closed
    
    Change-Id: I97eb8d236448e8783f09b4922aa465a2b1b3979b
    BUG: 1217788
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10488
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 275f7244ff9bfae085cfc8ee103990100e41057f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Apr 13 20:28:21 2015 +0530

    features/changelog: Consider only changelog on/off as changelog breakage
    
    Earlier, both chagelog on/off and brick restart were considered
    to be changelog breakage and treated as changelog not being
    continuous. As a result, new HTIME.TSTAMP file was created on
    both the above cases. Now the change is made such that only
    on changelog enable/disable, the changelog is considered to be
    discontinuous. New HTIME.TSTAMP file is not created on brick
    restart, the changelogs files are appended to last HTIME.TSTAMP
    file.
    
    Treating changelog as continuous in above scenario is important
    as changelog history API will fail otherwise. It can successfully
    get changes between start and end timestamps only when changelog
    is continuous (Changelogs in single HTIME.TSTAMP file are treated
    as continuous). Without this change, changelog history API would
    fail, and it would become necessary to fallback to other mechanisms
    like xsync FSCrawl in case geo-rep to detect changes in this time
    window. But Xsync FSCrawl would not be applicable to other
    consumers like glusterfind.
    
    Rationale:
    1. In plain distributed volume, if brick goes down, no I/O can
       happen onto the brick. Hence changelog is intact with data
       on disk.
    2. In distributed replicate volume, if brick goes down, since
       self-heal traffic is captured in changelog. Eventually,
       I/O happened whend brick down is captured in changelog.
    
    Change-Id: I2eb66efe6ee9a9228fb1fcb38d6e7696b9559d5b
    BUG: 1211327
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10222
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit 5f349f3f0cdc088d2908be0af2c4f1dfa94029e2
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Apr 29 12:09:26 2015 +0530

    features/shard: Take hole size into account while computing ia_size
    
    Change-Id: I1a90ad6669c1cb79aaae6b4bd9621c75d9985c8a
    BUG: 1207615
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10446
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 34833364e9839f0036bccd58ec0a8a963e69263e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Apr 24 17:07:37 2015 +0200

    protocol: increase default group-cache-timeout to 300 seconds
    
    sssd uses 300 seconds by default too. There is no need to overload sssd
    with requests that it would have cached.
    
    BUG: 1215187
    Change-Id: I3f04ea8cc90180d863253a9f46d62b71810a7b34
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10371
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3fe0c3c50eba9b64ebdd2abf0e8491d87078a440
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Apr 30 12:02:28 2015 +0530

    geo-rep: Fix minor bugs in meta-volume setup
    
    1. Access unreferenced access of fd:
           In meta volume configuration for geo-rep, if
       geo-rep directory is not created yet, open fails
       with no fd, but it is accessed in close(fd). So
       after creating 'geo-rep' directory in meta-volume,
       open the lock file to get fd.
    
    2. Fix volume_id in forming lock file name.
           For the very first time, gconf.volume_id would
       be null, as config is not reloaded yet. Hence, use
       'uuid' function to get the volume id.
    
    Change-Id: I8381ab7a44bc800df25d596218466641c10937a4
    BUG: 1210344
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10458
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: NetBSD Build System

commit 4d118cb5ee99b8401d70678fc3b3576ad938999d
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Apr 9 15:07:54 2015 +0530

    ctr/libgfdb: Performance enhancer for unlink/create/rename/link fops
    
    1) ctr_link_consistency option for ctr xaltor is provided so that
       the user can choose to switch it on or off.
       /* For link consistency we do a double update i.e mark the link
       * during the wind and during the unwind we update/delete the link.
       * This has a performance hit. We give a choice here whether we need
       * link consistency to be spoton or not using link_consistency flag.
       * This will have only one link update */
    
    2) In delete the wind time recording is moved to unwind path.
       /* Special performance case:
       * Updating wind time in unwind for delete. This is done here
       * as in the wind path we will not know whether its the last
       * link or not. For a last link there is not use to update any
       * wind or unwind time!*/
    
    Change-Id: I209472fb816f939db4a868b97ba053b028f17ea6
    BUG: 1217786
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10170
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cfb9ea4dc68440a18b7f07422901a715b00776f0
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Apr 30 16:54:16 2015 +0530

    glusterd/quota/tiering: Fixing volgen of quotad
    
    The quotad's graph generation was happening wrongly for
    tiered volume. The check is been inserted.
    
    Change-Id: I5554bc5280b0fbaec750e9008fdd930ad53a774f
    BUG: 1214219
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10474
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 82d78fa3181dff0969ca3b24e2e071ab2b8064d4
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Apr 16 12:30:16 2015 +0530

    dht/rebalancer: Marking tiering migration fops
    
    This is a follow up patch for http://review.gluster.org/#/c/10080
    In the above, the suggested change in
    http://review.gluster.org/#/c/10080/7/xlators/cluster/dht/src/dht-rebalance.c
    doesnot work. The reason it doesnt work is promotion and demotion are done in
    a multithread way. Whenever a promotion or demotion thread is called, the frame
    of the old sync_op thread is not carried with it. As a result the frame->root->pid
    is not set.
    
    Solution:
    When the file is getting migrated, we get a tiering.migration key_value in the
    xattr dict, so that we pass  this dic key-value when we do syncop_setxattr()
    to do  data migration and set the frame->root->pid GF_CLIENT_PID_TIER_DEFRAG
    in dht_setxattr() just before calling dht_start_rebalance_task().
    
    Change-Id: I86fef2d961b32fdd2c0c69d8512cbe846b393404
    BUG: 1194753
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10266
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ee9b35a780607daddc2832b9af5ed6bf414aebc0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Apr 28 11:53:33 2015 +0200

    nfs: fix spurious failure in bug-1166862.t
    
    In some environments, "showmount" could return an NFS-client that does
    not start with "1". This would cause the test-case to fail. The check is
    incorrect, the number of lines should get counted instead.
    
    Also moving the test-case to the .../nfs/... subdirectory.
    
    BUG: 1166862
    Change-Id: Ic03aa8145ca57d78aea01564466e924b03bb302a
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10419
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7d7b80efe8c745f3ff7de76fc31c4977098cae01
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Tue Feb 3 13:17:04 2015 +0530

    changelog: Fixing buffer overrun coverity issues.
    
    Coverity IDs:
    1214630
    1214631
    1214633
    1234643
    
    Change-Id: I172c4f49bf651b2324522f9e661023f73ca05339
    BUG: 789278
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9557
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sakshi Bansal
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 508eb854f3f94f52d4ebd050f3e45deb9cfa90c8
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Apr 27 12:33:06 2015 +0530

    cli/tiering : Parse detach-tier command properly
    
    gluster detach-tier help should show the usage of
    detach-tier command properly.
    
    Also, instead of force option, if any other was given,
    then the command should fail with a usage message
    
    Change-Id: Ie801529176db067c98fd1bfada056cbc647973fb
    BUG: 1211570
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10303
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit cf1c53343d4b6fe834833b76c50c61fd8a312de0
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Apr 15 12:29:16 2015 +0530

    build: Introducing  python-gluster package
    
    Currently the gluster namespace/module is owned by glusterfs-api rpm.
    Because of this, other packages (extra-xlators or libgfapi-python)
    have to depend on glusterfs-api to get the gluster namespace. The gluster
    namespace should be owned by a core package.This patch introduce new package
    called python-gluster and moves the ownership of gluster module
    to python-gluster.
    
    Change-Id: Ib75ab922736f3bea6355da4d8dbec3a08b2844d5
    BUG: 1211848
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10244
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 664d2d243deb132dd5daad0280ae9fa2406ca26a
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Apr 14 04:03:36 2015 +0530

    Upcall: Replaced opaque gfid with string in rpc cbk args
    
    For GF_CBK_CACHE_INVALIDATION, have changed the type of gfid
    to be string (cannonical form) instead of opaque byte format
    to ensure correctness across platforms supporting different
    endianness.
    
    BUG: 1200262
    Change-Id: Iac4372714f4b4ebcd9c4393aaf46ceba3f37f587
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10224
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2bf85951c6c25aa17acc591fabc3b3927b6dc82f
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Mar 30 16:56:59 2015 +0530

    Upcall: Process each of the upcall events separately
    
    As suggested during the code-review of Bug1200262, have modified
    GF_CBK_UPCALL to be exlusively GF_CBK_CACHE_INVALIDATION.
    Thus, for any new upcall event, a new CBK procedure will be added.
    
    Also made changes to store upcall data separately based on the
    upcall event type received.
    
    BUG: 1200262
    Change-Id: I0f5e53d6f5ece16aecb514a0a426dca40fa1c755
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10049
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 288e02853d913b96e4d6bce9afb16da7d891546f
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Fri Apr 17 10:56:57 2015 +0530

    NFS-Ganesha: Handling CLI commands when NFS-Ganesha keys are set
    
    When ganesha.enable is set to on and features.ganesha is
    enabled, there are a few behaviour changes that should
    be seen in other volume operations.
    
    1. ganesha.enable can be set to 'on' only
    when features.ganesha is set to 'enable'
    
    2.When gluster vol is started, and if ganesha.enable
    key was set to 'on', it should automatically export the volume
    via NFS-Ganesha.
    
    3.When ganesha.enable is set to 'on', and a volume
    is stopped, that volume should be unexported via NFS-Ganesha.
    
    4. gluster vol reset <volname>
    If ganesha.enable was set to on, then unexport the
    volume via NFS-Ganesha.
    
    5. gluster vol reset all
    If features.ganesha is set to enable, as part
    of reset all, set it to disable. This translates
    to teardown cluster.
    
    All the above problems are fixed by checking the global key
    and value, depending on the value, specific functions are called.
    And also, functions related to global commands
    are moved to cli-cmd-global.c
    
    Commit phase of features.ganesha enable/disable
    runs the ganesha-ha.sh setup/teardown respectively.
    Before the script begins, it is important that the
    NFS-Ganesha service starts on all the HA nodes.
    Having the start service commands in the
    commit phase could lead to problems.
    Moving the pre-requisite service start
    commands to the 'stage' phase.
    
    Change-Id: I5a256f94f8e1310ddcd5369f329b7168b2a24c47
    BUG: 1200265
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/10283
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 0c5910a39b8daad2b131c1f7f48b0bf3b8f46030
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sun Apr 26 16:25:08 2015 +0530

    features/bitrot: Use global timer wheel
    
    Change-Id: I761927ea263b4144b851881f25791fda5b794f59
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10381
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cb8ce71560a496db5392d322b7cc663054a8457a
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Tue Apr 14 00:48:24 2015 +0530

    bitrot: Scrubber log should report 'bad' file detection as ALERT in log
    
    If scrubber detect any bad object by mismatching of checksum of scrubber
    and signer then log messages shold come as a Alert instead of warning.
    
    Change-Id: I075d80700cbe6182e525a04419a80ab18419ff91
    BUG: 1210687
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10226
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit a152fa7ad96053093b88a010bff20e48aa5e5b70
Author: vmallika <vmallika@redhat.com>
Date:   Tue Apr 28 12:52:56 2015 +0530

    quota: Validate NULL inode from the entries received in readdirp_cbk
    
    In quota readdirp_cbk, inode ctx filled for the all entries
    received.
    In marker readdirp_cbk, files/directories are inspected for
    dirty
    
    There is no guarantee that entry->inode is populated.
    If entry->inode is NULL, this needs to be treated as readdir
    
    Change-Id: Id2d17bb89e4770845ce1f13d73abc2b3c5826c06
    BUG: 1215550
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10416
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 7648c0de36c7927b588abc66734c5b94afb08c00
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed Apr 15 11:37:22 2015 +0530

    glusterd: do not pass volinfo in glusterd_svc_manager function
    
    On restarting of glusterd first it will start all the bricks present
    in the volume then it will start all the services. During starting of
    all the services it may pass volinfo as a NULL. It will cause Assert
    failure in glusterd_bitdsvc_manager function and will cause a glusterd
    crash.
    
    Change-Id: Ia14cf5022da88516cdd576eb2d1e0e7b17a3782b
    BUG: 1207029
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10241
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 6faf89f4179c452be20f02966b9722641938599d
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Sat Apr 11 17:05:45 2015 +0530

    glusterd: volume info should not show "feature.scrub: resume" if scrub resumed
    
    If bitrot is enable on the volume and if user paused the scrub process and then
    resume the scrub process then command #gluster volume info <VOLNAME> should show
    status of option features.scrub: Active.
    
    If bitrot is enable on the volume and user disable the bitrot on the volume then
    command #gluster volume info <VOLNAME> should show status of option
    features.scrub: Inactive.
    
    If bitrot is enable on the volume and user paused the scrub porcess then command
    gluster volume info <VOLNAME> should show the status of option
    features.scrub: pause.
    
    Change-Id: I55972eef3b8570b7cb05dc28700d4e28dc45a86a
    BUG: 1209818
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10207
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 0be5e3d7c580f77f3db0d4282d2ac81071ccd3f5
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Apr 29 12:02:05 2015 +0530

    snapshot/scheduler: Use shutil.move instead of os.rename()
    
    os.rename is a wrapper on top of the rename function,
    which fails with invalid cross-device link if /tmp
    is a tmpfs. Hence using shutil.move
    
    Change-Id: Ia026d2a810b725ccd398db895e612c53bc6a2f95
    BUG: 1214574
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10347
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 3d0c87a38802b0751c79ec0f11bb7f8972f417cd
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Apr 28 18:42:41 2015 +0530

    glusterd: Use uint32_t for peerinfo generation number
    
    Using a uint64_t for the peerinfo generation number was overkill for how
    the generation number is used within GlusterD. It also prevented
    GlusterD from running on 32-bit architechtures, as uatomic_add_return
    doesn't support 64-bit values on 32-bit architechtures.
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      b78dba4 Use 32-bit generation number
      2c37e4b Change other generation number variables to uint32_t
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: I0f310f56a4fb97d6bcbc23255a379ed5bb1ed9e1
    BUG: 1205186
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/10425
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 0d3759fa8b4c0ba1c2d747ab96b9fd2442488635
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Apr 29 21:03:39 2015 +0200

    build: glfsheal should link against $(UUID_LIBS)
    
    Without this, building fails on Debian Jessie:
    
        /usr/bin/ld: glfs-heal.o: undefined reference to symbol 'uuid_clear@@UUID_1.0'
        /lib/x86_64-linux-gnu/libuuid.so.1: error adding symbols: DSO missing from command line
        collect2: error: ld returned 1 exit status
        Makefile:503: recipe for target 'glfsheal' failed
    
    While at it, clean some of the unused defines too.
    
    BUG: 1206587
    Change-Id: I2e513b2a806e6241542e60007d720cca16dabb06
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10453
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit dc089a1a51988c2b407040e1684d7b0adbd79556
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Mar 11 20:11:09 2015 +0530

    protocol/server : port log messages to new framework.
    
    Change-Id: I7901f55d06716161cc31d2b79a600a16b5ec2ef8
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9874
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 00700a0d665fa18e28b6898b5fd09c34fc0150bc
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Apr 30 04:57:11 2015 +0200

    Fix ENOKEY build failure on non Linux systems
    
    ENOKEY is Linux specific, using it will fail the build on any other
    system. Proposed fix is to use EINVAL instead.
    
    BUG: 1129939
    Change-Id: I7bdcb8dbc55aa50760c46c0d2ed932083b3066ed
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10456
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 4306245aef7cdcbfa6d7a59dccd031d4ada54105
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Apr 29 11:38:11 2015 +0530

    rdma:  porting rdma to a new message id logging format
    
    Change-Id: I71e940817ae0a9378e82332d5a8569114fc13482
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9868
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit d28a99d6f20650e5d78accb1e16bd3721a2b6d02
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 14 08:17:10 2015 -0400

    common-ha: delete-node implementation
    
    omnibus patch consisting of:
    + completed implemenation of delete-node         (BZ 1212823)
    + teardown leaves /var/lib/nfs symlink           (BZ 1210712)
    + setup copy config, teardown clean /etc/cluster (BZ 1212823)
    
    setup for copy config, teardown clean /etc/cluster:
    1. on one (primary) node in the cluster, run:
      `ssh-keygen -f /var/lib/glusterd/nfs/secret.pem`
    
      Press Enter twice to avoid passphrase.
    
    2. deploy the pubkey ~root/.ssh/authorized keys on _all_ nodes, run:
      `ssh-copy-id -i /var/lib/glusterd/nfs/secret.pem.pub root@$node`
    
    3. copy the keys to _all_ nodes in the cluster, run:
      `scp /var/lib/glusterd/nfs/secret.*  $node:/var/lib/glusterd/nfs/`
      N.B. this allows setup, teardown, etc., to be run on any node
    
    Change-Id: I9fcd3a57073ead24cd2d0ef0ee7a67c524f3d4b0
    BUG: 1213933
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10234
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5b5048670c34df3f9eab9a6a3ab8eec288bd9d74
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 16 11:34:18 2015 +0530

    features/shard: Implement rename() fop
    
    Change-Id: Ia39fa0f29eac84c18d13a94f704b1703565b504e
    BUG: 1207615
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10373
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 797e923da9f5f1eca4a51da177b1a7cbef75b5ad
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Apr 18 18:40:55 2015 +0530

    tests: Await for graph switch before testing open fop count
    
    In performance/open-behind.t, a test for open fop reaching the brick is done by
    switching off open-behind and performing a read operation. If the read operation
    is performed before a graph switch, the read happens on the old graph and hence
    open does not get accounted in the brick.
    
    To overcome this EXPECT_WITHIN 10 seconds has now been added to ensure that a
    graph switch has happened. The read operation happens subsequently after the
    graph switch.
    
    Cleaned up a "No volumes present" message from stderr while doing this.
    
    Change-Id: I1e1c0d7e4bd2057520b4dd46157d18f30837b8c9
    BUG: 1213066
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10293
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 6bde16f7dc4a43d85e488f25ad679abfd24e72d1
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 26 23:49:56 2015 +0530

    dht: tackle thread race in dht_getxattr_cbk
    
    problem:
     1. When two threads execute in parallel in dht_getxattr_cbk
    it may so happen that, both may find local->xattr to be NULL. As
    a result dht_aggregate_xattr may not get executed.
    
     2. In dht_getxattr_cbk,
    
                 thread1                         thread2
    T1      this_call_cnt = 2 -1
    T2                                this_call_cnt = 1 - 1
    T3                                fills local_xattr
    T4                                DHT_STACK_UNWIND -> local_wipe
    T5      tries to dereference local
            which is already freed,
            leading to crash.
    
    Solution:
     for problem1: Execute critical section inside frame lock
    to resolve race.
    
     for problem2: Calculate this_call_count just before out section.
    
    Change-Id: I9827ac8fafebb0c733a4e4f3c710b752f1cd45fa
    BUG: 1215592
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/10389
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit b3a966c241b5d5b8117f06a4c744c18b6a59bb18
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Apr 12 15:55:02 2015 +0530

    rebalance: Introducing local crawl and parallel migration
    
    The current patch address two part of the design proposed.
    1. Rebalance multiple files in parallel
    2. Crawl only bricks that belong to the current node
    
    Brief design explanation for the above two points.
    
    1. Rebalance multiple files in parallel:
       -------------------------------------
    The existing rebalance engine is single threaded. Hence, introduced
    multiple threads which will be running parallel to the crawler. The
    current rebalance migration is converted to a "Producer-Consumer"
    frame work.
    
    Where Producer is : Crawler
          Consumer is : Migrating Threads
    
    Crawler: Crawler is the main thread. The job of the crawler is now
    limited to fix-layout of each directory and add the files which are
    eligible for the migration to a global queue in a round robin manner
    so that we will use all the disk resources efficiently. Hence, the
    crawler will not be "blocked" by migration process.
    
    Producer: Producer will monitor the global queue. If any file is
    added to this queue, it will dqueue that entry and migrate the file.
    Currently 20 migration threads are spawned at the beginning of the
    rebalance process. Hence, multiple file migration happens in parallel.
    
    2. Crawl only bricks that belong to the current node:
       --------------------------------------------------
    As rebalance process is spawned per node, it migrates only the files
    that belongs to it's own node for the sake of load balancing. But it
    also reads entries from the whole cluster, which is not necessary as
    readdir hits other nodes.
    
    New Design:
            As part of the new design the rebalancer decides the subvols
    that are local to the rebalancer node by checking the node-uuid of
    root directory prior to the crawler starts. Hence, readdir won't hit
    the whole cluster  as it has already the context of local subvols and
    also node-uuid request for each file can be avoided. This makes the
    rebalance process "more scalable".
    
    Change-Id: I73ed6ff807adea15086eabbb8d9883e88571ebc1
    BUG: 1171954
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/9657
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 9f7557a50584dd71e7d84cedf16d4937dc821f42
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Thu Apr 16 17:50:04 2015 +0530

    cli,doc: man page of gluster (man gluster) should show bitrot command information
    
    Currently when user type incorrent bitrot specific command then every
    time cli error suggest wrong command to reuse.
    With this fix it cli will suggest specific bitrot command when user type
    wrong bitrot command.
    
    With this fix it will also display bitrot command information in man page
    by typing 'man gluster'
    
    Change-Id: I7dbf31332a8cc0723e54e8a37fea0afe19d95e0e
    BUG: 1207532
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10273
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit de7c629d02b723e6b4c3d50a14ea5f072e27ccc1
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Apr 7 12:49:37 2015 +0530

    nfs/auth,exports,netgroup : port log messages to new framework
    
    Five gf_log messages are not changed to gf_msg because gf_msg
    not sending the output to STDOUT.
    Bug id : BZ1215017
    
    Change-Id: Ie8de286355becc3fd73fa80057734b834cf40b04
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/10173
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit bacb5491e394b5e1bc16114bbbd6edaa68bf1f4f
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Tue Apr 28 17:08:32 2015 +0530

    libglusterfs: allocate a segment for quota logging
    
    Change-Id: Ia71488a20147ec3e99548aea15b4a57bb325fd06
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10420
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2bde49f98964724b9e12255539bd1a91b3c8b086
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Apr 6 17:30:02 2015 +0530

    nfs: Enable throttling for rpcsvc
    
    Busy nfs servers need throttling to prevent duplicate requests
    from casuing an increase in memory consumption.
    
    Change-Id: I855bb1e841ba06b523e55f86f7788a0f7a49d444
    BUG: 1212385
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10269
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 32c35e175ac362a9682b10600044a5fe17441176
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Apr 6 12:55:13 2015 +0530

    rpc: Perform throttling conditionally
    
    This change makes rpc's throttling to be performed only if
    attribute throttle is set in rpcsvc_t.
    
    Change-Id: I24620095570e206f5dc8fc6208fcf55cb22a1658
    BUG: 1212385
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10268
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit b04b957f2f27cf03958b456b3cec097d1e04923c
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Apr 6 12:34:55 2015 +0530

    rpc: Introduce attribute throttle for rpcsvc_t
    
    This attribute will be used to set/unset throttling for
    a rpcsvc_t program subsequently.
    
    Following APIs have been added to get/set throttle.
    
    int
    rpcsvc_set_throttle (rpcsvc_t svc, gf_boolean_t value);
    
    gf_boolean_t
    rpcsvc_get_throttle (rpcsvc_t svc);
    
    Change-Id: Ica8a9166cef22eb92d81fe68e48d0a5e24a1ef95
    BUG: 1212385
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10267
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a7f848245ae5b0e4bbe363de13ec1676753352c5
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Apr 13 16:26:56 2015 +0530

    nfs / acl3.c, nlm files : port log messages to new framework
    
    Porting log messages to a new framework for acl3.c, nlm4.c,
    nlmcbk_svc.c
    
    Change-Id: Iee4daae4fe1460eddf95d285615335b836d7f958
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/10217
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit f3ff9abbe5f80911a88222cbdbcfa8616b4743da
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Apr 13 15:50:12 2015 +0530

    nfs / nfs files : porting log messages to new framework
    
    Porting log messages to a new framework for nfs-common.c,
    nfs-fops.c, nfs-fops.h, nfs-inodes.c, nfs3-fh.c, nfs3-helpers.c.
    
    Change-Id: I55cd94de62eafe6ad3754cd065d7459a81a9f285
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/10214
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit ee6cd10ce947787bf6ea589bca1cb259c4bb214d
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Apr 13 12:21:09 2015 +0530

    nfs / mount files : porting log messages to a new framework
    
    Porting log messages to a new framework for mount3udp_svc.c,
    mount3.c, mount3-auth.c files.
    
    Change-Id: I1e9cab500b6052bfac43c5ae1c82278e20d2f898
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/10210
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 428933dce2c87ea62b4f58af7d260064fade6a8b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Sat Apr 11 20:03:47 2015 +0530

    geo-rep: Limit number of changelogs to process in batch
    
    Changelog processing is done in batch, for example if 10 changelogs
    available for processing then process all at once. Collect Entry, Meta
    and Data operations separately, All the entry operations like CREATE,
    MKDIR, MKNOD, LINK, UNLINK will be executed first then rsync will be
    triggered for whole batch. Stime will get updated once the complete
    batch is complete.
    
    In case of large number of Changelogs in a batch, If geo-rep fails after
    Entry operations, but before rsync then on restart, it again starts from the
    beginning since stime is not updated. It has to process all the changelogs
    again. While processing same changelogs again, all CREATE will get EEXIST
    since all the files created in previous run. Big hit for performance.
    
    With this patch, Geo-rep limits number of changelogs per batch based on
    Changelog file size. So that when geo-rep fails it has to retry only last batch
    changelogs since stime gets updated after each batch.
    
    BUG: 1210965
    Change-Id: I844448c4cdcce38a3a2e2cca7c9a50db8f5a9062
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10202
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8986a47c54db4769feb4e6664532386f1cd0275d
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Sat Apr 25 12:44:15 2015 +0530

    libgfapi : port gfapi to new logging framework
    
    Change-Id: Iaa0a92f82b9a0a26eda1a8d72b3b66ce66fab443
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9918
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 315364b78cd152835cf6d30e32fd145a942e1d7a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 27 00:00:08 2015 +0530

    cluster/ec: Handle unhandled states
    
    This was leading to hangs when get_size_and_version fails
    
    Change-Id: Iad9408c2dacc9a74594b8d2f94c95f402533b0f1
    BUG: 1215265
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10390
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit cd4e9abee1270c6400037912aacbbf171c6897c0
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Apr 27 12:48:07 2015 +0530

    libglusterfs: update glfs-messages header for reserved segments
    
    all the logging patches will be dependent on this segment allocation.
    Sending this change as a seperate one to avoid the conflicts.
    
    Change-Id: Iedd72ab6dc3526f1a6b01828807b5e6b9edcba90
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10400
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ada6b3a8800867934af57a57d5312f5a5d8374f0
Author: anand <anekkunt@redhat.com>
Date:   Fri Apr 17 14:19:46 2015 +0530

    libglusterfs: Implementation of sync lock as recursive lock to avoid crash.
    
    Problem : In glusterd,we are using big lock which is implemented based on sync
    task frame work for thread synchronization and rcu lock for data consistency.
    sync task frame work swap the threads  if there is no worker poll threads
    available,due to this rcu lock and rcu unlock was happening in different threads
    (urcu-bp will not allow this),resulting into glusterd crash.
    
    fix : To avoid releasing the sync lock(big lock) in between rcu critical
    section,implemented sync lock as recursive lock.
    
    More details:
    link : http://www.spinics.net/lists/gluster-devel/msg14632.html
    
    Change-Id: I2b56c1caf3f0470f219b1adcaf62cce29cdc6b88
    BUG: 1211640
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10285
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d4889b2cfd29e6ecc911d2b29d1f85d516a66eaf
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Apr 15 22:53:21 2015 +0530

    arbiter: load arbiter xlator on every 3rd brick of a replica 3 AFR subvol
    
    Logic for adding the 'glusterd_brickinfo->group' member and using it to
    find the brick positon has been taken from http://review.gluster.org/#/c/9919.
    Thanks to Jeff Darcy for that.
    
    This patch is a part of the arbiter logic implementation for 3 way AFR
    details of which can be found at http://review.gluster.org/#/c/9656/
    
    Change-Id: Idbfe4f29ee8e098e0102def8f38b32314316b188
    BUG: 1199985
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10257
    Tested-by: NetBSD Build System
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 70a729e9751e45e266f7462443dcf2b6be3cecbe
Author: Milind Changire <mchangir@redhat.com>
Date:   Mon Mar 30 16:53:05 2015 +0530

    geo-rep: log ENTRY failures from slave on master
    
    ENTRY operations failures on slave left no trace for debugging purposes.
    This patch captures such failures on slave cluster and forwards them to
    the master and logs them. Failures of specific interest are the ones
    which return code EEXIST on the failing operations.
    
    Change-Id: Iecab876f16593c746d53f4b7ec2e0783367856bb
    BUG: 1207115
    Signed-off-by: Milind Changire <mchangir@redhat.com>
    Reviewed-on: http://review.gluster.org/10048
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1adf231fc425ac35eb91a5b771ea0c5c97b1f6c3
Author: vmallika <vmallika@redhat.com>
Date:   Thu Apr 16 08:10:01 2015 +0530

    quota: display error when inode-quota cmds executed with cluster ver < 3.7
    
    In a heterogeneous cluster with op_version less than 3.7, inode quotas will
    be accounted on those bricks which has glusterfs version 3.7 and this is
    not available in older version.
    This will have incorrect values displayed when user queries inode count
    from CLI.
    
    This patch will display error when inode-quota commands
    are executed with cluster version less than 3.7
    
    Change-Id: Ia0e6d5635d1d8e7b2e2cfc3daa7b7f9e314a263a
    BUG: 1212253
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10261
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b4d909003851e327d2cf448f9409cf5e31893579
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 10 17:03:02 2015 +0530

    geo-rep: Adhering to the common storage for geo-rep
    
    Making geo-rep use the common storage shared by nfs,
    snapshot and geo-rep. The meta volume should be named
    as gluster_shared_storage, and it should be mounted
    at "/var/run/gluster/shared_storage/".
    
    geo-rep will have create a directory called 'geo-rep'
    in the meta-volume and all the lock files are created
    inside it.
    
    Change-Id: I82d0bff9be191f75f643606a9a21d53559047ac4
    BUG: 1210344
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10196
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ddc8dece96b0c04fca564aa3990f484119713720
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Apr 27 22:32:59 2015 +0530

    libglusterfs: Fix the return value of inode_ctx_get2()
    
    Currently inode_ctx_get2 return success for value2 even if it is
    not found. This patch fixes the same.
    
    Change-Id: I6bf3e6cb280ab3b9b8818bf48dc6e42a349dfa5d
    BUG: 12002268
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/10412
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f692757193bc9464a49b545931f201ba832c24a3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Sun Apr 26 20:38:30 2015 -0400

    build: configure: automake defaults to max filename length=99 chars
    
    automake's default rule for making tar files invokes tar with options
    to use Unix V7 tar file format, which has a maximum FQ pathname length
    of 99 characters. Some of the new tests in .../tests/bugs/... have names
    that are longer than 99 chars. These files are dropped from the dist
    tarfile.
    
    automake can be configured to use a newer (POSIX 2001) tar format that
    does not have limits on the length of file names.
    
    Change-Id: I2f3f239e410c66aa13b1257dc734691741b7c667
    BUG: 1215486
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10392
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 464d0d15328bd54173b367953ba9ee58d697afe5
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Apr 27 06:32:40 2015 +0200

    tier: fix off-by-one overrun in UUID string
    
    UUID strings are UUID_CANONICAL_FORM_LEN (36) bytes long
    plus the trailing nul character that various function (e.g.:
    uuid_unparse) will add. As a consequence, UUID strings must
    be declared as UUID_CANONICAL_FORM_LEN+1 long, otherwise
    we get a off-by-one overrun that corrupts the next variable
    on stack.
    
    BUG: 1129939
    Change-Id: I5837ad6ca06fa17cc7ab143eedd02d8099ecca2a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10394
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 472d5c67013913ca8646f32ece214a767a955ef9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Apr 26 17:59:49 2015 +0530

    storage/posix: prevent NULL dereference
    
    filler->fd is never set but used.
    
    Change-Id: Icf21c439b37c9faa3751658a9e63a74570ed153c
    BUG: 1215265
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10383
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5dd40bd4ad768c4d2eb07520efeb49467c709df6
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Feb 4 23:08:31 2015 +0530

    geo-rep: Re Enable ignore_deletes Option
    
    If this option is set, Deletes will not be propogated to Slave.
    This option is applicable for UNLINK and RMDIR.
    
    gluster volume geo-replication <MASTER> <SLAVEHOST>::<SLAVEVOL> \
            config ignore_deletes true
    
    Default value is false.
    
    PS: Use this option with caution, If you create the file in master
    with same path then it fails to sync to slave. Old file in Slave
    will have different GFID compared to New.
    
    BUG: 1189363
    Change-Id: I1f7816d1ea36460a654873739d3fb1b6c13e0f8d
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9583
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 60f764631971de4357d2f72a8995f844949de8ca
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Mar 17 12:18:30 2015 +0530

    geo-rep: Do not fail-back to xsync if Changelog is failed
    
    Unless change_detector is set to xsync, do not fallback to
    xsync, except during Initial Sync or Partial History.
    
    When a brick goes down, Changelog exception is raised due
    to which geo-rep fallback to xsync. Even after brick comes
    back geo-rep will not consume Changelog.
    
    BUG: 1202649
    Change-Id: I1f8ea26ac7735f6ee09b3b143ee3eb66bfc9fc37
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9758
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 08a51f0fcd35ac8e1c9ba431db9a41bcfc208c44
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Wed Mar 4 17:07:53 2015 +0530

    Snapshot:  New logging framework implementation of snapshot messages.
    
    Change-Id: I3e8b5f6ae59d16752beb8053c2afddfb5c00be14
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9796
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>

commit 6627f191ef28504780c8d27ae5c2f472478f8a14
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Wed Apr 22 15:57:44 2015 +0530

    glusterd: New logging framework, all the message label
    
    Change-Id: I5f83b070638384b3f2e3efe936f64080c3334eab
    BUG: 1194640
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/10332
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 3e1dbb49624f4dc430e0c6e7f4626bdf6f84120b
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Apr 10 15:54:27 2015 +0530

    libglusterfs/syncop: Pass xdata even in error case
    
    xdata should be passed even in error cases.
    lookup() call was missed in previous patch set.
    
    Change-Id: I1ad2c452d05a3b4433b640762aaea5d3a91f2ba5
    BUG: 1209869
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/10193
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1de3b05b3fd7514dbce5182c371c6be97819969
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Apr 10 13:02:59 2015 +0530

    glusterd: Remove direct references to peerinfo in frame cookies
    
    RCU protection requires that we don't have  direct references to
    protected data structures outside read-critical sections
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      82ebfdd Remove direct references to peerinfo in frame cookies
      dec4bec Remove incorrect and unneeded code from
              gd_syncop_mgmt_v3_unlock_cbk_fn
      7aced7b Use stack allocated uuid for frame cookie.
      38e4124 Address comments from 10192/2
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: Ic50e5fca0be72af5090f4cf318efa55d29075de9
    BUG: 1205186
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/10192
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 585b1f0d9e485674268cb90bd8f3fdb143bab06b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Apr 26 10:40:18 2015 +0530

    syncop: Implement syncop_fxattrop
    
    Change-Id: Ifc7937ceb451f6e11e40a9513017226fd0f115b0
    BUG: 1215265
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10382
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 540fc2829bd63a2fa070c68ed105eb23145df406
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Apr 13 10:37:55 2015 +0530

    glusterd: incorrect rsp.op_ret handling in volume get in cli
    
    Change-Id: Iabe99c06166578fc90121e7cfdca4a6a3f5328ae
    BUG: 1211132
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10229
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 18fd2fdd60839d737ab0ac64f33a444b54bdeee4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Apr 20 17:37:21 2015 +0530

    glusterd: initialize snapd svc at volume restore path
    
    In restore path snapd svc was not initialized because of which any glusterd
    instance which went down and came back may have uninitialized snapd svc. The
    reason I used 'may' is because depending on the nodes in the cluster. In a
    single node cluster this wouldn't be a problem since glusterd_spawn_daemon takes
    care of initializing it.
    
    Change-Id: I2da1e419a0506d3b2742c1cf39a3b9416eb3c305
    BUG: 1213295
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10304
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 4c3724f195240e40994b71add255f85ee1b025fb
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 16 17:45:04 2015 +0530

    cli: fix vol_type in volume info xml
    
    xml parsing of voltype should be inline with the cli
    
    Change-Id: I41ddddac00d07f03b56a041e1c3f5a132fbd7393
    BUG: 1212398
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10271
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 004f64e93d23f44144483d21422f47e81d358045
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Apr 24 10:10:35 2015 +0530

    core: Global timer-wheel
    
    Instantiate a process wide global instance of the timer wheel
    data structure. Spawning glusterfs* process with option arg
    "--global-timer-wheel" instantiates a global instance of
    timer-wheel under global context (->ctx).
    
    Translators can make use of this process wide instance [via a
    call to glusterfs_global_timer_wheel()] instead of maintaining
    an instance of their own and possibly consuming more memory.
    Linux kernel too has a single instance of timer wheel where
    subsystems such as IO, networking, etc.. make use of.
    
    Bitrot daemon would be early consumers of this: bitrot translator
    instances for multiple volumes would track objects belonging to
    their respective bricks in this global expiry tracking data
    structure. This is also a first step to move GlusterFS timer
    mechanism to use timer-wheel.
    
    Change-Id: Ie882df607e07acaced846ea269ebf1ece306d6ae
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10380
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7be43338ff292eb9ff43892e05eb83575e66433c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Apr 24 21:43:25 2015 +0530

    bitrot/scrub: fix induced throttling in syncop_ftw_throttle()
    
    Failing to reset scanning counter causes "incorrect" delay of around
    50 seconds per directory entry. This causes scrubber to run extremely
    slowly.
    
    [
        NOTE: This is a temporary fix. With the introduction of token
              bucket based throttling, inducing throttle via sleep()
              call would be unneeded.
    ]
    
    Also, fix logging messages in scrubber to log brick and full path
    of the object which is identified/marked as corrupted.
    
    Change-Id: Id501bd15dcdbd8a09613f80f9d84050304740027
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10375
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>

commit 652f5e8bd429ea0e2433e40ccee63ef1cd45baea
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Apr 25 05:03:47 2015 +0200

    Tests: fix spurious failures in trash.t
    
    Fix timing problems that cause rare spurious failures in trash.t
    
    BUG: 1129939
    Change-Id: I673e033b53b6b4bb993c22fadbdcee725b2c1e96
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10360
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 331ef6e1a86bfc0a93f8a9dec6ad35c417873849
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Dec 2 10:54:53 2014 +0100

    nfs: make it possible to disable nfs.mount-rmtab
    
    When there are many NFS-clients doing very often mount/unmount actions,
    the updating of the 'rmtab' can become a bottleneck and cause delays. In
    these situations, the output of 'showmount' may be less important than
    the responsiveness of the (un)mounting.
    
    By setting 'nfs.mount-rmtab' to the value "/-", the cache file is not
    updated anymore, and the entries are only kept in memory.
    
    BUG: 1169317
    Change-Id: I40c4d8d754932f86fb2b1b2588843390464c773d
    Reported-by: Cyril Peponnet <cyril@peponnet.fr>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9223
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a675ab96b917fc48fc3d7ca035590ebd7cf102bd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Apr 19 09:40:34 2015 +0200

    tiering: skip CTR-xlator and config options when disabled
    
    When compiling with --disable-tiering, GlusterD should not contain any
    references to the ChangeTimeRecorder xlator or any of the data tiering
    options.
    
    BUG: 1213125
    Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10296
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 009363dbc162dca71efce6689497b3948a14bd82
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Apr 9 19:00:58 2015 +0530

    geo-rep: Don't log geo-rep safe errors in mount logs
    
    EEXIST and ENOENT are safe errors for geo-replication.
    Since mkdir is captured in all the bricks of the changelog.
    mkdir is tried multiple times as per the number of bricks.
    The first one to process by gsyncd will succeed and all
    others will get EEXIST.  Hence EEXIST is a safe error
    and can be ignored. Similarly ENOENT also in rm -rf case.
    And also gsyncd validates these errors and log them in
    master if it is genuine error. This is coming up with
    the patch http://review.gluster.org/#/c/10048/
    Hence ignoring above said safe errors.
    
    Change-Id: I10ae86b11d49c7c3ba2be3110dace6b33daa509e
    BUG: 1210562
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10184
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b855aa062927ea4845f56d2d1a1a2a8af3dc4192
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Tue Apr 7 18:43:30 2015 +0530

    libglusterfs: avoid crash due to ctx being NULL
    
    Change-Id: Ib667ed42f0b598baddb829b448d6efc3d8e044f1
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10155
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f6e24fc54453669f3943e50f44cce9bb6070a71a
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Tue Apr 7 11:27:19 2015 +0530

    cli: Error out when there is not enough memory
    
    Change-Id: Ia8d061de5be1343cc10a945f6cf011686a770d33
    BUG: 1211594
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10144
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 557ea3781e984f5f3cf206dd4b8d0a81c8cbdb58
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 14 13:45:33 2015 +0530

    libglusterfs: Implement cluster-syncop
    
    This patch implements syncop equivalent for cluster of xlators. The xlators on
    which the fop needs to be performed is taken in input arguments to the
    functions and the responses are gathered and provided as the output.
    
    This idea is taken from afr-v2 self-heal implementation by Avati.
    
    Change-Id: I2b568f4340cf921a65054b8ab0df7edc4478b5ca
    BUG: 1213358
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10240
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3514f465ef58aff3ed160538fbd22fc72a27b2aa
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Apr 13 15:32:58 2015 +0530

    features/shard: Implement unlink fop
    
    Change-Id: I5cdd805821a4f3657f490223b97f42c724ee588f
    BUG: 1207615
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10249
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7efa7e2116856b4cf37797218612a41bdd237e77
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Apr 23 08:30:11 2015 +0530

    cluster/ec: Perform inode-write on healing subvols
    
    If the version numbers do not match, then writes are performed only on at least
    N-R bricks which have same version. But if we want to do healing of files which
    are constantly modified we need to allow writes on subvols that are undergoing
    heal. Data healing will mark 62nd bit while the heal is going on. When the data
    transaction sees that this bit is set it needs to perform the fop on that
    subvol irrespective of whether the versions match or do not match. Fop is
    considered successful only if N-R non-healing bricks succeed.
    
    Change-Id: I69a17582df397aaf6e8ca4b5e746c7ca802cbbde
    BUG: 1215265
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10372
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit de9d06cd7cfca0b42beffe003e7c1e09d469ca7e
Author: Günther Deschner <gd@samba.org>
Date:   Mon Apr 20 13:16:59 2015 +0200

    xlators/cluster/dht: Fix Resource leak (CID 1291751)
    
    Coverity CID 1291751.
    
    Guenther
    
    Change-Id: Ibe9dc3662811dc5889f85fa063ab9211fcaf7f12
    BUG: 789278
    Signed-off-by: Guenther Deschner <gd@samba.org>
    Reviewed-on: http://review.gluster.org/10301
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1b309fd9f80a84f1ccde59dca4a4362213e70f7f
Author: Anoop C S <achiraya@redhat.com>
Date:   Fri Apr 24 17:32:18 2015 +0530

    gfapi: Reduce the log-level from ERROR to TRACE
    
    Change-Id: I0b87f8ccc755a32ac64547c5f5973ea5c468018f
    BUG: 1202274
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/10364
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit 405b10cc8aeb812994ac8d86e76350afbec2fcaa
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Apr 24 19:10:11 2015 +0530

    tests : Skip geo-rep regression for now
    
    As geo-rep regression is causing cores,
    it is being disabled for now and will be
    re-enabled once the issues are fixed.
    
    Change-Id: Ie846b599369acb4a8fd814d1e889cffb4610a2c8
    BUG: 1163543
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10369
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 48de998d589350dafeb00bc6ecd22faa9f66b9da
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Apr 24 16:24:52 2015 +0530

    timer: Fix use after free issue
    
    Change-Id: I056c9777b242a11af7f576ad19b2db93dbdf82d4
    BUG: 1215117
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10367
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b72bc58ecc108a2fddbdb6f606cd86a57ca5a68f
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Mar 25 15:04:19 2015 +0530

    features/trash : Notify CTR translator if an unlink happens to a file
    
    This implementation is same as the posix_unlink_cbk() where CTR sends
    a request during a unlink to send the number of links to the inode
    and posix obliges sending it using the unwind xdata dict.
    For Trash xlator a unlink is stat + mkdir(if parent is not present)
    + rename. And hence this is handled in trash_unlink_rename_cbk().
    
    Change-Id: I402e83567b88e3c9fe171379693c82937af567f9
    BUG: 1205545
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/9989
    Tested-by: NetBSD Build System
    Tested-by: Joseph Fernandes
    Reviewed-by: Joseph Fernandes
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4973d0ea608147ff186f13ab51090f59986f1c9f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Apr 16 17:46:49 2015 +0530

    build: correct the version in glusterfs-api.pc
    
    The version in glusterfs-api.pc has moved backwards, breaking existing
    versioned dependencies in QEMU. The following table contains the
    GlusterFS version and the version for glusterfs-api.pc:
    
        .------------------------.
        | GlusterFS | pkg-config |
        |-----------+------------|
        |   3.4.x   |   4.3.4.x  |
        |   3.5.x   |   6.3.5.x  |
        |   3.6.x   |   7.3.6.x  |
        |   3.7.x   |   7.3.7.x  |
        |   master  |   7.x.y.z  |
        '------------------------'
    
    BUG: 1211836
    Change-Id: I62168a0ab4f0c78e61987371ae75a0d2dd56ced8
    URL: http://thread.gmane.org/gmane.comp.emulators.qemu/330176
    Reported-by: Andreas Färber <afaerber@suse.de>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10308
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ec6ccda3783e9a3edd5a2e4093e07ee37f266520
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed Apr 15 12:32:11 2015 +0530

    cli: validate brick while creating replicate volume
    
    When user create replicate volume by typing incomplete command
    "gluster volume create <VOLNAME> replica replica_count" then cli
    is crashing.
    Fix is to validate command properly. If user have not given any brick
    then it should return proper cli command usage error message.
    
    Change-Id: I3d4096a144e20f21ab956049af1dae196217a807
    BUG: 1211576
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10245
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit b6b18e32c820271cbee4770ff79d6c705c112bfa
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Apr 23 23:14:45 2015 +0530

    tests: Add tests/basic/ec/ec-12-4.t to bad_test()
    
    Lot of recent regression runs have been affected by this.
    
    Change-Id: I16dceae5c18c73ddca60e90f8c0fe782ef59d7f3
    BUG: 1163543
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10357
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: NetBSD Build System

commit 8c053f3fd16462e0afc89f409043d9462c5fa551
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Apr 23 10:18:49 2015 +0530

    geo-rep: Changes required as part of changelog version 1.2
    
    The index value for UNLINK and RMDIR in changelog
    is no more the last index. It varies based on whether
    the 'changelog.capture-del-path' is enabled or not.
    Hence, fixed index is used.
    
    The option to capture deleted path in changelog comes
    with the patch: http://review.gluster.org/#/c/10288/
    And the parser changes with http://review.gluster.org/#/c/10166/
    
    Change-Id: Idc1a2e2bf90c888be4524d3ce74865aea09485de
    BUG: 1214561
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10344
    Tested-by: NetBSD Build System
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 2e16e383128707806cecd9027088cde573ff182d
Author: Anoop C S <achiraya@redhat.com>
Date:   Wed Apr 15 13:01:51 2015 +0530

    features/trash: Minor coverity fixes
    
    CID 1288784
    CID 1288785
    CID 1288795
    CID 1288796
    CID 1288797
    CID 1288802
    
    Change-Id: I51dd7653a2dce3b7b6387e5d91c1c07eb157a04b
    BUG: 789278
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/10315
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Tested-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>

commit 272b55b54b3f760f0b95b29ec37ed719852ce4ed
Author: arao <arao@redhat.com>
Date:   Tue Feb 17 15:14:53 2015 +0530

    dht: Fixing dereference after null check
    
    CID: 1175023
    The check for null is made before dereferencing
    the pointer variable alongside.
    
    Change-Id: I827927f2fcf6d1f365f4d6b5a678373020b9daf9
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9663
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 0fc310accb6bf86e42e09e0876b51b8860075fda
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Apr 8 17:39:56 2015 +0530

    tools/glusterfind: Do not fail to list if Session is invalid
    
    If session is invalid, Show the session time as "Session Corrupted"
    
    BUG: 1209843
    Change-Id: I10f7fb79f6a3a2cabab3f21bce86f2a2f424e8b6
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10164
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: NetBSD Build System

commit 838317e199c6cc11ff5e7094552537f03a8f6313
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 20 23:23:55 2015 +0530

    cluster/afr,dht: Fix memleak after syncop_readlink
    
    Change-Id: Ia71c14c2c2709c541075748c9011437e0d8cac4b
    BUG: 1213542
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10305
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit ba9be029652fae1e024b14b5456d87260a18fb77
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Apr 23 06:32:38 2015 +0200

    Tests: trash.t portability fixes
    
    Fix various portability problems in trash.t
    - work around timing issues
    - avoid wildcard usage only supported by bash
    
    Original patch from Anoop C S and Jiffin Tony Thottan.
    
    Removed LONGER_HEAL_TIMEOUT from previous patch as it
    seems to run fine without it now.
    
    BUG: 1129939
    Change-Id: I0f6f484209ef4db7e0a7b733b863927cb248e73e
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10327
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ee255e239aaa1ed5f6388c48a8919989535f3dcc
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Apr 13 15:23:51 2015 +0530

    features/trash : fixing trash dir option
    
    Previously, problem was caused due to buffer overflow of variable used
    in the code. This patch fix the same.
    
    Change-Id: I3df5e06044470022f9475d93d33447db35384da2
    BUG: 1132465
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/10215
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 86b02afab780e559e82399b9e96381d8df594ed6
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Apr 13 02:42:12 2015 +0100

    glusterd: support for tier volumes 'detach start' and 'detach commit'
    
    These commands work in a manner analagous to rebalancing when removing a
    brick. The existing migration daemon detects "detach start" and switches
    to moving data off the hot tier. While in this state all lookups are
    directed to the cold tier.
    
    gluster v detach-tier <vol> start
    gluster v detach-tier <vol> commit
    
    The status and stop cli commands shall be submitted separately.
    
    Change-Id: I24fda5cc3ba74f5fb8aa9a3234ad51f18b80a8a0
    BUG: 1205540
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Signed-off-by: root <root@localhost.localdomain>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10108
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System

commit abbc525dd3cbe142753c5b44a2717c1ed6b26723
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Apr 15 22:58:59 2015 -0400

    tests: ignore results from some spuriously-failing tests
    
    These tests were selected based on a survey of the last 50 apparently
    spurious regression failures involving only one test, as of April 21, 2015.
    They were responsible for the following number of failures out of those 50.
    
      volume-snapshot.t: 24
      uss.t:              8
      glupy.t:            5
    
    In other words, they were responsible for 74% of those failures.  Until
    they're fixed (or we find some generic problem to which they're particularly
    vulnerable for some reason), ignoring their results should significantly
    improve our regression-test success rate.
    
    Change-Id: Ia0c2600df387f0bccc9dce819582fc883bdb5b89
    BUG: 1163543
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10322
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 765849ee00f6661c9059122ff2346b03b224745f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Apr 21 11:48:15 2015 -0400

    core: avoid crashes in gf_msg dup-detection code
    
    Use global_xlator for allocations so that we don't try to free objects
    belonging to an already-deleted translator (which will crash).
    
    Change-Id: Ie72a546e7770cf5cb8a8370e22448c8d09e3ab37
    BUG: 1212660
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10319
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f1bdc3f186576107fda4f3665c809c791b4cbe95
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Mar 27 16:03:20 2015 +0530

    features/shard: Consume size and block count in metadata read ops
    
    Metadata read fops like lookup, stat etc will now fetch the xattr that
    holds the size and block count information, extract the size and block
    count fields and set them in respective stbuf before unwinding the
    resultant iatt to the parent xlator.
    
    Change-Id: I881be8955092fa6b75f8b0e4f3deb01344cb638e
    BUG: 1207603
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10098
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1fbcecb72ef3525823536b640d244d1e5127a37f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Apr 16 19:28:21 2015 +0200

    Fix case mistake for MKDIR_P in Makefiles
    
    Some makefiles used $(mkdir_p) instead of the corectly defined $(MKDIR_P).
    The former is substituted as an empty string, leading to possible failures
    depending of the user shell tolerance. NetBSD's /bin/sh seems to choke
    more easily than Linux's /bin/bash, but if the later does not fail, it
    does not created the intended directories anyway.
    
    BUG: 1129939
    Change-Id: I8caed4000f3c91cb3a685453848fb854793945ed
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10276
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit f45779067dbba3077b9c64c930fd4ddd1c51243e
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Apr 14 04:35:09 2015 +0530

    gfapi: Modified CACHE_INVALIDATE flags
    
    Have prefixed CACHE_INVALIDATE flags exposed via gfapi with 'GFAPI_'.
    In addition as INODE_UPDATE is asynchronous and may need some
    support in NFS-Ganesha, have taken it out for now. Will revisit it
    later.
    
    Change-Id: Icbbc2c92a61c9225b6c5bc8c4212e8c4a3a0a10f
    BUG: 1200262
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10225
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b464723a48c2e35e7f209c3f909c964b6ba7fb47
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Apr 14 13:08:34 2015 +0530

    gfapi: Fix in glfs_h_create_from_handle
    
    While constructing glfs_object from the handle given, incase
    if inode is found in the inode table, we need not do "syncop_lookup"
    unless we need to return the inode attributes.
    
    BUG: 1200262
    Change-Id: I4682d9e4420a0bcb1b3e807b801ccb3d8de3d2cd
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10232
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit aa87c31d8d7406157af582c7aeafd5ed6a64fd2d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Apr 17 18:06:17 2015 +0200

    Correctly return error for run-tests.sh -r
    
    In recent modification introducing the -r option for run-tests.sh,
    there was a missing bit: When -r is used, the regression result is
    not returned and the outcome is always considered as a success.
    
    Fix it by correctly reporting the status.
    
    Change-Id: If4e3c96d51037fbcf6d9d0e10a3dd3e12da77447
    BUG: 1129939
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10289
    Tested-by: NetBSD Build System
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2ae52207f40c8ec840d6ab0907a08fed6b30282a
Author: Günther Deschner <gd@samba.org>
Date:   Wed Apr 15 12:10:34 2015 +0200

    xlators/storage/posix: Fix Dereference before null check (CID 1293501).
    
    Coverity CID 1293501.
    
    Everywhere in this call "name" is explicitly checked for NULL derreference just
    not here in this path.
    
    Guenther
    
    Change-Id: Ie3e7b704702cb979a036052238ed65eda1531407
    BUG: 789278
    Signed-off-by: Günther Deschner <gd@samba.org>
    Reviewed-on: http://review.gluster.org/10252
    Tested-by: NetBSD Build System
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 84df19e44801164219aaf83e61cc8f0b8b9bd08c
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Apr 17 15:15:50 2015 +0200

    Tests: python portability
    
    Make sure to use $PYTHON defined from tests/env.rc so that we get the
    path to the actually detected python interpreter.
    
    BUG: 1129939
    Change-Id: Ibf3e88f190d5e0c6a4a08e8d5ef9d0b5cba5078a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10286
    Tested-by: NetBSD Build System
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fc451b5b0fb8d7b3952ca6ecf91779cbcf00187f
Author: Michael Adam <obnox@samba.org>
Date:   Wed Apr 15 09:15:23 2015 +0200

    gfapi: fix potential non-0-terminated string (CID 1134002)
    
    Use correct target buffer length for strncpy and make
    sure that the target string is 0 terminated.
    
    Fixes Coverity ID 1134002.
    
    Change-Id: I97a74a94a818eb08a711e547f2ac6ae46087f065
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10247
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 7fb85e3670cb4743436fd2cf0fbbf9c0869728ec
Author: Michael Adam <obnox@samba.org>
Date:   Wed Apr 15 08:34:13 2015 +0200

    upcall: fix use-after free (CID 1288760, 1288761)
    
    Coverity IDs:
    1288760 - Read from pointer after free
    1288761 - Use after free.
    
    Change-Id: Ide9405b9c30a3e27941054a4ae61f585ef09cd8c
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10242
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit d18c68fbe1608a824bf50ffa3315d7acd5054a15
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Apr 16 12:11:24 2015 +0530

    geo-rep/cli : Fix geo-rep cli crash
    
    Fixes crash when "gluster vol geo-rep <master-vol> status"
    is run because of incorrect argc and index comparison.
    
    Change-Id: Id14d63d020ad9c5951b54ef50e7c140e58d9d7a6
    BUG: 1212063
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10264
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a3578deaa5886ddac6196ef3dc5ad78d97ba1692
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Apr 15 22:58:59 2015 -0400

    tests: report run_all status correctly on failure
    
    Change-Id: I469c78db4c9be8f81729a6f835355f8806f65e64
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10259
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 0486c7f40a5813dd50f73c4dc233c55c77b8d958
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Apr 13 05:47:09 2015 +0000

    quick-read: Do a null check before unref
    
    Commit 4ea5b8d2046b9e0bc7f24cdf1b2e72ab8b462c9e seems to have removed the check
    as a part of static analyis fixes but I'm seeing errors in the client log.
    
    --------------------
    touch  /mnt/fuse_mnt/zero-byte-file
    echo 3 > /proc/sys/vm/drop_caches
    cat  /mnt/fuse_mnt/zero-byte-file
    
    mount log:
    [2015-04-13 05:52:21.683256] E [iobuf.c:790:iobuf_unref] (-->
    /usr/local/lib/libglusterfs.so.0(_gf_log_callingfn+0x232)[0x7feda12c0e24] (-->
    /usr/local/lib/libglusterfs.so.0(iobuf_unref+0x56)[0x7feda1304c8e] (-->
    /usr/local/lib/glusterfs/3.7dev/xlator/performance/quick-read.so(qr_readv_cached+0x466)[0x7fed95b7e2fc]
    (-->
    /usr/local/lib/glusterfs/3.7dev/xlator/performance/quick-read.so(qr_readv+0x70)[0x7fed95b7e385]
    (-->
    /usr/local/lib/libglusterfs.so.0(default_readv_resume+0x270)[0x7feda12d4401]
    ))))) 0-iobuf: invalid argument: iobuf
    
    --------------------
    
    Hence re-adding the checks.
    Note: I'm using the same BZ Id used for the original commit though it is in
    MODIFIED state just for correlation.
    
    Change-Id: I79749814a9d4082933e3b306ce449492ee5b43a5
    BUG: 1109180
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10206
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 56a04936f29a21b7bd277b4b9dc92fea01730c2e
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Wed Feb 25 11:43:14 2015 +0530

    glusterd/snapshot: Fix memory leak while using scandir
    
    scandir allocates memory for dirent entries.
    Ensure to free them up once they are used.
    
    Noticed this while looking for a sample scandir implementation.
    
    Change-Id: Iff5f76e93e698d3f454f273d9dd7d9a15cf63953
    BUG: 1196027
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/9739
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2ab703d12020178f8520674e9903f2e74a650bbd
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Apr 6 06:21:05 2015 +0200

    Auto-retry failed tests to workaround spurious failures
    
    Add a -r flag to run-tests.sh that will cause failed tests to be
    retried once. The idea is to reduce the impact of spurious failures:
    no need to retrigger in jenkins, and no need to replay all the tests.
    
    Change-Id: I176bb32678835a669992fbac7de4dd14ee5c62bc
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10128
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 50b9dd3559802160aea923945fc104824fc76064
Author: vmallika <vmallika@redhat.com>
Date:   Wed Apr 15 05:50:01 2015 +0530

    quota/marker: fix inode quota healing after glusterfs upgrade
    
    There is a problem during upgrade where, inode quotas are not healed in
    the contri xattrs.
    Healing happens if contri xattrs are missing.
    But healing doesn't happen if contri xattrs are present and inode quota
    values are missing in the contri xattrs.
    
    This patch fixes the problem
    
    Change-Id: I6c88b74b5bb333a97c5419e24cc4ada82839f474
    BUG: 1211808
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10239
    Tested-by: NetBSD Build System
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit c07f166560e5f0b7f3ef400520773b2c7f1f4220
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Apr 7 15:32:18 2015 -0400

    tests: early bail-out on bad status or new core file(s)
    
    This started as a way to identify which test created new core files,
    since that's a critical piece of debugging information that's missing
    when we only check for cores at the end of a run.  It also exits
    *immediately* either on bad status or discovery of a new core file.
    This allows the run to be retried or aborted quickly, to reduce the
    latency of all jobs in the regression-test pipeline.
    
    Change-Id: Ib4a1c779b44f041ab8728f772874f6c23de95929
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10157
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 08a1041ca9aaf5300032294ca5c5e19dc8f836eb
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Apr 10 20:12:57 2015 +0530

    geo-rep: Added GF_CPPFLAGS to Makefile.am
    
    This change is required to include contrib files in glusterfs.h
    
    Change-Id: I40ef2c495015a6861fdd9f6a72599f094a89eb2a
    BUG: 1200262
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/10200
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 95f6e297a0a2349235a3258569dcc019aafe46df
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Apr 13 16:46:57 2015 -0400

    doc: correct omission of author credit for Translator 101
    
    Change-Id: I4d3cb518c9c45c99a2011d538d4ca24f6b676d76
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Change-Id: I4d3cb518c9c45c99a2011d538d4ca24f6b676d76
    Reviewed-on: http://review.gluster.org/10223
    Tested-by: NetBSD Build System
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit c37045c9ab572de7aa4c0dec5eeef4273ffd538a
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Mon Apr 13 14:08:53 2015 +0530

    NFS-Ganesha : Use common meta-volume for shared storage
    
    A fixed name and mount point is used to share the common volume
    required by various components. Make appropriate changes on the
    NFS-Ganesha to accomodate the commom meta-volume as the
    shared storage.
    
    Change-Id: I9c87e486c2bb3a414f9773c74ed46e111f3c9c14
    BUG: 1210344
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/10211
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: NetBSD Build System

commit c528589a585c23b4288784247310b8763612a822
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Apr 10 15:17:05 2015 +0530

    glusterd: Store ping-timeout in glusterd conf in memory
    
    As of now glusterd_conf_t's ping-timeout was of no use and hence statedump was
    not reflecting correct ping-timeout value configured in glusterd.vol
    
    Change-Id: I76ba7b721264565751538c7fcdcb801a28317581
    BUG: 1210627
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10191
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 6e8298654a7d0de29192b88d769132cfc51c9ac7
Author: vmallika <vmallika@redhat.com>
Date:   Wed Apr 1 20:03:37 2015 +0530

    quota/disperse: handle inode quotas in xattr aggregate
    
    with the inode quota feature, quota size is now
    increased from 64bit to 192bits which contains
    values of 'file size', 'file count' and 'dir count'
    
    This change in quota size xattr needs to be handled
    in disperse xattr aggregation
    
    Signed-off-by: vmallika <vmallika@redhat.com>
    
    Change-Id: I5fd28aa9f5b8b6cba83a98360236417a97ac16ee
    BUG: 1207967
    Reviewed-on: http://review.gluster.org/10112
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit d3b52c8283eb4c85018a5055a0dbe628b5bd2d29
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Apr 7 11:39:29 2015 +0530

    admin/doc : Object count for quota
    
    Change-Id: I271cca911f6dd1f481634063919a587843d93e50
    BUG: 1190108
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/10171
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit db5fc47e2022a18038e3877f69a708532b64969c
Author: Justin Clift <justin@gluster.org>
Date:   Sun Apr 12 16:23:55 2015 +0100

    Fix incorrect rfc.sh and checkpatch.pl use of "jenkins" instead of "gerrit"
    
    Change-Id: I6e78477554097a2be5aad8e3fb196970fb30dac2
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/10203
    Tested-by: NetBSD Build System
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 0333ac8abf9d5d1cc95fea80fba098c7d2c4c8c3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 30 13:50:11 2015 +0530

    cluster/ec: Entry self-heal fixes
    
    - Directory deletion should always happen with 'rm -rf' flag, otherwise the
      call may fail with ENOTEMPTY.
    - Instead of doing an explicit 'link' call, perform mknod call with
      GLUSTERFS_INTERNAL_FOP_KEY which acts as 'link' if the
      gfid already exists.
    
    Change-Id: I8826f92170421db37efb67dfc00afad4ab695907
    BUG: 1207085
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10045
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit fac4ab30f3076ba1147e652bd3ac8288d0d7f8b6
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Apr 7 13:56:16 2015 +0530

    doc : pNFS support for gluster volumes
    
    Change-Id: I910f8f786849b4ece3d3c258c2c52537edc173dd
    BUG: 1209380
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/10145
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit dbd9bd7b2d806163f9bb069ec04e24d9269f769c
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Fri Apr 10 19:14:42 2015 +0530

    NFS-Ganesha : Fixing HA script invocation and others
    
    gluster features.ganesha disable failed invariably.
    And also, there were problems in unexporting
    volumes dynamically.Fixed the above problems.
    
    Change-Id: I29aa289dc8dc7b39fe0fd9d3098a02097ca8ca0c
    BUG: 1207629
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/10199
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: NetBSD Build System

commit b5d7faa96b5ca44be6899c6976691e0fde7d70d1
Author: Vijaykumar Koppad <vkoppad@redhat.com>
Date:   Fri Jun 13 17:52:30 2014 +0530

    Geo-rep: Adding regression tests for geo-rep
    
    This patch introduces upstream regression suit for geo-replication
    
        * Modifies cleanup (tests/include.rc) to remove everything but
          hook-scripts.
    
    Prerequisites:
        * Passwordless SSH from root to root of current host.
        * Export /build/install/sbin and /build/install/bin to PATH
          variable for root user.
    
    Change-Id: I433dd8bbb17edba9baaf516fe0dce3133ba39184
    BUG: 1101111
    Signed-off-by: Vijaykumar Koppad <vkoppad@redhat.com>
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7392
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5cb5d7029216ce71b19fd798a86ef4c384262ba9
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Apr 7 15:05:09 2015 +0530

    tools/glusterfind: Prevent ssh public key overwrite issue
    
    Same ssh key was used for all the sessions, when multiple
    sessions created in Cluster, public keys get overwritten by
    newest sessions. Moved ssh keys to respective session dir.
    
    BUG: 1206547
    Change-Id: I3d8fac9b24bc7c71445c7b4deae83104693e7dab
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10150
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit a2deb5ffb7aba02fe50ef38d9ead84debc3411cb
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed Apr 8 00:27:54 2015 +0530

    glusterd: Restarting glusterd should not reset bitrot tunable value to default
    
    Previously when user restart glusterd then bitrot tunable value for option
    "scrub-throttle", "scrub-frequency", "scrub" cleared. glusterd was not storing
    these bitrot tunable value properly.
    
    With this fix it will store scrub-throttle, scrub-frequency, scrub, bitrot
    tunable value in /var/lib/glusterd/vols/<volname>/info file and it will resume
    these value when glusterd restart.
    
    Change-Id: I58e756e14fbb8513a6f878f808ea148e7aa33cb0
    BUG: 1209751
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10159
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 1387bd92e8ada3a0e46d833997a14d35e810f0de
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Fri Apr 10 14:16:36 2015 +0530

    bitrot/glusterd: Scrubber should not crawl bricks if bitrot is not enable
    
    If user create multiple volume and user enable bitrot only for few
    volume then scrubber should not crawl bricks of volume on which bitrot
    is not enable.
    Fix is while volfile generation check whether bitrot is enable on that
    particular volume or not. If bitrot is enable then only it add bricks of
    that volume in scrubber volfile.
    
    Change-Id: I53687c8e1acb39f8e4a712028b73f0b7006122b9
    BUG: 1207547
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10190
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 4e10fe52f88ad37b64a167afac1ab654e3016d5e
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Apr 10 16:15:53 2015 +0530

    doc:  add translator development urls in developer guide
    
    Change-Id: If74550dfea9121c69a86b13d52a02ce11f3bdc31
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10195
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit f5220016c6525a6e166b83bcc24a036c5db0498b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Apr 8 14:48:32 2015 +0530

    storage/posix: Introduce xattr-fill on fds
    
    ... with some of the code borrowed from http://review.gluster.org/#/c/3904/
    
    Change-Id: I4901ef14d6f843d8d69f102d43d21b60ba298092
    BUG: 1207603
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10180
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1efa50861b2cee68de9c9b751d9fc5eed08f5e5b
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Mar 26 15:18:54 2015 +0530

    glusterd: Replace transaction peers lists
    
    Transaction peer lists were used in GlusterD to peers belonging to a
    transaction. This was needed to prevent newly added peers performing
    partial transactions, which could be incorrect.
    
    This was accomplished by creating a seperate transaction peers list at
    the beginning of every transaction. A transaction peers list referenced
    the peerinfo data structures of the peers which were present at the
    beginning of the transaction. RCU protection of peerinfos referenced by
    the transaction peers list is a hard problem and difficult to do
    correctly.
    
    To have proper RCU protection of peerinfos, the transaction peers lists
    have been replaced by an alternative method to identify peers that
    belong to a transaction. The alternative method is to the global peers
    list along with generation numbers to identify peers that should belong
    to a transaction.
    
    This change introduces a global peer list generation number, and a
    generation number for each peerinfo object. Whenever a peerinfo object
    is created, the global generation number is bumped, and the peerinfos
    generation number is set to the bumped global generation.
    
    With the above changes, the algorithm to identify peers belonging to a
    transaction with RCU protection is as follows,
    - At the beginning of a transaction, the current global generation
      number is saved
    - To identify if a peers belonging to the transaction,
      - Start a RCU read critical section
      - For each peer in the global peers list,
        - If the peers generation number is not greater than the saved
          generation number, continue with the action on the peer
      - End the RCU read critical section
    
    The above algorithm guarantees that,
    - The peer list is not modified when a transaction is iterating through
      it
    - The transaction actions are only done on peers that were present when
      the transaction started
    
    But, as a transaction could iterate over the peers list multiple times,
    the algorithm cannot guarantee that same set of peers will be selected
    every time. A peer could get deleted between two iterations of the list
    within a transaction. This problem existed with transaction peers list
    as well, but unlike before now it will not lead to invalid memory access
    and potential crashes. This problem will be addressed seprately.
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      52ded5b Add timespec_cmp
      44aedd8 Add create timestamp to peerinfo
      7bcbea5 Fix some silly mistakes
      13e3241 Add start time to opinfo
      17a6727 Use timestamp comparisions to identify xaction peers instead
              of a xaction peer list
      3be05b6 Correct check for peerinfo age
      70d5b58 Use read-critical sections for peer list iteration
      ba4dbca Use peerinfo timestamp checks in op-sm instead of xaction peer
              list
      d63f811 Add more peer status checks when iterating peers list in
              glusterd-syncop
      1998a2a Timestamp based peer list traversal of mgmtv3 xactions
      f3c1a42 Remove transaction peer lists
      b8b08ee Remove unused labels
      32e5f5b Remove 'npeers' usage
      a075fb7 Remove 'npeers' from mgmt-v3 framework
      12c9df2 Use generation number instead of timestamps.
      9723021 Remove timespec_cmp
      80ae2c6 Remove timespec.h include
      a9479b0 Address review comments on 10147/4
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: I9be1033525c0a89276f5b5d83dc2eb061918b97f
    BUG: 1205186
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/10147
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7c7bbc027feb4c5b233e3078951e5bb1d9fc4618
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Apr 9 18:44:23 2015 +0530

    nfs: do not overwrite the return value and errno of resolve operation
    
    * In auth status check which is done in the resume function, the op_ret and
      op_errno values saved in nfs3_call_state are overwritten by the return value
      of the auth status check function.
    
    Change-Id: Id4682ddd399c78a1cef6313a534892ef309c57a6
    BUG: 1210338
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/10179
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 3fc4f31a78e06dc09e03a958be500683dc9bcd78
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Mar 10 15:13:29 2015 +0530

    configure.ac: print yes/no instead of 1/0 in output
    
    POSIX_ACLS support in output of configure shows
    0/1 instead of no/yes.
    
    Added BUILD_POSIX_ACLS to make value consistent.
    
    Change-Id: Ife728d0d03ff0eb03d4389fefc04507a76205ccd
    BUG: 1185654
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9848
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: NetBSD Build System

commit d10bd788fada54ad095e19b5aedf949e23fdabb2
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Apr 8 10:49:07 2015 +0200

    crypt xlator: Fix memory coruption after free
    
    crypt xlator allocated local memory through mem_get0(), but code called
    through STACK_DESTROY()/FRAME_DESTROY() does not expect memory to be
    allocated that way: it will use GF_FREE() even for data allocated by
    mem_get0(), which should be given the mem_put() treatment. As a result,
    allocating using mem_get0(), while relying on FRAME_DESTROY() cleanup
    led to memory corruption.
    
    Using GF_CALLOC() instead of mem_get0() sets memory allocation on par
    with cleanup code, and crypt.t can pass on NetBSD.
    
    The initial patch was crafted by Raghavendra Talur.
    
    BUG: 1129939
    Change-Id: Ib71b4b57f8d1bb782f950e3c8fa74a4f7e10946e
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10109
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 169ea3e4939b79e5f658d44ac190221324a8967f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Apr 10 10:51:02 2015 +0200

    Tests: fix spurrious failure in mount-nfs-auth.t
    
    Work around a timing-caused spurious error introduced by
    http://review.gluster.org/10047
    
    BUG: 1129939
    Change-Id: I0597377799f2464d9516fe710fa6e39c1f67a858
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/10182
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4797cb1c9dbf3910952f9d28d8272ff83cd25e7b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 8 21:42:49 2015 +0530

    cluster/ec: Fix readdir de-itransform
    
    Problem:
    gf_deitransform returns the glbal client-id in the complete graph. So except
    for the first disperse subvolume under dht, all the other disperse subvolumes
    will return a client-id greater than ec->nodes, so readdir will always error
    out in those subvolumes.
    
    Fix:
    Get the client subvolume whose client-id matches the client-id returned by
    gf_deitransform of offset.
    
    Change-Id: I26aa17504352d48d7ff14b390b62f49d7ab2d699
    BUG: 1209113
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10165
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit af569aaf6ee69ed77be8afc82b4c496041a7bd1b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Apr 7 15:02:30 2015 +0530

    features/bit-rot: Mark versioning fsetxattr as internal fop
    
    Changelog xlator was capturing bitrot-stub's fsetxattr sent
    for versioning. Since it was using the same frame as of the
    create fop, there was inconsistency in fop number and gfid
    of capturing metadata. So fix is to mark fsetxattr used for
    versioning as internal and add internal fop filter in
    changelog_fsetxattr.
    
    Change-Id: I51ff468995139838b22bf293a59a0713a92ee7a5
    BUG: 1170075
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10148
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 6eb27480b6559103e4437facd7aecbcd373479c9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Apr 3 18:14:13 2015 +0200

    build: make contrib/uuid dependency optional
    
    On Linux systems we should use the libuuid from the distribution and not
    bundle and statically link the contrib/uuid/ bits.
    
    libglusterfs/src/compat-uuid.h has been introduced and should become an
    abstraction layer for different UUID APIs. Non-Linux operating systems
    should implement their compatibility layer there.
    
    Once all operating systems have an implementation in compat-uuid.h, we
    can remove contrib/uuid/ from the repository completely.
    
    Change-Id: I345e5357644be2521685e00358bb8c83c4ea0577
    BUG: 1206587
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10129
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 26cbd3bdf5dad190559afbdf0ac125262c4e90a6
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Fri Feb 6 11:44:22 2015 +0530

    rpc-lib: Fixing the coverity issues
    
    Coverity CIDs:
    1210973
    1124887
    1124888
    1124682
    1124849
    1124503
    
    Change-Id: I012f6cf9d14753f572ab94aae6d442d1ef8df79a
    BUG: 789278
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9600
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 320455bddfbadcfbe1b173b0de54b3b25bf228f7
Author: arao <arao@redhat.com>
Date:   Wed Feb 11 18:58:08 2015 +0530

    io-stats: Fixing dereference after null check.
    
    CID: 1124492
    If 'this' pointer fails to exist then the component is hard-coded
    in the gf_log if not it is dereferenced.
    
    Change-Id: I988137d4f5ac4c9aedef7cef0c75b167a8a5c59f
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9639
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d06e6bac4b5aa6d0fbf1660b92c4100de8f79e68
Author: vmallika <vmallika@redhat.com>
Date:   Wed Apr 1 16:56:00 2015 +0530

    quota/cli: validate quota hard-limit option
    
    Quota hard-limit is supported only upto: 9223372036854775807 (int 64)
    
    In CLI, it is allowed to set the value upto 16384PB (unsigned int 64),
    this is not a valid value as the xattrop for quota accounting and
    the quota enforcer operates on a signed int64 limit value.
    
    This patches fixes the problem in CLI and allows user to set
    the hard-limit value only from range 0 - 9223372036854775807
    
    Change-Id: Ifce6e509e1832ef21d3278bacfa5bd71040c8cba
    BUG: 1206432
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10022
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fcb55d54a62c8d4a2e8ce4596cd462c471f74dd3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Mar 31 18:09:25 2015 +0530

    cluster/ec: Ignore volume-mark key for comparing dicts
    
    Change-Id: Id60107e9fb96588d24fa2f3be85c764b7f08e3d1
    BUG: 1207712
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10077
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 169875397d99bd4357f904468288865723b9fa3a
Author: shravantc <shravantc@ymail.com>
Date:   Wed Apr 1 18:31:58 2015 +0530

    doc: update on admin geo replication
    
    updated the geo replication session status
    added configurable options available for geo replication
    updated mountbroker for slaves, added simplified steps for
    auxiliary gluster mount setup for the agent.
    
    Change-Id: Ie8dac5ddb945ee93bcb8bc7694d35b0c6c01c606
    BUG: 1206539
    Signed-off-by: shravantc <shravantc@ymail.com>
    Reviewed-on: http://review.gluster.org/10103
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit da2f8d09de5da89e544a0d56a1b46c234d3ecb5b
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Mar 6 13:26:30 2015 +0530

    cluster/ec: Fix iobuf mem leak
    
    iobuf_get and iobref_add implicitly
    ref the iobuf.
    
    Hence, it is necessary to unref iobuf
    before setting it to NULL.
    
    Change-Id: Icadd8925574cf04fe708d8090868e49356653a8e
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9818
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit accd61fb64b96c4af47aa6cfa41adb0f2e47a60a
Author: GauravKumarGarg <ggarg@redhat.com>
Date:   Tue Mar 31 16:41:08 2015 +0530

    glusterd: bitd daemon should not start on the node which dont have any brick
    
    If user enable bitrot from node1 which have brick then glusterd starting
    bitd daemon on node1 as well as glusterd starting bitd deamon on another node2
    which does not have any brick (node1 and node2 are part of cluster).
    
    With this fix glusterd will not start bitd daemon on the node which
    don't have brick.
    
    Change-Id: Ic1c68d204221d369d89d628487cdd5957964792e
    BUG: 1207029
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10071
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit d57642044b720663c6474d318106c19e84f2c8bf
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Wed Feb 4 16:59:55 2015 +0530

    gluster-cli : Removing logically dead code
    
    Coverity CID: 1124451
    
    Change-Id: I7b2901fdd2ace4666f9e2c6deaf3838322a1c6ff
    BUG: 789278
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9579
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 36aef0411431f62d2412f71557730543edf05726
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Mar 26 15:45:55 2015 +0530

    doc/geo-rep: Mountbroker User Management
    
    BUG: 1136312
    Change-Id: I1c8374de6e7ec93e401ec1c224752bfa5538adee
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10007
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit a0750e3a921f06c2fb84a7ea1556679ec0f1ce09
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Mar 23 14:25:49 2015 +0530

    snapshot:Fetching wrong peer data during probe
    
    When adding a new friend to the cluster, the snap volfile
    are populating with wrong information for reconfigured option.
    
    For snap volumes, reconfigured data's are filling from the
    regular volumes data. This is because wrong dictionary key is
    used here.
    
    Change-Id: I659ebdc48c33419a2b825f26ce1f174abc8ea7dd
    BUG: 1204636
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9969
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7a999ac6b1d0dad7e0b6ab6ee0868e97f76fada6
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Apr 9 19:39:12 2015 +0530

    snapshot/scheduler: Adhering to the common storage for scheduler
    
    Making snapshot scheduler use the common storage
    shared by nfs, snapshot and geo-rep. The meta volume
    should be named as gluster_shared_storage, and it
    should be mounted at "/var/run/gluster/shared_storage/".
    
    Each component(nfs, snapshot, and geo-rep) should have
    their own repos inside the shared storage, and perform
    their operations in the shared storage
    
    Change-Id: I4f670bf089c80037bd2b0716ddf743f48d7411ca
    BUG: 1210344
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10183
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit da48df4e91b69b8f586d658de9573287cad2ce64
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Mar 16 13:12:12 2015 +0530

    glusterd/snapshot : While snapshot restore, compute quota checksum.
    
    Problem : During snapshot restore we anyways copy the quota conf file
    after that we need to compute the checksum for that. If not, there
    might be a checksum mismatch during glusterd handshake.
    
    Solution : Compute a checksum file for quota conf file if its
    present.
    
    Change-Id: Ic4a6567c6ede9923443abf4ca59380679be88094
    BUG: 1202436
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9901
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit df26c5e162b2ff413ff551119346e239df5ed663
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Fri Jul 4 11:45:03 2014 +0530

    glusterd/snapshot: Fix CLI msg for snap limit set
    
    Change of message from "will lead to deletion of snaps"
    to "Will limit creation of new snaps" when setting the
    snapshot limits.
    
    Change-Id: I4732555bb35d3ad30c2cef6ea6c7da42a8edf35d
    BUG: 1116263
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/8236
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit ca9e4bf6bcc947dd7c179c93dae206c6cde4d3b5
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Wed Feb 4 17:19:40 2015 +0530

    gluster-cli : Extra checks for word_count removed.
    
    Coverity IDs:
    1124453
    1124454
    
    In the first case, In the beginning of the function check is made
    to see of the word_count is less than 4. If yes it returns. So it
    wouldn't reach this part if that check takes the true path. So
    this code is logically dead.
    
    In second and third case, this is in false branch for word_cound <6.
    So word_count can't possibly be less than 5 at this point.
    
    Change-Id: Id5e1c81045ce7bc0ee6b7612ea54ef2b7f54b699
    BUG: 789278
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9582
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2b9a4799ef6caaeeca438c019f4a1f6cf423324a
Author: arao <arao@redhat.com>
Date:   Thu Feb 12 12:49:33 2015 +0530

    features/quota: Fixing Logically dead code
    
    CID: 1134007
    The code never reaches the condition check on retlen in
    ret label, hence removing the dead code.
    
    Change-Id: Ia0108b69489bb78a2561ff8da6e00685f472ae82
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9644
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 10ed06a5a1ec396bb8fc7cc1fa8182d93bf7dbb5
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Apr 9 14:58:25 2015 +0530

    snapshot/scheduler: Validate the number of entries in schedule
    
    A valid schedule entry in snapshot schedule must have
    six elements and adhere to the following format
    
    * * * * *
    | | | | |
    | | | | +---- Day of the Week   (range: 1-7, 1 standing for Monday)
    | | | +------ Month of the Year (range: 1-12)
    | | +-------- Day of the Month  (range: 1-31)
    | +---------- Hour              (range: 0-23)
    +------------ Minute            (range: 0-59)
    
    Change-Id: Idf03a3c43a461295dd3e2026bbcd0420319dd0e0
    BUG: 1209408
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10169
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 14dcabf21d308b69d0ec0a3ed910953f22e3aed8
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Apr 9 14:24:43 2015 +0530

    snapshot/scheduler: Fix deleting of snapshot schedule
    
    Check if the argument has an attribute before
    validating the attribute.
    
    Change-Id: Ia4c6c91c2fca2ec3e82b47d81fbc19a5e0f17eb4
    BUG: 1210204
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10168
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 3f21a347932d741de24bccffb761689c5b368e7e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 6 14:34:45 2015 +0530

    snapshot/scheduler: Only run if shared storage is mounted
    
    Before running any snapshot scheduler op command,
    verify if /var/run/gluster/snaps/shared_storage/ exists
    and if the shared storage is mounted at it.
    
    Change-Id: Ibb6ba6c01c227cacf9a19d1bf9264500373a4ed6
    BUG: 1209112
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10135
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 1c25d5f1492c2186e2c9f468a6c109bd4894fc4f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 1 09:06:53 2015 +0530

    doc: Fix command parameters in geo-rep doc
    
    Change-Id: Ie408e702999fb40d10f049e5238c64d70cde203e
    BUG: 1207939
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10081
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit d448fd187dde46bfb0d20354613912f6aa477904
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Feb 9 17:10:49 2015 +0530

    rpc: fix deadlock when unref is inside conn->lock
    
    In ping-timer implementation, the timer event takes a ref on the rpc
    object. This ref needs to be removed after every timeout event.
    ping-timer mechanism could be holding the last ref. For e.g, when a peer
    is detached and its rpc object was unref'd. In this case, ping-timer
    mechanism would try to acquire conn->mutex to perform the 'last' unref
    while being inside the critical section already. This will result in a
    deadlock.
    
    Change-Id: I74f80dd08c9348bd320a1c6d12fc8cd544fa4aea
    BUG: 1206134
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9613
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2788ddd3a0afa98f78128247cca89427a323b090
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Sun Feb 15 19:22:13 2015 +0530

    glusterd: remove-brick status/stop should not show output for non-existing brick
    
    Previously when user start remove-brick operation on a volume then by
    giving non-existing brick for remove-brick status/stop command it was
    showing remove-brick status/stoping remove-brick operation on a volume.
    
    With this fix it will validate bricks which user have given for
    remove-brick status/stop command and if bricks are part of volume then
    it will show statistics of remove-brick operation otherwise it will show
    error "Incorrect brick <brick_name> for <volume_name>".
    
    Change-Id: I151284ef78c25f52d1b39cdbd71ebfb9eb4b8471
    BUG: 1121584
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9681
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e405f6e419387d160f6564d15ad9fd3a43af0d10
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Mar 25 15:11:48 2015 +0530

    Snapshot: Remove brick details on snapshot create error
    
    Since we are not providing complete details of stopped
    bricks on snapshot create error, it is better to remove
    the incomplete brick details.
    
    BUG: 1205596
    Change-Id: I73386059c0d29a6cbe7f2bb6834d8b8fb393db0a
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9999
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e0de0cd9b24169b90c95e1f6a87f05c060185089
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Apr 2 23:06:18 2015 +0530

    glusterd: Better GlusterD handshake request validation
    
    To allow handshake requests to be validated correctly in a multi network
    environment, the request validation process has been improved.
    
    The handshake request initiator will add it's peer ID the request.
    
    The handshake request reciever will allow a request (as before) if,
    - it has no peers, or
    - the request came from a known peer
    
    Identifying the known peer is done as follows.
    - If the request contains a peer ID, it is matched against the IDs in
      the peer list. If a match is found, the request is allowed.
    - The address of the incoming request is matched against the peer
      addresses in the peer list. If a match is found, the request is
      allowed.
    - Otherwise, the request if disallowed
    
    Change-Id: I9eabe2935d16276bb147dfeebf8c8beb08e01411
    BUG: 1207611
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/10122
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 026d59f04b4226c646c6bd9ac1018863057b02c1
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Apr 6 18:52:50 2015 +0530

    doc: cleanup parent doc directory
    
    Change-Id: I65fee850c30e437abef695d2804af74617cc45fe
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10106
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 55ec6f27dd6be71224bb3b0da24c4258596db024
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Nov 26 12:35:23 2014 +0530

    cli: Allow options prefixed with '--' for geo-rep config cmds
    
    Geo-replications allows users to send rsync_options from
    cli but while parsing, options prefixed with '--' are
    treated as unrecognized apart from a few options. Because
    of this rsync_options can't be set through cli. This
    patch allows such options if it's a geo-rep config command.
    
    e.g.
    gluster vol geo-rep master fedora1::slave config rsync-options \
    "--bwlimit=1.5m"
    
    Change-Id: I4b4f10c0efd3f3a362ece65e697d5ce1498f84ac
    BUG: 1168108
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9198
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 3d03c4bf9b46fcbb26bdc1e06fb96099c1894871
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Jun 30 07:20:46 2014 +0000

    glusterd/geo-rep: Check if the state file is present or not.
    
    Currently every geo-rep operation other than start and stop
    force, checks if the state-file is present or not before
    performing the operation. This check is done to confirm that
    the session on which the op is being performed is created.
    
    This patch makes the start command also perform the same check
    and accordingly display the correct error.
    
    Change-Id: Ifd8bdfa3f362e91f58ead3202e2ebdbd411080e5
    BUG: 1114469
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8202
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8830e90fa1b131057e4ee1742cb83d78102714c0
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Mar 31 14:34:22 2015 -0400

    socket: use OpenSSL multi-threading interfaces
    
    OpenSSL isn't thread-safe unless you register these locking and thread
    ID functions.  Most often the crashes would occur around
    X509_verify_cert, even though it's insane that the certificate parsing
    functions wouldn't be thread-safe.  The bug for this was filed over
    two years ago, but it didn't seem like a high priority because the bug
    didn't bite anyone until it caused a spurious regression-test failure.
    Ironically, that was on a test for a *different* spurious
    regression-test failure, which I guess is just deserts[1] for leaving
    this on the to-do list so long.
    
    [1] Yes, it really is "deserts" in that phrase - not as in very dry
    places, but from late Latin "deservire" meaning to serve well or
    zealously.  Aren't commit messages educational?
    
    Change-Id: I2a6c0e9b361abf54efa10ffbbbe071404f82b0d9
    BUG: 906763
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10075
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9df5fdb357da74de38cb4e8c2cea776023641164
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Mar 30 16:03:24 2015 +0530

    tests : modifcation in mount-auth-nfs.t
    
    In the previous test script, for every change in export/netgroup file
    the volume is restarted to accodomate those changes. New changes will
    avoid those restarts.
    
    Change-Id: I2a6052075637f8e833096c6b3fcc01139dea85e4
    BUG: 1143880
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/10047
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3ed7d6de25cba5e24351fd4771e84c7182436916
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Apr 7 16:47:15 2015 +0530

    tools/glusterfind: Check existence of Session
    
    Use glusterfind list command to check a session is valid or not
    
        glusterfind list --session <SESSION> --volume <VOLUME>
    
    Session exists if return code($?) is zero else invalid session
    
    Change-Id: I37faa09e4e1bf2f10725dd8e5b0cc36a36a3cad4
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1205057
    Reviewed-on: http://review.gluster.org/10154
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0086a55bb7de1ef5dc7a24583f5fc2b560e835fd
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Apr 8 17:17:13 2015 -0400

    tests: remove tests for clear-locks
    
    These are suspected of causing core dumps during regression tests,
    leading to spurious failures.  Per email conversation, since this
    isn't a supported feature anyway, the tests are being removed to
    facilitate testing of features we do support.
    
    Change-Id: I7fd5c76d26dd6c3ffa91f89fc10469ae3a63afdf
    BUG: 1195415
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10167
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 093639d8003695889923cc7a106519c1f9a4e2f0
Author: arao <arao@redhat.com>
Date:   Wed Apr 1 12:29:24 2015 +0530

    cli: Fixing dereference after null check
         and dead code removal
    
    CID: 1124609
    CID: 1124596
    CID: 1124471
    CID: 1124475
    CID: 1124476
    The pointer variables are checked before
    dereferencing and the dead code is removed
    
    BUG: 789278
    Change-Id: Ia532733a64401d71ccf1f2b6e434d7bc910e0ed1
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/10083
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 221f260c9d5793d9a1b4ab60dd160bdd41ff3b59
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Apr 8 14:43:47 2015 +0530

    features/bitrot-stub: Packed format for version xattr
    
    Using __attribute__ ((__packed__)) for object signature xattr
    saves some bytes (7 bytes to be particular) occupied by the
    extended attribute on-disk as compared to the unpacked format.
    
    Change-Id: I91a6a0a54aa60e6fd8c357d72f7601b6ed213f2d
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10161
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 61afe3a0c87f11fa685db1e71867d80c533f42e0
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Mon Apr 6 15:23:55 2015 +0530

    cli: gluster volume help should give sufficient information for bitrot
    
    Previously command "gluster volume help | grep bitrot" was not giving
    sufficient information for bitrot.
    
    With this fix command "gluster volume help" will give appropriate information
    for bitrot.
    
    Change-Id: Ic385c760d4ecbfb16ff5d90dba8940b3616035e5
    BUG: 1207532
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10133
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a7f1d08b8f0bdf8d251590d6f7e4acc46f2486b4
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Wed Mar 25 21:07:36 2015 +0530

    Cluster/DHT Mismatching gfid values in dht_local_t
    
    If multiple files with the same name but different gfids
    exist on different subvolumes, dht_lookup_everywhere_cbk()
    copies the gfid from the last received response into
    local->gfid but does not update the local->stbuf structure.
    dht_linkfile_create() uses the value in local->gfid, but
    dht_linkfile_attr_heal() uses the one in local->stbuf, causing
    a mismatch and failure while trying to heal the linkfile attrs.
    
    Change-Id: I80d152be95b42d736c5d9182b955f42e374b82a5
    BUG: 1205785
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/9998
    Reviewed-by: Susant Palai <spalai@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 71897c714f570ae9a64ad0809fd890d1d5265b23
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Apr 8 12:19:18 2015 +0530

    dht : null dereference coverity fix
    
    Change-Id: I700e7ebdfe4929a6d74406ea081059bdddcf7a79
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9628
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 737c027edc51749ebe023baf4ec0db3077329988
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Apr 1 17:50:25 2015 +0530

    libglusterfs: avoid possibility of crash when ctx is null
    
    ctx is passed to gf_log_inject_timer_event() and pass through to
     __gf_log_inject_timer_event() where the struct members are getting
    dereferenced, and can cause crash if the passed ctx is null. This patch
    avoids the issue.
    
    Change-Id: I153dbb5d3744898429139e3d40bb4f0e9093632a
    BUG: 1208118
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10102
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit d3760ac3fe626378ef38c3626d642fe8cfd80ebb
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Apr 1 17:26:25 2015 +0530

    snapshot: correct error message in snapshot helper
    
    Change-Id: Ic01a5d4115383f1245bae3fba2bf92e23c8213ff
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9747
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 6ae434eeb3bfe421f34e624182d46ee11f57c736
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Apr 8 08:03:58 2015 -0400

    ganesha-ha: more robust pid file handling
    
    fix bug with reading pid file to determine if ganesha.nfsd is running
    
    Change-Id: I4050a119e2be93578045a221b67f616e152546d9
    BUG: 1188184
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10163
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4be65bb376e2fffd7175f579724aae4c5718d57c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Apr 1 16:00:05 2015 +0530

    features/shard: Introduce file size xattr
    
    With each inode write FOP, the size and block count of the file will be
    updated within the xattr. There are two 64 byte fields that are
    intentionally left blank for now for future use when consistency
    guarantee is introduced later in sharding.
    
    Change-Id: I40a2e700150c1f199a6bf87909f063c84ab7bb43
    BUG: 1207603
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10097
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 346e64e578573296028efa516cd93cfaf2b17b8f
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Mar 11 18:36:01 2015 +0530

    libglusterfs/syncop: Add xdata to all syncop calls
    
    This patch adds support for xdata in both the
    request and response path of syncops.
    
    Few calls like lookup already had the support;
    have renamed variables in few places to maintain
    uniformity.
    
    xdata passed downwards is known as xdata_in
    and xdata passed upwards is known as xdata_out.
    
    There is an old patch by Jeff Darcy at
    http://review.gluster.org/#/c/8769/3 which does the
    same for some selected calls. It also brings in
    xdata support at gfapi level.
    
    xdata support at gfapi level would be introduced
    in subsequent patches.
    
    Change-Id: I340e94ebaf2a38e160e65bc30732e8fe1c532dcc
    BUG: 1158621
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9859
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4f0c068d8fe2654f205202e129e673aaa9342c63
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Apr 6 13:06:31 2015 +0530

    nfs : introducing logging framework for nfs translator
    
    Change-Id: I3a47cdd06595c87da8e822d11683d68b43c11cda
    BUG: 1194640
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9945
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit e508e06c66e42ca22d8fe88f96ffb295fd1ddae3
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Apr 2 01:03:24 2015 +0530

    doc: introduce upgrade guide
    
    Eventhough we have release branches, its better to keep track of
    upgrade procedures of previous versions. This way we always have
    pointers to upgrade process.
    
    Change-Id: If7a5af0e9efc36bf0343487819a4d311775e65a8
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10107
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 5502ead3804695e6e1edc48fd17e2b3fe7241131
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Apr 8 14:46:33 2015 +0530

    features/bitrot-stub: header file update in noinst_HEADERS
    
    Missing "bit-rot-object-version.h" causing devrpm failures.
    
    Change-Id: I5af326c5871cc468a10dece4772b29eda06c4fa9
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10160
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 097795df7ebab48515d75e95a2c29e5ab42ac5ee
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Apr 1 02:56:23 2015 +0530

    ctr : Fix for heating of files during promotion/demotion
    
    This fix will solve the heating of the files during the promotion
    or demotion.
    Promotion:
    ~~~~~~~~~
    When a file gets promoted it get the current time stamp
     during creation only, but following writes or reads during the
    migration wont heat the file.
    Demotion:
    ~~~~~~~~
    When a file gets demoted it get the wind/unwind time stamp is set to
    zero. The following writes or reads during the migration wont heat
    the file.
    
    What is remaining ?
    ~~~~~~~~~~~~~~~~~
    Bug 1209129 ( https://bugzilla.redhat.com/show_bug.cgi?id=1209129 )
    Inspite of this fix there is still a issue remaining, i.e the heat of
    the file is not keep intact during a internal rebalance activity i.e
    a rebalance within a tier.
    
    Change-Id: I01e82dc226355599732d40e699062cee7960b0a5
    BUG: 1207867
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10080
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6bf07eb642cb82e0de5d96511b6fd13a8838d11d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Mar 30 15:24:00 2015 +0530

    glusterd:Change glusterd_list_add_order to add entry in ascending order
    
    Change-Id: I0f82b1b5ad37e06135e9af33a4b5342ddde3ca94
    BUG: 1207132
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10046
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2a224653df93c4b3a6b3914509f314196ad61008
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 09:50:44 2015 +0200

    features/changelog: fix possible illegal memory access (CID 1288819)
    
    Coverity CID 1288819
    
    strncpy executed with a limit equal to the target array
    size potentially leaves the target string not null terminated.
    Make sure the copied string is a valid 0 terminated string.
    
    Change-Id: Ie2d2970f37840146aa18724be3b89e93194c8160
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10062
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit c262430726635ce868558f299ad494734a173774
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Mar 29 10:13:45 2015 +0530

    cluster/ec: Have same ec_manager_* for [f]set/[f]removexattr
    
    ec_manager_xxx() function for [f]set/[f]remove xattr is exactly same except the
    reporting part. So moved that to common function and use same
    ec_manager_xattr() function for all these fops.
    
    Change-Id: Iaa57023b800f8d1f3f6a827f4ceba9b0a0337336
    BUG: 1199767
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10036
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit a8260044291cb6eee44974d8c52caa9f4cfb3993
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Mon Mar 30 14:27:44 2015 -0400

    glusterd: Support distributed replicated volumes on hot tier
    
    We did not set up the graph properly for hot tiers with replicated
    subvolumes. Also add check that the file has not already been moved
    by another replicated brick on the same node.
    
    Change-Id: I9adef565ab60f6774810962d912168b77a6032fa
    BUG: 1206517
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10054
    Reviewed-by: Joseph Fernandes <josferna@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit f0cd1d73c63001740cd7691a77df7631c9b8e8dc
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Mar 31 15:48:18 2015 +0530

    bitrot/scrub: Scrubber fixes
    
    This patch fixes a handful of problem with scrubber which
    are detailed below.
    
    Scrubber used to skip objects for verification due to missing
    fd iterface to fetch versioning extended attributes. Similar
    to the inode interface, an fd based interface in POSIX is now
    introduced.
    
    Moreover, this patch also fixes potential false reporting by
    scrubber due to:
    
      An object gets dirtied and signed when scrubber is busy
      calculatingobject checksum. This is fixed by caching the
      signed version when an object is first inspected for
      stalenes, i.e., during pre-compute stage. This version is
      used to verify checksum in the post-compute stage when the
      signatures are compared for possible corruption.
    
      Side effect of _not_ sending signature length during signing
      resulted in "truncated" signature to be set for an object.
      Now, at the time of signing, the signature length is sent
      and is used in place of invoking strlen() to get signature
      length (which could have possible 00s). The signature length
      itself is not persisted in the signature xattr, but is
      calculated on-the-fly by substracting the xattr length by
      the "structure" header size.
    
    Some of the log entries are made more meaningful (as and aid
    for debugging).
    
    Change-Id: I938bee5aea6688d5d99eb2640053613af86d6269
    BUG: 1207624
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10118
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7fb55dbdabf73f9169b0f3021a42fa120d64b373
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Apr 6 18:14:53 2015 +0530

    tests/bitrot-stub: Object versioning test(s)
    
    This patch introduces basic object versioning test(s) which
    is required for bitrot detection to work correctly. Basic
    test(s) such as opening a file in read-only mode, single
    open, multiple open()s are covered on FUSE mount _only_ as
    stub does not support anonymous fds yet. For this reason,
    the test case disables open-behind.
    
    Actual verification is implemented as a C source which
    makes use of the same on-disk data structures as used by
    the stub code. The data structures are moved to separate
    header file which is included by the test script. Such
    modularization helps in future enhancements to keep the
    version "data type" opaque and provide handful of APIs
    version checking (equal/greater/etc..).
    
    [
      This is just a start and should grow over time as stub
      is enhanced and codebase matures.
    ]
    
    Change-Id: Ibee20e65a15b56bbdd59fd2703f9305b115aec7a
    BUG: 1201724
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10140
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2dfc36811337666c26e42c13f19eb59a7cef674f
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Mar 30 21:46:25 2015 +0530

    features/bitrot-stub: Enhancement to versioning protocol
    
    .. and potential bug fixes / memleak.
    
    While assigning initial version to an object, both extended attributes
    (namely, ongoing version and the default signing version) were persisted.
    This is optimized to just persist the ongoing version along with safe
    handling of xattr request(s) in it's absence. This is better than the
    earlier approach as the two xattr sets were not atomic anyway (allowing
    a request to sneak in between between two set operations). This also
    allows to perform sanity checks on objects during lookup()/getxattr():
    objects with missing ongoing version but presence of signature are
    possible candidates of tampering (and catching implementation bugs).
    
    There were couple of instances in the code where versioning xattrs
    were incorrectly removed before in-memory versions were initialized,
    which have been fixed with this patch. A memory leak in the IPC code
    path is also fixed.
    
    Change-Id: I01c690ccfe7156a883582275f40f79a7c10c0900
    BUG: 1207054
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/10117
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6a465e6e7e46940e00a387089cc995464975b53d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Apr 7 21:45:49 2015 +0530

    storage/posix: Introduce xattr_fill capability in posix_stat
    
    Change-Id: I2b6503ad9333f445ebdcd9fa660da20b861b985f
    BUG: 1207603
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10158
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1d8e04c2544dec0a0f7fd8ada76287db2a2f71c1
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Apr 7 16:36:27 2015 +0530

    tests: Replace getxattr with getfattr
    
    Change-Id: Ibbe97dae51a81c8d5142c53a57fd9c630dfb6f46
    BUG: 1191396
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10153
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 20e86a1b4c733934ff9960314d06697ad05a4528
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Feb 4 12:14:52 2015 +0530

    afr : null dereference coverity fix.
    
    CID : 1194648
    
    Change-Id: Ib26e7cdbf412d563240885fb3113bcc1fe5c9c49
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9571
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 5ac39ab3cd4ba8c5c3a103912a13c443036bfe2e
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Feb 2 19:19:07 2015 +0530

    Cluster/afr : Coverity fix.
    
    CID:1194644
    
    Childup[] value will not be equal to -1 when afr_xl_op() function gets called
    
    Change-Id: Iaf7a9d41a54f6b2d52d9ba5dadb638f328afe14b
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9540
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 559bb9bec6f59278ac358b586916a1ff6caa53e1
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Apr 7 16:20:43 2015 +0530

    doc : GlusterFS NFS-ganesha integration
    
    Change-Id: Ie18df44d32125afcc750e1f0f2c4728aa2d93699
    BUG: 1209380
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/10151
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 057d2bed4175412e3a95224301eace3e133c1dd3
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Apr 2 15:14:48 2015 +0530

    snapshot/scheduler: Don't append timestamp in scheduled snapshots
    
    The scheduled snapshots will now have names as follows:
    Scheduled-<jobname>-<volume name>.
    
    Stopped appending time-stamp in scheduled snapshots because
    time-stamps are appended in snapshots by default unless
    explicitly asked not to.
    
    Therefore snapshot created from "Job1" of "test_vol" volume
    will look like
    Scheduled-Job1-test_vol_GMT-2015.04.02-09.43.02
    
    Change-Id: I75b4a87d265ed55193f08153fd7ffe521cc5ef68
    BUG: 1208097
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10115
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1a22f3e10c82847f054fc4b57977e059dab8ac29
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 6 14:56:21 2015 +0530

    snapshot/scheduler: Remove unwanted schedule enable check
    
    Allow add, edit, list, delete of schedules even when
    snapshot scheduling is disabled.
    
    Change-Id: Ie55ea7d6e9b3fccd914a786cc54bb323ac765a98
    BUG: 1209117
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10136
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6816c7d46630747dd76cdd9ff90eab77e1e4f95c
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 6 14:13:09 2015 +0530

    snapshot/scheduler: Check the correctness of Jobname and Volname
    
    Check for the correctness of Jobname and Volname. They should
    not be empty, and should contain only one word.
    
    If this condition is met, the rest of the whitespaces are
    also striped, before processing the command.
    
    Change-Id: I2c9503ab86456e0f4b37e31d483ee8b2d0b0e1af
    BUG: 1209120
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10137
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa0befea352402922839dd846c798c0da2afd271
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Feb 10 14:59:09 2015 +0530

    dht : coverity fixes
    
    CID : 1124352,1124365 (unchecked return value),
          1124377 ( logically dead code),
          1124511 (null dereference)
    
    Change-Id: I61e029a078559cfe15d36bf0aa53418f6214e5cb
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9622
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a0e3634c6f0d349a3433cdbeabd93043f5f43e9d
Author: Ernestas Lukoševičius <ernetas@gmail.com>
Date:   Thu Apr 2 23:28:29 2015 +0300

    mount.glusterfs: mounting volumes with volume files
    
    This is a patch for bug-1208676.
    
    When using volume files to mount glusterfs volume,
    this line is always true:
    
    [ -z "$volume_id" -o -z "$server_ip" ] && {
    
    That's because at this place, $volume_id and $server_ip are
    set only and only if the $volfile_loc file was unreadable
    or undefined.
    
    Change-Id: Icdf7612ac13a8f953f2a2adaa426b6339cd9f8fd
    BUG: 1208676
    Signed-off-by: Ernestas Lukoševičius <ernetas@gmail.com>
    Reviewed-on: http://review.gluster.org/10126
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit d1a5c805610115122b8ef61367b61425d7e39db5
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Apr 1 15:13:11 2015 +0530

    features/shard: Refactor code
    
    * Renamed shard_writev_create_write_shards() to shard_common_resolve_shards()
      to appropriately reflect its functionality and for reuse in other fops too.
    
    * Move code common to MKNOD and CREATE into a macro.
    
    * Cut down on if nesting in shard_lookup_cbk()
    
    Change-Id: I488255499673accd426390c6d42f2b39bab3d637
    BUG: 1205661
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10096
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2ef9ad2dc5822b9b88243cb7f60816fe1c531e91
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Apr 6 20:44:09 2015 -0400

    tests: fix spurious regression in uss.t
    
    Sometimes .snaps just doesn't seem to be available right after a
    mount.  I have no idea, but maybe wrapping the next command in an
    EXPECT_WITHIN will cut down on the spurious test failures.
    
    Change-Id: I9bfda9d34e10ff0b783337e700ab8255dc6795ab
    BUG: 1209286
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10143
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6e7d9a4e77a764e86bcde4e704ec05a3c84f9c11
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Mar 24 12:09:52 2015 +0530

    cluster/ec: Refactor inode-writev
    
    All _cbk() functions in inode-write.c do same things, i.e. store
    op_ret/op_errno, stat structures if they are available and combine them.  Moved
    this common operation into one function ec_inode_write_cbk() and made all the
    other _cbk() functions to use this instead.
    
    Change-Id: I2387b9f2d9598ced6299a26ea1900e9deb9fadc4
    BUG: 1199767
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9981
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 0e23ce3fbcf1f138105476cf3b86342268e259d9
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Apr 3 14:14:35 2015 +0530

    performance/md-cache: set right error check in {f}getxattr_cbk()
    
    Currently mdc_{f}getxattr_cbk() check(s) for a non-zero value to
    determine if any cache update has to be performed. Right from
    posix xlator, op_ret has a positive value upon success and -1 upon
    failure. This patch sets right the check in getxattr callbacks so
    that xattr cache update happens for successful calls.
    
    Change-Id: Ifa5ec38bdf7e3dc095de9a56d91559b13cd9e8b6
    BUG: 1208784
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/10127
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit 85865daa1b7dd11badf9f5192e050e1998c76f8a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 23 15:07:47 2015 +0530

    extras: Fix stop-all-gluster-processes.sh script
    
    "test -n" command takes single string as argument. The
    command was failing with "Too many arguments" when multiple
    pids are got.
    
    Change-Id: Icc409082f492c72522168d5e203684f00f52cf1b
    BUG: 1204641
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9970
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 97cfe210c73bcdab653a0da884627009f5c5808b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Apr 6 12:30:42 2015 +0530

    tests: move bug-1168875.t to tests/bugs/snapshot folder
    
    Change-Id: Ie4e960002b8de7e31f91365785c44df3ac04c88d
    BUG: 1178685
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10131
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e5f59739b210672480115177cbd4dbd391fabb92
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 2 15:07:31 2015 +0530

    glusterd: fix Null pointer dereference in bitrot disable
    
    CID : 128806
    
    Change-Id: Ia143a28a3dcb80d2175c908bd152c3d0b821bbb5
    BUG: 789278
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10113
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 331e705b6a458600c0b5cbcf2b0f7b9e1167bdc2
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Mar 20 18:35:26 2015 +0530

    cluster/dht: Unwind with proper op_ret
    
    1. Expected behavior of get_real_filename feature.
    
    A getxattr on a existing dir with glusterfs.get_real_filename:<filename>
    as key should result in one of the following things.
    
    a. A value returned for that key having the real filename (a file whose
    match is a case insensitive match to the filename passed in key).
    b. op_ret = -1 and errno set to ENOENT meaning that no such file exists
    under the specified dir in any case.
    c. op_ret = -1 and errno set to ENODATA. This is a case assuming no
    xlator interprets the glusterfs.get_real_filename key and it get
    passed down to the posix xlator. Naturally, posix xlator would not
    find any xattr with this key and would return ENODATA. This will be
    interpreted specially by the caller as the feature not being supported
    by underlying glusterfs.
    
    2. What assumptions are wrong?
    Initially the key used to be user.glusterfs.get_real_filename.
    In that case, when posix xlator did a getxattr call it would have
    received ENODATA as error. However, the key has now changed to
    glusterfs.get_real_filename. This leads to a EOPNOTSUPP error instead.
    
    Considering the above information, this is a rewrite of
    get_real_filename logic in dht.
    
    Change-Id: I012e9150047fc8563be91b0d112a368ac1cbf598
    BUG: 1204140
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9956
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit e47a64b929d400ade6c97c3e45531100b979fc51
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Mon Apr 6 18:17:10 2015 +0530

    cluster/dht: fix spurious smoke test failure
    
    There is smoke test failure due to implici declaration of function
    "uuid_parse" and "uuid_compare".
    
    Fix is to change these function caller name to "gf_uuid_parse" and
    "gf_uuid_compare."
    
    Change-Id: I79efa00c44d112c2ca732a9d9711c07bd5f1a069
    BUG: 1207532
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/10139
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 120cdbf3ba51f493df3bff112a9e21c19349b543
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Mar 30 12:49:13 2015 +0530

    build: sort gitignore entries
    
    Change-Id: I79d315efb47577ab88d090a96df13f1f92ed276c
    BUG: 1198849
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10099
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit dc128c6bb0f8935e0aaa64602cd8a2dcedaebbf4
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 6 15:01:15 2015 +0530

    build: add more files to .gitignore
    
    Change-Id: Icef0d7f443f7caf3aa386d3a6978f98cf3a5a4af
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10132
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 37bbcf6861590aa3d980846042855ee4212c89df
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Mar 24 13:59:00 2015 -0400

    cluster/dht: fix tier.c problems found prior to feature freeze
    
    This patch resolves tiering translator issues taken from the list
    in bug 1203776. These issues have been selected to be fixed
    first. The rest will be fixed in a subsequent patch (or are not a
    problem).
    
    3. Replace hardcoded #defines of promote/demote file names
    
    6. Use loc_wipe() in migrate_using_query_file()
    
    9. Only promote/demote files on the same node on which they reside.
    
    14. Replace calloc with GF_CALLOC in tier.c and ensure freeing done
    properly.
    
    15. Handle if parse_query_str fails
    
    22. Only load gfdb library on server side, remove SQL references
        from client.
    
    Change-Id: I6563b11e58ab2e4c6b1ce44db755781ad6d930fb
    BUG: 1203776
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/9987
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 90f72efed8313efe0410634677f36d0fbdc5eab4
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 09:41:10 2015 +0200

    features/changelog: fix possible illegal memory access (CID 1288821)
    
    Coverity CID 1288821
    
    strncpy executed with a limit equal to the target array
    size potentially leaves the target string not null terminated.
    Make sure the copied string is a valid 0 terminated string.
    
    Change-Id: I5ecc60549864cf50e3facbb8a2d9228cd67b57b5
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10061
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit e1e41ae67816ad6f23d074632c9d3f198e15aba3
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 2 10:09:39 2015 +0530

    glusterd: remove duplicate entries from volume set help
    
    gluster volume set help was displaying redundant entries for
    performance.cache-size & network.tcp-window-size as the same key is used in
    different translators. Fix is to consider all the redundant ones as NO_DOC
    
    Change-Id: I7739d992f6fdbb24765caedbb05099d269110476
    BUG: 1005344
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10110
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 17827defd6703298b68fee8fd08aef69ab0e2866
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Mon Feb 9 17:39:20 2015 +0530

    snapview: Fixing the coverity issues
    
    Coverity CIDs:
    1228601
    1220056
    1238185
    1257624
    
    Change-Id: Idb4cc3b44bc3ccb8b497ce355e1e3bacfb176db9
    BUG: 789278
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9615
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d2ada381fe332b6151d12d3ef1d1e47f9f7c77f7
Author: Anoop C S <achiraya@redhat.com>
Date:   Tue Mar 24 14:34:52 2015 +0530

    features/trash: More coverity fixes
    
    The following CIDs are being addressed:
    
    1288792
    1288794
    
    Change-Id: Ic2cdaf43f05488e04616ceb801b47a47c6a93656
    BUG: 789278
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/10082
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5e7cc20d3cc37a03f594237bdf85c67397c3ceac
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Tue Feb 17 17:27:03 2015 +0530

    cli: Removing negative value check for unsigned variable (coverity fix)
    
    CID: 1124663
    
    Change-Id: Ic24014cdb9a68ed310c5e3dcf21fcebd6bf9da60
    BUG: 789278
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9669
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f7a14c0fe5fe92fc6ebaf37322748918a57afef8
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Apr 2 12:51:34 2015 +0530

    snapshot/scheduler: Fix the snapshot create command.
    
    The create command being executed was sent with wrong
    parameters.
    
    Change-Id: I9b3cf23b3a02cf8309d50bf70439ad02b37f191a
    BUG: 1208067
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/10114
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 28397cae4102ac3f08576ebaf071ad92683097e8
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Apr 2 15:51:30 2015 +0200

    Avoid conflict between contrib/uuid and system uuid
    
    glusterfs relies on Linux uuid implementation, which
    API is incompatible with most other systems's uuid. As
    a result, libglusterfs has to embed contrib/uuid,
    which is the Linux implementation, on non Linux systems.
    This implementation is incompatible with systtem's
    built in, but the symbols have the same names.
    
    Usually this is not a problem because when we link
    with -lglusterfs, libc's symbols are trumped. However
    there is a problem when a program not linked with
    -lglusterfs will dlopen() glusterfs component. In
    such a case, libc's uuid implementation is already
    loaded in the calling program, and it will be used
    instead of libglusterfs's implementation, causing
    crashes.
    
    A possible workaround is to use pre-load libglusterfs
    in the calling program (using LD_PRELOAD on NetBSD for
    instance), but such a mechanism is not portable, nor
    is it flexible. A much better approach is to rename
    libglusterfs's uuid_* functions to gf_uuid_* to avoid
    any possible conflict. This is what this change attempts.
    
    BUG: 1206587
    Change-Id: I9ccd3e13afed1c7fc18508e92c7beb0f5d49f31a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10017
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 0aebfaa349c7c68c2d59531eabae5a03a748e16a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Apr 1 14:39:01 2015 +0530

    features/shard: Create and use xattr_req dict as and when needed
    
    Reusing local->xattr_req for the several calls and callbacks per xlator fop
    would cause keys set from previous call/cbk (sometimes even by the xlators
    below) to remain which in some cases can lead to errors.  For instance, the
    presence of "trusted.glusterfs.dht.*" keys (which are remnants of the previous
    call/cbk), can cause the GF_IF_INTERNAL_XATTR_GOTO() check in DHT to fail when
    the same dict is used to wind [f]setxattr.
    
    Change-Id: I8612d020f83f3dc55e4a34d10ccbdaf11d7b4fdd
    BUG: 1205661
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10095
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 13dbf333c47f0bc0efffddd4b8b83c4031cb7f36
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Mar 25 14:25:33 2015 -0400

    cluster/dht: Fix coverity bug in tiering code
    
    The bug was:
    
    *** CID 1291734:  Error handling issues  (CHECKED_RETURN)
    /xlators/cluster/dht/src/tier.c: 451 in tier_build_migration_qfile()
    
    The fix is to check the return code to the remove library call.
    It is legal to fail, we just log an INFO level message.
    
    Change-Id: I026eb49276b394efa3b8092ee2cc209c470aacb2
    BUG: 1194753
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/10000
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5599165e09e5c5e2862996b5f92cf1a1227b9039
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Apr 1 14:04:36 2015 +0530

    features/shard: Fail writes if /.shard already exists as a file
    
    Change-Id: Id7250ca4637c37a005cf2def43d5b843c1ea6562
    BUG: 1205661
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10094
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 00d4125a5cb7102efeb23873cbaf155a71faa9dd
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Mar 31 20:13:59 2015 +0530

    libgfchangelog: Use correct 'this' pointer on new thread creation
    
    When libgfchangelog is linked with non xlator application,
    it should point to 'master' xlator which is initiated separately.
    When ever a new thread is created, 'THIS' points to the global
    xlator. 'THIS' should point to corresponding xlator even then.
    This patch adjusts the pointer accordingly.
    
    Change-Id: I2a199bb3c73146a0329540aedcbae697a00f6f0a
    BUG: 1207643
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10074
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 614dbff79f7003382c239c5c75c48e78ce5397f5
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Thu Apr 2 10:15:07 2015 +0530

    tests: Spurious failure in bug-1117851.t
    
    This test runs file renames in a loop in the background and
    expects them to be done within 75 seconds. On slower VMs the
    operation takes about 75-80 seconds to complete causing the
    test to fail randomly. Increased the timeout to 120 seconds.
    
    Change-Id: I103e630c5a1bcea1fb4c7842892a2e67714c3fbb
    BUG: 1163543
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/10111
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit f66a85a484d41e68611f68d70e458c67f484d2e1
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Jan 27 16:44:20 2015 +0530

    glusterd: compute quorum on peers in cluster
    
    ... and not on peers participating in an ongoing
    transaction.
    
    Change-Id: I6bdb80fd3bf3e7593fdf37e45a441d4a490469b8
    BUG: 1205592
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/9493
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 08d35497e30714058002b4b0095171f1dad73ddc
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Apr 1 17:09:28 2015 +0530

    doc: remove latex and pdf files
    
    Change-Id: I45443e763836c440f9e1ed83f34de486dbfe8ac8
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10089
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 664604742770f7fcce2c7293074aa1e2d04b797b
Author: shravantc <shravantc@ymail.com>
Date:   Thu Apr 2 15:46:17 2015 +0530

    doc : editing admin managing volumes
    
    added Non Uniform File Allocation details and additional options
    fixed formatting issues
    fixed broken links
    
    Change-Id: I387f29e7aab3adab9ae11d5d7474d587e249c7d0
    BUG: 1206539
    Signed-off-by: shravantc <shravantc@ymail.com>
    Reviewed-on: http://review.gluster.org/10116
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit fea8d9701291ed5ebdbd655c916a866b5f40a34f
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Mar 31 17:03:42 2015 +0530

    geo-rep: Log Rsync performance
    
    Introducing configurable option to log the rsync performance.
    
    gluster volume geo-replication <MASTERVOL> <SLAVEHOST>::<SLAVEVOL> \
            config log-rsync-performance true
    
    Default value is False.
    
    Example log:
    [2015-03-31 16:48:34.572022] I [resource(/bricks/b1):857:rsync] SSH: rsync
    performance: Number of files: 2 (reg: 1, dir: 1), Number of regular files
    transferred: 1, Total file size: 178 bytes, Total transferred file
    size: 178 bytes, Literal data: 178 bytes, Matched data: 0 bytes,
    Total bytes sent: 294, Total bytes received: 32, sent 294 bytes
    received 32 bytes  652.00 bytes/sec
    
    Change-Id: If11467e29e6ac502fa114bd5742a8434b7084f98
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 764827
    Reviewed-on: http://review.gluster.org/10070
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cf5bf1863d58f823f9c67b0e5dda3ba9261ccf27
Author: arao <arao@redhat.com>
Date:   Wed Feb 18 13:11:42 2015 +0530

    rpc: Fixing dereferencing after null check
    
    CID: 1124607
    The pointer variable is checked for NULL and
    logged accordingly.
    
    Change-Id: Ied0d7f7ff33da22198eca65f14816b943cae5541
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9674
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f4be9bc3c530ab35a0cd1939df8c43abe54e540d
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 02:28:07 2015 +0200

    features/changelog: fix possible illegal mem access (CID 1288822)
    
    Coverity CID 1288822 (#1 of 2)
    
    strncpy executed with a limit equal to the target array
    size potentially leaves the target string not null terminated.
    
    In this case the strncpy is not needed due to the snprintf
    with the same target buffer which follows immediately.
    
    This patch also removes the now unneeded scratch_dir
    argument to gf_changelog_init_history(), which is semantically
    correct, since scratch_dir has previously been filled into
    jnl->jnl_working_dir by the caller, and this is now used to
    fill hist_scratch_dir.
    
    Change-Id: Ib1ed3a1058e80e34191758921b49c29030d6c9db
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10058
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 41bc3f7f023de198c695bdb7708afef3910cc761
Author: Michael Adam <obnox@samba.org>
Date:   Mon Mar 30 19:48:27 2015 +0200

    features/bit-rot: fix CID 1124725 - use after free
    
    Coverity fixes:
    CID 1124725
    CID 1291742
    
    The problem is that gf_tw_cleanup_timers() frees the handed
    in priv->timer_wheel but it can not set the pointer to NULL,
    so subsequent checks for priv->timer_wheel show it as not NULL
    and allow for access after free.
    
    The proper change might be to change gf_tw_cleanup_timers() to
    take a reference to the pointer and set it to NULL after free,
    but since it is under contrib/, I did not want to change that
    function. Instead this patch uses the function's return code
    which was not used previously. (Maybe this should even be done
    in a wrapper macro or function?)
    
    Change-Id: I31d80d3df2e4dc7503d62c7819429e1a388fdfdd
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10056
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit db7b8d6e5d4485fc5a6e836447dfa5d3cb85b5fd
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Mar 9 09:06:20 2015 +0100

    Tests: fix spurious failure in read-subvol-entry.t
    
    read-subvol-entry.t tests that if a brick has pending operations,
    it is not used for readdir operations. On NetBSD this test exhibits
    spurious failures, with the wrong brick being used to perform readdir.
    
    It happens because when afr_replies_interpret() looks at xattr for
    pending attributes, it uses alternative bahvior whether it is working
    on a directory or another object. The decision is based on inode->ia_type,
    which may be IA_INVAL at that time if we come there from:
      afr_replies_interpret.()
      afr_xattrs_are_equal()
      afr_lookup_metadata_heal_chec()
      afr_lookup_entry_heal()
      afr_lookup_cbk()
    
    Using replies[i].poststat.ia_type, which is correctly set, works around
    the problem.
    
    BUG: 1129939
    Change-Id: Id9ccdd8604f79a69db5f1902697f8913acac50ad
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9831
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4e721bde62bfa4080afe9714743410281260a277
Author: vmallika <vmallika@redhat.com>
Date:   Mon Mar 2 12:34:45 2015 +0530

    DHT: move regular expression log message to DEBUG
    
    Change-Id: I8652208aa2c3a600816c911a9e8af557c67d37c4
    BUG: 1197585
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9777
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 1d6cd6bb0f2f5875e8e4ad370cf1ff2c601cbfd4
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Feb 2 11:57:54 2015 +0530

    Xlators : Fixed typos
    
    Change-Id: I948f85cb369206ee8ce8b8cd5e48cae9adb971c9
    BUG: 1075417
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9529
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 12e603bb9d8bc220eeea01c0ecc8ca63f9df4bc4
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Apr 2 00:29:59 2015 +0530

    glusterd: Fix rebase errors introduced by 4b18fba
    
    4b18fba 'glusterd: group server-quorum related code together' a
    refactoring change, introduced some errors related to usage of
    userspace-rcu lists when rebasing. This patch fixes it.
    
    Changes done include,
    - Redo changes done by
      673ba26 glusterd: Replace libglusterfs lists with liburcu lists
    - Redo changes done by
      c7785f7 glusterd: Protect the peer list and peerinfos with RCU.
    - Redo changes done by
      891c7d0 glusterd: Prevent possible deadlock due to
              glusterd_quorum_count
    
    Change-Id: I789e5bc8b209d9ed6dd951d609baa90e89817639
    BUG: 1205592
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/10105
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 10b4ecb85c5009c6c7b9422bd5299ba43d8448a1
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Mar 5 18:19:30 2015 +0530

    iobuf: Do not call __iobuf_ref directly
    
    iobuf_get will be creating the iobuf and
    hence lock is not necessary to increment ref.
    
    However, it is a good practice to call
    iobuf_ref instead of __iobuf_ref so that
    we have a single point to get refs and
    this can be used later to do mem
    accounting etc.
    
    Change-Id: I1fd328c3c463c23fd5f6df505ccb5c86f6207f28
    BUG: 1199075
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9812
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4a339be28a715aa22d8d07b3137920edea8a1c4a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 30 17:44:50 2015 +0530

    geo-rep: Copy geo-rep hook-script during source install
    
    The hook-script S56glusterd-geo-rep-create-post.sh was not
    copying to glusterd working directory when geo-rep is
    installed through source. Hence the geo-rep create fails
    unless the script is manually copied. This patch addresses
    the issue by copying the hook-script during make install.
    
    Change-Id: I185a877ed720e8300f0e888ab481d0c8c23bf815
    BUG: 1207201
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10051
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 7616738176f44cce8b6cfb0e1f65be8e1dc72f49
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 09:56:35 2015 +0200

    libgfdb: fix possible illegal memory access (CID 1288820)
    
    Coverity CID 1288820
    
    strncpy executed with a limit equal to the target array
    size potentially leaves the target string not null terminated.
    Make sure the copied string is a valid 0 terminated string.
    
    Change-Id: I39ff6a64ca5b9e30562226dd34c5b06267b75b87
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10063
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Joseph Fernandes <josferna@redhat.com>
    Tested-by: Joseph Fernandes <josferna@redhat.com>

commit 7b8637833d2bd07165cd36e6868f4e906dcb7c61
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Feb 25 14:27:32 2015 +0530

    snapshot: remove volname(s) to volname for snapshot create
    
    Since we are not supporting snapshot of a multiple volume,
    it is wrong to display
    snapshot create <snapname> <volname(s)> [no-timestamp]
    [description <description>] [force]
    
    So changing volname(s) to volname
    
    Change-Id: I5d367c319ab30ff5f1c89bc8de795f3436820bcc
    BUG: 1196108
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9741
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 0d36d4f6bab80dab2137e4049ee64e7cec180161
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Mar 31 18:26:48 2015 +0530

    tools/glusterfind: Validate Volume name before session Create
    
    Do not create Session directories if Volume does not exists.
    
    Change-Id: I60c9107135c2bed2a7198582267b2328dec7e868
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1206065
    Reviewed-on: http://review.gluster.org/10072
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit ad0690d3bf979bf7098e718909d58399854c4560
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Mar 19 17:36:52 2015 +0530

    tools/glusterfind: Convert Output file path to absolute path
    
    BUG: 1203656
    Change-Id: Ie6c8f38894466246c453b2a863538a420acfe9f7
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10011
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit c1e1c7443a26d132b3ba6cb164f80ca934690ba6
Author: shravantc <shravantc@ymail.com>
Date:   Mon Mar 30 11:07:34 2015 +0530

    doc : editing admin directory quota
    
    added 'setting alert time' to managing directory quota.
    added 'Displaying Quota Limit Information Using the df Utility' to displaying quota limit information.
    
    Change-Id: Iaaf6201e8aa3687ee70ae28c41b870f2d7a4127f
    BUG: 1206539
    Signed-off-by: shravantc <shravantc@ymail.com>
    Reviewed-on: http://review.gluster.org/10039
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit dc26a253f5f393745bd435721e31d6e2e598eed1
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 02:36:30 2015 +0200

    features/changelog: fix possible memory illegal access (2 of 2, coverity)
    
    Coverity CID 1288822 (#2 of 2)
    
    strncpy executed with a limit equal to the target array
    size potentially leaves the target string not null terminated.
    Make sure the copied string is a valid 0 terminated string.
    
    Change-Id: If283dd6f716912f65729edf6ea26a4331a697151
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10059
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 4b18fba4064992e00cd5ebe1831afc79beab17b2
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Jan 27 15:12:03 2015 +0530

    glusterd: group server-quorum related code together
    
    Server-quorum implementation was spread in many files.  This patch
    brings them all together into a single file, namely
    glusterd-server-quorum.c. All exported functions are available via
    glusterd-server-quorum.h
    
    Change-Id: I8fd77114b5bc6b05127cb8a6a641e0295f0be7bb
    BUG: 1205592
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9492
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 2b949eb89e8ca22d2928c05d549b6f722adf1544
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Fri Mar 6 16:11:16 2015 +0530

    glusterd: gluster command should retrieve current op-version of the NODE
    
    Problem:
    glusterd was failing to get some specific volume option. for eg:
    gluster volume get <vol-name> cluster.op-version
    
    Fix:
    glusterd should set count value in dictionary while retrieving specific volume
    option.
    
    Change-Id: Iada768ea3d8a0006895525eca2c2dcc40432a4ea
    BUG: 1199451
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9821
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 59b1c24c81fe6aa0721a5a60de15b8978c3690ea
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Mar 24 11:38:40 2015 +0530

    Snapshot: Add/Modify snapshot section in man gluster
    
    Change-Id: I771846c678fbfa8d941f09ef2e1de3729079aa79
    BUG: 1205037
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9976
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 3fdd3de1a148cfaf4c1ccf72e8ce2893557cfff6
Author: Michael Adam <obnox@samba.org>
Date:   Mon Mar 30 19:25:02 2015 +0200

    features/bit-rot: fix assignment instead of check (Coverity fix)
    
    Fixes Coverity CIDs 1291728, 1291723, 1291732.
    
    Change-Id: I62f3d540cac0f555fe2839b8418e59691c3ff4fd
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10055
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 07bd6c320c75c39b599929039d028fbc497d4322
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Mar 30 18:59:52 2015 +0530

    libgfapi : return  if gf_strdup failed
    
    Change-Id: Ic8ad48b8118a8505ebbab2e9084007acca7226e9
    BUG: 1198963
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9807
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6d083f47e1399c58da02836f33fdb7d9c31fd689
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Mar 30 13:22:45 2015 -0400

    tests: fix volume_exists to be used from EXPECT_WITHIN
    
    Fixes the spurious volume-snapshot-clone.t regression failures.  In
    brief, the problem is that the script wasn't waiting for config commands
    to complete, and would *sometimes* query the status of a volume while
    that volume was still being deleted.
    
    It turns out that "!" doesn't work properly from EXPECT_WITHIN, so there
    was a choice between changing that or changing volume_exists.  This
    seemed less risky.  Because of code duplication, two instances of the
    function had to be changed, and the other caller (volume-snapshot.t) did
    too.
    
    Change-Id: I766d4dc7c5b11038ede8e45d9d1f29cd02a622a0
    BUG: 1163543
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10053
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ef5c3182224940f76d9290c1c4d9cc8e78fbdb83
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 13:47:21 2015 +0200

    features/trash: fix remove_trash_path in the internal case
    
    In the internal case, copy_trash_path adds a second
    path component "internal_op/", so remove_trash_path
    should remove it again. Originally, remove_trash_path
    did the same thing in the internal and non-internal case.
    This patch fixes this problem.
    
    Change-Id: If247d18217a2375d369672182f69a54881df26b9
    BUG: 1207709
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10073
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5c1ce6d29ee52af9daa23c1c7a54f23ce29a687e
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 10:30:22 2015 +0200

    features/trash: fix remove_trash_path() to do what it is intended.
    
    The intention is to set the the rem_path string pointer that
    is handed in from the outside. So the string has to be passed
    in by reference, or else the function just sets a pointer on
    the stack.
    
    Found by Coverity, CID 1288791
    
    Also fixes:
    CID 1288791
    CID 1288809
    CID 1288810
    CID 1288814
    CID 1288815
    CID 1288817
    CUD 1288818
    
    Change-Id: I6ef5eeb58b83a875cf90513291abe37dee3fc9fb
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10064
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 406a9a497764d2e18b02ed8684c79fa802280405
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Jan 5 05:11:46 2015 +0530

    test : fix for quota-anon-fd-nfs.t spurious failure
    
    quota with nfs sometimes fails to get parent
    with nameless lookups. This is fixed with patch# 9478
    Hence, adding nfs test-case back again.
    
    Change-Id: I9ede7c7dae4604aa7fa03ce7c36f46a9879b7479
    BUG: 1163543
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9381
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3d4203fe3acad47f0a29ebe094b3e427b13f363f
Author: vmallika <vmallika@redhat.com>
Date:   Fri Mar 20 14:25:58 2015 +0530

    quota: enhancement of build ancestry
    
    There can a small race window where marker accounting will
    be missed.
    Consider below example where NFS mount is used
    and bricks are restarted and a write operation is performed
    
    Currently:
    T1: lookup from protocol server, quota will initiate ancestry build
    T2: opendir FOP from ancestry build
    T3: write FOP from client
    T4: write_cbk
    T5: marker initiate accounting.
        There will be a problem here and txn aborts,
        because build_ancestry is not complete
        and parent not found for an inode
    T6: opendir_cbk
    T7: initiate readdirp, posix builds ancestry in readdirp
    
    
    With this patch, now calling readdirp on anonoymous fd
    during build ancestry:
    
    T1: lookup from protocol server, quota will initiate ancestry build
    T2: readirp FOP from ancestry build, posix builds ancestry in
        readdirp
    T3: write FOP from client
    T4: write_cbk
    T5: marker initiate accounting.
        No problem here as build ancestry was performed at T1
    
    
    Change-Id: I2c262c86f34f6c574940a6b8772d94f2bade9465
    BUG: 1184885
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9954
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit d6b6c32ac7f0a6b3d77009aec8bdd0cd289bd0ff
Author: vmallika <vmallika@redhat.com>
Date:   Mon Mar 2 13:10:24 2015 +0530

    function gf_string2bytesize_range should handle 'xB' byte values
    
    Change-Id: I208289aae2423e4bb015cf33bafd2a961e1c3fc6
    BUG: 1197593
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9779
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 562cdace9152add786f156e38dc3fbc8805a69b7
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 12:30:06 2015 +0200

    features/trash: fix storing/wiping of eliminate path (coverity)
    
    Functions store_eliminate_path() and wipe_eliminate_path() take
    eliminate as a plain pointer not pointer to pointer. Hence
    store_eliminate_path fails to hand the allocated and filled
    eliminate data out to the caller (in particular leaking memory),
    and wipe_eliminate_path() fails to NULL the freed eliminate path.
    
    This leads to several leak and access after free errors found
    by Coverity. This patch fixes the issue by handing in eliminate
    by reference and in the case of wipe_eliminate path, also NULLing
    out the free'd pointer.
    
    This fixes the following coverity IDs:
    
    CID 1288759
    CID 1288790
    
    Change-Id: I7520ae42c5f6e369a145bea67b4ff95b75d2ae73
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10068
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f5e4c943cf520c6ec2df3c231fef9ae4116097b8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Mar 30 13:10:00 2015 +0530

    doc/geo-rep: Documentation for management volume for geo-rep
    
    Documented new changes to admin guide for setting up
    geo-replication with the new active/passive switching
    logic that comes with http://review.gluster.org/#/c/9759/
    
    Change-Id: I47de9d2c1e678f7ad789f0ca2acf7ce67eb96c62
    BUG: 1196632
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10043
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 25f97b2788a33efcb0714ad639f8db380b864982
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Mar 24 10:30:31 2015 +0530

    Upcall: Added xlator options to enable cache-invalidation
    
    Added two xlator options to enable cache-invalidation and set
    cache-invalidation-timeout.
    
    In addition, made few minor changes in the upcall processing code
    in gfapi.
    
    Change-Id: Ie0b32ca8348e34e3fe4f1e7df30cc925fa4aad31
    BUG: 1200271
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/9975
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e6f5ace08ad0a068cb49d3ca1274a27aa031992b
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Wed Mar 25 15:11:57 2015 +0530

    NFS-Ganesha: Start and stop NFS-Ganesha service in a platform independent way
    
    Check for what binaries are installed at run time,
    pick appropriate command and perform the required
    action. The service managers supported are systemctl,service
    and invoke-rc.d.
    
    Change-Id: I8deef2bfe5a09da5b055fe6176a58452a882fa76
    BUG: 1202316
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/9991
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 9c37b68bc15c503a0ad5cc2fb04be7b917496d90
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Mar 3 00:27:34 2015 +0100

    build: require cmocka >= 1.0.1
    
    Our mem-pool unit test does a funky realloc(ptr, 0) as an alternative to
    free(ptr). cmocka 1.0.0 has a bug where this is not handled correctly
    and thinks to detect a memory leak. The next cmocka release will have
    this bug fixed, making our unit tests require cmocka >= 1.0.1.
    
    URL: https://cmocka.org/archive/cmocka/2015-02/0000059.html
    Change-Id: I3d7f9b4cf7ace3f958158425ecbcc8f176579122
    BUG: 1067059
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9801
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Andreas Schneider <asn@fedoraproject.org>
    Tested-by: Andreas Schneider <asn@fedoraproject.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6df8d1d8781f59fbab46c4b016dde0b2d33dd189
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Wed Feb 4 13:21:50 2015 +0530

    gluster-cli: Fixing operand error and removing logically dead code.
    
    Assign used instead of comparison
    Coverity CIDs:
    1124391
    1124346
    1124369
    1124370
    1124702
    1124390
    1124397
    
    Change-Id: If015382917cad65edc2fee38ae6328f1d072d6f6
    BUG: 789278
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9574
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e92270044e358ca5b290557026fab32f5d8368e9
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Wed Feb 18 16:32:17 2015 +0530

    libglusterfs : dead code fix.
    
    CID          : 1124884
    
    Change-Id: I3332e844a01c1432f1d80a6acda7a87e8b01801c
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9677
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6522f059eeec1b9962525b61c4c6640ae1afe85c
Author: arao <arao@redhat.com>
Date:   Tue Feb 10 02:51:43 2015 +0530

    features/changelog: Fixing Deference after null check
    
    CID: 1124481
    The goto label 'out' was trying to
    dereference a pointer which might be
    null, hence a check on not null is
    made before the use of it.
    
    Change-Id: I813e523207b8218a7a28c2b3ac36a8e472e36c89
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9617
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e59e3a341308a9f47231d0205359da6886bb82be
Author: arao <arao@redhat.com>
Date:   Thu Feb 19 10:13:22 2015 +0530

    fuse: Removal of dead code
    
    CID: 1124386
    Dead code/ Unreachable code and related
    unsed variable are removed.
    
    Change-Id: Iafd317f01778dfe61f8a0e5398341e4f3a62d7a5
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9690
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 17d719c9ba08ba6b6eb040723f78cfa45b0c2ae7
Author: arao <arao@redhat.com>
Date:   Tue Feb 17 14:54:45 2015 +0530

    features/snapview-server: Fixing explicit null dereferencing.
    
    CID: 1238184
    The pointer was not checked for null before
    dereferencing in the 'out' label, which is
    resolved now.
    
    Change-Id: I8aa7520102b84f63727754b8ac9c1f87ef8a6671
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9662
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2acb5325828a68b06b39ab44e6736c6ad4ca3a06
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Wed Feb 11 11:29:20 2015 +0530

    fuse: Fixing the coverity issues
    
    Coverity CID:
    1124806
    1124692
    
    Change-Id: I6dcf245ded9796fb42516eca63211d855262c26f
    BUG: 789278
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9629
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d7374684f648c1e45d695454f95a65acfe6d04e8
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Mon Feb 9 17:16:22 2015 +0530

    marker, quota: Fixing the coverity issues
    
    Coverity CIDs:
    1124601
    1124690
    1134008
    1134009
    
    Change-Id: I93992b11bb6d8f7edd065f602aec2cd7a8b433d0
    BUG: 789278
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9614
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a2fa3ba3f6b604b9a5b305092226b12e812fcaf1
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Wed Feb 4 14:47:36 2015 +0530

    gluster-cli : Fixing "argument can't be negative" coverity issue.
    
    Here value of fd can never have a negative value if it is to be
    closed. So changing the check from if (fd) to if (fd >= 0)
    
    Coverity CIDs:
    1124652
    1124653
    
    Change-Id: I8491afa93bab10acd2c2e01993a7f7468ca9ff87
    BUG: 789278
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9577
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 10f3289bac31a2b0020dfe1e97ed98601e4e4521
Author: Michael Adam <obnox@samba.org>
Date:   Tue Mar 31 02:01:40 2015 +0200

    fuse: add missing return in error path (CID 1288092)
    
    Fixes Coverity CID 1288092.
    
    Change-Id: I95347915b1dee6003d7a1cfb86f12cf2cd7310f8
    BUG: 789278
    Signed-off-by: Michael Adam <obnox@samba.org>
    Reviewed-on: http://review.gluster.org/10057
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 78474f8fab91affae7207d2704aa5a595b871982
Author: vmallika <vmallika@redhat.com>
Date:   Fri Mar 27 17:09:08 2015 +0530

    quota/cli: improve cli error message when setting limit on invalid path
    
    Change-Id: I5976777adf770d42aa33ebbe3833fb14c1ff658e
    BUG: 1206535
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/10026
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ffb2e85ff574891639d899cc59fcd9f75d4ce51e
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Mar 19 12:05:16 2015 +0100

    Tests: portability fixes for ipc.t
    
    This fixes portability problems in ipc.t so that it can run on NetBSD:
    
    1) EOPNOTSUPP value is OS-dependent. Learn it from system headers
       instead of hard-coding it in the script
    
    2) liglusterfs embbeds its own UUID implementation. The function name
       may be the same as in built(in implementation from libc, but with
       different prototype. In that case, we must make sure python will
       use libglusterfs's version, otherwise we will crash in libc's UUID
       code. Since dlopen() does not make any guarantee on what symbol
       will be used, me need to preload libglusterfs when loading python.
       This is done using LD_PRELOAD.
    
    3) In python code we need to load with RTLD_GLOBAL global in order
       to have dependencies loaded
    
    4) Python's ctypes.util.find_library does not lookup LD_LIBRARy_PATH
       and may therefore miss the library. On failure, retry with less
       portable but more reliable explicit name
    
    BUG: 1129939
    Change-Id: I024cdfd03a5a42a8ec23de38a99e7349aba92ea8
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9944
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d3eacb0d83834db485061d875d95b4f6af41f30a
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 19 15:15:07 2015 -0400

    tests: fix online_brick_count
    
    It turns out that "pidof" is unreliable on some platforms (e.g. Fedora
    21) because it will show spurious entries for processes using the same
    inode under a different name.  Use "pgrep" instead because it's
    name-based and doesn't get confused by glusterd/glusterfs being links
    to glusterfsd.
    
    Also changed bug-913555.t because it had the same mistake in its own
    version of the same function.  Now it uses the common version.
    
    Change-Id: I5d70edd5655faa5470e0f378b8c16a6adacbd4b4
    BUG: 1163543
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/9948
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f9ee09abd29002d8612bcdcbeaf4cf3e404b4cc6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 26 16:06:36 2015 +0530

    cluster/ec: Implement heal info for ec
    
    This also lists the files that are on-going I/O, which
    will be fixed later.
    
    Change-Id: Ib3f60a8b7e8798d068658cf38eaef2a904f9e327
    BUG: 1203581
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10020
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 3feaf1648528ff39e23748ac9004a77595460c9d
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Mar 30 17:23:29 2015 +0530

    Gfdb Query Fix and Volume option fix
    
    1) Query fix in find_changed_with_freq()
    2) Volume option typo fix for write_freq_threshold
       and read_freq_threshold
    
    Change-Id: I38e154818178aab412b2d7b2914cd29acef66ffb
    BUG: 1207343
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/10050
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 3fdecc25b4059e357a3bdce428bbafdf04377e14
Author: shravantc <shravantc@ymail.com>
Date:   Mon Mar 30 14:59:35 2015 +0530

    doc: editing admin setting volumes
    
    added procedure/steps to format and mount volumes
    before volumes are created. Includes step by step
    creation of thinly provisioned volumes.
    
    Change-Id: I92325d84d8b322948a7a58daf0de79e2097d252a
    BUG: 1206539
    Signed-off-by: shravantc <shravantc@ymail.com>
    Reviewed-on: http://review.gluster.org/10044
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8277b02a947ea63d438a77eb1335466ae5060b00
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Mar 27 23:43:05 2015 +0530

    build:change dependency for librdmacm to version >= 1.0.15
    
    Thanks to Niels for the fix
    
    Change-Id: I0954b6f498461dde2b986da9e0e45775175249c9
    BUG: 1206744
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/10028
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0a3420dbd57361174eb30fc054754f8c5499ecfb
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Mar 30 12:32:27 2015 +0530

    build: ignore cscope files
    
    It is common for developers to use cscope and generate
    these cscope.* files with: cscope -b -q or with some
    other switches of cscope. This patch avoid 'git' to worry
    about the same.
    
    Change-Id: I3525e6f1a36f9800f4c27a2cdc6ea9c668981717
    BUG: 1198849
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10040
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 624938999bf925af710e9f73c75040416f68b756
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Mar 25 23:39:16 2015 +0530

    geo-rep: Add support for acls
    
    This patch adds support for ACLS. When it sees SETXATTR
    in Changelog, it adds the file to data queue. rsync/tar+ssh
    will take care of syncing ACLS. User set ACLS will be
    synced to Slave.
    
    This requires "system.posix_acl_access" to go through when
    client-pid is equal GF_CLIENT_PID_GSYNCD in fuse layer.
    
    New config interface is introduced, sync-acls
    Which can be set using geo-rep config(Default is True)
    
    gluster volume geo-replication <VOLUME> <SLAVEHOST>::<SLAVEVOL> \
                   config sync-acls false
    
    Change-Id: I7eb3523fa72b8fed830efc98138891244e830d65
    BUG: 1187021
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/10001
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 86fa9298ea9d04766c0a693192e6660ad4b02165
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Mar 30 09:04:15 2015 +0200

    changelog xlator: avoid unsupported threaded event-poll usage
    
    The changelog xlator was modified to use a poller thread, which uses
    the same event pool as the xlator stack. Unfortunately, such threaded
    usage of event pool is not supported by event-poll code, only
    event-epoll supports it. As a result, platforms such as NetBSD that
    lack epoll support got broken.
    
    The fix is to remove the poller thread, which does not cause any
    functionnality loss because the xlator stack event poll is
    functionnal. That lets NetBSD pass AFR tests again.
    
    BUG: 1129939
    Change-Id: I3d73cf58e2ed8d92d9e0191f7abda3c37dea4159
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10030
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8907f67ba215172b01a7018adcbb063fcc4570e9
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Mar 30 12:21:05 2015 +0530

    doc: restructure developer docs to new layout
    
    The developer oriented information is scattered in source
    and its very difficult to identify which are those.
    With this patch subdirs are created under developer-guide
    which will be the parent for developer notes. The changes
    suggested in http://review.gluster.org/#/c/8827/ are also
    included in this patch.
    
    Change-Id: I4c8510d52c49f4066225f72cac8f97f087d6c70c
    BUG: 1206539
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/10038
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit e3bd2387a5973df4548fe4a62b5dfc227a2bdc64
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Mar 26 16:58:22 2015 +0530

    tools/glusterfind: Changelog_init before changelog_register
    
    With the new Changelog RPC based approach, Changelog_init
    needs to be called before changelog_register
    
    BUG: 1206127
    Change-Id: I817b84016d3f9ffdf2ea7a4e177953fe14ccc323
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10009
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 8e2a0f35e0ac66e75f2dcbe6a9ca8815d4233edf
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Thu Feb 12 11:20:49 2015 +0530

    qemu-block: Fixing coverity issue(Unused value)
    
    Coverity ID: 1124889 1124889 1124889 1124889 1124889 1124889 1124889
    1124889 1124889 1124889 1124889
    
    Change-Id: I82d57022c4a06fb70573b4e9436f934185f8fb84
    BUG: 789278
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9642
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 4481b03ae2e8ebbd091b0436b96e97707b4ec41f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Mar 12 15:43:56 2015 +0530

    core : free up mem_acct.rec in xlator_destroy
    
    Problem:
    We've observed that glusterd was OOM killed after some minutes when volume set
    command was run in a loop.
    
    Analysis:
    
    Initially the suspection was in glusterd code, but a deep dive into the codebase
    revealed that while validating all the options as part of graph reconfiguration
    at the time of freeing up the xlator object its one of the member mem_acct is
    left over which causes memory leak.
    
    Solution:
    
    Free up xlator's mem_acct.rec in xlator_destroy ()
    
    Change-Id: Ie9e7267e1ac4ab7b8af6e4d7c6660dfe99b4d641
    BUG: 1201203
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9862
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit d2629aef8302c6b7d832063351c0ce1f2f2efbdd
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Sat Mar 21 15:57:13 2015 +0530

    glupy: correct the definition of GlusterFS in setup.py
    
    Change-Id: I31597a623b4ebf3d3129067eb20c661c910b97fe
    BUG: 1198849
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9958
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8a2e2b88fc21dc7879f838d18cd0413dd88023b7
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 26 11:25:58 2015 +0100

    mem-pool: invalidate memory on GF_FREE to aid debugging
    
    Debugging where memory gets free'd with help from overwriting the memory
    before it is free'd with some structures (repeatedly). The struct
    mem_invalid starts with a magic value (0xdeadc0de), followed by a
    pointer to the xlator, the mem-type. the size of the GF_?ALLOC()
    requested area and the baseaddr pointer to what GF_?ALLOC() returned.
    
    With these details, and the 'struct mem_header' that is placed when
    calling GF_?ALLOC(), it is possible to identify overruns and possible
    use-after-free. A memory dump (core) or running with a debugger is
    needed to read the surrounding memory of corrupt structures.
    
    This additional memory invalidation/poisoning needs to be enabled by
    passing --enable-debug to ./configure.
    
    Change-Id: I9f5f37dc4b5b59142adefc90897d32e89be67b82
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/10019
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6a3024fe5953f51b51a7b9c2867d59c9e54c6d03
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Mar 19 15:39:20 2015 +0530

    tools/glusterfind: Ignore .trashcan dir during Brick Crawl
    
    BUG: 1203650
    Change-Id: Icf81726ad34bd5cfec6d8e06763b02a159e84c2e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/10010
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit aff367a601351ff7bfbfc572d6ae0d4ffafae0f0
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Mar 30 05:43:12 2015 +0200

    Tests: portability fixes
    
    Fix various portability problems in mount-nfs-auth.t,
    quota-ancestry-building.t and trash.t:
    
    - dd bs=1M is not portable, use dd bs=1024k instead
    - dd bs=1MB is not portable iether, use dd bs=1000000 instead
    - After restarting NFS service, wait for it to become available
    - After killing a process, wait for it to terminate
    - BSD awk does not accept a=b="", use a=""; b="" instead
    - NetBSD displays the original program name in paenthesis at the end
      of ps output. Strip it using sed 's/ *([^()]*)$//' is we want just
      the command
    - Do no use umount $N0, which leads to many troubles solved by
      EXPECT_WITHIN $UMOUNT_TIMEOUT "Y" umount_nfs $N0
    - The -p option for mkdir must be before the directory name
    - du -b is not portable. Use ls -l instead.
    
    BUG: 1129939
    Change-Id: I3d44a10a37d47ebb6a263c206566487e3ffb85d8
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/10033
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 299f6ce2b17216a6c09d5345139b9a78f7505b24
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Mar 20 18:57:52 2015 +0530

    libgfapi: revamp glfs_new function
    
    Current glfs_new() function is not flexible enough to error out
    and destroy the struct members or objects initialized just before the
    error path/condition. This make the structs or objects to continue or
    left out with partially recorded data in fs and ctx structs and cause
    crashes/issues later in the code path. This patch avoid the issue.
    
    Change-Id: Ie4514b82b24723a46681cc7832a08870afc0cb28
    BUG: 1202492
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9903
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b247ff4b297481148ab2fe4c7b832aac85f6ad72
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Mon Mar 30 12:44:06 2015 +0530

    doc: Fix Jeff Darcy's links in docs
    
    Change-Id: I4bc859662088a55fe70714feb3c47ed02ad08e94
    BUG: 1206539
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/10041
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 7b3db6df564f1af1845b7f436e74ac6e838cd5b6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jan 16 14:28:09 2015 +0530

    glusterd: replace glusterd_volinfo_delete calls with glusterd_volinfo_unref
    
    volinfo has its own ref counting mechanism. While deleting a
    volinfo object its always wiser to check there is 0 reference
    to it and then delete it.
    
    Change-Id: I446bd83432bd94aa19e29c6026367dfc1231786f
    BUG: 1183463
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9462
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 3db5f3a41b7029ce8005d1e1cc01808a15cc6019
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Mar 24 16:29:13 2015 +0530

    features/trash : Discarding extended truncate for trash-translator
    
    Change-Id: I5c571cbb2d6da1e95831ec206639926722a9d281
    BUG: 1132465
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/9984
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b828932c1430bfc62d7c3c83fec8e4a79ca4dbe6
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Thu Feb 5 13:37:37 2015 +0530

    bd: coverity fixes, removing logically dead code and correcting checks
    
    Coverity CIDs:
        1128910
        1128911
        1128913
        1128912
        1134020
    
    Change-Id: I2d871723fbfe43f9ff6b3beba7a99b0d81d4aff5
    BUG: 789278
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9588
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f2c1261123798403dd254926db4f2008de4b6d84
Author: arao <arao@redhat.com>
Date:   Wed Feb 18 14:57:31 2015 +0530

    protocol-client: Removal of Dead Code
    
    CID: 1124448
    CID: 1124449
    Removal of the dead code in the 'out' label.
    
    Change-Id: Ibdd05cbb6e2204f6aefdf442698225883c2d7734
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9676
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dcff68eb2e9837a1db6634571e8e03fc57ff3182
Author: arao <arao@redhat.com>
Date:   Thu Feb 19 14:37:18 2015 +0530

    symlink-cache: Fixing coverity issues
    
    CID: 1124389
    Misspelt variable leading to dead code
    and memory leak, corrected.
    
    Change-Id: I1278f07f81e2db33640e0f289558d919343cb6ce
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9694
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9272b1cf5655fff625b254a1ea952dcefd3c3af1
Author: arao <arao@redhat.com>
Date:   Tue Feb 10 11:06:27 2015 +0530

    bd: Fixing dereference after null check(FORWARD_NULL)
    
    CID: 1128907
    The pointer variable 'bdatt' redirected to a goto label
    when the value was NULL and in the other condition when it is not NULL
    , hence the bdatt is again checked for NULL at 'reverse xattr' label.
    
    Change-Id: I2289cbf30fde9faf97e6eebd4902953a44049f9e
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9619
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 059e085752d09e841fd685e3ca53aeb2983cd48b
Author: arao <arao@redhat.com>
Date:   Thu Feb 12 15:27:00 2015 +0530

    protocol-client: Removal of Logically dead code.
    
    CID: 1124447
    The values of the pointer varibale checked,
    before going to out label was always NULL,
    hence dead code related to that is removed.
    
    Change-Id: I0f9b84c7feb34072814557ddd023f2ae1c64ef7e
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9646
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2355012f3843859d639819d2308f995e08e270e5
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Feb 9 12:56:17 2015 +0530

    cli : logically dead code removed
    
    CID : 1124396
          1124398
    
    Change-Id: I708703529bbfe78c295523d2f4b85a55566a6249
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9606
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 49d68945c01cdb29490de3ebbee42036ca23ef87
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Mon Feb 16 14:26:54 2015 +0530

    io-stats : null dereference coverity fix.
    
    CID      :1124502
    
    Change-Id: I2911be340e8e48a52e951d0f04f6a96f3c219fab
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9659
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d680cbb47a2f630bbe062b48f910528e7ffad97d
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Thu Feb 12 11:47:31 2015 +0530

    protocol-client : dead code removed.
    
    CID             : 1124415,1124416,
                      1124417,1124418,
                      1124419,1124420,
                      1124425,1124426,
                      1124427,1124428,
                      1124445,1124446.
    
    Change-Id: Ib140b8907f4548f41fccb8044772397760fff835
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9643
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 298e94f8049df7e89f77bbd3d42d3c91981d492c
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Fri Feb 6 16:29:09 2015 +0530

    protocol/client : logical dead code removed
    
        CID :112438{2,3,4,5}
             11244{03,04,05,06,07,08,09,10,11,12,13,14,30,31,32,33}
             11244{34,35,36,37,38,39,40,41,42,43,44,56,57,58,59,60}
             11244{61,62,63,64,65,66,67,68,69,70}
             1128902
    
    Change-Id: I1b53aeee83209728d5711540210d19314f4165bc
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9601
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b7d8567145b948c7a51b6ecccfd5ff5c10c5a17a
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Feb 17 17:17:40 2015 +0530

    posix : unchecked return value coverity fix.
    
    CID   : 1124364
    
    Change-Id: I1e16e3ff46b191ba2ea527e628c77a99a56f6c31
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9667
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 683145ae2a8abee02763cef2334556fd39fc635a
Author: shravantc <shravantc@ymail.com>
Date:   Fri Mar 27 17:44:01 2015 +0530

    doc : editing admin_ACLs.md
    
    Updating control entries
    
    Change-Id: Iad5c9dcdf03fe987d1048078db6158f0e7c737a8
    BUG: 1206539
    Signed-off-by: shravantc <shravantc@ymail.com>
    Reviewed-on: http://review.gluster.org/10027
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anjana Sriram <asriram@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 3b647e10124cfc22983b11bf9bfaa36289a2a42f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sun Mar 29 19:59:19 2015 +0530

    glusterd: Use txn_opinfo instead of global op_info in glusterd_volume_heal_use_rsp_dict
    
    Due to http://review.gluster.org/#/c/9908/ global opinfo is no more a valid
    place holder for keeping transaction information for syncop task.
    glusterd_volume_heal_use_rsp_dict () was referring to global op_info due to
    which the function was always asserting on the op code.
    
    Change-Id: I1d416fe4edb40962fe7a0f6ecf541602debac56e
    BUG: 1206655
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10034
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit d5a9607598cf02e50bce306cffe97990a50129c0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Mar 28 21:09:57 2015 +0530

    glusterd : fix memory overrun for opinfo.local_xaction_peers
    
    Due to incorrect sizeof local_xaction_peers was not allocated as intended which
    lead a memory overrun in gf_free while freeing local_xaction_peers.
    
    Change-Id: Ie4d63289aae51727eea091bce0e6cb0a496ce7cf
    BUG: 1204727
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/10032
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 0934432c51aef8ae7e890c3fc2ff2ae843b46698
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 19 15:21:12 2015 -0400

    socket: use TLS 1.2 instead of 1.0
    
    Change-Id: I96e9b37e4855f5e12b2dbecf1f0b0887b21ad5ad
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/9949
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 651514dd66019a9f37dfa96374e31dd497a18a59
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 24 11:36:59 2015 +0530

    features/shard: Bug fixes
    
    * Return number of bytes written in writev cbk on success
    * Eliminate separate inode table for sharding xlator.
    * Fix appearance of "shard" as an option within the
      volfile for subvolume of type features/shard.
    * Fix values of min and max allowed shard block size
    * Return @new as opposed to NULL in shard_create_gfid_dict() on success
    
    Change-Id: I6319d377a196d1c5ceed1f65d337ff8eabcb21f8
    BUG: 1205661
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/10003
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit eeef9bf8c93b9a11df6ef530924ba4ab44e0092a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 19 19:32:44 2015 +0100

    md-cache: cache virtual POSIX ACL xattrs
    
    http://review.gluster.org/9627 introduces two new virtual extended
    attributes that are used similar to the existing POSIX ACL xattrs. These
    new xattrs should get cached in the same way.
    
    BUG: 1185654
    Change-Id: I6294b4f9ade887e29f8bd8ae5a3642891df8a631
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9947
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bc71cc39881730c8592718a5045a744387bfaea4
Author: Anoop C S <achiraya@redhat.com>
Date:   Thu Mar 26 12:00:39 2015 +0530

    features/trash: Removing dead callbacks
    
    Since ftruncate create, mkdir, writev, readv and
    unlink calls are being re-directed to corresponding
    truncate calls, we no longer need their cbks. So
    removing those cbks for now.
    
    Change-Id: I41ecde7093a555b3bf69b66afaa8eca835b4982a
    BUG: 1132465
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/10002
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ff6accece4ea0461a5623ea9d66cacea1a3268f3
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 26 12:11:55 2015 -0400

    build: attr package dependency
    
    Already fixed in the Fedora dist-git glusterfs.spec
    
    Change-Id: Icad7c4527d4b83417cbb81957e7b5da8b4d36368
    BUG: 1184627
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/10016
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 28c446a4eaaecfba8115dbaf66b3820b9d53257b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 26 12:24:02 2015 +0530

    features/snapview-client: Don't free un-allocated memory
    
    Change-Id: I8636ced27448dde4f2c11370fe2026067d4a7e74
    BUG: 1203637
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10004
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1f655aed1e439935c24da86fa70f19fd9151e7e8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 25 15:32:42 2015 +0530

    cluster/ec: Use fd when appropriate for updating size/version
    
    Change-Id: I5d3aca101c8cdda406d31d06c40404fa6a2b7170
    BUG: 1192378
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9995
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 764ce1e2f627d398dac9cc95b3f12dbb243a8770
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 26 08:38:11 2015 -0400

    tests: fix spurious failures in bug-1190734.t (remove-brick)
    
    This is the second leading cause of spurious failures, including those
    in tests for other spurious-regression-failure fixes (creating a bit of
    a "catch 22" situation).  While these failures have been hard to
    reproduce except during full regression-test runs, two changes have been
    made that might make this test more resilient to certain types of
    failures.
    
     * Use a specific "ls" instead of a general "find" to list/count only
       the files we're interested in, without (possibly) including transient
       artifacts from the "remove-brick" command.
    
     * Retry the file count up to five times, just in case there are other
       transient conditions causing it to yield the wrong result.
    
    Also, "inlining" some of the functions for removing the brick might help
    to highlight exactly which command within those functions was failing.
    
    Change-Id: I5a462b91fb4e04d9e9a53cc60f9db11b89101107
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/10013
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d331c3196392dd6cf857b79388780bf03b802392
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Mar 20 03:13:27 2015 +0530

    geo-rep: Use gfchangelog context init API
    
    With the RPC based changes to {libgf}changelog, changelog_init
    is required before changelog_register.
    
    Change-Id: Id125b2bd2e51aaaffa22ecab463dfb739c50d83c
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    BUG: 1170075
    Reviewed-on: http://review.gluster.org/9993
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d15dedd8c99e84018a50130a8ffe5e971b9f7bd4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 26 21:08:12 2015 +0530

    xlators/lib: Handle NULL 'name' for marker xattrs
    
    Change-Id: I18f00b7e92f483673250821c457d1e8be2eef081
    BUG: 1200372
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10015
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c8a723ac7cbd7bdc8bd01350c56e15fd7fa5e7ca
Author: anand <anekkunt@redhat.com>
Date:   Thu Mar 26 13:15:48 2015 +0530

    glusterd: clean up global xaction_peer occurances
    
    Remove xaction_peers from glusterd_conf_t which was left out by
    http://review.gluster.org/#/c/9980/ patch
    
    Change-Id: I8494ec181ec11922861d7bad12c46d45e036637b
    BUG: 1204727
    Signed-off-by: anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/10006
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit bf8a5c9f21381690dc8ba25bcfba44619a6e2434
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Jun 17 17:44:11 2014 +0530

    tests: Added a script to test the glfs_fini hang fix
    
    The script has been added as '.sh' instead of '.t' to avoid regression
    tests failure which may happen due to instability of glfs_fini.
    
    In addition, there is still some support needed to compile libgfapi*
    tests in our current regression test framework.
    
    BUG: 1093594
    Change-Id: If66817f330320e8c092340008b36616e1d954127
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/8092
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 02c045790136fc6e979a82d4d7fa8d1d298478fb
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Mar 25 09:21:06 2015 -0400

    tests: fix rebalance_completed
    
    This was causing spurious faiures in bug-884455.t and possibly
    elsewhere.
    
    Change-Id: Iad6b7515ca0c7c485300f79dcd2477efc76877f8
    BUG: 1163543
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/9994
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit c54e546040a15d6f1751816f59bdfba430b5fde3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 26 12:38:36 2015 +0530

    glfsheal: Do not print pending heals for non-afr xls
    
    Change-Id: Ib9a1998b964af1435e86de2c861ecb1c0e9026c9
    BUG: 1203637
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/10005
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 01d96d97f1bae4f83321285c701b93f2a668ad25
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Mar 2 11:14:08 2015 +0100

    nfs: do not fail to start when optional RPC-programs fail to register
    
    Some RPC-programs are not strictly required for the NFS-server. When
    these optional protocols fail to get registered at the portmapper, there
    is no need to fail the starting of the NFS-server.
    
    Required RPC-programs:
     - NFS
     - MNT
    
    Optional RPC-programs:
     - NLM
     - ACL
    
    Change-Id: Ife8ad871cff47554e3f42eb457c76431d0181964
    BUG: 1205579
    Tested-by: Brad Hubbard <bhubbard@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9988
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit c8e095765c5ef72df9979f917b1b8e66cd8d0115
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Mar 20 11:22:50 2015 +0530

    cli: log gluster version in cli init
    
    Change-Id: I4994043d303212da795c76867a7ee4355d318a8c
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9951
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7cd58994262d2d622c1533c6f7a905106a1cf197
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Mar 25 10:39:20 2015 +0530

    glusterd: clean up global xaction_peer occurances
    
    With http://review.gluster.org/#/c/9972/ there is no more need to maintain
    xaction_peers in glusterd_conf_t. This patch cleans up code for all the
    occurances of xaction_peers.
    
    Change-Id: I4fbf2df0fa9b8a8751029be36be7f76f6464cc76
    BUG: 1204727
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9980
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 087ad8a001c77ec9703a0a74256819cf99cc31d4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Mar 24 11:27:52 2015 +0530

    glusterd: Maintain local xaction_peer list for op-sm
    
    http://review.gluster.org/9269 addresses maintaining local xaction_peers in
    syncop and mgmt_v3 framework. This patch is to maintain local xaction_peers list
    for op-sm framework as well.
    
    Change-Id: Idd8484463fed196b3b18c2df7f550a3302c6e138
    BUG: 1204727
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9972
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f64666f113e7f0d3f7061dfed7e6e24928e85161
Author: Anoop C S <achiraya@redhat.com>
Date:   Wed Mar 25 19:51:41 2015 +0530

    features/ctr: Removing rpc-lib, rpc-xdr and api from CPPFLAGS
    
    Changetimerecorder doesn't seem to use rpc-lib, rpc-xdr
    and gfapi in the source. So removing those from Makefile.am
    
    Change-Id: I21c71db6212c10ba3821c6c456958a45c5312d41
    BUG: 1198849
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/9997
    Reviewed-by: Joseph Fernandes <josferna@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 21cd43cfd62f69cd011fced7ebec93b9347f9fce
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 11 17:43:12 2015 +0530

    libxlator: Change marker xattr handling interface
    
    - Changed the implementation of marker xattr handling to take just a
      function which populates important data that is different from
      default 'gauge' values and subvolumes where the call needs to be
      wound.
    - Removed duplicate code I found while reading the code and moved it to
      cluster_marker_unwind. Removed unused structure members.
    - Changed dht/afr/stripe implementations to follow the new implementation
    - Implemented marker xattr handling for ec.
    
    Change-Id: Ib0c3626fe31eb7c8aae841eabb694945bf23abd4
    BUG: 1200372
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9892
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 18dd162e00c8655648cea702bdb7b8bf25f1da97
Author: vmallika <vmallika@redhat.com>
Date:   Thu Mar 19 07:02:24 2015 +0530

    posix: handle failure from posix_resolve
    
    When building ancestory, posix_resolve gets the inode
    from the gfid. We need to handle the failure case from
    this function
    
    Change-Id: I19f0f0c739686b1b0ef96309212aa1c7911b3589
    BUG: 1203629
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9941
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 00863dde3984030674d946de9fe94d5c07334c5e
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Mar 23 19:49:19 2015 +0530

    Fixing build of xlator/cluster/dht/src/dht-rebalance.c when tiering is disabled
    
    1) Removed unnecessary include tier.h in dht-rebalance.c
    2) tier xlator will only compile when tiering is enabled in configure.ac
    
    Change-Id: Ia21aa9ff403506dc898a83236e9e2d382a0594da
    BUG: 1204604
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/9973
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1579d633dbeeeede20d016bbec806a00688e32f3
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Tue Mar 24 18:20:42 2015 +0530

    glusterd: bitrot scrub-throttle/scrub-frequency/scrub option handling
    
    CLI commands for bitrot features:
    volume bitrot <volname> {scrub-throttle frozen|lazy|normal|aggressive}
    volume bitrot <volname> {scrub-frequency daily|weekly|biweekly|monthly}
    volume bitrot <volname> {scrub pause|resume}
    
    These commands will handle their options and set respective value in
    dictionary.
    
    Change-Id: I1e8aa1b1c7d91a7f0faec9a2968b3072f42f8ba8
    BUG: 1170075
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9985
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 91708968d01b253ee1ebcec1fdc3d602435144ef
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 24 12:56:09 2015 +0530

    glusterd: Prevent possible dealock in glusterd_friend_remove
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      b02290e Prevent possible dealock in glusterd_friend_remove
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: I1efeaf18f2054f4252ee95244908613542d209d9
    BUG: 1205186
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/9979
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 891c7d0fad16e7f0f51af217a8aad0a653a353d7
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 24 12:15:19 2015 +0530

    glusterd: Prevent possible deadlock due to glusterd_quorum_count
    
    Also rename the macro glusterd_quorum_count to GLUSTERD_QUORUM_COUNT so
    that it stands out as a macro.
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      0fbd7ba Prevent possible deadlock due to glusterd_quorum_count
      5da3062 Rename glusterd_quorum_count to GLUSTERD_QUORUM_COUNT
      b3aa3c4 Enclose GLUSTERD_QUORUM_COUNT definition in a do-while block
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: Ic4b3949f303d72ce53e0139f62b83b8d13fb4e47
    BUG: 1205186
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/9978
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit fb81ee019655f8ce56f1610568526e51c49e8a11
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Mar 23 16:23:00 2015 -0400

    ganesha-ha: ganesha-ha.sh --status (one-liner) implementation
    
    Change-Id: I17b7f6864dd8c1f89500a4bb89f1c249835e68da
    BUG: 1188184
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/9974
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 6372bea9583fa77b77b48b2389257da2a115e167
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Mar 24 10:54:25 2015 +0100

    rpm: move libgfdb to the glusterfs-server package
    
    libgfdb is only used by processes that run on Gluster servers. There is
    no need to have this library (and its sqlite dependency) on any system
    that installs a glusterfs package.
    
    BUG: 1194753
    Change-Id: I6b7fdc70210ef2a847efd596a0c995f0a4cf5d9b
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9983
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit d71418ac4e2da989fc49eece4e2acbb9288b71f9
Author: Nandaja Varma <nandaja.varma@gmail.com>
Date:   Wed Feb 18 16:40:03 2015 +0530

    glusterd: Fixing wrong array comparison (Coverity fix)
    
    Coverity CID: 1256175
    
    Change-Id: Ib29fc2eaa54a7ce8369918e68bf117d0f04ca94d
    BUG: 789278
    Signed-off-by: Nandaja Varma <nandaja.varma@gmail.com>
    Reviewed-on: http://review.gluster.org/9679
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cd3d34289c92f01843a866f4432bdd2da1ee59db
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Feb 18 17:01:21 2015 +0530

    doc: document bit-rot feature
    
    Change-Id: Ibad640d01975906b7642c76a1649e3e272f3a8bc
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9712
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 866c64ba5e29a90b37fa051061a58300ae129a2c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Mar 13 21:23:20 2015 +0530

    features/bit-rot: filesystem scrubber
    
    Scrubber performs signature verification for objects that were
    signed by signer. This is done by recalculating the signature
    (using the hash algorithm the object was signed with) and
    verifying it aginst the objects persisted signature. Since the
    object could be undergoing IO opretaion at the time of hash
    calculation, the signature may not match objects persisted
    signature. Bitrot stub provides additional information about
    the stalesness of an objects signature (determinted by it's
    versioning mechanism). This additional bit of information is
    used by scrubber to determine the staleness of the signature,
    and in such cases the object is skipped verification (although
    signature staleness is performed twice: once before initiation
    of hash calculation and another after it (an object could be
    modified after staleness checks).
    
    The implmentation is a part of the bitrot xlator (signer) which
    acts as a signer or scrubber based on a translator option. As
    of now the scrub process is ever running (but has some form of
    weak throttling mechanism during filesystem scan). Going forward,
    there needs to be some form of scrub scheduling and IO throttling
    (during hash calculation) tunables (via CLI).
    
    Change-Id: I665ce90208f6074b98c5a1dd841ce776627cc6f9
    BUG: 1170075
    Original-Author: Raghavendra Bhat <rabhat@redhat.com>
    Original-Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9914
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7927e8747c731dbb105e93ae66c336338f48f0e6
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sun Feb 15 15:05:19 2015 +0530

    features/bit-rot: Implementation of bit-rot xlator
    
    This is the "Signer" -- responsible for signing files with their
    checksums upon last file descriptor close (last release()).
    The event notification facility provided by the changelog xlator
    is made use of.
    
    Moreover, checksums are as of now SHA256 hash of the object data
    and is the only available hash at this point of time. Therefore,
    there is no special "what hash to use" type check, although it's
    does not take much to add various hashing algorithms to sign
    objects with. Signatures are stored in extended attributes of the
    objects along with the the type of hashing used to calculate the
    signature. This makes thing future proof when other hash types
    are added. The signature  infrastructure is provided by bitrot
    stub: a little piece of code that sits over the POSIX xlator
    providing interfaces to "get or set" objects signature and it's
    staleness.
    
    Since objects are signed upon receiving release() notification,
    pre-existing data which are "never" modified would never be
    signed. To counter this, an initial crawler thread is spawned
    The crawler scans the entire brick for objects that are unsigned
    or "missed" signing due to the server going offline (node reboots,
    crashes, etc..) and triggers an explicit sign. This would also
    sign objects when bit-rot is enabled for a volume and/or after
    upgrade.
    
    Change-Id: I1d9a98bee6cad1c39c35c53c8fb0fc4bad2bf67b
    BUG: 1170075
    Original-Author: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9711
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 31f841d6b35c242942b6bdcbfdc83cf548d5235a
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Mar 13 22:00:22 2015 +0530

    cli/glusterd: CLI interface for BitRot detection
    
    * BitRot enable/disable CLI per volume
    * Volfile generation for Scrubber
    * Relevant glusterd infrastructure
    
    Change-Id: I1212af63f93ecc52b22ee6da920e1664f66a1e39
    BUG: 1170075
    Original-Author: Raghavendra Bhat <raghavendra@redhat.com>
    Original-Author: Venky Shankar <vshankar@redhat.com>
    Original-Author: Gaurav Kumar Garg <ggarg@redhat.com>
    Original-Author: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/9986
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 84db9f8271f150fbb6024186f7f681e941731280
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jan 7 11:14:31 2015 +0530

    mgmt/glusterd: generate volfile for BitD
    
    * Implement the skeleton of bit-rot xlator.
    
    Original-Author: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Signed-off-by: Anand Nekkunti <anekkunt@redhat.com>
    Change-Id: If33218bdc694f5f09cb7b8097c4fdb74d7a23b2d
    BUG: 1170075
    Reviewed-on: http://review.gluster.org/9710
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit a37f3ca2b286732fff18f0b0897d8bb1713c89b7
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Mar 5 14:50:26 2015 +0530

    libglusterfs: check and act based on gf_malloc result.
    
    Change-Id: If54f4be7db8b6f98e65570b09c07251e21ebae15
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9837
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 33a32b8efac9dbc159c0ed74b9a2a4c6ab686b98
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sun Mar 15 04:26:15 2015 +0530

    Update MAINTAINERS file
    
    - Added maintainers for BitRot detection
    
    Change-Id: Ib5dae02176372e33c7b616f161d909815edbb53f
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9916
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ef158c75d1d6fac76635e95a9a43145433169b44
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Aug 30 16:15:36 2014 +0530

    read-only: read-only/worm translator should be in brick graph by default
    
    Problem:
    read-only/worm translator is not loaded by default in brick graph because of which
    when read-only option is set through volume set volume still remains writable
    untill the bricks are restarted as the translator does not have an inmemory flag
    to decide whether the read-only/worm option is turned or not.
    
    Solution:
    read-only/worm should be loaded by default in brick graph and the read-only/worm
    option can be toggled through volume set command. read-only/worm translator now'
    has an in-memory flag to decide whether the volume is read-only or not and based
    on that either reject the fop or proceed.
    
    Change-Id: Ic79328698f6a72c50433cff15ecadb1a92acc643
    BUG: 1134822
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8571
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a20101e2e4d5f5595655544cfc798eb1d445638c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Feb 9 18:28:21 2015 +0530

    Bitrot Stub
    
    Bitrot stub implements object versioning required for identifying
    signature freshness. More details about versioning is explained
    as a part of the "bitrot feature documentation" patch.
    
    Change-Id: I2ad70d9eb109ba4a12148ab8d81336afda529ad9
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9709
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3c474a042aed68659fe0cfdf32e01285bde9f689
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sun Mar 15 03:43:49 2015 +0530

    core: Add inode context merge callback
    
    Certain translators may require to update the inode context
    of an already linked inode before unwinding the call to the
    client. Normally, such a case in encountered during parallel
    operations when a fresh inode is chosen at call (wind) time.
    In the callback path, one of inodes is successfully linked
    in the inode table, thereby the other inodes being thrown
    away (and the inode pointers for these calls being pointed
    to the linked inode).
    
    Translators which may have strict dependency on the correct
    value in the inode context would get stale values in inode
    context. This patch introduces a new callback which provides
    gives translators an opportunity to "patch" their respective
    inode contexts. Note that, as of now, this callback is only
    invoked during create()s unwind path. Although this might
    needed to be done for all dentry fops and lookup, but let
    that be done as an when required (bitrot stub requires
    this *only* for create()).
    
    Change-Id: I6cd91c2af473c44d1511208060d3978e580c67a6
    BUG: 1170075
    Original-Author: Raghavendra Bhat <rabhat@redhat.com>
    Original-Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9913
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 9f5addd987861d0a3a1144d576221a7f93af0970
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Feb 25 22:21:32 2015 +0530

    features/changelog: Make use of IPC fop
    
    Translators which wish to send event notifications can send
    "down" an IPC FOP with op_type as GF_IPC_TARGET_CHANGELOG
    and xdata carrying event structures (changelog_event_t).
    
    Change-Id: I0e5f8c9170161c186f0e58d07105813e34e18786
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9775
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 470d5c4af7f85809997a77af187c8f430b0354c8
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sat Mar 21 19:59:45 2015 +0530

    libgfchangelog: cleanups on disconnection
    
    [WIP patch as of now, just needs a little tweak]
    
    A pending TODO in the code caused regressions to fail as
    bitrot daemons are spawned during volume start (equivalent
    to enabling bitrot by default). The problematic part that
    casued such failures is during brick disconnections with
    unsafe handling of event data structured in the code.
    
    With this patch, data structures are properly cleaned up
    with care taken to cleanup all accessors first. This also
    fixes potential memory leaks which was bluntly ignored
    before.
    
    Change-Id: I70ed82cb1a0fb56c85ef390007e321a97a35c5ce
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    original-author: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9959
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 9c9f3f368c693b1cf5f67f3d8d4e599d4ba61383
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Mar 19 10:09:04 2015 +0530

    libgfchangelog: Fix faulty reference to xlator context
    
    Problem:
    libgfchangelog initializes global xlator on library load (via
    constructor: _ctor) and mangles it's xlator context thereby
    messing with certain important members of the command structure.
    On receiving an RPC disconnection event, if the point-of-execution
    was in libgfchangelogs context, accessing ->cmd_args during RPC
    notify resulted in a segfault.
    
    Fix:
    Since the libarary needs to be able to work with processes that
    have a notion of an xlator (THIS in particular) and without it,
    care needs to be taken to allocate the global xlator when needed.
    Moreover, the actual fix is to use the correct xlator context
    in both cases. A new API is introduces when needs to be invoked
    by the conusmer (although this could have been done during
    register() call, keeping it a separate API makes thing flexible
    and easy).
    
    Test:
    The issue is observed when a brick process goes offline. This is
    triggered when test cases (.t's) are run in bulk, since each
    test essestially spawns bricks processes (on volume start) and
    terminates them (volume stop). Since bitrot daemon, as of now,
    spawns upon volume start, the issue is much observed when the
    volume is taken offline at the end of each test case. With this
    fix, running the basic and core test cases along with building
    the linux kernel has passed without daemon segfaults.
    
    Thanks to Johnny (rabhat@) for helping in debugging the issue
    (and with the fix :)).
    
    Change-Id: I8d3022bf749590b2ee816504ed9b1dfccc65559a
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9953
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 191ab5693d3c9a0cdedc66bb24dd5efa535963d9
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Wed Mar 18 14:12:03 2015 +0530

    features/trash: Handling hardlinks in trash translator
    
    In the current code of trash translator, file is moved to
    trash directory without checking whether it is the last
    hardlink.This may lead to inconsistency for a file in that
    gluster volume.To avoid those scenarios,so a file is moved
    to trash directory only if it is the last hardlink.
    
    Change-Id: Id098e53a2236c6406ef91e6e2599ea2cff9bace3
    BUG: 1132465
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/9926
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 432355c9c6ca5937745f5d2b87ba391ad4877c92
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 6 21:09:10 2015 +0530

    cluster/ec: Refactor ec-dir-write
    
    - Also fixed iatt_combine to go over all the valid iatts
    
    Change-Id: I1d52d705ed0437f602357acde3e479cedb748681
    BUG: 1199767
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9827
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0940364b453fc37cb3e1844a743cf30c8ab2afc6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Mar 17 16:47:22 2015 +0530

    glusterd: Do not use global opinfo in syncop
    
    Global opinfo should not be referred by syncop framework as it uses local
    txn_opinfo for every transaction. There is one place in the codebase where the
    global opinfo is set with the local txn_opinfo which can lead to an incorrect
    opinfo for an on-going op-sm transaction which refers to the same global opinfo.
    
    Change-Id: Ida63a8871b8d03fe646146eddfd3f2473f1b1d7c
    BUG: 1202745
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9908
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2308c07b9d52b28f371388b9393b17508b2ddccd
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 19 10:38:23 2015 +0100

    build: let checkpatch check for a trailing dot
    
    The subject of a patch should not end with a dot (.). It is not common
    to have subjects of emails end with a dot, and neither is it common for
    patches.
    
    Change-Id: Id090241393aee3ca99df4887bdb2d7a7a8913164
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9940
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ira Cooper <ira@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 889044594614756243259a22ed1448408a2b33ac
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Mar 22 13:17:46 2015 +0100

    build: only include sys/sysctl.h when sysctl() is used
    
    BUG: 1198849
    Change-Id: I9597b4b7f37994865f88b99651ea9ec89787f5cf
    Reported-by: Adam Borowski <kilobyte@angband.pl>
    URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778790
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9963
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 709b5c158c40e5a8b8f5c4d0ad495550bec8bd4e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Mar 22 12:21:05 2015 +0100

    tests: move test-cases into their own component subdirectories
    
    Change-Id: I0327a48ba5a1a217f54557386b1ae1b986702340
    BUG: 1178685
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9962
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 8992b549df536eaf5ff6315221f66191f2eff7ef
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Mar 22 12:13:42 2015 +0100

    tests: move libgfapi tests to their own gfapi subdir
    
    Also, glfs_fini() is currently not stable yet, this test case causes
    many regression failures. The .t file has been renamed to .sh so that
    the test does not get run automatically, but can be run easily by hand.
    
    BUG: 1093594
    Change-Id: I63fa4ddf798a505bc94d13d32dd02f22a9b7ab73
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9961
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit a2d0d9f60a90951b7b5a59ce6c85cea786f3c31d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Mar 22 14:44:08 2015 +0100

    build: tier.h does not need to include sys/xattr.h
    
    FreeBSD does not have sys/xattr.h, including it in tier.h breaks
    building on FreeBSD. There is nothing in tier.h that seems to require
    definitions from the sys/xattr.h header, just remove it.
    
    BUG: 1194753
    Change-Id: If970272a0ce7728e0f18e5ae026880688ac31408
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9965
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>

commit e47fd239db2da78081daf1f451313956b53435ef
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Mar 22 13:38:03 2015 +0100

    build: pass SQLITE_CFLAGS while building dht files that include tier.h
    
    Building on FreeBSD has been broken by http://review.gluster.org/9724
    which introduces the cluster/tiering xlator. The CFLAGS passed to the
    compiler do not include the path where sqlite3.h can be found.
    
    In fact, an attempt was made to pass the flags on, but a later variable
    overwrite these again.
    
    BUG: 1194753
    Change-Id: I1c890fa9a0d82492726306fe6b03bd50ca985e31
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9964
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>

commit 507f3251f39405332fc1181e7004b60637f26be6
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Sun Mar 22 15:27:14 2015 -0400

    cluster/dht: Fix spurious failure in tier test.
    
    Need to wait for a few seconds for rebalancing to complete
    before stopping volume.
    
    Change-Id: Ib81c02645240e7d74ebfb3e31ccbc612fc77b119
    BUG: 1194753
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/9966
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 20355992e8eed7d3ed78a23bc7e922d6ae94860d
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Sun Feb 22 11:05:58 2015 -0500

    cluster/dht: Add tier translator.
    
    The tier translator shares most of DHT's code. It differs in how
    subvolumes are chosen for I/Os, and how file migration (cache promotion
    and demotion) is managed. That different functionality is split to either
    DHT or tier logic according to the "tier_methods" structure.
    
    A cache promotion and demotion thread is created in a manner
    similar to the rebalance daemon. The thread operates a timing
    wheel which periodically checks for promotion and demotion candidates
    (files). Candidates are queued and then migrated. Candidates must exist on
    the same node as the daemon and meet other critera per caching policies.
    
    This patch has two authors (Dan Lambright and Joseph Fernandes). Dan
    did the DHT changes and Joe wrote the cache policies. The fix depends on
    DHT readidr changes and the database library which have been submitted
    separately.  Header files in libglusterfs/src/gfdb should be reviewed in
    patch 9683.
    
    For more background and design see the feature page [1].
    
    [1]
    http://www.gluster.org/community/documentation/index.php/Features/data-classification
    
    Change-Id: Icc26c517ccecf5c42aef039f5b9c6f7afe83e46c
    BUG: 1194753
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/9724
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 8aa13c8e285ad496ed7c8511ae0b735eed73ebd4
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Mar 18 10:37:00 2015 +0530

    geo-rep/gverify: Ignore .trashcan while checking slave is empty.
    
    With trash translator, '.trashcan' is created in gluster volume
    during init. So geo-rep create used to fail, with slave not
    being empty. The gverify script should ignore '.trashcan' while
    checking whether slave is empty.
    
    Change-Id: Ib7ee265c6aa99b63c7ccf103747d47a6f756ad35
    BUG: 1203086
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9921
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 24e01e407a04db4983e45fc5338e4a732df7da28
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Mar 20 19:28:22 2015 +0530

    tiering/CTR:build CTR only if tiering is enabled
    
    Thanks to Niels for this fix
    
    Change-Id: I9a13c3de3ed5d4eb06c6af61a2519bf27f1b6259
    BUG: 1194753
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9957
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit f10dd13a285adb287fda452f9f3557f35ba178e1
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Mar 13 15:33:06 2015 +0530

    doc: adding logging details in admin guide.
    
    Change-Id: I4552d98ff6b51e8171865cd0a569f6e793db9dd0
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9876
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 7fea544079c0fdc2d1d6a29e039cc925f81b2117
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 19 20:30:13 2015 +0100

    build: remove broken and unused _la_LIBADD variable
    
    While building, the following warning is displayed:
    
      xlators/features/arbiter/src/Makefile.am:7: variable `_la_LIBADD' is defined but no program or
      xlators/features/arbiter/src/Makefile.am:7: library has `_la' as canonical name (possible typo)
    
    The _la_LIBADD really seems like a typo, dropping it should not be harmful to
    anything, except for the warning that will now be gone.
    
    BUG: 1199985
    Change-Id: I3f3ba911f59df2e51fdc6387295fff4bbcc5a12d
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9950
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e3f2ebfe6b621e84b0386d5a0613829241401d93
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 19 16:48:16 2015 +0100

    build: pass the correct CFLAGS and LDFLAGS when linking (to) libgfdb
    
    Change-Id: Id9a7d0f457d9759ab7d0a52a4000b5ae36d211f8
    BUG: 1194753
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9946
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6f389fbb812b384bdd9bf4a20e86930505531996
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Nov 21 11:47:23 2014 +0530

    features/shard: Introducing sharding translator
    
    Based on the high-level design by Anand V. Avati which can be found @
    https://gist.github.com/avati/af04f1030dcf52e16535#sharding-xlator-stripe-20
    
    Still to-do:
            * complete implementation of inode write fops - [f]truncate,
              zerofill, fallocate, discard
            * introduce transaction mechanism in inode write fops
            * complete readv
            * Handle open with O_TRUNC
            * Handle unlinking of all shards during unlink/rename
            * Compute total ia_size and ia_blocks in lookup, readdirp, etc
            * wind fsync/flush on all shards
    
            Note: Most of the items above are related. Once we come up
            with a clean way to determine the last shard/shard count for
            a file/file size and the mgmt of sparse regions of the file,
            implementing them becomes trivial.
    
    Change-Id: Id871379b53a4a916e4baa2e06f197dd8c0043b0f
    BUG: 1200082
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9841
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 32ed7aa5ad7049a9d85c795f997336c0366151a8
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 19 12:33:51 2015 +0000

    afr: arbiter xlator
    
    This patch adds the arbiter translator into the tree. This is a server
    side xlator used for replica 3 volumes. It sits above posix and will be
    loaded on the 3rd (last) brick of every afr subvolume in a replica 3
    configuration. It intercepts inode read/write operations: reads are
    unwound with ENOTCONN, inode writes are unwound with success without
    actually passing them down to posix. Metadata operations are allowed to
    pass through.
    
    The CLI for creating a 3 way replica with arbiter is also added but kept
    disabled (A 'normal' 3 way replica is created instead).
    
    This patch is a part of the arbiter logic implementation for 3 way AFR,
    details of which can be found at http://review.gluster.org/#/c/9656/
    
    Change-Id: I395b81f49d5da52c466daf5c8518f1bbad9c16fa
    BUG: 1199985
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9840
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 61489c1725f048c2e34a08e73f0ab367bbf673c1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 19 13:12:02 2015 +0100

    build: correctly install the snap_scheduler tools
    
    The current way of installing the snap-scheduler tools breaks the
    building of RPMs. The tools should be installed in /usr/sbin and there
    is no need to change the attributes/permissions after the installation.
    
    Change-Id: I1b8e206748617fb000d956b1b5da52d126971c29
    BUG: 1203557
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9939
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d06692d1deec425f74747e2c463e56f7eca981c8
Author: Anuradha <atalur@redhat.com>
Date:   Wed Feb 25 15:09:28 2015 +0530

    cluster/afr : enable inspection & resolution of files in split-brain
    
    Part 2/2 patch to enable users analyze and resolve
    split-brain.
    
    This patch enables :
    1) Users to inspect the files in data and metadata split-brain.
    2) Resolve the split-brain.
    Both using a series of setfattr commands.
    
    Consider a volume "test" with 2 bricks.
    
    1) To inspect a file f1:
    setfattr -n replica.split-brain-choice -v test-client-0 f1
            After the execution of this command, if no read_subvol
    is found, reads will be served from test-client-0 (corresponding
    to brick-0).
    
    2) To resolve split-brain :
    setfattr -n replica.split-brain-heal-finalize -v test-client-0 f1
            Execution of this command will lead to the resolution
    of data and metadata split-brain with subvol mentioned in the
    command (test-client-0 here) as the source and the rest as sink.
    
    Change-Id: Ia20f3ee5abd3119e3d54fcc599f1e55ac65fd179
    BUG: 1191396
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9743
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6f71bc02df5bd177c2f5dbf4e54b2af1525ab979
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Feb 25 16:11:23 2015 -0500

    glusterd: CLI commands to create and manage tiered volumes.
    
    A tiered volume is a normal volume with some number of new bricks
    representing "hot" storage. The "hot" bricks can be attached or
    detached dynamically to a normal volume. When this happens, a new graph
    is constructed. The root of the new graph is an instance of the tier
    translator. One subvolume of the tier translator leads to the old volume,
    and another leads to the new hot bricks.
    
    attach-tier <VOLNAME> [<replica> <COUNT>] <NEW-BRICK> ... [force]
    
    volume detach-tier <VOLNAME> [replica <COUNT>] <BRICK>
    ... <start|stop|status|commit|force>
    
    gluster volume rebalance <volume> tier start
    
    gluster volume rebalance <volume> tier stop
    
    gluster volume rebalance <volume> tier status
    
    The "tier start" CLI command starts a server side daemon. The daemon
    initiates file level migration based on caching policies. The daemon's
    status can be monitored and stopped.
    
    Note development on the "tier status" command is incomplete. It will be
    added in a subsequent patch.
    
    When the "hot" storage is detached, the tier translator is removed
    from the graph and the tiered volume reverts to its original state as
    described in the volume's info file.
    
    For more background and design see the feature page [1].
    
    [1]
    http://www.gluster.org/community/documentation/index.php/Features/data-classification
    
    Change-Id: Ic8042ce37327b850b9e199236e5be3dae95d2472
    BUG: 1194753
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/9753
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 99586305f66d6b5e81542139d84fbf111ace2554
Author: Anuradha <atalur@redhat.com>
Date:   Mon Mar 16 15:18:57 2015 +0530

    doc: heal info and split-brain resolution document
    
    Documentation for gluster volume heal info and split-brain
    resolution.
    
    Change-Id: Iacb30dff939c1acf06c24bd8844294d4a90ab38d
    BUG: 1154599
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9595
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit c270d4da8d0cc0a3856969f10ef6415be5615544
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Mar 18 22:07:19 2015 +0100

    gfapi: space/tab conversion in gfapi.map
    
    The last two patches incorrectly add symbols indented by spaces. The
    rest of the file uses tabs. This change corrects these occurences.
    
    Change-Id: Ibfb057b78c1203a594bfeb73a2955e798e86c8e1
    BUG: 1185654
    Reported-by: Kaleb S. Keithley <kkeithle@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9937
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b4a0db5ee3b827268fe1aeeed32ad7d417460c50
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Mar 18 19:55:31 2015 +0530

    Adding ChangeTimeRecorder(CTR) Xlator to GlusterFS
    
    **********************************************************************
                                ChangeTimeRecorder(CTR) Xlator           |
    **********************************************************************
    ChangeTimeRecorder(CTR) is server side xlator(translator) which sits
    just above posix xlator. The main role of this xlator is to record the
    access/write patterns on a file residing the brick. It records the
    read(only data) and write(data and metadata) times and also count on
    how many times a file is read or written. This xlator also captures
    the hard links to a file(as its required by data tiering to move
    files).
    
    CTR Xlator is the consumer of libgfdb.
    
    To Enable/Disable CTR Xlator:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
     gluster volume set <volume-name> features.ctr-enabled {on/off}
    
    To Enable/Disable Frequency Counter Recording in CTR Xlator:
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
     gluster volume set <volume-name> features.record-counters {on/off}
    
    Change-Id: I5d3cf056af61ac8e3f8250321a27cb240a214ac2
    BUG: 1194753
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/9935
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1755ee2765f3d1c9c26d51a49ad63d133932710
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    glusterfsd: add "print-netgroups" and "print-exports" command
    
    NFS now has the ability to use a separate file for "netgroups" and
    "exports". An administrator should have the ability to check the
    validity of the files before applying the configuration.
    
    The "glusterfsd" command now has the following additional arguments that
    can be used to check the configuration:
    
       --print-netgroups: Validate the netgroups file and print it out
       --print-exports: Validate the exports file and print it out
    
    BUG: 1143880
    Change-Id: I24c40d50110d49d8290f9fd916742f7e4d0df85f
    URL: http://www.gluster.org/community/documentation/index.php/Features/Exports_Netgroups_Authentication
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9365
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 5394f3cf60b0815d2919d24e9945ba47e3bb1f9b
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Feb 3 19:05:28 2015 +0530

    contrib/timer-wheel: import linux kernel timer-wheel
    
    This patch imports timer-wheel[1] algorithm from the linux
    kernel (~/kernel/time/timer.c) with some modifications.
    
    Timer-wheel is an efficent way to track millions of timers for
    expiry. This is a variant of the simple but RAM heavy approach
    of having a list (timer bucket) for every future second.
    Timer-wheel categorizes every future second into a logarithmic
    array of arrays. This is done by splitting the 32 bit "timeout"
    value into fixed "sliced" bits, thereby each category has a
    fixed size array to which buckets are assigned.
    
    A classic split would be 8+6+6+6 (used in this patch) which
    results in 256+64+64+64 == 512 buckets. Therefore, the entire
    32 bit futuristic timeouts have been mapped into 512 buckets.
    
    [
       NOTE:
         There are other possible splits, such as "8+8+8+8", but
         this patch sticks to the widely used and tested default.
    ]
    
    Therfore, the first category "holds" timers whose expiry range
    is between 1..256, the next cateogry holds 257..16384, third
    category 16385..1048576 and so on. When timers are added,
    unless it's in the first category, timers with different
    timeouts could end up in the same bucket. This means that the
    timers are "partially sorted" -- sorted in their highest bits.
    
    The expiry code walks the first array of buckets and exprires
    any pending timers (1..256). Next, at time value 257, timers
    in the first bucket of the second array is "cascaded" onto
    the first category and timers are placed into respective
    buckets according to the thier timeout values. Cascading
    "brings down" the timers timeout to the coorect bucket
    of their respective category. Therefore, timers are sorted
    by their highest bits of the timeout value and then by the
    lower bits too.
    
    [1] https://lwn.net/Articles/152436/
    
    Change-Id: I1219abf69290961ae9a3d483e11c107c5f49c4e3
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9707
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 2bf23b5b9be9ad600d71474a8f94b62765344b7c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Mar 18 19:50:03 2015 +0530

    geo-rep: Ignore .trashcan during xsync crawl.
    
    With trash feature, .trashcan directory gets created
    at each export directory. Xsync picks .trashcan to sync
    and fails with EPERM. Xsync should ignore .trashcan
    directory.
    
    Change-Id: I45bd226c96011ace2c40dd2de878d886c7d34ce5
    BUG: 1203293
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9934
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 87a9d23627586a5d5cd8a502a08ecbdb6f0f7bb2
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Feb 3 19:03:30 2015 +0530

    libglusterfs/rot-buffs: rotational buffers
    
    This patch introduces rotational buffers aiming at the classic
    multiple producer and multiple consumer problem. A fixed set
    of buffer list is allocated during initialization, where each
    list consist of a list of buffers. Each buffer is an iovec
    pointing to a memory region of fixed allocation size. Multiple
    producers write data to these buffers. A buffer list starts with
    a single buffer (iovec) and allocates more when required (although
    this can be preallocatd in multiples of k).
    
    rot-buffs allow multiple producers to write data parallely with
    a bit of extra cost of taking locks. Therefore, it's much suited
    for large writes. Multiple producers are allowed to write in the
    buffer parallely by "reserving" write space for selected number
    of bytes and returning pointer to the start of the reserved area.
    The write size is selected by the producer before it starts the
    write (which is often known). Therefore, the write itself need not
    be serialized -- just the space reservation needs to be done safely.
    
    The other part is when a consumer kicks in to consume what has
    been produced. At this point, a buffer list switch is performed.
    The "current" buffer list pointer is safely pointed to the next
    available buffer list. New writes are now directed to the just
    switched buffer list (the old buffer list is now considered out
    of rotation). Note that the old buffer still may have producers
    in progress (pending writes), so the consumer has to wait till
    the writers are drained. Currently this is the slow path for
    producers (write completion) and needs to be improved.
    
    Currently, there is special handling for cases where the number
    of consumers match (or exceed) the number of producers, which
    could result in writer starvation. In this scenario, when a
    consumers requests a buffer list for consumption, a check is
    performed for writer starvation and consumption is denied
    until at least another buffer list is ready of the producer
    for writes, i.e., one (or more) consumer(s) completed, thereby
    putting the buffer list back in rotation.
    
    [
       NOTE:
       I've not performance tested this producer-consumer model
       yet. It's being used in changelog for event notification.
       The list of buffers (iovecs) are directly passed to RPC
       layer.
    ]
    
    Change-Id: I88d235522b05ab82509aba861374a2312bff57f2
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9706
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit d236b01a8bf68b83c76ea1cfa8351833e19695f7
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Tue Mar 10 15:04:59 2015 +0530

    cli/glusterd: cli command implementation for bitrot features
    
    CLI command for bitrot features.
    
    volume bitrot <volname> enable|disable
    
    Above command will enable/disable bitrot feature for particular volume.
    
    BUG: 1170075
    Change-Id: Ie84002ef7f479a285688fdae99c7afa3e91b8b99
    Signed-off-by: Gaurav Kumar Garg     <ggarg@redhat.com>
    Signed-off-by: Anand nekkunti        <anekkunt@redhat.com>
    Signed-off-by: Dominic P Geevarghese <dgeevarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9866
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7c4461329bba38b72536ee71a8172bc861ddf890
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Feb 9 18:03:20 2015 +0530

    snapshot/scheduling: A cron based scheduler for snapshot scheduling
    
    GlusterFS volume snapshot provides point-in-time copy
    of a GlusterFS volume. Currently, GlusterFS volume
    snapshots can be easily scheduled by setting up
    cron jobs on one of the nodes in the GlusterFS
    trusted storage pool. This has a single point failure (SPOF),
    as scheduled jobs can be missed if the node running the cron
    jobs dies.
    
    The solution to the above problems is addressed in this patch.
    The snap_scheduler.py helper script expects the user to install
    the argparse python module before using it.
    
    Further details for the same are available at:
    
    http://www.gluster.org/community/documentation/index.php/Features/Scheduling_of_Snapshot
    
    Change-Id: I2c357af5b7d3e66f270d20eef50cdeecdcbe15c7
    BUG: 1198027
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9788
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3e18f093974c85ac92a4c48f0cd13aa9ff9c5cac
Author: vmallika <vmallika@redhat.com>
Date:   Wed Mar 18 23:17:23 2015 +0530

    features/quota : Introducing inode quota
    
    ==========================================================================
                                 Inode quota
    ==========================================================================
    = Currently, the only way to retrieve the number of files/objects in a   =
    = directory or volume is to do a crawl of the entire directory/volume.   =
    = This is expensive and is not scalable.                                 =
    =                                                                        =
    = The proposed mechanism will provide an easier alternative to determine =
    = the count of files/objects in a directory or volume.                   =
    =                                                                        =
    = The new mechanism proposes to store count of objects/files as part of  =
    = an extended attribute of a directory. Each directory's extended        =
    = attribute value will indicate the number of files/objects present      =
    = in a tree with the directory being considered as the root of the tree. =
    =                                                                        =
    = The count value can be accessed by performing a getxattr().            =
    = Cluster translators like afr, dht and stripe will perform aggregation  =
    = of count values from various bricks when getxattr() happens on the key =
    = associated with file/object count.                                     =
    
    A new interface is introduced:
    ------------------------------
            limit-objects  : limit the number of inodes at directory level
            list-objects   : list the directories where the limit is set
            remove-objects : remove the limit from the directory
    
    ==========================================================================
    
    CLI COMMAND:
    gluster volume quota <volname> limit-objects <path> <number> [<percent>]
    
    * <number> is a hard-limit for number of objects limitation for path "<path>"
      If hard-limit is exceeded, creation of file/directory is no longer
    permitted.
    
    * <percent> is a soft-limit for number of objects creation for path "<path>"
      If soft-limit is exceeded, a warning is issued for each creation.
    
    CLI COMMAND:
    gluster volume quota <volname> remove-objects [path]
    
    ==========================================================================
    
    CLI COMMAND:
    gluster volume quota <volname> list-objects [path] ...
    
    Sample output:
    ------------------
      Path                   Hard-limit Soft-limit   Used  Available
    Soft-limit exceeded?
    Hard-limit exceeded?
      ------------------------------------------------------------------------
    --------------------------------------
      /dir                      10       80%          10       0
    Yes
            Yes
    
    ==========================================================================
    
    [root@snapshot-28 dir]# ls
    a  b  file11  file12  file13  file14  file15  file16  file17
    [root@snapshot-28 dir]# touch a1
    touch: cannot touch `a1': Disk quota exceeded
    * Nine files are created in directory "dir" and directory is included in
    * the
    count too. Hence the limit "10" is reached and further file creation
    fails
    
    ==========================================================================
    
    Note: We have also done some re-factoring in cli for volume name
    validation. New function cli_validate_volname is created
    
    ==========================================================================
    
    Change-Id: I1823497de4f790a2a20ebb1770293472ea33ee2b
    BUG: 1190108
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9769
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fa50fcb6dddf4d7d0094c26cee802fd942f62727
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Mar 4 18:05:30 2015 +0530

    geo-rep / gsyncd: use RTLD_GLOBAL while loading libgfchangelog
    
    With the RPC based changes to {libgf}changelog, loading shared
    objects dynamically would need symbols to be available from
    other shared libraries. As an example, creating an RPC listner
    loads the RPC transport shared object which requires symbols
    to be available from already loaded shared objects.
    
    Using RTLD_GLOBAL makes the symbols available for symbol
    resolution of subsequently loaded libraries.
    
    Change-Id: I3d3ef790eded82911f05836c707509157680645c
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9814
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4737584fffcd25dbe35d17b076c95bf90a422cf2
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Feb 3 19:22:16 2015 +0530

    features/changelog: RPC'fy {libgf}changelog
    
    This patch introduces RPC based communication between the changelog
    translator and libgfchangelog. It replaces the old pathetic stream
    based interaction that existed earlier (due to time constraints :-/).
    
    Changelog, upon initialization starts a RPC server (rpcsvc) allowing
    clients to invoke a probe API as a bootup mechanism to request for
    event notifications. During probe, clients can choose an event
    filter specifying the type(s) of events they are interested in. As
    of now there is no way to change the event notification set once
    the probe RPC call is made, but that is easier to implement.
    
    The actual event notifications is done on a separate RPC session.
    The client (libgfchangelog) itself starts and RPC server which the
    changelog translator "connects back" during probe. Notifications
    are dispatched by a bunch of threads from the server (translator)
    and the client optionally orders them if ordered notifications
    are requried. FOPs fill in their respective event details in a
    buffer (rot-buffs to be particular) and a bunch of threads
    (consumers) swap the buffers out of roatation and dispatch them
    via RPC. To avoid writer starvation, then number of dispatcher
    threads is one less than the number of buffer list in rot-buffs.x
    
    libgfchangelog becomes purely callback based -- upon event
    notification from the server (and re-ordering them if required)
    invoke a callback routine specified by consumer(s).
    
    A major part of the patch is also aimed at providing backward
    compatibility for geo-replication, which was one of the main
    consumer of the stream based API. Also, this patch does not\
    "turn on" event notifications for all fops, just a bunch which
    is currently in requirement. Another pain point is that the
    server does not filter events before dispatching it to the
    clients. That load is taken up by the client itself (although
    it's done at the library layer rather than making it hard on
    the callback implementor). This needs improvement and care
    needs to be taken to not load the server up with expensive
    filtering mechanisms.
    
    Change-Id: Ibf60a432b68f2dfa60c6f9add2bcfd37a9c41395
    BUG: 1170075
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9708
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 728fcd41eb39f66744d84b979dd8195fd47313ed
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Feb 24 19:42:49 2015 +0100

    gfapi: add glfs_h_acl_set() and glfs_h_acl_get()
    
    These two functions add support for POSIX ACLs through the GFAPI-handle
    interface.
    
    The initial infrastructure for POSIX ACLs based on libacl has been added
    with the required changes to the POSIX xlator:
    - http://review.gluster.org/9627
    
    NetBSD does not support POSIX ACLs, so using any of the functions should
    return ENOTSUP.
    
    URL: http://www.gluster.org/community/documentation/index.php/Features/Improved_POSIX_ACLs
    Change-Id: Ie74f3f963c3f9d576cb2f2a1e6d97e3cd4b01eda
    BUG: 1185654
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9736
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 87c7fa3cfdadca4ee883daf84373302a42ad5fdc
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed Feb 18 19:45:23 2015 +0530

    Adding Libgfdb to GlusterFS
    
    *************************************************************************
    			Libgfdb						|
    *************************************************************************
    Libgfdb provides abstract mechanism to record extra/rich metadata
    required for data maintenance, such as data tiering/classification.
    It provides consumer with API for recording and querying, keeping
    the consumer abstracted from the data store used beneath for storing data.
    It works in a plug-and-play model, where data stores can be plugged-in.
    Presently we have plugin for Sqlite3. In the future will provide recording
    and querying performance optimizer. In the current implementation the schema
    of metadata is fixed.
    
    Schema:
    ~~~~~~
          GF_FILE_TB Table:
          ~~~~~~~~~~~~~~~~~
          This table has one entry per file inode. It holds the metadata required to
          make decisions in data maintenance.
          GF_ID (Primary key)	: File GFID (Universal Unique IDentifier in the namespace)
          W_SEC, W_MSEC 		: Write wind time in sec & micro-sec
          UW_SEC, UW_MSEC		: Write un-wind time in sec & micro-sec
          W_READ_SEC, W_READ_MSEC 	: Read wind time in sec & micro-sec
          UW_READ_SEC, UW_READ_MSEC : Read un-wind time in sec & micro-sec
          WRITE_FREQ_CNTR INTEGER	: Write Frequency Counter
          READ_FREQ_CNTR INTEGER	: Read Frequency Counter
    
          GF_FLINK_TABLE:
          ~~~~~~~~~~~~~~
          This table has all the hardlinks to a file inode.
          GF_ID		: File GFID               (Composite Primary Key)``|
          GF_PID		: Parent Directory GFID  (Composite Primary Key)   |-> Primary Key
          FNAME 		: File Base Name          (Composite Primary Key)__|
          FPATH 		: File Full Path (Its redundant for now, this will go)
          W_DEL_FLAG 	: This Flag is used for crash consistancy, when a link is unlinked.
                      	  i.e Set to 1 during unlink wind and during unwind this record
                              is deleted
          LINK_UPDATE 	: This Flag is used when a link is changed i.e rename.
                              Set to 1 when rename wind and set to 0 in rename unwind
    
    Libgfdb API:
    ~~~~~~~~~~~
    Refer libglusterfs/src/gfdb/gfdb_data_store.h
    
    Change-Id: I2e9fbab3878ce630a7f41221ef61017dc43db11f
    BUG: 1194753
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/9683
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dbd62a8d2b50392fbed0a0781a4f241dadb8f506
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Mar 18 15:25:08 2015 +0530

    marker: fix compile time warning on buf arg.
    
    Problem:
    marker-quota.c: In function 'mq_inspect_directory_xattr_task':
    marker-quota.c:3451:31: warning: variable 'buf' set but not
    used [-Wunused-but-set-variable]
             struct iatt           buf                          = {0,};
    
    Change-Id: I211378328bdb2509a5d2a186d173f7f30a670c8a
    BUG: 1198849
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9928
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ee7bde14cd8afa7752dbaecd72a4afe16fb7afa9
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jan 22 17:40:44 2015 +0530

    Quota: Build ancestry in the lookup
    
    Marker can fail or can account incorrect numbers when it doesn't find a
    ancestry for a inode.
    
    Solution:
    Current build_ancestry is done only on demand in the write/create FOPs
    in quota enforcer.
    It is good to do this in the quota_lookup as well.
    
    Change-Id: I8aaf5b3e05a3ca51e7ab1eaa1b636a90f659a872
    BUG: 1184885
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9478
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a216745e5db3fdb4fa8d625c971e70f8d0e34d23
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Wed Feb 18 14:49:50 2015 -0500

    cluster/dht: Change the subvolume encoding in d_off to be a "global"
    position in the graph rather than relative (local) to a particular
    translator.
    
    Encoding the volume in this way allows a single translator to manage
    which brick is currently being scanned for directory entries. Using a
    single translator minimizes allocated bits in the d_off. It also allows
    multiple DHT translators in the same graph to have a common frame of
    reference (the graph position) for which brick is being read. Multiple
    DHT translators are needed for the Tiering feature.
    
    The fix builds off a previous change (9332) which removed subvolume
    encoding from AFR. The fix makes an equivalent change to the EC
    translator.
    
    More background can be found in fix 9332 and gluster-dev discussions [1].
    
    DHT and AFR/EC are responsibile (as before) for choosing which brick to
    enumerate directory entries in over the readdir lifecycle.
    
    The client translator receiving the readdir fop encodes the dht_t. It
    is referred to as the "leaf node" in the graph and corresponds to the
    brick being scanned.
    
    When DHT decodes the d_off, it translates the leaf node to a local
    subvolume, which represents the next node in the graph leading to
    the brick.
    
    Tracking of leaf nodes is done in common utility functions. Leaf nodes
    counts and positional information are updated on a graph switch.
    
    [1] www.gluster.org/pipermail/gluster-devel/2015-January/043592.html
    
    Change-Id: Iaf0ea86d7046b1ceadbad69d88707b243077ebc8
    BUG: 1190734
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/9688
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 38ccaaf9d1a93c4fc6d733ee3bd5c73e5457bdab
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Mon Feb 2 16:23:22 2015 +0530

    CLI : GLobal option for NFS-Ganesha
    
    A new global CLI option has been introduced for NFS-Ganesha.
    gluster features.ganesha enable/disable.
    This option is persistent and shall be inherited
    by new volumes created after this option is set.
    
    gluster features.ganesha enable
    
    It carries out the following functions:
    1. Disables gluster-nfs across the cluster
    2. Starts NFS-Ganesha server on a subset of nodes and exports  '/'.
    3. Creates the HA cluster for NFS-Ganesha.
    4. Writes the option into the global config file.
    
    gluster features.ganesha disable
    
    1. Stops NFS-Ganesha server.
    2. Tears down the HA cluster for NFS-Ganesha
    
    With this change the older volume set
    options with keys "nfs-ganesha.host"
    and "nfs-ganesha.enable" will no longer
    be supported. This commit has only has the
    CLI related changes. Another patch will
    be submitted to support this feature entirely.
    
    Change-Id: Ie4b66a16c23b33b795738654b9a68f8e2c34efe3
    BUG: 1188184
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/9538
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 8a9c909702f4f6836bd1d0c791a7b1ae79d4ba15
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Mar 13 19:39:13 2015 +0530

    dht: suggest to add more bricks when min-free-disk is exceeded.
    
    Change-Id: I628fbd99c2478fcb8bb6e5be55e43467f25227bf
    BUG: 1165870
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9879
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit bf16d438237166c9379b8388a1be71b2dec4dd4d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Mar 16 11:36:38 2015 +0100

    Tests: do not hardcode NFS state directory
    
    tests/basic/mount-nfs-auth.t hardcoded /var/lib/glusterd/nfs/
    as the NFS state directory, cuasing failures if glusterfs was
    configured with state in another location.
    
    Fix this by obtaning the directory through a gluster volume get
    command. The nfs.mount-rmtab key gives us a file inside the
    directory we are looking for.
    
    This fixes tests/basic/mount-nfs-auth.t regression on NetBSD.
    
    BUG: 1129939
    Change-Id: I19184859c03faf5b9aeb95d080cf90fa581be380
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9896
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c73825b4bdb459219f06ec34706c0f2551cb9b0c
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Mar 12 23:51:41 2015 +0530

    doc: correct component name in manage volumes.
    
    Change-Id: I12cb0cdacace755d6c545c8697a4e18d6035954b
    BUG: 1075417
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9869
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit dde946f72a758410a80e05bf5f8447426db0b4a4
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Mar 17 20:40:58 2015 +0100

    Tests: ls portability regarding dot-files
    
    When run as root, BSD ls(1) lists dot-files, which includes
    .glusterfs in split-brain-healing.t's usage. This leads to failure.
    gfid-self-heal.t suffers the same problem.
    
    Fix by filtering out dot-files in ls(1) output
    
    NB: split-brain-healing.t also requires http://review.gluster.org/9831
    to pass on NetBSD.
    
    BUG: 1129939
    Change-Id: Ic572d3abf685e9b43f32ddee8a13b5f5c4ae641f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9885
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 89cb6bcc7335a9b5e12febcacc27f762bdcda595
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    glusterd: add new NFS options for exports/netgroups and related caching
    
    The following options for the Gluster/NFS server are added :
    - nfs.exports-auth-enable
    - nfs.auth-refresh-interval-sec
    - nfs.auth-cache-ttl-sec
    
    BUG: 1143880
    Change-Id: I37a73966c4ed27cd0f8c77200ef68a0d12b385b8
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9364
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1bf69fc65d777e1bbea28619c144a9cb373b47ab
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Mar 5 00:54:36 2015 +0530

    doc: document glusterfind feature
    
    Change-Id: I759f05d63028d6a52c3e1ee2ab9892583c4832e7
    BUG: 1193893
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9800
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1250003956bc9fe7f030f0541f1c823cb282a07a
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 17 12:06:25 2015 +0530

    glusterd: Remove compilation warning
    
    In glusterd_peerinfo_destroy, cast the passed 'strcut rcu_head *'
    pointer to 'gd_rcu_head *' before use in caa_container_of() to prevent
    the incompatible-pointer compilation warning.
    
    Also, refactor peerinfo->head to peerinfo->rcu_head to reduce confusion
    when reading code.
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      aa4a0bc Rename peerinfo->head to peerinfo->rcu_head
      c79144b Cast struct rcu_head * to gd_rcu_head * to prevent warning
      1d222c3 More head -> rcu_head renames
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    BUG: 1191030
    Change-Id: I7ede02090413839563ce44fdf6289697b28777e7
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/9922
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b5a01eb9b65a11866c2b4ce0068d60dc667ed2be
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Mar 18 12:58:59 2015 +0530

    geo-rep: Remove Generated file From git
    
    geo-replication/src/peer_mountbroker
    
    BUG: 1136312
    Change-Id: Ib9b287b4e1183cb44acbf01184a240be7f09be7c
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9923
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 7e98a0e0b1e346f89047b57e495f66f1b4223997
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Feb 18 19:07:23 2015 +0530

    feature/glusterfind: A tool to find incremental changes
    
    Documentation is available in patch:
    http://review.gluster.org/#/c/9800/
    
    A tool which helps to get list of modified files or list of all files in
    GlusterFS Volume using Changelog or find command.
    
    Usage
    =====
    glusterfind --help
    
    Create:
    -------
    glusterfind create --help
    
    The tool creates status file $GLUSTERD_WORKDIR/SESSION/VOLUME/status
    and records current timestamp to initiate the session. This timestamp
    will be used as start time for next runs.
    
    As part of create also generates ssh key and distributes to all peers.
    and enables build.pgfid and changelog using volume set command.
    
    Pre:
    ----
    glusterfind pre --help
    
    This command is used to generate the list of files modified after session
    creation time or after last run. To get list of all files/dirs in Volume,
    run pre command with `--full` argument.
    
    The tool gets all nodes details using gluster volume info and runs node
    agent for each brick in respective nodes via ssh command. Once these node
    agents generate the output file, tool copies to local using scp. Merges all
    the output files to generate the final output file.
    
    Post:
    -----
    glusterfind post --help
    
    After consuming the list, this sub command is called to update the session
    time based on pre command status file.
    
    List:
    -----
    glusterfind list --help
    
    To view all the sessions
    
    Delete:
    -------
    glusterfind delete --help
    
    Delete session.
    
    Known Issues
    ------------
    1. Deleted files will not get listed, since we can't convert GFID to
       Path if file/dir is deleted.
    2. Only new name will get listed if Renamed.
    3. All hardlinks will get listed.
    
    Change-Id: I82991feb0aea85cb6ec035fddbf80a2b276e86b0
    BUG: 1193893
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9682
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c9b1aea9b3f7087336c75548b59574f251813136
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 17 13:16:45 2015 +0530

    cluster/afr: Make read child match check in afr optional
    
    Having this particular check which was introduced by
    commit c78998c39f0857ea7aacba360632c148afc54a55 causes a drop in
    performance in readdirp. So the behavior is made configurable with this
    patch.
    
    Change-Id: I2858fc18b3539df7aa6d3f489e0d5cfaeb8a9b3c
    BUG: 1202669
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9917
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 368dfd695928e8fc40988b8f2de86c3b469172d2
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Wed Mar 18 11:33:50 2015 +0530

    NFS-Ganesha: Volume set option for managing NFS-Ganesha exports.
    
    A dummy translator has been introduced as a place
    holder for functions related to managing NFS-Ganesha
    exports. A volume set option is introduced to
    manage volume level exports.
    
    gluster vol set <volname> ganesha.enable ON/OFF
    
    1. gluster volume set <volname> ganesha.enable ON
    
    It creates the export config file with a unique export ID.
    Sends a DBus signal to export this volume dynamically.
    
    2. gluster vol set <volname> ganesha.enable OFF
    
    Unexports the specific volume. Deletes the specfic
    config file related to the volume.
    
    This change also removes the handling of the older
    keys "nfs-ganesha.enable" and "nfs-ganesha.host"
    
    Change-Id: I8d4a0b542326a6a0c8e4711600b106274d666587
    BUG: 1188184
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/9585
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 260a6943849f99227248a8fc852a8c8fc3d1e289
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Feb 23 17:28:47 2015 +0530

    Snapshot/clone: clone of a snapshot that will act as a regular volume
    
    snapshot clone will allow us to take a snpahot of a snapshot.
    Newly created clone volume will be a regular volume with read/write
    permissions.
    
    CLI command
    snapshot clone <clonename> <snapname>
    
    Change-Id: Icadb993fa42fff787a330f8f49452da54e9db7de
    BUG: 1199894
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9750
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c99c72b35fac16e08c4d170b6a46a786caaeef58
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Mar 16 15:47:30 2015 +0530

    libgfapi, timer: Fix a crash seen in timer when glfs_fini was invoked.
    
    The crash is seen when, glfs_init failed for some reason
    and glfs_fini was called for cleaning up the partial initialization.
    
    The fix is in two folds:
    
    1. In timer store and restore the THIS, previously
       it was being overwritten.
    2. In glfs_free_from_ctx() and glfs_fini() check for
       NULL before destroying.
    
    Change-Id: If40bf69936b873a1da8e348c9d92c66f2f07994b
    BUG: 1202290
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9895
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 33944a3eb3b589b1d309826b5f431497924ac3ae
Author: Anoop C S <achiraya@redhat.com>
Date:   Tue Mar 17 16:29:53 2015 +0530

    features/trash: Avoid unnecessary logging from trash_local_wipe
    
    Even when trash translator is disabled, the following error
    is being logged for each unlink/truncate/ftruncate calls.
    
    [...] E [trash.c:221:trash_local_wipe] (--> ...
            ... ) 0-trash: invalid argument: local
    
    This change replaces GF_VALIDATE_OR_GOTO macro with simple
    if condition.
    
    Change-Id: I7e6754cd53ec7c2d84669b6d40d883a2d1eee41e
    BUG: 1132465
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/9909
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 7970183f4c730d4aca3cfaa106fde015a0fbc415
Author: vmallika <vmallika@redhat.com>
Date:   Tue Mar 17 20:05:19 2015 +0530

    Quota/marker : Support for inode quota
    
    Currently, the only way to retrieve the number of files/objects in a
    directory or volume is to do a crawl of the entire directory/volume.
    This is expensive and is not scalable.
    
    The new mechanism proposes to store count of objects/files as part of
    an extended attribute of a directory. Each directory's extended
    attribute value will indicate the number of files/objects present
    in a tree with the directory being considered as the root of the tree.
    
    Currently file usage is accounted in marker by doing multiple FOPs
    like setting and getting xattrs. Doing this with STACK WIND and
    UNWIND can be harder to debug as involves multiple callbacks.
    In this code we are replacing current mechanism with syncop approach
    as syncop code is much simpler to follow and help us implement inode
    quota in an organized way.
    
    Change-Id: Ibf366fbe07037284e89a241ddaff7750fc8771b4
    BUG: 1188636
    Signed-off-by: vmallika <vmallika@redhat.com>
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9567
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 33bb32ce5866a15e7d5164c67f214c4797236066
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Mar 17 12:02:32 2015 +0530

    tests: Fix spurious failure in bug-866459.t
    
    10.TEST kill_brick $V0 $H0 $B0/${V0}1
    11.-EXPECT '1' echo `pgrep glusterfsd | wc -l
    
    Problem:
    On my Fedora 21 laptop, #11 always fails:"not ok 11 Got "2" instead of "1"
    On debugging, I found that after killing, the kernel takes some time to
    clean up the process until which it appears as defunct in the pgrep
    output:
    root  21795  2.0  0.0      0     0 ?        Zsl  11:57   0:00 [glusterfsd] <defunct>
    
    Fix:
    As long as TEST kill_brick is successful, we really don't need to double
    check with the pgrep output. Hence removing that line.
    
    Change-Id: Ia10e0a04803e54a074f73da6523fa6a98c677d58
    BUG: 1163543
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9904
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2a4561ef08b8be3b7d79b951252e87ba8f987120
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Mon Feb 16 11:47:58 2015 +0530

    gfapi: APIs to store and process upcall notifications received
    
    In case of any upcall cbk events received by the protocol/client,
    gfapi will be notified which queues them up in a list (<gfapi_cbk_upcall>).
    
    Applicatons are responsible to provide APIs to process & notify them in case
    of any such upcall events queued.
    
    Added a new API which will be used by Ganesha to repeatedly poll for any
    such upcall event notified (<glfs_h_poll_upcall>).
    
    A new test-file has been added to test the cache_invalidation upcall events.
    
    Below link has a writeup which explains the code changes done -
            URL: https://soumyakoduri.wordpress.com/2015/02/25/glusterfs-understanding-upcall-infrastructure-and-cache-invalidation-support/
    
    Change-Id: Iafc6880000c865fd4da22d0cfc388ec135b5a1c5
    BUG: 1200262
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/9536
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit d81182cf69a4f188f304fcce6d651ffd56b67aac
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Mar 17 09:27:05 2015 -0400

    NFS-Ganesha: Install scripts, config files, and resource agent scripts
    
    Resubmitting after a gerrit bug bungled the merge of
    http://review.gluster.org/9621 (was it really a gerrit bug?)
    
    Scripts related to NFS-Ganesha are in extras/ganesha/scripts.
    Config files are in extras/ganesha/config.
    Resource Agent files are in extras/ganesha/ocf
    
    Files are copied to appropriate locations.
    
    Change-Id: I137169f4d653ee2b7d6df14d41e2babd0ae8d10c
    BUG: 1188184
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/9912
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c8be9af5f54aa3e42dffee4024d2915743258242
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 5 11:29:25 2015 +0000

    afr: remove stale index entries
    
    Problem:
    During pre-op phase, the index xlator
    1. Creates the entry inside .glusterfs/indices/xattrop
    2. Winds the xattrop fop to posix to mark dirty/pending changelogs.
    If the brick crashes after 1, the xattrop entry becomes stale and never
    gets removed by shd during subsequent crawls because there is nothing to
    heal (changelogs are zero).
    
    Though the stale entry does not get displayed in the output of 'heal
    info' command, it nevertheless stays there forever unless a new write
    transaction is performed on the file.
    
    Fix:
    During index self-heal if afr xattrs are found to be clean (indicated by
    ret value of 2 on a call to afr_shd_selfheal(), send a dummy
    post-op with all 0s for the xattr values, which makes the index xlator
    to unlink the stale entry.
    
    Change-Id: I02cb2bc937f2e3f3f3cb35d67b006664dc7ef919
    BUG: 1190069
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9714
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0d2bed70faed3c63f25ed9269dc55562973ef9b7
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Mar 10 20:14:47 2015 -0400

    every/where: add GF_FOP_IPC for inter-translator communication
    
    Several features - e.g. encryption, erasure codes, or NSR - involve
    multiple cooperating translators which sometimes need a "private" means
    of communication amongst themselves.  Historically we've used virtual or
    synthetic xattrs, but that's not very elegant and clutters up the
    getxattr/setxattr path which must also handle real xattr requests.  This
    new fop should address that.
    
    The only argument is an int32_t "op" which should be recognized by the
    target translator.  It is recommended that translators using these
    feature follow some convention regarding the ops that they define, to
    avoid conflicts.  Using a hash of the target translator's type string as
    a base for a series of ops would probably be a good start.  Any other
    information can be passed in both directions using xdata.
    
    The default behavior for this fop, as with any other, is to pass through
    to FIRST_CHILD.  That makes use of this fop "transparent" to other
    translators that were written before it existed, but it also means that
    it only really works with pass-through translators.  If a routing
    translator (such as DHT) or a fan-out translator (such as AFR) is
    involved, the IPC might not reach its intended destination unless those
    translators are modified to forward IPC fops along all paths.
    
    If an IPC gets all the way to storage/posix it is considered an error,
    much like an uncaught exception.  We don't actually *do* anything in
    that case, but we do log it send back an EOPNOTSUPP error.  This makes
    the "unrecognized opcode" condition distinguishable from the "no IPC
    support" condition (which would yield an RPC error instead) so clients
    can probe for the presence of a handler for their own favorite opcode
    and either use that or use old-school xattrs depending on the result.
    
    BUG: 1158628
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Change-Id: I84af1b17babe5b30ec03ecf027ae37d09b873968
    Reviewed-on: http://review.gluster.org/8812
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6b3704990257643da54100d8581856a7d2c72f86
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Feb 17 12:12:11 2015 +0100

    socket: use TCP_USER_TIMEOUT to detect client failures quicker
    
    Use the network.ping-timeout to set the TCP_USER_TIMEOUT socket option
    (see 'man 7 tcp'). The option sets the transport.tcp-user-timeout option
    that is handled in the rpc/socket layer on the protocol/server side.
    This socket option makes detecting unclean disconnected clients more
    reliable.
    
    When the socket gets closed, any locks that the client held are been
    released. This makes it possible to reduce the fail-over time for
    applications that run on systems that became unreachable due to
    a network partition or general system error client-side (kernel panic,
    hang, ...).
    
    It is not trivial to create a test-case for this at the moment. We need
    a client that unclean disconnects and an other client that tries to take
    over the lock from the disconnected client.
    
    URL: http://supercolony.gluster.org/pipermail/gluster-devel/2014-May/040755.html
    Change-Id: I5e5f540a49abfb5f398291f1818583a63a5f4bb4
    BUG: 1129787
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8065
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Santosh Pradhan <santosh.pradhan@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2b97b57cd8c71cb07b7002cf3483e9cfc9403c58
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Sun Feb 15 23:35:56 2015 +0530

    Upcall: New xlator to store various states and send cbk events
    
    Framework on the server-side, to handle certain state of the files
    accessed and send notifications to the clients connected.
    
    A generic and extensible framework, used to maintain states in
    the glusterfsd process for each of the files accessed
    (including the clients info doing the fops) and send
    notifications to the respective glusterfs clients incase of
    any change in that state.
    
    This patch handles "Inode Update/Invalidation" upcall event.
    
    Feature page:
            URL: http://www.gluster.org/community/documentation/index.php/Features/Upcall-infrastructure
    
    Below link has a writeup which explains the code changes done -
            URL: https://soumyakoduri.wordpress.com/2015/02/25/glusterfs-understanding-upcall-infrastructure-and-cache-invalidation-support/
    
    Change-Id: Ie3d724be9a3419fcf18901a753e8ec2df2ac802f
    BUG: 1200262
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/9535
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 79009691c01f2b32b523d91a159aadd0e414f31b
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Jan 6 18:20:45 2015 +0530

    geo-rep: mountbroker user management
    
    Non root geo-replication setup is now simplified. This
    patch provides cli for mountbroker user and options management
    
    To set Options,
        gluster system:: execute mountbroker opt <KEY> <VALUE>
        # for example,
        gluster system:: execute mountbroker opt mountbroker-root /var/mountbroker-root
        gluster system:: execute mountbroker opt geo-replication-log-group geogroup
        gluster system:: execute mountbroker opt rpc-auth-allow-insecure on
    
    To remove option,
        gluster system:: execute mountbroker optdel <KEY>
        # for example,
        gluster system:: execute mountbroker optdel geo-replication-log-group
    
    To add/edit user,
        gluster system:: execute mountbroker user <USERNAME> <VOLUMES>
        # for example
        gluster system:: execute mountbroker user geoaccount slavevol1,slavevol2
    
    To remove user,
        gluster system:: execute mountbroker userdel <USERNAME>
        # for example
        gluster system:: execute mountbroker userdel geoaccount
    
    For info,
        gluster system:: execute mountbroker info
        gluster system:: execute mountbroker -j info
    
    For JSON output add -j after mountbroker, for example,
        gluster system:: execute mountbroker -j user geoaccount slavevol1,slavevol2
    
    PS: Each peer prints its own JSON output, aggregator required from consumer side
    
    BUG: 1136312
    Change-Id: Ie52210c0bcc91ac2ffd3ba58988222ffca62b47f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9398
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: darshan n <dnarayan@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fb6858b47585244fd3cef2f0e8155a13752e0365
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Mar 9 19:12:03 2015 +0530

    inode:  'this' has been set unwantedly.
    
    Problem:
      CC       libglusterfs_la-inode.lo
    inode.c: In function 'inode_table_destroy':
    inode.c:1630:19: warning: variable 'this' set
    but not used [-Wunused-but-set-variable]
             xlator_t *this = NULL;
    
    Change-Id: If4b37ab896ee0a309826d4be48c6599d6ec2710b
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9846
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anoop C S <achiraya@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>

commit 71210c021f7b6d7b79f31553d7bd8632d1f6e99f
Author: vmallika <vmallika@redhat.com>
Date:   Mon Mar 16 15:38:16 2015 +0530

    remove spurious failure test from bug-1087198.t
    
    Consider below scenario in the quota xlator
    
    T1 - write with delta1 bytes on fd1
         check_limit sees that delta1 bytes is not exceeding soft limit
    T2 - write with delta2 bytes on fd1
         check_limit sees that delta2 bytes is not exceeding soft limit
    T3 - delta1 and delta2 bytes are written to the disk.
    
    Here delta1 and delta2 are checked separately and do not exceed
    limit, but they together exceed the limit which is not checked.
    
    We need to find a solution to solve this problem. Till then for
    other regressions to pass, we remove the the test which checks for
    soft limit crossed.
    
    Change-Id: I8f76754e975c3315557a4c570db8bb5d9e56de15
    BUG: 1202292
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9894
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0778882d11265f258b3e0f3d9892527ac8ea7341
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Mar 15 23:07:01 2015 +0100

    tests: prevent regular hangs in ec/nfs.t
    
    When the test systems gets into a memory pressure state (the Jenkins VMs
    do not have much RAM), the localhost NFS-mount can get hung. It is
    possible to prevent this by writing with O_DIRECT. Unfortnately, the
    'dd' command on NetBSD does not seem to support such an option.
    
    The alternative is to reduce the I/O that can get cached on the
    NFS-client, like reducing the "count" option for "dd".
    
    Change-Id: I1da9cb41133bb934bcbae0a6bc091f798514ed3d
    BUG: 1163543
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9883
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 0ef870741a2f49d47a02725aed13a95335a6e42f
Author: Anoop C S <achiraya@redhat.com>
Date:   Fri Feb 27 15:14:08 2015 +0530

    Features/trash : Combined patches for trash translator
    
    This is the combined patch set for supporting trash feature.
    http://www.gluster.org/community/documentation/index.php/Features/Trash
    
    Current patch includes the following features:
    * volume set options for enabling trash globally and
      exclusively for internal operations like self-heal
      and re-balance
    * volume set options for setting the eliminate
      path, trash directory path and maximum trashable
      file size.
    * test script for checking the functionality of the
      feature
    * brief documentation on different aspects of trash
      feature.
    
    Change-Id: Ic7486982dcd6e295d1eba0f4d5ee6d33bf1b4cb3
    BUG: 1132465
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/8312
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 393cdb2613250031fce92cab8dede9154514f816
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Mar 13 19:08:38 2015 +0530

    gfapi: improve source comments and error messages.
    
    Change-Id: I0bfa44eb5b5f21e381af3e71c26ea863e4adc46f
    BUG:1202274
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9878
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 0ab4cb8174f478e8f725f13e96f608a6186e8384
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Mar 11 17:19:42 2015 +0530

    libgfapi: initialize child_down_count cond. variable.
    
    currently glfs_new_from_ctx() does not initialize child_down_count
    conditional variable, but, glfs_free_from_ctx()
    destroy this variable. mnt3udp_get_export_subdir_inode() from mount3
    calls glfs_free_from_ctx(), so bound to invite problems. This patch
    avoids the issue.
    
    Change-Id: I8c1ed83f0b39248edbb78db25c9434274b538e80
    BUG: 1200879
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9857
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit c7785f78420c94220954eef538ed4698713ebcdb
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jan 8 19:24:59 2015 +0530

    glusterd: Protect the peer list and peerinfos with RCU.
    
    The peer list and the peerinfo objects are now protected using RCU.
    Design patterns described in the Paul McKenney's RCU dissertation [1]
    (sections 5 and 6) have been used to convert existing non-RCU protected
    code to RCU protected code.
    
    Currently, we are only targetting guaranteeing the existence of the
    peerinfo objects, ie., we are only looking to protect deletes, not all
    updaters. We chose this, as protecting all updates is a much more
    complex task.
    
    The steps used to accomplish this are,
    
    1. Remove all long lived direct references to peerinfo objects (apart
    from the peerinfo list). This includes references in glusterd_peerctx_t
    (RPC), glusterd_friend_sm_event_t (friend state machine) and others.
    This way no one has a reference to deleted peerinfo object.
    
    2. Replace the direct references with indirect references, ie., use
    peer uuid and peer hostname as indirect references to the peerinfo
    object. Any reader or updater now uses the indirect references to get to
    the actual peerinfo object, using glusterd_peerinfo_find. Cases where a
    peerinfo cannot be found are handled gracefully.
    
    3. The readers get and use the peerinfo object only within a RCU read
    critical section. This prevents the object from being deleted/freed when
    in actual use.
    
    4. The deletion of a peerinfo object is done in a ordered manner
    (glusterd_peerinfo_destroy). The object is first removed from the
    peerinfo list using an atomic list remove, but the list head is not
    reset to allow existing list readers to complete correctly. We wait for
    readers to complete, before resetting the list head. This removes the
    object from the list completely. After this no new readers can get a
    reference to the object, and it can be freed.
    
    This change was developed on the git branch at [2]. This commit is a
    combination of the following commits on the development branch.
      d7999b9 Protect the glusterd_conf_t->peers_list with RCU.
      0da85c4 Synchronize before INITing peerinfo list head after removing
              from list.
      32ec28a Add missing rcu_read_unlock
      8fed0b8 Correctly exit read critical section once peer is found.
      63db857 Free peerctx only on rpc destruction
      56eff26 Cleanup style issues
      e5f38b0 Indirection for events and friend_sm
      3c84ac4 In __glusterd_probe_cbk goto unlock only if peer already
              exists
      141d855 Address review comments on 9695/1
      aaeefed Protection during peer updates
      6eda33d Revert "Synchronize before INITing peerinfo list head after
              removing from list."
      f69db96 Remove unneeded line
      b43d2ec Address review comments on 9695/4
      7781921 Address review comments on 9695/5
      eb6467b Add some missing semi-colons
      328a47f Remove synchronize_rcu from
              glusterd_friend_sm_transition_state
      186e429 Run part of glusterd_friend_remove in critical section
      55c0a2e Fix gluster (peer status/ pool list) with no peers
      93f8dcf Use call_rcu to free peerinfo
      c36178c Introduce composite struct, gd_rcu_head
    
    [1]: http://www.rdrop.com/~paulmck/RCU/RCUdissertation.2004.07.14e1.pdf
    [2]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: Ic1480e59c86d41d25a6a3d159aa3e11fbb3cbc7b
    BUG: 1191030
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/9695
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7d8be3613f7384f5118f26e194fe7c64ea69d11c
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Mar 11 13:31:09 2015 +0530

    geo-rep: Do not use xsync_upper_limit for change detection
    
    Use register time(xsync_upper_limit) only for stime update, do not
    use for change detection.
    
    Problem 1:
    If a file created before geo-rep, xtime xattr does not exist.
    Geo-rep updates xtime of the file to current time if not exists.
    xtime > upper_limit so geo-rep will not pick those files. Changelog
    either will have SETXATTR, and fails to sync the file.
    
    Problem 2:
    If a file is created before geo-rep create and updated after
    geo-rep start. xtime of the file is greater than upper limit(geo-rep
    start time/changelog register time). Geo-rep(XSync) will not pick this
    file for syncing. Changelog will have only DATA recorded for that file.
    Geo-rep tries DATA without any ENTRY ops and fails with rsync error.
    
    BUG: 1200733
    Change-Id: Ie4e8f284db689d2c755ef8e7ecbb658db1c0785f
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9855
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f0224ce93ae9ad420e23612fe6e6707a821f9cab
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Feb 23 14:46:48 2015 +0530

    feature/geo-rep: Active Passive Switching logic flock
    
    CURRENT DESIGN AND ITS LIMITATIONS:
    -----------------------------------
    Geo-replication syncs changes across geography using changelogs captured
    by changelog translator. Changelog translator sits on server side just
    above posix translator. Hence, in distributed replicated setup, both
    replica pairs collect changelogs w.r.t their bricks. Geo-replication
    syncs the changes using only one brick among the replica pair at a time,
    calling it as "ACTIVE" and other non syncing brick as "PASSIVE".
    
    Let's consider below example of distributed replicated setup where
    NODE-1 as b1 and its replicated brick b1r is in NODE-2
    
            NODE-1                         NODE-2
              b1                            b1r
    
    At the beginning, geo-replication chooses to sync changes from NODE-1:b1
    and NODE-2:b1r will be "PASSIVE". The logic depends on virtual getxattr
    'trusted.glusterfs.node-uuid' which always returns first up subvolume
    i.e., NODE-1. When NODE-1 goes down, the above xattr returns NODE-2 and
    that is made 'ACTIVE'. But when NODE-1 comes back again, the above xattr
    returns NODE-1 and it is made 'ACTIVE' again. So for a brief interval of
    time, if NODE-2 had not finished processing the changelog, both NODE-2
    and NODE-1 will be ACTIVE causing rename race as mentioned in the bug.
    
    SOLUTION:
    ---------
    1. Have a shared replicated storage, a glusterfs management volume specific
       to geo-replication.
    
    2. Geo-rep creates a file per replica set on management volume.
    
    3. fcntl lock on the above said file is used for synchronization
       between geo-rep workers belonging to same replica set.
    
    4. If management volume is not configured, geo-replication will back
       to previous logic of using first up sub volume.
    
    Each worker tries to lock the file on shared storage, who ever wins will
    be ACTIVE. With this, we are able to solve the problem but there is an
    issue when the shared replicated storage goes down (when all replicas
    goes down). In that case, the lock state is lost. So AFR needs to rebuild the
    lock state after brick comes up.
    
    NOTE:
    -----
    This patch brings in the, pre-requisite step of setting up management volume
    for geo-replication during creation.
    
    1. Create mgmt-vol for geo-replicatoin and start it. Management volume should
       be part of master cluster and recommended to be three way replicated
       volume having each brick in different nodes for availability.
    2. Create geo-rep session.
    3. Configure mgmt-vol created with geo-replication session as follows.
       gluster vol geo-rep <mastervol> slavenode::<slavevol> config meta_volume \
       <meta-vol-name>
    4. Start geo-rep session.
    
    Backward Compatiability:
    -----------------------
    If management volume is not configured, it falls back to previous logic of
    using node-uuid virtual xattr. But it is not recommended.
    
    Change-Id: I7319d2289516f534b69edd00c9d0db5a3725661a
    BUG: 1196632
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9759
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7a9a66cc5fb7f06118fab1fc2ae1c43cfbb1178f
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Jan 29 15:53:19 2015 +0530

    tools: Finds missing files in gluster volume given backend brickpath
    
    The tool finds the missing files in a geo-replication slave volume.
    The tool crawls backend .glusterfs of the brickpath, which is passed
    as a parameter and stats each entry on slave volume mount to check
    the presence of file. The mount used is aux-gfid-mount, hence no path
    conversion is required and is fast. The tool needs to be run on every
    node in cluster for each brickpath of geo-rep master volume to find
    missing files on slave volume. The tool is generic enough and can be
    used in non geo-replication context as well.
    
    Most of the crawler code is leverged from Avati's xfind and is modified
    to crawl only .glusterfs (https://github.com/avati/xsync)
    
    Thanks Aravinda for scripts to convert gfid to path.
    
    Change-Id: I84deaaaf638f7c571ff1319b67a3440fe27da810
    BUG: 1187140
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9503
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 38e342ca4a2167720bea82d3cee7fca08baba666
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Mar 4 18:38:07 2015 +0530

    xlator: avoiding possibility of a crash if (xl->ctx) is NULL.
    
    Change-Id: I41acd9970bef04bb16cd4d8532a84a95d5fb642a
    BUG: 1199003
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>.
    Reviewed-on: http://review.gluster.org/9810
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aaf7cd3c4059167b0f2ba821d14362a977f1d58c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Mar 15 14:16:56 2015 +0100

    nfs: improve cleanup of 'struct exports_file' to prevent memory leak
    
    BUG: 1143880
    Change-Id: I359470a1edb935e206eeeecd4de7022530fb397a
    Reported-by: Vijay Bellur <vbellur@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9882
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b3f63120e8f2b6f99d44ebe244aafafeb6ac890e
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Mar 13 11:37:14 2015 +0530

    rdma:changing list iteration to safe mode
    
    Change-Id: I2299378f02a5577a8bf2874664ba79e92c3811b5
    BUG: 1201621
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9872
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d8c18855caa07ff9d529395a760457281dd2f08e
Author: arao <arao@redhat.com>
Date:   Thu Feb 12 10:12:35 2015 +0530

    fuse: Fixing dereference after null check
    
    CID: 1124496
    
    The pointer is not checked against null and is dereferenced anyway,
    which is now checked.
    
    Change-Id: Ib810546445596671b3656f01a14bbad02cdc221c
    BUG: 789278
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9640
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 510b1f6292da249a641aea6bc06ede433cc66936
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Feb 3 13:17:19 2015 +0530

    xlators/storage/bd : Unused value is removed.
    
    CID:1128926
    
    Change-Id: I5ad1229e225a36f995245a847db1a19609a18cd8
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2c3b6ab03262108f95d706b9ebaa207b352fc32c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Mar 11 23:00:09 2015 -0400

    nfs: use free() for getline() allocated string in netgroups
    
    'line' is allocated through getline() which uses malloc(). GF_FREE()
    will fail to release the memory because it can not find the expected
    mem-pool header. Instead of GF_FREE(), free() should be used for strings
    that get allocated with getline().
    
    Subsequent calls to getline() with a non-NULL pointer will get the size
    of the allocation adjusted with realloc().
    
    Change-Id: I612fbf17d7283174d541da6f34d26e4f44e83bfa
    BUG: 1143880
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9860
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa66b8404f45712c45d75d6a2a37f32e2792cc83
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    gNFS: Export / Netgroup authentication on Gluster NFS mount
    
    * Parses linux style export file/netgroups file into a structure that
      can be lookedup.
    
    * This parser turns each line into a structure called an "export
      directory". Each of these has a dictionary of hosts and netgroups
      which can be looked up during the mount authentication process.
      (See Change-Id Ic060aac and I7e6aa6bc)
    
    * A string beginning withan '@' is treated as a netgroup and a string
      beginning without an @ is a host.
      (See Change-Id Ie04800d)
    
    * This parser does not currently support all the options in the man page
      ('man exports'), but we can easily add them.
    
    BUG: 1143880
    URL: http://www.gluster.org/community/documentation/index.php/Features/Exports_Netgroups_Authentication
    Change-Id: I181e8c1814d6ef3cae5b4d88353622734f0c0f0b
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8758
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aac1ec0a61d9267b6ae7a280b368dfd357b7dcdc
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    nfs: add auth-cache for the MOUNT protocol
    
    Authentication cache for the new fine grained contol for the MOUNT
    protocol. The extended authentication (see Change-Id Ic060aac) benefits
    from caching the access/permission checks that are done when an
    NFS-client mounts an export.
    
    This auth-cache will be used by Change-Id I181e8c1.
    
    BUG: 1143880
    Change-Id: I1379116572c8a4d1bf0c7ca4f826e51a79d91444
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9363
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1cb3b1abeda53bb430bbe1490fac154337ac9994
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    nfs: more fine grained authentication for the MOUNT protocol
    
    The /etc/exports format for NFS-exports (see Change-Id I7e6aa6b) allows
    a more fine grained control over the authentication. This change adds
    the functions and structures that will be used in by Change-Id I181e8c1.
    
    BUG: 1143880
    Change-Id: Ic060aac7c52d91e08519b222ba46383c94665ce7
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9362
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0c3d3a796bda37d8439855baf00137ad17714620
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    nfs: add support for separate 'exports' file
    
    The Linux kernel NFS server uses /etc/exports to manage permissions for
    the NFS-clients. Extending the Gluster/NFS server to support a similar
    scheme is needed for many deployments in enterprise environments.
    
    BUG: 1143880
    Change-Id: I7e6aa6bc6aa1cd5f52458e023387ed38de9823d7
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9361
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9f71b25f34a24741496875ab947f6f9c95ec277f
Author: vmallika <vmallika@redhat.com>
Date:   Wed Mar 11 18:03:47 2015 +0530

    syncop: assign lk_owner for the newly created frame
    
    syncop_inodelk doesn't work properly as lk_owner is not set
    in the frame created by 'synctask_create'.
    There is a possibility that more than one thread can acquire inode lock
    with syncop_inodelk
    
    Change-Id: I8193edb0d24b3a6e3a3f6a0c5d7ab5a1be8e7daf
    BUG: 1188636
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9858
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7c177bda6ccd1c3e7a7c070eb2ab0dc5e6b32a5c
Author: darshan n <dnarayan@redhat.com>
Date:   Wed Mar 4 19:18:10 2015 +0530

    geo-rep-cli: added a new option "no-verify" to geo-rep create.
    
    This patch adds a new option called as "no-verify" to geo-rep
    create command. With no-verify option, following checks does
    not take place before session creation:
    
    * if ssh port 22 is open in slave
    * has proper passwordless ssh login setup
    * slave volume is created and is empty
    * if slave has enough memory
    
    This option is needed by ovirt-engine as the tasks done
    by push-pem is taken care by ovirt-engine and also the
    above checks are done. Thus creation of password-less
    ssh can be avoided when geo-replication is managed
    through ovirt.
    
    Usage: volume geo-replication [<VOLNAME>] [<SLAVE-URL>]
           { create [[no-verify]|[push-pem]] [force]|
             start [force]|stop [force]|pause [force]|
             resume [force]|config|status [detail]|
             delete } [options...]
    
    Change-Id: I975265f27d6434be5409438257d09cd4190c9159
    BUG: 1198615
    Signed-off-by: darshan n <dnarayan@redhat.com>
    Reviewed-on: http://review.gluster.org/9799
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 65c68fb75640be2c5744782081250dda886a7b56
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 10 22:11:57 2015 +0530

    cluster/afr: Convert quota size from n/w to host order before use
    
    Change-Id: I3e4fe15716556441546fcd62b8ac2833869b21cf
    BUG: 1200670
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9853
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 02d42a5e80f3e2624eba2d00acff0aaebb20b12f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    nfs: add structures and functions for parsing netgroups
    
    Netgroups are often used by enterprises to group a set of systems. The
    NFS /etc/exports file support the @netgroup notation, and Gluster/NFS
    will get extended to support this notation as well. For this, it is
    needed that Gluster/NFS learns to parse the netgroup format.
    
    A change to glusterfsd (Change-Id I24c40d5) will add test cases where
    the parsing is used for regression testing.
    
    BUG: 1143880
    Change-Id: Ie04800d4dc26f99df922c9fcc00845f53291cf4f
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9360
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 381abb5bd2b09a4c40b20ddbe6d385f9a849e384
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Mar 10 19:27:50 2015 +0530

    glusterd: create nfs volfile even when NFS is disabled on all volumes
    
    This is required to determine if gluster-nfs daemon needs to be
    restarted. With http://review.gluster.org/9835 gluster-nfs volfile
    wouldn't be created if all volumes had nfs disabled before they were
    started even once. With the existing code, we wouldn't be able to
    determine if gluster-nfs needs to be restarted or reconfigured without
    the gluster-nfs volfile. This fix is ensure that we generate the
    gluster-nfs volfile even if it wouldn't be started, to honour the above
    requirement.
    
    Change-Id: I86c6707870d838b03dd4d14b91b984cb43c33006
    BUG: 1199944
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9851
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 219512c5014e9a13081d6a9981ae02b54586d801
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Feb 19 15:52:28 2015 +0530

    rdma: Free resources related to iobuf in fini
    
    If rdma transport is destroyed because of any reason,
    then rdma.so will be unloaded. But we are not setting
    iobuf registeration function to null. After this, if
    an iobuf request is came, then we will try to call a
    function which is not loaded.
    
    Change-Id: I3293f9974e16d8e865131785ee697ea02be8cdfc
    BUG: 1187456
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9697
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1a4e7362af1f351f389b73f9ae9c0b1fa423f7a3
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Feb 26 16:01:51 2015 +0530

    rdma:enhance logging when a connection error occur
    
    Change-Id: I6146307949a3d852d3af5f8b273004ad6b27451b
    BUG: 1196584
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9756
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e64415ad9d97e2dfd74481b47c88a0f483b4374a
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Mar 10 12:12:01 2015 +0530

    libglusterfs: Replace pipe2 with pipe.
    
    pipe2() doesn't works on Linux kernel version < 2.6.27 and
    glibc < version 2.9. Hence replacing it with pipe(),
    so that the build will not fail on Centos5.
    
    Change-Id: If17aed0d51466cd7528cf8dde0edfa28b68139e5
    BUG: 1200255
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9844
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f7d33653ebdeed737c101c64b53d638f2b40c886
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu May 1 08:23:52 2014 -0400

    glusterfs.spec.in: minor/nit changes to sync with Fedora spec
    
    sync with fedora spec
    
    Change-Id: Iddc55fbf82e5c4690669aa5836dc109b3d3fe19a
    BUG: 1091408
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/7632

commit 8f34055a2300cafadc03178ce03c7ce998399991
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Feb 3 05:30:50 2015 -0500

    build: don't report (hide) systemtap config option
    
    We don't actually support systemtap. We don't have any systemtap
    enablement. The configure doesn't actually do anything to configure
    systemtap support. It's confusing to show that systemtap is disabled,
    someone might try to run --enable-systemtap, and then we'll show that
    it's enabled, but it still doesn't actually do anything.
    
    Hide it until such time as we actually have some real systemtap support
    
    Change-Id: I8617121bee5bc724027e5f4d5eed00fd3c5a4ab2
    BUG: 865734
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/9564

commit d83ff159679095eedfdd9f42b2ed801d048493ce
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Feb 3 04:05:08 2015 -0500

    doc: convert gfapi symbol version to markdown and move to doc
    
    Change-Id: Iaa0dd288b24240660594023e04a7fd84e7e62a5e
    BUG: 1188557
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/9561

commit 4f2b49eefd1a56469770534d7941fa37ae759f11
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Mar 4 16:22:39 2015 +0100

    build: add more generated files to .gitignore
    
    Added *_unittest, *.log, *.trs, extras/run-gluster.tmpfiles and
    heal/src/glfsheal. Sorted the list of files to make it easier to modify
    in future.
    
    Change-Id: I0f21a03a89e61f84c6a85c8f1f98712c5819d633
    BUG: 1198849
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9803
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 9d6fab69105d866786d26d3d09158163ab5189c5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Mar 9 18:39:07 2015 -0400

    tests: add a helper script to identify line-numbers and commands of test-cases
    
    Use the tests/utils/testn.sh after a regression test failed to identify
    what command/line number belongs to the test-number.
    
    Jenkins will have something like this in the console output:
    
        Test Summary Report
        -------------------
        ./tests/bugs/quota/bug-1087198.t
          Failed test:  18
    
    Call the script like:
    
        $ ./tests/utils/testn.sh ./tests/bugs/quota/bug-1087198.t 18
        56 TEST grep -e "\"Usage crossed....
    
    BUG: 1200174
    Change-Id: I661c1178d7f5bc50fd40679232c65734c2bc5477
    Original-author: Pranith Kumar K <pkarampu@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9842
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b832e35493aca8c49359b1db4bd7ae3afbcdd2cb
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Mar 6 15:16:35 2015 +0530

    Performance: Replace ASSERTS in xlator fini() with info messages, for the known leaks.
    
    There are few known leaks in read-ahead and quick-read xlator fini().
    Until they are fixed replacing the ASSERTS with info, else any call
    to glfs_fini() in debug mode will core dump.
    
    Change-Id: Id60c6f952574863fc77c7d101cb5d5e9113090d8
    BUG: 1199436
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9819
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 1ae8b4c33af175545d6afe99aeb7a21896960a35
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Feb 5 16:12:53 2015 +0530

    snapshot: append timestamp with snapname
    
    Appending GMT time stamp with snapname by default.
    If no-timestamp flag is given during snapshot creation,
    then time stamp will not append with snapname;
    
    Initial consumer of this feature is Samba's Shadow Copy
    feature. This feature allows Windows user to get previous
    revisions of a file. For this feature to work snapshot
    names under .snaps folder (USS) should have timestamp in
    following format appended:
    @GMT-YYYY.MM.DD-hh.mm.ss
    
    PS: https://www.samba.org/samba/docs/man/manpages/vfs_shadow_copy2.8.html
    
    This format is configurable by Samba conf file. Due to a
    limitation in Windows directory access the exact format
    cannot be used by USS. Therefore we have modified the file
    format to:
    _GMT-YYYY.MM.DD-hh.mm.ss
    
    Snapshot scheduling feature also required to append timestamp
    to the snapshot name therefore timestamp is appended in
    snapshot creation itself instead of doing the changes in
    snapview server.
    
    More info:
    https://www.mail-archive.com/gluster-users@gluster.org/msg18895.html
    
    Change-Id: Idac24670948cf4c0fbe916ea6690e49cbc832d07
    BUG: 1189473
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9597
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8cdd272dcf277aa4148c57458cc5477a49b08383
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Feb 27 16:04:29 2015 +0530

    mgmt/glusterd: Changes required for disperse volume heal commands
    
    - Include xattrop64-watchlist for index xlator for disperse volumes.
    - Change the functions that exist to consider disperse volumes also
      for sending commands to disperse xls in self-heal-daemon.
    
    Change-Id: Iae75a5d3dd5642454a2ebf5840feba35780d8adb
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9793
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a38faffd2ccc104af37cffec4099f96ec354b891
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Mon Mar 9 18:13:39 2015 +0530

    rdma: return proper data type.
    
    Change-Id: I9bb0898af96cfcfaba0f0c976a7808bc6ea08e6a
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9838
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a70231c78aaea436575d427a1386a64d1471b776
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Feb 27 16:01:31 2015 +0530

    cluster/ec: Add self-heal-daemon command handlers
    
    This patch introduces the changes required in ec xlator to handle
    index/full heal.
    
    Index healer threads:
    Ec xlator start an index healer thread per local brick. This thread keeps
    waking up every minute to check if there are any files to be healed based on
    the indices kept in index directory. Whenever child_up event comes, then also
    this index healer thread wakes up and crawls the indices and triggers heal.
    When self-heal-daemon is disabled on this particular volume then the healer
    thread keeps waiting until it is enabled again to perform heals.
    
    Full healer threads:
    Ec xlator starts a full healer thread for the local subvolume provided by
    glusterd to perform full crawl on the directory hierarchy to perform heals.
    Once the crawl completes the thread exits if no more full heals are issued.
    
    Changed xl-op prefix GF_AFR_OP to GF_SHD_OP to make it more generic.
    
    Change-Id: Idf9b2735d779a6253717be064173dfde6f8f824b
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9787
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 72dc1025dc17a650f3838223c78e3205132deba9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Feb 10 19:13:35 2015 +0100

    posix: add ACL translation for the GF_POSIX_ACL_*_KEY xattr
    
    Adding support for two virtual extended attributes that are used for
    converting a binary POSIX ACL to a POSIX.1e long ACL text format. This
    makes it possible to transfer the ACL over the network to a different OS
    which can convert the POSIX.1e text format to its native structures.
    
    The following xattrs are sent over RPC in SETXATTR/GETXATTR procedures,
    and contain the POSIX.1e long ACL text format:
    
    - glusterfs.posix.acl: maps to ACL_TYPE_ACCESS
    - glusterfs.posix.default_acl: maps to ACL_TYPE_DEFAULT
    
    acl_from_text() (from libacl) converts the text format into an acl_t
    structure. This structure is then used by acl_set_file() to set the ACL
    in the filesystem.
    
    libacl-devel is needed for linking against libacl, so it has been added
    to the BuildRequires in the .spec.
    
    NetBSD does not support POSIX ACLs. Trying to get/set POSIX ACLs on a
    storage server running NetBSD, an error will be returned with errno set
    to ENOTSUP. Faking support, but not enforcing ACLs seems wrong to me.
    
    URL: http://www.gluster.org/community/documentation/index.php/Features/Improved_POSIX_ACLs
    BUG: 1185654
    Change-Id: Ic5eb73d69190d3492df2f711d0436775eeea7de3
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9627
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 7d3f27d4c9421c976eec3a39004e84bad20586d7
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Mar 9 10:29:29 2015 +0100

    Tests: fix spurious failure in sparse-file-self-heal.t
    
    On NetBSD sparse-file-self-heal.t often fails because $HEAL_TIMEOUT
    is too short. Raising to 80s works around the problem, as discovered
    by Anuradha Talur
    
    BUG: 1129939
    Change-Id: Ia950ff70ace24771ab1ef7fce51861f2417f86ab
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9833
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e99f9d3408e44c0ec12488662c9491be7da1f1fe
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Mar 9 15:53:53 2015 +0530

    glusterd: don't start gluster-nfs when NFS is disabled
    
    Change-Id: Ic4da2a467a95af7108ed67954f44341131b41c7b
    BUG: 1199944
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9835
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8612553ffe3d87481c70911a9b8491fb5f4139b5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 9 19:35:14 2015 +0530

    Fix dictionary leaks in ancestry-building code.
    
    Change-Id: I7a4a24ed95f897d1c14d89f3869c20ba40f85b7f
    BUG: 1188636
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9839
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 83eab209d82c92a2676d1f794d5d24af0ac5bbab
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Mon Mar 9 12:07:57 2015 +0530

    core : using gluster-like memory allocation for parse-utility feature
    
    Change-Id: I58dc7e0dc8d4ac4e10795e0536fcd0e1722116ed
    BUG: 1143880
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/9830
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3361bab0388f7cdad50e1c67e1127801fda05685
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Mar 7 06:10:41 2015 +0100

    glfsheal: Avoid infinite loop on exit
    
    Make sure we do not get stuck looping forever in event_dispatch_destroy()
    by limiting the retries when waiting for other threads, and by giving up
    when writing to other thread fails.
    
    This fixes regression tests hanging forever on NetBSD.
    
    BUG: 1129939
    Change-Id: I4459cfb1ab7294e8c15a21b592e0154c22abae07
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9825
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 854383198b6f02d85b4209a8e7dd7e7c0c118793
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Mar 5 17:28:08 2015 +0530

    rdma:  'list','wr' and 'new' memory has to be verified.
    
    Change-Id: I29a8825107b8f4cefe4f4c59296e98fe675ee943
    BUG: 1199053
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9811
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit b5e50cd714d105ff7aa1544182f07fb60320710d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 6 12:37:15 2015 +0530

    libxlator: Make sure marker_xattr is valid
    
    Problem:
    marker_xattr is allocated only when the op_ret is 0. If the final response is
    a failure, then the marker time is dict_set with key as NULL. this will be
    changed to ref:<address-of-value> by dict_set, so the value won't appear on the
    marker-key when the getxattr_cbk is in dht. So dht unwinds with failure EINVAL.
    
    Fix:
    Always populate marker_xattr. Fixed dict mem-leak as well.
    
    Change-Id: I1752f277a8852c47b0a2ccce9fd72ee88456ac02
    BUG: 1199406
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9817
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 5ab4a17a63acf7215e9dc98276e7547ae527a5a7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 6 14:36:52 2015 +0530

    cluster/afr: Handle getxattr of quota-size key
    
    Afr needs to query QUOTA_SIZE_KEY from all the subvolumes and return the
    value which is maximum of the readable bricks.
    
    Change-Id: Ibb9064c8652aea0d984796e7a06f8adca72aa971
    BUG: 1199431
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9820
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 3ceb64f3bd0919c556829c7297e67fb3ba40eaa9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Jan 31 00:32:05 2015 +0530

    mgmt/glusterd: Add bind-insecure option
    
    Also deleted default values for disperse-self-heal-daemon and locks.trace
    
    Change-Id: Icc927d176aa10f06b40c114aa296b02dbad3a8ff
    BUG: 1187858
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9516
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit f7f446f0a5bc37ba1096604618ab9850341959ef
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Feb 27 23:47:26 2015 +0100

    nfs: prevent logging missing 'system.posix_acl_access' xattrs
    
    Change http://review.gluster.org/9773 addresses the majority of the
    logging, but it seems it is still possible to trigger the excessive
    logging by requesting the ACL on files directly. Lets squash those too.
    
    BUG: 1197253
    Change-Id: I9e90ddd45f1a39641478f34c69c64dfe1c11c727
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9781
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>

commit 9b3c799fa3a5535e189d18200324d912339ac6a6
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Feb 24 16:48:20 2015 +0530

    gfapi: Add NULL check for volname in glfs_new()
    
    BUG: 1199388
    Change-Id: I66cb65355504eb47e4392576029a9a5422996a1b
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/9735
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit a25cdf135f01ebeb64a4497df1bb5146bfdc6620
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 13 11:45:53 2014 +0530

    Use common loc-touchup in fuse/server/gfapi
    
    Change-Id: Id41fb29480bb6d22c34469339163da05b98c1a98
    BUG: 1115907
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8226
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit adef0c8860f57c8137382d848244009e9a584497
Author: Nico Schottelius <nico@freiheit.schottelius.org>
Date:   Fri Mar 6 16:25:33 2015 +0100

    Replace /dev/stderr with >&2 in mount scripts
    
    /dev/stderr is not available on boot in CentOS 7 and thus
    mounting anything from /etc/fstab at boot time fails.
    
    Instead of using /dev/stderr, the standard error redirection ">&2" is being used.
    
    Change-Id: I15d07cd49e6b0392331047edb441925f48047b2b
    BUG: 1199545
    Signed-off-by: Nico Schottelius <nico@freiheit.schottelius.org>
    Reviewed-on: http://review.gluster.org/9824
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3d9423354a2d688c3609258883b1c03422996978
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 6 10:59:01 2015 +0530

    protocol: Fix typos in option description
    
    Change-Id: I7cf559fa5ffe3f6c437169820a86a7ee2f58b478
    BUG: 1199382
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9816
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c6bfde4da5da40f81ab7d96f4d43adb2553a633d
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Feb 24 16:36:05 2015 +0530

    cluster/dht: create request dictionary if necessary during refresh
    layout.
    
    Change-Id: I5a5d793c86ee5de345608eede5618e4e6c02af9f
    BUG: 1195668
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/9733

commit 3797caabb95ad8e62dee74a5331d324ddffc654f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Feb 2 18:49:01 2015 +0530

    cluster/afr: Implementation of quorum-reads
    
    Provide a way of disabling reads when quorum is not met.
    
    Change-Id: Ic4f57c2b87a0b8514600759de3a7a47e217fe3b5
    BUG: 1187885
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9543
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8fa36bc7a11968086e31ac32b9a24de07dd50d15
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 2 08:09:41 2015 +0530

    cluster/ec: Allow heal on name less loc
    
    loc->parent may not always be populated. Even in those cases,
    self-heal should happen if it can be completed using nameless loc.
    
    Change-Id: I8871fc811bec8b881ae7fb09dcd202c6693b9877
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9717
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1a2c1e9bf8d711d821fbd166ed6d7f7d9bcce69d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Sun Mar 1 11:48:12 2015 +0530

    geo-rep: Avoid duplicate entries in authorized_keys file
    
    When Georep create(force) command is run multiple times
    it appends master nodes public keys to Slave nodes without
    checking the existence of the key.
    
    With this patch, create push-pem force adds pub key only if
    not available in authorized_keys.
    
    BUG: 1197433
    Change-Id: Iad57f6c45698e258ad1a547fa7a2e376a315f0cd
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9776
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2452d284b38061981d7fbd7e5a7bd15808d13c21
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Mar 3 17:22:30 2015 +0530

    geo-rep: Handle ENOENT during cleanup
    
    shutil.rmtree was failing to remove file if file was not
    exists. Added error handling function to ignore ENOENT if
    a file/dir not present.
    
    BUG: 1198101
    Change-Id: I1796db2642f81d9e2b5e52c6be34b4ad6f1c9786
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9792
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>

commit bc2e58a436002e1627a225663bc7b11dddc1172f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Feb 18 14:47:01 2015 +0100

    testing: Switch to cmocka the successor of cmockery2
    
    This uses https://cmocka.org/ as the unit testing framework.
    
    With this change, unit testing is made optional as well. We assume there
    is no cmocka available while building. cmocka will be enabled by default
    later on. For now, to build with cmocka run:
    
        $ ./configure --enable-cmocka
    
    This change is based on the work of Andreas (replacing cmockery2 with
    cmocka) and Kaleb (make cmockery2 an optional build dependency).
    
    The only modifications I made, are additional #defines in unittest.h for
    making sure the unit tests function as expected.
    
    Change-Id: Iea4cbcdaf09996b49ffcf3680c76731459cb197e
    BUG: 1067059
    Merged-change: http://review.gluster.org/9762/
    Signed-off-by: Andreas Schneider <asn@samba.org>
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Change-Id: Ia2e955481c102d5dce17695a9205395a6030e985
    Reviewed-on: http://review.gluster.org/9738
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0bef7717d3100734c6c5a4ba85de7a39e76774db
Author: Michael Scherer <misc@zarb.org>
Date:   Mon Mar 2 16:24:05 2015 +0100

    build: adjust checkpatch for HEAD.
    
    README is called README.md in git HEAD, and we have a directory
    heal.
    
    Change-Id: I2e698b95c6924b5b21aa54257fefd6a6698255ee
    BUG: 1198849
    Signed-off-by: Michael Scherer <misc@zarb.org>
    Reviewed-on: http://review.gluster.org/9784
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 8e1fb1ca03e252036b90490d5b7f390b5a9b4413
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Tue Feb 3 15:21:51 2015 +0530

    xlators/dht : divide by zero coverity fix
    
    CID:1226163. BUG: 789278
    
    Change-Id: Ie31d65da236d7029784defad963672b2ded2676a
    BUG:1192435
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9563
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit e944ff1f5a187863343691dfc108237c10dde287
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Mar 5 14:23:38 2015 +0530

    cluster/dht: fixes to should_layout_fix logic
    
    * Don't consider "dir-spread-count" option. This option is not
    supported.
    * Consider transition to weighted to equal distribution or vice-versa
    a valid case for fixing the layout.
    
    Change-Id: I0dcfe555dae9269ce20a41611cfdaa4f96c9e98b
    BUG: 1196615
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/9809
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e08aea2fd67a06275423ded157431305a7925cf6
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Mar 4 14:37:05 2015 +0530

    rdma:setting wrong remote memory.
    
    when we send more than one work request in a single call,
    the remote addr is always setting as the first address of
    the vector.
    
    Change-Id: I55aea7bd6542abe22916719a139f7c8f73334d26
    BUG: 1197548
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9794
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 4a8384fe76aeef652554c48df737d3178eb0160c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Feb 19 19:35:17 2015 +0530

    cluster/afr: Do not increment healed_count if no healing was performed
    
    PROBLEM:
    When file modifications are happening while index heal is launched,
    index healer could pick up entries which appeared in indices/xattrop
    transiently during the course of the operations on the mount point, and
    do not really need any heal. This will cause index healer to keep doing
    index-heal in a loop as long as it finds this entry, by believing that
    it did successfully heal some gfids even when it didn't.
    
    FIX:
    afr_selfheal() now returns a 1 to indicate that it did not (need to)
    heal a given gfid. afr_shd_selfheal() will not increment healed_count
    whenever afr_selfheal() returns a 1.
    
    Change-Id: I0d97e11392a032a852e8c6508f691300ef0e5b98
    BUG: 1194305
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9713
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a42db19a5dd796f5387b0765f5fc05cef462df22
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Feb 19 04:09:26 2015 +0530

    libglusterfs: Change iobuf_pool_destroy to destroy all the arenas.
    
    Change-Id: If5e9d4ce98f845d3b52565ac62970959e663497f
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9699
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 2899e783af4a9036d1c83854c824bd1680f24cef
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Wed Mar 4 19:16:20 2015 +0530

    tests: Spurious failure in bug-1117851.t
    
    This test runs file renames in a loop in the background and
    writes to a status file to indicate that it is done.
    However, the status file was also created in the background
    and was sometimes not created in time before the test which
    checked the contents.
    
    Change-Id: Ida29456fbdc006f1da84a5f25a629cc6fa9830f4
    BUG: 1163543
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/9798
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 9c5011b8e49e34d736ba7cfadc0802e8b80682a7
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Feb 19 21:29:02 2015 +0530

    glfs_fini: Clean up all the resources allocated in glfs_new.
    
    Initially even after calling glfs_fini(), all the threads created
    during init and many other resources like memory pool, iobuf pool,
    event pool and other memory allocs were not being freed.
    With this patch these resources are freed in glfs_fini().
    
    The two thumb rules followed in this patch are:
    - The threads are not killed, they are made to exit voluntarily,
      once the queued tasks are completed. The main thread waits for
      the other threads to exit.
    - Free the memory pools and destroy the graphs only after all the
      other threads are stopped, so that there are less chances of
      hitting access after free.
    
    Resources freed and its order:
    1. Destroy the inode table of all the graphs - Call forget on all the inodes.
       This will not be required when the cleanup during graph switch is
       implemented to perform inode table destroy.
    2. Deactivate the current graph, call fini of all the xlators.
    3. Syncenv destroy - Join the synctask threads and cleanup syncenv resources
       Sets the destroy mode, complete the existing synctasks, then join the
       synctask threads.
       After entering the destroy mode,
            -if a new synctask is submitted, it fails.
            -if syncenv_new() is called, it will end up creating new threads,
            but this is called only during init.
    4. Poller thread destroy
       Register an event handler which sets the destroy mode for the poller.
       Once the poller is done processing all the events, it exits.
    5. Tear down the logging framework
       The log file is closed and the log level is set to none, after this
       point no log messages appear either in log file or in stderr.
    6. Destroy the timer thread
       Set the destroy bit, once the pending timer events are processed
       the timer thread exits.
       Note: Log infrastructure should be shutdown before destroying the timer
       thread as gf_log uses timers.
    7. Destroy the glusterfs_ctx_t
       For all the graphs(active and passive), free graph, xlator structs and few other lists.
       Free the memory pools - iobuf pool, event pool, dict, logbuf pool,
       stub mem pool, stack mem pool, frame mem pool.
    
    Few things not addressed in this patch:
    1. rpc_transport object not destroyed, the PARENT_DOWN should have
       destroyed this object but has not, needs to be addressed as a part
       of different patch
    2. Each xlator fini should clean up the local pool allocated by its xlator.
       Needs to be addresses as a part of different patch.
    3. Each xlator should implement forget to free its inode_ctx.
       Needs to be addresses as a part of different patch.
    3. Few other leaks reported by valgrind.
    4. fd and fd contexts
    
    The numbers:
    The resource usage by the test case in this patch:
    Without the fix, Memory: ~3GB; Threads: ~81
    With this fix, Memory: 300MB; Threads: 1(main thread)
    
    Change-Id: I96b9277541737aa8372b4e6c9eed380cb871e7c2
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7642
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit f82756b4909cebaf533570aec2b05ba55a7dcc95
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Mar 3 17:21:54 2015 +0530

    glusterd: Start quotad before spawning bricks during glusterd restart
    
    Change-Id: I66edc1b98b70a494e069df95a6f347634c8f862d
    BUG: 1198076
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9791
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 80ebd3a25ae7dcfcaebec58d7a80b919e2eed5ee
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Dec 14 21:33:17 2014 +0100

    changelog:  Unchecked buffer fill in gf_history_changelog_next_change
    
    A gf_history_changelog_next_change() calls gf_readline() to fill a
    buffer without checking buffer size. The size of maxlen is not verified
    to be less than the lenght of buffer. This could result in the over
    filling of buffer of maxlen is greater than PATH_MAX.
    
    Check the size of maxlen to be less than PATH_MAX and return a fail code
    as needed.
    
    BUG: 1174017
    Change-Id: Ic53b1a6e25af69a339bc15fb2d233dc1e457910f
    Reported-by: Keith Schincke <kschinck@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9275
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit f8b1bedd9de38d3d3be0b05c1bf5231f979a2cf1
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Sep 26 17:57:58 2014 +0530

    doc: Update glusterfs introduction doc.
    
    Change-Id: I4e9520bf46b7b9611c3719623a940b16b4cadda0
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8870
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 673ba2659cebe22ee30c43f9fb080f330150f55e
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jan 6 18:23:41 2015 +0530

    glusterd: Replace libglusterfs lists with liburcu lists
    
    This patch replaces usage of the libglusterfs lists data structures and
    API in glusterd with the lists data structures and API from liburcu. The
    liburcu data structes and APIs are a drop-in replacement for
    libglusterfs lists.
    
    All usages have been changed to keep the code consistent, and free from
    confusion.
    
    NOTE: glusterd_conf_t->xprt_list still uses the libglusterfs data
    structures and API, as it holds rpc_transport_t objects, which is not a
    part of glusterd and is not being changed in this patch.
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      6dac576 Replace libglusterfs lists with liburcu lists
      a51b5ab Fix compilation issues
      d98a06f Fix merge issues
      a5d918e Remove merge remnant
      1cca113 More style cleanup
      1917be3 Address review comments on 9624/1
      8d10f13 Use cds_lists for glusterd_svc_t
      524ad5d Add rculist header in glusterd-conn-helper.c
      646f294 glusterd: add list_add_order API honouring rcu
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: Ic613c5b6e496a677b9d3de15fc042a0492109fb0
    BUG: 1191030
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9624
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>

commit ef061b67f1b80c147c1959b896f7c9bdff01af96
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Feb 26 22:50:25 2015 +0530

    cluster/dht: Fixes to should_fix_layout logic
    
    * With recent introduction of locking in self-heal codepath,
      fix layout was not allowed to progress during remove-brick.
      This patch fixes the issue.
    
    * dht_should_fix_layout also considers "dir-spread-count" option if
      set, to determine whether we should proceed with fix-layout or not.
    
    Change-Id: Icd96986f7af705744131d62e7f1456114ac1ee53
    BUG: 1196615
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/9764
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit 95d5e60afb29aedc29909340e7564d54a6a247c2
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 1 13:15:45 2015 +0100

    core: add generic parser utility
    
    This generic parser will get used for parsing the netgroups and exports
    files for the Gluster/NFS server. The parsing of netgroups shows how the
    parser can be used (see Change-Id Ie04800d4).
    
    BUG: 1143880
    Change-Id: Id4cf2b0189ef5799c06868d211d3fcd9c8608c08
    Original-author: Shreyas Siravara <shreyas.siravara@gmail.com>
    CC: Richard Wareing <rwareing@fb.com>
    CC: Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9359
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2acfbcf34ed77985905b2d122adbfd541eb01db1
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Feb 18 21:40:46 2015 +0530

    event_pool: Add the code to destroy the poller threads and event pool gracefully.
    
    Change-Id: I49b6ceebb45773620c318fb5d20b81623db75ab6
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9691
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 4ff398987805ba72010d328c61a5682088d32cf4
Author: Manikandan Selvaganesh <mselvaga@redhat.com>
Date:   Thu Feb 5 10:59:48 2015 +0530

    dht : logically dead code removed
    
    CID :1124378
         1124401
    
    Change-Id: Ib48e4a8d3fb12c4e0323a3946afb46eeb3926984
    BUG: 789278
    Signed-off-by: Manikandan Selvaganesh <mselvaga@redhat.com>
    Reviewed-on: http://review.gluster.org/9584
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 1dc89418ec39929f6f9de448da85966beffeef27
Author: vmallika <vmallika@redhat.com>
Date:   Mon Mar 2 12:52:22 2015 +0530

    quota: quotad.socket  files should be created under /var/run/gluster
    
    Change-Id: I49502a4f7516c02f7e321c16eebd748545afde07
    BUG: 1197587
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9778
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a5b02c0d71c7952ebbb24b1075c216cc76761956
Author: Michael Scherer <misc@zarb.org>
Date:   Mon Mar 2 16:13:40 2015 +0100

    tests: prevent deleting /etc/passwd
    
    This happened twice last week on our gluster jenkins slave,
    http://www.gluster.org/pipermail/gluster-infra/2015-March/000818.html
    
    Change-Id: I40ff0e143256fb1b33ee4ab6dd0850727f9e2135
    BUG: 1163543
    Signed-off-by: Michael Scherer <misc@zarb.org>
    Reviewed-on: http://review.gluster.org/9785
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 33214ef83684c3b025c773931c071f8af030242b
Author: Mark Lipscombe <mlipscombe@gmail.com>
Date:   Fri Feb 27 15:36:48 2015 -0800

    rdma: segfault trying to call ibv_dealloc_pd on a null pointer
    if ibv_alloc_pd failed
    
    If creating an ib protection domain fails, during the cleanup
    a segfault will occur because trav->pd is null.
    
    Bug: 1197260
    Change-Id: I21b867c204c4049496b1bf11ec47e4139610266a
    Signed-off-by: Mark Lipscombe <mlipscombe@gmail.com>
    Reviewed-on: http://review.gluster.org/9774
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 4f65179a8f90547498b00caf48eaad618098ae70
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Feb 25 17:10:12 2015 +0530

    afr: catch proper result of glfs_set_volfile_server
    
    Change-Id: I5a1db7b88c33bf5faa7a8848502357b052a799f4
    BUG: 1194640
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9746
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit fc54f75ea49605e7fb5808e3fc01dfaa6b7c4649
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Feb 19 03:45:34 2015 +0530

    libglusterfs: Add functions for xlator and graph cleanup.
    
    Change-Id: If341e3c0a559aa5bbca9c1263a241c6592c59706
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9696
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7e416b6d00d626219c8d2067be720a915c4f85b1
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Feb 19 05:29:02 2015 +0530

    libglusterfs: Add timer thread destroy code.
    
    Change-Id: Iafbbbfd9319751742b3c79419e1dd8e2958fee07
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9701
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 84e6eac265c87be5e436f3e7a41f40dc2d9c65c5
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Feb 19 01:24:29 2015 +0530

    syncop: Add the code to destroy the synenv processors and
            syncenv structures
    
    Change-Id: I28020eb2fc08d886cd7c05ff96daf7ebb4264ffe
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9693
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5e12c658d6c2dc92fd336b745036641f054b3a40
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu Feb 19 04:49:35 2015 +0530

    libglusterfs: Add inode table cleanup APIs.
    
    Took the inode context free code from the patch
    http://review.gluster.org/#/c/4775/18/libglusterfs/src/inode.c
    
    Change-Id: I05fc025763fe4ce61dc61503de27ec1d3a203e50
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9700
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7c44ac371cc7553bd8d29455dafc2c07cf5b96e1
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Fri Feb 20 18:01:50 2015 +0530

    logging: Adding msg id segment for common errors.
    
    By this reservation, we are assigning some space for common errors
    like dict_{get,set},memory accounting..etc.
    
    Change-Id: Iee0f65b3dc4e00819f344bed01989352a4f8a87b
    BUG: 1194640.
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9752
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 1455ee40030c8d3c4818ba7d7ca8ca851e12b848
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jan 28 17:19:42 2015 +0530

    geo-rep: Add support for xattrs
    
    This patch adds support for xattrs. When it sees SETXATTR
    in Changelog, it adds the file to data queue. rsync/tar+ssh
    will take care of syncing xattrs. User set xattrs will be
    synced to Slave.
    
    New config interface is introduced, sync-xattrs
    Which can be set using geo-rep config(Default is True)
    
    gluster volume geo-replication <VOLUME> <SLAVEHOST>::<SLAVEVOL> \
                   config sync-xattrs false
    
    Change-Id: I70626d854a0d616469dd54d61e5ef155ed8b67d8
    BUG: 1196690
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9499
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c3e6d6b54741cfbc828272ace576339ae3a37173
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Dec 17 21:43:57 2014 +0530

    geo-rep: Unit tests infrastructure for geo-replication
    
    Added sample unit test file,
    $GLUSTER_SRC/geo-replication/tests/unit/test_syncdutils.py
    
    Install unittest dependencies, (tox https://tox.readthedocs.org/en/latest/,
    nose https://nose.readthedocs.org/en/latest/)
        sudo pip install --upgrade tox nose
    
    To run pep8 coding standards tests,
        cd $GLUSTER_SRC/geo-replication
        tox -e pep8
    
    To run unit tests,
        cd $GLUSTER_SRC/geo-replication
        tox -e py27
    
    py27 is for with Python 2.7+, or py26 for systems
    with Python 2.6+
    
    Change-Id: Ibdefe2c9d73afda9a7fa1c0db5b126f592b7cb40
    BUG: 1177722
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9290
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit efe09fff57dc01088168e60bff355b769c1bc7f7
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Feb 18 15:16:17 2015 +0530

    protocol/client: defer cleanup of private until RPC notifications are handled.
    
    This fix is required for glfs_fini to be able to perform fini on client
    xlators in a graph. We are deferring freeing of client xlator's private
    until all RPC related resources are destroyed. This guarantees that
    client xlator would free RPC related resources provided its private
    structures are still accessible via its this pointer.
    
    'Weak' property: If there are no epoll threads executing after calling
    fini() on a client xlator, then all its RPC related resources are
    guaranteed to be freed. We can now free the corresponding 'this'
    pointer.
    
    Change-Id: Ie00b14dda096ac128e1c37e0032f07d17fd701ce
    BUG: 1093594
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9680
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 60cff8ab4f5fa2ee7bea028937ba23674e1ee0cc
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Feb 23 16:10:33 2015 +0530

    epoll: Fix a leak in slot allocation.
    
    When the slots_used in a table becomes 0, the table will not
    get reused, leading to a leak.
    
    This patch fixes the leak.
    
    Change-Id: Ib86826d287368174ea7ebe0d0d64b2dec574634e
    BUG: 1093594
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9725
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4f143bfe4eabc34c5682a3b0421092e5e22ee507
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Feb 27 23:47:26 2015 +0100

    nfs: prevent logging missing 'system.posix_acl_*' xattrs
    
    The nfs.log gets spammed with messages that the system.posix_acl_access
    and system.posix_acl_default xattrs are not set. The logging happens
    because the dictionary that contains the xattrs is empty/NULL in case
    the getxattr() did not return any contents for the ACLs.
    
    Change-Id: Id31e30635146599915c6d8674a2dde065f348adc
    BUG: 1197253
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9773
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>

commit c48cbccfafbcf71aaad4ed7d868dbac609bc34fe
Author: Shyam <srangana@redhat.com>
Date:   Mon Feb 23 10:00:39 2015 -0500

    epoll: Fix broken RPC throttling due to MT epoll
    
    The RPC throttle which kicks in by setting the poll-in event on a
    socket to false, is broken with the MT epoll commit. This is due
    to the event handler of poll-in attempting to read as much out of
    the socket till it receives an EAGAIN. Which may never happen and
    hence we would be processing far more RPCs that we want to.
    
    This is being fixed by changing the epoll from ET to LT, and
    reading request by request, so that we honor the throttle.
    
    The downside is that we do not drain the socket, but go back to
    epoll_wait before reading the next request, but when kicking in
    throttle, we need to anyway and so a busy connection would degrade
    to LT anyway to maintain the throttle. As a result this change
    should not cause deviation in the performance much for busy
    connections.
    
    Change-Id: I522d284d2d0f40e1812ab4c1a453c8aec666464c
    BUG: 1192114
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9726
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 56488efe3c858da7f8a0b66d30a2eface2f6f35e
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu Jan 29 12:56:35 2015 +0530

    rpcsvc: New rpc routines defined to send callback requests
    
    Change-Id: I7f95682faada16308314bfbf84298b02d1198efa
    BUG: 1188184
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/9534
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 32dd227726ce60b2e60b8df61ca174d96a1b8b34
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Feb 27 15:30:04 2015 +0100

    nfs: nfs3_stat_to_fattr3() improvement
    
    During a review of backorti http://review.gluster.org/9170, Kaleb points
    out:
    
        ick, return-by-value. About 50% slower than passing a pointer to the
        target struct.
    
    Change-Id: I4464e6a4e50d82d446a834892d0308332b7c32d0
    BUG: 1197142
    Reported-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9772
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5b4755e9494b80f7b57c1515773991c962af0a2a
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Feb 27 16:46:58 2015 +0100

    NetBSD Portability fix: use pkill instead of killall
    
    NetBSD does not have the killall command.
    
    BUG: 1129939
    Change-Id: Ie022bfb7efd6288ab19050addcfbd2822fbc78c0
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9771
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit b117d4d84becd25ef79c049ebf9b8ec6c4abca88
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Feb 25 15:49:11 2015 +0530

    socket: allow only one epoll thread to read msg fragments
    
    __socket_read_reply function releases sock priv->lock briefly for
    notifying higher layers of message's xid. This could result in other
    epoll threads that are processing events on this socket to read further
    fragments of the same message. This may lead to incorrect fragment
    processing and result in a crash.
    
    Change-Id: I915665b2e54ca16f2ad65970e51bf76c65d954a4
    BUG: 1197118
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9742
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a0f30e637e6ee32b113fd21268be17e0618d39df
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Feb 27 13:25:37 2015 +0100

    Tests: At cleanup time, kill rpc.statd on NetBSD
    
    The NFS server cannot start is a rpc.statd is still running. Make
    sure the cleanup procedure remove any leftover rpc.statd.
    
    BUG: 1129939
    Change-Id: I03c41b18526583f3304321e4e4a27e99b8fbf1f6
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9770
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d5624b2d4baf509ad8d6037a0d9cabf9cd5ab1c5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 25 11:37:57 2015 +0530

    libglusterfs: Moved common functions as utils in syncop/common-utils
    
    These will be used by both afr and ec. Moved syncop_dirfd, syncop_ftw,
    syncop_dir_scan functions also into syncop-utils.c
    
    Change-Id: I467253c74a346e1e292d36a8c1a035775c3aa670
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9740
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6a77db6d19dba5367c02cbf2a5883ac49cef94e2
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Feb 27 03:50:40 2015 +0100

    Tests: give sane default for NetBSD NFS mount retry count
    
    Default NetBSD NFS retry count is 10000, which means tests will loop
    for a long time if the server is not available.
    
    We fix this by setting a default retry count to 2 (1 seems to low and
    breaks regression). If mount_nfs is called with a retry option, it will
    overrride this default.
    
    BUG: 1129939
    Change-Id: I1ae16f8caa74d6e9af1aa7a55fd111178af0ad78
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5dc152aac25ac7680ce0f83edc580d2a953d27a7
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Feb 25 15:44:59 2015 +0530

    libgfapi: In glfs_init() set the cwd to "/".
    
    Initially, when the cwd is NULL, while resolving a
    relative path, it was taken to be relative from the root
    of the volume.
    But this behaviour changed with the patch:
    http://review.gluster.org/#/c/9671/
    with this patch, if cwd is NULL, all the fops on the files
    (given relative path) under root directory will fail.
    
    Hence, setting the cwd to "/" during glfs_init() itself.
    
    Change-Id: I65018f6cd42539d09852069b84099034b9925418
    BUG: 1196019
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/9744
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fc214f0f90ab195b7542a18cc918db467f575b37
Author: Anoop C S <achiraya@redhat.com>
Date:   Sat Dec 20 12:22:02 2014 +0530

    cluster/dht: Propagate an event only after hearing the same from all subvolumes
    
    In dht_notify(), we propagate each event without checking whether
    all subvolumes have reported the same event earlier. As a result
    separate events are being forwarded for each dht-subvolume.
    
    This change is to make sure that we propagate a particular event
    only if all other subvolumes have already reported the same event
    once earlier.
    
    Change-Id: I6c73fa105e967f29648af9e2030f91a94f2df130
    BUG: 1176543
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/9322
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit f364d963b63a13979d07f7871a3c02b205e20bed
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Feb 26 13:59:02 2015 +0100

    dht: fix for dht_lock_count() compile error
    
    dht-common.h includes a function definition with "inline", but the
    function is not declared in the header. Dropping the "inline" compile
    directive so that linking against .o files works correctly.
    
    BUG: 1196650
    Change-Id: I105be591125b29cd455769b0c4ff22d6e139227d
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9760
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 0e3fd04e93b163f27ecbea4a3a777c041b4352b4
Author: Mark Lipscombe <mlipscombe@gmail.com>
Date:   Tue Feb 24 12:28:27 2015 -0800

    rdma: Fix failure to call rdma_bind_addr if unable to bind privileged port.
    
    When unable to bind a privileged port, rdma_bind_addr is not called.
    
    This patch fixes that.
    
    Change-Id: I175884a5d6a08b93dc62653ee0a6622bfc06e618
    Bug: 1195907
    Signed-off-by: Mark Lipscombe <mlipscombe@gmail.com>
    Reviewed-on: http://review.gluster.org/9737
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit d1397dbd7d6cdbd2d81d5d36d608b6175d449db4
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Feb 25 20:34:41 2015 +0530

    mgmt/glusterd: Refactor brick graph generation in volgen.
    
    This commit does the following:
    
    1. Adds several new functions for generation of brick xlator units
       in a volgen. Each such function takes care of generation of only
       one xlator in volgen.
    
    2. A new table, server_graph_table, links all individual graph generation
       functions together.  The order of xlator function generators in the
       table determines the topology of the brick graph.
    
    3. server_graph_builder() invokes individual graph generators by walking
       through server_graph_table. Addition of debug xlators into the brick
       graph is also handled by this walk. As a result, a lot of cruft that
       is present in the exisiting implementation of this function gets
       cleaned up.
    
    4. get_server_xlator() now makes use of server_graph_table to determine
       whether a xlator key corresponds to a server xlator or not.
    
    Change-Id: I46bb6e331544150302eb5b33c4007917aff2586d
    BUG: 1188196
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/9751
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2a60854e8360309347236852989d520a04975e9c
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Feb 24 10:25:16 2015 +0530

    cluster/dht: serialize execution of dht_discover_complete and
    STACK_DESTROY (frame).
    
    In the current code, dht_discover_complete can be invoked because of:
    1. attempt_unwind is true
    2. we are processing reply from the last subvolume
    
    In scenario 1, following race is possible:
    
    T1: calls dht_frame_return.
    T2: calls dht_frame_return. This happens to be last call and hence it
        invokes dht_discover_complete, goes ahead and destroys frame
    T1: since attempt_unwind is true, calls
        dht_discover_complete. However, since frame is already freed, call
        to dht_discover_complete can result in a crash.
    
    The fix is to make sure that destruction of the frame is done only by
    the thread executing dht_discover_complete.
    
    Change-Id: I45765b90c4a9d0af0b33f8911b564d99e12d099e
    BUG: 1195120
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/9729
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit 9112806b02b1c8668acff87af62553462aa7cf48
Author: Anuradha <atalur@redhat.com>
Date:   Mon Feb 9 12:44:33 2015 +0530

    cluster/afr : provide split-brain info by using getxattr
    
    This patch is one part to enable users analyze and resolve
    split-brain.
    
    Problem : To know if a file is in data/metadata split-brain
    
    Solution : Performing "getfattr -n afr.split-brain-status
    <path-to-file>" from the mount provides this information.
    Also provides the list of afr children to analyse to
    get more information.
    
    Change-Id: I4d9b429794759a906371416cb84c84a212e2c7b9
    BUG: 1191396
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9633
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1fd540c386b3b4a99e3ee1b926a30f0992266983
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Wed Feb 25 19:37:22 2015 +0530

    spec: correcting GlusterFS string
    
    Change-Id: Ia39d81f89cf783016700c8059f6a788029ee1b13
    BUG: 1075417
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9749
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1dbe0d63259f1fe63c453d56fd97567368e9c0f5
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Mon Feb 23 20:50:37 2015 +0530

    README: Adding information about Gluster dev workflow
    
    In the README.md (which is automatically rendered in
    github) there is no information about GlusterFS
    workflow. So community members send pull requests in
    github.
    
    This patch will put the workflow information, so that
    it would be easy for community members to know about
    it by looking at GlusterFS's github mirror.
    
    Change-Id: I62718f75aa26a45fe28e3e9399d1aa2338211c73
    BUG: 1195336
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/9727
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 5d59402af8397da1a8eb5f822e1e650ce3285833
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Feb 6 17:06:28 2015 +0530

    features/index: Add option to track specific xattrs for xattrop64
    
    This enables trusted.ec.dirty to be tracked in index
    
    Change-Id: Ief1619110859f6f9ccee3da229f0688b73e2124b
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9602
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 729428aae82e8b878227bb71e65b629783e17ffb
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Feb 15 17:56:51 2015 +0100

    Portability fix: rpc.statd location
    
    rpc.statd is in /usr/sbin on NetBSD
    
    BUG: 1129939
    Change-Id: I6d09e2525cc8242ef3d25d3d5421d57aac711ea4
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9654
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 46a2b9e48160c593a73756d91781298144528e50
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Feb 9 09:26:46 2015 +0100

    ec: Add trusted.ec.dirty xattr
    
    This xattr will be incremented before each data modifying operation and
    decremented after it. This will add the possibility to detect partially
    updated writes and refuse them on reads.
    
    It will also be useful for interacting with index xlator and have a way
    to heal dispersed files from the self-heal daemon.
    
    Change-Id: Ie644a8dd074ae0f254c809c5863bdb030be5486a
    BUG: 1190581
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9607
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a4a760a3cf793857e5fac7d13f5ef7028d30f666
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 20 12:58:20 2015 +0530

    glusterd/snapshot: Fix the ret check in gd_restore_snap_volume
    
    In gd_restore_snap_volume(), irrespective of the ret value
    we were trying to do a list_add_tail to new_volinfo variable.
    There might be cases where this variable might be NULL, and hence
    cause a crash.
    
    Change-Id: I158c5ae655ea27c9a91be3cb9d95a80a3dd05559
    BUG: 1194538
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9719
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit bf22868f82c89e0ee68d394a2257869a36662eaa
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Tue Jan 27 16:53:35 2015 +0530

    libglusterfs: Added support to set  'frame->root->lkowner'
    
    This support can be used by the clients using SYNCOP framework,
    to pass unique owners for various locks taken on a file, so that
    the glusterfs-server can treat them as being locks from different owners.
    
    Change-Id: Ie88014053af40fc7913ad6c1f7730d54cc44ddab
    BUG: 1186713
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/9482
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 30357bcfcd4a7c92e0e59ff58a26d48c8416c564
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jan 6 15:12:59 2015 +0530

    build, glusterd: Add liburcu to build system
    
    This patch adds liburcu related checks to the build system and updates
    the spec file to require 'userspace-rcu'.
    
    liburcu >= 0.7 is required to build GlusterFS, but 0.8 and above is
    preferred. For cases when liburcu 0.7.x is the available version, some
    function definitions (currently just one) from liburcu-0.8.6 have been
    made available in /contrib/userspace-rcu/.
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      a5cd6bd Add userspace-rcu checks to configure.ac
      fe5ced3 Add URCU libs to glusterd libtool flags
      1e43302 Add local definition of cds_list_add_tail_rcu for
              liburcu-0.7
      98da755 Move local definition of cds_list_add_tail_rcu into contrib
      8c44dfd Update spec file to include userspace-rcu0466e33 Rename
      rculist-additional.h to rculist-extra.h
      947c7b3 Add rculist-extra.h to dist
      19f32ad Address review comments 9605/1
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: Ifbb617d0dacce8fa01214f894badb9d8cdcaf56f
    BUG: 1191030
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/9605
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit a671b9a575b89c263af161293e78e49484859ec7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Feb 9 14:20:28 2015 +0530

    cli: Provide CLI to create disperse volume with data, redundancy counts
    
    Change-Id: Iba44be565c895e26b19b5ff85a886873f6b53e5c
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9616
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2b821b114836901bf1e661fc6c4e212298c9768d
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Feb 17 06:55:22 2015 +0530

    gfapi: handle inode_link failures gracefully
    
    Bug: 1193757
    Change-Id: I73bfb91a6a73ad4f06e8828d2d7efd34d9873888
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/9671
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit df9f1cd96854c82338c62897d788319b560e43ad
Author: vmallika <vmallika@redhat.com>
Date:   Thu Feb 19 17:54:03 2015 +0530

    Fix for test usst.t and bug-1167580-set-proper-uid-and-gid-during-nfs-access.t
    
    testcase usst.t and
    bug-1167580-set-proper-uid-and-gid-during-nfs-access.t
    uses below method to generate random string
    cat /dev/urandom | tr -dc 'a-zA-Z' | fold -w 8 | head -n 1
    
    Doing a cat on /dev/urandom can consume more CPU usage.
    
    Change to:
    uuidgen | tr -dc 'a-zA-Z' | head -c 8
    
    Change-Id: I9cb562557ae860026fb5e140ed9b5e297b4428d9
    BUG: 1163543
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9703
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 9d842f965655bf70c643b4541844e83bc4e74190
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Feb 11 17:13:45 2015 +0530

    glusterd: nfs,shd,quotad,snapd daemons refactoring
    
    This patch ports nfs, shd, quotad & snapd with the approach suggested in
    http://www.gluster.org/pipermail/gluster-devel/2014-December/043180.html
    
    Change-Id: I4ea5b38793f87fc85cc9d2cf873727351dedffd2
    BUG: 1191486
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Signed-off-by:  Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9428
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>

commit 571a71f0acd0ec59340b9d0d2519793e33a1dc16
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Feb 18 12:15:55 2015 +0530

    cluster/dht: synchronize with other concurrent healers while healing layout.
    
    Current layout heal code assumes layout setting is idempotent. This
    allowed multiple concurrent healers to set the layout without any
    synchronization. However, this is not the case as different healers
    can come up with different layout for same directory and making layout
    setting non-idempotent. So, we bring in synchronization among healers
    to
       1. Not to overwrite an ondisk well-formed layout.
       2. Refresh the in-memory layout with the ondisk layout if in-memory
       layout needs healing and ondisk layout is well formed.
    
    This patch can synchronize
       1. among multiple healers.
       2. among multiple fix-layouts (which extends layout to consider
       added or removed brick)
       3. (but) not between healers and fix-layouts. So, the problem of
       in-memory stale layouts (not matching with layout ondisk), is not
       _completely_ fixed by this patch.
    
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Change-Id: Ia285f25e8d043bb3175c61468d0d11090acee539
    BUG: 1176008
    Reviewed-on: http://review.gluster.org/9302
    Reviewed-by: N Balachandran <nbalacha@redhat.com>

commit d8f181d3171ed301a9992615083fcf98992577c8
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Thu Feb 19 17:30:35 2015 +0530

    Storage/posix : Adding error checks in path formation
    
    Modified a few log messages added for this fix.
    Also set the op_errno in an error check.
    
    Change-Id: I87caf2f89031aedad1aaee001aef54896dbecd3b
    BUG: 1113960
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/9702
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 633cc5aea181a0e76a16c11d4035542fe3b06f19
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jan 12 17:59:16 2015 +0530

    geo-rep: Add support for non standard AuthorizedKeysFile location
    
    In /etc/ssh/sshd_config, AuthorizedKeysFile can be customized
    using %u and %h variables, %u will be replaced by user name
    and %h will be replaced by home dir name. Default location is
    .ssh/authorized_keys
    
    For example,
    AuthorizedKeysFile .ssh/authorized_keys
    AuthorizedKeysFile %h/.my_secret_dir/authorized_keys
    AuthorizedKeysFile /etc/ssh/keys/%u/authorized_keys
    
    PS: Support only added for %h and %u in sshd_config
    
    BUG: 1181117
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Change-Id: Ic6ba20f9d202762dfdb6d0c73ea42e7f7c64e177
    Reviewed-on: http://review.gluster.org/9436
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 1226083d0ff5fcff21abd16b314effeee49ae770
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jan 15 15:19:50 2015 +0530

    geo-rep: Archive Changelogs and avoid generating empty XSync changelogs
    
    With this patch,
    - Hybrid Crawl will not generate empty Changelogs
    - Archives Changelogs when processed(Hybrid(XSync), History,
      and Changelog Crawl
    - Passive worker cleans up its processing directory
    
    BUG: 1169331
    Change-Id: I1383ffaed261cdf50da91b14260b4d43177657d1
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9453
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 7847db9a6dc560cb0078bdfdb0ac0187e8a79443
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Jul 22 18:49:44 2014 +0530

    posix: Fix unlink failing under specific condition
    
    PROBLEM:
    Files are undeletable when these three conditions are met:
    1. File does not have trusted.pgfid.<gfid> xattr set.
       This won't be set when build-pgfid is off (default).
    2. File has hardlink count > 1.
    3. build-pgfid option is turned on.
    
    FIX:
    Allow unlink on files not having trusted.pgfid.<gfid> xattr.
    
    Change-Id: I58a9d9a1b29a0cb07f4959daabbd6dd04fab2b34
    BUG: 1122028
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/8352
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit ee9b0aab614b56aa8f3c8ed56ced88f769c0ee47
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Feb 12 17:29:28 2015 +0530

    client/server: fix reconfigure for event-threads option
    
    Change-Id: Ica8bca13e4feb941e22651b642b848be165ccc9e
    BUG: 1104462
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9648
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit f099a87fd36b600ccb8268937d3cd7ca84799f77
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Feb 3 05:01:38 2015 +0530

    features/quota : Fix XML output for quota list command
    
    Sample output:
    ---------------
    
    Sample 1)
    ----------
    [root@snapshot-28 glusterfs]# gluster volume quota vol1 list /dir1 /dir4 /dir5 --xml
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volQuota>
        <limit>
          <path>/dir1</path>
          <hard_limit>10.0MB</hard_limit>
          <soft_limit>80%</soft_limit>
          <used_space>0Bytes</used_space>
          <avail_space>10.0MB</avail_space>
          <hl_exceeded>No</hl_exceeded>
          <sl_exceeded>No</sl_exceeded>
        </limit>
        <limit>
          <path>/dir4</path>
          <path>No such file or directory</path>
        </limit>
        <limit>
          <path>/dir5</path>
          <path>No such file or directory</path>
        </limit>
      </volQuota>
    </cliOutput>
    
    Sample 2)
    ---------
    gluster volume quota vol1 list --xml
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volQuota/>
    </cliOutput>
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <volQuota>
        <limit>
          <path>/dir</path>
          <hard_limit>10.0MB</hard_limit>
          <soft_limit>80%</soft_limit>
          <used_space>0Bytes</used_space>
          <avail_space>10.0MB</avail_space>
          <hl_exceeded>No</hl_exceeded>
          <sl_exceeded>No</sl_exceeded>
        </limit>
        <limit>
          <path>/dir1</path>
          <hard_limit>10.0MB</hard_limit>
          <soft_limit>80%</soft_limit>
          <used_space>0Bytes</used_space>
          <avail_space>10.0MB</avail_space>
          <hl_exceeded>No</hl_exceeded>
          <sl_exceeded>No</sl_exceeded>
        </limit>
      </volQuota>
    </cliOutput>
    
    Change-Id: I8a8d83cff88f778e5ee01fbca07d9f94c412317a
    BUG: 1185259
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9481
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit bdb5ca2339edc76b81d1ff996d695eecd849760f
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Feb 18 22:50:34 2015 +0530

    rdma: free rdma priv data if init fails
    
    Change-Id: I57b38c8783666e806836dacf3f74cf9f6876070a
    BUG: 1164079
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9687
    Reviewed-by: mohammed rafi  kc <rkavunga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit f1c4ce0e220a46b7a43c9303c0d137498d421101
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Wed Dec 17 13:58:56 2014 +0530

    Storage/posix : Adding error checks in path formation
    
    Renaming directories can cause the size of the buffer
    required for posix_handle_path to increase between the
    first call, which calculates the size, and the second call
    which forms the path in the buffer allocated based on
    the size calculated in the first call.
    
    The path created in the second call overflows the
    allocated buffer and overwrites the stack causing the
    brick process to crash.
    
    The fix adds a buffer size check to prevent the buffer
    overflow. It also checks and returns an error if the
    posix_handle_path call is unable to form the path instead
    of working on the incomplete path, which is likely to cause
    subsequent calls using the path to fail with ELOOP.
    
    Preventing buffer overflow and handling errors
    BUG: 1113960
    
    Change-Id: If3d3c1952e297ad14f121f05f90a35baf42923aa
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/9289
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 692dd7e83cc8a1c85581dda3f752d5ea3b184f8c
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Nov 24 17:07:02 2014 +0530

    cli: volume status for tcp,rdma type volume display only tcp port
    
    For tcp,rdma type voumes, there will be two ports, one for tcp
    and one for rdma. But volume status command only display tcp port.
    By this change, adding an extra column for rdma port and changing
    the port to tcp port.
    
    Eg:
    
    >gluster volume status pathy
    
    >For tcp,rdma type volume
    
    Status of volume: patchy
    Gluster process                             TCP Port RDMA Port  Online  Pid
    ------------------------------------------------------------------------------
    Brick brickname                             49152    49153      Y       14158
    
    >For rdma type volume
    
    Status of volume: patchy
    Gluster process                             TCP Port RDMA Port  Online  Pid
    ------------------------------------------------------------------------------
    Brick brickname                             0        49153      Y       14158
    
    For tcp type volume
    
    Status of volume: patchy
    Gluster process                             TCP Port RDMA Port  Online  Pid
    ------------------------------------------------------------------------------
    Brick brickname                             49152    0          Y       14158
    
    >gluster volume status patchy detail
    
    Status of volume: xcube2
    ------------------------------------------------------------------------------
    Brick                : Brick brickname
    TCP Port             : 49152
    RDMA Port            : 49153
    Online               : Y
    Pid                  : 14158
    File System          : ext4
    Device               :
    /dev/mapper/luks-2099dd4a-0050-4cae-ad7b-c6a0498c4e88
    Mount Options        : rw,seclabel,relatime,data=ordered
    Inode Size           : 256
    Disk Space Free      : 31.1GB
    Total Disk Space     : 47.9GB
    Inode Count          : 3203072
    Free Inodes          : 2926789
    
    >gluster volume status xcube --xml
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr>(null)</opErrstr>
      <volStatus>
        <volumes>
          <volume>
            <volName>xcube</volName>
            <nodeCount>2</nodeCount>
            <node>
              <hostname>hostname</hostname>
              <path>/home/brick1</path>
              <peerid>2d7bcb95-3d26-4d4f-b3c6-e2ee01b71662</peerid>
              <status>1</status>
              <port>49152</port>
              <ports>
                <tcp>49152</tcp>
                <rdma>N/A</rdma>
              </ports>
              <pid>5657</pid>
            </node>
            <node>
              <hostname>NFS Server</hostname>
              <path>localhost</path>
              <peerid>2d7bcb95-3d26-4d4f-b3c6-e2ee01b71662</peerid>
              <status>1</status>
              <port>2049</port>
              <ports>
                <tcp>2049</tcp>
                <rdma>N/A</rdma>
              </ports>
              <pid>5665</pid>
            </node>
            <tasks/>
          </volume>
        </volumes>
      </volStatus>
    </cliOutput>
    
    Change-Id: I81aab226edbd400d29cd3f510af4f344dd99ba51
    BUG: 1164079
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9191
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 554823cd784b0afb37da68e71e7fc63643b644dc
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Feb 17 15:50:54 2015 +0530

    glusterd: Use correct format specifier for dumping peer hostname
    
    Change-Id: Ifdde4f8256fa463472959078f53d033e5c55207e
    BUG: 1139682
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9665
    Reviewed-by: Anand Nekkunti <anekkunt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit abcb2017b07b0706aef0d9eeb729115ca605ad6d
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Feb 17 20:17:58 2015 +0530

    rdma: pre-register iobuf_pool with rdma devices.
    
    registring buffers with rdma device is a time consuming
    operation. So performing registration in code path will
    decrease the performance.
    Using a pre registered memory will give a bettor performance,
    ie, register iobuf_pool during rdma initialization. For
    dynamically created arena, we can register with all the
    device.
    
    Change-Id: Ic79183e2efd014c43faf5911fdb6d5cfbcee64ca
    BUG: 1187456
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9506
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 7c6da2f7ceea2956197641b6cdb1e2f79cdb063e
Author: Shyam <srangana@redhat.com>
Date:   Wed Nov 12 10:12:13 2014 -0500

    cluster/dht: Fix dht_link to follow files under migration
    
    Currently if a file is under migration, a hardlink to that file
    is lost post migration of the file. This is due to the fact that
    the hard link is created against the cached subvol of the source
    and as the source is under migration, it shifts to a linkto file
    post migration. Thus losing the hardlink.
    
    This change follows the stat information that triggers a phase1/2
    detection for a file under migration, to create the link on the new
    subvol that the source file is migrating to. Thereby preserving the
    hard link post migration.
    
    NOTES:
    The test case added create a ~1GB file, so that we can catch the file
    during migration, smaller files may not capture this state and the
    test may fail.
    Even if migration of the file fails, we would only be left with stale
    linkto files on the subvol that the source was migrating to, which is
    not a problem.
    This change would create a double linkto, i.e new target hashed subvol
    would point to old source cached subol, which would point to the real
    cached subvol. This double redirection although not handled directly in
    DHT, works as lookup searches everywhere on hitting linkto files. The
    downside is that it never heals the new target hashed subvol linkto
    file, which is another bug to be resolved (does not cause functional
    impact).
    
    Change-Id: I871e6885b15e65e05bfe70a0b0180605493cb534
    BUG: 1161311
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9105
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: susant palai <spalai@redhat.com>
    Reviewed-by: venkatesh somyajulu <vsomyaju@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit de6f4ce0dd894c78632bf7b2ebc00d8044fba688
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Fri Feb 13 17:10:37 2015 +0530

    build: .cmd_log_history should be renamed to cmd_history.log post upgrade.
    
    While upgrading from glusterfs-version < 3.6 to glusterfs-3.6,
    .cmd_log_history hidden file still present in /var/log/glusterfs/ directory.
    
    With this fix it will not have .cmd_log_history hidden file and it will
    rename it to cmd_history.log file.
    
    Change-Id: I2c1658056ddd75ce923f100961205a3b78394466
    BUG: 1165996
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9652
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit eebc3c06693c324be261c994f8e74886b7715770
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Feb 10 17:11:21 2015 +0530

    rdma: reduce log level from E to W
    
    glusterd process, when try to initialize default vol file, will
    always through an error if there is no rdma device. Changing the
    log levels and log messages to more appropriately.
    
    Change-Id: I75b919581c6738446dd2d5bddb7b7658a91efcf4
    BUG: 1188232
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9559
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 55ce0ef667de7995c4197314153877719a7de539
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Dec 23 11:31:37 2014 +0530

    rdma:read multiple wr from cq and ack them in one call
    
    we are reading one work completion request at a time
    from cq, though we can read multiple work completion
    requests from cq. Also we can acknowledge them in
    one call itself. Both will give a better performance
    because of less mutual exclusion locks are being performed.
    
    Change-Id: Ib5664cab25c87db7f575d482eee4dcd2b5005c04
    BUG: 1164079
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9329
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit e04039092d28dde70a9a394010cd04cf0a12726a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Feb 10 16:43:50 2015 +0530

    feature/gfid-access: Send a named lookup before trying to create a file.
    
    Normally a named-lookup is done by the kernel on an entry before it
    issues a dentry creation fop like create/mknod etc. This will enable
    cluster translators like dht to maintain internal consistency like
    deleting a linkto file if no corresponding datafile is present etc.
    While handling file creation on auxiliary gfid mounts, we issue dentry
    creation fop without issuing a lookup. If there are stale-linkto files,
    creation would fail with EEXIST, however access would fail since there
    is no datafile. A named lookup would cleanup the linkto file allowing
    create to succeed.
    
    Change-Id: I2932107296adac710dd179df7d0946b8697a497a
    BUG: 1191413
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9634
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 8618abaaf07a96c0384db9bd1e7dbbe663f4f24c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jan 6 20:26:39 2015 +0530

    glusterd/geo-rep: Allow replace/remove brick if geo-rep is stopped.
    
    Replace brick:
    If geo-replication was configured on a volume, replace brick
    used to fail. This patch allows replace brick to go through
    if all geo-rep sessions corresponding to that volume is stopped.
    
    Remove brick:
    There was no check for geo-replication for remove brick. Enforce
    'remove brick commit' to fail if geo-rep session corresponding
    to volume is running. Allow 'remove brick commit' only if all of
    the geo-rep sessions corresponding to that volume is stopped.
    
    Code is re-organized for better readability.
    
    Change-Id: I02282c2764d8b81e319489c977847e6e437511a4
    BUG: 1179638
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9402
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: ajeet jha <ajha@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 04c4ec96b88ee6392812a511de32b48bbe63a421
Author: Dan Lambright <dlambrig@redhat.com>
Date:   Tue Dec 16 10:28:57 2014 -0500

    cluster/dht: Modify dht-rebalance.c to use trusted.distribute.migrate-data
    rather than distribute.migrate-data and work with CLI.
    
    The change makes this work both when it is internally driven and from the
    shell. The problem is further described in bugzilla # 1147107.
    
    Change-Id: I4fe04cae661dca25432530ddf5ac6ff2c957d6b3
    BUG: 1147107
    Signed-off-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-on: http://review.gluster.org/9284
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 47f6f41f1204d0a1fd3cb699919c757d3238fdf3
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Feb 12 18:11:46 2015 +0100

    Temporarily remove nfs.t to avoid regression failures
    
    Test basic/ec/nfs.t is causing many regression failures due to
    a problem related with NFS.
    
    While the NFS problem is solved, this patch removes the test
    to avoid more regression failures.
    
    Change-Id: I29884c5e06732e427130d1bc82f1b83553916f95
    BUG: 1192114
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9649
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit b8ed8da853ac60a19a2099f0c1de21f50fe34fe4
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Dec 22 15:16:43 2014 +0530

    rdma: post multiple work request in a single call.
    
    ibv_post-send will allow to send multiple work request
    in a single call posting as linked list.
    
    So if the payload count > 1, we can perform the data
    operation in a single call to ibv_post_send.
    
    Change-Id: Ib2e485cbbe6887919109e73e17d4fab595d5e65e
    BUG: 1164079
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9327
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 60361d84a03048b0882935fb92c19ac3b68f9325
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Dec 22 11:04:50 2014 +0530

    rdma : agregate a vectored read as one
    
    For a vectored read with payload count>1 will make two read
    requests and to hold that a single contiguous memory is allocated.
    So after completing the read request, instead of sending as vector
    we will aggregate all the reads one.
    
    Change-Id: I15e7d7bddc1a62d5097a39392575f47cfff3d3a8
    BUG: 1164079
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9321
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit fe73f12f6ef2deb402b622747cad5e82b11e57af
Author: Shyam <srangana@redhat.com>
Date:   Sun Feb 8 20:08:46 2015 -0500

    epoll: Initialize server/client xlator event-threads correctly
    
    In the patch http://review.gluster.org/#/c/9488/ the default
    configuration for server and client protocol xlators, had
    event-threads set to 2, but the default conf was not updated
    with these values, hence the default threads remained at 1.
    
    This patch corrects the same by first updating the thread count
    from the default configuration before updating it with the
    latest.
    
    Change-Id: I3ce54053a59ca796b004fa5462e43ca19a5f2915
    BUG: 1104462
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9604
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1353aeadcd080c356a4c404dbfb10ff3f23ab4cf
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Mon Feb 9 15:41:37 2015 +0530

    api: coverity fix.
    
    CID 1214617: dereference NULL return value.
    
    Change-Id: I57447c3b1663edadfa966892c53bc2a16d4a166f
    BUG: 789278
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/9610
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit efd93f0b2b42f8a8b151bf694fdd340fbcb22ec0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Jan 31 16:07:03 2015 +0530

    cluster/afr: Enable auto-quorum for replicate with odd number of bricks
    
    Change-Id: I908934f1f22cf7d2d0ceccc0dedf28a69861997f
    BUG: 1187885
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9517
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit f18a3f30bbeaf3bb067b913082830d7f874555ca
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Feb 5 15:41:35 2015 +0530

    protocol/client: sequence CHILD_UP, CHILD_DOWN etc notifications
    
    ... from all bricks in the volume
    
    This patch is important in the context of MT epoll. With MT epoll,
    notification events from client xlators could reach cluster xlators like
    afr, dht, ec, stripe etc. in different orders.
    
    For e.g, In a distributed replicate volume of 2 bricks, namely Brick1
    and Brick2, the following network events are observed by a mount
    process.
    
    - connection to Brick1 is broken.
    - connection to Brick1 has been restored.
    
    - connection to Brick2 is broken.
    - connection to Brick2 has been restored.
    
    Without establishing a total ordering of events, we can't guarantee that
    cluster xlators like afr, dht perceive them in the same order.  While we
    would expect afr (say) to perceive it as only one of Brick1 and Brick2
    going down at any given time, it is possible for the notification of
    Brick2 going offline to race with the notification of Brick1 coming back
    online.
    
    Change-Id: I78f5a52bfb05593335d0e9ad53ebfff98995593d
    BUG: 1104462
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9591
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a7f5893c9243c8c563db215352fa7e47f6968e8b
Author: Shyam <srangana@redhat.com>
Date:   Mon Jan 26 14:20:31 2015 -0500

    epoll: Adding the ability to configure epoll threads
    
    Add the ability to configure the number of event threads
    for various gluster services.
    
    Currently with the multi thread epoll patch, it is possible
    to have more than one thread waiting on socket activity and
    processing the same. This thread count is currently static,
    which this commit makes dynamic.
    
    The current services which use IO path, i.e brick processes,
    any client process (nfs, FUSE, gfapi, heal,
    rebalance, etc.a), gain 2 set parameters to control the number
    of threads that are processing events. These settings are,
      - client.event-threads <n>
      - server.event-threads <n>
    
    The client setting affects the client graph consumers, and the
    server setting affects the brick processes. These are processed
    and inited/reconfigured using the client/server protocol xlators.
    
    Other services (say glusterd) would need to extend similar
    configuration settings to take advantage of multi threaded event
    processing.
    
    At present glusterd is not enabled with this commit, as it does not
    stand to gain from this multi-threading (as I understand it).
    
    Change-Id: Id8422fc57a9f95a135158eb6477ccf9d3c9ea4d9
    BUG: 1104462
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9488
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c61074400a45e69c6edbf82b8ed02568726d37ae
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Thu Jun 19 15:41:22 2014 +0530

    epoll: edge triggered and multi-threaded epoll
    
    - edge triggered (oneshot) polling with epoll
    - pick one event to avoid multiple events getting picked up by same
      thread
      and so get better distribution of events against multiple threads
    - wire support for multiple poll threads to epoll_wait in parallel
    - evdata to store absolute index and not hint for epoll
    - store index and gen of slot instead of fd and index hint
    - perform fd close asynchronously inside event.c for multithread safety
    - poll is still single threaded
    
    Change-Id: I536851dda0ab224c5d5a1b130a571397c9cace8f
    BUG: 1104462
    Signed-off-by: Anand Avati <avati@redhat.com>
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/3842
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5e25569ed0717aa8636ad708430a823d39f9aa60
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Feb 5 21:26:04 2015 +0530

    cluster/afr: Re-introduce heal-timeout option
    
    Change-Id: I87484c810006a92ed7489284b6d74e9b0aecae80
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9598
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2efb36047aa11838b2cde93a3e95741e7ba40bae
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Feb 5 21:23:37 2015 +0530

    syncop: Provide syncop_ftw and syncop_dir_scan utils
    
    ftw provides file tree walk.
    dir_scan does just a readdir not readdirp.
    
    Also changed Afr's self-heal-daemon's crawling functions to use this.
    These utils will be used by ec in future to do proactive/full healing.
    
    Change-Id: I05715ddb789592c1b79a71e98f1e8cc29aac5c26
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9485
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f75bb4a9ca14b50c7f828ee3fe4ba73dd78f094c
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Fri Jan 30 11:47:11 2015 +0100

    ec: Special handling of anonymous fd
    
    Anonymous file descriptors need to be handled specially because
    they can be used in some non standard ways (i.e. an anonymous fd
    can be used without having been opened).
    
    This caused NFS to fail on some operations because ec always
    expected to have a previous successful opendir call (from patch
    http://review.gluster.org/9098/).
    
    This patch treats all anonymous fd as opened on all subvolumes.
    
    Change-Id: I09dbbce2ffc1ae3a5bcbb328bed55b84f4f0b9f8
    BUG: 1187474
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9513
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b3b4f9d81a5c70b04fdb71b9eb7a619cfede7cf8
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Feb 4 15:39:31 2015 +0530

    rpc: fix ref leak in ping timer
    
    Change-Id: I4ddc371d01ec763706a168a215410015ee2a3787
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9578
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit e44d4e135747b04a5e2b7cfac21f9a3343e071db
Author: GauravKumarGarg <ggarg@redhat.com>
Date:   Wed Nov 12 17:41:33 2014 +0530

    DHT: cluster.min-free-disk option should validate correctly
    
    PROBLEM:
    Previously gluster accepting input value as a percentage which is out of range
    [0-100] and accepting input value as a size (unit is byte) which is fractional
    for option cluster.min-free-disk.
    
    FIX:
    Now with this change it will refer to correct validation function
    and it will accept value that is in range [0-100] for input value as a
    percentage and unsigned integer value for input as a size (unit in byte)
    for option cluster.min-free-disk.
    
    Change-Id: Iee1962a100542e146276cfc8a4068abddee2bf2d
    BUG: 1163108
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9104
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0b198a113e254f6a2702a87a45e823cea964ab11
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 3 21:34:45 2015 +0530

    cluster/afr: Fix parent read subvol selection policy in lookup
    
    When lookup has succeeded on multiple subvols of AFR (including
    the read child of the parent dir) and all of them are "readable",
    ideally the call must be unwound with postparent from the parent's
    read child. But that is not the case, due to a bug introduced in
    the commit c78998c39f0857ea7aacba360632c148afc54a55. This patch
    fixes the issue.
    
    Change-Id: I83b0c26494a5d0bdbc30fcbe974fbdb6f7e9c84a
    BUG: 1179169
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9569
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 552958c95ff4c4fea7c370a87e937e4a88973da1
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Feb 4 14:13:05 2015 +0530

    tests : spurious failure fix in heald.t
    
    Problem : heald.t uses EXPECT to check whether shd process is up or not, but as
    shd is spawned with NO_WAIT end of volume start transaction doesn't gurantee
    that the process will be up by that time.
    
    Solution : Use EXPECT_WITHIN instead of EXPECT
    
    Change-Id: Ic81725aa7e7cde9c0c873837fcc4a73d8318dfa0
    BUG: 1163543
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9575
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 3a332a834aac3f3a931b31dcaabe34901b309d6c
Author: Anand <anekkunt@redhat.com>
Date:   Fri Jan 9 14:24:08 2015 +0530

    libglusterfs : Corrected  functions calls.
    
    Problem  : There was mismatch between arguments and parameters in some functions
    (ex:glusterfs_uuid_buf_get,glusterfs_lkowner_buf_get). It could lead to stack overflow issues .
    
    Fix      : Arguments are removed during calling these function.
    
    Change-Id: Icb41bd4119502d192d9cc7242d385ebe62cdb51a
    BUG: 1180424
    Signed-off-by: Anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/9427
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ea6a31cd7c430768b8dfd3b4944fffde0be3a740
Author: arao <arao@redhat.com>
Date:   Thu Jan 29 16:37:35 2015 +0530

    geo-rep: Fixing the typo errors
    
    Change-Id: Iacc67e4ba9ac45e0858f3befe84ffb8fccf7e1c3
    BUG: 1075417
    Signed-off-by: arao <arao@redhat.com>
    Reviewed-on: http://review.gluster.org/9502
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 7842f86a5c48389b6c34009b08799adca19b7311
Author: Nandaja Varma <nvarma@redhat.com>
Date:   Fri Jan 30 14:17:23 2015 +0530

    tests: Removing rpmbuild/mock check from run-tests.sh
    
    Checks for rpmbuild/mock is removed from run-tests since this check
    is not in the glusterfs-regression-tests package.
    Alongside, the dependency mock is also removed from glusterfs.spec.in
    as mock is only used by basic/rpm.t.
    
    Change-Id: I5a9036141d0900b3a0bedd95b8c58fb0cdc13ca1
    BUG: 1178008
    Signed-off-by: Nandaja Varma <nvarma@redhat.com>
    Reviewed-on: http://review.gluster.org/9512
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b05b77923903deb26e5b1bae52da46ff6c1c878e
Author: Sakshi Bansal <sabansal@redhat.com>
Date:   Fri Jan 30 11:26:07 2015 +0530

    tests: fixing typo errors
    
    Change-Id: I8caab03531d74c64dcfa05c35a7daeee646cd2fa
    BUG: 1075417
    Signed-off-by: Sakshi Bansal <sabansal@redhat.com>
    Reviewed-on: http://review.gluster.org/9507
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/9548
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 95f1787639046de2a4e4b2d38dd66011d4df08a2
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Feb 2 12:24:11 2015 -0800

    Revert "tests: fixing typo errors"
    
    This reverts commit 22cb0af7c4074a10450f549b68c56f6da02cbf4d
    
    Change-Id: If260db796a65a92468e10a2f2157680a653c40e6
    Reviewed-on: http://review.gluster.org/9546
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit da1ff66255017501f54c50b3c40eeea11b5fc38f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Feb 1 15:03:46 2015 +0530

    cluster/ec: Wait for all bricks to notify before notifying parent
    
    This is to prevent spurious heals that can result in self-heal.
    
    Change-Id: I0b27c1c1fc7a58e2683cb1ca135117a85efcc6c9
    BUG: 1179180
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9523
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 3622146ac06918069a5994ac0dfa02aa98de4d8f
Author: Saravanakumar Arumugam <sarumuga@redhat.com>
Date:   Fri Jan 30 12:57:21 2015 +0530

    tests/snapshot: Avoid errors on make dist.
    
    Problem:
    "make dist" gives the following error:
    tar: bug-1140162-file-snapshot-and-features-encryption-option-validation.t:
        file name is too long (max 99); not dumped
    
    Here, .t file is not getting included on the "make dist" tarball as file
    name is too long for the "tar" command. Result is, upon distributing the tests
    through the tarball, this particular test will not get run on the target system.
    
    Solution:
    Rename the file to a shorter one(less than 99) to avoid this error.
    
    Change-Id: I29c8da649b8b5e00b3b4dada02c8b69b2d7f0e2c
    BUG: 1140162
    Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/9511
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 52765ad94f233e4b4e57515e49f5b7c9e7c08b43
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jan 7 21:56:58 2015 +0530

    geo-rep: Adding Slave user field to georep status
    
    New column introduced in Status output, "SLAVE USER",
    Slave user is not "root" in non root Geo-replication setup.
    
    Added additional tag in XML output <slave_user>
    
    BUG: 1180459
    Change-Id: Ia48a5a8eb892ce883b9ec114be7bb2d46eff8535
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9409
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 63f17d66258bca46532fe649bbb76a5e5948f22b
Author: Anand <anekkunt@redhat.com>
Date:   Thu Jan 29 14:01:12 2015 +0530

    glusterd : Corrected  server.statedump-path description.
    
    Problem : gluster volume set help for server.statedump-path has wrong
              description.
    
    Fix      : Server.statedump-path description corrected .
    
    Change-Id: I10f5494a01c6dbbb2204665666f3c3c1ad4599e8
    BUG: 1186993
    Signed-off-by: Anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/9500
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit f9e6f25fb5576c0b0cf9377d49c9896fa8278c00
Author: Dennis Schafroth <dennis@schafroth.dk>
Date:   Sat Jan 31 19:23:16 2015 +0100

    Compare key with GF_XATTR_LOCKINFO_KEY with length of GF_XATTR_LOCKINFO_KEY instead of length of 0
    
    BUG: 1187952
    Change-Id: I0a97c553e85a0f9260ab01d4b48c64831bf67c18
    Signed-off-by: Dennis Schafroth <dennis@schafroth.com>
    Reviewed-on: http://review.gluster.org/9518
    Reviewed-by: Joe Julian <joe@julianfamily.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 70b72316302b017436b44a58aa025dabd3558ae7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Feb 1 12:40:21 2015 +0000

    doc: self-heal daemon
    
    Documentation describing how the self-heal daemon works for replicate
    volumes.
    
    Change-Id: I89bdbbeee7f5106f0ee71870e11aa9c96f90753d
    BUG: 1118309
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9537
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit c78998c39f0857ea7aacba360632c148afc54a55
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jan 22 13:53:47 2015 +0530

    cluster/afr: When parent and entry read subvols are different, set entry->inode to NULL
    
    That way a lookup would be forced on the entry, and its attributes will
    always be selected from its read subvol.
    
    Change-Id: Iaba25e2cd5f83e983fc8b1a1f48da3850808e6b8
    BUG: 1179169
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9477
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e9276230e13e2c67b9944c604e8d4485ee3e3a63
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Feb 1 03:48:05 2015 +0100

    Emulate Linux truncate for G and GB units
    
    Recent modification in sparse-file-self-heal.t added a
    truncate -s 1G, and that unit was not emulated correctly
    for non Linux systems. As a result, all regression tests
    hang. Fill the gap to restore regression.
    
    BUG: 1129939
    Change-Id: Ib45376b4b2e74d1868f3ebdd5564b2186b4318fa
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9519
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c46070189e4d9a71f7884dad06ee48b935c591e9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jan 19 10:20:28 2015 +0100

    build: do not include automake/autoconf cache in the 'make dist' tarball
    
    Remove the caches from the 'dist-hook' target that 'make dist' executes.
    
    Also, there is no need to run ./configure inside contrib/argp-standalone
    if it will not get used. configure.ac has been modified to only
    configure the contrib/argp-standalone sources for distributions that do
    not have the <argp.h> header available.
    
    BUG: 1183538
    Change-Id: Iedd67139ec83f0076e24ed0d575f9053ac1a94ec
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9463
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 64132200590a9310ea221524e13db8a09bd89313
Author: Anuradha <atalur@redhat.com>
Date:   Fri Jan 23 10:51:11 2015 +0530

    afr : Change in heal info split-brain command
    
    Implementation of heal info split-brain command with
    glfs-heal.
    
    Change-Id: I233eb790de6eb5468a4cbb12a1cef0f97db2a1d2
    BUG: 1183019
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9459
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0f84f8e8048367737a2dd6ddf0c57403e757441d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jan 23 11:12:54 2015 +0530

    afr: Don't write to sparse regions of sink.
    
    Problem:
    When data-self-heal-algorithm is set to 'full', shd just reads from
    source and writes to sink. If source file happened to be sparse (VM
    workloads), we end up actually writing 0s to the corresponding regions
    of the sink causing it to lose its sparseness.
    
    Fix:
    If the source file is sparse, and the data read from source and sink are
    both zeros for that range, skip writing that range to the sink.
    
    Change-Id: I787b06a553803247f43a40c00139cb483a22f9ca
    BUG: 1166020
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9480
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e8eff5cf350b24ad628de8092d7927eab1e23c32
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Wed Jul 9 00:18:13 2014 +0530

    doc: Fix typos in stripe xlator src, no code changes present
    
    Change-Id: Icec4e6b0fe7845667b59e13e261734a5f69eba7e
    BUG: 1075417
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8264
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4493bfd8421116b5f45638b2f839874921f73fb3
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jan 21 08:25:23 2015 +0000

    glusterd/snapshot: Fail snap create even if one brick is down.
    
    In a n-way replication, where n>=3  fail snapshot,
    even if one brick is down.
    
    Also check for glusterd quorum, irrespective of the force option
    
    Modified testcase tests/bugs/snapshot/bug-1090042.t because
    it tested the successful creation of snapshot with force
    command.
    
    Change-Id: I72666f8f1484bd1766b9d6799c20766e4547f6c5
    BUG: 1184344
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9470
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 32c3d4e7a611f64a1f4eebe5711bcb112b94151f
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Jan 13 20:25:34 2015 +0530

    doc: Add doc for rdma transport.
    
    Also corrected few things related to rdma documentation
    in other docs.
    
    Change-Id: If35d7e2e884974ff3719f6a9f111f7b45ac8c0ec
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9443
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Ben England <bengland@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit abc043312db6307aabf95f593bfa405ac28a2c8a
Author: hchiramm <hchiramm@redhat.com>
Date:   Thu Sep 25 13:23:46 2014 +0530

    doc: update glossary documentation
    
    Change-Id: I0da7c3aaaeb43f633b4d6355ef83ac2d21e24d68
    Signed-off-by: Divya    <dmuntima@redhat.com>
    Signed-off-by: Pavithra <psriniva@redhat.com>
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8847
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit a48b18d6f661f863371e625084a88a01aaf989f0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jan 8 15:39:40 2015 +0530

    cluster/ec: Handle CHILD UP/DOWN in all cases
    
    Problem:
    When all the bricks are down at the time of mounting the volume, then mount
    command hangs.
    
    Fix:
    1. Ignore all CHILD_CONNECTING events comming from subvolumes.
    2. On timer expiration (without enough up or down childs) send
       CHILD_DOWN.
    3. Once enough up or down subvolumes are detected, send the appropriate event.
       When rest of the subvols go up/down without changing the overall
       ec-up/ec-down send CHILD_MODIFIED to parent subvols.
    
    Change-Id: Ie0194dbadef2dce36ab5eb7beece84a6bf3c631c
    BUG: 1179180
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9396
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b17122ffc75c65bda2cf3b3d99832bbf2718e8d3
Author: Xavier Hernandez <xhernandez@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@datalab.es>
    Reviewed-on: http://review.gluster.org/9420
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 88136b53f59e3b81aacc28df18bda575da35b02d
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Jan 11 23:13:08 2015 +0530

    libglusterfs: Avoid initializing per process globals more than once.
    
    gfapi consumers can invoke glusters_globals_init() multiple times
    through glfs_new(). This will result in re-initialization of already
    inited variables and non deterministic behavior. To avoid this, a
    new function gf_globals_init_once() has been added. The invocation
    of this function is guarded through pthread_once(), thereby ensuring
    single initialization of per process globals.
    
    Change-Id: I0ecde02ee49e0c7379c2eb0f1c879d89774ec82f
    BUG: 1184366
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9430
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c8a6904396142b832ec31c37f43f44b139d24e1f
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jan 20 17:57:22 2015 +0530

    uss: disable memory accounting for the snapshot daemon
    
    * Bring in option to disable memory accounting for a glusterfs process
      This reverses the changes done by the commit
      7fba3a88f1ced610eca0c23516a1e720d75160cd.
    
    * Change the key from "memory-accounting" to "no-memory-accounting", as by
      default all the glusterfs process enable memory accounting now. So to
      disable memory accounting for some process, "no-mem-accounting" argument has
      to be passed.
    
    Change-Id: I39c7cefb0fe764ea3e48f4e73e1305b084c5f497
    BUG: 1184366
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9469
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2f640b3f3ce21c6790c661f53ff39474192b5a21
Author: Shyam <srangana@redhat.com>
Date:   Tue Jan 27 10:42:54 2015 -0500

    test: Check till probe timeout, for conf change sync across glusterd
    
    Currently the test case changed here, checks for the peer count to
    be 1 until probe timeout and then checks for the changed
    configuration, if it has been synced.
    
    The peer count is not a gurantee that the configuration is also
    in sync, hence changing this test case to check for the conf
    update till probe timeout, by which time it should be in sync
    (or at least that is our tolerance), and the test case deemed
    as passing.
    
    Change-Id: I4b1560979cfde3bd3bd691852d7d3a63e253bcf2
    BUG: 1181203
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9498
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit ee3d92e83c64b654b42c9ecc5b0cc3ad80a1d51b
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Jan 27 17:42:53 2015 +0530

    feature/changelog: Fix changelog and history scan failure.
    
    Fixes bad file descriptor issue while cleaning up
    scratch directory during gf_changelog_register.
    
    Change-Id: Ia6aa8d55dcc2209144b48b6583681a155d919c42
    BUG: 1162057
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9495
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 6b22f5ba834e7ea382bee88f359a10faac407a77
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Jan 14 15:20:09 2015 +0530

    Remove inactive maintainers.
    
    Change-Id: I2b3916134c060d1beb35c36423fa28e6de54793c
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/9445
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e131fccf926bc2f19fb8c9f2980f60d5fec67994
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Jan 23 11:24:07 2015 +0100

    tests/features/ssl-authz.t: Fix spurious failures
    
    Fix two spurious failures in tests/features/ssl-authz.t
    1) Wait for bricks to come online after starting a volume, so that
       the mount is usable without "socket not connected" error
    2) For a mount that must fail, we may get the situation where there
       is no mount at all, which means creating a file will write to the
       mount point instead of failing. To cover that case, write the
       file and check it is absent from the brick.
    
    BUG: 1129939
    Change-Id: If95e1d65ab23d11123f778c20f8110a3177b0e7f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9483
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 0b9a6a63b50e0c4947233aee33fc86f603f77dd1
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Nov 5 22:37:48 2014 -0500

    socket: fix segfaults when TLS management connections fail
    
    Change-Id: I1fd085b04ad1ee68c982d3736b322c19dd12e071
    BUG: 1160900
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/9059
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d8d0db420598e1f4cebc8f973f1eff36e93dd83d
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Oct 13 04:57:54 2014 +0530

    glusterd/quota : remove quota-deem-statfs and quota-timeout values when quota is disabled.
    
    problem : If quota is disabled then all the options associated with
    quota is removed, except quota-deem-statfs and quota-timeout.
    When gluster volume info is issued then the user can see that quota
    is disabled whereas quota-deem-statfs and quota-timeout values still
    exist.
    
    Solution : remove quota-deem-statfs and quota-timeout option when quota is
    disabled
    
    NOTE : If features.quota-deem-statfs is turned on, it takes quota limits
    into consideration while estimating fs size.
    
    Change-Id: I8cca6a8f47d2355799228643aedc8fc03896cfad
    BUG: 1151933
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8924
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e39d80f9921c6fbfe084bdb66f95532794fc6aca
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jan 27 07:57:27 2015 +0000

    glusterd/snapshot: Ignore failure to copy geo-rep files.
    
    In case a new node is added to the peer, after a snapshot was
    taken, the geo-rep files are not synced to that node. This
    leads to the failure of snapshot restore. Hence, ignoring the
    missing geo-rep files in the new node, and proceeding with
    snapshot restore. Once the restore is successful, the missing
    geo-rep files can be generated with "gluster volume geo-rep
    <master-vol> <slave-vol> create push-pem force"
    
    Change-Id: I1c364f8aefdd6c99b0b861b6d0cb33709ec39da2
    BUG: 1181418
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9489
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit bf227251eadcc35a102fc9db0c39e36b7336954d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jan 13 09:31:18 2015 +0000

    glusterd/snap: Fix restore cleanup
    
    If restore commit is successful on the originator and
    a few nodes, but fails on some other node, restore cleanup
    should restate the volume and the snapshot in question
    as it was before the command was run.
    
    Change-Id: I7bb0becc7f052f55bc818018bc84770944e76c80
    BUG: 1181418
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9441
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit becdb76238c45ebe3edc967376f4aee87c0cb6e3
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Sun Dec 21 22:01:03 2014 +0530

    features/marker: do not call inode_path on the inode not yet linked
    
    * in readdirp callbak marker is calling inode_path on the inodes that
      are not yet linked to the inode table.
    
    Change-Id: I7f5db29c6a7e778272044f60f8e73c60574df3a9
    BUG: 1176393
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9320
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 6c10f6db7c53e96881b29ca70dfc08b1ffb231b3
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jan 20 14:58:34 2015 +0530

    cluster/dht: In MKDIR(), aggregate iatts from non-hashed subvols too
    
    PROBLEM:
    
    Gathering iatts from ONLY the hashed subvol during MKDIR and unwinding
    them can cause md-cache to cache and serve these values for a while to
    the application.
    And then, at a later point of time, when a LOOKUP on either the dir or
    its parent gathers attributes from all subvolumes of dht and things are
    evened out as part of DHT_UPDATE_TIME, the application could be getting
    a different set of [cm]times (i.e., one of the non-hashed subvolumes'
    times could be selected by virtue of having the highest values),
    causing it to think the directory underwent modification even when it
    might not have.
    
    The effect of this bug becomes apparent in programs like tar, which rely
    on the ctime of the files before and after archiving a file to
    ascertain that the file remained unchanged during this time.
    
    FIX:
    
    Aggregate iatts from ALL sub-volumes of DHT during MKDIR.
    
    Change-Id: I04c4ca3e3b9552772e2b089be680f8afeb72089e
    BUG: 1179169
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9465
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 304cfeea0106ee7a9e1786637bab403f72c96155
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jan 22 12:57:10 2015 +0530

    performance/md-cache: Initialise local->loc before winding nameless lookup
    
    That way, in the cbk, the latest values are updated in the cache.
    
    Change-Id: Ia149e352e4763e8f5b910a3f4cb64d2dda4534b1
    BUG: 1179169
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9476
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit f3ad194918dbbf00dcc9aebb226728294161ed7a
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Jan 16 14:32:09 2015 +0530

    geo-rep: Handle copying of common_secret.pem.pub to slave correctly.
    
    Current Behaviour:
        1. Geo-replication gsec_create creates common_secret.pem.pub file
           containing public keys of the all the nodes of master cluster
           in the location /var/lib/glusterd/
        2. Geo-replication create push-pem copies the common_secret.pem.pub
           to the same location on all the slave nodes with same name.
    
    Problem:
        Wrong public keys might get copied on to slave nodes in multiple
        geo-replication sessions simultaneosly.
    
         E.g.
          A geo-rep session is established between Node1(vol1:Master) to
          Node2 (vol2:Slave). And one more geo-rep session where
          Node2 (vol3) becomes master to Node3 (vol4) as below.
    
          Session1: Node1 (vol1) ---> Node2 (vol2)
          Session2: Node2 (vol3) ---> Node3 (vol4)
    
          If steps followed to create both geo-replication session is as
          follows, wrong public keys are copied on to Node3 from Node2.
    
          1. gsec_create is done on Node1 (vol1) -Session1
          2. gsec_create is done on Node2 (vol3) -Session2
          3. create push-pem is done Node1 - Session1.
              -This overwrites common_secret.pem.pub in Node2
               created by gsec_create in second step.
          4. create push-pem on Node2 (vol3) copies overwrited
             common_secret.pem.pub keys to Node3. -Session2
    
    Consequence:
          Session2 fails to start with Permission denied because of wrong
          public keys
    
    Solution:
          On geo-rep create push-pem, don't copy common_secret.pem.pub
          file with same name on to all slave nodes. Prefix master and
          slave volume names to the filename.
    
    NOTE: This brings change in manual steps to be followed to setup
          non-root geo-replication (mountbroker). To copy ssh public
          keys, extra two arguments needs to be followed.
    
          set_geo_rep_pem_keys.sh <mountbroker_user> <master vol name> \
          <slave vol name>
    
          Path to set_geo_rep_pem_keys.sh:
          Source Installation:
                  /usr/local/libexec/glusterfs/set_geo_rep_pem_keys.sh
          Rpm Installatino:
                  /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh
    
    Change-Id: If38cd4e6f58d674d5fe2d93da15803c73b660c33
    BUG: 1183229
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9460
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 27f2b8839e4d3ebe9ccbde071864b3e8016a3c4d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Jan 21 06:24:47 2015 +0100

    glusterd: Fix spurious volume delete failure
    
    If volume uses quota, volume delete operation should unmount the
    auxiliary quota mount usin glusterd_remove_auxiliary_mount(). This
    may fail with EBADF is the mount is already gone. In that situation,
    ignore the error so that volume delete succeeds.
    
    This fixes a spurious failure on NetBSD in tests/basic/quota.t 74-75
    
    BUG: 1129939
    Change-Id: I69325f71fc2c8af254db46f696c8669a4e6bd7e4
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9468
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f74ff011fce5959884a4f47f0c87ae8795d64a24
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Dec 31 14:26:37 2014 +0530

    glusterd: Fix strtok_r parsing.
    
    Found a bug where a replica 2 volume creation prompts
    saying the bricks are in the same hosts even when they
    are in different hosts.
    
    Change-Id: Ie55addae55c55e32ad2b5339530ab71f0e3711ab
    BUG: 1091935
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9373
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 217253b692610c4f6ce5d8426832c1d69844966c
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Jan 7 09:53:52 2015 +0530

    cli: volume-info <VOLNAME>, peer-status to report failure before exit
    
    BUG: 1181203
    Change-Id: I84260d66135b1980f93b258d5de58c9e6b7a8402
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9399
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 30ad195d49b971a5389d37c9d9a3583186f3d54a
Author: GauravKumarGarg <ggarg@redhat.com>
Date:   Wed Dec 24 16:39:03 2014 +0530

    glusterd: quorum validatation in glusterd syncop framework
    
    Previously glusterd was not checking quorum validation in syncop framework.
    So when there is loss in quorum then few operation (for eg. add-brick,
    remove-brick, volume set) which is based on syncop framework passed
    successfully with out doing quorum validation check.
    
    With this change it will do quorum validation in syncop framework and it will
    block all operation (except volume set <quorum options> and "volume reset all"
    commands) when there is loss in quorum.
    
    Change-Id: I4c2ef16728d55c98a228bb86795023d9c1f4e9fb
    BUG: 1177132
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9349
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f6a2f152aa9c8a66768e4ba0d1f66737c081639b
Author: Anand <anekkunt@redhat.com>
Date:   Wed Jan 14 22:23:05 2015 +0530

    glusterd: Added iov error checking in rpc callbacks.
    
    Problem : glusterd was crashing with SIGABRT if rpc connection is failed in
    debug mode.
    
    Reason  : It was happening due to iov is passing to assert() before checking
    rpc status in rpc call back function (rpc is  calling callback function with
    setting rpc status as -1 and passing NULL to iov if connection is failed).
    
    Fix     : Error checking for iov added after checking the rpc status verified
    and error messages are added properly .
    
    Change-Id: I35c05c438444d0454aadac4e45524565a7be68a8
    BUG: 1181543
    Signed-off-by: Anand <anekkunt@redhat.com>
    Reviewed-on: http://review.gluster.org/9449
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit cdb3fa6088957ed257bfe2c3af59a80033cb2cbb
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jan 19 11:17:20 2015 +0100

    gfapi: allow transport=NULL for set_volfile_server()
    
    Users of gfapi should not need to care about the supported transport
    methods, this is an advanced option. Simple use-cases for libgfapi
    should be able to pass NULL as transport, and the libraries should take
    care of connecting to the Gluster server(s) correctly.
    
    BUG: 1183547
    Change-Id: Id93f96a3d10ae9fb69d53192642145ba8deed863
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 7510d8edf4e7bea50e0c1f041202f063a5d138af
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 29 15:32:28 2014 +0530

    mgmt/glusterd: Implement Volume heal enable/disable
    
    For volumes with replicate, disperse xlators, self-heal daemon should do
    healing. This patch provides enable/disable functionality for the xlators to be
    part of self-heal-daemon. Replicate already had this functionality with
    'gluster volume set cluster.self-heal-daemon on/off'. But this patch makes it
    uniform for both types of volumes. Internally it still does 'volume set' based
    on the volume type.
    
    Change-Id: Ie0f3799b74c2afef9ac658ef3d50dce3e8072b29
    BUG: 1177601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9358
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 1ee8ce725f0e70f45419aa0e2f4d85db7223d766
Author: GauravKumarGarg <ggarg@redhat.com>
Date:   Tue Jan 6 16:58:38 2015 +0530

    glusterd: option features.uss should accept only boolean value
    
    "features.uss" with a non-boolean value gets set in the volume option
    table because of which subsequent volume set operation fails since
    features.uss does not contain a valid boolean value.
    
    Fix is not to allow a non-boolean value to get set in the volume option
    table. "features.uss" option should have validation function "validate_uss"
    which validate the input value given by user.
    
    Change-Id: I4a212f876627a4979715183b0d488fd69095f193
    BUG: 1179175
    Signed-off-by: ggarg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9395
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit a29d6c80dfbd848e0b453d64faf761fe52b4d6c5
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Jul 4 19:40:14 2014 -0700

    doc: add documentation for DHT
    
    Change-Id: Iaa1ea72499a81134eb57a15867e0d08dd9c55bbd
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8240
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b45f623a7a8e14ca09a10c6a04c4c5f81e3a62e2
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Jan 16 14:26:45 2015 +0530

    cluster/dht: Fix incorrect updates to parent times
    
    In directory write FOPs, as far as updates to timestamps associated
    with parent by DHT is concerned, there are three possibilities:
    a) time (in sec) gotten from child of DHT < time (in sec) in inode ctx
    b) time (in sec) gotten from child of DHT = time (in sec) in inode ctx
    c) time (in sec) gotten from child of DHT > time (in sec) in inode ctx
    
    In case (c), for time in nsecs, it is the value returned by DHT's child
    that must be selected. But what DHT_UPDATE_TIME ends up doing is to choose
    the maximum of (time in nsec gotten from DHT's child, time in nsec in inode ctx).
    
    Change-Id: I535a600b9f89b8d9b6714a73476e63ce60e169a8
    BUG: 1179169
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9457
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 8d73f6288249757662cf36e746835e3ecd84add1
Author: vmallika <vmallika@redhat.com>
Date:   Thu Jan 8 16:03:04 2015 +0530

    quota: For a link operation, do quota_check_limit only till the
    common ancestor of src and dst file
    
    In a dht_rename, if src_cached and dst_hashed are different, then
    rename is split into link and unlink.
    We need to handle quota_link properly.
    
    We have fixed quota_rename in patch# 8940, we need to handle quota_link
    similarly
    
    > http://review.gluster.org/#/c/8940/
    > quota: For a rename operation, do quota_check_limit only till the
    > common ancestor of src and dst file
    
    > Example:
    > set quota limit set to 1GB on /
    > create a file /a1/b1/file1 of 600MB
    > mv /a1/b1/file1 /a1/b1/file2
    > This rename fails as it takes delta into account which sums up to 1.2BG.
    > Though we are not creating new file, we still get quota exceeded error.
    > So quota enforce should happen only till b1.
    
    > Similarly:
    > mv /a/b/c/file /a/b/x/y/file
    > quota enforce should happen only till dir 'b'
    
    > Change-Id: Ia1e5363da876c3d71bd424e67a8bb28b7ac1c7c1
    > BUG: 1153964
    > Signed-off-by: vmallika <vmallika@redhat.com>
    > Reviewed-on: http://review.gluster.org/8940
    > Tested-by: Gluster Build System <jenkins@build.gluster.com>
    > Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    > Tested-by: Raghavendra G <rgowdapp@redhat.com>
    
    Change-Id: I2c814018d17f7af1807c1d1d162d8bdcbb31e491
    BUG: 1153964
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9419
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 10e4add35f64c24fe9ef03dc6824975fc9db1455
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 16 13:48:49 2015 +0100

    build: add a tmpfiles.d config file for /run/gluster
    
    New distrubutions have a /run directory on a volatile tmpfs filesystem.
    This causes /run/gluster to be removed with each reboot. A tmpfiles.d
    configuration is used to create the directory on boot.
    
    EL5 and EL-6 do not use /run, current Fedora versions do. By checking
    %{_tmpfilesdir} in the .spec, we can identify if the distribution uses
    tmpfiles.d.
    
    Change-Id: I231e7d6603d573cb905246558e14a51577c0eb56
    BUG: 1182934
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9458
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 4d003c1b1b6dfd4ba94bb006b7ab6451fc62e170
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Jan 5 09:39:07 2015 -0500

    tests: let force_umount work on multiple items
    
    Some scripts (e.g. features/weighted-rebalance.t) try to unmount
    multiple mountpoints at once, using UMOUNT_LOOP.  This dutifully
    passes the $* list through to force_umount, which (prior to this
    fix) would only unmount $1 instead of the whole set.  This would
    leave those devices mounted, which would not only be a resource
    leak itself but would cause other cleanup actions to fail.
    
    Change-Id: I2e3379c85792765025540f10be7cb37b8a4c1bcf
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/9386
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4f734b04694feabe047d758c2a0a6cd8ce5fc450
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Jan 13 10:50:06 2015 +0100

    ec: Don't use inodelk on getxattr when clearing locks
    
    When command 'clear-locks' from cli is executed, a getxattr request
    is received by ec. This request was handled as usual, first locking
    the inode. Once this request was processed by the bricks, all locks
    were removed, including the lock used by ec.
    
    When ec tried to unlock the previously acquired lock (which was
    already released), caused a crash in glusterfsd.
    
    This fix executes the getxattr request without any lock acquired
    for the clear-locks command.
    
    Change-Id: I77e550d13c4673d2468a1e13fe6e2fed20e233c6
    BUG: 1179050
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9440
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 63dc6e1942dffcddd99c5048a498ca00eead8baa
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jan 15 09:38:04 2015 +0100

    ec: Remove unneeded 'inline' for ec_is_internal_xattr()
    
    An incorrectly placed 'inline' keyword caused compilation warnings
    with gcc 5.
    
    Change-Id: I2bf8c39b1514ea7dac13e82eb3b6ff4b98e62c79
    BUG: 1182267
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9452
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 658b090e9b54580861f7355329b448a64c642b6e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jan 13 11:52:13 2015 +0530

    tests: increase PROBE_TIMEOUT value to 60 secs
    
    Its noticed that in a slower build system, nodes may take more than 20 secs to
    finish the handshaking.
    One of the recent regression failure
    http://build.gluster.org/job/rackspace-regression-2GB-triggered/3635/consoleFull
    is the proof for it.
    
    Change-Id: Ibb69c51f31a697d5cb23bb688db80092c1de3047
    BUG: 1163543
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9438
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Anand Nekkunti <anekkunt@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7b58df7965ad557e23681d61164bfc7d609ed2cd
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 12 17:05:32 2015 +0530

    cluster/dht: Don't restore entry when only one subvolume is present
    
    Problem:
    When rmdir fails with op_errno other than ENOENT/EACCES then self-heal
    is attempted with zeroed-out stbuf. Only ia_type is filled from inode,
    when the self-heal progresses, it sees that the directory is still
    present and performs setattr with all valid flags set to '1' so the
    file will be owned by root:root and the time goes to epoch
    
    Fix:
    This fixes the problem only in dht with single subvolume. Just don't
    perform self-heal when there is a single subvolume.
    
    Change-Id: I6c85b845105bc6bbe7805a14a48a2c5d7bc0c5b6
    BUG: 1181367
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9435
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit dec4700c663975896f3aad1b4e59257263b4f4ac
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Nov 10 12:41:49 2014 +0530

    features/changelog: Cleanup .processing and .current directory
    
    On changelog_register cleanup .processing, .history/.processing,
    .current and .history/.current from the working directory.
    
    Moved glusterd_recursive_rmdir and glusterd_for_each_entry to common
    place(libglusterfs) and renamed as recursive_rmdir and
    GF_FOR_EACH_ENTRY_IN_DIR respectively
    
    BUG: 1162057
    Change-Id: I1f98468a344cead039026762a805437b2f9e507b
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9082
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 2466f4debbb629cf847c42f5d317cd5627b095c1
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Jan 14 17:55:53 2015 +0100

    NetBSD portability fix: recover errno on runner error
    
    Some time ago we introduced F_CLOSEM to efficiently close unused
    file descriptors when using a runner. But since it also close the
    file descriptor used to send back errno to glusterd, it got unable
    to detect an error on execve().
    
    Fix this by backing out F_CLOSEM usage.
    
    BUG: 1129939
    Change-Id: I40d3255555145e04e8feafaa2ff4e5fb1570e9a2
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9447
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9ab533ff86dbf914b47228a9326fefd9ba04c65f
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Dec 17 13:19:00 2014 +0530

    protocol/client: Prevent "Dereference after NULL check" errors.
    
    Fixes 46 defects marked as "Dereference after NULL check" errors
    in coverity scan for client xlator.
    
    Change-Id: I0b4c991a3995ce74d7885fc5470ec7f5c589b411
    BUG: 789278
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/9287
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit a3bc6cf85d20ab21380f96f8d11cad29a53b3bb4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 14 17:10:41 2015 +0530

    storage/posix: Don't try to set gfid in case of INTERNAL-mknod
    
    Change-Id: I96540ed07f08e54d2a24a3b22c2437bddd558c85
    BUG: 1088649
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9446
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 8beaf169e39b262416e2274a028292379d39b310
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jan 9 14:43:22 2015 +0000

    cluster/afr: split-brain resolution CLI
    
    Extend the AFR heal command to include automated split-brain resolution.
    
    This patch [3/3] is the final patch for afr automated split-brain resolution
    implementation.
    
    "gluster volume heal <VOLNAME> [full | statistics [heal-count [replica
    <HOSTNAME:BRICKNAME>]] |info [healed | heal-failed | split-brain]| split-brain
    {bigger-file <FILE> |source-brick <HOSTNAME:BRICKNAME> [<FILE>]}]"
    
    The new additions being:
    1.gluster volume heal <VOLNAME> split-brain bigger-file <FILE>
    Locates the replica containing the FILE, selects bigger-file as source and
    completes heal.
    
    2.gluster volume heal <VOLNAME> split-brain source-brick <HOSTNAME:BRICKNAME>
    <FILE>
    Selects <FILE> present in <HOSTNAME:BRICKNAME> as source and completes heal.
    
    3.gluster volume heal <VOLNAME> split-brain <HOSTNAME:BRICKNAME>
    Selects all split-brained files in <HOSTNAME:BRICKNAME> as source and completes
    heal.
    
    Note: <FILE> can be either the full file name as seen from the root of the
    volume (or) the gfid-string representation of the file, which sometimes gets
    displayed in the heal info command's output.
    
    Entry/gfid split-brain resolution is not supported.
    
    Example can be found in the test case.
    
    Change-Id: I4649733922d406f14f28ee9033a5cb627b9538b3
    BUG: 1136769
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9377
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6da85222e5e49bcb15c4c8998f26c8dffb6a5b34
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jan 9 15:36:42 2015 +0000

    api: versioned symbols for glfs_resolve()
    
    A minor fix not addressed in http://review.gluster.org/#/c/9143/.
    
    Needed by http://review.gluster.org/#/c/9377/5/ to resolve a merge conflict and
    for a sucessful compile without warnings about implicit declarations.
    
    Change-Id: I4aeb3b53887687096b69516c42a0888c6e137bf6
    BUG: 1160709
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9439
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit c4561b6fd90c52667eebec9eecf974b4c0786382
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jan 8 09:43:50 2015 +0530

    rpc: initialise transport's list on creation
    
    Initialising the transport's list, meant to hold clients connected to
    it, on the first connection event is prone to race, especially with the
    introduction of multi-threaded event layer.
    
    BUG: 1181203
    Change-Id: I6a20686a2012c1f49a279cc9cd55a03b8c7615fc
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9413
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit e9c90da38e1b6fb7fc4e0d5d1e987c510d1c17d6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jan 13 11:40:03 2015 +0530

    tests: move all snapshot test cases from glusterd to snapshot component
    
    Change-Id: Id04037a38e80fe9b400678cfe6bc731cdefae834
    BUG: 1178685
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9437
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 015282013a22dda84d1849e18659d42bb5bb48f4
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jan 12 12:19:17 2015 +0530

    geo-rep: Handle Volume status error while getting slave nodes
    
    gluster volume status command not returns xml output, when any
    error like "Transaction in Progress", we need to handle returncode
    along with xml error.
    
    BUG: 1151412
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Change-Id: Id5b7712df7cff58744b4c5a0d00870aec1d926a8
    Reviewed-on: http://review.gluster.org/9432
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit f91d19a9ce6ec6659c84c3f907ebc3ecaceba176
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 12 12:50:50 2015 +0530

    storage/posix: Set gfid after all xattrs, uid/gid are set
    
    Problem:
    When a new entry is created gfid is set even before uid/gid, xattrs
    are set on the entry. This can lead to dht/afr healing that file/dir
    with the uid/gid it sees just after the gfid is set, i.e. root/root.
    Sometimes setattr/setxattr are failing on that file/dir.
    
    Fix:
    Set gfid of the file/directory only after uid/gid, xattrs are setup
    properly. Readdirp, lookup either wait for the gfid to be assigned
    to the entry or not update the in-memory inode ctx in posix-acl
    xlator which was producing lot EACCESS/EPERM to the application
    or dht/afr self-heals.
    
    Change-Id: I0a6ced579daabe3452f5a85010a00ca6e8579451
    BUG: 1088649
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9434
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 3971315248c57386e05e6c8f57369a4571555cb2
Author: Shyam <srangana@redhat.com>
Date:   Thu Jan 8 13:56:08 2015 -0500

    fuse: Fix cores in notify function when this is executed in parallel
    
    The fuse notify function gets called by the epoll or the poll thread
    and till the point there is a single epoll thread, 2 notify
    instances would not race with each other.
    
    With the upcoming multi thread epoll changes, it is possible that
    2 epoll threads invoke the notify function. As a result races
    in this function are fixed with this commit.
    
    The races seen are detailed in the bug, and the fix here is to
    enforce a (slightly) longer critical section when updating the
    fuse private structure and reserving state updates post error
    handling.
    
    Change-Id: I6974bc043cb59eb6dc39c5777123364dcefca358
    BUG: 1180231
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9421
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 9d37406b59fc33940c8e4e925ef9803b2d9b6507
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jan 9 10:15:04 2015 +0530

    glusterd: quorum calculation should happen on global peer_list
    
    Apart from snapshot, for all other transactions quorum should be calculated on
    global peer list.
    
    Change-Id: I30bacdb6521b0c6fd762be84d3b7aa40d00aacc4
    BUG: 1177132
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9422
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 04e222e88d56cf06c0470e60c6910611a8286657
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 12 10:33:06 2015 +0530

    storage/posix: Set correct fsgid before doing symlink
    
    Change-Id: Ic50dfa5e5084c7b148e42a5014cca2b47c8ab5ed
    BUG: 1180986
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9431
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit c49a77001bd80affa70d22ba974d8de9e3f0f0cd
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Nov 18 11:08:16 2014 -0500

    api: versioned symbols in libgfapi.so for compatibility
    
    Use versioned symbols to keep libgfapi at libgfapi.so.0.0.0
    
    Revisited to address broken build on Mac OS X
    
    See http://review.gluster.org/9036
    
    Rebased to include http://review.gluster.org/#/c/9376/ (glfs_resolve())
    but note that gerrit's "Rebase Change" couldn't do it.
    
    N.B. noticed that glfs_get_volumeid() decl in glfs.h was missing
    the __THROW, added it.
    
    On systems using ELF and the GNU toolchain, symbol versions are created
    with a .symver asm operand in the .c source file. Clang is claimed to
    be compatible with gcc, so we'll pretend for now that this also works
    with clang.
    
    On Mac OS X, aliases are created with __asm "magic" in the .h header
    file. In the normal case, when both the decl and defn match, that's
    all that's needed. In our case though the decl and defn don't match ---
    we have, e.g. a defn such as 'int glfs_foo(...)' and the corresponding
    decl is 'int pub_glfs_foo(...)'. To make this work we create the necessary
    aliases in the library at link time with the -alias_list link option.
    
    Note that this results in there being pairs of symbols in the .dylib,
    e.g. _pub_glfs_foo and _glfs_foo$GFAPI_3.4.0. We could use another
    link option, -unexported_symbols_list to elide the _pub_glfs_* symbols.
    (And we probably should.)
    
    Linux symbol versioning was essentially copied from Solaris; in general
    I would expect this to "just work" on Solaris, but until someone tries
    we don't really know.
    
    Change-Id: Icb96a3c2d80be7b6d7a6849bb9168f03a947f47c
    BUG: 1160709
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/9143
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit f839e25a1ee67279c0c59da9d7262728133e8b37
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jan 9 10:36:38 2015 +0530

    glusterd: glusterd socket files should reside in /var/run/gluster
    
    glusterfs socket files should not reside outside of gluster folder.
    
    Change-Id: I5d7b43b11c8c78a32df8aaf38917b80e4e33c9d0
    BUG: 1180972
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9423
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 119bedfa06c3a6bb38089dafbcd6e0c2bd9b26cf
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 7 20:48:51 2015 +0530

    tests: ancestry building quota tests on fuse mount
    
    quota-anon-fd-nfs.t is essentially testing ancestry building code path and
    quota limit reaching. Since nfs client and server on same machine leads to
    deadlocks, it is better to use fuse mount to trigger these code paths. Just
    stop the volume and start again, this wipes the inode table clean. Performing
    writes after this will trigger ancestry building + quota checks.
    
    Change-Id: I2d37a8662040a638d3fac3f9535d32498a5b434d
    BUG: 1163543
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9408
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 12022fc87ee6b12c07bff0381701e2977e722382
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Jan 10 05:49:42 2015 +0100

    Spare spurious regression in quota.t
    
    Like quota-nfs.t, quota.t shows spurious regressions because dd
    writes too fast. Reuse the C program used by quota-nfs.t to
    write slowly, and rename it to show it is not specific to quota-nfs.t
    
    BUG: 1129939
    Change-Id: I14b50e368023e88dc8bcc76c266cc908d62f89e2
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9410
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 548547b2e41c8e2cf79b929405cf18aecbdedebc
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jan 6 10:03:49 2015 -0500

    transport: fix default behavior for SSL authorization
    
    Previously, enabling SSL authentication/encryption but not authorization
    required explicitly setting ssl-allow=*.  Now that same behavior is the
    default (i.e. when ssl-allow is not set).
    
    Also, there's no reason that a name used for *login* auth (typically a
    UUID for internal purposes or a human name when using SSL) should
    validate as an RFC-compliant host name or IP address.  Therefore the
    validation only occurs when the auth type is "addr" (not "login" or
    anything else).
    
    Change-Id: I01485ff4f0ab37de4b182858235a5fb0cf4c3c7d
    BUG: 1179208
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/9397
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9408dc7b416ca80b3b8d8ecae2ef75c7e9cd21cd
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Jan 8 06:22:17 2015 +0100

    Fix bad shell calculation in tests/basiv/afr/self-heald.t
    
    A shell variable calculation in tests/basiv/afr/self-heald.t
    resulted in spurious regression failure at test 67.
    
    This is wrong and always produce an error: $((`date +"%j"`))%2
    This still fails because date +"%j" produces 008, which is considered
    an octal value: $((`date +"%j"` %2 ))
    This works: $((`date +"%j"|sed 's/^0*//'` % 2 ))
    
    BUG: 1129939
    Change-Id: I5d0d27b7bb64ef7d56bafebe71aafe01eb2f39a7
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9414
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit eaf7164ff824ad4d69cf225e49c54fc473b300b8
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Sat Nov 8 21:07:09 2014 +0100

    ec: Remove O_APPEND from flags on create and open.
    
    Allowing O_APPEND flag to pass through to the brick files
    corrupts fragment contents because writes are not stored on
    the desired place.
    
    Write fop has been modified so that it uses current file
    size as its write offset. This guarantees that all writes,
    even those comming from different file descriptors and
    clients, will write to the end of the file.
    
    Change-Id: I9f721f12217a98231fe52e344166d1c94172c272
    BUG: 1161621
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9079
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 71844788a1da0249201b27109e3ea00599569b93
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Fri Aug 8 09:47:10 2014 +0200

    protocol/server: Fix possible memory leaks of xdata
    
    There was a memory leak of xdata argument in fops (f)setxattr,
    (f)xattrop and statfs. This leak was minor because xdata is
    rarely, or even not used at all, in this fops.
    
    Change-Id: Ie1083ae227755a11cf72f8d89595520a5afb3042
    BUG: 1127653
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8434
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bbb4b7679be26ed5460524bcf26e779f6907d299
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 31 12:47:47 2014 +0530

    feature/changelog: Logging entry as well for explicit sync virtual xattr.
    
    This is an improvement over the patch 'http://review.gluster.org/9337'
    to trigger explicit geo-rep sync on regular files even if entry is not
    present on the slave. An attempt is made to find the pargfid and
    if available captures CREATE along with DATA in changelog.
    CREATE is captured with default file permissions. Setting this virtual
    setxattr on directories captures MKDIR in changelog. The value of
    setxattr can be as follows.
    
    If value = "1"       : Both CREATE and DATA is captured in changelog if
                           pargfid is available, else on DATA is captured.
       value = "any other: ENOTSUP is returned.
    
    Usage:
      setfattr -n glusterfs.geo-rep.trigger-sync -v "1" <file-path>
    
    NOTE: This patch supports explicit record of entries only for
          directories and regular files.
    
    Change-Id: Iedde8b2c8bc3b78db524050d8c866ff664811d01
    BUG: 1176934
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9370
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 70dc47389cbe08238d8c216c51d49583154bd08a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 5 16:21:52 2015 +0530

    cluster/ec: Handle internal xattr get/set
    
    Problem:
    Internal xattrs of EC like trusted.ec.size/config/version
    can be modified by users and that can lead to misbehavior
    in EC.
    
    Fix:
    Don't let the user modify the xattrs. Hide these xattrs
    in getfattr outputs.
    
    Change-Id: I39cec96ae12826b506b496fda7da74201015fd75
    BUG: 1178688
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9385
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit cf0770c61af2fa49fa435baf62cd5f28569175e4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 7 12:08:48 2015 +0530

    cluster/ec: Do not modify quota, selinux xattrs in healing
    
    Problem:
    EC heal tries to heal quota-size, selinux xattrs as well.  quota-size is
    private to the brick but since quotad accesses them using the standard
    interface as well, they can not be filtered in the fops.
    
    Fix:
    Ignore QUOTA_SIZE_KEY and SELINUX xattrs during heal.
    
    Change-Id: I1572f9e2fcba7f120b4265e034953a15ff297f04
    BUG: 1179640
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9401
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 05d3dfb9623f0939fa807cce3b9336a09fadab2a
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jan 8 08:35:33 2015 +0000

    glusterd: use list_for_each_entry_safe for cleanup
    
    Use list_for_each_entry_safe() instead of
    list_for_each_entry() for cleanup of local
    xaction_peers list.
    
    Change-Id: I6d70c04dfb90cbbcd8d9fc4155b8e5e7d7612460
    BUG: 1173414
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9416
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 4056ed598f642d2d23a65b79495b0247d84db2f4
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jan 6 07:40:32 2015 +0000

    glusterd: Refactor glusterd-utils.c
    
    Refactor glusterd-utils.c to create
    glusterd-snapshot-utils.c consisting of all snapshot
    utility functions.
    
    Change-Id: Id9823a2aec9b115f9c040c9940f288d4fe753d9b
    BUG: 1176770
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9391
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit d0b07fae1fece688333888cfc408bc7c031ae8bf
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jan 7 15:16:32 2015 +0530

    avoid memory leaks in snapview-server
    
    * snapview-server in readdirp, creates the inode for entries with names "." and
      ".." for each readdirp operation without creating dentries leading to memleak.
      It should have avoided creation of inodes for those entries
    
    Change-Id: I3b2025fd10872fcc3303d0becec764ffd4e37601
    BUG: 1179663
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9404
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 250944d56c0d942db07c194412acca27976a0310
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Jan 6 04:26:09 2015 +0530

    test : removing quota-anon-fd-nfs.t for time being.
    
    I am removing quota-anon-fd-nfs.t for time being as it is causing
    lots of regression failure. Meanwhile I will be working in parallel
    to find out the root cause for this spurious failure in another patch
    (http://review.gluster.org/#/c/9381/). I'll revert this patch once a proper fix is found.
    
    Change-Id: I0ef205241219ed3210d58d2b487f1b00292115f0
    BUG: 1163543
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9390
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit cd338784d39b9a4a55cc3c6a1613b90a2a63a8e3
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jan 1 15:55:22 2015 +0000

    api: export glfs_resolve()
    
    glfs_resolve() is an internal function in libgfapi. Export it so that it can be
    used by glfs-heal.c. The change is done in line with the approach followed in
    commit 7e497871d11a3a527e2ce192e4274322631f27d0 (http://review.gluster.org/9036)
    
    This patch [2/3] is required as a part of afr automated split-brain resolution
    implementation.
    
    Change-Id: If9057f2a037fd25a0dfa231683bfbaa72d3cb1b2
    BUG: 1136769
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9376
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 6e2318f0821d7c58eddc837b2d218247243a5c8d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Dec 26 12:18:31 2014 +0530

    glusterd: cluster quorum count check correction
    
    Due to the recent change introduced by commit
    da9deb54df91dedc51ebe165f3a0be646455cb5b cluster quorum count calucation now
    depends on whether the peer list is either all peers or global transaction peer
    list or the local transaction peer list.
    
    Change-Id: I9f63af9a0cb3cfd6369b050247d0ef3ac93d760f
    BUG: 1173414
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9350
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 64954eb3c58f4ef077e54e8a3726fd2d27419b12
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 26 12:57:48 2014 +0100

    tests: move all test-cases into component subdirectories
    
    There are around 300 regression tests, 250 being in tests/bugs. Running
    partial set of tests/bugs is not easy because this is a flat directory
    with almost all tests inside.
    
    It would be valuable to make partial test/bugs easier, and allow the use
    of mulitple build hosts for a single commit, each running a subset of
    the tests for a quicker result.
    
    Additional changes made:
    - correct the include path for *.rc shell libraries and *.py utils
    - make the testcases pass checkpatch
    - arequal-checksum in afr/self-heal.t was never executed, now it is
    - include.rc now complains loudly if it fails to find env.rc
    
    Change-Id: I26ffd067e9853d3be1fd63b2f37d8aa0fd1b4fea
    BUG: 1178685
    Reported-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reported-by: Atin Mukherjee <amukherj@redhat.com>
    URL: http://www.gluster.org/pipermail/gluster-devel/2014-December/043414.html
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9353
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c4ab37c02e9edc23d0637e23d6f2b42d0827dad2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jan 1 15:16:41 2015 +0000

    libglusterfs: change signature of syncop_(f)getxattr
    
    Pass xdata dict to syncop_(f)getxattr calls.
    
    This patch [1/3] is required as a part of afr automated split-brain resolution
    implementation.
    
    Change-Id: I3970b3dd6daf64681a031e37f8e9afb14fb3d668
    BUG: 1136769
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9375
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b8e3b91b8180dcc5e9f8bb62734832ace69ad143
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Jan 5 16:02:40 2015 +0530

    cli: logging improvements
    
    1. cli used to log messages at all log levels. This is related to
    a peculiar behavior of gcc which treats any enum variable whose type
    has non-negative only defined values to be an unsigned integer.
    This would cause cli's loglevel (defaulted from state->loglevel) to be
    set as (uint)-1 previously and hence all log messages across
    levels would appear in the cli log file. Now cli's loglevel defaults to
    log level INFO.
    
    2. Changed logging level of messages of type "Returning %d".. to DEBUG.
    
    Change-Id: I05094e523fc277d9ad32cc9d76aee873c0fd3859
    BUG: 1168809
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/9383
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f30af2735cab7475d86665856b433ca409e79ee7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Dec 31 15:15:53 2014 +0530

    cluster/afr: serialize inode locks
    
    Problem:
    Afr winds inodelk calls without any order, so blocking inodelks
    from two different mounts can lead to dead lock when mount1 gets
    the lock on brick-1 and blocked on brick-2 where as mount2 gets
    lock on brick-2 and blocked on brick-1
    
    Fix:
    Serialize the inodelks whether they are blocking inodelks or
    non-blocking inodelks.
    
            Non-blocking locks also need to be serialized.
    Otherwise there is a chance that both the mounts which issued same
    non-blocking inodelk may endup not acquiring the lock on any-brick.
    Ex:
    Mount1 and Mount2 request for full length lock on file f1.  Mount1 afr may
    acquire the partial lock on brick-1 and may not acquire the lock on brick-2
    because Mount2 already got the lock on brick-2, vice versa. Since both the
    mounts only got partial locks, afr treats them as failure in gaining the locks
    and unwinds with EAGAIN errno.
    
    Change-Id: Ie6cc3d564638ab3aad586f9a4064d81e42d52aef
    BUG: 1176008
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9372
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 2ddd3b2f2bdd6b2046edb0af1e3685dff866ddf6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Dec 24 14:11:42 2014 +0530

    tests: return non-zero value instead of exit in functions within the test run
    
    using 'exit 1' would terminate the test script which means cleanup
    will never get triggered for that test run which is incorrect.
    Instead use 'return 1'.
    
    Change-Id: I48c36cff4b2ddfcc2bd8ceb85484720161fe58f0
    BUG: 1163543
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9333
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 7e27cb2352b4f48935e85e3288a24ac03c3d1f83
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Jan 2 12:28:12 2015 +0530

    features/uss: Perform NULL check on @name in svc_getxattr
    
    LISTXATTR fop is internally converted into a GETXATTR with
    the "name" parameter set to NULL. In svc_getxattr(), a listxattr
    was causing a crash because of a NULL pointer dereference on @name.
    
    FIX:
    Add the necessary NULL check.
    
    Change-Id: I70024d40dc0695648c6d41b423c2665d030e1232
    BUG: 1178079
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9378
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4c3a6bc4573013df1912996e77ded48fddc01516
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Dec 24 14:17:21 2014 +0100

    Do not use umount -l on non Linux systems
    
    Lazy unmount are only supported on Linux. Force umount instead, since
    this code path is used in emergency exit anyway.
    
    On NetBSD, just have the filesystem calling exit, the kernel will unmount.
    
    BUG: 1129939
    Change-Id: If623ebf60b7a747ea7e78034b6d71ec2241dea4a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9334
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a96375c180901756753246cb00b42f44fd8b4fd7
Author: Anuradha <atalur@redhat.com>
Date:   Tue Dec 30 18:54:33 2014 +0530

    afr: Fixes to commit 85427a23c238499137cbfaafdb7b6ad27f67506a
    
            * Fixed a dict leak
            * Re-added 'return on failure' check
    
    Change-Id: I07edd03e4608fd2b7c4a91019a0e43033e6e78b2
    BUG: 1163804
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9368
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c8263975862afa9e5afc603bf2d05ab93087bcc4
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Dec 30 17:16:57 2014 +0530

    build: Remove files completely in make uninstall.
    
    If we create symlinks are part of make install,
    should remove them as part of make uninstall.
    
    Change-Id: Ie6e641caed60104cd256de4f020c1c6743d4ae60
    BUG: 1177767
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9367
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 59a195ba9ca5485697802eec3550d5535f437b47
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Nov 12 17:36:37 2014 +0530

    doc: added did-you-know.md to document the less-known
    
    behaviours and features of GlusterFS
    
    Change-Id: Ibabc6398be9fb1c20127aaad2c51a629fed7c10b
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9103
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 0250eb0698e567134ddd897b134bbe4f8da003a2
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue Dec 30 10:47:49 2014 +0530

    test: Make gfid-access.py more generic.
    
    Few of the hard coded values, uid, gid and file permissions
    are made as arguments to make the script more generic.
    Also fixes the permission issue which was hard coded
    as integer instead of octal.
    
    Change-Id: Icec700770de2b7cae00e02f783d072860e6d5e2b
    BUG: 1176934
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9366
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c399cec72b9985f120a1495e93e1a380911547d9
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Dec 26 19:12:22 2014 +0530

    geo-rep: Error handling in tar+ssh mode
    
    Georep raises exception if tar+ssh fails and worker
    dies due to the exception.
    
    This patch adds resilience to tar+ssh error and geo-rep
    worker retries when error, and skips those changelogs
    after maximum retries.(same as rsync mode)
    
    Removed warning messages for each rsync/tar+ssh failure
    per GFID, since skipped list will be populated after Max
    retry. Retry changelog files log also available, hence
    warning message for each GFID is redundent.
    
    BUG: 1177527
    Change-Id: I3019c5c1ada7fc0822e4b14831512d283755b1ea
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/9356
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 5e7e12694e3898ef7bb5425827122c434a465ce8
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Dec 24 21:26:28 2014 +0530

    feature/changelog: Virtual xattr to trigger explicit sync in geo-rep.
    
    A virtual xattr "glusterfs.geo-rep.trigger-sync" is provided
    in glusterfs through changelog translator. Geo-rep triggers
    a explicit data sync on setting this xattr on a file.
    Changelog captures a DATA entry on file's gfid on setting this
    virtual xattr on a file. This is supported only for files. It
    doesn't support directories.
    
    Usage: setfattr -n glusterfs.geo-rep.trigger-sync <file-path>
    
    Change-Id: Ia689326ac2dcb31035ffbecad2c548eda4eb9245
    BUG: 1176934
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9337
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 41e0e325aa7733285733fb00230fdaafdc80c25a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Dec 19 16:36:25 2014 +0530

    glusterd: Move statedump utils into a new file.
    
    Change-Id: I1bf26c9d294e95f7b82cfc7a96f9d5575f5e0362
    BUG: 1176770
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9313
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit f7a8bd08c80a33a9e2459b47e203a8bc841abc54
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Dec 18 09:18:12 2014 +0530

    glusterd: check_volume_exists should query in-memory representation
    
    ... instead of consulting the on-disk data directory. There is no reason
    why the on-disk is more accurate than the in-memory representation. In
    fact, it is the other way around when a node is reconciling
    volume/cluster configuration with the rest of the cluster.
    
    Change-Id: I786823efdf1d0f6b9e6fcdb72d51e5227c399ce1
    BUG: 1176770
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9292
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 94dacaa4e91d11760666e9c4e4a6bdf39ae03c6b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Dec 26 10:12:11 2014 +0530

    glusterd: coverity fix for overrun in glusterd_stop_uds_listener
    
    CID: 1260432
    
    Change-Id: I6845bc4c231b53428419a5a2ad0c78ea9da31058
    BUG: 1093692
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9338
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 86433c25b61073f244cde0bf80a7857b57ab1265
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Dec 26 10:36:00 2014 +0530

    mgmt/glusterd: Add option to enable lock trace
    
    Change-Id: I24ed0f866d53e91a8323c043a38f73207cbfd7d2
    BUG: 1168189
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9351
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b6ea761969f85fbb0f22810eb3a3bf1476c8792c
Author: vmallika <vmallika@redhat.com>
Date:   Wed Dec 24 15:13:36 2014 +0530

    quota: For a rename operation, do quota_check_limit only till the
    common ancestor of src and dst file
    
    Example:
    set quota limit set to 1GB on /
    create a file /a1/b1/file1 of 600MB
    mv /a1/b1/file1 /a1/b1/file2
    This rename fails as it takes delta into account which sums up to 1.2BG.
    Though we are not creating new file, we still get quota exceeded error.
    So quota enforce should happen only till b1.
    
    Similarly:
    mv /a/b/c/file /a/b/x/y/file
    quota enforce should happen only till dir 'b'
    
    Change-Id: Ia1e5363da876c3d71bd424e67a8bb28b7ac1c7c1
    BUG: 1153964
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8940
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2947752836bd3ddbc572b59cecd24557050ec2a5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Nov 17 14:27:47 2014 +0530

    cluster/afr: Make entry-self-heal in afr-v2 compatible with afr-v1
    
    Problem:
    entry self-heal in 3.6 and above, takes full lock on the directory only for the
    duration of figuring out the xattrs of the directories where as 3.5 takes locks
    through out the entry-self-heal. If the cluster is heterogeneous then there is
    a chance that 3.6 self-heal is triggered and then 3.5 self-heal will also
    triggered and both the self-heal daemons of 3.5 and 3.6 do self-heal.
    
    Fix:
    In 3.6.x and above get an entry lock on a very long name before entry self-heal
    begins so that 3.5 entry self-heal will not get locks until 3.6.x entry
    self-heal completes.
    
    Change-Id: I71b6958dfe33056ed0a5a237e64e8506c3b0fccc
    BUG: 1168189
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9227
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 02b2172d9bc1557b3459388969077c75b659da82
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 14 14:23:31 2014 +0530

    features/locks: Add lk-owner checks in entrylk
    
    For backward compatibility of entry-self-heal we need
    entrylks to be accepted by same lk-owner and same client.
    This patch introduces these changes.
    
    Change-Id: I67004cc5e657ba5ac09ceefbea823afdf06929e0
    BUG: 1168189
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9125
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7926fe6f7df664bbe5e050a8e66240dd67155eec
Author: Anand Avati <avati@redhat.com>
Date:   Tue Dec 23 10:04:00 2014 -0800

    afr: stop encoding subvolume id in readdir d_off
    
    The purpose of encoding d_off in AFR is to indicate the
    selected subvolume for the first readdir, and continue all
    further readdirs of the session on the same subvolume. This is
    required because, unlike files, dir d_offs are specific to the
    backend and cannot be re-used on another subvolume. The d_off
    transformation encodes the subvolume id and prevents such
    invalid use of d_offs on other servers.
    
    However, this approach could be quite wasteful of precious d_off
    bit-space. Unlike DHT, where server id can change from entry to
    entry and thus encoding the server id in the transformed d_off
    is necessary, we could take a slightly relaxed approach in AFR.
    The approach is to save the subvolume where the last readdir
    request was sent in the fd_ctx. This consumes constant space (i.e
    no per-entry cache), and serves the purpose of avoiding d_off
    "misuse" (i.e using d_off from one server on another).
    
    The compromise here is NFS resuming readdir from a non-0 cookie
    after an extended delay (either anonymous FD has been reclaimed,
    or server has restarted). In such cases a subvolume is picked
    freshly. To make this fresh picking more deterministic (i.e, to
    pick the same subvolume whenever possible, even after reboots),
    the function afr_hash_child (used by afr_read_subvol_select_by_policy)
    is modified to skip all dynamic inputs (i.e PID) for the case
    of directories.
    
    Change-Id: I46ad95feaeb21fb811b7e8d772866a646330c9d8
    BUG: 1163161
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/9332
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 79a5b2b991037cc1db5c71f7aa2a32ce712a22e9
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Jun 23 22:59:14 2014 +0530

    features/marker: log message clean up
    
    1. Changed log messages to be more appropriate.
    2. Changed loglevel of failures in fop_cbks to be recorded as TRACE.
       Logging of failures at higher loglevels is unessential in non-endpoint
     translators.
    3. Removed a log message related to memory allocation failure.
    
    BUG: 1174087
    Change-Id: I63c560c3bbd12706357fb3f696378c1a1e1efb44
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/8168
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 92cc5d4f64d55675b45b85f612f513500d4e4fc7
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Dec 23 21:13:32 2014 +0530

    geo-rep: Sync atime, mtime to slave when SETATTR
    
    Existing geo-rep only syncs chown and chmod, with this
    patch geo-rep also syncs atime and mtime.
    
    Change-Id: Iea52d86682873bb4a47eeb0d325f5b9ddf2de2cf
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    BUG: 1176934
    Reviewed-on: http://review.gluster.org/9331
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 0299f7f0f7c4d8e5e7e04d8bc1787ecbee6dbe52
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Dec 19 16:38:43 2014 +0530

    afr: coverity fixes
    
    Some fixes for the 17th Dec 2014 run.
    https://scan6.coverity.com:8443/reports.htm#v31028/p10714/g31029
    
    Change-Id: Ia4410ef87a56fffb61803d0a4e62369b058e1cfb
    BUG: 1176089
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9314
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 85427a23c238499137cbfaafdb7b6ad27f67506a
Author: Anuradha <atalur@redhat.com>
Date:   Fri Dec 12 12:56:22 2014 +0530

    cluster/afr : Change in volume heal info command
    
    	gluster volume heal <volname> info command
    will now also display if the files listed (in the output
    of the command) are in split-brain or possibly being
    healed.
    
    This patch also fixes build warning that occurs.
    Change-Id: I1fc92e62137f23b2b9ddf6e05819cee6230741d1
    BUG: 1163804
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9119
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f3df93783d8c817722e086b14b97fa6bc9d0fce8
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Dec 19 17:07:50 2014 +0530

    glusterd: fix unix domain notify fn
    
    ... and unlink the 'right' socket file
    
    Change-Id: Id12ee8c622914555b7933104e13b43b3b31b5d19
    BUG: 1176770
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9315
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 9a6ea92df1007cc6f402ff7cc560e3206fa42e62
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Dec 23 06:54:50 2014 +0100

    Avoid spurious directory metedata split brain
    
    When directory content is modified, [mc]time is updated. On
    Linux, the filesystem does it, while at least on NetBSD, the
    kernel file-system independant code does it. This means that
    when entries are added while bricks are down, the kernel sends
    a SETATTR [mc]time which will cause metadata split brain for
    the directory. In this case, clear the split brain by finding
    the source with the most recent modification date.
    
    BUG: 1129939
    Change-Id: Ic0177e0df753a4748624d0b906834ed54593adb9
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9291
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit da9deb54df91dedc51ebe165f3a0be646455cb5b
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Dec 12 07:21:19 2014 +0530

    glusterd: Maintain  per transaction xaction_peers list in syncop & mgmt_v3
    
    In current implementation xaction_peers list is maintained in a global variable
    (glustrd_priv_t) for syncop/mgmt_v3. This means consistency and atomicity of
    peerinfo list across transactions is not guranteed when multiple syncop/mgmt_v3
    transaction are going through.
    
    We had got into a problem in mgmt_v3-locks.t which was failing spuriously, the
    reason for that was two volume set operations (in two different volume) was
    going through simultaneouly and both of these transaction were manipulating the
    same xaction_peers structure which lead to a corrupted list. Because of which in
    some cases unlock request to peer was never triggered and we end up with having
    stale locks.
    
    Solution is to maintain a per transaction local xaction_peers list for every
    syncop.
    
    Please note I've identified this problem in op-sm area as well and a separate
    patch will be attempted to fix it.
    
    Finally thanks to Krishnan Parthasarathi and Kaushal M for your constant help to
    get to the root cause.
    
    Change-Id: Ib1eaac9e5c8fc319f4e7f8d2ad965bc1357a7c63
    BUG: 1173414
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9269
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 0e78a12381e988a06e1d5a2dd592d132e24a4e10
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 19 18:27:14 2014 +0100

    gfapi: always close the fd in glfs_h_creat()
    
    When running stress and performance tests against nfs-ganesha, the
    number of open file descriptors increases continously. If the tests run
    long enough, the brick processes will eventually run out of file
    descriptors.
    
    This seems to be caused by glfs_h_creat() which allocates a 'struct
    glfs_fd', but does not release it. A normal glfs_creat() returns the
    file descriptor to the application, whereas glfs_h_creat() returns a
    handle (struct glfs_object). The file descriptor associated with the
    handle can not be release by glfapi-applications.
    
    This fd-leak can be prevented by destroying the 'struct glfs_fd' before
    returning the 'struct gfls_object' to the gfapi-application.
    
    Change-Id: I32465077a35cd0449a8e584c53899b32f022e5af
    BUG: 1176242
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9318
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 72c8b09640976ecf0c2a50dcf92a1b8648e723d4
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Sep 5 07:32:20 2014 +0000

    glusterd: Returning success from mgmt_v3 handler functions
    
    The mgmt_v3 handler functions already send the ret code as
    part of the *send_resp calls, and further propagating the
    ret code to the calling functions will lead to double deletion
    of the req object. Hence returning success from the mgmt_v3
    handler functions.
    
    Change-Id: I1090e49c54a786daae5fd97b5c1fbcb5d819acba
    BUG: 1138577
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8620
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 81301d3b006e5490699d5bf70833d92b05a47dca
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Dec 17 11:20:20 2014 +0000

    glusterd: Copy brick port no. if brick is running
    
    Instead of relying on brickinfo->status, check if the brick
    process is running before copying the brick port number.
    
    Change-Id: I246465fa4cf4911da63a1c26bbb51cc4ed4630ac
    BUG: 1175700
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9297
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8484a88364b97ce3bc882db0f2da29633c03c1a5
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Dec 16 12:34:19 2014 +0530

    mgmt/glusterd: do not restart nfs server when snapshot is deactivated
    
    Change-Id: Ie5eaa2beb4446640b22873f91e17da90d1cd8fad
    BUG: 1174625
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9280
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit bb1517ed540857cc933c6d111b613bc1db0273c6
Author: Humble Devassy Chirammal <hchiramm@redhat.com>
Date:   Thu Dec 11 12:50:14 2014 +0530

    MAINTAINERS: Adding new sub maintainers.
    
    http://supercolony.gluster.org/pipermail/gluster-devel/2014-December/043177.html
    
    
    Change-Id: Iec587f383cf8da9832932194e2518a6bd99c6380
    Signed-off-by: Humble Devassy Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/9266
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cca09a2a342980f427b590f2655d23c371386a02
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Dec 16 19:01:20 2014 +0530

    performance/readdir-ahead: indicate EOF for readdirp
    
    posix xlator sends op_errno as ENOENT and op_ret as 0, to indicate readdir has
    been completed. readdir-ahead should send that op_errno that it has saved in the
    fd context, when it serves the readdir requests. Otherwise some xlators sitting
    above performance xlators such as snapview-client, which checks for end of
    readdir operation by checking op_ret to 0 and op_errno to ENOENT will not be
    able to identify end of readdir.
    
    Change-Id: Ib0835136c61cb1e0d7df933226c479c7db703a71
    BUG: 1174783
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9283
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 531e0a70ff7a7b87baf0a8886d1de880293c3fcb
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Dec 10 13:28:17 2014 +0100

    ec: Fix more mutex related coverity scan issues
    
    This patch solves CID 1257622.
    
    Change-Id: I95680c7de49cd84011d2ad38f02e5fad82e15c90
    BUG: 1170254
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9263
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 3abee447da0adcaba4d02f212deb0d45b5b7e2e7
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Dec 16 17:06:20 2014 +0100

    Regression test portability: ec.t
    
    This test unmount/remount the filesystem to invalidate cache,
    but this leads to timing problems on NetBSD. We can work them
    around without sleeping by remounting on another mount point.
    
    BUG: 1129939
    Change-Id: I10b3183e5e715053de162a6980af188710b607bb
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9285
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit e398f99d9ac7ca5c83004b814a4e8561916187f0
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Dec 17 10:41:05 2014 +0100

    telldir()/seekdir() portability fixes
    
    POSIX says that an offset obtained from telldir() can only be used
    on the same DIR *. Linux is abls to reuse the offset accross
    closedir()/opendir() for a given directory, but this is not portable
    and such a behavior should be fixed.
    
    An incomplete fix for the posix xlator was merged in
    http://review.gluster.com/8926
    This change set completes it.
    
    - Perform the same fix index xlator.
    - Use appropriate casts and variable types so that 32 bit signed
      offsets obtained by telldir() do not get clobbered when copied into
      64 bit signed types.
    - modify glfs-heal.c and afr-self-heald.c so that they do not use
      anonymous fd, since this will cause closedir()/opendir() between
      each syncop_readdir(). On failure we fallback to anonymous fs
      only for Linux so that we can cope with updated client vs not
      updated brick.
    - Avoid sending an EINVAL when the client request for the EOF offset.
      Here we fix an error in previous fix for posix xlator: since we
      fill each directory entry with the offset of the next entry, we
      must consider as EOF the offset of the last entry, and not the
      value of telldir() after we read it.
    - Add checks in regression tests that we do not hit cases where
      offsets fed to seekdir() are wrong. Introduce log_newer() shell
      function to check for messages produced by the current script.
    
    This fix gather changes from http://review.gluster.org/9047
    and http://review.gluster.org/8936 making them obsolete.
    
    BUG: 1129939
    Change-Id: I59fb7f06a872c4f98987105792d648141c258c6a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9071
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 466a6f37ebaaad746e2eae045ebd249e28673717
Author: vmallika <vmallika@redhat.com>
Date:   Thu Dec 11 11:18:03 2014 +0530

    uss/gluster: In SVS, check for entry-point in dict only if inode_ctx is
    not available
    
    Change-Id: I990487003b712bf4aed8f54291417965f301655e
    BUG: 1172430
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9265
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 15edbff0a6a8c339c663717a821665f663d7c874
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Dec 15 17:18:06 2014 +0530

    gfapi: use different name for GETSPEC callback than the one used by glusterfsd
    
    Change-Id: Ibd5be1e1080f9da4ac1fb9112538b3320ef2ff28
    BUG: 1174205
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9277
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 358576530c5503f251bc7f4c53cb04064a78aee6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 12 14:12:35 2014 +0100

    build: prevent double packaging of geo-replication and other scripts
    
    The regression-tests sub-package contains /usr/share/glusterfs/* instead
    of including only the needed files. This causes some of the scripts that
    are part of geo-replication to be packaged twice.
    
    BUG: 1169005
    Change-Id: Ib452e73f3c1775b252ab257aab852ad9af857e74
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9272
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 46f7fd66f7d77b3753c98e9e7c27ba6a5280db40
Author: Morten Johansen <morten@bzzt.no>
Date:   Thu Nov 6 12:05:24 2014 +0100

    Update admin_distributed_geo_rep.md
    
    Fixed typo
    
    Change-Id: If4281237394ed96b32ec2d6227827214908052cf
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/9268
    Reviewed-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1a048844117fe13af0b1eb70eab07d304a23a358
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Dec 9 23:20:18 2014 +0530

    features/snapview-client: handle fsync fop
    
    Change-Id: Idaf46bd7497266af837789b09a0c62698f56ee4e
    BUG: 1172262
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9258
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 09af313fe6b49b03501939dd9e46b783ca4b5416
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Dec 4 15:40:52 2014 +0100

    fuse: protect checking/modifying graph->used with a mutex
    
    While reviewing http://review.gluster.org/#/c/9060/ we noticed that fuse
    checks/modifies graph->used in a unlocked way. There is a potential race
    in case when fuse_graph_setup() gets called from two different threads
    (currently  unlikely, but poller/notify() might change in future?).
    
    In libgfapi we came to the conclusion that each glfs structure can be
    used to protect the checking/updating of graph->used. In fuse this would
    be the fuse_private_t with sync_mutex.
    
    BUG: 1170643
    Change-Id: If5ab5468d22fdb92cfb24a469f538f63f12baf78
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9237
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 12c15f47fe68bcf8b32f55f3ca42638fd4eda998
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sun Dec 7 16:57:54 2014 -0800

    build: FreeBSD 11-Current causes libtool to fail with '-shared'
    
    Thanks for Markiyan Kushnir <markiyan.kushnir@gmail.com> for
    reporting this
    
    Change-Id: I7f637295c7c2d54c33a4c16e29daf0b518874911
    BUG: 1111774
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/9251
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 9ca800392106201c555ff8d5e2bf7a77aa52234d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Dec 10 11:10:52 2014 +0100

    client_t: fix for potential NULL pointer dereference
    
    In case an error occurs, 'client' is free'd. The log message just before
    exiting the function should therefore not use the structure anymore.
    
    BUG: 789278
    Change-Id: I0848328b29585057cd037a5972c4e5f06a7f978b
    CID: 1226165
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9262
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit e679d6417d39a696126e3f7ede1f2f38afc6e44c
Author: Jan-Hendrik Zab <zab@l3s.de>
Date:   Thu Dec 4 23:41:09 2014 +0100

    Stop logrotate from complaining about missing files.
    
    Previously logrotate reported errors for files missing in
    "/var/log/glusterfs/geo-replication-slaves/*/*.log". Fixed by reordering
    directives in the example config.
    
    Change-Id: I7cdb9e0d82f08aa27d5e26664660204fdeb8e98e
    BUG: 1170825
    Signed-off-by: Jan-Hendrik Zab <zab@l3s.de>
    Reviewed-on: http://review.gluster.org/9264
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 757394c1d764955f0068dfaf10692ae2d56a2b94
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Aug 25 16:21:08 2014 +0530

    rpc/rpcsvc: add peername to log messages
    
    This would allow users/developers to associate rpc layer log messages
    to the corresponding connection.
    
    Change-Id: I040f79248dced7174a4364d9f995612ed3540dd4
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8535
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 0b293a95839a68005dd464526598a113b37b089b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 9 10:57:10 2014 +0530

    storage/posix: Set errno for xattrop failures
    
    Change-Id: I4d44068c8da5257227d62906ec18ae16f6ed6c02
    BUG: 1172477
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9261
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 1877c43a6530e92ef9dee52463ddc4216a703329
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Dec 9 12:24:38 2014 +0100

    nfs: prevent potential NULL dereference in mnt3_readlink_cbk()
    
    In case 'mres' is NULL, we jump to 'mnterr' where 'mres->req' will be
    used. This will cause a segmentation fault, which we really do not want.
    
    Change-Id: I01d6f3aa0343def54dcd4a5610001ff7d62c8834
    CID: 1256179
    BUG: 789278
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9257
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 7cfa31434eb132adc0ac5cba4dcde600897cd2eb
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Nov 28 18:08:53 2014 +0530

    features/snapview-client: handle readdir requests differently for samba
    
    * For samba export, the entry point is also added to the readdir response.
    
    Change-Id: I825c017e0f16db1f1890bb56e086f36e6558a1c2
    BUG: 1168875
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/9218
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ad1ed8006047e862810f43d818dc44534e953d91
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 5 14:35:08 2014 +0530

    cluster/afr: Associate the inode returned by inode_link() with corresponding entry
    
    Change-Id: Ic4436a64075a2615a2293cdfdf2ba6622827cafa
    BUG: 1129939
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9254
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ecb58c9a3f716a87da7174c1aa721561b18ad27b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Nov 28 17:54:52 2014 +0530

    api, glusterfsd: Cleanup upon failure in glusterfs_ctx_defaults_init()
    
    This got introduced due to 656711d935000c16. Coverity
    also picked this up as CIDs 1256176, 1256178, 1256180.
    
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Change-Id: If12fa0075634383975846181917a2f9650f790e3
    BUG: 789278
    Reviewed-on: http://review.gluster.org/9213
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 4aa63e28509eb47d293eddb4f61317d409598c23
Author: GauravKumarGarg <ggarg@redhat.com>
Date:   Fri Nov 28 12:02:20 2014 +0530

    glusterd: Coverity fix for string_overflow overrun
    
    In function glusterd_dump_peer() it is copying "input_key" into "key"
    buffer without checking the length which might cause string_overflow
    overrun. Similar problem with other coverity issue.
    With this fix it will copy "input_key" into "key" buffer by maximum
    length of buffer.
    
    Coverity CID: 1256171
    Coverity CID: 1256172
    Coverity CID: 1256174
    
    Change-Id: I4e092309d9503bd79ff82cf83ed5e8d758743453
    BUG: 1093692
    Signed-off-by: Gaurav Kumar Garg  ggarg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9208
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 6b83a658ede66ebbb0983f1e4a326fd12cc91c34
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon Dec 8 14:25:22 2014 +0530

    gfapi: new inode created in glfs_resolve_component even if inode is in inode table
    
    problem: USS allows split-brain file to be accessed while main volume
             gives I/O error.
    
    cause:
            AFR detects split-brain on lookup. It stores this information in
            inode context. open and readv fop checks this flag from inode context.
            open and readv fop fails if split-brain flag is set for the file.
    
            USS uses gfapi to access snapshot volume. During open call
            gfapi internally calls glfs_resolve_component. glfs_resolve_component
            generates a new inode even if inode is present for the file.
            Because of which afr_lookup acts on a new inode which does not
            contain the split-brain flag.
    
    Bug: 1171615
    
    Change-Id: I1b4fddf4bd3c734a319ecfae804a3439866d157c
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/9253
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit cd6ffa93dc2a3cb1fcc5438086aebc54f368c2e9
Author: Anoop C S <achiraya@redhat.com>
Date:   Wed Oct 29 09:12:46 2014 -0400

    libgfapi: Wait for GF_EVENT_CHILD_DOWN in glfs_fini()
    
    Whenever glfs_fini() is being called, currently no
    check is made inside the function to determine whether
    the child is already down or not. This patch will wait
    for GF_EVENT_CHILD_DOWN for the active subvol and
    then exits.
    
    TBD:
    Apart from the active subvol, wait for other CHILD_DOWN
    events generated through operations like volume set in
    future.
    
    Change-Id: I81c64ac07b463bfed48bf306f9e8f46ba0f0a76f
    BUG: 1153610
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/9060
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 92a293220117f896bfcc1950dabd5bb1bfae9965
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Fri Dec 5 19:46:53 2014 +0530

    rdma:vectored write fails for rdma.
    
    For rdma write with payload count greater than one
    will fail due to insuffient memory to hold the
    buffers in rpc transport layer. It was expecting
    only one vector in payload, So it can only able
    to decode the first iovec from payload, and the
    rest will be discarded.
    
    Thnaks to Raghavendra Gowdappa for fixing the
    same.
    
    Change-Id: I82a649a34abe6320d6216c8ce73e69d9b5e99326
    BUG: 1171142
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9247
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit fcdac758ad7b3dda9843f92597a15e4a30a3b746
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Dec 1 09:21:32 2014 +0100

    build: only install geo-rep scripts when enabled
    
    When geo-replication is not enabled, the related scripts should not get
    installed. EPEL-5 does not support geo-replication, and the installed
    but unpackaged scripts cause rebuilding for .el5 to fail.
    
    BUG: 1169005
    Change-Id: I1b6a352b73bd1ed1c5b330f54e26e81aed9a5a4e
    Reported-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9221
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 36236eecef55c710e1f11ba4a04fe01da67cab6a
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Nov 11 18:45:01 2014 +0100

    ec: Fix return errors when not enough bricks
    
    Changes introduced by this patch:
    
    * Fix an incorrect error propagation when the state of the life
      cycle of a fop returns an error.
    
    * Fix incorrect unlocking of failed locks.
    
    * Return ENOTCONN if there aren't enough bricks online.
    
    * In readdir(p) check that the fd has been successfully open by
      a previous opendir.
    
    Change-Id: Ib44f25a1297849ebcbab839332f3b6359f275ebe
    BUG: 1162805
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9098
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 318df520945a5d618f45a3a3f680e2b39a278375
Author: Jan-Hendrik Zab <zab@l3s.de>
Date:   Thu Dec 4 14:06:15 2014 +0100

    Fixed small typo in marker.c
    
    Change-Id: Iec89e7141f6ff3216355d8a6b971617e16df679b
    BUG: 1075417
    Signed-off-by: Jan-Hendrik Zab <zab@l3s.de>
    Reviewed-on: http://review.gluster.org/9238
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 80fa3559583ac2c45e4dda9a26272090cd72f1bb
Author: vmallika <vmallika@redhat.com>
Date:   Wed Dec 3 15:10:44 2014 +0530

    uss/gluster: Send success on parent lookup of entry-point
    
    When a lookup sent to snapview-server for entry-point directory
    protocol server first tries to resolve gfid of a parent directory.
    
    looking up the parent gfid from a latest snapshot can fail if the
    volume is a restored volume. As this gfid is already looked-up by
    snapview-client, we can return success for the parent gfid.
    
    Change-Id: Ic9b20561ef79b93032f07c3a81eae54a94e1747b
    BUG: 1162498
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9229
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5fdffa7164ffc5a798246411d065259b36658bc3
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Dec 5 11:16:07 2014 +0530

    cluster/afr: Eliminate locking in sh domain in metadata self-heal
    
    Change-Id: I9ef25a17c9a43ba06fac2ad3f7c18cb47de91537
    BUG: 1170913
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9240
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9a3d848e78425363246345a4cfb6783298e9f1b5
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Dec 1 11:00:44 2014 +0100

    ec: Temporary fix for quota.t
    
    This fix solves a problem with tests/basic/ec/quota.t that generates
    a segmentation fault in DHT.
    
    This is a temporary fix until bug #1167793 is solved.
    
    Change-Id: I8587e66a63375ba2b312e8c0bfa1dd0d94d4c19f
    BUG: 1129939
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9222
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 30ae004100067f52fe156098ffb215417db5559e
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Dec 3 16:42:31 2014 +0100

    ec: Fix mutex related coverity scan issues
    
    This patch solves 3 issues detected by coverity scan:
    
        CID1241484 Data race condition
        CID1241486 Data race condition
        CID1256173 Thread deadlock
    
    With this patch, inode lock is never acquired inside a region locked
    with fop->lock.
    
    Change-Id: I35c4633efd1b68b9f72b42661fa7c728b1f52c6a
    BUG: 1170254
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit ca2a3949715fb25862d1e34f9e65283287faa842
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Nov 25 09:54:29 2014 +0100

    ec: Fix incorrect value of EC_MAX_NODES
    
    EC_MAX_NODES was incorrectly calculated. Now the value if computed
    as the minimum between the theoretical maximum and the limit imposed
    by the Galois Field.
    
    Change-Id: I75a8345147f344f051923d66be2c10d405370c7b
    BUG: 1167419
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9193
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit bc91dd4de39ffd481a52b837f322f6782c14e9f1
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Fri Nov 7 12:12:19 2014 +0100

    ec: Fix self-healing issues.
    
    Three problems have been detected:
    
    1. Self healing is executed in background, allowing the fop that
       detected the problem to continue without blocks nor delays.
    
       While this is quite interesting to avoid unnecessary delays,
       it can cause spurious failures of self-heal because it may
       try to recover a file inside a directory that a previous
       self-heal has not recovered yet, causing the file self-heal
       to fail.
    
    2. When a partial self-heal is being executed on a directory,
       if a full self-heal is attempted, it won't be executed
       because another self-heal is already in process, so the
       directory won't be fully repaired.
    
    3. Information contained in loc's of some fop's is not enough
       to do a complete self-heal.
    
    To solve these problems, I've made some changes:
    
    * Improved ec_loc_from_loc() to add all available information
      to a loc.
    
    * Before healing an entry, it's parent is checked and partially
      healed if necessary to avoid failures.
    
    * All heal requests received for the same inode while another
      self-heal is being processed are queued. When the first heal
      completes, all pending requests are answered using the results
      of the first heal (without full execution), unless the first
      heal was a partial heal. In this case all partial heals are
      answered, and the first full heal is processed normally.
    
    * An special virtual xattr (not physically stored on bricks)
      named 'trusted.ec.heal' has been created to allow synchronous
      self-heal of files.
    
      Now, the recommended way to heal an entire volume is this:
    
        find <mount> -d -exec getfattr -h -n trusted.ec.heal {} \;
    
    Some minor changes:
    
    * ec_loc_prepare() has been renamed to ec_loc_update().
    
    * All loc management functions return 0 on success and -1 on
      error.
    
    * Do not delay fop unlocks if heal is needed.
    
    * Added basic ec xattrs initially on create, mkdir and mknod
      fops.
    
    * Some coding style changes
    
    Change-Id: I2a5fd9c57349a153710880d6ac4b1fa0c1475985
    BUG: 1161588
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9072
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 7319b01ffa3d4ff7b1405873c8caeaf8a1f7b5d6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Dec 4 07:20:35 2014 +0530

    protocol/server: No root-squash checks for self-heal pid
    
    Problem:
    Self-heal pid used to be -1 which was colliding with gsyncd. Gsyncd
    was not checked for root-squash authentication. Recently self-heal
    pid changed to -6, but root-squash authentication is not disabled
    for this.
    
    Fix:
    disable root-squash authentication for self-heal
    
    Change-Id: I93233d4ae681cb936d166b22992eb47c658ea977
    BUG: 1170407
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9231
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 469f25a9efa89c89231cddaf983cb7d449df0487
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Nov 20 22:42:37 2014 +0530

    features/index: closedir() if fd_ctx_set() fails in __index_fd_ctx_get.
    
    Change-Id: I9ab599cf4a90c2e285d63ec0f56af210709285b6
    BUG: 1166284
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/9168
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1eb11c7ca1eb153c579a127b0fe6c2d4b1bbc7c8
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Nov 26 11:40:15 2014 +0100

    Regression test portability: basic/afr/resolve.t
    
    Final test in basic/afr/resolve.t checks for a failure after
    breaking the backend. But since the tested file was accessed
    just before that operations, it may still be in kernel page
    cache. As a result, file read is handled by kernel cache and
    never sent to the filesystem, and the test is successful
    where it should have failed.
    
    Fix this by waiting 10s before reading the supposed-to-be-broken
    file.
    
    BUG: 1129939
    Change-Id: I97efc00bc8a5f954b1df786cdede468af8bf6485
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9075
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ae744a27602488239ef681510412d0c64607a87f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Dec 4 06:53:25 2014 +0100

    Regression test portability: stat
    
    Improve Linux stat emulation for BSD so that it can handle multiple
    files at once. This is required now tests/basic/afr/data-self-heal.t
    uses that syntax.
    
    BUG: 1129939
    Change-Id: I2720d0e8a0d4dedbb8d51fcde3586b4e7d8bb492
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9232
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 811abf66d158efa037f1314792f7c674a7640c50
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 1 10:08:53 2014 +0000

    heal: free leaked frames.
    
    'gluster v heal <VOLNAME> info` waits for about 10 seconds before printing the
    heal info and exiting.
    
    Problem: glfsh_process_entries() is not freeing the frames it created.
    Thus when glfs_fini() is called, it busy waits for 10 seconds for background
    frames to finish before returning error.
    
    Fix: Destroy the frames in that are created in glfsh_process_entries().
    
    Change-Id: I5484d1b7301a355b913ae9c15b8a62471036c755
    BUG: 1169335
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9224
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ac4c203bfb4c3ebe48a08ef695ee462ba9b5e2c7
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Fri Jun 27 16:28:52 2014 +0530

    Glusterfs/posix: Stack corruption in posix_handle_pump
    
    posix_handle_pump can corrupt the stack if the buffer
    passed to it is too small to hold the final path.
    
    Fix :
    Check if the buffer is sufficiently large to hold the new path
    component before modifying it. This will prevent the buffer
    overrun but the path returned will most likely have too many symbolic
    links causing subsequent file ops to fail with ELOOP.
    
    The callers of this function do not currently check the return value.
    The code needs to be modified to have all callers check the return
    value and take appropriate action in case of an error.
    
    Change-Id: I6d9589195a4b0d971a107514ded6e97381e5982e
    BUG: 1113960
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8189
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7a352c258d7608cbf105a66de880660d5fa3b850
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Nov 26 12:09:56 2014 +0000

    tests: change license of arequal-checksum.c to include GPL v2.
    
    In line with the licensing scheme of other files in the project.
    
    Change-Id: Ic4c7dfcd2f2ceaeda9ec05bd37de8ef49a1c6206
    BUG: 1168207
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/9203
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1a5a0e11f2098961eccb6e312be123b0061b6eb1
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Nov 26 12:17:08 2014 +0100

    ec: Change license
    
    Change-Id: Iae90ade2421898417b53dec0417a610cf306c44b
    BUG: 1168167
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9201
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cd9ed7bd85bb3e876ef825a0c312a91c2206cc39
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Nov 29 06:20:58 2014 +0100

    Regression test portability: stat(1)
    
    - Improve Linux stat(1) emulation for BSD: %t and %T should be 0 for non
      device nodes.
    - Remove what seems like a typo in entry-self-heal.t, which blocks in
      Linux stat(1) emulation for BSD.
    
    BUG: 1129939
    Change-Id: I7635aa105e6d309cdb74608bdaba4135c7c00dd4
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9217
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2ca5b712f93dde62aadbf34f954ad53089490ded
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Nov 30 18:26:17 2014 +0100

    Regression test portability: basic/file-snapshot.t
    
    - For some odd reason, setfattr(1) could fail on big-file just after
      it was created by touch(1). Add a test in between to wait for the
      file to be visible by ls(1).
    - After switching to a snapshot, the file content is still in kernel
      cache, and the old content may be readen for a few seconds after
      the snapshot switch. Use ( cd $M0 && umount $M0 ) to flush vnodes
      and therefore invalidate the cache.
    - Unmount the mount point at the end of the test for the cleanliness
      sake.
    
    BUG: 1129939
    Change-Id: I5a0d14db13e79323147761dfe50c41ae6a1cb844
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9220
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8261f0deb9bf75611135a6571bc4d9cef687ad37
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Fri Nov 28 15:24:46 2014 +0530

    uss: CIFS gives error while accessing .snaps directory
    
    CIFS sends getxattr call while accessing .snaps directory.
    snapview server should return ENODATA if getxattr is called
    on .snaps folder. Also flush on .snaps folder should be handled.
    
    Windows client sends and getxattr call on the parent folder
    of .snaps with a special key to get the real filename of a file.
    This is used by samba to do case insensitive check of files.
    
    Fixed few FreeBSD compilation error.
    
    bug: 1168875
    
    Change-Id: I74d5cb4419568c8ed8709ba6d1ddff0e41392204
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/9211
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 85fa19eef36c166287ba87597684d1e0b532add0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 21 08:50:23 2014 +0530

    tests: Data self-heal test cases
    
    Change-Id: I74d08797b791ea6649d9aba585996e9ec680e3f8
    BUG: 1128721
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8538
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit f5ef4d808724afe4ddd477b0c0e8b3eb985319db
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Nov 28 17:24:13 2014 +0530

    glusterd: use synclock_t for synchronizing concurrent '\op_sm\' invocations
    
        In glusterd_op_sm(), we lock and unlock the gd_op_sm_lock mutex.
        Unfortunately, locking and unlocking can happen in different threads
        (task swap will occur in handler call with use of synctasks).
    
        This case is explictely covered by POSIX: the behavior is undefined.
        http://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_mutex_lock.html
    
        When unlocking from a thread that is not owner, Linux seems to be fine
        (though you never know with unspecified operation), while NetBSD returns
        EPERM, causing a spurious error in tests/basic/pump.
    
        To fix this, we use synclock_t which was precisely meant for this.
        synclock is a pthread_mutex_t like synchronization object which uses the
        synctask handle for owner and is immune to the task being run on
        multiple threads during its lifetime.
    
    Change-Id: Idca15190d42f32a843088cc8236138f676377586
    BUG: 1129939
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/9212
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 24581a58e897a415dfcc96f65c41d82d0f1fb49a
Author: Petr Medonos <petr.medonos@etnetera.cz>
Date:   Mon Nov 17 12:37:25 2014 +0100

    mgmt/glusterd: Out of bounds access to fs_info struct
    
    Change-Id: Ifa0d4ac17f9da94660a7b7f567a0f07b5cec7aec
    BUG: 1164775
    Signed-off-by: Petr Medonos <petr.medonos@etnetera.cz>
    Reviewed-on: http://review.gluster.org/9138
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit eee41566697583f74784d9f9ff78651535d6eb91
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Nov 25 07:20:38 2014 +0530

    USS : fill proper uid and gid during a access call from nfs
    
    Problem : when an user tries to access a file/folder for which
    he does not have a proper permission required then fuse gives out
    a proper error "Permission denied", but nfs does not give out that
    error, rather he can access the file/folder. The reason being uid and
    gid of call frame stack takes a default value of uid and gid which
    point to root permission.
    
    Solution : Set a proper uid and gid during a access call from nfs
    
    Change-Id: Ib060706fde66ec7e60f242fab1f3e59122ed2245
    BUG: 1167580
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9194
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a93164cd2a7f7ec37cf30d52b1a73fdc211981c3
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Nov 24 08:24:24 2014 +0000

    glusterd/uss: Create rebalance volfile.
    
    Create a new rebalance volfile, which will not contain
    snap-view client translators, irrespective of the status
    of USS.
    
    This volfile, will be created and regenerated everytime
    the fuse-volfile is generated, and will be consumed
    by the rebalance process.
    
    Change-Id: I514a8e88d06c0b8fb6949c3a3e6dc4dbe55e38af
    BUG: 1164711
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9190
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 92242ecd1047fe23ca494555edd6033685522c82
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Nov 28 10:46:20 2014 +0530

    glusterd/uss: if snapd is not running, return success from glusterd_handle_snapd_option
    
    glusterd_handle_snapd_option was returning failure if snapd is not running
    because of which gluster commands were failing.
    
    Change-Id: I22286f4ecf28b57dfb6fb8ceb52ca8bdc66aec5d
    BUG: 1168803
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9206
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 4ad587a25ff218248f96696305d505c0d37c82f5
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Nov 28 12:03:24 2014 +0530

    glusterd: logging improvement in txn_opinfo getter/setter function
    
    There is a code path (__glusterd_handle_stage_op) where glusterd_get_txn_opinfo
    may fail to get a valid transaction id if there is no volume name provided in
    the command, however if this function fails to get a txn id in op state machine
    then its a serious issue and op-sm is impacted. From debugability aspect gf_log
    () can never give the consumer of this function, so logging these failures with
    gf_log_calling_fn is must here.
    
    Change-Id: I4937a9fb20cc6a747fd30dcd9fd4936398d0602a
    BUG: 1168809
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9207
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit a435f62853832d3b5a52ab20227399ea921fc8ce
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Nov 21 12:20:07 2014 +0530

    posix: remove duplicate dirfd calls in posix_opendir
    
    BUG: 1168910
    Change-Id: I285d352d20374bb3edee2db42d062d4724198425
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9186
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 45af6c5fc385f2c948bdb387585b3e0a41ccbcde
Author: Edward Shishkin <edward@redhat.com>
Date:   Mon Oct 27 21:35:16 2014 +0100

    Prevent metadata corruption in the race conditions between
    FOP->open() and FOP->link().
    
    Problem: crypt_open() modifies @local->format, which is used
    by crypt_link() to store the updated metadata string on disk.
    This results in metadata corruption.
    
    Fixup: Don't modify @local->format by FOP->open(). Instead
    modify a local copy, allocated in the low-level meta-data
    handler open_format_v1().
    
    Change-Id: I046bb39ddefc33afe59c8d3b1a2fa798298f8499
    BUG: 1157839
    Signed-off-by: Edward Shishkin <edward@redhat.com>
    Reviewed-on: http://review.gluster.org/8982
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dcbab25710aa60a22708a0de8c41735bfca06d07
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Nov 27 09:13:36 2014 +0100

    posix: Fix buffer overrun in _handle_list_xattr()
    
    In _handle_list_xattr() we test remaining_size > 0 to check that
    we do not overrun the buffer, but since that variable was unsigned
    (size_t), the condition would let us go beyond end of buffer if
    remaining_size became negative.
    
    This could happen if attribute list grew between the first
    sys_llistxattr() call that gets the size and the second sys_llistxattr()
    call that get the data. We fix the problem by making remaining_size
    signed (ssize_t). This also matches sys_llistxattr() return type.
    
    While there, we use the size returned by the second sys_llistxattr()
    call to parse the buffser, as it may also be smaller than the size
    obtained from first call, if attribute list shrank.
    
    This fixes a spurious crash in tests/basic/afr/resolve.t
    
    BUG: 1129939
    Change-Id: Ifc5884dd0f39a50bf88aa51fefca8e2fa22ea913
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9204
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c233d3e0414670546c6ff8edc65b761f86353ffc
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Nov 25 10:41:53 2014 +0100

    glupy: build fix if python and glusterfs prefix differ
    
    If python is installed in ${pythonprefix} and glusterfs
    in ${glusterfsprefix}, we have the following values:
    ${PYTHON}-config --prefix   => ${pythonprefix}
    $libdir                     => ${glusterfsprefix}/lib
    
    Using LDFLAGS="-L`${PYTHON}-config --prefix`/$libdir" we lookf for
    python libraries in ${pythonprefix}/${glusterfsprefix}/lib while
    we should be looking for ${pythonprefix}/lib
    
    Replacing $libdir by lib breaks bug 1159248, so let us look in both
    ${pythonprefix}/lib and ${pythonprefix}/$libdir
    
    BUG: 1129939
    Change-Id: I2fef1b795235d1543a0e5ac619c6c2d59127fb66
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9137
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit d6278602caabac85b49887dc45e83b3cadfeb19b
Author: vmallika <vmallika@redhat.com>
Date:   Thu Nov 27 18:38:59 2014 +0530

    gluster/uss: Handle notify in snapview-client
    
    As there are two subvolumes in snapview-client, there is
    a possibility that the regular subvolume is still down and
    snapd subvolume come up first. So if we don't handle this situation
    CHILD_UP event will be propagated upwards to fuse when regular subvolume
    is still down. This can cause data unavailable for the application
    
    Change-Id: I9e5166ed22c2cf637c15db0457c2b57ca044078e
    BUG: 1168643
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9205
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9ff09ed29cd6659c82f6dc6f9c3f17b570b97697
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 1 10:58:19 2014 +0530

    tests: entry self-heal test cases
    
    Change-Id: I9390bc9274eb2485af541c4044bac12e48c44064
    BUG: 1128721
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8539
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 51eaed7fb243a989fdf96461ba2d9acfc07977f8
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Nov 26 09:59:25 2014 +0100

    Regression test portability: batch of bugs (volume 2)
    
    Fix various regression test portability in tests/bugs.
    
    bug-861542.t
    - Avoid syntax specific to GNU sed.
    
    bug-860663.t
    - Command argument length is system dependent, and specifying 1000 file
      path may overflow it. Use a C program to do the job in a portable and
      efficient way.
    - Add a test that we created the specified amount of files.
    
    bug-858242.c, bug-808400-fcntl.c, bug-808400-flock.c
    - fstat64() is Linux-specific. Define it as fstat for other systems.
    
    bug-823081.t
    - Use portable tail -n instead of tail --lines
    
    In many tests:
    - Do not assume python interpreter name. Use $PYTHON as defined
      in env.rc by configure.
    
    utils/libcxattr.py
    - If python version is 2.6 or higher, use a portable mechanism to
      recover errno. The original version is retained for python version
      2.5 and earlier but it only works on Linux.
    
    BUG: 1129939
    Change-Id: If2fea1ffec5cc6ab2de426fb200e884450afe61b
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9097
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c147c36a70505ff239cef48030422840abd3fbcd
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jun 18 14:46:05 2014 -0400

    core: fix remaining *printf formation warnings on 32-bit
    
    This fixes a few lingering size_t problems. Of particular note are
    some uses of off_t for size params in function calls.
    
    There is no correct, _portable_ way to correctly print an off_t. The
    best you can do is use a scratch int64_t/PRId64 or uint64_t/PRIu64.
    
    Change-Id: I86f3cf4678c7dbe5cad156ae8d540a66545f000d
    BUG: 1110916
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8105
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6c5b74c66cc0eb10edf5e4d3a726c7efddb5842c
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Tue Sep 23 23:05:16 2014 +0530

    doc: Avoid duplicate rdma notes.
    
    Change-Id: I5ede0ffad3870d8d86cb5d551ce188c649b04b44
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8826
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7f7dabd7d0df82678e2977002b3d1068ae283dce
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Aug 26 12:57:59 2014 +0530

    extras: geo-rep: Customize the generate gfid script to dirs list
    
    generate-gfid-file.sh now accepts dirs list file and generate
    gfids only for those dirs list.
    
    Change-Id: Ia78a0a744dc8a079db56c38578cc6fcac2a6fa90
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8540
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8f07191a4ab312c8b99e2eb08c7a1fc7e2c5eff2
Author: Poornima Gurusiddaiah <pgurusid@redhat.com>
Date:   Tue Jul 1 14:38:54 2014 +0530

    dict: Remove the redundant hash calculation when the hash size is 1
    
    Currently the dict is created with hash size 1, i.e. there is
    only one hash bucket and the calculation of hash decomes redundant.
    
    Change-Id: Id70aea0d798902494ebb6d82955d97d591bc73d2
    BUG: 789278
    Signed-off-by: Poornima Gurusiddaiah <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/8211
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8277f4e4a4e92543ac139ef63d0ad82add397de7
Author: vmallika <vmallika@redhat.com>
Date:   Thu Nov 20 20:36:00 2014 +0530

    gluster/uss: Handle ESTALE in snapview client  when NFS server restarted
    
    When NFS server is restarted inode-context is lost.
    Nameless lookup will be sent to regular volume.
    If the gfid is from virtual graph, lookup will fail
    with ESTALE. We need to send a lookup to snapview server
    
    Change-Id: I22920614f0d14cb90b53653fce95b6b70023eba6
    BUG: 1166197
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9153
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ff9ffab7b4e991de6191f10909c32a7a08f20ada
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 13 22:39:44 2014 +0530

    dict: Write dict_foreach_* in form of dict_foreach_match
    
    Change-Id: Iaa3454f7f3b6516660b1976bea63e39ea7795f8f
    BUG: 1164051
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9121
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4ea5b8d2046b9e0bc7f24cdf1b2e72ab8b462c9e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jun 13 11:09:25 2014 -0400

    core: fix Ubuntu code audit (cppcheck) results
    
    See also http://review.gluster.org/#/c/7693/, BZ 1091677
    
    AFAICT these are false positives:
    
    [geo-replication/src/gsyncd.c:100]: (error) Memory leak: str
    [geo-replication/src/gsyncd.c:403]: (error) Memory leak: argv
    [xlators/nfs/server/src/nlm4.c:1201]: (error) Possible null pointer dereference: fde
    [xlators/cluster/afr/src/afr-self-heal-common.c:138]: (error) Possible null pointer dereference: __ptr
    [xlators/cluster/afr/src/afr-self-heal-common.c:140]: (error) Possible null pointer dereference: __ptr
    [xlators/cluster/afr/src/afr-self-heal-common.c:331]: (error) Possible null pointer dereference: __ptr
    
    Test program:
    
    [extras/test/test-ffop.c:27]: (error) Buffer overrun possible for long command line arguments.
    [tests/basic/fops-sanity.c:55]: (error) Buffer overrun possible for long command line arguments.
    
    the remainder are fixed with this change-set:
    
    [cli/src/cli-rpc-ops.c:8883]: (error) Possible null pointer dereference: local
    [cli/src/cli-rpc-ops.c:8886]: (error) Possible null pointer dereference: local
    [contrib/uuid/gen_uuid.c:369]: (warning) %ld in format string (no. 2) requires 'long *' but the argument type is 'unsigned long *'.
    [contrib/uuid/gen_uuid.c:369]: (warning) %ld in format string (no. 3) requires 'long *' but the argument type is 'unsigned long *'.
    [xlators/cluster/dht/src/dht-rebalance.c:1734]: (error) Possible null pointer dereference: ctx
    [xlators/cluster/stripe/src/stripe.c:4940]: (error) Possible null pointer dereference: local
    [xlators/mgmt/glusterd/src/glusterd-geo-rep.c:1718]: (error) Possible null pointer dereference: command
    [xlators/mgmt/glusterd/src/glusterd-replace-brick.c:942]: (error) Resource leak: file
    [xlators/mgmt/glusterd/src/glusterd-replace-brick.c:1026]: (error) Resource leak: file
    [xlators/mgmt/glusterd/src/glusterd-sm.c:249]: (error) Possible null pointer dereference: new_ev_ctx
    [xlators/mgmt/glusterd/src/glusterd-snapshot.c:6917]: (error) Possible null pointer dereference: volinfo
    [xlators/mgmt/glusterd/src/glusterd-utils.c:4517]: (error) Possible null pointer dereference: this
    [xlators/mgmt/glusterd/src/glusterd-utils.c:6662]: (error) Possible null pointer dereference: this
    [xlators/mgmt/glusterd/src/glusterd-utils.c:7708]: (error) Possible null pointer dereference: this
    [xlators/mount/fuse/src/fuse-bridge.c:4687]: (error) Uninitialized variable: finh
    [xlators/mount/fuse/src/fuse-bridge.c:3080]: (error) Possible null pointer dereference: state
    [xlators/nfs/server/src/nfs-common.c:89]: (error) Dangerous usage of 'volname' (strncpy doesn't always null-terminate it).
    [xlators/performance/quick-read/src/quick-read.c:586]: (error) Possible null pointer dereference: iobuf
    
    Rerunning cppcheck after fixing the above:
    
    As before, test program:
    
    [extras/test/test-ffop.c:27]: (error) Buffer overrun possible for long command line arguments.
    [tests/basic/fops-sanity.c:55]: (error) Buffer overrun possible for long command line arguments.
    
    As before, false positive:
    
    [geo-replication/src/gsyncd.c:100]: (error) Memory leak: str
    [geo-replication/src/gsyncd.c:403]: (error) Memory leak: argv
    [xlators/nfs/server/src/nlm4.c:1201]: (error) Possible null pointer dereference: fde
    [xlators/cluster/afr/src/afr-self-heal-common.c:138]: (error) Possible null pointer dereference: __ptr
    [xlators/cluster/afr/src/afr-self-heal-common.c:140]: (error) Possible null pointer dereference: __ptr
    [xlators/cluster/afr/src/afr-self-heal-common.c:331]: (error) Possible null pointer dereference: __ptr
    
    False positive after fix:
    
    [xlators/performance/quick-read/src/quick-read.c:584]: (error) Possible null pointer dereference: iobuf
    
    Change-Id: I20e0e3ac1d600b2f2120b8d8536cd6d9e17023e8
    BUG: 1109180
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8064
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c6f27ed5cc9a6fafc6e6f83aff00196bc7a49d38
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Nov 20 14:06:03 2014 +0530

    cli: .cmd_log_history should not be hidden
    
    Change-Id: I4513a2c260530855e09be64083e9344108c7a6c0
    BUG: 1165996
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9150
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 6600744dd1ade619685502f4d01d708acd95d8e8
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Nov 21 10:37:52 2014 +0530

    tests: mgmt_v3_locks.t fix
    
    this patch fixes a small issue introduced by http://review.gluster.org/#/c/9114/
    
    Change-Id: I42a91544fad2b5f8af70670e4c4cadcac094dd05
    BUG: 1163543
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9171
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: 长财 余 <einstcrazy@gmail.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 69d4b53380e3fe10edd94cba22a36f5a5f303348
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Nov 20 11:58:16 2014 +0100

    Regression tests portability: Do not 'cd' into volume
    
    Changing current directory to the root of the volume to
    execute tests from there keeps an open file descriptor
    to it that could interfere with some tests.
    
    I've removed all 'cd' and used abosulte paths on all
    tests.
    
    Change-Id: Ic54afb7d7974e9e80818201bcd99ee2b01d00442
    BUG: 1129939
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9151
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>

commit 66c789765d783bba8fe651e6a26feb5483af71a5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Nov 2 19:15:49 2014 +0100

    Replace copied (from rsync) checksum code by adler32() from zlib
    
    The weak checksum code that is included in libglusterfs has initialy
    been copied from the rsync sources. Instead of maintaining a copy of a
    function, we should use a function from a shared library. The algorithm
    seems to be Adler-32, zlib provides an implementation.
    
    The strong checksum function has already been replaced by MD5 from
    OpenSSL. It is time to also remove the comments about the origin of the
    implementation, because it is not correct anymore.
    
    Change-Id: I70c16ae1d1c36b458a035e4adb3e51a20afcf652
    BUG: 1149943
    Reported-by: Wade Mealing <wmealing@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9035
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit eb7a2f47bdee5048cfdaf2af149af5cfd7de4b10
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Tue Nov 18 14:58:20 2014 +0530

    rdma:Removing RDMA tech preview cli message.
    
    Creation of rdma and tcp,rdma volume will display a
    warning message since it was in tech preview. This
    patch will remove the warning message during the
    volume creation.
    
    Change-Id: I54f46097073bcb5a757ab047f540cd9b92553897
    BUG: 1164079
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9141
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 0dd772d13853ad862270dea74ad671118ee51813
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Wed Nov 19 17:22:21 2014 +0530

    mount:Handle -o transport option in mount.glusterfs
    
    In current scenario ,when tcp transport type(default)
    specified for mounting,glusterfs mount script won't
    append '.tcp' to volume name.But to accommodate the change
    in http://review.gluster.org/#/c/9146/, we need to
    append ".tcp" with volfile-id if '-o transport=tcp' is given.
    
    
    Change-Id: I506edeb339de062087f820f10e17c7d67b8b63fe
    BUG: 1164079
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9147
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: jiffin tony Thottan <jthottan@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 7d0bfc90027c824e6d49cba7c3c3dc818f9c365b
Author: GauravKumarGarg <ggarg@redhat.com>
Date:   Mon Nov 17 12:50:49 2014 +0530

    glusterd: Add hostname/ip-address along with host's UUID in glusterd log message
    
    Previously when host disconnected from cluster then glusterd logs
    identifies host using host's UUID.
    
    Now with this fix, UUID along with host's ip will be present in
    glusterd log message when one of the peer disconnected from cluster.
    So it will enhancement better readability of user from log file.
    
    Change-Id: I3b7eaf1b1a8963ef2096e67a78cf69f67d5d5166
    BUG: 1101382
    Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/9136
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 6ba258d2b7d4520af95ff638e02598e4aa247ec4
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Nov 20 16:26:36 2014 +0100

    pkg-config: make the version in gluster-api.pc backwards compatible
    
    Once we released gluster-api.pc with version=4. Since then we undid the
    library versioning and replaced it with symbol-versioning. The current
    libgfapi.so has version 0, but the symbols have the version from the
    main package at the time they were added.
    
    Because other packages (like samba) use the pkg-config version, we can
    not drop it, or decrease the version easily. The simplest solution is to
    keep the version=4 and add sub-digits for the actual package/symbol
    versions. In future, the version in gluster-api.pc will be like 4.3.x.y.
    
    Change-Id: If359c8de5b847a7e818199a7246636113837da2d
    BUG: 1166232
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9154
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9797bd197d48ca17a124c245295937ac3d48ab58
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 16 12:29:03 2014 -0400

    core: use gf_time_fmt() instead of localtime()+strftime()
    
    gf_time_fmt() has existed since 3.3; it provides consistent timestamps
    (i.e. UTC times) throughout the implementation. (BTW, the other name for UTC
    is GMT.)
    
    N.B. many (all?) commercial storage solutions use UTC time for logging.
    This makes for easier debugging across geographically distributed systems.
    
    Also adding a "%s" fmt for portably printing time as simple numeric
    value on systems regardless of whether 32-bit or 64-bit time_t. Plus a
    minor tweak to return a ptr to the dest-string to allow gf_time_fmt()
    to be passed as a param in a *printf().
    
    Someday we should pick the "one true" timestamp format and revise all
    calls to gf_time_fmt() to use it instead of the five or six different
    formats.
    
    Change-Id: I78202ae14b7246fa424efeea56bf2463e14abfb0
    BUG: 1109917
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8085
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 27c2be4af6f2dc0a18410e17862bb5d3a07231f3
Author: vmallika <vmallika@redhat.com>
Date:   Tue Nov 18 17:23:06 2014 +0530

    tests: spurious failure fix for bug-1164613.t
    
    Snapshot bricks are started asynchronously.
    It might take sometime before accessing the file.
    
    
    Change-Id: I62633974eca21f86632f7005ce6fd5c856b8be90
    BUG: 1163543
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9142
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 720e2c0df7bbf2d3daed20cadd5f3f710576a05c
Author: Anoop C S <achiraya@redhat.com>
Date:   Wed Nov 19 16:27:05 2014 +0530

    rdma: Client volfile name change for supporting rdma
    
    For rdma only volumes, daemons like snapd, glustershd
    etc make use of tcp transport for their operations.
    This patch will introduce the support of rdma by default
    for those daemons in rdma only volumes. In order to
    accomodate this change we rename the tcp client volfile
    labels from
    <volname>-fuse.vol
    to
    <volname>.tcp-fuse.vol
    
    Change-Id: Id9727b97d00e62a4a1556b9c0c56653d45c8fe1d
    BUG: 1164079
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/9146
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 33800b332ec7aa70fa14809c1030cfabaddc02a0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Nov 15 23:30:31 2014 +0100

    md-cache: check mtime_nsec and ctime_nsec fields for changes too
    
    When md-cache checks for an updated mtime/ctime in order to see if it
    should request a cache invalidation, it only looks at the whole-second
    "mtime" and "ctime" fields. If a file was modified a fraction of a
    second after the time of the cached data, md-cache won't notice the
    change.
    
    BUG: 1164506
    Change-Id: Ieb7baa46f84489d2d7ea8d60a7fb2595564eb955
    Original-author: Philip Spencer <pspencer@fields.utoronto.ca>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9131
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 83a4cdaa1972a16603e19916e093674b60680bb0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Nov 15 22:44:09 2014 +0100

    md-cache: cache the iatt when readv() was successful
    
    When md-cache is handling a readv callback, its logic is to skip
    checking the file's iatt (to see if it has changed since the time of the
    last cache) if "op_ret != 0".
    
    This is a mistake, and the intent was to skip only on error; for other
    fops, op_ret is 0 on success and nonzero on error, and md-cache has the
    same code for them.
    
    For readv, though, op_ret is the number of bytes read, so it will
    normally be positive except on EOF.
    
    BUG: 1164503
    Change-Id: Ifc0f2084b41b6f8d075a9260dc7cf69e97535eed
    Original-author: Philip Spencer <pspencer@fields.utoronto.ca>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9129
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4fbc86993a0b0e67bcf58b4882d9d86a8b8ba65a
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Nov 17 15:52:28 2014 +0100

    Regression tests portability: basic/ec/self-heal.t
    
    When checking for bricks availability, use ls -l produces a more reliable
    result than just ls.
    
    BUG: 1129939
    Change-Id: Ided548a8f4154714d2c33ec538d0623d7c328952
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9133
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>

commit 463d3e379d63e37764bc190be6c2f790769bea58
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Nov 13 07:03:54 2014 +0530

    tests: spurious failure fix for quota-anon-fd-nfs.t
    
    Change-Id: I4f7ee68c514d8d322e25cf74167f288a8b6f8164
    BUG: 1163543
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9108
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit f380e2029d608f97e3ba9a728605e1d798b09e8d
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Oct 21 08:59:46 2014 -0400

    rdma :mount fails for nfs protocol in rdma volumes
    
    When we mount rdma only volume or tcp,rdma volume using newly
    peer probed IP's(nfs-server on new nodes) through nfs protocol,
    mount fails for rdma only volume and mount happens with
    help of tcp protocol in the case of tcp,rdma volumes. That is for
    newly added servers will always get transport type as "socket".
    This is due to nfs_transport_type is exported correctly and
    imported wrongly.
    
    This can be verified by the following ,
       * Create a rdma only volume or tcp,rdma volume
       * Add a new server into the trusted pool.
       * Checkout the client transport type specified nfs-server
         volgraph.It will be always tcp(socket type) instead of rdma.
       * And also for rdma only volume in the nfs log, we can see
         'connection refused' message for every reconnect between
         nfs server and glusterfsd.
    
    BUG: 1157381
    
    Change-Id: I6bd4979e31adfc72af92c1da06a332557b6289e2
    Author:    Jiffin Tony Thottan <jthottan@redhat.com>
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/8975
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit b9bd3666ae094f54c5049d03c7907a9dff14503d
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Nov 13 06:59:41 2014 +0530

    tests: spurious failure fix in mgmt_v3_locks.t
    
    Change-Id: I7c4599648b5d47d93a447e58c063fab21e8f9ef7
    BUG: 1163543
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9114
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 4a3c36ba002eaf9e77c6d71180fcc7d0a415d69f
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Oct 30 10:35:57 2014 +0530

    rdma:client process will hang if server is started to send
    the request before completing connection establishment
    
    in rdma, client and server will interchange their available
    buffers during the handshake to post incoming messages.
    Initially the available buffer is set to one, for the first message
    during handshake,when first message is received, quota for
    the buffer will set to proper value. So before receiving the message
    if server started to send the message, then the reserverd buffer for
    handshake will be utilised, then the handshake will fail because
    of lack of buffers. So we should block sending messages by server
    before proper connection establishment.
    
    Change-Id: I68ef44998f5df805265d3f42a5df7c31cb57f136
    BUG: 1158746
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9003
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit c566e914a1ae84b18e20c917474be3028cd1b5de
Author: Anoop C S <achiraya@redhat.com>
Date:   Wed Nov 12 18:02:15 2014 +0530

    rdma: Wrong volfile fetch on fuse mounting tcp,rdma volume via rdma
    
    As of now for both tcp only volumes and rdma only volumes, volfile
    names are in the format <volname>-fuse.vol. This patch will change
    the client volfile namings as shown below.
    
     * TCP mounts always use <volname>-fuse.vol
     * RDMA mounts always use <volname>.rdma-fuse.vol
    
    Following the above naming convention, for tcp,rdma volumes both
    volfiles will be present under /var/lib/glusterd/vols/<volname>/
    such that rdma only volume can be mounted as
    
    mount -t glusterfs -o transport=rdma <server/ip>:/<volname> <mount-point>
    OR
    mount -t glusterfs <server/ip>:/<volname>.rdma <mount-point>
    
    The above command format can also be used to fuse mount a tcp,rdma
    volume via rdma transport.
    
    When we try to fuse mount a tcp,rdma volume with transport-type
    as rdma it silently mounts via tcp. This change will also make
    sure that it fetches the correct volfile based on the
    transport-type specified from client side.
    
    BUG: 1131502
    Change-Id: I34da4b01ac813b69494a43188f51145457412923
    Signed-off-by: Anoop C S <achiraya@redhat.com>
    Reviewed-on: http://review.gluster.org/8498
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 85e92d160bd71fdaeb3ae89d3440eec8fd438da9
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Oct 16 11:28:33 2014 +0530

    rdma: client connection establishment takes more time
    
    For rdma type only volume client connection establishment
    with server takes more than three seconds. Because for
    tcp,rdma type volume, will have 2 ports one for tcp and
    one for rdma, tcp port is stored with brickname and rdma
    port is stored as "brickname.rdma" during pamap_sighin.
    During the handshake when trying to get the brick port
    for rdma clients, since we are not aware of server
    transport type, we will append '.rdma' with brick name.
    So for tcp,rdma volume there will be an entry with
    '.rdma', but it will fail for rdma type only volume.
    So we will try again, this time without appending '.rdma'
    using a flag variable need_different_port, and it will succeed,
    but the reconnection happens only after 3 seconds.
    In this patch for rdma only type volume
    we will append '.rdma' during the pmap_signin. So during the
    handshake we will get the correct port for first try itself.
    Since we don't need to retry , we can remove the
    need_different_port flag variable.
    
    Change-Id: Ie8e3a7f532d4104829dbe995e99b35e95571466c
    BUG: 1153569
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/8934
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 43800dedb5f0b4644de913c3fd50c6b409ec7210
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Sep 18 04:21:04 2014 -0400

    rdma:rdma fuse mount hangs for tcp,rdma volumes if brick is down.
    
    When we try to mount a tcp,rdma volume as rdma
    transport using FUSE protocol, then mount will
    hang if the brick is down. When we kill a process,
    signal will be received in glusterfsd process and
    it will call pmap_signout with port listening on tcp only.
    In case of the tcp,rdma there will be two ports,
    and port which is listening for rdma will not
    called for sign out.
    So the mount process will try to connect to a port
    which is not open and it will keep trying to connect.
    This patch will call pmap_signout for rdma port also,
    So when mount tries to get the brick port,it will fail.
    
    Change-Id: I23676f65f96eb90b69b76478f7a21412a6aba70f
    BUG: 1143886
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/8762
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit cc57d9bee98270e6e961765716d421bf2f0950d3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Nov 15 23:07:04 2014 +0100

    changelog: correct mmap() error checking
    
    Upon failure, mmap() returns MAP_FAILED, which is not equal to NULL.
    This small correction makes sure that the potential error gets caught
    and handled.
    
    BUG: 1138621
    Change-Id: I0a88b5187afa7187dcaa8f7d2cb0f9bb775c929d
    Reported-by: Santosh Pradhan <santosh.pradhan@gmail.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9130
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit a7ec009499f2c8f0c96aa03110ff4755eef8f1b8
Author: Sachin Pandit <spandit@redhat.com>
Date:   Wed Nov 5 11:09:59 2014 +0530

    USS : Kill snapd during glusterd restart if USS is disabled
    
    Problem : When glusterd is down on one of the nodes and during that
    time if USS is disabled then snapd will still be running
    in the node where glusterd was down.
    
    Solution : during restart of glusterd check if USS is disabled,
    if so then issue a kill for snapd.
    
    NOTE : The test case which I wrote in my previous patchset
    is facing some spurious failures, hence I thought of removing
    that test case. I'll add the test case once the issue is resolved.
    
    Change-Id: I2870ebb4b257d863cdfc319e8485b19e932576e9
    BUG: 1161015
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9062
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 85c4aa0615f161a9ff1c6b58a82b5a652eb83c43
Author: vmallika <vmallika@redhat.com>
Date:   Mon Nov 17 07:14:28 2014 +0530

    gluster/uss: Don't send failure when accessing snap with name
    same as entry-point name
    
    In a scenario, if the snap name is same as the snap-directory than cd to
    snaps/snaps fails.
    Send a lookup to snap-view server instead of failing
    
    Change-Id: Ie7b811815ff30961500592bbc8cdb514a9d76ef5
    BUG: 1164613
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9135
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit dfc49143841fe84f846346a30dadce797940eebc
Author: Shyam <srangana@redhat.com>
Date:   Thu Nov 6 10:43:37 2014 -0500

    cluster/dht: Fix subvol check, to correctly determine cached file rename
    
    The check to treat rename as a critical failure ignored when the cached
    file is being renamed to new name, as the new name falls on the same
    subvol as the cached file. This is in addition to when the target of the
    rename does not exist.
    
    The current change is simpler, as the rename logic, renames the cached
    file in case the target exists and falls on the same subvol as source
    name, OR the target does not exist and the hash of target falls on the
    same subvol as source cached. These conditions mean we are renaming the
    source, other conditions mean we are renaming the source linkto file
    which we do not want to treat as a critical failure (and we also instruct
    marker that it is an internal FOP and to not account for the same).
    
    Change-Id: I4414e61a0d2b28a429fa747e545ef953e48cfb5b
    BUG: 1161156
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9063
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: susant palai <spalai@redhat.com>
    Reviewed-by: venkatesh somyajulu <vsomyaju@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 73be0be8149398b68213cb158cf94313169b5006
Author: Rudra Siva <rudrasiva11@gmail.com>
Date:   Sun Nov 16 08:37:40 2014 -0500

    client: writev,fsync to use correct rsp structure
    
    Presently writev_cbk and fsync_cbk pass truncate_rsp for decoding, this
    should not create any problems as they are structurally the same. Should
    they diverge in the future this could show up as a bug.
    
    Change-Id: Id7da7b6a20f468ca943ceb7926de64b7692f7ec8
    BUG: 1164559
    Signed-off-by: Rudra Siva <rudrasiva11@gmail.com>
    Reviewed-on: http://review.gluster.org/9134
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2be53848801a2e8afefdafd1acc821615cbbe343
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jul 10 07:30:42 2014 -0400

    client: pass xflags for unlink
    
    Nobody seems to use these currently, but I tried to for some debugging,
    and that led to a few head-scratches before I figured out that it wasn't
    being passed across the server/client boundary.  Might as well fix it
    before somebody tries to use it for real and has to go through the same
    exercise.
    
    Change-Id: Ieddfac106103db02fdf488c86f3f979d29a6ab83
    BUG: 1158614
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8287
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 656711d935000c161012c25340dbd65a59999dc3
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Fri May 9 15:30:04 2014 +0530

    mem_acct : Check return value of xlator_mem_acct_init().
    
    some code does not check xlator_mem_acct_init()
    return, thus fails to capture wrong memory accounting
    initialization. This patch fix the same.
    
    Change-Id: I01eab19d6cef472afd850b0f964132c01523492a
    BUG: 1123768
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/7728
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 8c4ae34f8803f44f2f1e459883581a953bca42ec
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Nov 13 13:55:36 2014 +0100

    ec: Avoid self-heal on directories on (f)stat calls
    
    To avoid inconsistent directory listings, a full self-heal
    cannot happen on a directory until all its contents have
    been healed. This is controlled by a manual command using
    getfattr recursively and in post-order.
    
    While navigating the directories, sometimes an (f)stat fop
    can be sent. This fop caused a full self-heal of the directory.
    
    This patch makes that (f)stat only initiates a partial self-heal.
    
    Change-Id: I0a92bda8f4f9e43c1acbceab2d7926944a8a4d9a
    BUG: 1163760
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/9117
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dfd3624ff6362ac58f57f9dd25c426dbfe488661
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 21 13:29:07 2014 -0400

    doc: update rebalance doc, add SSL/TLS doc
    
    Change-Id: I5d21aabaa6bfa6de40459c9a1969832a0a5d75e1
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8961
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fdef42e82d66011a3a92c9c96db4ada2fa8d4814
Author: jiffin <jthottan@redhat.com>
Date:   Tue Nov 4 20:33:01 2014 +0530

    gNFS : make it possible to mount a subdir that actually is a symlink
    
    We are using the function to export all sub-directories in a gluster volume via nfs.
    For real directories it works fine but if we have a symbolic link which points to the
    directory, it is not possible to mount that directory via nfs and the nameof the link.
    Kernel nfs resolves symlink handle to directoryhandle , similar gluster nfs should
    resolve the symbolic link handle into directory handle.
    
    Change-Id: I8bd07534ba9474f0b863f2335b2fd222ab625dba
    BUG: 1157223
    Signed-off-by: jiffin tony thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/9052
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit c3dc90b53558316904985932490584402aaef48d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Nov 12 12:02:44 2014 +0000

    uss/snapd: Handle readlink fops on snap view server
    
    Handle readlink fops in case of symlinks on
    snap view server
    
    BUG: 1162462
    Change-Id: Ia08e9e9c1c61e06132732aa580c5a9fd5e7c449b
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/9102
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f645655c65d1f9787a82a5dcbb0e24e2d32bed87
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Mon Oct 13 11:12:14 2014 +0530

    rdma: glusterd crash if rdma_disconnect is called as soon as connect a request.
    
    we are initializing connection in server side immediately after
    rdma_accept is called. But we are delaying adding the transport
    to listener list until getting RDMA_CM_EVENT_ESTABLISHED event.
    Before getting this event if disconnect is called glusterd will
    try to remove the transport from list which is not added. So if
    the list is empty it causes a glusterd crash . In this patch we
    will call the function to initialize the connection as soon as
    rdma_accept is called.
    
    Change-Id: I019480297a85349ede3101ee9c7c1596dc5c73e2
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    BUG: 1164079
    Reviewed-on: http://review.gluster.org/8925
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit c3c28ad86be6feb0b148df4681da432047dc0bc3
Author: vmallika <vmallika@redhat.com>
Date:   Fri Nov 14 12:06:39 2014 +0530

    mgmt/glusterd: Validate the options of uss
    
    Change-Id: Id13dc4cd3f5246446a9dfeabc9caa52f91477524
    BUG: 1111554
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8133
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 3e0a9c04ed86153a2822b92d69b31e20ef5c63f6
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Nov 14 12:06:39 2014 +0530

    posix:  Changed order of chown and chmod
    
        Problem:
        Rebalance process runs in the root mode. If a normal
        user create a file and if it  requires migration then
        because the migrated file is created by root, its owner and
        mode should  be changed to the source normal user and
        permission should be changed the previous mode. If
        the suid bit is also set, then at the destination
        suid bit should also be set.
    
        Two operations are performed in the given order:
        1. chmod
        2. chown
    
        But chown resets the suid bit. So changed the order
        of these two operations so that first chown will be
        performed and then chmod will be performd so that
        suid bit will be preserved.
    
    Change-Id: Ib63b5cf528f8336b69bf090ad43bb02eec1d1602
    BUG: 1086228
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/7435
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7c9e95f1876ca0d209509358e6d4e58c910dd71e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Nov 12 12:15:11 2014 +0530

    cli : Maintain separate cli log file per cli instance for cluster regression tests
    
    Change-Id: I7f49f4999d997b99c103fd67d13f972937e3aa92
    BUG: 1162987
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9100
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 21282c0a7bf2783c8845335fe4834b043689ef0d
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Sep 18 11:47:23 2014 +0530

    gfapi: Change lookup logic for "/.." and "/." .
    
    We should handle /.. and /. in unique way,
    otherwise we may end up setting glusterfs xattrs
    on parent of the brick dir.
    
    Change-Id: I206bb1751622bd912bc678fd52f4eddfd9b907c8
    BUG: 1128648
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8455
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa0ba671f3e64858b9c93571383f2a0452eddf26
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Nov 8 06:59:47 2014 +0100

    Regression test portability: wc
    
    NetBSD wc displays number with leading spaces, which cause arithmeric
    operations on values from wc -l to fail.
    
    Fix the problem by defining a wrappers that removes spaces.
    
    BUG: 1129939
    Change-Id: I6fa147cf07772f58d9e19e0efd1dae5dad3a4219
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9076
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a537342633707544c645cba0c3d46f2180c3b570
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Nov 4 15:56:36 2014 +0100

    Portability fix: mount.glusterfs
    
    Remove bash-specific syntax from mount.glusterfs
    
    BUG: 1129939
    Change-Id: Iec3a52686f7cee1825ac5a06c11fb8ac4d3e5d65
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9044
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 77a6917a650a88c12b6c27d37994f8bfef461345
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Nov 4 20:53:24 2014 +0100

    Build fix: xdrgen
    
    As discovered in https://review.gluster.org/8762, BSD systems fail to
    run xdrgen during glusterfs build. This seems to be caused by a
    difference between BSD make and GNU make whith implcit targets. The
    former seems to use absolute path here, which means we should not
    prepend it with the current directory path, otherwise we have the
    directory path twice and the files cannot be found my make.
    
    This is a second attempt after I178123bf6f3d9e963ff5b78839d498f530c05a97
    which was broken and reverted in I3c8966288f66d0eafa2e94490e3b64a057b4f2c0
    
    BUG: 1157839
    Change-Id: I797c536c319a156b71a42c82cbaf80bbf17b7234
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9046
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f6b9f295043d6a7f69e39fde0979b786471e6f92
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Oct 30 11:46:56 2014 +0530

    rdma:setting rdma REUSEADDR flag to rdma id.
    
    When we restart the process, it will go TIME_WAIT state to make sure that
    all the data in the transport is successfully delivered. REUSEADDR
    allows server to bind to an address which is in TIME_WAIT state.
    
    Change-Id: Ic7deb0d7442c29494fe088598ffe9c87977c04ff
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/9005
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit f3f7f2a2048359db67875a54a96dbf5a46f7bff3
Author: vmallika <vmallika@redhat.com>
Date:   Thu Nov 13 07:11:00 2014 +0530

    glusterd/snapshot: Don't append nouuid mount option for snapshot brick
    if original brick already has this option
    
    Change-Id: I2841d2ac371a3e9505f6061f35d1d447946c0bae
    BUG: 1133456
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8526
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 878b30420891c8b00043391cdce90930eaf18795
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Mon Nov 10 15:20:51 2014 +0530

    gNFS: Allow reading ACLs even without read permissions on the file.
    
    When root-squash is enabled or when no permissions are given to
    a file, NFS threw permission errors. According to the kernel-nfs
    behaviour, no permissions are required to read ACLs.
    
    When no ACLs are set, the system call sys_lgetxattr fails and
    returns a ENODATA error. This translates to ESERVERFAULT error
    in NFS. Fuse makes an exception to this error and returns a success
    case. Similar changes are made here to achieve the expected behaviour.
    
    Change-Id: I46b8f5911114eb087a3f8ca4e921b6b41e83f3b3
    BUG: 1161092
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9085
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b4597a92ccfebf362c63977bc4bada7b65e28753
Author: vmallika <vmallika@redhat.com>
Date:   Thu Nov 13 15:13:39 2014 +0530

    uss/gluster: creating file/directories inside .snaps should fail with
    EROFS
    
    When an attempt is made to create file/directories inside .snaps, it
    fails with wrong error message as "Stale file handle". It should fail
    with "Read-only file system"
    
    Change-Id: I3a812a0afc4762cbb71ab180b9394c866e576a66
    BUG: 1159840
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9039
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 75474f148daada475c235d0acaf345acad4ba9f3
Author: Sachin Pandit <spandit@redhat.com>
Date:   Thu Nov 13 03:57:57 2014 +0530

    test/uss : activate the snapshot after creating.
    
    Till now we were activating the snapshot along with the snapshot create.
    But one of the recent patches has changed that behavior. Now we have
    to explicitly issue activate-on-create using snapshot config if we
    want snapshot to be activated during snapshot create.
    
    Till patch fixes the regression failure which is seen lately.
    
    Change-Id: Ic53b16e22569e521bd70dd3bfa7154a0424151ce
    BUG: 1155042
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/9113
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit b6c553339ca0d14dc8d66ccc5d8d8db2be1dd14f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Nov 1 13:05:08 2014 +0100

    build: fix glupy linking warnings
    
    While building glupy on x86_64, the following warnings are thrown:
    
      Making all in glupy
      Making all in src
        CC     glupy.lo
        CCLD   glupy.la
      /usr/bin/ld: skipping incompatible /usr/lib/libdl.so when searching for -ldl
      /usr/bin/ld: skipping incompatible /usr/lib/libutil.so when searching for -lutil
      /usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
      /usr/bin/ld: skipping incompatible /usr/lib/librt.so when searching for -lrt
      /usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching for -lpthread
      /usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
    
    The libraries to link against are in /usr/lib64 on x86_64 in Fedora,
    RHEL and CentOS. Other architectures or distributions may use a
    different path. Instead of hardcoding "/lib" in configure.ac, the
    variable $libdir should be used so that the path gets adapted to the
    distribution and architecture.
    
    Change-Id: Iae5db3ee8a62959ccb7f958d7c95eb77c4d4b1dd
    BUG: 1159248
    Reported-by: Kiran Patil <kiran@fractalio.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9033
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 4fa4b7f2c2b57d1055adb76e8258b0db176bc356
Author: vmallika <vmallika@redhat.com>
Date:   Tue Oct 28 12:25:43 2014 +0530

    glusterd/snapshot: Snapshot should be deactivated when it is created
    
    By default snapshot should be deactivated and this should be a
    configurable option.
    
    This behaviour can be configured by the command below:
    gluster snapshot config activate-on-create <enable|disable>
    
    Change-Id: I1911595c32beed43bb2fca4bf99f0d264b422513
    BUG: 1157991
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8985
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 55aa4b185561edd7b3d1ab77a4f29a4facfdd7ff
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Oct 21 08:42:40 2014 +0000

    glusterd/snapshot: Check if LVM device path exists before delete.
    
    Check if the LV is present before deleting the LV. In case where
    the LV is absent (already deleted?), need not fail the snap delete
    operation.
    
    Also check if the LV is mounted before trying umount. In case it
    isn't umounted, only remove the LV.
    
    Change-Id: I0f5b2674797299d8748c6fac5b091f0caba65ca4
    BUG: 1104714
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8954
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e607ca013f106bffe7f141d92a70e60c659c47d5
Author: vmallika <vmallika@redhat.com>
Date:   Wed Nov 5 11:53:38 2014 +0530

    uss/gluster: Move all uss related logs into subfolder
    
    For USS we have 1 snapd log per volume and as many snap logs for volume.
    For example if there are 4 volumes having 256 snaps each and USS is
    enabled than total number of logs under /var/log/glusterfs for USS would
    be 1028 logs.
    
    Total logs = (4(snapd per volume) + 4(volumes)*256(snaps)) = 1028
    
    Hence, it makes sense to move into into sub-folder structure like
    
    /var/log/glusterfs/snaps/<vol-name>/<snapd + snaps logs>
    
    Change-Id: I29262e6458c3906916923cd67d1145d6ae10bec3
    BUG: 1160534
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9050
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 70b0c7b725408fc82969e15dcf67cd352b0fb68b
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Oct 21 07:57:22 2014 +0530

    USS : Display only the activated snapshots
    
    Instead of displaying all the snapshots in the uss world,
    it is better if we display only the activated snapshots.
    
    Change-Id: I70d3ec212b62ec15956ae3e826bc4201d8dedd17
    BUG: 1155042
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8958
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit a5e5813aeec36dbbfaa3b9821618d24972a1bf2f
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Oct 28 14:00:29 2014 +0100

    ec: Correctly handle quota xattrs
    
    Change-Id: I35e11d83c318210d44b918e847cf13db35b01510
    BUG: 1158008
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8990
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1800fba11260b348d06bfc21244c4ebc72bd7b95
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Nov 4 16:44:58 2014 +0530

    extras/hookscripts: Fix set behaviour for user.cifs and user.smb
    
    Setting either of user.cifs or user.smb to disable should disable smb
    shares when the smb share is already available.
    
    Change-Id: I213ffca9cedc14107daeb30271d1f41dd9d7fcf4
    BUG: 1105147
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/9042
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit a24a354737577d466ed1c29be1c4fa6bf1a31e11
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Fri Nov 7 15:29:45 2014 +0530

    Cluster/DHT : Rebalance skipped file count fix
    
    The return value in dht_migrate_file is used to indicate the status
    of the file migration. This value was being masked by the lock operation
    causing the skipped and failure file counts to be incorrectly calculated.
    
    Change-Id: Ice3d2f5d57766e18aa52659f22a76867d188dc65
    BUG: 1161518
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/9070
    Reviewed-by: susant palai <spalai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ffa4263c2f8fcb95ed5553a5a114bc26a920ad27
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 6 10:37:06 2014 +0530

    features/marker: Filter internal xattrs in lookup
    
    Afr should ignore quota-size-key as part of self-heal
    but should heal quota-limit key.
    
    Change-Id: Ic0b06bd20a563a00d6bfdc2dc5a76c661e533ecb
    BUG: 1161106
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9061
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 98f82412986339626bcd1218ff1da0fbb2664d6d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Nov 8 09:47:10 2014 +0100

    store: fix compile warning in gf_store_unlock()
    
    The following warning is logged when building on Fedora 20:
    
      store.c:712:15: warning: ignoring return value of 'lockf', declared
      with attribute warn_unused_result [-Wunused-result]
    
    It does not really matter if unlocking fails, close() will release the
    lock in any case. But, log the error in case close() can not finish and
    hangs indefinitely (is that possible?).
    
    Change-Id: If6c832f9aec10da6c1adb761b13b58e22d38a065
    BUG: 1009076
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9078
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b3ce1bfeaab08cdf51cccd60d6d7047c692f73a9
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Oct 31 06:52:39 2014 +0530

    cli: for rpc timeout throw a time out message
    
    Change-Id: I9660df1c3b2707583bd95806011b650cd1a2df1b
    BUG: 1161037
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9017
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 60f12e0eaf11a42f3f5ee8978ba540bbb6c8aadb
Author: vmallika <vmallika@redhat.com>
Date:   Wed Oct 8 12:26:37 2014 +0530

    glusterd/snapshot: mount snapshot volume with read-only option
    
    Snapshot volumes are readonly. If you mount the volume to the client it
    doesn't allow writes, but its attributes are rw which contradicts the
    functionality.
    
    mount script should set read-only attributes for snapshot volumes.
    
    Change-Id: I056253abd8dfe7b2b43a064fbdbd9c16b8eca679
    BUG: 1132946
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8518
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7c3609efb458ec270b53b852b2bb877900d9e68d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Nov 10 09:34:39 2014 +0100

    Spurious failures fix for bug-948729.t and bug-948729-mode-script.t
    
    Change I816b36e1d3e6933f92acf19d9be8eeaaa333356e causes sprurious
    failures in bug-948729.t and bug-948729-mode-script.t
    This seems to be caused by leftover information in /d/backends/
    probably in a dot-prefixed directory.
    
    Attempt to fix this by removing /d/backends and other work directories
    on cleanup. While there we test and report failure to remove anything.
    
    BUG: 1129939
    Change-Id: I0373c7f3c507db8ab509e8fd3aca2a386bea807e
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9081
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 5f0f2282d6e00a1de209a04c8270ee6cd8150d8b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Nov 6 14:32:57 2014 +0100

    Regression test portability: batch of bugs (volume 1)
    
    Fix various regression test portability in tests/bugs.
    
    bug-1004744.t:
    - Slower systems really requires an increased REBALANCE_TIMEOUT in include.rc
    
    bug-1023974.t:
    - use the -p option to mkdir before the path for portability sake.
    
    bug-1051896.t and bug-847622.t:
    - skip ACL test for NetBSD as it has no POSIX 1e ACL support.
    
    bugs-1053579.t:
    - Override the amount of secondary groups depending of the maximum
      the system supports.
    - Specify seq(1) format to avoid having trailing .00
    - Use more portable su -m USER -c COMMAND (also in bug-884597.t)
    - NetBSD does not fail high GID with NFS
    
    bug-1058663.c:
    - Depending on architecture, NetBSD can have SIGSEGV instead of SIGBUS
    
    bug-762989.t and bug-867253.t:
    - For non Linux systems, skip tests on features that are Linux-specific
    
    bug-765473.t;
    - Fix a {1} that bash is supposed to expand in 1 but does not, replace by 1.
    - Sync volume to make sure it imediatly knows a fd got bad
    
    BUG: 1129939
    Change-Id: I5405f94ccb8f20d35b3095096b0602c43719a1ae
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9009
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0d7fd69b01cf9aebb4f1517f064e89ff65b9ccf8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Oct 30 10:56:17 2014 +0530

    inode: Handle '/' in basename in inode_link/unlink
    
    Problem:
    inode_link is sometimes called with a trailing '/'. Lookup, dentry
    operations like link/unlink/mkdir/rmdir/rename etc come without trailing
    '/' so the stale dentry with '/' remains in the dentry list of the inode.
    
    Fix:
    Add assert checks and return NULL for '/' in bname.
    Fix ancestry building code to call without '/' at the end.
    
    Change-Id: I9c71292a3ac27754538a4e75e53290e182968fad
    BUG: 1158751
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9004
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a3252b9d8c4cc024b5528ca88076c7e33aecad38
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Nov 5 12:36:32 2014 +0530

    feature/gfid-access: Always send setattr down in overloaded setxattr.
    
    Problem: File ownership is not being preserved for root in geo-rep
             mountbroker setup.
    
    Analysis and Cause:
             Entry creations for geo-rep is overloaded in ga_setxattr.
             It happens in two phase, entry creation followed by setattr
             to preserve ownership as in master.
    
             If uid and gid of file being synced is root, setattr was
             not being sent down. Since, the file creation happens with
             non-root user in mountborker geo-rep setup, if setattr is
             not done explicitly, file ownership is not preserved for root.
    
    Solution:
             Always pass setattr down in overloaded ga_setxattr.
    
    Change-Id: I062215c1b2379d515f28ec7f271077ad37182c7e
    BUG: 1104954
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9051
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 7e497871d11a3a527e2ce192e4274322631f27d0
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Nov 3 16:07:30 2014 -0500

    api: versioned symbols in libgfapi.so for compatibility
    
    Use versioned symbols to keep libgfapi at libgfapi.so.0.0.0
    
    Some nits uncovered:
    
    + there are a couple functions declared that do not have an
      associated definition, e.g. glfs_truncate(), glfs_caller_specific_init()
    
    + there are seven private/internal functions used by heal/src/glfsheal
      and the gfapi master xlator (glfs-master.c): glfs_loc_touchup(),
      glfs_active_subvol(), and glfs_subvol_done(), glfs_init_done(),
      glfs_resolve_at(), glfs_free_from_ctx(), and glfs_new_from_ctx();
      which are not declared in glfs.h;
    
    + for this initial pass at versioned symbols, we use the earliest version
      of all public symbols, i.e. those for which there are declarations in
      glfs.h or glfs-handles.h.
      Further investigation as we do backports to 3.6, 3.4, and 3.4
      will be required to determine if older implementations need to
      be preserved (forward ported) and their associated alias(es) and
      symbol version(s) defined.
    
    FWIW, we should consider linking all of our libraries with a map, it'll
    result in a cleaner ABI. Perhaps something for an intern to do or a
    Google Summer of Code project.
    
    Change-Id: I499456807a5cd26acb39843216ece4276f8e9b84
    BUG: 1160709
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/9036
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1fe785152cc44e78fcd67da5091bc780eb42f1dd
Author: ggarg <ggarg@redhat.com>
Date:   Tue May 27 17:08:53 2014 +0530

    barrier: Correct gfid in statedump of barriered fops
    
    In brick statedump file the barriered fop's gfid was showing 0 when
    statedump was taken. This is because of statedump code was not
    referring to correct gfid.
    
    With this change statedump code will use correct gfid and gfid will
    not be 0 in statedump file when barrier is enable and user takes
    statedump of volume.
    
    Change-Id: Ia296cba7e132402df53c602daa160c1c2cd21245
    BUG: 1099369
    Reviewed-on: http://review.gluster.org/7893
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 97ccd45fb66a63c0b2436a0245dfb9490e2941b7
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Oct 27 12:12:03 2014 +0530

    glusterd : release cluster wide locks in op-sm during failures
    
    glusterd op-sm infrastructure has some loophole in handing error cases in
    locking/unlocking phases which ends up having stale locks restricting
    further transactions to go through.
    
    This patch still doesn't handle all possible unlocking error cases as the
    framework neither has retry mechanism nor the lock timeout. For eg - if
    unlocking fails in one of the peer, cluster wide lock is not released and
    further transaction can not be made until and unless originator node/the node
    where unlocking failed is restarted.
    
    Following test cases were executed (with the help of gdb) after applying this
    patch:
    
    * RPC timesout in lock cbk
    * Decoding of RPC response in lock cbk fails
    * RPC response is received from unknown peer in lock cbk
    * Setting peerinfo in dictionary fails while sending lock request for first peer
      in the list
    * Setting peerinfo in dictionary fails while sending lock request for other
      peers
    * Lock RPC could not be sent for peers
    
    For all above test cases the success criteria is not to have any stale locks
    
    Change-Id: Ia1550341c31005c7850ee1b2697161c9ca04b01a
    BUG: 1154635
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/9012
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 1a735e300a0ecd35d41f68f3c776350bb18f763a
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Oct 29 20:35:10 2014 +0100

    glupy: portability fixes
    
    Fixes portability problems so that NetBSD passes tests/features/glupy.t
    
    - Use python-config to detect python build environment on all systems,
      not just Linux and Darwin.
    - Get the site-package directory from python and make sure we install
      glupy.py there, Previously we installed within glusterfs prefix,
      which caused a problem if it was different that python's prefix.
    - Set PYTHONPATH for tests so that the detected site-packages is used
      in python's search path. This should be useless, but let us have it
      just in case.
    - Pass glupy.so path from glusterfsd to glupy.py through an
      environment variable and use it in CDLL instead of "", as the
      later seems not portable (at least it fails on NetBSD).
    - Use gil_init_key pthread_getspecific to avoid deadlocks (that
      code was #ifdef out, perhaps because it was not needed on Linux,
      but it seems to be required for NetBSD.
    - Recover the error message from Python and send it to the logs
      to help debugging problems.
    
    BUG: 1129939
    Change-Id: Icc71e77d6940f0759cc14c5c5cf7ca6fa431e0d2
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8978
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1c6ab3420b3b04eaf095098b614720b4e12ff498
Author: vmallika <vmallika@redhat.com>
Date:   Tue Nov 4 17:32:18 2014 +0530

    uss/gluster: Fix typo error in the description for USS under "gluster volume
    set help"
    
    gluster volume set help for uss shows "User Servicable Snapshots"
    whereas it should be "User Serviceable Snapshots"
    
    Change-Id: I3cc8b3ea2cb6d209e1a12678eb7d0e68f4160d99
    BUG: 1160236
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/9041
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b42255e87a06679b803e6bd83d02465d82c357b6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Nov 5 09:04:50 2014 +0530

    storage/posix: Treat ENODATA/ENOATTR as success in bulk removexattr
    
    Bulk remove xattr is internal fop in gluster. Some of the xattrs may have
    special behavior. Ex: removexattr("posix.system_acl_access"), removes more than
    one xattr on the file that could be present in the bulk-removal request.
    Removexattr of these deleted xattrs will fail with either ENODATA/ENOATTR.
    Since all this fop cares is removal of the xattrs in bulk-remove request and
    if they are already deleted, it can be treated as success.
    
    Change-Id: Id8f2a39b68ab763ec8b04cb71b47977647f22da4
    BUG: 1160509
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/9049
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8528253ddbac4cbcb7ce4881c085d9bfc0a82703
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Oct 28 11:48:02 2014 +0530

    cluster/afr: Preserve errno in case of failures on all subvols
    
    Problem:
    When quorum is enabled and the fop fails on all the subvolumes,
    op_errno is set to EROFS which overrides the actual errno returned
    from bricks.
    
    Fix:
    Don't override the errno when fop fails on all subvols.
    
    Change-Id: I61e57bbf1a69407230ec172a983de18d1c624fd2
    BUG: 1157976
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8984
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 08109ed5a7e09ec14ecb3640cfcaf9b32d83499b
Author: Shyam <srangana@redhat.com>
Date:   Fri Oct 24 15:44:22 2014 -0400

    xlator/io-stat: Check and copy loc->path
    
    Cases where loc->path is NULL, the current code in create/open/mkdir
    would copy the same blindly and as a result coredump.
    
    This is a preventive fix for the coredump. The reason for loc->path
    to be NULL in certain cases is yet to be determined.
    
    One such case is when resolve_loc_touchup fails to get inode_path due
    to loops in the inode table.
    
    Change-Id: Ic2ddf2cc9f2acaf9b939afc11afd193b4402ee7c
    BUG: 1159221
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/9029
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit edeb348a1cfe41aebd700e0689fa1139c1ebe408
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Nov 4 03:18:08 2014 -0800

    Revert "Build fix: xdrgen"
    
    This reverts commit 12bc39c144aa41a097435f2aab304ddfbbb9b625
    
    This causes all regression tests to fail. Reverting for now, we can include a
    correct fix later.
    
    Change-Id: I3c8966288f66d0eafa2e94490e3b64a057b4f2c0
    URL: http://supercolony.gluster.org/pipermail/gluster-devel/2014-November/042759.html
    BUG: 1157839
    Reported-by: Emmanuel Dreyfus <manu@netbsd.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/9040
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4a79fa4f2694888258942222db2c8390f168c731
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 25 10:12:46 2014 +0530

    features/quota: Use per-volume log file for crawler
    
    Change-Id: I195b3309bae7e684b7dbf771e4f3b4778d0dac4c
    BUG: 1146377
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8843
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 0da374020c17256141fb3971ae792b62097d72df
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Sat Nov 1 22:16:32 2014 +0530

    Cluster/DHT : Fixed crash due to null deref
    
    A lookup on a linkto file whose trusted.glusterfs.dht.linkto
    xattr points to a subvol that is not part of the volume
    can cause the brick process to segfault due to a null dereference.
    Modified to check for a non-null value before attempting to access
    the variable.
    
    Change-Id: Ie8f9df058f842cfc0c2b52a8f147e557677386fa
    BUG: 1159571
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/9034
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: venkatesh somyajulu <vsomyaju@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit adfccb57565ff1af0bbb79efc3cf489c55509aba
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 31 07:06:52 2014 +0530

    glusterd/geo-rep: Fix glusterd crash in non-originator slave node.
    
    Problem: glusterd crashes in non-originator slave node during geo-rep
             create push-pem.
    
    Cause: In glusterd_op_copy_file, the value of the key "common_pem_contents"
           is freed explicitly even after dict_set is successful when it is
           taken cared by dict_free.
    
    Solution: Free only in failure cases before dict_set.
    
    Change-Id: I65b5f32ee2b946107ad279b1fe3d728ec699bc7e
    BUG: 1159119
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/9018
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 12bc39c144aa41a097435f2aab304ddfbbb9b625
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Oct 31 04:58:59 2014 +0100

    Build fix: xdrgen
    
    As discovered in https://review.gluster.org/8762, BSD systems fail to
    run xdrgen during glusterfs build. This seems to be caused by a
    difference between BSD make and GNU make whith implcit targets. The
    former seems to use absolute path here, which means we should not
    prepend it with the current directory path, otherwise we have the
    directory path twice and the files cannot be found my make.
    
    BUG: 1157839
    Change-Id: I178123bf6f3d9e963ff5b78839d498f530c05a97
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9016
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit bf9e4330e4108e0dbab8ebf300bf7998551b9589
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Oct 28 18:19:30 2014 -0700

    rebalance: ``check_free_space`` should ignore quota_statfs
    
    quota_statfs() returns aggregated details of space usage
    of bricks this causes distribute to be confused during
    ``rebalance``, where ``statfs()`` values are used to
    schedule file migration.
    
    We can make sure the values of ``statfs`` are from
    individual bricks by selectively instructing
    ``quota_statfs()`` to return non aggregated values.
    
    Change-Id: I1397faeee66a1b9c26709cfda693286d227a4170
    BUG: 1158262
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8996
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5beb3a886c3bb12dfb0a9515e366de49859c2be1
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Oct 31 09:33:05 2014 +0100

    gluster --xml: survive missing fields
    
    Do not fail gluster --xml volume status detail with an empty output
    if some field is missing.
    
    Required for NetBSD to pass tests/bugs/bug-861542.t
    
    BUG: 1129939
    Change-Id: I7e2097dee5e18a5f3bb8fe6f14be53b33f4aa6b1
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/9024
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 927b9f3f48777dcb9e968f6b1bb3d5d450a8b7bc
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Oct 31 12:51:15 2014 +0530

    cluster/afr: Perform post-op in entry selfheal inside locks
    
    Take entrylks in xlator domain before doing post-op (undo-pending) in
    entry self-heal. This is to prevent a parallel name self-heal on
    an entry under @fd->inode from reading pending xattrs while it is
    being modified by SHD after entry sh below, given that
    name self-heal takes locks ONLY in xlator domain and is free to read
    pending changelog in the absence of the following locking.
    
    Change-Id: Ie083ceab10155c460447f04bdce7688480f1ac4f
    BUG: 1128721
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/9020
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 756949556b3ceb2279f09962ab5789960de86bd3
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Oct 31 09:26:28 2014 +0100

    Regression test portability: mock
    
    After some attempts at using mock on NetBSD which pulled a lot of
    dependencies, it seems that software really assumes the OS is
    Linux: chrooted build will fail because of missing Linux files.
    
    As a result, make tests/basic/rpm.t Linux-only, and remove mock
    and rpmbuild checks for non Linux systems.
    
    BUG: 1129939
    Change-Id: Ica2eb74dd23fbec379a26051a8f61b0dfc07a115
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8949
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit a718a11a1c21c1f74460b61c98579db4ae2747ac
Author: jiffin <jthottan@redhat.com>
Date:   Thu Oct 30 15:58:56 2014 +0530

    gNFS : mount fails if connection to brick(s) is not established yet.
    
           Connection between gluster-nfs and brick process requires
           time (especially for rdma).During that time when we try to
           mount using nfs ,it will fail saying that volume not found.
           So we need a check using 'is_nfs_export_available'before
           mounting to ensure volume is available.This patch will provide
           the check before nfs mount if it is not given in the test files
    
    Change-Id: I242eb6e3118ebaca1df46314302a203a0c9738a8
    BUG: 1158831
    Signed-off-by: jiffin tony thottan <jthottan@redhat.com>
    Reviewed-on: http://review.gluster.org/9011
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4120e8a47a6d9b8cb3e4bf6f8ede6d26667fb673
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 14 15:16:24 2014 -0400

    glusterd: add option support for own-thread
    
    Like enabling SSL, enabling own-thread has to be done separately for
    clients and servers.
    
     * client.own-thread for clients (including internal like self-heal)
    
     * server.own-thread for servers (including e.g. glusterd)
    
    It's very unlikely that you would ever want to set one without the
    other, but they're separate anyway just in case.  Check for "private
    polling thread" in the relevant logs to make sure the option took
    effect, because otherwise you might not notice any difference besides
    inreased performance.  ;)
    
    Change-Id: Ifaee8de52f0b959bcdf7f6b56faeee549ee56604
    BUG: 1158648
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8931
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8ab61c18d5de81aa613130e8f65b2f420476c08e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Oct 29 17:47:48 2014 +0530

    features/snapview-server: verify the fs instance in revalidated lookups as well
    
    Change-Id: Id5f9d5a23eb5932a0a53520b08ffba258952e000
    BUG: 1151004
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8999
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3b022b19b77c3a159682b76998fa9ac9518e1c3c
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Aug 4 09:52:09 2014 +0200

    Use F_CLOSEM if available
    
    Use F_CLOSEM to close all file descriptors if available.
    
    BUG: 764655
    Change-Id: Ib3c682825b89c163ebb152848f2533b3cb62cdce
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8379
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fb2e0a4afbe3263ebda3e1d2b72d921b2d7e2c50
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Oct 29 01:17:25 2014 +0100

    Regression test portability: TAP
    
    Even with successful tests on NetBSD, we had a failure message at
    the end: "No plan found in TAP output"
    
    This was caused by a white space left padded numerical variable.
    Stripping the white spaces fixes the problem.
    
    While there add SKIP_TEST for NetBSD on unspported tests so that
    it does not triger a failure.
    
    BUG: 1129939
    Change-Id: I8d0bc125c4208974657977568d838ee2dd19783c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8981
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 886eb63fc729d3effea292ef92e02168898d8205
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Oct 28 18:27:20 2014 +0100

    Lazy umount emulation: deal with stopped volumes
    
    On non Linux systems, lazy umount is emulated using contrib/umountd.
    It first check that the path given to unmount exists, but it should
    not give up on ENOTCONN as it is what happens when a volume is mounted
    but stopped.
    
    This lets NetBSD pass tests/bugs/bug-1049323.t
    
    BUG: 1129939
    Change-Id: I3451362453607a0fd82b095a9e5aa6f63bfe869a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8991
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d2da726fe76e61f4c499421d8d2bd588ca41b770
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Oct 9 09:08:57 2014 +0200

    Regression test portability: loopback devices
    
    Introduce functions to deal with loopback devices setup, mount
    and umount.
    
    Remove test for xfsprogs for non Linux systems, as loopback devices
    can be populated with other filesystems (e.g.: FFS for NetBSD)
    
    While there, remove mount.nfs test for non Linux systems. At least
    NetBSD has it in base system as mount_nfs.
    
    BUG: 1129939
    Change-Id: I816b36e1d3e6933f92acf19d9be8eeaaa333356e
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8914
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 92c4650ac809ee227c6591397a64269850f3217e
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Oct 1 06:50:02 2014 +0200

    Regression test portability: useradd/userdell
    
    Adjust useradd/userdel flags for NetBSD. Similar work will have to be
    done for other non Linux systems
    
    BUG: 1129939
    Change-Id: I2a30819a4915d04473f0ef0c0c063de6015212a1
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8895
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 96e1c33b681b34124bdc78174a21865623c9795b
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Oct 28 13:06:50 2014 +0530

    glusterd: Store rebalance state on all peers
    
    The rebalance state was being saved only on the peers participating in
    the rebalance on a rebalance start. This change makes sure all nodes
    save the rebalance state.
    
    Change-Id: I436e5c34bcfb88f7da7378cec807328ce32397bc
    BUG: 1157979
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8998
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 20efa36ed961a210cfc2cec7599acf92cec157ce
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Sep 23 14:56:40 2014 +0530

    doc: iobuf and iobref documentation.
    
    Change-Id: Ib6d8121a968e8160c587a8553b7333262bb44975
    BUG: 1118309
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/8818
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 17d502b2cfaa2c4d87402b601bf1851eb554bff3
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Aug 4 16:27:52 2014 +0530

    doc: Introduction to meta xlator.
    
    ... in the form of examples. This is by no means exhaustive.  Meta
    xlator is not as well known as it should be for its own good.  This
    patch is to get the ball rolling.
    
    Change-Id: I5898c37aa15706e886af68f19caac48c175df90b
    BUG: 1144282
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8410
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e5da8c1bc545cb004747ddbe1ea5f215ac166143
Author: Joe Julian <me@joejulian.name>
Date:   Tue Oct 21 23:37:44 2014 -0700

    Fixed missing / in replace-brick pause example
    
    BUG: 1155421
    Change-Id: I079f738e8381bada4595d3600921a39581edaea7
    Signed-off-by: Joe Julian <me@joejulian.name>
    Reviewed-on: http://review.gluster.org/8963
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 51be7065dba8e62bff177bec4bc093e864492d29
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Oct 22 21:08:03 2014 +0200

    Regression test portability: self-heald.t
    
    Fix portability problems in updated self-heald.t:
    - Use the k suffit in dd(1) bs argument instead of less portable M and K
    - Error message for disconnected bricks in NetBSD is "Socket is not connected"
    - On touch d/a while bricks are down, NetBSD updates d ctime/mtime even
      on bricks where a is not present, resulting in a different to-be-healed
      count than on Linux. We now tes both values. If NetBSD behavior is a bug,
      it is not in the heal process and should be tested somewhere else.
    
    This also requires fixes in heal process: http://review.gluster.org/8936
    
    BUG: 1129939
    Change-Id: Ibda1902a8fd64aa7cc5202744adca825e6b251c9
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8968
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a5d73daabf6df95bc73b186d92f3e2d1239a6f8a
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Wed Oct 29 00:44:33 2014 +0530

    logrotate: gluster logrotate config should not be global
    
    Issue : Previously glusterfs logrotate config file pollutes
    global config. So moved the directives inside the curly braces,
     so they don't pollute the global config state.
    
    Change-Id: I8836893dfcdf457d9c5d766612d687bfce64e2ae
    BUG: 1126802
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/8994
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c6e6b43b169b8452ee26121ce1ad0b0f07b512cf
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Oct 28 02:53:39 2014 -0400

    CLI: Show warning message only for remove-brick commit
    
    Earlier warning message for checking the removed-bricks for
    any unmigrated files was thrown both for remove-brick commit
    and force.
    
    With this change the warning message will be shown only for
    remove-brick commit.
    
    Change-Id: Ib1fa47d831d5189088c77c5cf709a25ff36d7379
    BUG: 1157974
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/8983
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 22e18a4c0c07a41fcdcde1ce0e90961b347d7a84
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Oct 14 12:11:24 2014 +0200

    Avoid spurious EINVAL in posix_readdir()
    
    On non Linux systems, we check that seekdir() succeeds and we return
    EINVAL if it does not. We need this to avoid infinite loops if some
    other component in GlusterFS makes an invalid seekdir() usage. This
    was introduced in this change: http://review.gluster.org/#/c/8760/
    
    But seekdir() also fails when using the offset returned for the
    last entry, and this is expected behavior. As a result, the seekdir()
    test produces a spurious EINVAL when reaching end of directory. That
    error is not propagated to calling process, but it may harm internal
    GlusterFS processing. At least it produce a spurious error message
    in brick's log.
    
    We fix the problem by remembering the last entry offset in fd private
    data. When a new posix_readdir() invocation requests that offset,
    we avoid returning EINVAL.
    
    BUG: 1129939
    Change-Id: I4e67a2ea46538aae63eea663dd4aa33b16ad24c7
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8926
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5ae0df29b4e590d9a8a5f3c8f9e98cc944b006cf
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed Oct 22 12:09:01 2014 +0530

    feature/changelog: Fix changelog missing SETATTR entries.
    
    Problem: Valid SETATTR entries are missing in changelog when more
             than one metadata operation happen on same inode within
             changelog roll-over time.
    
    Cause: Metadata entries with fop num being GF_FOP_NULL are logged
           in changelog which is of no use. Since slice version
           checking is done for metadata entries to avoid logging of
           subsequent entries of same inode falling into same
           changelog, if the entry with GF_FOP_NULL is logged first,
           subsequent valid ones will be missed.
    
    Solution: Have a boundary condition to log only those fops whose fop
              number falls between GF_FOP_NULL and GF_FOP_MAXVALUE.
    
    Change-Id: Iff585ea573ac5e521a361541c6646225943f0b2d
    BUG: 1104954
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8964
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit ef03f98bf9b5f7f317383b84d251299b8939e5cc
Author: Anand Avati <avati@redhat.com>
Date:   Tue Oct 28 14:05:06 2014 -0700

    inode: include dentry cycle checks for all existing inodes
    
    inode_link() has the responsibility of maintaining the DAGness of
    the dentry tree, and prevent cyclic loops from forming. To do this
    the technique used is to perform cyclic check only while linking
    inodes which already were linked in the inode table (i.e linking
    a new_inode() can never form a loop).
    
    While this was how it was supposed to be all along, the @old_inode
    variable was missed out to get updated if the given inode to inode_link
    itself was already linked (i.e, the code was only handling a complex
    case when the given new inode had a gfid which already existed)
    
    Without this patch, it is possible to call inode_link in a specific
    way which results in dentry loops.
    
    Change-Id: I4c87fa2d63f11e31c73d8b847e56962f6c983880
    BUG: 1158226
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/8995
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8df26e838c40f15bb2b26131d1533da339f5be3e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Oct 15 12:56:48 2014 +0530

    glusterd: op state machine shouldn't use global peer list
    
    Problem : op state machine was relying on the global peer list while sending
    lock/stage/unlock commit rpc requests to the peers in the cluster. Trusting on
    global peer list structure is dangerous as this structure gets modified if any
    peer modification command is attempted in the cluster when there is a ongoing
    transaction going through the state machine. An ideal usecase of this problem
    when rebalance is in progress and peer probe is executed rebalance op-sm and
    peer probe may run into race making peerinfo structure go for toss.
    
    Solution: Use local copy of peer list (xaction_peers) in glusterd op-sm.
    
    Change-Id: I1ff7118dc6a9a72633e2e87b7ab7bae1796595e0
    BUG: 1152890
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8932
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 27628b7b0950a673cfb5584c76d25c183f5be02f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Oct 24 17:10:15 2014 +0200

    Regression test portability: quota-anon-fd-nfs.t
    
    Fix portability problems in quota-anon-fd-nfs.t
    - Use mount_nfs wrapper and include nfs.rc to get it defined.
    - umount NFS before cleanup to avvoid deadlocks.
    - umount -l is Linux-specific, use umount -f on BSD.
    - wait for 1s for portmap registration before mouting NFS.
    - mount from $H0 instead of localhost: the later fails on NetBSD.
    - Test quota without filling GB of data, 20MB is enough and it
      will be gentle with smaller setups.
    - wait for write behind to complete before testing quota overflow
    
    BUG: 1129939
    Change-Id: I097d5faed2fa7b6438aaa56def85172f23bbe7dc
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8969
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Kiran Patil <kiran@fractalio.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3993728390cc50390a527f5f01d6dcf3e6293110
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jun 5 11:12:22 2014 +0530

    geo-rep: gid is not set in entry ops
    
    uid is sent in place of gid while CREATE and
    MKDIR.
    
    Change-Id: Icd1072cb9dcbfc1f419a3cdd456f3d02168175fa
    BUG: 1104954
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7984
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit a7ef6eea4d43afdba9d0453c095e71e6bf22cdb7
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Tue Jul 1 07:52:27 2014 -0400

    Posix: Brick failure detection fix for ext4 filesystem
    
    Issue: stat() on XFS has a check for the filesystem status but
    ext4 does not.
    
    Fix: Replacing stat() call with open, write and read  to a new file under the
    "brick/.glusterfs" directory. This change will work for xfs, ext4 and other
    fileystems.
    
    Change-Id: Id03c4bc07df4ee22916a293442bd74819b051839
    BUG: 1130242
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/8213
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4d3c6d93d1c75696987f262cf5a304b3038bc585
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Oct 27 10:28:55 2014 +0100

    changelog: replace MAKE_HTIME_FILE_PATH with snprintf()
    
    The used once MAKE_HTIME_FILE_PATH macro uses strcpy and strcat into a
    fixed buffer without checking the input lengths.
    
    Recommend replacing with a snprintf.
    
    Change-Id: Ia0245096774dc84be1b937e1d5750f3634fff034
    BUG: 1099645
    Reported-by: Keith Schincke <kschinck@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8977
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit c35135c8da3542f377dcb22d121d255eb796a819
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Aug 5 08:29:42 2014 -0400

    glusterfs.spec.in: use upstream logrotate exclusively
    
    retiring Fedora dist-git *.logrotate files
    
    Change-Id: I6a94aac6f45573216de3f9e673d10db6de5ccb98
    BUG: 1126832
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8418
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 42150856c117bd53427f297664106d8db771a33e
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Fri Oct 24 15:03:12 2014 +0200

    ec: Correctly handle xtime extended attribute
    
    Change-Id: I2bd34f063d6bf1835d5ae57a8e9aa03f3ec3deb3
    BUG: 1156404
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8972
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1fa3e87db77bb379173723a5e75b361a8e192f09
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Oct 9 17:32:48 2014 +0530

    features/snapview-server: check if the reference to the snapshot world is
    correct before doing any fop
    
    The following operations might lead to problems:
    * Create a file on the glusterfs mount point
    * Create a snapshot (say "snap1")
    * Access the contents of the snapshot
    * Delete the file from the mount point
    * Delete the snapshot "snap1"
    * Create a new snapshot "snap1"
    
    Now accessing the new snapshot "snap1" gives problems. Because the inode and
    dentry created for snap1 would not be deleted upon the deletion of the snapshot
    (as deletion of snapshot is a gluster cli operation, not a fop). So next time
    upon creation of a new snap with same name, the previous inode and dentry itself
    will be used. But the inode context contains old information about the glfs_t
    instance and the handle in the gfapi world. Directly accessing them without
    proper check leads to ENOTCONN errors. Thus the glfs_t instance should be
    checked before accessing. If its wrong, then right instance should be obtained
    by doing the lookup.
    
    Change-Id: Idca0c8015ff632447cea206a4807d8ef968424fa
    BUG: 1151004
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8917
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2855dff243f20a78cd8cc4e7cd581a9c558b2e69
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Sep 23 13:02:56 2014 +0530

    doc: documentation of inode and dentry management
    
    Change-Id: Ica510752d011596e8ecff5ea13c4b2bbf76ba186
    BUG: 1145475
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8815
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b2ae71dbcf1b932abc16f096eee74d50aa823b04
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Aug 15 11:13:46 2014 +0200

    glusterd: really get the inode size for a brick
    
    The device to get the inode size from does not get passed to the tool
    (tune2fs, xfs_info or the like) that is called. This is probably just an
    oversight. While correcting this, cleanup some bits of the function too.
    
    Change-Id: Ida45852cba061631fb304bc7dd5286df1a808010
    BUG: 1130462
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8492
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 306e6bf33fbaf5656764d01ad87452e265e2a6e9
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Oct 15 09:44:55 2014 +0200

    ec: Fix rebalance issues
    
    Some issues in ec xlator made that rebalance didn't complete
    successfully and generated some warnings and errors in the
    log. The most critical error was a race condition that caused
    false corruption detection when two specific operations were
    executed sequentially and they shared the same lock.
    
    This explains the problem:
    
    1. A setxattr is issued.
    2. setxattr: ec locks the inode before updating the xattr.
    3. setxattr: The xattr is updated.
    4. setxattr: Upper xlator is notified that the operation completed.
    5. setxattr: A background task is initiated to update the version
                 of the file.
    6. A stat is issued on the same file.
    7. stat: Since the lock is already acquired, it's reused.
    8. stat: A lookup is issued to determine version and size
             information of the file.
    
    At this point, operations 5 and 8 can interfere. This can make that
    lookup sees different information on each brick, determining that
    some bricks are corrupted and incorrectly excluding them from the
    operation and initiating a self-heal. In some cases this false
    detection combined with self-heal could lead to invalid updates of
    the trusted.ec.size xattr, leaving the file smaller than it should
    be.
    
    This only happens if the first operation does not perform a lookup,
    because chained operations reuse the information returned by the
    previous one, avoiding this kind of problems.
    
    To solve this, now the background update is executed atomically with
    the posterior unlock. This avoids some reuses of the lock while
    updating. However this reduces performance because the window in
    which new requests can reuse the lock is much smaller now. This has
    been alleviated by using the same technique implemented in AFR (i.e.
    waiting some time before releasing the lock).
    
    Some minor changes also introduced in this patch:
    
    * Bug in management of 'trusted.glusterfs.pathinfo' that was writing
      beyond the allocated space.
    * Uninitialized variable.
    * trusted.ec.config was not created for regular files created with
      mknod.
    * An invalid state was used in access fop.
    
    Change-Id: Idfaf69578ed04dbac97a62710326729715b9b395
    BUG: 1152902
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8947
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5c6e88320489d789fcd026bed72009b0806fe314
Author: Kotresh HR <khiremat@redhat.com>
Date:   Mon Sep 8 15:04:15 2014 +0530

    geo-rep/glusterd: Enable changelog and marker during geo-rep create.
    
    PROBLEM:
    Geo-rep misses few a files to sync when I/O happenned during
    geo-rep start.
    
    ANALYSES:
    To use the available changelogs to handle deletes/renames,
    'xsync upper limit' is introduced which limits the xsync
    crawl till the changelog register time.  But there is a
    small time interval between the changelog register time and
    the time changelog actually enabled. If there is I/O between
    this interval, it will not be synced through xsync as it is
    beyond changelog register time and not through changelog also
    as changelog is not actually enabled.
    
    SOLUTION:
    Enable changelog and marker during geo-rep create instead
    of geo-rep start so that entries are captured in changelog
    and above said interval is nullified.
    
    Change-Id: Ic5f0457a4b67a335cbbb37d34db5f8cb8bc901c4
    BUG: 1139196
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8650
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 378a0a19d95e552220d71b13be685f4772c576cd
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 21 16:54:48 2014 -0400

    socket: disallow CBC cipher modes
    
    This is related to CVE-2014-3566 a.k.a. POODLE.
    
    	http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566
    
    POODLE is specific to CBC cipher modes in SSLv3.  Because there is no
    way to prevent SSLv3 fallback on a system with an unpatched version of
    OpenSSL, users of such systems can only be protected by disallowing CBC
    modes.  The default cipher-mode specification in our code has been
    changed accordingly.  Users can still set their own cipher modes if they
    wish.  To support them, the ssl-authz.t test script provides an example
    of how to combine the CBC exclusion with other criteria in a script.
    
    Change-Id: Ib1fa547082fbb7de9df94ffd182b1800d6e354e5
    BUG: 1155328
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8962
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a7a8a7507ca938b23d20a52931fa034cfaaa29f8
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Tue Oct 21 19:50:29 2014 +0530

    Hooks : Infinite while loop introduced by another change.
    
    A change made to all the hook scripts introduced an
    infinite while loop in the script S31ganesha-reset.sh.
    It resulted in 100% CPU usage by this script.
    
    Change-Id: If62d8f0e065c6e6511363b8b26eae433f59bc5c3
    BUG: 1155489
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/8966
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0386f0a51e7e445c66bedc7472037e22066eb66a
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sun Oct 19 12:42:05 2014 -0700

    libglusterfs: Do not redefine AT_SYMLINK_NOFOLLOW on Darwin
    
    Change-Id: I6c31b0a01da4b2ad05d4df67418e917c2774faa9
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8943
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 56caf4349c8824fde70783fe404cc6f646dce149
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Oct 8 09:20:11 2014 +0200

    ec: Fix self-heal issues
    
    Problem: Doing an 'ls' of a directory that has been modified while one
             of the bricks was down, sometimes returns the old directory
             contents.
    
    Cause: Directories are not marked when they are modified as files are.
           The ec xlator balances requests amongst available and healthy
           bricks. Since there is no way to detect that a directory is
           out of date in one of the bricks, it is used from time to time
           to return the directory contents.
    
    Solution: Basically the solution consists in use versioning information
              also for directories, however some additional changes have
              been necessary.
    
    Changes:
    
     * Use directory versioning:
    
         This required to lock full directory instead of a single entry for
         all requests that add or remove entries from it. This is needed to
         allow atomic version update. This affects the following fops:
    
             create, mkdir, mknod, link, symlink, rename, unlink, rmdir
    
         Another side effect is that opendir requires to do a previous
         lookup to get versioning information and discard out of date
         bricks for subsequent readdir(p) calls.
    
     * Restrict directory self-heal:
    
         Till now, when one discrepancy was found in lookup, a self-heal
         was automatically started. This caused the versioning information
         of a bad directory to be healed instantly, making the original
         problem to reapear again.
    
         To solve this, when a missing directory is detected in one or more
         bricks on lookup or opendir fops, only a partial self-heal is
         performed on it. A partial self-heal basically creates the
         directory but does not restore any additional information.
    
         This avoids that an 'ls' could repair the directory and cause the
         problem to happen again. With this change, output of 'ls' is
         always consistent. However, since the directory has been created
         in the brick, this allows any other operation on it (create new
         files, for example) to succeed on all bricks and not add additional
         work to the self-heal process.
    
         To force a self-heal of a directory, any other operation must be
         done on it. For example a getxattr.
    
         With these changes, the correct healing procedure that would avoid
         inconsistent directory browsing consists on a post-order traversal
         of directoriesi being healed. This way, the directory contents will
         be healed before healing the directory itslef.
    
     * Additional changes to fix self-heal errors
    
         - Don't use fop->fd to decide between fd/loc.
    
             open, opendir and create have an fd, but the correct data is in
             loc.
    
         - Fix incorrect management of bad bricks per inode/fd.
    
         - Fix incorrect selection of fop's target bricks when there are bad
           bricks involved.
    
         - Improved ec_loc_parent() to always return a parent loc as
           complete as possible.
    
    Change-Id: Iaf3df174d7857da57d4a87b4a8740a7048b366ad
    BUG: 1149726
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8916
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d57ecca6322a451242f4a2b7b5978de7c8f9088e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Oct 21 14:44:03 2014 +0530

    libglusterfs: include compat-errno.h in common-utils to avoid smoke failures
    
    Change-Id: I14ae91bf20a0eb7a79b3d6028844f55642eb5426
    BUG: 1151303
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8955
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 49d6a7b17f7cffbb9a33b61c9751b37353b8bd08
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Oct 14 18:23:44 2014 +0200

    Regression test portability: quota.t
    
    - Use du -k to have size reported in kB, as NetBSD defaults to blocks
    - on overquota, Linux says 'No space left' and NetBSD 'Disc quota exceeded'
    
    BUG: 1129939
    Change-Id: I6a2baef94cb60e9fabf06a6f8d01f2acb6ee0a30
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8930
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit eea806646216f5e5a91fd35a4e138e193e3b6fac
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Oct 17 11:46:46 2014 +0530

    performance/io-threads: Fix static analysis error
    
    stub->fop can be more than FOP_MAX is what static analysis is complaining. This
    patch doesn't allow any 'log' to be printed in the case fop value is not in the
    definied range. It gives EINVAL instead.
    
    Change-Id: I293381e2c1ad0ab45154b0192a637612becaf744
    BUG: 1153935
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8939
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5ac067e560696410c059b21ca039f74687c62e7a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Oct 10 09:51:28 2014 +0530

    logs: Do selective logging for errnos
    
    Problem:
    Just after replace-brick the mount logs are filled with ENOENT/ESTALE
    warning logs because the file is yet to be self-healed now that the
    brick is new.
    
    Fix:
    Do conditional logging for the logs. ENOENT/ESTALE will be logged at
    lower log level. Only when debug logs are enabled, these logs will
    be written to the logfile.
    
    Change-Id: If203d09e2479e8c2415ebc14fb79d4fbb81dfc95
    BUG: 1151303
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8918
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e4d25d50b58d3ee08453492852b79425c398aa05
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Sep 29 11:31:24 2014 +0200

    ec: Fix 32 bits issues on file size calculation
    
    Some additional 32 bits issues have been added by a recent patch.
    This patch solves it.
    
    Change-Id: Ice81032fbe8e36e5ccad19a781b7876891993906
    BUG: 1146903
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8882
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8ea1eaf46153b56fb4c652a8eb9fb95a49038373
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Oct 6 16:34:58 2014 +0200

    ec: Fix incorrect management of healed bricks
    
    The final lookup made to restore final file attributes after a self-heal
    did clear the mask of bad bricks, causing that the final setattr won't
    modify any brick at all. This caused that some attriutes, specially the
    modification time of the file didn't get updated properly.
    
    Now the mask of healed bricks is saved before doing the last lookup.
    It's also used to correctly report the repaired bricks.
    
    Change-Id: Ib94083c9e1b562515dfb54f9574120f1f031dccc
    BUG: 1149723
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8905
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2d92565e60485c81bbe6b3ebde60aeb623eda36a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Oct 10 16:13:25 2014 +0530

    geo-rep: Failover when a Slave node goes down
    
    When a slave node goes down, worker in master node
    can connect to different slave node and resume the operation.
    
    Existing georep was not checking the status of slave node before
    worker restart. With this patch, geo-rep worker will check the
    node status using `gluster volume status` when it goes faulty.
    
    BUG: 1151412
    Change-Id: If3ab7fdcf47f5b3f3ba383c515703c5f1f9dd668
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8921
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 9aa1e5ef86dba5ff8233c8e7c8d4de6334b9fcd4
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Oct 17 16:55:05 2014 -0700

    heal/src: Fix build failure on OSX
    
    Fix involves removing GF_GLUSTERFS_CFLAGS is a
    non-existent configure value, use GF_CFLAGS instead
    
    Change-Id: Id5e29f46589dd75c1f71c53ffaf8af60584782c7
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8942
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>

commit 1dc824c6180ba7d2a620c5a660bdc5cabe7aabc1
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri May 30 01:43:15 2014 +0530

    feature/geo-rep: Fix skipped files logging.
    
    When changelog is failed to process even after max
    retries, files are skipped but were not logging.
    This patch addresses this issue to log the skipped
    files.
    
    Change-Id: Ic617e4151231fe18a171efa57a119e21164e1a6a
    BUG: 1103577
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7945
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 6c13daed1d601df76cfd1973d3ce800afa877fd2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Sep 4 21:47:50 2014 +0530

    glusterd: statedump support
    
    Although glusterd currently has statedump support but it doesn't dump its
    context information. Implementing glusterd_dump_priv function to export per-node
    glusterd information would be useful for debugging bugs. Once implemented, we
    could enhance sos-report to fetch this information. This would potentially
    reduce our time to root cause and data needed for debugability can be dumped
    gradually.
    
    Following is the main items of the dump list targeted in this patch :
    
        * Supported max/min op-version and current op-version
        * Information about peer list
        * Information about peer list involved while a transaction is going on
          (xaction_peers)
        * option dictionary in glusterd_conf_t
        * mgmt_v3_lock in glusterd_conf_t
        * List of connected clients
        * uuid of glusterd
        * A section of rpc related information like live connections and their
          statistics
    
    There are couple of issues which were found during implementation and testing
    phase:
     - xaction_peers of glusterd_conf_t was not initialized in init because of which
       traversing through this list head was crashing when there was no active
       transaction
     - gf_free was not setting the typestr to NULL if the the alloc count becomes 0
       for a mem-type earlier allocated.
    
    Change-Id: Ic9bce2d57682fc1771cd2bc6af0b7316ecbc761f
    BUG: 1139682
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8665
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 7e8eefca2caaaa61e1b31b747384f660c595d9c9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Dec 15 08:05:04 2013 +0530

    heal: glfs-heal implementation
    
    Thanks a lot to Niels for helping me to get build stuff right.
    
    Change-Id: I634f24d90cd856ceab3cc0c6e9a91003f443403e
    BUG: 1147462
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6529
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7808d4b7892ccd80bcabb1253ee359a64c51c612
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Oct 13 15:19:35 2014 -0700

    Revert "extras: reverse test for '}' vs. following 'else' placement"
    
    This reverts commit 0a8371bdfdd88e662d09def717cc0b822feb64e8.
    
    Change-Id: I946f449ad213cea70fbbd9cd3951f5838b9f82e5
    BUG: 1120646
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8927
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 3b5b5042ec2f119e3ec807829c101c421e90e2da
Author: Kotresh HR <khiremat@redhat.com>
Date:   Fri Oct 3 17:35:47 2014 +0530

    glusterd/geo-rep: Fix race in updating status file
    
    When geo-rep is in paused state and a node in a cluster
    is rebooted, the geo-rep status goes to "faulty (Paused)"
    and no worker processes are started on that node yet. In
    this state, when geo-rep is resumed, there is a race in
    updating status file between glusterd and gsyncd itself
    as geo-rep is resumed first and then status is updated.
    glusterd tries to update to previous state and gsyncd
    tries to update it to "Initializing...(Paused)" on
    restart as it was paused previously. If gsyncd on restart
    wins, the state is always paused but the process is not
    acutally paused. So the solution is glusterd to update
    the status file and then resume.
    
    Change-Id: I348761a6e8c3ad2630c79833bc86587d062a8f92
    BUG: 1149982
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8911
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit f5d544d435b1ca0868846e74ce292faa2e7388e4
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Sep 2 17:26:38 2014 +0530

    glusterd: print the peer name instead of a null UUID in a rpc failure message
    
    This patch improves the failure message by printing the correct peer name
    instead of a blank uuid in case of rpc connection is lost/broken.
    
    Change-Id: Ia232792051f23896883b239982cb48130e3ce60e
    BUG: 1146902
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8597
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 430b874c4f1a171c106a9e1e6507e14e79805a1d
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Oct 7 10:08:20 2014 +0200

    glusterd: make bricks respect 'transport.socket.bind-address'
    
    When GlusterD starts the brick processes, these will listen on all
    interfaces. When the 'transport.socket.bind-address' option is set in
    glusterd.vol, the brick processes should only listen on the specified
    hostname or IP-address.
    
    Change-Id: I8e7d1f294904081137c23f3446261329d0d13bba
    BUG: 1149863
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8910
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 678e91718c41b29046df7b9a019e4e9f7550efcb
Author: Mohammed Rafi KC <rkavunga@redhat.com>
Date:   Thu Sep 25 15:36:30 2014 +0530

    rdma: mount hangs for rdma type transport.
    
    rdma transport type mount will hang if there is a delay
    in network to receive,we will set transport as connected
    if we get an event type RDMA_CM_EVENT_ESTABLISHED,
    we cannot assure whether client or server will get the
    event first, the only condition is that the side which
    sends the first request should wait for the event.
    If client gets the event first, then it sends DUMP request,
    in server side the request will reach, but it will reject
    the rpc request since it didn't get the RDMA_CM_EVENT_ESTABLISHED.
    So in server we will set the connected flag as soon
    as rdma_accept is called.
    
    Change-Id: Iac5845e3592666daa575c727822889779b5bd203
    BUG: 1146492
    Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    Reviewed-on: http://review.gluster.org/8850
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 283fa797f4bf98130b42c36972305b8cb6e5aaaf
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Oct 6 22:51:22 2014 +0200

    glusterd: pass the bind-address to starting services
    
    When the transport.socket.bind-address option is set to a hostname or
    ip-address, the services started by GlusterD fail to connect to the
    management daemon. GlusterD always forces the services to connect to the
    "localhost" hostname, even if it is not listening on that address.
    
    GlusterD should take the transport.socket.bind-address option into
    consideration, and pass that to the glusterfs-clients with the -s or
    --volfile commandline parameter.
    
    Note that this is not a change that removes all hard-coded dependencies
    on "localhost". This change merely makes it possible to start required
    services when the transport.socket.bind-address option is set.
    
    Change-Id: I36a0ed6c69342e6327adc258fea023929055d7f2
    BUG: 1149863
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8908
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit ddb31110db8e1b5995d392ced988f34d2f9145d2
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Tue Jul 22 16:56:57 2014 +0530

    gNFS: Subdir mount does not work on UDP proto
    
    After enabling nfs.mount-udp, mounting a subdir on a volume over
    NFS fails. Because mountudpproc3_mnt_3_svc() invokes nfs3_rootfh()
    which internally calls mnt3_mntpath_to_export() to resolve the
    mount path. mnt3_mntpath_to_export() just works if the mount path
    requested is volume itself. It is not able to resolve, if the path
    is a subdir inside the volume.
    
    MOUNT over TCP uses mnt3_find_export() to resolve subdir path but
    UDP can't use this routine because mnt3_find_export() needs the
    req data (of type rpcsvc_request_t) and it's available only for
    TCP version of RPC.
    
    FIX:
    (1) Use syncop_lookup() framework to resolve the MOUNT PATH by
        breaking it into components and resolve component-by-component.
        i.e. glfs_resolve_at () API from libgfapi shared object.
    (2) If MOUNT PATH is subdir, then make sure subdir export is not
        disabled.
    (3) Add auth mechanism to respect nfs.rpc-auth-allow/reject and
        subdir auth i.e. nfs.export-dir
    (4) Enhanced error handling for MOUNT over UDP
    
    Change-Id: I42ee69415d064b98af4f49773026562824f684d1
    BUG: 1118311
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/8346
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 1642ee54cf78bb2d117f7ffb2a180acf12c54ab6
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Oct 2 05:18:20 2014 +0200

    Regression test portability: rpc-coverage
    
    - pull include.rc when running rpc-coverage.sh to get BSD stat(1)
      compatibility.
    - fix type in statfs_test and use mode instead of size so that
      it cannot pass by chance like it did.
    - BSD tail does not support --pid; Avoid that option by making
      the test simplier.
    - Use a subshell instead of pushd/popd, which seems more reliable.
    - Use flock -x instead of flock -e: same result on Linux, compatible
      with NetBSD flock.
    - when using file descriptors in the shell, avoit too high numbers
      otherwise we can easily hit the descriptor limit.
    
    BUG: 1129939
    Change-Id: I51bad02a0ef47f20e4a2c49098c1c6701b7e6b09
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8566
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 3e7508eafb1955a071da9108dce5ce1cf435f4f3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Oct 6 22:46:44 2014 +0200

    build: include contrib/umountd in the 'make dist' tarball
    
    When running 'make dist' on Linux, the new contrib/umountd directory and
    contents is not included in the resulting tarball. This causes the build
    from the tarball to fail.
    
    Change-Id: Ic575040212d91c6368f04b015cc9d2d5b2969a3a
    BUG: 1129939
    Reported-by: Emmanuel Dreyfus <manu@netbsd.org>
    URL: http://supercolony.gluster.org/pipermail/gluster-devel/2014-October/042441.html
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8907
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dee517728dbccf40077f45a286e9678f2aede8df
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Oct 1 20:41:58 2014 +0200

    ec: Fix memory leak caused by undestroyed fops
    
    Operations processed by ec_dispatch_one() were not correctly
    completed by ec_complete(), leaving some structures in memory.
    
    Now ec_complete() also calls ec_resume() for this type of fops.
    
    Change-Id: Iaf0f2e8227399ebb735db9f1bd007593e0ece041
    BUG: 1148520
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8896
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 473c34f895c49bf2bd327ece586d3613cd86c068
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Sep 21 13:57:47 2014 +0200

    Do not hardcode umount(8) path, emulate lazy umount
    
    1) Use a system-dependent macro for umount(8) location instead of
    relying on $PATH  to find it, for security and portability sake.
    
    2) Introduce gf_umount_lazy() to replace umount -l (-l for lazy) invocations,
    which is only supported on Linux; On Linux behavior in unchanged. On other
    systems, we fork an external process (umountd) that will take care of
    periodically attempt to unmount, and optionally rmdir.
    
    BUG: 1129939
    Change-Id: Ia91167c0652f8ddab85136324b08f87c5ac1e51d
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8649
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit baa6f0ad759af024e4731a0f3889fe857ae2f1bf
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Oct 2 02:14:07 2014 +0200

    POSIX filesystem compliance: PATH_MAX
    
    POSIX mandates the filesystem to support paths of lengths up to
    _XOPEN_PATH_MAX (1024).  This is the PATH_MAX limit here:
    http://pubs.opengroup.org/onlinepubs/009604499/basedefs/limits.h.html
    
    When using a path of 1023 bytes, the posix xlator attempts to create
    an absolute path by  prefixing the 1023 bytes path by the brick
    base path. The result is an absolute path of more than _XOPEN_PATH_MAX
    bytes which may be rejected by the backend filesystem.
    
    Linux's ext3fs PATH_MAX seems to defaut to 4096, which means it
    will work (except if brick base path is longer than 2072 bytes but
    it is unlikely to happen. NetBSD's FFS PATH_MAX defaults to 1024,
    which means the bug can happen regardless of brick base path length.
    
    If this condition is detected for a brick, the proposed fix is to
    chdir() the brick glusterfsd daemon to its brick base directory.
    Then when encountering a path that will exceed _XOPEN_PATH_MAX once
    prefixed by the brick base path, a relative path is used instead
    of an absolute one. We do not always use relative path because some
    operations require an absolute path on the brick base path itself
    (e.g.: statvfs).
    
    At least on NetBSD, this chdir() uncovers a race condition which
    causes file lookup to fail with ENODATA for a few seconds. The
    volume quickly reaches a sane state, but regression tests are fast
    enough to choke on it. The reason is obscure (as often with race
    conditions), but sleeping one second after the chdir() seems to
    change scheduling enough that the problem disapear.
    
    Note that since the chdir() is done if brick backend filesystem
    does not support path long enough, it will not occur with Linux
    ext3fs (except if brick base path is over 2072 bytes long).
    
    BUG: 1129939
    Change-Id: I7db3567948bc8fa8d99ca5f5ba6647fe425186a9
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8596
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a97ad9b69bb17f2351c59512fa9c6cb25d82b4da
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Sep 18 18:42:34 2014 +0200

    test/ec: Fix spurious failures caused by self-heal
    
    The sha1sum of a file may update the access time of that file.
    If this happens while a brick is down, as it is forced in the
    test, that brick doesn't get the update, getting out of sync.
    
    When the brick is restarted, self-heal repairs the file, but
    the test shouldn't access brick contents until self-heal finishes.
    If this is combined with a kill of another brick before self-heal
    has finished repairing the file, the volume could become inaccessible.
    
    Since the purpose of these tests is only to check ec functionality
    (there is another test that checks self-heal), the test that corrupts
    the file has been removed.
    
    Additional checks to validate the state of the volume have been added
    to avoid some timing issues.
    
    BUG: 1144108
    Change-Id: Ibd9288de519914663998a1fbc4321ec92ed6082c
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8892
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7e76bd24305ee29506dd11be5a0691cfa65b6d0c
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Sep 30 17:47:26 2014 +0200

    ec: Add state dump support
    
    Change-Id: I4504f3050674dde217e79af28cb4d2b5370fe2d5
    BUG: 1148010
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8891
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0a8371bdfdd88e662d09def717cc0b822feb64e8
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Sep 29 17:27:14 2014 -0400

    extras: reverse test for '}' vs. following 'else' placement
    
    The two-line form "}\nelse {" has been more common than the one-line
    form "} else {" in our code for years, and IMO for good reason (see
    the comment in the diff).
    
    Change-Id: Ic22c76fe76f0d91300daff36e755a18a8db58852
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8888
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f2131b8c79641c1bf9e20657757bcc9a62a0625a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Sep 29 20:03:58 2014 +0200

    gNFS: allow truncate() from SETATTR over NFS for owner
    
    NFSv3 does not have a TRUNCATE procedure, instead it is part of the
    SETATTR (change the 'size' attribute). SETATTR with a new 'size'
    succeeds on other NFS-servers, even when the owner of the file does not
    have write permissions. Make Gluster/NFS behave the same way, by
    checking if the RPC/pid comes from the NFS-server, and allow truncate()
    when the file is owned by the user calling SETATTR.
    
    BUG: 955753
    Change-Id: I4b7cb8efe5a2032c6cd2eef6af610032f76d8b39
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8889
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>

commit 0e1419d6fbf008b6384236d6103066afbc92dd77
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Oct 1 06:18:50 2014 +0200

    Regression test portability: truncate
    
    Use truncate -s 1M instead of truncate --size=1m for portability sake
    
    BUG: 1129939
    Change-Id: I5bf6ca1f9bb4fa3c91796a659a06bf368776b3e5
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8894
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit f54dd171bca5086f11733a1c4fe578e838b2e6fd
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 29 15:23:21 2014 +0200

    Regression test portability: stat
    
    Improve BSD compatibility for stat. The new version attemps to spawn
    less stat subprocesses.
    
    Also add translation for %X %Y and %Z
    
    BUG: 1129939
    Change-Id: I2b2134f9e8336a952aee6c7679ba0491abd5a35c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8565
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 192d5e6654cf4b3ebcfd6b36c0693955d0c41868
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Sep 22 17:56:57 2014 +0200

    Regression test portability: rpmbuild
    
    rpmbuild is required, check for its presence.
    
    BUG: 1129939
    Change-Id: Iae8534bf897a4605620277688a180d6542c1c80b
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8810
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 443e48abf9b373bb1a8c56d016aad3b974554b80
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Aug 20 21:50:06 2014 +0530

    cluster/afr: Add afr-v1 xattr compatibility
    
    All the special cases v1 handles and also
    self-accusing pending changelog from v1 pre-op also is handled
    in this patch.
    
    Change-Id: Ie10f71633fb20276f01ecafbd728f20483e7029c
    BUG: 1128721
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8536
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f95a25c35e1ced6a3c05030d34555b757b14e1c9
Author: vmallika <vmallika@redhat.com>
Date:   Mon Sep 29 13:02:30 2014 +0530

    glusterd/quota: Heal pgfid xattr on existing data when the quota is
    enable
    
    The pgfid extended attributes are used to construct the ancestry path
    (from the file to the volume root) for nameless lookups on files.
    As NFS relies on nameless lookups heavily, quota enforcement through NFS
    would be inconsistent if quota were to be enabled on a volume with
    existing data.
    
    Solution is to heal the pgfid extended attributes as a part of lookup
    perfomed by quota-crawl process. In a posix lookup check for pgfid xattr
    and if it is missing set the xattr.
    
    Change-Id: I5912ea96787625c496bde56d43ac9162596032e9
    BUG: 1147378
    Signed-off-by: vmallika <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8878
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c65d4ea8a10a4004cab145aaea0362e03b209267
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Sep 29 03:06:24 2014 +0200

    Fix invalid seekdir() usage
    
    According to POSIX, seekdir() should only be given offset obtained from
    telldir() on the same DIR *
    http://pubs.opengroup.org/onlinepubs/9699919799/functions/seekdir.html
    
    Code from afr-self-heald.c and index.c is operating outside of the
    specification, by doing using seekdir() with offset from a previously
    open/close/re-open directory. This seems to work on Linux (although with
    no guarantee it will always in the future). On NetBSD the seekdir()
    with a in invalid offset is a nilpotent operation, and causes an infinite
    loop, since index_fill_readdir() always restart from the beginning of the
    directory.
    
    The situation is fixed by using a non anonymous fd in afr-self-heald.c:
    we explicitely open the directory so that it remains open on the brick
    side during the timeframe where we want to reuse offsets in seekdir().
    This requires adding an opendir fop in index xlator.
    
    If the brick was not updated, the opendir will fail and we fallback
    to the standard violating approach for backward compatibility on Linux.
    On other systems we fail since it never worked.
    
    While there, add tests to check seekdir() success in index and posix
    xlators, so that incorrect usage from calling code produce an explicit
    error instead of an infinite loop. We can only do it on non Linux systems,
    for the sake of backward compatibility when the brick was updated but
    not the client.
    
    BUG: 1129939
    Change-Id: I88ca90acfcfee280988124bd6addc1a1893ca7ab
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8760
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 36d2975714ed6ef98c0f86a2fac22fc382ea8a9d
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Sep 29 15:48:55 2014 +0200

    doc: added documentation for dispersed volumes
    
    Change-Id: I8a8368bdbe31af30a239aaf8cc478429e10c3f57
    BUG: 1147563
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8885
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 535c4259119ca3beef2fee1526930e8be42bdd5d
Author: GauravKumarGarg <ggarg@redhat.com>
Date:   Mon Sep 29 14:03:49 2014 +0530

    glusterd: Perform brick order check in originator node.
    
    Currently in case of multi node cluster brick-order check for
    replicate volume done on every node. Its waste of time to perform
    brick order check on every node.
    
    This change will perform brick order check only at originator node.
    
    Change-Id: I8687fd28e587de8a280a9003b015ccd5729c9740
    BUG: 1091935
    Signed-off-by: ggarg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/8881
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 2736421b26ef03724297b62b4f07ad847c135709
Author: Sachin Pandit <spandit@redhat.com>
Date:   Thu Sep 25 08:32:52 2014 +0530

    USS : Decide the log entry based on the type of graph.
    
    Problem : When a lookup is issued, and if the entry is not found
    then snapview-client will log failure stating that
    "Lookup on normal graph failed with error Stale file handle"
    irrespective of type of graph it received call back from.
    
    Solution : Introduced a check to find out the graph from which
    the snapview-client received call-back.
    
    Change-Id: Iadd5b525c394be3675d40231711058e1cf1396cd
    BUG: 1146479
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8851
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 94045e4ae779b1bde54ad1dd0ed87981a6872125
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Sep 17 11:33:23 2014 +0530

    cluster/afr: Launch self-heal only when all the brick status is known
    
    Problem:
    File goes into split-brain because of wrong erasing of xattrs.
    
    RCA:
    The issue happens because index self-heal is triggered even before all the
    bricks are up. So what ends up happening while erasing the xattrs is, xattrs
    are erased only on the sink brick for the brick that it thinks is up leading to
    split-brain
    
    Example:
    lets say the xattrs before heal started are:
    brick 2:
    trusted.afr.vol1-client-2=0x000000020000000000000000
    trusted.afr.vol1-client-3=0x000000020000000000000000
    
    brick 3:
    trusted.afr.vol1-client-2=0x000010040000000000000000
    trusted.afr.vol1-client-3=0x000000000000000000000000
    
    if only brick-2 came up at the time of triggering the self-heal only
    'trusted.afr.vol1-client-2' is erased leading to the following xattrs:
    
    brick 2:
    trusted.afr.vol1-client-2=0x000000000000000000000000
    trusted.afr.vol1-client-3=0x000000020000000000000000
    
    brick 3:
    trusted.afr.vol1-client-2=0x000010040000000000000000
    trusted.afr.vol1-client-3=0x000000000000000000000000
    
    So the file goes into split-brain.
    
    Change-Id: I1185713c688e0f41fd32bf2a5953c505d17a3173
    BUG: 1142601
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8755
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3ba5f1d38d58e72d562f6d19498bed00fb2727bc
Author: Anuradha <atalur@redhat.com>
Date:   Fri Sep 26 14:18:05 2014 +0530

    cluster/afr : Fix incorrect looping of index healer
    
    Sending appropriate return value from afr_selfheal()
    fixes the issue.
    
    Credits : Krutika Dhananjay and Pranith Kumar.
    
    Change-Id: I01dbd49476f6bfbd02028fdde1f60cc0324a1e39
    BUG: 1146812
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8868
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 37ee11f4d42bff1f46fae7d2755e0d6d8a55e572
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Sep 26 10:12:47 2014 -0700

    Sane default for SSL on OSX
    
    - /opt/local is not preferred anymore use /usr/local
    
    Change-Id: I30cad4cbd28850063f26121cace05371e13bb314
    BUG: 1129939
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8872
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2a2f1130689d388f26b41f5df3e0bf572e0addb5
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Aug 29 10:42:02 2014 +0000

    glusterfs: allow setxattr of keys with null values.
    
    Disk based file systems allow to get/set extended attribute key-value pairs where
    value can be null. Fuse/libgfapi clients must be able to do the same on a
    gluster volume.
    
    Change-Id: Ifc11134cc07f1a3ede43f9d027554dcd10b5c930
    BUG: 1135514
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8567
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7113d873af1f129effd8c6da21b49e797de8eab0
Author: Kotresh HR <khiremat@redhat.com>
Date:   Thu Sep 25 17:34:43 2014 +0530

    geo-rep: Fix rename of directory syncing.
    
    The rename of directories are captured in all distributed
    brick changelogs. gsyncd processess these changelogs on
    each brick parallellaly. The first changelog to get processed
    will be successful. All subsequent ones will stat the 'src'
    and if not present, tries to create freshly on slave. It
    should be done only for files and not for directories.
    Hence when this code path was hit, regular file's blob
    is sent as directory's blob and gfid-access translator
    was erroring out as 'Invalid blob length' with errno as
    'ENOMEM'
    
    Change-Id: I50545b02b98846464876795159d2446340155c82
    BUG: 1146823
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8865
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit cf595e84a5d7fe3c99434dac71807f82e606cec4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Sep 29 08:48:40 2014 +0530

    cluster/afr: Fix inode leak
    
    Change-Id: I723b65d6fcae5bd39c0daece3b2f48baf0a72166
    BUG: 1145471
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8875
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e26b62b1a2e8ee80e025ad3bd3e841522730f695
Author: hchiramm <hchiramm@redhat.com>
Date:   Thu Sep 25 11:28:21 2014 +0530

    spec: Change summary of glusterfs to distributed file system.
    
    BUG:1146519
    Change-Id: I9b24321d9e677b535f8d79691862cf919553d635
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8844
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 3d36edb00c2adad9a957a445aafac3e800964bb1
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Sep 23 07:46:16 2014 +0200

    Use sane OS-dependent defaults for SSL configuration
    
    Current code assumes /etc/ssl exists, which may not be the case.
    Attempt to guess sane default for a few OS.
    
    BUG: 1129939
    Change-Id: I0f3168f79b8f4275636581041740dfcaf25f3edd
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8790
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8e57090f7da4027c46176c9786372a00e22df69d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Sep 25 15:28:03 2014 +0200

    Do not forbid fallocate on non Linux systems
    
    Linux fallocate() differs from posix_fallocate() by
    an extra flag that can have the FALLOC_FL_KEEP_SIZE value;
    
    Do not test FALLOC_FL_KEEP_SIZE existence to enable fallocate()
    in posix xlator, as sys_fallocate() in libglusterfs provides
    support for both implementations.
    
    BUG: 1129939
    Change-Id: Idf41a0396028a15e81281791bf6912d7fd674e3f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8856
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5123949bebc3520ed3d64986420c139801013c60
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 25 16:27:52 2014 +0530

    cluster/afr: More dict_t leak fixes
    
    Change-Id: I6618b7b2df0f88a3e6252f9136135cf402147a37
    BUG: 1134221
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8852
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c3101c66ba09a8e80eefeb68cf5ca1ab78dd8cae
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 25 09:11:46 2014 -0400

    glusterfs.spec.in: add psmisc to -server subpackage
    
    apparently some minimalist installs omit psmisc
    psmisc is needed for the killall in various %pre and %post scriptlets
    
    smarter logic for restarting glusterd in %post server
    
    Change-Id: I505573b364cc27321bb4117a387bdf71fe3ce310
    BUG: 1146426
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8867
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 3c29c50cf60135245290133fbfed11aa3cf01e39
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Sep 17 12:59:52 2014 +0530

    geo-rep: fix same file different gfid in master and slave
    
    While processing RENAME in changelog, if the file is unlinked
    in master, then geo-rep was sending UNLINK to slave instead of
    RENAME.
    
    If rsync job fails if one of the file failed to sync in the job.
    This patch adds logic to remove GFID from data list if the same
    changelog has UNLINK entry for it after the DATA. Or it removes
    those GFIDs during retry of changelogs processing.
    
    BUG: 1143853
    Change-Id: I982dc976397cd0ab676bb912583f66a28f821926
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8761
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 60a75cdca76b0a4b83eb6f5bc70a320d586d79aa
Author: Gaurav Kumar Garg <ggarg@redhat.com>
Date:   Wed Sep 10 17:33:20 2014 +0530

    glusterd: file-snapshot and features-encryption options should be validate correctly
    
    By giving non-boolean value to volume set command for features.file-snapshot
    and features.encryption option the command failed after that subsequent
    volume set request with valid value of the existing any volume set option
    fail.
    
    Previously when user supplies a non-boolean value in volume set command
    for features.file-snapshot and features.encryption option's then
    validation of that value was done by volinfo->dict but actual value
    of that option store in input dictonary. Now with this change it
    will refer correct dictonary for validation of supplies value.
    
    Change-Id: I4a93d8be848cd33fdf4b4eb9b1a8d15ec9d1e66a
    BUG: 1140162
    Reviewed-on: http://review.gluster.org/8688
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit adace43107e3a77dcb3d24c87e7a631c0f099602
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Sep 16 17:11:39 2014 +0200

    32 bit fix: use off_t and not size_t for truncate()
    
    Make sure off_t and not size_t is used when holding file offsets for
    ftruncate()/truncate(). It works on 64 bit machines where
    sizeof(size_t) == sizeof(off_t) == 8, but breaks for big offsets on 32 bit
    machines because sizeof(size_t) == 4 and sizeof(off_t) == 8
    
    BUG: 1129939
    Change-Id: Ia2637be772ba9b11731d59fdbffbd269f0ff56c8
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8742
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 94b0ac65c35d5e167d8e761f198edffe78c7dab2
Author: Bala.FA <barumuga@redhat.com>
Date:   Wed Jul 2 14:21:39 2014 +0530

    build: remove /sbin/ldconfig as interpreter
    
    using /sbin/ldconfig as interpreter in pre/post/postun throws error
    /sbin/ldconfig: relative path `1' used to build cache
    
    BUG: 1145989
    Change-Id: Ic321f200d92d2e49ff797965a006f63f483d29be
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/8835
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2471aa9aa23960e2e5e3a4db1b6e3e8388e2476e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 23 17:03:53 2014 +0530

    cluster/afr: Fix locking issues in entry self-heal
    
    Original reporter of the bug & designer of the solution:
            Pranith Kumar K <pkarampu@redhat.com>
    
    Change-Id: I9ed89aa92e4cd0f8049f5f6c7a3701e52989ae5e
    BUG: 1128721
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8837
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c16408ab40e882f6e4ab41c6acb403717cabd1bc
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Sep 24 15:52:58 2014 -0700

    OSX/FreeBSD: Regression fix
    
    Introduced in "1f6e992f1aaa676be5bd47d17e58f1171825cf43"
    
    Change-Id: I655cf613ca93a749ab5403cb3ec038e739993e2e
    BUG: 1146279
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8841
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>

commit b097225202629448e3b10dc4160125c376971682
Author: ggarg <ggarg@redhat.com>
Date:   Tue Apr 29 09:58:16 2014 +0530

    glusterd: Move brick order check from cli to glusterd.
    
    Previously the brick order check for replicate volumes on volume
    create and add-brick was done by the cli. This check would fail
    when a hostname wasn't resolvable and would question the user
    if it was ok to continue. If the user continued, glusterd would
    fail the command again as the hostname wouldn't be resolvable.
    This was unnecessary.
    
    This change, moves the check from cli into glusterd. The check
    is now performed during staging of volume create after the
    bricks have been resolved. This prevents the above condition
    from occurring.
    
    As a result of this change, the user will no longer be
    questioned and given an option to continue the operation
    when a bad brick order is given or the brick order check
    fails. In such a case, the user can use 'force' to bypass
    the check and allow the command to succeed.
    
    Change-Id: I009861efaf3fb7f553a9b00116a992f031f652cb
    BUG: 1091935
    Signed-off-by: ggarg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/7589
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 70d76f20ee127fe7e8e52b2d67e2362283a01f34
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Sep 13 12:08:56 2014 +0530

    cluster/afr: Fix spurious metadata self-heals
    
    - Added logging for metadata and data self-heals which helped
      in debugging this issue.
    - Added checks to skip self-heals when no sinks are available to heal
    
    Change-Id: I0d50dceb84cd9ad4fe00e0b749ddf7d4ff42348a
    BUG: 1128721
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8709
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bd592f8b8379087604f35c3b377f6e94b9e1697d
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Sep 19 19:08:05 2014 +0530

    protocol: Log ENODATA & ENOATTR logs at DEBUG loglevel in removexattr_cbk.
    
    Prevents messages of the following type from being seen by default in the log files:
    
    [2014-09-19 07:57:39.877806] W
    [client-rpc-fops.c:1232:client3_3_removexattr_cbk] 0-<volume_name>-client-0:
    remote operation failed: No data available
    [2014-09-19 07:57:39.877963] W
    [client-rpc-fops.c:1232:client3_3_removexattr_cbk] 0-<volume_name>-client-1:
    remote operation failed: No data available
    
    Change-Id: I3b1a121b0fc272eb772547275bb8085ed19db5a1
    BUG: 1144527
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/8781
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3b871bee4a0ad3bc8b393ba23bfcf3ad6886cf42
Author: Anuradha <atalur@redhat.com>
Date:   Tue Sep 23 18:24:09 2014 +0530

    cluster/afr: Fixed mem leaks in self-heal code path.
    
    AFR_STACK_RESET previously didn't cleanup afr_local_t,
    leading to memory leaks. With this patch, cleanup is
    done.
    
    All credit goes to Pranith Kumar Karampuri.
    
    Change-Id: I3c727ff4bb323dccb81da4b3168ac69bb340d17d
    BUG: 1145471
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8821
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6e8ad12fbac943336f9eb8d97bf2e0bedb9fb225
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Sep 22 16:48:50 2014 -0400

    build: remove warnings for recommended style
    
    Specifically:
    
     * space before function arguments
    
     * brace around single statement
    
    Ideally we would *reverse* these tests so they warn under the exact
    opposite conditions, but that would mean learning the internals of a
    script written in a defective language with cryptic variable names and
    too few comments.  Life's too short.  For now, just cutting down on some
    of the spam (which might obscure more serious issues) should suffice.
    
    BUG: 1120646
    Change-Id: I5ec684d0d788a34f29af9b1761743c8860973993
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8813
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 2288fec13e5fa8f1b2493fd75e35f748460b2039
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Sep 22 10:59:37 2014 -0700

    extras/checkpatch.pl: update coding guidelines script
    
    - Allow 'quoted string split across lines' since its a
      GlusterFS common practice
    - Remove a useless "+" - perl 5.20 complains with following
      warning "Useless use of greediness modifier '+'"
    
    Change-Id: Ibaf276ec84757b3ecc3e6db7f5e720b8e8a12dff
    BUG: 1120646
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8811
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6ddfdde6fb8de21c46442b4b6b15d5b6b1eff4e4
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Sep 23 07:03:11 2014 +0530

    doc/snapshot : admin guide updation.
    
    Change-Id: I1980bc0984f941cd415fbc754495353f561155a8
    BUG: 1145069
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8817
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5136c938dddd909ad7a998afa643dc3dcaa6233d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Sep 20 06:57:24 2014 +0200

    Do not hardcode setfattr(1) path
    
    Turn setfattr(1) absolute path into an OS-dependant macro. Let compiler
    option override it to fit custom installation if needed.
    
    BUG: 1129939
    Change-Id: I8f469c5741a85b6e8d8f6299a9540b3d64611d2f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8786
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5f79d6e08fbb930aa67dd59eb39cbece6f138b59
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Sep 18 16:50:47 2014 +0200

    ec: Add config information in an xattr
    
    To simplify backward compatibility of the ec xlator when some
    parameter or the implementation itself is changed, a new xattr
    is added to each file with the configuration needed to recover
    it.
    
    The new attribute is called 'trusted.ec.config', and it's a 64-bit
    value containing the following information:
    
        8 bits: version of the config information (currently always 0)
        8 bits: algorithm used to encode the file (currently always 0)
        8 bits: size of the galois field (currently always 8)
        8 bits: number of bricks
        8 bits: redundancy
       24 bits: chunk size (currently 512)
    
    This new xattr could allow, in a future version, to have different
    configurations per file.
    
    Change-Id: I8c12d40ff546cc201fc66caa367484be3d48aeb4
    BUG: 1140861
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8770
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 933e5bd5a7b32394c7a3c6e84543dc48ed24a732
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Sep 23 04:53:47 2014 +0530

    test : Fix for spurious failure
    
    Problem : Once the features.uss is enabled it does not wait for
    the process to be created. And if we try to check for
    the pid of the snapd then it will not be present which
    causes a failure.
    
    Solution : Adding a EXPECT_WITHIN which waits to get the pid
    until certain time period.
    
    Change-Id: If075860173a996f9eee13b346e939686b94ec3f6
    BUG: 1145450
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8814
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 125e5428d31f5e0b659cbdb9ccdc310991fc1981
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 18 18:26:08 2014 +0530

    cluster/afr: Do not reset pending xattrs on gfid or type mismatch in entry-sh
    
    Change-Id: Ie27219a376382e2455a0fcc094f8b7eb243738ae
    BUG: 1140613
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8816
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e149a051bf226e16c6b7f1a816f998dace85d33d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 23 12:43:02 2014 +0530

    cluster/afr: Don't start heal when lookup succeeds on < 2 children
    
    Problem:
    When self-heal code doesn't see at least 2 successes on looking up children,
    then self-heal can't be done. What is happening now is if all the lookups fail
    then the pending changelog is all zeros in xattrs so all the children are
    becoming sources and leading to crashes when the code paths further assume that
    some data structures are populated properly
    
    Fix:
    Don't proceed with self-heals when < 2 children succeed lookups.
    
    BUG: 1128721
    Change-Id: Iffdf0feebb6f98812d9d01cdd0cf97f3e19ba76f
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8698
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 371bb42410ca5bbcf1f13ad1c8d015fcbe6ec5ce
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jun 19 15:31:46 2014 +0530

    glusterd: Authenticate management handshake requests
    
    Management handshake requests, which are used to validate op-version
    supported by the peers, are now only allowed if,
    - the glusterd doesn't have any other peer, or
    - the request was sent by another peer.
    
    This prevents the op-version of a peer being changed because of a
    connection attempt by an invalid peer.
    
    Change-Id: I248c386ed5ec4f8360e7b5e7f9ab74b7e8a7fc65
    BUG: 1109741
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8126
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f14d9bdd52b428466e7863d06c89b4684be3da07
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Sep 22 13:29:13 2014 +0530

    cluster/dht: Modified the calculation of brick_count
    
    Whenever new_layout is calculated for a directory,
    we calculate the number of childs of dht, who will get
    the actual(Non-zero) layout-range, and assign range
    to only those subvolume and other will get 0 as
    their layout->start and layout->stop value.
    
    This calculation is based on either
    a) weight_by_size or
    b) number of brick who will be assigned the non-zero range
    
    So if in case we are not assigning the layout based
    on weight_by_size, we should choose the "bricks_to_use"
    instead of "bricks_used".
    
    In regression test,
    we found that priv->du_stat[0].chunks was zero. In this
    case "bricks_used" variable will be zero, which will cause
    crash for
    
    chunk = ((unsigned long) 0xffffffff) / bricks__used;
    calculation.
    
    Change-Id: I6f1b21eff972a80d9eb22771087c1e2f53e7e724
    BUG: 1143835
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8792
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit de713588b81acc912b33b00474ea3cfa6620ceb1
Author: hchiramm <hchiramm@redhat.com>
Date:   Mon Sep 22 11:07:46 2014 +0530

    doc: Include details of thin volume creation in snapshot guide.
    
    Change-Id: I12b49c0e8af2cc3d91c29300fdfc47d772d380d7
    Signed-off-by: hchiramm <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8791
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 58f23090fc0af2d93c02da68b06e02d1263df499
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Sep 5 14:55:01 2014 +0530

    synctask: add backtrace per waiting task
    
    The backtrace is 'saved' in a per-task buffer.
    This would come handy while debugging code using
    synctasks.
    
    Change-Id: I732b275f6d15b31f31361f5ecf2ba47cacde9b54
    BUG: 1138503
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8622
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1b53756e50cb9ad5422292d7f4e1e6fe23357222
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Sep 3 11:03:06 2014 +0530

    glusterd: Add last successful glusterd lock backtrace
    
    Also, moved the backtrace fetching logic to a separate function.
    Modified the backtrace fetching logic able to work under memory pressure
    conditions.
    
    Change-Id: Ie38bea425a085770f41831314aeda95595177ece
    BUG: 1138503
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8584
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 0cbfe677f361cf49b182748f4b71ded13f6bc988
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 16 14:05:17 2014 -0400

    tests: regression, can't run `prove $t` in subdirs
    
    In various tests we already use the pattern:
    
      . $(dirname $0)/../include.rc
    
    to locate various .rc files.
    
    Use the same pattern we already use to also find the new env.rc
    
    Change-Id: I0d438446fa00be2c143b5cf46025866182c94814
    BUG: 1142419
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8754
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 258e61adb5505124925c71d2a0d0375d086e32d4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 18 14:36:38 2014 +0530

    cluster/dht: Fix dict_t leaks in rebalance process' execution path
    
    Two dict_t objects are leaked for every file migrated in success codepath.
    It is the caller's responsibility to unref dict that it gets from calls to
    syncop_getxattr(); and rebalance performs two syncop_getxattr()s per file
    without freeing them.
    
    Also, syncop_getxattr() on GF_XATTR_LINKINFO_KEY doesn't seem to be using
    the response dict. Hence, NULL is now passed as opposed to @dict to
    syncop_getxattr().
    
    Change-Id: I5a4b5ab834df3633dea994f239bbdbc34cbe9259
    BUG: 1142052
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fb6702b7f8ba19333b7ba4af543d908e3f5e1923
Author: Gu Feng <flygoast@126.com>
Date:   Tue Sep 9 18:00:22 2014 +0800

    socket: Fixed parsing RPC records containing multi fragments
    
    In __socket_proto_state_machine(), when parsing RPC records containing
    multi fragments, just change the state of parsing process, had not
    processed the memory to coalesce the multi fragments.
    
    Change-Id: I5583e578603bd7290814a5d26885b31759c73115
    BUG: 1139598
    Signed-off-by: Gu Feng <flygoast@126.com>
    Reviewed-on: http://review.gluster.org/8662
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 0ee0cfae80f7b17115b78d76610b995edb1bfa8b
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Sep 10 23:43:07 2014 +0200

    ec: Fix invalid inode lock in ftruncate
    
    The fops 'truncate' and 'ftruncate' share some code and inodelk()
    was always made against the inode inside the loc_t structure
    instead of that of fd_t. Since ftruncate has the loc initialized
    to NULL, this fop was executed without any lock, allowing some
    concurrent modifications in the file size.
    
    Also changed the way in which 'fop' and 'ffop' are differentiated
    in shared code. Now it uses 'id' field instead of checking if 'fd'
    is NULL.
    
    Change-Id: Ibd18accf2652193b395a841b9029729e5f4867c6
    BUG: 1140396
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8695
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f32378b660dab5f3f311da8252969a7da16898f4
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Sep 15 11:57:43 2014 +0200

    ec: Fix some size_t vars to 64 bits even on 32 bits machines
    
    The 64 bits 'trusted.ec.size' extended attribute was incorrectly
    computed on 32 bits machines due to an overflow on negative
    numbers.
    
    Also changed some potentially dangerous uses of size_t in other
    places.
    
    Change-Id: Id76cfe49a2f350e564b5c71d8c8644fb9ce86662
    BUG: 1125312
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8738
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c788a7784d8526b72714d60bac6e1e09ae985a84
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Jun 25 21:22:49 2014 -0700

    extras/checkpatch.pl: linux kernel style patch verification
    
    This is to bring in adherence to coding policy, prior to patch
    submission for review.
    
     - no tabs
     - no whitespace
     - indentation (linux style) etc.
    
    This is in the interest at large for the GlusterFS codebase
    to be more cleaner and readable.
    
    ./rfc.sh - now supports running this for all patches diverged
    from "origin/master" revision.
    
    NOTE: One should take this as a handle for good guidelines and
    never use it as a tool for correctness, use common-sense in all
    the cases ;-)
    
    Change-Id: Ib9a5ed207cde152cb92b8d38cec83e8ce9ef7f28
    BUG: 1120646
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8181
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anders Blomdell <anders.blomdell@control.lth.se>

commit 1e1b709a4b438dfa768fd4c645e081ede06e7e14
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sun Jun 8 00:46:29 2014 +0530

    storage/posix: Log when mkdir is on an existing gfid but non-existent
    path.
    
    consider following steps on a distribute volume
    
    1. rename (src, dst) on hashed subvolume
    2. snapshot taken
    3. restore snapshots and do stat on src and dst
    
    Now, we end up with two directories src and dst having same gfid,
    because of distribute creating directories on non-existent subvolumes
    as part of directory healing.
    
    This can happen even with race between rename and directory healing in
    dht-lookup. This can lead to undefined behaviour while accessing any
    of both directories. Hence, we are logging paths of both
    directories, so that a sysadmin can take some corrective action when
    (s)he sees this log. One of the corrective action can be to copy
    contents of both directories from backend into a new directory and
    delete both directories.
    
    Since effort involved to fix this issue is non-trivial, giving this
    workaround till we come up with a fix.
    
    Change-Id: I38f4520e6787ee33180a9cd1bf2f36f46daea1ea
    BUG: 1105082
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8008
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 331e9e2051addfcc394c933a85046f450961e1af
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Sep 4 23:58:18 2014 +0530

    syncop: Invoke dict_unref() in inodelk only if dictionary is not NULL
    
    In the absence of this check, logs can get flooded with messages like this when rebalance is run:
    
    [2014-09-04 17:48:07.148262] W [dict.c:480:dict_unref] (-->/lib64/libc.so.6()
    [0x30daa47a00] (-->/usr/local/lib/libglusterfs.so.0(synctask_wrap+0x12)
    [0x7fa20b7c6ec2]
    (-->/usr/local/lib/glusterfs/3.7dev/xlator/cluster/distribute.so(dht_migrate_file+0x23f)
    [0x7fa200fdb58f]))) 0-dict: dict is NULL
    
    
    Change-Id: I4c93e4485293b35d86ba07df4d583d2758ec3f49
    BUG: 1130888
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/8601
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit 6f5bb1bfc520a91d70a02a9c13104c798e2dba14
Author: Anuradha <atalur@redhat.com>
Date:   Mon Sep 8 18:32:04 2014 +0530

    cluster/afr: Set all the xattrs needed by index xlator
    
    Index xlator removes the index file from indices
    xattrop directory in case the value for keys sent
    are zero.
    
    If all the required keys are not set by afr
    then index file might be removed in an invalid
    way.
    
    With this change all the keys required by index
    xlator are set by afr such that invalid removal of
    files does not occur.
    
    Change-Id: Idbed0764a95157fd5cab8d6685057a43788fc7df
    BUG: 1139230
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8652
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 68e062ea6e3e6957cc6212f778950cce54078a90
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Aug 7 06:37:30 2014 +0200

    Regression test portability: arequal-checksum
    
    Emulate GNU libc extension FTW_SKIP_SUBTREE for system that lack it.
    FTW_ACTIONRETVAL is another GNU libc extension we just ignore now.
    
    BUG: 764655
    Change-Id: I25d9641055a30fe72b4e248f51b53b2a3ba637e9
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8427
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b30f9e56cd92906ccb97e046b8928d7de76b4b50
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Aug 10 10:08:52 2014 +0200

    Do not assume sizeof(size_t)
    
    This fixes an assumption that sizeof(size_t) == sizeof(uint64_t), which
    is not guaranteed. At least on NetBSD/i386, size_t is 32 bit long.
    
    Caught by tests/basics/file-snapshot.t
    
    BUG: 764655
    Change-Id: Ib7620a2ffe8758521886af37bc280101a040d860
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8441
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit c7437f35df1127c05a4df0f7bf3ae95b71b7831e
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Sep 11 17:31:59 2014 +0530

    cluster/dht: Changed log level to DEBUG
    
    Change-Id: Ia4dde95367b44d63f57f0840c2a2f351b1cfb072
    BUG: 1138602
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8697
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 323ac2adb6a50713bd29c5bda028b6bf47bf2865
Author: Justin Clift <justin@gluster.org>
Date:   Wed Jun 25 22:52:50 2014 +0100

    Typo fix THANKS message
    
    BUG: 1142045
    Change-Id: I9323453d475779a01516adcb4c959e6ac4cf689c
    Reviewed-on: http://review.gluster.org/8174
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d97863562bb0d2f685df3d2e3aa4bef1299c8307
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Jul 14 17:34:04 2014 +0200

    ec: Optimize read/write performance
    
    This patch significantly improves performance of read/write
    operations on a dispersed volume by reusing previous inodelk/
    entrylk operations on the same inode/entry. This reduces the
    latency of each individual operation considerably.
    
    Inode version and size are also updated when needed instead
    of on each request. This gives an additional boost.
    
    Change-Id: I4b98d5508c86b53032e16e295f72a3f83fd8fcac
    BUG: 1122586
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8369
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 2be54585002cd1c9d02928b89a02047b58dd6aed
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Jul 15 13:42:28 2014 +0200

    ec: Only heal data/metadata when inode has enough information
    
    Sometimes loc_t structure in a heal request doesn't contain enough
    information to do an inodelk call (basically the gfid is missing).
    In these cases, self heal only recovers entry information.
    
    Change-Id: I459990c7df728ff4baf164df046672ddcde3efa5
    BUG: 1122581
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8368
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 3e1935c8141c4f0ff3ee5af30c62a02da772666b
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Sep 10 16:51:19 2014 +0530

    features/quota: fixes to dentry management code in rename.
    
    1. After a successful rename (src, dst), the dentry
     <dst-parent, dst-basename> would be associated with src-inode.
    
    2. Its src inode that survives if both of src and dst are present.
    
    The fixes are done based on the above two observation.
    
    Change-Id: I7492a512e3732b1455c243b02fae12d489532bfb
    BUG: 1140084
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8687
    Reviewed-by: susant palai <spalai@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 245eec73fb26654608b2524317f4a4af5f9ef61c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Sep 14 16:51:25 2014 +0530

    cluster/afr: Handle EAGAIN properly in inodelk
    
    Problem:
    When one of the brick is taken down and brough back up in a replica pair, locks
    on that brick will be allowed. Afr returns inodelk success even when one of the
    bricks already has the lock taken.
    
    Fix:
    If any brick returns EAGAIN return failure to parent xlator.
    
    Change-Id: I5b842d0fc094359cc4231494053d2bfeb606bbbe
    BUG: 1141539
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8710
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7c2c5afb8db02628aba3097151c4f6383508b397
Author: Justin Clift <justin@gluster.org>
Date:   Mon Sep 15 08:44:25 2014 +0100

    osx: LaunchDaemon plist filename should start with org instead of com
    
    Change-Id: I5e06bcc473224667387c555355d7e1e81bf4911b
    BUG: 1141659
    Reviewed-on: http://review.gluster.org/8734
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 926522a3fe8d2d59aeb357c1e4745a21e76e77f2
Author: Justin Clift <justin@gluster.org>
Date:   Mon Sep 15 09:48:05 2014 +0100

    osx: Remove legacy extras/MacOSX directory
    
    BUG: 1141682
    Change-Id: Ic84171b070985a11b70d4548aa5e507a121d2164
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/8736
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 63b1c2e2a4cda315e8242f5bc0cf39a13319dae1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Sep 12 16:54:45 2014 +0530

    tests: Fix typo in M2 definition
    
    Thanks to Anoop CS for finding the bug
    
    Change-Id: I237e3a396967096b8e49200aed279af970e0a4d5
    BUG: 1141167
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8707
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5d6f55ed9f122d3aeab583bb0ad16cb0c392a339
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jul 17 12:15:54 2014 +0530

    snapview-server: get the handle if its absent before doing any fop
    
    * Now that NFS server does inode linking in readdirp, it can resolve the
      gfid (i.e. find the right inode from its inode table) present in the
      filehandle sent by the NFS client on which a fop came. So instead of
      sending the lookup on that entry, it directly sends the fop. But
      snapview-server does not get the handle for the entries in readdirp
      (because doing a lookup on each entry via gfapi would be costly. So it
       waits till a lookup is done on that inode, to get the handle and the
       fs instance and fill it in the inode context). So when NFS resoves the
       gfid and directly sends the fop, snapview-server will not be able to
       perform the fop as the inode contet would not contain the fs instance
       and the handle. So fops should check for the handle before doing gfapi
       calls. If the handle and fs instance are not present in the inode context
       they should get them by doing an explicit lookup on the entry.
    
    Change-Id: Idd648fbcc3ff6aadc3b63ff236561ca967b92f5d
    BUG: 1115949
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8324
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2bce69036fdbd760f03fe55ac4954b5fa9febfeb
Author: hchiramm <hchiramm@redhat.com>
Date:   Fri Sep 12 11:37:09 2014 +0530

    doc: Move bd translator documentation to xlators directory.
    
    Change-Id: I21bd1cc6d0220035d28ca15e1e32b25a6c5a184a
    Signed-off-by: hchiramm <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8700
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit f1fecf5fb3ff34945bbacd0b4806bc57b9ddc355
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Sep 12 13:06:57 2014 +0530

    test: cleanup should clean all left over (stale) mounts
    
    This is a temporary work around to fix the spurious failures seen in ec
    testcases. As per the initial analysis it looks like quota
    (glusterd_quota_initiate_fs_crawl) is causing a mount point in /tmp to be stale.
    Once the root cause is identified this fix can be reverted as well.
    
    Change-Id: I8686f144ed298124074f749e75c13028ec00be01
    BUG: 1092850
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8703
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 51becaa5e803bd21807f30524da58a578061541b
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Aug 5 18:28:25 2014 +0200

    ec: Do not destroy inode context on inode invalidation
    
    Currently there is no need to handle inode invalidation requests,
    so this callback has been removed.
    
    Change-Id: I0ac2e47679bf62b1493e0403178305923bc036e8
    BUG: 1126932
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8420
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 26be0b3a9f334f33f1a6e53706045eb02983d713
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon Aug 4 20:50:31 2014 +0200

    ec: Removed SSE2 dependency
    
    This patch implements the Galois Field multiplications using pure C
    code without any assembler support. This makes the ec xlator portable
    to other architectures.
    
    In the future it will be possible to use an optimized implementation
    of the multiplications using architecture dependent facilities (it
    will be automatically detected and configured). To allow bricks with
    different machine word sizes to be able to work seamlessly in the
    same volume, the minimum fragment length to be stored in any brick
    has been fixed to 512 bytes. Otherwise, different implementations
    will corrupt the data (SSE2 used 128 bytes, while new implementation
    would have used 64).
    
    This patch also removes the '-msse2' option added on patch
    http://review.gluster.org/8395/
    
    Change-Id: Iaf6e4ef3dcfda6c68f48f16ca46fc4fb61a215f4
    BUG: 1125166
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8413
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>

commit 5157914bac0da41cba8fef10f9dfaef209e6e865
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Sep 10 23:39:19 2014 +0200

    tests/ec: Avoid spurious umount failures
    
    Change-Id: Id22d64a95adf3666a5e4208f87f9a6d91c40b267
    BUG: 1092850
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8694
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 976ecc99b4716f9189f0affdcba0ff8ea8d09d9e
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Sep 9 12:32:20 2014 +0530

    cluster/dht: Changed log level to DEBUG
    
    Change-Id: I7a4ee0c5a6a94bd4f31aff510a2971750913ed45
    BUG: 1138602
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8621
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: susant palai <spalai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1c8d4bf6ab299f8fb44dce354fb8f3232136be02
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Sep 9 06:05:24 2014 -0400

    CLI: Show warning on remove-brick commit
    Signed-off-by: Susant Palai <spalai@redhat.com>
    
    Change-Id: I48a4168f81bd272216549c76b0bc1b23e34894d6
    BUG: 1136702
    Reviewed-on: http://review.gluster.org/8664
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ed4a754f7b6b103b23b2c3e29b8b749cd9db89f3
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Sep 9 11:33:14 2014 +0530

    cluster/dht: fix memory corruption in locking api.
    
    <man 3 qsort>
    
         The  contents  of the array are sorted in ascending order
         according to a comparison function pointed to by compar, which is
         called with two arguments that "point to the objects being
         compared".
    
    </man 3 qsort>
    
    qsort passes "pointers to members of the array" to comparision
    function. Since the members of the array happen to be (dht_lock_t *),
    the arguments passed to dht_lock_request_cmp are of type (dht_lock_t
    **). Previously we assumed them to be of type (dht_lock_t *), which
    resulted in memory corruption.
    
    Change-Id: Iee0758704434beaff3c3a1ad48d549cbdc9e1c96
    BUG: 1139506
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8659
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b3314ea6e820fb659255d0e6e9a32ea259b7526d
Author: Shyam <srangana@redhat.com>
Date:   Tue Sep 9 13:31:51 2014 -0400

    cluster/dht: Fixed double UNWIND in lookup everywhere code
    
    In dht_lookup_everywhere_done:
    Line: 1194 we call DHT_STACK_UNWIND
    and in the same if condition we go ahead and call, goto
    unwind_hashed_and_cached; which at Line 1371 calls another UNWIND.
    
    As is obvious, higher frames could cleanup their locals and on
    receiving the next unwind could cause a coredump of the process.
    
    Fixed the same by calling the required return post the first unwind
    
    Change-Id: Ic5d57da98255b8616a65b4caaedabeba9144fd49
    BUG: 1139812
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/8666
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: susant palai <spalai@redhat.com>

commit c2513927b3aeaf03e0cfe1c1869c43f2a8f84153
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Sep 8 23:33:00 2014 +0530

    doc: Remove volume rename from gluster's man page.
    
    Change-Id: I5cde789088417f26d0c8319a1b24fdaa2c37dfe6
    BUG:  1031328
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/8656
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7d0a305e23a28631c7c3e8cfc648c9c9a24148f6
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Sep 8 21:52:30 2014 +0530

    quota/marker: Fix dict leaks
    
    Unref dicts in quota and marker functions before they return.
    
    Change-Id: I772edc7b46657a70fb136e037576c65e9beeaca8
    BUG: 1139327
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8655
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 822cf315a5d0f0d2bc90e9f2d8faa6e5e5701ed4
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jun 17 00:28:01 2014 +0530

    snapview-server: register a callback with glusterd to get notifications
    
    * As of now snapview-server is polling (sending rpc requests to glusterd) to
      get the latest list of snapshots at some regular time intervals
      (non configurable). Instead of that register a callback with glusterd so that
      glusterd sends notifications to snapd whenever a snapshot is created/deleted
      and snapview-server can configure itself.
    
    Change-Id: I17a274fd2ab487d030678f0077feb2b0f35e5896
    BUG: 1119628
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8150
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5c869aea79c0f304150eac014c7177e74ce0852e
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Mon Sep 8 16:44:23 2014 +0530

    gNFS: Fix memory leak in setacl code path
    
    If ACL is set on a file in Gluster NFS mount (setfacl command),
    and it succeed, then the NFS call state data is leaked. Though
    all the failure code path frees up the memory.
    
    Impact: There is a OOM kill i.e. vdsm invoked oom-killer during
    rebalance and Killed process 4305, UID 0, (glusterfs nfs process)
    
    FIX:
    Make sure to deallocate the memory for call state in acl3_setacl_cbk()
    using nfs3_call_state_wipe();
    
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    
    Change-Id: I9caa3f851e49daaba15be3eec626f1f2dd8e45b3
    BUG: 1139195
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/8651
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 72324ef5e6a1749fbdb1944b2f088f58090f81b3
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Sep 1 14:07:15 2014 +0200

    Always check for ENODATA with ENOATTR
    
    Linux defines ENODATA and ENOATTR with the same value, which means that
    code can miss on on the two without breaking.
    
    FreeBSD does not have ENODATA and GlusterFS defines it as ENOATTR just
    like Linux does.
    
    On NetBSD, ENODATA != ENOATTR, hence we need to check for both values
    to get portable behavior.
    
    BUG: 764655
    Change-Id: I003a3af055fdad285d235f2a0c192c9cce56fab8
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8447
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 165cf459cf2a61c391d16928d58b34543a7ec94e
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Sep 4 19:30:48 2014 +0530

    tests: Don't check for init process.
    
    As a way of checking for existence of pidof
    we were checking for init process, which may
    not be true in case of Containers.
    
    Change-Id: I402e7ab4f2459057826ed24094e87dd605eaac8a
    BUG: 1073168
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8600
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 15a2088da508539a292f2a1863377dc40d264c8c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Sep 3 20:49:53 2014 +0000

    cluster/afr: perform list-xattr during lookup
    
    Detect and heal mismatching user extended attributes during lookup.
    'Forward' port of http://review.gluster.org/#/c/7444/
    
    Change-Id: Id03c9746f083ffd3014711d0b3a2e5a71a45eed4
    BUG: 1134691
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8558
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d2600dfda2b8f87b5f08d96abfb2abc0677151e0
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Fri Sep 5 09:42:18 2014 +0530

    RPM spec file: Fixed the description for glusterfs
    
    Previously description was saying glusterfs is a
    clustered file-system which changed to ditsributed
    file-system.
    
    Change-Id: I3ee80024ba317e912890ceff2080b82ce111be95
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/8619
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fa696f2f0b1e50e34d009fb9378c41dc6edcc966
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Sep 5 15:11:06 2014 +0200

    Build fix: -lz for qemu-block xlator
    
    LIBZ_LIBS has been changed into ZLIB_LIBS everywhere in the
    sources, except in qemu-block xlator. Fix it so that it can
    find -lz and link correctly.
    
    BUG: 1129939
    Change-Id: I34ded175f056d1a0898804fe602e3d2d2cba27f5
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8623
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit fd500d4396f910e4cf759e0fffa4daf4ed24745a
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Aug 23 02:14:36 2014 -0700

    porting: Provide setfattr/getfattr implementation
    
    - Use 'getfattr' properly avoid redundant options during xattr query
    - Untabify certain parts of tests (remove tabs)
    - Avoid backtick evaluation for certain values to make code more portable.
    - Use awk on FreeBSD/Darwin, since 'wc' implementation is broken and adds
      spurious spaces in its output.
    
    Change-Id: I7dcc0b70874e43b4cda8c306ed18a31b7a3f990a
    BUG: 1131713
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8520
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>

commit 88159becd90d40323ecfc24cf40813538c9204cc
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat Aug 30 17:41:01 2014 +0530

    barrier: features.barrier should be a NO_DOC
    
    features.barrier is turned on/off internally by snapshot feature and hence it
    should not be exposed to the customer and this option should not be documented.
    
    Change-Id: Id9a421f94e291f1dc77044904bb18dd730c2d43e
    BUG: 1135691
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8572
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit dfe122966803bea65d7877d7e06e6f5d8af13890
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Sep 2 09:08:58 2014 +0200

    Regression test portability: EXPECT
    
    Make sure test_expect_not_footer() and test_expect_footer() work on
    non empty strings, otherwise it may produce errors such as in pgfid_feat.t
    on NetBSD:
    not ok 12 Got "" instead of ""
    
    This a a missing bit from previosuly merged patchset:
     I9cb76ba863897126534c3808fb0c9e564659835f
    
    BUG: 1129939
    Change-Id: I2635b67deec9cf60295faab52e7421947b1f7bda
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8576
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 271cdc1e06c790ecca2a883bc56ebf7992d496fd
Author: Vipul Nayyar <nayyar_vipul@yahoo.com>
Date:   Sun Jul 6 03:19:07 2014 +0530

    io-stats: Adding private data dumping method
    
    For the glusterfsiostat tool to be able to gather stats about mounted volumes
    from meta xlator, private information in the io-stats xlator needs to be dumped
    in the .meta folder.
    
    Added functionality for total data being read/written to be dumped along with
    latency related information for all fop functions present in io-stats.
    
    Change-Id: I75486f0ca361844a643861789f6c1406f439674c
    BUG: 1130023
    Signed-off-by: Vipul Nayyar <nayyar_vipul@yahoo.com>
    Reviewed-on: http://review.gluster.org/8244
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6064c220844e8c4963e22ec48c8f7da9da57fc2f
Author: Anuradha <atalur@redhat.com>
Date:   Wed Sep 3 19:04:02 2014 +0530

    cluster/afr : Mark pending changelog xattrs for new creations
    
    Based on type of file, set appropriate pending changelogs
    for new entries.
    
    Change-Id: Ifd124bf9bc54b996ce83ab9f39d03b3ccca7eb3c
    BUG: 1130892
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8555
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit bb2d5f49b5684e6484af16a580870cfe104aecd2
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Wed Sep 3 14:42:43 2014 +0530

    cluster/dht: Added code to capture races in dht-lookup path
    
    Change-Id: I9270d2d40ebd4b113ff961583dfda7754741f15b
    BUG: 1116150
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8430
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1f094f2519c163bd033ab535555448db34e9804d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 2 21:05:56 2014 +0530

    cluster/afr: Minor fixes to #8574
    
    * Fixed a bug in afr_selfheal_name_type_mismatch_check()
    * Fixed indentation
    * Removed redundant 'continue' statements
    
    Change-Id: Ie58b5dec9085ce9fe46ae9f244ebae1b1cef7ac5
    BUG: 1132469
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8586
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit e03559c20ab37f1a7db54a367258bb1cd005e50d
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Wed Sep 3 14:18:00 2014 +0530

    storage/posix : Missing space in log message
    
    Added a space in a log message
    
    Change-Id: Iabd50e6b5c9ff4673f59d6b52b785894b3dcdaf9
    BUG: 1116150
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8585
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2c4c1918e3a65f1b8a30b2e321c325c3c3aed950
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Sep 3 10:29:07 2014 +0530

    glusterd: Improve debugging experience for glusterd locks
    
    Today, when glusterd's internal locking mechanism fails
    with invalid type or when another competing lock is being
    held, the log message doesn't provide enough information
    directly as to which command saw this (first). Following
    is a snippet of how a failure would look in the log file.
    This would greatly assist in debugging.
    
    [2014-09-03 04:57:58.549418] E
    [glusterd-locks.c:520:glusterd_mgmt_v3_lock]
    (-->/usr/local/lib/glusterfs/3.7dev/xlator/mgmt/glusterd.so(__glusterd_handle_create_volume+0x801)
    [0x7f30b071e651]
    (-->/usr/local/lib/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_begin_synctask+0x2c)
    [0x7f30b072e19c]
    (-->/usr/local/lib/glusterfs/3.7dev/xlator/mgmt/glusterd.so(gd_sync_task_begin+0x55d)
    [0x7f30b072de6d]))) 0-management: Invalid entity. Cannot perform locking
    operation on vol types
    
    Change-Id: I0595f49d60e620e8b065f3506bdb147ccee383a7
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8580
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 312b339190b7b8f2e38cdd210bf2ee71e53b287e
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Sep 3 10:50:31 2014 +0530

    glusterd: Prevent rebalance starting with old clients
    
    Glusterd will prevent rebalance from starting when clients older than
    glusterfs-v3.6.0 are connected to a volume. This is needed as running
    rebalance with old clients connected could lead to data loss in some
    cases. The DHT xlator on newer clients (>= 3.6.0) has been fixed to
    prevent the data loss issues.
    
    Change-Id: If58640236382a2fc13f73f6b43777f01713859f7
    BUG: 1136201
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8583
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 60f33e6d12a854c425c2bbe237e0902a8e433631
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Tue Sep 2 17:43:43 2014 +0530

    glusterd: Set the rlimit for Open FDs to higher value
    
    Default 'open FD limit' is 1024. As the number of volumes/bricks
    increases, brick-to-glusterd socket FDs also increases in glusterd and
    runs out of the limit.
    
    Solution is to set the 'Open FD' limit to higher value in glusterd
    
    Change-Id: Iaa60b2155df2fa5a0759e054bdebffbc09f63ec1
    BUG: 1136352
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8578
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b81cec326d4d43519593cb56b7a0e68ea5c3421c
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Sep 2 05:29:52 2014 -0400

    CLI: Adding warning message in case remove-brick commit executed
    
    Change-Id: Ia2f1b2cd2687ca8e739e7a1e245e668a7424ffac
    BUG: 1136702
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/8577
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c087e5f634a0b2262118d61ab9c1d5c8e18c8819
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Wed Sep 3 10:42:47 2014 +0530

    Cluster/DHT: Changing rename log severity
    
    Changing log level for a rename message from debug
    to info to improve debuggability
    
    Change-Id: I53031fcf97fffd62095692477330ecde0cf47dcd
    BUG: 1130888
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8582
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a12cf2dedb98b115812163361846b02f8adc8353
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Aug 27 10:47:24 2014 +0530

    cluster/dht: remove specifying cached-subvol as part of name in
    unlink.
    
    commit 667b2496c3f29e24ed359a05b0f44df0d1894969 introduced a
    functionality where we can specify the subvol where file is stored. As
    part of same commit, dht_unlink was also changed to accept
    cached-subvol as part of name. While it makes sense to specify subvol
    while creating file, there is no necessity for specifying the subvol
    during unlink, since the default unlink logic works fine with this
    functionality too. Also, this code in unlink doesn't work well when
    files get migrated by rebalance process. Hence removing it.
    
    Change-Id: Ic3fc32ad657e2dcd677a4c80b04a618029eddd89
    BUG: 1130888
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8548
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4adfb6fb7c371c6bc03acdaf61f1cca496388356
Author: Shyam <srangana@redhat.com>
Date:   Tue Sep 2 12:37:07 2014 -0400

    cluster/dht: Modified test case to note rename failures as errors
    
    The bug referenced in this change, had an race condition that is now
    fixed by the following commits that are posted for review.
    
        http://review.gluster.org/#/c/8563/
        http://review.gluster.org/#/c/8570/
    
    These changes would now make the winning client not fail a rename,
    in case it failed to rename the linkto file. Hence when one client
    wins the link race, and the other still deletes the linkto file,
    the rename failure by the winning client is not a critical failure,
    hence it resolves the issue posted in the bug.
    
    As a result modifying the test case to treat the rename failures
    as errors, to catch any future issues.
    
    Change-Id: Ibe9caac7ee87dcbc4f581cfbd36173b734859ccb
    BUG: 1123950
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/8579
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4ce3db8e508e715a43352b082e861fd0e729951f
Author: Shyam <srangana@redhat.com>
Date:   Fri Aug 29 15:20:40 2014 -0400

    cluster/dht: Rename should not fail post hardlink creation
    
    In the rename path, we wind the creation of newname hardlink and
    linkto file in dst hashed a the same time. If the linkto creation
    fails, but the link creation succeeds, we enter the failure code
    and cleanup the created newname hardlink.
    
    In the interim if another client looks up newname and finds it as
    a hardlink from FUSE, it could send an unlink for oldname instead
    of a rename. This combined with the above cleanup code could end
    up losing all the files copies, and thereby losing data.
    
    This fix separates these steps into 2 parts, creating the linkto
    first and then the link file, so that post link file creation no
    failures would cleanup the newname file. If linkto fails then link
    is not attempted, thereby not polluting the name space with
    newname.
    
    Change-Id: I61da8e906060da16a31ea1076eec2f01fd617f44
    BUG: 1130888
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/8570
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 890ab583a519b3b189a61c5fd563b4326836b988
Author: Shyam <srangana@redhat.com>
Date:   Wed Aug 27 15:27:46 2014 -0400

    cluster/dht: Treat linkto file rename failure as non-critial error
    
    It is a critical failure iff we fail to rename the cached file
    if the rename of the linkto failed, it is not a critical failure,
    and we do not want to lose the created hard link for the new
    name as that could have been read by other clients.
    
    NOTE: If another client is attempting the same oldname -> newname
    rename, and finds both file names as existing, and are hard links
    to each other, then FUSE would send in an unlink for oldname. In
    this time duration if we treat the linkto as a critical error and
    unlink the newname we created, we would have effectively lost the
    file to rename operations.
    
    Repercussions of treating this as a non-critical error is that
    we could leave behind a stale linkto file and/or not create the new
    linkto file, the second case would be rectified by a subsequent
    lookup, the first case by a rebalance, like for all stale linkto
    files
    
    Change-Id: Ia53ad8b43c3cf8f48ef5b43fd1fec4274e807556
    BUG: 1130888
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/8563
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6bf5a2543a9990b718839496ac123ad2141145e7
Author: hchiramm <hchiramm@redhat.com>
Date:   Wed Aug 27 12:24:24 2014 +0530

    core: update INSTALL file.
    
    Change-Id: Ie6f041810da647e39d4bbb5384f51dadd6f69b30
    Signed-off-by: hchiramm <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8573
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2b7a2d2c21e2329828c27e6f9556ea8d9d512021
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Aug 30 16:33:59 2014 +0530

    USS: initialize a list before using it.
    
    Change-Id: Iba35e4397646a67384e878fbe7bdfb7586fc07f9
    BUG: 1130888
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8569
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6c4325ca57bca72d10e5172f8423262cdb3a379c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Aug 21 17:27:17 2014 +0530

    cluster/afr: Propagate EIO on inode's type mismatch
    
    Original author of the test script:
                Pranith Kumar K <pkarampu@redhat.com>
    
    Change-Id: If515ecefd3c17f85f175b6a8cb4b78ce8c916de2
    BUG: 1132469
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8574
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2c0a694b8d910c530899077c1d242ad1ea250965
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 2 09:40:44 2014 +0530

    storage/posix: Prefer gfid links for inode-handle
    
    Problem:
    File path could change by other entry operations in-flight so if renames are in
    progress at the time of other operations like open, it may lead to failures.
    We observed that this issue can also happen while renames and readdirps/lookups
    are in progress because dentry-table is going stale sometimes.
    
    Fix:
    Prefer gfid-handles over paths for files. For directory handles prefering
    gfid-handles hits performance issues because it needs to resolve paths
    traversing up the symlinks.
    Tests which test if files are opened should check on gfid path after this change.
    So changed couple of tests to reflect the same.
    
    Note:
    This patch doesn't fix the issue for directories. I think a complete fix is to
    come up with an entry operation serialization xlator. Until then lets live with
    this.
    
    Change-Id: I10bda1083036d013f3a12588db7a71039d9da6c3
    BUG: 1136159
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8575
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4ae887db6b770584219fab484dec027d278baef9
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 8 06:12:04 2014 +0200

    Regression test portability: mknod
    
    Linux mknod(2) is able to create fifo and named sockets. NetBSD and
    FreeBSD use mkfifo(2) and socket(2)/bind(2) for that.
    
    BUG: 764655
    Change-Id: I1d3969e3fcb6afdbd184c28bd268ffa2da7ae202
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8433
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 11a4d37571253ce2cb18f36bb0ee18d1946be315
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Aug 30 06:59:29 2014 +0200

    Regression test portability: EXPECT
    
    Make sure test_expect_not_footer() and test_expect_footer() work on
    non empty strings, otherwise it may produce errors such as in pgfid_feat.t
    on NetBSD:
    not ok 12 Got "" instead of ""
    
    BUG: 1129939
    Change-Id: I9cb76ba863897126534c3808fb0c9e564659835f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8568
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8b8f6da58926a9ae7e450021e17b0b68d9fea830
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Aug 31 05:45:16 2014 +0200

    Regression test portability: LVM
    
    Skip any test involving LVM on NetBSD as LVM is not supported
    
    BUG: 1129939
    Change-Id: I2237bae1128d1a81047c9ff7f905431156daf8b7
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9816fe18e839eb195a6f4482311b65df995b920f
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Tue Aug 26 16:40:49 2014 +0530

    Hook scripts should exit with correct exit status.
    
    When volume set options other than nfs-ganesha.host and nfs-ganesha.enable
    are executed, the hook script S31ganesha-set.sh should exit with
    exit status 0. The present behaviour results in an error message in
    one of the logs that could be  misleading.
    
    Similarly, hook script S30samba-set.sh should exit with
    exit status 0 if samba is not installed. Fixing the issue
    with a minor change in the script.
    
    Change-Id: I35d1dc8400bb7043385800ed97adc5321829437f
    BUG: 1122978
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/8385
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f52efa681b1a16c287ed00e2a79cc7f05e65fed1
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Aug 28 09:58:43 2014 +0530

    statedump: Print curr_stdalloc in mempool statedump ...
    
     ...for, it is curr_stdalloc that is incremented for every mem_get()
    and decremented on every call to mem_put() and can be used to detect
    leaks, when cold_count is 0.
    
    Change-Id: I418a132c3ea4c0b99ea5c6840ff3024d8d19ddf4
    BUG: 1134221
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8557
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 370592cd702a2c135ba4accfcbe9e1a63c3b6166
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Aug 28 10:46:50 2014 +0200

    build: fixes for compiling with -Werror=format-security
    
    Nightly builds on Fedora Rawhide (x86_64 and i686) started to fail with the
    following error:
    
      cli-rpc-ops.c: In function 'gf_cli_get_vol_opt_cbk':
      cli-rpc-ops.c:9339:25: error: format not a string literal and no format arguments [-Werror=format-security]
                               cli_err (msg);
                               ^
    
    The cli_err() should be called with a format-string like "%s" to prevent
    unexpected errors.
    
    Change-Id: I6a287795fb8b7a305c8f14323456eeabf68d100c
    BUG: 1134773
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8560
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ea96a0abcd23bd729d8167ec2b88af12d4dbb62c
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Aug 29 00:11:38 2014 -0700

    porting: Remove unnecessary code from mount_darwin.c
    
    - Cleanup mount_darwin.c to make it cleaner
    - Restructure the code to be more readable
    - Avoid unnecessary delays invoking `mount_osxfusefs`
    
    Change-Id: I7f28875b0ec872a08bf8e77dfc8ebe5eca750d0e
    BUG: 1135348
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8564
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2dd53eb4de91c25817af85475cfa9ff66e79c97b
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Aug 19 18:24:23 2014 -0700

    porting: various fixes regression tests OSX/FreeBSD
    
    - `wc -l` on OSX/FreeBSD adds spurious spaces, this clobbers
      up TAP output parsers - fix it.
    - `umount -l` doesn't exist on OSX/FreeBSD use 'umount -f' if
       available.
    - Add check for 'file' version, to handle mime type variations
      across versions
    - Converge 'glusterfs --attribute-timeout=0 --entry-timeout=0'
      into '$GFS'
    - Modify remaining 'mount -t nfs' to use 'mount_nfs'
    - Update sha1sum for OSX to use 'openssl sha1'.
    
    Change-Id: Id1012faa5d67a921513d220e7fa9cebafe830d34
    BUG: 1131713
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8501
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 04be6a47df5c7d5c04c84fed06df9a8a1652c582
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Aug 26 14:57:42 2014 -0700

    dht: Avoid using inline, if necessary use it with 'static inline'
    
    This avoids flat namespace problems on OSX and with clang
    
    Change-Id: Id80d94d71b120c6b1166218caa8cf9cf7f2da03a
    BUG: 1130888
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8547
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 98583a509f1c4ab3cdc20df668e11774fa65085b
Author: Prashanth Pai <ppai@redhat.com>
Date:   Wed Aug 27 15:02:49 2014 +0530

    doc: Converting GFID to Path.
    
    This is an attempt to document various possible ways to externally
    get file/dir path from its GFID.
    
    Change-Id: Ic31725a9706ddae8972aea9bb58f3b70978dbd06
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/8552
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 21c8946b0bc05d0bc8f84906e16b8c2cbca4c9f9
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Aug 21 21:35:52 2014 +0530

    cluster/dht: synchronize rename and file-migration
    
    Change-Id: I4f243c946f76d440680b651235f925e3d0ebf0fd
    BUG: 1130888
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8523
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b23be2e7581c6aa295053dc8866cab841ae374b6
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Aug 22 17:07:15 2014 +0530

    storage/posix: Don't unlink .glusterfs-hardlink before linkto check
    
    BUG: 1116150
    Change-Id: I90a10ac54123fbd8c7383ddcbd04e8879ae51232
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8559
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1b02e53a5fdf706290ce143fbbf8a09845105d0
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Aug 27 11:27:33 2014 +0530

    cluster/dht: invoke callback when there are no locks to be unlocked.
    
    Change-Id: I375cb68f1075c2d58cf9d09ed6bd5e2746e1637d
    BUG: 1130888
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8549
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dc844c545caa7f2cf08fd71caa5051348a5f3c78
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Aug 27 15:14:04 2014 +0530

    cluster/afr: Fix dict_t leaks
    
    dict_t objects that are ref'd in alloca'd "replies" in
    afr_replies_copy() are not unref'd after "replies" go out of scope.
    
    Change-Id: Id5a6ca3c17a8de72b94b3e0f92165609da5a36ea
    BUG: 1134221
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8553
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 92d1ae829ce5dfca7af2fdb33f10305732028602
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Aug 25 05:42:38 2014 +0530

    cli/snapshot : Add confirmation dialog to snapshot restore operation
    
    When restoring a volume, the user is not prompted for confirmation.
    Since restoring a volume rolls back the data to a previous point in time,
    there is the potential for updates to be lost.
    Hence it is better to display a confirmation dialogue during snapshot
    restore operation.
    
    Change-Id: I7b23eaeb43ad2aafa508e2ca5750d9b0fc7d6e36
    BUG: 1133426
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8525
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit f56558224423e3af92aa08aa702dbc8cbdc0c55b
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Jul 15 17:00:09 2014 +0530

    Add build generated *.py[oc] to .gitignore
    
    Related to:
    http://review.gluster.org/8237
    
    Change-Id: I8f888f0363c4358026ad17b2dc288014f7c51466
    BUG: 1119328
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/8311
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 840a50d1db2001fde687f4f79b2b923c8b762e59
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Aug 27 10:35:15 2014 +0200

    rpm: fix date in %changelog
    
    When building rpms, the following warning is printed:
    
      warning: bogus date in %changelog: Thu Jun 29 2014 Humble Chirammal <hchiramm@redhat.com>
    
    This orginates from the following change:
    > Change-Id: I4988a025bd18716fd6d355431196540e140224b3
    > Reviewed-on: http://review.gluster.org/8116
    
    The date of the change was the 19th, not the 29th. Correcting the date and the
    order of the changelog entries prevents this warning.
    
    Change-Id: Ied2d25ae3c81c58ec8ab35ff54be169ba6428ed6
    BUG: 1108669
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8551
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa0891b796809e3a932c709e1406298b4d5f0416
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Wed Jul 9 00:31:57 2014 +0530

    gNFS: correct some typos in comments.
    
    Change-Id: I304c760c2318edd4bab985ca19bf9ce62fd21a3c
    BUG: 1075417
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8265
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 861f65463708aedb20f1634c8b3214facc68348c
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Aug 26 14:40:01 2014 -0700

    glusterd: Add xml specific functions in HAVE_LIB_XML block
    
    Build failure on OSX and also on Linux with '--disable-xml-output'
    introduced in following commit "c080403393987f807b9ca81be140618fa5e994f1"
    
    Change-Id: I0db92c9f5e319dc1932bed9ecc1acc98adb57de3
    BUG: 983317
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8546
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 74cf4e1920db1edae6728cfe632e4ca7aea5be59
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Aug 19 16:14:03 2014 -0700

    porting: `pidof` portability for OSX/FreeBSD
    
    - Provide a portable `pidof` just to be used specifically with
      glusterfs regression tests on OSX and FreeBSD. This was
      written after countless hrs of effort to get a sane `pidof`
      working on either of the environments.
      `pidof` comes at the wake of lack of proper procfs support
      and also incompatible way of handling process names since
      glusterd/glusterfs are symbolic links to 'glusterfsd'
    - tests/utils/* directory should be part of 'PATH' to avoid
      abspath calculation using $(dirname)
    - cleanup() - rpcinfo command prints error on FreeBSD/OSX fix it
    
    Change-Id: I35f86273624cb279da1c8fae056ca27669e251d8
    BUG: 1131713
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8499
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 77ce88681c15e711e87d23b891a488b2fd825eb0
Author: hchiramm <hchiramm@redhat.com>
Date:   Tue Aug 26 15:29:29 2014 +0530

    doc: move split_brain.md to debugging dir.
    
    Change-Id: I4558514bca9365b4563e74f166f2a0156f798d0f
    Signed-off-by: hchiramm <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8544
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 172100209e531e94168d0974bfb0995704d9dddd
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Aug 14 16:44:23 2014 +0530

    libglusterfs/syncop: implement inodelk
    
    Change-Id: Iea489157490b70cb2bb03576b0d4943c6d8f052d
    BUG: 1130888
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8522
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1fe3d72e373bf0deaed152842d12d94bb9129dc
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Aug 11 10:14:18 2014 +0530

    cluster/dht: introduce locking api.
    
    Change-Id: I41389ba91951d3e63e617aa32cd0bee848261c72
    BUG: 1130888
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8521
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 27daeba0f7e02669919a7d89a04ea8fe39e06898
Author: Ajeet Jha <ajha@redhat.com>
Date:   Tue Aug 26 14:39:24 2014 +0530

    features/changelog: Removal of redundant fop color count while draining.
    
    Change-Id: Ie5581579df63513e636fa3dd92dd90699ea7d999
    BUG: 1128093
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/8542
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c080403393987f807b9ca81be140618fa5e994f1
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Jun 30 10:33:25 2014 +0530

    cli/glusterd: Support of volume get for a specific volume option
    
    This patch introduces a cli command to display a specific volume option/all
    volume options of a specific volume with the following usage:
    
    Usage: volume get <VOLNAME> <key|all>
    
    Change-Id: Ic88edb33c5509d7a37cd5ade6341e45e3cdbf59d
    BUG: 983317
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8305
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit acabde2c297c4175946565017ba17a251ad3fb1c
Author: Ajeet Jha <ajha@redhat.com>
Date:   Sat Aug 23 19:06:45 2014 +0530

    features/changelog: Crash consistency of changelog wrt snapshot
    
    This patch introduces call-path fop details logging for data operations
    in CHANGELOG.SNAP. This feature is enabled with barrier-enable
    notification and disabled with barrier-disable notification.
    
    Change-Id: Ib548d34203eb99cea478a6baff402e82251c73a4
    BUG: 1128093
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/8533
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b56751b3b9a9ed3cceb2f0d221fa40ef94a8d516
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Aug 26 14:44:28 2014 +0530

    doc: Remove outdated admin_UFO.md
    
    Remove outdated admin_UFO.md file and add file to point to upstream
    SwiftOnFile repo and documentation.
    
    Change-Id: I87e17c11197e0ed3dd9f10a3ace88c2b3c23566e
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/8543
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b6b279107c70044ea97949c573442340f31d0220
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Aug 23 23:46:51 2014 -0700

    tests: bug-1002207.t - should mount glusterfs before tests
    
    Change-Id: I9238ea8cf4e5ad9bab384ef08d873a5b0e578a33
    BUG: 1133266
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8519
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit dc450ab5e3798b47e89e90b64c49cb8e1f20efce
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Aug 8 11:52:17 2014 +0530

    cluster/afr: Fix all locked_on bricks are sinks check in self-heals
    
    Problem:
    Counts may give wrong results when the number of bricks is > 2. If the
    locks are acquired on one source and sink, but the source accuses even the
    down sink then there will be 2 sinks and lock is acquired on 2 bricks so
    even when there is a clear source and sink **_finalize_source functions think
    the file/directory is in split-brain.
    
    Fix:
    Check that all the bricks which are locked are sinks.
    
    Change-Id: Ia43790e8e1bfb5e72a3d0b56bcad94abd0dc58ab
    BUG: 1128721
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8456
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 71095db8f40888f6afc604c896c296dbe988d292
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Aug 25 09:46:14 2014 +0530

    cli/snapshot : update of a snapshot delete syntax in documentation
    
    Change-Id: Id1a4b9684a8dd5750ee6eed841e3d5195407fb7e
    BUG: 1112613
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8534
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 4bbaf4615be673dec70fc3e1f127139b6d079869
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Aug 16 02:32:49 2014 +0200

    Fix glustershd detection on volume restart
    
    On NetBSD and FreeBSD, doing a 'gluster volume start $volume force' causes
    NFS server, quotad, snapd and glustershd to be undetected by glusterd once the
    volume has restarted. 'gluster volume status' shows the three processes
    as 'N' in the online column, while they have been launched successfully.
    
    This happens because glusterd attempts to connect to its child processes
    just between the child does a unlink() on the socket in
    __socket_server_bind() and the time it calls bind() and listen().
    Different scheduling policy may explain why the problem does not happen
    on Linux, but it may pop up some day since we make no guaranteed
    assumptions here.
    
    This patchet works this around by introducing a boolean
    transport.socket.ignore-enoent option, set by nfs and glustershd,
    which prevents ENOENT to be fatal and cause glusterd to retry and
    suceed later. Behavior of other clients is unaffected.
    
    BUG: 1129939
    Change-Id: Ifdc4d45b2513743ed42ee235a5c61a086321644c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8403
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c2a0e3f722583731599785d16f12be5b3472934b
Author: ggarg <ggarg@redhat.com>
Date:   Mon Apr 14 16:38:15 2014 +0530

    cli: Fixing ambiguous message error for rebalance <volname> start command
    
    Previously output message of command 'gluster volume rebalance <volname>
    start/start force/fix-layout start' was ambiguous and poorly formatted.
    Previously output message was: "volume rebalance: <volname>: success:
    Starting rebalance on volume <volname> has been successful."
    
    Now with this fix properly formatted output message is:
    "volume rebalance: <volname>: success: Rebalance on <volname> has been
    started Successfully. Use rebalance status command to check status of
    the rebalance process."
    
    Change-Id: I23268fc13b05d1b39ffe4c702d0e4f73085acd1c
    BUG: 1087487
    Signed-off-by: ggarg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/7473
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ec257d019cacbe4998cc78b591fd5a212c8cff35
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Thu Aug 21 17:07:25 2014 +0530

    glusterd: Parsing key/value pair with value containing '='
    
    Parsing key/value pair in the brickinfo file, where value contains '='
    would truncate everything after '=' in value.
    
    For example:
    A key/value pair
    mnt-opts=rw,noatime,allocsize=1MiB,noattr2
    
    is parsed as:
    mnt-opts=rw,noatime,allocsize
    
    BUG: 1132451
    Change-Id: I756b2fc4b06875267212b1a5c3e91c5a40c6accb
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8524
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b87f92c0eee630690e2b515a7f79c28af6496a5e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Aug 1 18:30:32 2014 +0530

    mount/fuse: Handle fd resolution failures
    
    Problem:
    Even when the fd resolution failed, the fop is continuing on the
    new graph which may not have valid inode. This lead to NULL layout
    subvols in dht which lead to crash in fsync after graph migration.
    
    Fix:
    - Remove resolution error handling in FUSE_FOP as it was only added
      to handle fd migration failures.
    - check in fuse_resolve_done for fd resolution failures and fail the
      fop right away.
    - loc resolution failures are already handled in the corresponding
      fops.
    - Return errno from state->resolve.op_errno in resume functions.
    - Send error to fuse on frame allocation failures.
    - Removed unused variable state->resolved
    - Removed unused macro FUSE_FOP_COOKIE
    
    Change-Id: I479d6e1ff2ca626ad8c8fcb6f293022149474992
    BUG: 1126048
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8402
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 11beb72ef0ec80d13dcfe7061b46cad105f6e77e
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Aug 22 17:15:13 2014 +0530

    features/changelog: barrier all entry creation fops
    
    when a snapshot is taken, there are chances of entry creation fops
    not being recorded either in changelog or through the recursive
    ancestry xtime updation by marker. This causes consumers of changelog
    (primarily geo-replication as of today) to not be aware of these entries
    after a snapshot is restored. This can lead to inconsistencies. This patch
    is an interim workaround to barrier creates till changelog becomes completely
    crash consistent.
    
    BUG: 1128093
    Change-Id: Ie0dbfd74beecb88df5c2ddf9fc680af91547c3f3
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/8517
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: ajeet jha <ajha@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 85afebed24ec7b34dc44890e58ee91b5c9c14279
Author: jonKSA <cope.jonathan@gmail.com>
Date:   Wed Aug 20 12:34:37 2014 -0500

    doc: Update admin_guide for hadoop.
    
    Current version of admin_Hadoop.md contains an
    obsolete set of instructions.Changes are purely
    textual; no code changes.Linking to a community
    site extends the viability of the doc and allows
    instructions to keep pace with future versions.
    Instructions have been validated.
    
    Change-Id: Ie330b2a23513ae140d3cd5f19af3045fff3bc9d5
    BUG: 1132105
    Signed-off-by: jonKSA <cope.jonathan@gmail.com>
    Reviewed-on: http://review.gluster.org/8505
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3f019874a4726d4b2df7c8e81581b9bed5caeb93
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Fri Aug 22 15:16:40 2014 +0530

    Cluster/DHT : Additional log messages
    
    Adding log messages in the rename and lookup calls to
    help with debugging.
    
    Change-Id: I13b1c6f98fb49ead45362550c46359ab1f9028c0
    BUG: 1130888
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8516
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 75dfbf709126945f45507d7fa9d9b2b7eee68fc2
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 21 15:15:46 2014 +0530

    tests: metadata self-heal tests
    
    Change-Id: Idef49b22018908c0a2ed95852b0670a91a750eba
    BUG: 1132913
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8515
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bc38d564663a64072ca508da12a8b4b6d48995e9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 21 17:30:10 2014 +0530

    cluster/afr: Perform metadata sync inside metadata locks
    
    Change-Id: Ie55b3d37cacbdad74a3f63c3b0f025b0ffd0104a
    BUG: 1132461
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8514
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 3b70b160a46b22b77a8ad1897440ec1346795a0f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Aug 13 11:11:17 2014 +0530

    cluster/afr: Perform gfid heal inside locks.
    
    Problem:
    Allowing lookup with 'gfid-req' will lead to assigning gfid at posix layer.
    When two mounts perform lookup in parallel that can lead to both bricks getting
    different gfids leading to gfid-mismatch/EIO for the lookup.
    
    Fix:
    Perform gfid heal inside lock.
    
    BUG: 1129529
    Change-Id: I20c6c5e25ee27eeb906bff2f4c8ad0da18d00090
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8512
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 60f12dfbc87818831a65ac80ad8ba2fe166a29e2
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Aug 21 22:22:37 2014 -0700

    client: client3_3_readdir() - initialize ``local`` properly
    
    A crash is observed in the following scenario on OSX
    
    ~~~
    (gdb) p readdir_rsp_size
    $1 = 1552
    GLUSTERFS_RPC_REPLY_SIZE == 24
    GLUSTERFS_RDMA_MAX_HEADER_SIZE == 228
    
    ((1552 + 24 + 228)) == 1804
    
    GLUSTERFS_RDMA_INLINE_THRESHOLD == 2048
    
    if ((readdir_rsp_size +
     GLUSTERFS_RPC_REPLY_SIZE +
     GLUSTERFS_RDMA_MAX_HEADER_SIZE) > GLUSTERFS_RDMA_INLINE_THRESHOLD)
      ----> False
    ~~~
    
    ``local`` is never initialized leads to NULL reference later.
    
    This patch makes sure that local is initialized, correctly as its
    done in client3_3_readdirp() call.
    
    Change-Id: I46931fc96900b7740ae71536c954bb9deda5c879
    BUG: 1132796
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8511
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit aa9b19e4b3329f446f0eb9b3a4ed0dbb9ebe4d09
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Aug 12 04:14:21 2014 +0530

    glusterd/snapshot : Fail the snapshot create operation if geo-rep is running.
    
    As one of the recommandations for taking a snapshot is not to have
    an active geo-replication session, its better to display an error
    saying session is active when snapshot create command is issued.
    
    Change-Id: I94593dbd2659610e033ca316176dda1ac8dc5ce6
    BUG: 1129038
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8461
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 865d156d30498cd1bf4219ddbbb304d2ffd4aea0
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Aug 20 10:50:35 2014 +0200

    Fix quotad RPC options use-after-free bug in gluster
    
    In cli/src/cli.c:cli_quotad_clnt_rpc_init(), dict_unref (rpc_opts)
    causes the options to be freed while code in rpc/rpc-transport/socket
    still relies on it. The options are corrupted when memory is reallocated,
    which sometimes leads to a crashes on NetBSD when socket_connect()
    attempted to read options.
    
    Fix the problem by not doing the dict_unref(). Make sure the rpc_opts
    are freed on error, though.
    
    BUG: 1129939
    Change-Id: If1d6ea50cc3e1599e9e369863c8db0c0694d3671
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8502
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f83067f2a9fc5d85bbd985e14fcda07346371ec8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 21 10:44:14 2014 +0530

    cluster/afr: Set pending changelog based on filetype for new entries
    
    Change-Id: Ib6eea2dfe43aacf1f3446cc023adecbcf8645d48
    BUG: 1132102
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8506
    Reviewed-by: Anuradha Talur <atalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bbb7da5abe6b7275d9b633f8ad7692a4f2132c71
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri Aug 8 17:17:20 2014 +0530

    geo-rep/glusterd: API to check active geo-rep session for the volume
    
    Requirement:
    Snapshot needs an API to fail the CLI if any geo-rep session is active
    for that volume.
    
    Solution:
    A function "gd_vol_is_geo_rep_active" is provided to check if any
    geo-rep session is active for that volume. An in memory dict called
    'gsync_running_slaves' is maintained in 'volinfo' structure to keep
    track of active geo-rep session for the volume. The key
    'slavenode::slavevol' with value 'running' is added whenever geo-rep
    is started/resumed into the dict and the same is removed if
    stopped/paused. So the 'count' in dict is used to decide whether the
    geo-rep is active or not for that volume.
    
    Also added "this->name" in gf_log in routines which this patch is
    touched.
    
    Change-Id: I2b5de7dd686541c6b89c0fd0f7a4dbc92eecfac5
    BUG: 1129008
    Signed-off-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8459
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 33be39b42f3b9b0505f83a509ff87d416e106158
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 8 05:39:38 2014 +0200

    Regression test portability: mktemp
    
    Linux mktemp accepts to run without a template, NetBSD mandates it. Since
    the template option has the same syntax, add it everywhere. While there,
    also do this in scripts outside of regression testing.
    
    BUG: 764655
    Change-Id: I3ec140afbc9009257c81a56d77afcc21fef74cc4
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8432
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit a521fc1d22db5477552c0fabc1f918b43caa50c3
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Aug 10 19:56:06 2014 +0200

    Regression test portability: sha1sum
    
    Provide a shell function for sha1sum if missing
    
    BUG: 764655
    Change-Id: I8b232af8aab7f95ba7c7ad83e37a111d562201a5
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8450
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 011b3fc4afd2cb12b8b3248df05c3870ae4cfe78
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Aug 13 06:04:25 2014 +0200

    Regression test portability: dd
    
    Use dd msgfmt=quiet also in truncate replacement
    
    BUG: 764655
    Change-Id: I5ad022c1dc65ecc98996ccbe8a3d0e9de162aa1a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 28a2c9ee3994e19a708b0c42bc2445073f42a87d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Aug 14 11:45:02 2014 +0200

    Regression test portability: 127.0.0.0/8
    
    On Linux, the host answers any address in  127.0.0.0/8
    On NetBSD, any address must be configured with ifconfig lo0 alias before
    it can be used.
    
    BUG: 1129939
    Change-Id: Ia628716c104d955817a95e0c5e04ead924bb4847
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8483
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 473f115cbf18dd5229636c817d49b2c60471e227
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Aug 19 17:55:46 2014 +0200

    Regression test portability: mount
    
    Address various portability-related problems related to mount
    - In order to address the non-portability of NFS mount options,
      use the mount_nfs shell function everywhere, and use it to
      translate options.
    - Make sure NFS mounts are unmounted before shutting down the
      daemons in order to avoid deadlock. The change is done in every
      test that did not unmounted NFS mounts at the end of the script,
      and in global cleanup function as well. The force_umount shell
      function from volume.rc was duplicated as umount_nfs in nfs.rc
      so that we do not have to add an include on volume.rc for all
      NFS tests that do not need it.
    - The FUSE mount type on NetBSD is puffs|perfuse|fuse.glusterfs
      instead of just fuse.glusterfs, make the regexp configurable
      in include.rc
    - Finding wether the mount is RO or RW in mount output needs
      a system-dependent command configurable in include.rc
    - mount options in /proc/mounts may be limited to "rw", adjust
      the regexp for this case where there is no comma
    
    And while there change rm into rm -f in tests/basic/mount.t
    for removal opearation that should fail, since rm may ask
    for confirmation
    
    Change-Id: I1fb708486ec350b2885e2404879561c1020fa8fd
    BUG: 1129939
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8494
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 22d5361cec8ec2a101e0896a9642a995122ffad3
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jul 17 12:06:58 2014 +0530

    client: Add ping-timeout to statedump
    
    The ping timeout value of a client xlator can be seen by,
    
    ># cat $META/graphs/active/vol-client-0/private |grep ping_timeout
    ping_timeout = 42
    
    where $META is /<fuse-mountpt>/.meta
    
    Change-Id: I4f68f184fc3f30871269a23fc4a82a1378396058
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8321
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c42339ef09325735138cd59d64636aa61130ad6c
Author: Patrick Uiterwijk <puiterwijk@redhat.com>
Date:   Mon Aug 18 16:35:10 2014 -0400

    who-wrote-glusterfs: use the set $GITDM_REPO variable
    
    Change-Id: Ic119f83fff3930e164f3c81df1c9b60d5eb2d99f
    BUG: 1131272
    Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
    Reviewed-on: http://review.gluster.org/8495
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d0a3b4307e40b70d73faf4baed9fa0c930682894
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Aug 8 15:06:11 2014 +0530

    geo-rep: Fixing issue with xsync upper limit
    
    While identifying the file/dir to sync, xtime of the file was compared
    with xsync_upper_limit as `xtime < xsync_upper_limit` After the sync,
    xtime of parent directory is updated as stime. With the upper limit
    condition, stime is updated as MIN(xtime_parent, xsync_upper_limit)
    
    With this files will get missed if `xtime_of_file == xsync_upper_limit`
    
    With this patch xtime_of_file is compared as
    xtime_of_file <= xsync_upper_limit
    
    BUG: 1128093
    Change-Id: I5022ce67ba503ed4621531a649a16fc06b2229d9
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8439
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9b5231e5c98b8cfa116838287c7a14042702795f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Aug 18 12:11:35 2014 +0200

    NFS: stripe-xlator should pass EOF at end of READDIR
    
    NFS READDIR replies are made of a header, a sequence of
    entries, and a EOF flag. When GlusterFS's NFS server is
    used along with stripe xlator, it fails to set the EOF
    flag, which violates NFS RFC and confuses some clients.
    
    The bug is caused because nfs xlator sets EOF if it gets
    op_errno set to ENOENT. That value is produced in storage
    xlator and propagated through server, client, and other
    xlators until stripe xlator handles it. stripe only passed
    op_errno if op_ret < 0, which is not the case here. This
    change set adds a special case for that situation to fix
    the problem.
    
    Change-Id: Ie6db94b0515292387cfb04c1e4a9363f34fcd19a
    BUG: 1130969
    Reported-by: Emmanuel Dreyfus <manu@netbsd.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8493
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>

commit 6630fff4812f4e8617336b98d8e3ac35976e5990
Author: Shyam <srangana@redhat.com>
Date:   Tue Aug 12 10:48:27 2014 -0400

    cluster/dht: Fix dht_access treating directory like files
    
    When the cluster topology changes due to add-brick, all sub
    volumes of DHT will not contain the directories till a rebalance
    is completed. Till the rebalance is run, if a caller bypasses
    lookup and calls access due to saved/cached inode information
    (like NFS server does) then, dht_access misreads the error
    (ESTALE/ENOENT) from the new subvolumes and incorrectly tries
    to handle the inode as a file. This results in the directories
    in memory state in DHT to be corrupted and not heal even post
    a rebalance.
    
    This commit fixes the problem in dht_access thereby preventing
    DHT from misrepresenting a directory as a file in the case
    presented above.
    
    Change-Id: Idcdaa3837db71c8fe0a40ec0084a6c3dbe27e772
    BUG: 1125824
    Signed-off-by: Shyam <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/8462
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ba0f31b2a5c8bd35f99b1ba2a74c81a2c2ded200
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Aug 7 17:01:18 2014 +0200

    Regression test portability: stat
    
    Linux uses stat -c, stat --printf= or stat --printf
    NetBSD uses stat -f with different format strings. This change set
    changes all stat usage to stat -c and introduce a shell stat()
    fonction to perform the format string translation.
    
    BUG: 764655
    Change-Id: I024fca7c1b736b053f5888cbf21da0a72489ef63
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8424
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit c80b5b915a6bf2c6506d789f8ab6f0dcbf3dc617
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Aug 13 02:00:05 2014 +0200

    Regression test portability: mkdir
    
    mkdir -v (verbose) is not portable, just remove it.
    
    BUG: 764655
    Change-Id: If344792caf977698abe0bf497d9083bc9333df55
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8463
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 41a22836fd581216d0a071cef5676651d676fd29
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Aug 10 00:02:21 2014 +0200

    Enable aux-gfid-mount option on non Linux systems
    
    The aux-gfid-mount works on non Linux systems, and it is required
    to pass tests/basic/gfid-access.t
    
    BUG: 764655
    Change-Id: Ic6c8ef425e091440a139bbd25fadbf4f82e378cb
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8446
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 2510af16744f7825c91bed4507968181050bbf88
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Aug 12 18:19:30 2014 +0530

    geo-rep: Handle RMDIR recursively
    
    If RMDIR is recorded in brick changelog which is due to
    self heal traffic then it will not have UNLINK entries for
    child files. Geo-rep hangs with ENOTEMPTY error on slave.
    
    Now geo-rep recursively deletes the dir if it gets ENOTEMPTY.
    
    BUG: 1129702
    Change-Id: Iacfe6a05d4b3a72b68c3be7fd19f10af0b38bcd1
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8477
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 718f10e0d68715be2d73e677974629452485c699
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Aug 7 16:28:48 2014 +0530

    cluster/dht: Added keys in dht_lookup_everywhere_done
    
    Case where both cached  (C1)  and hashed file are found,
    but hash does not point to above cached node (C1), then
    dont unlink if either fd-is-open on hashed or
    linkto-xattr is not found.
    
    Change-Id: I7ef49b88d2c88bf9d25d3aa7893714e6c0766c67
    BUG: 1116150
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    
    Change-Id: I86d0a21d4c0501c45d837101ced4f96d6fedc5b9
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8429
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: susant palai <spalai@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8116328a6b4ead0207fc5f93fcac9a2606c6f6ab
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Aug 8 01:56:23 2014 -0700

    porting: FreeBSD related changes to regression scripts
    
    - json_verify do not use '/usr/bin' let bash evaluate the location
    - TEST for test code compilation `bug-1051896.t`, `bug-1058663.t`,
      bug-905864.t
    - run-tests.sh - better checks for installed packages
    
    Change-Id: Ic7feda36ddfc082c609aabd75da2e9a8f59a92b3
    BUG: 1111774
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8435
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Emmanuel Dreyfus <manu@netbsd.org>

commit 37b31605c6a2495848d52270e37b5fa0a8b9fdd5
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 13 10:27:47 2014 -0400

    rdma: glusterfsd SEGV at volume start
    
    glusterfsd NULL ptr deref in proto/server: get_frame_from_request()
    with 'transport rdma' volume
    
    no test case, our regression test framework doesn't have Infiniband.
    If it did, the test case would be to create a 'transport rdma' volume,
    start it, and create/write/read/delete files on the volume.
    
    Change-Id: I91a6956bdf8f61f3853e0c0951744460ba138576
    BUG: 1129708
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8479
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5fe2233a8243160443e9bb438a40b1bcacac4fca
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Aug 13 15:20:20 2014 +0200

    NetBSD /dev/fuse detection
    
    NetBSD's FUSE being pure userland implementation, there is no /dev/fuse
    to open. Test /dev/puffs (kernel fs-in-userland subsystem supporting FUSE)
    insead.
    
    BUG: 764655
    Change-Id: Ia65e95c246dc31ea2839cf64d7c851430828542e
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8478
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 250210a36bfd5b5c44ad49ca1c3f6aef148da322
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Aug 13 10:17:50 2014 +0530

    tests: trigger entry heals by lookup
    
    Trigger entry heals explicitly by lookup until heal full is fixed in
    afr v2 to do conservative merge.
    
    Change-Id: I474b518045bebcf399bc414caff3b415259381d6
    BUG: 1127148
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8465
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c03e07b4147bb2fe902be77f0bbef9c9bae977ab
Author: ggarg <ggarg@redhat.com>
Date:   Tue Jun 17 16:25:03 2014 +0530

    glusterd: Coverity fix for going out of scope leaks of directory pointer
    
    In function volgen_apply_filters() directory stream associated with
    "filterdir" should be close after opening directory stream corresponding
    to directory name. closedir() also closes the underlying file descriptor
    associated with "filterdir".
    
    Coverity CID: 1124723
    
    Change-Id: I78ed04047ded98bf95d201afed01c727aa506882
    BUG: 789278
    Reviewed-on: http://review.gluster.org/8088
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit fd6765b4a3f8162bf36054cf3de6e88a6bdfadd3
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Aug 11 17:36:12 2014 -0700

    porting: OSX/Darwin 10.9 porting issues
    
    xdrproc_t() arguments are variadic and non-variadic
    
    On OSX > 10.9
    -------------
    typedef bool_t (*xdrproc_t)(XDR *, void *, unsigned int);
    
    On OSX < 10.9
    ------------
    typedef bool_t (*xdrproc_t)(XDR *, ...);
    
    FreeBSD all versions
    ------------
    typedef bool_t (*xdrproc_t)(XDR *, ...);
    
    NetBSD 6.1.4
    -----------
    typedef bool_t (*xdrproc_t)(XDR *, const void *);
    
    Linux all versions
    -----------
    typedef bool_t (*xdrproc_t)(XDR *, void *,...);
    
    This weird and odd implementations across various platforms
    should be handled properly.
    
    Change-Id: Iad8b7da2e5b82526bf3708cff31ab10ce09f59c9
    BUG: 1128820
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8458
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a66a483be2febd36e6cb338c9fe73d332257d89e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Aug 11 20:22:53 2014 +0530

    cluster/afr: Fix mem-leak
    
    Problem:
    local->xattr_req is already reffed with xattr_req that comes
    in lookup fop. But when afr_lookup_xattr_req_prepare is called
    local->xattr_req is over-written with dict_new() which leads
    to ref leak on the dict which came in lookup fop
    
    Fix:
    Create local->xattr_req only when it is NULL
    
    Change-Id: Ib1548f2df97688859f2cace44b93b3b733297c36
    BUG: 1128801
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8457
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c77a77ef0fca8371bba956b78a2da80f73f6f26b
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Aug 9 23:54:15 2014 -0700

    osx: Enable qemu feature build on Darwin
    
    Change-Id: Ie5d437aa6c52c180fd8d54680c5f882e75c0bf7e
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8448
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ccb5dc01b8916f0e7d1e3d3535a81cc8b0f0c25e
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Aug 10 19:44:58 2014 +0200

    Always build EC xlator
    
    Now EC xlator does not require MMX anymore, always build it.
    
    BUG: 764655
    Change-Id: I50a64e22c080f2759eaa57786e7f69c34f11f89c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8451
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit a1dff6498afaed5e87b383f6de6c183f52d7db41
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Aug 8 02:59:34 2014 -0700

    osx: snapview-server fails to build on OSX use 'syscall.h'
    
    Change-Id: I29aeb32a972ed6d19e779b9e79fce9a489848497
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8436
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b97ade3b05acf3784b0df11421e6b78fca0cfe85
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 8 12:01:34 2014 +0200

    Search zlib without pkg-config
    
    NetBSD has zlib installed in base system and no .pc file for it. In
    order to discover it, fallback to AC_CHECK_LIB is PKG_CHECK_MODULES
    fail to find it.
    
    This enables cdc xlator, and we pass tests/basic/cdc.t
    
    BUG: 764655
    Change-Id: Ide84402aa38edc2709d12e2530401c6b8c722529
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8437
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 31a0dbb21ebfaa2b25f6b407cbdbb5da1509db29
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Aug 4 13:22:10 2014 +0200

    Regression test portability: xargs
    
    Linux xarg complains about an empty input, while NetBSD xargs does not.
    This breaks tests where xargs is in a pipe after a command that should
    be tested. Make sure we test the first command without xargs
    
    BUG: 764655
    Change-Id: I754d7d52332221c462ce3594f4e8d8d62ae606d5
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8280
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 76b72680017c836eff8805ea0339f7827ba3e561
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Fri Aug 8 15:54:03 2014 +0530

    mount: Verify mount failure in mount.glusterfs wrapper.
    
    The result of mount command execution is not checked properly, thus
    no proper message given for the end user. This patch fix the same.
    
    Bug Id: 1128165
    Change-Id: I3882e34e840ed15b5ce48ed5e1ad51208e2be913
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8438
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 84cfd657e50a436027000e6147982c5ca57e5e50
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Aug 8 10:01:35 2014 -0400

    extras/LinuxRPM: error in Makefile.am
    
    Change-Id: I50de95ca6eff09338ce4a6f9f2b42aeccd10cae2
    BUG: 1128192
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8444
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 8c837b8e2a0f6fb369b4bc08d9e2a40394478daa
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 8 05:19:15 2014 +0200

    Wrong test in self-heal.t
    
    self-heal.t checks for gfid before and after an operation, but fails
    to do it on the same file since the prefix is not the same: undefined
    $B1 before and $B0 after.
    
    The errorcause the test to fail on NetBSD. I do not know how this test
    could pass on Linux before.
    
    BUG: 764655
    Change-Id: I6df1175e177855afca1736cf8c847c51fe407576
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8431
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2ec6ea43f2ddc6c00a030be6d04c00f0924277b7
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sun Jun 29 18:56:44 2014 -0700

    build: make GLUSTERD_WORKDIR rely on localstatedir
    
    - Break-way from '/var/lib/glusterd' hard-coded previously,
      instead rely on 'configure' value from 'localstatedir'
    - Provide 's/lib/db' as default working directory for gluster
      management daemon for BSD and Darwin based installations
    - loff_t is really off_t on Darwin
    - fix-off the warnings generated by clang on FreeBSD/Darwin
    - Now 'tests/*' use GLUSTERD_WORKDIR a common variable for all
      platforms.
    - Define proper environment for running tests, define correct PATH
      and LD_LIBRARY_PATH when running tests, so that the desired version
      of glusterfs is used, regardless where it is installed.
      (Thanks to manu@netbsd.org for this additional work)
    
    Change-Id: I2339a0d9275de5939ccad3e52b535598064a35e7
    BUG: 1111774
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8246
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f29da9bcc812e3d0711005ce86051d70c277a165
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Jul 29 02:21:20 2014 +0200

    Regression test portability: truncate, md5
    
    Add shell functions to replace truncate and md5, which are Linux specific
    Resubmit because of failed regression test with no apparent cause
    
    BUG: 764655
    Change-Id: I07200cf886bd52904a5cf63c66f43f0b1cc91540
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8341
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9978e61dc51d0318f92b1f2c2cbebfe9ce70b2ea
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Aug 5 12:35:10 2014 -0700

    tests: weighted-rebalance.t shouldn't write to '/dev/tty'
    
    On our jenkins instance "/dev/tty" doesn't exist, necessary
    output fails as below message
    
    ~~~
    ./tests/features/weighted-rebalance.t: \
             line 72: /dev/tty: No such device or address
    ~~~
    
    Comment out the debugging code
    
    Change-Id: Iba29b80c8ba2dcaab3d6654d7c54332a915bffb8
    BUG: 1114680
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8421
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8111756d0f7ff8b7e92cbb4ddb3833f72830e0b3
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Wed Jul 9 00:54:48 2014 +0530

    libglusterfs: wrong function definition of synclock_destory().
    
    synclock_destory() has been prototyped in syncop.h,
    how-ever synclock_destroy() is the actual function used in syncop.c.
    Correcting this function definition along with few typos.
    
    
    Change-Id: I35a818190c1d37c303279ca7a820f01895751bd9
    BUG: 1075417
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8266
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ef60640dfab44a53083a717bb4ee1386f8baad92
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jul 23 18:24:55 2014 +0530

    doc: afr-locks and its evolution
    
    History and current state of how AFR uses the inode and entry locks
    provided by the locks xlator
    
    Thanks to Pranith for patiently explaining this.
    
    Change-Id: I25d21c6361e95aa0b3edcffe9b3b9e470f488bc6
    BUG: 1118309
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8364
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 866a9b96212989ea2cad399a56bb4b71623c6b0c
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Tue Jul 29 18:51:21 2014 +0530

    gluster vol set nfs-ganesha.enable off fails to unexport volume.
    
     Due to a parameter type change in upstream nfs-ganesha
    ( v2.1 and above ), gluster vol set <volname> nfs-ganesha.enable
     off doesn't unexport the volume in question if it was already
    exported.
    A minor change in the hook script would result in the
    expected behaviour.
    
    Change-Id: I46f76f3cde6b6ebd7a94d5ee16f05a3648a2840f
    BUG: 1124711
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/8390
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6cc22537b68cb52ebc0101fca7fb232c183b00a1
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Jul 29 18:50:29 2014 -0700

    socket: add boundary checks for iobuf_get2 over rpc_hdr_bytes
    
    A malformed packet can cause a OOM while peforming iobuf_get2()
    on a large enough packet side.
    
    Such a scenario is observed when running vulnerability tests,
    it would look like one of those tests perhaps based on DDOS (Denial
    of Service) attacks hand-crafts a RPC packet which is of a large
    enough size - since we do not verify the size and do not provide
    any boundary checks, there are secenarios where it leads to OOM.
    
    Reproducible consistently with those tests has revealed that we
    should be ideally be adding a boundary check.
    
    Limit such an allocation to a 1gigabyte, as it might be sufficient
    to handle for all variety of RPC packets.
    
    Change-Id: I5f1411dd96d6f167993d28a1718ffef2fb4e9923
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8384
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2ff46b74b25cc2e61bfe67c43b31d8f5ca88e4ac
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Aug 2 05:42:39 2014 +0200

    Regression test portability: arequal-checksum
    
    Building arequal-checksum on non Linux systems requires a few adjustments:
    - use __builtin_alloca() on all platforms
    - on systems without argp, get it from contrib/standalone-argp
      (this requires adding cflags support to the build_tester function)
    - FTW_ACTIONRETVAL option to nftw(3) is GNU libc specific, work around
      if it does not exist.
    - md5sum is Linux-specific. Use md5 -n on NetBSD and md5 -q on FreeBSD/Darwin
    - Use 'cc' as synonymous for all compilers, it can behave as gcc/clang depending
      on which is default
    - cleanup tabs/whitespaces
    
    BUG: 764655
    Change-Id: I9090c17da596fbf00fc1fbd7593163ce8cd3b84c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8283
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0e8c537d6f48857b0f3c0ef10ce1c4458e303be8
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri Aug 1 16:12:38 2014 +0530

    feature/geo-rep: Keep marker.tstamp's mtime unchangeable during snapshot.
    
    Problem:
    
    Geo-replicatoin does a full xsync crawl after snapshot
    restoration of slave and master. It does not do history crawl.
    
    Analysis:
    
    Marker creates 'marker.tstamp' file when geo-rep is started
    for the first time. The virtual extended attribute
    'trusted.glusterfs.volume-mark' is maintained and whenever
    it is queried on gluster mount point, marker fills it on
    the fly and returns the combination of uuid, ctime of
    marker.tstamp and others. So ctime of marker.tstamp, in other
    sense 'volume-mark'  marks the geo-rep start time when the
    session is freshly created.
    
    From the above, after the first filesystem crawl(xsync) is
    done during first geo-rep start, stime should always be less
    than 'volume-mark'. So whenever stime is less than volume-mark,
    it does full filesystem crawl (xsync).
    
    Root Cause:
    
    When snapshot is restored, marker.tstamp file is freshly
    created losing the timestamps, it was originally created with.
    
    Solution:
    
    1. Change is made to depend on mtime instead of ctime.
    2. mtime and atime of marker.tstamp is restored back when
       snapshot is created and restored.
    
    Change-Id: I4891b112f4aedc50cfae402832c50c5145807d7a
    BUG: 1125918
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8401
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 51394183e94ac0be70fcf22793b2040ba3f0b918
Author: Kotresh H R <khiremat@redhat.com>
Date:   Mon Aug 4 15:33:02 2014 +0530

    geo-rep/libgfchangelog: Support of symlinks while creation of working dir.
    
    In gf_changelog_register, enable symlink support while creating
    working directory if its not already created.
    
    Change-Id: I4b81762d04f5276a65087d2ff94f2a36dc504b58
    BUG: 1125843
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8409
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 6ff2fd2e05c35562cf9505b95d191ee7fe001823
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Jul 31 05:37:37 2014 +0200

    Do not call rpc_transport_unref() on NULL trans
    
    rpc_clnt_disable() sets rpc->conn->trans to NULL, hence we should not
    call rpc_transport_unref() afterwards. I moved it before the
    rpc_clnt_disable() call, but I am not sure it should be called at all,
    perhaps it should just go away.
    
    BUG: 764655
    Change-Id: I488d0207494e3a3fad52e64e67b2e740b236b864
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8393
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 36a6652f5d458c2ce0a734e11586a623848f991c
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Aug 1 01:30:45 2014 +0530

    glusterd: Bump max op version
    
    Change-Id: Ic66a0a751233ebbcb65d13f7e3265a046fae9a0b
    BUG: 1125431
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8397
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 8080a5555e7ba17b9e691171259899ca9e390c76
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Thu Jul 31 14:37:19 2014 +0530

    glusterd/snapshot:  Inherit the mount options of a original brick
    when creating snapshots
    
    When creating a snapshot a LVM is created at the backend and is mounted
    under /var/run/gluster/snaps/... However, this mount does not inherit
    the mount options for the original brick acting as the parent for the
    snap.
    
    If the snap is restored, this could lead to performance degredations,
    functional limitations, or in extreme scenarios even potential data
    loss.
    
    Change-Id: I67d70fd83430d83dacc5380c6c928e27fb9c9e1b
    BUG: 1125180
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8394
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f3204a06eb8156743110b1613b4b4b63b70572b6
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Jul 8 17:52:57 2014 +0200

    cluster/ec: Fix incorrect management of NFS requests
    
    Some operations, specially those comming from NFS, do not use a
    regular fd and use an anonymous fd (i.e. a previous open call has
    not been sent). Any context information created during open or
    create will not be present on these fd's, so we simply return NULL
    for contexts of those fd.
    
    Also it seems that NFS can send write requests with a very big
    buffer (higher that the default value of 128 KB). Some changes
    have been made to correctly handle these large buffers.
    
    Change-Id: I281476bd0d2cbaad231822248d6a616fcf5d4003
    BUG: 1122417
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8367
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d9fbc8518962c8607cc741626c2e197098e749b5
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Tue Jul 15 18:43:44 2014 +0200

    ec: Test volume mount point in a better way
    
    An 'ls -a1' on an empty volume seems to return 3 entries instead
    of the expected 2 ('.' and '..') in the build servers. I changed
    the test to a simple 'stat', which is enough and more reliable.
    
    Change-Id: I12d0f47394ad378b40fc9b86507cdb3543f99970
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8313
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 410c15a1fb1b9f1cfaa5ee315b9ca39e27c04ec8
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Jul 16 16:52:42 2014 +0200

    tests: Avoid test bug-884597.t to loop infinitely
    
    If some unexpected error happens while this test is trying to
    create a linkto file, an infinite loop is generated and the test
    never ends.
    
    This patch limits the number of retries it can do to find that
    file.
    
    Change-Id: Ie556c509116109ead99c78d671b2669b4428faac
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8318
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 41e2384181e854c06d3a234c2f37aacf9d92f53c
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Tue Jul 29 20:20:13 2014 +0530

    nfs-ganesha  dumps core when Pynfs tests OPDG1O and OPDG11 are run.
    
    Assgining -1 to ret if fd_create fails. The tests somehow
    enter an error case 'if' block (this will be a separate bug fix),
    before glfd is created. Need an addiitional check to see
    if glfd exists before entering the 'else' block in 'out'.
    
    glfs_h_creat was missing a similar check, adding that in
    this bug fix.)
    
    Change-Id: I3b69540c53e8169538848b9e7f23ffc8ef0ac189
    BUG: 1121062
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/8333
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 61e2ed9d178910fdf7d0499b54601a4191f9cb75
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Aug 2 02:23:34 2014 +0200

    Regression test portability: system-specific cleanup
    
    Add NetBSD system-specific cleanup code
    Define killall as pkill when it is missing.
    
    BUG: 764655
    Change-Id: I3a1cfa3029fd60ede334a670fc115c211700063d
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8290
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d09f69e76f86e727ea9a3487f57a0d7fd7b5bcd7
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri Aug 1 14:08:56 2014 +0530

    geo-rep/libgfchangelog: Create working dir during changelog_register if not present.
    
    Earlier, xysnc's register was being called first,
    which was creating working directory before calling
    changelog_register. Now it is history crawl first.
    Hence working directory would not have been created.
    Create it in gf_changelog_register itself if it is
    not already created.
    
    Change-Id: Ief3f2b87deaf5da16c135b64be1be42e0a7647f3
    BUG: 1125843
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8399
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b12ee8fbaf8f720f9072ea6b62bb844232870e6e
Author: Zhang Huan <zhhuan@gmail.com>
Date:   Fri Mar 7 11:08:47 2014 +0800

    storage/posix: fix issue in posix_fsync
    
    Fix the issue that posix_fsync does not correctly return and save
     error code in op_errno when call to sys_fdatasync fails.
    
    Change-Id: Id0b62cfa009dbb52c8a0992abd5c46330fa0a8c0
    BUG: 1125814
    Signed-off-by: Zhang Huan <zhhuan@gmail.com>
    Reviewed-on: http://review.gluster.org/8398
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 590006d824f4051acdccbe59415fc4772e3caa2f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 15 21:45:35 2014 +0530

    doc: mem-pool documentation
    
    Change-Id: I9bc454c92a078de5e3a30372a50c6f2cbdcd6c21
    BUG: 1118309
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8343
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 966997992bdbd5fffc632bf705678e287ed50bf7
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Jul 25 17:21:04 2014 +0530

    cluster/dht: Modified logic of linkto file deletion on non-hashed
    
    Currently whenever dht_lookup_everywhere gets called, if in
    dht_lookup_everywhere_cbk, a linkto file is found on non-hashed
    subvolume, file is unlinked. But there are cases when this file
    is under migration. Under such condition, we should avoid deletion
    of file.
    
    When  some other rebalance process changes the layout of parent
    such that dst_file (w.r.t. migration) falls on non-hashed node,
    then may be lookup could have found it as linkto file but just
    before unlink, file  is under migration or already migrated
    In such cased unlink can be avoided.
    
    Race:
    -------
    If we have two bricks (brick-1 and brick-2) with initial file "a"
    under BaseDir which is hashed as well as cached on (brick-1).
    
    Assume "a"  hashing gives 44.
    
                                  Brick-1              Brick-2
    
    Initial Setup:               BaseDir/a             BaseDir
                                 [1-50]                [51-100]
    
    Now add new-brick Brick-3.
    
    1. Rebalance-1 on node Node-1 (Brick-1 node) will reset
    the BaseDir Layout.
    
    2. After that it will perform
    a)  Create linkto file on  new-hashed (brick-2)
    b)  Perform file migration.
    
    1.Rebalance-1 Fixes the base-layout:
                     Brick-1             Brick-2           Brick-3
                     ---------         ----------         ------------
                     BaseDir/a            BaseDir           BaseDir
                      [1-33]              [34-66]           [67-100]
    
    2. Only a) is     BaseDir/a          BaseDir/a(linkto)   BaseDir
       performed                         Create linktofile
    
    Now rebalance 2 on node-2 jumped in and it will perform
    step 1 and 2-a.
    
    After (rebal-2, step-1), it changes the layout of the BaseDir.
                        BaseDir/a     BaseDir/a(link)    BaseDir
                        [67-100]           [1-33]        [34-66]
    
    For  (rebale-2, step-2), It will perform lookup at Brick-3 as w.r.t new
    layout 44 falls for brick-3. But lookup will fail.
    So  dht_lookup_everywhere gets called.
    
    NOTE: On brick-2 by rebalance-1, a linkto file was created.
    
    Currently that linkto files gets deleted by rebalance-2 lookup as it
    is considered as stale linkto file.  But  with patch if rebalance is
    already in progress or rebalance is over,  linkto file will not be
    unlinked. If rebalance is in progress fd will be  open and if rebalance
    is over then linkto file wont be set.
    
    Change-Id: I3fee0d28de3c76197325536a9e30099d2413f079
    BUG: 1116150
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8345
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9de6d8b555a5202cbf80753f41efa03032edb02b
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jul 31 11:51:12 2014 +0200

    ec: Add -msse2 option to avoid fedora/rawhide compilation errors
    
    This solves a compilation error on some compiler versions.
    To avoid compilation issues on non-Intel architectures, patch
    http://review.gluster.org/8366/ has already been merged. It
    disables ec on those architectures.
    
    These modifications are temporary patches until a proper
    solution for bug #1125166 is ready.
    
    Change-Id: I74d0b79e84601cc4f86ad08ce0f8102b99a79a68
    BUG: 1125168
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8395
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a278c2aecedfbe17e2749109d73b292ca25ff439
Author: Anders Blomdell <anders.blomdell@control.lth.se>
Date:   Tue Jul 29 17:11:20 2014 +0200

    Symlink mtime changes when rebalancing
    
    Added mtime preservation for special files during rebalance.
    
    Change-Id: If04921d4d66853fde8b4d8a3ab748790864f8f42
    BUG: 1122443
    Signed-off-by: Anders Blomdell <anders.blomdell@control.lth.se>
    Reviewed-on: http://review.gluster.org/8383
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 93a4558dddbea78a51171b2bf92e37da3ffb40dd
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jul 10 12:49:53 2014 +0530

    client/rpc: Add ping and msgs stats
    
    This can be seen as below,
    
    ># cat $META/graphs/active/vol-client-0/private |grep ping_msgs_sent
    ping_msgs_sent = 2
    
    ># cat $META/graphs/active/vol-client-0/private |grep "^msgs_sent"
    msgs_sent = 13
    
    where $META is /<fuse-mountpt>/.meta
    
    Change-Id: I2107ec2b045bac701377760635e18758adb943a3
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8285
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 72d2143c78bb01135eef8fa6a210e8a1a0f987ce
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Jul 29 02:32:14 2014 +0200

    Regression test portability: run-test.sh
    
    - Check for pidof(8) presence. It may not be present on non Linux systems
    - Add a -f flag to run-tests.sh to bypass utility presence checks
    
    Submit again because of spurious regression test failure
    
    BUG: 764655
    Change-Id: Iee6282c686c63a01808543054f8e5a3b5b79fca2
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8279
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 60f2e231bbf4daef11793710bb69bdfbcfca89a1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jul 30 15:19:38 2014 +0200

    build: fix compile issue in unittest on EPEL-5
    
    When building the current master branch on EPEL-5, the following error
    is observed:
    
          CC     dht_layout_unittest-dht_layout_mock.o
        unittest/dht_layout_mock.c:77:2: error: no newline at end of file
        make[5]: *** [dht_layout_unittest-dht_layout_mock.o] Error 1
        make[5]: *** Waiting for unfinished jobs....
    
    EPEL-5 has this gcc:
    
        $ gcc --version
        gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-54)
    
    The fix is simple enough, dht_layout_unittest-dht_layout_mock.c should
    have a line ending.
    
    BUG: 1124858
    Change-Id: I8ca7a1699fd1c35694073b9577f94ae525854713
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8392
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Luis Pabon <lpabon@redhat.com>

commit e8a1fc34ad3891e8b739278a909dbd91c56b9f4e
Author: Anders Blomdell <anders.blomdell@control.lth.se>
Date:   Tue Jul 8 15:36:45 2014 +0200

    Make RPM's with current git tag
    
    1. clear autom4te.cache
    2. autogen.sh
    3. configure --with-previous-options
    
    Change-Id: I90c1820d22207d18b1bb367444b21918467baea5
    BUG: 1117921
    Signed-off-by: Anders Blomdell <anders.blomdell@control.lth.se>
    Reviewed-on: http://review.gluster.org/8293
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit bb385390a945fe755a302a011aa7a2ec05941fad
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 21 10:22:22 2014 +0530

    nfs/drc: Fix memory corruptions
    
    * A wrong memory allocator was used to (de)allocate nodes (not data in
    them) of rb tree. This patch uses default allocator, since that suits
    our purpose.
    * Fix reference counting of client, though hitting the codepath
    containing this bug is highly unlikely.
    
    Change-Id: I7692097351d6e54288fee01da5af18e761fd0e8c
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1067256
    Reviewed-on: http://review.gluster.org/7816
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 73fc66fb2dd79b39b6021a6309fb859363c2e968
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jul 22 13:45:41 2014 +0530

    cluster/afr: Improve inodelk/entrylk failure log messages
    
    Change-Id: Ie792875546b4f8e11ebf870a6e63aaf5cb221976
    BUG: 1121920
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8344
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 9f41712d060a71259e4970b9c8b32771a6d1f2c7
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Tue Jul 15 13:49:41 2014 +0530

    glusterd: Error msg for snapshot status for no existing snaps
    should be aligned with error messages of info and list
    
    When a snapshot operation like status, info, list
    performed on a non-existing snapshot.
    For Status error message is displayed as 'Snap not found'
    For List and Info error message is displayed as 'Snapshot does not exist'
    Have the consistant error message all the places
    
    Change-Id: I7b241217dba62fda844481731a6858e4ecb12897
    BUG: 1119641
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8309
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8732ee5319bfe4649473c29458a6ab65b73d5516
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Sun Jul 27 10:36:52 2014 -0400

    glusterd/snapshot: Proper err msg for snapshot create command
    
    problem: Snapshot command fails if one or more bricks are not thinly
    provisioned. But the error message is a generic error message which
    is confusing to the user.
    
    fix: Provide correct error message in case of failure.
    
    Change-Id: Iad247f966423a8f73ef6da57cab7ed6cddc05861
    BUG: 1123646
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/8377
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7d74792d225196585c24f8843bdba61a14c1c3d3
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jul 22 11:43:09 2014 +0530

    cli : glusterd getspec usage correction
    
    gluster system getspec asks to input volume-id instead of volume name
    
    Change-Id: I0baef9c937fc8948477aa65c8f98916b28c1e484
    BUG: 1121870
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8342
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit df770496ba5ed6d2c72bcfc76ca9e816a08c383a
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 21 18:46:14 2014 +0530

    dht: fix rename race
    
    Additional check to check if we created the linkto
    file before deleting it in the rename cleanup function
    
    Change-Id: I919cd7cb24f948ba4917eb9cf50d5169bb730a67
    BUG: 1117851
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8338
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 45fbf99cb669e891a84a8228cef27973f5e774bf
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jul 17 21:59:26 2014 +0530

    storage/posix: removing deleting entries in case of creation failures
    
    The code is not atomic enough to not to delete a dentry created by a
    prallel dentry creation operation.
    
    Change-Id: I9bd6d2aa9e7a1c0688c0a937b02a4b4f56d7aa3d
    BUG: 1117851
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8327
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b56719fc478590815b6b8bc1e5a7dee5194555df
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Jul 28 09:53:50 2014 +0530

    doc : man page and admin-guide for newly introduced snapshot delete option.
    
    Change-Id: Iab5e7f63d673a2040e8d83ab7280121ff468836e
    BUG: 1112613
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8378
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 67a6f402d4a4af2e7d9b8d80b25c94f1a08ef029
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jun 6 12:51:57 2014 +0530

    libgfapi : glfs_create()/glfs_h_creat()/glfs_open()/glfs_h_open() should set
    fd->flags before syncop_open()
    
    glfs_create() and glfs_open() do not set fd->flags before calling syncop_open().
    This patch addresses this problem and ensure the flags are set in fd before
    invoking syncop_open()
    
    Change-Id: I9ef3243b1de610e1dd1a3e37b66fc2f763a865f9
    BUG: 1096047
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7999
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a95444c95cfde4d80c179f2af2f0334565049a51
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Jul 10 06:02:38 2014 +0200

    Regression test portability: ps
    
    ps aux is truncated to the terminal width on NetBSD, Use ps auxww to
    avoid that
    
    BUG: 764655
    Change-Id: I28a2fc23e2823dd6524a72da30111b86fc4bfa7b
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8281
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 38bae1bcf95e0b4f713120783c2e26fcc3f629b5
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Jul 10 15:13:27 2014 +0200

    Regression test portability: hostname
    
    The --fqdn option to hostname is Linux only
    This is resubmission of the same patch. I assume the regression test
    is a test bug
    
    BUG: 764655
    Change-Id: I6437124186435f10d1ee6a847e2593554d633716
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8282
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 195594585eb5f6038bda5f085a773b3f8543962d
Author: Kotresh H R <khiremat@redhat.com>
Date:   Wed Jul 23 18:12:39 2014 +0530

    tests/bug-961307.t: echo output string in case of failure for easy debug.
    
    Change-Id: I5bb5d7f2d9380da3247588e8eff10b559e17ff3f
    BUG: 1122533
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8362
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f8496dab2f6111bdc5ced0881d15061160b76e52
Author: Anders Blomdell <anders.blomdell@control.lth.se>
Date:   Thu Jul 24 16:55:45 2014 +0200

    Allow gluster to be used with linux automounter
    
    Added (ignored) -n option to mount.glusterfs command
    
    Change-Id: I9209da215d38507cd9d01b1e9af4aecff4414f83
    BUG: 1123004
    Signed-off-by: Anders Blomdell <anders.blomdell@control.lth.se>
    Reviewed-on: http://review.gluster.org/8373
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3e7c3b25129df098511970c79faf561be08ef87b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sat Jul 12 22:31:45 2014 +0530

    rpc,glusterd: Set ret to 0 after call to rpc_clnt_submit()
    
    This is to guard against a double STACK_DESTROY in the event that
    rpc_clnt_submit() failed and returned -1 anytime after sending the
    request over the wire. in which case the stack could be destroyed
    twice: once in the callback function of the request and once in
    the error codepath of some of the callers of glusterd_submit_request().
    This bug was introduced in http://review.gluster.org/#/c/8257/
    
    Change-Id: I18a345db6eafc62ba312743201ced7d3f8697622
    BUG: 1116243
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8301
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7b7f8533331f9478724e226a9c3a4a34dfe11228
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 9 17:31:52 2014 +0530

    doc: How to generate and read statedump
    
    Thanks to Poornima G's help with iobuf
    Section explanation.
    
    Change-Id: I17737fdbd1f402914f7e67fb4047f5c26ea5c36c
    BUG: 1118309
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8288
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5986d22e621e0c682f319bb6a0a8e622a8c0970d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Jul 27 08:45:50 2014 +0200

    Attempt to fix cmockery2 build
    
    The current code assumes cmockery2 is installed in default paths.
    Use PKG_MODULES_CHECK to find it using pkg-config if it is not. If
    not found by pkg-config, try AC_CHECK_LIB.
    
    There are also some build flag adjustement so that local overrides
    do not loose the required -I flags.
    
    This includes and enhance http://review.gluster.org/8340/
    
    BUG: 764655
    Change-Id: Ide9f77d1e70afe3c1c5c57ae2b93127af6a425f9
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8365
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 35c6ca05d8ee0e1be1b67ac64d32c21b195aaeea
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Jun 23 09:35:52 2014 +0530

    feature/snapshot : Interface to delete all snapshots belonging
    to a system as-well-as to a particular volume.
    
    Problem :
    With the current design we can only delete a single snapshot.
    And the deletion of volume which contains snapshot is not allowed.
    Because of that user might be forced to delete all the snapshots
    manually before he is allowed to delete a volume.
    
    Solution:
    Following is the interface with which user can delete
    all the snapshots of a system or belonging to a particular volume.
    
            Syntax : gluster snapshot delete all
    
            *To delete all the snapshots present in a system
    
            Syntax : gluster snapshot delete volume <volname>
    
            *To deletes all the snapshot present in a volume specified.
    
    ========================================================================
    Sample Output:
    
    Case 1 : Deleting a single snapshot.
    [root@snapshot-24 glusterfs]# gluster snapshot delete snap1
    Deleting snap will erase all the information about the snap. Do you still want to continue? (y/n) y
    snapshot delete: snap1: snap removed successfully
    
    -----------------------------------------------------------------
    Case 2 : Deleting all the snapshots in a Volume.
    [root@snapshot-24 glusterfs]# gluster snapshot delete volume vol1
    Volume (vol1) contains 9 snapshot(s).
    Do you still want to continue and delete them?  (y/n) y
    snapshot delete: snap2: snap removed successfully
    snapshot delete: snap3: snap removed successfully
    snapshot delete: snap4: snap removed successfully
    snapshot delete: snap5: snap removed successfully
    .
    .
    .
    
    -----------------------------------------------------------------
    Case 3 : Deleting all the snapshots in a system.
    [root@snapshot-24 glusterfs]# gluster snapshot delete all
    System contains 4 snapshot(s).
    Do you still want to continue and delete them?  (y/n) y
    snapshot delete: snap7: snap removed successfully
    snapshot delete: snap8: snap removed successfully
    snapshot delete: snap9: snap removed successfully
    snapshot delete: snap10: snap removed successfully
    ========================================================================
    
    Change-Id: Ifec8e128ab2011cbbba208376b9c92cfbe7d8d71
    BUG: 1112613
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8162
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit fb730072c27c9ae1b99ff41dbff45e721017d543
Author: Sachin Pandit <spandit@redhat.com>
Date:   Wed Jul 23 08:24:19 2014 +0530

    doc : man page for snapshot commands
    
    This patch also contains few modifications in admin documentation.
    
    Change-Id: I7bc2a88e6cbcfe81dcfafc2956f5b7c5524b0f0b
    BUG: 1122399
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8357
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit c57895242fff0c05a24f99273f25cd793336f08d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jul 17 08:30:52 2014 +0000

    glusterd: update volinfo->subvol_count during remove-brick operation.
    
    Problem:
    In glusterd_op_remove_brick(), volinfo->subvol_count was getting updated only if
    the replica count was reduced due to which subvol_matcher_verify() gave false
    errors under certain scenarios (see bug description).
    
    Fix:
    updated subvol_count for every remove-brick operation.
    
    Change-Id: Id72691e2bda1c624cd7d8cae92f6bf32c101a6d3
    BUG: 1120647
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8326
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 88eb28678c3a16264b5baa57af0d16778ea2c9e6
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sun Jul 20 14:59:42 2014 -0700

    glusterd: Avoid spurious WARNING 'op_ctx modification failed'
    
    This patch fixes by wrapping this whole scenario and skips
    op_ctx modification for necessary commands.
    
    Change-Id: I3ecec19caefdc699d9a2dabfb456a89758ae4aa4
    BUG: 1066529
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8337
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 54cfb7dab45105e5f9a123503c4f524b99c633ce
Author: ndarshan <dnarayan@redhat.com>
Date:   Tue Jul 22 14:19:19 2014 +0530

    cli: Xml output for geo-replication status command.
    
    This patch adds xml output for geo-replication status
    and status detail command.
    sample:
    --------------------------------------------------------------
      <geoRep>
        <volume>
          <name>master</name>
          <sessions>
            <session>
            <session_slave>:2a301d66-b9d2-44b4-b827-d680d67123eb:ssh://XXXXXXXXXX::slave</session_slave>
              <pair>
                <master_node>localhost.localdomain</master_node>
                <master_node_uuid>2a301d66-b9d2-44b4-b827-d680d67123eb</master_node_uuid>
                <master_brick>/root/master_b1</master_brick>
                <slave>ssh://XXXXXXXXXXX::slave</slave>
                <status>faulty</status>
                <checkpoint_status>N/A</checkpoint_status>
                <crawl_status>N/A</crawl_status>
              </pair>
            </session>
          </sessions>
        </volume>
      </geoRep>
    -------------------------------------------------------------
    
    Change-Id: Ia19dbe751c3ab1ec7cb8923cdd6c8b99c374072f
    BUG: 1121518
    Signed-off-by: ndarshan <dnarayan@redhat.com>
    Reviewed-on: http://review.gluster.org/8089
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit ddd132a3b20d650edbda318c773b6d54a04f6675
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Thu Jul 24 12:47:04 2014 +0530

    glusterd/snapshot: Print correct error message  on cli
    for snapshot operation performed on a cluster with
    op-version less than 30600
    
    Currently we get error message as  on cli 'Another transaction is in progress
    Please try again after sometime' when a snapshot operation is performed
    on a cluster with op-version less than 30600.
    We need to print the correct error message in this case.
    
    Change-Id: I5f144428d928393c3796bde96ce6e3a40fca8141
    BUG: 1122816
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8371
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 6328019bd197efa25294194acaf946557d84f9fb
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jul 23 18:08:08 2014 +0530

    cli: Fix no libxml compilation for snapshot status
    
    BUG: 1122186
    Change-Id: Ib887f2194258e85d40f65a758b6a963a17911395
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8363
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>

commit 00bcf8e80bd65de7a8a102b137d35af3ba2cc3c1
Author: Sachin Pandit <spandit@redhat.com>
Date:   Thu Jun 26 07:51:02 2014 +0530

    cli/snapshot : Dont display the snapshot hard-limit, soft-limit
    and auto-delete value in gluster volume info.
    
    Problem : Even though snap-max-hard-limit, snap-max-soft-limit and
    auto-delete values were not set explicitly, It was getting showed
    in the output of gluster volume info.
    
    Solution : Check if the value is already present in dictionary
    (That means, it is set), If value is not present then consider
    the default value,
    
    NOTE : This patch doesn't solve the problem where the values
    which is set globally are being displayed in gluster volume info
    
    Change-Id: I61445b3d2a12eb68c38a19bea53b9051ad028050
    BUG: 1113476
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8191
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit f4110bed9230025ef7cac8e550057e316f9de1cb
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jun 23 13:43:20 2014 +0530

    geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl
    
    For effective handling of deletes and renames use history crawl
    as much as possible. History crawl will run in loop till it syncs
    all data before live changelog time.
    
    When it uses xsync crawl(fallback when changelog not available, or
    very first crawl) it sets upper limit to crawl.
    
    After completing History crawl, it checks actual end time returned
    by history api to compare with register time, if actual end is less
    than register time then run history crawl one more time.
    
    If first turn history processing time is less than the CHANGELOG
    ROLLOVER TIME then sleep for the difference, After sleep if it is
    guaranteed that rollover will happen and switches to live changelog
    consumption without switching to xsync. This sleep is only when
    history processing completed < CHANGELOG_ROLLOVER_TIME and sleep
    only after the first turn, So will not affect the performance.
    
    BUG: 1112238
    Change-Id: I644ef24b07e42e81cec96a025ebd21244a555ec0
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8151
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 8a24b1487d440c23b00b56aba5b9bfb77af6ef03
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Jul 18 15:36:42 2014 +0530

    features/changelog: Capture "correct" internal FOPs
    
    This patch fixes changelog capturing internal FOPs in a cascaded
    setup, where the intermediate master would record internal FOPs
    (generated by DHT on link()/rename()). This is due to I/O happening
    on the intermediate slave on geo-replication's auxillary mount with
    client-pid -1. Currently, the internal FOP capturing logic depends
    on client pid being non-negative and the presence of a special key
    in dictionary. Due to this, internal FOPs on an inter-mediate master
    would be recorded in the changelog. Checking client-pid being
    non-negative was introduced to capture AFR self-heal traffic in
    changelog, thereby breaking cascading setups. By coincidence,
    AFR self-heal daemon uses -1 as frame->root->pid thereby making
    is hard to differentiate b/w geo-rep's auxillary mount and self-heal
    daemon.
    
    Change-Id: Ib7bd71e80dd1856770391edb621ba9819cab7056
    BUG: 1122037
    Original-Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8347
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1706151a42ce92057b01f4c6869bf66c65769021
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Jul 23 15:11:56 2014 +0200

    Disable Erasure Code xlator if MMX is missing
    
    Erasure Code xlator requires MMX instruction set.
    Disable building it if MMX is missing.
    
    BUG: 764655
    Change-Id: Id9fe87db33e00c5630c1f3633ebd50fc4ebaec4d
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8366
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f86d3facd31655a2b51af5a6910fc9355d442622
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jul 23 12:47:33 2014 +0530

    Bump op-version for 3.7.0
    
    Change-Id: I4542edeca140bc2252d765b5cfc2e24d1d90cdb1
    BUG: 1122398
    Reviewed-on: http://review.gluster.org/8354
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit b1cf59bf134105de678f42e96b3c96fd62d7f224
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Jul 16 15:49:48 2014 -0700

    porting: include compat-errno.h for errno's
    
    disperse module fails to compile since
    ENODATA is non-existent on FreeBSD/Darwin
    
    Use errno conversion in compat-errno.h to avoid
    build issues.
    
    Change-Id: I8203b7195c198c77202bde9bbec1813a487f923a
    BUG: 1111774
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8320
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 56ffb164743449897f1cdecd3dbe085a0f0a66d7
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Jul 9 15:16:00 2014 +0530

    features/marker: Fill loc->path before sending the control to healing
    
    Problem:
    The xattr healing part of the marker requires path to be present in the loc.
    Currently path is not filled while triggering from the readdirp_cbk.
    
    Solution:
    Current patch tries to fill the loc with path.
    
    Change-Id: I5c7dc9de60fa79ca0fe9b58d2636fd1355add0d3
    BUG: 1118591
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/8296
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 5e1872c464f34295df136d4120110c3c53c5f599
Author: ndarshan <dnarayan@redhat.com>
Date:   Mon Jul 21 13:55:33 2014 +0530

    cli: Xml output for geo-replication config command
    
    This patch adds xml output for geo-replication config
    command.
    sample:
    ---------------------------------------------------------------------
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <geoRep>
        <config>
          <parameter1_name>value</parameter1_name>
          <parameter2_name>value</parameter2_name>
          ...
          ...
          ...
        </config>
      </geoRep>
    </cliOutput>
    ---------------------------------------------------------------------
    
    Change-Id: Iac0451983ae5d0e65b95604eb1c29b968e1ee22f
    BUG: 1121518
    Signed-off-by: ndarshan <dnarayan@redhat.com>
    Reviewed-on: http://review.gluster.org/8270
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 464ff8f7592e7d6a9239ca1fab1928d4a608f253
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Wed Jul 16 13:50:53 2014 +0200

    ec: Fixed coveriry scan issues
    
    CID list:
    
      1226163 Logically dead code
      1226166 Missing break in switch
      1226167 Missing break in switch
      1226168 Missing break in switch
      1226169 Missing break in switch
      1226170 Missing break in switch
      1226171 Missing break in switch
      1226172 Missing break in switch
      1226173 Missing break in switch
      1226174 Missing break in switch
      1226175 Missing break in switch
      1226176 Missing break in switch
      1226177 Missing break in switch
      1226178 Data race condition
      1226179 Data race condition
      1226180 Data race condition
      1226181 Thread deadlock
      1226182 Uninitialized pointer read
      1226183 Uninitialized pointer read
      1226184 Read from pointer after free
    
    Change-Id: I4d33aa42289371927175c43bb29e018df64fb943
    BUG: 789278
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8317
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f6ddb4675c096dc81420ed84fb2a6fefa9fea563
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Jul 14 13:07:08 2014 +0000

    gluster: Fix the recursive goto outs in the source code.
    
    Added a script check_goto.pl, that when run from
    the source code root, will scan all .c files to match
    the following pattern:
    
    label:
            if (condition)
                goto label;
    
    On finding such a pattern the script will print the file name
    and the line number. There are certain cases where the above
    recursive pattern is intended. Hence adding those labels to
    ignore-labels. Thanks Vijaikumar Mallikarjuna for the perl
    script.
    
    Also fixed all such existing errors
    
    Change-Id: I1b821d0a8c296f16e40faff20bd029bdc880c2e9
    BUG: 1119256
    Signed-off-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8307
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 5b8de971a4b81bc2bd6de0ffc6386587226295c6
Author: Anders Blomdell <anders.blomdell@control.lth.se>
Date:   Fri Jul 11 19:10:21 2014 +0200

    Use C-locale for numeric/string conversion routines
    
    (strtod, ...) or config file parsing might fail.
    
    
    Change-Id: I649f29bbf87222399a0c2d1ed5a3bf136c613b9b
    BUG: 1117951
    Signed-off-by: Anders Blomdell <anders.blomdell@control.lth.se>
    Reviewed-on: http://review.gluster.org/8299
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 57c61d70ec1920f731f9509510e6913aa1d62aa3
Author: Tiziano Müller <tiziano.mueller@stepping-stone.ch>
Date:   Fri Jul 18 09:24:38 2014 +0200

    build: add libraries to LIBADD instead of LDFLAGS
    
    For a number of linker flags the order of the object files and the libs
    to link against matter (for example -Wl,--as-needed). Make sure that
    libraries are added via the LIBADD variable instead of LDFLAGS and
    therefore always come after the object files.
    
    Change-Id: I59d114752a0c7664b8678a72082ba5e445497fe5
    Signed-off-by: Tiziano Müller <tiziano.mueller@stepping-stone.ch>
    Reviewed-on: http://review.gluster.org/8331
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d30c3dcf1137a0a94c0be0d0c57de86aadad2a33
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Jul 12 02:15:14 2014 -0700

    fuse: fuse_readlink_cbk() - linkname NULL termination unnecessary
    
    op_ret incremented to compensate for NULL terminating character
    leads to self referential loop where OSXFUSE which would reply
    on a same READLINK() over and over again
    
    ~~~
    [2014-07-12 08:41:29.815473]
       T [fuse-bridge.c:1372:fuse_readlink_cbk] 0-glusterfs-fuse:
                                                  1: /a/b/1 => ../../1
    [2014-07-12 08:41:29.815820]
       T [fuse-bridge.c:1372:fuse_readlink_cbk] 0-glusterfs-fuse:
                                                  0: /a/b/1 => ../../1
    [2014-07-12 08:41:29.816165]
       T [fuse-bridge.c:1372:fuse_readlink_cbk] 0-glusterfs-fuse:
                                                  1: /a/b/1 => ../../1
    ~~~
    
    It happens due to the problem being (op_ret + 1) > strlen(linkname),
    for some odd reason this isn't an issue on Linux where there are odd
    safegaurds on these things - Example of following code
    
    ~~~
    ((char *)linkname)[op_ret] = '\0';
    send_fuse_data (this, finh, (void *)linkname, op_ret + 2048); <---- Here!
    ~~~
    
    This behaves normally with no issue, the reasoning i have is that
    internally 'readlink()' is verified with strlen() again or perhaps the size
    is re-adjusted to the strlen() of `linkname`
    
    This isn't the case on OSX, one needs to make sure that
    ~~~
    strlen(linkname) == op_ret
    ~~~
    Otherwise you would get READLINK() loops as shown above.
    
    This patch fixes the problem.
    
    Many thanks to Anand Avati for helping me out on this.
    
    Change-Id: Ia35818de78a5e4d89bad03ab06e2c5ed6e6753a4
    BUG: 1095525
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8300
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f548db88ad78c24124befef9473792a574f7e157
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Jul 16 15:41:05 2014 -0700

    porting: extattr_remove_fd() doesn't exist
    
    Fix typo extattr_remove_fd() --> extattr_delete_fd()
    
    Change-Id: I0dc3399722eb272d3c04836726e22b212ef15eba
    BUG: 1111774
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8319
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 13f644f78336c79850b332c35ad439fda8dac4fa
Author: Luis Pabon <lpabon@redhat.com>
Date:   Wed Apr 23 16:18:57 2014 -0400

    build: Support for unit tests using Cmockery2
    
    This patch will allow for developers to create unit tests for
    their code.  Documentation has been added to the patch and
    is available here:
    
    doc/hacker-guide/en-US/markdown/unittest.md
    
    Also, unit tests are run when RPM is created.
    
    This patch is a replacement for http://review.gluster.org/#/c/7281
    which removed unit test infrastucture from the repo due to multiple
    conflicts.  Cmockery2 is now available in Fedora and EPEL, and soon
    to be available in Debian and Ubuntu.  For all other operating
    systems, please install from the source:
    
    https://github.com/lpabon/cmockery2
    
    BUG: 1067059
    
    Change-Id: I1b36cb1f56fd10916f9bf535e8ad080a3358289f
    Signed-off-by: Luis Pabón <lpabon@redhat.com>
    Reviewed-on: http://review.gluster.org/7538
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c7f617dfe63fea23693c9ae74b8761349d17a986
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 9 15:03:16 2014 +0530

    features/gfid-access: Print real-gfid in statedump
    
    Change-Id: I1cac8f3ccfcf1fda64ff8470d4f2000d05dcab63
    BUG: 1117733
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8271
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d7c725f4ac8d0c20855f5ca1e4c2dcdddf422057
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Jun 30 07:01:10 2014 -0400

    DHT/mkdir : Fill the stbuf from the subvols on which directory creation
    was successful.
    
    Problem: In case a mkdir sees EEXIST on a non-hashed subvol it reports
    error to the application.
    
    Change-Id: I44b2f32fc1069e609d788b6d25b9366b1460395c
    BUG: 1114557
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/8203
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Anders Blomdell <anders.blomdell@control.lth.se>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 37b82b8abe665f2e6f991aa1aab8d8e1d2a02881
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Jul 16 16:03:00 2014 +0530

    protocol/client: Log ENOENT and ENODATA messages to debug.
    
    Change-Id: I6f8ccf1650ff74e46e5a93a6701d4e694118b273
    BUG: 1120136
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8315
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 74d92e322e3c9f4f70ddfbf9b0e2140922009658
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Jul 15 18:17:19 2014 +0530

    cluster/dht: Fix races to avoid deletion of linkto file
    
    Explanation of Race between rebalance processes:
    https://bugzilla.redhat.com/show_bug.cgi?id=1110694#c4
    
    STATE 1:                          BRICK-1
    only one brick                   Cached File
    in the system
    
    STATE 2:
    Add brick-2                       BRICK-1                BRICK-2
    
    STATE 3:                                       Lookup of File on brick-2
                                                   by this node's rebalance
                                                   will fail because hashed
                                                   file is not created yet.
                                                   So dht_lookup_everywhere is
                                                   about to get called.
    
    STATE 4:                         As part of lookup
                                     link file at brick-2
                                     will be created.
    
    STATE 5:                         getxattr to check that
                                     cached file belongs to
                                     this node is done
    
    STATE 6:
    
                                                dht_lookup_everywhere_cbk detects
                                                the link created by rebalance-1.
                                                It will unlink it.
    
    STATE 7:                        getxattr at the link
                                    file with "pathinfo" key
                                    will be called will fail
                                    as the link file is deleted
                                    by rebalance on node-2
    
    Fix:
    So in the STATE 6, we should avoid the deletion of link file. Every time
    dht_lookup_everywhere gets called, lookup will be performed on all the nodes.
    So to avoid STATE 6, if linkto file is found, it is not deleted until valid
    case is found in dht_lookup_everywhere_done.
    
    Case 1: if linkto file points to cached node, and cached file exists,
            uwind with success.
    
    Case 2: if linkto does not point to current cached node, and cached file
            exists:
            a) Unlink stale link file
            b) Create new link file
    
    Case 3: Only linkto file exists:
            Delete linkto file
    
    Case 4: Only cached file
            Create link file (Handled event without patch)
    
    Case 5: Neither cached nor hashed file is present
            Return with ENOENT (handled even without patch)
    
    Change-Id: Ibf53671410d8d613b8e2e7e5d0ec30fc7dcc0298
    BUG: 1116150
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8231
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 52da727e7564963a8a244fc5cb7028315e458529
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Jul 9 09:31:45 2014 -0400

    DHT/Create : Failing to identify a linkto file in lookup_everywhere_cbk path
    
    In case a file is not found in its cached subvol we proceed with
    dht_lookup_everywhere. But as we dont add the linkto xattr to the
    dictionary, we fail to identify any linkto file encountered.The
    implication being we end up thinking the linkto file as a regular file
    and proceed with the fop.
    
    Change-Id: Iab02dc60e84bb1aeab49182f680c0631c33947e2
    BUG: 1117923
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/8277
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 950f9d8abe714708ca62b86f304e7417127e1132
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jul 8 21:56:04 2014 -0400

    dht: fix rename race
    
    If two clients try to rename the same file at the same time, we
    sometimes end up with *no file at all* in either the old or new
    location.  That's kind of bad.  The culprit seems to be some overly
    aggressive cleanup code.  AFAICT, based on today's study of the code,
    the intent of the changed section is to remove any linkfile we might
    have created before the actual rename.  However, what we're removing
    might not be our extra link.  If we're racing with another client that's
    also doing a rename, it might be the only remaining link to the user's
    data.  The solution, which is good enough to pass this test but almost
    certainly still not complete, is to be more selective about when we do
    this unlink.  Now, we only do it if we know that, at some point, we did
    in fact create the link without error (notably ENOENT on the source or
    EEXIST on the destination) ourselves.
    
    Change-Id: I8d8cce150b6f8b372c9fb813c90be58d69f8eb7b
    BUG: 1117851
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8269
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8896ffd86b1856de17d65874f89a76ad84b6258b
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jul 17 14:17:17 2014 +0530

    glusterd: Correctly reset volinfo->caps during volume create
    
    Change-Id: I012899be08a06d39ea5c9fb98a66acf833d7213f
    BUG: 1120589
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8323
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e291ce0531f3be429f90fc3ba84fa33a2e17b0f6
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Jul 14 09:07:19 2014 -0700

    porting: use __builtin_ffsll() instead of ffsll()
    
    - NetBSD/Darwin doesn't implement ffsll()
    - use Compiler builtin
    
    Change-Id: Iee78b4b81747b0bd3877fd2fcb98746f642ce080
    BUG: 764655
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8308
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Justin Clift <justin@gluster.org>

commit 119109e95268061d9a68c09972302c35a1b22201
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Jun 4 18:40:00 2014 +0530

    libgfapi: Fixed an issue with healing files during glfs_resolve
    
              While resolving any path during the first lookup, libgfapi
              should generate and send gfid as well along with the new inode
              created to the syncop_lookup(..) so that POSIX translator
              can heal the files with missing gfid using the new gfid passed.
    
              This wasn't happening correctly in the current "glfs_resolve_component(..)"
              implementation. Fixed the same.
    
              Also have added the changes from http://review.gluster.org/5337 in
              libgfapi, which is a fix to unlink the inode on revalidate if entry not found.
    
              In addition to the above, have cleaned up a redundant gfapi log mesage.
    
    Change-Id: I0757dda782d16ba6bdbe7ebdbde9c43381229b0a
    BUG: 1116854
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/7976
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1dea949cb60c3814c9206df6ba8dddec8d471a94
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jul 3 17:13:38 2014 +0530

    make snapview-server more compatible with NFS server
    
    * There was no handle based API for listxattr. With this change, glfs_h_getxattrs
      also handles the listxattr functionality by checking whether the name is NULL
      or not (like posix). But all the gfapi functions for listxattr
      (glfs_h_getxattrs AND glfs_listxattr AND glfs_flistxattr) returns the names of
      the xattrs in a buffer provided by the caller. But snapview-server has to
      return the list of xattrs in a dict itself (similar to posix xlator). But
      the buffer just contains the names of the xattrs. So for each xattr, a zero
      byte value is set (i.e. "") into the dict and sent back. Translators which
      do xattr caching (as of now md-cache which caches selinux and acl related
      xattrs) should not cache those xattrs whose value is a zero byte data ("").
      So made changes in md-cache to ignore zero byte values.
    
    * NFS server was not linking the inodes to inode table in readdirp. This was
      leading to applications getting errors. The below set of operations would
      lead to applications getting error
      1) ls -l in one of the snaopshots (snapview-server would generate gfids for
         each entry on the fly and link the inodes associated with those entries)
      2) NFS server upon getting readdirp reply would not link the inodes of the
         entries. But it used to generate filehandles for each entry and associate
         the gfid of that entry with the filehandle and send it as part of the
         reply to nfs client.
      3) NFS client would send the filehandle of one of those entries when some
         activity is done on it.
      4) NFS server would not be able to find the inode for the gfid present in the
         filehandle (as the inode was not linked) and would go for hard resolution
         by sending a lookup on the gfid by creating a new inode.
      5) snapview-client will not able to identify whether the inode is a real inode
         existing in the main volume or a virtual inode existing in the snapshots
         as there would not be any inode context.
      6) Since the gfid upon which lookup is sent is a virtual gfid which is not
         present in the disk, lookup would fail and the application would get an
         error.
    
      To handle above situation, now nfs server also does inode linking in readdirp.
    
    Change-Id: Ibb191408347b6b5f21cff72319ccee619ea77bcd
    BUG: 1115949
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dcc1696045f12127ff37e6312a04c0024c8a4e24
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 15 15:55:34 2014 +0530

    mgmt/glusterd: do not check for snapd handle in restore if uss is disabled
    
    Change-Id: I01afe64685a5794cce9265580c6c5de57a045201
    BUG: 1119582
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8310
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 52ca745fb79d36d7587a7913639520c90a121168
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Jul 14 10:48:01 2014 -0400

    tests: make dd less noisy
    
    Also fixed one case in quota.t where error output is expected.  There
    are probably other similar cases which can be fixed separately.
    
    Change-Id: If80fad0d9fcff6f8ca91d00f4f7b2d5f3fef4256
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8298
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit de359f8b2aa1be9127b6d27a6283c202d089cd81
Author: Anders Blomdell <anders.blomdell@control.lth.se>
Date:   Thu Jul 10 20:17:25 2014 +0200

    Add possibility to run single tests
    
    Change-Id: I9282b711c09611bd0fd4cc814f3ec34aa67d10c0
    BUG: 1118453
    Signed-off-by: Anders Blomdell <anders.blomdell@control.lth.se>
    Reviewed-on: http://review.gluster.org/8291
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fde2b73746e73ea16ba246b8261b552ed2d894dd
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jul 15 09:06:58 2014 +0530

    glusterd: Improvements to peer identification
    
    This patch improves the peer identification mechanism in glusterd and
    lays down the framework for further improvements, including better multi
    network support in glusterd.
    
    This patch mainly does two things,
    1. Extend the peerinfo object to store a list of addresses instead of a
    single hostname as it does now. This also includes changes to make the
    peer update behaviour of 'peer probe' to add to the list.
    
    2. Improve glusterd_friend_find_by_hostname() to perform better matching
    of hostnames. glusterd_friend_find_by_hostname() now does and initial
    quick string compare against all the peer addresses known to glusterd,
    after which it tries a more thorough search using address resolution and
    matching the struc sockaddr's.
    
    The above two changes together improve the peer identification situation
    in glusterd a lot.
    
    More information regarding the problem this patch attempts to resolve
    and the approach chosen can be found at
    http://www.gluster.org/community/documentation/index.php/Features/Better_peer_identification
    
    This commit is a squashed commit of the following changes, the
    development branch of which can be viewed at,
    https://github.com/kshlm/glusterfs/tree/better-peer-identification or,
    https://forge.gluster.org/~kshlm/glusterfs-core/kshlms-glusterfs/commits/better-peer-identification
    
    commit 198f86e60fab74faf082eaa02657a4d8f60b92f0
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 15 14:34:06 2014 +0530
    
        Update gluster.8
    
    commit 35d597f3a6b3248373e727f7b7e889c92554d56c
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 15 09:01:01 2014 +0530
    
        Address review comments
    
        https://review.gluster.org/#/c/8238/3
    
    commit 47b5331e17304477322bd2daed5bbed503c34ca1
    Merge: c71b12c 78128af
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 15 08:41:39 2014 +0530
    
        Merge branch 'master' into better-peer-identification
    
    commit c71b12c164330e8d19d1df4734ab34ef9a8caad2
    Merge: 57bc9de 0f5719a
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jul 10 19:50:19 2014 +0530
    
        Merge branch 'master' into better-peer-identification
    
    commit 57bc9de9e4f49ff2b1620df9906cda50a3527a25
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jul 10 19:49:08 2014 +0530
    
        More fixes to review comments
    
    commit 5482cc363a687a9e246a0780ec88acd53e218501
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jul 10 18:36:40 2014 +0530
    
        Code refactoring in peer-utils based on review comments
    
        https://review.gluster.org/#/c/8238/2/xlators/mgmt/glusterd/src/glusterd-peer-utils.c
    
    commit 89b22c34757178f64d5fbaffa31e6302f841c060
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jul 10 12:30:00 2014 +0530
    
        Hostnames in peer status
    
    commit 63ebf9485cf50d736cf640238a1ab241671fcaf1
    Merge: c8c8fdd f5f9721
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jul 10 12:06:33 2014 +0530
    
        Merge remote-tracking branch 'origin/master' into better-peer-identification
    
    commit c8c8fdd2104b5b6b8a1af739b1dd952b74e6dd66
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Wed Jul 9 18:35:27 2014 +0530
    
        Hostnames in xml output
    
    commit 732a92a0167ad7b1d70edbc35ebd8307c2766ae1
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Wed Jul 9 15:12:10 2014 +0530
    
        Add hostnames to cli rsp dict during list-friends
    
    commit fcf43e3e317508f0c225024738a988a4af8e9205
    Merge: c0e2624 72d96e2
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Wed Jul 9 12:53:03 2014 +0530
    
        Merge branch 'master' into better-peer-identification
    
    commit c0e262416728a3c536a8347a216e471eb2251535
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jul 7 16:11:19 2014 +0530
    
        Use list_for_each_entry_safe when cleaning peer hostnames
    
    commit 6132e60224eb592f3657e535a12a3e72c772da42
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jul 7 15:52:19 2014 +0530
    
        Fix crash in gd_add_friend_to_dict
    
    commit 88ffa9a508fd5aac0b2a76e6e76487ce0cab786a
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jul 7 13:19:44 2014 +0530
    
        gd_peerinfo_destroy -> glusterd_peerinfo_destroy
    
    commit 4b36930a715b1e13cd1a77d136ef1cf78a06d574
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jul 7 12:50:12 2014 +0530
    
        More refactoring
    
    commit ee559b081d608c6501c10ae22166f26eeb65690e
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jul 7 12:14:40 2014 +0530
    
        Major refactoring of code based on review comments at
        https://review.gluster.org/#/c/8238/1/xlators/mgmt/glusterd/src/glusterd-peer-utils.h
    
    commit e96dbc7bbb05fad2a9c424de41a394b8023fe48d
    Merge: 2613d1d 83c09b7
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jul 7 09:47:05 2014 +0530
    
        Merge remote-tracking branch 'origin/master' into better-peer-identification
    
    commit 2613d1daebff0c56812de821c06ed4c16bb9d447
    Merge: b242cf6 9a50211
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 15:28:57 2014 +0530
    
        Merge remote-tracking branch 'origin/master' into better-peer-identification
    
    commit b242cf66d95dd3dd5e3975aa430baa6bd74b8a29
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 15:08:18 2014 +0530
    
        Fix a silly mistake, if (ctx->req) => if (ctx->req == NULL)
    
    commit c835ed26433830ceed57289143f596cf60421558
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 14:58:23 2014 +0530
    
        Fix reverse probe.
    
    commit 9ede17f9329b854b02e8ad159f173244789fd08c
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 13:31:32 2014 +0530
    
        Fix friend import for existing peers
    
    commit 891bf74c7350064dfb008d1b7294bcec28d680fd
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 13:08:36 2014 +0530
    
        Set first hostname in peerinfo->hostnames to peerinfo->hostname
    
    commit 9421d6a217381a7427a7d84f369280883ca4297a
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 12:21:40 2014 +0530
    
        Fix gf_asprintf return val check in glusterd_store_peer_write
    
    commit defac978c1d94011ce8195e311839b9ffce057e7
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 11:16:13 2014 +0530
    
        Fix store_retrieve_peers to correctly cleanup.
    
    commit 00a799f5de1121b0cb7421da8285f9407063e1bd
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 10:52:11 2014 +0530
    
        Update address list in glusterd_probe_cbk only when needed.
    
    commit 7a628e8a9c562d85709c69cfa13fb1774c521b75
    Merge: d191985 dc46d5e
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri Jul 4 09:24:12 2014 +0530
    
        Merge remote-tracking branch 'origin/master' into better-peer-identification
    
    commit d1919858e6639d2b54d716a61f662d9752ec5ff1
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 1 18:59:49 2014 +0530
    
        gf_compare_addrinfo -> gf_compare_sockaddr
    
    commit 31d8ef730d408f8d9ba8f504fa648f7dcd59da87
    Merge: 93bbede 86ee233
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 1 18:16:13 2014 +0530
    
        Merge remote-tracking branch 'origin/master' into better-peer-identification
    
    commit 93bbedeac5181e29f59b2acd08f638146812ec41
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 1 18:15:16 2014 +0530
    
        Improve glusterd_friend_find_by_hostname
    
        glusterd_friend_find_by_hostname will now do an initial quick search for
        the peerinfo performing string comparisions on the given host string. It
        follows it with a more thorough match, by resolving the addresses and
        comparing addrinfos instead of strings.
    
    commit 2542cdbc45aa9cfcaf1f174686158d5565cdd07b
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 1 17:21:10 2014 +0530
    
        New utility gf_compare_addrinfo
    
    commit 338676e8389a44bd91136eebd110197429c2566c
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 1 14:55:56 2014 +0530
    
        Use gd_peer_has_address instead of strcmp
    
    commit 28d45be51f594328741c44455bd80ac9d64ca501
    Merge: 728266e 991dd5e
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 1 14:54:40 2014 +0530
    
        Merge branch 'master' into better-peer-identification
    
    commit 728266eb16d5f5a4bf36266044425ae164337f99
    Merge: 7d9b87b 2417de9
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue Jul 1 09:55:13 2014 +0530
    
        Merge remote-tracking branch 'origin/master' into better-peer-identification
    
    commit 7d9b87b84955ec17daeaf88a3e7462914039430f
    Merge: b890625 e02275c
    Author: Kaushal M <kshlmster@gmail.com>
    Date:   Tue Jul 1 08:41:40 2014 +0530
    
        Merge pull request #4 from vpshastry/better-peer-identification
    
        Better peer identification
    
    commit e02275c52fb83c72ad082c098fd3e432c2b9c526
    Merge: 75ee90d b890625
    Author: Varun Shastry <vshastry@redhat.com>
    Date:   Mon Jun 30 16:44:29 2014 +0530
    
        Merge branch 'better-peer-identification' of https://github.com/kshlm/glusterfs into better-peer-identification-kaushal-github
    
    commit 75ee90d2f272e49b94d24c9ca4571e89a83055ff
    Author: Varun Shastry <vshastry@redhat.com>
    Date:   Mon Jun 30 15:36:10 2014 +0530
    
        glusterd: add to the list if the probed uuid pre-exists
    
        Signed-off-by: Varun Shastry <vshastry@redhat.com>
    
    commit b890625d8164c660695daef3285c67979eef723e
    Merge: 04c5d60 187a7a9
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jun 30 11:44:13 2014 +0530
    
        Merge remote-tracking branch 'origin/master' into better-peer-identification
    
    commit 04c5d60cb938c8d94b214689580b40abb1b0ffcd
    Merge: 3a5bfa1 e01edb6
    Author: Kaushal M <kshlmster@gmail.com>
    Date:   Sat Jun 28 19:23:33 2014 +0530
    
        Merge pull request #3 from vpshastry/better-peer-identification
    
        glusterd: search through the list of hostnames in the peerinfo
    
    commit 0c64f3346a977f9165ac55a84a1e03c40a7573a7
    Merge: e01edb6 3a5bfa1
    Author: Varun Shastry <vshastry@redhat.com>
    Date:   Sat Jun 28 10:43:29 2014 +0530
    
        Merge branch 'better-peer-identification' of https://github.com/kshlm/glusterfs into better-peer-identification-kaushal-github
    
    commit e01edb63153a1008db70b8fa76ae5b535e099326
    Author: Varun Shastry <vshastry@redhat.com>
    Date:   Fri Jun 27 12:29:36 2014 +0530
    
        glusterd: search through the list of hostnames in the peerinfo
    
        Signed-off-by: Varun Shastry <vshastry@redhat.com>
    
    commit 3a5bfa15855e660db2bfde644727371dd2d618cc
    Merge: cda6d31 371ea35
    Author: Kaushal M <kshlmster@gmail.com>
    Date:   Fri Jun 27 11:31:17 2014 +0530
    
        Merge pull request #1 from vpshastry/better-peer-identification
    
        glusterd: Add hostname to list instead of replaceing upon update
    
    commit 371ea354f198b4182382d5403c5960c0b2add6b6
    Author: Varun Shastry <vshastry@redhat.com>
    Date:   Fri Jun 27 11:24:54 2014 +0530
    
        glusterd: Add hostname to list instead of replaceing upon update
    
        Signed-off-by: Varun Shastry <vshastry@redhat.com>
    
    commit cda6d3152886623ecbf46baf0048ebe0119b30b6
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jun 26 19:52:52 2014 +0530
    
        Import address lists
    
    commit 6649b54aa0440130c08e827e0a1d1bbfb840eca9
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jun 26 19:15:37 2014 +0530
    
        Implement export address list
    
    commit 55990034eead92bc9b936240029e460a4bf152d5
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jun 26 18:11:59 2014 +0530
    
        Use first address in list to when setting up the peer RPC.
    
    commit a35fde8d19b9988eb04c652fb3a5e4f84d90ad00
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jun 26 18:03:04 2014 +0530
    
        Properly free addresses on glusterd_peer_destroy
    
    commit 1988081db09ac9205f3dc7268cef8be267f3ce8b
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Thu Jun 26 17:52:35 2014 +0530
    
        Restore peerinfo with address list implemented.
    
    commit 66f524d5749a12f4910dd6b06c9d91f37e1d831e
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon Jun 23 13:02:23 2014 +0530
    
        Move out all peer related utilities from glusterd-utils to glusterd-peer-utils
    
    commit 14a2a326a4dff11b55490dca2a14f39320931340
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Tue May 27 12:16:41 2014 +0530
    
        Compilation fix
    
    commit c59cd351d0a102d0d5f3ea9001fd33c4edcb262f
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Mon May 5 12:51:11 2014 +0530
    
        Add store support for hostname list
    
    commit b70325f0beb884ad12645ef40185f0bf6cedd741
    Author: Kaushal M <kaushal@redhat.com>
    Date:   Fri May 2 15:58:07 2014 +0530
    
        Add a hostnames list to glusterd_peerinfo_t
    
        glusterd_peerinfo_new will now init this list and add the given hostname
        as the lists first member.
    
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Change-Id: Ief3c5d6d6f16571ee2fab0a45e638b9d6506a06e
    BUG: 1119547
    Reviewed-on: http://review.gluster.org/8238
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit c74ff569ca40c7484c197d23ec342f8445c09b9c
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Wed Jul 9 01:22:54 2014 +0530

    compress: Change variable name
    
    'writen' and 'total_writen' variables has been defined in compress
    xlator. This patch replaced those with proper name.
    
    Change-Id: If8e38fae8f997a92686a891d64cbaf6b0b69129a
    BUG: 1075417
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8268
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 78128afce1b6476b3f23e4ca74d654934ac1ca2f
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Feb 25 17:28:10 2014 +0530

    cli: Changed "rebalance start" output
    
    Change-Id: Ie87f1a2107b07a6e519ed894a74edf3b3e0a8340
    BUG: 1063230
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/6946
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f924f8e28b2d4753e4c4bc89a83d4ab330205de2
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Jul 7 14:36:18 2014 +0530

    glusterd: Fix for resource leak coverity bug 1223045.
    
    Change-Id: I96261e7f5cd7b5550d3100750c80190dd932a8ab
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/8252
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit fc84c5af7b5515673f51a47f671738914c7c3530
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Thu May 29 11:04:56 2014 +0530

    gfapi : remove gfapi.py to avoid confusion
    
    python binding of libgfapi is evolving via libgfapi-python
    project. The example available here confuses end users,
    so removing it from this path.
    
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Bug Id: 1119328
    > Reviewed-on: http://review.gluster.org/7920
    > Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    > Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    > Reviewed-by: Thiago da Silva <thiago@redhat.com>
    > Reviewed-by: Prashanth Pai <ppai@redhat.com>
    > Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    
    Change-Id: I17b3aa0f0505342496019ce012cca21d84184027
    Reviewed-on: http://review.gluster.org/8237
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7c74e9c24a06c7ae8f29c4980ea8bffecb01a2c9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 8 16:42:02 2014 +0530

    cluster/afr: Fix dirent leak
    
    afr does itransform by taking the list of entries given by client xlator
    to separate list but doesn't free that list.
    
    Change-Id: Ibb4d38b4934b2bb924385c88f9d7942fad933cb9
    BUG: 1117243
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8261
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit 8d8abc19b0500b725f92164c096b64b3c37cd6b0
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Thu Jun 19 16:51:57 2014 +0530

    Autoload fuse module in centos5/el5 versions.
    
    This patch dynamically load 'fuse' module with the installation
    of glusterfs-fuse package in centos/el5 distributions.
    
    Change-Id: I4988a025bd18716fd6d355431196540e140224b3
    BUG: 1108669
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8116
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 25ceba47ffefa8cf9639c4f7ef907d0f2974f7d3
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Wed Jul 9 01:14:58 2014 +0530

    changelog: variable 'writen' is changed
    
    This patch change the variable name to 'written' in changelog, along
    with few other typo fixing.
    
    Change-Id: I1d3cbea5c89fc0a15233bb6e61b4fbd4bfdd3a67
    BUG: 1075417
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/8267
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 23ae9f3ad79d2d83447096d8b3627491b2e74bb8
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 9 18:36:18 2014 +0530

    test: utility to create files with a specific gfid
    
    python test utility that uses setxattr() interface to
    create files with a predefined gfid (which is also used
    by geo-replication). this utility aids in writing test
    cases for gfid-access translator.
    
    Change-Id: Ib11248844a094cc02dae74d969f2e9212f94ede4
    BUG: 1111490
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8275
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 210a59e48a52515615e440e2a6e1b650063c370b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Jul 10 05:45:52 2014 +0200

    Regression test portability: dd usage
    
    NetBSD, FreeBSD, and MacOS X dd(1) bs argument uses m for megabyte, while
    Linux uses M. Use bs=1024k instead of bs=1M for better compatibility.
    
    BUG: 764655
    Change-Id: I603f57adbc9b31f6d634b918726437fbfce42e03
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/8278
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f637f2f101b13388187f8a6852d3ae6f1d9c2ad5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 14 12:49:58 2014 +0530

    protocol/server: Add extra space between words
    
    Change-Id: Id658db992a43202602e0c30d2c8ca639c4aeadd6
    BUG: 1119167
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8304
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit eeab758c7c7e7670f86fc1d8c3785a1ecb7208b4
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jul 8 13:05:15 2014 +0530

    features/gfid-access: error handling for entry creation
    
    Proceed with setattr() only on a successfull entry creation.
    Winding a setattr() using a freshlyOC initiated inode would
    most likely fail in one translator or the other (e.g. DHT
    expecting the layout information to be set in the inode
    context), which is the case if the inode was not looked up.
    
    Therefore, gfid-access handles failure entry creations and
    passes the _correct_ errno back to the client instead of
    continuing with setattr() call and probably returning back
    incorrect errno. Also, filling up inode->gfid is required
    as the new inode is not looked up and ->gfid would be
    certainely required for inode operations.
    
    Change-Id: Ie92f5647a89bf558c07710ab0400bce69d59fc31
    BUG: 1111490
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8260
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 23455c034a95df2be900f0f83515f2a22c5dea8e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jul 9 09:40:42 2014 +0000

    glusterd/snapshot: Update fstype for local bricks only
    
    While creating snapshot, update fstype for local bricks only
    and not for bricks hosted on other nodes
    
    Also returning ret as 0, in case no cleanup is required in
    post-validation, so that a post-validation failure is not
    logged, every time a pre-validation failure happens.
    
    Change-Id: I6364e33cfd9528e0a988ee48f3443239ee884336
    BUG: 1111060
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8272
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 656e6b38189d14c440a46d4d69b5ddfc5d8cfffc
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon May 5 13:37:34 2014 +0530

    cli/snapshot: provide --xml support for all snapshot command
    
    Now --xml option can be used with all snapshot command. It
    will form the cli output in xml form.
    
    Change-Id: Ifc0ac31d2a9f91e136e87f3b51a629df7dba94e8
    BUG: 1096610
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/7663
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 99685f18f190a73f2a46478cac0b09f4c59834b1
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jun 17 13:42:45 2014 +0000

    dht: support heterogeneous brick sizes
    
    Calculation of layouts now considers the size of each brick, so that
    smaller bricks don't get an "unfair" share of allocations and start
    returning ENOSPC while the larger bricks still have plenty of space.
    
    The observation has been made that some clients might get ENOTCONN when
    trying to fetch disk-size information, and end up calculating layouts
    differently.  The following meta-observations can be made.
    
    (1) This scenario is extremely unlikely in configurations with AFR.
    
    (2) The most likely consequence of this scenario is that some files will
    be placed sub-optimally by the client with the obsolete (non-weighted)
    layout.  They'll still be found anyway, so this isn't a show stopper.
    
    (3) Without this patch it's *guaranteed* that some files will be placed
    sub-optimally, because any layout that fails to account for brick sizes
    is sub-optimal.
    
    (4) We shouldn't be doing fix-layout from two nodes simultaneously
    anyway.  That's inefficient at best.  Any instances of such behavior are
    separate bugs, which should be fixed separately.
    
    (5) In the most extreme edge case, two nodes doing weighted and
    non-weighted layout fixes could race and end up creating an internally
    inconsistent layout.  This condition is still transient; it will be
    detected and repaired automatically the next time anyone fetches the
    layout.  (If it's not that's also a preexisting bug that can show up in
    other contexts.)
    
    In conclusion, it's not the purpose of this patch to fix bugs elsewhere
    in DHT.  Its purpose is to make life incrementally better for users who
    add new hardware with larger disks etc. than the older equipment.  It's
    only one part of an ongoing process to improve layout management and
    repair, all the way up to support for multiple hash rings or tiering.
    
    Change-Id: I05eb6f9eface9cdaf8622e0260c8c7f29020447f
    BUG: 1114680
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8093
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d5ec66032ff96d7d417b5838a6bd1a047d52204c
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Mon Jul 7 16:17:05 2014 +0530

    DHT/Logging
    Changed the log level of a message from none to debug as none does
    not print a log level in the log file.
    
    Change-Id: I463d1095d69bbd0036958282da13cb8e0226f34f
    BUG: 1116797
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8253
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1392da3e237d8ea080573909015916e3544a6d2c
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu May 15 10:35:14 2014 +0200

    cli/glusterd: Added support for dispersed volumes
    
    Two new options have been added to the 'create' command of the cli
    interface:
    
        disperse [<count>] redundancy <count>
    
    Both are optional. A dispersed volume is created by specifying, at
    least, one of them. If 'disperse' is missing or it's present but
    '<count>' does not, the number of bricks enumerated in the command
    line is taken as the disperse count.
    
    If 'redundancy' is missing, the lowest optimal value is assumed. A
    configuration is considered optimal (for most workloads) when the
    disperse count - redundancy count is a power of 2. If the resulting
    redundancy is 1, the volume is created normally, but if it's greater
    than 1, a warning is shown to the user and he/she must answer yes/no
    to continue volume creation. If there isn't any optimal value for
    the given number of bricks, a warning is also shown and, if the user
    accepts, a redundancy of 1 is used.
    
    If 'redundancy' is specified and the resulting volume is not optimal,
    another warning is shown to the user.
    
    A distributed-disperse volume can be created using a number of bricks
    multiple of the disperse count.
    
    Change-Id: Iab93efbe78e905cdb91f54f3741599f7ea6645e4
    BUG: 1118629
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/7782
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ad112305a1c7452b13c92238b40ded80361838f3
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Mon May 5 12:57:34 2014 +0200

    cluster/ec: Added erasure code translator
    
    Change-Id: I293917501d5c2ca4cdc6303df30cf0b568cea361
    BUG: 1118629
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/7749
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6b4702897bd56e29db4db06f8cf896f89df1133c
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu Jul 10 10:19:06 2014 +0200

    tests: Fixed spurious failure in bug-887098-gmount-crash.t
    
    This script was trying to see if the mount process died by doing a
    'ps ax' and a grep of the original pid in the results. After that
    the pid of the first line returned by grep was compared to the
    original pid.
    
    This method can lead to false negatives because it's possible that
    the original pid appears in some other part of the 'ps ax' list.
    
    This patch uses get_mount_process_pid() from volume.rc to check if
    the process is still alive.
    
    Change-Id: I0285366e601a146793c47e9c1156a4bb36d6fcb3
    BUG: 1092850
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/8286
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6532a65b56a652622612a6edcd03fff90fbeff0f
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jun 18 23:36:48 2014 +0530

    features/changelog: prevent deadlock on thread cancellation
    
    helper threads (fsync, rollover) wake up periodically and perform
    their respective operation under a lock (crt->lock). These threads
    are also subjected to cancellation under some circumstance such as
    disabling changelog. This is inherently dangerous when funtions
    which are cancellation points for pthread_cancel(3) are used
    in the locked region.
    
    Consider this
    
             pthread_mutex_lock(&mutex);
             {
                    /* ... */
                    ret = fsync (fd);   <-- cancellation point
                    /* ... */
             }
             pthread_mutex_unlock(&mutex);
    
    A pthread_cancel(3) by another thread just before fsync(3) but
    after pthread_mutex_lock(3) would result in the thread getting
    cancelled when fsync(3) is invoked, thereby never unlocking the
    mutex. Moreover, in case of changelog translator, the locked
    region (under crt->lock in changelog-rt.c) is also the code
    path for fop changelog updation. Therefore, unlocking the
    mutex in thread cleanup handler (pthread_cleanup_pop(3)) might
    prematurely release the mutex during fop updation path.
    
    This patch fixes such problems existing in fsync and rollover
    threads. Fix is to enter the locked region with cancellation
    disabled and enable it after mutex unlock. Also, test for a
    cancellation request early on in case none of the functions
    are cancellation points.
    
    Change-Id: I1795627a12827609c1da659d07fc1457ffa033de
    BUG: 1110917
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8106
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c7251ebfe8e14090f9420786973c5f8232555b8e
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Jul 8 13:06:04 2014 +0530

    glusterd/regression: Temp fix for spurious err
    
    As discussed in the mail,
    Disabling the checking of snap brick status until
    the investigation is done on the port bind issue.
    
    Change-Id: I8854cee050de1b7f843e3d40631b6cb61fd8583e
    BUG: 1112559
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/8259
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b42688786f25420de671ea06030edf4371058433
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jul 3 14:01:20 2014 +0000

    socket/glusterd/client: enable SSL for management
    
    The feature is controlled by presence of the following file:
    
    	/var/lib/glusterd/secure-access
    
    See the comment near the definition of SECURE_ACCESS_FILE in glusterfs.h
    for the rationale.  With this enabled, the following rules apply to
    connections:
    
    	UNIX-domain sockets never have SSL.
    
    	Management-port sockets (both connecting and accepting, in
    	daemons and CLI) have SSL based on presence of the file.
    
    	Other IP sockets have SSL based on the existing client.ssl and
    	server.ssl volume options.
    
    Transport multi-threading is explicitly turned off in glusterd (it would
    otherwise be turned on when SSL is) due to multi-threading issues.
    Tests have been elided to avoid risk of leaving a file which will cause
    all subsequent tests to run with management SSL still enabled.
    
    IMPLEMENTATION NOTE
    The implementation is a bit messy, and consists of two stages.  First we
    decide whether to set the relevant fields in our context structure, based
    on presence of the sentinel file OR a command-line override.  Later we
    decide whether a particular connection should actually use SSL, based on the
    context flags plus what kind of connection we're making[1] and what kind of
    daemon we're in[2].
    
    [1] inbound, outbound to glusterd port, other outbound
    [2] glusterd, glusterfsd, other
    
    TESTING NOTE
    Instead of just running one special test for this feature, the ideal
    would be to run all tests with management SSL enabled.  However, it
    would be inappropriate or premature to set up an optional feature in the
    patch itself.  Therefore, the method of choice is to submit a separate
    patch on top, which modifies "cleanup" in include.rc to recreate the
    secure-access file and associated SSL certificate/key files before each
    test.
    
    Change-Id: I0e04d6d08163893e24ec8c031748c5c447d7f780
    BUG: 1114604
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8094
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0f5719a3598ff4f72cef8b4fe1fcc2587ec39931
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Tue Jul 8 10:03:56 2014 +0530

    Gluster/Doc : Updated admin guide diagrams
    
    Updated the diagrams for the sections on setting up
    distributed replicated volumes and striped replicated volumes
    
    Change-Id: I44ecd2aba75816fdb2f6324c4337cf5fb621ecae
    BUG: 1113842
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8256
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2e831d70c754800919f479f182ffb00562da5219
Author: Meghana Madhusudhan <mmadhusu@redhat.com>
Date:   Sun Jul 6 17:30:50 2014 +0530

    Changing the position of nfs-ganesha.log
    
    Changing the position of ganesha.log from /tmp/ganesha.log
    to /var/log/nfs-ganesha/ganesha.nfsd.log
    
    Change-Id: Iff95fbc7fc690f4fdbc1789d84f3e41aaca9045b
    BUG: 1116723
    Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/8249
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f5f972189b05515eaee9df2aa5afab6165887120
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jun 30 21:50:14 2014 +0000

    libgfapi: succeed lookup of "/.."
    
    For the root dir, ".." should resolve to itself.
    
    i.e. when
            glfs_h_lookupat (fs, NULL, "/..", &stat)
    (or)
            glfs_h_lookupat (fs, root, "..", &stat)
    
    is performed, stat must contain root dir's information.
    
    Change-Id: I1c92091cdc4ff00e6b17e5fa349009c6dfc441c1
    BUG: 1114814
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8207
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit c690c1131288914d0081b817a5ae5ba51e051229
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 8 21:57:09 2014 +0530

    tests: Print EXPECT style error messages rather than 'not ok'
    
    Change-Id: Ib23426c5ede0ab71387a6a112b313aa448b872cd
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8263
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b9f1d1a120b4469d51d2a96eecc7ce83516593ba
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Jul 8 08:18:27 2014 +0530

    rpc: Do not reset @ping_started to 0 in ping callback
    
    This is to avoid indefinite recursion of the following kind, that could
    lead to a stack overflow:
    
    rpc_clnt_start_ping() -> rpc_clnt_ping() -> rpc_clnt_submit() ->
    rpc_clnt_start_ping() -> rpc_clnt_ping() -> rpc_clnt_submit() ...
    and so on,
    
    since it is possible that before rpc_clnt_start_ping() is called a
    second time by the thread executing this codepath, the response to
    previous ping request could ALWAYS come by and cause epoll thread to
    reset conn->ping_started to 0.
    
    This patch also fixes the issue of excessive ping traffic, which was
    due to the client sending one ping rpc for every fop in the worst case.
    
    Also removed dead code in glusterd.
    
    Change-Id: I7c5e6ae3b1c9d23407c0a12a319bdcb43ba7a359
    BUG: 1116243
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8257
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 82e0fb290db880323613a3791acd33f96d421363
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Jul 5 12:19:28 2014 +0530

    client_t: Fix memory leaks
    
    - Assign frame->root->client so that gf_client_unref happens
      in server_connection_cleanup_flush_cbk
    - Avoid taking extra ref in gf_client_get
    
    TODO:
    The whole reason why there are two types of refs
    bind, ref-count is to avoid lock inside lock which
    is not the case now. I will be sending one more patch
    which will accomplish that as well as changing the
    tablearray to list
    
    Change-Id: Ic9971cf248c5ee2cdbfdef8e9ff6d54e3ec60ced
    BUG: 1116672
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8247
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 56c7b07c746ba7ae86117f19bbf304e1150184fb
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 20 12:59:43 2014 +0530

    geo-rep: Avoid duplicate stat in xsync changelog processing
    
    When A file/dir is identified for metadata sync, it was doing
    duplicate stat to get the metadata to sync.
    
    With this patch it avoids doing one additional stat call. Xsync
    performance will improve.
    
    rsync will copy files metadata, so no need to include for
    processing.
    
    BUG: 1111490
    
    Change-Id: I79dad6375fa4742d9aaca7d9856993c184a744dc
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8124
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 72d96e27b3a8cb990c00422289b42e9b90c44b18
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed May 28 18:36:34 2014 +0200

    tests/rpm.t: delete the working directory in case it exists
    
    Change-Id: Iea15d296e22a36b119f04aff61a975811054c20b
    BUG: 1092850
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7916
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ec74ceedaa41047b88d270c00eeb071b73e19664
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jul 5 11:44:30 2014 +0200

    nfs: prevent assertion error with MOUNT over UDP
    
    The MOUNT service over UDP runs in a separate thread. This thread does
    not have the correct *THIS xlator set. *THIS points to the global (base)
    xlator structure, but GF_CALLOC() requires it to be the NFS-xlator so
    that assertions can get validated correctly.
    
    This is solved by passing the NFS-xlator to the pthread function, and
    setting the *THIS pointer explicitly in the new thread.
    
    It seems that on occasion (needs further investigation) MOUNT over UDP
    does not unregister itself. There can also be issues when the kernel NLM
    implementation has been registered at portmap/rpcbind, so adding some
    unregister procedures in the cleanup of the test-cases.
    
    Change-Id: I3be5a420fc800bbcc14198d0b6faf4cf2c7300b1
    BUG: 1116503
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8241
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d6cc24f748c2287d7607de355ef236132c169a15
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Jun 28 04:40:05 2014 +0530

    Changes in statedump for stack, frame, locks
    
    Internal call-stacks don't have lk-owner so it is a bit
    difficult to confirm if a stack hung by comparing two
    statedump files. This change prints call-stack, frame's
    address. This should solve the comparison problem.
    
    Lock times and log times don't have same timezone because
    of which one has to manually convert the times for debugging
    the issues. This change prints blocked, granted times also
    in UTC.
    
    Also fixed line truncation issue when client-unique-string
    is big.
    
    Change-Id: I116372c0d63476823a36ca6dbfba91648f9234cc
    BUG: 1114188
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8197
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2c5eb5c708134218bf756cffeb5167bd03499028
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Jul 5 07:09:00 2014 +0530

    statedump: Don't print mem-type numbers
    
    Change-Id: I381bfa9535fe60c37758761d34b98dbbc4e5f569
    BUG: 1114188
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8239
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Justin Clift <justin@gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8202705f98d139ef7d691587b9f68cf1db2e397a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jul 3 06:50:56 2014 +0530

    features/gfid-access: Fix entry operations
    
    Problem:
    When more than one aux-mounts are performing rmdir .gfid/<pargfid>/dir
    simultaneously, then sometimes a hang is observed.  In gfid-access xlator When
    virtual parent/inode are replaced with real parent/inode in loc, virtual
    pargfid/gfid are not replaced with real pargfid/gfid respectively. Afr is using
    parent_loc->gfids to order the entry locks. But parent_loc->gfid contains
    random/virtual gfid generated by gfid-access xlator. Entrylk in client xlator
    is using loc->inod->gfid for sending entrylk which has 'real' gfid. Because the
    ordering is happening based on random gfids, One mount orders the locks as (L1,
    L2) where as the other orders them as (L2, L1) leading to a dead-lock thus
    a hang.
    
    Fix:
    Replace virtual pargfid/gfid with real pargfid/gfid when virtual-inodes are
    replaced with real-inodes in loc.
    
    BUG: 1114501
    Change-Id: Ie94e816122ef9e7aad51605adbf49291de60827e
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8204
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 83c09b75a8fbc3a46fc0e76f805e061e949678f1
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jul 3 13:27:13 2014 +0000

    socket: add certificate-depth and cipher-list options for SSL
    
    Change-Id: I82757f8461807301a4a4f28c4f5bf7f0ee315113
    BUG: 1114604
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/8040
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9a50211cdb3d6decac140a31a035bd6e145f5f2f
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Jun 30 08:07:36 2014 +0530

    glusterd/snapshot: fixing glusterd quorum during snap operation
    
    During a snapshot operation, glusterd quorum will be checked only
    on transaction peers, which are selected in the begin of the
    operation, and not on the entire peer list which is susceptible
    for change for any peer attach operation.
    
    Change-Id: I089e3262cb45bc1ea4a3cef48408a9039d3fbdb9
    BUG: 1114403
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/8200
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit dc46d5e84f88c5cc869b78ba9db32ed4035b9121
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Jul 3 19:46:59 2014 +0530

    cluster/dht: Added logging of new layout for dir-selfheal
    
    Added a log which logs the new layout which will be used
    for the directory self healing
    
    It prints:
    
    a) Subvolume name
    b) Error --> Is needed because layout healing depends on
                 the error and having it in log will help in
                 debugging
    c) Start     Starting of the layout range
    d) Stop      Ending of the layout range
    
    Change-Id: I48c9c697716a899165ed29b737362a75c62e09b3
    BUG: 1113066
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8173
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dedef037d64fef59d74b9861562aa7f93857a53e
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue Jul 1 20:25:04 2014 +0530

    glusterd/snapshot: Change file-system uuid to file-system label
    
    Problem: In XFS changing file-system UUID with xfs_admin is causing
    too much delay with large file-system. The time taken by xfs_admin
    tool to change UUID is directly proportional to the size of the file
    system.
    
    Cause: In XFS file-system UUID is stored in file-system superblock.
    Therefore for chaning UUID all the superblock needs to be changed.
    
    Fix: Instead of using file-system UUID use file-system label.
    
    Change-Id: Ifb4c668fb29cfc1c89d9b221abc8d09dc09589ec
    BUG: 1115107
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/8215
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 3df72ddcdb371c441b5535ad802fc59a794e3ac9
Author: Jose Castillo <jcastillo@redhat.com>
Date:   Tue Jul 1 15:51:07 2014 +0200

    Avoid hard-coded x86_64 arch in tests/basic/rpm.t
    
    tests/basic/rpm.t hard-codes x86_64 to pick the build-root for mock, causing
    errors when called from a different architecture. With this patch, we use
    'uname -i' to select the right architecture.
    
    v2: Fixed typo as suggested by Justin Clift.
    
    Change-Id: I07bc2af9317dc315bca460149ea3430071537780
    BUG: 962169
    Signed-off-by: Jose Castillo <jcastillo@redhat.com>
    Reviewed-on: http://review.gluster.org/8214
    Reviewed-by: Vikhyat Umrao <vumrao@redhat.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5723645715ae25c2de1bbdde1cf793e194e69eff
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Jul 1 19:03:52 2014 -0700

    porting: Enable 64bit inode properly on Darwin
    
    Usage of -D__DARWIN_64_BIT_INO_T was wrong, use
    
    -D_DARWIN_USE_64_BIT_INODE instead
    
    Change-Id: I4b532232d0a61fe30f08c41ffeba50fff4ecd79e
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8219
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6718342a2cc853e8e6b268abe802d5bd28eca8c0
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Jul 1 16:08:40 2014 -0700

    porting: Provide fallocate and fremovexattr for OSX
    
    Change-Id: I563216f83edaff6d01a251ef0c1746a14aec700c
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8217
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 1b74cf992986287a510fe3b28a8ee7554e8b0992
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Jun 21 02:00:23 2014 -0700

    porting: Port for FreeBSD rebased from Mike Ma's efforts
    
    - Provides a working Gluster Management Daemon, CLI
    - Provides a working GlusterFS server, GlusterNFS server
    - Provides a working GlusterFS client
    - execinfo port from FreeBSD is moved into ./contrib/libexecinfo
      for ease of portability on NetBSD. (FreeBSD 10 and OSX provide
      execinfo natively)
    - More portability cleanups for Darwin, FreeBSD and NetBSD
    - Provides a new rc script for FreeBSD
    
    Change-Id: I8dff336f97479ca5a7f9b8c6b730051c0f8ac46f
    BUG: 1111774
    Original-Author: Mike Ma <mikemandarine@gmail.com>
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8141
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit e4a3566681acbadfe0f7bd879443116885ada4eb
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 26 16:52:36 2014 -0400

    libglusterfs/client_t: cliententries are never expanded
    
    clienttable->cliententries are never expanded once all the available
    entries have been used.
    
    Also removed a couple chatty log messages.
    
    Change-Id: Iff2d92fe1116cc6c6b72ff3d173aee26e69780ed
    BUG: 1113745
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8184
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa21473f0ef4a38ed2e4ed3487443788f63fae88
Author: Vikhyat Umrao <vumrao@redhat.com>
Date:   Tue Jun 3 19:15:42 2014 +0530

    build: glusterfs.spec.in, adding nfs-utils package dependency for server package
    
    nfs-utils provides rpc.statd and it is a requirement for gluster-nfs
    
    Change-Id: I054b7d6d8fb1efe0fed9c90077a93c4f559c1ef4
    BUG: 1065654
    Reported-by: Satheesaran Sundaramoorthi <sasundar@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Signed-off-by: Vikhyat Umrao <vumrao@redhat.com>
    Reviewed-on: http://review.gluster.org/7966
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ca6980d0828a6e7f38d7638a3b99db5d9be36260
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Fri Jun 20 15:40:46 2014 +0530

    cli: Format the hostname column properly in the 'pool list' o/p
    
    In the pool list output, if the hostname is lengthier, then the indentation was not proper.
    
    Solution:
    1) get the full list of hostnames first (prior to display)
    2) Determine the maximum length of the hostname strings from that
    3) Create an appropriate display padding amount, using the length from (2)
    
    Change-Id: Icc3724975a5e30b02b8e06db709930cbac5e0875
    BUG: 1028871
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/8127
    Tested-by: Justin Clift <justin@gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 0e6cd39d55be3f4397772dcd75b0b59daedc8f55
Author: Sachin Pandit <spandit@redhat.com>
Date:   Wed Jun 25 03:57:42 2014 +0530

    TESTS : replace "umount" with "force_umount" giving 5 retries.
    
    Change-Id: I89dd87b9843273c57843bb28706f284e32debc48
    BUG: 1092850
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8167
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit caa8a4ea50734378e7e19f70b39a837c58e9d229
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Apr 17 23:21:05 2014 +0000

    rpc/auth: allow SSL identity to be used for authorization
    
    Access to a volume is now controlled by the following options, based on
    whether SSL is enabled or not.
    
     * server.ssl-allow: get identity from certificate, no password needed
    
     * auth.allow: get identity and matching password from command line
    
    It is not possible to allow both simultaneously, since the connection
    itself is either using SSL or it isn't.
    
    Change-Id: I5a5be66520f56778563d62f4b3ab35c66cc41ac0
    BUG: 1114604
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/3695
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 831efecf927788f26b630cb82d5d6ff4af411a3d
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Wed May 28 13:56:04 2014 +0530

    glusterd/snapshot : Fix for snap create preval for remote peer err msg
    
    Fix for the snap create prevalidation error collation when remote peer failed.
    
    Change-Id: If9563580eae4d9bc4d4d795f0b434f2c85b94007
    BUG: 1101993
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/7899
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 858b570a0c62d31416f0aee8c385b3118a1fad43
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 26 17:14:39 2014 -0400

    build/glusterfs.spec.in: %post server doesn't wait for old glusterd
    
    'killall glusterd' needs to wait for the old glusterd to exit
    before starting the updated one, otherwise the new process can't
    bind to its socket ports
    
    Change-Id: Ib43c76f232e0ea6f7f8469fb12be7f2b907fb7c8
    BUG: 1113543
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8185
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4e74cbf1da39f8244b5f732b314aab91495b4e29
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 30 20:56:58 2014 +0530

    performance/md-cache: Guard against null dict
    
    BUG: 1114677
    Change-Id: Ica4f4ad97d7d1edc3e48e7f1a6ec70b14acffc66
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8205
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e19dc72102d0afb4a95252f3f828b05455c9aac1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 27 12:46:34 2014 +0200

    Add contact data for the new port maintainers
    
    New port maintainers have been announced. These should be included in
    the MAINTAINERS file. Also include some corrections and add missing status
    tags.
    
    URL: http://supercolony.gluster.org/pipermail/gluster-devel/2014-June/041223.html
    Change-Id: I0729c0ea5fec8a645f18543915c0c0c3fce34329
    BUG: 1040351
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8188
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 86ee23319284e62351488f5c76625f0bb3aaad73
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Jun 26 16:25:59 2014 +0530

    geo-rep: History Change detector method select issue
    
    Geo-rep does history crawl even if change-detector is set
    to xsync.
    
    This patch fixes by taking priority to user configured
    change detector.
    
    BUG: 1113525
    Change-Id: Ic6c34e187c9cb6608c9ef8a010ea07015ba60a80
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8183
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 991dd5e4709296d80358d6d076507635c6b3b1e1
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 1 11:57:19 2014 +0530

    mgmt/glusterd: use the right rpc for snapd while getting pending node rpc
    
    * Also changed the testcase bug-1111041.t to correctly get the snapshot
      daemon's pid
    
    Change-Id: I22c09a1e61f049f21f1886f8baa5ff421af3f8fa
    BUG: 1111041
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8209
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit c6f040524d75011c44dcc9afdfef80c60c78f7f7
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jun 19 15:51:39 2014 +0530

    mgmt/glusterd: display snapd status as part of volume status
    
    * Made changes to save the port used by snapd in the info file for the volume
      i.e. <glusterd-working-directory>/vols/<volname>/info
    
    This is how the gluster volume status of a volume would look like for which the
    uss feature is enabled.
    
    [root@tatooine ~]# gluster volume status vol
    Status of volume: vol
    Gluster process                                         Port    Online  Pid
    ------------------------------------------------------------------------------
    Brick tatooine:/export1/vol                             49155   Y       5041
    Snapshot Daemon on localhost                            49156   Y       5080
    NFS Server on localhost                                 2049    Y       5087
    
    Task Status of Volume vol
    ------------------------------------------------------------------------------
    There are no active volume tasks
    
    Change-Id: I8f3e5d7d764a728497c2a5279a07486317bd7c6d
    BUG: 1111041
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8114
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 2417de9c37d83e36567551dc682bb23f851fd2d7
Author: Kotresh H R <khiremat@redhat.com>
Date:   Sat Jun 28 12:18:52 2014 +0530

    feature/changelog: Fix for missing changelogs at backend.
    
    Problem:
           A few changelog files are missing at the backend
           during snapshot with changelog enabled.
    
    Cause:
           Race between actual rollover and explicit rollover.
    
           Changelog rollover can happen either due to actual
           or the explict rollover due to snapshot. Actual
           rollover is controlled by tuneable called rollover-time.
           The minimum granularity for rollover-time is 1 second
           Explicit rollover is asynchronous in nature and happens
           during snapshot.
    
           Basically, rollover renames the current CHANGELOG file
           to CHANGELOG.TIMESTAMP after rollover-time. Let's assume,
           at time 't1', actual and explicit rollover raced against
           each other and actual rollover won the race renaming the
           CHANGELOG file to CHANGELOG.t1 and opens a new
           CHANGELOG file. An immediate explicit rollover at time
           't1' happened with in the same second to rename
           CHANGELOG file to CHANGELOG.t1 resulting in purging the
           earlier CHANGELOG.t1 file created by actual rollover.
    
    Solution:
           Adding a delay of 1 sec guarantees unique CHANGELOG.TIMESTAMP
           during explicit rollover.
    
    Thanks Venky, for the all the help in root causing the issue.
    
    Change-Id: I8958824e107e16f61be9f09a11d95f8645ecf34d
    BUG: 1109692
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8196
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit fe59c3485406cda02950e20f57d0ecc0cf964546
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 23 12:09:30 2014 +0530

    debug/io-stats: Free conf on init failures
    
    Change-Id: I1d227f7b2b8f8ad8d44df8711654ee885e79cf38
    BUG: 1111557
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8148
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6a6bd449247cfed587922cbc1b6b54a1fa0301ad
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 27 17:52:25 2014 +0530

    geo-rep: Fix the fd leak in worker/agent spawn
    
    worker and agent uses pipe to communicate, if worker dies
    for some reason agent should get EOF and terminate.
    
    Each worker-agent spawning is done in thread, Due to race
    if multiple workers in same node retain the pipe refs of
    other workers. Hence agent will not get EOF even if
    worker dies.
    
    BUG: 1114003
    Change-Id: I36b9709b9392299483606bd3ef1db764fa3f2bff
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8194
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit dd7c7b8a0fe209826f80cd158b80194835d3d155
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 26 07:15:17 2014 +0530

    tests: Trigger dir heal by lookup
    
    Heal full in v2 needs some improvements which Ravi
    is working on. Fixed the script to heal based on lookup
    from mount until then.
    
    Change-Id: I7b5f8a294019d9f8cfc9c2346d7997f31b4c3d7c
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8178
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cfd880b0745be62620299cc49d85c7070767bb6e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 26 11:29:19 2014 +0530

    quotad: Remove dead code
    
    client_t is created by server xlator for managing connection related
    resources. Quotad doesn't do that. So no need to handle anything related
    to it.
    
    Change-Id: I83e6f9e1c57458d60529dc62086bb63642932d49
    BUG: 1113403
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8180
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 13542be377fb6e7d664d36dc654659ebf2ca6051
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 26 12:55:39 2014 +0530

    libglusterfs: Ref root inode only once
    
    Change-Id: I75f309fc1fabb17c392697205b2b5cae6d855e72
    BUG: 1113437
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8182
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 13f942f95505c12d8675902f91a70050be97bf8e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jun 11 10:38:45 2014 +0530

    features/gfid-access: Handle loc modification correctly for virtual dirs
    
    Change-Id: I6e3321534dc2f711519b18e8bffb691ab952a8ba
    BUG: 1112659
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8163
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a39d94589eb626c28ae9b06bcc898ebf00147a59
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jun 27 11:38:57 2014 +0000

    glusterd/snapshot: Correct the mount path check
    
    Before removing a lvm, we check if the lvm is mounted
    on the brick path. If not, we remove the brick path only.
    Correcting this check to support restore cases, where the
    volname is not the non-hyphanated uuid, but the original
    volume's name.
    
    Change-Id: If158f4651d36efa2f94523458faf826230e9c76a
    BUG: 1113975
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8192
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit d78d53e853e43f78c59202f1c2e761d17dad93c5
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Jun 17 17:37:46 2014 +0530

    glusterd : Coverity fix in __server_getspec
    
    spec_fd handle should be closed in all the possible cases
    CID : 1124768
    Change-Id: I28390dc76a646a19258520570acef562b8d6fb1e
    BUG: 789278
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/8091
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a9797607a968a4d54d1f28f44048ec5925721098
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Tue Jun 24 14:19:29 2014 +0530

    glusterd/snapshot: Fixed errmsg and Quorum check in Snapshot Operation
    
    1) Removing the static message "unbarrier brick opfailed" and log
    errors / message in places.
    2) Calling the Snapshot Volume Quorum check if the commit
    is passed, as the check(which checks the sanity of
    glusterds or snapvolume) a successful commit makes more sense.
    
    Change-Id: I7b8f77aa9b2e553893a6ae71bd4b5bbbb60ab8f1
    BUG: 1112559
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/8158
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 187a7a926b6b1b57060046a030a5d9a44000fc4b
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon May 26 17:18:17 2014 +0530

    dht: pass xdata to xlators above.
    
    Change-Id: I96e9feb88443fcd7da40c33c0e8c4e2645b1fcf3
    BUG: 1096047
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/7872
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 39209965366f9bbc1d485532496fc265874c7527
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Jun 24 15:00:59 2014 -0700

    glusterd/snapshot: verify for lvm commands
    
    On non-Linux platforms we need to verify the
    run time availability of LVM specific commands
    and fail accordingly with a message.
    
    Change-Id: Ie1e3870648f01ee129e390e2240c66e0c6249b90
    BUG: 1061685
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8165
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>

commit fc1ae37ea4c353286f9a6f3d3e95041feee6ac7d
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Jun 23 05:11:11 2014 +0530

    glusterd/snapshot : Logging the soft-limit reach warning and
    hard-limit failure.
    
    Change-Id: I5083d30c04c784b7f134b8a919b84c225c25f806
    BUG: 1112085
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8147
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a98c4f8bb0517e961a30acdd3d0dce95aa68b96a
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sun Jun 22 14:35:23 2014 -0700

    tests: attr/xattr.h doesn't exist without libattr-devel fix it
    
    Use sys/xattr.h - glibc provided rather than external libs
    
    Change-Id: Iacf80c1089f11a5a9b46d24e2a62e41fa0c4f5ae
    BUG: 1084422
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8146
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: M S Vishwanath Bhat <vbhat@redhat.com>

commit e93e7d3050544a09785753d56c18f6538423915e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sun Jun 22 15:20:19 2014 +0530

    cluster/stripe: Fix EINVAL errors on quota enabled volumes
    
    Write operations on directories with quota enabled used to fail with
    EINVAL on stripe volumes. This was due to assert failure in
    stripe_lookup(), meant to ensure loc->path is not NULL. However,
    in nameless lookup (in this particular case triggered by quotad, which
    has stripe xlator in its graph), loc->path can be legitimately NULL.
    
    The fix involves removing this check in stripe_lookup().
    
    Change-Id: Ibbd4f68763fdd8a85f29da78b3937cef1ee4fd1e
    BUG: 1100050
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8145
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d3f0de90d0c5166e63f5764d2f21703fd29ce976
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri Jun 6 12:22:04 2014 +0530

    gNFS: Fix multi-homed m/c issue in NFS subdir auth
    
    NFS subdir authentication doesn't correctly handle multi-homed
    (host with multiple NIC having multiple IP addr) OR multi-protocol
    (IPv4 and IPv6) network addresses.
    
    When user/admin sets HOSTNAME in gluster CLI for NFS subdir auth,
    mnt3_verify_auth() routine does not iterate over all the resolved
    n/w addrs returned by getaddrinfo() n/w API. Instead, it just tests
    with the one returned first.
    
    1. Iterate over all the n/w addrs (linked list) returned by getaddrinfo().
    2. Move the n/w mask calculation part to mnt3_export_fill_hostspec()
       instead of doing it in mnt3_verify_auth() i.e. calculating for each
       mount request. It does not change for MOUNT req.
    3. Integrate "subnet support code rpc-auth.addr.<volname>.allow"
       and "NFS subdir auth code" to remove code duplication.
    
    Change-Id: I26b0def52c22cda35ca11766afca3df5fd4360bf
    BUG: 1102293
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/8048
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 5740fd404827a70e6318b6fff5773a9d9234d704
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Jun 23 13:20:07 2014 -0700

    glusterd: Use mkdir_p to create DEFAULT_WORKDIR
    
    On non-Linux platforms FSH(Filesystem Hierarchy Standard)
    is not followed 'create' the default expected directory.
    
    Change-Id: Ia55dc99aa398efb6d2d140985cbc0ae11bdc763c
    BUG: 1111774
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8155
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit f20d0ef8ad7d2f65a9234fc11101830873a9f6ab
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jun 20 08:40:47 2014 -0400

    xlators/mgmt: don't allow glusterd fork bomb (cache the brick inode size)
    
    Was don't leave zombies if required programs aren't installed
    
    Also, the existing if (strcmp (foo, bar) == 0) antipattern leaves me
    underwhelmed -- table driven is better;
    
    I like fully qualified paths to system tools too.
    
    File systems aren't going to change their inode size. Rather than
    fork-and-exec a tool repeatedly, hang on to the answer for subsequent
    use. Even if there are hundreds of volumes the size of a dict to keep
    this in memory is small.
    
    Change-Id: I704a8b1215446488b6e9e051a3e031af21b37adb
    BUG: 1081013
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/8134
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 10c04c617276dbd9af7ae04ae287fe6f75e2f2ae
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jun 23 12:36:17 2014 +0530

    cluster/afr: change message description in afr-messages.h
    
    Changed the description of AFR_MSG_SUBVOL_UP to make it more meaningful.
    
    Change-Id: I30fa13c2e9a280a22d48e777d259d04a3b71deef
    BUG: 1075611
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8149
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit b14a525554f1fce280874f0385fef6771ca93c89
Author: Poornima Gurusiddaiah <pgurusid@redhat.com>
Date:   Thu Jun 19 16:19:23 2014 +0530

    libgfapi: In glfs_*chown, if uid or gid is -1, do not set the corresponding flag.
    
    Change-Id: I23d0caa36c37dd5372f6e1d6a27c7904f4df547b
    BUG: 1111563
    Signed-off-by: Poornima Gurusiddaiah <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/8115
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 83fa1cfe185f05319a0048a63c8c163e4e632cf7
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Jun 21 19:20:46 2014 +0530

    cluster/dht: handle ESTALE appropriately in rmdir codepath.
    
    Till we separated the scenario of a file/directory not existing from
    parent not existing [1], we used to include a subvolume in the layout
    of a directory even if it is not present on that subvolume. This was
    done to allow a lookup racing with mkdir to create correct layout.
    However, there are other scenarios as well where a directory is not
    present. One such situation is trying to create a directory after an
    add-brick. Since there is no guarantee that all the ancestors are
    created after an add-brick (and hence directory cannot be created), the
    newly added brick should not be part of the layout. However, we used to
    consider newly added brick as part of layout (even before we do
    fix-layout of all the ancestors) and this was the root cause of [2].
    With [1], this issue got fixed and hence [2] got fixed too. However,
    [1] is not complete in the sense we didn't modify rmdir codepath
    appropriately. This patch fixes that gap.
    
    [1] http://review.gluster.org/6322
    [2] https://bugzilla.redhat.com/show_bug.cgi?id=1006809
    
    Change-Id: I79ab96bb8abb6f3d90bb6e235a1c465e1be0fd19
    BUG: 1032894
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/8142
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 6ddb67c8f53bdfc5fb0ca2427b6f1a0112c49ecc
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Fri Jun 20 20:01:59 2014 +0530

    glusterd/snapshot: delete temporary folder after snapshot create
    
    snapshot create create temporary folders in /tmp location with
    the name xfsmountXXXXXX. It should be cleaned up after snapshot
    create
    
    Change-Id: Idd0c480c1eee7f0fdeba92ae427510faac0f5234
    BUG: 1111614
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/8138
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit beeb30a4b777c5bbd6ebfd8f2074b99f30122e08
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Fri Jun 20 18:04:33 2014 +0530

    glusterd/snapshot: cli error message corrected
    
    snapshot delete on failure used to give invalid error
    message.
    
    Change-Id: I65d6edf8004c9a1bb91f28fa987b2d1629134013
    BUG: 1111603
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/8137
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8d92734f289ab55910045ba7b92bbef1d0dd123c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 19 13:51:41 2014 +0530

    tests: Change umount with force_umount with 5 retries
    
    Change-Id: I0e2dbdfd34080328dfa6b4eebef0366f2b0fcb04
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8117
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1e4a046828ea11cb4c7738a2a00fb715f84dc1ff
Author: Ravishankar N <root@ravi3.(none)>
Date:   Thu Jun 19 17:41:25 2014 +0000

    cluster/stripe: don't treat ESTALE as failure in lookup
    
    Problem:
    In a stripe volume, symlinks are created only on the first brick via the
    default_symlink() call. During gfid lookup, server sends ESTALE from the other
    bricks, which is treated as error in stripe_lookup_cbk()
    
    Fix:
    Don't treat ESTALE as error in stripe_lookup_cbk()
    
    Change-Id: Ie4ac8f0dfd3e61260161620bdc53665882e7adbd
    BUG: 1111454
    Signed-off-by: Ravishankar N <root@ravi3.(none)>
    Reviewed-on: http://review.gluster.org/8135
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a6620e3840bad41b84c590116183670cb1819667
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Jun 20 15:54:57 2014 +0530

    features/snapview-client: put local back to mempool after unwind
    
    Change-Id: I3a709a835b21edf757ee5a1cd04cd9d1c59201dc
    BUG: 1111552
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8128
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a55a2c5cc207a3050e1a37ccb574cc23a59d7294
Author: Ajeet Jha <ajha@redhat.com>
Date:   Thu Jun 19 17:37:18 2014 +0530

    features/changelog: Fix for history api issue during upgrade
    
    On failure during history changelog availability check, there
    was an attempt to destory attribute (of consume thread) which
    was not initialised.
    
    Change-Id: Ica7a98ee70eb1303303884b01ef76ab71430a351
    BUG: 1111169
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/8118
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit f022af610d85e7b7cc4f63bf0491a738b5a6f082
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 20 16:06:42 2014 +0530

    libglusterfs: Don't allow '-0' as input value for numbers
    
    Problem:
    io-stats tries to init log-buf-size as uint32. All gf_string2u*** functions
    which get the unsigned values from string don't want the string to contain '-'.
    So the GF_OPTION_INIT with '-0' as value fails init in io-stats, but by that
    time 'ret' is already reset to 0. Io-stats ends up returning 0 even when init
    failed. Because of this caller of init thinks initialization is successful when
    it is not. iostat_xlator->private is still NULL.  Because of this when a fop
    tries to access members of io-stat-private structure, it crashes.
    
    Fix:
    I initially thought may be we should fix all gf_string2u*** functions to
    accept '-0'. But all these functions are used only for setting volume options.
    If we accept '-0', gluster volume info shows output as follows:
    
    diagnostics.brick-log-buf-size: -0
    
    This seemed ugly, so I felt it is better to disallow '-0' as valid input for
    numbers.
    
    Also fixed return value in cases of failures in io-stats.
    
    Change-Id: I67ac92853b6d2be70516ad1d07505ffd9f058aa4
    BUG: 1111557
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8129
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0c85a8a125eccbd9cf0028116700d7025429656f
Author: ggarg <ggarg@redhat.com>
Date:   Wed May 28 15:01:16 2014 +0530

    glusterd: Spelling correction in glusterd log message
    
    Change-Id: I062302f97a88c528096a92b8dcb33860067e7c22
    BUG: 1101691
    Correction:  "Received" instead of "Recieved"
    Reviewed-on: http://review.gluster.org/7902
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 85ee12f7c061d7035a6441f5d11d9ebed5e574cf
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Jun 20 07:48:19 2014 -0700

    Revert "gfapi : remove gfapi.py to avoid confusion"
    
    This reverts commit d0547a28f59d80ed572652af3e327b761c4e540f
    
    Change-Id: I79ff562fff33d4ad7ca34c6442eb0e980890965a
    Reviewed-on: http://review.gluster.org/8139
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit eba1fb05791f1424f68998cf2175cad1ce6098de
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 19 05:06:53 2014 +0000

    features/index: Don't delete current xattrop index.
    
    Delete the base entry in indices/xattrop only when it is stale.
    
    Change-Id: I675c1510dd8293d068e31b552b0de48f50aac658
    BUG: 1101647
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8119
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit d0547a28f59d80ed572652af3e327b761c4e540f
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Thu May 29 11:04:56 2014 +0530

    gfapi : remove gfapi.py to avoid confusion
    
    python binding of libgfapi is evolving via libgfapi-python
    project. The example available here confuses end users,
    so removing it from this path.
    
    Change-Id: I90a0a29972f5230b8b440e8941aaca8a62e497a6
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/7920
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Thiago da Silva <thiago@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9d2b7cd3e8161f557390b5b434464362a0ba7a16
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jun 16 19:08:18 2014 +0530

    tests: changes to some of the uss testcases
    
    Made the below changes
    
    tests/basic/uss.t: removed the older way of getting the list of snapshots
    bugs/bug/bug-1109770.t: added uss disable test also to check snapd behavior
    
    Change-Id: I57b6bc8fa82bcaa544f483ad382e1bb4d11ef122
    BUG: 1092850
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8081
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 78e9180ca24f15e1366eb3d51cbb5e4576af91a2
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri Jun 6 03:27:21 2014 +0530

    feautre/gfid-access: Fix EINVAL when stat on .gfid
    
    Problem: Some of the inode operations on '.gfid'
    virtual directory was resulting in the error
    EINVAL from dht after failing to find the layout.
    
    Solution: Inode operations on '.gfid' virtual directory
    should not wind further down and should be handled
    accordingly in the gfid-access translator itself.
    
    Change-Id: I156cb10ffea0c46b0d747e26f74538d7fb01a1dd
    BUG: 1105891
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8011
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 124ba991069099258e4e69ccf3eefae1c88ebb8c
Author: Kotresh H R <khiremat@redhat.com>
Date:   Wed Jun 18 13:30:26 2014 +0530

    feature/geo-rep: Fix to retain pause state of gsyncd on restart
    
    On soft reboot, geo-rep monitor is writing 'faulty' into status
    file. It should not do it if previous state is paused as
    glusterd depend on the state file on node restart.
    
    Change-Id: Idd45abf13350b087371935f1b4f6e1a346433d27
    BUG: 1101410
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8097
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 3fe1a14a82f3894e6b9e9d3004a185c48ea4bf6b
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jun 19 15:21:33 2014 +0530

    glusterd: Check mount_dir for own bricks only during start
    
    During the start volume commit op brickinfo->mount_dir was being checked
    for all bricks by glusterd. This could lead to failures starting the
    volumes which were carried forward on upgrade.
    
    Change-Id: If3d3ee4b2b9f68341ff4422dd90faf32bc3e898f
    BUG: 1111124
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8113
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 2783fbed2a6a8481eadbab8ca5ad03513f7f54f4
Author: Sachin Pandit <spandit@redhat.com>
Date:   Fri Jun 13 08:55:31 2014 +0530

    docs : Admin document updation for snapshot commands.
    
    Change-Id: I8460e7feed7e1b0cf37e735852f5c269adfadd77
    BUG: 1061685
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8060
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 616b0aa44fe78a362f2dca3d066be47555ceb09f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jun 18 22:10:12 2014 +0530

    tests: Provide force_umount with 5 retries
    
    Change-Id: I2b5784c48eedcccb17690de438addd29075926bd
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8104
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f844e5019de872e0c138daa6257d1f6cac5a4aff
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Wed Jun 18 11:06:21 2014 +0530

    Cluster/DHT : Logging changes
    
    Removed trailing spaces from the code
    
    Change-Id: I427c9a01b514824f903e301863c2c29071db6483
    BUG: 1075611
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/8096
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3dccc3da7485059996ad490d4bf9ba23693110f7
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Jun 18 17:55:54 2014 +0530

    features/quota: Fix dict leak
    
    Change-Id: I971a52163c0f1a887bbb8585cd69df2339af51cb
    BUG: 1110777
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/8102
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit b54764ba860c3baba4b441ae7fcf043ab7eb46db
Author: Varun Shastry <vshastry@redhat.com>
Date:   Thu Dec 26 15:30:49 2013 +0530

    features/quota: Make dht_statfs_cbk more fool proof from quota_deem_statfs
    
    Problem:
    The function depends on the fact that if quota-deem-statfs option is enabled,
    all of the subvolumes send their xdata with quota-deem-statfs flag ON. But,
    this may not be true in case of errors in some of the subvolumes.
    
    There is a decision/policy made which assumes quota-deem-statfs to be ON if at
    least ONE of the subvolumes sends the flag ON. By this, df reports quota
    modified statfs values if *at least ONE* of the bricks sends the
    quota-deem-statfs flag ON. This can be visualized with the below "Transition
    Diagram/State Machine".
    
            Event: Each Quota deem statfs status from the individual bricks
            Action: Decision taken on the calculation of the statvfs received
            State: Whether quota deem statfs is ON or OFF (0: OFF, 1: ON)
            Input: Event from individual bricks
    
                  ___                  ___
                 /   \   OFF*         /   \  (OFF|ON)*
                |     |              |     |
                 \   /        ON      \   /
            -----> 0  ----------------> 1
    
    The below Transition Function depicts the relation between the statfs
    calculation based on the events received.
    
             State          Event          action
            -------------------------------------
              OFF            OFF            OFF
              OFF            ON            REPLACE
              ON             OFF           NEGLECT
              ON             ON            COMPARE
    
    Change-Id: I0e8fb7d3945a3ca3dde0bb99de6cd397e27a3162
    BUG: 1048786
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6652
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 2b87e157a50953b542d5fc49fac84813ee116ce5
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jun 18 11:28:05 2014 +0000

    glusterd/snapshot: Updating "global-option-version" in
    /var/lib/glusterd/options
    
    When auto-delete option is set, we should update the
    "global-option-version" in /var/lib/glusterd/options
    to the next version.
    
    Change-Id: Ic561f33531a27cb8cca01d25632511205927268a
    BUG: 1104642
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8099
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 438234fccb41f9621e7506737438d77bc4f0d4f2
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Jun 5 23:09:56 2014 -0700

    snapview/server: warning cleanup after clang complaints
    
    - svs_inode_new()/svs_fd_new() should only need "no" arguments as
      presented
    
    - define variables only with usability :-)
    
    Change-Id: I10a8d189a088701b29f26b6e4913560e32d16e75
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7998
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d0657d2989c1ba50ff76f15223ed9ce6a20a8682
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Jun 13 18:50:44 2014 -0700

    glusterd: Avoid simple inline function definitions with local scope
    
    C99/clang treats simple 'inline' function definitions as external
    scoped functions - this leads to flat_namespace issue on OSX.
    
    Avoid them by making them 'static inline' instead.
    
    Change-Id: I03deb4a72e0ba16e5e21e9739792b777898b67ed
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8067
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b6c8b1b47838228611e1a619890effe8b2dd2ad3
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri May 30 17:03:30 2014 +0530

    feature/geo-rep: Fix for changelog agent becoming zombie.
    
    Monitor process spawns changelog agent and is not
    wait on it, hence becoming zombie. When worker is
    dies/killed, it respawns both worker and corresponding
    agent leaving the earlier changelog agent in zombie
    state. This patch addresses this issue by waiting
    on agent process in montor process.
    
    Change-Id: I571b7d6487133848edca67e7446f1caa70ae01c9
    BUG: 1103643
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7956
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 93832829016a0a51a8938c0c89c6bd09b3229c9f
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Jun 17 15:09:50 2014 +0530

    cluster/dht: Do layout self healing of directory for nameless lookup
    
    Problem: Currently in the  nameless lookup code path, if at the
             end of the lookup, even if it detects that layout
             anamolies are there, layout healing will not be done as
             there is no code to heal it.
             So there can be race between mkdir and lookup.
    
             Assume mkdir is going on from some other mount point,
             Say, M1. Directories are created on some nodes but layout
             is not set yet.
    
             Now from M2, nameless lookup goes, lookup will be success
             full as the directory is present on some of the nodes, but
             it won't heal layout. Now if create goes after lookup fop,
             because layout is absent, file creation will fail.
    
    Fix:     Included the code of layout self-heal in the nameless
             lookup path. At the end of lookup, layout will be computed
             as it would have been in the named lookup, but it will be
             set to those node only, where directory is present.
             So after that if create fop goes, the probabiliy to get the
             subvolume with proper hash-range is high now, so reduces
             the race window.
    
    Other:  Whenever a directory is created, we have to choose a brick
            from which we start allocating layout in a circular fashion.
            To calculate this starting brick, I have changed the candidate
            from name of the directory to gfid of the directory
    
            But to compute where a given file belongs, we will still
            use the name of the file. Hash computed from the name of the
            file should belong to any one of the directory-hash-range
    
            Calculation of hash for a file is acting as a consumer and the
            setting of directory layout based on gfid is acting as a producer,
            which are independent from each other.
    
    Change-Id: I3808c55082cd1b5c72d2c77cbbc063f55aa38bee
    BUG: 1095888
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/7493
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3a499d170de2c7df06b127b709d27c64cef98886
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Jun 17 14:45:44 2014 +0530

    cluster/dht:  Bring option to choose gfid or name based hashing
    
    Change-Id: I11794eb2adceb88e75864aede450e904431a6273
    BUG: 1095888
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8049
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e232b4c674dad697bb520c34fa4c445d0ababfc3
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Sun Jun 1 11:05:51 2014 +0530

    mention use-readdirp option in mount section
    
    Change-Id: I843a8b7713f96dcb5fdb07b8cadc47b4adc0a7b9
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/7939
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d65e8a871aa81ef7d2275da025f66d6e6dabc47c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Nov 15 13:17:42 2013 +0530

    extras: add a script to stop all the glusterfs process
    
    Change-Id: I9f73bf0308625695ed78db06478963d16644852a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/6270
    Reviewed-by: Sachidananda Urs <sacchi@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 53d932b490c505901ddd1a0133e8125ad6dfd24c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jun 16 20:38:42 2014 +0530

    mgmt/glusterd: save the snapd port in volinfo after starting snapd
    
    Change-Id: I9266bbf4f67a2135f9a81b32fe88620be11af6ea
    BUG: 1109889
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8084
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit 84d370774cdbc6847f4f2f64a7f47abb27a7471b
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jun 16 18:56:18 2014 +0530

    glusterd: Use blocking quotad start only on quota enable
    
    Having quotad always being using the blocking runner variant is
    problematic. In some cases where quotad was started from the epoll
    thread, it lead to a deadlock which lead to glusterd becoming
    unresponsive.
    
    This patch makes the default quotad_start function use the non-blocking
    runner_nowait variant. The blocking start is used only when quotad is
    started on quota enable command.
    
    Change-Id: Ib27042748d69ea28e68badcfaddf61589aae4eba
    BUG: 1109872
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8082
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit d3bd3319afb208acfa905696fb0be5545f5883f6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jun 15 08:40:49 2014 +0530

    tests: Avoid sleep
    
    Change-Id: I7169be3532232754b9461c4e1b27bf6bc857f7a6
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8083
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6e33d855815726bd8ebf1c7cdc3cf233ff7ac231
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Jun 16 17:39:08 2014 +0530

    glusterd: Fail peer probe/detach commands when peer detach is ongoing
    
    Change-Id: Ifd8099bc235eb395e8fd9ead3197bef71c78042b
    BUG: 1109812
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/8079
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit de22a20a76f5cf0af3ca2898f0bfd8324a191e0c
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Jun 16 15:39:57 2014 +0530

    cluster/dht:  make loc->inode instead of loc->parent
    
    parent's inode should be taken from loc->inode.
    
    Change-Id: I979b7333efa93b1e8f4c73ccf048d48e308f9289
    BUG: 1104653
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/8073
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7382b66de76101d625ed888ec7b7f82fd7da56d3
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Fri May 30 11:26:40 2014 +0530

    Cluster/DHT: New logging framework
    
    Moved all relevant DHT gf_log calls to the new logging
    framework.
    
    Change-Id: I3af3cfe0416e332774a6c4ff6a091d006c400af2
    BUG: 1075611
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/7929
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0031bd1d18c874f3b68b59df7f84fce354b9b86c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jun 16 16:11:46 2014 +0530

    mgmt/glusterd: volume stop should also stop its snapview-daemon
    
    Change-Id: I702372c6c8341b54710c531662e3fd738cfb5f9a
    BUG: 1109770
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8076
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4f9dff83ad3b91fcb066f26c1085ada002b3bc36
Author: Anand Subramanian <anands@redhat.com>
Date:   Mon Jun 16 07:10:32 2014 +0530

    Minor fixes for correcting the goto statements for frame destroy and checking pthread_mutex_lock return values
    
    * Also some coverity fixes
    
    Signed-off-by: Anand Subramanian <anands@redhat.com>
    
    Change-Id: I0c27b913e62b0a072e508e37a3fb3421a9ca9503
    BUG: 1105439
    Signed-off-by: Anand Subramanian <anands@redhat.com>
    Reviewed-on: http://review.gluster.org/8071
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b8f3aab95f01ac7d590a5ba490e890d9cf8c2e50
Author: Susant Palai <spalai@redhat.com>
Date:   Tue May 13 12:56:17 2014 -0400

    DHT/readdirp: Directory not shown/healed on mount point if exists
                  on single brick(non first up subvolume).
    
    Problem: If snapshot is taken, when mkdir has succeeded only on
    hashed_subvolume, then after restoring snapshot the directory
    is not shown on mount point.
    
    Why:    dht_readdirp takes only those directory entries in to
    account, which are present on first_up_subvolume. Hence, if the
    "hashed subvolume" is not same as first_up_subvolume, it wont be listed
    on mount point and also not healed.
    
    Solution:
    Case 1: (Rebalance not running)If hashed subvolume is NULL or down then
    filter in first_up_subvolume. Other wise the corresponding hashed subvolume
    will take care of the directory entry.
    
    Case 2: If readdirp_optimize option is turned on then read from first_up_subvol
    
    Change-Id: Idaad28f1c9f688dbfb1a8a3ab8b244510c02365e
    BUG: 1092433
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7599
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 62265f40d7201854dbf33d59a74286dda671a129
Author: Kotresh H R <khiremat@redhat.com>
Date:   Mon Jun 16 12:30:39 2014 +0530

    features/changelog: Do not ignore self-heal fops in changelog
    
    Problem: Geo-rep fails to sync some files to slave as the
    changelog entries are missing for those files.
    
    Cause: Fops happened when the active brick is down and
    self- healed later when it came up.
    
    Solution: Capture self-heal fops as well in changelog so
    those entries are not missed.
    
    Change-Id: Ibc288779421b5156dd1695e529aba0b602a530e0
    BUG: 1109692
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8070
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 452eea5c43ee5af450e91f240860551af6aba241
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Jun 9 07:52:37 2014 +0530

    glusterd/snapshot : override postvalidate for few snapshot commands.
    
    snapshot info, list, config display and status does not
    require any operations to be performed during postvalidate stage.
    Hence it is better to override these commands in postvalidate.
    Or else there will be a warning in log message saying "postvalidation
    failed".
    
    Change-Id: I14d64f7bf9adee8821067dd74d5027215d7b02f8
    BUG: 1106406
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8014
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 7342076f420efd62c9c46cdf5454b283225d1ec8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jun 15 16:19:15 2014 +0530

    tests: Validate self-heal daemon completions
    
    Removed sleep with EXPECT_WITHIN
    Heal full doesn't generate indices until the files/dirs are
    recreated. So wait until they are re-created and then
    wait for heal completion.
    
    Change-Id: I82399f6a17f94ecc101db45b83d8ef7bfa9c64dd
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8069
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 47230eb38d96e51d2d5e976eda7ff82c62f6eedd
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Jun 4 12:43:18 2014 +0530

    features/quota: No root squash for quota aux mount by default
    
    With change 28209283a67f13802cc0c1d3df07c676926810a2, the root squash option
    is enabled by default even for the trusted clients. This disallowed quota
    auxiliary mount from setting the limit.
    
    This patch adds the quota aux mount process to list of 'special' clients which
    have the root squash disabled by default.
    
    Change-Id: Ie6583dd3deb170563daf001239c51bcff1ce078b
    BUG: 1104692
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/7967
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit ec845d93e74644bbfe27e0b085a38dbd7c02480f
Author: Anand Subramanian <anands@redhat.com>
Date:   Thu May 15 08:19:14 2014 +0530

    Get snapshot info dynamically via new rpc and infra for snapview-server to refresh snaplist
    
    BUG: 1105439
    Change-Id: I4bb312a53d88f6f4955e69a3ef2b4955ec17f26d
    Signed-off-by: Anand Subramanian <anands@redhat.com>
    Reviewed-on: http://review.gluster.org/8001
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 056b99bfbc181a88579b8139d444f7dd2fa3b19e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jun 15 07:54:02 2014 +0530

    tests: Fix spurious failure for tests/bugs/bug-918437-sh-mtime.t
    
    Change-Id: I355ae02bed54753480279ddb058cc4b19ace6792
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8068
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 72c7afcd091605e06a02e7c5de0eff18f0690a82
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Jun 12 14:18:05 2014 +0530

    dht/rebalance: Do not allow rebalance when gfid mismatch found
    
    Due to race condition, it may so happen that, gfid obtained
    in readdirp and gfid found by lookup are different for a given
    name. in that case do no allow the rebalance.
    
    Readdirp of an entry will bring the gfid, which will be stored
    in the inode through inode_link, and when lookup is done and
    gfid brought by lookup is different from the one stored in the
    inode, client3_3_lookup_cbk will return ESATLE and error will be
    captured by rebalance process.
    
    Change-Id: Iad839177ef9b80c1dd0e87f3406bcf4cb018e6fa
    BUG: 1104653
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/7973
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ced0dcd817d02ce7ea2b69bff94dad26a96efe71
Author: Joe Julian <me@joejulian.name>
Date:   Thu May 22 10:24:22 2014 -0700

    doc: Fix peer probe deficiencies
    
    Added the command to probe the first server to assign it a hostname
    
    Change-Id: I9c25f1ce3175e1ffe024f6b6ae14a4526228489a
    BUG: 1095594
    Reviewed-on: http://review.gluster.org/7852
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2244879873d155ba3647af2d089a6db6fb7d305d
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Tue May 13 10:44:30 2014 +0530

    Modified Gluster man page
    
    Change-Id: I03c910012eca29a7fbca3728827d99b80374ce9c
    BUG: 1097051
    Reviewed-on: http://review.gluster.org/7745
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 12b7797bfb143890ad4ca085332ec2f5e1ed08b8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 12 20:38:34 2014 +0530

    Fix resolution issues across fuse/server/afr
    
    Problems with fuse/server:
    Fuse loc touch up sets loc->name even when pargfid
    is not known. Server lookup does (pargfid, name) based
    lookup when name is set ignoring the gfid. Because of this server
    resolver finds that the lookup came on (null-pargfid, name) and
    fails the lookup with EINVAL.
    
    Fix:
    Don't set loc->name in loc_touchup if the pargfid is not known.
    Did the same even for server-resolver
    
    Problem with afr:
    Lets say there is a directory hierarchy a/b/c/d on the mount and the
    user is cd'ed into the directory. Bring down one of the bricks of replica and
    remove all directories/files to simulate disk replacement on that brick. Now
    this brick is brought back up. Creates on the cd'ed directory fail with ESTALE.
    Basically before sending a create of 'f' inside 'd', fuse sends a lookup to
    make sure the file is not present.  On one of the bricks  'd' is present and
    'f' is not so it sends ENOENT as response. On the new brick 'd' itself is not
    present. So it sends ESTALE. In afr ESTALE is considered to be special errno on
    witnessing which lookup has to fail. And ESTALE is given more priority than
    ENOENT. Due to these reasons lookup fails with ESTALE rather than ENOENT. Since
    lookup didn't fail with ENOENT, 'create' can't be issued so the command is
    failed with ESTALE.
    
    Solution:
    Afr needs to consider ESTALE errno normally and ENOENT needs to
    be given more priority so that operations like create can proceed even when
    only one of the brick is up and running. Whenever client xlator identifies
    that gfid-changed, it sets that information in lookup xdata. Afr uses this
    information to fail the lookup with ESTALE so that top xlator can send
    fresh lookup.
    
    Change-Id: Ica6ce01baef08620154050a635e6f97d51029ef6
    BUG: 1106408
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8015
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7aa3630b1f5e07227e9cd167cbd717bd7932ae78
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jun 13 11:23:29 2014 +0000

    glusterd/snapshot: Update fstype and fsuuid
    
    Update fstype and fsuuid before creating missed snapshot
    
    Change-Id: Ie9af0065fab288bd1c1a26396428f0cee6335f97
    BUG: 1109142
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/8062
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 56438208c8ada12f878e0317c587a3642bf1a3a0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jun 12 12:45:26 2014 +0530

    cleanup: Fix order of arguments passed in log message
    
    Change-Id: Iae85cdfc223875688ea17155fffcf2a3a435d245
    BUG: 764890
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8044
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 053389c89eb1c1937e795dd52f7c10a4a295b707
Author: Justin Clift <justin@gluster.org>
Date:   Fri Jun 13 03:33:51 2014 +0100

    tests: add missing check for yajl to run-tests.sh
    
    Also add it to the regression test Requires line, along with other
    missing dependencies.
    
    Change-Id: I2a83eb6797bafe8883d90565bb4c1ab93c074644
    BUG: 1108958
    Reviewed-on: http://review.gluster.org/8054
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 85055f8a909ed0c5ebb20dd2c1ed34e610c987fe
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Jun 13 12:01:34 2014 +0530

    logging: Flush log messages logged via gf_log_callingfn()
    
    Change-Id: Id1d83a6c5985dd57ef3cf1e3d2f4d04ff2dbabfa
    BUG: 889157
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8058
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 17f366722124cef253822ba3d78c560e766cb242
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Jun 4 15:01:14 2014 +0530

    extras: bash command completion for gluster
    
    Change-Id: Ifd6e68b0288dc65e41e467b4ad02bfc3bded341f
    BUG: 1108767
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/7979
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a41f212e4b5bf74e2752370de10b754a1fa3f675
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jun 12 20:14:33 2014 +0530

    get the path from the loc->path in the lookup instead of resolver doing it
    
    Change-Id: I7448e1199f4fd32fb0ae127b36dcf06641a153a9
    BUG: 1108887
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8053
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a6585d9c5e536818e01f05df8e58c18bbe59e231
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jun 12 15:02:06 2014 +0530

    glusterd: More snapshot backward compatability fixes
    
    Several volume operations, start, add-brick and replace-brick, expected
    the presence of a bricks mount directory, which is required for the
    snapshot feature. This should only be expected when snapshot is
    supported in the cluster.
    
    Change-Id: I92017bb5e069392352f9800cef1ddc80045fda35
    BUG: 1101903
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/8046
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 5b0f65717f0d9489ca1c8750724cf9c8bfa11cbc
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jun 6 12:48:32 2014 +0000

    glusterd/snapshot: Fix snap delete cleanup
    
    During commit the first thing that should happen is the
    snaps should be marked as GD_SNAP_STATUS_DECOMMISSION.
    So that if the node goes down the marked snap can be
    cleaned up when the node is coming back. Also during snap
    handshake while accepting snapshot from peer, we should
    check if the snap in question is decomissioned. In that
    case we shouldn't be accepting the peer data.
    
    Change-Id: Ib4e38d1b6bf49411928623fbc9f72f2b37b72086
    BUG: 1104714
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7996
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 60e8fdfeebb6005d3e3c310c720c2ff5e709f706
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Fri Jun 13 10:49:47 2014 +0530

    glusterd/snapshot: Fix for snapshot restore failure
    
    Problem: If restore fails due to quorum failure then the subsequent restore fails.
    
    Cause: Volume store is backed up during prevalidate failure and it is
    reverted or cleaned based on failure or success of the commit phase.
    In case of quorum failure we were not reverting the backup.
    
    Fix: Take backup when all the validation is done including quorum check.
    
    Change-Id: I55d57f6ee85fac04a0e6cbd0291a402601c725d6
    BUG: 1109024
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/8056
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 10cd2bc38e1f0a1297d59c0791a85ed9d01c93ff
Author: Sachin Pandit <spandit@redhat.com>
Date:   Wed Jun 11 09:03:16 2014 +0530

    glusterd/snapshot : Provide enable/disable option for snapshot auto-delete feature.
    
    This patch provides an interface to enable or disable
    the auto-delete feature.
    Syntax : gluster snapshot config auto-delete <enable/disable>
    
    DETAILS :
    
    1) When auto-delete feature is disabled, If the the soft-limit is
    reached then user is given a warning about exceeding soft-limit
    along with successful snapshot creation message (oldest snapshot is
    not deleted). And upon reaching hard-limit further snapshot creation
    is not allowed.
    
    Example :
    ------------------------------------------------------------------
    |Case - 1: Upon reaching soft-limit
    |
    |Snapshot create : snap successfully created.
    |Warning : soft-limit of volume (vol) is reached. Snapshot creation
    |is not possible once hard-limit is reached.
    |
    |-----------------------------------------------------
    |Case - 2: Upon reaching hard-limit
    |
    |Snapshot create : snap creation failed.
    |Error : hard-limit of volume (vol) is reached, Hence it is not
    |possible to take further snapshots. Please delete few snapshots
    |of the volume (vol) before taking another snapshot.
    ------------------------------------------------------------------
    
    2) When auto-delete feature is enabled, then as soon as the soft-limit
    is reached the oldest snapshot is deleted for every successful snapshot
    creation (same as existing method), With this it is made sure that
    number of snapshot created is not more than snap-max-hard-limit.
    
    Change-Id: Ie3ca64bbd2c763371f541cd2e378314e73b695b4
    BUG: 1105415
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8017
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6ba178fd9ebf9fc98415c30bcd338a68ee5eb601
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jun 3 00:28:08 2014 +0530

    protocol/server: reflect lru limit in inode table also
    
    Upon reconfigure, when lru limit of the inode table is changed,
    the new value was just saved in the private structure of the
    protocol/server xlator and the inode table used to have the older
    values still. A brick start was required for the changes to get
    reflected. To handle it, traverse through the xlator tree and check
    whether a xlator is a bound_xl or not (if it is a bound_xl it would
    have its itable pointer set). If a xlator is a bound_xl, then get
    the inode table of that bound_xl and set its lru limit to new value
    given via cli. Also prune the inode table so that extra inodes are
    purged from the inode table.
    
    Change-Id: I6909be028c116adaa1d1a5108470015b5fc6f09d
    BUG: 1103756
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7957
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 4d656f9008747172db52f6d532b610c487528bfb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 13 11:26:28 2014 +0530

    tests: Fix spurious failure in tests/bugs/bug-830665.t
    
    Problem with script:
    EXPECT_WITHIN fails the test if the command it executes fails.
    There is a possibility that the file script tries to 'cat' may not exist.
    In those cases it would fail leading to spurious failures.
    
    Fix:
    Add a function which returns empty string when the file doesn't exist
    and 'cat' file when it does exist.
    
    Change-Id: I0abfb343f2fce1034ee4b5b680e3783c4f6e8486
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8057
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 333d2a60eb121a4f09a0c3c0d35d8585af86bdd1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 13 08:42:25 2014 +0530

    tests: Revert janitor link file removal test
    
    I found that order of execution in afr-v2 self-heal is causing
    the links to disappear some times. I need to fix that issue
    and then submit this test again
    
    Change-Id: Ia886feb796b7854645813f486b7b7ac4e944ed17
    BUG: 1101143
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8055
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 21f2e1705af7d9330021c4e4f55f21f39b949634
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jun 12 12:42:05 2014 +0530

    cleanup: Fix domain in log message
    
    Change-Id: I554b9bcacf6c8acd6dffea0a485fc50e82c3dc04
    BUG: 764890
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/8043
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c9791397931a286242b669112b00cb03fefecd6e
Author: Kotresh H R <khiremat@redhat.com>
Date:   Wed Jun 11 16:23:40 2014 +0530

    feature/changelog: Fix compilation warning 'set but not used'
    
    Change-Id: I37de39aec341fbde9516aa8f8c963b70bd808bac
    BUG: 1108034
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8035
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 997d2fbd2dd31c0b16bf9323757cdc97200f6629
Author: ggarg <ggarg@redhat.com>
Date:   Thu Jun 12 18:51:51 2014 +0530

    tests: fix for spurious failure:
    
    Change-Id: I39cc497f12c83aa055acb6e88e4c3e1e8774e577
    BUG: 1089668
    Signed-off-by: ggarg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/8050
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1f21201a434dd37b621efd3cc5d2ef1fd077c303
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jun 4 12:30:44 2014 +0000

    glusterd/geo-rep: Create the conf file path correctly
    
    In case of mount brocker, the conf file path needs to
    be correctly created, and then fetch the status file
    
    Change-Id: Iaa1b04ee46f10961a7056e834170d68282c36efa
    BUG: 1104649
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7977
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 665366a72b720d2eee61aba8b3108e12747db767
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Jun 5 13:17:24 2014 -0700

    geo-rep/gverify: Never use ping to check for host reachability
    
    On many linux distributions with iptables enabled, ICMP traffic
    is usually dropped even when port 22 is open for SSH service
    
    So practically `ping` is an unreliable command
    
    ~~~
    root@rhs1:/var/log/glusterfs # gluster volume geo-replication geo-test \
                              17.16.10.1::geo-test-slave create push-pem force
    172.16.10.1 not reachable.
    geo-replication command failed
    ~~~
    
    ~~~
    root@rhs1:/var/log/glusterfs # ping 172.16.10.1
    PING rhs2.sjc.redhat.com (172.16.10.1) 56(84) bytes of data.
    From rhs2.sjc.redhat.com (172.16.10.1) icmp_seq=1 Destination Host Prohibited
    ...
    ...
    ~~~
    
    ~~~
    root@rhs2:/var/log/glusterfs # service iptables status | grep 22
    4    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:22
    root@rhs2:/var/log/glusterfs # service iptables status | grep icmp-host-prohibited
    25   REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited
    ~~~
    
    Change-Id: I33206ca071aa5d755c0762f7c486da222ec3c7db
    BUG: 1105337
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7997
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 073264c63185c1b3af41c2b1ca6749fcd36a5e94
Author: Poornima <pgurusid@redhat.com>
Date:   Wed Feb 5 02:50:08 2014 +0000

    glusterd/geo-rep: Fix the resource leaks.
    
    Change-Id: Ic741250999880bdf9e1226cd3eefa791fb66a888
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6905
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 115ecc8da8e79e02f23478a2b0721e783792d70e
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Wed Apr 30 15:25:29 2014 +0530

    Core: Fix issues reported by Cppcheck
    
    Fixed in this patch:
    
    [glusterfs/extras/geo-rep/gsync-sync-gfid.c:105]: (error) Resource leak: fp
    [glusterfs/libglusterfs/src/xlator.c:651]: (error) Uninitialized variable: gfid
    [glusterfs/libglusterfs/src/xlator.c:652]: (error) Uninitialized variable: gfid
    [glusterfs/xlators/cluster/ha/src/ha.c:2699]: (error) Possible null pointer dereference: priv
    [glusterfs/xlators/features/changelog/src/changelog.c:1464]: (error) Possible null pointer dereference: priv
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-mgmt-handler.c:865]: (error) Possible null pointer dereference: ctx
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-mgmt-handler.c:194]: (error) Possible null pointer dereference: ctx
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-syncop.c:1408]: (error) Possible null pointer dereference: this
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-utils.c:7002]: (error) Possible null pointer dereference: path_tokens
    
    Fixed in 3.4 and 3.5 branch (http://review.gluster.org/#/c/7583/ ,
    http://review.gluster.org/#/c/7605/ will be backported in a separate patch)
    
    [glusterfs/xlators/mount/fuse/src/fuse-bridge.c:4688]: (error) Uninitialized variable: finh
    [glusterfs/xlators/mount/fuse/src/fuse-bridge.c:3081]: (error) Possible null pointer dereference: state
    [glusterfs/xlators/cluster/dht/src/dht-rebalance.c:1719]: (error) Possible null pointer dereference: ctx
    [glusterfs/xlators/cluster/stripe/src/stripe.c:4940]: (error) Possible null pointer dereference: local
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-replace-brick.c:915]: (error) Resource leak: file
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-replace-brick.c:999]: (error) Resource leak: file
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-sm.c:248]: (error) Possible null pointer dereference: new_ev_ctx
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-utils.c:5297]: (error) Possible null pointer dereference: this
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-utils.c:6273]: (error) Possible null pointer dereference: this
    [glusterfs/xlators/performance/quick-read/src/quick-read.c:586]: (error) Possible null pointer dereference: iobuf
    [glusterfs/xlators/nfs/server/src/nfs-common.c:89]: (error) Dangerous usage of 'volname' (strncpy doesn't always null-terminate it).
    
    False positives
    
    [glusterfs/geo-replication/src/gsyncd.c:99]: (error) Memory leak: str
    [glusterfs/geo-replication/src/gsyncd.c:395]: (error) Memory leak: argv
    [glusterfs/xlators/nfs/server/src/nlm4.c:1199]: (error) Possible null pointer dereference: fde
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-geo-rep.c:1659]: (error) Possible null pointer dereference: command
    [glusterfs/xlators/mgmt/glusterd/src/glusterd-utils.c:7001]: (error) Possible null pointer dereference: path_tokens
    
    Insignificant/Don't care
    
    [glusterfs/contrib/uuid/gen_uuid.c:369]: (warning) %ld in format string (no. 2) requires 'long *' but the argument type is 'unsigned long *'.
    [glusterfs/contrib/uuid/gen_uuid.c:369]: (warning) %ld in format string (no. 3) requires 'long *' but the argument type is 'unsigned long *'.
    [glusterfs/extras/test/test-ffop.c:27]: (error) Buffer overrun possible for long command line arguments.
    [glusterfs/xlators/cluster/afr/src/afr-self-heal-common.c:138]: (error) Possible null pointer dereference: __ptr
    [glusterfs/xlators/cluster/afr/src/afr-self-heal-common.c:140]: (error) Possible null pointer dereference: __ptr
    [glusterfs/xlators/cluster/afr/src/afr-self-heal-common.c:331]: (error) Possible null pointer dereference: __ptr
    
    Change-Id: I7696ed1a2a9553b79f9714e10210a8d563a5abd8
    BUG: 1091677
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/7693
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 75279b20e956588ba7f6c7f2a5b8fa15da5672ed
Author: Sachin Pandit <spandit@redhat.com>
Date:   Thu Jun 12 04:31:47 2014 +0530

    tests : Fix for spurious failure of bug-1104642.t.
    
    Problem :
    This test case checks whether global option is updated
    when glusterd goes down and comes back up.
    
    There might be a scenario where the handshake is not
    completed yet and we issue a volume info in between.
    In that case when we try to grep a key from gluster volume info
    output it might not be there.
    
    Hence to get some time we can issue a peer status command
    and verify that the peer count is correct.
    
    Change-Id: I2933d55ce8c80517a555fa3c2e4cd768cde30abf
    BUG: 1104642
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/8041
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8a2454d4490abb4860fa9ebc83c8bda8ed8aa260
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Jun 5 18:24:56 2014 +0530

    extras/hookscripts: When set option disables smb, don't start smb.
    
    When user.smb or user.cifs option is set to disable, we remove the
    share options from smb.conf. If smb process is running, a sighup is
    required but we should not start the process if its not running.
    
    Change-Id: I1e2163ff209ba858380f7da459ff1dba3cf673f2
    BUG: 1105123
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/7994
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 254a5e484b01f946beff3f51f9ade38f4cdfe51b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 9 08:43:45 2014 +0530

    tests: Add fops sanity
    
    Original-Authors: MS Vishwanath and Sachidananda URS
    
    Change-Id: I7a76b74fc4de24a2d7ec5932ff2c47754abf0521
    BUG: 1084422
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7928
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f1705e2d338704806cbd90ec9d0d66c0b16cc2ef
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Thu Jun 5 10:00:33 2014 +0530

    glusterd/snapshot: Update file-system uuid during snap creation
    
    After the brick snapshot file-system UUID of the origin
    brick and the snapshot brick will be identical. If user
    is using file-system UUID to mount the backend bricks
    then this will result in unexpected behaviour.
    
    Fix: After taking the LVM snapshot create new UUID for
    the snapshot brick.
    
    Change-Id: I339c90abd72dd392de195b674ea22217e63dfd48
    BUG: 1105484
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/8002
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 604ba9abf377ff56bb671478386d4ab977fdcd57
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jun 9 18:33:21 2014 +0530

    mgmt/glusterd: provide interface for configuring the entry point to snapshots
    
    Change-Id: Ibfd0e43db8e5f3f0f2ab6ec6bed88f71397c0bf4
    BUG: 1107531
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/8025
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit d240958fb36e652a2b910fe79414fb8b934e6158
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 23 12:51:28 2014 +0530

    storage/posix: Janitor should guard against dir renames.
    
    Problem:
    Directory rename while a brick is down can cause gfid handle of that directory
    to be deleted until next lookup happens on that directory.
    
    *) Self-heal does not have intelligence to detect renames at the moment. So it
    has to delete the directory 'd' using special flags, because it has to perform
    'rm -rf' of that directory as it is not empty. Posix xlator implements this by
    renaming the directory deleted to 'landfill' directory in '.glusterfs' where
    janitor thread will perform actual rm -rf by traversing the directory. Janitor
    thread wakes up every 10 minutes to check if there are any directories to be
    deleted and deletes them. As part of deleting it also deletes the gfid-handles.
    
    Steps to hit the problem:
    1) On a replicate volume create a directory 'd', file in 'd' called 'f' so the
       directory 'd' is not empty.
    
    2) bring one of the bricks down (lets call it brick-a, the other one is brick-b
    
    3) Rename d to d1
    
    4) When brick-a comes online again, self-heal deletes directory 'd' and creates
       directory 'd1' on brick-a for performing self-heal. So on brick-a,
       gfid-handle of 'd' pointing to 'da is deleted and recreated to point to 'd1'.
    
    5) This directory 'b' with all its directory hierarchy (for now just the file
       'f') will be under 'landfill' directory.
    
    6) When janitor thread wakes up and deletes directory 'd' and gfid-handle of
       'd' without realizing that it is now pointing to 'd1'. Thus 'd1' loses its
       gfid-handle
    
    Fix:
    Delete gfid-handle for a directory only when the gfid-handle is stale.
    
    Change-Id: I21265b3bd3852f0967d916aaa21108ae5c9e7373
    BUG: 1101143
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7879
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit afeaab53f6ca450a3147a6230906a83ee1bebe5a
Author: Kotresh H R <khiremat@redhat.com>
Date:   Wed Jun 11 14:18:02 2014 +0530

    geo-rep/glusterd: Fix glusterd crash during geo-rep config reset.
    
    Problem:
    When "\!<config-option>" (i.e., reset) is used in geo-rep config,
    glusterd crashes with NULL pointer dereference of 'op_value' in
    glusterd_gsync_op_already_set.
    
    Solution:
    glusterd_gsync_op_already_set should be called only for geo-rep
    set option. So bypass glusterd_gsync_op_already_set for reset.
    
    Change-Id: I9d8ef242abf02011139d76a72564f66d68cc8585
    BUG: 1107984
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/8032
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit ee1ef00e2aee6f25b75d156c24ce7f5aab4529a4
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jun 6 16:04:40 2014 +0530

    geo-rep: Making replica failover check interval configurable
    
    Replica failover check interval is hardcoded to 60 sec
    by default. Now this option is made configurable and
    defaulted to 1 sec.
    
    To change the default value
    gluster volume geo-replication <MASTERVOL> \
    	<SLAVEHOST>::<SLAVEVOL> config replica_failover_interval 15
    
    Change-Id: Iada1b80d510452dcfedebd8a21bebd62394b0597
    BUG: 1066410
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/8003
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit f25c88375b0fc03a97a423b565217fb9b55f7850
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Jun 4 17:41:10 2014 +0530

    geo-rep: entry_ops errors handling
    
    Xattr.lsetxattr_l call will not raise OSError which
    errno_wrap can handle, so we need to use Xattr.lsetxattr
    to get proper OSError and errno_wrap ignores or retries
    accordingly.
    
    Change-Id: Ie0a777152ddbaf9ed80c977e4704974fec997bea
    BUG: 1105083
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7972
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit f0c8be68ca68ddb067a40830fecf389c74c13d02
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Jun 6 18:43:15 2014 -0700

    scripts: CTDB lockvol ping-timeout should be 10secs
    
    commit "4044e387dd40e2d12145fd32d5fd715406fcec8e" approach
    to this led to deadlocks instead we rely on an old trick at
    client side - without any need to modifying the volume globally.
    
    Change-Id: I6e3c6bf9c0a3a0dd99a51b5d2a6c1f050ed2384c
    BUG: 1091600
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/8007
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cc6608dbaabac6e46d7f36d964c861cfbaac8f59
Author: Poornima <pgurusid@redhat.com>
Date:   Sun Feb 9 23:29:23 2014 +0000

    protocol: Fix a possible memory leak.
    
    Change-Id: Ia3e7e33389b4d3a5e058b6b2fb2f1c3cb224d6fd
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6950
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5906be31845f6a63ff9d5cd15ad0c13af51b81ea
Author: Sachin Pandit <spandit@redhat.com>
Date:   Wed Jun 4 03:41:35 2014 +0530

    glusterd/snapshot : Store the global snapshot config limit in options.
    
    Problem : Initially we used to save the global config
    limit in glusterd.info, The problem with that approach
    was glusterd.info is local to a particular glusterd
    and hence is not synced during the handshake of glusterds.
    
    Solution : Store the global snapshot config in options,
    which is synced during handshake.
    
    Change-Id: I4c688bb4052a57df28aadba8581b14e2ddb510ef
    BUG: 1104642
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7971
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b9856eca80e2f820c88f60fdc6cb1427905671af
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Jun 5 09:22:34 2014 +0530

    features/locks: Clean up logging of cleanup in DISCONNECT codepath
    
    Now, gfid is printed as opposed to path in cleanup messages.
    
    Also, refkeeper update is eliminated in inodelk and entrylk.
    Instead, the patch ensures inode and pl_inode are kept alive as
    long as there is atleast one lock (granted/blocked) on an inode.
    
    Also, every inode is unref'd appropriately on a DISCONNECT from the
    lock-owning client.
    
    Change-Id: I531b1a02fe1b889fdd7f54b1fd522e78a18ed1df
    BUG: 1104915
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7981
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 8f88510feb49e362531a3cae4b5e295e7ca155e9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jun 11 10:39:35 2014 +0530

    tests: Remove spurious failure test
    
    Change-Id: If428a505c9b5fed31150d6375a318d10e0dc64cb
    BUG: 1107937
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8031
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 020c9842770ede1d715780699671e7e2ac9587ae
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue May 27 08:34:06 2014 +0000

    glusterd/snapshot: Remove mnt pt, while removing lvm
    
    During a delete/restore snapshot remove the mnt point dir
    created at /var/run/gluster/snaps along with the lvm
    mounted on it.
    
    Also removed glusterd_recreate_vol_brick_mounts and
    renamed glusterd_store_recreate_brick_mounts as
    glusterd_recreate_vol_brick_mounts, inorder to reduce
    redundant multiple calls
    
    Change-Id: Ie87907ebbf8ef790fba07ef8581d2eb8d55658d0
    BUG: 1101463
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7889
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 7445593036e411ef96b741448fab89284f91e7f8
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jun 5 04:44:25 2014 +0000

    glusterd/snapshot: Don't update the snap volume's op_version
    
    After the features.barrier key is removed from the snap_vol
    dict, it's op_version should also be updated, so that it
    doesn't inherit the op_version of the original volume when
    it had the key set.
    
    Also in glusterd_volinfo_dup(), which duplicates volinfo the volume
    op_version should not be updated, rather the original volume's
    op_version should be used.
    
    Change-Id: Ib2250700f649e6c906b14aeccee5e78f71d69780
    BUG: 1104944
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7986
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit ec5d64eafcd77b1746b83173de16f7ec742af7a6
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Mar 19 19:32:15 2014 +0530

    gsyncd / geo-rep: FSH recommended log locations
    
    Upgrading "working_dir" on the fly is a bit unclean yet
    (though it works) as currently config upgrade does not
    support "old" values to be expanded by using configuration
    variables.
    
    Change-Id: I44ed65c281f2e0ce3b6b467addc5c1c88ac674e7
    BUG: 1077516
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/7375
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 99781d55f16373e793138c7b011eea09a62075b9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Jun 8 11:23:26 2014 +0530

    features/gfid-access: Fix inode leaks and loc path corruption
    
    Change-Id: Ib506db28415d57b344aa90e07e74666ad2063c64
    BUG: 1104919
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/8009
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 94260c93a144b52964a27ddc9eaef869a3e8f354
Author: Ajeet Jha <ajha@redhat.com>
Date:   Mon Jun 2 14:49:07 2014 +0530

    features/changelog: skipping empty changelogs in history
    
    Empty changelgs are unlinked and htime-update is bypassed
    while publishing partially written changelog.
    
    Change-Id: I1533ad431e4fbf592d2f38837fce782932d01e9c
    BUG: 1105466
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/7949
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit b12b15a186714ec4d5639b778f15e075c833ce55
Author: Sachin Pandit <spandit@redhat.com>
Date:   Fri May 30 08:47:32 2014 +0530

    glusterd/snapshot : Dont create quota.conf if quota is not enabled.
    
    Problem : Quota.conf was getting created during handshake of glusterds
    even if quota was not enabled.
    
    Solution : Check if quota is enabled. If not, then dont create quota.conf.
    
    Change-Id: I55ae487aab5759b25a561705645c1c77ff108670
    BUG: 1101483
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7934
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b97e8f4ef649ed825b4f02b74e33946f6b551cec
Author: Kotresh H R <khiremat@redhat.com>
Date:   Mon May 5 15:33:25 2014 +0530

    feature/changelog: Add timeout to changelog barrier.
    
    This patch introduces configurable 'changelog-barrier-timeout'
    in changelog. The default changelog-barrier-timeout is set to
    120 sec which is same as barrier-timeout of barrier translator.
    On this timeout, all the barriered fops are unbarriered. It is
    safe to have this internal timeout for changelog barrier to
    prevent it from indefinite barrierring of fops if barrier
    disable notification does not come from snapshot for some
    reason.
    
    Change-Id: Iad07807935f88222cdefcd46312b4b6579186dce
    BUG: 1094226
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7669
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit a9cdfa3072f60171a97d9f6af6988b179d45747f
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Jun 9 21:58:29 2014 +0530

    gsyncd / geo-rep: Xsync crawl metadata synchronization
    
    Added "metadata" record for directory and file creations
    during the intial crawl.
    
    Change-Id: I811ae26e0144cadf7249cb64541ec354ab83fe66
    BUG: 1106604
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/8018
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f95a0f99599c0e1825a36eb424b3fe386d6d6b23
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon May 26 12:12:36 2014 +0530

    glusterd : glusterd message-id comments to support extracting the msg-id
    description through doxygen
    
    Change-Id: Ic9660519ae505b78e976e092e7ac80ae63b12a7f
    BUG: 1075611
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7867
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pavithra Srinivasan <psriniva@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f6262b543f0eaa08c2d69310bf2353c9cba009e6
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jun 5 10:06:47 2014 +0530

    features/gfid-access: Fix memory leaks.
    
    Change-Id: I90f6cdb1c8c4face1bb72a9cc77818d308389e45
    BUG: 1104919
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/7982
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4b846dbb61fc6f41ba1bb3d52455f1b44e3a656e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jun 2 14:47:15 2014 +0530

    mgmt/glusterd: delete only the oldest snapshot as part of autodelete
    
    Now this is how autodelete behaves:
    1) Upon creation when the max-soft-limit exceeds, the oldest snapshot is
       deleted. i.e if hard limit is 100 and by default soft limit is 90.
       Whenever snap count reaches 90, every new create results in the deletion
       of the oldest snapshot.
    2) If the snap limit (hard) is reconfigured and brought down
       the current snap count, then no snapshot is deleted and the next snapshot
       create fails as the current snapcount is more than the hard limit.
    3) When soft limit is brought down: say max limit is 100 and by default soft
       limit is 90 and current snap count is 90. Now, soft limit is changed to
       70 (70%). In this case the snapshot count remains 90 itself (i.e extra
       20 snapshots more than the soft limit are not deleted) and for every new
       create the oldest snapshot is deleted.
    
    Change-Id: I1f3b4b9eb093649f8628ebf09a15bd2570ddf340
    BUG: 1103665
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7951
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 66b99406a769a14b50aac2d077b5698b8be30aa6
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jun 3 16:14:35 2014 +0530

    glusterd: Better op-version values and ranges
    
    Till now, the op-version was an incrementing integer that was
    incremented by 1 for every Y release (when using the X.Y.Z release
    numbering). This is not flexible enough to handle backports of features
    into Z releases.
    
    Going forward, from the upcoming 3.6.0 release, the op-versions will be
    multi-digit integer values composed of the version numbers, instead of a
    simple incrementing integer. An X.Y.Z release will have XYZ as its
    op-version. Y and Z will always be 2 digits wide and will be padded with
    0 if required. This way of bumping op-versions allows for gaps in
    between the subsequent Y releases. These gaps will allow backporting
    features from new Y releases into old Z releases.
    
    Change-Id: I463f82902d997ec07e76dae58ac935f33e6393c2
    BUG: 1104997
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/7963
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 211785f29904995324bfd3c7fa4b35a498bf632a
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri May 30 12:37:23 2014 +0530

    rpc: Reconfigure() does not work for auth-reject
    
    Problem:
    If volume is set for rpc-auth.addr.<volname>.reject with value
    as "host1", ideally the NFS mount from "host1" should FAIL. It
    works as expected. But when the volume is RESET, then previous
    value set for auth-reject should go off, and further NFS mount
    from "host1" should PASS. But it FAILs because of stale value
    in dict for key "rpc-auth.addr.<volname>.reject".
    
    It does not impact rpc-auth.addr.<volname>.allow key because,
    each time NFS volfile gets generated, allow key ll have "*"
    as default value. But reject key does not have default value.
    
    FIX:
    Delete the OLD value for key irrespective of anything. Add
    NEW value for the key, if and only if that is SET in the
    reconfigured new volfile.
    
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    
    Change-Id: Ie80bd16cd1f9e32c51f324f2236122f6d118d860
    BUG: 1103050
    Reviewed-on: http://review.gluster.org/7931
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee198c61e56e3ad4abd260ff334e82a4d44eff94
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jun 4 23:01:41 2014 +0530

    tests: add testcase for user servicable snapshots
    
    Change-Id: Ida59727f592c85e81a438e0034a9f94582734417
    BUG: 1094815
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7980
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9707d98ab2e5252307f83104966cd2d318b6434c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jun 4 18:43:36 2014 +0530

    snapview-server: coverity fixes
    
    Change-Id: If4c866b1155bedabd5cf65dae22fa565b7440938
    BUG: 1094815
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7975
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e95dcdc3193cd33d98349d92218e438e5e37cebc
Author: Sachin Pandit <spandit@redhat.com>
Date:   Wed Jun 4 10:30:59 2014 +0530

    mgmt/glusterd : Import the global options irrespective of change in
    volume information.
    
    Problem : global options maintained by glusterd was getting
    synced only when there was change in volume information.
    
    Solution : Import the global option irrespective of change in
    volume information.
    
    Change-Id: I9e59b3cb25bdc19601a09fcf8df2e31a8481ece0
    BUG: 1104642
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7970
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 4215d071cec4fc8a62ca4fd6212d83f931838829
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 6 12:45:12 2014 +0200

    gNFS: Make NFS DRC off by default
    
    DRC in NFS causes memory bloat and there are known memory corruptions.
    It would be good to disable drc by default till the feature is stable.
    
    Change-Id: I93db6ef5298672c56fb117370bb582a5e5550b17
    BUG: 1105524
    Original-patch-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/8004
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4e1ca1be6c26846e876d4181c9f2adea37856ded
Author: Susant Palai <spalai@redhat.com>
Date:   Sun Jun 1 04:37:22 2014 -0400

    Rebalance: Avoid setting other component's xattrs
    
    Problem 1:
     In "gf_defrag_handle_hardlink" we used to do setxattr on internal
    afr keys. Which lead to afr aborting the op saying "operation not
    supported".
    
    Solution : Sending a new xattr with only required keys.
    
    Problem 2:
     Hardlink migration tries to create linkto files for 2nd to (n-1)th
    hardlink of a file on their respective hashed_subvolumes. It may so
    happen that the linkto file already exists on the hashed subvolume
    may be due to an earlier lookup or hashed subvolume on the older
    graph is same as that on the new graph. Hence any new link call may
    fail with EEXIST.
    
    Solution: Will log the message with DEBUG level for EEXIST . Otherwise will
    log with ERROR level.
    
    Change-Id: I51f9bfc8cf5b9d8e94a9d614391662fddc0874d4
    BUG: 1066798
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7943
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bf5a9778c4c05ddd1f2b371abb3d5f70fedf4752
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jun 4 19:53:50 2014 +0530

    features/gfid-access: calloc gfid and set in xdata
    
    Problem: the gfid passed to ga_fill_tmp_loc() was a stack variable which
    the function set in the xdata dictionary. Accessing it in a later point
    in time gave unexpected values.
    
    This was easy to hit when AFR was involved like so:
    ga_mknod()--->xxx-->afr_mknod():
    In afr_mknod transaction, once the stack-winds for the lock-phase are sent,
    the gfid in xdata becomes out of scope. When we send the actual op i.e.
    afr_mknod_wind(), the gfid in xdata is stale, causing posix to set junk
    gfids on the files.
    
    Fix:
    calloc the gfid and set it in the dict.
    
    Thanks to Pranith for the RCA!
    
    Change-Id: I0291fce34745268dc63095fc41fe31c7213dd5e1
    BUG: 1104707
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7978
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d64d0129ee8e0c32f027cf9df17e8debfaf73ab2
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Thu Jun 5 13:26:22 2014 +0530

    gluster: Set ping-timeout between glusterd peer rpc connection
    
    With Patch# http://review.gluster.org/#/c/7753/, ping-timeout
    got disabled between glusterd peer rpc connection.
    This would create regression for bug#1034479
    
    Change-Id: Ib7a756fce7d349ce5b7b4c6a287f2d040c83fc76
    BUG: 1097224
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7989
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f2b42887c1f9780980abe491ed34a13a7b3d4583
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed May 28 16:57:14 2014 +0530

    glusterd: Preserve backward compatibility during sync and store
    
    The glusterd volinfo struct gained several new members to support the
    volume snapshot feature. These members are also being exported/imported
    during volume sync and being stored/restored. This export/import and
    save/restore explicitly required these members to be present, and would
    fail if they were not. This lead to the failure of backward
    compatibility, preventing new peers from correctly interacting with
    older peers (especially during a rolling upgrade).
    
    This patch contains changes needed to preserve the backward
    compatibility in the places specified. The snapshot members of the
    volinfo will now be exported/imported and stored only when the cluster
    op-version is >= 4, ie. all peers in the cluster support snapshot.
    No change is required for the restore code as, the new members will be
    left at the default zero values if corresponding entries are absent in
    the stored volinfo.
    
    Change-Id: I79e4bc5780c991ec305b7b5e7d71c16afb6a4c40
    BUG: 1101903
    Reviewed-on: http://review.gluster.org/7944
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 77498fdbbca8554880eae4b8f559b9d6876e35b7
Author: Kotresh H R <khiremat@redhat.com>
Date:   Sun May 25 23:41:48 2014 +0530

    feature/geo-rep: Fix to retain pause state of gsyncd on restart.
    
    A new gsyncd options '--pause-on-start' is introduced. When node
    reboots, if the status is paused, gsyncd is started with this
    option. After gsyncd spawns worker and agent, worker will send
    SIGSTOP to negative pid of monitor to enter pause mode.
    
    Change-Id: I5aad82c9a9fc8c243f384940b77d25e26e520d6d
    BUG: 1101410
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7885
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 535003ca20a9dd00a09dd34ad26947d888aabe39
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Jun 2 14:11:29 2014 +0530

    logging: Prior to log initialization, print all logs to syslog.
    
    There can be calls to gf_msg even before caling logging_init().
    Currently such messages appear on stderr. In this patch, gf_msg
    is changed to log messages to syslog if the logging framework is
    not inited.
    
    Change-Id: I8fcf562f9d07b5b6b789fbd9e6f37b354de16b98
    BUG: 1103623
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7948
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 42b956971c47fd0708cbbd17ce8c78c2ed79bfba
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Fri May 23 14:42:08 2014 +0530

    glusterd: Handle rpc_connect failure in the event handler
    
    Currently rpc_connect calls the notification function on failure in the
    same thread, glusterd notification holds the big_lock and
    hence big_lock is released before rpc_connect
    
    In snapshot creation, releasing the big-lock before completeing
    operation can cause problem like deadlock or memory corruption.
    
    Bricks are started as part of snapshot created operation.
    brick_start releases the big_lock when doing brick_connect and this
    might cause glusterd crash.
    There is a similar issue in bug# 1088355.
    
    Solution is let the event handler handle the failure than doing it in
    the rpc_connect.
    
    Change-Id: I088d44092ce845a07516c1d67abd02b220e08b38
    BUG: 1101507
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7843
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a89e35727e3a9a7226c7a16479935b7109b11663
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon May 26 10:35:45 2014 +0530

    features/quota: unref and set priv->rpc_clnt to NULL once disabled.
    
    Change-Id: Ic1a6bc36b26cf31f00644bd674b24daa11745e64
    BUG: 1103636
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/7876
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7801334d4872c3b5c5580ea46654ef0cc0b83658
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Fri May 23 20:04:35 2014 +0530

    doc: Document libgfapi and its apis,usage,bindings..etc
    
    Change-Id: I3435f9a88acafa905e879c68bb7aa8b16023cf02
    BUG: 1086766
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Signed-off-by: Soumya k <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/7865
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 4e8d5af64d78533e801cac45ccb28ace7d91cc62
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed May 28 12:23:43 2014 +0000

    glusterd/geo-rep: Not setting the user name as the user group by default
    
    Also removing multiple mounts in gverify.sh
    
    Change-Id: I1567a9f711222c5f571a12f7c4ab49cef32d60c9
    BUG: 1101948
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7911
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 7e3b038c6cea6a89feae684012fa6a33443c7473
Author: Sachin Pandit <spandit@redhat.com>
Date:   Thu May 15 09:24:33 2014 +0530

    cli/snapshot : Dont Do the validation of snapshot config limit in CLI
                   code path.
    
    Problem : If we try to set the volume snap limit to
    more that 256, it always shows value cannot exceed 256,
    irrespective of system max limit.
    
    Solution : Dont do validation in CLI side.
    
    Change-Id: I292c0bc91a1806cd4906fca0151dd98135e6e49a
    BUG: 1098122
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7777
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 9f90cbee7da450271873340c0b13059064c41af1
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Jun 3 05:50:53 2014 +0530

    glusterd/snapshot : Remove the barrier key from snap volinfo
    before generating brick volfile.
    
    Problem : During snapshot creation if I/O is in progress,
    then barrier value is enabled. Hence during snapshot create
    and in-turn snapshot restore the barrier value is set to enable.
    Because of this further I/O on the mount point fails.
    
    Solution : Remove the barrier key from newly created snap volinfo
    before generating the brick volfiles.
    
    Change-Id: I180b3adfbb364159fd353b2d0fb630e004099aa5
    BUG: 1098487
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7892
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit ea58f256463efb07824dbd307af06f2c3960f254
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri May 30 01:07:04 2014 -0700

    build: Avoid gcc pragmas when clang is enabled
    
    Change-Id: I86544a9bfd24ef1a69315c0f6c3abcdd9aeb2c69
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7932
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1f95e55cc633e9b082b4eb37a6a825c0e33ac5c8
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jun 3 11:55:49 2014 +0530

    mgmt/glusterd: return proper value upon quorum failure in snapshot create
    
    Change-Id: I5474a7cdf03236121bef383955ab403e945cd7ae
    BUG: 1101561
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7961
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 31520d9334f9a40aa329d54651bca7e2c2e5d545
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Apr 1 09:20:05 2014 +0530

    glusterd/status : First fetch the snapcount and then send the rpc call
    for individual snapshots for snapshot status
    
    Problem :
    
    Initially, we used to do all the calculation in the
    glusterd side, once all the information related to
    snap was fetched, it was aggregated into one
    dictionary and that was sent back to CLI. Problem
    with this approach was, when number of snapshots
    are very high then CLI will timeout.
    
    Solution:
    
    First fetch snapcount and snapname from glusterd,
    then make a individual calls using the snapname
    fetched. This will resolve the timeout problem.
    
    Change-Id: I32609b3898ed227c804dd4d8ee4516f081240756
    BUG: 1087676
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7456
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 0fe5ab5b9215b8f0ecfb8bc4ba15a5370850654a
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue May 6 12:39:20 2014 +0000

    glusterd: Changes to provide interface for USS
    
    The changes which consists of the translators for the USS (User Servicable
    Snapshots) is submitted as a separate patch. Current patch provides the
    CLI access to the feature.
    
    Change-Id: I6b98a42fcfa82f0870d8048fe0bb53141565e9c6
    BUG: 1094815
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/7705
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 15f7b4de1124a37a53c7ddb5635b005322b23025
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jun 2 12:54:52 2014 +0530

    snapview-server: use telldir api to get the offset of the dentry
    
    * dirent structure (struct dirent) in NetBSD does not contain the offset
      member. Direct access of offset from struct dirent (used here to copy
      its contents to gf_dirent_t structure after making readdir call) causes
      glusterfs build failures on NetBSD. So like posix does, use telldir api
      to get the offset of the dentry (in this case glfs_telldir).
    
    Change-Id: I72472c16cbf55dd99ea80ba982b0a4205e6ebffb
    BUG: 1103591
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7946
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 294b9548489c04b7ae30ed4706cc7176d8b8780b
Author: Meghana M <mmadhusu@redhat.com>
Date:   Tue May 27 16:01:17 2014 +0530

    Hooks/nfs-ganesha:Change the hook script to enable new function signature of add export.
    
    Minor changes in the hook script to avoid some
    possible confusion when volume set options are used.
    Adding a few additional checks to ensure correct behaviour.
    
    Edited a few config parameters that have changed in upstream
    ganesha recently.
    
    Change-Id: I85b842cbbd4b35b7f72f3beb60abf6532ddaa8c7
    BUG: 1101416
    Signed-off-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/7890
    Reviewed-by: soumya k <skoduri@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a96350fa2b68626b8592d5cbd67405e4d8416cca
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri May 23 12:58:56 2014 +0530

    glfs_fini: Fix a possible hang in glfs_fini.
    
    glfs_fini is called when there is a failure in glfs_new,
    glfs_init etc. If an application sees a failure in glfs_new
    and calls glfs_fini, it will result in hang in glfs_fini.
    
    Fixed the hang.
    
    Change-Id: I80b52cd76d1d7f3fe9a10a91b7226d54176a8982
    BUG: 1091335
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7857
    Reviewed-by: soumya k <skoduri@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e8c13fa9bd2a838335e923ec48bcb66e2cb5861d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu May 29 11:59:30 2014 +0000

    glusterd: Fetching the txn_id before performing glusterd_op_bricks_select in glusterd_brick_op()
    
    In glusterd_brick_op(), the txn_id mut be fetched before
    failing the transaction for any other reason. Moving
    the fetching of txn_id to the beginning of the function.
    
    Also initializing txn_id to priv->global_txn_id where it
    wasn't initialized.
    
    Change-Id: I44d7daa444f00a626f24670c92324725f6c5fb35
    BUG: 1102656
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7926
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 4f9314a5eda016d5a03ad637f2c6171794cc9291
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed May 21 05:45:39 2014 +0200

    NetBSD qemu build fixes
    
    Fix NetBSD build for glusterfs built in qmeu sources
    
    BUG: 764655
    Change-Id: I4428a88b1e0d7c5f6740022861ffe230dbbd84bd
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/7815
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit db022ef7ecca77cbecbcc4c046b6d3aafd2cb86f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 21 17:47:03 2014 +0530

    cluster/dht: Fix min-free-disk calculations when quota-deem-statfs is on
    
    PROBLEM:
    
    As part of file creation, DHT sends a statfs call to all of its
    sub-volumes and expects in return the local space consumption and
    availability on each one of them. This information is used by DHT to
    ensure that atleast min-free-disk amount of space is left on each
    sub-volume in the event that there ARE other sub-volumes with more
    space available.
    But when quota-deem-statfs is enabled, quota xlator on every brick
    unwinds the statfs call with volume-wide consumption of disk space.
    This leads to miscalculation in min-free-disk algo, thereby misleading
    DHT at some point, into thinking all sub-volumes have equal available
    space, in which case DHT keeps sending new file creates to subvol-0,
    causing it to become 100% full at some point although there ARE other
    subvols with ample space available.
    
    FIX:
    
    The fix is to make quota_statfs() behave as if quota xlator weren't
    enabled, thereby making every brick return only its local consumption
    and disk space availability.
    
    Change-Id: I211371a1eddb220037bd36a128973938ea8124c2
    BUG: 1099890
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7845
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0d26de1b0a4a0fbf7e33dab8bc46c38c179e8645
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Thu May 22 11:22:12 2014 +0530

    libgfapi: Fixed few memory leaks in glfs_h_getxattr, glfs_h_setxattr calls.
              Also replaced the tabs with spaces in that entire file.
    
    Change-Id: Iee6dc031d27fe8d26caf90736d4b2ac7bc8c5206
    BUG: 1089414
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/7841
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8c7644cd730c482e53b756170463d54b33686db5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Sep 25 14:17:50 2013 +0530

    afr-v1 documentation.
    
    Change-Id: I0cb77e2e64492704f9fc016d9ba9872237664aa4
    BUG: 1086781
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6574
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit c50766a76783e15b25a9bc57a4ece190df4e2a5b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue May 27 17:46:08 2014 +0530

    mgmt/glusterd: return failure when server quorum is not met
    
    Change-Id: I0a7df141d01cf70da5aac9658b2a5a19f660dd3b
    BUG: 1101561
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7894
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 58c4a882c37eb2042cbea341fceb4bd0ef028d9a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun May 18 19:33:27 2014 +0530

    storage/posix: Remove special handling of ENOTSUP for [f]setxattr.
    
    Change-Id: I7df7b2263336af0abe5bc91c674f9401aff6c3e0
    BUG: 1098794
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7788
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3230db8561ddfec2aa26fc106ec65b4a307b6db6
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu May 22 10:25:47 2014 +0530

    cluster/afr: Add descriptions to message-ids.
    
    Change-Id: I7ec2821c96d4cbff78b4959d9b07019896cc9a2c
    BUG: 1075611
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7840
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 7b96fd92de79f367bfa8591becdb30340a4a26e7
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Mon May 19 13:09:07 2014 +0530

    cli: 'Snapshot Volume: yes/no' for volume info needs to be removed
    
    With initial design where the snap volume used to be displayed in
    gluster volume info,
    we used "Snap Volume: yes/on" to distinguish the volume whether its a
    snap volume or the original volume.
    But with new design the snap volumes are not listed in the volume info,
    hence this entry (snap volume:) doesn't make sense to show.
    
    Change-Id: Ic5b9948bf4ef74e89a611742c74a8989cb406866
    BUG: 1098910
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7794
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit ac43be9d9c1925a5fddf21ba2061f414e53140a8
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Tue May 20 12:25:47 2014 +0530

    glusterd/snapshot: Use external umount for un-mounting snapshot
    
    umount2 doesn't cleanup /etc/mtab entry after doing umount,
    so use external umount command for un-mount operation.
    
    Change-Id: I1a91a700433e2bf15dd21e6fcdd9da54441048d1
    BUG: 1098084
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7775
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 748175e35e9d2d2506a875bafd6b63889512b7e5
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Thu May 22 17:31:11 2014 +0530

    doc: Add 'expose volume capabilities' details of bd-xlator
    
    Change-Id: If7a89a36c2eca653e4fa7f59597ac8b03e4bc747
    BUG: 1086749
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Signed-off-by: Bharata B Rao <bharata.rao@gmail.com>
    Reviewed-on: http://review.gluster.org/7844
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 8049696c48dc1a51a76629c2bd2fdc1cf187a5b5
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 28 21:56:02 2014 +0530

    doc/rdmacm: fix formatting errors.
    
    BUG: 1086743
    Change-Id: I24798ef1e359dc2508d495e244151e93537b52a4
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/7914
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 42332a4269359a9c2dcb66a8abbc75a649f767a0
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 28 13:55:59 2014 -0400

    features/glupy: GPLv2 or LGPLv3+ license
    
    Change-Id: I1ce4735619ac03a81f6ed43bba27c9fbb25c4de1
    BUG: 1102305
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/7917
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a9d4b942d714f42dd12a6bfcc8d55cd12551dd25
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue May 27 05:30:29 2014 +0200

    NetBSD build fix for gettext
    
    NetBSD's gettext is in libintl, hence search it at configure time.
    
    BUG: 764655
    Change-Id: I651a74fe49c3f087fe135dab3453fd5b18b4268a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/7880
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 57df032636f613469cf0ef0a3ecffdcd2cd51249
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 28 15:12:42 2014 +0530

    doc: add readdir-ahead documentation
    
    Change-Id: Ib6fc3c9b59b498bfe3fb3dfc23dca874bdc0d21d
    BUG: 1086755
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/7903
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit a181282d1465c98c9b07bc7ea37e7096a7799a11
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu May 29 06:53:32 2014 +0000

    tests/cluster.rc: Moving the glusterd logs for cluster testcases
    
    Moving the glusterd logs for cluster testcases from /d/backends to
    logdir.
    
    Change-Id: I6f22ca0c2faa87b0774e718c6c26d6547afd7c51
    BUG: 1102593
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7924
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a726e3e538f65d028d5da4cdbdd7892b9577dba1
Author: Poornima G <pgurusid@redhat.com>
Date:   Thu May 22 16:46:15 2014 +0530

    rpm: Rename old hookscripts in an RPM-standard way.
    
    Change-Id: I5e47ac8af8033821787281574276f38933de73cf
    BUG: 1100251
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7362
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cc0378d39f4082f51d5ef6e02b3007fe9e78cb31
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed May 7 20:13:43 2014 +0530

    user servicable snapshots
    
    Change-Id: Idbf27dbe088e646a8ab81cedc5818413795895ea
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Anand Subramanian <anands@redhat.com>
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7700
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 58b9edee87bba3ffe812cf15f171926be017575b
Author: Susant Palai <spalai@redhat.com>
Date:   Fri May 9 00:39:10 2014 -0400

    Posix/readdirp : Avoid filling wrong stat info for dentry in readdirp
    
    Problem:  Upon no entry found for a dentry, posix_readdirp_fill
              used to fill the stat for the current entry with the
              previous one.
    
    Solution: Continue with other entries if lstat failed for current
              one
    
    Change-Id: Ic96b5900451ed6c8de59acf9fee2e116649d3cdb
    BUG: 1096578
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7733
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit deaaaec82a0aae1edfeb0688e20498fafa896c83
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Feb 19 05:47:07 2014 +0000

    DHT: Wrong error handling in gf_defrag_migrate_data
    
    Problem:
             Because of the condition (err = op_errno), err was set to
    zero always and ENOSPC error will be logged always. "dht_check_free_
    space" was returning 1 and it was mapped to EPERM in "rebalance_task
    _completion".
    
    Solution: Changed the return value in dht_check_free_space to -1
    as in rebalance_task_completion op_ret value -1 is mapped to ENOSPC.
    
    And fixed the wrong error condition after syncop_setxattr in
    gf_defrag_migrate_data.
    
    Change-Id: I474ea1bef3b1e34c89814ed0091dd02bd5b63737
    BUG: 1054703
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/6727
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 847a481ceb626af97a1487c6289cdd92677b212a
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Mar 19 17:22:10 2014 +0000

    DHT/Mkdir: Fail mkdir with ENOENT, if parent is not available
    
    Change-Id: I54227bcafb6d0d8cf716a679d2a34be7fc916898
    BUG: 1078847
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7306
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3023a363bdf10675daa6eb59179f53edfc66db7a
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri May 23 15:43:25 2014 +0530

    feature/gfid-access: Adding documentation
    
    Adding documentation to feature 'gfid-access' translator.
    
    Change-Id: Ib70c0957ea22580cef2c7219a31dd9df33e9cd37
    BUG: 1086751
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7862
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 21f43129b42dce6692cd7f82cc7a8be6682e35a4
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed May 28 14:37:18 2014 +0530

    transport/rdma: Add rdma connection manager documentation
    
    Change-Id: I15ad9cafbe607074ddb9b36f9e879c8421f6eae2
    BUG: 1086743
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/7901
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit d2d014c97fe18c1ca0d3b44045e5aae077ebbb63
Author: Susant Palai <spalai@redhat.com>
Date:   Tue May 27 01:29:38 2014 -0400

    doc: quota-scalability documentation
    
    Change-Id: Ia6516293a7d6dc2643bb05767875b0cb651a65ef
    BUG: 1086754
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7882
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit bb02cfb56ae08f56df4452c2b948fa962ae1212b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 15 11:50:53 2014 +0530

    cluster/afr: Don't support heal info healed/heal-failed commands
    
    Change-Id: Iecfd3150e4f4e795e3403bcb1ac56340759a37d0
    BUG: 1098027
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7766
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 38b2531d91e51dc73ba99ebcd3b98db75affa7d7
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed May 21 13:30:02 2014 -0700

    features/changelog: NULL termination after memcpy should be of dest pointer
    
    snippet code
    <
     ..memcpy (bufff, src, len - 1);
     ..*(src + len) = '\0'; ---> Wrong!
    >
    
    Source buffer lvalue() referencing with offset style NULL
    termination is wrong and unnecessary when we have a destination
    buffer, it is the destination buffer which should look to be NULL
    terminated
    
    Makes it more readable and also clearly logical.
    
    <
     ..memcpy (bufff, src, len - 1);
     ..bufff[len -1] = '\0'; ---> Correct!
    >
    
    Change-Id: I6d7f312aaa5c541f0345649ff1ef9f193892b674
    BUG: 1099986
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7836
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 048902f108ad3c437e83248c14de33e6519d9f07
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 20 19:18:31 2014 +0530

    tests: Run prove in UTC timezone
    
    This will make it easy in finding the relevant logs easy.
    
    Change-Id: I9ac9988327ea28c20477655df9c9f606fd7d6c8e
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7810
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b512d6b4554515d034f1b3e7cd15a5971cad248e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu May 22 14:18:39 2014 +0000

    glusterd/snapshot: Invoke restore cleanup for missed restores
    
    While performing missed restores invoke restore cleanup,
    to cleanup the snap file (from which the vol was restored)
    and also the old volinfo and if the old volume is a
    restored volume, then its lvm too.
    
    Change-Id: Ifa5700c69f49fa0e22e0060a039c2e5c0b02b585
    BUG: 1100324
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7848
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 47a490c6933304aa2d58c8c2fb242fdde1e0a4c3
Author: Kasturi Narra <knarra@redhat.com>
Date:   Fri May 23 19:52:10 2014 +0530

    doc:Adding documentation for glusterfs and ovirt integration
    
    Change-Id: Ie3b42a74198150c7e353d360ad38ac127d1a5ca2
    BUG: 1086782
    Signed-off-by: Kasturi Narra <knarra@redhat.com>
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/7772
    Reviewed-by: Sahina Bose <sabose@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Shubhendu Tripathi <shtripat@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit c9d53e53af5e6fe81d524360fa901c4c8d865520
Author: Susant Palai <spalai@redhat.com>
Date:   Mon May 12 01:55:15 2014 -0400

    Glusterd/Rebalance: Update rebalance status properly in
                        node_state.info
    
    credit: kaushal@redhat.com
            spalai@redhat.com
    
    Change-Id: I08d0771e2168a4a6ebd473e8a937b8b2eda1341a
    BUG: 1075087
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7214
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit c2d74c4649e9022dca90e283e31fbee2cc0de8f5
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Mon May 26 16:52:39 2014 +0530

    doc: update details about posix acl on nfs mount
    
    Change-Id: I591f2393a11893c77990a5b994196cb0a01358aa
    BUG: 1086774
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/7871
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit be8a3845c7d76d7da66ad278618ff29d0b81903c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed May 21 20:49:22 2014 +0530

    gsyncd : Use --remote-host option during cli invocation
    
    Required for unprivileged geo-replication sessions to
    execute glusterd commands (which are however restricted).
    
    Change-Id: Ib83b81defa061717f4465ffa665450d0f5d3d20d
    BUG: 1077452
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7833
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 74cc911d4301905d0722a943ca2b844637d4dc74
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed May 21 14:18:06 2014 +0530

    gsyncd / geo-rep: Mountbroker cli to use INET sockets
    
    unprivileged geo-replication session runs the slave gsyncd
    process as unprivileged, thereby executing gluster cli commands
    as an unprivileged user. By default, cli to glusterd
    uses unix domain sockets, thereby restricting cli command
    execution by non root users.
    
    This patch introduces '--remote-host' cli option to force
    cli to use INET socket. For this to work, the following
    needs to be added in glusterd volfile
    
          option rpc-auth-allow-insecure on
    
    Change-Id: I84b1711281bbcbde156200f80ebdb065afb55488
    BUG: 1077452
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7820
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bbb8313568bd0725f9faf1927ccefe79126a2113
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed May 21 11:54:24 2014 +0530

    gsyncd / geo-rep: fix cli query for volinfo fetch
    
    With an unprivileged geo-replication session, monitor
    was using user@slave for --remote-host option for gluster
    cli, thereby failing to sucessfully connect to the slave
    glusterd.
    
    This patch fixes the issue by selecting the hostname/IP
    from the speicified slave endpoint url.
    
    - For privileged geo-replication sessions, this patch
    has no effect as the slave endpoint url is just the
    hostname/IP.
    
    Change-Id: I88f66c406a8d9a34db7fc626965f949075e3ceac
    BUG: 1077452
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7818
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a6da7b531bccbec8c8320acb09e2ee6a5df73a33
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue May 20 19:57:37 2014 +0530

    mgmt/glusterd: Allow mount/umount requests over AF_INET
    
    Along with a simple naming convention change to avoid
    confusion as per below.
    
       s/gd_svc_cli_prog_ro/gd_svc_cli_trusted_progs/
       s/gd_svc_cli_actors_ro/gd_svc_cli_trusted_actors/
    
    Change-Id: Ibc73d88846636656f060a811f641f37a1a864615
    BUG: 1077452
    Original-Author: Vijay Bellur <vbellur@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7821
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5224a785faaa615adac7cd25207912ab109ad7e6
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue May 20 14:50:25 2014 +0000

    glusterd/geo-rep: Creating .ssh dir with right ownership
    
    Also adding -P option to the usage of df for portability in gverify.sh
    
    Change-Id: I0be19d26ea63769a934c6ccbfc04ef80768ebc9a
    BUG: 1099041
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7812
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Aravinda VK <avishwan@redhat.com>

commit 9dce23c30edb3622049d40ea16877c7b26e5753b
Author: Anand Avati <avati@redhat.com>
Date:   Sun May 18 11:40:27 2014 -0700

    meta: fix compile warning
    
    Change-Id: Ic346458b0e7264469d617b8313d4087b4b21c4b8
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7789
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit b7ae88b63fb6ea1abdb86669f2a786b94a6470b4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 23 13:06:26 2014 +0530

    libglusterfs: Fix unused variable warning
    
    Change-Id: If385ba0993fdbd3e3b7500b2b6631721911e0ab3
    BUG: 1100144
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7858
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 090131cd75f781d71c01357d148895e417bd3da2
Author: Nithya Balachandran <nbalacha@redhat.com>
Date:   Tue May 13 10:48:39 2014 +0530

    Doc: Indentation fix for Gluster man page
    
    Corrected the indentation for the Log Commands section
    
    Change-Id: I9c706bc727d67e4ae3bde4d2556b3ffcd920ceeb
    BUG: 1097051
    Signed-off-by: Nithya Balachandran <nbalacha@redhat.com>
    Reviewed-on: http://review.gluster.org/7746
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1d8ad8a993a256155032787b34f16d07843482ef
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri May 23 10:18:35 2014 +0530

    doc: fix brick port ranges in admin guide.
    
    Change-Id: Ie6ac43ea435b7b21ac2b7975cbfe38126b170100
    BUG: 1095595
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/7855
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 660c5dbba0d639b0ce8a13f69a05771cf895fb64
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri May 23 14:13:57 2014 +0530

    doc: distributed geo-replication
    
    Change-Id: Id89089aa52066634e8a6428c2bf00ea4f30f1943
    BUG: 1086758
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7859
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 8cd30687d3ffbc29838956305ea8716bb9719acb
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu May 22 14:31:13 2014 +0000

    glusterd/vol_locks: Dereference ctx->dict, only if ctx != NULL
    
    Change-Id: I7f753aff197fe08fad255fc75d7f88d2a4632de8
    BUG: 1100325
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7849
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f0ccf3ac43cd6e0fe1b3dc1a429cb3ec18a25db7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 21 17:15:34 2014 +0530

    encryption/crypt: Don't perform open on symlinks
    
    Change-Id: I9be8634f8f3b09def21ba977050330aa3f26c230
    BUG: 1099858
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7824
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5efeba0f44f9d2f79af8f51fe01ec66c59851d54
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri May 23 10:55:33 2014 +0530

    doc: changelog consumer library
    
    Change-Id: I1e641e1a61b78c84ed610a56eabdad1075865cd3
    BUG: 1086758
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7856
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 9ce93bc3be1dd5a5caecbb45966bc6b7b8e2c32b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 21 22:37:13 2014 +0530

    libglusterfs: Provide a way to disable mempool effects
    
    Problems:
     - Mempool comes in the way of debugging mem-leaks/corruptions
       because tools like valgrind can't detect mem-pools.
    
     - Accessing freed pointers may crash only when the mem-pool
       is completely exhausted.
    
    Solution:
    In DEBUG builds set mempool count to 0 irrespective of the
    pool size requested. This should help in debugging
    memory-leaks/corruptions.
    
    Change-Id: I7c6a2d696e330f12acff57ebdc589cc150e9ab79
    BUG: 1100144
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7835
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0127da7bb24794e737adc5a3195d3c54a175257f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 21 15:17:23 2014 +0530

    storage/posix: Don't allow open on symlink
    
    Change-Id: Ie38ecad621d5cb351c607c9676814c573834cb0b
    BUG: 1099858
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7823
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e9a1a7135b9927fbdefd2921b38e10bdbb694b97
Author: Varun Shastry <vshastry@redhat.com>
Date:   Sun Mar 23 13:28:36 2014 +0530

    features/quota: Send the immediate parent with limit in quota statfs adjustment
    
    Problem:
    Assume the directory structure /quota_limit_dir/subdir and quota_limit_dir is
    set with some limit. When quota-deem-statfs is enabled the output of
    'df /quota_limit_dir' would display quota modified values wrt to
    quota_limit_dir where as 'df /quota_limit_subdir/subdir' would display the
    quota modified values wrt volume root (/).
    
    This behaviour is not expected since, when mounted with subdirectory admin
    doesn't want users to know information above the subdirectory mounted.
    
    Solution:
    Any subdirectory within a quota_limit_dir would show the modified values as in
    the /quota_limit_dir. It searches for the nearest parent that has quota limit
    set and modifies the statvfs wrt that.
    
    Change-Id: Ie10fae8999bddbb766b1dbeb881723ed80dce688
    BUG: 1080296
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/7330
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit 15f698833de54793880505a1f8e549b956eca137
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Thu May 22 11:58:06 2014 +0530

    glusterd/snapshot: brick_start shouldn't be done from child thread
    
    When creating a volume snapshot, the back-end operation 'taking a
    lvm_snapshot and starting brick' for the each brick
    are executed in parallel using synctask framework.
    
    brick_start was releasing a big_lock with brick_connect and does a lock
    again.
    This will cause a deadlock in some race condition where main-thread waiting
    for one of the synctask thread to finish and
    synctask-thread waiting for the big_lock.
    
    Solution is not to start_brick from from synctask
    
    Change-Id: Iaaf0be3070fb71e63c2de8fc2938d2b77d40057d
    BUG: 1100218
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7842
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit cec37c9b66b8711b213f114875d215f56b8120aa
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu May 8 12:30:23 2014 -0300

    logging: remove unused message-id scripts
    
    The current unused implementation for message-ids in the logs depends on
    automatically generated files. The generated files are not included in
    the distributed tarball. This causes issues when distributions build
    packages, they need to re-run ./autogen.sh to create the needed files.
    
    I thought of including the generated files in the distribution tarball.
    However, the contents of these files are not actively used, so it seems
    to make more sense to drop it all together. These functions were the
    only users of libintl and gettext too, so dropped the requirement
    checking from configure.ac.
    
    A replacement for the message-id logging framework is in progress. Any
    changes that this patch makes, can be reverted in the submission of
    patches for the new framework.
    
    Reference: http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6212
    Change-Id: Iea82dd3910944a5c6be3ee393806eccabd575e11
    BUG: 1038391
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7714
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2e7ed9e196a04d19a78e2880af21b959ca1f578b
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Wed May 21 21:56:54 2014 +0530

    doc: Add details on qemu glusterfs integration
    
    Change-Id: Ib3cd71f278c29483a467ee5afdd1aeb9e5f54547
    BUG: 1086783
    Signed-off-by: Bharata B Rao <bharata.rao@gmail.com>
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Signed-off-by: Satheesaran S <satheesaran@gmail.com>
    Reviewed-on: http://review.gluster.org/7834
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit 79de5b63775f1ab8e2e498fd51b55509a30cd896
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon May 19 09:25:34 2014 +0200

    tests/rpm: always run ./autogen.sh to create missing files
    
    In some occasions 'install-sh' seems to be missing in the 'make dist'
    tarball when ./autogen.sh has not been run (skipped when 'configure'
    exists). With this changes, 'autogen.sh' is always run so that missing
    files should get added to the tarball.
    
    Also write the logs from mock to a known location, and copy them to the
    '/var/log/' directory that Jenkins archives after a regression test
    failure. This makes it easier to find build issues that mock detects.
    
    Change-Id: I8d0cf1afef61ebab0137aa0d20521e75a35ddbdd
    BUG: 1038391
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7786
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0a77eb1e4576d8722b27a42c98879cc7250e00fe
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 22 05:53:02 2014 +0530

    tests: s/timeout/EXPECT_WITHIN/
    
    Also fixed nfs.rc so that regression build works on my fedora VM
    
    Change-Id: Ife36343bf1a590430e24065b9bcdf5bed3ae546d
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7837
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 99afc640f27841ec819c0f32c01f567fd0b345f8
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Tue May 20 17:49:11 2014 +0530

    doc:  Add block device xlator details
    
    Change-Id: I4c24a7f0a4339364a80e5d1be0fc8de6b9c189c1
    BUG: 1086762
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/7809
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 5315df764458022d3664459123880880a27fc849
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 20 20:38:18 2014 +0530

    Tests: Umount nfs mount before volume stop
    
    Change-Id: Ia1b98ee56bfa562c3f97f1649699f49917ebbfc7
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7813
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit abaebaef5ab7e3bef254ded2ef9bb93aaa6c39dc
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue May 20 19:50:10 2014 +0530

    doc: afr-statistics command  documentation
    
    Change-Id: I44ae593c319a3ad2f724e1d8e9557d94c4200765
    BUG: 1086748
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/7791
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit f6677d1e307e94a282b3a0194e30785ea88c09bb
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon May 19 11:55:34 2014 +0000

    glusterd/geo-rep: Use getent passwd instead of $HOME
    
    $HOME might not be set in the env variables, as is the case
    when these scripts are executed using the runner framework.
    Hence using getent passwd instead of $HOME
    
    Change-Id: I99f6bcd788d727be534b3040600d66c8dbb7ee92
    BUG: 1099041
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7803
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 5e2e97300d6e5248bb1c58825e5fe586e93c7cf4
Author: Humble Chirammal <hchiramm@redhat.com>
Date:   Mon May 19 17:11:47 2014 +0530

    doc: zerofill api documentation
    
    Change-Id: I437735d68fdcc4a55f12fd51b1d40cd7a32ad783
    BUG: 1086756
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/7800
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 0b4fc6c8bfed9ccc87d97056399a848c8990e500
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat May 17 16:26:34 2014 -0700

    rpc: make sure we use relative path
    
    In commit "618d465295df02ae6d53be1327947a210bb8b47d" we made
    change regarding NetBSD make by replacing `$<`, fix it
    accordingly.
    
    Change-Id: Ief82887253ede8216efd0ae7d5f73329f1492846
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7787
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>

commit 7cd32c18a11d0dfeb70c276b0185e21d06a71fa5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 19 13:29:06 2014 +0530

    tests: Use uniform timeouts
    
    Change-Id: I479ab941b3b2da3b16f624400fbd300f08326268
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7799
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c13c1fd5a487eeca269e8b62114f607487ee30f6
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Tue May 13 17:36:01 2014 +0530

    glusterd: Disable ping-timer between glusterd and brick process
    
    When there are too many IO happening, brick process epoll thread
    will be busy and fails to respond to the glusterd pick packet within
    30sec.
    Also epoll thread can be blocked by a big-lock.
    
    Solution is to disable ping-timer by default and only enable where ever
    required
    
    Later when the epoll thread model changed and made lighter,
    we need to revert back this change. http://review.gluster.com/3842 is
    one such approach.
    
    Change-Id: I7f80ad3eb00f7d9c4d4527305932f7cf4920e73f
    BUG: 1097224
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7753
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1dd80a2e7762bc72d11a432a1ebd16be181dcb86
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri May 9 15:01:19 2014 +0530

    rpcsvc: Validate RPC procedure number before fetch
    
    While accessing the procedures of given RPC program in,
    rpcsvc_get_program_vector_sizer(), It was not checking boundary
    conditions which would cause buffer overflow and subsequently SEGV.
    
    Make sure rpcsvc_actor_t arrays have numactors number of actors.
    
    FIX:
    Validate the RPC procedure number before fetching the actor.
    
    Special Thanks to: Murray Ketchion, Grant Byers
    
    Change-Id: I8b5abd406d47fab8fca65b3beb73cdfe8cd85b72
    BUG: 1096020
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/7726
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f4944449940ee08d8add767ba81cd5ca8f8611a5
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue May 13 17:42:14 2014 -0700

    api: non glibc c++ systems do not define __THROW
    
    Let __THROW be defined conditionally for more portability
    
    Change-Id: I6e7cb1eb59b84988e155e9a8b696e842b7ff8f7f
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7757
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 98f5f436dd9106819dea8bc6c9a42e03ee1e31be
Author: Anand Avati <avati@redhat.com>
Date:   Fri May 16 21:31:02 2014 -0700

    meta: add .file_write method into meta_ops
    
    Add .file_write method in meta_ops and make write support into
    virtual files (like loglevel, measure_latency) much simpler.
    
    Change-Id: I812f782f645605c56f81b158bb0f289b3c8f909a
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7785
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 618d465295df02ae6d53be1327947a210bb8b47d
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri May 16 16:58:20 2014 +0200

    NetBSD build fixes
    
    - Shell scripts: == is specific to bash and ksh. Use = instead.
    - Shell scripts: use sh instead of bash if bash functionnality is not used
    - Shell scripts: ${var/search/replace} is specific to bash
    - sed: The -i option is specific to GNU sed.
    - Makefiles: $< outside of generic rules only work in GNU make.
    - xdrproc_t() is not universally defined as variadic. Do not specify third
      argument if it is not used
    - NetBSD FUSE specific: only include <perfuse.h> in FUSE client code,
      it harms in other locations
    - configure: Search for gettext() in libintl as NetBSD stores it there
    - Like MacOS X, NetBSD has unmount(2) and not umount(2) (un vs u)
    
    Some other build issues previously included in this change were
    removed:
    - __THROW macro, addressed in http://review.gluster.com/#/c/7757/
    - getmntent() compat shared with MacOS X, in http://review.gluster.com/#/c/7722/
    
    This patchset adds warning fixes for mount_glusterfs
    
    BUG: 764655
    Change-Id: I2f1faf8ff96362d3e2baf237b943df619011f1f4
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/7783
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit aa85de4be3f96a140a69170330293bfdfa3d24e7
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu May 15 00:15:52 2014 -0700

    contrib: Cross platform fixes after recent commits
    
    - provide a getment_r () version which behaves as
      re-entrant with some caveats for NetBSD/OSX specific.
    - some apparent warning issues fixed, always use PRI* format
      specification avoid using %ld i.e not portable
    
    Change-Id: Ib3d1a73b426e38b436b356355b97db0104a1a4a5
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7722
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f4a391e5a44950b0468af082255b9f5abf52b10b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri May 16 15:41:33 2014 +0530

    cluster/afr: move messages to new logging framework
    
    Change important (from a diagnostics point of view) log messages to use
    the gf_msg() framework.
    
    Change-Id: I0a58184bbb78989db149e67f07c140a21c781bc2
    BUG: 1075611
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7784
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 6a9a52c932bc5be469af119e5b0b3afb8046f625
Author: Meghana <mmadhusu@redhat.com>
Date:   Mon May 12 12:26:18 2014 +0000

     Hooks:Modified S31ganesha-set.sh to enable dynamic exports via NFS-ganesha
    
     Dbus signals have to be sent to add and remove exports on the fly,
     without restarting nfs-ganesha server. Adding those signals in
     the hook script to enable the same.
    
     Adding another to check to enable IP modification,
     without restarting nfs-ganesha.Adding checks to find the
     configuration file in /etc/glusterfs-ganesha.
    
     Removing nested volume set options. This introduces
     some issues that will be documented clearly.
    
    Signed-off-by: Meghana <mmadhusu@redhat.com>
    Change-Id: I28f7983f2d18529dc813ddc9773b33c6caee1ad4
    BUG: 1095656
    Signed-off-by: Meghana <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/7709
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 05a5ffe97222ca7c49828f0d762a47e85411ab61
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 15 14:40:16 2014 +0530

    tests: Wait for nfs export to be available
    
    Change-Id: I59a5e0cb78f2b670761a65272b8ab1d7bdb3668a
    BUG: 1092850
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7773
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 07e8f0226d5263501d2b23ed008c59ed45a5a5bd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri May 2 13:55:59 2014 +0530

    logging: Add extra logs to enable testing of log suppression
    
    Note:
    This patch may be reverted once the testing effort is complete,
    if desired.
    
    Change-Id: I840399c531a43049749073d4d59bc0c85f525be3
    BUG: 1075611
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7681
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 40c2808ebfd51bc0440683aac68b719c4c7a874c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 7 21:38:46 2014 +0530

    protocol/client,server: Suppress ESTALE logs
    
    Change-Id: I5c5e016138be2417eacf81812313dc854907fa47
    BUG: 1095256
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7696
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit a20b6b473bf72224b0ea7752987d47d44b8b633c
Author: Kotresh H R <khiremat@redhat.com>
Date:   Thu May 15 12:52:22 2014 +0530

    gsyncd/geo-rep: Fix remote vol info fetching for non-root
    
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    
    Change-Id: If1d2cab3fcfe2391105551e54f0b9729a7c204e4
    BUG: 1077452
    Reviewed-on: http://review.gluster.org/7767
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 745347c8a2374442b8be69c7245d585289541e1b
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed May 14 05:17:13 2014 +0000

    glusterd/snapshot: Putting back the missed_snaps_list code
    
    Setting of missed_snap_count was removed as part of an
    earlier patch. Putting back the code.
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    
    Change-Id: Ib6412d6100145e94d10f6f4a8a1fe4e645c1a69e
    BUG: 1097725
    Reviewed-on: http://review.gluster.org/7764
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit d1bf6eebb8da61aa22530a91ee168725efefe0bd
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon May 5 23:27:28 2014 +0000

    glusterd: Differentiate snap-volume directories properly.
    
    If /var/lib/glusterd is hosted on xfs system, the entry->d_type
    not showing the correct d_type owes to the restore path prematurely
    exiting. Hence checking entry->d_name to differntiate <snap-name>/info
    file, missed_snaps_list file and the <snap-name>/geo-replication
    directory, from the actual volume directories, without impacting
    the gluster volumes.
    
    Change-Id: I9a774a845282fe7cc697e37bbcf7c4545aee7678
    BUG: 1094557
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7680
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit eb04dab9992f8f5d4b2d45e1ca10032fededcff1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 29 05:49:21 2014 +0530

    cluster/afr: Fix bugs in quorum implementation
    
    - Have common place to perform quorum fop wind check
    - Check if fop succeeded in a way that matches quorum
      to avoid marking changelog in split-brain.
    
    BUG: 1066996
    Change-Id: Ibc5b80e01dc206b2abbea2d29e26f3c60ff4f204
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7600
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>

commit a9df8ccbd331e21bcbccf3abc65abe730d6f0489
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Wed May 14 11:28:15 2014 +0530

    libglusterfs: Use strncpy() instead of strcpy()
    
    Use secure strncpy() to copy the input data to static buffer
    and make sure to NULL terminate the copied buffer (if source
    buffer is longer than static buffer).
    
    Change-Id: If3564f1398c8eb92669d4bc92700bbdf6ee2278e
    BUG: 1097417
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/7759
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 09e9775127c7def49202e68c923e36a6032a3628
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon May 12 00:06:32 2014 +0000

    glusterd/geo-rep: Allow gverify.sh and S56glusterd-geo-rep-create-post.sh
    to operate for non-root privileged slave volume
    
    Mounting the slave-volume on local node, to perform disk checks
    in order to allow gverify.sh to operate for non-root privileged
    slave volume
    
    Allowing the hook script S56glusterd-geo-rep-create-post.sh
    to operate for non-root privileged slave volume
    
    Modified peer_add_secret_pub.in to accept username as argument
    and add the pem keys to the users's_home_dir/.ssh/authorized_keys
    
    Wrote set_geo_rep_pem_keys.sh which accepts username as argument
    and copies the pem keys from the user's home directory to
    $GLUSTERD_WORKING_DIR/geo-replication/ and then copies the keys
    to other nodes in the cluster and add them to the respective
    authorized keys. The script takes as argument the user name and
    assumes that the user will be present in all the nodes in the
    cluster. It is not needed for root.
    
    To summarize:
    For a privileged slave user, execute the following on master node as super user:
    gluster system:: execute gsec_create
    gluster volume geo-replication <master_vol> [root@]<slave_ip>::<slave_vol> create push_pem
    
    For a non-privileged slave user execute the following on master node as super user:
    gluster system:: execute gsec_create
    gluster volume geo-replication <master_vol> <slave_user>@<slave_ip>::<slave_vol> create push_pem
    then on the slave node execute the following as super user:
    /usr/local/libexec/glusterfs/set_geo_rep_pem_keys.sh <slave_user>
    
    BUG: 1077452
    Change-Id: I88020968aa5b13a2c2ab86b1d6661b60071f6f5e
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7744
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 48201f4faeef3602cb095bf47d14deebf91899ba
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sun May 4 01:34:08 2014 +0530

    gsyncd / geo-rep: Partial support for Non-root geo-replication.
    
    This patch enables geo-replication to be run as an unprivileged
    user. As of now, this is just the partial support, but is very
    close to achieve full functionality.
    
    Current limitation
    * Geo-replication executed Gluster CLI commands on the slave
      via SSH. On a non-root setup, Gluster CLI would run as an
      unprivileged user, failing to execute the command. As a
      workaround (for testing), setuid(2) Gluster CLI executable
      or use the glusterd option to accept commands by unprivileged
      CLI process. The nature of cli commands are "system::"
      commands (for key management) and remote volume info fetching.
    
    Remote volume info fetching has been modified to use --remote-host
    gluster cli option rather than ssh and remote cli execution.
    
    Change-Id: Ica89e2ba9b7f48fd6e1c876c477d7822dc693617
    BUG: 1077452
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7658
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d2db585ce7e26851178104433fa9422482d8719e
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Feb 19 20:47:46 2014 +0530

    features/changelog : historical journal consumption.
    
    Facilitates Glusterfs with the ability to detect file-operations
    happened in past by scanning the back-end(brick-level) glusterfs
    journal (changelog).
    
    Design:
      * List of changelogs produces in one perfectly running session are
        stored in htime file which also holds necessary information about
        the session start and end time.
      * Involves fixed sized seeks to identify N'th changelog in the list.
      * Requires O(log n), (where n is number of changelogs in the list),
        time to identify the end changelog for the given start-end time
        interval.
    
    Currently the background processing of changelogs is sub optimal. BZ
    1097041 tracks the development effort.
    
    For complete design, refer the below link:
    http://lists.nongnu.org/archive/html/gluster-devel/2014-02/msg00206.html
    
    Change-Id: I27e49f75e492e843084d0ecaf9130224d08462a0
    BUG: 1091961
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6930
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bfde478cedda8267134ee3807c8db5e042115eae
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon May 12 11:22:36 2014 +0530

    glusterd: Allow setting volume options by default based on op-version
    
    A new function glusterd_enable_default_options is introduced, which will
    set some volume options on a volume based on op-version. This function
    is called near the end of the volume create and will allow some options
    to be enabled based on op-version on newly created volumes. This will
    also be called during volume reset, to reset the options to their
    default values if they had changed.
    
    Change-Id: I91057d9e42409b17a884728b43ae3721328d4831
    BUG: 1096616
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/7734
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 5c65850c99829668ac199a49a0760443db74b581
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri May 2 13:09:03 2014 +0530

    geo-rep/glusterd: Pause and Resume feature for geo-replication
    
            This patch introduces pause and resume cli command
            for geo-replication.
    
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    
    Change-Id: I4f5e58e9175fe85077d56088473252391fb57de7
    BUG: 1093602
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7643
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 7d22fca1f5c9d792b148bae15e8d26a9c5d63efa
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon May 12 07:54:59 2014 +0530

    glusterd/snapshot : Quorum check should not be made if we
    perform snapshot status command.
    
    Problem : Snapshot status command used to fail as it used to
    hit the quorum check path.
    
    Solution : The condition checking where snapname is fetched
    based on the presence of snap_volume is moved inside create
    switch case.
    
    And also moved the chunk of code which does the actual
    quorum check to new function to make the code more
    readable.
    
    Change-Id: Idda2d7c576cdfab3a7d087bfa74bfa616372c20e
    BUG: 1096700
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7737
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit ba9aec54be5b8f00125ad018618a86de769fb6b5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue May 13 11:56:50 2014 +0530

    geo-rep: Changelog History API changes
    
    Additional argument added to API gf_history_changelog,
    actual_end - The end time till where changelogs are available.
    
    Added sort to history_get_changes API output.
    
    BUG: 1091961
    Change-Id: Id043409882a83cd0a7b9adc3d34d5147d17e532e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7747
    Reviewed-by: ajeet jha <ajha@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit e64dd0a358e7a7b4c0da86a6b17adf6f125c00d5
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Apr 30 11:12:40 2014 +0530

    glusterd : barrier enable/disable should fail if already enabled/disabled
    
    In barrier notify function, if we fail to set the barrier option execution goes
    to default_notify which returns 0 and command returns success.
    
    Fix : We need not call the default_notify function when handling
    GF_EVENT_TRANSLATOR_OP in barrier xlator's notify.
    
    Change-Id: Ia2c361b43cca7791c29829d69dcd6fc7923102f6
    BUG: 1092841
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7609
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 4f905163211f8d439c6e102d3ffd1bffb34f5c26
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed May 7 18:17:11 2014 +0530

    glusterd: On gaining quorum spawn_daemons in new thread
    
    During startup, if a glusterd has peers, it waits till quorum is
    obtained to spawn bricks and other services. If peers are not present,
    the daemons are started during glusterd' startup itself.
    
    The spawning of daemons as a quorum action was done without using a
    seperate thread, unlike the spawn on startup. Since, quotad was launched
    using the blocking runner_run api, this leads to the thread being
    blocked. The calling thread is almost always the epoll thread and this
    leads to a deadlock. The runner_run call blocks the epoll thread waiting
    for quotad to start, as a result glusterd cannot serve any requests. But
    the startup of quotad is blocked as it cannot fetch the volfile from
    glusterd.
    
    The fix for this is to launch the spawn daemons task in a seperate
    thread. This will free up the epoll thread and prevents the above
    deadlock from happening.
    
    Change-Id: Ife47b3591223cdfdfb2b4ea8dcd73e63f18e8749
    BUG: 1095585
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/7703
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 5adb10b9ac1c634334f29732e062b12d747ae8c5
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed May 7 14:05:31 2014 +0530

    libgfapi:  Added support to fetch volume info from glusterd and store in glfs object.
    
    Defined new APIs in the libgfapi module, given a glfs object,
     * to send handshake RPC call to glusterd process to fetch UUID of the volume
     * store it in the glusterfs_context linked to the glfs object.
     * to parse UUID from its cannonical string format into 16-byte array
       before sending it to the libgfapi users.
    
    Defined a RPC call in glusterd which can be used to query volume related
    info by other processes using 'clnt_handshake_procs'.
    
    Note - Currently this RPC call to glusterd process is used only to fetch UUID.
    But it can be extended to get other volume related structures as well.
    
    In addition to the above, defined a new variable to keep track of such handshake
    RPCs still in progress to make sure all the corresponding RPC callbacks have been
    processed before libgfapi returns the glfs object initialized.
    
    Also bumping up the GFAPI current version number since there is a new API
    "glfs_get_volume_id" defined and exposed by libgfapi as part of these changes.
    
    Change-Id: I303f76d7177d32d25bdb301b1dbcf5cd73f42807
    BUG: 1090363
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/7218
    Reviewed-by: Anand Avati <avati@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2fd499d148fc8865c77de8b2c73fe0b7e1737882
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Apr 17 18:32:07 2014 +0200

    rpc: implement server.manage-gids for group resolving on the bricks
    
    The new volume option 'server.manage-gids' can be enabled in
    environments where a user belongs to more than the current absolute
    maximum of 93 groups. This option triggers the following behavior:
    
    1. The AUTH_GLUSTERFS structure sent by GlusterFS clients (fuse, nfs or
       libgfapi) will contain only one (1) auxiliary group, instead of
       a full list. This reduces network usage and prevents problems in
       encoding the AUTH_GLUSTERFS structure which should fit in 400 bytes.
    2. The single group in the RPC Calls received by the server is replaced
       by resolving the groups server-side. Permission checks and similar in
       lower xlators are applied against the full list of groups where the
       user belongs to, and not the single auxiliary group that the client
       sent.
    
    Change-Id: I9e540de13e3022f8b63ff893ecba511129a47b91
    BUG: 1053579
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7501
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 47c33dd27150039a6e5e3295eacd8d2d5a7e0ce0
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue May 6 14:38:40 2014 -0700

    tests: min-free-disk test was incomplete
    
    - use '%' when we mean it for clarity
    - in bash we need to evaluate counter decrements
    
    Change-Id: Ibd17126945e8a335fa2671d658a2e0c71049fd1e
    BUG: 874554
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7687
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c7b0396f680863528248e6f5a162de47184b6c88
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Apr 29 12:14:24 2014 +0530

    geo-rep: Pause and Resume feature for geo-replication
    
    Changelog consumption/processing now happens in seperate process
    group than monitor. When monitor process group gets SIGSTOP all
    worker process, ssh, rsync will be paused except the changelog
    processing. When it gets SIGCONT it resumes its operation.
    
    Changelog agent runs as RepceServer, geo-rep worker communicates
    with changelog agent using RepceClient.
    
    Change-Id: I35c333e4d8b13d03a7808aed601960eef23cfa04
    BUG: 1093602
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7322

commit 65757e0f57f93103d87fdf9534c5ca25b66d14b7
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon May 5 11:04:00 2014 +0530

    geo-rep: Changelog History consumption more fixes
    
    Number of parallel threads to process changelog history
    is made configurable via sync_jobs
    
    Change-Id: Idcd8e655d9df540cfa48648b9e98af941f95e9d0
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7660
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 93129e862a2dde291ddbf22fe30d955b25da6059
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu May 8 16:54:00 2014 +0530

    geo-rep: Loading libgfchangelog.so only while running geo-rep
    
    In source install, libgfchangelog is installed in /usr/local/lib
    When glusterd runs /usr/local/libexec/glusterfs/python/gsyncd --version
    it fails to find library without LD_LIBRARY_PATH.
    
    This patch avoids loading library when it is run from glusterd
    during start.
    
    BUG: 1096026
    Change-Id: I59912227ac27ff4877d947a7c8f1fe2e8c5be06e
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7713
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 26a4b5c98e9e50ace28a9bed97f04ecea262e11d
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Apr 29 00:14:54 2014 +0530

    mgmt/glusterd: delete oldest snapshot upon exceeding soft-limit
    
    Change-Id: I2d6ebae3ced1910f2dee43eeb9fc430e9f31073f
    BUG: 1061685
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7587
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit d74c10603196a57c5fa033aaeb55f93f7ef7b4be
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon May 5 14:34:55 2014 +0530

    glusterd/snapshot: volume gets deleted if restore fails
    
    If the restore command fails in pre-validate phase
    then main volume gets deleted.
    
    Fix: Perform cleanup only when pre-validate passes.
    
    Change-Id: I7128c8582c3dd166a5683babb7e136ad0b56f0ac
    BUG: 1061685
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/7665
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 26043d1f8ed6892aca47abcb75cedfdc51e86a0a
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Tue May 6 14:56:23 2014 +0530

    glusterd/snapshot: Don't release big_lock before completing snapshot creation
    
    Releasing the big-lock can cause problem like deadlock or memory
    corruption.
    
    Same happened with bug 1091926 where glusterd on node-2 entered a commit
    phase and released a big-lock.
    
    The originator node received timeout for the commit phase and
    triggered a post-validate cleanup to the node-2.
    
    Now node-2 continued to work with the object that are alreday cleaned-up
    and resulted in a crash.
    
    Solution is to not to release big-lock in the commit phase of snapshot
    creation.
    
    Change-Id: I571194fdb0b0ecc91bd13f2a9fc92fe4338d14dc
    BUG: 1091926
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7579
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 5dda1d4e00b8235656b7e4e8de35f599bf033148
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Mon May 5 12:43:26 2014 +0530

    glusterd/snapshot: Execute lvm snapshots in parallel
    
    Back-end LVM Snapshot is executed parallely as synop task
    This helps is gaining performance when there are more bricks in a
    node.
    
    This patch also removes unwanted logs printed in snapshot cleanup
    
    Change-Id: I3174cb4547ebb670eca37a98eb9d75ecb0672a90
    BUG: 1061685
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7461
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 065b91b4993f1ab0abc8b1db4d5745a6b58545b0
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Tue May 6 14:32:28 2014 +0530

    glusterd/snapshot: Add brick-count suffix for the LVM snapshot
    
    When there are more than one brick created from the same LVM volume
    group, there will be a conflict with the LVM snapshot name we use.
    
    Solution is to add a brick-count suffix to the LVM snapshot name
    
    Change-Id: I7258e69fe0b50e86b81c66ab1db523ab3c7cbae0
    BUG: 1091934
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/7581
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 4f8c7cc34dad6a963f70dfcf11e737fd44c31a42
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sun May 4 01:04:11 2014 -0700

    runtime: Disable optimization for OSX versions < 10.9
    
    Optimization flags has led to segfaults at wrong locations
    throughout gluster code for versions < 10.9
    
    Assuming this to be a compiler bug, disable optimization
    flags
    
    Change-Id: Ia2dc983dc5bb06935f03b68c07688ce41255d7da
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7656
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>

commit 75baf16c01b7cc09fbf14e3c9ecf447c3c793c5b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed May 7 09:59:56 2014 +0530

    Update Maintainers to reflect recent changes
    
    Change-Id: I8dc3347d88942473810c2b4c9d52a69ecb6129e8
    BUG: 1040351
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/7689
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>

commit 1b042296ddc65f5eab9d6e5f1e30e353413d9bbb
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 5 09:18:35 2014 +0530

    cluster/afr: Remove stale index in self-heal codepath
    
    Change-Id: I635fc0fa955b33590f1c5b4dfec22d591ea8575c
    BUG: 1032894
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6592
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 933f60796d69686a153659c7b178dbd1475f9cb6
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed May 7 18:03:34 2014 +0530

    libgfchangelog: memory accounting intialization
    
    Needed as memory accounting turned ON by default now.
    Without this, GF_{CALLOC,MALLOC} calls assert.
    
    Change-Id: Ie54a6efb61871e70d4f7c796d9c86a867051e2e0
    BUG: 1094708
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7698
    Reviewed-by: Kotresh HR <khiremat@redhat.com>

commit 281d95cb7d53069158eae99392e9e7863c8850fd
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 5 11:29:12 2014 +0530

    mgmt/glusterd: Prevent spurious brick restarts
    
    Change-Id: I7ee5d18b926d6c31e3e4ea2f5fbe9050c8e1dee8
    BUG: 959986
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4954
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit a4b622e0bd60a5e19e73f415a6a64aa6661a971a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon May 5 11:28:25 2014 +0530

    mgmt/glusterd: Perform Pending quorum actions after Op
    
    Change-Id: I2bb67b5fb4a6f6dac892ef3206e7a79706018a6e
    BUG: 959986
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4955
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit e80daecc3dd3023f010c785ff0e238fc92214477
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue May 6 04:19:48 2014 +0000

    glusterd: Use a calloc-ed copy of txn_id for glusterd_do_replace_brick
    
    As glusterd_do_replace_brick() is spawned through gf_timer_call_after(),
    by the time it's called the event is freed, and the txn_id is lost.
    Hence using a calloc-ed copy, which will be freed as a part of rb_ctx
    dict.
    
    Change-Id: I3e309fe1a7ba96ad1d1ce01f4d2aa18178f59244
    BUG: 1095097
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7686
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit b47b46d98a5e1d3e6e9eb9bde4f81b745f2ac09d
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Apr 14 11:24:12 2014 +0530

    mgmt/glusterd: quorum check before taking the snapshot
    
    without force option:
    quorum fails if glusterds are not in quorum. If glusterd are in quorum, then
    volume quorum (i.e quorum of the bricks) is checked. volume quorum fails even if
    one of the bricks are down.
    
    with force option:
    even though the glusterds are not in quorum, and some bricks are down, the
    quorum check of the volume (i.e bricks) is done and if the volume quorum is
    met, snapshot is taken.
    
    Change-Id: I06971e45d5cf09880032ef038bfe011e6c244268
    BUG: 1061685
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7463
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit eeb4434d6196735323fa28cfd19b5f7b36e1f664
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat May 3 14:52:11 2014 -0700

    glusterd: NFS server wrongly started with `DEBUG` log-level
    
    Disable DEBUG
    
    Change-Id: I011231ba3df4a42f892f1305867bfc74bb101269
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7654
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b8cd471dbaadfa6ff9a92789f8fd670c144f9e9e
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue May 6 16:04:43 2014 +0530

    gsyncd / geo-rep: Initialize default memory accounting
    
    commit 7fba3a8 enables memory accounting by default. Since
    geo-replication binary (gsyncd) does not declare a memory
    accounting function, call like GF_{CALLOC,MALLOC} result
    int asserts.
    
    This patch initializes default memory accounting.
    
    Change-Id: I9ad1de8bca6745a9899a006a863a7cfeef73d52f
    BUG: 1094708
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7683
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 199435aac3be170f6dadd4e88a576cec808ee419
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Sat May 3 12:52:44 2014 +0530

    glusterd : Port glusterd sync log messages to gf_msg API
    
    Change-Id: Ic3ed2c96d8fc3a15fedaa80517a2c79c0c858963
    BUG: 1075611
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7652
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 451246a58dbbc1ec777f379a6b779be374379abd
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri May 2 15:09:25 2014 +0530

    glusterd: port network failure log messages to gf_msg API
    
    Change-Id: I23df6d179e9d66a71721e9844a34c5b96586f90f
    BUG: 1075611
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/7462
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit f9672386ac2e3da2dc5439eb0a3a53dfaa5181dd
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 28 13:17:22 2014 +0530

    glusterd: Port server quorum messages to the gf_msg API
    
    Change-Id: I84716cc07f3cbd8c1b2825a5676d6693fed6fade
    BUG: 1075611
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/7578
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 05d084b93f76475c86c9c445f92c43bbd2b52569
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon May 5 15:51:18 2014 +0530

    rpc: don't stop sending ping packets to an active server.
    
    - Removed an unnecessary ref on rpc_clnt object.
    - Removed saved_frames_delete function, which was unused.
    
    Change-Id: Ie8a9c4bb20c1fd59744b64b56eb043eca095e5e3
    BUG: 1094655
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/7678
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Raghavendra G <rgowdapp@redhat.com>

commit fb173e9a10d62d49cc8b57c6b3c5bbdf1b326c18
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Apr 29 19:12:20 2014 +0530

    glusterd: Allow bumping up the cluster op-version
    
    This patch allows a user to bump up the cluster op-version by doing
      # gluster volume set all cluster.op-version <OP-VERSION>
    
    The op-version will be bumped only if
    - all the peers in the cluster support it, and
    - the new op-version is greater than the current cluster op-version
    
    This set operation will not do any other change other than changing and
    saving the cluster op-version in the glusterd.info file. It will NOT,
    - change any existing volume
    - add the option to the global options list
    - fix the cluster op-version to the given version, it can be bumped up
      by other volume set commands.
    
    Change-Id: I084b4fcc45e79dc2ca7b7680d7bb371bb175af39
    BUG: 1092592
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/7603
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 86fccad56d2ffd6c65e1571ff87dbf625b8ce55e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Apr 22 10:27:23 2014 +0000

    glusterd/snashot: Perform missed snap creates
    
    When a brick is started, and the glusterfsd process requests
    for volfile, the brick_name is sent in the req dict. In
    glusterd, after fetching the spec the brick_name is looked
    up in the missed_snap_list, and any missing snap creates on
    the same brick are performed. After this, the glusterd
    responds back with the specfile.
    
    Also collate brick data from the node's hosting the bricks
    during restore. In case the data is absent, the local node's
    data is used. This is needed to ensure that, during a restore
    we collect the information created when a missed snap create
    is performed.
    
    Change-Id: I47cefdeba96f2702be810965734cf0fac61d3d2d
    BUG: 1061685
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7551
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit f846e54b8844decbc8bd73840e7d35b2dcaed2e0
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Apr 23 04:26:24 2014 +0000

    glusterd: Fetch brick mount_dirs during brick create.
    
    Fetch the mount directory path for a brick, during
    volume create, add-brick, and replace-brick.
    
    When a snap-create is missed, use this mount directory
    information to create the brick path for the missed snap brick.
    
    Change-Id: Iad3eec96a32cf340f26bdf3f28e2f529e4b77e31
    BUG: 1061685
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7550
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit a05c579f1c3695c4ddead0a5cfc2c92422bd4f8f
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat May 3 13:25:41 2014 -0700

    meta: print in json for stack/frames, cmdline and version
    
    - Follow formatting rules based on RFC4627 -
      http://www.ietf.org/rfc/rfc4627.txt
    - Add checks for json in regression test meta.t
    
    Change-Id: I480d32ce042b202d3ed8939623c629a03b458551
    BUG: 1089216
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7653
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f01626d5bad8eb0298897e90a124301008cdd0da
Author: Anand Avati <avati@redhat.com>
Date:   Sat Mar 29 06:01:36 2014 -0700

    meta: export process state dump
    
    Various parts of process state dump are exposed
    through most appropriate virual files/dirs
    
    Change-Id: Iff30f8ea76552f2f6d9c98def688c5ec4bc6f2af
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7542
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit 8160399a36eff62a49a066f16dea9140d877c5e8
Author: Anand Avati <avati@redhat.com>
Date:   Wed Mar 26 11:52:53 2014 -0700

    meta: (re-)Implement Meta translator
    
    The meta translator exposes details about glusterfs itself
    in the form of a virtual namespace.
    
    Loading the translator on the client side creates the
    meta virtual view under $mntpoint/.meta by default. The
    directory is not listed (even with ls -a) and can be
    accessed by doing a "cd /mnt/.meta"
    
    Change-Id: I5ffdf39203841a9562a8280a1f79dc76d4dded5d
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7509
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit 7fba3a88f1ced610eca0c23516a1e720d75160cd
Author: Anand Avati <avati@redhat.com>
Date:   Sat Mar 29 06:59:39 2014 -0700

    mem-accounting: enable memory accounting by default
    
    memory accounting are constant time operations which
    involve a few pointer dereferences and integer increments
    (no loops or searches etc.)
    
    benefits of having memory usage info outweigh the minor
    accounting overheads
    
    Change-Id: If9bc6db5ffd0e00f0fd64b2f6eed094bf3543996
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7543
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit 71ad38b3f86bdb0c4e9120b58ff451a6711ead9d
Author: Anand Avati <avati@redhat.com>
Date:   Sat Mar 29 06:48:52 2014 -0700

    mem-accounting: store type string and print in meta
    
    Change-Id: Ied1de473c72967110b54f033768f7ac60bf66edc
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7541
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit 9021be1fc1a9460438ce74dc5df091834a0bdae0
Author: Anand Avati <avati@redhat.com>
Date:   Sat Mar 29 04:45:17 2014 -0700

    statedump: strfd based APIs
    
    Expose strfd based APIs for extracing various types of xlator
    state information.
    
    Change-Id: Ibbb6594b6fb31206bc6a1b1ea6514ed41889583b
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7540
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit 3a35f975fceb89c5ae0e8e3e189545f6fceaf6e5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 1 10:29:54 2014 +0530

    mgmt/gluster: Use fsync instead of O_SYNC
    
    Glusterd uses O_SYNC to write to temp file then performs renames
    to the actual file and performs fsync on parent directory. Until
    this rename happens syncing writes to the file can be deferred.
    In this patch O_SYNC open of temp file is removed and fsync of the
    fd before rename is done.
    
    Change-Id: Ie7da161b0daec845c7dcfab4154cc45c2f49d825
    BUG: 908277
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7370
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4cf348fcb683ff8c5b85233610dc9aa8835bd532
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 2 15:36:14 2014 +0530

    glusterfs.spec: Add missing files in %files section
    
    Thanks to Niels for all the help in finding RCA.
    
    Change-Id: I5678c53a5c04de18ccd676fbaf5bf8b0c77c9c14
    BUG: 1080970
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7645
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d5918849bebc8df85b017e3eddefaef69f008889
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat May 3 16:17:04 2014 -0700

    changelog: in C99 `inline` shouldn't be part of function definition
    
    - C99 standard dictates that `inline` should be used only to hint
      function implementation not as a definition
              - http://clang.llvm.org/compatibility.html#inline
      This also leads to run time issues as 'undefined symbols'
    
    - Remember to use adding explicit headers when using an external
      function
    
    Change-Id: I66a9030da7ac38ded6e0b6a977182be977382fa2
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7655
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit aea76f0ec5ca01fd10810d704e5ad00cb4eba2fc
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat May 3 00:02:03 2014 -0700

    glusterd/snapshot: umount2 on OSX/NetBSD is unmount
    
    Change-Id: I8de4d47bb2a54b915243ea029cce2585fba34876
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7651
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 853d198e8e4e4aa5ef933432480b585ebd836533
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Apr 25 01:26:30 2014 -0700

    glusterd: Allow symlink parent for snap_mount_folder
    
    If '/var' is a symlink which is on OSX, 'glusterd'
    initialization fails which is not necessary fix it.
    
    Change-Id: I83adc16cfc0e0deaa18acf74ba99299ba4a21d60
    BUG: 1061685
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7558
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 49d235361cb42746329453121e83beeb7fe611e5
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri Apr 25 18:04:08 2014 +0530

    protocol/server: Validate outstanding-rpc-limit
    
    server.outstanding-rpc-limit by passes validation enforcement of gluster
    as protocol/server ignores any keys starting with rpc (rpc* wildcard).
    Which also causes a side effect, i.e. help text gets displayed as NULL.
    
    Change-Id: I925e028529d671e1e29a0c7ff7e625fdb49a1be4
    BUG: 1091364
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/7562
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e73fc9939aecfa9f7955653d02f12243aba02fc6
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Tue Apr 8 17:10:25 2014 +0530

    glusterd : Volname, brickpath & volfpath length validation
    
    While creating a volume and adding a brick validation for _POSIX_PATH_MAX is
    done on absolute pathname instead of relative pathname due to which a brickpath
    having less than _POSIX_PATH_MAX may also fail the validation if the directory
    length is greater than (_POSIX_PATH_MAX -strlen(brickpath/volume name).
    
    Also this fix addresses one cli response message correction which says the
    volume file is too long instead of brick path is too long (when brickpath
    length validation doesn't fail and vol file length validation fails.)
    
    It is also important to note that with the current design of volfile naming, it
    can not be guranteed that volname and brickpath can have max of _POSIX_PATH_MAX
    characters.
    
    Change-Id: I1283d1f9dea96ae797620002c8723719f26a866d
    BUG: 1085330
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7420
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c6f4504c12d35359986a08da222193057946570a
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Apr 15 17:48:16 2014 +0530

    mgmt/glusterd: handle postvalidate carefully when prevalidate fails
    
    * Also changed the order of peers retrieval and snapshot retrieval
      upon glusterd start, so that the snapshot bricks can be properly
      resolved while cleaning up the snapshots.
    
    Change-Id: I120704e4412a9cadb8d90a9b7969f2b4a1196bc5
    BUG: 1061685
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/7494
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 03c9c5db7259ea83161b2bd841f93c9f0688106e
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu May 1 17:42:19 2014 +0530

    barrier : fsync call over NFS should be barriered when barrier is enabled
    
    barrier_fsync was not getting hit when fsync call is issued from the
    application over NFS mount.
    Investigation reveals that NFS doesn't send an explicit fsync call to the
    glusterfs server, however NFS converts it with a stable write with O_DSYNC
    flag, so for a fsync call over NFS mount point, barrier feature always
    needs to check for writev and its correspoding flags. So to meet all the
    coditions of write with O_SYNC and fsync getting blocked when barrier is
    enabled the check has been modified with following:
    
          if (!((flags | fd->flags) & (O_SYNC | O_DSYNC)))
    
    Point to be noted here is we need to check both fd's flag and the explicit
    flag  as for NFS write fd->flags is 0.
    
    Bug ID : 1091902
    Change-Id: Ifd5377fca2cc93bb72158dd525b2aab8b4164ca8
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7633
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 11b0ea3d79445e3773d450132121387b67d7bc9a
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Apr 23 17:21:41 2014 +0530

    barrier : barrier O_SYNC write incorrect flag check
    
    barrier_writev function was doing the following check to determine whether its a
    O_SYNC write or not:
            if (!(flags & O_SYNC))
    The problem here is this flag is not fd's flag and gfapi write does not copy
    open call fd's flag into write flag because of which O_SYNC writes were not
    getting barriered even if barrier was enabled.
    
    The check has been modified as:
            if (!(fd->flags & (O_SYNC | O_DSYNC)))
    
    Change-Id: I07b23852d150b81c7317100ca6d22d082ad897cd
    BUG: 1090488
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7549
    Reviewed-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0088e318c1218191535ea0baa04b4fe858412f54
Author: Meghana M <mmadhusu@redhat.com>
Date:   Mon Mar 24 13:58:38 2014 +0530

    cli/hooks : Add volume set options to enable/disable nfs-ganesha support.
    
    1. gluster volume set nfs-ganesha.enable ON/OFF
    If the option is set to ON, the volume field in the nfs-ganesha configuartion file is
    edited. Gluster-nfs is disabled on that volume and the volume is exported using
    nfs-ganesha.
    
    2.gluster volume set nfs-ganesha.host IP
    This is used to provide the IP of the nfs-ganesha host.
    
    Note : nfs-ganesha.host MUST be set before using nfs-ganesha.enable ON
    
    The switch from gluster-nfs to nfs-ganesha is mostly done by the hook-scripts
    in the post phase of the 'set' option. As a result, gluster volume reset does not
    function as it is expected to. By default, nfs-ganesha will be set to off but the
    process  will not be killed.
    
    Hence, a few changes have to be made post 'reset' option as well. Those changes
    also have been added.
    
    Change-Id: I7fdc14ee49d1724af96eda33c6a3ec08b1020788
    BUG: 1092283
    Signed-off-by: Meghana <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/7321
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 66f560e0071db84d430f38b996364f6b8c4f0f6d
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Wed Apr 23 18:36:34 2014 +0530

    glusterd/snapshot: Restore cleanup
    
    If restores fails for some reason then we should revert
    the restore operation. To do so we take the backup of
    vols folder before doing a restore and if the restore
    fails then we revert the changes done.
    
    Change-Id: I97f72aec3a34fc122bf137beb336e94db3a04dff
    BUG: 1061685
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/7548
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f48656b32e328f96bda5aade55070867d5faf333
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Apr 29 14:28:29 2014 +0530

    extras/hookscripts: Remove %P from smb share path value.
    
    We had added %P in the value for path in smb share definitions to
    avoid ctdb errors. However, %P does not work well for windows
    clients and they fail to access the share.
    
    Solution for the original problem:
    The error messages were being generated by a monitoring script that ctdb
    runs. The script reads the path value from testparm and tests if it exists
    in the local machine. This particular check does not hold valid for
    virtual file system backends like gluster. There is no harm in asking
    ctdb to not to check the existence of such backend and can be done by
    setting the following config in ctdb.conf:
    
    CTDB_SAMBA_SKIP_SHARE_CHECK=YES.
    
    Change-Id: I91627c8a279126a5cc24c6347847f9bfbad53dd5
    BUG: 1068776
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/7598
    Reviewed-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit c7838fbd6afd876c922e1ec681bbbcf73be653e5
Author: Xavier Hernandez <xhernandez@datalab.es>
Date:   Thu May 23 11:13:25 2013 +0200

    storage/posix: do not dereference gfid symlinks before posix_handle_mkdir_hashes()
    
    Whenever a new directory is created, its corresponding gfid file must
    also be created. This was done first calling MAKE_HANDLE_PATH() to get
    the path of the gfid file, then calling posix_handle_mkdir_hashes() to
    create the parent directories of the gfid, and finally creating the
    soft-link.
    
    In normal circumstances, the gfid we want to create won't exist and
    MAKE_HANDLE_PATH() will return a simple path to the new gfid. However if
    the volume is damaged and a self-heal is running, it is possible that we
    try to create an already existing gfid. In this case, MAKE_HANDLE_PATH()
    will return a path to the directory instead of the path to the gfid.
    
    To solve this problem, every time a path to a gfid is needed, a call to
    MAKE_HANDLE_ABSPATH() is made instead of the call to MAKE_HANDLE_PATH().
    
    Change-Id: Ic319cc38c170434db8e86e2f89f0b8c28c0d611a
    BUG: 859581
    Signed-off-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-on: http://review.gluster.org/5075
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dd5e318e020fab5914567885c1b83815b39d46f9
Author: ggarg <ggarg@redhat.com>
Date:   Mon Apr 21 18:59:00 2014 +0530

    glusterd: Differentiate rebalance status and remove-brick status messages
    
    previously when user triggred 'gluster volume remove-brick VOLNAME
    BRICK start' then command' gluster volume rebalance <volname> status'
    showing output even user has not triggred "rebalance start" and when
    user triggred 'gluster volume rebalance <volname> start' then command
    'gluster volume remove-brick VOLNAME BRICK status' showing output even
    user has not run rebalance start and remove brick start.
    
    regression test failed in previous patch. file test/dht.rc and
    test/bug/bug-973073 edited to avoid regression test failure.
    
    now with this fix it will differentiate rebalance and remove-brick
    status messages.
    
    Signed-off-by: ggarg <ggarg@redhat.com>
    
    Change-Id: I7f92ad247863b9f5fbc0887cc2ead07754bcfb4f
    BUG: 1089668
    Reviewed-on: http://review.gluster.org/7517
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0f56f0ce2d2e18fbb2eedf14e93b5a592f0005c3
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Apr 14 19:18:41 2014 +0530

    glusterd/snapshot: Activation and De-activation of snapshot
    
    Previously, snapshots by default were activated on creation and there was
    no option to activate or deactivate them on demand.
    
    This will allow the user to activate and deactivate on demand.
    The CLI goes as follows
    
    1) Activate the snap using a command "gluster snapshot activate <snapname> [force]"
    2) Deactivate the snap using a command "gluster snapshot deactivate <snapname>"
    
    Note: Even now the snapshot will be activated during creation.
    
    Change-Id: I0946d800780f26c63fa1fcaf29aabc900140448f
    BUG: 1061685
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/7476
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b189bb33edc2582e53923dec51bdef0f118c3d36
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon Apr 28 19:14:20 2014 +0530

    glusterd/snapshot: Move read-only xlator to client graph
    
    read-only xlator is moved from server graph to client graph
    so that AFR & DHT healing can take place at server
    
    Change-Id: I140ec962330c59d3b44f9bc8084a1544a1fd6c54
    BUG: 1061685
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/7582
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e14b100da9801f6f694763eae47e5412982856f0
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Apr 14 14:51:28 2014 +0530

    glusterd: avoid repetitive logging of disconnect messages
    
    NFS/SHD process disconnecting from glusterd, when the respective service
    are down, would lead to repeated logging of disconnect related messages,
    owing to the rpc reconnect logic in glusterfs(d). This patch addresses
    that by logging the disconnect only on the first disconnect event.
    
    Change-Id: I4008d2436721f4ba093270df4ccb3fc885f22ca0
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/7468
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4044e387dd40e2d12145fd32d5fd715406fcec8e
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Apr 26 01:29:46 2014 -0700

    scripts: CTDB lockvol ping-timeout should be 10secs
    
    Users often forget to update the ping-timeout, perhaps
    we should take care of this automatically
    
    Change-Id: I6d14df8aa52665847233cb1760dfd54f41baadec
    BUG: 1091600
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7569
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jose A. Rivera <jarrpa@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 936010740d45c1ecde4072cf5323e838c31bbbf0
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri May 2 09:48:31 2014 +0530

    features/changelog: Fix to remove Warning message.
    
            Fix warning message introduced in changelog
            draining patch. It is not caught in gcc 4.4,
            caught in gcc 4.8!!
    
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    
    Change-Id: I01a8fda2102a409dd6e935805d4d48b41b615fe8
    BUG: 1091817
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7636
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit b3031351b0e69195413f5f5b9cad2752e3eb713d
Author: Sachin Pandit <spandit@redhat.com>
Date:   Sat Apr 26 14:06:47 2014 +0530

    glusterd/snapshot : Copy the quota config and cksum file before taking a snapshot
    
    Quota config and cksum file needs to be copied before taking a
    snapshot, so that when a snapshot is restored these files is
    copied back to the original place, and the restored snap volume
    can make use of these quota files.
    
    Before taking a snapshot the quota files are copied to
    /var/lib/glusterd/snaps/<snapname>/quota/
    
    Change-Id: Id175f28d4ee47be64d7491c6aae81a1794928490
    BUG: 1061685
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7527
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d12a77cb3263f79f66f48a3b9205746b7d3b50f1
Author: Sachin Pandit <spandit@redhat.com>
Date:   Tue Apr 22 08:09:18 2014 +0530

    glusterd/snapshot : Copy geo-rep status and config files before taking a snapshot.
    
    geo-rep status and conf files needs to be copied before taking a snapshot.
    The idea here is, when the snapshot is restored, these config and status
    files needs to be placed back in geo-replication folder so that
    geo-replication can start with the same state it was when taking
    a snapshot.
    
    Details :
    Before a snapshot is taken, Copy the status and config files present
    in /var/lib/glusterd/geo-replication/.
    
    The files copied are gsyncd.conf and status files of each session
    belonging to a volume whose snapshot is about to be taken.
    
    Change-Id: I0234ecd846883350c59777c2505290729de0ce05
    BUG: 1061685
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7495
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3d4a31d304064f88d2d1e414346c790f099743b5
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jan 29 03:06:19 2014 +0000

    glusterd/geo-rep: Looks for state_file and pid-file in gsyncd_template.conf
    
    If entries like state_file or pid-file are missing in the gsyncd.conf
    or if the gsyncd.conf is also missing, glusterd looks for the missing
    configs in the gsyncd_template.conf
    
    status will display "Config Corrupted" as long as the entry is missing in
    the config file.  Missing state-file entry in both config and template
    will not allow starting a geo-rep session.
    
    However stop force will successfully stop an already running session,
    if the state-file entries are missing in both the config file and
    the template, as long as either of them have a pid-file entry.
    
    if the pid-file entry is missing in the gsyncd.conf file, starting a
    geo-rep session will not be allowed.
    
    if the pid-file entry is missing in an already started session, then
    stop force will fetch it from the config template and stop the session.
    
    if the pid-file entry is missing in both the config and the template,
    stop force will fail with appropriate error stating pid-file entry is missing.
    
    Change-Id: I81d7cbc4af085d82895bbef46ca732555aa5365d
    BUG: 1059092
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/6856
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4b5ad0d6510d88767762e9c2ef5d028b674a6765
Author: Kotresh H R <khiremat@redhat.com>
Date:   Tue Apr 8 13:50:30 2014 +0530

    features/changelog: Barrier in changelog during snapshot.
    
            Changelog barriers unlink, rename, rmdir fops on barrier 'on'
            notification from glusterfsd mgmt layer and unbarriers the
            same on barrier 'off' notification during snapshot.
    
            Please see the following link for more details.
            http://www.gluster.org/community/documentation/index.php/Changelog_Design_changes_for_snapshot
    
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    
    Change-Id: Iea9c62fafc86242f9404e03679b1941aa9c88c9a
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7415
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Varun Shastry <vshastry@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c523a04a0bd3edce9cf8ed238b838ebd957f1066
Author: Kotresh H R <khiremat@redhat.com>
Date:   Mon Mar 10 20:03:55 2014 +0530

    feature/changelog: Draining of in-transit fops in changelog.
    
            This is required for Geo-rep to work with snapshots.
            Following things are done in this patch.
            1. Draining of in-transit fops during changelog rollover.
            2. Explicit rollover of changelog when snapshot barrier
               notification comes. During this, intransit fops are
               drained and changelog is rolled over.
    
            For more details on the purpose of the patch. Please
            visit following link.
            http://www.gluster.org/community/documentation/index.php/Changelog_Design_changes_for_snapshot
    
    Change-Id: I22690131e19d3027f6d8957178bdc3431b9062f6
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7216
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Varun Shastry <vshastry@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 12f1fab930dc0f6f103bae03fab981409ed31b4e
Author: Sachin Pandit <spandit@redhat.com>
Date:   Wed Apr 30 00:41:56 2014 +0530

    glusterd/snapshot : Barrier code integration with snapshot codebase.
    
    As we have new barrier translator in place, we are making use of
    that during snapshot phase.
    
    During snapshot create (pre-commit), we enable the barrier feature
    and after the commit we disable it.
    
    Change-Id: I94212b1c06b0d9b12255ee98313e2d8549b34b17
    BUG: 1061685
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7561
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9934033030d3afa039c0686f77a4c00fad270131
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 30 03:31:06 2014 +0530

    mgmt/glusterd: Fix wrong usage of snprintf
    
    Change-Id: I7db752390bb742fb9f6cacce84563ff782ae352b
    BUG: 1087677
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7608
    Reviewed-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 889359f8456d8d1799ec66bf0e5506732c7907b9
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 30 03:05:48 2014 +0530

    storage/posix: Remove dead code in xattrop
    
    Change-Id: I48ba81ad342e3c8fe1d81f8e57e61676dd356fb0
    BUG: 1092749
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7318
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 15ea78fffd63756fecf2f15887d3cad6a13d2a34
Author: Anand Avati <avati@redhat.com>
Date:   Tue Apr 29 13:54:53 2014 -0700

    logging: use duplicate stderr, instead of re-opening
    
    The special filename "-" is supposed to log to stderr. Instead of
    trying to explictly open "/dev/stderr" again (which may not be possible
    as permissions might have changed by then), dup the stderr and use
    the copy.
    
    It is not a good idea to use @stderr global variable directly, as
    ctx->log.logfile is fclose()d in glfs_fini() (was fixed in
    http://review.gluster.org/6452)
    
    Change-Id: Ia6c538fe363905588dcf4fc4783804073956a586
    BUG: 1088589
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7607
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 630d46d714a233919664c035f2c5c48c028777e8
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Feb 7 11:02:10 2014 +0530

    logging: Introduce suppression of repetitive log messages
    
    Change-Id: I8efa08cc9832ad509fba65a88bb0cddbaf056404
    BUG: 1075611
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7475
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f63fbca7540a4c9ce090e1ed5941ed8777ff6316
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Apr 21 20:28:22 2014 +0530

    [glusterd/snapshot] snapshot create force option
    
    Implement force option in snapshot create i.e
    
    1) Creation of snapshot fails if the original volume
    bricks are down
    2) With a force option creation of snapshot will continue
    even if the original volume bricks are down.
    
    This was the fix for bugs 1089527 and 1083502
    
    Change-Id: I8de0242adf8ee0af00db9fa8701d86fabc12e7fc
    BUG: 1090042
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/7520
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 57fddef768d0e0feee07e5d745dcb4656fe5cb84
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Tue Apr 29 18:56:56 2014 +0530

    glusterd/snapshot : Fix for snapshot delete failure
    
    Problem : snapshot delete used to fail when executed in loop,
    as there was race between process kill and umount.
    
    Solution : Before an umount is issued check if the process
    is still running, If so then issue for process termination.
    Give three tries for doing umount operation
    
    Change-Id: I7f4315e5d7d4a156dd513ec77443ead6ccd37b2e
    BUG: 1090449
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7532
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit edc55a31f61e4e546d957019044fa8c8e1de4219
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Mon Apr 21 19:29:01 2014 +0530

    [glusterd/snapshot]: snapshot create CLI msg correction
    
    Uniformity in cli output while creating snapshots
    
    Change-Id: Ic0fd09bbde9a1f55c441e1745f93c588d2e4c1a1
    BUG: 1090041
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/7518
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 48043e3c11921a6cac532f2e56ccca6b72539dba
Author: Joseph Fernandes <josferna@redhat.com>
Date:   Thu Apr 17 19:42:06 2014 +0530

    [glusterd/snapshot] Glusterd crashes when a same command
    eg snapshot create is fired simultaneously on a node
    
    Cause: In glusterd_mgmt_v3_initiate_snap_phases() , the function
    glusterd_mgmt_v3_post_validate() asserts on the NULL value of
    req_dic. req_dic is not initialized as
    glusterd_mgmt_v3_initiate_lockdown() is not able to acquire the lock
    and comes to the "out" section, before initializing req_dic
    (via glusterd_mgmt_v3_build_payload)
    
    Fix: Call glusterd_mgmt_v3_post_validate() only if the lock is
    acquired.
    
    Change-Id: I7cb55b6c0013ad1c8bbb922a62c34aab097bafe9
    BUG: 1090047
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Reviewed-on: http://review.gluster.org/7500
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 45d70cc74828b636c0d3c8e388f5b111e1a563ad
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Feb 7 11:24:41 2014 +0530

    geo-rep: Consume Changelog History API
    
    Every time when geo-rep restarts it first does FS crawl using
    XCrawl and then switches to Changelog Mode. This is because changelog
    only had live API, that is we can get changes only after registering.
    
    Now this(http://review.gluster.org/#/c/6930/) patch introduces History
    API for changelogs. If history is available then geo-rep will use it
    instead of FS Crawl.
    
    History API returns TS till what time history is available for
    given start and end time. If TS < endtime then switch to FS Crawl.
    (History => FS Crawl => Live Changelog)
    
    If TS >= endtime, then switch directly to Changelog mode
    (History => Live Changelog)
    
    Change-Id: I4922f62b9f899c40643bd35720e0c81c36b2f255
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6938
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d09b327a2796152eb80074169e17359394ae7cf8
Author: Sachin Pandit <spandit@redhat.com>
Date:   Mon Apr 28 05:58:41 2014 +0530

    glusterd/snapshot : Clean up of old barrier code.
    
    As a new barrier translator is introduced, we dont require
    the old barrier code. Hence cleaning thar up.
    
    Change-Id: Ieedca6f33a746898f0d2332fda1f1d4c86fff98f
    BUG: 1061685
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7577
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e2034a84d284c37ade9f49be1589e3f53321bb23
Author: Sachin Pandit <spandit@redhat.com>
Date:   Thu Apr 3 10:00:04 2014 +0530

    snapshot/config : Fix for bug which states gluster snapshot config
    command should only accept the decimal numeric value.
    
    Syntax : gluster snapshot config [volname]
                                     [snap-max-hard-limit <count>]
                                     [snap-max-soft-limit <percentage>]
    
    Problem : Snapshot config used to consider the alphanumeric value
    staring with digit as an integer (Example: "9abc" is converted to "9").
    
    Solution : Refined the code to check if the entered value is numeric.
    
    This patch also fixes some of the minor problems related to snapshot
    config.
    1) Output correction in gluster snapshot config snap-max-soft-limit.
    2) setting the soft limit to greater than 100% displays that "Invalid
    snap-max-soft-limit 0". The error message used to display "zero" in
    the output, Changed this to display relevant value.
    3) Setting greater than allowed snap-max-hard-limit output needs to
    have space in between.
    
    Change-Id: Ie7c7045722fe57b2b3c50c873664b67c28eb3853
    BUG: 1087203
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7457
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4d9e0bf658cce3cf9f808bb6d0a4cb2d8c9ad504
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Apr 28 15:27:13 2014 -0700

    glusterd: make sure that mntent.h is conditionally included
    
    Change-Id: I39c362c0908166707e10e8820cc1ee9a0989dcbe
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7584
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 540065ba490339ce173552751953485fa32ed0bf
Author: Anand Avati <avati@redhat.com>
Date:   Sat Mar 29 04:54:16 2014 -0700

    strfd: introduce strvprintf() API
    
    variant of strprintf() which accepts va_list as parameter
    instead of variable args (...)
    
    Change-Id: I205acf3aaf5440890d5f9cad693c6a358a5d9218
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7539
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit c61bc1f9e5874cb8380ec6398680fc71aea233b4
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Apr 7 10:57:45 2014 +0530

    glusterd: Ping timer implmentation
    
    This patch refactors the existing client ping timer implementation, and makes
    use of the common code for implementing both client ping timer and the
    glusterd ping timer.
    
    A new gluster rpc program for ping is introduced. The ping timer is only
    started for peers that have this new program. The deafult glusterd ping
    timeout is 30 seconds. It is configurable by setting the option
    'ping-timeout' in glusterd.vol .
    
    Also, this patch introduces changes in the glusterd-handshake path. The client
    programs for a peer are now set in the callback of dump_versions, for both
    the older handshake and the newer op-version handshake. This is the only place
    in the handshake process where we know what programs a peer supports.
    
    Change-Id: I035815ac13449ca47080ecc3253c0a9afbe9016a
    BUG: 1038261
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5202
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 91ab65f812ec3b674f53230eacbd0d71964d3d01
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 19 07:52:48 2014 +0530

    storage/posix: add list xattr capability to lookup
    
    BUG: 1078061
    Change-Id: Ie26d28b8a74aa0d1eceff14a84c3cd3e302dcdb5
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7293
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b00ef83d2b15594526b1c58ef944a7edaa7e9dfe
Author: Varun Shastry <vshastry@redhat.com>
Date:   Fri Apr 11 17:31:32 2014 +0530

    feature/quota: Logging corrections
    
    This patch solves the inconsistent quota usage logging when soft limit reached.
    
    Change-Id: I47e7f1e65ed4b8306a999a20cc8f6b1772d47627
    BUG: 1087198
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/7451
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5e4a5a4c27f120102d4c2e3c7d558a20d838cf24
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Feb 11 10:07:24 2014 +0530

    cli: Add a cli command to enable/disable barrier
    
    This patch adds a new
     'gluster volume barrier <VOLNAME> {enable|disable}'
    cli command. This helps in testing the brick op code path when testing
    the barrier xlator.
    This patch can be reverted later if not required for end users.
    Change-Id: Icd86a2d13e7f276dda1ecbb2593d60638ece7dcd
    BUG: 1060002
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6958
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 16e71bf8b76eb421e30f5fe239601ba85710c983
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Feb 6 13:04:32 2014 +0530

    glusterd: Add a barrier brick-op
    
    This patch introduces a new 'barrier' brick-op which will be used to
    activate/deactivate the barriering on the bricks. This includes
    barriering in the barrier xlator and in the changelog xlator. All the
    required code has been including a bricks select function, a payload
    builder and a brick-op handler.
    
    Change-Id: I91d9d77f691c2e89823f7dc4e84900ec40dc4dd2
    BUG: 1060002
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6943
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 29af4da4b552442e487a898d0b3172a78da0c663
Author: Sachin Pandit <spandit@redhat.com>
Date:   Sat Apr 19 16:30:19 2014 +0530

    glusterd/snapshot : Dont acquire a lock if config is of
    type DISPLAY.
    
    Problem : Currently we are acquiring a lock if we give
    "gluster snapshot config <volname>". As this is just a
    Read-Only command, we need not acquire a lock.
    
    Solution : This patch checks if the command given is of
    type DISPLAY. If so, then glusterd_v3_mgmt framework is
    not called, as reading information from local node is
    enough.
    
    This Patch also fixes "Assertion failed: volname" while
    doing the system config change when snap create was in
    progress.
    
    Change-Id: Ie8991f2cd746987b11152006e113e8706516138b
    BUG: 1087677
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Reviewed-on: http://review.gluster.org/7458
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fe7d28e5981620f82447c264c00cf39e67f557cf
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Apr 25 10:14:14 2014 -0400

    build: glusterfs.spec.in, minor/nit changes to sync with Fedora spec
    
    minor/nit changes to sync with Fedora spec
    
    Change-Id: I939eb79d5c3a19c09a3df3f30c82c86e1a610cd0
    BUG: 1091408
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/7565
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 9dd643dc68bfc22f7244706717d7dcb4ab090f06
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Apr 28 10:59:04 2014 +0530

    logging: Fix msg-id segment allocation
    
    Change-Id: I85efa4b91c263d7374d34dd0d84e9f1032d07ab6
    BUG: 1075611
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7580
    Reviewed-by: N Balachandran <nbalacha@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4963ec017ef93b22e6c0b929b5fe0633f7010f45
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 29 06:05:46 2014 +0530

    debug/trace: Fix length issue found in compilation
    
    Change-Id: I1cd7fd6464d0912294009c2293ed70f3f6744930
    BUG: 1092196
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7586
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d960a4ac74fb695581a2a00080fab16f8886ea9e
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Apr 28 16:31:15 2014 -0700

    nlm: fix rpc.statd typo
    
    Change-Id: I701fd82a8dd5a72727b8035bc6c2861465f1aa1f
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7585
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit c85d842c615b65da7f692cef36b5b9f51c62a0ca
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Wed Apr 23 12:41:33 2014 +0530

    libgfapi: A minor bug-fix in glfs_h_setxattr and glfs_h_removexattr calls.
    
    Change-Id: I62f63da37edf722d6d79c75f72ee7403e93e4936
    BUG: 1089414
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/7529
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Meghana M <mmadhusu@redhat.com>
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 49e2d5162013ccf5f3f99c68c2521ca1cc6c3f20
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Apr 25 20:36:11 2014 +0530

    cluster/afr: Fix inode_forget assert failure
    
    Problem:
    If two self-heals are triggered on same inode in
    parallel then one inode will be linked and the other
    inode will not be linked as an inode with that gfid
    is already linked in inode table. Calling inode-forget
    on that inode leads to assert failure.
    
    Fix:
    Always use linked inode for performing self-heal.
    
    Added inode-forgets in other places as well even though
    its not really a memory leak.
    
    Change-Id: Ib84bf080c8cb6a4243f66541ece587db28f9a052
    BUG: 1091597
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7567
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3ea85192f1521c32915ed38bb4db61be11d59922
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 21 08:35:12 2014 +0530

    dict: de-allocate data on dict-set failures
    
    Found the bug while browsing code. Very difficult to hit this though.
    
    Change-Id: I84bd5d23d19b6aa16866fc0f1b56aa22cb8a5f1f
    BUG: 1079215
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7310
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c52ab5eb52519d41b0ae146ec7b1276f2ffae9e9
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Thu Apr 24 14:39:20 2014 +0530

    glusterd: Help does not show performance.nfs.* opt
    
    Gluster does not display performance.nfs.* options in help.
    
    In Gluster NFS, write-behind is the only performance xlator
    which gets loaded. Gluster volume set help should display all
    the options provided by write-behind xlator.
    
    Change-Id: I4a41151a6c15eeed8e8d123a6044c6f0c42b56b0
    BUG: 1090826
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/7546
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a3c12fdabea5ee77ab95bc65962e56083b7d0fa6
Author: ggarg <ggarg@redhat.com>
Date:   Fri Mar 28 12:23:17 2014 +0530

    cli: Error out when character "." is available in volume name
    
    previously it was failed without showing any information why it is failed.
    
    Now with this fix, when "." or any non alphanumeric character
    present in volume name, it will give error messages
    
    Change-Id: I17e8e69c08345c4d760f3ba333fe841e754bc9c8
    BUG: 921215
    Signed-off-by: ggarg <ggarg@redhat.com>
    Reviewed-on: http://review.gluster.org/7364
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f2bac9f9d5b9956969ddd25a54bc636b82f6923e
Author: Kotresh H R <khiremat@redhat.com>
Date:   Thu Feb 13 23:53:27 2014 +0530

    features/libgfchangelog: APIs to process history changelogs.
    
    1. Create directories in following fashion for history API's
       usage when consumer is registered with libgfchangelog
       shared library through gf_changelog_register.
           scratch_dir/.history
           scratch_dir/.history/.current
           scratch_dir/.history/.processed
           scratch_dir/.history/.processing
    
    2. Added new file 'gf-history-changelog.c' and following APIs
       are provided for consumers to process history changelogs.
    
        1. gf_history_changelog_scan:
                Move processed history changelog file from
                .processing to .processed
        2. gf_history_changelog_next_change:
                Return the next history changelog file entry.
                Zero means all history chanelogs are consumed.
        3. gf_history_changelog_done:
                Scan .processing directory and generate a list of
                change entries.
        4. gf_history_changelog_start_fresh:
                For a set of changelogs, start from the begining.
    
    NOTE: Though this patch provides above funcationalities.
          It is considered functionally full with the
          patch (http://review.gluster.org/#/c/6930/).
    
    Change-Id: I200780c7278e0a6c008910d93faad5858a4b3e76
    Original-author: Kotresh H R <khiremat@redhat.com>
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6998
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 54a5a42848870ee17b923c6c37d65fdfe4a5fec9
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Apr 22 00:52:57 2014 +0000

    glusterd/snapshot: Compare and update snapshots during peer handshake
    
    During a peer-handshake, after the volumes have synced, and the list of
    missed snapshots have synced, the node will perform the pending deletes
    and restores on this list. At this point, the current snapshot list in
    the node will be updated, and hence in case of conflicts arising during
    snapshot handshake, the peer hosting the bricks will be given precedence
    Likewise, if there will be a conflict, and both peers will be in the same
    state, i.e either both would be hosting bricks or both would not be hosting
    bricks, then a decision can't be taken and a peer-reject will happen.
    
    glusterd_compare_and_update_snap() implements the following algorithm to
    perform the above task:
    Step  1: Start.
    Step  2: Check if the peer is missing a delete on the said snap.
             If yes, goto step 6.
    Step  3: Check if there is a conflict between the peer's data and the
             local snap. If no, goto step 5.
    Step  4: As there is a conflict, check if both the peer and the local nodes
             are hosting bricks. Based on the results perform the following:
             Peer Hosts Bricks    Local Node Hosts Bricks       Action
                   Yes                     Yes                Goto Step 7
                   No                      No                 Goto Step 7
                   Yes                     No                 Goto Step 8
                   No                      Yes                Goto Step 6
    Step  5: Check if the local node is missing the peer's data.
             If yes, goto step 9.
    Step  6: It's a no-op. Goto step 10
    Step  7: Peer Reject. Goto step 10
    Step  8: Delete local node's data.
    Step  9: Accept Peer Data.
    Step 10: Stop
    
    Change-Id: I79be0f0f5f2a4f5c72277a4e77c2be732af432e1
    BUG: 1061685
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7525
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a7c8d514c0487019d218c327deb52f7d09645875
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 21 03:32:00 2014 +0000

    glusterd: Rename the export dictionary as peer_data
    
    During a glusterd handshake, a dictionary is passed among
    the peers which contains, info of volumes, global opts,
    and now also info of snaps and list of missed snaps
    
    As it now contains more than just volume specific data,
    renaming the dict in the code-base from "vols" to "peer_data"
    
    Change-Id: Ib457172789ddd0d8978b08bceab0988c48e9eea7
    BUG: 1061685
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7524
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b46d0ba04901ebca81d0f477e3e9ac6ba8607946
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Apr 3 03:36:28 2014 +0000

    glusterd/snapshot: Recreate the mount dirs and mount the lvm snapshots on node reboot.
    
    The lvm snapshots of the bricks are mounted at /var/run/gluster/snaps/ or
    /run/gluster/snaps. These paths being on a tempfs, on reboot are removed.
    So when glusterd starts, we need to recreate these paths, activate the
    respective logical volumes (lvm snapshots of the bricks), and mount
    these logical volumes at their respective paths.
    
    Change-Id: Ic5ef61e79a25d9830df717c592391965fe09db62
    BUG: 1061685
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7452
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5d9172e0b3e14795db7aba321cfcac428a201399
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 7 06:02:10 2014 +0000

    glusterd/snapshot: Perform missed snap deletes and restores.
    
    Replacing is_volume_restored(gf_boolean_t) with
    restored_from_snap(uuid_t) in glusterd_volinfo_
    
    Also removed gd_restore_snap_volume from glusterd-volgen.c
    to glusterd-snapshot.c
    
    Change-Id: Ic615a1658cfaffa98d4590506ac82f20bf709ad6
    BUG: 1089906
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7455
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 49733d307f010bfeb3d2440402ff51a5366262f5
Author: Yuan Ding <beback198611@gmail.com>
Date:   Mon Apr 21 22:10:13 2014 +0800

    gNFS: gNFS drc cache failed to detecte duplicates.
    
    After the drc cache get full, message "DRC failed to detect duplicates" keep
    printed in the log.
    The root cause is drc_compare_reqs use the wrong compare type. This function
    should use type drc_cache_op_t as its input type. Since all rbtree related code
    (except function rpcsvc_drc_lookup) in drc cache pass drc_cache_op_t as compare
    type. Only rpcsvc_drc_lookup use type rpcsvc_request_t. It has been modified
    too.
    
    Change-Id: I925c097debe6b82f267986961fd4e7755f3de9af
    BUG: 1089676
    Signed-off-by: Yuan Ding <beback198611@gmail.com>
    Reviewed-on: http://review.gluster.org/7519
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 22f47322d246c94d0bec8e893e4837a67d39f544
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Mar 3 18:00:59 2014 +0530

    Barrier: Barrier translator options configuration
    
    barrier enable/disable, barrier-timeout configuration in barrier translator.
    
    Change-Id: I7cbf9cd4f5e55d42dcc6b7cd6827234566c7b6f3
    BUG: 1060002
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7177
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d7b3e068290c41b13ecd664771814202d7d26881
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 7 05:25:28 2014 +0000

    glusterd/snapshot: Adding snap_vol_id and snap_uuid to missed_snap_list
    
    Persisting missing snapshot info on disk as well as in memory in
    the following format:
    -------------NODE-UUID--------------:--------------SNAP-UUID-------------=---------SNAP-VOL-ID------------:BRICKNUM:-------BRICKPATH--------:OPERATION:STATUS
    927cb5fe-63da-48f5-82f6-e6a09ddc81c4:8258b18f-d408-483d-8239-204039dc6397=a17b4fe42c5a45f7a916438643edaa13:   3    :/brick/brick-dirs/brick3:    1    :   1
    927cb5fe-63da-48f5-82f6-e6a09ddc81c4:8258b18f-d408-483d-8239-204039dc6397=a17b4fe42c5a45f7a916438643edaa13:   3    :/brick/brick-dirs/brick3:    3    :   1
    927cb5fe-63da-48f5-82f6-e6a09ddc81c4:8258b18f-d408-483d-8239-204039dc6397=83a3cc05453b46b2a7eda4c9a9208638:   3    :/brick/brick-dirs/brick3:    1    :   1
    
    This data will be stored on disk at /var/lib/glusterd/snaps/missed_snaps_list
    
    In memory we maintain the data as a list of glusterd_missed_snap_info
    in conf, the key for this list are the first two fields,
    i.e NODE-UUID:SNAP-UUID.
    
    For every NODE-UUID:SNAP-UUID, there can be multiple operations missed
    on multiple bricks. So we maintain a list of glusterd_snap_op_t
    for every node of glusterd_missed_snap_info
    
    This list is maintained or updated during snapshot create, delete, and restore
    operations which are the only operations that if missed, are recorded in this
    list.
    
    During snapshot create, if a node is down, or a brick is down, we don't
    receive their mount point infos. snap_status of such bricks is marked as
    -1, and their brick details are added to this list.
    
    During snapshot delete, we check from originator node, if any other
    nodes, holding bricks of the said snap are down. Those are also added to the list.
    Also if the node is up, but the snapshot was pending for a snap
    brick, and its snap_status is -1, we add that to the list too.
    When a subsequent delete entry is processed for an already existing
    create entry, we just mark the create entries status as done (2), and don't
    add the delete entry to the list.
    
    During snapshot restore, we check from originator node, if any other
    nodes, holding bricks of the said snap are down. Those are also added to the list.
    Also if the node is up, but the snapshot was pending for a snap
    brick, and its snap_status is -1, we add that to the list too.
    Like delete when a subsequent restore entry is processed for an already existing
    create entry, we just mark the create entries status as done (2), and don't
    add the restore entry to the list.
    
    Change-Id: I54f63e28d3c40555d0f84528f38227103171f594
    BUG: 1061685
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7454
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d2cdc392accdd35995370ee5b52aee5e5af7dee4
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Apr 27 15:03:58 2014 +0200

    Update references to the maillinglist to gluster-devel@gluster.org
    
    gluster-devel@nongnu.org has moved to gluster-devel@gluster.org. All
    occurrences in the current (non legacy) documentation and code have been
    adjusted.
    
    Change-Id: I053162e633f7ea14fd3eed239ded017df165147c
    BUG: 1091705
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7573
    Reviewed-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 03813a6ec08405c815b993551d16f07075efd467
Author: Kasturi Narra <knarra@redhat.com>
Date:   Wed Apr 23 14:04:59 2014 +0530

    doc: Adding user documentation for WORM feature
    
    Change-Id: Ic31c8305254dd00eae986fbb322cac3761b5d330
    BUG: 1086760
    Signed-off-by: Kasturi Narra <knarra@redhat.com>
    Reviewed-on: http://review.gluster.org/7530
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 76ab97169f63da78c9e83daf040d7b09766497cf
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Apr 24 13:38:31 2014 +0200

    fuse: minor improvements for readdir(plus)
    
    Instead of using 'int' for the sizes, use a 'size_t' as it is more
    correct. Save the size of a fuse_dirent in a temporary variable so that
    strlen() on the filename is called fewer times.
    
    Also correcting some typos in comments.
    
    Change-Id: Ic62d9d729a86a1a6a53ed1354fce153bac01d860
    BUG: 1074023
    Reported-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7547
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f77e5b6ebe5d702065844db141ebd38ff7802168
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Apr 26 20:19:38 2014 -0700

    rpcgen: After recent changes parallel builds failed
    
    Parallel builds failed due to make file would overrun
    xdrgen (internally xdrgen uses tempfiles to add License
    header).
    
    Seperate out header and source generation and add explicit
    dependency to fix it.
    
    Change-Id: Id20f548493540b0f17a2300f0775646f9f20789c
    BUG: 1090807
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7572
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fbef3a51c501c67ce6814dd16efb87758d855d48
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Apr 27 07:00:34 2014 +0530

    libglusterfs: Define macro GF_PRI_USEC for Linux as well
    
    Change-Id: I073f1f4ead4391d497fbb7603f9ee0257271493b
    BUG: 1089172
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7571
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3b40a553f466aa3d671efc2ae892215bebaa4c7b
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Thu Apr 24 12:55:05 2014 +0530

    gNFS: Log properly for pmap_getport() fail in NLM
    
    In NLM callback path, if pmap_getport() FAILs, it just log the error
    message saying "Is firewall running on the client". It may happen
    that RPC services are not running e.g. "rpcbind" is not running or
    nlockmgr (NLM) is not registered with portmapper which all can be
    checked using "rpcinfo -p" command.
    
    FIX:
    Modify the log message to include the later case mentioned
    above.
    
    Change-Id: If422275b2ab59d1e974a6caa37132f31e9a34329
    BUG: 1090782
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/7544
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 6a188c6b2c95d16c1bb6391c9fcb8ef808c2141b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Apr 24 16:37:05 2014 +0530

    features/locks: Remove stale entrylk objects from 'blocked_locks' list
    
    * In the event of a DISCONNECT from a client, as part of cleanup,
      entrylk objects are not removed from the blocked_locks list before
      being unref'd and freed, causing the brick process to crash at
      some point when the (now) stale object is accessed again in the list.
    
    * Also during cleanup, it is pointless to try and grant lock to a
      previously blocked entrylk (say L1) as part of releasing another
      conflicting lock (L2), (which is a side-effect of L1 not being
      deleted from blocked_locks list before grant_blocked_entry_locks()
      in cleanup) if L1 is also associated with the DISCONNECTing client.
      This patch fixes the problem.
    
    Change-Id: I3d684c6bafc7e6db89ba68f0a2ed1dcb333791c6
    BUG: 1089470
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7560
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0af287791f0d50b5d2975cb2e2c902c797b05860
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Apr 2 05:39:22 2014 +0000

    glusterd/snapshot-handshake: Perform handshake of missed_snaps_list.
    
    In a handshake, create a union of the missed_snap_lists of the two peers.
    If an entry is present, its no op.
    If an entry is pendng, and the peer entry is done, mark own entry as done.
    If an entry is done, and the peer ertry is pending, its a no-op.
    If its a new entry, add it.
    
    Change-Id: Idbfa49cc34871631ba8c7c56d915666311024887
    BUG: 1061685
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7453
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 447f4dec70a8103fc188024ea76447425cf14c60
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Apr 25 16:08:09 2014 -0700

    rpcgen: 'hyper' is 64bit undefined on Darwin use quad_t
    
    "9819fcedf10f1430d4969c86e6df4dfe975b7dcf" After the commit i
    observed that we never used "hyper" as defined in .x previously
    in the .[c,h] files.
    
    Change-Id: I26152141bca6e789c4a3b3158fffe0a65e4b0878
    BUG: 1090807
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7566
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8647ea41d42c35d1e74232c37b898708dee315c4
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Apr 25 11:16:02 2014 +0530

    build: fix RHEL 7 build issue
    
    Glusterfs build on RHEL 7 fails with "Installed (but unpackaged)
    file(s) found".  This patch fixes it.
    
    BUG: 1058188
    Change-Id: I8f37935b75ba02d085e75a66cdbc4017d82faa2e
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/7557
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9819fcedf10f1430d4969c86e6df4dfe975b7dcf
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Apr 22 13:27:35 2014 -0700

    rpcgen: Remove autogenerated files instead build on demand
    
    Avoid modifying autogenerated files and keeping them in
    repository - autogenerate them on demand from ".x" files
    
    Change-Id: I2cdb1fe9b99768ceb80a8cb100fa00bd1d8fe2c6
    BUG: 1090807
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7526
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 40675af8b4a1a90331e353295c75c0ea63457cf6
Author: Kotresh H R <khiremat@redhat.com>
Date:   Thu Apr 24 14:21:46 2014 +0530

    feature/changelog: Change default rollover and fsync-interval time
    
      This will change the following default configurables.
       1. rollover-time: from 60 to 15.
       2. fsync-interval: from 0 to 5.
    
    Change-Id: I9c8db01376967c4f19547ec87f54833f8b139d29
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7545
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 841ac48b413f0e108d25af36429568b6d34dab39
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Apr 24 17:09:24 2014 -0700

    osx: Compilation fixes
    
    Change-Id: I822936cbeb4ec8af46be8e94644ea666b919ae5c
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 500a656c91558dd7913f572369f20b8550e9e98d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sat Apr 19 20:03:38 2014 +0530

    features/locks: Remove stale inodelk objects from 'blocked_locks' list
    
    * In the event of a DISCONNECT from a client, as part of cleanup,
      inodelk objects are not removed from the blocked_locks list before
      being unref'd and freed, causing the brick process to crash at
      some point when the (now) stale object is accessed again in the list.
    
    * Also during cleanup, it is pointless to try and grant lock to a
      previously blocked inodelk (say L1) as part of releasing another
      conflicting lock (L2), (which is a side-effect of L1 not being
      deleted from blocked_locks list before grant_blocked_inode_locks()
      in cleanup) if L1 is also associated with the DISCONNECTing client.
      This patch fixes the problem.
    
    * Also, the codepath in cleanup of entrylks seems to be granting
      blocked inodelks, when it should be attempting to grant blocked
      entrylks, which is fixed in this patch.
    
    Change-Id: I8493365c33020333b3f61aa15f505e4e7e6a9891
    BUG: 1089470
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7512
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bc434b3ca961757ade8c6093f4ff0dbe4b3a4672
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 23 14:05:10 2014 +0530

    rpcsvc: Ignore INODELK/ENTRYLK/LK for throttling
    
    Problem:
    When iozone is in progress, number of blocking inodelks sometimes becomes greater
    than the threshold number of rpc requests allowed for that client
    (RPCSVC_DEFAULT_OUTSTANDING_RPC_LIMIT). Subsequent requests from that client
    will not be read until all the outstanding requests are processed and replied
    to. But because no more requests are read from that client, unlocks on the
    already granted locks will never come thus the number of outstanding requests
    would never come down. This leads to a ping-timeout on the client.
    
    Fix:
    Do not account INODELK/ENTRYLK/LK for throttling
    
    Change-Id: I59c6b54e7ec24ed7375ff977e817a9cb73469806
    BUG: 1089470
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7531
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a3cb38e3edf005bef73da4c9cfd958474a14d50f
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Apr 17 15:54:34 2014 -0700

    build: MacOSX Porting fixes
    
    git@forge.gluster.org:~schafdog/glusterfs-core/osx-glusterfs
    
    Working functionality on MacOSX
    
     - GlusterD (management daemon)
     - GlusterCLI (management cli)
     - GlusterFS FUSE (using OSXFUSE)
     - GlusterNFS (without NLM - issues with rpc.statd)
    
    Change-Id: I20193d3f8904388e47344e523b3787dbeab044ac
    BUG: 1089172
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Signed-off-by: Dennis Schafroth <dennis@schafroth.com>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Dennis Schafroth <dennis@schafroth.com>
    Reviewed-on: http://review.gluster.org/7503
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9c13471b109587a639662fc690384285bee02bc6
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Apr 23 15:53:41 2014 +0000

    tests: print info about failed tests
    
    It's a bit frustrating to run a test normally (e.g. during development),
    see a failure, and then have to re-run it with DEBUG=1 to see what
    actually failed.  This tiny patch prints out the command line of the
    test that just failed, even if DEBUG=0 (in fact only if DEBUG=0 since
    otherwise it would be redundant).
    
    Change-Id: Icffa096d0bcc6f35176f0e47d9d1bc538698ca2c
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/7537
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 00e247ee44067f2b3e7ca5f7e6dc2f7934c97181
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Wed Apr 9 10:19:43 2014 +0530

    gNFS: Support wildcard in RPC auth allow/reject
    
    RFE: Support wildcard in "nfs.rpc-auth-allow" and
    "nfs.rpc-auth-reject". e.g.
      *.redhat.com
      192.168.1[1-5].*
      192.168.1[1-5].*, *.redhat.com, 192.168.21.9
    
      Along with wildcard, support for subnetwork or IP range e.g.
      192.168.10.23/24
    
    The option will be validated for following categories:
    1) Anonymous i.e. "*"
    2) Wildcard pattern i.e. string containing any ('*', '?', '[')
    3) IPv4 address
    4) IPv6 address
    5) FQDN
    6) subnetwork or IPv4 range
    
    Currently this does not support IPv6 subnetwork.
    
    Change-Id: Iac8caf5e490c8174d61111dad47fd547d4f67bf4
    BUG: 1086097
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/7485
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b6cc23204f1941184cb08ec3d84beecd2d06fd91
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Apr 9 11:53:33 2014 +0530

    glusterfs-server : barrier timeout tuning fix
    
    Problem : Reconfiguration of barrier timeout through gluster volume set shows a
    success but it never changes the default timeout value which is 120 seconds.
    After digging into the code deeper, it was found that timeout is never modified
    in reconfigure() as the first check i.e. whether barrier is already enabled or
    disabled always fails since barrier option is not modified in this request.
    
    Fix : Introduced notify() in barrier translator which will take care of the rpc
    request to enable/disable barrier. reconfigure() will simply set barrier
    enable/disable and timeout options blindly without any validation.
    
    Please note this patch only contains the changes in barrier translator however
    from complete code flow perspective the caller in the glusterfsd mgmt should
    call notify instead of reconfigure to fix this problem.
    
    Change-Id: I1371b294935f6054da7c1dc6a9a19f1d861e60fb
    BUG: 1085671
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7428
    Reviewed-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 43442dfe72dbdf4b89cb8b17bd3113ed11240cd0
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Apr 14 17:39:43 2014 +0530

    doc : remove brick usage change
    
    This patch takes care of changing admin guide (admin_managing_volumes.md) for
    remove-brick usage change. 3.6 version onwards remove-brick requires an explicit
    option (start/force etc).
    
    Change-Id: If6c5b0bf2c30c2b9a8c7644d314e2593006818c2
    BUG: 1086737
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7474
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 99bfc2a2a1689da1e173cb2f8ef54d2b09ef3a5d
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Apr 14 12:39:36 2014 +0000

    snapshot: use volume's brick_ids for the snaps
    
    brickinfo->brick_id was introduced to establish persistence of client xlator
    names and AFR chanelog attributes (http://review.gluster.org/7155). The
    snapshot volumes must also use the same IDs during snapshot create and
    restore to maintain persistence.
    
    Change-Id: I13d66d19b63520061ba9ec5f0ce661cf3b9eeafe
    BUG: 1066778
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7477
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 29e183b41b3c915de997464d0c137ad30559afd2
Author: Kasturi Narra <knarra@redhat.com>
Date:   Tue Apr 15 18:45:12 2014 +0530

    doc: Adding documentation for file-snapshot
    
    Change-Id: I52b70a2fb24f5e3f802f0ce8b1c50102c267e218
    BUG: 1086750
    Signed-off-by: Kasturi Narra <knarra@redhat.com>
    Reviewed-on: http://review.gluster.org/7487
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 31c9cd4631a25ab635f38b2e83800975ff212688
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Apr 21 13:53:29 2014 +0530

    glusterd: pass the right argument for perf subgraph
    
    Change-Id: Ic292dcd8e477066c1079f0f1e170f5153459b029
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/7514
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 20e317011af7c0f075819bf0648b225f6dc42350
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 27 20:34:44 2014 +0100

    fuse: prevent READDIR(P) from writing to much data to /dev/fuse
    
    In an environment with mixed architectures (32-bit servers, 64-bit
    client), it is possible that the on-wire Reply on a READDIR(P) procedure
    contains more direntries than the client can fit in the maximum size
    that the fuse-request indicated.
    
    A direntry is a dynamically sized structure, because the structure
    contains the name of the entry. The client sends a maximum size in the
    READDIR(P) Call to the server, and the server uses this size to limit
    the number of direntries to return. In case the server can pack more
    direntries in the requested maximum size (due to alignment differences
    between the architectures), it can happen that the client unpacks the
    list of direntries into a buffer that exceeds the maximum size that was
    given in the initial fuse-request.
    
    This change introduces a check for the maximum requested size of the
    fuse-response in fuse_readdir_cbk() and fuse_readdirp_cbk(). When the
    conversion from gluster-direntries to the fuse-direntry format takes
    place, the maximum size is checked, and the 'extra' direntries are
    discarded. The next readdir()/getdents() that is done, will fetch the
    just discarded direntries again.
    
    In addition to this bugfix, some extra logging in send_fuse_iov() and
    send_fuse_data() has been added to help diagnosing similar issues.
    
    Change-Id: If2eecfcdf9c248f3820035601446d2c89ff9d1a1
    BUG: 1074023
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7278
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2da51737c49f7917a974bdf9e6e566307583ad16
Author: Anand Avati <avati@redhat.com>
Date:   Thu Mar 27 21:21:12 2014 -0700

    strfd: memory backed file descriptor
    
    A file descriptor like interface, backed by a string, on which
    fprintf() like IO can be performed. Internally the backing string
    is grown on demand.
    
    Useful in generating virtual file content on the fly (used in meta)
    
    Change-Id: I60d8751c4c750f3f06aa454a4ccd9909b3ac8ac7
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7508
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 11473a6a10aaa5e62050e7e52115e2f8f10de124
Author: Anand Avati <avati@redhat.com>
Date:   Thu Mar 27 08:03:52 2014 -0700

    common-utils: new dirent compatible time fmt
    
    Introduce a new time format without "/" and spaces, in order to
    be used in (virtual) filenames.
    
    Change-Id: I468be54f1ec7f45265add4c458e19d95567439f7
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7507
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 81b32ab6e1c950577d0f2779db67283303e3e705
Author: Anand Avati <avati@redhat.com>
Date:   Thu Mar 27 06:35:34 2014 -0700

    fuse: allow xlators to request for direct-io-mode on virtual files
    
    Translators like meta, create virtual files with dynamic content
    generated only at the time of open(). Therefore the file size
    returned in lookup or stat is 0 (just like files in /proc). However
    the VFS does not read beyond the size, and if the size is 0, no
    READ ever reaches gluster for that file -- unless direct-io-mode
    is enabled.
    
    This patch allows translators to return "direct-io-mode" flag for
    such 0-byte virtual files in xdata of open_cbk/create_cbk.
    
    Change-Id: I3fe3312cd96baa4eecfe1247ab7255b4f455f049
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7506
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit bac02a359f86a742fbf750cf4f056160324d0746
Author: Anand Avati <avati@redhat.com>
Date:   Thu Mar 27 23:53:58 2014 -0700

    fuse-resolve: loc_wipe() after inode_link()
    
    the inode to be linked may have the last ref. loc_wipe() can
    destroy it before inode_link() gets to ref it.
    
    Change-Id: Ic2d44084e6e9c8289f35cae82c8e4575af105398
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7505
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a67630b3970f9ad035a1d1463d9c2a6c6e7de736
Author: Anand Avati <avati@redhat.com>
Date:   Wed Mar 26 10:59:27 2014 -0700

    defaults: add new symbol default_fops
    
    with members filled with pointers to appropriate default methods
    
    Change-Id: I6cdc43e4f6776e2ad45cd5cbca5642e0c639ffde
    BUG: 1089216
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7504
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 99d86b1a1afe62c06f7aa2e3d6bb68df7762ce48
Author: Soumya Koduri <skoduri@redhat.com>
Date:   Fri Mar 21 12:57:14 2014 +0530

    Added Handle-based ops to get/set/remove extended attributes in the libgfapi.
    
    Change-Id: I1a8e666018d7b93e0bba2d9882935681da909980
    BUG: 1089414
    Signed-off-by: Soumya Koduri <skoduri@redhat.com>
    Reviewed-on: http://review.gluster.org/7308
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 580ac71d3b91a10c3264eddc7600dd75dfb0ad88
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Apr 17 12:07:04 2014 +0200

    rdma: correct some spelling mistakes
    
    Change-Id: Ib7018aa8a79d36ab942516457a79039cb3e67355
    BUG: 1088849
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7498
    Reviewed-by: Vikhyat Umrao <vumrao@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 02ac5fa4b5ed4c1cb531724c85ff10c83f221541
Author: Anand Avati <avati@redhat.com>
Date:   Tue Apr 1 17:28:55 2014 -0700

    cluster/dht: force set dir inode ctx cached time in setattr()
    
    In setattr, the inode times may have been explicitly set "back
    in time". In such cases, if the inode ctx times are not force
    set, then they continue to be higher and continue serving the
    higher/older value in future calls to dht_inode_ctx_time_update()
    
    Change-Id: I9cbfa7cf7c4069b0106d1f462de08c5d59bc91b5
    BUG: 1083324
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/7378
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e55f3fe25a4fd2cc9021fad97faedc5e94aa4e7c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 17 17:01:07 2013 +0530

    Add upgrade scripts for quota
    
    Change-Id: I289662300d32f75e2fc6e789037c3224054a38a5
    BUG: 969461
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7418
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c7d59dc00860ac6c355845bf79ba787d9e92e036
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Sep 18 14:12:58 2013 +0530

    doc: Upgrade steps for quota
    
    Change-Id: Ib007029f74f52d28e424a15950d46504336bde10
    BUG: 969461
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7419
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 36ae3edd207bf173ba4d106024368df4c0d18c7e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 14 12:36:50 2014 +0200

    mount.glusterfs: return 32 in case of double mounting
    
    The mount.nfs helper returns 32 for this particular error case. It makes
    sense for mount.glusterfs to return the same error value.
    
    Change-Id: I628f4c93bc796bb096e91857195ffd3d296eaae9
    BUG: 1031973
    Reported-by: Deepak C Shetty <deepakcs@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7469
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1dc3331d93ea9a2bb17a6dfa54f24ff57ecd6047
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Apr 16 12:05:14 2014 -0700

    scripts: Use `/bin/bash` not `/bin/sh`
    
    If using `/bin/sh` this is what we see
    
    $ ./who-wrote-glusterfs.sh
    ./who-wrote-glusterfs.sh: 39: shift: can't shift that many
    
    Use `/bin/bash` instead where 'shift' without an argument
    is supported.
    
    Change-Id: I2be05f0062eb8456631c1cee859757052f1b6dc7
    BUG: 1087771
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7496
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d6ad57239d396f31ae0cd21e2e8e5db64aae5714
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Apr 15 18:06:24 2014 +0000

    doc: add documentation for NUFA feature
    
    Change-Id: I00f1c669d4ebc61f09c50f8de4c893907f6d75c2
    BUG: 1086745
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/7489
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 686ee24a80c6ee7a5135aace8c2536f2afbcf367
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Apr 15 20:12:04 2014 +0000

    doc: add documentation for server-quorum feature
    
    Change-Id: Ifaf5c18a320270a9b98c7b25536281fa42b64ad3
    BUG: 1086765
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/7491
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit f7e19ce46782fd62c50894ed541cebdcf72ead82
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Apr 15 11:24:31 2014 +0200

    scripts: add new email aliases
    
    Two developers started to use new email addresses, marking them as
    aliases. Also assign @gmail.com addresses to the "(unknown)" employer.
    
    Change-Id: Ic5722c1611b003182c0288ba530d6ab275c2ca1b
    BUG: 1087771
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7484
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit c29a9d63b3f36866f1c138fe9b5dd5da48ec720f
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Apr 15 10:26:31 2014 +0530

    doc: Add doc for network compression xlator
    
    Change-Id: Iaed94f1bfe7c97eade95923759980a1d10805663
    BUG: 1086752
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/7479
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a9d4d369efc978511e3cb69e5643945710cc9416
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Apr 2 11:36:20 2014 +0530

    dict: add dict_set_dynstr_with_alloc
    
    There is an overwhelming no. of instances of the following pattern in
    glusterd module.
    
        ...
    
        char *dynstr = gf_strdup (str);
        if (!dynstr)
           goto err;
        ret = dict_set_dynstr (dict, key, dynstr);
        if (ret)
           goto err;
    
        ...
    
    With this changes it would look as below,
    
       ret = dict_set_dynstr_with_alloc (dict, key, str);
       if (ret)
           goto err;
    
    Change-Id: I6a47b1cbab4834badadc48c56d0b5c8c06c6dd4d
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/7379
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 09d2dcac3a238cfe6bde1a7aed06facfa16caf20
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 10 14:43:47 2014 -0400

    configure: argp-standalone is always built, even when not needed
    
    This patch still configures argp, i.e. creates Makefile in
    /contrib/argp-standalone, for the `make dist`, but there's no reason
    to compile it when it's not going to be linked into anything.
    
    Change-Id: Id0fcb717b5821d8a4c176e6274339f46b3a4a249
    BUG: 1086773
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/7440
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c193996c94901d81a2a623799d83ef96f595d3e2
Author: Bala.FA <barumuga@redhat.com>
Date:   Thu Apr 10 14:03:55 2014 +0530

    build: set run levels for glusterd init script properly
    
    'chkconfig --add glusterd' does not set run levels for start/stop.
    This patch fixes it.
    
    Change-Id: I8962f5207d034b6875353e15eb60c4d08c5a4fe4
    BUG: 1086141
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/7432
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 493e7c1934e65f5b7de5e710528f503e083c49e4
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Apr 10 10:54:01 2014 -0700

    pkg-version: Use /bin/bash instead of /bin/sh
    
    `function` is reserved word only available in /bin/bash,
    Using `/bin/sh` with `function` keyword fails on Ubuntu.
    
    Change-Id: Ia0fff8f13ace2a0eb1dac50093ff42294d960814
    BUG: 1074919
    Reviewed-on: http://review.gluster.org/7439
    Reviewed-by: Bala FA <barumuga@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 712541cdefcc9614e5a79f628358f205ceda6e55
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Mar 11 15:05:44 2014 +0530

    logging: Make logger and log format configurable through cli
    
    Change-Id: Ic4b701a6621578848ff67ae4ecb5a10b5f32f93b
    BUG: 1075611
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7372
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e73af16885f6d11ebcb225edb4d12214ceeba74c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Apr 10 22:09:53 2014 +0200

    mount.glusterfs: return an error when mounting failed
    
    When mounting fails, mount.glusterfs incorrectly returns 0 for some
    error cases, it should return 1 instead. Also make sure that error
    messages are redirected to /dev/stderr and not printed to stdout.
    
    Unfortunately it is not possible with the current test-scripts to test
    commands like 'mount -t glusterfs ...'. Any mounting of Gluster volumes
    is done directly with the 'glusterfs' command instead.
    
    Change-Id: Ica9d45b6d5ae537de869a1fa0f6c3edab47225d1
    BUG: 1031973
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7441
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d69c1bd9b4caf633745e08be61921ac8636d5991
Author: M S Vishwanath Bhat <vbhat@redhat.com>
Date:   Thu Apr 10 22:21:22 2014 +0530

    Adding admin-guide for distributed-geo-rep
    
    Change-Id: Icbbc9d3fc14fc1a5ae9550f096eb69dda41e92a4
    BUG: 1086796
    Signed-off-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Reviewed-on: http://review.gluster.org/7437
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1c079acf4e9ef121e5e22e12243f15b080ae5f65
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Apr 11 12:56:24 2014 +0200

    doc: add documentation for the "Brick Failure Detection" feature
    
    The documentation from the feature page should be included in the
    sources.
    
    Change-Id: I4fd67ce1c56afc5236c00de8be9110dfa6bbe91f
    BUG: 1086700
    Feature-page: http://www.gluster.org/community/documentation/index.php/Features/Brick_Failure_Detection
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7449
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0e7f8af0db8201ee892979713ac86d5548f5ec73
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jul 11 19:42:16 2013 +0530

    cli,glusterd: Improve detach check validation
    
    This patch improves the validation for the 'peer detach' command.
    
    A check for if volumes exist with some bricks on the peer being detached
    validation is added in peer detach code flow (even force would have this
    validation).
    
    This patch also gurantees that peer detach doesn't fail for a volume with all
    its brick on the peer which is getting detached and there are no other bricks on
    this peer.
    
    The following steps need to be followed for removing a downed and unrecoverable
    peer.
    * If a replacement system is available
      - add it to the cluster
      - use replace-brick to migrate bricks of the downed peer to the new
        peer (since data cannot be recovered anyway use the 'replace-brick
        commit force' command)
      or,
      If no replacement system is available,
      - remove bricks of the downed peer using 'remove-brick'
    
    Change-Id: Ie85ac5b66e87bec365fdedd8352b645bb25e1c33
    BUG: 983590
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/5325
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 29bccc2ed18eedc40e83d2f0d35327037a322384
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Feb 19 16:30:11 2014 +0530

    gluster: GlusterFS Volume Snapshot Feature
    
    This is the initial patch for the Snapshot feature. Current patch
    includes following features:
    * Snapshot create
    * Snapshot delete
    * Snapshot restore
    * Snapshot list
    * Snapshot info
    * Snapshot status
    * Snapshot config
    
    Change-Id: I2f46920c0d61c515f6a60e0f8b46fff886d9f6a9
    BUG: 1061685
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Signed-off-by: Sachin Pandit <spandit@redhat.com>
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Signed-off-by: Joseph Fernandes <josferna@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/7128
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2045c9ea1c7c3aac9d377070df6f0ee99619f421
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Feb 28 11:10:51 2014 +0530

    build: rearrange spec file elements
    
    This is majorly cleanup wrt spec file elements/definitions.  This
    patch fixes to ease adding downstream specific conditions.
    
    BUG: 1074939
    Change-Id: I311abf8457417591a0d08569d3f83d73fa63cdc0
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/7165
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 4bacb40fc898ee9519cfe4e9ee50401ec466168c
Author: Bala.FA <barumuga@redhat.com>
Date:   Thu Feb 27 12:39:43 2014 +0530

    build: set version based on git tag or specific
    
    This patch brings version and release number generated at build time
    using git tags or fixed content from VERSION file.
    
    With git tag, version/release number are got from output of
    'git describe --tags --match "v[0-9]*"' command.
    
    This behavior can be overriden by having VERSION file with fixed
    version/release.  The VERSION file should have text describing version
    and release for example something like 'v3.4.0-1'
    
    For testing this patch, its required to remove autom4te.cache
    directory to avoid seeing previously set version.
    
    BUG: 1074919
    Change-Id: I8f68172e8b389b0ba0846e9adb4b597e67a909aa
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/7164
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 8d7dde6b322483389c25cc0f056c8b27c79c160e
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Apr 8 14:37:33 2014 +0530

    cluster/afr: Set right argument order for STACK_WIND_COOKIE
    
    Change-Id: Ia26e17a7147ed825319c7c29880b9cf4ae80a48c
    BUG: 1085259
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/7416
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit aa199093fdf37dcd87a73cea83f9b9164d5800c5
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 27 18:51:08 2014 +0000

    glusterd: call runner_end even if runner_start fails
    
    Change-Id: I5eca01a131307ba3be2aed4922eea73025ff284c
    BUG: 1081013
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/7360
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 19d9a31263e16c51bd4cba09b83becd8c43ddc1f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 8 23:45:31 2014 +0530

    cluster/afr: Mem leak fixes found in valgrind for iozone
    
    Change-Id: I869d191dc3470b2208c17343bbf772f01ef744cb
    BUG: 1085511
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7424
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cbe454b7189255a74df4464e12dff0fcf0064240
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Apr 8 12:28:04 2014 +0530

    features/locks: Fix a missing assignment in new_entrylk_lock()
    
    Change-Id: If5c03456d61ec930d588b57781fb545eed18e4a2
    BUG: 1085220
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/7413
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>

commit 5216e53dedcb74079aaeaec65a2af9486690fea6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 7 10:19:37 2014 +0530

    cluster/afr: Init local on txn-frame for zerofill
    
    Change-Id: I516f4fb0237dd0b3e512117bf987cea69f8678b8
    BUG: 1084485
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7407
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8235de189845986a535d676b1fd2c894b9c02e52
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Mar 20 18:13:49 2014 +0100

    rpc: warn and truncate grouplist if RPC/AUTH can not hold everything
    
    The GlusterFS protocol currently uses AUTH_GLUSTERFS_V2 in the RPC/AUTH
    header. This header contains the uid, gid and auxiliary groups of the
    user/process that accesses the Gluster Volume.
    
    The AUTH_GLUSTERFS_V2 structure allows up to 65535 auxiliary groups to
    be passed on. Unfortunately, the RPC/AUTH header is limited to 400 bytes
    by the RPC specification: http://tools.ietf.org/html/rfc5531#section-8.2
    
    In order to not cause complete failures on the client-side when trying
    to encode a AUTH_GLUSTERFS_V2 that would result in more than 400 bytes,
    we can calculate the expected size of the other elements:
    
        1 | pid
        1 | uid
        1 | gid
        1 | groups_len
       XX | groups_val (GF_MAX_AUX_GROUPS=65535)
        1 | lk_owner_len
       YY | lk_owner_val (GF_MAX_LOCK_OWNER_LEN=1024)
      ----+-------------------------------------------
        5 | total xdr-units
    
      one XDR-unit is defined as BYTES_PER_XDR_UNIT = 4 bytes
      MAX_AUTH_BYTES = 400 is the maximum, this is 100 xdr-units.
      XX + YY can be 95 to fill the 100 xdr-units.
    
      Note that the on-wire protocol has tighter requirements than the
      internal structures. It is possible for xlators to use more groups and
      a bigger lk_owner than that can be sent by a GlusterFS-client.
    
    This change prevents overflows when allocating the RPC/AUTH header. Two
    new macros are introduced to calculate the number of groups that fit in
    the RPC/AUTH header, when taking the size of the lk_owner in account. In
    case the list of groups exceeds the maximum possible, only the first
    groups are passed over the RPC/GlusterFS protocol to the bricks.
    A warning is added to the logs, so that most system administrators will
    get informed.
    
    The reducing of the number of groups is not a new inventions. The
    RPC/AUTH header (AUTH_SYS or AUTH_UNIX) that NFS uses has a limit of 16
    groups. Most, if not all, NFS-clients will reduce any bigger number of
    groups to 16. (nfs.server-aux-gids can be used to workaround the limit
    of 16 groups, but the Gluster NFS-server will be limited to a maximum of
    93 groups, or fewer in case the lk_owner structure contains more items.)
    
    Change-Id: I8410e59d0fd246d601b54b961d3ae9cb5a858c10
    BUG: 1053579
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7202
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 07df69edc8165d875edd42a4080a494e09b98de5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Apr 8 15:29:08 2014 +0530

    geo-rep: fix the code bug introduced due to flake8 refactoring
    
    Sorry for the bug, which got introduced due to code refactoring.
    http://review.gluster.org/#/c/7311/
    
    Change-Id: Ide519ca114aa8a7d7624d7af99945c857f069069
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7417
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6567d141c1b0112acb35e711371ae5a879fc645a
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Apr 7 17:38:32 2014 +0530

    gfapi: In glfs_set_volfile_server() remove the port number check.
    
    The documentation for glfs_set_volfile_server() api says that the
    port zero is a valid value. Specifying 0 uses the default port
    number GF_DEFAULT_BASE_PORT. Hence removing the check for port being
    zero.
    
    Change-Id: I942a7fe54a418231a438ab67756537df8f28d2de
    BUG: 1084964
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7409
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aef305334c379f6875f0f9ded1e05526c8e36c81
Author: Justin Clift <justin@gluster.org>
Date:   Sat Apr 5 03:38:17 2014 +0100

    tests: Increase bug-865825.t wait time for self-heal daemon
    
    BUG: 1084653
    Change-Id: I057bbd2e50803344552314b32d2d0e6240bf9604
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/7404
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 238d101e55e067e5afcd43c728884e9ab8d36549
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Mar 21 12:33:10 2014 +0530

    geo-rep: code pep8/flake8 fixes
    
    pep8 is a style guide for python.
    http://legacy.python.org/dev/peps/pep-0008/
    
    pep8 can be installed using, `pip install pep8`
    
    Usage: `pep8 <python file>`, For example, `pep8 master.py`
    will display all the coding standard errors.
    
    flake8 is used to identify unused imports and other issues
    in code.
    
    pip install flake8
    
    cd $GLUSTER_REPO/geo-replication/
    flake8 syncdaemon
    
    Updated license headers to each source file.
    
    Change-Id: I01c7d0a6091d21bfa48720e9fb5624b77fa3db4a
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7311
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0c20b17c09b2eca82f3c79013fd3fe1c72a957fd
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Mar 27 15:04:40 2014 +0530

    tests/afr: self-heal
    
    Basic functional tests related to self-heal.
    
    arequal-checksum.c is taken from
    https://github.com/raghavendrabhat/arequal after consent from all
    authors.
    
    Change-Id: I43facc31c61375f4dbe58bbb46238e15df5c9011
    BUG: 1080759
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7357
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ef08cf0fb6ce63094468d85f5b3bab7637e88b00
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 4 12:04:37 2014 +0530

    feature/barrier: Add statedump support
    
    This patch adds statedump support for barrier. This currently dumps
    barrier xlators private information and the queue of barriered fops.
    
    Change-Id: I273eb6e676db02c40c363feeff58a79737dc041e
    BUG: 1060002
    Reviewed-on: http://review.gluster.org/7136
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b69c4c843ce0c6a361c46fd53cbbbb9ce0e27cd8
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Feb 5 13:02:34 2014 +0530

    features/barrier: add barrier translator
    
    gluster feature page:
    http://www.gluster.org/community/documentation/index.php/Features/Server-side_Barrier_feature
    
    Change-Id: Ia9f8802a54d1ffbd1cf789b80f5d30819bf65f64
    BUG: 1060002
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6928
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d586ecc0a501440436a918ed973fd75facafc455
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sun Mar 30 08:37:02 2014 +0530

    log: Add missing log message from glusterfsd.c to glusterfsd-messages.h
    
    ... by retaining GLFS_NUM_MESSAGES as 33 which is its correct value.
    
    Also replace all occurrences of gf_log with gf_msg/gf_msg_debug.
    
    Change-Id: Ibfbe1d645de521e8d59ca406f78b1a8eb08aa7e0
    BUG: 1075611
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/7371
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 091c49d85cf727ab9c391ba1ac2b44e1091fd259
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 3 07:38:15 2014 -0400

    rpm: fix broken glusterfs-server install of hooks
    
    the %ghost hook directories are no longer ghosts now that files
    are installed in them
    
    Change-Id: I6133b891c73d87e4e35dc9c6c7ba7febbc9e2e7f
    BUG: 1080970
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/7391
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b66568b6cb6694016f95e9d5a5220d3bde76907d
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Mar 26 16:55:12 2014 -0700

    build: move argp-standalone into contrib/ directory
    
    Change-Id: Iedcddf95c3577da644c0aebbb297b04c93f1b6fe
    BUG: 1081274
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7352
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d8dd4049143c191cea451bade470b906c67dbbe0
Author: Justin Clift <justin@gluster.org>
Date:   Fri Apr 4 18:22:50 2014 +0100

    cli: Trivial wording improvement of a comment
    
    Change-Id: Ib569b39bdf0357c30c94c7a1b8d3ff87b811841c
    Reviewed-on: http://review.gluster.org/7403
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 50b33f4050e11876ecb8e3512880334de25e3f21
Author: Brian Foster <bfoster@redhat.com>
Date:   Fri Apr 4 12:59:58 2014 +0000

    afr: Simple 1-liner fix for crash in Rackspace
    
    BUG: 1084485
    Change-Id: I89ddf10add041638ef70baebbce0ec2807ef4b6d
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/7402
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d5072db4c56c2351437aa4c2d340bf2766e318ce
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Thu Apr 3 15:10:58 2014 +0530

    cli : Removal of dead code
    
    dead code reported by covscan is removed from cli-cmd-parser.c
    
    Fix for coverity CID: 1195423
    
    Change-Id: Ice1771dc8b3ef47fd2e63b380b12e850dc1d5d95
    BUG: 789278
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7389
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 49fbc578ef96b7952d4d77993fb8a7212ae486dd
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Mar 26 11:22:12 2014 +0530

    tests/afr: select correct read-child for entry OPs.
    
    Change-Id: If375c937579a18d603ed70232130a4664060e9d6
    BUG: 1080759
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7344
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 27bc6a07b4c82409845077aed0556114caa8dc99
Author: Justin Clift <justin@gluster.org>
Date:   Thu Apr 3 18:33:19 2014 +0100

    tests: Adjust test 767095 to cope with long hostnames
    
    BUG: 1084147
    Change-Id: Ie1ff8852a501690e681072c54620d305b5e20d6a
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/7395
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ca6af761fb63068b170b9e8b1143598af244e06c
Author: Prashanth Pai <ppai@redhat.com>
Date:   Tue Mar 25 16:15:15 2014 +0530

    features/glupy: Add mem accounting support
    
    When glusterfs is built from source using -DDEBUG flag and glupy
    xlator is added to vol file, the brick process used to crash when
    mounting the volume.
    
    This fix is largely derived from the fix submitted for BZ #1035751.
    Thanks to Justin Clift for helping in tracking this down.
    
    BUG: 1035751
    Change-Id: Id64f92eecc9335e34dd08812fe176774e7723c2c
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/7332
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 997c89b6172116557f981510a94232486ec526b0
Author: Kotresh H R <khiremat@redhat.com>
Date:   Tue Mar 25 11:11:41 2014 +0530

    features/gfid-access: Fix possible inode memory corruption.
    
            During lookup, the inode is not ref'd. Added code
            to ref the inode in call path and unref in cbk path.
            Also fixed a case where we should always be putting
            linked inode into context as it is not guaranteed
            that we get same inode that we passed in a call to
            inode_link.
    
    Change-Id: Iaec083a9258658bef3047e83956729d3dbcd9a59
    BUG: 1080295
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7329
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 5dedef81b6ef91d462ce49ded4e148dfc17deee2
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Wed Mar 19 11:30:22 2014 +0530

    cli: remove-brick no longer defaults to commit-force
    
    Problem : When gluster volume remove-brick is executed with out any option, it
    defaults to force commit which results in data loss.
    
    Fix : remove-brick can not be executed with out explicit option, user needs to
    provide the option in the command line else the command will throw back an usage
    error.
    
    Earlier usage : volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ...
                    [start|stop|status|commit|force]
    
    Current usage : volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ...
                    <start|stop|status|commit|force>
    
    Change-Id: I2a49131f782a6c0dcd03b4dc8ebe5907999b0b49
    BUG: 1077682
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/7292
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <sam.somari@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e75be8977ede9b9174d20b39c427e6fb4ccde567
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 24 22:54:03 2014 +0530

    cluster/afr: Remove eager-lock stub on finodelk failure
    
    Problem:
    For write fops afr's transaction eager-lock init adds transactions
    that can share eager-lock to fdctx list. But if eager-lock finodelk
    fop fails the stub remains in the list. This could later lead to
    corruption of the list and lead to infinite loop on the list
    leading to a mount hang.
    
    Fix:
    Remove the stub when finodelk fails.
    
    Change-Id: I0ed4bc6b62f26c5e891c1181a6871ee6e4f4f5fd
    BUG: 1063190
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6944
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1c1b8269d994c0885d753c8f0da8d5154876c7ae
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Mar 25 09:36:45 2014 +0530

    tests/quota: Wait till the rebalance is complete
    
    Change-Id: Ia6f0c81fb1542ce1de965a69a61535691df056c3
    BUG: 1077159
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/7380
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0c1d78f5c52c69268ec3a1d8d5fcb1a1bf15f243
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Mar 22 01:33:06 2014 -0700

    gfapi: glfs_set_volfile_server() now entertains multiple calls
    
    Previous API:
    
    glfs_set_volfile_server (..., const char *host, ...) - single call
    
    New API's:
    
    glfs_set_volfile_server (..., const char *host1, ...)
    glfs_set_volfile_server (..., const char *host2, ...)
    
    Multiple calls to this function with different volfile servers,
    port or transport-type would create a list of volfile servers
    which would be polled during `volfile_fetch_attempts()`
    
    glfs_unset_volfile_server (..., const char *host, ...) to remove
    a server from the list (this is provided for future usage)
    
    Change-Id: I313efbd3efbd0214e2a71465f33195788df406cc
    BUG: 986429
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7317
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e7dcc7f8240ef3f54f39b2f243c1eb0eb1cd3844
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Mar 26 11:09:17 2014 +0530

    tests/afr: gfid mismatch test
    
    Change-Id: I12bae9c4035d5b28292e8085a5b600a3e22abaf4
    BUG: 1080759
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7342
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 36c7f8341540a1c93b5b0aa84688e58ed93422f8
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Mar 26 11:41:37 2014 +0530

    tests/afr: select correct read-child for data OPs.
    
    Change-Id: If84bc489b6c45bde3bdb858da5f1600cea78c8a5
    BUG: 1080759
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7345
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9a3de81fe5c42c0495dccc5877cecbc2edb81f3c
Author: Susant Palai <spalai@redhat.com>
Date:   Tue Feb 18 13:03:50 2014 +0000

    DHT/Rebalance : Hard link Migration Failure
    
    Probelm : __is_file_migratable used to return ENOTSUP
    for all the cases. Hence, it will add to the failure
    count. And the remove-brick status will show failure
    for all the files.
    
    Solution : Added 'ret = -2' to gf_defrag_handle_hardlink to
    be deemed as success. Otherwise dht_migrate_file will try to
    migrate each of the hard link, which not intended.
    
    Change-Id: Iff74f6634fb64e4b91fc5d016e87ff1290b7a0d6
    BUG: 1066798
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7124
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 283ae136d4974eefabd65880098449ae244b2d50
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 26 11:03:01 2014 +0530

    tests: Stale file lookup test
    
    Change-Id: I6edfc5b7ee42677e92d9cff6a7180692d20e9310
    BUG: 1080759
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7341
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7c36d9ec0de67b9b9a0803fcd378ef8d3b453c87
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Mar 25 10:13:35 2014 -0700

    doc: Update manpages
    
    Change-Id: Id14c7c3229ed266cd15915a2136e3290ce2c5ed2
    BUG: 1031328
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7338
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 31e34cfd72712c76c127509d14d50eb008743fd5
Author: ShyamsundarR <srangana@redhat.com>
Date:   Fri Dec 20 13:19:00 2013 +0530

    log: enhance gluster log format with message ID and standardize errno reporting
    
    	Currently there are quite a slew of logs in Gluster that do not
    	lend themselves to trivial analysis by various tools that help
    	collect	and monitor logs, due to the textual nature of the logs.
    
    	This FEAT is to make this better by giving logs message IDs so
    	that the tools do not have to do complex log parsing to break
    	it down to problem areas and suggest troubleshooting options.
    
    	With this patch, a new set of logging APIs are introduced that
    	take additionally a message ID and an error number, so as to
    	print the message ID and the descriptive string for the error.
    
    	New APIs:
    		- gf_msg, gf_msg_debug/trace, gf_msg_nomem, gf_msg_callingfn
    
    	These APIs follow the functionality of the previous gf_log*
    	counterparts, and hence are 1:1 replacements, with the delta
    	that, gf_msg, gf_msg_callingfn take additional parameters as
    	specified above.
    
    	Defining the log messages:
    	Each invocation of gf_msg/gf_msg_callingfn, should provide an ID
    	and an errnum (if available). Towards this, a common message id
    	file is provided, which contains defines to various messages and
    	their respective strings. As other messages are changed to the
    	new infrastructure APIs, it is intended that this file is edited
    	to add these messages as well.
    
    	Framework enhanced:
    	The logging framework is also enhanced to be able to support
    	different logging backends in the future. Hence new configuration
    	options for logging framework and logging formats are introduced.
    
    	Backward compatibility:
    	Currently the framework supports logging in the traditional
    	format, with the inclusion of an error string based on the errnum
    	passed in. Hence the shift to these new APIs would retain the log
    	file names, locations, and format with the exception of an
    	additional error string where applicable.
    
    	Testing done:
    	Tested the new APIs with different messages in normal code paths
    	Tested with configurations set to gluster logs (syslog pending)
    	Tested nomem variants, inducing the message in normal code paths
    	Tested ident generation for normal code paths (other paths
    		pending)
    	Tested with sample gfapi program for gfapi messages
    	Test code is stripped from the commit
    
    	Pending work (not to be addressed in this patch (future)):
    	- Logging framework should be configurable
    	- Logging format should be configurable
    	- Once all messages move to the new APIs deprecate/delete older
    	  APIs to prevent misuse/abuse using the same
    	- Repeated log messages should be suppressed (as a configurable
    	  option)
    	- Logging framework assumes that only one init is possible, but
    	  there is no protection around the same (in existing code)
    	- gf_log_fini is not invoked anywhere and does very little
    	  cleanup (in existing code)
    	- DOxygen comments to message id headers for each message
    
    Change-Id: Ia043fda99a1c6cf7817517ef9e279bfcf35dcc24
    BUG: 1075611
    Signed-off-by: ShyamsundarR <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/6547
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 326b77695f15444f79cea9822e35361e6bd167d5
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Mar 26 17:30:32 2014 +0530

    rpm: Include the hook scripts of add-brick, volume start, stop and set.
    
    Change-Id: I9485da3d9a54a52cc524daff8f4f4caca3a6065d
    BUG: 1080970
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7346
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 468a14b8b10639f0983be57e985cc9db98c6550c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Mar 10 06:55:11 2014 +0000

    glusterd: suppress spurious error message during startup
    
    From glusterd log:
    ----------
    E [glusterd-store.c:1981:glusterd_store_retrieve_volume] 0-: Unknown key:
    brick-0
    ----------
    
    The message is emitted from glusterd_store_retrieve_volume() when it reads the
    volinfo file because it doesn't do anything with the key-value pair. Suppress the
    error. The key is needed by glusterd_store_retrieve_bricks() which anyway
    re-reads it.
    
    Also change the log level to WARNING since we do not error out if an unknown key
    is got while parsing the volinfo file.
    
    Change-Id: Icd7962d9e16e0f90e6a37ee053dcafe97d2cab94
    BUG: 1079279
    Reviewed-on: http://review.gluster.org/7314
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 21c282ef311d3d7385bba37ddb0a26fb12178409
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Mar 25 11:07:31 2014 +0530

    cluster/afr: Sparse file self-heal canges
    
    - Fix boundary condition for offset
    - Honour data-self-heal-algorithm option
    - Added tests for sparse file self-healing
    
    Change-Id: I14bb1c9d04118a3df4072f962fc8f2f197391d95
    BUG: 1080707
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7339
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 00802b3a484499267af2e4474d75d3f75887ad07
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Mar 23 08:01:15 2014 +0530

    features/compress: Add mem accounting support for compress
    
    Change-Id: I89a7a4cd64ef65ad3bab180d66797a62b4e1e195
    BUG: 923540
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7320
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f7a815a2d0e7e9d7ed1ec2da587790bd3ddda9e5
Author: Justin Clift <justin@gluster.org>
Date:   Fri Mar 21 20:13:16 2014 +0000

    features/glupy: Rename Glupy python module to avoid namespace conflict
    
    * Rename gluster.py to glupy.py to avoid namespace conflict (#1018619)
    * Move the main Glupy files into glusterfs-extra-xlators rpm
    * Move the Glupy Translator examples into glusterfs-devel rpm
    * Add Glupy entry to the MAINTAINERS file
    
    BUG: 1018619
    Change-Id: I48de598ba5ae8eec0e7e276bbcca1abb0e549cef
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/6979
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a8b03479af1cd23baddd373a4d52f366b49c2398
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Feb 27 08:23:33 2014 +0000

    glusterd: op-version check for brickops.
    
    cluster op-version must be atleast 4 for add/remove brick to proceed.
    This change is required for the new afr-changelog xattr changes that
    will be done for glusterFS 3.6 (http://review.gluster.org/#/c/7155/).
    
    In add-brick, the check is done only when replica count is increased
    because only that will affect the AFR xattrs.
    
    In remove-brick, the check is unconditional failing which there will be
    inconsistencies in the client xlator names amongst the volfiles of
    different peers.
    
    Change-Id: If981da2f33899aed585ab70bb11c09a093c9d8e6
    BUG: 1066778
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7122
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 17454dfea9f3c4d47fcf0b5370a6155f639c8aeb
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Feb 25 09:17:18 2014 +0530

    glusterd: persistent client xlator/ afr changelog names
    
    -Add a unique brick-id field to glusterd_brickinfo_t
    -Persist the id to the brickinfo file
    -Use the brick-id as the client xlator name during vol create, add-brick and
     replace-brick operations.
    -For older volumes,generate the id in-memory during glusterd restore but defer
     writing it to the brickinfo file until the next volume set operation.
    -send and receive the brick-ids during peer probe.
    
    Feature page:
    www.gluster.org/community/documentation/index.php/Features/persistent-AFR-changelog-xattributes
    
    Related patch:
    http://review.gluster.org/#/c/7122
    
    Change-Id: Ib7f1570004e33f4144476410eec2b84df4e41448
    BUG: 1066778
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7155
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2a77659e9c25cc51fed193147ba3bfea56c5f8f9
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Feb 7 16:45:58 2014 +0530

    glusterfsd: Remove dead code.
    
    Previous cleanup of this function had removed some lines
    which had left dead code. Just removing that.
    
    Fix for coverity CID: 1167461 .
    
    Change-Id: I2a34fc407ce0eb4c4ba759c8ce6574a00b37020a
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6937
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dc6f7acaeda69ac0765812b3d961197a68ef9bf5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Mar 22 19:30:45 2014 +0530

    encryption/crypt: Add mem-accounting for crypt xlator
    
    Without these changes crypt.t crashes when compiled with -DDEBUG
    
    Change-Id: I1f7372aa30a09dbe3ae81d1dd598cf36e17fe0b7
    BUG: 1030058
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7319
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 53194718bb2aed6b88084cafd9e84a4350663ac6
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Feb 27 06:50:15 2014 +0000

    Glusterd/Remove-brick: Reconfigure the nfs server volfile upon remove-brick start
    
    Problem : For remove-brick start operation  all client volfiles are reconfigured
    except nfs server volfile. Hence, even after layout is fixed by the rebalance
    process, the nfs clients dont see the change and go on creating directories and
    files in the decommissioned brick which leads to data loss after remove-brick
    commit.
    
    Solution : Reconfigure the nfs server volfile for remove-brick start
    
    credit: kaushal@redhat.com
            spalai@redhat.com
    
    Change-Id: Ib8cd8b45a9e1f888d5e00dff65cdf77c1613a2af
    BUG: 1070734
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7162
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 16151032862af8ee70f14eff57162d829d8d75f9
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Mar 10 18:28:02 2014 +0530

    debug/io-stats:fix compile warning
    
    Compiler Warning:
    ---------------------------------------------------------
    io-stats.c: In function 'io_stats_dump':
    io-stats.c:950:24: warning: comparison between 'gf1_cli_stats_op' and
    'enum gf1_cli_info_op' [-Wenum-compare]
                     if (op == GF_CLI_INFO_ALL ||
    io-stats.c:951:24: warning: comparison between 'gf1_cli_stats_op' and
    'enum gf1_cli_info_op' [-Wenum-compare]
                         op == GF_CLI_INFO_CUMULATIVE)
                            ^
    ---------------------------------------------------------
    Fix: Use the appropriate enum in function defintion of io_stats_dump().
    Note: Using the same BZ ID as the commit that introduced this argument.
    
    Change-Id: I24e1aaf9ab86b4f337e3daa729d561ec208f2a95
    BUG: 1030580
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7217
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6d3739292b7b51d2ddbab75b5f884fb38925b943
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jan 16 16:14:36 2014 -0800

    cluster/afr: refactor
    
    - Remove client side self-healing completely (opendir, openfd, lookup)
    - Re-work readdir-failover to work reliably in case of NFS
    - Remove unused/dead lock recovery code
    - Consistently use xdata in both calls and callbacks in all FOPs
    - Per-inode event generation, used to force inode ctx refresh
    - Implement dirty flag support (in place of pending counts)
    - Eliminate inode ctx structure, use read subvol bits + event_generation
    - Implement inode ctx refreshing based on event generation
    - Provide backward compatibility in transactions
    - remove unused variables and functions
    - make code more consistent in style and pattern
    - regularize and clean up inode-write transaction code
    - regularize and clean up dir-write transaction code
    - regularize and clean up common FOPs
    - reorganize transaction framework code
    - skip setting xattrs in pending dict if nothing is pending
    - re-write self-healing code using syncops
    - re-write simpler self-heal-daemon
    
    Change-Id: I1e4080c9796c8a2815c2dab4be3073f389d614a8
    BUG: 1021686
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6010
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit eb87c96f49b3dd2c7460e58c54ce909c706cd475
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Mar 19 18:03:54 2014 +0100

    build: do not create versioned <xlator>.so files
    
    There has been a misspelled option in the Makefile.am files. The option
    is called -avoid-version, and not -avoidversion.
    
    It is not trivial to provide a test-case for this. One way would be to
    check generated RPMs with a command like this (output should be empty):
    
      $ rpm -qlp *.rpm | grep -E '/xlator/.+.so.0'
    
    Change-Id: I2a6cc557eada4d098b73af5a254f8c75707543da
    BUG: 1078365
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7299
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 128863af2d7f37571583fe37424e76b46f8525d4
Author: Kotresh H R <khiremat@redhat.com>
Date:   Tue Mar 18 14:45:42 2014 +0530

    geo-rep/glusterd: Fix geo-rep status on introduction of volume lock
    
            Getting op context in 'glusterd_op_gsync_set' is no longer
            valid as it is expected that 'rsp_dict' sent from caller is
            filled. It was fine till now as no one was setting the op
            context. The introduction of volume locks sets it,
            consequently breaking geo-rep status command. Hence the
            code that gets dict from op context if present is removed.
    
            Also corrected some indentation issues in 'glusterd_op_gsync_set'
    
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    
    Change-Id: Ieacd6e6c9be3c92159f849caca2acf5aabca1e32
    BUG: 1077697
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7289
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3aeb95cfd072e06ed9dfbbb9249837da58c2e56a
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Mar 19 12:00:44 2014 +0530

    geo-rep: Fix ValueError - signal only works in main thread
    
    When a worker process not confirmed within 60 seconds of start
    then monitor thread was terminated instead of stopping and restarting
    the worker thread.
    Before terminate monitor thread tries to add a signal handler for
    SIGTERM to cleanup the stuff before terminate. Signal handling will
    not work inside thread, so ValueError was raised.
    
    This patch will not terminate monitor thread, instead only kills and
    restarts the worker.
    
    Change-Id: I14df26c0cc3097af29293c81536c13b86075e28f
    BUG: 1078068
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/7294
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit d4343f0d192862cb378eac13365bcfde31fa1d37
Author: arvindch <achembarpu@gmail.com>
Date:   Mon Mar 17 20:50:39 2014 +0530

    fixed a few misspellings. no code changes present
    
    Change-Id: Ia1a771301e9f1becbbffd8afd7eb68bec9696ef8
    BUG: 1075417
    Signed-off-by: arvindch <achembarpu@gmail.com>
    Reviewed-on: http://review.gluster.org/7283
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Anand Avati <avati@redhat.com>

commit 6224e878cdf780360b49760c4b0c20584bbc0b6f
Author: Luis Pabon <lpabon@redhat.com>
Date:   Sun Mar 16 23:07:19 2014 -0400

    build: Remove cmockery2 from repo
    
    While we wait for cmockery2 to be available from Fedora,
    we can remove cmockery2 from the repo.
    
    BUG: 1077011
    
    Change-Id: I75d462c607cd376a5d838ea83f4d12eb59757e73
    Signed-off-by: Luis Pabon <lpabon@redhat.com>
    Reviewed-on: http://review.gluster.org/7281
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9565ac3328dc91bd721a65b6d4e7957929e9ed59
Author: AkshataDM <oxta28@gmail.com>
Date:   Sat Mar 15 23:33:38 2014 +0530

    Made spelling changes to 19 files
    
    Change-Id: If91cf44578fe0b5176ea01ae5c5962e31606f640
    BUG: 1075417
    Signed-off-by: AkshataDM <oxta28@gmail.com>
    Reviewed-on: http://review.gluster.org/7280
    Reviewed-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 79d2a9e5b83b4d773e5b821c5c55f24718745cb7
Author: Meghana <mmadhusu@redhat.com>
Date:   Tue Mar 11 14:52:34 2014 +0000

    Changing the errno in glfs_h_rename
    
    Change-Id: I006215d910ee854aee488f3880f39ed425f294cc
    BUG: 1075488
    Reviewed-on: http://review.gluster.org/7226
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 40b0bf5fc01a17e9a1628cd9ff537b7e15353958
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 12 19:56:08 2014 +0530

    storage/bd: Fix allocations/deallocations
    
    Change-Id: I39c9eb083fc1c144fe6f011dd983b877fbbff0f7
    BUG: 1075717
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7230
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 0ddd69a60e49f1335ed29a8225e31d24c836083a
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Mar 12 15:22:14 2014 +0530

    features/quota: fix the dict leak when quota is off
    
    Change-Id: Iafe0c5104e38a1e34de1f2c2a19682178eb60e11
    BUG: 1075506
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/7227
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 61f071e15572b12d12cf9764cac6456fc2df5ff3
Author: Anand Avati <avati@redhat.com>
Date:   Sat Mar 8 12:50:47 2014 -0800

    locks: fix unconditional op_ret success of entrylk
    
    Bug introduced in recent refactoring. op_ret of entrylk() was always
    getting set to 0 even though second locker wouldn't have gotten a lock.
    This was resulting in multiple contenders to get locks granted at the
    same time.
    
    Change-Id: I99c187a9285fb80cc500b38f468f2ebda7048cab
    Signed-off-by: Anand Avati <avati@redhat.com>
    BUG: 849630
    Reviewed-on: http://review.gluster.org/7224
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 3076f75e57b971dd07165929b3dc4d0b0e312623
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Mar 11 09:32:03 2014 -0700

    scripts: CTDB hooks should add `_netdev` for network mounts
    
    Change-Id: I86ad5e9ed291866a8d478768fb447e269f51c39e
    BUG: 1075182
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7221
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Jose A. Rivera <jarrpa@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ecc475d0a517d7f58014bed93fc0957b3369d1b7
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Mar 6 19:09:13 2014 +0530

    hook-scripts: Move smb hooks to right place.
    
    Moved the hook-scripts to dirs corresponding to event.
    Also, edited S30samba-set.sh to with changes in
    other two hook scripts to bring uniformity.
    
    Change-Id: Ib98c0a18d4bb5d0ba4b881b2e19b40d72580b1c2
    BUG: 1073468
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/7201
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Reviewed-by: Bala FA <barumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bed3fcd3a47d3ca35b3536e0cad2b293dd240ce4
Author: Justin Clift <justin@gluster.org>
Date:   Thu Mar 6 16:53:50 2014 +0000

    tests: Add initial sanity checks to the GlusterFS Test Framework
    
    BUG: 1073168
    Change-Id: I0b995d94fe83053d3294df1b5fad2eef3b4355d3
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/7193
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dec7950d4b0944697e4bb8788cc02de2ac4d8708
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Mar 5 04:46:50 2014 +0000

    glusterd: send/receive volinfo->caps during peer probe.
    
    Problem: volinfo->caps was not sent over to newly probed peers, resulting in a
    'Peer Rejected' state due to volinfo checksum mismatch.
    
    Fix: send/receive volinfo capability when peer probing.
    
    Change-Id: I2508d3fc7a6e4aeac9c22dd7fb2d3b362f4c21ff
    BUG: 1072720
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/7186
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f1c4c9e6d47b637939b62b473178e1c3095651fc
Author: Satheesaran <satheesaran@gmail.com>
Date:   Thu Mar 6 15:40:31 2014 +0530

    glusterd: Fixed typo in console message during volume create
    
    While creating a volume, if the brick is created on the root
    partition, then the error statement is thrown.
    
    This error statements was containing two "is" in it.
    Removed one of the "is"
    
    Change-Id: I0d83f0feccda34989f7e2b97041d1f15ec9e2f00
    BUG: 1065551
    Signed-off-by: Satheesaran <satheesaran@gmail.com>
    Reviewed-on: http://review.gluster.org/7198
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e9ab4bc851490a8b494bf812acaac54a678c7bc2
Author: Justin Clift <justin@gluster.org>
Date:   Fri Mar 7 18:01:05 2014 +0000

    build: Don't build geo-replication rpms when on EL5
    
    Also fixes a typo bug where geo-replication isn't
    being disabled correctly
    
    BUG: 1074045
    Change-Id: I28d42637bedcc28d65b6a34ab0183559202c4aed
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/7210
    Reviewed-by: Joe Julian <joe@julianfamily.org>
    Tested-by: Joe Julian <joe@julianfamily.org>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 82f20483f753f2da6c1449d739fafa506a424eda
Author: Kotresh H R <khiremat@redhat.com>
Date:   Fri Mar 7 16:35:01 2014 +0530

    geo-rep: quick-fix for remote xtime set failed
    
    Remote xtime is required for failover/failback,
    this patch is quick fix to avoid the OSError.
    
    Code is masked out, this need to be resolved when
    failover/failback is worked on.
    
    Change-Id: If339d88a2ccd8ef18a3b3c015df765c93dcb020c
    BUG: 1073844
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7206
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c817c214033481fe59f9f44c325a9092dc337d07
Author: Luis Pabon <lpabon@redhat.com>
Date:   Thu Feb 20 13:50:19 2014 -0500

    build: GlusterFS Unit Test Framework
    
    This patch will allow for developers to create unit tests for
    their code.  Documentation has been added to the patch and
    is available here:
    
    doc/hacker-guide/en-US/markdown/unittest.md
    
    Also, unit tests are run when RPM is created.
    
    BUG: 1067059
    Change-Id: I95cf8bb0354d4ca4ed4476a0f2385436a17d2369
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Signed-off-by: Luis Pabon <lpabon@redhat.com>
    Reviewed-on: http://review.gluster.org/7145
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Justin Clift <justin@gluster.org>
    Tested-by: Justin Clift <justin@gluster.org>

commit a193f2262b93a06bf1a299f423d4ebaaa171a539
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Feb 28 14:41:52 2013 +0530

    cli: Changed log rotate command format to common format.
    
    Problem:
    The syntax of log rotate was
    volume log rotate <volname> [<brick>]
    All other commands are of the form:
    volume <verb|noun> <volname> [<actions>|options]
    
    Solution:
    Changed log rotate command usage to common format.
    Old syntax is also supported, it will be deprecated
    in next release.
    
    Change-Id: Ia6f6665185a1549c6f79ca763599b446f29e2c78
    BUG: 844187
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4594
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1fbffa0aa45560889e29a74c4c6ff16d526de700
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Mar 4 16:53:33 2014 +0000

    api: add glfs_get_volfile
    
    From the API-header description:
    
    > Sometimes it's useful e.g. for scripts to see the volfile, so that
    > they can parse it and find subvolumes to do things like split-brain
    > resolution or custom layouts.  The API here was specifically intended
    > to make access e.g. from Python as simple as possible.
    >
    > Note that the volume must be started (not necessarily mounted) for
    > this to work.
    
    Change-Id: If3f55ee9611cdf4b77aa53659f0af0d21957817d
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/7183
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d6c1468b2779b6247e44b75276436021a3469a59
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Jan 21 23:41:07 2014 +0530

    rpc: transport may be destroyed while rpc isn't
    
    rpc_clnt object is destroyed after the corresponding transport object is
    destroyed. But rpc_clnt_reconnect, a timer driven function, refers to
    the transport object beyond its 'life'. Instead, using the embedded
    connection object prevents use after free problem wrt transport object.
    
    Also, access transport object under conn->lock.
    
    Change-Id: Iae28e8a657d02689963c510114ad7cb7e6764e62
    BUG: 962619
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6751
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9f45d0f6212d6d5c96dafc4aba73d9d12b39c3d6
Author: Poornima G <pgurusid@redhat.com>
Date:   Fri Feb 28 12:13:55 2014 +0530

    libglusterfs/inode: Fix NULL dereferences.
    
    There could be scenarios where the inode_ctx_get() can
    be called to only check if the context exists, in such
    cases the buffer for the context might not have been passed.
    Hence fix inode_ctx_get() to not crash, when the buffer
    is not passed.
    
    Change-Id: I607d86eb401ccab0e5cd75f6f977c454994ec063
    BUG: 789278
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7167
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7b3399cd462d0fca6509168f13a67f43e8b2c7d2
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Feb 28 17:34:03 2014 +0100

    Reduce logging caused by non-existing extended attributes
    
    This changes the following log messages from INFO (default value) to
    DEBUG. We do not really care if someone tries to read extended
    attributes that do not exist.
    
        [2013-12-09 12:19:05.924497] E [posix.c:3539:posix_fgetxattr] 0-dis-rep-posix: fgetxattr failed on key system.posix_acl_access (No data available)
        [2013-12-09 12:19:05.924545] I [server-rpc-fops.c:863:server_fgetxattr_cbk] 0-dis-rep-server: 13074: FGETXATTR 1 (b8381953-ffa5-40fa-90dd-ae122335cc4b) (system.posix_acl_access) ==> (No data available)
    
    Change-Id: Idbbeb026f81e67025a2b36d7bfeb125ad2a1f61b
    BUG: 1027174
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7171
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee150bd45e4976bc31d1660102d487982b0ce83d
Author: Susant Palai <spalai@redhat.com>
Date:   Fri Feb 28 17:19:43 2014 +0000

    cli:  Rectify grammar in the "Usage" of "rebalance" command
    
    Problem: Currently Usage of rebalance command is : " Usage: volume rebalance
    <VOLNAME> [fix-layout] {start|stop|status} [force] "
    
    1) "force" option can be only used with "start" .
    
    2) "fix-layout" option can be only used with "start"
    
    But the current usage says "fix-layout" operation can be stopped and can get the
    status of "fix-layout" operation and also "stop" ,"status" operation can be used
    with "force" option which is not correct.
    
    Change-Id: I48e6c64c124f5803c8f09c78df0e14dc2b6a348a
    BUG: 1071411
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/7172
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit d11d3f877d37f95a915fbf5f894f23f8f88b1a18
Author: Justin Clift <justin@gluster.org>
Date:   Fri Feb 28 15:17:21 2014 +0000

    build: Add missing rpmbuild/BUILD dir for CentOS 5.x
    
    The rpmbuild/BUILD directory isn't created automatically
    by the build system on CentOS 5.x. This 1-line patch
    adds its creation to the build process.
    
    BUG: 1071504
    Change-Id: I90ad70608776cb491f2ba92fb7d6044cff4defcc
    Signed-off-by: Justin Clift <justin@gluster.org>
    Reviewed-on: http://review.gluster.org/7175
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2010fb2bc620e6f66ed769b140d92e1d94da1439
Author: Edward Shishkin <edward@redhat.com>
Date:   Fri Dec 13 21:17:44 2013 +0100

    Added test case for crypt translator
    
    Change-Id: I7a28a1285c19c3279c2f71e9d9914cf14c761858
    BUG: 1030058
    Signed-off-by: Edward Shishkin <edward@redhat.com>
    Reviewed-on: http://review.gluster.org/6504
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b0515e2a4a08b657ef7e9715fb8c6222c700e78c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jan 28 10:06:13 2014 +0100

    write-behind: track filesize when doing extending writes
    
    A program that calls mmap() on a newly created sparse file, may receive
    a SIGBUS signal. If SIGBUS is not handled, a segmentation fault will
    occur and the program will exit.
    
    A bug in the write-behind translator can cause the creation of a sparse
    file created with open(), seek(), write() to be cached. The last write()
    may not be sent to the server, until write-behind deems this necessary.
    
    * open(.., O_TRUNC, ...)/creat() the file, it is 0 bytes big
    * seek() into the file, use offset 31
    * write() 1 byte to the file
    * the range from byte 0-30 are unwritten so called 'sparse'
    
    The following illustration tries to capture this:
    
        Legend:
        [ = start of file
        _ = unallocated/unwritten bytes
        # = allocated bytes in the file
        ] = end of file
    
        [_______________#]
         |              |
         '- byte 0      '- byte 31
    
    Without this change, reading from byte 0-30 will return an error, and
    reading the same area through an mmap()'d pointer will trigger a SIGBUS.
    Reading from this range did not trigger the outstanding write() to be
    flushed. The brick that receives the read() (translated over the network
    from mmap()) does not know that the file has been extended, and returns
    -EINVAL. This error gets transported back from the brick to the
    glusterfs-fuse client, and translated by the Linux kernel/VFS into
    SIGBUS triggered by mmap().
    
    In order to solve this, a new attribute to the wb_inode structure is
    introduced; the current size of the file. All FOPs that can modify the
    size, are expected to update wb_inode->size. This makes it possible for
    extending writes with an offset bigger than EOF to mark the unwritten
    area as modified/pending.
    
    Change-Id: If5ba6646732e6be26568541ea9b12852a5d0b988
    BUG: 1058663
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6835
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6535bafe588ea901ac15d31ddb6550a2ba9cd915
Author: Kotresh H R <khiremat@redhat.com>
Date:   Tue Feb 25 16:20:46 2014 +0530

    geo-rep/gfid-access: Fix errno for non-existent GFID.
    
    Because of http://review.gluster.org/#/c/6318/ patch,
    ESTALE is returned for a lookukp on non-existent GFID.
    But ENOENT is more appropriate when lookup happens
    through virtual .gfid directory on aux-gfid-mount
    point. This is avoids confusion for the consumers
    of gfid-access-translator like geo-rep which expects
    ENOENT.
    
    Change-Id: I4add2edf5958bb59ce55d02726e6b3e801b101bb
    BUG: 1069191
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/7154
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a1bd3d295d9aa96011cff1d1f2915f26559118e7
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jan 16 01:24:41 2014 +0530

    socket: don't send notification 'up' on socket_writev failure
    
    Change-Id: If4e4b95fe025a412f25313d83c780046dfec5116
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6716
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit 7098d6adb08e74ead6bcce7bc9c5a1c0419a819e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Feb 16 16:58:46 2014 +0100

    rpm: drop the glusterfs-devel dependency from glusterfs-api
    
    This dependency was introduced when the Fedora packaging change for Bug
    1016938 was (incorrectly) merged back into the upstream community
    version.
    
    Change-Id: I74a52c96533fa381e86b47f719480f00b12722ac
    BUG: 1065750
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/7022
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Justin Clift <jclift@redhat.com>

commit f69e85511645fcbd0526e38ca88dd3e5bf0ed917
Author: Prashanth Pai <ppai@redhat.com>
Date:   Mon Feb 17 20:42:42 2014 +0530

    feature/compress: Validate option and enable doc
    
    * Validate network.compression option
    * Enable descriptions of xlator configurable options
    * Improve indentation in code
    * Make network.compression.mode not configurable by user.
      This is similar to "iam-self-heal-daemon" option in AFR xlator.
    
    Fixes BUGs: 1065658, 1065640, 1065655
    
    Change-Id: I99d82b574ee0e5c8c2baf5f5d52dbf8d015d330a
    BUG: 1065640
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/7024
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 64079f83528edb4cc4ae1a85a8633fd578b6e393
Author: Vijaykumar Koppad <vkoppad@redhat.com>
Date:   Wed Feb 19 18:51:26 2014 +0530

    build: fail configure if the libxml2 devel package is missing.
    
    Problem:
    Geo-replication uses volume info xml output.
    While installing glusterfs through build+install from source,
    and if the libxml2-devel package is not present in the system,
    build will succeed with just warning and XML output : no.
    If user fails to observe this and doesn't know that
    geo-rep is dependent on xml output, user won't be able use
    geo-rep.
    
    Solution:
    If libxml2-devel is unavailable, and if geo-rep is enabled error out in configure,
    otherwise just warn with XML_OUTPUT = no.
    If the xml-output is disabled while configuring, error out if
    geo-rep is enabled, otherwise just warn.
    
    Change-Id: Icde5d0c1e5f3b869e7db6ed6a046bdc49b450fcb
    BUG: 1066997
    Signed-off-by: Vijaykumar Koppad <vkoppad@redhat.com>
    Reviewed-on: http://review.gluster.org/7131
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fc01b0293bef8ba14650c6a52f733bb6b6b77954
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Feb 21 12:45:48 2014 -0800

    extras/hookscripts: Add `%P` as default relative root
    
    ctdb in its monitoring script looks for the "path" variable
    values at the system level not at share level.
    
    This relative root path, if any should be default for all
    volumes, to avoid issues with ctdb when doing subdirectory shares.
    
    Error:
    2014/02/21 12:50:34.355754 [41083]: ERROR: samba directory "/foodir" not available
    
    Fix: Add %P in your smb.conf
    
    [gluster-foodir]
    ...
    ...
        path = %P/foodir
    ...
    ...
    
    Change-Id: If3c110d844ba8301c901dbce40b23cac99d6d55b
    BUG: 1068776
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/7147
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 868287aa5f70bdfcf7f56663e042d74fe1acf0db
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Feb 15 17:54:38 2014 +0530

    performance/io-threads: Remove code duplication
    
    Change-Id: Ic905cc6074c796efce2972857b79ab53700a2de4
    BUG: 1065657
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/7010
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3a5914e421d10bca363f020b748e8648a4819495
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 18 12:22:59 2014 +0530

    glusterd: Check for ctx before dereferencing it.
    
    Fix for coverity CID: 1175010 & 1175011
    
    Change-Id: Ib894fadf94c36704166ac0e2a3b6febf9b3fe446
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/7025
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 47e6c202fea13458f62e397ab894f740fdced5c8
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Feb 18 16:47:09 2014 +0530

    rpc/socket: Avoid excessive INFO logs when SSL is not configured.
    
    Change-Id: I7f4dd2ae4225c8d3783417d0c3d415178f04c0da
    BUG: 1067011
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/7031
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f1f91f8016e468718df9c581662f8417a1fb999c
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Feb 18 15:44:56 2014 +0530

    build: Don't discard CFLAGS in configure
    
    The configure script was discarding the passed CFLAGS inadvertently.
    This caused failures while building rpms on epel7 and fedora-{19,20}, as
    the hardened CFLAGS passed by rpmbuild on these distros were discarded
    which lead to the failure of rpmbuild.
    
    Thanks to Neils de Vos for helping track this down.
    
    Change-Id: I5b2aa5d449d13bf67df6c19cda178bddfe6c3652
    BUG: 1066385
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/7029
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Justin Clift <jclift@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 66e2e76adaed74dae4a3606685460236870c077a
Author: Justin Clift <jclift@redhat.com>
Date:   Wed Feb 19 14:19:03 2014 +0000

    Changed Amar's email address to his gmail one
    
    Change-Id: Ia4a3d4f3e1be6dfcf0c23e8d481475927e3605da
    Reviewed-on: http://review.gluster.org/7133
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 9e0ec224148e1d3e0406eb5aa4479f3dca0d597b
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Feb 13 12:31:58 2014 +0530

    protocol/auth: Fix a possible double free.
    
    Assign NULL to addr_cpy to avoid double free.
    
    Fix for coverity CID: 1124891
    
    Change-Id: I0cd6721f066170190d8b5441ecdbc1704ed5e75b
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6993
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ff0cd7c4e326d848d5fa6591c7cc8ce54711d2d7
Author: Poornima G <pgurusid@redhat.com>
Date:   Wed Feb 19 14:12:29 2014 +0530

    libgfapi: In glfs_resolve_at(), do not override the previous return value.
    
    Overriding ret to contain glfs_loc_touchup()s' return value implies that
    if glfs_loc_touchup() is successful, glfs_resolve_at() is also successful
    which is not necessarily true. This was causing glfs_resolve_at() to
    succeed even if it couldn't resolve, thus create and other fops would
    fail. Hence overriding ret only if glfs_loc_touchup() fails.
    
    Change-Id: I0804afbd120b3798abe07e870bfc40bf162bc289
    BUG: 1066837
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/7125
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit da7972c10cd0495621ea95c186db86cfa8d997b6
Author: Poornima <pgurusid@redhat.com>
Date:   Tue Feb 4 22:52:14 2014 +0000

    mount/fuse: Fix the NULL dereference errors reported by coverity.
    
    Change-Id: I9df57e11b115d7323931735c86b586c0b65fa414
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6990
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9854ceaf9a91f2b40324e71dc0210628511fc878
Author: Soumya <skoduri@redhat.com>
Date:   Sat Feb 15 16:08:22 2014 +0530

    Docs: Fixed few broken link issues in the doc admin_settingup_clients.md
    Signed-off-by: Soumya <skoduri@redhat.com>
    
    Change-Id: If01c1a34aaf6a84b3c95d56a9536b38cd9773cbe
    Reviewed-on: http://review.gluster.org/7009
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 4b36051ce195d9ae7ec32bd614d32a023873ab29
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Feb 10 17:11:03 2014 +0530

    io-cache: Unlock and then goto out in failure case.
    
    Fix for coverity bug CID:1124625
    
    Change-Id: I76df453a17f2af7c48a80b6fc0ccd411ab96e371
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6949
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4a14159e82d7b736dec686a170b06e961d7aff53
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jan 8 17:01:44 2014 +0530

    protocol/client: conn-id should be unique when lk-heal is off
    
    Problem:
    It was observed that in some cases client disconnects
    and re-connects before server xlator could detect that a
    disconnect happened. So it still uses previous fdtable and ltable.
    But it can so happen that in between disconnect and re-connect
    an 'unlock' fop may fail because the fds are marked 'bad' in client
    xlator upon disconnect. Due to this stale locks remain on the brick
    which lead to hangs/self-heals not happening etc.
    
    For the exact bug RCA please look at
    https://bugzilla.redhat.com/show_bug.cgi?id=1049932#c0
    
    Fix:
    When lk-heal is not enabled make sure connection-id is different for
    every setvolume. This will make sure that a previous connection's
    resources are not re-used in server xlator.
    
    Change-Id: Id844aaa76dfcf2740db72533bca53c23b2fe5549
    BUG: 1049932
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6669
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7b3207168ef5496702ab10d48be4e4d7cf1f413b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Feb 14 08:20:44 2014 -0500

    storage/posix:  lgetxattr called with invalid keys on the bricks
    
    More invalid keys have crept in since this was fixed. We need a better
    strategy for avoiding this than the current noticed-in-an-strace...
    
    Cleaning tabs while I'm at it.
    
    Change-Id: I2ea97f6d1ab2a9fd569b5b5e01a4de891401fb81
    BUG: 765202
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/7003
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 82f995e6a9ba9ac4ca02d9db2f42bc9037936151
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Feb 12 14:37:23 2014 +0530

    glusterfsd: Use gf_strdup instead of assigning a literal.
    
    Fix for coverity bug CID:1124340
    
    Change-Id: Ibf8700bdeaaddade02e63470a773c5fe2aabc645
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6984
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e77c485c700c9e127ae564958eb5c4733e61f888
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Feb 15 12:14:19 2014 +0530

    rpc: Fix a crash due to NULL dereference
    
    Change-Id: Ib2bf6dd564fb7e754d5441c96715b65ad2e21441
    BUG: 1065611
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/7007
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1ad41c4ca167e4600f163408c1f859d55cdbdc07
Author: Poornima <pgurusid@redhat.com>
Date:   Wed Feb 12 03:18:43 2014 +0000

    protocol/client: Fix the possible resource leaks.
    
    Change-Id: Ib86dee366f5a6f0971c6472d1fb2c32dbf7f0102
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6985
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5fb60ca150efbf9072dd7b2de13362c8cc4daa1b
Author: Ira Cooper <ira@samba.org>
Date:   Tue Feb 11 07:05:29 2014 -0500

    glusterd: Free dup_value when error path is taken.
    
    When the error path is taken here, the data that was allocated for
    dup_value is never freed.  This patch frees it.
    
    Thanks to Kaleb Keithley <kkeithle@redhat.com> for his suggestions on how
    to fix this.
    
    Change-Id: Iad88b9ab035602d15961b46c4954d54d54e0d65e
    CID: 1124705
    BUG: 789278
    Signed-off-by: Ira Cooper <ira@samba.org>
    Reviewed-on: http://review.gluster.org/6780
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5f0a857c70863eb685ac03d4183502d3bd460b7c
Author: Jose A. Rivera <jarrpa@redhat.com>
Date:   Wed Feb 5 08:50:30 2014 -0600

    libgfapi: Add proper NULL checks
    
    Two spots check for NULL after the pointer in question has already been
    dereferenced. Checked for NULL (and set errno when needed) at appripriate
    spots, added a few NULL checks further up the stack, and some whitespace
    cleanup.
    
    BUG: 789278
    CID: 1124800
    CID: 1124805
    
    Change-Id: I1dd4ad3f285cca36f4e3f739288f154ec120aebb
    Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-on: http://review.gluster.org/6908
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit db95a98527caf1b5a52ef49e537d0ee575a9bc61
Author: Jose A. Rivera <jarrpa@redhat.com>
Date:   Wed Feb 5 09:11:55 2014 -0600

    glusterfsd: Check for NULL before dereference.
    
    BUG: 789278
    CID: 1124805
    
    Change-Id: I5926a4e59790f142d65f034726c9c369c2ad7808
    Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-on: http://review.gluster.org/6909
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 53779e4458c17a3978675585e8099c97c8c2b3a2
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Feb 11 02:22:32 2014 +0000

    glusterd/Vol-Locks : Moving globals into glusterd priv and code refactoring
    
    Moved globals(vol_lock and txn_opinfo dicts and global_txn_id) into
    glusterd priv
    
    Moved glusterd_op_send_cli_response() out of gd_unlock_op_phase
    as gd_unlock_op_phase and glusterd_clear_txn_opinfo should only
    be called if the txn id has been successfully generated. The
    cli resp should be sent irrespective of that.
    
    Changed log levels from ERROR to WARNING for some volume lock logs
    where the logs are expected and is not an error
    
    Added logs for better transparency of transaction ids.
    
    Change-Id: Ifac9b23aa9f1648c9ae252cfd3ac50bb2ed46728
    BUG: 1011470
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/6976
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a78dfebb7343671b0a3a0af8b46951894a3cf7a4
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Feb 12 17:23:28 2014 +0530

    add build-gfid option to enable pgfid tracking ...
    
    .. for inode to pathname mapping
    
    Change-Id: I0486d85b02e86d739fc1d8ea16d118fb666abf60
    BUG: 1064863
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6989
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0a8abcc5d0b727746a2ac6c0d5729700bfea742b
Author: Justin Clift <jclift@redhat.com>
Date:   Wed Feb 12 04:17:29 2014 +0000

    Removed the old and unused non-Glupy Python bindings code
    
    BUG: 1064096
    Change-Id: Ifd34f46f0f0b45bbc27d35953e6ecbca36753886
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/6980
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3c20c8427f0062c88cb90bac3c345addc8bbfb73
Author: Justin Clift <jclift@redhat.com>
Date:   Thu Feb 6 16:24:25 2014 +0100

    Clean up some weirdness with the gf_resolve inet defines
    
    Change-Id: I6bf6101aa0b5d6624891a8ebed2ac1fec2e11e1c
    Reviewed-on: http://review.gluster.org/6948
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3571066deedfe858ef37f09d6ad2160e5dd7b803
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jan 27 00:58:45 2014 -0800

    syncops: add support for custom PID
    
    AFR self-heal needs to issue syncops with special PID. Extend
    the custom UID/GID support to include custom PIDs
    
    Change-Id: I736c0e177f862b029f203acc87f9eb46c8cb839b
    BUG: 1021686
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6888
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 7b4d6e3ec61e9cb0b9d0ffa0aef2117b96e63f65
Author: Anand Avati <avati@redhat.com>
Date:   Thu Feb 6 12:32:01 2014 -0800

    storage/posix: calculate checksum only over read data
    
    If the last block of a file is not aligned to the requested
    size, checksum is calculated over junk data in the iobuf. Or
    it could be zeroes, resulting in a spurious checksum match
    in self-heal.
    
    Change-Id: I41422e08de90013dabfc348ec6fbb8ecdd4f8fb8
    BUG: 1021686
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6932
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 0cab34b3a5e94267bf6b39669b6e85af1fab8f3d
Author: Anand Avati <avati@redhat.com>
Date:   Fri Feb 7 14:29:34 2014 -0800

    core: add @xdata parameter to syncop_[f]removexattr()
    
    To be used in afr metadata self-heal
    
    Change-Id: I8dac4b19d61e331702427eeb5b606aab3d20b328
    BUG: 1021686
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6941
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 13f1d250ccbb7a3c945e35ebf182e7149b69069e
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Feb 12 14:39:03 2014 +0100

    Use libglusterfs wrapper to make setxattr portable
    
    BUG: 764655
    Change-Id: I332922521bef5684f18d5f7b226cb36d5303ae47
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6982
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 43f71899c4533ef6e160c7a8fb8c62bf0e6c3bba
Author: Poornima <pgurusid@redhat.com>
Date:   Wed Feb 12 02:44:09 2014 +0000

    cluster/stripe: Fix the possible resource leaks.
    
    Change-Id: Ic6fbc8c843f80edd7458d15229eb72a5609973a5
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6986
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fbcae0d20a409bccd8fc4daeceac010fab66d0a0
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Fri Feb 7 16:46:23 2014 -0600

    xlators/rot-13: Free memory when returning on error.
    
    Added GF_FREE() calls to free allocated memory that was left
    behind otherwise.
    
    BUG: 789278
    CID: 1124725
    
    Change-Id: I5aa086d6b13a93e14de50e47e02b0e9813af9572
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6940
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1b88d86a660a5f4e007fb229d79c54666ce04ffb
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Mon Feb 10 20:52:57 2014 +0530

    glusterd: Fix possible leaks on failure code path
    
    Fix the memory leaks in socket and glusterd in failure code
    paths reported by Coverity.
    
    CIDs: 1124777, 1124781, 124782
    
    Change-Id: I63472c6b5900f308f19e64fc93bf7ed2f7b06ade
    BUG: 789278
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6954
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 547ee245dac4f2689a0f3f8f66635e0195489602
Author: Kotresh H R <khiremat@redhat.com>
Date:   Wed Dec 4 14:14:20 2013 +0000

    geo-rep: Fix gsyncd restart issue.
    
    New function 'glusterd_gsync_op_already_set' is written which compares
    the geo-rep configuration value in gsync.conf with the one sent from
    cli. The generic function is written to compare op_value for any
    op_name sent from cli as this issue can happen with any configuration
    setting other than use-tarssh also. This routine is used to avoid
    restart of gsyncd if the configuration value is set to same as in
    gsyncd.conf.
    
    Also added error checking when glusterd_gsync_configure fails.
    Earlier, eventhough 'glusterd_gsync_configure' fails, error
    was not getting catched and success message was shown.
    
    Change-Id: If4dcd0ffc09e6e67c79ba86238f03eff1b7c7645
    BUG: 1060797
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/6897
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a9181877e3013dcaca5b59ef7764246163c10585
Author: Poornima <pgurusid@redhat.com>
Date:   Sun Jan 26 22:08:46 2014 +0000

    performance/io-cache: Fix dereferencing of freed pointer
    
    Change-Id: Ic4276c6d76c36f4eb77282dc06d2b8b212b58f08
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6822
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit db3b2149eeb44bcb716d994224d57eccf873d2a9
Author: Poornima <pgurusid@redhat.com>
Date:   Sun Feb 9 22:57:56 2014 +0000

    cluster/stripe: Fix the resource leaks.
    
    Change-Id: Ieb1fe112686f4932a6272a0117c1373e736d5b4e
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6951
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 58d7ef2f7628744db4c7bf8bf5735671e023f1d7
Author: Luis Pabon <lpabon@redhat.com>
Date:   Sun Feb 9 21:57:45 2014 -0500

    build: CFLAGS was being polluted by python flags
    
    The CFLAGS were being polluted by the python test for glupy. The
    test also sets CFLAGS -NDEBUG even when passing --enable-debug to
    configure.
    
    To fix it, the patch now saves the necessary python flags into
    new makefile flags which can now be used by the glupy Makefile.am.
    
    BUG: 1063541
    Change-Id: I8546a64b8ad4fe9318a97fb6a2f0c36087be1b29
    Signed-off-by: Luis Pabon <lpabon@redhat.com>
    Reviewed-on: http://review.gluster.org/6957
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit 8eb83e6d9a91c813275f1cbc8e0dc5423fb1ccc0
Author: Poornima <pgurusid@redhat.com>
Date:   Fri Jan 17 02:45:56 2014 +0000

    gfapi: Set log level to GF_LOG_NONE after closing log file in glfs_fini
    
    Currently any logs that are logged after calling glfs_fini will
    appear on stderr. Ideally to the end of the glfs_fini all the
    operations will be complete and there should be no further logging.
    But it appears that the client translator is still up and prints
    some log messages even after calling glfs_fini.
    
    In this patch the log level is set to GF_LOG_NONE once the log file
    is closed. This fix is not required if wait for "CHILD_DOWN" event
    is implemented in glfs_fini.
    
    Change-Id: Idde80e9a89f3a5264d02b7e6fc2a84d67550b20a
    BUG: 1054696
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6726
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2e093c728c856a41399ffdcf33c91d21c3a2f0f2
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Feb 11 13:16:38 2014 +0530

    mount.glusterfs: backward compatible option for root-squashing
    
    Change-Id: I74fa6686cff84cfad4a2587a0061e6bb2beea081
    BUG: 954057
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/6975
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8148dc2eab154e94d2c9e041cc0abbba9845ce51
Author: Ravishankar N <ranaraya@redhat.com>
Date:   Wed Jan 29 12:09:42 2014 +0000

    storage/posix: perform chmod after chown.
    
    Problem:
    When a replica brick is added to a volume, set-user-ID and set-group-ID
    permission bits of files are not set correctly in the new brick. The issue
    is in the posix_setattr() call where we do a chmod followed by a chown.
    
    But according to the man pages for chown:
    When the owner or group of an executable file are changed by an unprivileged
    user the S_ISUID and S_ISGID mode bits are cleared.  POSIX does not specify
    whether this also  should  happen  when  root does the chown().
    
    Fix:
    Swap the chmod and chown calls in posix_setattr()
    
    Change-Id: I094e47a995c210d2fdbc23ae7a5718286e7a9cf8
    BUG: 1058797
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6862
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 99c84c250501a676f73c0dd7e9b842f8c95b1f98
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Wed Jan 29 17:09:55 2014 +0530

    gNFS: Coverity fix for possible memory leak
    
    In nfs_gfid_dict(), if dict_new() fails, the control goes to
    out: block and dyngfid resource (dynamically allocated by
    GF_CALLOC()) is leaked.
    
    Add a validation for memory returned by GF_CALLOC()
    
    Drop unnecessary "goto" statements
    
    Coverity CID: 1124764
    
    Change-Id: Idda7923cc1c32260b3353f7a9141aa1cf43e4fe1
    BUG: 789278
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6852
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 408d50a64b7b3a9d6a4899060baa423ff126cc5f
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Feb 4 17:13:34 2014 +0530

    dht: Modified dht-statedump to print all subvolume_status
    
    Change-Id: I1aae33472bd15fc2bd7a170544f2994534fdf246
    BUG: 1058204
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/6800
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7ee0275333469f82e59214802601dc6e3c45f6d1
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Feb 3 10:58:47 2014 -0500

    libglusterfs/client_t.c: rhel5/i386 atomic, link failure
    
    RHEL5's gcc-4.1.2 on i386 does not have built-in atomic __sync_*()
    
    Change-Id: If7b1027570a6c8c962392871b002be0a37258ed3
    BUG: 1060703
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6894
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 28209283a67f13802cc0c1d3df07c676926810a2
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Apr 19 12:27:03 2013 +0530

    protocol/server: do not do root-squashing for trusted clients
    
    * As of now clients mounting within the storage pool using that machine's
      ip/hostname are trusted clients (i.e clients local to the glusterd).
    
    * Be careful when the request itself comes in as nfsnobody (ex: posix tests).
      So move the squashing part to protocol/server when it creates a new frame
      for the request, instead of auth part of rpc layer.
    
    * For nfs servers do root-squashing without checking if it is trusted client,
      as all the nfs servers would be running within the storage pool, hence will
      be trusted clients for the bricks.
    
    * Provide one more option for mounting which actually says root-squash
      should/should not happen. This value is given priority only for the trusted
      clients. For non trusted clients, the volume option takes the priority. But
      for trusted clients if root-squash should not happen, then they have to be
      mounted with root-squash=no option. (This is done because by default
      blocking root-squashing for the trusted clients will cause problems for smb
      and UFO clients for which the requests have to be squashed if the option is
      enabled).
    
    * For geo-replication and defrag clients do not do root-squashing.
    
    * Introduce a new option in open-behind for doing read after successful open.
    
    Change-Id: I8a8359840313dffc34824f3ea80a9c48375067f0
    BUG: 954057
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4863
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 97ce783de326b51fcba65737f07db2c314d1e218
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Feb 6 13:03:58 2014 +0530

    glusterd: Volume locks and transaction specific opinfos
    
    With this patch we are replacing the existing cluster-wide
    lock taken on glusterds across the cluster, with volume locks
    which are also taken on glusterds across the cluster, but are
    volume specific. So with the volume locks we are able to perform
    more than one gluster operation at the same time, as long as the
    operations are being performed on different volumes.
    
    We maintain a global list of volume-locks (using a dict for a list)
    where the key is the volume name, and which saves the uuid of the
    originator glusterd. These locks are held and released per volume
    transaction.
    
    In order to acheive multiple gluster operations occuring at the
    same time, we also separate opinfos in the op-state-machine, as a
    part of this patch. To do so, we generate a unique transaction-id
    (uuid) per gluster transaction. An opinfo is then associated with
    this transaction id, which is used throughout the transaction. We
    maintain a run-time global list(using a dict) of transaction-ids,
    and their respective opinfos to achieve this.
    
    Upstream Feature Page: http://www.gluster.org/community/documentation/index.php/Features/glusterd-volume-locks
    
    Change-Id: Iaad505a854bac8de8f83beec0357eb6cde3f7ea8
    BUG: 1011470
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5994
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b000b934aff4b452cf1c35c42272482a7738506e
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Jan 20 12:23:35 2014 +0530

    geo-rep: Config file upgrade
    
    When old config file is used with new geo-rep, config item like
    'georep_session_working_dir' was missing in old config file.
    
    With this patch geo-rep sets the default value for new items.
    
    Following config options supported:
      - georep_session_working_dir
      - gluster_params
      - ssh_command_tar
    
    BUG: 1036539
    Change-Id: I389c62e749f3b567f9ecf96d4b41367ef962c025
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6934
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fcfd2b973cdb9d798861bca1d30a4a42b819b73f
Author: Poornima <pgurusid@redhat.com>
Date:   Thu Jan 30 05:36:42 2014 +0000

    performance/io-cache: Fix for the bugs reported by coverity
    
    Change-Id: I24c10d874511a2f24dda2fb84d31f5074da1616f
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6869
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6b8ed063bb8a551856d0e659fa9fe4f5afa48c19
Author: Poornima <pgurusid@redhat.com>
Date:   Tue Feb 4 23:11:59 2014 +0000

    features/quota: Fix NULL dereference error reported by coverity.
    
    Change-Id: I48c1ebcb3261fa5da721e5b48d17c6c873df256d
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6907
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d4e7dd1d2fe2a76318ddd0a7200a9d4fa51dbaf7
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Feb 6 17:16:20 2014 +0530

    spec: geo-rep: Include hooks and upgrade scripts
    
    Added hook script S56glusterd-geo-rep-create-post.sh to
    %{_sharedstatedir}/glusterd/hooks/1/gsync-create/post/ and upgrade
    scripts added to %{_datadir}/glusterfs/scripts/
    
    BUG: 1036539
    Change-Id: Id114b827824e55516181ab8f564d419c258be3e2
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6926
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c1c3ab9e4c96e059ba1abc1a0b5ba221ef6e3d8d
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Thu Feb 6 12:39:24 2014 -0600

    cluster/afr: goto statements may cause exit before memory is freed.
    
    Memory is allocated for pump_priv and for pump_priv->resume_path, but if
    an error is detected the references to that memory go out of scope and
    the memory is never freed.
    
    This patch assures that the memory is freed on error.
    
    Patchset 2: These are Kaleb's recommended changes which, compared to my
                original fix, are more comprehensive and provide a more
                complete resolution to the memory leakage bugs in this
                function.  The bug reported by Coverity was limited to a
                single memory allocation.
    
    BUG: 789278
    CID: 1124737
    
    Change-Id: Ie239e3b5d28d97308bf948efec6a92f107bc648b
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6929
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0d23c99e46b3752b39487cb9268457a2f5e768fe
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Feb 9 18:51:02 2014 +0530

    tests: Set hard and soft timeouts to 0 to ensure enforcement.
    
    Change-Id: Ib233d00ea73e4141a404a2abadf9f6f81896c14d
    BUG: 1038598
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6942
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit dd9e406cf48142e7fa0619d17ccf3ecc71ce36ae
Author: Anuradha <atalur@redhat.com>
Date:   Thu Dec 5 19:02:10 2013 +0530

    quota : changes in quota list command
    
    Changes are made to quota list command such that it also
    shows whether hard-limit and soft-limit are exceeded or not.
    
    A test case to check the same is added.
    
    Change-Id: Idb365acfc5d1f2d9f3373dd5f98573d5fe87b50f
    BUG: 1038598
    Signed-off-by: Anuradha <atalur@redhat.com>
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6441
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1e26f070bb470adafd0a316c18f2fb9e1b103f27
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Fri Jan 3 12:11:19 2014 +0530

    glusterd: add volinfo to the list data structure in an order
    
    Currently volinfo is added at the end of the list while creating a volume.
    On gluster restart, readdir will not provide the ordered list and the data
    is populated in the same order as readdir.
    
    Solution is to insert the volinfo to the list in an order
    
    Change-Id: I1716ac6abbd7dd301a7125425fc413c6833f7a48
    BUG: 1039912
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6472
    Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 8b5b2bfcda0dc95aa170b8752ad97d94701172f2
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Mon Jan 27 16:38:14 2014 -0600

    performance/quick-read: Allocated memory not freed when not used.
    
    If memory is successfully allocated in the call to qr_content_extract(),
    but is not used, it is not being freed.  This patch frees the allocated
    memory if it is not passed to qr_content_refresh().
    
    BUG: 789278
    CID: 1124735
    
    Change-Id: I1c1f03a3b92fa26321ec6ee8822e6fa41da79875
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6827
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 14792bd894e7838efdc8f50a16af5445b448dc2e
Author: Susant Palai <spalai@redhat.com>
Date:   Wed Jan 29 10:47:20 2014 +0000

    cluster/dht: If hashed_subvol is NULL, do not fail
    
    Problem: With the current implementation we are allowing unlink
    of a file if hashed subvol is down and cached subvol is up.
    For the above op to work we should have the info of hashed_subvol.
    But incase we do remount of the volume we will have a zeroed layout
    for the disconnected subvol(start=0, stop=0, err=ENOTCONN) which will
    result  into hashed_subvol being NULL and failing unlink op.
    
    Solution: Dont fail if hashed_subvol is NULL. Check cached subvol
    and unlink in cached subvol. The linkto file in the hashed subvol
    can be remove later.
    
    Change-Id: Ic1982c15c8942a1adcb47ed0017d2d5ace5c9241
    BUG: 983416
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/6851
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7e06ec5b1ed6ecab8853065c9ea0dd7c1c0c58f0
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Jan 29 13:38:36 2014 +0000

    tests: Increase Expect Within time so that valid patches pass
    
    In some cases it is observed that fix-layout takes more
    than 20 seconds to complete, causing test to fail.
    Increasing it to a safe value of 30.
    
    Change-Id: I4ac8769e3a1594240ecda96700944ab3702daacc
    BUG: 1004744
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6855
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 66113e3473555c31926045218dc8b79c61751d5d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat May 18 11:52:09 2013 +0530

    features/marker-quota: more stringent error handling in rename.
    
    If an error occurs and op_errno is not set to non-zero value, we can
    end up in loosing a frame resulting in a hung syscall. This patch
    adds code setting op_errno appropriately in storage/posix and
    makes marker to set err to a default non-zero value in case of
    op_errno being zero.
    
    Change-Id: Idc2c3e843b932709a69b32ba67deb284547168f2
    BUG: 833586
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/5032
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 104e8df41073036eb47583503035bad298bdbe87
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Thu Feb 6 19:32:35 2014 -0600

    libglusterfs..xlator.c:  Close a library handle.
    
    Simple fix to ensure that a library handle is closed if it is not
    actually used.
    
    BUG: 789278
    CID: 1124783
    
    Change-Id: Ia3e734c46e1ad8c97cb8cc7f1a5616606bfbc550
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6933
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ff28179310c761a77210f1294cd2db70555fdad8
Author: Jose A. Rivera <jarrpa@redhat.com>
Date:   Thu Feb 6 14:19:43 2014 -0600

    libgfapi: Don't ignore return value of glfs_loc_touchup()
    
    BUG: 789278
    CID: 1124353
    
    Change-Id: I7d2958cbc98faf45d723f17868c515762c50c618
    Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-on: http://review.gluster.org/6931
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f32e00692e2dd2b375c95d26f69529d48d1d2a80
Author: Poornima <pgurusid@redhat.com>
Date:   Wed Feb 5 00:15:33 2014 +0000

    cluster/afr: Fix memory leak.
    
    Change-Id: I811d104684905a5a9a794cde8e925bd1a97f6546
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6906
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0ff6a1da6ac4a4b0e01ae50f1d8e3605e36bf2fc
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Feb 6 15:22:11 2014 +0530

    features/quota: fix crash in error handling after building ancestry.
    
    Change-Id: Ifbebf1aa496d49a6c4bb30258b83aaf9792828e5
    BUG: 1059833
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6923
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 032854831a3dd338d7d5aee9228937d0418b8876
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 4 18:26:57 2014 +0530

    glusterd: Fix a memory leak.
    
    errmsg may have malloc'ed memory, free it before leaving function.
    
    Change-Id: I4ab3b9db7a48a5e256eb8a08b8ab49818ce6ca1b
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6902
    Reviewed-by: Poornima G <pgurusid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7903c55a0d488f93790f5e80105f5252b88f32af
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 7 06:04:23 2014 +0000

    gverify: Correcting variable names
    
    Change-Id: I851a50e0ebb7554b821fb591375bb6ebd6240ade
    BUG: 1036539
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/6939
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 13b68bc693e92378f78f452763a6097bf1755072
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Fri Jan 31 12:13:30 2014 -0600

    features/index: Close directories left open on error.
    
    Two directory streams are opened, but not always closed if the function
    exits with an error.  This patch aims to ensure that the directories are
    closed in call cases.
    
    Some return values may be explicitly discarded.  This is done to avoid
    having a successful call to closedir() overwrite the value of ret.
    Also, the errno value is preserved in case a calling function needs to
    check errno.
    
    BUG: 789278
    CID: 1124710
    CID: 1124711
    
    Change-Id: I6bf3b5c9c6a1ec9a99cc9178243ea98572c2bac2
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6883
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 38e23d727a8fb5a4d688d9f8dc9178e6718215f5
Author: Poornima <pgurusid@redhat.com>
Date:   Thu Jan 23 02:08:19 2014 +0000

    quick-read: Remove unref of a freed iobuf.
    
    Change-Id: Ie21414658db571c9a483730b6d5e8997f04255c1
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6823
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9433cc43efd8d63b66ce5c0927a7bde01a6b7304
Author: Poornima <pgurusid@redhat.com>
Date:   Tue Feb 4 05:55:02 2014 +0000

    glusterd: Fix the NULL dereference errors reported by coverity.
    
    Change-Id: I51c120dfe2db44a2b74f35e5cafb4f364ed6e66e
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6901
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9f699ccd42712e5b991bd33319caf1e5c902f894
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Mon Feb 3 15:12:22 2014 +0530

    gNFS: Possible NULL pointer dereference
    
    In NFS-ACL code (acl3.c) i.e. acl3svc_setacl(), contol can
    go to "acl3err" block from setaclargs.mask validation or
    acl3_validate_gluster_fh() and acl3_map_fh_to_volume() macros.
    But at this point of time "cs" is yet to be init'd (the macro
    acl3_handle_call_state_init() is not yet invoked) which can
    cause a NULL ptr deref.
    
    FIX:
    Refactor the acl3 code.
    
    Coverity ID (CID): 1124491
    
    Change-Id: I3aca38770e03ce59d1705653b6d8349e6cc153b2
    BUG: 789278
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6890
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 432f7e45b2ddf511660d269548f248217a2b45ad
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 4 15:57:05 2014 +0530

    changelog: When connection is unsuccessful, close socket too.
    
    Bug fix for Coverity CID: 1124791
    
    Change-Id: I0362d45123ebc250290f3a5231f7fb113fa41212
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6900
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 055c02436fd6ef6984468b33158104770b41e422
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Jan 28 17:42:21 2014 -0800

    geo-replication: gverify should use disk_size and available_size
    
    "commit ef4bb42382a5c9c3ca0907136669a659c2a20311" was incomplete since
    reduction in sizes doesn't really have any affect on the problem when
    disks sizes are similar.
    
    Actual fix is to verify disk_size and then verify available_size
    
    Change-Id: Idb57f606df229c0bdaeda8852c74e84d29109ffc
    BUG: 1020154
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6844
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 4d7764a73f4c504ebd369c61f46e569ebc62ecc9
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jan 8 10:22:48 2014 +0530

    gsyncd / geo-rep: invoke changelog process() on non-empty change list
    
    Change-Id: Ida4890abdc90d683a4a83127a1573bbb3829ea23
    BUG: 1036539
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6793
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa7b0c640818df25b4f0297b1931ff52a77121bf
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Dec 12 17:03:09 2013 +0530

    gsyncd / geo-rep: ignore DHTs sticky bit file during crawl
    
    Change-Id: Ide927759c6a3d5301475eac9f6e785aa901d426e
    BUG: 1036539
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6792
    Reviewed-by: Kotresh HR <khiremat@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cbf6a264bd124c6b193709ad0e09c260c7d1845b
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Nov 18 19:13:27 2013 +0530

    gsyncd / geo-rep: "patch" up missing stime
    
    In cases (mostly upgrade) of unavailability of "stime" key and
    availability of "xtime" (slave's xtime), introduce "stime" key
    on the fly by setting it to the value to "xtime".
    
    Change-Id: Iaa424662d838154c8abc2cf00830c7f9d6be45ac
    BUG: 1036539
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6791
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0035b37a2d19c1ba8502cda93d9f5debfdd35c45
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Jan 20 19:38:44 2014 +0530

    gsyncd / geo-rep: cleanup the "tar" process
    
    A missing cleanup for the "tar" process (when tar+ssh
    is used as the sync engine).
    
    Change-Id: Ib9599b43e7ec606c70b7c5598793417142be3c0b
    BUG: 1036539
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6794
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c04c8a4cb1dcf20bdf05e9bdbf26862a1cf50979
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Feb 3 08:50:07 2014 +0000

    cli/cli-xml :  skipped files should be treated as failures for
    remove-brick operation.
    
    Fix: For remove-brick operation skipped count is included into
    failure count.
    
    clixml-output : skipped count would be zero always for remove-brick
    status.
    
    Change-Id: Ic0bb23b89e0cf5b884b6d1ae42bbf98deedc9173
    BUG: 1060209
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/6889
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3bc23e1ad08e212538d325ec0196ec7488ae7e62
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Jan 30 19:50:06 2014 +0530

    changelog: Restrict length of unix socket files to UNIX_PATH_MAX.
    
    Bug fix for Coverity-CID 1124847.
    
    Change-Id: I410ef8e06cbc491b1f72535298fae5e9bc77220d
    BUG: 789278
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6870
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e3162ed7e91510185316eae36f5c2c25bde53a68
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Fri Jan 31 15:11:37 2014 -0600

    libglusterfs: Allow all valid file handle values to be closed.
    
    Zero (0) is a valid file handle. The code, as written, interprets return
    values of open(2) that are less than or equal to zero to indicate an
    error.  Only -1 indicates an error.
    
    BUG: 789278
    CID: 1124756
    
    Change-Id: Ie77c25f1f557d5d5adcec464b49dc7df2e3dc7e5
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6884
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e021078220c30e781ef016b42f8cee8229042bb1
Author: Poornima <pgurusid@redhat.com>
Date:   Thu Jan 30 02:23:13 2014 +0000

    Fix for 'use after free' errors reported by coverity.
    
    Change-Id: I941fc89b2d696c7f227330321ed4bba3ed1deac4
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6868
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 60c1fa2ada704343c841b9a95d3f1cc1632fa00a
Author: Poornima <pgurusid@redhat.com>
Date:   Fri Jan 31 01:12:32 2014 +0000

    mgmt/glusterd: Fix double free.
    
    Change-Id: I7a8b7772849715b019c86c6c768f33c1d9dcb27c
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6881
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d0574d040b3d7f54ddafa0b768ddfc1e7f247536
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Mon Feb 3 17:49:51 2014 +0530

    Problem : getfattr fails and mount point becomes inaccessible while
    fetching glusterfs.ancestry.path key value for a gfid from aux-gfid-mount
    based mount point.
    
    Analysis : The caller of posix_make_ancestryfromgfid() function i.e.
    posix_get_ancestry_non_directory() is sending an incorrect type value as
    an argument leading to a crash in posix_make_ancestral_node() (head
    dirent pointer is NULL and an attempt to dereference causes seg fault).
    For a non directory operation this piece of code should not have been
    executed but due to incorrect type value this happened.
    
    Solution : In posix_make_ancestryfromgfid() call type is passed as
    logical or of type and POSIX_ANCESTRY_PATH instead of logical or of
    POSIX_ANCESTRY_PATH and POSX_ANCESTRY_DENTRY.
    
    
    Change-Id: Iaf844bea91396c5e2ee295d5a082998fda66f0a9
    BUG: 1060104
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/6892
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b187d3b5231406b524bf73b45f76e001692e282e
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Feb 5 21:50:20 2014 +0530

    tests/basic: Prevent mount-options.t from being run.
    
    mount-options.t introduces a race leading to failures in
    regression tests. Hence disabling the test unit till we
    sort out the race.
    
    Also removing the workaround introduced in mount.t.
    
    Change-Id: I7d60413bbff8597f90153cca838e326247e96cd9
    BUG: 1060654
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6911
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2f8a8cfc27e6a73ff0238681ea40563c8768d4e6
Author: Lukas Bezdicka <lukas.bezdicka@gooddata.com>
Date:   Wed Jan 29 11:20:08 2014 +0100

    libxlator: fix memleak in cluster_markerxtime_cbk and cluster_markeruuid_cbk
    
    Change-Id: Ide3574bf9f661b077f707990d47821feda18b1a3
    BUG: 841617
    Reviewed-on: http://review.gluster.org/6850
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7282094c5f387d7be1a353c7ed19c8e4a1e49eec
Author: surabhi <sbhaloth@redhat.com>
Date:   Mon Jan 27 14:09:10 2014 +0530

    libglusterfs:Fixing Dereference NULL return value.
    
    1.Checking of data for NULL.
    
    Change-Id: If49513f7c3fd1dc443c05dc62ed07d3254059e6e
    BUG: 789278
    Signed-off-by: surabhi <sbhaloth@redhat.com>
    Reviewed-on: http://review.gluster.org/6799
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0c721c4c046d3580f7774eb480ff139c3ef814b5
Author: ShyamsundarR <srangana@redhat.com>
Date:   Tue Jan 28 11:09:10 2014 +0530

    cluster/dht: Set restrictive open flags for files under rebalance
    
    Files that are being rebalanced are created in the new volume
    and access path needs to open these files to write changing
    data in parallel to both the old and new locations. While opening
    the file in the new location, we need to restrict the open flags
    to not use truncate or create and fail if exist flags, to prevent
    open failures or inadvertently truncate the file under rebalance.
    
    Change-Id: I12130e0377adc393f1925c45585200ad991fd0d5
    BUG: 1058569
    Signed-off-by: ShyamsundarR <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/6830
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 21a83b8be06aa73f40b83b9cfc97dc8a1972190a
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Mon Jan 27 17:49:29 2014 -0600

    features/index: Loop exit without freeing in-use memory.
    
    If the while loop is exited via the goto, the call to closedir(3) is
    skipped, leaving an open directory stream.  This patch ensure that the
    directory is closed if the loop is exited via the goto.
    
    BUG: 789278
    CID: 1124763
    
    Change-Id: Iec5da4b8d32c0a93c10d035ff38d0c063fd97cda
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6828
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 797c62eb56797189b51a1dcb35009499f920a3ea
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Sat Feb 1 22:49:22 2014 +0530

    glusterd: Reset opinfo.op ONLY if lock succeeded
    
    Change-Id: I0244a7f61a826b32f4c2dfe51e246f2593a38211
    BUG: 1060434
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6885
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ab8050448680f0c3f7e2bf670501926ca11764cf
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jan 29 16:57:12 2014 +0530

    glusterd: Bump MAX_OP_VERSION to 4
    
    Change-Id: Ib017a7d8ad8017bdcf15035018f4d04ecb5560e9
    BUG: 1059206
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6853
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 33e9e8fcb98cd8ddd483b37ff7114ea9fd8d75fb
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Tue Jan 21 02:27:03 2014 +0530

    quota: Fixing a possibility of GF_FREE on an array pointer
    
    Issue: when the charecter pointer is not heap allocated by the program
    we should not do GF_FREE on it.
    
    Change-Id: Ibccc25491a9ab924fd5b82c14566f551a061ec2e
    BUG: 789278
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6741
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 120235d6f5c85af2a0be17ad2705159e9d0b3adf
Author: Poornima G <pgurusid@redhat.com>
Date:   Tue Jan 21 23:50:23 2014 +0000

    cluster/dht: Fix layout sorting
    
    The layout was not being sorted in the ascending order leading
    to the wrong detection of holes/overlaps.
    
    From looking at the previous git commits it appears that the initial version itself had the err comparison code.
    Deductions from the current dht_layout_sort():
    1. The zero'ed out layouts should be in the from of list, if needed
    2. The layout should be sorted in the ascending order of layout error value.
    3. The layout should be sorted in the ascending order of the layout 'start'.
    But In some cases, with the err comparison code its not sorted in the ascending order. Example: If the input is as below for dht_layout_sort(), the sorting doesn't happen in ascending order.
    Input:
    0-1 err:0    2-3 err:0   6-7 err:0    0-0 err:20   4-5 err:0
    
    With the current sort, Output:
    4-5 err:0    0-0 err:0    0-1 err:0    2-3 err:0    6-7 err:0
    Expected: 0-0 err:20 0-1 err:0 2-3 err:0 4-5 err:0 6-7 err:0
    Looking at dht_layout_anomalies() it appears that, it doesn't require the layout to be sorted based on error value.
    The other solution was to replace line 468 with:
     if ((layout->list[i].err || layout->list[j].err) && (layout->list[i].start > layout->list[j].start))
    Since dht_layout_anomalies() didn't expect the layout to be sorted based on the error, removed the err comparison.
    
    Change-Id: I1215f6cd53efc7dba01c0958ba6cc7609dab6ff5
    BUG: 1056406
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6757
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit d2b0a016e713aea8920abe23f6113517d78e260a
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Mon Jan 27 14:52:37 2014 -0600

    cluster/dht: Abandoned memory if a call fails
    
    If the call to dict_set_dynstr() fails, the memory indicated by
    xattr_buf will not have been stored in the dictionary, so it must be
    freed.
    
    Patch set 2: Added a missed call to GF_FREE().  Fixed a formatting
                 consistency issue.
    
    Patch set 3: Cleaned a minor style nit.
    
    BUG: 789278
    CID: 1124786
    
    Change-Id: Id1f85bd2cbfac0b8727a3f6901f0a50ba921817d
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6826
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bbe02d77a5e7fb587787b9bbc06d28ca8419afb3
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Jan 22 14:08:45 2014 -0800

    mount.glusterfs/glusterfsd: Add dummy deprecated *fetch-attempts options
    
    volfile-max-fetch-attempts and fetch-attempts were not deprecated
    properly at 'b610f1be7cd71b8f3e51c224c8b6fe0e7366c8cf'.
    
    Provide a way for backward compatibility for broken third party apps.
    
    Change-Id: I597b50df08823e74691c5a20a4da4d13aab4b7ff
    BUG: 1045309
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
    Reviewed-on: http://review.gluster.org/6544
    Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8cf2a36dad6c8bac7cd3a05455fd555544ebb457
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jan 24 17:27:38 2014 +0530

    glusterd: Fix race in pid file update
    
    This patch only removes lines of code. For personal gratification, giving a
    detailed explanation of what the problem was.
    
    When glusterd spawns the local brick process, say when a reboot of the node
    occurs,the glusterd_brick_start() and subsequently the
    glusterd_volume_start_glusterfs() function gets called twice; from
    glusterd_spawn_daemons() and glusterd_do_volume_quorum_action() respectively.
    This causes a race, best described by a pseudo-code of current behaviour.
    
    glusterd_volume_start_glusterfs()
    {
           if(!brick process running) {
    
             step-a) reap pid file( i.e. unlink it)
             step-b) fork a brick process which creates and locks pid file and
                     binds the process to a socket.
    
            }
    
    }
    
    Time            Event
    ----            -----
    T1              Call-1 arrives, completes step-a, starts step-b
    T2              Call-2 arrives, enters step-a as Call-1's forked child is not
                    yet running.
    T3              Call-1's forked child is alive, creates pidfile and locks it,binds
                    its address to a socket.
    T4              Call-2 performs step-a; i.e.unlinks the pid file created by Call-1 !!
                    (files can still be stil be unlinked despite a lockf on it)
    T5              Call-2 does step-b, and the forked child process creates a *new* pid file
                    with it's pid and locks this file.
    T6              But Call-2's brick process is not able to bind to socket as it
                    is already in use (courtesy T3) and hence exits (so no locks anymore on the pidfile).
    
    Result:
    -  Pid file now contains PID of an extinct brick process.
    - `gluster volume status` shows this PID value. It also notices that there is no
    lock held on pid file by the currently running brick process (created by Call-1)
    and hence shows N/A for the online status.
    
    Also, as a result of events at T4, "ls  -l /proc/<brick process PID>/fd/pidfile"
    shows up as deleted.
    
    Fix:
    1.Do not unlink pid file. i.e. avoid step-a. Now at T5,Call-2's brick process
    cannot obtain lock on pid file (Call-1's process still holds it) and exits.
    
    2. Unrelated, but remove lock-unlock sequence in glusterfs_pidfile_setup()
    which does not seem to be doing anything useful.
    
    Change-Id: I18d3e577bb56f68d85d3e0d0bfd268e50ed4f038
    BUG: 1035586
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6786
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3395b98a341228e89cf0a88e0d86c90117dbb285
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Jan 30 22:27:24 2014 +0530

    tests: Fix regression failures
    
    Change-Id: I83dc651a5ce87adf51d1f539400cd91c801fc460
    BUG: 1045309
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6874
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit a7243ea310613ad0681fd68bc951492fe311916b
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Jan 25 02:39:11 2014 -0800

    build: GFAPI_VERSION should be 6.0.0 not 0.0.6
    
    ------------------------------------->
    "In essence, every time you make a change to the library and
    release it, the C:R:A should change. A new library should
    start with 0:0:0. Each time you change the public interface
    (i.e., your installed header files), you should increment the
    CURRENT number."
    
    So the version which was 3 became 5 when discard API was added
    and became 6 when zerofill was added. As per the above description,
    API addition will result in a change to the installed header (glfs.h)
    and hence warrants a change in CURRENT number ? Should you have
    changed the version to 6.0.0 instead of 0.0.6 ?
    <------------------------------------
    
    Thanks Bharata B Rao <bharata.rao@gmail.com> for pointing this out
    
    Change-Id: I0aa980a6713fbd28922a94c5debb170a89aa3512
    BUG: 862082
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6790
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Bharata B Rao <bharata.rao@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f676d5a3e037a205c93751b862b856b7639058c4
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Mon Jan 20 19:24:31 2014 +0530

    geo-rep: Fixing a memory leak issue reported by Coverity
    
    Issue: "errmsg" is allocated memory through  GF_CALLOC in function "gf_strdup"
    
    Fix: using GF_FREE to free the memory
    
    Change-Id: Iee8f8d806ea995591feee8e4ed0a0798ad07a8c4
    BUG: 789278
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6740
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 3023a50c1410b4da457e86bed69c320760d37344
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Fri Dec 13 14:18:16 2013 +0530

    dht: do not remove linkfile if file exist in cached sub volume
    
    Currently with rmdir, if a directory contains only the linkfiles
    we remove all the linkfiles and this is causing the problem when the cached
    sub volume is down and end-up with duplicate files showing on the mount point.
    
    Solution: Before removing a linkfile check if the
    files exists in cached subvolume.
    
    Change-Id: Iedffd0d9298ec8bb95d5ce27c341c9ade81f0d3c
    BUG: 1042725
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6500
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 922134fdc08afb2810cb0205f26693d36db6fd4e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 28 15:16:59 2014 +0530

    cluster/afr: Add gfid to index in wind un-conditionally
    
    Problem:
    If brick crashes just after performing xattrop before
    reaching index _cbk then the gfid will not be added to/deleted from
    index. If it is not deleted it will be deleted when self-heal is
    triggered. But if the crash happens before the file is added to index,
    user may think the system does not need self-heal even when there is
    this file that needs to be healed.
    
    Fix:
    Add file to index un-conditionally in wind phase. This way the
    file remains in index even when brick process crashes before reaching
    _cbk. This does not affect performance because of caching(check
    _index_action) built into index xlator.
    
    Change-Id: Ie83ac6aa1ac0ff66862e757864865b47ab39404d
    BUG: 1058713
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6836
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 410fe979b4e2492f04e9cc8949f5ef5041e1135a
Author: Poornima <pgurusid@redhat.com>
Date:   Thu Jan 23 22:55:45 2014 +0000

    features/qemu-block: Remove unref of freed iobuf
    
    Change-Id: I507a6504b379eef54be77b54d6e2beee63975ebf
    BUG: 789278
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6824
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e780df78fae4f69923df20c14f15b66dc918a61b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Dec 20 15:43:08 2013 +0530

    tests: Add sanity check for mount-options
    
    Change-Id: Ica246f99b8cdb6c0cf0e9143f50be056e37d3b7f
    BUG: 1045309
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6550
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3ab5d0672c7ef8a46e1b711e1593748bed407d32
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Oct 23 16:10:31 2013 +0530

    features/quota: Correct the statfs calculation when set limit is beyond ...
    
    actual disk space.
    
    Fixed one of the cases where 'df' values data show wrong when the quota limit
    is greater than back-end disk space.
    
    Change-Id: I09fb71a37602c6f3daf6b91dd3fd19b7f5f76817
    BUG: 969461
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6126
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6dfe01d7e726675913e98dc65c6c7406e5060e15
Author: Ajeet Jha <ajha@redhat.com>
Date:   Fri Jan 24 15:48:32 2014 +0530

    mount/fuse: adding a setxattr filter pass for geo-rep create.
    
    Adding filter pass for setxattr when key is "glusterfs.gfid.newfile".
    This was blocking creates at slave volume.
    
    Change-Id: I61455abd8688c52ac6894b5a04ba050076117ea3
    BUG: 1054199
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6797
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>

commit 2ef4e5a9913508bc7e371918a28adb3eb0eadbe4
Author: Ajeet Jha <ajha@redhat.com>
Date:   Thu Jan 16 17:25:49 2014 +0530

    features/gfid-access: populating inode during virtual_lookup_cbk.
    
    Setting appropriate ia_type and gfid for the inode, obtained during
    virtual_lookup_cbk of a directory by doing an "inode_link".
    
    Change-Id: I9582570c82e70ff5f1d4e441f9e9868ef82e9dc6
    BUG: 1054199
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6723
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c8975995d711e1bffe8acbb4650abc0d3bbea055
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Jan 24 15:16:39 2014 +0530

    mgmt/glusterd: Set right op versions for few options.
    
    compression and changelog translators appear first in 3.5. op-versions
    of options corresponding to these translators should be 3.
    
    Change-Id: Ib514207743e36eba53c3d5cf477c85136cf30b42
    BUG: 923540
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6774
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e435b4b059946fa823b2e22e29899cb256a48bef
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Jan 15 11:47:26 2014 +0530

    cluster/afr: Change default_value for option self-heal-daemon
    
    Change-Id: Ic3c8e179a63e82a4e416aea620796f8bb3236c7c
    BUG: 1052759
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6706
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit add56c1fd5c4ca13ebd6c84c458383d727cb2a3c
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Dec 27 17:54:50 2013 +0530

    tests: Add rpc coverage tests.
    
    1. Moves rpc-coverage.sh from extras/ to tests/basic/
    2. Fixes a symlink test
    
    Change-Id: I2fb8f8441434acfd7bd7fff72deedfbd2410d08c
    BUG: 764966
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6609
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 3a35e939ec811926f810afd792979f526f8dcce9
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Jan 23 12:40:09 2014 +0530

    features/gfid-access: fix lookup on .gfid/<parent>/bname
    
    In gfid translator, lookup was not handling the case when
    the lookup is sent on .gfid/<parent>/bname. In this case,
    we flip with fake inode of the parent with the real inode
    in loc and send it downwards.
    
    Change-Id: I639ff1dce10ffc045da419e333d455e208b6a0f0
    BUG: 1057881
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6795
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f05607fe05f7189dc65a6f328f83db0cbb946426
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Dec 23 14:54:05 2013 +0530

    mgmt/glusterd: make sure quota enforcer has established connection with quotad before marking quota as enabled.
    
    without this patch there is a window of time when quota is marked as
    enabled in quota-enforcer, but connection to quotad wouldn't have been
    established. Any checklimit done during this period can result in a
    failed fop because of unavailability of quotad.
    
    Change-Id: I0d509fabc434dd55ce9ec59157123524197fcc80
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6572
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a10100a4b8501d15c83b416b932d8d786ea550fb
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Sat Nov 9 13:44:18 2013 +0530

    features/quota: maintain correct link_count in ancestry building
    codepath.
    
    Ancestry building codepath can be executed simultaneously when a file
    has hardlinks. So, following fixes are needed:
    
    * modify local->link_count under locks in ancestry building codepath.
    * before invoking check_limit on newly constructed parents,
      link_count should not be set, but instead incremented by as many
      number of new invocations of check_limit.
    * decrementing link_count and the check whether the count has hit zero
      to resume the waiting call_stub should be atomic.
    
    Change-Id: I6f52e50547362a5ded6bd9f085570223aea372d1
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6491
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 49eb5ea29cf8d6eab0c5f60d70fe8d6a0113b61e
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Dec 2 09:32:53 2013 +0530

    features/quota: remove in-memory accounting of files in enforcer
    
    Accounting was done in enforcer (though marker is the ultimate source
    of truth) to offset cached directory size becoming stale. However,
    with enforcer being moved to brick we can no longer maintain correct
    cluster wide size for a directory. Hence removing accounting code from
    enforcer.
    
    Change-Id: I5ea94234da4da85ed5f5ced1354d8de3454b3fcb
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6434
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9a34ea6a0a95154013676cabf8528b2679fb36c4
Author: Anand Avati <avati@redhat.com>
Date:   Fri Jan 24 18:30:32 2014 -0800

    tests: support regex in EXPECT constructs
    
    Instead of just strings, provide the ability to specify a regex
    of the pattern to expect
    
    Change-Id: I6ada978197dceecc28490a2a40de73a04ab9abcd
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6788
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d9fbebde0d2ae166c750121f807c440f6ea65478
Author: Ira Cooper <ira@samba.org>
Date:   Fri Jan 24 11:24:28 2014 -0500

    glusterd: Free op_errstr before it goes out of scope.
    
    Also removed the NULL check on path_list, as it shouldn't be needed.
    
    Change-Id: I5b655f7b383f301afa8fc1c1c09b31e2afe47f0f
    CID: 1138527
    BUG: 789278
    Signed-off-by: Ira Cooper <ira@samba.org>
    Reviewed-on: http://review.gluster.org/6784
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c0c1210ffd5a45a47a3ad6a61545145f1a8e129c
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Nov 4 16:21:14 2013 +0530

    cluster/dht: set op_errno correctly during migration.
    
    Change-Id: I65acedf92c1003975a584a2ac54527e9a2a1e52f
    BUG: 1010241
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6219
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0f6fb218e41e3f5d2a1b76b217197b2ca7597ff7
Author: Ira Cooper <ira@samba.org>
Date:   Fri Jan 24 09:25:58 2014 -0500

    nfs/server: Logic error in mount tab handling.
    
    This error likely causes a double free and also a memory leak.
    
    Change-Id: I299209a8b5bf8aaf487e52e9a4f00948e1d40eb5
    CID: 1124703
    BUG: 789278
    Signed-off-by: Ira Cooper <ira@samba.org>
    Reviewed-on: http://review.gluster.org/6778
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 580d91eb563e8d8a9eb11dbe1c285541c70dbe16
Author: Ira Cooper <ira@samba.org>
Date:   Fri Jan 24 09:54:19 2014 -0500

    glusterd: Free leaked error message.
    
    The way the previous code was written you couldn't tell if the string was
    from the data area, or allocated, so we switched how the error message
    is printed, and now free unconditionally.
    
    Change-Id: Ia83cf9893acdfb5d537a61cc0bbf4aa7689e483d
    CID: 1124704
    BUG: 789278
    Signed-off-by: Ira Cooper <ira@samba.org>
    Reviewed-on: http://review.gluster.org/6779
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1968ec12e62a22fc6e55c4bcc7170d036bf28932
Author: Ira Cooper <ira@samba.org>
Date:   Tue Jan 21 22:46:59 2014 -0500

    mgmt: Fix memory leak of brickid from gf_asprintf.
    
    No GF_FREE, so one was put into the return path with proper checking.
    
    Change-Id: Idde2803608409dcbf216062f83b7f4493946ba70
    CID: 1124718
    BUG: 789278
    Signed-off-by: Ira Cooper <ira@samba.org>
    Reviewed-on: http://review.gluster.org/6755
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c0ac21222383315b9fe84ac7c0afdf01e3ecef7b
Author: Jose A. Rivera <jarrpa@redhat.com>
Date:   Fri Jan 24 10:00:02 2014 -0600

    libgfapi: Remove useless call to lstat
    
    There's no need to lstat cmd_args->volfile, since we already
    check to see if fopen fails. The error message was largely the
    same.
    
    BUG: 789278
    CID: 1124869
    
    Change-Id: I10827154b32c72d2e4a1ab0d3c1e464f8af6ffee
    Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-on: http://review.gluster.org/6783
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8814fdafab377139cdf3863096234f4d5b6e543e
Author: Jose A. Rivera <jarrpa@redhat.com>
Date:   Fri Jan 24 09:56:17 2014 -0600

    libgfapi: Fix pointer dereference before NULL check
    
    ctx is not checked for NULL before it is dereferenced, though the
    check in "err" seems to suggest we should guard against it.
    
    BUG: 789278
    CID: 1124827
    
    Change-Id: I6ed0b42992af5f370cce9aa2feb56811cdd54b42
    Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-on: http://review.gluster.org/6782
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8a21f10ad373dad117557555a7db43d489d05b28
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Nov 27 11:48:29 2013 +0530

    features/quota: use STACK_WIND_TAIL when quota is turned off.
    
    Change-Id: I8a0b7f3a1995a72560c210efbad1eaafb0bdf329
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6373
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 48b8186bdc2f5e45b58aadf849b2bd60c9a77330
Author: Dawit Alemu <dalemu@redhat.com>
Date:   Mon Dec 30 22:59:39 2013 -0500

    cli: Add options to the CLI that let the user control the reset of
    stats
    
    "volume profile info" automatically clears incremental stats. There
    isn't a command to:
    - fetch stats without clearing incremental stats and
    - clear cumulative and incremental stats
    
    This change introduces two arguments (i.e. peek and clear). 'clear'
    will wipe both incremental and cumulative stats. 'peek' fetches stats
    without wiping incremental stats.
    
    'volume profile info peek' - fetches incremental and cumulative stats
                                 without wiping incremental stats
    
    'volume profile info incremental peek' - fetches incremental stats
                                         without wiping incremental stats
    
    'volume profile info clear' - clears both incremental and cumultiave
                                  stats
    
    Change-Id: I91834515ad672eca5f882809941147d7d997c4c9
    BUG: 1047416
    Signed-off-by: Dawit Alemu <dalemu@redhat.com>
    Reviewed-on: http://review.gluster.org/6620
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bb63256b7ea1f186bbe3fae9040a6c191c9d6544
Author: Jose A. Rivera <jarrpa@redhat.com>
Date:   Wed Jan 22 21:51:42 2014 -0600

    libgfapi: Fix pointer dereference before NULL check
    
    Call to dict_keys_join dereferences xattr before it is checked
    for NULL. Restructured the function to check for NULL earlier and
    call dict_unref only when needed.
    
    BUG: 789278
    CID: 1124826
    
    Change-Id: I732fa304ad6f3b921c589832d13f73bbd36f589c
    Signed-off-by: Jose A. Rivera <jarrpa@redhat.com>
    Reviewed-on: http://review.gluster.org/6763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4ac61e7354d0c79e235e1b3be269a989ee0a83e6
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Thu Jan 23 15:37:09 2014 -0600

    cluster/dht: goto statements may cause loop exit before memory is freed.
    
    Memory is allocated at the top of the while loop via a call to
    gf_strdup(), but there are several goto calls that exit the loop, and
    the memory is not freed before each of those calls to goto.  This fix
    moves the final call to GF_FREE() higher in the loop so that the memory
    is correctly freed.
    
    Two variables, dup_str and str_tmp1, point to portions of the allocated
    memory.  Neither are used past the final call to GF_FREE( dup_str ).
    
    BUG: 789278
    CID: 1124780
    
    Change-Id: Id24b80cdbfd8b8855c80fffec63d7fce98cbed4a
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6771
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3340a896a15fdfbfff2777f3f53a472eb62ae2e9
Author: Christopher R. Hertel <crh@redhat.com>
Date:   Thu Jan 23 13:43:14 2014 -0600

    cluster/stripe: Remove redundant code blocks
    
    This appears to have been a cut&paste error.  The same set of 12 lines
    was repeated three times, causing a pointer to allocated memory to be
    overwritten twice resulting in a memory leak.
    
    This patch removes the redundant code.
    
    BUG: 789278
    CID: 1128915
    
    Change-Id: I3e4a3703b389c00e2a4e99e0a7368c5a3dda74d0
    Signed-off-by: Christopher R. Hertel <crh@redhat.com>
    Reviewed-on: http://review.gluster.org/6769
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 460ed4184801d5346c58cc32a34704910345a184
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 23 12:12:07 2014 +0100

    features/compress: rename "compress" option to "network.compression"
    
    Prevent mistaking the "compress" options for storage (at rest)
    compression. The cdc-xlator is implemented to support compressing of
    network traffic (READ and WRITE FOPs).
    
    URL: http://www.gluster.org/community/documentation/index.php/Features/On-Wire_Compression_+_Decompression
    Change-Id: I9fedf4106dcb226d135ab92e4b533aff284881d7
    BUG: 1053670
    CC: Venky Shankar <vshankar@redhat.com>
    CC: Prashanth Pai <ppai@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6765
    Reviewed-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 057e292380cc763ddd4a737d84f406406eaf6d36
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jan 23 18:18:02 2014 +0100

    protocol: pass the size of the data in the WRITE on-wire FOP
    
    Capturing GlusterFS traffic with tcpdump and displaying it in Wireshark
    shows that the size of all WRITEs are 0 bytes. It seems that the
    attribute is not used, and the size is calculated an other way.
    
    Even if the size attribute is not used (yet), it should be set correctly
    to prevent confusing while debugging network traffic with Wireshark or
    other tools.
    
    Note that the on-wire format is not being changed with this patch. The
    size is already part of the structure that is exchanged between the
    client and server.
    
    Change-Id: I9d67fe17bf203672116dea4948328e2af4004677
    BUG: 1057264
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6766
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vikhyat Umrao <vumrao@redhat.com>

commit 60b5f5cc2cb5c23ba852ad20a84328338d0546ae
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Dec 16 23:55:47 2013 +0530

    gfid-access: fix the issue of entry creation with wrong gfid
    
    * dict_set was happening with a string instead of 'uuid_t' causing
      entry creations to happen with wrong gfid
    
    * revalidate was causing excessive ESTALE logs as lookup was
      happening on '.gfid/' path itself causing server to become clueless
    
    Change-Id: I3b76ce7fdec9c2ff785be21f506f859f489f80f0
    BUG: 1054199
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/6520
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit ed2da47115fa9394357fd290894d1a1efc2ad750
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Nov 7 12:52:23 2013 +0530

    geo-rep: get new config value after config value reset
    
    When config.read is called it preserves the previous values
    from the the previously opened config file.
    
    For example
    import ConfigParser
    config = ConfigParser.RawConfigParser()
    config.read("defaults.conf")
    config.read("preferences.conf")
    
    When change in config file is identified it will open new
    instance of config to avoid getting old config values.
    
    Change-Id: Iec677e61ebd2c59c95aea94481f569d78bd913e4
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6747
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a0fbd41d2b10829503df1826bf2c98dc347de739
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Jan 17 16:45:55 2014 +0530

    geo-rep: Fix no error when slave size less than master size
    
    in df command output, default block-size is 1K, but BUFFER_SIZE is
    in bytes, so verify will succeed even if slave size is less than
    master size.
    
    Added -B1 to df command(that is --block-size=1) to get all values in
    bytes.
    
    BUG: 1056518
    Change-Id: I2384d2a6f2505d967e0538b95fbf111c15b26f30
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6746
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6c9fe8fa8896c5f4fbe8c9bac6c2c7f9add92a0b
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Dec 2 15:49:58 2013 +0530

    cluster/dht: Set quota limit key in dht_selfheal of dirs.
    
    Also fixed check in dht_is_subvol_in_layout to check if the
    layouts are zero'ed out.
    
    Change-Id: I4bf8ebf66d3ef1946309b6c9aac9e79bf8a6d495
    BUG: 969461
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6392
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7bea98fa5845ced670d7bb2d9b1336c03855a798
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Jan 21 22:03:41 2014 -0800

    storage/posix: HANDLE_PFX is redundant use GF_HIDDEN_PATH instead
    
    GF_HIDDEN_PATH usage would help in better readability of the code
    and avoids bugs produced from redundant macro constants.
    
    Change-Id: I2fd7e92e87783ba462ae438ced2cf4f720a25f5c
    BUG: 990028
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6756
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e48c5f8a84a1ec27492bcede0a028755a440be45
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Dec 18 00:02:58 2013 +0530

    geo-rep: optimizing update stime after directory synchronization
    
    Since xsync crawl generates new changelog when number of entries
    reaches 8K or when directory is reached. If a directory has number
    of files less than 8K then respective changelog file will have less
    entries. Since xsync generated changelog files processed one after
    the other, so syncjobs are underutilized. hence low bandwidth
    utilization.
    
    With this patch, changelog will be generated for 8K entries only,
    but stime will be accumulated. Multiple dirs stime will be
    updated together since the generated changelog will have entries
    accross the dirs.
    
    Change-Id: Ib0b40962a070f855f47f887d0840e412fb7928e1
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6744
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 505463a476c948bafd319c40376ba5bb4ac8ec78
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Jan 21 16:39:12 2014 +0100

    Create /var/run/gluster at install time
    
    BUG: 764655
    Change-Id: I67c33984a797bc92c7035724695c5ef2bbdf5267
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6750
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 79683794c2ee9c6b5c1182e2a378598c2037a9ff
Author: Susant Palai <spalai@redhat.com>
Date:   Thu Dec 12 06:20:55 2013 +0000

    quota: filter glusterfs quota xattrs
    
    Change-Id: I86ebe02735ee88598640240aa888e02b48ecc06c
    BUG: 1040423
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/6490
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit b2dfa011a3fdcb7d22764d143517d0fbd1c2a201
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Jan 22 14:47:23 2014 +0100

    Fix build with c99 compilers
    
    BUG: 764655
    Change-Id: If5dfdc9c7427bd3d39d8da8f79e33ae2da6a3137
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6034
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6c6c7eba87190bfe3c721faaa190949ff611405b
Author: Anand Avati <avati@redhat.com>
Date:   Sun Jan 19 19:44:06 2014 -0800

    locks: set @lock->frame = NULL when lock is granted
    
    This way disconnect cleanup code can differentiate which locks
    are granted vs blocked.
    
    Change-Id: I2a835c6865b6c804231d852953ea84eeccef35a3
    BUG: 849630
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6730
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 57edad947b4c43d7c8f05bac45c8e63c788f43ca
Author: surabhi <sbhaloth@redhat.com>
Date:   Tue Jan 21 14:55:29 2014 +0530

    core:Fixing NULL dereference issue.
    
    1.Checking of frame before calling STACK_DESTROY (frame->root)
    Signed-off-by: surabhi <sbhaloth@redhat.com>
    
    Change-Id: I21d27a8b4e556c00cd123afe8512e010a1a1f80d
    BUG: 789278
    Signed-off-by: surabhi <sbhaloth@redhat.com>
    Reviewed-on: http://review.gluster.org/6749
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d0cd37817c45c1f375a8230533cc66821bfe9b6e
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Jan 22 00:45:01 2014 +0530

    rpc: use GF_FREE when a string is gf_strdup'd.
    
    Change-Id: I522c30a600e712be9cc09393104e228e4d8e13f5
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6752
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2fe405c808fdbc9109bced9ec52be9d79ca321e7
Author: Ira Cooper <ira@samba.org>
Date:   Tue Jan 21 20:42:22 2014 -0500

    glusterd: Fix memory leak of hostname.
    
    The if causes a goto that allows the GF_FREE to be missed.
    
    BUG: 789278
    Change-Id: Ic2c20b7623ea880b8ab2d11ebe510a62633a036d
    CID: 1124785
    Signed-off-by: Ira Cooper <ira@samba.org>
    Reviewed-on: http://review.gluster.org/6754
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fdc82748a1d1f063e3c11c840e6ec54ddf0fe0e1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jan 15 14:22:44 2014 +0100

    build: Install /var/lib/glusterd/groups/virt by default
    
    /var/lib/glusterd/groups/virt is not installed by default, but that
    should be the case. It is provided as extras/groups-virt.example.
    
    "make install" should correctly install this file, and the rpm packages
    should include it.
    
    Change-Id: I5284306cfc2882e3147bd72f496ad29db906fcb2
    BUG: 1053854
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6717
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 17c4fb2d04f84b5632983866e8bddfbd7d77a054
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Oct 28 19:14:49 2013 +0530

    quota: get directory size before enforcing quota on rename
    
    Change-Id: If18cab5992ddc91457782786942971deb1b51ead
    BUG: 1023974
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6155
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b2ef4e3d11af79a765406672bb6ca070b40c9b64
Author: Susant Palai <spalai@redhat.com>
Date:   Mon Jan 6 12:38:08 2014 +0000

    quota: unmount quota aux mount for volume stop
    
    Previously df -h used to display "Transport end point not connected"
    for quota auxiliary mount after volume is stopped. This patch
    unmounts the auxiliary mount when the volume is stopped in all peer
    nodes for that volume.
    
    Change-Id: I78abb44386cd8242a532f92c13df8bdb57c78e31
    BUG: 1049323
    Signed-off-by: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/6656
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8d55c25f158921b508bff0e7f25158991913f922
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Dec 11 09:33:53 2013 +0530

    syncop: Change return value of syncop
    
    Problem:
    We found a day-1 bug when syncop_xxx() infra is used inside a synctask with
    compilation optimization (CFLAGS -O2).
    
    Detailed explanation of the Root cause:
    We found the bug in 'gf_defrag_migrate_data' in rebalance operation:
    
    Lets look at interesting parts of the function:
    
    int
    gf_defrag_migrate_data (xlator_t *this, gf_defrag_info_t *defrag, loc_t *loc,
                            dict_t *migrate_data)
    {
    .....
    code section - [ Loop ]
            while ((ret = syncop_readdirp (this, fd, 131072, offset, NULL,
                                           &entries)) != 0) {
    .....
    code section - [ ERRNO-1 ] (errno of readdirp is stored in readdir_operrno by a
    thread)
                    /* Need to keep track of ENOENT errno, that means, there is no
                       need to send more readdirp() */
                    readdir_operrno = errno;
    .....
    code section - [ SYNCOP-1 ] (syncop_getxattr is called by a thread)
                            ret = syncop_getxattr (this, &entry_loc, &dict,
                                                   GF_XATTR_LINKINFO_KEY);
    code section - [ ERRNO-2]   (checking for failures of syncop_getxattr(). This
    may not always be executed in same thread which executed [SYNCOP-1])
                            if (ret < 0) {
                                    if (errno != ENODATA) {
                                            loglevel = GF_LOG_ERROR;
                                            defrag->total_failures += 1;
    .....
    }
    
    the function above could be executed by thread(t1) till [SYNCOP-1] and code
    from [ERRNO-2] can be executed by a different thread(t2) because of the way
    syncop-infra schedules the tasks.
    
    when the code is compiled with -O2 optimization this is the assembly code that
    is generated:
     [ERRNO-1]
    1165                        readdir_operrno = errno; <<---- errno gets expanded
    as *(__errno_location())
       0x00007fd149d48b60 <+496>:        callq  0x7fd149d410c0 <address@hidden>
       0x00007fd149d48b72 <+514>:        mov    %rax,0x50(%rsp) <<------ Address
    returned by __errno_location() is stored in a special location in stack for
    later use.
       0x00007fd149d48b77 <+519>:        mov    (%rax),%eax
       0x00007fd149d48b79 <+521>:        mov    %eax,0x78(%rsp)
    ....
     [ERRNO-2]
    1281                                        if (errno != ENODATA) {
       0x00007fd149d492ae <+2366>:        mov    0x50(%rsp),%rax <<-----  Because
    it already stored the address returned by __errno_location(), it just
    dereferences the address to get the errno value. BUT THIS CODE NEED NOT BE
    EXECUTED BY SAME THREAD!!!
       0x00007fd149d492b3 <+2371>:        mov    $0x9,%ebp
       0x00007fd149d492b8 <+2376>:        mov    (%rax),%edi
       0x00007fd149d492ba <+2378>:        cmp    $0x3d,%edi
    
    The problem is that __errno_location() value of t1 and t2 are different. So
    [ERRNO-2] ends up reading errno of t1 instead of errno of t2 even though t2 is
    executing [ERRNO-2] code section.
    
    When code is compiled without any optimization for [ERRNO-2]:
    1281                                        if (errno != ENODATA) {
       0x00007fd58e7a326f <+2237>:        callq  0x7fd58e797300
    <address@hidden><<--- As it is calling __errno_location() again it gets the
    location from t2 so it works as intended.
       0x00007fd58e7a3274 <+2242>:        mov    (%rax),%eax
       0x00007fd58e7a3276 <+2244>:        cmp    $0x3d,%eax
       0x00007fd58e7a3279 <+2247>:        je     0x7fd58e7a32a1
    <gf_defrag_migrate_data+2287>
    
    Fix:
    Make syncop_xxx() return (-errno) value as the return value in
    case of errors and all the functions which make syncop_xxx() will need to use
    (-ret) to figure out the reason for failure in case of syncop_xxx() failures.
    
    Change-Id: I314d20dabe55d3e62ff66f3b4adb1cac2eaebb57
    BUG: 1040356
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6475
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c2b09dc87e0763dfdff1e93a1dc6cc4c05f091bf
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Aug 17 13:01:23 2013 -0700

    build: Start using library versioning for various libraries
    
    According to libtool three individual numbers stand for
    CURRENT:REVISION:AGE, or C:R:A for short. The libtool
    script typically tacks these three numbers onto the end
    of the name of the .so file it creates. The formula for
    calculating the file numbers on Linux and Solaris is
    
       /path/to/library/<library_name>.(C - A).(A).(R)
    
    As you release new versions of your library, you will
    update the library's C:R:A. Although the rules for changing
    these version numbers can quickly become confusing, a few
    simple tips should help keep you on track. The libtool
    documentation goes into greater depth.
    
    In essence, every time you make a change to the library and
    release it, the C:R:A should change. A new library should start
    with 0:0:0. Each time you change the public interface
    (i.e., your installed header files), you should increment the
    CURRENT number. This is called your interface number. The main
    use of this interface number is to tag successive revisions
    of your API.
    
    The AGE number is how many consecutive versions of the API the
    current implementation supports. Thus if the CURRENT library
    API is the sixth published version of the interface and it is
    also binary compatible with the fourth and fifth versions
    (i.e., the last two), the C:R:A might be 6:0:2. When you break
    binary compatibility, you need to set AGE to 0 and of course
    increment CURRENT.
    
    The REVISION marks a change in the source code of the library
    that doesn't affect the interface-for example, a minor bug fix.
    Anytime you increment CURRENT, you should set REVISION back to 0.
    
    Change-Id: Id72e74c1642c804fea6f93ec109135c7c16f1810
    BUG: 862082
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5645
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1ffc3ac9639e25c91ac26488b648d5523becb08e
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Tue Jan 14 23:50:51 2014 +0530

    core: Coverity issue "Use of uninitialized scalar variable"
    
    Issue:
    1. In "unlink (export_path)" "export_path" might contain an arbitrary value left from earlier
     computations.
    2. In "(msg[0] != '\0')"  msg might contain an arbitrary value
    
    Change-Id: Icca8f557fd6b5e046dff1d5a84a72061975868d0
    BUG: 789278
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6701
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 63638748d744377d899e9ee0b5e7831d7c1c2496
Author: Varun Shastry <vshastry@redhat.com>
Date:   Fri Dec 27 15:39:19 2013 +0530

    features/quota: Handle the corner case in statfs call
    
    Problem: Even though limit is not set quota used to send 'quota-deem-statfs'
    key in the dictionary resulting in incorrect calculations.
    
    Change-Id: I643cb35cca6648e40f1c745135280876958ddaa9
    BUG: 1046894
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6607
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>

commit c0a14c00bfb9152abdb5cedcf5aa1b9ed9a6ac6a
Author: Varun Shastry <vshastry@redhat.com>
Date:   Fri Nov 29 14:49:33 2013 +0530

    features/quota: Make grep search more accurately
    
    The hook script was searching the info file for "features.quota" to know the
    quota status (enable/disabled). When features.quota-deem-statfs the grep is not
    accurate. Fixed this issue.
    
    Change-Id: I4104a93c1c1e0ac9fd7ef7bfef993425ab50e651
    BUG: 969461
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6380
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a20e79ab3d0827936b679689055ea453c1d01abb
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Dec 17 16:04:46 2013 +0530

    quota: fix recording of last alert log message
    
    PROBLEM:
    
    Alert log messages, corresponding to disk usage crossing soft-limit on a
    directory, weren't being logged as often as expected.
    
    CAUSE:
    
    The mechanism in place to log alert messages, once every alert-time
    seconds, set the previous logged time incorrectly.
    
    FIX:
    
    Update previous logged time only if we logged an alert message, ie. when
    the "time was right" to alert.
    
    Change-Id: Iafcb7be11e3240e2d04b0bb29ddb88e4f4a1bd25
    BUG: 969461
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6532
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 39968c09626074b34b62541af5940f44ba70cc06
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Oct 22 16:12:58 2013 +0530

    features/quota: Metadata cleanup
    
    Quota and marker uses 'trusted.glusterfs.quota*' and 'trusted.pgfid*' xattrs to
    store its configurations and accounting information and also to build the
    parent inode chain in case of absense of path.
    
    Problem:
    After disabling and then enabling quota back, the xattrs may contain stale data
    leading to impaired accounting and thus improper enforcement.
    
    Solution:
    Clean up all the quota related xattrs after quota disable.
    
    Marker xlator implements a virtual xattr to cleanup quota and pgfid xattrs. In
    this approach glusterd mounts an auxiliary mount and sends the below command to
    all the files by crawling the mountpoint.
    
     #setfattr -n "glusterfs.quota-xattr-cleanup" -v 1 <path/to/file>
    
    Credit:
    Krishnan Parthasarathi <kparthas@redhat.com>
    Varun Shastry          <vshastry@redhat.com>
    Change-Id: I9380eca58a285dc27dd572de1767aac8f2cd8049
    BUG: 969461
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6369
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 902276ebd7d6d7b3158d7c4796cdd392b6e958c3
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Jan 9 17:03:37 2014 +0530

    test: Remove unnecessary code from test.
    
    We have not meddled with mount point to check for it again.
    
    Change-Id: I88eed777b6573a320065b9e14c2031db964e36d0
    BUG: 1053362
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6675
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c9008fe6a1a4d9c25c4b11804bcc9e5b6edf9bec
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Tue Jan 14 12:35:54 2014 +0530

    libgfapi: Fixing possible dereferencing of null pointer "glfd"
    
    Fix: Putting a check so that pointer derefrence does not happen
    when "gfld" is null
    
    Change-Id: I281b10be445bbeec3a2728fc139d5ac94372e5b6
    BUG: 789278
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6697
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit de557c602c8f0480686c4d560f012924ee0de936
Author: ndarshan <dnarayan@redhat.com>
Date:   Fri Dec 27 03:11:19 2013 -0500

    cli: Addition of new child elements under brick in volume info xml.
    
    Added new child elements; name and hostUuid under brick in
    volume info xml where name and host uuid of the bricks are stored.
    This does not break backward compatibility as the old value under
    brick is not removed.
    
    Change-Id: Ib9e388889c8dc0c7cd34dcc1871a59003f982f36
    Signed-off-by: ndarshan <dnarayan@redhat.com>
    Reviewed-on: http://review.gluster.org/6604
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dd1f4a480511c4785d004c06dd9c41ba54f05143
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Mon Dec 30 18:06:56 2013 +0530

    dht: Ignore directory with missing xattrs, which have err == 0, and start == stop
    
    From the history (Patch: http://review.gluster.org/4668/)
    
    When subvols-per-directory is < available subvols, then there are layouts
    which are not populated. This leads to incorrect identification of holes or
    overlaps. We need to ignore layouts, which have err == 0, and start == stop.
    In the current scenario (start == stop == 0).
    
    Additionally, in layout-merge, treat missing xattrs as err = 0. In case of
    missing layouts, anomalies will reset them.
    
    For any other valid subvoles, err != 0 in case of layouts being zeroed out.
    Also reverted back dht_selfheal_dir_xattr, which does layout calculation only
    on subvols which have errors.
    
    Change-Id: Idb72a869f1a6f103046bb7e6fe0019f6ac853fd4
    BUG: 1047331
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6618
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 260e817b8a652ddb705808098da1e07e3660f4c7
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Tue Jan 14 11:21:44 2014 +0530

    gNFS: Set default outstanding RPC limit to 16
    
    With 64, NFS server hangs with large I/O load (~ 64 threads writing
    to NFS server). The test results from Ben England (Performance expert)
    suggest to set it as 16 instead of 64.
    
    Change-Id: I418ff5ba0a3e9fdb14f395b8736438ee1bbd95f4
    BUG: 1008301
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6696
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: ben england <bengland@redhat.com>

commit f3e227d525ee04a3ea0196f7a15aa9b1a8f8cae1
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Tue Jan 14 23:24:50 2014 +0530

    geo-rep: Fixing null pointer dereference of "op_value"
    
    Change-Id: Id39743eaa5a52cc7fd4e2a1378a23384f5ef1fed
    BUG: 789278
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6700
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>

commit f139fc7e44da27670e90bd7ba55ff80e7c8b8ecd
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jan 13 12:42:31 2014 +0530

    cli: Don't override cli mode when stdin in not a tty
    
    Change-Id: I801c6e6ecd6c5a91e487e8e54ec5f684d450a080
    BUG: 1047378
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6687
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2f499e85a4ae0ac1e84785daa60a5bbfe979cc7f
Author: Kotresh H R <khiremat@redhat.com>
Date:   Wed Jan 8 10:52:28 2014 +0530

    glusterd/geo-rep : Allow volume to stop if geo-rep is not active.
    
    In staging phase of volume stop, code is added to read the state_file
    for each slave of the master to which the volume belongs. If any of the
    geo-rep session is active with at least one slave, volume is not
    allowed to stop else it is allowed.
    
    Change-Id: I4a01a357fc86b872e9635b3d19998cdbd9545114
    BUG: 1049727
    Signed-off-by: Kotresh H R <khiremat@redhat.com>
    Reviewed-on: http://review.gluster.org/6663
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7d89ec77763dc5076379753c736f7fce2bedd9ec
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jan 2 20:11:19 2014 +0530

    socket: propogate connect failure in socket_event_handler
    
    This patch prevents spurious handling of pollin/pollout events on an
    'un-connected' socket, when outgoing packets to its remote endpoint are
    'dropped' using iptables(8) rules.
    
    For eg,
     iptables -I OUTPUT -p tcp --dport 24007 -j DROP
    
    
    Change-Id: I1d3f3259dc536adca32330bfb7566e0b9a521e3c
    BUG: 1048188
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6627
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 54bf0ba4698a2d46db3485cc12ae04dd90349570
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Jan 3 11:59:43 2014 +0530

    consolidate code for #ifdef HAVE_LINKAT usage
    
    sys_link() now does
    
    ifdef HAVE_LINKAT
            linkat (...)
    else
            link (...)
    endif
    
    Use sys_link() in all places where we previously had the
    conditional behavior.
    
    Change-Id: I8bce5ac1175efd2ba7ab4bb5b372f6d1e0365d28
    BUG: 764655
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6633
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3af42583dd804371952d61e9d7ff4c640e67ba0d
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Jan 12 22:39:14 2014 +0530

    storage/posix: UNWIND right op_error and op_errno in *setxattr()
    
    1. errno was being set after gf_log() in posix_{f}handle_pair, this
    would cause errno to be overwritten.
    
    2. dht would expect -1 for indication of failure in setxattr
    callback (dht_err_cbk()). posix_{f}setxattr has been changed to set
    op_ret as -1 instead of -op_errno.
    
    3. dict_foreach() has been changed to return an error if the invoked
    fn() returns < 0.
    
    Bug report and test case credits to Zorro Lang <zlang@redhat.com>
    
    Change-Id: I96c15f12a5d7717b7584ba392f390a0b4f704a98
    BUG: 1051896
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6684
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit aa3b01533efcd85fc1e654ac14a03ab8e1d5bbab
Author: Anand Avati <avati@redhat.com>
Date:   Tue Dec 3 16:30:45 2013 -0800

    locks: various fixes
    
    - implement ref/unref of entry locks (and fix bad pointer deref crashes)
    - code cleanup and deleted various data types
    - fix improper read/write lock conflict detection in entrylk
    - fix indefinite hang of blocked locks on disconnect
    - register locks in client_t synchronously, fix crashes in disconnect path
    
    Change-Id: Id273690c9111b8052139d1847060d1fb5a711924
    BUG: 849630
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6638
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ce86c132347f0a788ab50ffbd6795a2eb982074e
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Jan 3 13:54:25 2014 +0530

    cluster/afr: Unable to self heal symbolic links
    
    Problem:
    Under the entry self heal, readlink is done at the
    source and sink. When readlink is done at the sink,
    because link is not present at the sink, afr expects
    ENOENT. AFR translator takes decisions for new link
    creation based on ENOENT but server translator is modified
    to return ESTALE because of which afr xlator is not able
    to heal.
    
    Fix:
    The check for inode absence at server includes ESTALE as
    well.
    
    Change-Id: I319e4cb4156a243afee79365b7b7a5a7823e9a24
    BUG: 1046624
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/6599
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5a26daaea96aa3f7855b8d75b6568449f5466cc2
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri Jan 10 11:57:05 2014 +0530

    gNFS: Server sets ACL mask wrongly in GETACL reply
    
    FIX:
    1. Set the ACL mask what was requested by client
    2. Validate the ACL mask in SETACL routine
    
    Change-Id: Icb8576a8fe2684e0beaf94e8db6a92bc70bbfe7f
    BUG: 1051865
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6683
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f7fcbc0ffe0e56f81f73f99e0d4825cd95ca0014
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Dec 9 17:51:40 2013 +0530

    mgmt/glusterd: Improve the description in volume set help output
    
    Change-Id: I785648970f53033a69922c23110b5eea9e47feb3
    BUG: 1046030
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6573
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6992e4e37df9b12aa3582bb71341e9591d9f6e20
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Sun Jan 5 01:01:39 2014 +0530

    glusterd: Comments for missing break in switchcase of glusterd_op_stage_quota
    
    Change-Id: I3ac5b73b9703a390f1de9cd6a999dfd8ec27d379
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6645
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 2edf1ec797e6f56515d0208be152d18ca6e71456
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Dec 30 09:59:18 2013 +0530

    glusterd: Relocate rebalance sockfile
    
    The defrag sockfile was moved from priv->workdir to
    DEFAULT_VAR_RUN_DIRECTORY. The format for the new path of the defrag
    sockfile is 'DEFAULT_VAR_RUN_DIRECTORY/gluster-rebalance-<vol-id>.sock'.
    
    This was needed because the earlier location didn't have a fixed length
    and could exceed UNIX_PATH_MAX characters. This could lead to the
    rebalance process failing to start as the socket file could not be
    created.
    
    Also, for keeping backward compatiblity, glusterd_rebalance_rpc_create
    will try both the new and old sockfile locations when attempting
    reconnection.
    
    Change-Id: I6740ea665de84ebce1ef7199c412f426de54e3d0
    BUG: 1049726
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6616
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a2f772de44cc09d595005f4d3316fbd0f37c46b8
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Fri Jan 10 12:26:29 2014 +0530

    MAINTAINERS: Update BD
    
    BUG: 1040351
    Change-Id: I2cbbae22e84fe7f8593db22a32ceb87ca97f46da
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6679
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit f9162911e85f95fa2a10d4b70d3f09876bd15adb
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Mon Jan 6 13:37:24 2014 +0530

    libgfapi : Fixing some NULL pointer dereferencing issues.
    
    1. Fixing dereferencing null pointer "gio"
    2. Checking "frame" before calling STACK_DESTROY (frame->root)
    
    Change-Id: If2ce8804a8e9f3f99f71a8c0d13900afb5635072
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6313
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 21ffbf9b92b2478c17f816a8d0418a7cb080998a
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Wed Jan 8 14:25:08 2014 +0530

    geo-rep: Fixing an incorrect memcpy operation.
    
    Currently we are copying a higher size variable to lower size
    variable i.e. copying a NAME_MAX  to PATH_MAX sized variable
    in "memcpy (sts_val->worker_status, monitor_status, strlen(monitor_status));"
    
    Change-Id: I81dca8e81a4aea5545d5982aed20e05a5e08641c
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6667
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2b05c1588ac60af26e1b16f9f27ef8d5e4e50a5f
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Dec 24 08:23:13 2013 -0800

    rpc/auth: Avoid NULL dereference in rpcsvc_auth_request_init()
    
    Code section is bogus!
    ------------------------------------------
    370:       if (!auth->authops->request_init)
    371:              ret = auth->authops->request_init (req, auth->authprivate);
    ------------------------------------------
    
    Seems to have been never been used historically since
    logically above code has never been true to actually execute
    "authops->request_init() --> auth_glusterfs_{v2,}_request_init()"
    
    On top of that under "rpcsvc_request_init()"
    verf.flavour and verf.datalen are initialized from what is
    provided through 'callmsg'.
    ------------------------------------------
            req->verf.flavour = rpc_call_verf_flavour (callmsg);
            req->verf.datalen = rpc_call_verf_len (callmsg);
    
            /* AUTH */
            rpcsvc_auth_request_init (req);
            return req;
    ------------------------------------------
    
    So the code in 'auth_glusterfs_{v2,}_request_init()'
    performing this operation will over-write the original
    flavour and datalen.
    
    ------------------------------------------
          if (!req)
                    return -1;
            memset (req->verf.authdata, 0, GF_MAX_AUTH_BYTES);
            req->verf.datalen = 0;
            req->verf.flavour = AUTH_NULL;
    ------------------------------------------
    
    Refactoring the whole code into a more understandable version
    and also avoiding a potential NULL dereference
    
    Change-Id: I1a430fcb4d26de8de219bd0cb3c46c141649d47d
    BUG: 1049735
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6591
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 88816bf4b2933da8fa2717cb0e25c521895da4e1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 7 15:54:14 2014 +0530

    cluster/afr: Stop index crawl on pending full crawl
    
    Full crawl is executed when index self-heal is useless, like
    disk replacement. So if there are on-going index crawls, they
    should be stopped inorder to start full self-heals.
    
    Change-Id: I9a1545f1ec4ad9999dc08523ce859e4fa152e214
    BUG: 1049355
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6659
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c0767852b3dfad94546a5458bcf4460797cdbf0b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 7 15:23:19 2014 +0530

    cluster/afr: Don't accept heal commands until graph is up
    
    Change-Id: Icca6c23b6a5965f462db8b65af3eb2e141c7cd39
    BUG: 1049355
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6658
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1e26be05c7b344dc8e7f980d0a6ab00695f2f42
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Tue Jan 7 14:22:03 2014 +0530

    gNFS: mnt3_find_export() by pass AUTH check
    
    NFS subdir mount does not respect nfs.rpc-auth-reject option
    in the volume. If the volume is being mounted, then it would
    validate the AUTH by mnt3_check_client_net() but if the client
    is mounting a subdir, the control takes a different code path
    i.e. mnt3_find_export() which does not bother about the AUTH.
    
    FIX:
    Enforce the AUTH check in mnt3_parse_dir_exports() which is
    invoked by mnt3_find_export() for subdir mount.
    
    Change-Id: I6fdd3e6bd6cbd32b0d9ca620cc4c30fdaff9ca30
    BUG: 1049225
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6655
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1e4f2d08f102e9fc1e27ffb5608d4b45c11e0b55
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jan 4 17:29:26 2014 +0100

    build: the main glusterfs package should not provide glusterfs-libs
    
    Because of this incorrect provides, there is no requirement to update
    glusterfs-libs. Most users will get a newer glusterfs-libs when updating
    anyway, but users that manually select RPMs for updating my skip the
    package, which will break their system.
    
    Change-Id: I636dfac3f0a521924f1c2e82948bb513b0a5c9f9
    BUG: 950083
    Fedora-BUG: 1048489
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6642
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b159d0a4c3ed128dc9f018b76c5d4b54a13060b3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Dec 11 10:17:46 2013 +0100

    Add the MAINTAINERS file
    
    Different projects (Linux kernel, QEMU, ...) have a MAINTAINERS file in
    the root of the git repository. This file mostly lists the maintainers
    or main committers for certain files and directories. On occasion it
    would be very helpful to know who to add as a reviewer for proposed
    patches.
    
    Change-Id: Ide68779c7477529808ccb0e7d421db160e3222ea
    BUG: 1040351
    URL: http://lists.nongnu.org/archive/html/gluster-devel/2013-11/msg00045.html
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6480
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 0fbb9c7baf13331d72fc42243cd031c2d7acdbe7
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Thu Jan 2 20:04:46 2014 +0530

    Crypt: Fixing incorrect placement of GF_FREE
    i.e. we are trying access the memory after freeing it using GF_FREE
    
    Change-Id: I2b22fd421131c618bd0d7c246ebf09f14751ad30
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6626
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 79cbf27b9b98d1feebcc2f1db5fc1c976d2c24cf
Author: Atin Mukherjee <amukherj@redhat.com>
Date:   Fri Jan 3 13:36:40 2014 +0530

    Glusterd : glusterd process generates core due to NULL store handle
    
    Problem : glusterd crashed as backtrace revealed that store handle was
    set to NULL.
    
    Solution : In glusterd_store_global_info() function out block the
    handle is dereferenced with out any NULL check which caused this
    segmentation fault. A NULL check is introduced to avoid this. While
    testing this fix, another issue was noticed where GF_ASSERT macro again
    does not gurantee the NULL dereference check and hence this macro call
    has been replaced by GF_VALIDATE_OR_GOTO macro call in places where
    there is a danger of macro getting crashed due to NULL dereference
    check.
    
    Change-Id: Ic301aa45ce4bbdc2da751d2386439df7bb24c016
    BUG: 1040844
    Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
    Reviewed-on: http://review.gluster.org/6619
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d062e09e0c7925f37cbfc42ef42c7fe6804823fe
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Wed Dec 18 14:32:25 2013 +0530

    pathinfo: Provide user namespace access.
    
    Do not allow to setxattr for pathinfo
    This change was missed out when submitted patch: http://review.gluster.org/5101/
    
    Change-Id: Ifd32d95089b9bacc5dee80a8b924bb8713dca8a1
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6535
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 825b976ee30a53e89fe747b4a3ba8f2eb862047c
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Thu Jan 2 20:55:59 2014 +0530

    gNFS: Small memory leak in rpcsvc_drc_init()
    
    1. The routine rpcsvc_drc_init() is only used while initialization of
    NFS xlator. It should just check for nfs.drc option and init DRC feature
    accordingly. If it's set to OFF, then rpcsvc_drc_init() allocates memory
    for svc.drc and set ret value to 0 and goes to out: block where drc is
    leaked.
    
    2. rpcsvc_drc_init() should just allocate svc.drc and init it. Here
    svc.drc can never be valid.
    
    3. If svc.drc gets init'd here, no point of checking for drc type here.
    
    Change-Id: I4085771cdb8c9c15d1b9c548b77929a37f27c124
    BUG: 1047902
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6628
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 311e3868bfdb3f2c1535d5a7cb8f759195457612
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri Jan 3 10:32:16 2014 +0530

    gNFS: Possible SEGV crash in NFS while DRC is OFF
    
    In rpcsvc_submit_generic(), FILE: rpc/rpc-lib/src/rpcsvc.c, while caching
    the reply (DRC), the code does not check if DRC is ON and goes ahead
    assuming DRC is on and try to take a LOCK on drc.
    
    FIX: Put a check on svc->drc by rpcsvc_need_drc().
    
    Change-Id: I52c57280487e6061c68fd0b784e1cafceb2f3690
    BUG: 1048072
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6632
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8ee2420266a0a1c47fcfee0796ef08d93d0797ab
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Jan 3 11:23:02 2014 +0530

    performance/io-cache: reduce the severity of log-message
    
    During a genuine error condition like network outage, the log grows
    with redundant information.
    
    Change-Id: I5a4f2f62da10ef656f14200c4c84a6917b1f0ddd
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 1048084
    Reviewed-on: http://review.gluster.org/6635
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d25d912835e01c40cb00a0ae93d49f68f9b3542b
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jan 2 23:06:39 2014 +0530

    glusterd: update volinfo->subvol_count in newly added peers
    
    Update the subvol_count when a peer imports information about the friend
    volumes.
    
    Change-Id: Id3884bd5727ff22be7ed87f43a1ec1b5fe34813c
    BUG: 1047955
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6629
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f54e9ca3897177ee41b5f5299b94b719448c46cd
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Dec 28 08:31:55 2013 +0100

    Use linkat() instead of link() for portability sake
    
    POSIX does not says wether link(2) on symlink should link on
    symlink itself or on target. Linux use symlink, most other
    systems use target. Using linkat(2) allows the behavior to be
    specified, so that the behavior is portable.
    
    Also fix configure test for NetBSD linkat(2), which ceased to work.
    
    BUG: 764655
    Change-Id: I2633fde3b0828ca8c199e11c827720c513e15852
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6613
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d1f8b7ebc71df415f6b8ff37e9654ecee0d9064c
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Dec 19 14:11:45 2013 +0100

    Use linkat() instead of link() for portability sake
    
    POSIX does not says wether link(2) on symlink should link on
    symlink itself or on target. Linux use symlink, most other
    systems use target. Using linkat(2) allows the behavior to be
    specified, so that the behavior is portable.
    
    Also fix configure test for NetBSD linkata(2), which ceased to work.
    
    BUG: 764655
    Change-Id: Iccd27ac076b7a74e40dcbaa1c4762fd3ad59da5f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6539
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2ce8918759e9676a54791848fd2ac85f48a05016
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Jan 1 21:36:27 2014 +0530

    libglusterfs: Add missing goto in eh_new()
    
    Change-Id: I64bbd8d5d919e78286a0521b62ca75f22ad296fa
    BUG: 795419
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6623
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2401384fbc882c02319881166b299f8e88c7ab55
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 23 18:28:36 2013 +0530

    mount/fuse: Remove duplicate GET_STATE call
    
    Change-Id: I5716cb0e9914f78489e3422a03efc689f5ebc413
    BUG: 952029
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6579
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7e3dd526c62b3a1bb59945efdfed2c2fbbcf9cf9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Dec 23 12:53:32 2013 +0100

    rpc/server: add anonuid and anongid options for root-squash
    
    Introduce new options to modify the behaviour of server.root-squash.
    With server.anonuid and server.anongid the uid/gid can be specified and
    the root user (uid=0 and gid=0) will be mapped to the given uid/gid
    instead of nfsnobody (uid=65534 and gid=65534).
    
    Many thanks to Vikhyat Umrao for writing the majority of the test-case!
    
    Change-Id: I6379a3d2ef52b9b9707f2f6f0529657580c8d779
    BUG: 1043886
    CC: Vikhyat Umrao <vumrao@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6546
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Vikhyat Umrao <vumrao@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d85726d19432384e2c3dd6ceff4b7b4ec3f8f57a
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Dec 23 02:52:12 2013 -0800

    crypt: On calloc failure follow goto statement
    
    At
    --------------------------------------------
    1423	if (local->vec.iov_base == NULL) {
    --------------------------------------------
    
    This condition being true leads to NULL pointer
    to be passed into `memcpy` later at
    
    ----------------------------------------------------
    1432	memcpy((char *)local->vec.iov_base + copied,
    ----------------------------------------------------
    
    Avoid this by clean exit through a goto statement with
    in the conditional.
    
    Change-Id: I2546b7dd634dc251adae8ca39497c4c3ef520f62
    BUG: 1030058
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6576
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Edward Shishkin <edward.shishkin@gmail.com>
    Tested-by: Edward Shishkin <edward.shishkin@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit efcfb60f87f6d5ce4aa8ec7f4cd3bbe51a87f538
Author: Louis Zuckerman <me@louiszuckerman.com>
Date:   Sat Dec 28 00:34:47 2013 -0500

    Updating extras/Ubuntu with latest upstart configs (BUG: 1047007)
    
    Change-Id: Ia769589f6af1d7ca3577185fd4c56eb9f43b3e2e
    BUG: 1047007
    Signed-off-by: Louis Zuckerman <me@louiszuckerman.com>
    Reviewed-on: http://review.gluster.org/6611
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a42d0938bf85a2fa23ce23ee88ea0cd24fd79d24
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Dec 27 14:24:29 2013 +0530

    features/index: Minor improvement in log message.
    
    Change-Id: Ic4f39785dab5ad64def4c06d7bd2f2dec09e19ab
    BUG: 1045690
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6606
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6b41a0b7dfd9f48e1518430bacba9135bee4fcb4
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Dec 27 16:51:29 2013 +0530

    test: Modified bug-1037501.t script
    
    Change-Id: I3114009681d49249fe292f94a464efc419c944cb
    BUG: 1037501
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/6596
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2909ef3ecb5f331630460d17c56da6291c1f254b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Dec 27 18:00:45 2013 +0530

    protocol/server: Change log message severity
    
    Change-Id: Ia6aaf8a106c26fa7118c86fadb6805d2877bb6ee
    BUG: 849630
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6610
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 412e6ab75834f4ec3ba024b702374a84b2f18eb0
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Dec 23 11:13:17 2013 -0800

    build: fix day in the %changelog
    
    This fixes `warnings` during build tests `rpm.t`
    
    Change-Id: I706ceb1a39d046fe26f70f7b1b06f059abd5d3c0
    BUG: 1000019
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6584
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d4b8825436daad701995e120f38da706e5fe97c1
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Dec 24 17:58:21 2013 +0530

    socket: unix socket connect path can't be greater than UNIX_PATH_MAX characters
    
    Change-Id: I74788b63dd1c14507aa6d65182ea4b87a2e1f389
    BUG: 1046308
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6589
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0d7279d32d5f55c0210bdcfda2d3f83e35f524b6
Author: Poornima G <pgurusid@redhat.com>
Date:   Mon Dec 23 05:11:15 2013 +0000

    gfapi: Closed the logfile fd and initialize to NULL in glfs_fini
    
    Currently if logfile is closed and other threads call gf_log
    after glfs_fini() is executed, it may lead to memory corruption.
    Adding gf_log_fini() which closes the logfile and initializes
    the logfile to NULL, thus any further logging happens to stderr.
    Also added gf_log_globals_fini() which should be filled in the
    future to release all the logging resources.
    
    Change-Id: I879163e1a3636e65300d166f782517ee773cab65
    BUG: 1030228
    Signed-off-by: Poornima G <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6552
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2ba42d07eb967472227eb0a93e4ca2cac7a197b5
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Dec 23 14:02:12 2013 +0530

    cli: Fix xml output for volume status
    
    The XML output for volume status was malformed when one of the nodes is
    down, leading to outputs like
    -------
              <node>
                 <node>
                   <hostname>NFS Server</hostname>
                   <path>localhost</path>
                   <peerid>63ca3d2f-8c1f-4b84-b797-b4baddab81fb</peerid>
                   <status>1</status>
                   <port>2049</port>
                   <pid>2130</pid>
                 </node>
    -----
    
    This was happening because we were starting the <node> element before
    determining if node was present, and were not closing it or clearing it
    when not finding the node in the dict.
    
    To fix this, the <node> element is only started once a node has been
    found in the dict.
    
    Change-Id: I6b6205f14b27a69adb95d85db7b48999aa48d400
    BUG: 1046020
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6571
    Reviewed-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 67ddf10d07ea14e1b9faeabde9dfc700247a6377
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Dec 20 12:27:30 2013 +0530

    mount.glusterfs:export PATH environment variable
    
    Problem: spurious warning:
    mount -t glusterfs 10.70.7.228:repvol /mnt/fuse_mnt/
    WARNING: getfattr not found, certain checks will be skipped..
    
    Fix:
    export PATH so that getfattr search succeeds.
    
    Change-Id: Ib19e2899e43a7d763a136b9fbc90823f743597a5
    BUG: 1040348
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6545
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f86c618cd0943930c391e6bf55fdf977b3245f36
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Mon Dec 23 16:27:42 2013 +0530

    bd: Check for capabilities for creating thin lv
    
    Check capabitlies of the volume before trying to create thin LV.
    
    BUG: 1028672
    
    Change-Id: I1375f6f2a7576e223fc5d7cd40315999446db86a
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6577
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f9698036fcc1ceedea19110139400d0cf4a54c9a
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Dec 23 09:32:22 2013 +0000

    cluster/afr: avoid race due to afr_is_transaction_running()
    
    Problem:
    ------------------------------------------
    afr_lookup_perform_self_heal() {
            if(afr_is_transaction_running())
                    goto out
            else
                    afr_launch_self_heal();
    }
    ------------------------------------------
    
    When 2 clients simultaneously access a file in split-brain, one of them
    acquires the inode lock and proceeds with afr_launch_self_heal (which
    eventually fails and sets "sh-failed" in the callback.)
    
    The second client meanwhile bails out of afr_lookup_perform_self_heal()
    because afr_is_transaction_running() returns true due to the lock obtained by
    client-1. Consequetly in client-2, "sh-failed" does not get set in the dict,
    causing quick-read translator to *not* invalidate the inode, thereby serving
    data randomly from one of the bricks.
    
    Fix:
    If a possible split-brain is detected on lookup, forcefully traverse the
    afr_launch_self_heal() code path in afr_lookup_perform_self_heal().
    
    Change-Id: I316f9f282543533fd3c958e4b63ecada42c2a14f
    BUG: 870565
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6578
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Varun Shastry <vshastry@redhat.com>

commit 879be836145f1d0b4bc381e7416ca8bd0811b718
Author: James Shubin <james@shubin.ca>
Date:   Sat Dec 21 03:35:37 2013 -0500

    Fix typos, and spacing issues.
    
    Change-Id: I459ba4e87e9bc4f1c373f7abe8701bfa8450253c
    BUG: 1045690
    Signed-off-by: James Shubin <james@shubin.ca>
    Reviewed-on: http://review.gluster.org/6556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1cc90698094f9483ee8b9731aef96e1a777a7887
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Dec 22 18:32:11 2013 +0530

    cli: Throw a warning during replace-brick
    
    Change-Id: Ia024d055645ac2ec5cd506f2533831a159b38c20
    BUG: 1039954
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6559
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 6e1449e5201591bbfcd0effa94f221317ad46a7a
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Dec 21 23:35:19 2013 +0530

    cli: Throw a warning during creation of rdma volumes.
    
    Change-Id: I77155a7a4ff56a10079aab206af197e9d03e8a8a
    BUG: 1017176
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6557
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6fcc8df5956501bbb3687331ea518b231611856a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Dec 16 10:29:19 2013 +0530

    glusterd: make volinfo a refcnt'ed object.
    
    Add glusterd_volinfo_remove(..) which removes @volinfo from the list
    of volumes in the cluster and performs an unref on @volinfo
    
    Change-Id: I5f546ca58f61bc334ab1bab4c51c4a21e1f66161
    BUG: 1038051
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6521
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 79d5a31279825bdc61ad036b30fbe7e41b76fe5e
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Dec 17 01:12:05 2013 +0530

    glusterd: rebalance to ref volinfo before starting
    
    Change-Id: Ib316897dcbd0748bfb3bfcda186b9fe30c07f80f
    BUG: 1038051
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6522
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 3991b0d0e934214882c064a0b720375af5c1575a
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Dec 19 18:11:38 2013 +0530

    cluster/afr: For entry self heal, mark all source bricks
    
    Problem:
    Whenever a new brick is added into a replicate volume, all
    source bricks are not marked as source. Only one of them is
    marked as source. Here marked as source refers to adding
    extended attribute at the backend of a file corresponding to
    the newly added brick. As well as source bricks should point
    to the newly added brick so that heal can be triggered.
    
    Fix:
    All source bricks will now point to newly added bricks and heal
    can be triggered based on the extended attributes.
    
    Change-Id: I318e1f779a380c16c448a2d05c0140d8e4647fd4
    BUG: 1037501
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/6540
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7b392ad395ae7597a3ed3a1aa7fe61faefd96368
Author: Anuradha Talur <atalur@redhat.com>
Date:   Sun Dec 15 13:26:15 2013 +0000

    glusterd : enable/disable quota using volume set cmd deprecated.
    
    Using the command 'gluster volume set <volname> quota {on|off}'
    doesn't really enable/disable quota. So, a message to the user is
    provided. Message asks the user to use 'gluster volume
    quota <volname> {enable|disable}' instead.
    
    Improvement of the previous method to solve the issue.
    
    Change-Id: Ibeda35bb49ec7b541d53e592b48fd132380fce76
    BUG: 1024626
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6512
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e22c42d9154c2d9090149003038f38164701dc08
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Wed Dec 18 12:38:26 2013 +0530

    glusterd: hold the lock when submitting ACC in replace-brick
    
    replace-brick handler sets the timer to perform the replace operation and unlocks the big_lock.
    So we need to lock inside 'glusterd_do_replace_brick' before submitting the ACC
    
    Change-Id: I5525c62533bd92d3ac46587e5353e2443ad85851
    BUG: 1044337
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6534
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 709d9247bb467b801814637bd181bc7cddd36cb5
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Dec 17 11:43:22 2013 +0530

    glusterd: ignore failure to stop a stopped service.
    
    kill(2) returns -1 with errno set to ESRCH when the pid of the process
    being killed doesn't exist. Failing glusterd_brick_stop on a stopped
    brick could result in volume-stop failing, in commit phase.
    This fix prevents that from happening.
    
    Change-Id: I00f46fa06e489a671efbb8e4119f545f8ccea329
    BUG: 1038051
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6525
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 30bdde315e01d4d71cca121f0cba55b7ae82dd1b
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Dec 17 16:09:02 2013 +0530

    glusterd: Fix stopping of stale rebalance processes
    
    Trying to stop rebalance process via RPC using the GD_SYNCOP macro,
    could lead to glusterd crashing. In case of an implicit volume update,
    which happens when a peer comes back up, the stop function would be
    called in the epoll thread. This would lead to glusterd crashing as the
    epoll thread doesn't have synctasks for the GD_SYNCOP macro to make use
    of.
    
    Instead of using the RPC method, we now terminate the rebalance process
    by kill(). The rebalance process has been designed to be resistant to
    interruption, so this will not lead to any data corruption.
    
    Also, when checking for stale rebalance task, make sure that the old
    task-id is not null.
    
    Change-Id: I54dd93803954ee55316cc58b5877f38d1ebc40b9
    BUG: 1044327
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6531
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 94915bc1b3b487ddb6d11412493877c9bd6d101b
Author: James Shubin <james@shubin.ca>
Date:   Fri Dec 13 10:44:34 2013 -0500

    Added Puppet-Gluster documentation from Puppet-Gluster project.
    
    Change-Id: I196d97fb446f5938671c4cde6c460334999679cf
    Signed-off-by: James Shubin <james@shubin.ca>
    Reviewed-on: http://review.gluster.org/6507
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 99f9dedd5b0f817364deff7c2bd1a8401e067e40
Author: James Shubin <james@shubin.ca>
Date:   Fri Dec 13 10:44:34 2013 -0500

    Add boilerplate for easy, local, documentation testing.
    
    Change-Id: I5386b4e1f05a30b051d81eaca557c93ede198b51
    Signed-off-by: James Shubin <james@shubin.ca>
    Reviewed-on: http://review.gluster.org/6506
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 329e38d4ab5af1a675b4d5651eda983f8a924418
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Tue Dec 17 08:43:50 2013 +0530

    gNFS: Client cache invalidation with bad fsid
    
    1. Problem:
    Couple of issues are seen when NFS-ACL is turned ON. i.e.
    i) NFS directory access is too slow, impacting customer workflows
       with ACL
    ii)dbench fails with 100 directories.
    
    2. Root cause: Frequent cache invalidation in the client side when ACL
    is turned ON with NFS because NFS server getacl() code returns the
    wrong fsid to the client.
    
    3. This attr-cache invlaidation triggers the frequent LOOKUP ops for
    each file instead of relying on the readdir or readdirp data. As
    a result performance gets impacted.
    
    4. In case of dbench workload, the problem is more severe. e.g.
    
    Client side rpcdebug output:
    ===========================
    
    Dec 16 10:16:53 santosh-3 kernel: NFS:
             nfs_update_inode(0:1b/12061953567282551806 ct=2 info=0x7e7f)
    Dec 16 10:16:53 santosh-3 kernel: NFS:
             nfs_fhget(0:1b/12061953567282551806 ct=2)
    Dec 16 10:16:53 santosh-3 kernel: <-- nfs_xdev_get_sb() = -116 [splat]
    Dec 16 10:16:53 santosh-3 kernel: nfs_do_submount: done
    Dec 16 10:16:53 santosh-3 kernel: <-- nfs_do_submount() = ffffffffffffff8c
    Dec 16 10:16:53 santosh-3 kernel: <-- nfs_follow_mountpoint() = ffffffffffffff8c
    Dec 16 10:16:53 santosh-3 kernel: NFS: dentry_delete(clients/client77, 20008)
    
    As per Jeff Layton, This occurs when the client detects that the fsid on
    a filehandle is different from its parent. At that point, it tries to
    do a new submount of the new filesystem onto the correct point. It means
    client got a superblock reference for the new fs and is now looking to set
    up the root of the mount. It calls nfs_get_root to do that, which basically
    takes the superblock and a filehandle and returns a dentry.  The problem
    here is that the dentry->d_inode you're getting back looks wrong. It's not
    a directory as expected -- it's something else. So the client gives up and
    tosses back an ESTALE.
    
    Which clearly says that, In getacl() code while it does the stat() call
    to get the attrs, it forgets to populate the deviceid or fsid before
    going ahead and does getxattr().
    
    FIX:
    1. Fill the deviceid in iatt.
    2. Do bit more clean up for the confusing part of the code.
    
    NB: Many many thanks to Niels de Vos and Jeff Layton for their
    help to debug the issue.
    
    Change-Id: I8d3c2a844c9d1761051a883b5ebaeb84062a11c8
    BUG: 1043737
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6523
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9031a90613c1cadcab32c418e0e2cc5b14afbba1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 9 16:46:06 2013 +0530

    cluster/afr: Add foreground self-heal launch capability through lookup
    
    Also renamed allow-sh-for-running-transaction -> attempt-self-heal
    
    Change-Id: I134cc79e663b532e625ffc342c59e49e71644ab3
    BUG: 1039544
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6463
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: venkatesh somyajulu <vsomyaju@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 588185463d1bbf1b011e3b0471771b3d4f4aa145
Author: Prashanth Pai <ppai@redhat.com>
Date:   Fri Dec 13 16:20:11 2013 +0530

    doc: Fix markdown format errors
    
    Made the following minor changes:
    * Fix broken links and point to correct image paths
    * Remove dead links and references
    * Fix table format to conform to Github Flavoured Markdown
    * Add few common terms to glossary
    * Maintain consistency of format in writing headings <h1..h6>
    * Remove irrelevant files
    * Remove references to contact Red Hat support.
    
    Change-Id: I4aed4945d56b5d68b8ea133ce5fa3162bfc2864f
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/6514
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit a9623ada6f7b39ac2d567f66a496072487d8e6ec
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Thu Dec 12 11:40:36 2013 +0530

    pathinfo: Provide user namespace access.
    
    Locality can be now queried by unprivileged users with
    key "glusterfs.pathinfo".
    
    Setting both "glusterfs.pathinfo" and "trusted.glusterfs.pathinfo"
    on disk is prevented with this patch.
    
    Original Author: Vijay Bellur <vbellur@redhat.com>
    
    Change-Id: I4f7a0db8ad59165c4aeda04b23173255157a8b79
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/5101
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 40e13bc5b44d0b0cdaf7833c848d4a52352e0a13
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Aug 8 15:50:31 2013 +0530

    rpc,glusterd: Use rpc_clnt notifyfn to cleanup mydata
    
    rpc:
    - On a RPC_TRANSPORT_CLEANUP event, rpc_clnt_notify calls the registered
      notifyfn with a RPC_CLNT_DESTROY event. The notifyfn should properly
      cleanup the saved mydata on this event.
    - Break the reconnect chain when an rpc client is disabled. This will
      prevent new disconnect events which can lead to crashes.
    
    glusterd:
    - Added support for RPC_CLNT_DESTROY in glusterd_brick_rpc_notify
    - Use a common glusterd_rpc_clnt_unref() function throught glusterd in
      place of rpc_clnt_unref(). This function correctly gives up the
      big-lock before performing the unref.
    
    Change-Id: I93230441c5089039643fc9f5632477ef1b695348
    BUG: 962619
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5512
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f502e28e8b416f80bd9506ac204948681610b305
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Dec 10 11:34:06 2013 +0530

    glusterd: Save/restore/sync rebalance dict
    
    A dictionary was added to store additional information of a rebalance
    process, like the bricks being removed in case of a rebalance started
    by remove-brick. This dictionary wasn't being stored/restored or synced
    during volume sync, leading to errors like a volume status command
    failing. These issues have been fixed in this patch. The rebalance dict
    is now stored/restored and also exported/imported during volume sync.
    
    Also, this makes sure that the rebalance dict is only create on
    remove-brick start. This adds a bricks decommissioned status to the
    information imported/exported during volume sync.
    
    Change-Id: I56fed23dc2de80a96648055fe705e9c3ffd55227
    BUG: 1040809
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6492
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7f70a9d2b2a0c3141ccdabb79401d39c871e47a9
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Dec 9 17:12:49 2013 +0530

    glusterd: Fix incorrect remove-brick status
    
    PROBLEM:
    
    'remove-brick status' was reported to be showing the status
    of a previous rebalance op that was aborted, on the node which
    doesn't participate in the remove-brick operation.
    
    FIX:
    
    Unconditionally reset defrag status to NOT_STARTED whenever a
    remove-brick or a rebalance op is attempted.
    
    Change-Id: Iddf3a14a2ef352e77e0f690fe65aa36ec3011257
    BUG: 1040371
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6482
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 44d644729b57ffbf71c70f21df0ffdd1e5fbb7c7
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Wed Dec 11 14:32:49 2013 +0530

    features/quota: log usage only if hard limit not exceeded.
    
    Change-Id: I60abf576999996e0d0d65534e1e416f6e10994c8
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    BUG: 969461
    Reviewed-on: http://review.gluster.org/6479
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 51a614384e694f37d957a3aa3a562c34877e71d5
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Dec 10 07:26:46 2013 -0500

    build: Merge glusterfs.spec changes from Fedora
    
    sync with FedoraSCM glusterfs.spec
    
    N.B. the %doc hack for clear_xattrs.sh doesn't work in the CentOS 5 mock
    builds of the rpm.t regression test, thus I'm leaving that out for now
    
    Change-Id: I6fa85618c916a90fdbed5b231ea58bb51c9d2b70
    BUG: 950083
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6473
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 7fc2499db89e385332f09fb06c10cb524f761875
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Dec 11 17:30:13 2013 +0530

    glusterd: fix error in remove-brick-replica validation
    
    Problem:
    Reducing replica count of a volume using remove-brick command fails
    if bricks are specified in a random order.
    
    Fix: Modify subvol_matcher_verify() to permit order agnostic
    replica count reduction.
    
    
    Change-Id: I1f3d33e82a70d9b69c297f69c4c1b847937d1031
    BUG: 1040408
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6489
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0404be9ca1d9fa15c83bc4132561091c1c839d84
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Sep 14 19:51:13 2013 -0700

    mount.glusterfs: getopts support and cleanup
    
    This patch is an attempt to provide some much needed
    cleanup for future maintenance of `mount.glusterfs`
    
    - Add checks for command failures
    - Spliting large code into subsequent simpler functions
    - Standardized variables
    - use 'bash' instead of 'sh' - since string manipulation
      and variable handling is far superior
    - Overall code cleanup and Copyright change to Red, Hat Inc.
    - Add new style of mounting with a comma separated list
      ~~~
      $ mount -t glusterfs <IP1/HOSTNAME1>,<IP2/HOSTNAME2>,..<IPN/HOSTNAMEN>:/<VOLUME> <MNT>
      ~~~
    - Update age old `manpage` with new options :-)
    
    Change-Id: I294e4d078a067d67d9a67eb8dde5eb2634cc0e45
    BUG: 1040348
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5931
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ea89a25b0b4e8796c421c32fb6dbc4661081f6e1
Author: Anand Avati <avati@redhat.com>
Date:   Thu Dec 12 15:43:28 2013 -0800

    dht: handle ESTALE/ENOENT in dht_access
    
    Had misssed out dht_access in the previous round of cleanup
    
    Change-Id: Ib255b9ad13ca62a8bc2eea225c46632aff8e820f
    BUG: 1032894
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6496
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>

commit 8bdc329e892f35ca19dfd07b542aa81afd855fce
Author: Anand Avati <avati@redhat.com>
Date:   Tue Dec 10 14:28:22 2013 -0800

    posix: if brick-uid or brick-gid is not specified, do not set
    
    Current code would set owner uid/gid explicitly to 0/0 on start
    even if none was specified. Fix it.
    
    Change-Id: I72dec9e79c51bd1eb3af5334c42b7c23b01d0258
    BUG: 1040275
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6476
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Lukáš Bezdička <lukas.bezdicka@gooddata.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b198e072cda4bbb98e19701399c4bb4f0743cf20
Author: Ajeet Jha <ajha@redhat.com>
Date:   Mon Dec 2 12:55:18 2013 +0530

    glusterd/geo-rep: more glusterd and cli fixes for geo-rep.
    
        -> handle option validation cases in reset case.
        -> Creating valid conf path when glusterd restarts.
        -> Reading the gsyncd worker thread status and displaying it.
        -> Displaying status-detail per worker.
        -> Fetch checkpoint info in geo-rep status.
        -> use-tarssh value validation added.
    
    misc: misc geo-rep fixes based on cluster, logrotate etc..
        -> cluster/dht: fix 'stime' getxattr getting overwritten.
        -> cluster/afr: return max of 'stime' values in subvol.
        -> geo-rep-logrotate: Sending SIGHUP to geo-rep auxiliary.
        -> cluster/dht: fix convoluted logic while aggregating.
        -> cluster/*: fix 'stime' min/max fetch logic.
    
    Change-Id: I811acea0bbd6194797a3e55d89295d1ea021ac85
    BUG: 1036552
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6405
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f999c17da5a5353196e68e7a68af64f91df6b902
Author: Ajeet Jha <ajha@redhat.com>
Date:   Mon Dec 2 12:37:34 2013 +0530

    gsyncd / geo-rep: geo-replication fixes
    
    -> "threaded" hybrid crawl.
    -> Enabling metatadata synchronization.
    -> Handling EINVAL/ESTALE gracefully while syncing metadata.
    -> Improvments to changelog crawl code.
    -> Initial crawl changelog generation format.
    -> No gsyncd restart when checkpoint updated.
    -> Fix symlink handling in hybrid crawl.
    -> Slave's xtime key is 'stime'.
    -> tar+ssh as data synchronization.
    -> Instead of 'raise', just log in warning level for xtime missing cases.
    -> Fix for JSON object load failure
    -> Get new config value after config value reset.
    -> Skip already processed changelogs.
    -> Saving status of each individual worker thread.
    -> GFID fetch on slave for purges.
    -> Add tar ssh keys and config options.
    -> Fix nlink count when using backend.
    -> Include "data" operation for hardlink.
    -> Use changelog time prefix as slave's time.
    -> Process changelogs in parallel.
    
    Change-Id: I09fcbb2e2e418149a6d8435abd2ac6b2f015bb06
    BUG: 1036539
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6404
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8f2fc6fb3a63ca87d82b6fa933f94fb1e3283a26
Author: Ajeet Jha <ajha@redhat.com>
Date:   Mon Dec 2 13:04:51 2013 +0530

    features/changelog: more changelog fixes.
    
    -> log additional records.
    -> include FOP number for metadata.
    -> prevent crash if inode is not found in a fop.
    
    Change-Id: I9edd4b71819ebd68c6a2b4150ae279c471d129da
    BUG: 1036536
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6403
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 493008a299cd1197df0caee72eacd12c1a54606b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Dec 11 15:19:25 2013 +0530

    cluster/dht: Make sure gf_defrag_migrate_data is not optimized
    
    Problem:
    Whenever there syncop_xxx() is used inside a synctask and gcc
    optimizes it when compiled with -O2 there is a problem where
    'errno' would not work as expected.
    
    Fix:
    Until http://review.gluster.com/6475 is reviewed and merged
    we are making sure the function is not going to be optimized.
    
    Change-Id: I504c18c8a7789f0c776a56f0aa60db3618b21601
    BUG: 1040356
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6481
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4bbbda2017be3cfae57c122d70d11c9470364f63
Author: Anuradha <atalur@redhat.com>
Date:   Wed Oct 30 11:57:38 2013 +0530

    cli : enabling/disabling quota using volume set cmd deprecated
    
    Using the command 'gluster volume set <volname> quota {on|off}'
    doesn't really enable/disable quota. So, a message to the user is
    provided. Message asks the user to use 'gluster volume
    quota <volname> {enable|disable}' instead.
    
    Change-Id: Ic4e12d5f8298ca9233639b4f6f8601ed6937fecb
    BUG: 1024626
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6192
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 11b4f3aedfacf2cb29c409765936940271329e73
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Sep 6 14:50:35 2013 +0530

    gfid-access: do chown() after creating the new entries
    
    changing the 'frame->root->uid' on the fly is not a good idea as
    posix-acl xlator on brick process would fail the op.
    
    Change-Id: I996b43e4ce6efb04f52949976339dad6eb89bede
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 847839
    Reviewed-on: http://review.gluster.org/5833
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cb44756616f2ef9a6480adf104efa108300b06c3
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Nov 22 11:27:14 2013 +0530

    glusterd: Improve rebalance handling during volume sync
    
    Glusterd will now correctly copy existing rebalance information when a
    volinfo is updated during volume sync. If the existing rebalance
    information was stale, then any existing rebalance process will be
    termimnated. A new rebalance process will be started only if there is no
    existing rebalance process. The rebalance process will not be started if
    the existing rebalance session had completed, failed or been stopped.
    
    Change-Id: I68c5984267c188734da76770ba557662d4ea3ee0
    BUG: 1036464
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6334
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6a163b22144a689cd89a6a605715959e654ea015
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Dec 5 11:16:55 2013 +0530

    dht: Set status to FAILED when rebalance stops due to brick going down
    
    Change-Id: I98da41342127b1690d887a5bc025e4c9dd504894
    BUG: 1038452
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6435
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <gowda.shishir@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c492b2cf8a18f09975da24e60330d0454cbd1e4e
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Dec 9 16:10:56 2013 +0530

    mount/fuse: cleanup old graphs.
    
    After a graph switch, a PARENT_DOWN event from fuse indicates
    protocol/client to shutdown all its sockets. However, this event will
    be sent only when the first fop is received from fuse mount after
    graph switch. Also, this event is sent only on previously active graph.
    So, if there are multiple graph switches when there is no activity on
    mountpoint, we'll be left with a list of graphs with their sockets
    still open.
    
    This patch fixes the issue by sending PARENT_DOWN to previously
    non-active graph when a new graph is available irrespective of whether
    there is an activity on mount-point.
    
    Change-Id: I9e676658d797c0b2dd3ed5ca5a56271bd94b4bb6
    BUG: 924726
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/4713
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 980fb894798240076142ea74b0d49dd2b4160462
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Dec 9 08:50:49 2013 -0800

    mount.glusterfs: Provide backward compatibility for "backup-volfile-servers"
    
    In commit "b610f1be7cd71b8f3e51c224c8b6fe0e7366c8cf" we deprecated
    "backupvolfile-server" and provided a new option for specifying
    multiple backup servers. This resulted in existing `fstab` entries
    invalid and leading to mount failure. Provide backward compatibility
    to avoid this regression.
    
    Change-Id: Ic20671bbe2a0df36b6110ffa928396f808eb76e5
    BUG: 1039643
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 00b159840added72099f61f45b38133e856d23bf
Author: Bharata B Rao <bharata@linux.vnet.ibm.com>
Date:   Mon Dec 9 11:15:02 2013 +0530

    libglusterfs: Explicitly open /dev/stderr logfile
    
    Currently if stderr is specified as logfile, /dev/stderr isn't opened but
    stderr is directly used. However libgfapi closes the logfile (and hence
    stderr) from glfs_fini() which results in stderr becoming unavailable for
    the application that links to libgfapi. Prevent this unexpected behaviour
    for the application by explicitly opening /dev/stderr like it is done for
    any other logfile.
    
    Change-Id: I76b754598a2acf40b91ff0461726c5918e278c84
    BUG: 1038924
    Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
    Reviewed-on: http://review.gluster.org/6452
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f4488e34553ec0bf68c270034af179ab14fd2b58
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Dec 6 14:33:51 2013 -0500

    build: FedoraSCM sources are not longer needed to build RPMs
    
    Also some updates to .gitignore
    
    Change-Id: I576af453ca7d1ec1f3db21ee4d8386927988e7db
    BUG: 950083
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6458
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 39dd3b21c59380fb5f4dcae59ebd4f8e000cfa98
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Dec 5 12:31:34 2013 +0530

    libglusterfs: Free IP address string in gf_is_local_addr()
    
    Change-Id: Ib113de269134c907aa2f35459e2764c142b94477
    BUG: 1032122
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6433
    Tested-by: Lukáš Bezdička <lukas.bezdicka@gooddata.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 64e3fada97bdb6dc4b885d6122e56eb93273503c
Author: Anand Avati <avati@redhat.com>
Date:   Wed Nov 27 12:54:41 2013 -0800

    index: fix the order of initialization
    
    thread spawning must be the last action. if not, failures after
    thread creation can set this->private to NULL and cause index_worker
    to segfault
    
    Change-Id: I71c85c25d7d6d1ed5f8d9c951db0262b8a3f1d90
    BUG: 1034085
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6426
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit def8890d5ea7e73dfa37023e5d324be0bc289f5a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Dec 2 11:37:55 2013 +0530

    cli: Fail creation of bricks on root partition in script mode
    
    Also added an option 'wignore' to save ourselves the trouble
    of modifying test scripts in our regression test suite as well
    as those that are still under review.
    
    Change-Id: Id320c03595506e9da187e766991c19640bd000c5
    BUG: 1028281
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6409
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b6c835282de500dff69e68bc4aebd3700c7388d0
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Oct 30 18:25:39 2013 +0530

    glusterd: Aggregate tasks status in 'volume status [tasks]'
    
    Previously, glusterd used to just send back the local status of a task
    in a 'volume status [tasks]' command. As the rebalance operation is
    distributed and asynchronus, this meant that different peers could give
    different status values for a rebalance or remove-brick task.
    
    With this patch, all the peers will send back the tasks status as a part
    of the 'volume status' commit op, and the origin peer will aggregate
    these to arrive at a final status for the task.
    
    The aggregation is only done for rebalance or remove-brick tasks. The
    replace-brick task will have the same status on all the peers (see
    comment in glusterd_volume_status_aggregate_tasks_status() for more
    information) and need not be aggregated.
    
    The rebalance process has 5 states,
     NOT_STARTED - rebalance process has not been started on this node
     STARTED - rebalance process has been started and is still running
     STOPPED - rebalance process was stopped by a 'rebalance/remove-brick
               stop' command
     COMPLETED - rebalance process completed successfully
     FAILED - rebalance process failed to complete successfully
    The aggregation is done using the following precedence,
     STARTED > FAILED > STOPPED > COMPLETED > NOT_STARTED
    
    The new changes make the 'volume status tasks' command a distributed
    command as we need to get the task status from all peers.
    
    The following tests were performed,
    - Start a remove-brick task and do a status command on a peer which
      doesn't have the brick being removed. The remove-brick status was
      given correctly as 'in progress' and 'completed', instead of 'not
      started'
    - Start a rebalance task, run the status command. The status moved to
      'completed' only after rebalance completed on all nodes.
    
    Also, change the CLI xml output code for rebalance status to use the
    same algorithm for status aggregation.
    
    Change-Id: Ifd4aff705aa51609a612d5a9194acc73e10a82c0
    BUG: 1027094
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 866d079c5bfc9b278c654090a9c088fe2131db1d
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Dec 4 12:32:59 2013 -0500

    contrib/qemu: remove the CONFIG_INT128 host config option
    
    These leads to compile failures in 32-bit build environments.
    
    BUG: 986775
    Change-Id: I0b702f616e1d0e11eda7e55666fd1a7c67bfaeab
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/6427
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit e967e5c5ab42359b765d602abb439b579d7a7423
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Dec 4 15:55:01 2013 +0530

    glusterd: create rpc obj for rebalance only if absent
    
    Change-Id: Iff305023577ff92a8f43f24dafcf201f86805769
    BUG: 1038051
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6423
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ae540f8e2732ab1bd0fbeabd4d4f5c6f2f417914
Author: Anand Avati <avati@redhat.com>
Date:   Wed Nov 27 05:09:57 2013 -0800

    glusterd: submit RPC requests without holding big lock
    
    If the endpoint of an RPC is not connected, the callback is called
    synchronously within rpc_clnt_submit(). Since callbacks typically
    hold the big lock, give up the big lock before calling rpc_clnt_submit
    and acquire it freshly after the call.
    
    Change-Id: Id89d8dd86c1a4012739ef4af7ea0935492b1a02b
    BUG: 1037849
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6413
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 8e21e00fc662abb4f6556d9a258fa9ec57a20ed0
Author: Vijaikumar M <vmallika@redhat.com>
Date:   Wed Nov 6 16:41:50 2013 +0530

    glusterd: Do not allow remove-brick commit if the bricks are not decommissioned
    
    Change-Id: Ibf47ea848bbb7ae37ccf91c40e5fe0e2338438b7
    BUG: 1027171
    Signed-off-by: Vijaikumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6233
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 133c370ec5e2688b6734acb087fe3769cb900a74
Author: Dawit Alemu <dalemu@redhat.com>
Date:   Thu Nov 14 12:52:14 2013 -0500

    cli: Add an option to fetch just incremental or cumulative I/0
    information
    
    'volume profile info' fetches both cumulative and incremental
    I/O statistics. There isn't a way to fetch just cumulative or
    incremental statistics.
    
    This change introduces two optional arguments, namely "incremental"
    and "cumulative", that can be tacked on to 'volume profile info'.
    In other words, the new command format is
    
    volume profile <VOLNAME> {start | info [incremental | cumulative]
    | stop} [nfs]
    
    'volume profile info incremental' - fetches incremental stats
    'volume profile info cumulative' - fetches cumulative stats
    'volume profile info' - fetches incremental and cumulative stats
    
    Change-Id: I5ddb45d990542ea611d23d251efebfec46f472d0
    BUG: 1030580
    Signed-off-by: Dawit Alemu <dalemu@redhat.com>
    Reviewed-on: http://review.gluster.org/6264
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e4b9a74f46bca3894d686ce87042168c4304f07b
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Wed Nov 27 15:50:21 2013 +0530

    gNFS: Inconsistent behaviour of setfacl/getfacl
    
    The permissions returned by NFS ACL are wrong, which are rejected
    by NFS client as "Invalid argument". Refactor the NFS ACL code
    to return the proper permissions which would match with the
    requested permissions.
    
    Change-Id: I409a6600538a90f2c5c2e8d84657c3b508468fe6
    BUG: 1035218
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6368
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 916785766777ea74c30df17b6e2c572bc1c9a534
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Nov 22 13:03:57 2013 +0530

    cli: More checks in rebalance status output
    
    Change-Id: Ibd2edc5608ae6d3370607bff1c626c8347c4deda
    BUG: 1031887
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6337
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8a0f744c461166be483f28fe9da37732586585d8
Author: Poornima <pgurusid@redhat.com>
Date:   Tue Dec 3 05:46:40 2013 +0000

    cluster/afr: handle NULL check before strlen/strcmp in fgetxattr
    
    xattr name can legally be NULL. Handle that case without crashing.
    
    Change-Id: Ie214cb05ccd52565dc247a9234ad83ae799d3866
    BUG: 1036879
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6412
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 17312534879f506c71ee72c549ba6fda6f9b063d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Dec 2 07:59:08 2013 -0500

    gfapi: add __THROW [(__attribute) ((__nothrow__))] to fn decls for C++ users.
    
    Off hand I don't know of anything written in C++ that is or could be a user
    of gfapi.
    
    Never the less, it's possible that one could exist, or be written, and
    marking the library entry points is a) friendly, b) possibly allows the
    C++ compiler to generate better code, and c) is a good practice when
    writing APIs that might be consumed by C++ applications. Considering we
    already take the first step and use __BEGIN_DECLS/__END_DECLS to be C++
    friendly, we should take the extra step
    
    Change-Id: Ib319ecaa452a46f258a9c6e8c7221454d2fefd0f
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6393
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ed31918c2cf80d6c875e0b31eff4ab634d9375f2
Author: Anand Avati <avati@redhat.com>
Date:   Tue Nov 26 19:38:01 2013 -0800

    protocol/client: handle network disconnect/reconnect properly
    
    if client/server state versions match, we still need to notify
    parent xlators of reconnection (CHILD_UP) because they were
    notified of CHILD_DOWN at the time of disconnection.
    
    Change-Id: I36c4bde6d8c3db9cb0c48eeb10663b56897c932e
    BUG: 1037267
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6396
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit cb7832895257dd22258e360f6a596b09ba7c20ac
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Dec 1 20:11:24 2013 +0530

    cluster/afr: Fix description string for option 'self-heal-daemon'
    
    Change-Id: I267b935a16a6fdc72a4e791f681289e6868baee6
    BUG: 1010834
    Reviewed-on: http://review.gluster.org/6385
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0e5837a4495028e56c75e95a694a0d6123623eb2
Author: Aravinda VK <avishwan@redhat.com>
Date:   Mon Dec 2 15:19:17 2013 +0530

    cli: xml: Rebalance status(xml) was empty when a glusterd down
    
    When a glusterd is down in cluster rebalance/remove-brick status
    --xml will fail to get status and returns null.
    
    This patch skips collecting status if glusterd is down, and
    collects status from all the other up nodes.
    
    Change-Id: I6df0feef41b5cc817cc8d7820ee2acac95176a98
    BUG: 1036564
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6391
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit be380f35a2c9c356a8adcb9118e4f77ff9d1fec6
Author: Anand Avati <avati@redhat.com>
Date:   Tue Nov 26 13:30:46 2013 -0800

    cluster/dht: handle NULL check before strlen/strcmp in fgetxattr
    
    @key can legally be NULL. Handle that case without crashing.
    
    Change-Id: Iaae293caa7eeb24afc9cd2580799173e2ce00911
    BUG: 1036879
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6395
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a36c812756405999d79fd29c329fef73f6b7b778
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Oct 7 16:00:59 2013 +0530

    features/marker: Filter quota xattrs on file as well
    
    Problem:
    Quota contributions of a file/directory are tracked by quota
    xlator using xattrs on the file. Quota allows these xattrs to be
    healed as part of metadata self-heal. This leads to
    wrong quota calculations on this brick after self-heal because
    quota xattrs don't represent the actual contributions on the
    brick anymore.
    
    Fix:
    Don't let self-heal of this xattr happen as part of self-heal
    by filtering quota xattrs on file in listxattr.
    
    Change-Id: Iea68a116595ba271e58c6fdcc3dd21c7bb55ebb3
    BUG: 1035576
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6374
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 182bad8bfd099da5e742da28c4820936eb1f3867
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Nov 25 15:16:23 2013 +0530

    cli, glusterd: More quota fixes ...
    
    ... which may be grouped under the following categories:
    
    1. Fix incorrect cli exit status for 'quota list' cmd
    2. Print appropriate error message on quota parse errors in cli
    
            Authored by: Anuradha Talur <atalur@redhat.com>
    
    3. glusterd: Improve quota validation during stage-op
    4. Fix peer probe issues resulting from quota conf checksum mismatches
    5. Enhancements to CLI output in the event of quota command failures
    
            Authored by: Kaushal Madappa <kmadappa@redhat.com>
    
    7. Move aux mount location from /tmp to /var/run/gluster
    
            Authored by: Krishnan Parthasarathi <kparthas@redhat.com>
    
    8. Fix performance issues in quota limit-usage
    
            Authored by: Krutika Dhananjay <kdhananj@redhat.com>
    
    Note: Some functions that were used in earlier version of quota,
          that aren't called anymore have been removed.
    
    Change-Id: I9d874f839ae5fdcfbe6d4f2d727eac091f27ac57
    BUG: 969461
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6366
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 72f733a64abeffee23fb87a3cb397baea1dc22a4
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Nov 26 14:23:08 2013 -0500

    glusterfsd: fix small memory leaks in glusterfsd-mgmt.c
    
    E.g. In glusterfs_volfile_fetch(), req.xdata.xdata_val is allocated
    in dict_allocate_and_serialize() but not freed after mgmt_submit_request().
    
    A survey of dict_allocate_and_serialize/_submit_request in
    glusterfsd-mgmt.c shows no consistent pattern of freeing the xdata_val
    and also the dict, which is a little disturbing. (Yes, clearly not
    every place this occurs needs to be freed the same way.)
    
    Change-Id: Ic306d60b157e97c822a562bfdf21896e40db632a
    BUG: 1036102
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6363
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bca9eab359710eb3b826c6441126e2e56f774df5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 28 14:15:29 2013 +0530

    mount/fuse: Prevent release_cbk not implemented warning
    
    Change-Id: I53f0cb30f62ee9154670debf92476a51d6156844
    BUG: 1035639
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6375
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3c5529332779ad6cd169370193978ac24974320d
Author: Anuradha <atalur@redhat.com>
Date:   Mon Nov 25 14:48:23 2013 +0530

    features/index : Creation of indices directory as soon as brick is up.
    
    Missing indices directory in the bricks leads to unwanted log messages.
    Therefore, indices directory needs to be created as soon as the brick
    comes up.
    This patch results in creation of indices/xattrop directory as required.
    
    Also includes a testcase to test the same.
    
    Change-Id: Ic2aedce00c6c1fb24929ca41f6085aed28709d2c
    BUG: 1034085
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6343
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 72d3dde33bd12f4aea96d59097bef5df45672610
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Nov 28 16:47:09 2013 +0530

    posix-acl: Fix crash resulting from GF_FREE() done on a CALLOC'd object
    
    The object in question was created in posix_acl_inherit () and
    was being GF_FREE'd as part of data_destroy().
    
    Change-Id: Ibdb7c3b5c10ce447f061bde68452502e5170de92
    BUG: 1035751
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6377
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a25d321bade8c3e7e07242f79ec9f1de2280af0f
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Nov 22 01:26:29 2013 -0800

    glusterfs.spec: Add 'python and python-ctypes' dependency
    
    Change-Id: Icde586131bab00476abc44d8dd4e2db7e9d59b2b
    BUG: 1033275
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6339
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 50a6e9a74014897b003cadbd297fd0343eb56367
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Oct 15 17:25:51 2013 +0530

    features/quota: Add the quota config xattr to newly added brick
    
    Issue:
    Quota directory limit configuration is stored in the xattrs. When a new brick
    is added these 'limit-set' xattrs have to be created to the directory in the
    new brick. This is done by the dht directory healing when the directory is
    created in the new brick. Since 'root' directory is already created DHT doesn't
    heal the limit-set xattr root.
    
    Solution:
    When the add-brick command is issued run the below hook script to heal the
    'limit-set' xattr. The hook script does the following only if limit is
    configured on root.
        1. Create an auxiliary mount.
        2. getxattr 'limit-set' on the root
        3. setxattr the same value on the root
    But this script needs the volume to be started to make the auxiliary mount.
    
    To handle the case when the add-brick is issued when the volume was stopped,
    symlink is created by the 'master' script to the corresponding location and
    these two are by default disabled.
    
    So, a 'master' script is added in the add-brick/pre. When add-brick command is
    issued, it enables one of the scripts mentioned above based on the condition,
        if volume is started - enable add-brick/post script
        else                 - enable start/post script
    After the actual script completes its job, it disables itself.
    
    Note:
    The enabling and disabling of the script is based on the glusterd's logic, that
    it only runs the scripts which starts its name with 'S'. So,
        Enable     - symlink the file to 'S'*
        Disable    - unlink the symlink.
    
    Change-Id: I2d3947a4d686c54417ec95f530af3bdd3444f4e2
    BUG: 969461
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/6104
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8690388bc7b3fe92c5dfc43a7173d5f05137e9cd
Author: Bala.FA <barumuga@redhat.com>
Date:   Thu Nov 21 17:16:39 2013 +0530

    cli: use proper copy to set node-name
    
    Previously node-name is set to point to node-uuid which could cause
    memory leak.  This is fixed by having memory copy of node-uuid.
    
    BUG: 1012296
    Change-Id: I3b638ec289d5b167c6e752ef1ba41f41efacb9da
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/6330
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7f62ee2432d850f9fa519ddce9f58f9288ceee29
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Nov 26 12:58:31 2013 -0500

    Fix CFLAGS handling with enable_debug.
    
    The value was getting stomped by the Python stuff (for glupy) after we
    had supposedly dealt with enable_debug, so we were getting stray -O2
    options that hamper debugging.
    
    Change-Id: Iacd616071c83b92018b597b6144ab565bd5fc66f
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/6362
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 21f7ad207bdb8ddf549aa65cafc1ad95e261ec3d
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Tue Nov 26 18:01:17 2013 +0530

    posix: do not allow to set/get "trusted.glusterfs.volume-id" xattr
    
    Change-Id: I2e9a2264b1fd5ebc1ed0aff30225e89acbd0bcb4
    BUG: 1034716
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6361
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2f218e1335d5fdab0b41716cc5c8976b20c367f6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 22 12:09:53 2013 +0530

    cluster/dht: Handle Link-info getxattr failure in rebalance
    
    When getxattr fails with errno other than ENODATA fail rebalance
    on that file. Log the reason for error.
    
    Change-Id: Ia519870b88e6e6dd464d1c0415411aa999f80bc9
    BUG: 1032927
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6341
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d4c9d342f64636304720d0091a605c85ea9f0e4d
Author: Anand Avati <avati@redhat.com>
Date:   Mon Nov 25 03:13:17 2013 -0800

    write-behind: handle iobref_merge() error gracefully
    
    .. by UNWINDing ENOMEM error, rather than crashing.
    
    Change-Id: Ica2d6399eaf7e381e7ebc41155620559c139c4d3
    BUG: 1034398
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6349
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>

commit e3f80f53b536eba17e35c184e9da3e4d59c30b58
Author: Anand Avati <avati@redhat.com>
Date:   Mon Nov 25 03:19:11 2013 -0800

    io-cache: handle iobref_merge() error gracefully
    
    .. by UNWINDing ENOMEM, rather than leaving pointer in vector pointing
    to stale memory.
    
    Change-Id: I7f3917ac056fae144f845c9d123233e91e278187
    BUG: 1034398
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6351
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>

commit 2a18e2426419cbab2f98368b3306fd37958394d2
Author: Anand Avati <avati@redhat.com>
Date:   Mon Nov 25 03:16:49 2013 -0800

    read-ahead: handle iobref_merge() error gracefully
    
    .. by UNWINDing ENOMEM rather than leaving pointers in vector which
    points to unref'ed (or even worse, re-used) iobufs.
    
    Change-Id: I849d8cbe5fc02ee992d4e28b7212c49aad4925c7
    BUG: 1034398
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6350
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>

commit c9579c4501a5d316f71fc44fd46a53060a4eed0c
Author: Anand Avati <avati@redhat.com>
Date:   Mon Nov 25 03:08:19 2013 -0800

    iobufs: make iobref container size dynamic
    
    With gfapi we can receive read/write size beyond the natural limits
    of FUSE and NFS server. iobref was hardcoded to hold iobuf refs up
    to 16 in count, which imposes a natural limit of 2MB with 128KB page
    sizes of read-ahead and io-cache. Fix this by making iobref's iobuf
    ref container size dynamic.
    
    Change-Id: I93d88104d6c5e7af96cc9f1bfcc870d80fa81dad
    BUG: 1034398
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6348
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>

commit 9da4958b7853f36a137c80493bec932b79d85e84
Author: Anand Avati <avati@redhat.com>
Date:   Mon Nov 25 10:28:56 2013 -0800

    socket: limit vector count to IOV_MAX
    
    IOV_MAX is the maximum supported vector count on a given platform.
    Limit the count to IOV_MAX if higher. As we are performing non-blocking
    IO getting a smaller return value is handled naturally.
    
    Change-Id: I94ef67a03ed0e10da67a776af2b55506bf721611
    BUG: 1034398
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6354
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>

commit 9f793d70bab528e96daf3478261aeb32b2ae5523
Author: Anand Avati <avati@redhat.com>
Date:   Wed Nov 20 12:46:58 2013 -0800

    cluster/dht: set layout in inode ctx even if linkfile fails
    
    Creating linkfile could have failed, but we dont care about linkfile
    for setting layout in the inode ctx (could be EEXIST etc.)
    
    So ignore @inode in cbk and pick it up from local->loc.inode
    
    Change-Id: I2952799d7ae0d3441b84b2ca2981afd75d7576e2
    BUG: 1032859
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6319
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d1879d04e39258ea25a49eed3244b395d4af2c1d
Author: Anand Avati <avati@redhat.com>
Date:   Thu Nov 21 06:48:17 2013 -0800

    core: fix errno for non-existent GFID
    
    When clients refer to a GFID which does not exist, the errno to
    be returned in ESTALE (and not ENOENT). Even though ENOENT might
    look "proper" most of the time, as the application eventually expects
    ENOENT even if a parent directory does not exist, not returning
    ESTALE results in resolvers (FUSE and GFAPI) to not retry resolution
    in uncached mode. This can result in spurious ENOENTs during
    concurrent path modification operations.
    
    Change-Id: I7a06ea6d6a191739f2e9c6e333a1969615e05936
    BUG: 1032894
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6318
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@gmail.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ec8c678c4d8b948c1b471e497db5adc0221c154b
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Nov 26 17:37:24 2013 +0530

    features/quota: Add TODO file.
    
    Change-Id: I31990f05ca1814d229026965b7675e3990a65678
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6360
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 33e0df30cbffbfbda5197704d0f788c83cd7ed78
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Oct 31 06:35:47 2013 +0530

    cluster/dht: instruct marker whenever it shouldn't do accounting
    
    This is needed for two reasons:
    
    * since dht-linkfiles are internal, they shouldn't be accounted.
    * hardlink handling in marker is broken. link/unlink of hardlinks
      present in same directory can break marker accounting. Hence, if src
      and dst are in same directory in case of rename, dht - if it breaks
      rename into link/unlink operations - should instruct marker to not to
      do accounting.
    
    Change-Id: I9c9f7384569f75a2792f6450ee7a5279bf751ae7
    BUG: 1022995
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6203
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 75f66a98dad3882aff4a68cf0648016101f0a416
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Oct 28 10:32:52 2013 +0530

    features/marker-quota: exclude dht-linkfiles from being accounted.
    
    Change-Id: I3239f5e8477664dcc04434e4d455ae447493a7ac
    BUG: 1022995
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6153
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1a2f51144fcbd920a6f3769d6b2f3ceeefdc220d
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Nov 14 17:10:09 2013 +0530

    core: add dht_is_linkfile helper procedure.
    
    components other than distribute (like marker to exclude linkfiles
    from being accounted) also need awareness of what constitutes a
    linkfile. Hence its good to separate out this functionality into
    core.
    
    Change-Id: Ib944eeacc991bb1de464c9e73ee409fc7a689ff1
    BUG: 1022995
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6152
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3f1ebe0298450cb8770a8753fe3a8a2519f78911
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Fri Oct 4 13:37:38 2013 +0530

    features/quota: make writes short when the entire write cannot fit into available space.
    
    This patch aims to prevent creation of infinite zero byte sized files
    due to amount of storage available before exceeding quota limit
    being less than write sizes. Imagine x bytes of storage is available
    before we exceed quota limit and quota enforcer is receiving writes of
    size y and (y > x). In this scenario, if we run a shell script like:
    
       # for i in $(seq 1 10); do dd if=/dev/zero of=$i bs=y count=1; done
    
    Then, we would end up with 10 zero byte sized files, because we allow
    only complete writes and all writes will fail because of lack of space.
    However, creates succeed since a create itself will consume zero
    bytes. In this pattern of creates and writes, size of volume would
    never grow and x bytes of space will always be available and we can
    end up with an infinite number of zero byte sized files.
    
    Change-Id: Ice148d6a2207883e41759f7b0be73abaa3198b41
    BUG: 1012216
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6035
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0d5cd92f51c02b8d664000b5a2d22a2ddbbc23b6
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Nov 14 17:05:26 2013 +0530

    cli/glusterd: Changes to quota command Quota feature
     re-work.
    
    Following are the cli commands that are new/re-worked:
    ======================================================
    
    volume quota <VOLNAME> {enable|disable|list [<path> ...]|remove <path>| default-soft-limit <percent>} |
    volume quota <VOLNAME> {limit-usage <path> <size> [<percent>]} |
    volume quota <VOLNAME> {alert-time|soft-timeout|hard-timeout} {<time>}
    volume status [all | <VOLNAME> [nfs|shd|<BRICK>|quotad]] [detail|clients|mem|inode|fd|callpool]
    volume statedump <VOLNAME> [nfs|quotad] [all|mem|iobuf|callpool|priv|fd|inode|history]
    
    glusterd changes:
    =================
    * Quota limits are now set as extended attributes by glusterd from
      the aux mount created by the cli.
    * The gfids of the directories on which quota limits are set
      for a given volume are stored in
      /var/lib/glusterd/vols/<volname>/quota.conf file in binary format,
      and whose cksum and version is stored in
      /var/lib/glusterd/vols/<volname>/quota.cksum.
    
    Original-author: Krutika Dhananjay <kdhananj@redhat.com>
    Original-author: Krishnan Parthasarathi <kparthas@redhat.com>
    
    BUG: 969461
    Change-Id: If32bba36c67f9c2a30417af9c6389045b2b7c13b
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6003
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ab3ab1978a4768e9eed8e23b47e72b25046e607a
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Sep 16 17:46:50 2013 +0530

    features/quota: Improvements to quota
    
    * Two stages of quota enforcement is done:
    
      Soft and hard quota Upon reaching soft quota limit on the directory
      it logs/alerts in the quota daemon log (ie DEFAULT_LOG_DIR/quotad.log)
      and no more writes allowed after hard
      quota limit. After reaching the soft-limit the daemon alerts the
      user/admin repeatively for every 'alert-time', which is
      configurable.
    
    * Quota enforcer is moved to server-side.
    
      It  takes care of enforcing quota. Since enforcer doesn't have the
      cluster view, it relies on another service called
      quota-aggregator. Aggregator, on query can return the size of a
      directory based on the cluster view.
    
      Enforcer is always loaded in the server graph and is by passed if
      the feature is not enabled.
    
      Options specific to enforcer:
    
      server-quota - Specifies whether the feature is on/off. It is used
      to by pass the quota if turned off.
    
      deem-statfs - If set to on, it takes quota limits into consideration
      while estimating fs size. (df command). The algorithm followed is,
      i.   Adjust statvfs based on limit configured on root.
      ii.  If limit is set on the inode passed, use size/limits on that inode to
           populate statvfs. Otherwise, use size/limits configured on root.
      iii. Upon statvfs, update the ctx->size on the inode.
      iv.  Don't let DHT aggregate, instead take the maximum of the usages from the
           subvols of the DHT, since each of it contains the complete information.
    
      Enforcer also makes use of gfid-to-path conversion functionality to
      work correctly when a client like nfs predominently relies on
      nameless lookups.
    
    * Quota Aggregator acts as a thin client to provide cluster view
    
      Its a lightweight *gluster client* process with no mount point,
      started upon enabling quota or restarting the volume. This is a
      single process run on each brick, which can answer queries on all
      volumes in the cluster. Its volfile stored in
      GLUSTERD_DEFAULT_WORKING_DIR/quotad/quotad.vol.
    
    Credits:
    Raghavendra Bhat        <rabhat@redhat.com>
    Varun Shastry           <vshastry@redhat.com>
    Shishir Gowda           <sgowda@redhat.com>
    Kruthika Dhananjay      <kdhananj@redhat.com>
    Brian Foster            <bfoster@redhat.com>
    Krishnan Parthasarathi  <kparthas@redhat.com>
    
    Change-Id: Id1cb25b414951da34c665a55f77385d482e0f9de
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/5952
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 460ce40d3e2069bf6262dccea6f5ae2fac60d90f
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Sep 16 21:35:08 2013 +0530

    features/marker: quota friendly changes
    
    * handles renames on dht linkfiles correctly
    
    * nameless lookup friendly changes. uses gfid-to-path conversion
      functionality from storage/posix to build ancestry till root.
    
    * log message cleanup.
    
    * build inode contexts in readdirp
    
    * Accounting still not correct with hardlinks.
    
    Credits:
    ========
    Vijay Bellur <vbellur@redhat.com>
    Raghavendra Bhat <rabhat@redhat.com>
    
    Change-Id: I415b6fbbc9691f5a38d9fd3c5d083a61e578bb81
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/5953
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d6dc8d0e9e2052818c9858f6b073a8bacc3fca88
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Sep 16 17:50:25 2013 +0530

    posix: placeholders for GFID to path conversion
    
    what?
    =====
        The following is an attempt to generate the paths of a file when
        only its gfid is known.
    
        To find the path of a directory, the symlink handle to the
        directory maintained in  the ".glusterfs" backend directory is
        read. The symlink handle is generated using the gfid of the
        directory. It (handle) contains the directory's name and parent
        gfid, which are used to recursively construct the absolute path as
        seen by the user from the mount point.
    
        A similar approach cannot be used for a regular file or a symbolic
        link since its hardlink handle, generated using its gfid, doesn't
        contain its parent gfid and basename. So xattrs are set to store
        the parent gfids and the number of hardlinks to a file or a
        symlink having the same parent gfid.  When an user/application
        requests for the paths of a regular file or a symlink with
        multiple hardlinks, using the parent gfids stored in the xattrs,
        the paths of the parent directories are generated as mentioned
        earlier. The base names of the hardlinks (with the same parent
        gfid) are determined by matching the actual backend inode numbers
        of each entry in the parent directory with that of the hardlink
        handle.
    
        Xattr is set on a regular file, link, and symbolic link as
        follows, Xattr name : trusted.pgfid.<pargfidstr> Xattr value :
        <number of hardlinks to a regular file/symlink with the same
        parentgfid>
    
        If a regular file, hard link, symbolic link is created then an
        xattr in the above format is set in the backend.
    
    how to use?
    ===========
        This functionality can be used through getxattr interface. Two
        keys - glusterfs.ancestry.dentry and glusterfs.ancestry.path - enable
        usage of this functionality. A successful getxattr will have the
        result stored under same keys. Values will be,
    
        glusterfs.ancestry.dentry:
        --------------------------
        A linked list of gf-dirent structures for all possible paths from
        root to this gfid. If there are multiple paths, the linked-list
        will be a series of paths one after another. Each path will be a
        series of dentries representing all components of the path. This
        key is primarily for internal usage within glusterfs.
    
        glusterfs.ancestry.path:
        ------------------------
        A string containing all possible paths from root to this gfid.
        Multiple hardlinks of a file or a symlink are displayed as a colon
        seperated list (this could interfere with path components
        containing ':').
    
        e.g. If there is a file "file1" in root directory with two hardlinks,
             "/dir2/link2tofile1" and "/dir1/link1tofile1", then
    
             [root@alpha gfsmntpt]# getfattr -n glusterfs.ancestry.path -e text
              file1
              glusterfs.ancestry.path="/file1:/dir2/link2tofile1:/dir1/link1tofile1"
    
        Thanks Amar, Avati and Venky for the inputs.
    
    Original Author: Ramana Raja <rraja@redhat.com>
    BUG: 990028
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Change-Id: I0eaa9101e333e0c1f66ccefd9e95944dd4a27497
    Reviewed-on: http://review.gluster.org/5951
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1d554b179f63a5a56ae447f2a5b0044c49ae2642
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 21 16:17:32 2013 +0530

    cluster/afr: Provide HA for pathinfo getxattr
    
    Problem:
    afr_[f]getxattr_pathinfo_cbks fail the fop even when it succeeded on
    one of the bricks. This can happen if the last response to pathinfo
    [f]getxattr is a failure.
    
    Fix:
    Remember if any of the [f]getxattr_pathinfos are successful and send
    that as the op_ret/op_errno value to the xlators above.
    
    Note:
    Winding fop to a client xlator that is not connected to server produces
    an error log. Preventing that by not even winding fop when client xlator
    is DOWN.
    
    Change-Id: I846e8c47423ffcfa2eabffe8924534781a36841a
    BUG: 1032927
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6332
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b87d96b97d4a0cdc0883bec8ea8b4730b82fb3ba
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Thu Nov 21 17:13:58 2013 +0530

    gNFS: More clean up for Gluster NFS
    
    1) Fix the typo in NFS default ACL
       The typo was introduced as part of the Fix to BZ 1009210 i.e.
       http://review.gluster.org/5980. The user ACL xattr structure
       was passed to default ACL xattr.
    
    2) Clean up NFS code to avoid unnecessary SEGV in
       rpcsvc_drc_reconfigure() which was not validating the
       svc->drc. Add a routine rpcsvc_drc_deinit() to handle
       the clean up of DRC specific data structures. For init(),
       use rpcsvc_drc_init().
    
    3) nfs_init_state() was returning wrong value even if the
       registration with portmapper failed, causing the NFS
       server process to hang around. As a result it used to
       get SEGV during rpcsvc_drc_reconfigure().
    
    4) Clean up memfactor usage across nfs.c nfs3.c.
    
    Change-Id: I5cea26cb68dd8a822ec0ae104952f67fe63fa703
    BUG: 1009210
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6329
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 07a3b04d5ce1d7a22a4ce01f1b6b8f8fc6ffbb05
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Nov 12 20:27:35 2013 +0530

    tests: add EXPECT_NOT macro
    
    We needed this macro while writing test cases for quota. With quota,
    a directory size is only guaranteed to be within some margin of quota
    limit, but not an accurate number. With not knowing what size to
    expect and EXPECT macro not complete enough to accept ranges of sizes,
    we can atleast write test-cases with EXPECT_NOT macro. After copying
    data to an empty file, it will be guaranteed the size will not be
    zero. This is good enough for quota test cases.
    
    Change-Id: I722ebd68044716a5eeaf0bd7e9aae61df8469017
    BUG: 1022995
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/6253
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6e7817232ca39330a9e8ba2220f5636eeec375af
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Fri Nov 22 01:37:33 2013 -0800

    group-virt: To minimize 'split-brain' enable quorum under virt profile
    
    Quorum as default is necessary when storing virtual machine images. It
    would be necessary to enable both server and client quorum
    
    Currently defaulted values are:
    ----------------
    server-quorum-type=server
    quorum-type=auto
    ----------------
    
    Change-Id: Ic2adb5856ce3c2589476e872e988cae6eeb9b25e
    BUG: 1032080
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6340
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fee08b2cbf8c118d33dea745e0ae3033b36969da
Author: Anand Avati <avati@redhat.com>
Date:   Wed Nov 20 15:11:13 2013 -0800

    fuse: revalidate group id cache on uid/gid change detection
    
    - Remember the uid and gid of the pid at the time of caching
      the group id list.
    
    - Next time when referring to the cache confirm that uid and gid
      of that pid has not changed since. If it has, treat it like
      a timeout/cache miss.
    
    - Solves group id caching issue caused when Samba runs on gluster
      FUSE mount and changes the uid/gid on a per syscall basis.
    
    Change-Id: I3382b037ff0b6d5eaaa36d9c898232543475aeda
    BUG: 1032438
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6320
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 544dee895a43ec9bb98fc8ace3d124d44bb617f2
Author: Anand Avati <avati@redhat.com>
Date:   Fri Oct 11 00:20:15 2013 -0700

    syncops: expose @flags in syncop_rmdir()
    
    Change-Id: I9b73c1db728e4cb3948fc118cceb292b21d48b96
    BUG: 1021686
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6112
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d13bf457d489559fd8c011533b2201a113243d71
Author: Bala.FA <barumuga@redhat.com>
Date:   Thu Nov 21 16:35:40 2013 +0530

    cli: fix possible memory leaks
    
    BUG: 955548
    Change-Id: Iae410712e7e6d7a76cd537c77f1919e3b4cdf6bb
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/6328
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6157e4198c4ed5782936efd47f39e3e66463a9d2
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Nov 22 00:15:48 2013 +0530

    Add description for git based installations.
    
    Change-Id: I60e445539f255b3220f885bd790f800e4c1ea55a
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6333
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 689b86cfe6c9258c8507c8391ed62aa1a640c1e3
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Nov 20 13:41:49 2013 -0500

    libglusterfs: use correct check for linux falloc.h availability
    
    We should check for HAVE_LINUX_FALLOC_H rather than HAVE_FALLOC_H
    to determine whether to include linux/falloc.h.
    
    Change-Id: I05eca4de2893a88d6b9cc5ebfce738708b9960d4
    BUG: 1032378
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/6314
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit ed75205b1ca592d0b33cc5663e7bdc4ccfc2cf02
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Nov 18 17:38:03 2013 +0100

    Build storage/posix xlator if fallocate() does not exists
    
    If fallocate() does not exists, just return EOPNOTSUPP
    
    BUG: 764655
    Change-Id: I808114f733c88985519dc47fb7537e1ced1db077
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6289
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2bb025699a8b9b34491c8b13a2bbb6da302a5d77
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Fri Nov 15 14:19:11 2013 +0530

    bd: Add Zerofill FOP support
    
    BUG: 1028673
    Change-Id: I9ba8e3e6cf2f888640b4d2a2eb934a27ff903c42
    Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6290
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5e31894fbda74a524e1fe30d26f7ed82a77eb5ff
Author: Anand Avati <avati@redhat.com>
Date:   Tue Nov 19 23:45:32 2013 -0800

    mount/fuse: handle --gid-timeout=0 properly
    
    Fix the bug which was using the timeout value as a flag to indicate
    if it was set (and hence would fail when timeout=0 would evaluate
    as False)
    
    Change-Id: Ie9a8f28d35603458cdac26c9a4e0343e7eda7344
    BUG: 1032438
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6308
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ff7ee1ecd7a5562b79522853c8699f07df7fafc0
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Wed Nov 20 11:40:10 2013 +0530

    gNFS: Coverity fix for CID 1128906
    
    Fix the Coverity issue introduced in RFE: NFS volume set/reset
    commit i.e.  http://review.gluster.org/6236
    
    Change-Id: I817b9da03a3ce7f5511303faea0c50dfdad60ff4
    BUG: 1027409
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6307
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3c38ba1e7b4959602f945112a26b8aee904fefaa
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Nov 14 12:15:53 2013 +0530

    glusterd: Start rebalance only where required
    
    Gluster was starting rebalance processes on peers where it wasn't
    required in two cases.
    - For a normal rebalance command on a volume, rebalance processes were
      started on all peers instead of just the peers which contain bricks of
      the volume
    - For rebalance process being restarted by a volume sync, caused by a
      new peer being probed or a peer restarting, rebalance processes were
      started on all peers, for both a normal rebalance and for remove-brick
      needing rebalance.
    
    This patch adds a new check before starting rebalance process in the
    above two cases.
    - For rebalance process required by a rebalance command, each peer will
      check if it contains atleast one brick of the volume
    - For rebalance process required by a remove-brick command, each peer
      will check if it contains atleast one of the bricks being removed
    
    Change-Id: I512da16994f0d5482889c3a009c46dc20a8a15bb
    BUG: 1031887
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6301
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bc9f0bb5ce108cba7e88be123681e2c269da31b7
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Nov 12 15:08:26 2013 +0530

    cli: List only nodes which have rebalance started in rebalance status
    
    Listing the nodes on which rebalance hasn't been started is just giving
    out extraneous information.
    
    Also, refactor the rebalance status printing code into a single function
    and use it for both rebalance and remove-brick status.
    
    BUG: 1031887
    Change-Id: I47bd561347dfd6ef76c52a1587916d6a71eac369
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6300
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e0dbbe851baf564037edc3b967563730a0ed9c81
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Nov 19 15:38:57 2013 +0530

    mgmt/glusterd: fix undefined sybmol error related to BD
    
    Change-Id: I2210f1ac7de04c6025c0ec02d998b626d41466ae
    BUG: 1028672
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6303
    Reviewed-by: M. Mohan Kumar <mohan@in.ibm.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d56be51dc665d96e4cd0fa25147b2d4da147561f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Nov 17 15:23:41 2013 +0100

    Do not build fallocate FUSE FOP if the system call does not exist
    
    BUG: 764655
    Change-Id: Ica310e75bee16741b837e658981238c1b99c254f
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6288
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 00aafce07140a96e641ad5d1f701932823738aaa
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Nov 17 01:51:48 2013 +0100

    Python build flag detection
    
    Ask python-config for proper python build flags
    
    BUG: 764655
    Change-Id: I7aede0f93637c61dbafc43580bff46af60f0f0d3
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6283
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5d2439657f7f81f1dcdc45e960c91ce4196ae118
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Nov 17 15:05:42 2013 +0100

    NetBSD missing backtrace(3) portability fix
    
    Implement backtrace(3) and backtrace_symbols(3) which do not exist in NetBSD
    While there, remove duplicate #include <stdio.h>
    
    BUG: 764655
    Change-Id: Iccd695765906e085c3f8fcb670506d4fea68fa39
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6285
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bf6f49a309f1894073f208b4a97a7baa6ec3e136
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Nov 17 05:37:01 2013 +0100

    Search gettext() in -lintl
    
    If gettext() is not found in libc, look it up in libintl (this is where
    NetBSD has it)
    
    BUG: 764655
    Change-Id: Ifba8681b8603ead5d0b8587b71457250982077e1
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6287
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fd2e62404cc7b8efbe71153a4361ab59f374f303
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Nov 19 13:57:30 2013 +0100

    autogen.sh portability fixes
    
    - Do not assume tar has --version, as BSD tar does not
    - Allow specifying python binary through PYTHONBIN in case it is e.g. python2.7
    
    BUG: 764655
    Change-Id: I71f0f4830e10915782775de811c92db8e6ab4c55
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6281
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 56b82b5294ae0ea0e73ae3d6bb58504442773e0f
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Mon Nov 18 12:49:21 2013 +0530

    Fix xml compilation error
    
    Compiling GlusterFS without xml package results in following build error
    
    cli-rpc-ops.o: In function `gf_cli_status_cbk':
    /home/mohan/Work/glusterfs/cli/src/cli-rpc-ops.c:6430: undefined
    reference to `cli_xml_output_vol_status_tasks_detail'
    
    Change-Id: I49b3c46ac3340c40e372bef4690cedb41df20e8a
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6295
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 56d0124224259ccfc4c8b1cc33939902ed480d23
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Fri Nov 15 18:23:29 2013 +0530

    BD fixes for coverity scan
    
    BUG: 1028672
    Change-Id: I2e7889fb113cedd2d5928b210149d3fd7b8b22ab
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6292
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1ef8a597db1ead482612f2f0bcc212d9a1349ccb
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Fri Nov 15 17:50:34 2013 +0530

    Fixes for ZF reported by coverity
    
    BUG: 1028673
    Change-Id: I7c75738cca22c81c5629d579ef5bea24000e622e
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6291
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f9443a3f148dde4bb1a628184140d59f45db64a2
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Nov 17 02:03:03 2013 +0100

    Have #include <signal.h> for kill(2)
    
    BUG: 764655
    Change-Id: I4d18c9a6c00cb4696645fcb437398562f00b9d24
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6284
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit eb412da2375e6bbae5cc7a39db9e60fbbdd7aaa0
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Nov 17 02:17:59 2013 +0100

    NetBSD missing loff_t portability fix
    
    define loff_t as off_t, is is already long long anyway.
    
    BUG: 764655
    Change-Id: I99edda9b804475a8696c2d32ccf8eae152851e21
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6286
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 432cecfbff496bfa9e71e8cbbed789458656c553
Author: Bala.FA <barumuga@redhat.com>
Date:   Tue Oct 29 17:17:12 2013 +0530

    cli: add peerid to volume status xml output
    
    This patch adds <peerid> tag to bricks and nfs/shd like services to
    volume status xml output.
    
    BUG: 955548
    Change-Id: I9aaa9266e4d56f632235eaeef565e92d757c0694
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/6162
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 884a668a9c3e12e17d64ebd5ccd9fbf3d203fd1e
Author: Bharata B Rao <bharata@linux.vnet.ibm.com>
Date:   Fri Nov 15 10:11:58 2013 +0530

    zerofill: Change the type of len argument of glfs_zerofill() to off_t
    
    glfs_zerofill() can be potentially called to zero-out entire file and
    hence allow for bigger value of length parameter.
    
    Change-Id: I75f1d11af298915049a3f3a7cb3890a2d72fca63
    BUG: 1028673
    Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
    Reviewed-on: http://review.gluster.org/6266
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: M. Mohan Kumar <mohan@in.ibm.com>
    Tested-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f21cefed298ba21f4739d6ab4ceea81b97d2aab8
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Thu Nov 14 13:12:09 2013 +0530

    fuse: Check the return status from state->resolve_now
    
    Change-Id: I85fc6dd393449d365bb908b38c2827b58cb08171
    BUG: 1030208
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6262
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e479660d9dd8bf7017c7dc78ccfa6edd9c51ec7a
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Mon Oct 28 12:46:37 2013 +0530

    gNFS: RFE for NFS connection behavior
    
    Implement reconfigure() for NFS xlator so that volume set/reset wont
    restart the NFS server process. But few options can not be reconfigured
    dynamically e.g. nfs.mem-factor, nfs.port etc which needs NFS to be
    restarted.
    
    Change-Id: Ic586fd55b7933c0a3175708d8c41ed0475d74a1c
    BUG: 1027409
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6236
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2990befa4cf9219f33b21b6c50d3e2afa4b7461b
Author: Poornima <pgurusid@redhat.com>
Date:   Thu Nov 14 01:29:30 2013 +0000

    gfapi: Closed the logfile fd in glfs_fini
    
    The logfile fd is not closed even after calling glfs_fini,
    hence in smb mount if connection to glusterfs volume fails
    at a point after the log file was opened, the fd would remain
    open until the process dies.
    
    This patch closes the logfile fd in glfs_fini.
    
    Change-Id: I608bfac9c6833b42750b0383ad26fd33ee378ee1
    BUG: 1030228
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6263
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4efbff29e773a8c59605f87bc3939c9c71b9da16
Author: Edward Shishkin <edward@redhat.com>
Date:   Wed Mar 13 21:56:46 2013 +0100

    Transparent data encryption and metadata authentication
    
    .. in the systems with non-trusted server
    
    This new functionality can be useful in various cloud technologies.
    It is implemented via a special encryption/crypt translator,which
    works on the client side and performs encryption and authentication;
    
                  1. Class of supported algorithms
    
    The crypt translator can support any atomic symmetric block cipher
    algorithms (which require to pad plain/cipher text before performing
    encryption/decryption transform (see glossary in atom.c for
    definitions). In particular, it can support algorithms with the EOF
    issue (which require to pad the end of file by extra-data).
    
    Crypt translator performs translations
    user -> (offset, size) -> (aligned-offset, padded-size) ->server
    (and backward), and resolves individual FOPs (write(), truncate(),
    etc) to read-modify-write sequences.
    
    A volume can contain files encrypted by different algorithms of the
    mentioned class. To change some option value just reconfigure the
    volume.
    
    Currently only one algorithm is supported: AES_XTS.
    
    Example of algorithms, which can not be supported by the crypt
    translator:
    
    1. Asymmetric block cipher algorithms, which inflate data, e.g. RSA;
    2. Symmetric block cipher algorithms with inline MACs for data
       authentication.
    
                       2. Implementation notes.
    
    a) Atomic algorithms
    
    Since any process in a stackable file system manipulates with local
    data (which can be obsoleted by local data of another process), any
    atomic cipher algorithm without proper support can lead to non-POSIX
    behavior. To resolve the "collisions" we introduce locks: before
    performing FOP->read(), FOP->write(), etc. the process should first
    lock the file.
    
    b) Algorithms with EOF issue
    
    Such algorithms require to pad the end of file with some extra-data.
    Without proper support this will result in losing information about
    real file size. Keeping a track of real file size is a responsibility
    of the crypt translator. A special extended attribute with the name
    "trusted.glusterfs.crypt.att.size" is used for this purpose. All files
    contained in bricks of encrypted volume do have "padded" sizes.
    
                      3. Non-trusted servers and
                         Metadata authentication
    
    We assume that server, where user's data is stored on is non-trusted.
    It means that the server can be subjected to various attacks directed
    to reveal user's encrypted personal data. We provide protection
    against such attacks.
    
    Every encrypted file has specific private attributes (cipher algorithm
    id, atom size, etc), which are packed to a string (so-called "format
    string") and stored as a special extended attribute with the name
    "trusted.glusterfs.crypt.att.cfmt". We protect the string from
    tampering. This protection is mandatory, hardcoded and is always on.
    Without such protection various attacks (based on extending the scope
    of per-file secret keys) are possible.
    
    Our authentication method has been developed in tight collaboration
    with Red Hat security team and is implemented as "metadata loader of
    version 1" (see file metadata.c). This method is NIST-compliant and is
    based on checking 8-byte per-hardlink MACs created(updated) by
    FOP->create(), FOP->link(), FOP->unlink(), FOP->rename() by the
    following unique entities:
    
    . file (hardlink) name;
    . verified file's object id (gfid).
    
    Every time, before manipulating with a file, we check it's MACs at
    FOP->open() time. Some FOPs don't require a file to be opened (e.g.
    FOP->truncate()). In such cases the crypt translator opens the file
    mandatory.
    
                            4. Generating keys
    
    Unique per-file keys are derived by NIST-compliant methods from the
    
    a) parent key;
    b) unique verified object-id of the file (gfid);
    Per-volume master key, provided by user at mount time is in the root
    of this "tree of keys".
    
    Those keys are used to:
    
    1) encrypt/decrypt file data;
    2) encrypt/decrypt file metadata;
    3) create per-file and per-link MACs for metadata authentication.
    
                              5. Instructions
                     Getting started with crypt translator
    
    Example:
    
    1) Create a volume "myvol" and enable encryption:
    
       # gluster volume create myvol pepelac:/vols/xvol
       # gluster volume set myvol encryption on
    
    2) Set location (absolute pathname) of your master key:
    
       # gluster volume set myvol encryption.master-key /home/me/mykey
    
    3) Set other options to override default options, if needed.
       Start the volume.
    
    4) On the client side make sure that the file /home/me/mykey exists
       and contains proper per-volume master key (that is 256-bit AES
       key). This key has to be in hex form, i.e. should be represented
       by 64 symbols from the set  {'0', ..., '9', 'a', ..., 'f'}.
       The key should start at the beginning of the file. All symbols at
       offsets >= 64 are ignored.
    
    5) Mount the volume "myvol" on the client side:
    
       # glusterfs --volfile-server=pepelac --volfile-id=myvol /mnt
    
       After successful mount the file which contains master key may be
       removed. NOTE: Keeping the master key between mount sessions is in
       user's competence.
    
    **********************************************************************
    
    WARNING! Losing the master key will make content of all regular files
    inaccessible. Mount with improper master key allows to access content
    of directories: file names are not encrypted.
    
    **********************************************************************
    
                   6. Options of crypt translator
    
    1) "master-key": specifies location (absolute pathname) of the file
       which contains per-volume master key. There is no default location
       for master key.
    
    2) "data-key-size": specifies size of per-file key for data encryption
       Possible values:
       . "256" default value
       . "512"
    
    3) "block-size": specifies atom size. Possible values:
       . "512"
       . "1024"
       . "2048"
       . "4096" default value;
    
                           7. Test cases
    
    Any workload, which involves the following file operations:
    
    ->create();
    ->open();
    ->readv();
    ->writev();
    ->truncate();
    ->ftruncate();
    ->link();
    ->unlink();
    ->rename();
    ->readdirp().
    
                            8. TODOs:
    
    1) Currently size of IOs issued by crypt translator is restricted
       by block_size (4K by default). We can use larger IOs to improve
       performance.
    
    Change-Id: I2601fe95c5c4dc5b22308a53d0cbdc071d5e5cee
    BUG: 1030058
    Signed-off-by: Edward Shishkin <edward@redhat.com>
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4667
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 98e796e50198945adc660e42f3f5ab5b668f7bba
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Sep 10 15:13:54 2013 +0530

    cluster/dht - rebalance: handle the rebalance @ inode level (!fd level)
    
    * migrate all the fd's on an inode to newer subvol after rebalance
    * use the migration in progress flag in inode, so all the operations
      on the inode can make use of it
    
    Change-Id: Ib807a46e927a1062688fc15119c916797c52a350
    BUG: 1013456
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5891
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5d7560e11e371919c97f78381c0d0c90885ce80f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Sep 10 17:40:04 2013 +0530

    libglusterfs/inode: introduce new APIs for ctx handling
    
    * inode_ctx_reset{0,1,2}() for reseting value1, value2, and both respectively
    * inode_ctx_get0() - to get the first value only
    * inode_ctx_set0() - to set the first value only
    * inode_ctx_get1() - to get the second value only
    * inode_ctx_set1() - to set the second value only
    
    Change-Id: I4dfbdac81d6a3f4e5784e060c76edabb1692ce03
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5890
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit cc742479562f085034b1ea969d4a5869d28a7136
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Wed Nov 13 22:44:43 2013 +0530

    bd: Add test case for bd xlator
    
    Change-Id: I73a0bfa7085d2e71b2489687fa53f5fe7d1e8ea1
    BUG: 1028672
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6050
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 81a57679c20ac0ac9b48e313af75036132e3a5ad
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Wed Nov 13 22:44:43 2013 +0530

    bd: Add support to create clone, snapshot and merge of LV images.
    
    Special xattr names "clone" & "snapshot" can be used to create full and
    linked clone of the LV images. GFID of destination posix file (to be
    mapped) is passed as a value to the xattr. Destination posix file must
    exist before running this operation.
    
    These operations form a basis for offloading storage related operations
    from QEMU to GlusterFS.
    
    Syntax for full clone: xattr name: "clone" value: "gfid-of-dest-file"
    Syntax for linked clone: xattr name: "snapshot" value: "gfid-of-dest-file"
    Syntax for merging: xattr name: "merge" value: "path-to-snapshot-file"
    
    Example:
    	setfattr -n clone -v <gfid-of-dest-file> /media/source
    	setfattr -n snapshot -v <gfid-of-dest-file> /media/source
    	setfattr -n merge -v "/media/sn" /media/sn
    
    Change-Id: Id9f984a709d4c2e52a64ae75bb12a8ecb01f8776
    BUG: 1028672
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/5626
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b222ce817f5f324fe20d4d3614001ed2f177afb8
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Wed Nov 13 22:44:42 2013 +0530

    bd: Add aio support to BD xlator
    
    Volume option bd-aio controls AIO feature for BD xlator. Code taken from
    posix-aio.c
    
    Change-Id: Ib049bd59c9d3f9101d33939838322cfa808de053
    BUG: 1028672
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/5748
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6ec9c4599e96de9dcae9426eae6bb1dde4dc7549
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Wed Nov 13 22:44:42 2013 +0530

    bd: Add BD support to other xlators
    
    Make changes to distributed xlator to work with BD xlator. Unlike files,
    a block device can't be removed when its opened. So some part of the
    code were moved down to avoid this situation. Also before truncating a
    BD file its BD_XATTR should be set otherwise truncate will result in
    truncating posix file. So file is created with needed BD_XATTR and
    truncate is invoked. Also enables BD xlator in stripe volume type.
    
    Change-Id: If127516e261fac5fc5b137e7fe33e100bc92acc0
    BUG: 1028672
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/5235
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 48c40e1a42efe1b59126406084821947d139dd0e
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Wed Nov 13 22:44:42 2013 +0530

    bd: posix/multi-brick support to BD xlator
    
    Current BD xlator (block backend) has a few limitations such as
    * Creation of directories not supported
    * Supports only single brick
    * Does not use extended attributes (and client gfid) like posix xlator
    * Creation of special files (symbolic links, device nodes etc) not
      supported
    
    Basic limitation of not allowing directory creation is blocking
    oVirt/VDSM to consume BD xlator as part of Gluster domain since VDSM
    creates multi-level directories when GlusterFS is used as storage
    backend for storing VM images.
    
    To overcome these limitations a new BD xlator with following
    improvements is suggested.
    
    * New hybrid BD xlator that handles both regular files and block device
      files
    * The volume will have both POSIX and BD bricks. Regular files are
      created on POSIX bricks, block devices are created on the BD brick (VG)
    * BD xlator leverages exiting POSIX xlator for most POSIX calls and
      hence sits above the POSIX xlator
    * Block device file is differentiated from regular file by an extended
      attribute
    * The xattr 'user.glusterfs.bd' (BD_XATTR) plays a role in mapping a
      posix file to Logical Volume (LV).
    * When a client sends a request to set BD_XATTR on a posix file, a new
      LV is created and mapped to posix file. So every block device will
      have a representative file in POSIX brick with 'user.glusterfs.bd'
      (BD_XATTR) set.
    * Here after all operations on this file results in LV related
      operations.
    
    For example opening a file that has BD_XATTR set results in opening
    the LV block device, reading results in reading the corresponding LV
    block device.
    
    When BD xlator gets request to set BD_XATTR via setxattr call, it
    creates a LV and information about this LV is placed in the xattr of the
    posix file. xattr "user.glusterfs.bd" used to identify that posix file
    is mapped to BD.
    
    Usage:
    Server side:
    [root@host1 ~]# gluster volume create bdvol host1:/storage/vg1_info?vg1 host2:/storage/vg2_info?vg2
    It creates a distributed gluster volume 'bdvol' with Volume Group vg1
    using posix brick /storage/vg1_info in host1 and Volume Group vg2 using
    /storage/vg2_info in host2.
    
    [root@host1 ~]# gluster volume start bdvol
    
    Client side:
    [root@node ~]# mount -t glusterfs host1:/bdvol /media
    [root@node ~]# touch /media/posix
    It creates regular posix file 'posix' in either host1:/vg1 or host2:/vg2 brick
    [root@node ~]# mkdir /media/image
    [root@node ~]# touch /media/image/lv1
    It also creates regular posix file 'lv1' in either host1:/vg1 or
    host2:/vg2 brick
    [root@node ~]# setfattr -n "user.glusterfs.bd" -v "lv" /media/image/lv1
    [root@node ~]#
    Above setxattr results in creating a new LV in corresponding brick's VG
    and it sets 'user.glusterfs.bd' with value 'lv:<default-extent-size'
    [root@node ~]# truncate -s5G /media/image/lv1
    It results in resizig LV 'lv1'to 5G
    
    New BD xlator code is placed in xlators/storage/bd directory.
    
    Also add volume-uuid to the VG so that same VG can't be used for other
    bricks/volumes. After deleting a gluster volume, one has to manually
    remove the associated tag using vgchange <vg-name> --deltag
    <trusted.glusterfs.volume-id:<volume-id>>
    
    Changes from previous version V5:
    * Removed support for delayed deleting of LVs
    
    Changes from previous version V4:
    * Consolidated the patches
    * Removed usage of BD_XATTR_SIZE and consolidated it in BD_XATTR.
    
    Changes from previous version V3:
    * Added support in FUSE to support full/linked clone
    * Added support to merge snapshots and provide information about origin
    * bd_map xlator removed
    * iatt structure used in inode_ctx. iatt is cached and updated during
    fsync/flush
    * aio support
    * Type and capabilities of volume are exported through getxattr
    
    Changes from version 2:
    * Used inode_context for caching BD size and to check if loc/fd is BD or
      not.
    * Added GlusterFS server offloaded copy and snapshot through setfattr
      FOP. As part of this libgfapi is modified.
    * BD xlator supports stripe
    * During unlinking if a LV file is already opened, its added to delete
      list and bd_del_thread tries to delete from this list when a last
      reference to that file is closed.
    
    Changes from previous version:
    * gfid is used as name of LV
    * ? is used to specify VG name for creating BD volume in volume
      create, add-brick. gluster volume create volname host:/path?vg
    * open-behind issue is fixed
    * A replicate brick can be added dynamically and LVs from source brick
      are replicated to destination brick
    * A distribute brick can be added dynamically and rebalance operation
      distributes existing LVs/files to the new brick
    * Thin provisioning support added.
    * bd_map xlator support retained
    * setfattr -n user.glusterfs.bd -v "lv" creates a regular LV and
      setfattr -n user.glusterfs.bd -v "thin" creates thin LV
    * Capability and backend information added to gluster volume info (and
    --xml) so
      that management tools can exploit BD xlator.
    * tracing support for bd xlator added
    
    TODO:
    * Add support to display snapshots for a given LV
    * Display posix filename for list-origin instead of gfid
    
    Change-Id: I00d32dfbab3b7c806e0841515c86c3aa519332f2
    BUG: 1028672
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/4809
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 15a8ecd9b3eedf80881bd3dba81f16b7d2cb7c97
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Wed Nov 13 22:44:42 2013 +0530

    bd_map: Remove bd_map xlator
    
    Remove bd_map xlator and CLI related changes.
    
    Change-Id: If7086205df1907127c1a1fa4ba603f1c48421d09
    BUG: 1028672
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/5747
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c1109ed6c6c7bff0df22c304158e9f392f83cf59
Author: Anand Avati <avati@redhat.com>
Date:   Wed Oct 30 14:30:26 2013 -0700

    gfapi: introduce glfs_readdir() and glfs_readdirplus() APIs
    
    Change-Id: I6b233bf647585675f233898351bf593f251716cc
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6201
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit eeac099cf405849f07989c410968e77f95acdc77
Author: Vikhyat Umrao <vumrao@redhat.com>
Date:   Tue Nov 12 18:11:23 2013 +0530

    server/rpc: bricks goes offline and comes back online, with lots of "No such file or directory" log messages
    
    Problem:
    Messages were getting logged very frequently at log level INFO.
    
    [2013-03-01 11:34:28.029222] I [server3_1-fops.c:1541:server_open_cbk] vol-server: 993888: OPEN (null) (--) ==> -1 (No such file or directory)
    [2013-03-01 11:34:28.031579] I [server3_1-fops.c:252:server_inodelk_cbk] vol-server: 993896: INODELK (null) (--) ==> -1 (No such file or directory)
    [2013-03-01 11:34:28.034041] I [server3_1-fops.c:252:server_inodelk_cbk] vol-server: 993914: INODELK (null) (--) ==> -1 (No such file or directory)
    [2013-03-01 11:34:28.040435] I [server3_1-fops.c:1338:server_flush_cbk] vol-server: 993938: FLUSH -2 (--) ==> -1 (No such file or directory)
    
    Solution:
    Moved them to DEBUG log level if error number equlas to ENOENT else to ERROR log level.
    It will help in decreasing the size of log files at INFO log level.
    For server_open_cbk and for some other functions we already have a patch, below is the URL for it.
    URL- http://review.gluster.org/6241
    This patch solves logging problem for functions server_inodelk_cbk and server_flush_cbk.
    
    Change-Id: I57372e851371e466f1674726015e28378b826f5f
    BUG: 1029372
    Signed-off-by: Vikhyat Umrao<vumrao@redhat.com>
    Reviewed-on: http://review.gluster.org/6252
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3a4bd6ddc551179a1785c3535e477ce5867da68d
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Wed Nov 13 10:45:40 2013 +0530

    zerofill: Update API version
    version 6 adds zerofill FOP
    
    BUG: 1028673
    Change-Id: I27cfc48cd6f7f0f6daf94e1c9cfbe420a0d090af
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/6255
    Reviewed-by: Bharata B Rao <bharata.rao@gmail.com>
    Tested-by: Bharata B Rao <bharata.rao@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b18257183d137c7ea8a76b4d57812fe26d9ea850
Author: Prashanth Pai <ppai@redhat.com>
Date:   Mon Mar 26 14:33:41 2012 +0530

    features/compress: Compression/DeCompression translator
    
    * When a writev call occurs, the client compresses the data before
      sending it to server. On the server, compressed data is decompressed.
      Similarly, when a readv call occurs, the server compresses the data
      before sending it to client. On the client, the compressed data is
      decompressed. Thus the amount of data sent over the wire is minimized.
    
    * Compression/Decompression is done using Zlib library.
    
    * During normal operation, this is the format of data sent over wire :
      <compressed-data> + trailer(8)
      The trailer contains the CRC32 checksum and length of original
      uncompressed data. This is used for validation.
    
    HOW TO USE
    ----------
    Turning on compression xlator:
    gluster volume set <vol_name> compress on
    
    Configurable options:
    gluster volume set <vol_name> compress.compression-level 8
    gluster volume set <vol_name> compress.min-size 50
    
    Change-Id: Ib7a66b6f1f70fe002b7c513588cdf75c69370805
    BUG: 923540
    Original-author : Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Prashanth Pai <nullpai@gmail.com>
    Signed-off-by: Prashanth Pai <ppai@redhat.com>
    Reviewed-on: http://review.gluster.org/3251
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 27935ee84c484fff3d8d29218c197812701957ed
Author: Vijaykumar M <vmallika@redhat.com>
Date:   Mon Nov 11 12:05:55 2013 +0530

    cli: Set the o/p width of hostname to 8 characters
    
    Change-Id: I91dcb19ba4d31c17e6041155c0e59af457b87f1b
    BUG: 1028871
    Signed-off-by: Vijaykumar M <vmallika@redhat.com>
    Reviewed-on: http://review.gluster.org/6245
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cfbc7ddbadfc7d01124aa713c4769c45e0522db5
Author: Vikhyat Umrao <vumrao@redhat.com>
Date:   Mon Nov 11 14:52:54 2013 +0530

    server/rpc: Numerous entries of error - "No such file or directory" in bricks log
    
    Problem:
    Messages were getting logged very frequently at log level INFO.
    
    One of the log file snippet -
    
    [2013-10-27 00:05:01.501355] I [server3_1-fops.c:1707:server_stat_cbk] 0-vol-server: 24846575: STAT (null) (--) ==> -1 (No such file or directory)
    [2013-10-27 00:05:01.505101] I [server3_1-fops.c:1707:server_stat_cbk] 0-vol-server: 24846577: STAT (null) (--) ==> -1 (No such file or directory)
    [2013-10-27 00:05:01.507299] I [server3_1-fops.c:1707:server_stat_cbk] 0-vol-server: 24846578: STAT (null) (--) ==> -1 (No such file or directory)
    [2013-10-20 19:50:35.554563] I [server3_1-fops.c:1538:server_open_cbk] 0-vol-server: 18714687: OPEN <gfid:01c70ca0-1952-4e82-abee-a07205757d8e>
    (01c70ca0-1952-4e82-abee-a07205757d8e) ==> -1 (No such file or directory)
    [2013-10-20 19:50:35.555520] I [server3_1-fops.c:1538:server_open_cbk] 0-vol-server: 18714697: OPEN <gfid:01c70ca0-1952-4e82-abee-a07205757d8e>
    (01c70ca0-1952-4e82-abee-a07205757d8e) ==> -1 (No such file or directory)
    [2013-10-20 19:50:35.558292] I [server3_1-fops.c:1538:server_open_cbk] 0-vol-server: 18714712: OPEN (null) (--) ==> -1 (No such file or directory)
    
    Solution:
    Moved them to DEBUG log level if error number equlas to ENOENT else to ERROR log level.
    It will help in decreasing the size of log files at INFO log level.
    
    Change-Id: I23d74320c9c21bbce4805c20295556cc2cc0a8d8
    BUG: 808073
    Signed-off-by: Vikhyat Umrao <vumrao@redhat.com>
    Reviewed-on: http://review.gluster.org/6241
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cbb47056ab09ae09eed2550584f190fd5a42fb12
Author: Dawit Alemu <dalemu@redhat.com>
Date:   Fri Nov 8 13:26:52 2013 -0500

    cli: write 'volume rebalance' error message in xml format when
    --xml is specified
    
    When 'volume rebalance' encounters an error the cli prints the
    error message in plain text independent of whether --xml is
    specified. This throws off client application that expect xml
    output (as mentioned in bz1026143).
    
    Now, if the --xml flag is supplied, the cli print 'volume
    rebalance' error messages in xml format.
    
    Change-Id: I16c6a7a4cdd2819eb73422ab849125986dc299a6
    BUG: 1026143
    Signed-off-by: Dawit Alemu <dalemu@redhat.com>
    Reviewed-on: http://review.gluster.org/6242
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b06ecde2997b72a41b2f2d25d55e61d30ea46bc2
Author: Brian Foster <bfoster@redhat.com>
Date:   Fri Oct 18 07:36:38 2013 -0400

    features/qemu-block: simplify coroutine model to use single synctask, ucontext
    
    The current coroutine model, mapping synctasks 1-1 with qemu internal
    Coroutines, has some unresolved raciness issues. This problem usually
    manifests as lifecycle mismatches between top-level (gluster created)
    synctasks and the subsequently created internal coroutines from that
    context. Qemu's internal queueing (and locking) can cause situations
    where the top-level synctask is destroyed before the internal scheduler
    has released references to memory, leading to use after free crashes
    and asserts.
    
    Simplify the coroutine model to use a single synctask as a coroutine
    processor and rely on the existing native ucontext coroutine
    implementation. The syncenv thread is donated to qemu and ensures a
    single top-level coroutine is processed at a time. Qemu now has
    complete control over coroutine scheduling.
    
    BUG: 986775
    Change-Id: I38223479a608d80353128e390f243933fc946fd6
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/6110
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0826f9073a93c6d499f3d2077695455854d0fa7f
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Sep 18 07:03:07 2013 -0400

    features/qemu-block: add qemu backing image support (clone)
    
    Add basic backing image support to the block-format mechanism. This
    is a functionality checkpoint that enables the raw mechanism
    required to support client driven "snapshot" and "clone" requests.
    
    This change enhances the block-format setxattr command to support
    an additional and optional backing image reference. For example:
    
    setxattr -n trusted.glusterfs.block-format -v "qcow2:10GB:<bimg>" ./newimage
    
    ... where <bimg> refers to the backing image for unallocated blocks
    in newimage. <bimg> can be provided in one of two formats:
    
    - a gfid string in the following format (assuming a valid gfid):
    
    <gfid:00000000-0000-0000-0000-000000000000>
    
    - or a filename that must be resident in the same directory as the
    new clone file being formatted. E.g.,
    
    setxattr -n trusted.glusterfs.block-format -v "qcow2:10GB:baseimg" ./newimage
    
    This latter format is more restrictive, simply provided for
    convenience or until something more refined is available.
    
    This change makes no assumptions about the backing image file and
    affords no additional protection. It is up to the user/client to
    recognize the relationship between the files and manage them
    appropriately (i.e., no writes to the backing image, etc.).
    
    BUG: 986775
    Change-Id: I7aff7bdc59b85a6459001a6bfeae4db6bf74f703
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5967
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c8fef37c5d566c906728b5f6f27baaa9a8d2a20d
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Sat Nov 9 14:51:53 2013 +0530

    glusterfs: zerofill support
    
    Add support for a new ZEROFILL fop. Zerofill writes zeroes to a file in
    the specified range. This fop will be useful when a whole file needs to
    be initialized with zero (could be useful for zero filled VM disk image
    provisioning or  during scrubbing of VM disk images).
    
    Client/application can issue this FOP for zeroing out. Gluster server
    will zero out required range of bytes ie server offloaded zeroing. In
    the absence of this fop,  client/application has to repetitively issue
    write (zero) fop to the server, which is very inefficient method because
    of the overheads involved in RPC calls  and acknowledgements.
    
    WRITESAME is a  SCSI T10 command that takes a block of data as input and
    writes the same data to other blocks and this write is handled
    completely within the storage and hence is known as offload . Linux ,now
    has support for SCSI WRITESAME command which is exposed to the user in
    the form of BLKZEROOUT ioctl.  BD Xlator can exploit BLKZEROOUT ioctl to
    implement this fop. Thus zeroing out operations can be completely
    offloaded to the storage device , making it highly efficient.
    
    The fop takes two arguments offset and size. It zeroes out 'size' number
    of bytes in an opened file starting from 'offset' position.
    
    This patch adds zerofill support to the following areas:
    	- libglusterfs
    	- io-stats
    	- performance/md-cache,open-behind
    	- quota
    	- cluster/afr,dht,stripe
    	- rpc/xdr
    	- protocol/client,server
    	- io-threads
    	- marker
    	- storage/posix
    	- libgfapi
    
    Client applications can exloit this fop by using glfs_zerofill introduced in
    libgfapi.FUSE support to this fop has not been added as there is no system call
    for this fop.
    
    Changes from previous version 3:
    * Removed redundant memory failure log messages
    
    Changes from previous version 2:
    * Rebased and fixed build error
    
    Changes from previous version 1:
    * Rebased for latest master
    
    TODO :
         * Add zerofill support to trace xlator
         * Expose zerofill capability as part of gluster volume info
    
    Here is a performance comparison of server offloaded zeofill vs zeroing
    out using repeated writes.
    
    [root@llmvm02 remote]# time ./offloaded aakash-test log 20
    
    real	3m34.155s
    user	0m0.018s
    sys	0m0.040s
    [root@llmvm02 remote]# time ./manually aakash-test log 20
    
    real	4m23.043s
    user	0m2.197s
    sys	0m14.457s
    [root@llmvm02 remote]# time ./offloaded aakash-test log 25;
    
    real	4m28.363s
    user	0m0.021s
    sys	0m0.025s
    [root@llmvm02 remote]# time ./manually aakash-test log 25
    
    real	5m34.278s
    user	0m2.957s
    sys	0m18.808s
    
    The argument log is a file which we want to set for logging purpose and
    the third argument is size in GB .
    
    As we can see there is a performance improvement of around 20% with this
    fop.
    
    Change-Id: I081159f5f7edde0ddb78169fb4c21c776ec91a18
    BUG: 1028673
    Signed-off-by: Aakash Lal Das <aakash@linux.vnet.ibm.com>
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/5327
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d5335f9e40f6e9533f7812d153b9727bcc04aa4e
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sat Nov 9 11:56:34 2013 +0000

    libglusterfs: fix bug in timespec adjustment
    
    The argument to the timespec_adjust_delta() function introudced in
    commit 6836118b21 needs to be passed by reference rather than by value
    for the function to do it's job.
    
    BUG: 1028663
    Change-Id: I62a3636906e67ed35b7786e9553f6819b48f3626
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/6243
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c80794079a246f4fee730d028350e80c38dbf034
Author: Anand Avati <avati@redhat.com>
Date:   Mon Oct 21 20:29:07 2013 -0700

    gfapi: remove unnecessary call to glfs_resolve_base()
    
    Calling glfs_resolve_base() on the root inode for every resolver
    invocation is unnecessary and wasteful.
    
    Here are the results from running a test program which performs
    path based operations (creates and deletes 1000 files):
    
    Without patch:
    [root@blackbox ~]# sync
    [root@blackbox ~]# time ./a.out 1
    
    real    0m4.314s
    user    0m1.923s
    sys     0m1.144s
    [root@blackbox ~]# sync
    [root@blackbox ~]# time ./a.out 1
    
    real    0m4.383s
    user    0m1.940s
    sys     0m1.177s
    [root@blackbox ~]# sync
    [root@blackbox ~]# time ./a.out 1
    
    real    0m4.339s
    user    0m1.863s
    sys     0m1.129s
    
    With patch:
    
    [root@blackbox ~]# sync
    [root@blackbox ~]# time ./a.out 1
    
    real    0m3.005s
    user    0m1.162s
    sys     0m0.816s
    [root@blackbox ~]# sync
    [root@blackbox ~]# time ./a.out 1
    
    real    0m3.188s
    user    0m1.222s
    sys     0m0.867s
    [root@blackbox ~]# sync
    [root@blackbox ~]# time ./a.out 1
    
    real    0m2.999s
    user    0m1.131s
    sys     0m0.832s
    
    Change-Id: Id160a24f44b4dccfcfce99a6f69ddb8938523cd5
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6131
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 11e28d3aedabac01b5cfc219745681426b5cf416
Author: Ravishankar N ravishankar@redhat.com <ravishankar@redhat.com>
Date:   Wed Nov 6 18:40:25 2013 +0530

    glusterd: modify remove-brick CLI message.
    
    In the current context "replica_cnt" is used just to know whether the
    specific key exists or not by calling "dict_get_int32", which we can
    replace by "dict_get ()". And changing the log message as it is more
    appropriate to say "migration of data" rather than "rebalance".
    
    This patch refactors commit 51c6fa7a354826744de98 against BZ 961669
    
    reviewed on : http://review.gluster.org/5566
    
    Change-Id: I48eae206a28d4083975e64407ed8fe4539f9c24b
    BUG: 1027270
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Original patch: Susant Palai <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/6001
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: susant palai <spalai@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9ebe1ede1f7bcf9a7cbc42314053ddf28c45b864
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Nov 6 17:25:22 2013 +0530

    posix: Fix excessive logging resulting from get_real_filename failure from samba
    
    Change-Id: I641d028165da7b8501bd372c62d2df89a9d4db1f
    BUG: 1027174
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6237
    Reviewed-by: poornima g <pgurusid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0b2487d3bc8bc526d9b08698ea1434e94a6420d5
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri Sep 20 16:58:47 2013 +0530

    gNFS: NFS segfaults with nfstest_posix tool
    
    Problem:
    nfs3_stat_to_fattr3() missed a NULL check.
    
    FIX:
    (1) Added a NULL check.
    (2) In all fop cbk path, if the op_ret is -1 and op_errno is 0,
        then handle it as a special case. Set the NFS3 status as
        NFS3ERR_SERVERFAULT instead of NFS3_OK.
    (3) The other component of FIX would be in DHT module and
        is on the way.
    
    Change-Id: I6f03c9a02d794f8b807574f2755094dab1b90c92
    BUG: 1010241
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6026
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3108d4529d57690f58027da61ac5e56a0987ed57
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 21 14:11:38 2013 -0400

    client_t: phase 2, refactor server_ctx and locks_ctx out
    
    remove server_ctx and locks_ctx from client_ctx directly and store as
    into discrete entities in the scratch_ctx
    
    hooking up dump will be in phase 3
    
    BUG: 849630
    Change-Id: I94cea328326db236cdfdf306cb381e4d58f58d4c
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5678
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c47408e896c9bcaf21e7f8956bdae85633f873e0
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Oct 31 08:18:56 2013 -0400

    mgmt/glusterd: add option to specify a different base-port
    
    This is (arguably) a hack to work around a bug in libvirt which is not
    well behaved wrt to using TCP ports in the unreserved space between
    49152-65535. (See RFC 6335)
    
    Normally glusterd starts and binds to the first available port in range,
    usually 49152. libvirt's live migration also tries to use ports in this
    range, but has no fallback to use (an)other port(s) when the one it wants
    is already in use.
    
    Change-Id: Id8fe35c08b6ce4f268d46804bbb6dddab7a6b7bb
    BUG: 1018178
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6210
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 301ecf4798ae5271b2155efee92e5d1ad734b05b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 30 11:57:01 2013 +0530

    features/gfid-access: Handle inode remap when parent inode is NULL
    
    Change-Id: Ic3f9d30d75df0bbbdf8fe28446fabe62d90fa854
    BUG: 1024666
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6194
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5e96e7d4a976975d8eac0bbf8d0d7ea663665bce
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Oct 22 20:18:28 2013 +0530

    glusterd: Release big-lock after log-rotate handler returns
    
    ... so that subsequent volume commands don't block waiting forever,
    for the lock to be released.
    
    Change-Id: I24b5ec47f6982900ab74ff1b492d523f31ecfb7f
    BUG: 1022055
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6122
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc86b3a22ab0519652f74ef8a75cf1cbfa290fb8
Author: Anuradha <atalur@redhat.com>
Date:   Thu Oct 24 15:03:48 2013 +0530

    glusterd : Improved quota volume reset command
    
    Quota volume reset command without "force"
    option fixed, doesn't fail anymore. It resets
    unprotected fields and not the protected ones.
    
    Also, an appropriate message is provided to the user
    for the following cases :
    1. only unprotected fields are reset, "force" option
    should be used to reset protected fields.
    2. Both protected and unprotected fields are reset.
    3. No field was reset, "force" option required.
    
    Test case for the same also added.
    
    Change-Id: I24e8f1be87b79ccd81bf6f933e00608b861c7a16
    BUG: 1022905
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6135
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a4056292528db49a666422c7f8e0c032441cc83f
Author: Anand Avati <avati@redhat.com>
Date:   Sun Oct 20 08:45:18 2013 -0700

    rpcsvc: implement per-client RPC throttling
    
    Implement a limit on the total number of outstanding RPC requests
    from a given cient. Once the limit is reached the client socket
    is removed from POLL-IN event polling.
    
    Change-Id: I8071b8c89b78d02e830e6af5a540308199d6bdcd
    BUG: 1008301
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6114
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0162933589d025ca1812e159368d107cfc355e8e
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Thu Oct 17 16:17:54 2013 +0530

    gNFS: Make NFS I/O size to 1MB by default
    
    For better NFS performance, make the default I/O size to 1MB, same as
    kernel NFS. Also refactor the description for read-size, write-size
    and readdir-size (i.e. it must be a multiple of 1KB but min value
    is 4KB and max supported value is 1MB). On slower network, rsize/wsize
    can be adjusted to 16/32/64-KB through nfs.read-size or nfs.write-size
    respectively.
    
    Change-Id: I142cff1c3644bb9f93188e4e890478177c9465e3
    BUG: 1009223
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6103
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f42a76492463e33c56868e3569932776b14d08e8
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Fri Oct 25 13:54:34 2013 -0400

    libgfapi: fixing tabs in glfsxmp.c with whitespace
    
    Just replacing tabs with whitespace. No code changes present
    in this patch
    
    Change-Id: Ic3f64f5a52b0ab5e5c9fe9f45113901dec751e68
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6148
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ef4bb42382a5c9c3ca0907136669a659c2a20311
Author: Ajeet Jha <ajha@redhat.com>
Date:   Thu Oct 17 13:14:02 2013 +0530

    geo-rep: Increasing the buffer_size for master-salve size comparision.
    
    The buffer size is increased to 100MB, considering the space required by slave
    filesystem bookkeeping.
    
    Change-Id: Ib296f0e03b4d7a2de6d5ff0ae9ab09a5261e3e7c
    BUG: 1020154
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/6102
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 93c49c6e8c443426792b8e6cf24805516fdcc9bd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Oct 23 13:39:18 2013 +0000

    gfapi: fix mem-types initialisation
    
    ... and also fill the body of mem_acct_init().
    
    Change-Id: I457d0629c20f999dd2f50e710c75b1c7575b6c19
    BUG: 1021904
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6134
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3033d9c7b4e981a39df76ba066b98f659a1f5045
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 23 10:12:08 2013 -0400

    dual license: update remaining files with correct license text
    
    Sayan Saha has previously approved changing everthing to dual license
    but somehow we have missed changing these files.
    
    I am explicitly not updating the copyright dates as nothing else that's
    copyrightable has changed in these files with the license change
    
    Change-Id: Ia965eeb7168447d69e28e939ad95ee388873b6e4
    BUG: 951549
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6128
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f063951d75b98406b23a7a12828b2a58a5f446bf
Author: Poornima <pgurusid@redhat.com>
Date:   Fri Oct 18 04:51:21 2013 +0000

    extras/hook-scripts: Enable per client logging for gluster shares served by SAMBA
    
    Edited hook scrips to add a variable in the option 'log file', which will be
    substituted for client IP.
    
    Change-Id: I50f143bb3114eb00afab2e1237d749804c885ca6
    BUG: 1020848
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6109
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7ebcf96c94c1292dcc7155c74b49257a9952b8d4
Author: Anand Avati <avati@redhat.com>
Date:   Sun Oct 13 23:15:48 2013 -0700

    gfapi: wake migration waiters after migration
    
    Wake call threads which are waiting on migration to complete with
    a cond_broadcast. Else if any call which arrives right when migration
    is attempted will end up hanging indefinitely.
    
    Change-Id: I7df5298f93998d9a54fb12c16654e62333018ece
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/6111
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>

commit e6bf83dbf781877d185057b3339ed81d7ec150e6
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Mon Oct 21 21:36:13 2013 +0530

    Rectify the guard macro name of glusterfs-acl.h
    
    Change-Id: I13bc7626c7f852647a75e3d5e397d2cd55757932
    BUG: 1009210
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/6117
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 34990cf1838fe85d995c15ea25bc0f77bfd66ed6
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sun Oct 20 21:45:45 2013 -0700

    libglusterfs: Propositions should be logical
    
    Mutually exclusive tests shouldn't be
    non-contradictory
     -- (A is B) && (A is not B) is not valid
    
    Change-Id: Icf97d1704fedca4b8eeeb67da8b7d4c8d4b578d5
    BUG: 769692
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6115
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9228618f9d566d1af29b6a4946426df09b7737bc
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Oct 18 11:06:59 2013 +0530

    build: disable logging framework on rhel6
    
    As rsyslog-mmcount is not yet available in rhel6 variant, this patch
    disables logging framework on rhel6 and its dependency
    
    BUG: 1018308
    Change-Id: I6b7c04640f8d38055e00c697d1017c7a530463d0
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/6108
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b2a9cbe5ce61ce170a55fb3dfd7f2d6de9c52f97
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Aug 31 22:34:02 2013 +0530

    mgmt/glusterd: Relax extended attribute checks for volume create and add brick force.
    
    Expectation with force is that user is aware of the consequences of
    sanity checks not being triggered.
    
    Change-Id: I79dfeed16a23829a7217cef33ab83f9f0ffae336
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    BUG: 1007509
    Reviewed-on: http://review.gluster.org/5746
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9d9ed58b3be5f3513b20146984c4bbacbc8d8750
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Oct 16 00:34:44 2013 +0530

    rpc: add remote peer's hostname to call_bail log msgs
    
    Change-Id: I982cf7619463983c04b401d70a76635991d072d2
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6091
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit 05d8c37c1e1b0554985196d507df3a65c764873b
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Oct 16 21:24:32 2013 -0700

    libglusterfs: Return 'ERANGE' for ASCII string to number system
    
    Using 'EOVERFLOW' should be limited to data structure
    alignments not Number systems.
    
    Change-Id: I7d337d414e998c0a729c95661df239e36c753a38
    BUG: 1017746
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6101
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9a31a25cfa3d8a4355412e2fff93482bb7352a52
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Oct 17 14:03:21 2013 -0400

    glusterfs.spec.in: bad %define _sharedstatedir for rhel5
    
    Change-Id: If2ca7052dfce9fada42180f1d469316fcde5adcb
    BUG: 1003184
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6105
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Justin Clift <jclift@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dfa08fe05843b5da077ddbe059d744ce3864044e
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Oct 16 00:56:01 2013 +0530

    gfapi: fix return value of glfs_fini
    
    Change-Id: I5b90c7602334226a978bbdae2f9516e8701b403f
    BUG: 1004519
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/6092
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc637b14cfad4d08e72bee7064194c8007a388d0
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jul 3 16:31:22 2013 +0530

    cli,glusterd: Changes to cli-glusterd communication
    
    Glusterd changes:
    With this patch, glusterd creates a socket file in
    DATADIR/run/glusterd.socket , and listen on it for cli requests. It
    listens for 2 rpc programs on the socket file,
    - The glusterd cli rpc program, for all cli commands
    - A reduced glusterd handshake program, just for the 'system:: getspec'
      command
    
    The location of the socket file can be changed with the glusterd option
    'glusterd-sockfile'.
    
    To retain compatibility with the '--remote-host' cli option, glusterd
    also listens for the cli requests on port 24007. But, for the sake of
    security, it listens using a reduced cli rpc program on the port. The
    reduced rpc program only contains read-only procs used for 'volume
    (info|list|status)', 'peer status' and 'system:: getwd' cli commands.
    
    CLI changes:
    The gluster cli now uses the glusterd socket file for communicating with
    glusterd by default. A new option '--gluster-sock' has been added to
    allow specifying the sockfile used to connect. Using the '--remote-host'
    option will make cli connect to the given host & port.
    
    Tests changes:
    cluster.rc has been modified to make use of socket files and use
    different log files for each glusterd.
    Some of the tests using cluster.rc have been fixed.
    
    Change-Id: Iaf24bc22f42f8014a5fa300ce37c7fc9b1b92b53
    BUG: 980754
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5280
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 390221fcc4cc974074750be223e551bd9f4405d9
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Fri Oct 11 17:29:10 2013 +0530

    posix: Fix readv FOP
    
    Suggested by Anand Avati in BD xlator code review.
    
    Change-Id: I31c353a26dfdeb3d0023c3f7e03ed25461d13c16
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    BUG: 837495
    Reviewed-on: http://review.gluster.org/6077
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 5033d450ca039b77b9245006e1de7c950754dbb1
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 16 15:58:33 2013 +0530

    cluster/afr: Remove 'max' from the log
    
    This patch avoids giving more info to the user about the
    internal heuristic employed in afr, for quota sizes.
    
    Change-Id: Ice3a164399f09b6967500ec0c17dc340e7ae9aba
    BUG: 1016683
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6098
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit dfe698bae7f4bbc5f506d29473888239a82156fc
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Tue Oct 15 22:37:44 2013 +0530

    afr: check for split-brain before proceeding with fops
    
    Bail out of fops if split brain has been detected during lookup
    
    Change-Id: Id387dbb1a25eec4a121dedceadc6069bdea24b5d
    BUG: 1010834
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5988
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 656db3a8e0601ba0a6af303b971111fbbed29906
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Sun Oct 13 15:08:10 2013 -0400

    libgfapi: Fix to compilation failure/warnings for examples/glfsxmp.c
    
    The comilation of glfsxmp.c i.e. "make glfsxmp" was failing
    with "undefined reference to `clock_gettime'" error.
    
    Fixed all compilation warnings for unused variables and
    wrong formart specifier in printf e.g. : "format ‘%d’ expects
    argument of type ‘int’, but argument 3 has type ‘__syscall_slong_t’
    [-Wformat]"
    
    Also added the compilation steps for glfsxmp.c in the
    README file
    
    Change-Id: I399ec7c9ad7b6412463c89099d63922caef6749e
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/6085
    Reviewed-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Shyamsundar Ranganathan <srangana@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0c129ad25c007d574e9c7e45f47e6ba7075f4bfa
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Oct 14 11:50:40 2013 +0530

    storage/posix: Lower log severity for ENODATA errors in getxattr()
    
    Change-Id: I101e329cce4c1305615c63ebcb42355f6c3e85e0
    BUG: 918052
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/6084
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1cf925670768383044588fa162d65be8545224ce
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Oct 11 12:46:06 2013 +0530

    dht: dht_lookup_dir_cbk should set op_errno as local->op_errno
    
    Two glusterfs clients return inconsistent errnos when the bricks of the volume
    were down. Consider two gluster mounts. Mount 1 was done when the bricks were
    online. Mount 2 was done after the bricks were killed, (using the 'glusterfs'
    command instead of the mount script).
    
    For any request, mount 1 will return ENOTCONN, where as mount 2 will return
    ENOENT.
    
    This happens because for the 2nd mount, a fuse would send a lookup on '/' for
    any request, as it hadn't been done yet. The client xlator returns ENOTCONN,
    but the dht_lookup_dir_cbk changed this to ENOENT unconditionally when
    aggregating. So, fuse returned ENOENT, even though the errno should have been
    ENOTCONN.
    
    Change-Id: I4b7a6d84ce5153045a807fccc01485afe0377117
    BUG: 1019095
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6072
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 6836118b214bb45ff94ae1bc176a6eefb1a17a6a
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Oct 10 04:19:16 2013 -0700

    libglusterfs: Add monotonic clocking counter for timer thread
    
    gettimeofday() returns the current wall clock time and timezone.
    Using these functions in order to measure the passage of time
    (how long an operation took) therefore seems like a no-brainer.
    
    This time suffer's from some limitations:
    
    a. They have a low resolution: “High-performance” timing by
    definition, requires clock resolutions into the microseconds
    or better.
    
    b. They can jump forwards and backwards in time: Computer
    clocks all tick at slightly different rates, which causes
    the time to drift. Most systems have NTP enabled which
    periodically adjusts the system clock to keep them in sync
    with “actual” time. The adjustment can cause the clock to
    suddenly jump forward (artificially inflating your timing
    numbers) or jump backwards (causing your timing calculations
    to go negative or hugely positive). In such cases timer
    thread could go into an infinite loop.
    
    From 'man gettimeofday':
    ----------
    ..
    ..
    The time returned by gettimeofday() is affected by discontinuous
    jumps in the system time (e.g., if the system administrator manually
    changes the system time).  If you need a monotonically increasing
    clock, see clock_gettime(2).
    ..
    ..
    ----------
    
    Rationale:
    
    For calculating interval timing for Timer thread, all that’s
    needed should be clock as a simple counter that increments
    at a stable rate.
    
    This is necessary to avoid the jumps which are caused by using
    "wall time", this counter must be monotonic that can never
    “tick” backwards, ever.
    
    Change-Id: I701d31e71a85a73d21a6c5cd15583e7a5a645eeb
    BUG: 1017993
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6070
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 793f8491789e58791b090a74472959df117e404b
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Oct 10 17:20:57 2013 +0530

    libglusterfs: Account for overflow in gf_string2bytesize
    
    gf_string2bytesize will now return an error when a value is greater than
    UINT64_MAX and set errno to EOVERFLOW. This is needed because casting a
    double value greater than UINT64_MAX to uint64_t will convert it to 0.
    
    BUG: 1017746
    Change-Id: I6f96efc1e3a1c236685593a6fb7f806a87e46019
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6068
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 75caba63714c7f7f9ab810937dae69a1a28ece53
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Oct 7 13:47:47 2013 +0530

    cluster/afr: [Feature] Command implementation to get heal-count
    
    Currently to know the number of files to be healed, either user
    has to go to backend and check the number of entries present in
    indices/xattrop directory. But if a volume consists of large
    number of bricks, going to each backend and counting the number
    of entries is a time-taking task. Otherwise user can give
    gluster volume heal vol-name info command but with this
    approach if no. of entries are very hugh in the indices/
    xattrop directory, it will comsume time.
    
    So as a feature, new command is implemented.
    
    Command 1: gluster volume heal vn statistics heal-count
    This command will get the number of entries present in
    every brick of a volume. The output displays only entries
    count.
    
    Command 2: gluster volume heal vn statistics heal-count
               replica 192.168.122.1:/home/user/brickname
    
               Here if we are concerned with just one replica.
    So providing any one of the brick of a replica will get
    the number of entries to be healed for that replica only.
    
    Example:
    Replicate volume with replica count 2.
    
    Backend status:
    --------------
    [root@dhcp-0-17 xattrop]# ls -lia | wc -l
    1918
    
    NOTE: Out of 1918, 2 entries are <xattrop-gfid> dummy
    entries so actual no. of entries to be healed are
    1916.
    
    [root@dhcp-0-17 xattrop]# pwd
    /home/user/2ty/.glusterfs/indices/xattrop
    
    Command output:
    --------------
    Gathering count of entries to be healed on volume volume3 has been successful
    
    Brick 192.168.122.1:/home/user/22iu
    Status: Brick is Not connected
    Entries count is not available
    
    Brick 192.168.122.1:/home/user/2ty
    Number of entries: 1916
    
    Change-Id: I72452f3de50502dc898076ec74d434d9e77fd290
    BUG: 1015990
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/6044
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 047882750e0e97f5eed21ebe3445cdb216b15a9d
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Sep 12 12:37:37 2013 +0530

    cluster/afr : Implementation of command "gluster volume heal vn statistics"
    
    "gluster volume heal volumename statistics" command gives the summary
    of the afr crawl done based on the entries present in the xattrop
    directory. Whenever afr crawls are attempted, the beginning time of
    crawl, end time of crawl, no of files healed, heal-failed count and
    number of files in split brain are shown along with the type of the
    crawl. If crawl is already in progress then it will give the number
    of files healed, heal failed count and number of files in split-brain
    from the beginning of the crawl and instead of telling the end time of
    the crawl, "CRAWL IN PROGRESS" message will be shown.
    
    Output format:
    command: "gluster volume heal volume-name statistics"
    Output:
    Gathering afr crawl statistics crawl statistics on volume volume-name
    has been successful
    ------------------------------------------------
    
    Crawl statistics for brick no 0
    Hostname of brick 192.168.122.248
    
    Starting time of crawl: Wed Jul 10 15:52:38 2013
    
    Ending time of crawl: Wed Jul 10 15:52:38 2013
    
    Type of crawl: INDEX
    No. of entries healed: 0
    No. of entries in split-brain: 0
    No. of heal failed entries: 0
    
    Starting time of crawl: Wed Jul 10 15:52:38 2013
    
    Ending time of crawl: Wed Jul 10 15:52:38 2013
    
    Type of crawl: INDEX
    No. of entries healed: 0
    No. of entries in split-brain: 0
    No. of heal failed entries: 0
    
    ------------------------------------------------
    
    Crawl statistics for brick no 1
    Hostname of brick 192.168.122.1
    
    Starting time of crawl: Wed Jul 10 15:52:42 2013
    
    Ending time of crawl: Wed Jul 10 15:52:42 2013
    
    Type of crawl: INDEX
    No. of entries healed: 0
    No. of entries in split-brain: 0
    No. of heal failed entries: 0
    
    Starting time of crawl: Wed Jul 10 15:52:42 2013
    
    Ending time of crawl: Wed Jul 10 15:52:42 2013
    
    Type of crawl: INDEX
    No. of entries healed: 0
    No. of entries in split-brain: 0
    No. of heal failed entries: 0
    
    --------------------------------------------------
    
    Change-Id: I10bf9d10b005741db9973fb1352e0dd59ed99aa9
    BUG: 949400
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4790
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9da2cb37834db98596dae8f7fb6d8f6abb513687
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Sep 17 11:44:34 2013 +0530

    transport/socket: don't try to set TCP_DELAY on unix domain sockets
    
    Change-Id: I290cd983bd0dff2e32e5ee90a12e888a3b31c6fd
    BUG: 969461
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/5954
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 46302d0f008c312f13cf780290cbb3e6a0a83b9d
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Oct 8 21:30:21 2013 -0700

    glusterfs.spec: Add _sharedstatedir for RHEL5
    
    -------------------------------------------------
    > # rpm --showrc | grep sharedstatedir | grep com
    -14: _sharedstatedir %{_prefix}/com
    > # cat /etc/redhat-release
    Red Hat Enterprise Linux Server release 5.8 (Tikanga)
    -------------------------------------------------
    
    EL5 package has a missing macro _sharedstatedir which
    should be pointing to `/var/lib` not `%{_prefix}/com`
    
    Change-Id: Ida72360d73d5dffa767c69642ee395e9c82fa8c6
    BUG: 1003184
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6054
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6d28941b0b32ae0053604021925dfdc8d40a1047
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Oct 9 08:29:18 2013 -0400

    build: sync glusterfs.spec.in with Fedora glusterfs.spec
    
    (this is the master branch)
    
    sync with Fedora glusterfs.spec 3.4.1-2+
    
    Change-Id: I8a303efb0ac8cd3e04531e2f02427e3590387493
    BUG: 950083
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6059
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d573f170cf3305c066f8b191f872d2d2f22f2025
Author: R.Shyamsundar <srangana@redhat.com>
Date:   Mon Sep 16 16:39:24 2013 +0530

    gfapi: object handle based API extensions
    
    There is an ongoing effort to integrate NFS Ganesha (
    https://github.com/nfs-ganesha/nfs-ganesha/wiki ) with GlusterFS as one of
    the file system back ends.
    
    Towards this we need extensions to gfapi that can handle object based
    operations. Meaning, instead of using full paths or relative paths from
    cwd, it is required that we can work with APIs, like the *at POSIX
    variants, to be able to create, lookup, open etc. files and directories.
    Hence the objects are the files or directories themselves and we give out
    handles to these objects that can be used for further operations.
    
    This code drop is an initial implementation of the proposed APIs.
    
    The new APIs are implemented as glfs_h_XXX variants in the file
    glfs-handleops.c to mirror glfs-fops.c style. The code leverages holding
    onto inode references and doling these out as opaque/cookie type objects to
    the callers, to enable them to be used as handles in other operations.
    
    An fd based approach was considered, but due to the extra footprint that
    the fd structure and its counterparts would incur, this was dropped to take
    the approach of holding inode references themselves.
    
    Tested by extending glfsxmp.c to invoke and exercise the added APIs, and
    further tested with a reference integration of the same as an FSAL with NFS
    Ganesha.
    
    Change-Id: I23629c99e905b54070fa2e6565147812e5f3fa5d
    BUG: 1016000
    Signed-off-by: R.Shyamsundar <srangana@redhat.com>
    Reviewed-on: http://review.gluster.org/5936
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d3558ae5c4b1cf6909e27e8fabd6ec44fe6aa971
Author: Poornima <pgurusid@redhat.com>
Date:   Fri Oct 11 04:06:56 2013 +0000

    gfapi: Fix iobuf leaks in gfapi
    
    In glfs_readv, if syncop_readv() fails with return value <= 0
    the iobref was not being unrefd which would cause iobuf leaks.
    
    Change-Id: I9850ae149e53cf75ba26f8b5f4c5446cce4b5991
    BUG: 1018176
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/6074
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 86f936f4381a8d8490255ef439ec3c44ca79fe76
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Oct 8 17:14:40 2013 +0530

    cluster/afr: Handle quota size xattr separately in lookup
    
    Quota size xattrs are not maintained by afr. There is a
    possibility that they differ even when both the directory
    changelog xattrs suggest everything is fine. So if there is at
    least one 'source' check among the sources which has the maximum
    quota size. Otherwise check among all the available ones for
    maximum quota size. This way if there is a source and stale copies
    it always votes for the 'source'.
    
    Change-Id: Ia222379cbafa7043dd03f533c105860f2c7b8b0d
    BUG: 1016683
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6052
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c436b89a7111bbaaed9f034799986ea7c760ce55
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Oct 9 11:13:11 2013 +0200

    rpm: glusterfs-api-devel requires glusterfs-devel
    
    When installing the glusterfs-api-devel package in order to build
    software that uses libgfapi, there are unmet dependencies. Installing
    glusterfs-devel additionally solved these link errors:
    
      $ echo 'int main(){}' > bar.c
      $ gcc -o bar bar.c $(pkg-config --libs glusterfs-api)
      /usr/bin/ld: cannot find -lglusterfs
      /usr/bin/ld: cannot find -lgfrpc
      /usr/bin/ld: cannot find -lgfxdr
      collect2: error: ld returned 1 exit status
    
    Change-Id: I12e922aa6609809c03ec2c9a0d8a47c5df91d0a1
    BUG: 1017094
    Reported-by: Eric Blake <eblake@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6056
    Reviewed-by: Bala FA <barumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cecc5b8fc05f071e9556c84153634b6d50c77dbb
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Oct 2 07:16:02 2013 -0400

    contrib/qemu: disable coroutine caching in qemu
    
    Coroutine caching in qemu is dangerous in the manner that the
    qemu-block translator embeds the qemu block subsystem code. After
    a graph switch, new requests can fork off and pass active graph
    data structures (i.e., inodes) down into old syncenvs and old
    graphs, leading to failures.
    
    BUG: 986775
    Change-Id: I7b7226ff57c7867d0e51a58a7c0e58f4d8424c31
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/6022
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 19ae2464c0800965c18c35132b0b6c7fe09d5f68
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Oct 2 07:15:44 2013 -0400

    features/qemu-block: invoke bdrv_init() only once
    
    bdrv_init() is intended to be invoked only once. If invoked again
    after initialization (i.e., due to graph changes), the block driver
    registration code can reinsert entries into bdrv_drivers,
    effectively corrupting the NULL terminated linked list. This
    manifests as an infinite loop for callers attempt to traverse the
    list (to locate a driver).
    
    BUG: 986775
    Change-Id: I2f95bda3c753dece4648cdad009d0e2a2d16f644
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/6021
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ce9a704361c0a3638e46911eb5275c02e6a5d9ab
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Oct 9 12:08:49 2013 +0200

    tests/basic/rpm.t: fix script error introduced by commit a66bf679
    
    The if-clause will always return false, causing each regression test to
    build the rpms. The following error is listed on the Jenkins Console
    Output of the regression test:
    
        ./tests/basic/rpm.t: line 42: [: argument expected
    
    BUG: 904005
    Change-Id: I343c80d8c57fa0ec8b8a531bb5f5c86209d88d7e
    CC: Harshavardhana <harsha@harshavardhana.net>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/6057
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>

commit e51ca3c1c991416895e1e8693f7c3e6332d57464
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 24 17:01:46 2013 +0530

    cli,glusterd: Implement 'volume status tasks'
    
    oVirt's Gluster Integration needs an inexpensive command that can be
    executed every 10 seconds to monitor async tasks and their parameters,
    for all volumes.
    
    The solution involves adding a 'tasks' sub-command to 'volume status'
    to fetch only the async task IDs, type and other relevant parameters.
    Only the originator glusterd participates in this command as all the
    information needed is available on all the nodes. This is to make the
    command suitable for being executed every 10 seconds.
    
    Change-Id: I1edc607baf29b001a5585079dec681d7c641b3d1
    BUG: 1012346
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/6006
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 11bb1fc5849a557d1a26e59bd651fbd0d07a1b8d
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Oct 7 13:08:49 2013 +0530

    extras/hookscripts: Fix the multiple entries in smb.conf problem.
    
    Problem:
    1. Force starts and user.smb sets were adding multiple entries to
    the smb.conf file for the same volume.
    Make a check for the entry and search with exact name.
    
    2. Again, while deleting the share name from smb.conf search with
    exact name so that volumes with names which are substrings of ones to
    be deleted don't get deleted.
    
    3. We don't need to use a tmp file while using sed -i, fixed that.
    
    Change-Id: Ie0f7c9d4790ef9a177a043378a761c9ffe1628e5
    BUG: 994727
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6043
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Tested-by: Lalatendu Mohanty <lmohanty@redhat.com>

commit 1f6b0f5cfc5abebe3a8facfb8b72e5554c1314d2
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Thu Oct 3 15:08:34 2013 +0530

    NFS: showmount timesout on fetching export list
    
    Bug: 1015184
    
    Issue:  showmount timesout on fetching export list. Socket writev
            function is failing.
    Cause:  XDR encoding of export list is failing. The calling function
            without checking the error returned by xdr_serialize_exports
            function is going ahead and writting into the socket causing
            the NFS process to hang. xdr_serialize_exports function returns
            -1 on error and message length on success.
    Fix:    Caller should check if the function is returning -1 (error) or
            not before proceeding.
    
    Change-Id: Ic3a5a9356e47b2ac938dd3e429cf2b71c0a0c715
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/6030
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 31cacce7702d1f08270c0b2f84ea0fdfcae6b3e0
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Mon Sep 16 14:56:50 2013 -0400

    hookscripts: Changes in hook scripts to make it work on all Linux/GNU distribution
    Removed the hard coded values for smb.conf, smb logfile location and smbd.pid.
    The current hook scripts also work for manully compiled (make, make install)
    instance of gluster and Samba. But we have to manually copy the hook scripts
    to respective locations.
    
    Change-Id: I14056830fcd2ecb48b3c4df89265f4408c8de3e3
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/5947
    Reviewed-by: poornima g <pgurusid@redhat.com>
    Reviewed-by: susant palai <spalai@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8c1f5cffea19c2119be7c55c79325a5d6324faa2
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Oct 4 10:17:09 2013 +0200

    Fix build on NetBSD-current
    
    BUG: 764655
    Change-Id: I2aaec9de617b0616525ad30f82ac6f75a6446d33
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/6036
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d9db4a8ff300012eee87f31d73e303862d2de9b6
Author: Bala.FA <barumuga@redhat.com>
Date:   Thu Sep 26 08:09:35 2013 +0530

    cli: add node uuid in rebalance and remove brick status xml output
    
    This patch adds node uuid in rebalance/remove-brick status xml output.
    Output XML will look like
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volRebalance>
        <op>3</op>
        <nodeCount>1</nodeCount>
        <node>
          <nodeName>localhost</nodeName>
     ==>> <id>883626f8-4d29-4d02-8c5d-c9f48c5b2445</id>
          <files>0</files>
          <size>0</size>
          <lookups>0</lookups>
          <failures>0</failures>
          <status>3</status>
          <statusStr>completed</statusStr>
        </node>
        <aggregate>
          <files>0</files>
          <size>0</size>
          <lookups>0</lookups>
          <failures>0</failures>
          <status>3</status>
          <statusStr>completed</statusStr>
        </aggregate>
      </volRebalance>
    </cliOutput>
    
    Change-Id: I5a1d4f9043b33b9e88150647a243ddb16154e843
    BUG: 1012296
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/6005
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dcfe4ab475c53cec7d117fb8052b26213a4b41db
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jul 25 01:14:48 2013 +0530

    glusterfsd, libgfapi: destroy the temporary graphs constructed for comparison
    
    * The new and the oldgraphs which have been constructed whenever there is
      a volfile change (either reconfigure of the existing graph or creating
      a new graph) for comparison should be freed. Otherwise frequent graph
      changes will lead to huge memory leak
    
    Change-Id: I4faddb1aa9393b34cd2de6732e537a60f600026a
    BUG: 948178
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/5388
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a25bd2d7695760c9fe35fec39065c9326f2952d6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Oct 3 11:52:53 2013 +0530

    Tests: Enable fore-ground self-heal
    
    Change-Id: Ibfca8ddb7c663d44ed447be13b2eabb7bd393bb3
    BUG: 993981
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6028
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c32db94e29f1c20d7eede05c7c6ad7657771aaa4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Oct 3 10:28:47 2013 +0530

    cluster/afr: Change Self-heal domain separator to ':'
    
    '-' can be present in a volume. This may lead to domain
    collisions in future.
    
    Tests:
    Checked in gdb that domain comes with ':' separator:
    
    Breakpoint 1, pl_common_inodelk (frame=0x7fdabcce51a4,
    this=0x8bde20, volume=0x8b50d0 "r2-replicate-0:self-heal",
    inode=0x7fdab822f0e8, cmd=6, flock=0x7fdabc76eee4,
    loc=0x7fdabc76ede4, fd=0x0, xdata=0x7fdabc6e0ab0) at inodelk.c:597
    
    Change-Id: I4456ae35ac8bf21e6361c34e9ad437f744a2e84b
    BUG: 993981
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/6025
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 79ba7b3e2ea6e2dc2e720c2cae1e6ae0aeeea392
Author: Aravinda VK <avishwan@redhat.com>
Date:   Thu Sep 19 14:24:35 2013 +0530

    geo-rep: logrotate: Logrotate handling
    
    In existing georep logrotate was implemented by handling SIGSTOP
    and SIGCONT, gsyncd was failing to start again after SIGSTOP.
    New approach uses WatchedFileHandler in logging, which tracks the
    log file changes or logrotate. Reopens the log file if logrotate is
    triggered or if same log file is updated from other process.
    
    As per python doc:
    http://docs.python.org/2/library/logging.handlers.html:
    The WatchedFileHandler class, located in the logging.handlers module,
    is a FileHandler which watches the file it is logging to. If the file
    changes, it is closed and reopened using the file name.
    
    A file change can happen because of usage of programs such as newsyslog
    and logrotate which perform log file rotation. This handler, intended
    for use under Unix/Linux, watches the file to see if it has changed
    since the last emit. (A file is deemed to have changed if its device
    or inode have changed.) If the file has changed, the old file stream
    is closed, and the file opened to get a new stream.
    
    Change-Id: I30f65eb1e9778b12943d6e43b60a50344a7885c6
    BUG: 1012776
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/5968
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a65d64e89c96b52b9805b63afbbc3e7b67dbc3ad
Author: Ajeet Jha <ajha@redhat.com>
Date:   Mon Sep 23 13:42:21 2013 +0530

    glusterd: Validating invalid log-level under geo-rep config options.
    
    Change-Id: I8ff6b48ef41fd6e9ea68c42dfb9878f8a08ed627
    BUG: 1010874
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/5989
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 7dba6f9b556288a95d6ca7e9c3222d14cae3def5
Author: Aravinda VK <avishwan@redhat.com>
Date:   Tue Sep 24 12:41:30 2013 +0530

    cli: runtime in xml output of rebalance/remove-brick status
    
    "runtime in secs" is available in the CLI output of
    rebalance status and remove-brick status, but not available
    in xml output when --xml is passed.
    
    runtime in aggregate section will be max of all nodes runtimes.
    
    Example output:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volRebalance>
        <op>3</op>
        <nodeCount>1</nodeCount>
        <node>
          <nodeName>localhost</nodeName>
          <files>0</files>
          <size>0</size>
          <lookups>0</lookups>
          <failures>0</failures>
          <skipped>0</skipped>
          <runtime>1.00</runtime>
          <status>3</status>
          <statusStr>completed</statusStr>
        </node>
        <aggregate>
          <files>0</files>
          <size>0</size>
          <lookups>0</lookups>
          <failures>0</failures>
          <skipped>0</skipped>
          <runtime>1.00</runtime>
          <status>3</status>
          <statusStr>completed</statusStr>
        </aggregate>
      </volRebalance>
    </cliOutput>
    
    BUG: 1012773
    Change-Id: I8deaba08922a53cd2d3b411e097a7b3cf591b127
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/5997
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 59b4e379e6d56af4828738c966b80c313415f632
Author: Aravinda VK <avishwan@redhat.com>
Date:   Wed Sep 25 12:04:11 2013 +0530

    cli: skipped tag in xml output of rebalance/remove-brick status
    
    Skipped files count is available in CLI output of rebalance status
    and remove-brick status, but not available in xml output.
    
    Example output:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <cliOutput>
      <opRet>0</opRet>
      <opErrno>0</opErrno>
      <opErrstr/>
      <volRebalance>
        <op>3</op>
        <nodeCount>1</nodeCount>
        <node>
          <nodeName>localhost</nodeName>
          <files>0</files>
          <size>0</size>
          <lookups>0</lookups>
          <failures>0</failures>
          <skipped>0</skipped>
          <status>0</status>
          <statusStr>completed</statusStr>
        </node>
        <aggregate>
          <files>0</files>
          <size>0</size>
          <lookups>0</lookups>
          <failures>0</failures>
          <skipped>0</skipped>
          <status>0</status>
          <statusStr>completed</statusStr>
        </aggregate>
      </volRebalance>
    </cliOutput>
    
    BUG: 1012772
    Change-Id: I05191293403e66e0d681f0cd0422aa3c78a2d91d
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/6000
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a5ef7bc7de744d1324ddf63207b1172d11086441
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Oct 1 14:51:46 2013 -0400

    protocol/server: eliminate an unnecessary frame create and destroy
    
    connection_cleanup creates a frame solely so that it can be copied.
    
    But the process of copying creates a new frame, and there's nothing
    apparently magic about the one being copied; we can eliminate an
    unnecessary create and destroy.
    
    Which in the grand scheme of things probably isn't the worst thing
    we do, but it's low hanging fruit.
    
    Change-Id: I4a23b84a53e086137b7d4167ad8c20b673d1ffe5
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/6019
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c499ef86a2dfd4e7727ce876b6cf18ba79c94fe5
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Sep 30 09:05:14 2013 +0200

    gfapi.py: support dynamic loading of versioned libraries
    
    Currently gfapi.py only loads libraries by filename ending in ".so".  On
    an installed system without development packages, the <lib>.so filenames
    are not available. ctypes.util.find_library() can be used to detect the
    files dynamically.
    
    In addition to this, also fixing some minor indention errors and package
    the library into the Python site-packages path. Python applications and
    libraries can now access libgfapi through 'from glusterfs import gfapi'.
    
    Change-Id: I71e38dabd3ade5dcf24813bf2fc25cda91b571c6
    BUG: 1005146
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5835
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a66bf67965dddd9decd9210c3a530fdc85b6430c
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Sep 30 16:10:32 2013 -0700

    tests: Gather only files which need to built
    
    Previous code would rather provide a filter but never look
    for newly "Added" files leading to failures in subsequent
    build.
    
    This patch fixes such issue by actually verifying pedantically
    for only files which need to be tested.
    
    Change-Id: Ia716acf82ee60f8ffe5e36257f1cc866c6062718
    BUG: 904005
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/6016
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dbe4566beff3239bbb23af50b1ef263b8b100e1b
Author: Anand Avati <avati@redhat.com>
Date:   Fri Sep 27 10:21:22 2013 -0700

    libglusterfs: add glusterfs-acl.h to Makefile.am
    
    Without this, glusterfs-acl.h is left out of 'make dist'
    and building RPM fails.
    
    Change-Id: I5dc9dc8eecdea4c4c0d06f0b3da23bd2df4e944e
    Signed-off-by: Anand Avati <avati@redhat.com>
    BUG: 1009210
    Reviewed-on: http://review.gluster.org/6015
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2526eea5dde0aa1af6ff43cf63f6e818798c8f2f
Author: Anuradha <atalur@redhat.com>
Date:   Fri Sep 27 17:42:17 2013 +0530

    Logging :  Improved the log message on unlock failure in afr_unlock_inodelk_cbk.
    
    "unlock failed on 1 unlock" seems meaningless in the log message. Improved it.
    
    Change-Id: If67d3f9d4aa5310d0b6728a6c89fa58a5cc93d12
    BUG: 1012947
    Signed-off-by: Anuradha <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/6012
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9b286d5937e7c78fd17185e9afe25e809153a265
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Aug 12 10:43:52 2013 +0530

    glusterd: Calculate volume op-versions only on set/reset
    
    The volume op-versions are calculated during a volume set/reset, reading a
    volume from disk and importing a volume during probe or volume sync. The
    calculation of the volume op-version depends on the clusters op-version as some
    features are enabled automatically depending on the clusters op-version. We
    also don't store the volume op-versions persistently and don't export the
    volume op-versions during sync. Due to this, there can occur cases which will
    lead to inconsistencies in volumes in different peers. One such case is below,
    
    Consider, a cluster made up 3 peers P1, P2 and P3, operating at op-version N.
    The cluster has two volumes V1 and V2, which have volume op-versions N (since
    volume op-version cannot be greater than cluster op-version). We have,
     Cluster-op-version = N
     V1 op-version = N
     V2 op-version = N
    A set operation on V1 causes the clusters op-version to be bumped up to N+1.
    Assume that there exist some features that are automatically enabled on
    op-version N+1. The op-version of V2 remains at N as no operation has been
    performed on it. So,
     Cluster op-version = N+1
     V1 op-version = N+1
     V2 op-version = N
    Now, we probe a new peer P4. On the new peer we will have the following
    op-versions,
     Cluster op-version = N+1
     V1 op-version = N+1
     V2 op-version = N+1
    This happens because we don't send volume op-versions during the sync after
    probe. P4 will freshly calculate the op-version of V2 (assuming features have
    been auto enabled due to the cluster op-version being N+1) as N+1.
    
    Another case is when glusterd on a peer restarts. Assume P3 was restarted,
    glusterd will recalculate the volume op-versions during the restore state.
    Again, op-version of V2 will be calculated as N+1 assuming auto enabled
    features. This will lead to inconsistency in the volume representation in
    memory and on disk, as glusterd will assume the volume contains auto enabled
    features, but the volfiles don't contain them as they were not regenrated.
    
    These kind of issues can be solved by calculating the volume op-version only
    when features are enabled and disabled (ie. during volume set/reset),
    persisting the volume-op-versions and exporting/importing them.
    
    Change-Id: I52de0668c92628622e85f4588fb28829a7231132
    BUG: 1005043
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5568
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 623d232d29bbed71349334988054a5bd205b1a39
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Sep 26 18:07:51 2013 +0530

    glusterd: Fix storing volumes on setting global opts
    
    Glusterd would not store all the volumes when a global options were set.
    When setting a global option, like 'nfs.*' options, glusterd used to
    modify the volinfo for all the volumes, but would store only the volinfo
    for the named volume. This lead to mismatch in the persisted and the
    in-memory representation of those volumes, which lead to problems like
    peers being rejected because of volume mismatches.
    
    Change-Id: I8bca10585e34b7135cb32af0055dbd462b3fb9b5
    BUG: 1012400
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/6007
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f84c710e93ab48dceabd3824f5286ed3edd9b60d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Sep 20 11:37:51 2013 +0530

    glusterd: Set errstr appropriately on peer op failure
    
    Change-Id: I27f5f7cd54115d7b236b42f6beaaa05a8b379dd7
    BUG: 1010153
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/5978
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8bd16cc88527584e91baa8773b4f01e7c44708c1
Author: ajha <ajha@redhat.com>
Date:   Fri Aug 30 15:14:46 2013 +0530

    features/changelog : Improvement in changelog "encoding-change".
    
    change in encoding method of changelog was critical section for
    "fop dispatch thread", "roll-over thread" and "reconfigure dispatch thread".
    
    In this patch the "encoding-method" is changed by the reconfigure dispatch thread
    lazily during handle_change, which solves the concurrency among the racing
    threads.
    
    BUG: 1002940
    Change-Id: I78c3e8887efa46d0fcc60755cdf4243031cfa3eb
    Signed-off-by: Ajeet Jha <ajha@redhat.com>
    Reviewed-on: http://review.gluster.org/5844
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>

commit 124d93ed3ea826cd16e4766f82b3c48af19cba5c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Sep 13 15:54:52 2013 +0200

    extras: add script and config for generating "Who wrote GlusterFS"
    
    This script and configuration can be used to generate statistics similar
    to the "Who wrote <linux-version>" series available on http://lwn.net.
    
    Example usage for statistics from the initial branchpoint of 3.4 to the
    current development of the release-3.4 branch:
    
     $ extras/who-wrote-glusterfs/who-wrote-glusterfs.sh \
           v3.4.0alpha...origin/release-3.4
    
    By default the statistics will be calculated over the currently checked
    out branch.
    
    Change-Id: Ie7b8b655c50dcb14257e42599e2f89642c8b5b42
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5912
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e9554f7792d893f0ea8afe368829f9944ef52bdf
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Thu Sep 19 12:01:38 2013 +0530

    gNFS: Incorrect NFS ACL encoding for XFS
    
    Problem:
    Incorrect NFS ACL encoding causes "system.posix_acl_default"
    setxattr failure on bricks on XFS file system. XFS (potentially
    others?) doesn't understand when the 0x10 prefix is added to the
    ACL type field for default ACLs (which the Linux NFS client adds)
    which causes setfacl()->setxattr() to fail silently. NFS client
    adds NFS_ACL_DEFAULT(0x1000) for default ACL.
    
    FIX:
    Mask the prefix (added by NFS client) OFF, so the setfacl is not
    rejected when it hits the FS.
    
    Original patch by: "Richard Wareing"
    
    Change-Id: I17ad27d84f030cdea8396eb667ee031f0d41b396
    BUG: 1009210
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/5980
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 84fa8af38d2eab0f72349abb8136811bd3e96570
Author: Anand Avati <avati@redhat.com>
Date:   Tue Sep 24 09:45:08 2013 -0700

    core: block unused signals in created threads
    
    Block all signal except those which are set for explicit handling
    in glusterfs_signals_setup(). Since thread spawning code in
    libglusterfs and xlators can get called from application threads
    when used through libgfapi, it is necessary to do this blocking.
    
    Change-Id: Ia320f80521a83d2edcda50b9ad414583a0175281
    BUG: 1011662
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5995
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8737b4697ad555a1e49ef87b5d439bfb74d8b5b5
Author: Anand Avati <avati@redhat.com>
Date:   Sun Sep 15 15:00:06 2013 -0700

    posix-acl: fixup extended ACL entries properly
    
    Typically when updating cached ACL from backend, we get both iatt and
    ACL xattrs (like lookup, readdirplus etc.) However in calls like
    setattr(), the mode would have updated but we receive only iatt and not
    the ACL xattrs. In such case we need to "spread" the effects of the
    changed mode properly into the cached ACL xattr ourselves.
    
    Change-Id: I23a7bc9c14722ff6848e175ed4bbe863a21ce2c9
    BUG: 998967
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5979
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 83937d1666f1f5e395afc7b2df477e9aad4c2278
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Jul 31 14:45:03 2013 +0530

    Revert "cluster/dht: Return success in dht_discover if layout issues"
    
    This reverts commit a3e593f9f17cb1e68db97bb5a0d8074793a33964 which
    was bought into fix dht_layout_anomalies error handling.
    
    We still see applications error'ing out due to graph switches.
    
    To fix the above issue -
    
    We cannot heal in dht_discover, as it is a gfid based lookup, and not
    path based. So, returning error here would lead to app's to see failure.
    
    Also, update the layout in inode_ctx even if it has anomalies. Let
    subsequent heals fix the issue.
    
    Conflicts:
    	xlators/cluster/dht/src/dht-common.c
    
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Change-Id: I68c1056c3587e04a02344548546ddd06034489c5
    BUG: 960348
    Reviewed-on: http://review.gluster.org/5443
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa971f439d6eef9e52091915ce7ab1127aac1368
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Sep 13 15:20:45 2013 +0530

    logging: Expose set_log_file_path() in libglusterfs.
    
    This patch also changes the behavior of glfs_set_logging().
    If logfile argument is not provided to glfs_set_logging(),
    libgfapi uses set_log_file_path() to create a logfile.
    
    Change-Id: I49ec66c7f16f5604ff2f7cf7b365b08a05b5460d
    BUG: 764890
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5910
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 848471799236063961eb37cb7bda3cf0e9a6f956
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Sep 13 11:11:41 2013 +0530

    logging: Remove multiple definitions of DEFAULT_LOG_FILE_DIRECTORY
    
    Change-Id: I8d670a228d3c1282aa7d70b151f166d04abc40e5
    BUG: 764890
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5909
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 711484d759cedbd77e449d306f7e31d596e6ae0d
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Sep 3 09:13:21 2013 +0000

    cluster/dht: Fix anomaly check
    
    We were wrongly detecting holes/overlaps for already accounted
    errors. Additionally, sort should also handle zero'ed out layout
    
    Change-Id: Ic3d13e1d735b914f9acc01fe919bc90656baea48
    BUG: 1003851
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5762
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit eec0e973be78e454665e6fbc645caddf44e362b9
Author: Anand Avati <avati@redhat.com>
Date:   Sat Aug 10 23:10:04 2013 -0700

    parser: use private namespace 'graphyy' instead of 'yy'
    
    This can cause linker errors when accessing glusterfs through
    libgfapi if the caller also uses a parser with 'yy' prefix.
    
    Change-Id: I6544333c47a1f18193741420717c989e4bdea7b1
    BUG: 764890
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5643
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 4152ef34ec08e09e885334955afe3ec88e798eb5
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Sep 10 15:14:52 2013 +0530

    glusterd/cli: Status detail cli parse check and vol geo status crash fix
    
    Change-Id: I1841864273fc4242de15fbfcf76fd5de40269f28
    BUG: 1006249
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5889
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7f608415063f04a1035bfe7d0f8ddfb9f0215e5c
Author: Anand Avati <avati@redhat.com>
Date:   Sun Sep 15 19:56:25 2013 -0700

    tests: take regression tests out of autotools
    
    make run-tests.sh "location independent" and replace 'make install'
    with cpio in glusterfs.spec.in
    
    Change-Id: I140473c7f558e1e0af93a863b79098ced516a76b
    BUG: 764966
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5986
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2e4064fe08e929fb4db30ae63c5cd404ab2d8b20
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 5 10:14:08 2013 -0400

    glusterd.service (systemd), ensure glusterd starts before local mounts
    
    NOTICE: this patch was accepted onto the release-3.4 branch for 3.4.1,
    but this same patch for master is languishing here in review.
    
    Try (emphasis on the try) to ensure that glusterd starts, and in turn
    starts glusterfsd before init attempt to mount any gluster (or gluster
    NFS) volumes in /etc/fstab.
    
    N.B. Joe Julian says this doesn't fix the problem for him, although it
    worked for me in kvm. Lennart Poettering says it should, and we should
    file a BZ against systemd if it doesn't. See
    https://lists.fedoraproject.org/pipermail/devel/2013-July/185870.html
    
    Change-Id: I4d8061217d8301beb0da485dc63a1984a7c57c37
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    BUG: 1004795
    Reviewed-on: http://review.gluster.org/5823
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 78b0b59285b03af65c10a1fd976836bc5f53c167
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Sun Sep 15 17:55:31 2013 +0530

    glusterd: Adding transaction checks for cluster unlock.
    
    While a gluster command holding lock is in execution,
    any other gluster command which tries to run will fail to
    acquire the lock. As a result command#2 will follow the
    cleanup code flow, which also includes unlocking the held
    locks. As both the commands are run from the same node,
    command#2 will end up releasing the locks held by command#1
    even before command#1 reaches completion.
    
    Now we call the unlock routine in the code path, of the cluster
    has been locked during the same transaction.
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    
    Change-Id: I7b7aa4d4c7e565e982b75b8ed1e550fca528c834
    BUG: 1008172
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5937
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fe16eaa5104cf015461c7b4b8f0d97e613344b1e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Sep 7 15:20:39 2013 +0530

    geo-rep: pack the value of 'readlink()' while crawling symlinks
    
    without having 'readlink()' value, symlink fails on slave mounts
    
    Change-Id: Ib84be8db77c033029ba8ba454fd629a496fc3fe1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 847839
    Reviewed-on: http://review.gluster.org/5950
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9905b562a3d4b508f83123e43574e8087651b357
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 16 14:24:54 2013 +0530

    geo-replication: treat MKNOD also as regular file create
    
    Change-Id: Iec04f642282b554a4d1b5f5c8cdc099fd001b3f4
    Original-Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 847839
    Reviewed-on: http://review.gluster.org/5949
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d702e702e7248da63449b714507010bb3ef1072d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 16 14:04:05 2013 +0530

    geo-rep: create hardlink as hardlinks in xsync crawl
    
    BUG: 847839
    Change-Id: Ieaa754f15611392c09afcc7190b9ff9da39d7fce
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5934
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e2093fb1500f55f58236d37a996609a2a1e1af8e
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Wed Sep 18 14:43:40 2013 +0530

    gNFS: NFS daemon is limiting IOs to 64KB
    
    Problem:
    Gluster NFS server is hard-coding the max rsize/wsize to 64KB
    which is very less for NFS running over 10GE NIC. The existing
    options nfs.read-size, nfs.write-size are not working as
    expected.
    
    FIX:
    Make the options nfs.read-size (for rsize) and nfs.write-size
    (for wsize) work to tune the NFS I/O size. Value range would
    be 4KB(Min)-64KB(Default)-1MB(max).
    
    NB: Credit to "Richard Wareing" for catching it.
    
    Change-Id: I2754ecb0975692304308be8bcf496c713355f1c8
    BUG: 1009223
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/5964
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 90ec0917558e6836d98faa4406b96158b13eacee
Author: Justin Clift <jclift@redhat.com>
Date:   Fri Sep 20 16:05:28 2013 +0100

    Fix typo in systemd service definition file
    
    Change-Id: Ia9dac04ad508fbaafbed24b2137b09872a1ca53c
    BUG: 1010352
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/5981
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 5d94695e9ad42343e72918024c046f22fe4941a0
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Aug 21 00:50:41 2013 -0700

    tests: Create a regression-tests package for distribution
    
    As of today regression tests are an in-house breed, by making
    it a new package and distributing it ensures larger set of
    people use it and contribute to it. This can also be used
    by any consumer/user to build their own environment for glusterfs
    regression testing which is today limited only to 'upstream'
    'glusterfs' releases and build.gluster.org
    
    Change-Id: I4f7e9fd1c49982dcf0d788ef6a83ffe895a956ac
    BUG: 764966
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5674
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 66747c96e6446da3da1c75ee7641fd75d1ed768c
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Sep 17 19:16:50 2013 -0700

    distribute: Rebalance should provide even disk space distribution
    
    Earlier disk space check had an issue which didn't
    provide the needed functionality to avoid migration
    when the destination had lesser available space,
    scenario we need to avoid is stated below :
    
    During rebalance `migrate-data` - Destination subvol experiences
    a `reduction` in 'blocks' of free space, at the same time source
    subvol gains certain 'blocks' of free space. A valid check is
    necessary here to avoid errorneous move to destination where
    the space could be scantily available.
    
    This patch provides a proper fix in place by subtracting
    necessary file blocks from destination and adding those blocks
    to source.
    
    Change-Id: I9c7840716a4256ef614ffc0fbfd9f2b456ac28c8
    BUG: 982919
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5961
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7da8040d96ae16d6d2b6079ffd8cbcfe5d28aac4
Author: meghana <mmadhusu@redhat.com>
Date:   Tue Aug 20 15:13:42 2013 -0400

    NFS : Coverity Fix.
    
    NFS defects reported by  Coverity run are fixed.
    
    Change-Id: Ib66847e8e66fb4a06b312c80814f9eafb032eba2
    BUG: 996390
    Signed-off-by: meghana <mmadhusu@redhat.com>
    Reviewed-on: http://review.gluster.org/5660
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit c550ae69526ad60b2f288ddc98a59141b9e64dcc
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Sep 13 18:48:38 2013 +0530

    cli/glusterd: improve rebalance fix-layout status reporting
    
    Problem:
    Currenly the CLI rebalance status command output does not indicate the
    'type' of rebalance, i.e. whether a full rebalance or only a fix-layout
    was carried out.
    
    Fix: After the rebalance status of all peers is received by the
    originator glusterd, alter it to reflect the type of rebalance
    before passing it on to the CLI process.
    
    Change-Id: I1940ffda0d36e25e5b33c84a0ea210394cc9e1d3
    BUG: 1004744
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5826
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f86a37bddf0f301c820c2a3ead50a93ce30dd2dc
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Feb 23 13:08:37 2013 +0530

    cluster/afr: Have common inode-write-fop cbk
    
    Change-Id: Ia7b324b86d6a7051d187106d7a060155e77defc5
    BUG: 910217
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5238
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 91e4b7aa1361087317238b9bf6427ef274737c8c
Author: Timothy Asir <tjeyasin@redhat.com>
Date:   Wed Sep 11 13:50:40 2013 +0530

    cli: add aggregate status for rebalance and remove-brick status xml output
    
    Add aggregate status information in <aggregate> section of gluster volume
    'rebalance status' and 'remove-brick status cli xml output.
    
    The aggregate status determined based on the most critical level
    and the aggregate status will have 'Complete' only when all
    individual status are 'Complete'.
    
    Change-Id: Ie805b9dd52fd82fd277c3da9ee91cc8b6dea8212
    BUG: 1006813
    Signed-off-by: Timothy Asir <tjeyasin@redhat.com>
    Reviewed-on: http://review.gluster.org/4950
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 67c28b19355c47e96d1420405cc38753a3e5f9be
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Sep 10 15:33:00 2013 +0530

    glusterd: Don't reset rebalance status on add-brick
    
    The rebalance status was being reset to 'Not started' when add-brick was
    performed. This would lead to odd cases where a 'rebalance status' on a
    volume would show status as 'not started' but would also include the
    rebalance statistics. This also affected the showing of asynchronus task
    status in 'volume status' command.
    
    By not resetting the status prevent the above issues from happening.
    Since we use the running/not-running of the rebalance process as the
    check when performing other operations we can safely leave the rebalance
    stats collected on an add-brick.
    
    Change-Id: I4c69d9c789d081c6de7e7a81dd0d4eba2e83ec17
    BUG: 1006247
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5895
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 49ae6d8cd0182a079fead5e20ae0e3b1e62de8c6
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Sep 17 19:27:57 2013 -0700

    build: AM_PATH_XML2 needs proactive check
    
    AM_PATH_XML2 needs check for its existence using
    aclocal macros - to avoid problems like below when
    libxml2 development libraries are not installed
    
    --------------------------------------------------
    
    ... GlusterFS autogen ...
    
    Generate gf-error-codes.h ...
    `gf-error-codes.h' -> `libglusterfs/src/gf-error-codes.h'
    Running aclocal...
    configure.ac:524: warning: macro `AM_PATH_XML2' not found in library
    Running autoheader...
    Running libtoolize...
    Running autoconf...
    configure.ac:524: error: possibly undefined macro: AM_PATH_XML2
          If this token and others are legitimate, please use m4_pattern_allow.
          See the Autoconf documentation.
    Running automake...
    --------------------------------------------------
    
    Change-Id: Ife463c34c45babc1c4c0ed6e8128b5c43419b9b9
    BUG: 947226
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5962
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit de2a8d303311bd600cb93a775bc79a0edea1ee1a
Author: Anand Avati <avati@redhat.com>
Date:   Tue Sep 17 16:45:03 2013 -0700

    Revert "cluster/distribute: Rebalance should also verify free inodes"
    
    This reverts commit 215fea41a96479312a5ab8783c13b30ab9fe00fa
    
    Realized soon after merging, that this patch is actually useless.
    Checking for inode utilization on dst relative to src is of no use
    because dst is already storing linkfile and inode is already consumed
    no matter what. We might as well perform the rebalance and save on an
    inode on the src node.
    
    Change-Id: I7b8b8d35d9063a710e1bee1c7c6c7739fcc45ad4
    Reviewed-on: http://review.gluster.org/5960
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Anand Avati <avati@redhat.com>

commit 215fea41a96479312a5ab8783c13b30ab9fe00fa
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Sep 16 22:36:10 2013 -0700

    cluster/distribute: Rebalance should also verify free inodes
    
    Currently during `MIGRATE_DATA` we never verified about the total
    inode usage among new and old bricks. Such checks are available for
    disk space usage but it is also needed for inodes during data
    migration. Such a check leads to uniform outcome of file distribution
    upon rebalance.
    
    Patch provides:
    
    - Check dst_inodes < src_inodes, a friendly `warning` message to
      indicate we have to ignore such an attempt
    - Rename __dht_check_free_space() --> __dht_check_free_space_and_inodes()
    
    Change-Id: I7bc4dd8b507883f0fb836300e99f0bb083493f5f
    BUG: 982919
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5948
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0402c691a9d245e00bd2e4bd100a6d5e591d3433
Author: Anand Avati <avati@redhat.com>
Date:   Tue Sep 3 18:13:27 2013 -0700

    fuse-bridge: enable --fopen-keep-cache based on FUSE_AUTO_INVAL_DATA.
    
    If kernel supports FUSE_AUTO_INVAL_DATA then it is safe(r) to turn on
    --fopen-keep-cache mode by default. Users report significant improvement
    in perf by enabling the mode.
    
    Change-Id: Icf9df4b7b43950d7e25302d9c2a1a7d14571a9a9
    BUG: 990744
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5770
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit 5ab18374d07c57de5647682d51afa05101be356f
Author: Anand Avati <avati@redhat.com>
Date:   Thu Sep 12 08:16:40 2013 -0700

    rpcsvc: allocate large auxgid list on demand
    
    For rpc requests having large aux group list, allocate large list
    on demand. Else use small static array by default.
    
    Without this patch, glusterfsd allocates 140+MB of resident memory
    just to get started and initialized.
    
    Change-Id: I3a07212b0076079cff67cdde18926e8f3b196258
    Signed-off-by: Anand Avati <avati@redhat.com>
    BUG: 953694
    Reviewed-on: http://review.gluster.org/5927
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit d7f7510f218e656cf2ba3bd821b80c14ab53846a
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 28 18:05:03 2013 -0700

    gfapi: implement a minimial glfs_fini()
    
    At the very least, we should PARENT_DOWN on the currently active
    graph and disconnect ourselves from glusterd.
    
    Further cleanups underway.
    
    Change-Id: I9276686a84b0975b5ce272b4cbec1b80920d5c5c
    BUG: 1004519
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5788
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 8eb3898578a4fe359934da57c0e51cfaa21685d4
Author: Anand Avati <avati@redhat.com>
Date:   Wed Sep 11 00:49:57 2013 -0700

    gfapi: use native STACK_WIND for read _async() calls
    
    There is little value in using synctask wrappers for async IO
    requests, as STACK_WIND is asynchronous by nature already.
    
    Skip going through synctask for read/write async calls.
    
    Change-Id: Ifde331d7c97e0f33426da6ef4377c5ba70dddc06
    BUG: 1009134
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5897

commit a5b74203589f1c06d86d50fb56940571bfc13e20
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Sep 16 14:18:53 2013 -0400

    qemu-block: support readdirp
    
    Support the readdirp fop in qemu-block to ensure that image files
    are handled correctly when readdirp is enabled. E.g., without
    readdirp support, incorrect stat data for formatted files can be
    reported back (and cached) via the client.
    
    BUG: 986775
    Change-Id: Ibc4bd0b42548953ebe30832f3d853bb68095f0ac
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5946
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ac2317aee9013aa0235318f8a4c808b3598d03b9
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Aug 20 18:09:22 2013 +0530

    glusterd : Blocking invalid values for geo-rep config options
    
    Change-Id: Ia9ee44763a9c2798b26d3225bf03a974d7ece21f
    BUG: 998962
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5666
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 52ce8fc0a8a8b87afe3e77d5aeee22baa7f216f8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Sep 16 14:02:25 2013 +0530

    geo-rep: retry in case of ENOENT errors in entry creations
    
    Change-Id: I8961633a7371c941a3feee44c949d5c934eca998
    Original-Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 847839
    Reviewed-on: http://review.gluster.org/5933
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>

commit 58423e6f14c7e35af97bb8abb5f61a7e719a02ce
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Sep 16 11:41:32 2013 +0530

    mount/fuse: Implement forget in cbks for fuse.
    
    With the introduction of inode_ctx_set in fuse as part of  2991503d014,
    forget cbk gets called for fuse xlator. Though nothing needs to be done
    inf forget_cbk, excessive log messages of the following kind are observed:
    
    [2013-09-16 06:09:50.758063] W [defaults.c:1331:default_forget]
    (-->/usr/local/lib/glusterfs/3git/xlator/mount/fuse.so(+0xa1f2) [0x7f51432781f2]
    (-->/usr/local/lib/libglusterfs.so.0(inode_unref+0x3c) [0x7f5144e5
    816c] (-->/usr/local/lib/libglusterfs.so.0(+0x2d061) [0x7f5144e58061]))) 0-fuse:
    xlator does not implement forget_cbk
    
    This patch prevents such log messages from being seen.
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    BUG: 979910
    Change-Id: Ie5874138f46822b10ff4213bd1134d78330ec460
    Reviewed-on: http://review.gluster.org/5932
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 91cd0eae2cc1d96cbafa6457835f146503355238
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Sep 4 11:50:40 2013 +0530

    cli,glusterd: Task parameters in xml output
    
    This patch introduces task parameters for the asynchronus task shown in
    volume status. The parameters are only given for xml output. The
    parameters shown currently are,
    - source and destination bricks for replace-brick tasks
      ......
            <tasks>
              <task>
                <type>Replace brick</type>
                <id>3d1a1005-9d2e-4ae0-bd62-577bc1d333a3</id>
                <status>1</status>
                <params>
                  <srcBrick>archm:/export/test4</srcBrick>
                  <dstBrick>archm:/export/test-replace1</dstBrick>
                </params>
              </task>
            </tasks>
      ......
    - list of bricks being removed for remove-brick tasks
      ......
            <tasks>
              <task>
                <type>Remove brick</type>
                <id>901c20ca-0da2-41de-8669-5f0caca6b846</id>
                <status>1</status>
                <params>
                  <brick>archm:/export/test2</brick>
                  <brick>archm:/export/test3</brick>
                </params>
              </task>
            </tasks>
      ......
    
    The changes for non-xml output will be done in a subsequent patch.
    
    Change-Id: I322afe2f83ed8adeddb99f7962c25911204dc204
    BUG: 916577
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5771
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 0b608508743baa63220a92361f443af8557a2b9b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Sep 11 13:44:10 2013 +0200

    qemu-block: fix building from distribution tarball when glib2-devel is installed
    
    Building RPMs from a 'make dist' tarball fails when qemu-block is
    enabled. Enabling is done automatically when the glib2 development files
    are available (enabled by ./configure).
    
    Manual building with:
    
      $ ./autogen.sh && ./configure && make dist && rpmbuild -ta *.tar.gz
    
    Building in mock works fine, glib2-devel is not installed by default so
    the qemu-block xlator gets disabled. This change also adds glib2-devel
    to the BuildRequires in the glusterfs.spec file, causing the qemu-block
    xlator to be built by default, and included in the glusterfs RPM.
    
    Change-Id: Ibb73628772586d9e07bbfde7a8ff2fc973489086
    BUG: 986775
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5896
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit df12400012af69f99dab62774244792b57c5178f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Sep 12 12:15:10 2013 +0200

    tests/basic/rpm.t: run mock builds inside the current working directory
    
    When running multiple mock builds at the same time, the space
    requirements under /var/tmp increases as well. Not all systems (like
    build.gluster.org) have enough free space in /var/tmp to host two
    mock-roots, which causes building to fail randomly.
    
    Change-Id: Iff1064d01893fb35ef59650d4373105068b5d3f7
    BUG: 1006269
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5899
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cd7951aa31ae4bbdf35fc6d1f2466636844b889d
Author: Aravinda VK <avishwan@redhat.com>
Date:   Fri Aug 30 14:37:03 2013 +0530

    cli: Add statusStr xml tag to task list and rebalance/remove brick status
    
    New xml tag statusStr added to following gluster cli commands
    gluster volume status all --xml (For Task status)
    gluster volume rebalance <VOLNAME> status --xml
    gluster volume remove-brick <VOLNAME> <BRICK1..> status --xml
    
    Example(volume status all):
    <task>
        <type>Rebalance</type>
        <id>82d8d122-8738-4144-8507-d93fc98b61df</id>
        <status>3</status>
        <statusStr>completed</statusStr>
    </task>
    
    Example(volume rebalance <VOL> status)
    <node>
        <nodeName>localhost</nodeName>
        <files>0</files>
        <size>0</size>
        <lookups>0</lookups>
        <failures>0</failures>
        <status>3</status>
        <statusStr>completed</statusStr>
    </node>
    
    Also modified task status as string instead of showing number
    in gluster volume status all
    
    Example:
    Status of volume: gv1
    Gluster process                                         Port    Online  Pid
    ------------------------------------------------------------------------------
    Brick sumne.sumne:/gfs/b1                               49154   Y       15489
    Brick sumne.sumne:/gfs/b2                               49155   Y       15493
    NFS Server on localhost                                 N/A     N       15913
    
               Task                                      ID         Status
               ----                                      --         ------
          Rebalance    82d8d122-8738-4144-8507-d93fc98b61df      completed
    
    BUG: 1003521
    Change-Id: Ib283016af4c18132fb13fb33d44075782d77823c
    Signed-off-by: Aravinda VK <avishwan@redhat.com>
    Reviewed-on: http://review.gluster.org/5739
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 643533c77fd49316b7d16015fa1a008391d14bb2
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Sep 11 01:26:13 2013 +0530

    mgmt/glusterd: Update sub_count on remove brick
    
    Change-Id: I7c17de39da03c6b2764790581e097936da406695
    BUG: 1002556
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5893
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7cfb26296f9f123c586f7e767402b97c724dc510
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Sep 6 15:49:14 2013 +0530

    doc: Steps to recover from split-brain
    
    BUG: 1006776
    Change-Id: I6f4bffe992758b2889df9ebfe117834dabe5c1cf
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4216
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 015f1fd479b42b79aac46a5b8d9980c770a32d9e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 10 19:13:47 2013 +0530

    rpc/rpc-lib: rpcsvc should reply when rpc_err is set
    
    Problem:
    When requests are received on a connection before setvolume
    is done, creating frame from the requests fail because there is
    no association of the transport with the conn(i.e. xl_private).
    xl_private is set only on set_volume. In such cases error response
    is not sent from server xlator to that request because of which
    operations on mount point are hanging.
    
    Fix:
    Set actor return value to RPCSVC_ACTOR_ERROR so that response is sent
    even in these cases.
    
    Change-Id: I74d7bc6849fde6c734008d67c1f4bc9d9f7a84f9
    BUG: 1006367
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5892
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7d9bc0d21408c31651a65a6ec0e67c3b8acd0fde
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Sep 4 13:06:57 2013 +0530

    cli: Fix 'status all' xml output when volumes are not started
    
    CLI now only outputs one XML document for 'status all' only containing
    those volumes which are started.
    
    BUG: 1004218
    Change-Id: Id4130fe59b3b74475d8bd1cc8134ac59a28f1b7e
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5773
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4c4aaa5abf68d4da8e3c626ab7a469b81354b9e2
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Sep 6 10:12:55 2013 -0400

    tests/basic/rpm.t: run mock builds in parallel
    
    save about six minutes per regression by building in parallel
    
    Change-Id: Iaf6fa545e20b0322b10e9e4ab7cc3d4254a0ece5
    BUG: 1006269
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5845
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit c05cd5a392efb382fc726c55f507beeedc824b02
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Aug 28 17:16:03 2013 +0530

    glusterd: Allow bumping down a peer's op-version during probe
    
    Earlier, a peer running a higher op-version couldn't be probed into a
    cluster running at a lower op-version. This created issues when trying
    to expand an upgraded cluster. This patch changes this behaviour.
    
    The cluster no longer rejects a peer being probed if its op-version is
    higher than the cluster op-version. The peer will reduce its op-version
    if it doesn't have any volumes. If the peer contains volumes and needs
    to reduce its op-version, it fails the handshake and the probe fails.
    
    Change-Id: I12c6c873922799e1557b7184e956baea643d0dea
    BUG: 1005038
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5715
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 367e9b922c2a50b862fc166cb7e9f238a9c40ab1
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Sep 10 12:56:55 2013 +0530

    glusterd: Added missing MY_UUID conversion in gsync staging
    
    Change-Id: Ia4bf607e044d50636fb0a599a2ff91059f5b17aa
    BUG: 1006177
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5887
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1f7469164a8d8fb0e031078073465b59c4334752
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Mon Sep 9 03:08:08 2013 -0700

    glusterfsd: use-readdirp w/o arguments should not turn off readdirp
    
    `use-readdirp` has an optional argument in argp -
    specifying just `--use-readdirp` command line should not
    'turn off' readdirp, since that undermines the meaning
    of such an argument.
    
    Change-Id: I965d87e29bd0d61997d9be96fa698e270a2ee173
    BUG: 983477
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5851
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ebcf1c8ddb76ca1234282e5189f6800d89db4b98
Author: Anand Avati <avati@redhat.com>
Date:   Thu Aug 29 23:35:23 2013 -0700

    cluster/dht: assign layout onto missing directories too
    
    The current self-healing algorithm is ignoring missing directories
    for assigning new layout. When lookup() is racing against mkdir()
    or when self-healing a half-done mkdir(), the layout assignment split
    must happen based on the final number of directories, and not the
    currently existing number of directories (because we finish mkdir()
    of missing directories before hash layout assignment).
    
    Without this fix, concurrent mkdir() and lookup() will step on
    each others feet, create a messed up layout on disk, and end up
    with different in-memory layouts.
    
    Once two clients have different in-memory layouts, creation of
    subdirectory will not arbitrate on the same hashed subvolume and will
    result in GFID mismatch of the sub-directory.
    
    Change-Id: Ia47acad67c265060405984c822b4d37512b9dbb3
    BUG: 907072
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5849
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Peter Portante <pportant@redhat.com>

commit d3e533fe333449a782b925414d856469987ee00a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Sep 6 12:08:19 2013 +0200

    rpm: fix "warning: File listed twice: .../glusterd.info"
    
    Commit a482e422 added glusterd.info to the %files section of the
    glusterfs-server package. However, this file was listed already. This
    causes the following warning when building the RPMs:
    
        warning: File listed twice: /var/lib/glusterd/glusterd.info
    
    Merging the attributes for /var/lib/glusterd/glusterd.info into one line
    prevents this warning.
    
    Change-Id: I0d518ec186a8725dc4c5cba00b60da83fdadf103
    BUG: 1005161
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5836
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2347a1a7594dafc1e6a74784287efe84963fe4ea
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 28 18:38:26 2013 -0700

    parser: make the parser thread safe.
    
    The volfile parser thread safe by guarding the parsing phase
    in a mutex. Thread safety becomes a problem when there are multiple
    glfs_t objects created by gfapi and all of them potentially parse
    the respective volfiles at the same time.
    
    Change-Id: I4376019c4956994b72397ab36e6ac3ce849797ec
    BUG: 1004519
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5790
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.org>

commit 1955f7dc84239f23660e23e637f9ddcc672cbeb7
Author: Poornima <pgurusid@redhat.com>
Date:   Fri Sep 6 16:13:30 2013 +0530

    gfapi: store the open/create flags in fd_t object
    
    The flags passed on to open and create calls were not being saved
    in the fd_t object, hence the fd migration was failing.
    
    Change-Id: I486bb818477fe4c393d64a711534a082162a0e53
    BUG: 1005159
    Signed-off-by: Poornima <pgurusid@redhat.com>
    Reviewed-on: http://review.gluster.org/5837
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b610f1be7cd71b8f3e51c224c8b6fe0e7366c8cf
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Jul 24 13:16:08 2013 -0700

    glusterfsd: Round robin DNS should not be relied upon with
    config service availability for clients.
    
    Backupvolfile server as it stands is slow and prone to errors
    with mount script and its combination with RRDNS. Instead in
    theory it should use all the available nodes in 'trusted pool'
    by default (Right now we don't have a mechanism in place for
    this)
    
    Nevertheless this patch provides a scenario where a list of
    volfile-server can be provided on command as shown below
    
    -----------------------------------------------------------------
    $ glusterfs -s server1 .. -s serverN --volfile-id=<volname> \
          <mount_point>
    -----------------------------------------------------------------
                       OR
    -----------------------------------------------------------------
    $ mount -t glusterfs -obackup-volfile-servers=<server2>: \
          <server3>:...:<serverN> <server1>:/<volname> <mount_point>
    -----------------------------------------------------------------
    
    Here ':' is used as a separator for mount script parsing
    
    Now these will be remembered and recursively attempted for
    fetching vol-file until exhausted. This would ensure that the
    clients get 'volume' configs in a consistent manner avoiding the
    need to poll through RRDNS.
    
    Change-Id: If808bb8a52e6034c61574cdae3ac4e7e83513a40
    BUG: 986429
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5400
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 94fdc3dd79fa052ba3eb8951fe5c4ddf9dd1c6e8
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Sep 6 06:49:09 2013 -0700

    Revert "tests/basic/rpm.t: run mock builds in parallel"
    
    This reverts commit 91e8103794349ebdd578b77987a089456a59c52b
    
    Reverting as regression tests are failing after this merge.
    
    Change-Id: I9dcd430b2f9a431c3c01deab1a205aed297216a3
    Reviewed-on: http://review.gluster.org/5842
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 91e8103794349ebdd578b77987a089456a59c52b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Sep 5 14:19:00 2013 -0400

    tests/basic/rpm.t: run mock builds in parallel
    
    save save about five minutes per regression
    
    Change-Id: I75d91cfef63347ca756b9e1fedcb697e9537edc0
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5828
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2a1f445d30f2d57951a4d5582c1d9b1f675ad704
Author: Anand Avati <avati@redhat.com>
Date:   Tue Sep 3 16:01:41 2013 -0700

    gfapi: apply an upper bound on nested symlink resolution
    
    In case of nested symlink resolution, implement an upper
    bound on the number of such nested levels the resolver will
    descend. This limit is arbitrary, and set to 2048 nested
    levels.
    
    Change-Id: I264e5bd60d317eda97f4e6f49bd5d8694f8664a9
    BUG: 1004100
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5768
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4b317e64cafe1e8621a8b24ebb8243931cda264a
Author: Anand Avati <avati@redhat.com>
Date:   Tue Sep 3 15:18:26 2013 -0700

    glusterfs, gfapi: fix symbol clash
    
    The callback structures in both protocol/client and glusterfsd,
    gfapi used the same name for the actor table - gluster_cbk_actors.
    
    CBKs are required only for the management connection, and the
    actors of protocol/client are NOP functions. This supposed-to-be
    NOP function dispatch tabble is actually ending up pointing to
    the actor table of glusterfsd or gfapi.
    
    These functions, even though set wrongly, are not even expected
    to be called through the protocol/client callback path. Glusterd
    however sends the FETCHSPEC (and other) notify callbacks to *all*
    connected clients unconditionally, and there is a small period
    of time when protocol/client is connected to glusterd for
    PORTMAP query. If the FETCHSPEC callback notify is issued in
    this window of time, we end up calling the wrong actor in the
    client side resulting in a crash.
    
    Change-Id: I605ff7df64c7faf4607369bbf275aedec28e1778
    BUG: 1004091
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5767
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 774e6d162dd826be6357de6112bac5a345790a9e
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Aug 13 11:02:21 2013 +0530

    gsyncd / geo-rep: use the correct virtual xattr to collect 'gfid'
    
    Change-Id: Ifea32ad1b2695f1668428fae6b263014bf320b70
    BUG: 996379
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5589
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 3b8b184afe5579425e0e4dcb50dd8dd99d33b63a
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Aug 26 18:14:48 2013 +0530

    gfid-access: Error logs for ga_newfile_parse_args
    
    Change-Id: I7aab98a70793bee936272f0b795f4c22c3733dd2
    BUG: 1001055
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5705
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 85c2b2de12e98a8cce34277541df8c5c511e7231
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Aug 29 22:57:44 2013 +0530

    gsyncd / geo-rep: distributify slave
    
    commit fbb8fd92 introduced slave distributification but had
    some problems (monitor would crash upon gsyncd start). This
    patch fixes the issue and makes code more pythonic ;)
    
    Change-Id: I2cbf5669d81966046a4aeeb4a6ad11a947aa8f09
    BUG: 1003807
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5761
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 717d2db0c0df5844cbc7ce99c8ec7457f24d8e0c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 28 13:58:16 2013 +0530

    gsyncd / geo-rep: Fix "regular file" overloading link()
    
    ... missing entry2pb() call before going ahead with create.
    
    Change-Id: I48de4df3f0ea6c789c9eeb10cd332ab461f3c868
    BUG: 1003805
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5760
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit eebd4e14853b1660ccf520f4ee34729d2b118878
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 28 01:33:11 2013 +0530

    geo-replication: fix the logic of choosing the remote node to sync
    
    Change-Id: Ie15636357d89e94b6bfad0e168b1fcad53508c47
    BUG: 1003807
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5759
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b2e8a4517d63100e9527a1995ef24507192fc363
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Aug 27 12:20:30 2013 +0530

    gsyncd / geo-rep: maximum number of retries per changelog
    
    With entry retries MAX_RETRIES is the threashold for the number
    of times we retry a changelog. After hitting this limit, the
    changelog is marked as processed after warning for incompleteness
    in the log.
    
    Change-Id: I777b71b4cdaa63335d9c936f2d64e5c0264a0f26
    BUG: 1003803
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5758
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e0fa0bb1b1e1758d2e68b4940939e87d438fa14f
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Aug 27 13:02:00 2013 +0530

    gsyncd / geo-rep: fix hardlink creation on slave
    
    Change-Id: I20fbd518bf519cbf2362b97aeb8be7c3b105087a
    BUG: 1003805
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5757
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f201b46d1b20db1f2b11344e99db3381d9d4c1e1
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Aug 27 14:02:24 2013 +0530

    gsyncd / geo-rep: handle ENOENT during readlink()
    
    Change-Id: I8611122fda63ea496ad4491473ecabe96bf19cfa
    BUG: 1003803
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5756
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8910136c09e11f651fe846e3f357341b9260930e
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 21 16:33:41 2013 +0530

    gsyncd / geo-rep: overload rename with an unlink
    
    This is certainly a "hack" for cases when after a rename
    the gfid is unlinked (which is now pointed by a different
    pargfid/basename). This was osbserved when a file edited
    (uisng vi/vim) on the glusterfs mount point which has a
    geo-replication session running.
    
    Change-Id: I0a5d9f0f549aa4403671fa1f11e95510142e5720
    BUG: 1003800
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5755
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit aa292ab99c9db37dd5080aa5d65f24a8887b855b
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 21 20:38:09 2013 +0530

    gsyncd / geo-rep: fix "regular file" overloading rename
    
    entry operation on the slave was using source parent gfid
    and basename when renames are overloaded to use regular file
    creation. This patch fixes the issue by using the destination
    parent gfid and basename for these cases.
    
    Change-Id: I1a4e8df7f07905224ce44ef5abd6f180234285ab
    BUG: 1003800
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5754
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2f305eaed9805ff32c95680c5ac83e001d100cdc
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Aug 13 11:09:31 2013 +0530

    gsyncd / geo-rep: "disjoint" cascading geo-replication sessions
    
    Slave's xtime is now stored on the master itself (and that too only on
    the root), which implies it cannot be propogated to the cascaded slave.
    Thus the intermediate master now makes use of it's own volume information
    to propogate volume-mark and xtime.
    
    On starting Geo-Replication "geo-replication.ignore-pid-check" marker
    option is enabled, which is an override for the client-pid check in
    marker. This options triggers marker update only for geo-replication
    auxillary mount (client-pid == -1). Since gsyncd not does setxattr()
    directly on the bricks, this option won't trigger a chain of spurious
    metadata updates that would need to be processed by gsyncd.
    
    Change-Id: If50c5ef275dfb6b4ff4fd35be2565587e2fdf3e1
    BUG: 996371
    Original Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5592
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a6a74c926be767decbcf55dc7d95228c6a62df12
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Aug 12 22:18:53 2013 +0530

    features/marker: force xtime updates (configurable) for client-pid = -1
    
    This is required by Geo-Replication that does auxillary mount
    with client-pid as -1 (which has special treatment at specific
    places in GlusterFS), to trigger xtime updates on the intermediate
    master in a cascading setup.
    
    Marker too had a check to "not" mark updates for geo-replication's
    auxillary mounts. With the new geo-replication design, xtimes are
    not set by the master on the slave for all entities. Due to this
    cascading setups were broken.
    
    This patch introduces "geo-replication.ignore-pid-check" option
    as a "override" for the client-pid check for gsyncd's client-pid.
    When this options is enabled, marker start "marking" even if the
    updates are from the special client.
    
    Geo-Replication on the detection of itself being an intermediate
    master, enables this option.
    
    Change-Id: I9f7140edd12fef5480595ee0f93f35b94cdb8345
    BUG: 996371
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5591
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9ccdba413ff12956df2221fce91b220300479d23
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 7 16:10:25 2013 +0530

    gsyncd / geo-rep: introduce "recovery" mode
    
    This mode introduces and optimized recovery of master,
    used during failover-failback cases. Files are only
    transferred if they are identified as changed on the slave.
    
    A normal failback mechanism would be just to reverse the
    direction of geo-replication syncing. Doing this is the
    correct way but could be time consuming. "Recovery" mode
    optimizes this by identifying files (as skipping them) duing
    the one-shot crawl.
    
    NOTE: Use this mode when you are _absolutely_ sure that the
    namespace on the master is intact, ie. there is number of files
    in master is equal to the number of files in the slave, but the
    slave was written to (after a failover) when master was brought
    back up.
    
    - gluster volume geo <MV> <SLAVE>::<SV> config special_sync_mode recover
    - gluster volume geo <MV> <SLAVE>::<SV> start
    
    Change-Id: Idb698949e4e86698b15d04a35d33095562f51714
    BUG: 994462
    Original Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5515
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 07bb6118677119fd21ff38d51b4cefd06c0ad35a
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Aug 12 22:15:58 2013 +0530

    gsyncd / geo-rep: remove deprecated code!
    
    This includes "xtime" base crawling and syncing,
    "Blind" and "Wrapup" mixins for failover/failback.
    
    Change-Id: I9bc8695dc1c19b1261332f64621305dff2929b32
    BUG: 994461
    Original Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5514
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 60431cecae08d2d39a2a3d6735b8544af8266f32
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 7 11:53:06 2013 +0530

    gsyncd / geo-rep: fix regular file creation on rename
    
    On creation of a regular file on the slave (this happens
    when an unlink()/rmdir() operation is performed on master
    after a rename() or a link().
    
    This patch fixes the regular file creation on the slave when
    the above mentioned series of operation occurs. entry_ops()
    on the slave for a rename() was missing the stat() information.
    
    Change-Id: Idb80c6b3e27c1797dade1113ac8ce920db9c740c
    BUG: 994353
    Original Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5509
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fe98c2902fd13dac93e5add60d1f10b2cef8ae37
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Aug 12 22:09:45 2013 +0530

    glusterd/cli: Geo-Replication "status detail" cmd
    
    Provides detailed status info in the following format
    
                        MASTER <master-vol>  SLAVE <slave-vol>
    
    NODE   HEALTH   UPTIME  FILES SYNCD  FILES PENDING  BYTES PENDING  DELETES PENDING
    -----------------------------------------------------------------------------------
    
    This patch introdues "status detail" command to show crawl related
    information in CLI. These values are "pulled" from gsyncd when
    "status detail" is executed.
    
    Change-Id: I1fdaf7180eacce054a864d34971dc160bd7301e1
    BUG: 990420
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5590
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 603119c57c5055e17693d47b9965216954f45247
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 31 13:01:30 2013 +0530

    gsyncd / geo-rep: Introduce basic crawl instrumentation
    
    This patch extends the persistent instrumentation work done by
    Aravinda (@avishwa), by introducing a handfull of instrumentation
    variables for crawl. These variables are "pulled up" by glusterd
    in the event of a geo-replication status cli command and looks
    something like below:
    
    "Uptime=00:21:10;FilesSyned=2982;FilesPending=0;BytesPending=0;DeletesPending=0;"
    
    "FilesPending", "BytesPending" and "DeletesPending" are short-lived
    variables that are non-zero when a changelog is being processes (ie.
    when an active sync in ongoing). After a successfull changelog process
    "FilesPending" is summed up into "FilesSynced". The three short-lived
    variabled are then reset to zero and the data is persisted
    
    Additionally this patch also reverts some of the changes made for
    BZ #986929 (those were not needed).
    
    Change-Id: I948f1a0884ca71bc5e5bcfdc017d16c8c54fc30b
    BUG: 990420
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5441
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f0b92a45e5c757ec25257e389c877b9b0de8ed07
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 31 19:40:28 2013 +0530

    gsyncd / geo-rep: periodically set slave xtime on slave
    
    setting the slave xtime on the slave (after each changelog/xsync)
    crawl helps in two things:
      * effective recover of master (failover/failback)
      * cascading setup - instances when the session from intermediate
                          master session is stopped, data is put on
                          the master -> slave sesssion and then the
                          cascading session is started again.
    
    Change-Id: Ifae10a6ac09dc0d17707c3b5a3090bcf1efec8b6
    BUG: 990900
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5451
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Avra Sengupta <asengupt@redhat.com>
    Tested-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1a642df1e963bf13d44de5b28a72ed2eb4dbca88
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jul 30 16:18:02 2013 +0530

    glusterd: Added op-version checks to geo-rep commands.
    
    Added op-version checks to all geo-rep commands. Min
    op-version should be 2.
    
    Change-Id: I942d897404e11e4d53123409731ba5cd252668fe
    BUG: 847839
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5732
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 81d32caa26ef0e3db10cae53e6820927fe0569fc
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 21 12:53:11 2013 +0530

    glusterd/gverify: Check for passwordless ssh in gverify.
    
    Change-Id: I8c2d398114ad4534bcc052f9a5be8bbb2e7e2582
    BUG: 999531
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5677
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc6938613cf12c621d705ceaa8cf695887447d5e
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Aug 20 13:36:10 2013 +0530

    glusterd: Allowing root@hostname::slave georep sessions to be created.
    
    non-root@hostname::slave-vol geo-rep sessions are not supported.
    only hostname and root@hostname sessions are supported, and are
    treated as the same.
    
    Change-Id: I87551e1bd4ff4e0e6520c34eb3d944587cc65476
    BUG: 998933
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5659
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3bfa0dde137f35d68e7f935ddd562136b4829e21
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Aug 7 17:09:17 2013 +0530

    glusterd/gverify.sh: Stops session being created with invalid slave details
    
    create force will fail with proper message, if the ip is not
    reachable, or is unable to fetch slave details.
    
    Change-Id: I44a3ba777b37702ffd0e48e9cb46c51e293327d4
    BUG: 988314
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5516
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 59d37265acf250b1b29c186020c55e9df0ef4215
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Aug 1 13:22:34 2013 +0530

    gverify/glusterd : Added check to warn the user of existing files in slave volume
    
    Change-Id: I41c9fb44613386189d9f3c090729f4ded8e4dea8
    BUG: 990997
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5453
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c7cc5252a350ff78b5f8396d05c85b9d2ade17b8
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Aug 2 15:34:00 2013 +0530

    glusterd: Saving geo-rep session details in a more specific path
    
    Now saving the session details in
    /var/lib/glusterd/geo-replication/<mastervol>_<slaveip>_<slavevol>
    repo to distinguish between two master-slave sessions where the
    slavename is same across two different clusters.
    
    Change-Id: I57c93f55cc9bd4fe2bffe579028aaf5e4335b223
    BUG: 991501
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5488
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fa095c24979db2d0a3a6413aa431fe7256be5206
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Aug 21 16:28:41 2013 -0700

    geo-replication: Use a md5 based unique control path
    
    A hostname fqdn can be of length 255 according to RFC1123
    ------------------------->
    /usr/include/bits/posix1_lim.h:#define _POSIX_HOST_NAME_MAX  255
    <-------------------------
    On linux this length is 64
    ------------------------->
    /usr/include/bits/local_lim.h:#define HOST_NAME_MAX 64
    <-------------------------
    
    When a given hostname is > 45 (characters) - SSH fails with
    
    -------------------------->
    "ControlPath too long for Unix domain socket".
    <--------------------------
    
    Indicating that the total length of ControlPath which is
    on linux should be 108
    
    ------------------------->
    /usr/include/linux/un.h:#define UNIX_PATH_MAX   108
    <-------------------------
    
    This leads to "faulty" geo-replication status.
    
    This patch brings in a new file called manifest which carries
    given a geo-rep session some unique information - with which
    a unique `md5` is generated in a 32length digest, this ensures
    that we don't exceed UNIX_PATH_MAX limitations instead we use
    a conservative approach and still be able to provide a unique
    socket path.
    
    Change-Id: I3a6a27d605d751a86e7c82eace4561d9b0134fe1
    BUG: 990330
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5681
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit 3b23f9acae02e6be192c00fc410a4d15974f5343
Author: Brian Foster <bfoster@redhat.com>
Date:   Tue Jul 2 10:47:00 2013 -0400

    performance/readdir-ahead: introduce directory read-ahead translator
    
    This is a translator to improve the performance of typical,
    sequential directory reads (i.e., ls). readdir-ahead begins
    preloading the contents of a directory on open and serves readdir
    requests from the preloaded content. readdir-ahead is currently
    implemented to only handle the single threaded directory read
    case.
    
    readdir-ahead is currently disabled by default. It can be enabled
    with the following command:
    
    	gluster volume set <volname> readdir-ahead on
    
    The following are results of a getdents test on a single brick
    volume.
    
    Test info:
    
    - Single VM, gluster client/server.
    - Volume mounted with native client using --gid-timeout=2.
    - getdents on single directory with 100k 0-byte files.
    
    Test results:
    
    - !readdir-ahead
    
    read 3120080 bytes from offset 0
    3 MiB, 4348 ops, 0:00:07.00 (416.590 KiB/sec and 594.4737 ops/sec)
    
    - readdir-ahead
    
    read 3120080 bytes from offset 0
    3 MiB, 4348 ops, 0:00:03.00 (820.116 KiB/sec and 1170.3043 ops/sec)
    
    BUG: 980517
    Change-Id: Ieceb9e1eb47d1d5b5af8da2bf03839537364653f
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4519
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 98df12f040d95d6a26047f03988b120984f7439e
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Sep 3 16:30:33 2013 +0530

    mgmt/glusterd: Regenerate client volfiles during upgrade
    
    Change-Id: I1442bc1d115a9c6ecf139a0ca9da74d07e0fe928
    BUG: 1003855
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5764
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2c15621d26fda5ba21e375d803baa5d8e09e6260
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Sep 3 13:30:13 2013 +0530

    cluster/afr: Set size based source only when sizes are unequal
    
    Change-Id: I18583f14edf1011401be15744371e2a6b79d75cc
    BUG: 1003842
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6f85f6ce64c99e70d3b674e2e01657803ee3c082
Author: Anand Avati <avati@redhat.com>
Date:   Tue Aug 27 05:02:20 2013 -0700

    afr: make NOP truncate/ftruncate efficient
    
    If truncate/ftruncate is called with the offset as the current size
    of file, then skip the durability fsync and unwind quickly.
    
    Change-Id: I0baec68d96c6d4d8217d33bd9738f7ed0d1b40c5
    BUG: 958118
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5737
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 53e98f11d1f3df30cc013af021464a257949a62d
Author: Anand Avati <avati@redhat.com>
Date:   Tue Mar 5 14:48:28 2013 -0800

    features/qemu-block: support for QCOW2 and QED formats
    
    This patch adds support for internals snapshots using QCOW2 and
    general framework for external snapshots (next patch) with
    QCOW2 and QED.
    
    For internal snapshots, the file must be "initialized" or
    "formatted" into QCOW2 format, and specify a file size.
    
    Snapshots can be created, deleted, and applied ("goto").
    
    e.g:
    
     // Format and Initialize
    
    sh# setfattr -n trusted.glusterfs.block-format -v qcow2:10GB /mnt/imgfile
    sh# ls -l /mnt/imgfile
    -rw-r--r-- 1 root root 10G Jul 18 21:20 imgfile
    
     // Create a snapshot
    
    sh# setfattr -n trusted.glusterfs.block-snapshot-create -v name1 imgfile
    
     // Apply a snapshot
    
    sh# setfattr -n trusted.gluterfs.block-snapshot-goto -v name1 imgfile
    
    Change-Id: If993e057a9455967ba3fa9dcabb7f74b8b2cf4c3
    BUG: 986775
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5367
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit 0d60175bd684cf6a14f750579d82dbd1ba97fcbc
Author: Anand Avati <avati@redhat.com>
Date:   Wed Mar 6 01:11:59 2013 -0800

    contrib/qemu: Import qemu block source code
    
    This qemu block format source code and its minimal
    dependency files will be used in the next patch to implement
    a qemu-block format translator.
    
    Change-Id: Ic87638972f7ea9b3df84d7a0539512a250c11c1c
    BUG: 986775
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5366
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit 7dbfbfd3694e02b90e8f3ce509f5279da1523a02
Author: Anuradha Talur <atalur@redhat.com>
Date:   Wed Aug 28 14:29:50 2013 +0530

    features/locks : Improves debuggability of inode/entry locks.
    
    Prints, in the statedump, the information about the mount that
    performed the inode/entry lk.
    
    For the entrylks that are granted after a blocked state, the
    blocked time is not printed. A patch for that will be sent
    later.
    
    Change-Id: Ib0c1ed21fa9328b435f96b590dd343f59814a08d
    BUG: 915629
    Signed-off-by: Anuradha Talur <atalur@redhat.com>
    Reviewed-on: http://review.gluster.org/5712
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f8e968a49468fdea5503423c2c9c4be82c76ad6f
Author: Bala.FA <barumuga@redhat.com>
Date:   Thu Aug 22 09:03:38 2013 +0530

    build: handle dependencies for syslog properly
    
    This patch conditionally enables rsyslog dependencies based on syslog
    build option.
    
    Change-Id: I2168f29a03504ec839c3048ce112e8dfb2226aa0
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/5684
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 85b6dcfb533c5b04038808135a581eb7ca9fd61d
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Wed Aug 28 17:39:23 2013 +0530

    cluster/afr: Improvement in logging of self heal completion status
    
    Additional information for source and sinks are added.
    
    Change-Id: I1704956ff86ac3ae36744efe7499c1d1c43faeaf
    BUG: 968301
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5638
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 479087c1e670faea4a0ef7a6d13a9869ef9de69f
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Aug 29 17:17:14 2013 +0530

    api: Add null check for active_subvol in glfs_close.
    
    Problem:
    In glfs_close, NULL value returned by glfs_active_subvol was not
    being checked and was causing a crash.
    
    Change-Id: I6eefa60e7b07dee251b98932b1d08a5c2981d3d7
    BUG: 1002511
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/5733
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2ec4b22bb02f572f74157df5264b247095fece77
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Aug 29 19:04:40 2013 +0530

    api: Fill loc.path and loc.gfid before syncop_open.
    
    syncop_open was crashing because of NULL dereference.
    This fixes that.
    
    Change-Id: I4bc48fac2a6c0b15c806cbbb4ae45c67891ab7ed
    BUG: 1002577
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/5734
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7dd4be82b1a346077673fde9218ae7c8ad8e11e0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 29 22:42:43 2013 +0530

    cluster/afr: Reset attempted count before attempting blocking lock
    
    Problem:
    internal_lock->lk_attempted_count keeps track of the number of blocking
    locks attempted. lk_expected_count keeps track of the number locks expected.
    Here are the sequence of steps that happen which lead to the illution that
    a full file lock is achieved, even without attempting any lock.
    
    2 mounts are doing dd on same file. Both of them witness a brick going
    down and coming back up again. Both of the mounts issue self-heal
    1) Both mount-1, mount-2 attempt full file locks in self-heal domain.
    lets say mount-1 got the lock, mount-2 attempts blocking lock.
    
    2) mount-1 attempts full file lock in data domain. It goes into blocking
    mode because some other writes are in progress. Eventually it gets the lock.
    But this results in lk_attempted_count to be still as 2 and will not be reset.
    It completes syncing the data.
    
    3) mount-1 before unlocking final small range lock attempts full file lock in
    data domain to figure out the source/sink. This will be put into blocked mode
    again because some other writes are in progress. But this time seeing the
    stale value of lk_attempted_count being equal to lk_expected_count, blocking_lock
    phase thinks it completed locking without acquiring a single lock :-O.
    
    4) mount-1 reads xattrs without any lock but since it does not modify the xattrs,
    no harm is done by this phase. It tries to do unlocks and the unlocks will fail
    because the locks are never taken in data domain. mount-1 also unlocks
    self-heal domain locks.
    
    Our beloved mount-2 now gets the chance to cause horror :-(.
    
    5) mount-2 gets the full range blocking lock in self-heal domain.
    Please note that this sets lk_attempted_count to 2.
    
    6) mount-2 attempts full range lock in data domain, since there are still
    writes on going, it switches to blocking mode. But since lk_attempted_count is 2
    which is same as lk_expected_count, blocking phase locks thinks it actually got
    the full range locks even though not a single lock request went out the wire.
    
    7) mount-2 reads the change-log xattrs, which would give the number of operations
    in progress (lets call this 'X'). It does the syncing and at the end of the sync
    decrements the changelog by 'X'. But since that 'X' was introduced by 'X' number
    of transactions that are in progress, they also decrement the changelog by 'X'.
    Effectively for 'X' operations 'X' number of pre-ops are done but 2 times 'X'
    number of post-ops are done resulting in -ve changelog numbers.
    
    Fix:
    Reset the lk_attempted_count and inode locks array that is used to remember locks
    that are granted.
    
    Change-Id: Ic0a79cd16f32392ea7c790511343c73592bbe6bd
    BUG: 1002698
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5736
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3a3441ef7665b5f55a9e2de63ea07173bf0f0db0
Author: Anand Avati <avati@redhat.com>
Date:   Mon Aug 26 21:58:26 2013 -0700

    nfs: prevent NFS server crash when upgrading from 3.2.x server
    
    After an upgrade the NFS3 filehandle size changed (became smaller),
    but when doing a live ugprade the client would send the old handle
    (expect ESTALE and do fresh lookup). But when reading the old
    handle we were reading it into a structure which was limited to the
    size of the new handle, while we should have been reading into a
    buffer which is as big as the NFS3 spec permits the handle size to
    be. The actor functions declare the structure on the stack. So the
    overflow is resulting in a stack corruption.
    
    Change-Id: Ie930875ac9db46b43d1cb8ad1e6d89cdaeded7ca
    BUG: 1002385
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5730
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c8ccfda3a7af1552419ba4f9dfb719fbf0e3f211
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 28 22:54:35 2013 -0700

    cluster/afr: unlock before aborting transaction
    
    Else this results in a missing frame causing a hang
    
    Change-Id: Ib5f3dc6a3999449faa2853cee2944af2fb065a20
    BUG: 1002399
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5731
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bf63e7c6a3fa1bfceb14acf5504b0d52833f7118
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Aug 14 07:09:52 2013 -0400

    cluster/stripe: enable coalesce mode by default
    
    It has been available for a while now and is probably the sane
    default due to the more efficient layout and performance benefit.
    
    BUG: 1001207
    Change-Id: I6275f9741866c0afd6e685f8dc5867a86485fd20
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5624
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit db0b19a5420d417cf4da70bf886b53619e17a739
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Aug 27 13:42:41 2013 +0530

    cluster/afr: Add special handling for failure postops
    
    Idea is to not leave the file in FOOL-FOOL scenario in case on
    all the bricks data transaction failed with EDQUOT to avoid
    increasing un-necessary load of self-heals in the system.
    
    For directory transactions don't leave pending changelog in case
    the failures are seen on all the subvolumes.
    
    Change-Id: I38a5561d1d581a78347a76a4a509514e4a0c3fb7
    BUG: 969461
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5709
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b880b6b2908ad4e4afc8e26613bd0db8f0b28750
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 28 22:43:41 2013 +0530

    stripe: remove unused param, handle mem alloc failure
    
    Change-Id: I9c27b1edab111031ca8eea9cc49480ea01e39089
    BUG: 1002207
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5716
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bbcdbd8c36c7756f39bb7464cd1c69b67e66cfaa
Author: Anand Avati <avati@redhat.com>
Date:   Fri Mar 15 11:20:53 2013 -0700

    synctask: minor enhancements
    
    - Enhance syncenv_new() to accept scaling parameters of syncproc.
      Previously the scaling parameters were hardcoded and decided at
      compile time.
    
    - New API synctask_create() which returns the created synctask. This
      is similar to synctask_new which only returned the status of whether
      a synctask could be created or not.
    
      The meaning of NULL cbk in synctask_create() means the task is
      "joinable". Until synctask_join() is called on such a synctask,
      the task is not reaped and resources are not destroyed. The
      task would be in a zombie state after synctask_fn returns and
      before synctask_join() is called.
    
    Change-Id: I368ec9037de9510d2ba951f0aad86aaf18d9a6b6
    BUG: 986775
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5365
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit faef08b7cf84ca9e68437abacad12133ef7569be
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 15 22:01:20 2013 +0530

    cluster/afr: Don't delay post op in cases of failures
    
    Change-Id: Ib0c3af6babc61dc3ed45252582876e2f243d6446
    BUG: 958118
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5635
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8fcf91b51ccd457d417e71c401f6e6af1dffc607
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 28 13:28:29 2013 -0400

    api: glusterfs-api.pc.in (and libgfchangelog.pc.in) use rpath (-Wl,-R...)
    
    Change-Id: Icdd23f1c31421c882db106cdad1b1406569594ca
    BUG: 1002220
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5717
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bbefeffafe9a2a5ba493e4bc0c9c9480d577e881
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Aug 9 14:17:33 2013 +0200

    nfs: persistent caching of connected NFS-clients
    
    Introduce /var/lib/glusterfs/nfs/rmtab to contain a list of NFS-clients
    which have a volume mounted. The volume option 'nfs.mount-rmtab' can be
    set to an alternative filename. When the file is located on shared
    storage, multiple gNFS servers can use the same file to present a single
    NFS-server.
    
    This cache is read when a system administrator calls 'showmount -a' and
    updated when an NFS-client calls MNT or UMNT from the MOUNT protocol.
    
    Usage:
    - create a volume for storing the shared rmtab file
    - mount the volume on all storage servers, at the same location
    - make sure that the volume is mounted at boot (add to /etc/fstab)
    - place the rmtab file on the volume:
       # gluster volume set <VOLUME> nfs.mount-rmtab <MOUNTPOINT>/<FILENAME>
    - any subsequent mount requests will add an entry to this file
    - 'showmount -a' requests will return the NFS-clients using the cluster
    
    Note:
    The NFS-server does currently not support reconfigure(). When a
    configuration option is set/changed, the NFS-server glusterfs process
    gets restarted. This causes the active NFS-clients to be forgotten (the
    entries are saved in the old rmtab, but we do not have a reference to
    that file any more, so we can't re-add them). Therefor a re-mount done
    by the NFS-clients is needed before they get listed in the rmtab again.
    
    Change-Id: I58f47135d60ad112849d647bea4e1129683dd2b3
    BUG: 904065
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4430
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <harsha@harshavardhana.net>
    Tested-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit cd2537541540074a5db452a49f9be220e3d76d32
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Aug 25 20:51:20 2013 +0530

    api: Set errno before invoking glfs_init_done()
    
    Change-Id: I3f4d3cfaf7078e126881111eb840d854b0b6466d
    BUG: 860212
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5704
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2991503d014f634da5cd10bcb851e986a3dcd5c2
Author: Anand Avati <avati@redhat.com>
Date:   Mon Aug 12 09:41:06 2013 -0700

    mount/fuse: perform lookup() on inodes linked through readdirplus
    
    Some xlators still require lookup() fop to be sent for proper working.
    This patch remembers inodes which have been linked through readdiprlus
    and makes the resolver send lookups on them.
    
    Change-Id: Ibe8a04a659539d90dfc794521b51bf2bda017a0b
    BUG: 979910
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5267
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 32fb404ef2fda7368c11c591bfa4dcf269cbd320
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Aug 22 16:25:58 2013 +0200

    build: fix days and dates in the %changelog of the spec-file (2nd part)
    
    This prevents more unneeded build warnings like:
    
        warning: bogus date in %changelog: Mon Apr 22 2008 ...
    
    Bug: 1000019
    Change-Id: I1d59fb93806e25a4629ce027beec324d03702e15
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5701
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cb533fc296e37ffbd7937a8550611d557b89ae0b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Aug 21 18:54:05 2013 +0530

    core: remove GLUSTERFS_CREATE_MODE_KEY usage
    
    Change-Id: I23b8cb7223b91a55af1cd4214f61bbe0e87351f6
    BUG: 952029
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5683
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d3bbbbb158942a974414b021e3320c72c49d0cfe
Author: Anand Avati <avati@redhat.com>
Date:   Thu Aug 22 15:02:00 2013 -0700

    gfapi: Add description of glfs_io_cbk function as a comment
    
    No code change, just add a comment describing the callback function
    type.
    
    Change-Id: I3a5c5b3d3fe042b4f535963dd477806832c15704
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5696
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit d64df6a92c2492812ef7c23cc133f5d7a113ec42
Author: Anand Avati <avati@redhat.com>
Date:   Thu Aug 22 14:14:22 2013 -0700

    rpc: fix typo which refers glibc macro
    
    A typo which read MAX_AUTH_BYTES instead of GF_MAX_AUTH_BYTES was
    picking the value 400 instead of the larger 2048. This causes
    failures when number of aux group ids is a large number.
    
    Change-Id: Idb8d59aee2690fd53e24c2e09f58a16fe387ef27
    BUG: 1000131
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5695
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 898edbf1335726566d501e2409b57fef4f97671e
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 08:54:59 2013 +0200

    doc: Move glusterd.vol to extras/ directory
    
    It's actually not documentation.
    
    Change-Id: I30c84abc9a31edb2f849dd2d6ff6d3129d87392d
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5474
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f4cffcc7ef52ccab3b08cb9be5bf16f046f5493a
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Aug 2 16:00:28 2013 +0530

    mount/fuse: do not forget the root inode
    
    In batch forgetting of inodes, nodeid should be checked and if it is for
    root, then it should not be sent forget.
    
    Change-Id: I99bd91ba70d8be4df88ddac005e38c449f4ed7d9
    BUG: 990744
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/5471
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 094b06c520498477804ef9ff8166ec0541d98c21
Author: Anand Avati <avati@redhat.com>
Date:   Thu Aug 22 12:34:26 2013 -0700

    bug-979365.t: fix wrong expectation of encountering fsync
    
    After the append-write detection patch, FSYNCs may or may not
    be issued depeneding on the order in which writes reach the
    server (in the presence of write-behind). Fix the test case
    to understand this non-deterministic behavior.
    
    Change-Id: I1dc3453a6dd4a12a66551948eb8311d789ac2ecf
    BUG: 927146
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5694
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 19fa9b4d6ee47e0f204b04abf9bc3adabbd9f0d4
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Aug 22 16:25:58 2013 +0200

    build: fix days and dates in the %changelog of the spec-file
    
    This prevents unneeded build warnings like:
    
        warning: bogus date in %changelog: Mon Apr 22 2008 ...
    
    Bug: 1000019
    Change-Id: Ie584e5faf5d04672186eada718aba7e71bd82b42
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5692
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 00a73eb528c39b2d6d0ee2fce83e82c1c47db619
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Aug 22 16:43:12 2013 +0530

    extras/hookscripts: Add default logfile for glusterfs vfs plugin.
    
    Glusterfs vfs plugin for samba makes call into gfapi which brings
    up complete client process stack of gluster. Not having default
    log file means not logging client process at all.
    
    This patch adds default logfile and loglevel for vfs plugin.
    
    Change-Id: Ie0fb6bbb445d6f3349fc35c713743094c0f08915
    BUG: 999910
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/5685
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 498a26b0307f2050e245c8d9330ba447c792d55d
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 21 17:34:02 2013 -0700

    io-cache: fix unsafe typcasting of pointer to uint64
    
    The typecast of pointer to uint64_t *, followed by setting of
    64bit in inode_ctx_get() results in memory corruption on 32bit
    system.
    
    Change-Id: I32fa3bf3b853ed2690a9b9a471099a59b9d7186a
    BUG: 997902
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5682
    Tested-by: Morten Johansen <morten@bzzt.no>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit 9cef2810909cf260762b7b9837c5a9fa67f8033c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jul 31 22:57:12 2013 +0530

    gfid-access: virtual access to filesystem through gfid path
    
    BUG: 952029
    Change-Id: I7405d473d369a4a951836eceda4faccbad19ce0e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5497
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit df9bfff8ea08176a3874fb0cdec8fd4b988d3ffa
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jul 31 23:58:04 2013 +0530

    core: changes to support gfid-access
    
    Change-Id: I38d2fdc47e4b805deafca6805e54807976ffdb7e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 952029
    Reviewed-on: http://review.gluster.org/5496
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 271804a26ca73c2eab706eff4b3be9a62bec2b13
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Aug 4 13:20:01 2013 +0530

    Revert "fuse: auxiliary gfid mount support"
    
    This reverts commit 4c0f4c8a89039b1fa1c9c015fb6f273268164c20.
    
    Conflicts:
    	xlators/mount/fuse/src/fuse-bridge.c
    
    For build issues added CREATE_MODE_KEY definition in:
            libglusterfs/src/glusterfs.h
    
    Change-Id: I8093c2a0b5349b01e1ee6206025edbdbee43055e
    BUG: 952029
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5495
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 51c6fa7a354826744de98a1c5c747955ae65850c
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Fri Jul 19 14:23:32 2013 +0000

    glusterd: add check in remove-brick start variant
    
    The 'start' variant of the remove-brick command only applies at the dht
    level wherein we can remove  all the bricks of a sub-volume (and remove
    multiple such sub-volumes) but not select bricks of it.
    
    This patch disallows removing individual replica bricks of multiple
    sub-volumes (i.e. reducing the replcia count of the volume) using
    remove-brick 'start'. The preferred method for such an operation is to use
    commit force.
    
    This patch also reverts the check to prevent removal of bricks from a
    replicate volume (commit 0d415f7)
    
    BUG: 961669
    Change-Id: I447ad27f73a0963b5e09fb317bf7267a7a5a6147
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5566
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cc8b149f34b3dc76a4ec094b822816852f6cfd5f
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Aug 20 18:25:09 2013 -0700

    tests: Avoid another 'grep' in ps output
    
    Previous fix at
    ----------------------------->
    764c42813df3de9659a1ab7b7356779d2e5d64e5
    <-----------------------------
    Was incomplete
    
    Change-Id: I6662168a7af078935a5cbcfae76ec40fc0c112b8
    BUG: 887098
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5672
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a232deaa82c561013d66322afdc1de1f526ecbd4
Author: Anand Avati <avati@redhat.com>
Date:   Sat Aug 10 16:10:26 2013 -0700

    md-cache: invalidate attributes on xattr update
    
    xattr update will result in at least ctime change. So invalidate
    attributes in xattr callback.
    
    Change-Id: Ie6e8f2fd9a11c56c27e78bd58c2ff1e1d6edce6e
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5641
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 41fa8da33435b8ba05a7eddbccddd96cde1aa762
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Aug 13 19:47:01 2013 +0530

    mount/fuse: save the basefd flags in the new fd
    
    Upon graph switch, the basefd's flags were not saved in the new fd created
    for the new graph upon which all the further requests for the open file
    would come. Thus posix was treating the fd as a read-only fd and was
    denying the write on the fds.
    
    Change-Id: I781b62b376a85d1a938c091559270c3f242f1a2a
    BUG: 998352
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/5601
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 317f2656225905794a26c454e8c22f30166107f2
Author: Bharata B Rao <bharata@linux.vnet.ibm.com>
Date:   Fri Aug 16 11:39:01 2013 +0530

    log: Fix logging to stderr
    
    This fix enables gluster clients like QEMU using glfs_set_logging()
    with "-" as logfile to see client side errors on stderr.
    
    Change-Id: I35f7b65460d1c03f910ceb3bad0a65677317e702
    Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
    Reviewed-on: http://review.gluster.org/5637
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3c9f3e642fd3ea81b9371eb1eec946882b1cb746
Author: Anand Avati <avati@redhat.com>
Date:   Thu Aug 15 13:53:52 2013 -0700

    glusterd: release big locks while doing mount
    
    Else things can deadlock in getspec v/s glusterd_do_mount()
    
    Change-Id: Ie70b43916e495c1c8f93e4ed0836c2fb7b0e1f1d
    BUG: 997576
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5636
    Tested-by: Joe Julian <joe@julianfamily.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e79be3d1655edb2b9f64a13e1fabae601c7d19e4
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Aug 7 12:25:07 2013 +0530

    glusterd: Try to start all bricks on 'start force'
    
    A volume would fail to start if any one of the bricks fails staging or
    fails to start, even with the 'force' option. With this patch, when the
    'force' option is given for a volume start, glusterd will continue and
    start other bricks even if one fails staging or starting.
    
    Also did a small fix in changelog, to prevent it crashing when it fails
    to init.
    
    Change-Id: I7efbd9ab13d12d69b0335ae54143fa17586f8f98
    BUG: 994375
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5510
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c12fccc4732df63273e8d013fd471e1c8f3b7d22
Author: Timothy Asir <tjeyasin@redhat.com>
Date:   Tue Apr 23 12:30:35 2013 +0530

    cli: Add server uuid into volume brick info xml
    
    Add server uuid as an attribute to the existing brick details in the
    volume info cli xml output.
    Currently, when a node has more than one ip, the oVirt-engine fails
    to map the corresponding server using the ip alone.
    If we get the host uuid along with brick details in volume info
    command it will be easy for ovirt-engine to find out the
    server and thereby we can avoid confusion in finding the server.
    
    Change-Id: I3c9c9acea80e10e0b2977477759d9af045e48959
    BUG: 955588
    Signed-off-by: Timothy Asir <tjeyasin@redhat.com>
    Reviewed-on: http://review.gluster.org/4875
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 764c42813df3de9659a1ab7b7356779d2e5d64e5
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Aug 14 15:44:33 2013 -0700

    tests: make sure to avoid 'grep' in ps output
    
    Change-Id: I48909facd2e3a2dc52a18e44d58c0e0fa2d96ec3
    BUG: 887098
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5631
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8cde114f65e7a08c9ca3637ff46b8b6cd6dc9426
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Sat Aug 10 20:49:12 2013 -0700

    glusterd: Move certain logs into 'DEBUG' level
    
    Confusing "Error" messages in logs can cause user panic
    and false positives - avoid them as necessary in future.
    
    Change-Id: I906c64eea879b19a8db099c89d1d7f874e5530db
    BUG: 995784
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5555
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2a195787746a6bfd3e1da6bf38c657ae0ccda24d
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon Aug 12 17:25:12 2013 +0530

    cluster/dht: Del GF_READDIR_SKIP_DIRS key from dict for first_up
    
    Currently, we sent GF_READDIR_SKIP_DIRS for all subvolumes if
    first_subvol != first_up_subvolume.
    
    Also first_up_subvolume can change with-in the life of a call and
    cbk. Saving the first_up_subvol in dht_local for checks.
    
    Change-Id: I6e369e63f29c9761993f2a66ed768c424bb44d27
    BUG: 996474
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5577
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bb1fb1e1614d2c1646e2d512779d723b66b2a766
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Aug 5 22:20:19 2013 +0530

    protocol/server: Relax lktable finodelk del_locker check
    
    Problem:
    Client xlator issues finodelk using anon-fd when the fd is not
    opened on the file. This can also happen between attempts to re-open
    the file after client disconnects. It can so happen that lock is taken
    using anon-fd and the file is now re-opened and unlock would come with
    re-opened fd. This will lead to leak in lk-table entry, which also
    holds reference to fd which leads to fd-leak on the brick.
    
    Fix:
    Don't check for fds to be equal for tracking finodelks.
    Since inodelk is identified by (gfid, connection, lk-owner)
    fd equality is not needed.
    
    Change-Id: I62152d84caef0b863c973845e618076d388e6848
    BUG: 993247
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5499
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3d509b1b5acfe55d003f0ae9b51486247226e16f
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 14 16:11:40 2013 -0700

    rfc.sh: Include BUG: header even in first run
    
    Set the commit hook before entiring editor mode. This fixes the
    error where rfc.sh after first clone does not set BUG: header
    
    Change-Id: Ic0e9f2d3f656bc81e29d35556022fbdff2f61225
    BUG: 764890
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5632

commit 1ea8ee6bc92ad887d47d3aff2404404681c4cfa9
Author: Bala.FA <barumuga@redhat.com>
Date:   Tue Aug 13 11:27:50 2013 +0530

    log: add logger.conf.example file
    
    This example file can be safely renamed as logger.conf to enable
    syslog logging
    
    Change-Id: If49dd6002a046915b2eca330b7a539f4fa1f94fa
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/5622
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fc82ae5ddf3b1821095de4188fead9a25bc24191
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Aug 9 17:21:56 2013 +0530

    log: add comments to rsyslog gluster configuration file
    
    Comments are added to rsyslog gluster configuration files to give
    clear meanings and example email alerting.
    
    Change-Id: I23577dc3b39bca89696c46ab6252dc5673d0803f
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/5621
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1d1daa234eac97554103da16a7d6090bc25e5294
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 7 04:16:52 2013 -0700

    cluster/afr: Add largest file is source policy
    
    For Write Once Read Many times type of work-load choosing largest
    file to be the source will always resolve fool-fool
    scenarios correctly. In other cases we fsync() the files and
    will have a reliable 'wise man'.
    
    Change-Id: Ic4dbea8d06db6d578fbcb866fb65ee2d066ac7ba
    BUG: 958118
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5519
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 1e49b3ac9b1019c742236be8db0ca8ec00750ae7
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Mon Jul 29 23:43:51 2013 +0530

    performance/write-behind: invoke request queue processing if
    we find fd marked bad while trying to fulfill lies.
    
    * flush was queued behind some unfulfilled write.
    * A previously wound write returned an error and hence fd was marked
      bad with corresponding error.
    * wb_fulfill_head (invocation probably rooted in wb_flush), before
      winding checks for failures of previous writes and since there was a
      failure, calls wb_head_done without even winding one request in head.
    * wb_head_done unrefs all the requests in list "head".
    * since flush was last operation on fd (and most likely last operation
      on inode itself), no one invokes wb_process_queue and flush is stuck
      in request queue for eternity.
    
    Change-Id: I3b5b114a1c401d477dd7ff64fb6119b43fda2d18
    BUG: 988642
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/5398
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8360037701788d49471cc0228fa873aa18382023
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 24 03:53:16 2013 -0700

    afr: treat appending writes as stable writes.
    
    Durability of appending writes is implicit in the file size. Therefore
    performing an explicit fsync() is unnecessary in such cases as self-heal
    can check for the size of file when pending changelog is not unambiguous.
    
    Change-Id: I05446180a91d20e0dbee5de5a7085b87d57f178a
    BUG: 927146
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5501
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0d756dc618c1a4b659a3531aec449506ce577f50
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Tue Aug 13 17:35:20 2013 -0700

    posix: Default value for `batch-fsync-delay-usec` should be '0'
    
    Also fixes for failing testcase `./tests/bugs/bug-888174.t`,
    which has been failing sporadically for many patches.
    
    Change-Id: Ic7d2c95da5d3126623cec403207afadd449bf950
    BUG: 927146
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5620
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a78f7dcddbc3d2048a184b7f4f45a63586eb5580
Author: Anand Avati <avati@redhat.com>
Date:   Fri Aug 9 11:12:29 2013 -0700

    libgfapi : Fix for hardlink creation on SMB mount
    
    Previously the inode of the hard link was left uninitialised hence
    glfs_loc_link() used to fail with invalid parameter.Since inode is
    same for both the files in hard link creation,   updated the inode
    field of hard link to be same as that of the original file.
    
    Original-author: susant palai <spalai@redhat.com>
    Change-Id: Ifd6439867d982524a7b48bf3f6add6e844b3c4c1
    BUG: 996063
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5576
    Tested-by: susant palai <spalai@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 528cbf0ef1b8cbabbab5141df69353d7cf9f59f5
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu Jun 13 14:51:46 2013 +0000

    glusterd: remove-brick:Allow simultaneous removal of multiple subvolumes.
    
    Currently, remove-brick supports removal of only one distributed
    stripe/ replica pair at a time. Fix it to support removal of multiple
    pairs. This is consistent with add-brick behaviour which supports adding
    multiple stripe/replica pairs simultaneously.
    
    Removal is successful irrespective of the order of the bricks given at
    the CLI, as long as the bricks are from the same subvolume(s).
    
    Change-Id: I7c11c1235ce07b124155978b9d48d0ea65396103
    BUG: 974007
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5210
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit e75071a5eee1a69caac4d0477f5458ddfe776f07
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Aug 9 17:21:56 2013 +0530

    log: add rsyslog gluster configuration file
    
    This patch comes with rsyslog gluster configuration file for fedora
    and rhel >= 6.  It disables syslog at rpm build time if targetted
    platform is rhel < 6 as there is no rsyslog support.
    
    Change-Id: I95c076874b6891ff08dee1b35980f95529fb0f37
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/5543
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e3f2d5fb1e8a12317959748eee15d4ec1f8f3fa6
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Aug 9 17:26:48 2013 +0530

    log: use /etc/glusterfs/logger.conf file for logging target
    
    This patch fixes to use /etc/glusterfs/logger.conf file instead of
    /var/lib/glusterd/logger.conf for logging target (whether to use
    syslog or not) at run time.
    
    Change-Id: Icb1de9ebfb7e529940e2aac970978ad70b34b213
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/5542
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4e63eafaed6073eab3d87c579e964fa5302f0d63
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Aug 9 16:51:11 2013 +0530

    log: set ident to openlog
    
    at syslog side, log message is identified by its properties like
    programname, pid, etc.  brick/mount processes need to be identified
    uniquely as they are different process of gluterfsd/glusterfs.  At
    rsyslog side, log separated by programname/app-name with pid works but
    bit hard to identify them in long run which process is for what
    brick/mount.
    
    This patch fixes by setting identity string at openlog() which sets
    programname/app-name as similar to old style log file prefixed by
    gluster, glusterd, glusterfs or glusterfsd
    
    Change-Id: Ia05068943fa67ae1663aaded1444cf84ea648db8
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/5541
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a1fe3d040a8c9b032cbcb5e831383628cddfa39a
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 7 16:04:23 2013 -0700

    cluster/afr: skip directory inspection when entry self-heal is off
    
    When user has explicitly configured to disable entry self-heal in the
    client, it is wrong to do the healing in opendir. So skip it. This
    is especially useful to reduce opendir() times after graph switches.
    
    Change-Id: Ic6eb9ff2334a5b8417f2f35410a366a536bad5df
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5528
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e0890b723519519b3a979940b982a0ea37d2daa3
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Aug 1 23:03:13 2013 -0700

    logging: [doc] Fix a typo
    
    /var/log/glusterd/logger.conf should be /var/lib/glusterd/logger.conf
    
    Change-Id: I3a4b19eb59d7acf83224fed01a5856565ffe1741
    BUG: 928648
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5466
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit ff38e3e0289439dd9e4521567bf1bfa9d184b5ef
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Aug 8 15:22:10 2013 +0530

    cluster/afr: Unwind frame on error in readdir[p]
    
    Change-Id: I5701bf115e0aa1adb4fb52f5418534910a2268d4
    BUG: 994959
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5531
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5fb1714c64660c69e51301f61b63e63931f85227
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Aug 7 09:11:48 2013 -0400

    build: sync glusterfs.spec.in with Fedora glusterfs.spec
    
    (this is the master branch)
    
    * add necessary requires
    * add -cli subpackage
    * fix other minor differences with Fedora glusterfs.spec
    
    Change-Id: Ifd535463a68cfd0793691e37148f411b95b41867
    BUG: 950083
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5522
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 993001dadf3b1706816b7762749a4c4426ac86df
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Aug 8 03:19:43 2013 +0530

    extras/hook-scripts: Don't add multiple entries in smb.conf
    
    When volume is force started, there may be entry in smb.conf
    for that volume. Always check for entry before adding one.
    
    Change-Id: I44f893174a993abaa31c24c1a81bb38a58617808
    BUG: 994727
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/5526
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 0f77e30c903e6f71f30dfd6165914a43998a164f
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jul 24 19:11:49 2013 +0000

    afr: check for non-zero call_count before doing a stack wind
    
    When one of the bricks of a 1x2 replicate volume is down,
    writes to the volume is causing a race between afr_flush_wrapper() and
    afr_flush_cbk(). The latter frees up the call_frame's local variables
    in the unwind, while the former accesses them in the for loop and
    sending a stack wind the second time. This causes the FUSE mount process
    (glusterfs) toa receive a SIGSEGV when the corresponding unwind is hit.
    
    This patch adds the call_count check which was removed when
    afr_flush_wrapper() was introduced in commit 29619b4e
    
    Change-Id: I87d12ef39ea61cc4c8244c7f895b7492b90a7042
    BUG: 988182
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5393
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1feaebfe0ae140ecafd5c37a0ce1bb5f0a1ac0cf
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 7 01:30:42 2013 -0700

    md-cache: fix xattr caching code in getxattr
    
    Bad condition check, fix it!
    
    Change-Id: I6e047de70f77d7b98b2ca771a467f14a76fd62fe
    BUG: 994392
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5513
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c6a555d1268c667b72728ffa58600fc0632465e4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Aug 6 17:40:05 2013 +0530

    features/locks: Convert old style metadata locks to new-style
    
    Problem:
    In 3.3, inode locks of both metadata and data are competing in same
    domain called data domain (old style). This coupled with eager-lock,
    delayed post-ops introduce delays for metadata operations like chmod,
    chown etc. To avoid this problem, inode locks for metadata ops are
    moved to different domain called metadata domain in 3.4 (new style).
    But when both 3.3 clients and 3.4 clients are present, 3.4 clients
    for metadata operations still need to take locks in "old style" so
    that proper synchronization happens across 3.3 and 3.4 clients. Only
    when all clients are >= 3.4 locks will be taken in "new style" for
    metadata locks. Because of this behavior as long as at least one 3.3
    client is present, delays will be perceived for doing metadata
    operations on all 3.4 clients while data operations are in
    progress (Ex: Untar will untar one file per sec).
    
    Fix:
    Make locks xlators translate old-style metadata locks to new-style
    metadata locks. Since upgrade process suggests upgrading servers
    first and then clients, this approach gives good results.
    
    Tests:
    1) Tested that old style metadata locks are converted to new style by
       locks xlator using gdb
    2) Tested that disconnects purge locks in meta-data domain as well
       using gdb and statedumps.
    3) Tested that untar performance is not hampered by meta-data and
       data operations.
    4) Had two mounts one with orthogonal-meta-data on and other with
       orthogonal-meta-data off ran chmod 777 <file> on one mount and
       chmod 555 <file> on the other mount in while loops when I took
       statedumps I saw that both the transports are taking lock on
       same domain with same range.
    
       18:49:30 :) ⚡ sudo grep -B1 "ACTIVE" /usr/local/var/run/gluster/home-gfs-r2_0.324.dump.*
       home-gfs-r2_0.324.dump.1375794971-lock-dump.domain.domain=r2-replicate-0:metadata
       home-gfs-r2_0.324.dump.1375794971:inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=9223372036854775806, len=0, pid = 7525, owner=78f9e652497f0000, transport=0x15ac9e0, , granted at Tue Aug  6 18:46:11 2013
    
       home-gfs-r2_0.324.dump.1375795051-lock-dump.domain.domain=r2-replicate-0:metadata
       home-gfs-r2_0.324.dump.1375795051:inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=9223372036854775806, len=0, pid = 8879, owner=0019cc3cad7f0000, transport=0x158f580, , granted at Tue Aug  6 18:47:31 2013
    
    Change-Id: I268df4efd93a377a0c73fbc59b739ef12a7a8bb6
    BUG: 993981
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5503
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 12f485982b41eec542673d74510e7ed8ef5e1fca
Author: M S Vishwanath Bhat <vbhat@redhat.com>
Date:   Fri Aug 2 16:15:45 2013 +0530

    Correcting a log message in glusterd-geo-rep.c
    
    Change-Id: I4352f513fc5616daa20e9a4ad51a63fb13a27dff
    BUG: 847839
    Signed-off-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Reviewed-on: http://review.gluster.org/5472
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d2338a18bafaf9037cb2c1a9249771a523690495
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 18:18:19 2013 +0200

    doc: Convert adding a fop howto to markdown
    
    Change-Id: Ia0a9ad228dcf69f40befc58fff7a56fffcfe915b
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5487
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit b2122ea4983c8b59802c8f2a346fe5f44d967042
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 15:37:33 2013 +0200

    doc: Convert the posix translator documentation to markdown
    
    Change-Id: I6b6c3b2063c81e8799c3273434119dd9bff1be79
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5486
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit f20af8251768c7f52c23b6bb8ebf19751dcf30e6
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 18:07:55 2013 +0200

    doc: The lock-ahead translator is not in tree, drop docs
    
    Change-Id: Idda32338af416dc085c48ff023eeacf2397b65fd
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5485
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 9b8b4dcd0bf595a0f886783ec6db38811ad48d24
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 18:18:08 2013 +0200

    doc: Convert the afr translator documentation to markdown
    
    Change-Id: I328986812df7adc849fa11b53ae483c2cd0825e8
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5484
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit aefabb62a9a0a0e63412e4fab6cd47f76e9a4619
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 17:31:07 2013 +0200

    doc: Remove the bdb translator documentation
    
    The translator was removed in ea08bf886732d9680f2d6de19f3d68908a55143b.
    
    Change-Id: I3d124be9e3962a54f0ab0247cfd4867b815f4a17
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5483
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit bf34745d800171aaef2ee53a404d4de57e293ce5
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 18:17:50 2013 +0200

    doc: Convert the write-behind translator documentation to markdown
    
    Change-Id: I213e230d283cd43bd1c2b2948882ab36f9170608
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5482
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 78725a148eda42ee9e48677b8df131099389cacc
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Thu Aug 1 15:39:00 2013 +0200

    doc: Re-format the translator tutorial
    
    Adjutst whitespace so that things don't overflow in PDF.
    
    Change-Id: Ic75abccbe744aac327b1c6311afb4c13271a723d
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5481
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit a7564731e30312047f0300760c248f86c1080d84
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Thu Aug 1 15:13:01 2013 +0200

    doc: Import Jeff Darcy's translator tutorial
    
    It's way better than what we have currently. It's the original text from Jeff's
    blog [1][2][3][4], unedited aside from the title, so that the content can be
    properly attributed.
    
    [1] http://hekafs.org/index.php/2011/11/translator-101-class-1-setting-the-stage/
    [2] http://hekafs.org/index.php/2011/11/translator-101-lesson-2-init-fini-and-private-context/
    [3] http://hekafs.org/index.php/2011/11/translator-101-lesson-3-this-time-for-real/
    [4] http://hekafs.org/index.php/2011/11/translator-101-lesson-4-debugging-a-translator/
    
    Original-Author: Jeff Darcy <jdarcy@redhat.com>
    
    Necessary editing will follow:
    * Nicer endings/openings of the subsections, as they are no longer separate articles
    * Wrap lines in terminal outputs so that they render nicely in PDF
    * Remove HeksFS references
    * Remove first person fear of developer wrath for manual creation of a volfile
    
    Change-Id: Ie9bb537b5817e8fa575ec0c66a58c48e6584698e
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5480
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit d5a4e34f02415cfcc7637efaa1e135305a7da230
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 15:37:33 2013 +0200

    doc: Convert the coding standards to markdown
    
    Change-Id: I5f3bec7b86ce31beb7459a27dc0f4ba39c6d9610
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5479
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit edb10e99d31516e00ef1822375375f676a12bf8a
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 10:15:28 2013 +0200

    doc: Drop corrupted and unused file
    
    Change-Id: Ib220f9264ac941e87a9eb0998775a1b5507c510f
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5478
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit bf2ece715894cbeb4b28a6d036013b0147a0f542
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 09:55:57 2013 +0200

    doc: Get rid of weird quoting
    
    pandoc: Error producing PDF from TeX source.
    ! Package inputenc Error: Unicode char \u8:‟ not set up for use with LaTeX.
    
    See the inputenc package documentation for explanation.
    Type  H <return>  for immediate help.
     ...
    
    l.6216 ... the objects access rights to "public‟
    
    Change-Id: I23428930d167064b7c5790eea09daedbef06153a
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5477
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 242f4d8e33bf266bd95eed3a3e72a836562cfd56
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 09:35:17 2013 +0200

    doc: Rename architectural diagram
    
    It should not be specific to old gluster version anyway and the dot in name
    causes trouble to pandoc/LaTeX:
    
    pandoc: Error producing PDF from TeX source.
    ! LaTeX Error: Unknown graphics extension: .2_Architecture.png.
    
    See the LaTeX manual or LaTeX Companion for explanation.
    Type  H <return>  for immediate help.
     ...
    
    l.98 ...ages/640px-GlusterFS_3.2_Architecture.png}
    
    Change-Id: I9d222a1628e1c14b004c059733fabd7b70c86f26
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5476
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 375f3b4164dcfe7aab7ffb747dc178079c17976e
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 08:58:41 2013 +0200

    doc: Drop volfiles from documentation tree
    
    They're mostly useless.
    
    Change-Id: Ib5db6f4439fee16e461afc0b0cd3b71c717a19c6
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5475
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 76380bcc17a5dd44b634057d6c2a8dd56d99d4aa
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Jul 31 08:52:45 2013 +0200

    doc: Drop the docbook admin guide
    
    It has been converted to Markdown.
    
    Change-Id: Idc4b2de7e79aa955d1d3cac96a9ee653ccf9fbd9
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5473
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 71d69e4331d7abff910e1f013bb7b2cb9d7f630c
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Wed Jul 24 14:49:58 2013 -0700

    Add switch and nufa options to 'gluster cli'
    
    Change-Id: Ic3c43291e0e1ead0d89c0436e8d70aa5dee2f543
    BUG: 924488
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5391
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ed67d15fe174617c013078c37c4c87fdb119c2a4
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Jul 18 18:43:37 2013 -0700

    glusterfsd: Cleanup in set_log_file_path()
    
    1. Remove un-necessary tmp_ptr - volfile_id is true if volfile_server
       is
    2. port is not '1' as default instead its GF_DEFAULT_BASE_PORT
    
    Change-Id: I3eab3f6ccce4b84724d25421002d2f25925ca72d
    BUG: 846194
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5344
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b777fc478d74b2582671fef7cb2c55206432c2bb
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Wed Jul 24 18:44:42 2013 +0000

    fuse: fix memory leak in fuse_getxattr()
    
    The fuse_getxattr() function was not freeing fuse_state_t resulting in a
    memory leak. As a result, when continuous writes (run dd command in a loop)
    were done from a FUSE mount point, the OOM killer killed the client
    process (glusterfs).
    
    Change-Id: I6ded1a4c25d26ceab0cb3b89ac81066cb51343ec
    BUG: 988182
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5392
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 572f5f0a85c97a4f90a33be87b96368a0d7e7a8e
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jul 10 18:10:49 2013 +0530

    cli,glusterd: Fix when tasks are shown in 'volume status'
    
    Asynchronous tasks are shown in 'volume status' only for a normal volume
    status request for either all volumes or a single volume.
    
    Change-Id: I9d47101511776a179d213598782ca0bbdf32b8c2
    BUG: 888752
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5308
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fbc543633525865b33ff0a156090006c5fdd1ab3
Author: Brian Foster <bfoster@redhat.com>
Date:   Fri Aug 2 13:07:33 2013 -0400

    fuse: sync fuse_kernel.h from linux 3.11.0(-rc3) header
    
    The linux 3.11 fuse kernel header supports up through version 7.22.
    Gluster has incrementally supported versions up to 7.22. This is a
    hard sync of the most recent kernel header to resolve various,
    minor descrepencies and facilitate updates going forward. The
    following changes are included:
    
    - Re-typed data structure definitions.
    - Missing comments and init flag definitions (i.e., splice).
    - Code format and whitespace differences.
    
    No functional changes are included.
    
    BUG: 990744
    Change-Id: I86921ef7be56d31bab332cf8589262c2b9348221
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5490
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dc72dd5a7637c778f345df962f63aaee509d0e12
Author: Brian Foster <bfoster@redhat.com>
Date:   Fri Aug 2 13:07:17 2013 -0400

    fuse-bridge: update to protocol minor version 22
    
    7.17
    - Distinguishes between POSIX and BSD locking support via a
      separate BSD locking support init flag. Older protocol versions
      (since BSD support was added) export both types of locking
      requests if FUSE_POSIX_LOCKS is specified. Gluster sets this
      flag, so set FUSE_FLOCK_LOCKS as well on kernels that support
      version 17 or newer.
    
    7.18
    - Adds ioctl() support for directories (and the associated
      FUSE_IOCTL_DIR flag). Gluster does not support the ioctl
      request, so no changes are required. Update the header.
    - Adds support for the delete notification to allow a filesystem
      to inform the kernel of a deleted inode. No gluster changes
      required.
    
    7.19
    - Adds support for the fallocate request. Gluster already supports
      fallocate and includes the request opcode definition and data
      structure. Update the header version number.
    
    7.20
    - Adds the FUSE_AUTO_INVAL_DATA init flag to enable attribute
      updates on reads and automatic cache invalidation on mtime
      changes. Behavior does not change unless the init flag is
      specified, no gluster changes required. Update header.
    
    7.21
    - Adds readdirplus support and updates the poll request to include
      events. Gluster already supports readdirplus and includes the
      relevant data structures. Poll is not supported, so no changes
      are required. Update the header with some missing
      READDIRPLUS_AUTO bits.
    
    7.22
    - Adds real asynchronous direct I/O support. Gluster already
      supports/enables the associated bit (FUSE_ASYNC_DIO), no further
      changes are required. Update the header.
    
    BUG: 990744
    Change-Id: Idf6fd75bbd48189587e548f7624626f9a75309e8
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5489
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8c1304b03542eefbbff82014827fc782c3c3584f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Aug 3 08:27:27 2013 +0530

    performance/open-behind: Fix fd-leaks in unlink, rename
    
    Change-Id: Ia8d4bed7ccd316a83c397b53b9c1b1806024f83e
    BUG: 991622
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5493
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a482e4220a6c9fe2909f9d5f1b484f68deecec64
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jul 30 14:00:46 2013 -0400

    build: sync glusterfs.spec.in with Fedora glusterfs.spec
    
    (this is the master branch)
    
    * Sync with latest Fedora updates
    * add glusterfs-libs RPM for RHEL6.5 oVirt/qemu-kvm, see BZ 916645
    
    BUG: 950083
    Change-Id: If5816f9b6a9478f6663c1de4d14a9f8341da9e84
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5455
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3af61d6758bc41e7c461d9d54f0caf872870329c
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jul 24 18:34:38 2013 +0530

    glusterd: Use volume op-versions during volgen
    
    Instead of using the cluster op-version, volume op-version is used to
    enable open-behind during volgen. For doing this, the volume op-versions
    are updated before regenerating the volfiles.
    
    Change-Id: I675bb549bf7c7c0279030dca698fb530781addc6
    BUG: 990830
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5385
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 36b102645ab66d141dcc831e67caa78966d45419
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 30 18:29:15 2013 +0530

    cluster/afr: Disable eager-lock if open-fd-count > 1
    
    Lets say mount1 has eager-lock(full-lock) and after the eager-lock
    is taken mount2 opened the same file, it won't be able to
    perform any data operations until mount1 releases eager-lock.
    To avoid such scenario do not enable eager-lock for transaction
    if open-fd-count is > 1. Delaying of changelog piggybacking is
    avoided in this situation.
    
    Change-Id: I51b45d6a7c216a78860aff0265a0b8dabc6423a5
    BUG: 910217
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5432
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: venkatesh somyajulu <vsomyaju@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c95db3046c672473611d9ac0ab6cd93bd8211347
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Mar 15 10:34:45 2013 +0100

    store: Add (un)locking functionality
    
    Some configuration/cache files (like the NFS rmtab) can be stored on
    a GlusterFS volume and be used by multiple storage servers. This
    requires suitable locking for the gf_store_handle_t structure. Introduce
    gf_store_lock() and gf_store_unlock() for this purpose. The
    gf_store_locked_local() function can be used to check if the
    gf_store_handle_t has been locked by the current process.
    
    This change also includes an unrelated correction where a FILE* was
    getting leaked. Krishnan Parthasarathi identified this while reviewing
    the new locking functionality.
    
    Change-Id: I431b7510801841d4bad64480b4bb99d87e2ad347
    BUG: 904065
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4677
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 423aa0d57a031e865374d18cdcc489273317d785
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 30 12:28:47 2013 +0530

    storage/posix: Enable Open-fd-count query in writev
    
    Change-Id: I86bdf865730416150c10617dcbad5c037579acde
    BUG: 910217
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5433
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1ece79c84c0306d38cb42cfa947dbc387af3ad0
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Jul 29 11:18:49 2013 -0400

    performance/io-threads: fix potential use after free crash
    
    do_iot_schedule() enqueues the stub and kicks the worker thread.
    The stub is eventually destroyed after it has been resumed and thus
    unsafe to access after being enqueued.
    
    Though likely difficult to reproduce in a real deployment, a crash
    is reproducible by running a smallfile benchmark on a replica 2
    volume on a single vm. Reorder the debug log message prior to the
    do_iot_schedule() call to avoid the crash.
    
    BUG: 989579
    Change-Id: Ifc6502c02ae455c959a90ff1ca62a690e31ceafb
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5418
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bc9cf5ba83dffbc2fb5a6821a6f40e6acff59897
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Jul 31 17:55:03 2013 -0400

    fuse-bridge: update to fuse protocol minor version 16 (Linux)
    
    7.14
    - Splice write support to fuse device node. No gluster changes
      required besides header update.
    
    7.15
    - Store/retrieve notification support. No gluster changes
      required besides header update.
    
    7.16
    - BATCH_FORGET request support. Implement a handler for
      BATCH_FORGET requests and update the header.
    - Updated ioctl() ABI. No gluster changes required besides
      header update.
    
    BUG: 990744
    Change-Id: If3061a720ba566ee6731ad8b77cdc665d8fbf781
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5449
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6235e8e956ce6d72c88ddb3ad81c0842ee4d089c
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Thu Aug 1 12:55:51 2013 +0530

    nfs: Fix for NFS crash during blocking NLM call.
    
    Bug 990887: During a blocking NLM call NFS server is crashing.
    
    Cause: When nlm4_establish_callback function is called from nlm4svc_send_granted the cs->req->trans
    pointer is NULL. Thus using this pointer will result in a crash. Whereas cs->trans points to a
    valid transport object. NLM should use cs->trans instead of cs->req->trans.
    
    Fix: Replaced cs->req->trans with cs->trans.
    
    Change-Id: I425e48e0aafc9a6c130912edf2e801d8c4c9472d
    BUG: 990887
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/5452
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ee98605f961c82a8f76ece4fae228bf4ddfed4c4
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 8 16:49:34 2013 +0530

    build: Better configure control & messages for xml output
    
    Users were not given a correct indication to whether xml output was
    going to be built on running configure as the only information was lost
    in the checks output. This would lead to conditions where the user would
    assume gluster was compiled with xml output, when it wasn't the case.
    
    With this change, a new line is added to the end of the configure output
    which indicates if xml output is being built or not. Also, a new
    configure flag, '--disable-xml-output', has been introduced which can be
    used to explicitly disable xml outpu from being built.
    
    Change-Id: Ie80ba0372b4c3967a836769c61b60263c8e5e350
    BUG: 947226
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4793
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 16061c0d0f681117a53895d309e3a09b38f673e2
Author: Tiziano Müller <tiziano.mueller@stepping-stone.ch>
Date:   Wed Jul 31 18:04:29 2013 +0200

    Fix broken parallel install
    
    There is an automake bug when using _LTLIBRARIES, breaking parallel
    `make install` (see http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7328)
    
    Change-Id: I06aea1dc4c3e6cb0ae9aee5a04dd61881c8b6a7e
    BUG: 981888
    Signed-off-by: Tiziano Müller <tiziano.mueller@stepping-stone.ch>
    Reviewed-on: http://review.gluster.org/5448
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 394055e31f3c90701336c84aafa7d3ab1e313c65
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jul 22 01:26:43 2013 -0700

    dht: make linkfile creation mode explicitly get set
    
    Because of posix default_acl on parent directory, the mode
    of linkfile can get masked with the mode in the default acl.
    
    This breaks DHT integrity. So let the mode get explicitly reset
    after mknod().
    
    Change-Id: Ia7328e1ee7b4430bda308f9da293dba78405e081
    BUG: 990410
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5440
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit dfedfec3593ca0fc026d8a094916824e1b90e60b
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jul 22 10:02:34 2013 -0700

    gfapi: perform open() on pre-existing inode in glfs_creat()
    
    Performing syncop_create() on a pre-existing file can result
    in opening the linkfile if DHT has a linkfile for the file.
    This is because dht_create() will perform the op on the
    hashed_subvol() and overwrite the layout in dht_create_cbk.
    
    Change-Id: I7a0db56921ec9fc3e278e0418db3b967f81e5598
    BUG: 990410
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5447
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 691b973704b4ba511b295ee6f8baf1c4a1d8d89c
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Jul 31 19:09:52 2013 +0530

    cluster/dht: Re-initialize skipped file count in glusterd
    
    Change-Id: I42d08b3a6a7a3839f5e9953e1f83959222c080f8
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    BUG: 989846
    Reviewed-on: http://review.gluster.org/5446
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d90b46a23a523720f4e40de993ca61ff0ba43617
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Jul 29 19:05:50 2013 +0530

    glusterd : Checking session created or not in case of geo-rep stop
    
    Performing statefile check in case of geo-rep stop, so as to provide
    proper error message in case session is not created.
    
    However in case of geo-rep stop force, we allow the command to succeed
    even in case that the session is not created, because the stop command
    is a failsafe command to stop running geo-rep sessions on any nodes.
    
    Change-Id: I2b6a0253de977633606c422cbbc9e37cede9a268
    BUG: 989541
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5417
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 031b69fc7b2f26d07113aabec95662816adfad86
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Jul 26 21:45:22 2013 +0530

    glusterd : initiating gsyncd restart during add-brick
    
    During add-brick, when a new brick is added in one of the
    nodes that was already a part of the existing volume, and
    gsyncd was already running on that node, then all gsyncd
    processes running on that node, for that particular master
    and any slave sessions will be restarted
    
    If a new brick is added in a new node, then after adding the
    brick, the user has to perform the following steps:
    
    1. gluster system:: execute gsec_create
    2. gluster volume geo-replication <master-vol> <slave-vol> create push-pem force
    3. gluster volume geo-replication <master-vol> <slave-vol> start force
    
    Change-Id: I4b9633e176c80e4a7cf33f42ebfa47ab8fc283f1
    BUG: 989532
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5416
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a960f929f341e7e56687227ef23b315a57780314
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jul 29 23:27:03 2013 +0530

    mount.glusterfs: remove use of LD_LIBRARY_PATH
    
    BUG: 989858
    Change-Id: Id7c3929a179e151b6d60d3382bd5310187bb2aa6
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/5423
    Reviewed-by: Bala FA <barumuga@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 21d032bf052957b50043f5f3775903d9d7f029c3
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jul 22 01:15:21 2013 -0700

    gfapi: fix glfs_readlink()
    
    glfs_readlink() is supposed to memcpy the buffer pointer
    returned by syncop_readlink(). Fix it.
    
    Change-Id: I5936b07abbd93cf02b354233dc60f6623e30a38b
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5439
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>

commit ac2cd684c2d8fa4a66800a6cc98f6c5c562b4b7f
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Jul 30 17:22:58 2013 +0530

    cluster/dht: Fix non-regular file ownership during rebalance
    
    Currently non-regular files were created as root:root, and
    their ownership never healed during rebalance process.
    
    Also, in dht_linkfile_attr_heal, we have to heal the linkfiles
    as default, as currently linkfiles are created as root:root.
    
    That check existed, as earlier linkfiles were created as
    frame->root->uid/gid
    
    Change-Id: I6cd88361b81bdd500e15bc47b623f5db8eec88e9
    BUG: 990154
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5434
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fd9a9ad14ba0abba907cbf52c51ee17738014232
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Jul 30 23:22:24 2013 +0530

    mgmt/glusterd: Fix a minor typo.
    
    Thanks to Patrick Matthäi <pmatthaei@debian.org> for the patch.
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    
    Change-Id: I59da74298894ccc2ab30967ffe44cc844aa73f82
    BUG: 814534
    Reviewed-on: http://review.gluster.org/5436
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 177f32e5b0d73336b2d5bde08bafff186b65e211
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 29 14:44:40 2013 +0530

    cluster/afr: Print self-heal log when self-heal succeeds
    
    Change-Id: I95e47e589419dc6a032cbd8ba01964b6c176c2d5
    BUG: 927146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5408
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit acf8cfdf698aa3ebe42ed55bba8be4f85b751c29
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Jun 20 14:06:04 2013 +0530

    Revert "storage/posix: Remove the interim fix that handles the gfid race"
    
    This reverts commit 97807e75956a2d240282bc64fab1b71762de0546.
    
    In a distribute or distribute-replica volume, this fix is required to prevent
    gfid mis-match due to race issues.
    
    test script bug-767585-gfid.t  needs a sleep of 2, cause after setting backend
    gfid directly, we try to heal, and with this fix, we do not allow setxattr of
    gfid within creation of 1 second if not created by itself
    
    Change-Id: Ie3f4b385416889fd5de444638a64a7eaaf24cd60
    BUG: 951195
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5240
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit e306698b00d2d3e736cbc97a1383bfb5d3724796
Author: shishir gowda <sgowda@redhat.com>
Date:   Fri Jul 26 11:59:12 2013 +0530

    cluster/dht: Treat migration failures due to space constraints as skipped
    
    Currently rebalance/remove-brick op's display migration failed count even
    for files which failed due to space issues (not enough space for file, or
    migration leading to cluster imbalance)
    
    These will now be counted as skipped, and rebalance/remove-brick status
    will display the additional counter
    
    Change-Id: I674904d380b5f8300e9ca9e6af557c3d30d6cff4
    BUG: 989846
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5399
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7e6432015afd758ca3fd9e32d3e62b29935b0874
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jul 30 18:22:48 2013 +0200

    build: use -Werror=implicit-function-declaration to detect build issues
    
    There have been review requests that include a call to a non-existent
    function. These problems should be detected as early as possible,
    preferably before (automated) regression tests.
    
    Bug: 990243
    Change-Id: Idcf4d27f45a1a6177105d02a039363702eb8e3b9
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5435
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0bbdfa3d403a90fa0f30e0e5bd56644c875c12c1
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Jul 30 12:29:35 2013 +0530

    api: Avoid a NULL deref in glfs_open().
    
    Change-Id: I23e9fabcb8a430bcd44595ca31460c54d7bd4a39
    BUG: 953694
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5426
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 04536e53082cdff5cd10a804502347ee83490c81
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Sep 18 14:07:40 2012 -0400

    libglusterfs/client_t client_t implementation, phase 1
    
    Implementation of client_t
    
    The feature page for client_t is at
    http://www.gluster.org/community/documentation/index.php/Planning34/client_t
    
    In addition to adding libglusterfs/client_t.[ch] it also extracts/moves
    the locktable functionality from xlators/protocol/server to libglusterfs,
    where it is used; thus it may now be shared by other xlators too.
    
    This patch is large as it is. Hooking up the state dump is left to do
    in phase 2 of this patch set.
    
    (N.B. this change/patch-set supercedes previous change 3689, which was
    corrupted during a rebase. That change will be abandoned.)
    
    BUG: 849630
    Change-Id: I1433743190630a6d8119a72b81439c0c4c990340
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/3957
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit c2064eff8919af6afdb38dbdb059bfc099e0afd9
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Jul 29 15:28:44 2013 +0530

    cluster/dht: Allow non-local clients to function with nufa volumes.
    
    nufa fails to init if a local brick is not found as of today.
    With this patch, if a local brick is not found, nufa switches
    over to dht mode of operations.
    
    Change-Id: I50ac1af37621b1e776c8c00a772b8e3dfb3691df
    BUG: 980838
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5414
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 355ff31dff9713319a1d2663e5f8d3d386c1b938
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jul 25 14:58:46 2013 +0530

    glusterd: Fixing create force issues while it returned true everytime.
    
    Now geo-rep create force will return true if a node is down, and log an
    appropriate message. It will also return true with an appropriate log
    message if the slave verification fails.
    
    However it will not return true if the config file is deleted, ot corrupted,
    so as not to get the state_file's path. It will also fail if the slave url
    is invalid. If the push-pem option is given and
    /var/lib/glusterd/geo-replication/common_secret.pem.pub is not present, then
    also the create force command will fail.
    
    Change-Id: Ie7532a0884ddf9c3008bd30832d171d5b53b540e
    BUG: 988314
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5405
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ebbe623fe44dddc9318067698bf3796035265997
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 29 12:36:10 2013 +0530

    libglusterfs: Fix compilation warning
    
    Change-Id: Ibba7a6fd3119c85c78cb12628d85c7f9210e6b8c
    BUG: 928648
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5412
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa70c0bba081b7a56a3894c5454a78b27753bdff
Author: Anand Avati <avati@redhat.com>
Date:   Sun Jul 21 00:43:18 2013 -0700

    gfapi: handle failures in graph switches
    
    A graph switch failure can potentially result in NULL returned
    for glfs_active_subvol(). Handle this gracefully in glfs_subvol_done()
    
    Change-Id: I6adbd878c354b9ed2314fc71cea4671792efa0a4
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5407
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c6b8143b9f61f59326563dd5274f9d1849577cef
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Feb 27 16:55:09 2013 +0530

    cli : Display error messages if virt file has been deleted or is invalid.
    
    "gluster volume set <VOLNAME> group virt" will display error message
    if virt file is deleted or is invalid.
    
    Change-Id: Icb202b6a445597fcd9a3dcef8001891f2601a115
    BUG: 916127
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4586
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 67cd7b9274b076750f768cd0994e58e36199f2b5
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Thu Jul 25 17:27:52 2013 +0200

    glusterfsd: TRACE is a valid log level too
    
    Change-Id: Ia17513817f8f6d7a4a8732fc0cfee21f16a75fac
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5401
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d16cdf141d449246b0b58870bd3d82efe232e5db
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Apr 23 00:58:22 2013 +0530

    cli, glusterd: Cleanup logging of bd op commands.
    
    This patch prevents messages of the form "bd op: %s : SUCCESS"
    from being logged in .cmd_log_history.
    
    Change-Id: Iebeb7e26d409bf99b9c8df0a5c1c5a5d30d78a61
    BUG: 823081
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4871
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: M. Mohan Kumar <mohan@in.ibm.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 412940c56e203b16ebf027fe5b9cbf58cd3a144e
Author: Anand Avati <avati@redhat.com>
Date:   Sat Jul 20 15:04:48 2013 -0700

    tests: fix test script to turn on write-behind
    
    Change-Id: I8a3ddc8183355236ff7725229441e27bbf8188e3
    BUG: 927146
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5406
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 62ba019c5ce096ae1d470f88074028ccc61b015c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jun 27 02:24:36 2013 +0530

    mgmt/glusterd: let each brick write the valgrind o/p to different file
    
    Till now all the brick processes were writing the valgrind information
    to the same log file.
    
    Change-Id: I0251c943935e2901b729c71f21d0677edb9f6867
    BUG: 922877
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/5394
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2ebbabbe45c38ca16fa9d5f2b113954783e36ff8
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Thu Jul 25 17:16:13 2013 +0200

    fuse-bridge: Cure some unhealthy format strings
    
    Mostly sign errors:
    
    Before:
    
    0-glusterfs-fuse: 74: CREATE() /FILE => 0x1e9de9c (ino=-7793743383831318294)
    0-glusterfs-fuse: 76: SETATTR() /FILE => -7793743383831318294
    ...
    
    After:
    
    0-glusterfs-fuse: 109: CREATE() /FILE => 0x267fe9c (ino=12597207469970374167)
    0-glusterfs-fuse: 111: SETATTR() /FILE => 12597207469970374167
    ...
    
    Change-Id: I422d2397fe071b0ac155b8c7e8a40a3365d6d58c
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/5402
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5757ed2727990fd2c3aaff420003638f1eec6b92
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jul 10 17:32:41 2013 +0530

    glusterd/cli changes for distributed geo-rep
    
    Commands:
    gluster system:: execute gsec_create
    gluster volume geo-rep <master> <slave-url> create [push-pem] [force]
    gluster volume geo-rep <master> <slave-url> start [force]
    gluster volume geo-rep <master> <slave-url> stop [force]
    gluster volume geo-rep <master> <slave-url> delete
    gluster volume geo-rep <master> <slave-url> config
    gluster volume geo-rep <master> <slave-url> status
    
    The geo-replication is distributed. The session will be created, and
    gsyncd will be spawned on all relevant nodes, instead of only one
    node.
    
    geo-rep: Collecting status detail related data
    
    Added persistent store for saving information about
    TotalFilesSynced, TotalSyncTime, TotalBytesSynced
    
    Changes in the status information in socket:
    Existing(Ex):
    FilesSynced=2;BytesSynced=2507;Uptime=00:26:01;
    
    New(Ex):
    FilesSynced=2;BytesSynced=2507;Uptime=00:26:01;SyncTime=0.69978;
    TotalSyncTime=2.890044;TotalFilesSynced=6;TotalBytesSynced=143640;
    
    Persistent details stored in
    /var/lib/glusterd/geo-replication/${mastervol}/${eSlave}-detail.status
    
    Change-Id: I1db7fc13ffca2e415c05200b0109b1254067f111
    BUG: 847839
    Original Author: Avra Sengupta <asengupt@redhat.com>
    Original Author: Venky Shankar <vshankar@redhat.com>
    Original Author: Aravinda VK <avishwan@redhat.com>
    Original Author: Amar Tumballi <amarts@redhat.com>
    Original Author: Csaba Henk <csaba@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5132
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit b13c483dca20e4015b958f8959328e665a357f60
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Sat Jun 1 16:17:57 2013 +0530

    gsyncd: distribute the crawling load
    
    * also consume changelog for change detection.
    * Status fixes
    * Use new libgfchangelog done API
    * process (and sync) one changelog at a time
    
    Change-Id: I24891615bb762e0741b1819ddfdef8802326cb16
    BUG: 847839
    Original Author: Csaba Henk <csaba@redhat.com>
    Original Author: Aravinda VK <avishwan@redhat.com>
    Original Author: Venky Shankar <vshankar@redhat.com>
    Original Author: Amar Tumballi <amarts@redhat.com>
    Original Author: Avra Sengupta <asengupt@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5131
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 4944fc943efc41df1841e4e559180171f6541112
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 26 16:12:11 2013 +0530

    cluster/afr: Handle REPLICATE_TRASH_DIR from old bricks
    
    Change-Id: Ib99f79d3fa607c818dbc62006516480f598d8add
    BUG: 886998
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4640
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 115f6a679ba0117a5757fe69f8f326d633c38fbf
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Jul 25 20:10:55 2013 -0700

    build: Add '--without bd' to disable 'bd' xlator rpmbuild
    
    Change-Id: I9f1774788362d8250693002318b617cd16e1a668
    BUG: 950083
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5397
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Bala FA <barumuga@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e9c583598b8ad58bbda15759067ff57eca619e95
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Jul 25 17:12:21 2013 +0530

    doc: Create a features folder.
    
    Moved rdma and bd documents to doc/features. Added a new
    document on rebalance.
    
    Change-Id: I04269202adc9605754fc29876433c88480b822a3
    BUG: 811311
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5395
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 131d78dd36bac795d50fee3b04969b5ea9cb613c
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 24 00:01:19 2013 +0530

    features/changelog: fixes when enabling changelog
    
    Other enhancements being:
          * ignore fops made by rebalance
          * ignore internally triggered fops
    
    BUG: 987734
    Change-Id: I7dd164ae3c209fdb8ec43a27e67b8846f937c93b
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5380
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 333872c8ad93cb9da682d27e89bc2a58cf86aba0
Author: Harshavardhana <harsha@harshavardhana.net>
Date:   Thu Jul 18 20:52:36 2013 -0700

    glusterfsd: is_mgmt_rpc_reconnect should not be `char` but gf_boolean_t
    
    Change-Id: I35c4dc040ebb5e926c7f54d823d1c81b1228bd4f
    BUG: 763046
    Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
    Reviewed-on: http://review.gluster.org/5345
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5fbee7cdad349f514ec6a1adc306bad6bb031297
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 5 23:50:52 2013 +0530

    write-behind: preserve error returned as-is
    
    Change-Id: Ib766403774c1323e0bbddafedeaa47e7fa3a59fa
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 987415
    Reviewed-on: http://review.gluster.org/5296
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7cfef511898ba2d555256e6d7f53bd97ed69e6e0
Author: Anand Avati <avati@redhat.com>
Date:   Thu May 2 23:36:01 2013 -0700

    core: increase the auxillary group limit to 65536
    
    Make the allocation of groups dynamic and increase the limit
    to 65536.
    
    Change-Id: I702364ff460e3a982e44ccbcb3e337cac9c2df51
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5111
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e45e0037f6df6a0fab846a83fb2c99bb09417cf4
Author: susant <spalai@redhat.com>
Date:   Wed Jul 24 14:11:55 2013 +0530

    cli :remove-brick process output leads to ambiguity
    
    The output of remove-brick  status as "Not started" leads to
    ambiguity.We should not show the status of the Server nodes
    which do not participate in the remove-brick process.
    
    Change-Id: I85fea40deb15f3e2dd5487d881f48c9aff7221de
    BUG: 986896
    Signed-off-by: susant <spalai@redhat.com>
    Reviewed-on: http://review.gluster.org/5383
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa04928a16858e70e6e87f2734e62b141de6f20e
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jul 23 17:02:30 2013 +0530

    features/marker: pass xdata in marker_unlink()
    
    Change-Id: Ia310af96b25f29351f3adc4bbc97aea271df7673
    BUG: 987747
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5379
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a496f0fd94276822169ff8ea9f961ac2dba7984a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 24 11:25:07 2013 +0530

    storage/posix: Fix conditional compiling for syncfs
    
    Change-Id: Ief22e1c0f2b5074060752d70da41ae93f1028d62
    BUG: 927146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5381
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 59dde88921ba506800c55f583c679630f85290e1
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Jul 4 16:07:59 2013 +0530

    cli: gluster volume heal commands are more elaborative
    
    1. "gluster volume heal volume-name"
    output :Launching heal operation to perform index self heal on volume volume-name has been successful
    
    2. "gluster volume heal volume-name full"
    Output :Launching heal operation to perform full self heal on volume volume-name has been successful
    
    3. "gluster volume heal volume-name info"
    Output :Gathering list of entries to be healed on volume volume-name has been successful
    
    4. "gluster volume heal volume-name info healed"
    Output :Gathering list of healed entries on volume volume-name has been successful
    
    5. "gluster volume heal volume-name info split-brain"
    Output :Gathering list of split brain entries on volume volume-name has been successful
    
    6. "gluster volume heal volume-name info heal-failed"
    Output :Gathering list of heal failed entries on volume volume-name has been successful
    
    Change-Id: I74c90e8129d23d513ddb7879358a9d21c94a5c0d
    BUG: 978936
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5286
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ab87748907b3312aaa751231a2e47b2efcf92b10
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Jul 17 12:10:24 2013 +0530

    cluster/dht: mark linkfile creation/deletion as internal fop
    
    Currently dht creates/deletes linkfiles for various ops like
    rename/linking and when layout changes. dht_linkfile_create
    already sends a key GLUSTERFS_INTERNAL_FOP_KEY in dict to
    identify this as an internal fop and not user based op.
    
    Enhancing rename related links/unlinks to send this key too.
    Marker/changelog or other xlators can now identify these as
    internal fops and handle them accordingly
    
    Change-Id: Ib1ca789e6dbce48703c55ad3f4f88f7cd2df3d06
    BUG: 987428
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5335
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 37ac6bdca826046cbcb0d50727af29baf9407950
Author: Anand Avati <avati@redhat.com>
Date:   Fri Jul 19 08:31:41 2013 -0700

    storage/posix: implement batched fsync in a single thread
    
    Because of the extra fsync()s issued by AFR transaction, they
    could potentially "clog" all the io-threads denying unrelated
    operations from making progress.
    
    This patch assigns a dedicated thread to issues fsyncs, as
    an experimental feature to understand performance characteristics
    with the approach.
    
    As a basis, incoming individual fsync requests are grouped into
    batches, falling in the same @batch-fsync-delay-usec window of
    time. These windows can extend in practice, as processing of
    the previous batch can take longer than @batch-fsync-delay-usec
    while new requests are getting batched.
    
    The feature support three modes (similar to the -S modes of fs_mark)
    
    - syncfs: In this mode one syncfs() is issued per batch, instead
      of N fsync()s (one per file.)
    
    - syncfs-single-fsync: In this mode one syncfs() is issued per
      batch (which, on Linux, guarantees the completion of write-out
      of dirty pages in the filesystem up to that point) and one single
      fsync() to synchronize or flush the controller/drive cache. This
      corresponds to -S 2 of fsmark.
    
    - syncfs-reverse-fsync: In this mode, one syncfs() is issued per
      batch, and all the open files in that batch are fsync()'ed in
      the reverse order of the queue. This corresponds to -S 4 of
      fsmark.
    
    - reverse-fsync: In this mode, no syncfs() is issued and all the
      files in the batch are fsync()'ed in the reverse order. This
      corresponds to -S 3 of fsmark.
    
    Change-Id: Ia1e170a810c780c8d80e02cf910accc4170c4cd4
    BUG: 927146
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4746
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cee1f9b5c7917bba220f1156b342bf07cac4ad38
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jul 23 14:06:56 2013 +0530

    tests: Avoid timing delays caused by fsync
    
    Change-Id: I2da53dd14d7352bdc878fce5a9019a955e150ce9
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5377
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 50cfc2d8e814ec649283bbd058eebd779d213d4d
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Jul 22 19:00:53 2013 +0530

    cli: Increased timeout for gluster volume heal commnads
    
    Problem:
    If number of files are very large, then gluster volume heal
    volumename info commnads take large time. So timeout of 2
    minutes seems to be insufficient.
    
    Fix:
    Increased timeout to 10 minutes
    
    Change-Id: I5f847163e01c4afbb587b726833ad80183f1a928
    BUG: 986945
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5372
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit eef0737ca6ae8056d906c7bff0a9280cc748270e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jul 22 16:44:09 2013 +0530

    cluster/afr: Handle parallel hardlinks self-heal
    
    Change-Id: Ieda11870c65edae500140b6c061f15a7b3f264f3
    BUG: 986905
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5370
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fa787929ba37e483ad041e090a82c14e3b7de900
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jul 22 19:14:56 2013 +0530

    glusterfsd: Use dynamic volfile buffer
    
    Glusterfsd used a fixed buffer to store volfiles fetched via getspec.
    This caused problems with large volfiles. Changining this to a dynamic
    buffer allows large volfiles to be loaded in memory.
    
    Change-Id: I40236dcb1c37b9a0136dfb5231cafabb3d4f00dc
    BUG: 986100
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5373
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 950371be29d029179ac5cd0ad2dfdbfcd4467b96
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon May 27 22:23:57 2013 +0530

    move 'xlators/marker/utils/' to 'geo-replication/' directory
    
    Change-Id: Ibd0faefecc15b6713eda28bc96794ae58aff45aa
    BUG: 847839
    Original Author: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5133
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 11f6c56f83b977a08f9d74563249cef59e22a05d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Jun 4 14:20:58 2013 +0530

    features/changelog: changelog translator
    
    This is the initial version of the Changelog Translator.
    
    What is it
    -----------
    Goal is to capture changes performed on a GlusterFS volume.
    The translator needs to be loaded on the server (bricks) and
    captures changes in a plain text file inside a configured
    directory path (controlled by "changelog-dir", should be
    somewhere in <export>/.glusterfs/changelog by default).
    
    Changes are classified into 3 types:
        - Data:     : TYPE-I
        - Metadata  : TYPE-II
        - Entry     : TYPE-III
    
    Changelog file is rolled over after a certain time interval
    (defauls to 60 seconds) after which a changelog is started.
    The thing to be noted here is that for a time interval
    (time slice) multiple changes for an inode are recorded only
    once (ie. say for 100+ writes on an inode that happens within
    the time slice has only a single corresponding entry in the
    changelog file). That way we do not bloat up the changelog
    and also save lots of writes.
    
    Changelog Format
    -----------------
    TYPE-I and TYPE-II changes have the gfid on the entity on
    which the operation happened. TYPE-III being a entry op
    requires the parent gfid and the basename. Changelog format
    has been kept to a minimal and it's upto the consumers to
    do the heavy loading of figuring out deletes, renames etc..
    A single changelog file records all three types of changes,
    with each change starting with an identifier ("D": DATA,
    "M": METADATA and "E": ENTRY). Option is provided for the
    encoding type (See TUNABLES).
    
    Consumers
    ----------
    The only consumer as of today would be geo-replication, although
    backup utilities, self-heal, bit-rot detection could be possible
    consumers in the future.
    
    CLI
    ----
    By default, change-logging is disabled (the translator is present
    in the server graph but does nothing). When enabled (via cli) each
    brick starts to log the changes. There are a set of tunable that
    can be used to change the translators behaviour:
    
    - enable/disable changelog (disabled by default)
      gluster volume set <volume> changelog {on|off}
    
    - set the logging directory (<brick>/.glusterfs/changelogs is the
      default)
      gluster volume set <volume> changelog-dir /path/to/dir
    
    - select encoding type (binary (default) or ascii)
      gluster volume set <volume> encoding {binary|ascii}
    
    - change the rollover time for the logs (60 secs by default)
      gluster volume set <volume> rollover-time <secs>
    
    - when secs > 0, changelog file is not open()'d with O_SYNC flag
    - and fsync is trigerred periodically every <secs> seconds.
      gluster volume set <volume> fsync-interval <secs>
    
    features/changelog: changelog consumer library (libgfchangelog)
    
    A shared library is provided for the consumer of the changelogs
    for easy acess via APIs. Application can link against this library
    and request for changelog updates. Conversion of binary logs to
    human-readable ascii format is also taken care by the library which
    keeps a copy of the changelog in application provided working
    directory.
    
    Change-Id: I75575fb7f1c53d2bec3dba1a329ea7bb3c628497
    BUG: 847839
    Original Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5127
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 41b721baee31356f442b1fb3f198456a0dd3b2db
Author: Bala.FA <barumuga@redhat.com>
Date:   Tue May 14 14:53:07 2013 +0530

    log: send current gf_log to syslog conditionally
    
    When compile time option GF_USE_SYSLOG is enabled (which is default),
    generated logs are sent to syslog with error code ERR_DEV.
    
    User can opt to use traditional log at run time by creating
    /var/log/glusterd/logger.conf file and restarting respective gluster
    services.
    
    Change-Id: I9837d0f99da1afc2189d7ecd214c4293ec53715a
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/5002
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 040319d8bced2f25bf25d8f6b937901c3a40e34b
Author: Bala.FA <barumuga@redhat.com>
Date:   Tue Apr 30 17:39:30 2013 +0530

    log: enhance syslog logging using CEE format
    
    This patch enables to use syslog as log target in addition to the
    default.  The logs are sent in CEE format (http://cee.mitre.org/).
    This logging can be disabled using compile time option by
    
    ./configure --disable-syslog
    (or)
    rpmbuild glusterfs.tar.gz --without syslog
    
    The framework provides two api
    
    void gf_openlog (const char *ident, int option, int facility);
    void gf_syslog (int error_code, int facility_priority, char *format, ...);
    
    consumers need to call gf_openlog() prior to gf_syslog() like the way
    traditional syslog function calls.  error_code is mandatory when using
    gf_syslog().  For example,
    
    gf_openlog (NULL, -1, -1);
    gf_syslog (GF_ERR_DEV, LOG_ERR, "error reading configuration file");
    
    Using syslog, admin is free to configure logger to
    * reduce repeated log messages
    * forward logs to remote logger
    * execute a command on certain log pattern
    * alert people for certain log pattern by email, snmp etc
    * and many more
    
    Change-Id: Ibacbcbbc547192893fc4a46b387496b622e4811f
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/4915
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f75957ab6baef8907c8421f44f785956fbf48038
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri May 10 12:30:17 2013 +0530

    log: error code generation support
    
    error code and message are generated at compile time by reading a json
    file which contains information of elements for each error code.  This
    framework provides error handling and ability to do more cleaner log
    messages to users.
    
    error-codes.json file contains error description is below format
    
    {
        "ERR_NAME": {"code": ERR_NUM,
                     "message": {"LOCALE": "ERR_MESSAGE"}}
    }
    
    At compile time autogen.sh calls gen-headers.py which produces C
    header file libglusterfs/src/gf-error-codes.h.  This header has a
    function
    
    const char *_gf_get_message (int code);
    
    which returns respective ERR_MESSAGE for given ERR_NUM.
    
    Change-Id: Ieefbf4c470e19a0175c28942e56cec98a3c94ff0
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/4977
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4c0f4c8a89039b1fa1c9c015fb6f273268164c20
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Tue Jul 16 11:49:20 2013 +0530

    fuse: auxiliary gfid mount support
    
    * files can be accessed directly through their gfid and not just
      through their paths. For eg., if the gfid of a file is
      f3142503-c75e-45b1-b92a-463cf4c01f99, that file can be accessed
      using <gluster-mount>/.gfid/f3142503-c75e-45b1-b92a-463cf4c01f99
    
      .gfid is a virtual directory used to seperate out the namespace
      for accessing files through gfid. This way, we do not conflict with
      filenames which can be qualified as uuids.
    
    * A new file/directory/symlink can be created with a pre-specified
      gfid. A setxattr done on parent directory with fuse_auxgfid_newfile_args_t
      initialized with appropriate fields as value to key "glusterfs.gfid.newfile"
      results in the entry <parent>/bname whose gfid is set to args.gfid. The
      contents of the structure should be in network byte order.
    
      struct auxfuse_symlink_in {
            char     linkpath[]; /* linkpath is a null terminated string */
      } __attribute__ ((__packed__));
    
      struct auxfuse_mknod_in {
            unsigned int   mode;
            unsigned int   rdev;
            unsigned int   umask;
      } __attribute__ ((__packed__));
    
      struct auxfuse_mkdir_in {
            unsigned int   mode;
            unsigned int   umask;
      } __attribute__ ((__packed__));
    
      typedef struct {
            unsigned int  uid;
            unsigned int  gid;
            char          gfid[UUID_CANONICAL_FORM_LEN + 1]; /* a null terminated gfid string
                                                          * in canonical form.
                                                          */
            unsigned int  st_mode;
            char          bname[];     /* bname is a null terminated string */
    
            union {
                    struct auxfuse_mkdir_in   mkdir;
                    struct auxfuse_mknod_in   mknod;
                    struct auxfuse_symlink_in symlink;
            } __attribute__ ((__packed__)) args;
      } __attribute__ ((__packed__)) fuse_auxgfid_newfile_args_t;
    
      An initial consumer of this feature would be geo-replication to
      create files on slave mount with same gfids as that on master.
      It will also help gsyncd to access files directly through their
      gfids. gsyncd in its newer version will be consuming a changelog
      (of master) containing operations on gfids and sync corresponding
      files to slave.
    
    * Also, bring in support to heal gfids with a specific value.
      fuse-bridge sends across a gfid during a lookup, which storage
      translators assign to an inode (file/directory etc) if there is
      no gfid associated it. This patch brings in support
      to specify that gfid value from an application, instead of relying
      on random gfid generated by fuse-bridge.
    
      gfids can be healed through setxattr interface. setxattr should be
      done on parent directory. The key used is "glusterfs.gfid.heal"
      and the value should be the following structure whose contents
      should be in network byte order.
    
      typedef struct {
            char      gfid[UUID_CANONICAL_FORM_LEN + 1]; /* a null terminated gfid
                                                          * string in canonical form
                                                          */
            char      bname[]; /* a null terminated basename */
      } __attribute__((__packed__)) fuse_auxgfid_heal_args_t;
    
      This feature can be used for upgrading older geo-rep setups where gfids
      of files are different on master and slave to newer setups where they
      should be same. One can delete gfids on slave using setxattr -x and
      .glusterfs and issue stat on all the files with gfids from master.
    
    Thanks to "Amar Tumballi" <amarts@redhat.com> and "Csaba Henk"
    <csaba@redhat.com> for their inputs.
    
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Change-Id: Ie8ddc0fb3732732315c7ec49eab850c16d905e4e
    BUG: 952029
    Reviewed-on: http://review.gluster.com/#/c/4702
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/4702
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1ebee3b0a8cf4526ab396ae8cad55634fad17fc
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jul 18 09:55:22 2013 -0400

    core: avoid infinite mutual recursion between THIS and gf_log
    
    This caused a stack overflow when (for some unknown reason) pthread_setspecific
    was failing.  Therefore __glusterfs_this_location called gf_log which used THIS
    which wraps __glusterfs_this_location which . . . you get the idea.  We have to
    break the loop somewhere, and we can't reasonably make _gf_log stop using THIS,
    so we make __glusterfs_this_location stop using _gf_log.
    
    Change-Id: I79c3ea40dd7980bb8ac76a52cdbf5c057b2e1c3c
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/5341
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 70e5090326f029e6bcebd398572b39d3705d0bf3
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Jul 17 11:17:04 2013 -0400

    mount/fuse: unlink the inode on revalidate if entry not found
    
    If an inode/dentry is linked via a client and removed via a
    separate client, the inode/dentry mapping in the initial client
    remains. A lookup of the removed name on the initial client
    typically returns ENOENT once the associated caches expire. If the
    initial client has multiple dentries linked to the same inode,
    however, lookups on the non-removed dentry create windows of time
    where lookups on the stale/removed name return successfully. This
    occurs because the stale mapping resolves to the still valid inode
    and tricks md-cache into returning valid lookup data.
    
    To correct this situation, unlink the stale inode mapping on a
    failed (ENOENT) revalidation lookup (i.e., when fuse has resolved
    the inode but a lookup returns ENOENT). Note that with this change,
    the state still occurs until an md-cache window has expired,
    allowed a lookup to pass through to the server and given the fuse
    translator an opportunity to clean up.
    
    Change-Id: I47dde2f11e2ef5b8dd51e9ac8be0f36cdb5081a3
    BUG: 985074
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5337
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit deb19de9f613611b374b1ff4d0f3a83079604c5a
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Jul 18 11:13:08 2013 +0200

    include <limits.h> for PATH_MAX
    
    I need to include <limits.h> in order to use PATH_MAX, Otherwise it will
    not build at mine. I believe it is standard compliant to do so:
    http://pubs.opengroup.org/onlinepubs/009695399/basedefs/limits.h.html
    
    BUG: 764655
    Change-Id: I3f124466f7f7742e94a9d1256bc9239ec16aab04
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/5340
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 15e11cfa1dec9cafd5a9039da7a43e9c02b19d98
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Jun 5 15:56:27 2013 +0530

    locks: Added an xdata-based 'cmd' for inodelk count in a given domain
    
    Following is the semantics of the 'cmd':
    1) If @domain is NULL - returns no. of locks blocked/granted in all domains
    2) If @domain is non-NULL- returns no. of locks blocked/granted in that
    domain
    3) If @domain is non-existent - returns '0'; This is important since
    locks xlator creates a domain in a lazy manner.
    
    where @domain - a string representing the domain.
    
    Change-Id: I5e609772343acc157ca650300618c1161efbe72d
    BUG: 951195
    Original-author: Krishnan Parthasarathi <kparthas@redhat.com>
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4889
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit ad5ab1216066495589d73015f47183cc26f10eb6
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Jul 9 09:09:30 2013 +0530

    dht: fix dht_discover_cbk doing a wrong layout set.
    
    with the sequence of operations are like below, we have issues
    with current code (MP == mountpoint):
    T0,MP1# mkdir /abcd (Succeeds on hash_subvol)
    T1,MP2# mkdir /abcd (Gets EEXIST as dir exists in hash_subvol)
    T2,MP2# mkdir /.gfid/<abcd's gfid>/xyz (lookup happens on abcd's
            gfid, calls dht_discover)
    T3,MP1# (Completes mkdir(), goes to dir_selfheal to set the layouts).
    T4,MP2# (dht_discover_cbk gets success for lookup as the entry
            existed, as layout is not yet written, it says normalize
            done, found holes).
    T5,MP2# (as layout anomaly is not considered an issue in this patch,
            dht_layout_set happens on inode, with all xlators pointing
            to 0s)
    T6,MP1# (completes mkdir call, inode has proper layouts)
    T7,MP2# mkdir /.gfid/<abcd's gfid>/xyz fails with ENOENT
            (with log saying no subvol found for hash value of xyz.
    
    Porting Amar's fix from down-stream beta branch.
    
    Change-Id: Ibdc37ee614c96158a1330af19cad81a39bee2651
    BUG: 982913
    Original-author: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5302
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit da50f61174dad89699da40212746b398b576ca15
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Jul 16 15:58:03 2013 +0530

    gfapi: fix for not able to rename folders
    
    If oldname is being renamed to newname, we need to
    check for type of newname only if newname exists.
    
    Change-Id: I068a283f9ffe67fcd5e8754d6bf052a2339efbf2
    BUG: 953694
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/5333
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3e1d8e1689c47d8b83343a403e7d09c018472155
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Jul 11 13:44:51 2013 +0530

    cluster/dht: Prevent dht_access from going into a loop.
    
    If access fails with ENOTCONN, do not wind to same subvol.
    We wind to first-up-subvol if access fails with ENOTCONN.
    In few cases, if dht has only 1 subvolume, and access fails with
    ENOTCONN, we go into a infinite loop of winding to same subvol
    
    The fix is to check if we previously wound to same subvol, and
    fail if first-up-subvol is same.
    
    Change-Id: Ib5d3ce7d33e8ea09147905a7df1ed280874fa549
    BUG: 983431
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5319
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c50aa14008f9612d273acb81470f544cad6cff1a
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jul 12 15:00:07 2013 +0200

    tests: call 'cleanup' at the end of each test
    
    Some tests do not cleanup after themselves. That is bad behaviour and
    makes it difficult to run single tests and verify the state of the
    system afterwards.
    
    Change-Id: I4ac5401d790d6bc81e6975fd1384874b21d6cf8a
    BUG: 983975
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5328
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3f6a5702642837411477f241c9756c1872d46b1f
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Apr 29 20:30:30 2013 +0200

    afr: customize client-pid=-1 xtime aggregation to tolerate a replica down
    
    Using the new 'pluggable policies' API of libxlator.
    
    Change-Id: Ie7528182dff8fb42c6e8287a106d3057944df775
    BUG: 847839
    Original Author: Csaba Henk <csaba@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4904
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2af3e8bd6dd0fba429681b6329283afe8c34c70b
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Mar 13 10:21:57 2013 +0100

    libxlator: implement pluggable aggregation policies
    
    The API is described in libxlator.h.
    
    Behavior remains the same for this commit; this
    is a preparatory step for per-translator customization
    of aggregation.
    
    Change-Id: I5d42923af59b2fd78e1ff59c12763875b57c5190
    BUG: 847839
    Original Author: Csaba Henk <csaba@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4903
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 51ed78005c676addef0d0a70ca47c794a6396075
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jun 13 19:38:57 2013 +0530

    cluster/dht: node-uuid for directories winds to all subvolumes
    
    this works similar to pathinfo now except that the request is sent
    to all subvolumes of dht. Underlying replica selects it's subvolume
    in a round-robin fashion till one of them returns successfully.
    
    Change-Id: Ie46c5f7090d04d8c2e487b209916ae6791e94624
    BUG: 847839
    Original Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5225
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a2a01c565328e57b05a2e4700f402c351adc9372
Author: Justin Clift <jclift@redhat.com>
Date:   Thu Jul 4 18:33:50 2013 +0100

    Adjust configure.ac to honor existing CFLAGS env variable
    
    Change-Id: I43a8defc7a8c0c2d391e7bd2c0b7bebfcc522a2a
    BUG: 961892
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/4979
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 74f67e3a86a1dc5324cd41d4fab78858718db1d2
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Sat Apr 27 12:44:05 2013 +0530

    cluster/*: get logic to calculate min() of the 'stime' xattr
    
    * in both distribute and replicate (ignoring stripe for now),
      add logic to calculate the min() of stime values.
    
    * What is a 'stime' ? Why is this required:
      -  stime means 'slave xtime', mainly used to keep track of slave
      node's sync status when distributed geo-replication is used.
      Logic of calculating 'min()' for this stime is very important as
      in case of crashes/reboots/shutdown, we will have to 'restart'
      with crawling from stime time value from the mount point, which
      gives the 'min()' of all the bricks, which means, we don't miss
      syncing any files in the above cases.
    
    Change-Id: I2be8d434326572be9d4986db665570a6181db1ee
    BUG: 847839
    Original Author: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4893
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 61b09562b934b53dadcd566f6feb72301097933c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jul 11 12:52:11 2013 +0530

    mount/fuse: Provide option to use/not use kernel-readdirp
    
    By default fuse kernel readdirp usage in fuse xlator is off.
    When mount option use-readdirp=yes is provided it starts using
    fuse-kernel's readdirp.
    
    Change-Id: Id37edc53b1adc1638186d956c2f74c1e4e48aa59
    BUG: 983477
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5322
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 07833f13d43a3e3532171bb2edbe068e3a7205b1
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Mon Jul 8 15:45:54 2013 +0530

    cli: check for null in is_server_debug_xlator()
    
    Command: gluster volume set <volname> diagnostics.client-log-level trace
    Expected output:
    "volume set: failed: option log-level trace: 'trace' is not valid
    (possible options are DEBUG, WARNING, ERROR, INFO, CRITICAL, NONE,
    TRACE.)"
    Current output: gluster cli receives a segmentation fault
    Fix: check for NULL before calling strstr
    
    Change-Id: If4c7a85a635849a388cf122543e12349c109643c
    BUG: 982174
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/5298
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ec64f13476cbd2f7702cecfef929f3ea8efc0a51
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Jul 11 11:52:25 2013 +0530

    cluster/dht: Unlink dst file after cleanup during migration
    
    If a rename happens during migration, unlink fails. This leads
    to stale xattrs, and Sticky bits still being set.
    
    By removing the xattrs and Sticky bits from dst (through fd ops),
    the stale link file would be cleaned up eventually (even if unlink
    fails on src).
    
    Change-Id: Iec537d021905438327a20e1d811aa06e74034364
    BUG: 983399
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5316
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 60d1949b00fa42e0c5d1f0a763004ca474a4645d
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Jul 11 13:05:55 2013 +0530

    cluster/dht: If linkfile unlink fails with ENOTCONN, do not fail
    
    Currently if linkfile fails with ENOENT, we do not fail. We also
    need to treat failures with ENOTCONN as success, as if cached subvol
    is up, rm of a file should succeed. A stale linkfile will get removed
    later
    
    Change-Id: I71d136847933351ed9e2c939bda4a69bc96a3cfc
    BUG: 983416
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5317
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5bb136c4ca18cc4c058040ea6db312be13edb098
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jul 11 14:28:41 2013 +0530

    glusterd: Give up biglock before brick's rpc unref
    
    This is to prevent the possibility of a deadlock when
    rpc_connection_cleanup being called in the same thread as rpc_clnt_unref
    
    Change-Id: Ia4dcc0a8a6e6158d4ddec68b780fccbc4cd64adb
    BUG: 962619
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5321
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6f7d308bf7e07a4202ab091382ccf9cd3c2b309c
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jul 8 16:06:31 2013 +0530

    glusterd: Correct op-version of some options
    
    New options being introduced in the master branch should now have
    op-version set to the GD_OP_VERSION_MAX (3). Some of the options have
    been backported to release-3.3 branch and hence should have their
    op-version reduced. Some other options had op-version incorrectly set as
    1.
    
    Change-Id: If40325b7b2da7aa36f90261024117cd18cf51ef0
    BUG: 981278
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5318
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 55ccdb71466ca8459f29454e9eee38fa7aa63e95
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jun 26 16:50:53 2013 +0530

    mount/fuse: expose 'glusterfs.gfid*' virtual xattr key
    
    currently two keys are exposed:
    
    'glusterfs.gfid' : output is 16byte binary gfid
    'glusterfs.gfid.string' : output is 36 byte canonical format of gfid
    
    e.g.
    [root@supernova glusterfs]# getfattr -n glusterfs.gfid -e hex f0
    glusterfs.gfid=0x68305acb73e541719804fcf36a4857e8
    
    [root@supernova glusterfs]# getfattr -n glusterfs.gfid.string f0
    glusterfs.gfid.string="68305acb-73e5-4171-9804-fcf36a4857e8"
    
    early consumers for this key would be geo-replication
    (as it has being designed to do namespace operations on
    gfid from the mount point, thereby needing the GFID for
    entry operations on the slave).
    
    Change-Id: I10b23dbd11628566ad6924334253f5d85d01a519
    BUG: 847839
    Original Author: Venky Shankar <vshankar@redhat.com>
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/5129
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 869b0f2c272d8e0f3afb7ad5f15ebc0f7c900a76
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu May 23 08:30:55 2013 +0530

    tests: Don't use stripe-replicate volume in bug-905864.t
    
    Today, stripe doesn't follow a deterministic order in sending posix
    locks to its subvolume. This may lead to dead locks. To avoid
    intermittent test failures, we modify bug-905864.t to run on replicate
    volume.
    
    Change-Id: I38b72f30bc31576d3ca642f0029cc8749314b1dd
    BUG: 905864
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5072
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 02c0b6f0fcd6e9c678b170a8150d2b79942724ef
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jun 20 14:04:10 2013 +0530

    performance/io-cache: check for non-null gfid before calling inode_path
    
    A new non-linked inode is added to lru list. Hence it might be possible
    that gfid might be NULL when inode_dump is called. To pass asserts in
    inode_path, we've to check for non-null gfid before invoking that
    procedure.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: Iff14efc6d6e2faa33b9f7a81e0a66f6a947b77ed
    BUG: 976189
    Reviewed-on: http://review.gluster.org/5241
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 72aef87eeddc59428af67f2e6a666839b0ddd09c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jun 27 18:05:54 2013 +0200

    test-ffop: the result of (O_TRUNC|O_RDONLY) is unspecified
    
    On RHEL-6 an open(.., O_TRUNC|O_RDONLY) fails. test-ffop expects this to
    succeed, but the behaviour is unspecified according to 'man 2 open':
    
           O_TRUNC
                  If  the  file  already exists and is a regular file and the open
                  mode allows writing (i.e., is O_RDWR or  O_WRONLY)  it  will  be
                  truncated to length 0.  If the file is a FIFO or terminal device
                  file, the O_TRUNC flag is  ignored.   Otherwise  the  effect  of
                  O_TRUNC is unspecified.
    
    Change-Id: I76b55419871fc758cbe82532f9b75476a0c14101
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5268
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 63ed610617458ac4fd85cb83471df2222380f28a
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon Jul 8 18:48:55 2013 +0530

    cluster/dht: Ignore subvols with error in min-free-disk/inodes
    
    Currently when selecting a alternative subvolume when hashed
    subvol has exceeded min-free-disk/inodes, we do not check if
    layouts have errors (including decommissioning). This leads
    to data being written to those subvolumes, and in case of
    decommissioning, will lead to data loss.
    
    Change-Id: Ie0c6cf4a29d7c53d8a6d8a8c1bd595cf58a0012a
    BUG: 982919
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5299
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 03780d066ae7c78b969e2316dbde85e4ca0fcb85
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Fri May 31 18:17:21 2013 +0530

    nfs: AUTH support for exported sub-directories
    
    Problem: NFS allows exporting subdirectories but there is not support for
    providing AUTH on per directory basis.
    
    Fix: Modified nfs.export-dir to include AUTH parameters
     e.g. nfs.export-dir "/dir1(10.1.1.2),/dir2(10.1.1.0/24|host1)
    
    During mount operation NFS will check if the IP from where the connection is made
    is configured in the AUTH parameter, else the mount operation will fail with
    EACCES error.
    
    Updated admin-guide and volume set help message.
    
    Change-Id: I5c6d22edb168b4f46376d1cd6878cd065fc081cc
    BUG: 968227
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/5124
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 60bdca792b7e572b4d79382dada1c6b93bebdd0e
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Jul 3 13:02:29 2013 +0530

    doc: Moved non-relevant documentation files to legacy
    
    Change-Id: I2d34e5a4e47cd03d301d9fd2525fb61ae997fcb8
    BUG: 811311
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5277
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0d9fe510e7a3204c524ca88d8679c0cb20c101b2
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu May 2 15:29:56 2013 +0530

    afr : change the log level in lookup path to minimize incessant logging.
    
    Change the logging levels from WARNING to DEBUG in the lookup path to
    minimize incessant logging in case of gfid mismatch errors.
    
    Change-Id: I631b16df3249cf826606f547531f985dac696088
    BUG: 959083
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4939
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit eb46c44b333dded7dedb71a48f64785e8b95f93b
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jul 4 16:49:58 2013 +0530

    glusterd: Bump GD_MAX_OP_VERSION
    
    Change-Id: I7a212435ce7e98fe01aad2c0d1f698de8ea84235
    BUG: 981278
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5287
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9e687332b4900cf4c91a4cf9b34da8d2a97e39df
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Jul 3 10:24:50 2013 +0530

    api: Bump version to 5.
    
    version 5 adds support for fallocate & discard.
    
    Change-Id: Ifdc226953a25e4a4eb63e55d2a7c7ec77c397215
    BUG: 953694
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5276
    Reviewed-by: Bharata B Rao <bharata.rao@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 45488a325f6c816675ca99874eb2cbdc0358a91e
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jun 27 17:59:43 2013 +0530

    nufa: allow subvols with fanout > 1
    
    Previously, nufa wouldn't work on volume topologies such as
    distribute-replicate or distribute-stripe.
    
    Change-Id: Ia89ed4412a00601022c1fc94f046056ce4820fe8
    BUG: 980838
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5262
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 78ee0265db1363b7b1f3943d6a3daa622b7564b8
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jun 27 14:55:59 2013 +0530

    glusterd/common-utils: move hostname helper functions to common-utils
    
    Change-Id: If47e209cb61ea0eb74ee2d6ef9e9342b2d6ee13a
    BUG: 980838
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5261
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b3cc22184452824d436903baa62635acee739c50
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Wed Jun 19 17:54:31 2013 +0530

    cli: Fix remove brick cli out for wrong volume name
    
    Problem:  gluster volume remove-brick command, was not printing the error in
              case of volume-name specified is wrong.
    
    Fix:      Fix will print error message to indicate that provided volume name is
              invalid. Although patch for bug 961669
              http://review.gluster.org/#/c/4975/ does print cli-output now, but
              still xml is unable to use the response values
    
    Change-Id: I2ee1df86c1e756fb8e93b4d6bbdd102b4f368f87
    BUG: 961307
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4972
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 98f62a731ca13296b937bfff14d0a2f8dfc49a54
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jun 24 14:05:58 2013 +0200

    posix: add a simple health-checker
    
    Goal of this health-checker is to detect fatal issues of the underlying
    storage that is used for exporting a brick. The current implementation
    requires the filesystem to detect the storage error, after which it will
    notify the parent xlators and exit the glusterfsd (brick) process to
    prevent further troubles.
    
    The interval the health-check runs can be configured per volume with the
    storage.health-check-interval option. The default interval is 30
    seconds.
    
    It is not trivial to write an automated test-case with the current
    prove-framework. These are the manual steps that can be done to verify
    the functionality:
    
    - setup a Logical Volume (/dev/bz970960/xfs) and format is as XFS for
      brick usage
    
    - create a volume with the one brick
    
        # gluster volume create failing_xfs glufs1:/bricks/failing_xfs/data
        # gluster volume start failing_xfs
    
    - mount the volume and verify the functionality
    
    - make the storage fail (use device-mapper, or pull disks)
    
        # dmsetup table
        ..
        bz970960-xfs: 0 196608 linear 7:0 2048
    
        # echo 0  196608 error > dmsetup-error-target
        # dmsetup load bz970960-xfs dmsetup-error-target
        # dmsetup resume bz970960-xfs
    
        # dmsetup table
        ...
        bz970960-xfs: 0 196608 error
    
    - notice the errors caught by syslog:
    
        Jun 24 11:31:49 vm130-32 kernel: XFS (dm-2): metadata I/O error: block 0x0 ("xfs_buf_iodone_callbacks") error 5 buf count 512
        Jun 24 11:31:49 vm130-32 kernel: XFS (dm-2): I/O Error Detected. Shutting down filesystem
        Jun 24 11:31:49 vm130-32 kernel: XFS (dm-2): Please umount the filesystem and rectify the problem(s)
        Jun 24 11:31:49 vm130-32 kernel: VFS:Filesystem freeze failed
        Jun 24 11:31:50 vm130-32 GlusterFS[1969]: [2013-06-24 10:31:50.500674] M [posix-helpers.c:1114:posix_health_check_thread_proc] 0-failing_xfs-posix: health-check failed, going down
        Jun 24 11:32:09 vm130-32 kernel: XFS (dm-2): xfs_log_force: error 5 returned.
        Jun 24 11:32:20 vm130-32 GlusterFS[1969]: [2013-06-24 10:32:20.508690] M [posix-helpers.c:1119:posix_health_check_thread_proc] 0-failing_xfs-posix: still alive! -> SIGTERM
    
    - these errors are in the log of the brick as well:
    
        [2013-06-24 10:31:50.500607] W [posix-helpers.c:1102:posix_health_check_thread_proc] 0-failing_xfs-posix: stat() on /bricks/failing_xfs/data returned: Input/output error
        [2013-06-24 10:31:50.500674] M [posix-helpers.c:1114:posix_health_check_thread_proc] 0-failing_xfs-posix: health-check failed, going down
        [2013-06-24 10:32:20.508690] M [posix-helpers.c:1119:posix_health_check_thread_proc] 0-failing_xfs-posix: still alive! -> SIGTERM
    
    - the glusterfsd process has exited correctly:
    
        # gluster volume status
        Status of volume: failing_xfs
        Gluster process						Port	Online	Pid
        ------------------------------------------------------------------------------
        Brick glufs1:/bricks/failing_xfs/data			N/A	N	N/A
        NFS Server on localhost					2049	Y	1897
    
    Change-Id: Ic247fbefb97f7e861307a5998a9a7a3ecc80aa07
    BUG: 971774
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5176
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 37d2c255e46eea98df473fbc693931462882392e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jul 3 09:45:41 2013 +0200

    fuse: pass the mountflags to older (< 2.6.21) kernels
    
    The change for Bug 853895 fixed mounting volumes read-only for recent
    kernels. Older kernels fail the first mount() syscall, and the second
    mount() did not add the 'mountflags'.
    
    Full analysis and a description for reproducing is in the bugreport. The
    test included in http://review.gluster.org/4163 would have caught this
    problem when the tests are executed on RHEL-5 or similar systems.
    
    Change-Id: I440591344a6a5af7b2018e37a2a1fda9de8b5ab2
    Bug: 980770
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5278
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 291344f9c80fe1a3c0fe784a1642da6795dcf5a4
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Jun 27 15:47:01 2013 +0530

    cli: Fix in letter case in volume heal output
    
    Change-Id: I25d13444c2cbff9b26642e91677ad1e09e77aa1e
    BUG: 978936
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5259
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0aa4248cf967b158c0cf6ce33c300ad4b3ee3249
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 3 21:28:25 2013 +0530

    cluster/afr: Let two data-self-heals compete in new domain
    
    Problem:
    At the moment data-self-heal acquires locks in following
    pattern. It takes full file lock then gets xattrs on files on both
    replicas. Decides sources/sinks based on the xattrs. Now it acquires
    lock from 0-128k then unlocks the full file lock. Syncs 0-128k range
    from source to sink now acquires lock 128k+1 till 256k then unlocks
    0-128k, syncs 128k+1 till 256k block... so on finally it takes full file
    lock again then unlocks the final small range block.
    It decrements pending counts and then unlocks the full file lock.
    
         This pattern of locks is chosen to avoid more than 1 self-heal
    to be in progress. BUT if another self-heal tries to take a full
    file lock while a self-heal is already in progress it will be put in
    blocked queue, further inodelks from writes by the application will
    also be put in blocked queue because of the way locks xlator grants
    inodelks. So until the self-heal is complete writes are blocked.
    
    Here is the code:
    xlators/features/locks/src/inodelk.c - line 225
    if (__blocked_lock_conflict (dom, lock) && !(__owner_has_lock (dom, lock))) {
             ret = -EAGAIN;
             if (can_block == 0)
                     goto out;
    
             gettimeofday (&lock->blkd_time, NULL);
             list_add_tail (&lock->blocked_locks, &dom->blocked_inodelks);
    }
    
    This leads to hangs in applications.
    
    Fix:
    Since we want to prevent two parallel self-heals. We let them compete
    in a separate "domain". Lets call the domain on which the locks have
    been taken on in previous approach as "data-domain".
    
    In the new approach When a self-heal is triggered,
    it acquires a full lock in the new domain "self-heal-domain".
        After this it performs data-self-heal using the locks in
        "data-domain" as before.
    unlock the full file lock in "self-heal-domain"
    
    With this approach, application's writevs don't have to wait
    in pending queue when more than 1 self-heal is triggered.
    
    Change-Id: Id79aef3dfa888945977fb9758374ac41c320d0d5
    BUG: 967717
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5100
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c2abf3a6e39c5a5832a165757483bc0ae23cdb63
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 3 21:21:48 2013 +0530

    cluster/afr: Refactor inodelk to handle multiple domains
    
    - afr_local_copy should not be memduping locked nodes, that would
      mean that lock is taken in self-heal on those nodes even before
      it actually takes the lock. So removed memdup code. Even entry
      lock related copying (lockee info) is also not necessary for
      self-heal functionality, so removing that as well. Since it is
      not local_copy anymore changed its name.
    
    - My editor changed tabs to spaces.
    
    Change-Id: I8dfb92cb8338e9a967c06907a8e29a8404782d61
    BUG: 967717
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5099
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b64a7f8497d9752f4da5a42aeeeebbd7727c442b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 28 16:03:52 2013 +0530

    cluster/afr: Provide an option to disable afr durability
    
    Change-Id: I40eec20ca6b3f857245a2438883822e251077ee9
    BUG: 979365
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5269
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 29619b4ee78926160435da82f9db213161e040d4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Jul 3 05:23:46 2013 +0530

    cluster/afr: post-op should complete before starting flush
    
    Problem:
    At the moment afr-flush makes sure that a delayed post-op
    is woken up but it does not wait for it to complete the
    post-op before flush unwinds.
    These are the steps that are happening:
    1) flush fop comes on an fd which wakes up a delayed post-op
    and continues with the flush fop.
    2) post-op sends fsync on the wire.
    3) flush completes and unwinds to fuse.
    4) graph switch happens on the fuse mount disconnecting the
    old graph's client connections to bricks.
    5) xattrop after fsync fails with ENOTCONN because the
    connections from old graph are taken down now.
    
    Fix:
    Wait for post-op to complete before starting to flush.
    We could make flush act similar to fsync (i.e.) wind
    flush as is but wait for post-op to complete before unwinding
    flush, but it is better to send flush as the final fop. So
    wind of flush will start after post-op is complete. Had to
    change fsync to accommodate this change.
    
    Change-Id: I93aa642647751969511718b0e137afbd067b388a
    BUG: 980548
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5274
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7fd38981278c8a51587f1db5b59f8cfeed5c6e5a
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu May 16 16:03:52 2013 +0530

    glusterd: More checks before starting rebalance/remove-brick
    
    Check if a previous remove-brick operation has been committed before
    starting a new rebalance/remove-brick task.
    
    Change-Id: I553e5ba64a6a352ca91032ab1a17997051a4494e
    BUG: 963541
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5019
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 979a17d49a8dc9a19d9f3a466c137d5cf2c79a07
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Jun 19 16:07:25 2013 +0530

    store: Fix resource leaks in gf_store_iter_* functions
    
    Also, removed (redundant) member fd from gf_store_iter_t
    
    Change-Id: I40f0469997f77fa2f578a5495ca4ce285f1a59f2
    BUG: 904065
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5243
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ef8092fab7b6fa5a16cc0e22b75945758519d5a6
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Jun 28 19:11:47 2013 +0530

    cluster/afr: Allow data/entry self heal for metadata split-brain
    
    Problem:
    Currently whenever there is metadata split-brain, a variable
    sh->op_failed is set to 1 to denote that self heal got failed.
    But if we proceed for data self heal, even code-path of data
    self heal also relies on the sh->op_failed variable. So if will
    check for sh->op_failed variable and will eventually fails to
    do data self heal. So needed a mechanism to allow data self heal
    even if metadata is in split brain.
    
    Fix:
    Some data structure revamp is done in
    http://review.gluster.com/#/c/5106/ fix and this patch is
    based on the above fix. Now we can store which particular self-heal
    got failed i.e GFID_OR_MISSING_ENTRY_SELF_HEAL, METADATA, DATA,
    ENTRY. And we can do two types of self heal failure check.
    1. Individual type check: We can check which among all four
       (Metadata, Data, Gfid or missing entry, entry self heal)
       got failed.
    
    2. In afr_self_heal_completion_cbk, we need to make check
       based on the fact that if any specific self heal got failed treat
       the complete self heal as failure so that it will populate
       corresponding circular buffer of event history accordingly.
    
    Change-Id: Icb91e513bcc752386fc8a78812405cfabe5cac2d
    BUG: 977797
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5253
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7062eda1575214819f5c7411748b06be95e08ffa
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jun 24 12:50:32 2013 +0530

    libglusterfs: Fix valid_host_name for consecutive dots
    
    The valid_host_name() function must reject addresses with consecutive
    dots in them.
    
    Change-Id: I1749de80c66e8fbad63b2e014f79e0203906030e
    BUG: 977246
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5249
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ac62c953e499dca873fbf808b95df0feb50bda27
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Jun 24 02:57:07 2013 +0530

    extras/hook-scripts: Set of changes for new samba share method.
    
    New method of creating a share of gluster volume
    through samba eliminates the requirement of fuse
    mount and changes in fstab.
    
    glusterfs vfs plugin has to be specified as required
    vfs object.
    Path now is relative to the root of gluster volume.
    / signifies complete volume.
    
    Change-Id: I3d80452cd58513ef59d6a816c1ab62ebc3b76a62
    BUG: 953694
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/5247
    Reviewed-by: José Rivera <jrivera@redhat.com>
    Tested-by: José Rivera <jrivera@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e216e2e6fcc537d7fdae4527043a2a71732c7d36
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jun 27 10:44:44 2013 -0400

    build: sync glusterfs.spec.in with Fedora glusterfs.spec
    
    * fix the hardening fix for shlibs
    * use %{__sed} macro
    * better short ChangeLog
    * fix hard-coded path in extras/systemd/glusterd.service in, use @prefix@
    
    Change-Id: I267244b68a97cbcd6f6ab62fc322c78db45023bb
    BUG: 950083
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5264
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit fdc83183263e04bee56672e9d9922cc9457146cb
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Jun 21 14:58:23 2013 +0530

    nfs: exit when all volumes are disabled
    
    Instead of triggering 4-5 error logs, when nfs is
    disabled for all volumes, exit the process.
    
    Change-Id: Ib286f143c4f74ba22f502aca0e7dcd0907db6563
    BUG: 976750
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/5245
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0c05cde4a16c426089933803d082183227422307
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jun 27 12:59:14 2013 +0530

    cluster/afr: Handle NULL fdctx in fsync
    
    Problem:
    If fdctx is NULL in afr_fsync, process crashes because
    of NULL dereference.
    
    Fix:
    if fdctx is NULL, always say witnessed unstable write so
    that fsyncs are done properly. Handled fdctx being null
    in afr_delayed_changelog_post_op otherwise fsync stub is
    never resumed and the mount was hanging.
    
    Change-Id: Icacc900e9be63c29db3325cb0e19cc250adebaac
    BUG: 978794
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5258
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4bea8a2cfeaa8e037c6566b6a192bc31a2c004ca
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 28 09:01:08 2013 +0530

    protocol/server: Initialize connection variable
    
    Change-Id: I46badd812e9b936911ddd2793cef7ce30ec220a6
    BUG: 979237
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5266
    Reviewed-by: Raghavendra G <rgowdapp@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 75ee14ffbe362c41be096eca9a2fef1ec7e8db94
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jun 24 14:34:50 2013 +0200

    build: declare lvm_lv_from_name() if it is missing from lvm2app.h
    
    The bd-xlator can not be built successfully on certain Debian
    distributions due to a missing declaration of lvm_lv_from_name(). This
    function is available for linking, but it does not exist in the header
    file.
    
    This change adds a detection for lvm_lv_from_name() in both the library
    for linking, and the declaration in the header file. If the 1st is
    missing, the bd-xlator can not be built, and if only the 2nd one is
    missing, we'll declare lvm_lv_from_name() ourselves. This makes it
    possible to build the bd-xlator on the affected Debian distributions
    too.
    
    Change-Id: I0c823a7861b02bb5d9c1abb76ebfff92f272f9eb
    BUG: 976946
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5250
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e00fb417781931454dfb51f3eac803f44d5b6eca
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Jun 4 17:58:34 2013 +0530

    nfs/auth: reject mounts if getaddrinfo fails
    
    When nfs.addr-namelookup is turned on, if the
    getaddrinfo call fails while authenticating client's
    ip/hostname, the mount request is denied
    
    Change-Id: I744f1c6b9c7aae91b9363bba6c6987b42f7f0cc9
    BUG: 947055
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/5143
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8404ec28e4216de1783ea6fe19c79789378250a9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jun 26 13:25:22 2013 +0200

    rpm: move the mount/api xlator to the glusterfs-api sub-package
    
    The main glusterfs package included the xlator/api.so file which caused
    a dependency on the glusterfs-api package:
    
      # rpm -i glusterfs-3.4.0-0.6.beta3.el6.x86_64.rpm
      error: Failed dependencies:
      libgfapi.so.0()(64bit) is needed by glusterfs-3.4.0-0.6.beta3.el6.x86_64
    
    Moving the mount/api xlator to the glusterfs-api package will prevent
    the automatic dependency generator to add the dependency to the main
    package.
    
    Change-Id: I4650c40cdfe610b9b69bab07d262093854aa6583
    BUG: 950083
    Reported-by: Vijay Bellur <vbellur@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5255
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f7b1245ca221fd7d4cee626ae358a2ebc933ffdd
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jun 17 13:44:10 2013 -0400

    build: sync glusterfs.spec.in with Fedora glusterfs.spec
    
     * add glusterfs-api and glusterfs-api-devel sub-packages
     * add extras/systemd/glusterd.service. Use it (or extras/init.d/glusterd)
       instead of the Fedora versions.
     * restores ability to build glusterfs RPMs from the dist tarball with
       'rpmbuild {-ts,-tb,-ta} glusterfs-XXX.tar.gz'
     * other minor cleanups mostly to sync with fedora .spec and to build
       from the dist tarball. Any differences will be resolved in the fedora
       .spec in the next release (i.e. beta4 or GA).
    
    (still considering whether to add fedora glusterfsd.{init,service} files
    to glusterfs or remove them from fedora.)
    
    BUG: 950083
    Change-Id: Ibda3cd57b24ef5c2a27446703e718e5044ec546c
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Bala FA <barumuga@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 183546aa2dbfe3371cf155800e2f70057e95e2bc
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Jun 18 11:25:39 2013 +0530

    doc: Move admin-guide to markdown format.
    
    Editing markdown is probably more easier than xml.
    
    pandoc can then be used for conversion to html, pdf and any other necessary
    formats. Note that pandoc has the following input and output formats:
    
    Input: markdown and (subsets of) Textile, reStructuredText, HTML, LaTeX, and
    DocBook XML.
    
    Output:plain text, markdown, reStructuredText, XHTML,  HTML  5,  LaTeX
    (including beamer slide shows), ConTeXt, RTF, DocBook XML, OpenDocument XML,
    ODT, Word docx, GNU Texinfo, MediaWiki markup, EPUB, Textile, groff man pages,
    Emacs Org-Mode, AsciiDoc, and Slidy, Slideous, DZSlides, or S5 HTML slide shows.
    It can also  pro‐ duce PDF output on systems where LaTeX is installed.
    
    All documentation changes can be submitted as changes to markdown and we can
    attempt a periodic documentation refresh on gluster.org.
    
    Change-Id: I5dcf7f79184cd6b6d62ce7065d2faa352622f6ac
    Reviewed-on: http://review.gluster.org/5232
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit fb064ec4e302e59aca9ba8a8d97e4cc2d82d31ef
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 17 13:06:23 2013 +0530

    nfs: Remove afr split-brain handling in nfs
    
    We added this code as an interim fix until afr can
    handle split-brains even when opens are not issued.
    Afr code has matured to reject fd based fops when
    there are split-brains so we can remove it.
    
    Change-Id: Ib337f78eccee86469a5eaabed1a547a2cea2bdcf
    BUG: 974972
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5227
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 03f5172dd50b50988c65dd66e87a0d43e78a3810
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jun 24 08:15:09 2013 +0530

    cluster/afr: Fix fd/memory leak on fsync
    
    Change-Id: I764883811e30ca9d9c249ad00b6762101083a2fe
    BUG: 976800
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5248
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit de31ac421953997ad148aea87f7176b2a10f07c4
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Jun 11 14:14:53 2013 +0530

    cluster/dht: In reconfig handle removed decommissioned nodes
    
    If no decommissioned nodes options are set in the options, then
    clear the conf->decommissioned_bricks.
    
    Change-Id: I426d2bcc874aab21b2eba0b16a580b9a26672ea2
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    BUG: 973073
    Reviewed-on: http://review.gluster.org/5199
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3f72e52c936edf7d1477a69fa3a01f89e0576881
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Jun 21 11:31:11 2013 +0530

    rpc: duplicate request cache for nfs
    
    Duplicate request cache provides a mechanism for detecting
    duplicate rpc requests from clients. DRC caches replies
    and on duplicate requests, sends the cached reply instead of
    re-processing the request.
    
    Change-Id: I3d62a6c4aa86c92bf61f1038ca62a1a46bf1c303
    BUG: 847624
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4049
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4cde70a0e5be0a5e49e42c48365f3c0b205f9741
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jun 17 06:19:47 2013 -0700

    glusterfsd: consider xlator type too in topology check
    
    When cluster.nufa option is enabled, we only change the translator
    type, but leave the translator name as-is. This results in the
    topology change check to conclude that a graph switch is not needed.
    
    Change-Id: I4f4d0cec2bd4796c95274f0328584a4e7b8b5cd3
    BUG: 975599
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5244
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit bc27b7a9e44f2af647b87ab393b0fd1cacd211cf
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Mar 15 10:26:53 2013 +0100

    store: move glusterd_store functions from mgmt/glusterd to libglusterfs
    
    Making the glusterd_store_* functions re-usable will help with future
    changes that need to read/write lists of items.
    
    BUG: 904065
    Change-Id: I99fb8eced76d12d5a254567eccff9790b43d8da3
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4676
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d7e80787fc61a4fe9e72ff80565dc720ac29441a
Author: Anand Avati <avati@redhat.com>
Date:   Sun Jun 16 06:19:52 2013 -0700

    gfapi: fix read past EOF in glfs_preadv()
    
    When syncop_preadv() returns 0, we are returning @size as-is
    (without modifying user passed buffer). This results in
    junk data being read when read offset is at or beyond EOF.
    
    Change-Id: I8aa9c957359f9a52833b944b452f501b6f5538d3
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5236
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-by: José Rivera <jrivera@redhat.com>
    Tested-by: José Rivera <jrivera@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cc9ca7d2b2f5c91d80265c28ca724cb233c2bd77
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 22 15:18:19 2013 +0530

    cluster/afr: Perform delayed changelog wakeups for anon fd
    
    Problem:
    Nfs xlator never does open on a file for performing writes,
    afr does not perform changelog wakeup for this fd so operations
    which do metadata operations as soon as the data operations are
    completed perceive a delay of 'post-op-delay-secs'.
    
    Fix:
    Perform changelog wakeup on anon-fd if the fd with same pid is
    not present in inode-list.
    
    Note:
    This approach is a short-term fix. A proper fix needs a new domain
    for taking metadata locks so that data/metadata locks don't compete
    with each other.
    
    Change-Id: I253afb289eadf30c7951e56fb2c4840d7132f5e4
    BUG: 966018
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5066
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bb1d5e826f6c64092a03bf292e72fb314e2b4a2d
Author: Michael Brown <michael@netdirect.ca>
Date:   Fri May 3 14:32:23 2013 -0400

    nfs/mount3: fix crash in subdir resolution
    
    * __mnt3_resolve_export_subdir_comp: if nfs_entry_loc_fill fails,
      mres->resolveloc does not contain valid data
    * gf_log should use 'gfid' instead of mres->resolveloc.inode->gfid
    * fixes a crash if program flow gets to this line
    
    Change-Id: Idb0d6f97ea73eaf9056d28267ad7a42aa8cf6579
    Signed-off-by: Michael Brown <michael@netdirect.ca>
    Reviewed-on: http://review.gluster.org/4948
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>

commit 1d6f6a65d76f0e8dc9b62fdae305b6246ce268c5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed May 15 15:54:29 2013 +0530

    protocol/server: print connection-id in fop failure logs.
    
    Currently we have tuple (server-xlator-name, callid) for identifying
    a call. However it does not uniquely identify the operation when there
    are multiple clients (since operations from all clients go through same
    server). Adding connection-id resolves this ambiguity.
    Also printing connection-id helps diagnose failures associated with
    connection state (like fds, locks).
    
    Change-Id: I13563bd06ee9b72fc1a10d239f77db5183658573
    BUG: 963540
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/5011
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 78a2e27ec7d85ed5e915817c9bcc080919791b7b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue May 7 15:58:45 2013 +0530

    glusterd: Log peer op status at the appropriate time
    
    Change-Id: Ia8e1af082078f2f791708ba4faa4992bf291dd6e
    BUG: 961339
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/5023
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bb5ded9bee8cf7671bcb7c06e9ebca91f7bf8d67
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue May 14 09:59:45 2013 +0530

    glusterd: Disable transport before cleaning up rpc object
    
    Problem:
    rpc_transport object, which is part of rpc_clnt, is destroyed
    prematurely. This is because, rpc_transport object is ref'd by socket
    layer and rpc layer. These ref's, until the synctask'izing of
    operations, were unref'd sequentially in the epoll thread.
    With more threads at play, the sequential unref guarantee is off.
    
    Fix:
    Shutting down the transport before proceeding with cleaning up of
    rpc_clnt object would serialize the unref's on the rpc_transport object
    and thus eliminating the race.
    
    Also, we don't store the address of brickinfo in brick's rpc notify
    function, to avoid the possibility of referring a freed brickinfo.
    Instead we use a string based id to 'reach' the corresponding brickinfo.
    
    Change-Id: If2739e2eeaee1e8b071ab2b6754b7ea0f81cfceb
    BUG: 962619
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5000
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bda60de187aadc885bbc705ccb9317f680f4b9d3
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Jun 17 16:28:17 2013 +0530

    nfs: log stale mount errors occasionally
    
    log the state mount errors only occasionally so
    as not to fill log file with too many of them.
    
    Change-Id: Ib5a2485dc2ce3a181cff34bbb6d7aba17a2e4d4d
    BUG: 804301
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/5229
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit eb6b81e1fc182daba4d202d15362250eee1c86d6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jun 17 10:56:55 2013 +0200

    protocol/rpc: move latest added procedures to the end of the array
    
    While looking at the newly introduced procedures FALLOCATE and DISCARD,
    it seems that these were added with already existing procedure numbers.
    This makes the protocol incompatible with existing roll-outs.
    
    It is very confusing when new procedures are added somewhere in the
    middle of the array. This will cause the number of existing procedures
    to change. It is much preferred to add new procedures at the end of the
    array. This changes not only corrects the enum that generates the
    procedure numbers, but also the ordering in the client and server
    fops-array for clarity.
    
    Correcting this greatly simplifies adding support for these new
    procedures in Wireshark and will prevent confusion to the people reading
    network traces (with or without Wireshark).
    
    Change-Id: Ib9e7978531d016c7230d756b855cb94cb0793b0f
    BUG: 974976
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5215
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 74fe3057270fabb79f311414dd9c47c6245b52c7
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue May 28 14:23:49 2013 +0530

    rpc: Cleanup rpc object in TRANSPORT_CLEANUP event
    
    rpc_transport object should be alive as long as the rpc_clnt object is
    alive. To ensure this, on rpc_clnt's last unref, we cleanup the
    corresponding rpc_transport object and complete the rpc_clnt cleanup
    later, in a bottom-up fashion.
    
    Introduced rpc_clnt_is_disabled, to allow higher layers to differentiate
    between the 'final'[1] disconnect triggered from upper layers, and a
    normal disconnect. This differentiation helps in cleaning up resources,
    at higher layers, in a race-free manner.
    
    [1] - 'final' here means that the rpc and the associated connection, is
    not going to be used anymore. eg - glusterd_brick_disconnect on
    volume-stop.
    
    Change-Id: I2ecf891a36e3b02cd9eacca964e659525d1bbc6e
    BUG: 962619
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5107
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d6e5c6d8c489063df5aca8998903e11afee8439d
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Jun 3 16:44:21 2013 +0530

    nfs: option to disable acl
    
    1. Option to disable or enable acl with nfs.acl boolean
       option.
    
    2. Deregister the acl service with the portmapper service
       when no longer required.
    
    Change-Id: I6562b6b40138d040aa2bf1e5641f4c0e0e9f9d09
    BUG: 970070
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/5136
    Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f857def7631f660b3e6574c58debdd4d37731f4f
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Jun 7 15:03:46 2013 +0530

    glusterd: Ignore directories matching *.tmp in store
    
    store being glusterd's persistent store under /var/lib/glusterd/
    
    Change-Id: I1c01a09a8ce4a73ea612f05e7f14d4ab39ad1628
    BUG: 971796
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5177
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dccd014947131fabfb14ab96ced05cbc685f7076
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Jun 11 13:15:23 2013 +0530

    cluster/afr:  Improvement in logging of self heal completion status
    
    Problem:
    As the end of the self heal, message logged by
    "afr_self_heal_completion_cbk" is inadequate to determine what exactly failed
    during the course of afr self heal. It is worth to have knowledge of what all
    types of self heal got triggered for an entity and whether the status is success
    or failure.
    
    Fix:
    At the end of self heal, it will log information about out of 4 types of self
    heal (gfid or missing entry self heal, metadata, data and entry self heal),
    who all got triggered and who all got failed or successful at the end.
    
    Change-Id: I5360762fbd7d391ac4c6af6706b4835c5801835a
    BUG: 968301
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5106
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 77e6caa440fb27d97fc9c6330c3598763c2351f5
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Wed Jun 12 16:59:13 2013 +0530

    libglusterfs: Fix circular buffer to dump entries if count is less than 1024
    
    Problem:
    To dump the values present in the circular buffer, index always
    moves from current index to used_len. But if circular buffer is not
    completely filled even once then next index to be filled  and used length
    value are always same which means it will never dump any value.
    
    Fix: Modified the logic of buffer traversing to dump values so that  it
    will still maintain FIFO and cover both the cases where buffer is either
    partially filled or being used more than once.
    
    Change-Id: If73a5e481cca1751d57aba1136c2d25d23ce073c
    BUG: 972459
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5197
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 4ec4ae08c346c3e75c013bbf0529b3d7dd9a60c0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jun 12 09:55:26 2013 +0200

    rpm: correct AutoRequires filtering on recent Fedora
    
    Recent Fedora releases (F17 and newer) do not need the
    __requires_exclude macro for filtering automatically generated Requires
    for <xlator>.so files anymore. It is already sufficient to filter each
    <xlator>.so from the Provides.
    
    This prevents the following (harmless) warning from being printed during
    build:
    
        Ignoring invalid regex -P ^(?!lib).*.so.*$
    
    BUG: 972465
    Change-Id: Icc36f421d283ddb993c8f31e0dfdaa4f27135bb7
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5203
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cede8eb3d0007dcd6eb8929d5031ff25be955ed6
Author: Brian Foster <bfoster@redhat.com>
Date:   Tue Jun 4 11:54:43 2013 -0400

    gfapi: async discard support
    
    From: Bharata B Rao <bharata@linux.vnet.ibm.com>
    
    Add glfs_discard_async() to meet QEMU's discard requirements.
    
    BUG: 963678
    Change-Id: I97723107fca88dd96cddc08cd67a286645a37922
    Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5144
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 17f287172413dc04244781aa5302a0e4f10e2777
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu May 23 12:19:42 2013 -0400

    glusterfs: discard (hole punch) support
    
    Add support for the DISCARD file operation. Discard punches a hole
    in a file in the provided range. Block de-allocation is implemented
    via fallocate() (as requested via fuse and passed on to the brick
    fs) but a separate fop is created within gluster to emphasize the
    fact that discard changes file data (the discarded region is
    replaced with zeroes) and must invalidate caches where appropriate.
    
    BUG: 963678
    Change-Id: I34633a0bfff2187afeab4292a15f3cc9adf261af
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5090
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d1ccc4e400728d90f2ef7904661f53deb7199123
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed May 8 08:54:11 2013 -0400

    gluster: add fallocate fop support
    
    Implement support for the fallocate file operation. fallocate
    allocates blocks for a particular inode such that future writes
    to the associated region of the file are guaranteed not to fail
    with ENOSPC.
    
    This patch adds fallocate support to the following areas:
    
    	- libglusterfs
    	- mount/fuse
    	- io-stats
    	- performance/md-cache,open-behind
    	- quota
    	- cluster/afr,dht,stripe
    	- rpc/xdr
    	- protocol/client,server
    	- io-threads
    	- marker
    	- storage/posix
    	- libgfapi
    
    BUG: 949242
    Change-Id: Ice8e61351f9d6115c5df68768bc844abbf0ce8bd
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4969
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 328ea4b16a276b0e65ca719f60b82ce851dda848
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 15 14:46:57 2013 +0530

    mgmt/glusterd, socket: Change logging for brick disconnects
    
    For unix path based sockets, the socket path is
    cryptic (md5sum of path) and may not be useful for
    the user in debugging so log it in DEBUG.
    
    Changed logging in brick_rpc_notify to log brickinfo
    for disconnects.
    
    Change-Id: I69174bbbbde8352d38837723e950ad8fc15232aa
    BUG: 963153
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5009
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 22d821969a7204d09339b1a52a1d38e609e5aa86
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jun 7 15:45:26 2013 +0530

    cluster/dht: Make sure loc has gfid
    
    Problem:
    In some code paths neither loc->gfid nor loc->inode->gfid
    is populated which leads to EINVAL for linkfile setattr
    in dht_linkfile_attr_heal.
    
    Fix:
    Populate loc->gfid before dht_linkfile_attr_heal.
    
    Change-Id: I062770e6f6eaead304eff1dae81f8588a3b97eed
    BUG: 971805
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5178
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 214dccb317437dab5464456a4eb30c88444370e7
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jun 6 10:46:57 2013 +0530

    glusterd: Add a cmd for getting uuid of local node
    
    Usage: gluster system:: uuid get
    
    This is needed since we generate uuid of a node in a lazy manner. ie, we
    generate a uuid for the node only on the first volume or peer operation,
    when the node needs an external identity.  With this command, we can
    force[1] the uuid generation, without a volume or peer operation performed.
    
    [1]: Querying for uuid (or uuid get), forces uuid to come into
    existence.
    
    Change-Id: I62c8b6754117756aa4d773dd48af4ddeb1a1d878
    BUG: 971661
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5175
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 50ae4e3eee81b746df60ce723dfe1c5659fa6fba
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Mon May 27 13:13:03 2013 +0530

    nfs: gluster volume set help shows null as default value
    
    Bug(967445): The default value for all nfs options is displayed as "(null)"
    
    Fix: Changed nfs options to show default value.
    
    Change-Id: I3b1f27439c19a6655f7dcc7891df40706db9e474
    BUG: 967445
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/5098
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5eae1db04bb9125032eb31c456d29939ad0f3a03
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 31 14:30:58 2013 +0530

    cluster/dht: Fix unused-but-set-variable warnings
    
    Change-Id: Ie2b2dc54aa0d500c35752c72d3b562bcc05b1fc2
    BUG: 969336
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5123
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d68fbc3f817831a676d60de7be5b095967aadc7a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu May 16 18:13:10 2013 +0530

    mgmt/glusterd: Set task op at the time of task-id set
    
    Problem:
    If a remove-brick start is executed on m1 with brick from m2
    on local subvolume no rebalance process is launched. Because of
    this volinfo->rebal.op is not set. This leads to volume status
    failures.
    
    Fix:
    Set rebal.op even when the reblance process is not started.
    
    Change-Id: I71c7e6f09353be14c1e8edca3c8685ebfdf226d6
    BUG: 964059
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5030
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d402b07952a7d08f36b2a8602b59032da9339508
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu May 9 11:28:58 2013 +0530

    cluster/dht: Ignore ENOENT errors for unlink of linkfiles
    
    If unlink of linkfile returns ENOENT, do not fail unlink.
    Proceed with unlinking of cached file.
    
    Change-Id: If7cec92b40c39d68dd9c3606c6c2c3a6bd67d27b
    BUG: 966848
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4971
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 31f58221811cf901f02059a4751b20483d26d79d
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Mar 1 16:18:26 2013 +0530

    template: A minimal example xlator to build on
    
    This xlator is intended to save new GlusterFS developers
    from fighting it with autotools.
    
    How to add template xl onto the xlator graph?
    [..]
    
    volname-template
    type testing/features/template
    subvolumes volname-dht
    end-volume
    
    [..]
    
    Change-Id: If513284bb590be7c3b093054108dba2883064190
    BUG: 916985
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4604
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 68a97ece53ec1da205a4da6da5d9d7f8b58b3f5e
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri May 17 11:00:29 2013 +0530

    cli: Remove unused port info from peer status.
    
    Problem: "gluster peer status" on some nodes gives port info and fails to give
    on other. But it is a hard coded value.
    
    Fix: Removing the port info from command
    
    Change-Id: I919f0349f252e658bfc13e60bb8e171da32eaf25
    BUG: 964026
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5027
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7413ed951f9b5615dc63f94a8e702cb8f6a8bd98
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 22 11:59:27 2013 +0530

    cluster/afr: Avoid order mismatch in blocking entrylks
    
    Problem:
    When taking blocking entrylks, afr orders the entrylks based on
    uuid_compare of gfids of parent dirs, if they are equal then it orders
    them based on the basenames. While this approach works fine, the
    implementation assumes loc->gfids to be populated at the time of
    the comparison, but loc may have gfid in loc->inode->gfid instead
    of loc->gfid which was leading to order mismatches and dead-locks.
    
    Fix:
    Implemented loc_gfid which gives gfid by checking both loc->gfid,
    loc->inode->gfid. Used this for ordering the blocking entrylks.
    
    Change-Id: Ib0db36bbaf0df09fa87c3c3bb6a834db74fc2154
    BUG: 965987
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5062
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5c1710ed60ccb151ccd7a2890b24bb99518d36da
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jun 4 15:20:45 2013 -0400

    transport/socket: fix connect/disconnect races
    
    We might receive a connect request while a disconnect is still in
    progress, requiring more states and (the return of) poller generation
    numbers to avoid redundant pollers.  We might also get either kind of
    request from within our own rpc_transport_notify upcall, so we have to
    avoid locking and use the PLEASE_DIE state instead.
    
    Change-Id: Icbaacf96c516b607a79ff62c90b74d42b241780f
    BUG: 970194
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/5137
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dbfe779f3049e6fbc2394bdacdb57165d51dc3f3
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Jun 4 16:43:35 2013 +0530

    cluster/dht: Prevent crash in dht_linkfile_lookup
    
    Assign local = frame->local before dereferencing
    local->linkfile.linkfile_cbk. Additionally, fail if
    op_ret is non_zero.
    
    Change-Id: I96a2f34ba29887da9ccaae38a644431cf7c43265
    BUG: 966858
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5141
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0c1916f3e1eb81aa81dc2d62e97f46880390838c
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu May 23 12:19:33 2013 +0530

    glusterd-syncop: Fix unlocking and collating errors
    
    * Only those peers which were locked need to be unlocked.
    * Fix location of collating errors in callbacks. The callback functions
      could miss collating errors if there was an rpc error.
    
    Change-Id: Ie27c2f1ec197da4f5077a4d6e032127954ce87cd
    BUG: 948686
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/5087
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a72e77f7bc5abfa739f19f6d02e7cf94b138c477
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue May 21 14:21:31 2013 +0530

    cluster/dht: Set layout when inode is present
    
    Problem:
    Lookups in discovery fail with ENOENT so local->inode
    is never set. dht_layout_set logs the callstack when
    the function is called in that state.
    
    Fix:
    Don't set layout when lookups fail in discovery.
    
    Change-Id: I5d588314c89e3575fcf7796d57847e35fd20f89a
    BUG: 965434
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5055
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3f5e575a0744488b4a1719c3e61864c3abc9ac22
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu May 2 12:56:46 2013 +0530

    system/posix-acl: check for the sticky bit of the parent directory
    
    * While creating links, check if there is sticky bit set for the parent
      directory and whether the sticky bit permits the user to create the link.
    
    Change-Id: Ic0d09d9ed579c4eb47462c71602a3a60cc7d3bc1
    BUG: 958691
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4934
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a3e593f9f17cb1e68db97bb5a0d8074793a33964
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri May 31 10:07:57 2013 -0400

    cluster/dht: Return success in dht_discover if layout issues
    
    We cannot heal in dht_discover, as it is a gfid based lookup, and not
    path based. So, returning error here would lead to app's to see failure.
    
    Also, update the layout in inode_ctx even if it has anomalies. Let
    subsequent heals fix the issue.
    
    Change-Id: I2358aadacf9a24e20a22ab0a6055c38c5eb6485c
    BUG: 960348
    Original-author: shishir gowda <sgowda@redhat.com>
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4959
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9e974f9311869fb317c9c691ed09e7dd18047248
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 15 12:09:28 2013 +0530

    socket: Prevent extra logging in socket_rwv
    
    Problem:
    If the socket is not even connected socket_rwv fails
    and the error log comes every 3 seconds for every
    re-connect.
    
    Fix:
    Prevent this error log if the socket is not even
    connected.
    
    Change-Id: I963f1345c4b6779dd5491948f7f5c4357a507b67
    BUG: 963088
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5008
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 114c02e54abae9b3cbf0f84bc48132bf1535118e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed May 15 18:18:24 2013 +0530

    mgmt/glusterd: Make sure peerinfo->uuid_str is assigned
    
    Change-Id: I9e2743ab61c8baee92a1dfd376ec4bb145776176
    BUG: 963524
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/5016
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c9eb8d1a3fa02a7542b1efe1ab9878abec46afa8
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu May 30 12:12:40 2013 +0530

    cluster/afr: Removed misleading log from afr_start_crawl
    
    Problem: If it is fresh volume with no files created the xattrop directory is
             not present. If crawl happens in that time, lookup for xattrop
             directory will fail and it results in  printing a misleading log.
    
    Fix:     Changed misleading log.
    
    Change-Id: Iae5da3e8423564d64096f88abdaf8c98e4935840
    BUG: 928575
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4993
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3c22cf86ad244f87dafd9b7a9f82331968879c15
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed May 22 09:58:15 2013 +0530

    cluster/dht: Handle linkfile creation with EEXIST error
    
    If linkfile create fails with EEXISTS, then check if the file
    is a linkfile for the same file. If not, return the error
    
    Change-Id: Iab42db54422dea69de0049b5196365e65edadd91
    BUG: 966858
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5060
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 599c6b472869cfaf0058e7b169de204450a41948
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Apr 30 13:03:08 2013 +0530

    glusterd-volgen: Improve volume op-versions calculation
    
    Volume op-versions calculations now take into account if an option,
     a. enables/disables an xlator, or
     b. is a boolean option.
    This prevents op-versions from being updated when a feature is disabled.
    
    Also, correctly close the dynamically loaded xlators in
    xlator_volopt_dynload() and prevent leaks.
    
    Change-Id: I895ddeeec6f6a33e509325f0ce6f01b7aad3cf5c
    BUG: 954256
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4952
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 003713139c8a7830a90a40dfead72f8299c17e31
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon Mar 18 14:44:20 2013 +0530

    cluster/dht: Linkfiles creation with correct uid/gid
    
    If renames are done with different uid/gid (non-owners), then we would
    end up with incorrect uid/gid.
    
    The fix is to create linkfiles, and heal the uid/gid as root:root. This
    preserves our notion of creation as root:root and heal the uid/gid as
    root:root in all paths. Additionally, we need to consider uid/gid from
    only src_cached subvol, and not from linkfiles.
    
    rename is also done as root:root if done on linkfile, as setattr of ownership
    on linkfile is done after the rename
    
    Change-Id: Icb5d431dc42da9c02dfae81980e3fe769a47a274
    BUG: 884597
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4682
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 39ae62c39662a37fef9d0809438482ce441a98e0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Apr 12 11:06:44 2013 +0530

    protocol/server: Change logs to give more info on disconnects
    
    Change-Id: I8304a12df417be164c564e0696f72c3334f21569
    BUG: 952138
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4824
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c9bf5e6d2897de488967f5d736a5b9898b3deb94
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon May 6 19:18:21 2013 +0530

    cluster/dht: Do not open fd in migration check/complete for non fd ops
    
    if local->fd == NULL, then in dht_migration_check_complete, do not do
    open call. Let the layout get updated, and proceed with invoking the
    registered target_fn.
    
    if local->fd == NULL, do not call dht_rebalance_in_progress_check for
    truncate fop, but proceed with truncate2.
    
    Change-Id: Ia5a5d40bcea7bfb320ef7096af1e035b8847d4ff
    BUG: 960055
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4958
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f162456794ae78d29edc42a2c040c1037145f24d
Author: shishir gowda <sgowda@redhat.com>
Date:   Fri Apr 26 15:33:42 2013 +0530

    cluster/dht: getxattr linkto as root:root
    
    In path based op's like truncate, we use getxattr instead of
    fgetxattr call. These can fail with permission denied issues
    as linkto file creation, and setattr of ownership is not atomic,
    and in cases where setattr failed (subvols down..)
    
    The fix is to perform getxattr as root:root as it is a internal
    fop. fgetxattr, bypass the access check, as it already has a valid
    open fd.
    
    Change-Id: Ie221c9172e3c1c7ed4e50c8782d362826910756f
    BUG: 957074
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4890
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit afd669d6bde01020259ec57298c8335bc2542e4a
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed May 8 17:37:00 2013 +0530

    statedump: Print entries in cb buffer in FIFO order
    
    Currently cb buffer was being printed in LIFO order, which
    is was against the percieved notion of logs having older
    entries printed before newer entries in the state dumps.
    
    Re-did the loop to prevent crash as when w_index == 0, we
    would access cb[w_index - 1].
    
    Change-Id: Idd085f73fa6937e506a2a1925e42fbcfd2d9bb1c
    BUG: 966847
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4968
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8b65fa6575de57fc5c5a5e7db98eebfd2a3aa18f
Author: shishir gowda <sgowda@redhat.com>
Date:   Fri May 3 12:27:07 2013 +0530

    tests/bugs: Increase timeout for rebalance completion check
    
    Change-Id: Ic299c0d7b3996f6e85f9627430efbdf3f9ea0a8f
    BUG: 884455
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4942
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bca2449cb59727196d328462c912a1be20117b9d
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon May 13 09:51:49 2013 +0530

    cluster/dht: Do migration inprog/complete check only if ENOENT
    
    Additionally, update op_errno to the lasted failure. If failures
    found in complete_check, error returned would be EUCLEAN instead
    of the right failure (in this case ENOENT)
    
    Change-Id: Ib813867f4b817af651627b9ea07b0b09fa2b26ce
    BUG: 966852
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4989
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1afbd1e8998a949695f008fd1403ea228eb42bd1
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu May 30 17:21:05 2013 -0400

    cli: set min-op-version and max-op-version for getspec
    
    Change-Id: I2185df5d6b560d9367ae404c91812048e1655180
    BUG: 969193
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/5119
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 83e4a149bd69d13fdd6fd4c80e603e04d15ff8e3
Author: Anand Avati <avati@redhat.com>
Date:   Fri May 3 05:44:17 2013 -0700

    api: Fix api.so and libgfapi.so build time dependency
    
    Not all versions of autoconf handle dependencies expressed
    as "A: B". Use the xxx_DEPENDENCIES variable to make it
    version independent
    
    Change-Id: Ia0b13399d0bf10995d9845e04cd9eb3ef6518dbe
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5118
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0f214cdb0e784266440deceff4770b383bab1daf
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon May 20 18:39:11 2013 +0530

    nfs: update nfs.addr-namelookup description
    
    replaced rpc-auth.addr.* with nfs.rpc-auth-* in
    keeping with the latest option exposed to the user.
    
    Change-Id: I418354a4d171dae28dd0befe8ba9e5ee893cd013
    BUG: 965025
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/5049
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7646169f20d2e2f23c6033347f019ee60521a524
Author: Anand Avati <avati@redhat.com>
Date:   Thu May 2 20:01:18 2013 -0700

    gfapi: add new API glfs_dup() to copy a file descriptor
    
    Duplicate a glfs_fd file descriptor. Inherit the internal
    fd_t with a reference.
    
    Change-Id: Ib30e9a46b608b9f78202957f4dab6ba6265a9ec0
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5109
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit deaf7574a6cb519cf678196476697db9fe69edd0
Author: Anand Avati <avati@redhat.com>
Date:   Wed May 29 03:15:19 2013 -0700

    api/Makefile: link api.so against libgfapi (and dependencies)
    
    Samba opens vfs_gluster.so with dlopen(..,RTLD_LOCAL). This makes
    the symobls in the shared module and the library it exclusively
    links against (specifically gfapi) not resolvable from the .so
    files which are opened in turn within (like xlator .so files)
    unless explicitly linked against the dependent libraries.
    
    This is not otherwise required in case of glusterfsd as the main
    executable symbols are always available for resolution from
    dlopen()'ed shared objects, making Samba's vfs_glusterfs
    requirement unique, but luckily not incompatible.
    
    Change-Id: I894c521daade7d46ec5bf07793f2eea02ebc9700
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5105
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ac8deb16b5f0aa131373f945cec205af90eaad4d
Author: Anand Avati <avati@redhat.com>
Date:   Wed May 29 03:12:19 2013 -0700

    socket: convert socket functions to file scope (static)
    
    The function names used in socket.c conflict with Samba's
    socket functions (samba.git/source4/lib/socket/socket.h). Convert
    our functions to file scope as they are anyways not called across
    files.
    
    Change-Id: If98ae557d3e2868f257c021b283ede6a5e92de02
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5104
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b0540090648a7670ef52e6733d127656f5aca5ed
Author: Ram Raja <rraja@redhat.com>
Date:   Sun May 26 21:55:23 2013 +0530

    configure.ac: add build option for glupy
    
    Check whether Python.h, glupy dependency, is installed in the system.
     ('Python.h' part of python-devel or python-dev package.)
    
    Allow following build options:
     --enable-glupy   build glupy; If dependencies are not met, abort
                      configure script run with error.
    
     --disable-glupy  don't build glupy even if dependencies are met.
    
     default          build glupy; If dependencies are not met, don't build
                      glupy and allow configure script run with warning.
    
    glupy-specific dependencies:
     python2.x, python-devel/python-dev package
    
    Change-Id: Ia495dd00cac7d12ad76645c8576a0adc0cb5d590
    BUG: 961856
    Signed-off-by: Ram Raja <rraja@redhat.com>
    Reviewed-on: http://review.gluster.org/5093
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7d0cf52a344e476963fe97e71f86488d5bb17b1c
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Apr 19 15:16:56 2013 +0530

    glusterd-volgen: Enable open-behind based on op-version
    
    This patch enables the open-behind by default only when the op-version
    allows it. Also the volume op-version calculations take account of this
    enablement.
    
    Change-Id: Idf7a3c274ec4828aafc815cdd1df829ecb853354
    BUG: 954256
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4866
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ea982a764b7cb447eb866129fef2cfafaa48eb6a
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed Mar 20 11:06:19 2013 +0530

    performance/write-behind: Enable write-behind when strict_O_DIRECT is not set.
    
    When open() with O_DIRECT happens, write-behind was being disabled for the
    fd irrespective of strict_O_DIRECT option. This commit disables write-behind
    only when strict_O_DIRECT is enabled.
    
    Change-Id: Ieef180e52910c3bf64d46b26b0e5dc3b8542f6d2
    BUG: 923556
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4697
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 19a6b34358cb2b12aec0eba1659fca65a50aa3a3
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun May 26 13:37:50 2013 +0530

    doc: Move relevant files out of legacy.
    
    Change-Id: Iff9166dd7baa3d60b70ffab5ce9a692d211fa4fb
    BUG: 811311
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5091
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9e702dd4001ff7937c50aacfe0690e0c40699737
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue May 7 13:09:05 2013 +0530

    protocol/client: Prevent excessive logging of client's "disconnect" messages.
    
    Problem: Currently when gluster volume start force is executed, client process
             will talk to glusterd to get the port of the brick. But if brick's path
             is not available it cannot return brick's port. So client process will
             keep connecting and disconnecting from glusterd for port-query which
             is ultimately responsible for execssive logging of disconnect messages.
    
    Fix:     Message will be logged just once at INFO level after the first
             disconnect from glusterd. Afterwards "disconnect" messages will be
             logged in DEBUG mode.
    
    Change-Id: I2b787f3820b5da45e090c562e5698fcfe24a02cd
    BUG: 959969
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4953
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 84e966cc8b6ae06699f8a57bc33d509b30ff777b
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri May 24 12:57:19 2013 +0530

    logging: Fix to avoid excessive logging.
    
    mem_get function: Log message related to mem_pool
    calloc is removed  as its been calculated in mempool
    'stats'.  This messgae is consuming nearly half of
    the total log messages in DEBUG mode.
    
    dht_hash_compute function: Changed log level from DEBUG
    to TRACE.
    
    client_fdctx_destroy function: Changed log  level from DEBUG
    to TRACE.
    
    Change-Id: Ic948db0419e76df4e95ebd0cabaf66eadbaada6b
    BUG: 966851
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/5086
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1a5e8638a177ac90177ae1b749b89c984930c875
Author: Anand Avati <avati@redhat.com>
Date:   Tue May 21 16:27:09 2013 -0700

    gfapi: handle graph switch (cwd, fds, locks)
    
    - Migrate open fds to new graph
    - Migrate locks held in open fd to new fd
    - Refresh CWD, so resolution of relative paths happens on refreshed
      inode (on new graph).
    
    Change-Id: I4b18083b9b290107ebda1f917fc85b635ab72fb4
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5059
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>

commit cb50f94f4299856046e1f1677ad1c8152de06136
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed May 15 17:30:30 2013 +0530

    glusterd: Allow volume start force to succeed if brick directories are recreated
    
    Change-Id: I4fc3c5c829adca256bb131f4a2722abc95741158
    BUG: 963665
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/5020
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 689618e2fc0cecbfa06ef02b6c259a1a8502971f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu May 23 11:25:27 2013 +0200

    extras: prevent "glusterd dead but subsys locked"
    
    Commit b5bf14a6 added support for a file under /var/lock/subsys,
    Hoewever, killproc does remove the $PIDFILE which cases subsequent
    checks on its existence to fail. When glusterd was stopped successfully,
    the $PIDFILE has been removed already, there is no need to try to remove
    is again.
    
    Upon executing '/sbin/service glusterd status', the message 'glusterd
    dead but subsys locked' would be returned because the file under
    /var/lock/subsys was not removed.
    
    Bug: 960476
    Change-Id: I781fe463e3c5472e42d668155cee4f63d349a568
    Reported-by: Satheesaran Sundaramoorthi <sasundar@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5074
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2a2244972082c026061a08c76d03ec2f19b0d438
Author: Anand Avati <avati@redhat.com>
Date:   Thu May 23 23:14:30 2013 -0700

    gfapi: ignore NULL and -1 parameters in glfs_set_logging()
    
    Permit changing either logfile or level by specifying the other
    as -1 or NULL respectively.
    
    Change-Id: I7df05db7b613c57e0106a5cce846ae26d2a160d4
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5085
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c04a0ca7cf3a9775e21d51f9bdaa113b0f19f051
Author: Anand Avati <avati@redhat.com>
Date:   Wed Apr 24 00:51:12 2013 -0700

    pkg-config: present API version and not package version
    
    This way PKG_MODULE() autoconf test checks for required API
    rather than release version (e.g required API could be in all
    all of 3.4.5, 3.5.1, 3.6.4 etc.)
    
    With the first "release" of gfapi, the current version (4) will
    be frozen.
    
    Version 3 is sufficient for QEMU's requirement. Version 4 is
    necessary for Samba VFS
    
    Change-Id: Iada3a4c88b9c67413dcd57004fd8a62926a21b42
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4932
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ed11e88b77fe45acd1181728435bb644607a2b22
Author: Anand Avati <avati@redhat.com>
Date:   Sun May 19 23:31:38 2013 -0700

    gfapi: provide stable st_dev in stat structure
    
    Samba depends on st_dev being unique and stable for different
    filesystems (it uses st_dev+st_ino as key to store metadata of
    a file).
    
    Change-Id: Ia022fabadfb5ef3fc9724c1b1ca86f1a20f98af9
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5045
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 05aaec645a6262d431486eb5ac7cd702646cfcfb
Author: Anand Avati <avati@redhat.com>
Date:   Thu May 2 08:00:22 2013 -0700

    dht,posix: support for case discovery
    
    This is support for discovering a filename in a given directory
    which has a case insensitive match of a given name. It is implemented
    as a virtual extended attribute on the directory where the required
    filename is specified in the key.
    
    E.g:
    
      sh# getfattr -e "text" -n user.glusterfs.get_real_filename:FiLe-B /mnt/samba/patchy
      getfattr: Removing leading '/' from absolute path names
      # file: mnt/samba/patchy
      user.glusterfs.get_real_filename:FiLe-B="file-b"
    
    In reality, there can be multiple "answers" as the backend filesystem is
    case sensitive and there can be multiple files which can strcasecamp()
    successfully. In this case we pick the first matched file from the first
    responding server.
    
    If a matching file does not exist, we return ENOENT (and NOT ENODATA).
    This way the caller can differentiate between "unsupported" glusterfs
    API and file not existing.
    
    This API is used by Samba VFS to perform efficient discovery of the real
    filename without doing a full scan at the Samba level.
    
    Change-Id: I53054c4067cba69e585fd0bbce004495bc6e39e8
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4941
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9b645be90f76e71f3d1587db66c0c1f9599e5b2d
Author: Anand Avati <avati@redhat.com>
Date:   Sun Apr 28 12:22:54 2013 -0700

    gfapi: link inodes in relevant entry FOPs
    
    Do not let inode linking to happen only in lookup(). While
    that works, it is inefficient.
    
    Change-Id: I51bbfb6255ec4324ab17ff00566375f49d120c06
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4931
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 79387af286421c0668f21a2c34adc9f18f6da464
Author: Anand Avati <avati@redhat.com>
Date:   Sun Apr 28 02:01:01 2013 -0700

    syncop: copy inode pointer in readdirplus
    
    Change-Id: I9ab2b8ac2da9fe13f56b8b08f715a0b603ece0cb
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4930
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5b2117650a8c8e83ce9ea6f325f8e63053a1af2c
Author: Anand Avati <avati@redhat.com>
Date:   Sat Apr 27 11:40:02 2013 -0700

    md-cache: support negative xattr entries
    
    Add support for negative xattr caching. For this, we need
    to fetch xattrs in every opportunity (including readdirplus)
    in order to treat missing key in cached dict as negative entry.
    
    This is crucial to detect missing ACL xattrs in Samba workload.
    
    Change-Id: I918a2ef4ab804724256f7546b15e808332ed518d
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4929
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e9ac9d4d5c1c3e9f3f0b5c80a881d67a675eccef
Author: Anand Avati <avati@redhat.com>
Date:   Sat Apr 27 21:40:19 2013 -0700

    gfapi: optimistic resolution with ESTALE detection
    
    Enhance the path resolver to be optimistic. Instead of performing
    a wasteful ->lookup() fop for every component in every API call,
    build in speculation logic to consider the previous resolution
    result temporarily, and if it results in ESTALE either later in
    the path resolution or in the FOP, then retry resolution with
    ->lookup() at every level and retry the FOP.
    
    This is the same optimistic resolution/retry logic Linux kernel
    resolver is proposing to use.
    
    Change-Id: Iecbc25248754caf0915cd7205910563ff88ce5e7
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4928
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4f63b631dce4cb97525ee13fab0b2a789bcf6b15
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue May 21 16:29:32 2013 +0530

    cluster/dht: Ignore decommissioned subvol in overlap optimization
    
    Change-Id: Ib727948c6e21b19fd509f258ff0aea1c5d1a84d1
    BUG: 966845
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/5056
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 757d697e586dd73edcd7400d9c6afee19ed49b85
Author: Rajesh Joseph <rjoseph@redhat.com>
Date:   Tue May 21 16:48:12 2013 +0530

    nfs: Unable to resolve FH
    
    Bug (965435):  while deleting files/directory from multiple machines nfs server
    logs show "Unable to resolve FH" error.
    
    Cause: The error is shown whenever the server receives rmdir/remove call and the
    file/directory is already deleted. Server always shows "Unable to resolve FH"
    irrespective of what is the actual error.
    
    Fix: The error message seems little misleading therefore changed the error
    message to display the actual cause.
    
    Change-Id: I4f9c151f737317d618278c59d9f66fe9f46350b8
    BUG: 965435
    Signed-off-by: Rajesh Joseph <rjoseph@redhat.com>
    Reviewed-on: http://review.gluster.org/5057
    Reviewed-by: Santosh Pradhan <spradhan@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 37f707023cb3777dcabd8b4be0d07878f9422025
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue May 21 21:40:31 2013 +0530

    glusterd: Give up biglock during rpc conn cleanup
    
    glusterd could deadlock after a peer-detach command as follows,
    
    1) glusterd_friend_cleanup function 'flushes' out messages in the rpc
    layer's queue, that haven't received a response. At this point, glusterd
    has already acquired the big lock.
    
    2) The side-effect of flushing out the messages is that the
    corresponding call backs are called.
    
    Call backs themselves are executed after acquiring the big lock. This
    results in the big lock being acquired in a nested manner (in the same
    thread),  which causes
    a deadlock.
    
    This can also happen during brick/NFS/SHD disconnect in volume-stop.
    
    Change-Id: Iab3aad143cd8ebbab53ea0b69687f0e7627dc8a9
    BUG: 965533
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5061
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit a387a545b44a553b9aedf1e2f4683c84dee0e6be
Author: John Smith <lbalbalba@gmail.com>
Date:   Sun May 19 19:57:04 2013 +0200

    tests: Change 'volume create' to 'volume create force'
    
    Using 'force' when creating volumes prevents errors when creating bricks in the root partition. This fixes test bug-823081.t for bug-962226
    
    Change-Id: I00996e1ab76713084076507d0aebdb65edc806c8
    BUG: 962226
    Signed-off-by: John Smith <lbalbalba@gmail.com>
    Reviewed-on: http://review.gluster.org/5036
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>

commit 323fe9ec806a4a922fc6f3fd2389368811d6b417
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed May 22 16:20:36 2013 +0200

    rpm: automatically load the fuse module on EL5
    
    The fuse module needs to be loaded before /dev/fuse can be used. On
    RHEL6 and Fedora the module is loaded on demand. RHEL5 needs to load the
    module manually.
    
    This change add a script under /etc/sysconfig/modules/ that loads the
    fuse module on boot and packages it in the EL5 version of
    glusterfs-fuse.
    
    One of the features of GlusterFS is to not depend on additional fuse
    userspace. The conditional requires on /usr/bin/fusermount is not
    needed, this command is never called in the current version (even though
    is it referenced in the sources).
    
    Change-Id: I77028dade54771cb49cea68a517100f73763dc85
    BUG: 947830
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/5070
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4df7a3c4888fbf1e1f84246aeac92af396879ce5
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Wed May 22 15:26:04 2013 +0530

    xlator: NULL terminate volume_options struct
    
    Problem:
    volume_options struct for open-behind and quick-read xlators
    were not NULL terminated.
    
    Fix:
    Make them NULL terminated.
    
    Change-Id: I2615a1f15c6e5674030a219a99ddf91596bf346b
    BUG: 965995
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/5064
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 16b5ec67120e198fb320e13ade9e31d3761b0932
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed May 22 00:18:04 2013 +0530

    syncop: synctask shouldn't yawn, it could miss a 'wake'
    
    Change-Id: I7731fd33ca0c925cc52f8d105275b44fc625a1e2
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5058
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2eed9c78569311e4fa75735d67e8838cc79109a7
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon May 13 17:50:56 2013 +0530

    md-cache: Make options structure NULL terminated.
    
    Change-Id: I8aa4f90ba7e1eecf3f978be04f8550049275464f
    BUG: 765785
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4994
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 277fabf577f95b20c61d65b28f8269e6abca6fee
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon May 20 17:17:05 2013 +0530

    syncop: Remove task from syncbarrier's waitq before 'wake'
    
    Removing task from syncbarrier's waitq after wake could result in a
    subsequent syncbarrier_wake, wake'ing up the already running task.  This
    fix makes the removal from waitq and wake 'atomic'
    
    The root cause and the fix are similar in spirit to what was observed
    in synclock's waitq implementation.
    
    Change-Id: I7dd9e6ad5945742bcda20eb5a06a9376bb18528e
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/5047
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 27b457fad288cc896db3151bf3bc71cce72f5499
Author: Anand Avati <avati@redhat.com>
Date:   Sat May 18 20:35:30 2013 -0700

    quick-read: prune cache on write/[f]truncate
    
    Cache needs to be pruned on write and [f]truncate. The lack of this
    is causing Samba ping-pong test to return wierd 'data increment' values
    during startup.
    
    Change-Id: I9cd6a839bcd02de738d78638211b78f382f58e0a
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/5033
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9a1a4e63992b318dd11bbb81920c0e09059c3dad
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon May 20 18:40:52 2013 +0530

    tests: Increase wait time for nfs mount.
    
    Change-Id: I61815b502c90314ea6924e3046fb9b396ff56e8b
    BUG: 927616
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5050
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c377febe7ac559a6940143db09a092b511647958
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat May 11 14:29:29 2013 +0530

    syncop: Update synctask state appropriately
    
    * Earlier, SYNCOP macro, the only consumer of synctask_yield, would set
    the task->state to SYNCTASK_SUSPEND. Today, we have glusterd having its
    own wrapper macros which don't set task's state. There is also the
    syncbarrier and synclock framework, which also participate in a
    synctask's scheduling (and need to keep a task's state up to date). It
    only makes more sense to leave a synctask's state to the synctask
    library, since its an internal affair.
    
    * Need to 'yawn' before 'yield' to avoid re-running tasks to set
      task->woken appropriately.
    
    Change-Id: Ic7a59e6ebcc46f03e53223ca237668d45a3cba40
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4985
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 10fbae681e072dd6359bf7a8c56e93c541c83b0b
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 14 16:07:03 2013 -0400

    configure.ac: build glupy with installed python
    
    IOW with more than just python2.6. Python2.7 is certainly what's on
    the vast majority of non-RHEL systems that are out there. Also our
    rpm.t regression test will build on epel-5 under mock; RHEL5 has
    Python2.4.
    
    Change-Id: I09c95c1fb6b3498e910ad239c4f0af7f786c3700
    BUG: 961856
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5007
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2b65c50554ec434a6ec9aecaea5d9885cf2aadf8
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon May 13 15:03:22 2013 -0400

    configure.ac: enable-debug change breaks _hardened_build
    
    See RHBZ 955283, and http://fedoraproject.org/wiki/Packaging:Guidelines#PIE
    
    The previous change for BZ 851092 in
    commit 058a736f9e36238c284ca80e7ed5f62434655019
    breaks the ability to enable _hardened_build in release-3.4 and master
    
    BUG: 851092
    Change-Id: Ib298a492fee22dd82042af704fe8cdd34c3e100e
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4998
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b6e78710bfe0905bdaae8ef4fadd2a676f44bdfe
Author: John Smith <lbalbalba@gmail.com>
Date:   Sat May 18 21:01:50 2013 +0200

    Tests: changing calls from 'fstat' to 'fstat64' fixes these tests on 32 bit platforms: bug-858242.t, bug-808400*.t
    
    Change-Id: Ifd85c711a8d16eb3ef17bd1c585acdc34121b12d
    BUG: 962226
    Signed-off-by: John Smith <lbalbalba@gmail.com>
    Reviewed-on: http://review.gluster.org/5034
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 714a2037e96f24d49ac1028bc953bd39ae0363b4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Jan 7 11:05:39 2013 +0530

    rpc-transport/rdma: reap async events in a dedicated thread.
    
    * Also sets srq_limit of srq to 10, so that we'll receive an event
      when we are about to empty the receive buffer list.
    
    BUG: 765051
    Change-Id: I5436166ea21fc963ee15088fc2df743ec4b96ba7
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4378
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 05d2d4a401cb2497185b091e666638e01f1d7f1d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Dec 18 12:47:43 2012 +0530

    rpc-transport/rdma: use rdma-cm for connection establishment.
    
    Till now gluster used tcp/ip based communication channel with
    gluster specific protocol to exchange infiniband addresses.
    
    Change-Id: I9de4db398a0e2af51d3d2d68c2fe42168102b190
    BUG: 765051
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/149
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b62e5ca7ed3b4ddb9b07dc16da1e295a4c28e01f
Author: Anand Avati <avati@redhat.com>
Date:   Fri Apr 26 01:23:13 2013 -0700

    locks: fix leaking entrylk lock structure
    
    When entrylk lock requests are blocked and granted aysnchronously,
    the entrylk lock structure was getting leaked.
    
    Change-Id: Ie3f29f550730189f27745d991b029e50c63e63da
    BUG: 962350
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4991
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2acc8c1f04d0376bedf36f1f746e542422344fa6
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri May 10 10:09:13 2013 +0530

    cluster/dht: Don't do extra unref in dht-migration checks
    
    Problem:
    syncop_open used to perform a ref in syncop_open_cbk so the extra
    unref was needed but now syncop_open_cbk does not take a ref so no
    need to do extra unref.
    
    Fix:
    remove the extra fd_unref and let dht_local_wipe do the final unref.
    
    Change-Id: Ibe8f9a678d456a0c7bff175306068b5cd297ecc4
    BUG: 961615
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4974
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5780e274c78aab671e5fb72d66fec23f90576e51
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu May 16 15:05:09 2013 +0530

    glusterd: Set op_errstr to error string received from peer
    
    ... in case of volume op failure on remote host
    
    Change-Id: I7177dc02369dffa82f217496559532d18b7c7c7a
    BUG: 963628
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/5018
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 692257695fa75ab1264277e33c91709391e2f693
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu May 9 13:16:51 2013 +0530

    client: Reset remote-port on first disconnect from brick
    
    Change-Id: I8940358788a7c4f8be81d705749f668a43422b8e
    BUG: 962930
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4988
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fbfe5b99b14694b252c0fd3b28e2d3490b8212dd
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Apr 18 23:46:37 2013 +0530

    rpc-transport: Moved unix socket options function to rpc-transport
    
    This change removes the asymmetry in the 'layer' (read rpc, transport
    etc) in which transport options were being filled for inet and unix
    sockets.
    
    Change-Id: Iaa080691fd5e4c3baedffa97e9c3f16642c1fc12
    BUG: 955919
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4850
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit db18b17c88c1976f9e523c4c6712c7e444927cc4
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu May 16 10:43:54 2013 +0530

    glusterd: Fix misleading log messages of the kind "Node <n> responded to <n>"
    
    PROBLEM:
    
    glusterd logs coming from glusterd_xfer_friend_add_resp() (wrongly)
    indicate that a node responded to itself, although it actually
    responded to one of its peers.
    
    FIX:
    
    Make glusterd_xfer_friend_add_resp() distinguish between remote host
    and self and print the appropriate hostname.
    
    Change-Id: I2a504eeb058c08a0d378443888eb6f1dc7edc76f
    BUG: 963537
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/5017
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f8d77623ff49ebc60686dcb17978175e861b6634
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu May 9 18:07:59 2013 +0530

    glusterd: Start bricks on glusterd startup, only once
    
    The restarting of bricks has been deffered until the cluster 'stabilizes'
    itself volumes' view. Since glusterd_spawn_daemons is executed everytime
    a peer 'joins' the cluster, it may inadvertently restart bricks that
    were taken offline for say, maintenance purposes. This fix avoids that.
    
    Change-Id: Ic2a0a9657eb95c82d03cf5eb893322cf55c44eba
    BUG: 960190
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4973
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4c0b149d8e7c574186a1ccefd9c74b79f8a06267
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat May 11 14:36:38 2013 +0530

    syncop: Remove task from synclock's waitq before 'wake'
    
    Removing task from synclock's waitq after wake could result in
    a subsequent unlock, wake'ing up the already running task.
    This fix makes the removal from waitq and wake 'atomic'.
    
    Change-Id: Ie51ccf9d38f2cee84471097644aab95496f488b1
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4987
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 845aeb709e0e7e037a5b5afc7bc084d58e7e97ee
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Wed May 15 15:30:33 2013 +0530

    tests: Ensure portmap registration before nfs mount.
    
    Change-Id: I12a660a7dfbe4a2d0428910d762434043395fe02
    BUG: 927616
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/5012
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6612f4d74792016add6d9067f732bad999d13b80
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 15 13:02:23 2013 -0400

    tests: basic/rpm.t leaves /var/tmp/rpm-tests.* directories
    
    When the test is terminated early because nothing changed that requires
    this test, the /var/tmp/rpm-tests.xxxxxx is not removed.
    
    BUG: 963333
    Change-Id: I98d44ca34f14d62da9d836c41a9015cfb520ff96
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/5015
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8a7cda772d34b96c45714160ce4ec3b0c0d5b29b
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed May 15 12:30:07 2013 -0400

    mount/fuse: enable fuse real async dio when available
    
    fuse has support for optimized async. direct I/O handling via the
    FUSE_ASYNC_DIO init flag. Enable FUSE_ASYNC_DIO when advertised
    by fuse.
    
    performance/write-behind: fix dio hang
    
    Also fix a hang observed during aio-stress testing due to conflicting
    request handling in write-behind. Overlapping requests are skipped
    in pick_winds and may never continue when the conflicting write in
    progress returns. Add a wb_process_queue() call after a non-wb request
    completes to keep the queue moving.
    
    BUG: 963258
    Change-Id: Ifba6e8aba7a7790b288a32067706b75f263105d4
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/5014
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 68712c33b4c792449e7d49ae348f96f97175bbd9
Author: Ram Raja <rraja@redhat.com>
Date:   Tue Apr 30 00:47:56 2013 +0530

    glupy patch by Ram, Justin: Add/Modify fops, structure types, utility fns
    
    Extend the following fops with Python:
      * open
      * readv
      * writev
      * opendir
      * readdir
      * readdirp
      * stat
      * fstat
      * statfs
      * setxattr
      * getxattr
      * fsetxattr
      * fgetxattr
      * removexattr
      * fremovexattr
      * link
      * unlink
      * readlink
      * symlink
      * mkdir
      * rmdir
    
    Add fd_t, inode_t and iatt_t structure types.
    
    Modify loc_t structure type; Alter the data types of the following
    attributes - inode, parent, gfid, pargfid.
    
    Modify uuid2str function, which returns a string equivalent for a ctype
    object representing a gfid, to make use of python's 'uuid' module for
    accurate representation of uuids.
    
    by Justin Clift:
               Adjust debug-trace.py to work with Python 2.6
    
               Work around 'zero length field name in format' bug in
               negative.py's uuid2str function
    
               Fix indentation errors in negative.py, glupy.h,
               glupy.c, gluster.py
    
    Change-Id: If0fcfb2866e21c0380a973f8ffab9ea7b6a4cd5d
    BUG: 961856
    Signed-off-by: Ram Raja <rraja@redhat.com>
    Reviewed-on: http://review.gluster.org/4907
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Justin Clift <jclift@redhat.com>

commit b9fdbc079025ffd743305cee868e02f653326419
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon May 13 14:59:21 2013 +0530

    glusterd: Perform NULL check on rsp.op_errstr before using it
    
    Change-Id: Id18b215a91cf016964ea98d2f414293b82167d24
    BUG: 962362
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4992
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7ad8b05dc3003102ac192b1bb6bcae5c57e148cf
Author: Anand Avati <avati@redhat.com>
Date:   Thu Apr 25 22:46:50 2013 -0700

    rpcsvc: fix dangerous setting of pointer on free'd structure
    
    The current code is setting @req->hdr_iobuf = NULL _after_ calling
    actor_fn() on @req. Calling actor_fn() takes away all guarantees
    of whether @req is still a valid object or destroyed.
    
    Unfortunately most of the times the object is allocated from mem-pool
    an a mem_put() still keeps the arena allocated (no crash). However
    once the mem-pool is full and allocation falls back to malloc()/free()
    the code actually becomes dangerous. This resulted in random crashes
    when the system load is high (when there were sufficient outstanding
    calls that @rpc pool got full)
    
    Change-Id: I4398c717aa0e2c5f06733212b64dd79e7b2a4136
    BUG: 884452
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4990
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0d415f7f8c08edc7b7af88567bb5ec4803defc94
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Thu May 9 16:14:33 2013 +0000

    glusterd: remove-brick: prevent removal from a replicate volume.
    
    Prevent the removal of brick(s) from a plain replicate volume and
    display the error message at the CLI.
    
    Change-Id: I8e182404564147329d8cd364b7c7931d19f14570
    BUG: 961669
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4975
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fd36cabb0db4139cba97fc75c6169b57ebea3e9d
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Apr 23 12:11:00 2013 +0530

    glusterd: Fix uuid to hostname conversion for 'volume status'
    
    Change-Id: I46c41c29c2d11652f6d8ccd5637be0ac9774fc1d
    BUG: 927648
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4873
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fa227c08341224ac95e45a710f7dbfbb3835a8fe
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 22 12:17:59 2013 +0530

    glusterd: Set op-version on startup based on install status
    
    If the current installation of glusterfs doesn't have a stored
    op-version and is,
    a. a fresh install, then set op-version to maximum
    b. an upgrade from release which didn't have op-version support, set it
    to minimum.
    
    The install status is detected using the peer-uuid.
    If both peer-uuid and op-version are not present in the store, the
    installation is fresh.
    If peer-uuid is present, but op-version is absent in the store, the
    installation has been upgraded from a version which didn't support
    op-versions.
    
    By setting the initial op-version as above, we can ensure that
    a. features are not enabled accidentally during upgrades
    b. a fresh install starts with all possible features enabled.
    
    Change-Id: I52aed9ebeb5d3823c81e65f739a78a924ecf7e12
    BUG: 954256
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4867
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1e62ff42dfcf84ded563f710cb8da92fa0f41936
Author: Ram Raja <rraja@redhat.com>
Date:   Tue Apr 30 00:38:04 2013 +0530

    glupy: Importing Jeff's glupy project into glusterfs
    
    Change-Id: I3891ef6eaf6ede7c8cbedc3298ce2501a69b2b05
    BUG: 961856
    Original-author: Jeff Darcy <jdarcy@redhat.com>
    Signed-off-by: Ram Raja <rraja@redhat.com>
    Reviewed-on: http://review.gluster.org/4906
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Justin Clift <jclift@redhat.com>

commit 40d026e10013f533c4fee33b87dabc4ca11c94b3
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed May 8 21:51:58 2013 -0400

    object-storage: final removal of ufo code
    
    See https://git.gluster.org/gluster-swift.git for the new location of
    the Gluster-Swift code.
    
    With this patch, no OpenStack Swift related RPMs are constructed.
    
    This patch also removes the unused code that references the
    user.ufo-test xattr key in the DHT translator.
    
    Change-Id: I2da32642cbd777737a41c5f9f6d33f059c85a2c1
    BUG: 961902 (https://bugzilla.redhat.com/show_bug.cgi?id=961902)
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4970
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Luis Pabon <lpabon@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fef1270fc2d665c67084c4ce06f60fc8faed4d52
Author: Santosh Kumar Pradhan <spradhan@redhat.com>
Date:   Fri May 10 14:31:27 2013 +0530

    gluster/CLI: crash upon executing "peer status" command
    
    Problem:
    While doing "gluster peer status", cli_cmd_peer_status_cbk() creates
    the frame and passes as arg to gf_cli_list_friends() which sets
    frame->local to GF_CLI_LIST_PEERS flag (value: 0x1). It expects
    gf_cli_list_friends_cbk() [invoked through cli_cmd_submit()] to
    reset frame->local to NULL. But if cli_cmd_submit() fails some
    where before gf_cli_list_friends_cbk() gets invoked, then the
    flag value remains in frame->local and causes a SEGV while
    destroying the stack i.e. [CLI_STACK_DESTROY => cli_local_wipe()].
    
    Fix:
    In gf_cli_list_friends(), if cli_cmd_submit() fails, then
    reset the value of frame->local to NULL.
    
    Change-Id: Ied19f07eaf67e3bd42c75cdc2ff3729b0789e632
    BUG: 961691
    Signed-off-by: Santosh Kumar Pradhan <spradhan@redhat.com>
    Reviewed-on: http://review.gluster.org/4976
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8923c14151d646ab90f05addc9e6c3ed178fee10
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue May 7 15:27:08 2013 +0530

    glusterd: Give up big lock before performing any RPC
    
    Change-Id: Ib0a772dc1cb9afc8adccd8f7092f480d2b525ea0
    BUG: 960580
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4964
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d4557824a64e1eb5aa2ee5dece237a5e9bb8eac8
Author: Michael Brown <michael@netdirect.ca>
Date:   Fri Apr 26 15:32:03 2013 -0400

    nfs3-server: call truncate fop only if necessary
    
    * nfs3svc_setattr_cbk: only truncate if requested size != current size
    
    Change-Id: I3d89e4d2b0710118f90cf5bf9cfdea61d8877491
    BUG: 960725
    Signed-off-by: Michael Brown <michael@netdirect.ca>
    Reviewed-on: http://review.gluster.org/4917
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b5bf14a6ab0d24073d0dd4debf87c7fc15a1e43f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue May 7 11:10:26 2013 +0200

    extras: /etc/init.d/glusterd should create a lockfile under /var/lock/sybsys
    
    Without a lockfile under /var/lock/subsys, the glusterd service is not
    stopped on shutdown or reboot.
    
    Change-Id: I9dc9b4204c5c39879c22191b2e8a2b81a4f3a58a
    BUG: 960476
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4960
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 273a42a421a7deeb3cde9865cfe4bab4826fdb7f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 1 15:05:04 2013 +0530

    cluster/afr: Club missing entry, missing gfid self-heals
    
    Problem:
    gfid-self-heal always assigns the gfid(GFID-1) it gets from lookup.
    Between the time of lookup to triggering the gfid-self-heal the
    entry could have changed. Now lets say there is a case where
    one of the files of the replica subolumes already has a gfid
    (GFID-2) and the other does not. In that case healing should
    happen with GFID-2 instead of GFID-1.
    
    Fix:
    Missing-entry-self-heal already handles all these cases. So removed
    separate handling of gfid-self-heal.
    
    Change-Id: Ie96261e9036c8f3cb4cad89347f9bf7b681cdc1a
    BUG: 767585
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/2670
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d3e3a849ddce1ade85ddb885474b66299e98744d
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon May 6 17:00:57 2013 +0530

    nfs: avoid double fd unref in opendir
    
    Noticed that the fd_unref was called on the fd regardless of the return
    value at nfs3svc_opendir_readdir_cbk(), hence removing an extra unref in
    the negative case in nfs_inode_opendir_cbk, which fixes the spurious
    fd_unref().
    
    Change-Id: I2bf68410dd86cdf9cfe8a3d43adc27497d8bb36f
    BUG: 959190
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4943
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 760d4e1d5836574239a13973003f4e5ec6f033a1
Author: Michael Brown <michael@netdirect.ca>
Date:   Sun May 5 03:04:16 2013 -0400

    rpc-lib: fix printf args when printing XID
    
    * Prior to change, XID is sometimes logged with wrong format string
    * Incorrect (0x%ux): generates output of "XID: 0x1920499352x"
    * Correct (0x%x): generates output of "XID: 0x72787e98"
    
    Change-Id: Id60b673a4356a4815cdb67303612181ac5624fe3
    BUG: 960153
    Signed-off-by: Michael Brown <michael@netdirect.ca>
    Reviewed-on: http://review.gluster.org/4949
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc39ee2ea3a22704ebacd0607cf6fd4eae9ec66a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu May 2 09:11:58 2013 +0530

    Revert "glusterd: Fix spurious wakeups in glusterd syncops"
    
    This reverts commit efa154bb0a4cac34d5a9610ec25d38eebe495f22.
    
    -- Following is Avati's analysis (edited) from gerrit --
    The claim of the patch (being reverted) is that it in some cases cbkfn
    is missed.  This is wrong analysis. cbk_fn is _always_ called. The patch
    treats ret > 0 as a "missed cbk". ret > 0 only means socket submission
    was not complete, and is queued to submit asynchronously when POLLOUT is
    raised.  This is sufficient to guarantee that cbkfn is going to be
    called (either the socket errors or submission succeeds and reply
    eventually arrives).
    
    This commit also removes spurious barrier_wake(s).
    
    call backs are guaranteed to be called even if the transport is
    disconnected. This means, a 'wake' would be called if rpc_clnt_submit is
    called.  Also, we count both successful and failed operations in a
    particular batch of operations for the synctask_barrier_wait.  So,
    calling synctask_barrier_wake on failure of rpc_clnt_submit (say, due to
    network failure) would result in a spurious wake.
    
    Change-Id: I7d508c2a54b74a65b82f097742206bc777afc53a
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4922
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 83cedcd9be2676e63b1be72ecaf3316a781773cb
Author: Anand Avati <avati@redhat.com>
Date:   Mon Apr 22 04:35:03 2013 -0700

    synctask: implement barriers around yield, not the other way
    
    In the current implementation, barriers are in the core of the
    syncprocessors. Wake()s are treated as syncbarrier wake. This
    is however delicate, as spurious wake()s of the synctask can
    mess up the accounting of the barrier and waking it prematurely.
    
    The fix is to keep yield() and wake() as the basic primitives,
    and implement barriers as an object impelemented on top of these
    primitives. This way, only an explicit barrier_wake() gets
    counted towards the barrier accounting, and spurious wakes
    will be truly safe.
    
    Change-Id: I8087f0f446113e5b2d0853431c0354335ccda076
    BUG: 948686
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4921
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 54b9cd3df357ac196af17f53282b3b1975dd4fb9
Author: Anand Avati <avati@redhat.com>
Date:   Sat Apr 27 11:59:36 2013 -0700

    gfapi: add new API glfs_set_xlator_option()
    
    This is the equivalent of specifying --xlator-option command line
    argument to glusterfsd.
    
    Change-Id: I1171dd518a85db4bd456fa0790f450e889a956cd
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4927
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aec246459b4c82fd666a3de20a55700008a5f831
Author: Anand Avati <avati@redhat.com>
Date:   Sat Apr 27 11:18:20 2013 -0700

    posix-acl: fetch ACLs in readdirplus
    
    Not fetching ACLs in readdirplus can potentially result in spurious
    wrong ACL decisions (which magically go away on a lookup() which
    populates the ACLs)
    
    Change-Id: Ided38b4d868fab482b477ce51b4878289ef9eed0
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4926
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b224d7ffb88c274ef0a65d4b5d30b2ce320c6200
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu May 2 16:13:59 2013 +0530

    glusterd: Syncop callbks should take big lock too
    
    Change-Id: I5ae71ab98f9a336dc9bbf0e7b2ec50a6ed42b0f5
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4938
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6556b5cf4077dc45a4c59d2d9ee2f23f5d0a80b0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu May 2 17:48:51 2013 +0530

    glusterd: delete "volume-name" from dict before processing the next option
    
    Change-Id: Ib78963c1f43a66dab50b443742979c7c4e4cbc23
    BUG: 958790
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4940
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 254181428e5c6f7e689bbceaddf434116960faab
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Mar 20 17:33:10 2013 +0530

    glusterd: Log hostname of the peer where there is cksum/version mismatch
    
    Change-Id: I08065aaa3c140d4b02af4ca38f5f4d00d7f0c2bb
    BUG: 958739
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4937
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b6e10801bee030fe7fcd1ec3bfac947ce44d023d
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Apr 30 19:41:34 2013 +0530

    performance/io-cache: check the inode context to be NULL before accessing
    
    Change-Id: I475af7f8ffd5e5d8adbd2a74af20e56ad7751f69
    BUG: 958108
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4916
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 39a1eaf38d64f66dfa74c6843dc9266f40dd4645
Author: Michael Brown <michael@netdirect.ca>
Date:   Tue Apr 30 11:34:57 2013 -0400

    Expand gluster's NFS FD header to 4 bytes
    
    * https://bugzilla.redhat.com/show_bug.cgi?id=950121
    * Oracle's DNFS does not properly XDR encoding on NFS FDs that
      are not congruent to 0mod4 bytes long
    * This patch is a workaround to support Oracle's buggy code
    
    Change-Id: Ic621e2cd679a86aa9a06ed9ca684925e1e0ec43f
    BUG: 950121
    Signed-off-by: Michael Brown <michael@netdirect.ca>
    Reviewed-on: http://review.gluster.org/4918
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d57e37a5235d8ddafa67d4b4e4dca5f3c2126591
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Apr 30 14:33:09 2013 +0200

    Fix uninitialized mutex usage in synctask_destroy
    
    synctask_new() initialize task->mutex is task->synccbk is NULL.
    synctask_done() calls synctask_destroy() if task->synccbk is not NULL.
    synctask_destroy() always destroys the mutex.
    
    Fix that by checking for task->synccbk in synctask_destroy()
    
    BUG: 764655
    Change-Id: I50bb53bc6e2738dc0aa830adc4c1ea37b24ee2a0
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4913
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7967e3e5cfd330190c2bcc45d3a111a1d563a7a0
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Apr 30 00:20:33 2013 +0530

    cluster/afr: Avoid self-healing extended attribute used by SELinux.
    
    Since removexattr() fails to remove "security.selinux" in a system
    where SELinux is enforcing, xattr self-healing fails.
    As a consequence of this, user extended attributes are not being healed.
    Added a check in afr to prune SELinux xattr from the dictionary
    used for removing xattrs from the sink.
    
    Minor changes in tests and md-cache as well.
    
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Change-Id: I854bfc0098dde812ce2afe64b125ee40c04bdeb1
    BUG: 957877
    Reviewed-on: http://review.gluster.org/4905
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3b1ecc6a7fd961c709e82862fd4760b223365863
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Apr 22 12:27:07 2013 +0530

    glusterd: Removed 'proactive' failing of volume op
    
    Volume operations were failed 'proactively', on the first disconnect of
    a peer that was participating in the transaction.
    
    The reason behind having this kludgey code in the first place was to
    'abort' an ongoing volume operation as soon as we perceive the first
    disconnect. But the rpc call backs themselves are capable of injecting
    appropriate state machine events, which would set things in motion for an
    eventual abort of the transaction.
    
    Change-Id: Iad7cb2bd076f22d89a793dfcd08c2d208b39c4be
    BUG: 847214
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4869
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f75be775a9b191eb74f6cb4c161d9af36f2fdc97
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Apr 25 00:28:07 2013 +0530

    tests: Modified test to use remove-brick instead of 'start' variant
    
    remove-brick start doesn't remove the brick from the volume immediately.
    It would wait until migration of data to other bricks are complete. Even
    when there is no data to be migrated, one can expect a finite delay from
    the time of remove-brick start command's exit and removal of brick(s).
    This may cause subsequent checks on brick count to fail in a
    non-deterministic manner.
    
    Also, renamed the test file name to reflect bug-id corresponding to
    community release.
    
    Change-Id: Ic43f011e251640decb68e46f4a10e0824ade0ac9
    BUG: 878004
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4885
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ee9984882e3b28e76fb3af5491a8d2bf22e432a3
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Apr 21 11:10:06 2013 +0200

    extras: include Fedora changes in init.d/glusterd
    
    The changes in the .spec file from Fedora have largely been merged into
    the glusterfs.spec.in. It seems that some dependencies have been missed,
    most importantly some additions to the init-script that are called while
    (un)installing or updating RPMs.
    
    These changes come from the downstream Fedora package that carries its
    own glusterd.init script. In future, Fedora/EPEL should be able to drop
    that file and use the Gluster project version.
    
    Change-Id: Iac25854b0c559b93fa1dd452a04663bd95ea3378
    BUG: 954149
    URL: http://lists.nongnu.org/archive/html/gluster-devel/2013-04/msg00077.html
    CC: Fedora GlusterFS Packagers <glusterfs-owner@fedoraproject.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4864
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ddad856d371b1cbc80e1a195e9d81edb1be31371
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Apr 29 17:05:03 2013 +0200

    Fix spurious brick disconnects
    
    Spurious disconnect were caused by a race condition inside
    rpc_transport_ref()/rpc_transport_unref() that allowed the refcount
    to drop to zero while the transport was still in use. The race
    condition is made possible because of an uninitiaized mutex
    produced when socket_server_event_handler() copies the transport
    
    BUG: 764655
    Change-Id: I34fe097a0ac21b0dbf58f5eed84880e3fd9814f2
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4900
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc8aa43d4689b3945681a2ab27427daebac297c7
Author: Ravishankar N <ravishankar@redhat.com>
Date:   Sun Apr 28 11:35:52 2013 +0530

    cli: Avoid storing empty lines in command history
    
    When the console manager is run in the interactive mode, it also saves
    empty lines (i.e. the Enter key is pressed without running a command) in
    it's command history. Avoid this by processing the line only if
    readline() returns a non-empty string. Makes it easier to navigate the
    history using arrow keys.
    
    	modified:   cli/src/cli-rl.c
    
    Change-Id: I0fcce394474589bb345b7c9ef39d25849dc0c2af
    BUG: 957139
    Signed-off-by: Ravishankar N <ravishankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4894
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e6b6d1235daa483384d2b0701561b8f3a85be583
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Apr 20 16:55:15 2013 +0200

    cli: add a command 'gluster pool list [--xml]'
    
    * unlike 'gluster peer status', which lists only info about peers,
      this command lists localhost also in the list, so the sorted
      output from all the nodes should match.
    
    * made the output script friendly by keeping it one output per line.
    
    Change-Id: I853656753b35c617debbcceecbb71c8d6dd3c334
    BUG: 764638
    Original-review: http://review.gluster.org/4221
    Original-author: Amar Tumballi <amarts@redhat.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4862
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5e0116109e3c444b11adb9809c75b4da72e85457
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Apr 23 12:57:40 2013 -0400

    build: sync glusterfs.spec.in with Fedora glusterfs.spec
    
    BUG: 950083
    Change-Id: I96aeb8fbe8b79bbc058ff9a45167d822abb576ed
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4876
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>

commit 915385553e46d65e0b91ce62066a5575b07ee44d
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 1 17:55:30 2013 +0530

    glusterd: Introduce volume op-versions
    
    Each volume is now associated with two op-versions,
     * op_version - the op-version of the highest op-versioned feature enabled
     * client_op_version - the op-version of the highest op-versioned feature
       enabled which affects the clients only.
    
    These two op-versions are generated dynamically and kept updated during
    runtime. Glusterd now uses the respective volumes' client-op-version during
    getspec requests.
    
    To achieve the above a new field in the vme table is introduced,
    client_option, this boolean field tells if the option is a client side
    option.
    
    Change-Id: I12c83b1dd29ab506026efd50d448cebbcee53c27
    BUG: 907311
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4584
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6419bd804b9cf43ad08fc54ef605c77b0e7895af
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 24 18:05:13 2013 +0530

    performance/io-cache: Avoid double mem_put in ioc_readv
    
    On readv error io-cache frame->local is not set to NULL
    so the local is mem_put in STACK_DESTROY as well. This
    patch sets frame->local to NULL in all cases.
    
    Change-Id: I00013df1377475aa5f3c0c681dcb58b32e1e8063
    BUG: 955751
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4884
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 054c1d7eb3782c35fc0f0ea3a5fd25337d080294
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Apr 16 17:22:41 2013 +0530

    nfs: change default nfs port to 2049
    
    This change makes it possible to mount glusterfs volumes
    without specifying vers=3 option.
    
    Change-Id: If5a974e2bdfd2adbeac3d82af774310cdf30f988
    BUG: 832939
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4840
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 1bcb1c4d5225e197464d1c64bafd4e7ef4042e78
Author: Anand Avati <avati@redhat.com>
Date:   Mon Apr 15 09:52:35 2013 -0700

    gfapi: POSIX locking support
    
    Change-Id: I37d9e1fb4a715094876be6af3856c1b4cf398021
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4881
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d37b2198dc8f763205f5b7e56a0e40252ccf97fe
Author: Anand Avati <avati@redhat.com>
Date:   Tue Apr 23 14:20:13 2013 -0700

    gfapi: implement readdirplus_r support
    
    This call is used by Samba VFS.
    
    Change-Id: Ib371502ad5a71b3b0e993f6b30e3dfb1f839c020
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4879
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 714c9776c5374496ebcecb0b139718ff5fef494b
Author: Anand Avati <avati@redhat.com>
Date:   Tue Apr 23 13:59:12 2013 -0700

    syncop: set credentials of running process in @frame
    
    Inherit the pid/euid/egid/groups of the running process in the
    frame. Do this only in cases where a loaded frame was not
    presented to the synctask.
    
    This behavior is required for Samba VFS.
    
    Change-Id: Ib181c90f47c6741197b9ce9f67a19e2914b647d2
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4878
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fdde66da060fefcbdec664b6420658936f18b345
Author: Anand Avati <avati@redhat.com>
Date:   Mon Apr 22 21:34:05 2013 -0700

    gfapi: handle root (/) resolution gracefully for realpath()
    
    Resolving path of / is crucial for realpath() to work properly.
    
    Change-Id: I8a1b482beba37f01afbd20446d9e6f6125f2ec34
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4872
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 86acc0f6176954fd687354d093e894636e5d6a73
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Apr 8 13:06:39 2013 +0530

    cluster/afr: Added documentation for eager-lock check
    
    Change-Id: Ifa42762adde8b55ef1e2b51a59c93cebd983343f
    BUG: 912581
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4792
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3f22b5bb7069cfff8607320c262702418c731c89
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Apr 12 16:35:51 2013 +0530

    glusterd: volume-sync needs to work with rejected peers
    
    Change-Id: I970a51d3f62bcf414eb9552a68d1068430b93216
    BUG: 950048
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4815
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a1db18cf7a6cde96f2e5b920ffbbf88e72a21fd4
Author: Anand Avati <avati@redhat.com>
Date:   Sun Apr 14 02:58:34 2013 -0700

    gfapi: support for chdir() and family
    
    Add support for chdir, fchdir, getcwd, realpath equivalents in
    GFAPI. These are required for the Samba VFS plugin.
    
    Change-Id: I91d2db9146994403c98961c489c7640c51d5add2
    BUG: 953694
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4853
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1fc9b98a4eb6eda8db30940a8bb07d206e2fa049
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Apr 19 13:02:39 2013 +0530

    tests: Fix volume-status test script
    
    * The functions now return the aggregated return value instead of just echoing it.
    * Fixed the shd test loop to use the proper variable
    * Added 'wait's for nfs and shd services to come online.
    
    BUG: 764966
    Change-Id: Iedbb5be0d5e50108ed4847d58625ccb093c22251
    Original-author: Kaushal M <kaushal@redhat.com>
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4856
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9d74f78141b681faf9d60456d00c73d2905f2735
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Apr 9 13:08:22 2013 +0530

    glusterd: validate performance.nfs.* option values during volume set stage
    
    PROBLEM:
    
    performance.nfs.* option values (which are of type boolean) are
    not validated during the stage phase of 'volume set'.
    The result - nfs graph generation fails during commit phase,
    AFTER the option and its (invalid) value have been placed in
    volinfo->dict.
    
    CAUSE:
    
    nfsperfxl_option_handler() - the function that validates the values of
    performance.nfs.* options - never receives the (key,value) pair that
    needs to be set, for validation during 'volume set' stage.
    
    FIX:
    
    In build_nfs_graph(), copy the (mod_)dict containing the (option,value)
    parameters into set_dict before attempting to build the client graph
    for the volume on which the operation is being performed.
    
    Of course, an easier way out would be to simply do a 'volume reset' and
    pretend nothing wrong happened!
    
    Change-Id: I56b17d0239d58a9e0b7798933a3c8451e2675b69
    BUG: 949930
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4814
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dcebed550ebfc878b0b3bd02ab7fe15db6764f81
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Apr 15 22:07:21 2013 +0530

    glusterd: Avoided deadlock in single node cluster, glusterd restart
    
    In a single node cluster, it is possible to deadlock on the "big
    lock", while restarting bricks. In glusterd_restart_bricks, we perform a
    glusterd_brick_connect, where we release the big lock in anticipation
    that glusterd_brick_rpc_notify could run in the same C stack (and
    deadlocking). So, in the restart code path, we could unlock before we
    have performed a lock on the big lock.
    
    To fix this, we need to take the big lock in the
    glusterd_launch_synctask 'thread' as well.
    
    Change-Id: I1abea1ca82b55c784b8a810a8194f254b32b1dcc
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4837
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9eb8fc771b32c0601969537ad7135edd89e49cf9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Apr 15 11:02:19 2013 +0200

    rpm: remove useless provides for xlator .so files and private libraries
    
    xlator .so files and private libraries should be skipped while scanning
    for provides:
    - https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering
    
    This prevents automatic generated provides like these in the glusterfs,
    glustrefs-fuse and glusterfs-server packages:
    - addr.so.0()(64bit)
    - afr.so.0()(64bit)
    - client.so.0()(64bit)
    - dht.so.0()(64bit)
    - ...
    
    BUG: 952122
    Change-Id: Icd08925eb1826f3593129e7c19de83528f7b6301
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4823
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6d6205ede5e90a919d082b4413055d684114253a
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Fri Apr 12 06:41:29 2013 +0530

    object-storage: provide more common cfg defaults
    
    Provide more common configuration defaults, as seen and recommended across
    many large customer installations, as well as provide some guidance on how to
    set the parameters.
    
    See BZ 904629 (https://bugzilla.redhat.com/show_bug.cgi?id=904629).
    
    Change-Id: Id9f20aafd75f2a0b589c67654dce87534bf80c33
    BUG: 904629
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4789
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bf7b83d2bcc490a9a70ddd0fcf71e8a81c5430a2
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Sun Apr 7 07:18:06 2013 +0530

    object-storage: cleanup err handling in Glusterfs.
    
    Change-Id: I4fa1a7b9214c6897459a99bedde80e84eb2b9cbc
    BUG: 904370
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4788
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bbaa273468f8e5377027aedcabcaa076dd7fec7e
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Sun Apr 7 06:05:56 2013 +0530

    object-storage: turn off stat() for container list
    
    Turn of stat() system calls used to fetch the file size during a
    container listing operation since these system calls can swamp Gluster
    and the result is most often not used.
    
    When a GET or HEAD request is made on a container, stat() system calls
    are made during the Python standard library method, os.walk, to
    determine if a given directory entry is another directory to recurse
    into, and then utils._update_list() will stat() each file to get it
    size, and finally utils.get_container_details_from_fs() will stat()
    each directory encountered.
    
    For most installations we have seen so far, we don't need the
    container listing to accurately return the size of all the objects in
    the container, so we can reduce the number of stat() system calls by
    not fetching the size of the object.
    
    For now, turn it off by default, and provide an /etc/swift/fs.conf
    configuration parameter to turn it back on:
    
      accurate_size_in_listing = yes
    
    The default for the above is "no".
    
    Change-Id: I7dde11e14bb32ecafa3eabb08852f1ffc4366b35
    BUG: 903396
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4787
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f34343d3751cd73e8eabe6d5544fb1f58b316595
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Apr 2 07:56:25 2013 +0530

    glusterd: big lock - a coarse-grained locking to prevent races
    
    There are primarily three lists that are part of glusterd process,
    that are concurrently accessed. Namely, priv->volumes, priv->peers
    and volinfo->bricks_list.
    
    Big-lock approach
    -----------------
    WHAT IS IT?
    Big lock is a coarse-grained lock which protects all three
    lists, mentioned above, from racy access.
    
    HOW DOES IT WORK?
    At any given point in time, glusterd's thread(s) are in execution
    _iff_ there is a preceding, inbound network event. Of course, the
    sigwaiter thread and timer thread are exceptions.
    A network event is an external trigger to glusterd, via the epoll
    thread, in the form of POLLIN and POLLERR.
    As long as we take the big-lock at all such entry points and yield
    it when we are done, we are guaranteed that all the network events,
    accessing the global lists, are serialised.
    
    This amounts to holding the big lock at
    - all the handlers of all the actors in glusterd. (POLLIN)
    - all the cbks in glusterd. (POLLIN)
    - rpc_notify (DISCONNECT event), if we access/modify
      one of the three lists. (POLLERR)
    
    In the case of synctask'ized volume operations, we must remember that,
    if we held the big lock for the entire duration of the handler,
    we may block other non-synctask rpc actors from executing.
    For eg, volume-start would block in PMAP SIGNIN, if done incorrectly.
    To prevent this, we need to yield the big lock, when we yield the
    synctask, and reacquire on waking up of the synctask.
    
    Change-Id: Ib929f9905b55fb6c3fc27fefb497a26dba058e4f
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4784
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 732cd267c924554a638519cff0df146b2688d6e8
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Apr 12 09:08:49 2013 -0400

    license: xlators/protocol/server dual license GPLv2 and LGPLv3+
    
    BUG: 951549
    Change-Id: I3de5bd86d4238a60a0a85ba2e15d9c131969b210
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4816
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 77a02c4dd8467e2a78b3ab3cdef95178ef4b1898
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 11 09:36:35 2013 -0400

    object-storage: rebase Swift to 1.8.0 (grizzly)
    
    Two minor tweaks found while packaging 3.4.0-0.1.alpha2 for Fedora 19
    
    BUG: 948039
    Change-Id: I97175636164702cf4042bc4a18ffead76ad386cb
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4807
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit efa154bb0a4cac34d5a9610ec25d38eebe495f22
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Apr 10 17:12:01 2013 +0530

    glusterd: Fixed spurious wakeups in glusterd syncops
    
    glusterd syncops perform a barrier_wake whenever rpc_clnt_submit returned -1.
    This is based on the wrong assumption that the cbkfn wasn't called.
    This would result in one more wakeup than there ought to be.
    
    Change-Id: I591e67c267f0e26d1145bf8fb5feeb2c13a751a1
    BUG: 948686
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4802
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2fbae10cc026c3a0dab82fdb47497f42f5683934
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Apr 10 15:08:51 2013 -0400

    build: add BuildRequires librdmacm-devel
    
    See http://review.gluster.org/149
    
    Installed librdmacm-devel RPM on the build server.
    
    Change-Id: Iafb30e9cf1b15272b80329cc6141c7e92b43daee
    BUG: 950083
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4804
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 432ce7e60fb58d3cbb019ab3159b7d393afaaed6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Apr 10 17:51:37 2013 +0200

    build: really disable fusermount if you say so
    
    There is no logic in configure.ac that provides a $disable_fusermount
    variable. So, use the $enable_fusermount variable instead.
    
    Follow-up-for: http://review.gluster.org/4773
    Change-Id: I81cdbd0045409d0036438d542ca6dc1934f784e4
    BUG: 948205
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4803
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Sachidananda Urs <sacchi@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a216f5f44675bfe189c318171dbc50e1c19bfc26
Author: Anand Avati <avati@redhat.com>
Date:   Tue Apr 9 17:22:01 2013 -0700

    tests: fix further issues with bug-874498.t
    
    The failure of bug-874498.t seems to be a "bug" in glustershd.
    The situation seems to be when both subvolumes of a replica are
    "local" to glustershd, and in such cases glustershd is sensitive
    to the order in which the subvols come up.
    
    The core of the issue itself is that, without the patch (#4784),
    self-heal daemon completes the processing of index and no entries
    are left inside the xattrop index after a few seconds of volume
    start force. However with the patch, the stale "backing file"
    (against which index performs link()) is left. The likely reason
    is that an "INDEX" based crawl is not happening against the subvol
    when this patch is applied.
    
    Before #4784 patch, the order in which subvols came up was :
    
      [2013-04-09 22:55:35.117679] I [client-handshake.c:1456:client_setvolume_cbk] 0-patchy-client-0: Connected to 10.3.129.13:49156, attached to remote volume '/d/backends/brick1'.
      ...
      [2013-04-09 22:55:35.118399] I [client-handshake.c:1456:client_setvolume_cbk] 0-patchy-client-1: Connected to 10.3.129.13:49157, attached to remote volume '/d/backends/brick2'.
    
    However, with the patch, the order is reversed:
    
      [2013-04-09 22:53:34.945370] I [client-handshake.c:1456:client_setvolume_cbk] 0-patchy-client-1: Connected to 10.3.129.13:49153, attached to remote volume '/d/backends/brick2'.
      ...
      [2013-04-09 22:53:34.950966] I [client-handshake.c:1456:client_setvolume_cbk] 0-patchy-client-0: Connected to 10.3.129.13:49152, attached to remote volume '/d/backends/brick1'.
    
    The index in brick2 has the list of files/gfid to heal. It appears
    to be the case that when brick1 is the first subvol to be detected
    as coming up, somehow an INDEX based crawl is clearing all the
    index entries in brick2, but if brick2 comes up as the first subvol,
    then the backing file is left stale.
    
    Also, doing a "gluster volume heal full" seems to leave out stale
    backing files too. As the crawl is performed on the namespace and
    the backing file is never encountered there to get cleared out.
    
    So the interim (possibly permanent) fix is to have the script issue
    a regular self-heal command (and not a "full" one).
    
    The failure of the script itself is non-critical. The data files are
    all healed, and it is just the backing file which is left behind. The
    stale backing file too gets cleared in the next index based healing,
    either triggered manually or after 10mins.
    
    Change-Id: I5deb79652ef449b7e88684311e804a8a2aa4725d
    BUG: 874498
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4798
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c9800f0986a10bbde9121239590e3cb25b94c5f8
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 12 17:26:35 2013 +0530

    glusterd: changes in 'volume create' behaviour
    
    This patch incorporates all the changes suggested on the behaviour of
    'volume create' command in http://review.gluster.org/#change,4214
    (comment #14, to be precise).
    
    Change-Id: Iaac524a59738b177415595b18aa8a136090d3d25
    BUG: 948729
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4740
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f364d542aaf272c14b1d6ef7c9ac805db0fdb45c
Author: Anand Avati <avati@redhat.com>
Date:   Fri Apr 5 16:26:53 2013 -0700

    tests: fix dependency on sleep in bug-874498.t
    
    With the introduction of http://review.gluster.org/4784, there are
    delays which breaks bug-874498.t which wrongly depends on healing
    to finish within 2 seconds.
    
    Fix this by using 'EXPECT_WITHIN 60' instead of sleep 2.
    
    Change-Id: I2716d156c977614c719665a5e1f159dabf2878b5
    BUG: 874498
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4796
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cf48bea3b298ea9aa35d82848a77b6bf681265d6
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Mar 18 12:32:35 2013 +0530

    mgmt/glusterd: enable valgrind usage even in non DEBUG build
    
    * Till now running glusterfs processes were allowed to run in valgrind
      mode only when built with debug mode enabled.
    
    Change-Id: I11e07ea2a4da4f82f70cdded6258a22d65d6db64
    BUG: 922877
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4688
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 9c1d7cebbc62723f719b2fd0c45e0a7452e0d6be
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Apr 4 11:23:08 2013 +0530

    cluster/distribute: Ignore non-participating subvols for layout checks
    
    When subvols-per-directory is < available subvols, then there are layouts
    which are not populated. This leads to incorrect identification of holes or
    overlaps. We need to ignore layouts, which have err == 0, and start == stop.
    In the current scenario (start == stop == 0).
    
    Additionally, in layout-merge, treat missing xattrs as err = 0. In case of
    missing layouts, anomalies will reset them.
    
    For any other valid subvoles, err != 0 in case of layouts being zeroed out.
    
    Also reverted back dht_selfheal_dir_xattr, which does layout calculation only
    on subvols which have errors.
    
    Change-Id: I9f57062722c9e8a26285e10675c31a78921115a1
    BUG: 921408
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4668
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ce111f472796d027796b0cc3a4a6f78689f1172d
Author: Anand Avati <avati@redhat.com>
Date:   Fri Apr 5 02:18:06 2013 -0700

    syncenv: be robust against spurious wake()s
    
    In the current implementation, when the callers of synctasks perform
    a spurious wake() of a sleeping synctask (i.e, an extra wake() soon
    after a wake() which already woke up a yielded synctask), there is
    now a possibility of two sync threacs picking up the same synctask.
    This can result in a crash. The fix is to change ->slept = 0|1 and
    membership of synctask in runqueue atomically.
    
    Today we dequeue a task from the runqueue in syncenv_task(), but
    reset ->slept = 0 much later in synctask_switchto() in an unlocked
    manner -- which is safe, when there are no spurious wake()s.
    
    However, this opens a race window where, if a second wake() happens
    after the dequeue, but before setting ->slept = 0, it results in
    queueing the same synctask in the runqueue once again, and get
    picked up by a different synctask.
    
    This is has been diagnosed to be the crashes in the regression tests
    of http://review.gluster.org/4784. However that patch still has a
    spurious wake() [the trigger for this bug] which is yet to be fixed.
    
    Change-Id: I9b4b9dd5115d6e62ba45162ae90dd5e917a4f83d
    BUG: 948686
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4795
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1ca50941d693f48e73723b12a1466a70dd272ea2
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Apr 8 15:32:49 2013 -0400

    tests: fix spurious regression test failures
    
    Change-Id: I752aeb8e25f43281d2f5cf33d0ff5aeae49687e7
    BUG: 764966
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4794
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 108475decfde8fd30818c37604ef8db837220624
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Apr 7 21:39:18 2013 +0530

    cli: Address a double free with volume info.
    
    Crash is observed when volume info is performed on a
    non-exisiting volume name and the output format is xml.
    
    Change-Id: I88aa5d9dc954b1352f5cc3b5b38742c832bc1bb8
    BUG: 949298
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4785
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e0fac0b68ff23a87da3eda4ced7a60b3e2fcf77a
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Apr 8 00:46:27 2013 +0530

    glusterfsd: Cleanup temporary files from /tmp
    
    For each gluster{d,fs,fsd} start, one or more temporary
    file(s) created in /tmp were not being unlinked. This
    patch cleans that up.
    
    Modified a typo in an unrelated log message as well.
    
    Change-Id: I3dec2a2ca40c7d6828eb238ec9cd08b6072cf0dd
    BUG: 949327
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4786
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6f6744730e34fa8a161b5f7f2a8ad3f8a7fc30fa
Author: Anand Avati <avati@redhat.com>
Date:   Thu Apr 4 19:35:11 2013 -0700

    afr: let eager-locking do its own overlap checks
    
    Today there is a non-obvious dependence of eager-locking on
    write-behind. The reason is that eager-locking works as long
    as the inheriting transaction has no overlaps with any of the
    transactions already in progress. While write-behind provides
    non-overlapping writes as a side-effect most of times (and only
    guarantees it when strict-write-ordering option is enabled,
    which is not on by default) eager-lock needs the behavior
    as a guarantee. This is leading to complex and unwanted checks
    for the presence of write-behind in the graph, for the simple
    task of checking for overlaps.
    
    This patch removes the interdependence between eager-locking
    and write-behind by making eager-locking do its own overlap checks
    with in-progress writes.
    
    Change-Id: Iccba1185aeb5f1e7f060089c895a62840787133f
    BUG: 912581
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4782
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 862b1164525b8a6d4f8d49b3049093847533f819
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 4 07:49:28 2013 -0400

    object-storage: rebase Swift to 1.8.0 (grizzly)
    
    Change-Id: I24265c12a45eac4cec761748096118c9647440be
    BUG: 948039
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4779
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 24ee79345fc7346ef78b8adf54008ae77524026b
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Feb 21 22:10:27 2013 +0530

    storage/posix: introduce node-uuid-pathinfo
    
    enabling this option has an effect on pathinfo xattr
    request returning <node-uuid>:<path> instead of the
    default - which is <hostname>:<path>.
    
    Change-Id: Ice1b38abf8e5df1568bab6d79ec0d53dfa520332
    BUG: 765380
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4567
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6a7d28c0f8c107baf376eceb9fc05d9e80bf74e5
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Apr 4 13:08:32 2013 -0400

    object-storage: use tox for unit tests; fix em too
    
    Add the ability to use tox for unit tests, since it helps us solve the
    problem of supporting multiple branches that require different
    versions of dependencies, and allows us to possibly support multiple
    versions of python in the future.
    
    Also fix the code to work with pre-grizzly environments, by not
    requiring the constraints backport.
    
    Also fixed the xattr support to work with both pyxattr and xattr
    modules.
    
    And fixed the ring tests to also work without a live /etc/swift
    directory.
    
    BUG: 948657 (https://bugzilla.redhat.com/show_bug.cgi?id=948657)
    Change-Id: I2be79c8ef8916bb6552ef957094f9186a963a068
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4781
    Reviewed-by: Alex Wheeler <wheelear@gmail.com>
    Tested-by: Alex Wheeler <wheelear@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a56dca94c3b174637074be46e9a537ba0ca02c4b
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Apr 3 05:40:17 2013 +0530

    object-storage: Import missing sys and errno modules.
    
    Import the missing modules and implemented unit test case for Glusterfs module.
    Thanks to Paul Smith for pointing it out.
    
    Change-Id: Ib04202aa0ae05c4da2ebbf11f87d6accc778f827
    BUG: 905946
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4758
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6956c710d9bffcc0d99526a9d6c051c4cebc0bdb
Author: sarvotham s pai <spai@redhat.com>
Date:   Mon Apr 1 00:44:34 2013 +0530

    gsync: Display additional information in status command
    
    Added code to display extra information when status command
    is executed.
     Information shown now are
    1 Number of files synced
    2 crawl time
    3 total sync time
    4 bytes synced
    
    bytes synced is taken from rsync output .
    --stats option of rsync gives extra infor
    mation about the sync.In stats output there
    is a field called Total transferred file
    size which states the ammount of bytes synced .
    This information is parsed from stdout output
    using regular expressions.Bytes synced information
    can be used to calculate throughput.
    
    Change-Id: Id9bba9fff45ee7049bb8257c6fd918e5237e05b1
    BUG: 947774
    Signed-off-by: sarvotham s pai <spai@redhat.com>
    Reviewed-on: http://review.gluster.org/4749
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fff8008c6cfa3b224859bc4ac7cf8a3d35c22204
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Apr 3 14:15:16 2013 +0530

    tests: Remove grep process entries from pidgrep
    
    Problem:
    We were picking process with lowest pid from ps|grep
    result. However, lowest pid need not be oldest process
    as recycling of PIDs can take place.
    
    Solution:
    Removed grep process entries from ps entries using
    grep -v grep.
    
    Change-Id: I2b9687a05a34cf6358f773183770d69a3fb9eb10
    BUG: 858488
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4765
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dcf3ecd3c08b37226481b81fb0f8b3987cbcbab4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Feb 28 14:50:16 2013 +0530

    cluster/afr: Treat all dir fop failure as success in changelog
    
    For example:
    If a new entry creation fop fails with EEXIST or a delete entry fop
    fails with ENOENT, on all the subvols the fop is wound, then no
    change took place to the directory. So we can treat that case as no
    change happened to the directory.
    
    Change-Id: I3b3a7931954da2166a9cba19ff9f76f37739d751
    BUG: 860210
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4626
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5cdd09c3087e7f0581392dd06d4a1d587176abcb
Author: Anand Avati <avati@redhat.com>
Date:   Wed Apr 3 16:31:07 2013 -0700

    posix: fix dangerous "sharing" of fd in readdir between two requests
    
    posix_fill_readdir() is a multi-step function which performs many
    readdir() calls, and expects the directory cursor to have not
    "seeked away" elsewhere between two successive iterations. Usually
    this is not a problem as each opendir() from an application has its
    own backend fd, and there is nobody else to "seek away" the directory
    cursor. However in case of NFS's use of anonymous fd, the same fd_t
    is shared between all NFS readdir requests, and two readdir loops can
    be executing in parallel on the same dir dragging away the cursor in
    a chaotic manner.
    
    The fix in this patch is to lock on the fd around the loop. Another
    approach could be to reimplement posix_fill_readdir() with a single
    getdents() call, but that's for another day.
    
    Change-Id: Ia42e9c7fbcde43af4c0d08c20cc0f7419b98bd3f
    BUG: 948086
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4774
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4e00f0017d7a3f77cb8c753b665352e25a33e1fa
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Apr 2 15:15:52 2013 +0530

    cluster/afr: Made afr_sh_purge_entry_common message log more clear.
    
    FIX:
    In missing entry self heal, once the source directories are determined
    after the lookup and if file is not present on any of the brick which
    contains the souce directory, the entry is removed from the directory.
    So log message should give information of "Purging of entry".
    
    Change-Id: I4d3deb602e0812dc1c9c8ba0a466716d81dede7e
    BUG: 947312
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4753
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a5a87f0d07dbcebbc5e1c9c6e0df5a8c77b6fa2d
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Wed Apr 3 16:59:27 2013 +0530

    dict: Put "goto out" in dict_unserialize to avoid process crash
    
    Problem:
    In the dictionary serialization function, if the
    [(buf + vallen) > (orig_buf + size)], then memdup is getting failed.
    
    Fix:
    Put "goto out" whenever this condition is met.
    
    Change-Id: I662628a936596dbb47825aad47d7dbab2879eb07
    BUG: 947824
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4767
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 63119434365ddcea2d0b80aad0757e2201001af3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Apr 3 15:27:01 2013 +0530

    pump: Set self-heal readdir size in pump
    
    Problem:
    In Pump entry self-heal happens for each directory during the
    first opendir using conservative merge. But in entry-self-heal
    readdir is issued with '0' size. So entry self-heal is not
    creating any files. After pump thinks entry self-heal is complete
    it proceeds to heal each of the file in the directory it just
    healed. Fortunately most of the times it chooses source-brick
    in pump as read-child for readdir. This happens because readchild is the
    subvolume on which lookup succeeds first. In pump lookup succeeds
    faster in local process than on the destination brick process most
    of the times. For all the entries pump finds in readdir it does a
    lookup. During this lookup the entry on the destination brick is
    created and healed. This is the reason why replace-brick
    succeeds whenever read-child for the directory is chosen as the
    source-brick.  Which is most of the times. When read-child is chosen
    as the destination brick, readdir returns no entries so replace-brick
    completes without syncing the whole data.
    
    Fix:
    Set readdir-size in pump so that entry self-heal happens with
    64k size. This ensures that entry self-heal triggered from
    opendir actually creates the files on the destination brick.
    
    Change-Id: I65ea45d3c2735a9578f3aa34eff771b6563241ca
    BUG: 909800
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4712
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 125e0cc4eb7042f5b8549c0b77140528c0fc1151
Author: Anand Avati <avati@redhat.com>
Date:   Wed Apr 3 13:38:00 2013 -0700

    build: enable fusermount by default
    
    The fusermount available in gluster is customized to ensure
    mounting with SELinux happens properly, i.e - to have a separate
    thread for fuse_thread_proc which can process getxattr requests
    and in parallel perform sys_mount() in a different thread, thereby
    avoiding a deadlock.
    
    However our build and packaging defaults to not including our
    fusermount. This patch reverses the defaults.
    
    Change-Id: I793af4c2f56aeac46efae3db30e7c64ee7c18850
    BUG: 811217
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4773
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e80a04f7850144449a0d2fc4f9d40d0227f170cc
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 14 15:54:07 2013 +0530

    protocol/client: Print valid loc identifiers
    
    Change-Id: I45f91105862a2484b8906a7a63b98ab4aaf80d05
    BUG: 924643
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4683
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0106fce7fed3dc8f38de3bf365182bdd782b5d9c
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 21 19:11:25 2013 -0400

    dht: make nufa/switch call dht's init/fini
    
    These functions keep changing as new functionality is added, so copying
    and pasting the code is not a good solution.  This way ensures that all
    fields get initialized properly no matter how much new stuff we throw in.
    
    Change-Id: I9e9b043d2d305d31e80cf5689465555b70312756
    BUG: 924488
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4710
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 42a9d608d5acbe8526050d23682071171d65da3b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 21 19:02:52 2013 -0400

    core: add dispatch table for init/fini
    
    This adds a layer of indirection so that derivative translators such as
    NUFA and switch can refer to the parent's init/fini (in both cases DHT's)
    without having to create stub functions.
    
    Change-Id: I1af1fea70a9ddd2aa20485af7ae65f9660f19dd6
    BUG: 924490
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4709
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6fc4820ae8d8f06c05616a4ac3cc8f296ce42ecf
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon Mar 4 07:17:31 2013 +0530

    cluster/distribute: Start rebalance with option readdir-optimize on
    
    With readdir-optimize set to on, we instruct the posix layer to ignore
    directory entries from not first subvolume. DHT discards directories
    returned from non first subvolume. By making posix itself ignore it,
    we are making directory crawls faster
    
    Change-Id: Ia1faf2dedec0c615c0632c3c063e846f5742ede6
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4613
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5625c999ed2cbafa843bf88938da2806253d0838
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Apr 3 13:17:29 2013 +0200

    build: require /usr/bin/fusermount when not carrying our own version
    
    The fuse.so from glusterfs-fuse will try to call /usr/bin/fusermount.
    This obviously fails when the fuse package is not installed and
    fusermount is not available.
    
    In order to prevent this problem, the glusterfs-fuse package should
    require /usr/bin/fusermount so that it gets automatically pulled in when
    glusterfs-fuse is installed with yum.
    
    BUG: 947830
    Change-Id: I20fe836a1aaf751dbc04d9ec4ba5ea50573c71c5
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4768
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b2aa9c6723e3cda46ef3ddc45f21a8a78cef1b77
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Wed Mar 27 12:35:49 2013 +0530

    rpc-lib: Move defaulting to socket message to debug level
    
    Problem:
    For every gluster cli operation from command line
    rpc init process is required. During init process we
    print "no transport type set, defaulting to socket"
    message at WARNING level, which is not necessary.
    
    Solution:
    Moved the log level to DEBUG.
    
    Change-Id: I73f4644264368b0f6c11a77ef66595018784ce79
    BUG: 928204
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4727
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 144e24c8f9f229ce4c81d4beaaa930fccb2c6f3a
Author: Bala.FA <barumuga@redhat.com>
Date:   Fri Mar 29 11:50:13 2013 +0530

    cli: add more meaningful error messages
    
    Change-Id: I6e88e6763fa537f4705427b4673d86e6443c2c98
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/4747
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1fd8e7309062b30bd864730d2c5554ae589c907a
Author: Bala.FA <barumuga@redhat.com>
Date:   Thu Mar 28 12:42:45 2013 +0530

    glusterd: add more specific log messages
    
    Change-Id: I57fbdd83f3098e64886c3dd690a1ae04fc37442d
    BUG: 928648
    Signed-off-by: Bala.FA <barumuga@redhat.com>
    Reviewed-on: http://review.gluster.org/4739
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b38d98e706724eb80a822f82c3c265d3ea41ff54
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Mar 4 16:23:46 2013 +0530

    Tests: Change rebalance status verification
    
    According to the comment at the following URL
    https://bugzilla.redhat.com/show_bug.cgi?id=916226#c2
    "success:" can come even before rebalance is completed.
    Changed it to check for "completed" instead.
    
    Change-Id: Ibe9d3b75493240f30261ac2a1280f32ef32886da
    BUG: 916226
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4614
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6b393b3ab6799ede09f6d2b303e35b8bc505f465
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Mar 3 20:41:30 2013 +0530

    cluster/afr: detect in-progress creation in lookup and return ENOENT
    
    if any subvol returned ENOENT while parent entrylk lock was held,
    yield and return ENOENT for the entire lookup.
    
    This is how the issue happens:
    
    Multiple clients A, B and C are attempting 'mkdir -p /mnt/a/b/c'
    
    1 Client A is in the middle of mkdir(/a). It has acquired lock.
      It has performed mkdir(/a) on one subvol, and second one is still
      in progress
    2 Client B performs a lookup, sees directory /a on one,
      ENOENT on the other, succeeds lookup.
    3 Client B performs lookup on /a/b on both subvols, both return ENOENT
      (one subvol because /a/b does not exist, another because /a
      itself does not exist)
    4 Client B proceeds to mkdir /a/b. It obtains entrylk on inode=/a with
      basename=b on one subvol, but fails on other subvol as /a is yet to
      be created by Client A.
    5 Client A finishes mkdir of /a on other subvol
    6 Client C also attempts to create /a/b, lookup returns ENOENT on
      both subvols.
    7 Client C tries to obtain entrylk on on inode=/a with basename=b,
      obtains on one subvol (where B had failed), and waits for B to unlock
      on other subvol.
    8 Client B finishes mkdir() on one subvol with GFID-1 and completes
      transaction and unlocks
    9 Client C gets the lock on the second subvol, At this stage second
      subvol already has /a/b created from Client B, but Client C does not
      check that in the middle of mkdir transaction
    10 Client C attempts mkdir /a/b on both subvols. It succeeds on
       ONLY ONE (where Client B could not get lock because of
       missing parent /a dir) with GFID-2, and gets EEXIST from ONE subvol.
    This way we have /a/b in GFID mismatch. One subvol got GFID-1 because
    Client B performed transaction on only one subvol (because entrylk()
    could not be obtained on second subvol because of missing parent dir --
    caused by premature/speculative succeeding of lookup() on /a when locks
    are detected). Other subvol gets GFID-2 from Client C because while
    it was waiting for entrylk() on both subvols, Client B was in the
    middle of creating mkdir() on only one subvol, and Client C does not
    "expect" this when it is between lock() and pre-op()/op() phase of the
    transaction.
    
    Original-author: Anand Avati <avati@redhat.com>
    Change-Id: Idca475dbbc2a51e09da6fa0f9e1e37148caef208
    BUG: 860210
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4625
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 93175bd20eaacf51b98d67963a9372af52b83634
Author: Alex Wheeler <wheelear@gmail.com>
Date:   Fri Mar 29 10:56:17 2013 -0400

    Adds missing functions to ring.py, and more thorough tests.
    
    Situation:
    The function get_part_nodes is being called by Openstack-Swift's proxy/controllers/base.py:
            https://github.com/openstack/swift/blob/1.7.4/swift/proxy/controllers/base.py#L410
            https://github.com/openstack/swift/blob/1.7.6/swift/proxy/controllers/base.py#L447
    As this was not implemented in the current GlusterFS version of ring.py, it was calling swift's
    original get_part_nodes, which would often return the incorrect node, resulting in the incorrect
    drive being associated with a request.
    There is another function that the original ring.py implements -- get_other_nodes, which has to
    do with replication.  Since GlusterFS is handling replication, this function should never be
    called.  However, in the interest of completeness, that function is also being replaced.
    
    Code changes:
    The two functions, get_part_nodes, and get_other_nodes have been implemented to override the
    default functions, and get_nodes has been updated to store information in self vars, about the
    account being operated on, as the two new functions are not called with that info, and get_nodes
    appears to always be called first.
    The code has be refactored to all call _get_part_nodes, much like swift has refactored their code.
    
    Reason for implementation this way:
    I didn't see a better way to do it, but am open to suggestions.
    
    Test cases:
    A mock ring is created with two different devices, test and iops
    
    test_first_device: Ensure that the first device, test, is returned for both get_nodes, and
            get_part_node, and get_more_nodes returns volume_not_in_ring.
    test_invalid_device: Ensure that a request for a non-existant device returns volume_not_in_ring.
    test_second_device: Same as test_first_device, but for the second device, iops instead of test.
    test_second_device_with_reseller_prefix: Test that calling with the reseller prefix, AUTH_ will
            still return the correct data.
    
    Change-Id: I2f3d526934a47b01e9c065d0edf0fbf06f300369
    BUG: 924792
    Signed-off-by: Alex Wheeler <wheelear@gmail.com>
    Reviewed-on: http://review.gluster.org/4748
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f3a9e390afd4088fdd805d5a8b917924d34cecff
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Mar 13 17:35:25 2013 +0530

    rpc/nfs: cleanup legacy code of general options
    
    Removing the code which handles "general" options.
    Since it is no longer possible to set general options which
    apply for all volumes by default, this was redundant.
    
    This cleanup of general options code also solves a bug wherein
    with nfs.addr-namelookup on, nfs.rpc-auth-reject wouldn't work
    on ip addresses
    
    Change-Id: Iba066e32f9a0255287c322ef85ad1d04b325d739
    BUG: 921072
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4691
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 87300be91cb9e1cd98ac5cba8998524d95c98d12
Author: Anand Avati <avati@redhat.com>
Date:   Sat Mar 23 13:55:09 2013 -0700

    synctask: introduce synclocks for co-operative locking
    
    This patch introduces a synclocks - co-operative locks for synctasks.
    Synctasks yield themselves when a lock cannot be acquired at the time
    of the lock call, and the unlocker will wake the yielded locker at
    the time of unlock.
    
    The implementation is safe in a multi-threaded syncenv framework.
    
    It is also safe for sharing the lock between non-synctasks. i.e, the
    same lock can be used for synchronization between a synctask and
    a regular thread. In such a situation, waiting synctasks will yield
    themselves while non-synctasks will sleep on a cond variable. The
    unlocker (which could be either a synctask or a regular thread) will
    wake up any type of lock waiter (synctask or regular).
    
    Usage:
    
        Declaration and Initialization
        ------------------------------
    
        synclock_t lock;
    
        ret = synclock_init (&lock);
        if (ret) {
            /* lock could not be allocated */
        }
    
       Locking and non-blocking lock attempt
       -------------------------------------
    
       ret = synclock_trylock (&lock);
       if (ret && (errno == EBUSY)) {
          /* lock is held by someone else */
          return;
       }
    
       synclock_lock (&lock);
       {
          /* critical section */
       }
       synclock_unlock (&lock);
    
    Change-Id: I081873edb536ddde69a20f4a7dc6558ebf19f5b2
    BUG: 763820
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4717
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit af939370ad20fe1be8e52ea953996e190e86c4ee
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sat Mar 9 16:36:56 2013 +0530

    cluster/afr: sync xattrs removed on source to sink(s)
    
    xattrs are first removed from sink followed by setting
    source xattrs.
    
    Change-Id: I181cb5b785b667bbfc6e40787a2183a8f45de06b
    BUG: 906646
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4656
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 864ac6b7b3d69b5f2cc0fafe4b12d861da3a633c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Apr 2 00:24:45 2013 +0530

    cluster/afr: prevent piggyback on stale pre_op
    
    Here are the logs of a file on which we saw EIO because of size mismatch:
    [root@lizzie ~]# grep 38f18204 /var/log/glusterfs/mnt-x-.log
    Reporting Unstable write for 38f18204-2840-408e-ae65-c01f4106b8c4
    for offset: 0, len: 7680
    
    Cleared unstable write flag for 38f18204-2840-408e-ae65-c01f4106b8c4:
    offset 0 length 7680
    
    Reporting Unstable write for 38f18204-2840-408e-ae65-c01f4106b8c4 for
    offset: 7680, len: 71680
    
    Reporting Unstable write for 38f18204-2840-408e-ae65-c01f4106b8c4 for
    offset: 79360, len: 15716
    
    fsync completed on 38f18204-2840-408e-ae65-c01f4106b8c4 for
    offset 0 length 7680 with changelog status: -1 -1
    
    According to these logs fsync did not happen after writev with
    offset: 79360, len: 15716. Which is the reason for this problem.
    
    In total 3 writes came. lets call them w1, w2, w3
    w1 does pre_op so pre_op_done[0], pre_op_done[1] counts become 1 and 1
    then is_piggyback_post_op() is called for w1 and it returns *false*
    
    w1's fsync is fired
    
    Now w2 and w3 come and see that pre_op_done[0], pre_op_done[1] are both 1,
    so pre_op_piggyback[0] and pre_op_piggyback[1] are both incremented twice,
    once by w2, one more time by w3 and become 2, 2  ------- Step-A
    
    Now fsync of w1 is complete and it goes ahead with post op and decrements
    pre_op_done[0], pre_op_done[1] to 0, 0
    
    Now w2, w3 writevs complete and is_piggyback_post_op will return *true* for
    both w2, w3.
    So fsync is not fired for both w2, w3
    
    this patch prevents Step-A from happening.
    
    Change-Id: I8b6af1f1875b2cf5f718caa3c16ee7ff3dc96b5c
    BUG: 927146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4752
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e0616e9314c8323dc59fca7cad6972f08d72b936
Author: Anand Avati <avati@redhat.com>
Date:   Sun Mar 17 03:32:44 2013 -0700

    dht: improve transform/detransform of d_off (and be ext4 safe)
    
    The scheme to encode brick d_off and brick id into global d_off has
    two approaches. Since both brick d_off and global d_off are both 64-bit
    wide, we need to be careful about how the brick id is encoded.
    
    Filesystems like XFS always give a d_off which fits within 32bits. So
    we have another 32bits (actually 31, in this scheme, as seen ahead) to
    encode the brick id - which is typically plenty.
    
    Filesystems like the recent EXT4 utilize the upto 63 low bits in d_off,
    as the d_off is calculated based on a hash function value. This leaves
    us no "unused" bits to encode the brick id.
    
    However both these filesystmes (EXT4 more importantly) are "tolerant" in
    terms of the accuracy of the value presented back in seekdir(). i.e, a
    seekdir(val) actually seeks to the entry which has the "closest" true
    offset.
    
    This "two-prong" scheme exploits this behavior - which seems to be the
    best middle ground amongst various approaches and has all the advantages
    of the old approach:
    
    - Works against XFS and EXT4, the two most common filesystems out there.
      (which wasn't an "advantage" of the old approach as it is borken against
       EXT4)
    
    - Probably works against most of the others as well. The ones which would
      NOT work are those which return HUGE d_offs _and_ NOT tolerant to
      seekdir() to "closest" true offset.
    
    - Nothing to "remember in memory" or evict "old entries".
    
    - Works fine across NFS server reboots and also NFS head failover.
    
    - Tolerant to seekdir() to arbitrary locations.
    
    Algorithm:
    
    Each d_off can be encoded in either of the two schemes. There is no
    requirement to encode all d_offs of a directory or a reply-set in
    the same scheme.
    
    The topmost bit of the 64 bits is used to specify the "type" of encoding
    of this particular d_off. If the topmost bit (bit-63) is 1, it indicates
    that the encoding scheme holds a HUGE d_off. If the topmost bit is is 0,
    it indicates that the "small" d_off encoding scheme is used.
    
    The goal of the "small" d_off encoding is to stay as dense as possible
    towards the lower bits even in the global d_off.
    
    The goal of the HUGE d_off encoding is to stay as accurate (close) as
    possible to the "true" d_off after a round of encoding and decoding.
    
    If DHT has N subvolumes, we need ROOF(Log2(N)) "bits" to encode the brick
    ID (call it "n").
    
    SMALL d_off
    ===========
    
    Encoding
    --------
        If the top n + 1 bits are free in a brick offset, then we leave the
    top bit as 0 and set the remaining bits based on the old formula:
    
       hi_mask = 0xffffffffffffffff
    
       hi_mask = ~(hi_mask >> (n + 1))
    
       if ((hi_mask & d_off_brick) != 0)
           do_large_d_off_encoding ()
    
       d_off_global = (d_off_brick * N) + brick_id
    
    Decoding
    --------
        If the top bit in the global offset is 0, it indicates that this
    is the encoding formula used. So decoding such a global offset will
    be like the old formula:
    
       if ((d_off_global & 0x8000000000000000) != 0)
          do_large_d_off_decoding()
    
       d_off_brick = (d_off_global % N)
    
       brick_id = d_off_global / N
    
    HUGE d_off
    ==========
    
    Encoding
    --------
       If the top n + 1 bits are NOT free in a given brick offset, then we
    set the top bit as 1 in the global offset. The low n bits are replaced
    by brick_id.
    
        low_mask = 0xffffffffffffffff << n   // where n is ROOF(Log2(N))
    
        d_off_global = (0x8000000000000000 | d_off_brick & low_mask) + brick_id
    
        if (d_off_global == 0xffffffffffffffff)
            discard_entry();
    
    Decoding
    --------
        If the top bit in the global offset is set 1, it indicates that
    the encoding formula used is above. So decoding would look like:
    
        hi_mask = (0xffffffffffffffff << n)
        low_mask = ~(hi_mask)
    
        d_off_brick = (global_d_off & hi_mask & 0x7fffffffffffffff)
    
        brick_id = global_d_off & low_mask
    
        If "losing" the low n bits in this decoding of d_off_brick looks
    "scary", we need to realize that till recently EXT4 used to only
    return what can now be expressed as (d_off_global >> 32). The extra
    31 bits of hash added by EXT recently, only decreases the probability
    of a collision, and not eliminate it completely, anyways. In a way,
    the "lost" n bits are made up by decreasing the probability of
    collision by sharding the files into N bricks / EXT directories
        -- call it "hash hedging", if you will :-)
    
    Thanks-to: Zach Brown <zab@redhat.com>
    Change-Id: Ieba9a7071829d51860b7c131982f12e0136b9855
    BUG: 838784
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4711
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 25053c9bdaf16f150815fb99f725bd037a49e97e
Author: M S Vishwanath Bhat <vbhat@redhat.com>
Date:   Thu Mar 21 18:51:57 2013 +0530

    cli: Made volume top help string clear
    
    nfs option is not applicable for read-perf and
    write-perf
    nfs option and brick option can not be used in
    same command
    
    Change-Id: I920ba0de011df0cc5e0adca6597aaea9372fe592
    BUG: 924335
    Signed-off-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Reviewed-on: http://review.gluster.org/4706
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 58bbfd91d1a6404ddee8fa2c49d0d1945eef5ad4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 27 18:56:35 2013 +0530

    mgmt/glusterd: Enable write-behind in nfs
    
    We observed that the number of write requests thus inodelks
    are increasing very rapidly to thousands without write-behind
    in the graph.
    
    Change-Id: Id71c9c2b0a4c9601a4644a58a933221c62dab0c0
    BUG: 928341
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4734
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d5c3024f9fb4e1671d8e0a969934350bb08e2db9
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Mar 26 14:15:58 2013 +0530

    rpc: disable root-squash dynamically upon volume set command
    
    Change-Id: I2ba9ca339ffbe07cb74833165a46a941225b623d
    BUG: 927616
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4722
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fdb05c6f84054ca640e3da1c19ea7d536d2751e0
Author: Anand Avati <avati@redhat.com>
Date:   Mon Mar 25 12:18:13 2013 -0700

    storage/posix: honor O_SYNC and O_DSYNC sent in @flags of writev()
    
    Historic bug - posix_writev() has been inspecting pfd->flushwrites for
    performing fsync() after write, instead of @flags for O_SYNC|O_DSYNC.
    
    pfd->flushwrites was never set anywhere and is unused completely. This
    is behavior from the time before anonymous FD where open() had @wbflags
    param. This is a leftover from that cleanup.
    
    Change-Id: Id9bfe562a60db4eb3bd0a7705bdba91f2df2f3ec
    BUG: 916372
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4738
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 0b81f2801b7a72130d86c88da938f288430cd3e5
Author: Anand Avati <avati@redhat.com>
Date:   Mon Mar 25 20:34:43 2013 -0700

    cluster/afr: fix fd leak with unsafe call_resume()
    
    Introduce AFR_CALL_RESUME macro which cleans up frame->local, like
    how AFR_STACK_UNWIND etc. do.
    
    Therefore fix leak in afr_fsync() path.
    
    Change-Id: I3855d8e7e84dbc44e05f507563b7f722bf9621b8
    BUG: 927146
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4745
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6ae6f3db02ec374448e9286b03651849ae30dff0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 28 22:26:24 2013 +0530

    cluster/afr: fsync before erase xattrs in data self-heal
    
    Added extra fsync to data self-heal code to make sure the
    data reached disk before erasing the changelogs
    
    Change-Id: I9e7e6e55cdc49de2b991705d1638946464a9d4f9
    BUG: 927146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4744
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2cd9b31a5f032af807dea7b3d1b40592444154b5
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Mar 28 11:41:25 2013 -0400

    glusterfs.spec.in: sync with fedora glusterfs.spec
    
    add --without ufo
    
    Change-Id: If1b77003ded537f9664fa6ad677d48d118516c64
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    BUG: 819130
    Reviewed-on: http://review.gluster.org/4742
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Luis Pabon <lpabon@redhat.com>
    Reviewed-by: Luis Pabon <lpabon@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ca6a3d1e396a65d25e54d331bef966178cd55375
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Mar 28 11:29:41 2013 +0530

    cluster/afr: piggyback and fsync resume changes
    
    1) pre_op_piggyback should always be decremented.
    2) Move fsync resume to just after post_op.
    3) fsync stub should be created from afr's local
       not from the final response.
    
    Change-Id: I220bb532eb03bea584292f4dd2e816ad0c3e0cf7
    BUG: 927146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4741
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8909c28c1173e10fd2f10706bd8a0f2ca5b5d685
Author: Anand Avati <avati@redhat.com>
Date:   Wed Mar 27 19:55:58 2013 -0700

    cluster/afr: fsync() guarantees POST-OP completion
    
    AFR now provides a stronger guarantee that fsync() returns only
    after completely finishing all the deferred/delayed POST-OP on that
    open file.
    
    To acheive this we make a stub out of the returning fsync and
    register it with the "delayed" frame in afr_changelog_wake_resume().
    
    The delayed frame, after getting woken up and finishing the POST-OP
    will call_resume() the registered stub (which UNWINDs the fsync) at
    the time of frame destruction.
    
    This provides a guarantee that an application's (or FUSE) fsync()
    returns only after finishing up all the previous transactions,
    including delayed POST-OPs and UNLOCK.
    
    Change-Id: Iaa955457e2f25088a144fde37ad0444277b5cf49
    BUG: 927146
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4737
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit ca10fdc81a72a71ac67ac9fc8c5ad5b92febd875
Author: Anand Avati <avati@redhat.com>
Date:   Sun Mar 24 12:19:56 2013 -0700

    cluster/afr: ensure DATA operations are made durable before POST-OP
    
    The changelogging scheme of AFR stores information about the state
    of all replicas in all replicas (in the extended attribute of the
    respective files on each server) in the form of 'pending counts'
    of operations (effectively "dirty flags"). These xattrs are blindly
    trusted while performing self-heal, and therefore utmost care has
    to be taken while updating and maintaing them.
    
    The most critical updation is the clearing of the pending counts
    corresponding to the *other* server in the changelog of a given
    server. Before clearing the pending count, we need durability
    guarantee of the write which was performed on the other server.
    
    To obtain such a guarantee, it may be necessary to explicitly
    introduce an fsync() phase (if the file itself wasn't already
    opened with O_SYNC).
    
    This patch introduces the detection of unstable stable writes on
    a file and issues explicit fsync() on the servers before performing
    the POST-OP clearing of pending flags.
    
    Change-Id: I2171b86a74ec91e40e5877eef0a4e7379578ecf7
    BUG: 927146
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4721
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1f7dadccd45863ebea8f60339f297ac551e89899
Author: Vijaykumar koppad <vijaykumar.koppad@gmail.com>
Date:   Tue Mar 26 17:42:32 2013 +0530

    libglusterfs/dict: fix infinite loop in dict_keys_join()
    
    	 - missing "pairs = next" caused infinite loop
    
    Change-Id: I9171be5bec051de6095e135d616534ab49cd4797
    BUG: 905871
    Signed-off-by: Vijaykumar Koppad <vijaykumar.koppad@gmail.com>
    Reviewed-on: http://review.gluster.org/4723
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 87d03fa7f48af6500cb8277db96ee7f6c690ea1c
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Feb 27 17:55:47 2013 +0530

    glusterd: Removed fd leaks in glusterfs_start utility function
    
    PROBLEM:
        The FILE* associated with the pidfile was leaked if
        pmap_registry_search on the brickinfo' path failed.
    
    FIX:
        Eliminates the use of the FILE* that was leaked. Uses
        glusterd_is_service_running utility function in place
        of the earlier attempt to check for the same.
    
    Change-Id: I94082bd5a94b8a6340f8cc11726d3264e364efe6
    BUG: 916549
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4596
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 544945a128b4de9c6b767939fb4c4c216b095d23
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Mar 25 08:22:16 2013 -0400

    config: better (i.e. more portable) test for libxml2
    
    Over the weekend I tried to build on MacOS X¹ and ran into the following
    issues:
    1) The recent change to autogen.sh to test for pkg-config falls down.
    2) After removing the pkg-config test in autogen.sh, w/o pkg-config the
       PKG_CHECK_MODULES macro invocation in configure[.ac] falls down. N.B.
       Solaris users run into this too, even through there's a (broken)
       pkg-config package that can be installed.
    3) There are other problems in the code related to fuse that are beyond the
       scope of this.
    
    It seems that pkg-config is only a requirement for the definition of the
    PKG_CHECK_MODULES macro used to detect libxml2. Since this seems to be
    inherently unportable — at least to MacOS X and Solaris — I'd like to:
    A) Change the use of the PKG_CHECK_MODULES macro to the more portable
       AM_PATH_XML2 macro provided by the libxml2 package in
       /usr/.../share/aclocal/libxml.m4
    2) Revisit the decision to add the check for pkg-config in autogen.sh in
       BZ 921817.
    
    For now this is just an rfc. If people are agreeable I'll reenter this
    change against BZ 921817.
    
    ¹Mountain Lion 10.8.3, XCode 4.6.1
    
    Change-Id: I237b1ed8919088345b8fd943423b2a6ad289981b
    BUG: 921817
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4720
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Justin Clift <jclift@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8db38ffbb887e3ba7661b97ebb4ac072f2d0ca8f
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Mar 25 00:12:52 2013 +0530

    glusterd: Simplify glusterd_service_stop()
    
    Change-Id: I396d250a3299ad1f7fce4bd14389b0c2756b6cb0
    BUG: 764890
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4718
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e701fb2713510f80a8a45c932637bcb52b5a103e
Author: Anand Avati <avati@redhat.com>
Date:   Thu Mar 21 15:09:01 2013 -0700

    glusterfsd: dump the in-memory graph rather than volfile
    
    Currently we have been printing in the logfile, the volfile
    verbatim as received from the server. However we perform
    pre-processing on the graph we receive from the server, like
    adding ACL translator, applying --xlator-option cli params,
    etc.
    
    So print the serialized in-memory graph as the "volfile" in
    the log. This can be very handy to double check if certain
    --xlator-option param actually got applied or not, and in
    general is showing a "truer" representation of the real graph
    actually used.
    
    Change-Id: I0221dc56e21111b48a1ee3e5fe17a5ef820dc0c6
    BUG: 924504
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4708
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 71cb0ad45b5be318e0ea2df91ea17e4c448a2a52
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Mar 12 17:03:53 2013 +0530

    mount: Added the xlator-option to mount.glusterfs script.
    
    Now all xlator-options can be set from the mount command as well.
    Example :
    mount -t glusterfs Hostname:/Volume_Name Mount_Point -o "xlator-option=xyz=123, xlator-option=abc=999"
    
    Change-Id: If52d994986839d1c969e3e2e01b2e1a29a3140b7
    BUG: 920583
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4660
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 71496826955cacac37abfd5fd017340a04988971
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Mar 20 23:01:39 2013 +0530

    glusterfsd: Fixed fd leak due to use of tmpfile()
    
    Change-Id: I3c2dc070ebe967100170e39f3545acacc6016d61
    BUG: 924075
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4703
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e0e34d04aa68ac154818b55e7c337607fb141971
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Mar 20 18:48:12 2013 +0100

    glusterd: Improve error logging when a brick from an old volume gets re-used
    
    The error message when creating a volume that contains a brick with
    certain xatts set on a parent directory is unclear.
    
    Users do not understand '... or a prefix of it is already part of
    a volume'. Most users check the final directory that is used for
    a brick, but not its parents.
    
    It would be helpful to present the user with the actual directory that
    is preventing the volume to use the brick.
    
    BUG: 923917
    Change-Id: I815ad32a992eb0e41ee8fca6ee9327400d042c45
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4701
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1a5979dc09e15dbc83aada0b7647d2482e431884
Author: Anand Avati <avati@redhat.com>
Date:   Thu Mar 21 13:46:51 2013 -0700

    nfs: ACCESS - reply only what was asked for
    
    Set only those bits which were requested by the client. Some clients,
    like AIX, do not like the fact that we are returning the EXEC bit
    set in the ACCESS reply even though it only asked for LOOKUP bit.
    
    Change-Id: I3c2fd5dce030ea5ddae0511497cafa078c4d76d6
    BUG: 924481
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4707
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 259ff34b33ac2c5aa2e541b1019f93da47f7428a
Author: Justin Clift <jclift@redhat.com>
Date:   Fri Mar 22 18:44:06 2013 +0000

    Added autogen.sh check for presence of tar
    
    Change-Id: I95313699edcf7bc2696505fcb475a4a67c1800cf
    BUG: 924891
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/4716
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bf3db1f609a9eb6de4dead98f6cc6e9beedf1975
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Mar 15 02:44:19 2013 -0400

    glusterfs.spec.in: sync with fedora glusterfs.spec
    
    remove hard-coded reference to swift version and dist tarballs
    
    minor improvements for rpm builds for regression tests, including
    adding cache on build.gluster.org to avoid random failures due to
    transient network or dns failures causing curl or git to fail.
    
    BUG: 819130
    Change-Id: I4f1213056ae2987dd2202f9cfbb3ed4f16ffc7cf
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4674
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Justin Clift <jclift@redhat.com>
    Tested-by: Justin Clift <jclift@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fec34ce4531d37ed6639054f1071f9123883251a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Mar 14 09:48:08 2013 +0530

    socket: Make non-ssl sockets perform non-blocking connect()
    
    Change-Id: Icb60cf7ad3ea7ca0eeb12fd19b95a6b340857bb2
    BUG: 920916
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4670
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 76bc5d1b2d25a4f25f4cf458e43ec3e19c3efae6
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Mar 19 14:06:39 2013 -0400

    dht: make DHT xattr names configurable
    
    This is necessary to support "DHT over DHT" configurations, so that the
    upper and lower instances of DHT don't step all over each other.  Why
    would we even consider such a thing?  Because it gives us the ability to
    do data tiering and rack-aware placement, either by themselves or as
    complements to other functionality such as erasure codes or
    deduplication which save space but cost performance.  By setting up the
    top-level DHT to place data into one of several lower-level DHT pools
    based on policy instead of pure elastic hashing, we get better
    performance for 90% of accesses and better storage efficiency for 90% of
    data, all for relatively low effort.
    
    Change-Id: I72e65c29edfc80babf39f7a2a00090f4588c4070
    BUG: 924265
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4694
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 790cbb82a12accc99312117bfa632227c8127f53
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Tue Mar 19 09:29:52 2013 +0530

    object-storage: Removed the redundant REMOTE_CLUSTER option.
    
    Gluster cli uses the remote-host option to connect to the glusterd
    and by default it uses localhost to connect to glusterd. So, UFO code
    will use the remote-host option everytime to connect to the glusterd.
    
    Change-Id: I5a684d3c43fe9bdc9cc0b7c472a9d8145f9e1fd4
    BUG: 878663
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4690
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5d19cddd601b2819d2ea908961c7ea9835beccc7
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Thu Mar 21 16:40:16 2013 +0530

    rpc-transport: fix glusterd crash when rdma.so missing
    
    Add checks before trying to delete vol_opt from list and free
    
    Change-Id: I2858f58518394beb8f74fa477be81d7bdd38304f
    BUG: 924215
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4704
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d8926b5e91091f896b877136238eef87383f72ed
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Mar 7 23:22:32 2013 +0530

    features/marker: log error when unlinking timestamp file
    
    ... so it's easy to figure out errno caused it. As of now
    it's only due to ENOSPC. Logging is done in the error handling
    routine, so any further changes that require unlinking of the
    timestamp file due to some error condition(s) are logged.
    
    Change-Id: Ia59338e2e32b2adbbd1d56aa260018270f1abae9
    BUG: 853911
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4649
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 66d5d91465deba55afa9e1ab3a2160fc9d1b9275
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 20 08:36:14 2013 +0530

    performance/io-threads: Fix range-check for least-rate-limit
    
    The issue could be fixed with .validate=GF_OPT_VALIDATE_MIN. But
    adding max value is more robust.
    
    Change-Id: Ia69c6f86855dbd34a26e20391e77bfa0f796a200
    BUG: 923573
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4698
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1d575d1706bf9968b84d10031bf4b2cfc571db91
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Mar 18 19:18:53 2013 +0530

    socket: Associated IP:port information with error logs to make debugging easier
    
    Change-Id: I4e7268f74b392c5cee8c7b8fc4bb5ab41d74dd04
    BUG: 922780
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4686
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f6d32dd6e8d0e4f52508162783b18828c0c363fa
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Mar 18 19:14:24 2013 +0530

    rpc: before freeing the volume options object, delete it from the list
    
    * Suppose there is an xlator option which is considered by the xlator
      only if the source was built with debug mode enabled (the only example
      in the current code base is run-with-valgrind option for glusterd), then
      giving that option would make the process crash if the source was not
      built with debug mode enabled.
    
      Reason:
      In rpc, after getting the options symbol dynamically, it was stored in the
      newly allocated volume options structure and the structure's list head was
      added to the xlator's volume_options list. But while freeing the structure
      the list was not deleted. Thus when the list was traversed, already freed
      structure was accessed leading to segfault.
    
    Change-Id: I3e9e51dd2099e34b206199eae7ba44d9d88a86ad
    BUG: 922877
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4687
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 78bf67f6d1caff4b56060a5029b0620f57634fc5
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Mar 20 10:52:08 2013 +0530

    cli: Better message on rebalance/remove-brick stop
    
    A better message is displayed when rebalance or remove-brick is stopped,
    as migration may be still in progress.
    
    Change-Id: I5f301cc66f349a1a85245f7d7508bf746756bdea
    BUG: 923529
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4695
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7645411f134c2b7ae004f0a8478449965e424a97
Author: Anand Avati <avati@redhat.com>
Date:   Wed Feb 27 14:30:15 2013 -0800

    nfs: handle stable write with @flags rather than fsync()
    
    stable writes can be "made stable" by simply setting O_SYNC (or
    O_DSYNC, accordingly) in the write flags or fd->flags. Performing
    fsync() at the end of the write is extremely inefficient and completely
    messes up eager-locking logic in AFR.
    
    Change-Id: I4d954c133641e246b2ab4df874bad0282667561f
    BUG: 916372
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4591
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fbb94768cb579f85416333f98a0fa655e10f88fc
Author: Prashanth Pai <nullpai@gmail.com>
Date:   Fri Feb 22 15:52:29 2013 +0530

    iobuf: Added a function iobref_clear
    
    Original-author: Venky Shankar <vshankar@redhat.com>
    
    Change-Id: Ibf861db6c1b084b798d210962344487a1919aad2
    BUG: 921942
    Signed-off-by: Prashanth Pai <nullpai@gmail.com>
    Reviewed-on: http://review.gluster.org/4595
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f325551e4c56f743cd1e2b9174d8b7dc9f861675
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Mar 20 11:39:01 2013 +0530

    nfs, afr: Fail lookup only on split-brain
    
    Change-Id: Icee9772f1f1bf5336eb82a4dc13e198424cd4a65
    BUG: 921996
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4699
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1cc57ff832cc48634cd697b828551f4cc3ee42b8
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Mar 18 17:13:51 2013 +0530

    rpc: For AF_UNIX sockets, do not set keepalive option.
    
    Change-Id: I65df52e89fe7783ff00c2b7a49be571d15e8f0d0
    BUG: 920009
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4684
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1975c5416402f3a64d5359e50a2c48b44f100d16
Author: JulesWang <w.jq0722@gmail.com>
Date:   Mon Mar 18 10:06:06 2013 +0800

    dht: fix a typo
    
    Change-Id: Id6f156957e58aad06bf2602f880c7e4102b80fd1
    BUG: 764890
    Signed-off-by: JulesWang <w.jq0722@gmail.com>
    Reviewed-on: http://review.gluster.org/4679
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1409ea2e80e8d15d3202bcf6e1b9c0e0d461697c
Author: Justin Clift <jclift@redhat.com>
Date:   Fri Mar 15 02:20:42 2013 +0000

    Warn on missing pkg-config, plus trivial comparator typo fix.
    
    Change-Id: I68eef93ee70a934feb9a53cca050b81a4e66e26c
    BUG: 921817
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/4672
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc988b255b33b323f9d310614d501a4069219831
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Mar 14 13:02:29 2013 +0530

    posix-acl: disable permission checks for fd based ops
    
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Change-Id: I9d49537c2c7b51d5598b80627d61f060aaec8549
    BUG: 921437
    Reviewed-on: http://review.gluster.org/4671
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 70df74418140e335ec56250dbce543b5faf066d5
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Feb 28 04:18:41 2013 +0100

    geo-rep: retire old style ssh setup
    
    Users are still using geo-rep with the old, deprecated, insecure, unsupported
    ssh setup. Not their fault -- the implementation of the new method had the
    following charasteristics:
    - old method is possible, but with default settings it's not working
    - it can be made operational by fiddling with "remote-gsyncd" tunable
    - with default setting, an unhelpful, actually misleading error message is
      produced
    - the UI gave no hint to the changes in the ssh setup
    
    http://review.gluster.org/4392 tried to fix these; what it accomplished was
    unrestricted support to the bad practice (by making the default old setup
    operational).
    
    From this on:
    - we disable the old method by reserving the "remote-gsyncd" tunable
    - if the old method is attempted, give a hint what to do
    
    Change-Id: Icade94725d8d8d2d4c89cab992d4226351637b86
    BUG: 895656
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/4602
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit caac150b2b0f799a09cab7b3b49498b9dc7ec0e8
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Mar 13 01:05:54 2013 -0400

    Renamed TMP_MAX to GF_TMP_MAX to avoid namespace clash on OSX.
    
    (Just moving things along. I don't mean to step on any toes, but wasn't
    sure if I had confused things with my previous review comment.)
    
    Change-Id: I095abf751ef952ba6e225305ec5c2afc5e62ee95
    BUG: 919953
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4654
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit ac524f5907058f96eb68ffe0503f60a37c0a5dc8
Author: Justin Clift <jclift@redhat.com>
Date:   Sat Mar 9 16:27:31 2013 +1100

    Fix improperly quoted PKG_CHECK_MODULES parameters.
    
    Change-Id: I11765fd1a25058b84fc32249ea745abefbade3f9
    BUG: 920372
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/4652
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8b5dbe6b43be3a5c23a7bd7ad1634b1e3b5bdc07
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Mar 5 17:43:26 2013 +0530

    Storage/posix: Don't log at ERROR level for failed getxattr.
    
    Problem:
    ENOATTR returned by
    getxattr -n <NotAnExistingAttribute> <file>
    was being logged at ERROR level.
    
    Solution:
    Moved logging to DEBUG level.
    
    Change-Id: I982a577a4c231faa958ea71abdb272f8d5ffd70c
    BUG: 918052
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4628
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8e495e92590107369626fdf98e93a7d0b2ca0507
Author: Justin Clift <jclift@redhat.com>
Date:   Sun Mar 10 21:35:54 2013 +0000

    Add missing pthread.h include to logging.h
    
    Change-Id: I986b3e978616510ed92903e192222be513297284
    BUG: 920369
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/4653
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 35660032d6549a519c3fd72d9e2044ff22614b38
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Mar 8 15:20:22 2013 +0530

    cluster/afr: Preserve mtime in self-heal
    
    Problem:
    Data self-heal may choose sink iatt to set mtimes.
    This happens because after syncing of data is done
    self-heal does one more xattrops/fstat to determine
    sources sinks to set the inode-ctx. Since this is done
    after data syncing and erase of xattrs, old source and
    old sink are now sources, but the mtimes of them differ.
    Old code just takes the first source from the list and
    update mtimes, which could be sink before the self-heal
    started.
    
    Fix:
    Set mtime from 'sources before syncing'.
    
    Change-Id: Id769e1b99aa4f041eaee775f64cbf2c57b799723
    BUG: 918437
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4658
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e125e2ae61c31da798ea9a7342ea9292f47c1d6b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 19 12:11:57 2013 +0530

    glusterd: Mark vol as deleted by renaming voldir before cleaning up the store
    
    PROBLEM:
    
    During 'volume delete', when glusterd fails to erase all information
    about a volume from the backend store (for instance because rmdir()
    failed on non-empty directories), not only does volume delete fail on
    that node, but also subsequent attempts to restart glusterd fail
    because the volume store is left in an inconsistent state.
    
    FIX:
    
    Rename the volume directory path to a new location
    <working-dir>/trash/<volume-id>.deleted, and then go on to clean up its
    contents. The volume is considered deleted once rename() succeeds,
    irrespective of whether the cleanup succeeds or not.
    
    Change-Id: Iaf18e1684f0b101808bd5e1cd53a5d55790541a8
    BUG: 889630
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4639
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit bc4350423a33d21464b507b4e229eb5244e0cb6e
Author: Varun Shastry <vshastry@redhat.com>
Date:   Fri Mar 8 15:27:57 2013 +0530

    features/quota: regression tests on general functionality of quota
    
    Change-Id: Ie8fd9d21f3a8644ce4d6f6cb887c101451cec10c
    BUG: 919998
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4657
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 69f17838000424a209a928fbdc0e608dfaf271d6
Author: Justin Clift <jclift@redhat.com>
Date:   Fri Mar 8 19:29:33 2013 +0000

    Add autogen.sh dependency checks and nicer output.
    
    Change-Id: I5c740d81765559fae022d0ab9dfe34988e46612e
    BUG: 919898
    Signed-off-by: Justin Clift <jclift@redhat.com>
    Reviewed-on: http://review.gluster.org/4651
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 930c4ada674804a8e5d2d90e0184437afdf2d7a0
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Mar 5 14:11:02 2013 +0530

    glusterd: Fixed volume-sync in synctask codepath.
    
    Change-Id: I2911d3ac80825310f84c5ba6bd7890e65e1ee219
    BUG: 865700
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4624
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b1755efdffacf5e3023a737974e6c8ffdc569386
Author: Lalatendu Mohanty <lmohanty@redhat.com>
Date:   Fri Mar 8 15:27:42 2013 +0530

    tests:Adding remove-brick test to volume.t
    
    Change-Id: Ibef0c151ef6518136cd5f4c39ec5e89f06ff4133
    BUG: 764966
    Signed-off-by: Lalatendu Mohanty <lmohanty@redhat.com>
    Reviewed-on: http://review.gluster.org/4650
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8500c9aff1d46a4cb129cdecac48ee369e46bebf
Author: Lars Ellenberg <lars@linbit.com>
Date:   Sat Mar 2 00:59:15 2013 +0100

    glusterd: fix segfault on volume status detail
    
    If for some reason glusterd_get_brick_root() fails,
    it frees the gf_strdup'ed *mount_point in its own error path,
    and returns -1.
    
    Unfortunately it already had assigned that pointer value
    to the output argument, the caller function
    glusterd_add_brick_detail() sees a non-NULL pointer,
    and free() again: segfault.
    
    Could be fixed with a one-liner (*mount_point = NULL)
    in the error path, but I think glusterd_get_brick_root()
    should only assign to the output argument once all checks passed,
    so I use a local temporary pointer, which increases the patch a bit.
    
    Change-Id: I3f3035f01e80a5e9bdf2da895e4cf7baa3dfbd2f
    BUG: 919352
    Signed-off-by: Lars Ellenberg <lars@linbit.com>
    Reviewed-on: http://review.gluster.org/4646
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 140e9756a569efd02ea970cb484d6f1a7c3da688
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Mar 7 19:41:33 2013 +0530

    cluster/distribute: Fix layout overlaps due to spread-count in selfheal path
    
    We needed to zero out the layout range, before we re-calculate the range.
    When spread-count is issued, we would end up with stale ranges in the layout.
    
    Replaced dht_selfheal_dir_xattr with dht_fix_dir_xattr, which correctly resets
    the un-used (after re-cal) layouts.
    
    Change-Id: I1a900d15df07335f59356bd23182ccec34381ab2
    BUG: 884455
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4647
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 90d77fbdd2c5066279f2c7ddeee0980811ba4923
Author: Anand Avati <avati@redhat.com>
Date:   Mon Mar 4 13:22:25 2013 -0800

    gfapi: dict_unref() xattr_req in fop finish instead of dict_destroy()
    
    The current way of calling dict_destroy() at the end of an API fop assumes
    that xattr_req is not stored/ref'd by any translators in the stack. However
    when translators like DHT store xattr_req in dht_local_t with a dict_ref()
    and perform dict_unref() in the unwind path, things get subject to a race.
    
    The race is between the woken up thread (by syncop_wake) i.e, the gfapi
    invoking thread and the thread where the FOP was unwound. As the C stack
    of STACK_UNWIND unwinds back, dht_local_unref() gets invoked within the
    DHT_STACK_UNWIND macro. This thread attempts dict_unref, which would
    be "safe" if it wins the race against the gfapi invoking thread. However
    if the gfapi invoking thread wins the race, it will perform dict_destroy()
    first and therefore make dict_unref() within dht_local_unref perform
    a double free.
    
    This is the embarrassing on-screen bug which showed up in a roomful of people
    during the gluster dev summit demo of qemu/libgfapi integration.
    
    Change-Id: I284c93de87cdc128d5801f42c84aa87f753090d4
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4644
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit ee5df68f08e44451e14c42adc9bc4d38721b5d6c
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Sun Feb 10 02:10:25 2013 +0530

    object-storage: Fixing the errors and warnings in unittest.
    
    Change-Id: Id22c968aefd82c4b62445b3ecc93cbabc2b35ffc
    BUG: 887301
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4394
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 598ca6bbaabc0b67708a1ecfbef1372eb9927ed9
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Thu Feb 7 07:42:34 2013 +0530

    object-storage: Restoring multi volume support in UFO.
    
    * Currently, the users of UFO are restricted to use just one volume
      at any given point of time. This patch removes this limitation.
    
    * The usage of gluster-swift-gen-builders has also changed. With this
      commit the users should mention the list of volumes that they want
      to expose through UFO. So, only the volumes mentioned during the
      ring file generation can be accessed.
    
      Usage: gluster-swift-gen-builders <vol-name1> [<vol-name2>]...
    
    This is an intermediate fix until we remove the account, container and
    object server processes. Once we have this frame work running, it will
    completely eliminate the ring files.
    
    Change-Id: I9ad3808519fec9c7c60ad846c4f8b653117a8337
    BUG: 909053
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4485
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Peter Portante <pportant@redhat.com>

commit b7b5c51bbeb6401c65cc879f7aacb9c7ca1c85b1
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Mar 6 14:04:51 2013 +0530

    storage/posix: Remove a redundant lstat in posix_handle_hard.
    
    Change-Id: I9129b71d5568eff3513c17e3607256783fdc42ec
    BUG: 903396
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4641
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 16ce96c299c93e09b1c1ddceaa75399a7211a7d0
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Mar 1 14:49:57 2013 +0530

    nlm: use appropriate open flags while locking
    
    In case of a shared/read lock, open the file in O_RDONLY
    mode, and in the case of an exclusive lock, open the file
    in O_WRONLY mode to emulate the behaviour posix fcntl
    implementation as given in the man pages.
    
    Change-Id: Ib9eab6570c3bc65f8bd48a14a9d801616213b295
    BUG: 916930
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4603
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2398e1e0da61f4ec5f209c704e037b54b5c249e1
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Mar 4 11:44:40 2013 +0100

    rpm: package /var/run/gluster so that statedumps can be created
    
    Creating statedumps fail when /var/run/gluster does not exist. This
    directory should be part of the 'glusterfs' package that is installed on
    storage servers and native clients.
    
    BUG: 917561
    Change-Id: Ibbc1e4016469fab3db0423337fabc4ba5a8302ab
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4616
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8203d34f5017034d1696c24dc78de16430df70ba
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Mar 1 09:55:44 2013 +0100

    cluster xlators: s/-1/GF_CLIENT_PID_GSYNCD/
    
    Change-Id: I03be3cb23684de4ab36cf2953002708466edd580
    BUG: 765433
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/4601
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9636e63913c98740cb428c026ea5f88a816d527e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Feb 26 12:39:17 2013 +0530

    glusterd: Added description for nfs.transport-type option in volume set help.
    
    Change-Id: I9fe81dc1c3172158e8dd86c4fa2a04af18cb9dde
    BUG: 782285
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4582
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1ffe690f563804ba1a87d3f526de32bc64e1a2cc
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Feb 26 11:37:30 2013 +0530

    Modified validation parameters for owner-uid and owner-gid.
    
    owner-uid and owner-gid will not receive negative values anymore.
    
    Change-Id: I82741d3d01b29e448294b2ec093fb70d22a5c77e
    BUG: 912297
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4581
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9dac72481beb92547d3554b3355f3497a73a7fff
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 27 18:36:32 2013 +0530

    cluster/afr: Turn on eager-lock for fd DATA transactions
    
    Problem:
    With the present implementation, eager-lock is issued for
    any fd fop. eager-lock is being transferred to metadata
    transactions. But the lk-owner is set to local->fd address
    only for DATA transactions, but for METADATA transactions
    it is frame->root. Because of this unlock on the eager-lock fails
    and rebalance hangs.
    
    Fix:
    Enable eager-lock for fd DATA transactions
    
    Change-Id: If30df7486a0b2f5e4150d3259d1261f81473ce8a
    BUG: 916226
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4588
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 29e75759d574952db96d9a85e20804af1eec7327
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Feb 26 18:34:53 2013 +0530

    libglusterfs: avoid the logging which says the port is invalid
    
    If the reserved ports file in proc contains just a newline, then
    do not proceed with ports checking and reserving.
    
    Change-Id: If610b0e49a97e5c22e7e2b1bb4155c9616a4612a
    BUG: 762989
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4583
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit d4269b00008ea727a0312a55f543f18e9a0d5edd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Feb 21 16:31:58 2013 +0530

    performance/write-behind: Add test case for fd being marked bad
                              after write failures.
    
    Change-Id: I5a3c27be0ad77b7f2660f45977f9f1f8f34ae31c
    BUG: 765473
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4560
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 549231dda9769f23eebf039bc0f7c34a4c086270
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Tue Feb 19 16:27:54 2013 +0530

    glusterd: Added the validation function for subvols-per-directory
    
    Change-Id: Ie2259023b9001311a2032792639c3093054f6750
    BUG: 896431
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4552
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 6788badddafd6c749136a6d1cbac030f031ada52
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Feb 28 10:54:36 2013 +0530

    glusterd: Fix some options in vme table
    
    Some of the options had invalid '.flags' members. In the original table
    these table these were supposed to be the op-versions, but, the entries
    for the below options were missing the flags field the op-version was
    entered in that place.
    
    Change-Id: I408f5a972743eb37d9a58a809e8be8cb385bced8
    BUG: 903478
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4593
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit da3f6576e4604a5bd7bff817886d561d856960e8
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Feb 27 17:04:47 2013 +0530

    cluster/distribute: Prevent spurious multiple defrag crawls
    
    In dht_notify, we used to create a thread to start defrag
    crawls after we had heard from all child subvols.
    This was in-correct, as a later event, could also trigger the
    crawl again(due to the fact that all subvols had responded).
    
    The fix is to make sure, the thread is started only once after
    all subvols have responded the first time
    
    Change-Id: Ifc2978b9dc866af2395b79911eca50ab38ff9457
    BUG: 916449
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4587
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8575228708c3655b45b90a36a32333536f04bd85
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Feb 27 17:41:11 2013 +0100

    Do not call xdr_string() with a NULL error message
    
    It is illegal to call xdr_string() with a NULL string. Linux
    just retruns false, NetBSD gets a SIGSEGV when xdr_string()
    calls strlen(NULL)
    
    BUG: 916439
    Change-Id: Ia958470ada6e8e55a86d439922ec942d038f5f13
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4589
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4579609e336b423639d844e3cd1d1fa0ff4c62ea
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Feb 21 15:35:18 2013 +0530

    glusterd: Added validation function for stripe-block-size.
    
    Change-Id: I050d01b01eac46550aa435da7d96a972e0393d35
    BUG: 770655
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4561
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 202bcaee24477dccf3a2047933a898ec0ad786c2
Author: Anand Avati <avati@redhat.com>
Date:   Wed Feb 27 12:18:59 2013 -0800

    cluster/dht: print hash function munging logs in DEBUG mode
    
    Change-Id: Ia2e6bce80710d103da9d78afdb389ea162b00686
    BUG: 912564
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4590
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit dafd31b7188057367cb9fb780f921f4bb8a930fb
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon Jan 7 15:50:57 2013 +0530

    cluster/distribute: Add filter to support file patterns to be migrated
    
    'gluster volume rebalance' command will be enhanced to support passing of these
    options/pattern.
    
    <pattern> is comma separated list as show below. The Precedence is from right
    to left.
    
    e.g- "*avi,*pdf:10MB,*:1KB"
         The precedence is as follows:
         migrate all files with size equal or greater than 1KB "*:1KB"
         migrate all pdf files with size equal or greater than 10MB "*pdf:10MB"
         migrate all avi files "*avi"
    
    With this option, it is possible to choose which files to migrate.
    
    Change-Id: I6d6d6a015bcbacf1debae2f278a2d92306fb055d
    BUG: 896456
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4366
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ae1a2902c2193cac46813728cdfde6227f8e0379
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 27 14:21:04 2013 +0530

    mgmt/glusterd: Move found-brick logs to DEBUG
    
    Change-Id: I1c311c21d7bdcad4956d3428bda39131c331cd7a
    BUG: 812356
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4585
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit dc8d19148a7cf16ead0eed60fe76e64a03391270
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Thu Dec 6 12:17:02 2012 +0530

    nfs/server: Fix multiple crashes in acl handling code.
    
    Change-Id: I9b39a485c8b98d9eabe6153487f4dfbd26f8af13
    BUG: 915280
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4578
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 990005435825bd4e66589d9a043951b388974ee3
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Feb 24 23:45:19 2013 +0530

    mgmt/glusterd: Expose error-gen options through volume set.
    
    Change-Id: I7c696d99b43544923fb96d177229cdbac32c09fe
    BUG: 915280
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4577
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 0c31e4515fc6c736d27cd9be8da3c95b1f33a21b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Feb 24 23:05:59 2013 +0530

    debug/error-gen: Add support for reconfiguring options.
    
    Change-Id: Ia10dc29e8608b02037b08e32a72766b6d43a98ba
    BUG: 915280
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4576
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 89ea4583161382de7e56007b3dee3359e2a41b98
Author: Anand Avati <avati@redhat.com>
Date:   Thu Feb 21 18:49:43 2013 -0800

    tests/cluster.rc: support for virtual multi-server glusterd tests
    
    Since http://review.gluster.org/4556 glusterd is capable of running
    many instances of itself on a single system. This patch exploits
    that feature and enhances the regression test framework to expose
    handy primitives so that test cases may be written to test glusterd
    in a cluster.
    
    Usage:
    
    1. Include "$(dirname)/../cluster.rc" to get access to the extensions
    
    2. Call launch_cluster $N where $N is the count of virtual servers
    
    Calling launch_cluster, starts $N glusterds which bind to $N different
    IPs and dynamically defines these primitives:
    
     - Variables $H1 .. $Hn assigned to hostnames of each "server".
    
     - Variables $CLI_1 .. $CLI_n assigned as commands to run CLI commands
       on the corresponding N'th server.
    
     - Variables $B1 .. $Bn assigned to the backend directories on each
       "server".
    
     - Function kill_glusterd, which accepts a parameter - index number of
       glusterd to be killed.
    
     - Variables $glusterd_1 .. $glusterd_n assigned to the command lines
       to restart the corresponding glusterd, if it was previously killed.
    
    The current set of primitives and functions were implemented with the goal
    of satisfying ./tests/bugs/bug-913555.t. The API will be made richer as
    we add more cluster test cases
    
    Change-Id: Ieb13ed9f4a72ac0321db0ca0844c7b294145bb32
    BUG: 913555
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4566
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 5e6dfce0b0d55d96b5bdad6a693fdb2826c20b92
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Feb 20 14:44:23 2013 +0530

    glusterd: Increasing throughput of synctask based mgmt ops.
    
    Change-Id: Ibd963f78707b157fc4c9729aa87206cfd5ecfe81
    BUG: 913662
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4570
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit dc43e7dd9934925f8cb96762c33be23ccb63528a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Feb 25 17:05:49 2013 +0530

    volgen: Use bind-address option for bricks when option set on glusterd
    
    Brick processes listen on all the interfaces on a given port.
    When multiple glusterds run on one machine, glusterd assumes
    that it 'owns' the ports on that machine. This can lead to the
    different glusterd instances to step on each other's ports.
    This fix ensures that brick processes listen only on the its
    host IP when glusterd has bind-address option set.
    
    Change-Id: I4c1b05643c64d3098bf56e977e768e611ffce0f5
    BUG: 913662
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4580
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 164c9586ae3b00128dbcea7791fc6178ae82b3af
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon Feb 25 10:02:15 2013 +0530

    cluster/distribute: Preserve file size during rebalance migration
    
    If holes are encountered, then we do not write these to the dst,
    which sometimes causes file size to be lesser than src. Data is not
    corrupted, as when non-zero reads are received, we do write that data.
    
    Calling a truncrate to give file size to prevent it from being
    truncated to less than src in case the file end has holes.
    
    Thanks to Brian Foster for providing the test case
    
    Change-Id: I3cdd143b63ec8d797273d76189dff8b05eb9e551
    BUG: 915554
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4574
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3f1ef648b969cb0acde4d920fc0ac21f533b51d0
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Feb 25 16:38:34 2013 +0530

    libglusterfs: Fixed valid_ipv4_address and valid_host_name
    
    In valid_ipv4_address(), strtok_r was ignoring consecutive dots,
    and was marking any address with consecutive dots as valid. Now
    such addresses will be marked as invalid.
    
    In valid_host_name(), any name ending with any special characters
    was marked as valid. Now such hostnames will be marked as invalid.
    
    Change-Id: If9b625d9040a14bde8c176fe36e337cb483e284a
    BUG: 822830
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4579
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 15d4ae7da9379c55ba4561265747bbbe261c4a9c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 20 09:53:41 2013 +0530

    cluster/afr: Don't queue transactions during open-fd fix
    
    Before Anonymous fds are available, afr had to queue up
    transactions if the file is not opened on one of its
    subvolumes. This happens until the attempt to open the
    file either succeeds or fails. These attempts happen
    until the file is successfully opened on the subvolume.
    Now client xlator uses anonymous fds to perform the fops
    if the fd used for the fop is not 'opened'.
    Fops will be successful even when the file is not opened
    so there is no need to queue up the transactions anymore in afr.
    Open is attempted on the subvolume where it is not
    opened independent of the fop.
    
    Change-Id: Id1a4b4ebe6f89f9efe8f6a8247918b91247d0819
    BUG: 913051
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4568
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8897d08e6af68b025bd10b1dffa680fcd2bcea5b
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Feb 21 12:37:26 2013 +0530

    glusterd: Added validation function for quota-timeout.
    
    Change-Id: I7f82f4217a41e0fe41272e6ef82925e1fe97fcd5
    BUG: 765230
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4557
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9f8a8df8146792d35caf56896129602ea22e65e1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Feb 21 16:29:43 2013 +0530

    tests: move common funtion definitions to include.rc
    
    Change-Id: I3526557d0a675692e94edb71b7d92c9202e6afa4
    BUG: 765473
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4559
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 91052d8b5677920f2e5aea56fc082e243c76ca43
Author: Anand Avati <avati@redhat.com>
Date:   Thu Feb 21 16:42:17 2013 -0800

    tests/fileio.rc: library for file descriptor based IO in tests
    
    There are situations in test scripts where we want to keep open file
    descriptors while performing other commands. Bash has abilities
    to manage file descriptors by numbers, but the syntax is a little
    brain damaging.
    
    This library provides wrappers around it to abstract away bash's
    syntax and also provides a helper function to pick a free file
    descriptor on the fly.
    
    The APIs are pretty self explanatory.
    
    Change-Id: I82f1d1957646dd6c468d9e85c90ec30c978c7ad6
    BUG: 764966
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4565
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 72ad9a3a8b684595dc394252c88c76c859919a45
Author: Anand Avati <avati@redhat.com>
Date:   Thu Feb 21 00:17:26 2013 -0800

    synctask: support for (assymetric) counted barriers
    
    This patch introduces a new set of primitives:
    
      - synctask_barrier_init (stub)
      - synctask_barrier_waitfor (stub, count)
      - synctask_barrier_wake (stub)
    
    Unlike pthread_barrier_t, this barrier has an explicit notion of
    "waiter" and "waker". The "waiter" waits for @count number of
    "wakers" to call synctask_barrier_wake() before returning. The
    wait performed by the waiter via synctask_barrier_waitfor() is
    co-operative in nature and yields the thread for scheduling other
    synctasks in the mean time.
    
    Intended use case:
    
      Eliminate excessive serialization in glusterd and allow for
    concurrent RPC transactions.
    
      Code which are currently in this format:
    
    ---old---
    
      list_for_each_entry (peerinfo, peers, op_peers_list) {
              ...
              GD_SYNCOP (peerinfo->rpc, stub, rpc_cbk, ...);
      }
    
      ...
    
      int rpc_cbk (rpc, stub, ...)
      {
              ...
              __wake (stub);
      }
    
    ---old---
    
      Can be restructred into the format:
    
    ---new---
    
      synctask_barrier_init (stub);
      {
              list_for_each_entry (peerinfo, peers, op_peers_list) {
                      ...
                      rpc_submit (peerinfo->rpc, stub, rpc_cbk, ...);
                      count++;
               }
       }
       synctask_barrier_wait (stub, count);
    
       ...
    
       int rpc_cbk (rpc, stub, ...)
       {
               ...
               synctask_barrier_wake (stub);
       }
    
    ---new---
    
      In the above structure, from the synctask's point of view, the region
    between synctask_barrier_init() and synctask_barrier_wait() are spawning
    off asynchronous "threads" (or RPC) and keep count of how many such
    threads have been spawned. Each of those threads are expected to make
    one call to synctask_barrier_wake(). The call to synctask_barrier_wait()
    makes the synctask thread co-operatively wait/sleep till @count such threads
    call their wake function.
    
      This way, the synctask thread retains the "synchronous" flow in the code,
    yet at the same time allows for asynchronous "threads" to acheive parallelism
    over RPC.
    
    Change-Id: Ie037f99b2d306b71e63e3a56353daec06fb0bf41
    BUG: 913662
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4558
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 1dbe9a05feac5032990457058f7cef686a293973
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Feb 20 14:11:36 2013 -0500

    glusterd: allow multiple instances of glusterd on one machine
    
    This is needed to support automated testing of cluster-communication
    features such as probing and quorum.  In order to use this, you need to
    do the following preparatory steps.
    
    * Copy /var/lib/glusterd to another directory for each virtual host
    
    * Ensure that each virtual host has a different UUID in its glusterd.info
    
    Now you can start each copy of glusterd with the following xlator-options.
    
    * management.transport.socket.bind-address=$ip_address
    
    * management.working-directory=$unique_working_directory
    
    You can use 127.x.y.z addresses for binding without needing to assign
    them to interfaces explicitly.  Note that you must use addresses, not
    names, because of some stuff in the socket code that's not worth fixing
    just for this usage, but after that you can use names in /etc/hosts
    instead.
    
    At this point you can issue CLI commands to a specific glusterd using
    the --remote-host option.  So far probe, volume create/start/stop,
    mount, and basic I/O all seem to work as expected with multiple
    instances.
    
    Change-Id: I1beabb44cff8763d2774bc208b2ffcda27c1a550
    BUG: 913555
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 673287ae4d265f67a445dedb8ace38b06e72dff7
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Feb 21 16:22:38 2013 +0530

    glusterd: use gf_strdup() in place of strdup()
    
    Change-Id: Idee71019dbc6eeaa0a808d671b29d6f3038a1a89
    BUG: 913487
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4562
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 96c61c5512daca3b9f67aec612a53241572fabbf
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Feb 21 18:27:10 2013 +0530

    call-stub: remove fall-through in ftruncate
    
    Change-Id: I58bf6b881ff63d627051bef1ab30bd0337ab65e2
    BUG: 913544
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4564
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4e15a0b4189fe586f66d810d372dffdbeea4d816
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Feb 20 15:26:02 2013 +0530

    syncop: Fixed indentation and whitespaces.
    
    Change-Id: I90e496b5d5027ac702ab3804ba52f26d537812a0
    BUG: 764890
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4554
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e4b504d624f503cce44fbf45d68abfef4cd02d1c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Feb 20 13:27:33 2013 +0530

    testcase for the open-behind xlator when open fails
    
    Test if the fops which are put into a stub and are waiting for
    the open to complete should be unwound with the error if open
    call itself fails.
    
    Change-Id: I8c363d98303a7df1a0ca9ea6ef207c7123fdd388
    BUG: 846240
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4553
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit a50dd81148c6c001bf0902fb60a8ea1450bb5e6f
Author: Anand Avati <avati@redhat.com>
Date:   Tue Feb 19 21:14:23 2013 -0800

    performance/write-behind: guarantee non-overlapping concurrent writes
    
    Maintain a list of writes (either written behind or SYNC) which are
    currently "in progress" (i.e, STACK_WIND'ed towards server) and hold
    off any new STACK_WIND of write (either written behind or SYNC) which
    overlaps with any of the "in progress" writes.
    
    This is a guarantee which AFR's eager-lock depends upon (though not
    strictly a write-behind requirement)
    
    Change-Id: Icedd0b51b440366a906dc9223d62b7fd6ef2ca03
    BUG: 857673
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4551
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>

commit 8271ed2cda0f37ac48f9c691c593615cdec4eae5
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Tue Feb 19 22:56:22 2013 +0530

    cli: Display option 'device vg' only when bd backend enabled
    
    Change-Id: If61c237948f51d48305f4897b3f226eead10bae8
    BUG: 912997
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/4555
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 11be941ccc2857514cf7b65552c84c20e27b99e1
Author: Anand Avati <avati@redhat.com>
Date:   Sun Feb 17 16:36:50 2013 -0800

    read-ahead: re-enable support for variable page size
    
    Support for variable size page-size was disabled with the introduction
    of fixed size iobufs. Since the introduction of variable sized iobufs
    there is no reason to not have configurable page-size in read-ahead.
    
    This patch enables necessary changes in the translator for configurable
    page-size.
    
    Change-Id: I677d70fef50641eb041269aca92a088b9d4961cc
    BUG: 764204
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4526
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>

commit e7fc8a2ca16b397ec69575aa22b179ef47410e46
Author: Anand Avati <avati@redhat.com>
Date:   Fri Feb 15 17:30:56 2013 -0800

    open-behind: propagate errors from ob_wake_cbk
    
    If opening fd in background fails, then remember the error and
    fail all further calls on the fd.
    
    Use the newly introduced call_unwind_error() function from
    call-stub cleanup to fail the future calls.
    
    Change-Id: I3b09b7969c98d915abd56590a2777ce833b81813
    BUG: 846240
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4521
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 01bb20f4aa42f735b72baff72ea770289851b46c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Feb 7 13:50:06 2013 +0530

    glusterd: log changes in volume set and volume reset codepath
    
    Change-Id: Ieed9194768e434e54ea7d3d42b705eb600445cf4
    BUG: 812356
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4543
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bcb423555ac7f0379344de41b50c012c1fde891d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Feb 18 16:41:46 2013 +0530

    glusterd: Added validation function for performance cache max and min size.
    
    Change-Id: I0b8dbc4b65412b8aff24873f030c03e3dcfcb988
    BUG: 782095
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4541
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d0f8b8fb947048fb1017dd1d9fd1ea144fcb6dc0
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Feb 11 11:53:36 2013 +0530

    glusterd: Made gd_synctask_begin less 'monolithic' in terms of LOC.
    
    Change-Id: I2dcaea56c2ca2c2c42c046ab7d2a39d586307868
    BUG: 852147
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4507
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 66ec7fb345441ba6283e68f95410ce3ee9d5554e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Feb 19 15:42:28 2013 +0530

    code cleanup: remove unused parameter 'dict'
    
    Change-Id: Id5c23a0cedf695eb9c25bc793cea3cf0a13f61c4
    BUG: 764890
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4544
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 12d865dd59e70a5dd0701190f116efe8811c088c
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 19 16:05:45 2013 +0530

    dht: Enable mem-accounting for nufa
    
    Change-Id: I0cf8a59c81e30603aadc45393bbd49d80ae1621f
    BUG: 912657
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4542
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5077242f1d17c9cc8f5233333dbdfe2f73e71e44
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Feb 13 18:00:04 2013 +0530

    features/quota: Add option to consider the quota limit in statfs estimation
    
    Adds an option, features.quota-deem-statfs (default off) to consider the
    quota limits while calculating the volume stats.
    
    Eg: Backend is of size 10GB and limit set on / is 5GB. If the option is off
    df show actual size to be 10GB and when it is on df shows 5GB.
    
    Change-Id: Ib30733bb69afecce1dea9d0491af89d551d214cc
    BUG: 905425
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4511
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2c8e3bcb4fc2e587762fc633525eb9c36257adec
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Feb 19 15:35:17 2013 +0530

    Tests: Disable open-behind
    
    Test assumes that open on the mount point opens the files on bricks
    right away.
    Change-Id: I94aae857515792e9b694723d30bb085f9e703745
    BUG: 821056
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4540
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f0bfbbd0f260fe898cd901b0ac0a6a805b33800c
Author: Anand Avati <avati@redhat.com>
Date:   Fri Feb 15 17:14:50 2013 -0800

    call-stub: internal refactor
    
    - re-structure members of call_stub_t with new simpler layout
    - easier to inspect call_stub_t contents in gdb now
    - fix a bunch of double unrefs and double frees in cbk stub
    - change all STACK_UNWIND to STACK_UNWIND_STRICT and thereby fixed
      a lot of bad params
    - implement new API call_unwind_error() which can even be called on
      fop_XXX_stub(), and not necessarily fop_XXX_cbk_stub()
    
    Change-Id: Idf979f14d46256af0afb9658915cc79de157b2d7
    BUG: 846240
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4520
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit f1ce56daf8dff68dc59a7ad4841e428296157011
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Feb 19 12:37:04 2013 +0530

    performance/open-behind: use anonymous fd for doing fstat and readv
    
    Change-Id: I61a3c221e0a15736ab6315e2538c03dac27480a5
    BUG: 846240
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4483
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b371736a58a3c0174fbd8823d51c690ec9d4f7d3
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Feb 19 13:22:25 2013 +0530

    cluster/afr: do complete split-brain check in all the fd based fops
    
    fd based operations such as readv checked only for data split brain
    instead of complete split-brain (i.e both data + metadata) assuming that
    open would have done the complete split-brain check. However open-behind
    would have unwound open, without winding to afr thus preventing the complete
    split-brain check and some appliations will be able to read the contents
    of the file even though the file has metadata split-brain. So let all
    the fd based fops do a defensive check of complete split-brain.
    
    Change-Id: Ia90b35f2b08426dfcad804b7f8105278c86fbd2d
    BUG: 846240
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4548
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fd407a4f5cdb869dc52efe8fc9e1d284f60f5992
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Feb 19 11:42:13 2013 -0500

    glusterfs.spec.in: resync with Fedora glusterfs.spec
    
    remove extraneous pwd and ls, left-overs from debugging regression
    failures
    
    BUG: 819130
    Change-Id: I9bc058bbbfd78218153737751481171f21001e6e
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4547
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit eac54f6f76e6fca4f94028b47d963108f63c8f02
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Feb 18 14:22:07 2013 +0530

    glusterd: Added option description, and validation function fields.
    
    In volopt_map_entry table, added option description field, and
    option validation function pointer.
    
    Change-Id: I21c6bccd175970592b470ce3ef3f418cb99a5a43
    BUG: 903478
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4535
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 81dceec250c9b2f5b87650e28e736e04c4b8597e
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Feb 19 10:55:50 2013 +0530

    tests: Add spaces around '=' in a string comparision in TEST primitive
    
    Change-Id: I0402949c8cd88cc93e073a7c8ae60b5ff4497ad2
    BUG: 764966
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4538
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 59ac567c8b5ebf20b573ecf250e13f841e817dbd
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Feb 18 13:16:39 2013 -0500

    distribute: add hash-name-regex option
    
    This is to support the common "write to temp file then rename" idiom. In our
    case this causes us to create a linkfile during the rename in (N-1)/N cases,
    with a significant impact on performance e.g. for UFO which uses this idiom.
    This patch allows the user to specify up to two regular expressions that
    separate the permanent and transient parts of a temp-file name:
    
        rsync-hash-regex reimplements the existing RSYNC_FRIENDLY_NAME
        pattern where the temporary name for EXAMPLE is .EXAMPLE.suffix
    
        extra-hash-regex can be used for a second pattern, active concurrently,
        and can include alternatives via the POSIX extended-regex syntax
    
    Change-Id: Ic1a6ed19324bc31fefe91ee34b8478877a9c5d2c
    BUG: 912564
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4116
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6ff25bc98193fd39e25acfce8e3b2f3b3d80a9c8
Author: Varun Shastry <vshastry@redhat.com>
Date:   Thu Jan 17 15:35:07 2013 +0530

    libglusterfs: make gf_string2percent_or_bytesize to convert float numbers.
    
    Change-Id: I0ac6588297bdb8b085c3c9b01848a098f7fd4293
    BUG: 912206
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4533
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ef830366a38d9420ad9a5065226b1911125ca8aa
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Feb 14 12:47:54 2013 +0530

    glusterd: Fix check for task-id existence in 'volume status'
    
    This fixes the issue of task-id tests failing randomly. The condition used to
    check rebalance/remove-brick was running was wrong, which could lead to the
    task-id for these tasks to not be displayed even when the actual commit hadn't
    occured.
    
    Change-Id: I765daceda5b6bed1387342c15f9ea00552ac85f5
    BUG: 857330
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4514
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8403f9a2d976c33e01fbd9e4a4b04e8f1e936806
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Feb 18 15:51:35 2013 +0530

    rpc: change dict key for fqdn
    
    changed the key from "client.fqdn", which could be wrongly
    construed as belonging to protocol/client, to "fqdn".
    
    Change-Id: Ib5f4a875a00b99cd903a29da19bafeb70baaab4e
    BUG: 906119
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4536
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e306d08ef10f330c36e6874cf16c7554c6cbc867
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 15 15:34:44 2013 +0530

    glusterd: Changing the volume entry table's representation.
    
    Change-Id: Ifd3a20452cc18ec2604aa97776e705b1998be03c
    BUG: 903478
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4518
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0435bc3a701fd89f3abeb43c80f50444a93bddd2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Feb 15 12:30:52 2013 +0530

    performance/write-behind: mark fd bad if any written behind writes fail.
    
    Change-Id: I515fc26c61e1ea929a3049b3001c58a64f3e6c87
    BUG: 765473
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4515
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6f6789884227b8260f140c39c063d77b0516af97
Author: Anand Avati <avati@redhat.com>
Date:   Sun Feb 17 21:46:47 2013 -0800

    LinuxRPM/Makefile: fix backquote which was triggering recursive make
    
    The following Makefile snippet:
    
    --snip--
    all:
    	@echo "To build RPMS run `make glusterrpms`"
    --snip--
    
    was using `backquotes` in the string, and thereby triggering a nested
    make on "glusterrpms" target implicitly as part of 'make all', thus
    defeating the intention.
    
    So use single quotes instead of backquotes.
    
    It is unexplained why this nested 'make glusterrpms' was not called on
    the build server during regression test.
    
    Change-Id: I8a8d1d4f565d03cfb27341e6183af5b09530eb60
    BUG: 819130
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4532
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1d172d6ee17b7d1e2cf4f4f1585941268cdc1039
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Feb 18 10:12:30 2013 +0530

    cluster/dht: improvement in rebalance logs
    
    provide space between path and next string, so that we can grep
    for the correct path in error logs.
    
    Change-Id: Ide53e341864dce432406a58e8cbb2ff1480cfbde
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815194
    Reviewed-on: http://review.gluster.org/4531
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 84f5e4b354526fbb7f0665345816e81c81245c8f
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jan 30 11:29:54 2013 -0500

    glusterfs.spec.in: resync with Fedora glusterfs.spec
    
    Resync with Fedora's glusterfs.spec, being careful to preserve recent
    additions to the glusterfs.spec.in such as the package-config for -devel
    and the OCF sub-package
    
    To build a set of RPMs:
     % ./autogen.sh
     % ./configure --enable-fusermount
     % make dist
     % cd extras/LinuxRPM && make glusterrpms
    
    Updated rpm.t, hopefully build system has all the dependencies to build UFO
    
    BUG: 819130
    Change-Id: I1b1c161337ad780cf7d3ab401fa1b10648f38cbd
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4454
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6c848529cb26e6e4a5dc9576283207ab72187974
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Feb 16 20:10:24 2013 +0530

    libglusterfs: Fix memory leaks in fd_lk_insert_and_merge
    
    Change-Id: I666664895fdd7c7199797796819e652557a7ac99
    BUG: 834465
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4525
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4741b2682084aaac1179310bd3672fde6f312404
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sun Feb 17 20:29:47 2013 +0530

    mount.glusterfs: Introduce mem-accounting as an option
    
    option mem-accounting enables memory accounting for the client
    process.
    
    re-factored to keep options with values and options without values
    in different sections of mount.glusterfs.
    
    Change-Id: I54ebc31a1eae6d7a5ce7b0255cd7df74d37d46c1
    BUG: 834465
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4524
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc501a57bc595ec1d65fa466cfd7d34f28f2012b
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Sat Feb 16 22:51:10 2013 +0530

    Better mechanism to handle memory accounting
    
    Memory accounting will now be enabled if:
    
    1) Any glusterfs process is spawned with argument --mem-accounting.
    2) DEBUG is defined.
    
    Change-Id: I3345e114127a57ce61916be0e2c4e0049a4c3432
    BUG: 834465
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4523
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fcc230c99dd7318c2bee54beaa152b5a8c66f186
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Feb 7 13:57:42 2013 -0500

    features: add a directory-protection translator
    
    This is useful to find all calls that remove a file from the protected
    directory, including renames and internal calls.  Such calls will cause
    a stack trace to be logged.  There's a filter script to add the needed
    translators, and then the new functionality can be invoked with one of
    the following commands.
    
    	setfattr -n trusted.glusterfs.protect -v log $dir
    	setfattr -n trusted.glusterfs.protect -v reject $dir
    	setfattr -n trusted.glusterfs.protect -v anything_else $dir
    
    The first logs calls, but still allows them.  The second rejects them
    with EPERM.  The third turns off protection for that directory.
    
    Change-Id: Iee4baaf8e837106be2b4099542cb7dcaae40428c
    BUG: 888072
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4496
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 614529c59123d3f2a20a6ee9a99d362a7d35e5b1
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Feb 8 11:44:41 2013 +0530

    rpc: bring in root-squashing behavior in rpc
    
    * requests coming in as root are converted to nfsnobody
    
    * with open-behind some acl checks wont happen and nfsnobody
      can read the file "whose owner is root and other users do not
      have permission to read the file". This is becasue open-behind
      does not send the open to the brick and sends success to the
      application, thus the acl related tests on the file wont happen
      which would have prevented the file from being opened.
    
    Change-Id: I73afbfd904f0beb3a2ebe807b938ac2fecd4976b
    BUG: 887145
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4516
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5b8cb263756a9d2beb5e70dca0b652286c7e6b67
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 17:20:05 2013 +0530

    glusterd: Made volume-heal use synctask framework.
    
    Change-Id: Ic6659335f18a3befcf9b8b3ca067883a2c889d03
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4493
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 86854a544e5bcc05bf6a57b7b622c48ddafc79b5
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 17:31:11 2013 +0530

    glusterd: Made volume-quota use synctask framework.
    
    Change-Id: I4c275253144ed3ac11a701a56dd1116c002471ba
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4495
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 99fe09f4fa805ea23848c1ec56088ec1435e9015
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 15 13:04:57 2013 +0530

    glusterd: Moved the volume entry table to a separate file.
    
    Change-Id: I893f41bd505fc0e02aec1e71f7a6209759b24a89
    BUG: 903478
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4517
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee352d032db8dce47535889a54e574bf6d511225
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Feb 11 17:54:32 2013 +0530

    glusterfsd: Remove 'top {read,write}-perf' thread
    
    'volume top {read,write}-perf' were performed in a different thread on the brick
    process, to prevent them from blocking the main polling thread. This was
    essential earlier when the rpc actor functions were run in the epoll thread. Now
    rpc actors can be launched on their own threads with the introduction of
    synctask support for rpcsvc. The brick-op actors are now launched using this
    feature, which makes the need for '{read,write}-perf' to be performed in a new
    thread.
    
    Change-Id: Idad7ab623f0bfb0c3a5cfae796c06e0fa3cff1b9
    BUG: 764890
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4510
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c87472e200c9fee74705a350ce45557bde47b946
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Feb 14 13:04:58 2013 +0530

    cluster/distribute: Reopen fds in migration internally as root:root
    
    Though linkfile_create and rebalance dst file create sent a setattr
    with correct ownership, there is still a race window where the linkfile
    open (client open due to migration) will fail, as its ownership will be
    root:root.
    
    Change-Id: I056092da6102319efa3bb9f1795f8c97db2a3fed
    BUG: 884597
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4513
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5d29e598665456b2b7250fdca14de7409098877a
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Feb 13 13:03:10 2013 +0530

    cluster/distribute: Remove suprious fd_unref call
    
    After fix http://review.gluster.org/4282 (libglusterfsterfs/syncop: do not
    hold ref on the fd in cbk) was pushed, syncop_open does not take a ref anymore.
    
    Change-Id: I5543986a4f2d965eef42ca979b39ac75439cec49
    BUG: 910661
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4509
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4443a5cde640fa612ba9537a662268d889c8c3df
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Tue Feb 12 13:10:40 2013 +0530

    fuse: Change "gid-timeout" default value to 2
    
    Originally default value was 0. Changed to 2 for
    performance benefits.
    
    Change-Id: Iaadc59cf3ef2a2eb42ff2f6624f466a544fc8074
    BUG: 902348
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4506
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7f2ebe378b9c0fdcfca92cb785a141bb1d5c43d4
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Feb 6 17:04:37 2013 +0530

    glusterd: Made log-rotate use synctask framework.
    
    Change-Id: Ib305168759db6730dfa0045da99de252eb5e9469
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4478
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a42490385d91831e83941d6999dd297d89e02027
Author: shishir gowda <sgowda@redhat.com>
Date:   Mon Feb 11 22:27:29 2013 +0530

    cluster/dht: Create linkfile with file uid/gid
    
    Currently, linkfile creation happens as root.
    
    use uid/gid returned from _cbk (link/rename) to set the correct ownership of
    the link files.
    
    Also added test/dht.rc to implement common dht functions
    
    Change-Id: Iecdcf52d89fed8286670ce430b9d19deebd27b8c
    BUG: 884597
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4304
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1ffb2558fb4bb896883ad71497bac0cc13df4f18
Author: Anand Avati <avati@redhat.com>
Date:   Tue Dec 4 22:35:58 2012 -0800

    synctask: implement setuid-like SYNCTASK_SETID()
    
    synctasks can now call SYNCTASK_SETID(uid,gid) to set the effective
    uid/gid of the frame with which the FOP will be performed.
    
    Once called, the uid/gid is set either till the end of the synctask
    or till the next call of SYNCTASK_SETID()
    
    Change-Id: I7eb74f7c473099bcae39310d2ab353d58f8eb2ba
    BUG: 884597
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4269
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>

commit 311a5df884c0d2320dd43191e6e6ba0a033eb683
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Sat Feb 9 04:37:28 2013 +0530

    object-storage: Use the wrapper functions provided by fs_utils.py to make
      system calls.
    
     The set of changes:
     * Unit test cases for fs_utils.py
    
     * Replaced os.path with os_path
    
     * Implemented wrapper functions do_write, do_chmod, etc in fs_utils.py
    
     * Replaced os.<sys-call> with the wrapper functions.
    
    Change-Id: I770da878e83eda6b98e49d70193990406a2642a7
    BUG: 887301
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4360
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3b19a14b86f753a0465a11a89eaabf3e19f42eca
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Mon Feb 11 11:27:40 2013 +0530

    Debug/io-stats: Enable INFO level in syslog
    
    Previously we had only ERROR, WARNING and CRITICAL
    levels allowed in syslog. Adding INFO level as per
    user request.
    
    Change-Id: I3276d62d12ebf4be68edf5e5b26341dc2bb4f47b
    BUG: 887924
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4499
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 30dd16a44cfc34aaddc6532308ebec285eb825c2
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 22 16:19:06 2013 +0530

    Tests: Remove 'sleep' from the test case
    
    Change-Id: Iaff2076b0ef7f69a6ba6efd4123271bde490977a
    BUG: 873962
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4498
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4e05a9c64b2a59cc0ff090082ab268463ba8b450
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Feb 9 07:06:18 2013 +0530

    Tests: Explicitly set eager-lock on
    
    Change-Id: I834fd5adab6e328ed106e413fc06e4280d1d24b2
    BUG: 888174
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4497
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7c0d35b2e7e234084d0414b3cf1e09969a43a677
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Dec 27 15:57:13 2012 +0530

    glusterd: harden 'volume start' staging to check for brick dirs' presence
    
    PROBLEM:
    
    When the brick directory of a volume is absent on any of the servers,
    AND an attempt is made to start the volume, commit fails ONLY on the
    node where the brick dir is absent, leading to a split-brain like
    situation.
    
    FIX:
    
    Harden 'volume start' to check for the presence of brick directories
    at the time of staging, thereby preventing commit failure.
    
    Change-Id: I67faeb9afbd3aa76f08645924462db126bf7a977
    BUG: 889996
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4365
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 19de18219b93097ede8d14c218011a873ebd50ed
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Sep 18 12:41:46 2012 +0530

    cluster/dht: pathinfo xattr changes for directories
    
    Since directories have presence on all subvolumes there is
    no definite meaning of ->hashed_subvol or ->cached_subvol.
    getxattr() code path chooses ->cached_subvol for pathinfo
    extended attribute. While this makes sense of files, it makes
    less sense for directories. Further if a hashed or a cached
    subvolume is down, and there's a getxattr request for a
    directory, we return with an errno.
    
    This patch changes pathinfo extended attribute contents by
    aggregating information from all subvolumes that are up.
    
    Change-Id: I58adb741d63ccfd1d0239af75eb65f26f0fb384d
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    BUG: 856455
    Reviewed-on: http://review.gluster.org/4047
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 13b92b4f418cc8e34da95a31c583411bae595f4e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jan 30 15:23:48 2013 +0530

    glusterd: Made gsync set use synctask framework
    
    Change-Id: I409fa5a9f55434ece47a8a51d4812d3eca42d269
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4473
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bbd6fb6e98f414719fc0a63c7de03d360154aa21
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Mon Feb 4 16:10:57 2013 +0530

    glusterd: Making volume-reset use synctask framework
    
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Change-Id: Ib25c8fa69d84b8132505ae3f1e67cf88d3f6f9ec
    BUG: 852147
    Reviewed-on: http://review.gluster.org/4474
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4a28ab092da134cb44888aee7efa290d9b81c87d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 16:37:58 2013 +0530

    glusterd : Made volume-set use synctask framework.
    
    Change-Id: I1aa08ca843b87839180f9097bca370270a856e6d
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4488
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fcf004a16cf7800c114fa3495dbc4ca5c0cc12f9
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Feb 8 15:03:46 2013 +0530

    tests/bugs/bug-762989.t: do not check the listening ports
    
    Change-Id: Ifbcf28bb476ee95343beaf42fb84a1b834c9ffcb
    BUG: 762989
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4486
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 78f6c48d960df65487f48e09af81feb55879e9b5
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 16:46:14 2013 +0530

    glusterd: Made volume-sync use synctask framework.
    
    Change-Id: I048aac2af4d9da9ed541d3756fefefbb2a29198e
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4489
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e289d3db5f448695bee004da99290346fa787093
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 16:59:21 2013 +0530

    glusterd : Made volume clear-locks use synctask framework.
    
    Change-Id: Ia1fe3d0500d999c1f95b43c9e53947834e39d680
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4490
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e4187ac41346a3dbb97f29cd99fbf56e0a2586ef
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 17:12:05 2013 +0530

    glusterd: Made volume-stop use synctask framework.
    
    Change-Id: I88270f70538bb89d828bb51830b54e9f59be258a
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4491
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 93f987daef56fd4062613f56cf365daf491b022e
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 17:17:04 2013 +0530

    glusterd: Made volume-delete use synctask framework.
    
    Change-Id: I52573bb49946f904484e2ead483e8f6f41cbd0c8
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4492
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 83a0868a16ace8d9a86490f189f35f1f332cdebd
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Feb 8 17:22:22 2013 +0530

    glusterd: Made volume-statedump use synctask framework.
    
    Change-Id: I230ecbd8978725070b5910ead4249f21038224a6
    BUG: 852147
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4494
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bbf7345adccec7cbcb0a14deca0d499987c5829d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Feb 8 13:05:39 2013 +0530

    Tests: Fixes to state-dump gen function
    
    Change-Id: I426e04a4e3d402639a052c6b3616157c36fefc56
    BUG: 908146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4484
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bda72009430ed76dc00433346b33be25c2fe2566
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Thu Aug 30 11:37:24 2012 +0200

    fuse: log options passed to fuse when mount fails
    
    This is done to ease debugging.
    
    Change-Id: I50cfca297e03f41cc47819d0700752e3d24a07d6
    BUG: 852754
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/3877
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 83c84028552d41ec0914a0c5db97e6557d9fe039
Author: Joe Julian <me@joejulian.name>
Date:   Fri Nov 30 14:17:31 2012 -0800

    gsyncd: allow the override of the compiled-in python path
    
    .. using the environment variable $PYTHON
    
    Change-Id: Ieaad8be98b826c803268216826e250d9944c8190
    BUG: 882127
    Signed-off-by: Joe Julian <me@joejulian.name>
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4252
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9869c0f86675d7bf44ecfc246185e4a5fff21c63
Author: merfi <lahoucine@benlahmr.com>
Date:   Sat Sep 1 20:34:09 2012 +0200

    glusterfsd can't listen in a specified address
    
    When specifying transport.socket.bind-address option,
    only the glusterd daemon uses this address. But glusterfsd
    still working with the default localhost address. For
    instance, when we want to use an IPV6 specific  address we
    will want that all process use that specified address even
    glusterfsd.
    
    To handle this change we just need to replace the fixed
    address “localhost” to the specified brick address
    “brickinfo->hostname”
    
    Change-Id: I540d30e6c155f71379a1cf1c0b459ac00faeb62c
    BUG: 865327
    Signed-off-by: Lahoucine BENLAHMR <lahoucine@benlahmr.com>
    Reviewed-on: http://review.gluster.org/3889
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 779004dbcd79e34a0c7ce73f574419b40ccade27
Author: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
Date:   Mon Sep 24 10:48:35 2012 +0200

    Respect autotools docdir variable
    
    Change-Id: If20d0806a925b880e0ba9bbc66604cae6c51ce6b
    BUG: 859861
    Signed-off-by: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
    Reviewed-on: http://review.gluster.org/3971
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d3e7881ecdba2124115de6666e48f34ce267d30d
Author: Anand Avati <avati@redhat.com>
Date:   Thu Feb 7 14:25:03 2013 -0800

    Use proper libtool option -avoid-version instead of bogus -avoidversion
    
    Change-Id: I1c9541058c7d07786539a3266ca125a6a15287d8
    BUG: 859835
    Signed-off-by: Anand Avati <avati@redhat.com>
    Original-author: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
    Signed-off-by: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
    Reviewed-on: http://review.gluster.org/3967
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 08d63afa1b26e4f42ab1b85a14e6bfc3836de28e
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jun 14 16:25:09 2012 -0400

    Add scripts for size-weighted rebalance.
    
    Change-Id: I04197e54fef2ff7b61fbee21ab837219354184f1
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/3573
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6a6ec980421a115a379aed97364817c16ce7b378
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Jan 23 10:03:07 2013 +0530

    object-storage: Store the lock file in /var/run/swift.
    
    * Openstack swift uses the /var/run/swift directory to store the pid files
      for all the servers.
    
    * Also, added a script that would unmount the gluster client on a volume stop.
    
    Change-Id: Ib5b9a2964987ca7696d9a2570f1f7af8490b2168
    BUG: 861497
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4417
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dc2da4a3d9629fe3249fe540e22748527ce05483
Author: Anand Avati <avati@redhat.com>
Date:   Wed Feb 6 09:03:03 2013 -0800

    afr: serialize modification of {entrylk,inodelk}_lock_count
    
    Typically this lock was not needed in practice, but with
    http://review.gluster.org/3842, this code gets executed in multiple
    threads for different servers and we lose a count. This results in
    leaked lock and a hang for a future transaction.
    
    Change-Id: I377ed20e44f2a45cff522289dfef181f0653eca2
    BUG: 765564
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4480
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 78ae7215614a7717d2cf838afefb1525fbb70602
Author: Anand Avati <avati@redhat.com>
Date:   Tue Feb 5 16:04:50 2013 -0800

    fuse-bridge: use READDIRPLUS support when available
    
    This patch makes use of READDIRPLUS call when support is available
    in the kernel.
    
    Change-Id: Iac78881179567856b55af1f46594a2b2859309f0
    BUG: 908128
    Signed-off-by: Anand V. Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3905
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit da9d54cac629d9c0f7ae6b431abfb134b5f0eca3
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Feb 5 19:19:06 2013 -0500

    dht: better layout-optimization algorithm
    
    This method deals with the case where swapping might gain a bigger overlap
    for the xlator currently under consideration, but sacrifices even more from
    the xlator we're swapping with. For example:
    
    A = 0x00000000 - 0x44444443 (new 0x00000000 - 0x55555554)
    B = 0x44444444 - 0x77777776 (new 0x55555555 - 0xaaaaaaa9)
    C = 0x77777777 - 0xffffffff (new 0xaaaaaaaa - 0xffffffff)
    
    Here, the new range for B has a bigger overlap with the old C than with the
    old B (0x33333333 vs. 0x22222222 to be precise) so looking only at that
    might lead us to swap. However, such a swap turns the new C's overlap from
    0x55555556 (vs. old C) to *zero* (vs. old B).  In other words, we've gained
    0x11111111 for B but lost 0x55555556 for C, so it's a bad idea.
    
    The new algorithm accounts for all effects of the swap, so it not only avoids
    bad swaps but can make some good ones that would have been missed previously.
    For example, if swapping a range X with a later range Y would not increase the
    overlap for X we would previously have skipped it even if the swap would
    increase Y's overlap without affecting X's.  This is the normal case when we're
    adding a new brick (which initially has zero overlap with any old range) so
    finding more good swaps is probably even more important than avoiding bad ones.
    
    Also, the logic in dht_overlap_calc was completely broken before, causing
    integer overflows instead of providing correct values, so no matter what
    higher-level algorithm was in place the GIGO effect would have resulted in
    bad decisions.
    
    Change-Id: If61ed513cfcb931916c6b51da293e3efbaaf385f
    BUG: 853258
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/3908
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7a9e27073789bdc0164cc6428aee5088a8faa2fb
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Nov 19 17:21:49 2012 +0530

    glusterd: synctaskize 'volume create' operation
    
    .. and also move brickpath validation to volume create stage
    
    Change-Id: Ia028677932ca5f6aa05dcf624f47033b62e7b212
    BUG: 862834
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4213
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0b7cdbf50dea9ee77bc8f71526a1566945672c19
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Jan 28 18:16:32 2013 +0530

    rpc: get hostnames of client to allow FQDN based authentication
    
    If FQDNs are used to authenticate clients, then from
    this commit forth, the client ip(v4,6) is reverse looked up
    using getnameinfo to get a hostname associated with it,
    if any, thereby making FQDN-based rpc authentication possible.
    
    Change-Id: I4c5241e7079a2560de79ca15f611e65c0b858f9b
    BUG: 903553
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4439
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2197c8b41423a7a9a5e55db0d3a5a27131966e72
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Feb 5 16:52:16 2013 +0530

    nfs/nlm: use req's uid and gid for open_and_resume
    
    Previously, NLM was setting the frame->root->{uid,gid}
    to root by default. This causes permission problems with
    root squashing for lock calls. Now, we obtain the uid and
    gid from rpc request. And duplicate #defines are removed
    from rpcsvc.h
    
    Change-Id: I5d6c87aed8d04aab2619bb913408048c0a02d1e7
    BUG: 906884
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4466
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 45c04e107c365d29ca9872b5e2d12c932bf43a24
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jan 21 16:37:43 2013 -0800

    open-behind: translator to perform open calls in background
    
    This is functionality peeled out of quick-read into a separate
    translator.
    
    Fops which modify the file (where it is required to perform the
    operation on the true fd) will trigger and wait for the backend
    open to succeed and use that fd.
    
    Fops like fstat() readv() etc. will use anonymous FD (configurable)
    when original fd is unopened at the backend.
    
    Change-Id: Id9847fdbfdc82c1c8e956339156b6572539c1876
    BUG: 846240
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4406
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c2953ea34c92f640cecf0f6575aa1acbdc5205b4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Feb 6 17:01:10 2013 +0530

    rpcsvc/dump: return correct return value
    
    fix e8d09b9ab9 resulted in rpcsvc_dump returning large non-zero
    values to caller in case of success. This patch fixes that issue
    by returning 0
    
    Change-Id: I594703dada74da17b33c98b073627a3378d170c5
    BUG: 903113
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4477
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6b292ff33fd842c77cd076e67b7f042d9f0cbedf
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Oct 15 11:09:18 2012 +0530

    libglusterfs/core: dump frame and callstack creation times in statedump
    
    Change-Id: I3772602ac264cbca490d77a0343038297faee7df
    BUG: 844688
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4087
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d831290debf7cc5741c30233d05aa18c9a59e99e
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jan 21 12:49:44 2013 +0530

    glusterd: Use client-op-versions during "volume set"
    
    The supported op-versions of the client and the name of the requested volume,
    are saved during server_getspec(). These are used during the staging of volume
    set. If the option being set is not supported by any of the clients which
    currently have the volume mounted, then set will fail.
    
    Change-Id: I4e6b60b274d5200508762dc0204cfa848a6c0aa4
    BUG: 907311
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4424
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 02d653931c8967accf766014efce0c2dce340cdf
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Nov 28 16:22:15 2012 +0530

    glusterd,glusterfsd,libgfapi: Client op-version
    
    This patch introduces op-version support for glusterfs clients.
    Now, a client sends its supported op-versions during the volfile fetch request
    and glusterd will return the volfile only if the client can support the current
    op-version of the cluster.
    
    Change-Id: Iab1f1f1706802962bcf27058657c44e8a344d2f6
    BUG: 907311
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4247
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 242c12bf602acc3cdb4517cd1b6b06d5099fee0f
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 6 08:39:59 2013 +0530

    tests: Test the open-fd count for a file on brick
    
    Change-Id: I59bc4974eff93e92c4f7041d3722ac60e88b0734
    BUG: 908146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4471
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2dbc9a53a1a8149f6a4fdcfd1be4a632f65d6e83
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 6 08:39:41 2013 +0530

    tests: Added function to generate brick statedump
    
    Change-Id: I5f394a028a3251ec673c8787b2c67691a8b57449
    BUG: 908146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4470
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 55feb734c757cdf64e356afb7b6e36f98f4b5c19
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 6 07:12:40 2013 +0530

    storage/posix: Fix open-fd-count virtual xattr
    
    Send open-fd-count maintained in inode.
    
    Change-Id: I23db5d052bdeb4f67978ff618ed5a0bed7d1592d
    BUG: 908146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4469
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee1472336c3e0747eef53b826985b51696d697ae
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 6 07:04:10 2013 +0530

    libglusterfs: Maintain open-fd-count in inode.
    
    Change-Id: I643d02959f92e40f68a53baf165753ed20f8b3e0
    BUG: 908146
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4468
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3a141cda38cd6908dc3f1103a02eb38007552e87
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 6 12:34:17 2013 +0530

    cluster/afr: Avoid priv->eager_lock value update race
    
    Change-Id: I7049c0c64e36a9dfa4cc0e0b34de7ec111d2f6c1
    BUG: 908302
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4076
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e0a331c4bea8713a67a0f8c5dc4bac1e6f81f358
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Feb 6 12:26:08 2013 +0530

    cluster/afr: Perform wakeup just before fop
    
    There is no necessity for the delayed-post-op to wait until
    the next fop phase on the fd completes. Change-log,
    locks are inherited by the time next fop phase is attempted
    so the wakeup can happen just before the fop phase is started.
    
    Change-Id: I0b8e591f591b0f7565eb55265ab51f476ed2b165
    BUG: 908302
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4073
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 765fdd0809afb1bdac49fae2a0a58ae092e5cde3
Author: Anand Avati <avati@redhat.com>
Date:   Tue Feb 5 17:03:38 2013 -0800

    fuse(efence): zero sized memory was being allocated.
    
    For the last call of getdents(), gf_malloc called with 0 size, which is then
    caught by efence.
    
    BUG: 782760
    Change-Id: If289029117a62ecfcecc70480e5ac8f0e050487d
    Signed-off-by: Anand Avati <avati@redhat.com>
    Original-author: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3846
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit e8d09b9ab9a93367a7135fc6b0e721c9d13e0e2d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Dec 18 14:43:27 2012 +0530

    rpcsvc: Fix memory corruption caused by rpcsvc_dump returning non-zero
    
    The convention followed is that any actor should return non-zero
    value only if it has not attempted to send the reply back. If an
    actor returns non-zero, rpcsvc_handle_rpc_call tries to send an
    error reply. Since, rpcsvc_submit_generic frees the rpc_req, its wrong
    to invoke it more than once on same rpc_req. When the transport is not
    connected, rpcsvc_dump used to pass the non-zero value it got from
     transport to rpcsvc resulting in memory corruption. Hence this patch
    makes rpcsvc_dump to return 0.
    
    Change-Id: I1b6f28969ee546c44d193d3d33debccb65585b69
    BUG: 903113
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4183
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 6763272e7f3fbe8afba948a8afb075b9cf2a5ca7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Feb 4 14:15:24 2013 +0530

    protocol/client: Avoid double free of frame
    
    When client_submit_request fails it calls cbk. The cleanups should
    happen only in cbk. The code committed as part of
    http://review.gluster.org/4357 violates this. Also found that
    clnt_release_reopen_fd violates this as well.
    This patch fixes these issue.
    
    Change-Id: Ic02ba278724b03c65c00b686c39fd7846122618a
    BUG: 821056
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 42a3cc275c819ee0929c371a33779a51d32eda3f
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Feb 4 17:38:16 2013 +0530

    glusterd: remove extra call to glusterd_volume_compute_cksum()
    
    In the commit phase of volume create, checksum on volinfo is
    computed twice - once in the call to glusterd_store_volinfo() and once,
    further down, in the same function glusterd_op_create_volume().
    
    Change-Id: I36f9426943cd48937d4946b4b4ef09f19f31d888
    BUG: 812356
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4463
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5165114025ca5d0ddea8ac6f04bc9d5527e762ef
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Jan 16 11:19:52 2013 +0530

    glusterd: log changes in volume create and delete codepath
    
    Making log changes involving two commands as they both share sections
    of code (like the part where the volume metadata is cleaned up in vol
    delete in case of success; and in vol create in case of failure).
    
    * Most of the changes are of the 's/THIS/this' kind.
    
    * Changed some of the log messages to give as much information as
      available in case of failure.
    
    * Changed log levels in some of the log messages.
    
    Change-Id: I10242511fe9400a07ab04717464d748d9172dd85
    BUG: 812356
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4462
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 06c4ba589102bf92c58cd9fba5c60064bc7a504e
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Mon Feb 4 10:17:01 2013 +0530

    group-virt: Change profile to include remote-dio and exclude posix-aio.
    
    remote-dio enables filtering O_DIRECT in the client xlator. This has been
    found to be useful for improving performance when there are multiple VMs
    talking to an image store.
    
    Aggregated throughput results for a single thread iozone run from multiple VMs
    and a single host can be seen below:
    
    -------------------------------------------------
    No. of VMs |   remote-dio on  |   remote-dio off |
    -------------------------------------------------
           2   |     400 MB/s     |    202 MB/s      |
           4   |     650 MB/s     |    410 MB/s      |
    --------------------------------------------------
    
    posix-aio has not been found to improve performance consistently with VM image
    workload. Hence not including that in the default virt profile.
    
    Change-Id: I592f68b95a955036f1a985352d2f4950ced1deef
    BUG: 907301
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4460
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 1c430d2747f2c0960dcdcd9da4b253c89674bdd7
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Feb 4 13:51:16 2013 +0530

    glusterd: "volume heal info" doesn't report output properly
    
    Problem: "volume heal info" doesn't reports files to be healed when gluster*
             processes on one of the storage node is not running
    
    Change-Id: Iff7d41407014624e4da9b70d710039ac14b48291
    BUG: 880898
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4371
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3804a3413daf7180da0f3fe9d5ea1c5c157d38cb
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jan 22 11:42:10 2013 +0530

    geo-rep / gsyncd: Separate log file directory for Mountbroker sessions
    
    ... so that a mountbroker session which is initiated b/w master
    and slave does not use the same log file if it's started after
    a normal geo-rep session b/w master and slave. This results in
    EPERM as the log file is owned by root and the geo-rep slave
    process (now running as a non privileged user) does not have
    access to it.
    
    Also, having separate log file directory for mountbroker sessions
    looks clean.
    
    NOTE: geo-rep's client mount log file location remains unchanged.
    
    Change-Id: Ic7a732e250aee5393b9c3f6ebf6dfe2c310b7fe4
    BUG: 893960
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4407
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c6116f744fe4791a8fa54778840316275e473587
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Jan 23 14:11:44 2013 +0530

    glusterd: Indexed node information in dict to retain consistency.
    
    Problem:
    --------
    Depending on the response time from different nodes, the response
    dict for rebalance status was populated in  a FIFO manner, and
    hence the output for the CLI was never consistent.
    
    Fix:
    ----
    Irrespective of the response time of the nodes, we now index the
    entries in the response dict for rebalance status, in reference
    to the peerlist. So, the order of the entries and hence the CLI
    output is always consistent.
    
    Change-Id: Ica7e89e5d95aa9860a6f3c7eff58ca2052e05bd6
    BUG: 888390
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4416
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 99c86cc5aefab052c924b2ff31197d02602da4f1
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Feb 4 12:04:04 2013 +0530

    tests: Made changes to verify if any of the bricks crashed
    
    Change-Id: I9da3b8a490159b1090a803b74d0058be0d884c94
    BUG: 905864
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4461
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 189eaecf61091145389142b961a1c9f190299f60
Author: Peter Portante <peter.portante@redhat.com>
Date:   Sat Jan 12 22:39:24 2013 -0500

    object-storage: yield during directory tree walks
    
    Have the co-routine (greenlet) yield during long running directory
    tree walks to avoid starving out other greenlets that might be
    available to run.
    
    A directory walk involves statting every file in the tree to get it
    size. For large numbers of files, this can get expensive. So we yield
    after every stat call, and after processing every directory.
    
    Change-Id: I07f1dfeef6a09b5817e0c237ecc748c491d52a31
    BUG: 894674
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4380
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Mohammed Junaid <junaid@redhat.com>

commit 2a46c8769bc2b6ad491a305ea1d38023d0e22617
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Thu Jan 24 11:26:37 2013 +0530

    cluster/dht: Correct min_free_disk behaviour
    
    Problem:
    Files were being created in subvol which had less than
    min_free_disk available even in the cases where other
    subvols with more space were available.
    
    Solution:
    Changed the logic to look for subvol which has more
    space available.
    In cases where all the subvols have lesser than
    Min_free_disk available , the one with max space and
    atleast one inode is available.
    
    Known Issue: Cannot ensure that first file that is
    created right after min-free-value is crossed on a
    brick will get created in other brick because disk
    usage stat takes some time to update in glusterprocess.
    Will fix that as part of another bug.
    
    Change-Id: If3ae0bf5a44f8739ce35b3ee3f191009ddd44455
    BUG: 858488
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4420
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 50f0882051dff81882115bf72abb67577099944f
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Dec 17 11:20:31 2012 +0530

    cluster/stripe: Mount issues with Stripe xlator
    
    Problem:
    * 'CONNECTING' is taken as CHILD_UP.
    * Sending notifications (default_notify()) for all the events individually
       while mounting.
    
    Solution:
    * Consider Child up only after the event CHILD_UP is received.
    * Send a single notification for all the children's events only
       while mounting.
    
    Change-Id: I1b7de127e12f5bfb8f80702dbdce02019e138bc8
    BUG: 885072
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4356
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 212ab59c511e13cc470e623061fcf113456841c8
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jan 22 14:09:25 2013 +0530

     protocol/server: upon server_connection_put, set xl_private of the transport to
     NULL
    
     Suppose the get_xlator_by_name returns NULL and the connection is put back
     then update the xl_private of the transport by setting to NULL. Otherwise
     server_connection_put would have freed the connection object and xl_private
     of the transport would still be pointing to the same location which is
     freed, thus leading to a segfault when the location is accessed.
    
    Change-Id: Id47e0edde3073b09765338c730847ba3095df9e2
    BUG: 901457
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4411
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4840090c8bf9f08d6da8a4101e2095c6295cf039
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jan 24 16:05:36 2013 +0530

    performance/write-behind: do not try to take LOCK in forget
    
    LOCK attempt in wb_forget is unnecessary
    
    Change-Id: Ibdedc23d0c829c34aedd6fc5bc0e0a584b832514
    BUG: 903566
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4423
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9708bd1f922ca38973cba65b4890c67c2edc6e2b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Oct 22 15:30:49 2012 +0530

    glusterd: do dict unref after sending reply to cli
    
    This patch channelizes dict unrefs of dictionaries created from the cli
    req during volume ops to one common function - glusterd_to_cli() - which
    is guaranteed to be called irrespective of whether the command succeeds
    or fails.
    
    This patch also removes extra unrefs at a few places.
    
    Change-Id: Ic8ba7166387b5dfd1f5ae860539e1b7093a94662
    BUG: 861044
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4003
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6b262d20940b088a1d72ad5518cc4908a7316b5a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jan 31 10:29:20 2013 +0530

    locks: Protected racy (read) access of ext_list
    
    Change-Id: Ibf639695ebd99c11c6960c9be82c0cee71b50744
    BUG: 905864
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4458
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 67d0e72b16104911fef1cebb0b7a1b24d683e899
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat Feb 2 00:14:28 2013 +0530

    mount.glusterfs: Fixed regexp matcher for existing mount points
    
    Change-Id: I58d237a3d2f4caa7f3865c2e4899c472f7457450
    BUG: 906887
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4457
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 80d08f13b0fd6ee0d10f0569165982913339607d
Author: Anand Avati <avati@redhat.com>
Date:   Sat Feb 2 18:59:10 2013 -0800

    cluster/dht: ignore EEXIST error in mkdir to avoid GFID mismatch
    
    In dht_mkdir_cbk, EEXIST error is treated like a true error. Because
    of this the following sequence of events can happen, eventually
    resulting in GFID mismatch and (and possibly leaked locks and hang,
    in the presence of replicate.)
    
    The issue exists when many clients concurrently attempt creation of
    directory and subdirectory (e.g mkdir -p /mnt/gluster/dir1/subdir)
    
    0. First mkdir happens by one client on the hashed subvolume. Only
       one client wins the race. Others racing mkdirs get EEXIST. Yet
       other "laggers" in the race encounter the just-created directory
       in lookup() on the hash dir.
    
    1. At least one "lagger" lookup() notices that there are missing
       directories on other subvolumes (which the "winner" mkdir is yet
       to create), and starts off self-heal of the directory.
    
    2. At least on some subvolumes, self-heal's mkdir wins the race
       against the "winner" mkdir and creates the directory first. This
       causes the "winner" mkdir to experience EEXIST error on those
       subvolumes.
    
    3. On other subvolumes where "winner" mkdir won the race, self-heal
       experiences EEXIST error, but self-heal is properly translating
       that into a success (but mkdir code path is not -- which is the
       bug.)
    
    4. Both mkdir and self-heal assign hash layouts to the just created
       directory. But self-heal distributes hash range across N (total)
       subvolumes, whereas mkdir distributes hash range across N - M
       (where M is the number of subvolumes where mkdir lost the race).
       Both the clients "cache" their respective layouts in the near
       future for all future creates inside them (evidence in logs)
    
    5. During the creation of the subdirectory, two clients race again.
       Ideally winner performs mkdir() on the hashed subvolume and proceeds
       to create other dirs, loser experiences EEXIST error on the hashed
       subvolume and backs off. But in this case, because the two clients
       have different layout views of the parent directory (because of
       different hash splits and assignements), the hashed subvolumes for
       the new directory can end up being different. Therefore, both clients
       now win the race (they were never fighting against each other on a
       common server), assigning different GFIDs to the directory on their
       respective (different) subvolumes. Some of the remaining subvolumes
       get GFID1, others GFID2.
    
    Conclusion/Fix:
       Making mkdir translate EEXIST error as success (just the way self-heal
       is already rightly doing) will bring back truth to the design claim
       that concurrent mkdir/self-heals perform deterministic + idempotent
       operations. This will prevent the differing "hash views" by different
       clients and thereby also avoid GFID mismatch by forcing all clients
       to have a "fair race", because the hashed subvolume for all will be
       the same (and thereby avoiding leaked locks and hangs.)
    
    Change-Id: I84592fb9b8a3f739a07e2afb23b33758a0a9a157
    BUG: 907072
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4459
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 34d8edf58ac0379d7495e57c9a846cdec3794b0d
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Tue Jan 29 09:55:26 2013 +0530

    gfapi: Mark fs->init status done in glfs_init_done for the case of glfs_init_async.
    
    This seen when we call glfs_init_async. The glfs_init_done function,
    calls the call-back function without assigning 1 to fs->init. The problem
    occurs when we call glfs_read or a similar api next time which checks if
    fs->init is 1 and will enter into an infinite wait if it is zero.
    
    Change-Id: I34a3d1652c80e737f5b05082a3fbb6e5978b14cd
    BUG: 839950
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4445
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 26d9d2bd27dd9e6ed9a77789afea0944032223d8
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jan 31 14:23:36 2013 -0500

    socket: restructure disconnect/poll-thread interactions
    
    Change-Id: I792c28f52068e4ed666069b740739662685160bc
    BUG: 906401
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4456
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 77f86aae037ddbe581aea9829c4f541de47a35d6
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jan 31 15:30:42 2013 -0500

    glusterd: identify local address by searching network interfaces.
    
    using bind(3) to identify local address fails when net.ipv4.ip_nonlocal_bind
    (i.e, /proc/sys/net/ipv4/ip_nonlocal_bind) is set to 1.
    
    Change-Id: I7047b6fb94ef0df10b78673fab34dbd169344fec
    BUG: 890587
    Original-author: JulesWang <w.jq0722@gmail.com>
    Signed-off-by: JulesWang <w.jq0722@gmail.com>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4437
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit b070c7be6f687e197260a764abe4357d419b205c
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Dec 12 15:11:35 2012 +0530

    glusterd: Made volume-status use synctask framework
    
    Change-Id: Id4062799104e5831467ced65a43bfe377b6163f4
    BUG: 852147
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4297
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2d0da44826d4b4652169604785ec63cce805bddd
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Dec 12 15:07:38 2012 +0530

    glusterd: Added syncop version of BRICK_OP
    
    - Made rsp dict available to all glusterd's STAGE/BRICK/COMMIT OP.
    
    Change-Id: I5d825d0670d0f1aa8a0603f2307b3600ff6ccfe4
    BUG: 852147
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4296
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 533151abab90afa833f50798f6a8c8db1586f914
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Dec 12 15:03:28 2012 +0530

    glusterd: Moved node rsp functions to glusterd-utils.c
    
    Change-Id: Ib4c4794563a5a694fab16f17c642f788399462f6
    BUG: 852147
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4295
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e2e12006a2156da24c1374fc5b544447d2914d52
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Oct 23 08:52:55 2012 +0530

    glusterd: Removed start-unlock event injection in 'synctask' codepath
    
    Change-Id: I87e02c95d0b650dab7f9ee86c96b2e09ada50109
    BUG: 862834
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4118
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 454c6c0fde1f0788c4a1a7506c434a9b7d822e85
Author: Venkatesh Somyajula <vsomyaju@redhat.com>
Date:   Wed Jan 23 12:07:12 2013 +0530

    cluster/afr: added logging of changelog for split-brain in glustershd.log file
    
    Change-Id: Iaf119f839cb2113b8f8efb7bf7636d471b6541bf
    BUG: 866440
    Signed-off-by: Venkatesh Somyajula <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4385
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 06a411edbeb84284c7564d8f82e8c2a77054360d
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Jan 28 14:09:39 2013 +0530

    test: Removed "for" loop of check_xattr function.
    
    Change-Id: I902a5f86d72df3efb45dba09eaa2e8be8b65edf6
    BUG: 802417
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4435
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e4811fd339dc6c77fb81c1bef3466a521c8c134b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 29 22:58:17 2013 +0530

    Tests: util to check if replace brick completed
    
    Change-Id: I7748395395454765a35e34611d11f58dd4ef3efb
    BUG: 857549
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4450
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit f0724402d19e339ab58680d6135a91801606f4d0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 29 22:58:42 2013 +0530

    Tests: Basic pump test case
    
    Change-Id: I94666debd5ec271ce5404a77efc421c12928e134
    BUG: 857549
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4451
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5fa1ebe63611759d30d9dec7bd54c879d5e1e420
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jan 11 17:39:20 2013 +0530

    test: test re-opens of open-fds
    
    Change-Id: Ic99c7f3cf1f6a381b0fc1b2ca1acc19f5fe75523
    BUG: 821056
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4387
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5c01280de7ce1a5f4608c7d6b5f6b4fcbf68523e
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jan 11 17:37:10 2013 +0530

    tests: Added util functions
    
    Added functions to extract gfid, gfid-str
    function to check if a file is open
    deleting gfid-link of a file
    
    Change-Id: If2f39f43a6631cddb68b4ba7febcd3cf66f399ee
    BUG: 821056
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4386
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 04e673f14e31c60e4c9cde9072bcec610fe3884b
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 31 10:03:32 2012 +0530

    protocol/client: Periodically attempt reopens
    
    If the brick is taken down and the hard disk is replaced
    and the brick is brought back up, the re-opens of the open-fds
    will fail because the file is not present on the brick.
    Re-opens are not attempted even if the files are re-created by
    self-heal until the brick is brought down after the files are
    re-created and brought back up. This is a problem with a VM-store
    in a replica-setup.  Until the fd is re-opened the writes will
    never happen on the brick where the hard-disk is replaced.
    To handle this situation gracefully, client xlator is enhanced
    to perform finodelk, fxattrop, writev, readv using anonymous fds
    if the file is yet to be re-opened. If the fop succeeds then client
    xlator attempts re-open.
    
    Change-Id: I1cc6d1bbf8227cd996868ab2ed0a57fb05e00017
    BUG: 821056
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4358
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit f78d789c6e9ce29f18487bd6d6a3b8f66a30a464
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Dec 29 14:03:06 2012 +0530

    protocol/client: Add fdctx back to saved-list after reopen
    
    Change-Id: I01caa1b51570359e6e3ffe1ffb7279cbdb0b0c64
    BUG: 821056
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4357
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 315ee9c4e0bdc9f2b1cad21ebfac44f906597fb1
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Jan 16 14:28:19 2013 +0530

    cluster/dht: stack wind with cookie
    
    Default_fops uses stack_wind_tail. It winds without creating the frame leading
    into wrong subvol return in the cookie. To avoid the problem caused by the
    same, we're getting the subvol by passing the cookie.
    
    Change-Id: I51ee79b22c89e4fb0b89e9a0bc3ac96c5b469f8f
    BUG: 893338
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4388
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit b5a6d4bd97800dd00849677c2ace4417dd914ccc
Author: Anand Avati <avati@redhat.com>
Date:   Tue Jan 29 23:56:25 2013 -0800

    fuse-bridge: fix some breakages from lock migration patch
    
    - do not attempt lock migration if no locks were ever acquired on
      an fd.
    
    - fix fd_lk_ctx_t ref leak during fd migration
    
    - remove spurious fd_unref() (probably added to compensate for
      the fd_ref leak in syncop_open_cbk)
    
    - remove @newfdptr out-param which makes fd ref management really
      tricky (and currently refs were unmanaged for the out-param).
      Instead acquire ref and unref within lock migration function.
    
    Change-Id: I4cc9c451f0df4c051612bd1fa7bef11e801570e4
    BUG: 808400
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4453
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit 12689595abd50d13711f855dddfb5cfe51f40455
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jan 30 15:46:49 2013 -0800

    fd-lk: implement new method to check for empty fd_lk_ctx_t
    
    to use this in fuse-bridge, to conditionally attempt lock migration
    to new graph.
    
    Change-Id: I9b10d5839c4ac6051c75e4c020371391cd886ac8
    BUG: 808400
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4455
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>

commit e979c0de9dde14fe18d0ad7298c6da9cc878bbab
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jan 30 13:47:31 2013 +0530

    libglusterfs/syncop: do not hold ref on the fd in cbk
    
    * Do not do fd_ref in cbks of the fops which return a fd (such as
      open, opendir, create).
    
    Change-Id: Ic2f5b234c5c09c258494f4fb5d600a64813823ad
    BUG: 885008
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4282
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 559219492477624290b4962a9f82c49bcda011d9
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jan 24 18:40:06 2013 +0530

    762989.t: fix a typo by grepping only the blocked port number from netstat o/p
    
    Change-Id: I14c3daa799f0936014bf8aa9fd798ecbaec6e912
    BUG: 762989
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4426
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b8d5fd2b88db7e18a10e57a0edf1a41eda4f5314
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jan 24 11:39:48 2013 +0530

    glusterfs : Moved option files, and statedumps from /tmp
    
    Change-Id: Ibdede396c4d6859225937316b7a59a661bcaf9f5
    BUG: 764890
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4422
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 326a47939dabff218205ca2959b9701e2e0ce47c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jan 28 16:14:09 2013 +0530

    cluster/afr: if a subvolume is down wind the lock request to next
    
    When one of the subvolume is down, then lock request is not attempted
    on that subvolume and move on to the next subvolume.
    
    /* skip over children that are down */
                    while ((child_index < priv->child_count)
                           && !local->child_up[child_index])
                            child_index++;
    
    In the above case if there are 2 subvolumes and 2nd subvolume is down (subvolume
    1 from afr's view), then after attempting lock on 1st child (i.e subvolume 0)
    child index is calculated to be 1. But since the 2nd child is down child_index
    is incremented to 2 as per the above logic and lock request is STACK_WINDed to
    the child with child_index 2. Since there are only 2 children for afr the child
    (i.e the xlator_t pointer) for child_index will be NULL. The process crashes
    when it dereference the NULL xlator object.
    
    Change-Id: Icd9b5ad28bac1b805e6e80d53c12d296526bedf5
    BUG: 765564
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4438
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7cc5edb3dcbacaec65b67831018b51a5a384f513
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 29 18:45:08 2013 +0530

    Tests: Test functionality of flush/fsync with afr
    
    Change-Id: I307a77e90e1852f5e43d50e347f7b52468105389
    BUG: 888174
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4447
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 360868e9b010f770bd727570e0f0404069c3375a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 29 17:58:09 2013 +0530

    cluster/afr: wakeup delayed post op on fsync
    
    Change-Id: I5d84ef72615f9d71b4af210976e2449de6e02326
    BUG: 888174
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4446
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 36a9ac82f05aeb01b0656bb82631a87db6a11803
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jan 25 10:58:19 2013 +0530

    cluster/afr: Change order of unwind, resume for writev
    
    Generally inode-write fops do transaction.unwind then
    transaction.resume, but writev needs to make sure that
    delayed post-op frame is placed in fdctx before unwind
    happens. This prevents the race of flush doing the
    changelog wakeup first in fuse thread and then this
    writev placing its delayed post-op frame in fdctx.
    This helps flush make sure all the delayed post-ops are
    completed.
    
    Change-Id: Ia78ca556f69cab3073c21172bb15f34ff8c3f4be
    BUG: 888174
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4428
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4cbb14cf6fc3f1b52ff0062a9fee88e2170ad454
Author: Anand Avati <avati@redhat.com>
Date:   Tue Jan 29 10:05:29 2013 -0800

    quick-read: various fixes
    
    - initialize xdata in qr_lookup even if it was NULL from top. This
      allows qr to do its job even if lookup originated from fuse-resolve.c
    
    - extend test cases to include 1 second delay and retry
    
    - fix bug while checking condition for cached unwind
    
      qr_readv_cached() unwinds if op_ret > 0. Therefore qr_readv()
      must wind to subvol only if !(op_ret > 0) (i.e, op_ret <= 0).
    
    - qr_readv_cached() is using uninitialized @conf pointer. Thanks
      to Raghavendra Bhat for catching this!
    
    Change-Id: Ifaf2ea2685e452210ef9ba3c2d1f2ab51900650c
    BUG: 846240
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4452
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 088050b257ac9cbd2115587b0f7306760c44a4a3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Nov 16 12:06:36 2012 +0530

    performance/io-cache: propagate errors while unwinding frame in
                          read path.
    
    Change-Id: Ieb5d592a987e8681d5ec019da309f75e3b207580
    BUG: 858242
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4204
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f811441e257cafb975dfcd16f14b4378beee524e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jan 25 10:00:57 2013 +0100

    tests: skip time consuming mock builds for code-only changes
    
    tests/basic/rpm.t takes a bulk of the time for the regression tests.
    Often the building of the rpm is not affected at all and therefor the
    tests does not add any value.
    
    With this change the rpmbuild/mock test will only be run when some
    changes affect the build system. Changes affecting 'tests/', 'doc/',
    '*.py', *.c' and '*.h' do not trigger the test anymore.
    
    Change-Id: Ic188b9e26cde3113b2bdf9cd1fab56d9fd85a4b7
    BUG: 904005
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4429
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fed0752313c37c500d3b88f0651c4923cec4cf9b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jan 29 10:50:01 2013 -0500

    socket: null out priv->ssl_ssl on disconnect
    
    This prevents problems when a socket transport is reused for a non-SSL
    connection (e.g. glusterd portmapper) after having been used for an SSL
    connection (e.g. a brick).  In that case, ssl_ssl will still be non-null from
    the first connection, even though the structure it points to has actually been
    freed.
    
    I'm not sure why/how we would reuse a socket transport in this way (the case of
    SSL after non-SSL has been common for a long time) but recent glusterd changes
    seem to have had that effect.
    
    Change-Id: I46f1ff3c409c122478bf720a7f02d92abcc32bed
    BUG: 902684
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4449
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c3f1c0c18a04615cb33040748d1eae558a9203b5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 29 11:27:58 2013 +0530

    mgmt/glusterd: Expose post-op-delay through cli
    
    Change-Id: I13e3699bd58d53896ae54e1bfafb3cd1c9580c7c
    BUG: 905307
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4443
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 15716cfe7a38dc1a49fde298d84c9efdb7617ada
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Jan 25 19:23:15 2013 +0530

    Tests: Fix latency calculation
    
    Idea is to make sure that the FINODELK max latency is not
    in the order of seconds.
    
    Change-Id: Ic47dc46c3b2d24d223fe7e2212c4c035de37c9ae
    BUG: 895235
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4434
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fd9612466a8dfbfe0f918426919cf8ec135ffb4b
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Jan 28 13:24:03 2013 -0500

    performance/md-cache: add force-readdirp flag to make readdirp configurable
    
    md-cache currently transforms all readdir fops into readdirp fops.
    This patch creates the 'force-readdirp' configuration flag to
    provide control over this behavior. force-readdirp is enabled by
    default to maintain current default behavior.
    
    BUG: 903175
    Change-Id: Idd70926dec7c271204bdfb11fb052e56d0a39420
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4440
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fb9f29e892e762e161fc9ed72403eeaadb050077
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jan 21 16:42:41 2013 -0800

    fd: expose __fd_ctx_del symbol
    
    used by open-behind for deleting context in locked critical region
    
    Change-Id: I3380152211fed6aacbb719468b720376e6ec1e7c
    BUG: 846240
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4405
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a81748c3f49790e78ef168e25db025d0da838338
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jan 21 13:12:11 2013 -0800

    fd: filter anonymous FD from fd_lookup() result
    
    Those callers whose requirements can accommodate an anonymous FD
    need to call fd_anonymous(). fd_lookup() is strictly for open()ed
    file descriptors only.
    
    Change-Id: I5d8da3db0f44b2e2161d345d7a662cfd4ef87500
    BUG: 846240
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4404
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 54c68942b456ffa8d15b39b43a7723712b2a1a25
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jan 28 12:31:16 2013 -0800

    bug-765564.t: fix path for file to rename
    
    The script assumed it was chdir'ed into the mount point while it
    was not. There also happened to be (conincidentally) a directory
    of name 'a' in the workspace. The first the script was run, the
    rename succeeded. All future tests are failing as the directory
    already exists.
    
    Change-Id: I92ad62e7893c03bb3f2af75c51d35bc35866dafe
    Signed-off-by: Anand Avati <avati@redhat.com>
    BUG: 765564
    Reviewed-on: http://review.gluster.org/4442
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cc96adbe4604ea5fd462d8db77486c2f963baf43
Author: Anand Avati <avati@redhat.com>
Date:   Fri Jan 18 14:04:23 2013 -0800

    quick-read: refactor
    
    - peel out 'open behind' functionality into a separate translator
    - issue where, if file size had grown by revalidate, data was not flushed
    - removed unnecessary acquistion of table->lock (e.g in qr_lookup())
    - keep inode ctx persistent, prune only data (effectively changing the
      order of lock acquisition from INODE -> TABLE)
    - validation with readdirplus
    - use variable size iobufs to simply cached reads
    
    Change-Id: If1586d0298fd1697ddff9fd7008efb3d286d436a
    BUG: 846240
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4403
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 99e63168c498cf57f3f8fabab1d2b86a4ea639ce
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jan 28 12:55:17 2013 +0530

    cluster/afr: before checking lock_count of internal lock make sure its not
                 entrylk
    
    when the expected lock count is equal to the attempted lock count, then before
    deciding that lock is failed on all the nodes, make sure the lock type is
    checked properly.
    
    Change-Id: I1f362d54320cb6ec5654c5c69915c0f61c91d8c7
    BUG: 765564
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4436
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c950d3f0e104fc7b78e493ad7ca0005a600b00f9
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jan 23 23:30:07 2013 -0800

    bug-867253.t: do a clean umount at the end
    
    On some machines, not doing a clean umount of NFS mount results
    in a hang, because sometimes the next script's cleanup() kills
    NFS server and the client mountpoint hangs forever.
    
    Change-Id: I64798202180c920650272cc19bcbe07d44377ff6
    BUG: 867253
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4421
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 710c52d23a2e7839a156c123167c6e13c8207f76
Author: JulesWang <w.jq0722@gmail.com>
Date:   Fri Jan 25 11:49:18 2013 +0800

    glusterd: make 'glusterd_is_local_addr' return bool
    
    Change-Id: Id3bd0bfc4802c166f7a32b0cc6a726aeb5617b5d
    BUG: 890618
    Signed-off-by: JulesWang <w.jq0722@gmail.com>
    Reviewed-on: http://review.gluster.org/4427
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0cd9ef501d4e938a49da7835d96cec9f72521ecd
Author: Brian Foster <bfoster@redhat.com>
Date:   Fri Jan 25 17:16:45 2013 -0500

    storage/posix: skip path construction when dentry list is empty
    
    This is a minor latency optimization to the readdirp path in
    storage/posix. During a recursive list, we hit this codepath with
    an empty list once per high-level directory to read when end of
    directory is reached. Skip constructing hpath, since we don't do
    anything with it in this case.
    
    BUG: 903175
    Change-Id: I98d7c65505205d55575f064b1e982700f1320cc0
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4432
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1939519979b6c4da110f08434fe63d0b03332d52
Author: Anand Avati <avati@redhat.com>
Date:   Fri Jan 25 19:22:55 2013 -0800

    replicate: fix lock counting in blocking lock path
    
    As of http://review.gluster.org/2828, the blocking lock code
    path's condition for checking completion of locking atempt is
    broken. The condition -
    
    	if ((child_index == priv->child_count) || ...)
    
    and
    
    	if ((child_index == priv->child_count) && ...)
    
    which is retained to check completion of blocking lock attempts
    for DATA/METADATA transaction will _always_ fail because a few
    lines above we have -
    
          child_index = cookie % priv->child_count;
    
    So child_index will never equal priv->child_count. This leaves
    the correctness at the mercy of the next part of the
    conditional -
    
    	.. (int_lock->lock_count == int_lock->lk_expected_count) ..
    
    This "works" as long as no server went down during the transaction.
    
    If a server goes down in the middle of the transaction, then this
    condition also fails, and the code wraps around and starts a
    blocking lock attempt loop all the way again from from the first server.
    This results in double locks getting acquired on those servers, and
    eventually the second condition gets hit (first condition is _never_
    hit) and we come out of locking phase.
    
    During unlock phase we perform only one unlock per server leaving the
    other lock "leaked" forever.
    
    Change-Id: I7189cdf3f70901b04647516fe1d1e189f36cc8dd
    BUG: 765564
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4433
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d8d138300b18fc2291a8a73059ac1d888141d6db
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Jan 25 13:49:47 2013 -0500

    glusterfsd: copyright message
    
    Change-Id: I91accd69e58c90f149ff66e0bfea563a9e59e790
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    BUG: 820551
    Reviewed-on: http://review.gluster.org/4431
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 6fd654dc94fae49fb84336bd2e92c7cc893280e3
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Jan 23 09:59:59 2013 +0530

    cluster/distribute: get_layout should account only available subvols
    
    The earlier logic used to check if (layout-spread-count <= subvol_cnt -
    decommissioned bricks). With this if a subvol was down, and layout-spread was >
    upsubvols, a mkdir ended up creating holes in the layout.
    
    The fix is to consider only the combination of subvols which are usable (not
    down or not decommissioned).
    
    Change-Id: I61ad3bcaf4589f5a75f7887cfa595c98311ae3bb
    BUG: 902610
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4412
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8dc7707c1b32465551d5d5553057e04748945fda
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jan 24 00:31:54 2013 +0530

    debug/io-stats: Handle open failures gracefully
    
    Change-Id: I85b22db5cc456b3e8c9f26c8254f08a796fc2b28
    BUG: 903336
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4418
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4faeedc99284ce4e6b86bec39309b949fb5423ac
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Nov 14 12:23:36 2012 +0530

    "gcc -pedantic": made 'inline' functions as 'static inline' functions
    
    for passing the build with -pedantic flag
    
    Change-Id: I80fd9528321e4c6ea5bec32bf5cdc54cc4e4f65e
    BUG: 875913
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/4186
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1ab086d8630687985fb412f4093a53d3e3e9aca1
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Feb 21 16:28:13 2012 +0530

    afr: Modified book-keeping structures for entrylks
    
    * There are upto 3 entry lockees that may be needed to perform
      entrylk'ing in posix dir-write operations.
    
    * For eg, rmdir ("/a/b") needs to acquire locks on two entities,
      - entrylk ("/a", "b")
      - entrylk ("/a/b", null)
    
    * Changed existing entrylk/rename/selfheal (entrylk) transactions
      to use the new book-keeping structures
    
    * Fixed few issues in afr_trace_entry_lk{in,out} functions. Tracing is now
      aware of the new entry lockee structure.
    
    Implementation notes:
    * Changed 'cookie' sent in stack_wind to encode lockee_entity_no
      and subvol_no.
    
      cookie is a non-negative integer such that 0 <= cookie < replica_count,
      When more than one lock is being acquired across the subvolumes,
      cookie % replica_count gives the subvol_no
      cookie / replica_count gives the lockee_entity_no.
    
    Change-Id: Idbf41803387a7d59a0f7fcb1453d91cea74da153
    BUG: 765564
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.org/2828
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 91ac9f97417790f439702c0297bca953ece597c8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Dec 14 01:05:39 2012 +0530

    cluster/afr: Remove strict-readdir implementation
    
    Leaving option frame-work un-changed for backward compatibility.
    
    Change-Id: I40bce1ec360801307e67f09e53b0721f64efab37
    BUG: 886998
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4309
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f935c12c50691af3196b3525206ad2df4de91cb8
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 22 14:48:38 2013 +0530

    Tests: Check that stale indices are removed on heal-info
    
    Change-Id: I1f652d0343053fb87e4979de8b94ba09b3f292f8
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4409
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 2c65cdfd6484dc073241c46de041da2ab380bc09
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 22 14:46:48 2013 +0530

    Tests: Add utils to get index-path, index-count
    
    Change-Id: I6eebae4b419f92212a30ce5e0dfc889a4541a4ce
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4408
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit e908659dfee988799deee888259ca54a0a9f6e31
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 17 21:24:53 2012 +0530

    self-heald: Remove stale index even in heal info
    
    Change-Id: Ic1c9559aec59c1fb9dfede4aba8895f3b86f32f1
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4098
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 16d2801f072f5eb1d2ddb56a2ab5eecd3a42010a
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Tue Dec 18 10:55:24 2012 +0530

    object-storage: use temp file optimization
    
    A file name '.<FILENAME>.<RANDOM>' will hash to the same GlusterFS node
    as a file named '<FILENAME>', thus avoiding creation/deletion of linkfiles on a rename.
    
    This is part of the work needed to address BZ 876660
    (https://bugzilla.redhat.com/show_bug.cgi?id=876660).
    
    Change-Id: I6f18c14b8eaa7a35c96f7e455ef3a19bee7dbde5
    BUG: 876660
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.org/4325
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Peter Portante <pportant@redhat.com>

commit 2f60c8a4776a6052cfba43605263dd32c616cfa2
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Jan 17 14:46:30 2013 +0530

    glusterd/cli: Updated the options descriptions for "volume set help"
    
    Change-Id: I0db00b7334bb9707ab48bd661ac03a3ad818d6e4
    BUG: 893458
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4393
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4fdc84da10104ef9bd3c2c7015e427056d32ccc5
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat Sep 8 00:53:52 2012 +0200

    geo-rep / glusterd: do non-blocking connect to checkpoint service
    
    glusterd should not hang if gsyncd ends up in some weird state
    
    Change-Id: Ic141daa0cd05d515848c8b6c25702418e15b7599
    BUG: 826512
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/3919
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 777d395feaa082a69e32d985bbc1cca3d3dad077
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Nov 21 14:07:05 2012 +0530

    core: fixes for gcc's '-pedantic' flag build
    
    * warnings on 'void *' arguments
    * warnings on empty initializations
    * warnings on empty array (array[0])
    
    Change-Id: Iae440f54cbd59580eb69f3ecaed5a9926c0edf95
    BUG: 875913
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4219
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6e18e3bd81f8dac9467aaa6cbe84499b891ca367
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Jan 22 00:26:58 2013 +0530

    Test to check if inode-link failures appear
    
    Change-Id: I572a6361f46efc3a0fe7f89a15f3a847c31901a7
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4402
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 50d91473c202a44f39cdf4640d7966af370f2dce
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 21 23:52:21 2013 +0530

    self-heald basic tests
    
    Change-Id: I50e5c4a6712cfc0a7c544551ba1ff182d851f522
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4401
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 376b4044052a4e5d25e2390bbb8c2659028d6b09
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 21 23:32:38 2013 +0530

    Tests: functions for shd statedump, child_up_status
    
    Change-Id: Ifed91d25b7c62e79019ece336e1065fa35beddb0
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4400
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ab6ef33d1c0afc4d265440e52f6e0cb5d2ed007d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Jan 21 18:06:25 2013 +0530

    Tests: Added function to get pending heal count from heal-info
    
    Change-Id: I0aed0bb79e45326e3872ae187cb9addd06342a56
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4399
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8d5bb5292d75794838ee37e87a97a01cfc59b932
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Oct 16 10:24:30 2012 +0530

    cluster/afr: Link inode only on lookup
    
    Problem:
    When "gluster volume heal <volname> info is executed, crawl's
    process_entry is not going to populate iatt structure so the
    iatt's gfid will be empty. So inode_links are failing.
    
    Fix:
    inode_link should be done only after lookup i.e. when heal is
    performed. So moved the inode_link related code to just after
    the lookup which is triggered when self-heal is done.
    
    Tests:
    The testcase that gives this issue does not give the inode-link
    failures anymore. glustershd heal, info commands are working as
    expected.
    Wrote basic automation tests for proactive-self-heal-daemon
    https://github.com/pranithk/gluster-tests/blob/master/afr/proactive-self-heal.sh
    
    Change-Id: Ic112bf104a4d553a64d3d8559f681a25ae1a5362
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4090
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9f7ff7df94067e8e7e571354835406ba5574a53a
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Jan 15 00:35:21 2013 +0530

    cluster/distribute: If cached_subvol is down, return ENOTCONN in lookup
    
    When we follow a linkfile, and the lookup returns a ENOTCONN error, return
    the error, as the cached subvol is down, and lookup_everywhere wont succeed,
    but actually ends up clearing the linkfile, and clearing the namespace.
    
    Change-Id: I772bf71531bc646e8fb62d3e8549a5fe0f3896da
    BUG: 893378
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4383
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e95e8f87152dc2895b7e2dcd0c43ed939e2f4058
Author: Shireesh Anjal <sanjal@redhat.com>
Date:   Mon Jan 21 18:59:50 2013 +0530

    cli: fix descriptions of owner-uid and owner-gid
    
    Change-Id: I04c0dd23bc5bc34fd9d7bddb11beeecb8e7e2a49
    BUG: 853842
    Signed-off-by: Shireesh Anjal <sanjal@redhat.com>
    Reviewed-on: http://review.gluster.org/4398
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 783f349575ac169c7777ab603614d19bcd968a7c
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Jan 2 16:37:04 2013 +0100

    build: glusterfs-server should own known files under /var/lib/glusterd
    
    In continuation of Change-Id Ib1df8da7e8abdcd3edece45bd39fe238f28838f1
    there are more files that should be owned by the glusterfs-server
    package.
    
    Note that starting glusterd, doing some peer-probes and creating volumes
    will create additional run-time files under /var/lib/glusterd. The
    filenames depend on the volumes that are created, and that prevents
    packages from knowing (and owning) them in advance. It seems common
    practice to leave files untouched under /var/lib/<app>.
    
    It would be okay to remove files generated by the package itself, but we
    should not remove files generated by other packages, or files that have
    been created by users manually. I do not see a way to detect files
    generated by gluster* applications and remove only these. Keeping the
    runtime files under /var/lib/glusterd (which do not have predictive
    names) is safe and they should not require much space anyway.
    
    BUG: 829734
    Change-Id: I2b79682b014fcf62c2a73f076cf0b11b4ba87f4a
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4361
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee05db0b1e8ea27eb63f62b951c71388bcf69c6e
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Dec 21 10:50:27 2012 +0530

    extras: Don't update RETVAL with invalid value.
    
    Problem:
    Start and restart functions update the value of RETVAL internally.
    Assigning $? to RETVAL after function return was updating RETVAL with
    invalid value.
    
    Fix:
    Removed assignment statement after start and restart functions return.
    
    Stop function was always returning 0 as return value due to one extra echo
    command. Removed echo line.
    
    Change-Id: Iec1a83a83463f419dd45e12daf4e5ded80568a3a
    BUG: 888442
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4349
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 13c1c105146288a12210dfbd2b2c4cbbd6960c06
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Jan 17 21:11:28 2013 +0530

    cluster/afr: Disable delayed post op when eager-lock is off
    
    Problem:
    When eager-lock is disabled, inodelks for write-fops on same
    fd conflict with each other. If eager-lock is disabled but
    delayed post-op is enabled then each write fop's inodelk unlock
    waits for post-op-delay-secs. So the conflicting write fop
    acquires inodelk after post-op-delay-secs. This results in
    post-op-delay-secs delay for every write fop on the fd for
    sequential writes (Ex: dd).
    
    Fix:
    Disable delayed-post-op when eager-lock is off.
    
    Change-Id: I87ea4c8d1c7bb269b9b174388ae50f37e82629b7
    BUG: 895235
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4391
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1ad17d69832369acf6177c378ddd8053174e8b6e
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Dec 11 21:45:46 2012 +0530

    glusterd: log changes in volume stop (and in op sm codepath)
    
    This patch makes log changes mostly in the op state machine as also
    in volume stop codepath of glusterd.
    
    Changes made:
    
    * Moved log level from INFO to DEBUG, of log messages on the various
      state transitions within a transaction.
      For example, messages of the following kind:
      a. "Sent op req to <n> peers"
      b. "Received LOCK from uuid: <peer-uuid>", etc.
    
    * Changed some of the log messages to give as much information as
      available in case of failure.
    
    * Added logs to identify on which machine lock/stage/commit failed.
    
    * Quite a few s/THIS/this changes.
    
    Also, with this change, log changes in all other volume ops
    should (hopefully) boil down to modifying the respective logs in
    handler, stage and commit (and brick ops in some cases).
    
    Change-Id: I2b8443042b07fb41a1d12033741f7e156aa6b3da
    BUG: 812356
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4382
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a2b85d13e50327da721e32071aecad21b10ffb1a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 15 23:07:24 2012 +0530

    cluster/afr: Fail readv on data-split-brain
    
    Problem:
    Afr prevents opens on a file in split-brian but the
    fd that is already open still has the capability to perform
    both reads and writes to the file.
    
    Fix:
    Fail readvs on a file with EIO.
    
    Change-Id: I8e07f24c36fab800499b36ab374f984b743332cd
    BUG: 873962
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4199
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ba16dc622a4ffc24baf7c2cde1210be7bf9fa019
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Jan 17 13:54:36 2013 -0500

    glusterd: replace obsolete /usr/local reference for remote ssh/gsyncd
    
    See https://bugzilla.redhat.com/show_bug.cgi?id=895656
        https://bugzilla.redhat.com/show_bug.cgi?id=764679 (GLUSTER-2947)
        https://bugzilla.redhat.com/show_bug.cgi?id=764623 (GLUSTER-2891)
    
    The comments in the bzs are a bit obtuse and/or vague. As near as I
    can make out we had, for a while, a "convenience symlink" to or from
    /usr/local/libexec/gsyncd, which no longer exists.
    
    And, lacking any comments in the code, I gather this is some sort of
    fallback or failsafe logic: if the first, normal attempt to invoke gsyncd
    fails then an attempt is made to ssh to the box and invoke it.
    
    In any event, there's nothing in /usr/local/... so it's unquestionably
    wrong to try to invoke anything there.
    
    BUG: 895656
    Change-Id: I3b7ac7a049b91ce101b930599294830147cc60ad
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/4392
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Joe Julian <joe.julian.prime@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 679cb2399fc1f8e97f2b29654ec422f267b03783
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Jan 10 10:49:17 2013 -0500

    afr: conditionally prioritize EIO errors over ENOENT
    
    The most important errno logic historically only prioritized ESTALE
    over ENOENT. Commit c8c0942d added EIO prioritization over ENOENT
    to ensure that split-brain was reported when it occurs in
    conjunction with bricks missing the file entry. The unintended side
    effect of this change is that (non split-brain) EIO errors reported
    from the bricks themselves are now reported to the client when the
    expectation is that afr should squash said errors in favor of
    marking the file inconsistent.
    
    The high-level problem is that EIO is overloaded with different
    meanings from different contexts. This commit adds an eio parameter
    to the errno priority logic to conditionally flag when EIO is of
    higher priority and should be propagated to the client.
    
    BUG: 892730
    Change-Id: Ib692a8a1f1737ef190d57894f392ec53ffb33aab
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4376
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9036bd1a7bab68351c38d65cd6a1c8af150467bb
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Dec 17 16:29:42 2012 +0530

    nlm: use virtual ip of server to connect to client
    
    In cases where the servers use virtual ip's, this commit
    makes sure we use them and not the physical ip.
    
    This change also refactors code around nlm4_establish_callback
    by sending granted msg only after a connection establishment,
    and removing the separate thread creation.
    
    Change-Id: I087362c547a25aa52ef7fc6653845a3863466ee6
    BUG: 888283
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4326
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fd8b19af1713f2800af743d851706b96ca15d9ec
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Nov 14 19:25:14 2012 +0530

    debug/trace: save the recent fops received in the event-history
    
    * Make use of event-history in debug/trace xlator to dump the recent fops,
    when statedump is given. trace xlator saves the fop it received along
    with the time in the event-history and upon statedump signal, dumps its
    history. The size of the event-history can be given as a xlator option.
    
    * Make changes in trace to take logging into log-file or logging to
    history as an option. By default both are off.
    
    Change-Id: I12baee5805c6efb55735cead4e2093fb94d7a6a0
    BUG: 797171
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4088
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 165044cee54ceaa8f0adec6d571e9ad54f4f8e5d
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jan 17 18:01:35 2013 +0530

    tests: Fix tests for bug 857330
    
    Changed some tests to use EXPECT, which I should have done originally, instead
    of using TEST. With recent changes to the EXPECT primitive we get more info for
    failures, which hopefully will make debugging of the intermittent failures of
    these tests easier.
    
    Change-Id: If763dcfb7e370a3f360277c3c183b950aede5685
    BUG: 857330
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4390
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d177372ee732acc3b2ce7a395d83f8c03ec19ce2
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Jan 10 10:49:08 2013 -0500

    afr: replace afr_more_important_error with afr_most_important_error
    
    afr_more_important_error() is written to return whether a new errno
    should override an existing errno for high-level operations that
    could span multiple sub-operations. It specifically prioritizes
    ESTALE over EIO over ENOENT, and otherwise defaults to the latest
    error passed having priority.
    
    This change preserves current behavior, but rewrites the logic to
    return the higher priority error of the existing and new errno. The
    purpose of the change is to make the logic a bit more clear and set
    the stage for future changes to make the logic flexible based on
    context.
    
    BUG: 892730
    Change-Id: Id1aa48855dfb0507abc9d1ef22f2259b30472576
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4375
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2a4c48b4ed0d1b04ad218ace529e24a96d4f0f3b
Author: Varun Shastry <vshastry@redhat.com>
Date:   Wed Dec 19 11:27:57 2012 +0530

    cluster/dht: update ctx-time only if we receive the new iatt
    
    1. Used local->postparent(contains merged iatt of all succesful calls) instead
    of postparent for dht ctx time update.
    
    2. dht_inode_ctx_time_update avoided in case of opret -1.
    
    Change-Id: Ie04a7842a41c241f911b6a3f76267b996d27fb43
    BUG: 881013
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4338
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8b87819b9f374f78d13746878d6ed7a260a8ae9a
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Dec 19 00:01:13 2012 -0500

    object-storage: add UFO unit tests
    
    Run the UFO unit tests following the main GlusterFS unit tests. The
    UFO unit tests run under the Nose unit test running harness, requiring
    the python-nose package to be installed. These unit tests run fast
    enough that we could even consider running them on a commit hook run
    by rfc.sh.
    
    Note that they are not functional tests, as they don't require a real
    Gluster file system to run.
    
    Change-Id: I55972890c24be16fc588a6950cb6bfd539287bbe
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4333
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit cea939a5b11bd035f87232e0f3178d832dcbdf1f
Author: Kaushal M <kaushal@redhat.com>
Date:   Sat Dec 29 12:43:59 2012 +0530

    cli: output xml in pretty format
    
    Gluster cli now prints XML outputs in 'pretty' format. This solves the problem
    of empty elements occuring as two tags instead of being collapsed into one.
    
    Change-Id: Iab7aeadcff29c18ae388b58e446a16e937ac09ed
    BUG: 849293
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4355
    Reviewed-by: Krutika Dhananjay <kdhananj@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b445678d03b5ad18f85b025f72384b9a343ec9ee
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 18 09:24:38 2012 +0530

    cluster/afr: Pre-op should be undone for non-piggyback post-op
    
    Problem:
    When fop fails post-op is always performed
    over the network irrespective of whether pre-op is piggybacked
    or not. Decrementing Pre-op-done count even for the piggybacked
    ones is wrong.
    I have added an assert for pre_op_done to be non-zero and when
    dd of=a if=/dev/urandom bs=5M count=1000 is executed and a brick
    is taken down, the mount is crashing.
    
    Fix:
    Decrement pre-op-done count only when the post-op is not
    piggybacked.
    
    Change-Id: Ie837251a43bfb437f0fada191302eeee60be1601
    BUG: 863939
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4310
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8307ae12fa47db0510ef4353017ad5627adba75d
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Oct 4 15:12:12 2012 -0400

    replicate: don't clear changelog for un-healed replicas
    
    Change-Id: Iebfa6770a688e89c051666b46977862188061738
    BUG: 802417
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4034
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 40ce0d6b12a105c975a58bf308b73ca677c7d5fb
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Jan 8 08:53:51 2013 +0530

    glusterd: Don't persist enable-pump in volinfo->dict
    
    - enable-pump option in the pump xlator is set during a replace-brick
      session. This was persisted in the volinfo->dict for volume file
      generation.
      It has two 'harmful' side-effects,
      a) It would lead to volinfo cksum divergence among peers in
         cluster (for the same version no.) during a replace-brick session.
    
      b) "enable-pump" key would appear in "gluster volume info VOLNAME".
         This key is used internally in volume file generation code to
         optionally load the pump xlator in the source brick. It is _not_
         an volume option.
    
    Change-Id: I37a8e7186e2985d187e4a166a599cf69145a90f9
    BUG: 886000
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4367
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b9249c8f9f838c2a9c28e5c09fffddc9c8917df6
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 14 10:48:46 2012 +0100

    Fix format security errors with hardening build flags
    
    These problems were found while building with the hardening options used
    by Debian. In order to prevent introducing new unsafe constructs, the
    options -Wformat" and -Werror=format-security are addeded to the CFLAGS
    by configure.ac if the compiler supports them.
    
    Also, a small spelling fix in posix-aio.c is included.
    
    Change-Id: I1034311644fa3c21bc5a7b842c41a3ca79108b3f
    BUG: 887278
    Original-author: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4311
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fba70e641eb52c90fa29fc26d916e4607e286779
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jan 10 13:06:21 2013 +0530

    protocol/server: do server_connection_put only if bound_xl is NULL
    
    If getting bound_xl fails, then while putting the connection back we
    should also check for bound_xl pointer for NULL apart from the op_ret
    and the connection object. We were checking just op_ret and conn pointer
    till now and if the mount from a machine is not allowed as auth.allow
    did not permit it, then also we were destroying the connection object.
    
    Change-Id: Iac43e8dc078d905edafb44d6670f88989a8f82a3
    BUG: 881062
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4373
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a65a482dc2f09de3e1115c593864248522eea29e
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Fri Jan 11 14:53:50 2013 +0530

    socket: Don't log readv failures if read-fail-log is false
    
    Change-Id: I6903d62cbc7107eb8498bcd81d07667b36890a02
    BUG: 764888
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4377
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fd32c05f461efd48e46d879cdba85a2fe894a2e0
Author: Raghavendra Talur <rtalur@redhat.com>
Date:   Fri Dec 21 12:23:19 2012 +0530

    extras: Changed the exit status in start function to 0.
    
    Problem:
    We were returning "1" when "glusterd start" was being called with service
    already running. As per
    http://refspecs.linuxbase.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
    we should consider it to be a success case and return 0.
    
    Fix:
    Just changed the return status from 1 to 0.
    
    Change-Id: I8d6d2014f0c32ba53834503e721e2a71df7330a8
    BUG: 845653
    Signed-off-by: Raghavendra Talur <rtalur@redhat.com>
    Reviewed-on: http://review.gluster.org/4348
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c5a70e5b1b646e5d5e6bec573c6729a7b149345d
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jan 8 11:20:14 2013 +0530

    Changes to support automake-1.13
    
    automake-1.13 obsoletes some macros that were being used. This patch replaces
    these macros.
    
    Change-Id: I2a24a923f284e9b54fb57ccc27eb0b5ad8dd6050
    BUG: 892882
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4368
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7e6395bd8e1810ba8c4614afe15616378b5f7ef5
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Dec 18 18:44:54 2012 +0530

    tests: make EXPECT_WITHIN also fail on command failure
    
    Change-Id: I051bbe2344f19e647826ee177932ae8b95747ebd
    BUG: 764966
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4334
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 292e1b3f7bccd7cbbced62707a1d4f59cef90222
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Jan 9 21:51:02 2013 -0500

    glusterd: fix memory corruption when probe fails
    
    Change-Id: If161e9bebfd518b355aaf37af7805e804772dc2d
    BUG: 893851
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4372
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 61905d64188f2db8e33bfe7bc4c499844a6b4b3a
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Dec 19 18:03:42 2012 +0530

    glusterd: Add GF_ASSERT check in glusterd volume op handlers
    
    Change-Id: Iea6ac1e612812ba8ffc4b60899a9e574a3b09ea6
    BUG: 873549
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4346
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 386031c784537e3877a0797f3fc28f9a221246ae
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Dec 24 15:17:13 2012 +0530

    glusterd: Set replace-brick id in op ctx only in origin glusterd
    
    Change-Id: I8282f911fb47f4cfb45947b2810d84105c82b5ff
    BUG: 889999
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4352
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit f1b2faab5e28e1ea33401022e16aec161fbca353
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Dec 20 13:27:13 2012 +0530

    cli: Fix task-id xml compilation
    
    Change-Id: I92ada7d5ba1eb46024f47c4f32c517db27ada576
    BUG: 857330
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4342
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit d3cc5862faa9ebda4d8d80f6b3e7a45c0df85c0c
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu May 3 16:29:06 2012 +0530

    glusterd: Made dst brick's port info available to all peers
    
    Change-Id: I1f65743a31d95013fdf22cded91c314e9934a3a9
    BUG: 816915
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.org/3275
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 129728f257bead0ce0c28b98d3989fabaebe21cd
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Dec 6 13:08:11 2012 +0530

    glusterd: log enhancements for volume start
    
    * changed some of the log messages to give as much information as
      available in case of failure
    
    * added logs to identify on which machine lock/stage/commit failed
    
    * added macros to represent error strings to maintain uniformity
      among error messages for a given kind of error
    
    * moved error logs wherever possible, from caller to callee to avoid
      code duplication
    
    Change-Id: I0e98d5d3ba086c99240f2fbd642451f175f51942
    BUG: 812356
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4353
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 90ee11d0c5b3b4d57382fdff4500b1da4bdea9a0
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Dec 21 14:37:29 2012 +0100

    nfs: correct phrasing of nfs-mount-udp option
    
    `gluster volume set help` shows the following typo for the nfs.mount-udp
    option:
    
    Option: nfs.mount-udp
    Default Value: (null)
    Description: set the option to 'on' to enable mountd on UDP. Needed by
    Solaris NFS clients if NLM support isneeded
    
    Also, AIX NFS-clients seem to need this option, hence rephrasing the
    description to be more helpful.
    
    BUG: 889500
    Change-Id: I91d88d74824da13dcfe828015d7b9e18abc93ef2
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4350
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b94999ba8566bbf91cb9b402d2376f1ac9e36242
Author: JulesWang <w.jq0722@gmail.com>
Date:   Fri Dec 21 14:32:35 2012 +0800

    glusterd: "volume status" for remote brick fails on cli.
    
    cli fails because key "brick-index-max" is missing in rsp dict.
    
    Change-Id: I38119bbd31b68fe3ad1152af2495dff7624d99b7
    BUG: 888752
    Signed-off-by: JulesWang <w.jq0722@gmail.com>
    Reviewed-on: http://review.gluster.org/4347
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b7fd110d42c658e56e8af234a81a7664bbf83ba4
Author: Varun Shastry <vshastry@redhat.com>
Date:   Fri Dec 21 17:25:54 2012 +0530

    system/posix-acl: prevent NULL pointer dereference of group_ce
    
    Thanks Amar Tumballi.
    
    Change-Id: I3ac9b46d4c3fcd12d1eec779317a03c47d267556
    BUG: 887098
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4351
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 91cc423b48df800dcfff7040ca4a95ef2a9d6afc
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Dec 20 16:48:50 2012 +0530

    logging: Added fflush in _gf_log.
    
    Change-Id: I06444b6bc3b1acc8cabd863087bd3508de3c548c
    BUG: 889157
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4344
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2cced9f0c116df102b6163d24c0ad7e09d198a69
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Dec 19 17:04:33 2012 +0530

    glusterd: Remove invalid free of op_errstr
    
    Thanks to Raghavendra Bhat for pointing it out.
    
    Change-Id: I77b0f02a71ce273c9d1ffcbb1ce7e9d5b34d9de9
    BUG: 873549
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4345
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ab7ffc390778a9a2ab3cb85490707972a1fd3f9b
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Dec 20 13:22:28 2012 +0530

    protocol/client: print a message regarding brick status in case of failure
    
    that way, it would help admins to look at the corresponding brick directly.
    
    All credit goes to Amar.
    
    Change-Id: I959df59111864cc0574945d827f8fe5f2d919491
    BUG: 839021
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4341
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 000e65d7af7be31236e060064fb3b4a332e78cf3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Nov 13 01:14:43 2012 +0530

    core: remove all the 'inner' functions in codebase
    
    * move 'dict_keys_join()' from api/glfs_fops.c to libglusterfs/dict.c
      - also added an argument which is treated as a filter function if
        required, currently useful for fuse.
    
    * now 'make CFLAGS="-std=gnu99 -pedantic" 2>&1 | grep nested' gives
      no output.
    
    Change-Id: I4e18496fbd93ae1d3942026ef4931889cba015e8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 875913
    Reviewed-on: http://review.gluster.org/4187
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e5a19e2ab587175c91fde0f0c33319dcbff73018
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Sat Dec 8 11:55:20 2012 +0000

    api: update Python wrapper
    
    This brings us back to functional parity with the C example, and also makes
    things more "Pythonic" (e.g. methods on Volume/File objects instead of bare
    functions).
    
    Change-Id: I46edfee46d91881e275de2f63e15d9f0a6448e80
    BUG: 839950
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4286
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5eb8bac561b7374589bd72d597ed7eec95aa7de6
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Sep 14 11:45:34 2012 +0530

    glusterd, cli: Task id's for async tasks
    
    This patch introduces task-id's for async tasks like rebalance, remove-brick and
    replace-brick. An id is generated for each task when it is started and displayed
    to the user in cli output. The status of running tasks is also included in the
    output of "volume status" along with its id, so that a user can easily track the
    progress of an async task.
    
    Also,
     * added tests for this feature into the regression test suite.
     * added a python script for creating files, 'create-files.py', courtesy
       Vijaykumar Koppad (vkoppad@redhat.com) into the test suite.
    
    This patch reverts the revert commit 698deb33d731df6de84da8ae8ee4045e1543a168.
    
    BUG: 857330
    Change-Id: Id43d7cb629a38f47f733fbc18cb4c5f2f0327c7a
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4294
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit da7ca1efcf3a621c27f05d621715e57fdc5aa397
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Nov 28 22:29:36 2012 +0530

    protocol/server: Do not access key after GF_FREE in _delete_auth_opt()
    
    PROBLEMS:
    
    1.'key' becomes a dangling pointer after the first call to dict_del()
       returns, in _delete_auth_opt(). Therefore, the second call to
       fnmatch() is made with 'key' pointing to deallocated space.
    
    2. Also, the name _delete_auth_opt seems to suggest that the function
       is intended to match and delete "auth" options from the dictionary.
       But it winds up deleting all the options irrespective of whether
       the pattern match was successful or not. The same is true with
       _copy_auth_opt().
    
    FIX:
    
    Changed _delete_auth_opt() to delete the key ONLY if it matches either
    of the two patterns (auth.addr.*.allow and auth.addr.*.reject).
    Similarly, changed _copy_auth_opt() along the same lines.
    
    Change-Id: Ic8664e5a0a29cefe43cb59a27e32fbdbeac154b5
    BUG: 881062
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4337
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6b0d888e0729e7f7922d9b0a76dc27bae724e812
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Dec 19 16:40:11 2012 +0100

    tests: let basic/rpm.t cleanup after itself when not in DEBUG-mode
    
    The temporary working directory unders /var/tmp is not cleaned when
    debugging of the test is disabled. The logic should be the othetr way
    around.
    
    With this correction, the output while running is reduced as well.
    Nothing of the output contains useful information and clutters the
    testing output for no reason.
    
    BUG: 888743
    Change-Id: Id7616ad41873f61fd5d435b380f98068f313d5a6
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4340
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e8c75fd92974285be6aa9df542a1a8d7f6309160
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Dec 19 11:38:49 2012 +0530

    cli: Making the op-ret check for gluster peer probe --xml more robust.
    
    Change-Id: I75ca74a9e962ea47abbb2970e37dd182429b734b
    BUG: 879490
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4335
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 09e4d0861c8df392dc19dc6c9656dd33571f260d
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Dec 19 11:58:15 2012 +0530

    cli: Fixing the xml output in failure cases for gluster peer detach
    
    Change-Id: I87aadec1949fccadde396b95f31eeb6832e461b4
    BUG: 879494
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4336
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c9c0fe3f7d737b175dea3833071f3e54d2f412fa
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Dec 12 17:34:43 2012 +0530

    cli: Fixing the xml output in failure cases for gluster peer probe
    
    Change-Id: I9ebec995cbf47d9ced7140e37787e74ff9c63769
    BUG: 879490
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4301
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 020fc237765670432ae645ee104c4816d724c5ea
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 18 19:14:58 2012 +0530

    Tests: Print the actual, expected values for EXPECT
    
    Change-Id: I394d23c0ea15bd340041550660cc5def017b5f15
    BUG: 764966
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4327
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2dcde13e0d46c02a22ac3180c1e6d3e878c80f4a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 18 20:39:21 2012 +0530

    Tests: Redirect 'TEST' errors when it is expecting errors
    
    Change-Id: Iad2535eca7a58526d1a23cea9b7cf445a3846782
    BUG: 764966
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4329
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a402a3ab29f780662cc8498f44841f08d6fc29db
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Wed Dec 5 16:01:24 2012 +0530

    features/locks : Made changes to display brick information on clearing locks.
    
    Change-Id: I664614677bc887ce087bfca067e6e57f0d6b659d
    BUG: 824753
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4272
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 439166bd0abafa44d9a1d59931ee0957b1dd5382
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Dec 18 16:24:54 2012 +0530

    rpc-transport/rdma: use 24008 as default listen port.
    
    Change-Id: I021d5e2dbe3653d4303b64fe1ada0556cd4b7966
    BUG: 878883
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4323
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e0c7d9edb67c19eee9dc3a536bd3347d350082f0
Author: Anand Avati <avati@redhat.com>
Date:   Tue Dec 18 15:21:20 2012 -0800

    Revert "tests: Test afr mknod, create when one of the bricks is offline."
    
    This reverts commit 29ea7b5c23571e7d2449b3ccd582d3fe70371ea9
    
    Change-Id: I1ea8bab057fc215ef628b5762cd4958dd961830a
    Reviewed-on: http://review.gluster.org/4332
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 116c1ce428238b56d48f80f78aea8e6b303bd89c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Dec 18 16:36:16 2012 +0530

    glusterd: Fix initialisation of this
    
    Change-Id: I77f9b153d23ca5de1cb098cde5951e56f04d3a1c
    BUG: 873549
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4324
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 00cdd4134a44098f39cf9caea2177573c985a4af
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Dec 18 15:32:45 2012 +0100

    geo-rep: do not access BaseException.message in syncdutils
    
    http://www.python.org/dev/peps/pep-0352/ explains that the .message
    property of BaseException is being removed. Most of the other exception
    handlers access <Exception>.args[] which should be suitable for this
    case too.
    
    Change-Id: I1810450b78d2b3d7f8bd07f2beb02cbe9e2adecb
    BUG: 888346
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4328
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fe4c85958d55495bb6d15f607d63f5df0751e8d3
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 18 08:35:27 2012 +0530

    Tests: Print elapsed time per test file
    
    Change-Id: I61f7653bec357ec2b49d5b7719e564c31c2addbf
    BUG: 764966
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4320
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8967a4bb6f379509fed1f9509643cd99ccd1d2fc
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Dec 6 18:05:53 2012 +0530

    Tests: Add util function to get changelog xattr
    
    Change-Id: I3f6b79145e78b035950929e7ed8edb259525612f
    BUG: 864666
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4317
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4854e57edb1d17c8c924ad8c72e6c0e20788afa8
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Dec 17 14:59:25 2012 +0530

    cluster/afr: check for the -ve values returned from dict_serialized_length
    
    Change-Id: I9fa7744b02791180ccb93adef10c363a1b38aa31
    BUG: 838204
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4319
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b8a19d235a5d4fef572fe3a4ad5ccddaf207ee49
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Dec 12 15:36:26 2012 +0530

    tests: Added basic sanity test for all volume-status cmds
    
    Change-Id: I482a38ca9f67a5f4b4cbc96731cb68c3b442c2d4
    BUG: 764966
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4298
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cdcbc5bb3dfd2b447df0dff843d7774a1a463a09
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Dec 12 21:01:09 2012 -0500

    object-storage: only open file when requested
    
    Only open a file when the caller of the constructor indicates that it
    expects to have a file pointer to access in the "fp" field.
    
    Found by Junaid during review http://review.gluster.org/4284, Patch
    set 6.
    
    We also bump the version number to mark a line in the set of changes
    we want to perform a mini release with to double check for performance
    regressions.
    
    Change-Id: I13cf336bb519088890192ee111f4ece85a5982c4
    BUG: 886730
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4303
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a1f4a415374b4ff9afd847b7a1fbb4890c5e34a1
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Dec 13 22:44:27 2012 -0500

    object-storage: don't sort object list, not req'd
    
    The REST API for listing objects in a container does not require that the list
    of objects be sorted (the API for listing containers in an account does
    require it). Since we can have thousands and thousands of objects in a
    container, don't sort them when it is not required.
    
    Change-Id: I6939ef3fec3ea3814a49e3a3046273304889831c
    BUG: 887301
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4312
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 10ef8ef65a29d1ed7257c8649870b8b735fe0e10
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Dec 12 09:51:40 2012 -0500

    object-storage: do not list directory for delete
    
    Do not list the entire directory contents of the directory containing the file
    before deleting it. We have already verified the files existence constructing
    the Gluster_DiskFile object.
    
    This fixes a customer issue. See 885281
    (https://bugzilla.redhat.com/show_bug.cgi?id=885281).
    
    Change-Id: I4425c42af3e03624370c779d74b7f073e6eef024
    BUG: 885281
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4302
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1338ad168a4a468636909322dace9dc9f750dd13
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Dec 10 00:41:27 2012 -0500

    object-storage: apply upstream DiskFile refactor
    
    Apply the upstream DiskFile refactoring in ahead of its use to easiliy apply
    the temp file optimization.
    
    Change-Id: I2708733eed3d87759c70eb3d9e6cd74ef91d0c7b
    BUG: 876660
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4288
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2fd8af2b750c43c657df9d8f9ba6fd5c1ba1f437
Author: Peter Portante <peter.portante@redhat.com>
Date:   Sun Dec 9 23:56:28 2012 -0500

    object-storage: a set of cleanups to DiskFile
    
    Here are a set of cleanups for things noticed while working on the
    unit test coverage:
    
      * Remove unused constants, adding a constant for default disk chunk
        size
    
      * Document missing logger parameter from constructor
    
      * Add iter_hook paramater to constructor in anticipation of 1.7.4
        support
    
      * Add back meta_file field even though it is not used in our version
        of the constructor for paranoid compatibility
    
      * Remove is_valid field as it is not referenced anywhere, and it is
        not a field of the super class
    
      * Rename fields only used internally by DiskFile with leading
        underscores
    
      * Convert to using os.path.join() instead of hard coded '/'
        references
    
      * Use data_file field where possible
    
      * Assert that put_metadata() will only work when the file exists
    
      * Remove update_object() method since it is identical to
        put_metadata() and a direct write will suffice
    
      * Create the directory object only if it does not exist when a
        marker directory is requested
    
    Change-Id: If207fed4c0f423e6bd3232e4507f87de877057c4
    BUG: 876660
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4287
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 47e21afaaf192b03db69d8f204b3e33e5f9596cf
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Dec 7 16:39:37 2012 -0500

    object-storage: Initial unittest of DiskFile class
    
    If we had this ahead of time, we could have avoided the errors that
    were encountered leading to the fix-account-mapping fix (see
    http://review.gluster.org/4222).
    
    This represents 100% coverage of the DiskFile module, but the coverage
    report says otherwise, unfortunately. That is because the put() method
    invokes eventlets during the test run, and coverage is not able to
    accurately track the coverage lines properly. If one comments out the
    "tpool.execute()" line in DiskFile.put() the coverage report then
    reports 100% for the DiskFile module.
    
    Additionally, we changed DiskFile.put() in four ways that should not
    change its behavior:
    
      1. Comments were added to explain various code paths and mark
         potential issues / fixes
    
      2. It no longer returns a boolean value, matching the behavior of
         swift.obj.server.DiskFile.put()
    
      3. It no longer logs a message when it detects a directory that
         already exists, instead is raises an exception
    
         We believe this is okay because we cannot find a code path that
         would lead to his condition. As a result, it makes it easier to
         test all the code paths in that routine.
    
      4. It no longer logs a message when create_dir_object() fails, since
         create_dir_object() raises an exception on failure only
    
         We also modified create_dir_object() to not return a boolean as a
         result of the above behavior.
    
    Note that by implementing these tests up to this point we found three
    code paths that would have failed if encountered due to missing
    imports. We also made changes to the DiskFile module to make it a bit
    easier to test, also eliminating an extra stat system call when
    deleting directory objects.
    
    Change-Id: I3286de83c1ec7c5e8d6cab9354e1c4397cee7497
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4284
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit 5267406e5bcd8847bfe9565ee8d5ce13eeedd8cc
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Dec 12 17:54:57 2012 +0530

    cluster/dht: Add "afr.readdir-failover=off" option the rebalance process
    
    By failing over readdir (default behaviour), rebalance could get duplicate
    files, as readdir would re-read from offset 0. Rebalance should not attempt
    to migrate these files again.
    
    Additionally, we need to handle these cases as failure in rebalance crawl.
    
    No test case provided, as we cannot determine the read child in afr.
    
    Change-Id: If07508b4f92dacc17e0f695b48a866c7c66004be
    BUG: 859387
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4300
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e0daaed286894a4793f1427e938615022356b13f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Dec 15 03:45:18 2012 +0100

    NULL reference fix in gfid log
    
    On callbacks, make sure loc.inode is not NULL before priting its gfid.
    
    BUG: 815227
    Change-Id: Iab22b65217b5711ad8a92c83e335d9cb1a23841c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4313
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1b681f27e04ae3b74a461ef2601ac8c48ad6b1c3
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Dec 13 12:51:03 2012 +0530

    write-behind: fixes issues with iobuf length for large writes
    
    Use of an unsigned type in some calculations of size would lead to segmentation
    faults, if several large adjacent writes came in concurrently.
    
    Also, improves buffer allocation code to take the size required into account.
    
    Credits for the patch go to Amar.
    
    Change-Id: I8a09c52d49909e4ee8e7d4dcfa02ec33ea36a551
    BUG: 880948
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4307
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ef95b1ec0981e5f9859f5308e15ae33608bd6c29
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Dec 12 10:39:31 2012 +0530

    glusterd: fix peer probe cli response on error
    
    A peer probe with peers with differing op-versions or with unresolvable
    addresses would not reply to the cli with the error.
    This regression was caused by some changes introduced into
    glusterd_peer_rpc_notify(), which caused the cli reply path not to be executed.
    
    Change-Id: I0392b61e0a1dc22fa074529bdba0e357f938d013
    BUG: 885591
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4293
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 524dd0ef4c76d6432a8ff793fdb9322b9265aade
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Dec 12 23:05:20 2012 +0530

    cluster/afr: Make afr quorum options visible in volume set help
    
    Change-Id: I705d814f63094279532806db0e1e0fc2815fc107
    BUG: 884328
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4306
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e504e024d35fea46936dbebbe235a5090517af2d
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Dec 13 14:56:52 2012 +0530

    Tests: Added util function for option help presence
    
    Change-Id: Iec9816af11d5ecb743adecdf335e97267994f758
    BUG: 884328
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4305
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6dd85beaf95eee881a6c244c41e5fd5db17cdf9e
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Dec 13 15:55:40 2012 +0100

    Spurious reserved port warning fix
    
    reserved ports is a Linux specitic concept. Make no warnings for
    other systems.
    
    BUG: 815227
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Change-Id: I40037b9e99e7fcbdd0d153865ee7c2ef3733132e
    Reviewed-on: http://review.gluster.org/4308
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9a395d2db3a88d4ba479dfe0f5ad3769efee7f3a
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Dec 12 12:05:32 2012 +0100

    NetBSD MS_RDONLY portability build fix
    
    NetBSD uses MNT_RDONLY where Linux uses MS_RDONLY
    
    BUG: 815227
    Change-Id: I8d78831f07e575b215aabc46eaa66e5e277bda0e
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4299
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 06d4cced24f9854e3439f03a0c940adc5306de48
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Nov 6 10:13:07 2012 +0100

    build: include OCF resource agents by default and package them
    
    This change introduces a glusterfs-resource-agents sub-package that
    contains the Open Cluster Framework (OCF) Resource Agents (RA). It also
    changes the build infrastructure to include the RA by default, making
    them available for anyone who is interested in using them with a OCF
    compatible Hight-Availability solution like Pacemaker.
    
    Build the RPMs without RA:
    $ make dist && rpmbuild -ta --without ocf *.gz
    
    Build the RPMs with RA (default):
    $ make dist && rpmbuild -ta *.gz
    
    There is no need to run ./autogen.sh from within the .spec, the whole
    autotools infrastructure is included in the 'make dist' tarball already.
    
    This also adds a test-case which builds the rpms with mock for the
    latest two EPEL releases.
    
    Change-Id: I12ef5f30f466868825352376156fb4e56b135c58
    BUG: 869559
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4130
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6d58cb0476dc13198596603a9efd5014ebcb0c45
Author: Filip Pytloun <filip.pytloun@gooddata.com>
Date:   Mon Dec 10 14:41:10 2012 +0100

    RHEL init script: ability to overwrite options from sysconfig
    
    Change-Id: I15df0aef73e097a9ccfb00e2d4cae81d3a5a82fc
    BUG: 885739
    Signed-off-by: Filip Pytloun <filip.pytloun@gooddata.com>
    Reviewed-on: http://review.gluster.org/4290
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>

commit fef94c2acffc15159a1d5428c2f6c3b1a1bbee10
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Dec 11 18:31:40 2012 +0530

    glusterd: Set op-version for quorum options
    
    Change-Id: I693cc96c1dc7dc560c3c25698f08b846e8a48fca
    BUG: 839595
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4291
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5ec55a34c99c7b458f8be013863967c631be6730
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Nov 26 12:21:23 2012 +0530

    Added virt group file - template for 'group' set
    
    - This sample file contains the set of volume options
      that are associated with volumes that would be used to
      store VMs.
    
    - To enable the set of options present in this file one must
      do the following,
      - # cp extras/group-virt.example /var/lib/glusterd/groups/<group-name>
        # gluster volume set <volume-name> group <group-name>
    
    Change-Id: I8848d3d222ce114900db885aeef2f20c83ece28c
    BUG: 851237
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4232
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a86e36373b648ba51a286614cae889a0fe9d3f52
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Dec 11 13:31:12 2012 +0530

    gsyncd / geo-rep: do not start geo-rep if replace brick is in progress
    
    Change-Id: I9db32544ceb6f90c8231aaf40d722f6869a72614
    BUG: 861945
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4289
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cc9701d4f533bf7337d2925424e2498ab64fdf13
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 16 07:08:30 2012 +0530

    cluster/afr: Remember type of split-brain in inode-ctx
    
    Along with this change, fixed the race of setting the
    split-brain status in inode-ctx after unwinding the fop from
    self-heal in case of back-ground self-heal.
    
    Change-Id: Ifc829300df485f50f139443802e8b6dc7038b4ad
    BUG: 873962
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4198
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 179e7333740fe990cac6fc2e63fbace844b17b8d
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Nov 9 10:48:29 2012 +0530

    glusterd: log appropriate message when locking fails
    
    PROBLEM:
    
    When a transaction is already in progress, and the user tries to
    execute another glusterd operation, the second operation fails as
    glusterd fails to acquire lock. But to the user, a message like
    "Operation failed" does not give ample information about why the
    operation failed.
    
    FIX:
    
    Made glusterd_op_txn_begin use and initialise error string, which is
    needed to capture failure in the "lock" phase.
    
    Also made gd_sync_task_begin set error string appropriately when
    locking fails.
    
    In the process, I had to introduce error string in some glusterd_handle_*
    functions. And because I introduced error string in these handlers, I
    decided to also set them in places where these handlers could possibly
    fail.
    
    HOW I TESTED IT:
    
    For want of a better idea, I "commented out" the call to
    "glusterd_unlock", recompiled glusterd and ran two glusterd volume
    operations, one after the other. The second operation fails with the
    message "Another transaction is in progress. Please try again after
    sometime." as expected.
    
    The tests were performed on two volume ops : one of them
    synctask'ized (volume start) and the other NOT (volume create).
    
    Change-Id: Ia862972929872ae2f053707a544824d9cadc37be
    BUG: 873549
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4197
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 448b59e60b0ea5e085769283e89893176b86659f
Author: shishir gowda <sgowda@redhat.com>
Date:   Fri Dec 7 10:00:15 2012 +0530

    cluster/distribute: re-set layouts to prevent overlaps
    
    When subvols-per-directory option is used, with bricks addition/removal
    the layouts might get distributed to other subvols, which were not part
    of the layout before. We need to clean up layouts on old subvolumes, to
    prevent overlaps.
    
    Also, we need to make sure if layout-cnt is never less
    than subvolume-cnt.
    
    Change-Id: I00994a092ca0c99aedcc41bd9412d43460f88a04
    BUG: 884455
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4281
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1d87098f2df19af5a42ade6b305cbb01b85af8ea
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 11 19:58:47 2012 +0530

    Synchronize ls-loop with main-script
    
    Change-Id: If9a15e4c272baa28eee4f2fdfdf52b2e032b3a96
    BUG: 884452
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4292
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0c9f4d12a3b724afd61f60fed5e131335579ae5a
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Nov 14 15:43:56 2012 -0500

    object-storage: unit tests to 100% cover utils
    
    Change-Id: I2d540e16cc3d420b9bb88e6857e9795d56e34529
    BUG: 884327
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4225
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 29c23f20a6213affb646c322b7219a0f7c5c3dfc
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Nov 14 11:31:43 2012 -0500

    object-storage: use temp file optimization for pkl
    
    Override OpenStack Swift's swift.common.utils.write_pickle with our own
    implementation that uses the GlusterFS temporary file operation. A file name
    '.<FILENAME>.<RANDOM>' will hash to the same GlusterFS node as a file named
    '<FILENAME>', those avoiding a move of the file on a rename.
    
    This is part of the work needed to address BZ 876660
    (https://bugzilla.redhat.com/show_bug.cgi?id=876660).
    
    Change-Id: I1cb9f97f289ab2ca76ec9221366df74de08268bb
    BUG: 876660
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4224
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5886396d969a317cfd46e3da82543b0868325acc
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Nov 26 14:25:21 2012 +0530

    cli: fail vol set when value = empty string/string with all whitespaces
    
    PROBLEMS:
    
    a. 'volume set' operation accepts empty strings and strings containing
       all whitespaces for value. The result - subsequent attempts to start
       glusterd fail.
    
    b. 'volume set group' operation, when passed an empty string or string
       containing all spaces as value, fopens the wrong file.
    
    FIX:
    
    Made volume set parser in cli check for and invalidate value if its length
    is 0 after all the whitespaces have been stripped off.
    
    Change-Id: I6792ee1fe9452d8e25e1fd1eeb1b9981be3389f1
    BUG: 859927
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4246
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 845aba3ddcfaf7bcef283002b7b5bbf2075d4539
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Nov 23 10:33:12 2012 +0530

    glusterd: fail vol set when value = empty string/string with all whitespaces
    
    PROBLEM:
    
    'volume set' operation accepts empty strings and strings containing
    all whitespaces for value. The result - subsequent attempts to start
    glusterd fail.
    
    FIX:
    
    Added relevant checks in xlator_option_validate_* functions in options.c
    and in conversion functions in common-utils.c to invalidate wrong option
    values.
    
    Change-Id: I33232c6b42ab4fcce85c2d0e0b0da145fc9232c3
    BUG: 859927
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4033
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 07c40a2d149f9adfa4ce400051c1313127349192
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Dec 10 11:56:41 2012 +0530

    rpcsvc: Add an extra log message
    
    Adds an extra log message in rpcvsc_check_and_reply_error().
    Also, makes a small change in the test-script.
    
    Change-Id: I2b686e6fa86529cc4fbf0066df64057a9784b849
    BUG: 884452
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4285
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c399ca2fe3b81e19b9ff7ddd3f8bebe41179be48
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Dec 7 16:34:14 2012 -0500

    object-storage: Use "-dev" in the version string
    
    Currently, we have not solved the account mapping story entirely (we
    don't have a way to support more than one account to gluster volume in
    the mapping).
    
    As such, do not declare this as the final version.
    
    Also update the default RHS 2.0 spec file to "-3" for the release
    number to refer to the fact that we now have a working account mapping
    (see http://review.gluster.org/4222).
    
    Change-Id: Ia1cd0d18c1d7a7b20f732cc0ff867fecda30a7af
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4283
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5e937c4ed16a7658628a3ce6e5d39832ec516bac
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Dec 6 16:49:04 2012 +0530

    Fix xdr_to_generic success check
    
    This patch fixes the success check for xdr_to_generic function across the
    codebase.
    
    Also, cleans up the brick_op actors table in glusterfsd-mgmt.c to make sure that
    the actors are called directly by rpcsvc.
    
    Change-Id: I3086585f30c44f69f1bc83665f89e30025f76d3a
    BUG: 884452
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4278
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ff33ea5175b98e0df743ae3af7681fcf1e1e89eb
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Dec 6 16:46:57 2012 +0530

    rpcsvc: do a 'iobuf_ref()' on buffer while synctaskizing actor
    
    Starting rpc actors using synctask causes rpcsvc to return before the actor
    actually finishes its actions. This would cause the buffer to be unreffed by
    socket and be possibly reused, before the actor used it, leading to failures
    in the actor.
    This patch makes rpcsvc take a ref on the buffer when synctaskizing the actor
    and store it in the request structure, and then later unref it when the request
    structure is destroyed. This makes sure that the buffer is not reused before the
    actor has finished.
    
    Change-Id: I8f81e1fef8f3719db220471d2d8ffb8916958956
    BUG: 884452
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4277
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d0b0e59952222c186120c91518ccf94862a86f64
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Nov 27 15:13:15 2012 +0530

    cli: cmd history echoes the last command string word twice with --mode=script
    
    PROBLEM:
    
    When a gluster command is executed with --mode=script option
    enabled, the last word in the command string is echoed twice
    in command history.
    
      Example:
      [2012-12-03 05:29:16.083176]  : volume start dis dis : SUCCESS
    
    FIX:
    
    Terminate argv with NULL when the words are shifted after omitting
    "--mode=script" from it.
    
    Change-Id: I3a2623efe02e58c97c34554988938a9299425492
    BUG: 823081
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4255
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 66e34de1bef45dfd71ddccda57947fdb3c319640
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Dec 6 15:58:06 2012 +0530

    cli: add print-logdir option
    
    Change-Id: I92fe55d72aa597cbac57a51d2e15b35d2bcfef0e
    BUG: 823081
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4275
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7f9adbed0535f1d23a9b47a54d59c708b5ef5caa
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Nov 8 12:31:10 2012 -0500

    object-storage: enforce RPM package dependencies
    
    We now have access to openstack-swift-* packages that work with these sources
    so we can enforce the dependencies and what gets obsoleted.
    
    Change-Id: I83f442f3eb2424d176a2257f3498ed39eed32251
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4223
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a8d59075bfff1428c34ade2ad2e13fa51e3f6dbb
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Nov 21 16:42:15 2012 -0500

    object-storage: fix account mapping
    
    Fix the account mapping so that we always use what is provided by the request.
    
    With this fix, "/mnt/gluster-object/AUTH_ufo0" directory hierachies won't be
    created. But this fix does not restore the one-to-one account to gluster
    volume name mapping.
    
    When the user runs the /usr/bin/gluster-swift-gen-builders script, it still
    only allows one cluster volume, and that is the only volume that is used. So
    the account names are effectively ignored. A future set of changes will
    address that problem.
    
    Change-Id: I2df608de2f00fd356a09c500d49fe12cc1a0a574
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4222
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit efbc6349251ef32df8c5f670f550a0aaec8400f5
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Tue Dec 4 14:25:33 2012 +0530

    BD backend documentation update
    
    BUG: 805138
    Change-Id: I2b4eb3fb7bad59c5dadf7f22fcc4d2b2a783984a
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/4273
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 6801fc385d69a43d829b504adea299cce6057e25
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Tue Dec 4 14:25:33 2012 +0530

    man page update for BD backend xlator
    
    BUG: 805138
    Change-Id: Ifbceb329ba9039e6617d377c6b7fdb67d2383ddd
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/4274
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 128c8ceebb308029d4a4a3c58c31f5bbfe072d29
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Dec 5 12:20:28 2012 +0530

    cluster/afr: Empty string should not be default option val
    
    Glusterd does not allow empty string as default value. Changed
    afr option values to disallow empty string as value.
    
    Change-Id: I92a2d658907dbc6101e1139dd91f548acb5506f5
    BUG: 859927
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4271
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ddfef121a2254973ae72883112d1863052c6a580
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Thu Nov 29 17:17:49 2012 +0530

    Add util function to kill brick
    
    Change-Id: Ic67edd7edeaab16461c0009b49d951bfb4d79929
    BUG: 859927
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4270
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f656425f3412005fa0d2b47b774052d4bf726bd4
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Oct 22 16:07:29 2012 +0530

    protocol/client: log ENOENT errors in debug mode.
    
    Change-Id: I9b4ffb4a2f6be7ff5a0521f6582a9bc6f172e26c
    BUG: 872490
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4153
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b2f8d63a191ee01526c4ce90b5ab63bfe4b05655
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Nov 20 12:03:16 2012 +0530

    glusterd-hooks: Made hook runtime work with synctask'ized codepath(s)
    
    Change-Id: If66799c204483c3486a2b8ca842bb1b5f2e53997
    BUG: 877992
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4210
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee2813f440e9b6874eed93de307b8070c8953d5b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Nov 22 18:48:40 2012 +0530

    rpc: check the ctx->listener before accessing rpcsvc object
    
    Change-Id: I3c913d1fab07deb41eec05c5adc29a3964315b43
    BUG: 858487
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6d1607becc4fd84f7422730f37582164c86127d2
Author: Anand Avati <avati@redhat.com>
Date:   Tue Dec 4 16:00:36 2012 -0800

    Revert "glusterd: add "volume label" command"
    
    This reverts commit dad16a51ba7e6b1c57529423c57257dbce97ee93
    
    Test script causing "silent" failures during execution.
    
    Change-Id: I26dbb8ed22256071cb415cc3aff572ef8372600e
    Reviewed-on: http://review.gluster.org/4268
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 698deb33d731df6de84da8ae8ee4045e1543a168
Author: Anand Avati <avati@redhat.com>
Date:   Tue Dec 4 15:25:34 2012 -0800

    Revert "glusterd, cli: Task id's for async tasks"
    
    This reverts commit ed15521d4e5af2b52b78fd33711e7562f5273bc6
    
    Strangely, the test scripts are "silently" passing for failures too. Reverting patch for now.
    
    Change-Id: I802ec1634c7863dc373cc7dc4a47bd4baa72764e
    Reviewed-on: http://review.gluster.org/4267
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 676b8793b9a77babf0275ee78eeacfa7291a8c35
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Nov 27 12:34:18 2012 +0530

    cluster/afr: mark new entry changelog for create/mknod failures
    
    Problem:
    When create/mknod fails on some of the nodes, appropriate pending
    data/metadata changelogs are not assigned. This was not considered
    to be an issue because entry self-heal would do the assigning of
    appropriate changelog after creating new entries. But using
    the combination of rebalance and remove brick we can construct a
    case where a file with same name and gfid can be created in a dir
    with different data and link-to xattr without any changelog.
    
    Fix:
    When a create/mknod failure is observed mark the appropriate
    changelog on the new file created.
    
    Change-Id: I4c32cbf5594a13fb14deaf97ff30b2fff11cbfd6
    BUG: 858212
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4207
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d1bb60ad794dcf0fc8bf0cf8dc4ac13349d749d4
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 4 18:22:33 2012 +0530

    tests: Util commands for rebalance and afr child-up, shd up
    
    Change-Id: I175171524b750dff5b2ec0c11dc006d77123ecd5
    BUG: 858212
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4237
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0adc7fd1a76e6868a940cc0725c2f8d93cbb9f29
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 4 18:21:08 2012 +0530

    tests: Test afr mknod, create when one of the bricks is offline.
    
    Also tests the test case in bug 858212.
    
    Change-Id: I00e1c3f6142e9dab6868d8fd9ef66d39a7d3fae2
    BUG: 858212
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4238
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 98879ebdddd4ca77440defad6a73acf4fa1e75ab
Author: Anand Avati <avati@redhat.com>
Date:   Wed Sep 5 17:20:05 2012 -0700

    rpc-transport/socket: implement read-ahead of RPC headers
    
    This reduces the number of read() system calls on the socket to
    complete the full RPC fragment reading.
    
    Change-Id: I421a53af195ead4aad70e09e0172a61ad7912d83
    BUG: 821087
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3855
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 741766c708f2a246854584c064d63d3fba67be90
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Dec 3 10:45:04 2012 -0500

    afr: use data trylock mode in read/write self-heal trigger paths
    
    Self-heal data lock contention between clients and glustershd
    instances can lead to long wait and user response times if the
    client ends up pending its lock on glustershd self-heal of a large
    file. We have reports of guest vm instances going completely
    unresponsive during self-heal of virtual disk images.
    
    Optimize the read/write self-heal trigger codepath
    (i.e., afr_open_fd_fix()) to trylock for self-heal and skip the
    self-heal otherwise to minimize the likelihood of a running/active
    guest of competing with glustershd on arrival of a brick. Note that
    lock contention is still possible from the client (e.g., via
    lookup).
    
    BUG: 874045
    Change-Id: I406443c061ff6acd2a851179626b78352caa5c03
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4258
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e19bf891d5373e1660e666fecf6740062a375617
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Dec 3 10:41:49 2012 -0500

    afr: support self-heal data trylock mechanism
    
    Introduce a block flag to support an optional blocking or
    non-blocking mode in the self-heal data locking mechanism. All
    callers are modified to use blocking mode, which is the current
    default behavior (no change in behavior is introduced by this
    commit).
    
    BUG: 874045
    Change-Id: Ib7ff9984578fa11de4e3b6981508100cdddd37cd
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4257
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7b5a21707edbbee1940f7cd3d05043bec998e51a
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Sep 14 11:45:34 2012 +0530

    glusterd, cli: Task id's for async tasks
    
    This patch introduces task-id's for async tasks like rebalance, remove-brick and
    replace-brick. An id is generated for each task when it is started and displayed
    to the user in cli output. The status of running tasks is also included in the
    output of "volume status" along with its id, so that a user can easily track the
    progress of an async task.
    
    Also,
     * added tests for this feature into the regression test suite.
     * added a python script for creating files, 'create-files.py', courtesy
       Vijaykumar Koppad (vkoppad@redhat.com) into the test suite.
    
    Change-Id: Ib0c0d12e0d6c8f72ace48d303d7ff3102157e876
    BUG: 857330
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/3942
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6a1b89c0c4221b13c21e66a048e08e4eb95de7bd
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Dec 4 15:39:45 2012 +0530

    storage/posix: if create returns EXIST, donot set gfid/xattrs
    
    Change-Id: I9f2b75b10bde428d36d6516aa09c18e590d17ed9
    BUG: 864801
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4265
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c1868c52725bbf972ed4f774fe6745201fe2f25e
Author: Brian Foster <bfoster@redhat.com>
Date:   Tue Dec 4 10:17:46 2012 -0500

    tests/bug-830665: use the default H0
    
    The use of 'hostname -s' leads to a failure on my VM due to
    attempting to create the volume on localhost. Use the default H0
    value.
    
    BUG: 830665
    Change-Id: Icf23c89d2387fe747aca6d99af12f7d4e1e3fbf0
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4266
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6b969c84b847927433bbe8466090d1c7970ea37c
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Dec 3 15:50:39 2012 -0500

    afr: make flush non-transactional
    
    Flush is historically a transaction to ensure all previous writes
    were complete. This is no longer required as write-behind has
    learned to make flush a barrier operation (re: conversation w/
    Avati).
    
    Flush taking a full file lock causes VMs running on afr volumes
    to stall when a migration occurs and self-heal is in progress.
    Make afr_flush() a non-transactional operation.
    
    BUG: 874045
    Change-Id: If2db83823e280c86b1b29b41361eed7081601632
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4261
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 924702de358160b2536138c073d293b76512838a
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Dec 3 12:16:28 2012 -0500

    glusterd: add "volume label" command
    
    This command is necessary when the local disk/filesystem containing a brick
    is unexpectedly lost and then recreated.  Since 961bc80c, trying to start
    the brick will fail because the trusted.glusterfs.volume-id xattr is
    missing, and if we can't start it then we can't replace-brick or self-heal
    so we're stuck in a permanently degraded state.  This command provides a
    way to label the empty brick with the proper volume ID so that further
    repair actions become possible.
    
    Change-Id: I1c1e5273a018b7a6b8d0852daf111ddc3fddfdc2
    BUG: 860297
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4259
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 86b01a278b55b19adefe9625e586252a5c75b474
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Nov 26 16:36:42 2012 -0500

    dht: support auto-NUFA option
    
    Many people have asked for behavior like the old NUFA, which builds and
    seems to run but was previously impossible to enable/configure in a
    standard way.  This change allows NUFA to be enabled instead of DHT from
    the command line, with automatic selection of the local subvolume on each
    host.
    
    Change-Id: I0065938db3922361fd450a6c1919a4cbbf6f202e
    BUG: 882278
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4234
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 48a1738467c2328a9f8d0fce09b64f286ef533e0
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Nov 29 21:43:23 2012 +0530

    fix memory leaks
    
    * write-behind: free the inode context in wb_forget
    * distribute: in readdirp callback put the allocated context to the inode
    * distribute: check if the layout is NULL before accessing it in layout_unref
    
    Change-Id: I7698f81b85b99d06bf6b01fc1a6e51e1593b5e27
    BUG: 790709
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4250
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 01217e4e16677b13c7febc66e4e4ca3f0025739b
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Nov 29 23:05:17 2012 +0100

    geo-rep / gsyncd: play nicely with peer multiplexing when setting a checkpoint
    
    The gsyncd invocation that instruments the "geo-rep config" command is
    multiplexed over peers to ensure the uniformity of configuration.
    In general, that works well, but checkpoint setting is a special case,
    because (unlike other instances of config-set) it is logged (as recording
    of checkpoint events is part of the feature).
    
    Problem is that the path components leading to the log file are
    created only on the original node, where gsyncd was started.
    Therefore the logging attempt will fail on the other nodes.
    
    Fix: ignore if opening the logfile on behalf of checkpoint setting
    fails with ENOENT.
    
    Change-Id: I677f3f081bf4b9e3ba4d25d58979d86931e6beb4
    BUG: 881997
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/4248
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Christos Triantafyllidis <ctrianta@redhat.com>
    Reviewed-by: Christos Triantafyllidis <ctrianta@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 555f1cfe7d5d36ee93efbe8c5585eb323d4b7185
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Dec 4 14:38:54 2012 +0530

    libglusterfs: fix unused-but-set-variable warning
    
    Change-Id: Ie152169a70eaec9554382b39d43ae7ffa04f041c
    BUG: 762989
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4264
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c6bb978f93e7e2974b0c8568af09b72bfbc35987
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Dec 4 12:44:22 2012 +0530

    tests: Introduce new test primitive EXPECT_WITHIN
    
    Introduces a new test primitive EXPECT_WITHIN with syntax,
            EXPECT_WITHIN <timeout in seconds> <expected output> <command>
    which runs the given command every second and compares its output with the
    expected output, till the timeout occurs.
    
    Change-Id: I91c6de157e5d33fffafe532ceba84e2a9223356f
    BUG: 857330
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4263
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit bb5382208696196aead94c011b3f9fa13a04da68
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Dec 3 06:40:11 2012 -0500

    nfs: do opendir for "naked" readdirp to force self-heal checks
    
    Instead of an opendir, the first thing the Linux NFS client usually sends
    us is a readdirp at offset zero, effectively bypassing our self-heal checks.
    Detect this condition and issue our own opendir to compensate.
    
    Change-Id: I69463370abd6235d705bf80b8c77fae4a61096ae
    BUG: 830665
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4067
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4675796361f19a9f1f897465587737391d94a235
Author: JulesWang <w.jq0722@gmail.com>
Date:   Tue Dec 4 10:12:30 2012 +0800

    cli: fix incorrect xml output of brick tag.
    
    Incorrect output:
    <brick>
      <brick>
      </brick>
    </brick>
    
    Expected output:
    <brick></brick>
    <brick></brick>
    
    Change-Id: I40c30feda4e6f3f1ec5da4122f8965b61c511ae6
    BUG: 880993
    Signed-off-by: JulesWang <w.jq0722@gmail.com>
    Reviewed-on: http://review.gluster.org/4262
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Kaushal M <kaushal@redhat.com>

commit fa1607ea596802d3d3177d775eeecb0f0e5d496f
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Oct 25 17:06:31 2012 +0530

    socket,rdma: before binding to any port check if it is a reserved port
    
    * The list of ports which are reserved is obtained by reading the file
      /proc/sys/net/ipv4/ip_local_reserved_ports.
    
    Change-Id: I3a832f53efbb79dd719b34a30cbaf28269f25816
    BUG: 762989
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4131
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3cade0a1e9dfc641e5b6db2f044af9f50ff604d6
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Dec 3 12:12:57 2012 +0530

    cli: Fix build when libxml2 is absent
    
    Also added a note to the top of cli-xml-output.c, explaining the style of coding
    to followed when adding code to it.
    
    Change-Id: I7f90a9c075adb49a9e071771d136b6f01ea68d11
    BUG: 882780
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4256
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f1ddc077a31671ff547efa205d86c1b8ebd3797a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 3 10:54:21 2012 +0530

    tests: Perform self-heal in foreground
    
    Change-Id: Ic9fa7ffe9cd704740e920b66162950f0c0322e67
    BUG: 865825
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4253
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2fd342a0c21d761d73bfee782717accbce819f24
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Nov 5 21:42:22 2012 +0530

    cluster/afr: Provide option to disable readdir failover
    
    In a replica pair unlike files, directories may not have their
    content in same order, so readdir for same (offset, size) may
    not give same entries on both the sobvolumes of replica pair.
    Switching over from one subvolume to another may not be a good
    idea sometimes. It may lead to duplicate entries or fewer entries
    or both. This patch provides a way to disable readdir-failover
    so that applications like rebalance can retry if they want to.
    
    Change-Id: I2b23eb224a2e84016a561362932613ac824c11a0
    BUG: 859387
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4159
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 07c3801808db787e6c0cf0b2bf60a7ab62bc38b7
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Mon Dec 3 10:50:29 2012 +0530

    tests: Test the exit status of touch
    
    Change-Id: I4fd52d6b54c5bcf16298c3a9ec98a12fea8df957
    BUG: 860663
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4254
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cb506f9b91fb20c46a1f7bdea940672cb8c0fdf7
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Fri Nov 30 12:11:02 2012 +0530

    encryption/rot-13: Cleanup trailing whitespaces
    
    Change-Id: I9f5c81ca4320b6e73087023102dff6e3911b5095
    BUG: 764890
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4251
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit ab52eb7d9f6f4e8e95c3bd15fe757c6e789cc29d
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Thu Sep 27 17:59:23 2012 +0530

    core: remove ref/unref while unwinding frames
    
    Change-Id: Ib196ffdf8122a9510cc7c5953303a6e730091302
    BUG: 853373
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4062
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 692c0e98da8613c004f24ccf7084fc517ba8b4e4
Author: Anand Avati <avati@redhat.com>
Date:   Mon Nov 26 20:02:18 2012 -0800

    build: make dist to capture current build tree state
    
    ChangeLog will now hold the 'git log' and 'git diff' against
    the HEAD of the tree from which 'make dist' was issued.
    
    Change-Id: I0b5b27de66b02d733612470a8c79d65f0b560fa1
    BUG: 764890
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4235
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a20b52d029cc98e4ffdb4d6b187e02ffdfcc9137
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Nov 28 15:43:17 2012 +0530

    cluster/afr: Added descriptions to afr options
    
    Change-Id: I4aef1c79743ee08b62e04d7b709f3e8c6b9dc56a
    BUG: 881517
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4244
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit bde0e142632854b8c74a4df0427662c024dd29c1
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Sep 26 18:09:33 2012 +0530

    cluster/dht: fail fix-layout if any of the subvol is down
    
    If any subvolume is down, and a layout is re-written and hash
    values change, entry names in the downed subvol can be reused
    in the other subvol which got the same hash range. when the
    downed subvol is brought back up, duplicate entried might appear
    
    Also separated handling of ENOSPC and ENOTCONN error.
    
    Change-Id: I5ed93990425a4cee70df2dab7c7c119fdc87ad56
    BUG: 860663
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4000
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c7baba53635c78b899a165d1de6b6982bb520325
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Nov 30 11:28:54 2012 +0530

    tests/README: add a note about usage of 'mount -t glusterfs'
    
    Change-Id: Ic9e02c34e8d7c8eb4a18c459d2a8899d85a59189
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/4249
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 1bfcabdb61920ed4156ac24799cdd846bec64233
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Tue Nov 27 12:33:06 2012 +0530

    mgmt/glusterd: Consider nodesvc to be running after online
    
    Definition of online in the message below is that the
    RPC_CLNT_CONNECT event arrives for the nfs/self-heal-daemon process.
    
    For automated tests, sometimes the script needs to wait until
    self-heal-daemon comes online, so that the relevant
    commands can be executed. Gluster volume status before this change
    printed whether the self-heal-daemon is running or not based on the
    lock availability on the pidfile. But there is a small window where
    the lock on pid file is present but the process is still not
    online. So the commands that were depending on this kept failing in
    the test script.
    
    Change-Id: I0e44e18b08d7b653d34fa170c1f187d91c888cd9
    BUG: 858212
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4236
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3d83e6c42ee0d43208a7b1ebb0595ee7c43bb066
Author: Pete Zaitcev <zaitcev@kotori.zaitcev.us>
Date:   Sun Nov 25 22:57:06 2012 -0700

    Replace "ssh foo gluster" with "gluster --remote-host=foo"
    
    With the current lack of authentication, there is no security
    improvement with passwordless ssh replaced. However, it is more
    convenient to install UFO if you do not have to generate ssh
    keys every time.
    
    There is a downside the gluster-server RPM becomes required.
    
    BUG: 880050
    Change-Id: I04f4ad666ac96713055723bd432131a4db325b4f
    Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-on: http://review.gluster.org/4231
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 01cd59506e8021b4adb7fe8b4877a7e60beb13f6
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Oct 18 15:40:02 2012 +0530

    cluster/dht: Heal dir uid/gid
    
    Identify mismatching uid/gid in lookup, and trigger a syncop
    heal. uid/gid of subvol with latest ctime is trusted (local->prebuf).
    
    Change-Id: Ib5c4bc438e7f4b1f33080e73593f40f400e997f0
    BUG: 862967
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/3964
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9864b3a8e46c2813a5793ce7ac7d3029ed324828
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Nov 29 14:06:30 2012 +0530

    debug/error-gen : Added dumpops to print private values of error-gen in the statedump.
    
    Change-Id: I4aa299bd8ecdaa82cdfdc2d97a89fcddcbb25930
    BUG: 767095
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4245
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 48d749dda368149a8f05ea5c09cab93f58835d0b
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:08 2012 +0530

    BD Backend: Test Cases
    
    BUG: 805138
    Change-Id: I04c1b68cf02d55d1481137fe6bb2386c2ba958f3
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/4145
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 983d290f7b36fea580ed9337bdc15e8f0f6f5bb3
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:07 2012 +0530

    BD Backend: CLI to create a full/linked clone of a image
    
    A new CLI command added to support cloning/snapshotting of a LV device
    
    Syntax is:
    $ gluster bd clone <volname>:<vg>/<lv> <newlv>
    
    $ gluster bd snapshot <volname>:<vg>/<lv> <snap_lv> <size>
    
    BUG: 805138
    Change-Id: Idc2ac14525a3998329c742bf85a06326cac8cd54
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3719
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 3c72850e8d00f0cf35ae054136be076a394e08e9
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:07 2012 +0530

    BD Backend: CLI commands to create/delete image
    
    Cli commands  added to create/delete a LV device.
    
    The following command creates lv in a given vg.
    $ gluster bd create <volname>:<vgname>/<lvname> <size>
    
    The following command deletes lv in a given vg.
    $ gluster bd delete <volname>:<vgname>/<lvname>
    
    BUG: 805138
    Change-Id: Ie4e100eca14e2ee32cf2bb4dd064b17230d673bf
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3718
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ca796eba11a3f965bfbaa9bbffb5ef00c9bbb7ad
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:07 2012 +0530

    BD Backend: Volume creation support
    
    A new parameter type is added to volume create command. To use BD xlator
    one has to specify following argument in addition to normal volume
    create
    
    device vg brick:<VG-NAME>
    
    for example,
    $ gluster volume create lv_volume device vg host:/vg1
    
    Changes from previous version
    
    * New type 'backend' added to volinfo structure to differentiate between
      posix and bd xlator
    * Most of the volume related commands are updated to handle BD xlator,
      like add-brick, heal-brick etc refuse to work when volume is BD xlator
      type
    * Only one VG (ie brick) can be specified for BD xlator during volume
      creation
    * volume info shows VG info if its of type BD xlator
    
    BUG: 805138
    Change-Id: I0ff90aca04840c71f364fabb0ab43ce33f9278ce
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3717
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit b7840704c2095ad64f56da8d37fbae26db3a81ac
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:07 2012 +0530

    BD Backend: Rename LV
    
    BUG: 805138
    Change-Id: I18c64435e66ede148c58d412a0639f45554209c8
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3558
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit a41567c137d2e1fca241d962205234c956ebae4f
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:06 2012 +0530

    BD Backend: Extend size of file (LV)
    
    Use the truncate interface to increase the size of file (LV).
    
    FIXME: lvm2 library does not provide any interface to extend size of LV.
    So lvextend binary is forked to achieve the same
    
    BUG: 805138
    Change-Id: If4c0bd112364437b89e091b7f53764b8e6e01a28
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3557
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6df32359a25dca53c9e809a70847ed45893a3ad0
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:06 2012 +0530

    BD Backend: Full clone and linked clone
    
    FIXME: There is no lvm2 api to create a LV snapshot. This patch forks
    lvcreate binary to achieve the same.
    
    BUG: 805138
    Change-Id: Icdbead16f797162fe6a31a672b619ce6a0391235
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9707e4486fc0ad90ffb4635bf0470df59822dc01
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:06 2012 +0530

    BD Backend: Unlink a file (LV)
    
    BUG: 805138
    Change-Id: I53d8a4bc09cbd9766ba937887cadd7ac475017ba
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3555
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b1d35091afdc0192ece2a9a079f12be1f8486767
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:06 2012 +0530

    BD Backend: Create a new file (LV)
    
    Add support to create a new file (LV) under a directory (VG). By
    default created LV is of one logical extent size.
    
    Also setattr/fsetattr interfaces added as part of this patch.
    
    BUG: 805138
    Change-Id: I51752b707b3766ab277d623ce574537346f376c9
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3554
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 61d196aa9cd049dfb9209db820bfe9a5e0b36399
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:06 2012 +0530

    BD Backend: Write support
    
    BUG: 805138
    Change-Id: I4a672fc58ee61dead99e0adcd46d7771f3fdd730
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3553
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2cc1fbf020798edee97d9f626a767ecec5deca69
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:05 2012 +0530

    BD Backend: Open,read and related calls support for LV
    
    BUG: 805138
    Change-Id: I811c179d4244342537dbedb8a24fd2ec628942ed
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3552
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit ee968619cf936f0e25299beb1996abc27ed3dc72
Author: M. Mohan Kumar <mohan@in.ibm.com>
Date:   Thu Nov 29 21:46:05 2012 +0530

    xlators: Add Block Device(BD) backend translator
    
    Add a new server storage xlator 'bd mapper'. Intention of this xlator is
    to add block device backend support to gluster. It exports block devices
    as regular files to the gluster client.
    
    The immediate goal of this translator is to use logical volumes to
    store VM images and expose them as files to QEMU/KVM.
    
    Given Volume group is represented as directory and its logical
    volumes as files.
    
    By exporting LUNs/LVs as regular files, it becomes possible to:
    * Associate each VM to a LV/LUN
    * Use file system commands like cp to take copy of VM images
    * Create linked clones of VM  by doing LV snapshot at server
    side
    * Implement thin provisioning by developing a qcow2 translator
    
    As of now this patchset maps only logical volumes. BD Mapper volume
    file specifies which Volume group to export to the client. BD xlator
    exports the volume group as a directory and all logical volumes under that
    as regular files.
    
    BD xlator uses lvm2-devel APIs for getting the list of Volume Groups
    and Logical Volumes in the system.
    
    The eventual goal of this work is to support thin provisioning,
    snapshot, copy etc of VM images seamlessly in glusterfs storage environment
    
    BUG: 805138
    Change-Id: I13b69d39d7fd199c101c8e9e4f2cf10772bdc3dd
    Signed-off-by: M. Mohan Kumar <mohan@in.ibm.com>
    Reviewed-on: http://review.gluster.org/3551
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit b90b2c17b6b678e5aa1440a62b7588f8b7c52947
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Nov 1 09:33:53 2012 -0400

    afr: send unique dict_t instances to replicas in self-heal fxattrop
    
    afr_sh_data_fxattrop() currently allocates and sends a single xattr
    dict_t instance to each replica. The callback codepath references
    the returned object in the self-heal in-memory state for the
    particular replica. If storage/posix is in the same address-space
    (i.e., running a single glusterfs client with a fuse->afr->posix
    graph), the same object is modified and returned for each child,
    causing corrupted in-memory state and afr xattrs.
    
    Allocate and send independent xattr dict_t's for each replica. This
    allows self-heal to work correctly in a single address-space
    graph.
    
    BUG: 868478
    Change-Id: I42832e85b5d1abb6098c28944c717e129300109e
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4149
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0314f16ec59d8c22597c8c14b53a473b736b8b1f
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Nov 1 09:46:12 2012 -0400

    afr: handle short writes in afr_writev_wind and self-heal to avoid corruption
    
    The current failure to handle short writes on writev fops leaves
    us open to file corruption. A short write on a user request is
    ignored and leaves replicas in an inconsistent state. A short write
    during a self-heal is ignored and incorrectly marks the files as
    consistent if the heal completes.
    
    Modify user writev handling to return the best case return value
    from each of the replicas. Short writes that occur relative to this
    value are marked as failed and will require a heal. Modify
    self-heal to set an error on a short write and abort the heal.
    
    BUG: 853690
    Change-Id: I18b30f58702326249230eeebb361b29e40b535f5
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4150
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c85a3eee54b4028573c905829d5b46c0b6512c56
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Nov 27 12:05:28 2012 +0530

    cluster/dht: send ACCESS call on dir to first_up_subvol if cached is down
    
    Change-Id: I4f518a969bbe3a11075e7c9ae10bd21bf059d5f3
    BUG: 867253
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/4240
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f8c19b4c6af34b96747881bcb85cddb87484f08e
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Oct 30 15:54:05 2012 +0100

    geo-rep / gsyncd,glusterd: do not hardcode socket path
    
    ... in gsyncd python code. Indeed, use the configuration
    mechanism to set it suitably from glusterd.
    
    Change-Id: I9fe2088b14d28588d1e64fe892740cc5755b8365
    BUG: 868877
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/4143
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fbfcb0ad2aac73c2b5ab8950770c1184352bbf24
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Aug 23 15:32:33 2012 +0530

    glusterd, cli: implement gluster system uuid reset command
    
    A commonly faced problem among glusterfs users is: after a fresh
    installation of glusterfs in a virtual machine, the VM image is
    cloned to make multiple instances of the server. This breaks
    glusterd because right after glusterfs installation on the first
    boot glusterd would have created the node UUID and this gets
    inherited into the clone. The result is wierd behavior at the time
    of peer probe where glusterd does not (yet) deal with UUID
    collisions in a user friendly way.
    
    To handle it gluster peer reset command is implemented which upon
    execution changes the uuid of local glusterd.
    
    Change-Id: If207dd2ad93ab94ef1a3253f409c21c442975f87
    BUG: 811493
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3637
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fadc34e7ce82f9e7f98f20e995cb2bbf71a00b20
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Nov 26 13:09:44 2012 +0530

    glusterd: Protected conf->xprt_list racy access.
    
    - epoll on RPCSVC_EVENT_ACCEPT would add corresponding xprt
      onto the xprt_list. Concurrently, synctask thread (volume op)
      would call into glusterd_fetchspec_notify which iterates on
      the xprt_list. Added a mutex to protect such a racy access of
      the list.
    
    Change-Id: Idc51b4bdb1c814dfab7790e1c899d6977f7640f2
    BUG: 878873
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4241
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5f88d4c1b036228ca4036e854d533f0b2fc3adc1
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Fri Nov 23 14:26:10 2012 +0530

    libgfapi: "tcp" is documented as the valid transport type instead of "socket".
    
    Change-Id: I066e9be7755a535f385c102cdd1822adeda7f319
    BUG: 860203
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4226
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 15bf92d53c72774e2fd7aba146644a2e460e543f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Nov 26 17:44:36 2012 +0100

    geo-replication: catch select.error on select()
    
    tailer() in resource.py does not correctly catch exceptions from
    select(). select() can raise an instance of the select.error class and
    the current expression only catches ValueError (and the instance will
    have reference called selecterror).
    
    The geo-rep log contains a call trace like this:
    > E [syncdutils:190:log_raise_exception] <top>: FAIL:
    > Traceback (most recent call last):
    > File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 216, in twrap
    > tf(*aa)
    > File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 123, in tailer
    > poe, _ ,_ = select([po.stderr for po in errstore], [], [], 1)
    > File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 276, in select
    > return eintr_wrap(oselect.select, oselect.error, *a)
    > File "/usr/libexec/glusterfs/python/syncdaemon/syncdutils.py", line 269, in eintr_wrap
    > return func(*a)
    > error: (9, 'Bad file descriptor')
    
    BUG: 880308
    Change-Id: I2babe42918950d0e9ddb3d08fa21aa3548ccf7c5
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4233
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c6570de4d5ba090cfb4bb9d2b0390f2526ed0636
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Nov 19 16:29:44 2012 +0530

    protocol/client: add an option to filter O_DIRECT flag in open
    
    with the option, the idea is all client-side caching will be disabled,
    where as on server side process, the fd will be treated as a regular
    fd, thus helping the performance better.
    
    "gluster volume set <VOLNAME> remote-dio enable" would set
    this option in client protocol volumes.
    
    Change-Id: Id2255a167137f8fee20849513e3011274dc829b4
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 845213
    Reviewed-on: http://review.gluster.org/4206
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cee1b62d013cfb164f2a014919721c920c06514a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Oct 30 10:23:20 2012 +0530

    glusterd: volume-sync shouldn't validate volume-id
    
    - volume sync would overwrite volume information on local node
      from the hostname supplied. This warning is provided to the user.
    
    - Also fixed a double free in volume-sync handler.
    
    Change-Id: Icc68d9d563fb50ca58d5880921f063692e1e6882
    BUG: 865700
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4188
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8fd4aa74149411ab739e2075e1f7c0709b8a0342
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 17 16:10:28 2012 +0530

    features/locks: implement fgetxattr and fsetxattr
    
    implement xattrs for GF_XATTR_LOCKINFO_KEY, which will be used
    for posix-locks migration from old to new graph after a switch.
    
    fgetxattr (fd, GF_XATTR_LOCKINFO_KEY) will return a dict.
    This dict has a serialized dict stored for key
    GF_XATTR_LOCKINFO_KEY. This serialized dict in turn has fdnum
    value of locks acquired on this fd with modified pathinfo
    (containing hostname and base directory components) as key.
    
    fsetxattr (newfd, GF_XATTR_LOCKINFO_KEY, dict) has following
    semantics. dict can be the result of a previous fgetxattr with
    GF_XATTR_LOCKINFO_KEY. In that case, a dict_get on dict
    constructed using serialized buffer is done on modified pathinfo
    as key. If a value is got, that value is treated as fdnum and for
    every lock l on newfd->inode we do,
          if (l->fdnum == fdnum) {
             l->fdnum = fd_fdnum (newfd);
             l->transport = <connection identifier of connection on which fsetxattr came>;
          }
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: I73a8f43aa0b6077bc19f8de52205ba748f2d8bbe
    BUG: 808400
    Reviewed-on: http://review.gluster.org/4120
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit dbc0968db04f09a57b3a2165803f8103c98c9acb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Nov 20 12:30:13 2012 +0530

    mount/fuse: add test cases for lock migration
    
    Change-Id: I1a48c63387c7803b36584070fd8f3684ccb696b1
    BUG: 808400
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4209
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 228f0ea02b259b2a80edc9f92c2508635085f871
Author: Raghavendra <raghavendra@gluster.com>
Date:   Tue Oct 23 13:16:42 2012 +0530

    cluster/stripe: handle GF_XATTR_LOCKINFO_KEY in f(get)(set)xattr
    
    Change-Id: I4463006a7f54c05e757d877c56e1330fd91aec45
    BUG: 808400
    Signed-off-by: Raghavendra <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4125
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6c3eebad5c52fde2c198232066b270a5f3996910
Author: Raghavendra <raghavendra@gluster.com>
Date:   Tue Oct 23 13:15:15 2012 +0530

    libglusterfs/mem-pool: implement gf_memdup
    
    Change-Id: I1d7a1e7418f424fe08c041d562098b947c01580f
    BUG: 808400
    Signed-off-by: Raghavendra <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4124
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit da0972232e97e761a839d9db9bbe7a04c6ff13e9
Author: Raghavendra <raghavendra@gluster.com>
Date:   Tue Oct 23 11:32:33 2012 +0530

    cluster/distribute: send getxattr on LOCKINFO to only cached subvolumes.
    
    lk is sent to only cached subvolume. Hence there is no point in
    sending LOCKINFO to other children (even in case of directories).
    
    Change-Id: Ia20fc358dfa84cee9a52d1f613564ff6f25aa0c9
    BUG: 808400
    Signed-off-by: Raghavendra <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4123
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6f4a9f43e4d18c42f5eb8db65f364620a85c7fd2
Author: Raghavendra <raghavendra@gluster.com>
Date:   Mon Oct 22 17:20:26 2012 +0530

    mount/fuse: migrate posix locks after a graph-switch
    
    Each posix-lock is associated with an fd and a transport.
    After a graph switch, this lock-state has to be associated
    with new fd and transport corresponding to new client graph.
    
    Change-Id: Ia0855e15600c85ef902bf612738f7d96557145be
    BUG: 808400
    Signed-off-by: Raghavendra <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4122
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 44b8fbe7537d0203649919cd6d1a62a69c4f7802
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 18 10:20:09 2012 +0530

    cluster/afr: handle GF_XATTR_LOCKINFO_KEY appropriately.
    
    values from all children need to be aggregated into a dictionary
    and serialized buffer of this aggregated dictionary has to be
    the value of GF_XATTR_LOCKINFO_KEY in the dict sent as a result of
    fgetxattr.
    
    Change-Id: Ie877f7c637c07feaee4c44d7ef86aa967a17b7e7
    BUG: 808400
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4121
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0e3261903b1ed624137263d3386cf7a6b6736f33
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 28 11:50:18 2012 +0530

    tests/bug-865825: turn stat-prefetch off before doing any afr self-heal
                      related tests.
    
    Change-Id: I5c45bb4f4d4aa59965c6dda34ab884071bef9c6f
    BUG: 865825
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4242
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9e2aeea9242c04228049003bf8f878ea38af76da
Author: Avra Sengupta <asengupt@redhat.com>
Date:   Thu Nov 22 16:02:47 2012 +0530

    cli: XML output for "gluster volume geo-replication status"
    
    Change-Id: I1a64bd5eb9b1040a2a2d9b97bfe9cc756835596e
    BUG: 864506
    Signed-off-by: Avra Sengupta <asengupt@redhat.com>
    Reviewed-on: http://review.gluster.org/4227
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 22f0be5a608bdfc5d2bc3d37f19689367966a6dd
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Nov 27 16:13:53 2012 +0530

    tests: Replace mount -t glusterfs with glusterfs -s
    
    Change-Id: I9aa9bd1efb9ae56caec0fee596b3f21ca496f66e
    BUG: 863068
    Signed-off-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-on: http://review.gluster.org/4239
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit 2389042e64ae20f88bd0e53d1fe879dc2856b6c4
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Oct 12 10:18:58 2012 -0400

    replicate: don't stop checking xattrs because one was absent
    
    The functional issue is described by the subject line.  This patch also
    addresses several efficiency/structure issues, such as...
    
    * Calling dict_set_ptr once for each txn type, instead of once overall.
    
    * Calling afr_index_for_transaction_type once per iteration instead of
      once per call (or better yet zero since the conversion is unnecessary).
    
    * Implementation of inner functions in a different file than their one
      caller, creating a spurious header-file dependency.
    
    Change-Id: I29e0df906a820533b66b9ced73e015dfe77267d2
    BUG: 865825
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4070
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2b1bf891f550487d2c05fc9e377f0d15d4a08d0a
Author: Venkatesh Somyajula <vsomyaju@redhat.com>
Date:   Fri Nov 23 18:12:52 2012 +0530

    Cluster/afr: Fix output for gluster volume heal vn info healed
    
    Problem:
    Whenever gluster volume heal vol full command is executed, the entries
    stored in the circual buffer for sh->healed are added in the dictionary
    in the _crawl_post_sh_action function irrespective of whether actual self heal
    (due to non-zero values in chage log) takes place or not.
    
    Fix:
    Value of key (actual-sh-done) will be set to 1 whenever self heal takes place
    due to non-zero change log values and if for some FOP self heal daemon finds
    that no self heal required after examining the pending matrix, the value will
    be 0.
    
    Change-Id: I11fd0b9ee76759af17c5bca6bfafbaf66bcaacbc
    BUG: 863068
    Signed-off-by: Venkatesh Somyajula <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4181
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b6bf52bdcc78c7a803430ebcd7be367fbbf9cc4d
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Thu Nov 15 14:20:39 2012 +0530

    nfs: avoid blocking lock calls in statedump code
    
    This change replaces LOCK () with TRY_LOCK () in
    nlm statedump code.
    
    Change-Id: I28c558b68854cf08c3a8190a00d6e3d507317628
    BUG: 843819
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4193
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 419e5835ec183a73560ad65a94fb036495c4f386
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Nov 24 07:23:53 2012 +0530

    tests: Add volume set tests for quorum
    
    Change-Id: I83e0408d8fd01afe990ebf634a8a09ea0b8ea54d
    BUG: 839595
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4229
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 016480eb8221a403e5224653e57c401fcb61acc0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Fri Nov 23 22:19:32 2012 +0530

    tests: Add volume utils in a new file
    
    Change-Id: Ie78d24ca466d4bddc5c0727ed8ed51707e1f2a34
    BUG: 839595
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4228
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7c23a94516c5dd21536c259f323a3cc113fdfa0d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Nov 6 12:18:24 2012 +0530

    mgmt/glusterd: Implementation of server-side quorum
    
    Feature-page:
    http://www.gluster.org/community/documentation/index.php/Features/Server-quorum
    
    Change-Id: I747b222519e71022462343d2c1bcd3626e1f9c86
    BUG: 839595
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3811
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 76a4afec6e03d15cb442e819f6fe7b94d6f9f487
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Nov 6 12:19:47 2012 +0530

    libglusterfs: Implement float percentage
    
    Change-Id: Ia7ea63471f0bbd74686873f5f6f183475880f1a0
    BUG: 839595
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/4162
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6dee0e3d99dd3423edc6ad2981733fac3ef8c67d
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Nov 16 13:48:58 2012 -0500

    glusterd: fix use of undefined realpath(3) result
    
    Change-Id: Ic50ae192c99cece25cd63f2277fb440fca5f0b04
    BUG: 877522
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4201
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 2fad4eb4efb13d5bf79b4425afa9ce3f87c13e85
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat Nov 17 11:59:39 2012 +0530

    glusterd: brick path availability check only for local bricks
    
    Change-Id: Ica50fb92608f5fd75f8887e0718177faf29d31c4
    BUG: 877522
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4203
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4a8f751b7c85b80ed3cbb5c1292200ebfaa49747
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Nov 19 14:28:20 2012 -0500

    socket: fix double-free when ssl_setup_connection fails
    
    Change-Id: I893b166da28f4c21e582ed477399c4bc0c1d20e1
    BUG: 877903
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4208
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d5999c107a89dda38e8107ab8660130e052418b6
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Nov 20 15:17:06 2012 +0530

    cli: XML output for "geo-replication <VOL> {start|stop}"
    
    Change-Id: I8d2213cc00deb458fb765b848d0e3452574cc98f
    BUG: 864499
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4217
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 14693665710677dfc809af2db199be3ecadacb18
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Nov 2 09:41:33 2012 +0100

    Use more portable mkstemp() instead fo mkostemp()
    
    mkostemp() with O_CREAT|O_EXCL|O_RDWR|O_TRUNC|O_APPEND is mkstemp()
    and mkstemp() is available on more systems than mkostemp()
    
    NULL-commit to cause jankins ro rebuild
    
    BUG: 764655
    Change-Id: I6ee0f635d3699bd70b0963b24af07bd7d5c2dc58
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4152
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f35d192b5f4a35b30fdd5dfe21429f93f645c5ba
Author: Pete Zaitcev <zaitcev@kotori.zaitcev.us>
Date:   Wed Nov 21 17:33:04 2012 -0700

    object-storage: Add a sorted list comparison to test
    
    After the commit b0cb7aaf for bz#870589, which adds 2 tarballs
    with layout patterns, Swift tests sometimes fail (depending on the
    kind of filesystem they are running at and the phase of the moon).
    
    As pattern tarball is unpacked, the underlying filesystem is free
    to return directory listings in any order, and straightforward use
    of '==' operator fails. As it turns out, one of the two comparisons
    had set() applied to the list already. So, add it to the other one.
    
    BUG: 874390
    Change-Id: I02de99593b9567a13076113d58e242b079fde002
    Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-on: http://review.gluster.org/4165
    Reviewed-by: Peter Portante <pportant@redhat.com>
    Tested-by: Peter Portante <pportant@redhat.com>

commit 1f64e5e3dd7f871e112ad9d3e9fae3cc5e15fd88
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Nov 21 12:06:26 2012 +0530

    gsyncd / geo-rep: include hostname in status cmd
    
    Including hostname of the node where geo-rep start was
    initiated from. This helps any consumers of the status
    command to identify and possibly issue commands on those
    node(s).
    
    Change-Id: I005083878a3a4794da3b7f3f7d2cc9d28f004e3f
    BUG: 858218
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/4218
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a64a0d89d5256386f6773709477aea87823e2e68
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Nov 8 12:31:10 2012 -0500

    object-storage: del 1.4.8 ref from dir hierarchy
    
    Remove the "swift/1.4.8" directory from the hierarchy, replacing it with "ufo".
    
    Change-Id: I60ba171182d7402a2193616c1c95c90cd2ead5bc
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4200
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 94ddaecadbb12c5e67617553b067554a657980a1
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Nov 15 17:36:13 2012 -0500

    Don't ignore all files that match (*o|*la|*lo)
    
    This has been hiding files in my tree, in particular, new directories that end
    with an "o". I am guessing here that these are really trying to just ignore
    .o, .la and .lo files.
    
    Change-Id: Ic438ca5c43188a63e9840512825f9ba05c359eeb
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4195
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d8fbd9ec2a674c5bfa80d975dfb328674053f82f
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Oct 22 19:19:50 2012 -0400

    perf/io-threads: least-rate-limit least priority throttling
    
    The 'least-rate-limit' io-threads translator option enables
    throttling of least priority operations. This is initially intended
    as a debug/diagnostic tool for users who might experience
    overloaded servers via background activity (i.e., self-heal).
    
    least-rate-limit defines the maximum number of least priority
    operations the io-threads translator will dequeue in one second.
    If the specified rate limit is met, the worker threads sleep for
    the minimal amount of time before the next least priority operation
    becomes available (or until a new request arrives).
    
    The requests/second metric is generic and relative to a variety of
    factors involved with a background operation (server, storage,
    etc.). The most recent measured rate ("cached least rate") is added
    to the io-threads state dump content (kill -USR1) to serve as a
    reference point to throttle background activity under particular
    conditions.
    
    Change-Id: I80f2282992137d57b1becaa5c6ae3858c066862a
    BUG: 853680
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4119
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2e40e0f42807f23d447d7fae67c1e2f834904c53
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Nov 21 14:35:10 2012 +0530

    cluster/afr: check transaction type for eager-lock after it is set
    
    Problem:
    Eager locking lk-owner decision is taken before transaction
    type is set. Default transaction type is DATA so all transactions
    are treated as DATA transactions at the time of eager-locking
    decision.
    
    Fix:
    Move the code that takes lk-owner decision after the transaction
    type is set.
    
    Test:
    Checked that the transaction type is set properly in gdb at
    the time of the lk-owner decision.
    
    Change-Id: I7607c7ff4f88c7ced5416a1cddb6586cf45d88f9
    BUG: 861335
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4220
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 79eb7c62e27d01d14b3053f9ecd14d6b964bac76
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Oct 29 12:41:03 2012 +0530

    libglusterfs: implement gf_strndup
    
    Change-Id: Ifb7bf22e8cf4ad1faccf7999c36919693912093f
    BUG: 808400
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4135
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bc3253b070ee9bf44360e258046a07c5630661bc
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Tue Nov 20 23:18:10 2012 +0530

    Put _check_key_is_zero_filled outside _xattrop_index_action
    
    Change-Id: Ifb89a3a911213b2816a540a104558e7c3c13e23a
    BUG: 874498
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4182
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 961bc80c7aeedaa0bdc580f9f08d1c8a2a0992cd
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Sat Nov 17 01:36:13 2012 +0530

    posix: Fix volume will not start if brick has no volume-id attribute
    
    Problem:
    If the extended attribute (trusted.glusterfs.volume-id) of a brick  is
    absent and <gluster volume start volume-name> command is executed then
    curretly volume-id from the volume file will be set as an extended attribute of
    the brick and volume will get started.
    But if setup is such that brick is used as a mount point and before
    executing the <gluster volume start volume-name> command, nothing is mounted on
    the brick then all the file operations will take place at the brick but actual
    intention of the brick is to be used as mount point only.
    
    FIX:
    Do not start the volume if extended attribute (trusted.glusterfs.volume-id)
    is set absent.
    
    Change-Id: Id2462d87d6087e97e0b8831512fdbc3595f7078b
    BUG: 860297
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4202
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 65cc8cb531456de934e8ba3175430e8fcb304ca5
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sun Oct 28 07:31:20 2012 +0530

    storage/posix: Make rchecksum O_DIRECT friendly
    
    Problem:
    When posix-aio is enabled to perform aio fd is set with O_DIRECT
    whenever possible in read, writev fops. Rchecksum does not take
    this into account. If either offset/size/memory-buf passed to
    pread in rchecksum fop is not aligned, pread fails with EINVAL.
    
    Fix:
    Before doing pread necessary O_DIRECT manipulation is done when
    aio is enabled. Memory buffer passed to pread is now page-aligned.
    
    Test:
    1) Create replica volume with aio enabled.
    2) dd if=/dev/urandom of=a bs=1M count=1
    3) kill one of the bricks in the replica pair
    4) dd if=/dev/urandom of=a bs=1M count=1
    5) bring back the brick. Self-heal succeeds after the change.
    
    The test above checks both rchecksum, writev fops that were
    changed in this patch.
    
    Change-Id: I186099a2854d4864c5b48086ab7bc5f1a7b27313
    BUG: 866459
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4134
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 18851652c9e3d566fd82fac91d67792d7c221f6b
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Nov 1 10:53:43 2012 -0400

    debug/error-gen: add the short write pseudo-error
    
    Add a separate enum for pseudo-errors in the debug/error-gen
    translator and include a short write error. The short write error
    causes writev requests to return with some non-error value less
    than the size of the write request.
    
    BUG: 853690
    Change-Id: I50b7d328386a8b78d03ce91b4c2ec83e0d32c9aa
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.org/4148
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit c0885f7dbbbf8fb9d9f813617e13c7ba59a6acef
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 23 09:18:52 2012 -0400

    tests: make _EXPECT handle more cases
    
    First issue is that _EXPECT wasn't handling args with spaces correctly. This
    was fixed by enclosing the entire expected-value expression in double quotes
    with a simple backslash escape for the end-of-line dollar sign.
    
    Second issue is that we were throwing away potentially useful debug
    information. Fixed by using egrep's -q option to suppress output, and
    eliminating redirections so that we can see any stderr output related to a
    script error.
    
    Change-Id: Ide3f49558dcece55bd90cad50b1ffc572592f11c
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4126
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit f90ca96f540ce1765ae25baea6205f998b005035
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 24 07:08:08 2012 +0530

    cluster/dht: dump the layout information of directories only
    
    testcase:
    The changes are for removing gf_log from statedump related sections in dht and
    using pthread_mutex_trylock in statedump sections. Changes are internal. So
    tests were done by attaching gdb to the process and executing by manually
    changing the values of some of the pointers.
    
    Change-Id: I41fa76c1812b462cb76f5bbf2fd14de080e73895
    BUG: 843822
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4117
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2100ebd982d09950a84a0d6ae25770ca17e6689c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Nov 19 12:01:09 2012 +0530

    nfs: after resolving the entry use the linked inode instead of old inode
    
    Change-Id: I56add0c3c852d096ec70a0e35610f46c2d12980a
    BUG: 877885
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4205
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 28994167a7fbbb35370b515eb72a9aaf49f58ac4
Author: Anand Avati <avati@redhat.com>
Date:   Sat Oct 20 00:14:13 2012 -0700

    fuse-bridge: fix posix-only configuration
    
    Recent changes in fuse-resolver had broken the use case of having
    a trivial configuration with only storage/posix translator. Fix
    it and include a regression test to avoid breakage in the future.
    
    Change-Id: I85cbcac4b5c2d3517dd03fd3dc6d07610697981b
    BUG: 868478
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4114
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 6149303d55c1a240ac878bbee7928cc7eb071447
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 31 14:13:14 2012 +0530

    glusterfsd: log all command line options in log file
    
    this would help support to make sure the glusterfs process
    received all the required options, as not all the options set with
    'mount -t glusterfs' will be visible with 'mount' command.
    
    also one need not bother checking 'ps ax | grep gluster' for getting
    all the details of the command.
    
    Change-Id: Idf635904074bc0892abb6b707ff91149e92a33e3
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 871063
    Reviewed-on: http://review.gluster.org/4146
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 702b2912970e7cc19416aff7d3696d15977efc2f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Nov 9 14:43:38 2012 +0100

    fuse: handle mountflags properly
    
    The internal mount API had no access to the generic
    mountflags used by mount(2).
    
    Thus the "ro" mount option that needs to be passed down to mount(2) as
    as a mountflag was incorrectly mangled into the fuse-specific mount
    parameter string (cf. http://review.gluster.com/655).
    
    This commit fixes the internal API and the "ro" issue. It also adds a
    check for the "rw" and "ro" mount options in tests/basic/mount.t.
    
    Thanks to Csaba Henk (csaba@) for suggestions and proposing an updated
    patch.
    
    Change-Id: I7f7bf49ae44d148f5c16f10736a0e412fb8f5e67
    BUG: 853895
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4163
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 474d3e08313acb74633a22e970326fb98b9122d3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Oct 17 22:20:47 2012 +0530

    glusterfsd-mgmt: make brick-ops work in synctask
    
    this way, the main epoll thread is freed up to serve other requests.
    
    Change-Id: Iecf68aceb8bd84433d0f9fcd98d96c734a4cc134
    BUG: 842955
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/4096
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cfe51eb7ff5d5d61c1cf9ad1588c7a3e8250736b
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Nov 7 12:55:08 2012 +0530

    features/locks: fcntl(3) on F_GETLK must return first conflicting lock
    
    - Added test program, getlk_owner.c to capture the bug when regressed.
    
    Change-Id: Ic2a0f6fa8d094c0f2e9f4a6febd278d4a2948223
    BUG: 869724
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4164
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0f87154a4ba93fc042c4308a6f51a5b6582802ac
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Oct 15 23:15:18 2012 +0530

    glusterd: copy peers that participate in volume xaction
    
    - To avoid working with a mutable list of peers in
      the scope of a volume xaction.
    
    Change-Id: I228ae96bccdce127026eff8320adb37b17e2cc6a
    BUG: 862834
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4113
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cb884f7eac134866ca47701d3208055acecbf9a0
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Nov 2 16:09:13 2012 +0530

    nfs: do not change root inode if enable-ino32 is set
    
    When a user sets nfs.enable-ino32 on,
    the root inode, which must be 1, is jumbled during
    hashing of the gfid into 32 bits.
    This patch avoids doing that, and returns inode of 1
    for the root inode.
    
    Change-Id: Ib65f2660998a95e1059be32bc298485c5cbe52df
    BUG: 864222
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4154
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1129698a490ac9266b1f613fababdf524e11f887
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Nov 8 01:16:56 2012 -0500

    object-storage: final changes to remove swift diff
    
    Final set of changes to remove the diffs carried to make UFO work with
    OpenStack Swift. The code is now a complete layering on top of OpenStack Swift
    where we either "monkey patch" or subclass as necessary.
    
    See BZ 870589 (https://bugzilla.redhat.com/show_bug.cgi?id=870589).
    
    There are a lot of changes here due for the most part to rearranging the
    directory hierarchy to have create a proper python module hierarchy under the
    "gluster" namespace. Plugin references have been removed. The differences that
    used to be in the swift.diff file are now replaced with server implementations
    for account, container, object, and proxy that subclass the swift versions.
    
    Additionally, the plugins/conf directory has been moved to the "etc"
    directory, and the plugins/bin directory promoted a level.
    
    Unit tests pass.
    
    A new setup.py file is provided so that the install process can use it for
    creating all the necessary python install infrastructure (eggs and paste
    support).
    
    A new RPM spec file is provided which to properly install the new code, and
    the sample configuration files have been modified to reference the new python
    egg.
    
    Change-Id: I4316c1b66dca80f847fe9b0d583174689c175599
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4180
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit e8d95655d5e73462723799d20e59bc4f21bdf973
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Nov 7 12:37:26 2012 -0500

    object-storage: refactor to use swift devices
    
    Refactor code to use the devices configuration file setting for account,
    container, and object servers, dropping mount_path from the fs.conf file, and
    constructing new account, container and object server rings.
    
    This removes the next to last set of diffs in the swift diff file. See BZ
    870589 (https://bugzilla.redhat.com/show_bug.cgi?id=870589).
    
    The key to the change is the dropping of the pre-built account, container and
    object rings, instead providing a script that will generate them for the user
    given the gluster volume name in use. In addition, we override the Swift
    check_mount() method and replace it with Gluster's which attempts to
    "auto-mount" if it is not already mounted.
    
    The following is an enumeration of the changes contained in this refactoring:
    
        * The refactoring to override the Swift check_mount() involved condensing
          a lot of code, removing redundancies and simplifying methods across a
          number of modules
    
        * Drop checking the mount point in the low level DiskDir, DiskAccount and
          DiskFile objects now that Swift's normal mount checking is used, and
          enable it by default in the template configuration file
    
        * Add missing get_container_timestamp() method for DiskAccount objects
    
        * Fix the plugin RPM spec file to provide the new ring builders, and while
          we were at it, finally fix the over-writing of the configuration files
          on install
    
        * Bug fixes
    
            * The monkey patched version of check_object_creation was not working
              correctly due to a missing import of HTTPBadRequest and a bad
              reference to validate_obj_name_component()
    
            * Only have the utils module import the plugins constraints module for
              the side effect of monkey patching if gluster is enabled
    
            * Removed the db_file.db file in the tree since it is created on the
              fly
    
            * Updated 2011 copyright notices to 2012
    
    Change-Id: I8f4454576b1423021c9bbf3c36176f8db51e62c0
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4179
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit 05cc14c2d301934d79ee37cd36f498247b7a9886
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Nov 2 10:49:14 2012 -0400

    object-storage: make proper refs to module vars
    
    Not sure how this worked before this, but mount_ip and mount_path do not
    exist, their uppercase versions do.
    
    Change-Id: I53e9b550991d17b5541ed4ada5f1bc9b3cb1b8b1
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4178
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b696fc0e595d14404d3659bf15069addf3cf95f6
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Oct 31 20:28:42 2012 -0400

    object-storage: reduce diffs, bury metadata update
    
    Further reduce the diffs we have to carry by moving the Gluster specific
    metadata stored when we create an object to the DiskFile class's put() method.
    
    Change-Id: I8cef5412627d3ddfdadbf78ef947e067db5bf620
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4177
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit ffc7618270522bb4550d29a11a81ab5aeca42d99
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Oct 31 17:16:07 2012 -0400

    object-storage: swift-diff removal: hide obj only
    
    Towards swift-diff removal: hide object_only behavior inside DiskDir class
    objects. See BZ 870589 (https://bugzilla.redhat.com/show_bug.cgi?id=870589)
    
    One of the last few reasons for having the swift diff is the need to update
    the account and container information from the file system when the
    configuration is not for object-only use (meaning, other updates to the file
    system can come from clients other than UFO, which means UFO currently has to
    generate the necessary metadata for each request instead of caching it).
    
    This change moves that logic into the DiskDir class methods so that the
    container and account server code does not have to track that.
    
    Change-Id: If0970c77c72245facd09c2035083e681d6d80303
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4176
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit 89aff74157857517bedfe10ef2da0a7f2a7b28a7
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Oct 31 06:51:54 2012 -0400

    object-storage: fix trailing whitespace
    
    Change-Id: Ib3c671e693c2c332af98a593ca14c42c36f5ca76
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4175
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit d2040d1213d0486d36ddb8280a232ef64d81a481
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 20:51:12 2012 -0400

    object-storage: remove the device and part params
    
    Change-Id: I60b4b1b976ad8359ba072d5d0ed6a8dd2087a738
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4174
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 6bd81f29d9cb6dc7131115629b9b6ca03dff2c4d
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 20:43:02 2012 -0400

    object-storage: only update metadata that changes
    
    See BZ 868120 (https://bugzilla.redhat.com/show_bug.cgi?id=868120)
    
    Change-Id: Ia7f5562cff32eee30c5ca18652d5d9a5a2b18bf4
    BUG: 868120
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4173
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 7066b4925dd51bdcf0f1eb2db6f455499e69c48b
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 20:19:07 2012 -0400

    object-storage: DiskAccount subclassing of DiskDir
    
    Changes to make DiskAccount subclass DiskDir complete. This change helps
    reduce the diffs ahead of further refactoring. Note that DiskDir initializes
    all the same fields as DiskAccount, plus a few more, and ends up reading the
    metadata properly, while only adding a couple of fields not used for account
    purposes.
    
    This change also passes the account controller's logger for use by the
    DiskAccount class.
    
    Along the way we:
    
        * Remove the redundant update_account() method in the DiskCommon base
          class, since the update_container() method in DiskDir performs the exact
          same functionality
    
        * Remove the initialization of variables ahead of assignments in two
          cases, and also move the initialization of the list variables closer to
          where they are used
    
        * Collapse the imports from swift.plugins.utils into one statement
    
        * Use a temporary directory for the db_file.db when we find ourselves in a
          unit test environment
    
    Change-Id: I4dc59b416a66393adfe0ed32c7a62c79731d70c0
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4172
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Tested-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit 92fed1249752ff1feb6cd0b004e9550ba666a7b0
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 19:49:42 2012 -0400

    object-storage: fix bad refs to check_acct_exists
    
    Fix bad references to check_account_exists: this is a module local method, not
    provided by Glusterfs. Not sure how we missed this. More unit tests would
    help.
    
    Also added the ability to run the Swift tree unit tests with gluster
    artificially enabled to test as many code paths as possible ahead of full
    functional tests.
    
    Change-Id: Iaf696d34db8f841c887f03569e65321fca8894d1
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4171
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit f3daa0bda0aa429cbf148fcef41cf34564828e4d
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 19:47:57 2012 -0400

    object-storage: fix bad refs to REMOTE_CLUSTER
    
    Change-Id: I07cd997ef9a98645a87792632f9dd612928678b7
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4170
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit ee28eaee7f75853d99eeee1773805cbcaabe32c6
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 15:47:09 2012 -0400

    object-storage: rename self.name to self.container
    
    Minor refactoring ahead of further diffs to add clarity to the code.
    
    Rename the DiskDir field from "name" to "container", which is what it is.
    
    Along the way, add a note regarding the one-to-one mapping of account name to
    gluster volume name, and fix the get_info() container method documentation to
    list all the dictionary keys returned.
    
    Change-Id: I659e1a9a070c16671287f17a170f9d77198534e7
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4169
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 7fa7029dafa5b0da42651ffcd88e84915741c1b8
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 15:19:05 2012 -0400

    object-storage: unused parameter cleanup & handl'n
    
    Unsed parameter cleanup and handling changes. The device and partition
    parameters are not used. The account parameter is used in place of the device
    parameter. Rather than just making the device parameter reference the value of
    the account parameter, we just don't use the device parameter at all and make
    references to account. We also remove the device_path field from the class
    since it is unused.
    
    Additionally, we assert that we have a logger since the rest of the relies on
    that fact.
    
    Change-Id: Iea556319744ab4f729b1ce23d987650a164749db
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4168
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Tested-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit a1fd8c85eabc40b401e116285240af0b367e167f
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 14:56:55 2012 -0400

    object-storage: add missing docs for params
    
    Add missing documentation for constructor parameters.
    
    Change-Id: I3a656cd22f6a2a61e0b4d563c75c2f7fe68d3c54
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4167
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit a6b51d60b07dea9ce5ef4cfb2ea9c2c2f7ecfe41
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 29 14:39:44 2012 -0400

    object-storage: minor code cleanups
    
    Apply a few minor code cleanups to help reduce future refactoring diffs.
    
      * Remove extra lines between methods so that all methods are consistently
        spaced by one line
    
      * Remove unused field meta_file
    
      * Add missing documentation for uid and gid parameters
    
    Change-Id: I0a38eb06680eb0709edfaa1828d09657823f778e
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4166
    Reviewed-by: Pete Zaitcev <zaitcev@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b6386c8fe34c7940357a916d3c715b278a144122
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Nov 14 14:58:09 2012 -0500

    build: fix missing include (from missing backslash)
    
    Caused by 1c4cb5237701bb138f9cce29036773086253f839.
    
    Change-Id: I9574b2316af6a5a0d59b5d80578016dfd5fc1ac9
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4191
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4e1c921636dbe3c8ec083a29a2508c6092ba8641
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Mon Nov 12 09:58:02 2012 -0500

    NFS is picking up geo-rep's already open (read-only) file descriptor
    
    Add anonymous member to fd_t and use it instead of over-loading pid for
    geo-rep and self heal
    
    Change-Id: I4d6b29a044a8ed4b8f69ff6e3f35ee227739b2af
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    BUG: 874272
    Reviewed-on: http://review.gluster.org/4185
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 1c4cb5237701bb138f9cce29036773086253f839
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Wed Sep 12 12:36:49 2012 +0530

    ACLv3 - Access Control Lists V3
    
    Change-Id: I43e544d6cdeac5e3880141477461e7c22cbf6e91
    BUG: 847622
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.org/4045
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ca666417f3e6f500ec75cb7389497e2f5c4bc6e6
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Nov 5 10:43:12 2012 +0530

    glusterd: Add missing options to vme table.
    
    Change-Id: Ifa48cb2c26dbbabe619e1bfbd41d9ecdce1150aa
    BUG: 814534
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/4155
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d55acadd85e37ee4bf56da36640a5bf8a0e2f66e
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Nov 5 16:39:37 2012 +0530

    nfs: resolve parent inode during inode_loc_fill
    
    This commit resolves the parent inode in nfs_inode_loc_fill
    if the inode has a resolved path.
    
    Change-Id: If407c91c246b0b9f3349cedae0baec8bd6831d10
    BUG: 872923
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.org/4157
    Reviewed-by: Krishna Srinivas <krishna.zresearch@gmail.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 128514fcb7f4943e6c97139f873db68a009ae893
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Nov 5 11:24:57 2012 -0500

    socket: fix SSL breakage from re/connect handling changes
    
    Change-Id: Ia1f5aeec5628b61cad8a10a9cdc6d9f1c67ec653
    BUG: 873367
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4158
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 009c728b401287ef9aa9ee4a7fb509ccc5baa156
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Oct 15 17:04:29 2012 +0530

    glusterd: Fixed glusterd crash in volume add-brick
    
    PROBLEMS:
    
    a. glusterd crashes when add-brick operation fails on the machine other
       than the originator, owing to double free done on op_errstr:
       once in glusterd_op_begin_synctask and once through a dict unref on
       req_dict in gd_sync_task_begin.
    
    b. In gd_sync_task_begin, there's no need to place the error string
       in the dictionary, when it is never retrieved and used elsewhere.
    
    c. Command execution status is not logged into .cmd_log_history.
    
    FIX:
    
    For (a) and (b): Knocked off code that places the error string in req_dict.
    That way, both the problems are solved.
    
    For (b), passed op_ctx to glusterd_op_send_cli_response as it is needed to
    extract the command string before logging.
    
    Change-Id: I549a07ba5e31332b691a8cacd1ab32c2673810ba
    BUG: 862834
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4102
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7997d36ce3d37b0b3ac33c1529f03969442b6595
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Aug 9 17:09:19 2012 +0530

    xlator/fuse: integrate fuse with event-history
    
    use event-history framework for saving and dumping (on necessity)
    important xlator specific information.
    
    Tests:
    Included the regression testcase.
    
    Change-Id: I6c0532e9ffe0b624286cdc4d2637b1bd2c0579e0
    BUG: 858215
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Signed-off-by: root <root@thinkpad.(none)>
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3925
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0d9a38bb576beac24d0694633a79cff7e8c11a9f
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Oct 29 16:21:24 2012 +0530

    features/quota: Failure of quota commands if the dir-name contains ':' in it
    
    PROBLEM:
    The first colon in the limit string is used to separate the path and the
    limit-value. The ':' in the path was the source of problem.
    
    FIX:
    Search for the last colon and separate based on the same.
    
    Added regression test.
    TEST:
    Create and set quota on directories with names containing ':' in start, middle
    and end.
    
    Change-Id: I363c8ad4cbfd02c23fc73974bef9aa8bc362d29c
    BUG: 848251
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4137
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b0cb7aaf04eff033a329e017a8628c84a62e33cd
Author: Peter Portante <peter.portante@redhat.com>
Date:   Sat Oct 27 00:10:47 2012 -0400

    object-storage: remove glusterfs filter requirement
    
    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=870589
    
    Remove the Glusterfs object, transforming it into a module providing module
    data fields (like swift.common.constraints) and module methods for
    mounting/unmounting and access the gluster volume information. As a result, we
    can then remove the glusterfs filter from the pipeline since we no longer need
    to provide the Glusterfs object through all the plugin code paths.
    
    This is one more step closer to removing our dependency on modifying the Swift
    code directly with these changes. See It is also the first step to acknowledging
    that we are not a plugin, but a layering on top of Swift.
    
    The major piece of work here is based on a recognition that the
    plugins/Glusterfs.py module provided a Glusterfs class that instantiated
    instances of an object that always contained the same data from the
    configuration file. The fields of such an object were not being changed and
    were treated as read-only in all cases. Since the object's data was the same
    for all instantiations there was no need to pass the data from the glusterfs
    filter all the way down into the bowels of the Gluster_DiskFile and DiskDir
    objects.
    
    Taking advantage of the nature of that data, we now just have those fields
    read into module variables, and change the Glusterfs object methods into
    module level functions. Much of the changes result from the consequence of
    making that switch from object to module.
    
    Here are a few other changes made along the way:
    
      * Bump the release numbers in the spec files in recognition of these changes
    
      * Create the plugins/fs_utils.py module so that the methods in the
        plugins/Glusterfs.py module don't have to include plugins/utils.py, which
        would create a circular dependency
    
        * Note that this dependency comes from methods in plugins/utils.py
          depending on the module level constructs in plugins/Glusterfs.py so that
          we only store those values in one place
    
      * Changed plugins/DiskDir.py:DiskDir class to not check for, and/or
        optionally create, the /etc/swift/db_file.db at run time, just create it a
        module init time
    
      * Removed the duplicate strip_obj_storage_path() from plugins/DiskDir.py and
        utils.py and move it to the Glusterfs module
    
      * Used os.path.join in plugins/DiskDir.py where possible
    
      * Renamed the .conf files to .conf-gluster so that we don't clobber existing
        config files
    
        * This is not a complete change, as the spec file also needs to be
          modified to avoid the clobbering
    
        * See also https://bugzilla.redhat.com/show_bug.cgi?id=865867
    
      * Removed the redundant DIR_TYPE definition in plugins/utils.py
    
      * Removed MOUNT_PATH from plugins/utils.py replacing references with that from
        Glusterfs
    
        * This actually fixes a bug if a user every used a different mount path
          from the default in fs.conf
    
      * Added ASYNCDIR definition to plugins/utils.py until such time as another
        refactoring can rely on the one from swift.obj.server
    
      * Renamed plugins/utils.py's plugin_enabled() function to Gluster_enabled()
    
      * The diffs we carry for Swift are now a bit smaller in that we no longer
        have to add the plugin() method, we don't have to keep a fs_object field
        in these objects, and we can reference the Glusterfs module directly
    
      * Unit tests were modified appropriately, but now need to be run in the
        context of a Swift tree; this is unfortunate, but further refactoring will
        address this
    
    Change-Id: Id5d2510d56364761c03b3979bc71187dbe2f82fe
    BUG: 870589
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4141
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 04fc3fdb5825fbfacaf610c6d86c5a4766f16ee3
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Nov 2 09:15:36 2012 +0100

    POSIX sh uses = and not ==
    
    BUG: 815227
    Change-Id: I5a498f1b917fb658914133ee071783e7b8e0d025
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4151
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b872ccf50845a6aaee71a938ae4186e86d09aedc
Author: Anand Avati <avati@redhat.com>
Date:   Wed Oct 3 17:48:38 2012 -0700

    api/examples: updated examples to use new calls
    
    Change-Id: I865d0c52de268b27bbdb8786d3f4af5ef3ce3d9a
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4023
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit cae3216a2bff57c41003a7ad9532decc51412dbe
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Oct 24 10:30:56 2012 -0400

    object-storage: use constants for directory names
    
    Change-Id: I6109ee55061eae53c4c6762ca31fb5c4b13f0071
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4140
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Vijay Bellur <vbellur@redhat.com>

commit 6478b569c379dd0520ac3a46789284af5eb6cb4d
Author: Peter Portante <peter.portante@redhat.com>
Date:   Tue Oct 23 11:47:44 2012 -0400

    object-storeage: refactor to use one memcache key
    
    Address BZ 868087: https://bugzilla.redhat.com/show_bug.cgi?id=868087
    
    Store all of the data needed to generate the correct set of container and
    account details in one object, respectively, rather than using three seperate
    memcache keys.
    
    Change-Id: I46bf60c405b37cdb22727965bfd67bc5c410e77c
    BUG: 868087
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4139
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit abc8e5b01bff976e1f6b3c1e2747a2a341bf0f64
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Sep 3 16:51:06 2012 +0530

    glusterd: 'volume set' changes for op-version support
    
    An op-version check is performed for the given keys during stage. The commit
    phase moves the cluster op-version to the required version if needed.
    
    Change-Id: Id5c387094dbec723df736b2ecdc49ff93c179e0e
    BUG: 814534
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/3780
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 0608244512f1ab0ba9916ab3da9f0bc57ee234fc
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Oct 22 10:18:32 2012 +0530

    cli: Mark port as N/A in volume status when process is not online
    
    Change-Id: Ie11c7331e3bc58c0f934f424dde4341cdffb9e2c
    BUG: 861542
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4048
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d7cc779da48e484d0edb7bfbd903f941d0ccca32
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Sep 3 15:58:26 2012 +0530

    glusterd: op-version handshake implementation
    
    Brings in a new rpc program MGMT_HANDSHAKE, which implements the op-version
    handshake. This is required for bringing in the op-version feature as described
    in http://www.gluster.org/community/documentation/index.php/Features/Opversion
    
    Change-Id: I4333fd2714dbbd3a2a3fca5862cbb3c56615529e
    BUG: 814534
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/3688
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5c272f4d1c4ae67a3cf5a6af17518c82f520c1de
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 22 13:59:31 2012 -0400

    Minor refactorings to mark an internal routine
    
    Just a couple of changes to mark a routine as internal to this module (leading
    underscore, helps understand what is part of the utils API and what is not),
    and use of the positional argument for memcache for consistency and reduction
    in line count (doing this ahead of another refactoring to keep changes
    concise).
    
    Change-Id: I71581ad6ac4c383b1de787b767be568fc0a87eef
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4138
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 232adb88512274863c9f5ad51569695af80bd6c0
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Wed Oct 17 16:45:45 2012 +0530

    protocols: Suppress getxattr log when errno is ENOENT
    
    Change-Id: I3f4fe3f382aec5fd142cc409b80bd73aebd8b39b
    BUG: 861015
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4097
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8534cd56d8633c9468f337372d78c436263f36f6
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Oct 19 01:35:46 2012 -0400

    Reduce the number of stat/fstat system calls made
    
    This address BZ 868086, https://bugzilla.redhat.com/show_bug.cgi?id=868086
    
    This refactoring consolidates the code a bit, and uses os.stat calls to get
    all the information in one call when gathering the metadata for an object. The
    five stat system calls (invoked via all the os.path.*() calls) have been
    reduced to one.
    
    We also added a unit test for the one new behavior where get_object_metadata()
    will now throw an OSError exception if it has a problem stat'ing a file that
    exists.
    
    Change-Id: Iad5410c77938af68a47be757a3170abd201adeb0
    BUG: 868086
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4112
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 4f6aeb63d380f726b185bc25db1e50093b3119b3
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Oct 19 01:03:00 2012 -0400

    Further reduce extended attribute reads/writes
    
    More refactoring towards reducing the number of extended attribute
    reads/writes to the file system. See BZ 868120:
        http://bugzilla.redhat.com/show_bug.cgi?id=868120
    
    Basically the redundant routines restore_object, restore_account and
    restore_container have been collapsed to one routine, restore_metadata, which
    will only write out metadata if the new metadata is different from what was
    originally read.
    
    Along with these changes come a set of unit tests for all the functions
    related to the routines that are in this module in the call tree where
    restore_metadata is invoked.
    
    Change-Id: I957ee2f8646cbe6df4d4420d3bdfb1f6ac62bdd2
    BUG: 868120
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4111
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 3ab5404fab2a26399cb6a3a58d8930378e4ccb23
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Oct 18 15:39:32 2012 -0400

    Move _add_timestamp() closer to where it is used
    
    Simple refactoring to move _add_timestamp() closer to where it is used ahead
    of further refactoring changes.
    
    Change-Id: I175c5672202f2d961c72d4e2f4a441b47de1ba28
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4110
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 1a013e3e78c0afa7f6c6d8de3826280779bd0f2d
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Oct 18 15:34:57 2012 -0400

    object-storage: reduce the number of getxattr system calls by one
    
    Initial step towards addressing BZ 865619.
    
    Prior to the patch, reading metadata for a given object or container involves
    at minimum three getxattr system calls for objects that use only one xattr
    key/value pair:
    
        1. (via pyxattr)  getxattr() to see if key exists and get its value
           length (so it can allocate memory for second call below)
        2. (from pyxattr) getxattr() to get actual value data
        3. (via pyxattr)  getxattr() to see if following key exists
    
    For objects and containers that only have to use one xattr key/value pair,
    this patch reduces the number system calls by one. This can be significant
    given that almost every Swift API operation requires reads of the object or
    containers metadata.
    
    This patch is mostly a change to plugins.utils.read_metadata() to try to
    unpickle the accumulated metadata as each key/value pair is read, rather than
    trying to accumulate all the key/value pairs and unpickle at the end. Once we
    get enough data to form the pickle, we no longer keep trying to get more keys,
    even if those keys exist.
    
    The extra keys can exist when the size of the stored metadata shrinks below a
    key threshold. See https://bugzilla.redhat.com/show_bug.cgi?id=865619 for more
    details.
    
    See also https://bugzilla.redhat.com/show_bug.cgi?id=865858.
    
    This patch also adds a unit test infrastructure, and uses it to test with full
    coverage, the read_metadata, write_metadata and clean_metadata functions. As a
    result, we found that an infinite loop would occur in clean_metadata() when an
    unexpected IOError would occur trying to remove a key (this patch contains a
    fix).
    
    Change-Id: Ia1838c5e73af453b65360c1c525824231aa7c5d4
    BUG: 865619
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4109
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 5110fc03f14913e128b54a27f7680a7082d1bea3
Author: Peter Portante <peter.portante@redhat.com>
Date:   Thu Oct 18 15:26:43 2012 -0400

    object-storage: Bump size of metadata stored per xattr key
    
    For Gluster, since we require XFS, and XFS has a max metadata value size of 64
    KB, use the increased stored size to reduce the number of system calls, and
    how often we exit and enter the Python interpreter (via calls to pyxattr
    module).
    
    Today, with the hardcoded 254 byte limit per xattr key/value pair, adding a
    couple hundred bytes of user specified metadata can translate to up to three
    xattr key/value pairs (remember that the internal python metadata dictionary
    is pickled first and then stored in chunks in the keys).
    
    Change-Id: I6648106e8fac31f973ce207a6fecbcdab11fa271
    BUG: 865493
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4108
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit c7f7f134a7e2ee14d07d16d96c7849c6fd310693
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 16 14:21:17 2012 -0400

    core: add STACK_WIND_TAIL for more efficient default_xxx.
    
    Change-Id: Ic38e2183d1320bb17c014aca33779471c8db5d5f
    BUG: 867132
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4092
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6be9a19b940dd52cdc6e2df4b212e6221b2cfcb2
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Oct 24 10:05:03 2012 +0530

    glusterd: Remove brick from brick list on all nodes.
    
    Change-Id: I7150691886550b80cf5de11464a36c3254c5d21b
    BUG: 866916
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4128
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 61c1d77f220e36af7feec14ae072d2f6e3230cf0
Author: Florian Haas <florian@hastexo.com>
Date:   Mon Feb 20 16:25:43 2012 +0100

    Add OCF compliant resource agents for glusterd and volumes
    
    These resource agents plug glusterd into Open Cluster Framework
    (OCF) compliant cluster resource managers, like Pacemaker.
    
    The glusterd RA is fairly trivial; it simply manages the glusterd daemon
    like any upstart or systemd job would, except that Pacemaker can
    do it in a cluster-aware fashion.
    
    The volume RA is a bit more involved; It starts a volume and monitors
    individual brick's daemons in a cluster aware fashion, recovering bricks
    when their processes fail.
    
    Note that this does NOT imply people would deploy GlusterFS servers
    in pairs, or anything of that nature. Pacemaker has the ability to
    deploy cluster resources as clones, meaning glusterd and volumes would be
    configured as follows in a Pacemaker cluster:
    
    primitive p_glusterd ocf:glusterfs:glusterd \
    	op monitor interval="30"
    primitive p_volume_demo ocf:glusterfs:volume \
    	params volname="demo" \
    	op monitor interval="10"
    clone cl_glusterd p_glusterd \
    	meta interleave="true"
    clone cl_volume_demo p_volume_demo \
    	meta interleave="true" ordered="true"
    colocation c_volume_on_glusterd inf: cl_volume_demo cl_glusterd
    order o_glusterd_before_volume 0: cl_glusterd cl_volume_demo
    
    The cluster status then looks as follows (in a 4-node cluster; note
    the configuration above could be applied, unchanged, to a cluster
    of any number of nodes):
    
    ============
    Last updated: Fri Mar 30 10:54:50 2012
    Last change: Thu Mar 29 17:20:17 2012 via crmd on gluster02.h
    Stack: openais
    Current DC: gluster03.h	- partition with quorum
    Version: 1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558
    4 Nodes configured, 4 expected votes
    8 Resources configured.
    ============
    
    Online: [ gluster02.h gluster03.h gluster04.h gluster01.h ]
    
     Clone Set: cl_glusterd [p_glusterd]
         Started: [ gluster02.h gluster03.h gluster04.h gluster01.h ]
     Clone Set: cl_volume_demo [p_volume_demo]
         Started: [ gluster01.h gluster02.h gluster03.h gluster04.h ]
    
    This is also a way of providing automatic glusterd and brick recovery
    in systems where neither upstart nor systemd are available.
    
    Change-Id: Ied46657bdfd2dd72dc97cf41b0eb7adcecacd18f
    BUG: 869559
    Signed-off-by: Florian Haas <florian@hastexo.com>
    Reviewed-on: http://review.gluster.org/3043
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0d868525d2d6e33761842e0e134eb59475c6c2bb
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Oct 23 22:41:41 2012 +0530

    glusterd: fix for remove-brick on just created/stopped volumes
    
    in a fix to avoid race between stopping the brick and deleting
    it in remove-brick (15396f490d23c665d51a64a049679cb40472ab05)
    we moved delete of the brick inside stop volume, which was
    totally inside the 'if (volinfo->status == STARTED)' section.
    thus it made remove-brick of stopped/created volume as a failure.
    
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 867252
    Change-Id: Ie251e59a0b7ddb6965d8d48fb2a3bdb3bd11653d
    Reviewed-on: http://review.gluster.org/4127
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>

commit 8952b2729d7d554ac435a5057f3c758bfe95a2bb
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Oct 17 15:36:04 2012 +0530

    glusterd: do not log rdma not found messages in error mode
    
    Change-Id: Ie35b05ed2ee004bd6479ccdd3459cbcd9cf8c208
    BUG: 867313
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4094
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit cf63a76ca03240eb617ca5bd2aa9b3f7abe7b6a4
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Oct 20 19:30:06 2012 +0200

    NetBSD negative timeout missing support workaround
    
    Newer and simplier version: since the default of negative_timeout is 0,
    we can just avoid sending a fuse_entry in that case, and this is enough
    to work around the problem.
    
    BUG: 764655
    Change-Id: Ibfc6230e3cb9871ccade7fb756e61ebc47cb6487
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4115
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 6decc75807caa95ee93d70e8f23119bbada84a44
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Oct 18 18:39:34 2012 +0200

    In some cases AI_ADDRCONFIG confuses NetBSD 6.0
    
    BUG: 764655
    Change-Id: I29198c94c6788f9e01f57e11798f3d3d7cd9c8de
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/4105
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 09d981409f1379265ee02db9cd5f62672fba4747
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Oct 10 09:12:50 2012 -0400

    nfs: do lookup on getattr after brick-status change
    
    By doing a lookup, we get a chance to do all of the self-heal checks that
    would occur if we were using native protocol, and return proper status if
    the self-heal fails.  Best of all, we don't need to misrepresent times.
    
    Change-Id: I76477d1e5fce4d83e4029e02fcdd71e81e23110d
    BUG: 830134
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4058
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit bb41c8ab88f1a3d8c54b635674d0a72133623496
Author: Anand Avati <avati@redhat.com>
Date:   Wed Oct 17 15:51:18 2012 -0700

    tests: pre-commit regression tests
    
    Framework for writing test cases to be submitted with patches.
    
    This framework and the test cases get exercised by Jenkins in
    the pre-commit regression test. Jenkins is configured to give
    a +1 verified vote only if the regression test passes without
    failures (which includes test cases added/changed by the patch
    being tested)
    
    Every patch should include a test case (either extensions/changes
    to existing test cases or add new ones, as appropriate). The test
    case should be part of the same commit so that both code and
    test case get reviewed together.
    
    Test cases added are cumulative. Every new patch gets
    tested against its own test case and every test case previously
    added.
    
    A lot of new commits in the near future will be pure test cases
    (with no code change) which will get added in "catch up" mode.
    
    The tool used for implementing test cases is 'prove', and the
    framework itself is modeled similar to the POSIX compliance
    filesystem test suite.
    
    Under the top level directory, a new directory named 'tests/'
    is added. This contains top level classifier directories and
    framework files/scripts.
    
    Functionality tests should be created under a classifier directory
    below 'tests/'. For e.g:
    
      tests/basic/mount.t
      tests/performance/write-behind.t
    
    Bugs which get fixed should include a test case script named
    by the bug id, so that we are guaranteed any new change will
    not bring the issue back. For e.g:
    
      tests/bugs/bug-123456.t
    
    Triggering of regression tests in Jenkins is manual at this point
    as we do not want the entire test suite to run against every
    revision of a patch while it is still in the review/resubmit cycle.
    
    Signed-off-by: Anand Avati <avati@redhat.com>
    
    Change-Id: I8078244619135ccaba38e068925f8ca85141055a
    BUG: 764966
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4101
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 56d1f81949fde78615cd9fec048259d261f99c40
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Oct 8 11:02:55 2012 +0530

    glusterfs: add gf_mkostemp api and use it instead of mkostemp of libc
    
    Change-Id: Icc12b99e2233d22037e2c4bb2b6966e45668b7dd
    BUG: 764890
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4091
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 2b8043986e6f35a91bf1919c657d73f67b905ef7
Author: Peter Portante <peter.portante@redhat.com>
Date:   Wed Oct 17 15:25:34 2012 -0400

    object-storage: Don't catch generic exceptions around xattr calls
    
    We should really avoid catching generic Exception objects around any of our
    system calls. This simple fix brings this code in line with the other code
    wrapping xattr calls.
    
    Change-Id: I75492a61081fbfbec34c8d91a47214858c67e405
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4099
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit dbe793bcde5d0ba936eceb19bcb8a6f376a0dbc4
Author: Peter Portante <peter.portante@redhat.com>
Date:   Tue Oct 16 23:27:21 2012 -0400

    object-storage: Refactor code to reduce Swift diffs carried
    
    The upstream Swift code base contains the following commit which adds the
    ability to modify constraint values using the swift.conf file:
    
     https://github.com/openstack/swift/commit/a2ac5efaa64f57fbbe059066c6c4636dfd0715c2
    
    These changes rely on the above commit being back-ported to Swift 1.4.8 (see
    https://github.com/portante/swift/commit/fc2421b04022ac6bbe9d5014362ec5f99f94c5e0).
    
    As a result, a good number of differences we carry can be removed, since the
    provided swift.conf file now contains the values we need.
    
    Along with these changes, we add middleware to get constraints loaded properly
    (via monkey patching) until subclassing is implemented in a future commit. We
    further simplify the diffs to a minimal set by storing the timestamp in file
    system metadata and moving new files to the plugins/middleware directory.
    
    Note that the original "gluster" middleware was in the swift.diff file, and
    has been renamed to "glusterfs" and moved to the new plugins/middleware
    directory. The "gluster" middleware is now a temporary way to get the
    constraints properly loaded (both of these middleware pieces should disappear
    in future commits when we refactor further to subclass the Swift objects
    instead of patching them).
    
    Change-Id: I9dc00d6b6cdd64e277896d75c2fb06431c3e69cb
    BUG: 862052
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4093
    Tested-by: Peter Portante <pportant@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 59dfcf15578e08731f80c1f0c88cd4b7cd79d23d
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Oct 5 15:44:22 2012 +0530

    cluster/dht: ignore empty ->hashed_subvol during lookup
    
    ->hashed_subvol is not valid (== NULL) when the subvolume
    the entity hashes to is down. For directories, we need not
    rely on ->hashed_subvol as we aggregate information from all
    subvolumes. So, during lookup, NULL ->hashed_subvol is ingored
    but logged.
    
    Change-Id: I306e4e274fe29d60ff028add4a6c3bcd67b2f314
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    BUG: 856459
    Reviewed-on: http://review.gluster.org/4046
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 53e49e8592140d9f9d2134df6bb8322276e27cff
Author: shishir gowda <sgowda@redhat.com>
Date:   Thu Jul 26 15:21:38 2012 +0530

    cluster/distribute: Always return the latest time in struct iatt.
    
    save the a/c/mtime in inode_ctx, and dht_inode_ctx_update
    checks the passed iatte, and updates the stat's time,
    and inode_ctx's time accordingly. For preparent times, only
    the iatt stat to be returned is updated, not the ctx.
    
    With this, update, WIPE is removed, as we would always be passing
    back the latest mtime, and hence cache times will be relevant.
    
    TODO-handle rename WIPE calls
    
    Change-Id: I8e4c738cd830f3fafeef789c9181f9c242ac96a2
    BUG: 857791
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/3737
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f59494ba652f20d8bb83ace256ad965783a9bbf4
Author: Anand Avati <avati@redhat.com>
Date:   Sun Oct 14 12:08:25 2012 -0700

    syncop: save and restore THIS from the time of context switch
    
    The current yield() code assumes that the point of yielding
    is always in the translator where the synctask was created. This
    can be a problem for nested syncops and/or where syncop is issued
    by a different translator.
    
    So, save the THIS pointer just before swapcontext() and restore
    it right after resuming.
    
    Change-Id: I86aad2329ccbc3ac1f04fbec3835136ff3fa79fb
    BUG: 862838
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4085
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

commit bccb4b7a63eaa5e32b34c90dfdd5efa5c99b546a
Author: Pranith Kumar K <pkarampu@redhat.com>
Date:   Sat Oct 13 12:06:14 2012 +0530

    mgmt/glusterd: avoid directly using conf->uuid
    
    Change-Id: I398c8741b02aa2f34d428c948e93f422e520a9ab
    BUG: 862834
    Signed-off-by: Pranith Kumar K <pkarampu@redhat.com>
    Reviewed-on: http://review.gluster.org/4084
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>

commit 22050e51e876c5756e255cd707036cca8b8d544c
Author: Peter Portante <peter.portante@redhat.com>
Date:   Mon Oct 15 11:46:12 2012 -0400

    object-storage: change logging of some errors to warnings
    
    There are a number of errors logged which should probably be warnings, given
    that the code recovers on those paths.
    
    Change-Id: Ie643bbccb71e7b84ba76d68bac473d1dde663c44
    BUG: 866557
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4089
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ddb4652c30dc26bdb1548a35e2e970a032d4d290
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Oct 5 16:51:42 2012 -0400

    Remove the test subdirectory diffs ahead of initial refactoring.
    
    A subsequent commit will refactor the changes required of Swift to be much
    more minimal in nature, but does so by relying on an upstream Swift change to
    allow constraint values specified in the swift.conf file (see
    https://github.com/openstack/swift/commit/a2ac5efaa64f57fbbe059066c6c4636dfd0715c2).
    
    As a result, we can remove the test subdirectory diffs and assume that they
    will be present as a result of the upstream patch above.
    
    Change-Id: Ic450aca235d4c9f345e480f9b761bcb2857bd689
    BUG: 862052
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4082
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 49a3d884c985cd2f0f8622844b1b9307294a1fcc
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Oct 5 16:41:48 2012 -0400

    Reduce the number of gratuitous differences in constraints.
    
    Ahead of further refactoring to make things a bit easier to review, we have
    restored some of the code formatting as it was in the original constraints.py
    file from which this file as copied.
    
    Change-Id: Icd0b42b4790bc076c54dcbf08a9745648769acfd
    BUG: 862052
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4081
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3d10587d9d6400c9141b1f278bb5e2027fa784b8
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Oct 8 11:02:55 2012 +0530

    glusterfs: code cleanup
    
    Change-Id: I99bbb720d8b42c8b3899bb1353c6b73f7fcd50f1
    BUG: 764890
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4042
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3c05477e69ad61eb744948a7e921ae53665f97e5
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Oct 12 15:06:26 2012 -0400

    Fix BZ 865858: remove unnecessary system calls around xattr ops
    
    The following is a simple refactoring of the read and write metadata methods
    to just make calls to get/set/remove xattr operations instead of trying to
    stat/open/close the file. For a single GET operation, this brings down the
    number of system calls made from 13 to 3 for a file object with no
    significantly sized metadata (meaning, only 1 xattr key/value pair is needed
    to store the metadata).
    
    Change-Id: I698f5886d63d5203f130c8eac1536a3ee4b0dbfb
    BUG: 865858
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4078
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5b5453c3d6da0af8f2104c201d85ea4e795b6f17
Author: Anand Avati <avati@redhat.com>
Date:   Tue Oct 9 17:40:18 2012 -0700

    write-behind: use uint64_t for overlap comparison
    
    off_t is 'long int' (signed word) and therefore ULLONG_MAX - 1
    
    Change-Id: I027de7a1b2ca24865d5d787f9986930e97911ca4
    BUG: 857673
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4079

commit 49fad94c91bfba557d77e179bb020b70c0e18fbc
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Oct 12 13:07:24 2012 -0400

    Refactor to use pyxattr's get/set/remove methods
    
    These methods are not deprecated, the old ones with the xattr suffix are
    considered deprecated starting with 0.4 of pyxattr.
    
    Change-Id: I86ba7a44cec81a273931bf7e470de5eb04e82663
    BUG: 865858
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4077
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a9c613dfcfcb19299af00be4fc0d3b05dbd007d9
Author: Peter Portante <peter.portante@redhat.com>
Date:   Fri Oct 5 16:15:29 2012 -0400

    Fix a small typ-o in the Swift README
    
    Change-Id: I6c737bcc0d60d656df63ffe1c03ad336606ec090
    BUG: 862052
    Signed-off-by: Peter Portante <peter.portante@redhat.com>
    Reviewed-on: http://review.gluster.org/4080
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 101858ca54e6cba44cde2baf4ceac4a4b339885b
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Oct 12 18:07:04 2012 +0530

    protocol/client: Conditional logging in client3_3_unlink_cbk
    
    Change-Id: I4af398362cdb3f99782dcd3728988e4cf1fbb479
    BUG: 861925
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4069
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 760a564f2cd9a3271c8151e1ce65c8178e220250
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Oct 12 15:32:10 2012 +0530

    cluster/afr : Edited log message in afr_sh_entry_expunge_entry_cbk
    
    Change-Id: I9f7562d28c8bc798552c403164397f929a7bd1e7
    BUG: 860246
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4052
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d6b5690c38acc6a6269447b3cb2d5479069e48c1
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sun Jul 8 10:37:49 2012 +0530

    core: Add support for systemtap
    
    - First cut (configure plumbing only)
    - Intended to allow people who want to test userspace
      probes for their favourite xlator(s).
    
    Change-Id: I5bf202073a2f1cc29dc4a55714167b7f48b463a1
    BUG: 865734
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3638
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 397aa9235e12885cd96ddfb4ba507ea0e5d98f11
Author: Varun Shastry <vshastry@redhat.com>
Date:   Fri Oct 12 10:45:36 2012 +0530

    features/quota: Accept float numbers for quota limit.
    
    Quota limit can be given a floating value like 2.5GB or 0.5TB, which was not
    possible before.
    
    Change-Id: I2c89fd521e8b70be51252677c7986abcfa9d11a2
    BUG: 819394
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4068
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3dd35245f34a574303617828ed5d1f3cf6fdcdb9
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Oct 9 16:00:46 2012 +0530

    glusterfs man page edit
    
    Updated man page,
    * Added some of the options which were not there before.
    * Updated the default dirs.
    
    Change-Id: Ia796377120dc2fb990b2591c7607a16ef93f1fe2
    BUG: 825906
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/4060
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5459e74ef28bd08e48f95c2732f04144fdbbee56
Author: linbaiye <linbaiye@gmail.com>
Date:   Fri Sep 28 18:56:26 2012 +0800

    Preventing client crashing as the callings of GF_CALLOC has been failed.
    
    As the callings of GF_CALLOC can seldom come to a failure, glusterfs client
    will crash due to segment fault. We should have returned once the variables
    of transaction's local can't be alloced.
    
    Change-Id: Ia3798b8349d832b23c7825e64dbad93ebe29cd1b
    BUG: 861335
    Signed-off-by: linbaiye <linbaiye@gmail.com>
    Reviewed-on: http://review.gluster.org/4005
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7413b50220779d185efdb1d259c379a119a30a77
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Oct 4 20:55:30 2012 +0530

    performance/write-behind: use try lock while taking statedumps
    
    Change-Id: I690e8bf650d6e6e50899c2e17a79f42789e701eb
    BUG: 843792
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4036
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 68433db9ba07267c72d169b3ed4892e052e2eae2
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Oct 1 15:06:43 2012 +0200

    cli: introduce "--" as option terminator
    
    This way it becomes possible to pass option-like arguments to
    cli commands.
    
    Change-Id: I8eb1a44ce5d1bfe901d2b3e7cc7bfb84bb3012c9
    BUG: 815194
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/4007
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dde806643b736d9c24b4c62ac6826a02929ec4a5
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Sep 26 11:37:31 2012 +0530

    storage/posix: remove dependency on loc->path in posix_lookup()
    
    Change-Id: I0a3bc8650d9ff83977be696aa5caf9c7570197fd
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 781318
    Reviewed-on: http://review.gluster.org/3997
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 10c1a9c26e97ad363da84675ac22c4fb6420d28f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Oct 3 17:15:08 2012 -0400

    replicate: don't use synctask_new from within a synctask
    
    Change-Id: Iebf821ff720c63ab6da4b219d82c7f1d00769992
    BUG: 862838
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4032
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 72dafec18a79c0b66a18460725e0ade527939408
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Oct 8 16:18:50 2012 +0530

    cluster/afr: gluster volume heal $VN info sporadically reports nothing to heal
    
    PROBLEM:
    Whenever rsync is done at the mount point of a replicate volume and during the
    rsycn glusterd and bricks of one of the machine gets killed then executing
    gluster volume heal info gives results sporadically.Sometimes it says Number of
    entries are zero and other time it gives different output. When glusterd and
    brick of one of the machine gets killed then at other machine,
    RPC_CLNT_DISCONNECT will get triggered periodically. So it may happen that
    during the execution of gluster volume heal info command, RPC_CLNT_DISCONNECT
    also gets triggered and glusterd will assume that it got a new rpc_disconnet
    notification and glusterd will call the glusterd_op_ac_send_unlock_drain
    function instead of calling the glusterd_op_ac_rcvd_brick_op_acc function which
    is responsible for printing the entries. So because of RCP_CLNT_DISCONNECT
    notification, glusterd will execute functions responsible for
    RPC_CLNT_DISCONNECT(glusterd_op_ac_send_unlock_drain) rather than executing
    functions responsible for gluster volume heal info
    command(glusterd_op_ac_rcvd_brick_op_acc).
    
    FIX:
    Put a condition in for RPC_CLNT_DISCONNECT in the glusterd_peer_rpc_notify
    function so that if RPC_DISCONNECT is triggered for the first for a peer then
    glusterd mark that peer as disconnected so that if RPC_DISCONNET is triggered
    again, because peer is already marked as disconnected, glusterd will not inject
    EVENTR_ACK_DRAIN and prints the Number of entries.
    
    Change-Id: I770e3175b050fd7c7beb801b611a2dff9bfcbac8
    BUG: 857503
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4043
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 92754cd1d12cdda18b27911f3e50eabd907edce6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Oct 8 14:16:21 2012 +0530

    client-handshake: synchronize config.remote_port setting b/w
    rpc_clnt_reconnect and client_query_portmap_cbk
    
    problem:
    -------
    Theoretically there is a possibility that we could complete
    querying the remote brick's port number before rpc_transport_connect
    can return. If rpc_clnt_reconnect happens to be the caller of
    rpc_transport_connect and we've already got the remote brick's port
    number by the time rpc_transport_connect returns, without synchronization,
    rpc_clnt_connect resets config.remote_port to zero even before we have
    attempted a connection with remote brick.
    
    fix:
    ---
    By making only poll thread do setting and resetting of
    config.remote_port, we avoid the race-condition.
    
    Change-Id: I51879ba1cac651a80ff5c9c070ec7fe1ceea9e05
    BUG: 765051
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.org/4044
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 85866c6a9ef9b7401bb05f93fa9602f844d5a35b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Oct 11 16:42:33 2012 +0200

    build: do not unconditionally restart glusterd in glusterfs-geo-replication %post
    
    When the glusterd service is disabled and/or not running, the %post
    scriptlet for the glusterfs-geo-replication sub-package should not start
    glusterd.
    
    To resolve this, an additional condition will only restart glusterd on an
    update ($1 -ge 1) and only when it is running (condrestart).
    
    Change-Id: I4c18954e979377cf7211c3a55d14896898836fe6
    BUG: 766640
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4063
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f1f3d1c62d1e066c065f250caa0fc005b66dba37
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Sep 6 13:08:00 2012 +0530

    cli: Changes and enhancements to XML output
    
    This patch contains several xml related changes which fix some bugs and
    introduce xml output for commands which were missing it. These include,
    * XML output for rebalance & remove-brick status
    * XML output for replace-brick
    * XML output for 'volume status all' in on xml document
    * proper XML output for "volume {create|start|stop|delete}"
    * type & status of a volume in 'volume info' is now given as a string as well
    
    This patch also cleans up the '#if (HAVE_LIB_XML)' sections from the code-base,
    so that it is not littered around.
    
    Change-Id: I5bb022adf0fedf7e3ead92b4b79bfa02b0b5fef5
    BUG: 828131
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/3869
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6be13228c45188b104ffde22cee36fb24db8484d
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Oct 11 22:43:17 2012 +0530

    glusterd: volume-start, add-brick and remove-brick to use synctask framework
    
    - Added volume-id validation to glusterd-syncop code.
    - All daemons are restarted using synctasks in init().
    - glusterd_brick_start has wait/nowait variants to support
      volume commands using synctask framework and those that aren't.
    
    Change-Id: Ieec26fe1ea7e5faac88cc7798d93e4cc2b399d34
    BUG: 862834
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3969
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1f2dbafc72e6b4942a47dacb3899665118d7ec6b
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Oct 11 22:41:56 2012 +0530

    glusterd: Moved peer rsp handling functions to glusterd-utils
    
    - Moved inner functions used in conjunction with synctask, 'out'.
    
    Change-Id: I7fbfd9881ea58645c4295a9fa7163ddd15a45d2f
    BUG: 862834
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4066
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 751da4675cf3add21e567aebb92de2c10457afee
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Oct 10 10:23:37 2012 +0530

    glusterd: add-brick failed to start bricks when more than one were given
    
    Change-Id: I1487487a656e15e1a9a8685524ea40f0636e0e50
    BUG: 864772
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4051
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7ed127844df4618edfcda83eec3fff8259d4071b
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Wed Oct 10 16:30:11 2012 +0530

    cluster/afr Changed the message's log level from Error to Debug
    
    Change-Id: Ic2506561367bfec9022dc53e9b17b03dc343df95
    BUG: 859411
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/4055
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 46e20cce6ad6454074d4a55da5bebaad6152b429
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Oct 10 15:18:06 2012 +0530

    storage/posix: return -1 if lstat call returns non zero value apart from -1
    
    * If lstat() call in posix_{pstat, istat} returns non zero return value
      other than -1, then treat lstat() call to have been failed and return -1
      itself. This might happen if there is some bug in the backend filesystem.
    
    Change-Id: Ie23787f6c838f14f92edadad71b83471e3d22289
    BUG: 864401
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/4056
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1d814dcae0f06e75527017647b605f585125aa61
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Oct 10 13:18:25 2012 +0530

    cluster/afr: check transaction type for eager-lock after it is set
    
    Problem:
    Eager locking lk-owner decision is taken before transaction
    type is set. Default transaction type is DATA so all transactions
    are treated as DATA transactions at the time of eager-locking
    decision.
    
    Fix:
    Move the code that takes lk-owner decision after the transaction
    type is set.
    
    Test:
    Checked that the transaction type is set properly in gdb at
    the time of the lk-owner decision.
    
    Change-Id: Ib1c886866f28788aed67622982e86d667b2cdb80
    BUG: 864786
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/4053
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 15396f490d23c665d51a64a049679cb40472ab05
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Oct 10 17:57:20 2012 +0530

    glusterd: glusterd_brick_stop should be race free wrt pmap
    
    This is important for the effort to make glusterd use synctask
    framework.
    
    Change-Id: I0affb10a342df99df8daccfd6eef8fa6dd63928c
    BUG: 862834
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4057
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 144db7f39f35a51c24558c81faea3f49c237312f
Author: Anand Avati <avati@redhat.com>
Date:   Wed Sep 19 16:37:34 2012 -0700

    gfapi: added more API calls
    
    - stat
    - lstat
    - access
    - readlink
    - mknod
    - mkdir
    - rmdir
    - symlink
    - rename
    - link
    - opendir
    - closedir
    - seekdir
    - telldir
    - readdir_r
    - statvfs
    - chmod
    - fchmod
    - chown
    - lchown
    - fchown
    - utimens
    - lutimens
    - futimens
    - getxattr
    - lgetxattr
    - fgetxattr
    - setxattr
    - lsetxattr
    - fsetxattr
    - listxattr
    - llistxattr
    - flistxattr
    - removexattr
    - lremovexattr
    - fremovexattr
    
    Change-Id: Ic2467293ddfbcefaa9b41c82cec61a5602636833
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4022
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit dbed2e2f150eb227c26258f8c065e7789e3f9bda
Author: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
Date:   Mon Sep 24 10:10:29 2012 +0200

    Fix docs to reflect change in GLUSTERD_DEFAULT_WORKDIR
    
    Change-Id: I8ee98cece7a3c4ccdc4c444ff755fba37c75f169
    BUG: 859849
    Signed-off-by: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
    Reviewed-on: http://review.gluster.org/3970
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 748cf71a49d35b1a0366576521a2a7daa7fc3df3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Oct 1 21:10:07 2012 +0530

    glusterd: bring an option to change the transport-type of the volume.
    
    'gluster volume set <VOL> transport [<tcp>|<rdma>|<tcp,rdma>]'
    
    is the command to change the transport type
    
    * also moved 'memory-accounting' volume set key into VME table
    
    * fixed a crash in 'volume set help' if the vme->type was wrong
    
    Change-Id: Ic4f7ef62277a22b561b05e94c1b1bf19a51d2095
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 797001
    Reviewed-on: http://review.gluster.org/4008
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6c2e3e6a651e0f507e812114ada00cc5f505b4f2
Author: Anand Avati <avati@redhat.com>
Date:   Wed Oct 3 00:26:01 2012 -0700

    glfs-resolve: fix resolution of "/"
    
    Change-Id: I78d63b39dde14a9a32ea197cf0dedeb5695b35c9
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4021
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 43514de5c0bf498a774bb197e5ab8c0833e72b70
Author: Anand Avati <avati@redhat.com>
Date:   Tue Oct 2 15:07:01 2012 -0700

    syncop: fix symlink param
    
    make syncop_symlink() accept 'const char *linkname' instead of
    'char *linkname'
    
    Change-Id: I7751d552e4a4cc6e8b8e587b9e520213f4e11b45
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4020
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 5f423c68a119c2de9c092b4cc71aba02cde4d566
Author: Anand Avati <avati@redhat.com>
Date:   Tue Oct 2 02:12:30 2012 -0700

    syncop: Implement some missing operations
    
    - syncop_mkdir()
    - syncop_rmdir()
    - syncop_rename()
    
    Change-Id: I177db0f9af7c99fc6645d59521c8fb82f73812ca
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4019
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 8d92fabe6a29143a70b26182e63dddfb80c14f98
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Oct 3 12:22:50 2012 +0530

    cli: fixed cli crash during volume set operation
    
    PROBLEM:
    
    The cli crashes in the following case:
    gluster> volume set v3 auth.allow "write-behind"
    
    CAUSE:
    
    The second strncat operation in the last iteration of the for loop,
    in cli_to_glusterd writes off the end of the space malloc'd for "cmd",
    leading to memory corruption.
    
    FIX:
    
    Made the last strncat operation conditional so that in the last
    iteration, strncat is avoided.
    
    Change-Id: I8f836c684f33a6328e384ab8e677b8e32bcb4e55
    BUG: 862526
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/4025
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 557602e7637a7ef702db2b60f9cf10ecbe2837f3
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Oct 3 16:53:23 2012 -0400

    core: make sure there are processors for just-queued tasks
    
    Change-Id: I6196ad02fab6c24ac473cda0f78f9e946f0329ce
    BUG: 862838
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4031
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cffc3756652977268307ac5759abc5dddee74468
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Oct 3 14:56:19 2012 +0530

    glusterd: rebalance should use runner_run_nowait to free up glusterd's epoll thread
    
    Change-Id: Ia32b8c426643e1affcb02dbfb8f32b1844f34303
    BUG: 861342
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/4024
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 565cf6625da100f125cab21e590ab3e7ad0dce7e
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Oct 3 09:49:40 2012 -0400

    build: libraries must be in LDADD/LIBADD
    
    Libraries must not be listed in LDFLAGS, because _order is important_.
    Details see
    http://stackoverflow.com/questions/4241683/linker-flags-in-wrong-place
    http://www.gentoo.org/proj/en/qa/asneeded.xml#doc_chap2_sect3
    
    Change-Id: I0479456d6702748c555031bb20641ce430732ec7
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4030
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 58e6296fa2b59506cacab32689df77a211e578cb
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Oct 3 09:48:45 2012 -0400

    build: split CPPFLAGS from CFLAGS
    
    Automake provides a separate variable for preprocessor flags
    (*_CPPFLAGS). They are already uses in a few places, so make it
    consistent and use it everywhere. Note that cflags obtained from
    pkg-config often are cppflags, which is why LIBXML2_CFLAGS moves with
    into AM_CPPFLAGS, for example.
    
    Change-Id: I15feed1d18b2ca497371271c4b5876d5ec6289dd
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4029
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b026c96a61a65393ab0469aa1d9187b1c258e3a7
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Oct 3 09:45:22 2012 -0400

    build: move -L arguments out of CFLAGS
    
    "-L" is a linker flag, and as such should be in LDFLAGS, not CFLAGS, to
    have guaranteed effect.
    
    Change-Id: I014db3f48823d4923b45e0695b62b124eb1a1506
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4028
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1ecbb7ca68bd39ede792414b21a772469ecb4094
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Oct 3 09:30:27 2012 -0400

    build: remove useless explicit -fPIC -shared from
     CFLAGS
    
    libtool will automatically add "-fPIC" to the compiler command line as
    needed, so there is no need to specify it separately.
    
    "-shared" is normally a linker flag and has an odd effect when used with
    libtool --mode=compile, namely that it inhibits production of static
    objects. For that however, using AC_DISABLE_STATIC is a lot simpler.
    
    Change-Id: Ic4cba0fad18ffd985cf07f8d6951a976ae59a48f
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4027
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ec79583cfd2ae10998dedfeb0c2c2a83a81cdec3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Sep 6 00:44:04 2012 +0530

    dict: add new API 'dict_add()'
    
    * this new API is used only when we are sure that there is no
      replacing keys, ie. in dict_unserialize().
    
    Change-Id: I383dffc65056ebdaf0ab19727f7dc14ec7017fc1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 850917
    Reviewed-on: http://review.gluster.org/3844
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3372f198a8272b3467944c759be9975ee8f0aa02
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 27 16:59:13 2012 +0530

    fuse: create a new fd during fd-migration.
    
    Migration of fd to new graph involves creation of a new fd
    to be used only for calls sent in that graph.
    
    Earlier approach of using same fd across all graphs, with the
    associated inode always guaranteed to be the one valid in
    currently active graph, had issues because of the broken
    immutability of the association of fd with an inode
    (for the life of fd).
    
    With this patch, there will be a basefd, which the kernel will be
    aware of. This basefd, contains a mapping of an fd which is valid
    in currently active graph.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: I2b459f05bc2690a66498be107fad6444e3158138
    BUG: 802414
    Reviewed-on: http://review.gluster.org/3566
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 04371377f2f1a842ee3875f9fa415bbc97f20f65
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 2 13:37:08 2012 -0400

    build: remove -nostartfiles flag
    
    The "-nostartfiles" is a discouraged option and is documented to
    potentially result in undesired behavior. Since I see no reason why it
    should be in glusterfs, remove it.
    
    Change-Id: I56f2b08874516ebad91447b2583ca2fb776bb7ab
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4018
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c1d129fec4e8810e0080a276d29ec49fe4cfc4fb
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Oct 2 16:17:22 2012 +0200

    common-utils: valid_host_name() should allow (sub)domains starting/ending with a digit
    
    Some (sub)domains start or end with a digit. If this is the case, it
    will not be possible to 'gluster peer probe' hosts in that (sub)domain.
    This is overly restrictive, and RFC 1912 contains a note that describes
    the common use of start/end digits in (sub)domains:
    >
    > Allowable characters in a label for a host name are only ASCII
    > letters, digits, and the `-' character.  Labels may not be all
    > numbers, but may have a leading digit  (e.g., 3com.com).  Labels must
    > end and begin only with a letter or digit.  See [RFC 1035] and [RFC
    > 1123].  (Labels were initially restricted in [RFC 1035] to start with
    > a letter, and some older hosts still reportedly have problems with
    > the relaxation in [RFC 1123].)  Note there are some Internet
    > hostnames which violate this rule (411.org, 1776.com).
    >
    
    This change will also allow (sub)domains to consist out of digits only,
    like the example of 411.org above. It is still not allowed to start or
    and a (sub)domain with a `-' (dash) character.
    
    Change-Id: I7236edfe80fd08f28247536bef5287f63b564a63
    BUG: 862297
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4017
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7d347b2b0fc1c6d5262e42bf6f89e61a1fc18204
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 2 10:42:01 2012 -0400

    build: replace INCLUDES by CPPFLAGS
    
    automake warns: "INCLUDES" is the old name for "AM_CPPFLAGS"
    (or "*_CPPFLAGS")
    
    So abolish INCLUDES, and place the flags into GF_CPPFLAGS which then
    needs to be mentioned for glusterd.
    
    Change-Id: I326f890a69724d8b7163ce726f70ca4618c53958
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4016
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 33699838151670aac03f7f21b582419fd7611526
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Oct 2 10:03:34 2012 -0400

    build: add missing backslash in api/src/
    
    Seems like an accidental omission of the backslash.
    
    Change-Id: If78efd9d985a08829ecd6307fd8209d05d0e1fbf
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4010
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 22fdadad060aacaede110ce4f1fd678481baaa0f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Oct 2 09:45:56 2012 +0200

    extras: hook scripts should not start Samba if it is not running
    
    If the smb service was turned off by the administrator, the hook scripts
    should not start the service on starting/stopping a volume.
    
    By calling the service script with "condrestart" instead of plain
    "start", the service script checks if samba actually was running.
    
    Change-Id: I93408050a65445d98d2f9bb61992e216e04e0b04
    BUG: 861506
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/4015
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4efddca7551a3a443fdc37de4062a641e05cd2b2
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Oct 1 16:08:00 2012 -0400

    init.d: implement reload action for SUSE init script
    
    Change-Id: Ic17832b5bb33bc43faa1ff81c5221ec4e3f9294d
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4012
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 76e4895a87395d651d8a1d520548b6c82ad6a5b4
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Oct 1 16:07:09 2012 -0400

    init.d: use proper dependencies in SUSE init script
    
    "/usr", the place where the binaries usually reside, requires
    $remote_fs.
    
    Change-Id: I830c45b09b78b6c3b36c1475ac3f13cf6c2df588
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4011
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9059a76c67f0e3157c02b3de4b8f9339981e7c23
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Oct 1 16:09:26 2012 -0400

    build: consolidate common compilation flags into one variable
    
    Some -D flags are present in all files, so collect them.
    This adds -D${GF_HOST_OS} to some compiler command lines,
    but this should not be a problem.
    
    Change-Id: I1aeb346143d4984c9cc4f2750c465ce09af1e6ca
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4013
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b9f76b7179cfa3fb65b6e25b85a5458eeeb88bb5
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Oct 1 15:57:41 2012 -0400

    build: add missing GF_CFLAGS in api/src/
    
    GF_CFLAGS seems missing in two spots.
    
    In one of those, adding it to libgfapi_la_CFLAGS would make it equal
    to AM_CFLAGS, so remove libgfapi_la_CFLAGS there.
    
    Change-Id: I50c22f16210ecd40371d4abb0e418c7a4f94c12f
    BUG: 862082
    Original-author: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jan Engelhardt <jengelh@inai.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.org/4009
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5f9ad8a2bcc18d8ae828140d20203de496b371a4
Author: Anand Avati <avati@redhat.com>
Date:   Sun Sep 30 13:26:59 2012 -0700

    linux-aio: fixes while setting O_DIRECT flag
    
    Linux AIO needs O_DIRECT to be set for effective operation. O_DIRECT
    in turn has constraints on when it can work (offset, size alignment)
    
    So use O_DIRECT (unless instructed by application) only when offset
    and size alignments match. Else, io_submit() will happen over
    non-O_DIRECT fd, effectively blocking till the completion of the IO.
    
    Also fix a multithreading bug where detection/setting of O_DIRECT
    for a request was not atomic with io_submit() of that request.
    
    Change-Id: I190017e8bc78217429aff0714dca224cbe6f251d
    BUG: 837495
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/4006
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>

commit 5b896df0543e484b4de4de0a6ffa1053c5f92273
Author: linbaiye <linbaiye@gmail.com>
Date:   Fri Sep 21 16:50:34 2012 +0800

    Fix problems of mismatch type.
    
    Checking if an uint32_t is less than zero is unnecessary, so we change
    the parameter and return value to int.
    
    Change-Id: I5c08eaf8fd4c33768a366b22f0f5db9575056a1e
    BUG: 789278
    Signed-off-by: linbaiye <linbaiye@gmail.com>
    Reviewed-on: http://review.gluster.org/3965
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c2c7db16704a1da97ffe2e411c8014c856231a2a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Aug 22 23:52:03 2012 +0530

    dict: no need to memdup() the XDR buffer for dict_unserialize
    
    * current memdup() of full buffer is not required as
      'dict_unserialize()' does its own memdup() of the value.
    
    Change-Id: Iba866b68b753d060ee35bb300ee687e7d293ac82
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 850917
    Reviewed-on: http://review.gluster.org/3845
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3d3222074028900ed1d4866116ba7f4dbef5e614
Author: M S Vishwanath Bhat <vbhat@redhat.com>
Date:   Wed Sep 12 06:50:11 2012 +0530

     Made test-ffop.c exhaustive by making it to test all types of fops.
    
    Change-Id: I26052d0cbf72f81a6aa0c52498e99b635d1273e9
    BUG: 861380
    Signed-off-by: M S Vishwanath Bhat <vbhat@redhat.com>
    Reviewed-on: http://review.gluster.org/3931
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit c903de38da917239fe905fc6efa1f413d120fc04
Author: Anand Avati <avati@redhat.com>
Date:   Thu Sep 13 22:26:59 2012 -0700

    write-behind: implement causal ordering and other cleanup
    
    Rules of causal ordering implemented:
    
    - If request A arrives after the acknowledgement (to the app,
      i.e, STACK_UNWIND) of another request B, then request B is
      said to have 'caused' request A.
    
    - (corollary) Two requests, which at any point of time, are
      unacknowledged simultaneously in the system can never 'cause'
      each other (wb_inode->gen is based on this)
    
    - If request A is caused by request B, AND request A's region
      has an overlap with request B's region, then then the fulfillment
      of request A is guaranteed to happen after the fulfillment of B.
    
    - FD of origin is not considered for the determination of causal
      ordering.
    
    - Append operation's region is considered the whole file.
    
    Other cleanup:
    
    - wb_file_t not required any more.
    
    - wb_local_t not required any more.
    
    - O_RDONLY fd's operations now go through the queue to make sure
      writes in the requested region get fulfilled before getting
      processed.
    
    - O_SYNC fd's operations now go through the queue to make sure
      previously acknowledged writes on the file (via other fds) are
      fulfilled before getting processed.
    
    - Option to not honor O_SYNC is now removed.
    
    - Option to ignore O_DIRECT is added (useful when running a VM and the
      drive appears with NCQ/TCQ or WCE=1 for the guest.)
    
    - Option to disable_first_nbytes is removed (as the cause of the
      bug which required this was diagnosed to be missing TCP_NODELAY.)
    
    - General cleanup and better conformance to coding style and convention.
    
    Change-Id: Ib44fb72da3727246b4a85174cb568c2f0231f6de
    BUG: 857673
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3947
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit dd8eb06e26138e149252365043706067782416af
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 26 12:31:15 2012 +0530

    cluster/afr: Provide option to set readdir-size in entry-self-heal
    
    Problem:
    Entry self-heal does lookups on all the entries that are read
    in readdir. More the size of readdir more number of lookups happen
    in parallel. It is observed that it leads to HUGE cpu spikes
    rendering everything else on the system unusable.
    
    Fix:
    Provided the option self-heal-readdir-size to configure the size.
    Default value is at 1KB.
    
    Tests:
    Checked that the readdirs are happening with the configured value
    in entry-self-heal.
    
    Change-Id: Icaa937ad88857e6f9a12375b1e7f6a49192bc8b1
    BUG: 860895
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/4002
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 947523a74c97b057b8bcfdf2c65943495ab118d2
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Fri Sep 21 15:38:07 2012 +0530

    cli: removed extra dict unrefs and memory leaks
    
    PROBLEMS ADDRESSED:
    a. The following change
          http://review.gluster.com/#change,3948
       introduces extra dict unrefs in cli.
    b. There are instances of memory leak in gf_cli_*_cbk functions.
    
    FIX:
    Problem (a) is fixed by ensuring the dict is ref'd (indirectly at
    the time of creation) and unref'd (in CLI_STACK_DESTROY) ONLY
    once. The following is the rationale behind this approach:
    
       The number of refs and unrefs on dict varies across the different
       commands that use it. The cli thread MUST wait for the
       gf_cli_*_cbks to complete before the frame is destroyed. This
       rules out the need to do extra refs and unrefs in the code path.
    
    Problem (b) is fixed by doing unref on dicts that are created for
    the purpose of unserializing the response but never freed in
    gf_cli_*_cbk functions.
    
    Change-Id: I5a7431543fc8e3cac4d256f5c87d1e3c62a331be
    BUG: 823081
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/3966
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1ee65fe16f427c48d55856879f125d8e218a5823
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Sep 25 20:25:08 2012 +0530

    Fixed some general typing errors.
    
    Eg: changed recieved to received
    
    Change-Id: I360fcb99c97c8a0222e373fee20ea2fccfb938db
    BUG: 860543
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3998
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 2c04db460276c9de666d7ddaffc031492a7de867
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 27 01:32:45 2012 +0530

    mgmt/glusterd: Prevent extra unref in vol start
    
    Problem:
    Volume start cli handler does dict_unref of the dict
    unconditionally. It needs to be unrefed only on failure.
    
    Fix:
    Unref the dict only on failure.
    
    Tests:
    Volume start works fine after the fix.
    
    Change-Id: I64e5ad3d48f69545dd5e1132672182732b98c466
    BUG: 860833
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/4001
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bc2b5977a52baff96ffd69b118967a82d5933555
Author: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
Date:   Mon Sep 24 09:50:44 2012 +0200

    Fix parallel build issues
    
    Prevent creating symbolic links in not yet created sbindir.
    Since lex creates two files, make them depend on each other to
    prevent race condition.
    
    Change-Id: I72b633b24de33407006d70571b0a40adaa99dc2b
    BUG: 859843
    Signed-off-by: Kacper Kowalik (Xarthisius) <xarthisius.kk@gmail.com>
    Reviewed-on: http://review.gluster.org/3968
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 36db38a5722127e9f330915783cddae453be5db3
Author: Vijay Bellur <vbellur@redhat.com>
Date:   Tue Sep 25 00:17:56 2012 +0530

    build: Install glusterfs-logrotate as config file
    
    Change-Id: I8255eb4249503eac0add87444da934256faffc01
    BUG: 860037
    Reviewed-on: http://review.gluster.org/3973
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f29e26188635231652f57a518d85f110313933a2
Author: Anand Avati <avati@redhat.com>
Date:   Tue Sep 25 17:08:31 2012 -0700

    protocol/client: quick-reconnect after portmap query
    
    Currently the disconnect after a portmap query is treated like an
    ordinary disconnect and the reconnection attempt (in this case, to
    the brick) is attempted only after 3 secs. This results in a delay
    which is unnecessary.
    
    Mark the disconnection happening because of a successful portmap
    query as needing a 'quick reconnect' to avoid the delay for this
    special case.
    
    Change-Id: I43c8292ff0c30858d883ff3569a3761acbf2f5eb
    BUG: 860220
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3994
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit e8712f36335dd3b8508914f917d74b69a2d751a1
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 24 13:14:56 2012 +0530

    cluster/afr: Trigger heal on local subvols on any child_up
    
    Problem:
    The index in the child that comes online is generally empty
    because the changes would have happened on the other child which
    has been up.  So the sync begins when the other child's poll
    time-out happens (i.e. 10 minutes). The expectation is that the
    sync must be triggered as soon as the connection with any brick
    is established.
    
    Fix:
    Whenever any child_up happens trigger the index self-heal on all
    local children in the replicate subvolume.
    
    Tests:
    1) Checked that the self-heal is triggered on all local children
    whenever any child comes online.
    2) Checked that the volume heal commands are working fine.
    
    Change-Id: I4f64737866470a2f989349a889ea52782930e11d
    BUG: 852741
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3972
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ddcfd0888294b99049c7b05c0a43129b5099b19e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Sep 18 13:09:10 2012 +0530

    protocol/server: put the connection back if setvolume fails
    
    In server_setvolume, put the connection back (thus removing it
    from a the list of connections that protocol/server is maintaining
    if the connection object is a newly created one) if some operations
    such as getting the bound_xl etc fails. Otherwise the process might
    segfault upon statedump, when it tries to access NULL bound_xl of a
    connection.
    
    Change-Id: Ifa340f534cd88d5601a9219da622b323fbe98b80
    BUG: 858191
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3953
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 95a33a59039f582987c86755961c97ac07338197
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Sep 25 20:47:08 2012 +0530

    gfapi: fix the failure in glfs_open()
    
    * the issue is happening because the resolve_symlink() logic was
      reversed
    
    Change-Id: I10eca14d82e3ebf5a0195d5db1330f9e1a3e2dc4
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 839950
    Reviewed-on: http://review.gluster.org/3978
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7add67bcca82e438b4aece5aad096a08a866e26c
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 25 10:35:14 2012 +0530

    cluster/afr: Wake up post-op on non-co-operative transaction
    
    Problem:
    The problem is observed when kernel untar is done. One file untar
    happens every second. The reason for this is, setattr lock is blocked
    on the prev fd data-transaction full-lock (because of eager-lock).
    Because of post-op-delay the post-op (xattrop + unlock) of the prev
    data-transaction happens after 1 sec.
    Until this the setattr is blocked resulting in performance problems
    in untar.
    
    Fix:
    Whenever an loc data, meta-data transaction comes, it should wakeup
    the prev-post-op on the same process' fd.
    
    Tests:
    The performance problem in untar went away. I put a breakpoint in
    client_finodelk for a 2G file dd and the inodelk is hit only 4 times.
    This confirms that the change does not affect post-op-delay in a
    -ve way.
    
    Change-Id: Ice3c2a1211f4dca6520a19bc4ba6cb9efb2902ad
    BUG: 845754
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3975
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5ad96fb5a8c79fe50c21a726a7cbda4eaa3b96cc
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Aug 27 19:54:20 2012 +0530

    geo-rep / gsyncd: gsyncd binary wrapper context fixes
    
    Changes to __gf_calloc (commit ed4b76ba) triggers a recursive
    sequence of _gf_log() and __glusterfs_this_location() calls. This
    is due to __gf_calloc() trying to access THIS which is not valid
    in the context of geo replication binary wrapper. This patch fixes
    the problem by introducing the relevant context in the wrapper.
    
    Change-Id: I32b0b6927074692dbf66bad2f3e93434201aaa82
    BUG: 846569
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/3859
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 373b25827f0250d11461fbe76dd6a0e295069171
Author: Anand Avati <avati@redhat.com>
Date:   Mon Aug 20 10:48:16 2012 -0700

    core: enable process to return the appropriate error code
    
    Setup a pipe() in glusterfs_ctx_t to communicate with the fork'ed
    child the exit status and return it to the shell.
    
    Change-Id: Ibbaa581d45acb24d5141e43ae848cae29312d95f
    BUG: 762935
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3836
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a6234eeb2a0fb106b801a3241ce7538fd5562ff6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Sep 17 16:14:41 2012 +0530

    libglusterfs/graph: pass correct translator pairs during reconfigure
    
    when we autoload xlators like acl, worm or mac-compatibility,
    they will be loaded on top of old graph.
    However, corresponding ones won't be present in new graph, since
    newgraph doesn't contain autoloaded translators. While
    passing xlator pairs to reconfigure, this fact should be accounted
    and correct xlator pairs should be passed instead of blindly passing
    oldgraph->first and newgraph->first.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: I8f4fe37b7e26dc2dcae78c1fe0d4a04f8ab84ed0
    BUG: 857874
    Reviewed-on: http://review.gluster.org/3949
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit aa4468cdf5acfb0087151349befa1b0d49448bd6
Author: Anand Avati <avati@redhat.com>
Date:   Thu Sep 20 00:32:47 2012 -0700

    glusterd: use runner_run_nowait() variant for starting bricks
    
    This is a temporary change, which will be undone once glusterd is ready
    for handling portmap queries in a different thread while exec'ing
    brick processes.
    
    Change-Id: I389b9c38c7444e95fe9d8d0ff20fc91f4bfaf150
    BUG: 762935
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3963
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit e31a5847e269d865b7248554e328bc9ac358454a
Author: Anand Avati <avati@redhat.com>
Date:   Thu Sep 20 00:30:39 2012 -0700

    runner: introduce a new variant runner_run_nowait()
    
    which makes the child blindly _exit(0) (thereby relieving
    the caller quickly) and the grandchild continues to actually
    do execvp().
    
    Change-Id: I4dac0f39aaaa5b2ae5dbeb96e221b8257f8d3a22
    BUG: 762935
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3962
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit 2fc6834e7a5d721e97a47f3ebaa201902af73c5a
Author: linbaiye <linbaiye@gmail.com>
Date:   Thu Sep 20 12:37:29 2012 +0800

    Prevent fuse from setting an invalid value of fd_ctx
    
    This patch is used to prevent __fd_ctx_set() from setting an invalid value.
    
    Change-Id: I6756d83eab20fc485b3696ae341e21324f1c885c
    BUG: 789278
    Signed-off-by: linbaiye <linbaiye@gmail.com>
    Reviewed-on: http://review.gluster.org/3961
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit e09245b8d152fdae8152f8e29d2be1827e6090e1
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Wed Sep 12 17:16:22 2012 +0530

    glusterd: Fix to log command status at the appropriate time
    
    PROBLEM:
    In the existing implementation, the success/failure of
    execution of a command is decided (and logged) in glusterd
    handler functions. Strictly speaking, the logging mechanism
    must take into account what course the command takes within
    the state machine before concluding whether it succeeded or
    failed.
    
    FIX:
    This patch attempts to fix the above issue for vol commands.
    The format of the log message is as follows:
        for failure:
        <command string> : FAILED : <cause of failure>
        for success:
        <command string> : SUCCESS
    
    APPROACH (in a nutshell):
    
     * The command string is packed into dict at cli and sent to
       glusterd.
     * glusterd logs the command status just before doing a
       "submit_reply", which is called (either directly or
       indirectly via a call to glusterd_op_cli_send_response)
       at 2 places for every vol command:
       i. in handler functions, and
       ii. in glusterd_op_txn_complete
    
    In short, the failure of a command in the handler implies the
    command has indeed failed. However, its success in the handler
    does NOT necessarily mean the command succeeded/will succeed.
    
    Change-Id: I5a8a2ddc318ef2dc2a9699f704a6bcd2f0ab0277
    BUG: 823081
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/3948
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f9652adfd1315c0a817917eb35f61f43f58e673b
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Aug 7 11:40:16 2012 +0530

    glusterd: Fix compile time warning for gsyncd helper routine
    
    Change-Id: I262cc654a3d85ed690446b3875959565600b4bcd
    BUG: 846197
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.org/3784
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit 38afd84faa383c5e0be21c48c918112b7b01a5cf
Author: Anand Avati <avati@redhat.com>
Date:   Mon Aug 20 10:19:15 2012 -0700

    rpcsvc: framework for executing actors as synctask
    
    An rpcsvc_program can be registered by setting .synctask field
    to 1 which will make actors of that program be executed in a
    synctask, thus freeing up the rpc/poll thread while the actor
    executes.
    
    Change-Id: Idacef2ad3bcae0f354fd0fc16ca06ba7094d7b98
    BUG: 762935
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3833
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a3c5722b39895f5fa4721cfae456e26bc758b33a
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Aug 13 14:05:17 2012 +0530

    performance/io-cache: provide hook for dumping inode context
    
    Change-Id: Idcf24200ad8f0cf018ab92118f6b77cc4b9edcab
    BUG: 843787
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3816
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1c5dafc906833a4530142057061cd82b9d4a7ca6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Sep 18 20:45:47 2012 +0530

    fuse: override 'gid-timeout' option to disable aux gid compatibility
    
    while mounting -o gid-timeout=-1 will be treated as disabling aux-gid
    
    Change-Id: I85c350868a8cc4a43f5e5aec9427222580da675b
    BUG: 835834
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.org/3954
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 08bad02bba6d934cc03d50c0bbcce2370ec66416
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 19 13:36:25 2012 +0530

    syncop: Implement access fop
    
    Change-Id: I959144451790d7e47ae48564923d324451a9db23
    BUG: 858602
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3958
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9cc24de746ce0e616fa09120b89aaa9a626f33cb
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Sep 18 14:39:51 2012 +0200

    mount/fuse: readdir() should return 32-bit inodes when 'enable-ino32' is used
    
    The glusterfs mount option 'enable-ino32' does not change the behaviour
    of readdir(). fuse_readdir_cbk() uses entry->d_ino directly, and this
    was missed in commit c13823bd16b26bc471d3efb15f63b76fbfdf0309.
    
    By adding the function gf_fuse_fill_dirent(), the fuse_dirent structure
    is filled in a similar way as the fuse_attr structure. This helper uses
    the same function to squash the 64-bit inode in a 32-bit attribute.
    
    Change-Id: Ia20e7144613124a58691e7935cb793b6256aef79
    BUG: 850352
    URL: http://lists.nongnu.org/archive/html/gluster-devel/2012-09/msg00051.html
    Tested-by: Steve Bakke <sbakke@netzyn.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/3955
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f4831ec958fd8a37e759b6e3338377808be8bc2e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Fri Aug 24 08:40:12 2012 -0400

    dual license
    
    rebased
    
    BUG: 820551
    Change-Id: I9c51d68e52a9252c5a43af1677380a410ca69519
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/3856
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 5d67526f6028d75a57056dc83d2e3086cec8779b
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Aug 28 18:11:43 2012 +0530

    cli/: Filter out the loopback address for brick creation.
    
    Don't create the volumes with brick address 0.0.0.0 to 0.255.255.255
    (http://en.wikipedia.org/wiki/Reserved_IP_addresses)
    
    Change-Id: Ic5464ec370bddf498a5220acf2d367b877e21e66
    BUG: 787627
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3865
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit db2b6e73fa35dc0a44eb7f7d5f3943891444903b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Sep 5 23:57:05 2012 +0530

    logging: log ENOENT errors in DEBUG mode instead of ERROR or INFO
    
    Change-Id: I0a43769223991e4ad5206b4382d737a0c3557bf3
    BUG: 851953
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3934
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8062ad0799ad4e92882c25f5a7c6e95a06d63c12
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Aug 27 11:53:41 2012 +0530

    features/marker: if parent inode is NULL, then get it by inode_parent
    
    * If parent inode is NULL (nameless lookups which uses gfid for looking up the
    inode), then try to get it by inode_parent, instead of returning  which results
    in the inode's contribution not being added to the list.
    
    * Prevent exceesive logging while adding the inode's contribution to the list
      if the operation fails. (Check if the inode's gfid is null which indicates
      that the inode is not yet linked to the inode table and hence addition
      of its contribution to the list can fail).
    
    Change-Id: I5300f00195ae92a5122613898ae3dabddb2d0bfe
    BUG: 851953
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3935
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9289f4be460e910189f553fe2b63e6e3aabe5b27
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Sep 10 11:08:01 2012 +0530

    CLI: Displaying time as N/A when unix time is 0
    
    Problem:
    'volume top open' command was displaying '1970-01-01 00:00:00.000000' when no
    file has opened yet.
    
    Fix:
    Made the fix in gf_time_fmt() to make it more generic according to patchset 1
    review comment.
    
    Change-Id: I748ed203bd0d9fbaac94b5b51ed708b34fccd434
    BUG: 852000
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3924
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f7342ad3a91ac5140e9c24e20007519847f4f4ec
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Sep 17 15:44:16 2012 +0530

    Clean up of typepunning errors ( Strict aliasing warnings )
    
    Change-Id: I48733967facc526fb523a8dc9bd068f8c5cc5971
    BUG: 764282
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3950
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4d0895c966f38355950d22ce378579fd35b7c9b2
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Sep 12 12:38:43 2012 +0530

    glusterd: Fix remote processes not being shown in "volume status"
    
    Also, refactor function name so it makes more sense.
    
    Change-Id: I3bd3e1bdcacb522ddf4f39d09f73be1c53915362
    BUG: 856480
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/3933
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b59296014303ae93367b8c38f158b3db28fbbe35
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Aug 22 18:05:44 2012 +0530

    protocol/server: dump the ltable and fd table related inodes only
    
    Do not dump the entire inode table in the statedump. Instead dump
    those inodes only which are present in fdtable or ltable.
    
    Change-Id: If848f9a6198927b4cc0abd47339461f3ea41d6df
    BUG: 844688
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3848
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b3c6ee00f9fdc80330979e62fbd7f9bec9440b35
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 12 14:06:53 2012 +0530

    features/quota: Avoid mem_put on null local
    
    Problem:
    QUOTA_STACK_UNWIND does not check if local is NULL before mem_put.
    This leads to a callingfn log for every setxattr in quota.
    
    Fix:
    Made sure the mem_put happens only on non-null local in quota.
    
    Additional changes:
    Removed unused QUOTA_STACK_DESTROY macro.
    
    Tests:
    Peformed setfattr on the mount point and the Invalid argument
    logs don't come anymore. Checked that the change does not introduce
    any memory leak in quota.
    
    Change-Id: Ie4534c7af0fff80e35d8510311055f930262594f
    BUG: 856541
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3936
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8f9e94c65516662ff49926203a73b3a0166c087e
Author: Anand Avati <avati@redhat.com>
Date:   Tue Aug 28 23:23:52 2012 -0700

    gfapi: add symlink (auto resolution) support in resolver
    
    - new internal API glfs_lresolve() for usage with APIs
      like glfs_lXXXX() (e.g. glfs_lstat())
    
    Change-Id: I61c60af6bda3072f189684ad8ac9815d59f455fc
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3866
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 0d3bec589748b4cc8295d9ed109d21c94e3d8854
Author: Anand Avati <avati@redhat.com>
Date:   Mon Sep 17 12:56:49 2012 -0700

    mount/fuse: treat NULL gfid is a failure in lookup disregarding op_ret
    
    It is not possible to inode_link() with a NULL gfid. If a lookup
    (or any other "entry" op) returns a success but has a NULL gfid,
    then treat it as a failure even if op_ret was 0.
    
    Currently AFR does this when self-healing fails/aborts in certain
    situations (like entrylk acquisition failure, gfid mismatch etc.)
    returning a NULL gfid in struct iatt of lookup_cbk with op_ret = 0.
    Fixing this is an independent patch and fuse-bridge needs to be
    robust against such misformed replies in any case.
    
    Change-Id: If5f75780c0b5b1303f466711f1992f90a77e768a
    BUG: 856921
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3952
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit 92d2720b2764c2ce399751b1cbbf691fc3f53489
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Sep 13 12:33:31 2012 +0530

    cli: Fix double free in cli_add_key_group
    
    Change-Id: I3c2f030ac7c53913612a3fbac5e582c47b005621
    BUG: 851237
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3943
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dc772ca6b0fcba8dc4ff4506ac7c171e289bd78a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sun Sep 2 15:22:34 2012 +0530

    storage/posix: Option to set brick(of a volume)'s root dir's uid/gid
    
    CLI
    ---
    gluster volume set VOLNAME owner-uid uid
    gluster volume set VOLNAME owner-gid gid
    where uid,gid are the owner's user id and group id respectively that
    would be set on the root of all brick (backend) fs.
    
    TODO: uid/gid should not be -1. Today we don't validate that in CLI.
    
    Change-Id: Ib6a2fb5e404691c5fe105a89faaeff3e1ab72e91
    BUG: 853842
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3891
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit df731a50f222fdf3a25e48a0f9ff6d97fc8772b1
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Sep 12 16:08:56 2012 +0530

    glusterd: Fixed _is_prefix check for two file paths
    
    Change-Id: Iad1f7c865c4ce5092d85379257ba7a5ec95f7ebc
    BUG: 764890
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3937
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3e2057542da6a0f182243b527bc7f1fd43d1fd3c
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Sep 11 16:34:54 2012 +0530

    All: License message change
    
    License message changed for server-side, dual license GPLV2 and LGPLv3+.
    
    Change-Id: Ia9e53061b9d2df3b3ef3bc9778dceff77db46a09
    BUG: 852318
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3940
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2564ab2bc8cd3aa2561e091f72278e480fcef33d
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Sep 12 11:47:13 2012 -0400

    glusterfs SEGV on Fedora 17 from UFO fallocate(2) call
    
    An upload of a file will cause the volume's glusterfs to SEGV
    when it fields a FUSE_FALLOCATE op. Swift inspects libc to determine
    if there is a symbol for fallocate(2) and if so will use it. And
    while the libc in RHEL 6 does have fallocate(2), the version of
    fuse in RHEL 6 does not support fallocate, and things are handled
    gracefully elsewhere (the kernel perhaps?)
    
    N.B. fallocate was added to version 7.19 of fuse. Fedora 17 and
    later (and maybe earlier too) has 7.19. RHEL 6 still has 7.13.
    Glusterfs uses the 7.13 version <linux/fuse.h>
    (in contrib/fuse-include/fuse_kernel.h)
    
    Thus on Fedora 17, with both fallocate(2) in libc and fallocate
    support in fuse, the fallocate invocation is dispatched to glusterfs,
    but the dispatch table (fuse_std_ops in
    xlators/mount/fuse/src/fuse-bridge.c) is too short for one thing;
    the fallocate opcode (43) indexes beyond the end of the table, and
    even when that doesn't directly cause a SEGV, the NULL pointer at
    that location does cause a SEGV when attempting to call the function
    through the pointer.
    
    BUG: 856704
    Change-Id: I148acbf1265f01a15bd158f227c8a7cb9365606e
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.org/3938
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ab039cc10f8493c6964ddc5b1510219708a31c60
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Aug 29 14:55:13 2012 +0200

    fuse-bridge: Pass unknown option down to fuse
    
    In Linux, certain "filesystem-specific" options (passed in string form in last
    argument to mount(2)), such as "rootcontext" or "context" are in fact common to
    all filesystems, including fuse. We should pass them down to the actual
    mount(2) call untouched.
    
    This is achieved by adding "fuse-mountopts" option to mount/fuse translator and
    adjusting the mount helper to propagate it with unrecognized options as they
    are encountered.
    
    BUG: 852754
    Change-Id: I309203090c02025334561be235864d8d04e4159b
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/3871
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4f87fd0ae2ce629576ca5f647a99888d31a46815
Author: Anand Avati <avati@redhat.com>
Date:   Thu Aug 30 13:15:39 2012 -0700

    dht: improve dht_fix_layout_of_directory for better re-assignment
    
    Jeff Darcy wrote:
    > AFAICT, the fix-layout code doesn't do the same rotation that the
    > new-directory code does. Therefore, the new bricks always claim
    > completely predictable hash ranges for every directory, leading to
    > either a 0-1-2-3 pattern or a 1-0-2-3 pattern.  In other words, a
    > file whose hash falls into the second quarter of the range will always
    > be assigned to brick 2, and a file whose hash falls into the fourth
    > quarter will always be assigned to brick 3.  The rest will be split
    > according to the original pattern.  Put still another way, instead of
    > same-named files in different directories being spread across N bricks,
    > they might be spread across only two bricks (bad) or totally
    > concentrated on one brick (worse) regardless of N.
    
    The current dht_fix_layout_of_directory() code, in an attempt to
    maximize overlap of new layout with existing layout (to minimize
    movement of data) fails to do a good job of randomizing new assignment
    even when it could do a better job. In an example where we expand
    from 2 nodes to 4 nodes, the current possibilities are limited in the
    following way -
    
    (theoretical hash range: 00 - 99)
    
    OLD 1
    -----
    server1: 00 - 49
    server2: 50 - 99
    
    NEW 1
    -----
    server1: 00 - 24
    server2: 50 - 74
    server3: 25 - 49
    server4: 75 - 99
    
    OLD 2
    -----
    server1: 50 - 99
    server2: 00 - 49
    
    NEW 2
    ------
    server1: 50 - 74
    server2: 00 - 24
    server3: 25 - 49
    server4: 75 - 99
    
    The above shows that when add-brick from 2 bricks to 4 bricks, server3
    and server4 always get the _same_ hash range no matter what the original
    hash range assignment was.
    
    The fix in this patch is first do the standard new directory assignment
    to a directory (with rotation etc.) and then do the reassignment to
    maximize overlap. This way newly added servers still get random ranges
    and existing servers have a probability of getting either of the quarters
    which were part of its half previously. The same principles hold for
    all add-brick from M to M+N.
    
    Change-Id: I0cbbf3bfa334645728072d66aaaa80120d0b295f
    BUG: 853258
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3883
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c3d7286a67ce0ac4db9cb8fa079a48f423245000
Author: Anand Avati <avati@redhat.com>
Date:   Tue Sep 11 12:28:52 2012 -0700

    event: peel out poll and epoll specific code into separate files
    
    code re-org, no change in logic.
    
    Change-Id: Ib1cb3d3f4cf8989a916df7476479c26570d07a84
    BUG: 821087
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3932
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 35d178dbd4ddb8c407e911823c850642563baa9f
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Mon Aug 20 21:34:26 2012 +0530

    cli: Added special key "group" for bulk volume set.
    
    gluster volume set VOLNAME group group_name
    
    - where group_name is a file under /var/lib/glusterd/groups containing one
      key, value pair per line as below,
      key1=value1
      key2=value2
      [...]
    - the command sets key1 to value1 and so on.
    
    Change-Id: Ic4c8dedb98d013b29a74e57f8ee7c1d3573137d2
    BUG: 851237
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3831
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a032de191ec32be363d1feedfbd839f6dbde2579
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Sep 2 07:15:46 2012 +0200

    Detect python > 2.5, make sure MKDIR_P is substituted
    
    gluster build machine generate configure scripts unable to detect python > 2.5
    This change include a more recent python.m4 so that newer python can be
    correctly detected.
    
    Build.gluster.com also produces a configure that fails to subsitute
    MKDIR_P, leading to bugs at make install. Works this around by
    introducing mkdirp.m4 from aclocal-1.11, with the autoconf version test
    removed because build.gluster.com also has an outdated autoconf. And
    we need a bit from a recent autoconf
    
    NB: this patchset changes nothing since the last one, I just fix title
    in gerrit.
    
    BUG: 764655
    Change-Id: I3ffac50cc7a10cb9e56dd490dbc2b550bba3fabd
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/3888
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5499205a08c0b69156628684b5dc235f1355b026
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sat Sep 8 12:12:48 2012 +0530

    glusterd: Expect setmntent(3) to return NULL
    
    - Closed the mtab FILE * using endmntent(3)
    
    Change-Id: I5e1ebb7f092abda638cfbb5524da693dcac6c872
    BUG: 851109
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3920
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7a2362d818baf7cae0ae54ffede436821491c876
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Sep 7 01:05:20 2012 +0200

    geo-rep/gsyncd: work around rsync argument overflow
    
    instead of passing the files to be synced as args to rsync, have rsync
    read them on stdin with '-0 --files-from=-'
    
    Change-Id: Ic3f71a0269941ce50051af8adfad183a52a79b01
    BUG: 855306
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/3917
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c78919ce37ca55aa789733ca7f2b4beef72d7a54
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Sep 7 20:59:54 2012 +0530

    cluster/dht: handle percent option for 'min-free-disk'
    
    * with the init option cleanups, setting of 'conf->disk_unit'
      was reset, which made it not set the '%' in the option.
    
    * bring a global check, which makes the option assume its
      percent, as long as value is < 100.
    
    Change-Id: I00bd1395a309cdc596a2b2b80304c6d98696a24a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 852889
    Reviewed-on: http://review.gluster.org/3918
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c13823bd16b26bc471d3efb15f63b76fbfdf0309
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Sep 3 12:49:21 2012 +0200

    mount/fuse: add mount-option "enable-ino32" for the native client
    
    By default the GlusterFS-native client uses 64-bit inodes. Some 32-bit
    applications can not handle these correctly. Introduce a client-side
    mount option "enable-ino32" which causes the FUSE-client to squash the
    64-bit inodes into a 32-bit value.
    
    Change-Id: I3296d16528bfb50457b9675f6b8701234ed82ff0
    BUG: 850352
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/3885
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit baddf332d589d29d9bcb18d11dcbb875650e4298
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 4 21:10:45 2012 +0530

    storage/posix: Make posix_fremovexattr anon fd friendly.
    
    Problem:
    For anonymous fds posix_fremovexattr fails to work because the open
    never happens and the fd-ctx is not set with the fd-number.
    
    Fix:
    Use posix_fd_ctx_get which opens and sets the fd-number in the fd-ctx
    for anonymous fds.
    
    Tests:
    Added a syncop call in glustershd to test this change and it worked fine.
    
    Change-Id: I9629190a87eb27a7a1578e4fe732a5eb1248f30c
    BUG: 854331
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3903
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b46e98787f735f6b7cd434e4eeb7f8f011a6e63b
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Wed Aug 29 16:51:50 2012 +0200

    mount.glusterfs: Ignore noauto and _netdev options
    
    BUG: 827121
    Change-Id: Icab4ca9adecc7b9d62e3d5e7d161c442f16ad940
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Reviewed-on: http://review.gluster.org/3873
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit dd7bc2d8834e02eef4a98d26e2bfb21ab7695539
Author: Jules.Wang <lancelotds@163.com>
Date:   Tue Sep 4 05:42:41 2012 +0800

    afr: add option description of 'open'.
    
    Signed-off-by: Jules Wang <lancelotds@163.com>
    Change-Id: I6c7dd337c758e82e9d58d4d65f53b5aa72ac5dfb
    BUG: 764890
    Reviewed-on: http://review.gluster.org/3895
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ca21f6bff47ae0ee564ee4ebbba04da3b0ff2128
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 4 21:13:32 2012 +0530

    libglusterfs: Implementation of syncop_fsyncdir
    
    Change-Id: I832b9c0bfbe804fbca98dc9e8fbe7d3174fecc82
    BUG: 854326
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3902
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 17bb78c13fcbb62a4446fec944e7d8ce39a42b0c
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Sep 6 22:44:15 2012 +0200

    glusterd: fix mountbroker option parsing routine
    
    Properly adjust it to the new dict API as of
    http://review.gluster.org/3829.
    
    Change-Id: I8f55d2b1d590b15000984f4862c52b3cd226cef8
    BUG: 850917
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/3914
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8b6fe1072561c64f190db6f001f235bf9a30c138
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Sep 6 23:21:55 2012 +0200

    posix: adjust new xattrops to new dict API
    
    - http://review.gluster.org/3909 introduces new xattrops
    - http://review.gluster.org/3829 changes the dict API
    
    The new xattrops has been written against the old dict API,
    but been committed after the dict API change, resulting in
    a build error.
    
    Change-Id: I10b9acc79927f3505b5e13116653fb9a584ffd31
    BUG: 850917
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/3915
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ff4b227910903b0958bdd5437d6d93ddb54919ce
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 5 20:16:52 2012 +0530

    storage/posix: Add or_array/and_array op for xattrop
    
    Problem:
    For set/reset of outcast (ALL changelog bits set per transaction
    type i.e. data/mdata/entry) from afr the capability of OR/AND in
    xattrop is needed in posix.  Otherwise marking outcast will only
    be possible in self-heals where appropriate locks are held so
    that no other transaction is in progress, so exact number can be
    computed with which when XATTROP_ADD happens all bits will be set
    for that changelog.
    
    Fix:
    Implemented new xattrop-op OR_ARRAY, AND_ARRAY. Made checks in
    __add_array to work well with __or_array.
    
    Tests:
    From Afr code made an OR_ARRAY with ALL bits set and it reflected
    on the changelog xattrs. changelog incrementing did not have any
    effects on the all-set changelog.
    
    From Afr code made an AND_ARRAY with 0 and it reflected in the
    changelog xattrs.
    
    Change-Id: Ie89c78a43d05789e3a8fa03d2422b52083ae80b9
    BUG: 847671
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3909
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fb6c8f8b4efb113d302fd53910bbe5c321eafd7a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Sep 6 12:20:13 2012 +0530

    cluster/distribute: remove gf_log() from statedump functions
    
    Change-Id: I83cccab6819d6a74e96c2717ca539fa1568cac89
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 843822
    Reviewed-on: http://review.gluster.org/3912
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9c2fac537d04904b763fdf277355e9d856118f66
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Sep 3 10:40:36 2012 +0530

    mgmt/glusterd: Typo in the error message of the volume stop
    
    Change-Id: I86e4fdb48d9b29789f3446b8c0925eb81cf220c9
    BUG: 852999
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3892
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 632fdcaac9114282ecdaf1a88e3740565fda41c8
Author: Csaba Henk <csaba@redhat.com>
Date:   Thu Sep 6 17:52:11 2012 +0200

    cli: sanitize exit value
    
    The pattern established in http://review.gluster.com/3218
    as of which cli exits with negated return value of the
    command instrumentation function should be uniformly
    followed. (Prior to this commit whether cli exits
    with 255 or 1 on failure depended on the way of invocation.)
    
    Change-Id: Icbab1f435042b3321c689fa785109bf87195d86d
    BUG: 765214
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.org/3913
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cfbe7823b238171c0e63fa88c894f4a065ee7abd
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Aug 24 14:15:32 2012 +0530

    mount/fuse: If gfid is not present assign gfid
    
    Change-Id: I2fb8c607694eb8bbe5ec0f67d8db794066a89ca4
    BUG: 821138
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3854
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit be1d21a8795b215035f546c8da83df205afeb449
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Sep 5 13:07:49 2012 +0530

    core/statedump: parse the file and set the path of the statedump files
    
    * As of now "gluster volume set statedump-path" option sets the path of
      the statedump files for brick processes only. If SIGUSR1 is sent directly
      to all the gluster processes instead of using gluster cli command, then
      some of the statedumps will still be in /tmp (such as nfs server, glustershd).
    
    * This patch makes glusterfs processes search for the file
      /tmp/glusterdump.options and consider the options given in it. There if path
      key is set, then all the processes use that path when SIGUSR1 is sent or cli
      statedump command is executed. (Note that after taking statedump, if
      /tmp/glusterdump.options file is removed, then the default way is resumed).
    
    Change-Id: I2e8fbfb4823318512e03b234e90d3a3888724ddc
    BUG: 851175
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3907
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d6c99b6134f1eb90b3a8020c3538101df266e9b5
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Sep 6 00:13:04 2012 +0530

    libglusterfs/dict: make 'dict_t' a opaque object
    
    * ie, don't dereference dict_t pointer, instead use APIs everywhere
    * other than dict_t only 'data_t' should be the valid export from dict.h
    
    * added 'dict_foreach_fnmatch()' API
    * changed dict_lookup() to use data_t, instead of data_pair_t
    
    Change-Id: I400bb0dd55519a7c5d2a107e67c8e7a7207228dc
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 850917
    Reviewed-on: http://review.gluster.org/3829
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 54b71368ef290bc579f113e683a82b09893fb50a
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Sep 3 17:33:46 2012 +0530

    rpc/socket: Wrong Log-File Error-Message
    
    Problem:
    The port changed in rpc-clnt.c:rpc_clnt_reconfig was not being
    updated to the variable peerinfo.identifier before the logging.
    
    Change-Id: Ic56a74738c6f7664e9719b125a014126cea69141
    BUG: 847211
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3894
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8274d3e87a950eb7c11bb64e4d0716d0480980a5
Author: Varun Shastry <vshastry@redhat.com>
Date:   Thu Aug 30 17:23:41 2012 +0530

    License change to 2 additional files.
    
    Change-Id: I4689602cbea0e46498d10b8785bcde86d369e75d
    BUG: 852318
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3880
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 95e1c03d1572e6a84ee3d45bc3a48b001a708982
Author: Niels de Vos <ndevos@redhat.com>
Date:   Wed Sep 5 10:09:07 2012 +0200

    build: Don't use python-ctypes on SLES
    
    There is no python-ctypes on SLES 11, so don't require is for building
    the RPM.
    
    Change-Id: I3399318c1d2a603bb8d228ed4f1b5cbcb7a3a9c3
    BUG: 854503
    CC: Jörg Petersen <joerg.h.petersen@googlemail.com>
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.org/3906
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e1d24d45c56fd841c0a9a0a2ad32b08ebb2cd5b1
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Sep 2 07:11:04 2012 +0200

    Honour configure --localstatedir and --sysconfdir
    
    Makes sure /etc/glusterd to /var/lib/glusterd migration does nonour
    configure --localstatedir and --sysconfdir.
    
    BUG: 764655
    Change-Id: I65a5f96424d67531e81e75b084265bd4e6e30f29
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/3890
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9d0da50fdeb8ae235d34d7990a2bc28adf52434c
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Tue Sep 4 15:08:56 2012 +0530

    glusterd: Made volume reset recognize options in <domain>.<specifier> format
    
    PROBLEM:
    Volume reset command does not reset options when specified in
    <domain>.<specifier> format.
    
    FIX:
    Changed glusterd_options_reset to use "key" (as opposed to "key_fixed")
    to fetch "value" in a way that ensures "key" ALWAYS holds the option
    name in its fully qualified form, irrespective of whether the option
    was specified in its fully qualified format or in short form.
    
    Change-Id: Ibc3a87f4d29cb09e34b54c4b5ead564fefade350
    BUG: 847846
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/3901
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit a06a074b8cf3444acabca9003ae98539029453b0
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Sep 3 15:53:40 2012 +0530

    glusterd: Removed pattern match lookup logic on volume options
    
    In light of the comments received on the following patch,
    http://review.gluster.com/#change,3860
    this change knocks off the pattern match lookup logic that once
    enabled wildcard entries to be used for volume options.
    
    Here's a bit on the history of the macro "pattern_match_options",
    coming straight from the author's(Csaba) mouth:
    
    "So, the history of pattern_match_options is as follows:
    
    i. In the volume option table we used to be able to have wildcard
    entries like auth.addr.*.allow and there was a special lookup logic
    to support that, cf.
    http://github.com/gluster/glusterfs/commit/v3.1.0qa40~19
    
    ii. However, later on we stopped using this mechanism:
    http://github.com/gluster/glusterfs/commit/v3.1.0qa40~9
    
    iii. Later on we added the code that allowed the usage of option
    names both in fully qualified (<domain>.<specifier>) and short
    (<specifier>)forms:
    http://github.com/gluster/glusterfs/commit/v3.1.0qa41~10.
    
    At this point, maintaining support for wildcard table entries became
    more difficult (~ error prone), so that part was placed under the macro
    pattern_match_options and -- given that we made no use of the feature
    -- a simple direct lookup logic was introduced. I chose to keep the
    pattern matching logic in the code because I was not really sure about
    the future of it and thought we might want wildcarded table entries
    later. ..."
    
    Change-Id: I261735143891931e8150c36fe5b33ae74b1c663d
    BUG: 847846
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.org/3893
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit b80158698405f198a3d2b77ee5817d1096740600
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Mon Sep 3 17:59:05 2012 +0530

    cli: Do not print brick info for non-replicate volume
    
    Change-Id: I5e91df64ededd78371c0cd4d900f93ab4a0298ee
    BUG: 852406
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/3867
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit fad24c87cef0cc40c661614cd1cf1ab936311dcb
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Aug 29 14:43:30 2012 +0530

    cli, glusterd: Changes to 'peer status' xml output
    
    Glusterd now returns the status of a peer as both a string and a number.
    The xml output for peer status has been modified, such that the <status> element
    now contains the status number and a new <statusStr> element contains the status
    string.
    
    Change-Id: I0d4b74b84a991893d1029b8408d66ff078bbd254
    BUG: 847760
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/3868
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit b10eea2c44272bf491b670466430f4a6d1ac364b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Aug 30 19:01:22 2012 +0200

    Add missing contrib/libgen files to distribution
    
    BUG: 764655
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Change-Id: I3f49eb4a1a186cb2d178539ada6a05c8c1aa8265
    Reviewed-on: http://review.gluster.org/3882
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a9ba00f5e4f9f00464c109bc41ec73725722f692
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Aug 24 11:52:01 2012 +0530

    cluster/afr: Don't stop entry/data self-heal on metadata split-brain
    
    Problem:
    Entry/Data self-heal is orthogonal to meta-data self-heal.
    meta-data split-brain should not affect entry/data self-heal.
    
    Fix:
    Prevented aborting rest of the self-heals when metadata split-brain
    happens.
    
    Tests:
    1) Simulated meta-data split-brain then checked data-self-heal
    succeed on regular file, entry-self-heal succeed on dir.
    2) Reset meta-data change-log on one of the subvols and checked
    that meta-data self-heal also completes.
    3) Executed self-heal sanity script.
    
    Change-Id: I05ca222d855d3a6000703e3775471d0f874d35d6
    BUG: 851451
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3853
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <obdurodon@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e442b07f1d77e059e4b009adb4c9d0273850dcf5
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Aug 28 14:45:47 2012 +0530

    dht/rebalance: set the correct ownership on the dst file.
    
    Currently, the dst file created has root:root ownership, till
    migration is completed. During this phase, open fails on the dst
    file if uid/gid is non-root.
    Setting the dst_file to the correct ownership fixes the issue
    
    Change-Id: Icfec89eb10dc866cdee38dab17695fe21174ef99
    BUG: 852361
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.org/3861
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d81c03fce9b16f09744bfe0cea61c624fba093ea
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Aug 28 17:29:53 2012 +0530

    glusterd: Fixed incorrect assumptions in rpcsvc actors of glusterd
    
    Change-Id: Iabfcb401de9d658e32433aa1e8c87b329cbd2cf7
    BUG: 851109
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3864
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fbf2e9dfce3487c245715370abadd469a3bc744f
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Aug 28 13:12:31 2012 +0530

    glusterfsd: rpcsvc actors must return success after an attempt to submit reply
    
    rpcsvc attempts to send "error reply" using the req object. If actor has
    already performed rpcsvc_submit_generic, then req is destroyed. So if the
    actor returned -1 (RPCSVC_ACTOR_ERROR) on failing to submit reply, then req
    would be 'free'd' twice and will result in a crash eventually.
    
    Change-Id: I5eae19570202bbe5e154e9cb03390cfeb9b5f223
    BUG: 851410
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3863
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2ff5e1c2a1c0fedd437d2d892dfab21f720f5a1c
Author: Varun Shastry <vshastry@redhat.com>
Date:   Mon Aug 27 16:48:55 2012 +0530

    All: License message change
    
    The license message is changed to
      Copyright (c) 2008-2012 Red Hat, Inc. <http://www.redhat.com>
      This file is part of GlusterFS.
    
      This file is licensed to you under your choice of the GNU Lesser
      General Public License, version 3 or any later version (LGPLv3 or
      later), or the GNU General Public License, version 2 (GPLv2), in all
      cases as published by the Free Software Foundation.
    
    Change-Id: I07d2b63ed5fbbbd1884f1e74f2dd56013d15b0f4
    BUG: 852318
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.org/3858
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 4b4e9a058f5e591acb5b39df5113beb99258d7ef
Author: Thomas Oulevey <thomas.oulevey@cern.ch>
Date:   Thu Aug 23 11:50:50 2012 +0200

    init.d: Fix init.d on Redhat, so it does not always return 0.
    
    * Installing gluster with puppet, it gives an error if service "hasstatus => true" is used.
    * Introduced a $RETVAL variable set to previous command return value.
    
    Change-Id: I186ec59f892f04f25c06478315ca85183cb6232a
    BUG: 836007
    Signed-off-by: Thomas Oulevey <thomas.oulevey@cern.ch>
    Reviewed-on: http://review.gluster.org/3847
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 16e880a9580dc920dedf36856154cf791e7d040a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Sun Aug 12 13:29:10 2012 +0530

    afr: Avoid excessive logging in self-heal.
    
    - (Excessive) Logging has been very useful as 'bread-crumbs' in
      many a root-cause analyses. This patch aims at avoiding logging when
      the information could be reconstructed using the xattrs, statedump,
      and/or "volume heal" CLI commands.
    
    Change-Id: Iebc6b10ae18f0dd9704bdc6dd03bcfe0f2a09abd
    BUG: 844804
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.org/3805
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 058a736f9e36238c284ca80e7ed5f62434655019
Author: Deepak C Shetty <deepakcs@linux.vnet.ibm.com>
Date:   Fri Aug 3 15:46:22 2012 +0530

    Add support for --enable-debug configure option
    
    Currently default build adds -g -O2 to CFLAGS unconditionally
    and there is no way to control them from configure.
    
    This patch adds support for --enable-debug option to the
    configure cmdline.
    
    If yes, then only -g is added. If no, then -g -O2 is added.
    Build defaults to --enable-debug=no.
    
    Also fixes couple of Makefile.am's which had -g hardcoded.
    
    v2:
       Adds -O0 for debug=yes case.
    v3:
       Added bugID while submitting patch
    
    Change-Id: I7505619be6fc683de463a0bd44ba5500b0bedfe1
    BUG: 851092
    Signed-off-by: Deepak C Shetty <deepakcs@linux.vnet.ibm.com>
    Reviewed-on: http://review.gluster.org/3822
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Deepak Shetty <dpkshetty@gmail.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 99a0fcb7a46c996518a93c3975805f53108a4eba
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jul 30 13:05:52 2012 +0530

    socket: code cleanup
    
    * for more review friendly way
    
    * reduce the level of indirections at each line.
    
    Change-Id: I82ace7683fb281d97a64da724f054ece28215054
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 764890
    Reviewed-on: http://review.gluster.org/3839
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c57197c8fc1f3f6419a728a5f8b60457c468accb
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Aug 22 22:33:24 2012 +0530

    posix-acl: make use of 'umask' flag passed as argument in fop
    
    * currently "umask" is reffered only from xdata dictionary, instead
      we should utilize fop argument.
    * not taking of setting of "umask" in fuse for now, considering the
      backward compatibility with earlier releases.
    * dict_del() the "umask" and "mode" keys from xdata dict as the fop
      after reaching posix layer tries to set every entry in xdata as
      xattr on file/dir.
    
    Change-Id: I7199b05a5bde132df20e7812a99bc02ef7b988ce
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 850873
    Reviewed-on: http://review.gluster.org/3843
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c48387d8e43f83b06acf329ece6c0278a7911d1e
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 22 02:10:36 2012 -0700

    epoll: whitespace cleanup and remove unused variable
    
    Change-Id: Idd7269f8b3a6dfaf931b378128eff93088b3be73
    BUG: 821087
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3841
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 49ba15d599a8979d1d3df7a39204d52081d8719e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Aug 20 23:46:03 2012 +0530

    fuse: make background queue length configurable
    
    * also make 'congestion_threshold' an option
    * make 'congestion_threshold' as 75% of background queue length if
      not explicitely specified
    * in glusterfsd.c, moved all the fuse option dictionary setting
      code to separate function
    
    Change-Id: Ie1680eefaed9377720770a09222282321bd4132e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 845214
    Reviewed-on: http://review.gluster.org/3830
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4dc4e4b770fc5fa1aeebc41223ede9195ede4965
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Aug 4 12:21:42 2012 +0530

    syncop: Added scaling down logic
    
    RCA:
    Whenever the self-heald tests are done with more than 16 replicates
    The number of sync procs goes to > 2. These threads never die.
    
    Fix:
    Added scaling down logic in syncops so that the threads terminate
    themselves whenever the extra thread is idle for ~10 minutes.
    Minimum number of threads is still 2.
    
    Tests:
    Added logs for launching and terminating procs, made timeout to
    6 seconds and ran volume-heal in a while loop. After logs say
    max number of procs are launched, attached process to gdb and
    verified that the number of syncop threads are 16. Stopped
    volume-heal and observed the logs for terminating the procs.
    Attached gdb to process again to check that the syncop threads
    are just 2. Did this 5 times. Things worked fine. Which procs
    were terminated was random. No proc structure was erroneously
    re-used. Procs never exceeded 16 and were never < 2.
    
    Change-Id: I61dd9c25cc478ac8cbda190bee841a995b93c55c
    BUG: 814074
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.org/3195
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 428ff73e5f1bcb4c77f48cf38bc2059245eefec4
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Tue Aug 21 05:11:07 2012 +0200

    NetBSD build fix
    
    BUG: 764655
    Change-Id: I65009625dfa627e0ca3b7ff2784b778d26ec04b1
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.org/3837
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fb1d42df1679332f2a729b16171b0c72383c9918
Author: Anand Avati <avati@redhat.com>
Date:   Mon Aug 20 09:46:33 2012 -0700

    rpcsvc: remove .vector_actor and related changes
    
    The .vector_actor method of rpcsvc_actor_desc is defunct now after
    rpc unification. Remove the field and all related usage of it.
    
    Change-Id: I53048cebeae78f50259e8c4a7fec3497691fe388
    BUG: 762935
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.org/3832
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit defc74df52c0afdd10736f21ca7d5a2a4c2cd0e6
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Fri Aug 17 12:44:46 2012 +0530

    Self-heald: Prevent logging of errno ENOENT
    
    Change-Id: Ie56228dfbdc7e519a344681487164a835488a470
    BUG: 835423
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.org/3826
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7bf3723fba2dc7d2896fc2a6e5b5f65db0b8c179
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Aug 13 18:57:20 2012 +0530

    cli: Proper xml output for "gluster peer status"
    
    Change-Id: I5d72d3844aba0417652498f4dc706b4a68d36bd8
    BUG: 847760
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.org/3814
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <krishnan.parthasarathi@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2f2e3bfb5ef89b5ba266a3df7496f95b11fb93e1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Aug 17 14:21:07 2012 +0530

    syncop: handle 'dataonly' flag in syncop_fsync()
    
    * and also in syncop_readv(), don't look at _cbk args if op_ret
      is < 0.
    
    Change-Id: I3ab2982bc6d186e75b6adb74c8981e4ff7058bbe
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 839950
    Reviewed-on: http://review.gluster.org/3828
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 99f0daf2f46d56b78adfe1a3df1195e1388feaab
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Aug 9 13:12:31 2012 +0530

    performance/write-behind: avoid deadlock while taking the statedump of fds
    
    * Provide a hook for forget
    
    Change-Id: Ide7ea6d4c6a7d0d93b81570cb544f2bbda526eeb
    BUG: 846916
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.org/3795
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b757819289b014dbf706b26ca17f6cb584301ffc
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Aug 8 18:42:24 2012 +0200

    cluster/dht: don't leak upon GF_REALLOC failure
    
    Change-Id: I7dfabcc2981df5c5a1e1a54c3135400a60626cd1
    BUG: 846755
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3798
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7daa85508314838ce8f0c2cb731827d0f92eb5ee
Author: Jim Meyering <meyering@redhat.com>
Date:   Tue Jul 31 12:27:02 2012 +0200

    gsyncd: don't use void* arithmetic; don't leak upon OOM; remove cast
    
    (duplexpand): Ignore risk of overflow in computation of the realloc
    object count, since we'd need a string with 2^62 space-separated tokens
    to trigger that (that's w/64-bit size_t; w/32-bit it'd be easier, but
    still improbable).
    
    Change-Id: If4521afe7b46110742991dd0ee234284ef8970df
    BUG: 846755
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3793
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d22726cf8a76167acd63a9af7233b798a1e484f2
Author: Jim Meyering <meyering@redhat.com>
Date:   Thu Aug 9 14:29:57 2012 +0200

    utils: don't leak after failed GF_REALLOC
    
    This is primarily to avoid a leak upon failed GF_REALLOC
    when glusterd_readin_file reads a file that is too large.
    Also, remove unnecessary memset-0 of PATH_MAX+256-byte buffer.
    
    Change-Id: Id06bd5faef024e1d865f6f0f56bfbb837c9c6168
    BUG: 846755
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3804
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 602b0193775bc78768390be08488c3b0aa5601fb
Author: Varun Shastry <vshastry@redhat.com>
Date:   Tue Aug 14 14:21:30 2012 +0530

    cli/: Displaying the size in human readable format
    
    rebalance status displaying the size in bytes. Converted to
    human readable
    
    Change-Id: Ie39938970f92bf7507db2a6de4d5958408f3892c
    BUG: 825193
    Signed-off-by: Varun Shastry <vshastry@redhat.com>
    Reviewed-on: http://review.gluster.com/3781
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>

commit 3e62998978d3e6735a1857b4082e8c39dfd327d2
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Aug 14 14:45:28 2012 +0300

    fix "--client-pid"
    
    http://review.gluster.com/3698 broke special clients by omitting the
    conversion of the client_pid_set parameter to the new xlator option
    framework.
    
    Change-Id: I0dc886dffba9c4a9fe8d97e5feccfa5f95784ce1
    BUG: 848034
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3820
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6e3244a131b6d25141bef0cbc59968d3271f8ea3
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Aug 15 17:27:52 2012 +0200

    fuse: have setxattr on geo-rep related xattrs take effect
    
    In http://review.gluster.com/3687 setxattr was made to a noop for
    geo-rep special clients, with the exception of some special ones,
    relevant to geo-rep. These exceptions were all in trusted namespace.
    
    That's no good, because with a mountbroker (unprivileged) setup,
    the relevant attributes are in system namespace. So here we
    just let setxattr through for any geo-rep related xattr, regardless
    of namespace.
    
    Change-Id: I261141293b7db955a2e8b2405b4510cb10a42694
    BUG: 848447
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3821
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 623dbe5afc1cfd1e22064a4e60750289b2ef6b0e
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Thu Aug 16 13:27:00 2012 -0400

    misleading/wrong keep-alive error message in log
    
    Gluster NFS and brick logs contain the following log entries:
    
    [2012-08-16 09:23:39.498998] W [socket.c:410:__socket_keepalive] 0-socket: failed to set keep idle on socket 8
    [2012-08-16 09:23:39.499049] W [socket.c:1876:socket_server_event_handler] 0-socket.glusterfsd: Failed to set keep-alive: Operation not supported
    [2012-08-16 09:23:42.673756] I [client-handshake.c:1636:select_server_supported_
    
    Stepping through the code though, setting keep-alive did actually work,
    it's the keep-idle that failed.
    
    The actual problem is setting keep-idle on non-AF_INET sockets results
    in the spurious error message in the log.
    
    BUG: 848882
    Change-Id: I3a54c96aea0642307f17a7945cca9f9438543243
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3823
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6930c6950f7b7a8186ebfcdf9ebcad11e90740c0
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Aug 9 19:29:33 2012 +0530

    rpc: Reduce frame-timeout for glusterd connections
    
    Reduce frame-timeout for glusterd connections from 30mins to 10 mins. 30mins is
    too long when compared to cli timeout of 2mins. Changing to 10mins reduces the
    disparity between cli and glusterd.
    
    Also, fix glusterfs_submit_reply() so that a reply is sent even if serialize
    failed.
    
    Change-Id: Id5f68f2ff28ea7453d9a62429fe12aa0c0a66952
    BUG: 843003
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3803
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit acf73966abd3ad3fe341a933f76c821e19fd7b95
Author: Anand Avati <avati@redhat.com>
Date:   Tue Aug 7 00:14:43 2012 -0700

    rfc.sh: set 'Change-Id: ' header on first run
    
    Let first run of rfc.sh include 'Change-Id:' as well
    
    Change-Id: I7b45a00d98f8c70ca3658c223a98f412f20cbb6f
    BUG: 764890
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3785
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e404e9b81f18c0a36a5c67ebf041ac0a00ca2eb1
Author: shishir gowda <sgowda@redhat.com>
Date:   Tue Aug 7 12:55:31 2012 +0530

    cluster/dht: Optimize readdirp calls in DHT
    
    Bring in option which is supported by posix xlator
    to filter out directory's entries from being returned.
    DHT would now request non-first subvols to filter out
    directory entries.
    
    dht xlator-option readdir-optimize will enable this
    optimization
    
    Change-Id: I35224bc81c9657f54f952efac02790276c35ded5
    BUG: 838199
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.com/3772
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cdf6ad3695b0842acc3d4aadc5ebb474f07e8913
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon Aug 13 06:35:18 2012 +0200

    NetBSD swapcontext() portability fix
    
    Further analysis of the problem reveals some wrong conclusions I made
    before. NetBSD's swapcontext() preempts no thread. It alters the
    pthread private pointer, leading to multiple threads with the same
    pthread pointer. That led me to the wrong conclusion that thread were
    preempted. I guess this can be called a bug: NetBSD swapcontext()
    is incompatible with libpthread.
    
    Fortunately, there is a workaround, swapcontext() can be told to
    let the pthread private pointer untouched. This change just does
    that, fixing the crashes without sacrifying performances.
    
    There is just one problem: not all NetBSD ports have the capability
    to do that: at least ports using sh3, sparc, sparc64 and powerpc
    are left broken by this change. This problem will be addressed by
    upcoming fixes in NetBSD.
    
    BUG: 764655
    Change-Id: I4191cb984176fce7064730ab55bd62c9156846cd
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3794
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit eabf3911675562a920040d0fe1a783ece1beb341
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Aug 9 13:23:48 2012 +0530

    performance/write-behind: store the wb_inode in local before winding
    
    * Store the write-behind's inode context in the local structure before
      winding the call so that in callback inode context is found.
    
    * Before returning EBADFD check if the inode context (wb_inode) is NULL,
      along with the inode type.
    
    Change-Id: If5a1c667efe6882a6efef1439cee3effc32ff9a7
    BUG: 846536
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3796
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit e42faa7488b41513750ad37837ac52a68f639775
Author: Jim Meyering <meyering@redhat.com>
Date:   Thu Aug 2 10:51:40 2012 +0200

    fuse-bridge: fuse_thread_proc: avoid realloc-clobber induced leak upon OOM
    
    Change-Id: I835d14b702b875bb07f41e157583592df9b72f36
    BUG: 846755
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3792
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 94271805633a1ee5487b036dfd81b63c0250df39
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Aug 8 17:11:52 2012 +0200

    geo-rep: don't leak or segfault upon OOM
    
    In glusterd_urltransform, a failed GF_REALLOC would clobber
    the would-be-realloc'd buffer, linearr, with a NULL pointer,
    (thus leaking that memory) and then control would pass to the
    error-handling code that would attempt to free
    (via glusterd_urltransform_free) linearr[i], which is almost
    guaranteed to segfault when linearr is NULL.
    
    Change-Id: Ia75bf70fd8ff893a18804d49688048ef96db6037
    BUG: 846755
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3791
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bfac66f129646bc78f1ed3a7dccb3010114e57aa
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Aug 7 13:13:24 2012 +0530

    logging: do the 'right' check for loglevel
    
    logging functions should not print anything if loglevel in argument list
    is lower than what is set for the process.
    
    Change-Id: Id61779ffe6b76724243aa222c6889dd51a8f2f9b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 846201
    Reviewed-on: http://review.gluster.com/3786
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 828b2b7059093972381bc64047025a7d8cac508e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Aug 7 10:03:47 2012 +0530

    core: moved back the pthread_key_t specific variables as global
    
    in a patch to move all the global variables inside 'ctx', moved all
    the pthread_key_t specific globals, which needed to be global, not inside
    some structures.
    
    Change-Id: I5e7107a8a64f5b80e90fd469fb084f62b2312705
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 764890
    Reviewed-on: http://review.gluster.com/3783
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 87d453f7211d3a38113aea895947143ea8bf7d68
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Aug 5 20:32:53 2012 +0530

    glusterd: while building graph, set xl->ctx
    
    as glusterfs_'ctx'_t  is used as reference in many places, it is
    important to set it right. In many places, xl->ctx is assumed to
    be present, hence it has to be set right.
    
    Change-Id: I37d767f384edb1819277c4ecee97dd94108aedff
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 845715
    Reviewed-on: http://review.gluster.com/3779
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ed4b76ba9c545f577287c0e70ae3cc853a0d5f3f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 2 13:14:25 2012 +0530

     core: reduce the usage of global variables
    
    * move all the 'logging' related global variables into ctx
    * make gf_fop_list a 'const' global array, hence no init(),
      no edits.
    * make sure ctx is allocated without any dependancy on
      memory-accounting infrastructure, so it can be the first
      one to get allocated
    * globals_init() should happen with ctx as argument
    
    not yet fixed below in this patchset:
    * anything with 'THIS' related globals
    * anything related to compat_errno related globals as its
      one time init'd and not changed later on.
    * statedump related globals
    
    Change-Id: Iab8fc30d4bfdbded6741d66ff1ed670fdc7b7ad2
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 764890
    Reviewed-on: http://review.gluster.com/3767
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 66205114267ec659b4ad8084c7e9497009529c61
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon May 14 14:23:56 2012 +0530

    mount/fuse: ignore any erros that might've happened while resolving entry in resolver.
    
    One error we hit was absence of gfid on backend. While the lookup
    code-path generates a new uuid and sets it on file, resolver code
    doesn't do that. Since, functionally (atleast after resolving parent
    inode, we would be resolving the path in new-graph) both resolver
    and lookup does same work, it would be no harm in ignoring errors
    during resolving the entry. This would help us to continue with
    the _extra_ work (like healing gfid as of now) in fuse_lookup_resume.
    
    Change-Id: If46d5e07c32e67b5744287a6ef55d0b0fe347689
    BUG: 821138
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3344
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8a1dedca925fe99860f61b554b7c86d8c1302596
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Aug 3 12:11:46 2012 +0530

    mgmt/glusterd: Fix a compilation failure when libxml2-dev is not present
    
    Addresses problem introduced by 1e4a2354b57a1eb
    
    Change-Id: I7cea76410769c584af6960860260fbd061a6df8a
    BUG: 844696
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3778
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6731020700b949e1e7351d8e5d390f329bf4fba2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 26 18:44:14 2012 +0530

    fuse-resolve: consider cases where an entry should be resolved even when parent belongs to active itable.
    
    When parent is root, the parent inode returned will always be
    active_subvol->itable->root and hence there can be cases where we
    should explicitly resolve the entry in active graph.
    
    BUG: 804592
    Change-Id: I5829278e27435e06785a923ce8776616cedfb519
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3710
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2e1d2c96f544772ed4f1c8eb66c1d5e9f4a01484
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 31 12:02:22 2012 +0530

    performance/io-cache: use pthread_mutex_trylock to hold mutex in statedumps
    
    Do not use pthread_mutex_lock and gf_log functions while dumping information
    to statedump, to avoid deadlocks.
    
    Change-Id: I2bb4592126c5d1eacf614130815a839c4a90c59a
    BUG: 843787
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3758
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1e4a2354b57a1eb173f31a15bf96b2e174fa34a5
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Jul 31 11:31:16 2012 +0530

    glusterd: Made volume set help/help-xml a non-cluster operation.
    
    - Retained apparent redundant checks in stage, commit phase of set
      volume for the help options for backward compatibility
    
    Change-Id: Iaefe3805d6b5eeeced2e7e4870830edf3e61dc87
    BUG: 844696
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.com/3761
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 36827add0f55d674768ff9c90c5fbb636ae99054
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Aug 1 16:28:13 2012 +0530

    performance/quick-read: use pthread_mutex_trylock to hold mutex in statedumps
    
    Do not use pthread_mutex_lock and gf_log functions while dumping information
    to statedump, to avoid deadlocks.
    
    Change-Id: I0d30b04ae322f131b7a42d277ebd4385e83769e6
    BUG: 843789
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3764
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c8ed0096d53de3e39feee5b857b6b657118bc0a1
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 25 22:39:13 2012 -0700

    glfsxmp extension
    
    Change-Id: I3859621637025e464bc83d748bae7dff9808643f
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3735
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 1b42c864d64b0b9af06d251797fba70334d84f67
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 25 23:24:11 2012 -0700

    gfapi: let glfs_init() return on non-RPC errors
    
    Change-Id: Ic3a15044434926127b8de273b1033b8ad452290c
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3732
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a3072499338b2d86f5cc3ac83f49c5249dc97778
Author: Anand Avati <avati@redhat.com>
Date:   Wed Aug 1 23:18:40 2012 -0700

    gfapi: set errno in glfs_init()
    
    save errno from glfs_init_done and set it in glfs_init_wait()
    
    Change-Id: I1a2f43a7e7b0f07f279c175df987ff94d642b629
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3771
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a9e3e24dd3c1afe7cb573b653040478a0f1210e6
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 25 23:33:33 2012 -0700

    gfapi: missed setting port option
    
    Change-Id: I72790de10cefaae3d3307b6fbb9899907b019ccc
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3733
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Bharata B Rao <bharata.rao@gmail.com>

commit e7897b80ba38066af2dc306b98c466e9cfe87e81
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Aug 2 20:37:39 2012 +0530

    glusterd: Fix glusterd crash resulting from uninitialised pointer
    
    PROBLEM:
    glusterd crashes during replace-brick operation as the
    pointer old_brickinfo is dereferenced without being initialised.
    
    FIX:
    Have old_brickinfo initialised to point to the brick info of
    the brick being replaced before dereferencing it.
    
    TEST:
    Ran glusterd in debug mode before and after the fix;
    process crash ceased in the latter case.
    
    Change-Id: I53f21b5424f534bbdba3b3fc407d4501a2c0052f
    BUG: 844332
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.com/3777
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5f766567423ba8272f29397fe36da1fd2186ffaf
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Jul 31 17:04:44 2012 +0530

    cluster/afr: Unwind with correct pre/post parent bufs
    
    RCA:
    In case of dir fops create, mknod, mkdir, link, symlink, rename
    if the fop fails on read-child then unwinds are happening with
    all-zero pre/post iatt-bufs. The bug occurs because the parent
    bufs are not saved if the response is not from read-child.
    
    Fix:
    Save the pre/post-bufs for the first response. If the response
    comes from read-child, overwrite whatever we have cached.
    
    Tests:
    Attached the mount process to gdb.
    Tested that the unwinds happen with proper pre/post iatt bufs in
    the following cases:
    1) All success case
    2) Failure on read-child
    3) Failure on non-read-child
    4) Failure on all children.
    
    Tested soft-link self-heal to test the change made in that.
    Tested errno ENOTEMPTY for rmdir, rename fops.
    
    Change-Id: I82882423d2d766b4f4a3044203bcb5dbcaee1755
    BUG: 845242
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3775
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a89871f9c7a4c42e87f2d856b51f33ceaf1cf163
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jul 31 12:41:13 2012 +0530

    performance/write-behind: maintain a per-inode request queue instead of maintaining per-fd
    
    path based operations like stat etc, whose results will be affected by
    writes have to be ordered with writes. With request queues maintained
    in inode this can be done naturally, than when they are maintained per
    open fd.
    
    Change-Id: Ibdde3b81366f642d07531632fc9062cb44fad2e7
    BUG: 765443
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/712
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b25eba06d5d50543975d24a0dc0a3a1934faf40b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Aug 2 16:23:08 2012 +0530

    protocol/server: use pthread_mutex_trylock while dumping statedumps
    
    Change-Id: Iec6f539ee7d36c25aca3960abc6d2611707617c8
    BUG: 843821
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3774
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 91bf4e5137b56cf52162e30db92df02ef9964b10
Author: yinyin <maillistofyinyin@gmail.com>
Date:   Wed Aug 1 21:08:22 2012 +0800

    rpc-lib: fix rpc_clnt_reconfig log on remote_host change
    
    Change-Id: I5446d7fb975d4fb8105264e026fef165ae73a925
    BUG: 764890
    Signed-off-by: yinyin <maillistofyinyin@gmail.com>
    Reviewed-on: http://review.gluster.com/3773
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 53011831614791b6858bf9735fe96d59a1a29f1e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jul 30 21:01:21 2012 +0530

    cluster/afr: Handle child_up & fd not opened case in xaction
    
    RCA:
    When an fd is opened while a brick is down, after the brick
    comes back up afr issues open on the other brick. It can
    fail for a number of reasons (enoent etc). While the system
    is in that state, inode/entrylks pre-op happen only on the
    brick that is up and fd is opened for fd-fops. post-op should
    consider only the bricks where both pre-op and fop succeeded
    as success, rest of them as failures. Code now marks only the
    children that are down as failures as opposed to child_down &
    fd-not-opened. This makes change-log appear as success on the
    subvolume where we did not do any fop leading to no change-log
    but differences in data/metadata for reg-files.
    
    Fix:
    Mark non-participants of fop as failure. This is tracked in
    transaction.pre_op[].
    
    Tests:
    Simulated the scenario using err-gen on top of one of the client
    xlator which fails all fops always. Performed fops and the changelog
    represented pending fops on the brick with err-gen loaded. Tested
    the case of brick down and perform entry/metadata/data operations
    to confirm they still work as expected.
    
    Change-Id: I41905936126b19abba56ca581c0301a894507e1a
    BUG: 844987
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3765
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9c8fe5beb872f5e1d7824b292cb97b47289cb6bd
Author: Jules.Wang <lancelotds@163.com>
Date:   Wed Aug 1 09:37:09 2012 +0800

    mem-pool: remove 'if' by asserting condition directly.
    
    before:
    
    if (!condition) {
        GF_ASSERT (0);
    }
    
    after:
    
    GF_ASSERT (condition);
    
    BUG: 764890
    Change-Id: I9894fcc609579f5efd3f98dbff41ca1487ce6dd2
    Signed-off-by: Jules Wang <lancelotds@163.com>
    Reviewed-on: http://review.gluster.com/3762
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 980f99e29eed340baf8c9bdcc5d85a36794bde20
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 5 16:58:56 2012 +0530

    cli: more clear separation of error messages
    
    the intention is to make CLI output more script friendly.
    use ':' as field separator per command and each field should
    be meaningful.
    
    this is phase-1 of the change, and hence RFC, once I get review
    comments, will be doing more changes, if required
    
    Change-Id: I11e70084f78a197ac50f9401dd7af312e63647ef
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815194
    Reviewed-on: http://review.gluster.com/3753
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7d21da4cef50bc43d3b3cfca54d6c9a03ed645a8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 2 00:34:52 2012 +0530

    supportability: print all missing frames
    
    earlier, the statedump and backtrace were printing frames only if
    it matched type GF_FOPs or GF_MGMTs (GF_MGMT is not in use now).
    This made all the frames from glusterd, or any other frames which
    got created outside the scope of 'fops' not getting printed.
    
    now, made two classifications, one as FOPs (which gets logged
    with the proper name), and another set is !FOPs (ie, else part),
    which gets logged with only the op number.
    
    Change-Id: Ifa18cdb75f7afefe6bb489d319b589cda8e64c1d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 845114
    Reviewed-on: http://review.gluster.com/3768
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7004dd1d50dc24910832c549af3808c83c63c671
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Aug 2 01:42:38 2012 +0530

    core: remove libglusterfs/src/scheduler.[ch]
    
    * as its not part of the build
    * confuses with some TAGS and 'git greps'
    
    Change-Id: I1f97307a8ce486ba56a4a3ad0151276b0a72e096
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 764890
    Reviewed-on: http://review.gluster.com/3769
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a5341ef545b1568cbe33db80f62950e428ede98a
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Aug 1 16:38:34 2012 +0530

    performance/read-ahead: use pthread_mutex_trylock to hold mutex in statedumps
    
    Change-Id: I4491c96fc7d9879ba9040dcda3700c81d99ba184
    BUG: 843796
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3766
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3bf5cd69c6c8997b089ad9d007c72cfd92c7f44e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jun 6 17:34:03 2012 +0530

    event-history: implement gf_log_eh for saving events
    
    Change-Id: I2ddf4e7849bda91bb99423e27082c2bae6800a70
    BUG: 795419
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3532
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d3a8a50a9da28cd12277ffac25767a790761d32f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 1 12:09:38 2012 +0530

    mount/fuse: initialize entry and negative timeouts correctly.
    
    There was a typo which resulted in updation of attribute_timeout
    for both options.
    
    Change-Id: I6e212eaf3570cadde88d2a2c3b44121c893c9427
    BUG: 804592
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 5070aa3973066ba7347b14b4b993dcde11e08165
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Mon Jul 30 22:31:31 2012 +0530

    protocol/client: Fix negative return in client_setvolume
    
    PROBLEM:
    The function dict_serialized_length could, owing to an error,
    return a negative integer (-EINVAL) that gets assigned to an
    unsigned int member 'dict_len' of gf_setvolume_req structure.
    
    FIX:
    Hold the value returned by dict_serialized_length in local
    variable ret (which is a signed int). Test if ret is negative,
    in which case the control would anyway branch to the label fail
    where the function returns. Otherwise dict_len is assigned with
    ret, in turn giving a more meaningful value to the attribute
    length.
    
    TEST:
    Attached gdb to glusterfs mount process, set breakpoint at
    client_setvolume, forced dict_serialized_length to return
    -EINVAL (indirectly by forcing _dict_serialized_length to return
    -EINVAL after setting count to -1 within its body) and checked
    the value of ret (which is now sure to contain a negative value)
    whose value will be appropriately tested to decide the next
    course of action within client_setvolume: whether to simply
    exit due to an error or execute the subsequent statements.
    
    Change-Id: Ib22ad8f30d8ae04acaf2ff5bfee9c348a2c47148
    BUG: 789278
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    Reviewed-on: http://review.gluster.com/3755
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9fcc3f4dede2829d457b6e1c76f53c25ba790988
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jul 25 20:46:53 2012 +0530

    cluster/afr: Handle failures in fop_cbk gracefully
    
    RCA:
    Afr crashes when a last fop response fails and
    'fop output' arguments are NULL. Afr does not handle
    these gracefully.
    
    Fix:
    Changed the fops to not access the 'fop output' arguments
    in case of failures.
    
    Tests:
    Changed afr wind_cbk code to fail the last response by setting
    op_ret as -1 and op_errno as ENOMEM and setting all other output
    variables as NULL to test the change. Removed the code to verify
    success cases. No crashes or errors seen.
    
    Change-Id: Iad9bc54db093a162f85bfb8dbeeda5b95acd21d8
    BUG: 844689
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3760
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b18c913f58aadcadb830b59d8ed8979d18c0e0d0
Author: M S Vishwanath Bhat <msvbhat@gmail.com>
Date:   Tue Jul 31 16:28:27 2012 +0530

     Fix issues in make dist
    
    Change-Id: I2fb3b0b35e2b5fdb08ee1857bf31ec8f65889306
    BUG: 844669
    Signed-off-by: M S Vishwanath Bhat <msvbhat@gmail.com>
    Reviewed-on: http://review.gluster.com/3759
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b21395aee3b5676f94231165f492f776133ff507
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Jul 29 20:22:07 2012 +0530

    cluster/afr: update loc inode after inode_link
    
    RCA:
    inode passed to inode_link is not assigned any gfid if the
    inode with that gfid is already linked, so loc for opendir
    does not have a valid inode
    
    Fix:
    Use the linked_inode returned by inode_link in the loc to
    perform further operations on the entry.
    
    Tests:
    Checked that opendir comes with an loc with valid inode.
    Checked that re-opendir happens successfully. Tested index,
    full self-heal work fine with the fix.
    
    Change-Id: Idf4ced4cc2320133744962059d363e373af0e5ec
    BUG: 826580
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3748
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7e892ac95a4dd4c38ca793ef1b987cd24758ec4d
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jul 19 20:08:57 2012 -0400

    rpc/socket: finish initialization in own thread
    
    ...if we have one, that is.  This addresses Avati's review comment on
    ea7759f1240b1e97684273b9369472695173a66.
    
    Change-Id: I71a272f7eeff8279981a75241d60620ca4975c99
    BUG: 764731
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3701
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5c89c315e7dba0e57605b71ec93720b4f74ea21d
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jul 5 14:30:38 2012 +0530

    glusterd: Modifed replace-brick mount cleanup to use lazy umount
    
    Change-Id: I83a985967cbaee4927f1b8ca4bc01c9fb0171522
    BUG: 806890
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.com/3143
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 879c01087d58742515524664e8a193a04a0d4146
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Jul 19 15:01:13 2012 -0400

    cluster/stripe: handle short writes and errors in writev callback
    
    cluster/stripe write callback handling is broken in the event of
    server side errors and short writes due to crudely summing up the
    return values from each node. This can produce incorrect results
    or cause an application to rewrite the wrong portions of a buffer
    in an attempt to handle this condition.
    
    Modify cluster/stripe writev handling to record the requested size
    of each write and use this data to return the number of consecutive
    bytes written from the original request. This allows an application
    to retry a write at the point of error (and potentially consume
    said error).
    
    BUG: 809975
    Change-Id: Ic35cb1e092c29545205aa32e352485c507534ce0
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3700
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b3025cb8dd79751c12b7bb375ec701b532688cbc
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jul 26 12:50:05 2012 +0530

    performance/io-threads: dump the io-threads specific information in statedump
    
    Change-Id: Ib9b9eab2d2e90fce21ef32f0f884101938978859
    BUG: 843377
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3736
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 224227ef6612680b191bef143b75c7929f9a4c34
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Jul 30 14:48:08 2012 +0200

    geo-rep / gsycnd: restore the generic signature for sendmark_regular
    
    Earlier fixes to 842330 changed the generic (*a, **kw) signature,
    although that was not related to the issue.
    
    We restore the generic signature as it was used for a reason
    (proxy methods that do none or only algebraic transformations
    on passed arguments idiomatically have generic signature, both
    to serve as visual cue and agnosticism wrt. the inner API).
    
    Change-Id: Ib609a3a58be53d78b7f1221a3c162c6aec8fd488
    BUG: 842330
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3754
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9181871ff49a5b1e5b1acc9c8a96c99d28e80a5e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jul 25 06:27:57 2012 +0530

    libglusterfs/statedump: add start and end markers in the statedump file
    
    Also do not overwrite the statedump file if statedump is taken on the same
    process again. Instead add the timestamp to the filename
    
    Change-Id: I451a0decf2dad5c398631cab1fc2a69811c69af8
    BUG: 843408
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3738
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 331c8d44d8e2781150c9bea56f36576a9dda0d6f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Jul 27 10:51:50 2012 +0530

    performance/io-threads: Provide option to turn off least-priority
    
    RCA:
    In cases when self-heal is in progress, self-heal fops are starved
    because of least-priority. This affects other fops with conflicting
    inode, entry locks with self-heal.
    
    Fix:
    This patch provides configuring enable/disable of least-priority.
    
    Additional changes:
    Moved RCHECKSUM fop to low instead of least because it will still
    affect the performance of other fops if RCHECKSUM is in LEAST
    priority.
    
    Tests:
    Tested that the enabling/disabling of fops is working fine.
    Tested that RCHECKSUM fop priority is assigned LOW when
    least-priority is disabled.
    
    Change-Id: I8d72872b33e2ac7e1ad3afb27582682b0eb98a80
    BUG: 843704
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3743
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 96d5c52b7e9e4c4a654213e092dde9c54282fe64
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 19 13:45:25 2012 +0530

    volgen: add option to add trace/error-gen in client volume file
    
    bash# gluster volume set <VOLNAME> debug.trace client
    bash# gluster volume set <VOLNAME> debug.error-gen client
    
    would add the corresponding translator in client volume file just
    below io-stats translator. (gets added even in nfs volfile)
    
    Change-Id: I698eb9b348c59aaff9967a4e238fabfc40e69a11
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 782262
    Reviewed-on: http://review.gluster.com/3699
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 86e326921e29bc39f2ea4efe6a1882199de18a79
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Tue Jul 24 12:44:11 2012 +0530

    glusterd: Persisted hooks friendly user.* keys
    
    - Fixed validation of user.* keys in presence of multiple key, value
      pairs in a single volume set command
    
    Change-Id: I5b96de2d009fbc79772121308d9b4c0a552bac52
    BUG: 825902
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.com/3715
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c9b96e26a3bab09a4146b2bec57a57c69b9aa8b7
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Jul 28 12:18:50 2012 +0530

    features/locks: Fix statedump code
    
    RCA:
    Taking blocking mutex/spin locks lead to dead locks
    because of the locking order in statedumps. Also we
    were asked to remove gf_logs if possible to avoid extra
    cost in signal handlers.
    
    Fix:
    changed blocking mutes/spin locks to their non-blocking variants.
    Removed gf_logs in locks xlator statedump code-path.
    
    Tests:
    State-dump success cases are working fine.
    Triggered try-lock failures by putting statedumps in a while loop.
    In parallel did chown of the same file in a while loop.
    
    Change-Id: I81539a62f8216f267f57bb703ef132c85bfd557d
    BUG: 843781
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3747
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c2859a6039ecb74a4b88989326fa538d1d5b06c2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Jul 28 07:49:36 2012 +0530

    cli: Prevent creation of volumes with tokens as volnames
    
    RCA:
    yyparse confuses volnames with tokens when any of the
    tokens 'volume', 'type', 'subvolumes', 'option', 'end-volume'
    are used as volnames. This happens because io-stats xlator
    name is same as volname in fuse volfile. Both nfs, fuse volfiles
    are affected by this problem.
    
    Fix:
    We could fix this also by changing io-stats xlator name to
    something other than 'volname'. But I am worried of the
    backward compatibility issues it may introduce. Disallowing
    creation of volumes with tokens as volname seems like a safer
    fix.
    
    Tests:
    All volume creation operations with tokens as volname give
    invalid volume name error.
    
    Change-Id: Ifc63a5c31375e92541b954ec133aa3c8e6a56a02
    BUG: 844030
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3745
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6a5e047bc56fc80a0f87f3a44056ffc38ba68c25
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Wed Jul 25 16:56:31 2012 +0530

    glusterd: Ensured 'store' data reaches disk.
    
    - Opened temporary file(s) with O_SYNC flag to avoid explicit fsync'ing.
    - Sync'd directory entry after creation and rename of 'store' files.
    - Thanks to Jeff Moyer's article on http://lwn.net/Articles/457667/
    
    Change-Id: I68a8672dc6a0b24d128de53f3b60c74dd08d8ab8
    BUG: 765434
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.com/3726
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fa0442e00149b4c8dc6ac21fb0a7742a360c240d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Jul 27 09:08:57 2012 +0530

    Warnings: Fix set, unused variable warnings
    
    Change-Id: If7ee85aa0d93f9018a76e7f60fcb7dcaf849dbdc
    BUG: 839950
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3742
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b4dbbe007da003962361c9a2579d1114f71619cc
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 26 17:16:00 2012 +0530

    acl: enable handling of FMODE_EXEC flag
    
    on linux systems, with open(), we can get below flag as per
    'linux/fs.h'.
    
    /* File is opened for execution with sys_execve / sys_uselib */
    
    Instead of adding '#include <linux/fs.h>, its better to copy this
    absolute number into other variable because then we have to deal
    with declaring fmode_t etc etc..
    
    With the fix, we can handle the file with '0711' permissions in
    the same way as backend linux filesystems.
    
    Change-Id: Ib1097fc0d2502af89c92d561eb4123cba15713f5
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3739
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 07c90f84d3cb11fd9539008f3a95c49d088e62bc
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jul 26 00:37:56 2012 -0700

    gfapi: unglobalize oldvol{file,len}
    
    Multiple initialization of volumes works fine now.
    
    Change-Id: Ibc16957b39325817bc6f9ab90ebac9cefdafabf8
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3734
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit f153c835807ac31006ba690b1deb47b20b51bc83
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jun 27 16:42:35 2012 +0530

    cluster/afr: Modified split-brain handling
    
    RCA
    The bug is observed because the decision to mark
    a file in split-brain is taken outside appropriate locks.
    Lookup gathers xattrs outside any lock. The xattrs being
    in split-brain in lookup should only be taken as a hint.
    Appropriate inodelks should be taken before confirming
    a split-brain. Self-heal confirms this at the moment.
    If data/metadata self-heal is turned off, inspecting of
    xattrs could not be performed so split-brain behavior
    does not work correctly if the self-heal options are turned off.
    
    Fix
    Self-heals are launched to inspect xattrs even when the
    data/metadata self-heal options are turned off. The decision
    to heal data/metadata after the xattrs are inspected is based
    on whether the options are turned on/off. So decision to set/reset
    split-brain flag is taken inside appropriate locks.
    
    Testcases:
    tests 33-36 in
    https://github.com/pranithk/gluster-tests/blob/master/afr/self-heal.sh
    
    Change-Id: Ia8aeab08208b50c06609ad35a9d72f3d553ee343
    BUG: 833727
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3626
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c2a7a22bfe18316eab441d49e515726e53f74582
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Jul 20 15:49:42 2012 +0530

    cluster/afr: Filter O_TRUNC in afr-fix-open
    
    RCA:
    When open was done while a brick is down, afr opens the file after
    the brick comes backup. If this happens after the self-heal on the file
    is completed by self-heald etc, the file will end up in truncated state.
    
    Fix:
    Filter O_TRUNC while afr-fix-open because afr_open turns O_TRUNC
    into truncate transaction, so there will be pending changelog for
    the subvolume on which open fails.
    
    Testing:
    Had to simulate the race by stopping fix-open until self-heald completes
    self-heal on the file after brick online.
    
    Change-Id: I32759cc37f4bb34f206d01606a279f17b246dba4
    BUG: 841840
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3705
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 22e4e55ecf65764812cfb76cd0b14a40b4161f25
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Jul 23 09:22:35 2012 -0400

    performance/write-behind: detect short writes and pend an EIO error
    
    Write-behind returns write requests immediately and queues the request
    in memory for merging, etc. If a write is incomplete, pend an EIO
    error for the next fop. This ensures that write failures are not
    silent and potentially ignored.
    
    BUG: 809975
    Change-Id: I0e0e6c8e710efab58ccfaf746501d00e459eb7ef
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3712
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fd2f9c0be1a5e170ca71079b2da2c9f3d64341ae
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Aug 19 12:08:15 2011 +0530

    performance/write-behind: preserve lk-owner while syncing writes.
    
      - This patch also makes syncing of non-overlapping but consecutive
        writes parallel. Till now only contiguous writes were synced
        parallely.
    
    Change-Id: Icf0d5ea373f30c79fcdc90ba44b7e7a1bc5f0111
    BUG: 765141
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/269
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 34d395fc16449ec3fe709d77609677992752b61a
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Jul 25 08:14:38 2012 -0400

    cluster: fix crash on link of named pipe in stripe/replicate vol
    
    A crash occurs when attempting to link a named pipe on a striped,
    replicated volume. The cause for this crash is attempting to deref
    a NULL inode pointer in stripe_link_cbk(). The RCA for this bug
    uncovered a couple of problems:
    
    - AFR ignores the inode pointer it receives on failure (returning
      NULL).
    - stripe assumes the inode pointer is valid on failure.
    
    Either one of these changes addresses the crash, but this patch
    includes both changes. AFR is modified to pass along the inode
    pointer it receives (which could still be NULL). stripe is
    modified to not assume the inode pointer is valid on fop failure.
    
    BUG: 842825
    Change-Id: I9cb2cc918552620929c3ecbd69bc66d4635eafdc
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3727
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 75ee490213b7f7673970ef80dee3bcc567848c26
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jul 25 09:56:58 2012 +0530

    cluster/afr: Perform data self-heal for non regular files
    
    RCA:
    Data self-heal for non regular files open the files
    and then proceeds using that fd. This approach
    does not work for symlinks because open on symlink opens
    the file resolved by it.
    
    Fix:
    If the file is not a regular file then perform self-heal using
    loc. It needs to get 'big' lock and then perform lookup to get
    changelog then erase data part of chagelog, then unlock.
    
    Test cases:
    Automated at
    https://github.com/pranithk/gluster-tests/blob/master/afr/special-file-self-heal-test.sh
    
    Change-Id: I924a922f5135872efe2cccf2e712ada082c5689f
    BUG: 811317
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3724
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 787d52d8e8bf415e48fa41ff9c7fef4693804903
Author: Brian Foster <bfoster@redhat.com>
Date:   Tue Jul 24 08:25:50 2012 -0400

    cluster/stripe: don't fail if no fctx on a non-regular file
    
    cluster/stripe broke directory rename. Only check for fctx on regular
    files.
    
    BUG: 842652
    Change-Id: I8a1e7ff30d57c994082cb10471f610023713ee53
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3720
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 12516e8af663032a0e6133f5f8f62f1078f9462d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jul 25 23:09:08 2012 +0530

    features/index: make pthread_attr_t local to init()
    
    RC & FIX:
    No need to carry around pthread_attr_t in index_priv.
    So made it local to init()
    
    Tests:
    stepped through init() in gdb, it succeeded.
    
    Change-Id: I0525ac0676f9a329fccb0fd064933594ec117261
    BUG: 843071
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3729
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7cce8c843e9002f521da0e1af892914c5bd68737
Author: shishir gowda <sgowda@redhat.com>
Date:   Wed Jul 25 13:08:14 2012 +0530

    cluster/distribute: Suppress user xattr mismatch log message
    
    Changing the log-level to DEBUG.
    Xattr mismatch can occur when parallel setxattr's race, or when
    one of the bricks was down. A subsequent setxattr will fix the
    condition when all the subvols are up. In this case, the 'user.swift'
    xattr used by ufo was out of sync, but did not cause any other error.
    
    Change-Id: I6fdff78869b8ff72c305bbe122033e6c1d9d3cff
    BUG: 838197
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.com/3722
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 8180d474a9f4aad495168102399b0465ad8efb06
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jul 25 15:08:46 2012 +0530

    features/index: Fix race in this->private initialization
    
    RCA:
    In index_worker function at the time of assigning priv from
    this->private, this->private may not be set in init() function
    of index xlator.
    
    Fix:
    Set this->private before creating the thread.
    
    Additional Changes:
    Added code to handle error path completely.
    
    Test cases:
    Attached the process to gdb and simulated failures.
    executed fini in gdb using call fini(this) after init
    was successful.
    
    Change-Id: I1874a30d009a35352173b827574cf83daf431453
    BUG: 843071
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3728
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 9d3dff4cf2b4f29f514b9eae00330dfe3e144fff
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Jul 25 16:07:00 2012 +0530

    gsyncd / geo-rep: Fix sendmark() invocation for Normal Mixin
    
    Change-Id: I0ae81ab01418becba83e401ec36c6db5323945e8
    BUG: 842330
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/3725
    Tested-by: Vijay Bellur <vbellur@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 7ab25973f11cf4eedcf3cf1a628f03937536391b
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 24 02:31:05 2012 +0530

    libglusterfs: fix creation of spurious root inodes
    
    Suppose lookup is sent on a newly created inode (gfid is root gfid),
    and in the call back inode_link is done, where if there is an inode
    already present in the inode table for that gfid, then we start using
    the present inode and the newly created inode supposedly gets destroyed
    when refcount comes down to zero through inode_unref calls.
    
    But inodes with root gfid are not unrefed. Now since in inode_link,
    the gfid has already been copied to the new inode and later the actual
    inode is found from the inode table, the new inode does not gets unrefed
    if its gfid is root gfid. Thus those spurious inodes with root gfid will
    be present throughout the lifetime of the filesystem.
    
    To fix this first search the inode table for an inode, with the gfid, present
    in the stat structure received as an argument. If the inode is not found,
    then copy the gfid to the newly created inode. Now whenever unref is called on
    on the new inode it gets unrefed and thus eventually gets destroyed
    
    Change-Id: I0f25f0a8dca3245abda1c322c216f063b52cf842
    BUG: 841188
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3716
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 18950598bef63c11237e7cdc959442e524a74061
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jul 24 01:13:25 2012 +0530

    Fixes for gsyncd / geo-rep and FUSE listxattr
    
    This patch fixes two problems with recent changes to
    Geo-Replication
    
    First:
    ------
    Recent changes to geo-replication relies on Rsync to tranfer
    extended attributes. Essentially Rsync would invoke a listxattr()
    and then getxattr() the set reutrned by listxattr() and finally
    transfer it to the remote slave. Xattrs like security.selinux would
    create problems as they are not allowed to be set explicitly (unless
    there's a rule that allows this). So, to make Rsync behave sanely we
    filter out all "*.selinux*" xattrs from listxattr() (which is getxattr()
    with ->name as NULL).
    
    Second:
    -------
    Python's "if {..} else {..}" shortcut ".. and .. or .." was misused here.
    This is a straightforward fix by interchanging last two variables (classes
    in this case). Also fix a typo in sendmark_regular() definition.
    
    Change-Id: I097b5f5d88a36c7eef5560a78d4332948a545942
    BUG: 842330
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/3714
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit d6f88e9edb564ed2300939e4f4fb6d83ac7fc5b6
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Jul 23 13:34:27 2012 -0400

    afr: pass back xdata in create
    
    A striped, replicated volume spits an error on file creation because
    stripe requires xdata to process stripe information and AFR isn't
    passing it back.
    
    This fix was suggested by Amar Tumballi.
    
    BUG: 842373
    Change-Id: Ia7063590ca5e873d4a4e155989cf067e8a07501f
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3713
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 35810fb2a7a124a78af3a4749e5b7c682c67e458
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jul 20 16:50:50 2012 +0530

    libgfxdr.so: change license
    
    Change-Id: I049441e465127195c192443ab0234548d2449e50
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3704
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Bharata B Rao <bharata.rao@gmail.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit b86c7c3870b1209d995498b9ee0c28f4dcce875f
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri Jul 20 17:39:43 2012 +0530

    gsyncd / geo-rep: Fix typo in 'purge' flow
    
    Change-Id: I6c329b895178545d16b0cb9f01ad116f5342f752
    BUG: 841855
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/3706
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit aa9f47d1729f6a7f08aef4c23d44febe498bb280
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Jul 18 04:07:20 2012 +0200

    geo-rep / gsyncd: convert ignore-deletes to a mixin too
    
    Change-Id: I164a1d1dd5f15569afd6806834119a6844949df0
    BUG: 841062
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3684
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit de22a7760db69b82de8959d238fe444af8b387d0
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Jul 18 03:59:00 2012 +0200

    geo-rep / gsyncd: add support for sending xtimes through rsync
    
    Note that in said mode metadata synchronization is best effort:
    rsync syncs metadata at last so if rsync is interrupted in between
    xattr sync and metadata sync stages, then file will be considered
    in sync
    
    Change-Id: I1c75eab33b0a1000abf3ad36b2d484a89eeda1bd
    BUG: 841062
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3683
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 9f5b8911b484230304fa52c0fcd92f696a4af74a
Author: Krishnan Parthasarathi <kparthas@redhat.com>
Date:   Thu Jul 12 17:35:37 2012 +0530

    glusterd: Refactored brickinfo APIs
    
    This patch modifies the existing brickinfo function signatures
    and/or names to do one thing right and call them by 'appropriate' names.
    
    - Decoupled brickinfo_get and is_brickpath_available
    - Removed dead comment about realpath(3) in canonicalize_path
    - Renamed glusterd_brickinfo_from_brick to glusterd_brickinfo_new_from_brick
      to make the name of the function reflect that an allocation is happening
    
    Change-Id: I29daba6d431ca799d43c927b9dfbaeda327e83e8
    BUG: 764890
    Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Reviewed-on: http://review.gluster.com/3668
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit c0b07bdf5d253cf5620726f149700960e962b8ec
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 18 16:28:00 2012 -0700

    fuse-bridge: utilize the option handle framework for double
    
    Also make other option initialization code use GF_OPTION_INIT
    framework for setting options and default values.
    
    Change-Id: I68a5c7b674f487fef9d23195654d3a5b2f7b8811
    BUG: 841417
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3698
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 20f8dc8ba11321a37437e4286f61be72de5256f1
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 18 16:12:01 2012 -0700

    libglusterfs/options: enable validator macros for type 'double'
    
    Values like 'entry-timeout' and 'attribute-timeout' in FUSE are of
    C type double. Enable support in the options framework for using
    this type.
    
    Change-Id: If1a619595a5925937e88540710860df27347acd0
    BUG: 841417
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3697
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 7018d7178e366146881d693e0159e13307e888ee
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 18 15:50:35 2012 -0700

    fuse-bridge: expose negative entry caching of FUSE
    
    Fuse kernel module supports caching negative entries, enabled
    by specifying a timeout while returning ENOENT to lookup. This
    patch enables the functionality to be enabled with the command
    line.
    
    Also fixed a typo bug in mount.glusterfs.in.
    
    Change-Id: I47eab2834cca9a05887266358afbf504bbb4c489
    BUG: 841417
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3696
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>

commit 00bd49b6c97b6b81fa55be3dc49459080d7c3b1b
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Oct 18 17:57:44 2011 +0530

    glusterd: atomic store update.
    
    All 'updates' to store are done in their respective tmp files and a rename to
    their original copies is done in one pass. Failure to write or rename
    successfully, promptly reduces the store's revision no., giving us an
    opportunity to 'correct' it via peer 'detach-attach' operations, if need
    be.
    
    Change-Id: I44a33c41cb4d3d1cfbb455bc1f2f074d4f17dade
    BUG: 765434
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/654
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 84a735558d2682446b2e45d97ff97e698ab2d256
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jul 17 22:54:21 2012 +0530

    FUSE: ignore setxattr for some keys from gsyncd aux mount
    
    Context
    -------
    gsyncd/geo-rep plans to rely on Rsync to sync extended attributes.
    When this is in place, all xattrs *visible* on the mount point would
    be candidate for syncing. This set could include gluster internal
    xattrs too (as xome xlators do not filter out in their cbks). Syncing
    these xattrs to the slave could result in unexpected functioning of
    the slave mount.
    
    Soln.
    -----
    For gsyncd auxillary mounts (identified by client_pid -1), we only
    allow xtime related xattrs to go through and silently ignore (w/o
    propagating error back to the client) the rest of them. This provides
    a future proof solution as we need not worry about what xattrs show
    up on the mounts. Also, 'user' namespace xattrs are always passed
    through even if it's from a gsyncd aux mount.
    
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Change-Id: I6fac5e03d2b25fa4cdece4b2897fb202617b3c23
    BUG: 841062
    Reviewed-on: http://review.gluster.com/3687
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 20fedc3232e876917f963b28a4f4b3bf469b2e6f
Author: shishir gowda <sgowda@redhat.com>
Date:   Fri Jul 6 09:54:33 2012 +0530

    cluster/distribute: cli support for setting directory-layout-spread
    
    gluster volume set <volname> subvols-per-directory
    
    Change-Id: I5f1420eeb2268897d9b4c70edb933ed1f07649d1
    BUG: 838006
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.com/3634
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 083556e498ede1d97011162b9731f2c4f544af59
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 18 13:53:59 2012 -0700

    glusterfs-api.pc: include pkgconfig file in -devel RPM
    
    Previous patch missed out including the .pc file in the -devel
    RPM while purging the -api.rpm.
    
    Change-Id: I895feefc62e88a962a829612aa829401fed081f8
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3693
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 67a85803b58ece292bbf50125b39b9e10db45320
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Jul 16 13:44:08 2012 -0400

    Example of using libglfs from Python.
    
    Change-Id: I081582c457428d55db8ec1ed6d90f1e439f51f0d
    BUG: 839950
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3675
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b324e317311974fbbb9ba13548364213a7a7a41a
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jul 12 15:40:43 2012 -0700

    glfsxmp: libgfapi based example
    
    This is an example application which uses libgfapi. It is
    a complete autotools based build system which demonstrates the
    required changes in configure.ac, Makefile.am etc to successfuly
    detect for and build an application against libgfapi.
    
    There are two approaches to building a libgfapi based application:
    
    1. In the presence of pkg-config in your build system.
    This is the recommended approach which is also used in this example.
    For this approach to work, you need to build glusterfs by passing
    --pkgconfigdir=/usr/lib64/pkgconfig (or the appropriate directory)
    in your distro. This already happens if you build RPMs with the
    glusterfs.spec provided in glusterfs.git. You will also need to
    install glusterfs-api RPM.
    
    2. In the absence of pkg-config in your build system.
    Make sure your LDFLAGS includes -L/path/to/lib where libgfapi.so is
    installed and -I/path/to/include/glusterfs where the 'api' directory
    
    Change-Id: Ic4eab2df002d7e8d20593a03e643859423048848
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3666
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit dbd7aa2d6b4128faa771d616c429b3a315740cec
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jul 12 15:51:41 2012 -0700

    glusterfs-api.pc: pkgconfig for API consumers
    
    Change-Id: I08c60ff9ec5d336077c39f903720f8850d4ddc72
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3665
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>

commit 2475e0193c4b4a37028bd8168113d6cd6949fe0e
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jul 12 15:37:38 2012 -0700

    gfapi: API/library for accessing gluster volumes
    
    Change-Id: Ie4cbcf91b58218bebf23cf951c313aceeb29f311
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3664
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Bharata B Rao <bharata.rao@gmail.com>

commit 162505c019934c13aadf63ed82d4532d5cf5ca82
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Jul 18 13:55:39 2012 -0400

    libglusterfs: remove debug log messages from gidcache
    
    The debug log messages for every cache lookup/add pollute the debug
    output.
    
    BUG: 800892
    Change-Id: I6b75fd5b7005b8c007106347de8827a0d6c2fd03
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3692
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c1fe8b7fd74eb6cc0d84fdb4811ab9d027539f62
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Jul 18 08:45:36 2012 -0400

    mount/fuse: check for fuse inval notify support when fopen-keep-cache enabled
    
    The fopen-keep-cache feature relies on the fuse notification system
    to operate correctly. As Csaba has pointed out, the inode invalidation
    functionality was added in FUSE version 7.12. Require that the user
    have 7.12 or later to enable fopen-keep-cache. If not supported, warn
    the user and disable the feature.
    
    BUG: 833564
    Change-Id: Ib9eecb56b689d8edff118b34e2dcc7dba6539b04
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3690
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f2e0aad9e3f189a6d2b1cb72e94b55e0b9c043ff
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jul 17 17:46:12 2012 +0200

    geo-rep / gsyncd: rsync option cleanups, fixes
    
    - add two tunables for rsync: "rsync-options" and "rsync-ssh-options"
    - always pass "--no-implied-dirs" to rsync
    
    Change-Id: I3d67a4cba8cabd681edac80e6b1fb8ea322008bd
    BUG: 841062
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3682
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit f2c110aa4aa9c1943d9200058fc449c300a01338
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jul 17 16:44:46 2012 +0530

    stripe: filter coalesce key in getxattr()/listxattr()
    
    as 'stripe-coalesce' is an internal key, no need to show it on top
    of the mount-point.
    
    Change-Id: Iab836e73d59c42774db8a2eee13fe3b0cd994bc9
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 801887
    Reviewed-on: http://review.gluster.com/3680
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>

commit a4e11fd67e3608c828e5bb8abf7a310b4f0a3017
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jul 16 15:50:30 2012 -0700

    glusterfs_ctx_t: un-globalize the filesystem context
    
    So far there has been a global glusterfs_ctx_t object which
    represents the running instance of the filesystem (client or server).
    It contains the various graphs, connection to the management daemon
    over which new graphs are obtained, calls stacks issued on this
    filesystem, and a bunch of such things.
    
    With the introduction of libgfapi, it is no more true that there will
    be only one filesystem context in a process. Applications can
    be written to use libgfapi and obtain serveral instances of different
    filesystems/volumes in the same process.
    
    This involves messy untangling of assumptions inside libglusterfs that
    there would only be one global glusterfs_ctx_t and offload that
    assumption to glusterfsd/ and cli/ (where it is true).
    
    Change-Id: Ifd7d1259428c26076140a5764a2dc7361694139c
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3678
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 06c1d6b2b87e542479e069132ee3cf9efa11384e
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jul 17 13:44:32 2012 +0530

    storage/posix: use the size returned by getxattr to allocate memory
    
    Change-Id: I71c234b12a1d16405e508b715932022fdce346f0
    BUG: 838195
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3681
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit aea7759f1240b1e97684273b9369472695173a66
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jul 17 10:50:43 2012 -0400

    rpc-transport/socket: Add SSL support.
    
    Based on OpenSSL.  Key/certificate management is still manual.  Enabling
    SSL also enables multi-threading, though multi-threading can be forced on
    or off using a separate option.
    
    Change-Id: Icd9f256bb2fd8c6266a7abefdff16936b4f8922d
    BUG: 764731
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/362
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ea0a0937a0524b8a449e470fbaea772a349d40fb
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jul 16 14:03:06 2012 -0700

    common-utils: implement generate_glusterfs_ctx_id()
    
    This patch creates a common and shared version of the often copy/
    pasted generate_uuid() function, which is used to create an ID string
    to uniquely identify an instance of a glusterfs process/glusterfs_ctx_t.
    
    Change-Id: Ie4e697ae28b6e954c5c261c69e37738f289d77e4
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3677
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 24717f14fa9e409f01f89c0905163b0db1e40729
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jul 16 03:51:10 2012 +0530

    storage/posix: use ssize_t variable to get the return value of getxattr
    
    Change-Id: Ida065e108a1d2a61b134fb847e8c4981b46fc3c6
    BUG: 838195
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3673
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3a96dcf9633bc097694a2f7a3acd0b08f830ef5e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Mon Jul 16 18:11:17 2012 +0200

    build: Create directories and files that get created during runtime
    
    This should not be needed for files marged as "ghost", but rpm-4.9 is
    broken in this respect :-(
    
    Building the packages works again:
    $ make dist
    $ rpmbuild -ta glusterfs-3git.tar.gz
    
    The now created files and directories are not packaged in the RPM, but
    are marked as belonging to the packages. Here a example for
    glusterfs-geo-replication:
    $ rpm -qlp glusterfs-geo-replication-3git-1.fc17.x86_64.rpm \
        | grep /var/lib
    /var/lib/glusterd/geo-replication
    /var/lib/glusterd/geo-replication/gsyncd.conf
    $ rpm2cpio < glusterfs-geo-replication-3git-1.fc17.x86_64.rpm \
        | cpio -t --quiet '/var/lib/*'
    $
    
    Change-Id: I32019cfbf40e25d9b7ce875fa92b98bae19dabee
    BUG: 839668
    See-also: https://bugzilla.redhat.com/show_bug.cgi?id=839656
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/3674
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 59ff893d11844eb52453ce4f7f098df05fcde174
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Jul 16 13:51:09 2012 -0400

    libglusterfs,mount/fuse: implement gidcache mechanism in fuse-bridge
    
    This change genericizes the cache mechanism implemented in commit
    8efd2845 into libglusterfs/src/gidcache.[ch] and adds fuse-bridge as
    a client. The cache mechanism is fundamentally equivalent, with some
    minor changes:
    
      - Change cache key from uid_t to uint64_t.
      - Modify the cache add logic to locate and use an entry with a
        matching ID, should it already exist. This addresses a bug in
        the existing mechanism where an expired entry supercedes a newly
        added entry in lookup, causing repeated adds and flushing of a
        cache bucket.
    
    The fuse group cache is disabled by default. It can be enabled via
    the 'gid-timeout' fuse-bridge translator option and accompanying
    mount option (i.e., '-o gid-timeout=1' for a 1s entry timeout).
    
    BUG: 800892
    Change-Id: I0b34a2263ca48dbb154790a4a44fc70b733e9114
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3676
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 911603eb0e1c85e79cf261f99f442c833ead8178
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jul 12 22:48:13 2012 -0700

    common-utils: implement iov_copy
    
    Change-Id: I7ab97279dafc1211b417e1c03332572887453c66
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3663
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Shishir Gowda <sgowda@redhat.com>
    Reviewed-by: Vijay Bellur <vbellur@redhat.com>

commit 01fe42db6e185ee7eb59677af9bc5bdf174bf548
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Jun 13 14:15:14 2012 +0530

    geo-rep / gsyncd: fixes to communication with child processes
    
    due to not using the proper Python keyword, errhandler thread
    was possible to run into empty select
    
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    BUG: 764678
    Change-Id: I3c39e718e72545c27d50fd73aa6daf54062331b0
    Reviewed-on: http://review.gluster.com/3560
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b69a5928718c8236a32d4a6eaec600a01d5fcd99
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 22 14:03:32 2012 +0530

    geo-rep / gsyncd: sanitize error log of external commands
    
    If a command invoked by gsyncd fails, gsyncd makes a log
    of what comes out on its stderr. So far the log indeterministically
    broke lines at random places. Now put some effort into reconstructing
    original lines and having a faithful log.
    
    BUG: 764678
    Change-Id: I16fcc75d3e0f624c10c71d9b37c937ca677087cc
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3561
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fb8efa4c6ab4bc1af49d05b0bc6b16eb188ea3b1
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 30 13:29:18 2011 +0530

    storage/posix: implement native linux AIO support
    
    Configurable via cli with "storage.linux-aio" settable option
    
    Change-Id: I9929e0d6fc1bbc2a0fe1fb67bfc8d15d8a483d3f
    BUG: 837495
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3627
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit ab44480749a289aaaf78dad4123ef16d1872ea1b
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jul 11 16:23:44 2012 -0700

    syncop: accomodate non-syncenv calls
    
    Use mutex/cond and support syncop_XXXXXX() calls in non-syncenv
    environments. syncenv environments continue to use swapcontext
    based soft context switches. In non-syncenv environments this
    blocks the caller thread on the mutex. The intended use case is
    in libgfapi where it is expected to block the caller thread while
    performing synchronous calls.
    
    Change-Id: Id6470c99bdc2fe4b7610372139f7fa99b2da400b
    BUG: 839950
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3662
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit aabe0c96cac4d219015a2fe085a7f89ebb9744d1
Author: Jim Meyering <meyering@redhat.com>
Date:   Fri Jul 13 19:20:19 2012 +0200

    cli-xml-output.c: avoid NULL-deref upon OOM
    
    Fix typo: s/buf/*buf/ in test after *buf = xmlBufferPtr(...
    Spotted by coverity.
    
    Change-Id: I92cd317832818647009a74f2a8407b5d3ecb958c
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3670
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a732e54aad9cff72097ff3020ef5c15ecd61b388
Author: Jim Meyering <meyering@redhat.com>
Date:   Fri Jul 13 18:38:52 2012 +0200

    gsyncd: don't dereference NULL upon failed realloc
    
    Fix typo: s/buf/*buf/ in test for failed *buf = realloc...
    Spotted by coverity.
    
    Change-Id: Ie1db59956e331c3691f4ed470a3fbaf2bd2e2055
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3669
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7820b2c1f88b207a8b1270b8c3cb3b797b7563d2
Author: Jim Meyering <meyering@redhat.com>
Date:   Fri Jul 13 10:29:48 2012 +0200

    remove useless if-before-free (and free-like) functions
    
    See comments in http://bugzilla.redhat.com/839925 for
    the code to perform this change.
    
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    BUG: 839925
    Change-Id: I10e4ecff16c3749fe17c2831c516737e08a3205a
    Reviewed-on: http://review.gluster.com/3661
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2dc0d32e5d8b205fa407073b209bb663d546dde8
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jul 11 16:45:33 2012 +0200

    no semantic change: reverse condition and if/else clauses...
    
    Reverse an if-condition and the corresponding then/else code
    blocks to hide a false-positive if-before-GF_FREE from the
    useless-if-before-free script.
    
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    BUG: 839925
    Change-Id: Ia68558218d63ae77b6c1c85e15231b66cce5bd49
    Reviewed-on: http://review.gluster.com/3651
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ce65a6b2f52f95922d29acba43e08315c50df136
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Jul 13 16:23:51 2012 +0530

    libglusterfs: syncop for flush ()
    
    Change-Id: I17f925345782313c75102c4767121ba8e283028e
    BUG: 764813
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3667
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 32ffb79f18cbaebcbe6bba51599ca234f44675cc
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Jun 13 12:08:38 2012 -0400

    fuse/md-cache: add support for the 'fopen-keep-cache' mount option
    
    fopen-keep-cache disables unconditional page-cache invalidations
    on file open in fuse (via FOPEN_KEEP_CACHE) and replaces that
    behavior with detection of remote changes and explicit
    invalidations from mount/fuse. This option improves local caching
    through the page cache and native client.
    
    This change defines a new 'invalidate' translator callback to
    identify when an inode's cache mapping has been determined to be
    invalid. md-cache implements the policy to detect and invoke
    inode invalidations. fuse-bridge and io-cache implement
    invalidate handlers to invalidate the respective caches (page
    cache in the case of fuse).
    
    BUG: 833564
    Change-Id: I99818da5777eaf06276c1c0b194669f5bab92d48
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3584
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ca4900497142127c31d0dba7a53a921200aaf790
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 5 13:34:28 2012 +0530

    protocol/server: return 'xdata' even in case of error
    
    helps to better utilize dict for more clarity on
    errors, if required.
    
    Change-Id: I3ff90e16be946e5f60974d4bde68a729d596c9de
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 826982
    Reviewed-on: http://review.gluster.com/3633
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 89bd58e170118e4d534e6113c1c368c1a39cc919
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 12 22:59:04 2012 +0530

    core: remove the unused files - round 2
    
    BUG: 764890
    Change-Id: I3eb626eeaa2a09f0e248444f560c2a0eaf46c642
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3660
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ac6be8b4204330d117d24e1473becda3f3989cb1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Jun 30 23:55:54 2012 +0530

    rpc: variable name changes
    
    's/3_1/3_3/g' in case of glusterfs protocol
    's/3_1_/_/g' in case of CLI and mgmt protocol
    
    Change-Id: I6e6510d02c05f68f290c52ed284c04576326e12c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 764890
    Reviewed-on: http://review.gluster.com/3632
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4ba54d10f081da2d8a241f116d7d5bf4081259cc
Author: Niels de Vos <ndevos@redhat.com>
Date:   Thu Jul 12 12:39:33 2012 +0200

    extras: install clear_xattrs.sh
    
    The script was not installed by default, this breaks building the RPM
    packages since Change-Id Iba695a6d19389fbc1776da5e939d67318916aadf.
    
    Change-Id: I4fb982cb5217dc7b3ec3c7a664dd3997a2e05170
    BUG: 812214
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/3659
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 08745892b4edd34296bfa5f2f4967329515346fb
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Tue Jul 10 09:33:02 2012 -0400

    calls to dict_allocate_and_serialize() are not 64-bit clean
    
    All calls to dict_allocate_and_serialize() pass the address of a 32-bit
    type, but must cast it to the 64-bit pointer type (size_t *).
    
    This happens to work on LE machines, but even if it's apparently benign,
    it's still a bug. On BE machines it is not benign.
    
    GF_PROTOCOL_DICT_SERIALIZE() hacks around it by creating a size_t temp
    var, but that's, well, a hack, IMO when you consider that all the callers
    are actually passing &<u_int>; the param should just be a u_int * and
    eliminate the buggy casts and the temp var in the macro.
    
    Nobody apparently uses the Fedora/EPEL PPC RPMs, but they might. People
    are trying to build gluster.org bits on SPARC and tripping over this.
    
    Change-Id: I92ea139f9e3e91ddbbb32a51b96fa582a9515626
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    BUG: 838928
    Reviewed-on: http://review.gluster.com/3642
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c76b49047aa396c0296a6ba2120e14abc0d27491
Author: Jim Meyering <meyering@redhat.com>
Date:   Tue Jul 3 17:06:46 2012 +0200

    geo-rep: don't let unexpected status provoke undefined behavior
    
    glusterd_gsync_read_frm_status reads what is expected to be a NUL-
    terminated status string from the specified file, but makes two
    mistakes when trying to do the favor of trimming trailing spaces.
    Do not let a leading NUL byte of status cause us to read buf[-1]
    and possibly to clear that and any preceding "trailing" spaces.
    Do not let a blen-byte input (with no NUL byte) cause our use of
    strlen to access beyond the end of non-NUL-terminated buffer.
    
    I looked at this code because coverity reported that it was
    assuming a read-provided buffer to be NUL-terminated.
    
    Change-Id: I140be0948e31196e5be08766d4e6400bf6f4dfa1
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3647
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee480749ee61af01b18ddb37e80a73153c7de92e
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue Jul 10 16:47:07 2012 +0200

    extras: add clear_xattrs.sh to the glusterfs-server sub-package
    
    Change-Id: Iba695a6d19389fbc1776da5e939d67318916aadf
    BUG: 812214
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/3644
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1ef9a920c1735865bce77ba8c93756e85c47f272
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon Jul 9 01:58:30 2012 +0530

    storage/posix: handle getxattr failures gracefully
    
    Use proper variable types for getting return value of getxattr calls,
    which otherwise can lead to segfaulting of processes or page allocation
    failures in the kernel.
    
    Change-Id: I62ab5d6c378447090c19846f03298c3afc8863ba
    BUG: 838195
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3640
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b1a5fa55695f497952264e35a9c8eb2bbf1ec4c3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Jul 5 08:45:52 2012 +0530

    core: check for pre-allocated blocks in backend fs, fix it.
    
    There is a possibility that the backend FS (like XFS) can
    allocate blocks beyond EOF for better performance reasons, which
    results in 'st_blocks' with higher values than what is consumed by
    the file descriptor. This would break few logic inside GlusterFS,
    like quota behavior etc, thus we need the exact number of blocks
    which are consumed by the file to the higher layers inside GlusterFS.
    
    Currently, this logic won't work for sparse files (ie, file with holes)
    
    Change-Id: Ied216733a8862e84f7da8386ae0a144f3f5cd5f2
    BUG: 817343
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3631
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f671ce6c6fa619b5cea2559495b4b21920f5de73
Author: Jim Meyering <meyering@redhat.com>
Date:   Tue Jul 3 16:32:25 2012 +0200

    glusterfsd: don't ignore tmpfile write failure (2x)
    
    In both glusterfs_volfile_reconfigure and mgmt_getspec_cbk,
    we fwrite to a temporary file, fflush the stream, and then
    rewind and read from it.  However, if either the fwrite or
    fflush were to fail, we would have ignored a write failure
    and would then read and process corrupt or incomplete input.
    In each case, add a test of ferror so that we don't ignore
    the write failure.
    
    Found by inspection.
    
    Change-Id: I8e84deb7d020a907870c9da2dde5c7371ce6ddb7
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3648
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7f2788675ba99193b7f18b3b9efbbbe3b5d0b2e5
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 14:13:45 2012 +0200

    cli: cli_cmd_get_confirmation: don't reference answer[-1] for NUL input
    
    Change-Id: I83baa54fc5392e92a6a451c549d356ff1ffc92cb
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3606
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a8ce48126dc57726f820e8815cff8b24911ca076
Author: Jim Meyering <meyering@redhat.com>
Date:   Mon Jul 9 22:50:09 2012 +0200

    cli: print_brick_status: don't smash stack
    
    For bricklen > 110 (i.e., 2 * fieldlen), the if-clause
    would be executed 2 or more times, making strncpy write
    past the end of "buf", clobbering the stack.  Rewrite,
    removing unnecessary use of strncpy, strlen and decl/use
    of the temporary buffer, and instead, specifying precision
    via a printf-style format directive.
    
    Coverity identified the static buffer overrun.
    
    Change-Id: I176386e752c397dea22265de9f3c6eb631334f4f
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3646
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7c88fcd63df71cc1b81caea791235a828c9b419e
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 13:56:36 2012 +0200

    read_conf: don't let a corrupt config file cause invalid line[-1] reference
    
    Change-Id: Ifbc698768d9418a54c1501efa335edd4048cfd41
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3603
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4a505c0eb8736d75a677530a7789fc9bc03d4c28
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 11:33:10 2012 +0200

    gsyncd: don't let a bogus config file make us read/write buf[-1]
    
    Change-Id: Ic55c28c572c1878f8a223ae2fd25d301a7ef0c12
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3596
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 57e72677ac1123b583be8daec2287efac87362df
Author: Jim Meyering <meyering@redhat.com>
Date:   Tue Jun 19 11:41:19 2012 +0200

    glusterd: avoid buffer overrun for over-long volname
    
    [in glusterd_store_is_valid_brickpath]
    When strlen(volname) is no smaller than sizeof(volinfo->volname),
    volinfo->volname would end up not being NUL-terminated.
    Then, a use of that buffer that expects it to be NUL-terminated
    (i.e., glusterd_store_brickinfopath_set's GLUSTERD_GET_BRICK_DIR)
    will access beyond the end of the buffer.
    Instead, diagnose the too-long volume name and fail.
    
    Change-Id: I655d8638547bf342d33280c14ff1edacc3cdeb5a
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3591
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fa946a8448dd3916c3fb31c9ba6cf195f98fc58c
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 10:01:08 2012 +0200

    nfs-common: don't let 0-length path cause buf[-1] access
    
    Change-Id: I5f0e93448a954aff1ff08a0980fb9bfd60e63988
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3594
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3c28358a6ff00cb05bfccd8be15f4d204aaccefd
Author: Jim Meyering <meyering@redhat.com>
Date:   Tue Jun 19 15:21:37 2012 +0200

    xlator options: remove overwritten data-self-heal initializer
    
    In the struct volume_options, the "data-self-heal"
    .default_value = "" setting appeared before a setting of
    .default_value = "on".  Remove the former.
    
    Change-Id: Ieddcc18f61581f9448d806cd8bf8eefaaf0118b9
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3589
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 22aa93129319a667b004111a4385520a4ba30060
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jul 11 21:59:20 2012 +0530

    rpc: add extra arguments to _callback's actor function
    
    Need to differentiate the callback functions based on which
    rpc-clnt the callback is received. without it, all callback
    actor handling will be like global.
    
    BUG: 839345
    Change-Id: Ide024f5585eab3c5fe6c3b33250772fb6e8ad655
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3656
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ea08bf886732d9680f2d6de19f3d68908a55143b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Jul 11 22:25:30 2012 +0530

    core: remove unused code
    
    BUG: 764890
    Change-Id: Ia8bcaa7a4daeb706bcb0bba24b2e634e9ca20d49
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3657
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cb60a046bbb24cc864aa007707c75bdadf2157e3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Jun 30 08:28:10 2012 +0530

    xlators/protocol: better filename
    
    3_1 name was used for very first version of GlusterFS which
    used RPC for its protocol, even though we changed protocol
    after 3.1.x, we kept the name of few files as is. Changed
    the file names to something better.
    
    Change-Id: I297f1979e7c7e909e60674eec2e632506bc776f5
    BUG: 764890
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3628
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5934ce33f1aa09be452c04330f59a8ae1a1b04f9
Author: Amit Chauhan <amitchauhan.gfs@gmail.com>
Date:   Wed Jul 4 18:28:48 2012 +0530

    Gluster Cli:Pressing Control-d hangs gluster cli
    
    Gluster Cli hangs on pressing CTRL+d. This happens due to
    break statement was used when it reads end of stdin.
    exit statement is used instead of break.
    
    Change-Id: I2b0e00c0c5fbe8cb9182a96c06ed052d79845087
    BUG: 807563
    Signed-off-by: Amit Chauhan <amitchauhan.gfs@gmail.com>
    Reviewed-on: http://review.gluster.com/3630
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e6e0e5bede9315db377afdec9c7bd92cfaa9c4bb
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jun 7 23:23:55 2012 -0700

    md-cache: cache SELinux and Posix ACL xattrs only if enabled
    
    Fetch and cache SELinux and Posix ACL extended attributes only if
    they are enabled in the command line respectively. Fetching the
    extra extended attributes is pointless and negatively impacts
    performance
    
    Change-Id: I1bd1dbb1abb4a6929fad5f78bbfeaab8542ab4e2
    BUG: 765785
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3538
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 96e24e01fa01144e784597c9dc3648c78da78a61
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jun 12 19:17:41 2012 +0530

    glusterd: copy /etc/glusterd to /var/lib and remove /etc/glusterd instead of
              moving
    
    * Change default directory from /etc/glusterd to /var/lib/glusterd
    
    Change-Id: Iefa82e4fdb94ce5a84dfb40855c80e16e9ffcc40
    BUG: 830218
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3548
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 34a06d3c13aba1a22680e070b08284f2d7c69890
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jun 25 19:37:09 2012 -0700

    nfs: make NFS filehandles deterministic
    
    The NFS3 file handles now includes just the bare minimum of
    (ident, exportid, gfid) and removes legacy 'variable' members
    which are unnecessary since the introduction of GFID backend
    
    Change-Id: Iff6e4435d170074b18d208742b48e79b130e2a4d
    BUG: 835336
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3616
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 5a3d849b8563067d35c1422e43e605bd9533f3c2
Author: Anand Avati <avati@redhat.com>
Date:   Tue Jun 26 21:06:39 2012 -0700

    cluster/afr: post-op-delay support
    
    post-op-delay introduces an artificial delay between the OP and
    POST-OP-CHANGELOG phases of a write transaction to increase the
    probability of changelog-piggyback and eager-locking to work
    more efficiently.
    
    Also enable eager-locking by default.
    
    Change-Id: I865ca4b68512c44818719c7e388952f15d53e6c2
    BUG: 836033
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3621
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit d90596a15c03434f14258d754e37b84e3ec57310
Author: Anand Avati <avati@redhat.com>
Date:   Wed Jun 27 15:04:55 2012 -0700

    cluster/afr: cleanup lk_owner and PID mess
    
    Historically PID (frame->root->pid) was used by the locks translator
    to identify a locker (and make decisions about which locks contend
    or cooperate/merge). Since the introduction of lock_owner parameter
    the usage of PID (for locks) was deprecated and is now unused. This
    patch nukes the usage of PID in AFR
    
    The usage of lk_owner has also ended up being a mess, because of the
    differentiation required between ->lk() and ->inodelk(), (->lk() needs
    to be identified by the process (roughly) and ->inodelk() needs to be
    identified by the transaction) and also because of optimizations like
    eager locking (locks are no more identified by the transaction as they
    now get inherited by the next transaction).
    
    The scheme (and technique) now is:
    
    - All FOPs (the third phase of the transaction) happen with the lk_owner
      which is set by the topmost layer (FUSE, NFS etc.)
    
    - All entrylks are issued with lk_owner set to the frame->root address.
    
    - Inodelks which will not be subject to eager locking are issued with
      lk_owner set to frame->root.
    
    - Inodelks which are subject to eager locking are issued with lk_owner
      set to the address of fd_t (which are the only type of frames which
      get subject to the eager locking optimization)
    
    - At the start of the transaction, the transaction frame's lk_owner is
      set to the either frame->root or fd_t (and never unmodified) depending
      on the type of transaction.
    
    - Just before the third phase (FOP phase) the set lk_owner is "saved"
      away and overwritten by the lk_owner submitted by the top layer (FUSE
      or NFS)
    
    - Right after the third phase, the saved lk_owner is "restored" to resume
      the transaction into the POST-OP and eventually UNLOCK using the same
      lk_owner which was used during the LOCK phase.
    
    Change-Id: I6ab8e4d6b65ae4185fa85ad3fded8e9188b2f929
    BUG: 836033
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3620
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit 9781fea0dbde3faeeeb52451965de5d891e79bf2
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Sun Jun 24 16:17:21 2012 +0200

    cluster/afr: add a new option to select read-subvol by index
    
    read subvolume is a nice option to set prefred read child if you have a
    replication over 2 datacenter.  if you have 2 datacenter and have a
    distributed replication where one set of servers are in datacenter one
    and the other (the replicated) are in the other datacenter
    read-subvolume it not very handy since it goes over name and the
    subvolume name is different for each replication pair.  i added a new
    option called read-subvolume-index which take the number of the
    subvolume to choose.  0 fo first , 1 for second and so on subvolume in
    every replication.  this option can now be used in the --xlator-option
    mount option to choose the prefered read child for all replication at
    once.  For Example on all clients in datacenter one you can use
    --xlator-option=volumename-replication-*.read-subvolume-index=0 to
    prefer read from the servers in datacenter one.  when you expand or
    shrink the volume no changes are needed to the client config since the
    wildcard will set this option automatic on reconfigure.
    
    Change-Id: I3b47432f77037c380ff4a6296636c6f8fc953db9
    BUG: 837420
    Original-author: domwo <glusterfs@wollina.de>
    Signed-off-by: domwo <glusterfs@wollina.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3615
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fe4777660a0a92da6da582103690fa0c2e5c7496
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Sun Jun 24 15:52:43 2012 +0200

    cluster/afr: fix for read-subvolume option does not work
    
    changed order of prevered read child in afr_select_read_child_from_policy
    when a read child is set over config option read-subvolume it shoudl be first to return
    
    Change-Id: I1c5a8171379bb2bad76f6653e9d68a9349d55142
    BUG: 833750
    Original-author: domwo <glusterfs@wollina.de>
    Signed-off-by: domwo <glusterfs@wollina.de>
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3614
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7c6a948988e1183387ce652711bdfc12046e944f
Author: Niels de Vos <ndevos@redhat.com>
Date:   Fri Jun 8 11:59:31 2012 +0200

    Mark /var/lib/glusterd as owned by glusterfs, subdirs belong to -server
    
    Change-Id: Ib1df8da7e8abdcd3edece45bd39fe238f28838f1
    BUG: 829734
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/3539
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 434cf66b5ad85c659091139919bb4805b0a6ff08
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 14:06:24 2012 +0200

    xdr_vector_round_up: don't let vcount <= 0 cause invalid array reference
    
    Change-Id: I6a69f20fddb7271fe47f80acb97d2198e9998ccc
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3605
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b8bc3adfd943071bdab2ed186736f99d39397576
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 14:03:14 2012 +0200

    get_mnt_opts: don't let empty option string cause (*mpt_optsp)[-1] reference
    
    This looks like a "can't happen" case (depending on what add_option does),
    so you may prefer to add an assertion instead.
    
    Change-Id: Ibfdd34fca045e5213de836cca252bd96408b2136
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3604
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 004d01ddfa6b9388835bb05a3b13a766719e2158
Author: Venkatesh Somyajulu <vsomyaju@redhat.com>
Date:   Thu Jun 21 18:31:23 2012 +0530

    mgmt/glusterd: Added spaces in the logs
    
    Change-Id: Ic44e339219a845946e18c8c926fe993e09f86624
    BUG: 820555
    Signed-off-by: Venkatesh Somyajulu <vsomyaju@redhat.com>
    Reviewed-on: http://review.gluster.com/3609
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 295c0280d117cfca85f354d8098ea72c30ef2ced
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 13:45:46 2012 +0200

    valid_ipv4_address: don't access addr[-1] for 0-length input string
    
    valid_ipv6_address: Likewise.
    
    Change-Id: I6225873a5e323f81de5f25335aceeee571629e28
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3602
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c62eeda7718e4c15e19ade68455826ab32438f98
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 13:34:11 2012 +0200

    libgf_client_chdir: don't access path[-1] upon chdir("")
    
    Admittedly, this code may not be reachable via
    glusterfs_chdir, assuming libgf_client_path_lookup
    with such a loc.path would fail.
    
    Change-Id: I0b72ade0918da30d49bff756dcf04d1512d0177f
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3601
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9945a0030a78c33b46dc3fafd313cb87a91289fa
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 13:29:38 2012 +0200

    libgf_count_path_components: don't access pathdup[-1] for empty input
    
    Change-Id: I432f8c8fac907f625d79b2c5bb626a1f7013a73e
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3600
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 237d32b784cfb0ff93f7f1081d89809af962ed56
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 13:17:49 2012 +0200

    libgf_init_vmpentry: assert strlen(vmp) > 0 to guard against using vmp[-1]
    
    Change-Id: I091e6066fd470e9e0b67a00464b5713b86d3783c
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3599
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee3ed7c0bfcd340cd747a20812062925d5550d2a
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 11:58:07 2012 +0200

    libgf_rrindex: don't return &str[-1] for an empty string input
    
    libgf_trim_to_prev_dir: handle empty path (i.e., don't access path[-1])
    libgf_alloc_fd_ctx: assert that vpath is not empty
    
    Change-Id: I8f9d233680f78107187132889916cdcf4262af72
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3598
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b535e4936d31e88595abc79a28ba87031aeccc4c
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 11:37:44 2012 +0200

    pidinfo: don't let a corrupt /proc/PID/status cause buf[-1] access
    
    Change-Id: I5d10eb92af753513eb5e5e3d7d2ad3ace57917d7
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3597
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2310671cd15cd1639436a824922fa0a924cd6367
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 10:07:12 2012 +0200

    geo-rep: handle input without trailing newline; don't reference buf[-1]
    
    Do not truncate final byte of a line that does not end in a newline.
    Do not clobber stack (resbuf[-1]) for input that starts with a NUL byte.
    Likewise in glusterd_urltransform.
    
    Change-Id: Ifdcad02d908c8dcbc1a0eee78d318dd4e7860322
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3595
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 13e7f9dc6971be887fc73a460517fa84e11b927c
Author: Jim Meyering <meyering@redhat.com>
Date:   Wed Jun 20 10:00:02 2012 +0200

    xlators/nfs: don't test/set dirpath[-1] for a zero-length name
    
    Change-Id: Ic6ccfc964c9739f067ccf14a95fd0e09baf0dd51
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3593
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 528d94380bb9e45ebc4f09d532085476f87f32cc
Author: Jim Meyering <meyering@redhat.com>
Date:   Tue Jun 19 12:30:21 2012 +0200

    glusterd-rpc-ops: avoid buffer overrun for over-long key
    
    strncpy explicitly does not NUL-terminate when source string
    has length >= the length specified via strncpy's 3rd argument.
    Assuming strncpy is justified (i.e., that it may truncate),
    be sure to NUL-terminate its destination buffer.
    
    Change-Id: Ia67bf136cdfae6d9850f673923c01baa3cdef9d8
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3592
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b9fd37b8a4973929bf3d5e756a1aa4fc803e8c27
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Jun 11 16:21:04 2012 +0530

    features/worm: Allow worm option to be set throught volume set
    
    'volume set <volname> worm on' adds the worm xlator on the bricks.
    
    Read-only and worm cannot exist together, and a check is added.
    
    Regular volumes can still be mounted with worm mount option.
    
    If a volume is started before conversion to worm, the bricks need
    to be restarted for the option to take force.
    
    Updated feature.read-only option to features.read-only to keep it
    consistent with other features based options.
    
    Change-Id: I1a8fab363aaf66e6da615dcffa328332ae39fa04
    BUG: 811612
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3545
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e6c461abe5fd63baa25007e1880d0f04f3ae01bb
Author: Jim Meyering <meyering@redhat.com>
Date:   Thu May 31 11:29:29 2012 +0200

    glusterd: avoid buffer overrun due to lack of NUL terminator
    
    Assume that this use of strncpy is not spurious (i.e., that it does
    sometimes truncate), and ensure that the result is NUL-terminated.
    Otherwise, callers that treat ->filepath as a NUL-terminated
    string could operate on a bogus file name and/or segfault.
    
    Change-Id: I276bf8a4da330284cc0300e8da7113a48b9b9b37
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3590
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 64a2627cc1cfb8cc547c160c2362d05401b8ed87
Author: Jim Meyering <meyering@redhat.com>
Date:   Mon Jun 4 16:41:17 2012 +0200

    bdb: fix erroneous strncpy in file name construction
    
    Using strncpy like that fails to copy the trailing NUL byte of
    dirent->d_name, which is required, since the result buffer,
    entry_path is stat'ed in the code just below.  Besides, there is
    no need for strncpy, since we know the source buffer will fit
    in the possibly-just-realloc'd destination buffer: use memcpy
    and +1 to include the trailing NUL.
    
    Change-Id: I4d4cfb5b7df3c018516919f2d67c21c07de126cb
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3588
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d1610978436dda903e50552eed0cb8116dae88b9
Author: Jim Meyering <meyering@redhat.com>
Date:   Mon Jun 4 15:04:01 2012 +0200

    posix: avoid unnecessary strncpy
    
    When strlen(SRC) < LEN, using strncpy is misleading.
    Use strcpy instead.
    
    Change-Id: I76832353dc415de99f0583d085d5c2444d5fe8b0
    BUG: 789278
    Signed-off-by: Jim Meyering <meyering@redhat.com>
    Reviewed-on: http://review.gluster.com/3587
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b583363dcc0cf87b4ca27b99bca532da764e3a07
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jun 27 11:04:48 2012 +0530

    glusterd: Fix peer probe when username/password is missing
    
    Prevent failure of building volumes dictionary during peer probe, when
    username/password for a volume is missing. This situation can be caused by
    migration of gluster from pre-3.3 to 3.3 and above.
    
    Change-Id: Ib924ecd3d941ddaa5c7773e4d45b076c488b6421
    BUG: 834229
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3619
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4df765df74b4406c7cce90e66c4256e3850a8c5f
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Sat Jun 23 10:28:54 2012 +0530

    glusterd, cli: handle uuid conflicts in probe gracefully
    
    A commonly faced problem among glusterfs users is: after a fresh
    installation of glusterfs in a virtual machine, the VM image is
    cloned to make multiple instances of the server. This breaks
    glusterd because right after glusterfs installation on the first
    boot glusterd would have created the node UUID and this gets
    inherited into the clone. The result is wierd behavior at the time
    of peer probe where glusterd does not (yet) deal with UUID
    collisions in a user friendly way.
    
    With this patch the peer which got the probe request will compare
    the uuid of the machine which send the probe request with its own
    uuid and send the proper error to cli if the uuids are same.
    
    Change-Id: I091741ec863431fb6480a09a3f4c68a0906a3339
    BUG: 811493
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3612
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4df8241e740255744deea983f5e0c63ade202409
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Sat Jun 30 17:04:26 2012 +0530

    rpc: Fixed ping timer algo.
    
    The purpose of the ping timer is to assert the absence of any evidence
    the server is possibly alive.
    
    The current implementation updates the 'last_sent' timer in the following
    points in time,
    - rpc_clnt_submit: when rpc messages are being queued at the transport
      layer. (wrong!, since we have no way to determine if server actually
      received the message)
    - rpc_clnt_notify: when client receives pollout event on sending a message
      on the 'wire'. (correct, since it indicates ACK from server)
    
    The fix removes the 'incorrect' update of 'last_sent'.
    
    Change-Id: I56af7b15c3672673696977a7c50ee66eafa4ec55
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3625
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5a5148f07a808d1b94a116eb41a9452bd58ed6bb
Author: shishir gowda <sgowda@redhat.com>
Date:   Fri Jun 22 13:28:31 2012 +0530

    cluster/dht: Remove dht dependency on glusterfsd-mgmt
    
    glusterfs_ctx->notify can be used by any xlator to talk to
    glusterfsd-mgmt.
    Note- This is for any rpc communication initiated by the xlator,
          and not from glusterd.
    
    Change-Id: Ic0e4af106fe1e98d797ca621facda8839b87598a
    BUG: 835757
    Signed-off-by: shishir gowda <sgowda@redhat.com>
    Reviewed-on: http://review.gluster.com/3618
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5672e77d3102a990a2aa11e7e56ebfe6a0eee369
Author: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jun 13 09:13:04 2012 -0400

    localtime and ctime are not MT-SAFE
    
    There are a number of nit-level issues throughout the source with
    the use of localtime and ctime. While they apparently aren't causing
    too many problems, apart from the one in bz 828058, they ought to be
    fixed.  Among the "real" problems that are fixed in this patch:
     1) general localtime and ctime not MT-SAFE. There's a non-zero chance
        that another thread calling localtime (or ctime) will over-write
        the static data about to be used in another thread
     2) localtime(& <64-bit-type>) or ctime(& <64-bit-type>) generally
        not a problem on 64-bit or little-endian 32-bit. But even though
        we probably have zero users on big-ending 32-bit platforms, it's
        still incorrect.
     3) multiple nested calls passed as params. Last one wins, i.e. over-
        writes result of prior calls.
     4) Inconsistent error handling. Most of these calls are for logging,
        tracing, or dumping. I submit that if an error somehow occurs in
        the call to localtime or ctime, the log/trace/dump still should
        still occur.
     5) Appliances should all have their clocks set to UTC, and all log
        entries, traces, and dumps should use GMT.
     6) fix strtok(), change to strtok_r()
    
    Other things this patch fixes/changes (that aren't bugs per se):
     1) Change "%Y-%m-%d %H:%M:%S" and similar to their equivalent shorthand,
        e.g. "%F %T"
     2) change sizeof(timestr) to sizeof timestr. sizeof is an operator,
        not a function. You don't use i +(32), why use sizeof(<var>).
        (And yes, you do use parens with sizeof(<type>).)
     3) change 'char timestr[256]' to 'char timestr[32]' where appropriate.
        Per-thread stack is limited. Time strings are never longer than ~20
        characters, so why waste 220+ bytes on the stack?
    
    Things this patch doesn't fix:
     1) hodgepodge of %Y-%m-%d %H:%M:%S versus %Y/%m/%d-%H%M%S and other
        variations. It's not clear to me whether this ever matters, not to
        mention 3rd party log filtering tools may already rely on a
        particular format. Still it would be nice to have a single manifest
        constant and have every call to localtime/strftime consistently use
        the same format.
    
    Change-Id: I827cad7bf53e57b69c0173f67abe72884249c1a9
    BUG: 832173
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3568
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d87bd36040128c6553e8ee06a363eeb60d16e72c
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jun 21 04:58:04 2012 +0530

    cli: improvements in the output of rebalance status
    
    Change-Id: I14149dc0eef9236fb089cc1404166efee46ddd1b
    BUG: 834263
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3608
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c7974318f09ed720471a02f3ec72569d4d7bbdfa
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Jun 14 11:53:48 2012 +0530

    libglusterfs: Fix sizet validation for cache-size
    
    Validation of 'cache-size' option will not fail when given value is greater than
    max. Values lesser than min will cause validation to fail.
    
    Change-Id: I9c744b5ace10604d5a814e6218ca0d83c796db80
    BUG: 831568
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3570
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 79aa6092a277975cb618d89da645080e51958543
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Jun 15 15:13:31 2012 +0530

    protocol/client: Re-open should not have O_CREAT|O_TRUNC|O_EXCL
    
    RCA
    The bug is observed in 3.2.x because posix xlator changes
    the uid/gid of file as per frame->root-uid/gid if O_CREAT flag
    is set in open fop. Posix does not do this in 3.3.x so that
    bug does not appear anymore but this issue exposed the actual
    bug in client xlator re-open. Re-open of a file on re-connection
    should not perform re-open with the same flags at the time of
    open/create/opendir. Imagine a case where a file is opened with
    O_TRUNC|O_RDWR and some data is written to it, now if the brick
    goes down and comes back the file will be truncated.
    When I tested this case, the file is not truncated because locks
    xlator resets O_TRUNC unconditionally.
    Client xlator re-open bug and locks xlator bug cancel each other.
    
    Fix
    Reset O_CREAT|O_TRUNC|O_EXCL flags in re-open.
    Locks xlator should not reset O_TRUNC.
    
    Additional changes
    Removed wbflags as it is not assigned at all.
    
    Testcases
    Automated go program is at:
    ://bugzilla.redhat.com/show_bug.cgi?id=807976#c2
    
    Change-Id: I0080344fdda2e62e7c976c35a5bf5f1fa8838891
    BUG: 807976
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3582
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d51d9b4154d6a70efcde30514620cc0442252436
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Tue Jun 12 23:58:14 2012 +0530

    features/marker: use buf->ia_gfid in all the lookup callbacks
    
    * In general use buf->ia_gfid for gfid instead of inode's gfid
      in the callbacks of the fops where new inode is created (such
      as create, mkdir, mknod, symlink). In the callback path inode
      would not be having the gfid within it, if it is not yet linked
      to the inode table which happens in protocol/server.
    
    Change-Id: I75b348ad152a1bcd634a4c2db34aca97956ccb21
    BUG: 822067
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3567
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fe8572380620d2ec7e95f9b6304ed735f013aa1c
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri May 25 09:49:58 2012 +0530

    cluster/afr: Don't reset split-brain when data-self-heal is off
    
    BUG: 804606
    Change-Id: I8cefcb6efa687fac4ad412403c085b3767218f72
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3586
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3709b2860688f4f9645a52006e3ede35b7d02830
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Thu Jun 14 11:55:45 2012 +0530

    debug/io-stats: if some dict operation fails then goto out instead of proceeding
    
    Change-Id: I9c6d9b48c6162f6be2b405bacfc97605909c4e5e
    BUG: 769826
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3569
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 310e29808b1aaa0208ccd13e2ba802007861231e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Jun 12 19:39:49 2012 +0530

    cluster/afr: Treat EEXIST as success in hardlink
    
    BUG: 831151
    Change-Id: I6ecc099cf5f3ae58b19dfb00ed0b3f9959e711e5
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3571
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d191f745bbec5f53e19c33702e5749fa8fba9aee
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jun 11 11:38:14 2012 +0530

    cli: Change cli output for heal commands
    
    Change-Id: I05011ba7c1fe79867e151672622e9d8669884dd2
    BUG: 826406
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3544
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c053ef8a5657426fff8f807a066e4b1bb76bd881
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue May 29 10:02:52 2012 +0530

    rpc-transport/rdma: decode and handle RDMA_ERROR msgs.
    
    RDMA_ERROR msgs are resulted as part of failure to decode requests
    or failure to send reply (for eg., reply being bigger than a msg
    that can be sent inline, but client has not provided any write-chunks
    to rdma-write into).
    
    Change-Id: I0184cfb5ff8f49ed892767345e32e6c7b01c49e7
    BUG: 822337
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3474
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0ccc7c3102676eb6e96047dd7eeaf1d55fcbfcd9
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jun 13 12:12:18 2012 +0530

    debug/io-stats: do not store the string allocated from stack into dict
    
    * Unlock if some error happens after the lock is held
    
    * White space cleanup
    
    Change-Id: If90d9a9ae91c485bb21b1ad222af445981edb77b
    BUG: 769826
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3565
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8a4c0b911c7bce4fd0fbab0cc23a59dcca93a5d3
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 22 16:08:48 2012 +0530

    gsyncd / geo-rep : failover/failback
    
    This commit is based on Venky Shankar <vshankar@>'s
    original implementation. Let us first quote Venky's
    description, then we summarize changes to his work.
    
    ------
    First version of failover/failback.
    
    Failback mechanism uses two exclusive modes:
      * blind-sync
        This mode works with xtime pairs (both master and slave) to
        identify candidated to sync the original master from the slave
    
      * wrapup-sync
        This mode is similar to the normal working of gsyncd except
        that orphaned entities in the gluster volume are not assigned
        xtimes. This prevents un-necessary transfer of data for such
        entities.
    
    Modes can be enabled via:
    
      gluster volume geo-replication M S config special_sync_mode blind
      gluster volume geo-replication M S config special_sync_mode wrapup
    
    To turn off the special modes (i.e. to revert to normal gsyncd behaviour) use:
    
      gluster volume geo-replication colon-d0 192.168.1.2::colon-d config \!special_sync_mode
    ------
    
    Code has been refactored to meet following goals:
    
    - make checkpointing work with special sync modes
    - move out sync mode related conditionals from the crawl
      loop and make all decisions to be made at startup
      time
    - be intrusive to the crawl loop to smallest possible degree
      (we will have to change/revisit it for other reasons,
      and the complexity of that should not increase)
    
    So, xtime parsing/updating/evaluation that's specific to
    the certain special modes are represented as mixin classes;
    basic operation logic is in an abstract base class.
    On startup, special-sync-mode tunable is dynamically dispatched
    to the corresponding mixin and the actual master class is
    derived from the chosen mixin and the ABS.
    
    Change-Id: Ic9b8448f31ad4239a8200dc689f7d713662a67de
    BUG: 830497
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3541
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 118ce698e8af425bf75ceab2c9e71cfdaa0ac848
Author: Csaba Henk <csaba@redhat.com>
Date:   Sun May 27 03:56:24 2012 +0530

    geo-rep: checkpointing
    
    - gluster vol geo-rep M S conf checkpoint <LABEL|now>
    
      sets a checkpoint with LABEL (the keyword "now" is special,
      it's rendered to the label "as of <timestamp of current time>")
      that's used to refer to the checkpoint in the sequel.
    
      (Technically, gsyncd makes a note of the xtime of master's root
      as of setting the checkpoint, called the "checkpoint target".)
    
    - gluster vol geo-rep M S conf \!checkpoint
    
      deletes the checkpoint.
    
    - gluster vol geo-rep M S stat
    
      if status is OK, and there is a checkpoint configured, the checkpoint
      info is appended to status (either "not yet reached", or
      "completed at <timestamp of completion>").
    
      (Technically, the worker runs a thread that monitors / serializes /
      verifies checkpoint status, and answers checkpoint status requests
      through a UNIX socket; monitoring boils down to querying the xtime
      of slave's root and comparing with the target.)
    
    - gluster vol geo-rep M S conf log-file | xargs grep checkpoint
    
      displays the checkpoint history. Set, delete and completion events
      are logged properly.
    
    Change-Id: I4398e0819f1504e6e496b4209e91a0e156e1a0f8
    BUG: 826512
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3491
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 1877c8ea84adfc6c8943bba806e410de5eba84a7
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed Jun 13 14:24:52 2012 +0530

    mgmt/glusterd: fix the infinite loop in lazy uuid generation
    
    * This is how the lazy uuid generation leads to infinite loop of function calls.
     MY_UUID -> glusterd_uuid_init -> glusterd_retrieve_uuid -> MY_UUID
    
    * Also while starting glusterd if valgrind option is not given in the volfile,
      then reset the ret variable to 0.
    
    Change-Id: Ief719f436d8a264a591ee6aefc6da3c0f6c75e8f
    BUG: 811493
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3564
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2fde351b8228720bc13f8bea3453b6af1d68c5ad
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Jun 7 14:01:46 2012 +0530

    cli: Fix time_t conversions
    
    BUG: 828058
    Change-Id: I2511a0473d9310d3a51d0994f415a5d319bfc98b
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3550
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 72301d4d542e5960c7f48832887b60c7dfff136f
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon Jun 11 16:39:17 2012 +0530

    swift: Donot display async_pending container.
    
    async_pending container is for internal, should not be exposed to the users on a
    GET.
    
    Change-Id: I460242667ae0cb5e96d4c63296f0bae4bb83b28e
    BUG: 829137
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3547
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cd439e79ca7b3b26b11fb894220550156936c354
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon May 7 13:53:31 2012 -0400

    cluster/stripe: implement the coalesce stripe file format
    
    The coalesce file format for cluster/stripe condenses the striped
    files to a contiguous layout. The elimination of holes in striped
    files eliminates space wasted via local filesystem preallocation
    heuristics and significantly improves read performance.
    
    Coalesce mode is implemented with a new 'coalesce' xlator option,
    which is user-configurable and disabled by default. The format of
    newly created files is marked with a new 'stripe-coalesce' xattr.
    Cluster/stripe handles/preserves the format of files regardless
    of the current mode of operation (i.e., a volume can
    simultaneously consist of coalesced and non-coalesced files).
    Files without the stripe-coalesce attribute are assumed to have
    the traditional format to provide backward compatibility.
    
    extras/stripe-merge: support traditional and coalesce stripe formats
    
    Update the stripe-merge recovery tool to handle the traditional
    and coalesced file formats. The format of the file is detected
    automatically (and verified) via the stripe-coalesce attributes.
    
    BUG: 801887
    Change-Id: I682f0b4e819f496ddb68c9a01c4de4688280fdf8
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3282
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ed648c3b393ec06d0da7c1a9af42286fb3cc978e
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jun 7 00:45:48 2012 -0700

    glusterd: generate node UUID lazily
    
    A commonly faced problem among glusterfs users is: after a fresh
    installation of glusterfs in a virtual machine, the VM image is
    cloned to make multiple instances of the server. This breaks
    glusterd because right after glusterfs installation on the first
    boot glusterd would have created the node UUID and this gets
    inherited into the clone. The result is wierd behavior at the time
    of peer probe where glusterd does not (yet) deal with UUID
    collisions in a user friendly way.
    
    This patch is for the 'prevention' of the issue. The approach here
    is to avoid generating a UUID on the first start of glusterd, but
    instead generate a node UUID only when a node UUID is found to be
    necessary. This naturally avoids the creation of node UUID on first
    boot and prevents the issue to a large extent.
    
    This issue also needs a 'cure' patch, which gives more meaningful
    error messages to the user and provides CLI to recover from the
    situations (gluster peer reset?)
    
    Change-Id: Ieaaeeaf76ed35385844e98a8e23fc3dd8df5a208
    BUG: 811493
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3533
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 7efa697c26b31c52f0f8cc976a505ff34bfbe33d
Author: Anand Avati <avati@redhat.com>
Date:   Thu Jun 7 17:09:45 2012 -0700

    io-cache,quick-read: bring down log level
    
    log messages were unnecessarily in INFO level. The two functions
    with the same name were non-static and actually the quick-read's
    call landed in the io-cache's version:
    
    2012-06-07 17:02:29.848667] I [io-cache.c:1549:check_cache_size_ok] 0-single-master-io-cache: Max cache size is 33791991808
    [2012-06-07 17:02:29.848751] I [io-cache.c:1549:check_cache_size_ok] 0-single-master-quick-read: Max cache size is 33791991808
    
    Changed them to static declaration.
    
    Change-Id: Id9daf9593b2832e4c261f95eac6181efea8899a5
    BUG: 765227
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3536
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 81e7464a54165b5d8b40847355d3bb6fe7b6e9df
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Apr 4 12:00:30 2012 +0530

    libglusterfs : Fix validation for integer volume options.
    
    Integer volume options which specified only the min value as 0, would not be
    validated during "volume set".
    The range check for an option happened only if  both min and max were not 0. In
    the above case, even though a minium was specified, the range check did not
    happen as both min and max were 0.
    
    To allow forced validation in such cases, a new member, "validate", has been
    added to volume_options_t. This member takes the values GF_OPT_VALIDATE_BOTH,
    GF_OPT_VALIDATE_MIN and GF_OPT_VALIDATE_MAX (GF_OPT_VALIDATE_BOTH is the
    default).
    
    Change-Id: I351de0eedb6028120e5c0b073ee5d9c141dee717
    BUG: 809847
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3084
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 86ff555eaaefb616b3dde5924a40271d99314861
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Jun 6 17:28:40 2012 +0530

    mount.glusterfs: Add support for {attribute,entry}-timeout options
    
    Change-Id: Ib41a2537ac86513a008029fca818951706a144f7
    BUG: 829279
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3530
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 212e9c12c08a266c84b60cb184ed49c01cf3c158
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jun 6 13:46:50 2012 +0530

    cluster/afr: Check for null gfid_req
    
    gfid_req is set only by the fuse xlator. Fresh lookups
    performed by self-heal-daemon, rebalance will not have
    gfid at all.
    
    Change-Id: I6712e3063067ecc5f19956e75d28c86bfc19fc65
    BUG: 829203
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3529
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b8fb6096b94905e2d304cd4219a70939495bfcc5
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jun 4 19:13:49 2012 +0530

    protocol/client: Remember the gfid of opened fd
    
    This is needed when the fresh lookup triggers self-heal, gfid
    won't be present in inode yet. Similar situation happens with
    Rebalance as it does not perform inode_link.
    Added similar fix for re-opendir.
    Removed inode from fdctx and removed some duplication of code.
    
    Change-Id: Ic94e5738c8585ed86801d2eed9ddab1015246710
    BUG: 826080
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3517
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 497532ef7e5c4361ac6c2c76fe5f2d209b986953
Author: Anand Avati <avati@redhat.com>
Date:   Tue Jun 5 13:45:39 2012 -0700

    rpc-transport/socket: fix the state machine for XDATA reading
    
    The socket state machine was broken for reading XDATA on the server.
    This code was structured such that when there was a partial read in
    a particular state, some variables would remain uninitialized in the
    next 'run' of the state machine. Also did some re-org of the state
    machine with two more states to make the code more readable and similar
    in state-breakup pattern to the other states.
    
    Change-Id: Ia32c78d4b9567bb08c6df8dc9fd6f05749d312a4
    BUG: 829062
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3524
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 990bc3991a0a998dc74d43250fed40ad1f72e849
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jun 6 18:06:09 2012 +0530

    mount/fuse: use correct fdctx to inherit direct-io-values from.
    
    Change-Id: Ifea178f4dbe57720c16dc3851b262952f3d81159
    BUG: 762533
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3531
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4b09879d04606b7996cfea85af3f06a307728bee
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jun 4 10:13:19 2012 +0530

    glusterd: nfs.disable fix for "volume set help"
    
    Fixes volgen to include "nfs.disable" in output of "volume set help".
    Also fixes some incorrect entries in glusterd_volopt_map.
    
    Change-Id: Ica5edf1ece31f9daa040fcdf559c1643ecdfd568
    BUG: 828027
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3509
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit be1d2cd4d042bda2e53e3c45dd36e8ed9525ba32
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jun 5 21:59:47 2012 -0400

    rpc: avoid an invalid free of item on a list
    
    If we actually "consumed" vol_opt by putting it on THIS->volume_options,
    it's still in use and we shouldn't free it before returning.
    
    Change-Id: I8ef3e4ce8a8b9f2552faa3345f1686e173d1aa10
    BUG: 829104
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3528
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a7370dc95ec2a875c937c682e6f0c8aa31c91b4a
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Jun 1 00:52:43 2012 +0530

    glusterfsd: further fd leak fixes for graph change
    
    Change-Id: I8e23d6bb95cddbb3862c524d79d1a956956b7a51
    BUG: 789278
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3527
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ada4ab0bb93d00fcccbd566cb9cce8265ecf7c67
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jun 5 15:07:23 2012 +0530

    cli: Fix error output for peer probe on address validation failure
    
    Displays an error message and sets proper return value on failure of address
    validation in peer probe.
    
    Change-Id: I5ced5524040e19a95dc832b6f676874983d0f2a7
    BUG: 817648
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3520
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 73366888815d308feb0393775db0dc5ea8f5a026
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat Jun 2 18:36:43 2012 +0200

    Use linkat(2) when linking on symlink
    
    link(2) behavior is not standardized when it comes to symlink. BSD
    links to the symlink target (and fails if it does not exist),
    Linux links to the symlink itself. Use linkat(2) instead of link(2)
    in order to get a portable behavior.
    
    BUG: 764655
    Change-Id: If7f6f17b48a4ccf8827c3795ec147306df6b5542
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3507
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6eee473eba94697953e8b3e1b04fe5ef1de5f474
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Jun 5 14:15:54 2012 +0530

    core: coverity fixes (mostly resource leak fixes)
    
    currently working on obvious resource leak reports in coverity
    
    Change-Id: I261f4c578987b16da399ab5a504ad0fda0b176b1
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 789278
    Reviewed-on: http://review.gluster.com/3265
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 04fd2972fe8a9b9568ac781ba7677f13fdce0f57
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Jun 5 15:02:49 2012 +0530

    glusterd: Set errstr for duplicate add-brick
    
    Sets op_errstr when add-brick is given a duplicate brick.
    
    Change-Id: I7b8f8139f9f09834a71a5abc725692b145896830
    BUG: 803336
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3519
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0baa65b651036ada96d9fc190232e4f100dc12e8
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Mar 23 16:44:38 2012 -0400

    replicate: default read_child to a local brick if there is one.
    
    Controlled by the "choose-local" option (on by default).
    
    Change-Id: I560f27c81703f2c9c62fdb51532c8eb763826df7
    BUG: 806462
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3005
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4ffd6292486f42628e1e9e01e3267daadc86698a
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jun 5 17:52:03 2012 +0530

    fuse: be good at suicide
    
    We get hung on the exit path if we kill only
    the current thread on AUTH_FAILED. Kill indeed
    the current process.
    
    Change-Id: I36042f245a22bd2a284df37fd6d3a3e0b76f81e9
    BUG: 826975
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3523
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e57280a9470cb21750954a740b3aa94929321ae9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jun 4 23:23:45 2012 +0530

    Self-heald: inode_link files while crawling
    
    Change-Id: I559a3ff507b9487b1dfca7871c188a05d89ea6d6
    BUG: 826580
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3515
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7c73a25a78774bfbca9fbbafb7ead2dffafaa5b1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jun 4 10:41:50 2012 +0530

    posix: fix the 'ENOENT' logs for setxattr()
    
    from marker, setxattr() is attempted on the path even after the
    unlink() happens if the fd is still active. In such cases, we should
    not be logging the failures.
    
    Change-Id: Icdd9c951f0d331cdda0bec42ae343302b2dbafde
    BUG: 766611
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3514
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 72ac995f844bf1a0cd7e2b51e9f38e7250de9bba
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Jun 4 16:05:49 2012 +0530

    mount.glusterfs: update the glusterd WORKDIR
    
    Change-Id: I70d091611d314598412b5315adcbe1b5147a8773
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 824231
    Reviewed-on: http://review.gluster.com/3513
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ba60970485e06d70ed4b973a1386e0601c49a86d
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Jun 4 09:56:33 2012 +0530

    libglusterfs: valid_host_name() fix
    
    Fix valid_host_name() to allow single character hostnames.
    
    Change-Id: I72527ecedec52fa47336d95b0586eb18dac6273d
    BUG: 827403
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3508
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2ec55e40aee7ba0905b4e1eafbbff07bfbba15a5
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Jun 1 11:09:07 2012 +0530

    protocol/client: do not ignore the xdata received for some fops
    
    opendir, fsetattr, fsync, lk were sending NULL xdata to the server
    even though it (xdata) had values within it.
    
    Change-Id: Ic274ab903c5c1e443409dd250ede80cd85d10b36
    BUG: 826923
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3502
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3dc56cbd16b1074d7ca1a4fe4c5bf44400eb63ff
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun May 13 07:43:32 2012 +0200

    Use inet as default listener
    
    This patch was proposed by Anand Babu Periasamy on gluster-devel@
    It fixes the inet/inet6 mismatch between client/glusterfsd/glusterd at mine
    
    BUG: 764655
    Change-Id: I172570aa58ea08c4c74cfd28f121d3d4e02a55e0
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3319
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Anand Babu Periasamy <abperiasamy@gmail.com>
    Reviewed-by: Anand Babu Periasamy <abperiasamy@gmail.com>

commit 6aa52274afb95c0c79df23d8a2093fbd557935d2
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 23 16:44:25 2012 +0530

    glusterd-volgen: by default include 'cluster/distribute' in volfile
    
    include 'cluster/distribute' even if there is just one brick in the
    volume, that way, the directories would have some of the required
    extended attributes on it before a 'add-brick'.
    
    this fixes the issues of applications getting errored out when a
    'add-brick' is done when a volume had only one brick before.
    
    Change-Id: Ie9d559e6b26aafd3d67908ab20a006e4e5e70d73
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815227
    Reviewed-on: http://review.gluster.com/3213
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2084c0e3d748b7e28d2fc9749ad9d1e2bf63208c
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Apr 24 11:53:56 2012 +0200

    cli: let commands specify the exit value in batch mode
    
    Old behavior: when cli is ran in batch mode (sequence of commands are
    fed to it in stdin), if a command returns an error (ie. -1), the cli
    exits upon it with 255 (-1 on 8 bit).
    
    New behavior: consider any non-zero return from cli commands as error
    and use the negative of that return value as exit value, thus giving
    control to cli commands over the exit value, while (as of the existing
    command set) adhering to the convention of exiting with 1 on error.
    
    Spotted upon stumbling upon mount/umount commands which did want
    to exit with 1 on error but that was not possible as of old behavior.
    
    Change-Id: I6f41191cdc718c3e676cfae1e404152f4cb715c5
    BUG: 765214
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3218
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 982be4925851e13b027c5dce59e7a92a76cb9aae
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 9 16:52:53 2012 +0530

    mount.glusterfs: enhance option 'transport=' for 'rdma'
    
    Change-Id: I9e05cc8f4b73c6a83a4be956423f4e209237c215
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 798163
    Reviewed-on: http://review.gluster.com/2855
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d19e38aa7c043ae101445706b5c75f61f57f51a1
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Jan 6 15:07:48 2012 +0530

    features/locks: update user_flock structure before inserting
    
    Change-Id: Idfa00e4f3263d50b327f5a2c6f13ec68ffc8fbee
    BUG: 805994
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3048
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7150f4197bd709da0a8887d5ad35e58ee2eeb72e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon May 28 16:55:52 2012 +0530

    protocol/client: provide a buffer for storing reply of readlink.
    
    since a readlink response can be bigger than size of rdma-msges
    that can be inlined, we need to provide a buffer where server
    can do an rdma-write of response.
    
    Change-Id: I6ab06c3a94702f810ab0c57b409aaaf35cc93057
    BUG: 822337
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 10ca7875b8c003ccc7d11f0406d9867d1f5a1223
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Jun 1 00:57:40 2012 +0530

    glusterd: fix issues with volume reset handling
    
    - properly resolve shortened key names
    - make sure user gets decent feedback
    
    Change-Id: I94b75f34b29cb71fb1a2edf17c3f1bf841bb552a
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    BUG: 826958
    Reviewed-on: http://review.gluster.com/3500
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1904ef07f6b0f71e4b01a505c95606a7e364596e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon May 28 15:31:36 2012 +0530

    glusterd: regenerate brick vol-files on upgrade
    
    If upgrade/downgrade option is set in glusterd it terminates
    after the volfiles are regenerated. No need for 'sleep 10'
    hack anymore.
    
    BUG: 825872
    Change-Id: I12e666eb871aad7e7efa954b9307993952745d92
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3482
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1d799568db8e5dc068795c53b864aa355040be15
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Jun 1 15:39:18 2012 +0530

    glusterd: makefile typo fix.
    
    instead of /var/lib/glusterd, symlink was pointing to /var/log/glusterd
    
    Change-Id: I485ad8d6cc8535378179621dea7539328d22454c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 824231
    Reviewed-on: http://review.gluster.com/3503
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ed6aba9463e2d247edef0eaa6248d6036fbb810b
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Jun 1 15:00:16 2012 +0530

    core: xlator option framework cleanups
    
    - Upon init/reconf, if an option is not in the opt dict,
      and a default value is neither specified, null it out.
      With this, the xlator config data that comes
      out of init/reconf becomes deterministic in terms
      of the xlator option declarations and the incoming
      option value dictionary. (Needed for correct operation
      of volume reset.)
    
    - We can rely bravely on the guarantee given by init/reconf
      as of which no NULL value is passed to the converter
      functions. Drop the spurious null check of not_null(),
      and rebaptize it to pass().
    
    Change-Id: Ifa068bcc0275456c01ed00a3a315a985eb262e49
    BUG: 765147
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3505
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0ebe766bd4211466c4f89b7d48baa0cdaaac08ed
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Wed May 23 03:37:16 2012 +0530

    nfs/nlm: when setting nlmclnt->rpc_clnt, do not overwrite old rpc_clnt
    
    Change-Id: I01a1c0c0c8d3402b8fe061258001eea2c0029e83
    BUG: 819518
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3419
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8efd28456db7fa68aabc355a8fc217430b5bf97a
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Apr 27 11:36:57 2012 -0400

    Add server-side aux-GID resolution.
    
    Change-Id: I09bcbfa41c7c31894ae35f24086bef2d90035ccc
    BUG: 827457
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3241
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 14c88a74175e921a724a747e140b95f2f631bdf4
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Fri Jun 1 16:20:19 2012 +0530

    protocol/server: do not wind opendir call if fd creation fails
    
    If resolve fails in some fd based operation, then do not use fd to get
    gfid (fd might be NULL). Use the gfid present in resolve structure.
    
    Change-Id: I1058274a2f9b4e58a76e4e6019e7c5ce1906d365
    BUG: 827376
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3504
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e8eb0a9cb6539a7607d4c134daf331400a93d136
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Mar 29 12:47:49 2012 -0400

    Optimize for small dicts, and avoid an overrun.
    
    As dicts get used more and more in the I/O path (especially for xattrs and
    the new xdata feature), removing some of their inherent inefficiency
    becomes more important.  This patch addresses some of the issues around
    allocating data_pair_t structures separately.  Along the way, I found that
    the way we're allocating the "members" hash table was subtly wrong, and
    could lead to a memory overrun.  This is a latent bug because nobody uses
    dict_get_new_full that way, but I added an assert to guard against that
    possibility.  One beneficial side effect is that we now save four pointers'
    worth of space per dict, offsetting the extra space used for the new
    members.
    
    Change-Id: Ie8c3e49f1e584daec4b0d2d8ce9dafbc76fb57b2
    BUG: 827448
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3040
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 27620d0f7d9b101cc47a13a23928f767248a8cff
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed May 30 19:02:29 2012 +0530

    protocol/client: do not access the local object after being freed
    
    Change-Id: I2d3aeb084168b9ed68a670b91e09126917f82968
    BUG: 826588
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3494
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 69dd0b2e824e6eeb585bed99d13680ce94a23d11
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu May 24 20:45:56 2012 +0530

    mgmt/glusterd: self-heals should be on in glustershd
    
    BUG: 825740
    Change-Id: I44829fb985f9c394b1e240e8ee7f8d026593add9
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3481
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4a92900e5fc7814cca2574453654b9f9cca7f43a
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Wed May 30 22:34:25 2012 +0530

    cluster/dht: set conf->defrag to NULL after freeing the defrag structure
    
    Also no need to free the xlator object after rebalance is over, as the process
    is about to be killed.
    
    Change-Id: I6973e43c0353b5de61c0b39e52a22c618be361f4
    BUG: 826584
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3495
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 833a2225449d1f4873647a61c8ba481e4db1ec4b
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 3 16:03:16 2012 +0530

    cluster/distribute: set the inode layout in readdirp_cbk() for files
    
    with this, inode-linking it in readdirp_cbk will be neater.
    
    Change-Id: Ie2cd646438f851e1755e9b6a3fc9898059bee359
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 816140
    Reviewed-on: http://review.gluster.com/2717
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ddc044bfa2840981de4003c3b9efcac84387dc2b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Mar 12 09:32:40 2012 -0400

    replicate: add hashed read-child method.
    
    Both the first-to-respond method and the round-robin method are susceptible
    to clients repeatedly choosing the same servers across a series of opens,
    creating hot spots.  Also, the code to handle a replica being down will
    ignore both methods and just choose the first remaining (which is not an
    issue for two-way but can be otherwise).  The hashed method more reliably
    avoids such hot spots.  There are three values/modes.
    
    0: use the old (broken) methods.
    
    1: select a read-child based on a hash of the file's GFID, so all clients
       will choose the same subvolume for a file (ensuring maximum consistency)
       but will distribute load for a set of files.
    
    2: select a read-child based on a hash of the file's GFID plus the client's
       PID, so different children will distribute load even for one file.
    
    Mode 2 will probably be optimal for most cases.  Using response time when we
    open the file is problematic, both because a single sample might not have
    been representative even then and because load might have shifted in the
    hours or days since (for long-lived files).  Trying to use more current load
    information can lead to "herd following" behavior which is just as bad.
    Pseudo-random distribution is likely to be the best we can reasonably do,
    just as it is for DHT.
    
    Change-Id: I798c2760411eacf32e82a85f03bb7b08a4a49461
    BUG: 802513
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/2926
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e066a5fea7bdaa5da78e49c9a5bf344af2f33d3c
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Mar 23 13:16:06 2012 -0400

    distribute: support user-specified layouts.
    
    The new type is DHT_HASH_TYPE_DM_USER=1 (on disk in network byte order) and
    we treat it the same as DHT_HASH_TYPE_DM except that we don't stomp on it
    during rebalance.
    
    Change-Id: I893571a9b89577acdea2fe868915b18d3663fd77
    BUG: 807312
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3004
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a5b8c32afba6509c4de4ec08830f5833fcbdaf1a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat May 19 16:07:42 2012 +0530

    mgmt/glusterd: Do shd validation for replicate volumes
    
    Staging needs to build graphs for replicate volumes in stopped
    state as well.
    Change-Id: I6474cd0fc43c9fa1916826d4a452f301fe7fe811
    BUG: 823128
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3489
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4bc0fa312f8a64c7ee0f52e5635d7f082454aaa2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Apr 16 14:42:56 2012 +0530

    storage/posix: Prevent gfid handle leaks
    
    The case which can lead to gfid handle leaks:
    Self-heal removes directory '/d' with 10 files in it, in brick b1.
    This dir is renamed to <landfill>/<hashval of '<brick-path>/d'>
    by posix. Before the janitor thread could remove the directory,
    self-heal could remove another directory with same path '/d'.
    Then again the rename to same path is done by posix as before.
    The gfid-handles of the old '/d', 10 files in it are not unlinked.
    
    To prevent such problems, rename the directory to be removed to
    <landfill>/<gfid-str>.
    
    Change-Id: Iad13708e1ebcc5222b64c058aa9a2d372e1bfa5b
    BUG: 811970
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3159
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d2ac835ba0d51ce1679dc71640472eecbfbaa704
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Apr 14 12:21:25 2012 +0530

    storage/posix: Move landfill inside .glusterfs
    
    Change-Id: Ia2944f891dd62e72f3c79678c3a1fed389854a90
    BUG: 811970
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3158
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 67740785050158dad8793f8d0ab6beeb30f99b3f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri May 25 16:13:41 2012 +0530

    glusterd-hooks: added support for separate namespace for 'volume set' keys
    
    The keys in the above mentioned namespace could be used by hook
    scripts to peform tasks on 'special' keys as defined by the storage
    admin. The choice of the key and its semantics of it are outside
    the scope of glusterd. It is the responsibility of the storage admin
    to keep the meaning of the key(s) consistent.
    
    If a user gives a command like
    
     'gluster volume set <VOLNAME> user.for-this-key do-this"
    
    scripts would get 'user.for-this-key=do-this' as argument.
    
    Change-Id: I5509e17d99e4ddd8bf5df968dcd51ff9a80dc3ab
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 825902
    Reviewed-on: http://review.gluster.com/3443
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cd88d3db0f48c4354711a606937a2f0b9ba7f87a
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 29 17:21:34 2012 +0530

    glusterd: cut out a standalone socket path calculation routine
    
    Change-Id: If5f196c9154ea59e37b83d3e4cad445fee6e9d45
    BUG: 826512
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3490
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit f2a3291c2fe5a00bca1e4a77a37560ec30cc24bf
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 30 19:05:06 2012 +0530

    logging: change the 'logfile' value in a locked region
    
    'logfile' is a global variable, and it can change if log-rotate
    command is issued. currently 'fprintf(logfile)' happens in a
    locked region where as the 'fclose(logfile)' can happen outside
    the locked region causing racy behavior.
    
    Change-Id: I40871e5c365303b7c602e2c302b085d64f6b945f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 826032
    Reviewed-on: http://review.gluster.com/3493
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0fd6f1491050a2ac515ecbe8a1100342a3948305
Author: Anand Avati <avati@redhat.com>
Date:   Tue May 29 22:30:53 2012 -0700

    protocol: do not log getxattr/ENODATA as warning
    
    When SELinux is enabled, most of the files do not have labels and
    result is a ton of unnecessary logs
    
    Change-Id: I0e781e2fb6bcfb3fb12298175a41f7b981af9c39
    BUG: 811217
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3486
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit be395fe8a31a580510595b672f72626d61d81493
Author: Anand Avati <avati@redhat.com>
Date:   Tue May 29 22:01:42 2012 -0700

    fuse: make SELinux support configurable
    
    Make support for SELinux labels (extended attributes) configurable
    and disabled by default as it can cause significant performance
    penalty when enabled (it need not be enabled unless specially crafted
    policies are set -- which is not by default)
    
    Change-Id: I97bc4b1c26cf055fd520e9bf2d49e52b14fe7515
    BUG: 811217
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3484
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 1c2624a3ff8a0d72bc88b1b869c255e3ca4c395d
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 15 22:12:53 2012 +0530

    glusterd: change working-directory from /etc/glusterd to /var/lib/glusterd
    
    as it is changed in RPM based install (using spec file), makes sense to do
    it everywhere, even in source install
    
    Change-Id: Ibe5ebd860b1529aca295b79d683a3b2e6797506c
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 824231
    Reviewed-on: http://review.gluster.com/3338
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c31447bda4e5e0b8e40689db9635fc5c0aa04136
Author: Raghavendra Bhat <raghavendra@redhat.com>
Date:   Mon May 28 12:15:29 2012 +0530

    performance/md-cache: make cache timeout reconfigurable via cli
    
    Change-Id: I73685bf73a14435884d3489343bbe71c331eb2a5
    BUG: 825638
    Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
    Reviewed-on: http://review.gluster.com/3458
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5f94c61868c420cd9a642d0f758a4a815eb5aae8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri May 25 00:25:05 2012 +0530

    server protocol : logging and negative case logic fixes
    
    * log 'resolve' gfid, instead of inode gfid, which fails to log
      for everything which fails to resolve.
    
    * in case of 'op_ret == -1' never look into xdata or any other
      argument.
    
    * bring uniformity in the _cbk() code.
    
    BUG: 821139
    
    This patch is not complete fix for above mentioned bug, but is
    useful the debug it properly
    
    Change-Id: I159becdde70720cba072e494f70951395dc6868f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3437
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bf7634c7ae83b0b94f392c2b8e77ed75baaa78ff
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Tue May 29 16:33:52 2012 +0530

    swift: Fix for multiple mounts on the same mount point.
    
    When swift server receives multiple requests on a volume and if the
    volume is not mounted before hand, for each request swift tries to
    mount the GlusterFS volume on the mount point. This process is racy
    and may mount multiple times on the same mount point.
    
    Also added a new option object_only in fs.conf which should be enabled
    only if the user requires ReST interface and will have better performance.
    By default it is set "off".
    
    Change-Id: Ie1718554c5aaf577e823bbd84da8e78d803e954d
    BUG: 821310
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3477
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 02a25d55acfbc5d38e2426438c5055cac6ac569b
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri May 25 23:41:19 2012 +0530

    glusterd: Run post hooks on a different thread
    
    This change ensures post hooks can 'wait' if need be
    and _not_ prevent glusterd from being able to run other operations
    meanwhile.
    
    Also ensures that post hook scripts are 'serialized'
    between transactions. ie, post hook scripts of txn1 are completed
    before post hook scripts of txn2 are started, where txn1 happens before
    txn2.
    
    Change-Id: Iaeb676737d8c67e7151127c8d1fd8c2891e10aee
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3450
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0418b0861230072f5a7b59fd54536db1b4a20843
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed May 23 14:08:37 2012 +0530

    nfs/nlm: statedump of locks
    
    This change allows statedump of nlm locks
    giving number of clients, number of locks
    each client holds and the files on which lock(s)
    is/are held.
    
    Change-Id: I6341c12ec58005ef71b93b316b527e610ff7ee8f
    BUG: 824804
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3432
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 28afac7af6989953e53b35ed7fbb944a45f691a4
Author: Anand Avati <avati@redhat.com>
Date:   Sun May 27 16:52:21 2012 -0700

    storage/posix: readdirp enhancements
    
    - avoid multiple calls to posix_istat(). use cheaper posix_pstat()
    - code re-org
    
    Change-Id: I4a2e32626ade49b7d18158952849c6fe7bd6875c
    BUG: 816140
    Reviewed-on: http://review.gluster.com/3460
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5d0194e8ed68d587ffbe0531fe634790fd51f698
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue May 29 00:35:20 2012 +0530

    build: Update licensing in buildspec
    
    Change-Id: I1d3348a99dad621608eccb08a71c85766e9ae451
    BUG: 820551
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3469
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 54ab2a3cbe534c5e716e34a365e3710666d76a46
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon May 28 23:53:14 2012 +0530

    libglusterfs: Fix incorrect NULL check
    
    Change-Id: I22e1bf1669e639b5097b2b56c90b47e8b733a34d
    BUG: 825197
    Reviewed-on: http://review.gluster.com/3467
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 99ea01aa92109f0fa5b35f47e7d04dce11baa654
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Tue May 8 15:15:31 2012 +0530

    nfs/mount: Support MOUNT protocol on UDP. Needed for NLM on solaris clients.
    
    Change-Id: I3f5c35d06827fb267a7dae53d949c61567a945d0
    BUG: 799287
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3337
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cc5b1f06a8bfd94c669007d27d0e5103a8856dc3
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed May 23 15:15:51 2012 +0530

    glusterd: Replace-brick should create dst brick path only on 'dst' node.
    
    Change-Id: I61e6f8aa44dfef85c7cd98f40b176b796422c4b2
    BUG: 824302
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3415
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fdb85ae8f90ace0d105b81217adac6790fc2c9ae
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri May 25 16:41:14 2012 +0530

    rpc-transport/rdma: logging enhancements
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: I07f00fb768dfdabdc04b43fdb8a0609098cd1838
    BUG: 822337
    Reviewed-on: http://review.gluster.com/3445
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ec51a99e89ac4a70b4b4cbce0bc57c95d568099e
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat May 26 02:24:23 2012 +0530

    glusterd/geo-rep: do away with unneded function exports
    
    Change-Id: I0c0b500bcb0b183ae445800fd334cd838b8af0d3
    BUG: 764890
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3455
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f2e05c9f7b5e484fb0deadfc37f0a33f536c4440
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat May 26 19:04:25 2012 +0530

    glusterd/geo-rep: cleanup and fixes
    
    - fix the hilarious fd leak of "geo-rep status"
    - instead of "corrupt", which can trip up users to think their
      data is in danger, use the term "defunct" to describe the
      condition when gsyncd is dead/unresponsive
    - don't use buffered I/O when unnecessary
    - stop using PATH_MAX for sizing buffers that don't hold paths
    - some cleanups wrt. memory management
    
    Change-Id: I396aacc45dc06a002318b19c60c44041fa9fa18d
    BUG: 764268
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3454
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4227ec88ab7ee386ae22ab9b6fc27152944fc9df
Author: Venky Shankar <vshankar@redhat.com>
Date:   Fri May 25 15:41:14 2012 +0530

    glusterd / geo-rep : fix rotating slave log file
    
    Attempt to rotate log files for slave that are local.
    Remote slaves (identified by the 'ssh' scheme) are
    ignored.
    
    Change-Id: I89959278c0eefffabc6a6702d4ef661cf52644a6
    BUG: 821443
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/3444
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c97c3136bd2932705bf30b354417008b4e0eff2b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri May 25 06:39:48 2012 +0200

    Switch to GNU basename_r() and dirname_r()
    
    BSD basename() and dirname() return static storage, hence they are not
    thread safe, while GNU flavors are. glusterfs assumes the GNU behavior.
    As a fix, we added a BSD-derived, thread-safe version of basename_r()
    and dirname_r() in contrib/libgen. BSD systems can use it instead of
    their built in versions.
    
    Unfortunately, there are more reliance on GNU behavior in glusterfs.
    There are place where free() is called on static storage returned by
    basename(), place where a second call to dirname() overwrite the
    string obtained once, and so forth.
    
    Each of these problems can be fixed, but it is likely to be a pandora
    box. We need to accept that glusterfs heavily rely on GNU behavior,
    and switch contrib/libgen's basename_r() and dirname_r() to the GNU
    version. This change does just that.
    
    BUG: 764655
    Change-Id: Id874b9c7aacd9aa3a7a4bd6a92a9633f5b2d6ac0
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3430
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c40b73fc453caf123e806adebac6c69b003bc636
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat May 19 02:43:05 2012 +0530

    geo-rep / gsyncd: further cleanup refinements
    
    - Regarding issue of leftover ssh control dirs:
    
      If master side worker is stuck in connection establishment
      phase, have the monitor kill it softly (ie. first by SIGTERM,
      to let it cleanup). This is trickier than sounds on first hearing,
      because if worker is stuck in waiting for a RePCe answer
      (in threading.Condition().wait()), then SIGTERM is ignored
      (more precisely, Python holds it back for the wait and resends it to
      itself when wait is over).
    
      So instead of signalling the worker only, we send TERM to the
      whole process group -- that brings down the ssh connection, which
      wakes up the waiting worker, which then can cleanup. Only problem
      is that monitor is also in the process group and it should not coomit
      a suicide. That is taken care by setting up a one-time SIGTERM
      handler in the monitor.
    
    - Regarding slave gsyncd stuck in chdir:
    
      Slave gsyncd is usually well behaved: if master does not send
      keepalives, it takes care to exit. However, if a hang occurs
      in early phase, when slave is to change to the gluster mountpoint,
      no timeout is set up for that (and unlike on master side, neither
      is there an external actor like the monitor to do that).
    
      So, to manage this scenario, we do the chdir in a (supposedly)
      short lived thread, and in the main thread we wait for the termination
      of this thread. If that does not happen within the time limit, main
      thread calls for cleanup and exit. (This logic explicitely takes the
      appropriate action in the cases when chdir succeeds or when hangs;
      but what about the remaining case, when chdir fails? Well in that case
      the chdir thread's exception handler will put the process to
      cleanup and exit route.)
    
    Change-Id: I6ad6faa9c7b1c37084d171d1e1a756abaff9eba8
    BUG: 786291
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3376
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 53343d368ae826b98a9eff195e9fcbea148c948f
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 15 22:34:02 2012 +0530

    glusterd-portmap: adhere to IANA standards while assigning brick ports
    
    RFC 6335
    
    Change-Id: Iafbba70d24db95807ae73d27c96288d18d7232e5
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 824233
    Reviewed-on: http://review.gluster.com/3339
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bd89bed0e9f968336f275d92616dd519374719d0
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed May 23 14:44:26 2012 +0530

    nfs/nlm: avoid duplicate replies for nlm procedures
    
    The way NLM handles errors and corresponding response
    messages has been simplified to avoid duplicate replies
    in case of failures.
    
    Also, unlock_cbk and unlock_fd_resume functions are moved
    in with other unlock functions.
    
    Change-Id: I94100aa3c8de95dabebed4598651bbcd49d95782
    BUG: 824316
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3414
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5b13919fa5ae449c7b796f9de3454bb9f0f886a3
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu May 24 12:51:32 2012 +0530

    glusterd/remove-brick: Reset decommission stats on all nodes
    
    Decommissioning is started only on nodes where the bricks which
    are being decommissioned are present. The stats were reset only
    when decommission was started. Hence stale stats were being
    shown on nodes where the bricks were not present.
    
    BUG: 822778
    
    Change-Id: I2d839f877d4e040b463bebde5ba753b7265ab633
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3425
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6af14c76f45754b190e74c824f73227190382ed3
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed May 23 14:54:02 2012 +0530

    geo-rep / gsyncd: add "--super" to rsync invocation
    
    This forces rsync to perform supposedly privileged operations on
    unprivileged slaves (like chown(2)).
    
    For consistent behavior (with gsyncd's "chown" RPC call that's
    being used for symlinks and directories), we also pass
    "--numeric-ids" to rsync.
    
    Also took the chance to retire gsyncd's "--rsync-extra" option
    which was there for debugging purposes (related to a resolved
    issue).
    
    Change-Id: I4ee4d0d3a8c4e0f6746d34d7722c8a567a67491c
    BUG: 822121
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3426
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6846a3343ff5d94262734a682a672983a75ef878
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu May 24 19:56:55 2012 +0530

    cluster/afr: decrement changelog when fdctx is absent
    
    Change-Id: I9d76ddbd2cf8e4e8e4ad70529ba3a70178489a68
    BUG: 765194
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3435
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 89b3466373191b7d2f0001778308b2393ea74da6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu May 24 12:58:04 2012 +0530

    rpc: fix the vecsizer issue
    
    * currently, we needed 'base-address' of the header for glusterfs
      writev vecsizer and 'current-address' of the buffer which is
      reading the data on socket, for nfs write vecsizer.
    
    * nfs write issues started coming after http://review.gluster.com/3182
      was pushed into repo, now fixed.
    
    * fixed by sending both as argument for vecsizer from the transport
    
    Change-Id: I6db360ce265ce5f083f1794ebdb3867f8cfad9ec
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 824472
    Reviewed-on: http://review.gluster.com/3431
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9f81eb0b24f27ea9797bb8a4ff062e6f77e872fd
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue May 8 16:21:29 2012 +0530

    glusterd/rebalance: Display run-time of rebalance process
    
    Added run-time value field to cli output of rebalance/remove-brick.
    
    A new cluster/distribute boolean option rebalance-stats when set to
    ON, time taken for migration of each file is logged.
    
    With rebalance-stats OFF (default), rebalance logs will only have
    entries showing time spent in each directory.
    
    Change-Id: I02a8918621120068cd71ffaf2999d30b3a2d10a2
    BUG: 821987
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3303
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit eff9a75fd95d98b30d0aaa04903ab42b56951d34
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 23 14:48:09 2012 +0530

    mount.glusterfs : multiple fixes
    
    * made log-level and other string comparisons be case insensitive
    * fixed wrong spelling, wrong command usage in case of brick inode
      computation
    * used 'cut' instead of 'tr' as piping the result to read was not
      working fine in few cases.
    
    Change-Id: I9caab481cfd80000b8ef9de7a44006729c88cc1b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 823403
    Reviewed-on: http://review.gluster.com/3413
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f5eaa270405da6b39fcad426bfd7c182fa11203f
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Apr 18 14:30:16 2012 +0530

    glusterd: Disconnected bricks of 'stale' volume before deleting it.
    
    If glusterd_delete_bricks is called before glusterd got the DISCONNECT event
    from the brick that was stopped, then glusterd_brick_rpc_notify would
    dereference a free'd brickinfo. This can happen if the brick had not been
    disconnected before.
    
    Change-Id: I6c07ec50f6739422a14478a549edd06c4c0ce913
    BUG: 802015
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3183
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0c950f914270d1415c05475fc49a0be9dd33ea9b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed May 23 18:09:48 2012 +0530

    cluster/afr: Release inodelk on erase changelog failures
    
    Change-Id: I58271e1ac5a116b5bc717d7cad9f03eb7dc8a1a4
    BUG: 811551
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3417
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 69680ec053f741961a141c81fa095f76531665e2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed May 23 23:43:44 2012 +0530

    protocol/client: use correct xlator object while creating frames
    during reopening files and reacquiring locks.
    
    Change-Id: I29f42fcfa9e782ce9e323e53024e5034029914a7
    BUG: 822337
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3420
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 945e19f9d97ec0beff03add5d414e0c9bfc45c13
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed May 23 15:49:09 2012 -0400

    Fix build error from recent FUSE changes.
    
    Change-Id: Ia878949d00b1ef188b18c853763918b83521ee34
    BUG: 762389
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3423
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d65a0f9f1b31cb688719d92a257a4d8e70ae83ce
Author: Anand Avati <avati@redhat.com>
Date:   Wed May 23 12:03:51 2012 -0700

    Revert "fuse-resolve: consider cases where an entry should be resolved even when parent belongs to active itable."
    
    This reverts commit 595bc33c1d0a3a6fe3d54d3eb876ac0b336d9dea
    
    Change-Id: I6c67404d4ff0bc83cfac83d786bc6e66d221a84a
    Reviewed-on: http://review.gluster.com/3422
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2606b87470e396e3e79269764e01f572da051e41
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat May 19 14:49:21 2012 +0530

    performance/quick-read: fix race-conditions in qr_unlink.
    
    The list of fds on which open needs to be done as part of unlink,
    was being modified at different places using different locks.
    This resulted in a race-condition where open was marked as in-transit,
    but fdctx was removed from the list of fds on which open was being
    sent even before open was done. Because of this, open_in_transit would
    be set forever (as an open was never actually sent, there would be no
    open_cbk called and hence we could not reset the variable), blocking
    all the future fd based fops on this fd.
    
    Change-Id: Ie84a55bee578869a9a060a094ba28480e7643ae8
    BUG: 819490
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3371
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bb8a0664ef36809d8b8e75fcb973a2089e5d08a6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 23 12:59:02 2012 +0530

    distribute: use global synctask 'env' instead of local
    
    creating a local synctask_env can lead to creating of many more
    syncop threads than required. The current syncop logic can handle
    the scale-up/scale-down of threads depending on the load. Hence,
    its neater to use global synctask env.
    
    Change-Id: Id46f963a0190c0154513317ae03323db155ac15a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 823774
    Reviewed-on: http://review.gluster.com/3412
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2eb4a5b86596fbcbb1c0baa9f1b7de0843896dd9
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue May 22 17:21:20 2012 +0530

    protocol/client: do not print the null gfid when symlink fails
    
    Change-Id: I1a2748768bc30a00c4f7b2e2fda1d282bc581658
    BUG: 823880
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3411
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0a1ca704cc5668a8d227b07565ea17a462666efb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue May 22 23:41:34 2012 +0530

    mount.glusterfs: use proper format specifer for getting the inode number and
                     device type for the mount point
    
    Change-Id: I3ca46cce61a08c8636ee9fc031a37a0a4bcb728e
    BUG: 764655
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3410
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7fcdcebd81fd38cbb59cf9a890e44ac01b08c3ee
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Mon May 21 18:38:11 2012 +0200

    Fix volume create
    
    Improve Krishnan Parthasarathi's patch, which fixed situation where
    a brick mount point did not had EA enabled. This fixes an incorrect
    assumption that dirname(3) returns the same address it was given as
    argument. GNU dirname(3) does it, BSD dirname(3) does not.
    
    Also makes the code a bit easier to read.
    
    Change-Id: I031fda5b9359a64eefb2279e640e73a416e58d90
    BUG: 812214
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3380
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fa287178ac714071ceacf8697bd36cc8a8a8da00
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Thu May 10 16:24:45 2012 +0530

    core: canonicalize paths
    
    canonicalize paths during add-brick, creation of volume,
    setting nfs.export-dir in volgen
    
    BUG: 789870
    Change-Id: I1d3788ac850359b0def0457113831e825a475d58
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3315
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bb2fc0a23e46413a14baef1846a9873681d32fe2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun May 20 21:02:55 2012 +0530

    cluster/afr: Unlock higher entry locks in rename entrylk failure.
    
    BUG: 823255
    Change-Id: Ic6ad33518ea42c9518a21381518bd4f4afdd87cb
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3382
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 93893b9ac06479bdfe28f94fce961594b928121a
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon May 21 15:47:28 2012 +0530

    swift: Passing account name in container_update.
    
    This patch also contains fixes to bugs
      * 811501
      * 812498
      * 821310
    
    Also, removed the default set of users in the proxy-server.conf file.
    
    Change-Id: Ief83905d10ff7bf7c43685ada4d7f05959cee9d1
    BUG: 821310
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3390
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit afc623f85e766a9006d7ba7cb81123ca3e10a719
Author: Kaushal M <kaushal@redhat.com>
Date:   Sun May 13 09:32:56 2012 +0530

    cli,glusterd,debug/io-stats: Clear top stats
    
    Introduces a cli command to clear "volume top" stats. The syntax for clearing
    stats is
     # gluster volume top <VOLNAME> clear [nfs]
    
    This patch also fixes io-stats xlator, to create ios_stat struct for open fop as
    well, along with create and mkdir fops. This allows stats to be recorded for
    files that exist already after clearing stats or restarting brick process, which
    would not occur otherwise.
    
    Change-Id: I1b87e192025be7bb8a51eaff3d09c747d05d7def
    BUG: 771709
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3334
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 25ee4c27d9beaac0bdbf640851639e12e8f625b2
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 24 23:49:06 2012 +0530

    nlm: do not use killall command to kill rpc.statd
    
    killall command will kill the rpc.statd process only in normal mode.
    If the process is running in valgrind mode, then killall is not able
    to kill rpc.statd and several instances of rpc.statd will be running
    for every restart of the nfs server (graph changes etc).
    
    So to avoid that get the pid of rpc.statd using /var/run/rpc.statd.pid
    and send SIGKILL signal to that pid to accomplish what killall command
    was doing.
    
    Change-Id: I2509bf918ddd0dcdd9a4562ee23f13488c7a5979
    BUG: 815756
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3225
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c7cc38b66f5e8581815d4d680190b96592313bc3
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Mar 9 09:11:23 2012 +0100

    geo-rep / gsyncd: fix cleanup of temporary mounts
    
    [This is a "forward port" of fafd5c17, http://review.gluster.com/2908]
    
    The "finally" clause that was meant to cleanup after the
    temp mount has not covered the case of getting signalled
    (eg. by monitor, upon worker timing out).
    
    So here we "outsource" the cleanup to an ephemeral child process.
    Child calls setsid(2) so it won't be bothered by internal process
    management. We use a pipe in between worker and the cleanup child;
    when child sees the worker end getting closed, it performs the cleanup.
    Worker end can get closed either because worker closes it (normal case),
    or because worker has terminated (faulty case) -- thus as bonus, we get
    a nice uniform handling with no need to differentiate between normal and
    faulty cases.
    
    The faulty case that was seen IRL -- ie., users of maintainance mounts
    hang in chdir(2) to mount point -- can be simulated for testing purposes
    by applying the following patch:
    
      diff --git a/xlators/mount/fuse/src/fuse-bridge.c b/xlators/mount/fuse/src/fuse-bridge.c
      index acd3c68..1ce5dc1 100644
      --- a/xlators/mount/fuse/src/fuse-bridge.c
      +++ b/xlators/mount/fuse/src/fuse-bridge.c
      @@ -2918,7 +2918,7 @@ fuse_init (xlator_t *this, fuse_in_header_t *finh, void *msg)
               if (fini->minor < 9)
                       *priv->msg0_len_p = sizeof(*finh) + FUSE_COMPAT_WRITE_IN_SIZE;
       #endif
      -        ret = send_fuse_obj (this, finh, &fino);
      +        ret = priv->client_pid_set ? 0 : send_fuse_obj (this, finh, &fino);
               if (ret == 0)
                       gf_log ("glusterfs-fuse", GF_LOG_INFO,
                               "FUSE inited with protocol versions:"
    
    Change-Id: I14bad56a60a7fa82d0104fa4b9a20f4e42a7186f
    BUG: 786291
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3259
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 04f6cd78fab5a2fa8a02da3be27b080a15aec203
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Fri May 18 17:43:49 2012 +0530

    nfs/nlm: nlm-unlock call should reply success in case it is not able to find the lock in the list.
    
    Change-Id: I84b298702c445320082ef03de90c924931f1a1e1
    BUG: 822384
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3368
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f42dd77fb8cdf5ef439db2c0e8eb6468419998b7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue May 1 23:30:53 2012 +0530

    protocol: handle proper vector size for writev()/readv()
    
    * fixes the offset handling issue when 'xdata' is sent in writev/readv fop
      at the transport layer itself.
    * client_writev() was not sending xdata on wire, fixed
    
    Change-Id: Ib5ced64c84d415f07032662017979c65d9a1a128
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 808078
    Reviewed-on: http://review.gluster.com/3182
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0039e876e3bfd889a92e9b51332a7e3b2b93d4b7
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sat May 19 17:14:14 2012 +0200

    Thou shalt not free(3) memory dirname(3) returned
    
    On Linux basename() and dirname() return a pointer within the string
    passed as argument. On BSD flavors, basename() and dirname() return
    static storage, or pthread specific storage. Both behaviour are
    compliant, but calling free on the result in the second case is a bug.
    
    BUG: 764655
    Change-Id: Ic82414aff1f8db2a7544b16315761ce1c05276c4
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3377
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit ce6dc515e13fad593458dab942712f9068420fd2
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 15 21:24:43 2012 +0530

    fuse: sync with upstream
    
    Cherry-picked following commits from
    git://fuse.git.sourceforge.net/gitroot/fuse/fuse
    form 555d6b50..acc5c79d interval:
    
      commit 1193a39c0869a3608f22472735bcffdcccb6b2a5
      Author: Reuben Hawkins <reubenhwk@gmail.com>
    
          cleaning up warnings
    
      commit dba9185999dfa35161d4c810735df0ab3fde5104
      Author: Laszlo Papp <ext-laszlo.papp@nokia.com>
    
          Check the 'mtablock' for negative value
    
      commit e63a9d8ee6529c9d15a87745276f45c9bdad3961
      Author: Miklos Szeredi <miklos@szeredi.hu>
    
          fusermount: clean up do_mount() function
    
      commit 81fee822a098a3e26969401fc486f136465f96f0
      Author: Laszlo Papp <ext-laszlo.papp@nokia.com>
    
          Eliminate the unused value
    
      commit 60eb44ee5eb2756465610b215968f176f4aaac6e
      Author: Laszlo Papp <ext-laszlo.papp@nokia.com>
    
          Fix resource leaks in fusermount
    
      commit d6bec4020fddd4dd67248789a1af600580f2cbda
      Author: Miklos Szeredi <mszeredi@suse.cz>
    
          In case of failure to add to /etc/mtab don't umount.
    
      commit 1e7607ff89c65b005f69e27aeb1649d624099873
      Author: Miklos Szeredi <mszeredi@suse.cz>
    
          fusermount: chdir to / before performing mount/umount
    
      commit 2fcbc2a5a94983813c533c015134c6974f8ee636
      Author: Miklos Szeredi <miklos@szeredi.hu>
    
          fusermount: don't save/restore cwd
    
      commit bd99f9cf24e16643752b02fb4fa7b48f2124ab4e
      Author: Miklos Szeredi <miklos@szeredi.hu>
    
          Fix check for read-only fs in mtab update
    
    Nb.:
    - not picked changes that implement and enforce mount/umount
      mechanisms based on newer util-linux features (umount --fake
      and --no-canonicalize)
    - not picked fusermount "auto-unmount" feature
    
    Change-Id: Ib9498516184336e77ec047e5414125332d0a4292
    BUG: 762389
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3343
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6012dfe6b9c4d69914078cc0b716bf11aac5e957
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue May 15 13:41:57 2012 +0530

    fuse: reorganize mounting code
    
    Macro-driven conditional compilation was a chaos.
    
    New scheme is:
    
    contrib/fuse-lib/mount-common.c:
      libfuse routines used both by glusterfs and fusermount
    contrib/fuse-lib/mount.c:
      libfuse-derived but customized mounting code for glusterfs
    contrib/fuse-util/mount_util.c:
      libfuse routines used only by fusermount
    
    Change-Id: I3e0ba7f74e36556b78244cd7676eb4d379939602
    BUG: 762389
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3342
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 439d0426dd60ef6c1f4af13fcbbe73f1d206acc6
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon May 14 17:07:28 2012 +0530

    fuse, glusterfsd: mount logic fixes
    
    Commit 7d0397c2 introduced two issues:
    
     i) broke the libfuse derived mount logic (details below)
    ii) in case of a daemonized glusterfs client is ran as daemon, parent
        process can return earlier than the mount is in place, which breaks
        agents that programmatically do a gluster mount via a direct call to
        glusterfs (ie. not via mount(8)).
    
    This patch fixes these issues by a refactor that merges the approaches
    sported by commits
    
      7d0397c2 fuse: allow requests during mount (needed for SELinux labels)
      c5d781e0 upon daemonizing, wait on mtab update to terminate in parent
    
    Original daemonized libfuse event flow is as follows:
    
      try:
        fd = open("/dev/fuse")
        mount("-oopts,fd=%s" % fd ...)
        mount(8) -f    # manipulate mtab
      except:
        sp = socketpair()
        env _FUSE_COMMFD=sp fusermount -oopts
        fd = receive_fd(sp)
    
      where fusermount(1) does:
        fd = open("/dev/fuse")
        mount("-oopts,fd=%d" % fd ...)
        sp = atoi(getenv("_FUSE_COMMFD"))
        send_fd(sp, fd)
    
      daemonize(
        # in child
        fuse_loop(fd)
      )
      # in parent
      exit()
    
    As of 013850c9 (instead of adopting FUSE's 47e61004¹), we went for async
    mtab manipulation, and as of c5d781e0, still wanted keep that in sync
    with termination of daemon parent, so we changed it to:
    
      try:
        fd = open("/dev/fuse")
        mount("-oopts,fd=%s" % fd ...)
        pid = fork(
          # in child
          mount(8) -f
        )
      except:
        sp = socketpair()
        env _FUSE_COMMFD=sp fusermount -oopts
        fd = receive_fd(sp)
    
      daemonize(
        fuse_loop(fd)
      )
      waitpid(pid)
      exit()
    
    (Note the new approch came only to direct [privileged] mount, so fusermount
    based mounting was already partially broken.)
    
    As of 7d0397c2, with the purpose of facilitating async mount, the event flow
    was practically reduced to:
    
      fd = open("/dev/fuse")
      fork(
        mount("-oopts,fd=%s" % fd ...)
        fork(
          mount(8) -n
        )
      )
    
      daemonize(
        fuse_loop(fd)
      )
      exit()
    
    Thus fusermount based mounting become defunct; however, the dead
    code was still kept around. So, we should either drop it or fix
    it. Also, the mtab manipulator is forked into yet another child
    with no purpose, while syncing with it in daemon parent is broken.
    mount(2) is neither synced with parent.
    
    Now we are coming to the following scheme:
    
      fd = open("/dev/fuse")
      pid = fork(
        try:
          mount("-oopts,fd=%s" % fd ...)
          mount(8) -n
        except:
          env _FUSE_DEVFD=fd fusermount -oopts
      )
    
      where fusermount(1) does:
        fd = getenv("_FUSE_DEVFD")
        mount("-oopts,fd=%s" % fd ...)
    
      daemonize(
        fuse_loop(fd)
      )
      waitpid(pid)
      exit()
    
    Nb.:
    
    - We can't help losing compatibility with upstream fusermount,
      as it sends back the fd only when mount(2) is completed,
      thus defeating the async mount approach. The
      'getenv("_FUSE_DEVFD")' mechanism is specfic to glusterfs'
      fusermount (at the moment -- sure we can talk about it with
      upstream)
    
    - fusermount opens /dev/fuse at same privilege level as of
      original process², so we can bravely go on with doing the open
      unconditionally in original process
    
    - Original mounting code actually tries to mount through
      fusermount _twice_: if first attempt fails, then, assuming
      subtype support is missing in kernel, it tries again subtype
      stripped. However, this is redundant, as fusermount internally
      also performs the subtype check³. Therefore we simplified the
      logic to have just a single fusermount call.
    
    - we revert the changes to mount.glusterfs as of 7d0397c2, as
      now there is no issue with glusterfs to work around in that scope
    
    ¹ http://fuse.git.sourceforge.net/git/gitweb.cgi?p=fuse/fuse;a=blobdiff;f=ChangeLog;h=47e61004;hb=4c3d9b19;hpb=e61b775a
    ² http://fuse.git.sourceforge.net/git/gitweb.cgi?p=fuse/fuse;a=blob;f=util/fusermount.c;h=b2e87d95#l1023
    ³ http://fuse.git.sourceforge.net/git/gitweb.cgi?p=fuse/fuse;a=blob;f=util/fusermount.c;h=b2e87d95#l839
    
    Change-Id: I0c4ab70e0c5ad7b27337228749b266bcd0ba941d
    BUG: 811217
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3341
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a2b7f11f279b9acc74c1a3b6d893fda7c160683d
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed May 16 18:22:35 2012 +0530

    common-utils: Simplified mkdir_p interface and put it to use.
    
    - Simplified mkdir_p interface.
    - Removed mkdir_if_missing from codebase
    - Modified glusterd consumers of mkdir_if_missing to use mkdir_p
      with allow_symlinks=_gf_true. This implicitly assumes that glusterd
      is in 'control' of the brick path and glusterd's working dir in the sense
      that the symlinks (if any) in any of the above mentioned paths are under
      the 'storage administrator's control.
    
    Change-Id: I7383ad5cff11b123e1e0d2fe6da0c81e03c52ed2
    BUG: 823132
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3378
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cfcc252514f3c3e99a3f40ca3415f77c2295a8e0
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon May 21 13:34:20 2012 +0530

    performance/md-cache: use mdc_fsetattr_cbk as the callback if setattr is on a fd
    
    Change-Id: I114a16055540e0cd3317b83b329600251ffe03c3
    BUG: 823886
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3386
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e43920cab790ad27a195764d8a2d94cb19bbbfc2
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Sat May 19 23:40:13 2012 +0530

    locks: Fixed opt arg parsing in clear-locks
    
    Change-Id: I470fd21d5d53e3c6f0bd2a4f84c6327532e18559
    BUG: 823151
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3391
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 16f9cf846e028d8d24138c6b34bf149b4e4ed2bf
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri May 18 22:00:03 2012 +0530

    cluster/afr: Assign gfid path if path is NULL in lookup
    
    Change-Id: I45be4ea7f04ee79b67a83134fe8ebd18067a707f
    BUG: 820355
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3373
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4accf5836251cbf348cac193ba108ea67c6888b3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon May 21 14:13:05 2012 +0530

    protocol/client: free the 'loc2' variable of client_local
    
    in common client_local_wipe(), local->loc2 was not getting freed
    up, but its used in few functions for logging purpose.
    
    Change-Id: I05715843b59aa216a79f5164a152c605dc9ad114
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 823133
    Reviewed-on: http://review.gluster.com/3388
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d37eec9667319f8d6553b030ea06f56493d1a249
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon May 21 09:05:23 2012 +0530

    protocol/server: fix a crash with NULL dereference
    
    in setxattr() and fsetxattr() _cbk functions
    
    Change-Id: I9798d182e7f68509e8e37d43cb18e4c2f4bd6fab
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 823244
    Reviewed-on: http://review.gluster.com/3384
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ad36d5b7349c7ff784116b12f5dada24121728df
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri Apr 20 17:21:12 2012 +0200

    geo-rep / gsyncd: fixes regarding the command invocation framework
    
    Some of the bugs to fix were found by the following stress-test:
    make "glusterfs --client-pid=-1" exit immediately on slave
    side.
    
    Also fix eintr_wrap which should not "adopt" exceptions generated
    by the wrapped call, by re-raising them as GsyncdError.
    
    Change-Id: Ia0d39e0635975ebbbf98d86e1e26f3122e1ed6ff
    BUG: 764678
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3258
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 7e6ee8afd7b36988c0f95bc6e1ba94a39d8ca30a
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Apr 4 03:12:26 2012 +0200

    geo-rep / gsyncd: recognize ECONNABORTED as termination of aux glusterfs
    
    Don't dump stack, rather log the "glusterfs session went down" message.
    
    If the aux glusterfs is already dead when we try to do some file
    operation, we get a failure with ENOTCONN, which is already handled
    as above. However, it's also possible that glusterfs dies while we
    are in a syscall into it -- in that case we get ECONNABORTED, and
    so far then we end up with an ugly stack strace. From now on we
    take ECONNABORTAD as well into consideration.
    
    Nb. wrt. testing: it's not easy to synthetically force the aux glusterfs
    to end this way; for that we have to provoke gsyncd into intensive
    synchronization. I succeeded in that with the following ruby oneliner:
    
    ruby -rcgi -e '
      Dir.chdir($*[0])
      a=[]
      Thread.new { loop { while a.size >= 100; File.delete a.shift; end; sleep 1 }}
      loop { a<<CGI.escape(STDIN.read 10); open(a[-1], "w") {}}' MTPT < /dev/urandom
    
    where the geo-rep master is mounted at MTPT. With this going on, deliver a
    SIGKILL to the geo-rep session's aux glusterfs. (It is giving ECONNABORTED
    non-deterministically, actually in the minority of cases.)
    
    Change-Id: I24fd8d0295cdba91d8b994057a1255ca8e2d1a67
    BUG: 764510
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3078
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 73d2435beccdf1bad1b8c650de848ab0d42ea976
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon May 7 16:59:43 2012 +0530

    geo-rep / gsyncd: typo fix
    
    fix topy.
    
    Change-Id: I84df3e850dd24d9e86713dfa401c603a84a81ca6
    BUG: 763302
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3375
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2c2dbe72edb64b80144d9fb861886c0ceb5dc757
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu May 17 14:14:13 2012 +0530

    glusterd: replace-brick should create dst brick path only once.
    
    Change-Id: I51d1a5315fa7a4290a63a59c1ef14b3e82cdc929
    BUG: 822338
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3354
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 43ff1680d9135bbc85dad24f51f02996d22580df
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed May 16 18:22:35 2012 +0530

    common-utils: Added C wrapper to mkdir(1) -p functionality.
    
    - Modified glusterd-rebalance to use mkdir_p C wrapper.
    
    Change-Id: If9a00b8c0e00af644b9c3e64a5fc94cf6201827c
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3347
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 43d9661f4ad1566981676d08f6ddf02109ca5757
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat May 19 11:14:25 2012 +0530

    protocol/server: del_locker should delete one locker per unlock
    
    Change-Id: Ie3281d693c1b6d1f631c77aece8039a08ad8f8fb
    BUG: 771595
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3370
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 46d4372003434b149a1e7cea98903e82c914e4b3
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Apr 16 21:37:31 2012 +0200

    glusterd / mountbroker: warn if mountbroker-root permissions are suspected to be too strict
    
    At the level of mountbroker, this is a best effort, as "too strict" depends
    on the purpose it's being used for (thus we just warn, don't err). However,
    it's a good guess, as it stands for existing use cases of mountbroker.
    
    Change-Id: Ic5e7d6cb44ced5509c05e0ee8a9043252470683f
    BUG: 765214
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3171
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bde1f0b8b645e3d8a4acfc859bb530af3d7dab5b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Tue May 1 11:40:17 2012 +0200

    storage/posix,fuse-bridge: fill the d_type attribute in READDIRP replies
    
    d_type should contain the type of the the dir-entry (man 3 readdir).
    Currently the d_type is always set to DT_UNKNOWN (0). The POSIX standard
    readdir() returns a 'struct dirent' on both Linux and NetBSD with the
    d_type attribute.
    
    Commit bb315cb180c3547218b5ed581d38e76aec74cf94 removed setting d_type
    in xlators/mount/fuse/src/fuse-bridge.c. This was using
    d_type_from_stat(). The stat() seems to have been removed for
    performance reasons. Instead of removing d_type completely,
    dirent->d_type could have been used. Therefore the fuse-brige can now
    add "fde->type = entry->d_type" back into fuse_readdir_cbk() without
    causing the previous performance impact.
    
    Change-Id: I4514bbc0acceb33d09c3cf50bda51e34d953efca
    BUG: 817785
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/3256
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fa90243e20eeef91eda5a5bb249bed05066852e3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Apr 14 14:33:53 2012 +0530

    cluster/afr: Enforce order in pre/post op
    
    The xattrop order in pre/post op on all the subvols
    is client-0, client-1... client-n where n is (replica-count - 1).
    This order can lead to invalid split-brains if the brick
    dies in the middle of xattrops.
    
    Example: transaction completed pre-op, so on all the subvolumes
    xattrs have '1' changelog. Now post-op is sent to both the subvols.
    On subvol-0 change-log of client-0 is decremented to 0, before
    decrementing change-log of client-1 to 0 the brick dies.
    This change-log status on subvol-0 gives the meaning that a
    change is done on subvol-0 successfully but on subvol-1 it failed.
    Which is not what happened.
    Changes done when the subvol-0 was down will lead to pending
    change-log on subvol-1 for subvol-0. Which is correct.
    When the subvol-0 is brought back up, the change-log will be in
    split-brain state even when it is not a legitimate split-brain.
    
    If the brick dies in the middle of xattrops it should remain fool.
    Pre-op should perform xattrop of the local change-log first and
    post-op should perform xattrop of the local change-log last.
    In case of optimistic changelogs txn_changelog should be done
    last on local if it succeeds, first if it fails.
    
    Change-Id: Ib6eeb20cdc49b0b1fd2f454f25a9c8e08388c6e7
    BUG: 765194
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3226
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 24c1cbf4f7afd54a506a8265de9d22ce2b2e670f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Apr 2 21:46:42 2012 +0530

    cluster/afr: Perform conservative merge on dir with xattr split-brain
    
    Change-Id: I96d59ad239c2c5efee14dd4b01a10a3f565d491e
    BUG: 765587
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3091
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ee5e73bb00cbec6a4ddd398d7461edcbe6d21f87
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Mar 13 11:15:36 2012 +0530

    cluster/afr: Handle files w.o. xattrs and size mismatch.
    
    Change-Id: Ia27ee996bed8f5915c154718bf6e859b6a2fc335
    BUG: 765587
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3090
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2a07f4fc090fe1f5cccff4d25e66cdc942ee5444
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 5 14:26:22 2012 +0530

    cluster/afr: Mark zero size file as sink in absense of xattrs.
    
    Change-Id: I4500f39a49ee16e6e88451dcf147d9f49b1d749e
    BUG: 765587
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3089
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit de5f112a08fc5993ed34cfdca687652aa3fc9ae5
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 5 11:31:47 2012 +0530

    cluster/afr: Determining sources should do both fxattrop, fstat
    
    Change-Id: Ifab37db2af8d489cd516e992b7423c765dcabc4f
    BUG: 765587
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3088
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3213a4e013e6f4a67772daa329761f42fea881f0
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu May 10 16:11:17 2012 +0530

    glusterd,cli: Enable errstr for peer detach
    
    This patch adds an op_errstr member to the gf1_cli_deprobe_rsp structure to
    enable return of an errstr to cli.
    
    Change-Id: I0cbb6805b05d7cc0603c13d1c1550bb2bd062a7a
    BUG: 816840
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3307
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit feb99ca3081f838faf9fd9cebfabab8d4c9d015c
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu May 3 10:43:38 2012 +0530

    glusterd, cli: Enable errstr for peer probe
    
    Presently glusterd only returns an errno to cli for peer probe command. This
    patch allows glusterd to return an errstr as well to cli. An op_errstr member
    has been added to gf1_cli_probe_rsp and gd1_mgmt_probe_rsp structs to allow
    this.
    In case of an error, cli will display the errstr if it was set. If errstr is not
    set cli will display the error message based on errno.
    Also, to allow for return of errstr in cases such as handshake failure, an
    errstr member has been added to the glusterd_peerctx_t struct.
    
    Change-Id: Iece2b44a7181555e960d9fe4517ec6cda4cdb385
    BUG: 816840
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3262
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4aa7bc40c9f129d6bea738941dea5b95b80d58e9
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri May 18 14:58:52 2012 +0530

    features/quota: get the top xlator from the active graph outside the list
    
    In quota reconfigure we were getting the top of the active graph within the
    list which contains the limits set on the volume. Suppose the list is empty,
    then the code inside the list traversal loop is not executed, and thus top
    will be NULL which might lead to segfault when accessed later.
    
    Change-Id: I1648d69256490878339294537e17300399ddbf2c
    BUG: 822827
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3364
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6629bab3bf3c110ce275ad184b5e358272b7593a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon May 14 16:41:10 2012 +0530

    Self-heald: Enable configuring of heal poll timeout
    
    Change-Id: I631e5bf4b3615b553b72e7ac7f490714b3b995f9
    BUG: 821395
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3329
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fb5e9b848c2dd358dc23fe56e0e95d3bfd3b9f72
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri May 18 08:14:07 2012 +0530

    glusterfs/rebalance: Register cbk for glusterfs_rebalance_event_notify
    
    In case of n/w failures, cbk needs to be passed to
    mgmt_submit_request.
    
    Change-Id: I519720dbdde4c8d46381144403751bf7ed6d3a51
    BUG: 822086
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3359
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3a4641ceb6f66d30b9f9618a613f6e01c97ca72a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri May 18 13:35:58 2012 +0530

    cli: validate quota enable/disable arguments properly
    
    Change-Id: I175cfd418fae52f3e82402c989b9f5da15058146
    BUG: 807667
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3363
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c023c1517a0b8adb3c24ddc6dfa30e4242076ee8
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed May 16 06:36:19 2012 +0200

    Provide missing basename_r and dirname_r
    
    Some systems (e.g.: NetBSD) do not have thread-safe basename(3) and
    dirname(3). This is fine with OpenGroup's Single Unix Specification
    which allows these functions to use static storage. Unfortunately,
    glusterfs uses them a lot and assume thread-safety.
    
    This patch brings FreeBSD's thread-safe basename_r(3) and dirname_r(3)
    in the contrib directory, and tweaks the build process so that
    NetBSD builds use them instead of libc basename(3) and dirname(3)
    
    BUG: 764655
    Change-Id: Ic9a159fffdc7bacc9408f8e90854e4c2db81930c
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3320
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b71d314482d572f7e54a306bb566f0f8883b2ce8
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri May 18 09:15:47 2012 +0200

    Library search order fix
    
    Set LD_LIBRARY_PATH before starting glusterfs. This avoids loading
    xlator from another glusterfs version if there are diffeent builds
    installed on the system (e.g.: in /usr, /usr/local, /opt, /usr/pkg...)
    
    BUG: 764655
    Change-Id: I13bf0bea043351498b4bc885c5ac45b108229a0a
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3361
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b0a243a6351db8acd943ba6cfb3935fa063a4fee
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri May 18 09:39:23 2012 +0200

    stat(1) portability fix
    
    stat(1) flag to specify format is not portable. This change works that
    around and makes the script a bit more readable: ${getinode} instead of
    stat -c %i
    
    BUG: 764655
    Change-Id: Iae3c40b03118078530c29d14d5f7180c36361c16
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3362
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5b6c82cfc0d07981b618fe5a7bd7f4125de9e6a4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri May 18 17:00:07 2012 +0530

    features/locks: Don't delete blocked locks in pl_flush
    
    Change-Id: I442e8d866df317b901f24cf447412179bb61a01c
    BUG: 810502
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3366
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8c112a419db6b7f5605d08d3aab964e4835eb8d9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri May 18 11:06:52 2012 +0530

    features/locks: insert_and_merge should not operate on blocked locks
    
    Change-Id: I9417fe28d6c2907b8160cd70c2d2c755731bbe67
    BUG: 810502
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3365
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 63a9bbb2a846af752e5f7f80b110fc40dc916c4d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 12 17:13:09 2012 +0530

    init.d: stop only 'glusterd' process on '/etc/init.d/glusterd stop'
    
    earlier it used to stop even brick processes and gluster NFS server
    process, which is not a expected behavior for command
    '/etc/init.d/glusterd stop'
    
    Change-Id: Ibc092cdf2693b3b2ae491d32ce3f0113854149c8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 796998
    Reviewed-on: http://review.gluster.com/2919
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 19394ef5f133d18aea757129bd903307814f1afb
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Fri May 11 12:51:38 2012 +0530

    protocol/client: Concatinate the graph uuid along with process uuid in
    setlk_version.
    
    Change-Id: Idec06c5ef1d440864e465f008a38c86395b52aba
    BUG: 820831
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3314
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 80a2d2752fcc363cba04a7421451cbe000edd6c5
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed May 16 15:40:47 2012 +0530

    geo-rep / gsyncd.c: fix coverity fix
    
    gsyncd wrapper was segfaulting as coverity fix freed
    up pointer at wrong place (after it was reused)
    
    Instead of the apporach of the original coverity fix
    that added elaborate control flow to hunt down potential
    leaks, here we move the code over to static allocations
    in place of (the not really necessary) dynamic ones.
    
    Change-Id: Ida3855ff4a4f4371b350d27f858f129ceed51785
    BUG: 789278
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3345
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8c7e1cfdebc6591bbedbe2e1b98b7b3279e6519c
Author: Alexander Bersenev <bay@hackerdom.ru>
Date:   Wed May 16 13:02:06 2012 +0600

    Fixed a memory leak in stripe translator.
    
    When iobuf is created it has reference count = 1.
    After iobref_add (local->iobref, iobuf); reference count becomes 2.
    After iobref_unref(local->iobref); it becomes 1 and never becomes 0.
    So iobuf never deletes and this causes a memory leak.
    
    I emulated it, creating files on brick manually.
    After 5 mins of:
    while true; do dd if=file of=/dev/zero bs=16384; done
    top showed me this:
    4618 root      20   0 1721m 1.5g 1868 S  0.0 16.2   5:41.77 glusterfs
    
    1.5 gb of memory has leaked.
    
    For what this if for? Can it be true in the normal conditions?
    if ((local->replies[i].op_ret < local->replies[i].requested_size) &&
        (local->stbuf_size > (local->offset + op_ret))) {
    May be delete it entirely?
    
    Change-Id: I17c115ab566e5bba662dd809e0c747db3c0310c8
    BUG: 822378
    Signed-off-by: Alexander Bersenev <bay@hackerdom.ru>
    Reviewed-on: http://review.gluster.com/3340
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Brian Foster <bfoster@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 834fa2fd36fed9b5ccd03079f780e6c5ae58f317
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu May 17 13:56:02 2012 +0530

    protocol/client: check if the name is NULL before duping it
    
    Change-Id: I1cefc34af6fae2e71b05179824963e06361c35a2
    BUG: 822385
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3353
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Anand Avati <avati@redhat.com>

commit 07c9a96627932ad3fc8c99193f8cfdae522ca9c1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri May 11 18:11:31 2012 +0530

    libglusterfs/fd: while dumping the fd_ctx use fd->xl_count
    
    While dumping the fd_ctx when statedump is issued fd->xl_count should be
    used to determine the number of xlators instead of using latest graph's count,
    since while creating the fd only those many slots would have been allocated
    as the number of xlators in the graph at that instant. Then the graph would have
    changed, thus the xl count.
    
    All the above things should happen before any operation is done on fd, otherwise
    fd_ctx_set will allocate the extra slots for the new xlators present in the
    graph.
    
    Also added the program which can be used to reproduce the bug.
    
    Change-Id: I11fe75d71ef5d37e29e2958d53752aa31098c313
    BUG: 820887
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3335
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cbcf82aa58058fe05dbd9a8d8879ca0364e5df95
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Thu Apr 12 14:49:44 2012 +0530

    nfs/nlm: procedures for PC clients
    
    *  This change introduces four NLMv4 procedures:
    
       NM_LOCK, SHARE, UNSHARE and FREE_ALL.
    
       These are used by PC clients (windows/dos) to control access
       to files.
    
       1. NM_LOCK: this lock is not monitored by statd.
    
       2. SHARE: A share reservation is a lock on the whole file
          that is taken whenever a file is opened on windows clients.
          This has ACCESS (N, R, W, RW) and DENY MODE (N, R, W, RW).
            ACCESS:    mode of access requested by the client;
            DENY MODE: what the requesting client wants to
                       deny other clients.
    
       3. UNSHARE: remove a share reservation obtained by SHARE.
          Called while closing a file.
    
       4. FREE_ALL: remove all share reservations and locks,
          both monitored and unmonitored, of the calling client.
    
    *  lock and nm_lock use a common function with only
       a flag conveying whether or not to monitor a lock.
    
    *  NOTES:
       1. SHARE reservations are not STACK_WIND'd to subsequent xlators.
          These are maintained in-memory in the nfs xlator.
    
       2. Consequently, for SHARE reservations to work effectively,
          all PC clients  *must* mount from the same gNfs server.
          Not doing so will result in different servers maintaining
          separate SHARE reservations which will not be enforced
          for obvious reasons.
    
    Change-Id: Id4f22670a94ed58691a6a7f4c80aa8c11421a277
    BUG: 800287
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3212
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>

commit d8ede99e6f429d3a63b794c495f99fc8f76e9651
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 20 17:22:43 2012 +0530

    Self-heald: Print the time stamp of the event-history
    
    Change-Id: I45767e26288ef6de6446ddf2ea82ed31e128d227
    BUG: 796579
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3277
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1d02db63ae17788c7ab28ac81dea0675500be845
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue May 15 16:31:55 2012 +0530

    client/protocol : Changes in client3_1_getxattr()
    
    Copy args->loc to local->loc in client3_1_getxattr(). This prevents logs with
    "(null) (--)" in client3_1_getxattr_cbk().
    Also save args->name in local->name and print it in the log as well.
    
    Change-Id: I1bfd00c6bbbe9f617744af7acd2f07ceafaadb3a
    BUG: 812199
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3336
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c04fe640f5a0baf146a8530cf012fe35aa9ca588
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon May 14 13:21:56 2012 +0530

    cluster/replicate: check for 'loc->path' before dereferencing it
    
    Change-Id: I4dada6fd509aa289e97fdb0b50b28300a15e6a0e
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 820355
    Reviewed-on: http://review.gluster.com/3325
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cb83c85511fc7fbfe34f97baebdda9d2bb309511
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon May 7 13:31:24 2012 +0530

    glusterd: Fixed glusterd_brick_create_path algo.
    
    - check if any prefix of the brick path has "trusted.gfid"
      or "trusted.glusterfs.volume-id" set.
    - set trusted.glusterfs.volume-id on the bricks as soon as
      its induction into the volume is settled. Earlier, the setting of
      "volume-id" used to happen during the first run of the brick process,
      leaving of window for bricks part of one volume to be (ab)used by another
      volume inadvertently.
    - removed creation of brick directory (if missing), during start volume force.
      This is to avoid directory creation as part 'force'ful starting of volume
      and leave the responsibility with the user, who understands the
      'availability' of the export directory (brick) better.
    
    Change-Id: I4237ec4ea7a4e38a7501027e7de7112edd67de8c
    BUG: 812214
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3280
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 74fbeb2d1a997a0238aa15ab2dccc98764b667a2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Mar 13 17:33:34 2012 +0530

    cluster/afr: Return EIO if read-child < 0 in inode-read fops
    
    Change-Id: I8fb2369caffae8f295774b8b12a086c66ec714c7
    BUG: 800884
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3332
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 27ae1677eb2a6ed4a04bda0df5cc92f2780c11ed
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun May 13 09:11:57 2012 +0200

    NetBSD build fixes
    
    Last batch of NetBSD build fixes, makes 3.3.0qa40 operational.
    Round 2: only include <sys/syslimits.h> for NetBSD
    
    BUG: 764655
    Change-Id: Icd7290f1e340675d763665a0d0c5f95bc14e0c55
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3321
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7503c63ee141931556cf066b9b255fc62cefcb68
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Apr 18 12:30:17 2012 +0530

    fuse-resolve: Attempt fd-migration in resolver, if migration
    was never attempted.
    
    Since fd is always associated with an inode, we can create an
    fd only after resolver resolves an inode. So, there is a possibility
    that graph-switch can happen after resolver kicks in, but before
    it can complete, thereby resulting in the newly created fd not
    migrated to new graph. So, instead of migrating fds only during
    graph-switch, we give a second chance during fd-resolution.
    
    As an example, consider following sequence of events during a
    create call:
    1. create wants to resolve parent inode, hence it starts
       resolution for parent
    2. graph-switch happens (it can happen since fuse-request reader
       thread returns after winding lookup calls)
    3. fd-migration of all the fds which are currently in fdtable is
       attempted (Note that the fd corresponding to current create call
       is not yet created and added to fd-table, hence it will not be
       migrated as part of graph switch)
    4. resolution of parent triggered as part of create, completes
    5. fd is created in fuse_create_resume and this fd is not migrated
       to new graph
    6. Any future fops on this fd will fail with EBADF errors
       (create call itself will succeed)
    
    Change-Id: Iae06ecfaca24eaacb2e166ffefbbbb57446332ba
    BUG: 804592
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3181
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4b94890c9777e7d78881d6c72ff739c91a9d3e99
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Apr 25 15:39:20 2012 +0530

    mount/fuse: Use state->lk_lock to print lock information on EAGAIN.
    
    Change-Id: I24a4a0b1c8dc0b8e08b380a5bc8efc111ccdb2c3
    BUG: 808400
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3227
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fd3d555dea7c151265ca252d3c55129ba3fcdbb6
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue May 15 16:00:52 2012 +0530

    nfs/mount: avoid duplicate reply on ENOENT
    
    Change-Id: I310e525b5bd302c0acadcc077213fbd570bf772d
    BUG: 820582
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3333
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6b993b7b515a096f61185e8a5df88adb2f7fa8e9
Author: Joe Julian <me@joejulian.name>
Date:   Tue May 15 01:09:52 2012 -0700

    Fix spelling error
    
    "temporary" was misspelled
    s/tempaory/temporary/
    
    BUG: 818884
    Change-Id: I19e28b4f0cbeeb6d7441590b0c4ddcfc49bb13d2
    Signed-off-by: Joe Julian <me@joejulian.name>
    Reviewed-on: http://review.gluster.com/3331
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4a4477ee29b7620ef28140d6fc664e0473b1ba28
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon May 14 14:50:05 2012 +0530

    cluster/dht: Handle ENOENT failure in dht_rmdir_opendir_cbk
    
    We should not treat ENOENT as a failure in rmdir.
    
    Change-Id: I1570d2be2bbafe7fc61ca39b8f7f68ee60d2c707
    BUG: 806761
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3327
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9c17a68d77f58d6b471a2601070d17dee38546d8
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sun May 13 21:56:06 2012 +0530

    features/marker: use the gfid from the stat structure instead of inode
    
    in fresh lookup, the inode would not have linked to the inode table
    until the fop reaches back to protocol/server, thus it would not contain
    the gfid within it (gfid would still be null). So use the stat structure
    to get the gfid in lookup callback instead of inode's gfid.
    
    Change-Id: Id70277f0228f3db64b05d613108cfb4f070197e6
    BUG: 791087
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3323
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8c4bf91025e2bf510a56f5789594beceb3c3827c
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Apr 27 11:41:14 2012 +0200

    NetBSD build fixes
    
    Change-Id: Ib8183d4b585465d05a7adf3a4ceae93ae1bded15
    BUG: 764655
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3238
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 511f99b88d0e1b2962b3b5bbddf722ad07d15575
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri May 11 11:23:58 2012 +0530

    build: Include COPYING-{LGPLV3,GPLV2} and remove COPYING
    
    Change-Id: Ib7867a79b3831b24b5f26cfee44b87e72f6be09b
    BUG: 820551
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3309
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7319017fae450af1d8988bc3a95eec40d913e701
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Tue May 8 07:21:17 2012 -0400

    license: dual license under GPLV2 and LGPLV3+
    
    Note that the license was not changed in any of the following:
    	.../argp-standalone/...
            .../booster/...
            .../cli/...
            .../contrib/...
            .../extras/...
            .../glusterfsd/...
            .../glusterfs-hadoop/...
            .../mod_clusterfs/...
            .../scheduler/...
            .../swift/...
    
    The license was not changed in any of the non-building xlators. The
    license was not changed in any of the xlators that seemed — to me — to
    be clearly server-side only, e.g. protocol/server
    
    Note too that copyright was changed along with the license; I did
    not change the copyright in files where the license did not change.
    
    If you find any errors or ommissions please don't hesitate to let me know.
    
    The complete list of files with the license change is:
    	libglusterfs/src/byte-order.h
    	libglusterfs/src/call-stub.c
    	libglusterfs/src/call-stub.h
    	libglusterfs/src/checksum.c
    	libglusterfs/src/checksum.h
    	libglusterfs/src/circ-buff.c
    	libglusterfs/src/circ-buff.h
    	libglusterfs/src/common-utils.c
    	libglusterfs/src/common-utils.h
    	libglusterfs/src/compat-errno.c
    	libglusterfs/src/compat-errno.h
    	libglusterfs/src/compat.c
    	libglusterfs/src/compat.h
    	libglusterfs/src/daemon.c
    	libglusterfs/src/daemon.h
    	libglusterfs/src/defaults.c
    	libglusterfs/src/defaults.h
    	libglusterfs/src/dict.c
    	libglusterfs/src/dict.h
    	libglusterfs/src/event-history.c
    	libglusterfs/src/event-history.h
    	libglusterfs/src/event.c
    	libglusterfs/src/event.h
    	libglusterfs/src/fd-lk.c
    	libglusterfs/src/fd-lk.h
    	libglusterfs/src/fd.c
    	libglusterfs/src/fd.h
    	libglusterfs/src/gf-dirent.c
    	libglusterfs/src/gf-dirent.h
    	libglusterfs/src/globals.c
    	libglusterfs/src/globals.h
    	libglusterfs/src/glusterfs.h
    	libglusterfs/src/graph-print.c
    	libglusterfs/src/graph-utils.h
    	libglusterfs/src/graph.c
    	libglusterfs/src/hashfn.c
    	libglusterfs/src/hashfn.h
    	libglusterfs/src/iatt.h
    	libglusterfs/src/inode.c
    	libglusterfs/src/inode.h
    	libglusterfs/src/iobuf.c
    	libglusterfs/src/iobuf.h
    	libglusterfs/src/latency.c
    	libglusterfs/src/latency.h
    	libglusterfs/src/list.h
    	libglusterfs/src/lkowner.h
    	libglusterfs/src/locking.h
    	libglusterfs/src/logging.c
    	libglusterfs/src/logging.h
    	libglusterfs/src/mem-pool.c
    	libglusterfs/src/mem-pool.h
    	libglusterfs/src/mem-types.h
    	libglusterfs/src/options.c
    	libglusterfs/src/options.h
    	libglusterfs/src/rbthash.c
    	libglusterfs/src/rbthash.h
    	libglusterfs/src/run.c
    	libglusterfs/src/run.h
    	libglusterfs/src/scheduler.c
    	libglusterfs/src/scheduler.h
    	libglusterfs/src/stack.c
    	libglusterfs/src/stack.h
    	libglusterfs/src/statedump.c
    	libglusterfs/src/statedump.h
    	libglusterfs/src/syncop.c
    	libglusterfs/src/syncop.h
    	libglusterfs/src/syscall.c
    	libglusterfs/src/syscall.h
    	libglusterfs/src/timer.c
    	libglusterfs/src/timer.h
    	libglusterfs/src/trie.c
    	libglusterfs/src/trie.h
    	libglusterfs/src/xlator.c
    	libglusterfs/src/xlator.h
    	libglusterfsclient/src/libglusterfsclient-dentry.c
    	libglusterfsclient/src/libglusterfsclient-internals.h
    	libglusterfsclient/src/libglusterfsclient.c
    	libglusterfsclient/src/libglusterfsclient.h
    	rpc/rpc-lib/src/auth-glusterfs.c
    	rpc/rpc-lib/src/auth-null.c
    	rpc/rpc-lib/src/auth-unix.c
    	rpc/rpc-lib/src/protocol-common.h
    	rpc/rpc-lib/src/rpc-clnt.c
    	rpc/rpc-lib/src/rpc-clnt.h
    	rpc/rpc-lib/src/rpc-transport.c
    	rpc/rpc-lib/src/rpc-transport.h
    	rpc/rpc-lib/src/rpcsvc-auth.c
    	rpc/rpc-lib/src/rpcsvc-common.h
    	rpc/rpc-lib/src/rpcsvc.c
    	rpc/rpc-lib/src/rpcsvc.h
    	rpc/rpc-lib/src/xdr-common.h
    	rpc/rpc-lib/src/xdr-rpc.c
    	rpc/rpc-lib/src/xdr-rpc.h
    	rpc/rpc-lib/src/xdr-rpcclnt.c
    	rpc/rpc-lib/src/xdr-rpcclnt.h
    	rpc/rpc-transport/rdma/src/name.c
    	rpc/rpc-transport/rdma/src/name.h
    	rpc/rpc-transport/rdma/src/rdma.c
    	rpc/rpc-transport/rdma/src/rdma.h
    	rpc/rpc-transport/socket/src/name.c
    	rpc/rpc-transport/socket/src/name.h
    	rpc/rpc-transport/socket/src/socket.c
    	rpc/rpc-transport/socket/src/socket.h
    	xlators/cluster/afr/src/afr-common.c
    	xlators/cluster/afr/src/afr-dir-read.c
    	xlators/cluster/afr/src/afr-dir-read.h
    	xlators/cluster/afr/src/afr-dir-write.c
    	xlators/cluster/afr/src/afr-dir-write.h
    	xlators/cluster/afr/src/afr-inode-read.c
    	xlators/cluster/afr/src/afr-inode-read.h
    	xlators/cluster/afr/src/afr-inode-write.c
    	xlators/cluster/afr/src/afr-inode-write.h
    	xlators/cluster/afr/src/afr-lk-common.c
    	xlators/cluster/afr/src/afr-mem-types.h
    	xlators/cluster/afr/src/afr-open.c
    	xlators/cluster/afr/src/afr-self-heal-algorithm.c
    	xlators/cluster/afr/src/afr-self-heal-algorithm.h
    	xlators/cluster/afr/src/afr-self-heal-common.c
    	xlators/cluster/afr/src/afr-self-heal-common.h
    	xlators/cluster/afr/src/afr-self-heal-data.c
    	xlators/cluster/afr/src/afr-self-heal-entry.c
    	xlators/cluster/afr/src/afr-self-heal-metadata.c
    	xlators/cluster/afr/src/afr-self-heal.h
    	xlators/cluster/afr/src/afr-self-heald.c
    	xlators/cluster/afr/src/afr-self-heald.h
    	xlators/cluster/afr/src/afr-transaction.c
    	xlators/cluster/afr/src/afr-transaction.h
    	xlators/cluster/afr/src/afr.c
    	xlators/cluster/afr/src/afr.h
    	xlators/cluster/afr/src/pump.c
    	xlators/cluster/afr/src/pump.h
    	xlators/cluster/dht/src/dht-common.c
    	xlators/cluster/dht/src/dht-common.h
    	xlators/cluster/dht/src/dht-diskusage.c
    	xlators/cluster/dht/src/dht-hashfn.c
    	xlators/cluster/dht/src/dht-helper.c
    	xlators/cluster/dht/src/dht-inode-read.c
    	xlators/cluster/dht/src/dht-inode-write.c
    	xlators/cluster/dht/src/dht-layout.c
    	xlators/cluster/dht/src/dht-linkfile.c
    	xlators/cluster/dht/src/dht-mem-types.h
    	xlators/cluster/dht/src/dht-rebalance.c
    	xlators/cluster/dht/src/dht-rename.c
    	xlators/cluster/dht/src/dht-selfheal.c
    	xlators/cluster/dht/src/dht.c
    	xlators/cluster/dht/src/nufa.c
    	xlators/cluster/dht/src/switch.c
    	xlators/cluster/stripe/src/stripe-helpers.c
    	xlators/cluster/stripe/src/stripe-mem-types.h
    	xlators/cluster/stripe/src/stripe.c
    	xlators/cluster/stripe/src/stripe.h
    	xlators/features/index/src/index-mem-types.h ¹
    	xlators/features/index/src/index.c ¹
    	xlators/features/index/src/index.h ¹
    	xlators/performance/io-cache/src/io-cache.c
    	xlators/performance/io-cache/src/io-cache.h
    	xlators/performance/io-cache/src/ioc-inode.c
    	xlators/performance/io-cache/src/ioc-mem-types.h
    	xlators/performance/io-cache/src/page.c
    	xlators/performance/io-threads/src/io-threads.c
    	xlators/performance/io-threads/src/io-threads.h
    	xlators/performance/io-threads/src/iot-mem-types.h
    	xlators/performance/md-cache/src/md-cache-mem-types.h
    	xlators/performance/md-cache/src/md-cache.c
    	xlators/performance/quick-read/src/quick-read-mem-types.h
    	xlators/performance/quick-read/src/quick-read.c
    	xlators/performance/quick-read/src/quick-read.h
    	xlators/performance/read-ahead/src/page.c
    	xlators/performance/read-ahead/src/read-ahead-mem-types.h
    	xlators/performance/read-ahead/src/read-ahead.c
    	xlators/performance/read-ahead/src/read-ahead.h
    	xlators/performance/symlink-cache/src/symlink-cache.c
    	xlators/performance/write-behind/src/write-behind-mem-types.h
    	xlators/performance/write-behind/src/write-behind.c
    	xlators/protocol/auth/addr/src/addr.c ¹
    	xlators/protocol/auth/login/src/login.c ¹
    	xlators/protocol/client/src/client-callback.c
    	xlators/protocol/client/src/client-handshake.c
    	xlators/protocol/client/src/client-helpers.c
    	xlators/protocol/client/src/client-lk.c
    	xlators/protocol/client/src/client-mem-types.h
    	xlators/protocol/client/src/client.c
    	xlators/protocol/client/src/client.h
    	xlators/protocol/client/src/client3_1-fops.c
    
    ¹ Copyright only, license reverted to original
    
    Change-Id: If560e826c61b6b26f8b9af7bed6e4bcbaeba31a8
    BUG: 820551
    Signed-off-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3304
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f6694199e637f67051b02ae423a4823a1594ee50
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Wed May 9 14:06:58 2012 -0400

    glusterfs.spec.in, Add BuildRequires: libxml2-devel so that configure will
    DTRT on Fedora's Koji build system
    
    Change-Id: I14a64d2e562282e4e7d1d37b526c112c9f343454
    BUG: 819916
    Signed-off-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3305
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Joe Julian <me@joejulian.name>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 72da7808cb0497b4ac6df55c58c9bf34daeee7ac
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu May 10 15:48:22 2012 +0530

    locks: Set flock.l_type on successful F_UNLCK to signal last unlock on fd.
    
    NLM expects a successful F_UNLCK on an fd to set flock.l_type to F_UNLCK
    if it were the last unlock else F_RDLCK.
    
    Change-Id: Ib304ac6102664abbb13d1fda649b3da63f1ee97e
    BUG: 800300
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3306
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4789058d916de596720213154cd1e2f73695aa13
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu May 10 22:22:45 2012 +0530

    build: Include protocol/server* shared libraries in the glusterfs-server rpm
    
    Change-Id: I46354dd8c0e9c9d81366d3e92af4a24a9d2c568a
    BUG: 764702
    Reviewed-on: http://review.gluster.com/3308
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 17b0814243b4ccd56c0ce570b7f42d5e572e1e71
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu May 3 16:39:55 2012 +0530

    geo-replication: coverity resource leak fixes
    
    Change-Id: I5739e9c9ae6fe78a6defb640d630e5f918ac1295
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 789278
    Reviewed-on: http://review.gluster.com/3266
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 53a09f49abb291625c96409627cba348f0c35e55
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Apr 29 23:08:42 2012 +0530

    mgmt/glusterd: Avoid re-starting nfs unconditionally.
    
    NFS server is restarted unconditionally when a volume option is
    configured through the set interface. This patch prevents restart
    of NFS server when operations are performed on translators that
    are not part of the NFS graph.
    
    This does not prevent re-start of a NFS server when an option
    corresponding to a translator that is part of the NFS graph is
    re-configured.
    
    Change-Id: Ic4b8e48e5e7e80438f230521042c267ec3b96a25
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3247
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8af87a7ff4da6791a339e2bdb159a4b0c4a66c30
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Apr 20 18:49:40 2012 +0530

    cluster/dht: rmdir should succeed last on the hashed subvol
    
    mkdir and rename both first happen on the hashed subvol.
    Rmdir should succeed, only if all non hashed subvol succeed,
    and finally removal from hashed_subvol succeeds.
    
    if hashed_subvol is unavailable, then rmdir should be sent
    on all subvols
    
    Change-Id: I1bf5d5fc25393d0e2fde13ae403cf867a01f5ec7
    BUG: 773187
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3202
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc481386d296921d883d1b8678795eb45bb8b8b7
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue May 8 13:57:31 2012 +0530

    glusterfsd: Make sure mountpoint is an absolute path
    
    If the mountpoint path given to glusterfs is not an absolute path, convert it to
    an absolute path by concatenating it with the curren working directory.
    This prevents cases, where in gluster cannot perform clean unmounts when mount
    is done with a relative path.
    
    Change-Id: Ie25add4e1dc59171e522c4244c79a6c148844ab3
    BUG: 819466
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3302
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 27fb213be6101bca859502ac87dddc4cd0a6f272
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 26 18:44:14 2012 +0530

    fuse-resolve: consider cases where an entry should be resolved even
    when parent belongs to active itable.
    
    When parent is root, the parent inode returned will always be
    active_subvol->itable->root and hence there can be cases where we
    should explicitly resolve the entry in active graph.
    
    Change-Id: I4e82df9a351ff6b5304891abc9932495bf7ea79d
    BUG: 804592
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3007
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d6244e238976e45ccb8c64ab4a0fe443fe44c952
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu May 3 10:09:27 2012 -0400

    quick-read, md-cache: selectively cache xattr data to conserve memory
    
    The md-cache translator can cache items for a long period of time and
    thus is sensitive to memory usage associated with the items it
    references. This implements two changes to help conserve memory:
    
    - quick-read - Migrate the file content data to a local dict and
    	delete from the xdata dict that passes through the stack.
    - md-cache - Create a local dict to selectively store the xattr
    	data md-cache is interested in. This includes a slight
    	optimization to not allocate an empty dict in the case
    	where we have not received any xattr's of interest.
    
    I've tested both changes independently and together by running a
    readdirp test against several compiled source trees (~340k files).
    The base test results in a 7.7GB RSS on the client. The quick-read
    modification cuts RSS down to 4.1GB, which is still large due
    to md-cache unintelligently caching a large number of empty
    dictionaries. The combined modification cuts RSS down to 462MB
    on the same workload.
    
    NOTE: Theoretically the md-cache change should supercede the
    quick-read change, but practically I save an extra 150MB or so with
    both. I already had the change and consider it an improvement that
    quick-read clean up after itself.
    
    BUG: 812876
    Change-Id: Id59734d12dd6476b0e32480939e633448adb6884
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3268
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 11a19ce031932640584f8bc207274f4e08d97c5f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 27 18:43:23 2012 +0530

    Resolve: Assign correct path while resolving
    
    Change-Id: Ia17ff38a60225dd2e9115aaa298bed42f9e43f56
    BUG: 812277
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3248
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f233e26f99decc0b2552ed10cd81c30c684139ac
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 27 16:15:12 2012 +0530

    mgmt/gluster: Load index xlator on brick always
    
    Change-Id: I56e4fce83a6bd557a3d0dc115a7dd0cd699328e0
    BUG: 816941
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3239
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 44a1857e544f64e10e8bfb4641bedd841910a6c6
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri May 4 15:13:03 2012 +0530

    protocol/{client,server} : Log improvements
    
    Make use of gfid in log messages.
    
    Change-Id: I28548be64d19418f99ee9ccdbd3ac4ae67c6c015
    BUG: 814666
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3274
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit eb7c8dd03d84d7c3917d18a59d86c379382c8b2d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat May 5 09:54:22 2012 +0530

    glusterd: remove-brick: add more error handling
    
    with this, we can make sure, all wrong patterns in CLI can be
    reported with proper message back to user, instead of resulting
    in an wrong volume type.
    
    Change-Id: Ib461956dd7d51f7f81c19c27112d44c2adb3a66d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 803711
    Reviewed-on: http://review.gluster.com/3278
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c4dadc74fd1d1188f123eae7f2b6d6f5232e2a0f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 18 17:30:39 2012 +0530

    Self-heald: Dump the event history completely
    
    Change-Id: Icf08ef1752795276f88c343d1d74af104095c6cb
    BUG: 796579
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3276
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ca5861fdf9fdf9c29523893418312bdf1796c28e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 25 14:58:31 2012 +0530

    cluster/afr: Fix inodelk-trace logs to print lk-owners
    
    Change-Id: Icc983effcf1b6283410a162f260755e97d41ee65
    BUG: 810502
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3228
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c5d9ac3477d295b5e97166ac655a52463a0d1fb8
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Apr 23 19:58:41 2012 +0530

    cluster/afr: Perform Flush with lk-owner given by parent xlator.
    
    Lk-owner of posix-lk and flush should be same, flush can't clear
    posix-lks without that lk-owner.
    
    Change-Id: If775abb5741a0beb00c419b54d023fbd429e3cb7
    BUG: 810502
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3221
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0caffe52b8db6670dfa2b1c825477ede7ba304c6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue May 1 10:50:50 2012 +0530

    protocol/client: hold lock when cancelling ping_timer in
    client_ping_cbk.
    
    Change-Id: I2b4e723ef119c62902f8a692a8a1f424da0d08b4
    BUG: 816951
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3254
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9bd1b291e3e107250b38d05702df7cd751382bdc
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Mon Apr 30 16:43:16 2012 +0530

    libglusterfs/inode.c: do not link the inode in the dentry cache for "." and ".."
    
    Change-Id: I18c2e090c1ca64f47ce70dc63c9f73ea7def2f86
    BUG: 810828
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3220
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 298ff93eab48de51a1bd77e4b12e88a7add1d174
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu May 3 15:56:15 2012 +0530

    glusterd/store: Move remove-brick/rebalance status to node_state.info
    
    Hence forth, all node related info, which does not need chksum or
    versioning can be stored in this file. This data might not be in
    sync across nodes, as it contains only information related to
    local node.
    
    Change-Id: I88a48c1b7bb7b4c29625550a9ff349442bcc5d09
    BUG: 812234
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3141
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4ec3c04a43b89fc76c8919aadfe28fb0b8990cd0
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat May 5 16:50:18 2012 +0530

    mgmt/glusterd: allow volume start force
    
    Change-Id: If920bf0bf96b61b39bccbb10e66f5f39a55967f5
    BUG: 812214
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3279
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 530a44a7c936dca76bda30bd40abdcc47c21fa7f
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Apr 11 08:55:46 2012 +0530

    swift: Gluster object storage plugin for Openstack Swift.
    
    Change-Id: I5e07339064b1f3bb2aa5b04740ed870e114db4f9
    BUG: 811430
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3118
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3651c7425ef41eae70d86b67151b62e8b6d5a3fc
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri May 4 12:27:16 2012 +0530

    mount.glusterfs: Fix log-level
    
    Change-Id: Ia5ad073ba384e1569970ada8763a8bf9bccbc9c4
    BUG: 818835
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3272
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 44c152bd8feb089b8b6d7124f88d0d97cd80bdf2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 6 15:19:59 2012 +0530

    self-heald: loc should have gfid path for better logging
    
    Change-Id: I31e51c8bd68a72ea2216df306a2f5c738c5d155c
    BUG: 810144
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3099
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 66701832cf2db0fc3fc55bc99d01d4b0f1cb6a2a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 6 15:43:31 2012 +0530

    self-heald: Don't trigger self-heal always.
    
    - If self-heal is disabled, the crawl is always spawned but immediately
      terminated upon realizing that the self-heal-daemon is disabled. Fixed it.
    - If for some reason finding child position fails, it should still spawn timer
      and should keep the timer alive until the position is found to be REMOTE.
    
    Change-Id: I20cc6af93a1ff26f2b837bbf063bbe508b5fdc78
    BUG: 810144
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3100
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 352f09f8eb5c2487612e6e6afa20742c9b9d6df4
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri May 4 12:00:14 2012 +0530

    extras/hook-scripts: Fixed EXTRA_DIST to explicitly list *.sh files
    
    Change-Id: I48785317b42e37a6e7768c89bdb7ca8ac41220fa
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3271
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cfaf9989e63dda0cc8e4e2c5e42bcd4ad4e43c4b
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed May 2 11:59:35 2012 +0530

    stripe: don't send parent pointer in stripe_readdirp_lookup()
    
    Change-Id: I53e28f4046c13ad13c9300990a95480a5c62f180
    BUG: 808353
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3232
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e4b3c0d90c46e6dde97f57fa93ed215b0d34e0c4
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Apr 12 17:52:10 2012 +0530

    iobuf: option to provide larger size of buffers
    
    provide an option to failover to standard allocation if iobuf of
    required size doesn't exists. this can be achieved by keeping an
    arena dedicated for all the out of boundary allocations.
    
    Change-Id: I41a2bd7d353dc7bcb2e1a6e4b41735afe9865975
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 812784
    Reviewed-on: http://review.gluster.com/3136
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit d879951ca9e69632517cf13f8f8773c330c14165
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu May 3 12:45:25 2012 +0530

    glusterd/rebalance: Switch off afr self heal in rebalance process.
    
    Self heal if any will be taken care of the self heal daemon.
    
    Change-Id: I4f3c270b6fce250cbdf6f986066f64e7c4b2f29f
    BUG: 808977
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3263
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3b47032cbec05ebd90a73e362eaf2653789a09bc
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 2 14:23:27 2012 +0530

    cli: fix remove-brick output behavior in failure cases
    
    earlier it was dependant on server sending the dict for knowing
    the command. Now it preserves the dictionary in frame->local,
    which is used to understand the command.
    
    Change-Id: Ica675b497e466f77878f67792ae96b71f0704d6b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815745
    Reviewed-on: http://review.gluster.com/3235
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 5f48ad266195ec85171db48cf3dba83f98cbe728
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed May 2 18:38:52 2012 +0530

    glusterd: Added glusterd command specific optional args for hooks scripts.
    
    start volume: --first=yes if the volume is the first to be started
                  and --first=no otherwise
    
    stop volume: --last=yes if the volume is the last to be stopped
                  and --last=no otherwise
    
    set volume: -o key=value ... for every key, value supplied in
                volume set command
    
    Change-Id: Ia8530771f8b9d7424fd1c736cb4c3622b5cabec2
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3260
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d88237faa6982c9f0beca65262a220becaacb096
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed May 2 16:29:49 2012 +0530

    cluster/pump: Fixed fd leaks in pump directory traversal logic
    
    Change-Id: Ie54c8c9b19be6824445ada6bbcd4983e90a7c5c4
    BUG: 818593
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3267
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7509afb03da6fe9a0f07e902869f44d4ff545fa7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Apr 26 15:41:10 2012 +0530

    RPC: change the AUTH_GLUSTERFS_v2 value to private range
    
    As per RFC5531, the value we were using with AUTH_GLUSTERFS_v2 (6)
    is already a standard number for RPCSEC_GSS. Hence having a number
    from the free pool for now, till IANA approves a standard number
    for GlusterFS RPC itself.
    
    Change-Id: I10ef6f349bccf3cf42fadfa3861c374adae2a808
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 816148
    Reviewed-on: http://review.gluster.com/3230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos@redhat.com>
    Tested-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c204e8c2713678e990b74c98f9eda8f18d714b3d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Apr 29 09:32:43 2012 +0530

    protocol: fix memory leak of lk-owner buffer in *lk() calls
    
    Change-Id: I7fb0e1757c5e04b1a2609c9822ac79301808f671
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 768330
    Reviewed-on: http://review.gluster.com/3244
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a2ca310cd334bc4c3387107a0931f695efac5ba9
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Sat Apr 14 11:58:28 2012 +0530

    glusterd: Disallow (re)-using bricks that were part of any volume
    
    Change-Id: I001a67bed1cc3118174a5ddc2f2011e8e48d8ae8
    BUG: 812214
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3147
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b8cfc761bd7a664a4ed73999e898973c9718ecee
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri May 4 00:29:40 2012 +0530

    cluster/afr: Fix race in nonblocking entrylk
    
    Change-Id: I6d96c1aed4bf08b90b6918e3694c688eccdc2445
    BUG: 818578
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3270
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9b3def01e4b6c7c3e6899e4ad52ee64440285f54
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Apr 30 07:29:16 2012 +0530

    libgluster: Fix counting, synctask state errors
    
    When a synctask is executed in synctask_switchto, if by the time
    it goes to check the woken/sleep part a reply already comes and
    __wake is called, already running task is going to be put in runq
    this generates a false warning "re-running already running task".
    
    If the reply does not come before the woken/sleep check, then the
    running task is put in waitq which decrements env->runcount even
    when the task is not in runq, this leads to -ve runcount everytime
    a task goes from runq->switchto->waitq.
    
    This patch fixes both of them by introducing a new state for the
    task called SYNCTASK_SUSPEND just when the task is suspended before
    yeild in SYNCOP.
    
    Change-Id: Ib82182cf950f9d85b5656f6243541489a104ca3d
    BUG: 816551
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3249
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 170a3a411c88f6ce1662c55440a372f512e901d1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed May 2 11:38:33 2012 +0530

    log cleanup: in setxattr() path
    
    * in posix we log occassionally if errno is ENOTSUP, added a
      suggestion to mount with 'user_xattr' option.
    
    * changed server's *etxattr_cbk to log ENOTSUP in debug level.
    
    * changed client's *etxattr_cbk to log ENOTSUP in debug level.
    
    Change-Id: Icd604050aaa68546011f2c950ecd7883ac6ee820
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 811957
    Reviewed-on: http://review.gluster.com/3140
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7ee1c22353e3af4153d1716a5f3629615de4510e
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Apr 18 18:16:30 2012 +0530

    extras: Added hook script to help in CTDB setup
    
    Change-Id: Ib43cd3583e791aabc8cc25fe4eea43a620f73d01
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3188
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3d5d5846d86b305955c1f1fcd1f426b5ecb1df6f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Apr 26 20:07:32 2012 +0530

    glustershd: allow changing of log-level through cli
    
    Change-Id: Ie33ad4f4ffcb025b22801d6beb9b87d8325021a0
    BUG: 815903
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3234
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 69a946bfea058bd5f9776343d7ccc1864d4a81b8
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed May 2 10:31:27 2012 +0530

    rpcsvc: size check before calloc in rpcsvc_handle_disconnect
    
    Change-Id: Ib9e9e28b4fd3d68ebd4b5dcbd0ee4576217b9d4f
    BUG: 782761
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3257
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1c825e5f2498ec586c0e9123c472f6d134706e08
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Apr 27 14:34:07 2012 +0530

    mgmt/glusterd: take the statedumps of running bricks if one of the bricks is down
    
    Till now if one of the bricks of the volume is down, then statedump of that
    volume (bricks) did not take the statedumps of running bricks.
    
    This patch fixes that issue and cli command will take the statedumps of
    running brick processes.
    
    Change-Id: Id9b11905d3d759202e505c2ecfa6ccd5dce6a9ff
    BUG: 816884
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3237
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3dd38a4a35885adf6ac2e0c6c4e38d36ab862441
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Apr 29 09:51:06 2012 +0200

    get rid of ZR_PATH_MAX
    
    As suggested by Amar Tumballi
    
    Change-Id: Id1cd74fd7530e8c846f3be4a88b1fa301a728cf1
    BUG: 764655
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3243
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d09a5beae2d26803b67ab8f3de6862044a8a758c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Apr 30 16:18:50 2012 +0530

    libglusterfs/fd: use reallocated memory for intializing new graphs contexts
    
    While setting fd_ctx, if we have to scale the fd contexts, then we get the
    xl_count of the new graph and reallocate the memory for contexts so that
    it is suffecient for contexts of xlators of both new as well as old graph, and
    then initialize the new graph xlator contexts. For that we are considering the
    old pointer itself, instead of using newly reallocated pointer.
    
    Change-Id: I32c18cd69c03c771b4a63e5186c65ae658e54e92
    BUG: 817461
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3250
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 67ceb347c83e3b994791feb58fc607475fa1177e
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Mon Apr 30 09:36:38 2012 -0400

    contrib/rbtree: additional license from Richard Fontana
    
    BUG: 807724
    Change-Id: I1e9a7aac7b535687b9e48bdb0e94c7f52dc6aad7
    Signed-off-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3252
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 99bdbb2ed9697bb93f006d4060d4f1aaeb0850af
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Apr 18 15:45:44 2012 +0530

    glusterd: Fail replace-brick subcmds on bricks other src/dst.
    
    Change-Id: I5b55d3e353e70a9d4d8b7948853cbfa5b001a447
    BUG: 811956
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3184
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4c84a4cd5e5e563e1e91656f7462b4c444e5f4e6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Apr 27 13:20:21 2012 +0530

    storage/posix: fix illegal memory access in fgetxattr()
    
    we were not checking for the return value of the fgetxattr(key), and
    used to continue with the allocation even if size was -1, leading to
    wrong memory access.
    
    Change-Id: Ib5cf2e74fee95bc919b12efe89fed5cd25807efd
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815346
    Reviewed-on: http://review.gluster.com/3236
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f9ca9f09ce47715573d0ae2b5e174e8b63185b56
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Apr 27 16:19:38 2012 +0530

    storage/posix: Fix leak of dict in getxattr calls.
    
    get_new_dict does not take a ref. Ref was taken only when any data
    was added to the dict.
    But in the out tag: we call explicit unref, which would move the ref
    count to -1, if it was a unsuccessful call. unref destroys the dict
    only if ref == 0.
    
    Change-Id: Ie08c301237c2042daf90a7ef25569e3b06e3e1e9
    BUG: 816870
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3240
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c3a16c32f5bd1924766d5844c100d5aa6ce8c392
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Tue Mar 13 20:49:35 2012 +0530

    nfs: use hostname without port numbers
    
    Change-Id: I7c4cba84723a9ca73f1d1f1e9a2c479a2bfd14fe
    BUG: 798969
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2973
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8b6534031ab9b60da293e9c2ffb95141d714f973
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Apr 20 11:41:20 2012 +0530

    libglusterfs/fd.c: Dynamically scale fd->_ctx when there are no
    slots for new keys.
    
    Since while migrating fds to new graph we retain the same fd object,
    we might run out of slots for new keys in fd->_ctx after some graph
    switches.
    
    Change-Id: I1e3865c76f4703768f9b10b0453558877c2f5448
    BUG: 811562
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3201
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4213745eba97ffe1e2bdb13446fe2fd87e7c6fef
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Mar 27 15:31:50 2012 +0530

    features/quota: update inode ctx in reconfigure.
    
    Till this patch, quota was relying on lookups after reconfigure, for
    new limits to be effective. However, this might be restrictive for
    users who don't want to change directories after resetting quota
    limits.
    
    Change-Id: I236aa31fdc7dcbc01d40d38c9b5b7b0a28a4d2ea
    BUG: 802905
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3022
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Tested-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ecb818902e4ee7491aaeae21226b62a0ab806370
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Apr 26 14:28:05 2012 +0530

    cli: Make use of cli_err()
    
    Use cli_err() in case of errors instead of cli_out().
    
    Change-Id: Ib0766e59516a1ccd56a2133f33fac3877c4384d6
    BUG: 815194
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3229
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 81df001b3efb2313e68745abd84f02e24fba6e67
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Thu Apr 26 17:42:11 2012 +0530

    nlm: use correct subvolume when opening the file
    
    Change-Id: Ia0a482c89f10481184dc8f0f5b27cf6612ac114a
    BUG: 816476
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3233
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6db7f8f173d30313ab9f1d88e7a6398ac97fdf8d
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Apr 26 15:57:42 2012 +0530

    glusterfsd: Change a free() to GF_FREE()
    
    Change-Id: I19bad33864b67e7ac79d8c5e642efa19dbc5bd80
    BUG: 816163
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3231
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit bb55a0c967a829a0b5eb5a4883d86540511a9d1c
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Mon Mar 26 11:16:11 2012 -0400

    contrib/rbtree license GPL -> LGPL
    
    The latest source of rb.c in the avl-2.0.3 package from GNU/FSF is
    now licensed under LGPL, a better license for allowing our partners
    to write translators and applications for gluster.
    
    Resubmitting with a BZ. The real question is whether this is okay with
    LGPL or whether we should go all the way to a BSD-licensed implementation.
    
    Change-Id: Ifb9c344c84d960832671a2619d37b925e4dede2d
    BUG: 807724
    Signed-off-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3008
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8afd8abd982442155d727aaec82c76706d77b84f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 6 12:49:34 2012 +0530

    cluster/afr: Log enhancements
    
    Change-Id: I12918cb0a4e85310d4463bc3e75e7c89565a3218
    BUG: 810144
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3098
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e8f9d42504126f8af6bbb8d160925148ad44c5de
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Apr 24 19:39:40 2012 +0530

    pump: Removed extra dict_unref in pump_command_reply
    
    afr_local_cleanup is already performing the dict_unref on local->dict.
    
    Change-Id: I07bcb100db0a0b96b3a698c444f43f96065746fb
    BUG: 804905
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3223
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 8be3e656aa58e790c301c9078afdbd4bd4909d92
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Apr 24 10:39:31 2012 +0530

    glusterd/rebalance: Remove state dependency on rpc event
    
    Status is updated by event_notify handshake by the rebalance process.
    If there is disconnect, before rebalance process, only then the
    state is moved to failure.
    
    Change-Id: I334055397c3d38688dbef653826bc07ac47a1911
    BUG: 813167
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3165
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit bd892b972eb5df5d3f48637cc473f9622684087d
Author: shylesh <shmohan@redhat.com>
Date:   Wed Apr 25 03:00:28 2012 -0400

    cli: Show proper remove-brick usage
    
    Change-Id: I669736b34f50caa146eea47dcd8c081f6436a585
    BUG: 816051
    Signed-off-by: shylesh <shmohan@redhat.com>
    Reviewed-on: http://review.gluster.com/3224
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 8f2eba00fd315b42aeaa01d683b765fbd2ee111b
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Apr 24 10:27:18 2012 +0530

    rebalance: handshake_event_notify to make fsd talk to glusterd
    
    Event_notify can be used by others to communicate with glusterd.
    A cbk event is also added for future use.
    
    req has a op, and dict.
    rsp has op_ret, op_errno, and dict.
    
    With this, rebalance process can update the status before
    exiting.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: If5c0ec00514eb3a109a790b2ea273317611e4562
    BUG: 807126
    Reviewed-on: http://review.gluster.com/3013
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3f35280a364bd35293d3e5804eb2a659a7f174b1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 23 11:11:43 2012 +0530

    cli: implement a fn 'cli_err()' to send error messages to 'stderr'
    
    we were using 'cli_out()' to send all the possible msgs, which is not
    very friendly with scripts, because if one want to get only valid
    output with "<command> 2>/error.log 1>/proper-info.log"
    
    Change-Id: I008ebcbd90935c41dbfc1bd2adeb094ed21116cb
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815194
    Reviewed-on: http://review.gluster.com/3208
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 90d5d569b5a2333094ba8741bb29fe040b695b23
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Apr 24 10:32:53 2012 +0530

    glusterd: glusterd_op_build_payload() fix for geo-rep
    
    Change-Id: I9f625022fa6d70ccda70d197e4124fa73be8e776
    BUG: 815603
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3215
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4a0f5e49f85f88912cc9c73b379403ead82e4912
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Apr 24 16:36:52 2012 +0530

    glusterd: command check failure fixes
    
    due to the patch 29f2de478cc6a475e6ae760d9cbe7ac847e9d79c (coverity
    issues fix), geo-replications assumption of anything other than -2
    is valid error (ie, expected error), was broken, which resulted in
    staging failure of all geo-replication commands. now fixed!!!
    
    Change-Id: I26c3574e966dd8ba89ef423a3ad17aa863a62c13
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815613
    Reviewed-on: http://review.gluster.com/3219
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2a59514236630756dc996e08b50f539ccc2d3ff0
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 24 18:40:00 2012 +0530

    mount/fuse: unref the fds after they have been migrated to the new graph
    
    In fuse upon graph changes fds were being migrated to the new graph.
    It was done by taking all the fds from the fdtable in a structure and then
    migrating each fd in the structure to the new graph. But after the fds
    are migrated the structure which had the fds within it (that is refed fds)
    was being freed without unrefing the fds, thus leading to a fd leak.
    
    Change-Id: I7b25220a48954384a004373d378cee11c6109f7e
    BUG: 811552
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3222
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1fc54cf7c5e2a88cf8f59d98f6e0eb7df485ae80
Author: Anand Avati <avati@redhat.com>
Date:   Mon Apr 23 00:39:14 2012 -0700

    statedump: fix deadlock during state dump of fds
    
    Existing state dump of FD context tries to be extra safe by trying
    to call the fd dump callback outside the inode lock. It acheives
    this by taking an fd ref and unreffing it later. This exercise can
    be harmful at times when the fd unref performed by state dump ends
    up being the last unref and triggers fd_destroy. fd_destroy in turn
    triggers inode_unref which blocks on inode table lock, while the
    inode table lock was already held by the thread before it even
    attempted fd ctx dump.
    
    The fix takes away the dangerous ref/unref of the fd during state
    dump and instead calls fd_ctx_dump() whiel the inode lock is held.
    This is not a problem as long as the dump functions do not call any
    inode function which tries to take an inode lock (none of the
    existing fd dump ops do)
    
    Change-Id: Ia4b27ba5a321285d3e64896a679a00363bb1e822
    BUG: 815242
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3210
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit be2cc2f7ce90b97328d933517ce66169ae89baeb
Author: shylesh <shmohan@redhat.com>
Date:   Tue Apr 24 02:32:32 2012 -0400

    cli: Return -1 if fix-layout stop is issued
    
    Change-Id: If2e4b842029a1a720403cbec0c076f3dbf1fc6df
    BUG: 803971
    Signed-off-by: shylesh <shmohan@redhat.com>
    Reviewed-on: http://review.gluster.com/3216
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 19c2d6b3d61e2fcf52e1097de4d70ecbb2966ffd
Author: shylesh <shmohan@redhat.com>
Date:   Tue Apr 24 02:49:52 2012 -0400

    dht: Log message fix gfid's to gfids
    
    Change-Id: I9ad67b6ded05992d1b56ca843f685c4fe2b15b71
    BUG: 815186
    Signed-off-by: shylesh <shmohan@redhat.com>
    Reviewed-on: http://review.gluster.com/3217
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 5d3108d182877795eab118a448d1e21f021d7d9c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Mar 27 15:05:15 2012 +0530

    libglusterfs/inode.c: add inode_resolve
    
    inode_resolve takes an itable and path as arguments and returns either
    NULL or the inode corresponding to the path
    
    Change-Id: Id42d62cce6b04dbfec7d606120b09a1e54ab484e
    BUG: 802905
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3021
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7313b22f10fafe7773a15d8306496d1d56ef5f81
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Mar 30 15:58:43 2012 +0200

    NetBSD build fixes
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    
    Change-Id: I8f9aabeadd2f842521a82e59594115bd80155d68
    BUG: 2923
    Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
    Reviewed-on: http://review.gluster.com/3053
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 92baa61bfe5853fca301eb1e10f063097df24e2e
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Apr 18 16:51:35 2012 +0200

    geo-rep / glusterd: update list of reserved tunables
    
    (keeping up with http://review.gluster.com/399)
    
    Change-Id: Iefc095a65efaa722a980315603f9ad027ee16eba
    BUG: 764557
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3189
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7cc14db79d4579cfa50c30108fdf67ffa61cb94a
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Apr 19 14:10:44 2012 +0530

    glusterd,glusterfsd : Perform proper cleanup of connections and socket files
    
    Perform proper disconnections and cleanup in glusterd on stopping nfs-server and
    self-heal daemon processes to prevent glusterd from opening unneded unix domain
    socket connections.
    
    glusterfsd processes will cleanup the socket files properly in
    cleanup_and_exit() to prevent junk socket files.
    
    Also, fix rpcsvc_program_unregister() to preform the unregistering properly.
    
    Change-Id: I1c7302c1166cf43feba1c7a813c3dc10169dc53a
    BUG: 810089
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3168
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 7c49e18bb58e91698630f95b67bd52e79ad391ca
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Apr 21 16:20:17 2012 +0530

    glusterfsd: print entire path of functions whenever serializing a reply fails
    
    Change-Id: I72c0296e16c90ec09ecb1678b4c78e8ffd834580
    BUG: 814926
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3205
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cbd13c0c1e2abbd04aff616d9767fc7b95365707
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 23 10:55:22 2012 +0530

    cli: fix the output of 'gluster volume list'
    
    make it script friendly
    
    Change-Id: I5b196cf5cf1744090a1360eef95c9a842d7be996
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 815190
    Reviewed-on: http://review.gluster.com/3207
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 853452410adc284faba03c001f0b25188deeeea8
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Apr 16 17:53:06 2012 +0200

    gerrit / rfc.sh: further trim of fetch target
    
    We _really_ don't need anything to be fetched from anywhere except for origin.
    
    We can do away with all other tracked repos (which still can be a nuisance
    eg. if they are in a VPN that we are not happen to be joined to).
    
    Change-Id: I98b375698f999500153e5a000dc8dac5005dfaec
    BUG: 764966
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3162
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 29f2de478cc6a475e6ae760d9cbe7ac847e9d79c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Apr 13 17:29:41 2012 +0530

    core: coverity issues fixed
    
    this is not a complete set of issues getting fixed. Will
    address other issues in another patch.
    
    Change-Id: Ib01c7b11b205078cc4d0b3f11610751e32d14b69
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 789278
    Reviewed-on: http://review.gluster.com/3145
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4c9e8fad23836d87b0c4327e990c789630fe5b97
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Apr 23 12:51:50 2012 +0530

    doc: Added admin guide
    
    Change-Id: Ic60558dee0d20df0c2a1bf41e4bd072ae4774912
    BUG: 811311
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3209
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: divya M N <divyasetty@gmail.com>
    Reviewed-by: divya M N <divyasetty@gmail.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 664daecef49d5e497bb5dd867fc1f51b046d4bf2
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Apr 17 00:19:54 2012 +0200

    clean up handling of special client pids
    
    - no need to name a lower boundary [drop GF_CLIENT_PID_MIN]
    - drop utility function to decide about pid speciality [gf_pid_client_check()];
      when we implement uniform policy for special pids, use just comparison with
      GF_CLIENT_PID_MAX (currently such uniform policy exists in io-threads, where
      special clients get lowest priority)
    - io-threads: drop numeric literal, use GF_CLIENT_PID_MAX
    - xattr flipping (in fuse):
      - fuse_xattr_alloc_default() made static
      - avoid compiler warnings wrt. partial enum traversal in the switch
        by not casting the original numeric value to gf_client_pid_t (enum) type
      - trim down the switch to those cases with which there is something to do
        [GF_CLIENT_PID_GSYNCD, GF_CLIENT_PID_HADOOP]
      - eliminate the (theoretical) chance of succesfully returning
        from fuse_flip_xattr_ns() with unallocated nkey
        [as was the case with pids GF_CLIENT_PID_{MIN,MAX,DEFRAG}]
    
    Change-Id: Ic2b83b908d8e3be23a7fba1e5895869828a6194b
    BUG: 765433
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3170
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6fbf369d59cf87b903403699666d99232a372fef
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Apr 19 16:53:19 2012 -0400

    Make option code quieter to make logs more readable.
    
    A lot of this stuff is extremely uninformative, such as messages about
    default values that can be read from the code.  Having them in the logs
    makes more important messages harder to find, so they're down to
    GF_DEBUG_TRACE now.
    
    Change-Id: I18921b3deac7a01ad94c50670b90342d1130837b
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3198
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7d0397c2144810c8a396e00187a6617873c94002
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Apr 23 11:51:22 2012 -0400

    fuse: allow requests during mount (needed for SELinux labels)
    
    Change-Id: Ia1af402897e6a7290acf79617c34fdc804751729
    BUG: 811217
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3199
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit eb9003cdca755980da9ed5a3a3fb0fc52c750131
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Apr 23 10:49:02 2012 +0530

    libglusterfs: Never block syncproc
    
    Change-Id: I64cd8a2ef37926173c19a33df0716183530e22bf
    BUG: 814074
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3194
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fc024df2b6f9307f23a4a0800103555708036b17
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 2 16:32:18 2012 +0530

    cluster/distribute: handle dht_layout_normalize errors differently in
    dht_lookup_dir_cbk and dht_discover_complete.
    
    return value from dht_layout_normalize is interpreted as follows:
    
    ret > 0 - number of subvolumes returned ENOENT errors.
    ret = 0 - no anomalies found.
    ret < 0 - there are holes/overlaps.
    
    We need to handle errors differently in dht_discover_cbk because,
    if a subvolume is newly added, the directory will not be present on it
    and we cannot create a directory there since a nameless lookup has
    resulted execution in this code-path. Hence if directory is guaranteed
    to be present in atleast one subvolume and there are no holes/overlaps
    in the layout, lookup can be treated as successful.
    
    there is no change in behaviour dht_lookup_dir_cbk caused by this
    patch.
    
    Change-Id: I9b0b510f1c7de187be95a47da6c9ec57b5e38d1d
    BUG: 802233
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3069
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fdcbf065a9a4c39f08dfbe9e40695de250829bd8
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Apr 23 13:22:42 2012 +0530

    glusterfs.spec: Added hook-scripts in server rpm
    
    Change-Id: Idd0ed2a72ea9ec947eaf142b889730e8d4be63c1
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3211
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f47b0fa1ccd594be9f0cda7f756973a04c0faed6
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Sat Apr 21 17:42:10 2012 +0530

    nfs/nlm: remove /var/run/rpc.statd.pid before starting rpc.statd.
    
    Sometimes rpc.statd fails to start if rpc.statd.pid exists.
    
    Change-Id: Ic6feb375330fceb8dd6c35330757738fb5cbe16f
    BUG: 814265
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3206
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Saurabh Jain <saurabh@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 66fddb979d7f33a86869211c06e4a9ef4a54a080
Author: Anand Avati <avati@redhat.com>
Date:   Sun Apr 15 22:14:38 2012 -0700

    storage/posix: prefer absolute path handles over GFID handles
    
    Change-Id: I9afefa2f8a39c5f2c77271ea64aff95249c88821
    BUG: 791187
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3204
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e2216fbc37831f76039cae77bf724550827daa0f
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Apr 19 13:17:49 2012 +0530

    cli: Strip whitespace from "volume set" option values
    
    Strips the whitespace from options values before sending to glusterd.
    This prevents options containing whitespace to be written to the volfiles which
    would cause the volfile parser to fail.
    
    Change-Id: I46faee7b0853141fa102d06bb067c7ab499a2f6e
    BUG: 813937
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3192
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3a26a7324128aed8181959b995d09ffc19ec2265
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 18 16:17:51 2012 +0530

    mgmt/glusterd: Make priority threads configurable
    
    Change-Id: I7aa4c80fac3269052adb1b5516e9dd774d5f9e0a
    BUG: 812515
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3187
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2d836326ce8962a734ac099560256fe00e3b2c9c
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 18 14:33:01 2012 +0530

    performance/io-threads: Change the thread scaling logic.
    
    Change-Id: Idc0db1cb2c26dcb0b36a58d4d43f2da10cde62c5
    BUG: 812515
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3186
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9083ed64125f17ff04383f32300582d7b33c0be4
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Apr 20 11:20:41 2012 +0530

    storage/posix: Don't allow mkdir() on HIDDEN_DIRECTORY
    
    Change-Id: Iecbd71d13ee8a492a99689674be99b4a451593db
    BUG: 788150
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3200
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d10e17bf59966d66ebe4ea5627cf89b10bcd5fe8
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Thu Apr 5 18:42:25 2012 +0530

    nlm: register client name with statd for blocking, nonblocking and reclaim lock calls
    
    Change-Id: If983f7b2f94703442e0745c5cbd2701edb2a972a
    BUG: 809362
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3097
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 443806fcfa6332163e08a63620e54d2f6be3996e
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Apr 19 13:18:33 2012 +0530

    stripe: make sure we have complete set of subvolumes before making fop
    
    Change-Id: Ifc3b05183945a7ce3e25f8c777daaf3fd4aecff3
    BUG: 810450
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3190
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 10e8f8e7a9dbcb048fd6991d3c474e3430676859
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Apr 19 17:59:21 2012 +0530

    glusterd: Enable hooks for volume set.
    
    Change-Id: I0cfa83feea719fb98c37418ad7b8dbe613ce7641
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3193
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 857ba84a236bcfb665aa930976106d990e96db77
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Apr 19 23:51:15 2012 +0530

    rpc-transport/socket: Set NODELAY for connect socket
    
    This is essentially a re-introduction of setting TCP_NODELAY
    on the connect socket which was erroneously removed as part
    of commit 2da18b6
    
    Change-Id: Icc3a8faafce0e63a9dde592a48f22b90a72860d1
    BUG: 795635
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3197
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit cbb7a20daf7d59681eb21495361236cf68e9cd3b
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Apr 13 14:28:05 2012 +0530

    glusterd: Moved 'hooks' interface code to glusterd-hooks.*
    
    Change-Id: Ia7c0e37154414bddb05516e11b3cc4e6ae83ff38
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3142
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1a46dcecd0cfba549ae54bf61eaea2223b39c10f
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Apr 19 12:18:53 2012 +0530

    rpc-clnt: use the correct xdr_size for getting the iobuf
    
    earlier we used to get the size of rpc_msg from an empty msg, which
    was resulting in minimum size allocated for rpc-msg. the correct way
    is to fill the required fields in rpc_msg structure and then calculate
    the size, and allocate the iobuf.
    
    Change-Id: I3692831b53b8820a36e4562a1fa3d4c3dbdf4f9d
    BUG: 813787
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/3191
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3ad81d490f9e822efa34b3ffaf3c527e99af5d40
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 18 14:48:35 2012 +0530

    cluster/afr: Set errno correctly in find_fresh_parents failures
    
    Change-Id: I923103a03c1efe38285cd70842ec91b98a3f6bfd
    BUG: 765551
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3185
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c284511c1ff7639ff674bca9260553680a917aa3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 17 15:45:44 2012 +0530

    cluster/afr: Handle transient parent-entry xactions in lookup
    
    This patch addresses the case when the lookup on an entry is performed
    while it is being renamed. The lookup can possibly return 2 different
    gfids when lookup on one subvol reached before rename and on other
    after rename. In such cases the conflicting entry self-heal is
    triggered to resolve the issue, but if there are lot entry transactions
    going on the parent directory of the entry then the non-blocking
    locks could fail resulting in EIO. To avoid this, lookup queries
    locks xlator if there are any parent-entrylk on entry's basename.
    If afr finds that there are such locks and gfids are differing then
    it chooses the file with latest ctime as the iatt of the entry.
    This solution is not foolproof, but it decreases the probability of
    hitting the EIO. The correct solution is to take blocking locks on
    the parent-entry to find out the correct source. Taking blocking
    locks in lookup is not good. One stale entry lock can hang the whole
    filesystem. So we chose to go with this for now.
    
    Change-Id: Ibebb6c3074f56f80a96893b6bf5b77941e30d400
    BUG: 765551
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3179
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 64177411f7c032eeb2b65635a9ca4e5767a72b40
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Apr 4 23:37:58 2012 +0530

    extras: Added (hook) scripts to start/stop samba on volume start and stop
    
    These are example/helper scripts that demonstrate how one could
    leverage the recently added hooks interface in glusterd.
    The scripts are in 'beta'.
    
    Change-Id: I7aaf999f3bdfb276ef64e115a57cbdb36c7a896e
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3086
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f8bbf1cef9da21ea55649f5a05a88479853cd8eb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Apr 16 14:50:16 2012 +0530

    cli: do not put the frame->local to mempool since its a calloced structure
    
    In cli, frame->local is not allocated from the internal mempool, rather its
    calloced. So while destroying the stack, we have to set frame->local to NULL.
    Otherwise if frame->local is not NULL, STACK_DESTROY will try to put it back
    to the mempool and thus segfault.
    
    Change-Id: I5bd17d099e16fb8e73f3250cc022008e26e28f50
    BUG: 812735
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3167
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 678efee04855f88919904d98176b0d7c44e543d6
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Apr 18 10:49:09 2012 +0530

    cluster/dht: Remove un-used pathinfo code for link files
    
    Currently, we do not return LINK: attributes for a file
    in pathinfo requests.
    
    Change-Id: If8667bd6af06de3d11c37dd0a09726dfe1d2e330
    BUG: 795289
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3175
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 1b8f254daf05f84ebc3170e7b840608fc7baf068
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Tue Apr 17 23:58:08 2012 +0530

    nfs/nlm: disable NLM if rpc.statd is not found.
    
    Change-Id: I571e1f14cefdfabecd8996b6d0ffc928464d2b51
    BUG: 813258
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3174
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c9a8da5bb8c78aba4b2477c011e2a4f335351fd8
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 16 12:07:15 2012 +0530

    glusterd: Properly validate compressed form of IPv6 addresses
    
    Properly validate IPv6 compressed notation, when used in volume set.
    
    Change-Id: Ia489125a45472fc0971c6b11de073aaeb9b1a123
    BUG: 810442
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3152
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6ff8c16cbaa23e209d270d2d559a6072e554e68f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 18 11:44:21 2012 +0530

    cluster/afr: Build parent loc for expunge
    
    Change-Id: Ifd1a4117924a7f9a90eb8e02dd2d655f2156fabd
    BUG: 765551
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3178
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fb9f485db2b4a92c16c0683cf3d5cfcd07054d71
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 17 13:20:43 2012 +0530

    features/locks: Find parent-entrylk presence in lookup
    
    Change-Id: I8fc85676827f26b07bf578ea1152d3e251adb4af
    BUG: 765551
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3177
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c0eec503b78949bd1785e5bf2533db211f3d256c
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Apr 18 12:16:51 2012 +0530

    glusterd/rebalance: Start process with xlator option client-pid -3
    
    This would prevent updation of xtime by the marker.
    Set frame->root->pid while creating sync-task. Removing the command
    option, as it is in-effective
    
    Change-Id: Ifaa587df67a72ec0571c7d0043de8048e2be12a8
    BUG: 812287
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3180
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7522df3b98467c2ddfb9cc12f5c807d4408267cc
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Apr 17 23:30:23 2012 +0530

    glusterd (remove-brick): fix data-loss issue
    
    * when more than one brick (more than one distribute subvolume)
      was removed using single command, rebalance process used to
      get started only on one node, causing data-loss when 'commit'
      was done, because the brick's data was not migrated at all.
      Fixed the logic of validating rebalance required in remove-
      brick case.
    
    Change-Id: I3a90ff9f9593e5215110a3a0974bb97e7271f910
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 812770
    Reviewed-on: http://review.gluster.com/3173
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 7ef32ae76d1c1e4a5ff47899d175be9fdeb73bc8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 16 11:38:33 2012 +0530

    performance/quick-read: disable reading from cache if unlink has
    happened after fd was opened.
    
    If dentry being unlinked is the last one, there is a possibility that
    later, a new entry with same name being created. After creation of new
    file, we shouldn't be returning the contents of this new file, when
    application reads using fd opened before unlink.
    
    Change-Id: Ic98aa9cd76d24e8a37ce02a0aae6c66290043192
    BUG: 811976
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3151
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 80eeaab2be884f0ebc89704011421541742cd5e6
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Thu Apr 5 15:57:47 2012 +0530

    nlm: send sm-notify to clients whenever the nfs server is restarted so that clients reclaim the locks.
    
    Change-Id: I0a8e291ad0a78e2e68070b1d289d32a786da8da2
    BUG: 802885
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/3096
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b69f0110410c670eb6c31b6669d47ec2aaeb92f4
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Apr 16 12:05:45 2012 +0530

    nfs: option to disable NLM
    
    Adding support to disable/enable nlm with the following command:
             # gluster volume set <VOLNAME> nfs.nlm [on|off]
    
    Change-Id: I1ad3e44c5d4349d0f3463bfca0995fd10def39dd
    BUG: 812869
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3160
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>

commit c20f501d0632d6105f0d570ac8dec251974ebe87
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Apr 16 14:39:10 2012 +0530

    cluster/dht: Handle failures in getxattr_cbk
    
    Change-Id: Ifbce2d69f0fdd0c45cba92b6fc2dffe13c60de28
    BUG: 810106
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3156
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 0049c2405aa39fe4ef299bd646e7a53e40753039
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 16 19:31:44 2012 +0530

    glusterd : Fixes for breakages caused by volume-id validation
    
    Fixes glusterd_op_build_payload() to,
    1. take account of status cmd type when building payload for "volume status" to
       prevent "volume status all" from failing.
    2. take account of volname being "help/help-xml" in volume set to prevent
       "volume set help/help-xml" from failing
    3. obtain volname using key "master" prevent "volume geo-replication" commands
       from failing
    
    Also, fails op and sets correct op_errstr if volume not found during
    glusterd_dict_set_volid(), to make sure cli displays proper message.
    
    Change-Id: I40ded15c50b54a82ee61bf6d6e9d07f571679c8c
    BUG: 812801
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3157
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 79620e8f63148b1ad7d8180da46176a759435590
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Apr 11 17:04:15 2012 +0530

    cli: Fix for "volume status all"
    
    Fixes output of "volume status all" when some volumes are stopped and some
    changes to xml output.
    
    Change-Id: I77938422c0258bb69e32b54c23df1225474532bc
    BUG: 811539
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3130
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4359d00fcb17d22ef487bff34943475c77194692
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Apr 17 15:37:38 2012 +0530

    nlm: unregister nlm v1 when gNfs is stopped
    
    NLM v1, registered to communicate with statd
    is unregistered once gNfs is stopped.
    
    Change-Id: I165658488f4971e743736f5f77c7247590e64bd5
    BUG: 786345
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3166
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>

commit 6b0a44b4df1c1f7d70b2296862d25bf166009ebc
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Apr 17 11:23:46 2012 +0530

    protocol/server: Check if dict arg is NULL in setxattr
    
    Change-Id: I44d199ffa5d08115cc0aa7cb0b99298a9907af60
    BUG: 808067
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3164
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 41bd7281a5fe4062fabe963d7862117aca50cc3d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Apr 16 13:26:40 2012 +0530

    features/marker: fix possible NULL access in strcmp()
    
    for a given setxattr call, loc->path can be NULL now, handle
    that case properly
    
    Change-Id: Ic56ec81aa8eb62aafdb524bf22f6d84390ab1d4b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 812767
    Reviewed-on: http://review.gluster.com/3154
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 754112b7b716c68fb6cf44941ce4f343698d533e
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon Apr 16 12:57:57 2012 +0530

    protocol/client,server: Lock self healing off by default.
    
    Also, merged the options client.grace-timeout and server.grace-timeout
    into one option "features.grace-timeout".
    
    Change-Id: Icb9f0809f89379de673f8c9f7ca4725bc113797f
    BUG: 812760
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3153
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 42c06ba048d0bcb7093063bf99dfa3e520a038a5
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Apr 13 15:22:57 2012 +0530

    glusterd/rebalance: Start process with xlator option client-pid -3
    
    This would prevent updation of xtime by the marker.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I11e287511026326271c2926e55993e48b32018f6
    BUG: 812287
    Reviewed-on: http://review.gluster.com/3144
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c75a5d348f0d30b61bdc45e9e54d623957a6050f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Apr 14 18:02:05 2012 +0530

    cluster/afr: increment change log with correct byte order
    
    Change-Id: Id2af3e61ad659ff6d168161673e5e1e19f36bdb5
    BUG: 765194
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3149
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 369873fbeac1c33bf5f2468e475c3a08608e8965
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Apr 16 13:31:59 2012 +0530

    cluster/dht: Revert to calling ftruncate
    
    Additionally, change lookup failure error to DEBUG level.
    
    Change-Id: I6eaf8e92a9cd34eba125a1e0e183bc3b6dc71945
    BUG: 812769
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3155
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit c6e226751efb4ce98e5c887b955c778b713b77bc
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Apr 13 14:19:11 2012 +0530

    nfs/server: hard resolve fh on restart
    
    the filehandle passed to hard resolving code was not initialized
    to it correct value (resovlefh).
    
    Change-Id: I0a26c7b90bf3efec7fda26fed0823755c4b9e87b
    BUG: 802779
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3150
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit dc4c44d51e3eb4b53e78840bf223911e48ce62b5
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 13 18:37:55 2012 +0530

    libglusterfs: Syncop procs should not exceed SYNCENV_PROC_MAX
    
    Change-Id: I0eb2adac06eae31939c8ed6b544b4be43d1a5885
    BUG: 810109
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3146
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 77645c35323c30f881ac5e5418c8723642f3845f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Apr 12 17:32:00 2012 -0400

    Fix dangling references to examples.
    
    Change-Id: Ic90f332fb6554173a03f7a026fc3677e7cf42eae
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3139
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 5c67b2c99de39c988be7c5fffd504fdbaae74a01
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Apr 11 13:40:28 2012 +0530

    glusterd: IPv4 auth improvment
    
    Check if last character of an IPv4 address is valid to prevent successful
    validation of addresses with '.' as last character.
    
    Change-Id: I0af6c288e12a47986ce3f8b02c317b99767e69e6
    BUG: 811458
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3124
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 362c5283ace6f048d0404a8a390faeb014ebe351
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Apr 12 12:39:48 2012 +0530

    server: Modified logging information to ease log based analysis
    
    Change-Id: I1bde6505346b5dda37cf88c66f9af8ff48668ed9
    BUG: 811864
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3133
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 28f373d89fba7266473c952d9c2bf6ec5f02628c
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 9 12:17:16 2012 +0530

    xlator/server,xlator/nfs : Fix authentication for address lists
    
    Fixes authentication problems when address lists are given for
    auth.{allow,reject} and nfs.rpc-auth-{allow,reject}.
    
    Change-Id: I9959ebfa6820aef52c883372e1085660560e1e73
    BUG: 810179
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3104
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b19a7fee17ddedfc6692deb5a8dc8df927a2cf7b
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Apr 12 15:32:05 2012 +0530

    dht/rebalance: Display migration failure count
    
    Change-Id: Ib2f8be2c98eae1b4df5d2090c1f1eec8ab264a35
    BUG: 811923
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3135
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bada6aeb2cabd12a11b0fe17bb01e9f2045b013d
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Apr 11 15:30:22 2012 +0530

    glusterd/remove-brick: Replace ABORT with STOP
    
    Remove-brick stop now invokes rebalance stop. This leads
    to a graceful stop of decommissioning.
    The volfile is also updated (removal of decommission)
    
    Change-Id: I5a8f725c0f54439b810ce32d988c21c02229c703
    BUG: 811513
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3126
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d80846bee0621f591a7b519743e4d91a620ccdca
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Apr 11 11:47:17 2012 +0530

    dht/rebalance: Handle ASSERT_ON_CHILD_DOWN gracefully
    
    In rebalance process, instead of terminating, send a stop
    event. The migration in question will either complete or
    be handled as error.
    Also, handle few syncop calls as errors, instead of just
    logging them.
    
    Change-Id: If6ed54474cb0f1fe0e28a5765e6d90966740dfde
    BUG: 811444
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3120
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c2ebd7aa84ed666ac8d1f0e9424cd01f877fb53b
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Apr 11 12:11:06 2012 +0530

    glusterd/remove-brick: Remove support for pause option
    
    Decommissioning through rebalance has no pause option.
    
    Change-Id: I90f165cdb2eccfaefc99365ae4b48d81320fb753
    BUG: 811459
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3123
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit c238e5073a8d60fede1f88e584c14de42885276e
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Apr 10 15:34:02 2012 +0200

    geo-rep / gsyncd: log sync failures as warnings
    
    Syncing of certain files can fail naturally if changes happen on
    master (eg. file gets deleted). Therefore logging an error is
    misleading.
    
    Change-Id: I7b54904e5ec7c85e4e0fa1e330123d2c44c78ac5
    BUG: 764510
    Reported-by: Vijaykumar Koppad <vkoppad@redhat.com>
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3113
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijaykumar <vkoppad@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit ecfe2d0a94dd6626e2e6c1e7707549adf550a5af
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Apr 9 17:20:10 2012 +0530

    glusterd/rebalance: re-establish conn between rebalance process
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: Ib13b4b9beebf18632027e4dd7c68f627c311781c
    BUG: 810688
    Reviewed-on: http://review.gluster.com/3110
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d2a73be6d94d108673e3427e534c1abbe71ccbff
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Sun Apr 1 14:50:08 2012 +0530

    mount.glusterfs: multiple fixes
    
    * noticed that the regex to parse the options were not fool proof.
      for example, 'ro' in a logfilename could have made the mount
      point read-only. Now fixed.
    
    * this issue existed for 'acl', 'worm' options.
    
    * log-server/log-server-port options were legacy, and no more
      needed in codebase.
    
    * refactored option processing in general to avoid above issues
    
    Change-Id: I172d24c86ece9a34420ba997fa385e304b4924ae
    BUG: 806978
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3058
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8a45a0e480f7e8c6ea1195f77ce3810d4817dc37
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Apr 3 15:37:25 2012 +0530

    glusterd: Added volume-id to 'op' dictionary
    
    Volume-id passed in op dictionary would help detect possible split brains
    among peers in a cluster. The idea is to check if the volume's id and
    the vol-id that was passed are equal.
    ie, same volume name, but different volume id indicate that glusterd
    'metadata' of one of the participating peers is stale or there is
    a split brain.
    
    This is over and above the existing checksum based validation of peer
    supplied cluster 'metadata' (ie, volume info file).
    
    Change-Id: I1049ef249e417e540ccb4243e450f92fcd0f46f9
    BUG: 797734
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3083
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b337b755325f75a6fcf65616eaf4467b70b8b245
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Apr 9 18:21:43 2012 +0530

    glusterd: Removed 'unprotected' concurrent access of priv->volumes on glusterd restart
    
    This must have been removed as part of
    afe542eca18888463798747d2a95e5a9d239a4a0 (reverting to non-synctask behaviour).
    
    Change-Id: Ic23c8bbf8f90f4c9af6e68349de63e22d7f25606
    BUG: 810829
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3109
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e46a57fda716c00b7c490be74485863c80d6f7b4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 8 11:40:48 2012 +0530

    features/quota: don't adjust statfs buffer if size used is already
    greater than available limit.
    
    members f_bfree and f_bavail of struct statfs are unsigned types.
    A negative value assigned to them is interpreted as some positive
    number and resulting in incorrect output of df output.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: I4d3d38b9bb6f675958ee38ad4d6c71ebcf4bb9a1
    BUG: 773530
    Reviewed-on: http://review.gluster.com/3102
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ea8378299e4d9ae5a8d296feb1d16950d07173de
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Apr 9 16:29:45 2012 +0530

    glusterd/rebalance: Provide option start rebalance with valgrind
    
    Change-Id: Ia7a836425f5dbfe07b2e46563e49aaeaaaaa4e14
    BUG: 810836
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3108
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 122da53bd1a82eaaf4aeb2ce6443fe8d0fe3ab46
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 11 16:14:31 2012 +0530

    cluster/afr: Perform gfid-less lookup in afr
    
    Change-Id: I78d9f0563e25047f392675ae32db38d2c94f6651
    BUG: 795355
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3129
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7edec07b139626bb64ea34e143a02dbfd28a6d9f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 11 16:14:16 2012 +0530

    storage/posix: Handle gfid-less lookup
    
    Change-Id: I4605dbb1dd8bf8e26de7f253e54a7f4840c8a8be
    BUG: 795355
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3128
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a3c61c6aea4045a6adafcc7350bd14f1e9c68ca1
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 12 22:03:49 2012 +0530

    libglusterfs: loc_copy should set name only if src->name is set
    
    Change-Id: If06d97dd1ff1293730e0cd4933f6ab3283f0475e
    BUG: 788051
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3137
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 918678dc8e5a8cac1ec2dea7f8d2b11a186f38eb
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Apr 12 15:46:37 2012 -0400

    md-cache: fix dict memory leak in mdc_inode_xatt_update
    
    We currently either dict_ref() or dict_copy() into mdc->xattr.
    The double dict_ref() call path is obvious. Alternatively,
    dict_copy() does not ref the dict in the situation where it
    creates a new dict, but we only call dict_copy() in this
    context when we already have a dict, which should mean the
    extra ref is unnecessary.
    
    BUG: 801582
    Change-Id: I72e3f1a16f942f04752c033812d13d50ee7c2c2c
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3138
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6a995ab3300a5ee0ee79a4d7d75281a79deec96e
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Thu Apr 5 10:29:18 2012 -0400

    contrib/md5: prune contrib/md5/* from tree
    
    Previous change set did not delete contrib/md5 from the tree.
    
    BUG: 807718
    Change-Id: I74eee1897fac24b83b379f2433de5e4648eb5f4c
    Signed-off-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3095
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f2921551424a97dcc3914cc79a241dca42675b97
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Apr 11 23:55:58 2012 +0530

    glusterfsd: mem-pool count of dict_t is adjusted
    
    increased dict_t pool count based on test results.
    
    Change-Id: Ia5b24940b79a1489b00cca2993241c32be94bbec
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 809034
    Reviewed-on: http://review.gluster.com/3131
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 472b55a6db996ca3058fec3aa6ab9a8745cbd5cb
Author: Anush Shetty <ashetty@redhat.com>
Date:   Wed Apr 11 11:49:46 2012 +0530

    Error-gen: declare the structure for cbks
    
    Change-Id: Iaa2e367ad225a2b24dd56c3941163f90be74e6ee
    BUG: 811445
    Signed-off-by: Anush Shetty <ashetty@redhat.com>
    Reviewed-on: http://review.gluster.com/3121
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 076830c068fb39bbc3e863c89a4253cbea36357e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Apr 9 23:11:52 2012 +0530

    doc: Move outdated documentation to legacy
    
    Change-Id: I0ceba9a993e8b1cdef4ff6a784bfd69c08107d88
    BUG: 811311
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3116
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit df8e2f53b70f4f49af70df308010dddfe5ca35ec
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Apr 11 16:07:43 2012 +0530

    dht/rebalance: Correct log messages
    
    Change-Id: Ica73707922c1bf1a0975a8057d39c1441b987b0a
    BUG: 808376
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3127
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dde9cfcaf3016968fade7591ddfc1c95851e9e59
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Apr 11 11:51:31 2012 +0530

    protocol/client: in link_cbk() try to print valid information in case of error
    
    currently there is a chance we don't have a source 'loc_t' path information
    instead we would have gfid. Need to print destination information too.
    
    Change-Id: I7a5edbdc9abe18fdb330fc7ed49c9946cf7fe382
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 810146
    Reviewed-on: http://review.gluster.com/3122
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 0bfadb56d0ce0ffaa410eccb2a9d9eaaf6f3ab7c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Apr 11 14:40:44 2012 +0530

    protocol/server: validate connection object before dereferencing
    
    in 'release()' and 'releasedir()' fops the check for 'connection object'
    was not done before dereferencing it. the check was in place for all
    other fops. handling the missing cases now.
    
    also removed some warnings related to 'set-but-unused'
    
    Change-Id: I47b95318e8f2f28233179be509ce090b2fb7276d
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 801411
    Reviewed-on: http://review.gluster.com/3125
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f56404a3358c799f907f36aecedf774b1875a56c
Author: Anand Avati <avati@redhat.com>
Date:   Fri Apr 6 11:17:34 2012 -0700

    fuse-bridge: generate GFID as gfid-req in fresh lookup
    
    This is necessary for self-heal to assign fresh GFID when
    performing lookup on files/dirs without GFID (migration from
    old version, etc.)
    
    Change-Id: I6f070255dc6e85bf6625b704cb5fb7f831ee58e6
    BUG: 795355
    Signed-off-by: Anand Avati <avati@redhat.com>
    Reviewed-on: http://review.gluster.com/3101
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit 7f5c1e5777d77570be0f9698de39d2f1905c509f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Apr 10 17:12:05 2012 -0400

    Fix compiler warnings and typos from Debian build.
    
    Mostly to do with "-Werror=format-security" being buggy, but while we're
    here we might as well fix some typos and such.  Credit goes to Patrick
    Matthäi <pmatthaei@debian.org> for pointing these out.
    
    Change-Id: Ia32d1111d7c10b1f213df85d86b17a1326248ffd
    BUG: 811387
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3117
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4bb82b2c779bb984a980e371c3119254cf1cb0f8
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon Apr 9 12:14:59 2012 +0530

    storage/posix: Avoid excessive logging in posix.
    
    When quota or gsyncd is enabled, the marker translator performs setxattr on
    files/directories. If the file/directory is deleted before setxattr, posix gets
    an error when it does setxattr and logs it. But its not an error for marker and
    it handles the case gracefully. Hence, avoid logging for these keys.
    
    Change-Id: Ic614777399497be92ed1c2b4718d46adfb639d96
    BUG: 765498
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3105
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 05a9780c9111396f4e2c3ebdae77cf8a257f1a54
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Apr 9 21:27:40 2012 +0530

    glusterd: Modified algo for creating hooks directories.
    
    - This change will ensure that hooks directories are created
    when glusterd is upgraded from a version that doesn't have
    the hooks feature or the 'current' hooks version.
    
    Change-Id: I8a0ea64eda52a15b1605b98588b9b19df209a73e
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3111
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 79b3e4111a1a64dc74046571845b3ed83b8ede24
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Apr 9 17:22:16 2012 +0530

    rebalance: revert sending PARENT_DOWN event to xlators
    
    reverting patch 1043dedfb54c80bdbb6e050920ced204515b226e
    
    Change-Id: I2e919c8a5e43f3cce74a8eaf58554830fa708364
    BUG: 808402
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3107
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1222e2ae2d42cf12569a0cf00bb1f1504ef4e7b7
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Apr 4 16:04:10 2012 +0530

    remove-brick: Abort should revert volume changes
    
    Also, enhanced gluster cli output.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I520ccfb63b3568a2e6654d8a5fbf265b9b903af1
    BUG: 788524
    Reviewed-on: http://review.gluster.com/3082
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7768d700a18f5bdb1e4640070ec5dd380384c7a9
Author: Venky Shankar <vshankar@redhat.com>
Date:   Mon Apr 2 12:47:55 2012 +0530

    hadoop-glusterfs: Fix IndexOutOfBounds Exception
    
    Fix IndexOutOfBounds Exception which is hit when one
    of the replica pair is down. Problematic code existed
    in assuming a uniform size for each replica in pathinfo
    string.
    
    Change-Id: I85377ba5549e0603fe86e8d787115004f50e0c6a
    BUG: 808009
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/3087
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f132cc666ba4aa5e804de1c4529674618ca0d875
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Apr 5 19:00:08 2012 +0530

    cluster/afr: Fix a compilation warning
    
    Change-Id: I36dc1b53fd4a7d824fe8506a4ad83ad652f95ce5
    BUG: 807718
    Reviewed-on: http://review.gluster.com/3094
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 8b892fff8be9adca22c180a62d1dd01d83559330
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 3 15:36:55 2012 +0530

    self-heald: succeed heal info always
    
    Succeeding the mgmt op enabled the rsp_dict to be used to get the
    reason for the failures.
    
    Change-Id: I781ded31afa5aafd717543a5339dee3f316aade8
    BUG: 807556
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3076
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6424f5a6cce467751fdfe991addc922a498d44fc
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 3 15:20:44 2012 +0530

    mgmt/glusterd: Use the correct status string for filtering
    
    Change-Id: Id62bec56aeda0cede19369708242f0b92f800125
    BUG: 807556
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3075
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3e27f277951e9369517bdd16170639f587d3fb9d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 3 11:13:09 2012 +0530

    self-heald: Add node-uuid option for determining brick position
    
    Change-Id: Ia60981da7473d74682d86286e4d540568c8de25b
    BUG: 807556
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3074
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 73e2c0dec5b432c788cd80c4210b887517188f3d
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Apr 4 03:42:31 2012 +0200

    geo-rep / gsyncd: shuffle directory entries in crawl
    
    In order to randomize the walk of the file tree.
    
    Change-Id: I9fc3b83d5804914a50faae8df7dbcfed2ba6f4b4
    BUG: 809675
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3079
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit bd83e10deec2e7dcd289ca30d2a3de19e0d59c30
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Apr 2 11:56:21 2012 +0530

    nfs/nlm: dummy actor for FREE_ALL procedure
    
    NLM4_FREE_ALL rpc procedure has been provided nlm's
    null procedure as actor to facilitate windows Nfs mounts.
    
    NOTE: windows Nfs needs several other NLM procedures to work.
    As a result, this patch only makes it possible to do a working
    mount of a volume with "nolock" option in windows.
    *Windows mount WITHOUT "nolock" option does NOT work as expected*
    
    Change-Id: Ie163982497871312c5bb15f8c141fef460cadc34
    BUG: 800287
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3063
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>

commit 7d62749f14663ea6c0000a4aab2c32041cbb4e75
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 3 08:12:34 2012 +0530

    self-heald: Find self-heal failures, split-brain
    
    Change-Id: Ib967f0fe0b537fe60e51d7d05462b58a7f16596e
    BUG: 806745
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3077
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1f3a0dd4742a2fcd3215aee4a5e22125d7ea4f4d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Apr 4 18:04:52 2012 +0530

    fuse-bridge/fd-migration: document migration failures in fdctx.
    
    Change-Id: Ib85871e586f89f88dd7bf738fbb284b5d7b70a86
    BUG: 809919
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3085
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 42a0889d93450e6f1f3472ec0818e678412346c2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Apr 1 15:48:26 2012 +0530

    cluster/afr: Handle self-heal of files with holes
    
    Change-Id: I6c04fe3022f234455d52620f42b9add80fc6abe4
    BUG: 765424
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3065
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 69f70038171862daedcbbccf0eaba3d1f8d885f5
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Tue Mar 27 11:14:23 2012 -0400

    Replace GPLV3 MD5 with OpenSSL MD5
    
    Ric asked me to look at replacing the GPL licensed MD5 code with
    something better, i.e. perhaps faster, and with a less restrictive
    license, etc. So I took a couple hour holiday from working on
    wrapping up the client_t and did this.
    
    OpenSSL (nee SSLeay) is released under the OpenSSL license, a BSD/MIT
    style license. OpenSSL (libcrypto.so) is used on Linux, OS X and *BSD,
    Open Solaris, etc. IOW it's universally available on the platforms we
    care about. It's written by Eric Young (eay), now at EMC/RSA, and I
    can say from experience that the OpenSSL implementation of MD5 (at least)
    is every bit as fast as RSA's proprietary implementation (primarily
    because the implementations are very, very similar.) The last time I
    surveyed MD5 implementations I found they're all pretty much the same
    speed.
    
    I changed the APIs (and ABIs) for the strong and weak checksums.
    Strictly speaking I didn't need to do that. They're only called on
    short strings of data, i.e. pathnames, so using int32_t and uint32_t
    is ostensibly okay. My change is arguably a better, more general API
    for this sort of thing. It's also what bit me when gerrit/jenkins
    validation failed due to glusterfs segv-ing. (I didn't pay close enough
    attention to the implementation of the weak checksum. But it forced me
    to learn what gerrit/jenkins are doing and going forward I can do better
    testing before submitting to gerrit.)
    
    Now resubmitting with a BZ
    
    Change-Id: I545fade1604e74fc68399894550229bd57a5e0df
    BUG: 807718
    Signed-off-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/3019
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3c5aed7d8226e50296c6a7106e0d59682732e9b5
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 3 15:22:45 2012 +0530

    locks, stripe: check if dict is NULL before refing it
    
    Change-Id: Ifab58504280ed92e4435f7805052745e56bef5ef
    BUG: 808003
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3073
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0e4c74861f762d4af7b7d8ffce5384920a6aa335
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Apr 3 13:17:28 2012 +0530

    quota: log msgs indicating NULL parent inode in DEBUG level.
    
    with name-less lookups its common to hit situations where parent
    inode is NULL.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: I980b14c3d4691e850ae15768f73cf1b7d867e930
    BUG: 809032
    Reviewed-on: http://review.gluster.com/3071
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e5b5bb4de46a2a37c8ff392c456c306026517269
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Apr 3 01:57:23 2012 +0200

    libglusterfs/run: POSIX compatible closing of child fds on non-Linux
    
    It just occurred to me that I realized there are POSIX features that let this be
    done cleanly. However, For Linux we keep the proc based approach to get more
    graceful strace logs.
    
    Change-Id: I6b473271b2adfd85cef6612eb65d88e5d00f5943
    BUG: 764294
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3068
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1043dedfb54c80bdbb6e050920ced204515b226e
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Apr 2 16:52:10 2012 +0530

    dht/rebalance: Send PARENT_DOWN event before cleanup in rebalance
    
    To prevent any crashes, due to backend ops (e.g: afr self heal),
    sending GF_EVENT_PARENT_DOWN before calling cleanup_and_exit.
    
    Change-Id: I58c87c114bf259a69a8d081d291ca908b30ec407
    BUG: 808402
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3062
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 943ca064ec6ab2f009f12b3d5f1e90a5402f04d6
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat Mar 31 00:15:02 2012 +0200

    libglusterfs/run: clean up properly also if program could not be spawned
    
    Change-Id: Ie81a6e1a99c1cb002653c0175bb3c5fcff9c8a4a
    BUG: 808427
    Reported-by: Krishnan Parthasarathi <kparthas@redhat.com>
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3055
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 22cc617902794f4136fe6ba7b631ebe9f7bd4563
Author: Csaba Henk <csaba@redhat.com>
Date:   Sat Mar 31 00:15:02 2012 +0200

    libglusterfs/run: test suite refinement
    
    If run is compiled as a standalone self-test program
    
    (-DRUN_STANDALONE -DRUN_DO_TESTS)
    
    add the possibility to pass an integer which makes
    the program sleep that many seconds before exit
    (0 forever).
    
    This makes it possible to investigate post-test
    state (eg. if there are leftover zombies).
    
    Change-Id: Ia8d80a74eb83615ad50db2e17bb2701dc0d69070
    BUG: 808427
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/3067
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit b283a09b05606b953339ea419d16cb1ec40326c3
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 2 11:08:24 2012 +0530

    cli: Limit value of bs * count in "volume top"
    
    The maximum value of bs * count is limited to 10GB. This prevents gluster from
    returning 0 throughput with large values of bs * count. If throughput for values
    larger than 10GB is required, use dd.
    
    Change-Id: Ia4ea70cb20f3f32b6cb81fd451ad56933f438452
    BUG: 803322
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3059
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7bcf48a73f6313a0cffbc37288041f1dc8bba71e
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Apr 2 18:32:05 2012 +0530

    cli/rebalance: Fix parse error for volume rebalance cmd
    
    gluster volume rebalance <vol> force was handled as a success.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I4f73aa5935c7e62673d457b52a6dfea6c7197dcc
    BUG: 808991
    Reviewed-on: http://review.gluster.com/3064
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit dcfd0f4ee8c3c405f768cbb79219c0c5fa071a56
Author: Brian Foster <bfoster@redhat.com>
Date:   Mon Apr 2 09:56:42 2012 -0400

    md-cache: fix time comparison to support 0 timeout
    
    The time comparison currently causes caching when the current
    time matches the timeout. This causes caching to occur even
    when the timeout parameter is set to 0. Fix the condition to
    support the no caching scenario. A longer term approach is to
    use gettimeofday() for more accurate granularity, but this
    apparently fixes a known bug.
    
    Change-Id: I6552c5961743edb22a1aec2e6a3a6e041d0647b2
    BUG: 809193
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/3066
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit b0bb1a2c979078efa3ab024e14119df6087c4320
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Mar 27 18:22:15 2012 +0530

    cli: do the proper STACK_DESTORY of created frames
    
    * fixes memory leaks
    * fixes some random local mem-pool empty messages
    
    Change-Id: Ic79f279f2acfe4722fa54d52397d0267b3918928
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 803638
    Reviewed-on: http://review.gluster.com/3018
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit dc2a52fa0d83ba2e807a175655fc0362b707a22d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Apr 2 14:57:20 2012 +0530

    nlm: print the reason of failure when clnt_create fails to create the client object
    
    Change-Id: Icc271e2166dbccc2cc12029e26c674fdb79fe975
    BUG: 808390
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3061
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e51f690d7c5eda400316ba97ab2f4ce448b51e7d
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Apr 2 13:00:47 2012 +0530

    glusterd: Include port in nfs status
    
    Change-Id: I679e491e801b694e8a0f93dd87cf540441dae927
    BUG: 806877
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3060
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0f3b55be4376c1c59131d999469d3b3c6aaddd87
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Mar 30 10:04:45 2012 +0530

    performance/quick-read: open shouldn't be worried about checking
    whether it is being done on a deleted dentry.
    
    lookup would've taken care of sending ENOENT, in case the entry
    was already deleted.
    
    Change-Id: I79c51e34ae3a202eb04123a2a58d0e819b6e94fa
    BUG: 808017
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3044
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 67450da471307d1c09bd21694a76fb12b2fcd405
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Mar 30 17:18:07 2012 +0530

    mgmt/glusterd: unregister NLM service from portmapper
    
    Native NLM v4 service is unregistered from portmapper
    when Nfs is stopped.
    
    Change-Id: Id74cf9a31f6b00450504a1271bb47617aa5ec1fc
    BUG: 786345
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/3052
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ca4d7c9dfc1d7f8c09994a862868f55b8320eb95
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Mar 27 12:50:59 2012 +0530

    performance/io-cache: Enhance state-dump output
    
    Along with weight, print uuid and path. If only the inode is
    cached, only weight, path and uuid will be printed.
    
    Change-Id: Ie7567832915319f26c6bab8a34576f6c43be7998
    BUG: 806900
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3014
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c2dd1510e18e4c91d54ce4de91ecd47b408524dd
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Mar 31 20:43:12 2012 +0530

    mgmt/glusterd: Improvements for volume heal CLI.
    
    1) Brought in a CLI improvement for volume heal cmd when it fails
    before initiating a transaction.
    
    2) Minor improvements in UI messages related to self-heal-daemon.
    
    Change-Id: I983c1e54b48f2efe8793fa5b00fa50df2067683b
    BUG: 807261
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/3057
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit 778c8d616ba2e9b47cafbbe95dbec7f2eb788302
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Mar 31 13:30:22 2012 +0530

    cluster/afr: Fix frame leak in hardlink self-heal
    
    Change-Id: I8560fc2ba0d989eeb33226f8eb8c7fbad46dfe32
    BUG: 765391
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3056
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 06226c19a2b6a8840c0fd88837164f1e2150ba5b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Fri Mar 30 15:42:21 2012 +0530

    glusterd: remove-brick validation behavior fix
    
    earlier one of the major validation case was missed if user provided
    a 'replica N' option for remove-brick where N is already existing
    replica count of the volume. This would have left the volume in
    inconsistent state, eventually crashing glusterd. Now fixed.
    
    Change-Id: I418f3bbb983d36aa51214c616a887e5a3ee98e74
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 803711
    Reviewed-on: http://review.gluster.com/3050
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 96e68adc348e96c1b9d70f6a621f607591f052c2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Mar 30 12:03:32 2012 +0530

    features/locks: INIT the list before insert_merge
    
    Change-Id: I1612565e2bbf1811a85341016b86571bdf6e5062
    BUG: 805994
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3047
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c078b9df8d8f44ca90e61566f83f83809ce5ac0f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 29 19:45:29 2012 +0530

    cluster/afr: Handle invalid inode in open_fd_fix
    
    Change-Id: Ie009fb4b8b7745ebd5b76f7a40287998be35eef3
    BUG: 804914
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3045
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 66d430da4e3788aeb41eea46455ca25a2d19a626
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Mar 26 16:11:29 2012 +0530

    glusterd: Added init scripts like interface for gluster commands
    
    Directories to hold the scripts mentioned above would be created for each
    gluster command under glusterd's 'working dir' as follows:
    (eg.)
    <glusterd-working-dir>/hooks/version/create/pre
    
    <glusterd-working-dir>/hooks/version/create/post
    
    where, version corresponds to the version of hook scripts.
    
    The scripts beginning with 'S' under the above directories would be run before
    (pre) and after (post) the volume created. The scripts would receive a command
    line argument as below:
    --volname=<volname>
    
    This can be optionally used  by the script.
    
    Change-Id: Ia81b4ff9dd4477d99dd59b39c805aa645521edb0
    BUG: 806996
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3010
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3f81c44a03e9ab78be2b4a69e3e36d41a4de324a
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Mar 29 14:00:50 2012 +0530

    glusterd: Used runner's RUN_PIPE to get inode size in xfs/ext3/ext4
    
    Change-Id: I8057fd04baf36db86fe679a1beb86f76a1085b7c
    BUG: 786367
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/3033
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit 73c789cd9c530ded113905ef7efb47e1ac3251d6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Mar 30 13:33:10 2012 +0530

    nlm: do not destroy the NULL client object
    
    Change-Id: Ie1946b33353a91a266d2b21727d0c8eaa06af7f9
    BUG: 808341
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3046
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6f10f48a6a1632cd62206fd84634ab0e5db1c361
Author: shylesh kumar <shylesh@gluster.com>
Date:   Wed Mar 28 14:13:00 2012 +0530

    cluster/stripe: minimum blk size log message
    
    Change-Id: I16ba2e17796cd91e89a6216d4981c09f1bcdc5cb
    BUG: 807637
    Signed-off-by: shylesh kumar <shylesh@gluster.com>
    Reviewed-on: http://review.gluster.com/3026
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cc2e9ad0751da55dfdcd86fea2d5b312a1cbd1b5
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 29 22:43:29 2012 +0530

    cluster/afr: Fix split-brain log
    
    Change-Id: Id6869fb83bb083809a2a69227e233458e0b9e0bf
    BUG: 787653
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3041
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 80d0c49125c67fcc0aab48cce7ef895dabf1d006
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 29 21:07:06 2012 +0530

    cluster/afr: Fix the split-brain log
    
    Change-Id: Ia4937dee009af7c945ec590a827c982b0e6ad307
    BUG: 787653
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3039
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 630e272a89fde08315b6159b83fcbbd6711a6046
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 29 13:02:32 2012 +0530

    glusterd: add-brick: give proper reason in few error cases
    
    had missed few 'else' cases, which were needed to send the right
    error message to the user regarding the reason for failure.
    
    Change-Id: I42d92782f4dec6f6bdffd42df254b7f38a715e36
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 772544
    Reviewed-on: http://review.gluster.com/3032
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 33bbab6ff9b34b1e623a53cc0c3483563f2aeace
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Mar 29 18:18:50 2012 +0530

    cli, glusterd : "volume status detail" fixes
    
    Use _PATH_MOUNTED, which refers to /etc/mtab, in
    glusterd_add_brick_mount_details(), instead of _PATH_MNTTAB, which refers to
    /etc/fstab.
    
    More changes to cli to show available information.
    
    Change-Id: I9da97c0fec14b3372f281efc0be37b2799bc2d0d
    BUG: 808044
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3037
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7cc52b98a54ef29844a302f2d4f129adcaefcbf3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Mar 28 00:14:29 2012 +0530

    cli: give warning to user in add-brick if stripe count given
    
    * as it is currently not so well tested, user should get notification
      about possibility of problems with the volume type changes.
    * added warning instead of removing the feature because with keeping
      an option we can enhance what is there already.
    
    Change-Id: I6cf3491870ac2e50e85c5dbe15c61622a47c18cb
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 787967
    Reviewed-on: http://review.gluster.com/3034
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit db501c73701b620be67b4c33ea16cac983dcd9b1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sun Mar 25 22:48:09 2012 +0530

    core: fix all the iobuf related refs and unrefs
    
    reviewed the code against all the possible places where
    iobuf/iobref ref unref are present, and hopefully fixed most of
    the issues around memory leaks with respect to iobuf
    
    Change-Id: I9aa30326962991f8e23acedd389a0e962e097885
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 797875
    Reviewed-on: http://review.gluster.com/2994
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2dea3b34755d9af1d1c1ffe517c6a087cf44512a
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 27 15:52:47 2012 +0530

    cli,glusterd: more volume status improvements
    
    The major changes are,
    * "volume status" now supports getting details of the self-heal daemon processes
    for replica volumes. A new cli options "shd", similar to "nfs", has been
    introduced for this. "detail", "fd" and "clients" status ops are not supported
    for self-heal daemons.
    * The default/normal ouput of "volume status" has been enhanced to contain
    information about nfs-server and self-heal daemon processes as well. Some tweaks
    have been done to the cli output to show appropriate output.
    
    Also, changes have been done to rebalance/remove-brick status, so that hostnames
    are displayed instead of uuids.
    
    Change-Id: I3972396dcf72d45e14837fa5f9c7d62410901df8
    BUG: 803676
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3016
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 735714edca08e2de16c0e447f8c3256913186ce6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Mar 29 16:31:24 2012 +0530

    features/locks: check whether dict is NULL before refing it
    
    Change-Id: I8906b80e584466aceb5a7402e3cee6ac2a552fab
    BUG: 808003
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/3036
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3fb9ee6caa3325423ac221b5f24e980c24edafde
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Mar 26 12:27:12 2012 -0400

    Save old volfiles in the RPM standard way.
    
    I just got bitten by this again.  It appears that the previously merged fix
    was inadvertently reverted by a subsequent change.
    
    Change-Id: I3a2067ee891fd5b8be0cd6cee58dcbc8cb6005e9
    BUG: 764702
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3009
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d1c8d296a23244a351bc2274e78c315b0870aeeb
Author: Kaushal M <kaushal@redhat.com>
Date:   Thu Mar 29 12:41:22 2012 +0530

    glusterd: Increase output_string size in glusterd_get_volopt_content
    
    The number of volume options with docs has increased, which causes the
    output_string to overflow and causes glusterd to crash. This change prevents
    glusterd from crashing.
    
    Change-Id: I79f8931f92ad55245aa547e7df15c9826537b615
    BUG: 807914
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3030
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9d884d7139e9c5b3edca2ecb89f7824ac207ad98
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Mar 29 15:17:14 2012 +0530

    cluster/dht: send dict with linkto key for lookup in rmdir_readdirp
    
    Without this, if there are any stale link files, rmdir fails with
    ENOEMPTY error.
    
    Change-Id: I7056b272122eb5540c22412856f46f638774c119
    BUG: 807246
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/3035
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 834408a49f204e8c256dad4b46d0f19053bf4b0e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 29 12:17:12 2012 +0530

    cluster/afr: handle fstat failure in data-self-heal
    
    The final fstat which makes the call_count 0 could be a failure.
    In that case the buf could either be NULL or buf is all zeros.
    If buf is NULL then it will crash, if it is all zeros
    buf->ia_type will be IA_INVAL and it proceeds to special file fix.
    sh->type is assigned with the ia_type of the file to be healed.
    I modified the code to depend on that instead.
    
    Change-Id: Icf7e19ff5908207128f2a1ee2963ad6b791c1ac5
    BUG: 804645
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/3031
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit fbfb4d48491b160436e6ac986057a8fe5e320502
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Mar 29 11:21:07 2012 +0530

    performance/quick-read: fix build errors.
    
    Change-Id: I8c4781bdd6c3cfd50cff95c31ecd6d653b916ac3
    BUG: 765363
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3028
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 864c9b612a5965a0934dcbdc51f84018d27c2c80
Author: M S Vishwanath Bhat <vishwanath@gluster.com>
Date:   Tue Mar 27 17:59:15 2012 +0530

    build-deploy-jar.py: Print usage message when hadoop home directory is missing.
    
    Change-Id: I0b55b33a36a4a5e4f1b71547629d20ae6b5eba5a
    BUG: 807155
    Signed-off-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-on: http://review.gluster.com/3017
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 3360fca3f3abf4dd6b1025063610f5c8c880a747
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Mar 28 16:18:17 2012 +0530

    cli, glusterd: "volume set help" additions
    
    "auth.allow/reject" and "server.statedump" options are included in "volume set
    help" now.
    
    Change-Id: I7f9ba89d1782c26792347ffd2cd4042c3c396934
    BUG: 783390
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/3025
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1f7692fecd1b5eaab60a01b64e9e4a67f0630804
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Jan 19 12:40:34 2012 +0530

    cluster/afr: Handle afr data self-heal failures gracefully
    
    Change-Id: I5f91098111a8ca29982f3b4292e2109e4a36cce1
    BUG: 765373
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2662
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 243f02a5ef77d69fa91c18092d5da8578bb8f042
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 27 01:20:21 2011 +0530

    performance/quick-read: make unlink aware of open-behind behaviour of quick-read.
    
    quick-read should do an open of all the fds that are waiting for to be
    opened behind before doing an unlink on a path.
    
    Change-Id: I4c8d65c0511e8a37765ff57e30d99dd89b56c4fc
    BUG: 765363
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/506
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bfb6366bd2a6de4cb5322dda72fbc1e6ad1edc41
Author: shylesh kumar <shylesh@gluster.com>
Date:   Wed Mar 28 10:50:06 2012 +0530

    cluster/stripe- do not ref if dict is null
    
    Change-Id: Ifa4a5253482d837e2583de078e908b8c442f9dca
    BUG: 807214
    Signed-off-by: shylesh kumar <shylesh@gluster.com>
    Reviewed-on: http://review.gluster.com/3024
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit b8c4da2ce0326d5c1a3303d4c3931e60b40e9bdc
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Mar 28 06:31:56 2012 +0530

    protocol/client: Set grace_timer_needed flag to false on a disconnect.
    
    A grace timer is registered on a disconnect, but a reconnect timer sends a
    connect request after every 3sec and if the server is down, the client protocol
    receives disconnect and a grace timer will be registered which on timeout will
    increase the lk-version value. Its enough to register the grace timer once after
    the first disconnect and later just ignore other psuedo disconnects until the
    next successful reconnect.
    
    Change-Id: I7f34a98a79fdc25370ef15a6712bfa316a9b7c7c
    BUG: 807271
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/3020
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit af0eb165f624c6a76e84e5a0c78881715ceae7c3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Mar 27 08:47:35 2012 +0530

    performance/write-behind: queue setattr fop with writes always.
    
    stat returned in setattr_cbk can be cached by the kernel. Hence it is
    always necessary that we return correct stat, which implies that setattr
    should not be out of order with respect to write fops.
    
    Change-Id: I305feeb4802f8a41ffaf032100832cbd65dfc5c1
    BUG: 765443
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3011
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c3c4ee24a64a2447f77788cb84559f1e07a21e04
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Feb 13 19:15:17 2012 +0530

    glusterd: Fixed replace-brick commit_force algo.
    
    - commit force subcommand of replace-brick (rb) should be allowed
      even if source brick is (irrecoverably) offline.
    - modified rb_timer to be active only for start subcommand. This is
      important since, the rb timer event relies on src_brick and dst_brick
      objects to be 'alive' when it 'happens'. In the case of
      abort/commit/commit force it is very likely that src_brick and/or
      dst_brick objects could have been destroyed.
    
    Change-Id: Ib8b8a4d690fbdd6f99b8aff306490eb59c54a437
    BUG: 772845
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2620
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3184ad0f88255fdec5a33b29790f677848c422e3
Author: Kaushal M <kaushal@gluster.com>
Date:   Tue Nov 15 18:26:44 2011 +0530

    cluster/dht : Acl fix for distribute directory selfheal
    
    Send acl xattrs, if present in the xattrs returned during lookup, during
    directory self-heal.
    
    Change-Id: I5337bbd3f3963aeed500a8a552e5f6713089b53e
    BUG: 764787
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/737
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 98b98d6cd7d94bfae5b4a7b54b04b59bf9381df9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 26 18:36:29 2012 +0530

    libglusterfs/fd: ref fds while copying the fdentries.
    
    Change-Id: I8973ec5d9858adfbdd6efc7cd596cf5d5af0e3cb
    BUG: 767862
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/3006
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 78e5e52c51ceb2255ac28ab86a91ed887d334cf6
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Mar 7 14:04:07 2012 +0530

    mgmt/glusterd: native sort of info files
    
    dependence on sort(1) has been removed,
    sorting of the files is now done using qsort(3).
    
    Change-Id: I90e162ba626506d01323ddfbfa594cf64b2e43c3
    BUG: 790337
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2990
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c1f8af00eaa03f1c2a7ea145ff627ca749e330cb
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Mar 23 13:13:09 2012 -0400

    Fix build problem with "trash" being semi-removed.
    
    With "trash" removed from xlators/features/Makefile.am but not from
    configure.ac, configure fails trying to create .../features/Makefile
    from .../features/Makefile.in which was itself never created.
    
    Change-Id: Idcba2c282c09821ae620e59748952e8d26117fdc
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/3003
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9d3af972f516b6ba38d2736ce2016e34a452d569
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Mar 20 17:22:24 2012 +0530

    core: adding extra data for fops
    
    with this change, the xlator APIs will have a dictionary as extra
    argument, which is passed between all the layers. This can be
    utilized for overloading in some of the operations.
    
    Change-Id: I58a8186b3ef647650280e63f3e5e9b9de7827b40
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 782265
    Reviewed-on: http://review.gluster.com/2960
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit afe542eca18888463798747d2a95e5a9d239a4a0
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 22 16:37:42 2012 +0530

    glusterd: bring back the 'non-synctask' behavior
    
    revert back to non synctask behavior
    
    Change-Id: Icfc9cbdeaf8dd6735df8366a6121c6598c56fade
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 805802
    Reviewed-on: http://review.gluster.com/3002
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit dc174a4d60ebca6a67e32c1834c2f0dcbff2c3c0
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 22 04:11:38 2012 -0700

    Revert "core: enable process to return the appropriate error code"
    
    This reverts commit 16717f4df7b0fbd3c255f5faf8a2744444231bb7
    
    Change-Id: I65624db4d31e11e1bec66b07b352ce823ef069b9
    Reviewed-on: http://review.gluster.com/3001
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2db6b286d091346b4386fd6091eb22bd9d3ea7a0
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 22 13:51:23 2012 +0530

    glusterd: fix bugs of syncop for operations
    
    * free the stack created for synctask
    * use different key than 'operation' in dictionary as thats being used
      already by other glusterd operations
    * send proper frame to 'rpc_clnt_submit()' API, as it gets used
      internally
    * also make sure to destroy the above frame in all _cbk()
    * move everything specific to synctask into one file, so it is easy to
      maintain
    
    Change-Id: Ia1a4414fffec6f9e51700295947eea4a2104a8c2
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 805802
    Reviewed-on: http://review.gluster.com/3000
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 1522ac5c15516156bb33f8d47b0c0e7de6cd411f
Author: Kaushal M <kaushal@redhat.com>
Date:   Tue Mar 20 18:05:18 2012 +0530

    cli: Display available information in "volume status detail"
    
    Display the available information in "volume status detail", without failing
    and erroring out if some information is missing.
    
    Change-Id: If8edc268fe91ca9c681f25135738a75eec43b8c3
    BUG: 765464
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2989
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f7842792de7661dd72c40fb950102e5dfcf0e487
Author: Rahul C S <rahulcs@redhat.com>
Date:   Wed Mar 21 12:15:52 2012 +0530

    Add space for heal vol req log message.
    
    Change-Id: Iadf1d6304bcae8f666f2435ffa2d71c50dd1395a
    BUG: 764658
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2991
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>

commit 11be645bb84ade2c5c9f42baec5ca6c6d1dc1d2c
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Mar 14 15:10:48 2012 +0530

    dict: add a dict_dump() function to dump the dictionary contents
    
    helps for debugging some functionalities where we have to understand
    what we send from one end point to another is properly received on
    the other endpoint without any errors.
    
    Change-Id: I9b802f12ae542e499161a1f3b9a5602f7b93b0ee
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 782265
    Reviewed-on: http://review.gluster.com/2959
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ebb5c6cc1e0d47513edb851128e424e747bb9166
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Mar 21 12:39:13 2012 +0530

    glusterd: Disabled self-heal on clear-locks internal mount
    
    - Also, changed afr_get_xattr_clrlk_cbk to use dict_set_dynstr for
      clear-lock summary. Earlier, it was relying on 'str' passed from
      xlators below.
    
    Change-Id: I175f4542e6ef2c859c4811eecb9d8c5a7d25a283
    BUG: 800779
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2992
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit abae8a2086e71aaf193b12df90ae3fe687117c28
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 13 15:23:39 2011 +0530

    core: enable process to return the appropriate error code
    
    Credit of this patch goes to Avati <avati@gluster.com> as I just did a
    rebase to the lastest master.
    
    Change-Id: I53b2adf90fd9808433bdc35b57dad0682bc90860
    BUG: 762935
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/579
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c3bdb1d4c6c4491afdf1ba26bb0d6204270cc058
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Dec 20 14:54:35 2011 +0530

    glusterd: bring in feature to use syncop for mgmt ops
    
    * new sycnop routines added to mgmt program
    * one should not use 'glusterd_op_begin()', instead can use the
      synctask framework, 'glusterd_op_begin_synctask()'
    * currently using for below operations:
      'volume start', 'volume rebalance', 'volume quota',
      'volume replace-brick' and 'volume add-brick'
    
    Change-Id: I0bee76d06790d5c5bb5db15d443b44af0e21f1c0
    BUG: 762935
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/479
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 8217148c97a474a9eab4a309589ceb8ff281f5c6
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Mar 21 21:57:37 2012 +0530

    features/locks: Avoid race in pl_inode_get
    
    Change-Id: I6c7b878fb43863137aac6552ee66f091534a6296
    BUG: 770080
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2998
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b1f1d57ca547cfa7644914bf7ff2d731b4a49134
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Mar 21 15:41:26 2012 +0530

    features/locks: Avoid race in creating domains
    
    Thread:1                 |       Thread:2
    -----------------------------------------
    1) Does inodelk on inode1| 1) Does inodelk on inode1
    2) It tries to get the   | 2) It tries to get the
    dom object for the volume| dom object for the volume
    volname-replicate-0. But | volname-replicate-0. But
    the domain list is empty.| the domain list is empty.
    3) Create the new domain |
    dom1 and add it to head  |
    of the list of domains.  |
    4) inodelk happens on    | 3) Create the new domain
    dom1 on range r1.        | dom2 and add it to head
                             | of the list of domains.
                             | 4) inodelk happens on dom2 on range r2
    5) unlock for r1 comes   | 5) Unlock on r2 succeeds.
    on inode1.               |
    6) It tries to get the   |
    domain, of the inodelk   |
    for volume               |
    volname-replicate-0, gets|
    dom2 but the lock on     |
    range r1 is not present  |
    so it fails.             |
    
    subsequent inode lock, unlocks will keep happening on the domain dom2.
    The stale lock present in the dom1 on range r1 will live on.
    It wont cause any hangs, but the statedump will always be scary.
    
    Change-Id: I9adc120d33febf685b30859cc307768c2fc63ae5
    BUG: 770080
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2993
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c40b9975d0bb3fdffdab281ad4f5e222d63d8674
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 21 10:58:03 2012 +0530

    protocol/client: memory leak fixes.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: I804c934d79ed13ded9d1b741cef6597bc238e476
    BUG: 803675
    Reviewed-on: http://review.gluster.com/2987
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b8e98e8d6fa1a783f9dac4eb17609f799fde4b2b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Mar 20 17:11:04 2012 +0530

    performance/read-ahead: destroy pages which survived from being flushed
    in flush_region because of frames waiting on them, after those frames
    are served.
    
    Change-Id: Ic8402f3da32058a1a11e62124b598b0ec3befeff
    BUG: 767948
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2982
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit dbae3d58d7dbfb404211866a17da1559cdde3387
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Mar 20 16:48:18 2012 +0530

    performance/io-cache: destroy the pages which survived in
    __ioc_page_destroy because of non NULL waitq in ioc_fault_cbk.
    
    Change-Id: I00b83f8bf0a654b3a3a23cf0b25657fbfda17804
    BUG: 767948
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2981
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e8f9aabb782d4e97b1c2a6df379128c3f3962401
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 20 16:00:41 2012 +0530

    protocol/server: remove the transport from the list irrespective of lock-heal is on/off
    
    Upon getting disconnect, remove the transport from the list of transports that
    protocol server maintains irrespective of whether lock-heal is on or off, since
    upon reconnect a new transport would be created.
    
    Change-Id: I18a269a93487d6e2cb11c345b6dde813d089809c
    BUG: 803815
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2980
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit a2291931d550cbbc19983bccb93dbf31a9993db4
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon Mar 19 12:05:09 2012 +0530

    features/marker: Replacing -1 with GF_CLIENT_PID_GSYNCD as part of code cleanup.
    
    Change-Id: Ia665060bff636b372904a726aba5249de9ade124
    BUG: 769494
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2971
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit c816d16288d3089d9e986c3155cb5ca9265b6210
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Mar 12 09:32:40 2012 -0400

    replicate: fix a glitch in up_count/down_count updates.
    
    Change-Id: I4919a98191bf7fe5edad9a149a129bcd177cd4a8
    BUG: 802522
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/2927
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2ffefd720a54fb815b1efa11e9de766fe1518831
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon Mar 19 21:26:56 2012 +0530

    protocol/client: Handle failures in lock self healing gracefully (part2).
    
    During reopening of fd's and reacquiring of locks on the fd (after a
    reconnect), a release on a fd on which reacquiring of locks is in progress
    will free up fdctx. This patch will keep fdctx valid until the reacquiring
    of locks is in progress.
    
    Change-Id: I0fae27544a7f8ddaa26def4ee4d41a8a2b322521
    BUG: 795386
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2819
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d98c3e19342be3b8b3e2c7e3d7e544de34143bdf
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 19 18:10:34 2012 +0530

    rpc-clnt: separate out connection_cleanup() from destroy()
    
    noticed that there are possibilities where one would like to do a
    connection_cleanup() before destroying a RPC connection itself, also
    current code is such that, rpc_clnt_connection_cleanup() does
    rpc_clnt_ref() and unref(), creating a race window/double unref
    possibilities in the code.
    
    by separating out the functions, this race window/double fault can be
    prevented.
    
    Change-Id: I7ebd3392efa891232857b6db9108b0b19e40fc12
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 802403
    Reviewed-on: http://review.gluster.com/2979
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 55c22fbfae259bff3b0e0cca192f709b74d8bee5
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon Mar 19 21:07:33 2012 +0530

    protocol/client: Handle failures in lock self healing gracefully (part 1).
    
    During reopening of fd's and reacquiring of locks on the fd (after a
    reconnect), a release on a fd on which reacquiring of locks is in progress
    will free up fdctx. This patch will keep fdctx valid until the reacquiring
    of locks is in progress.
    
    Change-Id: I0464c751a5aa986abac0b72b48b261fceeba24e8
    BUG: 795386
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2937
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 83277598bda524f44b76feed6adc7b19fc49d49a
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Mon Mar 19 19:56:21 2012 +0530

    protocol/server: Handle server send reply failure gracefully.
    
    Server send reply failure should not call server connection cleanup because
    if a reconnection happens with in the grace-timeout the connection object is
    reused. We must cleanup only on grace-timeout.
    
    Change-Id: I7d171a863382646ff392031c2b845fe4f0d3d5dc
    BUG: 803365
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2947
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f076c23f381d9013d4fa2145c329033a51194597
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Mar 19 18:02:57 2012 +0530

    protocol/client: Avoid STACK_DESTROYing more than once in RELEASE fops.
    
    Change-Id: I435327c6133aa6739731dabddde860b0b43c1497
    BUG: 804607
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2978
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit b315c42344f808bd9e2cba06bade0e5da58b0381
Author: Rahul C S <rahulcs@redhat.com>
Date:   Mon Mar 19 15:03:09 2012 +0530

    print bound_xl only once in server statedump
    
    since, currently there is only one bound_xl for
    all connection objects, it does not make sense
    to print the bound_xl for every conn object.
    
    Change-Id: Iaf4a170fe63fb7e80133c449a20f298f0e86364c
    BUG: 765495
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2975
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a77c4a7954df0f0e3d075895039e66eb4361562b
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Mar 19 15:13:14 2012 +0530

    features/quota : Fix timeout min value
    
    Change timeout min value to 0, so that default value of 0 successfully validates
    and mounts happen properly.
    
    Change-Id: I579c6192b97ffe2678fa95c912679b514fa7d8c0
    BUG: 804509
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2976
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 028936e2dc544158011eb32ad1629eeed75a42e9
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Mar 19 11:56:20 2012 +0530

    cluster/dht: Prevent crash in dir xattr selfheal
    
    Change-Id: I2ca4ab2f8e8611e7b2ac9ed2edc2e304727259dc
    BUG: 804280
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2970
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit def3dd7f37150657e1b41a2df8a563a93394a518
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 19 14:07:14 2012 +0530

    libglusterfs/call-stub: ref dict while storing it in readdirp stub
    
    Change-Id: I11224f7afa2e87dc242cc2e9e865c7ab2bb88c7e
    BUG: 765785
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2974
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 65c6e3706f5290947179922c9e3b8f05ea6ae91c
Author: Harshavardhana <fharshav@redhat.com>
Date:   Fri Jan 6 16:00:25 2012 -0800

    libglusterfs/dict: Add boundary conditions
    
    Functions modified:
    1. data_to_int16()
    2. data_to_uint16()
    
    Change-Id: I6775ca5d39f519c24ca3a07ce41018472e238cdf
    BUG: 769692
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/2599
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5f59fbd81830a5f2157b3206d8413ba862aa5253
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Mar 14 16:45:21 2012 +0530

    cluster/stripe: fix {set/get}xattr query for dirs/symlink
    
    This patch fixes the following problems:
    * ENOENT returned for getxattr (xtime) on symlinks
        Non-data entities are created only on the first subvolume but
        getxattr fop winds to all subvols. This results in all subvols
        except the first one to return ENOENT which is propogated down
        the stack.
    
    * ENODATA returned for getxattr (xtime) on directory
        setxattr calls always wind to the first stripe subvolume.
        xtime getxattr invocation winds to all subvolumes but the
        xattr is present in only the first one, resulting in all
        subvols except the first one to return ENODATA.
    
    Fix
    
      For symlinks getxattr now always winds to the first subvol and
      for directories setxattr sets the xattr on all subvols.
    
    NOTE
    
       For directories the all-subvol-wind in setxattr is done
       only when request is from a special client (client-pid == -1)
    
    Change-Id: I9236345ef319506770d2034b840ee4ac04704b21
    BUG: 801394
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/2948
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1477fe376ae51ae077430aea25aa6a7a34596768
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Mar 18 14:10:08 2012 +0530

    Logs: Improved logs in lock/unlock execution path
    
    Statedump will now start showing the lk-owner of the stack.
    
    Change-Id: I9f650ce9a8b528cd626c8bb595c1bd1050462c86
    BUG: 803209
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2968
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dfc481bf2dfe9a26d8c311de578ca82b347810d0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Mar 8 14:13:56 2012 +0530

    protocol/client: replace STACK_UNWIND_STRICT macro with CLIENT_STACK_UNWIND,
    which does appropraite cleanup before unwinding.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: Ic49d6e21c5fc56e747afec35be2bebbbbd2a6583
    BUG: 767359
    Reviewed-on: http://review.gluster.com/2897
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4d4a1e0801d1a7b2b3ec226309809c5fddd84319
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Mar 8 10:59:43 2012 +0530

    rpc: don't unwind the fop in caller if client_submit_request fails
    
    client_submit_request guarantees that the cbkfn - which we pass to
    it as argument - is called whenever there is a failure.
    
    Change-Id: I0e8ce5a6b320246dc13ce4318b04739d38d183a3
    BUG: 767359
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2896
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 968c6ba70cbcc058823947cc925072e03cbb0ac8
Author: M S Vishwanath Bhat <vishwanath@gluster.com>
Date:   Fri Mar 16 17:02:46 2012 +0530

    Using correct path to build and find jar file in build_deploy_jar.
    
    Change-Id: Ifeadd60370b36ab7b345c336a40a17091698ffe5
    BUG: 803879
    Signed-off-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-on: http://review.gluster.com/2955
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit e6753927338a12175f3a87fd4349d41847b8d2aa
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Mar 18 13:49:07 2012 +0530

    rpc: cancel reconnect timer in rpc_clnt_disable
    
    When the graph is considered no longer needed, rpc_clnt_disable
    is called, which disconnects the connection to server but the
    reconnect timer is not cancelled in that function, so it is
    reconnecting to the server before the grace-time-period.
    The locks of the disabled graph are still there on the server
    which are leading to hangs.
    
    Change-Id: I8d37f1296370e37117005137a0a430e636da4d2e
    BUG: 803209
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2967
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7fdd830431614231e0372faaff33359932b9631a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Mar 7 08:11:57 2012 +0530

    volgen: by default don't include performance xlators in nfs volfile
    
    Change-Id: I183ff00b0c0d23cec1123c320b7444eec0f71765
    BUG: 790333
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/2883
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 9fd44bd90ecb60760919bda85308132341f857f9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Mar 18 13:07:30 2012 +0530

    protocol/server: Clear internal locks on disconnect
    
    If there is a disconnect observed on the client when the
    inode/entry unlock is issued, but the reconnection to server
    happens with in the grace-time period the inode/entry lk will
    live and the unlock will never come from that client.
    The internal locks should be cleared on disconnect.
    
    Change-Id: Ib45b1035cfe3b1de381ef3b331c930011e7403be
    BUG: 803209
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2966
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f20d895a8ed2a3ee032bd0f85d5bfaf645575fd7
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 12 17:50:34 2012 +0530

    mgmt/glusterd: don't create the brick path in 'volume start'
    
    create the missing brick directory only on a
    'gluster volume start <VOLNAME> force' command
    
    Change-Id: Ica4fab9cefe953d73de9a30843d48f94e6ab735c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 801610
    Reviewed-on: http://review.gluster.com/2921
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6bf0a809c99ec33fee73e6ebebb58baa2614f977
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 6 14:35:45 2012 +0530

    protocol/server: send forget on the renamed inode
    
    If rename is given on a file "a" to "b" ("b" is already existing file),
    then after rename, the inode for "b" would still be in the inode table
    and would not get forget (for fuse client, the fuse kernel module would
    send, but on server forget will not come on that inode), thus leading
    to inode leak even when the mount point is empty.
    
    To avoid that before doing inode rename, unlink the previous inode that
    "b" is pointing to and send forget on that, if "b" is the last dentry
    for that inode.
    
    Change-Id: Ie4dcc39ea190ee8f28029b4d7661df576d9cf319
    BUG: 799833
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2874
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 93022c0cc6c22b3a30ded3e109a3fe0a0dce8ca0
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Mar 7 13:06:38 2012 +0530

    mgmt/glusterd : volume set validation fixes
    
    This is the new version of the patch by Kaushik at review.gluster.com/699
    
    The following new option types have been introduced:
     * GF_OPTION_TYPE_INTERNET_ADDRESS_LIST
     * GF_OPTION_TYPE_PRIORITY_LIST
     * GF_OPTION_TYPE_SIZE_LIST
    and option types of several options in translators have been updated to use the
    new types.
    
    valid_internet_address(), valid_ipv4_address() & valid_ipv6_address() functions
    has been updated for * wildcard matching. Previously used standalone wildcard
    address checking functions have been removed.
    
    Changes have been done to stripe translator to correctly set, update and use
    stripe-blocksize. Also minimum value for block-size has been set to 16KB.
    
    Change-Id: I2aa484ff695f6a915a8fc9a9f965cf0344f41d59
    BUG: 765248
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2899
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c3bbf6aa6c090fd066ab0079aa1c8ae332309d2a
Author: Louis Zuckerman <louiszuckerman@gmail.com>
Date:   Tue Feb 7 11:16:10 2012 -0500

    Updated the Ubuntu upstart jobs for glusterd in extras/Ubuntu.
    
    Using upstart jobs, instead of an initscript, solves Bug 765014.
    See also: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/876648
    
    The new upstart jobs split the work of starting glusterd & mounting glusterfs volumes into two parts: a glusterd service runner and a glusterfs volume moung blocker which waits for the service runner.
    
    This is the method preferred by Ubuntu developers to block a mounting event until a required service is available.  These changes will be included in the Ubuntu glusterfs-server package starting with release 12.04, Precise Pangolin.
    
    Tested on Ubuntu 12.04
    
    Change-Id: I9bb4e8cb05a1da0997c23f2ef7fea8737f6a2eb9
    BUG: 765014
    Signed-off-by: Louis Zuckerman <louiszuckerman@gmail.com>
    Reviewed-on: http://review.gluster.com/2727
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 598ab12c30b44c4c5f5922f3b76eec2ed8872790
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 14 16:13:17 2012 +0530

    mount/fuse-bridge: don't pass flags O_CREAT | O_EXCL during open as part of
    fd-migration during graph-switch
    
    Change-Id: Ia1494941d3e3d5bebdba3483b0ea7b32c9704b8c
    BUG: 802710
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2943
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 642343cc55e6ea2b0d463d77334c34790c30080f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Mar 16 16:09:42 2012 +0530

    Self-heald: Handle errors gracefully and show errors to users
    
    Change-Id: I5424ebfadb5b2773ee6f7370cc2867a555aa48dd
    BUG: 800352
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2962
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit f159e2247b58441449ad8da13ddf5cc5d3887b93
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Mar 16 22:10:02 2012 +0530

    cluster/afr: set_read_child when xactions in progress in fresh lookup
    
    Change-Id: I33e0268635ae7a1f247b0052994e027f990083da
    BUG: 800755
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2963
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 7cc412c7a2d2e4a6c7709b84bed75c10e5476244
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 15 16:04:10 2012 +0530

    mem-pool: more debug friendly logs by using gf_log_callingfn()
    
    Change-Id: I4d6e53ad8660314315f2ff3aa92ffbe707d6efe9
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 803638
    Reviewed-on: http://review.gluster.com/2951
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e3a3912f890a73a13020acba86394125bb501b95
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Mar 15 11:52:07 2012 +0530

    afr: Copy loc->gfid independent of lookup being fresh or otherwise
    
    This change ensures that entry self-heal following a lookup on that entry
    would have loc->gfid 'filled'.
    
    Change-Id: If723c71ca43e1f062dcb99cbe5488342514dace0
    BUG: 786087
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2950
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bf818f9a9e299475b09b85e28f3bca57f4a00624
Author: Rahul C S <rahulcs@redhat.com>
Date:   Sat Mar 17 18:32:04 2012 +0530

    Change option brick-with-valgrind to run-with-valgrind
    
    brick-with-valgrind does not make much sense because all the
    glusterfs/glusterfsd server processes are run with valgrind.
    So changing the option from brick-with-valgrind to
    run-with-valgrind.
    Also fix misspelt 'valgrnd' for valgrind log file namenames.
    
    Change-Id: I87aad6d65ffc37d8f8679be215709a9174385ecd
    BUG: 804293
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2965
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit a3c8c7be83a4be1cb3d89a187da05d9247cc4f07
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Mar 15 10:51:12 2012 +0530

    cli/remove-brick: Enhance remove-brick status to display
    
    Rebalance status now contains info from all nodes.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I6208c9879927fb6ddc0713c1480feadcf4f3fd75
    BUG: 797887
    Reviewed-on: http://review.gluster.com/2949
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 3823d7ee14fca54e513d45374e882c6de64fd2a7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Mar 16 09:11:58 2012 +0530

    protocol/server: memory leak fixes.
    
    Change-Id: I203832d9d52373f068f90e30dc7672329d65bbea
    BUG: 803675
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2954
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit ca15758018b4da68da40c34f240de75b44cb49e9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Feb 23 15:43:58 2012 +0530

    cluster/afr: Enable eager-lock
    
    Eager-lock is disabled by default.
    Use cluster.eager-lock on/off to change the config.
    write-behind on and eager-lock off is not supported configuration.
    
    In afr, when eager-lock is enabled the inode lock on fd is taken
    using the fd address as the lk-owner. So the lock is
    interchangableale between the inode-locks on the same fd.
    
    Change-Id: I7eef1ecd510f8028f5395dee882782da53c0de3f
    BUG: 802515
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2925
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit cba2f84cd084fdf005977690dce3c54fa9f8b133
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Mar 16 16:59:45 2012 +0530

    rpc-lib: memleak fix in rpcsvc_volume_allowed
    
    Change-Id: Iaa6baa4a3e036b2b5c808ea5e79017fffeb80a24
    BUG: 801754
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2956
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit fb406f942befbe48eec75043d89ecd0824f91dd6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Mar 16 16:25:07 2012 +0530

    protocol/server: add and remove the transports from the list, inside the lock
    
    Till now for graph changes, glusterfs client used to remember the old graph
    also. Hence the transport object on the server corresponding the old graph
    never received disconnect. But now since the graph cleanup is happening,
    transport on the server side gets disconnect for the cleaned up graph.
    
    Server maintains, all the transports in a list. But addition of the new
    transport to the list, or removal of the transport from the list is not
    happening within the lock. Thus if a thread is accessing a transport
    (in cases of statedump, where each transprt's information is dumped),
    and the server gets a disconnect on that transport, then it leads to
    segfault of the process.
    
    To avoid it do the list (of transports) manipulation inside the lock.
    
    Change-Id: I50e8389d5ec8f1c52b8d401ef8c8ddd262e82548
    BUG: 803815
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2958
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 178652106c5d731b24ddc9bb9bc1d8aae3952e2d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Mar 16 11:35:36 2012 +0530

    glusterfsd: Handle errors in response send
    
    Change-Id: I2d0a136fdfc4c86fb89cff5565efbf4af80e1edf
    BUG: 799265
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2961
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 6aab9d9602dc1ef62a2d1d63aa1764a062bf9d9f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Mar 3 17:28:17 2012 +0530

    protocol/server: Avoid race in add/del locker, connection_cleanup
    
    conn->ltable address keeps changing in
    server_connection_cleanup every time it is called.
    i.e. New ltable is created every time it is called.
    Here is the race that happened:
    ---------------------------------------------------
    thread-1                        | thread-2
    add_locker is called with       |
    conn->ltable. lets call the     |
    ltable address lt1              |
                                    | connection cleanup is called
                                    | and do_lock_table_cleanup is
                                    | triggered for lt1. locker
                                    | lists are splice_inited under
                                    | the lt1->lock
    lt1 adds the locker under       |
    lt1->lock (lets call this l1)   |
                                    | GF_FREE(lt1) happens in
                                    | do_lock_table_cleanup
    
    The locker l1 that is added just before lt1 is freed will never
    be cleared in the subsequent server_connection_cleanups as there
    does not exist a reference to the locker. The stale lock remains
    in the locks xlator even though the transport on which it was
    issued is destroyed.
    
    Change-Id: I0a02f16c703d1e7598b083aa1057cda9624eb3fe
    BUG: 787601
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2957
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 5e50175f56d05ab6c1295b0e0f0c11695e49c277
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 15 14:00:13 2012 +0530

    core: bring a cmdline option to set memory-accounting
    
    currently this is implemented as a command line option, and not
    as an easier translator option. this is because as of now, before
    even the volume files are parsed, we would need memory accounting
    enabled. there is scope for improving this behavior, but for now,
    this approach solves the problem.
    
    Also, this feature's major consumers are the testers who are
    looking for leaks, hence option is hidden from usage output.
    
    Change-Id: I09a5b13743ae43ff42c251989f921319e94cabe3
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 799199
    Reviewed-on: http://review.gluster.com/2856
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit eb8a9aae19755bc21afe2d8ed4893b788c4e84ff
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 1 17:25:12 2012 +0530

    core: dict allocations through mem-pool
    
    Change-Id: I7401639060957d437808779745a1e46c3f9f4585
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 798503
    Reviewed-on: http://review.gluster.com/2851
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d05708d7976a8340ae7647fd26f38f22f1863b6a
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Mar 14 15:35:51 2012 +0530

    dht: Rebalance status should display status from each process
    
    Change-Id: Id128417219bdb7146253618a5f8f31ef35013894
    BUG: 801322
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2942
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 212d739886cde04ca79f58915a84b6ed09eec00b
Author: krishna <ksriniva@redhat.com>
Date:   Tue Feb 28 13:28:31 2012 +0530

    remove code that was part of hard resolution which is not needed anymore.
    
    Change-Id: I9321745a40765eff048a656a7885f12847a0a318
    BUG: 781318
    Signed-off-by: krishna <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2830
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6826e046157a6ea1a07ba2a38a1825b05eb0b666
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Feb 27 05:41:17 2012 +0100

    glusterd/mountbroker: enhance mountbroker-geo-replication.* option to take multiple volumes
    
    Comma can be used in the value of a "mountbroker-geo-replication.*" option
    with semantics as of these examples:
    
      option mountbroker-geo-replication.foolabel vol1,vol2,vol3:geouser
    
    and
    
      option mountbroker-geo-replication.geouser vol1,vol2,vol3
    
    will allow geouser to mount any of the volumes vol{1,2,3} with params of a
    geo-rep aux mount under label foolabel, resp. geouser
    
    Also fix memleak in parsing of this option.
    
    Change-Id: I5311388812f503a078a52a14f2679f5ddb33b248
    BUG: 765214
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2818
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 48adf93423ba52f2a0e6d9d59060e6f2f1aa203c
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Mar 12 17:34:32 2012 +0530

    afr: Corrected getxattr 'key' matching in case of clrlk cmd
    
    - Added local->dict cleanup into afr_local_cleanup
    
    Change-Id: Ie1b96615735a9d2a2be1757cd016dbe225aae31c
    BUG: 800412
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2922
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bf65ae4fef113d78b7555db8520cd9f64817eda2
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Mar 14 18:28:09 2012 +0530

    glusterd: Fix brick op to prevent glusterd crashing
    
    Was building payload only for node types GD_NODE_BRICK & GD_NODE_NFS.
    Payload wasn't being built for nodes GD_NODE_SHD & GD_NODE_REBALANCE, which made
    glusterd crash when those operations were performed.
    
    Also fix a compile warning.
    
    Change-Id: Id33e21c84901d4d112c54514b7f16add31aeb950
    BUG: 803313
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2946
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 160ff641157359dc60d1a37652ef449b3c21ebad
Author: krishna <ksriniva@redhat.com>
Date:   Thu Mar 8 17:11:42 2012 +0530

    rpc: log in DEBUG when nfs clients try to see if ACL requests are accepted by nfs server
    
    Change-Id: I897b48a02ce2150d268a1a8b45163e9e1aee6cff
    BUG: 801338
    Signed-off-by: krishna <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2901
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 152bf376b51a896f65470a65d8e9410f19d8689b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Mar 13 16:58:04 2012 +0530

    rpm spec file: update the 'logrotate' config file during rpm install
    
    so there is no need for admin to worry about logrotate configs.
    
    Change-Id: Iec6def870d0c3550f2642ade023c03de52d6d530
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 801372
    Reviewed-on: http://review.gluster.com/2935
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit aa0f68aa8ec38808a83553abde8d8211047e7b4e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Mar 12 21:06:45 2012 +0530

    nfs: do not call inode_path on the newly created inode
    
    While resolving, for building the path into the loc, inode_find
    is called with gfid as argument to get the inode from the inode
    table. If the inode is not found, then a new inode is created.
    Then the path is build using inode_path. But if the inode is
    not linked to inode table (newly created inode), then gfid will
    be null and inode_path returns null gfid as the path. Suppose the
    lookup operation on that gfid fails, then we print the null gfid
    in the log message.
    
    To avoid it, build the path using the gfid only if inode_path
    fails.
    
    Change-Id: I2506fa8675761ddb0bc02980cd3583d9d068fc85
    BUG: 802424
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2930
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7bd561996d5a32071942b598739b130e020f89ee
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Mar 12 13:15:14 2012 +0530

    locks: Fixed incorrect list ptr manipulation in clearing entrylks
    
    Avoided unwinding blocked entry lock frames inside pl_inode->mutex.
    
    Change-Id: I424c4a1762c889c1a567c588d4ca383a6c338886
    BUG: 800412
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2878
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 84ef0ec98763c1ce92d0cc24d29d9953bb6bd3f1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Dec 14 16:01:20 2011 +0530

    performance/io-cache: cleanup the xlator private data completely in fini.
    
    Change-Id: Ib8859c57e89248ccaad94662f88944e79ec28d5a
    BUG: 767862
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/791
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1e5653165a97999288cbf40e670d6c84a31ad3f6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 5 15:15:04 2012 +0530

    fuse-bridge/graph-cleanup: don't provide a cbk for cleanup syncop task
    
    without a cbk, syntask_new returns only after the task is complete.
    Hence we don't have to wait on a conditional variable in the caller.
    
    Change-Id: Ie83894aa6fc02cc3a973930e67ae2b35de3b7647
    BUG: 767862
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2870
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a059bc30561a3046e255ba1e6ad54b09f0b03636
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Mar 8 01:26:29 2012 +0530

    cluster/afr: handle sending NULL dentry name for inode link in self-heal-daemon
    
    * Without the dentry name, dentry cannot be created in inode_link, which
     leads to trying to access the null dentry to check if it is cyclic and
     thus segfault. So send the parent inode also NULL, which just returns
     the proper inode after assigning the gfid and type to the inode without
     trying to create dentry.
    
    * Handle failures such as dentry_create returning NULL, in inode_link
      properly and return NULL in such cases.
    
    * Increase the lru limit of inode table of self-heal-daemon to 2048
    
    Change-Id: I7ae0e0e9be279d1694b6aafb5e054585e43f03ff
    BUG: 801149
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2893
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f9be1e7c665be0507e431cb42cd55032807bd3ea
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Dec 14 16:06:21 2011 +0530

    performance/read-ahead: cleanup xlator private data completely in fini.
    
    Change-Id: I3bb143036557d7d3844dc825f6870140e414f85a
    BUG: 767862
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/792
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7161d0995c937c1712d29a04356a11ca51e9ce07
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Dec 14 15:47:01 2011 +0530

    performance/quick-read: implement fini
    
    Change-Id: I92d4e7ded470b0e97b699656a890bab8c113bf4f
    BUG: 767862
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/790
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 29a3dc028d2847bd8421b23b7c7ee5419bd30392
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 12 12:53:01 2012 +0530

    mgmt/glusterd: provide an option to make a volume read-only
    
    this can be triggered by "gluster volume set <VOLNAME> read-only on",
    which adds read-only translator on server graph, thus making the
    volume read-only.
    
    Change-Id: Iee32e6b2f3022d16016534914a5198d1cd327e25
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 798877
    Reviewed-on: http://review.gluster.com/2915
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit eae8a469e7172380dd9c820405e7528a0ec33bad
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 14 10:14:18 2012 +0530

    performance/io-cache: store op_errno in page.
    
    This will enable us to pass appropriate op_errno indicating EOF even
    during cache-hits.
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    
    Change-Id: Ib239b5de9b8fca2bd8eb5ec87c93f2cb1c11a99c
    BUG: 795789
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2939
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c0b3ba9b3b65de88628a36cc51d2864ec72de0d0
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Mar 14 14:16:08 2012 +0530

    glusterd: Checked if peer is connected and 'handshaked' before sending updates
    
    Change-Id: Ia57378d5c81b263d6fcbc9d54ccc7fb138d83d8e
    BUG: 801731
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2941
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 404e8f27d3a9e950173e02151eccbb792615e535
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Mar 13 13:54:11 2012 +0530

    distribute-rebalance: fix the logic of ENOENT handling
    
    due to this, we were missing the entries from the last subvolume of
    distribute for all the rebalance or remove-brick operations
    
    Change-Id: I486f15c1d3d17cbf6f353f6179b2623af61f4868
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 770346
    Reviewed-on: http://review.gluster.com/2933
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 90333660ce4dd1fc94aa8f6b30c085d354f6693e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Mar 13 17:26:13 2012 +0530

    storage/posix: don't allow rmdir()/lookup() on HIDDEN_DIRECTORY
    
    so that we won't even have a GFID set on the GFID dir itself.
    
    Change-Id: I65be7d675a308f51f4c62a86499341412b20c47f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 802726
    Reviewed-on: http://review.gluster.com/2936
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 718a8ab91f6b9bd84da52c2029707f48e9fecaa4
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Mar 13 13:13:11 2012 +0530

    rpc-lib/rpcsvc: nfs auth corrections
    
    in comparing ip addresses during authentication,
    we need to take only the ip address of the client
    instead of the transport endpoint (ip:port).
    
    Change-Id: If48eca37edea1d69deb150720fbaea0ea2443a00
    BUG: 771845
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2929
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 91b4c34805f69c30c4730352eee873cee0dc17ee
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 12 18:07:09 2012 +0530

    nfs: no need to recalculate the 'ino' from gfid
    
    it is guaranteed to be sent properly from posix layer itself now
    
    Change-Id: Ifbbf558f3bcfa609bf107a75c692003ca261ac0a
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 800831
    Reviewed-on: http://review.gluster.com/2923
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit daa7cb945027e6564068310a9b857d0eb4ec1779
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Mar 14 12:15:05 2012 +0530

    glusterd: file perm change for glusterd.info
    
    this is need for the vdsm gluster plugin, changing
    glusterd.info file's permission to 644 from 600.
    
    Change-Id: I9de39f1b8b31a6c2f448e2ff6601eb270d042343
    BUG: 802217
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2940
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b61103d7ea35a2ea190465c836fe0d22f9f6f8c1
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Mar 9 09:38:36 2012 +0530

    core, cli : Changes to statedump
    
    This patch,
    * Enables missing inodectx, fdctx dumpops for cli statedump command.
    * Reintroduce changes introduced in statedump.c by 489a7a10 which were
      overwritten by db20a0f8.
    * Change strncasecmp() in gf_proc_dump_parse_set_option() to strcasecmp()
      to properly parse similar options like fd-fdctx, inode-inodectx
    
    Change-Id: I85ad854dce73048617b933d29cf360af9d0ed90a
    BUG: 797788
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2914
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 84da099ed321621928f11fe9cd164a4b0cfe1883
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 14 09:58:05 2012 +0530

    features/marker: Nameless lookup related fixes
    
    while filling a loc structure, marker should not error out if loc->name
    is NULL or loc->path is just a gfid.
    
    Change-Id: Ie3a9cffde2d17da0377f1e41de93b099a9133abe
    BUG: 801364
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2938
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit a476aba5b0368c3bc649db319ee748ae410144d9
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Feb 27 12:41:24 2012 +0530

    cli, glusterd, nfs: "volume status|profile|top" for nfs servers
    
    Enables usage of volume monitoring operations "volume status", "volume top" and
    "volume profile" for nfs servers. These operations can be performed on
    nfs-servers  by passing "nfs" as an option in cli. The output is similar to the
    normal brick outputs for these commands.
    
    The new syntaxes for the changed commands are as below,
     #gluster volume profile <VOLNAME> {start|info|stop} [nfs]
     #gluster volume top <VOLNAME> {[open|read|write|opendir|readdir [nfs]]
                   |[read-perf|write-perf [nfs|{bs <size> count <count>}]]}
                   [brick <brick>] [list-cnt <count>]
     #gluster volume status [all | <VOLNAME> [nfs|<BRICK>]]
              [detail|clients|mem|inode|fd|callpool]
    
    Change-Id: Ia6eb50c60aecacf9b413d3ea993f4cdd90ec0e07
    BUG: 795267
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2820
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit fcb5ebde1e84da871a7f43df9ecbce7d1d1de435
Author: Brian Foster <bfoster@redhat.com>
Date:   Thu Mar 8 16:11:58 2012 -0500

    system/posix-acl: fix reference counting in posix_acl_readdirp_cbk
    
    unref. the acl pointers from posix_acl_get()
    
    Change-Id: I1247f64ceded17bfa204d1b899ec56a27bef0cdb
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    BUG: 801183
    Reviewed-on: http://review.gluster.com/2904
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 61a550b77b776145d45025467f3fa6e9040bc2e0
Author: Brian Foster <bfoster@redhat.com>
Date:   Wed Mar 7 14:56:19 2012 -0500

    system/posix-acl: fix acl inode assignment in posix_acl_readdirp_cbk
    
    If an entry includes no ACL returned via dictionary, it is possible
    to skip down to acl_set without updating acl_access and/or
    acl_default. If either are set from the previous iteration, the
    unrelated ACLs are set to the current entry. Use a single set of
    pointers to ensure that valid ACLs are always set.
    
    Change-Id: Ia94887ded91845bc39d4d5e95ef00d190681e517
    BUG: 801183
    Signed-off-by: Brian Foster <bfoster@redhat.com>
    Reviewed-on: http://review.gluster.com/2903
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit fa5b0347193f8d1a4b917a2edb338423cb175e66
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Mar 10 00:54:12 2012 +0530

    protocol/server: Remove connection from conf->conns w.o. race
    
    1) Adding the connection to conf->conns used to
    happen in conf->mutex, but removing happened under conn->lock.
    Fixed that as below.
    When the connection object is created conn's ref, bind_ref count
    is set to '1'. For bind_ref ref/unref happens under conf->mutex
    whenever server_connection_get, put is called.
    When bind_ref goes to '0' connection object is removed from
    conf->conns under conf->mutex.  After it is removed from the list,
    conn_unref is called outside the conf->mutex.
    conn_ref/unref still happens under conn->lock.
    
    2) Fixed races in server_connection_cleaup in grace_timer_handler
    and server_setvolume.
    
    Change-Id: Ie7b63b10f658af909a11c3327066667f5b7bd114
    BUG: 801675
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2911
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4a37d78da3fef69f0074cab3ff71182a68876358
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Mar 13 16:48:58 2012 +0530

    glusterd: Updates on members of cluster must include peer to-be friended
    
    Updates about members of cluster must be sent to the peer to-be friended.
    
    Change-Id: I56745885d75af7c609227ba8582da1bb07c1b894
    BUG: 801731
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2934
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8c7549f9094d99d679de447230edaa5040db3e92
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Mar 5 19:04:49 2012 +0530

    cli: More xml output changes
    
    * Added xml output for "volume quota" which was missing.
    * Fixed xml output for "volume info all" so that it contains only one xml
      document
    * Fixed no xml output for normal "volume status"
    * Fixed normal output for "volume set"
    
    Change-Id: I3d85b6800e428226f2970d669e38e4331c99a218
    BUG: 799957
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2868
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6a8fcff3fb6955162dc4eeaeaa627bb31311627e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 12 14:22:01 2012 +0530

    features/quota: store quota context even for the cases where loc.name
    is NULL
    
    with name-less lookups, loc.name is NULL.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Change-Id: Ie3914924896c90a7fb7251cb0184c8e561ef7f4f
    BUG: 801364
    Reviewed-on: http://review.gluster.com/2917
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 2056df6f5e9ae7ccc6bb1b8f0b036f206b218999
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Mar 9 12:36:49 2012 +0530

    core: Made lkowner_unparse use 'type-safe' format-specifier
    
    Change-Id: Ibd39edb5fccef525f7f0929401f7329508c59ced
    BUG: 767229
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2907
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 05318789c5dbc92634a03e355acddbffb122b64e
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 12 18:28:31 2012 +0530

    glusterfsd: handle a case of NULL dereference during rebalance
    
    Change-Id: I9dbe1235f9b5eb7dd43c92bd46830ed9e5734768
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 801787
    Reviewed-on: http://review.gluster.com/2924
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 58776c0800ab146b1dd9a8461a98ca719afff6ef
Author: Amar Tumballi <amarts@redhat.com>
Date:   Sat Mar 10 19:59:07 2012 +0530

    iobuf: add a counter to keep track of request misses
    
    requests can be denied if the size of the request is higher than the
    available sizes.
    
    Change-Id: Id1bf2a56de799ccb94f3791899f2e33f68cd1e2b
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 802047
    Reviewed-on: http://review.gluster.com/2913
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 08cc17a5528d0194bdb835e05e3950d5516274c3
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 12 17:24:33 2012 +0530

    glusterd: minor log fix in handle probe query
    
    now prints the destination hostname instead of self.
    
    Change-Id: If73158c36780d597a67ec9185d99083764966c04
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 802265
    Reviewed-on: http://review.gluster.com/2920
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c8e7ec5e24613d8a20cd06d9e1b70e9386a889c4
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 12 13:00:45 2012 +0530

    protocol/client: remove unused variables from 'priv/conf'
    
    'last_sent', and 'last_recieved' variables were not used anymore
    after having RPC layer. Hence removed it from the code.
    
    Change-Id: I1ba74d47f909406ebde43476ccfed724e6c7e77f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 801721
    Reviewed-on: http://review.gluster.com/2916
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit afae9366d220d79fb8b0b1ab96f0e95d25dc4a90
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Feb 24 15:23:08 2012 +0530

    cluster/afr: save the xattr obtained in the {f}xattrop_cbk in local
    
    If the {f}xattrop operation succeeds on one of the subvolumes and fails
    on another (thus the xattr dict obtained from the failed subvolume in
    the callback will be NULL), then afr would be unwinding with op_ret = 0
    (since the operation was successful on one subvolume), but the xattr dict
    would be NULL (afr is not saving the xattr it has received in the callback
    in its local structure and will send the xattr it has received in the last
    callback). xlators above afr might segfault when they access the xattr since
    they would have assumed that xattr would be present as op_ret is 0.
    
    Change-Id: I50761a302150285f31dfdaa397f890c9370a989a
    BUG: 797119
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2813
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c9322f64cc4b8c661cf282bf1a2b08e0d6567b16
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Mar 12 14:26:36 2012 +0530

    glusterd: Peer(s) mustn't send updates about members not yet in cluster
    
    Also, peerinfo is added to peers list synchoronous with the request triggering
    it. This ensures that atmost one request sees that the peer (in question) is
    not in peers list.  Earlier, 'concurrent' handle_friend_update requests would
    see that a particular peer is not in the peers list yet, as the addition of the
    'peer' into the list happened asynchronously, on the 'connect' event of the
    'peer'.
    
    Change-Id: I6f017fb43079862fbe5ae7db8f9f4e4fefaa091d
    BUG: 801731
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2918
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e7d9f599ee52408819be649ef41ffc00c77e785e
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Feb 29 12:41:55 2012 +0530

    cluster/stripe: Readdirp - send aggregated block_size in stat
    
    Change-Id: Iee83a355ab767acac89b11d0a5add8527fc387a7
    BUG: 797308
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2833
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 152a0194e736e073d96fedd980b976cc1f1d4df8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Mar 10 17:22:55 2012 +0530

    Print non-zero timestamps in statedump
    
    Change-Id: I686842bc0934128b825828066f613c2a6280ceb9
    BUG: 801689
    Reviewed-on: http://review.gluster.com/2912
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7157a2cf42c4cf7c2ec2805e0732b49ebabd975e
Author: M S Vishwanath Bhat <vishwanath@gluster.com>
Date:   Sat Mar 10 15:51:22 2012 +0530

    posix_fill_readdir: Using strcmp to compare GF_HIDDEN_PATH with entry->d_name instead of strncmp.
    
    Change-Id: I29b6fc81213e52a697ed96559c3216c5512799ed
    BUG: 802005
    Signed-off-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-on: http://review.gluster.com/2910
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b596986ca43b2acd83debe3c77607cc4e8ff1dc6
Author: krishna <ksriniva@redhat.com>
Date:   Thu Mar 8 16:38:36 2012 +0530

    nfs/nlm: logging NFS client IP address when FH->volume mapping fails or when resolve_and_resume fails.
    
    Change-Id: Ia89113f46c1d7c9ed629e9dc0ff0779c41ed947f
    BUG: 765259
    Signed-off-by: krishna <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2900
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ef108d4fa77fd9aba48a7b9475c9b72352c16e6a
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Fri Mar 9 12:44:05 2012 +0530

    protocol/client: Register a timer(grace-timer) conditionally.
    
    A grace timer is registered on a disconnect, but a reconnect timer sends a
    connect request after every 3sec and if the server is down, the client protocol
    receives disconnect and a grace timer will be registered which on timeout will
    increase the lk-version value. Its enough to register the grace timer once after
    the disconnect and later just ignore other psuedo disconnects.
    
    Change-Id: I36a153aa86b350d87fe50d014ee0297f558a7fb6
    BUG: 795386
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2906
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 56ec59a465c4a4a34bac3a785964c2517570898b
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Feb 22 08:11:57 2012 +0530

    glusterfsd: fix some option definitions
    
    VOLUME_NAME used earlier in option definitions are confusing with
    glusterd specific volumes. It should be translator name in volume
    file.
    
    Change-Id: Id4d86c8def65aa6ff1346ef49f8b20ea428de615
    BUG: 788437
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/2789
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f75277b12af4c7e72c448480feec0d0e2e6582cd
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Mar 7 17:48:12 2012 +0530

    features/locks: Make inodelk ref-counted
    
    Ref when the object is allocated.
    Unref after the response is submitted to that inodelk.
    
    Ref when the lock is granted.
    Unref when the lock is unlocked.
    
    Change-Id: I2bfe9182b67bea7dc7b9d0ed9f99f1c7fa0b8a3c
    BUG: 783449
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2891
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7afa2747234778be3f2cffb860a8c48286dde566
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Mar 6 11:26:17 2012 +0530

    nfs/server: allow deletion of files by default
    
    this is needed for Micrsoft Windows-based Nfs clients
    which do not ignore ACCESS3_DELETE permission not being
    granted, while linux/unix systems ignore the same.
    behaviour on linux/unix systems remains unchanged
    
    Change-Id: I67f5f66a7486b93163aebedec5fbaa303173964e
    BUG: 790781
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2875
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3193c56b7e3d0be9713138784b1a6477136add9e
Author: krishna <ksriniva@redhat.com>
Date:   Fri Mar 9 09:43:18 2012 +0530

    nlm: support ipv4 only
    
    Change-Id: I0d8381b7d4da0e961677cca63d6d2c82836c1632
    BUG: 800735
    Signed-off-by: krishna <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2909
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 17111383828b44bf8f437aef76870c2c01fdd946
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Mar 9 10:05:48 2012 +0530

    cluster/dht: Replace ftruncate call with truncate in rebalance
    
    ftruncate call seems to be broken as of now (marker).
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: Ib49ced0471e1b8e9ee411eb5a9ff1b83c4d82bec
    BUG: 801658
    Reviewed-on: http://review.gluster.com/2905
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 5b290bc6e3df76bea04c11cb15643173c33455bd
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 8 22:17:46 2012 +0530

    syncop: Make syntask scalable
    
    At the moment, synctask uses task->frame to perform
    all the syncops, this will lead to high-memory usage if the task
    crawls millions of directories. i.e millions of STACK_WINDS/UNWINDS.
    To prevent this, in each task a new stack is created to perform
    the fops which is reset after every syncop.
    
    Change-Id: I53c262ec348be9b1d91af73da01f1c217f31ce6e
    BUG: 798907
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2850
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit bc10ade1cff9d6cd3b3528ec6c845efadc722481
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 7 21:02:16 2012 +0530

    performance/io-cache: pass appropriate op_errno even during successful
    reads.
    
    An op_errno equal to ENOENT with op_ret equal to zero is used by
    storage/posix xlator to indicate EOF. NFS relies on this protocol
    for correct functioning.
    
    Change-Id: I136fbf429a829bd7bd75ce8ce236f9557a418a5d
    BUG: 795789
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2894
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 204ab142977163f634cbf4ec92be58754225504a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Mar 8 07:45:15 2012 +0530

    performance/io-cache: move mem-pool initialisation to init.
    
    mem-pool is global structure which is stored in ioc-inode-table and hence
    can be initialised in init.
    
    Change-Id: I4bc88fe3e8c729312e41f62c98f665af5fb26a62
    BUG: 765340
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2895
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9ae2f79879b295639b55411c5339eba04e627345
Author: Venky Shankar <vshankar@redhat.com>
Date:   Thu Mar 8 14:51:02 2012 +0530

    xlator/lib: fix spurious STACK_UNWIND
    
    Change-Id: If37eba97710fc79713f70c4117015d49f93ad137
    BUG: 801285
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/2898
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5fdd65f5f4f5df1d28b0fb4f7efed226d5db1b3c
Author: M S Vishwanath Bhat <vishwanath@gluster.com>
Date:   Fri Feb 24 13:18:56 2012 +0530

    renaming hdfs -> glusterfs-hadoop
    
    Change-Id: Ibb937af1231f6bbed9a2d4eaeabc6e9d4000887f
    BUG: 797064
    Signed-off-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-on: http://review.gluster.com/2811
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e1ab347720f25ed2e7db633a7202f7b873f4b90a
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Mar 7 05:29:41 2012 +0100

    cleanup and fix xattr namespace flip
    
    - function of actual flipping made static
    - clean out references to particular namespaces from flipping logic
    - namespaces involved in flipping defined at single location
    - fix fnmatch(3) invocation with reversed pattern and string arguments
    - instead of "user", use "system" to flip from, because latter is
      free from supervision of the VFS layer (cf. attr(5))
    
    Change-Id: I3cc5836fadcad5b237fd5c67d0dcaea63aee9164
    BUG: 798716
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2890
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 33e9f9da8546dc57ecf6b3705f6b6474150ec78c
Author: shishirng <shishirng@gluster.com>
Date:   Tue Mar 6 18:55:37 2012 +0530

    glusterd/rebalance: Bring in support for parallel rebalance
    
    This patch, enables rebalance processes to be started on all
    nodes where the volume is spread across (1 process per node)
    
    node-uuid xattr identifies which node takes ownership of the
    task to migrate the file. The model employed is push (src pushes
    to dst)
    
    Change-Id: Ieacd46a6216cf6ded841bbaebd10cfaea51c16d6
    BUG: 763844
    Signed-off-by: shishirng <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2873
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f6a779ffc5b515163995dc2d240c3271cc6bceeb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 7 17:34:37 2012 +0530

    features/marker: GFID file handle based backend related fixes
    
    * make sure loc->gfid is filled.
    
    Change-Id: I5304e650d9fc181ee1f3b65be7f2ff3847d9722e
    BUG: 790389
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/2888
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 57a51c734408e9439640d215795f7d2188f2383b
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Sun Mar 4 00:01:17 2012 +0530

    glusterd: Append internal mount logs of clear-locks command to a single file
    
    To ensure logs of all clear-locks commands executed from a
    'peer' (glusterd) are in one place.
    
    Change-Id: I9f531a1e24d4502769740010da73b3d4adb5c5c9
    BUG: 799267
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2861
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit fe7d9a874d50fe51e26f6ac9293026534b8f22a1
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Mar 7 15:13:04 2012 +0530

    cluster/distribute: fix log level of few messages
    
    Change-Id: Ibdeeb705e75a94bb96a1ae259be32ddd2ca5fec8
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 797715
    Reviewed-on: http://review.gluster.com/2885
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8e29fe73b96f1feb3cc4093eb2e71c7c92be4a31
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Mar 7 23:45:47 2012 +0530

    libglusterfs/fd: fixed fd_anonymous() leak
    
    fd was getting leaked whenever there was a overlapping operations,
    which caused memory leak, and process fd leaks, which made most of
    the operations on NFS mount of a replicate volume not work. With
    the fix, things are back to normal.
    
    Change-Id: I2d2158b2972ba5dae270d6ff7b1a827403653c04
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 787368
    Reviewed-on: http://review.gluster.com/2892
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 63281d7eeb5b8ac44e3630ccfbc61774eedf2ae2
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Mar 7 00:19:29 2012 +0530

    protocol/client: Added lk_ctx info in fdctx dump
    
    - Added a brief explanation as to why we can't use gf_log
      when in statedump.
    
    - Removed gf_log messages from client_priv_dump since
      it can cause a 'deadlock' - See statedump.c for explanation
    
    - Added try-lock based accessors for fd_lk_list for dump purposes.
    
    Change-Id: I1d755a4ef2c568acf22fb8c4ab0a33a4f5fd07b4
    BUG: 789858
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2882
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ac568d561ba15a148d8de6a3d4431714bce230f6
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 5 23:54:51 2012 +0530

    cluster/distribute: send proper 'dict' in readdirp()
    
    if we do the STACK_WIND from readdirp_cbk(), we were not sending
    the right dictionary which made our linkfile determination a
    failure.
    
    Change-Id: Ie3f26748608f1a81123fe475d8a42bf2717475c3
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 799887
    Reviewed-on: http://review.gluster.com/2869
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit ebbc6e802bbffc9c0fd03db1cafefcaaca3a0f05
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Mar 7 16:03:32 2012 +0530

    protocol/client: Free readdirp xdr leak
    
    Change-Id: I5e46deedd93e852a483693de42e4bec0082bc08b
    BUG: 796186
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2886
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 1e22ab9d218405f5081a30e90c4541e43243a216
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Mar 7 14:16:07 2012 +0530

    nfs: fcntl lock self healing.
    
    Change-Id: Ic3e00e8ea3b873acbc3abb5155aecdaac848a3e5
    BUG: 795386
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2884
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>

commit 0d99aa113d42d96b35e5bc477349b28ef161c4af
Author: krishna <ksriniva@redhat.com>
Date:   Tue Mar 6 15:52:34 2012 +0530

    nlm: call nlm4_cancel_fd_resume instead of nlm4_unlock_fd_resume when CANCEL proc is called.
    
    Change-Id: Id4c74165f24cccb46ca5de406dd7e47e4a8b99e1
    BUG: 798222
    Signed-off-by: krishna <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2877
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 293aa0b9a08da1c4703ddd992a2e03d53ec84cc5
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Mar 7 00:30:17 2012 +0530

    xlator/lib: Drain out sent requests to avoid multiple STACK_UNWINDs
    
    Change-Id: If28e4b6e157ac0cb9e1f325bbba39f6c3f1c2b45
    BUG: 789078
    Reviewed-on: http://review.gluster.com/2881
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 228d01916c57d5a5716e1097e39e7aa06f31f3e4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Mar 5 16:05:12 2012 +0530

    glusterfsd: Don't reconfigure if process does not know volfile server
    
    Change-Id: I09e5527bb1496e0029d73f08dd7892d74df93084
    BUG: 799882
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2865
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e435faeae8bdedbfcdeae6a37e51b913b7c7ff00
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Mar 2 13:26:36 2012 +0530

    cluster/afr: handle node failures in lookup
    
    When a transaction is in progress lookup depends on inode ctx
    for read-child. If the lookup fails on the read-child while
    another transaction is in progress, it should select the
    read-child as the next success_child which is in fresh_children.
    
    Change-Id: I33a04b102966b63a64bacf8d2e29f0d0119fdac6
    BUG: 773225
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2858
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 347b4d48cba3cc1e00d40ec50e62497d65a27c84
Author: Rahul C S <rahulcs@redhat.com>
Date:   Thu Feb 23 16:51:59 2012 +0530

    cli: Fix volume statedump cli output typo
    
    Change-Id: I1363123d13fa4364e917344fdd928ac48b85326c
    BUG: 796617
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2807
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b7dc6b4df748d890d6b76c613f4911c4bd5947eb
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Feb 27 16:08:56 2012 +0530

    glusterd: Rename nodes in "volume set help-xml" output
    
    Change-Id: I44bbfb6e78a459783d7d5bbccda6bbbd3ec1e391
    BUG: 791054
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2823
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0783ca994d9ea95fd9ab3dd95d6407918f19f255
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 1 12:34:56 2012 +0530

    cluster/afr: Reset re-usable sh args in sh_*_done
    
    The bug is observed due to stale value of active_sink count
    set in metadata self-heal.
    
    Change-Id: I41996999213c323c0f4d4db575d87b2d0b4b3fec
    BUG: 798874
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2849
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5d813bb5fa005d15de47ba0cde0af7bda6bd9995
Author: Amar Tumballi <amarts@redhat.com>
Date:   Mon Mar 5 14:17:57 2012 +0530

    rpc-clnt: print xid of the saved frames getting unwind
    
    so that one can match the corresponding submit failed errors in
    brick logs
    
    Change-Id: I4422805a20c251aeffb51d63572c251176b2620c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 799337
    Reviewed-on: http://review.gluster.com/2864
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6756245b1514374712136c8dc1f4ac2a19a6da21
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Feb 29 15:16:53 2012 +0530

    fops/removexattr: prevent users from removing glusterfs xattrs
    
    * Each xlator prevents the user from removing xlator-specific
      xattrs like trusted.gfid by handling it in respective removexattr
      functions.
    
    * For xlators which did not define remove and fremovexattr,
      the functions have been implemented with appropriate checks.
    
    xlator         |     fops-added
    _______________|__________________________
                   |
    1. stripe      |     removexattr and fremovexattr
    2. quota       |     removexattr and fremovexattr
    
    Change-Id: I98e22109717978134378bc75b2eca83fefb2abba
    BUG: 783525
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2836
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 33b9f156e6b6137e33bd9becfe640166986ecc55
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Feb 29 10:20:54 2012 +0100

    glusterd: mountbroker-geo-replication.* fix
    
    mountbroker-geo-replication.* option's value was always
    discarded due to bogus control flow
    
    Change-Id: I5ec57dd0db9502ba088c42e07e32ac3e15317ce5
    BUG: 797702
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2835
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit 5b9d47a3a39fac39e3fbccd4083f2f45c9ce5b49
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Feb 29 10:21:03 2012 +0100

    geo-rep / syncdaemon: determine suitable xattr namespace based on privilege
    
    Change-Id: I91fe16d7e5e4c21f138eab4ee0b9334aec40e41b
    BUG: 765433
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2838
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar@redhat.com>

commit eb3bab1c6d391131cdff48a458fbfec2f53d7c6c
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Mar 4 23:45:26 2012 +0530

    glusterfsd: Unref iobuf after using it
    
    Change-Id: Ieefc08d9af2125fabc2a86e5ff3a933aec539da0
    BUG: 799882
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2866
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7fec9b41d8e1befa8d58a76d98207debddd60b65
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Mar 3 00:01:23 2012 -0800

    Revert "afr: [Un]Set the 'right' lkowner for [f]{inode|entry}_lk and the 'enclosed' fop."
    
    This reverts commit 2e80fdbeb6abbb23ff6789c2b98c82704883af0a.
    
    Change-Id: I417fd43e4195d63e5b8b83dd3beb712887130e1e
    Reviewed-on: http://review.gluster.com/2860
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit aaac9cf176b407f89a1e8015140916b3f9d3cddb
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Mar 1 00:17:21 2012 +0530

    Refactor xlator/lib for better readability & maintainability.
    
    Change-Id: I6468462ae2bbc05c1dd6c2aea66b440aa7cfdd09
    BUG: 789078
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2845
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f822d76d5a247ea6ba7375a35cb72b63fa413005
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Mar 2 15:34:51 2012 +0530

    cluster/afr: copy the parent's gfid from child loc while building parent loc
    
    Suppose the process is not a fuse or nfs mounted client, and some other process
    such as rebalance, then after lookups inode would not be linked to the inode
    table (since the inode was created for rebalance purpose only), thus keeping
    inode's gfid NULL.
    
    And afr while building the parent loc using child loc, does not copy the
    pargfid present in child'd loc structure. protocol/client will search for
    the gfid either in loc or in loc->inode and assert if it cannot find the
    gfid in either of them.
    
    Change-Id: I882e449fb8b79d5c69e4a942abcd844dc4d5d30c
    BUG: 799262
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2857
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit 71cffc0b66b849306778515d385083b9f78857f5
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Mar 2 00:54:12 2012 +0530

    Fix memory leaks found in readdir
    
    Change-Id: I0e221e4de9ee12586b09cd8bf7f394e9d4b88a11
    BUG: 765785
    Reviewed-on: http://review.gluster.com/2853
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0d62b3e4cd9de73b0cb7e54f904eefe27581cf4d
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Thu Mar 1 22:34:59 2012 +0530

    protocol/client: Calling GF_FREE on memory allocated via GF_CALLOC.
    
    This is a temporary fix. A clean fix would be to allocate memory using mem_get0
    and free via mem_put.
    
    Change-Id: I6351ab22c2f05ba8fa4aaad67f375027df873807
    BUG: 796656
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2852
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 316e694d53f20a76ee36654a9a865a493800dc3c
Author: Csaba Henk <csaba@redhat.com>
Date:   Wed Feb 29 10:21:09 2012 +0100

    geo-rep / syncdaemon: make the timeout for establishing the connection to slave configurable
    
    It can be set through the connection-timeout tunable but we keep it hidden,
    intended as a workaround for some special scenarios not for general use.
    
    Change-Id: I31f9fa3873afa7babc2106ee34484123a01bdc57
    BUG: 789078
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2839
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 326a7d04260c15f1b6e201621438844f8747b963
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 21 22:06:29 2012 +0530

    cluster/afr: Add new option to know which process it is in
    
    Afr xl needs to maintain inode-table inside the xl if it is in
    self-heal-daemon. The code was depending on the option
    self-heal-daemon to do this. This is wrong as the option can be
    reconfigured to on/off. Added a new option which can't be
    reconfigured for this purpose.
    
    Change-Id: Idc42c403c4bd9b73d1f328427ae4158ff1420b3a
    BUG: 795741
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2787
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 86f631f4283cba7185e5b1d5a3be4b9a614ed985
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Feb 23 14:46:04 2012 +0530

    protocol/server: Make conn object ref-counted
    
    Change-Id: I992a7f8a75edfe7d75afaa1abe0ad45e8f351c8b
    BUG: 796581
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2806
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f93045296870cb6938d9b4356a4f3198cbebe3ba
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Feb 29 19:25:30 2012 +0530

    hdfs/plugin: Fix regex for parsing pathinfo string
    
    Change-Id: I3a5d78f39a15c8029cd40225013e9ac40beb9373
    BUG: 797116
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/2844
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0978b5a36d379839ff543fd54612fde476deede7
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Feb 27 11:15:51 2012 +0530

    cluster/afr: Handle errors in build_parent_loc
    
    BUG: 787671
    Change-Id: I0b01b0f9e14a26d757748413dd71909e915c7573
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2826
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bcfd365c10d20bde920a3c6cdd1f95b7da5ffe84
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Feb 14 21:27:10 2012 +0530

    afr: [Un]Set the 'right' lkowner for [f]{inode|entry}_lk and the 'enclosed' fop.
    
    afr 'mangles' the lkowner inorder to ensure [f]inodelk/[f]entrylk fops from the
    same application contend. But other fops that are 'visible' to the application
    should operate with the lkowner provided by fuse for correct functioning of
    posix-locks xlator.
    
    Change-Id: I7e71f35ae7df2a070f1f46d4fc77eed26a717673
    BUG: 790743
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2752
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1936e29c3ac3d6466d391545d761ad8e60ae2e03
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Feb 29 16:31:18 2012 +0530

    cluster/afr: Hardlink Self-heal
    
    Change-Id: Iea0b38011edbc7fc9d75a95d1775139a5234e514
    BUG: 765391
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2841
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6e9a8f61b7d7371fa749c168162c716c2b0be70b
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Mar 1 12:18:48 2012 +0530

    glusterd: Changed clear-locks cmd to use trusted-volfile for its internal mount
    
    Change-Id: Iba8add1802832d4fa7082bc6a68eee966ddc508b
    BUG: 798127
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2846
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 8747925fb0847364be98afc2c2d59b42b2f8514c
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Mar 1 12:20:08 2012 +0530

    cluster/rebalance: Fix expression in check_free_space
    
    Migration should fail if available space in dst < src
    
    The expression was evaluating otherwise
    
    Change-Id: Ief64ad8797e405d0cdc787eef49bfbf4051dffac
    BUG: 798864
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2847
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6c4b8d02db7b47d67a306a71a72bcc016fbdf183
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Feb 29 23:23:54 2012 +0530

    mgmt/glusterd: do not close the same fd twice
    
    In volfile generation part, if the close on the file stream for
    the volfile fails, then we should not again close the same file
    stream which may lead to undefined behavior.
    
    Change-Id: Idec00955eea11d5b2ea74574f8d4e53fa80c220a
    BUG: 798599
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2843
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 70fb696abd6144199bc08b05d403daaca314c7b4
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Mar 1 00:35:36 2012 +0530

    perf/md-cache: hold lock on modification of md_cache structure
    
    as it is possible that multiple fops can alter the content of
    md-cache structure from inode-ctx, we need to safe-guard the
    issue of corruption due to race conditions.
    
    Change-Id: Iea051f8f6adff7690d6d60f3cf82eda75150b449
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 798179
    Reviewed-on: http://review.gluster.com/2834
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 49a0c12e490f72d94acd6169a33f3f0f855000db
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Feb 29 16:06:25 2012 +0530

    cluster/stripe: Send xattr request in lookup even when type is INVAL
    
    Change-Id: I6f66b5aa39eaa5eadca2a91b1d4e948490f0aa06
    BUG: 798161
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2837
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 0054807e5288727599bc264e64f83e9fb526732f
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Feb 29 16:16:12 2012 +0530

    nfs: prevent crash during cthon lock test
    
    When cthon was invoked to test nlm, the mount point
    would hang, and crash nfs server, and all the brick
    processes. This path fixes the crashes.
    
    Change-Id: Ide88adb7e25ea722b143bfd62e23361ff7be4b67
    BUG: 798194
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2842
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 72eda6a45b52e98458e4efa3e9819a8a3a25faef
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 28 09:27:32 2012 +0530

    libglusterfs: Handle loc_copy for nameless loc
    
    BUG: 787671
    Change-Id: I7601f482ae753ead83be16d1df33c2187e76dc5c
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2825
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 15141a7660b1e4430513c8a96a498da652023894
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Feb 28 15:27:24 2012 +0530

    protocol/client: send unique key to server during handshake
    
    utilize the graph->id for making the key unique.
    
    Change-Id: I0c1b355aa901af88e65fd12cb9e0535318856867
    BUG: 783982
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/2831
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Mohammed Junaid <junaid@redhat.com>

commit ca8e61069b4fec42efa76da2070d362607770bc7
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Feb 28 12:57:26 2012 +0530

    nfs/doc: corrections
    
    corrections in nfs configuration helpers displayed
    with "gluster volume set help".
    
    Change-Id: Iffc0d10eacbaea647270cd875d4cbd5f80333671
    BUG: 771876
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2829
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2da18b6724b7daf7c3a973515fc3d59e7d2c4622
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Feb 22 14:51:53 2012 +0530

    transport/socket: configuring tcp window-size
    
    Till now, send and recieve buffer window sizes for sockets
    were set to a default glusterfs-specific value.
    Linux's default window sizes have been found to be better
    w.r.t performance, and hence, no more setting it to any
    default value.
    
    However, if one wishes, there's the new configuration option:
       network.tcp-window-size <sane_size>
    which takes a size value (int or human readable) and will set
    the window size of sockets for both clients and servers.
    Nfs clients will also be updated with the same.
    
    Change-Id: I841479bbaea791b01086c42f58401ed297ff16ea
    BUG: 795635
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2821
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5ad1c2caed743fc10a0645055a825252dfbf77ba
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Feb 28 18:03:29 2012 +0530

    storage/posix: In lookup check for buf->gfid being NULL
    
    There are few cases where create and lookup race.
    Lookup ends up getting a valid struct iatt, but with no gfid set.
    We need to check for gfid being 0, and handle it as an error.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I36ae1978b325aff964cbc3b24730c1e993666267
    BUG: 797167
    Reviewed-on: http://review.gluster.com/2832
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c2c82c360fda20533093c27c82ce0725cf40cab5
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Feb 27 05:41:11 2012 +0100

    glusterd/mountbroker: fix handling of MEET mountbroker keyword
    
    Change-Id: I5331a17a772e9ef15e132b9f335e5ff9d70735b7
    BUG: 765214
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2817
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c1e3d3b963a46fb92d309ac3d0a11adfad8ce745
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Feb 24 14:59:43 2012 +0530

    locks/glusterd: Fixed clearing of posix locks from failing always.
    
    Change-Id: Ieaf636c6f0d2aa1d001143a2d1433fce85dc8c7a
    BUG: 797042
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2812
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 19dd4b7f0080a1924099ace7e3d7fcd9f0314f2d
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Feb 24 15:25:06 2012 +0530

    mgmt/glusterd: pass defrag_cmd in rsp dict for volume info
    
    glusterd_import_volinfo used to error out as it was not able
    to find the rebalance key in the dict
    
    Change-Id: Ife35a041072a8a978d7595e8381f68e624bd8da3
    BUG: 797105
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2814
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a3f6b0c4f231ccdb727227c9c35816b4823cef90
Author: Amar Tumballi <amarts@redhat.com>
Date:   Thu Feb 23 12:53:19 2012 +0530

    mempool: add more counters to understand the usage scenarios properly
    
    current design of mempool is to fallback to standard calloc/free if
    all the buffers in pool are exhausted. Understanding more about those
    numbers will help us to tune mempool parameters properly over time.
    
    Change-Id: I2c94373186f7c6a486caff2611c2d9df2c37db3c
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 797730
    Reviewed-on: http://review.gluster.com/2804
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 85471322df9676cc344cc2b03627c02ed90da3cd
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Feb 23 22:58:44 2012 +0530

    glusterfsd: unref the dict and free the memory to avoid memleak
    
    Change-Id: Ib7a1f8cbab039fefb73dc35560a035d5688b0e32
    BUG: 796186
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2808
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bd94f6a1cc26fbcf8811e04dab0c90257b44d89a
Author: Kaushal M <kaushal@redhat.com>
Date:   Mon Feb 27 15:34:11 2012 +0530

    cli: Fix broken "volume set help/help-xml"
    
    Change-Id: I4e71e67f32ff37cfe23bc77c0e27645ac495a247
    BUG: 796040
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2822
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3cad6558b030bc3b0ebb662ec7d0346ab9a32cc2
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Feb 26 22:16:59 2012 +0530

    cli: Add 'exit' command.
    
    Based on request at:
    http://community.gluster.org/i/make-cli-understand-command-exit/
    
    Change-Id: I9116236a8c2f7767c88672b8d3d6565906bfc61f
    BUG: 797551
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2815
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 20b50008c710c973ebb0a84506b55e6aea044fad
Author: Csaba Henk <csaba@redhat.com>
Date:   Mon Feb 27 05:40:58 2012 +0100

    libglusterfs: fix GF_FREE
    
    Argument-taking macros should be possible to use with
    same syntax that of C functions. In particular (assuming
    FOO is a single-argument macro),
    
      FOO(bar)
    
    should break and
    
      if (cond)
        FOO(bar);
      else
        baz();
    
    should compile.
    
    Change-Id: If852c128a7317dc0dda1c669be7c6af40501e48d
    BUG: 762061
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2816
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 728de5be7ce2975efb59bb5928fd7261d5ec7760
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Dec 15 17:38:05 2011 +0530

    locks: Made dump locks formatting more 'readable'.
    
    Also,
    Added inode's path to dump locks.
    Added basename to entrylk dump output.
    Added whence field of range locks to dump output.
    
    Change-Id: Ifd3f8b585a52de7ff68cd54506619ac3eaedeecc
    BUG: 789858
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/798
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 88c6c11813cbd60a6b8e5ec4e2edd40e326ac311
Author: Shylesh Kumar <shylesh@gluster.com>
Date:   Thu Feb 23 14:59:36 2012 +0530

    Change rebalance log file name
    
    Log file name for the rebalance process should
    be <volname>-rebalance.log
    
    Change-Id: I1ed169cdc92b11058b80360086b3c1f7618064ef
    BUG: 795714
    Signed-off-by: Shylesh Kumar <shylesh@gluster.com>
    Reviewed-on: http://review.gluster.com/2805
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit d4ff4103e09ba076653aa6f0774269c47cc931f2
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Feb 22 19:38:14 2012 +0530

    glusterd: Modified server graph to have index xl above pump
    
    Index xlator needs a resolved inode in the incoming xattrop request to perform
    its indexing. In the case of replace-brick pump xlator doesn't resolve the
    inode in the (fop) requests it sends 'downwards', leading to null gfid sent to
    index xlator.
    
    Change-Id: I6b6e7af4354670616bf342292df1a25c219dd9e9
    BUG: 796171
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2801
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit 5842656feba99a239b922f8099fb336c66b61929
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Feb 21 14:23:13 2012 +0530

    Introduce new extended attribute: node-uuid
    
    Request for trusted.glusterfs.node-uuid returns pathinfo
    like string but containing the UUID of glusterd instead
    of the backend path for the requested file. This info
    is benificial for tasks like parallel rebalance that will
    make use of the UUID for data locality.
    
    Change-Id: I766a09cc4a5f63aebd11c73107924a1b29242dcf
    BUG: 772610
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/2614
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7820f7563aff8e1a5e73eb75adc387635a301b6e
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Feb 23 12:24:08 2012 +0530

    protocol/client: Pass correct dict in client_readdirp
    
    Also, alloc entry->dict before calling unserialize to it.
    
    Change-Id: I8a9db93afd6e95e75307467cd654805780d7b467
    BUG: 796534
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2803
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 52904f0d416aedf61fcebe2e5051bfa92999c6e4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Feb 22 16:08:26 2012 +0530

    build: Changes to specfile for correctness and package relevance.
    
    - Removes a stale dependency of glusterfs-client on glusterfs-core
    - Server specific shared libraries included in glusterfs-server package.
    
    Change-Id: I852304e6351a9a7864b2049f603e11f6a5601ffb
    BUG: 764702
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2797
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4ac06a16999bde2f9860f6a8713e7f2544b44f9a
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Feb 23 01:25:47 2012 +0530

    features/marker: Use loc.inode to obtain parent if loc.parent isn't set.
    
    Change-Id: I89dddb19168a3ffb269afc9f6bcb2d7e7c9a69cd
    BUG: 790389
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2802
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>

commit 72187f8e02e7d3aa17636ade033482e4de41657a
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Feb 22 08:30:47 2012 +0530

    glusterfsd: give out the error on screen when cmd is given without options
    
    'glusterfs' cmd would take default options when no option is given,
    but sometimes default option may not work, in that case, we need
    to provide usage output
    
    Change-Id: I2ebd342890da11d2afaa0a23ee3a01d87694ff28
    BUG: 791198
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/2790
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 683ce1bca3b6c541e565eec014fa7cc3308957d8
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Feb 22 18:27:15 2012 +0530

    glusterfsd: unref the dict and use dict_set_dynstr to avoid memleak
    
    Unref the new dict and use proper dict api (dict_set_dynstr) to save
    data for displaying volume status information, which otherwise leads
    to memory leak in the process.
    
    Change-Id: Icb9ceb1a867c5b9759211a67027d983ab9b7e1c2
    BUG: 796186
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2799
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ca502ca780202c71623a34349c88d114ad58ec12
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Feb 22 14:38:42 2012 +0530

    cli: print the type of the inode in gluster volume status inode output
    
    Instead of a number print the type of the inode in the output of
    gluster volume status inode. This is what the output symbols indicate.
    
    R -----> Regular file
    D -----> Directory
    L -----> symbolic Link
    B -----> Block special device
    C -----> Character special device
    F -----> FIFO
    S -----> Socket
    I -----> Invalid inode type
    
    Also supress a warning message displayed at the time of build.
    
    Change-Id: I5a2adfe044ce21d9da159652d4b6e25cd0a2fdca
    BUG: 796078
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2794
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1350aecc7e600e73b810522c7727be20bdd3ae40
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Feb 22 18:35:07 2012 +0530

    protocol/client: Print correct error message
    
    Change-Id: Ic68626c4a205cd78b60831aa7bd838b6d8824fa1
    BUG: 796195
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2800
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 67104b716a93520d66c6e572b5f94aa808645e56
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Feb 21 16:55:28 2012 +0530

    mempool: adjustments in pool sizes
    
    * while creating 'rpc_clnt', the caller knows what would be the ideal
      load on it, so an extra argument to set some pool sizes
    
    * while creating 'rpcsvc', the caller knows what would be the ideal
      load of it, so an extra argument to set request pool size
    
    * cli memory footprint is reduced
    
    Change-Id: Ie245216525b450e3373ef55b654b4cd30741347f
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 765336
    Reviewed-on: http://review.gluster.com/2784
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f37fcaab9eb0601898f4ba6fb747d5c8d3fe4195
Author: Amar Tumballi <amarts@redhat.com>
Date:   Wed Feb 22 17:27:59 2012 +0530

    mount.glusterfs: multiple fixes
    
    * fix return value in case of proper 'backup-volfile-server' option,
      and actual default server based mount failed.
    
    * fix a syntax error (bug: 796050)
    
    Change-Id: I6a530c9b9431e46f45ec9eeb99f6103386dd10dc
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    BUG: 796101
    Reviewed-on: http://review.gluster.com/2798
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a423cf80d17285de69594401559b7a255281c26c
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Feb 22 15:06:23 2012 +0530

    cluster/stripe: Readdirp should call lookup on entries
    
    We were calling stat on each entry. Also, the inode ctx
    needs to be populated with the stripe_fd_ctx_t.
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    
    Change-Id: Ibaafa360f22b551d1609041f13a4339e22c95645
    BUG: 795669
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2795
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 064bd0f25a02bd65e32a1c03bfb124340dd60651
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Feb 2 19:17:12 2012 +0530

    cluster/afr: Don't trust the fd returned in open_cbk
    
    Change-Id: Id7d85a38875e3675904fc134e54e723c6a0c4de2
    BUG: 786766
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2792
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2b52b096a7db3124fdd97554e63792f36e889af9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Feb 22 13:46:37 2012 +0530

    features/locks: Don't access free'd memory
    
    Change-Id: I4e22ede84622f2c9c46cc0bc9f17bef73afa815c
    BUG: 796069
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2791
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f3b2305009b98de42c84e5b86668cf8b5f41e01f
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Feb 22 15:07:03 2012 +0530

    pump: Fixed undefined reference to fill_loc_info fn.
    
    Changed function to pump_fill_loc_info since its use is relevant
    only in pump's context.
    
    Change-Id: I5be1a908f88328f732dacfd7eac18f0c62f49eb8
    BUG: 796066
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2796
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2d470cd910b49976befea664ae5cc7ea6aa10020
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Feb 21 10:45:32 2012 -0800

    libglusterfs/options: Cleanup xlator percent_sizet code.
    
    Change-Id: I1a39252d6c26f7e30b77ef682b8b3cdcde8a4a51
    BUG: 769691
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/2619
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 311de6f96c4fabf30f734e62996ec18817447e2f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 21 18:12:41 2012 +0530

    features/index: Set correct ret value in index_add
    
    Change-Id: I6314ea25ef26920593a3113eb2951d18255db34f
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2786
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 42cc043875621a02444f3324b2f9629ac68ab5aa
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Feb 21 23:35:05 2012 +0530

    build: More rpmbuild friendly changes
    
    Change-Id: I7dcd5c6461bbddde3bcc3d2519777e4c8889fe52
    BUG: 764702
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2788
    Reviewed-by: Venky Shankar <vshankar@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f2eb8e4a17219e6a75b8673181f4bb0b85697d66
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Feb 21 17:35:31 2012 +0530

    build: rpmbuild friendly changes
    
    Change-Id: Ia1299d4404da0bd6787516924ebadcf9d6e021d1
    BUG: 764702
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2785
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0344a8a12e7675bee24c770d71eff52db6b2d128
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Feb 21 13:39:29 2012 +0530

    glusterd/auth: 3.2.x compatibility
    
    volumes created with GlusterFS 3.2.x will be compatible
    with GlusterFS 3.3 w.r.t auth.allow enhancements
    
    Change-Id: I615e46d648e1270a7b856cd71fab24cfe791ddb8
    BUG: 795634
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2779
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6a6abb5367f46bab4a7363db9e181c845a334cdb
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 21 14:46:05 2012 +0530

    features/index: Fix fd leak
    
    Change-Id: Ib01d03999b099369674495ce500f48d492758f91
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2781
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 709de8c86a2947c98d59a5b32bcf258c196bab4b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 21 11:25:07 2012 +0530

    libglusterfs: Warn on missing _cbk calls in xlator
    
    Change-Id: I44684b5eeca3674ed8d5b7b0120699bb3767e38d
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2782
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit e311a30f845255b44f3abc56215f584a3c245136
Author: Kaushal M <kaushal@redhat.com>
Date:   Fri Feb 17 12:32:18 2012 +0530

    cli, glusterfsd: Fixes for "volume top {read,write}-perf"
    
    Changed variables to use unsigned types, to support larger comninations of
    block_size * block_count
    Also increases cli time out for "volume top" ops to 600, to allow more time
    for glusterd to return the results to cli.
    
    Change-Id: I4b953799c78a5a184311f6f8c4a7a99dc9e87a07
    BUG: 783980
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2761
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0ef7e763c85c045ef7937d0ca02d8c5f0333e6e8
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Feb 21 14:47:48 2012 +0530

    core: utilize mempool for frame->local allocations
    
    in each translator, which uses 'frame->local', we are using
    GF_CALLOC/GF_FREE, which would be costly considering the
    number of allocation happening in a lifetime of 'fop'. It
    would be good to utilize the mem pool framework for xlator's
    local structures, so there is no allocation overhead.
    
    Change-Id: Ida6e65039a24d9c219b380aa1c3559f36046dc94
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 765336
    Reviewed-on: http://review.gluster.com/2772
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1f296b84e6c7bf55fc81d0c1dade7ccda75229a6
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 17 17:22:59 2012 +0530

    cluster/distribute: send the right 'dict' for check_is_linkfile()
    
    earlier we were using 'check_is_linkfile_wo_dict()' for readdirp_cbk(),
    which is no more required now.
    
    Change-Id: I52295e08f8c494b7a081cfc684164a7f72562d0d
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 794641
    Reviewed-on: http://review.gluster.com/2763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1979cee4716fdb95909654148eebb8b0b973f484
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 21 11:18:32 2012 +0530

    features/index: Add release, releasedir cbks
    
    Change-Id: Ice45a0b4e953e270273aa4155a895d6ec033fda8
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2780
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 39fb5051ffdf6a978537e8c50f05b7a0135f7075
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Feb 21 15:50:35 2012 +0530

    features/md-cache: Change strdup to gf_strdup
    
    Change-Id: Ic96e7d38b988efab49f723c9d1d46f65037a84ed
    BUG: 795682
    Reviewed-on: http://review.gluster.com/2783
    Reviewed-by: Anand Avati <avati@redhat.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 490d8805f0d9b4e58258505d678f0e75e089aa26
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Jan 10 17:42:24 2012 -0500

    Honor O_SYNC etc. properly.
    
    Change-Id: I3dd90fe230386ad5571c5e639f27460e3d003f0e
    BUG: 773100
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/2626
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit bca46fd46b1a1a28daeb9ea3f47cef9bbacecd6d
Author: Amar Tumballi <amarts@redhat.com>
Date:   Tue Feb 21 15:02:39 2012 +0530

    rpc/clnt: handle PARENT_DOWN event appropriately
    
    Change-Id: I4644e944bad4d240d16de47786b9fa277333dba4
    BUG: 767862
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-on: http://review.gluster.com/2735
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7197111677619da96c80572a09331d6e28c1015b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Feb 8 15:06:30 2012 +0530

    fuse-bridge: Handle graph-switch.
    
    The purpose of this patch is to let protocol/client know when its transports can
    be disconnected, without application running on gluster mount noticing any
    effects of graph switch.
    
    In order to do this, we migrate all fds and blocked locks to new graph.
    Once this migration is complete and there are no in-transit frames as viewed
    by fuse-bridge, we send a PARENT_DOWN event to its children. protocol/client
    on receiving this event, can disconnect up its transports.
    
    Change-Id: Idcea4bc43e23fb077ac16538b61335ebad84ba16
    BUG: 767862
    Reviewed-on: http://review.gluster.com/2734
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6d19136de7af9135dd23662f18c3ee544a2888da
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 21 12:45:24 2012 +0530

    performance/md-cache: Add mem_acct_init
    
    Change-Id: I1b91ee0bde160762548c39646ceb96c3c778e06c
    BUG: 795651
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2778
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 81ab6622d403558cd6f31efeb535fe886d3beeaa
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Feb 16 21:30:47 2012 +0530

    cluster/afr: Add commands to see self-heald ops
    
    Change-Id: Id92d3276e65a6c0fe61ab328b58b3954ae116c74
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2775
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5f117a4a1fca3ec2d163fe77615cf6859c0450e4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Feb 14 22:40:34 2012 +0530

    cluster/afr: Self-heald, Index integration
    
    Change-Id: Ic68eb00b356a6ee3cb88fe2bde50374be7a64ba3
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2749
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8456c28af75a4083286fc6ceadc03f2703f4c9b6
Author: Anand Avati <avati@redhat.com>
Date:   Fri Feb 3 00:16:30 2012 +0530

    md-cache: replace stat-prefetch with md-cache in a backward compatible way
    
    - preserve CLI set option key as "performance.stat-prefetch"
    - create a symlink stat-prefetch.so to point to md-cache.so
    
    Change-Id: Ib95e7c30073f13ae04c39e9466967ba1db5a0614
    BUG: 765785
    Reviewed-on: http://review.gluster.com/2714
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit c41a9d1c3fe4002bdf8849c4e8ae7c2e10841c69
Author: Anand Avati <avati@gluster.com>
Date:   Sat Sep 24 16:14:11 2011 +0530

    md-cache: meta-data caching translator
    
    This is a metadata caching translator which is well integrated with
    glusterfs core framework and leverages some of the recent protocol
    changes to do a better job at caching.
    
    - It uses the attributes returned along callbacks of all calls to
      update its attribute cache as frequently as possible without
      issuing calls on its own (i.e, very low overhead)
    
    - It caches attributes returned via readdirp into the inode contexts
      corresponding to those entries (i.e, well integrated)
    
    - It caches and updates xattrs and not just inode attributes (i.e,
      eliminates the need for a separate xattr-prefetch translator)
    
    In its current form it has a timeout based consistency model
    
    Change-Id: I891f6225c1a4c08bb111e287571d5f6d326dbe97
    BUG: 765785
    Reviewed-on: http://review.gluster.com/2713
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 1206437fcfc1f3e1bd4a6faec3341c240bae5cf2
Author: Anand Avati <avati@redhat.com>
Date:   Tue Feb 21 09:25:14 2012 +0530

    syncop: Multi-processor support in syncenv
    
    This patch introduces:
    
    - multithreading of syncop processors permitting synctasks to be executed
      concurrently if the runqueue has many tasks.
    
    - Auto scaling of syncop processors based on runqueue length.
    
    - Execute a synctask (synctask_new) in a blocking way if callback function
      is set NULL. The return value of the syncfn will be the return value
      of synctask_new()
    
    Change-Id: Iff369709af9adfd07be3386842876a24e1a5a9b5
    BUG: 763820
    Reviewed-on: http://review.gluster.com/443
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit dfc88bf3727fb33e2fc273bd7f24401e0209f39e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Feb 20 19:48:07 2012 +0530

    storage/posix: Add xattr for gfid2path
    
    Change-Id: I1fe987d255bf50e8433043749b482b67554a0ac3
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2774
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d349334fc0b3b069875b2724a5a46dfeb84289e4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 20 22:27:31 2012 +0530

    nfs/server: Fix compilation warnings
    
    Change-Id: If5c2375adb3769827cf5099cb6b2d19ba75bf238
    BUG: 795421
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2776
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 12480df27becfc5aef5ff0f1d712d4d73c894c7a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Feb 2 19:14:28 2012 +0530

    features/index: Index translator implementation
    
    Change-Id: If8a11ecbdd010f64fb4409add5751080f4b59086
    BUG: 763820
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2722
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ed2036979499cb272336187c06955aa5e484023d
Author: Krishna Srinivas <ksriniva@redhat.com>
Date:   Mon Feb 20 14:34:39 2012 +0530

    NLM - Network Lock Manger V4
    
    Change-Id: Ic31b8bb10a28408da2a623f4ecc0c60af01c64af
    BUG: 795421
    Signed-off-by: Krishna Srinivas <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2711
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit db20a0f8a99f715a77366e518720612f043d5c9e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Feb 20 18:42:37 2012 +0530

    libglusterfs: Implement circular buffer and event history
    
    Implement circular buffer framework, so that it can be used by other components
    such as event history management. And event history is implemented which can
    be used by xlator to dump some information to a file (such as information of some
    structure etc).
    
    Through statedump, history of each xlator can be dumped. An option called history
    should be given to the statedump command.
    
    Change-Id: I7c5e8f6bd1018584eaee856e933e7c4b94c6709c
    BUG: 795419
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2769
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f764516c2e526624ce0088963924ff2d88304553
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Wed Feb 8 18:06:39 2012 +0530

    protocol/client,server: fcntl lock self healing.
    
    Currently(with out this patch), on a disconnect the server cleans up
    the transport which inturn closes the fd's and releases the locks acquired on
    those fd's by that client. On a reconnect, client just reopens the fd's but
    doesn't reacquire the locks. The application that had previously acquired
    the locks still is under the assumption that it is the owner of those locks
    which might have been granted to other clients(if they request) by the server
    leading to data corruption.
    
    This patch allows the client to reacquire the fcntl locks (held on the fd's)
    during client-server handshake.
    
    * The server identifies the client via process-uuid-xl (which is a combination
      of uuid and client-protocol name, it is assumed to be unique) and lk-version
      number.
    
    * The client maintains a list of process-uuid-xl, lk-version pair for each
      accepted connection. On a connect, the server traverses the list for a
      matching pair, if a matching pair is not found the the server returns
      lk-version with value 0, else it returns the lk-version it has in store.
    
    * On a disconnect, the server and client enter grace period, and on the
      completion of the grace period, the client bumps up its lk-version number
      (which means, it will reacquire the locks the next time) and the server will
      distroy the connection. If reconnection happens within the grace period, the
      server will find the matching (process-uuid-xl, lk-version) pair in its list
      which guarantees that the fd's and there corresponding locks are still valid
      for this client.
    
    Configurable options:
      To set grace-timeout, the following options are
        option server.grace-timeout value
        option client.grace-timeout value
    
      To enable or disable the lk-heal,
        option lk-heal [on|off]
    
    gluster volume set command can be used to configurable options
    Change-Id: Id677ef1087b300d649f278b8b2aa0d94eae85ed2
    BUG: 795386
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2766
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4d1b040f00e7ec8de997d151b35fa035bba9cb25
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Feb 20 14:34:39 2012 +0530

    volgen: give an option to insert trace/error-gen
    
    currently, these translators can be plugged in on the server
    volfile. Need to enhance on client side too.
    
    Change-Id: I8c3696f62f1de646a736d68c4c427c6fffd6bbf4
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 782262
    Reviewed-on: http://review.gluster.com/776
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6827f56dfcde4546e5adb3af65e7f21bef7fd58a
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Feb 15 14:33:19 2012 +0530

    protocol/client: delete locks only for non-anonymous fds
    
    delete_granted_lock_owners () is not called for anonymous
    fds since they are not involved in locking
    
    Change-Id: Icdc7818f98f5371232ba276ed442704ef69e6b0e
    BUG: 787365
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2754
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c0b8e886cac4ef0f16d5f93adab02229bb1414cd
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Feb 14 15:05:19 2012 +0530

    iobuf: use 'iobuf_get2()' to get variable sized buffers
    
    added 'TODO' in places where it is missing.
    
    Change-Id: Ia802c94e3bb76930f7c88c990f078525be5459f5
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 765264
    Reviewed-on: http://review.gluster.com/388
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 975933a25d14cbac861e809b40c6edd01acaa28d
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Feb 20 12:31:10 2012 +0530

    glusterd: auth allow enhancements
    
    * PROBLEM:
    
      When address-based authentication is enabled on a volume,
      the gNfs server, self-heal daemon (shd), and other operations
      such as quota, rebalance, replace-brick and geo-replication
      either stop working or the services are not started if all
      the peers' ipv{4,6} addresses or hostnames are not added in
      the "set auth.allow" operation, breaking the functionality
      of several operations.
    
      E.g:
        volume vol in a cluster of two peers:
        /mnt/brick1 in 192.168.1.4
        /mnt/brick2 in 192.168.1.5
    
        option auth.allow 192.168.1.6
        (allow connection requests only from 192.168.1.6)
    
        This will disrupt the nfs servers on 192.168.1.{4,5}.
        brick server processes reject connection requests from both
        nfs servers (on 4,5), because the peer addresses are not in
        the auth.allow list.
    
        Same holds true for local mounts (on peer machines),
        self-heal daemon, and other operations which perform
        a glusterfs mount on one of the peers.
    
    * SOLUTION:
    
      Login-based authentication (username/password pairs,
      henceforth referred to as "keys") for gluster services and
      operations.
    
      These *per-volume* keys can be used to by-pass the addr-based
      authentication, provided none of the peers' addresses are put
      in the auth.reject list, to enable gluster services like gNfs,
      self-heal daemon and internal operations on volumes when
      auth.allow option is exercised.
    
    * IMPLEMENTATION:
    
      1. Glusterd generates keys for each volume and stores it in
         memory as well as in respective volfiles.
         A new TRUSTED-FUSE volfile is generated which is
         fuse volfile + keys in protocol/client,
         and is named trusted-<volname>-fuse.vol.
         This is used by all local mounts. ANY local mount (on any peer)
         is granted the trusted-fuse volfile instead of fuse volfile
         via getspec. non-local mounts are NOT granted the trusted fuse
         volfile.
    
      2. The keys generated for the volume is written to each server
         volfile telling servers to allow users with these keys.
    
      3. NFS, self-heal daemon and replace-brick volfiles are updated
         with the volume's authentication keys.
    
      4. The keys are NOT written to fuse volfiles for obvious reasons.
    
      5. The ownership of volfiles and logfiles is restricted to root users.
    
      6. Merging two identical definitions of peer_info_t in auth/addr
         and rpc-lib, throwing away the one in auth/addr.
    
      7. Code cleanup in numerous places as appropriate.
    
    * IMPORTANT NOTES:
    
      1. One SHOULD NOT put any of the peer addresses in the auth.reject
         list if one wants any of the glusterd services and features
         such as gNfs, self-heal, rebalance, geo-rep and quota.
    
      2. If one wants to use username/password based authentication
         to volumes, one shall append to the server, nfs and shd volfiles,
         the keys one wants to use for authentication, *while_retaining
         those_generated_by_glusterd*.
         See doc/authentication.txt file for details.
    
    Change-Id: Ie0331d625ad000d63090e2d622fe1728fbfcc453
    BUG: 789942
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2733
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 27e51951bc53f36b2286c70eb2263173b29d7a85
Author: Venky Shankar <vshankar@redhat.com>
Date:   Wed Feb 15 12:04:24 2012 +0530

    GlusterFS Hadoop Plugin
    
    Apache Hadoop plugin to run Map/Reduce (MR) jobs on data
    stored on GlusterFS. This is a drop in replacement for
    HDFS requiring the plugin jar and modification to a
    single conf file to enable MR jobs to process data on
    GlusterFS.
    
    Change-Id: I8862efec30708849fa7c544fed88b8e50e622fed
    BUG: 790671
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/2751
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4a65356275cda45f665dfa99d3712f6fb9087aff
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Feb 17 19:21:07 2012 +0530

    cluster/dht: Support for hardlink rebalance when decommissioning
    
    The support for hardlink rebalance is only available for decommissioning
    of a node. this can be triggered in two ways
    1. remove-brick start
    2. if decommission node value is set in vol file, then a normal rebalance
       command
    
    The way we handle it is-
    if (nlink > 1)
    do
           * if src file doesnt have linkto xattr
                    * mark src's linkto to the dst
           * else
                    * perform a link on the dst
                    * do a look up
                    * if nlinks = dst.nlinks
                            * migrate data
                    * else
                            * continue crawling
    done
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: If43b5524b872fd1413e9f7aa7f436cb244e30d8d
    BUG: 763844
    Reviewed-on: http://review.gluster.com/2737
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 6123265556e54891369cc79a72b670a4b23a8a41
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Feb 16 14:47:27 2012 +0530

    cluster/dht: Handle get cached/hashed subvol failures gracefully
    
    Change-Id: I7a41c2876be04acd166b2004d9aa66af078d32ea
    BUG: 790328
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2757
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit be0fdd8363fd3683c782d9fef86a1b9ffb38983a
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Jan 20 00:01:53 2012 +0530

    cluster/dht: Exit clean when assert_no_child_down is enabled
    
    Change-Id: If90b1080edcf3792f8590492b585a6dd48fac18e
    BUG: 783249
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2664
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 82da7e9acf6c6091599835117439260f0505d528
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Feb 18 12:12:10 2012 +0530

    cluster/distribute: send the proper 'loc_t' for statfs()
    
    in dht-diskusage.c, which was getting used for getting free disk
    space of all subvolumes
    
    Change-Id: Ieb2bb5f2479fac1803b9af4ef1948954a026c2ee
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 290282
    Reviewed-on: http://review.gluster.com/2767
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e8b6dad4dea4535a179a03824aa44628f9adaa17
Author: Joe Julian <me@joejulian.name>
Date:   Wed Nov 9 18:27:25 2011 -0800

    Merged in the fedora spec file to bring glusterfs into compliance
    with FSH and Redhat/Fedora requirements.
    Created a single spec that works for both 3.1 and 3.2 versions.
    
    Releases will now require changing the source url in configure.ac
    at the same time the release version is set.
    
    OLDBUG: 2970
    BUG: 764702
    
    Change-Id: I1ec9d10fce6dbd72c329d04c7ad61df2ad117adb
    Signed-off-by: Joe Julian <me@joejulian.name>
    Reviewed-on: http://review.gluster.com/701
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7ba1e1ed45cee56ef51b9c04df99c976546d5d04
Author: shishirng <shishirng@gluster.com>
Date:   Wed Jan 18 15:29:15 2012 +0530

    cluster/dht: Rebalance will be a new glusterfs process
    
    rebalance will not use any maintainance clients. It is replaced by syncops,
    with the volfile. Brickop (communication between glusterd<->glusterfs process)
    is used for status and stop commands.
    
    Dept-first traversal of dir is maintained, but data is migrated as and when
    encounterd.
    fix-layout (dir)
    do
            Complete migrate-data of dir
            fix-layout (subdir)
    done
    
    Rebalance state is saved in the vol file, for restart-ability.
    A disconnect event and pidfile state determine the defrag-status
    
    Signed-off-by: shishirng <shishirng@gluster.com>
    Change-Id: Iec6c80c84bbb2142d840242c28db3d5f5be94d01
    BUG: 763844
    Reviewed-on: http://review.gluster.com/2540
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 061d70e8195d082043b071118333b7e3173fa3ec
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Feb 18 12:58:39 2012 +0530

    extras/rpc-coverage.sh : behavior fix
    
    don't treat getfattr after 'setfattr -x' (ie, removexattr())
    as an error. ignore the output so the script runs for completion
    
    Change-Id: Id7089b91e7259a39be7cb6fce627828774c4acbc
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 787956
    Reviewed-on: http://review.gluster.com/2768
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit df12073c4cc8340eb85b5d25c2da84fc21ec1f38
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Jan 31 17:04:37 2012 +0530

    cli/glusterd: volume status modification
    
    * Method of getting mount details of brick has been
      changed from direct reading of /etc/mtab to using
      libc's <mntent.h>, providing a fairly portable
      version independent of different linux distributions.
      It is only supported on Linux though.
    
    * Wrong fs type (rootfs for /) in fedora-based
      distributions has been fixed.
    
    * Allows options (detail, mem, fd, et al) to "all" volumes.
    
    * Use of the fnmatch's GNU extension flag,
      FNM_LEADING_DIR is restricted to Linux hosts only.
      In case of non-Linux hosts, partial match functionality
      is absent.
    
    Change-Id: I102ce808c192ef635c2536a2167101be0aa0fc50
    BUG: 786367
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2705
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit acb691f8908049e651fc12ff1cf01e9cf4ddde65
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Sat Dec 24 13:49:52 2011 +0530

    cli, glusterd : Added support for clear-locks command.
    
    Change-Id: I8e7cd51d6e3dd968cced1ec4115b6811f2ab5c1b
    BUG: 789858
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2552
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b016fe67b6c8957eebc9736b9af9406326800b6d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Feb 17 12:15:48 2012 +0530

    mount/fuse: unref the fd from resolve to avoid fd leak
    
    Change-Id: I162e07219b98669bc6e09784830ca9407518fd8b
    BUG: 794618
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2760
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 489a7a10fe2e00d00d86f0304145a4910bb94070
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Feb 1 14:44:07 2012 +0530

    cli: Fix for statedump crashing gluster processes
    
    1. Fixes the bug in statedump causing the gluster process to crash when an unknown
    option was given in the 'glusterdump.*.options' file.
    2. Also fixes cli, making it send full statedump option strings even when only
    partial option strings are given in 'volume statedump' command.
    3. Minor change to order of operations during statedump to allow option parsing
    errors to be written to the dump file.
    
    Change-Id: Ic878cbca4dbf46b83fba0fd88fcb3c03f05ae46d
    BUG: 772586
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2706
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7fa06c4ce1a44bbd89d3798193f173c057533bb6
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Feb 15 19:48:50 2012 +0530

    protocol: remove the 'path<>' from rename() and link()
    
    missed it in the previous round of cleanup, path is completely
    useless in resolve function.
    
    Change-Id: I1aef0f5276afb77dfacfcc0c337ac80b4fcacc55
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 790298
    Reviewed-on: http://review.gluster.com/2756
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 47e748fe60c46d543c87f3228eb59d6580db8cf1
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Feb 15 17:20:40 2012 +0530

    posix: handle some internal behavior in posix_mknod()
    
    assume a case of link() systemcall, which is handled in distribute by
    creating a 'linkfile' in hashed subvolume, if the 'oldloc' is present
    in different subvolume. we have same 'gfid' for the linkfile as that
    of file for consistency. Now, a file with multiple hardlinks, we may
    end up with 'hardlinked' linkfiles. dht create linkfile using 'mknod()'
    fop, and as now posix_mknod() is not equipped to handle this situation.
    
    this patch fixes the situation by looking at the 'internal' key set in
    the dictionary to differentiate the call which originates from inside
    with regular system calls.
    
    Change-Id: Ibff7c31f8e0c8bdae035c705c93a295f080ff985
    BUG: 763844
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/2755
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 4cc4e47f6cad1127ad425cc0ab10bc42ab1411c8
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Feb 16 17:48:44 2012 +0530

    storage/posix: reset op_ret to -1 after call to MAKE_INODE_HANDLE
    
    MAKE_INODE_HANDLE uses op_ret. We do not reset it to -1, and in few
    instances we jump to label out, where we unwind with op_ret.
    
    Change-Id: Iac4d9f250f5253b3ce0cd91cc385168247efd4a8
    BUG: 788998
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2759
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b19719d037f32a5af109bc474afda2230a0a2403
Author: Shylesh Kumar <shylesh@gluster.com>
Date:   Thu Feb 16 11:06:08 2012 +0530

    filter stripe internal xattrs from getxattr call
    
    Change-Id: Ia0e9662644494c61033e7a7853353294598984af
    BUG: 787964
    Signed-off-by: Shylesh Kumar <shylesh@gluster.com>
    Reviewed-on: http://review.gluster.com/2758
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 26800453aacd76e6edc36c078aaacbe7c16aa75e
Author: Kaushal M <kaushal@redhat.com>
Date:   Wed Feb 15 16:18:25 2012 +0530

    cli: Enable output in XML
    
    This patch enables gluster cli to output data in xml format. XML output can be
    obtained by passing "--xml" as an argument.
    
    A new "volume list" command, which lists the volumes present in a cluster, has
    been added. This can be used for obtaining a quick list of volumes.
    
    Several commands, including "volume top", "volume profile", "volume status" and
    "volume info", "volume list", have custom XML output routines. Other commands
    use either one of the 2 generic output routines, cli_xml_output_str() &
    cli_xml_output_dict().
    NOTE: When using "all" for "volume status" and "volume info" the XML output will
    have multiple roots.
    
    Change-Id: I6117baa02ec06fda116177dbd401f66521263ac6
    BUG: 790713
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2753
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c8d47f056ef69d2a644646fd24e8f58de4c0e70e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Feb 15 11:22:00 2012 +0530

    features/marker: copy the gfid to loc from oplocal->loc.inode
    
    Change-Id: I8cfb70c163a3c4a0bd682678f71b38b5bae20ab4
    BUG: 790393
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2750
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 69dad8baff6b0461fde1edbcb1418d0ba3beaa6c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Jan 12 12:53:48 2012 +0530

    mgmt/glusterd: changes to run nfs server and self-heal daemon with valgrind
    
    Currently glusterd can start only the brick processes in the valgrind mode.
    This patch ensures that nfs server and self-heal daemon are also started
    with valgrind along with the bricks.
    
    Change-Id: I3136deb58d54075627cdd204002eb26fdfdde462
    BUG: 773600
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2638
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1fbed11ead209a8bcd1fd65846e0dfac6d5e1f2d
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Feb 14 16:28:44 2012 +0530

    nfs: avoid logging invalid fdctx in case of anonymous fds
    
    if get_fd_ctx fails (as in case of anonymous fds), overwhelming
    amount of entries are seen in the nfs log, causing dd and other
    heavy i/o operations to become unresponsive. this patch logs an
    invalid fdctx only if it is not an anonymous fd.
    
    Change-Id: I4e917d150d6a053af77d47a94a2f1c2633acadb5
    BUG: 787365
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2747
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 22d2abe742a67f1700f0f8f2a6449f3640826b27
Author: Rahul C S <rahulcs@redhat.com>
Date:   Tue Feb 14 17:09:21 2012 +0530

    Allows Successful log rotation when no bricks are specified.
    
    log rotate must happen for all the bricks if no specific
    brick path is given as an argument for the command.
    
    Change-Id: I39e55883fd301bedffae996384a8284119011951
    BUG: 765578
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2748
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 38d73bdfc659dde4a2632da2da01c785b642c728
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Feb 13 16:33:32 2012 +0530

    glusterd: Fail volume 'modify' operations when rb is ongoing
    
    * add-brick, stop-volume, remove-brick are the operations that are explicitly
     'failed' when attempted while replace-brick is in progress.
    * we attach the volume-id to the dst_brick volfile ensuring that the replace-brick
      operation holds 'claim' on it.
    
    Change-Id: If60b2af566ca940b2add600b473c99730e06ab47
    BUG: 765470
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2740
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5f002b5418b557fd03ce59fbfd5d41272bdf491a
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Feb 14 15:27:49 2012 +0530

    protocol xdr: remove 'path<>'
    
    client was sending 'path' on wire, which gets ignored on server
    side, and also doesn't get freed up, which causes memory leak.
    
    also with not having path on wire, the xdr size on wire most of the
    time can remain constant, which helps in allocating RDMA buffers.
    
    Change-Id: Ie0d36a670be60b02fd1e925c6f977b1a71def5cd
    BUG: 790298
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/2744
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 69a7f2fea23880fbdc776b657dd6aa32c643c6c4
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Feb 14 15:50:40 2012 +0530

    rpc : fix the leak with glusterfs v2 auth structure conversion
    
    both 'groups' and 'lkowner' were getting leaked after the conversion
    
    Change-Id: Iab7cc1cf5afdad18ead9f33e6ccf98e0a934a09a
    BUG: 790298
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/2746
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit b27512e006ae55777f481937d321f60fa195c48d
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Nov 16 16:23:48 2011 +0530

    locks: Added a getxattr interface to clear locks on a given inode.
    
    getxattr returns a summary of no. of inodelks/entrylks cleared.
    cmd_structure: trusted.glusterfs.clrlk.t<type>.k<kind>[.{range|basename}]
    where,
    type = "inode"| "entry"| "posix"
    kind = "granted"| "blocked" | "all"
    range = off,a-b, where a, b = 'start', 'len' from offset 'off'
    
    Change-Id: I8a771530531030a9d4268643bc6823786ccb51f2
    BUG: 789858
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2551
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 58a538e99806ae84ec4d4bf03aa726302e16d07b
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Feb 14 12:26:29 2012 +0530

    features/quota: fix a crash in fgetxattr() by checking for NULL arg
    
    'name' can be NULL in getxattr() as it is overloaded in glusterfs
    code to support listxattr() too.
    
    Change-Id: I70ccee027828e9b2b08da770f513c4edc5c7a46b
    BUG: 772601
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/2743
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit caa5db96282186333e294d93571eb49a3ed63f18
Author: shishir gowda <shishirng@gluster.com>
Date:   Sat Feb 11 18:46:10 2012 +0530

    cluster/stripe: Support for NFS anonymous fd's
    
    Moving storing of all ctx info to inode ctx. anonymous fd's do not
    have the ctx stored in them, hence readv/writev can fail.
    Open call does not need the additional lookup calls, as all the
    required fctx info will be available in the inode ctx populated
    any one of the following create/mknod/lookup
    
    Change-Id: I94ca69ff821d46ac8ed3ba1b87b97a3d1c736566
    BUG: 786095
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2726
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit b0e28fe22293b6b9811094f4048c84a8383e8c8d
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Feb 11 22:25:09 2012 +0530

    features/marker: set loc->gfid in setxattr initiated from marker.
    
    Change-Id: I7abb62272b7c8bb25ad37cbc13da7b4713924b7a
    BUG: 787151
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2736
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amarts@redhat.com>

commit 0e6df0100e13123fe38f28c5a090777e894d8f52
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Feb 6 17:49:14 2012 +0530

    core: add an extra flag to readv()/writev() API
    
    needed to implement a proper handling of open flag alterations
    using fcntl() on fd.
    
    Change-Id: Ic280d5db6f1dc0418d5c439abb8db1d3ac21ced0
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 782265
    Reviewed-on: http://review.gluster.com/2723
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit e17ac220e4bff53fb89f5bea636acb61e347cf50
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Feb 13 13:00:26 2012 +0530

    protocol: code cleanup
    
    make dict serialize and unserialization code a macro
    
    Change-Id: I459c77c6c1f54118c6c94390162670f4159b9690
    BUG: 764890
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/2742
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@redhat.com>

commit 635f3bc0f8a05ad1280f8ab7d55181502bcad700
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Feb 9 15:57:51 2012 -0500

    Fix case where we free a definitely-NULL iobuf
    
    Change-Id: I7097386b41c8881f875c9cc3e41354df5c904dea
    BUG: 789118
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/2732
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 18a5e19b62ff675aaa187fe53bd5cfa6d5945ef4
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Jan 16 14:04:10 2012 +0530

    core: log xlator options in init
    
    * The options (default as well as explicitly set)
      for each xlator are logged at DEBUG log-level
    
    Change-Id: I757e206bf06ef5dc60a3255e2377a821c284b6f1
    BUG: 767087
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2647
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b71c572df106f33cda0e4b90f174f6426f598741
Author: krishna <ksriniva@redhat.com>
Date:   Thu Feb 9 12:08:07 2012 +0530

    support for nano second resolution for mtime,ctime,atime attributes.
    
    Change-Id: Id5078f270d0fec280b53d4aa7b16bbaf42a2df05
    BUG: 784095
    Signed-off-by: krishna <ksriniva@redhat.com>
    Reviewed-on: http://review.gluster.com/2730
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f47558fc72bcb6d786b117061add384f9f6aa6d5
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Feb 8 16:36:22 2012 -0500

    Use /dev/zero instead of /dev/urandom to get realistic numbers.
    
    Change-Id: I460a03759b3e450765758e456f0b4f514ca934ae
    BUG: 788716
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/2728
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 8e81cbacc53adc77bc4eabb5a26d6d13012f5f86
Author: Anand Avati <avati@redhat.com>
Date:   Mon Jan 30 15:03:56 2012 +0530

    fuse: fix resolver to handle graph switches properly
    
    perform resolution on the latest graph by caching it in state->itable
    and use fuse_nodeid as just a hint to the possible final resolved inode
    (in case it was resolved off the latest graph). GFID is the primary key
    for resolving inodes on the latest graph.
    
    Change-Id: I3921c6f59c9ff80e4ff076bec3bd334423fc36cc
    BUG: 785675
    Reviewed-on: http://review.gluster.com/2703
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit aec6d5d89249868dc99d8fb432d8ab120bb38ef1
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jan 5 02:01:00 2012 +0100

    geo-rep: gsyncd: fix up fallback xtime for orphans on master side
    
    Change-Id: I2fa543b4bd317e06ea621ae968300ffb7223a68a
    BUG: 771787
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Reviewed-on: http://review.gluster.com/2580
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f4db9775655b24b9896ad697c534caec8868562d
Author: Kaushik BV <kbudiger@redhat.com>
Date:   Fri Jan 20 11:47:54 2012 +0530

    nfs: export-dir option changed to type GF_OPTION_TYPE_PATH
    
    Change-Id: Ica47482cfed794d6923047db859191462919d6fe
    BUG: 782424
    Signed-off-by: Kaushik BV <kbudiger@redhat.com>
    Reviewed-on: http://review.gluster.com/2667
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a4818cef9838ed3b1a270f395b4cce9551532927
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Feb 6 15:12:51 2012 +0530

    glusterd: Initialised op_sm/friend_sm before cluster restore.
    
    Cleaned up peerinfo/rpc association.
    
    Change-Id: I11bcaa3ea1f2b86c6b4e235873a60bb5bf76a892
    BUG: 786006
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2725
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 0272f7de41fa529f51bc69fdaf694c77b47250f2
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 3 13:54:02 2012 +0530

    protocol/client: assign the right value to 'conf' before de-refing it
    
    variable assignment was done after it was actually getting de-referenced.
    moved the assignment few lines up.
    
    Change-Id: Id65e3e2d3dfe071e1c5b14c32488647070398ae4
    BUG: 787117
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/2712
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 1969ef17591342af2148d3a740b368f8cc6f8d5d
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Feb 1 15:52:36 2012 +0530

    mount/fuse: check for existence of volfiles
    
    If glusterd is not running in the client host and/or
    if there are no volume created yet, this patch ensures
    that appropriate error message is displayed
    
    Change-Id: I15d23a45d70aa27bbdd42f435fe705b14c779e3f
    BUG: 786077
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2708
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b708b18b833d1f2ba4da394884bc762a821ff56b
Author: Kaushal M <kaushal@gluster.com>
Date:   Tue Aug 23 12:23:53 2011 +0530

    cli, protocol/server : improve validation for the option auth.(allow/reject)
    
    cli now checks validity of address list given for 'volume set auth.*'
    
    Server xlator checks addresses supplied to auth.(allow/reject) option
    including wildcards for correctness in case volfile is manually edited.
    
    Original patch done by shylesh@gluster.com
    Original patch  is at http://patches.gluster.com/patch/7566/
    
    Change-Id: Icf52d6eeef64d6632b15aa90a379fadacdf74fef
    BUG: 764197
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/306
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1d77fe2458be6dc567435dc59bb94870cd0fe529
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Jan 9 15:43:10 2012 +0530

    glusterd/quota: inform the user if some quota command is executed without enabling it
    
    Change-Id: I676e52b0e0a9a6868eaa56d0309faa264e6e73be
    BUG: 771639
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2609
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5ebc522717ef891c138307d02dcbc0bc1e9017f8
Author: Kaushik BV <kbudiger@redhat.com>
Date:   Mon Jan 30 19:17:12 2012 +0530

    read-ahead: add performance.read-ahead--page-count option to 'volume set' framework
    
    Change-Id: I727be1ae2e3da1816afa52fc9555269aa07c39c1
    BUG: 783379
    Signed-off-by: Kaushik BV <kbudiger@redhat.com>
    Reviewed-on: http://review.gluster.com/2700
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9636f5b16c1847bc94d42ca6ac948c680bd55f2e
Author: Kaushik BV <kbudiger@redhat.com>
Date:   Fri Jan 20 11:54:21 2012 +0530

    extras: create PID file for glusterd when started from init scripts
    
    thanks to Jaroslav Pulchart (jaroslav.pulchart@centrum.cz) for the patch
    
    Change-Id: Id07bf50536c8638f790f06e6e5994f85555c3978
    BUG: 771221
    Signed-off-by: Kaushik BV <kbudiger@redhat.com>
    Reviewed-on: http://review.gluster.com/2668
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7d81a11e661654394e116af52f0cab3d400ee2cf
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Jan 21 20:05:55 2012 +0530

    extras/test: add a test file to test 'f-fops'.
    
    mainly to test f*xattr(), fchown()/fchmod()/ftruncate() on fuse
    mounts.
    
    Change-Id: I59edbe172f307a2ba94f11c650ac0176fd35564f
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 766571
    Reviewed-on: http://review.gluster.com/2692
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 08041c321229bdfb2cbe1b638fb4fabb0b9da013
Author: Kaushal M <kaushal@gluster.com>
Date:   Mon Sep 12 15:14:26 2011 +0530

    protocol/client : prevent client from reconnecting when server
    authentication fails
    
    This prevents the client from trying to reconnect on server
    authentication failure. Reconnecting on authentcation failure causes hung
    mounts on unauthorised clients. This patch fixes this problem.
    
    Also, mount.glusterfs script unmounts mount-point on mount failure to
    prevent hung mounts.
    
    Change-Id: I5615074d27948077bad491a38cecae1b7f5159fb
    BUG: 765240
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/398
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 3ec7680a70bcace6b195ae412362b7e1b072eaeb
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Jan 11 15:39:38 2012 +0530

    glusterd: Changed op_sm_queue locking mechanism to accomodate nested calls to op_sm
    
    Today if an rpc call made inside an op_sm can fail due to a disconnected peer,
    resulting in the rpc callback to be called in the same stack with appropriate
    status set. All glusterd rpc cbks move the state machine based on the status
    returned by the rpc layer, which would result in a nested call to op_sm. With
    the current scheme of locking, glusterd would end up in a deadlock situation
    
    The new scheme will fail the nested glusterd_op_sm (). This prevents the
    deadlock.  It would work without any change in overall behaviour, as the
    current op_sm () call in execution wouldn't return until all events in the
    queue are processed.
    
    Change-Id: I6a7ba16d3810b699bcd06dc28a5ff3205a25476f
    BUG: 772142
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2625
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2313600f0749094f1246e663a0db15da3c2812db
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Jan 6 12:18:35 2012 +0530

    glusterd: Improved err msgs for add_brick
    
    Change-Id: I4b97d7e26b8c81ed52657467981be0c4adc291ae
    BUG: 772145
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2589
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 83a3daf7c205f119169eb2d7091432de05b1861c
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Dec 16 18:27:52 2011 +0530

    distribute: utilize new 'fremovexattr()' fop for rebalance
    
    instead of existing 'syncop_removexattr()' which is not rename proof
    for now.
    
    Change-Id: Ib171710645a6ee35c86d851a057b68461ecbab27
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 766571
    Reviewed-on: http://review.gluster.com/2691
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3c0c468640ccd020a585c9f19366f857ee78d013
Author: M S Vishwanath Bhat <vishwanath@gluster.com>
Date:   Tue Jan 31 01:32:50 2012 +0530

    removing the dead code in cli-rpc-ops.c
    
    Change-Id: Ie80b7938944a5984e4d9cd0a5f52b7976030ea73
    BUG: 783972
    Signed-off-by: M S Vishwanath Bhat <vishwanath@gluster.com>
    Reviewed-on: http://review.gluster.com/2701
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 698c0750e5b93fb9aa842a1d70def9ecfa6da41c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Feb 1 22:35:55 2012 +0530

    performanc/stat-prefetch: check if loc->gfid is present before checking loc->name
    
    After gfid based backend changes loc will either contain the gfid of the inode
    or it will contain the parent gfid and the name of the entry. So before unwinding
    when loc->name is not there we have to check if loc->gfid is present or not.
    If loc->gfid is null and loc->name is also NULL, then unwind with the error.
    
    Change-Id: If88b9462bde09a80e79f27899c995605697ce453
    BUG: 785675
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2710
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 52c13660eec1dd38f71e7119b319209f8cfd84e8
Author: Csaba Henk <csaba@redhat.com>
Date:   Tue Jan 24 18:28:22 2012 +0100

    Revert "mgmt/glusterd: Allow insecure ports by default"
    
    This reverts commit f6e0e614fbd07a57de44f0d16c304d01d1a5b269.
    
    Conflicts:
    
    	xlators/mgmt/glusterd/src/glusterd.c
    
    Change-Id: I1da429e4b8c3f8c67367b173aa11dbe2b0435046
    BUG: 781256
    Signed-off-by: Csaba Henk <csaba@redhat.com>
    Reviewed-on: http://review.gluster.com/2695
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b1a884aae98927d847085c9794f8b4aa8bebf838
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Jan 30 19:34:03 2012 +0530

    features/marker,quota: Incorporate changes to support nameless lookup
    
    Change-Id: Ic5f00a9891bd835ebee5a3e103ef0f75d0b7fc25
    BUG: 783925
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2702
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit c3aa99d907591f72b6302287b9b8899514fb52f1
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Jan 19 17:49:42 2012 -0500

    Fix race between read-ahead and write.
    
    Change-Id: I0ed1aca585733302b5e3840f392849e12f0b0f0d
    BUG: 783313
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/2666
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 20d74c540879d3994d56b9baf7044c79ae5df5e3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Jan 29 16:17:21 2012 +0530

    storage/posix: Fix rename gfid handle unset
    
    Change-Id: I365ef264056691914ad5bd620d8150f8b71ec887
    BUG: 785524
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2698
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 21bad6eb3a3c48ad3edc37927aeabcd3de8b9d64
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Jan 29 16:09:29 2012 +0530

    storage/posix: janitor should unset gfid handles
    
    Change-Id: I449b6a55122dfc27035569e6eb1d74ddcea68a69
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    BUG: 785522
    Reviewed-on: http://review.gluster.com/2697
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit e2303e774e1e37cd9becb672a67278502724b369
Author: Mohammed Junaid <junaid@redhat.com>
Date:   Tue Jan 24 17:12:59 2012 +0530

    features/quota: Check for error in statfs fop call back.
    
    Change-Id: Ia73d2b77dcb0507a7b8362c336c71301526aaf82
    BUG: 783927
    Signed-off-by: Mohammed Junaid <junaid@redhat.com>
    Reviewed-on: http://review.gluster.com/2685
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e99cb60af1e153efd616014da6a54d2f95c119d1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jan 4 00:08:14 2012 +0530

    glusterd: provide option to take statedump of the nfs server
    
    Currently the cli command for taking statedump is for glusterfs servers
    only. Statedump of nfs server cannot be taken. With this patch if one
    gives nfs as an option to the statedump command, then the nfs-server's
    statedump is taken.
    
    Change-Id: I4ef7a68e608da4aa2f17541d7b42cd78ce2624b6
    BUG: 771587
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2579
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5a8c58cf6e6c993c8665a31e6f108744ca27ccf4
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Nov 3 15:16:18 2011 +0530

    glusterd: Refactored rb subcmds code and fixed some minor issues.
    
    Change-Id: I680a1c8f01883433d4cd1ed51723acebd8fe9245
    BUG: 765441
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2689
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 623919a78a7faac30d1f0df5793681da2c449e32
Author: Kaushal M <kaushal@redhat.com>
Date:   Sun Jan 1 15:59:28 2012 +0530

    cli: Extend "volume status" with statedump info
    
    This patch enhances and extends the "volume status" command with information
    obtained from the statedump of the bricks of volumes.
    
    Adds new status types : clients, inode, fd, mem, callpool
    The new syntax of "volume status" is,
     #gluster volume status [all|{<volname> [<brickname>]
                             [misc-details|clients|inode|fd|mem|callpool]}]
    
    Change-Id: I8d019718465bbc3de727653a839de7238f45da5c
    BUG: 765495
    Signed-off-by: Kaushal M <kaushal@redhat.com>
    Reviewed-on: http://review.gluster.com/2637
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit a078235dbede380ca695251e86a1502ca131d816
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Nov 29 18:30:39 2011 +0530

    cluster/afr: Perform xattrop with all afr-keys
    
    Self-heal does not happen if the file has change log xattr
    only for one of the subvol keys. This patch makes sure that
    xattrop is done for all the afr subvol keys after a new entry
    is created in entry-self-heal.
    
    1) Added matrix create/cleanup functions
    2) Impunging a new file does multiple xattrops on the source
    subvol, one per sink. The code can do a single xattrop after
    the entry is created on all the sinks.
    3) Missing entry self-heal uses one frame per sink to heal
    the file. This leads to multiple xattrops on the source subvol.
    That code is changed now to use one frame which will
    create the file on all subvols.
    
    Change-Id: I65a42f9779b03f7efae283479f8653fb2cb8046b
    BUG: 762680
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2503
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit d04a781d9acf328bf5f7a45d67c0d2b4cdd35311
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Jan 24 18:47:35 2012 +0530

    cluster/afr: Stack wind with correct frame
    
    *) Found possible races in _cbk fixed them as well.
    
    Change-Id: Id9a9f3cbf71f55827addb24ba2cbddecb8326b5b
    BUG: 784279
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2687
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c13e3e090cc4d97dbf87a21b9de77e0b37ee5dd9
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Dec 14 13:37:36 2011 -0500

    Make volfile-save scriptlet follow .rpmsave convention.
    
    Change-Id: I7a106defcc441679cf7c48f78eea2c04feb2853e
    BUG: 764702
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/788
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6b0cd9fc8450029449f7c320a2e5d766e87ac8d4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Jan 26 16:11:02 2012 +0530

    protocol/client: Pass the right arguments to CLIENT_GET_REMOTE_FD
    
    Change-Id: I04f984f20964650a38009bba7711d2757151ade5
    BUG: 762935
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2694
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit cf57b7b517af68c56fb8d4c229e2988c306384c4
Author: Harshavardhana <fharshav@redhat.com>
Date:   Mon Jan 9 17:15:23 2012 -0800

    common-utils: Add support for solaris, bsd and mac os/x
    
    get_mem_size() is more standardized now.
    
    Change-Id: I8e3dc29df0a64a5eb8eea4fd3965b268cb1a85c2
    BUG: 772808
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/2618
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e8c722ba2832e4d0cae6ba3d043e5f06aaadbacd
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Wed Jan 25 07:01:48 2012 -0500

    Add format/printf/attribute to log decls
    
    This enables compile-time checking of printf-style format checking
    
    Reason for doing it this way: N/A
    
    Description of test cases: N/A
    
    Change-Id: I9e26a5dceef5b545b9434b1d418c3d1193b4ef9a
    Signed-off-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/2693
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ef1f9cfbaeb62fbabfcc175dc643baa125b393bb
Author: Venky Shankar <vshankar@redhat.com>
Date:   Tue Jan 24 10:52:00 2012 +0530

    geo-rep: gsyncd: Python3 compat fixes
    
    Change-Id: I2eef82faab3eed1189e3786a5dca296773e1caa0
    BUG: 784498
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/2690
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Csaba Henk <csaba@redhat.com>

commit fd61cd598b70fbc9442350483a3777d77990d257
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Jan 24 15:53:52 2012 +0530

    protocol/client: if the remote_fd is -1, then unwind instead of sending the call to server
    
    For calls with remote_fd set to -1, client xlator is sending the call to the
    server which results in server not resolving it and thus fd being NULL. Locks
    xlator when tries to get the inode context using the fd it segfaults. To avoid
    it unwind the call in the client xlator if the remote_fd is -1.
    
    Change-Id: Ic34a49fdf1012dd371f4b194703c0be74f29bda2
    BUG: 784187
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2684
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit e98752525706fd6d9989367eb84f1a7fc1b81fa4
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Dec 23 10:00:28 2011 +0530

    protocol: allow extra data in all the 'fops' over wire
    
    Change-Id: I3920c68b5b317fc4a4acfd26d64d900bf7bd59d1
    BUG: 782265
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/2511
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 49c325d949b2df06572df7dd3825735fb9c8cd6f
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Jan 21 20:05:55 2012 +0530

    complete the implementation of missing 'f**xattr()' fops
    
    in debug/* and cluster/* translators and a syncop_fsetxattr()
    
    added a test case for testing the working of 'f-fop()' on
    fuse mount.
    
    Change-Id: I0c2aeeb30a0fb382ef2495cca1e66b00abaffd35
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 766571
    Reviewed-on: http://review.gluster.com/802
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit d7ecaaa1ed0f88869812ea17cb64a102a74c8c1c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jan 17 05:57:24 2012 +0530

    core: add 'fremovexattr()' fop
    
    so operations can be done on fd for extended attribute removal
    
    Change-Id: Ie026f1b53793aeb4ae33e96ea5408c7a97f34bf6
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 766571
    Reviewed-on: http://review.gluster.com/778
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 6c54022f1b1c7f5f458f6a7e783203d11e7f89b5
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Jan 5 15:38:32 2012 +0530

    cluster/dht: handle ENOENT err in rename fop
    
    A ENOENT should not be a error propogated for rename failures.
    As, ENOENT can arise only due to internal unlink call of rename.
    
    Change-Id: I925622da8ef370d0385bc5b30cf8dc9b8e852beb
    BUG: 768879
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/2583
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit cf8486cbef329ef66868f658fa35f470f97db462
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jan 18 18:06:44 2012 +0530

    core: get xattrs also as part of readdirp
    
    readdirp_req() call sends a dict_t * as an argument, which
    contains all the xattr keys for which the entries got in
    readdirp_rsp() are having xattr value filled dictionary.
    
    Change-Id: I8b7e1290740ea3e884e67d19156ce849227167c0
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 765785
    Reviewed-on: http://review.gluster.com/771
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit b02afc6d008f9959db28244eb2b9dd3b9ef92393
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jan 17 05:28:51 2012 +0530

    core: change lk-owner as a 1k buffer
    
    so, NLM can send the lk-owner field directly to the locks translators,
    while doing the same effort, also enabled sending maximum of 500 aux gid
    over protocol.
    
    Change-Id: I87c2514392748416f7ffe21d5154faad2e413969
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 767229
    Reviewed-on: http://review.gluster.com/779
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 0694749c3e5039be327110a64dd66619b5d9121c
Author: Shylesh Kumar <shylesh@gluster.com>
Date:   Tue Jan 24 12:14:36 2012 +0530

    cluster/afr: set loc->gfid for building root loc
    
    Change-Id: Icb902846d243df0502f664bfd187280cecd4397c
    BUG: 784176
    Signed-off-by: Shylesh Kumar <shylesh@gluster.com>
    Reviewed-on: http://review.gluster.com/2681
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e04d45facc722d944d51439f4ae57b2af2a03d3e
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Jan 24 12:03:56 2012 +0530

    glusterd: fix transpose of memset arguments
    
    a fix for transposed arguments to memset in glusterd_get_all_volnames
    function introduced in volume status enhancement.
    
    Change-Id: Iaea60c7d19b23992684f91b016b0841e2153b0a9
    BUG: 765464
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2680
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit aecc9f52647e0ebc89cc5ca56a9f5182b7feb594
Author: Harshavardhana <fharshav@redhat.com>
Date:   Mon Jan 23 13:20:04 2012 -0800

    Revert "distribute: utilize new 'fremovexattr()' fop for rebalance"
    
    This reverts commit c4e4be31ec2783b984e7dbb9ecbc1eea84044ad0 ..
    
    There is a problem here. syncop_fremovexattr doesn't exist in the codebase yet. Have a dependency merge for this. No other patches can be uploaded without a build failure now.
    
    Change-Id: Ic2c6194d905ffcfa7cbdc29c9bc8739f628d404e
    Reviewed-on: http://review.gluster.com/2679
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 54b8d503dd23e72ed3076988c52e689f3554ebc8
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Thu Jan 19 18:09:34 2012 +0530

    pump: move internal pump xattrs out of trusted domain
    
    * the trusted.glusterfs.pump.{start|pause|commit|status|abort} xattrs
      have been moved out of trusted domain. This enables separation of
      xattrs used as gluster-internal commands (handled by pump) for
      replace-brick, which are not set in the back-end, from xattrs set
      on the replace-brick source and destinations bricks.
    
    * macros definitions from pump.h and glusterd.h, #defining these xattrs
      have been merged and put into libglusterfs/src/glusterfs.h
    
    Change-Id: I87b8bfbf045aa140f5d3f0c9baa9b2e79f87b67b
    BUG: 783049
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2663
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4e2a26eb285de9e0a5836ad5e2edbc14eb9adc80
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Dec 16 18:27:52 2011 +0530

    distribute: utilize new 'fremovexattr()' fop for rebalance
    
    instead of existing 'syncop_removexattr()' which is not rename proof
    for now.
    
    Change-Id: I3b2afbe58ce90658100cc56b01e23bed672854e8
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    BUG: 766571
    Reviewed-on: http://review.gluster.com/803
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 366c98afe6d8ec1e69d33baad5e914fa3229f2a1
Author: root <shishirng@gluster.com>
Date:   Mon Jan 23 14:32:31 2012 +0530

    storage/posix: Pass correct size to sys_lgetxattr
    
    We were passing op_ret (0), instead of size variable obtained by previous
    sys_lgetxattr to determine the  size
    
    Signed-off-by: root <shishirng@gluster.com>
    Change-Id: I886dedc2ab752ac1feabe7a79725ea5f069d6865
    BUG: 783916
    Reviewed-on: http://review.gluster.com/2676
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 4e92c58d27b5cea9d7346d6dd88be9b3479c9e3b
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Jan 13 06:12:11 2012 +0100

    rpc: extend actors with flag signing if privilege is required
    
    Currently we allow the following RPC messages for unprivileged users:
    GLUSTER_CLI_GETWD, GLUSTER_CLI_MOUNT, GLUSTER_CLI_UMOUNT
    
    Change-Id: I05414f3ca7cbe47de45c5e5cfba1537efc774e6c
    BUG: 781256
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Reviewed-on: http://review.gluster.com/2641
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit d3ca9f05ec3a9881b5aeadb7b61cfcb97dbdb718
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Jan 13 06:05:34 2012 +0100

    cli: exit with error if connection problem occurs
    
    Change-Id: I97fc4d0a260120810b71dd5d9957a269d4550a3b
    BUG: 781256
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Reviewed-on: http://review.gluster.com/2640
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit bb1e07b7f42e7db415527852e98fcc1cbf2e1285
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jan 13 23:17:07 2012 +0530

    nfs: changes for using nameless lookup and anonymous FDs
    
    - Use gfid to create filehandle instead of encoding path components
    - Utilize nameless lookups of GFID for deep resolution instead of
      crawling the namespace with component hints
    - Use anonymous FDs for file based operations
    - Do away with fdcaching code for files and dirs
    
    Change-Id: Ic48fb23370b25d183f7e1fc1cc5dffa9d5bab3fb
    BUG: 781318
    Reviewed-on: http://review.gluster.com/2645
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 7e1f8e3bac201f88e2d9ef62fc69a044716dfced
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jan 13 13:27:15 2012 +0530

    core: GFID filehandle based backend and anonymous FDs
    
    1. What
    --------
    This change introduces an infrastructure change in the filesystem
    which lets filesystem operation address objects (inodes) just by its
    GFID. Thus far GFID has been a unique identifier of a user-visible
    inode. But in terms of addressability the only mechanism thus far has
    been the backend filesystem path, which could be derived from the
    GFID only if it was cached in the inode table along with the entire set
    of dentry ancestry leading up to the root.
    
    This change essentially decouples addressability from the namespace. It
    is no more necessary to be aware of the parent directory to address a
    file or directory.
    
    2. Why
    -------
    The biggest use case for such a feature is NFS for generating
    persistent filehandles. So far the technique for generating filehandles
    in NFS has been to encode path components so that the appropriate
    inode_t can be repopulated into the inode table by means of a recursive
    lookup of each component top-down.
    
    Another use case is the ability to perform more intelligent self-healing
    and rebalancing of inodes with hardlinks and also to detect renames.
    
    A derived feature from GFID filehandles is anonymous FDs. An anonymous FD
    is an internal USABLE "fd_t" which does not map to a user opened file
    descriptor or to an internal ->open()'d fd. The ability to address a file
    by the GFID eliminates the need to have a persistent ->open()'d fd for the
    purpose of avoiding the namespace. This improves NFS read/write performance
    significantly eliminating open/close calls and also fixes some of today's
    limitations (like keeping an FD open longer than necessary resulting
    in disk space leakage)
    
    3. How
    -------
    
    At each storage/posix translator level, every file is hardlinked inside
    a hidden .glusterfs directory (under the top level export) with the name
    as the ascii-encoded standard UUID format string. For reasons of performance
    and scalability there is a two-tier classification of those hardlinks
    under directories with the initial parts of the UUID string as the directory
    names.
    
    For directories (which cannot be hardlinked), the approach is to use a symlink
    which dereferences the parent GFID path along with basename of the directory.
    The parent GFID dereference will in turn be a dereference of the grandparent
    with the parent's basename, and so on recursively up to the root export.
    
    4. Development
    ---------------
    
    4a. To leverage the ability to address an inode by its GFID, the technique is
    to perform a "nameless lookup". This means, to populate a loc_t structure as:
    
    loc_t {
       pargfid: NULL
       parent: NULL
       name: NULL
       path: NULL
       gfid: GFID to be looked up [out parameter]
       inode: inode_new () result [in parameter]
    }
    
    and performing such lookup will return in its callback an inode_t
    populated with the right contexts and a struct iatt which can be
    used to perform an inode_link () on the inode (without a parent and
    basename). The inode will now be hashed and linked in the inode table
    and findable via inode_find().
    
    A fundamental change moving forward is that the primary fields in a
    loc_t structure are now going to be (pargfid, name) and (gfid) depending
    on the kind of FOP. So far path had been the primary field for operations.
    The remaining fields only serve as hints/helpers.
    
    4b. If read/write is to be performed on an inode_t, the approach so far
    has been to: fd_create(), STACK_WIND(open, fd), fd_bind (in callback) and
    then perform STACK_WIND(read, fd) etc. With anonymous fds now you can do
    fd_anonymous (inode), STACK_WIND (read, fd). This results in great boost
    in performance in the inbuilt NFS server.
    
    5. Misc
    -------
    The inode_ctx_put[2] has been renamed to inode_ctx_set[2] to be consistent
    with the rest of the codebase.
    
    Change-Id: Ie4629edf6bd32a595f4d7f01e90c0a01f16fb12f
    BUG: 781318
    Reviewed-on: http://review.gluster.com/669
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 33c568ce1a28c1739f095611b40b7acf40e4e6df
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Jan 18 13:59:32 2012 +0530

    glusterd: Fixed crash in stop volume found using efence.
    
    Change-Id: I84d38b8af248920a1559d05f0e4f43d3eda0f43e
    BUG: 782710
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2651
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 9b389a3f76bc858f95e498c1539317c7a8bc6188
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Jan 19 11:41:55 2012 +0530

    cluster/afr: do not unlock without holding the lock on the fd
    
    In afr_open_fd_fix we were unlocking the local->fd->lock, without
    holding the lock on it if we were not able to get the fd context.
    Now we are directly going to out and returning, instead of going
    to unlock without holding the lock.
    
    Change-Id: I0da638bbd2c269127cf111b3aac707e4a95d20c6
    BUG: 783036
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2658
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 6481f062b8ad0f47fa7715f78b7bf61623d1dc9a
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Jan 17 11:54:20 2012 +0530

    cli: trivial changes in cli-rpc-ops.c
    
    * the get_volume_cbk has been cleaned up(w.r.t whitespace) and a memset
      used where appropriate. some other functions have been
      affected(in a good way) by the whitespace-dealing commands in emacs.
    
    Change-Id: Iba473290e87747f8bb06d335db06c872a241d7cd
    BUG: 781333
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2653
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3169891538331a8a0e954010c5dac8360997da12
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Jan 18 15:16:48 2012 +0530

    glusterd: Fixed crash in peer probe found using efence
    
    Change-Id: Ie09d1e4eb9a8d338f8e5cf6360b398b196141a81
    BUG: 782718
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2655
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 36cedb338ec1d021e189379f30100f0d983e3e01
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Dec 6 11:35:33 2011 +0530

    core/setxattr: prevent users from setting glusterfs xattrs
    
    * Each xlator prevents the user from setting glusterfs-internal
    xattrs like trusted.gfid by handling it in respective setxattr
    functions. The speacial case of trusted.gfid is handled in
    fuse (Not in posix because posix_setxattr is used to set gfid).
    
    * For xlators which did not define setxattr and/or fsetxattr,
    the functions have been implemented with appropriate checks.
    
    xlator         |     fops-added
    _______________|__________________________
                   |
    1. afr         |     fsetxattr
    2. stripe      |     setxatrr and fsetxattr
    3. quota       |     setxattr and fsetxattr
    
    Change-Id: Ib62abb7067415b23a708002f884d30e8866fbf48
    BUG: 765487
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/685
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 4e76cea78b11e9290b16c2faa85cf81b8e32b7ea
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jan 7 16:10:06 2012 +0000

    trivial: gluster_pmap_actors should only use GF_PMAP_* procedures
    
    GF_HNDSK_NULL is not suitable for gluster_pmap_actors, instead use
    GF_PMAP_NULL. The actual value (0) is not different for these, so there
    is no fuctional change.
    
    Change-Id: Ibb998ebae88b457c57a42ce63dad095d2d4a22c5
    BUG: 772468
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/2603
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 3007bdddb1cae3d2b036ebddfc76ca6f6e06a184
Author: Kaleb KEITHLEY <kkeithle@redhat.com>
Date:   Mon Jan 9 12:32:46 2012 -0500

    don't try to get ngroups from /proc on non-Linux systems
    
    Emmanual Dreyfus abandoned his changes, seemingly because he couldn't
    get rfc.sh to correctly generate his changed patch set. Since Mac OS
    is an important port, I suggest we keep this change alive. (This
    change also works on the other BSDs too)
    
    Now with added Solaris support
    
    BUG: 764655
    Change-Id: I6a9ab7383777f9a09ab5c9a6914f45eee43461fb
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
    Reviewed-on: http://review.gluster.com/2617
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 0e1679aee746040cdd509c5cd4004a4641c4c203
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Jan 13 18:21:39 2012 +0530

    cli,glusterd: Display volume UUID in the output of 'volume info'
    
    Cleaned up some leaks along the way.
    
    Change-Id: Ibc76c539eee935c0630f9580d0d914814b1a6fe1
    BUG: 781445
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2643
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit faf9099bb50d4d2c1a9fe8d3232d541b3f68bc58
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Jan 3 16:05:51 2012 -0800

    cluster/distribute: dht_aggregate() fix a logic error before xattr comparisons
    
    Change-Id: I20f015263bed9851225005d5f41a5d518bd22592
    BUG: 769691
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/2557
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 718a2744076ff21d19c0e9b2cadac5b975a3f6a9
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Jan 7 22:05:11 2012 +0000

    trivial: correctly document that GLUSTER_CLI_VERSION=2 matches version 0.0.2
    
    Change-Id: I0d7eb0ac67ad83e5f21b60cc2acc514ac602ea42
    BUG: 772469
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/2604
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit cf944c8ad5da87bce15b08d0bbb2ecd62e553d86
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Fri Jan 6 16:02:55 2012 +0530

    glusterd: prevent adding bricks already in use
    
    The add-brick command now checks if the brick provided for
    add-brick is used in any volumes, even if the volume was
    never started by looping through the brick lists of all
    volumes.
    
    Change-Id: I15035d41d91386448a3e3d4063d909b880288681
    BUG: 771831
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2607
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit bfd429e583f50a4f4712de88dc0a15baadebbf9b
Author: Harshavardhana <fharshav@redhat.com>
Date:   Wed Jan 11 12:24:38 2012 -0800

    common-utils: Cleanup old stuff and standardize
    
    Change-Id: If15058c3a1cc4070d1ebbabe37e012a70353310e
    BUG: 769691
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/2635
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3207a33ef67ed0d065935360adb309a7ae046317
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Dec 27 15:09:39 2011 +0530

    glusterd: improve replace brick status message
    
    when replace-brick status is invoked without starting
    replace brick on the specified bricks, appropriate error
    message is displayed
    
    Change-Id: I57230db84314caf807f1ff54f74307d85bdc1633
    BUG: 769926
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2531
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 919e3424849db2276e003dcd919a470838bf084f
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Mon Dec 19 23:40:11 2011 +0100

    posix-acl: properly process umask in case client sent it
    
    FUSE used to interpret the umask itself. That was a bad idea, since
    there are cases where umask is not applied, such as when extended POSIX
    ACLs are present and default ACLs are set on parent directory.
    
    The FUSE bridge was changed to send original mode with umask (alongside
    masked mode, for compatibility). If that is the case, we decide whether
    to apply the umask or not in the posix-acl translator depending on
    whether a default umask is set, or not.
    
    The original, broken, behavior is preserved in following cases:
    * Unpatched client (not sending umask with original mode)
    * Unpatched server (not understanding umask with original mode)
    * Old FUSE on client side (FUSE < 7.12 or linux < 2.6.31)
      (can not find out the umask and original mode)
    
    Change-Id: I2e3bfc4c7c9611bc51119ca5c8e28f6582677516
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Tested-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    BUG: 765508
    Reviewed-on: http://review.gluster.com/668
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 8a78d969ee8b7c284751364d72496eec84c7290b
Author: Lubomir Rintel <lubo.rintel@gooddata.com>
Date:   Thu Nov 3 08:51:50 2011 +0100

    fuse-bridge: preserve original mode and umask
    
    FUSE used to interpret the umask itself. That was a bad idea, since
    there are cases where umask is not applied, such as when extended POSIX
    ACLs are present and default ACLs are set on parent directory.
    
    Thus, FUSE was changed to pass umask to operation handler itself in case
    the fuse server is initialized with FUSE_DONT_MASK. In case FUSE
    supports it, gluster client sends mode unmasked and umask separately (
    masked mode is still sent, for compatibility with old servers).
    the mode as-is for compatibility with older clients.
    
    Change-Id: I55862b39a25261446f18ba0b3c03f85b41c4d722
    Signed-off-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    Tested-by: Lubomir Rintel <lubo.rintel@gooddata.com>
    BUG: 765508
    Reviewed-on: http://review.gluster.com/667
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 169c73f28dae61236de54889edcaa8236d91da59
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Dec 7 20:51:03 2011 +0530

    cli: volume status enhancement
    
        * Support "gluster volume status (all)" option to display all
          volumes' status.
    
        * On option "detail" appended to "gluster volume status *",
          amount of storage free, total storage, and backend filesystem
          details like inode size, inode count, free inodes, fs type,
          device name of each brick is displayed.
    
        * One can also obtain [detailed]status of only one brick.
    
        * Format of the enhanced volume status command is:
          "gluster volume status [all|<vol>] [<brick>] [detail]"
    
        * Some generic functions have been added to common-utils:
    
               skipword
               get_nth_word
          These functions enable parsing and fetching
          of words in a sentence.
    
               glusterd_get_brick_root    (in glusterd)
          These are self explanatory.
    
    Change-Id: I6f40c1e19810f8504cd3b1786207364053d82e28
    BUG: 765464
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/777
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 4e40a7e48757feedc959c7982acf05c73f739a15
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jan 11 10:38:45 2012 +0530

    mount/fuse: Fix memory leaks
    
    Change-Id: Iff10650dc8234f9d8ca0472f2e1ea9c60fbd6d4e
    BUG: 773211
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2630
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 984de558a959854ddb4042f2fb3d47508883b788
Author: Anand Avati <avati@gluster.com>
Date:   Thu Dec 8 11:08:48 2011 +0530

    core/stack: perform locked winds
    
    In configurations like pump, where there is a cluster translator on
    top of io-threads, there are situations where two concurrent stack-winds
    can be performed on the same call stack in multiple threads. This patch
    holds locks during the call frame list manipulation
    
    Change-Id: I51539210dc8101f7a80cf9bc103b5eff0c86dc9f
    BUG: 765522
    Reviewed-on: http://review.gluster.com/774
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 836c5f0075e83816d00003da440d5c728aefb93e
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Jan 9 17:03:21 2012 +0530

    cli: Corrected replace-brick error messages and usage string.
    
    Change-Id: I2739529ca572fd762fbbed27de9e433e8c5b1f81
    BUG: 772583
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2613
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 979e12f16b57cbb848fb9096d673dc58ed9b67a4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jan 9 19:48:44 2012 +0530

    cluster/afr: Remove dead code
    
    Change-Id: I239128c51b728fbb7814fd6a41020b76c88fbd93
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    BUG: 772876
    Reviewed-on: http://review.gluster.com/2623
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5303f98f674ab5cb600dde0394ff7ddd5ba3c98a
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Mon Dec 26 14:39:24 2011 +0530

    extras: add check for brick path existence
    
    Adding a couple of checks to validate brick path(s)
    
    Change-Id: I2d8538add21407d9457542373b528c2a02cd7eb6
    BUG: 765572
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2514
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 22282b4fb82b83621c15773c4c44ff3d28a82e3c
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Wed Jan 4 13:06:29 2012 +0530

    lib/mount-broker: move utility functions to common-utils
    
    functions skipwhite and nwstrtail have been moved from
    mount-broker to common-utils library for general use.
    
    Change-Id: I9cfefb28bbfcf5d0bd37e35865ff3f3b7923fc53
    BUG: 765464
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/2560
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>

commit ea275f8cfe8abf5877f67b21afb2c1e6e08f06b7
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Jan 5 11:21:25 2012 +0530

    glusterd: Fixed add-brick error message.
    
    Change-Id: I9260d5a0203ae2990d37b30bcc7c94c81c1e168e
    BUG: 770678
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2581
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit c66ced7d876c8c96561724901be52a0a8afd4baa
Author: Junaid <junaid@gluster.com>
Date:   Wed Jan 4 12:46:53 2012 +0530

    features/marker: xtime should not be updated for modifications done by special client.
    
    Change-Id: Ia577422dedb94a1febeceb2a50cabf61d48cb714
    BUG: 769494
    Signed-off-by: Junaid <junaid@gluster.com>
    Reviewed-on: http://review.gluster.com/2559
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>

commit 0a4ac033095c0675c90abc353736f388873291c0
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Jan 4 19:05:18 2012 +0530

    glusterd: Added checks for remove-brick handler.
    
    Removing bricks in a plain stripe-replicate is failed
    if replica count is not reduced explicitly.
    
    Change-Id: I6d0de4862595744d1d1998b9a287c34c53d7fe5f
    BUG: 770561
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2577
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 60862f5916dff99c91dd6d6319c958d02cb535d8
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Jan 3 11:07:00 2012 -0800

    libglusterfs: Add boundary conditions to data_to_int8() function.
    
    Change-Id: Iff50d44568895a75fc8743a10346990f764cf8fa
    BUG: 769692
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/2556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a6777636fbb94a34a37cadd7840429f72fc5b747
Author: Rahul C S <rahulcs@redhat.com>
Date:   Tue Jan 3 22:24:22 2012 +0530

    Avoid setting dict when size is -1
    
    when lgetxattr fails and returns size as -1, we
    still try to set the dict. Instead it should set
    proper errno & exit.
    
    Change-Id: I282dc0765e562bd9bbcf852453cd3b72d918b269
    BUG: 771313
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2555
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit fb825bccca8348cbff64edb239ee0cd66942984e
Author: Venky Shankar <vshankar@redhat.com>
Date:   Sun Jan 1 23:48:15 2012 +0530

    cluster/stripe: Fix block size reported in pathinfo xattr
    
    Block size (or stripe size) is reported when request is made
    for pathinfo xattr (trusted.glusterfs.pathinfo) for a striped
    volume. When the block size is changed, the new block size is
    reported for files created with older block size. This can be
    confusing ( or even erroneous ) for applications relying on
    pathinfo xattr to find chunks in backend.
    
    Change-Id: I79cb6721bbd33f44c3fada4dd52e459d2c128e24
    BUG: 766530
    Signed-off-by: Venky Shankar <vshankar@redhat.com>
    Reviewed-on: http://review.gluster.com/2545
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 29b9b0c72809456b1ba334a40adc1ed9929eca91
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Jan 2 18:40:31 2012 +0530

    glusterd: Fixed add-brick handler algorithm.
    
    In the fix for 765774, setting the op dictionary with modified stripe
    and replica count was (accidentally) removed affecting the correctness.
    The stage and op functions of add-brick rely on the fact that stripe/replica
    count are zero if there is no change in them during the add-brick operation.
    
    Change-Id: I55a23878e618b355009ffd0fce8c4904dbb70691
    BUG: 770914
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/2548
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit be003fbb3ac7a1f1021774ecb75a4929f1ba85d4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Dec 15 16:51:02 2011 +0530

    cluster/afr: Handle fini for afr,pump
    
    Change-Id: Idc0a05a8a25f278a7ab05e242263e0a5001bde18
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    BUG: 767862
    Reviewed-on: http://review.gluster.com/800
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c8c0942d1c890fd9b74c8e2fb3897bc96f9b9b82
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Dec 29 11:58:21 2011 +0530

    cluster/afr: EIO should overwrite ENOENT in lookup
    
    In case if lookup decides there is a gfid-mismatch,
    some enoents and self-heal cant remove the stale entry,
    it tells lookup to unwind with EIO but since ENOENT
    has more priority it is not over-written, this patch
    fixes that case.
    
    Change-Id: Icd68c4a5cf05dd97c568964ab647a34fdb6e26f4
    BUG: 765528
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2541
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8de9cad2234109913cf090b93e77980603424e85
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Dec 23 14:57:37 2011 +0530

    mgmt/glusterd: log the rebalance command received properly in the log file
    
    Change-Id: If18d9a49f5a3442755440e08ee7a63f6c6e54c5d
    BUG: 770058
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/2500
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 145b0f5a45c600c4f84f0d85adf36035a0abce5e
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Dec 23 11:49:02 2011 +0530

    debug/io-stats: Handle fini for io-stats xlator
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I0b36a2f4836fa84ced7414fdba4d68e0cb6cac7b
    BUG: 767862
    Reviewed-on: http://review.gluster.com/2499
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 1c4098a05e8e035c4e155aebb410fe2c811ccd50
Author: Rahul C S <rahulcs@redhat.com>
Date:   Fri Dec 23 03:28:13 2011 +0530

    Added/Removed white spaces wherever necessary in replace-brick
    
    Change-Id: Ic11d04813109bc6252e4dfe754c7b4c5c74014cd
    BUG: 769985
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2498
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit d2b6d69023c954eed1031c03e0b6750bb81f52ac
Author: Harshavardhana <fharshav@redhat.com>
Date:   Fri Dec 2 16:57:22 2011 -0800

    mount/fuse:  Cleanup / remove unnecessary comments
    
    Change-Id: If236e82c2e89d2ab4a0e3278319976aeb9fc05a6
    BUG: 769691
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/2491
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>

commit e9659b4103680eb82e7004b411d2db18c5fbb9bd
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Dec 28 12:09:08 2011 +0530

    cluster/afr: Handle error cases in local init
    
    - Fop should unwind with appropriate errno
    - Local is de-allocated on errors
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Change-Id: I4db40342ae184fe1cc29e51072e8fea72ef2cb15
    BUG: 770513
    Reviewed-on: http://review.gluster.com/2539
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e1f6ebc1a41d1759c2c4ec1d81a9b8a777b7a25d
Author: Rajesh Amaravathi <rajesh@gluster.com>
Date:   Wed Nov 23 12:52:04 2011 +0530

    rebalance: remove the *.fix.layout xattr from trusted domain.
    
    moving trusted.distribute.fix.layout from trusted domain.
    
    Change-Id: If4317e4320998bbd739a8472b8814d75c425d341
    BUG: 765487
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/747
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 8be9b0502843b755adad7badfc4e144cf7c410f6
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Dec 25 22:17:08 2011 +0530

    build: Change dependency of rsync version for geo-replication
    
    Change-Id: Iaf49121ef04bb02114f74cdc2fd2985a564d5407
    BUG: 764476
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-on: http://review.gluster.com/2505
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit 8543529f381d16349662269342d55ab67a1a4582
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Dec 26 10:10:13 2011 +0530

    cluster/afr: Handle split-brain/all-fool xattrs for directory
    
    In case of split-brain/all-fool xattrs perform conservative merge.
    Don't treat ignorant subvol as fool.
    
    Change-Id: I6ddf89949cd5793c2abbead7c47f091e8461f1d4
    BUG: 765528
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2521
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a0c5efcf2cb2be5c9736c75af7a6d8754a101bf5
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Dec 21 10:43:28 2011 +0530

    features/posix-acl: handle fini for features/posix-acl
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I6cd3a9c3a513cc2a998b82610613bbfa0622eec4
    BUG: 767862
    Reviewed-on: http://review.gluster.com/811
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 4511ed196f94f639846b899e6b58f5f6af3fa668
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Dec 13 12:58:25 2011 +0530

    extras: clean up a brick's gfid xattr
    
    * extras/clear_xattrs.sh: This script enables a brick from a
    deleted volume(stale brick) to be used in a new volume by
    clearing all the trusted.gfid xattr from the brick tree.
    
    * One should run this script on all machines which have
    stale bricks if one wants to re-use the same bricks
    for a new volume.
    
    NOTE: This script *SHOULD BE RUN ONLY AFTER STOPPING A VOLUME*,
    thereby ensuring that no replace-brick or rebalance operations
    are on-going.
    
    Change-Id: I35a4a2784fe502749184b87299b1a043b8e48e90
    BUG: 765572
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/781
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 31fa06932952f0cb706653aa7d0450646009eb07
Author: Rahul C S <rahulcs@redhat.com>
Date:   Thu Dec 22 13:17:21 2011 +0530

    Improve cli output of gluster volume heal command.
    
    Improving cli outputs according to the type of the volume,
    the "heal" action can be performed on the volume.
    Also checks if the volume is started & then if the
    "self-heal" daemon is not started, prints appropriate
    message.
    
    Change-Id: I25b0822e4d518c50e2f1173aa8c7c11ae6b76d3f
    BUG: 769774
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/2496
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit d7d9f3d4002d31ceefed6ce80ec7567eca9ba6d3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Dec 20 10:05:12 2011 +0530

    cluster/afr: Set pargfid when missing
    
    client asserts for missing pargfid in case of unlink. So
    Afr needs to make sure it is present in that fop.
    
    Change-Id: Iea0ad65e1e7254c8df412942c52d5870e853aa51
    BUG: 769055
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/2495
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5ccbfdd87bebbc4c65a76c72191ac564ff844df8
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Dec 19 22:10:38 2011 +0530

    libglusterfs: set inode path to be NULL in case of errors
    
    Some of the functions calling inode_path, __inode_path
    are assuming the path to be set to NULL in case of errors.
    Instead of fixing it in the calling functions, fixing it in
    the __inode_path function.
    
    Change-Id: I77736a2700d3c2c9732a536bcf2a398fe626d54e
    BUG: 765430
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/810
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bddb3a014af22133d958da96ad32a02f8ff66805
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Dec 19 18:35:19 2011 +0530

    protocol/server: Do connection cleanup if reply fails
    
    We observed that after the first connection cleanup happens on
    DISCONNECT the lock calls in transit are granted or added in
    blocked locks queue. These locks were never cleaned up after that
    because no unlock would come up on that connection. This would
    leave references on that transport so it would never be destroyed.
    Now, the connection cleanup happens whenever the reply
    submission fails.
    
    Also cleaned up the old code which is not used any more.
    
    Change-Id: Ie4fe6f388ed18d9c907cf8ae06b0b7fd0601a660
    BUG: 765430
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/809
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 23495efe35515891cc56b49ef967d5b1ba195e3e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Dec 19 12:45:34 2011 +0530

    features/locks: Fix release of locks on disconnect
    
    When a disconnect comes on a transport, all the locks on that
    transport should be cleared irrespective of entry presence.
    
    Change-Id: I1c432ec1ddc8fe3f7bf236992f47437d0dacd6ae
    BUG: 765430
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/808
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 941edee5dc38328fb46dd8b284956357ca67dec9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Dec 16 21:47:14 2011 +0530

    cluster/afr: Fix meta data lock range
    
    Change-Id: I7615f31309c6c8f5373e1ff0535d84396dfa1455
    BUG: 765430
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/807
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7eed1d5ba51b65e865f79a392aff70048c702bf0
Author: Harshavardhana <fharshav@redhat.com>
Date:   Fri Dec 2 16:58:14 2011 -0800

    transport/rdma: Add attr_timeout, attr_retry_cnt, attr_rnr_retry
    as configurable options
    
    Change-Id: Ifc4710f149be35979746ddfbfb4181638601bc64
    BUG: 766040
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/766
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0074f208448d131a25721d8cd4ed408c5c57c72a
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Dec 19 12:42:31 2011 +0530

    glusterd: Fixed spurious checks in add_brick.
    
    Previous algo,
     - didn't allow volume type change from plain distribute
       to distribute-[stripe][-][replicate].
     - performed 'add-brick' on temporary volinfo without correct
       initialisations. This was superflous.
    
    Change-Id: If5d5d78e59bd04685df9c27974f715df5f0b43f3
    BUG: 765774
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/804
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 2a3e74e7a68aac1ad6d89122bbc4d64cd304986b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Dec 13 17:13:59 2011 -0500

    Fix local==NULL crash in wb_sync_cbk during disconnect.
    
    Change-Id: I26dc48a85756e189b1ef5cfef1658f9c2aed2157
    BUG: 767359
    Signed-off-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-on: http://review.gluster.com/784
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 255fed3b0d5b9d210d1da47dbd647dd6497cd550
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Dec 15 22:16:13 2011 +0530

    cli: validate the volume set command properly
    
    For volume set command if after the volume name the key and the
    value of the option are not given, then gracefully exit by
    showing the proper usage of volume set, instead of sending the
    request to glusterd, which makes glusterd crash.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Change-Id: I2f0d189a55663c7f47dddff35d4dc68fae16b755
    BUG: 767591
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/797
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 4debbfe7f629626fd2e77a2d98f37f4e808e9f95
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Dec 19 16:36:33 2011 +0530

    cluster/stripe: copy the gfid from the dentry structure to loc
    
    In stripe_readdirp_cbk we used to send stat call on each of the entry
    we have got from readdirp, by creating a new inode (but without
    setting the gfid in loc). Protocol/client asserts if it cannot find
    gfid in either loc or loc->inode. This patch copies the gfid of the
    entry from the stat structure to loc.
    
    Change-Id: I35228227e943f3b01fac720d6c587764c47e6869
    BUG: 768840
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/806
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 3853f4ccaf1f0446af9a3f523008c64834a63df6
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Dec 15 15:13:14 2011 +0530

    rpc-transport/socket: Donot fail reconnect if error is ENOENT
    
    A AF_UNIX family socket should retry connect if error is ENOENT.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Change-Id: I23b1da12faadc8043d370862bfe29c0c5c223364
    BUG: 767932
    Reviewed-on: http://review.gluster.com/795
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a6098362f93e321ce25424d2f95cc1d61783f6b9
Author: Rahul C S <rahulcs@redhat.com>
Date:   Thu Dec 15 18:16:29 2011 +0530

    Default option to be set to "all" if no option is given to
    volume statedump cli command.
    
    Change-Id: Ia167e9d0fd1f9a50f79554d40e6fa7d292896aa4
    BUG: 767545
    Signed-off-by: Rahul C S <rahulcs@redhat.com>
    Reviewed-on: http://review.gluster.com/799
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushal M <kaushal@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 3a0fe71cebd59c1204c60a7d20b2fe2b94f07665
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Dec 14 14:46:09 2011 +0530

    glusterd: Fail 'requests' from non-peers.
    
    glusterd should not honour "volume op requests" from peers who are not
    part of the cluster.
    
    Change-Id: I6cb6d630a9da02ab060650f21edb46db8deb70e8
    BUG: 767559
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/787
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cd24be007c64bd10d8c28e8e9b1c988478a32c8c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Dec 14 10:36:27 2011 +0530

    debug/error-gen: add option to generate errors at random percentage
    
    Currently error-gen has a option where the percentage of the errors generated
    can be specified. This patch adds a new option, which if given errors
    are generated at random percentage. If both the random failure option and
    the specific percentage of the errors are provided, then random error
    generation is given preference.
    
    Change-Id: I43fffcd7da8935761ed7d30e2a9677895d6a31fb
    BUG: 767192
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/786
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ebe0cedb072baf4c1f4bd81f22745c428ab6b911
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Dec 6 14:00:40 2011 +0530

    protocol/client: Be strict about gfids in fop req
    
    Change-Id: I7508ab3a93329bb6a679801fddfcd0e5b0c7c134
    BUG: 765198
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/770
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7235e5b1af090ffc9d87ac59daadf7926433b495
Author: Rajesh Amaravathi <rajesh@redhat.com>
Date:   Tue Dec 13 15:26:55 2011 +0530

    mount/fuse: export PATH for which in mount script
    
    exporting PATH environment variable for mount.glusterfs.in
    to correct the "which: no getfattr in ((null))" error
    during fuse mount.
    
    Change-Id: Id7d024c0d1cf3d265489557897e9e1f8e7ce4ce4
    BUG: 765561
    Signed-off-by: Rajesh Amaravathi <rajesh@redhat.com>
    Reviewed-on: http://review.gluster.com/782
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 91c7ad753884c81b46f05f200b9d9dc00eec5132
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Dec 13 15:54:49 2011 +0530

    cluster/afr: Double the call count if transaction is for rename
    
    In rename the changelog modification needs to happen both on
    old parent-dir and new parent-dir, so 2 stack winds are
    done per brick.
    
    Change-Id: I43f34661e397c4288162213944529e18b7724b1d
    BUG: 766603
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/783
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1d38ec6ce40279d7e8ef2b5a9bd59a2d289eca23
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 24 15:42:55 2011 +0530

    fuse: bring in the reverse invalidation
    
    Thanks to Csaba Henk <csaba@gluster.com> for the patch
    
    Currently one can invalidate the inodes using 'setxattr()' with
    key 'inode-invalidate' (and any value). This can be further
    extended to do a purge of inode table itself.
    
    Change-Id: I165d5d585ed808b9e463ac0aad859ec64568c7a2
    BUG: 762277
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/324
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 289c2902d6a81f7a5b6da04c24cc955bd5427178
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Dec 8 11:42:50 2011 +0530

    iobuf: fix a crash in iobuf when statedump is taken
    
    With the previous patch this change was missed.
    
    Change-Id: If536cef3fa423415eaa4104e6c3e5e72c5d0a22d
    BUG: 3854
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-on: http://review.gluster.com/775
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 017344be59fbbd4cf6d29d3f5a6581b468dc29c9
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 27 18:01:29 2011 +0530

    libglusterfs/iobuf: have fixed number of arenas
    
    * so overall memory usage will be in limit.
    * the array is hard-coded, need to improve upon this.
    * need more benchmarking to tune the proper values to the array
    * fixed the issue of pruning of arenas.
    
    Change-Id: I38a8ffab37378c25d78f77a2d412b1b8935c67d3
    BUG: 3474
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/543
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 254fbfd92d4088c97ddde79a37b4e08e80c8eff3
Author: Harshavardhana <fharshav@redhat.com>
Date:   Mon Nov 21 16:28:47 2011 -0800

    cluster/distribute: Assert checks at known locations
    and new function dict_get_ptr_and_len().
    
    Change-Id: I653a1cc8123baa36d750250d02721aa98b196f38
    BUG: 3158
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/744
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2b64c93c9f7f69fab506bdfca163a2805a2ea46c
Author: Anand Avati <avati@gluster.com>
Date:   Mon Dec 5 14:18:22 2011 +0530

    CONTRIBUTING: add a DCO
    
    The new CONTRIBUTING file has a Developer Certificate of Origin with
    instructions for contributors to ensure 'Signed-off-by:' line in the
    commit log (git commit -s). Corresponding changes also done in Gerrit
    to reject patches which do not have Signed-off-by: line.
    
    Change-Id: Ia3e1e8d3cfd4b32e4cfd4d2df91c6dbd57e2f60e
    BUG: 3234
    Signed-off-by: Anand Avati <avati@gluster.com>
    Reviewed-on: http://review.gluster.com/767
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 99d606e810286eef6f19e39d24dd63cb602a0bb1
Author: Rahul C S <rahulcssjce@gmail.com>
Date:   Fri Nov 25 17:21:46 2011 +0530

    Changes all parent values for quota_check_limit
    and quota_update_size from 0x0 to NULL to make
    sure uuid_copy happens between pointers
    
    Change-Id: I73ef5f9054f972fce00b8f42125dc49c9d86c3f2
    BUG: 3830
    Reviewed-on: http://review.gluster.com/756
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 430f76a6c1c9af06b433a9d6080168b92b30e034
Author: Kaleb KEITHLEY <kkeithle@f16node1.kkeithle.usersys.redhat.com>
Date:   Thu Dec 1 12:44:38 2011 -0500

    bz 3826, fix for parallel make in fedora build system
    
    builds of glusterfs in the fedora build system often fail due to a
    race condition between running yacc and starting to compile the y.tab.c
    produced by yacc
    
    We found that the previous fix would still occasionally trip the race
    condition. This revised patch changes the automake Makefile.am to generate
    the parser files without incurring the race condition. An extra dimension
    of the problem is that the tarball from
      http://download.gluster.com/pub/gluster/glusterfs/3.2/3.2.5/glusterfs-3.2.5.tar.gz
    contains files that you don't get when you clone from the git repo (e.g.
    libgluster/src/{graph.lex.c,y.tab.c}, and all the Makefile.in files) so
    build issues on fedora build systems do not manifest themselves on jenkins
    and vice versa.
    
    This works on jenkins, the fedora build system, and my f16 vm/guest
    machines. (Finding the right combination that works on all three was an
    exercise to say the least. I'm open to other suggestions for avoiding
    the race condition.)
    
    Run autogen.sh to (re)generate the Makefile.ins. Then run configure to
    produce all Makefiles, followed by `make -j X` where X>1
    
    see also https://bugzilla.redhat.com/show_bug.cgi?id=756510
    
    BUG: 3826
    Change-Id: Iaeecb59c61a77bf3927da18253c83cf5ffed4254
    Reviewed-on: http://review.gluster.com/765
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit f5d5e8012a3762d0ffb95a0ca624a3fce3c262cd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Nov 24 13:50:23 2011 +0530

    mount/fuse: Inherit direct-io-mode values from fds already
    opened, for a new fd being opened.
    
    When an fd is being opened, it inherits direct-io-mode characterstics
    (either enabled or disabled) from the fds already opened on inode. If none
    are opened and user has not specified the mode through cmdline options,
    default mode is used.
    
    Change-Id: I0c9e959100e9130e46bbd16d63eca278260635b4
    BUG: 801
    Reviewed-on: http://review.gluster.com/55
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 5d194403e96d97f82681b5e7d96ddf8e48858cb7
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Nov 29 15:20:48 2011 -0800

    contrib/uuid: Make sure that uuid_types.h are generated per system specific.
    Just the same way e2fsprogs maintains. This avoids unnecessary problems
    for different architectures.
    
    Change-Id: I3911998373756707996afb7b926ec0780ea18b81
    BUG: 3833
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/764
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit fbf6ce560dd6e72fc9d404e32d313732077a250f
Author: Kaleb KEITHLEY <kkeithle@f16node1.kkeithle.usersys.redhat.com>
Date:   Tue Nov 29 09:36:50 2011 -0500

    bz 3826, fix for parallel make in fedora build system
    
    builds of glusterfs in the fedora build system often fail due to a
    race condition between running yacc and starting to compile the y.tab.c
    produced by yacc
    
    This patch changes the automake Makefile.am to generate the parser files
    without incurring the race condition
    
    This works on jenkins, the fedora build system, and my f16 vm/guest
    machines. (Finding the right combination that works on all three was an
    exercise to say the least. I'm open to other suggestions for avoiding
    the race condition.)
    
    Run autogen.sh to (re)generate the Makefile.ins. Then run configure to
    produce all Makefiles, followed by `make -j X` where X>1
    
    see also https://bugzilla.redhat.com/show_bug.cgi?id=756510
    
    BUG: 3826
    
    Change-Id: I06ba0d0a1d59f0f44c0dd2cd9d227ca08d99e205
    Reviewed-on: http://review.gluster.com/763
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 1b3571d38fc789100e2c053750eca1109494596b
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Nov 21 12:35:34 2011 -0500

    Add command-line support (but no doc) for enforce-quorum option.
    
    Change-Id: Ia52ddb551e24c27969f7f5fa0f94c1044789731f
    BUG: 3823
    Reviewed-on: http://review.gluster.com/743
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f52dd9bf2005449f49acd5666a02594fb4c5ac6f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Nov 20 09:13:14 2011 +0530

    cluster/afr: Update read-child if it becomes stale
    
    Change-Id: I00c714a89575023f6dbdd3430dcbf191e5d08019
    BUG: 3650
    Reviewed-on: http://review.gluster.com/740
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7ae082e9c519ea91540c4d49f9df44c4e6e9f39a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Nov 15 12:14:56 2011 +0530

    rpc-transport/rdma: add gf_ prefix to all procedure, variable names
    
    Change-Id: I251be23d2c60b88589f71e7a8c3b1f2b7e3eb3e6
    BUG: 3319
    Reviewed-on: http://review.gluster.com/148
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit f4297a0eec29b7eba2f1ddfde0d273d5f6660723
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 16:29:28 2011 +0200

    NetBSD build tweak to use linkat(2)
    
    linkat()é is guarded by -D_INCOMPLETE_XOPEN_C063 for now since support
    for OpenGroup extended API set 2 is not yet complete.
    
    Change-Id: If1038dac61b6945c73a208c6e05f1154ff913098
    BUG: 2923
    Reviewed-on: http://review.gluster.com/232
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 26fd1cecc985d3cd4d84c7fa061b371757c34a6e
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Nov 24 09:15:29 2011 +0100

    case to uint64_t when convering gfid to inode, otherwise it can get
    garbled on 32 bit machines.
    
    Change-Id: Id2acc1f9ae98194d541f5468616be441896c4239
    BUG: 2923
    Reviewed-on: http://review.gluster.com/753
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit ad2d5765d955899f56fec5c05ba9e0e55ccac395
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 16:23:23 2011 +0200

    Let NetBSD use its recently added Linux xattr API
    
    Change-Id: Ibd365e8d83c6faf631df7cb99ec62440496fcbdf
    BUG: 2923
    Reviewed-on: http://review.gluster.com/230
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 86ed5d68596e577b4d923750a619a6921f2cfe18
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Mon Oct 3 13:56:23 2011 -0400

    Add volfile-generation hook facility.
    
    Change-Id: I958c393ce5cfffcde8d120499a43dbe6105a082c
    BUG: 3688
    Reviewed-on: http://review.gluster.com/558
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 3f1092c1a79adefd4400bfb6fd20029a22b0f827
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Oct 16 08:06:18 2011 +0200

    We must #include <signal.h> for sigprocmask(2). Failure to do so will break
    on NetBSD kernel without COMPAT_13 option.
    
    Change-Id: Ia710bbe31ed48e4df4cd47f99e335d7226b99173
    BUG: 2923
    Reviewed-on: http://review.gluster.com/594
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 79c379c70ced3fd8a487cf007ba6c82b0773fb9a
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Sun Oct 16 08:09:11 2011 +0200

    usleep(3) shall not be called with argument higher than 1s
    
    Change-Id: Ied0a2fedb3b7604f6abbf0a4aa7f71e43a5ea568
    BUG: 2923
    Reviewed-on: http://review.gluster.com/595
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 8b8459b5ee5d3bd2dbbf416e12a1be0cd90c270f
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Thu Nov 24 06:32:36 2011 +0100

    Use /bin/mount on Linux, /sbin/mount on other systems
    
    Change-Id: I8d2e518d29cedb1fbfa77d0189a2d4a24957e662
    BUG: 2923
    Reviewed-on: http://review.gluster.com/752
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit b21d430729c45990492703145c075940e6b1c681
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Nov 10 11:09:56 2011 +0530

    afr: Fixed backgroundness detection in self-heal algo.
    
    Change-Id: I9888d8a0b86fdaf6589885766f2de7222d8c8ba2
    BUG: 3802
    Reviewed-on: http://review.gluster.com/705
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
    Reviewed-on: http://review.gluster.com/745
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 3b2febc1c4b1b0f8d473e4e2503ffdff54236c9b
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sun Nov 13 17:45:54 2011 +0000

    rpc-transport: fix some indentions
    
    Some lines are indented with spaces, others with tabs. When Tabs are not
    disaplayd as 8 spaces, the indention is completely messed-up.
    
    Change-Id: I31ddf44c5b7f5fe1c5493adca98e95514f2920bd
    BUG: 3822
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/742
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 41e99d3686f3a63b4c6afa9addc93472971e9570
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Nov 15 13:49:18 2011 -0800

    rpm: rpmbuild fix for opensuse
    
    Change-Id: I4ccf75288aad6d5f210bd7c51c0ce9924bb0efad
    BUG: 2925
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/729
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 5aed416a5f61b18a7eb105fde0752d1f66c37a88
Author: Sachidananda Urs <sac@gluster.com>
Date:   Wed Nov 23 00:02:33 2011 +0530

    Change the start/stop order of glusterd script at boot time.
    
    In cases of client and server sharing the same machine, mounting GlusterFS at
    boot time failed due to the start and stop order we use for glusterd. And people
    had to resort to the idea of adding mount command in rc.local.
    
    Currently the start and stop order at the boot time were 90 and 12, and netfs
    started before `glusterd' and failed to mount GlusterFS. By changing
    the rc order to 20 80 glusterd is started earlier than netfs, thus enabling
    netfs to mount GlusterFS during boot process.
    
    Thanks to: alex@net13.info for the suggestion in bug 2484.
    
    Change-Id: I482f4dac5e5dd8bc5b8f5034c394f5dbe6c1fd3e
    BUG: 2484
    Reviewed-on: http://review.gluster.com/746
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Harshavardhana <fharshav@redhat.com>
    Tested-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 9ac21b5a3e1b0d4afba1afb04ec62ce75e302a5e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Oct 26 12:30:29 2011 +0530

    cluster/afr: Remove treating sh_frame as special loop_frame
    
    Change-Id: I0d87f06f989b2d4b971967c52d4898331693a801
    BUG: 3675
    Reviewed-on: http://review.gluster.com/735
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0413d46873d082bbd3ee41aced3db01e444422d9
Author: Anand Avati <avati@gluster.com>
Date:   Wed Nov 23 18:10:51 2011 +0530

    gerrit: auto-rebase test
    
    Change-Id: I4bd0c2ad1ef5880e2de94d3bcc17158f18e114ab
    BUG: 3234
    Reviewed-on: http://review.gluster.com/750
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 74a2eebd9ed68fe5d8785af47c4dede9051e2ae4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Nov 23 17:49:59 2011 +0530

    Whitespace cleanup
    
    Change-Id: Ifd560492f93b1a35b36bb663c62b3c427e066caa
    BUG: 3158
    Reviewed-on: http://review.gluster.com/749
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7a91ea707ca0f0fec8c63f97eedec04c6a16c50e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Nov 23 17:49:59 2011 +0530

    Whitespace cleanup
    
    Change-Id: I6126e22694c177d3e2b0b4e98551a9038d5cdacd
    BUG: 3158
    Reviewed-on: http://review.gluster.com/748
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3cf35466424046e85dff9f4de2cd6a1c0f9d781b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Nov 14 10:10:27 2011 +0530

    cluster/afr: Open fd fix should perform opendir for dirs
    
    Change-Id: Iee12828ca515d44ed71d9cf97dcb8627c85f0593
    BUG: 3740
    Reviewed-on: http://review.gluster.com/725
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 896fc241850aaa021f6f8958da4e37e37679c0cd
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Nov 15 13:44:43 2011 -0800

    cluster/distribute: Add support for 'min-free-inodes' on each distribute subvolume.
    
    This change is required as increasingly large number of small files
    would cause inodes to run out before they run out on available disk space.
    It is highly necessary to support algorithmic checking of inodes too
    just as we do for disk space.
    
    Change-Id: I9b87405328d443825e239ee80ab664aceb50ee68
    BUG: 3799
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/730
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit af7d85074fc05afdee3ff48f62b0ec5c057a3e6b
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Nov 18 17:53:53 2011 +0530

    cli: remove reference to 'RAID01' for stripe-replicate volume
    
    Change-Id: I3a9b3059fd9b918cb32bbe724ae1125fb1f5642a
    BUG: 3158
    Reviewed-on: http://review.gluster.com/738
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 89a6dc3c2b31299ac10de449d318ecf341e8b840
Author: Niels de Vos <ndevos@redhat.com>
Date:   Sat Nov 12 17:58:44 2011 -0500

    cli-cmd: call cli_cmd_unlock in the same function as cli_cmd_lock
    
    cli_cmd_submit calls cli_cmd_lock, but cli_cmd_unlock is done in
    cli_cmd_await_response. It is clearer to do the locking and unlocking in
    the same function.
    
    Only cli_cmd_submit seems to call cli_cmd_await_response, therefore
    moving the cli_cmd_unlock to cli_cmd_submit should be safe.
    
    Change-Id: I015ae0e2a404005c43606ef5258e3cfad41a88d4
    BUG: 3821
    Signed-off-by: Niels de Vos <ndevos@redhat.com>
    Reviewed-on: http://review.gluster.com/721
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 829f2b90fba8f66287e2e3b89aed9c971c2d828b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Nov 13 11:56:46 2011 +0530

    cluster/afr: Fix memory leaks
    
    Change-Id: I79a1c70c47649fbcf236191f174d766d5806545c
    BUG: 3805
    Reviewed-on: http://review.gluster.com/719
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c9fbd4c309552f7f845e73c92315abe3b6d7081b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Nov 2 13:09:41 2011 +0530

    cluster/dht: set gfid in lookup loc
    
    Change-Id: I59599cc88be1d973c955600fdd54e6c49c77b4a2
    BUG: 3770
    Reviewed-on: http://review.gluster.com/681
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 119289fa51cd6e6ceb149dd3a9596478a85adff4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Nov 5 14:54:28 2011 +0530

    cluster/afr: Handle absence of gfid in lookup
    
    Change-Id: I6295245a7f40ba4f786f1f9f35b337f3f711128d
    BUG: 3783
    Reviewed-on: http://review.gluster.com/739
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 33477a140fb4e891a05dd9261013e83035155350
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Nov 2 11:27:30 2011 +0530

    fuse: enable kernel read-only mode
    
    Enables kernel read-only mode on mounting with '-oro' and disables the gluster
    read-only translator from being loaded. As a result, '-oro' is reported
    correctly in the mount options.
    
    Change-Id: If94d97836b13668974cfac61b6e5d52e19880e10
    BUG: 3742
    Reviewed-on: http://review.gluster.com/655
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>

commit e1de01c3fdde2497cc4a24491b75579624467456
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Oct 5 11:47:14 2011 +0200

    log to stderr if "-" is given as log-file
    
    This works around broken /dev/stderr on some systems.
    
    Change-Id: I017b03082ff630c4a713ae74990e88b3fa20d0e1
    BUG: 3686
    Reviewed-on: http://review.gluster.com/560
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 76d5e5d5b51eb2ffe5a0608bf8869650bb76585f
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Tue Sep 20 09:49:57 2011 -0400

    Add quorum checks to avoid split-brain.
    
    Change-Id: I2f123ef93989862aa796903a45682981d5d7fc3c
    BUG: 3533
    Reviewed-on: http://review.gluster.com/473
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e6a3902410aaa8756e9c07302d88399fb99641c7
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Nov 17 15:12:32 2011 +0530

    mgmt/glusterd volume delete - Unref dict only in case of an error
    
    Change-Id: I6edee785c69864bf42d869ed9cccb52cabc1523d
    BUG: 3817
    Reviewed-on: http://review.gluster.com/736
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 88ee850e68838df34d0a57307299e07dac7d9771
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Sep 27 18:16:12 2011 +0530

    rpc: Need to update conn->last_recieved.
    
    This is important for protocol/client's ping_timer to function correctly.
    
    Change-Id: I9f45d701126bb739535d9c5ec280833362bef9ed
    BUG: 3816
    Reviewed-on: http://review.gluster.com/512
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

commit 9b391694eb53b73a5284bd5294ee66a690e7398d
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Oct 31 18:05:23 2011 +0530

    glusterd:replace-brick subcmds should detect src_brick offline.
    
    Change-Id: I686494c9c2d01fd027d333b267334842cb1dc875
    BUG: 3043
    Reviewed-on: http://review.gluster.com/651
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1e652740f74298637577e9861cb5092091404d29
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Oct 31 15:54:52 2011 +0530

    glusterd: Extended glusterd_is_service_running to get svcs's pid.
    
    Also, volume status cmd would print "N/A" if pid couldn't be
    retrieved from pidfile.
    
    Change-Id: Ie83d228b1cf86397d181885b325e337a403e6ed2
    BUG: 3043
    Reviewed-on: http://review.gluster.com/650
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c5be0df9149155f9e23a8e9f24d0becb0543efe1
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Nov 7 16:13:42 2011 +0530

    cluster/afr: lookup should honor gfid present in loc
    
    Change-Id: I2319258743e478cc3a932d8ff0b2204a97cd4f8e
    BUG: 3760
    Reviewed-on: http://review.gluster.com/680
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3bc27345bf3aaf911960793ef4d48909f585bd84
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Nov 4 19:10:11 2011 +0530

    dht,afr: Fixed gfid problems
    
    *) removed uuid_generate usage in pump and afr, self-heald
    *) filled the gfids for the fops which were sending no gfid in loc
    
    Change-Id: I85da3c10f5ee2006248b0123155a60867870d202
    BUG: 3760
    Reviewed-on: http://review.gluster.com/679
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7e085ebc9ca0d34e6251611fdc42dadc243ce276
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Nov 17 14:17:46 2011 +0530

    glusterd: Fixed volume profile's "are all bricks down?" algo.
    
    "count" key is not set if no brick in the volume (located across peers) is
    running. Sending "count" even when zero bricks are running from originator
    glusterd to client, simplifies "are all bricks down?" algo.
    
    Change-Id: I2b1da13ed4b1b9276917908223c9b2c45ca024b3
    BUG: 3553
    Reviewed-on: http://review.gluster.com/642
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5aadd0765ba4c21b5ef626f7f8ca8ccff530dd2f
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 31 12:23:21 2011 +0530

    xlator: prevent a crash in xlator_destroy due to uninitialized list
    
    was happening when any of the dlopen() fails for xlator loading, and
    xlator_destroy() was called as it was using a uninitialized list for
    traversal.
    
    now, the list gets initialized at the begining of the xl-init(), so
    xlator_destroy() works smoothly.
    
    Change-Id: I320f6fe922e6d351e6d7c0a3e8da1f6b414d3c47
    BUG: 3731
    Reviewed-on: http://review.gluster.com/606
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 43a36decf24b126936bffda273c79e23f547004d
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Nov 15 18:58:59 2011 -0800

    cluster/dht: Fix a typo
    
    Change-Id: I6bcdc7d600ebb9ef68c60319f96cd9e28d12c861
    BUG: 3809
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/732
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit ebc497ddb9d362b9f6390b4a8176afe9f2b5def0
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Nov 7 14:42:37 2011 +0530

    libglusterfs: copy the stat structure in entry_copy
    
    Change-Id: I7a8bd3b3f9600ced4a945f07447698876933ade0
    BUG: 3760
    Reviewed-on: http://review.gluster.com/678
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 51a78ad316975763d45c11affa571892e03643e8
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Nov 15 14:44:24 2011 -0800

    glusterfs: An effort to fix all the spell mistakes and typo
    in the entire glusterfs codebase.
    
    This patch fixes many of spell mistakes and typo in the entire
    glusterfs codebase and all supported modules.
    
    Change-Id: I83238a41aa08118df3cf4d1d605505dd3cda35a1
    BUG: 3809
    Signed-off-by: Harshavardhana <fharshav@redhat.com>
    Reviewed-on: http://review.gluster.com/731
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8c182c6bf700cdc8a7e2d4b75109ad0acee2e70d
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 28 15:41:47 2011 +0530

    core: remove 'ino' variable from 'loc_t' structure
    
    Change-Id: I53b007fbdb42313d207d5d63fbfaaa6aaf033f95
    BUG: 3518
    Reviewed-on: http://review.gluster.com/523
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 14f4e023822a22e0a4902acfd28c8f5ea8c94ccd
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Nov 16 15:39:29 2011 +0530

    core: remove 'ino' variable from 'inode_t' structure
    
    Change-Id: I0f078d1753db65d2f2e0380d1b0450c114cf40dd
    BUG: 3518
    Reviewed-on: http://review.gluster.com/522
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 217842180858afff79d06c24389752299c5ed716
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Nov 16 12:25:28 2011 +0530

    mgmt/glusterd: more cleanup
    
    * 'GD_OP_RENAME_VOLUME' removed
    * unused handler function for rebalance is removed.
    
    Change-Id: Id081cb02a6445c09347bacc0fdf9cd600ff94e5d
    BUG: 3158
    Reviewed-on: http://review.gluster.com/734
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7e3faaf682bf8f35fea9e2b4d930cbb68dae213e
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Nov 11 13:41:01 2011 +0530

    cluster/distribute: Trigger selfheal only if rmdir succeeded once
    
    A EACCES error also should not trigger a selfheal.
    Only if rmdir succeeded on any subvol, a selfheal should be triggered
    
    Change-Id: Ifebb980f0ebd1548adfd3be975ca52ca44c3f3ab
    BUG: 3786
    Reviewed-on: http://review.gluster.com/716
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit d4ff78d02d049335d827f9293a4e931261b5c2bb
Author: Gaurav <gaurav@gluster.com>
Date:   Tue Oct 11 11:15:30 2011 +0530

    NFS: logging enhancement.
    
    Change-Id: Ie1731a6b2b63e07bc49a84c2f9dd87c5b50a9f53
    BUG: 3527
    Reviewed-on: http://review.gluster.com/573
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f97897c394a7f3e9d5e870ba9814ff2ebfc4cc01
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Nov 14 15:53:27 2011 +0530

    Cluster/stripe setattr: Wind only to first_child for special files
    
    Change-Id: Ib055578477461a24562d5da139809cf0965b931e
    BUG: 3807
    Reviewed-on: http://review.gluster.com/724
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 3440b6d68a5e787a6a1baba2073ee0c44a9b1632
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Nov 10 16:39:31 2011 +0530

    cluster/distribute: Use local call_cnt while winding
    
    layout->cnt might be modified in cbk's or different threads, which
    will lead to corruptions
    
    Change-Id: Icfdab01ac583cb3d27d62f878b79e0098b597952
    BUG: 3730
    Reviewed-on: http://review.gluster.com/694
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit a3c49bb260263dce98d44c28e7106da2a2173ed9
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 14 15:57:49 2011 +0530

    glusterd: remove some of the stale 'log <CMD>' functions
    
    Change-Id: Ibda7e9d7425ecea8c7c673b42bc9fd3489a3a042
    BUG: 3158
    Reviewed-on: http://review.gluster.com/726
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit deac165b27d09e762743b180044c33ce90bbeaef
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Nov 12 22:02:37 2011 +0530

    mgmt/glusterd: delete volume to have dictionary as context
    
    earlier only DELETE_VOLUME was having volume name as context, where
    as all other OPs used to have dictionary
    
    Change-Id: I5bfcc458bff3295374eb4f0b0a31f6134745debd
    BUG: 3158
    Reviewed-on: http://review.gluster.com/718
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit a29ab15988f46fbe98151c37676185de970fb187
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Nov 13 00:18:32 2011 +0530

    glusterd/cli: rpc cleanup
    
    no more backward compatibility between glusterd <-> glusterd
    
    Change-Id: Ibfcca1c7e315a90b2639c4cba8da19b11875051a
    BUG: 3158
    Reviewed-on: http://review.gluster.com/610
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7a97478dd1a343fcc5d9d4eab963882191a3de69
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Nov 2 18:38:50 2011 +0530

    XDR: cli-glusterd xdr consolidation
    
    By using only 1 xdr struct for request and 1 xdr struct for response,
    we will be able scale better and also be able to parse the o/p better
    
    For request use-
            gf1_cli_req - contains dict
    For response use-
            gf1_cli_rsp - conains op_ret, op_errno, op_errstr, dict
    
    Change-Id: I94b034e1d8fa82dfd0cf96e7602d4039bc43fef3
    BUG: 3720
    Reviewed-on: http://review.gluster.com/662
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 913b21621e2dad9146366f24048ff07a8046e5c5
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Fri Nov 4 21:46:08 2011 -0400

    Reflect quota-adjusted values in statfs.
    
    Change-Id: I7a2a0b1ad0aa2a972aad9712658083c61052bef2
    BUG: 3813
    Reviewed-on: http://review.gluster.com/675
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@gluster.com>

commit be406a1845e84a659ca5c5834b19c094e88cbaaf
Author: Junaid <junaid@gluster.com>
Date:   Fri Nov 11 17:05:43 2011 +0530

    features/marker-quota: Use stack_wind_cookie in place of stack_wind to preserve the cookie value.
    
    In marker_rename, some of the call back functions make use of cookies sent by the calling functions. In case of stack_wind the
    frame->cookie is over written with the address of new frame.
    
    Change-Id: I8ec98f3305700e2c3295a10dff159ca6a19a380a
    BUG: 3808
    Reviewed-on: http://review.gluster.com/722
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 01de95f41429967fffaa0e9de4badb101839c3ea
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Nov 7 14:09:36 2011 +0530

    storage/posix: assign ino as -1 if gfid is missing
    
    Change-Id: I422c87f977b5da083f9fcfaf20f0ca9a872da0a4
    BUG: 3767
    Reviewed-on: http://review.gluster.com/677
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit a1fd4c9916cc56c10f83b2a1aa7ecee4d563f82a
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Nov 9 14:20:10 2011 +0530

    cluster/distribute lookup: send revalidate calls to all subvols for directories
    
    If mkdir fails on a subvolume, layout is set taking into account
    only the subvols where it was successful. stat does not trigger
    selfheal, as its layout based.
    Revalidate on directories needs to be sent to all subvols, to fix
    the error, and not just on the layout.
    
    Change-Id: If17055508ffcf268806258ed49e7d7500a89d0f2
    BUG: 3793
    Reviewed-on: http://review.gluster.com/693
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 62088ee6a8d2413c828409dec09e31d600987110
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 9 14:40:02 2011 +0530

    rpc-transport/rdma: send correct vector count when both rpc-header and program-header are received through rdma-reads.
    
    Change-Id: I1b0b91eb7216f32a5748325d6dda37f3998302c7
    BUG: 3754
    Reviewed-on: http://review.gluster.com/697
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5e14417b478520620bb5990eda41e3ad3e9af09c
Author: Sachidananda Urs <sac@gluster.com>
Date:   Sat Oct 29 14:20:02 2011 +0530

    Move some of the messages to log level `TRACE'.
    
    Change-Id: I46133b5e2218b9d810251b3dadadd8f157ab07d7
    BUG: 3761
    Reviewed-on: http://review.gluster.com/643
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 78f3ee4fb1687db948ad5d07d1ed9e6177cc54bc
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Oct 17 11:04:35 2011 +0530

    rdd: create the file and do rdd if the file does not exist.
    
    rdd takes input file and copies the its data to the specified output
    file ( by creating it) by selecting random offset. If the input file
    does not exist it will not work. This patch will create the input file
    if it does not exist and then does the copy. File size is given as an
    argument. If the file exists it truncates the file and then does the copy.
    
    Change-Id: Ia09451e9e80e13f27320f1edc12c73c0dcf663a9
    BUG: 3724
    Reviewed-on: http://review.gluster.com/596
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 34795adcc93497d97f1cd258102f4fa4b540464b
Author: krishna <krishna@gluster.com>
Date:   Thu Sep 29 17:44:55 2011 +0530

    Fix memleaks in NFS
    
    Change-Id: I522d4bad71d1e914fa88367f70f5e8c28d64fbbe
    BUG: 3542
    Reviewed-on: http://review.gluster.com/533
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Shehjar Tikoo <shehjart@gluster.com>

commit bb67817cf582678685ce1207f2a1d41fb4c3649b
Author: Rajesh Amaravathi <rajesh@gluster.com>
Date:   Wed Nov 2 15:26:53 2011 +0530

    debug/io-stats: prevent setfattr crash when no value given
    
    Check for whether the dump file is given, and proceed
    on success. If dump file is not given, unwind with ENOENT.
    
    Change-Id: If524a2b20d643e0e75d81daebe59560a78000524
    BUG: 3716
    Reviewed-on: http://review.gluster.com/663
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit cb9ffbe767b8e5edb30bee95e33ebe9945101250
Author: Rajesh <rajesh@gluster.com>
Date:   Wed Aug 24 12:47:24 2011 +0530

    mount/fuse: check for recursive mounts
    
    Adding check_recursive_mount() in mount.glusterfs.in
    to check if mount point is in the lineage of any
    brick path. Gracefully fails if mount point leads
    to recursive mount.
    
    Change-Id: Iedc4cd767d241c8e256181e472c0815f3831a316
    BUG: 2003
    Reviewed-on: http://review.gluster.com/314
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 359eee148b2be5aaf9677f61f98b89a50d0f1b88
Author: Harshavardhana <fharshav@redhat.com>
Date:   Tue Nov 8 16:58:44 2011 -0800

    fusermount: Build problem fixed with new glibc
    
    Change-Id: Id25e688d3dbecb74d820388faec5ee5041f21630
    BUG: 3797
    Reviewed-on: http://review.gluster.com/714
    Reviewed-by: Anand Avati <avati@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fc9fbbc35efaa84e68e108895ad64b062feed280
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Nov 3 14:47:01 2011 +0530

    stripe readv_cbk: Fix stat return values
    
    Workaround -
    If the read request, does not fall to the subvolume with the largest
    file size set, then we never return the correct size. This leads to
    clients seeing a truncated file error.
    
    The work around is to wipe stat being returned as part of read call.
    
    Problem -
    We were passing the stbuf returned by the first child/index, which
    can be different to the size/blocks returned by stat. This led to
    applications viewing the file as being truncated.
    
    The stbuf size needs to be the largest of all results, and blocks
    the aggregation from all subvolumes. (similar to stat)
    
    BUG: 3774
    Change-Id: I46c53c18b2b42b1f5b86b05555bbab73bf993476
    Reviewed-on: http://review.gluster.com/666
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 3200a2be434c462b43bf3ffe0343ddc8900c5d88
Author: Kaushal M <kaushal@gluster.com>
Date:   Mon Oct 31 10:02:16 2011 +0530

    cli : Modify "top read-perf/write-perf" output
    
    Improves alignment and width of columns in the output of "top
    read-perf/write-perf".
    
    Change-Id: I9a4ec3a121f40e099c96952e2388b27ed90b6fe6
    BUG: 3719
    Reviewed-on: http://review.gluster.com/645
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 32173e1c70dcb53470b0738ed4d0022388193113
Author: Kaushal M <kaushal@gluster.com>
Date:   Thu Oct 20 10:53:58 2011 +0530

    cluster/afr : Fix self-heal of special files
    
    Fixes self-heal of special files like device files, fifo files, socket files
    etc. Does it by doing the following:
    * Prevent setting of pending data xattr on a special file during entry self-heal
      when a new fils is created.
    * Allow data self-heal to be started on all file types other than directories.
      During data self-heal, for special files just erase pending xattrs, if those
      xattrs were set by previous releases of glusterfs.
    
    Change-Id: I34d8121e23ad00e85371ae2a36ef30cf3bd5db7a
    BUG: 3525
    Reviewed-on: http://review.gluster.com/618
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit a29f1a0e36bde5ca7b8f3762f10b210b5e12a875
Author: Venky Shankar <venky@gluster.com>
Date:   Wed Oct 5 16:56:30 2011 +0530

    fuse: flip xattr key from user to trusted namespace for certain
    clients.
    
    This is needed for gsyncd/hadoop-plugin running as non-super
    user to be able to request extended attributes under trusted
    namespace. Request for a key is made under 'user.' namespace
    and is flipped by fuse xlator for specific xattr name to the
    corresponding 'trusted.' extended attribute.
    
    Both applications set a identifier (client-pid) while doing a
    FUSE mount, which is checked by get/set/remove interfaces in
    FUSE translator.
    
    Change-Id: I72f77a5dd1ee1d69c8b0e09209449348dbcf879a
    BUG: 3701
    Reviewed-on: http://review.gluster.com/563
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit af708e9fc2eb2104b9e8e3b5a3eaf99201664324
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Oct 25 11:45:10 2011 +0530

    cluster/afr: Remove unused 'ino' code
    
    Change-Id: I425e2d23e9e45f10ddeff2eacf918dd90f8baee7
    BUG: 3744
    Reviewed-on: http://review.gluster.com/639
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c770722983f73aa838b5985755999050c746550a
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Oct 11 16:33:24 2011 +0530

    changing of the volume types after volume is created.
    
    with this patch, one can do all the below operations:
    
    on a simple distribute volume 'test' with bricks A,B, add bricks C and D:
    
     bash# gluster volume add-brick test replica 2 C D
    
    now the volume 'test' becomes distribute-replicate, with pairs A-C, B-D.
    same holds good for stripe.
    
    and now, one can change the replica count 2 on volume 'test' to 4 like below:
    
     bash# gluster volume add-brick test replica 4 E F G H
    
    now, volume has 'replica' count 4, with pairs being 'A-C-E-F' and 'B-D-G-H'.
    
    after this, if user wants to reduce the replica count, he can do
    
     bash# gluster volume remove-brick test replica 3 C H # (one from each pair)
    
    This should work to reduce the replica count
    
    Change-Id: I4f109141a9ba7be4a92a5f5810a4163baeb92973
    BUG: 3305
    Reviewed-on: http://review.gluster.com/158
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit fb653259265cbef00117e89451689dcea6c356b5
Author: Junaid <junaid@gluster.com>
Date:   Mon Oct 17 12:38:14 2011 +0530

    features/marker-quota: Donot log when inode or inode-ctx is NULL.
    
    When running rm -rf from mount point, quota-updation process may endup in a state where the
    inode is already removed from the gluster inode table, but the updation has process is still in
    progress. This is not a error condition because the updation is done asynchronously.
    
    Change-Id: I739bff466d23f55f842c16dd4fa2808df188ddf8
    BUG: 3609
    Reviewed-on: http://review.gluster.com/597
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit dbf7aa864d8f0515fe4d742fc520a4d1134dbbd4
Author: Rajesh Amaravathi <rajesh@gluster.com>
Date:   Tue Oct 11 16:09:52 2011 +0530

    io-stats: improve io-stats dump output
    
    * Cumulative statistics' output has been formatted
      to match #gluster volume profile <vol> info
    * Fop count, latency measurements have been tabulated
      for better readability.
    * Minor formatting of individual fop call counts
      and throughput info dumps.
    
    Change-Id: I0fa524f773018be2f73077d107e34170d19fc420
    BUG: 3544
    Reviewed-on: http://review.gluster.com/581
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 1252cc90da6156945c3636c1a2b5f702bc14fb2d
Author: Kaushal M <kaushal@gluster.com>
Date:   Fri Oct 14 10:33:18 2011 +0530

    glusterd: fix '.cmd_log_history'file handle leak on SIGHUP
    
    Closes the .cmd_log_history file and reopens it to prevent leakage of file
    handles.
    
    Change-Id: I1c846ccf9a0c1c90c9209f26a1c5332d3dd94ffd
    BUG: 3678
    Reviewed-on: http://review.gluster.com/584
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 1e6780efd7320250a213eca25ee85bbf217825c4
Author: Rajesh Amaravathi <rajesh@gluster.com>
Date:   Fri Sep 30 18:05:38 2011 +0530

    glusterd: allow non-related directories with same prefix
    
    Earlier, using two directories with names like /test and /test1
    failed volume creation. This patch sees that the next character is
    checked to be '/' to conclude that they are recursive.
    Eg: /test and /test2 succeed, while /test and /test/alpha does not.
    
    BUG: 3645
    Change-Id: Idc90211a7a572200ed983c87c4344271f53b0132
    Reviewed-on: http://review.gluster.com/544
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 90d820d193c06efdae0a7e513faaadffb2bfdafd
Author: Anand Avati <avati@gluster.com>
Date:   Sat Oct 22 09:48:17 2011 +0530

    locks: perform inode_ref of pl_update_refkeeper outside locked region
    
    Performing inode_ref inside the critical section of pl_update_refkeeper
    (around pl_inode_t->mutex) causes a deadlock with inode_table_t->lock.
    The other thread (process state dump) holds the inode_table_t->lock first
    to loop over inodes and then while dumping an inode's lock context, tries
    to acquire pl_inode_t->mutex thereby completing the deadlock.
    
    The fix is to perform inode_ref outside the critical section in
    pl_update_refkeeper
    
    Change-Id: I689ab4a9b46b36287740279fdec6159182c86119
    BUG: 3753
    Reviewed-on: http://review.gluster.com/628
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit ea4cd6ff18bb811b053b8fc6bcef7d6377dac30b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Oct 24 08:27:40 2011 +0530

    pump: Change crawl to accommodate afr_lookup changes
    
    Change-Id: I600120252445c06d9cc3e7aa24022c2559b6abe2
    BUG: 3747
    Reviewed-on: http://review.gluster.com/638
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2712393ba21dbfdc7b3443ed019d35ab60628b2a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Oct 21 14:45:08 2011 +0530

    cluster/afr: Take gfid-req from xattr_req only if inode->gfid is null
    
    Change-Id: Iddf5b59d3534c517dcd3c0d7b819e3768f6e915a
    BUG: 3747
    Reviewed-on: http://review.gluster.com/637
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ae78820311fc95047195735b1519fa4d626de208
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Oct 22 11:32:40 2011 +0530

    mount/fuse: set gfid in lookup after a failed revalidate lookup
    
    Change-Id: I1904aa63d9365ebda3e979449454ac08db85d93d
    BUG: 3747
    Reviewed-on: http://review.gluster.com/636
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit b3d696f78b16f246bd34f87aafb52317033408cc
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Oct 21 12:17:04 2011 +0530

    Stripe mknod: Always call mknod if REGULAR file on first child.
    
    This prevents a possible race between mknod(REGULUAR files) and remove.
    mknod first creates on the first_child, and only if successful, on other
    subvolumes.
    
    Change-Id: I0ddaeb92c1884c771c966bb151db052ab5735367
    BUG: 3727
    Reviewed-on: http://review.gluster.com/608
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit bdf20a205a4d67d5f6d3ac6010a34291c2822a80
Author: Venky Shankar <venky@gluster.com>
Date:   Wed Sep 28 16:38:00 2011 +0530

    cli: add geo-replication log-rotate command
    
    Rotating geo-replication master/monitor log files from cli.
    On invocation, the log file for a given master-slave session
    is backed up with the current timestamp suffixed to the file
    name and signal is sent to gsyncd to start logging to a new
    log file.
    
    Sample commands:
    
    * Rotate log file for this <master>:<slave> session:
    gluster volume geo-replication <master> <slave> log-rotate
    
    * Rotate log files for all session for master volume <master>
    gluster volume geo-replication <master> log-rotate
    
    * Rotate log files for all sessions:
    gluster volume geo-replication log-rotate
    
    Change-Id: I75f641b4e082a04d5373c18583ca4a1d9651d27a
    BUG: 3519
    Reviewed-on: http://review.gluster.com/529
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>

commit 84ebee8c20ce667a5ec5fddc0aa47f8b5bef39f8
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Oct 18 10:30:42 2011 +0530

    build: warning suppression (round n)
    
    with this patch, there are no more warnings with gcc (GCC) 4.6.1 20110908
    
    Change-Id: Ice0d52d304b9846395f8a4a191c98eb53125f792
    BUG: 2550
    Reviewed-on: http://review.gluster.com/607
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 26a51e5e6ec1639a7601c0fc373fd9f6493b014a
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Oct 2 11:34:41 2011 +0530

    libglusterfs/syncop: fix minor memory leaks
    
    * most of the leaks can happen in syncop_lookup(), if rsp_dict is
      not provided by user
    
    Change-Id: I5a887c45f1a46a91502147e44f7ed9d41f50dbc6
    BUG: 3715
    Reviewed-on: http://review.gluster.com/550
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 429550b75d2b97f24a102cc648bf9d8240965f93
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 13 12:59:41 2011 +0530

    distribute: handle migration of symlink and special files
    
    TODO: currently, wrt. rebalance/decommissioning, only pending thing
    is hardlink migration.
    
    Change-Id: I30cd06802e84c95601a5a081198f1f09c6d6bc01
    BUG: 3714
    Reviewed-on: http://review.gluster.com/578
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 54b44736b1558cd7e3adf75a8ecfe1a5c236dc20
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Oct 19 13:44:32 2011 +0530

    Remove EXCEPTIONS file.
    
    Change-Id: I79fe05102a954ee1c831ceca229f6dbc1997113d
    BUG: 3737
    Reviewed-on: http://review.gluster.com/617
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e1fda0971decffeddbaa0a4491270d991d83359c
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Oct 13 17:52:44 2011 +0530

    pump: status shouldn't be cleared until migration is complete during commit.
    
    Clearing pump status on migration complete is futile because we would be
    'replacing' src brick with destination brick in the volume anyway.
    
    Change-Id: Ib12fee84bd5445c4a20dac1cf10555331d7b8ebd
    BUG: 3653
    Reviewed-on: http://review.gluster.com/585
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c59dd30a13993b1988132de168f4f152757ff420
Author: Pete Zaitcev <zaitcev@yahoo.com>
Date:   Tue Aug 16 14:42:49 2011 -0600

    Print microseconds as a fraction.
    
    Change-Id: I35cdf2c771974b9c51db47f24cd044ae014e52ce
    BUG: 3426
    Reviewed-on: http://review.gluster.com/244
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit fed29e0ae382ef24f4d3dff3623daefc57dab6ce
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Oct 14 18:28:27 2011 +0530

    cluster/afr: Prevent truncation of mask uint64_t->gf_boolean_t
    
    Change-Id: If67f726f21b713fa9312dc499a1aca4cb00f71de
    BUG: 3682
    Reviewed-on: http://review.gluster.com/589
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3edfb0c492d73b349d83f904c42e6edfb9678965
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Oct 10 18:44:41 2011 +0530

    glusterd: Removing delayed moving of op sm for stop vol/remove brick op.
    
    Earlier we waited for brick disconnect or 5s whichever is smaller, before we
    move op sm from brick op stage to commit stage. This involves a race where both
    the above mentioned events can happen 'concurrently' and result in double free.
    
    Change-Id: I8b1524afded84c20d55e29cfe2579ca872d2ac26
    BUG: 3700
    Reviewed-on: http://review.gluster.com/575
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 513cd0d12e3b72e9a3714deeee251414e651213f
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Oct 2 13:20:25 2011 +0530

    glusterd: take off 'auto-commit' behavior of decommissioning
    
    currently if 'remove-brick <BRICKS> start' is given, after all
    the data is migrated, in the _cbk() function from rebalance
    complete we used to re-write the volume file without the bricks.
    But the flaw of this method is that, currently the _cbk() function
    is called on only the node on which rebalance actually happens,
    hence other nodes are not aware of this behavior. So, had to remove
    the 'auto-commit', instead we want the user to issue a command
    'remove-brick <Bricks> commit' (or 'force') explicitely to remove
    the bricks
    
    Change-Id: Ifdac1292095029429da502aa6e4c0cf4ee124990
    BUG: 1952
    Reviewed-on: http://review.gluster.com/551
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 18071a240bd4c0d92f583632a7cdef1cd32bbe62
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 3 15:41:04 2011 +0530

    libglusterfs/iobuf: increase the iobref's iobuf array size
    
    earlier it was hardcoded to 8, now increased the size to 16.
    also return the exact error code in client_submit_vec_request(),
    so there will be no missing frames in case of errors.
    
    Change-Id: I82a6ee681a543b673a7cf1a0b9c5ade2a7175ebe
    BUG: 3679
    Reviewed-on: http://review.gluster.com/555
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 33ac0c6b48ccbaf357644710c804e55bdfdb12da
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Oct 7 12:29:29 2011 +0530

    smoke.sh: Avoid running extended attribute tests with dbench
    
    Change-Id: I6d58e387e2bf9d5616ec3950abdb0680801523db
    BUG: 3234
    Reviewed-on: http://review.gluster.com/564
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>

commit 3e7d8614cdb4bd77d31b7e10cdd56ab212291568
Author: Sachidananda Urs <sac@gluster.com>
Date:   Thu Oct 6 23:34:50 2011 +0530

    Fix a typo in log message.
    
    Change-Id: I5c2b170977f21c9a83d36f60d9a145c6cc221358
    BUG: 2346
    Reviewed-on: http://review.gluster.com/562
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ea3df58fd3fffcfe6f6e703ff3358a6cf1bc0619
Author: Junaid <junaid@gluster.com>
Date:   Fri Sep 30 15:41:33 2011 +0530

    cluster/dht: Handle 'user.ufo-test' sent by ufo in dht setxattr.
    
    In this case, send setxattr to all the bricks to test user xattr support and return error if setxattr fails on even one of the bricks.
    
    Change-Id: I9a9b27312a650d25bbc1f57e1ab8899d63d0593d
    BUG: 3185
    Reviewed-on: http://review.gluster.com/542
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f8959749d26de4b13774e04ba4d01d799dc1c725
Author: Junaid <junaid@gluster.com>
Date:   Fri Sep 30 12:15:17 2011 +0530

    features/marker-quota: Return error when inode-contribution is not present in inode_ctx.
    
    Also, create the inode_contribution node even before checking for dirty and xattr not present in mq_inspect_directory_xattr function.
    
    Change-Id: Ie5b6e6ba8d5abcfc6aeb9b192720ac10aac1319e
    BUG: 3624
    Reviewed-on: http://review.gluster.com/539
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 78dd69c4c732d3d74070118f0b6b708264d8fc0c
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Sep 30 17:40:26 2011 +0530

    locks: Avoid printing blocked times for locks that were never blocked.
    
    Change-Id: Ieedbfbe3ce2d4a87a8fe0e1a4322a1bb0549a2bf
    BUG: 3662
    Reviewed-on: http://review.gluster.com/545
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9d062a1359994e4c035a413fc9c5aec28fa5e7ae
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Oct 6 10:33:52 2011 +0530

    glusterd: pending_node type missed in profile volume op.
    
    Change-Id: Ib3c73a8432fdd2559422577a2f0c91d50b5a098c
    BUG: 3704
    Reviewed-on: http://review.gluster.com/561
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1b2164ec8cfea7ab99fc4a0cb86fa3d41e4fb7e5
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Oct 3 17:21:19 2011 +0530

    Stripe: Prevent dir gfid mismatch and ENOTEMPTY errors
    
    gfid mismatch issue-
    rmdir- first remove from non first child (FC), and then last from FC. If one
    fails, FC entry is not removed and op is failed.
    mkdir- first create dir from FC, followed by other childs. If FC is success
    then, we succeed, banking on entry self heal
    
    ENOTEMPTY issue-
    
    unlink: remove from non FC and then on success remove from FC. If non FC remove
    fails, fail unlink
    create- Create first on FC, and on success create on  non FC.
    
    Change-Id: Ia8b9e92cd2aba891d249d1995e383fea0581ffca
    BUG: 3663
    Reviewed-on: http://review.gluster.com/557
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit e397772955f10f22fcb920f34a32efd859fb727d
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Oct 3 15:25:12 2011 +0530

    glusterd: Handle restoring of volumes created in older versions.
    
    Change-Id: Idd9cb9d05122750ac78410b8f5a080104d6c1e0a
    BUG: 3685
    Reviewed-on: http://review.gluster.com/554
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 72f80b87c40a899a5c6f838d368a80e6f9846f69
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Oct 3 14:53:04 2011 +0530

    glusterd: Shouldn't inject COMMIT_ACC event before receiving ACC from all peers.
    
    Change-Id: I88b9935f93d9a06e46c3351c2fd37c969396bb0a
    BUG: 3683
    Reviewed-on: http://review.gluster.com/553
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4235f7a74e0c4c637f1db2f49624a972d72b12fb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Oct 3 16:01:25 2011 +0530

    cluster/afr: set the read child ctx only if the self-heal source is valid
    
    Change-Id: Ifdf0db71594ce526ad85c21103726798d9aceef4
    BUG: 3639
    Reviewed-on: http://review.gluster.com/556
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b6eee04da4a699c7cd850bf2121825cc67f14707
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Oct 2 08:46:46 2011 +0530

    core: made changes to return value of __is_root_gfid()
    
    now returns 'true(1)' is gfid is root, 'false(0)' if not.
    earlier it was the inverse, which was bit confusing
    
    Change-Id: Id103f444ace048cbb0fccdc72c6646da06631584
    BUG: 3518
    Reviewed-on: http://review.gluster.com/549
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0db88567b916dc0dbfb0dfe2ed8a47f8d50fb317
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Oct 1 19:20:28 2011 +0530

    libglusterfs/syncop: do not rely on synctask set in makecontext
    
    Across glibc implementations, interpretation of argc/argv passed
    to makecontext() is different. This patch does away with dependence
    on such arguments passed to makecontext(). Instead,synctask reference
    is retrieved from pthread_getspecific().
    
    Change-Id: Ie01feaa0b7d430f8782c2f6805ccdf8026e401f4
    BUG: 3636
    Reviewed-on: http://review.gluster.com/547
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9ef8eabae21a3073f3dc09602d0680d631cbd576
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 29 12:11:44 2011 +0530

    statedump: do not print the inode number in the statedump
    
        Since gfid is used to uniquely identify a inode, in the statedump
        printing inode number is not necessary. Its suffecient if the gfid
        of the inode is printed. And do not print the the inodelks, entrylks
        and posixlks if the lock count is 0.
    
    Change-Id: Idac115fbce3a5684a0f02f8f5f20b194df8fb27f
    BUG: 3476
    Reviewed-on: http://review.gluster.com/530
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 161ab1b9664abf3561902c94b8748e9a95d4867c
Author: Kaushal M <kaushal@gluster.com>
Date:   Mon Sep 26 10:24:46 2011 +0530

    glusterd: cleanup unneeded volumes after peer detach
    
    Performs cleanup on the detached peer and in the cluster after a
    peer detach, and also adds a new check before starting detach.
    
    Cleanup -
     On the detached peer, cleanup removes the entries of those volumes
    on the peer that do not have all their bricks on it. This prevents
    these stale volumes from being added to a new cluster when peer is
    attached to one.
     In the cluster, all those volumes which have all their bricks on the
    detached peer are removed.
    
    Checks-
     Checks if all the peers in the cluster are online and connected,
     except the peer being detached, before starting detach. Using force
     will bypass this check and do detach.
    
    Change-Id: I4fef9ea3cc72ce8c4ce0a82b4ee8a1663a502061
    BUG: 1926
    Reviewed-on: http://review.gluster.com/431
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit acea7409a35d03c438ff2738f701add26f0061c9
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Sep 14 18:29:18 2011 +0530

    glusterd, cli: adds 'force' for 'peer detach'
    
    Adds add a 'force' option to 'peer detach' to forcefully detach a peer from a
    cluster, even when the cluster contains volumes with bricks on the peer.
    
    Change-Id: I134df51c16a07345c8869b318141d427b572eba5
    BUG: 3549
    Reviewed-on: http://review.gluster.com/429
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 795c8996c18f5e8ef5986581644374d0c5068772
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 30 12:53:16 2011 +0530

    distribute rebalance: preserve proper mode in destination
    
    * don't set 'sticky' and 'sgid' bits to 0 without checking if the
      source had those bits prior to rebalance.
    
    Change-Id: Ia826cb3cfb55312cdbf00d3421f2bd06b3103ce6
    BUG: 3656
    Reviewed-on: http://review.gluster.com/541
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 36ef90d6de0e97812bebb303a7fa5215ae4c6ebe
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 30 12:22:34 2011 +0530

    rebalance process: propagate proper errors to user
    
    * cluster/distribute: while rebalance, differentiate between valid
      errors, validation check failures (may not be migrate failure),
      and success.
    
    * mgmt/glusterd: differentiate the errors based on errno. If a valid
      error has happened, mark the rebalance status as failure, and
      stop the rebalnace crawl.
    
    Change-Id: I2d7bd7b73d2b79bfaf892ad4364bc89830a0d5bb
    BUG: 3656
    Reviewed-on: http://review.gluster.com/540
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ba20df9f1a218177e7c7dcc15a11143183d28243
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Sep 29 16:44:40 2011 +0530

    locks: dump client pid and time of blocking/granting.
    
    Change-Id: Icaa919f3009fb70f6af9b95fceaf800f3beca447
    BUG: 3662
    Reviewed-on: http://review.gluster.com/532
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b9c48822413fad5caaafa92c039dae6494476d76
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 29 08:12:22 2011 +0530

    cluster/afr: Don't unlock sh_frame on failure in algo
    
    Change-Id: I0ef541c1f387c397c345e3f2bc9a57f1eff282a1
    BUG: 3647
    Reviewed-on: http://review.gluster.com/527
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b1bf3edb6cf153277f37d1a899e7c6b9e6cb6c24
Author: Rajesh Amaravathi <rajesh@gluster.com>
Date:   Mon Sep 26 11:08:48 2011 +0530

    gnfs/server: allow 255-char file names
    
    * Posix requires 255 character filenames(NAME_MAX), so
    buffer to store a filename should be 256(+1 for
    terminating '\0' character).
    
    BUG: 3572
    Change-Id: I9d3dbb49d96b3da946cbab97f927209d71ece620
    Reviewed-on: http://review.gluster.com/531
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Krishna Srinivas <krishna@gluster.com>

commit d82f740d34f3a0b353408caf6509bef709f877a8
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 30 10:51:54 2011 +0530

    glusterd rebalance: allow 'status' and 'stop' from all the peers
    
    * the check to see which command is issued to do the source node
      check had an error.
    
    Change-Id: I5cebe6e263c416d859af4f413d47c7b643815f6f
    BUG: 3655
    Reviewed-on: http://review.gluster.com/537
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 5cfca9f388cd153bcbcb963ba91867acf3bfac25
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Sep 30 07:07:59 2011 +0530

    cluster/afr: set fd ctx on opendir
    
    Change-Id: Ica845035781f47de990e9dcfefdeb37bed99d515
    BUG: 3637
    Reviewed-on: http://review.gluster.com/536
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit abb4cbeea35c40d69f18aba599f58d7e2dc5fdaf
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Thu Sep 8 11:07:10 2011 -0400

    Second round of warning suppression.
    
    Used a #pragma to kill ~170 in rpcgen code.  Added GF_UNUSED to deal with
    a few more from macros elsewhere.  The remainder are function return values
    (mostly context and dict calls) that really should be checked.  Those would
    be harder to fix without real understanding of the code where they occur,
    so they remain as reminders.
    
    (Patchset 2: deal with older gcc that doesn't handle #pragma GCC diagnostic)
    
    (Patchset 3: fix include paths in generated files)
    
    (Patchset 4: keep up with trunk, squash 9 new warnings)
    
    (Patchset 5: six more, all in AFR)
    
    Change-Id: I29760c8c81be4d7e6489312c5d0e92cc24814b7b
    BUG: 2550
    Reviewed-on: http://review.gluster.com/378
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b43596fb4cdb84ae8b5665537914fe72517b8722
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 29 19:37:18 2011 +0530

    mgmt/glusterd: skip shd graph generation for non-replicate vols
    
    Change-Id: I1bb83342bc0fa883ede527527ec8fd6ee470f781
    BUG: 3666
    Reviewed-on: http://review.gluster.com/535
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit ce8a569e9f18cfff2f2befe259c2022d9b37538f
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Sep 14 09:50:45 2011 +0530

    performance/io-cache,quick-read: increase cache-size limit
    
    Does the following:
    1. Increases cache-size limit from 6GB to 32GB.
    2. Prevents 'volume set'from failing when cache-size is set over the
    limit. Just issues a warning.
    3. Performs check on cache-size by comparing with total system memory
    available in init () and reconfigure () methods.
    
    Change-Id: I7dd4d8c53051b89a293696abf1ee8dc237e39a20
    BUG: 3495
    Reviewed-on: http://review.gluster.com/409
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f3a6752cc455676d6e1f946b513636d991825da8
Author: Rajesh Amaravathi <rajesh@gluster.com>
Date:   Tue Sep 27 16:25:58 2011 +0530

    glusterd: allow non-related directories with same prefix
    
    Earlier, using two directories with names like /test and /test1
    failed volume creation. This patch sees that the next character is
    checked to be '/' to conclude that they are recursive.
    Eg: /test and /test2 succeed, while /test and /test/alpha does not.
    
    Change-Id: Idee1e15b7e0a0d0965d1aea910b52f1da286d64b
    BUG: 3645
    Reviewed-on: http://review.gluster.com/511
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 6d1e6a5b7c447d612684de1a75b6701b1f628fb6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 29 18:04:01 2011 +0530

    glusterd: prevent rebalance being called in volume status execution
    
    Change-Id: I70e7d38a5cb3f6b0033ab9cabd7dfed0c68b77b8
    BUG: 3668
    Reviewed-on: http://review.gluster.com/534
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit a8270c537c257da13c4b48c1524ecb77ee67308f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 29 11:04:35 2011 +0530

    protocol/server: check for the fd being NULL and unwind
    
    Change-Id: I400e515431cf739fe0b2f90840359496a2b529d2
    BUG: 3158
    Reviewed-on: http://review.gluster.com/528
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit fb648cf39c8715e5a25752defdfc95ec0ba04217
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 27 14:44:01 2011 +0530

    cluster/afr: Handle files without gfid in self-heal
    
    Change-Id: Ibcaaa9c928195939ff1e31b28b592e524e63a423
    BUG: 3557
    Reviewed-on: http://review.gluster.com/519
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 09cfa5dffa79abd833354a26783db9edcfb69105
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 27 14:42:28 2011 +0530

    libglusterfs: wipe other variabes in loc
    
    Change-Id: I0553bb7f64d69f5684c3d21f3809da4e9e3529c1
    BUG: 3557
    Reviewed-on: http://review.gluster.com/515
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit c7985fe0d384846fb8974ab75eda7995bb354d79
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 27 15:52:31 2011 +0530

    glusterd : 'volume stop' to check if other ops are in progress
    
    * handles the case of 'rebalance' in progress
    * inturn it will also handle the case of decommissioning in progress
    * also now checks if a replace-brick is in progress
    
    Change-Id: I0266483089515d16fe8167afe06a07696328a8e3
    BUG: 3358
    Reviewed-on: http://review.gluster.com/518
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit dd400b5c5c49f1479db668b185a81fd434f7b219
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 27 23:10:58 2011 +0530

    glusterd rebalance: minor enhancements
    
    * honor 'stop' command as early as possible
    * don't send a setxattr() call if file doesn't have dht linkfile
    
    Change-Id: I159641d03cd15e5818b811ad113d298f7f0112db
    BUG: 3584
    Reviewed-on: http://review.gluster.com/520
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 8b539b2a3d91df2be314665bda15bdedd898d347
Author: krishna <krishna@gluster.com>
Date:   Wed Aug 10 13:00:16 2011 +0530

    by default make option rpc-auth.addr.namelookup off.
    
    Change-Id: I11c1d55bebfc86c634cf446c50585f6c56c02665
    BUG: 3345
    Reviewed-on: http://review.gluster.com/204
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 45172a5415abc6b2f17eea74d51805ac85cc0072
Author: Kaushal M <kaushal@gluster.com>
Date:   Mon Sep 5 14:33:43 2011 +0530

    cli : new volume statedump command
    
    Changes:
            1. Add a new 'volume statedump' command, that performs statedumps of
            all the bricks in the volume and saves them in a specified location.
            2. Add new server option 'server.statedump-path'.
            3. Remove multiple function definitions in glusterd.h
    
    Statedump Information:
    
    The 'volume statedump' command performs statedumps on all the bricks in
    a given volume. The syntax of the command is,
            gluster volume statedump <VOLNAME> [type]......
    
    Types include,
            * all
            * mem
            * iobuf
            * callpool
            * priv
            * fd
            * inode
    Defaults to 'all' when no type is specified.
    
    The statedump files are created by default in /tmp directory of the
    server on which the bricks are present.
    This path can be changed by setting the 'server.statedump-path' option.
    
    The statedump files will be named as,
            <brick-name>.<pid of brick process>.dump
    
    Change-Id: I01c0e1a8aad490da818e086d89f292bd2ed06fd4
    BUG: 1964
    Reviewed-on: http://review.gluster.com/321
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 16b7e3bf201686ca03f8c35c20295e05abe52df8
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Sep 26 14:38:58 2011 +0530

    build: Solaris build fixes
    
    Change-Id: Ic47d07a199ecbc42a141e391bbc75096e270e404
    BUG: 3446
    Reviewed-on: http://review.gluster.com/503
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 370ecfbf3e9a778282100d85747f506cdeb2b40a
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue Sep 27 14:18:38 2011 +0530

    glusterd: Should not cleanup peerinfo too soon.
    
    friend_remove_cbk cleans up peerinfo and the unrefs the associated rpc_clnt
    obj. When the cbk is run inside call_bail or saved_frames_unwind, we might end
    up destroying the rpc_clnt and associated saved_frames_pool while we are still
    using saved_frames to iterate through the frames.
    
    Change-Id: Idf7768478a6d07a87c7faeac5b70e13bcacd2641
    BUG: 3511
    Reviewed-on: http://review.gluster.com/510
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2e00396e04f261af45c33b55b9b73157a2e8fc72
Author: Kaushal M <kaushal@gluster.com>
Date:   Tue Sep 27 12:37:22 2011 +0530

    storage/posix : prevent unmount of underlying fs
    
    posix xlator now performs opendir () on the brick directory during init ().
    This will prevent the underlying filesystem mounted to that directory from being
    unmounted.
    
    Change-Id: I02c190ab8a91abc4ab06959b36f50e0a3fa527ae
    BUG: 3578
    Reviewed-on: http://review.gluster.com/509
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9dc9fb48f1790a76c499b105687cee82b2840865
Author: Kaushal M <kaushal@gluster.com>
Date:   Mon Sep 26 10:33:56 2011 +0530

    glusterd: support for resetting single option
    
    Allows resetting of only single options using 'volume reset' command.
    New syntax of volume reset is: 'volume reset [option] [force]'.
    Giving "all" as options or not specifying an option, causes all options
    to be reset.
    
    Change-Id: Ib9e220f326adeb1be1a774737a0b12c910012cea
    BUG: 2980
    Reviewed-on: http://review.gluster.com/450
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit ea71efe027e9f741032b6bf9dd995bcaa2fa7947
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 26 17:42:40 2011 +0530

    cluster/distribute: fixed a spurious inode ref
    
    While bringing in support to open-fd migration, dht_local_init()
    itself started doing 'loc_copy()'. I had left one case in dht_lookup()
    where there is a extra loc_copy() on existing copied 'local->loc',
    which would cause 2 inode_refs on a given inode, and only one
    inode_unref() happens in dht_local_wipe().
    
    Change-Id: Idd0375bdf9a6408db1e97e80389249ef8d802adb
    BUG: 3590
    Reviewed-on: http://review.gluster.com/504
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 0286dd866a89c035073294c348a43beca3109c38
Author: Kaushal M <kaushal@gluster.com>
Date:   Mon Sep 26 11:19:24 2011 +0530

    glusterd: more checks before starting rebalance
    
    Checks if specified volume is of a distribute type and has more than one
    brick before attempting to start rebalance.
    
    Change-Id: I9a3405019e7af4a7d7e162b0dc054bf9a99364e7
    BUG: 3561
    Reviewed-on: http://review.gluster.com/501
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 68ff38bd2f77c62cd0c5729b047003694a7d63af
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 26 20:43:17 2011 +0530

    glusted: while doing add-brick, handle distribute volume separately
    
    so the logic of different type of counts etc won't come into action,
    which would fail the add-brick operation.
    
    Change-Id: I5c8769d6d1c2433ffb084e5dce9c1e01678cff40
    BUG: 3630
    Reviewed-on: http://review.gluster.com/505
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit b894944857a7ce61a3bd31566d6169ed8d19ce8b
Author: Anand Avati <avati@gluster.com>
Date:   Sun Sep 25 18:34:14 2011 +0530

    rpc: fix wrong wiping of state machine's state
    
    The macro __socket_proto_read() is used to read one sub-header in a fragment
    after another. It also has to 'get out' of the state machine's
    switch/case construct in two situations -
    
    a) finished reading the full header
    
    b) after a partial read, (and return in the same state at next pollin)
    
    The 'reset' of the state should happen only after a full read of the header
    and not if there was a partial read of the header.
    
    Change-Id: I3650a83e1fae0f317cfd1b549835c72e39dc5253

commit 76580479033087f6dde080c27618baf19b18b658
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 15 12:57:44 2011 +0530

    glusterd: cleanup of volinfo '*_count' definitions
    
    earlier, sub_count was having different meaning depending on the
    volume type.
    
    now, for replica and stripe count, one can directly access the
    'replica_count' or 'stripe_count' to get the corresponding
    value from the volume info. 'sub_count' is preserved as is for backward
    compatibility. there is a new variable 'dist_leaf_count' to get
    info about how many bricks are present in one distribute sub volume.
    
    Change-Id: I5ea1c8f9ae08f584cca63b91ba69035c7e4350ca
    BUG: 3158
    Reviewed-on: http://review.gluster.com/435
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 1b096c3ff0a4c25ff22a32d9594d2e289a3d67ea
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 23 16:19:20 2011 +0530

    glusterd-volgen: prevent a crash when volume type is stripe-replicate
    
    when volgen tries to check for decommissioned nodes, a check for
    stripe replicate volume was missed
    
    Change-Id: Ie3aa97da2ec0d94fcf65f96bb4006b3fb54f59dc
    BUG: 3616
    Reviewed-on: http://review.gluster.com/494
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 1fdcbb61872b0a849490d1f0de4fdb545e2865aa
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Sep 21 11:53:45 2011 +0530

    rpc: No timeouts for lock fops.
    
    As of today, all fops bail out after 30 mins by default. This is not desirable
    with lock fops since it could be 'rightfully blocked' for a really long time.
    But the client would assume that the lock fop has 'expired' after 30 mins and
    clean up its references to the locks.  Later when the locks xlator decides to
    grant it, we are left with an orphan (stale) lock .
    
    This fix exempts lock fops from timeouts. Only on network disruptions both
    client and server decide to 'clean up' the locks held.
    
    Change-Id: If1d74ba21113650b976728e9b764c551a0a49e59
    BUG: 3617
    Reviewed-on: http://review.gluster.com/478
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 95876fa0ee03b0ee4cd31fa9874b4de596ae70a4
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 21 14:16:46 2011 +0530

    statedump: dump important details of oldgraph also
    
    * with this, it helps to find out most of the leaks in the process
    
    Change-Id: I70b476e4d63d74843d6664cfe407164f2b79b781
    BUG: 3567
    Reviewed-on: http://review.gluster.com/491
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2b21ea3c625fab19e88c21f4c104dca321eef262
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Sep 23 11:49:29 2011 +0530

    libglusterfs: Adding missing event strings for events.
    
    Change-Id: Idf55abfa77712d32b27798fedcfddb65599b562b
    Reviewed-on: http://review.gluster.com/493
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4765dd1a1c51c67ab86687fbd871c89156680c34
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Sep 16 10:40:32 2011 +0530

    glusterd: Implemented cmd to trigger self-heal on a replicate volume.
    
    This cmd is used in the context of proactive self-heal for replicated
    volumes. User invokes the following cmd when (s)he suspects that self-heal
    needs to be done on a particular volume,
            gluster volume heal <VOLNAME>.
    
    Change-Id: I3954353b53488c28b70406e261808239b44997f3
    BUG: 3602
    Reviewed-on: http://review.gluster.com/454
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 53b5da6dfab2e6b11ab2e40119e92ff7d4527b2c
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Sep 22 12:53:55 2011 +0530

    posix-getxattr: Honor xattr name if specified
    
    Currently, getxattr works like listxattr, and does not honor a call
    with a name (key) being specified. The fix handles such scenarios when
    a name is passed. If the name param is NULL, then it behaves like a listxattr.
    
    Changing key size to 4096, as 1024 might not be sufficient length for keys.
    
    Change-Id: I317b2e6372e97048e3166d91145c19c9e92e647e
    BUG: 3599
    Reviewed-on: http://review.gluster.com/486
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit eede6ce87fc19878873e8320c172d1acb2deaa33
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Sep 22 10:26:02 2011 +0200

    geo-rep: disallow some special characters in url syntax
    
    - space is disallowed to make rsync target unambigous for gsyncd wrapper
    - *, ?, [ is disallowed so that we can tell away globs from urls
    
    Nothing too bad would happen without these restrictions, but this way
    gluster errs out early instead of producing some mystical error
    further down on the way.
    
    Change-Id: Idd4e68f7d91598a7a8e30ccbc6d395da570cdf2e
    BUG: 3610
    Reviewed-on: http://review.gluster.com/490
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 21eabe9bae81b3cc732fcf773fb5c1995f19d0d7
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Sep 22 10:12:24 2011 +0200

    geo-rep: add support to glob patterns with "geo-rep config"
    
    Change-Id: I0d54cea72e4363eab85ade774cc918081d8036e9
    BUG: 3610
    Reviewed-on: http://review.gluster.com/489
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b27b9d36de798bb18eaa95524f3900f9e17ce3e5
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Sep 20 16:20:18 2011 +0200

    geo-rep: implement IP address based access control
    
    - gsyncd gets allow-network tunable which is expected to
      hold a comma-separated list of IP network addresses
    - for IP addess matching, bring in ipaddr module from Google
      (http://code.google.com/p/ipaddr-py/, rev. trunk@225)
    
    This will let users control master's access to slave's volumes
    until we implement unprivileged geo-rep (delayed due to some
    technical issues). It's also needed for the completeness of
    our hardening efforts, as plain file slaves won't be able
    to work with an unprivileged gsyncd.
    
    Change-Id: I58431cba6592f8672e93ea89a5eef478905b00b9
    BUG: 2825
    Reviewed-on: http://review.gluster.com/488
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d7c9d2bfbd20727f90b0118c982ff9612aacacf2
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Sep 19 15:47:46 2011 +0200

    geo-rep: gsyncd: make sure path operations do not act outside the volume
    
    Change-Id: I2da62b34aa833b9a28728fa1db23951f28b7e538
    BUG: 2825
    Reviewed-on: http://review.gluster.com/462
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7e04913aa6f4ddb45e95099ef648564bf90da0b3
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Sep 13 13:12:38 2011 +0200

    gsyncd: control rsync target
    
    - require/perform rsync invocation with unprotected args
      (so that target is revealed to gateway program)
    - make use of some procfs wizardry to find gsyncd sibling
      and match rsync target against its working directory
    
    Change-Id: Iae1e39b0e61f22563c0f2a2e0605567e0d1902df
    BUG: 2825
    Reviewed-on: http://review.gluster.com/461
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2ab00369e7ef99d287dad5301d2f334dcfd67a70
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Sep 11 19:45:57 2011 +0200

    gsyncd: implement restricted mode and utility dispatch
    
    With this change, the suggested way of setting up a geo-sync
    slave is to use an ssh key with gsyncd as a forced command
    (see sshd(8)), or set gsyncd as shell. This prevents the master
    in executing arbitrary commands on slave (a major security hole).
    
    Detailed list the changes:
    - All gsyncd invocations that are not done by glusterd are
      considered unsafe and then we operate in so-called "restricted mode"
      (see below)
    - if we are invoked on purpose (ie. it's not the case that sshd forced
      us to run as frontend of a remote-invoked command), we execute gsyncd.py
    - if invoked by sshd as frontend command, we check the remote command
      line and call the required utility if it's among the allowed ones
      (rsyncd and gsyncd)
    - with rsync, we check if invocation is server mode and some other
      sanity measures
    - with gsyncd, in restricted mode we enforce the usage of the glusterd
      provided config file, and in python, we enforce operation in
      server mode and some other sanity checks
    
    Impact on using geo-rep the old way: remote file slave now also
    requires a running glusterd (to pick up config from).
    
    Missing: we not implemented check of the rsync target path.
    The issue of master being able to modify arbitrary locations
    is planned to be mitigated by using geo-rep with an unprivileged
    user.
    
    Change-Id: I9b5825bfe282a9ca777429aadd554d78708f1638
    BUG: 2825
    Reviewed-on: http://review.gluster.com/460
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 1098aaa51d2e3dca9e6c48ee1e9cb43bc87936f4
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Sep 2 19:03:33 2011 +0200

    geo-rep: rewrite gsyncd wrapper in C
    
    This rewrite does not change functionality;
    it's purpose is to prepare followup modifications which will let
    all slave side helper programs being dispatched to through
    gsyncd. The string processing that's required for that task would
    be too much cumbersome in shell.
    
    Change-Id: Ia7858aba5efeb5dcff16a918ea1c02253f0e49ab
    BUG: 2825
    Reviewed-on: http://review.gluster.com/459
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3672c989f369c5b57aff8d0d01fc221804ada6eb
Author: shishir <shishirng@gluster.com>
Date:   Mon Sep 19 18:23:04 2011 +0530

    Peer probe: Handle probe of friend with multiple hostname
    
    Currently, when a peer is probed with a different hostname already belonging
    to a cluster, a duplicate entry is created with uuid to set to 0.
    This leaves the peerinfo in a inconsistent state, and when a detach of
    this peer is issued, the correct entry gets removed.
    
    The fix is to identify a peer with a hostname not matching to the probed
    hostname and remove the incorrect entry.
    
    Change-Id: I2f6c02f505f4426871623a4a8b45a12996095098
    BUG: 3200
    Reviewed-on: http://review.gluster.com/456
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2e61c86ba89d546c7cab522b53d6b9c7f164cd8c
Author: Gaurav <gaurav@gluster.com>
Date:   Thu Sep 22 12:48:41 2011 +0530

    NFS : Posix compliance fixes.
    
    Change-Id: I4f1d8883a3eedee20557e306815674a6dc062bfe
    BUG: 1337
    Reviewed-on: http://review.gluster.com/487
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b8f2f460f9a5f977ef6debc2e59cae75324c95ca
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 19 13:01:26 2011 +0530

    statedump: add more memory accounting related stats
    
    * iobuf: add variable to keep count of total number of allocations
    * iobuf: include 'purged' and 'filled' arenas also in dump
    * mempool: more details added (with a name to tell why mem-pool
      is created)
    * memory-accounting: print number of allocs in each type
    
    this would give us much better understanding of the memory
    allocation pattern
    
    Change-Id: I117ac0c1da943a4cc91543a01963ba7940db2b5f
    BUG: 3567
    Reviewed-on: http://review.gluster.com/376
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5619b2dc4189e9de4a2327dc63ccb647f863f2b1
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Sep 21 12:06:14 2011 +0530

    glusterd: fix 'volume status' showing incorrect online status
    
    glusterd now checks if a brick process is running to set online status,
    instead of using brickinfo->signed_in. The earlier method used to show
    incorrect online status as brickinfo->signed_in was not updated when
    brick process was killed with SIGKILL
    
    Change-Id: Id5589ea8abbcffebe5c794e5a4adf4f0e6e489f0
    BUG: 3573
    Reviewed-on: http://review.gluster.com/476
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit aa7815c29a849346a75389f6ad15d8190f5a6710
Author: Rahul C S <rahulcssjce@gmail.com>
Date:   Tue Sep 20 17:44:07 2011 +0530

    cluster/distribute: validate buf before accessing.
    
    The macro to check & reset rebalance flags was accessing the iatt
    structure even in case of failures leading to null dereference.
    
    Change-Id: I518f4cc9086cecbe6cf791c8a351287fe3613650
    BUG: 3594
    Reviewed-on: http://review.gluster.com/472
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 8fc81caf43d491a49134e6491b813843e490bb99
Author: krishna <krishna@gluster.com>
Date:   Wed Sep 14 16:09:16 2011 +0530

    nfs: enhance NFS log messages.
    
    Change-Id: I6c2eaa2795756f515b5fb2ea5098d3dcb4ef77c4
    BUG: 3527
    Reviewed-on: http://review.gluster.com/433
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit abe47d434308e2ac5926fc8e292cced3688b7ca4
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Sep 21 17:11:49 2011 +0530

    Rebalance: Mount rebalance client with assert-on-child-down set to on
    
    This will prevent rebalance to be started when a brick is down, or
    stop rebalance if a brick goes down during a rebalance op.
    
    On restarting the rebalance once all the bricks are up, rebalance proceeds
    as usual.
    
    Change-Id: I196ae658c3a3856cce5314eca194e62d42171b9d
    BUG: 3574
    Reviewed-on: http://review.gluster.com/481
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit b274b8792c6bf6d95cad078fadad0ffe4c2bf43a
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 20 13:23:08 2011 +0530

    glusterfs protocol: handshake to log the version of the peer
    
    * As RPC program's name is just used for logging, we now have
      'PACKAGE_VERSION' part of the string, which gets logged in client
      side.
    * From client, we send the PACKAGE_VERSION in handshake dictionary,
      which gets logged on serverside handshake.
    
    The change doesn't break any compatibility between client or server
    as it would only enhance the logging part of handshake.
    
    Change-Id: Ie7f498af2f5d3f97be37c8d982061cb6021883ce
    BUG: 3589
    Reviewed-on: http://review.gluster.com/467
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 4a8981eb99c09d76872b8aa167863b49f74b52f2
Author: Lakshmipathi <lakshmipathi@gluster.com>
Date:   Tue Sep 20 13:06:11 2011 +0530

    build : rpm spec file changes
    
    Thanks to
    Scott Zahn <Scott@zahna.com>     - Fixed spec file to add the correct
                                       ldconfig path addition for i386 and
                                       x86_64.(BUG:2279)
    Persson <Persson@katamail.com>   - Fixed  without_georeplication macro
                                       (BUG:3541)
    JoeJulian <Joe@julianfamily.org> - Minor rpm cleanups.(BUG:3546)
    
    Patch  create the library references for both 64bit and 32bit rpms
    
    Change-Id: Ia281fa0d3d8b32ff19b74f379cda7ca9315a4beb
    BUG: 2279
    Reviewed-on: http://review.gluster.com/466
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 03591027b06c556baa95c6fa4569be0bff4adcd8
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 20 18:30:42 2011 +0530

    cluster/afr: Make local->child_up immutable
    
    Afr transaction performs lock, pre-op, op, post-op and unlock steps in that
    order. The child_up[] is overloaded with the information of where all
    the first two steps succeeded. This works perfectly fine for
    Transaction, but the locking/unlocking part of the code is re-used by
    data self-heal. In that each loop_frame does lock, rchecksum,
    read-from-source and write-to-sinks, unlock steps.
    
    Rchecksum fop assumes that the fop needs to happen on one source + all
    sinks and sets the call_count to that number. But if the lock step fails
    on any of the sinks it will mark the child_up of that child to 0, which
    will result in call_count mismatch and the frame will hang thinking that
    some more cbks need to come. When this happens loop_frame will never go
    to unlock step leading to hangs on that file.
    
    Change-Id: I3dd0449cc6193a980bacf637d935881f4b22210a
    BUG: 3597
    Reviewed-on: http://review.gluster.com/474
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 82d1a445b92526629d699f947a2d2bd029c8db75
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 21 12:20:34 2011 +0530

    glusterd rebalance: set the proper status as per command given
    
    for both 'migrate-data start' or 'migrate-data start force' commands
    the defrag status should start with 'migrate-data-started' state.
    
    Change-Id: Ic645bc764c4d24ab438187fb139c4a1c3ade8949
    BUG: 3593
    Reviewed-on: http://review.gluster.com/477
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 4c0efe75411112d6e386fe10a138ec2d9218b8b8
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 21 08:12:32 2011 +0530

    mgmt/glusterd: Create volfile in correct path
    
    Change-Id: Ie52e4b1a338282f2697e2ce374dd566d2c5cf5d1
    BUG: 3586
    Reviewed-on: http://review.gluster.com/475
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit b30f66e20d830daec057075d67f181e904984a27
Author: Venky Shankar <venky@gluster.com>
Date:   Tue Sep 13 22:11:33 2011 +0530

    geo-rep: gsyncd: add --ignore-deletes option
    
    When this option is set, a file deleted on master will not trigger
    a delete operation on the slave. Hence, the slave will remain as a
    superset of the master and can be used to recover the master in case
    of crash and/or accidental deletes.
    
    This options is not enabled by default.
    
    Change-Id: I9244d9dfa4f38f19436036f36bec0d9c3a1f7993
    BUG: 3552
    Reviewed-on: http://review.gluster.com/426
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>

commit e8b81f72d7a45ce443e72c45ae68952911deac50
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Aug 29 16:54:50 2011 +0530

    storage/posix: Filter custom getxattrs in lookup
    
    Change-Id: If948ff1b355ea4fd92036bcc43e7b32325aeb3e4
    BUG: 3470
    Reviewed-on: http://review.gluster.com/325
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cb2c6982bd6d588a91fa2827f95f0d9cf3ff2560
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 14 09:02:01 2011 +0530

    cluster/distribute: minor fixes in open file migration
    
    * incorporated Avati's comments on the first patch.
    * send proper stat information while unwinding
    
    Change-Id: I36982cec610753c241c372272620ab2bd581fd9f
    BUG: 3071
    Reviewed-on: http://review.gluster.com/408
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b5b0bb056391659802099908f4bccde5afdb9e34
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 20 11:03:32 2011 +0530

    features/locks: free the string allocated by inode_path
    
    Change-Id: I1b7d4059610713b92c4bb78676c3b48335e3a0fe
    BUG: 3468
    Reviewed-on: http://review.gluster.com/465
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8d4d8088c73f2ffc60b8e5c23a33e6b996fb5053
Author: Kaushal M <kaushal@gluster.com>
Date:   Tue Sep 6 17:18:20 2011 +0530

    glusterd: run 'volume top read-perf/write-perf' in different thread
    
    Runs the 'volume top read-perf/write-perf' operations in a different
    thread without blocking glusterd. Prvents glusterd from being
    unresponsive when large values of 'bs' and 'count' are given.
    
    Also increase cli timeout for top/profile commands , from 120s to 300s
    to allow large i/o top read-perf and write-perf to return result.
    
    Change-Id: I4b7de1d735f33643d836772db7f25133f112b75a
    BUG: 2720
    Reviewed-on: http://review.gluster.com/375
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit e0178776546f06646c11bcb1ea345f82436d73aa
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Sep 19 22:01:13 2011 +0530

    rpc:memcpy data of right size to auth params
    
    Change-Id: I6999e0a1463ee3475f7607990337326b3f008538
    BUG: 3587
    Reviewed-on: http://review.gluster.com/464
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit e163bc5b3ab062e3cb22b0386dbe056ab4a54952
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Aug 31 16:03:28 2011 +0200

    s@GFS_PREFIX"/sbin@SBIN_DIR@
    
    $sbindir is the install path for gluster* binaries,
    so this is what should be used in their invocation
    
    Change-Id: Ie748b4cbf59c3ee77f721ff6e0ab7151742ce0ab
    BUG: 2825
    Reviewed-on: http://review.gluster.com/458
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit b23d329608163ee2aa1aa89b907a5a6e50291464
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Mon Sep 12 17:29:47 2011 +0530

    glusterd: provide a option to start processes with valgrind
    
    By enabling the brick-with-valgrind option in glusterd,
    one can automatically start all bricks with valgrind monitoring
    them.
    
    Change-Id: Ib0a97a83c4461c0878454e96bc84462f6cad6bc8
    BUG: 3461
    Reviewed-on: http://review.gluster.com/311
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8ad4d3f53000724389db6003ca6d6d777b880017
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Mon Sep 19 16:43:50 2011 +0530

    glusterd/top: volume top succeeds on partial brickpath
    
    Rewrite of glusterd_volume_brickinfo_get in glusterd-utils.c
    An additional argument to glusterd_volume_brick_info_get_by_brick
    and glusterd_volume_brickinfo_get enables matching brick path in
    two ways: Complete or partial(ancestor and descendent paths matched).
    
    Change-Id: Ia87833a6f0c139599c3e40b59d60c64281b4084b
    BUG: 3271
    Reviewed-on: http://review.gluster.com/162
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 608f2d698569abc82cc671e81477e89e9c553bda
Author: Kaushal M <kaushal@gluster.com>
Date:   Mon Sep 19 15:13:43 2011 +0530

    cli: enable order checking stripe-replicate volumes
    
    This is a followup patch to  e378778686fca24934e76c41e6496b12162a5420
    Enables brick order checking for volumes of type stripe replicate.
    
    Change-Id: Ib9b090a3514d05bb7602c423de7d3123f107a3b5
    BUG: 2441
    Reviewed-on: http://review.gluster.com/455
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 39fee9a8f8264df61f77563acb048a441265afcf
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Mon Sep 19 14:25:47 2011 +0530

    glusterd: make sort portable
    
    fixed for fd leaking. reopening of file was not needed
    
    BUG: 3491
    Change-Id: I1351bdcaa41a5901574f5e779c33bf6f80a938f9
    Reviewed-on: http://review.gluster.com/453
    Reviewed-by: Csaba Henk <csaba@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 909f80181c9a6985c49964de4854f5d5460dbf09
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Mon Sep 19 13:22:54 2011 +0530

    protocol/client: minor log enhancements
    
    minor changes to the log enhancements of bug 3473.
    
    Change-Id: Id38d29db5a744e0ab7342d10ead6d16866228062
    BUG: 3473
    Reviewed-on: http://review.gluster.com/452
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit d70f640ea121643fadef2f19a33d18d81c9f5bb5
Author: Sachidananda Urs <sac@gluster.com>
Date:   Mon Sep 19 12:32:33 2011 +0530

    Fix typo in log message.
    
    Change-Id: Ia51ffe03c8b94ddfe21c6609bc0d54b5bd29eca7
    BUG: 3158
    Reviewed-on: http://review.gluster.com/392
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 02db3a0e457654b35c1a147403f1e99f691dcd52
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Sep 10 15:22:37 2011 +0530

    features/marker: Use appropriate loc struct to do removexattr on newpath after rename.
    
    Change-Id: I060e62c1fbb288179063a6d64d73bad1a6572661
    BUG: 3493
    Reviewed-on: http://review.gluster.com/390
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9895baf2719ac9911bc20ca54d0ff84f761baaed
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Fri Sep 16 14:03:40 2011 +0530

    cli: check wordcount to validate volume set help
    
    Change-Id: I93650af9fb29cffc48733d9bba5fd2fb580c44a1
    BUG: 3543
    Reviewed-on: http://review.gluster.com/436
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 0cb13b43c612dffe6aa8ba9367c5f808e725efff
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Mon Sep 12 11:11:56 2011 +0530

    glusterd: make sort portable
    
    The result of sorting the volume info file has
    been programmatically redirected, instead of using
    the -o option.
    
    Change-Id: Id789fab8dc92b254571a4fc7239e4872f3ac055f
    BUG: 3491
    Reviewed-on: http://review.gluster.com/395
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e378778686fca24934e76c41e6496b12162a5420
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Aug 3 18:12:21 2011 +0530

    cli : check for bad brick order while creating replicate volume
    
    gluster cli now checks the brick order when creating
    a replicate or distributed-replicate volume.
    If a non-optimal order is found the user is given a
    warning and asked if the volume creation can proceed.
    
    Change-Id: I38c4cb65bffb40ccf95319cf3f4f3423a4cdebe9
    BUG: 2407
    Reviewed-on: http://review.gluster.com/151
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 46a7adafe94b14778328d77a7f743fbce17341e3
Author: Kaushal M <kaushal@gluster.com>
Date:   Tue Aug 16 13:17:38 2011 +0530

    glusterfsd: enable max fetch attempts
    
    Enables usage of 'volfile-max-fetch-attempts' option of glusterfsd.
    Also, adds an option to 'mount.glusterfs' for setting the max fetch attempts.
    For a server with multiple ips, each call to gf_resolve_ip6() returns a
    different ip. Since gf_resolve_ip6() is called for each fetch attempt,
    this change also enables rrdns support for gluster.
    
    Change-Id: I3edadbf0ff43ff414b30eb50dd9ca4a6fd6b1089
    BUG: 2441
    Reviewed-on: http://review.gluster.com/239
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5de8c537936c547d8eafa3913e63a84646134f36
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 16 15:17:24 2011 +0530

    performance/quick-read: fix memory corruption.
    
      - macro QR_STACK_UNWIND destroys the stub present in local and hence no need
        of explicitly calling call_stub_destroy on it.
    
    Change-Id: Ib81c9a0d382765e783722b14fdbd7877086b1bec
    BUG: 3562
    Reviewed-on: http://review.gluster.com/439
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 003a578d9b324e769e231451a53688b48550e0f0
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Sep 15 02:29:54 2011 +0200

    libglusterfs: run: fix closing of redirection fd in child
    
    When run was doing a program invocation like "echo foo > foof",
    the file descriptor to foof was closed before stdout could be
    reopened to it.
    
    To fix this, we change the order of actions: first do redirections,
    then do the fd cleanup. This also simplifies code (as there are less
    fds which are exempt of the cleanup).
    
    Change-Id: I5f74e41f2999e59916a40c8a89d7fb730d808c27
    BUG: 2562
    Reported-by: Rajesh Amaravathi <rajesh@gluster.com>
    Reviewed-on: http://review.gluster.com/428
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Rajesh Amaravathi <rajesh@gluster.com>
    Reviewed-by: Rajesh Amaravathi <rajesh@gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 35bbb34a3f4a74f0d2288aacd984c71c7ebdfa3c
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Fri Sep 2 15:10:30 2011 +0530

    protocol/client: log enhancements
    
    * print paths wherever it is possible to log, to help debugging.
    * bring uniformity in log level.
    
    Change-Id: I2fa85b629de5dd0f0057ed96cba08ecb0ff1a798
    BUG: 3473
    Reviewed-on: http://review.gluster.com/328
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 9eec7900639684e5a2fd80b273437fefe6b5b930
Author: krishna <krishna@gluster.com>
Date:   Wed Sep 14 16:13:27 2011 +0530

    rpc: Use correct variable for volume-specific insecure ports check
    
    Change-Id: Ica59a3154c4e7d980d3477dd3879c7cebe92ad87
    BUG: 3515
    Reviewed-on: http://review.gluster.com/418
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 16a4d4352c762f6035e1a39f619d358ba7688502
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Sep 16 15:03:32 2011 +0530

    cli: if the create volume command does not contain bricks, exit gracefully
    
    Change-Id: I41f896d5a9c514994874b6e4e956d38fed742d4b
    BUG: 3571
    Reviewed-on: http://review.gluster.com/438
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 4ee093305a0237368118e425723792a028b02a94
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Sep 15 17:09:00 2011 +0530

    glusterd: profile cmd incorrectly reports all bricks down.
    
    If there are no bricks of a volume running 'local' to glusterd
    where the 'profile info' command is issued, glusterd incorrectly
    reports that all bricks of the volume are down.
    
    Change-Id: Idd703c991f0bcf59b76b9ef8f4ad8cd71960a55b
    BUG: 3553
    Reviewed-on: http://review.gluster.com/430
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 77cce4c7df9a61b599a27522696720e747714ff2
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Sep 15 18:14:53 2011 +0200

    rpc: fix up mountbroker xdr defs and regenerate headers
    
    Change-Id: I8a88d2b9228c3614ee7cbaf48782a419e6aee0f6
    BUG: 3482
    Reported-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-on: http://review.gluster.com/432
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 45f03a58a0fbfc1d5e647c764b10e37d0a9ebb26
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 8 14:06:32 2011 +0530

    Proactive self heal process implementation
    
    Change-Id: I96db0d94566ceabf1649f890318363f738c06553
    BUG: 2458
    Reviewed-on: http://review.gluster.com/403
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3bea46c1f232a4480e57ac482f92f7673af7034f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 7 21:26:41 2011 +0530

    dict: add reset function which empties the dict
    
    Change-Id: I267c81a129197534fb318671eafb76e144a15c8c
    BUG: 2458
    Reviewed-on: http://review.gluster.com/402
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 78dee45ef829296dbcb4cf28e06feb8e25458c91
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 6 13:56:03 2011 +0530

    debug/io-stats: Allow multiple children in graph
    
    Change-Id: Ie4fb75d8000ff95daa8bf9f6757926822de28a65
    BUG: 2458
    Reviewed-on: http://review.gluster.com/401
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 4a7d4dcd70bfc480ea20ae10d44257e56e86789c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 13 15:15:10 2011 +0530

     features/quota: explicitly create xattrs in marker_create_cbk
    
     - the earlier approach of creating quota related xattrs through
       side-effect of updating size and contribution values won't work,
       since when no contribution xattr is present, the updation process
       treats contribution value as zero and hence will be equal to size
       of freshly created files
    
    Change-Id: If9b2063b1ac3a4cf50d3fe2c81e907bc8eccb677
    BUG: 3531
    Reviewed-on: http://review.gluster.com/385
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@gluster.com>

commit 9a16332d518c6318b761b230a0e1bb8ce357228e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 9 17:14:41 2011 +0530

    features/quota: implement mknod fop.
    
    Change-Id: If8f2a0bb635160ee78f35787ee9f8a4db87ae8ac
    BUG: 3531
    Reviewed-on: http://review.gluster.com/384
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@gluster.com>

commit b57e956caaf4536218b3b55ae78b4597858bdfde
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 14 15:59:21 2011 +0530

    glusterfsd: log the package version just after log init
    
    helps getting output of 'glusterfs --version' from the users while
    debugging any issues/bugs.
    
    Change-Id: I4f15aca143c1e403c70409378afc9ed7a678b286
    BUG: 2346
    Reviewed-on: http://review.gluster.com/415
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7a153f17b1892ca8747d5b570d80795b4006790a
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 14 13:51:40 2011 +0530

    libglusterfs/common-utils: resolve_ip6() to take AI_ADDRCONFIG
    
    AI_ADDRCONFIG flag is needed for 'getaddrinfo()' call as hint so
    that while resolving a hostname, ip list will be taken from proper
    configured address family
    
    Change-Id: Iad6067ad64444d3930d5be593ca819a8de5fc0c1
    BUG: 3548
    Reviewed-on: http://review.gluster.com/414
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d705b28fd1bb066632854da493031118776d00df
Author: Venky Shankar <venky@gluster.com>
Date:   Tue Sep 13 11:36:55 2011 +0530

    GlusterFS Hadoop specific DSL for mountbroker
    
    Change-Id: Ie379992bdea0974c8c5e1a4d7bc3e87cefe0d256
    BUG: 3539
    Reviewed-on: http://review.gluster.com/404
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b039cb193eddc51c6f31bf9a230281faada475fe
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 13 16:54:24 2011 +0530

    glusterd rebalance: fix minor issues
    
    there were bugs introduced due to parallelizing rebalance op.
    
    * argument to dict_set_str () should be static as for the life of dict
    * uuid_utoa() output should not be considered as static
    
    * overloading 'volinfo->defrag' in other nodes is a overkill, just KISS
    
    Change-Id: I43d00c8e22beb2dd5c5f9824552f7337543b2255
    BUG: 2112
    Reviewed-on: http://review.gluster.com/407
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 25daa42911d2ff697880ee29c591cac5f2abebed
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 9 09:42:51 2011 +0530

    support for de-commissioning a node using 'remove-brick'
    
    to achieve this, we now create volume-file with
    'decommissioned-nodes' option in distribute volume, then just
    perform the rebalance set of operations (with 'force' flag set).
    
    now onwards, the 'remove-brick' (with 'start' option) operation tries
    to migrate data from removed bricks to existing bricks.
    
    'remove-brick' also supports similar options as of replace-brick.
    
    * (no options) -> works as 'force', will have the current behavior
             of remove-brick, ie., no data-migration, volume changes.
    
    * start  (starts remove-brick with data-migration/draining process,
              which takes care of migrating data and once complete, will
              commit the changes to volume file)
    * pause  (stop data migration, but keep the volume file intact with
              extra options whatever is set)
    * abort  (stop data-migration, and fall back to old configuration)
    * commit (if volume is stopped, commits the changes to volumefile)
    * force  (stops the data-migration and commits the changes to
              volume file)
    
    Change-Id: I3952bcfbe604a0952e68b6accace7014d5e401d3
    BUG: 1952
    Reviewed-on: http://review.gluster.com/118
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 17e57f27c714c94dd5d9fa91650f83d069f2f4e4
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Sep 12 15:51:42 2011 +0530

    mgmt/glusterd: check the availability of fuse for few glusterd operations
    
    Change-Id: I410cc6a86c32637566e5498f69f46cb40322e7fb
    BUG: 2715
    Reviewed-on: http://review.gluster.com/364
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 8778c0bf72cc28a56becf0fd989bf66df51fd8a3
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Aug 31 18:04:19 2011 +0530

    mgmt/glusterd: fail glusterd if gsyncd does not behave as expected
    
    Change-Id: Ic54220328f15c579dcf441de2aad8620751a97ef
    BUG: 2744
    Reviewed-on: http://review.gluster.com/331
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>

commit 58c5e9feae1fdf618bb120f4c8ea318cc628dd06
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 13 12:11:52 2011 +0530

    socket: provide proper arguments to getaddrinfo
    
    -----
    from 'man getaddrinfo' :
    
    If hints.ai_flags includes the AI_ADDRCONFIG flag, then IPv4 addresses
    are returned in the list pointed to by res only if the local system has
    at least one IPv4 address  configured, and IPv6 addresses are only
    returned if the local system has at least one IPv6 address configured.
    -----
    
    Change-Id: Ie30344daf1bb9d41ac58741b38e83af35cd8b5e9
    BUG: 2456
    Reviewed-on: http://review.gluster.com/405
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a07bb18c8adeb8597f62095c5d1361c5bad01f09
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 7 12:53:09 2011 +0530

    distribute rebalance: handle the open file migration
    
    Complexity involved: To migrate a file with open fd, we have to
    notify the other client process which has the open fd, and make
    sure the write()s happening on that fd is properly synced to the
    migrated file. Once the migration is complete, the client
    process which has open-fd should get notified and it should
    start performing all the operations on the new subvolume,
    instead of earlier cached volume.
    
    How to solve the notification part:
    
    We can overload the 'postbuf' attribute in the _cbk() function to
    understand if a file is 'under-migration' or 'migration-complete'
    state. (This will be something similar to deciding whether a file
    is DHT-linkfile by its 'mode').
    
    Overall change includes below mentioned major changes:
    
    1. dht_linkfile is decided by only 2 factors (mode(01000),
       xattr(trusted.glusterfs.dht.linkto)), instead of earlier
       3 factors (size==0)
    
    2. in linkfile self-heal part (in 'dht_lookup_everywhere_cbk()'),
       don't delete a linkfile if there is a open-fd on it. It means,
       there may be a migration in progress.
    
    3. if a file's revalidate fails with ENOENT, it may be due to file
       migration, and hence need a lookup_everywhere()
    
    4. There will be 2 phases of file-migration.
    
    -> Phase 1: Migration in progress
       * The source data file will have SGID and STICKY bit set in its mode.
       * The source data file will have a 'linkto' xattr pointing the
         destination.
       * Destination file will have mode set to '01000', and 'linkto' xattr
         set to itself.
    
    -> Phase 2: File migration Complete
       * The source data file will have mode '01000', and will be 'truncated'
         to size 0.
       * The destination file will have inherited mode from the source. (without
         sgid and sticky bit) and its 'linkto' attribute will be removed.
    
    4. Changes in distribute to work smoothly with a file which is in migration /
       got migrated.
    
    The 'fops' are divided into 3 categories, inode-read, inode-write and others.
    inode-read fops need to handle only 'phase 2' notification, where as, the
    inode-write fops need to handle both 'phase 1' and phase2. The inode-write
    operations will be done on source file, and if any of 'file-migration' procedures
    are detected in _cbk(), then the operations should be performed on the destination
    too.
    
    when a phase-2 is detected, then the inode-ctx itself should be changed to represent
    a new layout.
    
    With these changes, the open file migration will work smoothly with multiple clients.
    
    Change-Id: I512408463814e650f34c62ed009bf2101d016fd6
    BUG: 3071
    Reviewed-on: http://review.gluster.com/209
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 09eeaf4e68c225b8e5ccc0a9b4f10f8c4748e205
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Aug 24 23:01:31 2011 +0200

    geo-rep: partial support for unprivileged gsyncd via mountbroker
    
    gsyncd:
      - mounting code is split to a direct and a mountbroker based backend
      - option gluster-command gone
      - new options: gluster-params, gluster-cli-options, mountbroker
      - mountbroker mount backend is used if either a mountbroker label
        is given through the mountbroker option, or if gsyncd is
        unprivileged; in this case the username is used as label
      - have gluster cli invocations log to stderr so that we don't
        hit a permission issue with the logfiles
    glusterd:
      - do gsyncd pre-config with new options
      - add option geo-replication-log-group, so if that specified
        geo-rep logfile directories are given to that group (and
        thus members of the given group can do logging there)
    
    This is just WIP as geo-rep relies on trusted extended attributes
    and those are not accessible for unprivileged users. Even if we
    solved this issue, glusterd security settings are too coarse,
    so that if we made it possible for an unprivileged gsyncd
    to operate, we would open up too far.
    
    Change-Id: Icd520b58cbadccea3fad7c0f437b99de1e22db14
    BUG: 2825
    Reviewed-on: http://review.gluster.com/399
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 37ac355cbbd36497f914905615bffb3e35805f0a
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Jul 30 17:50:22 2011 +0200

    glusterd / cli: mount-broker service
    
    Mountbroker is configured in glusterd volfile through a DSL
    which is restriced enough to be able to appear in the role
    of the value of a volfile knob.
    
    Basically the DSL describes set-theorical requirements
    against the option set which is sent by the cli (in the
    hope of getting a mount with these options).
    
    If the requirements meet and the volume id and the uid
    who is to "own" the mount can be unambigously deduced from
    the given request, glusterd does the mount with the given
    parameters.
    
    The use case of geo-replication is sugared by means of volume
    options which then generate a complete mount-broker option set.
    
    Demo:
    
    - add the following option to your glusterd volfile:
    
        option mountbroker-root /tmp/mbr
        option mountbroker.fool EQL(volfile-id=pop*|user-map-root=*|volfile-server=localhost)&MEET(user-map-root=john|user-map-root=jane)
    
    - before starting glusterd, create /tmp/mbr owned by root with mode 0755
    
    - with cli, do
    
       $ gluster system:: mount fool volfile-id=pop33 user-map-root=jane volfile-server=localhost
    
    - on succesful completion (volume pop33 exists and is started, jane is a valid username),
      the mount path will be echoed to you
    
    - you can get rid of the mount by
    
       $ gluster system:: umount <mount-path>
    
    Change-Id: I629cf64add0a45500d05becc3316f67cdb5b42ff
    BUG: 3482
    Reviewed-on: http://review.gluster.com/128
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 78170472e6c7f0bce95ab035cc4ed86ec662e80d
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Jul 30 16:45:50 2011 +0300

    add --user-map-root option
    
    This makes client fake that given user is a superuser,
    by changing FUSE requests coming with uid of user so that uid
    is set to 0.
    
    User can be given in numeric form, in which case it's treated
    as an uid directly, or else it's tried to be resolved to an
    uid with getpwnam(3).
    
    Implies --acl.
    
    Change-Id: I2d5a3d3e178be7ffdf22b46a56f33a7eeaaa7fe1
    BUG: 3242
    Reviewed-on: http://review.gluster.com/127
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 32b96d66890a16fd23c8ae065297c7a98097d340
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Jul 23 12:16:07 2011 +0200

    cli: add --log-{file,level} options
    
    Apart from diagnostic purposes, it's needed when cli is ran by
    unprivileged user who most likely has no write access to the
    canonical log file.
    
    Change-Id: Ib9d1a31711966ff1efe2592fbc0a911820cf8ee3
    BUG: 3242
    Reviewed-on: http://review.gluster.com/95
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 3d67836dba4f5a94f33e9ac13b7ebbf01344ac37
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Jul 23 12:14:48 2011 +0200

    cli: fix option parsing bug which implied that only a single option can be used
    
    Change-Id: I89467d00030f4714568ef63650ecef0aef1bf753
    BUG: 3242
    Reviewed-on: http://review.gluster.com/94
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d58382182ee53fcc83ec04f211c000a5a4db9a0b
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Jul 15 11:44:56 2011 +0200

    cli: reimplement "--version" without excess bloat
    
    Change-Id: I787d241e72b6a6c43db96c220d68fe369bb700a4
    BUG: 3242
    Reviewed-on: http://review.gluster.com/93
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 74bf2c1fc5d7377472d8c6ba8e27a333fc618899
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Jul 15 11:34:35 2011 +0200

    Revert "cli: Only admin should run gluster CLI"
    
    This reverts commit 8d64ca70b4c2467d4ed8c76a9eae385abdebd7a7.
    
    Change-Id: Id2c6b491c7dd133510380f576ad59655a01d6121
    BUG: 3242
    Reviewed-on: http://review.gluster.com/92
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 36059b73949a1eee32a3b2aa16b09263628ff050
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Jul 15 11:34:25 2011 +0200

    Revert "cli: gluster --version implementation"
    
    This reverts commit e93b270e8d09fc9d36a39b22987d3a172197e73b.
    
    Conflicts:
    
    	cli/src/cli.c
    
    Change-Id: Ibc0f6f752f713b15afc8b5458be5045ecb21235e
    BUG: 3242
    Reviewed-on: http://review.gluster.com/91
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e139eeeb627368112aa1341d2f0ef6770dd7078e
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Aug 10 20:04:20 2011 +0300

    gsyncd: python3 compat fixes
    
    Also add __codecheck script which can verify if source is OK at the
    syntactical level with a given Python interpreter.
    
    Change-Id: Ieff34bcd3efd1cdc0e8f9a510c05488f35897bbe
    BUG: 1570
    Reviewed-on: http://review.gluster.com/320
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit f3081a22740c70485c50d3837fa93da5fd843f26
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Aug 15 03:17:18 2011 +0300

    glusterd: fix cleaning up of runner object
    
    in lack of that, if geo-rep component is not installed, glusterd got a zombie child
    
    Change-Id: Ic4a2a4ffc943de68dd02db76a32b1618821ddf56
    BUG: 2744
    Reviewed-on: http://review.gluster.com/317
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 417de9db670650edd96e82a6e43087bea49deeee
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Sep 5 20:14:21 2011 +0530

    rpc: Need to keep ref when handling cbk in call_bail.
    
    Change-Id: Ic944599cfa2696a0ae77105185d49fb510ce6fec
    BUG: 3511
    Reviewed-on: http://review.gluster.com/361
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5d03ebd31f2984614ecdc8f117bd4599ade497d1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Sep 12 11:45:37 2011 +0530

    glusterd: free the allocated string to avoid memory leak
    
    Change-Id: I520abf3c57a15be8bb7dd1e92ad0b049ef5c8970
    BUG: 3341
    Reviewed-on: http://review.gluster.com/394
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 225dd7da8959c78331d16ba2c2a955b1432bc873
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Aug 31 13:02:21 2011 +0530

    protocol/client: avoid code duplication in fd based operations
    
    Change-Id: I012f78bac8ba82333628c59ef51d5e5f43d05ac7
    BUG: 3158
    Reviewed-on: http://review.gluster.com/329
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a2ef31b01537d8edd5ecf3738967704b0a19b137
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Aug 22 22:37:43 2011 +0530

    features/marker: unref the local incase of errors before unwinding
    
    Change-Id: I4dcad7ddf84bf98b4b7f4a0e407a418426674280
    BUG: 2784
    Reviewed-on: http://review.gluster.com/299
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 02b30e294b46cf54edf005db5ce5b0c2dc75919f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Sep 9 13:17:10 2011 +0530

    mgmt/glusterd: volume set help-xml format change
    
    Change-Id: I503364c855d52605e301f4d3c205af6c9fc0e1df
    BUG: 3366
    Reviewed-on: http://review.gluster.com/380
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 5efdbef0d74359122dbf76539e0975bea691456a
Author: Junaid <junaid@gluster.com>
Date:   Fri Sep 9 14:35:57 2011 +0530

    features/marker-quota: Prefix the function names with mq (marker-quota).
    
    This is to fix to bug marker translator and quota translator cannot co-exist in same process.
    
    Change-Id: I9f132b663f03641f4f2c7e168df8400adbc5570f
    BUG: 3020
    Reviewed-on: http://review.gluster.com/381
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit a0695e0524cc61d05156b66ebe3542870712daae
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 7 13:50:19 2011 +0530

    cluster/afr: perform self-heal with least priority
    
    Change-Id: Id8a1dffa3c3200234ad154d1749278a2d7c7021b
    BUG: 3502
    Reviewed-on: http://review.gluster.com/336
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 85a2f0ec5021d53f34fe1630028f413835abd31e
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 7 12:46:30 2011 +0530

    glusterd rebalance: make co-operate with all other 'op'
    
    that way, we can share the rebalance state with other peers
    and can prevent confusion/conflicts when multiple rebalances
    are done by different peers.
    
    Change-Id: I24159e69332644718df7314f6f1da7fce9ff740e
    BUG: 2112
    Reviewed-on: http://review.gluster.com/343
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 77eb7bdfd02f2ba61847fb9c35e9e19e3da4fcc4
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 8 00:34:32 2011 +0530

    cli: 'gluster create volume' - improve option parsing
    
    now 'replica' 'stripe' and 'transport' options can be given in any order
    
    Change-Id: Ied992ae55e86028bd4f2d662ebd246db138d4548
    BUG: 3521
    Reviewed-on: http://review.gluster.com/370
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0a2de8337e7111d9cb860329d83b5aae3ecacd2f
Author: Junaid <junaid@gluster.com>
Date:   Wed Sep 7 17:36:09 2011 +0530

    features/marker-quota: Perform xattr related operations with root permissions in rename fop.
    
    Change-Id: Id9ac1ecdd9753377c9eb24464f51dcbdc0cd2821
    BUG: 3194
    Reviewed-on: http://review.gluster.com/367
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f655fa043fc65ecad1d633a52a40a4c20ff18c97
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Sep 2 15:59:40 2011 +0530

    performance/io-threads: treat -ve pid as request for fop with least priority
    
    Change-Id: Ib6730a708f008054fbd379889a0f6dd3b051b6ad
    BUG: 3502
    Reviewed-on: http://review.gluster.com/335
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 550148f3bb3505335909cde9e937c2362a1e67e3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Sep 2 08:50:48 2011 +0530

    cluster/afr: Make data selfheal trigger to be configurable.
    
    By default, lookup triggers data self-heal but that is not the preferred way
    of operating replicated volumes. We would like the data self heals to be
    triggered in open instead.
    Number of back-ground self-heals allowed is 16 and lookups block until
    self-heal is completed. We want to prevent blocking in fops. We can not make
    lookups independent of self-heal frames because when there are gfid conflicts
    the decision of which file is correct is determined in self-heal phase.
    So in afr, lookup self-heal is going to guarantee name space consistency
    and open/fd fops will take responsibility for data consistency, these
    are non blocking. The user needs to set the option cluster.data-self-heal
    "open" for this behavior.
    
    Change-Id: If9463cdb9ebac114708558ec13bbca0270acd659
    BUG: 3503
    Reviewed-on: http://review.gluster.com/334
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 4d2afaae2f3c42b710acf8c7ebdb4b50d502b813
Author: Anand Avati <avati@gluster.com>
Date:   Wed Aug 31 22:57:34 2011 +0530

    posix-acl: configurable super user ID
    
    In configurations with a uid mapper, super user ID could be mapped
    to a non-zero value. Hence making it configurable in access control
    would be necessary for proper super-user semantics.
    
    Change-Id: I51e8e0395680e9b96a99657a0af547659bd9affe
    BUG: 2815
    Reviewed-on: http://review.gluster.com/332
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit c83856797fd55fa59c885ba5efd3ac912fcb9a96
Author: Anand Avati <avati@gluster.com>
Date:   Tue Aug 16 12:56:21 2011 +0530

    cluster/afr: eager locking of FD writes
    
    This patch is a change in the way write transactions hold a lock
    which optimizes the case of sequential writes from a single writer.
    
    Lock phase of a transaction has two sub-phases. First is an attempt
    to acquire locks in parallel by broadcasting non-blocking lock
    requests. If lock aquistion fails on any server, then the held locks
    are unlocked and revert to a blocking locked mode sequentially on
    one server after another.
    
    The change in this patch is to make the initial broadcasting lock
    request attempt to acquire lock on the entire file. If this fails,
    we revert back to the sequential "regional" blocking lock as before.
    
    In the case where such an "eager" lock is granted in the non-blocking
    phase, it gives rise to an opportunity for optimization. i.e, if
    the next write transaction on the same FD arrives before the unlock
    phase of the first transaction, it "takes over" the full file lock.
    Similarly if yet another transaction arrives before the unlock phase
    of the "optimized" transaction, that in turn "takes over" the lock
    as well. The actual unlock now happens at the end of the last
    "optimzed" transaction.
    
    Any operation which arrives before the unlock phase of the previous
    transaction is a potential candidate to become an "optimized"
    transaction. In cases where the previous transaction had aquired
    lock as a "regional" blocking lock, and the next transaction comes
    in before its unlock phase, then it would not be an "optimized"
    transaction.
    
    Implied assumption
    ------------------
    
    Since two or more transactions can now operate within the same
    large lock, there is a possibility that overlapping transactions
    can arrive at oppoosite orders on the servers. However in the
    larger picture this is not possible as write-behind already
    ensures that no two overlapping writes on an inode are in transit
    at the same time. Overlapping writes across clients are not a
    problem as they compete at locks anyways.
    
    Theoretical benefits and potential harms
    ----------------------------------------
    
    In case of a single writer: The benefits are large for sequential
    writes. In the best case the entire file write can happen with just
    one lock and unlock per server, provided writes are coming in fast
    enough and getting pipelined by write-behind soon enough (which is
    usually the case). If the writes are not coming in fast enough, then
    the optimization "kicks in" for only those subsets of writes which
    are close enough to get "piggybacked". For random writes the benefits
    are the same as well. In any case the overall performance is better
    than or equal to the performance without this optimization for a single
    writer.
    
    In case of multiple writers: When multiple writers are not writing
    concurrently, there is no negative performance impact. When multiple
    writers are writing concurrently to the same region, there is no
    negative impact either, as they were previously getting arbitrated
    at the locks translator too. In the case of multiple writers writing
    to different regions concurrently, there will be an increased number
    of "failovers" from failed parallel non-blocking to sequential blocking
    regional locks. This above "worst case" has a simple workaround that
    as soon as we detect > 1 open-fd-count in lookup xattr, we can disable
    this optimization on those fds.
    
    Beneficial side-effects
    -----------------------
    
    There is another similar optimization in AFR for changelogs which goes
    by the name of "changelog-piggybacking". That works in a similar way where
    pending flags get 'taken over' or 'piggybacked' by the next transaction
    if its 'pre-op' phase kicks in before the 'post-op' phase of the
    previous transaction. It has been observed that this changelog-piggybacking
    optimization gives a saving of about ~55% savings of xattr calls hitting
    the wire, measured across various types of network interfaces. The side
    effect of this eager-lock optimization is that it gives an almost 100%
    saving of xattr calls by making the optimistic-changelog work much more
    efficiently as it gives a wider overlap of the xattr phases of two
    consecutive transactions.
    
    Change-Id: I41c02eb3b64c14c68ef66a344610ec3f024cd59d
    BUG: 3409
    Reviewed-on: http://review.gluster.com/240
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 73ae561db9054c67ce120eb87fa955943bdc06bd
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Tue Sep 6 17:29:31 2011 +0530

    storage/posix: posix getxattr log enhancement
    
    Now the key is logged with getxattr failure.
    
    Change-Id: I96a9234cf138ae0922dc403e2fddcd4df0d89df8
    BUG: 3283
    Reviewed-on: http://review.gluster.com/373
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit d7b1463bf35a9c5ac30456d143cb4b67a03a93a6
Author: Rajesh Amaravathi <rajesh.amaravathi@gmail.com>
Date:   Mon Aug 29 10:30:56 2011 +0530

    mount/nfs: Gluster nfs crashes with subdirectory mount
    
    Glusterfs used to crash trying to dereference a NULL
    pointer. Also, in mnt3_resolve_export_subdir, volume
    name was prefixed to sub directory exported, resulting in
    mount fail of sub directory. Fixed both issues.
    
    Change-Id: I746f0c244b4cbf03033d73ac3e40518762d76385
    BUG: 3481
    Reviewed-on: http://review.gluster.com/323
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 51138e1cbf602e16011768040440cf829367c40c
Author: Pavan T C <tcp@gluster.com>
Date:   Wed Sep 7 18:05:57 2011 +0530

    Save the mode flags set by the application when ACLs are in use
    
    While inheriting the ACLs from a directory that has default ACLs, make sure
    that the mode flags set by the application are saved. It is required to
    inherit only the Read, Write and Execute permissions while leaving the others
    viz. setuid, setgid and sticky bit untouched hence honouring the requests made
    by the application during create operations (mknod, mkdir et al).
    
    For a description of the problem, root cause and evaluation, refer:
    http://bugs.gluster.com/show_bug.cgi?id=3522
    
    Change-Id: I994077fb321a35d8254f0cc5a7de99a17ec40c47
    BUG: 3522
    Reviewed-on: http://review.gluster.com/368
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 7d4560cbcdcae0d74cf486c544d5eb58775da51f
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Aug 10 05:02:43 2011 +0300

    gsyncd: do the homework, document _everything_
    
    Change-Id: I559e6a0709b8064cfd54c693e289c741f9c4c4ab
    BUG: 1570
    Reviewed-on: http://review.gluster.com/319
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>

commit d39a7fad09a6b4abcb23d132fd7dfdf0d440e928
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sat Sep 3 14:51:45 2011 +0530

    nfs3: Resolve entry vs. hash conflict at same dir depth
    
    Intro Note
    ==========
    The current code in hard fh resolution takes the first-match approach, i.e.
    which ever dirent either matches the hash or matches the gfid first
    is the one chosen as the result for the next step of fh resolution. In
    the latter case, i.e., dirent matches the gfid, we the next step is to
    conclude the fh resolution by returning the entry whose gfid matched.
    In the former, i.e., the hash matches the dirent, we choose the hash-matching
    dirent as the next directory to descend into, for searching the file to be
    operated upon.
    
    Problem
    =======
    When performing hard fh resolution, there can be a situation where:
    
    o the hash of the primary entry,i.e. the entry we're looking for and the hash
    of another sibling directory, match. Note the use of "sibling", meaning both
    the primary entry and the hash matching one are in the same directory, i.e.,
    their filehandle.hashcount will be same.
    
    o the sibling directory is encountered first during the dir search.
    
    Because of the current code described in "Intro", we'll end up descending into
    the sibling directory even though the correct behaviour is to ignore this and
    wait till we encounter the primary entry in the same parent directory.
    
    Once we end up descending into this sibling directory, the directory depth
    validation check fails. The check fails because it notices that the resolution
    is attempting to open a directory that is deeper in the fs tree than the file
    we're looking for. When this check fails, we return an ESTALE. So basically, a
    false-positive results in an estale to Specsfs.
    
    This is not a theoretical situation. Me and Avati saw this on specsfs test
    where sfs created terabytes-sized file system for its tests. The number of
    files was so huge in a single directory that the hashes of two entries ended up
    colliding.
    
    Change-Id: I4a6df11d326a67a507b1cd716c2c8e00b5a858a4
    BUG: 3510
    Reviewed-on: http://review.gluster.com/357
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shehjar Tikoo <shehjart@gluster.com>

commit 694ef54978f382507a5127ce66da7770929ba2c2
Author: Jeff Darcy <jdarcy@redhat.com>
Date:   Wed Sep 7 20:03:24 2011 -0400

    Eliminate many "var set but not used" warnings with newer gcc.
    
    This fixes ~200 such warnings, but leaves three categories untouched.
    
    (1) Rpcgen code.
    
    (2) Macros which set variables in the outer (calling function) scope.
    
    (3) Variables which are set via function calls which may have side effects.
    
    Change-Id: I6554555f78ed26134251504b038da7e94adacbcd
    BUG: 2550
    Reviewed-on: http://review.gluster.com/371
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 81530d227deb52af38c7df770aef2200b9de539f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 7 20:46:20 2011 +0530

    glusterd: send the 'stripe-count' value to peer during handshake
    
    without which, if a peer is added after volume of type 'stripe-replica'
    is created, it won't be reflected in the newly added peer.
    
    Change-Id: I77ee6aa3f33994bd4c6dbfefd853cc7e7491c1db
    BUG: 3523
    Reviewed-on: http://review.gluster.com/369
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 34be428d5640a0ad4c47a05ee3e716189b4a54ed
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 25 17:51:18 2011 +0530

    glusterd: fail the 'peer probe' if the first connect attempt fails
    
    so 'gluster peer probe' command doesn't hang till timeout (120s),
    instead it will send the proper error msg to client.
    
    Change-Id: I398fa16d526f869f1d27eeb57aeb7ee4451fbecd
    BUG: 1852
    Reviewed-on: http://review.gluster.com/342
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit f0f3b040dfa062021d3a193e5a19c380eb5e908d
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Aug 29 17:53:24 2011 +0530

    modify to the way we used XDR definitions files (.x files)
    
    Earlier:
    step 1: copy the existing <xdr>.x files to /tmp
    step 2: generate '.[ch]' files using 'rpcgen <xdr>.x'
    step 3: check diff with the to the existing files, add only your part
            of changes back to the original file. (ignore other changes).
    step 4: there is another file to write wrapper functions to convert
            structures to/from XDR buffers, update it with your new structure.
    step 5: use these wrapper functions in the newly written procedures.
    step 6: commit :-|
    
    Now:
    step 1: update (mostly adding only) the <xdr>.x file
    step 2: run '<path-to-src>/extras/generate-xdr-files.sh <xdr>.x' command
    step 3: implement rpc procedure to handle the request/response.
    step 4: commit :-)
    
    Change-Id: I219f9159fc980438c86e847c6b030be96e595ea2
    BUG: 3488
    Reviewed-on: http://review.gluster.com/341
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit f78c8253d7fb75762effcf64683cbce10783a55b
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Aug 28 12:53:12 2011 +0530

    glusterfs protocol: bring in variable sized iobuf support
    
    is a step towards reducing glusterfs memory footprint. should also
    help a bit in overall performance.
    
    Change-Id: I074d5813602b2c960d59562e792b3dc6e43d2f42
    BUG: 3475
    Reviewed-on: http://review.gluster.com/322
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 10d49cf0878e96301ea366276e27e91b5527483e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Sep 3 14:13:06 2011 +0530

    cluster/afr: Prevent double big lock when data self-heal loops are not spawned
    
    The steps in normal data self heal:
    1) take big lock by self-heal frame. Get the xattrs/stat to decide
    source, sink information.
    2) spawn loop frames which perform self-heal by taking small locks on
    the file. Every time a new lock is taken and the old lock is released.
    3) Before releasing the final small lock a big lock is taken by the
    self-heal frame, and unlock on small-lock. Erasing of the pending xattrs
    happen then the big unlock happen and that is the end of the data self-heal.
    
    When a data self-heal is needed for a file and the fop
    that triggers the self-heal is open with O_TRUNC. Fuse sends open then
    an explicit truncate for this. Open triggers the self-heal but by the
    time it tries to spawn the loops the file size is truncated to 0, so
    no loops are formed.
    These are the steps:
    1) Take big lock by self-heal frame. Get the xattrs/stat to decide
    source, sink information.
    2) loop frames are not spawned. The big lock is not released.
    3) One more big lock is taken by the same self-heal frame, Erasing of
    the pending xattrs etc happen, now it does two big unlocks, but after
    the first unlock, the information on which the locks were performed is
    forgotten, so the next unlock becomes a no-op. So there is a stale big
    lock on that file preventing further writes.
    
    As a fix, if the loops are not spawned, use the previous big lock to
    perform the rest of the operations needed in completing the data
    self-heal. No need to have one more big lock.
    
    Change-Id: Id03171269594e447b2b6d1331e362d83bd1e3430
    BUG: 3506
    Reviewed-on: http://review.gluster.com/339
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit f1fec244b043fc74999692b181d321827daf8677
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Aug 31 10:06:45 2011 +0530

    cluster/afr: Bring down the self-heal window size to 1
    
    This is brought in an effort to be nice to the system resources when
    self-heal is in progress.
    
    Change-Id: I123f1eb4d8000613a35c0117f0aa27f926f3a921
    BUG: 3503
    Reviewed-on: http://review.gluster.com/333
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 992e580df4a38bb96b0114a3b033d0dc0b8425b7
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 23 10:25:35 2011 +0530

    mgmt/glusterd: code re-structuring
    
    created new files per operations, (or group of operations)
    
    Change-Id: Iccb2a6a0cd9661bf940118344b2f7f723e23ab8b
    BUG: 3158
    Reviewed-on: http://review.gluster.com/281
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 0504c5c24a8d8329321b9d5cdbc873c0fda32935
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Aug 3 11:30:20 2011 +0530

    glusterd: Removed local cli lock
    
    This change contains,
    - removal of the local cli lock used to serialize
    cli ops to a glusterd.
    - glusterd's state-machine can handle competing 'lockers' with
    guaranteed progress.
    - flush cluster lock on 'owner' disconnecting and as 'owner',
    send unlock to all on first peer disconnect.
    
    Change-Id: I25961436b0790b4196f2b3438b105c37279399ad
    BUG: 3320
    Reviewed-on: http://review.gluster.com/123
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit e795fcf2895496ad5412bfd4ac50a358567ecabb
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Aug 25 14:46:52 2011 +0530

    performance/io-threads: Introduce new priority and priority-thread-limits
    
    Change-Id: I7b4e7c467b833bc5896808e6e1d1b1a0322c4fdb
    BUG: 3483
    Reviewed-on: http://review.gluster.com/318
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cd567c063ec25b280d3fb5686a69b068c2d6d6df
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Aug 10 16:58:38 2011 +0530

    mem-pool: Make mem-pool ptr avialable in ptr
    
    The header of the ptr returned from mem-pool will now store the
    mem-pool ptr it belongs to. mem_put will now take only the pointer
    to be freed.
    
    Also, changing MALLOC call to GF_CALLOC in mem_get when we run out
    of entries in mem-pool. This also will have the header information
    saved.
    
    Change-Id: I3de182663a7f5b49c9e9425e9531775b70bdff67
    BUG: 3390
    Reviewed-on: http://review.gluster.com/205
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 9c68f3b53ffd27ea03e90da883c43e84bf94dd15
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Aug 24 12:57:18 2011 +0530

    rdd: changes in rdd.c and whitespace cleanup
    
    Change-Id: Ic117c6a3f9234a0181db1a106ef8a6574248f010
    Reviewed-on: http://review.gluster.com/313
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit b617b89372f9f6cb5031dfb8513029a7fa490f73
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Jul 15 02:45:18 2011 +0200

    gsyncd: refine command invocation
    
    Use subprocess module instead of os.spawn* / ad-hoc fork/exec.
    With this, we do now:
    
    - close uneeded files in children
    - watch childrens' stderr:
      - have a thread which collects childrens' stderr into a ring buffer
        (so that stderr pipe doesn't get stuffed)
      - on command failure show stderr
    - distinguish between rsync exit values, tolerate only partial errors
    - if connection is broken to slave, show ssh/slave gsycd's stderr
    
    Change-Id: Ia92f57b5bdfa47f8c44375c50cf279006a0bf69b
    BUG: 2946
    Reviewed-on: http://review.gluster.com/85
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Kaushik BV <kaushikbv@gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>

commit f9b09cd2be47c044c1396e70724a427ef46f8b81
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Jul 25 11:53:55 2011 +0300

    glusterd: do preparative gsyncd invocations with proper logging
    
    Change-Id: I28de4cce140faf1b35ecdc5cbd408f21c9926341
    BUG: 3231
    Reviewed-on: http://review.gluster.com/96
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit f16a44f94f76e6c677cee37090d059e8bb5443f5
Author: Kaushal M <kaushal@gluster.com>
Date:   Fri Aug 19 15:07:36 2011 +0530

    cli: "profile info" output improvements
    
    Some changes to profile info output.
    
    Change-Id: I94a4bec1ca1c0670b3d9643f8321683b59c665aa
    BUG: 3028
    Reviewed-on: http://review.gluster.com/260
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 9848ac8bf7a6854e9d4dee2dcb53621c67b33d6e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Aug 24 12:49:48 2011 +0530

    features/locks: avoid using reqlock to prevent race
    
    Change-Id: Id8613f9641f748f996062342878070ba8fb27339
    BUG: 2473
    Reviewed-on: http://review.gluster.com/312
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>

commit 7f459fc826346c33a58412fb45a6781c5fd1cc0d
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jul 7 02:02:50 2011 +0200

    glusterd / geo-rep: in status, display slave URLs in simpler normalized form
    
    Ie. instead of writing out the fully expanded canonical URL like
    
      ssh://root@192.168.3.4:gluster://127.0.0.1:bar
    
    we just display
    
      ssh://root@starship::bar
    
    Change-Id: I2bd70650cbc9973d925f652bccb163d391e406c9
    BUG: 2536
    Reviewed-on: http://review.gluster.com/79
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>

commit b827cdb230b8253c53d646793dd8f21df8202d41
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Aug 23 13:47:41 2011 +0530

    xlator: fix for the volume set help crash
    
    Change-Id: I1649ed61b13b935d714ca024e6883f3903c5edeb
    BUG: 3460
    Reviewed-on: http://review.gluster.com/310
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 6e02c879ad847b760a05f9afd3fddc9f152bda23
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Aug 23 12:32:36 2011 +0530

    performance/stat-prefetch: fix memory leak
    
    Change-Id: I84580e297ba93a9a093c2e3432ea52e3c0db4a1a
    BUG: 3467
    Reviewed-on: http://review.gluster.com/307
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit dd996d529d155143e3ad49dc3b30461d9eb3ff43
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 23 11:44:05 2011 +0530

    cluster/distribute: unwind the proper dict in getxattr_cbk
    
    without which, quota would get confused about the total size
    
    Change-Id: I0fb822ee67e3c1585f783ae35292fe71c47ee249
    BUG: 3421
    Reviewed-on: http://review.gluster.com/304
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 601f5725a0a2e4855d9a4a952709e5c0cadbd846
Author: Junaid <junaid@gluster.com>
Date:   Mon Aug 22 17:32:08 2011 +0530

    features/marker-quota: Fix invalid reads in readdir_cbk.
    
    Change-Id: Icc1e9dc039f1f2d7ee94c689779a715a69d373fa
    BUG: 3389
    Reviewed-on: http://review.gluster.com/296
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d9ead57226faf82f3f1375a29e06d348625ba905
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 22 14:55:09 2011 +0530

    mgmt/glusterd: Initialize local variable in volgen
    
    Change-Id: I84b4f7c9c2787334ce67e5c3e0534953b691c8e0
    BUG: 3460
    Reviewed-on: http://review.gluster.com/295
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>

commit 4f9396545ba9c91d4bebfc81148c0082237141f4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Aug 22 13:54:15 2011 +0530

    cluster/afr: Perform flush on all the children involved in self-heal
    
    Change-Id: I66362a3087a635fb7b759d7836a1f6564a6a7fc9
    BUG: 3456
    Reviewed-on: http://review.gluster.com/294
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b9ae4b19da2898fa610d1bfd4b9e5829acabb121
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Aug 22 12:14:22 2011 +0530

    cluster/afr: Change definition of stale child
    
    The code is checking for priv->child_up[i], which can change while the fop
    is in progress. Since pending[child][id-of-transaction] alone is enough
    to tell if the child became stale or not, use just that.
    
    Change-Id: I494bf02cca66f4fd41526195fafce86a202c6bd1
    BUG: 3455
    Reviewed-on: http://review.gluster.com/293
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b249ff7505392ae5cac1421a6a44310800d26feb
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Aug 22 11:59:11 2011 +0530

    cluster/afr: Paused fop should not continue with fop
    
    Change-Id: Idce22a6266c354e327d5d717715d2e62533eec58
    BUG: 3448
    Reviewed-on: http://review.gluster.com/292
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b6e3e9c480be4226925b51c5e9ee0c368aa94a6d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sun Aug 21 18:53:04 2011 +0530

    features/marker: changes in marker to avoid race conditions and corruptions
    
    Change-Id: I38ddfab200d59dd4c8e9f9dd964a98f3d7aa7ab7
    BUG: 3389
    Reviewed-on: http://review.gluster.com/289
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 08e8c966869b091fb4df8bfc8cadc37cb40719a5
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Aug 21 18:21:21 2011 +0530

    protocol/client: Changes to be benign to replace-brick
    
    Change-Id: Ic227781760a5f6dbf8aad69a19f90e45d4aaec13
    BUG: 3415
    Reviewed-on: http://review.gluster.com/288
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit af32ab6bc031347289201f33f496b6b713f7a3f6
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Aug 21 17:46:57 2011 +0530

    debug/io-stats: Handle loglevel in init
    
    Change-Id: I5aa6ee7509a8f730ca64e2f7bada56d502785a6c
    BUG: 3415
    Reviewed-on: http://review.gluster.com/287
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5ace31ac2160b216a396c0d8c992fa19dbad6f47
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Thu Aug 18 18:20:24 2011 +0530

    glusterd: replace-brick status was not 'shared' with peer.
    
    Change-Id: Ia2d89fd919b077232a37debc2aebe1bc72150856
    BUG: 3432
    Reviewed-on: http://review.gluster.com/285
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 45acdcbbdc2de50c59a8c3e21884a02902e6571f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Aug 21 16:58:15 2011 +0530

    cluster/afr: fop should not continue if it is paused, until resumes
    
    Change-Id: Ie026ebed98cf5ff75ae1a13437d29f67d0e0254a
    BUG: 3448
    Reviewed-on: http://review.gluster.com/286
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit aa07e855859d6a175fccb309ec3158e6ca894b0c
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Aug 21 16:34:19 2011 +0530

    debug/io-stats: Handle log-level properly.
    
    Change-Id: I8e5b8841705b161068bdb2ccd2ac119d6b250c88
    BUG: 3415
    Reviewed-on: http://review.gluster.com/284
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 22b5de922b7d4ce57db48b3ad518e98a9c91f4ee
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sun Aug 21 15:56:33 2011 +0530

    cluster/afr: set frame local
    
    Change-Id: I861b3c4494735b0ba6e038cdc39c50b9866747a8
    BUG: 3448
    Reviewed-on: http://review.gluster.com/283
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 350ae611cad29a0ad95d3e209a858d693579c1b2
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Aug 20 19:26:05 2011 +0530

    rpc/xdr: Fix for Solaris build failure
    
    Change-Id: I4704dfad655a79afb87ab275ba09413f785a97a4
    BUG: 3446
    Reviewed-on: http://review.gluster.com/280
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>

commit 1af420c700fbc49b65cf7faceb3270e81cd991ce
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Aug 20 15:48:27 2011 +0530

    cluster/afr: Perform self-heal without locking the whole file
    
    Change-Id: I206571c77f2d7b3c9f9d7bb82a936366fd99ce5c
    BUG: 3182
    Reviewed-on: http://review.gluster.com/141
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 2ebacdfdd3c39bf2d3139cb7d811356758a2350a
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Aug 20 18:26:08 2011 +0530

    mgmt/glusterd: Correct generation of nfs options in volfile
    
    Change-Id: If3db4f81215271072030d7119081de5d8b1b3d78
    BUG: 3414
    Reviewed-on: http://review.gluster.com/279
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit fdb7636bd719e560d9d8c0895a3b80bf3973b9d0
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 20 16:11:02 2011 +0530

    while validating options, make sure memory accounting is init()ed.
    
    Change-Id: Ifad5827c6b022de7d84e081ce77effda0c245a13
    BUG: 3415
    Reviewed-on: http://review.gluster.com/277
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 80694bb5ff2f61cfd6e2bb7908add6c853490407
Author: krishna <krishna@gluster.com>
Date:   Sat Aug 20 14:32:35 2011 +0530

    if nfs.port is not configured init the transport.socket.listen-port to GF_NFS3_PORT
    
    Change-Id: I6c0db600ba2010b0a0272f58b16c4955b4b570f2
    BUG: 3308
    Reviewed-on: http://review.gluster.com/273
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 64b12d90f39dd474a1a403594cf3f4598f21cd25
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Aug 20 15:52:27 2011 +0530

    xlators/nfs: Fix a typo in option description
    
    Change-Id: I626893fd16094742869d4abfa488b66924c2796e
    BUG: 3445
    Reviewed-on: http://review.gluster.com/276
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 7fe3d3fe2b0bec8085b15fb4d9db8fdead826d57
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Aug 20 15:18:09 2011 +0530

    libglusterfs: Fix a crash in gluster volume set help
    
    Change-Id: I585e8e685f5c23b6fa632ef708adf2e349ba6704
    BUG: 3415
    Reviewed-on: http://review.gluster.com/274
    Reviewed-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 7c6cf654700fb05502591e84b2000bb5230283e2
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Aug 19 13:51:14 2011 +0200

    cli: remove bogus assertion
    
    Since 86c818a9 (cli: taking my revenge ...) we cannot assert
    an exact match for the op/subop keywords in the followup parser
    functions. That is,
    
     # gluster vol stat foo
    
    is a valid invocation.
    
    Change-Id: I3f7f410f64f440744141f458886e4bba8ceeca17
    BUG: 3439
    Reviewed-on: http://review.gluster.com/268
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d9c6513289ca33204cdc110112ff8e45cbc8970a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Aug 19 15:56:49 2011 +0530

    cluster/afr: Update fresh_children in lookup if no other ops in progress
    
    If write/truncate fails we should remove the child that failed the fop
    from the fresh children. The previous code assumes that the children
    that succeeded the fop are fresh children, which is wrong. Fixed that
    in this patch.
    
    Change-Id: I1e6e21e20faea00516a0fdd2e95f2d7e9cf9076d
    BUG: 3411
    Reviewed-on: http://review.gluster.com/263
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 5e89fda5180e66b1757bc620dfdb5701ce4d43f1
Author: Anand Avati <avati@gluster.com>
Date:   Fri Aug 19 22:49:41 2011 +0530

    options handling: remove missing options check in reconfigure
    
    last minute change broke things. undo'ing damage.
    
    Change-Id: I330cf819b03e09f80d609d580d8b4c3497a98bbf
    BUG: 3415
    Reviewed-on: http://review.gluster.com/271
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c4dd6f5771e9a530c90cb6e23d6f43a7224fb654
Author: Anand Avati <avati@gluster.com>
Date:   Fri Aug 19 15:19:44 2011 +0530

    smoke-test.sh: script used by gerrit as part of pre-commit test
    
    Change-Id: Idc3be3e22cca5fc623b27c2f500f59785cbd332b
    BUG: 3234
    Reviewed-on: http://review.gluster.com/262
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit dd2c197c1d5d5942a65c860997ec1d5793ef249f
Author: Anand Avati <avati@gluster.com>
Date:   Fri Aug 19 14:56:13 2011 +0530

    option validation: further fixes
    
    fixes in option handling changes
    
    Change-Id: I0a44cdb088e3f08cd43d583a580736d0903fa88c
    BUG: 3415
    Reviewed-on: http://review.gluster.com/261
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 0143a2ef653d0f7a337c8220f127655dadbca942
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Aug 18 23:19:22 2011 +0530

    mgmt/glusterd, cli: Introduce gluster volume status <volname>
    
    Change-Id: Iea835b9e448e736016da2e44e3c9bfff93f2fa78
    BUG: 3439
    Reviewed-on: http://review.gluster.com/259
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit d2849bd349081b332540713cfeaa561f57356b2a
Author: Anand Avati <avati@gluster.com>
Date:   Thu Aug 11 16:08:36 2011 +0530

    xlator options: revamp xlator option validation/reconfigure code
    
    - move option handling to options.c (new file)
    - remove duplication of option validation code
    - remove duplication of gf_log / sprintf
    - get rid of xlator_t->validate_options
    - get rid of option validation in rpc-transport
    - get rid of validate_options() in every xlator
    - use xlator_volume_option_get to clean up many functions
    - introduce primitives to init/reconfigure option types
    
    Change-Id: I51798af72c8dc0a2b9e017424036eb3667dfc7ff
    BUG: 3415
    Reviewed-on: http://review.gluster.com/235
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 6073fc29bf79fad0b0a3ae423d637ded39a00a3a
Author: krishna <krishna@gluster.com>
Date:   Wed Aug 17 12:22:49 2011 +0530

    do rpcsvc_init() after we fill nfs_state structure and add to nfsx->options keys for allowing insecure client ports.
    
    Change-Id: Iae755d1460f2c7296fc7980b5257afcf778e7767
    BUG: 3296
    Reviewed-on: http://review.gluster.com/247
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit d41eda762e4e98d95d3c80dd849a11e6aec11b56
Author: Anand Avati <avati@gluster.com>
Date:   Thu Aug 18 11:27:06 2011 +0530

    rpc-clnt: fix merge error of http://review.gluster.com/248
    
    cherrypicked patch did not have the logic to reset port number to
    reconnect to glusterd.
    
    Change-Id: I78c903d5a28626f83b5024bd323e77b5f159e374
    BUG: 3409
    Reviewed-on: http://review.gluster.com/254
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit c0180cc22f5f52f5776c74a6d1ae90100dbb5087
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Aug 10 17:57:04 2011 +0530

    glusterd: fix for volume stop causing inconsistent volume status
    
    This fixes problem caused by race between glusterd and glusterfsd
    occuring when they try to unlink pidfile during volume stop, which led
    to the volume being stopped, but the status of the volume remained in
    started state.
    
    Change-Id: Ia99bb1a1fc6c78db138211538dfd10c577e82917
    BUG: 3147
    Reviewed-on: http://review.gluster.com/206
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit cef6d3596fcbda71c19e66c5a6de502847aece9e
Author: Anand Avati <avati@gluster.com>
Date:   Fri Aug 12 00:46:50 2011 +0530

    rpc-clnt: perform XDR encoding in unlocked region
    
    Change-Id: Ia11c3ced4bec5959a5f0d8fcd4c6070b2ead220a
    BUG: 3409
    Reviewed-on: http://review.gluster.com/248
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 2902b6f325d4bbb6cd947cee0301bf75d9634196
Author: Venky Shankar <venky@gluster.com>
Date:   Wed Aug 17 15:19:05 2011 +0530

    allocate extra bytes (for \0) when calling realloc
    
    We use strcat to concat pathinfo strings. strcat appends a \0 at
    the end. Therefore allocate extra bytes for the same to avoid
    asserts being hit during gf_free call
    
    Change-Id: I582f5858e7375a5bacfc5c702c612ee09c3bb355
    BUG: 3413
    Reviewed-on: http://review.gluster.com/249
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 7d15ee5ee37384e40600306e3efbc037ff6f9e9b
Author: Anand Avati <avati@gluster.com>
Date:   Wed Aug 17 04:18:48 2011 -0700

    Revert "Make sure glusterd and glusterfsd use the same address family"
    
    This reverts commit 1dade36a6dfc6cae5559d5139f6b733e1b6fded1
    
    This commit breaks glusterd. The insertion of --xlator-option=<transport family> in between --brick-port and <port> fails command line validation during glusterfsd start.
    
    Change-Id: I40186ca89d1d16cf798404747771353b1f1a3e1d
    Reviewed-on: http://review.gluster.com/251
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 61a9ed994d817ffe9aab4b5adb31ffcb6ca6820c
Author: Anand Avati <avati@gluster.com>
Date:   Wed Aug 17 04:16:59 2011 -0700

    Revert "Remove white spaces"
    
    This reverts commit 6ab425e4f3d34b1467f694ada9a36eacfac9bf3c
    
    Dependency revert for http://review.gluster.com/229
    
    Change-Id: I7c4fcc45a6c25aedf4f06cbdeedc1fecbe424f45
    Reviewed-on: http://review.gluster.com/250
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit b1b952d62d452641cd17ab5bf1a386cc4a05b17b
Author: krishna <krishna@gluster.com>
Date:   Wed Aug 17 12:48:46 2011 +0530

    do not init nfs->override_portnum to GF_NFS3_PORT
    
    Change-Id: I7dc26b64a177ce5d30352cf7c531f38517c0368a
    BUG: 3308
    Reviewed-on: http://review.gluster.com/155
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shehjar Tikoo <shehjart@gluster.com>

commit 12895212d64e2f209190f389a92be7f5e67ec84e
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Wed Aug 17 06:19:05 2011 +0200

    Remove white spaces
    
    Change-Id: I646c0c8e70268de6a20bb23dc3834ac6f5d2bbf2
    BUG: 3422
    Reviewed-on: http://review.gluster.com/245
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 02f45250af3fcb58a309e4089b64e2b147b1b265
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 16:20:14 2011 +0200

    Make sure glusterd and glusterfsd use the same address family
    
    NB: This was heavily tested on 3.2.2, but code has changed a lot
    in the area. This patch itself is untested.
    
    Change-Id: Ie472f04b0804276c2d8a9efc5c96106c33029498
    BUG: 3422
    Reviewed-on: http://review.gluster.com/229
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 023969d911b90420bd1733bae57d04e24dee5eda
Author: Venky Shankar <venky@gluster.com>
Date:   Tue Aug 16 11:32:35 2011 +0530

    adjust allocated length to memory overrun fix
    
    size of the allocated length is incorrectly calculated which could
    cause memory overrun while filling the buffer
    
    Change-Id: I4fbdbd1fff937ca15bae9f634ef5757dda52caa8
    BUG: 3413
    Reviewed-on: http://review.gluster.com/236
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit a0071bdf2a0f73fd17ac769298ed65b245f0607c
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Aug 13 21:52:35 2011 +0530

    cluster/afr: read_child should be >= 0
    
    Change-Id: I447fb6a93cdd77de322cd5ded30673411c4cf79e
    BUG: 3251
    Reviewed-on: http://review.gluster.com/233
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit e618c1b59debbb9184874a06cbc64b8ac846a0d3
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 09:12:27 2011 +0200

    - Use linkat(2) instead of link(2) so that linking to symlink work on
    non Linux systems
    - Also use mkfifo to create FIFO on NetBSD: it does not wotk with mknod
    
    Change-Id: I19ffd22b4d79009ef5f9d4a50fc6dd556c3c3ff4
    BUG: 2923
    Reviewed-on: http://review.gluster.com/226
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 53da3edbe5b43a994cc916b6571563491a8a414b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 12:00:49 2011 +0200

    POSIXly correct: \n replacement is GNU sed specific
    
    Change-Id: I5e4ca551b60477d454964e568209ad06f21cc64e
    Reviewed-on: http://review.gluster.com/227
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit abe7843ca6faa03a9b6e1ece3fb85d4c5b02580a
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 09:17:44 2011 +0200

    Allow georeplication for NetBSD
    
    Change-Id: Id8d62f4f83255c67a5aa615aed23ba44c182290e
    BUG: 2923
    Reviewed-on: http://review.gluster.com/220
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit c5d7fa2bf4c766200971cfbb877d4a25b3cb32b0
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 06:46:15 2011 +0200

    Build fix for NetBSD
    
    Change-Id: Icb0163d61bfbd3bad520c06a655f80ec05fc3fb2
    BUG: 2923
    Reviewed-on: http://review.gluster.com/214
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 22105b3c741a26f525e0b31bb3d880c1eaa05c30
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 06:48:07 2011 +0200

    Build fix
    
    Change-Id: I10dca7aee73df31f8b279591852d6ac19eab8ccc
    BUG: 2923
    Reviewed-on: http://review.gluster.com/228
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 139e03445e590911dbf00f30b0cfc005ee8a106b
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 06:34:54 2011 +0200

    For systems where O_DIRECTORY does not exist, we defined it as 0,
    therefore ((flags & O_DIRECTORY) == O_DIRECTORY) is always true even
    if the flag is not set.
    
    Change-Id: Ie7837d521ea20b36ed70cf93c1763c226ff0e9f0
    BUG: 2923
    Reviewed-on: http://review.gluster.com/213
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 8a24e3179fc822e3ec59eaac8f6a2050b8dd9b40
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 09:23:15 2011 +0200

    Do not distribute UFS1 extended attribute backing store
    
    Change-Id: Ie05751aa8d96a2f7996843a914e1a66df2777eba
    BUG: 2923
    Reviewed-on: http://review.gluster.com/222
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 5b6be1cdb500b375d673d9b2f2dfe7cfbda5d2b8
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 10:26:47 2011 +0200

    One more missing change :-/
    
    Change-Id: I6eeaee73e7c9124a1959acb2fe47d5cad3a3baac
    Reviewed-on: http://review.gluster.com/225
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 9fa3aeadfe162483e01f285c7fd4d5f0fb712c18
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 09:51:28 2011 +0200

    Use bourne shell, fix error in previous commit
    
    Change-Id: Id2a304d5090eb2564c5d56ea260fa53b9b17d0d5
    Reviewed-on: http://review.gluster.com/223
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit cc756d0075ff9829700cfc74d1bf3e2080523f65
Author: Emmanuel Dreyfus <manu@netbsd.org>
Date:   Fri Aug 12 06:43:07 2011 +0200

    sed -i is available from GNU sed, but is  not portable. Output to a new
    file and move it to the original one on success instead.
    
    Change-Id: Ib23dd9becd035054e6490dcb4d64b3f9eff89bf4
    Reviewed-on: http://review.gluster.com/212
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit b4d166be42acd65d083a6e839f96989746b0ef46
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 11 14:59:19 2011 +0530

    RO: fix read-only xlator support broken due to worm xlator fix
    
    Change-Id: I7234909eecdc6af1b8482465f19d0490fcba94ad
    BUG: 3166
    Reviewed-on: http://review.gluster.com/210
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 86999525240983dcbd3fe66eb40a0947730c695c
Author: shishir <shishirng@gluster.com>
Date:   Tue Jul 19 16:02:12 2011 +0530

    WORM: Write Once Read Many times xlator support
    
    This xlator will allow files to be opened for write in append mode
    only. Mount with --worm(glusterfs) or -o worm (mount) option to
    enable worm xlator
    
    Change-Id: I1be02fcf2aee2182ea2c66b514357918136fabeb
    BUG: 3166
    Reviewed-on: http://review.gluster.com/23
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 5ce1b5c357d490f68ae89bfd3ce31326a81a1183
Author: Anand Avati <avati@gluster.com>
Date:   Wed Aug 10 23:11:36 2011 +0530

    posix-acl: disable permission checks for fd based ops
    
    If write calls are coming in through an fd with O_RDWR or O_WRONLY
    flag then a permission check is unnecessary. However writes from
    NFS ideally need a "stateless" check in each call and this results
    in a permission failure due to the read-only mode (disregarding the
    FD's writeability).
    
    For now it is acceptable to disable write checks as almost always
    the NFS client would already be doing such basic access control.
    Also because the previous access-control translator (prior to
    posix ACL introduction) too was permitting writes and reads
    unconditionally.
    
    In fact the Linux KNFS server too assumes the NFS client would have
    done the permission check.
    
    Change-Id: I33e5de8911a87881f9341b8b92574780c2dfbeba
    BUG: 3388
    Reviewed-on: http://review.gluster.com/208
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit b58dc65f2ac305056a25a2177cee9a03cd1bdca2
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Aug 9 12:30:19 2011 +0530

    Change Copyright current year
    
    Change-Id: I2d10f2be44f518f496427f257988f1858e888084
    BUG: 3348
    Reviewed-on: http://review.gluster.com/200
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 2153b8400bc05f1a9e10c7b650dd96a4617121f1
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 9 11:37:38 2011 +0530

    fix build issues in Mac OS X (10.6)
    
    Change-Id: Ifc6f156441f6545d579c3fac2fffca36fb395951
    BUG: 3354
    Reviewed-on: http://review.gluster.com/196
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit eddb2069f3b0e122cbd034328d87e08e737f4c4e
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Aug 8 16:54:12 2011 +0530

    fuse-resolve: prevent linking of inodes of different inode-table
    
    This can happen in deep_resolve_cbk, which happens after a graph
    switch. Root cause was because the graph change happened while
    a FOP was in transit and by the time the call came back, the active
    translator of fuse is now changed.
    
    Fix is to make sure the resolve operation happens on a given
    inode table, instead of taking the latest graph of fuse for
    each operation
    
    Change-Id: Idd6e2d5c2d5fc5d571f7a1fbc174e210babf8a2b
    BUG: 3355
    Reviewed-on: http://review.gluster.com/195
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 1b5a860f159916f0b289069ef3223e6fd754d36b
Author: krishna <krishna@gluster.com>
Date:   Thu Aug 4 15:51:28 2011 +0530

    pass xlator pointer to rpcsvc_init() so that it can init svc->mydata to xlator
    
    Change-Id: Icfd95cc67400c16a951d6a9f922fbdc07f40c5b6
    BUG: 3314
    Reviewed-on: http://review.gluster.com/180
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 09ed778309cd4d4cdbc19ad7cbdcea3da7408a66
Author: krishna <krishna@gluster.com>
Date:   Fri Aug 5 15:25:16 2011 +0530

    NFS server: allow clients to connect from insecure (>1024) ports and support for both rpc-auth-allow-insecure and rpc-auth.ports.insecure
    
    Change-Id: I4e3fbfe37d6d3e8443d5b7b79faf6e364fdb87be
    BUG: 3296
    Reviewed-on: http://review.gluster.com/178
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit d62c0abf597a2e77e3fb0cfa0d4598aedea64d33
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 8 10:47:53 2011 +0530

    Changes to EXCEPTIONS and included EXCEPTIONS in packaging
    
    Change-Id: I6c5c1536016489bf6b981356942901f69862393a
    Reviewed-on: http://review.gluster.com/188
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 0cf100b58c34b40eb7f35fa6913996539e0e3aa9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Aug 6 14:00:03 2011 +0530

    LICENSE: s/GNU Affero General Public/GNU General Public/
    
    Change-Id: I3914467611e573cccee0d22df93920cf1b2eb79f
    BUG: 3348
    Reviewed-on: http://review.gluster.com/182
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 4e116e2af014754e88170986820312e755617476
Author: Anand Avati <avati@gluster.com>
Date:   Sat Aug 6 18:00:49 2011 +0530

    cluster/dht: clear local->cached_subvol when switching to do_fresh_lookup
    
    The presence of local->cached_subvol makes dht_lookup_everywhere_done behave
    as though it was a lookup on a file where linkfile needs to be recreated. In
    a fresh lookup, local->cached_subvol should be NULL.
    
    Change-Id: Ie6bd6ad536def03d970526d51e20c6daeb00922b
    BUG: 3317
    Reviewed-on: http://review.gluster.com/187
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit bed8d32a52b2a58b905e91828c3155cba2544058
Author: Sachidananda Urs <sac@gluster.com>
Date:   Thu Aug 4 16:59:52 2011 +0530

    Replace mktemp(3) with mkstemp(3).
    
    Man page states:
    Some implementations follow 4.3BSD and replace XXXXXX by the current process ID
    and a single letter, so that at most 26 different names can be returned.  Since
    on the one hand the names are easy to guess, and on the other hand there is a
    race between testing whether the name exists and opening the file, every use of
    mktemp() is a security risk. The race is avoided by mkstemp(3).
    
    Change-Id: Ida95403b55024ecd07ef811a0835e01a9a7f092b
    BUG: 3331
    Reviewed-on: http://review.gluster.com/163
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit b510ec361482a57c32b81aebb9d61a50676727f9
Author: Junaid <junaid@gluster.com>
Date:   Thu Aug 4 15:47:15 2011 +0530

    features/marker-quota: Performance improvement.
    
    With this patch new transactions will not be triggered if an updation is
    already in progress on that inode.
    
    Change-Id: I587385498c4b2af8bd9624ca41c60742c5ef2485
    BUG: 2988
    Reviewed-on: http://review.gluster.com/76
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>

commit 22c6a64f851e844091b4060f20ee3c24b28c80f7
Author: Anand Avati <avati@gluster.com>
Date:   Fri Aug 5 14:52:01 2011 +0530

    save even more trees
    
    make the build even more quiet.
    make anush even more happy by saving even more trees.
    
    Change-Id: I301aba34e4470805114989650a13f9fe35f42d35
    BUG: 3255
    Reviewed-on: http://review.gluster.com/176
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit b22ffeec89bbefd2d7b9fa62a25ede5545f1cbe6
Author: Anand Avati <avati@gluster.com>
Date:   Fri Aug 5 14:04:43 2011 +0530

    save more trees
    
    make the build more silent
    
    Change-Id: Ied4c87c40af4b1f1034af4a13c1153d82883751b
    BUG: 3255
    Reviewed-on: http://review.gluster.com/171
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 4b640273b05dec6923c13d14d4d40e136e2df99f
Author: Louis Zuckerman <me@louiszuckerman.com>
Date:   Fri Jul 29 18:03:41 2011 -0400

    Provides an upstart job for glusterd on Ubuntu, solving Bug 3282
    
    Mounting from localhost in fstab fails at boot on ubuntu when glusterd is started by debian initscript.
    
    A new directory, extras/Ubuntu, contains the new upstart job (glusterd.conf) and a brief README.Ubuntu file.
    This makes the upstart job available to package maintainers like the SysV initscripts are in extras/init.d.
    
    This has been tested on Ubuntu 10.10 Maverick.
    
    Change-Id: I6ccd06054e920cd6dc45dba4eb8ab89aa30f8b47
    BUG: 3282
    Reviewed-on: http://review.gluster.com/126
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 3780881e1bc4387f55e065508fb8fad371fc2b51
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Aug 1 16:20:12 2011 +0530

    storage/posix: handle dictionary being NULL in a function
    
    also print a warning message if dictionary is NULL, while sending a
    mkdir request in distribute self-heal.
    
    Change-Id: Ib9cac6ed1635203802f089986f8acb1ce416265d
    BUG: 3215
    Reviewed-on: http://review.gluster.com/136
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 3778cb5f668149d893ff6ae09d73878afc957133
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jul 14 01:41:48 2011 +0000

    features/marker: log failures due to file not being present during quota updation transaction in DEBUG.
    
    Change-Id: I6733586ba56ed4fdc2abbef63c38b8c491f89819
    BUG: 3143
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/32
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Mohammed Junaid <junaid@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 03aa9ecde933269282ca1043a16378e0d1e5cb49
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Aug 1 17:11:59 2011 +0530

    glusterd rebalance: handle a race condition while starting a rebalance
    
    due to the race, there was a possibility of having two (or more) threads doing
    glusterd_defrag_start(), which would cause different thread to access same
    pointer, and at some point making it NULL, causing other threads to crash with
    SEGV.
    
    Change-Id: Id05b99dd6f33329027b8a07f1c8da5a65fd6dae9
    BUG: 3295
    Reviewed-on: http://review.gluster.com/138
    Reviewed-by: Anand Avati <avati@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 5bd8f537da3fe570e481713a1c2c4ee6e88ac38e
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Aug 2 15:30:06 2011 +0530

    DHT rename: Recreate linkfile after unlink
    
    This is done, so that there is no gfid mismatch. Unlink the older
    linkfile if it exists, and recreate it with the correct gfid.
    
    Also removed unused rename related code.
    
    Change-Id: Ice0cdff51db786dafb1a019f7642c7d000e8c5f3
    BUG: 2522
    Reviewed-on: http://review.gluster.com/142
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit a08927b04e2d55edcb12be77128949798ed8f142
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Aug 3 14:09:17 2011 +0530

    mgmt/glusterd: Ignore case in friend find by hostname
    
    Change-Id: I8dabf07ebb30ec500d847c11d5c72c2d87d10239
    BUG: 3309
    Reviewed-on: http://review.gluster.com/145
    Reviewed-by: Vijay Bellur <vijay@gluster.com>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>

commit 8da4623f2274faa9e9d88f7d30babb9ea80fb141
Author: Sachidananda Urs <sac@gluster.com>
Date:   Fri Jul 29 16:26:03 2011 +0530

    Remove redundant function `cli_path_strip_trailing_slashes'.
    
    Use cli_canonicalize_path instead, to remove trailing/duplicate slashes.
    
    Change-Id: Ie76267a4fa9ee9986cb36039afad4dfff830d5f8
    BUG: 3183
    Reviewed-on: http://review.gluster.com/124
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit df0a72d9c118c2a1146f2787eee6d5f0a58853f0
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Jul 29 16:36:27 2011 +0530

    Variable IOBUF: Use variable iobuf for cli/glusterd/glusterfsd(mgmt)
    
    By using variable iobufs, xfer data size is no more limited to
    128K (default). This helps in scaling.
    
    Change-Id: Iab453db9223d887306d150cd6fe0b1eae9c422cc
    BUG: 2472
    Reviewed-on: http://review.gluster.com/13
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 76acac485b9f06f36d145b4c31fa6f4da3c70f52
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Jul 29 16:30:36 2011 +0530

    IOBUF: Bring in variable iobuf support
    
    Rebasing Raghavendra's patch to master
    
    Change-Id: Ie7a0c9a7b8e73cfe48c4573a5153460d5126208e
    BUG: 2472
    Reviewed-on: http://review.gluster.com/12
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 9867f3954138e795123b4b308e256e641c55f3ec
Author: Anand Avati <avati@gluster.com>
Date:   Mon Aug 1 11:24:35 2011 +0530

    glusterfsd: initialize sigset_t in sigwaiter
    
    Thanks to kkeithle@redhat.com for pointing out.
    
    Change-Id: I8167ffffddbdbc3dc09f7474bd834dbf4a49db9b
    BUG: 3280
    Reviewed-on: http://review.gluster.com/129
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit a13fbaca0512cae3853a2372d0d8237eb24dd225
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Jul 13 00:52:14 2011 +0200

    gsyncd: do some basic sanitization on logs
    
    - exceptions raised by us will be logged as single-line error messages
      (full stack strace is shown only at DEBUG loglevel)
    - common/well understood exceptions are mapped to "user-parsable" error logs
    
    Change-Id: I75f1fb848483372364b2093878d9cfed576c9739
    BUG: 2778
    Reviewed-on: http://review.gluster.com/125
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 6c7a89321af50925fb53da378d996881a1907f31
Author: krishna <krishna@gluster.com>
Date:   Wed Jul 27 18:16:59 2011 +0530

    RPC unify code change
    
    Change-Id: Ibe18a2a63fd023ac57652c4dfc8ac8a69d983b83
    BUG: 3112
    Signed-off-by: krishna <krishna@gluster.com>
    Reviewed-on: http://review.gluster.com/116
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 8b9cb1701f6365f7b4f5ed166f37020781f59467
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 12 03:38:01 2011 +0200

    geo-rep: minor fixes
    
    Change-Id: I5c5211858bdb2bd28324818362d95edd97f94207
    BUG: 2778
    Reviewed-on: http://review.gluster.com/81
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>

commit 8efbc829490420ebe75b42a1e0f268b950aaba91
Author: Rajesh <rajesh@gluster.com>
Date:   Fri Jul 29 13:18:20 2011 +0530

    cli: Improve message in gluster top
    
    Removed "volume top successful" message.
    If top fails,"volume top unsuccessful" is displayed.
    If errstr is set, it is displayed.
    "No entries in list" messages deleted.
    
    Change-Id: I8ed35ea7db365b7af6b10833672fcab0e4e8751d
    BUG: 2722
    Reviewed-on: http://review.gluster.com/121
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 9759d7e6d8f11ef6111fd6d313ced098efa2e38b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jul 19 15:09:13 2011 +0530

    performance/io-cache: hold lock on ioc_inode whereever a page is being accessed/modified
    
    Change-Id: Ifc435c2e289b2a8ceeed2a091e555953af179936
    BUG: 2939
    Reviewed-on: http://review.gluster.com/21
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit dbc567ec9f97a540e6cab8006ba285ab62fc372c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Jul 15 01:54:31 2011 +0000

    performance/quick-read: Handle unwinding of frame corresponding to read fop properly, while validating cache.
    
      - there was a possibility of double unwind in case of errors.
      - use a new frame to do open in fd-based fops.
        In case of errors, qr_resume_pending_ops will be called to resume all the
        fops waiting on open. Hence if we use frame corresponding to fop (without
        creating a new one), there is a possibility of frame being freed by the
        time open would've returned to quick-read.
    
    Change-Id: Ie4cc19907f9d6362860bdb984779c8f4cf822332
    BUG: 3168
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-on: http://review.gluster.com/34
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit cfec0be455f388f4106e3df55b00c691631c40ea
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Jul 26 16:35:10 2011 +0530

    IO-threads: Support for loading io-threads xlator on client side
    
    New set option performance.client-io-threads added to enable/disable it.
    Default behavior is io-threads is off on client side
    Loaded only on fuse volume below io-stats.
    
    Change-Id: I13aea9a564d5270901c3c356fa6bede836c6a66d
    BUG: 3122
    Reviewed-on: http://review.gluster.com/105
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit bc16882a04baaac214f1b41598827038e8872363
Author: Junaid <junaid@gluster.com>
Date:   Mon Jul 25 14:59:25 2011 +0530

    features/marker-quota: Perform removexattr with frame uid and gid set to root.
    
    Change-Id: Iabd8ff835c76d828e4af50ce4941d2ff86797eee
    BUG: 3194
    Reviewed-on: http://review.gluster.com/98
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>

commit bed25e47ee047d2f3af1120ee66f17147171bd6e
Author: Junaid <junaid@gluster.com>
Date:   Tue Jul 19 11:26:43 2011 +0530

    mgmt/glusterd: Read the contents of vol-info file into a dynamically alloced
    string.
    
    Change-Id: I06173a4cf22e12bc543f8ff2d151078333b500e1
    BUG: 3154
    Reviewed-on: http://review.gluster.com/8
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pavan T C <tcp@gluster.com>

commit f3c0281d9b4654888a5525b443f1e6090d874725
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 22 15:23:32 2011 +0530

    glusterfsd-mgmt: initialize ctx->mgmt before calling rpc_clnt_start()
    
    this is required because if 'CONNECT' event comes before the clnt_start()
    function ends, we may loose the event if it is not initialized.
    
    Thanks to Jeff Darcy <jdarcy@redhat.com> for pointing it out
    
    Change-Id: Iebbd651b7563265800f41922367ca133fbbf4fc3
    BUG: 3207
    Reviewed-on: http://review.gluster.com/77
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit ff5fddcf54805464c1033ee4665835784e260831
Author: shishir <shishirng@gluster.com>
Date:   Wed Jul 27 15:03:40 2011 +0530

    Stripe_readdirp: Fix race in wind/unwind which led to crash
    
    Scenario - The race window exists when before we wind to a stat call
    in readdirp_cbk, whereas stats have returned to cbk. We would free up
    local, which leads to a crash.
    
    Fix - We assume all entries to be regular files, and set the wind_count
    as a multiple of entries * subvol (stat calls). When we encounter a non
    regular file, we decrement the windcount accordingly (subvol times). If
    the last entry happens to be a non-regular file, and all stat calls have
    wound back, we unwind from here itself.
    
    Change-Id: Ia8e225ef557cbe1fedb9b72de9bd9fa61f371a24
    BUG: 3257
    Reviewed-on: http://review.gluster.com/115
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 2a6de14e22445fc3017c9aa25b9c56bc4259d373
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 12 22:18:58 2011 +0200

    gsyncd: exit in slave when RePCe session came to an end
    
    Change-Id: I4317e60fce3280c45dbcc4a5f233a4344aba9500
    BUG: 2778
    Reviewed-on: http://review.gluster.com/83
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit cf4501899ca75a6641a31cf7116d439dfb6dd4de
Author: shishir <shishirng@gluster.com>
Date:   Tue Jul 26 12:56:54 2011 +0530

    NFS: Implement nfs_forget call
    
    Make sure the inode_ctx is deleted
    nfs_release is not needed, as __nfs3_fdcache_remove_entry cleans up
    the ctx
    
    Change-Id: I690efa1eb1d4cd39cee258bb29692cc58ab9c380
    BUG: 3250
    Reviewed-on: http://review.gluster.com/103
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shehjar Tikoo <shehjart@gluster.com>

commit fa979753d9fe27c6338a0d384d0f183ea716003d
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 12 21:59:24 2011 +0200

    gsyncd: log exit properly
    
    Change-Id: Iedd8c0ce9dec2d8dcb01e0e5b409cb53185b1716
    BUG: 2778
    Reviewed-on: http://review.gluster.com/82
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>

commit 06af690050b5b0ca4da34d4c89fda3d3deffe908
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Jul 11 14:57:18 2011 +0200

    geo-rep: compactify logging
    
    Change-Id: I19f6cf539289062b39e3c0f73fa88f4ff9488349
    BUG: 2778
    Reviewed-on: http://review.gluster.com/80
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Kaushik BV <kaushikbv@gluster.com>

commit 55219903e32e750cfdf58260e7c3a2c4f2bfe16e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Jul 25 15:31:21 2011 +0530

    libglusterfs: Bring in os_daemon_* routines to replace modified FreeBSD code
    
    Change-Id: I41f4635b1b75adb6d22e2e325b99941f8d7a0b42
    BUG: 3206
    Reviewed-on: http://review.gluster.com/100
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 98b32b5798c7d782cae4c16b608f600ab51fffce
Author: Junaid <junaid@gluster.com>
Date:   Thu Jul 21 23:51:45 2011 +0530

    features/marker-quota: Fix some random memory leaks.
    
    Change-Id: I1b01adf1d0ecf494f960d125f2bdcc9c10137115
    BUG: 3169
    Reviewed-on: http://review.gluster.com/75
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Tested-by: Raghavendra G <raghavendra@gluster.com>
    Reviewed-by: Raghavendra G <raghavendra@gluster.com>

commit 58e3c67007d52b5c2383badf32d5809edfc0c6cb
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 26 17:23:27 2011 +0300

    save the trees
    
    Change-Id: I394621c76a95ed596aedcd45030d80a79de30acf
    BUG: 3255
    Reviewed-on: http://review.gluster.com/108
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 58ccea44011065f57968114c9a8e89307ec05276
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 27 14:36:56 2011 +0530

    rpc: in client connection init(), return the proper error code
    
    without the proper error code, rpc won't know if transport is successfully
    loaded or not.
    
    Change-Id: Idc3ad56d2f47cf1e81ba39f90a7f7b47305d7d9a
    BUG: 3260
    Reviewed-on: http://review.gluster.com/112
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit baf66413aa1d7ea65d092f2301d2ec749b6a217e
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Jul 6 14:10:25 2011 +0530

    glusterd: handle replace-brick in paused state.
    
    This change ensures that glusterd retains 'state' information
    of an ongoing replace brick operation even if it went down midway.
    
    Change-Id: I697c2f27a96b3200c7865bd1d3a1de9692ce0da1
    BUG: 3252
    Reviewed-on: http://review.gluster.com/6
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit 48665f87f55d07eb790c882e5b10217416140319
Author: Gaurav <gaurav@gluster.com>
Date:   Tue Jul 26 11:34:10 2011 +0530

    Glusterd: Remove dependency on AI_ADDRCONFIG for AF_UNSPEC
    
    Change-Id: I0a22b2cc5a0ea1a57633fddabad54aca7b3d4e86
    BUG: 2456
    Reviewed-on: http://review.gluster.com/102
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Csaba Henk <csaba@gluster.com>
    Reviewed-by: Vijay Bellur <vijay@gluster.com>

commit b922437795a68b32cd6fb337dfd66a4ead13b4ee
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jul 14 16:17:57 2011 +0530

    cluster/distribute: while fixing layout, consider ENOSPC errors
    
    in case of layout 'creation', layout->err == ENOSPC should be ignored
    where as, while layout 'fixing' we should consider what was already
    present in the layout.
    
    Change-Id: Ifb613b41065813c9f1202e65e94b4b0282766d11
    BUG: 2258
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Reviewed-on: http://review.gluster.com/15
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit 73eca3be5c5ccc71bbad934338c1ef58ed37c483
Author: Rajesh <rajesh@gluster.com>
Date:   Tue Jul 19 15:57:30 2011 +0530

    rpc-transport/socket: avoid logging socket read fails
    
    An option, transport.socket.read-fail-log was added in glusterd.
    This can also be added to any translator which uses socket.c.
    A gf_boolean_t flag(read_fail_log) is added in socket_private_t.
    Using this, logging of socket read failures can be controlled.
    The options is set to 'off' in glusterd.vol by default.
    
    Change-Id: I85cf4afc1f534f5f51018449d5d84baef18fce23
    BUG: 3156
    Reviewed-on: http://review.gluster.com/22
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit d35e17152720a074c15f54f5c3b8a400e456b19e
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 22 03:45:34 2011 +0530

    cluster/dht: dht_rename() - handle GFID situations
    
    In the pre-GFID era, the linkfile of the destination file could be reused
    the linkfile for the renamed file when dst_cached == src_cached.
    This patch handles this situation and reverts the previous (wrong) fix.
    
    Change-Id: Iba57b5eb91cf8b1fb40e74f6399cdf99b8b00410
    BUG: 2464
    Reviewed-on: http://review.gluster.com/90
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Amar Tumballi <amar@gluster.com>

commit 65cc08d80d5db6a6854249cc04bece0a9554adfb
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 13 09:21:55 2011 +0000

    glusterd: Add bind-insecure xlator-option for glusterd
    
    This is required if the number of connections from the glusterd
    increases.
    
    Change-Id: Iff78773f593a8bfae13ec9eec52c5a67ea936ef2
    BUG: 3142
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Reviewed-on: http://review.gluster.com/11
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Pavan T C <tcp@gluster.com>

commit b06ba047f48e92323d8dc8af7ed485d35fbbccf2
Author: Vishwanath S Bhat <vishwanath@gluster.com>
Date:   Thu Jul 21 15:19:14 2011 +0530

    glusterd - Removed hardcoding of transport type in replace-brick.
    
    Replace-brick didn't support transport types other than tcp.
    Test case: replace-brick should work with tcp and rdma.
    
    Change-Id: If33f108b70247d81791d25a1a05247f49847b4d7
    BUG: 3092
    Reviewed-on: http://review.gluster.com/72
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kp@gluster.com>

commit 2c068a98e4b0bf54e7553ed7411fa8c7fe3173ba
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Jul 23 06:03:18 2011 +0200

    gerrit: add a dry-run mode to rfc script
    
    With DRY_RUN=1, rfc.sh will not perform the git push just display
    the push command. This can be useful if one wants to give a final
    review for the submitted change list (check for typos, misplaced bug
    id-s) or if one is offline.
    
    Change-Id: I90e2016ba78e2a0ecf37044b3db0277a25914f77
    BUG: 3234
    Reviewed-on: http://review.gluster.com/87
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 434da60ba4ce9a2b47ea47a7790ce48a342de00a
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Jul 23 05:50:53 2011 +0200

    gerrit: some fixes for the rfc script
    
    In rebase_changes():
    
    - Using "--all" for git fetch is bogus: the scope of this quantification is not
      over the tracked refs of the upsteam repo (which we do want, but that kind
      of universal quantification is already implied by the notion of "tracking"),
      but over the set of all the registered remotes, which is an annoying side effect.
    
    - $EDITOR is weaker than the git configuration settings. For the purpose of the
      script, we need to override any kind of setting, and that can be done
      via $GIT_EDITOR.
    
    Cf. git-fetch(1), git-commit(1).
    
    Change-Id: Ia91ee5c4d42dce9248f26f7697528e3c97355871
    BUG: 3234
    Reviewed-on: http://review.gluster.com/86
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 2d29b67a63779ac7b115d214bb037c12b122cf2f
Author: Kaushal M <kaushal@gluster.com>
Date:   Tue Jul 19 09:05:54 2011 +0530

    glusterfsd: check for process mode before performing mount
    
    create_fuse_mount() now checks if it is a client process before performing
    mount. If not a client process, it returns an error.
    
    Added changes suggested
    
    Change-Id: If8548ad60d345bb8cd09686ceed0d83522799761
    BUG: 2469
    Reviewed-on: http://review.gluster.com/5
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 37b4b7ccad5a479ed2ce96598e902a12fd457bd5
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jul 20 12:21:12 2011 +0530

    debug/io-stats: allow log-level to be set to INFO
    
    Change-Id: Ieba6591b0641dcb7dad724c1d8199dc5e91b6bfd
    BUG: 3198
    Reviewed-on: http://review.gluster.com/43
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit c6053cac7794dfd9bf693e91cd76c2a45d7859eb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jul 20 12:35:14 2011 +0530

    debug/io-stats: print the time at which maximum fds were open in gluster top
    
    Change-Id: I257bc29945d5acf8fb316f396fb011a2ab652d7a
    BUG: 3076
    Reviewed-on: http://review.gluster.com/54
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Shishir Gowda <shishirng@gluster.com>

commit a7e38564ec859afc15274a0d9a16d6e04ed3f6e2
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 20 14:53:04 2011 +0530

    Top/Profile: Report error when all bricks are down on volume
    
    Profile - If all bricks are down, report errror.
    Top - If all bricks or the specified brick is down, report error.
    
    Change-Id: I39d4acd631b481233ab2e9f66c8f4160caef5762
    BUG: 2600
    Reviewed-on: http://review.gluster.com/63
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit 46afd33ebe184604443a695ebf8eaea8c2098443
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 19 21:08:14 2011 +0530

    glusterd rebalance: use lstat() instead of stat()
    
    so the symlinks pointing to directories are not considered
    as directories themself and the control flows outside
    gluster's scope
    
    Change-Id: Iae910ce6c68886d34ae6e5efe46062481b40cd25
    BUG: 3191
    Reviewed-on: http://review.gluster.com/30
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Anand Avati <avati@gluster.com>

commit e74bf1ae7d974ae3681818a0a6240adee5983323
Author: Kaushal M <kaushal@gluster.com>
Date:   Tue Jul 19 14:36:13 2011 +0530

    cli: modifications to "profile info" output
    
    Units are now shown for the latencies and duration
    Changed some text to be more meaningful
    
    Change-Id: I1891d6ac541421606dda30ed10f9b40b21e2fa52
    BUG: 3028
    Reviewed-on: http://review.gluster.com/18
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Vikas Gorur <vikas.gluster@gmail.com>

commit 9e7f02aa79e889e4b91604ef84b5f948dc3787f9
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jul 18 17:13:54 2011 +0530

    news: note the move to gerrit
    
    Review changes incorporated
    
    Change-Id: I3d19a68ea22873a5fdd1a3cacea1ba37bf8dbd0f
    BUG: 1

commit fbe8cc85a10bf57689d836457cfb59c5c51554c7
Author: Anand Avati <avati@gluster.com>
Date:   Mon Jul 18 16:06:59 2011 +0530

    s/Patchwork/Gerrit/
    
    Change-Id: I3d2e0c081cce5c69a6a168ddd0d850cdba84f53e

commit 15d2e7dd88f640c7e30989d37e735e37070119d8
Author: Anand Avati <avati@gluster.com>
Date:   Mon Jul 18 15:47:05 2011 +0530

    fixed URL in README
    
    Change-Id: I2ce02b67ee844119f854a0a2e83b5ebeb036801a
    BUG: 1

commit 1357fa6fa07bc34248643d2b9a329bddc873b15a
Author: Anand Avati <avati@gluster.com>
Date:   Mon Jul 18 14:54:25 2011 +0530

    Fixed URL in README
    
    Change-Id: I134e8d57b188025a115fcfc363009bb3893676a1
    BUG: 1

commit 0773f5a34e3b5c503674bceaa1902454fc841879
Author: Sachidananda <sac@gluster.com>
Date:   Sun Jul 17 08:10:29 2011 +0000

    Strip extra `/' from filenames.
    
    While peforming replace-brick, delete-brick, remove-brick... and related
    operations resolve extra slashes as single path separator. i.e treat /foo//bar//
    as /foo/bar.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3183 (When creating volumes brick paths are not handled properly.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3183

commit 613a6369d63e3ec87735a5427e4e87894f884749
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Apr 11 03:13:34 2011 +0000

    mgmt/glusterd: allow add brick in pure replicate setup
    
    Currently in pure replicate if the replica count is 4 and there are
    4 bricks, then suppose 3 bricks are removed then add brick works only
    if 3 bricks are provided. Providing lesser bricks fails.
    This patch fixes that scenario.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1574 ([glusterfs-3.1.0qa18]: add-brick to a replicate volume fails if a brick is removed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1574

commit 273f898364463cd10165fc82c8c5250a0962c452
Author: Sachidananda <sac@gluster.com>
Date:   Sat Jul 16 12:54:00 2011 +0000

    Canonicalize path names while creating volumes.
    
    When a volume is created resolve symbolic links, delete duplicate slashes in the
    path name.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3183 (When creating volumes brick paths are not handled properly.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3183

commit 260edb905171ebed3692eaeca404d13202cd5fd0
Author: Pranith K <pranithk@gluster.com>
Date:   Sat Jul 16 08:20:11 2011 +0000

    PUMP: set pump lk_owner,pid to frame->root
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3182 (Afr self-heal should happen with out big lock)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3182

commit b43038ee84839fa6b0e6aee037f7d952d8f52b6d
Author: Pranith K <pranithk@gluster.com>
Date:   Sat Jul 16 08:19:47 2011 +0000

    cluster/afr: Don't depend on fuse lk_owner for inodelks
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3182 (Afr self-heal should happen with out big lock)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3182

commit 97807e75956a2d240282bc64fab1b71762de0546
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jul 14 06:31:47 2011 +0000

    storage/posix: Remove the interim fix that handles the gfid race
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2745 (failure to detect split brain)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2745

commit 61f68b31f24311d09f4d2a02968ff52fd7b5a73f
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jul 14 06:31:33 2011 +0000

    storage/posix: Succeed lookup even if there is no gfid on the file
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2745 (failure to detect split brain)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2745

commit 5dff9a2938c199285662bb5b33d7e3aeda0e3fb6
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jul 14 06:31:08 2011 +0000

    cluster/afr: Fix conflict files and gfid self-heal
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2745 (failure to detect split brain)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2745

commit 84c3d7a83a8c84ca11514202a1bc365026fd1c87
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jul 14 06:30:40 2011 +0000

    cluster/afr: Detect conflict/gfid self-heals
    
    Added some helper functions that can be reused
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2745 (failure to detect split brain)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2745

commit 10e50f9df6de9efccd66dc8b37c73c52569e3559
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jul 14 06:30:20 2011 +0000

    cluster/afr: make expunge/impunge re-usable
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2745 (failure to detect split brain)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2745

commit b0a3a3fda3f0993cd8c0e1b135bb569b6543e7c0
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jul 14 08:07:46 2011 +0000

    cluster/afr: Choose next call child from fresh-children for inode-read-fops
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2840 (files not getting self-healed when the first child goes down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2840

commit bfc0e16e43815ab6d6e67f4bd26694ebd72b3360
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jul 14 08:07:04 2011 +0000

    cluster/afr: Add fresh children along with read-child to inode context
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2840 (files not getting self-healed when the first child goes down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2840

commit 64b2a56ad0f8ddae9ece8696f7d50a3129c145a3
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Jun 27 03:10:23 2011 +0000

    cluster/afr: Move afr local alloc functions from header files to sources
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2840 (files not getting self-healed when the first child goes down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2840

commit bf8e3a864eafe7eef5795cd134f6c0d5812a4f17
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Jul 15 01:22:51 2011 +0000

    io-threads: Initialize mutex and cond
    
    Thanks to Emmanuel Dreyfus for sending out the fix.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3170 (Uninitialized mutex and cond in io-threads)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3170

commit 1742383787355241d5aaa4b2bdd92d089ef2d508
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 15 01:05:16 2011 +0000

    posix: perform readdir filling in locked region
    
    When two application threads share an open dir fd (DIR *) and issue
    readdirs, storage/posix will receive separate readdir fops in separate
    threads in parallel. This has two-fold issues
    
    1. In the following pair of operations -
    
       entry = readdir(dir)
           and
       strcpy (gf_dirent->name, entry->d_name)
    
       @entry is a static buffer in libc which can get reused by another thread
       to get filled with a longer name. This can cause the second operation
       to overflow the buffer as the allocation was for the smaller name.
    
    2. In the following pair of operations -
    
       seekdir (dir, offset)
          and
       entry = readdir(dir)
    
       If two threads are executing these sequence in parallel in separate
       threads, then one of them will end up reading wrong/unexpected entries.
    
    It would be sufficient to fix 1. by using readdir_r but that still keeps
    the second race open. Hence the patch moves all the set of operations to a
    locked region which solves both races.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3171 (Crash in server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3171

commit f50e5eb7777ee31701f5d757ffa8de2c238b5e50
Author: Gaurav <gaurav@gluster.com>
Date:   Mon Jun 20 07:59:27 2011 +0000

    Glusterd: IPV6 support for glusterfs.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2456 (IPv6 support for glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2456

commit ded0a9a2a0a9024def7a4b199ac3bbfa5d66485a
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 13 02:08:05 2011 +0000

    cluster/stripe: send the xattr keys with create/mknod itself.
    
    so stripe is more acl friendly
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3160 ([818f8c87d56bc46d0d0903275699351b66f17e57] Posix compliance test hangs during link tests in distributed-stripe.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3160

commit 5d7657c4b48a73305cf35986323121e7dfe92bef
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 12 05:20:10 2011 +0000

    storage/posix: make sure we are starting on a genuine backend
    
    also do the check in 'glusterd' to let the user know of the
    problems (if any) during the volume create/start time itself.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3065 (make sure the export directories are not re-used as part of another volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3065

commit 7f4f7765597a7f0daa5bca7c3bcb2479d7ed15bc
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 1 04:42:14 2011 +0000

    glusterd-rebalance: utilize distribute's internal rebalance feature
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3070 (After 'rebalance', the gfid of the file gets changed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3070

commit 8d18bc22d1cfc8a481bc8d20da5843c65b567226
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 1 04:41:54 2011 +0000

    distribute: bring in feature to do rebalance from inside
    
    do the 'rebalance' on a file with 'setxattr()' with
    'distribute.migrate-data' key. the valid 'value' is "force" or
    anything else.
    
    current implementation of 'rebalance' is same as 'glusterd-rebalance',
    and hence comes with limitation of not rebalancing hardlinks, non-regular
    files, and files with open-fds.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3070 (After 'rebalance', the gfid of the file gets changed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3070

commit 3f76fe277ec0a826bf3052134ad877ee65ce9e79
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 1 04:40:05 2011 +0000

    cluster/distribute: bring in directory-spread-count option
    
    global spread count option is given through volume file
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2257 (enhance distribute to control the spread count (ie, control the hashing range))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2257

commit 6cf06cfd4bf72b16ac7665323629d354b78b6b05
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 1 04:39:41 2011 +0000

    cluster/distribute: handle layout overlaps while giving a new fix
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit 05a1422bbd82a28ccf7fa7c17b357f8350508e6e
Author: Junaid <junaid@gluster.com>
Date:   Sun Jun 26 09:35:21 2011 +0000

    Revert "features/marker-quota: hold lock on dirty inode's parent while healing a dirty inode."
    
    This reverts commit cd2518b4ab627471db74d7f4a473416f318754db.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 9dd6f5a66b3d1ba703e55e06a26f1121ef96c1d4
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Jul 13 04:33:43 2011 +0000

    mgmt/Glusterd: Fix build warning
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit b5938787afbf3c24ee4fc995e72577f1369ceb7a
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Jul 13 04:33:42 2011 +0000

    io-stats: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit 5c6fb46c64f2c8e51da2090dd554abfdbfd2b53e
Author: Kaushal M <kaushal@gluster.com>
Date:   Wed Jul 13 04:11:53 2011 +0000

    Changed error message displayed and logged, on rebalance failure
    
    Signed-off-by: Kaushal M <kaushal@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3106 (Rebalance start failure message is not appropriate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3106

commit c4da48f0dc9858e70555bf92374cb9e6a6f088b9
Author: Pavan <tcp@gluster.com>
Date:   Wed Jul 13 03:34:18 2011 +0000

    nfsrpc: Re-order NFS auth array contents
    
    Some NFS client implementations can default to AUTH_NULL given a certain order
    of auth_array in MOUNT reply. We re-order it here to make sure that such
    clients (Example - 2.6.26), do not have such security loop holes.
    
    Signed-off-by: Pavan T C <tcp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3144 (permissions given in fuse mount don't have effect in nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3144
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3144 (permissions given in fuse mount don't have effect in nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3144

commit c77014be787a1d8ff23923b53b39054da35785de
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 13 03:34:02 2011 +0000

    posix-acl: perform access checks on read/write/truncate for NFS calls
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit e27c4da87295a210e77ca13ff23a24078abc25c0
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 13 03:33:47 2011 +0000

    access-control: Handle F_OK in perm check, and O_APPEND, O_TRUNC in open
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057

commit 4223545bdc67383e622d34ee878d3461ad4f63b0
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 13 03:33:26 2011 +0000

    DHT access: For nfs calls, op_ret is always 0, and mode is op_errno
    
    Return the values received from the subvol
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057

commit e103ab41f3fd917e9a6df3d6113e2c4c3603b29b
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 13 03:32:53 2011 +0000

    NFS access control list: Decode the NFS requests into mode format
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 3057 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057

commit 9388760b9aad1ae2512eb108a4ca6b5c8638ea07
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 13 03:32:41 2011 +0000

    access-control: NFS access control expects a return of valid mode
    
    The permission check is same as that of posix. We break the requests
    into single checks, aggregate all the valid modes and return in reply.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 3057 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057

commit 9f2adc333dad1beb17b81bd55f5e32366320a4dc
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 13 03:32:02 2011 +0000

    access-control: Save group permissions returned from backend
    
    The backend permissions returned in stat for group is already masked
    value. Use the xattr value
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 3102 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3102
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3102 (Read calls go ahead even when the group has no permissions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3102

commit 843ffc77e0f1ba6cc1b2332f0a57e2fa339c9f4c
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 13 03:31:47 2011 +0000

    access-control: Return mode part of NFS access control request
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 3057 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057

commit e89725cd62430addf09d9c1afbfb07d8c86b9ef0
Author: Rahul <rahul@gluster.com>
Date:   Tue Jul 12 13:47:51 2011 +0000

    Check type for a value greater than Distribute and not for stripe
    
    Signed-off-by: Rahul <rahul@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3161 ([818f8c87d56bc46d0d0903275699351b66f17e57] Volume type incorrect.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3161

commit 7c4ad6d3321cc440590a6132b7dc8d0d0a58ce3b
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 13 00:37:25 2011 +0000

    storage/posix: set all keys present in 'params' dict while creating an entry
    
    so, there is no need to do a 'setxattr()' after entry creation, which could now
    fail due to ACL on server side.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3164 (set xattr keys while entry creation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3164

commit 8b57a5c2fb16f2c85c0f74edbe7b841a6dc4a265
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:39 2011 +0000

    protocol/client: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit e312fb0ffaaf4e5bcf69dcebaabcbd3898ba8765
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:38 2011 +0000

    write-behind: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit 2f457d1a6441903327b0da5e01f9cad186b13ef5
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:37 2011 +0000

    quick-read: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit aa9f9c3113009f136642e9bdedfcef6d04d85b44
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:36 2011 +0000

    io-threads: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit 14426adfe61fde6c6e6367a6025f314046ed8aa5
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:35 2011 +0000

    io-cache: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit a3009537811b4343c86f13555717eef5e0ea2641
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:34 2011 +0000

    quota: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit 61f4b2b5f10bc1f36c86dac5a9a9d640975dee11
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:32 2011 +0000

    stripe: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit 6b40f3eba97c8aad653f0602754127f7ae5a9707
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:31 2011 +0000

    dht: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit e87432be87c37c36467a85e3d2c55970f8439915
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:30 2011 +0000

    afr: changes in volume_options to assist volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit 1d0cb953bb117689fb8381d65932ead486d13b05
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jul 12 05:33:29 2011 +0000

    mgmt/Glusterd: Implementation volume set help/help-xml
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2041 (volume set help option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2041

commit f9e0638b7597f4b1a4245f63c94d3d6bd3158136
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Jul 4 06:32:32 2011 +0000

    nfs: Change NFS3 access op to use access fop
    
    This change is needed so that we have a uniform dependence on
    posix-acl for permission checks as well as ACL checks.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3057 (acl permissions don't work on nfs mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3057

commit 43d6d33d35618eb684975d6f0d1263e25ae6466c
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Jul 7 03:03:40 2011 +0000

    features/locks: Do not block UNLOCKs
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit e30c38b783c728182eb9cc478fabc7a7830c8efc
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jul 6 08:35:14 2011 +0000

    mnt/fuse: generate uuids in fuse_lookup, not in fuse_lookup_resume.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3041 ([glusterfs-3.1.5qa2]: stat gives EINVAL)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3041

commit 67f6fc6156cb14875600cd7e44d937587196e3b3
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Jul 4 02:27:06 2011 +0000

    glusterd: check replica_count for 0 before using it for volume creation in stripe replicate volume
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3123 ([a7cdaf3de307c96cb55219a0743962ee1e1fc955]: glusterd crashed when started)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3123

commit 4c55f76d6a4d13ec1ed3cffd31ff4acc3d3122f0
Author: Venky Shankar <venky@gluster.com>
Date:   Fri Jul 1 00:18:53 2011 +0000

    afr/stripe: collect pathinfo xattrs from all childs
    
    Signed-off-by: Venky Shankar <venky@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3046 (getxattr for afr should returns realpath from all childs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3046

commit 1a82b4539b69390dfb1a158c420385c7ad5d999f
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Jun 17 07:20:08 2011 +0000

    cluster/afr: Handle lookups when self-heal is off
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2586 (read child is set without checking the xattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2586

commit 9866f23b9b0ceb8be876600be9832987b8646540
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 8 02:56:03 2011 +0000

    mount.glusterfs: fix to handle the error cases better
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3085 (backupvolfile-server option doesn't work)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3085

commit 44f57f49309116de175a9c91c84fb7b8999a05ad
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 8 02:55:40 2011 +0000

    cluster/stripe: quick-read friendly behavior in lookup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3140 (contents of files are invalid after apply patch 7573)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3140

commit fcce7c289a0c27345404ab17e2cce6e8f5ad7fc9
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 8 02:55:20 2011 +0000

    cluster/stripe: cleanup and memory leak fixes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3140 (contents of files are invalid after apply patch 7573)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3140

commit fa1feca4172776ba4ae011ffa679a02055951e37
Author: Krishnan P <kp@gluster.com>
Date:   Tue Jul 12 02:31:05 2011 +0000

    server: Reassociating 'old' conn can lead to chaos.
    
    Since we moved to a single socket connection b/w client and server,
    inherting connection state is unnecessary and can sometimes be
    dangerous when clients reconnect even before the server detects
    a socket error on the old connection.
    
    Dirty detail: This reassociation results in 'ref count' not decreasing
    in tandem with the connection disconnects. This results in a resource
    leak.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3104 (Self-heal does not work in dis-rep!)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3104

commit 42e0b1731d925fd5a0bfaa107a2e01ba47fae125
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 12 05:29:25 2011 +0000

    cluster/distribute: send proper 'params' dictionary during linkfile creation
    
    when the code path enters the 'subvol_filled()' case, local->params is set,
    which contains the 'gfid-req' value, but the linkfile creation was not
    checking for its existance.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3159 (mknod (linkfile creation) with no 'gfid-req' key)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3159

commit 2c688714a2a081fc1be30febcd839caf8e201456
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 12 05:16:46 2011 +0000

    storage/posix: move the helper functions to separate file
    
    helper functions were more than 800 lines
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3158 (Keep code more readable and clean)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3158

commit 79f4135994e5051c711595c791d5831bdad24738
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 12 05:16:32 2011 +0000

    storage/posix: call 'gfid_heal()' instead of 'gfid_set()' in lookup()
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2994 ([glusterfs-3.2.1qa2]: untar and rm in parallel hangs untar)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2994

commit 818f8c87d56bc46d0d0903275699351b66f17e57
Author: Sachidananda <sac@gluster.com>
Date:   Mon Jul 11 05:37:39 2011 +0000

    Fail volume creation on existing directories of a read-only file system.
    
    Thanks to kp@ for the fix.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2609 (Error message not properly provided when trying to create a volume from a read-only source)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2609

commit 03df277c7880541570107bbaa7f91e5cf7ad5a69
Author: Krishnan P <kp@gluster.com>
Date:   Tue Jul 12 01:51:17 2011 +0000

    pump, afr: dict related memory fixes.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2489 (GlusterFS crashing with replace-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2489

commit 1f5119627b278b98518afb68a7eb88752932976c
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jul 12 02:11:59 2011 +0000

    cluster/dht: fix race between two directory renames
    
    let the race get arbitrated at the dst_hashed subvolume.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2522 ([glusterfs-3.1.3qa8]: rm -rf shows invalid argument)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2522

commit b894a5c79f93707149181a51bfab67fdbffcc43b
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jul 12 02:11:42 2011 +0000

    storage/posix: detect race in posix_rename()
    
    detect a race in rename between two clients by checking for
    reassigned gfid or presence of dir when not expecting.
    
    checks not necessary for rename of files.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2522 ([glusterfs-3.1.3qa8]: rm -rf shows invalid argument)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2522

commit a9080b7c706be4ac917866d73e70e36fd933b54d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jul 7 01:33:05 2011 +0000

    client-handshake: skip CHILD_DOWN notifications when client is querying port using different volume names in the presence of rdma.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3091 (rebalance fails with "transport endpoint not connected" in 3.2.1 rdma set-up)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3091

commit e9c29f722776a91993403428cafdb2b7e1056bd8
Author: Junaid <junaid@gluster.com>
Date:   Thu Jun 23 03:20:09 2011 +0000

    debug/io-stats: Added sys-log-level option.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3044 (provide option to set syslog loglevel through CLI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3044

commit 089ae1b7299f2d30a7b56da0c700f42d7a0341d7
Author: Junaid <junaid@gluster.com>
Date:   Thu Jun 23 03:19:15 2011 +0000

    mgmt/glusterd: Make glusterd aware of sys-log-level options.
    
    There are two options:
      * brick-sys-log-level
      * client-sys-log-level
    Which set the log-level on brick and client respectively. Uset
    
      gluster volume set <volname> <brick|client>-sys-log-level value
    
    to set the option.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3044 (provide option to set syslog loglevel through CLI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3044

commit ae5f7c2c1d88cee0029c555f2416fe7c998cc1c2
Author: Junaid <junaid@gluster.com>
Date:   Wed Jun 29 03:13:56 2011 +0000

    libglusterfs/logging: Added functions to set sys-log-level.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3044 (provide option to set syslog loglevel through CLI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3044

commit e9d960391794db917bd3e984c8dc3fd7e3cec706
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jun 1 08:00:03 2011 +0000

    quota: update limit stored in inode-ctx when limit is removed on a directory.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2971 (quota remove command doesn't remove quota on directories.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2971

commit cf395e9af76de16162328fbcf0aef4e8c72adfb8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jun 22 02:35:58 2011 +0000

    fuse: fix inode-leaks in fuse_lookup_and_resume codepath.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2525 ([glusterfs-3.1.3qa8]: inode leak in rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2525

commit b320532ca74643108df399663e3c002af3e0e219
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jul 6 02:18:49 2011 +0000

    fd: put the fd back to fd_mem_pool of inode table instead of freeing in case of failure
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3103 (memleak in inode table creation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3103

commit 500813986241a8b5f6ff0658f4471a8f58e6c48e
Author: Vishwanath <vishwanath@gluster.com>
Date:   Fri Jul 1 07:39:21 2011 +0000

    remove hardcoding of transport type to "tcp" while generating vol files in replace-brick
    
    Please ingore previous patch for this. Please consider this one.
    
    Signed-off-by: Vishwanath S Bhat <vishwanath@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>

commit a36225a984240629a906608c85a9ac7e432aacfe
Author: Rahul <rahul@gluster.com>
Date:   Fri Jul 1 05:53:10 2011 +0000

    Fixes missing ".." entry in the mount point
    
    Signed-off-by: Rahul <rahul@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3097 ([b7aeaa619b82509fbe8d187bbc1618cb319d6877] ".." entry in mount point missing.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3097

commit bf4a7bed6420377aac26693f450a450bc54d005c
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jun 27 07:59:52 2011 +0000

    libglusterfs/syncop: add more functions
    
    do proper 'ref's and implement 'write()' and 'ftruncate()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3081 (synchronous operations should be enhanced)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3081

commit a879613637f54a7a2016549b308b359b7577b5ad
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Jul 5 23:08:40 2011 +0000

    cli: Exit if glusterd is not operational in non-prompt modes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3120 (Provide connection timeout between cli and glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3120

commit 8f14d85777c93277403bcac727c0447dcba3cdc0
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:19:39 2011 +0000

    mount.glusterfs: support -o acl parameter
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 57b3b7e62487eef4c534e3fe65f954cf5d6d0ce4
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:19:29 2011 +0000

    glusterfs: add --acl command line option to load ACLs on the client side
    
    also set the turn off filtering of ACL keys in FUSE xattr FOPs.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 4b643cfa8847be71bb381b5a8a1a420837722e51
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:19:15 2011 +0000

    access-control: superseded by posix-acl translator
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 04ed499a8eef1c77c491227941d187778fb5c2e4
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:18:10 2011 +0000

    posix-acl: implementation of POSIX ACL as a translator
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 6433214452c5d8d3ae63c5f4f578862be348ca63
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:18:04 2011 +0000

    storage/posix: set ACL keys during new entry/inode creations
    
    honor "system.posix_acl_access" and "system.posix_acl_default" keys in
    params dict to setxattr into the backend while creating new entry/inodes
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 54aaf46e5b6e95fe9df257728b76f67bdb5dd17c
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 8 03:23:08 2011 +0000

    fuse: introduce "noacl" option to disable ACL checks
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 8af1177029b7103ba84bc59eb58d7c5c8635e6cd
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:17:11 2011 +0000

    fuse: fill frame->root->groups with aux gids of the process
    
    Pick the groups in /proc/<pid>/status from the line starting
    with "Groups: " by parsing the list of integers which follow
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 14d65cb9e0c6f5a6176014701c86760a392d3a44
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:17:04 2011 +0000

    dht: set linkto xattr with linkfile create (mknod)
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit 1a70453c6501e149cd415f5f11048cf44e526d6c
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 1 17:16:50 2011 +0000

    byte-order: htole*/letoh* and htobe*/betoh* for forced endian conversions
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2815 (Server-enforced ACLs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2815

commit a40c52707762258eddb35a63ee1f78bc4e0a52dd
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jul 6 03:10:05 2011 +0000

    dht disk usage: Correct free blk calculation
    
    Use f_bavial instead of f_bfree for %free calculation
    This fixes mismatch of df output wrt backend and glusterfs
    
    where: f_bfree = /* # free blocks */
           f_bavail; /* free blocks avail to non-superuser */
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3084 (Correcting percent calculation of disk space)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3084

commit a7cdaf3de307c96cb55219a0743962ee1e1fc955
Author: Junaid <junaid@gluster.com>
Date:   Fri Jul 1 05:17:42 2011 +0000

    features/marker-quota: call stack destroy when hardlink count is not greater 1.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit ac683df2322123472ba52dbeecb9cd5512ecc58c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Jul 1 00:12:35 2011 +0000

    mnt/fuse: Do a pthread_cond_broadcast for both CHILD_UP and CHILD_DOWN events.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3091 (rebalance fails with "transport endpoint not connected" in 3.2.1 rdma set-up)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3091

commit a21c3bb99e5ad59e8e9ec0a050ce8617ce3fe167
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Jun 30 06:59:12 2011 +0000

    inode table: avoid memleak by freeing the allocated structures incase of failure
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3103 (memleak in inode table creation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3103

commit 64316c419f013464641b84900acc0ff4eeeaf2ae
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jun 30 03:20:31 2011 +0000

    rpc-transport/rdma: call ibv_fork_init to make rdma work with fork.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3091 (rebalance fails with "transport endpoint not connected" in 3.2.1 rdma set-up)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3091

commit ea6763a5b956c29f4c1862ed355398631ff4a9cc
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jun 30 03:20:50 2011 +0000

    mount/fuse: wait till CHILD_UP event is recieved to do the first lookup.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3091 (rebalance fails with "transport endpoint not connected" in 3.2.1 rdma set-up)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3091

commit 935d7744674ec961dd967133721de1429460c91f
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jun 23 01:12:48 2011 +0000

    cluster/afr: fix the range of the lock taken in [f]truncate
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3077 (afr [f]truncate locks wrong region in transaction)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3077

commit 91086a2a7dcbfa30cdb5c188e9268ae4379bd28e
Author: Junaid <junaid@gluster.com>
Date:   Tue Jun 28 03:01:12 2011 +0000

    mgmt/glusterd: return 0 when glusterd_op_get_ctx fails on other glusterd's.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3078 (Quota: list comamnd fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3078

commit 41650a8c03ad86bcebe8c595ab9e7f13ec899a4f
Author: Junaid <junaid@gluster.com>
Date:   Thu Jun 30 00:46:20 2011 +0000

    features/marker-quota: Change the log-level of gf_log to debug in quota_inodelk_cbk().
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 7388f9f5910c0c69039a1476d902b48dda98b394
Author: Junaid <junaid@gluster.com>
Date:   Wed Jun 29 20:41:27 2011 +0000

    mgmt/glusterd: 'Quota' use quota-crawl.log to store logs of maintainence mount.
    
    Allow to set limits even when quota is disabled.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2620 (CLI improvements in quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2620

commit 7cd21dec47426e32be9f4548f4ec716b0575867e
Author: Junaid <junaid@gluster.com>
Date:   Wed Jun 29 20:41:17 2011 +0000

    cli: 'Quota' use quota-list.log to store logs of maintainance mount.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2620 (CLI improvements in quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2620

commit b7aeaa619b82509fbe8d187bbc1618cb319d6877
Author: Junaid <junaid@gluster.com>
Date:   Mon Jun 20 07:11:47 2011 +0000

    features/marker-quota: Skip contribution creation on root.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 83d1f9642e7310f085caaeb0c5b72a88c445d31b
Author: Vishwanath <vishwanath@gluster.com>
Date:   Thu Jun 23 05:41:39 2011 +0000

    spelling corrections in glusterfs code
    
    Signed-off-by: Vishwanath S Bhat <vishwanath@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2903 (Last spelling errors in source code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2903

commit a846faead3d416d9af75106694e85a776f7d07a8
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 22 23:23:06 2011 +0000

    distribute: handle 'fix.layout' key in setxattr() instead of getxattr()
    
    as 'fix.layout' command does changes to directory layout, its not a
    'read/get' type of operation, and hence as per the symantics, it suits
    setxattr() better
    
    also fix a memory leak in getxattr(), where 'local' was allocated twice
    in few cases
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3075 (the 'fix.layout' command should happen through 'setxattr', not getxattr().)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3075

commit 308668c055b542724d226a3b7a835e7ea06082ed
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 23 08:07:23 2011 +0000

    libglusterfs: added syncop_* functions
    
    * implemented open,close,readv,writev,listxattr,create,unlink
    
    * also fixed a dictionary ref issue with lookup_cbk
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3081 (synchronous operations should be enhanced)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3081

commit f948a24e51e447642c35bff881057f306768a5e0
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 23 01:51:47 2011 +0000

    bring in strict check on export directory being re-used for different volume
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3065 (make sure the export directories are not re-used as part of another volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3065

commit 89452c4db44966bb80601c73c3b835d002af9fd5
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 16 23:42:53 2011 +0000

    gluster volume info: fix the output of 'stripe-replicated' volumes
    
    also fix the glusterd-store to preserve the required information
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3040 (need a way to create volumes with 'stripe+replicate' setup..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3040

commit c9854677fcd5a0a68e885cc18b6d9d6d92218f23
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 21 04:56:41 2011 +0000

    gluster volume create: option for stripe + replicate volume
    
    So RAID01 like option is a possibility
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3040 (need a way to create volumes with 'stripe+replicate' setup..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3040

commit 0d87bfca5c9a95977215599d5800e751ec8f2205
Author: Sachidananda <sac@gluster.com>
Date:   Wed Jun 22 05:57:06 2011 +0000

    Fix typos in manpages.
    
    Thanks to: Patrick Matth?i <pmatthaei@debian.org> for patches.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2902 (Errors in manpages)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2902

commit d7642fb9bc13bb9c2da35bd8e80c311d5fc5096c
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Jun 22 04:24:58 2011 +0000

    Stripe selfheal: Prevent spurious STACK_DESTROY call
    
    The stack is destroyed in the cbk
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3056 ([4597929cc527f8abaf9ef9e1d5499ea416e5c7ff] Crash in client at client3_1_mknod_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3056

commit 9123fd82ab1946ed6f2c3d025043da1183d84d31
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jun 22 02:51:50 2011 +0000

    fuse: consider a lookup as revalidate even if the inode is present in new graph.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3041 ([glusterfs-3.1.5qa2]: stat gives EINVAL)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3041

commit 305b40239fda0b01537f05f94c3184e9523594c4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Jun 21 05:07:04 2011 +0000

    performance/quick-read: Perform error handling only when GF_CALLOC fails
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3011 (Uninterruptible processes writing(reading ? ) to/from glusterfs share)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3011

commit f63dabd5d68a0904967705937380fed1eb9c99cf
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Jun 21 03:22:09 2011 +0000

    Stripe lookup: aggregate xattrs
    
    stripe default setxattr works on first child. If the first cbk is
    not the first child, then we were loosing the xattrs.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3066 (aggregate xattrs in stripe lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3066

commit 1d85e0dc80c19645f924c8fcbbb32c53ef09e701
Author: Junaid <junaid@gluster.com>
Date:   Tue Jun 21 00:51:25 2011 +0000

    mgmt/glusterd: Enable quota only when volume is started.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2620 (CLI improvements in quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2620

commit 71a13f09978dc3858b9dd2771f605582e0c2e0dd
Author: Gaurav <gaurav@gluster.com>
Date:   Mon Jun 20 08:32:59 2011 +0000

    NFS : Pass valid argument in mnt3svc_dump.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2692 (NFS server crashes on showmount -a)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2692

commit 8c24158f2bda14e9debcc2f4ccde53aa9629c2b7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Jun 20 01:46:07 2011 +0000

    performance/quick-read: reset open_in_transit to zero in case of an error.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3011 (Uninterruptible processes writing(reading ? ) to/from glusterfs share)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3011

commit 608b22609793549eb8e8e2b2899af2d1ff5c193c
Author: Krishnan P <kp@gluster.com>
Date:   Mon Jun 20 01:01:20 2011 +0000

    pump: mark pending before notify to children to avoid race in single CPU.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3050 ('replace-brick' hangs on vm's)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3050

commit 96ae0db506f43ceed0d3346d0351b1bb73b0b19c
Author: Junaid <junaid@gluster.com>
Date:   Sun Jun 19 23:41:25 2011 +0000

    features/quota: Print a log when reconfigure fails.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2775 (crash in reconfigure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2775

commit 1748b0c7925fa2165cbf11c4aab90e07bff7d4cb
Author: Krishnan P <kp@gluster.com>
Date:   Mon Jun 20 00:56:10 2011 +0000

    afr: bg self-heal must be off if self-heal-count=0.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3036 (self-heal problem in replace-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3036

commit b64dd21f05016065e0b825db62da87981554df88
Author: Sachidananda <sac@gluster.com>
Date:   Sun Jun 19 12:51:45 2011 +0000

    Fix the command line log to display correct error message.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3054 (Typo in cli message)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3054

commit d4df768b6efff0da2931396b8b9b28c5174e4d7a
Author: Sachidananda <sac@gluster.com>
Date:   Sun Jun 19 11:07:31 2011 +0000

    Print error message to report missing mount point.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3053 (No proper error is shown when the mount point is not present)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3053

commit 58cf35b353f5a9fedfddd6da2f5811c58f1be3cc
Author: Gaurav <gaurav@gluster.com>
Date:   Thu Apr 7 01:42:33 2011 +0000

    CLI : Display possible options in proper format.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2598 (Volume access option suceeds with any string value)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2598

commit 2f07f751bf69a196df85d3e715c0ad1a7a26419c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed May 11 02:42:21 2011 +0000

    extras: Add quota-related debugging scripts.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit e2685adcb71b30621e34905584910390e0b248e1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri May 27 01:17:12 2011 +0000

    print the owner and the transport for the blocked locks in server statedump
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2949 (self-heal hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2949

commit 4c81f6268d254f452b861bcd63608982c3ddb560
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jun 18 03:53:46 2011 +0000

    stack: make process state dump more debug friendly
    
    store points of stack wind and unwind (function names) for each
    frame and dump them in process state dump
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 50001216d26a16736691ab06758049c22e664936
Author: Junaid <junaid@gluster.com>
Date:   Wed Jun 15 02:41:36 2011 +0000

    cli: Print the error message sent by glusterd when quota list cmd fails.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2856 ([glusterfs-3.2]: Misleading 'quota remove' output.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2856

commit 4e1ec35ef4f7bbf70c3e08e7c246946551f19e93
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 16 07:48:22 2011 +0000

    core: fill 'ia_ino' from 'ia_gfid' in 'storage/posix' to preserve same ino number
    
    take the least significant 64bit from gfid and assign it to 'ia_ino',
    hence for a given file (or directory), the 'ia_ino' number is always
    same, and we need not worry about the 'itransform' in 'cluster/*'
    translators.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3042 (inode number should be constant on storage)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3042

commit f04898973f15cfa13fcf39a903786983885352bc
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Jun 10 00:34:10 2011 +0000

    cluster/afr: Give proper device id for mknod
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2840 (files not getting self-healed when the first child goes down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2840

commit 17d3a0fc214c347d9e0a6cc4855302a41a09b535
Author: Junaid <junaid@gluster.com>
Date:   Thu Jun 16 21:57:40 2011 +0000

    mgmt/glusterd: chdir into mount in second child process while crawling the fs in quota enable.
    
    Because the management mount is waiting for glusterd's response and glusterd is
    doing waitpid on the child which is trying to do chdir into mount, thus causing
    a deadlock situation.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2560 (Lazy umount should be done for the maintainance mode mountpoint)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2560

commit 0101eb0b6444dc22860d8fdc82170aefa87ff0b3
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 16 06:43:12 2011 +0000

    logging: fill proper domain names at places where it is missing
    
    also changed some error messages where it was not explicit
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 25e8700721a71128c9f6143dc2effcdbcee692fc
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 16 05:30:05 2011 +0000

    gluster rebalance: handle the migration of files with 'holes'.
    
    treat a block (512bytes) of '0' as hole too (something like 'rsync')
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit e3a061d6fa5f436fe37493b7257860014ae75950
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 16 07:39:43 2011 +0000

    gluster rebalance: bring in a 'force' option
    
    * also correct the free space available logic to check the size
      without the file in migration (this considers the sparse files too)
    
    * 'force' option will bypass the free-space check logic, hence will
      cleanup all the linkfile
    
    * 'force' option is valid only with 'migrate-data' option
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit 442f64a83bd2c5da085bc6dc50533df2d483be3b
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 16 04:36:46 2011 +0000

    build: fixes to work on solaris
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3002 (build issues on solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3002

commit 41263d553f25e4f59d2751e7e3b2a23b264370f8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:56:01 2011 +0000

    features/marker-quota: use contribution value to reduce parent's size, if the value to be subtracted is not passed as argument to reduce_parent_size.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit cd2518b4ab627471db74d7f4a473416f318754db
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:55:51 2011 +0000

    features/marker-quota: hold lock on dirty inode's parent while healing a dirty inode.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 1040e5149c90e5452c4e86bec5763c392840d160
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Jun 14 23:55:40 2011 +0000

    features/marker-quota: hold parent inodelk during creation of xattrs on directory.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 5c1c571ad6582142772351e4c106a5b1182a77bc
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:55:30 2011 +0000

    features/marker-quota: check for refcount being zero holding lock in quota_local_unref.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit d773462f7c6d1c3c81fa691fc5911641c5bf4394
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:55:21 2011 +0000

    features/marker-quota: wipe parent_loc in marker_local_unref.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 1bdf3cdb86209af56c415151863d6cf67290944a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:55:09 2011 +0000

    marker-quota/rename: use contribution values from backend instead of in-memory while reducing parent sizes during rename
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 7e598e4baa1952d407c1edab329e01634fe719c4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:55:00 2011 +0000

    features/marker-quota: use mutexes while accessing contribution values.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit acbf2d5dd4782c4236373237d73980163936d17c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:54:47 2011 +0000

    features/marker: fixes in dirty inode self-heal codepath.
    
    - fix fd-leak of fd opened on the directory.
      - don't add (instead just assign) next offset at which readdir has to be sent
        to local->d_off.
      - assign to local->d_off before winding lookup call to get child contribution.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit c4c0f7cd9b951bf0f201fa6a52eaebfd4b86c45b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:54:36 2011 +0000

    libglusterfs/call-stub: Allow unwinding of frames for rename during call_resume_unwind.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 8dac046fb727995aca517cceadcc5c59efc8c3f2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:54:27 2011 +0000

    features/marker-quota: performance optimization.
    
    - abort updation process if delta is zero.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit a87555181d47522e985325c67b7d17c49dbd38de
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 23:54:16 2011 +0000

    features/marker-quota: fixes in rename path.
    
    - remove xattrs from newpath after rename is complete.
      - hold inodelk on both parents (if they are different) before doing rename and
        gather contribution values of oldpath and newpath to their parents while still
        holding the locks. Use these contribution values to reduce parent sizes.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 01d67311c83ae272f3ee3632c1e8f13ccebaca81
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jun 9 00:00:10 2011 +0000

    features/quota: after validation on a path, reset variable just_validated to zero before checking the size of parent.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2741 (Quota: new files not getting created even if space is available)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2741

commit 9d2b83aaecd66c161863379be3ec22d45ffbe4fb
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Jun 15 06:17:44 2011 +0000

    PUMP: perform opendir on pump xlator instead of its child
    
    When replace-brick is performed, there is a high probability for the
    directories on the source brick to not have any pending entry xattrs.
    So for proper self-heal we need the force merge to kick in.
    If the opendir is performed on pump xlator directory is examined and
    if the entries on its children do not match then force merge is
    triggered, so missing entries will be created on the sink.
    Pending xattrs are set from source to sink on the files present on
    source in this process. So when the lookup happens the self-heal
    is triggered.
    
         Before this fix, the code is working because the self-heal source is
    decided based on what file is biggest in size which is a wrong and
    removed.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2586 (read child is set without checking the xattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2586

commit 1b70ee9a2e469d2d970abf8e07c1c522c8bdc1df
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jun 10 06:56:49 2011 +0000

    cluster/distribute: remove the unused variable from 'conf'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3013 (error in the log file upon taking the statedump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3013

commit e1aa1e0e20e32e30284c5ffc1add92aebaaaf87e
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 9 00:15:59 2011 +0000

    rdma: fix the excessive logs
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit a7a2b8218958579006778b1200a0e40125291e0f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 8 23:37:46 2011 +0000

    build warning fixes
    
    mainly fixes all the sockaddr related 'strict aliasing' warnings
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2550 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2550

commit e719518e561033af0ffd07d0c8ad7d777715fe89
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 8 23:37:22 2011 +0000

    fixing some build issues in Mac OS X
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2966 (MacOSX compile failure: duplicate symbol _k)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2966

commit dad63fa8ac00397e337f328b0bb7b641e2680932
Author: Sachidananda <sac@gluster.com>
Date:   Thu Jun 16 07:56:33 2011 +0000

    Update man pages to include newer options.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2444 (keep man pages upto date with new codebase.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2444

commit 1d4378e0e78309682c13d0fc0c97c3c3bb6674b7
Author: Krishnan P <kp@gluster.com>
Date:   Thu Jun 16 01:28:28 2011 +0000

    pump: cleanup xattrs on both commit and abort path.
    
    This change makes glusterd to send a setxattr command
    for replace-brick commit operation similar to abort.
    
    Earlier we could commit even before the 'migration'
    of data was complete, with this change we fail that
    operation.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3033 (Changes to replace-brick and syntask interface.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3033

commit 4e6f6408b0e177dcdc0b19561bbaab6b7e26c23a
Author: Krishnan P <kp@gluster.com>
Date:   Thu Jun 16 01:27:42 2011 +0000

    glusterd: do_operation_abort and then kill dst_brick.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3033 (Changes to replace-brick and syntask interface.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3033

commit 87508c1edc7b8f4a88b2506ac642e878b1f2ac16
Author: Krishnan P <kp@gluster.com>
Date:   Thu Jun 16 01:26:55 2011 +0000

    afr: holding stack var via dict_set_static_bin corrupts.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3033 (Changes to replace-brick and syntask interface.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3033

commit 84fe7114833aed4efc31a1beaf7fcff0124c0ab4
Author: Krishnan P <kp@gluster.com>
Date:   Thu Jun 16 01:26:00 2011 +0000

    syncop: Modified to accept one 'non-frame' arg.
    
    Earlier syncops used to accept one argument which
    was a call frame to carry out the fops synchronously.
    Now we have two args passed to synctask function, one
    call frame and another void pointer.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3033 (Changes to replace-brick and syntask interface.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3033

commit 3f2c74a941f34b29dd92e4754d01ebea9db42218
Author: Sachidananda <sac@gluster.com>
Date:   Thu Jun 16 01:21:25 2011 +0000

    Delete/correct deprecated options in sample vol files.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3031 (Fix share/{doc,man} directory)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3031

commit 8791651c43337c081d684c04c4018c2c3eb56ac5
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jun 15 23:52:48 2011 +0000

    features/locks: check for inodelk lists and blocked inodelks instead of entrylk in inodelk.c
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3032 (entrylks are checked instead of inodelks while checking the blocked inodelks conflict)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3032

commit 4566fb78c16948f91e7d5b1934d8722b51508053
Author: Sachidananda <sac@gluster.com>
Date:   Wed Jun 15 06:54:22 2011 +0000

    Bring `examples' directory upto date.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3031 (Fix share/{doc,man} directory)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3031

commit 4ba661f5989db0148c7c1f4631645f932a99fe56
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Jun 14 12:31:07 2011 +0000

    features/locks:update the refcount while releasing a lock
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3025 (open lock and close leads to memleak)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3025

commit 9e59ce6d30f4ffd3dc7fb88c29fbd0ea79b9de28
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 01:42:10 2011 +0000

    performance-translators: print path to file while dumping fdctx.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 90117ca1c28b54845d617cdba0887d6453f875a4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 01:41:56 2011 +0000

    performance/read-ahead: dump pages in read-ahead cache.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit aae8ad0cf080ff3e4f704f3bcccef39a07cabb05
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 01:41:36 2011 +0000

    performance/stat-prefetch: dump cache and list of ops waiting for lookup completion.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit e8f67179ca60eb81a4b1fa92e37bd0eb6213d659
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 01:41:24 2011 +0000

    rbthashtable: implement traverser procedure.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 72d56ff2a8bd0eacfa8036f7583fc0dd4de460d0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 01:41:11 2011 +0000

    libglusterfs/inode.c: Add version of inode_path which can be called holding inode->lock.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 837f172e8775c908cb90c14a956ed010d468a0ad
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 01:40:58 2011 +0000

    performance/quick-read: dump inode and fdctx during statedump.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit dd4a0d45a91104117c0ad5de85deaabe6df88677
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 14 01:40:45 2011 +0000

    performance/io-cache: print cache information during state dump.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 1f14a1fccd5a8eed92936d9910d4b9a45ca1b56c
Author: Junaid <junaid@gluster.com>
Date:   Tue Jun 14 03:28:59 2011 +0000

    cli: 'QUOTA' Display the limit-set and size of the directory in KB, MB, etc
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2829 (Display the quota limit as it is configured)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2829

commit 6ae674eef777fda74191e2186d95778b9d5671f3
Author: Junaid <junaid@gluster.com>
Date:   Tue Jun 14 03:28:40 2011 +0000

    libglusterfs/common-utils: Added gf_uint64_2human_readable function.
    
    This function converts the given number to its corresponding representation in
    KB, MB, etc.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2829 (Display the quota limit as it is configured)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2829

commit a383d5b22aae9837f5609f304ee0488bcf8bafba
Author: Junaid <junaid@gluster.com>
Date:   Tue Jun 14 03:44:30 2011 +0000

    mgmt/glusterd: Set the generic options in the graph before merging it with the parent graph while building nfs-server volfile.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 3003 (Modification of one of the options of volume is reflected in all the volumes in the nfs-server-volfile)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3003

commit 4a95dd213c039834c958bc1e3845037aa87fcde2
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Mar 21 05:35:06 2011 +0000

    Prevent spurious getxattr for gfid-req in posix_lookup
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2570 (getxattr failed msgs seen in log when log-level is DEBUG)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2570

commit 2a2060359a6991e310e6532376273bccb9cfbadc
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Apr 12 05:19:22 2011 +0000

    DHT: check for mis-matching user xattrs
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2717 (Detect user_xattr mismatches for dir's)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2717

commit b81ab76a2b3163b9326c5c024c7dc5f51e6ae868
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 1 04:51:08 2011 +0000

    gluster rebalance: fix the mount command string
    
    error creeped in while bringing in 'runner' options
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit c31eb96811e6e99f79466fdf9c1dbb0c6fb00f7f
Author: Lakshmipathi <lakshmipathi@gluster.com>
Date:   Mon Mar 21 04:32:26 2011 +0000

    removed unused old sample files
    
    Signed-off-by: Lakshmipathi.G <lakshmipathi@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2552 (remove  old sample vol.files)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2552

commit 1b8376013d2358a50bd7487e1abaa377d51ec4e6
Author: Junaid <junaid@gluster.com>
Date:   Mon May 30 09:18:23 2011 +0000

    cli: Display a warning upon disabling quota.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2912 (Display warning upon disable quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2912

commit f87ec977c2c6bf8c562c11ad72069648beb6d8cd
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Jun 10 05:11:51 2011 +0000

    DHT selheal dir: Recreate dirs with correct gfid.
    
    When selfheal of dir is triggered, make sure the dirs are recreated
    with the correct gfid, to prevent mismatch of gfids in the backend.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2994 ([glusterfs-3.2.1qa2]: untar and rm in parallel hangs untar)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2994

commit 89e277a5deb2cd5191106119e91bf285a5b74e51
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jun 10 04:37:14 2011 +0000

    cluster/afr: propagate proper errno returned by lock fops
    
    If locks could not be held on any of the servers, then propagate the
    errno returned by the lock FOPs instead of hardcoding EAGAIN/EINVAL.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2993 ([glusterfs-3.2.0qa2]: hang while doing the selfheal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2993

commit 42c85439fe470a8cb4eb82944cb5ed094b740f8e
Author: Anand Avati <avati@gluster.com>
Date:   Thu Jun 9 02:32:01 2011 +0000

    cluster/dht: use GFID returned from hashed subvolume
    
    .. to perform lookups on remaining subvolumes. This way, if there is a
    race between two clients to 'fix' GFIDs with gfid-req, then the hashed
    subvolume will arbitrate and return the winner in stbuf->ia_gfid. This
    patch uses the returned gfid as the new gfid-req thereby preventing
    mismatching GFIDs on other servers due to further races.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2522 ([glusterfs-3.1.3qa8]: rm -rf shows invalid argument)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2522

commit 29397bda249d8d3f93dd6ee5c449b3590dbaf15e
Author: Lakshmipathi <lakshmipathi@gluster.com>
Date:   Tue Jun 7 03:47:11 2011 +0000

    build : use pid file to kill nfs process
    
    Signed-off-by: Lakshmipathi.G <lakshmipathi@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2969 (add --pidfile option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2969

commit 2b53a40350afa4dd9e0d77502700cdee0299766c
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 8 09:29:21 2011 +0000

    rpc-transport/rdma: don't return '0' in case of un-initiated rdma_connect()
    
    needed to handle the re-configuration of the port in client protocol. If
    there is a successful 'connect()' after the query port, the remote-port
    value gets reset to '0'. In this case, if the connect() return 0 for
    already connected socket, the query_portmap will keep happening in a loop.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2294 (Currently there is no way through cli to make a volume listen on both the transports (socket/rdma))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2294

commit d9db06e6ca108cada080de93d3cc25ba2b14becb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jun 8 09:29:06 2011 +0000

    nfs:command to change the transport type of nfs server for volumes of transport tcp, rdma
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2294 (Currently there is no way through cli to make a volume listen on both the transports (socket/rdma))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2294

commit 19f375da5b43f940131623b2f33675aa2b3f5c8a
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 8 09:28:49 2011 +0000

    fix multiple transport portmap issues in client handshake
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2294 (Currently there is no way through cli to make a volume listen on both the transports (socket/rdma))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2294

commit fe4eb7c3ac96218fe151633c5ccd34b7c0bea783
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 8 09:28:23 2011 +0000

    glusterd-volgen: fix rdma volume file path in case of 'tcp, rdma' transport.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2294 (Currently there is no way through cli to make a volume listen on both the transports (socket/rdma))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2294

commit aa9a6bc1bfd87aa70018dc6acc90fb94cba811c6
Author: Gaurav <gaurav@gluster.com>
Date:   Wed Jun 8 05:59:03 2011 +0000

    NFS : Don't set setattr_valid for exclusive create call.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2553 (NFS file create with Mac client and UNCHECKED mode returns "Operation not permitted")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2553

commit a9fd99f0d0206d4951aa50630b7921a50523bf23
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Jun 2 04:39:27 2011 +0000

    cluster/stripe: check if key is a valid ptr. before dereferncing
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2978 (Geo-replication fails on stripe(Master) setup.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2978

commit ddb2505383441b0bf41e31c13f90420f5d14d1dc
Author: Lakshmipathi <lakshmipathi@gluster.com>
Date:   Mon Jun 6 04:11:19 2011 +0000

    rpmbuild : restart glusterd after installing geo-replication rpm
    
    Signed-off-by: Lakshmipathi.G <lakshmipathi@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2901 (Cannot start geo-replication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2901

commit d11c17b8dae415f0f5c9af2cd4ec3423419ff996
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Jun 3 01:05:32 2011 +0000

    protocol/server: logging changes
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2982 ([glusterfs-3.2.1qa2]: logging changes is server protocol)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2982

commit 2c421f21040e1f9273cb9850c95756d3a4ca91af
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 2 02:59:07 2011 +0000

    performance/io-cache: fix the check of min and max file size.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2974 (volume set for 'cache-min-file-size' succeeds even if 'min-file size' is greater than 'max-file-size')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2974

commit 7959e867632baad702d1d5c8dc4fc4854d17e3e1
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Jun 6 04:22:47 2011 +0000

    glusterd: replace brick status grows with dir tree.
    
    replace-brick status message's size can grow long with
    deep directory trees.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2489 (GlusterFS crashing with replace-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2489

commit 125fc0ca98332cd20917daab0a170342b7f5e156
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Mon Jun 6 04:22:46 2011 +0000

    syncop: Increase stack size for deep call stack.
    
    pump performs a depth-first traversal of directories using the
    syncop stack and this necessitates a larger stack when handling
    deeper directory trees.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2489 (GlusterFS crashing with replace-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2489

commit e45c3e22a13332253fcc89ea528a4d77aa9ecc0f
Author: Junaid <junaid@gluster.com>
Date:   Mon Jun 6 22:36:43 2011 +0000

    mgmt/glusterd: Updated the error messages sent on cli quota command failure.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2856 ([glusterfs-3.2]: Misleading 'quota remove' output.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2856

commit 99588612db403dffdb6380ceaaec1a8b10a3be5d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jun 6 03:10:39 2011 +0000

    cluster/afr: Log errors in afr self-heal with GF_LOG_ERROR
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2986 (Failed operations should should be logged `E' or `W')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2986

commit c997393c8a546e28648d56d2e86651f4bb4b38d8
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jun 6 03:10:38 2011 +0000

    protocol/client: Change log level of error to GF_LOG_ERROR
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2986 (Failed operations should should be logged `E' or `W')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2986

commit 1c034335054090c7dd967ea21a234c1dd8e78c9c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jun 1 00:31:07 2011 +0000

    cli: fix the build warning message
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2944 (warnings in cli_out)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2944

commit 197d850ff62ddcb266e3a9fab30ce753bf123540
Author: Gaurav <gaurav@gluster.com>
Date:   Tue May 31 23:40:27 2011 +0000

    NFS : Handle buffer overflow in nfs3_create_exclusive.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2972 (Buffer overflow in nfs3_create_exclusive.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2972

commit 37b562b1605f900927494ec501dff4190eb26097
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri May 27 04:28:15 2011 +0000

    glusterd: add upgrade/downgrade xlator options
    
    If started with upgrade-option, the current behavior is to recreate
    brick volfiles, as from 3.2 marker xlator is default.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2904 (glusterd should have upgrade/downgrade xlator options)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2904

commit f4c4007263255c49b00eaf62542ec2386ca60302
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 31 01:01:01 2011 +0000

    gluster rebalance: prevent data migration from higher disk space to lower
    
    this is done using the 'statfs()' on inode feature.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit 0d2d861849a3b066eac676ebed4e16accdfe8598
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Apr 14 05:11:33 2011 +0000

    DHT:first_up_subvol should be the one up the longest
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2684 (Dir missing from mount point)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2684

commit dd476eb4678df02ff22f9aa7db7453f857721c42
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon May 30 03:42:50 2011 +0000

    stripe: changes to print stripe information in statedump
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2958 (stripe information is not printed in statedump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2958

commit 8b53f87878d0eae5bab521d3d429ca19ea903d9a
Author: Lakshmipathi <lakshmipathi@gluster.com>
Date:   Mon May 30 04:45:19 2011 +0000

    build : with rpm install invoke glusterd upgrade option to modify vol files and start
    
    Signed-off-by: Lakshmipathi.G <lakshmipathi@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2904 (glusterd should have upgrade/downgrade xlator options)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2904

commit 5f1c41d9088272617fd1afeccd679abdb5f36a3f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed May 25 05:14:25 2011 +0000

    cli: bring in format checking option for 'cli_out()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2944 (warnings in cli_out)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2944

commit d150340907efe888cdabfd4e49552fa8c75f2445
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed May 25 05:14:04 2011 +0000

    cli: fix format string build warnings
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2944 (warnings in cli_out)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2944

commit d720547e9e5960481930f532fe208f7c6db4cd93
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue May 31 06:40:27 2011 +0000

    client_bind: When allow-insecure xlator option is set, donot bind.
    
    There is no need to bind a client, as connect will assign a port.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2868 (Add xlator-option to support insecure-bind for clients)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2868

commit 756c7aea3fef2a77b13ed731ab202c5426db3768
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 31 06:39:41 2011 +0000

    glusterfsd: prevent giving '-s' option without '--volfile-id' option
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2934 (for glusterfs binary, -s option without --volfile-id will fail without any notice to user)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2934

commit 753f17aca63057e4c4a70c1f3cbf7729f890cb69
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri May 27 00:41:55 2011 +0000

    dht-rename: Unlink older link files before creating new one
    
    If a older link file exists, unlink it and then create the linkfile.
    This will prevent mis-match of gfid's.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2464 ([7b07d444a77526f27f860210930bf1d4c7fbea9b]: rm -rf gives Invalid argumenrt error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2464

commit c5a7947e6a7422360816e45fc3c12cf9c0152802
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue May 31 06:08:12 2011 +0000

    pump: init last_event array to be used in afr_notify
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2870 (Inconsistent xattr values when creating bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2870

commit 1b0c33f8960fb1fae03012b479d6cac9ce4d8941
Author: Sachidananda <sac@gluster.com>
Date:   Mon May 23 12:23:11 2011 +0000

    Fix typo in log message related to io-threads.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2926 (Typo in log message)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2926

commit 793aba82fa9585985b4285a92f9bce5b28f5c8db
Author: Gaurav <gaurav@gluster.com>
Date:   Mon May 30 05:00:50 2011 +0000

    RPC : Valid typecasting for ipv4 and ipv6 in rpcsvc_get_listener_port.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2956 (Invalid typecating for ipv4 and ipv6 in rpcsvc_get_listener_port.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2956

commit d7497c4f1b361b1d1c42c157cbcf7ce8bc16fd44
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu May 26 07:45:49 2011 +0000

    statfs(): honor the 'inode' on which the statfs() call is made
    
    fuse-bridge : fill the 'loc' properly with correct 'inode'.
    dht : if directory, send statfs() to all subvol, else send it to only
          cached subvol.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit 411aa2902d304495a4a374a09b767e588b330e88
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed May 25 04:26:00 2011 +0000

    performance/stat-prefetch: return ESTALE if inode's gfid is not the same as cached gfid for a path.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2927 (Mismatched link/target gfid and ESTALE/ENOENT)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2927

commit fcd35ea786dea454b11837f818be959082c8e731
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon May 30 07:55:00 2011 +0000

    features/locks: Unwind with SUCCESS on non-blocking entrylk success
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2949 (self-heal hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2949

commit f1a6ff00a1a4d5bb1124d853c60f68c55d42ad4d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon May 30 07:54:59 2011 +0000

    cluster/afr: Send Non-blocking lock in non-blocking entrylk
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2949 (self-heal hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2949

commit b8957c72e34d9f3174722059618d148b4a4ff38e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri May 27 01:13:39 2011 +0000

    cluster/afr: Send the first child up/down after all its children notify
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2870 (Inconsistent xattr values when creating bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2870

commit 865c74963525bba325c6262a14e37764d1bc0a8a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri May 27 01:13:40 2011 +0000

    cluster/dht: notify should succeed when waiting for all subvols first event
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2870 (Inconsistent xattr values when creating bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2870

commit 493274b4051beca13f7153bc583cb60661a546c0
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:32 2011 +0000

    glusterfsd-mgmt: include signal.h
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit b0c07f4db5f1ed2eeb58709d1021e11ca8fd5600
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:31 2011 +0000

    rpc: NetBSD portability fixes
    
    NetBSD's <dirent.h> does a #defiine d_ino d_fileno. Since glusterfs
    declares structs with d_ino members, we must include <dirent.h> early
    so that d_ino get preprocessed into d_fileno conssitently.
    
    Also define proper xdr types for NetBSD.
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit 7eb3ba062cd0d8ad2d4692c99185af2afde0ee05
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:30 2011 +0000

    fuse: NetBSD portability fixes
    
    Make sure NetBSD pulls proper FUSE header
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit 24d94224ea8c9b67dd7bb9a2ee929f63717d51d7
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:29 2011 +0000

    quick-read: Fix dirname(3) usage
    
    glibc dirname() modify the string it is given and returns it.
    glusterfs takes this behavior for granted, and assume that if it
    gives a malloc'ed string to dirname(), then it can free()) the
    return value.
    
    Here is what SUSv2 says:
    http://opengroup.org/onlinepubs/007908799/xsh/dirname.html
    "The dirname() function may modify the string pointed to by path,
    and may return a pointer to static storage"
    
    At least NetBSD returns a static storage. glusterfs will return it to
    a calling function that has the responsability to free it, causing
    a SIGSEGV.
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit fa19eabd89c0efc52830ad5f6ac63285175acce7
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:28 2011 +0000

    stat-prefetch: fix dirname(3) usage
    
    glibc dirname() modify the string it is given and returns it.
    glusterfs takes this behavior for granted, and assume that if it
    gives a malloc'ed string to dirname(), then it can free()) the
    return value.
    
    Here is what SUSv2 says:
    http://opengroup.org/onlinepubs/007908799/xsh/dirname.html
    "The dirname() function may modify the string pointed to by path,
    and may return a pointer to static storage"
    
    At least NetBSD returns a static storage. glusterfs will return it to
    a calling function that has the responsability to free it, causing
    a SIGSEGV.
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit 80b84f4b852c2794c46af4de1e8ab48673163dc3
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:27 2011 +0000

    fuse: NetBSD portability fixes
    
    - NetBSD uses libperfuse(3).
    - Add @GF_FUSE_LDADD@ to fuse.so library dependecies so that -lperfuse is
      added at configure time for NetBSD.
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit beb2b28ff105bad260c4fda891c174a6bff0abd4
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:26 2011 +0000

    rpc: TCP_KEEPALIVE undeclared in NetBSD
    
    Works around "error: 'TCP_KEEPALIVE' undeclared" on NetBSD
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit 291588c6d912e137ef4d8c19d0447e43c7d87bc4
Author: Anand Avati <avati@gluster.com>
Date:   Mon May 30 04:18:00 2011 +0000

    fuse: NetBSD portability fixes
    
    On NetBSD use libperfuse(3), rename umount2(2) as unmount(2), and skip
    inexistant /etc/mtab management.
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit f2e0b36ea6d31a09f4013b2e6f6ffccc4aca9c0b
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:24 2011 +0000

    errno: NetBSD does not have EDOOFUS
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    [avati@gluster.com: check for EDOOFUS instead of !NetBSD]
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit 7f1c2eb4d473b9323b3a31b33473f7fe06cee449
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:23 2011 +0000

    rpc: use AI_ADDRCONFIG selectively
    
    NetBSD does not have AI_ADDRCONFIG. This patch has a side effect: glusterfsd
    listens on IPv6 adresses only by default. Option transport.socket.bind-address
    in volume server-tcp must be used to listen on an IPv4 address.
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit 9737ef5bbaaf2b4c02ea1710dccbd5464173b2e3
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 16:56:22 2011 +0000

    mount.glusterfs: The == operator is a non-standard bash extension. = should be used instead
    
    Thanks to: Emmanuel Dreyfus <manu@netbsd.org>
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2923 (NetBSD port)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2923

commit dd55755e0ccc94f721e8ada7e50c976c9cb68c4b
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Apr 13 00:27:02 2011 +0000

    rpc-clnt: consider the (re-)configured port for only one connect() call
    
    this way, if remote_port is set due to queryport, that can fall back
    to default port (or 'option remote-port' value) when it disconnects.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2709 (issues with port (re-)configuration in client protocol)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2709

commit dbd9dfdba36bee1a249c0e29edbfe0ded59e8c2d
Author: Junaid <junaid@gluster.com>
Date:   Tue May 17 06:29:22 2011 +0000

    cluster/stripe: Fix a typo in strncmp.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2760 (Quota: stripe volume not showing the quota size properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2760

commit f2d0baecfffe96231b52304ad0560c0697150fff
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun May 15 04:59:53 2011 +0000

    mgmt/glusterd: Display a warning message to CLI in case of a corrupt geo-rep session
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2828 (gluster geo-rep stop should not show unsuccessful when the status is corrupt)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2828

commit e1f79413774939bd23563b1d85b0c64a989301bc
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri May 27 00:29:10 2011 +0000

    pump: Detect 'empty' brick and finish migration.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2909 (replace brick of empty brick never says migration completed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2909

commit fdf3bd3e548c380820219b135e16e9731e31c7c6
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun May 29 08:11:22 2011 +0000

    mgmt/glusterd: Set option listen-backlog to 128
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2941 (glusterd breaks when starting ~100 volumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2941

commit b4fc412a46d8a71cf02d847b0e359b6668e218f2
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun May 29 08:10:48 2011 +0000

    rpc: Introduce option for listen()'s backlog
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2941 (glusterd breaks when starting ~100 volumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2941

commit 4c1c8feee4afd6cabeabc17c85bbc7634adb683f
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu May 26 05:45:07 2011 +0000

    TOP: exit status should be non-zero for success
    
    The fault was incorrect loop. An extra iteration was being performed,
    and dict_get failed due to non-existant data leading to status being
    set to non-zero
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2882 (Make volume top command exit status as zero on success)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2882

commit 7dc5a648caee92ce6d62bbe7b4dc1406662c3858
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu May 26 04:17:15 2011 +0000

    mgmt/glusterd: Start nfs after all bricks are started on glusterd re-start
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2941 (glusterd breaks when starting ~100 volumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2941

commit 235938a9137cf261de20df365f4feae7a33ce5d9
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed May 25 07:30:15 2011 +0000

    performance/io-cache: fix annoying logs during reconfigure
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2945 (disturbing logs in io-cache reconfigure())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2945

commit 4e9c47c4b5ae3209c2853cf034aa00777c76d55e
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 20 15:32:27 2011 +0000

    cluster/dht: detect linkfiles mismatching gfids and delete+recreate
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2522 ([glusterfs-3.1.3qa8]: rm -rf shows invalid argument)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2522

commit 9072b817b0803f999081c6244b18a9ae8fb0234c
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu May 26 03:32:27 2011 +0000

    reimplement invocation of external programs with run API
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2562 (invoke external commands precisely with fork + exec)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2562

commit 302ad26982d1eb7762e743e14dda627ffb317379
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu May 26 03:32:26 2011 +0000

    libglusterfs: add 'run' sub-lib for safe and convenient invocation of external programs
    
    Summary:
    
    - arguments first collected, then the invocation happens with fork + exec
    - flexible specification of arguments (besides si{mp,ng}le argument
      addition, support for adding multiple of them at a time / specifying one with
      printf style formatting) [ ==> goodbye printf percentage soup when composing
      commands ]
    - single point of error check
    - simple command runs are done in just one line
    - support for redirection, popen(3) like functionality
    
    API is documented in details in libglusterfs/src/run.h
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2562 (invoke external commands precisely with fork + exec)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2562

commit 3435813379c276c3c020cb4e3942554be0040ecc
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu May 26 03:32:25 2011 +0000

    libglusterfs: clean up memory types
    
    Unify them in one header, weed out overlap.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2562 (invoke external commands precisely with fork + exec)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2562

commit 6ff690a54ea7d26089be29470e499292971dd30e
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu May 26 03:32:24 2011 +0000

    Revert "temporary workaround for mtab update race thingy"
    
    This reverts commit 59b9ab45a01d52e197ab6f76fd71e64910396d57.
    
    [c5d781e0 made this temporary workaround unnecessary]
    
    Conflicts:
    
    	xlators/features/marker/utils/syncdaemon/resource.py
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2690 (race between mtab updates of mount and umount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2690

commit 19b08a3b627cb8a7f74fc608bfcaddc4e063aa6f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Apr 13 02:24:49 2011 +0000

    replicate: print favorite child as an int instead of unsigned int
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2668 ([glusterfs-3.2.9qa7]: createbench error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2668

commit 2cd8411a0278f98ed820aad3e482de079d0540c0
Author: Venky Shankar <venky@gluster.com>
Date:   Mon Apr 25 03:10:01 2011 +0000

    cli log level command and per translator log level
    
    Signed-off-by: Venky Shankar <venky@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2714 (implement cli log level command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2714

commit 03c58c782d99440a5947289d0ff216bca8ef7c57
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed May 18 23:21:02 2011 +0000

    debug/error-gen: include error-gen-mem-types.h in distribution tarball.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2915 (error-gen-mem-types.h is not included in distribution tarball generated by doing 'make dist')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2915

commit c5d781e05599e9e7ad736d42c9c1033992c76ded
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun May 15 04:52:33 2011 +0000

    upon daemonizing, wait on mtab update to terminate in parent
    
    This fixes the race in between the mtab update attempts of mount and umount
    when we do a lazy umount right after mounting, in order to hide the given fs
    instance; yet this way we still avoid the deadlock of the fs and mount which
    we can hit if we wait unconditionally for the mtab update to terminate (cf.
    bz #511).
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2690 (race between mtab updates of mount and umount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2690

commit 357df32e16dd21e7aedb699c7bd99cac9b95a040
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon May 2 03:47:39 2011 +0000

    Introduce client-allow-insecure xlator-option.
    
    Allows glusterfs clients to bind to any port and does not restrict it
    to 1024.
    
    This is a xlator-option only, and is not supported in volume set cmd.
    The reason is, few clients may choose this, and few may not. Hence
    only supported as a xlator-option during mount time.
    
    For this to work with glusterfs, server.allow-insecure should be set
    to on
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2868 (Add xlator-option to support insecure-bind for clients)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2868

commit afad4e2d64c6bb01ff5dceb29b20ebcc02c1747b
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Apr 20 23:46:05 2011 +0000

    cluster/stripe: make sure gfid is checked with valid data
    
    earlier logic of determining if different subvolumes have different
    gfid for same file had a flaw. It could have checked with a empty
    gfid field in case a reply comes from other subvolumes before first
    subvolume
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2773 ([glusterfs-3.2.0qa12]: stripe lookup says gfid different)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2773

commit ef3d2a48f480d29c2087a5562c73681530f2c727
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Apr 18 00:58:49 2011 +0000

    gnfs-loganalyse: Track fh & entry operations given filename
    
    Introduces support for outputting only those NFS operations
    that operate on a given filename and all the filehandles that
    are seen in the log file for that filename.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 913 (NFS-specific log analyzer tool)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=913

commit 4ba7635f4d3f199dbb082b45cfe7b49f7e243587
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon May 2 05:36:17 2011 +0000

    glusterd: send the duplicate brick info to the cli
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2803 ([glusterfs-3.2.0qa14]: volume create succeeds even though there is a volume with an export directory in the path of current volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2803

commit 276c0cecadbe763e98c5cfd18b3ad32822964789
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon May 2 05:08:39 2011 +0000

    Validate stripe-block-size option
    
    Minimum size is 512 bytes and should be a multiple of 512 bytes.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2861 (Stripe block-size has no check for valid option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2861

commit 0f020affb2cbbcf7c3a25f9f10fe8f14bf012b8e
Author: Sachidananda <sac@gluster.com>
Date:   Mon May 2 03:32:31 2011 +0000

    Move `self-heal completed' message to log level INFO.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2867 (Move self-heal completed message to INFO level)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2867

commit e08383ca1236924e292dc4ce0b8ff2208f4f5170
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun May 8 23:41:23 2011 +0000

    features/marker: whitespace cleanup
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 86c818a98a18a3b6c33a494202922f1cd275ac7b
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed May 11 02:39:14 2011 +0000

    cli: taking my revenge for forcing "geo-replication" into commandline
    
    Accept unambigous initial fragments of keywords, eg.
    
      gluster vol geo stat
    
    is recognized. Compared to readline integration:
    
    - no external dependency
    - works in shell too
    - works for inner keywords of operations
      (as in above example, or "vol crea <vol> repl 3 ...")
    - you save pressing tabs :)
    
    If not desired in customer builds, can be disabled by an #ifdef
    (not integrated into build system as of now); however, I think
    folks in house could like it.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2757 (refactory gsync/gsyncd/syncdaemon/whatever to geo-replication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2757

commit 0652f9f92123e8bb3c0fee02c9fb3bbe23d9f7c6
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 29 12:25:36 2011 +0000

    syncdaemon: fix listing xattrs when there is none and failure handling
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2859 (gsyncd crashes if master vol root has no xattrs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2859

commit 6f2ed82bfcfe494ef273bff55cf69480a7472cc5
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 29 06:24:45 2011 +0000

    syncdaemon: some refactor on monitor
    
    - detect faulty state early
    - keep the feedback fd in gsyncd module
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2537 (gsync autorestart)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2537

commit 9ffd9c51f3833e04a60373648ba3c69c2ed7a68a
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 29 06:24:43 2011 +0000

    marker: fill out the volume-mark properly in case of marking corruption
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2858 (volume-mark corruption swallowed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2858

commit a8addec412a7d6816e06dbbef2e14022edc6ec39
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 29 06:24:42 2011 +0000

    syncdaemon: add --normalize-url option
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2828 (gluster geo-rep stop should not show unsuccessful when the status is corrupt)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2828

commit fa445b44c66eeebc09a3df74d5e924037a3d89c6
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 29 06:24:41 2011 +0000

    glusterd / geo-rep: set session owner to the uuid of the master vol instead of that of glusterd
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 97fdc05ab86ca2af992c42b09ed40413be2ef0d8
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 29 06:24:40 2011 +0000

    glusterd / cli / rpc: move geo-replication reply parameters into dict
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 6dd0282fbfa14eb5a6ae3df1083ef1eea443ea20
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Apr 27 04:46:24 2011 +0000

    posix: glusterfs.test should be removed xattr immediately after use.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2609 (Error message not properly provided when trying to create a volume from a read-only source)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2609

commit a7ca559bdebfcef9a38dfedb8e4757d42431bf94
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Wed Apr 27 04:46:23 2011 +0000

    Detect read-only filesystem and fail the brick creation operation.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2609 (Error message not properly provided when trying to create a volume from a read-only source)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2609

commit 57b53ca592c8d2d01767c7943cb071eb24e6835f
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon May 2 01:38:09 2011 +0000

    set: Fix incorrect nfs.rpc-auth strings in nfs_option_handler
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2866 (volume set for nfs rpc-auth.addr* option succeeds, but vol file not updated)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2866

commit 68a7f34104854101dcc2c54a797f5aced90908e5
Author: Anand Avati <avati@gluster.com>
Date:   Wed May 4 06:02:02 2011 -0700

    configure.ac: set default version to 3git

commit 44fca3bae2092c50bad31427eaf5b2aec9672e09
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Apr 15 01:27:25 2011 +0000

    add 'logrotate' config file to the package
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2053 (We need to support the standard *nix 'logrotate' for server and client log files.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2053

commit 581ee51454d70ace694acfdd6a5b8abb12050dc9
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon May 2 03:47:19 2011 +0000

    gf_auth also needs to handle server.allow-insecure
    
    When server.allow-insecure option is set, the connection from client
    can be from any port. gf_auth also needs to check for this option
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2868 (Add xlator-option to support insecure-bind for clients)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2868

commit e3571d4aab9b727715f0e51d12e6e0596f0111ce
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue May 3 05:04:57 2011 +0000

    glusterd: Checked brick path length in 'staging'.
    
    Added checks for brick path length in 'staging' of add/replace
    brick and create_volume subcommands.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2847 (volume creation fails if brick path is long)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2847

commit f5708f4d0696529faf1fb0ad108123a76c816d78
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Tue May 3 02:05:38 2011 +0000

    glusterd: Cleaned up 'store' if vol create fails.
    
    glusterd's internal 'store' needs to be cleaned up if
    volume creation operation fails.
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2847 (volume creation fails if brick path is long)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2847

commit 53af855f2aad8c19f2bbc7561534b473ae8c7dc4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed May 4 04:14:02 2011 +0000

    cluster/afr: set loc gfids for fresh lookup
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 0336456447f636f6fcf8e53bbfb6295d40434fdf
Author: Gaurav <gaurav@gluster.com>
Date:   Thu Apr 21 03:58:48 2011 +0000

    NFS : Use proper exit point in nfs_init_state.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2695 (Mac host showmount -a not working.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2695

commit 6b02f2ac6a3889af0b0e1cdb4402352379b37539
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Apr 21 03:43:20 2011 +0000

    cluster/distribute: corrected layout mismatch handling logic
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2281 (I/O operations exit when add-brick is done)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2281

commit 27deebbf6c67f5076cae241e98043aa8b8b57ff8
Author: Gaurav <gaurav@gluster.com>
Date:   Wed Apr 27 03:20:11 2011 +0000

    NFS : Maintain common state for MOUNT1 and MOUNT3.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2695 (Mac host showmount -a not working.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2695

commit 7e8da0f5a8bfdd2d1db084fb508b417194754bff
Author: Sachidananda <sac@gluster.com>
Date:   Mon May 2 02:56:40 2011 +0000

    Move the log `self-heal pending' message to INFO level.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2867 (Move self-heal completed message to INFO level)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2867

commit ea5eec6b7e736c1ce149b32e8fcd1180c1c2db9f
Author: Sachidananda <sac@gluster.com>
Date:   Mon May 2 02:47:53 2011 +0000

    Move self-heal completed log message to INFO level.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2867 (Move self-heal completed message to INFO level)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2867

commit cadd9a1b75fb1f78d2fb7c578212ee0225cfeb83
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon May 2 03:11:54 2011 +0000

    loc_t: add 'gfid' and 'pargfid' fields
    
    these fields are used mainly in case of selfheal path, where
    'inode->gfid'||'parent->gfid' is not yet set.
    
    These fields in 'loc' will have lower precedence than 'inode->gfid'
    in client protocol.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit fd7e3b6052881319d4671771aae44933bbf858d4
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Apr 9 01:54:19 2011 +0000

    enable memory accounting for error-gen xlator
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 1f06da6875d8ecff5efa2b6db387ef6084bb68a1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 24 22:45:31 2011 +0000

    performance/write-behind: initialize lock in wb-file before wb-file is set in fd-ctx.
    
    - Consider a combination of fuse->quick-read->read-ahead->wb->client.
        quick-read can do open-behind (open is returned as success even
        before it is issued to backend) and hence the fd can already be
        in the list of open fds of the inode. A flush call on some other
        fd opened on the same inode, will result in ra_flush issuing flush
        calls to all the fds opened on the same inode. This can result in
        wb_flush trying to hold a lock on non-initialized lock there by causing
        memory corruption.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2679 (Crash in GlusterFS 3.0.5 in GSP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2679

commit 77f485dc30e5cd81d63cb7a92dc77b3ace69d40d
Author: Anand Avati <avati@gluster.com>
Date:   Thu Apr 28 01:08:32 2011 +0000

    marker: fix NULL deref in logging
    
    Fix bad gf_log argument
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2852 (Glusterfsd crashes on AMI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2852

commit 28cea0ebbd4ce4cd64e1da4e43512230a0050ee9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 22 11:55:58 2011 +0000

    mgmt/glusterd: Fix ret value in importing of options/gsync slaves
    
    In case the volume options or gsync slaves are absent the import should
    succeed.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2832 (peer probe hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2832

commit 625f779dba824d40626473cd85aaacdefbfae1ce
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 21 17:38:10 2011 +0000

    cli: fix up parsing of geo-replication status
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 775323c1b2fa9a557d3ea74d57e843575f7b1278
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 21 16:43:49 2011 +0000

    syncdaemon: have the monitor kill the worker if it does not connect in 60 sec
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

commit de809504282731332c9bc0fc7f7da5be34f206ce
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 21 16:43:48 2011 +0000

    cli: adhere to timeouts properly
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 5e59de561e49e8f401cf0786635c05c31cc3dfb8
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Apr 21 06:55:46 2011 +0000

    mgmt/glusterd: fix up the buffer sizes to accomodate a correct estimate of sizes of the snprintf invocations, and errout if not feasible
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2561 (gsyncd command's must be preconfigured)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2561

commit 2017d5ed79a0843262695394bfff61968902e9ef
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Apr 21 06:55:45 2011 +0000

    cli: check if gsyncd is present in the configured place, enable geo-replication if present
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2744 (make geo-replication package friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2744

commit 49603aec03e98a2a38fad66627593b69b6269cbf
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Apr 21 06:55:44 2011 +0000

    cli: changes in struct cli_cmd to disable gluster command at run-time
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2744 (make geo-replication package friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2744

commit b5848ed21b9e718011a8f3f3870c4ed978ff17a5
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 21 08:56:09 2011 +0000

    syncdaemon: handle errors in glusterfs mount more carefully
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2826 (stale auxiliary mounts are left over)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2826

commit 92e982b9d2f37ae88b22406be9ee88bf14b57197
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Apr 15 01:10:48 2011 +0000

    gluster volume create: fix help message with transport option 'tcp, rdma'
    
    used to create a volume which listens on both sockets and ibverbs
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2742 (cli help for volume create is not upto date)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2742

commit 81c04158559f9f61ff0581544541cc18778cb1de
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Apr 21 07:08:28 2011 +0000

    prevent few excessive logs
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 2c12b90a84c544343e384e1d60d03b10be9fc45b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Apr 21 05:03:56 2011 +0000

    features/marker-quota: handle creation of regular files using mknod.
    
    - Add the disk-used to parents' size.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2649 (Quota: size field is not getting updated properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2649

commit 14f9c126c1237410bd9ef159e746afd7ff8c2753
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 21 05:22:23 2011 +0000

    glusterd / cli: make the needed changes to let a masterless geo-rep config request get thru
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 58465cdca9386fe2fa15049911223f7282e1b412
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Apr 21 04:16:44 2011 +0000

    features/marker-quota: handle overflow of counter used to set frame->root->lk_owner.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2804 (Occasional log messages seen indicating failure of inodelk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2804

commit 1f074563ecdaf92b2ecf12d7ea79b2b5d8f50c2d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Apr 21 04:10:17 2011 +0000

    features/marker-quota: Add the disk space used to parent sizes during creation of new-files or symlinks.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2649 (Quota: size field is not getting updated properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2649

commit c1b2279adcc3b3a311221f247c6ee563214cf32c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Apr 18 14:23:17 2011 +0000

    do not allow create volume or add-brick if given path or any brick is a part of either
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2803 ([glusterfs-3.2.0qa14]: volume create succeeds even though there is a volume with an export directory in the path of current volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2803

commit 14b9fab371eb7a160fbf15ea4b979d0d98a0e5e0
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Apr 19 08:59:26 2011 +0000

    cli: change geo-replication syntax to support slave-only invocation
    
    (for sake of slave side configurability).
    
    Also pulled out sub-op, now we have
    
      volume geo-replication [<VOLNAME>] [<SLAVE-URL>] {start|stop|config|status} [options...]
    
    -- more convenient to use when working on a given session (ie. we just change the
    geo-rep subcommands), and aligns better with other volume commands, cf. eg.
    
      volume replace-brick <VOLNAME> <BRICK> <NEW-BRICK> {start|pause|abort|status|commit}
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 0dd8c38d17e51c4b8bd1471854315e27c25cc615
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Apr 19 07:19:17 2011 +0000

    geo-replication: revamp CONFIG command
    
    Drop the config_type RPC req field, use just a "subop" key in the param dict.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 29ac0febecbca0700bb4b1e2335b8dace5ff452c
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Apr 19 09:35:45 2011 +0000

    syncdaemon: fix double wait in monitor
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2816 ([glusterfs-3.2.0qa14]: gsyncd monitor crashed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2816

commit 19e4ef605fe95c08c48bcade95096082a54cdd2d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Apr 20 00:59:26 2011 +0000

    glusterd: log the error immedietly after the syscall failure
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 746aa1faa4d2f3a3186e8f660e6a140457580fb3
Author: Gaurav <gaurav@gluster.com>
Date:   Wed Apr 20 05:12:58 2011 +0000

    NFS : Check proper permissions in access control for setattr.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2818 (Permission problems with gluster NFS works with native FUSE)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2818

commit 2d8f4fae7c06c73cd828c247e462a2b1017f5679
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Apr 20 12:47:12 2011 +0000

    features/marker: reduce the size corresponding to destination file if it is already present from parent directories.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2697 (Quota: add-brick creates the size go awkward, though it was perfect earlier)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2697

commit 698d972d8256662dc23a012c4328dca37aaced56
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Apr 19 04:56:58 2011 +0000

    features/marker-quota: initialize dentry_child_count to total number of children a directory has in a single go.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2809 ([e89f2a1f5daf1513c533a47b90aec8f90702d09f]: glusterfsd crashed in quota_dirty_inode_readdir)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2809

commit 450a7be2cede5a44c74f5f74224292af0c81a45f
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Apr 18 21:53:45 2011 +0000

    marker: fixes to bypass marker fops in case features are enabled
    
    mainly in unlink and rename
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2801 (glusterfsd process crash while running rebalance on simple volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2801

commit 3776483431bfcd867a07b83ebd7d303a5d3538b6
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:31 2011 +0000

    glusterd / geo-rep: harvesting further benefits of static gsyncd pre-config
    
    - log-file does not need to be a reserved option anymore as we
      wouldn't overwrite the user setting
    - reimplement glusterd_gsync_get_param_file(): all use cases
      have now pre-configured values, so instead of putting together
      the needed pathname by ourselves, we can just get it from
      gsyncd config
      - refactor it to a common backend with glusterd_get_canon_url()
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit ced2d41bfdf6ee3ee820fa6090e4bf3147ab0d84
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:30 2011 +0000

    glusterd / geo-rep: do all gsyncd pre-configuration in glusterd init
    
    This is made possible by gsyncd config templating, by which
    session specific settings can be expressed in a generic form.
    
    Benefits:
    - in glusterd we use only generic (rx pattern based) config settings
      so we don't violate users' freedom to make settigs for their sessions
    - don't have to invoke gsyncd in excess to prepare a session
    - we can pre-configure slave side too (relying on the templates and
      gsyncd service auto-discovery)
    - much leaner, much more expressive code
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 8d034b840e957d96a3c3e1f86a3ff28aabb8c896
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:29 2011 +0000

    syncdaemon: add session-owner option
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 369f66ea51506315545501ab3fd4fe87d011a0e5
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:28 2011 +0000

    syncdaemon: implement template substitutions for config values
    
    So, for example, a log file setting of
    
      /var/log/${mastervol}/${eSlave}.log
    
    will be substituted with the volume name of the master and the
    canonicalized-escaped name of the slave for each master-slave pair.
    
    As template expanders, beyond the various forms and derivatives
    of master and slave, the following are also available:
     - gsyncd tunables (set in command line or in config)
     - for regexp sections, regexp group captures can be accessed
       via "match<i>_<n>", where i=1,2 corresponds to the i-th peer-rx
       in the section title and n=1,... to the n-th capture.
    
    This will enable us to have a static configuration (not having to
    add new entries on each gsyncd start).
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 5a0d15682fb62d768ce088b5d9c9aad974a1460c
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:27 2011 +0000

    gsyncd service auto-discovery
    
    If glusterd is running, gsyncd will find it out and adopt related settings
    automagically (even if started from not by glusterd)
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 0a38334bd3b21df2448a869760292c499c59bb0c
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:26 2011 +0000

    cli: make it possible to set per-command timeouts for connection
    
    Also make getwd command impatient, having it to time out in 1 sec
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 184fba37889b87c27af90adf357b38fa95f1e78d
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:25 2011 +0000

    cli: implement "system:: getwd" command
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit cc6d5c66090f576383c26bd0bdefadbcad708435
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:25:24 2011 +0000

    cli: preliminary cleanup for system:: commands
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2785 (gsyncd logs on slave side go to /dev/null)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2785

commit 853293b6dd759a20418a4878821db57f933cc50d
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:21:24 2011 +0000

    mgmt/glusterd: geo-rep: restart-upon-reconfig: don't bail out if the gsync session we adjust does not exist
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2777 (geo-replication config setting should have effect on already running sessions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2777

commit d884d4ce74e3d2c582698c9b54b58b4529472a4e
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:21:23 2011 +0000

    syncdaemon: fix swallowing of exit value
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

commit 8ac5926d11cb66c7ef226bb466604414593bab87
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:21:22 2011 +0000

    syncdaemon: pythonize accidentally copied ruby line in code
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2791 (trying to set up geo-replication with a gluster slave on the LAN screws up geo-rep irrecoverably)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2791

commit 7280a000aaea2d6c6294a82f64a626714cbe2702
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 18 17:21:21 2011 +0000

    syncdaemon: don't accept simple identifiers anymore as sugared urls
    
    - we want to enforce the separation of the volume name and the url namespaces
    - resolving simple ids as relative paths was lame anyway
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2786 (Having to prepend geo-replication master vol with colon spoils the UI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2786

commit c6a18b8db0719c0d86c412de6eb386419777d871
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Apr 18 12:29:51 2011 +0000

    mgmt/glusterd: Fix compiler warning
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2797 ([glusterfs-3.2.0qa13]: peer probe fails with gsync running)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2797

commit 7f61b4d1c31181a2c01285a45a99a3ded22349ee
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Apr 18 10:42:03 2011 +0000

    mgmt/glusterd: Send the gsync sessions that are running to the new peer.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2797 ([glusterfs-3.2.0qa13]: peer probe fails with gsync running)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2797

commit 94d32434fdb1d7fc333ab9bf4bf8d3a4eb0dff9e
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Apr 18 08:49:54 2011 +0000

    mgmt/glusterd: do not allow replace-brick operations when geo-rep sessions are active on this volume.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2765 (geo-replication should have mercy on brick failure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2765

commit e89f2a1f5daf1513c533a47b90aec8f90702d09f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 18 08:30:54 2011 +0000

    features/marker-quota: reduce contributions to parents during unlink only if it is the last link.
    
    - since we are not having different contributions for different (parent, name)
        pairs, but only for different parents, links present in the same directory
        will have only one contribution representing all of them. Hence parents will
        not be updated for each link call and parents account for just file-size
        instead of (numlinks * filesize). However this patch will cause issues
        for links present accross directories, as only one of their contributions
        is subtracted when all of them removed (Here all the links are accounted
        in their parents, thereby total size accounted is [numlinks * filesize]).
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2689 (Quota: xattrs getting corrupted)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2689

commit bb4c33f65f3e7eaeb03f3ac249d6eedd123c5ba6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 18 08:30:35 2011 +0000

    features/marker-quota: remove contribution xattrs from oldloc in rename.
    
    - Though we are setting in memory contribution to zero, during updation
        process contribution is actually fetched from backend. If they are not
        deleted and if newpath did not exist before doing rename, contributions
        from oldloc->inode will be retained even for newloc->inode, there by
        preventing addition of file-size to parents in newpath.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2689 (Quota: xattrs getting corrupted)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2689

commit c034f263c0ced77b6b8f806b4533a612631a9c77
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Apr 18 07:34:54 2011 +0000

    mgmt/glusterd: geo-rep config set/del restarts the geo-rep process so that it takes up the new configuration values
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2777 (geo-replication config setting should have effect on already running sessions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2777

commit 4d644dda668e5b55f3f9516e8552e689608b7ad7
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Apr 18 05:03:00 2011 +0000

    cli: Fix profile info alignment
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2794 (Alignment is not proper in profile volume info)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2794

commit 2f9ce3f4fd23d1a9256e84830805a62f1ebe76fb
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Apr 18 02:09:00 2011 +0000

    mgmt/glusterd: change the cli output of geo-rep start/stop to resemble the output of volume start/stop
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 67705d888c4e038f188da8a21ade8db447cd7009
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Apr 7 04:45:40 2011 +0000

    DHT: Propogate error if dht_rmdir_opendir_cbk
    
    Earlier rmdir would succeed on all up subvols, but fuse would get an
    error if one of the subvol was down. In follow up lookup, self heal
    would be triggered, and since st_mode would be 0, the permissions
    would be bad. The behaviour now is to fail rmdir if subvol is down
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2591 (Directories changing to d--------- permission after trying to delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2591

commit 72b57e311fe8634d26b4c56a78016f9359208443
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Apr 17 11:21:51 2011 +0000

    cli: UI cleanup for geo-replication command
    
       * provide a unified output in case of failure of geo-replication session
       * provide a better formatting  of the output geo-replication status command
       * update the help option of geo-replication command
       * fix few typos
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2536 (gsync service introspection)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2536

commit 91b3d10880678cfa9c5ce03204eb62897a4564e8
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Apr 17 10:46:08 2011 +0000

    cli: removal of dead code due to the code movement of geo-rep start from cli to glusterd.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2676 ([glusterfs-3.2.0qa7]: glusterfs server crashed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2676

commit 3a621ae053a31db49f7adc506bd5ffbd24a0c64d
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Apr 17 10:46:07 2011 +0000

    mgmt/glusterd : change of syntax of geo-replication command
    
    master is referred as a volume name rather than a URL scheme.
    
    old syntax:
    
       > volume geo-replication start :vol-foo /bar/boo
    
    new syntax:
    
       > volume geo-replication start vol-foo /bar/boo
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2786 (Having to prepend geo-replication master vol with colon spoils the UI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2786

commit 4b813b3d14476a5cf6a3a54c32c2939a31fe9ba9
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Apr 17 10:46:06 2011 +0000

    mgmt/glusterd: unify the geo-replication status rpc messages.
    
    the intelligence of determining the type of status command is now at glusterd,
    rather then explicitly setting it while parsing at cli.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2536 (gsync service introspection)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2536

commit 666e43aca607c90d95379caa13b42a4ed976e8a7
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Apr 17 04:45:59 2011 +0000

    syncdaemon: minor cleanups on termination
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

commit 856a7ee345713b66ccb6eba6fca276273807fe30
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Apr 16 16:04:27 2011 +0000

    glusterd/volgen: make it possible for builders to set the op_errstr during graph validation
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2559 (provide two options in CLI for gluster volume gsync indexing <volname> <enable|disable>)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2559

commit 4ade518a232418ccccc6a7bc3c381022465b6c84
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Apr 16 13:36:04 2011 +0000

    glusterd: some cleanups needed for 70adbe7b [refactor gsync_status() ...]
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2780 (geo-replication operations take too much time to complete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2780

commit c9d85b6268523f1872dde05f271e16afd0358939
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Apr 16 04:13:35 2011 +0000

    cli: check for connectivity before doing mount
    
    in quota limit list.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2732 (Quota: the local mount on server fails while using quota list command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2732

commit 87e4d4814458c57a3337e7c610f6ead76d0cb28f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Apr 16 09:31:24 2011 +0000

    marker/quota: use correct byte ordering when updating parent's size.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2649 (Quota: size field is not getting updated properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2649

commit 26dc794e6586ca911678fc80e831e18cd99973fa
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Apr 16 09:45:49 2011 +0000

    marker: avoid memleak by unrefing dict, fd and local
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2784 ([glusterfs-3.2.0qa13]: memleak in marker)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2784

commit 3e873600920a180960e6730a531ba7a5912f5543
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Apr 16 10:03:53 2011 +0000

    features/marker-quota: fixes in self-healing of dirty inode code path.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2649 (Quota: size field is not getting updated properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2649

commit e52a0cc23b16bf653ce544caaffa0e7ffb5fab4e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Apr 16 10:07:29 2011 +0000

    extras/quota-xattr-cleanup: don't follow symbolic links.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2664 (Quota: recreating the volume on same bricks shows similar info as for earlier one using "list")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2664

commit 70adbe7b71771b48e5bd8d79e38132afa04e4752
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Apr 16 10:32:54 2011 +0000

    glusterd: refactor gsync_status() so that we can get at the pidfile
    
    This is useful for iterated polling of gsyncd's status, without having to
    incoke gsyncd to find out about the pidfile.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2780 (geo-replication operations take too much time to complete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2780

commit c78dafac7f82de8a7b72f42fcd58c01dbc4a88df
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Apr 16 10:32:53 2011 +0000

    syncdaemon: load xattrs from libc on-demand
    
    This reduces startup time for invocations other than master / slave role
    (kind of which now proliferates glusterd)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2780 (geo-replication operations take too much time to complete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2780

commit 679c3986b9b72d19d6057d400ec8f1fba1569853
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Apr 16 06:05:31 2011 +0000

    quota: do not assign frame->local to NULL which leads to memleak
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2772 ([glusterfs-3.2.0qa12]: excessive quota local NULL errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2772

commit d5110f12ac0352991f22cbf4f80d855a8f35ba42
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Apr 16 05:23:58 2011 +0000

    quota: assign local to frame local to prevent memleak
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2772 ([glusterfs-3.2.0qa12]: excessive quota local NULL errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2772

commit a70c0034cc5c7e38390167ebfa9c8706be16fd6d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Apr 16 00:48:46 2011 +0000

    mgmt/glusterd: Fix percentage latency formula
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2783 (Fix percentage latency and precisions of profile info)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2783

commit 426eed2dd4992f3fb6048dff49b0e2db38d2a87b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 15 22:58:12 2011 +0000

    mgmt/glusterd: Send the error msg to user if gsync start fails
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2781 (geo-replication start error message)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2781

commit 1f5ad47e48cf4901b027a674179025c078c00953
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Apr 15 22:05:21 2011 +0000

    features/quota: set 'frame->local' to local in fsync
    
    so fsync call can succeed
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2772 ([glusterfs-3.2.0qa12]: excessive quota local NULL errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2772

commit f727e847133e479a37e86a7feb5826496a7313f7
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 15 09:10:03 2011 +0000

    syncdaemon: yet another try to exit properly
    
    The final cleanup sequence + call to _exit, which was just done in the main
    thread, now is called for in each thread when the thread crashes. Seems we
    aren't left there hanging this way.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

commit 43d95c00ee49cb4852d199f11e2647a5930b07c8
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 15 09:10:02 2011 +0000

    syncdaemon: when getting a single config option, don't display the option name, just the value
    
    This intends to ease scripting (you can just pass on the value to xargs etc.)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 5c9c2555911d8d7131e3c0d918f6ee9c0b3b612f
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Fri Apr 15 09:15:23 2011 +0000

    mgmt/glusterd: does not allow disabling of indexing (xtime marking), if a gsync session is active.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2559 (provide two options in CLI for gluster volume gsync indexing <volname> <enable|disable>)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2559

commit 2479f442ca8f9e2dd23988e1f2dc20238443a769
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 15 07:00:42 2011 +0000

    mgmt/glusterd: handle error condition in quota fs crawl
    
    Quota enable starts a crawl on the maintenance mount point, but if the chdir to
    the mount point fails it will start the crawl on '/'. So the child should exit
    with EXIT_FAILURE when the chdir fails.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2770 (Handle error cases in quota fs crawl)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2770

commit 49b796949c9a3cc9d5a541503e03589fb7bcbde2
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Apr 15 07:56:47 2011 +0000

    TOP: validate bs/count pair for write/read-perf measurement
    
    If either one the above args are supplied, the other arg should be
    supplied too.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2771 (bs or count tag missing with volume top write-perf/read-perf command blocks glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2771

commit baaa7286ed6b70121efa6a83a8adb3a2f1ec45da
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Apr 15 07:05:38 2011 +0000

    cluster/stripe: aggregate xattrs holding quota-size in lookup and getxattr calls.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2760 (Quota: stripe volume not showing the quota size properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2760

commit 2ca0f2d3ab4c80ed4d002bcb2ca1425d1db42c78
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Apr 15 07:05:24 2011 +0000

    features/quota: use disk usage instead of file-sizes.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2760 (Quota: stripe volume not showing the quota size properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2760

commit cdcbfcd3900ad450023c8b3d06174dfb81644788
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Apr 15 07:05:10 2011 +0000

    features/marker-quota: Use the actual disk-space consumed instead of ia_size returned in iatt for calculation of sizes.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2760 (Quota: stripe volume not showing the quota size properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2760

commit da66edbe927152ba12c9a702fd157a45a3f3cb42
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Apr 15 14:02:39 2011 +0000

    mgmt/glusterd: fix double free.
    
    - the limit-usage string should be stored as static, since remove-limits will
        be modifying it and probably freeing it.
      - this static string should also be explicitly freed in glusterd_quota_disable
        since dict_del won't free it.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2776 (gluster quota remove crashed glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2776

commit cfe11cd627f8322ad2701dad6c021d3570bbbf1d
Author: Krishnan Parthasarathi <kp@gluster.com>
Date:   Fri Apr 15 01:00:56 2011 +0000

    top: Modified integer bounds check for count/bs
    
    Signed-off-by: Krishnan Parthasarathi <kp@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2721 (Incorrect validation message in gluster top CLI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2721

commit 7a56f1b9a18e4863917e4b6aaeacba2e28073ab6
Author: Lakshmipathi <lakshmipathi@gluster.com>
Date:   Fri Apr 15 05:08:47 2011 +0000

    rpm : create new package for geo-replication and preserve symlinks
    
    Signed-off-by: Lakshmipathi.G <lakshmipathi@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2744 (make geo-replication package friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2744

commit b5d944f911f1638a8063235443410de36df6f2fd
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 15 02:55:46 2011 +0000

    mgmt/glusterd: Memory leak and message cleanup
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2764 (Cleanup memory leaks seen in quota and gsync code paths)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2764

commit b565cf8bfc75e6f6c85a47bc8a06737cd6e79fae
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Apr 15 02:49:51 2011 +0000

    DHT: Make assert-no-child-down a boolean option
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2765 (geo-replication should have mercy on brick failure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2765

commit dc75b9889d0dca8cde08860e96be1c88059644c6
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 15 02:26:24 2011 +0000

    syncdaemon: name tempdirs used by gsyncd more characteristically to ease debugging
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 78ca8b9fb8790f5741d5bf01aa870d7b77b9c57f
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 15 01:48:36 2011 +0000

    glusterd / geo-replication: have gsync's glusterfs client use assert-no-child-down for dht volume
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2765 (geo-replication should have mercy on brick failure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2765

commit 8699c929fb9e07303a6a779e8d4713c4a837b33d
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 15 01:09:01 2011 +0000

    glusterd / geo-replication: set location of ssh keyfile for gsyncd
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2756 (support for providing custom ssh private key)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2756

commit 0c77e6f156e57717f9cd3feb35d589e36dcb831f
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 14 16:35:02 2011 +0000

    glusterd/volgen: partially revert 50ab0ad4
    
    Moving the adjustment of marker's timestamp file to generation
    phase was not correct, as generation should be side effect free.
    Moved it back to the point where volfiles are written.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2529 (Starting Gsync  causes ENOTCONN to glusterfs client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2529

commit 0dfe24fc9fc8bf92044fa59e27f61169dfdcd5bc
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Apr 15 00:58:00 2011 +0000

    use "geo-replication" all over as the official name of this feature
    
    Use GEOREP macro if you want to refer to the feature in code.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2757 (refactory gsync/gsyncd/syncdaemon/whatever to geo-replication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2757

commit e1be6195464836dd910e3b62f518c897dd06740d
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 14 16:35:00 2011 +0000

    glusterd/volgen: refactor some things
    
    - use macros for exported volume tunables
    - introduce glusterd_volinfo_get_boolean as retrieval of boolean
      optuions was a recurring pattern and became somewhat cumbersome
    
    Also fixed illegal access to volinfo dict.
    @pranith: use always the glusterd_volinfo_get* API for that purpose
    so that defaults are taken to consideration.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2757 (refactory gsync/gsyncd/syncdaemon/whatever to geo-replication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2757

commit 066074291fad64a78923bbca06d25b5a6a5307d7
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 14 16:34:59 2011 +0000

    syncdaemon: split gluster_command to make it possible to set options for glusterfs
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit f689a077d3f0a8c75d7ef083d92ef0faeb2ba5a0
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Apr 14 16:34:58 2011 +0000

    syncdaemon: work around python feature of allowing double leading slashes in canonicalized paths
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 4175e092e3521c1f095d6307ea9b05c7c49b02c6
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 14 11:53:12 2011 +0000

    mgmt/glusterd: restart gsyncd on glusterd restart
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2761 (Restart gsyncd processes on glusterd restart)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2761

commit 4055c85a23043afdf3ad708d28aedc55805b1043
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Apr 14 07:04:20 2011 +0000

    features/marker: fix the excessive logs in marker
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2754 ([glusterfs-3.2.0qa11]: excessive logging in marker)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2754

commit 9b0374043ebe59fa638b8af330ea1d403503c143
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Apr 13 00:29:16 2011 +0000

    cli: add log file for cli instead of '/dev/null'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2737 (there is no log file for gluster cli)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2737

commit 4d6e05f0aac70fbdec6b9530ed7b5d6ce4de0f03
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 14 04:31:22 2011 +0000

    mgmt/glusterd: Prevent dict unserialize for buf with 0 length
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2753 (perf-test failed with "buf is null!" message)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2753

commit d6cbfe3b4be0af43a14df76e2305488158cff3e1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Apr 14 05:10:34 2011 +0000

    quota: resume the stub when its not NULL
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2758 ([glusterfs-3.2.0qa11]: symlink hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2758

commit 1d1452e070f990cc91fea87408ea4905abde2fb7
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Apr 14 04:21:48 2011 +0000

    DHT: Add xlator-option assert_no_child_down
    
    If this is set, when CHILD_DOWN event is received, call exit
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2536 (gsync service introspection)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2536

commit 6c16974a0ed485c72f84922fcf67b76ac8f64358
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 14 03:45:20 2011 +0000

    cluster/afr: Avoid null dereference
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2750 ([glusterfs-3.2.0qa11]: nfs server crashed in afr_sh_entry_expunge_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2750

commit 1c5706c43d17beb2dd8eb78c5b740bafd5b05506
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Apr 13 10:23:03 2011 +0000

    marker: pass cookie properly while filtering quota xattrs.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 8c833f1ecab9af3762f4e332126399e61fae090c
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Apr 13 23:30:22 2011 +0000

    mgmt/glusterd: fail the volume stop opeeration if Gsync sessions are active.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2751 (Volme stop must not be proceeded if gsync sessions are active for the volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2751

commit 93cb168fb362c7aea3c10371574a5c5566bb0222
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Apr 13 22:14:37 2011 +0000

    mgmt/glusterd: Implementation of volume gsync status [master [slave]]
    
    Changes made in the path of gsync start/stop as well, where we
    maintain a list of  active gsync sessions, hence gsync stop could be
    executed at all nodes.
    A new dict in glusterd_volinfo_t added to maintain an active list
    of gsync slaves running on each master.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2536 (gsync service introspection)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2536

commit 77cd50a12887b13db4c49be6a979a5ecb8239570
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Apr 13 10:37:31 2011 +0000

    quota/(f)truncate: pass correct delta for updating parent sizes after successful completion.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2741 (Quota: new files not getting created even if space is available)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2741

commit 55594008c2d719c7097998b3d8aa9771bcc9d3ff
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Apr 13 01:13:56 2011 +0000

    mgmt/glusterd: check for 'peerinfo->mgmt' before accessing it
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2728 ([glusterfs-3.2.0qa11]: glusterd crashed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2728

commit 1875dd6c05a5964b46ce38f1bd3c0679ad5d17bf
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Apr 14 00:05:39 2011 +0000

    glusterd: Respond to cli with empty iobref is serialize fails.
    
    This usually happens if the size exceeds 128k. Earlier the cli used
    to hang if the response exceeded 128k size.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2725 (volume top displays "error" for path max)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2725

commit b3c2bbab35695a2358a4031aa05e31eb5e19c28b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 14 01:08:22 2011 +0000

    mgmt/glusterd: Handle the features/quota for quota
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2540 (quota enablement yields bogus client volfile)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2540

commit efd0f26ba8116da1148c75c950f2490dbe42ebc5
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Apr 13 05:13:19 2011 +0000

    glusterd: report the user if disable quota is given on already disabled quota
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2620 (CLI improvements in quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2620

commit 9c46226f7a98e843b1c95ecdcf44830e05d5e1f5
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 13 07:36:14 2011 +0000

    PUMP: initialize loc at declaration
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2726 ([glusterfs-3.2.0qa11]: glusterfs server crashed due to stack overflow)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2726

commit 41df71222e0d3975b8160d82a630d70ac15786be
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Apr 13 07:36:13 2011 +0000

    mgmt/glusterd: server graph should have io-threads below pump
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2726 ([glusterfs-3.2.0qa11]: glusterfs server crashed due to stack overflow)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2726

commit 6608d60aa6ba733fbdc612e27499524b28adadbf
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:10 2011 +0000

    cli: simplfy gsysnc configuration command
    
    New syntax is
    
     volume gsync config <master> <slave> [[!]opt [val]]
    
    In details:
    
    - instead of "volume gsyncd configure M S config-get-all" :
                 "volume gsyncd config M S"
    - instead of "volume gsyncd configure M S config-get O" :
                 "volume gsyncd config M S O"
    - instead of "volume gsyncd configure M S config-del O" :
                 "volume gsyncd config M S !O"
    - instead of "volume gsyncd configure M S config-set O V" :
                 "volume gsyncd config M S O V"
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2738 ("volume gsync configure <master> <slave> config-<subop> ..." is overly verbose)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2738

commit ebd99e25bf811ab14540f74dd50b445c217e7ee0
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Apr 13 01:46:09 2011 +0000

    cli: join value arguments of "gsync config-set" with spaces
    
    When a given gsync tunable is supposed to hold a command (which
    can take options), it's quite possible that it spaces in its value.
    Try to approximate this situation by joining the leftover arguments.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2713 ([glusterfs-3.2.0qa10]: config-set works only for one value)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2713

commit 72f88e50dbf1f492db7bcc70b074bc64e6b994cb
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:08 2011 +0000

    glusterd: sanitize gsyncd config option validation
    
    - rely on --config-check functionality of gsyncd to find out if option exists
    - maintain a list of those options with which we don't want the user to fiddle with
      (glusterd internals imply these so it' just the proper component for it)
    - fail if user does a set/del on these
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2659 (gsync config-del option is not working properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2659

commit ac27e6980869d52ea90b869de01538dec28620ae
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:07 2011 +0000

    syncdaemon: ensure -/_ invariance in tunables, in all components
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2659 (gsync config-del option is not working properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2659

commit b1cad2780c34f9dd664f67565ceac3b5a5cf3bcb
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:06 2011 +0000

    syncdaemon: refactor gsyncd.py cmdline interface to configuration
    
    - existence of given tunable is checked
    - add --config-check option to just do a check for existence of tunable
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2659 (gsync config-del option is not working properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2659

commit e5c38128fa76b3e11047d49448aab77d3a551804
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:05 2011 +0000

    syncdaemon: force termination for unhandled exception in any thread
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2736 (gsyncd hangs if crash occurs in the non-main thread)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2736

commit 13d1856a40122008dee35a96771f832945c220f8
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:04 2011 +0000

    syncdaemon: streamline user-visible messages (and control flow a bit, too)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2644 (no volume-mark, if the behaviour persists have to check if master gsyncd is running.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2644

commit ea2e55bae0203b00dc4872a3333dce84cf7bef7d
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:03 2011 +0000

    syncdaemon: fix parsing of the volume-mark structure
    
    The parsing error implied that all xtimes were considered to be valid,
    regardless of the volume mark.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2535 (gsync cascading)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2535

commit 9a81400a4accc68bfe55a0bee69ca7e2ed5894f3
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:02 2011 +0000

    syncdaemon: return exit code properly
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 64161529ebe151e36c7fc86b419543b4ac02a681
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:01 2011 +0000

    syncdaemon: fix pidfile deletion on failed pidfile acquisition
    
    (not triggered in glusterd instrumentation of gsyncd as glusterd does pidfile
    probing by itself)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit c0139158ae8992513e93932d8670b5db8605ead2
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 13 01:46:00 2011 +0000

    syncdaemon: minor fixes
    
    - whitespace fix
    - remove superfluous imports
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 7cf0dbcd300f554985ebde4759511c048927c53a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 12 01:21:57 2011 +0000

    mgmt/glusterd: Remove excessive INFO logs
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 4e928f1d9a9cbbf18d3df3481f1d985f12a9c5ba
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 12 22:40:14 2011 +0000

    mgmt/glusterd: log stats commands to cmd log
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2735 (log stats commands (top/profile) to cmd log)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2735

commit bc16a1e999648ba58f863d26281c152fb477174a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 12 07:17:44 2011 +0000

    mgmt/glusterd: volume reset force implementation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2729 (Implement force option for volume reset)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2729

commit fb3e469e29578393a0d5f964991d26b5449bffb0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Apr 12 09:00:02 2011 +0000

    features/quota: update quota-limit stored in directory contexts after reconfigure.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2604 (Quota: crossing the set limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2604

commit bdb3e709e3eec1863181339bf1a5b66b702ac1bb
Author: Junaid <junaid@gluster.com>
Date:   Tue Apr 12 10:01:28 2011 +0000

    features/marker: Filter the quota xattr's on getxattr with NULL name argument.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 4b6a08fba53d895c84676d8c3ae6a5ef45fa2286
Author: Junaid <junaid@gluster.com>
Date:   Tue Apr 12 12:03:06 2011 +0000

    features/marker: Call update txn when the directory size and its contribution are not same.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit ba365f725a91bcd3dcfae1d8311f9f148ce69055
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Apr 12 10:30:24 2011 +0000

    remove excessive logs due to log enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit d7cba3b0bb4867e02a5999f830e5315cd7022520
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 12 04:00:35 2011 +0000

    script: fix the typo while doing replace brick
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1436 (script for running basic gluster commands)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit b71aa0cdb7113dfa7e94720da48cc46c476cde4a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Apr 4 14:50:11 2011 +0000

    declare favorite child as int instead of unsigned int
    
    In afr_private_t structure favorite child is declared as unsigned int.
    In init function of afr we set favorite child to -1, if that option is
    not found in volfile. But favorite child value will be set to a huge
    value instead of -1 since it is an unsigned int and in statedump file
    favorite child value is displayed as a huge value instead of -1.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2668 ([glusterfs-3.2.9qa7]: createbench error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2668

commit 2e4eeb06adc1e6a8a7ded02752ade780ac977200
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Apr 12 14:22:15 2011 +0000

    libglusterfs: Check for null dereference in statedump
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2731 (coredump when process state dump command is issued immediately after mounting fuse client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2731

commit 10ad4b52e03dbdc3674f49a5d9322f220ea65088
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 12 10:03:52 2011 +0000

    cli: Fix typo in top help string
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2719 (Incorrect help string for volume top)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2719

commit 5ca2445270b4b77f2399a9f6332083ff933234a1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Apr 12 09:20:53 2011 +0000

    features/quota: check for proper return value in case failure of dict_get_bin
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2723 ([glusterfs-3.2.0qa11]: glusterfs client crashed in quota_validate_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2723

commit 470bef24d742165a6499128f0b7a8748bdc8be96
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Apr 12 09:17:55 2011 +0000

    features/quota: add error checks for failure of quota_inode_loc_fill.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2727 ([glusterfs-3.2.0qa11]: nfs server crashed in quota_check_limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2727

commit cc734698b6edcbf54b244a23ff757ae6f2f669b5
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 12 09:07:57 2011 +0000

    quota: assign frame->local to local before checking op_ret
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2733 ([glusterfs-3.2.0qa11]: nfs server crashed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2733

commit 35998844040cf713f229e896524a1a6be249e31d
Author: Junaid <junaid@gluster.com>
Date:   Tue Apr 12 08:19:27 2011 +0000

    features/quota: Validate the quota options. and donot include into the client volfile.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2541 (insufficient option validation in quota translator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2541

commit 1fd570380ba5def514ff42e81008a7ddd588348f
Author: Junaid <junaid@gluster.com>
Date:   Tue Apr 12 05:06:03 2011 +0000

    features/marker: Adding NULL checks.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 9c26fbc70ab797eea7967bc77857e73eca9aeffe
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Apr 12 05:02:00 2011 +0000

    protocol/client: convert to errno before checking for EAGAIN
    
    in *lk_cbk() functions. Network error code may be different than
    what is actual errno code.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 6a2c2fa4f13f9ed96098c4fec40f747e171e6819
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Apr 12 05:00:18 2011 +0000

    protocol/client: fix the fd_count decrement logic
    
    the error creeped in during some code cleanup and logging enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1761 (incorrect self-heal behaviour when files are deleted)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1761

commit 59b9ab45a01d52e197ab6f76fd71e64910396d57
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Apr 12 02:47:45 2011 +0000

    temporary workaround for mtab update race thingy
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2690 (race between mtab updates of mount and umount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2690

commit 1b18a7d64574ca08b937113fcb19b9d851abd43c
Author: Junaid <junaid@gluster.com>
Date:   Tue Apr 12 08:11:32 2011 +0000

    libglusterfs/dict: Donot perform NULL check on data in dict_foreach
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1816 (send volume options in friend add)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1816

commit 214ceccb0758e62724dc2548d140aff5885391a0
Author: Junaid <junaid@gluster.com>
Date:   Tue Apr 12 04:37:16 2011 +0000

    mgmt/glusterd: Mount a maintainance client only on the glusterd which received quota enable through cli.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 2a6598646824da9d6a957fb5b3e4c6bb40fb6835
Author: Venky Shankar <venky@gluster.com>
Date:   Mon Apr 11 05:48:36 2011 +0000

    build fixes
    
    Signed-off-by: Venky Shankar <venky@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2550 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2550

commit cfd85789c44ce3f88d6bf87d7b0a47dafb8c6d57
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Apr 12 00:26:25 2011 +0000

    mgmt/glusterd: Fix warning in glusterd build
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2718 (Fix warning in glusterd build)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2718

commit 9ccb1e7b152ea9d27356482d51bd1946d377b799
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Apr 11 03:19:25 2011 +0000

    libglusterfs/src: bring in VALIDATE_OR_GOTO to args
    
    so we can capture places which are calling these function with
    invalid arguments
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 902478bf9e2e1fee15ef979020d28d2095211e93
Author: Junaid <junaid@gluster.com>
Date:   Mon Apr 11 11:32:39 2011 +0000

    mgmt/glusterd: Quota client lazy umount.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2560 (Lazy umount should be done for the maintainance mode mountpoint)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2560

commit dff1a8bd5bcd392826561c93058f8a52606a2832
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Apr 11 08:38:40 2011 +0000

    mgmt/Glusterd: Do not disable marker on gsync stop.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2559 (provide two options in CLI for gluster volume gsync indexing <volname> <enable|disable>)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2559

commit f0ef00478f1f2722d349606924d0d3479eb5da80
Author: Junaid <junaid@gluster.com>
Date:   Mon Apr 11 07:13:40 2011 +0000

    features/quota: Adding the option "timeout" to quota.
    
    This option tells the quota translator when to perform the next aggregation.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 3a709be6850e50915c9e188cc308d7bfa5f781e5
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 11 05:42:20 2011 +0000

    syncdaemon: do not use os.getlogin() for getting the name of the current user
    
    This function relies on the terminal (cf. getlogin(3)), which is not available if we run as daemon
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2712 (username resolution in gsyncd fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2712

commit 78bd9a86c3e87c9e79f62990773767f81cab896d
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Apr 11 02:25:18 2011 +0000

    mgmt/Glusterd: logging of few commands in cmd_log_history
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2449 ([glusterfs-3.2.0-cisco1]: gsync commands are not logged in the cmd_log_history)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2449

commit 882085db173a031a4cc24b5dec7e369f1b512747
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Apr 11 05:00:31 2011 +0000

    marker: check the return value being less than zero instead of -1
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2711 ([glusterfs-3.2.0qa10]: glusterfs server crashed in marker_setxattr operations)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2711

commit 204db674a9c6a724f5fe887c02cd98386043f4fe
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 11 01:13:58 2011 +0000

    features/quota: handle failed fops gracefully.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2701 ([6db2b422f05d0553d0a83af603ae4d176b41cbdf]: crash in quota_readlink_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2701

commit f5625e628f1959331eed85082cb6bfdc324db3c2
Author: Junaid <junaid@gluster.com>
Date:   Mon Apr 11 01:15:53 2011 +0000

    cli: Validating the cli quota options.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2612 (quota limit-set not in line with help)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2612

commit 974be663a9113d4aed684dce00f5288669d511e8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 10 22:38:03 2011 +0000

    features/quota: Add checks for any of the parents of file being NULL while checking limits.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2685 (nfs server crashed in quota_check_limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2685

commit 1992dc12443f376f9b2974f4e830b4b17e3574c0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 10 10:53:36 2011 +0000

    features/quota: use signed type to store delta.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2604 (Quota: crossing the set limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2604

commit 67d77aa96dccefe68a44473bf45cf6796e741b7d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Apr 8 14:46:54 2011 +0000

    buf and statpost should be checked for NULL before accessing it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2701 ([6db2b422f05d0553d0a83af603ae4d176b41cbdf]: crash in quota_readlink_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2701

commit 86a091ac0d46ce2b06b79ceafe728ee65fc6ebbf
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 11 04:09:17 2011 +0000

    syncdaemon: fix transaction code
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2659 (gsync config-del option is not working properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2659

commit 2f38fdac226b5b5bd02a78e9933ec46b05cac32d
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 11 04:09:16 2011 +0000

    syncdaemon: minor fixes
    
    - fix yet another instance of calling exit (instead of {sys.,os._}exit)
     - fix logging to stderr with "-" as logfile
     - whitespace fix
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit dd3cc7d398c3b4432097b7cc2716e2afec9a8e47
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Apr 11 04:09:15 2011 +0000

    syncdaemon: fix setting None as new master
    
    We checked for the event of a new master being adopted by:
    - checking for state change in list of masters
    - checking if our chosen master is a foreign one
    and if these held, then wrote out the actually available master to config
    
    However this was flaky: if
    (1) native master changed
    (2) there was already a foreign master adopted
    (3) actually the master was not available
    then we wrote out the None to config.
    
    This could occur if:
    - on syncd startup, native master just changes from None to the volume native
      [implies (1)]
    - foreign master adopted from earlier run via config [implies (2)]
    - actually foreign master was not available [implies (3)]
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2670 (strange behaviour with intermediate-master and slave)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2670

commit b003ee6e9e8316a59a1de204f727748e442ef0af
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Apr 10 05:30:45 2011 +0000

    protocol/server: prevent unnessary logs in INFO level
    
    'op_ret == 0' in readdir() is a valid return code.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit a6ec94de9346f2973d013237cc6584ff9aa89974
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 10 05:06:04 2011 +0000

    cluster/distribute: Account for the first lookup sent to check whether the path is a directory while aggregating quota-xattrs.
    
      - The total number of lookups sent for a directory is equal to
        (no of children + 1). Hence we should not aggregate the xattrs
        from the first lookup.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2604 (Quota: crossing the set limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2604

commit 0a05984fd99577a1ea5bf8d2cdddd08d9a88ba75
Author: Junaid <junaid@gluster.com>
Date:   Sat Apr 9 05:34:23 2011 +0000

    cli: Cleanup the maintainence mount points used by quota.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2704 (Stale mount-points seen after execting quota list command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2704

commit 11c2526e045a5a9b168175d5fd658302a8dcb31b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 10 05:11:29 2011 +0000

    marker/quota: use correct byte order while storing xattr values in backend.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2604 (Quota: crossing the set limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2604

commit ef19a8ba4c0628566c01ebd247869797a7ba5dde
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 10 10:55:08 2011 +0000

    features/quota: Fix race-condition while resuming stub.
    
    - call-stub is resumed in fops calling quota_check_limit and quota_check_limit
        when validate_count is zero, indicating no pending validates. During
        validates, validate_count was decremented in quota_validate_cbk, but check
        for validate_count being zero was done in quota_check_limit (which is
        called by quota_validate_cbk). Hence there is a time window b/w decrementing
        validate_count in quota_validate_cbk and checking whether
        validate_count is zero in quota_check_limit, during which if the
        control is passed to code in fop checking for validate_count being zero,
        same stub will be resumed twice - once in fop and once in quota_check_limit.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2686 ([glusterfs-3.2.0qa8]: nfs server crashed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2686

commit 3ea5bff8dfebbf325daccf81511c5d4534b2ca86
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Apr 7 17:06:25 2011 +0000

    DHT: send revalidate to all subvols and not just first subvol
    
    Reverting commit 23d9783a192669b638d42b8dd127ad69ea36f950.
    When first subvolume is down, mount point becomes inaccessible.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand Avati <avati@gluster.com>
    
    BUG: 2532 ([glusterfs-3.1.3qa8]: bringing first subvolume down makes mount point inaccessible)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2532

commit ee96f768b99362ec724c8918d24028def065536a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Apr 10 10:43:05 2011 +0000

    libglusterfs/xlator: set THIS properly whenever some operation is done iteratively on more than one xlator in the graph.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand Vishweshwaran Avati <avati@shell.gluster.com>
    
    BUG: 2683 ([glusterfs-3.2.0qa8]: glusterfs client crashed in reconfigure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2683

commit 6db2b422f05d0553d0a83af603ae4d176b41cbdf
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 8 02:50:03 2011 +0000

    mgmt/glusterd: Fix op_ctx issue with replace brick
    
    Replace brick recognizes command originator by the presence of op_ctx.
    Brick op uses the op_ctx to collect the brick response on all the
    machines in cluster. This patch satisfies both these assumptions to
    make glusterd functional in replace-brick.
    This is a hack for 3.2.0. Need to Fix the assumptions in later release.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2691 ([glusterfs-3.2.0qa9]: glusterd error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2691

commit 64cefcee88c6164f20668187929c76ec54a72d23
Author: Gaurav <gaurav@gluster.com>
Date:   Fri Apr 8 00:54:33 2011 +0000

    NFS : Exclusive create storing verifier.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2553 (NFS file create with Mac client and UNCHECKED mode returns "Operation not permitted")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2553

commit d6a7e92da11663cdb6068466f22e230ceb0dc31d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Apr 7 23:57:58 2011 +0000

    features/quota: Add checks for any of the parents of file being NULL while checking limits.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2685 (nfs server crashed in quota_check_limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2685

commit 25837b52939398bf3964d20301f0e641033c5c68
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Apr 7 00:22:23 2011 +0000

    gluster rebalance: don't move a hardlinked file.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit 0d440ddb80c55320fe9deda15cecec8e31cab2c1
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Apr 6 05:46:44 2011 +0000

    gluster rebalance: don't depend on the sticky bit for validating link file.
    
    do the getxattr() with 'trusted.distribute.linkinfo' key, which
    returns success only if the file has a link. With this we can preserve
    the exact same permission as old file.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2530 (Rebalance not working properly (file permission issues))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2530

commit 12de69e4204c0dced7cccc8450954ad2e20c1075
Author: Junaid <junaid@gluster.com>
Date:   Fri Apr 8 01:12:40 2011 +0000

    features/marker: Synchronise the read and write of marker_local_ref.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2663 (glusterfsd crash with bonnie++ when marker is enabled)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2663

commit ca381e5aeadb4e2fdced09c3e86b12498ce84c11
Author: Junaid <junaid@gluster.com>
Date:   Thu Apr 7 15:38:25 2011 +0000

    mgmt/glusterd: Quota cli message improvements.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2620 (CLI improvements in quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2620

commit 54558cfc3653d5b5201ec7fd45594cb610eefbca
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 7 21:11:15 2011 +0000

    mgmt/glusterd: serialize the dict only if its not NULL
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2691 ([glusterfs-3.2.0qa9]: glusterd error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2691

commit 56814fefa0a4cff5d08528aa9103e01350d0e53a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Apr 7 09:41:47 2011 +0000

    do not access the empty loc inode
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2611 ([glusterfs-3.1.0-qa5]: crash in quota_rename)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2611

commit 62e1096fb01f7a12c5bc5ff77e3cb427248b80ad
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Apr 7 07:44:51 2011 +0000

    removed reference to GF_LOG_NORMAL
    
    instead used GF_LOG_INFO, which is more standard log level.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2669 (RuntimeError: cannot recognize log level "normal")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2669

commit 19b2e01f1c53c358c5673c3d216c0349b55481a6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Apr 7 07:10:42 2011 +0000

    do not change the arguments of a function
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2685 (nfs server crashed in quota_check_limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2685

commit 4bf80aa399f70aa976796154728d518362708792
Author: Junaid <junaid@gluster.com>
Date:   Thu Apr 7 06:53:27 2011 +0000

    features/marker: Perform quota updation on rmdir and unlink by holding inodelk on parent.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2664 (Quota: recreating the volume on same bricks shows similar info as for earlier one using "list")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2664

commit a99c9b5ffd92ac05d173ff2bad698a0f7947b327
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 7 06:40:47 2011 +0000

    debug/io-stats: Fix races and performance issues in profile
    
    Fix the race in update_latency and memset of interval stats.
    Update fop hits and latencies only when both the options are set.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2636 ("profile info" lists 'nan' in latency when heavy i/o is running)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2636

commit db347c756609e5fb6792bfd69046c97fd6aacc0e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Apr 7 06:40:46 2011 +0000

    mgmt/glusterd: Fix gluster-profile performance issues
    
    Add count-fop-hits option to io-stats
    use count-fop-hits instead of dump-fd-stats for profile
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2636 ("profile info" lists 'nan' in latency when heavy i/o is running)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2636

commit 476b672347641c3f0d6b346b13feaf530ecbbe93
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Apr 7 02:51:50 2011 +0000

    extras: scripts to cleanup xattrs stored by quota.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2664 (Quota: recreating the volume on same bricks shows similar info as for earlier one using "list")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2664

commit 7a32aa912ea4e49d3ef922ec6e0cb3d394109962
Author: Junaid <junaid@gluster.com>
Date:   Mon Apr 4 12:03:04 2011 +0000

    features/marker: Check for NULL before dereferencing pointers stored in local.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2607 (Fileop fails when quota is enabled)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2607

commit ee494c7519e5da09b66003de514db5e700c3001d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sun Apr 3 12:01:41 2011 +0000

    print the gfid of the inode for which dentry is not found
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2652 ([glusterfs-3.2.0qa6]: dbench keeps on running)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2652

commit af4604ad4cf58f4b9b3fab26121c3ebd105428ca
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Apr 6 12:41:12 2011 +0000

    mgmt/glusterd: Reset context upon operation completion
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2650 (replace brick failed in distributed-replicated setup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2650

commit 50a0adf03e1401395b04c7bba3d5007658cae9e4
Author: Junaid <junaid@gluster.com>
Date:   Wed Apr 6 23:57:24 2011 +0000

    features/marker: Check if gsync is enabled in getxattr fop before performing gsync related operations.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2681 (marker returns dummy data for volume-mark attribute if xtime is switched off)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2681

commit 35dea20e40958ebbf018354e040570e654eb6bfc
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 5 14:24:59 2011 +0000

    check buf for NULL before accessing it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2675 ([glusterfs-3.2.0qa7]: glusterfs client crashed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2675

commit 06c954a910fe8749b362490c62e5b49be5b0c385
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Mar 31 06:05:41 2011 +0000

    check dict before unrefing it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2642 ([glusterfs-3.2.0qa5]: invalid reads in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2642

commit 8e8d4e0869623f352c7993293c6e132d795a34bf
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Apr 6 05:37:05 2011 +0000

    nfs: convert errno EDQUOT into appropriate nfs-errno.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2607 (Fileop fails when quota is enabled)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2607

commit 9bff4a73fedd388bb9c57a3e999361540ac333eb
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Apr 6 00:59:04 2011 +0000

    protocol/client: Avoid logging when EAGAIN is received for *lk requests
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 1887 (logging mess)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1887

commit 7bfaed649bf8a479afd051ea3c5adc7a4717b2fa
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Apr 5 10:22:57 2011 +0000

    change occurrences of marker_gsync to marker-gsync
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 282109ed02a1ad220027bc69398941ba2b115cd2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Apr 5 09:02:53 2011 +0000

    features/marker, cli: use appropriate conversion specifiers.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2649 (Quota: size field is not getting updated properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2649

commit 322ed6812d9a5b3c975b5c949ff5adfd16d40eb4
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Apr 5 04:00:26 2011 +0000

    protocol/client: make sure to send only genuine events up to parent
    
    that way parent notify logic is fine.
    
    also, remove 'xlator_notify()' call in code, instead use 'default_notify()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2584 (Inode number changes on a directory when one of subvolumes is down in replicate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2584

commit b8ae8d95a814d9329c34e6bf3d705c0fc07115b7
Author: Gaurav <gaurav@gluster.com>
Date:   Thu Mar 31 05:42:47 2011 +0000

    NFS : Store verifier for exlusive mode craete.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2553 (NFS file create with Mac client and UNCHECKED mode returns "Operation not permitted")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2553

commit e4c5ad45612e845eb476b29d51ec12b963660855
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 30 00:03:59 2011 +0000

    cluster/dht: send back the proper inode number in the cbk functions
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2584 (Inode number changes on a directory when one of subvolumes is down in replicate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2584

commit 8a4e51fcc1d8fd69038c513712729bf9dba5c4e2
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 30 00:03:43 2011 +0000

    cluster/dht: log level fixes in lookup* functions
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 99af7219c54b2264ede898fa619125c629519174
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 30 00:03:20 2011 +0000

    log gfid mismatches for the same file in cluster xlator lookup
    
    This can help in pin pointing some of the issues resulted in gfid
    mismatch for the same file, which is harder to find through basic
    debugging/logging of current codebase.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    
    BUG: 2346 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit a1a0e929534cb56e3a938229c7f87bfd0f1c17ec
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Mar 24 07:28:00 2011 +0000

    cluster/afr: log enhancements - part 1
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@shell.gluster.com>
    
    BUG: 2346 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit ba044581fa8781886fbd4f4675f388c79f599b2c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Apr 1 03:00:04 2011 +0000

    features/quota: use a double pointer to uint64_t as an argument to dict_get_bin while getting size.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2604 (Quota: crossing the set limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2604

commit ff9e63c0975e786a69e5ecede78b178f20baceb7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Apr 1 02:56:18 2011 +0000

    features/quota: add NULL check before doing strcasecmp
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2646 (glusterfs-client crashes during getxattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2646

commit f338193a707ae5b6b5ab6f820bea32612c4311bb
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Apr 3 15:44:17 2011 +0000

    syncdaemon: refine intermal configuration of gsyncd
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2561 (gsyncd command's must be preconfigured)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2561

commit 01b3dff29adee2041b0ef1b374eda8c88fb07678
Author: Csaba Henk <csaba@lowlife.hu>
Date:   Sat Apr 2 19:40:49 2011 +0000

    syncdaemon: add monitor mode to support autorestart
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2537 (gsync autorestart)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2537

commit e77c35248e8ce796bc5b108c10013089a0c65bde
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Apr 2 19:40:48 2011 +0000

    syncdaemon: provide transactional semantics to config file writing
    
    So updating the config file from multiple contexts won't mess it up.
    This prepares the next commit where we'll set options internaly (which lacks
    the serial nature of user actions).
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2537 (gsync autorestart)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2537

commit cfb9c834f96dc57c47dac8d27da4266d0dab1f3f
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Apr 2 19:40:47 2011 +0000

    syncdaemon: give some refactoring to cascading code
    
    - expiry check of foreign volinfo moved back to GLUSTERServer,
      so that under the hood we can removexattr the expired ones;
      a nice side-effect is that we can use the same dict layout
      for foreign and native volinfo (ie., foreign needs no
      timeout field)
    - get_volinfo() is renamed to get_sys_volinfo() and most of the logic
      is stripped off of it (what remained there is the check
      against foreign master ambiguity)
    - volinfo transition logic is cut out to an almost purely functional
      static method (only impurity is the exeption raised upon
      forbidden volinfo change)
    - ping renamed to keep-alive, as something called "ping" is
      not supposed to have payload (yeah, keep-alive is a bit fishy
      on this front too, but could not come up with better...)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2535 (gsync cascading)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2535

commit f007eb1a0701cd3e13e6ba67208cd1db9325a370
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 31 11:59:52 2011 +0000

    syncdaemon; adding corresponding pcloses to gsyncd invocation via popen
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit 913da6c337cfe342d60f3773057a14d645248421
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 31 05:58:58 2011 +0000

    syncdaemon: fix up fallback xtime value for slave
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2535 (gsync cascading)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2535

commit c0e6146f53d3e91764e9ff602ccba9a637b2db7d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Apr 1 03:44:02 2011 +0000

    debug/io-stats: Fix bugs in re-configure options
    
    If the options are not present in vol file reset the option values.
    If there is an invalid option log an error and continue,
    no need to exit
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2638 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2638

commit cd4fd271c6636ecc100171403b324a65a9e77fe2
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Apr 1 03:24:12 2011 +0000

    Replace strdup call to gf_strdup as GF_FREE is being called
    
    Also, fix validation of bs and count to <= 0.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2645 (volume top write-perf results in memory corruption)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2645

commit 5c709704ab5767b55f4eef7cddea52e18e2a6d42
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 29 07:07:05 2011 +0000

    cluster/afr: log enhancement - part 3
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit d983f04c961304dc57d14c305751b0d1113c3a5d
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 29 07:06:45 2011 +0000

    cluster/afr: log enhancement - part 2
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit fa6ba86900abc9b023adf4ce642aba5eb0a35500
Author: Anand Avati <avati@gluster.com>
Date:   Mon Mar 28 09:30:38 2011 +0000

    nfs: capture attrs of create request in cs->stbuf for later use
    
    when attrs coming in as part of create request contain modes other
    than mode, they were getting discarded previously and a setattr
    was getting performed on a 0-filled iatt structure. This would
    result in EPERM at the access control translator as non-root users
    cannot chown a file to uid 0.
    
    Not seen with Linux NFS client as it (very likely) relies upon
    auth-unix to set the ownership of the file or sends an explicit
    setattr after the create.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2553 (NFS file create with Mac client and UNCHECKED mode returns "Operation not permitted")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2553

commit 9c09f44f716df2c45e25b6a9a6465592fde19ea3
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 31 11:59:51 2011 +0000

    syncdaemon: fix gsyncd invocation for config-set
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2555 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2555

commit 0f67ad828895960ab96f9e237eae8acbc6c63988
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 31 08:13:31 2011 +0000

    syncdaemon: minor cleanups in cascading code
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2535 (gsync cascading)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2535

commit 05daec675f1716554864e34e0a3c9c71423b6594
Author: Vijay Bellur <vijay@dev.gluster.com>
Date:   Thu Mar 31 22:11:00 2011 -0700

    Revert "Process dir/link from other subvol if error in dht_readdir"
    
    This reverts commit cd3d977b10e24c4b46e55f9831113aba3a241583.

commit 498dbbc506ec9c694e18c3ae9a0d3d346abe338d
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Mar 31 04:57:22 2011 +0000

    TOP: Improve output format
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2614 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2614

commit c68b1e28ae9b7528aa844764e719c7267976be83
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Mar 31 04:57:05 2011 +0000

    TOP: Validate command options
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2628 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2628

commit 58974b02b6ebb65ee1f7baf23b0fe6c3e7fcf8cd
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Mar 31 04:56:10 2011 +0000

    TOP: handle list-cnt behaviour uniformly.
    
    Valid range is 0-100. if list-cnt is 0 or there are no files in the list,
    handle it uniformly.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2622 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2622

commit 3b5195cfa4976e1d83646b70b0f08f583a7a1094
Author: Junaid <junaid@gluster.com>
Date:   Thu Mar 31 04:28:43 2011 +0000

    features/quota: Use appropriate inodes while logging and create contexts in inode for files.
    
    - It also fixes limit checks if limit set in the directory.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2604 (Quota: crossing the set limit)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2604

commit 1c148f85c5abf561faeb68c699a13c8bd683de5e
Author: Junaid <junaid@gluster.com>
Date:   Thu Mar 31 04:28:26 2011 +0000

    features/marker: Fix memory corruption.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2629 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2629

commit 99779326d09f7ac98bb75bb1432d53c7c320a5c9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 31 04:27:22 2011 +0000

    mgmt/glusterd: Delete volume profile options on profile stop
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2638 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2638

commit a728fc84b67f8ba37cf63a8e3ef67cf8b0bb1f32
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 31 03:31:01 2011 +0000

    mgmt/glusterd: Improve profile output messages
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2616 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2616

commit 43700ed04c1bac15f5df3702410c83fb63607476
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Mar 31 03:31:00 2011 +0000

    cli: Improve profile output messages
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2616 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2616

commit 215a8352e2219c7ead29693ccab3452054a89041
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 31 03:29:35 2011 +0000

    syncdaemon: fix "--debug" option of gsyncd.py
    
    also be explicit about logging to a stream (ie. don't rely on the feature of accessing
    stdin through /dev/stdin)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2637 (gsyncd --debug broken)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2637

commit e0f03d7430f6b79e9ed0fa68234753e33368e3e6
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Mar 30 23:47:59 2011 +0000

    mgmt/glusterd: Fix space in error message
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2623 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2623

commit 5f6e7aecdb4dba8b181e90be99eb21ad40129315
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Mar 30 23:43:41 2011 +0000

    mgmt/glusterd: Mark the brick stopped when kill -SIGTERM is done
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2621 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2621

commit 0cccbefebfd2e95dbbf7f078f5e45267c60d48ed
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 29 07:06:26 2011 +0000

    cluster/afr: white-space cleanup - part 2
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit f7fb326c250997f274e4e928faec9aeca4ce12c9
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Mar 15 01:57:15 2011 +0000

    nfs-rpc: Append replies to end of connection's txlist
    
    ..instead of prepending.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2491 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2491

commit c294df619656798b107933a42a0f5613c1df0830
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Mar 15 01:57:14 2011 +0000

    core: Add list_append_init
    
    To append to end of list, as compared to list_splice_init which prepends.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2491 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2491

commit a54e0358b1d66c04448b22c1a01e076b5a527008
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Mar 15 01:57:13 2011 +0000

    nfs-rpc: Exit txbuf transmission loop on EAGAIN
    
    ..instead of looping till the buffer is completely transmitted.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2491 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2491

commit 325ee7aeab629a7435922d9e61d04fd3418ec6d7
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Wed Mar 30 07:54:41 2011 +0000

    return after stack winding instead of destroying the frame
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2624 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2624

commit ca67876f15347faccba9fdd3f3f2997c58ef3fa6
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Mar 30 06:03:06 2011 +0000

    mgmt/Glusterd: prevent memory overflow
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2632 (possible memory overflow in one of the code paths in volume gsync stop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2632

commit f8c798350a5efa537418d1453f3e547574e68b55
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Mar 30 06:03:05 2011 +0000

    mgmt/Glusterd: add pid extension to the pid file of the gsyncd
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2538 (pidfile naming)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2538

commit d1c0e5b0dc64bb431c384b7584ea362143d8ef46
Author: Anand Avati <avati@gluster.com>
Date:   Wed Mar 30 01:18:46 2011 +0000

    nfs: more fixes to capture sattr for further usage
    
    in
    
    - mkdir
    - mknod
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2553 (NFS file create with Mac client and UNCHECKED mode returns "Operation not permitted")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2553

commit d1700d209431e19a2ecca43f644935533d705af1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 29 14:08:04 2011 +0000

    assign local to frame->local before checking for error conditions
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2617 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2617

commit 3ce486929518da2673b6cef5ef1047849f587729
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 29 13:37:26 2011 +0000

    access the proper loc structure when inode ctx get fails in quota
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2611 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2611

commit b40d510cf534b6fa1acb827ed7c26bcdebc5fd36
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Mar 30 00:28:29 2011 +0000

    io-stats list: init counter to 0 for counting members
    
    By setting init the counter cnt to -1, we were loosing 1 entry when
    displaying the list on the cli.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2606 (gluster volume top open lists only 99 entries)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2606

commit d088ffe14da46247052e34c5cfaced46f5079b24
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Mar 29 14:15:32 2011 +0000

    debug/io-stats: fix memory corruption.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2619 (Memory corruption in io-stats)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2619

commit 4597929cc527f8abaf9ef9e1d5499ea416e5c7ff
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Mar 29 09:10:07 2011 +0000

    Gsyncd: Cascading of gsync daemons
    
    This patch allows the slave of a gsyncd to be started as the master of another slave gsyncd.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2535 (gsync cascading)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2535

commit 4c246c02f4ab569fca92255b7efb819243711d6b
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Mon Mar 28 07:21:51 2011 +0000

    mgmt/glusterd: Fix double free on quota limit-usage.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2595 (Quota: re-setting the space-limit crashes the glusterd on the same node)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2595

commit b6ffe3ed1d44fddaed2a5eb2586b0584bfc17d5a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Mar 28 04:32:32 2011 +0000

    mgmt/glusterd: Add rpc-auth-allow-insecure option
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2582 (allow option to accept messages from insecure ports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

commit 94a2118801138db92dda0cf74691fea95d7f9d12
Author: Gaurav <gaurav@gluster.com>
Date:   Mon Mar 28 04:30:28 2011 +0000

    NFS : Volume access option accepts only valid values.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2598 (Volume access option suceeds with any string value)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2598

commit 61b669c8366bc43e62324bbd0ce381cdbe633b93
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Mon Mar 28 04:04:55 2011 +0000

    features/marker: check for op_ret before doing any operations in lookup callback
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2497 (client crashes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2497

commit b65f54c9aa1e3405b731769e56460592ba69ed60
Author: Pavan T C <tcp@gluster.com>
Date:   Mon Mar 28 03:50:29 2011 +0000

    Loosen restrictions on hostnames
    
    Signed-off-by: Pavan T C <tcp@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2249 (Problems with hostname validation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2249

commit b691214fd9114e2b4c7d419ef06aedd28614127a
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Mar 24 07:27:26 2011 +0000

    cluster/afr: whitespace cleanup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 408a2b029824a3915ce094aed520061e80c078c8
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sun Mar 27 14:03:10 2011 +0000

    check the local for NULL before accessing it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2592 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2592

commit 2406e21dd2d63b4ab69d8179d69dae17f0e4a0d9
Author: Pranith K <pranithk@gluster.com>
Date:   Sun Mar 27 08:51:29 2011 +0000

    mgmt/glusterd: Add the new volume only after all ops succeed
    
    - Print errors to the user when any of the op fails in create volume
    - Add the volume to the list only after all the ops succeed
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1888 (volfile generation error ignored)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1888

commit 48b0c02ba2b9c828b29ce236c838ab0e56ddab08
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 25 21:43:44 2011 +0000

    protocol/server: change allow_insecure option in reconfigure
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2582 (allow option to accept messages from insecure ports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

commit 8b32b9ab363639888938c631882c8cfd6b00a3f5
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 25 21:43:31 2011 +0000

    mgmt/glusterd: Provide volume option to allow insecure ports for server
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2582 (allow option to accept messages from insecure ports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

commit f6e0e614fbd07a57de44f0d16c304d01d1a5b269
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 25 21:43:17 2011 +0000

    mgmt/glusterd: Allow insecure ports by default
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2582 (allow option to accept messages from insecure ports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

commit 8a15f00cd8ad19fa414d2ef63dc71147ae191d73
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 25 21:43:03 2011 +0000

    rpc: Don't warn on failure to bind to privileged port
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2582 (allow option to accept messages from insecure ports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

commit 3f37921807fc84af6d9529ae18aa8575e2458fc5
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 25 21:42:49 2011 +0000

    rpc: Provide an option to allow insecure ports
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2582 (allow option to accept messages from insecure ports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

commit a9a6d95ecb86f45b197bc36d8e6a504d65367c3a
Author: Junaid <junaid@gluster.com>
Date:   Fri Mar 25 01:49:07 2011 +0000

    cluster/dht: Fix double freeing in quota aggregate.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 0952bbb30564e8a2359039841290f9956c96e1b9
Author: Junaid <junaid@gluster.com>
Date:   Fri Mar 25 01:48:52 2011 +0000

    features/quota: Return dynamically allocated address of local.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit c55d855c74d860ff0dae942f95c290eba45f15f8
Author: Junaid <junaid@gluster.com>
Date:   Fri Mar 25 01:44:20 2011 +0000

    mgmt/glusterd: Fix double memory free.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 3f6be7a12972684500d4357a170a3de4f452a63b
Author: Junaid <junaid@gluster.com>
Date:   Fri Mar 25 01:39:12 2011 +0000

    features/marker: Handle fop's gracefully when none of the feaures are enabled.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2529 (Starting Gsync  causes ENOTCONN to glusterfs client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2529

commit 2339b9e87e8e48df9b64ba016949a2f40b50324e
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Mar 23 21:44:13 2011 +0000

    mgmt/glusterd: Avoid printing no-error message to user when op fails
    
    - Prints the peer hostname/uuid where the error happened in case the
    peer does not return an error string.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2585 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2585

commit 1180b2136f6cf014a08f072f8ecc4aac2b69580f
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 25 05:58:35 2011 +0000

    mgmt/glusterd: Fix import friend volumes
    
    - Sync transport type of the volume
    - Stop stale bricks
    - start new bricks if the volume is started
    - Restart/Stop nfs server based on the new information
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2549 (Quota[glusterfs-3.2.1qa3]: enable/disable crashes the glusterd on other node)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2549

commit fc06afc8cd1a646f71e0ed1713b05b8aa533c6d2
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Mar 23 05:25:26 2011 +0000

    mgmt/glusterd: fail create volume on create-volfiles failure
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1888 (volfile generation error ignored)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1888

commit e488f48ebc3d545b9924b828e59f08a5d42571ba
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Mar 23 00:52:22 2011 +0000

    Gsyncd: fix a typo for the command-line arg of gluster process
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 89b45f610dfc455dd6c8fd84c1d3c9945ad62f4c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 22 05:01:56 2011 +0000

    send proper device id to posix while self healing device file entry
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2567 (self heal on device files changes the major and minor number)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2567

commit cd3d977b10e24c4b46e55f9831113aba3a241583
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Mar 22 04:43:56 2011 +0000

    Process dir/link from other subvol if error in dht_readdir
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2137 (dhtafr - self heal after renaming directory)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2137

commit 0ed446b7c8c8bcda74a5d64cdb8f0ac2d11b2389
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Mar 22 04:43:20 2011 +0000

    Implement stripe readdirp fops
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2159

commit c1f1345e6fc2a008ef03632cd64211bf20c244bb
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Mar 21 02:00:19 2011 +0000

    nfs3: Flush file I/O call states on open failure
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2566 (NFS read hangs when arequal-checksum script is run)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2566

commit f2a9ce7abacc8749589d0b931ca155d2c7578774
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Mar 17 19:08:49 2011 +0000

    nfs: Remove redundant and erroneous check for create mode EXCLUSIVE.
    
    nfs3.c/nfs3_create_common:
    
    The if condition checks for create mode being EXCLUSIVE. However, when
    create mode is EXCLUSIVE, this function never gets called (nfs3_create_exclusive is
    called). Also, instead of checking, it actually sets the value of createmode (= instead of ==).
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2553 (NFS file create with Mac client and UNCHECKED mode returns "Operation not permitted")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2553

commit bd132d8e410dbc24cbef751925cd937939f35747
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Mar 23 03:53:28 2011 +0000

    Prevent deadlock in io-stats list management of top.
    
    Senario: thread t1 has lock on the queue, and waits on the element lock to remove
    it and unref it. Thread t2 has a lock on the element being removed from the queue,
    but waiting on the queue on the list to update it.
    
    The fix is to move list management to outside of the lock. Additonal to this change
    is adding locks to ios_stat_ref
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2578 (Mountpoint hung while running the dbench)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2578

commit 9bd4f25b6b0ea8103324b685fcc21525a29849a8
Author: Gaurav <gaurav@gluster.com>
Date:   Wed Mar 23 00:50:17 2011 +0000

    CLI : Validate options farmework.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2064 (NFS options are removed upon glusterd restart)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2064

commit 6f6c817314a2a867be996c2ad6d9a1337617ded4
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 22 07:08:24 2011 +0000

    do not check loc and fd since they can be passed as NULL only
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit e4957b1ae771fa7a1e56cfd25f55deaa527dff4c
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Mar 22 06:30:44 2011 +0000

    TOP: remove trailing '/' from brick path
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2573 (trailing '/' with brick name says "volume top unsuccessful" while running 'top' command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2573

commit 384f81cf412c0da9d13a547c0aeb2cd33e59774d
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Mar 22 05:20:01 2011 +0000

    Moved stats cleanup to forget from unlink and rmdir
    
    Additionally, replace inode_ctx_get with inode_ctx_del in cleanup
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2575 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2575

commit 95f59725adbefd574cfd694dc101ee9c803f167a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 22 04:50:07 2011 +0000

    free priv structure if something fails in init for locks
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit a4233a41bf6a2f9ddbce15a530b1678c55ba24a5
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 11 05:02:15 2011 +0000

    cluster/afr: skip openfd flush when the file is already deleted
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2497 (client crashes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2497

commit e115072f4b654d407fcf435256334645ab471776
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Mar 22 04:36:39 2011 +0000

    features/marker: Donot fail init when both gsync and quota are not enabled.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2529 (Starting Gsync  causes ENOTCONN to glusterfs client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2529

commit 9c7bc4f5da67a630fe543bd8bdf5d1aaf2acef99
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Mar 17 19:01:02 2011 +0000

    libglusterfs/compat.h: Fix build warning in dirent_size().
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2550 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2550

commit c077bd932beff169a366c99c94ff45e432d1d793
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 22 03:01:03 2011 +0000

    remove the names from the log files
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2573 (trailing '/' with brick name says "volume top unsuccessful" while running 'top' command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2573

commit b230793b8b345ff25168567209cae10294b53f23
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Mar 21 07:26:30 2011 +0000

    cli: Fix memory leak in gluster profile
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2571 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2571

commit 6167c66758de454284560474f3b4a893d8a69965
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Mar 18 00:41:08 2011 +0000

    spelling errors fixed across the code base
    
    recieve -> receive
    maintainence -> maintenance
    verison -> version
    commited -> committed
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2262 (Spelling errors in source)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2262

commit c0d8f11be283637622b0ece82ba8392f0a67e87c
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Mar 17 08:00:49 2011 +0000

    man pages updated
    
    Thanks to Divya MN <divya@gluster.com> for all the effort
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2444 (keep man pages upto date with new codebase.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2444

commit 50ab0ad4ffb5ea844c6fe1f708df65b769c88db1
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Mon Mar 21 07:16:17 2011 +0000

    mgmt/glusterd: Glusterfsd not restarted on changes to marker option.
    
    Bricks are not restarted when some marker options are changed and the Marker
    translator is included statically in the server volfile.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2529 (Starting Gsync  causes ENOTCONN to glusterfs client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2529

commit 1ef501b5c526a2dec6592cb8693996a81e5834c4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 21 01:54:42 2011 +0000

    cluster/distribute: aggregate quota-sizes in lookup and getxattr.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 7852c982ffd85ee38b42894f3c966d1634d550be
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 21 01:54:26 2011 +0000

    features/quota: Client side quota.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit d0e3c762318673a6081ab96abc525a568f82170b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 21 01:53:58 2011 +0000

    features/quota: removed quota.c and quota-mem-types.h files.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 941442ced02900128c6893caa6159bac2f1d9683
Author: Pranith K <pranithk@gluster.com>
Date:   Sun Mar 20 03:25:50 2011 +0000

    mgmt/glusterd: Dont reset the port on brick stop
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2564 (replace brick fails on master)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2564

commit 24d326a5180adaedf8d49a2d087afa0ec470a537
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Mar 18 05:37:24 2011 +0000

    Change NFS_PATH_MAX value to 4096
    
    This is tmp fix for crash seen on solaris gnfs server is received path is
    longer than PATH_MAX. On solaris default PATH_MAX is 1024, and linux default
    PATH_MAX is 4096.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2476 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2476

commit dece0547259a5d73fd6c2616802f83388b5ff4da
Author: Gaurav <gaurav@gluster.com>
Date:   Fri Mar 18 03:52:08 2011 +0000

    CLI : Fix memory free for key_fixed.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2554 (Invalid memory access in glusterd.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2554

commit bb5b31fb96dbc2092e2967924462c59863845749
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Mar 18 00:56:14 2011 +0000

    fuse: set 'graph->used' after graph change
    
    Because in the current way, we have chances of changing the graph
    to old one too. with this, we can control this.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2503 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2503

commit 26dcbc729395b00dae45cd62222aaccbd2ab7aff
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Mar 18 00:38:36 2011 +0000

    debug/io-stats: don't log the dangling volume message
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 131d82cacd4600654d3e931287d2556f50bd9db5
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Mar 18 00:38:13 2011 +0000

    libglusterfs: added graph id in logging
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 3d912aa905105098db1eea1e4c3e9c42aa0c7da7
Author: Rahul <rahul@gluster.com>
Date:   Thu Mar 17 01:55:43 2011 +0000

    Added checks for fix-layout & migrate-data usage.
    
    Signed-off-by: Rahul <rahul@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2547 (rebalance command usage and help mis-match)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2547

commit 6d8077eb9c7129f4bdb352132e565906568dfb66
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 17 11:44:25 2011 +0000

    Revert "syncdaemon: make /usr/libexec/gsyncd the default remote gsyncd (incomplete hacky quickfix)"
    
    This reverts commit 8c801cfd05eb533ae64ea9f06e49e632955cf0c0.
    
    The commit in question was just a temporary fix (which violated
    component boundaries).
    
    Since 9043b0f8 we don't rely on this fix.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit 223bfc4d19a2b7cccc62e05129e09591233edc44
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 17 00:46:38 2011 +0000

    syncdaemon: fix up exit value
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2380 (TypeError: 'str' object is not callable)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2380

commit 236600d7de4e900ad3905908853785dc2ac6629f
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 17 00:46:37 2011 +0000

    syncdaemon: don't try to set log level to None
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 0a1f00cdcb087e00c184c62c1a9f22803c257cf2
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:38:49 2011 +0000

    libglusterfs/src/*.c: log enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 0f39192ef6bc7b1c74cfaeb04ed21305996d67e9
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:43:33 2011 +0000

    protocol/client: log enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 0349ec857004428f29b50f3604e5ab126dfb407e
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:43:27 2011 +0000

    protocol/server: log enhancements
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit d3e9a97b6ef340f827cf55de5340a8bf5c732f3e
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Wed Mar 16 09:43:21 2011 +0000

    protocol/server: White space cleanup and NULL check validations.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 0d7628c6c2b0c1d1e1bdcc6dc3904d30d6ebf38e
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:43:13 2011 +0000

    protocol/auth directory updated with whitespace cleanup and proper logs
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit d643c1093a89398de6cbe333aeea5cf91a56b3ad
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:43:04 2011 +0000

    cluster/dht: log enhancements
    
    Signed-off-by: Shishir Gowda <shishirng@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 7df49c62422d33d19eaebeddd3fcdacccc9c7bce
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:42:29 2011 +0000

    cluster/dht: whitespace cleanup
    
    also fill tabs by spaces (untabify), and indent the code
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit a938b273338094599c79dad7f60883599450e4ac
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:42:19 2011 +0000

    features/locks: logging enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 56b86533b1e2eca1535a7b20955b72baf25cd2ae
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Mar 16 09:42:12 2011 +0000

    features/locks: White space related changes to adhere to coding guidelines.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 825a104afe892f91c77dfc3622b50116341c5bb2
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:42:06 2011 +0000

    features/access-control: logging enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit d5bbe1e4d45a96f3a68c8e862ad051e675970911
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Mar 16 09:41:58 2011 +0000

    features/access-control: White space related changes to adhere to coding guidelines.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 4e6c54e75436c7e922981a2513a3a5c9fd293568
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:41:52 2011 +0000

    performance/stat-prefetch: logging enhancements
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit eb537b0e5f97a74b4562fa8cb0ce24b60732323c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:41:44 2011 +0000

    performance/stat-prefetch: whitespace related changes to adhere to coding guidelines.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit b75f0fd11c4eba196ad236a5618df2befd137df0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:41:31 2011 +0000

    performance/write-behind: logging enhancements
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit aad5b36d0f04b3c7bf1cec0af63b158fd37b2183
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:41:25 2011 +0000

    performance/write-behind: whitespace cleanup.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 3629c2880488ea9d4fa34f9e026bd9007b91bd4a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:41:16 2011 +0000

    performance/read-ahead: logging enhancements.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit d0b82760dc06b16f323d65506337c8373ce6ceb1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:41:09 2011 +0000

    performance/read-ahead: white space related changes to adhere to coding guidelines.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit f6da369103a3a8962f3d6b7f9df6bd2f1f8cc8db
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:40:50 2011 +0000

    performance/quick-read: logging enhancements
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 4aeaa48108d924ea67d77fedfadb7d96a13712dd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:40:43 2011 +0000

    performance/quick-read: propagate errors during open back to actual fops.
    
    - If open fails and there are any other fops waiting on that open, those fops
        should also unwind with appropriate errors. Before this patch, irrespective
        of success/failure of open, fops waiting on it were stack_wound and since
        fd was invalid, they would fail with EBADFD errors. Due to this
        actual error would've got masked by EBADFD.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 094d42b9a8d1d5d68d29bfb9b0b735f5c94f8a36
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:40:35 2011 +0000

    performance/quick-read: whitespace related changes to adhere to coding guidelines.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 39b953c2749f1d9a9302276e6c829dc4681758a8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:40:22 2011 +0000

    performance/io-cache: logging enhancements
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 67609fd909f8fa0dc5fa812cc17c5441747ca4b8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 16 09:40:14 2011 +0000

    performance/io-cache: whitespace related changes to adhere to coding guidelines.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit e02171f1b86cfb3cd365c4c47edc83b8230985bd
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:40:06 2011 +0000

    rpc-transport: log enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 02d8dcbb5c7483ade3dd052d75e6430cb0253d1f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:39:57 2011 +0000

    rpc-transport: whitespace cleanup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit d4aae8327ac5581cd47dd0fcea796ddbb03be5ea
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:39:46 2011 +0000

    rpc/rpc-lib : log enhancements
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit abc2a6b0b91a82bb59327cd2a4ca72b8954e1425
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:39:21 2011 +0000

    glusterfsd: log enhancement
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit ca6528592eed88ff1598b25f1aaa1c99c14a2e32
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:39:15 2011 +0000

    glusterfsd: whitespace cleanup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 532edf1c4a8f0db7447d12657a100e8dd91a74e0
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:39:07 2011 +0000

    storage/posix: log enhancements
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 75bda6e41d9b244ab9d040a035582ea6bd4c8120
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:38:35 2011 +0000

    libglusterfs/src/*.c: whitespace cleanup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 858944850adf7ec04898a15db90e231655ac4965
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:38:56 2011 +0000

    storage/posix: whitespace cleanup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 924d2ed32d19a2a0014f803edd3d4511a0af99c2
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:38:28 2011 +0000

    libglusterfs: all header files updated
    
    * whitespace cleanup       (M-x whitespace-cleanup)
    * indentation fixes        (M-x indent-region)
    * replaced tab with spaces (M-x untabify)
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit ebe47d5dae42da18b289e7be44eb67a8157a56b1
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:38:21 2011 +0000

    libglusterfs: gf_log_nomem() and other minor updates
    
    log will be done when the memory allocation fails, hence in code,
    no explicit logs required for memory allocation failures.
    
    also, if there are logs before actually doing a log_init(), they will
    be logged in 'stderr'.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit ce01662eefb575d1afe397486653920ec101f40f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 16 09:37:55 2011 +0000

    libglusterfs: logging/mem-pool section white-space cleanup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit b44b06a9d0adb50b426e0ee195a9867e01240ada
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Wed Mar 16 13:11:45 2011 +0000

    mgmt/glusterd: Use PATH_MAX for pid_file.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2534 (Glusterd crashes on gsync stop.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2534

commit 9796d4bf3015042f1b2bef22a2be6c22fed4cf4d
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Wed Mar 16 12:59:54 2011 +0000

    features/marker: Invalid option "marker", use "gsync" instead.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 6ddc55874985008ee51982d755743f0d01161a44
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Wed Mar 16 05:58:09 2011 +0000

    mgmt/glusterd: Use dict_set_dynstr in place of dict_set_str.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 10eafa32914f2458f3bb30073724758a95a82310
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Mar 16 03:35:46 2011 +0000

    TOP: glusterd/mgmt related changes
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2516 (Implement gluster volume top command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2516

commit 3d1fc9ebe2b0292108dd0737cf8f40d6fcb8cf51
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Mar 16 03:35:16 2011 +0000

    TOP: cli, rpc/xdr related changes
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2516 (Implement gluster volume top command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2516

commit f208d7148fefd55b4073bda978816d71831ffefa
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Mar 16 03:34:53 2011 +0000

    TOP: io-stats related changes
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2516 (Implement gluster volume top command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2516

commit 4db0bc5977eb3e2d5bc0e3666bb6de5719d153a4
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Mar 15 22:25:55 2011 +0000

    features/marker: QUOTA related changes in marker translator.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit fa4e997970fb0e1d0abaae742a35701bcb576150
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Mon Mar 14 22:22:04 2011 +0000

    storage/posix: Added GF_XATTROP_ADD_LONG_ARRAY flag to perform 64bit xattrop operations.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 031eee923d8fd79bc1cf78b7b24fe82e44186848
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Mar 15 05:35:45 2011 +0000

    mgmt/glusterd: QUOTA Glusterd related changes.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit c5d93456dcd17ddeb189c3e1390e58f95e30b851
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Mar 15 05:36:18 2011 +0000

    cli: QUOTA cli related changes.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 8221c3cae1ce5c2f7d897e5637591c5437aeea69
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Mar 15 05:36:33 2011 +0000

    rpc: QUOTA rpc related changes.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2473 (Support for volume and directory level quota)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2473

commit 7d61416a443b1786158c6236f182b6c11b3619f7
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Feb 15 03:08:17 2011 +0000

    features/marker: open the timestamp file with O_TRUNC to update the ctime
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2354 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2354

commit ab7dc7aafa61ae66db4ce7aa5e33e3ee408fd878
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Feb 15 03:09:02 2011 +0000

    Revert "features/marker: Use touch TimeStamp file instead of futimens, to avoid the dependency of newer libc"
    
    This reverts commit e045741f2bb75344a557cd618e1c7b1691238703.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2354 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2354

commit da57b8e7541ced2be0464f461e29dc7428bbcb14
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 14 05:36:16 2011 +0000

    used S_ISVTX instead of 01000 in code for sticky bit check
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2369 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2369

commit c886643f97373944030c118b7f78d0a8c06b2291
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Mar 14 04:20:51 2011 +0000

    cluster/afr: Fix wrong memory allocation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2517 (the size of allocated memory may be wrong)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2517

commit ac408b608130768fc9d67b836cef7c3f69f24de5
Author: Vijay Bellur <vijay@dev.gluster.com>
Date:   Mon Mar 14 10:13:36 2011 -0700

    Revert "Eliminate syscall tight loop when handling EAGAIN in NFS."
    
    This reverts commit 689c1b5044e701e1b695a6e6c80647b9471ba454.

commit d66758b4930224ba8d050f728b701b3259bf9cc7
Author: Vijay Bellur <vijay@dev.gluster.com>
Date:   Mon Mar 14 10:13:08 2011 -0700

    Revert "Make sure we are looking at the right errno in the fix for bug 2452."
    
    This reverts commit dae57d72a58ff61fe6eda800d386bf83574ef5c2.

commit 9043b0f8b927e687decc738cf736e603436e9e51
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Mar 14 05:01:31 2011 +0000

    mgmt/Glusterd: Make use of regexp pattern-matching sections to set a sane value for remote-gsyncd
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit eadce9083876fb71d1be8f77715866fc8af45ba4
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Fri Mar 11 07:57:52 2011 +0000

    Gsyncd: Explicitly mention the path for the gsyncd.py script
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2437 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2437

commit 086ef357b64d4b7e5340226ada639813b1efd101
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Mar 13 23:10:14 2011 +0000

    Gsyncd: Include a directory glusterfs in the libexecdir, so that it is not cumbersome with other scripts
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2477 (Cleanup up the installation of geo-replication scripts.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2477

commit 2108ee66f226a124fd2ec20692e9941ed15464a5
Author: Anand Avati <avati@gluster.com>
Date:   Thu Mar 10 03:21:21 2011 +0000

    afr-entry-self-heal: fixes to detected renames (gfid based)
    
    - perform expunge first (before impunge) to be able to delete renamed away files
    - perform readdirp instead of readdir to get gfid along with entry names
    - if gfid mismatch is found, expunge the entry
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2500 (Self Healing not working)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2500

commit 3145f70fc27d8259b885049bcf7a737f4b7de569
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Mar 13 23:33:13 2011 +0000

    mgmt/Glusterd: remove the checks performed for all ops in brick_op
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit 05dbcd0cb2415bb218221eccc1e7005645aa318b
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 21:49:04 2011 +0000

    mgmt/glusterd: remodel glusterd store
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1754 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1754

commit 5a8edf3fc4deb4713d390690b144342e24659f8c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Mar 12 01:08:34 2011 +0000

    rpc-transport/rdma: handle cases where peer is NULL in send_completion.
    
    - There can be valid cases where peer is NULL - For eg., race b/w pollin
        received on handshake socket and as a result transport getting disconnected
        and handling of a send/recv completion on the same qp for some previous
        read/write - in send/recv_completion_process. Hence we should be checking
        for a valid peer pointer before accessing it.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2514 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2514

commit 40a5e452bea79d1c7c78af480354e16ef970ca63
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Mar 11 01:48:57 2011 +0000

    nfs-rpc: Fix order of freeing request and connection objects
    
    ..to prevent segfaults due to double frees and dereferencing of freed
    up memory.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2504 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2504

commit 57d4551c05cdc17d2a9d687aca66802ce7af53f0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Mar 11 04:32:20 2011 +0000

    posix: Set op_errno to ENOMEM on failed iobuf_get
    
    This prevents a situation where op_ret for the read fop is
    -1 but the op_errno is still 0.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1977 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1977

commit 1c6e8fdf678d18e3b1a5472ebc076e7b3cb323e4
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Mar 11 02:21:10 2011 +0000

    posix: Handle offset greater than file size of EOF determination
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1977 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1977

commit 190ef2ee5006614615144ed46935d1f8267bd021
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Mar 1 03:59:48 2011 +0000

    syncdaemon: fortify handling of failed xtime queries
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 3e95176263e31135039bc65b9aa510801af20d4d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Mar 9 07:14:54 2011 +0000

    do not access the inode while doing statfs in trace
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2502 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2502

commit b42578dbff924a2c0f70f379e4bcf67950d4ce9a
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Mar 9 06:16:45 2011 +0000

    mgmt/glusterd: mem-factor added as an option
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2501 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2501

commit 4f1639f6bffa0b882ce826e55c65025ba2630656
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Mar 8 02:06:22 2011 +0000

    Fix solaris build failure in latest git
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2440 (Fix solaris build issues seen on latest git)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2440

commit be00f14b935f775b4df45e2acf281b19a28f8f7e
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 8 01:07:26 2011 +0000

    gluster rebalance: set the proper permission of the file
    
    remove the sticky bit from the mode.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2369 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2369

commit a0aafa365dd355864d24232bd6d7f399ef38f9ef
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 02:20:39 2011 +0000

    cli: gluster profile CLI
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1965 (need a cmd to get io-stat details)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1965

commit 496a04f3b2d46893635f93e5a33032969a826cd2
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 02:20:20 2011 +0000

    libglusterfs: Add sort routine
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1965 (need a cmd to get io-stat details)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1965

commit 9c945fdebc195c030701257abf42c4959f97234e
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 02:20:00 2011 +0000

    glusterfsd: translator info event handling implementation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1965 (need a cmd to get io-stat details)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1965

commit 34bf8de743aaff3e7c242833a10791aedc404ea3
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 02:19:39 2011 +0000

    mgmt/glusterd: gluster profile implementation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1965 (need a cmd to get io-stat details)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1965

commit 970b22e377e20408df8646cdc61a968b55c145b1
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 02:19:20 2011 +0000

    rpc/xdr: Add gluster profile and brick op structures
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1965 (need a cmd to get io-stat details)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1965

commit 332508e8e3b5cd2ffe1c68e496d294d4fef2dea4
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 02:18:44 2011 +0000

    debug/io-stats: Changes for handling gluster profile
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1965 (need a cmd to get io-stat details)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1965

commit d23585307a0e333c9b1ff627df4c7e30b3642201
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Mar 10 02:18:22 2011 +0000

    rpc: Changes for handling unix domain sockets avoid race
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1965 (need a cmd to get io-stat details)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1965

commit 45fd0d904d11f07f8b523af2d1357f081e3c5dc1
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:43:03 2011 +0000

    syncdaemon: don't follow symlinks on entries query
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 38d57757b33983052594e14582611ef05f753581
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:42:48 2011 +0000

    syncdaemon: fortify purge implementation to not do silly things like following symlinks
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2377 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2377

commit 19e65beb16d2dc337d144e25337561ff6e82826a
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:42:33 2011 +0000

    syncademon: fortify handling of failed entries queries
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 6cfb0fe84547db1ce8c21f0710cd0c74e88607c0
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:41:29 2011 +0000

    Revert "syncdaemon: Syncdaemon should not crash on ENOENT while performing setxattr()"
    
    This reverts commit d6407c59a4fd262749edd11ecb457b1e5be7a77a.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2342 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2342

commit 8717ef57a7b2554fe35da27f3cfd775083538313
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:41:10 2011 +0000

    Revert "syncdaemon: Handling of deleted symlinks (of directories). When a symlink of a directory of master is deleted. The corresponding delete in slave is handled as rmdir() of the symlink assuming the file to be directory"
    
    This reverts commit bee672e5f70b3c6712280130aeb61da0674add11.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2377 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2377

commit 0121c4c9574e09181f73f9ca7316bce2c5ec7ba9
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:40:52 2011 +0000

    Revert "syncdaemon: Create conf directory if not preset"
    
    This reverts commit 38ae1720be39b62a4f199aa5be4ac85948bc23f0.
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit fa04a42cc5b9f187ea169b26cc60ee25ac8a3c31
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:40:38 2011 +0000

    syncdaemon: improve loglevel handling
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit f2dd7abbf1af9832c891e6edadba696cefbccbe1
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:40:21 2011 +0000

    syncdaemon: ensure stdio is flushed before exit
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit 50492481a2b1e5a1425598fb44d802ec047f6c2f
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:40:05 2011 +0000

    syncdaemon: add support from dumping urls in canonical and escaped canonical form
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit cbdf22d79ada40e483583a4277aba2faaa769892
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:39:47 2011 +0000

    syncdaemon: add versioning to config file
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit f9a982f30922d812097a70b87628a590b2f51f15
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 10 00:39:27 2011 +0000

    syncdaemon: configinterface: add support for regexp based pattern-matching sections
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit cad088fe3a77bd3322de278c0337c1e29906f9cc
Author: shishir gowda <shishirng@gluster.com>
Date:   Sun Mar 6 22:14:32 2011 +0000

    build fixes in mac os x
    
    Looks good.
    
    ----- Original Message -----
    From: "Amar Tumballi" <amar@gluster.com>
    To: rfc@dev.gluster.com
    Sent: Thursday, March 3, 2011 6:30:52 PM
    Subject: [PATCH BUG:625] build fixes in mac os x
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 625 (Gluster Fails to build on OS X 10.6.2)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=625

commit 7ef59472f10a69c90d94b73e97bca385c6b4b29e
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Mar 7 07:23:51 2011 +0000

    mgmt/glusterd: preserve delete volume payload structure for backward compatibility
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2494 ([glusterfs-3.1.3qa4]: replace brick and delete volume fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2494

commit f3dc620caaa7068ff12323a0001075140624733c
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Mar 7 04:38:35 2011 +0000

    mgmt/glusterd: reset pending count before sending the op
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2493 ([glusterfs-3.1.3qa4]: glusterd not reaching default state on errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2493

commit 108de35b1775db82cccaf0bd1b62ccacfb1c61e8
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Mar 7 04:38:15 2011 +0000

    mgmt/glusterd: fix payload errors
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2492 ([glusterfs-3.1.3qa4]: gluster operations fail)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2492

commit 135aca330b0429776125bdd98be4ccd85dcfa715
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Mar 4 02:41:35 2011 +0000

    mgmt/glusterd: Handle race in peer connect and reverse probe
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2486 ([glusterfs-3.1.3qa2]: Core generated due to SegFault in glusterd_sm.c)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2486

commit 5b909c83de45e9457eef773cb24770b47d51a632
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Mar 4 02:22:37 2011 +0000

    Solaris xattr support for symlink and special files.
    
    Since glusterfs uses xattr for storing gfid, and xattr support for
    symlinks and special files does not exist in solaris. The work around
    is provided by creating hidden files under export directory on solaris
    hosts only. the hidden files ares maintained in .glusterfs_xattr_inode directory,
    and all xattr ops on symlink and special files are redirected to respective
    inodes.
    
    All dir entries with name starting as .glusterfs (GF_HIDDEN_PATH) will
    not be shown in readdir ops.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2213 (Symlink fails with ENODATA)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2213

commit 0066a093a258bfd1a9130134318c3df3571a091d
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Mar 3 06:22:59 2011 +0000

    debug/trace: add logs for 'forget', 'release' and 'releasedir'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2332 (update 'debug/trace' to log gfid instead of 'ia_ino')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2332

commit 8f132b363d41e7fe94a8712ed297a5f810e8ed56
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Mar 3 05:47:33 2011 +0000

    glusterd: check for the variable before dereferencing it
    
    check if 'peerinfo->mgmt' is set (ie, handshake is completed), before
    sending any request to that peer.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2486 ([glusterfs-3.1.3qa2]: Core generated due to SegFault in glusterd_sm.c)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2486

commit 568d4027033a5cb89d6aaee757d4c71e5369fe25
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Mar 3 03:43:06 2011 +0000

    glusterd: handle a crash in dump_version_cbk (in handshake)
    
    reset 'frame->local' to NULL before STACK_DESTROY(), which prevents
    freeing of valid 'peerctx' pointer.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2485 ([glusterfs-3.1.3qa2]: Core generated due to SegFault in glusterd_rpc_notify)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2485

commit dae57d72a58ff61fe6eda800d386bf83574ef5c2
Author: Pavan T C <tcp@gluster.com>
Date:   Fri Mar 4 01:44:22 2011 +0000

    Make sure we are looking at the right errno in the fix for bug 2452.
    
    Signed-off-by: Pavan T C <tcp@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2452 (Excessive CPU usage /very low throughput while using NFS mounts)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2452

commit 689c1b5044e701e1b695a6e6c80647b9471ba454
Author: Pavan T C <tcp@gluster.com>
Date:   Wed Feb 23 06:23:26 2011 +0000

    Eliminate syscall tight loop when handling EAGAIN in NFS.
    
    Signed-off-by: Pavan T C <tcp@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2452 (Excessive CPU usage /very low throughput while using NFS mounts)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2452

commit 826bf14de9eafe1cb67c45f25a9cfb236649801a
Author: Gaurav <gaurav@gluster.com>
Date:   Thu Mar 3 02:04:51 2011 +0000

    NFS : Check for duplicate entries while filling up child_up array.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2483 (Showmount output is not consistent with exported volumes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2483

commit 77d82df9d5e0047b0f1779130c4031cf3ce8ae1b
Author: Rahul <rahul@gluster.com>
Date:   Tue Feb 22 04:13:14 2011 +0000

    Display correct usage of rebalance command when it is wrongly entered.
    
    Signed-off-by: Rahul <rahul@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1922 (Volume not present wrong message displayed on command line)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1922

commit 5166c40af2502d1a26d4c0947378321b9bc3857c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 1 06:55:03 2011 +0000

    gluster rebalance: send the proper 'procnum' to glusterd
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2333 (make glusterd more rpc friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2333

commit 4175d3e8e2ca1afc0e9f3404ca04fe29d522c81f
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 1 03:37:12 2011 +0000

    gluster rebalance: give option to split the command
    
    the 'gluster volume rebalance <VOLNAME> start' is enhanced with two more options:
    
    * 'gluster volume rebalance <VOLNAME> fix-layout start' (for fixing layout only)
    * 'gluster volume rebalance <VOLNAME> migrate-data start' (for migrating data only)
    
    Also the old way of running rebalance in one shot will still work fine
    
    * 'gluster volume rebalance <VOLNAME> start'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2258 (enhance gluster volume rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

commit ae578f0c6518afd22cf13c21eebca203352774d3
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 1 03:36:45 2011 +0000

    gluster rebalance: get the proper/exact error msg to cli
    
    introduce a new field in XDR structure, and hence change the version
    of program.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1922 (Volume not present wrong message displayed on command line)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1922

commit d95f28de8482c816c2b718d3cf62b667e7a6953c
Author: Gaurav <gaurav@gluster.com>
Date:   Tue Mar 1 06:02:52 2011 +0000

    CLI : NFS disable option through volume set.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2094 (Need option to turn off NFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2094

commit 4d9de810f1cb4211fc59ab5b042771402c998331
Author: Gaurav <gaurav@gluster.com>
Date:   Tue Mar 1 06:02:39 2011 +0000

    CLI : NFS persistent local/global options.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2064 (NFS options are removed upon glusterd restart)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2064

commit 63632c7b95d204cb077d999e32690a2cdcba1327
Author: Anand Avati <avati@gluster.com>
Date:   Tue Mar 1 14:49:59 2011 +0000

    rpcsvc: safe mem_put of req in nfs_rpcsvc_submit_vectors
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2481 (Crash in NFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2481

commit f8ac2f645716847929f89ed218487f67db3e9f01
Author: Anand Avati <avati@gluster.com>
Date:   Tue Mar 1 14:40:27 2011 +0000

    rpcsvc: perform mem_put at the very end for safe unrefs
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2481 (Crash in NFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2481

commit 7e546e16925e50dc33db05c67b8b5cad1b3922ef
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Feb 24 00:08:46 2011 +0000

    Gsync : Do not expose volume gsync, when geo-replication is disabled
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit a3ab0ad1f1c0a5574ae294f5d72aac4df8f50124
Author: Gaurav <gaurav@gluster.com>
Date:   Mon Feb 28 22:40:46 2011 +0000

    NFS : Send error reply on rpc decoding failure.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2436 (Not able to send error reply in nfs_rpcsvc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2436

commit 731f07378bc0dce305fd3625e9bd4846096a97e3
Author: Gaurav <gaurav@gluster.com>
Date:   Mon Feb 28 22:40:30 2011 +0000

    RPC : Sending error reply on decodong failure.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2435 (Not able to send error reply in rpcsvc.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2435

commit 972836043ea378cafb9639f2db9f04652955eef1
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 1 02:10:15 2011 +0000

    glusterd: remove rpc code from internals of glusterd
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2333 (make glusterd more rpc friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2333

commit bf73fd2d8d6805a9a3b947464c65a9847442bba3
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 25 08:38:44 2011 +0000

    glusterd: separate out cli specific programs and mgmt specific programs
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2333 (make glusterd more rpc friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2333

commit 36bd0291118dfee4df9d387eb94681d41a0abcbb
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 25 08:37:21 2011 +0000

    glusterd: dependency on 'priv->mgmt' completely removed
    
    using 'peerinfo->mgmt' instead.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2333 (make glusterd more rpc friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2333

commit 66825f283a28c591af673a9fa752e5f5dd8302db
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 25 08:35:36 2011 +0000

    glusterd: keep mgmt program peerinfo specific
    
    With different version of glusterd in different machines, its not
    possible to support using just one mgmt program. Instead each
    peerinfo structure should have its own mgmt programs, so one glusterd
    can support multiple versions
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2333 (make glusterd more rpc friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2333

commit 204fc1205af14bdd98d9a86b9f7293c5b7f6747a
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Mar 1 03:16:29 2011 +0000

    v2 Prevent removal of trusted.gfid xattr
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2461 (remove xattr of trusted.gfid succeeds)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2461

commit b99e0e06788380e41d6c08ea308a6dd87a7afdfe
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Feb 23 03:38:36 2011 +0000

    mgmt/Glusterd: while resetting the volume options, the previous data structures w.r.t auth. must be deleted
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2374 ([glusterfs 3.1.2] gluster volume set auth.reject command failure on nfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2374

commit 156e1e26d76d4b62ad1fae15938a1350c9bc892a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 1 00:49:19 2011 +0000

    check for inode and path being NULL before copying them
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2463 ([7b07d444a77526f27f860210930bf1d4c7fbea9b]: ./autogen.sh crashes glusterfs in fuse_getattr or fuse_setattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2463

commit ba1cea55eedec2f7f9fbbc10e581da2c9bcd8038
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 28 06:07:40 2011 +0000

    Stop building uuid test program
    
    Building tst_uuid.c results in a compilation error with -DDEBUG
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2447 (Enable assert () and memory accounting with DEBUG)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2447

commit 46c69ec62db97c52c5e8e42e23cf440f742e033e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Feb 23 09:34:30 2011 +0000

    rpcsvc: Handle more than one payload vectors.
    
    - fops like write can recieve payload data in more than one vector. This can
        happen with write-behind being loaded on client side.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2454 (rdma data corruption)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2454

commit c46f85b026a1d0ad90f7be0efa4cd380962a1741
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Feb 23 02:12:50 2011 +0000

    if volume created is both of tcp and rdma type show it in volume info
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2294 (Currently there is no way through cli to make a volume listen on both the transports (socket/rdma))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2294

commit 63f00588bbfd477c2f4579fd4392c14679dd7ac0
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Feb 24 06:16:36 2011 +0000

    mgmt/glusterd: prevent spurious cmd unlocks
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2460 ([glusterfs-3.2.0-gsync1]: gluserd crashed trying to access freed request)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2460

commit 8a96aa607b4e3a6c782a0d912b6bf101f82f7c07
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 28 00:25:05 2011 +0000

    performance/io-cache: Whitespace cleanup
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 8d6de6959ad49f413968b562a5963d665dc11488
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 28 00:24:47 2011 +0000

    libglusterfs/dict.c: Whitespace cleanup
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 44020e349649f774021bf65931ee10cf6b6ddd47
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 28 00:24:27 2011 +0000

    cluster/afr: Re-factoring code for alignment
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit b7be90b2674b0c9f1c219479c08b45e424684146
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 28 00:24:00 2011 +0000

    cluster/afr: Whitespace cleanup
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 3e2d1070754cbea8b0ef6c4239ffce9ffe5d856a
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 28 00:23:36 2011 +0000

    libglusterfs/xlator.c: whitespace cleanup
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit be002fbdba6c66ea6f04f51e45310faedcba5fd2
Author: Anand Avati <avati@gluster.com>
Date:   Fri Feb 25 13:23:56 2011 +0000

    dht: log filename on failed reavalidate
    
    The previous log message is pretty much useless without the path
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

commit 7b07d444a77526f27f860210930bf1d4c7fbea9b
Author: Lakshmipathi G <lakshmipathi@gluster.com>
Date:   Tue Feb 22 08:29:07 2011 +0000

    install gluster binaries under /opt/glusterfs/version with sym.link at /usr/bin
    
    Signed-off-by: Lakshmipathi G <lakshmipathi@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2279 (rpm spec file changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2279

commit 65ad0fb37b4df6ef842235c0ff3981c2611d56c5
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Feb 22 06:40:18 2011 +0000

    Solaris build fixes.
    
    Including compat.h for definitions of IXDR_PUT_U_../IXDR_GET_U..
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2440 (Fix solaris build issues seen on latest git)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2440

commit 4a95f8f3b39f58349ef0935b1746e543408b3080
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 18 03:10:29 2011 +0000

    man pages updated
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2444 (keep man pages upto date with new codebase.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2444

commit 991b61661d74de5b1349050308dbd131e0de607c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Feb 22 05:25:30 2011 +0000

    check the op_ret for less than zero in sp_create_cbk since posix can send negative values other than -1
    
    posix can send -ve values other than -1 in create:
    
    op_ret = setgid_override (this, real_path, &gid);
    
            if (op_ret < 0) {
                    goto out;
            }
    
    In stat-prefetch we check op_ret only for -1 which results in function
    proceeding and op_ret may become 0 due to other function calls in
    sp_create_cbk, hence crashes in fuse.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2409 (crash in stat prefetch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2409

commit 21e4db42468d5bb7ebd9fa6a91461edd11b2a6da
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Feb 22 05:25:11 2011 +0000

    storage/posix: set op_ret to -1 when setgid_override fails.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2409 (crash in stat prefetch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2409

commit 2a184da3ca83f03dec69fcf0f26ae84c231d2e37
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Feb 18 03:37:50 2011 +0000

    Solaris: disable cli support rebalance and replace brick
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2440 (Fix solaris build issues seen on latest git)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2440

commit 46279693027230d5454ad98c267d93d5139e19af
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Feb 22 05:00:37 2011 +0000

    send the CHILD_DOWN event also to fuse
    
    and start the fuse thread in CHILD_DOWN event too.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2005 (Mounting Gluster volume with RO bricks hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2005

commit d437dd91bf167675615d7c7c2f99abbed2d899a1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Feb 21 06:48:23 2011 +0000

    log the total replace brick command received
    
    Log the full replace brick command which says whether the command is
    start/pause/status/abort/commit.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1404 (need a dump of all the op/mgmt commands)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1404

commit 3af42dac5fbea3af8d65799fd50300838f2e1d33
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 18 03:34:23 2011 +0000

    glusterd/cli: option added to create volume with both transports
    
    to avail the option, enter the volume create command with arguments
    'transport tcp,rdma'
    
    and while mounting, on the mountpoints which works on rdma,
    
    do, mount -t glusterfs <IP>:/<VOLNAME>-rdma <MOUNT-POINT>
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2294 (Currently there is no way through cli to make a volume listen on both the transports (socket/rdma))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2294

commit 28bda239100b9eef9b378dac2052a19d7264a51c
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 18 05:18:20 2011 +0000

    debug/trace: updated the logs to print gfid instead of 'ino' values
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2332 (update 'debug/trace' to log gfid instead of 'ia_ino')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2332

commit e8aed37adf3f623abd1b05a6926615002987bf17
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Feb 19 01:52:22 2011 +0000

    glusterd: make it more RPC friendly
    
    make sure each procedure has a actor associated with it.
    that way proper versioning can be implemented in modules
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2333 (make glusterd more rpc friendly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2333

commit b2d94417764ca5462cbdcdd634ea45ba12c8877f
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jan 13 06:55:37 2011 +0000

    fuse-resolve: correction in resolve logic
    
    * bring in soft (gfid based) and hard (path based) resolving
    * 'fd' resolving to new graph is not yet done.
    * fuse-resolve works similar to server-resolve
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2281 (I/O operations exit when add-brick is done)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2281

commit 23d9783a192669b638d42b8dd127ad69ea36f950
Author: Anand Avati <avati@gluster.com>
Date:   Fri Feb 4 21:43:49 2011 +0000

    dht: do not send revalidates to all subvols
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2450 (scalability enhancements)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2450

commit a144f2ca40d43a6ee3a50802fe1e8d1eda7a53b7
Author: Anand Avati <avati@gluster.com>
Date:   Fri Feb 4 21:43:19 2011 +0000

    core: have framework for GF_EVENT_CHILD_MODIFIED notifcation event
    
    If anything changes anywhere in the graph, all xlators know that
    something has changed. Previously dht and afr would mask certain
    events from propagating up. Now they forward GF_EVENT_CHILD_MODIFIED
    event in those situations
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2450 (scalability enhancements)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2450

commit 595e0df48bf387a87eb62a76d437a7ea79a0bc8a
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Feb 21 04:02:24 2011 +0000

    mgmt/glusterd: In store-retrieve exit with error message instead of crashing.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2066 (glusterd crashed while trying to restore volumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2066

commit b00b3d46c226d339a1cfde70ceab101cee2ac865
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Feb 21 08:45:41 2011 +0000

    rpc/rpc-clnt: don't use iobref passed from caller to hold iobufs required for building program and rpc headers.
    
    - clustering translators like replicate assume iobrefs will be used as
        read-only by lower layers and there by use the same iobref while
        winding calls to multiple children. Since iobrefs can hold only limited
        number of iobufs, this limits the number of children these translators
        can have without overflowing iobrefs.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2157 (glusterfsd crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2157

commit 6312b2fca35b907acf6d29591a608767a2d67781
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Feb 22 01:38:30 2011 +0000

    free the tokens obtained from the cli
    
    The cli command which is tokenized is not freed leading to a memory
    leak.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2113 (cli: memory corruption in add-brick and create volume parsing functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2113

commit ccee8039720f8253d460384aa6659edd8e75f3db
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Feb 18 00:06:26 2011 +0000

    Fix getcwd size arg to make it work in solaris.
    
    glusterfs/d -f path failed if the path was not absolute.
    If the BUF argument is NULL, then on solaris the size argument has to be passed.
    On linux, if the size argument passed is 0, then it dynmically allocates a buffer
     of the required size. The fix is to pass PATH_MAX as the size for consistency.
    
    Signed-off-by: Shishir Gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2443 (starting glusterfs/d -f with relative path crashes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2443

commit 65e5cc0f394e1d2faaab3dc5d097a3f01b03dd41
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Feb 17 07:31:18 2011 +0000

    Solaris build fixes
    
    Disable geosync build for non-linux platforms.
    And fix solaris related build failures.The symbol getxattr was not
     available on solaris. The build on linux passed as getxattr symbol was
    available in the library. The argument was not being used, hence
    removed it.
    Make 64 bit build default in CFLAGS option by passing -m64 option
    Signed-off-by: Shishir Gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2440 (Fix solaris build issues seen on latest git)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2440

commit 46f0277dfcca246b12700b2c6893abcc14480623
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jan 26 13:28:04 2011 +0000

    replicate: set read-child to the subvolume which replied first (fastest)
    
    In the old logic read-child was set to the last subvolume which replied.
    Now it is updated to the first subvolume. This way we can ensure that local
    servers are preferred for reads _most_ of the times.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1172 (ls -lh on NFS mount of 2-mirror replicate gives incorrect file size)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1172

commit d3c622abaa6788e3b62628d2847618713b896cdf
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jan 25 15:03:52 2011 +0000

    io-threads: use slow/normal/fast classification of fops
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2241 (GlusterFs Stat Actions Degrade During I/O)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2241

commit c3590820ad372fa77c70ebfa37aaa0c4b540dd7a
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jan 25 15:03:51 2011 +0000

    io-threads: implement bulk and priority queues
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2241 (GlusterFs Stat Actions Degrade During I/O)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2241

commit 8d69845dfdd31b798fb02b08a1eabbc88d31243c
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jan 25 15:03:50 2011 +0000

    io-threads: whitespace cleanup
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2241 (GlusterFs Stat Actions Degrade During I/O)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2241

commit ea0634bf88dd63294559c2e4542b73b772b7ec56
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Feb 18 01:27:31 2011 +0000

    Validate peer probe command's hostname/ip address.
    
    Note, if an ip octet range exceeds 255, though this fails as a valid
    ipv4 address, it is still a valid hostname.
    valid chars are: 'a'-'z', '0' - '9', '-', '.' with a max of 255 chars.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2194 (gluster peer probe on a ip octet value bigger than 255 has no validation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2194

commit 2795f3e03a299daf88e3172b068511d41c493247
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 21 12:11:59 2011 +0000

    libglusterfs: Enable assert() and memory accounting with DEBUG
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2447 (Enable assert () and memory accounting with DEBUG)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2447

commit c47961cc18f7bbc1b46e1cdf5662b8ec409065e5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Feb 3 01:56:28 2011 +0000

    performance/quick-read: disable caching for fds opened with GF_OPEN_NOWB flags.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2240 (Solaris client hangs on file read operations)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2240

commit bf767b85e3e92ec4bad52c6af141299d2afa4480
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 18 02:55:38 2011 +0000

    cluster/dht : implement a fsetxattr() command
    
    Thanks to Jeff Darcy <jdarcy(at)redhat.com> for the patch
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2319 (DHT uses wrong subvolume for fsetxattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2319

commit 069d7765898ef6f8d1334b23bf8ed9aee017b47a
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 18 02:54:49 2011 +0000

    rpc/xdr: update .x files
    
    * now, 'rpcgen $filename-xdr.x' file will result in $filename-xdr.h
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2153 (glusterfs3.x does not match "generated" source)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2153

commit 52cf9e992749a7cd5b2411581eff4c052d055ea9
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Feb 8 02:22:52 2011 +0000

    cluster/afr: stop spawning self-heal loops when the self-heal fails
    
    With the current model of self-heal, any loop wont resume if a
    self-heal failure happens. I have added the fix to stop spawning the
    initial loops on self-heal failure.
    Fixed the invalid read shown in valgrind in diff-self-heal.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1174 (Replicate spawns read loops even after destination fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1174

commit e77eae0f04b90ad9722ce82d59fd552cae63c347
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Feb 17 19:18:12 2011 +0000

    libglusterfs/dict: memcpy() data_t in unserialize.
    
    This fixes a race in dht_getxattr() where the xattr dictionary
    returned by one of the subvolumes can get free'd before STACK_UNWIND,
    leading to applications seeing junk values.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2442 (getxattr() on a directory sometimes returns junk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2442

commit fc63f24904b14aaad338aa44107cbda7e547e6b1
Author: Sachidananda <sac@gluster.com>
Date:   Fri Feb 11 02:08:55 2011 +0000

    Check correct variable after function call.
    
    And some white space cleanups.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2410 (Wrong variable checked after a function call)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2410

commit de44838d514e1f83a81dcff9438adbbb268ef981
Author: Sachidananda <sac@gluster.com>
Date:   Thu Jan 27 00:29:21 2011 +0000

    Typo fixes in log and cli messages.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2321 (Typo in logs and cli messages)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2321

commit 26cedae57d5b7cb8d50ed077ce29c92e30d6e260
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Feb 16 01:48:03 2011 +0000

    glusterd-volgen: fix a issue of wrongly closing '0' fd.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2421 ([glusterfs-3.1.2gsync10]: epoll_create returning 0)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2421

commit 3f0525e65e7eb1d48610f13152b676dd6d9208f5
Author: Anand Avati <avati@gluster.com>
Date:   Wed Feb 16 01:41:44 2011 +0000

    volgen: avoid fclose() on cosed FILE *
    
    It can so happen that a previously freed up FILE * structure has 0'ed
    out memory and a second fclose() on it can result in close(0). This
    results in bad bad things happening.
    
    Signed-off-by: Anand Avati <avati@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2421 ([glusterfs-3.1.2gsync10]: epoll_create returning 0)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2421

commit 43b68bb25c9ee16c10342ef643a6ecb82a345e16
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Feb 15 18:01:54 2011 +0000

    syncdaemon: fix RePCe version query
    
    RepceClient.repce_version fetched its own RePCe version, instead of
    querying peer, so lame.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2381 (RePCe versioning)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2381

commit 8ce08eb78165c9107925f23ac3057ee2cc01ff2f
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Feb 15 11:34:51 2011 +0000

    syncdaemon: Checking for the existence of gsyncd by trying to aquire a lock on the pidfile.
    
    If the locking succeeds then gsyncd is not running and if it fails then it means
    that gsyncd is running.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 1569424d1425a2f81c428d3968cd103ab2cad49e
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Feb 15 10:52:32 2011 +0000

    syncdaemon: change pidfile handling approach
    
    Signal handling of the python interpreter is a bit messy, so we cannot
    rely on executing a final clause upon termination. Switch over fcntl
    lock based pidfile handling which can provide reliable info about status
    of the process. (Due to aforementioned reason, pidfile as such is not
    guaranteed to be cleaned up, but lock acquisition is a reliable measure.)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit a68b4ad416970ec0ca710f650f54b87c3b92428e
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Feb 15 08:58:05 2011 +0000

    syncdaemon: Check for ctx context in the glusterd_op_stage_gsyc_set().
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 647d599f86f5577a94800607ff95b3e3636c4782
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Feb 15 03:08:44 2011 +0000

    syncdaemon: set the default value of timeout to 120sec
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 5a6720f1ee4ad6d96dae23742315c8ef35555a3b
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Mon Feb 14 19:27:34 2011 +0000

    syncdaemon: Moved the gsync start code to cli.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 98cfaa15d8c51728ea4d3555667328b94ef497c1
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Feb 14 16:43:36 2011 +0000

    Changes to include geo-sync in spec
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 30504941ea36ed40bbb628e8144ec2413e6fe765
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 14 16:42:05 2011 +0000

    syncdaemon: fix some pidfile issues
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 8c801cfd05eb533ae64ea9f06e49e632955cf0c0
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 14 16:42:04 2011 +0000

    syncdaemon: make /usr/libexec/gsyncd the default remote gsyncd (incomplete hacky quickfix)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2427 (set a proper default for remote syncdaemon)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2427

commit 248a1b7d387832dd97f43eb74b8b9d168292f3a0
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 14 16:42:03 2011 +0000

    syncdaemon: use "ping" message instead of "__version__" to wait for remote to come up
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2424 (Starting gsyncd with --debug : AttributeError: type object 'FILEServer' has no attribute '__version__')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2424

commit 741ce91b89cf221f8be94168e1d04916cc2f3204
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Feb 14 13:33:00 2011 +0000

    cluster/dht: Send removexattr() to all subvolumes.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2426 (removexattr is not sent to all subvolumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2426

commit d6f065b350a72a34b9a435a89d9b7cb59081bb44
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Mon Feb 14 01:01:19 2011 +0000

    syncdaemon: config-get-all option add to gsync cli.
    
    Signed-off-by: Mohammed Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 0cc73c92734acc86cb559fc2d3b3ee8c834e5f63
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 14 11:19:25 2011 +0000

    syncdaemon: fix KeyError
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 653a46850d765ca00a76452c76950ed60ab967d3
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 14 10:57:59 2011 +0000

    syncdaemon: make configparser code work with all supported python versions
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 1b04647157079d35851e206b8e9572960b2de214
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Sun Feb 13 03:46:56 2011 +0000

    syncdaemon: Using /usr/local/libexec/python/syncdaemon as the default directory where the python scripts are installed.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 76cbd26728a491fef0c7e2d657a931910ba3f8d1
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Feb 13 02:01:30 2011 +0000

    syncdaemon: conf file to be read properly
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 38ae1720be39b62a4f199aa5be4ac85948bc23f0
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Feb 13 01:58:09 2011 +0000

    syncdaemon: Create conf directory if not preset
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit f0831feae02a0c248b674c9cf9e9cc282e0e4854
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Feb 11 07:19:05 2011 +0000

    fix a typo in xdr_gf1_cli_gsync_set_req function
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2418 ([glusterfs-3.1.2qa7]: crash in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2418

commit 206b11705f36d4cc74d80465e77ecc9d74c69405
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Feb 11 07:06:52 2011 +0000

    initialize the cli_req structure before sending it to xdr
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2418 ([glusterfs-3.1.2qa7]: crash in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2418

commit bee672e5f70b3c6712280130aeb61da0674add11
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Feb 9 08:15:59 2011 +0000

    syncdaemon: Handling of deleted symlinks (of directories). When a symlink of a directory of master is deleted. The corresponding delete in slave is handled as rmdir() of the symlink assuming the file to be directory
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2377 (gsyncd.py RepceClient: call (symlink) failed on peer with instance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2377

commit 7b16a08989e804e857589c8a34881140150dc11c
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Fri Feb 11 01:06:55 2011 +0000

    syncdaemon: configinterface.py file moved under xlators/features/marker/utils/syncdaemon/ directory.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit d6407c59a4fd262749edd11ecb457b1e5be7a77a
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Feb 9 02:12:59 2011 +0000

    syncdaemon: Syncdaemon should not crash on ENOENT while performing setxattr()
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2342 ([glusterfs-3.1.2geosyncqa4]: crash in gsyncd script)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2342

commit 6248ead2ab0481a40d91b824fb249e4bc4f943ba
Author: Gaurav <gaurav@gluster.com>
Date:   Wed Feb 9 00:39:55 2011 +0000

    NFS : Fail Nfs init if volume-id not found.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2124 (NFS crashes when volume-id option is not given with dynamic-volume option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2124

commit 2e81c881f036d90323fd07d7df07d881723d7a28
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Thu Feb 10 05:29:34 2011 +0000

    gsync: cli support for gsyncd.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 08ca1d3c7801d22f1de452f098b0a5df251ca5e7
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Feb 9 06:11:02 2011 +0000

    removed some of the stale scripts
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2393 ('gluster-volgen' and 'gluster-defrag' scripts are stale, but present in AMI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2393

commit 07402f590e12b097e8267e924e0ae69d9b8964fb
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 20:42:24 2011 +0000

    syncdaemon: config revamp #3: implement command line get/set/del interface to configuration
    
    The INI style config file has following type of sections:
    
    - [global]
    - [peers <local>]
    - [peers <local> <remote>]
    
    Option dispatch to sections is derived from command line (ie., [global]
    if no arg given, [peers <local>] with <local> being the only arg,
    [peers <local> <remote>] if <local> and <remote> args are provided).
    So this all happens under the hood, gsyncd users need not to specify
    sections.
    
    New command line options:
    
    - query options:
      --config-get-all
      --config-get OPT
    - modify options:
      --config-set OPT VAL
      --config-del OPT
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit ebd7e1771c69a056f0456ff2dccac4319806f63b
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 20:42:23 2011 +0000

    syncdaemon: config revamp #2: implement canonicalized urls, use them in config file sections
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit d6363c595ace12a1bf9060dcd76a9e88e58d3db0
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 20:42:22 2011 +0000

    syncdaemon: config revamp #1: drop simplecfg, switch to stdlib's ConfigParser
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 71888401e2b959db316a9a296580d1e1c0c3a882
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Feb 8 06:33:38 2011 +0000

    syncdaemon: Removing the simplecfg.py entry from the Makefile.am, since it is removed.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit e045741f2bb75344a557cd618e1c7b1691238703
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Feb 8 04:05:21 2011 +0000

    features/marker: Use touch TimeStamp file instead of futimens, to avoid the dependency of newer libc
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2354 (handling futimens with older glibc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2354

commit ff7a493428e011f961d541e59e52ddb53c331d9c
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 20:28:48 2011 +0000

    syncdaemon: refine RePCe version check to tolerate difference in minor
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2381 (RePCe versioning)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2381

commit b6fcde94b37ba6d669ef24e4537846f33ac8ef41
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Jan 28 03:34:05 2011 +0000

    volgen: specify a mode argument for open(2)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2310 (georeplication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2310

commit 44773417bcaafeb6b7a8c44b5dc22bc7969e3102
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Feb 3 21:23:15 2011 +0000

    cluster/dht: Perform self-heal as root
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2370 (cluster/afr: Perform self-heal as root)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2370

commit 9f2e9fc465361e7821627a8c3a22863bb25b0810
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Feb 3 21:22:44 2011 +0000

    cluster/afr: Perform self-heal as root
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2370 (cluster/afr: Perform self-heal as root)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2370

commit 9cfa22f828f69c9f1f48b5e8994a4dff48d283a6
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Feb 7 05:42:18 2011 +0000

    protocol/client: decrement reopen fd count in cases of re-open errors
    
    In post-client-handshake client tries to re-open files, dirs, but if those
    files/dirs are already deleted when the brick is down the reopens
    won't even get triggered. In those cases the re-open fd count needs to
    be decremented to make sure the child up is triggered.
    I have also made similar changes in all the error cases of re-open/re-open-dir
    cbks. Lock recovery is already handling all these errors.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1761 (incorrect self-heal behaviour when files are deleted)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1761

commit 3a467b62babad8d44605db34601927025227f90e
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Feb 4 01:12:31 2011 +0000

    cluster/dht: restore attrs of dirs in self-heal
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2371 (dht: Set owners of directories after performing self-heal as root)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2371

commit ffbbb6a17075714865820a2f9722edcd70a4436f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Jan 31 03:29:13 2011 +0000

    rpc/rpc-clnt: don't access rpcreq after putting the struct back into mem-pool.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2335 (Segmentation fault in saved_frames_unwind)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2335

commit 3bad56d0d39e132b43d0122a570ba1b59a9a7caa
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 4 01:29:08 2011 +0000

    gluster rebalance: fix the permission issue of rebalanced files
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2369 (Rebalanced files written as root:root on any brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2369

commit 31efe81b13d6761cf153e71f7ac150751b2d4090
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 01:32:57 2011 +0000

    syncdaemon: add "setattr" server method, needed to synchronize metadata of links/dirs
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2318 (gsyncd.py :chmod on directory not working)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2318

commit d376253d1e91b9fc29f6a23253021647e139c2c1
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 01:32:56 2011 +0000

    syncdaemon: fix broken symlink handling in "purge" call
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2340 ([glusterfs-3.1.2geosyncqa4]: crash in gsyncd script while posix compliance test was running)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2340

commit 4b96f79fa19191344ddeeafd40df8b6d18ef7cc9
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 01:32:55 2011 +0000

    syncdaemon: version the rpc
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2381 (RePCe versioning)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2381

commit 67f842aa406a05fd701f9dbdcd373516fa529087
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 01:32:54 2011 +0000

    syncdaemon: improve program termination
    
    - get rid of annoying "TypeError: 'str' object is not callable" message with python 2.4
    - don't leave program hanging dead when failure is hit
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2380 (TypeError: 'str' object is not callable)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2380

commit 681928ddc750c28b12ec5097aff0dc694a5275d6
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Feb 7 01:32:53 2011 +0000

    syncdaemon: display slave role in log output
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2379 (master and slave log should be easier to distinguish)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2379

commit e266833e72749368019b7dcae32dc206d180acdd
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Fri Feb 4 11:22:55 2011 -0800

    Revert "distribute: Return ESTALE when dir selfheal finds no fix"
    
    This reverts commit a4c948aca6058049523e31acf33ce5770f8693ad.

commit ed743d89affe8be2d9d7da87479a498af40e12b0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Feb 4 03:14:37 2011 +0000

    mount3: Do not return error when mount list is empty
    
    An exports list can be empty when no subvolumes have come up.
    No point returning error and confusing the user.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2345 (Taking distribute brick down returns 10006 error on mount command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2345

commit 44e68cbf833cc176d589780d47ffdbe5b4c3ab7c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Feb 4 02:04:08 2011 +0000

    nfs: Set volume started after root lookup succeeds
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2345 (Taking distribute brick down returns 10006 error on mount command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2345

commit a139e43f484d1b434c9120f9fb99bf5ff33fb51d
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Fri Feb 4 02:12:19 2011 +0000

    marker: Updating the xtime marks on both the paths in rename fop.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2372 (marker: time stamp not updated with rename)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2372

commit 5f8e2cab86eab7f5ee5b4bb9b649376e476c740c
Author: Gaurav <gaurav@gluster.com>
Date:   Mon Jan 31 04:25:38 2011 +0000

    Logging : Use of uuid_utoa and uuid_utoa_r.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2308 (Threadsafe uuid to string conversion function)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2308

commit f3648c88ebc6d58a10854d564d3fc2c82290ce13
Author: Gaurav <gaurav@gluster.com>
Date:   Mon Jan 31 04:25:23 2011 +0000

    Logging : New uuid to string conversion functions.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2308 (Threadsafe uuid to string conversion function)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2308

commit ba40a3ece0a0b5b381e7d05c74d09cdd1818b817
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Feb 3 23:16:03 2011 +0000

    libxlator: New policy for aggregation of xtime:
    
    -Try to salvage errors like ENOENT/ENOTCONN/ENODATA,
                   -Propogate back any other error from any brick
                   -EINVAL if some assertion of the aggregation logic is broken
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2341 ([glusterfs-3.1.2gsyncqa4]: crash in gsyncd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2341

commit 7f59d855bb160a14a517e82b71e4f387b50cbf63
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Feb 3 23:15:17 2011 +0000

    libxlator: memdup the data that is required for aggregation of attributes
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2339 ([glusterfs-3.1.2geosyncqa4]: crash in gsyncd script)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2339

commit df9122f70deb6dbd0d950219ad1876e0a1ccd940
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Feb 2 01:46:15 2011 +0000

    cluster/afr: fix races in self-heal
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1188 (3.0.5 client crash - afr_set_split_brain)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1188

commit cbd61752ffefab6b42d29057e0f5b5e59191d51d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jan 27 02:50:38 2011 +0000

    performance/io-cache: disable caching if indicated by NFS.
    
    - wbflags - which contain flags to disable caching - passed by NFS were not
        stored in local by ioc_open, there by causing failure of io-cache to
        honour these flags.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2289 ([3.1.2qa3] EIO while reading & writing from a file concurrently)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2289

commit 066b1809876ba156d925edcb8fb470ee90319d3c
Author: Sachidananda <sac@gluster.com>
Date:   Tue Jan 25 05:32:01 2011 +0000

    Move hostname, ip address validating functions to libglusterfs.
    
    hostname and ip address validation functions are duplicated in several
    source files. Move them to libglusterfs.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2249 (Problems with hostname validation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2249

commit 7691550a5bd281e9d21771b37066d44434e92934
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jan 24 22:55:07 2011 +0000

    use rpc_clnt_{new,start} (), instead of rpc_clnt_init();
    
    to prevent a race between getting a CONNECT/DISCONNECT event before
    registering a notify function
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2314 (notify function registration in CLI)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2314

commit efda1b98f5ef5449687cf9ded8d0b2c82d948885
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jan 19 02:08:48 2011 +0000

    free GF_CALLOCed memory by GF_FREE instead of FREE
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 89f556574552abe80d9afe155eb366634375846c
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jan 17 10:51:17 2011 +0000

    glusterfsd-mgmt: handle the RPC_DISCONNECT event properly
    
    This patch solves the issue of hanging mount point in case of wrong server name
    is given during mount command
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1453 (mount command didn't give error message)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1453

commit 0e651882a9aadcb35ea764ea65c05c3661175e00
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Jan 17 00:44:39 2011 +0000

    remove op_errstr from glusterd_handle_rpc_msg as op_errstr is not used in that function
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1598 ([glusterfs-3.1.0qa22]: crash in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1598

commit bd8f7b95972abdbaba0b4ec067b6cb7968ad7e56
Author: Gaurav <gaurav@gluster.com>
Date:   Thu Jan 13 07:29:08 2011 +0000

    cli: Show 'commit' option in replace-brick.
    
    Signed-off-by: Gaurav <gaurav@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2273 (replace-brick help does not show commit option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2273

commit 85300e25f2d47e33b169d14fa9eb0b7cfe39011b
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jan 27 05:23:35 2011 +0000

    adding syncdaemon
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2310 (georeplication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2310

commit 7d883898c5225df3f7c38e67274b74ff8ac396c0
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Jan 27 05:23:34 2011 +0000

    mgmt/glusterd: restart bricks when syncdaemon is enabled
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2310 (georeplication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2310

commit 66808736b7af00a868e98464282b1118fc80a612
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jan 27 05:23:33 2011 +0000

    volgen: add marker to brick volfiles
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2310 (georeplication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2310

commit 482d77b85d84bf5c2b48e4717f8d186967e42e63
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jan 27 05:23:32 2011 +0000

    implement "--client-pid" option which can forcibly set the pid value in messages to a predefined value
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2310 (georeplication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2310

commit a2a92b99fc031544ff8a87861d34b2bbbdd2753c
Author: Junaid <junaid@gluster.com>
Date:   Thu Jan 27 05:23:31 2011 +0000

    adding marker translator
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2310 (georeplication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2310

commit 73bce15b61755509de23d32646135254d369a2f6
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Jan 27 05:23:30 2011 +0000

    adding libxlator, to ensure proper client side aggregation of marks by clustering translators
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2310 (georeplication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2310

commit 11dd59b788334fe2de1653ae85395986ba531606
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jan 24 20:35:44 2011 +0000

    rpc: handle proper 'ref', 'unref' of transport from rpc-clnt
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2250 ([glusterfs-3.1.2qa2]: SegFault in rpc-clnt.c)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2250

commit 40cdb88962cff1d32cd46cb089ad8bcd9be3d62d
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Jan 24 01:49:23 2011 +0000

    features/access-control: skip access-tests if the call is from fuse
    
    Fuse cant send aux gids. So access-control checks treat
    non-primary-group membership of user as "other". So skip
    access-control checks if the call is from fuse. We added a hack to
    treat all calls with pid set to 1 as calls from nfs. So for calls with pid
    not 1 we skip the access-control checks on all fops.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2296 (svn / subversion fails on gluster volume (replicated and non-replicated))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2296

commit 945ac04532d5efeeef324be485dcf2bade41708e
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Jan 19 01:49:05 2011 +0000

    mgmt/glusterd: error out if remove-brick comes for final bricks
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2298 (removing the last pair of bricks from a volume results in inconsistency)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2298

commit 26e1bfc68a6b4dff95d5fb244076116896add68d
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Jan 13 01:25:09 2011 +0000

    cli: return error when cmd execution fails
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2287 (Gluster CLI returns wrong return code.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2287

commit 5fd43d28ff12ac1c4e4d60e77a38659013b1ab3a
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Mon Jan 3 00:37:22 2011 +0000

    protocol/server: Distinguishing the locks based on the type of fop like inodelk and entrylk.
    
    Currently, the protocol server considers entrylk to be held only on directories
    and inodelk on files and thus when a client unmounts itself while holding locks,
    it fails to free entrylk locks held on files and inodelk locks held on directories.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2221 (Failed to free Inodlk locks on directories when the client holding the locks was unmounted before releasing the locks held.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2221

commit df6d34d0042421bb87f30bcf5e03d4ba0de7501c
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Dec 17 02:53:15 2010 +0000

    glusterd: de-register nfs rpcs when it is stopped
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1783 (kill glusterd and stop the cluster and start again - check nfs process)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1783

commit f2a067c4fe92f7aefc5f64ea1e5b000c16af0946
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jan 13 03:38:51 2011 +0000

    nfs3: Handle root resolution failures
    
    ..to prevent a second reply to the client which results in accessing
    a call state structure that gets freed on the first reply.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2286 ([glusterfs 3.1.2qa3]: Crash due to corruption in gf_dirent_free)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2286

commit 5368b898fad7264405275adc2092859e3c87c14e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jan 11 23:31:40 2011 +0000

    performance/quick-read: Fix unwinding of same frame twice when qr_loc_fill fails.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2274 (crash in fd_unref)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2274

commit 29b664f062795614417b9348f40503360f9f9c56
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Jan 11 04:47:00 2011 +0000

    mgmt/Glusterd: make nfs.mem-factor settable through CLI
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2277 (Regression in Gluster NFS re-read performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2277

commit 89cbbee063243d84dc64b15b2e2f403be1ca226b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jan 11 01:40:16 2011 +0000

    nfs: Introduce tunable for memory consumption
    
    NFS has used a common define called the mem-factor to determine
    how much memory is allocated for the following items:
    
    o inode table
    o local structures used by nfs for storing fop state
    o local structures used by nfs3 for storing nfs op state
    
    These are all allocated through the mem-pool. The factor is multiplied by
    a multiple that is specific to each data structure. For eg.
    
    define GF_NFS_CONCURRENT_OPS_MULT     15
    define GF_NFS_INODE_LRU_MULT          6000
    
    The first value is used for allocating a mem-pool for storing
    state for each fop or nfs op that is currently being handled. Knowing that linux
    allows at most 128 in-flight requests, this multiple combined with the default
    mem-factor of 15 gives us 225 slots in the mem-pool for the local structures.
    
    Similarly, 6000*15 gives us a space of 90k inodes in the lru.
    
    That means, increasing the common mem-factor will allow increasing the perf
    under some conditions. This patch introduces the mem-factor as a configurable
    option.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2277 (Regression in Gluster NFS re-read performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2277

commit e344d58762e12aa1edd1d4b133e1c1f77229b370
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Jan 11 01:24:02 2011 +0000

    exit if the key or the value is null while retrieving the peer information in glusterd_restore
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2271 ([glusterfs-3.1.2qa3]: entry->hostname in glusterd_friend_find_by_hostname is 0x0)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2271

commit f5934192a32a76baa12b7a22035187e63b7fdc1d
Author: Sachidananda <sac@gluster.com>
Date:   Fri Jan 7 06:11:34 2011 +0000

    Add corresponding va_end.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2247 (Add corresponding va_end)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2247

commit 985f87517b7d00afd626f2cc85ca2ab02d33e613
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Jan 7 00:45:48 2011 +0000

    cluster/replicate: update st_nlink count of stat sent to application after completion of entry-self-heal.
    
    - certain applications like 'find' use st_nlink count to optimize searches.
        Hence an incorrect hard link count can result in non-healing of some of
        the newly created subdirectories.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2187 (Self heal errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2187

commit 38d0824031f445620fa0d704043cd5dedadea721
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Jan 5 07:02:14 2011 +0000

    nfs3: Ignore requests for volumes without a single CHILD-UP
    
    NFS ignores the requests for subvolumes on which child-up has never been
    received.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2200 (cp dies with "Invalid argument" after failover)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2200

commit de6936a022e34a22eca39e189da368c03b46481f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Jan 4 03:15:35 2011 +0000

    check the value of op_ret pointer not the address
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 2e81e4b828d53068e291100f4024d628d9a59443
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jan 7 03:49:24 2011 +0000

    storage/posix: in opendir, allocate proper size for fd ctx pointer
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2280 (wrong size allocated for posix_fd in posix.c:posix_opendir())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2280

commit 879dc2f04f2bd35362bee214618f78ec4d688949
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jan 4 14:00:28 2011 +0000

    logging: reintroduce build warning for mismatching format strings and parameters
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit cfc387b0af174dfe303cdb3ef3ccfba979ef75ac
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jan 4 13:59:52 2011 +0000

    logging: fix format warnings
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit cbba1c3f55a7f73791310085b5d9bc65008f0b9b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Dec 29 05:42:02 2010 +0000

    nfs3: Force root lookup before starting fh resolution
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2200 (cp dies with "Invalid argument" after failover)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2200

commit 165efc45ab5518033612a58c1ac51243eb6bcef8
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Dec 28 01:14:19 2010 +0000

    nfs/server: unrefing inodes on error in nfs_loc_copy ().
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2252 (unreffing of inodes not done when memory allocation fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2252

commit 010394ee5e237606023f455955e005e111b9fa5b
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Dec 28 01:13:45 2010 +0000

    xlator.c: Unrefing inode's on error in loc_copy.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2252 (unreffing of inodes not done when memory allocation fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2252

commit 03c791e2d699574dae077d05a171a768bfb28ec3
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Dec 23 04:28:26 2010 +0000

    nfs: Support subdirectory exports
    
    Enable exporting directories as separate exports. Even though the directories
    wont show up in showmount output, they'll still be mount'able.
    
    The new option:
    
            nfs.export-dirs <on|off>
    
    is enabled by default so that users dont have to wait till this option
    is incorporated into the gluster command line.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1743 (XenServer is not compatible with GlusterNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

commit f0eeffe7b658164fb060a9805aa6cc422aba213b
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Dec 23 04:08:43 2010 +0000

    afr_lookup_done: Propogate the same inode number as sent in first lookup
    
    If only one subvolume was up, we used to unwind, without updating the ino
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2144 (errors removing directories when one subvolume is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2144

commit 818a4d128048721d70be2d6c8eafd2f41034b260
Author: Anand Avati <avati@gluster.com>
Date:   Wed Dec 29 12:23:08 2010 +0000

    stripe: fix memory leak
    
    destroy the frame copied and clean the local structure in stripe to avoid memory leak
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2253 (Memory leak in glusterfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2253

commit 98a1f381ba15dfc9c19ea3f9d778e8efb9e6be8e
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 8 03:43:20 2010 +0000

    quiesce: bring in feature to re-transmit the frames
    
    there was a corner case of 'fops' failing if they were in transit
    during a disconnection, if the failure is due to 'ENOTCONN'
    re-transmit the frame.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1500 (Mount point should not be in-accessible between reconnect to server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1500

commit 0cc2b35734224f44dda2fbd853506e04d889eb07
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Dec 22 04:56:37 2010 +0000

    change the log level from warning to debug while getting pending matrix
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1080 (clang errors in the file afr-self-heal-common.c)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1080

commit 2bf223a5d31cc82ffa7a06371fde6615ced3b68f
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Dec 22 04:35:10 2010 +0000

    send_fuse_iov: check args to prevent possible NULL dereferencing
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2223 (Crash in send_fuse_err)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2223

commit 2e317d2d35a50a6440865de5445008fd814cd298
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Dec 20 03:59:02 2010 +0000

    rdma : prevent confusing logs when both 'poll_in' and 'poll_err' are received.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 48f3faaa492b7a6f93e1f3d79cb66b34fd080468
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Dec 20 00:24:33 2010 +0000

    nfs3: Access cbk must account for auxgids on group access checks
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2045 (Write permission denied for non-primary group membership)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2045

commit d0fff8965875ed7e7cee223bd2c7b12df10cb6d7
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Dec 20 00:24:32 2010 +0000

    nfs: Do not touch iatt on failed fops
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2169 (NFS crash in nfs-fops due to failed fop from subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2169

commit 953f89d82f2c444719ba3150c9890c072a2e7fb3
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Dec 16 01:24:33 2010 +0000

    glusterd,cli: print single error message on failure
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1922 (Volume not present wrong message displayed on command line)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1922

commit e7512cbb171856a925b7db938da423b493339b00
Author: Harshavardhana <harsha@gluster.com>
Date:   Wed Dec 15 19:46:49 2010 +0000

    Add volume key to select data-self-heal-algorithm
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2218 (Replicate self-heal causes servers to go 100% cpu and unresponsive.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2218

commit e89a57733381b5fc70128eefc3184c03004b994a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Dec 15 06:00:28 2010 +0000

    log the total rebalance command recieved into the logfile
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2231 (log the total rebalance command recieved, in the logfile to avoid confusion)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2231

commit 8ba141e5e5d6616f05f69bb958b4a879198c1de5
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Dec 15 00:37:22 2010 +0000

    libglusterfs: data_copy needs to init the lock
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2226 (data_copy needs to init the data lock)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2226

commit 70f29baa5d45f765903d1547c57640e578836e7f
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Dec 13 05:53:54 2010 +0000

    Make STRIPE_STACK_UNWIND and STRIPE_STACK_DESTROY default calls in stripe
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2134 (inode leaks on stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2134

commit b4218f679113b3b0a6e08a0dd9482ec99ee77a38
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Dec 13 13:40:34 2010 +0000

    Implement STRIPE_STACK_UNWIND and STRIPE_STACK_DESTROY
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2134 (inode leaks on stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2134

commit ef27058512773a76853e3c6c715465f87da2b13a
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Dec 13 05:31:28 2010 +0000

    Remove check for path in stripe_local_wipe
    
    The check for path is done in loc_wipe. During loc_copy, inode ref is taken
    before path set succeeds or fails.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2134 (inode leaks on stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2134

commit f190be2ea2793b6a9be51fef1043224b477986dd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 23:03:37 2010 +0000

    performance/io-threads: implement rchecksum fop.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2220 (Implement rchecksum fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2220

commit 4e2b53708e0ca3f740815dbe7741f276069235ab
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Dec 14 01:03:38 2010 +0000

    setsockopt should be called with solaris specific arguments for solaris server
    
    ----- Original Message -----
    From: "Raghavendra Bhat" <raghavendrabhat@gluster.com>
    To: glusterfs@dev.gluster.com
    Sent: Tuesday, December 14, 2010 11:56:43 AM
    Subject: [PATCH BUG:2205 v4] setsockopt should be called with solaris	specific arguments for solaris server
    Looks fine to me.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2205 ([glusterfs-3.1.2qa1]: error while setting the keepalive time interval)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2205

commit 1637eabfd3e953a609cd5c82f58a7daa9d88b243
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Dec 13 06:06:20 2010 +0000

    cli: remove duplication of cmd help
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2089 (Documentation bug in replace-brick options)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2089

commit b754e531b48113596fddcd7d0b433ebcbf016c27
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 03:34:21 2010 +0000

    mgmt: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 361c804e9d70bd5a1c38eae1944635ca127c9ed9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 03:34:05 2010 +0000

    nfs: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit f9b61e81eb6ffbfcd25e43191797570b07412ef4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 03:33:52 2010 +0000

    features/quota: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 5ef77ec5a06d2fddb37c313fbee316da06002b82
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 03:33:38 2010 +0000

    cluster/distribute: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 3fd60a81d3a536cfd005e7fe3171d397d1019067
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 03:33:21 2010 +0000

    cluster/replicate: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 04fe9457923ff74e9fc396ed13c6a5eef4810493
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 00:14:25 2010 +0000

    libglusterfs: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 5f708e77242b0658f1619cca16e3e679163fb570
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 00:14:12 2010 +0000

    performance/quick-read: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit cc0c857ceba2bec066cb4167f4c84dfea925546b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 00:13:59 2010 +0000

    performance/io-cache: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 11b1c0735d7709d37ef775ff036e473a1b60801d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 00:13:41 2010 +0000

    performance/io-threads: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 9b87966e12fa53f59e383f701e9e391916a7860a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 00:13:28 2010 +0000

    performance/write-behind: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit 26caaeae10414f9888a438ad8559692a7f74f918
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 00:13:15 2010 +0000

    protocol: fix warnings due to format string mismatches during invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit aaad9c6f6ebe4bff3307e532cd802fafaed4a67f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Dec 13 00:12:54 2010 +0000

    rpc: fix format string mismatches in invocation of gf_log.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2211 ((re)introduce warnings for format string/parameter mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2211

commit df5f71b401decfb32006d7564db1a13bcd5e8be2
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Dec 10 12:24:16 2010 +0000

    client-reopen-cbk: fix a gf_log() crash due to wrong argument list
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit c40ce6beac9c3d9d006bcbd91bdac5e96055a00e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 9 01:03:57 2010 +0000

    rpc-transport/rdma: QP configuration changes.
    
    - set send and recv count to 4K.
      - set max_send_sge of QP to 2 since for msgs of type RDMA_NOMSG, there
        can be two vectors - rpc header and message from program.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2197 (applications running on large number of clients simultaneously result in ibv_post_send errors on server.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2197

commit ef8feeb8608728c738543b854f7f0795e80780e2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 9 01:03:39 2010 +0000

    rpc-transport/rdma: add informative debug messages when posting of send requests fail.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2197 (applications running on large number of clients simultaneously result in ibv_post_send errors on server.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2197

commit 625fb341b14acc704c588344ab5390c05b387179
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Dec 8 23:20:14 2010 +0000

    set the return value to -1 intitially which may be returned as success in validate_or_goto
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 9d4ba49cd3f8055d4305d85c6149311e36d78bdd
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Dec 8 23:14:04 2010 +0000

    check the return value after setting the fd context in afr
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 48d6fe293a487727d4686f64ef410a3df569f6a8
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Dec 8 22:55:24 2010 +0000

    check the return value properly after calling inode_path
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2203 ([glusterfs 3.1.1]: Core generated with Segmentation fault in afr-open.c)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2203

commit 40e1d364161b45299fcefd50879d532a01f4d2b5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Dec 10 04:48:49 2010 +0000

    rpcsvc: while handling transport-cleanup event look for listener with transport trans->listener instead of trans.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2208 (transport cleanup event is not sent to programs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2208

commit 9f480be0333863a2cb30088504d233fd6eb46ebf
Author: Anand Avati <avati@gluster.com>
Date:   Thu Dec 9 02:06:52 2010 +0000

    protocol: avoid repetitive disconnect logs
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 353fb2e97bfc3a44cc5301fa8dfb015406565048
Author: Anand Avati <avati@gluster.com>
Date:   Wed Dec 8 09:58:27 2010 +0000

    replicate: propagate CHILD_DOWN upwards properly
    
    During initialization if one subvolume returns CHILD_DOWN, then
    do not consider the other subvolume as down if we still haven't
    heard from it yet
    
    This causes DHT (on top) to prematurely (and wrongly) send
    CHILD_UP/DOWN upwards
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2200 (cp dies with "Invalid argument" after failover)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2200

commit 147b20c4a485ddb4b31b1811be4bf90610c91f7f
Author: Anand Avati <avati@gluster.com>
Date:   Tue Dec 7 05:36:54 2010 +0000

    nfs: cleanup inode_ref/inode_unref to fix inode leaks and extra unrefs
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2195 (Crash in __inode_retire on NFS failover)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2195

commit 64cdcbe39bcb8d52d0c6aa88ce5cd5f3d6062a9e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Dec 7 06:53:49 2010 +0000

    mgmt/glusterd: Use a static buffer to perform ioctl with SIOCGIFCONF
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2163 (Can't create volume using 3.1.1qa11 on OpenSolaris 2009.6)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2163

commit e3232db35a20e5cfd68ab3fb0b7d0931c4cfb67d
Author: Anand Avati <avati@gluster.com>
Date:   Tue Dec 7 00:19:30 2010 +0000

    gfid: disable setting/getting of gfid from higher level translators
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2196 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2196

commit f783ecfbfd8c873d97644b8b6b0d95e3f878b992
Author: Anand Avati <avati@gluster.com>
Date:   Tue Dec 7 00:02:10 2010 +0000

    rpc-clnt: show disconnect messages in log file by default
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit fceef36419503f332ffd1fccdcb03da86cf9cdb3
Author: Anand Avati <avati@gluster.com>
Date:   Mon Dec 6 23:28:19 2010 +0000

    inode: fix crash in logging during cyclic loop detection
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2196 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2196

commit caa77054005ea9ca9b806006103cd3f7eed10c7d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Dec 6 07:55:56 2010 +0000

    check whether the file is a symlink while doing utimes
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 881 (GlusterFS daemon hangs on replication of symlink (3.0.4))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=881

commit 574d938adcfe74f912fb2de8f77fc7a9d18c689b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 2 00:34:09 2010 +0000

    mount.glusterfs: use option --direct-io-mode instead of --disable-direct-io-mode
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2173 (enabling/disabling direct-io mode is not possible when glusterfs is mounted using mount command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2173

commit ae6e73f4d2a9fba6ccef42d49d70d8bbd7cba84a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Nov 26 00:45:50 2010 +0000

    nfs: Start nfs process even if portmap registration fails
    
    It helps to have the process be listed in ps ax|grep output
    so that user can get the path to the log from the listed
    command line and check what the problem is.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2093 (volumes cannot start when one node in a replicated setup is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2093

commit 773c9688bc8d3190eab3797190bd06d7acf275aa
Author: Anand Avati <avati@gluster.com>
Date:   Mon Nov 29 06:24:15 2010 +0000

    fuse-bridge: construct fa->rdev properly
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2145 ([3.1.1qa9] mknod does not work properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2145

commit 69a62d2a6d8ad127787aad2215c2130a03f58090
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Mon Nov 29 09:01:41 2010 -0800

    rpm: glusterfs.spec.in fixes for upgrade via rpm -Uvh

commit c0be54cfcd4491ca212226ed5687740813a4aeb6
Author: Anand Avati <avati@gluster.com>
Date:   Thu Nov 25 23:35:18 2010 +0000

    stat-prefetch: changes to incorporate gfid
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2136 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2136

commit 47548f09f005998598edd8183804cd93c35a12f3
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Nov 24 12:42:56 2010 +0000

    mgmt/glusterd: Enable stat-prefetch for fuse
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2136 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2136

commit b605865986f19cf5e376a16b963f68f28d4aea44
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Nov 25 04:11:11 2010 +0000

    nfs3: Prevent second lookup on a fresh entry lookup
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit 50e5c72fd63c44119b272435e715a712d848476a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Nov 25 04:11:10 2010 +0000

    nfsrpc: Add new macro nfs_rpcsvc_request_procnum
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit 6623055696e1b28267305ac45087497f4c6a884a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Nov 25 04:11:09 2010 +0000

    nfs: Export subvolumes on per-subvolume CHILD-UP
    
    ..so that nfs clients can mount an UP subvolume even if other subvolumes
    havent come up yet.
    
    This was a problem because nfs was waiting for all children to receive
    CHILD-UP before exporting any subvolume.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2093 (volumes cannot start when one node in a replicated setup is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2093

commit 26a8202550593232f941cd2251cfbeb304991808
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Nov 25 00:17:08 2010 +0000

    nfs3: Fresh inode lookup on failed revalidation
    
    Brings in changes that were earlier introduced in commit:
    f5afcc47f9f00472d6c2b3f48127e02332cd457a
    
    but reverted because the patch was buggy and caused a seg-fault
    due to extra inode_unrefs.
    
    It fixes that extra inode_unref and cleans up the revalidation logic.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit ac5e34ec840889bc3eaf07d2f7091432ff698fe2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Nov 25 00:17:07 2010 +0000

    nfs: Undo selective changes in inode revalidation
    
    Those changes were brought in by commit 161850285ff06e90f2c990989bab9513dd4a4289:
    "nfs: re-implement logic to perform fresh lookups when lookup revalidates fail"
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit 9e67fd90e0df32b9a450632566855339b133d3a6
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Nov 25 02:26:26 2010 +0000

    mgmt/glusterd: Move .cmd_log_history to log directory
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2154 (Move .cmd_log_history to log directory)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2154

commit c56b9967a33b8bb106d37df0cf6979b340dbf950
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 24 07:35:26 2010 +0000

    rpc-transport: don't merge payload iobuf and iobuf which holds program header into single iobref.
    
    - io-cache holds a reference on iobref passed from transport layer. Hence,
       two iobufs are accounted instead of one in calculated used cache size.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2135 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2135

commit b7ca86e7614c61f8bf0b1e4bea47b4bc0a7fe080
Author: Sachidananda <sac@gluster.com>
Date:   Thu Nov 25 01:05:08 2010 +0000

    rpc-coverage.sh: Make error messages explicit.
    
    Make failure explicit, with `set -e' script exits silently and we have
    no way to know where it failed unless run by set -x.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit f7436a82bc0d02639efaa8e4fdf922a9849d0713
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Nov 25 02:04:43 2010 +0000

    mgmt/glusterd: Temporary fix for a crash seen in replace-brick
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2084 ([3.1.1qa5] : replace-brick fails to migrate data when migration from same hostname)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2084

commit 5725f33e314c2fca6a4b9c2b102fc66361145301
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Nov 25 02:11:45 2010 +0000

    cli: Enhance message shown upon successful volume creation
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2034 (Why not start a volume after it has been created?)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2034

commit 43a039789cbbdb50d67c960c7a6f4d0ac1858e48
Author: Anand Avati <avati@gluster.com>
Date:   Wed Nov 24 07:24:33 2010 +0000

    resolver: include par_idx access within the conditional section
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 9f8edf2b2576a235526087f4fbc5769940f019ad
Author: Anand Avati <avati@gluster.com>
Date:   Wed Nov 24 07:15:19 2010 +0000

    iatt: fix bug in ia_makedev
    
    the wrong binary operator was resulting in lookup/stat showing wrong
    major/minor numbers for device files
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2145 ([3.1.1qa9] mknod does not work properly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2145

commit ab5c5610bb37e5f4fbcc4722abf21de3dc2c9679
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Nov 20 05:52:24 2010 +0000

    volgen: put back an amended form of check erased in 96f44835 ("do not error out if brick count is less than sub count...")
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2054 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2054

commit cef1669d5fdf43e1df38189759345170b90a1455
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Nov 16 19:35:12 2010 +0000

    volgen: clean up 0fbf226c (... add nfs.enable-ino32 as an option ...)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1972 (xcs get doesn't work with gNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1972

commit 8b1aac46732c871c6b97c1f2bbb7fcc5b79d52bd
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Nov 23 07:13:27 2010 +0000

    display the error to the user if volume stop is given on a volume which does not exist
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2140 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2140

commit 0ccd9f4f2ddf83d35cfa9bbc872ca84f6fb9c8a9
Author: Anand Avati <avati@gluster.com>
Date:   Tue Nov 23 10:35:56 2010 +0000

    inode: catch loop formation during inode_link() and fail linking
    
    - explores all parent branches
    - performs loop formation check only if the operation is resulting in relinking
      of an inode already existing in the table
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 7f68e386132af9e02bf37a3b4d0653de000bdefe
Author: Anand Avati <avati@gluster.com>
Date:   Mon Nov 22 10:52:51 2010 +0000

    resolver: handle corner cases of handling root inode better
    
    - changes in deep resolution and simple resolution of pure paths
      to handle resolution of "/"
    - warn on pure path resolution
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit f1205225417b3e0d5cf27f5ba85ccdfe0ef6b246
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Nov 22 00:55:44 2010 +0000

    display the error message to the user if a volume with the name is tried to be created
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1209 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1209

commit c509e7f185d4f76be9f5ddbd61839239198a0b1d
Author: Anand Avati <avati@gluster.com>
Date:   Fri Nov 19 06:25:40 2010 +0000

    rpc-coverage.sh: enhancements for more extensive testing
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit f6785d2b4999db7d42e8c1cd054fd7ec174e8136
Author: Anand Avati <avati@gluster.com>
Date:   Thu Nov 18 08:35:24 2010 +0000

    nfs: treat GF_EVENT_CHILD_CONNECTING as subvolume up status
    
    GF_EVENT_CHILD_CONNECTING is sent as a status from underlying subvolumes
    after a sufficient margin of time (tcp connect() timeout) if the subvolumes
    are not reachable.
    
    This should avoid the problem of NFS not being reachable if any volume
    is down
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2093 (volumes cannot start when one node in a replicated setup is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2093

commit e098653b73c7b379b2ad6bf7878bac65147f7ebe
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Nov 18 05:38:59 2010 +0000

    features/locks: Send prelock unlock only if it is not grantable and is a blocking lock call.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1017 (Locking deadlock when upgrading lock)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1017

commit e111591585c8e5f3c8404b72ad13b5f5580c25c4
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Nov 17 23:36:06 2010 +0000

    Remove spurious inode_ref call on parent dir in fuse_create_cbk
    
    The additional ref caused leaks. The ref is taken in __dentry_create
    called from inode_link
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2117 ([glusterfs-3.1.1qa7]: memleak in glusterfsd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2117

commit 001a44f7dc6cec6fb5ce555ce583af4428cc471d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Nov 18 02:32:38 2010 +0000

    error out if the data-self-heal-window-size is less than 1
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2120 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2120

commit 99134d33f85e38e5c37227ecb8fdfbe03bd521d0
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Nov 18 06:26:26 2010 +0000

    mgmt/glusterd: Avoid creating multiple destination brickinfo during replace-brick
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2084 ([3.1.1qa5] : replace-brick fails to migrate data when migration from same hostname)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2084

commit f0cdfd03051cee8d25f03103ed467438c6479e47
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 18 06:31:01 2010 +0000

    cluster/pump: send PARENT_UP to dst_child after init is successful
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2122 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2122

commit 61a8945649eced6c490a92e6533c5fb3a9d9a1d3
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 18 06:21:55 2010 +0000

    rpc-clnt: add check for NULL argument for rpc_clnt_start
    
    prevents crash when rpc_clnt_start is called before init
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2122 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2122

commit 9c80f63d8264718c5855f1f6cca9e5a801392ed3
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Nov 16 03:52:17 2010 +0000

    protocol/client: skip notify if query portmap is successful
    
    Mount point does not hang, though stale handle error on / till the downed brick is
    online again
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1905 (Mounting volume is not working when any one server is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1905

commit ce9f328aa93892ea79057c41c70836eb49fae8b5
Author: Anand Avati <avati@gluster.com>
Date:   Tue Nov 16 08:17:07 2010 +0000

    protocol/client: use the new rpc_clnt initialization methods
    
    This way of initializing an rpc_clnt object by splitting into a
    passive rpc_clnt_new and a delayed rpc_clnt_start between which
    registration of callback programs and notify methods are performed
    provides a race-free way to avoid the missing of connect notifications
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2078 (Volume Migration is not working)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2078

commit 8faf940c00e3722a2322ee70ba1e18d9b9bc8c9c
Author: Anand Avati <avati@gluster.com>
Date:   Tue Nov 16 08:16:42 2010 +0000

    rpc-clnt: introduce new way of creating rpc-clnt objects
    
    rpc_clnt_new() creates a new passive rpc clnt object.
    
    rpc_clnt_start() triggers the connection/reconnection from the object.
    
    rpc_clnt_init() - the old way - still works.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2078 (Volume Migration is not working)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2078

commit 15d56782ae560aa556d6af64896c4c879c6c46e6
Author: Anand Avati <avati@gluster.com>
Date:   Tue Nov 16 08:15:48 2010 +0000

    rpc-clnt: move rpc_clnt_reconnect() call to rpc_clnt_init
    
    Previously rpc_clnt_reconnect() was called inside rpc_clnt_connection_init
    which in turn was called from rpc_clnt_init. This change makes
    rpc_clnt_connection_init re-usable for the next patch
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2078 (Volume Migration is not working)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2078

commit b985dce6c4415a9d67fefabdbf2e5fe287e1dc62
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Nov 16 04:56:38 2010 +0000

    nfsrpc: Fail auth-unix if more than 16 gids found
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2045 (Write permission denied for non-primary group membership)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2045

commit 015b08d64dfea093d8fcd0a30b655469b18bbc2e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Nov 16 04:56:37 2010 +0000

    rpc-lib: Fail auth-unix if more than 16 gids found
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2045 (Write permission denied for non-primary group membership)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2045

commit 36f696c7dbc785be464acae737f4c25ed3af861a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Nov 16 03:44:37 2010 +0000

    rpc-lib: Copy auxiliary GIDs into request from de-XDRed buffer
    
    Fixes a problem where secondary groups are not accounted for in
    permission checks.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2045 (Write permission denied for non-primary group membership)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2045

commit 4cfd6e1b45da64429c3e10886e2ceb4e9c9deb5d
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Nov 16 01:07:20 2010 +0000

    Stripe I/O exits when graph changes
    
    Adding event CONNECTING to be handled like CHILDUP in notify.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2111 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2111

commit 66c768a4845482c42a77e458ecbc73488998fb13
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Nov 16 01:21:54 2010 +0000

    protocol/client: fix ping timeout checks in reconfigure()
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2104 ([3.1.1qa5]: network.ping-timeout set failed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2104

commit eb13791c229b011b41e63099ce097a4271ae0451
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Nov 16 01:26:00 2010 +0000

    cli: fix memory corruption in create volume and add-brick
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2113 (cli: memory corruption in add-brick and create volume parsing functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2113

commit bc3cad79cd0cf48318e723fd3377af979673374e
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Nov 16 01:26:45 2010 +0000

    fuse: dentry create time inode resolution fixes
    
    treat successful 'inode' resolution as stale entries in case of
    entry creation fops, instead of continueing with an error log with
    old entry.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1240 (DVM: after graph change, inodes should resolve to new inode-table)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1240

commit e10f1ec908139d9778406d07274dd390b7f56bc8
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Nov 16 00:12:58 2010 +0000

    Solaris: df -h returned invalid size
    
    The reason seems to have been multiplying fields with f_bsize, while
    they are in f_frsize units. On linux both f_bize and f_frbsize seems to
    have been the same
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1021 (NFS: df -h shows incorrect out put)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1021

commit 961fc917e8e9f13b8cab69b1ba11767d5c41a8ce
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Nov 15 06:44:44 2010 +0000

    Remove symlnk of log dir to /etc/glusterd
    
    Hence forth the default log dir will be /usr/local/var/log/glusterfs
    Missed out on log locate changes
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2109 (Remove symbolic link of log directory from /etc/glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2109

commit b552465ca4a8d65650cb1d0beb4ccfe5eaf93c26
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Nov 15 02:55:38 2010 +0000

    Remove symlnk of default log dir to /etc/glusterd
    
    Hence forth the default log dir will be /usr/local/var/log/glusterfs
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2109 (Remove symbolic link of log directory from /etc/glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2109

commit 6d42bc03d0ebe6100d9f3815f06637cb1b44c2ac
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 15 03:46:30 2010 +0000

    glusterd rebalance: update the status in failure cases
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1999 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1999

commit 553c15160e4e3b063f4b689ee762b6d14be9953b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Nov 15 05:57:46 2010 +0000

    Revert "nfs: Use only 38467 as default port instead of 3846[567]"
    
    This reverts commit be5c02a81c19336a6b922b1e1f28293c90955e7f.
    
    By default, continue to register the three original port numbers
    so that an upgrade to future version from 3.1 release does not
    break mount requests against portmap, which may have old port
    numbers registered.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1743 (XenServer is not compatible with GlusterNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

commit 78654d270cde028c5d7f9da29b2790b90c19e11f
Author: Anand Avati <avati@gluster.com>
Date:   Mon Nov 15 05:34:00 2010 +0000

    nfs: opendir/closedir for every readdir
    
    Revert "nfs3: Unref & unbind dir fd with inode lock on EOF"
    
    This reverts commit 4e6fb304ce41acbaf7c9ba67c06bf443e65082e8.
    
    The above commit (which unbinds fds at EOF) does not fix the original
    bug (1619) because a readdir from a second app could have already
    started before the readdir_cbk of the first app's readdir reaches
    NFS code. Hence the race still exists.
    
    Performing extra unrefs when EOF is received is not a reliable way
    of detecting that a client has performed a closedir (and to close
    the fd ourselves). Neither is interpreting a 0 cookies a new opendir.
    Clients can always use telldir/seekdir and hit EOFs twice.
    
    Due to the way NFS3 protocol is designed, it is just not possible
    for the server to reliably detect opendirs/closedirs performed by
    the client and map the corresponding readdirs to the same dir fd
    on the server side.
    
    The only reliable way of fixing this is to perform opendir/closedir
    at the cost of performance. Any optimization towards keeping dir fds
    open attempting to map them with application's opendir/closedir will
    either result in fd leaks or extra fd unrefs.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2061 (NFS server crashes in readdir_fstat_cbk due to extra fd unref)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2061

commit 7d48999c13b885d034528cfca61a8b63ade8a365
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 15 04:02:45 2010 +0000

    cluster/replicate: Fix memory leak in afr_fd_ctx_cleanup.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1438 (memory leaks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1438

commit 415f7f6a29b361dfccc197a6b67add1733c7f617
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Nov 13 02:06:12 2010 +0000

    check for dict also while setting the port for source brick while doing replace brick
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2084 ([3.1.1qa5] : replace-brick fails to migrate data when migration from same hostname)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2084

commit ec43d07c3ab758e0e8cfa427d914ab9c653068a4
Author: Pranith K <pranithk@gluster.com>
Date:   Sun Nov 14 00:13:25 2010 +0000

    cli: remove special behavior for help commands without readline
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2091 (Gluster CLI exits after issuing volume help)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2091

commit 22aa43c16357811f8218215d2f2f830005860c96
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Nov 14 12:08:23 2010 +0000

    mgmt/glusterd: fixes for uninterrupted replace-brick with nfs
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2084 ([3.1.1qa5] : replace-brick fails to migrate data when migration from same hostname)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2084

commit 479393858a1744adf7c9f56216ca228b188a7398
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Nov 14 12:07:30 2010 +0000

    cluster/pump: Reset saved path upon pump completion
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2084 ([3.1.1qa5] : replace-brick fails to migrate data when migration from same hostname)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2084

commit d6f1f04ef0db60bcc0f4963dbd1b76ce73c36779
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Nov 11 23:00:19 2010 +0000

    performance/quick-read: handle the errors in qr_loc_fill properly when an fop needs to do open before continuing.
    
    - without need_unwind set, 'goto out' will result in infinite loop.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2075 (inode_from_path silently consumes 99% CPU causing nfs client disconnects)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2075

commit 20fb15dc02a4d1a4b38335a988c0c1abafee7355
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Nov 12 04:01:01 2010 +0000

    mgmt/glusterd: "peer probe new-hostname" should replace old-hostname of friend
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1995 (Gluster Peer probe command keeps ip address instead of server name in the destination server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1995

commit fe349e42baa47dd7c010707bddbd114946f4d95b
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Nov 12 05:23:42 2010 +0000

    stripe: allow lookup on an entry if other than first subvolume is down
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2099 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2099

commit e48f8e62e0d7d68ca8b45402a6b9a79352fd8063
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Nov 11 00:19:54 2010 +0000

    nfsrpc: Change log levels for RPC program search messages
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2072 (NFS server crash in __nfs_rpcsvc_program_actor)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2072

commit c364d4114c0f0ec888e03c909266f521dd6dc87c
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 11 01:54:50 2010 +0000

    cli: fix issues with running command over ssh
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2081 (gluster CLI does not work over ssh)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2081

commit b43ef598abec07cff6090dd507419347621b473c
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Nov 12 00:55:02 2010 +0000

    mgmt/glusterd: set the transport type correctly in create volume
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2095 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2095

commit ed8499c728df609a3d09743ee60f85f6ecea9d16
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Nov 12 04:05:22 2010 +0000

    distribute: handle a case of 'local->key' being free'd twice.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2097 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2097

commit 26db1945888a4c85d55c3c5c75beb49e09c19588
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Nov 12 04:15:08 2010 +0000

    Solaris: vasprint fix for %llu crash
    
    vasprint now inturn call gf_vasprintf, which calls vsnprintf.
    vsnprintf allocates buffer of required size, and hence prevents
    the sigsegv seen in vasprintf w.r.t %llu
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1058 (vasprintf dumps core when %llu is involved)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1058

commit 0bd8ecda6554e20336112febf1ade9e1d66bea8e
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Nov 12 04:15:38 2010 +0000

    Solaris: Fix crash seen in rpc_clnt_reconnect
    
    rpc_clnt_set_connected was being called from mgmt_rpc_notify with
    incorrect argument. The crash was only seen on solaris.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2013 (Gluster 3.1 should be supported on the current versions of Solaris and OpenSolaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2013

commit 7b8015edf8ac2fc33e486d2ef66b01c53c200d60
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Nov 10 07:56:45 2010 +0000

    rpcsvc: Fix crash in program search after portmap registration failure
    
    Failure to register with portmap was leaving the registered programs list in
    inconsistent state. This was causing a crash.
    
    portmap registration can fail if there is an NFS server already running.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2072 (NFS server crash in __nfs_rpcsvc_program_actor)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2072

commit 681d7d3aa926e0959ad3f66e53282cb4e55d6202
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 10 02:59:10 2010 +0000

    rpc/rpc-lib: don't build libgfrpc as a module.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1427 (libgfrpc.so is not portable)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1427

commit f406a2e2754a5aa44736f25459e33ef068b6b14a
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Nov 9 06:51:31 2010 +0000

    rpmspec: add glusterfs-core dependency for glusterfs-fuse package
    
    also add dependency for rdma package
    
    Thanks to Bernard Li <bernard@vanhpc.org> for the patch
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2019 (glusterfs-fuse should require glusterfs-core (RPM spec file))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2019

commit eaf0618e47b4e575180a9cbdbeda6ff5995fb144
Author: Anand Avati <avati@gluster.com>
Date:   Tue Nov 9 05:38:12 2010 +0000

    protocol/server: fix log level of message in server-resolver.c
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1092 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1092

commit 6fb49f18a9bbfd1266b4773e757e459519c6719c
Author: Anand Avati <avati@gluster.com>
Date:   Tue Nov 9 05:27:02 2010 +0000

    replicate: optimistic changelog
    
    The standard way of maintaining changelog in replicate has been to
    write out pending flags and to unset the pending flag post the
    actual operation.
    
    This new optimization kicks in only when all subvolumes are up.
    
    The optimization is that, during pre-op, no changelog is written for
    METADATA and ENTRY/RENAME operations. If during the operation nothing
    failed, no changelog is updated in post-op either. If however,
    something does fail during an operation, then, pending flags get
    written during post op pointing only towards the failed nodes.
    
    DATA transactions continue to work the way they are.
    
    If one subvolume is down, pending flags are written in pre-op changelog
    itself as before.
    
    The impact of this optimization is only in the case when both servers
    die or the client dies while the 'FOP' stage of the transaction is
    in progress. By nature of METADATA and ENTRY operations, detecting a
    mismatch later is not dependent on the presence of changelog. Changelog
    only determines the direction in which self-heal happens for these types
    of transactions. For the direction too this optimization does not have
    a major impact because in the cases of failure (both servers dieing or
    client dieing) the final state (direction of self-heal) would be
    arbitrary anyways as the syscall wouldn't have completed.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2068 (performance enhancements)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2068

commit 667c5e22467cbecd371bfc052e7f65b6b6b41e2d
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Nov 9 05:14:22 2010 +0000

    libglusterfs: Memory accounting changes
    
    This patch disables memory accounting by default and provides better
    alignemnt for faster fetch.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2068 (performance enhancements)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2068

commit 16eb9f73a5a7699d5c51d8139b4f1bc77ee3deda
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Nov 9 04:08:33 2010 +0000

    glusterd test-script change in add/remove-brick syntax
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1436 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit 891216e186b436444bc5368a96318df7364ce30a
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Nov 9 03:17:31 2010 +0000

    cli: remove volume type from add-brick and remove-brick cmds
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1983 ("type" in add-brick is completely redundant)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1983

commit 1badd4511f1cd7ea7c3187b121f793cabb414f3a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Nov 9 02:48:31 2010 +0000

    client: Return correct pre/post iatt for dst during rename
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2050 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2050

commit 030393152fe6e7660cc4464be8b65ec1d6ecbbc5
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Nov 9 00:36:24 2010 +0000

    mnt3: Fail mount requests for disallowed clients
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1385 (showmount says no access though it can be mounted.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1385

commit 19aa7b6923f84ffb8a558263e2dede4661862342
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Nov 9 00:05:31 2010 +0000

    rpc-transport/rdma: set the default quota of recv buffers to 128.
    
    - since quota is returned once the reply is recieved, 32 is too less value.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2060 (Infiniteband errors on large file find)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2060

commit 8205e939178ba2253117869024a306442b30d3d1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Nov 8 06:40:21 2010 +0000

    check if the brick being added is the destination brick of replace brick
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2033 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2033

commit e3808ac86f8ff5baebea59e610a791cef5f5f2c9
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Nov 8 06:25:18 2010 +0000

    nfs: Support nfs.port to allow changing nfs port numbers
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1743 (XenServer is not compatible with GlusterNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

commit be5c02a81c19336a6b922b1e1f28293c90955e7f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Nov 8 06:25:17 2010 +0000

    nfs: Use only 38467 as default port instead of 3846[567]
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1743 (XenServer is not compatible with GlusterNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

commit 0f9ec3dec9d51ac5a8f692896d0724b3e87e9ae2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Nov 8 06:25:16 2010 +0000

    nfsrpc: Decouple TCP connections from programs
    
    ..so that multiple programs can be served from the same connection
    or multiple ports can be bound to the same port number.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1743 (XenServer is not compatible with GlusterNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

commit 13c4f8d0f9114a9f8324d0dec8bd926c04a5dfc5
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 8 05:02:06 2010 +0000

    glusterfsd.c: cleanup_and_exit() doesn't call all the 'fini()'
    
    calling 'fini()' of each xlator needs more synchronization work to
    be done. We will be doing a direct 'exit()' as of now.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1879 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1879

commit 96d16edec3dda4cd565b9d4106411c36bebe6dd5
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 8 02:53:16 2010 +0000

    protocol/server: array declarations changed to alloca()
    
    This is to make sure we don't spend CPU cycles in memset(0) on the
    array, instead do a 'alloca()' on size of the request.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit bdfaaf42b643e2e51b85dd9ff5f7da91db3e0710
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Nov 8 00:54:27 2010 +0000

    access-control: Allow Writes/Reads to proceed without perm checks
    
    a. We expect that when the fds are opened through FUSE, thats when the
    perm checks happen, depending on the read/write mode used.
    
    b. In case of nfs clients, we expect the nfs clients to perform the checks
    based on getattr/access nfs requests.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2058 (posix permission compliance error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2058

commit 96f44835ea31b6d432337013b0b70191f6fa903a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Nov 4 02:44:02 2010 +0000

    do not error out if brick count is less than sub count which is valid in the case of replicate
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2054 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2054

commit 7d4b708b7d2180045793677534e9fedd47da794c
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Nov 5 03:54:39 2010 +0000

    fuse: init entry timeout
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2059 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2059

commit 8f16c5ed15e3c0cfbef396c63dbc45778ea84475
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Nov 4 05:11:50 2010 +0000

    Remove the hard-coded thread-count option in volgen
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit 9c4777534bdcce46f2391852933336bc73309f93
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Nov 4 02:34:26 2010 +0000

    rpc-transport/rdma: create request_context only if message contains read chunks or write chunks.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1992 (glusterd crashed while submitting a callback.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1992

commit d19a72024c8cd5e40dc48df27c21fda701e76c54
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Nov 4 02:33:19 2010 +0000

    rpc-transport/rdma: Fix 2KB as threshold size for msgs that can be transferred inline.
    
    - Any fop/mop that can result a reply whose size is greater than this threshold
        allocates and submits a buffer along with the request to receive reply.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 56450b818756a762c925c76f8c6218ea1c5f7efe
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 1 01:25:03 2010 +0000

    rpc-transport/rdma: increment post->ctx.count in a loop doint rdma_read.
    
    - incrementing by the number of read chunks even before doing rdma read will
        cause issues since post->ctx.count is used while posting rdma read.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1877 (data corruption while running arequal.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1877

commit 86a1ef81527da5b9eb11ba3dc361c1c4ca291ca8
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Nov 3 06:35:29 2010 +0000

    nfs: Introduce rpc.register-with-portmap to disable portmap registration
    
    For systems that need to run multiple nfs servers, we need to prevent
    more than one from registering with portmap service. Use this option
    to turn off portmap registration for Gluster NFS.
    
    Portmap registration is on by default.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1743 (XenServer is not compatible with GlusterNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

commit b16c0784da56fc2e7d660753882ec63587e2049e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Nov 3 06:35:28 2010 +0000

    nfs: Remove conn_destroy/init callbacks
    
    NFS is transport-independent, so no point emulating knowledge
    of transportin software.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1743 (XenServer is not compatible with GlusterNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1743

commit d6d7a85487d8ec8017d1d13aa36642ad0355b3e4
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Nov 3 06:35:27 2010 +0000

    nfs3: More robust root gfid checks
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2051 (find fails with loop detected error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2051

commit 5afc77d585c480f185dd7b24b753a6924218bb86
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Nov 3 00:34:10 2010 +0000

    mnt3: Fix UMNTALL crash with Windows clients
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1666 (GlustNFS is incompatible with Windows 7 NFS client.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1666

commit 428b6edc2e141ec701e4a8b0f2964bf251e0014b
Author: Mohammed Junaid Ahmed <junaid@gluster.com>
Date:   Tue Nov 2 05:29:05 2010 +0000

    Throwing an error while mounting glusterfs when fuse is not installed.
    
    Signed-off-by: Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2002 (Mount fails, but gives no error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2002

commit 0fbf226cdeb970f4b5829f92c6d27523f3ef4f04
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Nov 3 05:29:49 2010 +0000

    mgmt/Glusterd: add nfs.enable-ino32 as an option to set from CLI
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1972 (xcs get doesn't work with gNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1972

commit ba1d55c083a39f56077305037de0b619316b2717
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Nov 3 02:13:31 2010 +0000

    Fix DHT getxattr for directories
    
    When a heal on the directory or layout changes, the user xattrs
    do not get healed in dht. The current fix sends the getxattr call
    n all the subvolumes, aggregates it and sends the response
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1991 (distribute directory self-heal does not copy user extended attributes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1991

commit 8ca96737a92a032334b745ffb6f4b872b8359fb0
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Nov 2 04:05:07 2010 +0000

    Cli memory leak fix for tmp_list in cli_cmd_volume_add_brick_parse
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2047 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2047

commit c4ef206dd37a9e6c547caae5bf10b19d336dde8d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Nov 2 00:45:27 2010 +0000

    use uuid_copy instead of memcpy
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 0fe40b1f74a4b070ce2e8928adab52524b86e273
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Nov 2 01:39:00 2010 +0000

    Fix crash while freeing tmp_list in cli_cmd_volume_create_parse
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2047 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2047

commit 33ce70b6fb7f3e268bcb166477c1e79e19b48a11
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Nov 2 01:27:56 2010 +0000

    socket: avoid check on lowlat for enabling nodelay
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2040 (Using 'du' and 'ls' command, it got slow performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2040

commit de001e8659d78dd16ba8515228c70fd2986e56df
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Oct 30 13:09:08 2010 +0000

    cli: Fix memory leaks
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1198 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1198

commit 961d5fb6025f4901d63be8cfc8062bd8e2093021
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Oct 30 12:11:36 2010 +0000

    mgmt/glusterd: Honor log filename set during add-brick
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2042 (No volume log files found in the specified directory for the newly added bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2042

commit 586000144be8919a234939ad43b04394d5f2636e
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Oct 29 07:03:38 2010 +0000

    mgmt/glusterd: Start nfs before killing source brick in replace brick commit.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 1b4613936e2d176df8e5a8548af2d59116bd9531
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Oct 29 07:23:54 2010 +0000

    copy the gfid of root to the iatt structure of root
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit c65be2d304c67e57447d6d4a2e53fae07e31ff5c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 29 05:38:13 2010 +0000

    nfs: Introduce nfs.enable-ino32 to support legacy 32-bit only apps
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1972 (xcs get doesn't work with gNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1972

commit 413b2a5f9b77fd3d7f3b26c848482ec7b914102f
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 29 04:32:18 2010 +0000

    protocol/client: add check for changed gfids to fail revalidates
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit ffbe9470cd189b7921509c08c9b2d308b8ac390e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 29 03:13:22 2010 +0000

    rpc-transport: fix race-condition between rdma-read completion and updating the count of number of vectors to be passed to rpc.
    
    - If rdma read completes before incrementing the vector count, the count
        value sent to rpc will be improper. For fops like write, this may result
        in missing out a vector to be written, thereby causing data corruption.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1877 (data corruption while running arequal.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1877

commit 9c29312628af743f16badb4bc820cbd31f2a9488
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Oct 29 03:39:56 2010 +0000

    cli,mgmt/glusterd: fsm log implementation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1966 (Unnecessarily verbose logs at the default log level)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1966

commit c1b80f0f590e2d7448b890b57e80f4a1b2e39a03
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Fri Oct 29 03:32:44 2010 -0700

    Revert "rpc-transport/rdma: create request_context only if message contains read chunks or write chunks."
    
    This reverts commit b66f4598f4dafb6479232b20c5c521ab0da4e84a.

commit 8ea6882c424afd3f18ad1273ec31d34f5d74e47e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Oct 28 07:02:44 2010 +0000

    script for testing glusterd sanity
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1436 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit d654c29d20f24802e6c5aa24a9206377428b9359
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Oct 28 13:15:54 2010 +0000

    performance/quick-read: white space cleanup
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2027 (Updates not happening with replication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2027

commit 82ad7b3be8478628ef448c97a702f4c6f1298329
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Oct 28 13:15:26 2010 +0000

    performance/quick-read: set right validation checks
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2027 (Updates not happening with replication)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2027

commit d615015ef4707d0df476547cbf7b6f83a29d804b
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 28 00:52:50 2010 +0000

    replicate: attempt re-open of files before performing openfd selfheal
    
    in cases where subvolume state gets swapped between open and write
    opening file on the remaining subvolumes is necessary before attempting
    a self-heal. previously files were opened after self heal.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 918 (AFR write fails when subvolumes' state is swapped)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=918

commit 00b0a53bae2a5e39f197359581a3850a32970e54
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 28 00:52:30 2010 +0000

    replicate: fix hang/missing frame during locking
    
    nonblocking style locking would result in a missing frame when all
    subvolumes are down or when no subvolume on which fd was opened
    is up. Check for this condition and unlock gracefully
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 918 (AFR write fails when subvolumes' state is swapped)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=918

commit 87c0e8fba2d0be4496ec4085136fca459f62c00c
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Oct 27 23:57:55 2010 +0000

    Solaris build fixes: Patch for 64bit build
    
    This will fix build failures when -m64 option is used to build
    gluster
    
    Signed-off-by: Super-User <root@Solaris-10.(none)>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1990 (Gluster mainline build on solaris fails with errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1990

commit e93b270e8d09fc9d36a39b22987d3a172197e73b
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Oct 27 10:33:23 2010 +0000

    cli: gluster --version implementation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2006 (Add gluster version command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2006

commit b2f195720b27d9e69f7b851478515781e5786469
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 27 05:36:32 2010 +0000

    socket: Reduce keepalive idle and interval time
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1956 (NFS client hangs after failover)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1956

commit 6ac081eccaa4f034874aa6687d87fb8b30207ebf
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Oct 8 01:49:25 2010 +0000

    Remove libglusterfsclient option from gld-dm benchmarking tool
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 968 (gluster client encountered out of memory very quickly when running glfs-bm)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=968

commit 7efad96683f605d5a0eb21b0377a6e14b89cd910
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Oct 27 05:10:19 2010 +0000

    mgmt/glusterd: update brick-count as soon as it is added in add-brick
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2023 (add-brick fails in regression)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2023

commit 0e1bead7b77adab9115b2af977bc78273a34a70d
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Oct 27 04:55:03 2010 +0000

    mgmt/glusterd: glusterd_is_local_addr implementation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1855 (Initial server in a cluster not a friend)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1855

commit e4a43cf475f5a2d908cffdb518028ba74dc9f8b1
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 21 04:51:47 2010 +0000

    added a test script to test rpc procedures
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 1bafcd847a2bdaea7aebdb212bbb480eaeee7ede
Author: Csaba Henk <csaba@lowlife.hu>
Date:   Wed Oct 27 04:33:15 2010 +0000

    libglusterfs: fix buffer overflow in gf_string2int()
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2022 (gf_string2int() overflows target pointer)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2022

commit 38c91384861f29f97c3f564a36ee799f1eb57cc1
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 27 03:07:29 2010 +0000

    mgmt/glusterd: Unlock upon a cli request failure
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1873 (Stop volume gluster command execution failed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1873

commit c02cd37866ae22e3a433d737f3c80395bb72f002
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Oct 6 05:23:44 2010 +0000

    distribute: bring in statfs normalization
    
    We had normalization of statvfs structure in 'cluster/unify' translator,
    with distribute, we had this section as 'TODO:'. Now, the same code is
    migrated to distribute.
    
    Thanks to <marty.rosenberg@gmail.com> for sending the patches
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1035 (The distribute translator does not handle differently sized block sizes and/or fragment sizes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1035

commit 40dd9e9e18c5de009baf9e437d3222fa6b473237
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Oct 9 07:34:52 2010 +0000

    log locate should check if the export directory is valid
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1871 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1871

commit 78bccc25b7c1b54c46c6aab9e34c7c455486d1fd
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Oct 8 07:36:55 2010 +0000

    fuse: retire the faked-FLUSH-upon-RELEASE hack
    
    Now the code has lived up to the glorious state of not relying
    on getting the FLUSH whenever a file is released. So we don't need
    to forge one in release for the cases when the kernel doesn't send
    it.
    
    Undo commits:
    - 155ffe5c
    - c50bc710
    - b8779318 (partly, just release related parts)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 223 (flush not sent)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=223

commit a7d41a64fb11451e622db19813738c3ee3942c92
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Oct 26 05:20:34 2010 +0000

    report the error if a volume not in the started state is tried to be stopped
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 2010 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2010

commit a53d14d5f5be431279c5e56963b495bf164cf453
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Oct 26 04:00:30 2010 +0000

    volgen: macro cleanup
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit db94ed06a688fb596aba4deafdf59a5af2fd6bbe
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Oct 26 04:00:29 2010 +0000

    libglusterfs, glusterfsd: add shortname resolution + optname hinting support to VOLUME SET
    
    Trie code used for hinting is contributed by Avati.
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 9f14b0a0ef26b6d41b61222dcf34fe7cdf46cb46
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Oct 26 04:00:28 2010 +0000

    libglusterfs: fix graph mem types
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 3b70ff915a7451911dd35733171b97d7073df2c4
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Tue Oct 26 03:58:59 2010 +0000

    glusterd-volgen: Fix division by zero clang warning.
    
    Also clean up surrounding calculations a little bit.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1089 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1089

commit 1a2463cefac2cd9faf80ce7041b2fa1d9cfff36c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Oct 26 06:39:08 2010 +0000

    nfs3: Translate ENOTCONN into IO error for client
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1923 (Unknown error 526 when one of the subvolumes for distribute is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1923

commit 29dc176fa7832699b34a3a3e2f1a5f14ae55274a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Oct 26 06:39:07 2010 +0000

    nfs-rpc: Fix log message for unsupported program
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1973 (Unnecessary log message "RPC program not available")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1973

commit bd890a0f53142e60e70e6cad8363738d607fbdb4
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Oct 26 06:39:06 2010 +0000

    core: Use lru_limit as count for inode and dentry mempool
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1948 (For each subvolume started, glusterfs process takes up around 30-35MB more memory)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1948

commit c9c411b48aa0477cd44c18cbdf83d14389d27221
Author: noah williamsson <noah.williamsson@gmail.com>
Date:   Mon Sep 27 07:47:11 2010 +0000

    OS X: fnctl() flag FNM_EXTMATCH is not supported under Mac OS X
    
    Signed-off-by: Noah Williamsson <noah.williamsson@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 7ca61c1082b6c7554ea7b615ca3f2d3c8ab4b090
Author: noah williamsson <noah.williamsson@gmail.com>
Date:   Mon Sep 27 07:47:10 2010 +0000

    OS X: Include rpc/types.h
    
    Signed-off-by: Noah Williamsson <noah.williamsson@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit d6a34a08d5a583c4f0f2264511286ed39a071e1b
Author: noah williamsson <noah.williamsson@gmail.com>
Date:   Mon Sep 27 07:43:49 2010 +0000

    Correct enum declaration of gf_dump_procnum, fixing duplicate symbol error when linking on Mac OS X
    
    Signed-off-by: Noah Williamsson <noah.williamsson@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 9272cce5feb55c6526078f2d1440bb0d0591d651
Author: Csaba Henk <csaba@lowlife.hu>
Date:   Tue Oct 26 03:56:32 2010 +0000

    fuse: "terminating upon EBADF" log message is confusing, set its level to DEBUG
    
    Signed-off-by: Csaba Henk <csaba@lowlife.hu>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1887 (logging mess)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1887

commit 81e718ab513e2cdf1b1e22b268c5798752d79cc1
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 9 15:46:40 2010 +0000

    server: parse more precisely when validating auth options
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1885 (auth validator in server parses too sloppily)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1885

commit b66f4598f4dafb6479232b20c5c521ab0da4e84a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Oct 24 23:44:34 2010 +0000

    rpc-transport/rdma: create request_context only if message contains read chunks or write chunks.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1992 (glusterd crashed while submitting a callback.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1992

commit 7c479d61681d3ddb7fcc325752384eac89ae809d
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 21 02:25:49 2010 +0000

    rpcsvc: handle NULL deref in case of program mismatch
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1982 (rpc: crash on progver mismatch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1982

commit 93de6e1f8106220d1c41f2ca9fdc207c76dd0560
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Oct 14 05:56:53 2010 +0000

    NULL checks in the fops of io-cache
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1757 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1757

commit 29377452062b07b6487105ebe65a717898e19e2a
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 14 05:12:12 2010 +0000

    io-stats: handle the case of 'cleanup_and_exit()' properly
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1933 (Segfault while expansion of volume from distributed mirror)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1933

commit 0d11145c0c2a9bac61398bff2fbab14820f0764a
Author: Mohammed Junaid <junaid@gluster.com>
Date:   Thu Oct 14 04:14:47 2010 +0000

    takes either 'y' or 'yes' and 'n' or 'no' for stop volume, delete volume and remove-brick
    
    Signed-off-by: Mohammed Junaid <junaid@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1942 (cli: loose parsing of confirmation answer)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1942

commit 2ec661c0729370f0acd966fab0ae644f7e62bd71
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 13 04:09:15 2010 +0000

    extras: Do not check_config() for glusterd in Debian init
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 681bfd7ff32202314a5cdf8a8e13478c6c45acdb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 13 01:38:20 2010 +0000

    server: Don't free conf in fini.
    
    - This will fix race condition between handling DISCONNECT event and doing
        fini. Though conf need to be freed, this will be done in future where
        finis of all translators are properly implemented to make sure no
        corruptions.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1758 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1758

commit a8212606e23312fabd5c2068ade05efacae9c086
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Oct 12 04:13:19 2010 +0000

    rpc-transport/rdma: associate mem-pools with device instead of transport.
    
    - this will help to reduce memory usage of glusterfs process.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 959f051b0c39f114d54b5bb303dd2241603d7607
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 13 03:05:09 2010 +0000

    Correct location of git repository
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1941 (wrong git url)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1941

commit 5ca019f339d76187f26757222084319cd1b28ad6
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Oct 19 03:02:10 2010 +0000

    Propogate rebalance already started error to cli
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1882 (starting rebalance while previous rebalance is still running)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1882

commit 54219ecf2ad344a55e974ff4b86a02408c9c17f2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Oct 25 00:11:51 2010 +0000

    xlator.c/option-validation: change the log level to warning when given value is out of range.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1214 (When cache-size is given out of range, error is logged but GlusterFS starts)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1214

commit 1e1f97a89cdd454bcfbf158ae7520932bacb1aa1
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 14 02:34:31 2010 +0000

    client: move reopen{,dir} code to handshake file
    
    and minor log level changes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 44b27f7ec27173c5d12c12aa3947cc1f409d8c1f
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 14 02:34:01 2010 +0000

    client: decrement the 'openfd' count in case of opendir_cbk too
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 14d2ed37a966a10d8553e8b5a5283d35f9addc7e
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 18 04:22:47 2010 +0000

    server: print information about disconnected client
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 41b14258c08a0065c573a2ec9f39fb3354fd9be3
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Oct 18 05:02:11 2010 +0000

    debug/io-stats: init() should also set loglevel
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit cfad660310978ffda6263d44ab2445d42c2621b2
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Oct 18 08:15:30 2010 +0000

    Log level mess clean up
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1886 (log-level mess)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1886

commit f014877f37488d6f9d4c505f0675ad45cd770546
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Oct 19 07:50:05 2010 +0000

    Remove additional failure cli msg for peer detach
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1955 (Redundant log messages when "peer detach" fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1955

commit a9187b9609dacb017aff171c317cd5332ef64bd5
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Oct 20 01:20:59 2010 +0000

    mgmt/glusterd: resolve the bricks before comparing uuid
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1985 (peer detach fails if bricks are not resolved)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1985

commit db61075a123008ebd94ab8ff00b984e484155654
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Oct 21 03:38:30 2010 +0000

    Solaris build: Fix linux only features
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1990 (Gluster mainline build on solaris fails with errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1990

commit cd9a247906924106c722ecf4611b7be4b5408ad9
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Oct 21 03:37:52 2010 +0000

    Solaris build: Handle namespace clash for rpc-clnt.h
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1990 (Gluster mainline build on solaris fails with errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1990

commit f3737b2ee75bda6cd05744f2fbd13cb92ecab655
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Oct 21 03:37:27 2010 +0000

    Solaris build: Remove sigtimewaitd
    
    This part of code was stale as a result of fixes for volume start force
    changes. Removing the unwanted code
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1990 (Gluster mainline build on solaris fails with errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1990

commit 559055ebfebe8d58c8607c521661c1f1c1d3a2d5
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 21 04:06:49 2010 +0000

    nfs3: Correctly funge solaris root lookup FH for DVM
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1997 (Solaris mount fails with "RPC program not registered")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1997

commit 46b7ce29e1b300044e03841a1a70325f190416c1
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 21 04:06:48 2010 +0000

    nfs: Fix volume-id option declaration
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1972 (xcs get doesn't work with gNFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1972

commit 8ce807dd811e32b704a7beec1bbbcbb2625a7219
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Oct 21 04:33:44 2010 +0000

    do not hardcode the replace brick remote port to 34034
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1998 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1998

commit 51ddf878b1d74369434c6b95b49a76bce32fd4b1
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Oct 13 00:12:49 2010 +0000

    glusterd-rebalance: if file is open, don't do rebalance
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1934 (Server segfault with 3.1 platform ISO during volume expansion)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1934

commit e788e2dec0c90c77a88b561636df569d94c8e638
Author: Vijay Bellur <vijay@dev.gluster.com>
Date:   Tue Oct 19 06:20:24 2010 -0700

    Revert "glusterd-rebalance: if file is open, don't do rebalance"
    
    This reverts commit 6e6b4b4fd002347ca08691f73e10b961f693d754.

commit 6e6b4b4fd002347ca08691f73e10b961f693d754
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Oct 12 04:09:35 2010 +0000

    glusterd-rebalance: if file is open, don't do rebalance
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit b9d6e0c879feb9d86cdadf4072a7ebeb5eb29798
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Oct 12 03:54:31 2010 +0000

    rpc-transport/socket: initialize fragcurrent pointer in correct state while reading vectored replies.
    
    - If fragcurrent is initialized in the same state which reads payload data,
       there is a possibility of it getting reset during partial reads from socket.
       Hence it should be initialized just before entering the state which reads
       payload data.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1929 (different value is logged for read header size for multiple reads)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1929

commit a6304aec8c366ad7853f95348aa6c73a0b873678
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Oct 12 03:08:46 2010 +0000

    mgmt/glusterd: create brick path if does not exist
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 9bad9d59f0f19fe20f90c6ed80e25c7db08b3371
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Oct 12 03:06:30 2010 +0000

    Change assert to GF_ASSERT
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit f637330995eab92a1d0b9f4ad9c43acfaad35037
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Oct 12 02:21:16 2010 +0000

    rpcsvc: calculate dump response length instead of hard coding it.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 15c9f6789fe41afdda12052c9ce6d538e0c2f5e6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Oct 12 02:26:34 2010 +0000

    rpc-transport/rdma: by default use infiniband port 1
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit ed4975b13db3220d461b8ea2a764efd6572e156a
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 12 02:25:46 2010 +0000

    nfs: avoid assignment of structure pointer into serialized buffer
    
    With the introduction of variable sized file handle feature in NFS,
    on-wire lengths of file handles can be lesser than file handle structure
    of code. Direct pointer assignment into the offsetted buffer and
    dereference and result in reads beyond the end of buffer and crashes.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 999 (Crash in nfs3_fh_resolve_and_resume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=999

commit 48672d26a01f3ce443479b19820e2822a6c650f6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Oct 8 00:25:30 2010 +0000

    check if fd is NULL before accessing it in fuse_open_resume
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1858 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1858

commit fab78b45f7e99ea2e41a4ef3603a56e9eac5b776
Author: Harshavardhana <harsha@gluster.com>
Date:   Fri Oct 8 17:43:36 2010 +0000

    Add mount.glusterfs to fuse since its only needed for native client
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1770 (Cleanup rpmbuild)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1770

commit 161850285ff06e90f2c990989bab9513dd4a4289
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 12 01:22:28 2010 +0000

    nfs: re-implement logic to perform fresh lookups when lookup revalidates fail
    
    - implement lookup to pass via inode layer so that looked up entries make it to inode cache
    - implement lookup revalidation failure check in the fop layer
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit efa94a4237bc98c629671e6fbb58948789604fe5
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 12 01:22:11 2010 +0000

    Revert "nfs3: Revalidate inode on receiving ESTALE on lookup"
    
    This reverts commit f5afcc47f9f00472d6c2b3f48127e02332cd457a.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit c3b6df1a8e27c66a5c17cc1d6a92fdc37354ae6f
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 12 01:21:51 2010 +0000

    protocol/client: prevent propagation of CHILD_DOWN after pmap query
    
    pmap query results in a new port to which the rpc client reconnects.
    This involves disconnection of current connection to pmap which was
    propagating CHILD_DOWN upwards prematurely
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit 91580140b3df01838c5c5a6dac301efb87c4bd93
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 12 01:21:32 2010 +0000

    protocol/server: be consistent in setting rsp.dict_len and rsp.dict
    
    in cases where op_ret was -1 and dict was not NULL, the code was
    setting a dictionary length but not the serialized dictionary. This
    would cause crashes in the xdr serialization function
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit 2478d21c8d7c0e4d66990f7da7323f2c750a9d82
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Oct 11 15:17:18 2010 +0000

    unwind if layout is NULL in getxattr for dht
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1917 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1917

commit f182151cf338cad36d1d503f33b65ca40785b797
Author: Vijay Bellur <vijay@dev.gluster.com>
Date:   Mon Oct 11 12:32:04 2010 -0700

    Revert "nfs: re-implement logic to perform fresh lookups when lookup revalidates fail"
    
    This reverts commit 563ef3d12f8d7a927b403d04c279d9fc702faad0.

commit 61308de7645f1df462bef50e9c22237899218c65
Author: Vijay Bellur <vijay@dev.gluster.com>
Date:   Mon Oct 11 12:31:26 2010 -0700

    Revert "Revert "nfs3: Revalidate inode on receiving ESTALE on lookup""
    
    This reverts commit 6dd3b7fa3bc7acf9281cc17f08010675e2297089.

commit d31e97336aac057510203f0942856b66baf4a91b
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Oct 11 12:13:51 2010 +0000

    mgmt/Glusterd: fixes in volume reset
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit 27c8b7a36972db1a80d51764f9dfc6d3deb10a80
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Oct 11 09:13:27 2010 +0000

    Remove references to COPYING.* files
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit d6978803395fb1d1635dd454894e26d9feb806d9
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 11 07:30:55 2010 +0000

    dht: change behaviour CHILD_UP/DOWN/CONNECTING event propagation
    
    The first CHILD_UP/DOWN/CONNECTING event to pass dht upwards should be only after
    all subvols have reported their status atleast once.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1643 (Initial requests after mount ESTALE if DHT subvolumes connect after nfs startup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1643

commit 4868116c1ca08868abe69c271dc108f1d0b5a227
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 11 07:30:30 2010 +0000

    Revert "distribute: Propagate CHILD-UP when all subvols are up"
    
    This reverts commit 6b2e2fb0903fc56105c267881f202a4865a8b6c7.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1643 (Initial requests after mount ESTALE if DHT subvolumes connect after nfs startup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1643

commit 563ef3d12f8d7a927b403d04c279d9fc702faad0
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 11 06:43:35 2010 +0000

    nfs: re-implement logic to perform fresh lookups when lookup revalidates fail
    
    - implement lookup to pass via inode layer so that looked up entries make it to inode cache
    - implement lookup revalidation failure check in the fop layer
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit 6dd3b7fa3bc7acf9281cc17f08010675e2297089
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 11 06:42:39 2010 +0000

    Revert "nfs3: Revalidate inode on receiving ESTALE on lookup"
    
    This reverts commit f5afcc47f9f00472d6c2b3f48127e02332cd457a.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit bf68324270f7e15f140ccb74ab355f8179cce92f
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Oct 11 06:42:32 2010 +0000

    Set correct logging level for log messages
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1887 (logging mess)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1887

commit 47a87215e30d3ea2dc6ec9ae178f5a9e3eae9e96
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Oct 11 06:03:40 2010 +0000

    features/locks: free fdctx in release.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1438 (memory leaks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1438

commit 2854c559340d33473750fac65aace58506951276
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Oct 11 08:38:19 2010 +0000

    Copyright changes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 5d4800fa35d3a9ca08175fe2bbdd78c2b0b5e184
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Oct 11 06:18:07 2010 +0000

    Do graph init after topology change
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit ab42cb8d75985e33fb27e9fc5da0bc37c1024804
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 11 00:04:57 2010 +0000

    fuse_loc_fill(): handle a case of NULL dereference
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1889 (gluster FUSE client crashes on irregularity)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1889

commit 74dabe95193a0bc76c3ba149431a9110149a8e9e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Oct 11 04:28:30 2010 +0000

    get the remote-host option from the dictionary in reconfigure
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1898 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1898

commit 81b6fa2b813d6913dd6329ef6a463669d282ebb6
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Oct 11 03:49:45 2010 +0000

    Add log-level validation for volume set command
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1886 (log-level mess)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1886

commit 3dc782527482d2c62c9344669ccaa2dc42481a58
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Oct 11 03:26:00 2010 +0000

    mgmt/glusterd: handle reqs from unknown peers for friend sm
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1838 (handle peer detach gracefully in case of lost frames)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1838

commit eb99bee0246d5a43bbee7383b3809a360aa70018
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Oct 11 02:23:18 2010 +0000

    Add confirmation to volume delete command
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 2eb9861cbc0387b1054bfeb7864c255a42b475f5
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sat Oct 9 06:58:00 2010 +0000

    mgmt/Glusterd: Memory leak fixes, minor CLI changes
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1852 (Usage message of volume set printed twice)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1852

commit afb6997fe74af257c7e687e33fe88a292f7a4a00
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Oct 8 09:52:52 2010 +0000

    io-stats, volgen: make the distinction between client and brick loglevel in volgen's scope
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1789 (add log-level options to volume set)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1789

commit d1f938c16e309431382ab9aaa32d50bf0ccd3260
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 8 20:21:59 2010 +0000

    rpc-transport/rdma: fix the bug which was causing an ioq-entry being mem_put twice.
    
    - in case of failure to send message, ioq-entry would be freed, but it used to
        get added to the ioq-list. Failure in sending a message (for reasons
        other than insufficient quota), would result in transport being
        disconnected. In the process of handling pollerr, when ioq-list is flushed,
        the same ioq-entry which would've already been freed, would be freed for
        second time.
      - this patch also fixes spurious disconnects happening when quota was not
        available while sending a request.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1854 (GlusterFS 3.1 beta crashes over Infiniband with rdma issue)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1854

commit 0ccb63dbc52f66975205baf8452d2b57418da4aa
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Oct 9 07:41:14 2010 +0000

    set keepalive for client connections
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1802 (Gluster volume creation failed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1802

commit 13f1fff6da4b2b9ee30f43346cb382abfc1bc304
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Fri Oct 8 10:34:18 2010 +0000

    mgmt/Glusterd : Volume info fixes
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1872 (gluster volume info is not working with qa42-)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1872

commit e0cdcbf68ab1dc1cc1af874cd84579d89a3e3747
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Oct 8 10:17:55 2010 +0000

    rpc-clnt: do rpc_transport_destroy() in rpc_clnt_destroy()
    
    handles the case of peer detach properly
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit cd5c9df4b67073089a5502d5e4c2e2e7d2141e4a
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Oct 8 07:06:57 2010 +0000

    mgmt/glusterd: Fix replace brick to pass src-brick and dst-brick port nos properly.
    
    Fix also contains patch from shishir ng for maintaining replace-brick
    states in glusterd.
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 09914c02f24b4cc74cb6aad9994ae590cf8b76bf
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 8 07:01:42 2010 +0000

    rpc/clnt: allocate a new cbk_program before registering it.
    
    - Refer Bug 1836 for more details.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1862 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1862

commit 2e43696eb90dc835d0aa8000e19b6f207760309c
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Oct 8 06:58:51 2010 +0000

    migrate from port 69* to 24007
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1870 (Change the port from 69* to some other ports.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1870

commit 98e1ea0f178bdb8d26037edda9aae7bc2339bac4
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Oct 7 03:20:59 2010 +0000

    Possible race condition between cleanup and dereferencing
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1760 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1760

commit d4b0360c8c4c5dab692f827972ccea0e728af688
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Oct 8 01:37:54 2010 +0000

    mgmt/glusterd: memory leak fixes
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit ce616c5fa08722044ee311f5f6c7c4e3ccb684c4
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Oct 8 00:19:17 2010 +0000

    mgmt/glusterd: print state, event names for numbers in friend sm
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1847 (print event names, state names instead of numbers for FSMs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1847

commit 99b04920189df06cfd8704a773c51cdb995b7ae0
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Oct 8 04:54:36 2010 +0000

    support for configuring keepalive idle time
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1802 (Gluster volume creation failed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1802

commit 95d595d9cbe727401021cf1caf0d59b3ab12d454
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Oct 7 10:15:18 2010 +0000

    mgmt/glusterd: Always kill nfs with SIGKILL
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1853 (kill nfs process with SIGKILL while restarting)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1853

commit e7178b0646d1542faea6d6acab0291ca0d176b35
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Oct 7 07:26:14 2010 +0000

    Glusterfsd Crash in server_link_cbk
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit c7b518ab85f6fbcbdbae64c8fa092e998a14d1e9
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Oct 7 06:37:12 2010 +0000

    mgmt/Glusterd: Volume set enhancements
    
    - performance.flush-behind, transport.keepalive added
    - volume info to display the options reconfigured
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit f62484f42230db9d240c9b0eaadac48d845053b1
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Oct 7 04:41:28 2010 +0000

    mgmt/glusterd: Change event, state numbers to names for op-sm
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1847 (print event names, state names instead of numbers for FSMs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1847

commit 5979bc3b964adcb8a536dc354e4eca08acaff03e
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Oct 7 05:56:22 2010 +0000

    protocol/rpc/transport: bring in one more event for 'TRANSPORT-DESTROY'
    
    needed because, a RPC disconnect doesn't mean that a RPC transport/listener
    is dead. With this, the race in server protocol cleaning up the lock table /
    fd table when some frames are in transit will be handled properly.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1843 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1843

commit 3c0a7fb86eef1eecada77a6f040f96e1fd9e0536
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 7 05:50:53 2010 +0000

    nfs3: Fix gfid to ino conversion
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1724 (kernel untar fails during add-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1724

commit 58ce5f46af7e08db3d786c597ec5144294fbd099
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 7 05:23:59 2010 +0000

    nfs: Revert downed-subvolume changes
    
    For the record these are the patches committed as:
    
    1. "nfs, nfs3: Base volume access on CHILD-UP-DOWN event"
    http://git.gluster.com/?p=glusterfs.git;a=commit;h=f47b0c55de9941823fbefe4b3a7e37179d6d4329
    
    2. "nfs: Fix multiple subvolume CHILD-UP support"
    http://git.gluster.com/?p=glusterfs.git;a=commit;h=336e2df7b74be7ad4c9ed403ca10b9f7f7ef9a58
    
    3. "nfs,nfs3: Disable subvolume on ENOTCONN"
    http://git.gluster.com/?p=glusterfs.git;a=commit;h=8c6e27cdaf895e3031c3256efb9472a6c0bf61f3
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1724 (kernel untar fails during add-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1724

commit 32b62dd42fc479d19211a3c223b665d28d2207f2
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 7 05:58:06 2010 +0000

    lock recovery: temporarily disable lock healing
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 0c0c82729b947256beefcd3999d230302faef1fd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 6 08:00:18 2010 +0000

    rpcsvc: allocate a new program structure before registering it.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1836 (server is hung in infinite loop while trying to search for an actor during request processing)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1836

commit 96155f065e229f6123cc90b9ca37df9cbd7598c7
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Oct 6 04:44:14 2010 +0000

    transport: set 'trans->options' before calling 'trans->init()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 7c7cf68b798ac6ff1d4727c288cdcba15589e456
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Oct 6 07:32:07 2010 +0000

    changes for the sanity script
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1436 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit 4880761284daf6da623322e1d3f7152486c5770f
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Oct 6 02:04:01 2010 +0000

    mgmt/glusterd: set the return value in case of failure
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1823 (add-brick fails first time but works in next attempt)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1823

commit 05727129fd08e237d2b4f5daf4726438ebc6efb6
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Oct 5 08:02:41 2010 +0000

    mgmt/glusterd: dont access req after reply
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit ef13a1046f72c993b8e053e5fc5f671e9bd2579b
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Oct 5 07:48:21 2010 +0000

    cli: fix Number of bricks output
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1815 (gluster volume info - Number of Bricks field)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1815

commit 4c7ca7ec15760681703450dc9279a8c3cf8b98c0
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Oct 5 07:34:45 2010 +0000

    mgmt/glusterd: send volume options to friend
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1816 (send volume options in friend add)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1816

commit 6b74f3ec7b6e0fed2e253df456b067fc27049117
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Oct 5 07:02:07 2010 +0000

    Reply back to CLI on error, by validating each xlator's opts
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit 7aec50bdad06665243a16f1ce83a03037bcd5d56
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Tue Oct 5 07:01:52 2010 +0000

    mgmt/Glusterd : Reply to CLI error: graph construction
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit 79db3aced2ffca84a696192343d5b811833eb671
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Oct 5 06:40:32 2010 +0000

    features/locks: Handle lock upgrade and downgrade properly in locks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Pavan Vilas Sondur <pavan@dev.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1017 (Locking deadlock when upgrading lock)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1017

commit 99ac72b988f0ccd0bf876cf3e2326b8406f71461
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 5 05:07:37 2010 +0000

    replicate: use the new rmdir prototype for cleaner entry self-healing
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1761 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1761

commit f62ff8a8df7ab7c0c551b650f9bd2f1a87b8dc71
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Oct 5 04:48:27 2010 +0000

    features/locks: cluster/afr: Misc fixes for lock recovery.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 79342c436fb994e6a41e3c7b69c962af37e8946a
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Oct 5 03:50:06 2010 +0000

    glusterfsd: '-f' option help update
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1809 (glusterd help text for -f is wrong)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1809

commit b5c5a7fa141e77a5d688647c753b2d59d6330f83
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Oct 5 03:49:39 2010 +0000

    rpm spec file: add proper Obselete keys
    
    Thanks to Bernard Li <bernard@vanhpc.org>
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1808 (Allow RPM upgrade from glusterfs 3.0.x to 3.1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1808

commit fe2777ccaff5d2660af65472962bbef8d10b1814
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Oct 5 01:58:46 2010 +0000

    nfs3: Convert gfid to ino only for non-root
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1724 (kernel untar fails during add-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1724

commit 25c2e7e18a07f76a8e2168eb9c3d8f87c558069e
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Oct 5 00:24:40 2010 +0000

    Do not exit to shell after gluster help if readline mode is not enabled
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1709 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1709

commit 3f89342de32f214cdb9d641c402954ae9345af71
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Oct 4 17:57:59 2010 +0000

    volgen: add interface to complete option names from specifier (after-dot) part
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 6658fdde8f6e328e232d9d40067df8ae4b16e8b2
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 22:15:57 2010 +0000

    distribute: check for 'conf' before dereferencing it
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1806 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1806

commit 372ed08f25da2eb7e09f27685cb1773b88c62173
Author: Harshavardhana <harsha@gluster.com>
Date:   Mon Oct 4 17:54:12 2010 +0000

    init.d: Path not resolved during compilation to actual prefix
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1810 (qa 40 glusterd path is hardcoded, won't start by default.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1810

commit 2136876274690bc7377b97ca0ed812a6befafee2
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 13:51:29 2010 +0000

    glusterd: more sanity checks during restart
    
    * check for validity of pid file before doing pmap search, as in
      few cases, pmap_signin() may take more time.
    * remove stale code from 'init()'
    * update pmap->last_alloc during restore itself to handle glusterd
      restarts more agnostics to port collisions
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 0d31e7e4239d4765198ea6f46b98ba680038f7ad
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 13:28:00 2010 +0000

    fuse: handle the case of NULL dereference
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1798 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1798

commit 4c28d069b5be71bb2136d85e7a9b9fe0d07e04a1
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 13:27:43 2010 +0000

    glusterd-volgen: fix the auth.allow/auth.reject keys
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1798 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1798

commit dc1113c4a02b1b1186bf37e09685631891d85537
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Oct 4 12:15:34 2010 +0000

    cli: mgmt/glusterd: Add commit force op to replace-brick
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 841ee8d5021980d836c834792b581475b05b0e6b
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Oct 4 11:24:43 2010 +0000

    volgen: revise option list for VOLUME SET
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit ca8615173f495a906520c3a1b238ed8266a932bf
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Oct 4 11:20:38 2010 +0000

    mgmt/glusterd: dont change ret val in cmd handlers if fails
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit 846383acb963b9c74a386192bb5050a9366a8036
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Oct 4 11:19:23 2010 +0000

    mgmt/glusterd: cleanup during detach
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1765 (peer probe  on removed-detached bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1765

commit bde5cb81e251032594e2bba57fb4a72c10e32207
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 11:01:14 2010 +0000

    rpc: don't refer to 'req' after calling 'prog->actor()'
    
    there are chances that a error reply is sent to client from actor,
    in which case, 'req' would be free'd and accessing it would result
    in error.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1790 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1790

commit 98d51842863d52bab2674258c3ec12d668139539
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Oct 4 10:59:08 2010 +0000

    initialize the list earlier while handling create volume and add brick
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit b6fea1abc756c31d93244263a654b56f2f8b7894
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Oct 4 10:06:08 2010 +0000

    nfs3: Convert gfid into inode number
    
    ..avoids stale file handle errors at the client when client detects
    changing inode numbers from the server.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1724 (kernel untar fails during add-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1724

commit 8c6e27cdaf895e3031c3256efb9472a6c0bf61f3
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Oct 4 10:06:07 2010 +0000

    nfs,nfs3: Disable subvolume on ENOTCONN
    
    ..so that nfs does not return an error to the client, instead
    the subvolume gets disabled till it comes back up again.
    
    The client is expected to keep retransmitting requests in the mean time.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1724 (kernel untar fails during add-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1724

commit 64609b65c2ffc34577b342dab12595b13a52d8a2
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Oct 4 08:54:55 2010 +0000

    mgmt/glusterd: added new brick validation functionality
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit 85c013f3accfc409c1a520d0ad529a2c1c16c653
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Oct 4 08:44:11 2010 +0000

    Change GNU GPL to GNU AGPL
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1388 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1388

commit 6a244f2e95b09603507782061ac08b7e0c28fd64
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Oct 4 08:18:19 2010 +0000

    cluster/pump: mgmt/glusterd: Misc fixes for replace-brick
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 14d6a7023fc1abc985675e9ee3e5fee4cd519210
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Oct 4 08:11:27 2010 +0000

    implement volume level address allow/reject setting
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit ef0c7384299e6104a2d4a967847b8c9cea1e79b8
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 08:02:29 2010 +0000

    stat-prefetch: reduce the stat-prefetch mem-pool size
    
    because we are not calling 'fini()' on old graph, after every graph
    change, we are leaking lot of memory. Hence reduce the foot-print for
    now, bring in changes to call 'fini()' later.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit c2e93bf6e391657c23a16b6536f7976136c32ce5
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Oct 4 07:45:08 2010 +0000

    Additional status check for rebalance in progress
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1791 (remove-brick during rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1791

commit 63281f698908897218bb6ca427e280217a4b38c2
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 07:38:11 2010 +0000

    /etc/init.d/glusterd (for RPM based distros), fix output format
    
    Thanks to Bernard Li <bernard@vanhpc.org> for the patch
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1677 (Fix output formatting for Red Hat init script)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1677

commit f02499e16624f29ac2be5531f1c4c298a12f33a8
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Oct 4 06:47:35 2010 +0000

    Add log-level option to command volume set
    
    log-level option to set brick's log-level
    client-log-level to set client's log-level
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1789 (add log-level options to volume set)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1789

commit 408c164d0adf67d0ab636d3f617fc48c896d33a6
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Oct 4 06:32:47 2010 +0000

    cli: add more type for volumes
    
    Added 'Distributed-Replicate', 'Distributed-Stripe' as types
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit e2438fdde0458b70b0cd201b4950b676188d0824
Author: Harshavardhana <harsha@gluster.com>
Date:   Mon Oct 4 04:50:53 2010 +0000

    Some cleanup in rpm specification file
    
    Thanks to Bernard Li <bernard@vanhpc.org> for rdma 'BuildRequires' fix
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1770 (Cleanup rpmbuild)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1770

commit 2420fd1f0cc5c357776d3766884b86859f3c3781
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Oct 4 02:50:55 2010 +0000

    mgmt/glusterd: update volumes on friend update
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit ebc40051898881fa3d49946046448ee34e356338
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Oct 4 02:17:09 2010 +0000

    mgmt/glusterd: update volumes from friend
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1784 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1784

commit 73f8e094495a71f6a6a4c90495874396f2614567
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 4 00:29:17 2010 +0000

    rpcsvc: bump log level of message for missing transport type
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 6d9bcd67e99ad638ca260f04cff401e7d9ebe3c5
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Oct 3 14:57:11 2010 +0000

    volgen: impemlent dynamic (pattern-based) option matching
    
    So now auth.addr.*.allow can be a basic option, without any specific support code!
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 609a89ceace25a0a81d0a9cafde3a4d1afd1b916
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sun Oct 3 02:41:29 2010 +0000

    mgmt/Glusterd: new command volume reset <volname>, volume set enhancements
    
    - Write the reconfigured options in 'info' file to make it persistant
    - Implementation of volume set  <volname> history
    - Implementation of volume reset <volname>
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit 53b8c7470f9e40c60c5eebd1fbad5c6d274f7ee5
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Oct 3 04:14:19 2010 +0000

    mgmt/glusterd: changes for detach everywhere
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1765 (peer probe  on removed-detached bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1765

commit c0c419a3572307e71026144b8907a33b464f6066
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 2 18:44:16 2010 +0000

    volgen: add a precise getter function which considers default values as well
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit ff7f17da9e1817c6d02da3e98163fce834b429f6
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 2 18:44:15 2010 +0000

    volgen: add support for auth.addr.%s.{allow, reject} options
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit e463cb64d99cf741fabf9e46f7511554607e250e
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 2 18:44:14 2010 +0000

    volgen: fix up replace-brick + pump generation
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit a3bf2a40fbd0b1b7478e0fbf87dd5a1a9c42e5ab
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 2 18:44:13 2010 +0000

    volgen: some refactor to make frequent invocations more handy
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 99caede76b0ef312d622b2387bf9524724e7c6df
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Oct 2 11:25:05 2010 +0000

    rmdir: introduce extra flags parameter in FOP prototype
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 5a4e1e69b2ec65dcefa6b37b8ac7d058f3a2c29f
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Oct 2 11:25:04 2010 +0000

    xdr: introduce extra flag in rmdir request
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 77085451a88878728e703215f9bf871a74df92ba
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sat Oct 2 08:29:38 2010 +0000

    Set the lock owner properly for lock self heal.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 8d70c0dd0a9346d75469634777daa362ec8f89f6
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sat Oct 2 08:03:44 2010 +0000

    cluster/pump: Do not do lookup if it is "." and ".." in pump.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 33d7a49bd55d6810d87811c109c7445e27b04c17
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Oct 2 07:36:33 2010 +0000

    rpc-transport/rdma: send disconnect event only if the transport is already connected.
    
    - A disconnect event can be sent before a connect event to rpc, if some error
        happens during rdma handshake.
      - Also call rdma_quota_put only if peer is not NULL.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 1b7a997a7b368aa459dcd57ec23532fe4cdd6e0c
Author: Pranith K <pranithk@gluster.com>
Date:   Sat Oct 2 04:12:51 2010 +0000

    mgmt/glusterd: print peer state names instead of state numbers
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1779 (print peer state names instead of state numbers)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1779

commit ef44323b4ba58fa8c1eb89105851983f828dd91b
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 2 07:30:39 2010 +0000

    volgen: reimplement volgen
    
    Generating a volfile occurs in two steps:
    - Build a graph (ie, glusterfs_graph_t instance) by graph manipulation
      primitives
    - Write out the graph to a file by the the graph printing API.
    
    Graph builder routines can optionally make use of a "modifier dict",
    which can contain overrides wrt. volume options. This can be used
    for a "dry-run" graph generation.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 067d0e476abe42f1e290039cb903928080e90d8d
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 2 07:30:38 2010 +0000

    implemented graph printing
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 1cc15f9b0057cd6c8843c8b9cbb36c02d334ec6f
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Oct 2 07:30:37 2010 +0000

    xlator: make it possible to do type setting and dynamic loading separately
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1750 (clean up volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1750

commit 73c6b2f21a67bed186a279adacb4eb28eafcd853
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sat Oct 2 06:14:33 2010 +0000

    protocol/client: Fix dumping of locks in client.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 99ff5f22db3404abbbab6e7d7edabe930762118d
Author: Pranith K <pranithk@gluster.com>
Date:   Sat Oct 2 05:31:55 2010 +0000

    mgmt/glusterd: destroy frames in callback
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit 0ac18907614886fa00858b6a1abfeb099b49348a
Author: shishir gowda <shishirng@gluster.com>
Date:   Sat Oct 2 02:14:07 2010 +0000

    Replace assert in mem_put with gf_log_callingfn
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1759 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1759

commit 365c814f7ba4cc8e04959927c3ded9cdd5b2ab24
Author: Pranith K <pranithk@gluster.com>
Date:   Sat Oct 2 01:36:16 2010 +0000

    mgmt/glusterd: handle peer not connected in peer detach
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1762 (peer detach/peer status ,created glusterd crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1762

commit c5714ce6e6fe20575159220bbdf178ebf33ca0ad
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Oct 2 00:23:31 2010 +0000

    debug/trace: print more information while logging inodelk and finodelk.
    
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 26b259476421b89e2df76572c101f5a628ae1bbe
Author: shishir gowda <shishirng@gluster.com>
Date:   Sat Oct 2 01:21:35 2010 +0000

    get server xattr only if name is not NULL
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1701 (better statistics  gathering in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1701

commit 17295c37f9ad12163f7c449dbe6f76aff90b493f
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Oct 1 13:04:57 2010 +0000

    rebalance: bring in two stages
    
    step 1: fix layout (quick pass, so the newly added brick can
            participate in distribute's entry creations)
    
    step 2: migrate data (do the actual rebalance)
    
    Its advised to run rebalance after add-brick, and let it complete
    at-least 'step 1', so things will be smooth with distribute.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 4afbc4e1c44d5da4d4cd6141fb2b693e7baeabe4
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Oct 1 13:03:58 2010 +0000

    glusterd: put all the code related to 'rebalance' in new file
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit b656bff2dd912bcd5caf5bf9303bdef17f753ce1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Oct 1 09:23:40 2010 +0000

    changes for replace-brick status message
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1767 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1767

commit 24ec0fbc4bd145b93b80afa480d5cb4cf785717e
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Oct 1 08:01:14 2010 +0000

    stat enhancements
    
    * dht to send 'setxattr' to all subvolumes in the layout
    * server dumps info on total bytes read/written for 'trusted.io.stat.dump' key
    * server dumps all the mount point IP for 'trusted.list.mount.point' key.
    * io-stats dumps latency information only if measured
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1701 (better statistics  gathering in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1701

commit a3f90eeb0ad97e4f86aef603f95b0562ab18f36d
Author: Pranith K <pranithk@gluster.com>
Date:   Fri Oct 1 08:00:12 2010 +0000

    mgmt/glusterd: handle glusterfs crashes for start/stop of bricks
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1741 (gluster volume stop after one process crashed.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1741

commit fd2e7d007e5362f0738cd9a825349abcf5d27d8f
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Oct 1 05:45:12 2010 +0000

    Changes to replace flock with gf_flock across GlusterFS.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 55c6e672503a2451186e17b9c1b7daf6e3ae5463
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Sep 30 12:44:26 2010 +0000

    contrib/fuse: update from upstream [555d6b50 in git://fuse.git.sourceforge.net/fuse/fuse]
    
    """
    commit 555d6b504308eac6b976321ce938ee4bec62c354
    Author: Miklos Szeredi <mszeredi@suse.cz>
    Date:   Tue Sep 28 10:13:24 2010 +0200
    
        Fix option escaping for fusermount.
    
        If the "fsname=" option contained a comma then the option parser in
        fusermount was confused (Novell bugzilla #641480).  Fix by escaping
        commas when passing them over to fusermount.
    
        Reported by Jan Engelhardt
    """
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1752 (sync with upstream for "Fix option escaping for fusermount.")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1752

commit 828829a9cf7b925709f9a1f289d9a6cb94b74dd8
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Oct 1 04:33:49 2010 +0000

    cluster/pump: Initiailize pthread mutex and saved fds list.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 3009bc7b585ae9973c6b50ce464a52f20182c63f
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Oct 1 04:21:17 2010 +0000

    remove 'gfs_id' field from all protocol xdr structures
    
    It was kept as a debugging requirement/placeholder. Because RPC is
    mostly bug free with regard to basic xdr structures, it doesn't
    make sense to carry this forward in release. Saves 8bytes in each
    request.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 1af483d3716d6b520c1b4fd984ccecee638b2886
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Oct 1 02:22:08 2010 +0000

    check if the table is NULL before accessing it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1757 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1757

commit f5afcc47f9f00472d6c2b3f48127e02332cd457a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 1 01:58:05 2010 +0000

    nfs3: Revalidate inode on receiving ESTALE on lookup
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1756 (NFS must revalidate inode on first ESTALE on lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1756

commit 9555e5ee7dd2c3a2c98cf505bb198e453ea747d1
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Oct 1 01:42:46 2010 +0000

    cluster/afr: Recover locks on child_up from source to sink.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit d355ecd89427871d8d3f20a99acd284baccef6e1
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Oct 1 01:41:46 2010 +0000

    mgmt/glusterd: Make replace-brick atomic
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 4ec7688091f9d6ee2a6886d53055b94f284c1f7a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Oct 1 01:35:22 2010 +0000

    changes for the gluster sanity script
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1436 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit 64437e01d920597140b35bfeb46591966584e7fc
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Oct 1 01:12:39 2010 +0000

    Allow graph processing even if reconfigure fails
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1730 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1730

commit da74288339563759f568aa5052fdce4c45ebcd22
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Sep 30 11:41:07 2010 +0000

    glusterfsd: perform init new graph if re-configure fails
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit af18c636c44b1ea56296850e55afe0e4b2ce845c
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Sep 30 02:25:31 2010 +0000

    protocol/client: cluster/afr: Support lock recovery and self heal.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 865 (Add locks recovery support in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

commit 760daf28898cbb8b5072551735bebee16450ba08
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 30 09:00:14 2010 +0000

    glusterd: fix in log filename and log rotate
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1731 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1731

commit 5a5a7f939c830d8e4a542c8fff00138b83ddd4fc
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Sep 30 08:46:03 2010 +0000

    mgmt/glusterd: memory leak fixes
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit bf152d98cee31a2346f3aec32301ca4a4bbfcea1
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Sep 30 03:41:04 2010 +0000

    Block add, remove and replace brick ops when rebalance is in progress
    
    Also fixing msg, changing defrag to rebalance
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit d39ed89765a8d0a1f767b864fd6826d29de7ad1f
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 30 02:18:11 2010 +0000

    start the per brick process with 'glusterfsd' instead of 'glusterfs'
    
    for users, it becomes easy to differenciate which process is exporting
    bricks, and which is used as a client process.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit f63e4b6e9aada6f96c71513bcf7f501f613a30fe
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 30 01:49:52 2010 +0000

    rpc: in rpc_clnt_destroy(), destroy the memory pool also
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1727 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1727

commit b7aed950dbeba2fdc952f734ca2f713acee2345d
Author: Pranith K <pranithk@gluster.com>
Date:   Thu Sep 30 02:22:52 2010 +0000

    mgmt/glusterd: remove debug messages in cleanup_and_exit
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1746 (volume delete fails after volume stop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1746

commit 65c704747809e126edde164cd0ce9f98ea7f6dc8
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 30 02:31:47 2010 +0000

    protocol/client: handle more NULL dereference
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1745 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1745

commit 76b0e35e7809c38e62f33b5068c61623a6914d5f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 29 10:47:58 2010 +0000

    protocol/server: set 'this->private' only if 'init()' is successful
    
    If volume file is fetched (due to HUP or volume file changes) and
    server init is called again, server protocol init fails with 'bind
    to port failed' error. If 'this->private' is set to new 'conf'
    before successful init, the whole process goes to corrupted state.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 0dc7064bd6047e9283d873f418d2e0a4e0ba29e6
Author: Anand Avati <avati@gluster.com>
Date:   Wed Sep 29 06:53:35 2010 +0000

    replicate: remove checks which prevented self-heal when open fds were present
    
    this check is not needed anymore since the introduction of changelog piggybacking
    as the optimization technique instead of first-write-to-flush technique
    
    some of the self-healing issues with NFS mounts should be resolved
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit b8c42e5cef817bdd0270b1991c0a365aa321f7cc
Author: Anand Avati <avati@gluster.com>
Date:   Wed Sep 29 06:53:03 2010 +0000

    replicate: keep read_child in inode ctx as up-to-date as possible
    
    In every transaction check if the currently set read child in the
    inode context failed in the fop and set it to another subvol on
    which the latest fop has passed. This will prevent read fops landing
    on subvols which have witnessed a failure.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1172 (ls -lh on NFS mount of 2-mirror replicate gives incorrect file size)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1172

commit 87697e7ed88ca650fe70e26d59b67254ed2393f9
Author: Anand Avati <avati@gluster.com>
Date:   Wed Sep 29 05:41:34 2010 +0000

    pump: skip "." and ".." entries while traversing dir tree
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 723c57faa30e102732aa29c8c4608703081970f3
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Sep 29 05:08:34 2010 +0000

    mgmt/glusterd: resolve uuid if null
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1734 (replace brick should accept both ipaddress and hostname for bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1734

commit 528dde957c809014aee40737d01cb667e858e0c9
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Sep 29 04:49:53 2010 +0000

    glusterd: make sure init is not called when there is no topology change
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit 2ce4be96bf1c3d08381cbdeb8d57800635702f37
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Sep 29 04:48:18 2010 +0000

    mgmt/glusterd: set the error before starting checks
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1734 (replace brick should accept both ipaddress and hostname for bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1734

commit 6689104ce7eed29c7878c124fa13caecaa1245ef
Author: Pranith K <pranithk@gluster.com>
Date:   Wed Sep 29 03:59:19 2010 +0000

    mgmt/glusterd: volume start force
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1736 (implement volume start force)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1736

commit 95dd4ae4dc2a8a3b3673e60c1fa6cbdbb9409d2c
Author: Anand Avati <avati@gluster.com>
Date:   Wed Sep 29 03:22:24 2010 +0000

    storage/posix: prevent chmod() from getting called on symlinks
    
    symlinks, if at all their mode can be changed (on non-linux platforms)
    can only be done via lchmod(). Attempting chmod on a symlink can be
    disastrous.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 881 (GlusterFS daemon hangs on replication of symlink (3.0.4))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=881

commit 9406c06522f9e8ef8ee73f6da55937cb1fa04d22
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 28 06:11:07 2010 +0000

    features/quiesce: new translator
    
    'Quiesce' is used to describe pausing or altering the state of running
     processes on a computer
    
     In GlusterFS context, this translator looks for CHILD_DOWN/CHILD_UP
     events, and will hold the requests for some time if the child node
     is in disconnected state
    
     current timeout is 20seconds, will be made tunable soon
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1500 (Mount point should not be in-accessible between reconnect to server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1500

commit 3702814c02c0789d8b65b4f096cd0d37947eef3f
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 28 02:58:20 2010 +0000

    defaults.{c,h}: _resume functions added
    
    * cleaned up whitespace
    * untabify
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1500 (Mount point should not be in-accessible between reconnect to server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1500

commit 95d45c7479db322028ab186f4f565c30cbdfba69
Author: Anand Avati <avati@gluster.com>
Date:   Wed Sep 29 01:11:07 2010 +0000

    replicate: clear pre_op_done/piggyback values after open fd self-heal
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 34a635c43fa4e33df29be2141348b6c360fcacc9
Author: Anand Avati <avati@gluster.com>
Date:   Wed Sep 29 01:08:05 2010 +0000

    replicate: use new style (un)locking in self heal of missing entries
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 960 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=960

commit aee339605337916aaa1e38a0e9ed2422f0f0dcfb
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Wed Sep 29 00:28:07 2010 +0000

    replicate: replace first-write-to-flush optimization
    
    use a changelog piggybacking optimization instead of first-write-to-flush
    optimization and do other cleanups (removal of post-post-op hook etc.)
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 25e4eefc40de8fc47260c1d8209679269686c162
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Wed Sep 29 00:28:06 2010 +0000

    whitespace cleanup
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 28980e69cf720a614fdd6666da5021524bc1f071
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Sep 28 23:28:28 2010 +0000

    mgmt/glusterd: brick info get should compare uuid instead of hostname
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1734 (replace brick should accept both ipaddress and hostname for bricks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1734

commit 4e72e3ac439bab76880236a87558fc54009c007c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 28 11:01:38 2010 +0000

    rpc-clnt: handle NULL dereferences
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1723 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1723

commit 2e8f8e85e9f5ccbefe834498d4cf665728c70303
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 28 11:01:10 2010 +0000

    client-handshake: prevent NULL dereference
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1720 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1720

commit 7fa2a88a28578dce36d88436776c05aee65165fd
Author: Anand Avati <avati@gluster.com>
Date:   Tue Sep 28 23:04:24 2010 +0000

    resolver: set safer conditionals during path creation
    
    when client would send just the path as part of a transaction, path
    reconstruction would create parent directory's path instead of actual
    path at the time of resolution.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 935 (Directories change mode from 0755 to 0644 automatically)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=935

commit 6686ddc22785fba5ea488fcaafa598161469085b
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 28 09:30:27 2010 +0000

    mgmt/glusterd: Fix incorrect state machine transition
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 981970098a68ae222805ae77a0ea53eb1f95fd21
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 28 09:29:52 2010 +0000

    mgmt/glusterd: compute cksum upon volume retrieval
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit d7e694ad7049cd819f8dbc26ec1e7d35b4d1a6fe
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Sep 28 09:27:23 2010 +0000

    mgmt/glusterd: prevent cleanup_and_exit if its already started
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1706 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1706

commit 84952d98750165f211d632940fbbd95059553dc2
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 28 06:21:44 2010 +0000

    Changing readdir calls to readdirp calls in DHT
    
    Changing readdir calls to readdirp calls to handle layout issues
    seen in dht.
    Also, changing posix readdir call to do stat after dir read for readdirp.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1690 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1690

commit 387f4d385e1d2c29af54c4f87eef7a07acfcfdf9
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 28 05:37:02 2010 +0000

    more proper error returns in case of graph topology validation
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 5ea64d983b31c6882d4582af71a339b6a4fcccf2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Sep 28 04:30:39 2010 +0000

    nfs: Free inodes layer fop locals to fix memory leak
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1259 (Memory leaks to 5.7g usage in gnfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1259

commit 9c8a9bd96733dc3ccde4d76786fe0ad009b3bf6e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 28 06:03:59 2010 +0000

    change the loglevel from error to debug while reconfiguring
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1729 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1729

commit fd3662166f8d7e8247bc535f0816bb3abea01889
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Sep 28 04:30:38 2010 +0000

    distribute: Propagate -1 op_ret on failed fop
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1717 (dht_attr_cbk does not propagate op_ret on failed fop causing nfs crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1717

commit 059c05561e1df6e24229e7adf613f868fa0275b9
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Sep 27 08:13:19 2010 +0000

    do not allow remove brick if the total bricks given is less than the sub_count
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1713 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1713

commit c3bf3b45a7cf612833c14fc701f751ffc04a7e73
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 27 01:57:15 2010 +0000

    access-control: report possible errors in graph during 'init()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1712 (Error is not logged for a dangling volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1712

commit a381d3a29fc149d78aecba22fdb285314aa9b711
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 28 05:17:27 2010 +0000

    glusterd: logs is a symlink to default var log dir
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1728 (glusterd log file location)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1728

commit a89ec9419758b420ce11dddac27327ec34141da6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 28 04:31:51 2010 +0000

    unref the dict allocated in set_volume, remove_brick
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1726 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1726

commit 1fd7b1c4fcfd4041c2a9cb89dcc3874f70324cde
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 28 03:47:40 2010 +0000

    Starting/stoppin glusterd changes brick pairs
    
    the problem was the pair information was not maintained anywhere.
    When glusterd re-starts, it reads the brick dir entries and
    populates the brick list. adding brick info to volume info file
    to fix this issue
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1714 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1714

commit 65a84c9d0d691ac4f7a5f33374140e50746a96af
Author: Pranith K <pranithk@gluster.com>
Date:   Tue Sep 28 02:47:08 2010 +0000

    mgmt/glusterd: prevent detach of peer with its bricks existing in cluster
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1681 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1681

commit dbbec1261eae8440726b001df8fe4c06837d6f3d
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 27 09:26:17 2010 +0000

    distribute: don't check for inode's gfid in _cbk
    
    * in dht_lookup_dir_cbk(), at the entry itself we are dereferencing
      local->inode, which can be NULL in many cases. Hence no need to
      check/dereference that variable. Just check 'local->gfid'.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1696 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1696

commit efd1f08b57a3175cab9bb543833bc3c9192b527d
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Sep 27 16:20:19 2010 +0000

    replace brick fixes
    
    Reviewed ok.
    Just like commit, maybe we can move 'pause' also to the commit op of replace brick since it can be performed only when replace brick has been started. I'll send in a patch for that soon.
    
    ----- Original Message -----
    From: "Vijay Bellur" <vijay@gluster.com>
    To: glusterfs@dev.gluster.com
    Sent: Monday, September 27, 2010 7:59:25 PM
    Subject: [PATCH BUG:1235] replace brick fixes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 4a9c36ea9df9dada0d16c5fdb9fe149b360d9150
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 27 08:57:05 2010 +0000

    glusterfsd: after volume fetch, return proper values from functions
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit edf5b0b4b89b46a566607d159b282c57298679db
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 27 08:55:55 2010 +0000

    io-threads: fix NULL dereference in 'reconfigure()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1715 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1715

commit f4ff82641baf75cf534531a4dc2eb588db1218cb
Author: Pranith K <pranithk@gluster.com>
Date:   Mon Sep 27 05:57:51 2010 +0000

    mgmt/glusterd: delay probe till connection happens
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1607 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1607

commit 542476b4bcf248c02ad087381c03c49c2b4c8014
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 27 02:06:26 2010 +0000

    access-control: handle a case of wrong error handling
    
    in rename_src_stat_cbk(), we were checking the return value as '-1',
    but the function can return '-EFAULT' (ie, -14 in few cases).
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1691 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1691

commit c0cd0637bb8c28db5d3de0a89f312cad96ba2347
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 27 01:22:57 2010 +0000

    fix a build warning about stack overflow
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1710 (build warning)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1710

commit acd2c4dc93381df9806243b6d367a36301e5eb66
Author: Pranith K <pranithk@gluster.com>
Date:   Sun Sep 26 23:55:41 2010 +0000

    mgmt/glusterd: perform post operations of volume set
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1708 (update store, re-compute checksum, restart nfs for volume set)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1708

commit 4725bd37787fe1c02213ab63316abb234077990f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Sep 25 07:52:18 2010 +0000

    protocol/server: Check before de-referencing conf
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1698 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1698

commit 336e2df7b74be7ad4c9ed403ca10b9f7f7ef9a58
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sat Sep 25 04:42:30 2010 +0000

    nfs: Fix multiple subvolume CHILD-UP support
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1643 (Initial requests after mount ESTALE if DHT subvolumes connect after nfs startup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1643

commit cb1c1d78a3aededcc1d1f77f6e91e23fda83a631
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Sep 25 04:40:33 2010 +0000

    mgmt/glusterd: Do not look into brick when logfile is being set for volume
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 0b68f788a8ff0579f70e546bcd365ee0c3a49a12
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Sep 24 13:37:32 2010 +0000

    mgmt/glusterd: resolve brick before doing uuid compare
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit bd73298410ac6814ed2f45acf2beafee21dc0af1
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 24 10:16:23 2010 +0000

    glusterd: add new stats related options for 'volume set'
    
    * 'gluster volume set <VOLNAME> latency-measurement <yes|no>'
    * 'gluster volume set <VOLNAME> dump-fd-stats <yes|no>'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1701 (better statistics  gathering in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1701

commit dca5c02cf31e373e6e4ff376a5f35684cd43e081
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 24 10:18:31 2010 +0000

    glusterd-volgen: add 'io-stats' xlator on server volfile too
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1701 (better statistics  gathering in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1701

commit f91dad3f618b2d981e69ecd5000974db712f9188
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 24 10:14:37 2010 +0000

    io-stats: bring in latency measurement feature
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1701 (better statistics  gathering in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1701

commit 96846cb2aaac582323a5f7347581dad2f5f2cd31
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 24 10:14:23 2010 +0000

    stack.h: remove the time/latency measurement code
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1701 (better statistics  gathering in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1701

commit 25e868b571bc394dd65b54849f369e1a0c29caab
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Sep 24 08:50:24 2010 +0000

    check if the bricks provided are the same and are alredy being used
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1682 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1682

commit 6e952607f17dd5ea6e3748f2bbc26234f4b1e553
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 24 07:51:53 2010 +0000

    rpc/rpc-transport: fix frame-loss during rdma-reads.
    
    - total no of rdma reads in progress was tracked using refcount of post
        (refcount = total rdma reads + 1). However doing rdma_post_unref _after_
        rdma_do_reads, can result in race condition between execution of
        rdma_post_unref and procedure handling rdma read completion. This makes
        it impossible to find out whether the current rdma read was the last
        rdma-read being done in procedure handling rdma read-completion.
        The fix to this should either do rdma_post_unref before posting an rdma
        read or use another variable to track the number of rdma-reads.
        This patch implements second method.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1700 (write fops are bailing out on a distribute setup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1700

commit f2c5894f254d9b3d17b058adce7c7b4152da2f5e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Sep 24 04:38:36 2010 +0000

    mgmt/glusterd: add option to force kill gnfs process
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1517 (gluster volume stop - starts a new nfs server.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1517

commit 0cf88c1d35bbc86fdfc1b8035222b248d6725807
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Sep 24 04:09:03 2010 +0000

    mgmt/glusterd: initialize addrinfo variables
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1695 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1695

commit e9880384632d8ae489a1f6cdc5429ba6e378ce40
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 24 03:17:36 2010 +0000

    glusterd: fetch-spec now allows NFS like '/<volume-name>'
    
    To make mount options similar, so less confusion
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 6965560fe9f9291093e9d91c5787ce0374371eb8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 24 01:40:34 2010 +0000

    rpc-clnt: print frame-sent time till microsecond resolution in call_bail.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 0209aab58c56e06fd86487be76312d04fd8f5593
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 24 00:29:29 2010 +0000

    glusterfsd: handle relative path for '--volfile/-f' option
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit ad9c5f801ebffb0993d5f764b27e12b01beba2ce
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Sep 23 08:29:15 2010 +0000

    mgmt/glusterd: cleanup generate_perf_xlator_list ()
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1670 (Volume set enable disable support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1670

commit 7e1b8bb370b4082e66ebe6e458fc45aa653ab3f1
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Sep 23 08:29:14 2010 +0000

    dict: add dict_get_str_boolean() function handily query string-boolean values
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1670 (Volume set enable disable support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1670

commit 406bcbb443aaca1655be9dcb9101a717eafdc061
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Sep 23 02:09:25 2010 +0000

    Check for possible fd/ctx NULL in afr
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1636 (Replicate crashed in afr_nonblocking_inodelk on deref of NULL fd_ctx)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1636

commit c5a5fea9e6a1f1709e6826c1eea89dfd25cc496b
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Sep 23 09:18:37 2010 +0000

    mgmt/glusterd: Misc fixes to pump / cli / glusterd wrt replace brick.
    
    Patches from Vijay and Shishir have been pulled in into this one big patch.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit fa3ca3c61fbd7ad95f57f0522624396b8f05ecf6
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 23 06:30:43 2010 +0000

    distribute: don't update the inode's gfid directly
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1680 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1680

commit a2e35ea0166c42435f860990c9476dda470843c8
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 23 05:14:05 2010 +0000

    distribute: bring in feature to fix the layout of root inode
    
    * If the errno is ESTALE for root, fuse doesn't send fresh lookup on
      the path (it does for all other inodes). Earlier layout mismatch for
      root never used to happen inside codebase, and if noticed, it was
      serious issue.
    
      Now with DVM, after a add-brick or a remove-brick, layout can be
      changed even for 'root' inode. Needed to fix this issue inside
      distribute itself, instead of fuse sending 'fresh' lookup on root.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1630 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1630

commit 279d46c1068761ffd6349db2913f06c4bb692e17
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 23 03:52:57 2010 +0000

    fuse-resolve: remove stale code
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1240 (DVM: after graph change, inodes should resolve to new inode-table)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1240

commit 7f645c3ac3678bab9b74c62b33951450841af967
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 23 00:45:53 2010 +0000

    gluster cli: handle case of no brick given in log locate/rotate
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1679 (gluster volume log locate/rotate segfault)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1679

commit 2b0299da40ec4d35106d1caaadf936387a54fcce
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Sep 22 23:42:11 2010 +0000

    cli: Make volume rename hidden
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 26228ccddc85ab575e4508a03297af57713a5b28
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 22 22:42:51 2010 +0000

    glusterfsd: destroy mgmt in cleanup
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1517 (gluster volume stop - starts a new nfs server.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1517

commit 22560c7faf95157c8ff4df9953d83147e153d3d7
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 22 15:05:22 2010 +0000

    mgmt/glusterd: Always use io-stats as the topmost xlator with appropriate volname to be nfs friendly.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1670 (Volume set enable disable support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1670

commit 37b4a747f5741dda0a24b97420460734452a4b1d
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Sep 22 13:27:04 2010 +0000

    cli: Avoid exposing volume set-transport
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit b89e9348aed56c40fec1f8401230dd5a1965f235
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Sep 22 13:26:41 2010 +0000

    mount/fuse: generate gfid only in case of a fresh lookup
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 5c4ac19e88f5d7954770aceed930ee193c4138b5
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 22 10:03:17 2010 +0000

    fuse-resolve: don't resolve fd to new graph for now
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1674 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1674

commit 435603caeb651dc1050c85281e3838df9d37ce64
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 22 09:43:45 2010 +0000

    distribute: in linkfile creation check for valid gfid in inode
    
    * if inode->gfid is not valid (ie, null), take the gfid from the
      parameter dictionary passed from higher layer
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1565 (deleting files after dht rebalance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1565

commit 66b1613efdae3ba2740241ee325e5f0b0634424d
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 22 08:50:23 2010 +0000

    distribute: while selfhealing directory, send proper gfid in dict
    
    * this was the root cause for having layout mismatches in case of
      add-brick, because the gfid of directories on newly added brick
      was always mismatching, which caused many operation on that
      particular brick fail.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1629 (files missing during add-brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1629

commit 0a14d255dcd6fa3e9d575bae1fecd164763104bb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 22 08:14:02 2010 +0000

    rpc/rpcsvc: add debug messages when rpc-messages are handed over to/from transport.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 679395dc7ed5b716f3fb37886f7ec8e59ab02659
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 22 06:17:32 2010 +0000

    mgmt/glusterd: skip sending req to disconnected peers
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1673 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1673

commit 2915e10dd0ffe529ddf747451051cf9924c708f3
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Sep 22 05:21:28 2010 +0000

    Restart all bricks which are down when glusterd comes up
    
    This is only done is the volume is started.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1562 (insufficient consistency check on start of glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1562

commit 3225d7ccf599e726012fb2d32fe3cc68b979e0ea
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 22 04:23:45 2010 +0000

    rpmspec file: add option for '--without rdma'
    
    Thanks to Bernard Li <bernard@vanhpc.org> for the patch
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1650 (Add '--without rdma' rpmbuild argument)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1650

commit d42f248c58b2ca73fb56a3e091c8e967e2435546
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 22 04:21:02 2010 +0000

    mgmt/glusterd: replace-brick validations
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1657 (validations for replace-brick while stage op)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1657

commit f47b0c55de9941823fbefe4b3a7e37179d6d4329
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 22 03:32:17 2010 +0000

    nfs, nfs3: Base volume access on CHILD-UP-DOWN event
    
    Overall, the aim of this patch is to change the result of an nfs
    op depending on whether the underlying volume is up or down
    as notified by CHILD_UP and CHILD_DOWN events.
    
    This patch contains three intertwined changes:
    o Only when the lookup on the root of a volume is successful does gnfs now
    export the subvolume. Till now the result of the lookup was not used to
    determine whether we should export that volume. Not accounting for root lookup
    failure resulted in ESTALEs on first access because some children of distribute
    were down at the time of the root lookup.
    
    o Only when lookups on all the subvolumes have succeeded are
    these exports enabled through NFS.
    
    o When a child of say distribute goes down, on CHILD_DOWN event nfs will
    ignore all incoming requests from the client because ignoring these
    will prevent ESTALEs for those requests and in the hope that ignoring the
    requests will make the client retransmit. There are risks in this approach
    absent the DRC but we're willing to live with that for now.
    When a child goes down, the mount exports list will continue to show it
    but mount requests will be denied.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1643 (Initial requests after mount ESTALE if DHT subvolumes connect after nfs startup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1643

commit 6b2e2fb0903fc56105c267881f202a4865a8b6c7
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 22 03:32:16 2010 +0000

    distribute: Propagate CHILD-UP when all subvols are up
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1643 (Initial requests after mount ESTALE if DHT subvolumes connect after nfs startup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1643

commit a4c948aca6058049523e31acf33ce5770f8693ad
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 22 03:32:15 2010 +0000

    distribute: Return ESTALE when dir selfheal finds no fix
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1641 (Distribute must return error when dir selfheal has no fix)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1641

commit 151c120908fbd8e18072a6e64a641911c307a51c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 22 03:32:14 2010 +0000

    core: Introduce string representation of GF_EVENTS
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1643 (Initial requests after mount ESTALE if DHT subvolumes connect after nfs startup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1643

commit b6121c62717c89ddc38b72ef18ba110c944cde70
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 22 02:29:12 2010 +0000

    mgmt/glusterd: opinfo unlock should be done in txn_complete
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1664 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1664

commit 05fd7d004a307a1aba158df82a868e3d271fe966
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 22 02:01:36 2010 +0000

    mgmt/glusterd: Restart src brick and add pump when replace brick cmds are given.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1669 (pump xlator should be excluded by default)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1669

commit e6bdd4f642d5f4d0afbe76b21fdd644c326edb0e
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 22 02:01:10 2010 +0000

    mgmt/glusterd: Enable/disable xlator options support added.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1670 (Volume set enable disable support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1670

commit 14bd64ad53409fb093c499eca45cb23fe9f96772
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Sep 22 01:40:45 2010 +0000

    Remove brick for stripe should check for pairs/subvolumes
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1658 (removing single brick works)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1658

commit 8432caca68b9006061226998648c0dd0ff5ebbd3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 22 00:10:28 2010 +0000

    performance/quick-read: fix memory leaks.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1438 (memory leaks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1438

commit 7655ccebd46936a42a6edb62184455077a6505fd
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 21 22:22:45 2010 +0000

    server-helper: check for conf before dereferencing
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1667 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1667

commit a2688982b7694f18d6a1d7e20ab36274cca9cc27
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 21 08:12:36 2010 +0000

    unmount the replace brick client irrespective of whether the previous commands succeeded or not after the mount
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1661 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1661

commit 78a09306fe1bd955616b8dd56e85f3af954c96b0
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Sep 21 09:12:31 2010 +0000

    libglusterfs: handle failure properly in gf_system()
    
    - Child must be terminated if execve(2) fails, otherwise it will deadlock
      parent
    - Status, as of given by waitpid(2), is aggregated data, should not be
      returned as is. In fact, there is not much point in threading up the
      exitvalue: callers usually return gf_system result as is, and according
      to glusterfs conventions, they should return -1 on failure. Therefore
      now we check only for success/fail, and return 0/-1.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1665 (glusterd hangs if spawning a child is failed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1665

commit eb8561e302bd83305fb093eb8cca42b4f9f62b22
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 21 10:49:49 2010 +0000

    cli: remove trailing slashes from brick paths
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1659 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1659

commit bd1fa94c8e26cb34566ad460092c2089597e2b17
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 21 05:37:10 2010 +0000

    mgmt/glusterd: print critical log for responses from unknown peers
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1490 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1490

commit 6dbd6185483591fc2f83beee9d2766d1ea0c61a4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 25 04:37:44 2010 +0000

    mount/fuse: By default enable direct-io only for fds not openened with O_RDONLY.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 801 (Direct io-mode support and related changes in caching translators.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=801

commit 7547953e3a7a458d60f8bbfef8e141aff087bfa3
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 21 05:12:08 2010 +0000

    fix the typo in the getxattr of replace-brick
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 7e4d13b56022dfe57fc1512e247eb030edec17fb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 21 03:51:57 2010 +0000

    check the private structure of the xlator before accessing it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1651 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1651

commit 0484b5768da303998549e8153d08899e58edab68
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 21 02:02:48 2010 +0000

    cli, mgmt/glusterd: send errno in case of Peer reject
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1653 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1653

commit ae376259304b654206c50b095dabf172fc355438
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Sep 20 23:55:55 2010 +0000

    Friend find should handle hostname/ip
    
    Regardless of friend being added(probe) using hostname or ip address,
    friend find should succeed if any of the above pair is provided.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit ad234382336a6f2dafb4cb698dfabbf7957b498b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 20 09:54:12 2010 +0000

    cli, mgmt/glusterd: volume sync command
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1310 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1310

commit e71b50e49612af4e76510b0c2a6f0519adfd852d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Sep 20 08:09:09 2010 +0000

    rpc-transport/socket: set keepalive socket option.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 1473491b576700bb3891abb8adb49e0c31cef8bc
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Sep 20 07:28:30 2010 +0000

    cluster/afr: print correct offset in debug message during diff self-heal.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 960 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=960

commit abbfbe2461511183a983f5c97f08f2653f40d47b
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 20 02:29:14 2010 +0000

    build glusterfs with '-O0' flag by default
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1599 (can we build glusterfs with -O0 -g by default)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1599

commit 5c297be9612f76dad6f970092fb6762b4ee4844a
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Sat Sep 18 03:31:56 2010 +0000

    Glusterd: gluster volume set <volume> <option> <value>
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1159 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1159

commit faa817ea9cb119c7f65fce24f03a172fa4b4ada1
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Sep 18 06:31:33 2010 +0000

    mgmt/glusterd: detach peer properly when msg submission fails
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 2bd9adb71d9b64799fef7978ff1da97fadab3056
Author: Anush Shetty <anush@gluster.com>
Date:   Sat Sep 18 06:21:33 2010 +0000

    change stat structure to iatt
    
    Signed-off-by: Anush Shetty <anush@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1642 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1642

commit 994d6de08c208509f69b2a0df16f6398dde49215
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Sep 18 03:21:56 2010 +0000

    cluster/afr: allocate memory big enough to hold iatt structures.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 927 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=927

commit dc648b30d2b892ef9413a32893070d1abf69f3df
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Sep 18 03:20:58 2010 +0000

    cluster/replicate: stack_wind into read_child only if it is up.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1637 (replicate should wind reads into read-child only if it is up)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1637

commit 1cc83c61c06b8271e856466530513dd63c3e8681
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Sep 18 01:54:09 2010 +0000

    check for 'link_inode' in server protocol
    
    * also log and return in case of 'fd_bind' getting fd with NULL inode.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1635 (running mixed tests glusterfs crashed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1635

commit 8ba46b4c2d6f67887454d1e6756e6dc476d9457d
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Sep 18 01:30:35 2010 +0000

    mgmt/glusterd: Proceed state machine when cli response fails
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1530 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1530

commit d111e0fa0b9769b8ffb8df97a976ba74efae576d
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 17 23:21:55 2010 +0000

    rdma: do event_unregister() in fini() too.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1611 (crash in gf_free)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1611

commit 0693997b778d1f3c328f0ad0d6ab8b1ad3be6b72
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 17 22:52:11 2010 +0000

    server-resolve: check for variables before dereferencing
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1628 (glusterfs crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1628

commit 1f7610608c4888fecc416a46b52d35c791a5116f
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Sep 17 13:36:12 2010 +0000

    glusterd: refactor service termination
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit dbb2b3764c6f9cfeaeacd868e3167210017ba848
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Sep 17 06:41:13 2010 +0000

    reorganize /etc/glusterd/logs, add nfs log too
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1319 (gnfs support in gluster command line)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1319

commit 4e6fb304ce41acbaf7c9ba67c06bf443e65082e8
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Sep 17 06:32:01 2010 +0000

    nfs3: Unref & unbind dir fd with inode lock on EOF
    
    ..so that when EOF is reached on this fd, any further
    requests on the same inode do not get handled through this
    fd but result in a new fd being opened.
    
    Unbinding results in the fd getting deleted from the inode's fd list.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1619 (glusterfs nfs server crashed on dht+replica(2x2))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1619

commit 941db02552773bcd6a3782e793fcbc41d4268697
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Sep 17 06:14:24 2010 +0000

    mount/fuse: Perform malloc for appropriate length
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1631 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1631

commit 91174380ae00a108512a4230f4cd2c1901d4bb94
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Sep 17 05:47:20 2010 +0000

    free the dict_val to avoid memory leak
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1621 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1621

commit 3d7356c0c205898bd4d515300c563be9ce113ec3
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Sep 17 04:12:51 2010 +0000

    Fix crash in dht_pathinfo_getxattr_cbk
    
    The crash happened due to NULL dereferencing.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1626 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1626

commit b2693d5e059c99095ceafb9ee8401f65825213c5
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Sep 17 04:12:18 2010 +0000

    Fix transalator indent for option
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1626 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1626

commit 853a2751c578fa11af131cacccb9e6248de4eca1
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Sep 17 01:27:04 2010 +0000

    cli: fix incorrect return value for system:: getspec
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit c92a4ad01f81de34e1955a19e42ab28a2865ea84
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:22 2010 +0000

    portmap: add support for registering multiple bricks on one port
    
    Rationale: if a brick serves multiple volumes, all of them need
    to be registered for the port the brick server listens on.
    
    Implementation: to register volumes "foo" and "bar" for port 6543,
    you have to send a SIGNUP for brick: "foo bar", port: 6543.
    Upon a pmap lookup, we match the search term to
    whitespace tokenized bricknames on server side.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 3b27ee5d59cfd08e419dfbf1b71b54e724b1ed14
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:21 2010 +0000

    portmap: make grounds for typed service mapping
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit afa6e19f6a9e1dde0f00d72c21c760a5dca341b0
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:20 2010 +0000

    cli: added system:: portmap brick2port
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit e690af8375f55bf8d8e56a0334cc9bd88867326e
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:19 2010 +0000

    cli: added system:: getspec
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 202761d052d2faa2c92b23c5afc32c27853b11ad
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:18 2010 +0000

    cli: add system namespace
    
    See "gluster system:: help" to get the feel of it.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit cecc24958374cfecddd64535c10d53ead8c7ad24
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:17 2010 +0000

    cli: make cli behave nicely with batch commands piped in in stdin
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit d787bca47fc038facb34221ee9855934f7230ef4
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:16 2010 +0000

    cli: add "--remote-host=<hostname>" option
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 63ec13f022ae99c1664fbdbc9e6623903ba843af
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Sep 15 08:11:15 2010 +0000

    cli: add a simplistic option parser, convert "mode script" to "--mode=script"
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1570 (geosync related changes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1570

commit 47bc630dca589235d7c10e2748cebaa5e419d5d7
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 15 10:53:00 2010 +0000

    server: Check gfid presence using uuid_is_null
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1608 (stat fop on dir returns ENOENT from server-resolution path)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1608

commit a2277a40ff8d19272abe11d9bf0257535ae0856c
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 16 07:41:42 2010 +0000

    logging: fix a crash in gf_log_callingfn()
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1623 (crash in logging callingfn())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1623

commit a64c84f2bc2ed70479df1ba281ff518461cc7cfb
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 16 07:01:53 2010 +0000

    distribute: send proper 'gfid' in calls originated from lookup/mkdir
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1608 (stat fop on dir returns ENOENT from server-resolution path)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1608

commit 279fbb6f71f36b90480f19e5a98d0b1d27215733
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 16 04:04:58 2010 +0000

    performance/write-behind: dump contents of wb-file
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 27d45ce245376cb012b0dd80dee6ccb26cc12645
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 16 01:27:39 2010 +0000

    cluster/pump: introduce another flag to enable pump functionality
    
    * by default pump will act as a pass through xlator, only when
      replace-brick start command is issued, it will set the flag,
      and then pump features (ie, afr) will come in to picture.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1590 (Stack overflow during self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1590

commit b956f2389144ce19386770187ad7d17350a4bd1d
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 16 01:08:15 2010 +0000

    protocol/client: prevent a crash while taking process state dump
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1616 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1616

commit f8accba64ce850bfb13bb3a4978ae8493ff5f6d4
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 16 00:13:46 2010 +0000

    avoid code duplication while freeing respnse hostname
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1614 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1614

commit 6fe0be9ffdd11789aa7567183ee415b121a85734
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Sep 15 23:53:57 2010 +0000

    check if the brick to be added is online
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1603 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1603

commit 0e2c2f46ddc36ccedeea8b42f7789f09224b5c9f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Sep 15 09:41:40 2010 +0000

    check req structure in the ctx before transferring probe response
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1614 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1614

commit e7535ad313d08ec587311729f049397d3ed995ce
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 15 08:35:42 2010 +0000

    mgmt/glusterd: gf_strdup the rsp msg and free xdr memory
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1613 (glusterd crash in create volume failure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1613

commit 1c92eefd50f6ade459b293da6aa5e44b0cd72271
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Sep 15 08:14:07 2010 +0000

    free the handle and pmap structure in fini for glusterd
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1580 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1580

commit c109ffb893ab80dd7b9dac038f5778961859ceff
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 15 06:49:56 2010 +0000

    cli, mgmt/glusterd: disallow probe to a cluster
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1594 (make probe oneway)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1594

commit 89ec6582d1977c98372cb69f6471fcfde8437bb7
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 15 06:46:48 2010 +0000

    rpc: add ref/unref for rpc clnt
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1594 (make probe oneway)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1594

commit 2ea1c2b68c46b8315790900291b18eb6f04010f9
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Sep 6 03:28:06 2010 +0000

    Deadlock in state dumping while holding the logging lock
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 976 (Deadlock in state dumping while holding the logging lock)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=976

commit 703dbf354d53fdcc37851bb71420730675a7e170
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Sep 6 01:36:57 2010 +0000

    Leak in Locks
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 996 (leak in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=996

commit 28d02d0b216ab2c580b1d3a48a793a312e1a98ae
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 15 05:16:48 2010 +0000

    socket.c: suppress spurious 'dict_get' logs in glusterd debug mode
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1606 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1606

commit 015a9b1f5a83572445171458312a90dbe0e4aca8
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 15 04:34:08 2010 +0000

    nfs3: Copy deviceid from correct gfid start octet
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1600 (showmount works but unable to mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1600

commit 7618628ff3c469af38d9c58840e5d0c8fde7156a
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 15 04:53:34 2010 +0000

    rpc-transport.c: handle a double free
    
    * 'this->name' was getting freed in '(transport)->fini()'.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1605 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1605

commit 3d1a0c2e3787f1c1b6cb1eb45690f36e175e983b
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Sep 15 03:28:48 2010 +0000

    error out if a peer is not connected or not in befriended state
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1603 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1603

commit 2745bc6a917b356d55b1cbdff1644a2465fa133d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 15 03:18:57 2010 +0000

    nfs3: Set gfid[15] to 1 for root
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1600 (showmount works but unable to mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1600

commit 560842297b9a067f358d3c3969eb3bdbb6132036
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Sep 15 02:02:05 2010 +0000

    Volume stop/start fails sometimes
    
    If the pid file is not present, do not fail the volume stop.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1602 (Volume start/stop sometime fails.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1602

commit 1fc3aed7cf33b96f33693eee3c0551a0ab6a1f0f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Sep 15 01:25:51 2010 +0000

    check if the peer is connected before updating friend and send response once befriended
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1601 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1601

commit abf28c8fd12f662f32c1a81f84620f562de8f14b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 15 00:27:10 2010 +0000

    memory leak fixes.
    
    - free memory allocated by libc when decoding request arguments in server and
       reply in client.
     - free memory allocated to saved_frames during connection cleanup.
     - free memory allocated for transport name while creating listeners.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1438 (memory leaks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1438

commit cfbbf68f8af83521b41b40c07db48897b976b626
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 14 23:43:39 2010 +0000

    Cleaning up mem_get0.
    
    mem_get0 is exactly the same as mem_get, but with the addition of a call
    to memset(0). hence, making mem_get0 to call mem_get
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1520 (gnfs crashes on start-up in mem_get0)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1520

commit 92cd5175b42d291314a2ede95b05ad10cb91b988
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 14 07:40:39 2010 +0000

    remove 'ino' from protocol structures
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 59cba5744656671cc16574be6822e3b000dccd90
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 14 07:40:26 2010 +0000

    posix: remove variables used for maintaining generation numbers
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 8e068b0615859829ac1bb2351b78307b2b496cdc
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 14 07:40:11 2010 +0000

    remove 'gen' from iatt/protocol structures
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit c55cc2d5362a607692beac96a34add2e79a9ad44
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 14 09:27:14 2010 +0000

    compare op_errstr before freeing
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1598 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1598

commit a9cbdd2916ab6851d108833e30536c02bf502f17
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 14 06:31:10 2010 +0000

    posix: fix an issue with existing data in case of readdir
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1597 (readdirp  fails if there is old data in the subvolumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1597

commit 7b591588b3031d0c6351d7c0a4626caad5fb3263
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 14 06:21:20 2010 +0000

    compare rsp.spec before freeing it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1596 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1596

commit 8b667fed03a49dc59ef9ae937a081145d38dc5a1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Sep 14 05:23:35 2010 +0000

    check if the export directory is present while starting volume and send the response to cli
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1593 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1593

commit bc4f737210bc0971d031cf9b3ff8fe941482eabc
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 14 03:54:39 2010 +0000

    socket: add xfer data counts
    
    * keeping track of data transfered over wire helps to identify the
      protocol overhead, and also can help us in debugging more on server
      loads
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit ff9eb1d536f2c57ec216b9ce8b96d1f536984008
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 14 04:31:02 2010 +0000

    performance/io-cache: fix memory leak in ioc_mknod.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1438 (memory leaks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1438

commit df331224c570d85f597d51b6072c44c1ff5f46f5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 14 04:09:52 2010 +0000

    rpc: print xid of the rpcreq corresponding to frame being bailed out.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 9446e8d3ec23e43352ab589ca53ea42413c21588
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 14 03:56:00 2010 +0000

    glusterfs3.x: change gfid type to opaque
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit efe088dcba88c4e95279692bda05d8dcf64c0ab4
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 14 03:55:24 2010 +0000

    glusterfs3.x file is updated with changes done to xdr.{h, c} files
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 9ff89d858075d8f916c76a9ade84b9844da4d23e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Sep 14 02:39:11 2010 +0000

    nfs,nfs3,mnt3: Transition fh resolution to gfid
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 2152dae595438b919fbcb7349d15ead139e120d8
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Sep 14 02:39:10 2010 +0000

    posix: Copy gfid from stat to dirent for readdirp
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 429a94c78ad3e6a956c847836a061c860d19e499
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 14 02:23:32 2010 +0000

    mgmt/glusterd: make probe one way
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1594 (make probe oneway)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1594

commit 8a2d1cf7a1425b9de2622635a1149f460bf1f36b
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 14 01:27:22 2010 +0000

    Add checks in mem_pool to catch possible double frees
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1520 (gnfs crashes on start-up in mem_get0)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1520

commit b0003a7e789e0618656dd4214195578f53d1e84e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 14 00:54:22 2010 +0000

    mgmt/glusterd: free xdr allocations
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1186 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1186

commit 174f963c846331c6dafda169451790b6039ef3fb
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 13 08:32:37 2010 +0000

    rpc: in rpc_clnt_destroy(), cleanup the transport too
    
    * if we don't cleanup the transport, it will trigger false
      events on the free'd transport which causes crash
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1423 (Crash in gf_timer_call_cancel)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1423

commit 39e268ee69618488616df1c253b851c07442c863
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Sep 13 07:54:50 2010 +0000

    Volume create propogate error msg to cli if invalid export
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1180 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1180

commit a13bc5aab51ae0e03721c48c8eb98b08c6137872
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Sep 13 07:54:30 2010 +0000

    Print error msg to the CLI from glusterd
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1180 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1180

commit 47a0854524123c21ef1a40d4f33c5593eb586565
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 13 06:59:55 2010 +0000

    gluster log {rotate,filename} : uuid check for bricks
    
    Thanks to Raghavendra Bhat <raghavendrabhat@gluster.com> for
    pointing out the fix.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1550 (volume log rotate failed.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1550

commit 58cedad283af2005f7f4969f7ac50a8e937e5594
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 13 03:41:08 2010 +0000

    io-threads: return -1 in case of 'init()' failures
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1591 (glusterfs server crashes with another translator inserted into volume chain)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1591

commit a6a5b539bba3ce9ab82d6e137f2d961cde9546fe
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 13 02:48:45 2010 +0000

    afr: reduce the size of readdir request during entry-self-heal
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1585 (Errors during self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1585

commit a3dd23e5fd0d4fc950068d54f085a99f17955842
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Sep 13 02:00:36 2010 +0000

    No space left on device error
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1588 (No space left on device error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1588

commit 6d52dfb6646286f2dfd554dc008e96f9b13aade9
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 10 20:24:07 2010 +0000

    logging: provide a API to print calling functions
    
    * logs 3 calling functions
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1493 (log enhancement to print calling function..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1493

commit d0ee998f5c997cfdebd0b7ff4bcbc9b2ea74c1ff
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 9 07:40:41 2010 +0000

    posix: remove gen related xattr usage
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 4f31b51fcb998651598cc297825ce4a3405a65fa
Author: Sachidananda <sac@gluster.com>
Date:   Tue Sep 7 10:01:20 2010 +0000

    cluster/afr: Clean up dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1083 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1083

commit 1b541ad1ec3b30982adbd1f08b050b4291ddb271
Author: Sachidananda <sac@gluster.com>
Date:   Tue Sep 7 09:46:41 2010 +0000

    performance/io-cache: Fix clang errors.
    
    Clang error fixes plus some whitespace cleanup.
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1111 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1111

commit 14df5292f3860abbf64358739a0ca5510e7bb869
Author: Sachidananda <sac@gluster.com>
Date:   Mon Sep 6 10:06:03 2010 +0000

    features/trash: Fix clang errors.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1127 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1127

commit df35c2f74b81247b591f6dd1e6dc72503ca180e2
Author: Sachidananda <sac@gluster.com>
Date:   Mon Sep 6 09:58:46 2010 +0000

    features/quota remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1128 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1128

commit 993edcc972269424901357578568b48af70a6a63
Author: Balamurugan Arumugam <bala@gluster.com>
Date:   Mon Sep 13 03:40:16 2010 +0000

    extras: modify run level scripts to support glusterd.
    
    Signed-off-by: Bala.JA <bala@gluster.com>
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1589 (Change init.d scripts to include glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1589

commit 288040196caa67b559ea668cef21284515109d94
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Sep 10 08:15:26 2010 +0000

    mgmt/glusterd: set req in opinfo
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 6858155d8b0681f9caea5295a2de63252ff9631c
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Sep 10 07:32:29 2010 +0000

    mgmt/glusterd: add a dict to glusterd commit response.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1582 (replace-brick data missing added brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1582

commit 5bec5e4fd6b0cae5e7a5e4d0a72090f4d613b94e
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 10 05:53:59 2010 +0000

    glusterfsd: exit process instead of starting fuse in case of failures
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1586 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1586

commit 4aada05a7a2b21d4c5275812a6e8f838e3a10512
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 9 07:18:50 2010 +0000

    rpc/rpcsvc: fix invalid free in rpcsvc_create_listeners.
    
    Sending on behalf of Raghavendra G
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit c1d8e31ad0b772149620465e79774cbf7b048d41
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Sep 9 05:55:53 2010 +0000

    Fix incorrect logmsg about disk space in dht
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1573 (Incorrect information about disk space in dht)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1573

commit c1f4f9ba17fd40ef9c726a9599f3122f29ef0092
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 9 05:56:59 2010 +0000

    free the tmp string allocated while getting brick information
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1580 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1580

commit 6ee84e00f0d96e292163ebad86b2e7521776dca1
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Sep 9 05:44:49 2010 +0000

    mgmt/glusterd: Do not check for src/dst while issuing replace brick cmds.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1582 (replace-brick data missing added brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1582

commit 80439c92add5aa54ee628697d4b27c9b56692fd0
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 9 05:06:55 2010 +0000

    glusterd: fix init time warnings
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1584 (starting glusterd for the first time gives warning logs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1584

commit d65c85001a6d57f6b147d565d45a704c890cfe08
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Sep 9 05:56:02 2010 +0000

    mgmt/glusterd: Use appropriate length while doing strncpy
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1583 (glusterd crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1583

commit 9ed068a03e6f07e7f0bb69b32c08cd251f369ce8
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 9 02:43:10 2010 +0000

    stripe: fixed create issues after gfid changes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1581 (stripe create is broken)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1581

commit 576d7030430c7a2e68c8454b40ebaa83853f0ba2
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 9 02:40:37 2010 +0000

    do not use pmap_registry_get function, instead use this to get pmap while removing
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1580 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1580

commit 7c915b6ffcf00fad0fa8e1075bd80ca63de36ea3
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Sep 9 02:23:37 2010 +0000

    rpmspec: Include manpages of glusterd and glusterfs-volgen.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1275 (Fix rpm glusterfs spec file for 3.1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1275

commit 7fc5e8c5de75eaa0a37de1402af1e879703139df
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Sep 9 02:23:17 2010 +0000

    rpmspec: Rename ibverbs as rdma package and include the relevant files.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1275 (Fix rpm glusterfs spec file for 3.1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1275

commit eae063da57a47102d264f27395677262fb17dc75
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 9 02:03:15 2010 +0000

    dict.c: fix a redundant log in DEBUG level
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1493 (log enhancement to print calling function..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1493

commit 6faa7618225f6e5e8e43bf04dae05929c3c6453f
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 9 02:02:54 2010 +0000

    glusterfsd: first time errors in volume file should exit the process
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1551 (glusterfs process doesn't exit when init fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1551

commit f0121a3d7896ace6d3d525c41d13f695bc8e25c9
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Sep 9 01:16:44 2010 +0000

    features/locks: Dump transport pointer also while dumping locks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1577 (dump transport pointer as part of dumping locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1577

commit 8e4650a662d0fddd1a67dff765bdf20046b70abe
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 9 01:01:04 2010 +0000

    mgmt/glusterd: op mem leak fixes
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1186 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1186

commit 9b226cc588eafd4932f2ade1c4e9280f4eca39bf
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Sep 8 13:37:52 2010 +0000

    mgmt/glusterd: Send volume-id during volume exchange
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1480 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1480

commit dcb434eb13996bb15ab1088fb445315faa3f8ead
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 8 10:40:19 2010 +0000

    gluster cli: don't print port in peer status
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1566 (gluster peer status port number)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1566

commit 43d36d456314f6d4e67c3d8f06cceb585f467915
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Sep 8 08:53:21 2010 +0000

    allow brick to be added in a plain replicate volume if a brick is removed
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1574 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1574

commit 5ed8eba1b15b538ca2c74d8130fb3f0a394921ec
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 8 07:32:54 2010 +0000

    rpc-transport/rdma: while notifying a reply, pickup the correct iobref from request context.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1567 ([rdma] data corruption due to read-ahead)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1567

commit 5ebe2fdfaea372c139db2f6d8afe32aa113c0f8f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 8 06:14:23 2010 +0000

    mgmt/glusterd: send response in case of friend not found
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1512 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1512

commit 440ffb55f08beabc7f2ee98f22852ce103613b30
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 8 05:18:24 2010 +0000

    mgmt/glusterd: Various replace brick changes.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 94d232ec8ab0dbbda643039fb3e41495cae5e7e9
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 8 03:59:50 2010 +0000

    protocol/client: send CHILD_UP directly fuse if parent is NULL
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1568 (Fuse init doesn't happen when vol file is changed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1568

commit 65ac3fdba1b21a103547d80f4446cfdcaf90139b
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 8 03:29:41 2010 +0000

    glusterd: preserve brick's port, retrive it while starting glusterd
    
    * this solves the problem of having brickinfo->port as 0 when
      when glusterd is restarted while glusterfsd processes are
      running
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1569 (data not available in client when glusterd killed and restarted.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1569

commit 8152690933c0c1168ccc7e79f3e366c3dfa780d8
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Sep 8 03:32:45 2010 +0000

    fuse: suppress wrong/confusing log message about graph setup failure
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1527 (mount time defunct window with remote volumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1527

commit faaf7cbab67ae57b58623bf82d11b835ace028cf
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 8 01:22:22 2010 +0000

    mgmt/glusterd: make glusterd to listen on default ports of both socket and rdma transports.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1555 (rdma remote port defaults to 6997)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1555

commit d2e2e69bb4a212df08c3c4469cb91a88d244ed9f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 8 01:20:43 2010 +0000

    rpc-transport/rdma: change the default listening port to 6968.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 37f01b2714bba57b28b9125c3652b8e35db6504a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 7 13:14:40 2010 +0000

    rpc-transport/rdma: honour port argument sent in rdma_connect.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1555 (rdma remote port defaults to 6997)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1555

commit 270dffa378a651369d6727fa38ae99934d953259
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 7 13:02:27 2010 +0000

    rpc-transport/rdma: fix memory corruptions caused by rdma.
    
    - disconnect notification should be sent before unrefing transport,
        since transport might be freed when unrefed.
      - set trans->listener. This member is used by rpcsvc to decide whether
        a listener or a new connection is dead.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1558 (glusterd hung)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1558

commit 171973d18d22e4f0f4117656c188d395bf3ac8a5
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 7 12:59:07 2010 +0000

    in case of failures, don't hang fuse mount
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1527 (mount time defunct window with remote volumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1527

commit 8c8e5b25779f68c646ec00003a7bb2101e55cbc0
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Sep 7 10:40:57 2010 +0000

    cluster/afr: Various self heal fixes wrt gfid.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 6b4784d5382fb3177e423751eb8d056e8bf384b4
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 7 10:13:29 2010 +0000

    fuse resolve to return if resolve not successful
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1406 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1406

commit ed561b78d9837b9f799ebb410bcc26b7e5413f33
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 7 09:30:29 2010 +0000

    glusterd: rebalance fixes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1481 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1481

commit 266df1a7d660dc0b824e6e60903536aff9242f4b
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 7 09:12:38 2010 +0000

    socket.c: more detailed info about mismatched msg type
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit db83e51918472c9f2bff7771edad6738acafbc26
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Sep 7 09:12:22 2010 +0000

    cli: fixed a minor log rotate failure msg
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1550 (volume log rotate failed.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1550

commit 1ec9ef73eedaabdc30d6b1c6200f0180118cf604
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 7 08:53:08 2010 +0000

    mgmt/glusterd: resolve bricks upon restart
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1286 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1286

commit 6066038c7bd96791143a63ed03a617c8cb7020f8
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 7 07:35:56 2010 +0000

    Volume info should display transport-type
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1230 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1230

commit f4b1b0af4732e397de3ab3fe2be1dd8bb83614b4
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 7 06:14:02 2010 +0000

    mgmt/glusterd: Disallow final brick remove of a volume
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1547 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1547

commit 962b9845ce57657c9abde24b5a4c647febfdfa67
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 7 05:40:00 2010 +0000

    Add gf_cmd_log msg for volume start
    
    Also fix existing gf_cmd_log msgs
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1556 (Add cmd log msg to volume start)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1556

commit 968fe7420a600fb9f83edd21576ab1b180d65d1c
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 7 05:29:36 2010 +0000

    mgmt/glusterd: create store handle in store create brick
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1372 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1372

commit 4f64c970ed1e334ba17413178eaf355f454c201f
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 7 04:29:55 2010 +0000

    Change cli volume/peer cmd's --help option to help
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1529 (need man pages for 'gluster' and 'glusterd')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1529

commit 95bafb5ad41458fbb16c680af94c2841c49c5322
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 7 04:29:34 2010 +0000

    Man page updates
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1529 (need man pages for 'gluster' and 'glusterd')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1529

commit 09f9bd0bdc3d0f055f83ef1fc76be065cb26b26d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 7 04:08:59 2010 +0000

    test: changes for the gluster cli
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1436 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit cb0352cd4f4748ee6e33bc64d2e2b09d09fe20eb
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Sep 7 04:03:31 2010 +0000

    cli: add script mode for gluster
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1554 (add script mode for gluster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1554

commit 406e42973feeae6b78626f2db19971dc8f79c25f
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Sep 7 00:38:22 2010 +0000

    DHT mount fails with parsing of subvolumes
    
    following error msg is seen in the log
    
    E [graph.y:296:volume_sub] parser: Volume 'new-dht', line 38: subvolume 'new-client-0new-client-1new-client-2new-client-3' is not defined prior to usage
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1536 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1536

commit 4f32456db7a0b9134f3a3433704533df213cc9ad
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Sep 6 23:59:48 2010 +0000

    Typo in log msg for volume create localhost
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1539 (Typo in error message)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1539

commit ed9a1cfa9873a0b069a8026d8852e44d94396d86
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 6 12:40:32 2010 +0000

    glusterfsd-mgmt.c: suppress a confusing log during rpc_clnt_init()
    
    * it complains about 'transport-type' not being given. fixed.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1545 (transport type rdma fails in glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1545

commit edad666e5165dec75ed1970d9e5f7927b43c5bd2
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 6 11:46:01 2010 +0000

    glusterd-volgen: write new nfs options in nfs.vol
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1548 (nfs should be able to get different uuid for different subvolumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1548

commit e3a44226b3ed746260c4f3cf30d2f9f930fb7349
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 6 11:45:31 2010 +0000

    mgmt/glusterd: volume to have 'uuid'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1548 (nfs should be able to get different uuid for different subvolumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1548

commit d38b2217393c460937505f30bd61576e7957f877
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Sep 6 09:01:24 2010 +0000

    cluster/afr: Fix hang in create when one subvol is down.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1544 (Create fails when 1 server is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1544

commit 716776f2e35d240db7b9731a4eda557a0be462f8
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:32:25 2010 +0000

    cli: change volume create help string
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1542 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1542

commit 6307567a26ecf296b5f806050867beb3c7cccd4f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:27:20 2010 +0000

    cli: check for argument presence before accessing
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1543 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1543

commit 8432a5bf65174144c58d3322066abeb85c9f3541
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:18:45 2010 +0000

    cli: prompt user before remove-brick and stop volume
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1538 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1538

commit 8d64ca70b4c2467d4ed8c76a9eae385abdebd7a7
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:12:36 2010 +0000

    cli: Only admin should run gluster CLI
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1546 (gluster commandline should be available only for super user)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1546

commit 698ff066c1d32d9774d7d662ab87528b85b66774
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:05:58 2010 +0000

    cli: Print volume type None as Distribute
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1535 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1535

commit 84f359537317a291e369b689083808a2e52379dd
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:05:21 2010 +0000

    cli: stripe/replica count should be greater than 1
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1534 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1534

commit c7c5a784c833af4018e628d5d7a2bdc40eb59dba
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:04:16 2010 +0000

    cli: In volume create check for presence of bricks
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1532 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1532

commit e807464de55fc366907c5bc8e3cf84b11da19e46
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 08:02:08 2010 +0000

    cli: print volume info cmd usage in case of parse errors
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1533 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1533

commit f0e6630fb33ba69c85e267848290389d60f25d21
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Sep 6 06:02:23 2010 +0000

    nfsrpc: Set THIS before vector sizing upcall
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1499 (GNFS from mainline Glusterfs-3.1-qa13 crashes while initiating SFS2008)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1499

commit 100bec738c83afab77b7b4654397335b1b9cefdf
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Sep 6 05:53:16 2010 +0000

    do not restrict the size of the subvolume string as it may corrupt the stack for large number of bricks
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1536 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1536

commit d96a02e48399c79ee5fc3581f28053fcf662fc5f
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Sep 6 05:50:06 2010 +0000

    Man page entries for glusterd
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1529 (need man pages for 'gluster' and 'glusterd')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1529

commit 1bdee1756e70ec2611e568776dd93c70f5e6feef
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Sep 6 05:44:14 2010 +0000

    rpc-clnt: fix memory corruption happening while encoding auth data.
    
    - buffer containing authdata pointed by rpc-request was allocated on stack of
       procedure rpc_clnt_fill_request, but was being used as source for xdr-encoding
       in rpc_clnt_record_build_record. Hence by the time auth-data is being copied
       during encoding of request, it might've been freed and hence contain garbage.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit d48378e4971b6b75f328923054959f6dc4dd89f6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Sep 6 05:41:51 2010 +0000

    debug/trace: use uint64_t variable while using localtime.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 737 (uint32_t ia_atime crashes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=737

commit f5b97620b10fff73693fbe8e7f98226b837cf5f9
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Sep 6 04:18:09 2010 +0000

    exit from the test for the first failure itself
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1436 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit 1e99540dc0a08527b6a0fb355667e39d3df6b3cf
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Sep 6 04:22:02 2010 +0000

    protocol/client: ignore rpc_clnt_destroy as temp fix for sigterm handling
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1517 (gluster volume stop - starts a new nfs server.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1517

commit 7150cb4e6a1703c143aaa517166a6b5ad7f758f2
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Sep 6 01:40:18 2010 +0000

    changes in fuse proc thread initialization
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1527 (mount time defunct window with remote volumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1527

commit 59baa88ab0f240e60f9d4044f4cf096a73d33caa
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Sep 6 04:07:33 2010 +0000

    doc: Fix make dist failure for gluster.8
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1529 (need man pages for 'gluster' and 'glusterd')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1529

commit 8b30d3459fd92d8c16a009d145142c5b8fe4fe65
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Sep 6 03:35:02 2010 +0000

    misc replace-brick fixes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 3cb231e7970222a7360f982934edc5c6f8475883
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Sep 6 01:58:48 2010 +0000

    Man pages for gluster
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1529 (need man pages for 'gluster' and 'glusterd')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1529

commit 386ea89d93497f805c77773515a735a11ef67f29
Author: shishir gowda <shishirng@gluster.com>
Date:   Sat Sep 4 01:12:58 2010 +0000

    Create volume adding transport type option rdma
    
    Adding transport type option to cli volume create command.
    This is optional, and defaults to TCP. The other transport
    supported is rdma
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1507 (need to add 'transport <type>' options to create brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1507

commit 4309c9b0d658185b1b7f07a98240b85870d35204
Author: shishir gowda <shishirng@gluster.com>
Date:   Sat Sep 4 01:12:09 2010 +0000

    Add brick hostname should not be localhost
    
    Add brick hostname should not be localhost or 127.0.0.1, but valid
     nodeid or ip. This will prevent volfiles being generated at
     respective glusterd's as hostname would be localhost
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1505 (volume create/add-brick requires ip or hostname for localhost)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1505

commit 4c87d30724b29a83c6a0f4a101468824fa76ac19
Author: shishir gowda <shishirng@gluster.com>
Date:   Sat Sep 4 01:11:34 2010 +0000

    Volume create hostname should not be localhost
    
    volume create hostname should not be localhost or 127.0.0.1. It
     should be a valid nodeid or ip. This will prevent invalid vol
     files being created on glusterd's when localhost or 127.0.0.1 is
     specified
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1505 (volume create/add-brick requires ip or hostname for localhost)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1505

commit 07d84f0f77ea336b3c3ae65907261ed3242feacb
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Sep 5 13:04:50 2010 +0000

    mgmt/glusterd: misc fixes in replace-brick and get volumes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 1fb0d35691d385fc7677e42d2e06bb089dbf0b8b
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Sep 5 13:04:14 2010 +0000

    cli: Display proper message when no volumes are present
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit be223c0df766cf1dae3672fc2e94604162ba9aa8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Sep 4 12:49:37 2010 +0000

    mgmt/glusterd: Add GET volume support
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit dba7332557fa0e8169c980b67a0f60a50f99bcf8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Sep 4 12:49:16 2010 +0000

    cli: Add support for GET volume
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 461dc0ce08d1deb6a9314e118bb511894d5390c8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Sep 4 12:48:55 2010 +0000

    protocol/server: set trans in frame->root
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1477 (server crash at afr_unlock_common_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1477

commit a582adf732d976e46eaad9def18f55dbec4d8674
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Sep 4 05:37:16 2010 +0000

    dont destroy the mempools in cleanup and exit as some other thread may be refering to it
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1523 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1523

commit eef8162e92149794298146fe881789da6a61cdf5
Author: shishir gowda <shishirng@gluster.com>
Date:   Sat Sep 4 04:58:17 2010 +0000

    Hiding add-brick/remove-brick type option
    
    Currently add-brick and remove-brick type option of replica/stripe
    along with count does not change the behaviour. Hiding the usage
    options.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1528 (Hide type option for add-brick and remove brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1528

commit 4f708eb8bbc80e5107fc3679b9f7ccac51883782
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Sep 4 04:07:58 2010 +0000

    rpc-transport/socket: fix memory leaks.
    
    - In the course of reading a single rpc-msg, socket_proto_state_machine may be
       executed multiple times (since sockets are non-blocking), hence wherever
       memory is allocated or referenced, checks should be added whether the memory
       is already allocated or referenced.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1438 (memory leaks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1438

commit 1972bd268f1a989d063701de2afee73c15059e01
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 3 14:10:03 2010 +0000

    remove legacy/protocol from the build
    
    * as its no more valid after gfid changes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 4432f46fa75bf62a6a8e9295f9792a73589f924b
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 14:01:29 2010 +0000

    gfid: server resolver changes to use gfid instead of ino/gen
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 2c400f60cad3ac0b9dbf1be06b48675d40fcc824
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Sep 3 11:46:21 2010 +0000

    gfid: protocol/xdr changes to handle gfid based fops.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 64443fa783c9c43a597440164b35fd8131b7f4d3
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 14:01:08 2010 +0000

    gfid: changes in distribute to handle uuids in iatt structure
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 71c66d9c9a36a28107cfc202aa38f51b3dde8731
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 14:00:51 2010 +0000

    gfid: handling of gfids in storage/posix
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 8a5e677bbd8bdec555e6699ec5b8b1a66fe8096d
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 14:00:32 2010 +0000

    gfid: set request gfids for new entries in fuse
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit a7fd7dbed9b995c173664bcadf3d2e5b6131e4ea
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 14:00:05 2010 +0000

    gfid: changes in symlink() prototype to have params dictionary with uuid in it
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 8b9a144414162413a399d59975fe3b7347907f4f
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 13:59:48 2010 +0000

    gfid: changes in mkdir() prototype to have params dictionary with uuid in it
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit d838e4496dec6b8889de47dd0ee31c4899ec7407
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 13:59:30 2010 +0000

    gfid: changes in mknod() prototype to have params dictionary with uuid in it
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit b304333f8686468b2d3b2c60e040b1667d8c38c9
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 13:59:06 2010 +0000

    gfid: change in create() prototype to have params dictionary with uuid in it
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit ac60a2a7f3c7b07830669e282d9fc796cbc78f38
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 13:58:48 2010 +0000

    gfid: changes in inode management
    
    - incorporate usage of uuid (gfid) as the key for finding inodes
    - deprecate inode number/generation number based inode_get
    - undo code specific to generation numbers (attic list etc.)
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 2822157056d8347518f7e1b8bf9ee04bea7286ae
Author: Anand Avati <avati@gluster.com>
Date:   Fri Sep 3 13:58:11 2010 +0000

    gfid: introduce uuid based handles for inodes
    
    gfid represents a gluter file id. This is a universally unique id
    assigned to a logical inode, independent of the inode numbers
    assigned by the various backend filesystems to that file/directory.
    The gfid of a file/directory will be the same on servers depending
    on the cluster translator in picture.
    
      The same gfid can be used as a handle across layers of various
    translators and across servers and clients. This was not the case
    previously as the cluster translators would pick the backend inode
    number from one of the servers and convert that into a logical
    inode number by performing some mathematical transforms.
    
      This new technique of addressing inodes also makes dynamic volume
    management have a more robust implementation as the file handles
    remain the same on all versions of the graphs, and allows for
    seamless NFS daemon restarts as well.
    
      This change makes way for server originating communication which
    was not possible earlier as the servers did not have any reliable
    way of addressing client side inodes at all. gfid solves this problem
    by preserving the same uuid as the handle on all the servers and
    across all clients
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit f5661d03f0f59cc2473f60232872ddafd325cd9d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 3 06:28:36 2010 +0000

    rpc-transport/rdma: notify rpc when pollerr happens, so that client side can try to reconnect.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit cc8e13e38931cabcf2d6361554717941bb82c7ab
Author: Sachidananda <sac@gluster.com>
Date:   Fri Sep 3 06:25:54 2010 +0000

    cli: Fix clang errors.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1145 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1145

commit dd7e5feef61f3e7c6360a410d69b063dee7b3df8
Author: Sachidananda <sac@gluster.com>
Date:   Fri Sep 3 05:49:51 2010 +0000

    cluster/afr: Remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1081 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1081

commit b3a4a0e88587c113137a838afbfab7069f1660df
Author: Vijay Bellur <vijay@dev.gluster.com>
Date:   Fri Sep 3 02:49:30 2010 -0700

    Revert "fuse: introduce pre-test micro-framework, check for execve-over-direct-IO"
    
    This reverts commit 588d807bdcbf5ed4df4d903428ab701479e9f8ac.

commit a0fbf69e7c7689466549db8815f2d87f5c16f664
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Sep 3 04:01:02 2010 +0000

    mgmt/glusterd: clear op ctx after cli response
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1513 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1513

commit e66ed16e8ce5d382ee56f55ca6153299e909e44b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 3 02:10:45 2010 +0000

    mgmt/glusterd: fix warnings during build.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1307 (gluster volume defrag <VOLNAME> status)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1307

commit 9459b3aeeb2f99f2f7f3a580e6e19d99db1c0678
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 3 02:05:52 2010 +0000

    cluster/replicate: fix warnings during build.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 960 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=960

commit a5aae54b1082a0a2c59d0e6e3e64b349d0bd6f17
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Sep 3 00:49:07 2010 +0000

    do not free the hostname from the response
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1511 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1511

commit c02661a69dfc0c6949666f972129e2983a52cb1f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Sep 2 08:05:36 2010 +0000

    mgmt/glusterd: retrieve version upon restart
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1265 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1265

commit 64c230aebd867c84a8320f1d98976bb102727413
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 2 07:57:45 2010 +0000

    check if the export directory is present only on the brick being added
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1510 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1510

commit 588d807bdcbf5ed4df4d903428ab701479e9f8ac
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Aug 27 09:39:33 2010 +0000

    fuse: introduce pre-test micro-framework, check for execve-over-direct-IO
    
    The presence of some potential FUSE features in the actual kernel-side FUSE
    implementation we run on is not always straightforward. More precisely, it is
    straightforward only if there is a dedicated feature flag or protocol revision
    number. In the other cases we are left to clumsy and platform specific hacks
    which wire in 3rd-party software revision numbers into our source... at least,
    if we insist on sticking to (the otherwise venerable) KISS principle.
    
    However, here we go for another route, loosely inspired by the way autotools
    provide an abstraction layer for our build system over the gory details of
    platform specific build environments.
    
    At start time, we use a preliminary set of FUSE operations which overlay the
    standard ones such that apart from the "usual stuff", they also present some
    synthetic files to the FUSE client (kernel). Then we spawn some test programs
    which perform the needed tests on these synthetic files to evaulate the FUSE
    implementation in terms of the features in question. According to the result
    of the test programs, we set the respective parameters of the fuse xlator;
    when the testing phase is over, the FUSE operation set is replaced by the
    standard one.
    
    As of now, we use this approach to test whether execve(2) works with
    direct I/O. If yes, and if glusterfs is used with --enable-direct-io-mode,
    then we let direct I/O for files opened for reading; if no, then we restrict
    direct I/O only to writing files.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 801 (Direct io-mode support and related changes in caching translators.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=801

commit 77db91866e9e8b333017e3bdb3079d024bb94818
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 2 07:04:48 2010 +0000

    rpc-transport/rdma: when rdma msg of type RDMA_ERROR is recieved, disconnect transport.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1462 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1462

commit 06ef40a683393ee086a74fb56a6e168b550fd716
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 2 07:27:18 2010 +0000

    mgmt/glusterd: fix rebalance with new option use-readdirp
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1508 (add-brick works but files are not distributed to newly added server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1508

commit fed472201fdf17ef57ea9b823b9215a0b3f558ec
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 2 07:26:54 2010 +0000

    cluster/distribute: add option 'use-readdirp' to force readdirp
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1508 (add-brick works but files are not distributed to newly added server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1508

commit ee7f340f73eb2b61d5d1f6b881eede3b39432c9f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 2 07:06:47 2010 +0000

    mgmt/glusterd: memory leak fixes
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1186 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1186

commit 0d1199ecf08cb513db7bcd26db672811207fe5cf
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Sep 2 03:08:55 2010 +0000

    cluster/dht: check for op_ret in dht_selfheal_dir_mkdir_cbk ()
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1503 (segfault in distribute during failover testing)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1503

commit a2b9b121d2670014fce07e0e3bdc311c587c0f2f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 2 05:04:32 2010 +0000

    dump total entries cached in stat-prefetch to state-dump file
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 4d14dffa00b134c1092133c90e92689f0ef82374
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 2 06:36:49 2010 +0000

    cluster/dht: fixes to handle 'fix.layout' attribute properly.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1508 (add-brick works but files are not distributed to newly added server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1508

commit 419e787880bacf8f3c85880a57a52ac4e532430b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 2 05:05:57 2010 +0000

    nfs3: Do not unref dst inode on rename cbk
    
    This gets done when the call state gets wiped. Doing it here results
    an extra unref causing a segfault.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1464 (fd leak after rename)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1464

commit 132d951d4392c4f0fd9aa012626b861b49ccaa8d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Sep 2 05:03:26 2010 +0000

    update the volume information first before checksum
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1504 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1504

commit 3e5c243396b6acf1a76d66d80c798466dc5caa55
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 2 05:24:48 2010 +0000

    cli, mgmt/glusterd: Added replace brick cli response
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1322 (Replace brick should show status of paused and abort states)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1322

commit 060380d460caa74b30eb6c0dedc8e25c64030acf
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 2 06:10:11 2010 +0000

    nfs3: Free vectored write args using FREE not GF_FREE
    
    ..because the file handle in write3args is allocated inside
    libc using malloc not memory accounting code in glusterfs.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1499 (GNFS from mainline Glusterfs-3.1-qa13 crashes while initiating SFS2008)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1499

commit fabe6417986dedd92adc2ac5d8d71cfd4dd918da
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Sep 2 04:02:52 2010 +0000

    mgmt/glusterd: support for GET_NEXT volume info
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1255 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1255

commit ea86a09143c5c59349ca82ddcbc2178a84cccde7
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Sep 2 04:03:12 2010 +0000

    cli: Changes for GET_NEXT volume info
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1255 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1255

commit 232d32ca93bf974734bc4bc4802f1430bb4b0c95
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Sep 2 01:56:02 2010 +0000

    mgmt/glusterd: multi subvol support for nfs xlator
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1319 (gnfs support in gluster command line)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1319

commit e94814533da94fb936355cde924ef3a6f6c11f46
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Sep 2 01:22:15 2010 +0000

    crash fixed in 'gluster volume log locate'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1506 (crash in log locate..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1506

commit 4c5e364c36baa92374eb0eac60dafb8da3786286
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Sep 1 23:44:54 2010 +0000

    Remove brick validation
    
    Added checks for duplicate bricks in cli arguments, valid bricks
    for the volume, valid volume name, and prevent removing of incorrect
     pairs for replica.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1486 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1486

commit 1d6e57d4a8bf4d69f724774d019f3cb7b4c0e1c3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Sep 1 13:01:23 2010 +0000

    mgmt/glusterd: gnfs support in gluster command line
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1319 (gnfs support in gluster command line)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1319

commit 5772cbf49f331557a217f1e31b681afa8d94080a
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 1 05:18:39 2010 +0000

    mgmt/glusterd: Fix replicate/stripe subvolume count in volgen.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1497 (gluster volume create creates incorrect volume file)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1497

commit 736d553ed7f98f783074b98499de5fb3c024c795
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Sep 1 05:13:29 2010 +0000

    peer status returns duplicate peer info on restart
    
    removing the peerinfo file for hostname once peerinfo is stored
     in the uuid file name.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1498 (Peer status duplicate entries on restart of glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1498

commit e7b0551ef5eb9a17ab97c34fc148de880b546217
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 1 03:44:12 2010 +0000

    rpc-transport/rdma: set whether pollin data is for request/reply.
    
    - with implementation of call backs client and server can both recieve
       request/reply.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1488 (rdma client fails to connect to the servers)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1488

commit 222b98ee5c38cbe4119718603f0d8d9a3a2d7fbc
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Sep 1 03:12:56 2010 +0000

    check if the volume is already started before starting
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1496 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1496

commit 780023f5e567b9ff9573edc47d71a1c7282bdbb5
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Sep 1 00:01:17 2010 +0000

    mgmt/glusterd: send unlock upon commit failure
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1476 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1476

commit 25dc93419e882ba733841a18e8addc1c7a6a01ab
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Aug 31 10:25:51 2010 +0000

    cluster/afr: Break STACK_WIND loop when the call count is reached.
    
    Fix also has a check for self heal relevant to pump.
    Tested with dbench with AFR client and pump on server.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1443 (Crash in afr_nonblocking_entrylk_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1443

commit 70652df2f7780aa734119941ac54d88ae6de7ae9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Aug 31 12:52:34 2010 +0000

    mgmt/glusterd: memory leak fixes
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1186 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1186

commit e7cbae70c89c8813918d9deb3895cb6886cdaeeb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Aug 31 10:02:54 2010 +0000

    rpc-transport/socket: use xdr_sizeof instead of sizeof when trying to read vectored request/reply
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 0b6e1ca3694201814fa4e32d81fa281290fd8ad9
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 31 11:15:27 2010 +0000

    mgmt/glusterd: prevent a double reply for the same request.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1401 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1401

commit c9d43f40282af3b3b0c6675e587c573941192769
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 31 07:45:20 2010 +0000

    fixes in 'gluster volume rebalance'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1481 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1481

commit d1a277785af5d9d0e38d0576d2a9c69e27a232df
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Aug 31 08:57:19 2010 +0000

    check if the export directory is present only on the correct host
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1489 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1489

commit 6530488a49ed0c9395b091c42b148091075a9d86
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 31 07:51:14 2010 +0000

    'gluster volume log' feature added
    
    * 'gluster volume log filename <VOLNAME> [BRICK] <path>'
    * 'gluster volume log locate <VOLNAME> [BRICK]'
    * 'gluster volume log rotate <VOLUME> [BRICK]'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit da5bf7cf104cd060b2f94d47132029689bfff685
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:37 2010 +0000

    nfs, mount3: Fix assumptions of this being child xl
    
    This is plain wrong. this must always be the xlator that receives the callback.
    Use cookie to access the child subvolume on which the fop was issued.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1410 (nfs uses this for child translator during frame creation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1410

commit 73c0aa4c27c50beea25be8de0b27b078dfcfa724
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:36 2010 +0000

    nfs: Create frames with frame->root as nfsx
    
    frame root was being set to the subvol on which the fop was to be performed.
    Apart from just being totally wrong behaviour, this also messes up
    mem-accouting because there THIS points to the wrong xlator resulting in crap
    addresses being dereferenced through the mem type index.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1410 (nfs uses this for child translator during frame creation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1410

commit d6f9504e01d444d625c24a5c2dcc5c7684c159d6
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:35 2010 +0000

    nfs: Set actorxl to enable setting THIS to nfsx
    
    ..for fixing mem-accounting for NFS in mainline.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1280 (gf_mem_set_acct_info goes into spinlock busyloop, never returns)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1280

commit 66beeeb7739531335ad0982b51886e82f7c8647f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:34 2010 +0000

    nfsrpc: Introduce THIS-setting support to fix mem-accounting
    
    Not setting THIS in nfs/rpc has been a blocker for NFS on mainline because
    without THIS set correctly to nfsx, mem-accounting goes looking into
    translators other than nfsx for nfs memory allocations, resulting in
    dereferencing bad addresses.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1280 (gf_mem_set_acct_info goes into spinlock busyloop, never returns)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1280

commit 2dd921a2848365f5fd538dd891b36a9f355ca78c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:33 2010 +0000

    nfs3: Close dst cached fd & unref inode on rename
    
    If the src file is over-writing an existing file and if the
    destination file is open, then  close the cached fd on the
    destination file and unref the inode for it.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1464 (fd leak after rename)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1464

commit 4b892368108b9c41449fb1185319cf3acf3c2ea8
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:32 2010 +0000

    nfs: Free fop local only after inode checks
    
    Fixes a crash that occurs because the nfs-fops code accesses
    a fop local after it has been returned to the mem pool.
    
    Generally seen when nfs load is so high that the mem-pool runs out
    of memory and starts CALLOCing.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1449 (NFS crash in nfs_fop_fsync_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1449

commit 83e7543be0bf8941cb6383c7e23b9bc0f54e67ba
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:31 2010 +0000

    nfs3: Return ESTALE when going beyond fh-hashcount or max-hashes
    
    During fh resolution, if we go beyond the max hashes support by
    gnfs or if we go beyond the dir depth specified in the filehandle,
    then return ESTALE.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1378 (Deep directory creation crashes gnfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1378

commit 0f40d735c09f2fb09bcf0d1678250e70a40ca56f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:30 2010 +0000

    nfs3: Logging and comments made more accurate
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1378 (Deep directory creation crashes gnfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1378

commit 1cd5a6fbd345b450a0e69041b53d92fb04fdcc5a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:29 2010 +0000

    nfs3: Support hashcounts larger than hash array size
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1378 (Deep directory creation crashes gnfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1378

commit 217fb3e2acbb221668ad5d54ef4067a2bac47c4a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:28 2010 +0000

    nfs3: Unref dir fd once usage ends in hard fh resolution
    
    There are three conditions when a dir fd_t needs to be unrefed
    when:
    
    a. the inode being searched is found as the candidate entry,
    b. we have exhausted all the entries in the current dir,
    c. we decide to step into a child directory because of a hash
    match.
    
    This decision is made in nfs3_fh_resolve_check_response.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1397 (Cached dir fd_ts are a leakin')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1397

commit e1422d796fefd6a3ae599507e71efdb922eede02
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:27 2010 +0000

    nfs3: Dont ref dir fd_t used in hard fh resolution
    
    ..because the extra ref was under the mistaken assumption that
    directory fd_t will be cached even during hard fh resolution and
    that is not the case.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1397 (Cached dir fd_ts are a leakin')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1397

commit 713fd9536459f730450fc06177c0feea6d6bdd28
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 31 06:50:26 2010 +0000

    nfs3: Dont ref cached fd after fd_lookup
    
    ..because fd_lookup returns a ref'd fd_t.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1397 (Cached dir fd_ts are a leakin')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1397

commit f6285605745d566bf7c43599285783f9409b7315
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 31 06:17:44 2010 +0000

    Add fuse.glusterfs to PRUNEFS variable in updatedb.conf(5)
    
    Append fuse.glusterfs to PRUNEFS variable in updatedb.conf(5).
    updatedb(8) should not index files under GlusterFS, indexing will slow down
    GlusteFS if the filesystem is several TB in size.
    
    Plus some whitespace cleanup.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 538 (disable glusterfs mount from updatedb.conf)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=538

commit 9c11d4f68d05180b602cf1e40aad7c708bb5c0a6
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Aug 31 04:10:46 2010 +0000

    Log all commands from glusterd
    
    Logging all commands processed by glusterd which causes some
    change. the log file is @ /etc/glusterd/.cmd_log_history.
    
    gf_cmd_log() is used to write to this log
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1404 (need a dump of all the op/mgmt commands)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1404

commit 4ae3853d857e584189289b33f8ba929fbd9cc7e1
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Aug 31 04:10:17 2010 +0000

    Add command logging facility for glusterd
    
    Added new command logging facility to gf_cmd_log() which can be used
    to log all commands to a .cmd_log_history file situated in the
    glusterd working directory.
    
    Accepts 1 st argument a domain string (e.g: volume, peer..) followed
    by msg string (similar to gf_log)
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1404 (need a dump of all the op/mgmt commands)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1404

commit cd5d2fc036003eb0c1a7f91755d3f5aa327067b4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Aug 31 03:20:29 2010 +0000

    rpc-transport/rdma: By default, enable building of rdma only if libibverbs is installed.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit e41b82c5704b0a9caba7c511688c9a152c5f2b0f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Aug 31 03:09:36 2010 +0000

    rpc-transport/rdma: free ioq entry even when churning of message fails.
    
    - An ioq entry is added to ioq-list only when it is not processed due to lack
       of quota. For all other cases, it should be freed to avoid memory leak.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit e1afe36eb3b006be12e7d7a5b87ff181c6da1250
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 31 01:17:56 2010 +0000

    fix a crash in cleanup_and_exit ()
    
    * fini() was being called without proper 'THIS' being set.
    * in protocol/client, a frame was getting created after frame
      pool was destroyed
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1030 (mount directory is not unmounted after killing glusterfs process)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1030

commit ddafbca363a5b0f0d8d1f11aa35e250d2c2c91bd
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Aug 31 01:12:56 2010 +0000

    fix typo in commandline help message
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1482 (typo in help message)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1482

commit a29aec5fb2c6f6dd1d8e24049c282353c7f5db0f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 31 00:59:47 2010 +0000

    mgmt/glusterd: Update store on start/stop volume
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1480 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1480

commit 507ee7301f2372a20c28897d60e1ec753539d886
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Aug 30 08:24:50 2010 +0000

    fuse: have the fsname passed to mount(2) include the volfile id
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1478 (show volfile id in mount(8) output)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1478

commit 1a1052461546576092f2f3b90c1f0f66817b18c2
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Aug 30 16:05:16 2010 +0000

    mgmt/glusterd: Return replace-brick status
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1322 (Replace brick should show status of paused and abort states)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1322

commit 80d091411f6d4b9bc6bd5f19c921bdb295611b5d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Aug 30 05:52:27 2010 +0000

    mgmt/glusterd: fixed volgen creation problems
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1454 (Remove brick unsuccessful - wrong volume info)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1454

commit 61bed5ef8b8ebda1ffac737a5526b8187852bc2d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 30 08:04:24 2010 +0000

    Add rdma as valid transport type for client and server protocol.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 06607a4de8c4414bb102d61b9cf6307d8da020bb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 30 08:04:07 2010 +0000

    changes to client to make use of the rdma functionality.
    
    - preallocate buffers in client and pass them to transport layer whenever a
       large response is expected.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 300b4fefcbb5a5ced4f0554e109679e44cdf44ea
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 30 08:03:52 2010 +0000

    Bring in new transport rdma.
    
    - rdma is new transport and improvement over current ib-verbs. It uses
       rdma-read and rdma-write for efficiently transferring large buffers.
       For more details please refer to rfc-5666 and rfc-5667.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 55bbf23b3a608f67b7a05939f4205049e92d081a
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Aug 30 03:54:32 2010 +0000

    Only admin should be able to run gluster command
    
    Checking for port number to fail any requests coming in
    from client. if port is >1024, then fail the requests
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1403 (only admin (uid 0) should be able to run 'gluster' command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1403

commit 8e4d735b67c78f10fd752f2b48981843595e67b5
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Aug 30 01:44:00 2010 +0000

    glusterfsd: call fini of fuse and all active xlators in cleanup_and_exit()
    
    * handles the case of stale mount point in case of killing glusterfs process
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1030 (mount directory is not unmounted after killing glusterfs process)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1030

commit baebaab45980e63f85622e70363fe898cdc572ad
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Aug 30 01:36:33 2010 +0000

    Volume Add-brick validation for exports
    
    Added checks for export already in use, duplicate exports in command,
    and check whether exports are valid.
    
    Also, cleaned up error handling in glusterd_handle_add_bricks
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1457 (volume add brick validation for export)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1457

commit 27f39a7c9d10e836295ae4ad1a88d1f0a911079f
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Aug 30 01:16:05 2010 +0000

    mgmt/glusterd: remove volfile, brick file upon remove-brick
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1475 (glusterd should delete brick related files upon remove brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1475

commit a2dd1e8702eb8dc7234d8262e34182adf1f0573c
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Mon Aug 30 01:33:14 2010 +0000

    Provides the ability to filter the output of state dump
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 828 (glusterdump filled up the /)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=828

commit fb3cb751f18a931d2a61d168fa13bf8ec3b45e1a
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Aug 29 07:08:37 2010 +0000

    mgmt/glusterd: handle port allocation so ports are reused for same brick
    
    * if 'brickinfo->port' exists use it instead of pmap_registry_alloc(),
      hence a brick after stop/start starts on same port
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1473 (reuse the ports while starting 'glusterfsd')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1473

commit 127dd2ada6e06abf0761ea647f7ae18a5de78e4f
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Aug 29 06:43:58 2010 +0000

    gluster{d,fs,fsd}: add logrorate functionality to SIGHUP
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1472 (SIGHUP should do 'logrotate')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1472

commit 157560b6dce9cf790e8405ce895d80f4efab1539
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Sat Aug 28 06:02:54 2010 +0000

    cli, mgmt/glusterd: added volume stop <VOLNAME> force functionality
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1361 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1361

commit 48055db6c1b8e669e6c83cc3e579569f05629026
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sat Aug 28 05:23:28 2010 +0000

    mgmt/glusterd: Fix some more options in volgen.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1455 (df command hangs before showing the gluster mount)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1455

commit e38fcf1f24b963f3fae9447e77bbc16a422739ae
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 28 02:18:47 2010 +0000

    dump the volume file details in log file if graph init succeeds
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1468 (after dvm changes, volfile info is not dumped in logfile)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1468

commit 9478240b8bfc42e444d9380aeeffb015d8e75b7e
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 28 02:02:51 2010 +0000

    afr: enable metadata self-heal by default
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1467 (enable the metadata-change-log by default)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1467

commit 5c7fb40b7fc592c8eedeeb91a96d0d89fb7b38f9
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Aug 28 01:50:37 2010 +0000

    change the path to brickpath while creating the pidfile
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1409 (Gluster add brick fails if all the bricks are local)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1409

commit 3ff1dbc7ad46427f175e1592a63b14ad8493c350
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Aug 28 01:10:02 2010 +0000

    performance/stat-prefetch: while removing an entry from cache, remove it from caches stored in all opened fds.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1414 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1414

commit 4a62b116eff66068bb16020093057708f4e106f8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Aug 27 11:55:29 2010 +0000

    mgmt/glusterd: look for local hostname in is_local_addr()
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 20e48cac3ced9df6af761ab85e18e2da77b0c920
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Aug 27 09:06:13 2010 +0000

    check for ENOENT after unlink system call in stop volume function
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 8cad5c4f10ae431914e015c79986470ed75319e0
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Aug 27 09:30:46 2010 +0000

    change the shell to bash form sh
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit fdc016fabed01e8497ffe281d7f35708b0eb25cd
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 27 09:28:37 2010 +0000

    fix notify mechanism to send CHILD_UP to fuse
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 18482a0d744a222fba6e235a1c6f2c30e27e8c03
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 27 09:06:29 2010 +0000

    protocol/server: fix a static buffer free.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 71622b82d95a3d2a4d0db9be1ec57939bebc9cdc
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Aug 27 07:22:24 2010 +0000

    volume create should not succeed on invalid export
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 899bebbb01220178d94dc3a669bd1ebbff800c25
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Aug 27 07:19:02 2010 +0000

    mgmt/glusterd: allocate hostname before dict_set_str for transport
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 8071909e84b6a479a6b5be1eddd15e8b16fc1a80
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 27 06:45:38 2010 +0000

    rpc: server to client callback mechanism
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit fd282c4299a5354aa272345e312ac600d9dcc680
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Aug 27 05:55:02 2010 +0000

    Volume create checks for used bricks
    
    Added check for create volume from using bricks already in use.
    Also cleaned up the error handling fixes in glusterd_handle_create_volume
    
    Volume create should now fail if a brick is specified that is already in use.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit cd5578895e7a218518ed20eaa34c6d833ea65aaa
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 27 04:49:34 2010 +0000

    mgmt/glusterd: fixes in volgen file paths
    
    * fixed argument to few xlator options generated by volgen
    * commented out many options which we want to be default
    * pid file and volume file name to contain export path info in them
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 07873893ad88e961cd0736872700f2bdc746d49c
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Aug 27 03:57:53 2010 +0000

    Misleading probe message for friend
    
    Progress with probe if host already is present in the list and
    state is not default or request received.
    
    To test, probe from on host, on the other host, do a probe back to
    host1. This should now continue with probe for the first time. Second
    probe should return already friend msg.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit c97156833355697a381e5e6a1c14142d8c9f3593
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Aug 26 12:17:37 2010 +0000

    cli, mgmt/glusterd: validate brick
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 228d11a9c91a5f5be9a2827a93cc5b7afef2d96a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Aug 27 00:33:31 2010 +0000

    cli: command parse validation
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1431 (cli: check if arguments exist before the accessing them)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1431

commit fc8b3fcbe1ab7fa8a7b15437d49df287856f2e95
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Aug 26 13:31:23 2010 +0000

    cluster/afr: Hold ref on the right fd
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1365 ([3.1.0qa5-15] Self-heal doesn't happen from 1st subvolume to others)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1365

commit 7fc38ce7783891218a0cb83d233d579e64831e33
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Aug 26 11:42:24 2010 +0000

    mgmt/glusterd: free op ctx only if it is allocated
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 1236 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1236

commit 67d8b620186807f38277713930da2a1d1926d6d0
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 26 09:09:59 2010 +0000

    glusterd-pmap: trigger signout by RPC_DISCONNECT event
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1314 (portmapper functionality)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1314

commit 0b87986fb6c35771f1ee60a161d427725c954c38
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 26 08:13:06 2010 +0000

    glusterfsd: don't call pmap-signout in 'cleanup_and_exit()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1434 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1434

commit ee3f7b941f889619d0688372f93e31f7e6a7cf3b
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Aug 26 07:55:38 2010 +0000

    mgmt/glusterd: Use a C based volgen and support various xlator options.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1429 (Use a C based volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1429

commit 2d935ef9c8cba1dae93e8e7dc0238aa46358edc3
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 26 07:42:30 2010 +0000

    fix glusterfsd to glusterfs getspec
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1445 (getspec doesn't work from glusterfsd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1445

commit d23ea83d476d2d0a1672ff346a398a76952d7e09
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 26 07:40:07 2010 +0000

    rpcsvc: handle the case of null dereferencing
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1446 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1446

commit 77459d46b1b242e5a8a3f4beecfb922ee7df80b0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Aug 26 05:57:25 2010 +0000

    rpcsvc: fix double free happening when listener creation fails.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 9fe52c92ace1c8c1e6e016aad8bb14973d6c9dc0
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 26 05:53:41 2010 +0000

    glusterd: handle failure of 'getspec' in case of '-' in volume name
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1433 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1433

commit 44f187fad77512e6b9d22852b79dc9621d688798
Author: Sachidananda <sac@gluster.com>
Date:   Thu Aug 26 05:44:07 2010 +0000

    cluster/dht: Fix clang errors.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1069 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1069

commit e1c52f630af0691872eff97e8156307a2964161c
Author: Sachidananda <sac@gluster.com>
Date:   Thu Aug 26 04:45:46 2010 +0000

    glusterfsd: Clang error fixes.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1077 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1077

commit af7b57b3099d07be2469895e4c83e3fa4442777e
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 26 04:10:19 2010 +0000

    Cli volume create detect dup bricks
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1184 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1184

commit d36c42a35fcc95468d692e5e7dd00fa7ca17b653
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Aug 26 03:53:31 2010 +0000

    script for testing basic gluster commands
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1436 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1436

commit fabb7e5e5dab69689bde255225748f8513a09d84
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 26 03:32:21 2010 +0000

    Cli volume add-brick validation
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1440 (volume add brick validation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1440

commit 33dfb02e92eb64009d353057f567dec02295886c
Author: Sachidananda <sac@gluster.com>
Date:   Wed Aug 25 03:39:03 2010 +0000

    cluster/afr: Remove dead assignments.
    
    Signed-off-by: Sachidananda <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1075 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1075

commit f76af04e90a4a3bf7995315923330fdfab407b4a
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 24 12:30:57 2010 +0000

    cluster/afr: Remove dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1078 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1078

commit 763d114d6e803ec87a418fec6a7b7cdda8a119d9
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 24 11:07:18 2010 +0000

    cluster/afr: Clang fixes.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1079 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1079

commit 503821aca0454a825b6cbb64e8a74ac8820f18ce
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 24 06:43:54 2010 +0000

    cluster/afr: Clean up dead variables.
    
    Clang error fixes.
    
    Plus some white space cleanup.
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1080 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1080

commit d13ddaf872915e16de37acdd7ccd913f3077a95d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Aug 26 00:39:59 2010 +0000

    replace struct stat by stuct iatt
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1441 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1441

commit e541154b79f8632fa82fa5b4f8f27aa2cb4ea55a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Aug 26 00:30:03 2010 +0000

    transport/socket: free priv->incoming.request_info if not already freed after reading each message.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1438 (memory leaks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1438

commit fb7cfce92572cd827de99fc076b5bb883972a057
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Aug 26 00:29:21 2010 +0000

    rpcsvc: handle the return value of rpcsvc_create_listeners properly.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 7c7219fd881dd6485fbad2e80121a3c2dffd6d9b
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Aug 25 06:16:46 2010 +0000

    Cli volume create validation
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1185 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1185

commit 194ec62165c89a84ad7d36013dd77e981a374c93
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Aug 25 06:07:14 2010 +0000

    cluster/afr: Do not issue blocking locks in self-heal.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 960 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=960

commit c83b6f73f08eb81788dd1fe35c461b19dc9405df
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Aug 25 02:09:06 2010 +0000

    cli: print usage message when parsing of cmd fails
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1432 (print usage string in case of command parse errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1432

commit 606cf3e291029169ec8154dec52c9b5ec6afc455
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Aug 25 01:59:15 2010 +0000

    cli: check if the arguments are present before accessing
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1431 (cli: check if arguments exist before the accessing them)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1431

commit a0c874f09e294ec75a18a5436bd01eaa97f22f81
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Wed Aug 25 01:58:23 2010 +0000

    Help Added to the Gluster-CLI for all sub commands (some deletions in the old patch)
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1156 (gluster --help should display all the options)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1156

commit 5ad84d3decb201e587cca5de7dd0c2c13e6419f6
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Aug 25 01:40:56 2010 +0000

    mgmt/glusterd: check if the brick already exists in stage add-brick
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1289 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1289

commit fb0bb972dfac3c255c53ddc7b588b73a08883288
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 25 01:40:00 2010 +0000

    storage/posix: calculate the correct size of each dirent in readdir/readdirp.
    
    - In addition to posix, protocol/server also adds a check to make sure that
       iobuf allocated to hold readdir/readdirp response can hold all the dentries,
       rpc and proc (readdir/readdirp) header.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1430 (encoding of readdirp response fails occasionally)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1430

commit 36ae62ada88b8477994d17527868370a4634999e
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Aug 25 01:32:52 2010 +0000

    cli: print volume create command usage in-case of parse errors
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1263 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1263

commit 29a9b190148ac7f2bf83e381a9e8024b164904b6
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Aug 25 01:29:07 2010 +0000

    cli: validating if the arguments exist before accessing in volume create
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1202 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1202

commit 89e6c3ee0a031eec5090fe2396678769e08fb01f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Aug 25 01:18:38 2010 +0000

    legacy/protocol/client: fix namespace collisions.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1418 (Crash in saved_frames_put)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1418

commit edc92766239de2a3054df9e9ad2607a8955c6d0b
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 24 03:59:05 2010 +0000

    cluster/afr: Clean up dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1084 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1084

commit b4ce27c974c02c15bc51373cd93a11de593ceade
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 24 02:53:01 2010 +0000

    cluster/afr: Clean up dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1086 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1086

commit 4c3680ad355fa8c5f691eef73eec4f2677829340
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Aug 24 02:15:56 2010 +0000

    fix the typo present in sh_missing_entries_create function
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 905 (Typo in log message in sh_missing_entries_create of afr-self-heal-common.c)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=905

commit fbd4023aada9d51d9be1b9060ab90ae20cccf119
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 24 01:16:10 2010 +0000

    glusterd: avoid cleaning up rpc during peer detach
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1423 (Crash in gf_timer_call_cancel)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1423

commit 60dc724b3d5442b07f3be3b2d8b8edc7f48205a9
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 24 00:49:49 2010 +0000

    cluster/afr: Remove dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1087 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1087

commit cbdc4f6ba6f5e8e2ef0d40d9f6cf857dfd8b91df
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 24 00:42:39 2010 +0000

    fuse graph initialization related changes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1406 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1406

commit 80221e913e90d244c334edbbd51ad9bc05c0fca0
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 23 13:04:21 2010 +0000

    doc: Include transport-type in glusterd.vol
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1377 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1377

commit 40c39c390b3dee1a4906b3f1fcaab42beb9d8f19
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 23 12:56:07 2010 +0000

    glusterd: Inject right event during peer detach
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1215 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1215

commit df4a7d75765b042ddbda4cbcd419743a37767ec3
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 23 03:51:21 2010 +0000

    glusterd: support for volume version and cksum
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1310 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1310

commit 39dc05e370286a62428a94e3e7666e2eedaea941
Author: Sachidananda <sac@gluster.com>
Date:   Mon Aug 23 00:08:37 2010 +0000

    performance/io-cache: Remove dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1112 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1112

commit 436f2b329f41f28a65fc4898df5435f154bd6027
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 23 01:42:47 2010 +0000

    rpcsvc: allow creation of both rdma and socket for a single server transport.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 513 (Introduce 0 copy rdma)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=513

commit 0d33cce6f7bbb71abe0086469f2f726151b0e62c
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sun Aug 22 14:09:48 2010 +0000

    protocol/server: features/locks: Fix nonblocking entrylks, inodelks in locks and server.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 960 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=960

commit 63f9e2a49573a0b539c0082fd0c08c1b4d4db983
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sun Aug 22 14:08:43 2010 +0000

    cluster/afr: Use 2 phase locking for transactions and self heal.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 960 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=960

commit 37ec7db018979d04d02ae5670b53dbed7a498ba8
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 17 05:19:04 2010 +0000

    xlators/nfs: nfs3-helpers.c remove dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1115 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1115

commit 8f18a47a14ffc4456e470b15f6ad14f9dd10cd79
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 17 04:59:49 2010 +0000

    xlators/nfs: nfs3.c - remove dead assignments.
    
    Removed dead assignments and unused variables reported by clang.
    
    One of the reports uncovers a minor bug in gnfs.
    > Dead store  Dead assignment  xlators/nfs/server/src/nfs3.c  2860  1
    
    A separate bug is logged for the above report and assigned to Shehjar.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1114 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1114

commit a437f594608cd307ca2c25871b79966de54cc93f
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 21 01:54:30 2010 +0000

    gf_system: fork/exec instead of system
    
    * most of the glusterd 'system()' are replaced with 'gf_system()'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1292 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1292

commit ad0e7a86c256b6e49daddafd954809b6040804b2
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 21 01:53:42 2010 +0000

    glusterd: prefix added to gluster commands
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1283 ([3.1.0qa3] gluster volume create and volume start fail on when glusterfs is installed on prefixed path)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1283

commit daf868e13511d97492ca4ece5fe60a2a4f69a20f
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 21 01:50:31 2010 +0000

    portmapper program added to glusterfsd mgmt rpc
    
    * some bug fixes glusterd-pmap.c
    * also renamed 'fetch-spec.c' -> 'glusterfsd-mgmt.c'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1314 (portmapper functionality)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1314

commit c429e47ae3925d0bc1ca113e37d903410f3e043a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Aug 20 23:44:52 2010 +0000

    fix the wrong log message displayed by glusterd in remove brick
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1411 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1411

commit 6b55c3b072b5663a4709b79513ada9f44d8ab8c2
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 20 07:50:39 2010 +0000

    generate separate volume files for nfs in case of 'portmapper' mode
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1319 (gnfs support in gluster command line)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1319

commit 883913af305e2de2d51ebac083b359bafebb782c
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Aug 20 07:23:15 2010 +0000

    check whether xlator is NULL in FUSE_FOP macro
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1407 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1407

commit a81debc473fe5eddeba318c91715252238069b1e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Aug 20 05:37:31 2010 +0000

    performance/stat-prefetch: use SP_STACK_UNWIND instead of STACK_UNWIND_STRICT.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 993 (memory leak-in stat-prefetch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=993

commit a6cc486e5733bcbe1bf562d6a523a5dd334cdf81
Author: Sachidananda <sac@gluster.com>
Date:   Fri Aug 20 01:28:32 2010 +0000

    xlators/mgmt: exit if directory creation fails.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1408 (glusterd continues despite directory creation fails.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1408

commit c2518242ed0723b7fa6c09564a3330572e189d74
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Aug 20 01:16:21 2010 +0000

    Hide cli peer command port option
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1261 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1261

commit 1fd482cae739799d2cdb0ffe78b544c249784305
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Aug 19 11:50:08 2010 +0000

    cli: Fix issues in non readline mode
    
    Signed-off by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1300 (gluster core dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1300

commit a5dac1f49eb247d854348fe8ec54c33e664adf30
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Aug 19 10:42:33 2010 +0000

    rpcsvc: decouple creation of listener from rpcsvc_program_register and rpcsvc_init.
    
    - with this patch every program that wants to register itself with rpcsvc should
        also create one or more listener(s) and register with portmap (if necessary).
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 01c00dd2e1d3113acb3f20c5dc7c20fa8d286339
Author: Sachidananda <sac@gluster.com>
Date:   Thu Aug 19 09:42:09 2010 +0000

    libglusterfs: Fix warnings reported by clang.
    
    Fix errors reported by clang.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1088 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1088

commit 82cea5108995d3ce21cd6489edd6161e9b6568aa
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 19 07:22:15 2010 +0000

    Probe should not probe for existing friend
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1331 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1331

commit 074f03afb246eb56ad55355bd775adc16488baa9
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 19 07:21:42 2010 +0000

    Probe on localhost not needed
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1216 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1216

commit 84bc269be4d2415e7d39ed33fa9925fd54447814
Author: Sachidananda <sac@gluster.com>
Date:   Thu Aug 19 04:48:06 2010 +0000

    xlators/storage: posix.c - remove dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1089 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1089

commit ecd0a913dc7359c3dad6cb9188ac999a6613d8b3
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 19 04:33:07 2010 +0000

    protocol/client: fix ESTALE in statfs on root inode
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1397 (Cached dir fd_ts are a leakin')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1397

commit 12e997d86358f44ab3729e1619591d1c8d0a8dc5
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 19 02:42:18 2010 +0000

    protocol/server: remove default progport from the fop program definition
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1396 ([3.1prealpha3] Multiple glusterfs processes fail to start with different port nos)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1396

commit b1f5031a3aa7c733990d0441a921c0b100309304
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Aug 19 02:06:03 2010 +0000

    rpcsvc: change in port selection criteria for program to listen on.
    
    - give preference to port specified in options over the port in program
       structure when both are specified. This will enable us to run multiple
       glusterfs server instances on the same machine.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1396 ([3.1prealpha3] Multiple glusterfs processes fail to start with different port nos)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1396

commit f51252fa0d89556542fdfd190e8a94b28b013c36
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 18 14:23:02 2010 +0000

    rpcsvc: check for listener on default port used by mgmt (6969) while registering programs.
    
    - If programs have not provided a default port, rpcsvc tries to allocate a
       listener bound to default port. While registering programs, if programs
       have not given any port information, programs will be associated with
       either default listener or the one provided in options provided during
       rpcsvc_init, with latter given more precedence.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 03df0871493d111116f168ec5331bffe99f6470f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 18 09:11:12 2010 +0000

    rpcsvc: unref transport stored in request before putting request structure back to mem-pool.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit b189d31f61ac3436bf0ad9ae2bff13efccbc06d0
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Aug 18 08:56:56 2010 +0000

    fuse: prevent NULL dereference in case resolve on path failed.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1391 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1391

commit 1aa2219484e040a950d55d9414e2b7e77df37fe7
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Aug 18 08:57:22 2010 +0000

    rpc-transport/socket: proper cleanup and NULL deref checks.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1326 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1326

commit 4cefe9c27be2d6db9d688ff1c922bf65bf43f5a1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Aug 18 07:39:52 2010 +0000

    Modify the help message for volume create
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1229 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1229

commit 3c75958d1948753976405f848f59326fc1896c95
Author: shishir gowda <shishirng@gluster.com>
Date:   Wed Aug 18 07:49:15 2010 +0000

    Fix memory corruption in mem pool
    
    Added new interface mem_get0, which calls memset on the
    mem pool entries being returned.
    Gluster and Kernel compile should now succeed.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1393 (Gluster and kernel compile fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1393

commit 0b890833c8cba9bac71877e528d810eba91dd1e6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Aug 17 23:58:37 2010 +0000

    rpc: add rpc_req structure to request_info structure, used by transport layer to get corresponding request to reply received.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 4e01a54eaa6da1bd6817d62dcc51a75e22699e2b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Aug 17 05:35:42 2010 +0000

    rpc - cleanup and changes related to rdma
    
    - remove rpc_conn_state structure.
       - add a member to point struct rpc_req in rpc_transport_req structure.
         This is needed for rdma to store rdma specific per request data.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit d8a8a66523e06abc0f44e1cdfe528cbf28d881a9
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Aug 17 22:23:25 2010 +0000

    cluster/afr: rename should not consider ENOTEMPTY as failure
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1352 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1352

commit ad99cabe6ca5925513c3896dab6fad29df50d7cf
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Aug 17 14:52:34 2010 +0000

    rpmspec: include copying.gpl and copying.agpl
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1275 (Fix rpm glusterfs spec file for 3.1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1275

commit 7e6b5454ade0c4fdfae73b882662d1606b7acde6
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Tue Aug 17 12:59:57 2010 -0700

    Makefile.am fix for COPYING changes

commit 711ea846fd1c1a5f15ed7a54501ffd41097d0cf6
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Aug 17 10:37:21 2010 +0000

    rpm spec: rename glusterfs-main to glusterfs-core
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1275 (Fix rpm glusterfs spec file for 3.1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1275

commit 8e6be30d2233e766398bd03dedf2b576131804c3
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 17 09:44:20 2010 +0000

    client: Do reconfig upon failure
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1341 (glusterfs-volgen should behave differently for flag '--internal')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1341

commit c8e411f2c46970eceba45534322437f89ed8a543
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Aug 17 09:19:20 2010 +0000

    changed GNU General Public License to GNU Affero General Public License
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1388 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1388

commit 65e98c7e1d0d96cef2118bd93f8322a8a29ab96b
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Aug 17 06:07:17 2010 +0000

    cluster/afr: truncate should not treat EFBIG as failure
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1351 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1351

commit c0dfd786795a8704e92b8e35120780b8c8907f32
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 17 06:06:30 2010 +0000

    cli: block command hang
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1370 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1370

commit 08699df02322c5f8ec926edf367da4cb96b90ad3
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 17 05:38:25 2010 +0000

    xlators/performance: quick-read.c remove dead assignments
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1109 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1109

commit ed180da84f153b47373e109f445f6775f950cb69
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Aug 17 05:06:58 2010 +0000

    cluster/afr: Return correct flock structures correctly in lk fops
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1042 (Use correct flock structures in lk fops)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1042

commit 20cdb9ab09b96e92a2ded9999078b8462dffd8c1
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 17 04:50:59 2010 +0000

    glusterd: fix for a crash in add-brick
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1380 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1380

commit ab72e06f7bcf6a815424f67181d44e7a1a465846
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Aug 17 03:31:36 2010 +0000

    volume creation validation
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1267 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1267

commit 8bc0ae16215248f85c64070f2f8600e5ab59e9ae
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Aug 17 03:26:51 2010 +0000

    Do not allow all to be a volume name while creating volume
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1209 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1209

commit e5737546071bd1d38430503bb64b9998bd7870dd
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 17 03:37:46 2010 +0000

    cli: Implement help command
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1229 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1229

commit ead92558ee8ec71442b2fa2da1a0df197ee78467
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 17 01:46:43 2010 +0000

    xlators/nfs: rpcsvc-auth.c - clean up dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1119 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1119

commit d552322816e82b3bc14533ecec9b770a213e7530
Author: Anand Avati <avati@gluster.com>
Date:   Tue Aug 17 02:53:51 2010 +0000

    protocol/client: fix reconnection to happen on portmapper first
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1341 (glusterfs-volgen should behave differently for flag '--internal')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1341

commit 9eccb80f42328cff1e652b12e01a3b02898f5edf
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 16 11:47:04 2010 +0000

    glusterd: Fixes for add brick
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1374 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1374

commit 3af126d594c8e0710ba6a3fb4024224eb7f8e4b4
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Aug 16 07:26:33 2010 +0000

    rpm spec: Use only 3 rpms for GlusterFS
    
    Generates the following 3 rpms:
    1. glusterfs-fuse
    2. glusterfs-main
    3. glusterfs-ibverbs
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1275 (Fix rpm glusterfs spec file for 3.1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1275

commit 0ec245abd60928994e2afbeac73cb53c5af7a4cf
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 16 05:18:19 2010 +0000

    volgen: generate listen port in server for portmap mode
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1375 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1375

commit fac7244477c6f2537f9abf3e83abf5e77177e548
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 16 03:19:32 2010 +0000

    rpc: move handling of fragment headers to socket.
    
    - fragment headers are only specific to tcp and hence should be handled in
        transport-socket instead of by rpc layer.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 5065b0824ed01cca59501d74c227b136a5b0e65e
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Aug 16 02:37:34 2010 +0000

    mgmt/glusterd: cli: Various fixes for replace brick.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1304 (Free state info for replace brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1304

commit 659e2d938f4da023411114c13a14337c21083411
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Aug 16 02:35:40 2010 +0000

    cli: Cleanup replace brick operations.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1304 (Free state info for replace brick)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1304

commit 32041afec462237c44a557ccdc4a32c6e33bad96
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Aug 16 02:35:00 2010 +0000

    mgmt/glusterd: Cleanup replace brick.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1303 (Cleanup replace-brick state info)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1303

commit fa71c7ff9d23bff6e597a87c2c58d8b620594856
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Aug 16 02:34:32 2010 +0000

    cli: Cleanup replace-brick cli call.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1303 (Cleanup replace-brick state info)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1303

commit a2f198db704a52e6e805a5637dfa399513de02c2
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 16 02:10:15 2010 +0000

    glusterd: Fix for a crash during restart
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1369 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1369

commit 7ebf4817f3535c8b5e78a0edb3b40ed2843a305f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Aug 15 13:03:10 2010 +0000

    glusterd: Set appropriate directory permissions
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1291 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1291

commit cd8c7a98e0ccab7866c6deb9174b662584ef91c6
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sun Aug 15 12:39:05 2010 +0000

    cluster/pump: Save path (/) when abort is received in pump.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit c87c868f40f4c2f46892afebf9557cf3003dabe4
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 14 05:10:49 2010 +0000

    'gluster peer *' enhancement
    
    now 'gluster probe' will be 'gluster peer probe' and
    'gluster detach' will be 'gluster peer detach'.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1291 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1291

commit 2b8545f1a21efe5e9944bccdebdff49e22fb6e6b
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 14 04:36:47 2010 +0000

    new option to volgen '--portmapper-mode'
    
    * without which, it generates volume files in old fashioned way.
    * with portmapper mode, no port option is taken, and there will be
      one process per one export.
    * corresponding changes in 'mgmt/glusterd' is made
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1341 (glusterfs-volgen should behave differently for flag '--internal')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1341

commit dd6c4b0e0db5fbe05a0c7927c780c96d5a97a966
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 14 03:36:29 2010 +0000

    volume-id fix in mount.glusterfs
    
    * now user can give numrical volume names if needed.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1364 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1364

commit 78814d4a5451b4fbd83fa286a866d6e520f92d74
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Aug 14 04:31:38 2010 +0000

    portmapper: minor fixes
    
    * in bind, initialize the array index to port
    * in search, check if brickname is NULL
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1363 (crash is pmap_registry_search())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1363

commit 57af0c92e351516c4056404ce0f2255c06b3c032
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 13 07:10:25 2010 +0000

    gluster create volume: cli validation added
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1267 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1267

commit bce6e99400713a4ece37996376d28146aeebc3d4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Aug 13 07:03:47 2010 +0000

    glusterd: Check for DIR before readdir
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1323 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1323

commit 752cb30f695963befd95e0db1d56113c6cce976e
Author: Anand Avati <avati@gluster.com>
Date:   Fri Aug 13 06:04:35 2010 +0000

    portmap: crash fix while getting registry pointer
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1346 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1346

commit b2925e78a54e1aab7e2a06d40127c59cc922cf1b
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 13 05:58:51 2010 +0000

    cli cmd validation
    
    * check buffer/stack overwrite if there is large number of argument to
      gluster command
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1265 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1265

commit 42436eb494e29745bd5e63865085fc26316ddf57
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 13 02:33:37 2010 +0000

    if frame is NULL, don't continue to destroy it.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1272 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1272

commit 4f414b5c497541d8ab1ba8aa3edc38c2d468bc23
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 13 01:56:33 2010 +0000

    protocol/client: send proper errno when op_ret is -1
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1353 (gnfs crash on nfs3_fill_create3res)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1353

commit 16e313fba3830876410739113beb1f9ae5a9eade
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Aug 13 02:08:31 2010 +0000

    fixes read data corruption seen by patch b04d963e91f8b3c72343e1043d6ed8c68699c4fe
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1333 ([3.1.0qa4]md5sum mismatch of files on client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1333

commit 79ec0ccdfacf562f19c0c0959ed305ec204f71bf
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 12 13:08:38 2010 +0000

    fix the 'no logfile set' log during gluster process start.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1348 ('no logfile set' displayed when glusterfs is started)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1348

commit 11c210ea3fdb724af4ea8a221dffc20dad9924a0
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Aug 12 12:27:35 2010 +0000

    cluster/afr: Remove dead pump code in afr_lookup
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1347 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1347

commit d502952cbe42760bf27a9e6cf2c616b6d7e5d379
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 12 08:09:43 2010 +0000

    fix in cli notify
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1345 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1345

commit df72e61b29c8a574ce8db254f1fc33a0261a03bb
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Aug 12 06:19:40 2010 +0000

    cluster/afr: Avoid Null de-reference when post parent is NULL
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 857 (Crash in afr_sh_entry_expunge_entry_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=857

commit 9349f559dc715cc7598edfb09e95470464ea1acb
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Thu Aug 12 04:12:44 2010 -0700

    added glusterd-pmap.h to noinst_HEADERS in Makefile.am

commit 9d89f5bf0190037ce6e5e2b8c5bc35f67e421e88
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Thu Aug 12 05:05:03 2010 +0000

    protocol/client: query portmap and reconnect on new port
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1314 (portmapper functionality)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1314

commit 12ce6a962aee3674eb722a09241b43923712ee8e
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Thu Aug 12 05:05:02 2010 +0000

    rpc-clnt/socket: rpc_clnt_reconfig() API to support overriding of port numbers
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1314 (portmapper functionality)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1314

commit b69a4f1e31726260a07f883cefac28ed29cc6a12
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Thu Aug 12 05:05:01 2010 +0000

    portmap functionality in glusterd
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1314 (portmapper functionality)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1314

commit f862864468c9d11d646bdcc347a1121fe75a1917
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Aug 12 04:43:20 2010 +0000

    minor assignement errors reported by clang fixed
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1117 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1117

commit a207ab15d43d625b91d0976409c92514e4c77664
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 12 03:58:20 2010 +0000

    argument sanity checks added in inode.c
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1311 (crash  during nfs alpha test)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1311

commit a9383208a60163f49e87c88a86439acd06f8356c
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 12 04:49:50 2010 +0000

    client changes for 'gluster volume migration' to work
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1303 (Cleanup replace-brick state info)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1303

commit e0347526dd77f7171ae9da72fc92ca99a79dd282
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Aug 12 04:49:15 2010 +0000

    cluster/pump: Dynamically control sink connect and disconnect.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1303 (Cleanup replace-brick state info)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1303

commit e98ebc1da4f49fba2bcaaf3212b00058e615cf29
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Aug 12 03:26:39 2010 +0000

    glusterd: Fixes for detach
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1215 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1215

commit a6a2e3a86c0d4c0873e822a38769677df2050f11
Author: Kaushik BV <kaushikbv@gluster.com>
Date:   Thu Aug 12 01:57:04 2010 +0000

    log added in case of invalid options provided for the io-threads volume
    
    Signed-off-by: Kaushik BV <kaushikbv@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1033 (io-threads doesn't log its options)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1033

commit 78615ceea81479b38af43697766bcc04421a256d
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 12 01:54:38 2010 +0000

    logging enhancements
    
    * per translator loglevel introduced, if set, it will override process
      wide log level.
    * with extended attribute 'trusted.glusterfs.<xlator-name>.set-log-level'
      with the value being '<LOGLEVEL>', one can change log level of particular
      translator.
    * with extended attribute 'trusted.glusterfs.syslog' with the value
      '<BOOLEAN>', one can enable disable syslog for gluster
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 601 (Enable changing 'log-level' of GlusterFS process at runtime)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=601

commit 553aa029de1817ae182cc86c1d00f8eb8ff52b50
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 12 01:54:10 2010 +0000

    fixed some backward compatibility issues
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit aa17ab8aa1851ac8848b0e36c420f6dd09fe9616
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Aug 12 01:47:38 2010 +0000

    rpc: Cleanup reconnect timer while destroying rpc_clnt
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1334 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1334

commit d8bb87b4c7dd40adf4fe0ba0a0946483599e0acc
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Aug 11 05:58:31 2010 +0000

    rpc fixes
    
    * set THIS properly so memory accounting works fine.
    * also check for few pointers before dereferencing them.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1317 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1317

commit fe38de53620d2c8c9dd1050a377f05a315f125d8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Aug 11 07:45:29 2010 +0000

    cli: Use appropriate conversion for deprobe resp
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1215 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1215

commit e17db5e4f67779f2e5095018bfda6f3b477e38ba
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Aug 11 00:33:03 2010 +0000

    cli: Do not await connection for miscellaneous cmds
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1262 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1262

commit d30f7058780477239dc8fe1ad691f4661a4988e6
Author: Sachidananda <sac@gluster.com>
Date:   Tue Aug 10 11:16:59 2010 +0000

    Cleanup dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1085 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1085

commit ca938bbe6f50fc77cbcfb3ca47efef0feb8e7526
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 10 08:18:47 2010 +0000

    glusterd: Remove dependency on existence of peers directory
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1310 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1310

commit ced85cce0700d702640c66829a72822e430f1cca
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 10 05:55:49 2010 +0000

    glusterd: Remove incorrect check for open fd during store ops.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1321 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1321

commit b0f54a49164a1c618b9e207349bd96705b44dfa6
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Aug 10 01:57:45 2010 +0000

    cli: Introduce timeouts for command response and connection
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1262 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1262

commit 5f7018275bf8006ff758817037d03936b8a95d43
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Aug 9 07:42:02 2010 +0000

    glusterd: restore peer information upon restart
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1310 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1310

commit b8779318dd2d99e44f54de741beee32f55553e75
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Aug 9 05:43:01 2010 +0000

    fuse resolve related changes
    
    Now fuse is fully complaint with DVM, as even if there is a fop
    request on inode belonging to old graph, it will be resolved
    corresponding to new graph and operations will be performed wrt.
    new graph, which makes DVM truely spontaneous.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1240 (DVM: after graph change, inodes should resolve to new inode-table)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1240

commit 0b501ac95edc0ef5945228eb47e6482cfc4efa41
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Aug 9 05:38:46 2010 +0000

    'gluster volume rebalance' related fixes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1307 (gluster volume defrag <VOLNAME> status)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1307

commit 6ff316dca7c9eebab14e71b6ad0908c2e45a5ee2
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Tue Aug 10 03:28:50 2010 -0700

    fix build of nfs (cleanup of configure.ac)

commit 272dfb00a9bdb9d537183dd0cfed83f698f5351a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:42:01 2010 +0000

    core,glusterd: Solaris getxattr build fix
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1178 (Gluster mainline build fails on Solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1178

commit 3501c98d23a9dcc4e05e972cb8de600fc46e4bf9
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:42:00 2010 +0000

    build: ucontext on Darwin needs _XOPEN_SOURCE
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 85a5ae02a7e262ffb5f4f51d1ea063e2669b0556
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:41:59 2010 +0000

    build: Solaris sigwait needs _POSIX_PTHREAD_SEMANTICS
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1178 (Gluster mainline build fails on Solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1178

commit b56548d530a3c6b059906e2bd242e7845434e07b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:41:58 2010 +0000

    glusterd: Solaris build fixes
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1178 (Gluster mainline build fails on Solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1178

commit 6cf8c2114a691a9b3f0eb42164d51e7fa86d33ea
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:41:57 2010 +0000

    rpc-lib: Solaris build fixes
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1178 (Gluster mainline build fails on Solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1178

commit 3b2de50546579b43ead84cff98f5c74e7bf7f840
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:41:56 2010 +0000

    nfs/rpc: Solaris build fixes
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1178 (Gluster mainline build fails on Solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1178

commit 5eb7cabfe7835604d132e4850ca6b656427df57f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:41:55 2010 +0000

    nfs: Do not build nfs/rpc as shared library
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1274 (nfs fails to start)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1274

commit 0af39ff8d03173a7ba3df1b13476b7ed447131aa
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Aug 10 02:41:54 2010 +0000

    nfs, nfs/rpc: Rename functions to prevent gfrpcsvc conflict
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1274 (nfs fails to start)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1274

commit b0304d47f67aa8fa677e4898fa46b96df88c8322
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Aug 6 07:49:36 2010 +0000

    glusterd: Set right return value during delete volume
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1191 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1191

commit 4f4dcb98a7bd55e84b3bb1d0bdf57cdd9090fcee
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Aug 6 05:38:41 2010 +0000

    fix rpm spec file to build rpms for 3.1
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1251 (ping_pong tests make client go segfault after bailout)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1251

commit acdeed002d30209e0a058c2df0346d4f16c08994
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Aug 6 05:31:45 2010 +0000

    add pump xlator and changes for replace-brick
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1235 (Bug for all pump/migrate commits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1235

commit 453cb4bf0b70c876eb468def34054095cfd66359
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Aug 6 05:25:16 2010 +0000

    v2[PATCH BUG:1286] glusterd: Regain volume state upon re-start
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1286 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1286

commit 3f6e5e670b7c1e30c64f2f11419947bd8982d51b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 4 22:24:51 2010 +0000

    performance/io-cache: Disable caching when files are opened with GF_OPEN_NOWB
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1168 (Disable caching when files are opened with GF_OPEN_NOWB)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1168

commit e85069767b28fe12cf3dcc4ccf1a5cfc10753c4b
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 5 04:00:59 2010 +0000

    mem pool for call_stub_t
    
    Ran posix compliance test and sanity test
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit f9431f330e8f304e82d9b1443018987a926d56b6
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 5 04:00:14 2010 +0000

    mem pool for fd_t
    
    Ran posix compliance test and sanity test
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 767b6b7d3f5b5e96e13f459fae6260d7cb129403
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 5 03:59:38 2010 +0000

    Implement mem pool for inode dentry
    
    Ran posix compliance test and sanity test
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 305025fbf823007fe715ea1ae0bbe44102221663
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 5 03:58:37 2010 +0000

    Implement mem pool for frame and stack
    
    Ran posix compliance test and sanity test
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit d8a94293b142f963ad255e4fe9c2d1fafe3caeb6
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 5 01:58:46 2010 +0000

    Fix for seg fault in dict_unserialize if undersized buffers are passed
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1031 (dict_unserialize crash if undersized buffers passed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1031

commit b04d963e91f8b3c72343e1043d6ed8c68699c4fe
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 4 04:45:25 2010 +0000

    rpc: changes to glusterfs programs that can take an optional payload argument.
    
    - The existing interface required the transport to separate the procedure
        header and procedure payload into two different buffers. Making this
        separation can prove cumbersome for transports like rdma wherein the header
        and payload can be received in a single buffer (For eg., header and payload
        of write fop sent as inline msg using rdma-send). This patch delegates the
        responsiblity of separating out header and payload to programs.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 21e4580c24b3e4a1270ad482e1d905afffb00fba
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Aug 4 05:27:55 2010 +0000

    remove same process transport shortcutting mechanism in rpc
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1223 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1223

commit c6c504df9843d273805636df5f88aed8cde694b5
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Aug 4 05:47:31 2010 +0000

    cli: fix a stack buffer overflow error
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1279 (Buffer overflow build error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1279

commit 737782bb930dae296605d53ed8d25ee8dbb23d87
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 5 01:53:37 2010 +0000

    if rpc->status is not SUCCESS, don't decode the msg
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1753 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1753

commit d1d06c102cfb6ea04a5e6f7db414a00c1a8351e2
Author: shishir gowda <shishirng@gluster.com>
Date:   Thu Aug 5 04:44:20 2010 +0000

    Fix cli volume defrag command hang
    
    gluster volume defrag <volname> hang is being fixed. Also, if a invalid
     volname was specified, it used to create mount point and call gluster
     client mount on it. This is also being fixed
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1247 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1247

commit dc10948a186931f22df2b1d3b4053c0c6bcac1de
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 5 10:15:25 2010 +0000

    fix memory-leak in case of disconnections in RPC server
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1227 (memory leak in rpcsvc_conn_alloc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1227

commit f9f4c5722536faee3d9ecbd8b99ce138e724f401
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 3 08:06:43 2010 +0000

    make some not implemented commands return success
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1264 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1264

commit 1be4d5e16e38f142931a0df1e3d25ed492cb494e
Author: Sachidananda <sac@gluster.com>
Date:   Sat Jul 31 11:15:41 2010 +0000

    Remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1065 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1065

commit 76a28f5853947751bc4e1802446dfbde4d600b5d
Author: Sachidananda <sac@gluster.com>
Date:   Sat Jul 31 09:11:21 2010 +0000

    Remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1067 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1067

commit d048ec1c1a2abcd4bad3ea5cf07cac328e990ff2
Author: Sachidananda <sac@gluster.com>
Date:   Sat Jul 31 09:03:49 2010 +0000

    Remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1066 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1066

commit 8d7682cd5cfb22b06a4f11e2589137ebe85a4709
Author: Sachidananda <sac@gluster.com>
Date:   Sat Jul 31 08:56:10 2010 +0000

    Remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1068 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1068

commit b4cd88214effe7889b581489d3865ac080d25391
Author: Sachidananda <sac@gluster.com>
Date:   Sat Jul 31 08:43:51 2010 +0000

    Remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1070 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1070

commit 51947922e1803dc4fceb80190faf5e37dcb2b290
Author: Sachidananda <sac@gluster.com>
Date:   Fri Jul 30 23:28:05 2010 +0000

    Remove dead variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1106 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1106

commit 790a7cfcf57e89c45716c2657665ae187b7b3fb6
Author: Sachidananda <sac@gluster.com>
Date:   Fri Jul 30 23:25:06 2010 +0000

    Remove unused variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1090 (clang errors in the file features/locks/posix.c)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1090

commit 83b77d5eaa1f1658e86b639c39574c04fa3feb48
Author: Sachidananda <sac@gluster.com>
Date:   Fri Jul 30 22:31:20 2010 +0000

    Remove unused variables.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1107 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1107

commit 76acc9ad1c686d3f01a17ca73fada66334b86938
Author: Sachidananda <sac@gluster.com>
Date:   Fri Jul 30 22:07:50 2010 +0000

    Remove unused variables
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1105 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1105

commit 21e9722f79663cc8502bfa21ad8d722357f8d491
Author: Sachidananda <sac@gluster.com>
Date:   Fri Jul 30 10:05:14 2010 +0000

    Remove dead variables reported by clang.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1108 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1108

commit eba11d7a2e2718064e99ae3f155ccca395a39cb1
Author: Sachidananda <sac@gluster.com>
Date:   Fri Jul 30 09:22:51 2010 +0000

    Remove dead variables reported by clang.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1110 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1110

commit 543f9ef5754bf50bc1817cfe9ddc13201f4e009f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Jul 29 03:09:38 2010 +0000

    libglusterfs: Prevent multiple timer threads from being spawned
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1246 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1246

commit fac3ff8bfb3958a3bdc34dc9bff7cb281597e40f
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sun Jul 25 18:13:08 2010 +0000

    syncop: initial implementation
    
    Resending Avati's syncop patch with a few bug fixes.
    
    (please do not skip the IMPORTANT NOTES section)
    
    * Framework for SYNChronous OPerations
    --------------------------------------
    
    This patch provides a framework for performing synchronous operations
    over the underlying actual asynchronous GlusterFS FOPS.
    
    * Use cases
    -----------
    
    1. Convenient implementation of crawler thread in replicate/pump
    
    2. Convenient implementation of high level control flow in DVM
    
    * Background
    ------------
    
    All (almost) threads in GlusterFS are hosts for executing aysnchronous
    file operations using the STACK_WIND and STACK_UNWIND primitives - as calls
    and callbacks.
    
    While the STACK_WIND and STACK_UNWIND macros provide high control for
    efficiently implementing file operations in a clustered/parallel environment,
    there are tasks where the nature of the task itself is sequential and
    the execution performance of the task is not critical. In these cases the
    complexity to implement the task with STACK_WIND/STACK_UNWIND based operations
    as calls and callbacks is an overkill.
    
    * Introduction
    ---------------
    
    syncop: are wrappers around the STACK_WIND/STACK_UNWIND based asynchronous fops.
    
    synctask: a sequential task (a C function) which uses syncops.
    
    syncenv: an environement to schedule and execute synctasks.
    
    The synchronicity is implemented via ucontext.h based continuations.
    
    Execution of synchronous tasks is possible only in a synchronous environment.
    Therefore, the first step  is to create such an environment -
    
            struct syncenv *env = syncenv_new (0);
    
    This creates a synchronous environment, with a thread (scheduler) to host the
    synchronous tasks. Creation of this environment is generally to be done at the
    time of process initialization. Next is to spawn a synchronous task in this
    environment -
    
            int slow_self_heal (void *data);
            int completion_func (int ret, void *data);
    
            ret = synctask_new (env, slow_self_heal, completion_func, data);
    
    Here slow_self_heal is a task which is implemented using synchronous operations.
    When slow_self_heal() completes, completion_func() is called with the first
    parameter as the return value of slow_self_heal(). Both these functions get
    the @data argument as the same value passed to synctask_new().
    
            int
            slow_self_heal (void *data)
            {
                xlator_t *child = FIRST_CHILD (THIS);
                fd_t     *dir = NULL;
    
                ...
    
                dir = syncop_opendir (child, loc);
                entry = syncop_readdir (dir);
    
                ...
    
                return ret;
            }
    
    * IMPORTANT NOTES
    -----------------
    
    - calling syncops in code executing outside the synchronous environment will
      very likely cause and undesired blocking of the executing thread leading to
      deadlocks!!
      The synchronous environment is a special thread where such sleeps are safe,
      and these sleeps result in the scheduler to 'swap in' other synctasks.
    
    - syncops can put the task to sleep. DO NOT issue syncops while holding mutexes.
      This is very similar to the blunder of holding a mutex and doing STACK_WIND.
    
    - It works best when synctasks use only syncops. If a call_frame is created and
      STACK_WIND'ed, the callback would very likely happen in a thread outside the
      synchronous enviroment, at an undefined time - as expected. So note that the
      synchronous environment does not tame the notorious behaviour of STACK_WIND.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit cadd1256355f4e1a5bd43c3a71dbd6cb97dff66d
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Jul 29 00:46:08 2010 +0000

    fixes for spurious entry self-heal in afr
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 974 (Spurious self-heal?)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=974

commit c9b709917b3d549d544133d51e85dbf9287278d1
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Jul 28 12:17:47 2010 +0000

    glusterd: Bug fixes in add/remove brick.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1239 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1239

commit 40d3ad15856c88d93d16264aa1f6bb55806aafde
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jul 28 06:23:31 2010 +0000

    changes to rpc
    
    - use mem-pool for requests and saved_frames.
      - preserve the rpc_req structure till rpc invokes program's reply.
        This will enable us to store transport specific data that has to
        last till reply has come (eg., memory regions of chunk lists in
        case of rdma).
      - change signature of rpc_clnt_submit to accept rsphdr_vector and
        rsppayload_vector. The buffers pointed by these vectors will be
        from iobufs and these iobufs are added to an iobref which should
        also be passed as an arguement to rpc_clnt_submit.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit b8692a3c3cc8e0dab404664e0aeb6ebaea6ab6e5
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Jul 28 05:03:43 2010 +0000

    glusterd: Fix a crash when get volume fails
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1239 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1239

commit 550cdfbcf2a5300c926f87403e12f19424bffeac
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 28 04:23:57 2010 +0000

    fix all clang errors in xlator/protocol
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1092 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1092

commit 927aedbb556ee07250248181f52642eeb6de9e58
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 28 03:31:10 2010 +0000

    removed last few remaining 'ERR_ABORT's from codebase
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 966 (NULL check for avoiding NULL dereferencing of pointers..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=966

commit 753146c0ff4b1b55892b71b36d6ca97797867aaa
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 27 11:13:32 2010 +0000

    some check added to the variables after GF_CALLOC
    
    handles some NULL dereference problems
    (reported by clang when ran with code where '#define GF_CALLOC NULL').
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 966 (NULL check for avoiding NULL dereferencing of pointers..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=966

commit 0aae2c46579421b871919e93619273d9a9bc79fb
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 27 11:12:51 2010 +0000

    fix all the clang errors in 'rpc/*'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1133 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1133

commit b2b6281e3487d3d797ab7974df69790a28c443c9
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Jul 28 03:51:18 2010 +0000

    nfs3: NULL fdentry check before removing from fdcache
    
    Suppose a file name 1 is created and some data is written to it. After this
    another 512 files are newly created and written to. When the the 513th file is
    created and an fd_t opened for it, it results in 1's fd_t being replaced in the
    fd-lru with 513th file's fd_t. This is the correct behaviour resulting in all
    refs getting unref from the fd_t of 1 and the fd and all related state being
    freed.
    
    But, in some workloads, some refs are still pending even after the fd_t is
    removed from LRU, resulting in the fd still being bound to the inode. In
    nfs3svc_remove_cbk, while removing the inode state, we also ensure that any
    fd_ts in the cache for this inode are also removed. While removing the fd_t,
    this situation where the fd_t has replaced with another, even while a ref
    remains on the fd_t, results in a crash in the fdcache_remove path in
    nfs3svc_remove_cbk. This happens because the fd_ctx_get results in a NULL value
    because the ctx was already deleted when this fd_t was removed from fd-lru
    earlier. This patch fixes the crash by introducing a NULL check.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 885 ([NFS Xlator] Crash in nfs3_fdcache_update)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=885

commit 46037573958dbb3a99283ed22862e62f60f526ad
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jul 27 06:16:52 2010 +0000

    access-control: Fix O_CREATE determination check
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1167 (gnfs crash with  fio)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1167

commit 7ced5bf710bbbee3290845b7ee65b5c895c06e7d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jul 27 06:16:53 2010 +0000

    replicate: Set setxattr wait-count to child-count to avoid race
    
    A race is seen during a compilebench load against NFS where a NFSv3 MKDIR is
    immediately followed by a LOOKUP on the new directory. By the time this lookup
    comes in, the setxattr issued by distribute for the mkdir has not returned yet
    from all the replicas. Since replicate returns a reply for setxattr after
    receiving reply only from one subvol, the MKDIR is unwound from distribute.
    
    When the LOOKUP is received at distribute, the setxattr has still not completed
    at the second replica, whereas that is where the lookup is sent by replicate.
    Finding that the xattr is missing from the dir, distribute returns ESTALE to
    NFS, which return NFS3ERR_STALE to nfs client.
    
    This patch changes replicate setxattr behaviour by forcing replicate to wait for all
    children rather than one to call back before unwinding the stack.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 937 (compilebench fails on NFS+dist+repl+all perf xlators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=937

commit 045efc1f5d59d98fff28ea29039ead4015fe1e6b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jul 27 06:16:51 2010 +0000

    nfs3: Error returns must check for <0, not == -1
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 854 (nfs server didn't start)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=854

commit ba98d9f472979d4bd648933b7940eb20e3c82116
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jul 27 06:16:50 2010 +0000

    nfs3: Return ESTALE when fh resolver exhausts dirents
    
    During hard fh resolution, if a directory traversal goes right
    through to end-of-dir without finding a hash match, we need to return
    an ESTALE, not ENOENT.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 854 (nfs server didn't start)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=854

commit 5e67bfb1dbb279e210d7ad1310818ef4a08ab913
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jul 27 06:16:49 2010 +0000

    nfs3: Stop ESTALE from falling into SERVERFAULT
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 854 (nfs server didn't start)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=854

commit abbc27d2b1460a10d7168114f2252313b98e4a08
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Jul 28 01:57:44 2010 +0000

    cli: Init conditional mutex at the right place
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1205 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1205

commit 9460675a921d504a31088b0e0f42143cc7f2a56f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Jul 27 14:49:07 2010 +0000

    DVM: Changes in CLI output
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1220 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1220

commit 26cc6b015bb29f942194d1ca2a3dd21d5483d829
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Jul 27 08:48:49 2010 +0000

    DVM: Changes for remove brick
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1220 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1220

commit 232235a9ddeaf33159ee8af809efee440b06c6d1
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Tue Jul 27 03:13:55 2010 +0000

    cluster/afr: Logging improvement for self-heal
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1037 (selfheal information in normal logging mode)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1037

commit 7c3ee2fd042c56ef6f53159f1ae9dd9a8f91c6f4
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Jul 27 02:06:45 2010 +0000

    fix volume creation errors in replicate and stripe
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1228 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1228

commit 14f00f972b8dda94f7797ed71398c5e365883fd6
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Jul 27 01:54:39 2010 +0000

    Cancel ping timer if socket or ib error
    
    If the there is an socket or ib error, fail the ping request
     to prevent retries. Which  would cause active connections
     to be disconnected
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 907 (cancel ping timer in case of socket fd error or iberror)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=907

commit a7795fedd4ee2ed7de2dce89fd782ae20b03f6a4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Jul 26 12:10:08 2010 +0000

    cli: Changes to provide proper exit status for gluster commandline
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1205 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1205

commit f803fae036177c3b9d9513f5b6300d426366eb62
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Jul 26 07:07:24 2010 +0000

    cli: Fixes related to get brick-replace to work.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1187 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1187

commit 667b2496c3f29e24ed359a05b0f44df0d1894969
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jul 26 06:13:57 2010 +0000

    dht enhancements
    
    * create(filename@<distribute-volume-name>-<subvol-name>), will
      create the file in corresponding subvol of dht.
    * same for unlink()
    
    same logic can be extended to other fops if there is a need
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1200 (enhance distribute with hooks so lot of debugging can be done online)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1200

commit 4792bb9a6caa4c74b6facebaba9379694893070e
Author: Anush Shetty <anush@gluster.com>
Date:   Mon Jul 26 05:07:18 2010 +0000

    Set fdctx only if op_ret is not -1
    
    Signed-off-by: Anush Shetty <anush@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1218 (Crash in client_fdctx_destroy)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1218

commit 470127fba6ca05671bd6b2ef9c187877711bf6cb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Jul 26 02:25:09 2010 +0000

    Changes in pidfile format for start and stop volumes
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1217 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1217

commit a5534cc60911ca914111710e9faa3376b198c8e3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Fri Jul 23 06:51:05 2010 +0000

    cluster/afr: ignore errno from offline nodes during self-heal
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 904 (Error while self-healing directories)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=904

commit 931a59e2b9130c6e748f2b7193cd0c2ac5a557bf
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Jul 25 00:38:01 2010 +0000

    DVM: bug fixes in cli and glusterd for probe, start volume
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1187 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1187

commit ea294f8fd967e8fc6e77558ecf1ab4fd298b7c4f
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 23 03:36:01 2010 +0000

    glusterfs-volgen changed to create one volume per brick
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1208 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1208

commit 80e2bfb8e4aaf5e7ae6647f2df4be1af80ee8b0a
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Thu Jul 22 05:51:16 2010 +0000

    custer/afr added self-heal logging in normal mode
    
    Changes are made such that self heal
    messages are printed (filename, type of selfheal such as data/meatadata/entry
    selfheal and the cause which triggered the selfheal) in the log file
    when run in normal mode.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1037 (selfheal information in normal logging mode)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1037

commit dbab7f87b6fbcc4d1f518e6f98101331df51ce4a
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 23 03:13:48 2010 +0000

    client protocol should send the fops only after handshake
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1195 (crash in protocol server due to unauthenticated fop request..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1195

commit 9c2753d1bee735cb74968106c7ce8ca1460504c6
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 23 03:13:19 2010 +0000

    handle some NULL dereference in server protocol
    
    which can happen due to un authenticated clients sending requests.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1195 (crash in protocol server due to unauthenticated fop request..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1195

commit b12d471100bd7ade9b3a6c0d917e0416f1b62e9b
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jul 23 01:02:01 2010 +0000

    glusterfsd: fix bug in GETSPEC which would result in loading of -f volfile
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit be4dee16c18e262b168c74face54cf17ca13e2f4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Jul 22 04:17:35 2010 +0000

    Changes for Dynamic Volume Management
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1196 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1196

commit 5601c137674b4dabd39b1cf26a36327bfbc707a6
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Jul 22 01:25:44 2010 +0000

    free sh_priv->loops[i] in afr-self-heal-algorithm.c to avoid memory leak
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 992 (memory leak in afr_sh_algo_diff)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=992

commit c907de75c8f957700ebe52dea980bda5d551f438
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Jul 21 17:17:09 2010 +0000

    glusterfsd: ban specifying fuse in volfile
    
    "fuse-in-volfile" was defunct anyway -- it resulted in a broken mount which
    had all calls hang on it.
    
    So the challenge was either to fix it or remove it. It got thumbs down.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit d4a56de8bba96a150a0a59593187a317476a7b80
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 21 07:52:17 2010 +0000

    glusterfsd: move mgmt_init() to happen post deamonize()
    
    else results in loss of timer thread
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 7ad75da5e8cb57336380f688650547275b939c3a
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 21 04:23:15 2010 +0000

    cli: fix consistent behaviour with newlines in cli_out()
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 066778ac7994bb574bd49281e8b225c3cd378f44
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 21 04:00:27 2010 +0000

    cli: fix 'unrecognized command' error on empty command
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit d69b8b56d7be4a15e7eac9dcd45d9b19ac2dc0bf
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 21 03:54:16 2010 +0000

    glusterd: implement GETSPEC
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 74195df7a5bdc6ae9489d63a3b8157cbb2ddd8e2
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 21 03:53:53 2010 +0000

    mount/fuse: disable fuse support from volfile
    
    glusterfsd: implement GETSPEC functionality to fetch volfiles from server
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit feefd93f84c7a91365718e30e4e52d765e128f75
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 21 02:00:33 2010 +0000

    glusterfsd: make SIGINT gdb friendly
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 5342e3a819896c9ae01a959c580a7f0eb0b3ccb2
Author: Sachidananda <sac@gluster.com>
Date:   Mon Jul 19 06:17:58 2010 +0000

    Dead assignment cleanup.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1138 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1138

commit 3e34ad9388e3cf2493f3d75a760e6943f59dc55c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 20 02:40:58 2010 +0000

    add port as an optional argument to 'probe' command
    
    * there will be just 'one' glusterd per machine, but in case if its
      run on different port, then this option is useful to probe.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1074 (port related issues in 'gluster probe' command)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1074

commit 9e3b58a2abdee5c1cf748eb463042ca9ef6aac66
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 20 01:23:17 2010 +0000

    'glusterd' command
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit e235a743d2b4d409945770a6d5f803360932bd3d
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 20 00:23:23 2010 +0000

    fix mount.gluster so there is no fixed default port
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1171 (mount.glusterfs has old/stale port values as default..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1171

commit 24a8879abfd075836f064b688610c6616184eec3
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Mon Jul 19 07:37:06 2010 +0000

    rpc/rpc-lib added saved frame's call timestamp
    
    it will be good to have the time stamp at which the calls were sent to the
    server in the gf_log of saved_frames_unwind
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 908 (saved_frames_unwind() : print time stamp of when call was sent to server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=908

commit a3ed6014101d2bc3904041c1c7a062cdf6bdf7d7
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Jul 19 07:43:08 2010 +0000

    encryption/ features/quota change STACK_UNWIND to STACK_UNWIND_STRICT
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 00b18468235259e7813be53d758facf55c4ee28b
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 20 00:23:04 2010 +0000

    'gluster volume defrag' related bug fixes
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1073 ('gluster defrag <VOLNAME>' fails in mainline)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1073

commit d257c6ba46bfb874961124cd02a526a2cd969347
Author: Sachidananda <sac@gluster.com>
Date:   Tue Jul 20 05:15:56 2010 +0000

    Delete dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1113 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1113

commit fcf62afec2730e14372221e323127cc11dae46db
Author: Sachidananda <sac@gluster.com>
Date:   Tue Jul 20 05:03:59 2010 +0000

    Remove dead assignment.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1131 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1131

commit 6d25218a8cb0722e156de3fe73c2e5e577117a62
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Jul 20 04:25:49 2010 +0000

    performance/symlink-cache convert STACK_UNWIND to STACK_UNWIND_STRICT
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 0590f3b38519d022b88d43cb0a70962880bc3a9e
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Jul 20 04:25:17 2010 +0000

    performance/stat-prefetch convert STACK_UNWIND TO STACK_UNWIND_STRICT
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 3d50c10261b9d3128f54f01442364fc91a907f4f
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Jul 20 04:24:40 2010 +0000

    features/locks convert STACK_UNWIND to STACK_UNWIND_STRICT
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 22516806e1c0c7830362f8d7fe055037df0d09e8
Author: shishir gowda <shishirng@gluster.com>
Date:   Tue Jul 20 04:24:08 2010 +0000

    features/trash convert STACK_UNWIND TO STACK_UNWIND STRICT
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit a81a794c9311f90551277670c0f9d201bd96abfc
Author: shishir gowda <shishirng@gluster.com>
Date:   Mon Jul 19 06:15:34 2010 +0000

    debug/* Change STACK_UNWIND TO STACK_UNWIND_STRICT
    
    Also fixed log msg typo found in bug 1031
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 0985f3995e446e23ca6edc380b998581889ae5d0
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jul 19 06:10:34 2010 +0000

    dht: set 'lookup-unhashed' to ON by default (instead of 'auto').
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 826 (distribute option lookup-unhashed should be on by default)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=826

commit ddd614192d05c767012fccedb73b30cef5bf4927
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jul 19 06:09:57 2010 +0000

    volgen now takes 'num-replica' and 'num-stripe' options
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1155 (currently volgen doesn't take num-replica and num-stripe options)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1155

commit 8f8739ea6709128f1a01ad26f677e8da12e0c726
Author: Sachidananda <sac@gluster.com>
Date:   Mon Jul 19 06:08:29 2010 +0000

    Remove dead assignments.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1140 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1140

commit a6b90707bf68fe62bf115cfb143d9df69627cb64
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Jul 19 05:54:25 2010 +0000

    Changes for volume commands
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1161 (gluster volume start command segfaults glusterd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1161

commit 87ec1b72dac8f50f9eb4ba3b127baca19993ae94
Author: Sachidananda <sac@gluster.com>
Date:   Mon Jul 19 05:51:46 2010 +0000

    Dead variables cleanup.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1140 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1140

commit d20bf5113875b694b9dae0b75261feafc243c004
Author: Sachidananda <sac@gluster.com>
Date:   Mon Jul 19 05:12:53 2010 +0000

    Remove dead assignment reported by clang.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1130 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1130

commit 321dee291451dcb299b61dcd26fce21df8c3b074
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Jul 19 03:25:31 2010 +0000

    fuse: fix clang spotted C abuses
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1120 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1120

commit de3f20878d00759aa79fb1fea955997ce5207d04
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Jul 19 00:33:22 2010 +0000

    fix the errors reported by clang in io-stats xlator
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1132 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1132

commit c3b919783e16534f3dcb0844174503e77f90d707
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Jul 16 08:54:15 2010 +0000

    fix the clang errors reported in trace.c
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1072 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1072

commit ce0e4c3d6eb710f29cb02166fdfa9e6afb013df6
Author: shishir gowda <shishirng@gluster.com>
Date:   Fri Jul 16 08:37:29 2010 +0000

    return ENOENT instead of ESTALE for links in client for stripe
    
    Instead of returning a ESTALE for links and symlink return
     a ENOENT, as they only exist on the FIRSTCHILD, and any
    lookup fails in the other bricks.
    
    Signed-off-by: shishir gowda <shishirng@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1152 (ln on symlink returns NFS STALE error even on success)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1152

commit 56c182ca23a7552dfa4c19667f82ca1313fb9e55
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Fri Jul 16 00:23:31 2010 +0000

    dump total cache used in quickread in the statedump information
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 11cae38ac007ed55c2bc1217da1a80fc367100e8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Jul 15 06:05:52 2010 +0000

    Fix compilation issues when uuid/uuid.h is not present
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 2546b7f5bf1d747262d956cb233676c563423370
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Thu Jul 15 03:50:12 2010 -0700

    Revert "dht: perform revalidate on one subvolume"
    
    This reverts commit 97e060d04b6b86225264644ff8fef0459577a031.

commit bb209f56147878ac420e4d1915e989bb11d272a2
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Jul 15 00:33:03 2010 +0000

    Bring in uuid to contrib
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 47dc8def246c6338cb95e71b4656962a5f74ee90
Author: Anand Avati <avati@gluster.com>
Date:   Wed Jul 14 16:26:17 2010 +0000

    protocol/lib: rename files to standardized names and places
    
    -  move xlators/protocol/lib/* to rpc/xdr/
    -  rename CLI and glusterd XDR filenames
    -  remove xlators/protocol/lib (libgfproto1.so)
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 2865e149c48eb5ed028cffb12e1e5273b47f2b1d
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 14 14:27:54 2010 +0000

    remove dead assignments in stripe.c
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1071 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1071

commit 654a720eed0bc5faaeeaa4eb34f1cfc10df76230
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 14 13:58:20 2010 +0000

    proper way to do defrag of a mountpoint
    
    Usage: "glusterfs-defrag <MOUNTPOINT>"
    
    there are new features added to distribute with this patch:
    
    * bash# getfattr -n trusted.distribute.linkinfo <file>
      Gives output in the format "<hostname>:<directory>", if there is a
      linkfile present, where hostname is server, directory is backend
      directory where the actual linkfile is present.
    
    * bash# getfattr -n trusted.glusterfs.pathinfo <path>
      Gives layout information if directory, and info about actual
      location of file in backend servers, in the form of
      'hostname:directory'. (TODO: should extend it to all xlators)
    
    * bash# getfattr -n trusted.distribute.fix.layout <path>
      scales out the directory layout in distribute, so when new
      servers are added, layouts are fixed to include them.
    
    * removed 'scale-n-defrag.sh' as its no more required.
    
    * changed 'defrag.sh' to have a feature to specify target bricks,
      so defrag happens to only those nodes. moved the file to
      'glusterfs-defrag', which now gets installed to '${prefix}/bin'
    
    * storage/posix:
      takes new option 'hostname' so it can resolve to same hostname
      given during 'gluster volume create'.
      with 'trusted.glusterfs.pathinfo' posix returns the value in
      'hostname:real_path' format.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1073 ('gluster defrag <VOLNAME>' fails in mainline)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1073

commit e73a856e926465068f6f6cf5a0cace501589957c
Author: Pranith Kumar K <pranithk@gluster.com>
Date:   Wed Jul 14 07:11:28 2010 +0000

    v2 [PATCH BUG:1050] protocol/server Convert-OS-specific-lock-value-to-Glusterfs-lock
    
    server/protocol's getlk implementation needs to convert the flock on the system
    to glfs own flock before returning it to the client to prevent
    misinterpretation of the flock structure.
    
    Signed-off-by: Pranith Kumar K <pranithk@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1050 (fcntl F_GETLK lock calls do not return correct flock on non-linux systems)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1050

commit 32451a4dd02bdd95ec800d51267d2e6be43914a4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Jul 14 00:20:28 2010 +0000

    Fixes a crash seen in create volume
    
    Also includes some re-factoring changes.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1063 (gluster volume create command segfaults)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1063

commit 9186c9e84c857a0b1bfbfa4e7b46e9eb741186fb
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Mon Jul 12 09:03:04 2010 +0000

    typo error: should check for less than instead of greater than
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 6ef7f0e25fb7c76231b4d4ae05cbc45330de300d
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Jul 12 08:19:44 2010 +0000

    Changes in CLI and glusterd
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 9bee476eabb5034a27e994008a12ef684755d76c
Author: Anand Avati <avati@gluster.com>
Date:   Mon Jul 12 08:13:08 2010 +0000

    cli: move readline to separate thread
    
    move readline handling to a synchronous input thread to avoid deadlocks
    with poll loop
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit ce8cee660a5cda88ea58e362be01e50cbccfff27
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 9 03:14:13 2010 +0000

    provide a port option for gluster command line
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 9563c51ddeedee87a1d71defc20c0a7f06f24d23
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sun Jul 11 06:33:17 2010 +0000

    dump total files cached in quick-read in statedump information
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1059 (enhancements for getting statistics from performance translators)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1059

commit 915adb9c1291d140e57765b7fad0c5bb0e7d5ed5
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jul 8 08:16:13 2010 +0000

    gluster-CLI-and-mgmt-glusterd-added-to-codebase
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 7e489f3cc7f3eb738d2698dcf588bad0bdc12a8b
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jul 8 05:47:52 2010 +0000

    fix up OS X after dynamic volume changes
    
    Note that contrib is not needed to be in toplevel Makefile as
    its not a separate target, rather stuff is "pulled in" from there.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit c35f6bf8f735eaf35c950d7b7789f6b64ba2c8c0
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jul 8 05:46:50 2010 +0000

    minor option handling refactorizations
    
    - clean up ZR_* internal option defines
    - make argument order of glusterfs_graph_activate() aligned with
      other graph ops
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 6779d91ea8ee8bb8f337213b0be2d31e4fd62619
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jul 8 05:45:58 2010 +0000

    fix fuse volume creation from volfile
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit f605883c4fe99428c560a18a1051693f7aadf84e
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jul 8 05:44:05 2010 +0000

    fix up option handling
    
    After 79241696, the following anomalies came up:
    
    - --mac-compat and --read-only was rejected originally
      on server side, 79241696 cancelled this check
    - direct I/O option handling was interfered by 79241696
    - --mac-compat had no effect on Linux and does not compile on Mac
    
    Restore original behaviors.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit 2233d7d3c54bf2fc7dc291ae19d8516b44f6e6af
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jul 7 08:15:12 2010 +0000

    performance/io-cache: implement mknod fop.
    
    - mknod_cbk has to initialize ioc_inode context, since there is a possibility
        that open following immediately after mknod may not result in lookup before
        open fop.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1054 (Crash in ioc_open_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1054

commit c85998fec484a0060c2a7cbcbf7ed42a109c6478
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 7 08:05:58 2010 +0000

    make DUMP as another program
    
    * on server side, make it a rpc program.
    * on client its another program at protocol
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 44604ecf4bfbef991bfcf5f0524ff044177d81a1
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 6 10:05:01 2010 +0000

    assign proper 'fop' number to 'frame->root->op' on server side
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit f0578eb3acf0c14b519b74f87c693bd72c506b8a
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 6 08:47:25 2010 +0000

    Handle a crash in inode.c on 32 bit, big endian platform
    
    Thanks to  <tlisiecki@proximetry.pl> for reporting the bug and
    sending the patch.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 985 (Crash with SEGV in libglusterfs on 32 bit, big endian platform)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=985

commit 90717586363520bbb68e2ec4a7aa12272effa64e
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 6 07:12:11 2010 +0000

    removed 'fop->checksum' from codebase as its not required anymore
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 734 (keep only the working/usable code in build tree to focus more on development)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=734

commit 4e14d858bc51f99d89880364249344e1b957f400
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sun Jul 4 06:20:07 2010 +0000

    nfs3: Fix race updating op queue on uncached fd open
    
    The order of locking while performing async fd opens was resulting in
    a deadlock when a particular pattern of operations was generated by
    compilebench. This patch improves handling of those situations while
    locking the fd-cache, inode and inode queue.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1047 (Compilebench hangs nfs server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1047

commit 1a7f42d7fb73f464f18c4375e3b4ef8139f20d1c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 6 01:42:27 2010 +0000

    improvement to error-gen
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1051 (Use proper 'fop' indexing)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1051

commit d1b057ac65fb61cb6f0c25aafb7d1ba54c6fe36b
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 6 06:15:46 2010 +0000

    avoid repeating code
    
    'frame->local = NULL' is done in submit_reply, instead of doing in
    every _cbk (), of server3_1-fops.c
    
    also fixes bug=1052
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 22a79cd791a5d8baa3c623673ff7bd0bb62564e4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Jul 6 01:26:38 2010 +0000

    glusterfsd: Handle setting entry-timeout to 0
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1034 (rename() is not atomic)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1034

commit a45ac57e4e12a32f7136f22c2eb0519fbd61354c
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 2 12:48:10 2010 +0000

    allocate space for '\0' in string, while adding xlator-option
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1044 ('--xlator-option' is not working)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1044

commit 3ec73cb88e8a302e973f8d1a68bcaf3981512b20
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Jul 5 11:24:27 2010 +0000

    mount/fuse: Handle setting entry-timeout to 0.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1034 (rename() is not atomic)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1034

commit 43cdbc3756bde8c4c95dd3c3a89c802ec204c847
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jun 15 00:39:26 2010 +0000

    nfs: Assign incremental lk owner to frames
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 960 (Disk space leakage and fs corruption after VMs are vmotion'ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=960

commit a8ef67630c48dfec336cc2088ac78cb29074022c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jun 15 00:39:25 2010 +0000

    nfs: Support directory level exports
    
    nfsx has followed traditional approach of exporting whole volumes
    as NFS exports. The Platform requires and some users have approached us for
    introducing exports of only specific directories instead of full Gluster
    volumes. This commit introduces this support through two nfsx options:
    
    Option 1:
    
    =========
    option nfs3.<volume-name>.export-dir <subdir1-in-vol>,<subdir2-in-vol>,..<subdirN-in-vol>
    
    export-dir will allow the export of a particular dir as a single export
    by itself. For eg.:
    
    volume posix
            type storage/posix
            option directory /export/
    end-volume
    
    volume posix-ac
            type features/access-control
            subvolumes posix
    end-volume
    
    volume nfs
            type nfs/server
            subvolumes posix-ac
            option rpc-auth.addr.allow *
            option nfs3.posix-ac.export-dir /homes/shehjart
    end-volume
    
    A comma separate list of sub-directories will set up those dirs as separated exports.
    At the nfs client, the mount command will be:
    
    $ mount <nfsserver>:/posix-ac/homes/shehjart /mnt
    
    Option 2:
    =========
    option nfs3.<volume-name>.export-volumes <on|off>
    
    There can be situations where users only want the directory level
    exports and require that volume exports be completely disabled. The
    above option allows us to do this. By default, volume exports are
    enabled. From the earlier example, replacing <volume-name> with
    posix-ac, will disable mounting of the posix-ac volume as a whole.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 989 (Support directory exports in nfsx)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=989

commit 2f15ffd6b5beef9abd501c594bc3cb38c2683f77
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 2 04:55:28 2010 +0000

    NULL dereference fixes in code base after running with 'clang'
    
    * 212 logical (NULL deref/divide by zero) errors reduced to 28
      (27 of them in contrib/ and lex part of codebase, 1 is invalid)
    * 11 API errors reduced to 0
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 966 (NULL check for avoiding NULL dereferencing of pointers..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=966

commit 3dc79ca8e6119f5ff61058cc87f9a4fc251017ef
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Jun 18 02:18:02 2010 +0000

    performance/write-behind: explicitly enforce ordering of overlapping writes.
    
    - If there are non-contiguous offsets (offsets which do not start where
        previous write ended), wait for completion of previous writes to server,
        before sending new ones.
      - Send flush call to server only when all writes are completed.
      - If a file is opened with O_APPEND, at any point of time a maximum only one
        write call to server should be in transit. This is to avoid reordering of
        writes in the presence of afr which can result in data corruption.
        See bug #934 for more details.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 970 (extracting kernel tarball hangs midway.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=970

commit 01923eed1115e53c5be9fba3e72f75c7c631bf95
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 29 05:36:30 2010 +0000

    minor fixes in rpc + protocol
    
    * proper use of mem_acct_init in client.c/server.c
    * fentrylk_resume to be called instead of finodelk_resume in
      server_fentrylk().
    * handle the case of xdr decoding failure on server by sending the
      proper error reply to client, so there is no missing frame.
    * removed unwanted functions from server-helpers.c
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit c46f8452d75e2f1b4ab77306177f39bdbb4b232c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 29 03:39:16 2010 +0000

    backward compatibility of protocol
    
    * made most of the 'legacy' server and transport functions as
     'static' as they were getting cross linked with newer functions.
    
    * changed the name of few functions with prefix 'gf_'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 0da2a6d08cc8fc2315742d010c8a8cab38ef75bb
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Jun 28 02:49:46 2010 +0000

    Move rpc to top-level
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 2c5c3cedc096c36ef9d004ffa0cdb5324d2915e6
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jun 24 12:41:03 2010 +0000

    OS X: fix up rpc protocol
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 29893bcba579f7e37a6ace018ffda1c8abe45550
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 24 07:58:51 2010 +0000

    added proper mem-types to GF_CALLOC in protocol
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit b8b2a9d2f49686d5056fb0ce6150cf9c54180b12
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 23 04:01:24 2010 +0000

    change volume file options back to 'transport' from 'rpc-transport'
    
    This helps to keep the backword compatibility with old volume files.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit e82ca8fc5164f4ba2ff396da86b4a490d9a47370
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 23 02:55:21 2010 +0000

    minor improvements in protocol
    
    * rpc_clnt_submit() now takes 'cbkfn' as an argument.
    * readdir xdr now uses dirent structure directly instead of
      using 'opaque' buffer through which it was serializing /
      unserializing the dirent structure.
    * 'gfs_id' field (currently used for debugging) is properly updated
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 487e9f1d59bbf7b37a30ceef5dbfd8ca77b94988
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 22 11:30:23 2010 +0000

    moved 'auth_glusterfs' xdr definitions to rpc-lib
    
    as authentication is part of RPC header and GlusterFS payload
    comes at later stages
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 23bec6b810bfd0ae78eb9ba2e9c644c42a3da1da
Author: Anand Avati <avati@gluster.com>
Date:   Mon Jun 21 02:17:49 2010 +0000

    io-threads: initialize conf->w_attr
    
    Uninitialized value was causing pthread_create() to fail on solaris
    resulting in hung calls
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 1001 (unclean termination upon getting signalled)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1001

commit 10d3dfe91c1f0eb185fc4ca88be77a200f992c61
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jun 16 21:48:03 2010 +0000

    performance/io-cache: destroy table->mem_pool in fini.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 995 (memory leak in io-cache)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=995

commit 7ac6287fb65bdddf3874f3a2c2602e857fbc6b87
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jun 21 04:26:14 2010 +0000

    misc updates in mainline
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 002ab96fd30f8924533fc454ecea00be04c013d5
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jun 21 04:26:00 2010 +0000

    make rpc protocol as default, and move the old one to legacy
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit fdd20492638fe98a62b5e6d5e82f18cf4799fd1a
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jun 21 07:00:04 2010 +0000

    rpc protocol
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit b9b8734a9496ccf5f8ed5527dc7714930a59948b
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jun 21 04:24:40 2010 +0000

    renamed xlator/protocol to xlator/protocol/legacy
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 2a5fada7546032e1fc1b106ddd40e42cc45349e1
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Tue Jun 15 22:07:57 2010 -0700

    Revert "performance/write-behind: explicitly enforce ordering of overlapping writes."
    
    This reverts commit e46c613364cd90f9c277db8b0733a99fc1d255de.

commit dbcb981892d922da61afa4bd9e3df9d22414e22a
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed Jun 9 00:00:23 2010 +0000

    Changes to volgen such that it does not error out in python2.4
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 988 (volgen in master generates error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=988

commit 45cfee031062fe40899a6c4c9049d0267b7c7ee6
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 10 01:14:56 2010 +0000

    changed the order of gf_log in xlator.c to prevent hang
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit d0b2695d773d3bbf162b367735c39d0e5bd7063a
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Jun 8 06:14:30 2010 +0000

    Fix compilation failure on Solaris in __socket_keepalive()
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 987 (Solaris compilation fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=987

commit a912b145157beb1700250872d672bb03fffe658f
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jun 8 06:03:41 2010 +0000

    mem-types: include *-mem-types.h in noinst_HEADERS variables in all Makefile.am
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit b316601c29012bd983b2f232f3a605fd937e654a
Author: Anand Avati <avati@gluster.com>
Date:   Mon Jun 7 13:19:11 2010 +0000

    quick-read: fix size parameter to GF_CALLOC of priv to fix mem corruption
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 723 (enhancements to quick read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=723

commit 79241696fbdebe2583298f12cbaee068ce60c655
Author: Anand Avati <avati@gluster.com>
Date:   Mon Jun 7 12:37:34 2010 +0000

    dynamic volume changes for graph replacement
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 971 (dynamic volume management)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

commit c4ebd25a176d6d51d702b1009e261c3c27237a48
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jun 1 17:27:18 2010 +0000

    fuse: add a built-in fuse traffic dumper mechanism
    
    It makes fuse dumping possible on platforms where strace is not available (eg. OS X),
    moreover it makes reporting of fuse related bugs more convenient.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 972 (Metabug for misc. fuse features)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=972

commit d23ae73d0e34010b464454ce81f53f44901ca544
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jun 3 04:39:44 2010 +0000

    performance/quick-read: fix the size-to-be pruned.
    
    - size-to-be pruned used to be a negative number because of cache-used being
        subtracted from configured cache-limit (with cache-used > cache-limit).
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 980 (quick read - fetching from backend issue)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=980

commit f6048901a2068af13e21ba66b41a0667b740b1d4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jun 1 05:07:58 2010 +0000

    performance/quick-read: set default cache-size value to 128MB.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 723 (enhancements to quick read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=723

commit f6ac7f6f6e28c7567e05c701f88fbdd6a971bf29
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon May 31 22:43:57 2010 +0000

    cluster/afr: Check before accessing xattrs in data self heal.
    
    The lookup xattrs might be null, because a lookup might not have been issued during self heal,
    especially if only data self heal is required.
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 815 (quick-read and replicate self-heal interaction result in empty reads)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=815
    
    BUG: 815 (quick-read and replicate self-heal interaction result in empty reads)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=815

commit 5b0d583cc4399e6d1b6d79ea9513c9f8ca789f8f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon May 31 22:43:56 2010 +0000

    extras/gnfs-lognalyzer: Delete class instance to release mem early
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 913 (NFS-specific log analyzer tool)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=913

commit 4f49c3d22599b4296e51da0d2684633904ec134e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon May 31 22:43:55 2010 +0000

    mount3: Handle unmount for unknown volume names
    
    In case the nfs client sends an unmount request for a volume
    that does not exist anymore.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 961 (Unmount with invalid export crashes nfsx)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=961

commit 91afbb094ce97fb8f8183227cd56410ad3746449
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon May 31 22:43:54 2010 +0000

    mount3: Handle <volname> as well for unmount dirpath
    
    Till now nfsx would crash if the export was mounted simply as
    <volname> as compared to the traditional method of /<volname>.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 944 (vmware unmount crashes nfsx)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=944

commit 7cda6661979dfec1614575a9729b84cbf49e6b25
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon May 31 22:43:53 2010 +0000

    nfs3: Special-case the lookup for parent dir of root
    
    When a lookup request comes in for (rootfh, ".."), we need to handle
    it in a way that returns the attributes and handle of the root dir.
    Not doing so crashes nfsx because the inode table is not able to
    find a inode for the root's parent. This inode was being referenced in
    nfs3_lookup_parentdir_resume when filling a loc for the lookup fop.
    
    For the record, such a lookup request is sent by vmkernel.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 942 (NFS crashes as a vmware ESX data store)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=942

commit da08199c57cedb3dc922ed6bec07932cd2aefabd
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon May 31 22:43:52 2010 +0000

    nfs3: Funge . and .. ino/gen in readdir of root
    
    In the readdir reply for the root of the export, replace the ino
    and gen number for the . and .. entries with 1 and 0 respectively.
    On clients which inspect this field, the client will error out due
    to the change in inode number of the root directory when see for "."
    
    .. also needs to be replaced because we do not have a concept of
    the parent directory of root. The return of 1 and 0 is the same as
    the behaviour of: stat /.. command.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 942 (NFS crashes as a vmware ESX data store)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=942

commit 5e03484d1d24ae93f7cad5fe575edd9ce8e0195b
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri May 28 07:00:42 2010 +0000

    OS X: make location of launchd service configurable
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit a841aba0844e69e3a11205f4f0b5176bcc0cb362
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri May 28 06:05:48 2010 +0000

    OS X: salvage signal handling from mount routine
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 065ac01684dabd4cca4bde3048ef2f13cc2357cb
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sat May 29 16:09:24 2010 +0000

    protocol/client: Add missing argument to readlink unwind call.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 967 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=967

commit 37495f6c2ee3ce3cf5a68631dc421825c540fbda
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri May 28 04:17:30 2010 +0000

    cluster/stripe: NULL pointer dereference checks added
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 966 (NULL check for avoiding NULL dereferencing of pointers..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=966

commit e2c119796e396966277ddd27ccdd4b72171271cf
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri May 28 04:17:02 2010 +0000

    cluster/stripe: added STACK_UNWIND_STRICT macro
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 966 (NULL check for avoiding NULL dereferencing of pointers..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=966

commit c729fde0667e595b49444dcae55a3539ce2edc64
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu May 27 12:35:12 2010 +0000

    catch up with 4911659 on OS X
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 952 (EBADF returned by server-protocol confuses AFR)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=952

commit 49116597598fbb793286e72b52b5c79e4db31943
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu May 27 04:38:45 2010 +0000

    protocol/server: Use EBADFD instead of EBADF in the case of a failed fd resolution.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 952 (EBADF returned by server-protocol confuses AFR)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=952

commit 3bd7269c9390db1fa57ac08106d97dc9981e9a85
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu May 27 04:27:59 2010 +0000

    protocol/client: Unwind with error if getting remote inode number fails.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 951 (Unwind if inode_ctx fails in all FOPS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=951

commit 7817f40998113c23cece55c71bdb732bce6de490
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed May 26 18:50:27 2010 +0000

    nfs/lib: Remove "-module" from LDFLAGS
    
    libglrpcsvc is a library and not a module according to Mac OS X.
    Hence "-module" needs to be removed for linking to work.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit f2ac33d36dc3c9e14129a65e7ebf4759120f11a1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue May 25 04:20:45 2010 +0000

    stat information of postparent stored in preparentstr insteadof postparentstr in trace
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 945 (stat information of postparent stored in preparentstr instead of postparentstr in trace)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=945

commit c90bea236d66da360988df479239f21d0a3addc1
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue May 25 05:16:47 2010 +0000

    take the return value of trace_stat_to_str for preparent and postparent in corresponding variables
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 945 (stat information of postparent stored in preparentstr instead of postparentstr in trace)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=945

commit 665591074fbef562b48a9cd1b74b3d4cc92cd667
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue May 25 09:00:38 2010 +0000

    Check whether NULL is returned after GF_CALLOC in the init function of io-stats
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 946 (Null check in init function of io-stats)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=946

commit 419ff2e73983efc5b31e98795e99ab4fdff41e6e
Author: Anand Avati <avati@gluster.com>
Date:   Wed May 26 09:28:39 2010 +0000

    resolver: set safer conditionals during path creation
    
    when client would send just the path as part of a transaction, path
    reconstruction would create parent directory's path instead of actual
    path at the time of resolution.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 935 (Directories change mode from 0755 to 0644 automatically)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=935

commit e46c613364cd90f9c277db8b0733a99fc1d255de
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed May 26 04:11:22 2010 +0000

    performance/write-behind: explicitly enforce ordering of overlapping writes.
    
    - If there are non-contiguous offsets (offsets which do not start where
        previous write ended), wait for completion of previous writes to server
        before sending new ones.
      - Send flush call to server only when all writes are completed.
      - If a file is opened with O_APPEND, at any point of time a maximum only one
        write call to server should be in transit. This is to avoid reordering of
        writes in the presence of afr which can result in data corruption.
        See bug #934 for more details.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 934 (md5sum mismatch when files are transferred using vsftpd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=934

commit 4d195fb92fed43ab7ca9d1568432913e4dbeef0e
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon May 24 14:16:17 2010 +0000

    features/locks: Use fuse supplied lock owner even for internal locks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 934 (md5sum mismatch when files are transferred using vsftpd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=934

commit 5e849ce81a060a543201c431c5ba00e413cfdfff
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon May 24 09:32:56 2010 +0000

    socket: make tcp keepalive work on OS X
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 754 (enable tcp keepalive)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=754

commit dda7eb5ff4d38cc0f280aa0e828da46e6d97195b
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon May 24 09:30:42 2010 +0000

    fix format string warning on OS X
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 936 (Provide microsecond timestamp in logfile)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=936

commit b48459eb7369bdc0eac6a516138e5095962449f3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon May 17 07:22:16 2010 +0000

    performance/quick-read: implement an upper size limit for the cache.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 723 (enhancements to quick read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=723

commit 3047188b314b3d2a4788451d2b7ab633b8d127ff
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu May 20 07:24:28 2010 +0000

    libglusterfs: Use usecond resolution for logging
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 936 (Provide microsecond timestamp in logfile)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=936

commit 719354ddbd6b68f2b1df6d03e70683a65daf1eb0
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue May 18 03:41:38 2010 +0000

    free this->private in fini in io-stats
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 930 (conf not freed in io-stats fini)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=930

commit 174f26f113a7a361a9aa5c959310fcc3867e0dc6
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 18 01:38:17 2010 +0000

    socket: Support TCP-KEEPALIVE
    
    Introduces two new socket options:
    
    1. transport.socket.keepalive: bool
    Sets keepalive on a transport. On by default.
    
    2. transport.socket.keepalive-interval: integer
    Number of seconds between each keepalive message on the socket.
    Default in linux is 2 hours. To change that value for a given
    transport, use this option. Integer value is interval in seconds.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 754 (enable tcp keepalive)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=754

commit c705b679fbe41aa9ac4486ebf46d3b2ae95d1628
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 18 01:37:42 2010 +0000

    nfs: Introduce trusted-write and trusted-sync options
    
    Introduces two new options:
    
    1. nfs3.*.trusted-write: Forces UNSTABLE writes to return STABLE to NFS
    clients to prevent the clients from sending a COMMIT. STABLE writes
    are still handled in a sync manner and so are COMMITs if they're sent
    at all.
    
    2. nfs3.*.trusted-sync: Forces all WRITEs and COMMITs to return STABLE
    return flags to NFS clients to avoid the overhead of STABLE writes, and
    COMMITs that follow UNSTABLE writes. This includes the trusted-write
    functionality. In addition to the trusted-write, it also writes
    STABLE writes in an UNSTABLE manner.
    
    Both violate the NFS protocol but allow better write perf in most
    configurations. Use with caution.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 924 (Slow NFS synchronous writes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=924

commit 3b88b2dfbc1a33a6967cfedf63a615ee1e81e49d
Author: Sachidananda <sac@gluster.com>
Date:   Tue May 18 00:20:24 2010 +0000

    Log proper error message when hostname or ip does not conform to standards.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 923 (Hostnames with underscores fail)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=923

commit 67ade7b062a13d896187d1bc784baded59f73fcf
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon May 17 07:10:22 2010 +0000

    OS X: enable mac-compat for OS X clients.
    
    Injecting volumes at startup this way is pretty hacky but it will do for now.
    Refactoring that part will come as separate commit.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 11fb070964adf57eea4191d315a752c96f80a426
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon May 17 07:09:13 2010 +0000

    OS X: adjustments, minor fixes to eliminate warnings
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit bfb10f41a8e3fe7326f507451459529c5b39b72e
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon May 17 07:07:57 2010 +0000

    OS X: NFS adjustments needed for OS X
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 18d982e6d0d330af8ccd2b12252ae29fe0932023
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon May 17 07:06:58 2010 +0000

    OS X: basic additions for OS X client support
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 86ee9d3e144d2371e5ae7edf663916b8da6d2616
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon May 17 04:42:46 2010 +0000

    cluster/afr: Don't dereference fd ptr - it might be NULL due to a failed call.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 914 ([3.0.4] Crash in afr_opendir_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=914

commit 8734ba0fc9e066065dfd23f8f6da12f2fd89e80e
Author: Lakshmipathi <lakshmipathi@gluster.com>
Date:   Fri May 14 02:01:36 2010 +0000

    Bug 799: dht prints 100% full when subvolume is not connected to remote host
    
    Signed-off-by: lakshmipathi <lakshmipathi@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 799 (dht prints 100% full when subvolume is not connected to remote host)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=799

commit bb315cb180c3547218b5ed581d38e76aec74cf94
Author: Anand Avati <avati@gluster.com>
Date:   Thu May 13 12:53:25 2010 +0000

    fuse, dht: use readdir by default.
    
    dht - switch over to readdirp based algo if one subvolume is down
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 898 (small file performance enhancements)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=898

commit 97e060d04b6b86225264644ff8fef0459577a031
Author: Anand Avati <avati@gluster.com>
Date:   Thu May 13 13:16:48 2010 +0000

    dht: perform revalidate on one subvolume
    
    generation numbers should detect recreations and no need to rely on
    layout changes anymore
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 898 (small file performance enhancements)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=898

commit 8ed739a72a43242083afeccdedda079ff939f714
Author: Anand Avati <avati@gluster.com>
Date:   Thu May 13 12:53:05 2010 +0000

    write-behind: update default values for better small file performance
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 898 (small file performance enhancements)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=898

commit 2a0398dee8521704b90d3f1776a5e380bf8ac5b3
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed May 12 19:10:47 2010 +0000

    added features/mac-compat
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 800 (Problem on OSX with NFS and CIFS exports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=800

commit 9bdda4ce0aaebb3f8109152f056d9b35229fb708
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 13 06:59:19 2010 +0000

    nfs3: Final unref only on successful remove
    
    The final unref on the inode during a file removal
    should take place only if the file removal was successful.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 857 (Crash in afr_sh_entry_expunge_entry_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=857

commit 40c53115e312a7b5b5bc0b7cf880820bc8e7c8e1
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon May 10 09:30:37 2010 +0000

    nfs: fix warning on 32 bit
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 902 (iozone hangs during random read throughput test)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=902

commit e3ea64186ad389393274a1f4c2c2f9fe13df5606
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon May 10 17:35:41 2010 +0000

    glusterfs-profiler: Add text mode support.
    
    glusterfs-profiler works in text mode by default now. This allows it to run on systems which don't have matplotlib installed.
    
    Modes can be selected using:
    
      -m graph        - Graphical mode
      -m text         - Text mode (default)
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 268 (Add timing instrumentation code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=268

commit 7c9df496895aeff28510e63473783511318db87a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sun May 9 23:13:55 2010 +0000

    extras: Add NFS-specific log analyzer tool
    
    Most of the time, a NFS request and the reply are separated by hundreds
    of lines of other debugging output most of which is not always relevant
    for NFS debugging. This script synthesizes the full glusterfs log into
    the parts relevant for NFS while bringing together the NFS requests with
    there replies on one line.
    
    Min log-level required for this script to be useful is DEBUG. Only
    works for NFS translator.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 913 (NFS-specific log analyzer tool)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=913

commit 2848a53f53b414e8289bce1527ce0cee78719b70
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Sun May 9 23:13:54 2010 +0000

    nfs3: Round-up read reply bytes of multi-vector reply
    
    A previos commit brought in support for returning read replies
    when subvolumes return reads in multiple iovecs. This did
    not completely fix the problem since the bytes in iovecs
    all together could be unaligned with the 4 byte
    boundary as needed by XDR for the opaque data. This resulted
    in read requests being either retransmitted or rejected with
    an error message in syslog on the NFS client.
    
    Signed-off-by: Shehjar Tikoo <shehjart@dev.gluster.com>
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 902 (iozone hangs during random read throughput test)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=902

commit 80c3061c07c46b4ac11beb5f0ebad08b8af2cafe
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Sun May 9 23:13:53 2010 +0000

    rpcsvc: Move xdr round up functions to rpc code
    
    Signed-off-by: Shehjar Tikoo <shehjart@dev.gluster.com>
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 902 (iozone hangs during random read throughput test)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=902

commit eba21f8fb6715e3933253b0114f03a153be80649
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Sun May 9 23:13:52 2010 +0000

    nfs: Fine tune nfs_entry_loc_fill return values
    
    A previous change to this function introduced a regression
    for exclusive creates. This patch fixes the regression by
    bringing the return values in line with what the callers
    expect in different situations of loc filling.
    
    Signed-off-by: Shehjar Tikoo <shehjart@dev.gluster.com>
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 857 (Crash in afr_sh_entry_expunge_entry_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=857

commit fb2d84b8507354ed6128cacf4289f405cdc8bdc6
Author: Anush Shetty <anush@gluster.com>
Date:   Fri May 7 04:25:28 2010 +0000

    Adding GF_LOG_OCCASIONALLY to prevent repeated log messages
    
    Signed-off-by: Anush Shetty <anush@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 10 ([ glusterfs 2.0.0 ] - Repeated Log messages with invalid remote-host in protocol/client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=10

commit 8be447d390f2e0b7dee2edf46b20b75a9ff107dc
Author: Simone Gotti <simone.gotti@gmail.com>
Date:   Tue May 4 16:48:55 2010 +0000

    Unset split-brain flags in afr_self_heal_completion_cbk if self heal completes successfully.
    
    Signed-off-by: Simone Gotti <simone.gotti@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 884 (I/O errors after fixed split brain and successfully completed self heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=884

commit 45a2f82f659bf0af9e4bde403dad887f29d41e65
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri May 7 01:53:11 2010 +0000

    nfs3: Submit multiple vectors received in read callback
    
    There is a possibility of io-cache or read-ahead returning
    a read buffer that straddles two separate pages in ioc or ra,
    through two struct iovecs. Current nfs3 read reply does not
    return as many vectors as received from a subvolume leading to
    a short read for the NFS client.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 902 (iozone hangs during random read throughput test)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=902

commit 79f8c310dfa52c035e41e46daa25ccf0419bea27
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri May 7 01:53:10 2010 +0000

    rpcsvc: Support multiple vectors during reply submission
    
    RPC reply path allows attaching a single iovec to a reply. This limits
    the replies for certain program ops which need to return multiple vectors
    for eg, the NFSv3 read reply.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 902 (iozone hangs during random read throughput test)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=902

commit c1f052da3652595effee1e514b1e9fb9055e13a1
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 6 08:36:16 2010 +0000

    nfs3: Use standard macro to return ESTALE
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 857 (Crash in afr_sh_entry_expunge_entry_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=857

commit c8a94aa7c522e7c820ae181c6f60e657bc12ea6d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 6 08:36:15 2010 +0000

    nfs: Handle failed parent loc filling
    
    Just because an inode_get for parent (ino, gen) returns a valid
    inode_t does not meant that the inode_path(..in nfs_parent_inode_loc_fill..)
    will return successfully. The failure of nfs_parent_inode_loc_fill was
    not handled resulting in a NULL path being passed for the fop.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 857 (Crash in afr_sh_entry_expunge_entry_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=857

commit 9dabc8b0a9a2582004e3f8a14e5d8cac201ce01a
Author: Anush Shetty <anush@gluster.com>
Date:   Thu May 6 05:52:40 2010 +0000

    Fix for crash in stripe_entry_self_heal
    
    Signed-off-by: Anush Shetty <anush@gluster.com>
    Signed-off-by: Anush Shetty <anush@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 887 (Crash in stripe_entry_self_heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=887

commit dce48d4793d76c38143dc55fe45b30ead12ffbf5
Author: Sachidananda <sac@gluster.com>
Date:   Wed May 5 01:15:09 2010 +0000

    Add key/type pair to volume_options.
    
    This avoids warning message to be logged for internal option
     `transport.socket.lowlat' as not being recognized, when transport/ib-verbs is
     used.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 818 (transport.socket.lowlat option is not given  as can be seen from the vol-file still the warning shows up in the logs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=818

commit a6096217aa96c4ee2fe39977f1d169a33be6fd40
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Wed May 5 01:14:02 2010 +0000

    Check whether a server is down before calling rename on the directory
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 820 (distribute directory rename problem when one subvol is down)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=820

commit b0ed997cda2195e9178cbaa96d26976aa6dd2acf
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed May 5 00:27:45 2010 +0000

    posix: Support thread-safe vectored writes/reads
    
    ..by maintaining internal offsets and using pwrite/pread
    instead of writev/read.
    
    The recent io-threads change is causing concurrent writes to
    a file from different io-threads. This results in a race between
    two threads both of which are trying to call lseek-writev. The
    lseek-writev sequence should be a critical section. This is where
    pwrite syscall helps. pwrite also requires an offset to be given so
    for supporting pwrites for multiple iovecs we maintain an offset
    within posix for the duration of the write fop and pass this internal
    offset to pwrite.
    
    The same logic also applies to read, only difference is that we do
    not need to read multiple iovecs but only provide an atomic
    lseek-read sequence.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 883 (Data corruption due to thread unsafe reads and writes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=883

commit 716f4dc26097811161cbd59c919df11593cb46af
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 4 04:01:30 2010 +0000

    nfs3: Fix NFSv3 string error for EISDIR
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 858 (Crash with afr_local_cleanup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=858

commit 3954ddddfe6c600ff2bb8d70463bc6fb4fe67225
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue May 4 02:29:22 2010 +0000

    performance/read-ahead: don't set ra_file in fd->ctx unless all memebers of ra_file is initialized
    
    - If ptr to ra_file is set in fd->ctx even before initializing all its
        members, A race condition may occur b/w a thread executing ra_fstat,
        ra_readv etc (where all files open on the same inode are flushed) and
        the thread doing initialization of ra_file (in ra_open_cbk or
        ra_create_cbk). Because of this race-condition, flush_region might be
        called on an uninitialized ra_file, thereby causing crash.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 868 (crash in ra_fstat)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=868

commit bb4955c4e12618171ae69c4161db709ff7d29981
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon May 3 18:10:46 2010 +0000

    cluster/afr: Unwind lk using struct flock from a successful server
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 882 (directory traversing problem (client crash))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=882

commit 3917c5a3d14853e1d4642d3ccd913c9a7de27173
Author: Pradeep Patil <pradeep@gluster.com>
Date:   Sun May 2 23:55:43 2010 +0000

    crash fixed in stat-prefetch.c
    
    Signed-off-by: Pradeep Patil <pradeep@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 876 (crash in stat-prefetch)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=876

commit 7840d9de272ef2f24c4c755a857ad8ae06703b55
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 4 00:37:01 2010 +0000

    frame's 'op', 'type' restructured
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit f75b76350747f5f58a4bbe704915c74979cc5ac3
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 4 00:36:24 2010 +0000

    structuring of protocol - 2
    
    * 'transports/' and 'auth/' moved to xlators/protocol/
    * transport.{c,h}, authenticate.{c,h}, protocol.h moved to
        xlators/protocol/lib/src/
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 7504b0e623914d097933f0a613ba50e376131828
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 4 00:35:59 2010 +0000

    structuring of protocol
    
    * isolated 'protocol.h' and transport.h from libglusterfs/* and
      glusterfsd/*
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit 72ca9bdf90c45ff3f4bad3d2de934101dfaca4ff
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue May 4 00:35:36 2010 +0000

    'features/locks': remove all reference to 'transport_t'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 875 (Implement a new protocol to provide proper backward/forward compatibility)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=875

commit c8a0827765e78b285ca50cb26ab1dca620e3bfe1
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Apr 27 09:56:00 2010 +0000

    dht: don't overwrite the layout after the subvolume expansion
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 864 (dht self-heal overwrites layout causing 'missing' files.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=864

commit b03a5683680b7be5ff7c88083276811a381aac68
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 28 01:37:39 2010 +0000

    fusermount: bring in updates from upstream
    
    * Fix checking for symlinks in umount from /tmp.  Reported by Al
        Viro
    
        * Fix umounting if /tmp is a symlink.  Reported by Franco Broi
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 657 (Metabug for tracking fuse upstream)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=657

commit 07744014e26e6c3edb14e624ef2f68c56694375a
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Apr 29 00:27:57 2010 +0000

    performance/io-cache: Dump private information
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 828 (glusterdump filled up the /)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=828

commit 6f1895d77df52f0e0aa7c2a7aff09c9398640aef
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Apr 27 09:11:51 2010 +0000

    cluster/stripe: Memory accounting changes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 585c23e8c7e81272d206aca19b2c0807975fec92
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Apr 27 09:11:17 2010 +0000

    nfs/server: Memory accounting changes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 63c8d8f2998dcbcfd392b67ea68ad3d3ec4a2805
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Apr 27 08:47:40 2010 +0000

    features/access-control: Memory accounting changes
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 2c5a280f9a7ad7eb971db4d55e6ce806c5cdd6bc
Author: Anand Avati <avati@gluster.com>
Date:   Tue Apr 27 07:44:45 2010 +0000

    cluster/dht: perform inode number overwrite in readv_cbk iatt with checks
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 862 (Crash in dht_readv_cbk with error-gen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=862

commit 55d332f5eca51ee4820ecd62af1cdb2a24ad100e
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 27 03:46:39 2010 +0000

    Set op_ret to -1 when open fails in posix_create
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 825 (when create() races both return success)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=825

commit 81d53a0f5d09afed172ceb93061156c8910fa5d1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 26 07:48:29 2010 +0000

    performance/quick-read: don't try to validate again if qr_readv is called just after validation.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 852 (QR cache-timeout 0 causes high CPU usage and app hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=852

commit cade6a8f2305800750bf7d9a6907e02f8b06f0b6
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Apr 22 06:12:00 2010 +0000

    stat-prefetch: Remove checks for loc->parent
    
    ..because loc->parent can be NULL for the root inode.
    Having this check makes sp return EINVAL on perfectly valid
    fops.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 845 (NFS BETA Test - Test Case 1: 4dist-repl-chown1m)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=845

commit 8626e201a5bceb623bb77a82fd5437ba3668cf19
Author: Sachidananda <sac@gluster.com>
Date:   Thu Apr 22 04:13:36 2010 +0000

    Filter out extended attribute visibility on the mount point.
    
    Filter out extended attribute visibility on the mount point.
    This causes rsync -X to remove the extended attributes and `Stale NFS file
    handle' error on mount point, resulting in making the mount point inaccessible.
    
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 797 (DHT layout and posix generation number xattr's should be filtered)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=797

commit 582de0677da4be19fc6f873625c58c45d069ab1c
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Apr 22 13:33:09 2010 +0000

    Memory accounting changes
    
    Memory accounting Changes. Thanks to Vinayak Hegde and Csaba Henk for their
    contributions.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 329 (Replacing memory allocation functions with mem-type functions)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=329

commit 72baa17282f5cf749fa743fd601c7b728ece4fa2
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 22 20:38:42 2010 +0000

    debug/io-stats: Call readdirp in readdirp instead of readdir
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 268 (Add timing instrumentation code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=268

commit 0a5b61b7a1aae73dbb9f98c932c47751107e0e4e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Apr 23 06:45:34 2010 +0000

    mount/fuse: Destroy STACK when truncate and other op are part of same SETATTR
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 829 (SETATTR stack leak?)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=829

commit bf18a37a1b66ca3ac75713d39e68dde1a116f4cf
Author: Harshavardhana <harsha@gluster.com>
Date:   Wed Apr 14 20:20:38 2010 +0000

    extras/volgen: Volgen patchset
    
    -- Supports NFS Translator.
    -- Consolidated common API's into Common.py.
    -- Removed unused CreateBooster.py.
    -- Added code for "--add-server" for dynamic volumes.
       Currently its commented out we will use it when needed.
    -- No more options hiding in background anymore. All options
       specified for each translator are commented and exposed.
       Only necessary values are  enabled. This is done due to
       necessary cleanup of unwanted options by exposing them.
       PENDING: "replicate" translator
    -- Quota is disabled for native NFS on client side.
       Only server side quota can be used as of now.
    -- Additional code cleanup.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 822 (Volgen changes supporting NFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=822

commit 7c7bafa3b17dcc0c799b5d42ccb5726e52c4d94f
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Apr 20 09:08:26 2010 +0000

    Do not hardcode the lru_limit on inodes to 1 Million while creating the inode table
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 834 (lru_limit on inodes is hardcoded to 1 million)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=834

commit 3eb79f8704909d118a694d9c41c5b97fa558aa91
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Apr 22 00:47:19 2010 +0000

    core: Set ctx in global_xlator to prevent NULL ptr reference
    
    This results in a crash in STACK_UNWIND after a call bail out.
    Since the call bail does not occur in the context of an xlator,
    the old_THIS in STACK_UNWIND is handed a global_xlator which did
    not have its ctx set, resulting in a NULL de-reference.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 844 (mixed testing with 35 clients)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=844

commit 1233dad03fb71afe2714ee76476cea75e26aab25
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Apr 20 02:43:08 2010 +0000

    nfs: Remove reference to top
    
    This is not needed anymore and also conflicts with changes being
    made for DVM.
    Should have been removed with the bug fix for bz 770.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 770 (NFS Xlator - Crash when both GlusterFS server/NFS Server are in the same file)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=770

commit 74b165a23fdb4791d2dcd83194ef8765bb43716e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Apr 15 12:30:37 2010 +0000

    cluster/afr: Check for call_count in ENTRY_RENAME_TRANSACTION
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 824 (Crash in afr rename transaction)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=824

commit 477f6d1cdcc347bb0fa4ae79c9e48be7d0811235
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 13 12:47:14 2010 +0000

    cluster/afr: Send xattr in lookup from the source subvolume.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 815 (quick-read and replicate self-heal interaction result in empty reads)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=815

commit 51f521ac9a140c147d22a2a38463984132a083a8
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 13 18:39:34 2010 +0000

    cluster/afr: Fix possible NULL dereference in readdirp_cbk
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 722 (Segfault in glusterfs 3.0.3 replicate/afr_readdirp_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=722

commit 4b754a77545fb7db030471fd4d84b8eee6008d7c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Apr 12 21:57:35 2010 +0000

    nfs3: Use nfs3state in call_state to avoid getting from rpc request
    
    This change avoids having the nfs translator depend on the sanity
    of the rpcsvc_request_t type after NFS reply has been sent. This
    was a problem because the request structure is guaranteed to be
    invalid after the reply for the request has been submitted by the
    RPC program. NFS3 handler was ignoring this behaviour and accessing
    the private in request after reply submission resulting in access to
    corrupted data.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 757 ([NFS-Alpha] Crash in nfs3_call_state_wipe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=757

commit 3d125eaed2fbf71c8c6dcddd45a9fa61ef4a4448
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Apr 11 19:08:48 2010 +0000

    fuse: fix too early freeing
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 755 (Fuse loc error when files are created and deleted simultaneously)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=755

commit 28818a5371e306a5cc0970f359aa5f20c8769794
Author: Anand Avati <avati@gluster.com>
Date:   Thu Apr 8 14:07:00 2010 +0000

    protocol: fix endianness for nanosecond field in stat structure
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 801 (Direct io-mode support and related changes in caching translators.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=801

commit 7ef3c9773015d1c77ba23a482eeaa25e2ff31328
Author: Anand Avati <avati@gluster.com>
Date:   Thu Apr 8 13:15:32 2010 +0000

    afr: afr_fsetattr - send proper inode pointer to afr_read_child()
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 814 (replicate complains of invalid inode in afr_read_child())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=814

commit 1e30fc3e001594e9cfd372079adf2172bc9ed3df
Author: Anand Avati <avati@gluster.com>
Date:   Thu Apr 8 12:24:31 2010 +0000

    iatt: change S_IF macros with IA_IF macros in missing places
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 730 (unknown filetypes and inode conflicts in afr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=730

commit e53cb0787943d51f880daa829aa5699851e985e8
Author: Anand Avati <avati@gluster.com>
Date:   Thu Apr 8 12:23:10 2010 +0000

    afr: fix inode ref leak in lookup
    
    first success lookup sets local->cont.lookup with inode_ref and second
    setting leaks
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 813 (inode ref leak)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=813

commit 0143139ba85211e8b96ec238c97d0885ae0817b1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 5 05:59:17 2010 +0000

    performance/quick-read: read directly from backend for fds opened with O_DIRECT flag.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 723 (enhancements to quick read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=723

commit c724beb161ce5f21862e9bb425736efed7532777
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 7 10:07:29 2010 +0000

    NFS: type fixes: some portability cleanup
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit d9e256b0e4203a7f79f862ecc83c509e516f0e14
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Apr 7 10:05:29 2010 +0000

    NFS: type fixes: sanitize rpcgen generated typedefs
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit 24591071a3c6a4362b8bb6818f42d3b7ec176342
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Apr 7 11:49:00 2010 +0000

    cluster/afr: Cleanup fd ctx in releasedir cbk
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 805 (memory leak in afr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=805

commit 73739935f511e431a64232c9b737342c7ba859e7
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Apr 6 21:18:15 2010 +0000

    initialization fixes
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit e78fb59b75a455127c004dd751ebcc4af1b14124
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Apr 7 07:25:39 2010 +0000

    nfs3: Allow all access to superuser except execute at all times
    
    During building glusterfs from source, the make phase fails because the
    access test by super user actually returns the access test bits using
    only the user, group and other, without accounting for the special
    status of super-user.
    
    This results in a permission denied for the super-user.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 807 (GlusterFS compilation fails on NFS Client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=807

commit 3642cd246ea598d7a72dff74f49b78964678719c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 5 13:36:36 2010 +0000

    performance/quick-read: make use of nanosecond resolution of mtime to decide whether to keep cache or not.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 801 (Direct io-mode support and related changes in caching translators.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=801

commit 33101bd66614908efafc91ff2950ef3e34b76a3b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Apr 5 13:36:07 2010 +0000

    performance/io-cache: make use of nano second resolution of mtime during cache validation.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 801 (Direct io-mode support and related changes in caching translators.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=801

commit 9c2bc1bc61af888192bde18170b113b4f6f8b4ca
Author: Anand Avati <avati@gluster.com>
Date:   Mon Apr 5 13:35:45 2010 +0000

    fuse: change behavior of direct io mode.
    
    If bigwrites are available, then disable direct io mode only by default
    (previously direct io mode was disabled in any case).
    
    Added new command line option to force enabling of direct io mode
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 801 (Direct io-mode support and related changes in caching translators.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=801

commit 7cb8982cbbe8298cd1bdd35055f7d3818f4a136f
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Apr 7 04:19:48 2010 +0000

    backword compatibility with 3.0.x releases - restored
    
    * glusterfs.h - added back the removed 'fop' types in same order
    * call-stub.c - enhanced logging in case of failure
    * server-protocol.c - added a ENOSYS function for these fops, so
                          there will be no crash if a old client
                          connects to mainline server.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 734 (keep only the working/usable code in build tree to focus more on development)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=734

commit d90c2f86ca7a8f6660e98da1e48c4798539b7d51
Author: Vikas Gorur <vikas@gluster.com>
Date:   Sun Apr 4 14:11:26 2010 +0000

    core: Do internal latency measurement of FOPs.
    
    This patch adds a facility by which each translator
    keeps track of the average latency of a FOP from
    its point of view. That is, the duration between
    the translator handing over the call to a lower-level
    translator and the reply coming back.
    
    The latency measurement is off by default, and can
    be toggled by sending SIGUSR2 to the GlusterFS process.
    
    Latency data is printed as part of the process state dump.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 268 (Add timing instrumentation code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=268

commit 9c2bfa8a4441d27178f3b843bfa0a77df9f867e5
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Apr 2 18:03:33 2010 +0000

    extras/profiler/glusterfs-profiler: Add graphing tool.
    
    glusterfs-profiler is a Python tool that can graphically display
    the profiling information printed in the process state dump.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 268 (Add timing instrumentation code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=268

commit d9b34f3f2c5de8cdde6dd8c24fade839b7727ab2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Apr 2 04:32:30 2010 +0000

    nfs: Redesign fop argument passing to support single volfile use
    
    The current design of the interaction between the generic NFS layer and the
    protocol handlers like mount3 and nfs3 is such that it does not allow using a
    single volume file which contains the nfs/server and the protocol/server.
    This is because the common nfs-fops layer assumes that ctx->top is always the
    nfs/server. This is wrong. The fops layer needs access to top because top or
    rather the generic NFS xlator's private state has a mem-pool. The fops layer
    needs this mem-pool to get memory for storing per-fop state. Since the fops
    layer cannot anymore take ctx->top be the nfs/server, all layers need to start
    passing the nfs/server xlator_t right down to the fops layer.
    
    I am also taking this chance to remove the synchronous equivalents of the fops
    and also remove the dirent caching directory operations.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 770 (NFS Xlator - Crash when both GlusterFS server/NFS Server are in the same file)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=770

commit 8d2342b19c715f2d6ecb024eace8102e2c5e3a29
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 23:52:33 2010 +0000

    nfs: Fix RPC library name to avoid conflict with system librpcsvc
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit 41f05fcefc1c192a3f322e827114897ec0ace316
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Mar 24 14:01:36 2010 +0000

    Fix further cppcheck reported issues.
    
    Reported-by: Patrick Matthäi <pmatthaei@debian.org>
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 420 (fix leaks pointed out by cppcheck static analyzer)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=420

commit aa6028a600ccfea14d3f047402dfe157047cabdc
Author: Harshavardhana <harsha@gluster.com>
Date:   Wed Mar 31 08:29:54 2010 +0000

    Hardcoded infiniband port is now handled dynamically by searching for active ports.
    
    * If user specifies a port then that port will be used regardless of which port is active.
    * If user doesn't specify any port then any one of the active ports is used.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 793 (Infiniband port handling should be dynamic by picking up from active ports)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=793

commit f66f04e3af1f31a4c51b6a87f5e32ea2e3c7b438
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:27:05 2010 +0000

    nfs: Add NFSv3 protocol support
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit e63053803dca86b4283b71bc4ef4cb180ec72d89
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:27:04 2010 +0000

    nfs: Add MOUNTv3 protocol support
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit c4fd1cf7325972d8ff64ef3a2bea70edcf4f1085
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:27:03 2010 +0000

    nfs: Add generic nfs translator
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit 8b2949db0d56bdf5842abcb72437cc7dccd884df
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:27:02 2010 +0000

    nfs: Add RPCv2 service
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit eff83c8dae2a9f6d52ae2d8b069190a13f92deaf
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:27:01 2010 +0000

    nfs: Add RPC and NFS XDR translation routines
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 399 (NFS translator with Mount v3 and NFS v3 support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=399

commit fce2ae459b356977aab9b0100db22047e54a994b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:27:00 2010 +0000

    access-control: Introduce new translator
    
    The access control translator is required for performing permission
    checks on files and directories in line with posix conformance.
    This is required to be kept separate from storage/posix so that
    ACL support can also be later integrated into this translator.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 400 (Support auxiliary gids in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=400

commit 26f826c75c9e629c71535f3d9e5962d4aedb6898
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:26:59 2010 +0000

    core: Expose default callbacks
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 400 (Support auxiliary gids in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=400

commit d337c518a5b6aad42db1489a5093efa6692962dc
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 31 07:26:58 2010 +0000

    core: Add iatt protection bit testing macros
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 400 (Support auxiliary gids in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=400

commit 31e69430140538f5fee3e8dc89bd2971917820d1
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Mar 28 23:53:17 2010 +0000

    fop namespace cleanup.
    
    removed 'lock_notify', 'lock_fnotify', 'setdents', 'getdents' from
    'fop' list, and removed 'stats' from mop list, as they are no more
    used in the codebase, and had made code bulky/buggy.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 734 (keep only the working/usable code in build tree to focus more on development)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=734

commit a79d50fc723ffa4d93fa8f567676b18591fac5fe
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Mar 29 00:35:52 2010 +0000

    libglusterfs/transport: no need to set address-family if one is not set in the configuration family.
    
    - if not set, address family defaults to AF_UNSPEC and getaddrinfo will fill
        appropriate address family for transport types tcp/socket.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 693 (glusterfs 3.0.2 will not listen on IPv6 address)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=693

commit d99804c05fe6302f638c6d748c1613a595390cd5
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 29 02:08:54 2010 +0000

    stripe readv: proper validation of 'op_ret'.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 536 (fsx tool fails over stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=536

commit cf99ded428cfdf562d5cd220c77dfc8b4617d9d8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Mar 26 02:41:58 2010 +0000

    performance/write-behind: Resume all the consecutive non-write operations in the request queue in a single go.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 740 (read-ahead does not work to its full potential when loaded on top of write-behind)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=740

commit 440bf123be4933d7268dbf558135ca341c6467be
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Mar 29 00:16:52 2010 +0000

    libglusterfs: Remove passive iobufs from statedump
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 782 (Remove passive iobufs from statedump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=782

commit 04f1cd8629775fe635fa2c61f83907648f3b4e72
Author: Harshavardhana <harsha@gluster.com>
Date:   Fri Mar 26 06:51:12 2010 +0000

    Fix backtick evaluation bug in cache-size
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 768 (cache-size might be wrong in glusterfs.vol)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=768

commit 0b3a225f4b0de4943c6e69eca296b322a9af52bf
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Mar 25 01:50:58 2010 +0000

    cluster/afr: UNWIND if opendir returns an error.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 756 (simaltaneous rm -rf hangs the clients)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=756

commit 08d746def4b21d20153395ff1f061e833b06cd4d
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 24 13:27:14 2010 +0000

    stripe: proper fix for reading 'holes'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 713 (fsx tool segfaults in readahead and iocache)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=713

commit 731431c4016479fa810e62aff49e92f57513eb8d
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Thu Mar 25 02:14:42 2010 +0000

    fix utimes
    
    Change utimes to lutimes to prevent errors from symbolic links for linux. For non-linux systems keep utimes.
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 34 (No such file or directory on du)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=34

commit bd1242b66da347e61db5f2e51638eca9e641b20d
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Mar 24 04:22:33 2010 +0000

    Remove glusterfs-guts from the repository.
    
    Goodbye, glusterfs-guts/!
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 734 (keep only the working/usable code in build tree to focus more on development)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=734

commit 08fd3a63f56c3bae0cbf57d59a3e4c32da791312
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 24 04:05:16 2010 +0000

    mount script has new option '-o ro'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 712 (mount.glusterfs script doesn't handle 'ro' option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=712

commit 3f8dc989b71977c2e3f94482b21be92b8562ea83
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 24 04:04:51 2010 +0000

    added '--read-only' command line option for glusterfs
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 712 (mount.glusterfs script doesn't handle 'ro' option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=712

commit 1a15248382e53e5c04cb6235144001d697f6b09b
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 24 04:04:02 2010 +0000

    new 'features/read-only' module added
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 712 (mount.glusterfs script doesn't handle 'ro' option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=712

commit 1e55e8f29b4cebb3398a46e36b8791980bb1db6d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Mar 23 17:02:29 2010 +0000

    extras/volgen: Add copyright headers.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 751 (Copyright headers missing)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=751

commit faad9087d032044765636e1cb55a6fb3659e374f
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 23 08:25:57 2010 +0000

    man pages updated
    
    man 8 glusterfs
    man 8 mount.glusterfs
    man 8 glusterfs-volgen
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 734 (keep only the working/usable code in build tree to focus more on development)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=734

commit 456701edd15dc2a953cbfc15f0dd657b876844c3
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 23 08:16:59 2010 +0000

    updated the build tree.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 734 (keep only the working/usable code in build tree to focus more on development)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=734

commit 12aefd726dc2b4effcde8136df1f88cebb1084f0
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 23 01:32:20 2010 +0000

    Replace struct stat by struct iatt
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 749 (crash in stripe_readv_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=749

commit 83ab05db5505a033a66385a7e1aaad605fea562b
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Mar 18 17:23:15 2010 +0000

    fix warnings on 32 bit
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 283ec9608e6cbc9393941d5fae901e558360d2bd
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Tue Mar 16 09:46:33 2010 +0000

    iatt: changes across the codebase
    
    - libglusterfs
      -- call-stub
      -- inode
      -- protocol
    - libglusterfsclient
    - cluster/replicate
    - cluster/{dht,nufa,switch}
    - cluster/unify
    - cluster/HA
    - cluster/map
    - cluster/stripe
    - debug/error-gen
    - debug/trace
    - debug/io-stats
    - encryption/rot-13
    - features/filter
    - features/locks
    - features/path-converter
    - features/quota
    - features/trash
    - mount/fuse
    - performance/io-threads
    - performance/io-cache
    - performance/quick-read
    - performance/read-ahead
    - performance/stat-prefetch
    - performance/symlink-cache
    - performance/write-behind
    - protocol/client
    - protocol/server
    - storage-posix
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit cc7515fc3db005383ffa575236ec29c212ed1e48
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Tue Mar 16 09:46:32 2010 +0000

    introduce iatt.h for inode attributes (to replace 'struct stat')
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 8477f1c8a7b38e78531e0bc40fcc38d21052857c
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Tue Mar 16 09:46:31 2010 +0000

    iatt: configure.ac not to build filter
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 49465d7136098b40166231d131ad10cc0f55a45d
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Tue Mar 16 09:46:30 2010 +0000

    xlator.h: whitespace cleanup
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 4b690df4e2055ce42557c303e3738e11c7aec172
Author: Harshavardhana <harsha@gluster.com>
Date:   Mon Mar 15 04:14:14 2010 +0000

    Fixed "." delimiter for cache-size calculation which would fail on different locale.
    
    Thanks to Filip Valder < valder (a) netdevelo.cz > for suggestions.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 720 (Default . decimal delimiter will not work for other locale)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=720

commit 536e5a2208d162801367f8a4189a29ca7fd8f1a9
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 10 02:14:55 2010 +0000

    stripe: logic fixes
    
    * for setting 'local->failed'
      Earlier, stripe was not handling different errors from subvolumes,
      and hence failure testcases using 'debug/error-gen' were failing.
      With this fix, tests pass fine.
    
    * proper event handling in notify.
      Send CHILD_UP and CHILD_DOWN events properly.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 691 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=691

commit a35b3f0c302d920bcb4c282677b14e2eba789ec9
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 10 00:30:56 2010 +0000

    stripe: whitespace cleanup
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 691 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=691

commit e0385ed5e905fb14044bb117c596cc1825193c32
Author: Sachidananda <sac@gluster.com>
Date:   Tue Mar 9 03:18:56 2010 +0000

    When option mandatory is given, print warning messages instead of Error.
    
    Change the log level to Warning instead of Error.
    Signed-off-by: Sachidananda Urs <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 704 (GlusterFS starts despite error is logged in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=704

commit 2fb2bef51a53b4c776f54633000eb41ac88fe82b
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 9 07:57:14 2010 +0000

    send lookup on every subvolume if local->hashed_subvol is NULL in nufa/switch
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 114 (Creating files or directories gives "Invalid argument")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=114

commit 06d49096fbf562690738c377db3f8825d1fc9b96
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 9 06:34:17 2010 +0000

    cleaned up some outdated files
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 491 (Outdated files in glusterfs source (Broken links in them))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=491

commit e6bb22238a9c920e4a4373da1d9c756884543028
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Mar 11 04:11:17 2010 +0000

    protocol/server: Do gf_flock to flock conversion at the right place
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 708 (solaris : ping pong test hangs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=708

commit e66adead7078163cd9d9c0bbd8ec6289b4e4ea35
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Mar 9 02:37:30 2010 +0000

    extras: Add script to be used before using quota translator.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 569 (Memory leak in quota translator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=569

commit ffc138f7f19bf55c6daf8aea7f15bde1ca3cfc6a
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 8 05:31:11 2010 +0000

    handle SIGINT in glusterfsd
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 703 (SIGINT not handled in glusterfsd)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=703

commit 8cb697667ff3da6cd497dedeeb7f65a9992145ee
Author: Anand Avati <avati@gluster.com>
Date:   Thu Mar 4 06:52:49 2010 +0000

    dht: preserve and return proper pre/postparent structures during unlink
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 689 (Segfault (11) on op UNLINK)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=689

commit 727fe837b8f7bfcdd59267f7745398934564543e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:10 2010 +0000

    quick-read: Store and propagate wbflags argument in open fop
    
    ..this is needed to ensure underlying translators like
    write-behind, ioc, etc, do not return zero-filled stats
    to NFSx.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 4b2f769dcd18fbb855d7d11b82a61bcca64fc85c
Author: Anand Avati <avati@gluster.com>
Date:   Wed Mar 3 11:51:30 2010 +0000

    distribute: cleanup intermediate hardlink and linkfile on failed rename
    
    implement a generic cleanup function which handles cleanup of
    temporary linkfiles and hardlinks created as part of the rename
    transaction, and callable from any stage of failure.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit fa194179431b7e9aac68333c91a9c3254a15335d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:08 2010 +0000

    distribute: perform self-heal as root
    
    prerserve original frame uid and gid and perform self-heal by changing
    uid/gid to root (0) temporarily.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit a8f10e72f265e96f3785f278a3c4a3631b9f0392
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:07 2010 +0000

    distribute, nufa: return 0 mtimes in preparent/postparent
    
    Returning 0 times means the values are unreliable and not to be
    trusted for the purposes of caching.
    
    This is a temporary fix till we bring in proper times handling in
    DHT to return consistant values for parent inodes.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 11433ebf94a58e0a40f115be8c6fe919c29ed61b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:06 2010 +0000

    distribute: Save ino/dev from first subvolume during mkdir
    
    A self-heal on directory creation results in the subsequent
    call to dht_selfheal_new_directory to happen only for the last subvolume.
    But when this function is called for the last subvol it is possible
    that the st_ino returned in this function's callback is the st_ino
    from the hashed subvolume(assigned in dht_mkdir_hashed_cbk).
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 549d1a81f49f58f842f69f64f7d152a3e6ecb0d0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:05 2010 +0000

    distribute: Restore parent ino from local in symlink
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 83c650fe5b11a177b56274483aeecd3127520831
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:04 2010 +0000

    distribute: Restore inode from saved ino on readv
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 0a86bd1aa3004a9f27e59eb08f8facf312234737
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:03 2010 +0000

    distribute: Respect end-of-dir on readdir only for last subvol
    
    We need to ensure that only the last subvolume's end-of-directory
    notification is respected so that directory reading does not stop
    before all subvolumes have been read. That could happen because the
    posix for each subvolume sends a ENOENT on end-of-directory but in
    distribute we're not concerned only with a posix's view of the
    directory but the aggregated namespace' view of the directory,
    which is maintained by distribute.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 59947fc4c28a0310d76a663d2440c08b762ed3fd
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:02 2010 +0000

    distribute: Return pre/post-parent on successful unlink
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit b49ad40a7e7f656b509291b07bf539c64bae3ee1
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:01 2010 +0000

    distribute: Return ino from the first-up subvolume in lookup
    
    Not returning this from the first-up subvolume results in
    
    different inode numbers being returned for a directory
    when the same directory is read again through the NFS
    readdir request.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit ed54528c22193f7e2cf6833bbcd22dc338d02c74
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:00 2010 +0000

    replicate: Use link's parent ino for post/pre-parent not target dir's
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 5493db0d0664b9ed2515758122837c0d93d0f388
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:59 2010 +0000

    replicate: Restore parent ino from saved inode number
    
    Not doing this was resulting in a 0 inode number being returned
    in postparent on lookup, which in turn results in a ESTALE at
    the NFS client since an inode number change was observed.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 8a7b7b09c96ab3f3f3426b0176cd0115f350e50f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:58 2010 +0000

    trace: Display op_errno even on successful readv
    
    ..this helps to show an op_errno that might contain
    an ENOENT sent from posix. Remember posix now sends
    and ENOENT even with an op_ret == 0 when reading
    encountered an end-of-file.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 473 (Trace misreporting pre/post attributes for setattr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=473

commit e180e55a9945c738043d148265eb40951e870a0f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:57 2010 +0000

    trace: Do not print results on failed readlink
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 473 (Trace misreporting pre/post attributes for setattr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=473

commit cbe617301a264d4193c507c06e77a8445cdf8f25
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:56 2010 +0000

    trace: Print st_dev for struct stat
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 473 (Trace misreporting pre/post attributes for setattr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=473

commit dc3e568cfa5a37e531a18f2b3628b28fbcb41f1a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:55 2010 +0000

    trace: Support new option: force-log-level
    
    trace has till now forced the log level to be set to
    NORMAL. This masks other log output that we might need
    to observed in combination with the trace output. This
    new option allows us to force the log-level to something
    other than NORMAL.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 168 (trace does not output debug messages)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=168

commit 3f467f4464755989db4d22da04ae1cb895d2db11
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:54 2010 +0000

    trace: Print correct variable in lookup_cbk
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 473 (Trace misreporting pre/post attributes for setattr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=473

commit 390f4fd29830a902d6187bc95bfd8c5f5aad5935
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:53 2010 +0000

    trace: Do not clobber own itable
    
    .. as it could've been assigned by our parent such as server or nfs.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 473 (Trace misreporting pre/post attributes for setattr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=473

commit 1582bc4e20d3f800c88d1c526cd32e92acf779dc
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Mar 3 11:50:23 2010 +0000

    core: Provide helper macro to set [ug]id in frame
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 400 (Support auxiliary gids in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=400

commit efa1ce755bca123507997e6b5f3e27482fc0e3af
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:51 2010 +0000

    core: Add NULL check for inode in fd_lookup
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit ac93e41b70d27c077ac295a1c288938156f241b0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:49 2010 +0000

    core: Add setattr mode test macros
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 508075b079d731f7aa5fa36d7295fceeef2c3c1d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:48 2010 +0000

    core: New function: gf_dirent_for_namelen
    
    Given the length of a name that needs to be stored in d_name, the
    new function allocates enough space for a gf_dirent_t and
    returns a ref.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 9fe5c6d391fd159fe27022ab806408831ed5b27f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:47 2010 +0000

    posix: Support EOF for file reading
    
    This is a small hack to notify higher translators that an end-of-file
    was encountered at the end of the readv operation. This is helpful
    in determining end-of-file without sending another readv fop.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit 1262b1e4fe3fcdfe3f8d6e3c29f41de68cfe8fa3
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:46 2010 +0000

    posix: Support end-of-stream determination
    
    state, higher translators do not need to perform another readdir
    to determine end of stream. Instead, if a successful directory
    read operation is accompanied with an op_errno=ENOENT, it means
    end-of-stream on the directory fd_t.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit bdf3fc698515b44e6f1a11f6dbc8d9ff4b5fd74e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:37:45 2010 +0000

    iobuf: Expose macros and create new ones
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 597 (miscellaneous fixes for xlators to work well with NFS xlator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=597

commit db199434dfccfb4db5335f6ba18298e9e61bc415
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Mar 3 02:14:37 2010 +0000

    transport/socket: fix to valid_ipv6_address.
    
    - while checking for hexadecimal numbers, strtol on valid strings of
        hexadecimal numbers will return a NULL string in endptr (but not a
        NULL endptr). Thanks to Donald Neal <dmneal@wand.net.nz>, for pointing
        this out.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 693 (glusterfs 3.0.2 will not listen on IPv6 address)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=693

commit 85a1716cd55b002b5d20a7903e28f106ee614814
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Mar 1 17:47:06 2010 +0000

    cluster/afr: Failover readdir calls.
    
    This patch makes the replicate readdir call fail over to the next
    subvolume if the first call fails. It takes care to ensure that
    entries are not duplicated.
    
    The failover behavior of readdir only comes into effect if
    the option 'strict-readdir' is on.
    
    Signed-off-by: Vikas Gorur <vikas@dev.gluster.com>
    Signed-off-by: root <root@client02.(none)>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 453 (afr_readdir does not fail over)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=453

commit 2970ec54473fd55b27aeeb43a1f6bca879281cf0
Author: Anand Avati <avati@gluster.com>
Date:   Thu Mar 4 04:00:53 2010 +0000

    io-stats: new counters
    
    Add new counters and statistics for:
    
    a) total read data - since process start, last interval and per fd
    b) total write data - since process start, last interval and per fd
    c) counts of read IO block size - since process start, last interval and per fd
    d) counts of write IO block size - since process start, last interval and per fd
    e) counts of all FOP types passing through it
    
    Usage:
    
    1. For dumping global stats
    
    sh# setfattr -n io-stats-dump /tmp/filename /mnt/gluster
    
    2. For enabling per-fd stats
    
    option dump-fd-stats on
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 268 (Add timing instrumentation code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=268

commit 90fbc2d6e32eb4d9dbd4ddf1fe77751013003640
Author: Anand Avati <avati@gluster.com>
Date:   Thu Mar 4 03:59:55 2010 +0000

    io-stats: indentation fixes
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 268 (Add timing instrumentation code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=268

commit c90fd15d335ad452618faf410182ab195193cbc4
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Mar 3 12:52:01 2010 +0000

    libglusterfs: Copy va_list types using va_copy instead of memcpy.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 621 (3.0.2 GlusterFS fails on Solaris 10)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=621

commit 25126f64ea049a374fcd724a793328db7c96037f
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Mar 2 07:20:31 2010 +0000

    posix: gen number fixes on non-Linux systems
    
    Most non-Linux platforms do not support extended attributes on special
    files and symlinks. Use the mtime as the generation number for these
    files on such systems
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 621 (3.0.2 GlusterFS fails on Solaris 10)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=621

commit f2097590eb05e3b8e5946aa1966cfd29bfd23dc5
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Mar 2 03:45:26 2010 +0000

    features/quota: Remember '/' loc_t to initiate xattr calls.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 685 (writing to a file fails complaining of "Transport endpoint not being connected")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=685

commit 2c7e6f22f7efc3c55593d3ef5467063ca4a49256
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Feb 25 15:38:11 2010 +0000

    socket: Add NULL check for failed ioq entry allocation
    
    This is seen in OOM situations.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 679 (Crash in socket_ioq_new)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=679

commit bcab556247cc6f008cafb9df2128cc99d5cc6047
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Feb 25 05:17:02 2010 +0000

    features/quota: store the entire vector in local instead of just a pointer to it in writev.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 685 (writing to a file fails complaining of "Transport endpoint not being connected")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=685

commit 12c06f4e1723cec1d9e7e3d7e653e2ae14e18659
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Tue Mar 2 03:46:34 2010 +0000

    local->failed set to one twice
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 690 (local->failed set twice)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=690

commit bf0b366cc90ed8bc9932be69bfff1456af65cd02
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 1 03:14:39 2010 +0000

    stripe read fix (when read() is done on a sparse file over glusterfs)
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 536 (fsx tool fails over stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=536

commit 904fef5cfece1e6eb69510b7409efe779867ca0a
Author: Anand Avati <avati@gluster.com>
Date:   Sat Feb 27 07:00:10 2010 +0000

    io-threads: more fixes
    
    * conditional for scaling up threads was wrong
    
    * ETIMEDOUT check was performed wrongly
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 583 (filesystem access hangs while deleting large files)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=583

commit 042fe15e637c4bfe569d9b1c3a7e30889895c109
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Feb 23 13:50:25 2010 +0000

    storage/posix: Don't use FTW_CONTINUE
    
    FTW_CONTINUE is not defined on Mac, and POSIX only specifies
    that the walker function must return 0. So just return 0.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 625 (Gluster Fails to build on OS X 10.6.2)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=625

commit 24309c6e131a5bf84b05ae26d10838b94ffd28c4
Author: Anand Avati <avati@gluster.com>
Date:   Tue Feb 23 02:52:46 2010 +0000

    dht: fix READDIR semantics which got broken in 512dcad823feb199d78f5b66a09bc404ccb899e8
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 584 (automatically configure 'lookup-unhashed' option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=584

commit fa598e1bbb33125f0463f4cfc382206fbabb352d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Feb 22 23:59:05 2010 +0000

    performance/write-behind: fix data corruption while aggregating the adjacent contiguous iobufs into a single iobuf
    
    - while aggregating, we should make sure that the destination has enough
       memory. __wb_collapse_write_bufs assumed that destination vector's iov_base
       was aligned to the start of an iobuf and hence memory of page_size is
       available for aggregation. This assumption is not always true, like in the
       configuration consisting afr->write->io-cache (afr is on top). Refer to the
       bug url for more details.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 542 (write-behind crashes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=542

commit b7c361c6c387fe858a51e65cbc6e3be0724bb088
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Feb 22 23:58:35 2010 +0000

    performance/write-behind: refactor __wb_collapse_write_bufs
    
    - refactor done to remove duplicated code.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 542 (write-behind crashes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=542

commit 30207094c563e7e4f2d6e1f4c54abd7e918c22d4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Feb 23 01:27:21 2010 +0000

    performance/io-cache: set path in local during lookup.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 570 (Cache only those files whose sizes falls under a configured window size)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=570

commit 5ae4f11319de9a800a595175678762f9fc924755
Author: Anand Avati <avati@gluster.com>
Date:   Mon Feb 22 11:00:20 2010 +0000

    io-threads: single queue/multi-thread model
    
    This patch lets io-threads work with a single queue and multiple
    threads work on picking the next request from the queue and process
    it.
    
    Whenever the number of pending requests in the queue double, a new
    worker thread is spawned.
    
    Workers expire after a (configurable) timeout of inactivity
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 583 (filesystem access hangs while deleting large files)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=583

commit 5f524f4b2f0dbccfe6c8d4aab16ce425dd6d2b50
Author: Anand Avati <avati@gluster.com>
Date:   Mon Feb 22 10:59:40 2010 +0000

    common-utils: gf_log2 handles 0 input
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 583 (filesystem access hangs while deleting large files)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=583

commit 2a78ca786da6233cce3ed9603676aa9ef293e3cf
Author: Anand Avati <avati@gluster.com>
Date:   Mon Feb 22 09:23:13 2010 +0000

    dht: fix leak introduced in 137f94ed123b1c7c7ada541aaa599679e19888f6
    
    dht_layout_t was getting leaked in dht_readdirp_cbk when dht_layout_get
    was called but was not unref'ed
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 584 (automatically configure 'lookup-unhashed' option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=584

commit 9dbae0c80569689533c92a29871e3fa6dbbae1b9
Author: Anand Avati <avati@gluster.com>
Date:   Mon Feb 22 08:59:10 2010 +0000

    dht: unlink stale linkfiles in rmdir to prevent ENOTEMPTY
    
    Thanks to He Xaobing <allreol@gmail.com>, this patch is inspired by
    
    http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=188#c2
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 188 ([ glusterfs 2.0.6rc2 ] - "Directory not empty" on rm -rf)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=188

commit 96ed73c1556da79e0a58cf1c051471a9b322b05b
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Feb 22 05:17:28 2010 +0000

    storage/posix: Check for path before logging it in case of an error in xattrop FOP.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 614 (GlusterFS crashes while printing error if fsetxattr call fails in posix)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=614

commit a748fd6bfe1ab2d0df439b180ca109c70deac835
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Feb 22 05:01:00 2010 +0000

    features/quota: Changes in arguments in STACK_UNWINDs for most FOPs.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 569 (Memory leak in quota translator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=569

commit ec7277113956520fa6637c94d60d13d398617225
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Feb 22 05:00:01 2010 +0000

    features/quota: Fix memory leak while syncing disk usage.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 569 (Memory leak in quota translator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=569

commit bca308d50d90559b33fe7e1e6ee18b8f194552f3
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Feb 22 04:39:26 2010 +0000

    Add new gf_strstr dropin replacement for "strstr"
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 609 (Add new "conf-dir" option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=609

commit 867b0beafbcd4dde7515923e21302926a1ca9fb9
Author: Anand Avati <avati@gluster.com>
Date:   Mon Feb 22 04:28:07 2010 +0000

    inode: guard against possible infinite loops
    
    Check to prevent accidental linkage of inodes with inode number 1.
    Such links will result in loop formation in the inode table.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 537 (infinite loop in inode_path ())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=537

commit fa3b447cb058a7012ed2f68b89bc9b9e933c7367
Author: Anand Avati <avati@gluster.com>
Date:   Mon Feb 22 03:42:04 2010 +0000

    protocol/client: better pointer check on saved_frames mapping in ping timer
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 434 (Crash with 3.0.0pre2 on client01 with "metarates" parallel MPI metadata benchmark)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=434

commit 40a07c180a479472b7fac8f16b7d825ca26f6f50
Author: Anand Avati <avati@gluster.com>
Date:   Mon Feb 22 02:52:31 2010 +0000

    protocol/client: add memory allocation checks
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 431 (segfault in timer thread :O)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=431

commit 94d31fdaf967f0d224a2bfa7b275b0344e0f5700
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat Feb 20 18:53:38 2010 +0000

    fuse: bring over recent mounting code changes from libfuse upstream
    
    Following commits were ported (commit ids as of
    http://git.gluster.com/?p=users/csaba/fuse.git
    repo):
    
    commit 06fe3eb9c864b69bea98600c0a7eab7b63834735
    Author: mszeredi <mszeredi>
    Date:   Thu Feb 18 11:05:12 2010 +0000
    
        * Fix stack alignment for clone()
    
     ChangeLog               |    4 ++++
     include/fuse_lowlevel.h |    1 +
     util/fusermount.c       |    9 ++++-----
     3 files changed, 9 insertions(+), 5 deletions(-)
    
    commit dfe1aab6520d70d72d36edf0508fef9a865daa5f
    Author: mszeredi <mszeredi>
    Date:   Tue Jan 26 18:20:12 2010 +0000
    
        * Fix race if two "fusermount -u" instances are run in parallel.
        Reported by Dan Rosenberg
    
        * Make sure that the path to be unmounted doesn't refer to a
        symlink
    
     ChangeLog         |    8 +
     lib/mount.c       |    2 +-
     lib/mount_util.c  |   31 +++--
     lib/mount_util.h  |    3 +-
     util/fusermount.c |  380 +++++++++++++++++++++++++++++++++++++++++++++--------
     5 files changed, 351 insertions(+), 73 deletions(-)
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 657 (Metabug for tracking fuse upstream)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=657

commit f9269f4776141ae78fb10d1bf5ae63da7595a369
Author: Raghavendra Bhat <raghavendrabhat@gluster.com>
Date:   Sat Feb 20 06:06:19 2010 +0000

    fuse: check the return value of pthread_cond_timedwait before logging in fuse_thread_proc
    
    Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 650 (log message says "pthread_cond_timedout returned nonzero value" even when the return value is zero)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=650

commit 2cf958fd48129f682c19645ef007f9b1fe9fcd82
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Feb 11 10:29:11 2010 +0000

    Support new option "conf-dir"
    
    Addresses fetching volume files from a non standard directory right
    now it is hardcoded to "CONFDIR" which is build time constant.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 609 (Add new "conf-dir" option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=609

commit 54b77d368f5a0e7cef6da6754c14a16d05dc7dda
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Feb 14 09:28:34 2010 +0000

    cluster/stripe: Set op_ret as failure if inode is not being set in lookup cbk
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 560 ()
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=560

commit 52aa84d64cda85c2f3d07c71c9cfe7e1c18d250d
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Feb 18 09:41:17 2010 +0000

    Add quota support to volgen
    
    New options on command line
    1. --volume-size-server  - Volume sizes for server side posix exports
    2. --volume-size-client  - Volume sizes for client side exports
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 611 (Add quota support to volgen)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=611

commit 961cb224ddc86b5e35fe84c0f59d93720b7f86c7
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Wed Feb 17 06:36:28 2010 +0000

    Remove dns lookup issued for each hostnames.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 563 (glusterfs-volgen: can't handle multiple network interfaces)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=563

commit 23fe45312765c1af8788aa103c51703a2fc28220
Author: Anand Avati <avati@gluster.com>
Date:   Thu Feb 18 10:28:06 2010 +0000

    server_writev: add proper iobuf into iobref
    
    this typo results in corruption when write-behind is loaded on server side
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 639 (Data corruption with  write-behind on server side)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=639

commit f823b85d80bd2c9563a7a9d8762ea668dee13176
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Feb 12 04:08:03 2010 +0000

    features/locks: Set dummy fd ctx in all relevant places so that release callback in locks is always called.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 449 (Handle flock calls in a different domain from fcntl calls)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=449

commit 090a96d0a5963bc62efc3354480e277610cab7e6
Author: Anand Avati <avati@gluster.com>
Date:   Sun Feb 7 04:30:20 2010 +0000

    dht: Remove pointer casting in layout handling
    
    Small changes by Anand Avati <avati@gluster.com> over original submission:
    
    Remove pointer casting (copy data to proper memory before using it). Fixes bug #493.
    Hello,
    
    See bug #493 for more information on this patch.
    
    http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=493#c2
    
    This patch assumes that the scope of disk_layout is local wherever it is
    used. Seems correct, not really checked, though.
    
    Greetings,
    
    Hraban Luyat
    
    Signed-off-by: Hraban Luyat <hraban@0brg.net>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 493 (tcp + dht + armv5tel: ???brick: disk layout has invalid count 29696???)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=493

commit fd4523e667f19cf5c4f3849679aacf41f860a766
Author: Hraban Luyat <hraban@0brg.net>
Date:   Mon Dec 21 01:29:46 2009 +0000

    Fix memory access in afr's self-heal code (replace pointer casts by memcpy).
    
    The previous patch I submitted for this file (afr's self-heal code)
    introduced a terrible error. I overlooked the error checking in the
    original code and misplaced the memcpy (too early).
    
    So, please disregard the last one, this one is better :) hopefully.
    
    Apologies.
    
    Signed-off-by: Hraban Luyat <hraban@0brg.net>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 493 (tcp + dht + armv5tel: “brick: disk layout has invalid count 29696”)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=493

commit 137f94ed123b1c7c7ada541aaa599679e19888f6
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Feb 5 01:38:29 2010 +0000

    'lookup-unhashed' option of distribute should be 'auto' by default.
    
    * Added 'auto' option, older boolean options works as they used to.
    
    * This option should make 'create' rate faster, also handles
      self-healing of linkfile properly in case of scaling to
      more servers or filesystem is getting full.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 584 (automatically configure 'lookup-unhashed' option)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=584

commit c3005ce736d6bb3391e5f46930d355fc6b0f4d6e
Author: Anand Avati <avati@gluster.com>
Date:   Fri Feb 5 05:00:20 2010 +0000

    Fixes for MacOSX and Solaris build
    
    Fixes for Solaris and MacOSX build errors.
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 481 (Fix compilation failures in Solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=481

commit 4f736b6eb9d761287b6bf4ecfc19974a43a8644f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Feb 1 07:31:40 2010 +0000

    cluster/dht: Remove linkfile before unlinking the datafile.
    
    dht_unlink: If a linkfile exists, remove it first before attempting
    to remove the datafile. This eliminates the case where dht would
    end up with the linkfile intact and the datafile gone, and the user
    not being able to remove the linkfile.
    
    Thanks to He Xiaobin <allreol@gmail.com> for debugging this
    issue.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 188 ([ glusterfs 2.0.6rc2 ] - "Directory not empty" on rm -rf)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=188

commit 8bcc534da4b2b29709a80327687085876b02ff5a
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Feb 2 06:51:15 2010 +0000

    storage/posix: Set op_ret to -1 when open fails.
    
    Thanks to Jeff Darcy <jdarcy@redhat.com> for
    the bug report and the patch.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 581 (posix_open does not report open(2) failures correctly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=581

commit 902422d4de87b5db099cf084025120cc980fabbd
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Jan 29 03:26:12 2010 +0000

    performance/write-behind: Set right an incorrect message displayed in log
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 579 (write-behind cache-size less than 128KB leads to error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=579

commit 4462b4a31e7ac3a4394f46d7d3067cc03fd24dee
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Jan 28 08:24:23 2010 +0000

    cluster/dht: Check for size 0 in check_is_linkfile()
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 574 (Sticky bit files are not listed in the output of ls on a dht volume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=574

commit 15b3f715ac6c7dc127723908f269f0418b61de71
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jan 27 07:19:43 2010 +0000

    transport/socket: guess an appropriate address family when it is not specified in configuration.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 561 (with address family set to 'inet-sdp', transport/socket doesn't work correctly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=561

commit e5a43ac65f60b7c4163eba6d7e15b60c54879813
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jan 28 06:55:05 2010 +0000

    storage/posix: Fix device number handling.
    
    There are two fixes in this patch:
    
    1) If the device number has changed, do a fresh stat on the export
       directory and if it matches the device number of the file,
       assume a remount happened and remember the new device number
       as official (this helps automounted export volumes).
    
    2) Don't log the "device number changed" message if it is due
       to a stat on ".." (in posix_readdirp), as it could be because
       ".." leads us out of the exported volume.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 576 (crossing device (2056) + fuse LOOKUP error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=576

commit 5a574d96c392b19a92bb925b4b4dd268393831ea
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Tue Jan 26 09:06:18 2010 +0000

    Revert "Server backend storage hang should not cause the mount point to hang."
    
    This reverts commit a0b148ea4e2a0163548eeb89b7580be4adbb8070.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 272 (Server backend storage hang should not cause the mount point to hang)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

commit ffc36da0fd9a925aa2a23026b9244787d2c0a5fd
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Tue Jan 26 03:43:15 2010 +0000

    Fix fetching volume file from the server, by sending parent up through the xlator graph.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 573 (3.0.1 doesn't fetch volfume files from the server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=573

commit 6041019b63cef990d9892ea2a1cfe219166509df
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Jan 25 07:02:45 2010 +0000

    mount/fuse: Fix file type checking.
    
    This patch fixes two things:
     - Check for symlinks and set d_type appropriately
     - Use S_IS* macros for checking.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 571 (find -type l ignores symlinks on GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=571

commit 7b12c4eb7e20251b9b128e905518478df25d2af2
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Jan 25 05:59:28 2010 +0000

    storage/posix: Fix an access-after-free bug in release() and releasedir().
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 533 (close() should not block main loop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=533

commit 61dbadb2e775d8f2011157c453100a77024e87bf
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Jan 25 05:43:24 2010 +0000

    performance/io-cache: cache only those files whose size falls under configured window.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 570 (Cache only those files whose sizes falls under a configured window size)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=570

commit 3eef8dfd1bd7775e2b5ddddb07726b4bf4f6ee22
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Jan 25 05:09:40 2010 +0000

    Fix occurence of cache-size being floating point
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 516 (cache-size should not be hard-coded to 1GB)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=516

commit e5f49cc81a976489cb7629cdf1aacf467e9e22a5
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 17:37:38 2010 +0000

    protocol/client: timeout tweaks
    
    * option frame-timeout 0 now means no frame timeout
    * option ping-timeout 0 now means no ping timeout
    * extended frame-timeout range from 0 to 1 day
    * extended ping-timeout range from 1
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 450 (frame-timeout range should be higher)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=450
    
    BUG: 423 (Disable protocol timeout)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=423

commit 83d1db8ee0cc79a8d5532df0d61d0efc8c1fc0a6
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 16:52:48 2010 +0000

    trace: multiple fixes
    
           Jeff Darcy <jdarcy@redhat.com>
    
           Jeff Darcy <jdarcy@redhat.com>
    
    - whitespace and indentation cleanup
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 168 (trace does not output debug messages)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=168
    
    BUG: 473 (Trace misreporting pre/post attributes for setattr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=473
    
    BUG: 519 (Possible SEGV when tracing readlink)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=519
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit c9a205497328a0d9ad0d005ae5c2483011e852f9
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 15:18:21 2010 +0000

    protocol/server: unlink dentry only for non-root inodes
    
    in server_lookup_cbk, unlink dentry from the crash on receiving
    ENOENT from subvolume only for non-root inode. ENOENT can be returned
    for root inode if export directory is deleted
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 526 (glusterfsd crash when export dir is deleted and revalidate happens on /)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=526

commit bc111de015918ceeb0234596860a461dccb6862c
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 14:49:05 2010 +0000

    write-behind: fix 'option enable-trickling-writes'
    
    fix logic in __wb_mark_winds to properly initialize incomplete_writes
    and conditionally check based on enable_trickling_writes flag
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 547 (write-behind enable-trickling-writes working?)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=547

commit 899b89a8c2faee55128db392cdb426e08e2289e7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Dec 23 15:06:38 2009 +0000

    booster/fcntl: implement F_GETFD and F_SETFD.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 446 (apache does not start in daemon mode on fedora core 11.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=446

commit da505a63c12ea9be0e783711547fe7bbfecf05ea
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 13:26:39 2010 +0000

    dht: initialize layout type
    
    Instead of relying on CALLOC's zero initialization which happens
    to be the value of DHT_HASH_TYPE_DM, explicitly set the value
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 523 (Hash type is not initialized in dht_layout_new)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=523

commit 6313f854fb41ef0a61a40b08a4cf05254763eb21
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Jan 23 12:53:56 2010 +0000

    protocol/client: Look only for op_ret while handling a setvolume response.
    
    op_errno should not be looked up to stop processing setvolume_cbk().
    This fixes the problem of 3.0.x clients crashing if they attempt to
    connect to 2.0.x servers.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 564 (3.0.1rc3 server daemon crashes when any of the 2.0.x version client connects)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=564

commit 502fef89bb352aa8092c3b2e606757c5ef644171
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 07:03:08 2010 +0000

    error-gen: change all STACK_UNWIND calls to STACK_UNWIND_STRICT
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 6f15b21994e26925a587ab8965ab909abbfbeece
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 07:02:35 2010 +0000

    error-gen: unwind fsync with proper parameters
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 553 (server crashed in server_fsync_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=553

commit 546168723f5b04a95aa1dab80679591335c5fc75
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 05:14:49 2010 +0000

    protocol/server: cleanup whitespaces
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 272 (Server backend storage hang should not cause the mount point to hang)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

commit a0b148ea4e2a0163548eeb89b7580be4adbb8070
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 05:14:31 2010 +0000

    Server backend storage hang should not cause the mount point to hang.
    
    Submitted-by: Krishna Srinivas <krishna@gluster.com>
    NOTE: fixed compilation issues in posix.c introduced while merging
    
    storage/posix polls for FS/kernel being functional by issuing
    statvfs() call. In case statvfs expires the timer, storage/posix will
    send CHILD_DOWN to upper translator. Ultimately this will cause
    protocol/server to disconnect all clients connected and also cleans up
    the data structures. Hence if soft lockup or other kernel bug causes
    backend FS to hang, the clients will not be hung.
    
    Signed-off-by: Krishna Srinivas <krishna@gluster.com>
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 272 (Server backend storage hang should not cause the mount point to hang)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

commit 9c53d5daf403f6fbfde76dec121295a4c156b32e
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 05:13:24 2010 +0000

    core: fix initialization of disjoint xlator graph
    
    if graph has disjoint subgraphs, send GF_EVENT_PARENT_UP to every top node
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 272 (Server backend storage hang should not cause the mount point to hang)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

commit 95dba6f085379ce8e07f316bc92c479956b5b221
Author: Anand Avati <avati@gluster.com>
Date:   Sat Jan 23 00:46:16 2010 +0000

    protocol/server: handle group id decoding in a stricter way
    
    This causes crash between 3.0.x servers and 2.0.x clients
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 564 (3.0.1rc3 server daemon crashes when any of the 2.0.x version client connects)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=564

commit 375f08e1b56f61c5687bb276fb95bea230085f77
Author: Anand Avati <avati@gluster.com>
Date:   Fri Jan 22 08:53:49 2010 +0000

    transport: set proper reference counts on peer_trans for local connections
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 562 (crash resulting from bad refs in transport_setpeer)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=562

commit a116e5b3ef2d4fbb57a5690a01368ec7aa0942aa
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Jan 22 03:02:32 2010 +0000

    transport/socket: use appropriate address family macro when address family is inet-sdp.
    
    - sa_family should be set to AF_INET_SDP only during call to socket system
        call. For all other calls, sa_family should be AF_INET.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 561 (with address family set to 'inet-sdp', transport/socket doesn't work correctly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=561

commit ab8cabcd30bbb5dde4cb8a35d4fd88136994f526
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Jan 21 05:36:42 2010 +0000

    Cache size is now dynamic and is 20% of the total memory on the client side.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 516 (cache-size should not be hard-coded to 1GB)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=516

commit 27399cc92d62a168f768c490fc19c935e7e513f1
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jan 21 07:28:59 2010 +0000

    cluster/afr: Send the struct flock returned by the server to the user.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 521 (SPECFS validation fails over distribute + replicate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=521

commit 84fe79c086a4623e1bb1c0ca5cebff19d19d15ec
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jan 21 06:46:25 2010 +0000

    storage/posix: Make the janitor sleep duration configurable.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 533 (close() should not block main loop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=533

commit a6a1f596a443b6a015dca6435f1d22fc582acc80
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Jan 19 08:11:05 2010 +0000

    extras: Add defrag scripts to the repository
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 478 (Add defrag scripts into glusterfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=478

commit a23185f3a43ec95a56af9f0f543b67a1fcfb4852
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Jan 15 06:59:00 2010 +0000

    storage/posix: Hand off calling close() and closedir() to the janitor thread.
    
    Let the janitor thread handle calling close() and closedir() on fd's and DIR *
    when posix_release is called. This avoids blocking the main server loop
    due to close().
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 533 (close() should not block main loop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=533

commit 4951f4dcc1b795b42fa845b6a89a9902af5b6586
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jan 12 13:21:59 2010 +0000

    stripe entry self heal
    
    Create the entry (either regular file or directory), when its
    missing in some of the subvolumes and available on some.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 535 (stripe entry self-heal..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=535

commit e6f074f93195b2e7d92812f26782e8dc281a1329
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Dec 30 21:45:20 2009 +0000

    default log file now doesn't start with '-'
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 490 (Default log file path should not begin with '-')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=490

commit 5522f6eaef99616efe01b8f4688be0486e511b12
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jan 12 04:14:25 2010 +0000

    cluster/afr: Pick a source for metadata self-heal even if all nodes are innocent.
    
    If metadata changelog has been disabled, all subvolumes
    will be innocent. In that case, simply pick the subvolume
    on which the file has the lowest uid as the source and
    sync other subvolumes to it.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 451 (metadata self-heal does not a pick a source if mode/times have been changed at the backend)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=451

commit da09bf7fafa725db7f6e778f7fb5645276978948
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Jan 12 17:47:25 2010 +0000

    libglusterfsclient/readv: fix data corruption.
    
    - libgf_client_readv should return the total number of bytes read by
         multiple invocations of libgf_client_iobuf_readv, instead of return value
         of last invocation.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 531 (accessing a file through apache results in Permission denied errors.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=531

commit a1965b73da712644d1536d0dac3212041de5eb0c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Jan 6 20:18:47 2010 +0000

    cluster/unify: don't call xl_init_tree on namespace node.
    
    - just before xl_init_tree call on namespace, unify node is set as parent of
        namespace node and since xl->ready of unify node is set only after return
        from init call, calling xl_init_tree on namespace node will result in
        execution of init of unify node for the second time. This results in
        following bugs:
    
        * since during second execution, parent of namespace node is unify, init of
          unify xlator fails.
        * even if init did not fail, re-execution of init in itself is bad, since it
          results in memory leaks etc. Worse, it can result in infinite recursive
          calls into init of unify node.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 518 (unify does not start)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=518

commit 7317a250caa96b00072a8a7cb2b2c18016e8a8d2
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Jan 11 01:20:21 2010 +0000

    features/locks: Fix broken interface grant_blocked_inode_locks
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 496 (deadlock in pl_inode_setlk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=496

commit 3647c9707f0124ae2fea21b4d501461e0e9b0169
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Jan 11 01:19:05 2010 +0000

    features/locks: Do not call grant blocked locks in pl_forget
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 496 (deadlock in pl_inode_setlk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=496

commit d0c355917839ac06463ea1d0852eb56835cb7b45
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jan 12 03:57:42 2010 +0000

    fuse: treat DESTROY message as proto requires, ie. don't leave it unanswered
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit fb234e86288776386daad21fd6632414376b1cdc
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Jan 8 12:22:45 2010 +0000

    transport/socket: Enable NODELAY even if no option is set.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 524 (TCP_NODELAY not set when expected on client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=524

commit 2674d226f41bf090c8f69c676f22102f877a75c5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 24 12:10:09 2009 +0000

    libglusterfs/inode: add NULL checks.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 510 (crash in inode_ref)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=510

commit 3adb7082c63d28950aca21718be84b65806e5d6e
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jan 7 05:17:17 2010 +0000

    cluster/afr: Use dict_ref instead of dict_copy_with_ref.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 509 (Crash in afr_local_cleanup ())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=509

commit 90d18c74defcc11ee4b31c49d2700f96c18016e9
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jan 5 07:19:40 2010 +0000

    fuse: fix memleak
    
    continuing the work of d281971e
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 438 (Memory leak)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=438

commit 013850c9bedacdb868eee6b70f3aa6b46d4acfab
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Dec 24 06:59:44 2009 +0000

    fuse: add mtab entry asynchronously
    
    Instead of taking libfuse's approach to the bug referred
    -- making use of an ad-hoc mount option --, we get over
    the issue by not waiting for mtab manipulation to complete.
    If mtab manipulation happens to fail for some reason, just
    log an error message (instead of aborting the mount).
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 511 (mount hangs with some audit configurations)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=511

commit ea1403d8d922c3f08dc6feecc17d6eb33b8a72d2
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Dec 24 05:30:42 2009 +0000

    storage/posix: Zero out the checksum array in rchecksum.
    
    Set the checksum bytes to zero to ensure random junk
    is not returned as the checksum.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 3bcf8d4ce67654e2b5648ae11aaeb2e49dbcfa95
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Dec 28 06:07:48 2009 +0000

    cluster/afr: Allocate diff algorithm loop_state structures only once.
    
    Instead of CALLOC'ing a loop_state structure at the beginning
    of every loop, keep a table of allocated structures and reuse
    them.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 9658e13bd91849f75d968376aae5b937aabec512
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Dec 24 05:30:40 2009 +0000

    cluster/afr: Report number of blocks healed during diff self-heal.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 9331e101a4cd0a3faff25cf7dd603762296c7345
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Dec 24 05:11:40 2009 +0000

    protocol/client: Fail revalidate with ESTALE.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 6917011ee224fc41f6ca46a674d9c2df4e72913a
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Dec 22 01:53:33 2009 +0000

    properly ref/unref fd in stripe_opendir_cbk
    
    fixes the crash due to dereferencing NULL fd pointer
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 497 (Client crashes in fuse_fd_cbk while running ltp tests)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=497

commit 77d9a17a712a250c773a2bc724f16ecb3a3aa919
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Dec 21 04:30:04 2009 +0000

    features/locks: Unwind if inode is NULL to prevent 'lost' frame.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit 96ae032a9cb9b198f31e26aba30a39e5148a2ba4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Dec 18 12:38:04 2009 +0000

    Support for Compilation on Solaris
    
    This is based on patch at:
    
    http://node3.rnode.ru/glusterfs-3.0.0-p1.patch
    
    Thanks to Petrunin Egor <shellcode@mail.ru> for this patch.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 481 (Fix compilation failures in Solaris)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=481

commit 2a51ab19e6370325a5ebac9ed63f8606738919ec
Author: Hraban Luyat <hraban@0brg.net>
Date:   Sat Dec 19 15:47:25 2009 +0000

    More robust dictionary (un)serialization (fixes bug #397).
    
    Hello,
    
    This patch fixes bug 397: dictionary (de)serialization used pointer
    casting which forced word-alignment on (at least) armv5tel, causing
    corruption while writing and reading buffers into memory. It also adds
    some debugging (more information in case of errors).
    
    I tried to send this a few times already but I think it got bounced from
    the list.
    
    Greetings,
    
    Hraban Luyat
    
    Signed-off-by: Hraban Luyat <hraban@0brg.net>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 397 (dictionary serialization / deserialization fails on armv5tel)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=397

commit ea18fce5cd759a19aa928393a4b30cb87d33beec
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Dec 18 07:51:12 2009 +0000

    fuse-bridge: Don't try to fill a loc in setattr when we can proceed on with an fd.
    
    This fixes broken ftruncate on unlinked files.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 472 (OpenOffice fails on GlusterFS $HOME due to fuse_loc_fill error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=472

commit 40541428c7df4192d93b6bc61a92784ca56c8b3f
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Dec 18 07:49:43 2009 +0000

    fix typo in configure.ac
    
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 4921bc8c0fd045fdb82eb21eb358d378cdcad976
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Dec 18 07:06:27 2009 +0000

    distribute: Dont dereference sbuf on failed readlink_cbk
    
    This fixes a crash that was caused due to a NULL pointer deref
    because a NULL sbuf is returned if the readlink fop fails.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 492 (distribute crashes in readlink)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=492

commit ff5170faa131b201bf8170601dbeae18b400542f
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Dec 17 15:41:21 2009 +0000

    Added null checks in "fini"
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 364 (Segfault in io-cache)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=364

commit cfe095763c4ec59026467e3b76a92c61c18f0792
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Dec 16 19:09:16 2009 +0000

    bug fixes in call-stub creation for {fsetattr, fxattrop}_cbk()
    
    'wind' flag was set in case of 'unwind' stubs, causing wrong variables
    to get free'd, causing process to segfault.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 483 (booster unfsd segfault)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=483

commit b64d55a5b879812ff01f749a609238316031f332
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Dec 16 00:48:16 2009 +0000

    cluster/dht: Check for pointers before de-referencing in dht_stat_merge()
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 463 (Crash in dht_stat_merge ())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=463

commit d049402c7336df73b1af7524f5f06a42069aa6b5
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Dec 14 17:59:15 2009 +0000

    more cleanup in stripe stat structures
    
    Removed few more 'fops' from stripe. More cleaner stat structure return.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>
    
    BUG: 340 (Kernel Compilation fail in stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=340

commit 32b3961727cb61aed79de80bdc2c46da0dcea4d8
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Dec 11 08:50:34 2009 +0000

    fix typo in posix
    
    Signed-off-by: Vijay Bellur <vijay@dev.gluster.com>

commit 8379edd97876a85fe1231b7cc8d4cc40f962c5cc
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Dec 7 09:43:23 2009 +0000

    Disable fusermount by default in the rpm spec file and remove bdb references.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 349 (FreeBSD compilation error (alloca.h).)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=349

commit f0a026b837df2c85d44e1991a802d00201402a47
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Dec 7 02:07:39 2009 +0000

    Changed occurrences of Z Research to Gluster
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>

commit 2fa7e528f50236355aa29874bd57d96c429ef33f
Author: Anand Avati <avati@gluster.com>
Date:   Mon Dec 7 07:33:49 2009 +0000

    resolver: include RESOLVE_EXACT type for failure case when inode not found
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit a12bfdc8f32212354824a1b8dd7b27840518c4dc
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Dec 7 05:44:31 2009 +0000

    cluster/afr: Sync the parent directory's mtime during missing entries self-heal.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 137 (Parent directory mtime not reset after a create in self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137

commit 0ae2b4be39214426a50f5e1fd09562f309819f32
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Dec 7 04:52:47 2009 +0000

    cluster/afr: Don't do entry self-heal in the background.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 326 ([2.0.8rc9] Spurious self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

commit 7499335588eabb578c4dab06263cd416a4f3b2d5
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Dec 7 04:40:57 2009 +0000

    cluster/afr: Hold inode lock on 0-infinity for a flush transaction.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 326 ([2.0.8rc9] Spurious self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

commit 4fdfc9fdcce340209d35e62f585c5897ca2a1104
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Dec 6 21:18:53 2009 +0000

    fix typo in 76d6f3fbe
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit e026edec58aa234ef0c923eb6fed50dc227b7f8a
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Sun Dec 6 21:16:12 2009 +0000

    Save st_dev properly in stbuf.st_dev from the same subvolume.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 433 (Posix conformance test failed on 3.0.0pre2 (Dec 3) release)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=433

commit 3b2c86c8ed77b04cda05b7cbd8e73f6d01db1bed
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Dec 6 16:38:06 2009 +0000

    removed every reference to BDB from configure.ac
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 343 (Placeholder bug for adding volgen into rpm, bdb makefile changes, etc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=343

commit 2bee3fb30bb05e5c6b9af9cbbe0b10deba0db790
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Sun Dec 6 13:51:03 2009 -0800

    Revert "performance/write-behind: Changed default value of option disable-till to 0"
    
    This reverts commit e6c35f74ff4a204cf016ebf201a2630b331f9434.
    
    This commit is found to trigger spurious self heal by causing flush and writev to get
    reordered. Reverting as a workaround.

commit c50bc71035d87b5df77f6331ced6229af5508a10
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Dec 6 14:29:04 2009 +0000

    fuse-bridge: set lk_owner to -1 for release forged flush.
    
    Server would interpret 0 as a sign of us getting disconnected.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 76d6f3fbe993dddd72540f461090803636fa2dc5
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Dec 6 14:27:57 2009 +0000

    fuse-bridge: make use of lock owner data in a protocol adherent way.
    
    No need for pid fallback, for those cases where we use it,
    it's always available.
    
    It appears conditionally in read/write/truncate (related to mandatory
    locking). There just get it for demonstrative purposes.
    
    Discard it from release, there locking data exists only as a
    portability hack, no use of it on Linux.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 33f3abffe4f0de929d3732a472ad3df766d575b7
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 13:48:43 2009 +0000

    resolver: handle resolutions of paths
    
    support a new type of resolution where only the path is sent from the
    client over the wire without inode/parent/generation numbers. this can
    happen when cluster translators could not look up inodes on a server
    and later when the server comes up applications issues operations on
    the inode without a lookup (since they could be cd'ed inside). In these
    cases the server makes the best attempt to resolve the path and perform
    the fop on it
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit f08a2073d58ffff8c5b358fbb05702377a251b87
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Sun Dec 6 11:34:07 2009 -0800

    Revert "protocol/client: return ENOENT if inode context is missing"
    
    This reverts commit 4439876a34f2e5d19db0d8b05ce7d7722c1c466f.
    
    This revert is necessary for path handle resolution to work over the
    protocol where client/server talk only with the path, without inode
    or parent inode and generation numbers

commit 9e38b5066d42d47f1011e1d1bc32ed9c41df57ec
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sun Dec 6 13:29:08 2009 +0000

    features/locks: Implement release xlator callback.
    
    This patch solves the lock bailout problem seen recently when autoconf tools were run. This is a workaround,
    where 'flock' locks are removed in pl_release, if an explicit UNLCK call does not come. The complete fix would
    be to allow 'fcntl' and 'flock' locks to operate in different domains.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 449 (Handle flock calls in a different domain from fcntl calls)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=449

commit fe37a56dd42294e26158a29c15a35aeb8cb38be2
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 13:06:18 2009 +0000

    distribute: more cases of st_dev setting
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 433 (Posix conformance test failed on 3.0.0pre2 (Dec 3) release)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=433

commit 72e82741b52fb749eb912f97848b707d97ec69ff
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 12:47:25 2009 +0000

    distribute: return st_dev from the same subvol from where itransform is performed
    
    distribute should return st_dev from the same subvolume it itransforms the inode
    number. this is to ensure that there will not be false replacements of inodes in
    inode management
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 433 (Posix conformance test failed on 3.0.0pre2 (Dec 3) release)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=433

commit 0117cf0d3dfeb49b739e0da84f429b5375fd922a
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 12:46:14 2009 +0000

    fuse-bridge: log cases where newer generation is found in table
    
    This is usually the case when there is a bug a cluster xlator and returns
    generation number from the wrong subvolume
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 433 (Posix conformance test failed on 3.0.0pre2 (Dec 3) release)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=433

commit b5ad85803b85ae83b2a1bcbe18c8b42265dc34dc
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sun Dec 6 10:50:18 2009 +0000

    features/locks: Disable mandatory locks, until we can use lock-owner field without problems in mandatory locking.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 21b06ce3e46c3125ee5f281b49f6fcc3a09c02e7
Author: Pavan Sondur <pavan@gluster.com>
Date:   Sun Dec 6 10:34:39 2009 +0000

    features/locks: Correct the order of arguments and print a log message in pl_flush.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit fdc187d11ead26710add3cd45dd5f306dad59900
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 07:42:30 2009 +0000

    protocol/server: more fixes in server_link_cbk
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 448 (server_link_cbk refers to @inode when op_ret is -1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=448

commit a53cd95827df0a9c560fdf5e07b0c23d03707b04
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 05:31:44 2009 +0000

    THIS: set THIS pointers before forget/release/releasedir callbacks
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ea93dd6397b79842c1d8e5189ff217201c002a8d
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 04:45:17 2009 +0000

    afr: fix fd ref leak in self-heal
    
    sh->healing_fd should be ref'ed only when healing_fd_opened is not set
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 7a3c372c7a8a3ad7d481f94a899fd4333d146634
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 04:44:59 2009 +0000

    libglusterfsclient: fix libgf_client_read to handle short reads
    
    Fixes two issues in the current code
    -short reads (reading larger than file size) result in failure of full read
    -reads which span multiple iterations return with the op_ret of only
       the last read
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 334 (glusterfs_read/readv should break large-reads into 128Kb block sizes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=334

commit 4235868f0ded7aeb157aef05f10d2df4a470a2c5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Dec 6 04:42:01 2009 +0000

    performance/stat-prefetch: remove the usage of THIS.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit bf23224e5dc2af09efd0888490f7af191052c874
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Dec 6 04:39:13 2009 +0000

    performance/stat-prefetch: fix memory leak.
    
    - rbt_hash_remove only removes entry from the hash table. It does not free
        the data.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 438 (Memory leak)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=438

commit 4d8c682181822834f46adaa6afea029556a0bb59
Author: Anand Avati <avati@gluster.com>
Date:   Sun Dec 6 04:41:02 2009 +0000

    protocol/server: fix bad reference to @inode in server_link_cbk
    
    when op_ret is -1, gf_log refers to @inode which can be NULL. fix
    this to refer to state->loc2.inode instead
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 448 (server_link_cbk refers to @inode when op_ret is -1)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=448

commit 9cedbb537f648a38606d14c425caa952dd5d0049
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Fri Dec 4 20:43:01 2009 +0000

    Fix critical argument validation bug found during initial testing.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 437 (Fix critical argument validation check on Fedora11 systems)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=437

commit a2d7ca2ee22de61bf43525e4a8a2928ce6dd8851
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Fri Dec 4 20:42:55 2009 +0000

    glusterfs-volgen honours now build level prefix.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 437 (Fix critical argument validation check on Fedora11 systems)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=437

commit b5da78348291435b2f711018c529c83dc824cff8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Dec 5 16:35:14 2009 +0000

    libglusterfsclient/chdir: assign op_ret the return value of libgf_client_chdir.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 446 (apache does not start in daemon mode on fedora core 11.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=446

commit 05140d5f3c84cde0f0a568a6deb000bb906174b2
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Dec 5 22:04:32 2009 +0000

    corrected the stripe's stat structure return logic.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 340 (Kernel Compilation fail in stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=340

commit 759d2ec189ce632022494baa478cc0d5256697e0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Dec 4 15:16:05 2009 +0000

    performance/stat-prefetch: don't check whether previous lookups have been failed in sp_process_inode_ctx.
    
    We need this patch for following reasons:
       1. The inode used in the successful lookup call may not be the one passed to
          fops operating on path. This may happen, if revalidate of inode is failed,
          but the lookup itself succeeds (in case of reavalidate failures, fuse
          sends a fresh lookup using new inode) and since inode_link, if there is an
          inode already associated with a path retains it.
       2. Only fops that "wait" in stat-prefetch for a lookup which is already in
          progress, need to check for the result of the lookup they are waiting on,
          before resuming and sp_process_inode_ctx is _not_ used in such contexts.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 428 (looks like stat cache not upto date..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=428

commit d281971e5061d4a339b31340798d6f1dbff348be
Author: Anand Avati <avati@gluster.com>
Date:   Sat Dec 5 06:03:04 2009 +0000

    fuse: fix leak in fuse_getxattr and fuse_getattr
    
    In fuse_getxattr, @finh was leaked in the case of posix ACL getxattr
    request
    
    In fuse_getattr, @state was leaked when fuse_loc_fill() failed
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 438 (Memory leak)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=438

commit 73ef824cbb8a468b70b57e503c98c226aed813a7
Author: Vikas Gorur <vikas@gluster.com>
Date:   Sat Dec 5 03:06:40 2009 +0000

    cluster/afr: Fix inode_ref's for local->cont.lookup.inode
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 3e86687e74bdf4847f3e35063dfb46e9871d6959
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Dec 4 21:27:15 2009 +0000

    fix crash in server protocol server-connection-destroy
    
    a variable allocated inside a condition was getting reffered outside
    the block. If the condition fails, there used to be a crash.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 439 (crash in server protocol, while destroying connection)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=439

commit 89bbaa124af8c54bb7ca8b85ad5d40f0bb754e49
Author: Anand Avati <avati@gluster.com>
Date:   Fri Dec 4 09:28:23 2009 +0000

    posix_rchecksum() - fix leak of read buffer
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 4439876a34f2e5d19db0d8b05ce7d7722c1c466f
Author: Anand Avati <avati@gluster.com>
Date:   Fri Dec 4 08:12:43 2009 +0000

    protocol/client: return ENOENT if inode context is missing
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit cba270e7dfe271dfa43cd7127089b91dfedf838f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Dec 4 06:04:37 2009 +0000

    mount/fuse: Refactored fuse_setattr.
    
    If both truncate & setattr need to be sent from fuse_setattr,
    they are now sent one after the other (setattr first, and then truncate)
    instead of being sent parallelly. The earlier code that sent them parallelly
    had a couple of problems:
    
    1) A bug in the logic that would sometimes cause the setattr call
       to never return, making the application hang.
    
    2) A possibility that truncate and setattr would race at the server/io-threads/posix
       end, thus returning the wrong stat structure to the application.
    
    This patch also removes an unneccessary "can_fuse_return" call in
    fuse_attr_cbk, which would cause a call to hang if STAT or FSTAT failed.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 05ad7717083057de819ad545591bffeb8af2f741
Author: Anand Avati <avati@gluster.com>
Date:   Fri Dec 4 04:52:33 2009 +0000

    afr: fix memory leaks
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 349f9b77178aac3d2823bb35b0dc6c40b7a3b876
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 3 21:47:23 2009 +0000

    performance/stat-prefetch: add "caller" arguement to sp_process_inode_ctx.
    
    - since sp_process_inode_ctx is called by many fops, if the context is not
        set "caller" argument can be logged in log msgs to identify caller.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 45494f35deb30b6e0410351bdea7cf10f8f83c04
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 3 21:47:11 2009 +0000

    performance/stat-prefetch: implement sp_check_and_create_inode_ctx.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 4db7a358a294e11568ef818e64d5b3f37176609b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 3 21:46:52 2009 +0000

    performance/stat-prefetch: refactor sp_lookup_cbk to use sp_update_inode_ctx.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 58535b168ca9d65a5c5018f89882d7c18d8f15fe
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 3 21:46:40 2009 +0000

    performance/stat-prefetch: dont check for inode context in fops like create, mkdir.
    
    - context will not be set as a fresh inode is passed in each of these calls.
        instead create a new context.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 290a38912ce9f942f4ebdd24fcb0033214ecc537
Author: Anand Avati <avati@gluster.com>
Date:   Fri Dec 4 03:50:47 2009 +0000

    protcol/server: server_connection_destroy - destroy frame after issuing flush
    
    frame was getting destroyed after unlocking, but before issuing flush. This
    could result in corruption if an fd was opened between server_connection_cleanup
    and server_connection_destroy because of pending open calls in io-threads at the
    time of POLLERR disconnection
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 430 (Server crash when client is killed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=430

commit e7b86dedcdde48e37a2d50370998d7285624bdb8
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Dec 2 18:18:35 2009 +0000

    features/locks: Process State Dump support for locks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit aa53bb583d2d01867a2db1d217001fc897e2b835
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Dec 3 16:10:17 2009 +0000

    fixing some warnings on 64bit machine.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 408 (warning while building on 64bit machine..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=408

commit cec1f78d42f49f35448d81c944afb9afae19c959
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Dec 3 16:10:16 2009 +0000

    features/locks: Fix inodelk leak when issued an UNLOCK.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit f4983bb29be027e40fcd379d0a018b87cf82fc85
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Dec 3 16:09:22 2009 +0000

    storage/posix: Fix Leak in posix_getxattr while filtering gen-number xattr.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 54046015d3c732b48304c9a5ecf7a7f8ff94c90e
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:12 2009 +0000

    mount/fuse: Print correct log message if encountered with errno - EAGAIN.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 26257254fb42c132ff2e0565655fdc382184d8af
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:11 2009 +0000

    features/locks: Release all locks of an fd when a client disconnects.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 120b446967ef33701a31d0da23324177922a3d73
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:10 2009 +0000

    features/locks: Changes in log messages reflecting lk-owner.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 83487d024bcfe671ef83752c8c3a8b56b8dcee2b
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:09 2009 +0000

    protocol/server: Changes in protocol client to include lk_owner in protocol header.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 687311adfd08f55de5f70cc89d69c5da0f37a80f
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:08 2009 +0000

    features/locks: Use owner field in inodelks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 31b18f256fa3972a0cebc51cc15127440321c4c4
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:07 2009 +0000

    features/locks: Use owner field for entrylks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit e0c09ea80904a26ac932eec546d7675fc0d2cd08
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:06 2009 +0000

    features/locks: Use lock_owner from fuse in posix locks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 1c8aa56a1bcff7640b65102782641ab0d53861d2
Author: Pavan Vilas Sondur <pavan@gluster.com>
Date:   Thu Dec 3 14:51:05 2009 +0000

    mount/fuse: Use fuse lock_owner field in posix locks.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 336 (Use lock owner field from fuse in locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

commit 4645dc9a0be85d64f0a19c4cc9cf8cdc24e24865
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Dec 3 08:11:36 2009 +0000

    mount/fuse: Handle the case when attribute_timeout is set to 0 in dictionary.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 252 (client coherence problem with locks and truncate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=252

commit 6922f156d65e7426b90f6ae5ebf0fc87f162554c
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Dec 3 08:10:57 2009 +0000

    glusterfsd: Handle argument attribute-timeout when set to 0
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 252 (client coherence problem with locks and truncate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=252

commit 3208d63c0ffd1735bc95c6986b2a3ddd96ba71d6
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Dec 3 05:37:05 2009 +0000

    core: Change replicate trash directory name to ".landfill".
    
    The earlier name ".trash" conflicts with the name used by
    the trash translator.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 227 (replicate selfheal does not remove directory with contents in it)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=227

commit 5821d2cf591789760e790d4af0575d1b9754c08d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Dec 3 05:15:09 2009 +0000

    core, client, server: Support auxiliary group ids
    
    Support for auxiliary group ids is needed for transmission
    of more than one group id right through the xlator tree
    so that posix can use these group ids to perform
    in-house permission tests. The in-house permission checks are
    needed so that we do not have to depend on non-POSIX calls
    like setfs[ug]id for changing the user for each fop.
    
    The setfs[ug]id  are also limited since they do not allow setting
    multiple group id as required for operation with NFS, which sends
    us all the group ids for a process issuing file system requests.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 400 (Support auxiliary gids in GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=400

commit 930f709881d85774baab1df57c2c03de93110bf7
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Dec 3 03:57:15 2009 +0000

    cluster/afr: Don't mark the fop as failed if rmdir returns ENOTEMPTY.
    
    Marking the fop as failed in the ENOTEMPTY case led to spurious
    entry self-heals.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 326 ([2.0.8rc9] Spurious self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

commit 2615d1a9558868b0b247375fc7560ea399390516
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Dec 3 03:43:12 2009 +0000

    libglusterfsclient: Separate order of path compaction and VMP search for abs and rel paths
    
    The previous set of changes for relative paths in libglusterfsclient
    break the absolute path operation. The fix involves differentiating
    between absolute and relative paths in terms of the order
    in which the 2 operations are performed:
    
    - path compaction
    - VMP search
    
    For absolute paths, since we assume that VMP is already perfixed to the
    path, we need the following order of operation:
    
    1. VMP search
    2. path compaction on the path components beyond the VMP.
    
    For relative paths, the operations are reversed because there
    we do not have a VMP pre-fixed in order to perform a VMP search.
    This means that a path compaction combined with prepending of the
    CWD is needed to get an absolute path before the VMP is searched for.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 0f73d6c94ce00eae317463fe32de40bb4225c820
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Dec 3 03:16:34 2009 +0000

    performance/stat-prefetch: don't access stat if lookup has been failed.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 429 (crash in lookup_cbk when lookup returns with error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=429

commit d666c882cf6896fb700a15bd72e53c675356f8fc
Author: Erick Tryzelaar <idadesub@users.sourceforge.net>
Date:   Wed Dec 2 17:32:05 2009 +0000

    Hopefully fix rpm building for everyone by rm-ing *.a and *.la
    
    My Fedora 11 machine doesn't seem to make the .a files, so it errors out,
    but it appears someone else's machine does, so try to fix it by explicitly
    removing the .a and .la files, rather than excluding them from the %files
    section.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 0cac194a149871999072e8573d7eccc4b4723e0c
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Dec 2 18:19:53 2009 +0000

    Disable fusermount by default in configure.ac.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 343 (Placeholder bug for adding volgen into rpm, bdb makefile changes, etc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=343

commit 29890d798167338c0aaa3a1bab26fe416ddadf19
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Dec 2 14:28:59 2009 +0000

    posix-compliance test now passes over stripe
    
    * needed to have ctime in the statbuffer from first subvolume.
    * unlink should be sent to all subvolumes no matter what.
      (earlier it was sent to all nodes only in case of regular files,
       causing directory not empty type of errors in 'rm -rf' cases)
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 321 (over distributed-stripe set-up, annihilate.sh fails.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=321

commit a3d5eb9b2a08190528b1e024bdfbff41c0a6b88f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Dec 2 14:17:18 2009 +0000

    storage/posix: Change janitor sleep duration to 10 minutes.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 227 (replicate selfheal does not remove directory with contents in it)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=227

commit be762405e773ac25054cd08ba7f5760389db3bdd
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Dec 2 14:02:44 2009 +0000

    cluster/afr: Don't do transactional flush if pre-op has been nowhere done.
    
    If a pre-op has not been done on any subvolume at all, there
    is no reason to make flush a transaction call.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 427 (flush on a file opened read-only should not hold locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=427

commit 9cc2207e2ffc23e88c23a95bb0783156a85b57c4
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Dec 2 13:29:34 2009 +0000

    storage/posix: Filter out generation number xattr.
    
    Don't return the generation number xattr "trusted.<volname>.gen"
    in getxattr, since this can cause replicate self-heal to copy
    it over to another subvolume.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit e6c35f74ff4a204cf016ebf201a2630b331f9434
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Dec 2 12:17:32 2009 +0000

    performance/write-behind: Changed default value of option disable-till to 0
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 425 (Change disable-till default to 0)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=425

commit 494db717941e90ae209d416e00bf2c63490ba75e
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Dec 2 08:34:25 2009 +0000

    features/locks: Release blocked locks also when server requests to release all locks of a 'transport'.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit 7d740b2c01224019525fda01235f56c3a4416747
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Dec 2 12:20:10 2009 +0000

    cluster/afr: Add log messages when setattr fails in self-heal.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 14c5492a2c03728f18a20125b785f43f441dbfd5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Dec 2 12:29:56 2009 +0000

    performance/stat-prefetch: get inode context from local->loc.inode instead of inode passed as arguement in sp_lookup_cbk.
    
    - @inode in sp_lookup_cbk may be NULL in case of failure of lookup.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 426 (stat on mount point hangs.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=426

commit 855a57a1f9c05d627c22f3091a7e0603d3e4092f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Dec 2 10:28:34 2009 +0000

    cluster/afr: Fix conditional typo.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit c04c1a170dcc605efcf80c8ae2674b69488b591d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Dec 2 07:48:45 2009 +0000

    storage/posix: Added janitor thread.
    
    The janitor thread deletes all files and directories in
    the "/" GF_REPLICATE_TRASH_DIR directory. This directory
    is used by replicate self-heal to dump files and
    directories it deletes.
    
    This is needed because letting replicate walk the directory
    tree and delete a directory and all its children is too racy.
    Instead, replicate self-heal only does an atomic rename(),
    and the janitor thread takes care of actually deleting them.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 227 (replicate selfheal does not remove directory with contents in it)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=227

commit 90328b827768552a05bb12abf62d09c9566309d1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Dec 2 01:00:44 2009 +0000

    performance/stat-prefetch: fix access to inode table.
    
    - Access the inode table from one of fd->inode->table, inode->table or
        parent->table instead of from root xlators itable.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 67d6a0a6195a72bce251891fccbd38929d5586dc
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Dec 1 20:28:28 2009 +0000

    fixes to compile on MacOSX (no fuse client)
    
    These changes are required to make GlusterFS compile on MacOSX (10.5).
    
    Currently glusterfs server component alone will work over Mac, and it has
    to be built with following options to ./configure.
    
     "bash$ ./configure --disable-fuse-client --disable-fusermount "
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 361 (GlusterFS 3.0 should work on Mac OS/X)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=361

commit 0c4b5814e7402658493f1e16ef7fa9a8fa8b4be5
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Nov 28 03:09:02 2009 +0000

    bring new MOP called NOTIFY.
    
    which can be used as a bridge between client and server processes,
    when needed.
    
    This mop is needed now, so that many features in 3.0.0 can come in
    with this without bumping protocol version.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 201 (server should get notified about client 'umount')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=201

commit 0a6b3ce3bf4acd994cb67c9c79b7c03909443bdd
Author: Anand Avati <avati@gluster.com>
Date:   Tue Dec 1 20:06:18 2009 +0000

    afr: remove memcpy of @local contents in afr_local_copy
    
    copy out members which are needed. memcpy of full local causes
    a copy of pointers without references and results in various corruption
    errors
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit dc16ba6f79726e9c42d2309947ad805978375b8c
Author: Anand Avati <avati@gluster.com>
Date:   Tue Dec 1 19:58:02 2009 +0000

    afr: fix fd reference leak
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 933e87700e25e83bcd5e9ba4c4f580d48fcaccee
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Dec 1 12:03:08 2009 +0000

    performance/io-cache: Hold locks on inode before creating rbt tree.
    
    Lock is held before creating a RBT in inode. Also, did some re-factoring.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit 6afe4faeaa77911490b2eca0830928367543e504
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Dec 1 14:39:45 2009 +0000

    libglusterfsclient/read: break reads bigger than the iobuffer size into smaller ones.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 334 (glusterfs_read/readv should break large-reads into 128Kb block sizes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=334

commit 435b234325bdcdcea88c3e1c7e9d97deeee3eb9a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Dec 1 14:39:31 2009 +0000

    libglusterfsclient/readv: break reads bigger than the iobuffer size into smaller ones.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 334 (glusterfs_read/readv should break large-reads into 128Kb block sizes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=334

commit b491da7cc5fdcebdf641c5768685061221643611
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Dec 1 14:46:21 2009 +0000

    extras/benchmarking: port glfs-bm.c to master.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 422 (port glfs-bm to latest code-base)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=422

commit 8d9b1a1987840b5ab254db0ffe47663641d9ae15
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Dec 1 14:51:15 2009 +0000

    changed the version of glusterfs from 2.1.0 to 3.0.0
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ade63327d7beaf6f8458aba9f8980e15016b6f31
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 30 01:20:20 2009 +0000

    trash_ftruncate fop added
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 142 (enhance features/trash  translator so it can work on client side too..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=142

commit 4f7886034742709b285499aa0052fdb21e9c42f6
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 30 01:19:10 2009 +0000

    trash_truncate fop added
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 142 (enhance features/trash  translator so it can work on client side too..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=142

commit 7bb52eb192f9541e70bf48a206c2d78b5dbb5cb2
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 30 01:18:41 2009 +0000

    trash_rename fop added
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 142 (enhance features/trash  translator so it can work on client side too..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=142

commit 056e3e7a56a24291c6f07b9ef572ee8c8ff7c700
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 30 01:18:09 2009 +0000

    trash_unlink fop added
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 142 (enhance features/trash  translator so it can work on client side too..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=142

commit 936001b147a3adcf9731d02e8f2fb62e5e50caf4
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Nov 30 01:16:35 2009 +0000

    features/trash initial cleanup commit
    
    * support O_TRUNC flag in open (call comes to FS as 'truncate'
      or 'ftruncate' fop)
    * option to provide 'eliminate-pattern' so those files matching
      won't be kept in trash. Eg:
          option eliminate-pattern *.out|*~
    * option to give 'maximum' file size to keep in trash, ie, when a
      20GB file is deleted, it won't be kept in trash if max file size
      given is 1GB. Eg:
          option max-trashable-file-size 1GB
    
    These particular features are developped as a part of college project
    by following team:
    
    Sunil bhagwath <sunilkbhagwat@gmail.com>
    Yashaswi Kumar <yashaswikumar@gmail.com>
    Rashmi B K     <rashmibk17@gmail.com>
    Sandeep M      <astrophyster@gmail.com>
    
    Submitting after minor coding standard edits and memoryleak fixes.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 142 (enhance features/trash  translator so it can work on client side too..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=142

commit 90cebe19380b4319e3a4345f31268563b51e08c3
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Nov 30 01:17:22 2009 +0000

    Booster configuration fixed for per transport type and honours conf-dir option.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 421 (Make booster configuration honour conf-dir and transport type)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=421

commit 85ed82893aca7dd6307100660b9bba0233d52240
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Dec 1 06:11:06 2009 +0000

    cluster/afr: Don't do memcpy of afr_local_t in afr_local_copy.
    
    For the background self-heal frame's local_t, copy only
    required members --- not a wholesale memcpy. The memcpy
    lead to pointers being copied and then double free'd.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit cc57da87504621655d4acb7ec65e27f45b2b72d1
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Dec 1 06:11:05 2009 +0000

    cluster/afr: Set file size properly before unwinding from self-heal.
    
    Set the buf.st_size of the original frame's afr_local_t, and
    not the copy_frame'd one.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit ab99355f55ce8a55d5c9b339ced830723be5f213
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Dec 1 06:11:04 2009 +0000

    cluster/afr: Set the self-heal "source" as read subvolume even when not doing self-heal.
    
    This patch sets the read-subvolume equal to the self-heal "source"
    even if we're not doing self-heal (because some one else is already
    doing it).
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit d2a30ec4aaeaa546f6370a1377c44574ada5edbc
Author: Anand Avati <avati@gluster.com>
Date:   Tue Dec 1 07:02:02 2009 +0000

    stat-prefetch: fix unsafe reference to @local in sp_lookup_cbk
    
    stat-prefetch uses the main syscall frame for performing lookup on
    demand. this causes a potential reference to a freed local in
    sp_lookup_cbk after resuming the main syscall frame (which could
    have unwound and destroyed)
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 242 (If any of the writes fail, write-behind should not wait till the fd is closed for reporting errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=242

commit d7e0bf1757e5fae23bce3d09cd0d9fbbd822a067
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 30 15:48:38 2009 +0000

    performance/stat-prefetch: make lookup to wait for the completion of another lookup on same path if one is in progress.
    
    - If current lookup (2) does not wait for completion of the lookup (1) which
        is in progress, there can be a race condition where (2) completes ahead of
        (1) and resuming all the waiting operations in the queue. When (1) returns,
        the original operation (eg., stat, chmod etc) might've already unwound and
        hence the frame would've been destroyed.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 47a8f97b729dd6bb2a2dabd3ed250ebbdf8be7fc
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 30 15:48:21 2009 +0000

    performance/stat-prefetch: don't use same variable for getting inode context of an inode and its parent.
    
    - this bug results in updation of flags in inode context of the parent
        instead of that of inode.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit cff970c45034f917a76182bc0a326d59f2cebd40
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 30 15:48:08 2009 +0000

    performance/stat-prefetch: fix errors in handling memory allocation failures in sp_inode_ctx_process.
    
    - the variables that are used for making decisions are assigned before
        memory allocations and these variables were not reset to
        correct values in case of memory allocation failures.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 2a3adcfe5c8d649a17b2d30f3715f26794dff6bb
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Nov 29 19:26:57 2009 +0000

    fix leaks pointed out by cppcheck static analyzer
    
    See http://cppcheck.sf.net
    
    [./build/libglusterfs/src/y.tab.c:2104]: (error) Memory leak: cmd
    [./libglusterfs/src/md5.c:306]: (error) Resource leak: f
    [./xlators/debug/io-stats/src/io-stats.c:1396]: (error) Possible null pointer dereference: this - otherwise it is redundant to check if this is null at line 1402
    [./xlators/cluster/stripe/src/stripe.c:3597]: (error) Memory leak: dup_str
    [./xlators/debug/trace/src/trace.c:2426]: (error) Possible null pointer dereference: this - otherwise it is redundant to check if this is null at line 2429
    
    These appear in rarely hit error cases or test/demo code so nothing
    serious, in fact.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 420 (fix leaks pointed out by cppcheck static analyzer)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=420

commit cc3967db49e5983f43530708c1eb4b2708546ad9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Nov 30 04:35:09 2009 +0000

    cluster/afr: Preserve generation number along with inode in lookup and creation fops.
    
    This fixes fuse_create_cbk conflict warnings and random errors while
    running dbench (typically open handle failure with ENOENT).
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit d21e0108638bdde5f46361aadb370061293c8146
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Nov 30 02:27:12 2009 +0000

    cluster/afr: Refactored lookup_cbk and introduce precedence of errors.
    
    Error handling in afr_lookup_cbk was faulty because it
    did not give priority to errors such as ESTALE over ENOENT,
    and ENOENT over other errors. This patch fixes that, and
    also breaks up afr_lookup_cbk into multiple logical functions.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 205 ([ glusterfs 2.0.6rc4 ] - Hard disk failure not handled correctly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=205

commit 357e464ffee8cbed84e0c34727b9226adbdb7bd2
Author: Anand Avati <avati@gluster.com>
Date:   Sun Nov 29 09:27:54 2009 +0000

    afr: fix crash in afr_sh_data_close
    
    when active_sink count is 0, the code proceeded into a dangerous loop
    resulting in a crash while issuing the call or in the callback
    afr_sh_data_setattr_cbk or afr_sh_data_flush_cbk
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 6c949d9d0ddc3397eac3207c0718743d49bd8707
Author: Anand Avati <avati@gluster.com>
Date:   Sun Nov 29 07:45:20 2009 +0000

    protocol/server: enhance trace logging
    
    add logging of fop name, callid number and make logging more friendly
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 77a7250b16c119e20c2d5c66a80b559455953a47
Author: Anand Avati <avati@gluster.com>
Date:   Sun Nov 29 07:37:32 2009 +0000

    afr: handle fdctx->pre_op_done handling
    
    reset pre_op_done[i] to 0 after issuing a postop in flush. this was
    missed during the introduction of pre_op_done[] array and was resulting
    in a lot of spurious self heals when spurious flushes were received
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 51600217be80dc9e1b1ad8bf20b7e5a95d31ec1c
Author: Anand Avati <avati@gluster.com>
Date:   Sat Nov 28 05:34:41 2009 +0000

    afr: fix logic to break out of diff/checksum loop
    
    When checksum fop returns error, mark for terminating the loop at the end
    of the iteration (when all checksum calls of that iteration return) and
    not immediately
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 1ec37aa78fccb45aa701a3380f6acf95819c7a39
Author: Anand Avati <avati@gluster.com>
Date:   Sat Nov 28 05:34:11 2009 +0000

    protocol/server: fix improper validation of fd in server_rchecksum
    
    state->fd validation should be done _after_ resolve_and_resume()
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 915299aff39c993fbe21e68e9458100db519535e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Nov 28 11:04:19 2009 +0000

    performance/quick-read: add options to doc/translator-options.txt.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 419 (Issues with writing files of size >= 1MB)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=419

commit 79243bfdeeb328126d30da22fd48756a1bf65dd3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sat Nov 28 10:52:37 2009 +0000

    performance/quick-read: change the maximum value of max-file-size to 1000KB from 1MB.
    
    - protocol restricts the maximum buffer size that can be received over network
        to 1MB. Since the buffer holding reply of lookup should also contain the
        lookup header and other key/value pairs of xattr_reply dict, the maximum
        file size that can be fetched through dictionary cannot be equal to 1MB.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 419 (Issues with writing files of size >= 1MB)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=419

commit 04da2ae78b83e1cb3e14379dd72d694fa03fc5e1
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Nov 26 15:47:28 2009 +0000

    Excluding static libraries.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 413 (rpmbuild fails with unpackaged files)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=413

commit 4b363f1c968e7b9d2c339ea8e30dac5ca935da0e
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Nov 26 15:42:26 2009 +0000

    Removed deprecated export_dir in print string.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 412 (Remove deprecated export_dir in print string)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=412

commit 07d5b01960a8fc7754d1957451210fff2ed4617e
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 26 14:55:03 2009 +0000

    moved unify from 'cluster/unify' to 'legacy/cluster/unify'
    
    maintaining unify is not feasible, and its design of namespace is
    not scalable too. hence moving it to 'legacy/' directory..
    
    Thanks to unify, we learnt something about rename(). 'cluster/unify' has
    served GlusterFS well for more than 2years, and its the time to say
    goodbye :-(
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ff9944ff7910441a1f8b9784c153d5de5be62142
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Nov 26 13:36:34 2009 +0000

    performance/stat-prefetch: Changed rbthash to make use of 1 bucket
    
    rbthash makes use of 1 bucket and a common mem-pool is being used for all rbt entries.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 03949adaf0c7fcfe10f31a802723613b357ec191
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Nov 26 12:08:44 2009 +0000

    Volgen rewritten using option parser and added proper support for booster.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 411 (Rewrite volgen using option parser and extend cifs/nfs support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=411

commit 9b2159c6111cff889c543fdaf7628fce03e50154
Author: Anand Avati <avati@gluster.com>
Date:   Thu Nov 26 07:22:08 2009 +0000

    THIS: transport to use xlator_notify() for proper setting of @THIS
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit bf34a8714e6ab9dce0670c2648f839165904f2f7
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Nov 26 07:51:26 2009 +0000

    protocol/server: Introduce option trace to log requests and replies in normal log.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit e91b3c49e3ab8787513764dfdadf503bc9a5da1f
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Nov 26 07:50:49 2009 +0000

    protocol/server: Get all fops to use the new 'resolve_and_resume' path in server/protocol.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 63f963700f0c89292092047ec2423e8d8ab1f955
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Nov 26 06:37:30 2009 +0000

    Changed rbthash_table_init() to take a mem-pool argument.
    
    Changes in libglusterfs/rbthash:
    
    rbthash_table_init() now takes a mem-pool argument.
    The mem-pool argument would be mutually exclusive to expected_entries.
    If expected_entries is provided, mem-pool would be ignored and vice-versa.
    
    Changes in io-cache:
    1) Moved rbthash creation to readv.
    2) rbthash makes use of 1 rbt instead of 4096
    3) A global mem-pool is being used in place of a mem-pool per rbt.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit a928aa5e0d65b9439b8a10eb9dede954220ba9f3
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Nov 25 21:29:25 2009 +0000

    fixes in nufa
    
    Now nufa uses dht_conf->private variable to store its
    contents, and doesn't pollute distribute's structures.
    
    It used to hang earlier as layout_lock was not INIT()'d.
    
    whitespace-cleanup done on the code too.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 409 (implement a switch scheduler)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=409

commit fc87b19f0bd511ee294c058ea9066189ca06ce88
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Nov 25 21:26:24 2009 +0000

    switch translator added
    
    switch translator is a wrapper around distribute to work for a
    pattern based scheduling.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 409 (implement a switch scheduler)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=409

commit 057c071403eb808b065e760d91101d519f86b65c
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Wed Nov 25 14:40:55 2009 +0000

    Volgen supporting multidisks and booster configuration for nfs and cifs
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 396 (Volgen multiple export directory support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=396

commit 3429e8755756191d010896083ca9a7141682ead9
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Nov 25 15:13:37 2009 +0000

    add an extra check for loc->parent when loc->ino is not 1
    
    This extra check is needed only in case where setup is
    "server -> chain -> client", where for the root inode, inode->ino
    is not updated in the first lookup call, hence used to crash.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 377 (segfault in protocol/client with chaining)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=377

commit 28e2901806d35055ca58470bf26d72edb803ba01
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Nov 26 04:16:27 2009 +0000

    Fixed typo in gf_proc_dump for attribute_timeout.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 410 (Typo in gf_proc_dump for attribute_timeout)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=410

commit b80fac541701689b07940be518431bacb101f09f
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 26 03:29:46 2009 +0000

    don't allow stripe with just one subvolume
    
    stripe code assumes in many places that it will have more than one subvolume,
    but the strict check was not there in init, hence, if somebody configures stripe
    with just one subvolume, it will cause many fops with frame loss.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 340 (Kernel Compilation fail in stripe)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=340

commit d1f3cdc4dcae63b1bb8e6fd6ff0db791646e2ad2
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Nov 26 00:53:49 2009 +0000

    protocol/server: Changed logging level of message on deep resolution
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 61a73726a51936fb59245a0ba9511c4907306130
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 26 00:38:28 2009 +0000

    changed the log level of failure case in client_setvolume_cbk
    
    It *should* be an error when a handshake fails. Its hard to debug
    it otherwise
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 26 (Version mismatch not handled correctly)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=26

commit 25c220cf505c71139afe0cefe5a04b7e435f77ba
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Wed Nov 25 13:15:36 2009 +0000

    Added boundaries for each fops, mops and cbks.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 366 (Infinite loop with centralized logging.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=366

commit 2517ec18aeae5d6952aace778dacdd1cde93efe0
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 10:08:54 2009 +0000

    cluster/afr: Include "common-utils.h" instead of alloca.h
    
    alloca.h should be included on a platform-specific basis.
    Lets common-utils.h handle that.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 349 (FreeBSD compilation error (alloca.h).)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=349

commit 1c6a55b04c418106cf2be5156fa8e53b1adaa1b4
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Nov 25 02:19:31 2009 +0000

    protocol/client: Make log message print both generation number and inode number.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 1bcb009cf65e57117653bbbb5cdf673f9d9142e9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Nov 25 07:51:23 2009 +0000

    cluster/afr: Do self-heal on unopened fds.
    
    This patch completes the previous patch for self-heal of
    open fds in replicate.
    
    If an fd was never opened on a subvolume, we remember that
    and do the open after we've done self-heal on that fd.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 9806bd1f58d80d158e3cfb6edee40e92ee30c6d7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Nov 24 20:47:00 2009 +0000

    performance/stat-prefetch: Add refcounting to cache objects
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 405 (Segmentation fault in stat-prefetch.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=405

commit ca4c8115a839568405e1dea2f4bda01f43357921
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Nov 24 20:46:48 2009 +0000

    performance/stat-prefetch: remove lock member in sp_fd_ctx_t.
    
    - since the lifetime of fd context can be no longer than the fd, we can use
        lock in fd.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 405 (Segmentation fault in stat-prefetch.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=405

commit 81af21adec38eb04de19694af1b3ce8a1a095ab7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Nov 24 20:46:34 2009 +0000

    performance/stat-prefetch: don't free the cache in readdir if the offset is not the expected one.
    
    - cache creation is expensive operation. Also, cache will be freed in
        releasedir. Hence, just remove all entries from cache without freeing
        the cache. However this is not entirely true, since sp_cache_remove_entry
        frees the old table and reinitializes a new table if all entries are being
        removed. When rbtree based hash table provides an interface to remove all
        the entries, sp_cache_remove_entry should be modified not to destroy the
        table.
    
      - this patch also fixes a race condition wherein the cache being used in
        lookup getting freed in readdir if the offset is not equal to expected
        offset.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 405 (Segmentation fault in stat-prefetch.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=405

commit 250edc9e494fe0c59eff580df18080111ecb475e
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 08:45:10 2009 +0000

    cluster/afr: Refactored the self-heal interface.
    
    Cleaned up the self-heal interface to callers.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 74612a456ad1602f8038fae79fee654eb427602a
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 08:45:09 2009 +0000

    cluster/afr: Do self-heal on reopened fds.
    
    This patch brings in partial support for self-heal of open
    fds. The precondition is that the fd should have been opened
    successfully during the initial open() (or create()), and we
    assume that protocol/client has successfully reopened the fd
    when the subvolume comes back up.
    
    It works by doing an "up/down flush" (a dummy flush transaction
    to do post-op wherever necessary) and then triggering
    data self-heal on the file in the post-post-op hook of the
    dummy flush transaction. This ensures that any writes
    that come in during self-heal will wait until self-heal completes.
    
    The up/down flush is also done when a subvolume goes down,
    so that post-op is done on all subvolumes where pre-op was done.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 218959e0597b16755a98b19786ed6a42cd15cbc4
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 08:45:08 2009 +0000

    cluster/afr: Provide a post-post_op hook in the transaction.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 9e3fddb13769288ddc13db3125b8bedf26058cdf
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 08:45:07 2009 +0000

    cluster/afr: Refactored the data self-heal algorithm.
    
    Refactored the operation of the data self-heal algorithm
    as:
    
    * open all fd's (if fd not supplied by caller)
    * lock 0-0 (if lock not supplied by caller)
    * fxattrop, fstat (instead of lookup)
       ... self heal ...
    * unlock (if lock not supplied by caller)
    * close (if fd not supplied by caller).
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 21cffbc219efc36229002e71a02b9270cfee9186
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 08:45:06 2009 +0000

    cluster/afr: Hold blocking locks for data self-heal.
    
    Data self-heal now holds blocking locks, and instead of locking
    on all subvolumes, it only locks on {data-lock-server-count} subvolumes.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit a63e189822a777b450eeaeda8622cdb0e5e7cb1d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 08:45:05 2009 +0000

    cluster/afr: Set read-child = source regardless of foreground/background self-heal
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 3fe840d93730f1f7feef053e58dfbc40f99cae04
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 07:41:36 2009 +0000

    cluster/afr: Fix inode context bitmasks.
    
    Set opendir_done and split_brain flags correctly
    in the inode context.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 249 (Self heal of a file that does not exist on the first subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

commit 4a43031ce0f045b673a50159dce5316bcae825ee
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 06:07:16 2009 +0000

    cluster/afr: Fix double-free in opendir self-heal callback.
    
    local->cont.opendir.checksum was being free'd both in the
    self-heal completion function and self-heal unwind.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 249 (Self heal of a file that does not exist on the first subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

commit 6adfd865588bdcf5ea67e8bde61dce131d18108c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 23 18:57:40 2009 +0000

    performance/quick-read: use STACK_UNWIND_STRICT for unwinding.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit fe34bb798cbadc964447ad2fd60a870dc2891572
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 23 18:57:33 2009 +0000

    performance/write-behind: use STACK_UNWIND_STRICT for unwinding.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 9aed8cd65940f99c9cdf647414d932750d2caf2d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 23 18:57:27 2009 +0000

    performance/read-ahead: use STACK_UNWIND_STRICT for unwinding.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit afdc2c956912d8b01db414fceacd74d9c3ab3dbe
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 23 18:57:21 2009 +0000

    performance/io-threads: use STACK_UNWIND_STRICT for unwinding.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 8b8205c2be7ea70b9eaab8da3cec5ec7e830c516
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 23 18:57:13 2009 +0000

    performance/io-cache: use STACK_UNWIND_STRICT for unwinding.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 54188f9d8878b2a961050e001658f35e163caebc
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Nov 23 18:56:22 2009 +0000

    performance/stat-prefetch: use STACK_UNWIND_STRICT for unwinding.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 7c6bc261e7d60bb1c4103c2e2e64a8ab89aa66e9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Oct 14 14:07:51 2009 +0000

    cluster/afr: Unlock only those paths which have been locked during rename.
    
    For ENTRY_RENAME_TRANSACTIONs, keep track separately whether the
    lower_path and the higher_path have been locked, and unlock only
    those which have been.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

commit 1cd2e389020b8713d45dce44df9f473622109b0d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 24 04:46:35 2009 +0000

    cluster/afr: Fix handling of revalidate lookups.
    
    This patch does two things related to revalidate:
    
    1) If a revalidate fails on any subvolume, the entire lookup
       call is failed.
    
    2) Self-heal is not triggered on a revalidate if revalidate
       has failed on any subvolume.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 389 (auto-heal fails randomly and causes "Stale NFS file handle" errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=389

commit 5b483cb62f00faa66e8795e24856600b961c8d4a
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Tue Nov 24 03:40:53 2009 -0800

    Revert "libglusterfs/src/gf-dirent.c: In gf_dirent_nb structure d_name should be char array of size 1."
    
    This reverts commit e151ab3ed4718606767146f18b416f8900552fbc.

commit 40dfc3e78b590af907caa8a4461730284648034c
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Nov 20 07:35:45 2009 +0000

    storage/posix: Fix condition typo.
    
    Do comparision instead of assignment in if-condition
    in posix_link.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 254 (storage/posix has to do inode number transformation wherever it unwinds with a stat structure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=254

commit 96ac4559414035288fa18e72a21628ea3cdf6a4c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Nov 19 17:28:00 2009 +0000

    performance/io-cache: don't use stat got in read_cbk if it is zero-filled.
    
    - translators like io-cache, read-ahead return a zero-filled stbuf in
        readv_cbk and usage of zero filled stat for cache validation is not
        correct.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 376 (server-side io-cache is preventing client-side io-cache from working)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=376

commit 83598e6015d76e2bebd0a3ad5141801a2864af1c
Author: Paul Rawson <plrca2@gmail.com>
Date:   Tue Nov 17 00:13:24 2009 +0000

    Fix Redhat init file so that it knows the correct binary location
    
    Signed-off-by: Paul Rawson <plrca2@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 388 (Redhat initfile fix)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=388

commit 9503af54284e27104051cc7eafffd3f138c28851
Author: Erick Tryzelaar <idadesub@users.sourceforge.net>
Date:   Mon Nov 16 13:27:30 2009 +0000

    Fix rpm building for Fedora 11.
    
    I was running into a problem compiling glusterfs on Fedora 11, rpmbuild was
    complaining that it couldn't find any .a files. Since it doesn't look like
    gluster's creating archive libraries anymore, I removed this line from the
    spec file, and gluster started to compile again.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 717faf468fcac827d00c81c76ac53057c43e28fa
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 15:07:22 2009 +0000

    transport/ib-verbs: assign to qpreg before accessing it in __ib_verbs_lookup_peer.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 381 (glusterfs crash in ib-verbs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=381

commit 68a9546e5ce01e6fefc8ae97d5d7e27da1f6d52a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 00:29:17 2009 +0000

    performance/stat-prefetch: don't cache dentries corresponding to directory.
    
    - distribute picks up the inode number from hashed subvolume. But readdir
        is done from different subvolumes based on the offset. Hence there is a
        possibility of inode number and device number for directories being
        inconsistent between two stat calls.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 371 (rm -rf fails on stat-prefetch.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=371

commit d14d014782dd4d7023f99a054d0c4db37d020435
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 00:29:05 2009 +0000

    performance/stat-prefetch: don't use pre-allocated dirent structure in sp_get_cache_entry.
    
    - since we don't know the size of dentry before calling sp_get_cache_entry,
        we must dynamically allocate the dentry in sp_cache_get_entry and copy the
        contents from cache.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 371 (rm -rf fails on stat-prefetch.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=371

commit 892710a37abcb10fdcff395a4369efce2af4c63f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 00:28:49 2009 +0000

    cluster/distribute: copy the stat structure while copying dentries in readdirp_cbk.
    
    - only the transformed inode number was being copied, leaving other fields of
        stat 0.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 371 (rm -rf fails on stat-prefetch.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=371

commit dd216deb8a9e281ec41867c354efb0067cde4785
Author: vinayak hegde <vinayak@gluster.com>
Date:   Thu Nov 19 01:39:39 2009 +0000

    debug/error-gen: Correct log messages in init function.
    
    Signed-off-by: Vinayak Hegde <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 291 (feature enhancement of error-gen translator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=291

commit 6148894110fd83d020e92b49b9b6f2532d7c7a99
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Nov 18 01:11:11 2009 +0000

    Check for other return values as well from call to inode_path.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 7a5325d284a850f4a18de8795f88e45816bfaf4f
Author: vinayak hegde <vinayak@gluster.com>
Date:   Tue Nov 17 06:17:04 2009 +0000

    cluster/stripe: Wrong variable is checked after calloc.
    
    Signed-off-by: Vinayak Hegde <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 368 (setattr on a non-regular file makes glusterfs crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=368

commit 5cd0d1c7447c6947e81c659635a472a97d41303d
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Nov 16 13:08:31 2009 +0000

    protocol/client: Changed default ping-timeout to 42
    
    This change is necessary to avoid frequent disconnections between client and server under load.
    A disconnect-connect sequence is costly in terms of clean up and re-building of context,
    self-heals etc. This value should be optimal for most use cases. Users requiring a lower
    ping-timeout value need to configure it explicitly.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 384 (Increase default timeout in client protocol)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=384

commit 916ca4d87c410c075a622fc24848ba06868c280a
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Nov 17 05:24:03 2009 +0000

    Do not access a free'd lock while releasing all inodelks of transport.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit 7a6b1de614c6db02eeb437c06fd2568ccea7d34e
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Nov 18 07:02:25 2009 +0000

    cluster/afr: Handle op_ret properly in opendir_cbk
    
    Change the success condition to op_ret >= 0 instead
    of op_ret == 0.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 249 (Self heal of a file that does not exist on the first subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

commit 71d6a1c8aaa82780bdf4191732216ac1f5c57e65
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:20:41 2009 +0000

    libglusterfsclient/umount: fix double free.
    
    - calling glusterfs_fini results in double free.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 9d9cbb893661763783f2e4fb8093ff7f0a720143
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:20:30 2009 +0000

    libglusterfsclient: don't change the st_dev in stat-structure before doing inode_link.
    
    - st_dev is used for storing generation number of the inode in
        inode_link and libgf_iattr_transform changes the st_dev to fake_fsid.
        If inode_link is done after libgf_iattr_transform, the generation number
        stored will be wrong and will result in ESTALE errors from server.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit ed75d6588899b3a812818e82ac7805998dbbd5e0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:20:15 2009 +0000

    libglusterfsclient/open: don't send create call if the file is already present, instead send open.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 80f89493ce2d78095a2df64e48c7bd7291b4558d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:20:02 2009 +0000

    protocol/server: add debug messages.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 9e481a7aee95cc7aebba8843820069909f21fe07
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:19:50 2009 +0000

    libglusterfsclient: update iattr cache only if operation was successful.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 2bf35da812016c8adb05b0aa90c9f0b25e50a878
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:19:37 2009 +0000

    libglusterfsclient: fix memory leak.
    
    - glusterfs_glh_getxattr was implemented using libgf_client_lookup. Hence the
        inode corresponding to the path on which getxattr was done was refed twice
        - one during path_lookup and the other in libgf_client_lookup - but unrefed
        only once.
      - with inode generation number changes the inode returned by inode_link may
        not be the same as the input argument. Hence the inode returned by
        inode_link should be used, not the one returned in libgf_client_lookup_cbk.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 64a4b1f78ee719f33928f4de9abac2a09ce84f21
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:19:22 2009 +0000

    booster: implement xattr related apis.
    
    - implement setxattr, fsetxattr, lsetxattr.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 95d31d089ed8e8a1bb90377160ac0bccdd47b6c0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:17:49 2009 +0000

    libglusterfsclient: change the prototype of glusterfs_lsetxattr.
    
    - it no longer needs handle to be passed as arguement. handle is searched
        in the vmp table based on the path.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 8d22d68815fbd27e7ef1b4b2f5bb70c3d82ddb96
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:17:36 2009 +0000

    libglusterfsclient: fix __do_path_resolve to return zero if the path happens to be resolved in path_to_parenti.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 134d85015b0251ddc079678e1e0997cb41d0516b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:17:25 2009 +0000

    libglusterfsclient: getxattr should return the length of the xattr when size is zero
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 1f1d1569f4bcd8acbfb80e0bdd11b752cdead637
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:17:14 2009 +0000

    libglusterfsclient/ftruncate: add braces to ensure proper evaluation of if conditional.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 6b65a11e4e1e351a85cddd86f18b320addec49fb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:16:57 2009 +0000

    booster: implement creat64.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 1e401ee2a94091154d114c11b55853bda3f49e29
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:16:45 2009 +0000

    booster: implement truncate and truncate64.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 9c5547193f637cb52cbb91c0409dd3580acafdcb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:16:33 2009 +0000

    libglusterfsclient: implement glusterfs_truncate.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit a0c05848d2ed0b0600d73214594a161cbb42302c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:16:12 2009 +0000

    booster: implement ftruncate64.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit a33380068a9ab9eea80a6d0b6207d9e3cc9bdff4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:16:01 2009 +0000

    libglusterfsclient: fix libgf_vmp_virtual_path. - This procedure used to return garbage as virtual path if the path happens to be exact mount point but without the trailing slash and the vmp had a trailing slash.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit eb4043706c901f8609e65c9a35463ea3f7e2c569
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:15:46 2009 +0000

    booster: implement getcwd.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit c7dba5ff1468f5e56d22b47cc97ff6cd4937f98f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:15:30 2009 +0000

    booster: implement fchdir.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 119b179fdc83d49e8242a93439fb043990eb74c9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:15:11 2009 +0000

    booster: implement chdir.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 3940cf2fc26ed0d2417caef87ff25d17ec8d3bb4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:14:58 2009 +0000

    libglusterfsclient: implement glusterfs_getcwd.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 7894bef2174945af06dceb506d501b8e789342fd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:14:42 2009 +0000

    libglusterfsclient: implement glusterfs_fchdir.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit d779e00360e7a30d721b3c2d8d94d198e5aa2cc0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:14:24 2009 +0000

    libglusterfsclient: implement glusterfs_chdir.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 43ffa430d64117e8864d38cf19202369d4809c6d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:14:04 2009 +0000

    libglusterfsclient: Support relative paths.
    
    - This patch is a port of the patch with same title on 2.0 branch.
        The original patch was sent by Shehjar <shehjart@gluster.com>.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 8cf1cd070e794f18ed5ec28d5a3cb758fa8bf0f2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 18 01:13:38 2009 +0000

    Revert "booster, libglusterfsclient: Support samba specific relative paths"
    
    This reverts commit e6fc0cbe716a18f02891d3911481fdcb121d8840.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 369 (Samba does not work with booster.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=369

commit 8f0ec7204d4b79dfb9fcf5f61df6275f6d4896fb
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Nov 18 05:20:08 2009 +0000

    libglusterfs: Fix error handling in _gf_log.
    
    Unlock the mutex when an error occurs instead of jumping
    straight to "out".
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 394 (Possible deadlock in _gf_log)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=394

commit 4b233c6341134d11b170fa4cdbafc49246b46975
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Nov 16 02:59:04 2009 +0000

    Upgrade FUSE protocol to rev. 7.13
    
    2.6.32 will feature FUSE proto 7.13 which lets us tune the maximal number of
    in-kernel backgrounded requests via INIT.
    
    Hereby we live up to this enhancement.
    
    Signed-off-by: Csaba Henk <csaba@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 385 (Upgrade FUSE protocol to rev. 7.13)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=385

commit 0c7597a1339f1a6762505cfe7292202a0db196a6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Nov 13 16:08:15 2009 +0000

    transport/ib-verbs: fix race-condition resulting in freeing of transport while it was still being used.
    
    - while handling a failed work completion status, the transport is
        disconnected. But further down in the code, the transport is still
        used. There can be a possibility that transport might've been freed
        by the time control reaches this point. More detailed description of
        events leading to this situation can be found at
        http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=381
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 381 (glusterfs crash in ib-verbs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=381

commit d67322fdfa27746f82fb6e37ffe57efde9bfa021
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Nov 13 16:07:50 2009 +0000

    transport/ib-verbs: synchronize ib_verbs_recv_completion_proc with ib_verbs_receive so that the former doesn't overwrite the pointer from which latter reads.
    
    - There can be a condition wherein,
        1. the thread executing ib_verbs_recv_completion_proc (thr 1) stores the
           buffer pointer and notifies the upper translators about a POLLIN event.
        2. the thread waiting for events on socket (thr 2) calls transport_receive,
           but in ib_verbs_receive it has not still read the data.
        3. thr 1 receives work completion event for another work request and
           overwrites the buffer pointer.
        4. thr 2 reads from the new pointer there by missing the data stored in
           buffer pointed by pointer which got overwritten.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 382 (Data can be lost before it is read in ib_verbs_receive.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=382

commit 63e966d8c466599f84affb55fbedfb39e2a0068f
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Nov 15 21:39:20 2009 +0000

    fixing a crash in posix (on 32bit)
    
    fd_ctx_get () was getting passed with type punned argument, now
    corrected by passing the right argument, and doing the typecasting
    later
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 383 (glusterfs server crash on 2.0.8)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=383

commit 91f8b2a1668a4c63e0c21df4f7ac6dfb506f79d7
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Nov 13 14:00:40 2009 +0000

    fixes in stripe
    
    * fix in stripe readv, so that a read request which falls in
      two (or more) subvolumes, depending on stripe-size works fine.
    * fix in stripe_setattr_cbk, where 'postop' stat structure was
      returning wrong 'st_size'.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 368 (setattr on a non-regular file makes glusterfs crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=368

commit 3c6647577f81568b7ad5cbf7435ef98aaa79e00a
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Nov 13 13:13:09 2009 +0000

    mount/fuse: Assign the right inode to fuse_entry_out in fuse_create_cbk().
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 380 ([3.0.0 pre1] Crash in fuse_create_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=380

commit 5c9a8a92edbd011e4fd5ec8e5f77eb13d7d8b771
Author: Anand Avati <avati@gluster.com>
Date:   Fri Nov 13 07:53:06 2009 +0000

    protocol/client: preserve open/create flags in fdctx for reopening
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 410909f31704db212174dff874f71621c3cb0576
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Nov 12 04:06:04 2009 +0000

    Disabled centralized logging by default.
    
    Signed-off-by: Harshavardhana <harsha@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 366 (Infinite loop with centralized logging.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=366

commit adebbb2ba19e52b194a4050c2e43a6c92f19c605
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Nov 11 14:26:10 2009 +0000

    performance/quick-read: set return value to zero after successful init.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 374 (quick read fails to initialize if no options are given)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=374

commit 0486b355db0c014f49662ed593a7ab7e74c2cb59
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Nov 12 03:23:27 2009 +0000

    mount/fuse: Prevent a hang on the mount point if no server is up when the client is started.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 373 (Spawn fuse thread after a parent_up and wait and block until child_up)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=373

commit 2e7fc582cd590f747b0d3cae3d38bbbccffe6a25
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Nov 12 06:27:05 2009 +0000

    extras/glusterfs-volgen: Make the script more user-friendly.
    
    Error messages now print more detail.
    Details of export/mount files written is also printed.
    
    Also adds a new option '--version'.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 343 (Placeholder bug for adding volgen into rpm, bdb makefile changes, etc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=343

commit 53fd5927ea0dc2f7c9cd019002abdc3751135dcd
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Nov 12 08:40:37 2009 +0000

    cluster/afr: Fix self-heal loop driver termination logic.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 26fbaa23cafee4643b7604660762656c4a71684b
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Nov 12 08:44:16 2009 +0000

    cluster/afr: Ensure directory contents are in sync during opendir.
    
    The problem: If some files on the first subvolume disappeared
    without leaving a trace in the entry changelog (this can happen,
    for example, when an fsck has deleted files or when a hard drive
    is replaced), those files would never be self-healed even though
    they would be present on the second subvolume. This is because
    readdir is sent only to the first subvolume, and since the files
    don't appear in the directory listing, no lookup would ever be
    sent on them.
    
    This patch fixes this problem by doing a readdir on all the subvolumes
    during the first opendir on a directory inode. If a discrepancy in the
    contents is detected, entry self-heal in a special "force merge" mode
    is triggered on that directory.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 249 (Self heal of a file that does not exist on the first subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

commit 4717e5279e169a36a870a267039e788cf22602a8
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Nov 12 08:44:15 2009 +0000

    cluster/afr: Refactored inode context bitmasks.
    
    Defined symbolic constants for the bit masks and
    made 'split-brain' a single bit field in the ctx.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 249 (Self heal of a file that does not exist on the first subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

commit b526009f2f5ad813ec88602a3d4fd2ff322809a0
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Nov 12 08:44:14 2009 +0000

    mount/fuse: Do readdirp in fuse_readdir.
    
    Do the readdirp FOP in fuse_readdir. This is needed because
    dht_readdir is not "reliable", whereas dht_readdirp is.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 249 (Self heal of a file that does not exist on the first subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

commit 84a50d45b4502d7efb842b41560f4ae5d62e3d78
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Nov 12 08:44:13 2009 +0000

    cluster/dht: Do readdir in dht_readdir instead of readdirp
    
    The readdir call will not be used by applications (fuse will
    only ever send readdirp), but it will be used by
    afr to do directory self-heal at the time of opendir.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 249 (Self heal of a file that does not exist on the first subvolume)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=249

commit 18d85b59b9e8cc422c06e3ea94694d0cb2d26e1b
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Nov 12 19:48:54 2009 +0000

    fix a crash in debug/trace
    
    stat structure (which is an argument to function) was getting freed
    instead of string which actually should have freed.
    
    Signed-off-by: Amar Tumballi <amar@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 378 (trace segfault in trace_create_cbk)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=378

commit f9bb9dee5f92d50c4e87995680198e488a4f50ce
Author: Anand Avati <avati@gluster.com>
Date:   Fri Nov 13 02:58:58 2009 +0000

    protoocl/client: file directory reopen support
    
    reopen files and directories which were open before a disconnection after
    reconnecting. operations on files/directories which could not be opened
    continue to return EBADFD
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 590e5879f819018aee63b800b0f66fd6ff49641d
Author: Anand Avati <avati@gluster.com>
Date:   Fri Nov 13 02:58:25 2009 +0000

    protocol/client: whitespace cleanup
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 170 (Auto-heal fails on files that are open()-ed/mmap()-ed)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=170

commit 63ece0f8bc81c2ec145465ff132a18ca47e50be5
Author: vinayak hegde <vinayak@gluster.com>
Date:   Wed Nov 11 22:52:01 2009 +0000

    cluster/stripe: Initialize frame->local before checking for directory or regular files.
    
    Signed-off-by: Vinayak Hegde <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 368 (setattr on a non-regular file makes glusterfs crash)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=368

commit 15a6e0be9bc1c56bd2a0a67c926b01f2f8631ae4
Author: vinayak hegde <vinayak@gluster.com>
Date:   Wed Nov 11 07:13:06 2009 +0000

    cluster/stripe: Set local->inode value before referring it.
    
    Signed-off-by: Vinayak Hegde <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 362 (GlusterFS crash while doing mkdir in stripe setup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=362

commit 8b8691ef70f37d42100f502604ef94b8b9e5f5f8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Nov 10 02:32:50 2009 +0000

    cluster/stripe: local was not being set in stripe_mknod_ifreg_setxattr_cbk()
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 367 (GlusterFS crash while doing mknod in stripe setup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=367

commit 9bbe8d4cd989d331409e174cefd38caed41b0ea0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Nov 9 14:17:34 2009 +0000

    core: Replace inode_search with inode_grep in inode_from_path
    
    This fixes a situation where the inode_from_path fails to
    return an inode even though the inode exists in the table.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit c1bf268b28d5d5959295cf1a22bdb71d0a6a9687
Author: Sachidananda <sac@gluster.com>
Date:   Mon Nov 9 08:33:25 2009 +0000

    Add unhashed-sticky-bit option to volume_options structure
    
    Signed-off-by: Sachidananda <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 365 (unhashed-sticky-bit is not recognized)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=365

commit ef078a335980b5962239556e9b3a98f589662337
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Nov 4 01:23:18 2009 +0000

    Add glusterfs-volgen to master, change fusermount options and other changes to rpm spec file.
    
    The patch has the following changes:
    * Rename glusterfs-volgen.py and include it in the rpm spec file
    * Enable fusermount by default. Change fusermount configure option from disable to enable.
    * Remove BDB from configure.ac, essentially removing it from the normal build.
    * Remove all dependencies on fuse in the rpm spec file.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 343 (Placeholder bug for adding volgen into rpm, bdb makefile changes, etc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=343

commit e98020d5f6f2f22f09d2c21d80ad8ceb6ae46284
Author: vinayak hegde <vinayak@gluster.com>
Date:   Wed Nov 4 23:36:35 2009 +0000

    performance/stat-prefetch: In lookup_cbk do not set error no to EINVAL, when inode_ctx_get returns -1.
    
    Signed-off-by: vinayak <vinayak@laptop.(none)>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 360 (All fop fails when stat-prefetch is loaded on afr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=360

commit f98e7524b4c442ae08c3a335d412b1eeccb5863b
Author: vinayak hegde <vinayak@gluster.com>
Date:   Thu Nov 5 02:54:27 2009 +0000

    cluster/afr: In fop structure afr_readdirp is not correctly registered.
    
    Signed-off-by: Vinayak Hegde <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 360 (All fop fails when stat-prefetch is loaded on afr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=360

commit add4dd9623de51dd67ecb8450ad1a57894d92dc2
Author: vinayak hegde <vinayak@gluster.com>
Date:   Thu Nov 5 02:53:48 2009 +0000

    performance/stat-prefetch: In sp_readdir_cbk op_ret value is not handled.
    
    Signed-off-by: Vinayak Hegde <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 360 (All fop fails when stat-prefetch is loaded on afr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=360

commit e151ab3ed4718606767146f18b416f8900552fbc
Author: vinayak hegde <vinayak@gluster.com>
Date:   Thu Nov 5 02:53:03 2009 +0000

    libglusterfs/src/gf-dirent.c: In gf_dirent_nb structure d_name should be char array of size 1.
    
    Signed-off-by: Vinayak Hegde <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 360 (All fop fails when stat-prefetch is loaded on afr.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=360

commit 47da643a0e9d8786489fe3173de318732556b6f0
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Nov 4 02:03:05 2009 +0000

    Do not abort make install if a chown on the fuser-mount script does not succeed.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 343 (Placeholder bug for adding volgen into rpm, bdb makefile changes, etc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=343

commit 7bd570a007202e6eb505091dba611b8320633a26
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Nov 3 11:08:32 2009 +0000

    Remove fuse_lowlevel.h from xlator.h in libglusterfs.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 343 (Placeholder bug for adding volgen into rpm, bdb makefile changes, etc)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=343

commit 612aed4b6aab7447195c7e6715bbbf257b4c62f2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Nov 4 00:15:20 2009 +0000

    libglusterfsclient: Dont alloc root inode context
    
    ....because the lookup on root inode done a few lines before this
    call already allocates an inode context. This one just over-writes
    that context, results in invalidation of the cached iattrs.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 354 (Stale file handle on unfs3 booster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=354

commit f04b9fcfeb9b459552207031d003f801189d1cea
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Nov 4 00:15:19 2009 +0000

    libglusterfsclient: Prevent root inode number clobbering
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 354 (Stale file handle on unfs3 booster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=354

commit 51d105d63fa82dae5465d19598b489d453b3a902
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Nov 3 10:17:07 2009 +0000

    cluster/afr: Bail out of the self-heal driver loops as soon as possible
    
    Don't wait for the next recursive call to sh_{full,diff}_loop_driver
    to decide that we've reached the end of file, as the frame could
    have been destroyed by that time (if subvolumes are posix).
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit cd7a02533dbbc192cc117037cf39848d55210c83
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Nov 3 09:23:03 2009 +0000

    Remove unnecessary log message. It also accesses a freed lock after an 'unlock'.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit 2bda225433762f78c09c2a751b321eb9d94c37c6
Author: Corentin Chary <corentin.chary@gmail.com>
Date:   Tue Oct 27 12:57:35 2009 +0000

    transport/name.c: refine the address resolution logic when listen-host is not specified.
    
    - when listen-host is not specified and there are are no interfaces having
        adresses belonging to the address-family specified, listen at 0.0.0.0/::0.
    
      - this patch is necessary since with AI_ADDRCONFIG, getaddrinfo fails if there
        are no active interfaces for the address family specified and when
        listen-host is specified we still want the functionality provided with
        usage of AI_ADDRCONFIG.
    Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 339 (glusterfsd fails to start when there are no active interfaces having address in the address family configured.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=339

commit 2a62b1748edcb8319e6ce36e72717c8154635db6
Author: Sachidananda <sac@gluster.com>
Date:   Tue Nov 3 08:38:25 2009 +0000

    Wrong variable is checked after stat call.
    
    Signed-off-by: Sachidananda <sac@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 355 (Wrong variable checked after a stat call)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=355

commit c1aa64729130aab9b58925871768d6c9c7d6a4ba
Author: vinayak hegde <vinayak@gluster.com>
Date:   Mon Nov 2 23:41:26 2009 +0000

    configure.ac: Before checking for libglusterfsclient BUILD_LIBGLUSTERFSCLIENT should be initialized to no.
    
    Signed-off-by: Vinayak <vinayak@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 353 (./configure adds libglusterfsclient when it shouldn't)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=353

commit 7269a745125d46d52f31a4550136690fd0166355
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Nov 2 03:24:10 2009 +0000

    storage/posix: Changed error message displayed for option background-unlink.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 352 (Wrong message logged for option `background-unlink')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=352

commit f8a56c6322d729fcdb96c754dd421fffb025e3bb
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Nov 2 00:34:10 2009 +0000

    features/locks: Do not try to set value in dict when lookup has failed.
    
    lock-count was being set without checking for op_ret from lookup. This would
    cause a lot of Critical messages in the log as dict would be NULL in case
    of a lookup failure.
    
    Also, removed some trailing white spaces and did some minor re-factoring.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit b4b20984721e169763a5ac26ffb9353d1ca3568a
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Oct 30 05:27:50 2009 +0000

    cluster/afr: Don't try to self-heal if there are locks held
    
    If the inodelk_count or entrylk_count is positive on a
    file/directory, don't try to do self-heal on it.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 326 ([2.0.8rc9] Spurious self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

commit 2b610a095febf0e89e5341c575b5579c78a009a3
Author: Corentin Chary <corentin.chary@gmail.com>
Date:   Thu Oct 15 06:32:41 2009 +0000

    volgen: remove trailing whitespace
    
    Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ef79f934c38743f3618c00bc24043a484f284a47
Author: Corentin Chary <corentin.chary@gmail.com>
Date:   Thu Oct 15 06:32:40 2009 +0000

    volgen: Add conf-dir option
    
    Add a conf-dir option to change the output directory for
    generated files.
    
    Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 0e7875dbf8f70904257725fd4d2be30333da84a2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 30 03:43:54 2009 +0000

    core: Use parent for condition to create dentry not name
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 348 (touch on booster segfaults)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=348

commit 44f6b7a54224dde7e1663f435f05a6a5cac25a7b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 30 03:28:40 2009 +0000

    booster: Must check errno for error number not return value
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 346 (booster returns success on failed getxattr and lgetxattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=346

commit 10cddf14e9f7a7446ea48bedb07ee9e7d0f21e4f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 30 03:28:39 2009 +0000

    core: Check for NULL to avoid segfault
    
    A segfault as a result of this was observed during tests.
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 348 (touch on booster segfaults)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=348

commit e6fc0cbe716a18f02891d3911481fdcb121d8840
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 30 03:28:38 2009 +0000

    booster, libglusterfsclient: Support samba specific relative paths
    
    Signed-off-by: Shehjar Tikoo <shehjart@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 158 (libglusterfsclient: Applications are restricted to using absolute paths)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=158

commit 5d9a4d81b3928e6af15aaeb7fab18fb451f7abcc
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 30 03:15:19 2009 +0000

    iobuf: initialize size without 4KB padding
    
    since new fuse bridge takes care of landing write buffers to aligned iobufs
    and the 4KB header padding is no more necessary
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit bee7b8877dfbc321637e00106c073fecdd0847f0
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 30 03:15:02 2009 +0000

    glusterfsd: whitespace cleanup
    
    Signed-off-by: Anand V. Avati <avati@blackhole.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit ef2d6b3449ab9cf0cf653b7b84595521db63a412
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 30 01:26:19 2009 +0000

    libglusterfsclient: don't do inode_link on root inode.
    
    Signed-off-by: Raghavendra G <raghavendra@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 348 (touch on booster segfaults)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=348

commit 8345b6448d292a8da4464debb4dc65b55f1f6eeb
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 30 00:10:20 2009 +0000

    performance/io-cache: change the data-types to be big enough to hold size of data flushed.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit e16f05a6d1f756f16e363d93f432f950901cf777
Author: Pavan Sondur <pavan@gluster.com>
Date:   Fri Oct 30 01:45:20 2009 +0000

    Fix logic while granting blocked entrylks, which could run into an infinite loop.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit c68255daa11937b7f91de11f8d4361d798aa8cbc
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 29 22:53:57 2009 +0000

    call-stub: fix leak of fxattrop dictionary
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 382b4d03ab029a94f29231e19db9996596985bb7
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 29 22:53:28 2009 +0000

    protocol/server: fix leak of xattrop dictionary
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit d72c47cb04725c694921e7f3277f6230c26bc936
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 29 05:08:34 2009 +0000

    cluster/afr: Move deleted files to /.trash in entry self-heal.
    
    If entry self-heal determines that a file/directory should
    be deleted from a subvolume, move that entry to a directory
    called "/.trash" on that subvolume. This is for two reasons:
    
    1) It limits the damage that can be done by a "wrong" entry
       self-heal.
    
    2) It solves the problem of a to-be-deleted directory not
       being empty.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 227 (replicate selfheal does not remove directory with contents in it)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=227

commit 14962ce3e69e452a2447c12cde3369759365fda9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 28 04:46:25 2009 +0000

    performance/io-cache: change the hash function used for rbtree based hash table.
    
    - the earlier hash function does not distribute pages uniformly for offsets that
        fit into 32 bits. The reason is that the hash function just xors the contents of
        the key 4 bytes at a time with the current value of hash. Hence for keys that
        fit into 32 bits, the hash will be the key itself. Since we are using the
        rounded_offset (which is a multiple of 128KB) as the key, the key will
        be exactly divisible by the number of buckets configured (4096) resolving all
        the pages into the first bucket.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit 13e6947744e8a26d2380af200942fd4ed61fd845
Author: Pavan Sondur <pavan@gluster.com>
Date:   Thu Oct 29 05:06:58 2009 +0000

    Remove unnecessary check of xattr_req in lookup.
    
    Signed-off-by: Pavan Vilas Sondur <pavan@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit c770322ca4c9ccf50530d6a05ac4107fa1236f60
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 29 07:32:46 2009 +0000

    storage/posix: Serialize do_xattrop.
    
    Hold a lock on the inode for the getxattr/add-array/setxattr
    section since multiple threads can enter into it causing
    wrong values to be written and triggering spurious replicate
    self-heal later.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 326 ([2.0.8rc9] Spurious self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

commit 32c963cfea91e196ee1ebf98a5579989c53fdc6c
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 29 07:32:26 2009 +0000

    storage/posix: Refactor xattrop
    
    Move common code into do_xattrop.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 326 ([2.0.8rc9] Spurious self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

commit 6e2dba2c418cd09206b390fad0f413fc287b93ee
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 29 09:09:15 2009 +0000

    protocol/server, mount/fuse: Handle returned inode in create properly
    
    Check if linked_inode is different from returned inode in create,
    and if so, make the fd point to the correct inode.
    
    Signed-off-by: Vikas Gorur <vikas@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 347 (Assertion failed: inode->ref)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=347

commit c555dcbb3a41f47149035c1d9ea95f67812db8c8
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Oct 29 05:59:44 2009 +0000

    transport/socket:Enable NODELAY by default for lowlat client and server sockets
    
    TCP_NODELAY is enabled by default for lowlat client and server sockets.
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 344 (Add support for TCP NODELAY in master)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=344

commit c0b5cc88687f4f0b25a411b7d0746dcadb297ce3
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Oct 29 05:58:37 2009 +0000

    protocol/client: Support for TCP_NODELAY
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 344 (Add support for TCP NODELAY in master)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=344

commit 0897c400c0864be252e5d23d41b71779f70eafe4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Thu Oct 29 05:58:07 2009 +0000

    transport/socket: Support for TCP_NODELAY
    
    Signed-off-by: Vijay Bellur <vijay@gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 344 (Add support for TCP NODELAY in master)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=344

commit 82c0df9941abfb4836947fce1ff9da266dbd7499
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Oct 28 17:04:33 2009 +0000

    Print inodelks in and out if option trace is on.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit 08327b6a6bdb7a3807a9d279b6d5f99686d13b99
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Oct 28 17:04:05 2009 +0000

    Print entrylks in and out if option trace is on.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit 03c6fe7f7e51d391beb370d04964af1de9728d28
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Oct 28 17:03:37 2009 +0000

    Trace locks in and out with an option in normal log mode.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit 9a62a3747cfcef2db3bc0b630a92f24d9436eeca
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 29 01:03:09 2009 +0000

    posix: posix_[f]setattr() handle valid=0 case by performing {f, l}chown (-1, -1)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit b3b4fc4afb7d206d0a481f3234bf83c768f02aa2
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Oct 28 12:27:54 2009 +0000

    Implement lookup in locks to return lock count in a dict value.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit 53ff4f0299cf14c6c413d3e49991a6f05f9cda19
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 28 18:42:35 2009 +0000

    libglusterfs/rbtree: change rbthash_init_table to take no of expected entries in the hash table as argument.
    
    - the expected number of entries is used to create the memory pool of the hash
        table. Having constant macro for this purpose is not suitable since different
        users of rbtree based hash table store different number of entries in the
        table.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit 07e8d8a37713d39f63713d8c05dd99a0610a3c35
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 28 16:15:37 2009 +0000

    performance/io-cache: fix memory leak.
    
    - page table of cache was not being destroyed in ioc_forget.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit 11dd6bcb416c2e937ced2b2bbd35fe10b21f283f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 28 16:15:03 2009 +0000

    performance/io-cache: fix double free.
    
    - the destroyer function passed to rbthash_table_init is used to free the data.
        The data being inserted is page and it is destroyed in ioc_page_destroy. Hence
        no destroyer function needs to be passed to rbthash_table_init.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit f513157e93bbba885f12f10ca2fb94424d7aea5e
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Wed Oct 28 07:15:55 2009 -0700

    Add -s (signoff) to format-patch.sh

commit 7e66ba43d7b75b63cdbf08e2d871136a6648a3a7
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Oct 28 06:22:44 2009 +0000

    Add glusterfs-volgen to master
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 343 (GlusterFS volume generator - 'volgen')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=343

commit ef7524ec1eda990cb89bee06eff2ef2d7c49d0d2
Author: Anand Avati <avati@gluster.com>
Date:   Wed Oct 28 05:40:12 2009 +0000

    fuse: use postbuf in truncate_cbk for attributes to return
    
    this causes a problem where inodes even after truncate show old
    file size for a short time (till attributes are expired in fuse kernel module)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 1f4e97c01a8483e227e9e66d421302b4114decd1
Author: Anand Avati <avati@gluster.com>
Date:   Wed Oct 28 04:20:14 2009 +0000

    xlator: initialize all xlators in a loop instead of top down initialization
    
    top-down initialization will miss out on xlators from disconnected subgraphs
    and notify can go prematurely to these xlators
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 341 (mountpoint first access failure in single address space mode client/server)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=341

commit 6bfbcf7326a1261c8ff7cde9fd2c76a55cf756ae
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Oct 27 08:47:28 2009 +0000

    mount/fuse: Derive fd from the file handle for setattr
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit b4dd7534007dccbc90d7341259bd92a0ff6a678c
Author: Anand Avati <avati@gluster.com>
Date:   Wed Oct 28 02:36:31 2009 +0000

    protocol/server: resolver fixes
    
    1. do not set ENOENT for RESOLVE_MAY case
    2. set op_ret to -1 and op_errno to EINVAL when request has neither of entry, inode or fd handles
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 3809bb1bbd617dbde1d943dbcf6b0346329187b6
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Oct 26 03:01:33 2009 +0000

    performance/io-cache: change data structure used to store page-cache.
    
    - io-cache uses rbtree based hash tables to store page-cache instead of lists.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 335 (Io-cache optimization)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=335

commit 78d281d6026ad1ebe8cc65c4396055902369ea89
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Oct 27 06:09:46 2009 +0000

    cluster/afr: Set local->fd in fsync.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 5674c41b3ea4eac8fe8f4f74bd978699bc847332
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Tue Oct 27 05:52:16 2009 -0700

    extras/init.d: make install directory configurable with --with-initdir

commit fad22625b4012e9a5d6b29bb23f0d864c611ae1c
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Oct 27 05:13:05 2009 +0000

    mount/fuse: Use correct offset for name in fuse_getxattr
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c415e5cfb87bc240ae8438e9df995ce45b55004e
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Oct 26 19:53:33 2009 +0000

    Don't stop an already running glusterfsd upon upgrade or install.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 338 (rpm post uninstall kills glusterfsd process)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=338

commit b5fe35e215626b98b19876bc0f53b9184aef664b
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 26 11:57:28 2009 +0000

    cluster/afr: Remove struct's for [f]chown, [f]chmod, utimens from afr_local_t.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 78c98cac267ef9aebcaa3c35d70ea93c17462e62
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 26 09:15:13 2009 +0000

    cluster/afr: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit a284bf490cdf6ce334a4e70b22eedd7e639620f9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 26 05:24:19 2009 +0000

    cluster/afr: Pick the data self-heal algorithm dynamically.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit d40ce2cbcd41a25eb053f2970db9bbaab2dafa22
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 26 05:07:31 2009 +0000

    cluster/afr: Check the target of symlink's in entry self-heal.
    
    During entry self-heal, make sure not only that a symlink
    exists on all subvolumes, but also that their targets match.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 193 (symlink contents not self-healed by replicate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=193

commit 82dea3043878099e392b71bef9ae5de616ac5533
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 26 05:34:21 2009 +0000

    storage/posix: Ensure time(2) is stored in a 64-bit variable.
    
    Before multiplying the time_t value by 2^32, store it in a
    64-bit variable. This is necessary on 32-bit systems, where
    time_t is only 32-bits, and left-shifting by 32 results in 0.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit bd145077164ee20e3eb03f09b401e9a3ebdf8b6e
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 26 05:45:59 2009 +0000

    protocol/server: touchup loc only if inode/entry resolution was successful
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 79a5b7273d107f3c73534a117157184ffbc170e8
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 26 05:43:59 2009 +0000

    protocol/server: fix assignment of inode number in server_readlink
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 106a651826eeaacf9d0b40fe6d088d6bdc997675
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 23 13:02:01 2009 +0000

    booster: seperate out the implementations of readdir and readdir64.
    
    - readdir and readdir64 should not call same procedure booster_readdir
        in their implementation, since the layout of dirent structures returned by
        libc implementations of readdir and readdir64 is different (readdir returns
        struct dirent *, where as readdir64 returns struct dirent64 *).
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 333 (ls on paths not on virtual mounts report wrong directory contents)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=333

commit 7445700d0323cbfac11b0e1367b0052438e38318
Author: Vikas Gorur <vikas@gluster.com>
Date:   Sat Oct 24 08:17:36 2009 +0000

    cluster/afr: Set read-subvolume to the source while self-heal is in progress.
    
    Just before the lookup is unwound during background data self-heal,
    the read subvolume is set to the self-heal source subvol so that
    read operations on the file work correctly, and don't have to
    wait for the self-heal to complete.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 4163a3f8fbcc5e0d84d955258161f3a6f7a86de8
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Oct 23 10:11:47 2009 +0000

    cluster/afr: Do self-heal in the background.
    
    This patch introduces a new option "background-self-heal-count", with a
    default value of 16.
    
    This means that upto {background-self-heal-count} number of files/directories
    will be healed in the background at any given time. If such number of self-heals
    are already in progress, further self-heals take place in the foreground.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 6490122f107c992f2600fc7d3214a43c3f50df70
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Oct 23 09:31:52 2009 +0000

    cluster/afr: Pipeline the "diff" data self-heal read-write loop.
    
    Start upto "data-self-heal-window-size" instances of the read-write loop
    of the "diff" data self-heal algorithm simultaneously.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 10dea439359238aed4dbad0e2c25df9fb2d5f28e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Fri Oct 23 08:37:29 2009 +0000

    mount/fuse: Don't use fsi if it is already cleaned up
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit a5219b99db8076dc8606a44fd1cfaf2bd69a0d31
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 23 08:23:20 2009 +0000

    protocol/server: deep resolution support
    
    when requested ino/gen is not available in the inode table cache,
    then use the path presented by the client to lookup entries with
    the hope that the requested ino/gen gets populated into the cache.
    
    re-perform regular search after finishing the deep component
    lookup
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 52b02bbabaaa78061c6b223715f57853cbcfd652
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 23 08:22:49 2009 +0000

    protocol/server: send fresh lookups on revalidate failures
    
    also unlink non existent dentries in lookup_cbk
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 919d80171c73cf3ed516c089603f0c635cf5a376
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 23 08:22:20 2009 +0000

    whitespace fixes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 00d2fafa1bcab7758aa20741a20fb4ea38b9a8ff
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 15 04:48:09 2009 +0000

    cluster/afr: Pipeline the "full" data self-heal read-write loop.
    
    Start upto "data-self-heal-window-size" instances of the read-write loop
    of the "full" data self-heal algorithm simultaneously.
    
    Add a new option "data-self-heal-window-size" with range [1-1024],
    and a default value of 16.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 320 (Improve self-heal performance)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=320

commit 58efcf03a63324b7bbfda864647d35256917058a
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Oct 23 06:44:46 2009 +0000

    cluster/afr: Prevent spurious entry self-heal.
    
    If the initial lookup shows that 'pending' is positive, then
    self-heal will hold a lock and do a lookup again. This lookup
    might show that 'pending' is zero everywhere. However, entry
    self-heal used to consider this as a case of 'no sources' and
    try to merge the directories. This patch checks for that case
    and does not do the merge.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 326 ([2.0.8rc9] Spurious self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

commit dfa1f5755b11d11c81cbbdd79dcb5b3f8d216ac9
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 22 02:04:39 2009 +0000

    fuse-bridge: send fresh lookup on failed revalidate to return new nodeid
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit fc00f8c622f207577b4568b5e8dd43c6147e34c2
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 22 02:04:21 2009 +0000

    inode.c: whitespace fixes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 8c86febc41816730c9fd44fd87cefe3ef330d072
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 22 06:36:22 2009 +0000

    cluster/afr: entry self-heal: Store parent_loc on the heap for impunge_parent_setattr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 137 (Parent directory mtime not reset after a create in self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137

commit d5009323b3031122508fbd8daa61025b7c397e3c
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 22 05:37:36 2009 +0000

    cluster/afr: entry self-heal: Set parent directory's attributes using a new frame.
    
    There was a race condition in assuming that afr_sh_entry_impunge_parent_setattr_cbk will
       always return before impunge_xattrop_cbk and impunge_setattr_cbk.
    
       This patch fixes two additional problems:
    
    1) Building the parent_loc from impunge_local->loc after STACK_WIND to
       impunge_xattrop_cbk has happened. In a simple afr-posix configuration
       the stack will have been destroyed by the time building of parent_loc is
       attempted.
    
    2) parent_loc built in impunge_newfile_cbk was not being loc_wipe'd.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 137 (Parent directory mtime not reset after a create in self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137

commit 1fe48896b950e74b589a8ed2c62bfb8571a0bf16
Author: vinayak hegde <vinayak@gluster.com>
Date:   Tue Oct 20 23:56:28 2009 +0000

    glusterfsd.c: Unnecessary writing of strerror of errorno on pipe
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 4 (mount --bind fails if run immediately after mounting GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=4

commit 568b3ffa1625a12585cc14565fdb9acfa5b36a1a
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 20 11:53:24 2009 +0000

    protocol/server: generation number and dentry resolution
    
    - handle generation number in protocol
    - rewrite server dentry resolution code for inode cache miss
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 40fb2587c5709f732dcd575945a8fdbaa51c07ea
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 20 10:54:24 2009 +0000

    inode: fix internal refs and minor fixes
    
    * also fix trailing whitespaces in a couple of places
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 492993570bb02bd7d244693ad28e409973fa9f4c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Oct 20 03:43:43 2009 +0000

    performance/write-behind: fix to bug in setattr which was causing frames to be missed.
    
    - local->file was being assigned even before file pointer was got from any of
        the fds opened on the inode, thus making local->file to be NULL. In
        wb_setattr_cbk, since local->file is NULL (and hence file passed to
        wb_process_queue), wb_process_queue does not resume the pending operations
        queued for the file.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 327 (dbench does not complete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=327

commit 61d0ad544322ea0e0e9b0549662b8ca912641951
Author: vinayak hegde <vinayak@gluster.com>
Date:   Tue Oct 20 07:18:16 2009 +0000

    performance/read-ahead: Process state dump operations are added.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit f8d40aad7e21389911b151d6445dd8197bec0049
Author: vinayak hegde <vinayak@gluster.com>
Date:   Tue Oct 20 07:17:42 2009 +0000

    performance/quick-read: Process state dump operations are added.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit f90bc2a051ea4d6d23dd4c28ca018fcb1aa9cdaf
Author: vinayak hegde <vinayak@gluster.com>
Date:   Tue Oct 20 07:17:06 2009 +0000

    performance/write-behind: Process state dump operations are added.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit 4d5ab4c0b8a296e12d80933aad03d06a044c6af2
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Oct 20 01:35:17 2009 +0000

    cluster/afr: Attempt to set fd ctx in create only if the call has succeeded.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 325 (crash in afr_fd_ctx_set)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=325

commit a2a09bb7f3d60a441c1e678484e2a1a3ac332a1e
Author: Anand Avati <avati@gluster.com>
Date:   Sun Oct 18 15:02:02 2009 +0000

    protocol/client: incoroporate generation numbers
    
    protocol/client uses the new inode_ctx_{get,put}2 API to store both inode and
    generation number in context
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 7d62e85887047a64df17904c91136c1bc1c89bd4
Author: Anand Avati <avati@gluster.com>
Date:   Sun Oct 18 15:01:07 2009 +0000

    protocol: format changes to incorporate generation numbers
    
    incorporate 64bit generation field in all protocol headers to accompany an inode
    number
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 11ddca1cd151479243fe23e579b76c5984f422c3
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Oct 18 14:05:40 2009 +0000

    inode_ctx_{get,put,del}2 API support
    
    support for storing multiple values for a key in inode context - used for storing
    inode and generation number pairs on the server in protocol/client inode ctx
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 3d09fb99093a84a303edc443b68bdf9eb10096b4
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Sun Oct 18 13:35:15 2009 +0000

    fuse: use inode_t address as nodeid and use new inode API
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 7e831d735e3746fa9e6ec2e797e1a7f68ac5c148
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Sun Oct 18 13:35:14 2009 +0000

    inode: API changes for generation number support
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit b2c0c6c713a00631e658c7faafe51d0c941d65ef
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Sun Oct 18 13:35:13 2009 +0000

    inode: fix indentation and spacings
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 9d73eb4c8a9bf1e802985abee83ad36439ab681a
Author: Anand Avati <avati@gluster.com>
Date:   Sun Oct 18 11:42:30 2009 +0000

    locks: fix leak in inodelk
    
    unlock was resulting in leak of lock structure if it was unlocking the last existing lock
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 306 (Enhance locks to aid debugging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=306

commit aacde00714c60db438c2fdc5ebacbe60a988f60b
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Oct 18 09:58:18 2009 +0000

    storage/posix: Set right the op_ret value from posix_readlink()
    
    Since op_ret was being returned as 0, fuse would regard the readlink () as a failure.
    Also, set right the buffer size of gen_key in posix_{f, l}stat_with_gen.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit aa701e2f607902628fce196de3eb0402aede7736
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 16 09:13:22 2009 +0000

    indentation fixes to conform to coding standards in locks
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 7bf78408ffec1efbceed17ed2e540d7d0af19763
Author: Anand Avati <avati@gluster.com>
Date:   Fri Oct 16 09:12:57 2009 +0000

    locks: keep ref on the inode while locks are held
    
    keeping refs on the inode while there are held locks prevents the
    inode from getting pruned away
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 5d423ab4548c941921c1e64135fec6e15c7787f2
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Fri Oct 16 08:48:42 2009 +0000

    posix: posix_{f, l}stat_with_gen to return 0 on success (instead of >= 0)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit d56c6a81ba22e5caca68bfa6fc0eb5f3079c9d22
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Fri Oct 16 07:30:26 2009 +0000

    posix - generation number support
    
    - use sequential gen counter
    - move span_devices handling and generation assignment to common functions
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 355150088d688fafd82c54af80a583a26732d0da
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Fri Oct 16 07:30:25 2009 +0000

    posix - use lchown and lchmod in setattr
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit ff38298144730c95627cfc11416baa6b75d3c94d
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Fri Oct 16 07:30:24 2009 +0000

    distribute - more NULL check
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit cb76cadb74a36e220a2b6a886c0c8068abdad0c7
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Fri Oct 16 07:30:23 2009 +0000

    distribute,nufa: layout handling changes
    
    changes to make revalidate not fail but instead perform fresh lookup
    and swap inode context (layout) safely
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit fa4e9d639b95b557ae64dab38c4c3ff8a0ec0d7a
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Fri Oct 16 07:30:22 2009 +0000

    fix double initialization of dht_local_t
    
    This was causing leak of the first initialized frame->local in
    every create call
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 3defca52e68cd65b6a32876e00de72832e247171
Author: Anand V. Avati <avati@blackhole.gluster.com>
Date:   Fri Oct 16 07:30:21 2009 +0000

    NULL checks on local->loc.parent
    
    check for presence of local->loc.parent != NULL before defering to
    pick ino for post/preparent parameters. local->loc.parent can be NULL
    legally when loc is describing "/"
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 315 (generation number support)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

commit 61b5516701224073bbf71afea93ce58d5bd6b811
Author: vinayak hegde <vinayak@gluster.com>
Date:   Fri Oct 16 00:38:25 2009 +0000

    performance/write-behind: initialize frame->local before goto out label
    
    if mtime,atime are not changed,
    frame->local will not be initialized.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 310 (While trying to create a file on replicate with write behind set-up, client crashes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=310

commit 6fda29fcd64dffbbfdbbf63eed69a557e46598d0
Author: Anand Avati <avati@gluster.com>
Date:   Thu Oct 15 11:28:00 2009 +0000

    shuffle hash layouts on directories
    
    allow for hash layouts to be written differently for different
    directories to give a better spread for same filenames across
    directories
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 324 (distribute does not spread files of the same name among all servers)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=324

commit ccb0f6fa67c148545e536d1033abe1652520bdb3
Author: vinayak hegde <vinayak@gluster.com>
Date:   Thu Oct 15 00:27:14 2009 +0000

    performance/write-behind: In wb_setattr, inode is checked twice
    
    1. check for is it a directory,
    2. otherwise check for inode and continue.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 310 (While trying to create a file on replicate with write behind set-up, client crashes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=310

commit 8b048b48b6925d0f774875abe5cdfccf4b26a868
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 15 01:47:54 2009 +0000

    performance/io-cache: remove caching in lookup.
    
    - caching file contents in io-cache during lookup is obsolete since quick-read
        does the same work.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 314 (Hang in quick-read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=314

commit b78fa55bbbb645d4a9ac58ff7f6b59684dfa83d4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 15 08:39:01 2009 +0000

    performance/quick-read: frame->local need not be set in qr_open_cbk.
    
    - local is used only by certain operations and hence it need not be set by
        all the operations invoking open.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 323 (fd leak with quick-read loaded in translator tree)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=323

commit 680164e64ab9a3817364626cd27cdc997ca16414
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Oct 14 21:14:36 2009 +0000

    performance/quick-read: flush should proceed with winding if fd-context is not found.
    
    - if the fd-context is not set, quick-read has no role to play other than
        just passing down the call to underlying translators.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 317 (Data corruption with write-behind loaded in translator tree.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=317

commit 44db9af90b7280520c1c599d2bf54dd477961948
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 14 14:00:58 2009 +0000

    storage/posix: Use the right macro to set nsec of mtime in posix_do_utimes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 296 (handle futimes correctly in FUSE)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=296

commit 4203033c2da0598712d34389f8ef5ce8c24334b4
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 14 14:00:07 2009 +0000

    mount/fuse: Initialize attr and set nsec values for atime and mtime.
    
    attr was not being initialized and NSEC values were not being set in attr.
    These were being referenced in posix_do_utimes which could cause a failure of
    utimes ().
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 296 (handle futimes correctly in FUSE)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=296

commit 347385beb519d75cd1457a36cf13a02fd2e60a92
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 14 13:48:23 2009 +0000

    performance/write-behind:STACK_UNWIND happens only in failure path of wb_stat()
    
    Only in case of errors STACK_UNWIND happens in wb_stat().
    Also, fixed an incorrect check which would fail all writes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 309 (In replicate set-up when exnihilate.sh is run , client crashes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=309

commit 89b40ae93a09043e9d9384ce8c631d0c5abe6787
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 14 07:32:37 2009 +0000

    storage/posix: Initialize op_errno to 0 in posix_create.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 309 (In replicate set-up when exnihilate.sh is run , client crashes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=309

commit a9364b0a56186a3203820aca69b9875266e4c5f6
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Oct 14 05:50:59 2009 +0000

    io-cache: NFS-friendly changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 65f02619c7d4b29caa8dd11b78c294c521116f12
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Oct 14 02:07:25 2009 +0000

    performance/write-behind: return from wb_open after STACK_WIND
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 312 (iozone crash in Distribute-Replicate)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=312

commit 7c4429b9631c3c9866620887d6a41030466f71e3
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 13 07:32:46 2009 +0000

    afr transaction: fix op_ret check during locking
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

commit 103a9ecfaf5881b31844b8a12a5b98dc5308a800
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Oct 13 06:42:28 2009 +0000

    cluster/afr: Set mtime of parent directory in self-heal properly.
    
    While creating/deleting an entry as part of entry self-heal,
    set the parent directory's mtime to match that on the source
    subvolume.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 137 (Parent directory mtime not reset after a create in self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137

commit 7d6e73d4421265a304fd22964649e555a2db8097
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Oct 13 06:42:13 2009 +0000

    posix/client/server: Send postparent in lookup even if lookup fails on the entry itself.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 137 (Parent directory mtime not reset after a create in self-heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137

commit f085beebd03b2c8be2fa57039ad3cbcb6eaa66d3
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 13 06:42:15 2009 +0000

    prevent spurious unlocks from afr selfheal
    
    afr selfheal now remembers all the nodes on which locks were successfully
    held and sends unlocks only to those nodes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

commit b20cee457232a88517af44ae4505361dd3a4de15
Author: Anand Avati <avati@gluster.com>
Date:   Tue Oct 13 06:22:37 2009 +0000

    afr transaction prevent spurious unlocks
    
    mark a subvol with held lock only if op_ret == 0
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

commit babdbcbb6a434d65b0fdd9df708e94bea13cf05d
Author: vinayak hegde <vinayak@gluster.com>
Date:   Mon Oct 12 23:38:41 2009 +0000

    performance/write-behind: In wb_setattr file is used before getting fd context
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 310 (While trying to create a file on replicate with write behind set-up, client crashes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=310

commit e84a3cf74947d7a6deace07a1726376aa0a8a6a4
Author: vinayak hegde <vinayak@gluster.com>
Date:   Mon Oct 12 09:09:33 2009 +0000

    performance/write-behind: file is referenced, without checking for NULL
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 310 (While trying to create a file on replicate with write behind set-up, client crashes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=310

commit 6df45979aae89a217e43c59a8f0a8087915ce5d8
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 12 07:01:13 2009 +0000

    cluster/afr: Hold second lock after first lock has been granted for rename transactions.
    
    Hold the lock on the {higher_path} only after the lock on the
    {lower_path} has been granted successfully.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

commit 0f177f59d199484a15490359f6db69bfa8dff82d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 12 09:12:45 2009 +0000

    protocol/server: Set preparent and postparent in the response struct.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 5cec042dfa7d7c9699d3110f849a78b2569aa8d9
Author: Anand Avati <avati@gluster.com>
Date:   Mon Oct 12 11:26:59 2009 +0000

    replicate: fix missing frame in entry-self-heal
    
    when files on all backend nodes are missing, the logic in afr_sh_entry_erase_pending
    is broken and results in missing lookup frame. this causes processes to enter into
    uninterruptible sleep state.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 311 (missing frame (lookup) when entry-selfheal finds missing files in all backend nodes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=311

commit a3da2ad4cd1c8c6adaa0f5055820541254f8c91d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 9 12:40:19 2009 +0000

    performance/quick-read: change the default option values in quick-read.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 273 (Code review and optimize quick-read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=273

commit 077d73fa467bcd0a5ac4be26bb4b366d5fc20a69
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 9 09:15:36 2009 +0000

    posix: Ensure ENOTEMPTY return on rmdir
    
    Since we added an extra step after rmdir, i.e.
    the lstat on parent dir as part of the NFS-friendly
    changes, the successful return from postparent lstat
    clobbers the -1 error return from rmdir.
    
    This prevents this particularly ENOTEMPTY error from
    being propagated to higher translators.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 73027dae835fc968dc443294fc8c109110168d37
Author: Anand Avati <avati@dev.gluster.com>
Date:   Fri Oct 9 08:00:23 2009 +0000

    Add INIT_LIST_HEAD which was left out in the previous commit
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 297 (Posix locks cannot handle a single unlock over multiple held locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=297

commit 7ef987661626ee2e9de033470bafb7c864e01fe1
Author: Corentin Chary <corentin.chary@gmail.com>
Date:   Tue Oct 6 06:36:31 2009 +0000

    Add all generated files to .gitignore
    
    Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 2231e5f8ab2be2721ebb6662bd1e252cd89cea7a
Author: Corentin Chary <corentin.chary@gmail.com>
Date:   Fri Oct 9 06:25:11 2009 +0000

    features/locks: Fix insert_and_merge
    
    Init the list structure, because it will be used later,
    and subtract_lock does not do it.
    
    Also remove the special handling for unlocks, which was
    probably introduced as a workaround for this bug.
    
    Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 297 (Posix locks cannot handle a single unlock over multiple held locks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=297

commit 58bc556b84792562ff6cdc60e0e7a48006eb56a9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 9 02:40:10 2009 +0000

    performance/write-behind: Add enable-trickling-writes to volume_options.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit 72fc9328b1959f2f3e8b24048995cb70a090e0a3
Author: vinayak hegde <vinayak@gluster.com>
Date:   Fri Oct 9 02:38:13 2009 +0000

    debug/trace: Check asprintf return value to avoid warning, while build
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 308 (Warning in debug/trace.c, during build)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=308

commit ec7c17bc6f54c2a28353d5b099e6501793eed8f8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:56 2009 +0000

    performance/stat-prefetch: checking for cache and creation if not present is made atomic.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 9f876873728bc605f68d386e454c922a5305184d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:54 2009 +0000

    performance/stat-prefetch: lookup path in xattrop if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 3fb8e1d67a7d2a4513fa96df726f557fb5aa3df5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:53 2009 +0000

    performance/stat-prefetch: implement sp_entrylk.
    
    - lookup on path should be sent in entrylk if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 94f24f06644b9e872f4b34f100017672b5d08978
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:52 2009 +0000

    performance/stat-prefetch: implement sp_inodelk.
    
    - path has to be looked up in inodelk if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit ebbe78de0281735f683d5414b34d1418e8c9d5b8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:50 2009 +0000

    performance/stat-prefetch: lookup path in removexattr if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit f86d713f8e60dbd6d80f25a05fb3a55acc6457d0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:49 2009 +0000

    performance/stat-prefetch: implement sp_getxattr.
    
    - path should be looked up in getxattr if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 4c83e0c25c39c90723a0c7ba6a706784b651704f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:48 2009 +0000

    performance/stat-prefetch: lookup path in setxattr if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 506a26985572949525cd8560d77a2fa13332d8bd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:46 2009 +0000

    performance/stat-prefetch: lookup path in opendir if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit d53db7415fd919b405818864aafa51b53aab7627
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:45 2009 +0000

    performance/stat-prefetch: lookup path in create if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit bbaf6e2d35841c2976855e09e3c744bc6c364821
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:43 2009 +0000

    performance/stat-prefetch: remove stat corresponding to oldloc->path from cache in sp_link.
    
    - ctime of oldloc->path will be changed on completion of link fop.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 7fcb479dc329d9931c0ec975ab8b87450d6d8b24
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:42 2009 +0000

    performance/stat-prefetch: lookup oldloc->path in link if it has not already been looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit aa8323817ebacf664b0e4c68996efa5847342bf8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:40 2009 +0000

    performance/stat-prefetch: lookup oldpath and newpath in rename if they've not already been looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 5cb21335e3f12815d3e60b93d5edaea8d4ba26da
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:38 2009 +0000

    performance/stat-prefetch: lookup path in symlink if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 153e2fd4f5fc35d23b3dad0cc147f4586b88823d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:36 2009 +0000

    performance/stat-prefetch: lookup path in rmdir if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 9857c10cd6b7b4497f8bc2d96aa559d1191f65d8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:35 2009 +0000

    performance/stat-prefetch: lookup path in unlink if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 19322c4a2a2c439a7c90dabe07cee07deb9dc79a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:33 2009 +0000

    performance/stat-prefetch: fix mkdir to unwind with proper number of arguments.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit be267e3449f84b35f749beec7c90e895a231b32c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:31 2009 +0000

    performance/stat-prefetch: lookup path in mkdir if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit d4f0250bc6db1a8462ed05e970e81f02c47673b4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:30 2009 +0000

    performance/stat-prefetch: lookup path in mknod if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 54990af07b8156bbe7d7686b3aa1e0bd2b7372c1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:29 2009 +0000

    peformance/stat-prefetch: lookup path in readlink if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 7a4c856af87c024ee8e9ff0164e26e48876380d5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:27 2009 +0000

    performance/stat-prefetch: implement sp_access
    
    - sp_access should send lookup on the path if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit b49ab8f21d69bf0ffb19f1837cf665a0d63ead7d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:26 2009 +0000

    performance/stat-prefetch: lookup path in truncate if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 063041b55c6375d8253aec4f2d191fb1a90de31a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:16 2009 +0000

    performance/stat-prefetch: lookup path in setattr if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 31a48a6b868249f01e8a1660469390b2d34969c0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:14 2009 +0000

    performance/stat-prefetch: implement sp_stat.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit f01de62f519c1cd110bf34a6cf585e8f8f88e4c2
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:12 2009 +0000

    performance/stat-prefetch: lookup path in checksum if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit f114e547b742eb321f7ac4746ba79605289fbe74
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:11 2009 +0000

    performance/stat-prefetch: lookup the path in open if it is not already looked up.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 8260e8c1ec061ea8fadc79695f5269781d543376
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:10 2009 +0000

    performance/stat-prefetch: implement procedure sp_process_inode_ctx.
    
    - this procedure processes inode_ctx to make decisions like whether the
        current procedure can continue (i.e., inode is already looked up),
        or the procedure has to initiate/wait for lookup on the path. It also
        sets up the frame->local and adds the stub corresponding to current fop
        if needed.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit f89f4c64af2d9253dea28504d9f27bf08b544bf0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:08 2009 +0000

    performance/stat-prefetch: use op_errno instead of errno to store error code.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 2dc9d11fe1c8aaeba972c6fd693de1f32e5e3f1a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:07 2009 +0000

    performance/stat-prefetch: Add support code to implement lookup-behind.
    
    - change sp_lookup and sp_lookup_cbk to support sending lookups when needed.
        lookups might need to be sent in fops like open, chmod, chown etc which
        operate on a path, since the actual lookup sent to stat-prefetch by its
        parent xlators is not propagated down the xlator tree if the path is
        cached.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 490edcd9f76726e5cc46bf9e7ddd69e496d32d7b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:05 2009 +0000

    performance/stat-prefetch: remove lookup-behind in sp_lookup.
    
    - lookup-behind should be done on-demand basis, in fops like open
        instead of in sp_lookup itself. This would reduce network traffic
        between client and server related to lookup, if the only use of
        lookup was to fetch stat structure.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 5c3bd66db8a911ca4da021d76237970c9eabd66c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:04 2009 +0000

    performance/stat-prefetch: optimizations to sp_lookup.
    
    - if stat cache cannot be found for a path in its parent inode and the path
        is a directory, we can get the cache from the inode corresponding to path
        and look for "." in that cache.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 78da899c5ceac63c424ad3d9e712b6a26abae7ba
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:02 2009 +0000

    performance/stat-prefetch: Add accounting of cache hits and misses.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit b9bfc46a9a26c356bd79a453c6daa77692f0a624
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:21:01 2009 +0000

    performance/stat-prefetch: change behaviour of sp_lookup when xattr_req is not NULL.
    
    - if the xattr_req is empty (fuse just creates an empty dictionary and
        sends along lookup) we can still use the cache prefetched during readdir,
        since we need not fill the reply dictionary.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit f5aa617d7cc4a48bb5e76fc7de763e9c3624e6b4
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:20:59 2009 +0000

    performance/stat-prefetch: change the cache to use rbtree based hashtable instead of list for caching dentries.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 59d4142ff1938e3b327fb81bee49402057ae1382
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 06:20:50 2009 +0000

    performance/stat-prefetch: fix memory leaks
    
    - sp_cache_get_inode uses fd_lookup which internally increases the refcount of
        fd by 1. This needs to be unrefed once we get the cache.
      - for directories, stat is stored in the inode context in sp_lookup_cbk.
        but, while doing so, no check was being done for the presence of context
        in inode, resulting in leak of memory equal to sizeof (struct stat) when
        multiple lookups happened on the directory.
      - path constructed in sp_readdir was not freed.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 3949b2828a78e4ecb95edb06f09fb9e7e3e5ce9b
Author: vinayak hegde <vinayak@gluster.com>
Date:   Thu Oct 8 23:35:57 2009 +0000

    debug/error-gen: Feature enhancement of error-gen translator
    
    In debug/error-gen translator 3-options are provided.
    failure - specifies the percentage failure in fops.
    error-no - specifies which error-no to be returned.
    enable - specifies which are the fops to be enabled for this translator.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 291 (feature enhancement of error-gen translator)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=291

commit d160d55c41913de26a43117b00fcab63746ce96d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Oct 9 00:05:43 2009 +0000

    performance/write-behind: Refining the check for fd_ctx in fds
    
    - An fd opened on a directory should not be considered bad if the fd context
        is not set since the context is set only for fds opened on files.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 260 (ls on booster VMP results in error: "File descriptor in bad state")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=260

commit c74e5ac0a26ad217edc2f6ba1ed4bb0511e49084
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Oct 8 05:59:49 2009 +0000

    libglusterfs/defaults: default_readdirp should call fops->readdirp instead of fops->readdir.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit adc495298c22fa3463cdd46a5e3def37878f28bb
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 8 06:31:33 2009 +0000

    performance/write-behind: Change STACK_UNWIND to STACK_UNWIND_STRICT.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit a310d0e6b0754c43c8b89ea5b78dcc4e8f2e0462
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Oct 8 05:48:21 2009 +0000

    cluster/dht: Change STACK_UNWIND to STACK_UNWIND_STRICT.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 1534a696daf25ddea67bd2bc8e2ba1993eb366c6
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Oct 7 13:12:36 2009 +0000

    Initialize local before any call to STACK_WIND to prevent a crash
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 304 (Write behind crashes when a chmod is issued)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=304

commit ef488e7cceea97c4e2750b463000a2b77fc82323
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Oct 7 12:55:54 2009 +0000

    assign client_readdirp to .readdirp in protocol/client & fix 2 other bugs in call_stub
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 305 (Readdirp crashes in client protocol)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=305

commit 6215731b42a4149e78fb56cb62c2f2dc571ea2a5
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Oct 7 06:43:44 2009 +0000

    mount/fuse: Handle FATTR_MODE flag properly.
    
    Handle the FATTR_MODE flag in fattr_to_gf_set_attr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 0b1197defa255ee533e568c9534bc6a5b5aadc29
Author: Vijay Bellur <vijay@gluster.com>
Date:   Mon Oct 5 23:59:13 2009 +0000

    Changed occurrences of Z Research to Gluster.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 5ea9f35a538e83ebc50fca81efecbcd8ddd9951b
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Oct 7 04:38:49 2009 +0000

    cluster/afr: Change STACK_UNWIND to STACK_UNWIND_STRICT.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit bb8ea22c3c936254dc4e3a3813f18b78d1aec6b4
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 5 09:25:33 2009 +0000

    mount/fuse: Don't send fsetattr if ATIME or MTIME needs to be changed.
    
    There is no "futimes" call. Hence, if either the FATTR_MTIME or FATTR_ATIME
    flag is set, don't send fsetattr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 296 (handle futimes correctly in FUSE)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=296

commit 29f81133a6cd95ebc9fac627a4fb0da73977f5a8
Author: Pavan Sondur <pavan@gluster.com>
Date:   Mon Oct 5 09:45:52 2009 +0000

    Removed remaining references to chmod, chown and utimens as part of setattr changes.
    
    Removed references to chmod, chown and utimes. Removed utimes references in AFR and writebehind.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit f3e46f2cb44e95c453bfa20c870dca6e42fc9a7a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Oct 5 07:42:02 2009 +0000

    core: Add rbtree based hash table
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 39243caeca3322801429afcef5094ea734438669
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Oct 5 07:42:01 2009 +0000

    mem-pool: Include stdlib for calloc()
    
    Doing so removes build warnings about calloc and free
    for files that use mem-pool but do not by themselves
    include stdlib.h, for eg., rbthash.c
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit d03e51668d5d0849d7acd7659a3e8028db85b089
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:07 2009 +0000

    libglusterfsclient: Port directory reading to readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 56bba06b2103aeadf33a7c7a5914f083f4d3b092
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:06 2009 +0000

    client: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 6968e06d007c57084414dfd433f005175b5ddc23
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:05 2009 +0000

    server: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 4b624979ce50a4fbdb34bc93241b6591d64b7f0a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:04 2009 +0000

    stat-prefetch: Port stat-prefetching to readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 2bcd6ffad9d9445b90627a219ccfff9535a22c6a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:03 2009 +0000

    io-threads: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit e1b3fa2194f0ec63b2206e081f7dc352d842ea53
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:02 2009 +0000

    trace: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 95b6af6c355dfd5f705fd152884d6a40c8676b2c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:01 2009 +0000

    io-stats: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit d4bd1b3945d6792f7f8ec05b1bb642adfc824aa6
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:08:00 2009 +0000

    error-gen: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 12947025dd2acd58b233d1c83efcab1038764189
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:07:59 2009 +0000

    unify: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit ee3b60524b49fc02d68c7ba219d8015a0d7c7a97
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:07:58 2009 +0000

    map: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit d3c3d0a8ddc97d7be64a2c2102fab67b8d5e81af
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:07:57 2009 +0000

    ha: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 512dcad823feb199d78f5b66a09bc404ccb899e8
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:07:56 2009 +0000

    distribute: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 02bced30690a5d298f262dce459bfecd001da2fe
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:07:55 2009 +0000

    afr: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 6b5a8b8536a943bd7f3241e1a08de934f7566169
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:07:54 2009 +0000

    posix: Support readdirp fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 55f55db6500835e95b324a2f28144c6a3dc55c62
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Oct 2 03:07:53 2009 +0000

    core: Separate readdirp and readdir fops
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 292 (Separate readdirp functionality from readdir fop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=292

commit 81cc40fee8b9cebcf5fc544c5d0c734fa7dfbb90
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Oct 6 06:45:04 2009 +0000

    storage/posix: Process "glusterfs.content" key in lookup only for regular files.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 301 (lookup should ignore ISDIR error when trying to get content)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=301

commit f719a641841a2bbd6f59945e5e32350cfe89f814
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 5 05:38:09 2009 +0000

    features/locks: Change STACK_UNWIND to STACK_UNWIND_STRICT.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 965b74d7d6faeebb17f580cefcadca15dece3b08
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 5 05:37:51 2009 +0000

    storage/posix: Change STACK_UNWIND to STACK_UNWIND_STRICT.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 97b564c708fbb44cf1ac512d7eaca701767120d5
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 5 05:37:31 2009 +0000

    libglusterfs: Add STACK_UNWIND_STRICT macro.
    
    STACK_UNWIND_STRICT (op, frame, this, op_ret, op_errno, ...)
    
    The "op" argument is the name of the fop (lookup, open, etc.).
    This macro makes sure that the number and type of arguments
    passed match those of the callback function for the fop.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 269 (Add a specialized STACK_UNWIND macro for each FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=269

commit 7e6c9643e69e1f8172e5be3564213d35332ae099
Author: vinayak hegde <vinayak@gluster.com>
Date:   Mon Oct 5 05:21:58 2009 +0000

    glusterfsd.c: Pipe is used during daemonization as ipc.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 117 (Wrong command line does not throw error)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=117

commit 8e0f5e7105c0d03b50a9342f4285a985b9cdb090
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Oct 5 04:01:36 2009 +0000

    cluster/afr: Initialize local->first_up_child in AFR_LOCAL_INIT.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 285 ("first up child" can change during a transaction)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=285

commit b441730b5b54fcd9355bef42bd0f45a4147212e4
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:16 2009 +0000

    libglusterfsclient: Remove redundant fchown and fchmod
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 23d896068f98538954772dcd90a112b6cac17d63
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:15 2009 +0000

    libglusterfsclient: Use fsetattr for fchown
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 1640178a1004cb5a43cdf2e5fb375807812f367f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:14 2009 +0000

    libglusterfsclient: Use fsetattr for fchmod
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 507a4aa75d295f6fa7db04885b65aec0f497b21e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:13 2009 +0000

    libglusterfsclient: Support fsetattr fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 3dc513b108df276b974c0ddc47f7ac9bff907448
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:12 2009 +0000

    libglusterfsclient: Remove redundant chown code
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 0778d42be1a463f643994592073837b59d33bd76
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:11 2009 +0000

    libglusterfsclient: Remove redundant chmod code
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 52193c0a79cb39b7456a57ff6470000dd39d6420
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:10 2009 +0000

    libglusterfsclient: Remove redundant utimens code
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 46c23afc98e3f0c8063c4baada7baa3dd3134727
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:09 2009 +0000

    libglusterfsclient: Use setattr for utime
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit a2013f6bc70832c7cbcc1cabbb4d74725c0adac7
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:08 2009 +0000

    libglusterfsclient: Use setattr for utimes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit bdeb23cac1edbc7d88978b3676461db462d89c53
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:07 2009 +0000

    libglusterfsclient: Use setattr for chown
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit b017bcb852e3549ba7dc1dc6d23e157178bb1305
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:06 2009 +0000

    libglusterfsclient: Use setattr for chmod
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 709d46bcdbd006fa92c9d15e7c02ba7bff86685b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:05 2009 +0000

    libglusterfsclient: Support setattr fop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit 25217d43f9786b71de4d86cae122403f2cbaf1e5
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:04 2009 +0000

    distribute: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 398de05aeba82ddfa055e8696521f3d5a4cbabe5
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:03 2009 +0000

    ha: Handle memory allocation failures
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 3e25f229787c1b53ab61333a41345a35c070e089
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:02 2009 +0000

    ha: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 5c61f94b00e4fcc8199126f03816896e015eb511
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:01 2009 +0000

    symlink-cache: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 7c1bdb3aad6063f69338d92490cd4d11d4d578f1
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:59:00 2009 +0000

    io-threads: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 1e0b3920dc0bcb8d15586adceacacedba75b17ab
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:59 2009 +0000

    read-ahead: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit b342852f9d41c8274cdc808c1a481487b44a7ab9
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:58 2009 +0000

    write-behind: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit cc709f8731b81faceab00b6ce18cf129e8ec8e3e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:57 2009 +0000

    filter: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit b02cf677ff6ec178f35e4300bb83b130c1834b05
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:56 2009 +0000

    stripe: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit ef07ef24562d3fe4355af849d2a50a16b8fb6db7
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:55 2009 +0000

    error-gen: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 5654dc9f93abe195fd4a1d3ed4a4971710db06e4
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:54 2009 +0000

    locks: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit ecf1ea918f206a23c2c74a792ee61f4c5ac799c2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:53 2009 +0000

    io-stats: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 2bc402003cd4526f74e4b543a717aafb52a8b9ed
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:52 2009 +0000

    trace: NFs-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 26907996756cc17f1a7df30b6f8ef130b7140924
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:51 2009 +0000

    client: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit b5c4ad4cbb7e313f66d22148e93b58c486e32d1b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:50 2009 +0000

    server: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 9710782e8a42712dfbbea46b50ac3681e57a860d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:49 2009 +0000

    posix: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit a27e706e3105dc363bcbe3c0e3c91979cc6c89a0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:48 2009 +0000

    unify: NFS-friendly logic changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit e11d66c8d6dea72d02f9bcdbf65c67bd5c60b5cc
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:47 2009 +0000

    Global: NFS-friendly prototype changes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 145 (NFSv3 related additions to 2.1 task list)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=145

commit 186a86f342625a9dce53fe537f8237c6099d5c54
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Oct 1 06:58:46 2009 +0000

    Global: Introduce setattr and fsetattr fops
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 146 (Add setattr FOP)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=146

commit dca4b2a23cb55e1e15fb393e7cbfd39b59280c9c
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 30 05:48:22 2009 +0000

    Changes to use this->name while using logging instead of explicitly mentioning posix-locks.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 290 (Clean up a calls to gf_log in locks' code)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=290

commit 820b88c3389b59dce190e6846703c267d7113a63
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 30 05:47:49 2009 +0000

    Make changes such that glusterfs builds with Werror and fix LONG_LONG_MAX definition.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 289 (glusterfs does not build with Werror)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=289

commit 572fb95127a37c3bf45a60083ad247064d634085
Author: Pavan Sondur <pavan@gluster.com>
Date:   Tue Sep 29 11:03:54 2009 +0000

    Check if path is valid after call to inode_path before accessing it.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 287 (call to inode_path can result in a segfault)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=287

commit 41c32c84892365c5230a5e61addc44dbfcd2e5cf
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Sep 28 20:58:26 2009 +0000

    cluster/afr: dir-write: Fix inode number handling.
    
    create, mkdir, symlink, mknod: Prefer to return itransform'd inode number
    from the first_up_child. If not, fall back on any other child that returned
    succcess.
    
    link, rename: Return the same inode number that
    was passed as part of loc_t.
    
    Also adds a new member to afr_local_t, local->first_up_child
    which is initialized at the start of the transaction. This
    fixes the race where a subvolume might go down during the transaction
    and thus have the first_up_child change.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 285 ("first up child" can change during a transaction)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=285

commit 03b5a87b2f4d641c798440923b255ca30a13bf47
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 25 02:55:12 2009 +0000

    libglusterfsclient: don't destroy the iobuf pool during fini.
    
    - some of the iobufs in pool will be cached by io-cache and hence refcount
        will not be zero. Hence the assertion of ref being zero in
        __iobuf_arena_destroy fails. Commenting out iobuf_pool_destroy during fini, till
        we introduce proper cleanup in all translators, thereby allowing io-cache
        to release the buffers it has held.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 283 (booster aborts complaining the refcount of iobuf is not zero during glusterfs_umount_all.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=283

commit 009fc3e3e921517a7b986f7b5a73676f43edb358
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 25 02:55:44 2009 +0000

    libglusterfsclient: traverse the vmplist during fini only if any entries are mounted.
    
    - the vmplist.list is inited only during mounting of first entry. Hence doing
        a list traversal when no vmpentries are present, results in a segfault.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 282 (segfault of applications using booster observed when the application does not mount any vmps.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=282

commit 5816d5dcc5e564017c101acb65e496a8d631b4eb
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 24 04:18:18 2009 +0000

    cluster/afr: Fix memory leak in "diff" self-heal algorithm.
    
    FREE sh->private after diff self-heal is done.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 281 (memory leak in "diff" self heal algorithm)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=281

commit 2317913ae5556fe402828d97f7da761124c15ba2
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 24 04:30:06 2009 +0000

    glusterfsd/main: Do a sem_post only if running in daemon mode.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 4 (mount --bind fails if run immediately after mounting GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=4

commit 551782dfd54cb554633de526a0c4e188776c5e78
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 00:49:52 2009 +0000

    booster: Cleanup booster_cleanup and register for atexit
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 279 (File written with booster results in self-heal after dd exits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=279

commit d528f134094d86ec7344875160a41e0ce4ebc1b0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 00:49:51 2009 +0000

    libglusterfsclient: Support TRACE loglevel
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 210 (libglusterfsclient: Enhance logging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=210

commit cd13c7e7368ec60ec9b6559e2eced41bcc10d6bc
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 00:49:50 2009 +0000

    libglusterfsclient: Wait for all call pools to be destroyed
    
    This ensures that the process using libglusterfsclient does
    not exit before all the fops and calls have been replied to.
    It helps to ensure that the backends are in a sane state when
    the program exits.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 279 (File written with booster results in self-heal after dd exits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=279

commit 881e5f243d3c56dcaf54595378beb91c45f1ded5
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 00:49:49 2009 +0000

    libglusterfsclient: Clean up fini and umount code paths
    
    This patch cleans up the umount and fini paths in preparation
    to support waiting for unwind of all pending call frames.
    
    Two misc fixes are:
    1. Fix to avoid deadlock in _libgf_umount by
    using _libgf_vmp_search_entry instead of
    libgf_vmp_search_exact_entry since the latter tries to take a
    lock already help by _libgf_umount.
    
    2. Avoid a crash in _libgf_umount by deleting the vmp
    entry from the list before it gets freed.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 279 (File written with booster results in self-heal after dd exits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=279

commit 7398c0a694343c15292f076dbb0ae8508004d003
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 00:49:48 2009 +0000

    iobuf, logging: Expose existing functions as required
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 279 (File written with booster results in self-heal after dd exits)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=279

commit 5d7db5410fc4a96268dcacf759a3b5ab79c2c28e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 00:49:47 2009 +0000

    libglusterfsclient: Reduce logging aggressiveness to TRACE
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 210 (libglusterfsclient: Enhance logging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=210

commit 41cd359539cf0b59c4435cbecd38b71bab796449
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 00:49:46 2009 +0000

    booster: Reduce logging aggressiveness to TRACE
    
    Internal users feel the amount of logging brought in
    due to a previous logging enhancement patch is a bit too
    aggressive for DEBUG, so this changes it to TRACE.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 210 (libglusterfsclient: Enhance logging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=210

commit 03764d0d308b46ebfa53d21df1d49a549c459e64
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Sep 24 01:01:00 2009 +0000

    libglusterfsclient: Re-validate root inode on every path resolution
    
    If the root inode's is outdated, send a revalidate on it.
    A revalidate on root inode also reduces the window in which an
    op will fail over distribute because the layout of the root
    directory did not  get constructed when we sent the lookup on
    root in glusterfs_init. That can happen when not all children of a
    distribute volume were up at the time of glusterfs_init.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 256 (revalidates should be sent on '/' in libglusterfsclient.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=256

commit c72b902afce2b977c8d0b9b1a0463f615365d825
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 24 00:59:04 2009 +0000

    performance/write-behind: Add a NULL check for request->stub before checking request->stub->fop.
    
    - for non-write wind requests, the request structure outlives the stub.
        The call stub is destroyed when stack is wound but request is destroyed
        only when the reply has come.
        (for writes, both stub and request are destroyed when refcount becomes 0,
         which happens only when the write operation is stack unwound and a reply
         for the write operation has come from underlying translators, for non-write
         unwind requests the request is first destroyed before resuming the stub).
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 280 (simple stripe, with write-behind set up, when dbench is run client crashes.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=280

commit 155ffe5c5a52a8f52978dc68509e5912b5db7bc4
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Sep 22 07:53:14 2009 +0000

    fuse: emit a flush from release if we didn't get an adjacent FLUSH message from the kernel
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 223 (flush not sent)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=223

commit 334981987010f895594031f8363f481eb7ae6416
Author: Pavan Vilas Sondur <pavan@dev.gluster.com>
Date:   Wed Sep 23 06:03:25 2009 +0000

    Implemented inodelks with support for domains.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit 231196910d9d36af9546ddc511b26da5628b3ab8
Author: Pavan Vilas Sondur <pavan@dev.gluster.com>
Date:   Wed Sep 23 06:02:55 2009 +0000

    Implemented entry locks and support for domains.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit 435b28132b8f276681d19ae14fa988d26a16f659
Author: Pavan Vilas Sondur <pavan@dev.gluster.com>
Date:   Wed Sep 23 06:01:10 2009 +0000

    Removed internal.c and old domain definition in locks.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 222 (Enhance Internal locks to support multilple domains and rewrite inodelks)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=222

commit 5535110f8e760eecb12140aafd70174e7d7bfcda
Author: vinayak hegde <vinayak@gluster.com>
Date:   Wed Sep 23 06:19:21 2009 +0000

    Changes for custom daemon function.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 4 (mount --bind fails if run immediately after mounting GlusterFS)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=4

commit 7df1671b5af320f2c5aaeadfccda2e64d2ff404e
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Tue Aug 11 13:21:11 2009 +0000

    mount.glusterfs had a problem understanding when "volfile" was given as one of the mount arguments.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 204 (mount.glusterfs mounts to incorrect mount point)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=204

commit 044679501c13024950751cbebe8fd47cc73e8bf9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 23 00:22:17 2009 +0000

    performance/write-behind: store currently aggregated data size in wb_file
    
    - this helps us to not traverse the request list whenever we need currently
        aggregated data in the queue
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit 3d1f342671bb11159569fd2a4f20b2c9007e7b55
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 23 00:21:51 2009 +0000

    performance/write-behind: store the current window size in wb_file.
    
    - this would increase the performance since we don't have to traverse the
        request list every time we need the current window size.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit 2f1261c194d8735e50dfa3846b3cd23654ed7391
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 23 00:21:31 2009 +0000

    performance/write-behind: reduce usage of iov_length.
    
    - request structure now holds a member write_size which is initialised at the
        time of request creation and used later.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit 35f96c039e8961e48af46af43b6ecf7a335feb15
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:32 2009 +0000

    cluster/afr: Add new option "data-self-heal-algorithm"
    
    option: data-self-heal-algorithm type: string default: "full"
    
    This option allows the user to specify the algorithm to
    be used for data self-heal. Currently supported values
    are "full" and "diff".
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit d2b7e65ec0c35c4ee16f28f449553d90fb88fa6a
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:31 2009 +0000

    cluster/afr: Add the "diff" self-heal algorithm.
    
    The "diff" self-heal algorithm works as follows:
    
      For each block:
        Compute MD5 checksum on source and all sinks
        If checksum on a sink differs from source:
          Read block from source and write to sinks
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8c224de82b9b3e75f2dd9c264d5d3726dd1ef379
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:30 2009 +0000

    cluster/afr: Make the self-heal algorithm pluggable.
    
    Abstract the read/write loop part of data self-heal. This
    patch has support for the "full" (i.e., read and write entire
    file) algorithm.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 356449c0b39d600a16b195df30d0fc37693575f8
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:29 2009 +0000

    cluster/afr: Open source and sinks in read/write mode during self-heal.
    
    Since a self-heal algorithm (e.g., rsync) might want to both read
    and write from both the source and sink files, open them as O_RDWR.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a4d729c7dccd5cdf72f640e39564103412d867ec
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:28 2009 +0000

    protocol/server: Implement rchecksum.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4f9fa11a788dc367f89ca47544f42323c0e73a14
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:27 2009 +0000

    protocol/client: Implement rchecksum.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 45707a5ae95a9154a57fb7bf56f7cd64e2c40896
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:26 2009 +0000

    storage/posix: Implement rchecksum.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit faf97734112ebe11d8a411351d9f23b528b9d616
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:25 2009 +0000

    libglusterfs: Add RCHECKSUM fop.
    
    rchecksum (fd, offset, len): Calculates both the weak and strong
    checksums for a block of {len} bytes at {offset} in {fd}.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 239d2cbdb0a4c32df9f21de8385e2c466b934178
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 17 05:56:24 2009 +0000

    libglusterfs: Add checksum functions.
    
    gf_rsync_weak_checksum:   Calculates a simple 32-bit checksum.
    gf_rsync_strong_checksum: Calculates the MD5 checksum.
    
    The strong checksum function makes use of Christophe Devine's
    MD5 implementation (adapted from the rsync source code,
    version 3.0.6. <http://www.samba.org/ftp/rsync/>).
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 0def744b2e66e81ac37532b26716e83d3b8bc9dd
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 22 00:22:12 2009 +0000

    booster: implement F_DUPFD command in fcntl.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 277 (running dd on booster returns EINVAL)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=277

commit 8301f05f77aa08f04e249c19576a7c111e586109
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 22 01:39:10 2009 +0000

    performance/write-behind: add option "enable-trickling-writes".
    
    - With this option enabled, writes are stack-wound even though not enough
        data is aggregated, provided there are no write-requests which are
        stack-wound but reply is yet to come. The reason behind this option
        is to make use of the network, which is relatively free (with no writes
        or replies in transit). However, with non-standard block-sizes of writes
        the performance can actually degrade. Hence making this configurable.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit 35d1cabfd1266609ec22f11e5e4ddba13f0ffc56
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 22 01:38:37 2009 +0000

    performance/write-behind: reduce traversal of request list during wb_mark_winds.
    
    - move all the decision making code to __wb_can_wind.
      - don't continue traversing the request list, once we know any of the
        following conditions are true:
        * requests other than write are present in queue.
        * writes are happening at non-contiguous offsets.
        * there are no write requests, which are wound to server but not yet
          received the reply.
        * enough data is aggregated for writing.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit db33e097111ca76f487f087d494984d45d4b3b64
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 22 01:38:50 2009 +0000

    performance/write-behind: reduce list-traversal during wb_mark_unwinds
    
    - don't traverse entire request list to get the window-size, instead break when current
        window size becomes greater than configured limit.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit 32a6898678686df1b2c82a37e548170ba5c3512b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 22 01:38:25 2009 +0000

    performance/write-behind: remove redundant traversal of write-requests in the wind list in wb_ sync.
    
    - no need of getting the total_count of number of requests in the list.
        Even if there is a single request, we need to sync it.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit 8a0d85eb936f9483a5d23d67cf5989351d5f86d7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 22 01:38:12 2009 +0000

    performance/write-behind: Aggregate adjacent contiguous write-buffers into single iobuf.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit ecb8f4dfce0bfdba8d14532231a7596a73def38e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 22 01:37:59 2009 +0000

    performance/write-behind: fine-tune logic of wb_mark_winds
    
    - remove wb_mark_wind_aggregegate_size_aware, since wb_mark_wind_all does
        the same work (with check for whether current aggregated data size is
        greater than the configured limit before calling it). Moreover,
        wb_mark_wind_aggregate_size_aware called __wb_get_aggregate_size
        redundantly, thereby reducing the performance, since for small
        sized large number of writes, traversing the list of requests takes
        significant amount of time.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 276 (write behind needs to be optimized.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=276

commit fd0b40a2f3e7e1c56b742c9ae081785811030a3c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Sep 21 05:32:42 2009 +0000

    libglusterfsclient: Fix build warnings
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 275 (libglusterfsclient: Generic build failure bug for libglusterfsclient and booster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=275

commit 6f7c6c102a418553a109e1b2bb5b1f87578bab58
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Sep 21 05:32:32 2009 +0000

    booster: Fix build warnings
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 275 (libglusterfsclient: Generic build failure bug for libglusterfsclient and booster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=275

commit 1fc259cb73cb199052519f548dfbb1b83829b28f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Sep 21 05:19:47 2009 +0000

    storage/posix: Update nr_files after system call succeeds.
    
    In posix_open(), posix_create(), and posix_close(), update
    stats->nr_files only after the FOP has succeeded.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 248 (Updating stats in posix is incorrect)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=248

commit 578e42399fa86f15dffffd5d35f96f3a248d651d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 18 05:53:52 2009 +0000

    performance/quick-read: refine logic of qr_readv.
    
    - An extra vector was being allocated when the number of bytes being read
        from cache were equal to the iobuf size.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 274 (Memory corruption in Apache running on booster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=274

commit c98c65c940a8120982aeaf5f15d0522a002c5b80
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 18 05:48:04 2009 +0000

    performance/quick-read: optimizations to lookup
    
    - qr_lookup not to send request for file-content if the cache is already
        present during revalidates.
      - flush the cache in qr_lookup_cbk if the cache is not in sync with the file.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 273 (Code review and optimize quick-read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=273

commit 4a272e7ba02487b2596814035a266974d57e6b04
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 18 05:48:13 2009 +0000

    performance/quick-read: make a comment more explicit.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 273 (Code review and optimize quick-read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=273

commit 6f692f0f39f9fe32936135947c91629044ae4d2c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 18 05:47:56 2009 +0000

    performance/quick-read: checking for qr_file in inode-context and creating if not present should be atomic.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 273 (Code review and optimize quick-read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=273

commit 5de57e490c8e3c2764777da6bf750a4f5e23f2b3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 18 05:47:43 2009 +0000

    performance/quick-read: refine the logic in qr_lookup.
    
    - a new size has to be set in xattr_req only
        if (quick-read is configured with a maximum file size limit
            && ((xattr_req does not have a request key for getting content)
                 || (the size requested in xattr_req is not equal to configured
                     size in quick-read)))
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 273 (Code review and optimize quick-read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=273

commit cb596d7e847543906c62eb3b07c88c60acac15ae
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 17 15:08:21 2009 +0000

    protocol/client: access glusterfs context from the ctx member of xlator object
    
    - A global context pointer cannot be used with libglusterfsclient, since
        there can be many contexts in a single process.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 271 (applications using booster protocol/client crash in client_setvolume_cbk.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=271

commit f0f547f79792af9fe8228f2028bd1dd30d976e68
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 17 00:08:26 2009 +0000

    performance/write-behind: check for the presence of context only in fds not opened on directories.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 260 (ls on booster VMP results in error: "File descriptor in bad state")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=260

commit bad3de155a3a910c6665a39555aeb823803635c9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 16 12:33:21 2009 +0000

    client-protocol: fix race-condition encountered while accessing fdctx
    
    - In protocol/client, fdctx is accessed by two sets of procedures,
      protocol_client_mark_fd_bad falls in one set whereas the other set consists of
      all fops which receive fd as an argument. The way these fdctxs are got is
      different in these two sets. While in the former set, fdctx is accessed
      through conf->saved_fds, which is a list of fdctxs of fds representing
      opened/created files. In the latter set, fdctxs are got directly from fd
      through fd_ctx_get(). Now there can be race conditions between two threads
      executing one procedure from these two sets. As an example let us consider
      following scenario:
    
      A flush operation is timed out and polling thread executing
      protocol_client_mark_fd_bad, fuse thread executing client_release. This can
      happen because, immediately a reply for flush is written to fuse, a release on
      the same fd can be sent to glusterfs and the polling thread still might be
      doing cleanup. Consider following set of events:
    
      1. fuse thread does fd_ctx_get (fd).
      2. polling thread gets the same fdctx but through conf->saved_fds.
      3. Now both threads go ahead and does list_del (fdctx) and eventually free
         fdctx.
    
      In other situations the same set events might occur and the threads
      executing fops other than flush in the second set might be accessing a
      fdctx freed in protocol_client_mark_fd_bad.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 127 (race-condition in accessing fdctx in protocol/client)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=127

commit c55a0a287b18ace123964e017c759947a5fbac2f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Fri Sep 11 07:42:44 2009 +0000

    performance/quick-read: access glusterfs_ctx from xlator instead of using glusterfs_get_ctx
    
    - since glusterfs_get_ctx gets the global context pointer, there can be
        problems in a multithreaded application running on libglusterfsclient
        doing multiple glusterfs_inits. Hence use context specific to the
        current xlator tree stored in each xlator object.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 240 (segmentation fault in qr_readv)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=240

commit a767c08c0e92e2e8caf4667d97aa5e5c3a13efb0
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed Sep 16 08:53:33 2009 +0000

    Add iot_fxattrop to io-threads
    
    It was already implemented but not set to .fxattrop
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 267 (Add fxattrop to iothreads)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=267

commit 9fd8f212bc1f6031b9ad7eaaf014d39916881947
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 15 04:47:50 2009 +0000

    Dumop inodectx added
    
    Added dumpop inodectx.
    Support for dumop inodectx added in dht, locks and client-protocol.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit dcfc4bdd5962ad18665d9ad3f3309884c941845e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 15 04:46:44 2009 +0000

    Changed prototype for inode_table_dump() and inode_dump().
    
    Changed prototype for inode_table_dump() and inode_dump()
    Added support for dumpop inode in mount/fuse and protocol/server
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit 5480b6eca96a8da4b159783a19f2ed5c2f640769
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 15 04:45:08 2009 +0000

    protocol/client: Support for dumpop priv.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit b542a8e5323fad46ce4e5f8921c906a58cff91d2
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 15 04:44:41 2009 +0000

    mount/fuse: Support for dumpop priv.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit db3d9ff328a9ce65db452d628f33c3151e131d5e
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 15 04:43:48 2009 +0000

    cluster/dht: Support for dumpop priv.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit fd9c608193b3318a543f25f75af7b888d85c4405
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 15 04:43:29 2009 +0000

    libglusterfs:Acquire lock before accessing fdtable contents during statedump.
    
    Hold lock while dumping fdtable.
    Dump only inode ino instead of the complete inode.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit 58e6643e036bda21f686955d779bb95ac513ab62
Author: Vijay Bellur <vijay@gluster.com>
Date:   Tue Sep 15 04:42:09 2009 +0000

    glusterfsd: Removing conditional compilation for SIGUSR1 handler.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit 34a7a97b3be80fa8af7d285211ab575a4c00ea79
Author: Anand Avati <avati@gluster.com>
Date:   Wed Sep 16 05:43:01 2009 +0000

    io-cache: fix table->max_pri to 1 as the lowest priority
    
    patch http://patches.gluster.com/patch/1319/ breaks when no priority
    is mentioned in the config. the patch makes ioc_get_priority() return
    1 as the value when no priority is given, but ioc_get_priority_list()
    was still returning 0 as the max_pri (maximum priority) which would
    result in lru list heads not getting initialized
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 261 (support for disabling caching of certain files)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=261

commit 47b340a0d499d5f9364f763e5794a433be609e17
Author: Vinayak Hegde <vinayak@gluster.com>
Date:   Wed Sep 16 02:37:19 2009 +0000

    cluster/stripe, when dbench is run, client crashes because in stripe.c priv is dreferenced without initialising.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 266 (In stripe client crashes after some time when disk space is full)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=266

commit e16fc897aeece7598da195bb9bd050e352ff31ec
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 15 08:06:56 2009 +0000

    booster: use __REDIRECT macro to prevent creat being renamed to creat64.
    
    - nm on libglusterfs-booster.so shows only creat64 defined but not creat. This
       behavior is observed due to following reasons.
    
       1. Booster is compiled with _FILE_OFFSET_BITS=64.
       2. fcntl.h when included with _FILE_OFFSET_BITS=64 defined, renames all
       occurences of creat to creat64 in the source code from the point of
       #include <fcntl.h>.
    
       fcntl.h should be included since booster.c uses many of the macros defined in
       that header and glusterfs (booster in turn) has to be compiled with
       _FILE_OFFSET_BITS=64 since glusterfs uses datatypes (off_t, stat etc) whose
       sizes vary depending on whether this macro is defined or not. Basically, this
       macro should be defined to provide portability across 32 and 64 bit
       architectures.
    
       The correct fix is to make glusterfs to use datatypes big enough to hold 64 bit
       variants as well as 32 bit variants (like int64_t replacing off_t) and not to
       define _FILE_OFFSET_BITS=64 at all.
    
       As a temporary work around,
       1. we can implement creat functionality in a function with different name, say
       booster_false_creat
       2. rename this function to creat using __REDIRECT macro. since this renaming
       happens after renaming of creat to creat64 (from the first __REDIRECT macro
       in fcntl.h), we will end up with creat symbol being defined in
       libglusterfs-booster.so
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 264 (creat is not resolved properly to the symbol defined in booster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=264

commit 3508a2d237cee98eb5c890011b569a1820b57f5c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 15 08:07:30 2009 +0000

    libglusterfsclient: NULL terminate the vmp entry during vmp_entry_init.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 263 (files are not resolved to glusterfs when vmp is not terminated with a '/'.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=263

commit 7bc96160b977345bda80c09e212d9d9c80243e7f
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 15 08:07:15 2009 +0000

    booster: use appropriate conversion specifier during logging in close.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 262 (crash in booster close due to invalid conversion specifier during logging.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=262

commit 8719f88fc85051b706c0fbf2904ace04435b2b05
Author: Stephan von Krawczynski <skraw@ithnet.com>
Date:   Mon Sep 14 05:59:55 2009 +0000

    2.0.6 patch for io-cache pattern-matched non-caching
    
    Hello all,
    
    here is a small feature patch. Its intention is to give the user more control
    over the files performance/io-cache really caches. If the user knows exactly
    which files should be cached and which shouldn't there is currently no way to
    tell glusterfs _not_ to cache certain pattern. This patch allows you to
    disable caching by setting the priority of a pattern to "0". If you do not
    give any priority option it works just like before and caches everything.
    Honestly I am not totally sure that disabling caching works the way we did it,
    please comment.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 261 (support for disabling caching of certain files)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=261

commit ece4e80b2d2326aa5fadc46c866947c9644622a7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 15 01:15:14 2009 +0000

    storage/posix: transform inode number in stat structure
    
    - when export directory is configured to span across multiple mountpoints,
        the inode number has to be transformed in order to make it unique.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 254 (storage/posix has to do inode number transformation wherever it unwinds with a stat structure)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=254

commit a5f0b3d7d1b23053ce9327be91323e92ce554b32
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Sep 15 01:03:56 2009 +0000

    extras: Add LD_PRELOAD test tool
    
    This tool allows us to check the sanity of the LD_PRELOAD
    mechanism so that we can be sure that an application's syscalls
    will be redirected into booster when that library is LD_PRELOADed.
    
    In case of failed syscalls, this tool should be run first
    to see if the calls are redirected as required.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 251 (Improve booster debugging through ld-preload testing tool)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=251

commit ad33df39dec4850c249c453822a99b3038b41389
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 15 00:33:30 2009 +0000

    transport/ib-verbs: initialize fini member of new-transports created during accepting client connections.
    
    - This bug used to cause a memory leak of 2 * sizeof(ib_verbs_private_t) for each new client connection.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 259 (Memory leak on server side when there are large number of disconnections from clients)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=259

commit e73e7afe5630894faa7a2829969cd16ea99e3c71
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 10 07:18:10 2009 +0000

    libglusterfsclient: Wait for time ample enough for all the children of distribute to initialize before sending lookup on '/'.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 255 (libglusterfsclient should wait till all the children of distribute are initialized before sending first lookup on '/')
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=255

commit 31f0f48130fb68908413e710d960c5d7c6476b45
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 9 12:15:11 2009 +0000

    protocol/server: server_stub_resume should check for failure of lookup when oldloc.parent is NULL.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 215 (crash on ib-verbs in 2.0.6-rc4)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=215

commit aedc8ae261095530e334788afb7191fa3a92e710
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 9 00:39:13 2009 +0000

    booster: Fix fd_t leak in pread64
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 174 (booster: fd_ts, they are a leakin)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=174

commit 6aff97e9698918af6d5e479b0240610d40cbe344
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 9 00:39:12 2009 +0000

    libglusterfsclient: Fix incorrect NULL check for fd
    
    We should check fdctx instead.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 253 (Global bug for libglusterfsclient NULL checks and CALLOC handling fixes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=253

commit 19f3591e4ac291d48252849e03afd2ac77205316
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 9 00:39:11 2009 +0000

    libglusterfsclient: Handle CALLOC failure in libgf_client_lookup
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 253 (Global bug for libglusterfsclient NULL checks and CALLOC handling fixes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=253

commit bc94b7e77fffcbcde8f838cae8fee552d5bd1189
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 9 00:39:10 2009 +0000

    libglusterfsclient: Handle CALLOC failure in libgf_init_vmpentry
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 253 (Global bug for libglusterfsclient NULL checks and CALLOC handling fixes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=253

commit 226c228ff8effd6cc5edcb3326907b1faf69eaea
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Sep 9 00:39:09 2009 +0000

    libglusterfsclient: Add inode_ctx NULL check during iattr cache validation
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 253 (Global bug for libglusterfsclient NULL checks and CALLOC handling fixes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=253

commit fd418ecf5d1eb4d3b65cff0890f8897592f2e9c8
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Sep 8 23:39:35 2009 +0000

    libglusterfsclient: Enhance logging
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 210 (libglusterfsclient: Enhance logging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=210

commit c4feaddee1120985422346eb0ffdfb62c796ad1b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Sep 8 23:39:13 2009 +0000

    booster: Enhance booster logging
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 210 (libglusterfsclient: Enhance logging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=210

commit b1cb5fce13eb1a31e694f0fcb81002d48455b750
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Sep 8 06:08:00 2009 +0000

    mount/fuse: Set d_type in readdir_cbk using the stat buf for the entry.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 207 ([ glusterfs 2.0.6rc4 ] - "ls --color" takes time)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=207

commit b1246773d17fadf93abb54c2fd504b3fc31944a9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Sep 8 05:06:22 2009 +0000

    cluster/afr: Check op_ret in afr_getxattr_cbk before accessing dict
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 250 (Crash in replicate getxattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=250

commit 1eb3fd72b13353fdb93dd0773d9da7aafccdde6b
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Sep 3 09:44:34 2009 +0000

    cluster/afr: Do not try to self-heal "/"
    
    If the root directory does not exist on a subvolume,
    don't try to create it.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 28 (Deleting a backend export directory in an AFR setup can cause a segfault while trying to self heal)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=28

commit 5ce1007f3b9a5234caa5b8a8c168c6b673d37f7e
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 3 04:48:14 2009 +0000

    performance/write-behind: hold locks when accessing members of wb_file.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 243 (Hold locks when accessing members of wb_file_t.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=243

commit bdec7d133963bb94528bfbf5c47dd1eb08bf4b35
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 2 04:54:23 2009 +0000

    performance/write-behind: communicate back the errors in writes to servers, in the next immediate writes from application.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 242 (If any of the writes fail, write-behind should not wait till the fd is closed for reporting errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=242

commit c7f757aea81e65980c68b4293836097ce595b5b3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Sep 2 01:12:39 2009 +0000

    libglusterfsclient: handle intermediate path components which are symlinks properly in glusterfs_glh_realpath.
    
    - while building the realpath, if the intermediate path happens to be a
        symbolic link, the content of link was being appended at dirname (path),
        instead of appending to intermediate path.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 237 (If any of the path component other than the last one, happens to be a symbolic link glusterfs_glh_realpath does not construct correct path.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=237

commit 6f1a9007f4876d46bd2d67e67312c24771d82bf5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 1 00:34:02 2009 +0000

    libglusterfsclient: handle paths terminating with '/' properly in libgf_trim_to_prev_dir.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 236 (Stack overflow due to infinite recursion in glusterfs_glh_realpath)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=236

commit 8d696f317ef06e045de380d4408b814a3214ced7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Sep 3 13:42:04 2009 +0000

    libglusterfsclient: handle failures in glusterfs_glh_realpath.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 235 (Handle failures in glusterfs_glh_realpath appropriately)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=235

commit ea8a20f3e68d5ccade465b60d98030c0c1bb4426
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 1 00:19:57 2009 +0000

    libglusterfsclient: check for memory allocation failure in glusterfs_glh_realpath.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 235 (Handle failures in glusterfs_glh_realpath appropriately)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=235

commit b27afdea5d8c594e160a099e2dd814fa33529276
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 1 03:52:20 2009 +0000

    libglusterfsclient: handle symlinks properly in glusterfs_glh_opendir.
    
    - exclude symbolic links from set of filetypes to which ENOTDIR is returned,
        since a symbolic link can point to a directory.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 234 (Apache-2.2 on booster returns HTTP_FORBIDDEN for a directory which is present)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=234

commit 342100dac9d0e01039b8cd8a0da4426b70d27060
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Tue Sep 1 00:00:44 2009 +0000

    libglusterfsclient: fix to the way symbolic links are handled in glusterfs_glh_realpath.
    
    - don't assume the content returned by readlink while constructing realpath
        of a symbolic link to contain vmp as part of the path. This is necessary in
        case of symbolic links which contain relative paths as targets.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 233 (Crash in Apache running on booster when a client tries to access a symbolic link)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=233

commit 6cd8070af4c83cca9f3f7685a2a04bcb95059dd1
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 31 22:53:33 2009 +0000

    performance/quick-read: if open fails during cache validation, don't continue validation process.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 232 (Quick-read: if open fails during cache validation, don't continue validation process.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=232

commit d6bc71ccb3a5265b01d188497213d797d7217c3d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 31 22:52:34 2009 +0000

    performance/quick-read: Fix access of freed memory in qr_open_cbk.
    
    - It may so happen that current frame might be unwound and
        local might be freed when waiting operations are resumed.
        Hence store the information of whether this frame belongs
        to an open call in a local variable, instead accessing the
        flag from local at the end of qr_open_cbk.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 231 (Quick-read: Fix access of freed memory in qr_open_cbk.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=231

commit 8c95c2b69c08fa5c7d845e73d0e63fb2f001c511
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Sep 4 01:43:43 2009 +0000

    storage/posix: Synchronize access to this->private.
    
    Hold lock on priv while updating variables inside it.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 175 (Statistics for number of open files in Posix incorrect)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=175

commit fdef6f360f0755847d2520d79a4c7f0af35c7b0a
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Sep 7 03:13:50 2009 +0000

    storage/posix: Handle setgid bit on directories correctly
    
    If a directory has the setgid bit set, then any entry
    created under it must have group ownership same as
    the directory.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 241 (Gluster not honouring SETGID flag)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=241

commit eecce95c2fc4713146e4ba99817abaac94102763
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:37:37 2009 +0000

    performance/stat-prefetch: don't check for a non-null parent and inode in newloc during rename.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit ef073ee5430e1f3af3bd580dd99a72352889756b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:37:26 2009 +0000

    performance/stat-prefetch: minor bug-fixes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 6bf11bf0dee3d3e70536a96cb8f8a4b01c26b445
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:37:16 2009 +0000

    performance/stat-prefetch: update design document.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit a5c829a3aa1d2f66dc85350bd4c163ef12507d44
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:37:10 2009 +0000

    storage/posix: handle dentries from different mount points in readdir
    
    - If posix translator is configured to have export directories to span accross
        different mount points, inode number is transformed in the dentry returned.
        Otherwise, the entry is not added to list of entries returned in readdir
        callback.
      - storage/posix returns ENOENT if the file is on different mount point other
        than that of exported directory and is not configured for export directory
        spanning across multiple mountpoints during lookup. But, since stat-prefetch
        shortcuts lookup calls, its necessary that readdir return only valid
        dentries.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 727c933a62e6b436c0aabcf80b6cd67620ee5429
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:37:02 2009 +0000

    performance/stat-prefetch: implement release callbacks.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 1d8f96e8c88b698a6cd1ec1f1a54f1b8aef70504
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:36:57 2009 +0000

    performance/stat-prefetch: implement sp_fxattrop.
    
    .../performance/stat-prefetch/src/stat-prefetch.c  |   37 ++++++++++++++++++++
     1 files changed, 37 insertions(+), 0 deletions(-)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 5e89bf62f8fb7a2a863f8b0c08ee1815a5aa5b38
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:36:47 2009 +0000

    performance/stat-prefetch: implement sp_xattrop.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 284b42546e01f81e53b45695de1b4c893c98f418
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:36:37 2009 +0000

    performance/stat-prefetch: implement sp_checksum.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 251c9d6e83d4bdcc8180fc9f612fbef7ff4d39c3
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:36:28 2009 +0000

    performance/stat-prefetch: implement sp_getdents.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 26be5dc52d771b37d4e9da8814111448e4e68148
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:36:17 2009 +0000

    performance/stat-prefetch: flush stat corresponding to directory being read in readdir
    
    - delete the entry corresponding to basename of path on which fd is opened
       from cache stored in parent. This is necessary because readdir changes
       st_atime.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 155e6342d4f72d3be500510277b0808859ae2d2c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:36:08 2009 +0000

    performance/stat-prefetch: implement sp_setdents.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 9d30a68082659c27a9dac6e4d1a98e2be8bf5bf8
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:36:02 2009 +0000

    performance/stat-prefetch: implement sp_removexattr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit a3449caf58d7e4876cf0246e22b044a8de8bde2b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:35:52 2009 +0000

    performance/stat-prefetch: implement sp_setxattr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 52c34af5f4814b0b85efdc3c4d23638b6ca5514c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:35:36 2009 +0000

    performance/stat-prefetch: implement sp_rename.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 42d7559e8de1ca9c35dee6f731350c01a53932ad
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:35:02 2009 +0000

    performance/stat-prefetch: implement sp_fsync.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 562e2afbc6540d093086d4b41c6acedb48e1b0c5
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:32:06 2009 +0000

    performance/stat-prefetch: implement sp_writev.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 4b4b44960f5b6ccf1b0c5a222708654ae1d32a53
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:32:00 2009 +0000

    performance/stat-prefetch: implement sp_readv.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 1a2db6ed799d9ce05232422f5d5094da4fd5c35c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:31:53 2009 +0000

    performance/stat-prefetch: implement sp_rmdir.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 29c282b1605afe6d6016660e21018e1954ce0a79
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:31:45 2009 +0000

    performance/stat-prefetch: implement sp_unlink.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 22ec7a4cb2e05f2c3c4512d80256008caa8b994b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:31:37 2009 +0000

    performance/stat-prefetch: implement sp_readlink.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 4538285776eeaa5383d7473438440d953fd9e232
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:31:28 2009 +0000

    performance/stat-prefetch: implement sp_utimens.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 4d305aa59877b52a6818e87630c3ee7f5b050d5b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:31:19 2009 +0000

    performance/stat-prefetch: implement sp_ftruncate.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 464f92cac5cd932386bb3b816c207e16c88cfe06
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:31:12 2009 +0000

    performance/stat-prefetch: implement sp_truncate.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit e5097a05fb2b95c53c24ab891e54259e6c5f4378
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:31:04 2009 +0000

    performance/stat-prefetch: implement sp_fchown.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit d943335cf06c6569d6517e073b1619a8ea013298
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:30:58 2009 +0000

    performance/stat-prefetch: implement sp_chown.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit cde006b0f117944761e97e81d44362a046676422
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:30:47 2009 +0000

    performance/stat-prefetch: implement sp_fchmod.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 724f869021f7d673ed5b0993e39e93687587ee8d
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:30:39 2009 +0000

    performance/stat-prefetch: implement sp_link.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 81d858f16cba61dfdf9f4b1348703d2e5358a0ad
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:30:32 2009 +0000

    performance/stat-prefetch: implement sp_symlink.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit ff9a9eae29edc7927fea9d6bf006c8b181e2bbd7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:30:25 2009 +0000

    performance/stat-prefetch: implement sp_mknod.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 385faf46a6878c7a42a1a2cb2c7c68c92cc0cc3b
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:30:15 2009 +0000

    performance/stat-prefetch: implement sp_mkdir.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit acb388c4c584cbc601bee69b0ca297eb3a9ef296
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:30:06 2009 +0000

    performance/stat-prefetch: implement sp_opendir.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit b18aa9cd570cb20680aa3d5bac11a2674d2a2f78
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:29:54 2009 +0000

    performance/stat-prefetch: implement sp_create.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit ded6f40765a34dce2ec49d1b643770f110882b15
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:29:41 2009 +0000

    performance/stat-prefetch: implement sp_open.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit b0d3d94b8ca94d1a133f74050d078a4bd6fa5260
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:29:29 2009 +0000

    common-utils: introduce new macro GF_VALIDATE_OR_GOTO_WITH_ERROR
    
    - the existing macro GF_VALIDATE_OR_GOTO sets errno to EINVAL
        which may not be appropriate in all cases.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 2cbc63ca8bbfcb91bce775651e1acc0994a18ac0
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:29:19 2009 +0000

    stat/prefetch: free cache if it cannot be put into context of fd
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 8c110d0aba119d199e2e8d29418ed45119aeb30c
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 26 01:36:53 2009 +0000

    performance/stat-prefetch: introduce sp_fd_ctx_t to hold context of fds
    
    - we need following extra members along with cache
        1. basename of path on which fd is opened. This is necessary to search
           for cached entry in fd based fops.
        2. inode corresponding to dirname of path on which fd is opened. This
           is necessary to get cache where entry corresponding to file on which
           fd is opened.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 3a0317982bfc8c507cfaf8dc919d5f4bab4371f7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:28:55 2009 +0000

    performance/stat-prefetch: implement sp_chmod.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 517c1997f5cb1ee7b62cc925f943b33e91e7b974
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:28:42 2009 +0000

    performance/stat-prefetch: implement sp_readdir.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit ebc5d9888dfd7fcc000fac82dcfbad9fb91a9082
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 26 01:36:11 2009 +0000

    performance/stat-prefetch: implement sp_lookup.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit bcd092a21f4284277a7f59c58715bb253ed90ff7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Sun Aug 23 22:28:18 2009 +0000

    rewriting stat-prefetch translator
    
    - stat-prefetch aims to optimize operations like 'ls -l' where a readdir
       is immediately followed by stat calls on each of the directory entry read.
       More details on design can be found in doc/stat-prefetch-design.txt
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 221 (stat prefetch implementation)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

commit 314eb5fecf61b61ae9ba6bd76a44ea14bbd04513
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Sep 2 05:13:21 2009 +0000

    mount/fuse: Include missing header files in Makefile.am
    
    Compilation fails in a new glusterfs tarball due to missing fuse headers.
    Including them in Makefile.am.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 244 (compilation after make dist fails because of missing headers)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=244

commit cf1005c9f650069a22d443dec32f33129431990a
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Mon Aug 31 22:35:28 2009 +0000

    ib-verbs: handle failure of ibv_create_qp gracefully.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 217 (crash in ib_verbs_create_qp)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=217

commit addf1c713a017a7b1b4a871243f599267255e815
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Aug 28 00:17:01 2009 +0000

    libglusterfsclient: Compare compcount with path not maxentry
    
    When searching for an exact entry we need to compare the
    component counts in the candidate VMP and the count in the
    path being searched. This is opposite to the current
    situation where we compare the component count in VMP
    and the component count in maxentry, which will always
    be same.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 209 (VMP parsing through fstab has issues)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=209

commit 22e0167d054c6880a66d51a7d86695fe2dd97f44
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Aug 28 00:16:50 2009 +0000

    libglusterfsclient: Enhance VMP searching logic
    
    Another attempt to enhance searching for VMP entries.
    There was a problem of returning the longest prefix match
    from all the VMPs without checking whether the number of
    matched components were same as the number of components
    in the candidate VMP.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 209 (VMP parsing through fstab has issues)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=209

commit d165f43bb127e2a055721aa7793743fd55e94ed3
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Aug 28 00:16:42 2009 +0000

    booster: Support backward compatible options
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 209 (VMP parsing through fstab has issues)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=209

commit c50ead8d5318d759207543ea040baaf8ddadc628
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Aug 27 01:53:32 2009 +0000

    core: Fix build failure on non-Linux systems
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 230 (Bulid fails on Solaris and Mac OS due to Linux specific flags)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=230

commit bc1bacb14650809f4685025c9fb4b799f9510df9
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Wed Aug 26 05:08:18 2009 +0000

    libglusterfsclient: don't use pointer returned by basename while freeing allocated memory.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 228 (Segmentation fault in glusterfs_getxattr)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=228

commit 4d479650245d15e6bb5d6993919ebd3eaa68f089
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Aug 25 05:09:28 2009 +0000

    fuse: protocol fix: fix bogus parsing of MKDIR message
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 226 (mkdir after rm of regular file of same name fails)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=226

commit 8572d0ced5db512620f515704e2a9c05d6a4589c
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 20 13:49:03 2009 +0000

    changed booster fstab to parse the arguments same as mount.glusterfs
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 209 (VMP parsing through fstab has issues)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=209

commit cb539b0b65d1868410a10266edb042bdaf867301
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Aug 20 18:51:10 2009 +0000

    protocol/client: 'connecting' event is properly notified.
    
    when there are no servers available to client, and transport init is
    not successful, send 'connecting' event once to parent so it doesn't
    hand in there.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 224 (Client hangs if none of the servers are up)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=224

commit 45883c74f2c3b11b77fa94be714341ccf0e21198
Author: Krishna Srinivas <krishna@gluster.com>
Date:   Sun Aug 16 14:34:08 2009 +0000

    in server_rename if we do_path_lookup on the newloc and parent directory is not found, the server crashes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit b4d6c3d1bb461d2c8a396c9ed3881a4da40fc6ab
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sat Aug 15 12:58:08 2009 +0000

    TAKE2[PATCH BUG:213 1/1] Support for Process State Dump
    
    Support for process state dump.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 213 (Support for process state dump)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=213

commit a31b0016347b3bc9b341fa0f4541ed137224f593
Merge: 862cbb3 1082475
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Mon Aug 17 15:25:44 2009 -0700

    Merge branch 'fusilli' of /data/git/users/csaba/glusterfs-fusilli
    
    Conflicts:
    	xlators/mount/fuse/src/fuse-bridge.c

commit 862cbb38375f0176582b06019ba406818d236828
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 4 19:43:31 2009 +0000

    added log message when server fails to send the reply frame
    
    As of now, if a frame submit fails on server, there are no logs,
    and clients will have missing frames (which leads to 'hangs').
    Supporting situation like this very tricky without proper log
    messages. As a step to make our log message lean and meaningful,
    this log is important.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 190 (missing frames due to larger reply message size.. (ib-verbs))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=190

commit a55616242a4f883a864ac03b5282a12c6b8da03e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Aug 13 02:57:18 2009 +0000

    libglusterfsclient: Sync access to VMP list on new entry addition
    
    Some weeks back, I'd separated the big lock into vmplock and mountlock.
    See commit 304e4274ca9b0339539581c5413e3339078c1182 in mainline.
    
    At that time, we did not have a solution to the problem
    of when to init the vmplist in a thread-safe manner, since
    there was no lock to protect the vmplock specifically, and that
    when libgf_vmp_map_ghandle was called inside glusterfs_mount
    so the "lock" was already being held.
    
    Now that we have separate mount and vmp locks, the
    accesses can be synced correctly.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 211 (libglusterfsclient: Race condition against vmplist in libgf_vmp_map_ghandle)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=211

commit 425f895f0f89831221451c5aa8e0a7e31e95f2aa
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Aug 13 02:57:17 2009 +0000

    libglusterfsclient: Enhance VMP search logging
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 210 (libglusterfsclient: Enhance logging)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=210

commit e3a4b55920bf6620f5635a6785ae6f2eaf6eba2d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Aug 13 02:57:16 2009 +0000

    libglusterfsclient: Use components for VMP searches
    
    Till now, we've been doing a character by character comparison
    between a given path and the VMP, to search for the glusterfs
    handle for the given path.
    
    This does not work for all cases and has been a known bug.
    This commit changes the byte-by-byte comparison into a more
    accurate component based comparison to fix search
    failures.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 209 (VMP parsing through fstab has issues)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=209

commit 53430bbd47dd61544e10596ca490e64cb2a4e85f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Aug 11 04:59:29 2009 +0000

    features/locks: Fix reverse logic in posix_lock_to_flock
    
    if the lock's end point is LLONG_MAX, the corresponding
    struct flock's len must be 0.
    
    Previous code had LLONG_MAX and 0 reversed.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1e7a880cecfb4df0bb560f8d071cafda4889b6df
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Aug 11 01:43:33 2009 +0000

    mount/fuse: Don't log setlk returning EAGAIN as a GF_LOG_ERROR.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 70b1a8670152187bc4fb06d6a11437abe8481a9b
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Aug 11 01:42:14 2009 +0000

    features/locks: Set the right log level in a few places.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 95ee2689a6684e8e2436d5e8256c170ab3161673
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Aug 10 02:17:43 2009 +0000

    glusterfs log prints "TLA Revision" tag, remove it and reflect git instead
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 10824751f8669e7c39ebd46ab698ed0abd4e5165
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Aug 16 15:51:23 2009 -0700

    fuse: a compat fix for older protocol revisions

commit 15d85ff1fb518ddd15e03daa297f59457376725f
Author: Csaba Henk <csaba@gluster.com>
Date:   Sun Aug 16 07:02:27 2009 -0700

    fuse: optimize request iov aligment for writes
    
    Idea by Avati.

commit 3d894362ae0b8d346f29e9c3ea98e325d83a083a
Author: Csaba Henk <csaba@gluster.com>
Date:   Fri Aug 14 15:51:37 2009 -0700

    fuse: switch off direct I/O mode if big writes are supported

commit a91679b605ffbe71fa7124964df8aea08ccba464
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Aug 12 04:17:59 2009 -0700

    update user guide wrt. FUSE requirements

commit 901ba842cd6c42ff24e0539a1b8231b3e802e1ce
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Aug 11 18:26:11 2009 -0700

    bring in fusermount

commit fbb636390fe51dc6aa52ec7523a36b183434a28c
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Aug 11 06:24:40 2009 -0700

    fuse: add proper mounting support, based on libfuse routines

commit 472ac9944b2e99b8dd4a7e33f8dc4ae0f111b0cc
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Aug 10 19:46:45 2009 -0700

    fuse: move libfuse derived code over under contrib/

commit ab5df475c5c7e9e0f3268fe94a6280e71d34c1db
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 14 17:10:38 2009 -0700

    upgrade FUSE protocol to 7.12 and add support for older versions of the protocol

commit d5910898f1602dc16ab158b06c37abcd98a0588a
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Jul 13 22:28:07 2009 +0200

    basic version of direct FUSE interface (ie. not relying on libfuse)

commit 57a6cb9806ad9d99e6866a21d16fcb1bafef000c
Author: Anand Avati <avati@dev.gluster.com>
Date:   Thu Aug 6 21:51:33 2009 +0000

    protocol/client: fixed registration of saved_fds
    
    In client_open_cbk, client_opendir_cbk the list_add_tail macros were invoked with wrong
    ordered arguments, causing the existing registered fd list to get unlinked from the
    saved_fds list. The effects of this is far fetched - when transport disconnects, open
    fds are no more marked bad as they are not reachable from the saved_fds list. After
    reconnection, resumed access on this fd causes reference to invalid fds on the server.
    It could appear in the form of 'unresolved fd' error, readdir happening on a file fd,
    files reading from other files, etc.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 192 (sefault in posix-readdir)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=192
    
    BUG: 126 (Immediate segfault when used for rootfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=126
    
    BUG: 173 ([ glusterfs 2.0.6rc1 ] - "server SEG fault")
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=173
    
    BUG: 194 (Apache+Booster results in inconsistent download size using wget)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=194

commit cce2f6f690b2cac2ed7383fb9306c0dd8b5d3aa6
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Thu Aug 6 00:55:53 2009 -0700

    Removed BRANCH: tag

commit 546390e845166ffcfcce6e47e105a453c3ac565c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 4 18:56:52 2009 +0000

    server-lookup: added path info from header to log message
    
    in the previous commit, the path info was removed to prevent the
    segfault, which instead could have been provided from request
    header directly. More specific information is required for debugging,
    and hence adding the path log.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 189 (segfault in server-lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=189

commit e981886cb1da8cbde1f93a9ab249130e8be163f5
Author: Anand Avati <avati@dev.gluster.com>
Date:   Tue Aug 4 18:15:23 2009 +0000

    dht_stat_merge - use the highest uid when ambiguous
    
    When directories on different subvolumes have different ownerships, use the highest uid/gid till self-heal resolves the inconsistency
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 191 (random Permission denied errors)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=191

commit aaf483185e6fdd1b0102ee2ae27e53826efdfc21
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 4 18:15:45 2009 +0000

    add check for making sure 'fd' belongs to directory in posix-readdir
    
    The root cause of this error is not found yet. But this check will
    make sure that there is no crash when the situation happens.
    Segfault can happen when a readdir() call comes over file's fd.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 192 (sefault in posix-readdir)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=192

commit 33b5ce10ef7b5c6db6e73f6070fd4579c2765c94
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 4 17:51:58 2009 +0000

    logging related bug fix in server_lookup()
    
    When 'dict_unserialize' failed, the log message was trying to
    print 'state->loc.path' and 'state->ino', which gets filled in
    later stages in flow. Caused segmentation fault when there was
    a failure.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 189 (segfault in server-lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=189

commit edd633f30adba95c65d29c58a2562ccbb18c3495
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 4 17:51:44 2009 +0000

    increased ib-verbs buffer size
    
    Noticed that in few cases, where ib-verbs doesn't handle a bigger
    sized buffer to be sent across, which happens without problem in
    tcp. Caused frame losses in the case where server's reply msg was
    bigger, hence the msg got dropped at the server end. With this patch
    ib-verbs buffer size is fixed to 512KB. (4 x page-size)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 190 (missing frames due to larger reply message size.. (ib-verbs))
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=190

commit 2c056117b6cfe4bf3f62c791d2c6514bae8655d9
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Aug 4 17:51:31 2009 +0000

    adding an option to mount.glusterfs for server failover to fetch volume files.
    
    With this option, 'single point of failure', in case of volfile server can be
    avoided
    
    Thanks to Cory Meyer <cory.meyer@gmail.com>
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 185 (Request to support secondary volfile-server option in mount.glusterfs)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=185

commit e26e9b861d92edfb7c00aa1b7c8c3a4126a563fb
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Aug 4 04:39:34 2009 +0000

    cluster/afr: inode-read: Check stat buf for NULL before attempting to set inode number.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 184 ([ glusterfs 2.0.6rc2 ] - Client Segfault while running fs-perf-test)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=184

commit acb06b282a64b2751d33424e4e833c0c7dcf87d7
Author: Raghavendra G <raghavendra@gluster.com>
Date:   Thu Jul 30 23:08:42 2009 +0000

    client-protocol: log messages at WARNING loglevel when client_bind on privileged port fails.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 140 (use appropriate loglevel to log in case of failure to bind to privileged socket)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=140

commit b63f69cdf40ef5bd79abdcd641b3dcc4bcb3cb1a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Jul 31 12:38:36 2009 +0000

    libglusterfsclient: Bind fd on fd creation code paths
    
    When an fd_t is fd_create'd, we need to call fd_bind on it to
    ensure that any fd_lookup on the inode gets us this fd. We're not
    doing this so translators like write-behind were not able to order
    path-based requests at all resulting in some fops like stat, which
    could be issued after a writev, overtaking a previous writev which
    is still being written-behind.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 179 (fileop reports miscompares on read tests)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=179

commit 2f8a834e7b6acef73795237d6c6269eb9838de53
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Jul 31 04:14:48 2009 +0000

    libglusterfsclient: Invalidate iattr cache on reads
    
    Earlier we have invalidated the iattr cache on writes. Now
    we need to do so for reads also, so that we are not updating
    the iattr cache with 0-filled stat received from io-cache.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 180 (fileop fails at chmod with stale file handle error over unfs3)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=180

commit fdbc5cf320fe85d128d498184135df10146047ba
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jul 30 12:05:11 2009 +0000

    replicate: Return ino from first subvolume on inode creation fops
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 177 (replicate: On file/dir creation, replicate returns inode from random subvolumes)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=177

commit 83ef3c8211282a9ef66659bfbde25116e4949b71
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jul 30 12:04:05 2009 +0000

    libglusterfsclient: Use iobufs for storing application write data
    
    Till now we've been creating an iovec, storing references in it
    to the application data and simply passing it on to the translator
    tree. This means that the buffer being passed to the translators is
    not at all associated with the memory ref'd by the iobref argument
    to write fop. This is a problem when write-behind is a translator in
    the tree since it assumes that the memory in the iovecs passed to
    write fops is already refcounted by the iobref and so it simply copies
    the address of the application data. The problem is that the application
    can continue using this buffer, free it or over-write it destroying the
    data that write-behind may write at a later time.
    
    The solution involves copying the application's write buffer into
    an iobuf which will be referred to by the iobref.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 178 (libglusterfsclient: Data corruption on using write-behind in translator tree)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=178

commit 9beaccbee6b9e3356e04887c2f3e3f6e8d781228
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Jul 29 08:02:57 2009 +0000

    booster: Fix fd leak due to incorrect NULL check
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 174 (booster: fd_ts, they are a leakin)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=174

commit a4c6e7c816fa9dfbed07a30af56a4ada824ce40b
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Tue Jul 28 00:52:56 2009 +0000

    glusterfsd: handle logfile path specification appropriately.
    
    when logfile path is not specified as absolute path, the symbolic
    link created to the logfile (only in invocation of glusterfs with
    --run-id) might end up as a broken symbolic link.
    
    for example, command-line invocation like below will result in
    broken symbolic link:
    glusterfsd -f /home/glusterfs/volfiles/nufa/nufa.vol
    -l ../home/glusterfs/logs/nufa.f1.log --run-id nufatest /mnt/nufa/
    
    symbolic link will be created at $PWD/../home/glusterfs/logs/nufa.f1.log
    will have a value of ../home/glusterfs/logs/nufa.f1.log.<date>.<time>.<pid>.
    this symlink might be broken.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 156 (Broken symbolic link when relative path is given for a log file)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=156

commit 8225fd2307d8a5a9bba4f21b5534b8469f679605
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jul 27 16:48:37 2009 +0000

    server-protocol: fix in server-loc-fill()
    
    to continue with 'hashed' inode, even if inode_path() on the inode
    fails. This will is needed for few lock operations, to unlock the
    lock held on inode. (ie, it fixes 'rm -rf *' hang issue, seen from
    multiple clients).
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

commit 152e36883a79c0d73e0725357a4a2870b06eb75b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jul 28 04:51:35 2009 +0000

    libglusterfsclient: Fix solaris build error
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 115 (./configure adds libglusterfsclient when it shouldn't)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=115

commit ed80e78aecf5f46e29e5cb9034f2b2c06836b8d4
Author: smyczek <smyczek@simplito.com>
Date:   Mon Jul 20 18:44:00 2009 +0000

    libglusterfs: fix SuperFastHash function used in dicitionaries in fact it always returned the value of second parameter (len) as a result.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 155 (The SuperFastHash function used in dictionaries is broken.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=155

commit 1b89e8689c070ceeeafa24e03c8aed6e17540aef
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jul 23 11:25:01 2009 +0000

    cluster/afr: Use user-supplied struct flock to STACK_WIND
    
    afr_lk_cbk:
     Use the original struct flock supplied by the
     user to do further STACK_WIND's, and not the flock returned
     by the previous STACK_WIND.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 159 (Client hangs when coherent byte range locks is attempted in replicate setup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=159

commit f33cdc33e28fa8364691a853e3bee84b335a4f9c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sat Jul 25 12:59:14 2009 +0000

    libglusterfsclient: Workaround for local memory corruption
    
    There seems to a reproduceable corruption specifically of
    the libglusterfs_client_local_t that is allocated for
    the read call. Therefore, the subsequent access to fd inside
    local leads to a segfault. This is a temporary fix.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 164 (libglusterfsclient: Segfault due to memory corruption of frame local in libgf_client_read)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=164

commit ccd93eb64c0f2f73f83e025d3efae794803aaa4c
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Jul 27 09:30:48 2009 +0000

    cluster/afr: Return same inode number in stat buf for readv_cbk
    
    Remember the inode number that had been returned in lookup_cbk
    and set the stat buf->ino to the same.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 166 (libglusterfsclient: Cached stat buf inode is different from ino in inode_t)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=166

commit ffa5118b2eec9cd12e43ca10d86e91d02a9090a8
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Jul 27 04:29:26 2009 +0000

    cluster/afr: Set inode number in unwind_buf in the inode-write calls.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 166 (libglusterfsclient: Cached stat buf inode is different from ino in inode_t)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=166

commit df868214c077065cfeafcfdadb6bbf5151d20b3d
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jul 23 16:19:26 2009 +0000

    libglusterfsclient: Avoid overwrite of inode found through ino number
    
    In libgf_client_loc_fill, there is a possibility that all
    the ino, par and name are specified as non-NULL,non-zero args.
    
    So if an inode is located in the itable using the ino and the
    subsequent search for the inode using the par-ino and the file
    name does not result in an inode being found, the current
    code over-writes the inode that was found through the ino. The
    correct behaviour is to stop further searches if inode
    was already found using ino.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 161 (unfs3 crashes on link system call by fileop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=161

commit 955c6e0c87b501501d87806f1e69ece8f0559dd6
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jul 23 16:18:43 2009 +0000

    libglusterfsclient: Fill new loc with target's ino on link
    
    In the loc_t of the link being created, we must fill in the inode
    of the old/target loc since this is a link operation. The
    inode_link to the new parent is called in libgf_client_link.
    
    This fixes a crash while running fileop over a fully-loaded
    dist-repl vol file.
    Ref: Bugzilla 161
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 161 (unfs3 crashes on link system call by fileop)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=161

commit 48755d7eaf9d22e4707b7abc7b3df46256fa6069
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Thu Jul 23 15:38:32 2009 -0700

    enable libglusterfsclient build by default
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 03d6dae5a4003bcaf86eb887f63444c0565ad32c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Jul 20 01:25:12 2009 +0000

    libglusterfsclient: Fake a fsid for every VMP
    
    This is needed to work around the replicate behaviour of
    possibly returning device number for the same file from
    
    different subvolumes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 148 (replicate: Returns st_dev from different subvols resulting in ESTALE thru unfs3booster)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=148

commit a12f332cff050db3aa3905436158cbd339fa6963
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sun Jul 19 03:26:13 2009 +0000

    libglusterfsclient: Move DHT root-lookup workaround to init
    
    The workaround for the DHT requirement for a lookup on /
    needs to be done only once when the xlator graph is inited.
    Doing it on every path's lookup results in a major performance
    penalty when using distribute subvolumes upwards of 16, as reported
    by Avati.
    
    Ref: bug 152
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 152 (libglusterfsclient: DHT workaround is a major performance bottleneck)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=152

commit 1a56bed50190e20999d28b7da8418927ecb8b041
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Jul 18 00:37:51 2009 +0000

    added timestamp to crash dump log.
    
    also did some minor enhancements in formating
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 151 (crash dump log should be in 'logviewer' friendly format)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=151

commit 7b8d2b38a12ed7e0a63ad9b1c38bfa20d8317b11
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:44:24 2009 +0000

    fix build warnings in 'libglusterfsclient'
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit 500d114032c0d6f92abd25fbf6786b866a0b3dd5
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:44:11 2009 +0000

    fix build warnings in 'afr'
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit 0af7bd9a1f590a17490663869420bd8777189b97
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:43:56 2009 +0000

    fix build warnings in 'server-protocol'
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit 793ca3c52a9ba6a1723e5ad767449f8b69ac19a8
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:43:19 2009 +0000

    fix build warnings in 'client-protocol'
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit 05211cdaff7ac117095c2213722b386c0f172ed0
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:42:55 2009 +0000

    fix build warnings in 'io-cache'
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit d62362acd64a2d495431f6c4ff7dffc8d47856df
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:42:33 2009 +0000

    fix build warnings in 'auth' module
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit ca859dfe78e3da853181e5e9e314586bf9300204
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:42:10 2009 +0000

    fix build warnings in glusterfsd
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit 632cce5e720acaa28ab680a6850f2aa8289d4628
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:41:44 2009 +0000

    fix build warnings in 'libglusterfs/'
    
    return value of 'asprintf' was not checked, and the flow was
    continuing without returning error, which could cause potential
    segfaults in code (mostly possible during ENOMEM case).
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 130 (build warnings)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=130

commit 5be3c142978257032bd11ad420382859fc204702
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 17 22:09:17 2009 +0000

    posix getxattr supports new key 'trusted.glusterfs.location'
    
    which can be used to get the file location by 'hostname' of the
    machine where file resides.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 131 (provide a way to get the file location in clustered storage)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=131

commit 2105226253d4fe8cca2e31de76960ddc1a47a8c3
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 15 20:06:02 2009 +0000

    removed mod_glusterfs from the build
    
    future plan is to have httpd use booster and libglusterfsclient
    instead.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4b3633cde1bb9a9a692eade129e4a45dbf82d8ec
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Jul 17 08:48:10 2009 +0000

    libglusterfsclient: Invalidate not update iattr cache on writev
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 149 (libglusterfsclient interacts incorrectly with write-behind on writev)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=149

commit 847e02d901a5cedf4f28d34fa2431b41a07b9a2a
Merge: 2a385c2 5dfa1eb
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Thu Jul 16 00:40:33 2009 -0700

    Merge branch 'master' of ssh://git.sv.gnu.org/srv/git/gluster

commit 2a385c2984a8dd670c4b77361d8a24c3567138f5
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 14 17:38:42 2009 +0000

    server: don't check for 'loc->parent' in entrylk and inodelk calls
    
    the lock operation on entry or inode is going to happen on only one
    inode, and it doesn't need dentry (with info on parent) for the
    lock operation to complete. Hence, in server_{inode,entry}lk() calls
    after server_loc_fill, we -should not- be checking for parent inode.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

commit bdcdc8dd18dda19af698f147e3f32ed7f9e5efd5
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jul 14 17:38:08 2009 +0000

    change mount.glusterfs.in to work with non-bash shells too.
    
    removed 'fuction ' prefix to function definitions which was very
    much /bin/bash specific.
    
    Thanks to Brent A. Nelson <brent@phys.ufl.edu> for the patch.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 139 (tiny glitch in mount.glusterfs in 2.0.4)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=139

commit 41986e06d0e8e5f66f20944bc8d8abeca1d73ab1
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 23 19:08:46 2009 +0000

    iostat to have more io details
    
    classified stat for write/read fops based on their block size.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit eb4d32ae6b30e5a6aaebf068cc07e7ad2c6ea6d2
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:29:06 2009 +0000

    quick-read: implement release and forget cbks.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8a184d6f5674b3d5ec50eeaf089ded3c9c14300f
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:28:45 2009 +0000

    quick-read: implement qr_lk.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 5c95b6568201a6b9e0043ad838892599ab0e0d90
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:28:34 2009 +0000

    quick-read: implement qr_ftruncate.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 56428dbbbdd802d2d8cf4377d4f03a59caab7c8b
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:28:22 2009 +0000

    quick-read: implement qr_fsync.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 689f87e0db1eaa6ccc0b311b4e469fd922e4237f
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:28:08 2009 +0000

    quick-read: implement qr_finodelk.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ed9687b7fc050b6fcd8ef79eab977d1ef2f1e801
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:27:57 2009 +0000

    quick-read: implement qr_fentrylk.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 206e1af66adea885fcaf5ad02a510ac0deb36870
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:27:46 2009 +0000

    quick-read: implement qr_flush.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit cd945c716fdbd430d575f43732801163b076b258
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:27:34 2009 +0000

    quick-read: implement qr_fgetxattr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit aa42833f33952aae55afb6e02376d7f2a766f438
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:27:23 2009 +0000

    quick-read: implement qr_fsetxattr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit aa0902f9d18bdc72e5d0ed2add15962a02b0b40f
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:27:11 2009 +0000

    quick-read: implement lc_fchmod
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c744ff99b5e72f7b6ee1909b90649333b6ffc98d
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:26:58 2009 +0000

    quick-read: implement qr_fchown
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8579b0edbc8c6d14614777aa7ca7de6d42fb1662
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:26:47 2009 +0000

    quick-read: implement qr_fstat.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 01ccfc375925a1643afbd5ce2eb8078a617db881
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:26:35 2009 +0000

    quick-read: implement qr_writev
    
    - writev on any fd opened on a file invalidates the cache stored during lookup
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 493e712940fd4c1ce621db0c970597b11446da3e
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:26:14 2009 +0000

    quick-read: implement qr_readv
    
    - pseudo-code of the algorithm is given below
        if (content is cached) {
           validate-contents ();
           if (content cached is valid) {
              stack unwind with cached content;
           } else {
             goto read-from-storage;
           }
         } else {
            goto read-from-storage;
         }
    
         return;
    
    read-from-storage:
         if (open is already done on fd) {
              stack-wind read;
         } else {
           add the current readv to list of operations waiting on completion of
           open;
    
           if (open on the fd is in transit) {
             do nothing;
           } else {
             stack-wind open;
           }
         }
    
         return;
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit eaac497bfe4dd95a5d5ea34bf59c16bf946960e9
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:26:00 2009 +0000

    quick-read: implement qr_open
    
    - The file is opened actually only if it is not cached already in lookup.
        This adds responsibility for fops operating on fds to make sure that a
        valid fd actually opened on a file is used to complete the fop.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 06f02a48e0632469a7fd3ab1d7b5364a0de82d91
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:25:45 2009 +0000

    quick-read: add qr_lookup.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1b4e68977c43b8d432d28d7301add35b01464ae5
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 00:25:28 2009 +0000

    Implementing quick-read translator.
    
    lookup can fetch the entire file in xattr dictionary using the key
    "glusterfs.content". We set the maximum size of the file that can
    be fetched so in the xattr_req dictionary using the same key. If file-size
    is less than or equal to the value set in dictionary, the content is stored
    in the dictionary using same key in lookup_cbk.
    
    For small files, we can do an optimization wherein we do not really send the
    calls open, read and close to the storage translators. Instead there can be
    an xlator which fakes open, read and close calls. For reads, it sends the data
    it has cached during lookup and hence saving the time for open, read and close
    calls to reach storage translators (this time can be significant if calls have
    to go through network to reach storage translator).
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 3e3be6de2d954bcd134e8f377ea1af4cab682e04
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Jul 15 09:36:36 2009 +0000

    Return stat from read subvolume in dir-write ops.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 138 (create family calls do not return stat buf from read child)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=138

commit e07a362a54c6f1bff5b87ce30a5302f0cd01c086
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jul 14 08:05:14 2009 +0000

    Return stat info from read-child in all the inode-write ops
    
    Also modifies the inode-write ops to wait for the call
    to read-child to return (whether success or failure)
    before unwinding.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 125 (stat information not returned from the same subvolume always)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=125

commit 3ce764351c0cdf01637eb0f19ec9846e91ca3f35
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 15 01:38:33 2009 +0000

    add strict validatation of GF_OPTION_TYPE_PATH option type.
    
    Make sure that users don't provide "../" in the path value in volume file,
    which should be considered security issue.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 141 (GF_OPTION_TYPE_PATH should check for presence of ".." in path)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=141

commit 61d9179fd8e884e3ace5b1ffd38f89e5032dbb42
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue Jul 14 09:43:23 2009 +0000

    fuse-bridge: Export user.glusterfs-booster-mount xattr
    
    This needs to be exported in order to have the booster
    Mount Point Bypass technique work through libglusterfsclient.
    Booster uses the mount point to register with libglusterfsclient as
    a VMP. Subsequently, all file operations on the mounted GlusterFS
    mount point get redirected to libglusterfsclient.
    
    This fixes bug 136.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 136 (booster does not redirect ops on GlusterFS mount point into libglusterfsclient)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=136

commit f2ba42e4c6e44db9274d051065a233d9ed622959
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jul 13 16:59:18 2009 +0000

    break inode_path if the length of the path crosses PATH_MAX
    
    a given search for path can't exceed the length of PATH_MAX in any case.
    Hence, its best to make sure by adding a check inside the for loop of
    inode_path, so that it won't enter an infinite loop.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 134 (infinite loop in inode_path ())
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=134

commit 106f0e848a6ae3a04ee9d1c1752badf60767d039
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jul 10 13:39:10 2009 +0000

    cleanup 'ctx' from inode and fd
    
    Removing unused 'dict_t *ctx' from both inode and fd structures.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 128 (cleanup unwanted ctx dictionary in 'inode' and 'fd' structures.)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=128

commit 22c076cadc04e15aa84f86bca621d38fbf111932
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jul 9 23:59:26 2009 +0000

    ib-verbs: don't append ioq_entry to pending_list if first attempt of writing to network fails
    
    * fix to bug #101 - When a buffer bigger than ib-verbs-work-request-send-size
        was attempted to write to network, ib-verbs returns ENOTCONN. Neverthless,
        the ioq_entry corresponding to the write was appended to the pending lists
        of ioq_entries waiting to be written to network. This resulted in double
        free of header, once in protocol_client_xfer and again during cleanup of
        transport. The transport cleanup happened due to the timeouts of
        subsequent operations, since ioq_entry corresponding to writev
        was blocking any other operations from reaching server.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 101 (ib-verbs config crashing while dd'ing with a big mtu size)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=101

commit 359e87e72fcfc30909b0131a5e559466713245ed
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 14 06:41:33 2009 +0000

    fuse_bridge: handle failures in init() more gracefully
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 132 (fuse-bridge could do with some cleanups)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=132

commit fc4aa3ee763e8f05a8bd649d414fb8c278fe7380
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 14 06:40:09 2009 +0000

    fuse-bridge: formatting cleanups
    
    - use PRIu64 for printing "unique"
    - use fcntl defines instead of explicit numeric values for querying open flags
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 132 (fuse-bridge could do with some cleanups)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=132

commit 1253692116532433d04d606ec81fbccd4db8a50a
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jul 14 06:38:34 2009 +0000

    fuse-bridge: further allocation failure handling fixes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 132 (fuse-bridge could do with some cleanups)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=132

commit e16068f9e62b2812e4e78ed25b0b05fa67c5f3c8
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jul 9 12:17:54 2009 +0000

    fuse-bridge: handle state allocation failure
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 124 (state allocation failure not handled)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=124

commit a81ffd3b4eb53f57ef360872a85241d86b6c46ad
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jul 9 06:47:14 2009 +0000

    Added NULL checks in a few places.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 119 (filter + replicate crash..)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=119

commit 161188e919968f1d782e857151f2f4dca1fdfc22
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jul 9 05:33:54 2009 +0000

    Return inode number always from the first up subvolume in AFR.
    
    Also fixes a bug in the "KLUDGE" part. It was setting lookup_buf
    when it should have been setting local->cont.lookup.buf
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
    
    BUG: 116 (Replicate: Need inode number from first subvolume on fresh lookup)
    URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=116

commit c276dfe936dbb48cd5569099c5cc142122d160f8
Merge: 964cb91 dd6635d
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Thu Jul 9 14:08:44 2009 -0700

    Merge branch 'master' of ssh://git.sv.gnu.org/srv/git/gluster

commit 5dfa1ebac3eab4f0ff8fab6936e6678bb76c5f60
Merge: 964cb91 dd6635d
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Thu Jul 9 14:08:44 2009 -0700

    Merge branch 'master' of ssh://git.sv.gnu.org/srv/git/gluster

commit 964cb91e0341f1a15dd57e8487e0c01490b804d8
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Wed Jul 8 23:54:48 2009 -0700

    Added format-patch.sh. This script is to be used as a replacement of "git format-patch" with similar arguments for submitting patches to the GlusterFS project

commit dd6635dc3763979a63d37cb8232324e4bd2d605e
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Wed Jul 8 23:54:48 2009 -0700

    Added format-patch.sh. This script is to be used as a replacement of "git format-patch" with similar arguments for submitting patches to the GlusterFS project

commit fffaec58ea396cd8cf3303e38f331c25a4feaad1
Author: Csaba Henk <csaba@gluster.com>
Date:   Wed Jul 8 06:55:09 2009 +0000

    detabify fuse-bridge.c (and other whitespace fixes)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 45dc9a636f085d0cc2a86b949e86afedca411203
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jul 7 20:42:42 2009 +0000

    protocol/server: use translated flags in protocol/server open and create fops
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a2205684e2ea21e33dac00b40a0314af045ad6be
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jul 7 20:42:21 2009 +0000

    protocol/client: use translated flags in protocol/client open and create fops
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 9ec22fd9fc28684b7e2093b4c67d449c7f021623
Author: Anand Avati <avati@gluster.com>
Date:   Tue Jul 7 20:41:59 2009 +0000

    protocol: add functions gf_flags_from_flags and gf_flags_to_flags
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bde0032cfbe51383c697247831e26394ca6cd913
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Jun 30 01:14:44 2009 +0000

    write-behind: set default window-size to 1MB.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 80c769b54ed8e95ae3f51e19d2ef8c2e8ea5e44d
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Tue Jul 7 07:58:05 2009 +0000

    use fuse_reply_iov() in fuse_readv_cbk
    
    changes come in two places.
    
    configure.ac - define HAVE_FUSE_REPLY_IOV if fuse_reply_iov is
                   available in libfuse.
    
    mount/fuse - use fuse_reply_iov() in place of fuse_reply_vec(), if
                 HAVE_FUSE_REPLY_IOV is defined.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 54f5ccceca2531f1a88cb4d0404f92edffa09cae
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Jul 7 02:33:43 2009 +0000

    filter: use O_ACCMODE for checking file access modes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4e9757859750eb3625828f83681845f1352af356
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Jul 7 02:33:31 2009 +0000

    read-ahead: use O_ACCMODE for checking file access modes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ecc844dc15fffacaf37916e4570e520534f2545c
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Jul 7 02:33:15 2009 +0000

    write-behind: Use O_ACCMODE while checking for access modes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c8ef6e541f4dacd58258b0448046d4fae2c511be
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jul 2 06:20:21 2009 +0000

    libglusterfsclient: Update attr cache on read/write
    
    We werent updating the attr AKA stat cache on read and write
    on files so every stat on the file before the timeout was returning
    stale attr from the cache. Yuck!
    
    This fixes it. Turns out there is a good aspect of unfs3's notoriety
    when it comes to doing stat()s for every operation.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 41027a22054af821caeb2b47a7b93ff028ecaedf
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 22:08:21 2009 +0000

    libglusterfs/defaults - send CHILD_UP notify only to the parent which has been init()ed.
    
    fixes bz# 12
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8d74fe9ba6c3c2f68f71cacd56fad9328b8b0090
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 04:27:10 2009 +0000

    libglusterfs/logging - fix memory leak
    
    in _gf_log(), free 'msg' before returning.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 346b7f0c63920a73fd70b88d683c6a033e6b8abd
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Jul 6 05:59:47 2009 +0000

    Set timestamps properly when creating missing entries.
    
    In AFR self-heal set timestamp of a freshly created missing entry
    to that of the source entry.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit fd70ec76469204ffa7c8145c978f2fba6dca9a7a
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:25 2009 +0000

    libglusterfs - remove definition of ZR_FILENAME_MAX
    
    to maintain uniformity of maximum length of file name, through out
    glusterfs, use NAME_MAX.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit fe3d249f1aec607aed5895d66a869620ba30f9cf
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:32 2009 +0000

    cluster/afr - replace ZR_FILENAME_MAX by NAME_MAX
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit d538b139fb197d7397e45b4bc5a9446823186568
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:31 2009 +0000

    cluster/unify - replace ZR_FILENAME_MAX by NAME_MAX
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bf70c1361f8eb82607f5fd9396edfad62ced7b89
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:30 2009 +0000

    protocol/server - replace ZR_FILENAME_MAX by NAME_MAX
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit f0314a6b781126dbbb25edf37460f68750d88896
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:29 2009 +0000

    protocol/client - replace ZR_FILENAME_MAX by NAME_MAX
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8fae42f8203df6a49b33eb7341def9782251f269
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:28 2009 +0000

    storage/bdb - replace ZR_FILENAME_MAX by NAME_MAX
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 28760cc3d37318e7e90ec65bf2ce6376916e8a3e
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:27 2009 +0000

    storage/posix - replace ZR_FILENAME_MAX by NAME_MAX
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 6abd0c49267973f57b8cf98f25e61ec587b2533a
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jul 6 05:47:26 2009 +0000

    libglusterfs/call-stub - replace ZR_FILENAME_MAX by NAME_MAX
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a70f38f15a115cc258f297d6634dab90bc30f4dc
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Jul 6 03:39:19 2009 +0000

    Updated man page with log-server options
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c78658544870e06ff399b9cee7ef22a1c18e5e4d
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Jul 6 03:39:11 2009 +0000

    Added new man page for mount.glusterfs
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 552c392449eb5ed3d249bea8d4467f817781caf0
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Mon Jul 6 03:39:03 2009 +0000

    Modified mount.glusterfs to print usage in case of no mountpoint provided and "-o" options to be agnostic of their position.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 7261ef381a2c3c7bf5ef0ecd2392f7cab9e60e37
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sat Jul 4 05:10:28 2009 +0000

    mem-pool: Do not perform chunkhead2ptr on MALLOCed memory
    
    Memory allocated from the heap instead of the mem-pool
    need not under go the chunkhead to ptr conversion when returning
    to a mem-pool user since this address can be use directly.
    
    This fixes a crash in io-threads.
    
    Ref: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=102
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c3f24c43a4cfb576a23de689c6107c4479e51307
Author: Csaba Henk <csaba@gluster.com>
Date:   Thu Jul 2 11:03:57 2009 +0000

    booster: automake 1.11 compatibility fix
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 94f62eb4d50c7917c7c1ca36386045b110b30eda
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jul 2 00:52:28 2009 +0000

    libglusterfsclient: Use O_ACCMODE for access mode checks
    
    Ref: http://www.gnu.org/s/libc/manual/html_node/Access-Modes.html
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 52d0ae7bc35680bcec094be39f119d966ea9a77f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jul 2 07:08:47 2009 +0000

    Print volume file after printing other details.
    
    This makes the log format compatible with earlier
    versions. Fixes bug #105.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ebfcb5368c225aed11c007aee1e362c5d345c2b0
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Jul 2 01:55:29 2009 +0000

    performance/write-behind - bug fix in open() and create().
    
    open() & create() calls should reset frame->local to NULL.
    
    bz# 104
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4d176f44ce7b251794159371232954f810cfae02
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 1 00:49:54 2009 +0000

    server protocol forget cleanup
    
    as client now doesn't send forget at all to server, it should take care
    of forgetting the inode when there is a successful unlink and rmdir fops.
    
    also cleaned up unwanted forget fop's code.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8301e2ffc44beb09cec7e01aa8672e857c6c3977
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jul 1 00:47:29 2009 +0000

    cleanup client_forget
    
    upon detailed inspection of 'forget' behavior, it became evident that
    forgets from client should not goto server side, as server keeps its
    own purging mechanism to forget its inodes.
    
    if client sends all forget to server, many highly used required inodes
    may get freed up (it will surely effect io-cache buffers on server side)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit e2a6e26f446605cabf89a402a851cfaf5c5f6036
Author: Harshavardhana <harsha@zresearch.com>
Date:   Wed Jul 1 04:13:09 2009 +0000

    rpm spec file updates (removed mod_glusterfs and respective dependencies)
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c284d5e73760aef176eefa25ee2054a67662bf98
Author: Harshavardhana <harsha@zresearch.com>
Date:   Wed Jul 1 04:13:29 2009 +0000

    fuse 2.8 support for xlator/fuse
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 5feb0ccb6efc006b2b17d29509b63a41fa14293c
Author: Harshavardhana <harsha@zresearch.com>
Date:   Wed Jul 1 04:13:23 2009 +0000

    fuse 2.8 version check at configure level
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 88f907af098c2876ca8777783098dae9ad624540
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 30 17:48:59 2009 +0000

    build warning fixes
    
    integer typecast warnings fixed
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 9d16a33e6171adf7512df839af6f6ffbab96799c
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 30 13:50:54 2009 +0000

    enhancement in write-behind
    
    Write calls should not be pushed to background only when the
    mandatory locking is enabled, in all other cases (eg: O_SYNC,
    O_DIRECT etc), we should not be 'caching' any data, but the
    calls can be pushed to the background.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 193b0e696fb7612998e23e21628023e9fffd08ee
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 30 17:08:50 2009 +0000

    version changes in GIT repo to differentiate between branches
    
    package-version: because master is undergoing changes for 2.1.x release,
    protocol-version: because of addition of mops 'log'
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 141d78e170b1e35b8897fe583cb5955646c8c211
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Jun 30 00:15:34 2009 +0000

    client_xattrop: use dict_allocate_and_serialize during serializing xattr
    
    - though the previous commit fixes bug #29, this patch fixes bugs
        arising in similar situations where xattrop is initiated by
        xlators other than afr.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit eeeffd41703003be30b3f1811fa54f5f8047ed73
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Tue Jun 30 00:43:56 2009 +0000

    cluster/afr - use different dictionaries for sending xattrop requests to each of the subvolume
    
    - This patch fixes bug #29.
      - Using separate copies of dictionaries also eliminates a potential bug in a
        setup consisting of afr with a posix and client, each having io-threads on
        top as children. Since posix_xattrop after performing required operations
        on the xattr array passed in dictionary, sets the result at the same key
        and in the same dictionary passed as input argument,
        there can be race conditions where in the results of the operation on
        posix-child can be sent to the other child as input argument for xattrop,
        which ofcourse is wrong.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a3ece0caa52ad2eacf8a8691aaca53295cde972f
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Jun 29 09:38:29 2009 +0000

    booster: Fix build problems with various libtool versions
    
    We've been facing a problem on some test systems where the
    booster.so is built by libtool as an executable rather than
    a dynamically loadable library.
    
    This problem is probably caused by it seeing a _init function in
    the source. This is the name of the libc initiliazation
    function so it could be the source of the problem.
    
    In any case, ld-preloadable libraries must not have a function
    called _init, instead they need to have __attribute ((constructor))
    as the attribute for any and all functions the library wants
    executed before the program's main(). Our earlier approach was
    inherently problematic.
    This commit also cleans up the booster Makefile for better
    build behaviour. Credit: Harsha.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 304e4274ca9b0339539581c5413e3339078c1182
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Jun 26 13:05:00 2009 +0000

    libglusterfsclient: Fix glusterfs_mount-vmp search deadlock
    
    It is possible that the only translator in the libglusterfsclient
    tree is the posix. In that case, inside gluster_init, the graph
    init routines will need to call lstat on the posix subdirectory.
    
    Since even the glusterfs stack is running over booster, those
    calls will also first require vmp searching. BUT, the vmp lock
    is the same as the mount lock that was already taken when we entered
    glusterfs_mount, so a deadlock occurs.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit d6ce087395220ea0b6e4bff4d3e561de624447a3
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jun 25 14:31:30 2009 +0000

    booster: Another attempt to fix 32 and 64 bit interoperability
    
    With this patch, we might have finally arrived at a solution
    to the problem of function definition conflicts between
    our functions and those of libc while over-riding the libc versions.
    
    This commit defines functions which do not conflict with libc,
    then it uses libc's own macro to redirect/rename these functions
    to the actual sys call names in the binary.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit f5ec3b6a9597bb50fe4d8b6a4c9d92a3b46306dc
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jun 25 14:31:29 2009 +0000

    libglusterfs-fd: Simplify gf_roundup_power_of_two
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit e3e880180165efffbc0866eeda2154004f7d64f5
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jun 25 14:31:28 2009 +0000

    booster: Remove gf_fd_unused_get2
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 76aa99422562a500c3b82cb826ce582576065a83
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jun 25 14:31:27 2009 +0000

    booster: Add new booster-specific fd-table
    
    The reason we need a booster specific fd-table is because
    the libglusterfs fd-table has come to a point where it is
    optimized for libglusterfs-style of fd allocations.
    This conflicts with the way booster requires fds to be allocated
    so this commit brings in a re-based version of a booster-specific
    fd-table written by Raghu.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4fd96085c5a029e7be9e24e0c33b13268b290d6b
Author: Erick Tryzelaar <idadesub@users.sourceforge.net>
Date:   Fri Jun 26 13:36:00 2009 +0000

    Fix some trivial typos.
    
    I noticed that there were some minor spelling mistakes/typos in some
    of the source files. This patch fixes the ones I've found.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 75da95d8419dd209d879194e1b73a6190129a504
Author: Harshavardhana Ranganath <harsha@gluster.com>
Date:   Thu Jun 25 23:12:00 2009 +0000

    Added new options for log-server and log-server-port
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 66224718ab57238e16b30d8b461c380d64df237c
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 25 16:11:44 2009 +0000

    version check between client/server made more specific to protocol only.
    
    This patch is a step towards giving compatibility between the versions of
    GlusterFS. Now onwards, the protocol-version won't depend on release
    versions. In general, multiple glusterfs versions can have common
    protocol-version.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit dc321571317b911faa31eed8b3bd4ce396963179
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Jun 24 18:31:10 2009 +0000

    dht_readdir_cbk: use stat attributes in the READDIRPLUS dirents to
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 622636c6e18a1013261bf924084d7a78a7cc86b1
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Jun 24 18:31:09 2009 +0000

    rename dht_first_up_child to dht_first_up_subvol
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ad7909163aef151b15638110119fb9adaf3dbcee
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Jun 24 18:31:07 2009 +0000

    posix_readdir: fill stat structure into dir entry
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c4cf372fbc70e7354597692b385691149f163d2a
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Jun 24 18:31:06 2009 +0000

    gf-dirent: add support for stat attribute in dir entry (to work like
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 5052d8e23d2e3b33a185d3bd5f9eca8264238acb
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 24 13:31:11 2009 +0000

    mount script to take arguments like nfs
    
    Ref: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=37
    
    earlier instead of path, it used to take port number, which is an
    option (-o server-port=<port>), now.
    
    new syntax is
    
     bash# mount -t glusterfs <hostname>:<path/key> [mountpoint]
    
    [This patch is backward compatible with earlier syntax]
    
     bash# mount -t glusterfs <hostname>:<port> [mountpoint]
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c15ab84a1dd687e9e97b17fb7250ba945857026e
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 23 13:41:26 2009 +0000

    server-protocol: interpret the 'op' value properly when a packet is received.
    
    Ref: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=35
    
    The check done earlier was not handling the case when a 'op' is == MAX_VALUE (which
    is not defined), and used to skip to the next array (like gf_mops[MAX] == gf_cbks[0])
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 60aaf35a044357b3a639e0d8f46102a3272b5c65
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Jun 23 10:13:04 2009 +0000

    check if the 'key' is the volume file name itself.
    
    With this patch, one can fetch any volumefile which is not pre-defined in
    volume file with 'option' in server protocol volume, instead clients can
    fetch the volume files based on the key name itself [From the confdir only]
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1bd3a412d01c2d0cbbcf91e7983e2d4c9c8bbec4
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jun 22 19:26:06 2009 +0000

    mount.glusterfs.in correctness in case of duplicate mount
    
    mount.<fstype> script/program should return success in case when it finds
    duplicate mounts. It was returning failure earlier. Someversions of
    automount programs had issues with this behavior.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit e7b8470623ff647a6fe2740b555bf1ce2dae7d21
Author: Csaba Henk <csaba@gluster.com>
Date:   Tue Jun 23 04:25:22 2009 +0000

    Fix typos in my previous commit 6010e2a4e
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 384ee312ba44e3d8c456ab0c93d74274597d71f4
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Jun 22 07:53:03 2009 +0000

    glusterfsd - build proper mount/fuse structure.
    
    while appending mount/fuse to a translator tree, make sure
    that <xlator_t-of-fuse>->next points to the first xlator in
    the list of xlators and not the subvolume of mount/fuse.
    
    NOTE: tree traversal should always happen through <xlator_t>->children
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 6010e2a4e14a850469f0977e43245e64a33301fa
Author: Csaba Henk <csaba@gluster.com>
Date:   Mon Jun 22 00:56:13 2009 +0000

    fuse: instead of having a fixed option list, assemble it using "fuse_opt_add_arg"
    
    This makes it easier to adjust the option list, and also reduces redundancy.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 96896689b4e774af6460905b30adabec6e1fa540
Author: Vijay Bellur <vijay@gluster.com>
Date:   Sun Jun 21 01:28:51 2009 +0000

    Avoid accessing local unconditionally in trash_common_*_cbk functions.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ae1201785ca7f14690d19c533bb8a7f5150ea29b
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 18 15:58:22 2009 +0000

    local->loc should be filled in dht-mknod()
    
    local->loc should be properly filled while creating a linkfile. otherwise
    this causes the segfault in underlying volume layer (mostly client-protocol).
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 93c8ce0e3fc295087775185c0f8594f06244098d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 16 05:25:17 2009 +0000

    Add command line option to specify central log server.
    
    Added two command line options:
    
    --log-server SERVER
    --log-server-port PORT
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit cc931ebf51e7a810e08155ba0b916b10f25d7f16
Author: Harshavardhana <harsha@zresearch.com>
Date:   Tue Jun 16 10:34:44 2009 +0000

    Remove the trailing "/" which fails build with new version of automake
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a3864e8054cd047a004c7705c27b64b28912d947
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Jun 18 14:21:15 2009 +0000

    making dht and nufa's 'min-free-disk' option to take both percent and disk-size
    
    Originally from Paul Rawson <plrca2@gmail.com>
    
    http://patches.gluster.com/patch/391/ : patch re-submitted with patching guidelines.
    
    cluster/distribute, and cluster/nufa uses new option PERCENT_OR_SIZET for its
    option 'min-free-disk'.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit d3e1a3d453c358f2b5a6b86805767c8361fde2ee
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 17 20:58:20 2009 +0000

    adding an extra xlator option type, GF_OPTION_PERCENT_OR_SIZET.
    
    Originally from Paul Rawson <plrca2@gmail.com>
    
    http://patches.gluster.com/patch/391/ : patch re-submitted with patching guidelines.
    
    with this patch, the xlator volume options get another type which can take
    arguments either in 'percent' or in 'bytes', which is useful in many cases.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bb451c37bc05c8a33130e6b93020378d742f0ca2
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jun 18 05:33:27 2009 +0000

    libglusterfs: Prevent gf_fd_put'ing of unallocated fd
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 617de1c718d4f082c8a8cf86c258284f5c918b2c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jun 18 05:33:20 2009 +0000

    libglusterfs: Chain newly allocated fdentries.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 804e34cc4955cf5f176e70381da08cc617b6f79b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu Jun 18 05:33:13 2009 +0000

    libglusterfs: Change GF_FDENTRY_ALLOCATED constant
    
    This change is being brought in so that we can
    
    differentiate between fdentry_ts when debugging using
    gdb.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 80485e438268251f734936139d8239c59f70de54
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Jun 17 20:56:52 2009 +0000

    change the log level of disk full message in dht-diskusage
    
    the current msg is getting printed in warning level. Instead changed
    it to debug, as the msg specific each node being full is already getting
    printed in higher priority, hence this msg looks excessive.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 84bfdfee65be197a8aeb8d8378e135147152761f
Author: Harshavardhana Ranganath <harsha@zresearch.com>
Date:   Tue Jun 16 11:04:10 2009 +0000

    Booster build should not depend on if mod_glusterfs is disabled
    
    Thanks to Erick Tryzelaar
    
    Sending this patch on behalf of Erick Tryzelaar <idadesub@users.sourceforge.net>
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 7437305962f485074cf643fec8161925e9bd5225
Author: Vijay Bellur <vijay@gluster.com>
Date:   Wed Jun 17 11:52:13 2009 +0000

    Removed the swap being done for __noswap functions.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 9286a599f62289e8630ee28ea7da7308396d8fdf
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Jun 5 17:51:59 2009 +0000

    change ha-statfs() to handle the case of loc->inode being NULL
    
    This fix is needed in ha_statfs(), as the current code doesn't handle
    the case of loc->inode being NULL, which is a valid case in statfs()
    [Remember its stateless call]. This was causing 100% disk full logs in
    distribute or nufa as the logic of checking whether the subvolumes have
    enough disk space on them used to fail.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bb4e14b213a39e9d403be9790ef0a75388496dee
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Jun 15 13:05:52 2009 +0000

    client: Replace saved_fds dict with list
    
    Thhie change removes a huge inefficiency in file open
    path where every open resulted in dictionary operations
    in order to let the client maintain a list of fd_t's being
    used over a particular client context.
    
    Resolves: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=16
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit efcce990960fb91d422630fc7b310b216a500fed
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Mon Jun 15 13:05:39 2009 +0000

    libglusterfs: Turn fd-table O(1)
    
    This commit reduces CPU usage of gf_fd_unused_get drastically by
    making it O(1) instead of O(n).
    
    Related to: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=16
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 7006ae207c9e8ab9685d8e2e7455bd4e3b217c97
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Jun 15 04:12:42 2009 +0000

    write-behind: fix memory corruption
    
    - wb_sync did not set local = NULL after stack_wind. It also used to free
        local if its not NULL as part of cleanup process. Hence there was a double
        free in STACK_DESTROY done in wb_sync_cbk.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4eac667d30bce0768bc7e220614f703d45ee6f81
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Jun 15 04:12:21 2009 +0000

    write-behind: check for memory allocation failures and take appropriate action
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8f29c29480ad4f716229d480ada7fc2b6711f22e
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Jun 15 07:16:31 2009 +0000

    Do stat to check mode of the export directory in storage/posix.
    
    Doing an lstat means init fails if the export directory
    is a symlink pointing to a directory.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit e298a2183a8a294abda9c656879dc30f6c17f027
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Jun 15 00:02:57 2009 +0000

    booster: fix build error in fcntl implementation.
    
    - F_DUPFD_CLOEXEC is defined only in linux kernel versions >= 2.6.24
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c3cf6a57c0b241fa768a57ee2fb294196d03f4a0
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Mon Jun 15 02:58:36 2009 -0700

    io-cache: fix warning by initializing conf = NULL

commit 65f52bfa965bcffca1157a3ce0711133dc28161b
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Mon Jun 15 02:57:25 2009 -0700

    read-ahead: fix warning by initializing conf = NULL

commit 26fbb96e454df1844fc73c1122c08c8ae405f824
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Fri Jun 12 05:11:53 2009 +0000

    libglusterfsclient: Call inode_lookup to prevent pruning
    
    This bug shows up while using unfs3 with replicate. The absence
    of an inode_lookup on a looked-up/created inode results in it
    getting pruned from the inode table. Consequently, a subsequent
    lookup for the inode results in a different inode number being
    returned by replicate. This breaks unfs3 because it tries to remember
    the inode numbers returned by two different stat-family calls.
    
    Resolves: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=11
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 7aa062466f34cd1eee911d34bdb87591d410c399
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed May 27 17:50:32 2009 +0000

    strict check of extended attribute flags while opening a striped file
    
    Added a fd_ctx structure for stripe, which takes care of understanding the
    extended attribute flags, and opening the right blocks in order (to make
    sure the read/write operations happen in order).
    
    Helps to handle situations like accidentally adding subvolumes to stripe, etc
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a20d4929663ccbfa45d574d62240a5277b47ab39
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed May 27 17:49:10 2009 +0000

    stripe: don't allow entry modification operations when any node is down
    
    if entry modification operations (like create/mknod/rename) happen when there is
    a node down, there will be inconsistency in striped fs. rather than curing it,
    prevent the issue from happening
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit d918b28cf3df2826656fef868f1825f4e6c45723
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Wed May 27 17:46:29 2009 +0000

    stripe cleanup
    
    stripe.c:
     indentation cleanup
     log messages cleanup
     coding standard guidelines
     removed ERR_ABORTs
    
    stripe.h
     moved the structure definitions here
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1125e8cbc072753fab78ba735bed3f29db61fcc4
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jun 11 01:46:04 2009 +0000

    io-cache: handle memory allocation failures
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 180cfc0c4b6b9a46da35a536a565f010babfa4a7
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 9 05:08:59 2009 +0000

    Initialize central logging in glusterfs main().
    
    Modified from patch 522 (made a function extern) -- Avati
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 181ab58c6adeda6f99eb9330ed8ce720ab0f2818
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 9 05:09:01 2009 +0000

    Implemented LOG MOP in server-protocol.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 2943c77d88eccc195c59ded0aa9a377fcef906d9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 9 05:09:00 2009 +0000

    Log to a central server.
    
    Several functions to support centralized logging:
    
     - create a logging thread upon init
     - gf_log submits log messages to the logging thread which
       in turn sends it to the server using the MOP log
    
     - on the server side, log messages from a client are written
       to the filename <log file name>.client-<transport-identifier>
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit e7e6144a7688b35255ef5d69b060bd90e319679f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 9 05:08:59 2009 +0000

    Functions to store a central log flag in TLS.
    
    The flag is set in TLS so that a re-entry into
    gf_central_log does not deadlock.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit f7ca417394aeb5a8c2144e3b2ae6493ef172b32d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 9 05:08:59 2009 +0000

    Include glusterfs.h in dict.c
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 7db5c60ded012414f323029da263979e20215e5f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 9 05:08:58 2009 +0000

    Implemented LOG MOP in client-protocol.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1a6989613914cc86a64c3eb21cfddba15ce372d9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Jun 9 05:08:58 2009 +0000

    Added MOP log to libglusterfs/*
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 77d8cfeab52cd19f3b70abd9c3a2c4bbc9219bff
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jun 11 08:47:06 2009 +0000

    Do not fail over readdir in replicate.
    
    If readdir fails on a subvolume, do not
    fail-over to the next subvolume, since the
    order of entries and offsets won't be same
    on all subvolumes.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 998a1e0f740b6730f7885ad8c74afaad503d3256
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jun 11 08:46:40 2009 +0000

    Do itransform on every entry in readdir_cbk.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 3b99c6d82f9259db54f2d2d0a2520f88e7b12843
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:02:27 2009 +0000

    booster: fix memory corruption in booster_cleanup
    
    - calling glusterfs_umount_all leads to memory corruption.
        hence commenting out for timebeing.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 943a38e9f8beaaaa7fe741398c573fc458037723
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:02:15 2009 +0000

    libglusterfsclient: reset the vmplist and vmpentries to 0 in glusterfs_reset
    
    - Generally glusterfs_reset is called after fork in child to empty out
        vmplist.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4a31c02a568464cc4030b20cefe71ccb007b45bf
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:01:59 2009 +0000

    booster: implement fcntl.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 5dcbc0563f10cf68db2af10665953425ed262906
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:01:45 2009 +0000

    libglusterfsclient: implement glusterfs_fcntl.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8ebb4499d0bf568ea58562708f8baaedfe9fa58a
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jun 11 04:59:00 2009 +0000

    booster: implement readdir_r and readdir64_r.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 75f555fd89d2bf3dbd5aceeb112b748f4a8966e3
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:01:16 2009 +0000

    libglusterfsclient: implement glusterfs_readdir_r
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ac53b60bc29831cecfa7d5919278afc6c7053392
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:00:59 2009 +0000

    libglusterfsclient: update offset in glusterfs_read_async_cbk only if offset stored in fd_ctx is used.
    
    - this helps in implementing sendfile(2). manpage says that
        "If offset is  not  NULL,  then sendfile()  does  not modify the current
         file offset of in_fd"
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 157469a43272d06f63f0d4eaa15bd994c9cc0ba0
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:00:44 2009 +0000

    booster: call glusterfs_umount_all during cleanup
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit e0650e53ca9df6e86272efb0a2e2587e42f24a53
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 07:00:26 2009 +0000

    booster: implement sendfile.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ee22651f34b467859959b17b881da465001c6bc8
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jun 11 04:58:30 2009 +0000

    libglusterfsclient: implement glusterfs_sendfile.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 29a3619d6bb5680213c817b13dad7d8ad6e2903b
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 06:59:50 2009 +0000

    libglusterfsclient: add glusterfs_umount_all.
    
    - unmounts all the entries in the vmplist.
      - this api helps booster to cleanup all the mounts in a single call.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 82130d7ef5e4e4842dba44f0283336d98035a590
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 06:59:34 2009 +0000

    libglusterfsclient: make glusterfs_umount thread safe
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 54976b687227e5e12d4138e29a64640318a2db3b
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 06:59:14 2009 +0000

    libglusterfsclient: make glusterfs_mount thread safe.
    
    - this patch also checks for the presence of vmp before adding
        an vmpentry.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit dfff100cc31ad1343d8ecb76b72ec650c2b8b5b4
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 10 06:55:32 2009 +0000

    booster: remove mount table which maps a path to glusterfs handler.
    
    - if there are any glusterfs mounts(real, not virtual) which are not specified
        through booster-fstab those mounts are also added to the virtual mountpoint
        list of libglusterfsclient. This also removes the mount table in booster and
        all the mounts whether they are real or virtual are handled by
        libglusterfsclient.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8f4e5ace5d95535266a0ad1d6cec5f59325148c4
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Jun 11 04:36:14 2009 +0000

    Filter out changelog xattrs in replicate.
    
    The AFR changelog xattrs, "trusted.afr.*" are now
    filtered and prevented from being visible on the
    mountpoint.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1c4d58fe57162a5247356dc95aa6204f26cbf4fe
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Jun 10 01:25:38 2009 +0000

    io-threads: Fix missed notification in sem_timedwait
    
    We're performing a calculation for skewing idle time
    that resulted in a timespec.tv_nsec value becoming larger than
    1000 million or less than 0, forcing sem_timedwait to return
    with an EINVAL instead of waiting for a request notification
    from sem_post in iot_notify_worker(). This resulted in a missed
    notification that resulted in a hang followed by a timeout
    on the protocol/client side.
    
    This commit avoids the over- and under-flow in tv_nsec by
    skewing the tv_sec value instead.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bd2b529fd3d1965ccfe8cc03f9223ed1e98f7e79
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jun 11 01:45:45 2009 +0000

    read-ahead: handle memory allocation failures
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit b930b38a2ab16b3d25b4bf2441e584f7fc882a17
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jun 4 06:14:31 2009 +0000

    read-ahead: return with error code EBADF for fops on fds without file set in their context.
    
    - since a successful open/create will _always_ set a pointer to ra_file_t in
         context of fd, this fix makes sense.
       - an example of operations on bad fd can be afr sending read on the child
         which was down during open.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 3f4362cedee499beb6a872b3dbb3ac920aa51d21
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Jun 4 06:13:58 2009 +0000

    read-ahead: unwind with a return value of -1 and error code of ENOMEM on memory allocation for ra_file in open/create
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit cc2c0b53566584279f624d49bd1cb70936bbf5ea
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri May 29 16:08:04 2009 +0000

    removed unused option 'page-size' in io-cache
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 5b90d71324802e88c72947b807884036cfd32b78
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Jun 8 07:18:18 2009 +0000

    Print PID after daemonizing glusterfs.
    
    PID used to be printed before glusterfs became a daemon,
    which is incorrect since becoming a daemon involves
    forking and thus the PID changes.
    
    Fixes bug #8.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 7c42fd0f2059329d620225962146cdd0414a8f69
Author: Anand V. Avati <avati@dev.gluster.com>
Date:   Tue Jun 9 06:17:37 2009 -0700

    configure.ac: print summary to stdout

commit e98d3808478c09fb4058a53a7dc215d8fae1553f
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Jun 3 00:38:26 2009 +0000

    server-helpers: cleanup connection only if there are no active transports.
    
    - thanks to Ioannis Aslanidis <iaslanidis@flumotion.com> for reporting.
      - breakup the server_connection_cleanup into smaller procedures.
      - do following operations in a single atomic operation.
          1. conn->active_transports--
          2. collecting pointer to lock table and all fds if there are no active transports
        this will avoid any race conditions.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1d940e5ab2baeb901792f4b60a3abf3fcec19491
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Jun 3 02:17:19 2009 +0000

    Fix crash in afr data self heal. Bugzilla ID: 3
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a4a0054caee6c75ae442d4984b95bf9753eded36
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Jun 3 01:05:42 2009 +0000

    libglusterfsclient: Avoid dirent copies in readdir cbk
    
    We can avoid memory allocation, de-allocation and
    data copies by just using the entries passed to us from
    a lower layer and by de-linking the entries from the original
    list.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4c0b91a5a045e3f03a049320d26542ab9fec4745
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Jun 3 01:05:34 2009 +0000

    libglusterfs: Add empty and NULL dirents list checks
    
    These checks are needed in case a higher layer intends to
    delink the dirent list and passes a NULL pointer to
    fop_readdir_cbk_stub for the entries parameter.
    
    Consequently, the gf_dirent_free must guard against an empty list
    because the stub that is passed to it mgiht have an empty
    dirent list.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 08d46effee3b5e07b89a3a04251714383cf02eec
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Jun 1 17:58:41 2009 +0000

    ib-verbs error log enhancement
    
    Earlier it was thought that only not having 'opensm' running will cause
    handshake errors in ib-verbs.
    
    Recently understood that even having a wrong 'ib-verbs.port' option can
    also cause the same behavior, and it took more than 5-6 e-mail iterations
    with the user and lot of brain cycle in support team to understand the
    problem. Made the log message more descriptive, so user can be find the
    cause, or can send us email without wasting time.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 2dc70c22bdd25362a95f19ab551d39e99f76ebfb
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 29 13:52:07 2009 +0000

    io-cache: prevent frames from getting woken up while page is getting validated
    
    1. A page will be put on the inode waitq if the 'freshness' has to be verified with an fstat()
    
    2. while the fstat is in transit, other calls (like lookup) can update ioc_inode->tv, resetting the freshness (page still on inode waitq)
    
    3. Another read request on the same page, after the updated freshness, will wake up the page frames neglecting the fact that the page is also waiting on the inode (waiting for the fstat completion)
    
    4. once the page's frames are woken, the page becomes elegible for purging and can get destroyed for various reasons, leaving a destroyed page pointer in the inode's waitq
    
    5. fstat returns and hits the destroyed page pointer causing a crash
    
    The fix is to all together disable cache hits when any page of the same inode is under validation. The otherwise cache hit will now be subjected to the ongoing validation by getting queued to the inode waitq.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 834efc91985b7a572e5acd9be463eb8ffdf3ba11
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri May 29 16:09:05 2009 +0000

    unify getdents count reduced to 512 (from 1024)
    
    Thanks to Krishna <krishna (at) gluster.com> for pointing this out.
    
    When a unify self-heal of large directory (directory with lot of entries)
    is done, the getdents_cbk used to fail because of new limit of buffer size
    (128KB). Noticed that earlier it used to streach upto 4MB, hence the value
    1024 worked fine. By reducing it to 512, noticed, we can fit in well within
    128KB limit, and hence unify self-heal goes through.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 3c1fa49fb56c3a35f82bc25e4553431fe04f5231
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 28 04:43:05 2009 +0000

    libglusterfsclient: Increase readdir block size
    
    This improves the potential for pre-fetching a larger
    number of dirents. Consider that, with 255 chars as the max
    name length for each dirent, in the worst case scenario, where
    we actually have files with such large names, we're not getting
    more than 4 entries with the current block size of 1024.
    
    Generally also, increasing the size to 4k provides us
    with a higher chance that directories with low to medium
    number of dirents will be pre-fetched in a single readdir fop.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit b6434aadbe3e862815f4237fdf4c97284680a134
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 28 04:42:58 2009 +0000

    libglusterfsclient: Add dirent pre-fetching and caching
    
    The fop interface is such that we're able to extract more than
    1 dirent in a readdir fop. This commit now enables libglusterfsclient
    to read multiple entries on a glusterfs_readdir call. Once these
    have been pre-fetched, they're cached till either glusterfs_closedir
    ,glusterfs_rewinddir or glusterfs_seekdir are called.
    The current implementation is beneficial for sequential directory
    reading and probably indifferent to applications that do a lot of seekdir
    and rewinddir after opening the directory. This is because
    both these calls result in dirent cache invalidation.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1fea167f86ed4501ed01b5c678cddc7c815f1a5b
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 28 04:42:51 2009 +0000

    booster: attr_timeout: Read timeout from booster fstab
    
    In order to expose the timeout values for stat and inode
    caching, this commit introduces a new fstab option "attr_timeout"
    that defines the number of seconds for which a looked up inode
    or a stat()'ed structure is valid in the cache.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bc99744f209d2c6905f858e9ab44d09fb661e94a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed Jun 3 01:31:37 2009 +0000

    libglusterfsclient: Simplify inode and stat caching
    
    There is a mechanism for caching the inode numbers got from a lookup
    and a struct stat got from a stat or fstat but I wasnt sure if it worked.
    This commit simplifies cache updates and checks and the accompanying
    tests have made sure that the cache does work.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit f47f568aa0fd8d12c211e3b249fcf7a67ec56f9e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 28 04:42:37 2009 +0000

    libglusterfsclient: Allocate right sized structure
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a29ec1f1484902400f08b24ed777ea984923ffea
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sun May 24 23:05:26 2009 +0000

    booster: Clean-up handling of log/fstab env variables
    
    Handle two cases when deciding log/fstab file:
    1. It turns out that that strdup or strlen doesnt actually
    check for NULL before trying to do its thing with the string
    so it seg-faults on seeing a NULL char pointer.
    
    2. getenv can return an empty string if the
    env var was exported as:
    $ export GLUSTEFS_BOOSTER_LOG=
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit f888b3f5be4be893323b644dba0668ae3d40228e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sun May 24 23:05:18 2009 +0000

    booster: Eliminate gluster context creation race
    
    When multiple threads try to create a glusterfs context using the
    glusterfs_init function, those threads end up using the global
    vairables in the vol file parser in an non-synchronized manner,
    resulting in a seg-fault.
    
    There is now a big lock around searches and additions from the mount
    table in do_open. This lock granularity could be reduced.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 380cd4e6d296cde9d203ce6c4fa01be189fbf34c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Sun May 24 23:05:11 2009 +0000

    booster: Clear up env var usage
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit a7e5888508a2f08e6891eb5a472b7edf737e15da
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu May 28 20:12:05 2009 +0000

    bug fix in dht-diskusage when statvfs->f_blocks is 0
    
    This can happen when 'option export-statfs-size off' is given in
    posix volume. Caused divide by 0 error.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit f5d0e815b43b3957396dd6c4a768ba87db2ae9c5
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu May 28 02:46:45 2009 +0000

    Remove absolute path for init scripts.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 4e89da5054837a2266fe1732a309c341dd6cd663
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 26 09:02:29 2009 +0000

    socket: New option: Set receive and send buffer size
    
    ..and hope for a chance to improve performance on
    high speed links like 10GigE.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 23976ec1e8554963d5e6a868c3982a8baa3d361a
Author: Pavan Sondur <pavan@gluster.com>
Date:   Wed May 27 10:39:38 2009 +0000

    Fix mismatch in size of used buffer to prevent an infinite loop
    
    A mismatch in the size of the used buffer, between reading and then further writing caused an infinite loop and big files(1Mb, 10Mb etc) could not be downloaded through the lighttpd web service using mod_glusterfs. This is because the big file which is broken up into chunks, has a read and a subsequent write.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit b84ab58d8c849347fc6a337a4e897c365c0b08ae
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue May 26 05:02:27 2009 +0000

    Do itransform in AFR readdir.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 696428efb6195374bfd07c1b483871e1fdb68a55
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue May 26 05:01:35 2009 +0000

    Always do itransform of the inode number from the first up child.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 0af126294a1eeb89383a4e477962f908f003026f
Author: Anand Avati <avati@gluster.com>
Date:   Tue May 26 04:31:28 2009 +0000

    add booster_fstab.h in noinst_HEADERS to fix build breakage after 'make dist'
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 2951b04c7ac8a2888fffb2ebc127ecc1ec617d79
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon May 25 05:02:25 2009 +0000

    Preserve atime/mtime during data self heal.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 8b56178a7928bc7d30f408096303eaff3fe6d823
Author: Anand Avati <avati@gluster.com>
Date:   Fri May 22 03:33:41 2009 +0000

    fix crash in __socket_reset. Previously iobuf_p was an allocated pointer, but since introduction of IObuf it is no more. Now iobuf has to be unref'ed instead.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit abb075def55110f606ff43e64933afee61dea261
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:32 2009 +0000

    THIS: use xlator_init() for initializing xlators
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 6d5aff7bfd2403aa132d41c659c76abaf58f0503
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:31 2009 +0000

    THIS: add xlator_init() API to set @THIS
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bbce052d47e5f17a476379f5de6925ae795465bb
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:30 2009 +0000

    THIS: bootstrap @THIS in fuse thread
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bebe16ae8db873474d43d751cca484cca6ed2715
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:29 2009 +0000

    THIS: unify now uses xlator_notify for setting THIS
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 17cf09641d81f02094288ef9de52cdf720fc516f
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:28 2009 +0000

    THIS: protocol/client now uses xlator_notify for setting THIS
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit f0fed682ecca92c1ade5076637c4cbd450ce19f3
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:27 2009 +0000

    THIS: ib-verbs now uses xlator_notify for setting THIS
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ad3fdbb2e15e1590efe955c3561aff964c972353
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:26 2009 +0000

    THIS: socket now uses xlator_notify for setting THIS
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 61e343c72b384faa56e034750bd5bb5b4667681b
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:25 2009 +0000

    THIS: default_notify to use xlator_notify for THIS compatibility
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 9cec4a0a790cc74106f92375506d7a16e09bdb10
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:24 2009 +0000

    THIS: xlator_notify API to be used for propagating notifications with proper THIS setting
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 99bf8da4764f425ac4022c9854acbd4247b6fdfc
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:23 2009 +0000

    THIS: set appropriately in call stub resumes
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit b7c1bcb4ea5ddd498f04b178f60209abbc9f01ed
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:22 2009 +0000

    THIS: set appropriately in STACK_* macros
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 207fb347ed24716ac4f443bab2d1daeb9ae5ccf4
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri May 22 02:10:21 2009 +0000

    globals: add globals.h/c THIS: macro to access thread specific current xlator CTX: macro to access glusterfs global context (glusterfs_ctx_t)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit bd297be1d1fedc85d70b9b1f3e4d4aa7b9980c76
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu May 21 02:20:26 2009 +0000

    Check for returns when apxs fails and disable mod_glusterfs
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c7fd9f1df36a01ac9a1509d1001b0d259005b0f9
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Thu May 21 01:37:05 2009 +0000

    mem-pool,io-threads: Destroy mem-pool on deallocation
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ef7fcc0d7c2695ab3b10477b3e1290e43831da99
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Wed May 20 22:50:10 2009 +0000

    booster: Move fstab parsing into booster from libglusterfs
    
    This is another attempt at fixing build problems on Solaris.
    I am told that booster build is disabled on Solaris and I know
    that it is disabled on Mac OS X also. Getting it to work
    on both these systems is now on my TODO list, mainly
    because on both these systems, we can have a glusterfs client
    running without requiring FUSE.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 5bb6653c434c74b5f2d5b706f60f8d4149a40a2d
Author: Csaba Henk <csaba@zresearch.com>
Date:   Tue Apr 28 10:22:03 2009 +0000

    add xlator debug/io-stats
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit d734a305d534d6430d1401ec358100f28547ca09
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed May 20 13:36:01 2009 +0000

    add 'non-blocking-io' to the options array in sockets.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 0961d301dd74a133a16425b10be02787a499e453
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 12:42:31 2009 +0000

    io-threads: Use boolean enums instead of integer 1
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 693e4f912b618d35b85fe6521d87fb7f683421d0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 12:42:22 2009 +0000

    io-threads: Change mutexes/condvars to spinlocks/semaphores
    
    It seems that use of mutexes is resulting in pretty high thread
    sleep and wake-up cost. What is worse, if a worker thread has
    acquired a  lock, there is a possibility of the main glusterfs thread
    being put to sleep. We change the use of mutexes into spinlock.
    At the same time, we cannot anymore use condvars for notification since
    the condvar interface depends on mutexes itself. Semaphores come to
    out rescue. Luckily, even the pthread semaphores have a timedwait
    interface to allow our idle worker threads to make an exit decision.
    
    Further, it is possible that spinlocks are not available on all systems
    so all this is curtained behind #defines so we can fall back to
    mutexes and condvars implementation.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 62a920642a54eac6e4b24a3590f17d628202a210
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 12:42:14 2009 +0000

    io-threads: Reduce default max for threads to 64
    
    We've had complaints from users who've used
    autoscaling option with default settings for min and
    max threads, about high memory consumption because of
    the large default value for max-threads.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 9a916de3f35dbbfe4399696891a0937d650bf72e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 12:42:06 2009 +0000

    io-threads: Support mem-pool allocator for iot_request_t
    
    This commit brings in support for allocation of iot_request_t's
    in io-threads through the use of the mem-pool. We're hoping
    that the overheads of hundreds and thousands of small allocations
    can be avoided through this.
    
    The important point to note is that the memory pool is not
    for the translator as a whole but there is one small memory
    pool for each worker thread. Not only does that help us
    avoid malloc overheads for small allocations like iot_request_t
    but also avoid contention on the heap data structures when multiple
    threads want an iot_request_t from the pool.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ef0af3ca33a007f2aae2016cc27b6d828367c987
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Fri May 15 05:50:09 2009 +0000

    io-threads: Add graceful shutdown of worker threads
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit c22810911149506d972133c4e87dbcab01330daa
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu May 7 00:51:39 2009 +0000

    io-threads: handle memory allocation failures
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 7f001813bc04ede65b05d588f16e0a6c68a94cfe
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon May 18 08:19:10 2009 +0000

    Change errno to EAGAIN in readv/writev
    
    When mandatory locks are enabled and a read/write
    would block due to a lock and if the fd is opened
    with O_NONBLOCK, return EAGAIN (previously EWOULDBLOCK).
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a9d0be4f1b78d9c03e9379fc5cea0ead6114c1d0
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 04:34:11 2009 +0000

    mem-pool: Restructure mem-pool behaviour
    
    This commit changes mem-pool behaviour to return a directly usable
    address by performing the required adjustment on the address
    being returned.
    
    This is different from the previous behaviour where we're trying to fit
    into the requested size, the list_head*2 also. This is not efficient
    enough in terms of space but hopefully works better than not having any
    mem-pool at all. Besides, I am not comfortable with mem-pool meta-data
    and caller-useable memory area being the same because of the potential for
    mem-pool's data structure corruption.
    
    PS:
    Please do read the comments in the code for more info during review.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 25dc191c51efb97ec970b137edfe4557302b7357
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 04:33:58 2009 +0000

    mem-pool: Fix #define spelling
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3aea8a66a457349e19bde40eb33510edd0597cff
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 04:33:48 2009 +0000

    mem-pool: Remove hard coded value for pad boundary
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit acf28ed1ef3565ca1321fe9647d9b065a24fa46a
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 04:33:37 2009 +0000

    mem-pool: Fix memory leak in mem-pool init phase
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d71a5601fb2cf661d973a08a4cef9a15a9ec2363
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 17:57:02 2009 +0530

    booster: Fall back to remaining real_* functors
    
    It is possible that some of the real_* functors for stat
    family of syscalls are NULL. I've seen this on libc. In that
    case, this commit attempts to use any available function that
    performs an equivalent operation.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 87b938d02b51a0b4c864fc5deba1a1f177a05a4c
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 17:56:54 2009 +0530

    booster: Dont de-init fd tables on VMP-init failure
    
    In case the init procedure for VMP fails, we want to
    continue using booster through the old approach, which means
    leaving the fd-table intact.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9189418db9e50fa20c31ac5c7c5b6aaa16a9fa1e
Author: Shehjar Tikoo <shehjart@gluster.com>
Date:   Tue May 19 17:56:47 2009 +0530

    booster: Do not read info for non-glusterfs mount points
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c5b90f75951faddf55c61f2fe57f1c26070a63b6
Author: Harshavardhana Ranganath <harsha@dev.gluster.com>
Date:   Tue May 19 06:39:42 2009 -0700

    Appropriate changes to statvfs struct for Solaris host.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 35fc174ea3a37546d7c90be8fa6076b8f9416d73
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:24:43 2009 +0530

    libglusterfsclient: Comply with EEXIST rule on rename
    
    During a rename, if the new file exists, the old name needs to
    over-write the new name. We're returning EEXIST, which is wrong
    behaviour.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 95ce0a87f5fbb139f7002360d63a005bfb9c097d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:24:34 2009 +0530

    libglusterfsclient: __do_path_resolve: Fix pathname resolution bug
    
    In __do_path_resolve, we need to use the new_loc.path as the input
    for resolution rather than the resolved variable, simply because we're
    not interested in resolving the names that have been resolved, as
    pointed out by the variable name 'resolved'. Instead, we need to resolve
    new_loc, which stores the next component in the path to
    be looked up.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fe06790a3637c30dc8d5e0be7367f27ee24c36bd
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:24:21 2009 +0530

    libglusterfsclient: Wipe loc->ino in libgf_client_loc_wipe
    
    Not cleaning up the ino member of a loc_t results in SIGABRT
    in __inode_link because in some cases, the loc->ino is
    different from loc->inode->ino. This happens especially in code
    blocks which re-use a loc_t structure for pointing at different
    inodes/files. For eg, if a loc_t has been assigned an inode and
    an ino, and followed by a libgf_client_loc_wipe, then re-use of this
    loc in say libgf_client_lookup results the SIGABRT because
    libgf_client_lookup calls inode_link with the same loc_t. However,
    this loc_t has just been assigned a new inode pointer but the ino
    member still contains a previous inode's inode number. This difference
    in inode numbers results in an assertion failure, so the SIGABRT.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1279d7398c63bdad448cf0418579f6df1d9f6f34
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:24:08 2009 +0530

    booster: Add telldir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e3e7f850eda010ab8c84417e57a4fbace4073022
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:23:58 2009 +0530

    booster: Add seekdir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 358f5ba40866545ce240ed8fda77c4d2e57a4262
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:23:38 2009 +0530

    booster: Add rewinddir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e420eb2206aa773eb32f1a7146cba4d6da5d9d03
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:23:24 2009 +0530

    libglusterfsclient: Refine readdir entry parsing logic
    
    Here I am only refining the entry parsing code in order
    to clarify the exit conditions from the loop. There were
    a few workloads where this loop went infinite.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e1ae573f73d69fe1a244ed1493793961dd4cf811
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:23:14 2009 +0530

    libglusterfsclient: Add telldir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 35bf3f058473b61605fd28cd9cbee7726adedf9d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:22:57 2009 +0530

    libglusterfsclient: Add seekdir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit dddcf498610ebd332992e9600dd728cc87e6355d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:22:42 2009 +0530

    libglusterfsclient: Add rewinddir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit aeda0a31977e8da295b913e6a306ff01ccf0ce0a
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:22:29 2009 +0530

    libglusterfsclient: Revert and re-do readdir conformance
    
    This commit basically reverts the previous readdir conformance
    patch I sent a few days back. That commit had a completely retarded
    and broken way of maintaining per-directory dirent.
    
    It was broken for two reasons:
    1. Creating a wrapper structure around the directory's fd_t
    only for storing a struct dirent is not clean enough. This commit
    takes a better approach by storing the dirent in fd_t context.
    This dirent is valid only if the fd_t refers to a directory.
    
    2. That commit was made and tested under the assumption (..stupidity
    is a better word..) that only opendir call is used for opening a
    directory. That is not correct. Directories are also opened using the
    open syscall. The point is, glusterfs_open returns an fd_t and so did
    glusterfs_opendir. The previous patch actually changed opendir to
    return a new wrapper structure. That is fine, if we go by the POSIX
    definition of open and opendir because, they're both supposed to
    return different types, an int and a DIR*. However, in
    libglusterfsclient, all other code assumes that directory handles
    corresponding to DIR* and file descriptors corresponding to int types
    are the same type, resulting in use of the same locking and fd context
    addition/extraction code. So a directory opened using opendir returned
    a wrapper structure which went down into the libglusterfsclient stack
    where some function called a lock on the handle assuming it was an
    fd_t, since it is not and dereferencing of the supposed fd->inode->lock
    results in a seg fault.
    
    Obviously, this didnt show up till unfs3 used open() to open a
    directory and not opendir.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4f1a87a245b960f1cd1fb4fe40b4254ac3793213
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 18:22:19 2009 +0530

    booster: Supplement fstab option parsing
    
    Previous fstab option parsing logic was completely
    retarded and did not handle all cases. This fixes the situation
    so we now work without any problems.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a5301c874f978570187c3543b0c3a4ceba143c25
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Mon May 18 17:24:16 2009 +0530

    workaround for not including sys/cdefs.h -- including sys/cdefs.h breaks build on solaris and other platforms

commit 0346e3e889d854f6f96d9f9b162a8d65ddb35f52
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon May 18 03:02:54 2009 -0700

    Bug fix in pl_readv/writev to handle the mandatory lock case properly.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 49523c834f075007352d07bf09463af9499b59f5
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Fri May 15 03:56:22 2009 -0700

    client-protocol: Fix memory corruption in client_lookup
    
    - memory corruption was due to new members being added between allocation
        of buffer for serializing xattr_req dictionary and dict_serialize of
        xattr_req.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 254f770af6ae6ff207fc567b6576a31469c84f67
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Fri May 15 03:55:50 2009 -0700

    dict.c: make dict_serialized_length and dict_serialize to hold locks.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9669c70c901474dc21ef08e49478b5f5dead8f64
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Fri May 15 03:55:20 2009 -0700

    dict.c: Add dict_allocate_and_serialize
    
    - this procedure atomically allocates a buffer and serializes dict into it.
      - this procedure helps avoid memory corruptions due to race conditions where
        in new members are added into dict between allocating a buffer for
        serializing and actually serializing buffer into it.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit dec2674685da30d6cef157748bcf52454ec97208
Author: Csaba Henk <csaba@gluster.com>
Date:   Sat May 16 04:28:40 2009 +0200

    make getxattr fail with ERANGE if reply is bigger than what was requested
    
    Edited by avati: make the function signature of fuse_xattr_reply_buf() use 'const char *value' instead of 'char *value'
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b4651c4b8c7ebbcee7bfc7ef50afebf7e25d5744
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu May 14 00:21:02 2009 -0700

    apache/2.2/mod_glusterfs: port to use new glusterfs_readdir interface.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 43a568d732962c8e095d3072f672451bcbe95f47
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Wed May 13 12:46:29 2009 -0700

    avoid duplicate mounts while using mount.glusterfs
    
    This change is needed as the format of how the /etc/mtab entry of glusterfs
    mount looks is now changed.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ce653eadc2d13e9f4d3748d217ef7614539a2f34
Author: Harshavardhana <harsha@zresearch.com>
Date:   Fri May 15 02:39:15 2009 -0700

    modified init scripts to honour @prefix@
    
    fixes http://savannah.nongnu.org/bugs/?26581
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 11cae446e0c115bbfa5ee3e6b18ef0e2c45b84fe
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu May 14 02:12:20 2009 -0700

    Edited log message for --volfile-check
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 19a1ce89421b7f066168059e972c906b8c194e54
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Wed May 13 01:26:24 2009 -0700

    minor log enhancement in 'ib-verbs' transport.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 92a84f8c0f0925f85ad40db1212ff5ef0c1fc809
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Mon May 11 13:19:49 2009 -0700

    replace BIG_FUSE_CHANNEL_SIZE with 'this->ctx->page_size'
    
    Send the struct stat's  'blksize' variable same as GlusterFS's page-size,
    instead of BIG_FUSE_CHANNEL_SIZE.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4f7552c23bc4d0691062bd6a90fa76aa53bdf97c
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Fri May 8 01:33:02 2009 -0700

    default log file different per mount (or if server, per volumefile)
    
    This feature is required becuase when more than one glusterfs process
    is started with default log file, all logs will be going to same file,
    which after a while gets more confusing.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f4fbc7200c32c50501df7a84b4ddeb4eeb0f5525
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon May 11 11:25:40 2009 +0530

    posix: Fix build warning on incorrect type
    
    This fixes a build warning due to use of incorrect
    type for size_t, for Core 2 Duo.
    
    Extra fix from avati: change %ld to GF_PRI_SIZET
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5c1d9108c1529a1155963cb1911f8870a674ab5b
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Thu May 7 17:21:21 2009 -0700

    stripe init 'block-size' pattern parsing bug fixed.
    
    ref: http://savannah.nongnu.org/bugs/?26416
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 20e8fc7a61fd22af1657cffa674c287ad29a7699
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu May 7 04:16:28 2009 -0700

    scheduler-nufa: fix initialization of refresh-interval
    
    - refresh-interval was being reported as not provided in the options
        even when configured.
      - fixes bug reported in rt #1007
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 124f02ed49615e8337d249a2c56e95a5298a856b
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu May 7 05:05:03 2009 -0700

    Set op_errno properly in afr_flush.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b3f7efe247ad114b6071ba6a2d6816f783d4aa15
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri May 8 15:45:24 2009 +0530

    booster: Add fstab parsing support
    
    This commit changes the booster.conf format from a
    simple custom format to that of the /etc/fstab.c
    
    See booster_mount(..) for the mount options supported/required
    for LD_PRELOADing booster. I'll write a small help doc soon.
    
    This commit also brings in fstab parsing code into libglusterfs
    because Darwin libc only supports reading the hardcoded /etc/fstab.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5f4c102297bae265a7c9a16a86ee032ffbd44830
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri May 8 15:45:09 2009 +0530

    booster: Standardize conf file and env variable
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit adb56cb5e0f0d718764b25f1b37397be720f8750
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu May 7 15:02:09 2009 +0530

    backend-xattr-sanitize.sh: script added to extras/
    
    Run the script as:
    
    sh$ ./backend-xattr-sanitize.sh /data/export0
    
    and it will remove all the known stale xattrs on the backend files and dirs

commit babc4dfb08504e41a35cf06e8c297a19c87ac397
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu May 7 13:28:21 2009 +0530

    valid_host_name(): accept string lengths upto 75 chars (the limit accepted by glibc resolver)

commit fd2e7d9ebb94ccf5faf5c9d9891978e09fce0b05
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed May 6 05:40:15 2009 -0700

    symlink-cache: fix return value of readlink
    
    - sc_readlink wrongly returned strlen (link) + 1 when link was present in
        cache.
      - this fixes rt #828. Since fuse_readlink_cbk does link[op_ret] = '\0', there
        was a memory corruption.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 542d9ed6c1758df85fc0e252952cfb80669f4a70
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed May 6 08:59:21 2009 -0700

    fix in mount.glusterfs for proper direct io mode option.
    
    fixes the bug which causes GlusterFS not to have valid 'direct-io'
    option through mount command or /etc/fstab entries.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 92a84a43e057ce2448c235d3bf66a0b694338d65
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu May 7 11:59:23 2009 +0530

    protocol/client: indentation fixes

commit 2ff188571e94831b389f5677e06b94d11eb5fc62
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu May 7 11:06:34 2009 +0530

    protocol/client: removed conf->child

commit f9f5519b66a25651eb03de577f68d481abdd4c40
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu May 7 01:24:41 2009 +0530

    transport shortcut b/w client and server
    
    This patch makes the server pass back the transport pointer of the client. If the UUID matches, the client makes the local transport 'shortcut' with the remote transport (pointer received from server)
    
    The shortcut simulates a socket queue. Instead of serialized messages going over the network and getting queued in the tcp socket queue, the messages get queued in a transport specific queue picked by a polling thread.

commit 12eb832e255a1abb90434ab3e0d1e1632ae7ce03
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed May 6 14:40:45 2009 +0530

    fix log message from transport-timeout to frame-timeout

commit cba961e9f4ff3452f5e8e6152c632a258b737576
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed May 6 12:23:54 2009 +0530

    libglusterfsclient: Improve readdir conformance on re-entrancy
    
    readdir is supposed to be non-re-entrant only with respect to the
    given dir stream, not the whole process.
    
    What that means is the static struct dirent that we maintain in
    libglusterfsclient should be per-directory handle and not
    process-wide.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f82651ef4ff5a9e94fa9c0d1f9cf091345440b56
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed May 6 12:23:14 2009 +0530

    libglusterfsclient: Fix large directory reading bug
    
    As of now, we use 1024 bytes as the buffer for reading directory
    entries. If a directory as many files, then its possible that it does
    not fit into this buffer, thereby requiring more than one call to
    readdir. Now suppose the last bunch of directories fit more or less
    exactly int the 1024 byte buffer. If this happens, the offset
    extracted by the current logic(in libgf_client_readdir) never gets
    updated beyond the first entry in this last block, because the last
    block's first entry always remains same. This explanation is
    convoluted, I know, but I too found out the hard way.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8d1b62393b58ff3ac5b157e0adea15578c949bbf
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 20:45:48 2009 +0530

    booster: Use CONFDIR as booster.conf default location
    
    This commit changes the default location of the booster.conf
    file from /etc/booster.conf to a directory defined
    during the build process.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit faef6fded892c310a3debdce273a382286a4ec19
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 20:45:26 2009 +0530

    booster: Change booster conf env var name
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f6862d75d1ca50b12372d5f9c3e651d6f74c5900
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed May 6 11:43:33 2009 +0530

    afr self-heal: update file size of the returning stat buf with source file's size

commit 3f3dea5f23e2b49ac8ad14bf8dd34dfadf6a72f5
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue May 5 20:04:50 2009 +0530

    log level fixes in read-ahead

commit 9cb93f58be9d032bec12ca04275e84904bf22c0b
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue May 5 20:03:36 2009 +0530

    log level fix in storage/posix

commit f62628af61f5ef72c6af2b807c1bba71f291a366
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue May 5 19:19:30 2009 +0530

    io-cache logging level fixes

commit e9800f8915257f8e3fc94dea8257e20a5561dfd7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:57 2009 +0530

    libglusterfsclient: Add 0-byte size/count guards
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fe94d6e4992d7b7f2bcee73dfd2b0af76e1f2611
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:50 2009 +0530

    booster: Add lchown API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8a3495e7d4b2273746d9e38aefbae583131951ca
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:43 2009 +0530

    booster: Add remove API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bddbe5f7a4437fc4c295b7830fa2916011ab799a
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:37 2009 +0530

    booster: Add getxattr,lgetxattr API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ad8e8fa72f287da034027bf26fc1fbfb1437d47e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:29 2009 +0530

    booster: Add readdir64 API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c803febb9b013e384bcccf37a2c68dc90deea444
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:23 2009 +0530

    booster: Add statvfs API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fe6a39da3cd7370e9a7d9f7908e06cbdce64ce6a
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:15 2009 +0530

    booster: Add statfs API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4de7dc7151d307021177107fcf8dd636b306bb59
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:08 2009 +0530

    booster: Add lstat API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 13a58f94a781d91ab3d7854996df66c9802d972b
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:04:00 2009 +0530

    booster: Add fstat API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 938191c57f0ef3a657a764033f70df6595dc736c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:03:52 2009 +0530

    booster: Add stat API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cec18ef672700dea563a8c899170ece4730257e5
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:03:42 2009 +0530

    booster: Add closedir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit abeec15e1da0c40bee134253035af88739e09960
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:03:32 2009 +0530

    booster: Add readdir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 792cd732264d751895e8469e7c5f3cb172574180
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:03:24 2009 +0530

    booster: Add opendir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fc602c0c17064dfbd81d3d85141b55a40c45d8d9
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:03:16 2009 +0530

    booster: Add realpath API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e749da85ec67dfa62af5702d199b8f1bcc53d1d7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:03:09 2009 +0530

    booster: Add readlink API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1504e1d50c7efcf20fe55fc7db526bb1d364244a
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:03:02 2009 +0530

    booster: Add symlink API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 48e30d6715574c34bc760798e1657b5900129c25
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:55 2009 +0530

    booster: Add unlink API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 62b29b0db6f7d417a3281c3937bd5af20e1bf201
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:48 2009 +0530

    booster: Add mkfifo API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7d87f8f5ce56278f56427196b5e2c5e4c0be02ad
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:38 2009 +0530

    booster: Add mknod API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4311e7f01dc244baa1a1b8fc50f74a823dbd38c4
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:31 2009 +0530

    booster: Add utime API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 48ee90ab87cf0c01fee0188728d70d67c6724b97
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:24 2009 +0530

    booster: Add utimes API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit acac22c87374310544b3a4bb301e9bfa3ea26001
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:17 2009 +0530

    booster: Add rename API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 11cdc6e5282d4c7d906da3e20b50df78ddba2efd
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:10 2009 +0530

    booster: Add link API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9b012b098915c8bdbdcb8a4c38fb353fa39e82d4
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:02:02 2009 +0530

    booster: Add ftruncate API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e4e97f2bdaf6d98c5a133491efdffebb64fae4d6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:54 2009 +0530

    booster: Add fsync API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e6f4a6879a6f9bb11e6774182b211b57f1a827fa
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:47 2009 +0530

    booster: Add fchown API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8fa2a984c315418b940c481ea7729c00ed0b033a
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:40 2009 +0530

    booster: Add fchmod API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ad4f864c448a3bbcec67d3fb3c44e07993cd70e7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:32 2009 +0530

    booster: Add chown API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 13610ba31d3b5a60c4d03343438f696725558e65
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:24 2009 +0530

    booster: Add chmod API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 76aa5e491dc3577bf8471cb649fee7b3d0a3dc9d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:16 2009 +0530

    booster: Add rmdir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 93c3a887695fc4fa7a65d6556398cffcf22d099e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:09 2009 +0530

    booster: Add mkdir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 358d3e7f99ecdc48c044f11f9f6011805d061ec4
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:01:02 2009 +0530

    booster: Add log message
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 83ae751616ce18d3010664f13ac8b8ecf8dd313d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:56 2009 +0530

    booster: Clean-up pwrite64
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 00b1e268fb0d3696820bd2e849c42deebe80a3cd
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:49 2009 +0530

    booster: Clean-up pwrite
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6696009a6662cc77458246ffc3dccc22f8d6c185
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:41 2009 +0530

    booster: Clean-up lseek64
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 513a2d15c16a9b5c96ceb321bed08d34d659e12b
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:34 2009 +0530

    booster: Clean-up lseek
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 24b360d865dbf344f8369e656d282739f07c18e8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:27 2009 +0530

    booster: Clean-up write
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8cacf5455bc97e84f62605df60a6ae5f66b61a1c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:20 2009 +0530

    booster: Clean-up writev
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 0c86f9686f2c91ef8838972ad038ba0c587cd09d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:12 2009 +0530

    booster: Clean-up pread64
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2763f86eea23898501c5299f58edc37e2c1262e5
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 16:00:04 2009 +0530

    booster: Clean-up pread
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a35a80b79702d3a81a9d62fc200ae61c6ec67b74
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:55 2009 +0530

    booster: Clean-up readv
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 61201d40bc22f1299bc49202433664664ec23ce6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:47 2009 +0530

    booster: Clean up read
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f0bef18b788c8beadc4131c5a6534761857c7f46
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:40 2009 +0530

    booster: Support VMP-based creat
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d470dd599c8dbf609411e52e587ea5c171214b21
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:32 2009 +0530

    booster: Add VMP-based open support
    
    In brief, when an open is called the VMP-based open is called first.
    If that fails, the fallback is the Mount-Point Bypass(MBP) technique
    which uses entended attributes to determine if the given
    path is a gluster mount. If it is, it goes ahead to create a
    glusterfsclient handle. All subsequent calls to this real mount point
    get redirected to the glusterfsclient handle. The other fallback is
    the actual open syscall on the local file system itself. This happens
    when the absence of an extended attribute tells us that the path is
    not even a glusterfs mount point.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3364e5eb2d5f5110e86924112dfe3f10597c9c9f
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:25 2009 +0530

    booster: Remove fcntl.h from include path
    
    We define the O_CREAT, etc. flags so that we can remove fcntl.h from the
    include path. fcntl.h has certain defines and other lines of
    code that redirect application's open and open64 calls to the
    syscalls defined by libc.
    
    For us, thats not a Good Thing (TM).
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 313713a254e193623807d019f4c0e17e637ed316
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:18 2009 +0530

    booster: Integrate VMP-based mounting
    
    This commit brings into booster the use of VMP based operations
    which will allow users of booster to specifiy a VMP and use it
    for transparently operating on a glusterfs client context.
    
    Since applications are oblivious to booster's presence, because it is
    LD_PRELOAD'ed, we need to specify the VMPs and the corresponding
    options like volfile, logfile, loglevel, through a conf file.
    
    By default, this conf file is the /etc/booster.conf. This can be
    over-ridden through the GLFS_BOOSTER_CONF environment variable
    for the application.
    
    The format of the conf file is very simple for now. Each VMP is
    described on a single line with space separated fields.
    
    Format: <Virtual Mount Point> <volfile-path> <log-file> <log-level>
    
    <log-level> takes the string representation of the usual glusterfs
    log levels.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 42d5355a6221ea473372c891544e4cc7b265bbe9
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:11 2009 +0530

    libglusterfsclient: A Fix deadlock in ftruncate
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7eb61fb44986fc834a19d9f38754f1be54d07e09
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:59:03 2009 +0530

    libglusterfsclient: Conform'ify glusterfs_readdir
    
    This commit does two things:
    1. Changes glusterfs_readdir prototype to conform to the POSIX
    readdir().
    2. Uses a 1024-byte value instead of sizeof(struct dirent) for the
    @size for libgf_client_readdir. This allows even larger names to fit
    into a single readdir request to the server.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b48df70c58f52878d58f3e1a0adc870688cdfcdc
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:56 2009 +0530

    libglusterfsclient: Add VMP-based lchown
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit dec408299ea7a2cb9aa9aa3ea3a3c72ee79169de
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:48 2009 +0530

    libglusterfsclient: Add remove API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4353ba5cdf0dab29e30997ce5b67055c8f1e1cba
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:38 2009 +0530

    libglusterfsclient: Add lightweight path resolution
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e57175c0177ecc8b9ff80d3ce6c5f9a3f8248214
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:30 2009 +0530

    libglusterfsclient: Add lgetxattr API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d18d2550484f3d930557fed038a6bf9ffa23de48
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:23 2009 +0530

    libglusterfsclient: Add setxattr,lsetxattr API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 84d5566fab6daaffe3ad5da76d87a9c9e20e7170
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:16 2009 +0530

    libglusterfsclient: Make stat resolve all symlinks
    
    We want to resolve even nested symlinks when calling stat,
    therefore, we need to depend on realpath-like functionality
    and not just a readlink.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a0cd85c307f3576291829beb825323d43aeca7f8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:09 2009 +0530

    libglusterfsclient: Fix realpath operation
    
    This commit does two things:
    1. Ensures we go on to traverse nested symlinks by calling realpath
    recursively on the symlink.
    
    2. Makes glusterfs_realpath, a VMP-based operation, return a resolved
    /real path that actually has the VMP pre-fixed to the resolved path.
    If this is not done, we'll be returning a path that is valid only
    within the glusterfs context, i.e. the path will point to a real
    file/dir only if a glusterfs handle identifies which glusterfs context
    the file is in.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d1e74d7faa8670d6a7bf47ab9105af03d7dcf9a6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:58:03 2009 +0530

    libglusterfsclient: Dont lookup oldpath on symlink
    
    The target of the symlink does not have to be interpreted in
    any way. It should be sent across as it is.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5cfa7a3a5ee9199399137e217597b1b97f7a4e38
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:57:56 2009 +0530

    libglusterfsclient: Improve path matching heuristic
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b46296282155281768407c93f878ba3823118463
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:57:49 2009 +0530

    libglusterfsclient: Guard against un-inited VMP searches
    
    On my system, an selinux module gets inited before
    booster even though the FS calls from the selinux module
    get routed through our LD_PRELOAD'ed wrappers. In this
    scenario, the VMP list is un-inited, resulting in a seg-fault
    if it is dereferenced. The list_empty check does not help
    because the pointers in the list have non-NULL values.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4ecd27aed126b20012abe1449bc49b4c646cb9d0
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:57:42 2009 +0530

    libglusterfsclient: Add comments to API
    
    Some of the functions have also been moved within
    the header to reflect the order in which users will
    read through and try to understand how to use the lib.
    
    For eg. the init, mount and umount functions have been moved to
    the beginning to clarify how to start by init and de-initing.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 90f854f470b354bc36d46397d39a065cbe89e27d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:57:34 2009 +0530

    libglusterfsclient: Expose a few remaining APIs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b12fde2b06c4701970201aaebc7f45a8b964812c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue May 5 15:57:27 2009 +0530

    libglusterfsclient: Add VMP-based rename
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6fdf8f4c7d5cced776c925052eb8a81c332a3573
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon May 4 10:59:18 2009 -0700

    Do not lock entire file for metadata operations.
    
    Metadata operations now lock only a single byte at offset
    (LLONG_MAX - 1) instead of the whole file, to avoid contention
    with writev().
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1a5bcf508b22c1f9f5bd2f555e290f6725035cd2
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon May 4 10:50:48 2009 -0700

    Made afr_flush a 'quick-unwind' transaction.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9aea45a0e1338a10558c4f3f434d172c4bc8c209
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Sat May 2 14:37:04 2009 +0530

    io-threads: Clarify thread count range
    
    This patch cleans up io-threads behaviour regarding the
    range values that can be specified for min-threads
    and max-threads. THe major change is that the min threads
    have been reduced to 2 to signify that io-threads needs minimum
    two threads for its operation, while keeping the default number of
    threads at 16. The idea is to decouple the default thread count
    from the minimum thread count.
    
    Note to Avati:
    This applies over Raghu's indentation and logging take-3 patch.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 80c30634da16f7b333d07eeff9839b70d577e39f
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon May 4 10:33:11 2009 -0700

    io-cache: indentation and logging fixes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5d417f0f8853e4f17caf25255f98c559f3670434
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Apr 30 07:09:42 2009 -0700

    io-threads: indentation and logging fixes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bed4717a1b41e3e9af47ff1673e28925ba351f92
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 30 10:42:14 2009 -0700

    Cleaned up log messages in storage/posix.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f9d689ef3dd7040e09f704d24696b268ac1bdff6
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 29 05:23:17 2009 -0700

    write-behind: indentation and logging fixes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 60d91b69768bd97cd83adc6edb4e1f7d6c13b6ba
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 29 04:21:59 2009 -0700

    read-ahead: indentation and logging fixes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 946436dc17f7df47608b9a64aa11b77d7caf309d
Author: Harshavardhana <harsha@zresearch.com>
Date:   Fri Apr 24 05:47:39 2009 -0700

    Fix a conditional during dependency check
    
    Conditional was wrong and dependency check would fail.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ce6fa580af849b03c4641baf77bf07c590be934a
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Apr 29 08:51:41 2009 -0700

    bug fix in server protocol segfault when the volume file key is NULL
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 78aa2ee7d2f646a41f19858db9c48a8afc82e83f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Apr 29 03:23:55 2009 -0700

    Cleaned up log messages in features/locks.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d22b495e0c4c180de63082add3e3e3168f1a0e1f
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Wed Apr 29 02:16:51 2009 +0530

    cluster/unify - unify_forget() should not try to access inode->ctx, if inode->st_mode is not set.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2de8717247d3dc1dcda4e3e8b3c260887c3e5891
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Sun Apr 26 22:51:18 2009 -0700

    mod_glusterfs/apache/2.2: fix segmentation fault
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3e3fa81c3465bc329d448aac78de8e556d9d513f
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Sun Apr 26 21:36:33 2009 -0700

    memory leak fix in auth/login.c
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f827d1536635c53dbee27ade459f1e207c1115e8
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 19:29:50 2009 +0530

    protocol/server indentation fixes

commit 604f38b8df4ac8427f55bc708bb72d8700924122
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 16:02:22 2009 +0530

    protocol/server log level fixes

commit 7bbbc9c8786d079055138ac4f8ea98b576c73ce0
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 15:11:21 2009 +0530

    protocol client log cleanup

commit 7ce91b4e860b7c077c64e54f49943b2f77972967
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 15:11:05 2009 +0530

    fuse-bridge log cleanup

commit d2ed893e3a526506ef302281d6bc936e6219063d
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 15:10:38 2009 +0530

    socket transport logging cleanup

commit 702affac485649f9509b1d6912e1a7737dbb23ca
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 15:10:16 2009 +0530

    dht logging cleanup

commit a76ce13ce29249f4622fcfef39bcd087c1cd050a
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 15:09:57 2009 +0530

    afr logging cleanup

commit 34f9a0b30043cf7836601cb620b4bcc4239357ac
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 28 15:09:22 2009 +0530

    libglusterfs log cleanup

commit 29f111a22fe574eaa6938bf0bd3516796abe597d
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 21 19:39:24 2009 +0530

    log message cleanup in distribute
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 53f4af3aad6601ded97b5ef19d2383fe8efa7984
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 21 21:36:27 2009 +0530

    log message supressing in DNS resolution
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3699c3b966dec936bbbe9ec610d48feb41e0880a
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Apr 21 21:34:38 2009 +0530

    cleanup of logs in socket and ib-verbs transports
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9c540ee5bf8a620db3855814db7b0f0f71644aac
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:08 2009 -0700

    Cleaned up log messages in replicate.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 04532fe34c582f551ec7d81b3fa6168f3a4a4d21
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:07 2009 -0700

    Cleaned up log messages in client-protocol.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f99f41b67e500a38015b61781b59224a8395dd98
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:06 2009 -0700

    Cleaned up log messages in mount/fuse.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8825c34d14e76914f7357c773c86b89ff03592cc
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:05 2009 -0700

    Cleaned up log messages in xlator.c
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit add02343dd4d9a095552a703f8fa732455b0ff8d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:04 2009 -0700

    Cleaned up log messages in spec.y
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 0651c3a12c30f21067111498e9710864698c028b
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:03 2009 -0700

    Cleaned up log messages in inode.c
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c3e4bb1bc8c7aac727a236f101c5d9f36a536c5a
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:02 2009 -0700

    Changed logging format to remove line number & function name from NORMAL and higher levels.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b52a5a408b82496a295c1065f2286c6755a04689
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:34:01 2009 -0700

    Introduce new log level GF_LOG_TRACE.
    
    TRACE is the most verbose log level, meant to have a
    full trace of operation.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 174872b3644d36f6d0f8a34d9c06092abc126e4f
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 21 02:18:38 2009 -0700

    Remove log level TRACE and the macro GF_TRACE.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e0c284c6e7c98b3a2fbd5c60d59b928d6e7af88a
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri Apr 24 15:28:40 2009 +0530

    iobuf: Define MAP_ANONYMOUS
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7b2e459db65edd302aa12476bc73b3b7a17b1410
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Apr 24 15:18:15 2009 +0530

    rename transport-timeout to frame-timeout, and set default to 30mins

commit d892c56c1d0b1de466ee4cf4071ab7b722808c00
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Apr 24 00:57:42 2009 -0700

    Revised README
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 689347f278e5acfda95a24f7804a1450043311f3
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 23 06:53:02 2009 -0700

    Do not fail lookup() in case of split-brain.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 99351618cd15da15ee875f143154ea7f8e28eaf4
Author: krishna <krishna@gluster.com>
Date:   Wed Apr 22 23:43:58 2009 -0700

    "option unhashed-sticky-bit on/off"
    
    "option unhashed-sticky-bit on/off" will configure distribute to set or not
    the S_ISVTX bit in the stat.st_mode of the actual file in case it is
    pointed to by the link file. This can be enabled during migration.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b6f634f602559cfe0c4609f16c9f33a32243b578
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Apr 23 11:20:17 2009 +0530

    fix build warning in locks translator

commit d886ceb9cbf45434ea0218f0098862daafb26ecb
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Apr 23 11:09:37 2009 +0530

    minor build fix - set EXTRA_DIST to point to MacOSX/Portfile instead of Portfile

commit b0acbf09c21ff898ad3315811974e49cc80e6f2b
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 23 04:05:00 2009 +0530

    fix bdb_db_get() to return exactly read bytes and to copy the read data to given buffer only when needed.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e5686c440f3c03fbb24759342e5badf102579634
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 22 07:33:59 2009 -0700

    mod_glusterfs/lighttpd/1.4: port to use virtual mountpoints.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5f0bf570069770ee5c98fea728f0231f93eaab5c
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 22 07:34:10 2009 -0700

    mod_glusterfs/lighttpd/1.4: ensure each line is no more than 80 characters
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7a77bad6d583ee9266e6e3f566bf19d579177e3e
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 22 07:32:30 2009 -0700

    mod_glusterfs: port apache/1.3/mod_glusterfs to use virtual mount points
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e26b63ccfc3aa0b29afb7235b863b7b4a7c8ae95
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 22 07:32:42 2009 -0700

    apache/1.3/mod_glusterfs: ensure each line is of maximum 80 characters.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3c68984b6f8dbb772a858fcf829d6c6f81503912
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 22 07:32:53 2009 -0700

    libglusterfsclient: implement glusterfs_umount
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b817670c609dda2a1038fb94bd5a7dc6fa522518
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 22 07:33:03 2009 -0700

    mod_glusterfs: port apache/2.2/mod_glusterfs to use virtual mount points
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 725a1fcb1e84507c28f009d0f83692e0b57e474b
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 22 07:33:15 2009 -0700

    mod_glusterfs: coding guidelines related changes
    
    - make sure code fits into 80 character lines.
      - proper indentation of declarations.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c8e9a96e2c3801701e7f218f1b12fef16071b088
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Apr 23 10:20:06 2009 +0530

    replicate dir self-heal - when creating a missing dir/file, set pending xattrs on source subvolume for that dir/file

commit bb592b1a8465fa078d0cd5f445f08280b78a93e4
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Apr 23 02:18:52 2009 +0530

    fix in afr directory self-heal (partial healing)
    
    impunge loop was 'continued' on a different subvolume in certain cases, resulting in healing of partial files

commit 86fff0e75b445dee3cda6b788699930eb649334e
Author: Harshavardhana <harsha@zresearch.com>
Date:   Tue Apr 21 02:24:22 2009 -0700

    Add MacOSX based packaging file into repo
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 38a6a5b1a12eff04f26ded17ce4585a6ebdc7986
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Apr 22 04:31:36 2009 -0700

    Bug fix in releasing inode locks when transport gets disconnected.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit df6d9e16817d952c17700d44ab478e6d6af704a0
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Apr 22 01:02:09 2009 -0700

    Release all pending locks in pl_forget().
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7eb63e30f22f7a9d785f6620be22d2b3aab77ada
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Apr 22 12:55:47 2009 +0530

    iobuf_pool->arenas_cnt should be incremented in iobuf_arena_alloc, and not iobuf_pool_add_arena (to avoid counting of unpruned arenas)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4877476fa1a591c51f4b3ee76082766f38a33b23
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Apr 22 04:01:06 2009 +0530

    0-byte write guard
    
    guard server_writev from 0-byte writes from client where iobuf will be NULL. This is possible only via libglusterfsclient (not fuse)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bc1dff620cc185c3e08853b9b7fb4c5a04c48ebe
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Apr 22 03:59:30 2009 +0530

    handle iobuf NULL return case in fuse-bridge, by waiting 10 seconds and trying again
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cf508025fe506a507fe16ed52df74dc7e0ca7c64
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Apr 22 03:44:01 2009 +0530

    fd leak fix
    
    steps:
      - server_finodelk uses req->volume pointer into state->volume
      - finodelk is queued by locks translator
      - c call returns from server_pollin and hdr is FREE'd
      - now state->volname is pointing to FREE'ed region (junk)
      - server_finodelk_cbk calls gf_add_locker
      - gf_add_locker remembers lock with junked path along with fd_ref
      - gf_del_locker from new server_finodelk cannot string match with junked volume thus
        lock is not deleted, hence fd_ref remains as a leak
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8d2e5d8062361df451be7c6f748a23884f1cf315
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Apr 22 02:21:46 2009 +0530

    afr_lookup_cbk - self-heal getting missed
    
    compare for mismatching sizes and attributes before overwriting local->stbuf for read-child subvolume. This causes files with differing sizes on backed not to get self-healed if xattrs were missing.
    
    Also add the ESTALE check for compulsorily failing revalidates in case of 2nd unwind and beyond
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 07f1524165f864e09033b7f78e921c5375d4e2d6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:50:33 2009 -0700

    posix: Ensure EINVAL return on NULL args
    
    Initing op_errno to EINVAL ensures that this is the value
    that gets returned on STACK_UNWIND, in case any of the VALIDATE macros
    result in exit from "out" due to a NULL argument. If this is not done
    , we get op_ret as -1 with errno set to 0 in the application's
    syscall.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 27e1c9fbd3fb6eda4f7d64ff04dad9d306c237e7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:50:20 2009 -0700

    call-stub: Check for NULL in the correct variable
    
    It looks like the argument fd was meant to be checked here instead
    of the fd in the call stub. This fixes a NULL fd bug that results in
    an EINVAL on opendir.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 31643eb227a5dfba11d23068e9626bf9546283bd
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:50:08 2009 -0700

    io-threads: Add fxattrop fop
    
    -- added some indentation fixes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e246a3131676197aff0430429db1e7d7cc00be65
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:49:55 2009 -0700

    io-threads: Add xattrop fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a9b4360d889097e8ea25497eb669daebcaf1e381
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:49:45 2009 -0700

    io-threads: Add readdir fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d1eb9b13d2e50485e69301ade12afe5ea8636af8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:49:24 2009 -0700

    io-threads: Add removexattr fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 609c5aff6faa21cf3aaefa6b7a2a31a91590d726
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:49:10 2009 -0700

    io-threads: Add fsetxattr fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a77340b94147a078918536a5297746803c846809
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:48:56 2009 -0700

    io-threads: Add fgetxattr fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d7753849cc66c3aef66dc1270920389d3c42e7ce
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:48:45 2009 -0700

    io-threads: Add getxattr fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6b426bc53e2e6106e32568f09354d4e4ce382f11
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:48:33 2009 -0700

    io-threads: Add setxattr fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1cb8064b2a653f06062c226dc12d524d8f1a2da2
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:48:21 2009 -0700

    io-threads: Add statfs fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d769066ddcb7b3fab456a57704b184d0617b8d52
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:48:08 2009 -0700

    io-threads: Add fsyncdir fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 282a39c19ee15f8908eb28f0b2d6983b665d57a7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:47:56 2009 -0700

    io-threads: Add opendir fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cdbeb01abbfc26345df98e5a98a0e5ed513b7cf8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 21 04:47:42 2009 -0700

    io-threads: Add link fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6bff99a8f92befa78ddea62519a05f945db5cdfa
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:36:44 2009 -0700

    libglusterfsclient: Add VMP-based realpath
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cf22fd1d0430705e226d61ff8d9492925ce95d46
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:36:21 2009 -0700

    libglusterfsclient: Add VMP-based readlink
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a9febb4bd30f41681755a0ee925ae3de6f0fa292
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:36:05 2009 -0700

    libglusterfsclient: Add VMP-based symlink
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cb95018adab1377c862dca32f58825b336adafd0
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:35:50 2009 -0700

    libglusterfsclient: Add VMP-based unlink
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6f91c9dc86be9c10467ccb5bc3edde2c5d767b9f
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:35:32 2009 -0700

    libglusterfsclient: Add VMP-based mkfifo
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bcc9a67fc22147f54a27a81ee35f4c081a0e6b73
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:35:17 2009 -0700

    libglusterfsclient: Add VMP-based mknod
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a7205e78bfb962d9e5ff11db2a0b394e6db03256
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:34:58 2009 -0700

    libglusterfsclient: Add VMP-based utime
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e707afad9f6282bc425f8b0262ea5a6db018ec92
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:34:41 2009 -0700

    libglusterfsclient: Add VMP-based utimes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b4259400090a28a5dbe27922ad8bc309db2a7c4a
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:34:20 2009 -0700

    libglusterfsclient: Add VMP-based statvfs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6cb3159ef38428572b81160e91e7c685ed44acb0
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:34:02 2009 -0700

    libglusterfsclient: Add VMP-based statfs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit de2192ea754883ea6ae643f63c44c2cbeb20f981
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:33:43 2009 -0700

    libglusterfsclient: Add VMP-based link
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 12d9b4cccd559776f125440a232ff5b944ab3442
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:33:26 2009 -0700

    libglusterfsclient: Add VMP-based opendir
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e2ba80403c3e73220a2b48b813df1561a9081e09
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:33:06 2009 -0700

    libglusterfsclient: Add VMP-based chown
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 74a46284e17045db302e5bcde0052ea6c7b4c038
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:32:46 2009 -0700

    libglusterfsclient: Add VMP-based chmod
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 721783da4f9705331356328b8082873aec1ced0e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:32:29 2009 -0700

    libglusterfsclient: Add VMP-based rmdir
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 07da4292a8678a415acfec130c40febc9a63b6b4
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:32:06 2009 -0700

    libglusterfsclient: Add VMP-based mkdir
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit dc53183708d6d9ff998487427312000f30dcb7ee
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:31:49 2009 -0700

    libglusterfsclient: Add VMP-based lstat
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 84eb262529ea5389df2296d182ecd5e0582602a7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:31:31 2009 -0700

    libglusterfsclient: Add VMP-based stat
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit aa1e2fd37ab93b194308f94edd8ab0a342c7830e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:31:09 2009 -0700

    libglusterfsclient: Fix stat cache bug
    
    The way stat cache gets updated was not consistent across
    all syscalls. Consequently, I was running into a bug that
    returned a 0 st_ino. The fix actually resides in the hunk
    that changes the lines in libgf_client_lookup but similar
    changes were also required in other users of stat cache.
    
    This commit fixes the bug and also cleans up the way stat
    cache is updated.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f29383ef35d210f2a72883cb6157e915200f7c7c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:30:51 2009 -0700

    libglusterfsclient: Add VMP-based setxattr
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4074769dd2435ab3521ab39eb2775c3e80fc32b4
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:30:36 2009 -0700

    libglusterfsclient: Add VMP-based creat
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d875df0c5c095488db29a202eac74d10d540aa3b
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:30:15 2009 -0700

    libglusterfsclient: Add VMP-based open
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bb2ca0ec0da700f600d1fa30d111c2aa42804f70
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:29:57 2009 -0700

    libglusterfsclient: Add VMP-based getxattr
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6cd656152901ba19ef52f762d000e329e3f7dbc6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:29:40 2009 -0700

    libglusterfsclient: Add VMP-based get
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 86a1c646eeea353643bd6bd5eb040cf584b407c1
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:29:21 2009 -0700

    libglusterfsclient: Add virtual mount point support
    
    One part of the glusterfsclient library requires users
    to use a handle to address a particular glusterfs context.
    This can become cumbersome for applications that need to use multiple
    such context. For such applications, we make it easy by letting them
    define virtual mount points(VMPs), which are just paths that identify
    a particular glusterfs context. This is done through a new
    glusterfs_mount(..) interface.
    
    Subsequenly, any path based operations, that pre-pend a VMP before
    the files and directories inside the glusterfsd export, get internally
    routed to the correct glusterfs context. This helps users do away
    with the need to maintain their own path-to-glusterfs_handle_t
    mapping.
    
    The old handle-based interface still exists for whoever wishes to use
    it.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7c7fd9039b0d0ba17190677f864c5a22d46ab4d6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:29:00 2009 -0700

    libglusterfsclient: Must return size from readv
    
    The line being removed made libgf_client_readv return
    a 0 on successfull return when the return should really
    be the size of data read.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7bc1747de75d7a65059fbcb191c3776210de1491
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 20 12:28:40 2009 -0700

    libglusterfsclient: Expose glusterfs_realpath
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 82394d484803e02e28441bc0b988efaaff60dd94
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Apr 20 03:54:04 2009 -0700

    Check return value of afr_sh_select_source.
    
    If select_source returns -1, abort self-heal.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fbefbfee743a01b5ad9977ad24de372258aeb65c
Author: Harshavardhana <harsha@zresearch.com>
Date:   Mon Apr 20 04:59:54 2009 -0700

    change errno EINVAL to ENOENT in case of all fuse_* calls for fuse_reply_err ()
    
    Seen "rm -rf" returns EINVAL in case fuse_loc_fill fails when there is a race condition which can happen when multiple "rm -rf" are done on a same directory listing from multiple terminals.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2f5ee29248f4eafcd1c2f5cc31432d22739349d0
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Apr 20 03:38:15 2009 -0700

    Minor fix in afr_sh_build_pending_matrix.
    
    Remove incorrect check for xattr[i] being NULL.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit aa085b10678c01693d0f7222bd4054bb8e8836cc
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Mon Apr 20 13:15:12 2009 +0530

    inode.c - NULL check for the extra __inode_search performed, when presented inode is not hashed.
    
    This bug fixes #967

commit 8660bb2bef59c00df194087ed75ba81f34555a73
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Mon Apr 20 12:00:50 2009 +0530

    afr-transaction: handle double flushes
    
    __if_fd_pre_op_done - reset fd_ctx->pre_op_done to 0 so that double flushes do not result in two xattrop() calls

commit 3b8f7ed4c080dc45da02dc751478863007199c26
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Mon Apr 20 08:08:26 2009 +0530

    client_protocol_reconnect - do not send notify of CHILD_DOWN event if errno from transport_connect() was EINPROGRES
    
    This bug was racing between a CHILD_UP from poll thread resulting from the event_register() of the new socket called in fuse thread. CHILD_UP would sometimes overtake the CHILD_DOWN for EINPROGRESS. So replicate would receive CHILD_DOWN as the latest event. This resulted in self-heal not happening etc.

commit 42617775a2821dc74300b89dd14a08b068575b2b
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 18 13:27:21 2009 +0530

    keep ctx->page_size fixed at 128KB but only add the margin for iobufs which are created

commit fb5cc405ae45b4e573d6acbe3383349a278f2bdf
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 18 11:19:34 2009 +0530

    enhancement to migrate-unify-to-distribute.sh

commit 093141a74962f11654c44fe2292605f9cf65e709
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Apr 17 16:07:00 2009 -0700

    added migration script from unify based setup to distribute based setup
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9a4a2e2286cb372ca462f6f25f78de686ea3e4ce
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 18 02:49:03 2009 +0530

    pruning buffer margin - do not destroy if no other non-filled arenas are in the pool

commit 307528ef9a33a4d294b3ea49bbf5f0b16b27aa0f
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 18 01:09:31 2009 +0530

    disconnect transport peer if system is out of memory while allocating iobuf

commit 50b2291e3b046ea6b8fdfcb7e206c772eae64f0e
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Apr 17 23:35:43 2009 +0530

    iobuf - account with iobref_size() instead of iov_length (vector)

commit 1d6dfe94fb970b51d96653da6c3361533d697fc3
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Apr 17 23:12:37 2009 +0530

    added 2 APIs iobuf_size and iobref_size to return the system memory usage by an iobuf, and by all iobufs in an iobref respectively

commit 7867577b346c7f003be67ad202f4085cf35fdf7c
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Apr 17 06:15:16 2009 -0700

    Destroy old ping timer before setting new one.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7b1beca0a3b60a8b9347a3122d77aea081ccb773
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Apr 17 05:42:23 2009 -0700

    Fix two memory leaks in afr self heal code.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 98a872df828aa2786c7bf595d430ef64351f4192
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Apr 17 17:52:07 2009 +0530

    add 4KB margin in iobuf to accommodate fuse header

commit 0b20c24a399eb03fdc431ea2761e1334e0032651
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Apr 17 04:23:58 2009 -0700

    Fixed parameter to finodelk in STACK_WIND in dht
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4e3eae6561b38b53bef2d20177ab62602db45c14
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri Apr 17 02:33:01 2009 -0700

    libglusterfsclient: Fix typecast to fix build warning
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4a632ea96be3012c583165865bbde392f99a327b
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Fri Apr 17 14:19:18 2009 +0530

    protocol/client - set remote inode number in inode context for root inode also, during lookup_cbk().
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6bd53940d198e55780cbc7d8678da6d67df80265
Author: Harshavardhana <harsha@zresearch.com>
Date:   Fri Apr 17 01:08:00 2009 -0700

    Renamed abs_top_srcdir to top_srcdir for older versions of autotool
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4e68cf7c4d912556e25eb1226669d7b438ff8a3f
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:59:02 2009 -0700

    libglusterfsclient: Remove unused variables
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 27d73ca503b2e508c682fca2848f8ae38390a146
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:58:50 2009 -0700

    libglusterfsclient: Add realpath API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4ada36f9bd6e008dfea65d708d785907b993b946
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:58:39 2009 -0700

    libglusterfsclient: Add lstat API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7cd3cc24c8f3178382074c8a3a319df17b85769d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:58:26 2009 -0700

    libglusterfsclient: Add readlink API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a6f0446541e917979a697edd06dd28634bf3ec6d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:58:13 2009 -0700

    libglusterfsclient: Add symlink API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7aff8936f9c86677ee205e1cf9cb41f4ea9edecd
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:58:00 2009 -0700

    libglusterfsclient: Add unlink API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 42528875cdaee764070e54b8fcd5e91ba8733e98
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:57:40 2009 -0700

    libglusterfsclient: Add mkfifo API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 933c3eee81f843db1fb8a2eda491d49cfc04efea
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:57:24 2009 -0700

    libglusterfsclient: Add mknod API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 169976dfafeb714f3c94b9a2f635f36759334b9c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:57:13 2009 -0700

    libglusterfsclient: Add utime API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c9017ae0de2531342125eaf2a6aca3b9a251b16e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:57:01 2009 -0700

    libglusterfsclient: Add utimes API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 366bd140f3f0fbc6b343aab067713c398ae601af
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:56:51 2009 -0700

    libglusterfsclient: Add rename API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5feab82f0c228410d94f3dfa53025f85d6eac8b1
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:56:40 2009 -0700

    libglusterfsclient: Add statvfs API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ff2bacf3466ddd4473ae3774e1f822981f4d8198
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:56:29 2009 -0700

    libglusterfsclient: Add statfs API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f199ebf5d0c4d90abbc5d0dafd67561f39f398b8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:56:08 2009 -0700

    libglusterfsclient: Add link API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e18b8031ab4c7ce763e1e7d57bf5c98a1cbe7167
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:55:55 2009 -0700

    libglusterfsclient: Add ftruncate API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9193494d20a8555a90126b9d23e848b0b8ca196e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:55:40 2009 -0700

    linglusterfsclient: Add fsync API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 912f1a8492c8c20743c8d7f0a75aeb31f2483932
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:55:26 2009 -0700

    libglusterfsclient: Add fchown API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 67561c965210f299b8a7e4ea1be0a702095b19f6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:55:12 2009 -0700

    libglusterfsclient: Add fchmod API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 01a48790c4a0c9805eb55bfe1c60860ee91f48a1
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:54:58 2009 -0700

    libglusterfsclient: Add closedir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit eb4d5f0074ab6430973188906a8083d26e24e790
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:54:42 2009 -0700

    libglusterfsclient: Add opendir API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f6ebe58492095a5d7ceb5762cb35defca945ab45
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:54:27 2009 -0700

    libglusterfsclient: Add chown API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e7d7a19d5733dfcea87467c5f96e1aaa812d5df8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:54:14 2009 -0700

    libglusterfsclient: Add chmod API
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f887fd6f7c6a5b740ebbf220706ebc44a938d67e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:54:00 2009 -0700

    libglusterfsclient: Abstract away inode attr cache updates
    
    This commit creates a separate function that allows users of
    the inode attribute cache to update the cache when required.
    Major users are lookup, stat and fstat functions.
    
    The function libgf_update_iattr_cache(..) allows updating the lookup
    and stat caches separately using flags.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4c98eaf4c464e7e2f1c6ce66414fd7864f5c8bfa
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:53:51 2009 -0700

    libglusterfsclient: Replace dict based inode ctx with array based one
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c71110fb153adfd4628718f634348b7a5712bf32
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:53:39 2009 -0700

    libglusterfsclient: Fix fd_ctx leak on release cbks
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit adb677be13e6b755c3eeb685759d2522f6c466a7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:53:24 2009 -0700

    libglusterfsclient: Replace dict-based fd ctx with array-based one
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 00968db3069e7b145f108d53a62d1899c9c1f3f9
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:53:12 2009 -0700

    libglusterfsclient: Generalize [RW] checks on dirs
    
    This patch moves the read-write permission check on directory
    inode into libgf_client_opendir, so that when I am next adding support
    for the opendir syscall, I dont have to perform similar checks again,
    outside this function.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1873d0bdb53af0311e8ad344116c0923448a6ff5
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:52:54 2009 -0700

    libglusterfsclient: Check for directory on O_CREAT
    
    If we have received an O_CREAT for a name where that basename is a
    directory, and if we have successfully looked up the inode for this directory,
    then we can check for S_ISDIR in libglusterfsclient and prevent sending a message
    to the server through libgf_client_creat. See also the comment inline.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 79215d4f2487e6db87e5fd637f0262037c1d230b
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:52:43 2009 -0700

    libglusterfsclient: Create and use LIBGF_REPLY_NOTIFY macro
    
    All reply notifications can now be abstracted away through
    this macro and all cbk functions should now call this.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ba4833355a1ee77f828b538a357e07c46f36b037
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:52:27 2009 -0700

    libglusterfsclient: Fix segfault on non-NULL loc->name
    
    The gf_log message actually assumes that loc->name will have a valid
    non-NULL name in it, whereas if the loc_t being passed to it was
    actually created on a function stack, i.e. a local function variable
    and was then passed down the code path to do_path_resolve without ever
    initing it or zeroing the structure, its possible that the name member
    has a non-NULL but corrupted address. This leads to a segfault.
    Whereas, we know loc->path will always have the full path.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c1b3deff1186c581cb8d9893a3a0de6bf00d3adc
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:52:04 2009 -0700

    libglusterfsclient: Use macros for argument checks
    
    Having those if {} blocks to check for argument
    validity hurts the eye so this patch replaces those checks
    with macros. One macro already exists in libglusterfs. The second
    macro is introduced by this commit for libglusterfsclient-specific
    check for paths.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b3e3fc79d4e7008a27d935decefcca51ba89dc17
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 16 23:51:45 2009 -0700

    libglusterfsclient: Rename XLATOR_NAME define
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 41011cdb4c9f76a1805f0b908d1d7f77cef545b2
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Fri Apr 17 00:32:17 2009 +0530

    protocol/client - NULL check for loc->inode added in statfs(), before trying to retrieve remote inode number from loc->inode's context.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4c4021bea2d9f484321066518e10d2b139af2a3a
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu Apr 16 06:15:48 2009 -0700

    RPM spec file updates for RHEL,CentOS,Fedora,SLES and OpenSUSE for upcoming 2.0.0 stable release
    
    * Updates to ahere to RPM standards hugely driven by Fedora dist-f11.
    * RPM spec file portable across RHEL, Fedora, CentOS, SLES, OpenSUSE.
    * RPM spec build options made compact and removed unnecessary.
    * %changelog old entries removed as they were giving many warnings
      during rpmlint.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7ae141bb054494c86cfb60b377ab989c30938f66
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Apr 16 17:32:05 2009 +0530

    add NULL check in iobuf_arena_destroy

commit 6bc3f3c19b9e720ade3702ce409a8a99cc13f1dc
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Apr 16 03:41:54 2009 -0700

    logging enhances to commit d77279ef04ca75ab9715864274567d1ce0ce66a6
    
    - logging made more relevent.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8a00ad080cbea0d01470c5f724d7d8ff54b0e254
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Apr 15 06:02:22 2009 -0700

    Use original pid when calling the FOP in afr transaction.
    
    Save the original pid while locking and restore it
    after the FOP is done. This ensures posix-locks can
    release locks (fcntl) properly.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 34f8f0b3e1f992cf59da2c2d410471e440e6ed92
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 15 03:11:21 2009 -0700

    write-behind aggregate-size related changes
    
    This patch brings in following changes:
       1. make aggregate-size as non-configurable and make it to be equal to
          maximum iobuf size.
       2. best effort to write data in chunks of length as close to aggregate-size
          as possible but not greater than aggregate-size, since aggregate-size is
          made equal to Maximum size of iobuf.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ffb863c3a8cbfb2105ac23ce5fc5be1df372458c
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Apr 15 03:12:17 2009 -0700

    write-behind: adhere to coding guidelines.
    
    - make sure lines are not greater than 80 characters in length
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e77eb62f253bc2288b1b4ff582f99ebf16a28c47
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 16 14:38:02 2009 +0530

    cluster/distribute bug fix - try to create linkfile in dht_lookup_everywhere_cbk(), only if hashed subvolume can be determined, else error out with ENOENT.
    
    -- with local fixes (avati)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d1703344735d9c4df89b84310deaf1b9703f8c49
Author: Harshavardhana <harsha@zresearch.com>
Date:   Wed Apr 15 01:00:01 2009 -0700

    Fixed the build problems observed
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e6c22c0587bbd9cb84969f5673db043c32e485ef
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Tue Apr 14 15:28:34 2009 +0530

    eliminate this_ino_get(), this_ino_set(). handle inode_ctx_{get,set}() at the fop level itself.
    
    they used to log ambiguously
    and was of no use. logging is now more precise and will help in debugging,
    in case of errors.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f7902b7072015c9c20f47e999af85c923f202d33
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 14 08:15:50 2009 -0700

    Changed xattr format of afr changelog to support adding and removing of subvolumes while keeping existing data.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d77279ef04ca75ab9715864274567d1ce0ce66a6
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Apr 14 02:53:09 2009 -0700

    server-helpers: Add check for NULL connection arguement being passed in helpers.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3baa437e9980e7dac9893d6c11ccc1623a5faee2
Author: Anand V. Avati <avati@gluster.com>
Date:   Tue Apr 14 15:09:37 2009 +0530

    remove unused variable @ret in ib_verbs_options_init
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 54c40bbfb48e2f7469149d6724e2ac77bce0690a
Author: Anand V. Avati <avati@gluster.com>
Date:   Tue Apr 14 14:51:26 2009 +0530

    use MAP_FAILED macro to free mem_base in arena_destroy
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1ce5acccf5186e70424826d4f22cee3a29ac114e
Author: Anand V. Avati <avati@gluster.com>
Date:   Tue Apr 14 14:51:16 2009 +0530

    FREE arena->iobufs in iobuf_arena_destory
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8b32e03f87599bd3d87ec99c5718d40ff10831ff
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Tue Apr 14 14:20:04 2009 +0530

    cluster/unify link() should be sent to only one subvolume.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7a4bc3fbb352396b27489b0e97327d0fc82b85d5
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Apr 14 00:41:43 2009 -0700

    minor bug fix in posix_create() when 'o-direct enable' option is given.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 33e81bc94986929caab14a05231b25787a25a41b
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Apr 13 23:40:22 2009 -0700

    bug fixes in dht-disk-usage feature.
    
    fixes bugs seen with dht's disk usage.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d8bc2834d056a23f55bd86a5fd704bd81e35836d
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Apr 13 07:23:59 2009 -0700

    Send statbuf from the same subvolume, even across revalidates.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8e0d48cbb23cf056277ebc609d47b5184b95fa87
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Mon Apr 13 18:42:36 2009 +0530

    use ctx->page_size in all translators and transports instead of having their own configurations
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 451620e0ec88f717e7046ebb27fe1f29d73796d9
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Mon Apr 13 17:50:21 2009 +0530

    introduce page_size in glusterfs_ctx_t to be used by all translators set it to 128KB in main()
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3093ff0b125c520fdac3db627af708f495c9a47e
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Mon Apr 13 15:41:01 2009 +0530

    client_readv_cbk - when op_ret is 0, iobuf comes NULL from transport, handles this case
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a0bb8a02cd334aeda02e6146ea541a7dae4223d5
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:03:43 2009 +0530

    bug fix in iobuf_select_arena - call __iobuf_pool_add_arena (unlocked version)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3fb7252c5ec7edd8c9234d4fcc369fd10707a613
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:03:35 2009 +0530

    bug fix - arena destruction now calls munmap and not FREE
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit dc9cdbdc1c03c231ba405e540fac7d6483159bb2
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:03:28 2009 +0530

    add purge list support to make iobuf_pool_purge() in expensive, and actually call it in iobuf_put :-)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b9a210a419ff28f2d75b10a680520fd6cc37ac5a
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:03:21 2009 +0530

    bug fix in iobuf_select_arena - never created a new arena
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 688db6452befde5d7cd2b35f86b770b4c19c53fc
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:03:13 2009 +0530

    add @filled list in iobuf_pool to keep away filled list from getting searched in iobuf_select_arena
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4f0d487c96b84123289d3c48fd84188efe136293
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:03:02 2009 +0530

    change arena size to 8MB
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 00dff3bddc375e88e710a751f47843f9da77a70c
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:02:57 2009 +0530

    use MAP_FAILED macro to check for mmap failure instead of (void *) -1
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 014cdf385642947d0592102b2c7338a8ad1c2d4e
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Apr 13 14:02:47 2009 +0530

    fixed sizeof parameter in CALLOC of a new arena
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5dd850ae840ddb402ca4aaae19c668094947507e
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Apr 13 11:21:20 2009 +0530

    switch scheduler to validate the subvolume specified for a pattern, against the given subvolumes of cluster/unify.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ec06475f22db2a3683167c5ffbe236c8e4aaf0ab
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Apr 13 04:47:39 2009 +0530

    changes to database read interface, to make use of a given buffer instead of allocating internally.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 945f438d393297cf72a3157532625b6b02e87268
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Mon Apr 13 02:09:25 2009 +0530

    log formatting fixes. use GF_PRI_SIZET for size_t.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3f1e93c29856ec1e75327525899d1f0d6a81c0a3
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Apr 12 04:16:09 2009 -0700

    minor initialization bug fix in quota's build_loc
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ecead44b5c8d1215e7c398ca1132a4b0b11a44bb
Author: Amar Tumballi <amar@gluster.com>
Date:   Sun Apr 12 04:12:00 2009 -0700

    in dht, initialize the free available space properly, so the first few creates are not confused.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e00bdb4a323b60ced500df59071d2a940b976ae9
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 8 02:28:16 2009 -0700

    Coding Style: Add a few points
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4a62b5af1c9add4a74ea38ab9008bf129e2b4110
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Apr 10 00:34:34 2009 -0700

    feature to disable volumefile's checksum
    
    in server volume define, "option verify-volfile-checksum no" to disable
    the checksum feature.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit be9909606428d78ec23ea02900640c68ca2a40d2
Author: Anand V. Avati <avati@gluster.com>
Date:   Fri Apr 10 09:22:18 2009 +0530

    reset errno to 0 before calling first fuse_lowlevel_new() to reliably detect for unsupported params
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fa9eb588fbe758cbc1ebe727d2455f1dcd0b065f
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri Apr 10 07:09:49 2009 -0700

    io-threads: Remove unnecessary call to pthread_attr_setstacksize
    
    We do not need to explicitly set the stack size to its default
    value.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4f81149489ae80b20ac28d1fdbe48ee56d0a181b
Author: Anand V. Avati <avati@gluster.com>
Date:   Sat Apr 11 00:54:29 2009 +0530

    prefix ULL to large constants (to fix bdb build warning)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 45c4fb76dfd0756ebd86bf431f5b5761068901b5
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 23:32:24 2009 +0530

    updated glusterfsd to create iobuf pool at initialization
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6d94a368e061afeeac6fb57c5910c71f60791dc3
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 23:22:26 2009 +0530

    updated libglusterfsclient with IOBUF/IOBREFs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 77714c065d99767f5a3820bc1c62b22522681821
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 23:09:15 2009 +0530

    updated transport/ib-verbs to use IOBUF/IOBREFs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 07e8f887547c1b9fd71a3ca45b2c1ac974c939ad
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 23:00:59 2009 +0530

    updated transport/socket to use IOBUF/IOBREFs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 19cac9a1b3d7d4f5720049c4fb2b5e08b27d27e8
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 22:04:44 2009 +0530

    updated mount/fuse with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1650945f2379cc33eab1b21c033d42152fa2592f
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:53:57 2009 +0530

    updated encryption/rot-13 with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5617f5e3a3840b59263ede767c53f80088593c66
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:52:08 2009 +0530

    update features/quota with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 91e3976e99523908541932c02b2c4e9df28a9510
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:48:35 2009 +0530

    updated features/filter with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5d80832d2dc0127b8f380afd7d49ff7b27ac79ec
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:46:54 2009 +0530

    updated features/locks with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d7b12cdc8d2bcbf89530e00710da308bd757e35d
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:43:51 2009 +0530

    updated debug/error-gen with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit aed3aaef43589633f2a43d48435ef234582f37e0
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:42:45 2009 +0530

    updated debug/trace with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d720afb836ecd22c13859356261e85334422f119
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:40:19 2009 +0530

    updated performance/io-cache with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit be1d7c1e3b61477a82152a07a11993061e89b894
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 21:23:00 2009 +0530

    updated performance/io-threads with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 795fb95f42697796008e34790e0768929d478a3a
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 19:00:45 2009 +0530

    update performance/read-ahead with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c29b1710529fb52724ba37e09ca0f10cd7fcffa8
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 18:51:39 2009 +0530

    update performance/write-behind with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e062dd5c2f76106593829ebbb86003de966f00f2
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 18:43:35 2009 +0530

    update protocol/server with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ad86fba6e22b10b06aa44426c2ab3591c54ed0a7
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 18:15:11 2009 +0530

    updated protocol/client with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2e743ddc4a89f8a4d0c9ff0f16a6faf0218e453f
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 18:14:10 2009 +0530

    updated transport interface functions to accommodate IOBUF/IOBREF
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 0e9cda6d77a63723014bb2c040d8215fd7180a10
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 02:33:49 2009 +0530

    update storage/bdb with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6e641226df9a90a4d88c859d4bc1c27fdacc2037
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 02:17:25 2009 +0530

    update storage/posix with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fa5847401431f62013f1ef66363b5a0c1b29a0c5
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 02:02:52 2009 +0530

    update cluster/map with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 645c60e308de5290b9059eae557a320bd6a294d9
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 01:59:56 2009 +0530

    update cluster/ha with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 89cacef43e843c7563ed5d4ebb6ec16a3b81df3e
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 01:57:14 2009 +0530

    update cluster/dht with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f33f0669efd89216a528bab3694ac4645a7f523b
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 01:52:08 2009 +0530

    update cluster/afr with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e0e6acd6fbdcbd294c89e61cbe108fc1b96a62a8
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 01:39:34 2009 +0530

    update cluster/stripe with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f551e72584b3525d5a55c6fb4456d7b9ca5cb5f3
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 01:25:26 2009 +0530

    update cluster/unify with new readv writev prototypes
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c723c0dae5fd2887b714a08bcaeadb663e4de44b
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 01:21:57 2009 +0530

    do away with frame->root->{req,rsp}_refs members
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4554d82bbe2ecec6c79b6a791522358c8855408d
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 01:12:10 2009 +0530

    update prototype of writev and readv_cbk to use IOBREF in parameter (step towards elmination of frame->root->{req,rsp}_refs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3524572538e5abe839fa29fe94da8f7591cedce8
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Apr 11 00:09:08 2009 +0530

    IOBREF support for holding iobuf refs along with fops (replacement for frame->root->{req,rsp}_refs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e953968683d988c8fc3020ede2cb8e5229a548a6
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Apr 10 23:11:33 2009 +0530

    use 128Kbyte as the channel transfer size in fuse-bridge
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 124fb0c752530322e6311dde668422afef6b2afe
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Apr 3 15:17:04 2009 +0530

    IOBUF support (to be used by transports and fuse)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a31e26f8df26b1229e9fbca60ff8bf462b234241
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri Apr 10 04:22:37 2009 -0700

    io-threads: Reduce default min and max threads
    
    Going by the memory usage for each threads, it is prudent to
    have lower number of threads by default and let users who understand
    the memory consequences increase the thread count for themselves.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e1977a4e75637109889b581201e44e24506398c8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri Apr 10 04:21:53 2009 -0700

    io-threads: Use non-default thread stack size
    
    The default stack size on Linux is around 8 MiB for each
    thread. This is clearly too high for our purpose. This commit reduces
    the stack size down to 1 MiB.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bf7b4623821c8ffe8070297949e18dc6e3757e9c
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Apr 9 07:59:21 2009 -0700

    posix_unlink: make unlinking in background configurable through volume spec file
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fb034ba3036fadc7cf35edc5cae7481149a67ca0
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 9 03:54:51 2009 -0700

    Compulsorily do self heal if file sizes differ.
    
    If file sizes differ, then compulsorily do self-heal. If no 'wise'
    sources are found, then pick a 'fool' with the biggest file size.
    If even 'fools' aren't found, pick the 'innocent' source with the
    biggest file size.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bfbcde78924fc5847b31ae56fe8d14ea52b60dfd
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 9 03:53:59 2009 -0700

    Handle files which have no pending xattrs at all.
    
    If a pending xattr key is non-existent on a file (call such
    files 'ignorant'), make all other non-ignorant subvolumes point
    towards the ignorant one.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ec35b79f746d8a9451d7a3b9894025fdad7382f4
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 9 03:53:26 2009 -0700

    Erase xattr during self-heal based on original dict.
    
    Decrement xattr during self-heal based on the original dict instead
    of pending_matrix, as the pending_matrix might have been
    altered later.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 445b57bf7207107a9ef078697b7d03bb9349747a
Author: Csaba Henk <csaba@zresearch.com>
Date:   Tue Apr 7 02:14:20 2009 +0200

    niftify mount(8) output for glusterfs mounts
    
    Originally, mount(8) shows a glusterfs mount like this:
    
    glusterfs on <mp> type fuse
    
    With this patch, mount(8) will show a glusterfs mount like this:
    
    <volfile> on <mp> type fuse.glusterfs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8123c907015e6ad6e2975ba77eadd4db32e08628
Author: Harshavardhana <harsha@zresearch.com>
Date:   Tue Apr 7 00:43:23 2009 -0700

    Commit package making files for FreeBSD and Solaris platform.
    
    Commit for package making related files for FreeBSD and Solaris. These files
    are supposed to be in repository to not loose track and update them as needed.
    I will update them soon for upcoming release where we support Solaris on
    ib fabric also.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b976536e616e6dd23dd4a3981d150b168f9d2bef
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:43:31 2009 -0700

    libglusterfsclient: Complete support for rmdir fop
    
    glusterfs_rmdir code path wasnt implemented completely. Here is an
    attempt to complete it.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ca32040f350a7b8ad2e24ee68b417d6bec266038
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:42:14 2009 -0700

    libglusterfsclient: Create new directory inode
    
    Make sure we give an allocated inode in the loc so that the underlying
    callbacks are able to fill it with the relevant information about the
    directory being created.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 364af2266e9cd9d1f4d88763e61a5b28d1336414
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:41:50 2009 -0700

    libglusterfsclient: Return ENOENT on missing ancestor component
    
    If any of the path's components, except the basename, are missing
    from the dentry cache and the corresponding lookup from the server
    also fails, return an ENOENT.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 353f30ad17c9ace576df47abedf71054d8eb434e
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:40:12 2009 -0700

    libglusterfsclient: Return EEXIST on lookup success in glusterfs_mkdir
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 957ae7ba2ba7b8276dab963b7af7dbf16eeb5888
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:36:57 2009 -0700

    libglusterfsclient: Perform explicit create
    
    We must create the file based on the O_CREATE in the flags
    instead of depending on the return status of the lookup.
    This works because we've already handled O_EXCL earlier and
    also handled a missing file(ENOENT)
    in case this was actually an open and not create.
    Adapted from Raghu's original patch.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d4ab91b1f254a21cac538fdffa7ff37db10ae83c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:35:32 2009 -0700

    libglusterfsclient: Handle O_CREAT on lookup failure
    
    On lookup failure, if O_CREAT is required, then we must:
    
    1. explicitly lookup the parent directory.
    2. create a new inode for the new file being opened.
    
    This special case is required for file creation because:
    1. We cannot depend on the previous lookup to have reliably looked up
    the parent inode.
    
    2. inode for the new file does not exist in the itable.
    
    Patch adapted from Raghu's original fix.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e8282fd242ba4061a40b992ebe4549b4dd23fa11
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:34:56 2009 -0700

    libglusterfsclient: Dont depend on ENOENT
    
    Dont depend on the dentry and explicit lookup function, i.e.
    libgf_client_path_lookup(..), to return ENOENT on not
    finding a dentry. Just use op_ret = -1 as a lookup failure
    status.
    Patch adapted from Raghu's original fix.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ccbb9c7df1d887bc835a04e0f76799770ba3e2b8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:34:24 2009 -0700

    libglusterfsclient: Remove spurious strcmp
    
    This strcmp existed because of assumptions that do
    not hold true since the change in libglusterfsclient
    internals recently.
    
    This is another step in fixing the seg-fault on glusterfs_create.
    Patch adapted from Raghu's original fix to the problem.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2524bf2e9cb89627833b1120eac0f78b279c1751
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:33:56 2009 -0700

    libglusterfsclient: Resolve path on empty caches
    
    The earlier case was that the explicit lookups to the server
    were being sent only when the parent inode was NULL. This situation
    breaks when the parent inode is available in the i- or d-cache
    but the child dirent is not. In such a case, no explicit lookups
    were being sent to get the missing child dirent.
    
    Now, explicit path lookup happens even if the inode for parent or basename
    is not found in the caches.
    
    This also fixes a seg-fault occuring during glusterfs_open, in my test
    case, but one that could occur almost anywhere lookup code is used.
    Patch adapted from Raghu's original patch.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 47f03734685076fce51eaacb706796d2213bdbf1
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Apr 7 05:32:47 2009 -0700

    libglusterfsclient: Fix segfault in glusterfs_open
    
    libgf_client_loc_fill gets passed a name=NULL argument.
    So when this function returns the filled loc argument, this loc
    is actually missing the inode structure that was to be filled.
    
    The segfault actually occurs a few lines later when
    we try to access fd->flags but fd returned by fd_create is NULL
    because we'd passed a NULL inode to it, i.e. the loc->inode.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 07fcdfebf25c30811a9313ac3d9a0fdbbceaad6c
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Wed Apr 8 04:24:22 2009 +0530

    introduction of secondary index database in storage/bdb
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit abf35ff6c7a2cc94d9e1e738fb76f711bd2abc16
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Wed Apr 8 04:24:00 2009 +0530

    link() & rename() on storage/bdb will always return EXDEV.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8fea700263bd356e6ecacd3dabc9a9c00043a804
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Wed Apr 8 04:23:30 2009 +0530

    storage/bdb untabify, code alignment to limit to 80 characters per line.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 34ae34826cce3233402bf36cd6f0174be06a83dc
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Apr 7 17:38:07 2009 -0700

    map translator cleanup.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4e90ca853b774f64c6adde73a62ed2649bda5eab
Author: Vikas Gorur <vikas@gluster.com>
Date:   Wed Apr 8 02:30:18 2009 -0700

    Fix minor bug in afr_open_cbk.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 225e86b37492e5004eb51498b46471d74f30841d
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri Apr 3 02:06:52 2009 -0700

    io-threads: Refactor un-ordered worker exit path
    
    This is being done for the same reason as the
    previous refactoring for ordered threads.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fe1cedc1a960493337676885881018e4687c12a2
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Fri Apr 3 02:06:25 2009 -0700

    io-threads: Refactor ordered worker exit path
    
    This patch re-factors the exit path of an ordered worker
    on a time-out. Earlier we're checking for exit permission
    in such a way that required us to release and acquire
    the worker lock a second time in the worker loop opening
    a window wherein a new request could've been appended to the
    request queue.
    
    This patch makes the decision to exit while still holding on to the
    worker lock.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3acd56bec5afef9db673ae8d7dbe52bc7943b298
Author: Csaba Henk <csaba@zresearch.com>
Date:   Mon Apr 6 21:25:12 2009 +0200

    add .gitignore
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5634986f594fe75d0cd2e69cadf002a2c701f366
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 7 06:55:43 2009 -0700

    Fix in changelog logic.
    
    If a writev fails, remember it by marking it in the fd context.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d46684117a02359886e096d1bcc9f590b54144a6
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 7 06:55:15 2009 -0700

    Consider a subvolume dead if an fop fails on it
    
    Transaction fops earlier called afr_transaction_child_died only
    if an fop failed due to ENOTCONN or EBADFD. Now they consider a child
    dead regardless of the reason for failure. This handles cases such
    as ENOSPC.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d71e72248096d12ce2a8ca7ccb36ef97ae486583
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Apr 7 03:27:24 2009 -0700

    Add lock-less versions of fd_ctx_*
    
    Added __fd_ctx_get
          __fd_ctx_set
          __fd_ctx_del which do not hold any lock.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 27996c714f7fd6a7686f2d4a3552efbc1e54c2c7
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Apr 6 10:27:45 2009 -0700

    Enabling booster after port to work with changed libglusterfsclient interface.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2d59bde99600ecb15b7ebba9cd0283925c9f20f4
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Apr 6 10:56:52 2009 -0700

    fix to fd leak in posix_create() in case of some failures.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c7962678224374fa295d4063c2f5387c7280536e
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Apr 2 19:45:04 2009 -0700

    nufa to take care of free disk-space while creating files.
    
    nufa gets awareness about the available free-disk-space in subvolumes.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 258fec70ba2cc588f500f3e3bc16c99af212b4c9
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Apr 6 05:21:29 2009 -0700

    Fix in return value of afr_sh_mark_sources
    
    afr_sh_mark_sources now returns:
      -1   if two wise subvols conflict (split-brain)
       0   if all subvols are innocent (no self-heal needed)
      >0   if sources found
    
    Also, changes to callers of afr_sh_mark_sources to handle return
    value properly.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6b18487d2811b4fb004d0f4c5c98a101a93b35ed
Author: Csaba Henk <csaba@zresearch.com>
Date:   Mon Apr 6 14:03:21 2009 +0200

    bitrot-13 fix
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7a543c3b45139adce1189785200ad23b2ec867d2
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Apr 6 04:00:59 2009 -0700

    Fix an incorrect type-cast in libglusterfsclient.c
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 258da6cd992c279469f2288f8a3cd41be69d43c2
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 6 00:37:54 2009 -0700

    io-threads: Cleaner stub destruction
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 45dab1eefd85e38570c2c3ccfac0061245f70e74
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Apr 6 00:25:51 2009 -0700

    io-threads: Sanity check worker thread idx
    
    This patch adds sanity check for the ordered worker thread index
    returned from the inode's context. If the index is corrupted we
    STACK_UNWIND with ECANCELED.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fed1aa318dcf939326b955a8fcc2da2b1535acb9
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Apr 3 22:13:53 2009 +0530

    disabling booster

commit 8a5005ecf06f23f1607c0ff4111a21c00bd74205
Author: Amar Tumballi <amar@gluster.com>
Date:   Fri Apr 3 08:27:44 2009 -0700

    distribute to take care of available disk space while creating new dirs, and files.
    
    distribute gets awareness about disk-space while creating the files
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f235826215205ac626abb0ad475e7a89f7003da5
Author: Rommer <rommer@active.by>
Date:   Wed Mar 18 14:32:50 2009 +0200

    fix broken transport-type unix
    
    fix broken transport-type "unix"
    however unix transport not working with defined transport.socket.bind-path
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7a52d4ba1f1f8b68ecd79b4d5409f3b930b4efd4
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Mar 30 07:25:32 2009 -0700

    libglusterfsclient - reimplement glusterfs_fgetxattr and glusterfs_fsetxattr
    
    - glusterfs_fgetxattr and glusterfs_fsetxattr earlier used lookup and setxattr
        fops for implementation. Change it to use fgetxattr and fsetxattr fops
        instead.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 475a5909f3f80a1fc91630ea22bec228bfdc676b
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Mar 30 07:20:35 2009 -0700

    libglusterfsclient - fix bug in __do_path_resolve
    
    - add argument lookup_basename to __do_path_resolve which indicates whether to
        lookup basename(path). This is necessary for apis like glusterfs_get, which
        dont want basename(path) to be looked up by libgf_client_lookup_path.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 65bd768543c4de3d2ffd8d17efbd79e1e03666a4
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Mar 30 06:33:06 2009 -0700

    libglusterfsclient - move lookup timeout related code to libgf_client_path_lookup
    
    - this simplifies the resolution of path to inode, the apis which receive
         path as argument just need to call libgf_client_path_lookup for
         path->inode translation.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ab534d54e4e2e1eb921c7a3c98d44137471c7ac5
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Mar 30 04:21:59 2009 -0700

    libglusterfsclient - fix indentation
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e60d2194840b78034db1ad5c8b385a691ab3ddb6
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Mar 30 03:57:20 2009 -0700

    libglusterfsclient - change implementation of glusterfs_get
    
    - remove redundent lookups happening in glusterfs_get.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8b8448799cc43f20f5812bf5629c8670f76f78d3
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Mar 25 23:22:55 2009 -0700

    mod_glusterfs/lighttpd/1.4 port and memory leak fixes
    
    - port owing to changes in interface of libglusterfsclient.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 38be3fda5ce27352c45475fc4de442806cbddd36
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Mar 25 23:22:28 2009 -0700

    mod_glusterfs/apache/1.3 port
    
    - port owing to changes in interface of libglusterfsclient.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e600abcb96979f80a0a20074347e8efc6cae880d
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Mar 25 23:22:03 2009 -0700

    mod_glusterfs/apache/2.2 port
    
    - port owing to changes in interface of libglusterfsclient.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cf6f21928dbe3489de5dfdc3513f3be5f5ef529d
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Mar 25 06:52:05 2009 -0700

    libglusterfsclient code changes
    
    - add dentry support to libglusterfsclient.
      - changes related to using array, to store context in inode instead of
        dictionary.
      - code changes related to cleanup of libglusterfsclient interface.
      - added glusterfs_mkdir and glusterfs_rmdir
      - other changes in libglusterfsclient to make it work with code changes
        in other parts of glusterfs.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6eb419f1ca68f536a700e63c1521e428560a0d9d
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Fri Apr 3 06:30:54 2009 -0700

    server-protocol - reimplement connection cleanup to happen in 2 phases
    
    - first phase, which happens when POLLERR is received on transport,
         releases all locks, flushes all open fds.
       - second phase, which happens when both the transports of connection destroyed,
         destroys the containers like lock table, fd table along with the connection.
       - the first phase, clears up any references to transport held by translators
         like posix-locks(in the form of blocked locks) paving way for the second phase.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d3d7245970189629937f6330a6d946f5fbb454af
Author: Vikas Gorur <vikas@gluster.com>
Date:   Fri Apr 3 05:34:10 2009 -0700

    Made afr inode context a 64-bit packed value instead of a structure.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 75c70231fe7e13a68239dac889568d243a79a75e
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 2 08:31:23 2009 -0700

    Load balance read operations among subvolumes in afr
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1e7c9fa93716844e60d41811b8b79f8605a5044c
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 2 08:30:32 2009 -0700

    Defined afr_inode_ctx_t structure.
    
    Notification of a split-brain situation, which was earlier signalled
    by the mere presence of inode context is now signalled by
    the 'split_brain' member in the structure.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9f2ef60274dae8b302d691ba8d266cd76dcd7c4b
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 14:01:05 2009 -0700

    io-threads: Support autoscaling volfile options
    
    This commit finally makes the autoscaling feature visible to the user.
    Know that we're now using two separate thread-pools, one for data
    requests, called ordered thread-pool in io-threads, and the other
    for meta-data requests, called un-ordered thread-pool.
    We do not expose this information to the user to keep io-threads
    simple. Consequently, when the user specifies a min-threads and
    max-threads value, the number of threads assigned to each pool
    is equal, i.e. both pools start with their min threads set to half of
    the option "min-threads" and both scale up their threads at most up to
    half of option "max-threads".
    
    Volfile options will be added to the wiki and user-guide.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b1bbd77f16a13f8109d1e2e1b4ed869db1e86645
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 14:00:36 2009 -0700

    io-threads: Cleanup request queueing,thread firing
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ae53812b2ccfd7842fa6430081465ed90f18814b
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 14:00:06 2009 -0700

    io-threads: Allow scaling to be switched off
    
    The default is also to provide no scaling. For both, ordered and
    unordered request pools, when scaling is off, we maintain atleast the
    minimum number of threads specified in the volfile.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b64fa35870b54b8d9e62afd71c92e35b1f7a4cfd
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:59:43 2009 -0700

    io-threads: Add ordered threadpool state and code
    
    Now we have the remaining fops going through the ordered
    thread-pool.
    
    To route a request through ordered thread, we use
    iot_schedule_ordered(..) and the worker thread for
    ordered requests is iot_worker_ordered(..)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ee79908d3b577c061b497e35481b8d1523502077
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:59:24 2009 -0700

    io-threads: Add un-ordered thread-pool.
    
    This commit adds everything needed to:
    
    a. Get un-ordered request going through the un-ordered
    thread-pool. This happens through, the
    iot_schedule_unordered(..). The unordered thread-pool
    consists of thread running the iot_worker_unordered(..)
    function.
    
    b. Make threads in the un-ordered thread pool start-up
    and exit depending on the thread state.
    
    Note that at this point the requests that need
    ordering are still going through iot_schedule(..).
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e27f7f344e12d0885a48fcca8dfce36440f5e9e8
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:58:49 2009 -0700

    io-threads: Classify requests for threadpool type
    
    New io-threads will serve requests through two separate
    threadpools.
    
    One thread pool for requests that must be ordered
    on a file that is open. so that the server can process the requests
    in the order they were entered in the requests queue, and not in the order
    the io-thread is able to send a request, which in turn is determined
    by how the thread gets scheduled. This can also be called the
    data-intensive ops thread pool.
    
    Second thread-pool for requests that dont care about ordering, i.e.
    requests like lookup, open, create, mkdir, etc.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 42df79e2ad14053f38a12f30b29b81dd897921c9
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:58:30 2009 -0700

    io-threads: Wire in support for rename fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 369476e93e4ab99234602a5bbe2070d734b45567
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:58:11 2009 -0700

    io-threads: Wire in support for symlink fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6afeb9dd1bb9f329b5b0508d49c2e5142c6fc8cc
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:57:51 2009 -0700

    io-threads: Wire in support for rmdir fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 21363da2935615b5574cce597c95a8a7b0503766
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:57:34 2009 -0700

    io-threads: Wire in support for mkdir fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cbf8858a230b91174dc6134e4729a047db6ff914
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:57:18 2009 -0700

    io-threads: Wire in support for mknod fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ef73c3de6097c6114b5492d5972c257b849e10b7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:56:50 2009 -0700

    io-threads: Wire in support for readlink fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d767455020f9730793230a14cd9e795194c5257f
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:56:27 2009 -0700

    io-threads: Wire in support for access fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit eab231f3596aa4b6ad2b9b8f3d1a4cc97bda76bc
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:56:04 2009 -0700

    io-threads: Wire in support for fchown fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3ca0a7859f6f8f7ebc6ac32b6f17035f2115d2a0
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:55:44 2009 -0700

    io-threads: Wire in support for chown
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d56683ccfa1b53c42717ff36490066cff25fd7d0
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:55:19 2009 -0700

    io-threads: Wire in support for fchmod fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f05ca55ef77fb2004b0f573aa267c92405166d9c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:54:52 2009 -0700

    io-threads: Wire in support for chmod fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit dffa5a92c70732e790b6c789e2aacb7f8c5c34cc
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Wed Apr 1 13:54:33 2009 -0700

    io-threads: Wire in support for lookup fop
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b91e83aa0d3891b4cd725b6044131096405dfba8
Author: Anand V. Avati <avati@gluster.com>
Date:   Thu Apr 2 16:37:37 2009 +0530

    wb_flush - keep reference on fd for process_frame to perform STACK_WIND of flush.
    
    This patch fixes bug report by Greg <greg@easyflirt.com> on gluster-users@ with subject 'glusterfsd crash'
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f2cdc5d10c56ef8010ab83acf31b3fb6c4c2fd1f
Author: Anand V. Avati <avati@gluster.com>
Date:   Thu Apr 2 16:49:37 2009 +0530

    change char to int in execute_cmd (based on comment on #26006 from Giorgio Marinelli <gio@reversiva.net>
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1e9b5a5a35e8d53e631788443dadf1fe30853743
Author: Bharat Shetty Barkur <bharat.shetty@gmail.com>
Date:   Thu Apr 2 01:41:55 2009 -0400

    Changed few lines to ensure Optimization (lesser code).
    
    Changed few lines to ensure lesser code optimization while checking the EOF for the file pointed to by specfp.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit aa0fd06dad70a7ecfc3dab819e9b3fab8baad2a9
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu Apr 2 02:49:42 2009 -0700

    Build fixes for ib-verbs compilation on solaris
    
    Build fixes for solaris on ib-verbs with recent OFUV Update 3 release.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 63115897fe77e584552624c88f84eaeac55d9b57
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Apr 2 04:05:50 2009 -0700

    unify-self-heal: Fix un-ref'ing of incorrect dict
    
    dict_unref'ing of the dict in local
    results in a crash due to de-referencing a NULL spinlock.
    That is because after a STACK_UNWIND(..), we cannot expect
    the frame->local to be allocated still.
    
    Fix by using the other available reference to local->dict.
    
    Ref: https://savannah.nongnu.org/bugs/?26058
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 26af4e1229106e3d4d311fcfa1646f1ce9f3f271
Author: Vikas Gorur <vikas@gluster.com>
Date:   Thu Apr 2 03:39:24 2009 -0700

    Print log message when AFR receives CHILD_UP/DOWN notification
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 522b2bdb540bef4911e0874030d1f9b3003ba104
Author: Anand V. Avati <avati@gluster.com>
Date:   Thu Apr 2 15:51:34 2009 +0530

    socket_connect() - if socket is already created, do not fail transport_connect() -- causes spurious CHILD_DOWN events to be sent up when reconnect() thread misinterprets the failure of transport_connect() to be an actual teardown of the transport
    
    the spurious CHILD_DOWN events cause self-heal in replicate to not heal files in that subvolume, writev to not modify that subvolume etc, accounting for a lot of discrepencies in replicate which are being in the mailing lists recently.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3acfb275879fb8392f8cb4ea2a58766afbc42baa
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu Apr 2 02:50:33 2009 -0700

    Fixes server goes into infinite loop on Solaris when poll_err is not set.
    
    Server goes into infinite loop when poll_err is not set.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cda677a98d039de6381887422d0b482ed412daaf
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 2 06:09:56 2009 +0530

    mount/fuse to silently send fresh lookup for ESTALEd revalidates. log only in DEBUG level.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8e621bdfff915f40d67ed5b2d17914226c601108
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 2 06:09:26 2009 +0530

    cluster/stripe to propogate ESTALE to parent.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2b63980c5da5e82c1a80fe91115fb8d8af201755
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 2 06:08:57 2009 +0530

    cluster/unify propogates ESTALE to parent translator, if any subvolume returns ESTALE during revalidate.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 60615a0a78ab8bc93dd027c1338c588c4f3d49a7
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 2 06:08:17 2009 +0530

    cluster/replicate should propogate the ESTALE error to parent, when at least one subvolume returns ESTALE.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 705c7c9bacafc22b714ac15e3925cb5eaeb45b0a
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 2 06:07:25 2009 +0530

    cluster/{dht,nufa} propogate ESTALE (when at least one subvolume returns ESTALE for revalidate) to parent translator.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e8cce0bed6e5e6bd926ee465c5ec7a00b0b37793
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Apr 2 06:07:04 2009 +0530

    cluster/{nufa,dht} fail revalidates with ESTALE, in case a stale layout is found in inode->ctx.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 905b9fd38a3da787de3f30d1cbdd5e85d56e2f81
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Apr 2 01:10:03 2009 +0530

    Review comment from Krishna was missed out in previous commit of fix for sending first_lookup in 2nd call

commit 25d415e1917df1cac363142fb6fd3768f3e7d2af
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Apr 1 21:54:43 2009 +0530

    use (fgetc() != EOF) instaed of feof() in parser
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 978174fd7362b6c425db78c8d316b96050603844
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 30 23:36:41 2009 -0700

    Bug fix in posix-init(), when span-devices is set above 1
    
    removed the extra '!' in if statement, which was a typo earlier.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 39d67cbf8921db55e7205a94bce5c6d154a3a3d5
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 31 15:49:57 2009 -0700

    fix a segfault with io-threads when iot-schedule is called with NULL inode
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit db365c30d07f5faae4197e37148f64e75b54a7ec
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Mar 31 10:56:10 2009 -0700

    Enable glusterfs client to exit after a configured number of failed connects \ while fetching volume specification file from server
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit aa63a122433d51e89148af27dab98cf68846dab4
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Mar 31 11:18:55 2009 -0700

    Avoid infinite loop while parsing volume specification files on Linux/ARM.
    
    - patch submitted by anonymous user (ref: bug #26006 on savannah).
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 96b687b9b8d58fc70dfaaed42dbe1b35799117f8
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Mar 31 06:22:16 2009 -0700

    Add new type of option type INTERNET_ADDRESS for validation
    
    - used to validate options like remote-host, bind-address.
      - Also validate options of translators created during fetch of volume
        specification file from remote server.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c8ddd2588ae7d9890b2d30fd1dadc6f9b054d7f4
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Tue Mar 31 12:25:58 2009 +0530

    log message changes in mount/fuse for SETLK, GETLK, GETXATTR, SETXATTR fops
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9922b37658d7d996321382c5157bf33bbbb1330d
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Mar 30 21:14:45 2009 -0700

    Add support for log-level NORMAL in fuse mount helper script.
    
    - patch submitted by John Feuerstein <john@feurix.com>.
      - copying changes in the patch verbatim to
        xlators/mount/fuse/utils/mount.glusterfs.in and
        xlators/mount/fuse/utils/mount_glusterfs.in
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a0c1de7c9cf41d37f95660fe45da66418e263340
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Mar 28 14:17:55 2009 +0530

    first call of fuse is INIT internal call, and not first system call. 2nd call is the system call where first_lookup() has to be done.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3276e650f8af676ed602279f4be85d053aa6065d
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sat Mar 28 00:32:34 2009 +0530

    memory leak (of header) when frame is attempted to be xfer'ed when transport is disconnected
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3baa99ebef316c6a9947c17c6d0c4bca863a8c82
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Mar 27 22:11:31 2009 +0530

    ping-pong timer: - share last_sent and last_received between channels so that any activity ensures the remote host being alive (useful under heavy loads) - timer expiry disconnects both transports
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6c28cb81b2a326a416968932919ea9d19f3b56ab
Author: Anand V. Avati <avati@gluster.com>
Date:   Thu Mar 26 17:29:52 2009 +0530

    fix duplicate setting of values in inode->ctx and fd->ctx
    
    this patch avoids setting of duplicate key/value pairs in the context.
    note that consumers have to explicitly check for previous existance of key
    to avoid any kind of resource leak resulting from this overwrite.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 675e8b4a1f07668a6145c16283b68daa165a7a0c
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Mar 26 08:47:13 2009 -0700

    libglusterfsclient: Fix NULL argument bug
    
    inode_ctx_get was being passed a xlator_t type
    that was initialized to NULL resulting in a
    EINVAL return from glusterfs_fstat.
    
    Reported on gluster-devel
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a59582c3faed3efcf713caeb990ea5c35479dd8d
Author: Anand V. Avati <avati@gluster.com>
Date:   Thu Mar 26 16:26:21 2009 +0530

    posix_unlink - open/unlink/close only regular files
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 36e39bf9cb4b7c712ef411d60203bf05af7e129f
Author: Anand V. Avati <avati@gluster.com>
Date:   Wed Mar 25 18:08:43 2009 +0530

    Enhancements to distribute selfheal
    
    - create missing directories instead of creating linkfiles when
      entry missing  on hashed subvol
    
    - detect cases where there are dirs and linkfiles for a name and
      make them all dirs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a2d44f8cd32988ad52ad924b61a2ef5fc41e4b0e
Author: Csaba Henk <csaba@zresearch.com>
Date:   Wed Mar 25 02:19:14 2009 +0100

    make the location of the mount utility tunable at configure time
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ec5a5fa20823aed3127bdbea4e754ef308d81d89
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Mar 23 05:16:16 2009 -0700

    Fixed typo in warning string in afr.c
    
    Fixed typo.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3df266c278ab74c6bf1980bd17a545595bd04344
Author: Bharat Shetty Barkur <bharat.shetty@gmail.com>
Date:   Sun Mar 22 13:57:37 2009 -0400

    Changed the gf_log warning for return of null via CALLOC from 'old' to 'newdata'
    
    Fixed the warning message to be more clearer for return of the null by CALLOC, by changing old to newdata.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 4e5c297d7c3480d0d3ab1c0c2a184c6a4fb801ef
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Mar 24 03:46:08 2009 -0700

    fix to rm of large file blocking other operations on the same directory containing file (ref: rt #779)
    
    posix_unlink follows the below procedure to avoid client noticing delay during
    unlink of large file
    1. open file
    2. unlink file
    3. stack_unwind
    4. close file
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6e8017479fd9997ae47e7c8cbb74247d7e2b4fd0
Author: Vikas Gorur <vikas@gluster.com>
Date:   Tue Mar 24 05:44:59 2009 -0700

    Made self heal logic more precise.
    
    Discard earlier patch sent for the same error. This patch fixes
    it more comprehensively.
    
    This solves the spurious split-brain seen by many users.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8f590ad883c170827cc06dcbcb17e5aaa1788996
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Mon Mar 23 23:45:53 2009 -0700

    dht memory leak fix
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 270621b34af7528755373e04b07f959c8dca274b
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Mar 21 19:04:15 2009 -0700

    fixes crash in write-behind
    
    in wb_flush, there was a chance that wb_process_queue()
    was called with NULL frame, which causes crash.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 617fa2504283b63dde7f27186648ef9a9f060f52
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Fri Mar 20 12:50:51 2009 -0700

    when the both channels in client protocol is disconnected, fd's are marked as bad
    
    patch solves the problem of fds being valid even in the case of server
    disconnection, which causes operations on wrong fd when server comes back up.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cf15c8ab0fab3ad9e37cab544ccbbccd59ab03db
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Fri Mar 20 12:49:12 2009 -0700

    fixes issue of hashing to wrong subvolumes in case when a subvolume is down
    
    When a hashed subvolume is down, variable 'subvol' was NULL, but was sent to itransform.
    This patch solves this, and readdir is sent to proper subvolume now.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c20359b5b2a564e83b5830b9a17013e780096e2d
Author: Amar Tumballi <amar@gluster.com>
Date:   Wed Mar 18 18:31:30 2009 -0700

    fixed sys_<fops> related warnings. (on mac os x and opensolaris)
    
    The fix in posix will fix 'unresolved' symbol errors in Mac/Solaris/FreeBSD
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 103d82700483bf744f86719e97846b065ca3394c
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Wed Mar 18 17:10:51 2009 +0530

    dht_layout_dir_cmp - if xattr is missing, it is an error only if cached layout has entry for that subvolume.

commit b9fef00edbe7272d31be0ca22f3b2794918300e0
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Tue Mar 17 21:59:30 2009 -0700

    Add return after STACK_UNWIND
    
    We must add a 'return' after a STACK_UNWIND due to a stub creation
    failure, because if we dont, we'll end up adding a NULL stub to the
    worker thread request queue.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2d7f44e39792c71e4f7bb768acffc2f5a76c80e0
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 17 19:05:43 2009 -0700

    Moving few translators which are not well tested, are in beta stage to 'testing/' directory.
    
    This way, users will be aware which are in 'beta' stage, and we can keep on
    adding new translators (if any) seemlessly to stable codebase and once tested
    can move them to proper places.
    
    To use these translators, everyone will have to prefix 'testing/' to existing
    type of translator (in volumefile)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b947dc7161427b8c84f47b0a97861a36557f5748
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Tue Mar 17 18:15:19 2009 -0700

    ib-verbs recv-size and send-size argument takes SIZET arguments now.
    
    With this patch, to specify recv-size and send-size of ib-verbs to <n>KB, we need not give
    the option as integer value of 'n * 1024' value. This is neater to do deployments.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 0a7f4cfc1c516da573949a9521248744ce97c4e9
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 17 16:08:10 2009 -0700

    afr data self heal bug fix
    
    fixes the issue of corrupting self-healed copy in AFR
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ac8fe9901b3215c27ef8bc0971bf2bd140bbfcd5
Merge: 8e0453e 1601bb6
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Mar 17 22:38:26 2009 +0530

    Merge branch 'master' of ssh://avati@git.sv.gnu.org/srv/git/gluster

commit 8e0453e615255a5f64777a68d873a6f46262b5b3
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Mar 16 07:05:33 2009 -0700

    IO-threads Cleanup: Remove useless data structures.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit babf82427ce19aee091259b25613c426c696c330
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Mar 16 07:04:21 2009 -0700

    IO-threads Cleanup: Clean-up request scheduling and queueing interface.
    
    This patch does two things:
    
    1. Cleans up the request scheduling and queueing interface so that all
    fops only need to call iot_schedule and not iot_queue and in some
    cases iot_schedule.
    
    2. Till now, we've had open and create calls go through the main
    glusterfsd thread when sending open and create fops. This patch makes
    them also go through the worker threads. But since the open and
    creates requests would not be called with a valid inode number in the
    loc_t, these requests will get assigned to the worker at index 0.
    This will be fixed RSN, when we introduce various techniques of
    distributing the inodes(..not requests..) over the worker threads.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8e3e0e776cc04ad9f840383c4693ee73adc79558
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Mar 16 07:03:02 2009 -0700

    IO-threads Cleanup: Change workers list to dynamically allocated array
    
    Worker threads were represented as a list in iot_conf_t
    which made us traverse the list of workers in order to
    decide which thread gets the request. Now we represent the
    workers as a dynamically allocated array so that we can just index
    into the array to schedule the file.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3a83fdc459a620d5ce0360bcf5fa071118d5430f
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Mar 16 07:01:33 2009 -0700

    IO-threads Cleanup: Change request queue into a struct list_head
    
    This patch changes the per-thread request queue from a custom circular
    linked list, into the standard list.h list which is easier to
    understand and has a cleaner interface.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3099d29e8e65554af31927c8f767b9b6103ca58e
Author: Vikas Gorur <vikas@gluster.com>
Date:   Mon Mar 16 04:03:55 2009 -0700

    Add system call abstraction layer
    
    - syscall.c provides platform-independent system calls
    - previous code for this from compat.c removed
    - posix xlator uses new functions from syscall.c
    - solaris_flistxattr added to compat.c
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7d61f9d69309ccb0f9aa787caacfef77bc4e32d2
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Mar 12 04:41:23 2009 -0700

    write behind preserves order of fops with respect to writes
    
    - the execution order of fops like read, stat, fsync, truncate etc whose results
     are affected by writes, are preserved.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 473d02d1698259b4a0a6c22fdf70071e69c6e987
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Fri Mar 13 01:12:20 2009 +0530

    implement forget for cluster/unify
    
    inode_ctx_put() would set a list allocated on heap and would not be free()ed anywhere.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 215a91c4729bff06899375c02ae1568f24d683a9
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Mar 12 20:29:56 2009 +0530

    unify revalidate should propogate the error from any of the subvolume upto the parent, so that parent sends a fresh lookup.
    
    unify revalidate fails if one of the subvolume returns error.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1601bb69f48b79572789c67d12753fcaa0bd2f24
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Mar 12 04:41:23 2009 -0700

    write behind preserves order of fops with respect to writes
    
    - the execution order of fops like read, stat, fsync, truncate etc whose results
     are affected by writes, are preserved.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7af8d8edbd8554235348e0f54348edf222c0b46e
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Thu Mar 12 16:21:51 2009 +0530

    Add extra 'volume' parameter to inodelk/entrylk calls
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 31c817836c9c56eca1441b3b6f8b83db41c67f94
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Wed Mar 11 18:57:17 2009 +0530

    xlator.c option validation should check for empty valid options list (for strings).
    
    'if (!opt->value)' always fails as 'value' member is an array of size ZR_OPTION_MAX_ARRAY_SIZE and is always non-null. it should have been 'if (opt->value[0] == NULL)' instead.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b1c6a8507d59d16f9691652703be48f4539ca093
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 9 22:37:57 2009 -0700

    feature to span the export directory across different mountpoints
    
    This feature enables exported directory containing different mountpoints.
    With, 'option span-devices <n>' where n is number of different mountpoints
    export directories can have, one can enable this feature. By default the
    number will be 1, and the inode scaling won't come into picture.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3b45b4c922a5f5835afa4e9211d64da2c6868633
Author: Krishna Srinivas <krishna@zresearch.com>
Date:   Tue Mar 10 00:00:58 2009 -0700

    ping timer will not timeout if we recently got POLLOUT on the socket i.e if ((cur - (sent|received)) < timeout)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6a70225b69e7c617cb0ff62124b2687a7027c64a
Author: Bharat Shetty Barkur <bharat.shetty@gmail.com>
Date:   Sun Mar 8 12:54:25 2009 -0400

    Fixed two more occurrences of poll_out variables used for logging.
    
    Changed the poll_in variable to poll_out variable at two more places in the code.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d4adb2b0f5e7cd8e91d384f3f9047deab2464647
Author: Harshavardhana <harsha@zresearch.com>
Date:   Mon Mar 9 10:31:53 2009 -0700

    removed word "tla" from last of the remaining files
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 2323b92d9b7b679c84cab64697fc715434e28ac9
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Mar 10 00:27:52 2009 +0530

    failover to any active transport when requested channel is not connected
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ae378b63c0ae93d8077d250de6a035b92bac8697
Author: Harshavardhana <harsha@zresearch.com>
Date:   Mon Mar 9 03:19:31 2009 -0700

    Fixed build problems for init script installation.
    
    Fixed build problem for init scripts (Reported by Krishna and Vikas).
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fdfdd7cf05b7378c879917acb9129d69a407aee9
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Mar 9 16:16:02 2009 +0530

    dht_readdir_cbk - retry on same subvol if no entries match the hash
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5e4e99f4c1aa09b9e323c6fd23fcc3517447a6d7
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Thu Mar 5 07:55:43 2009 -0800

    changing the conversion specifier from 'd' to 'o' while printing st_mode
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 0991858fca6dc93de685e9527fb9ff47d77f616f
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Tue Mar 3 16:00:58 2009 +0530

    added fgetxattr and fsetxattr FOPs
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d092dff9a6e23d5fdef64154b6f3d6211f7482a6
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Thu Mar 5 17:05:35 2009 +0530

    fixed deadlock in io-cache
    
    ioc_create_cbk was holding inode->lock and calling inode_ctx_put,
    which also holds the same lock.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit cb602a1d7d41587c24379cb2636961ab91446f86
Author: Krishna Srinivas <krishna@zresearch.com>
Date:   Tue Mar 3 02:54:20 2009 -0800

    Changed the default transport-timeout to 600
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit eab182e8a8b2f9a89147334f39e51db60aafa953
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Mar 5 02:04:28 2009 +0530

    disable building of user-guide
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 762b1f9aefe07971178e584e288833bf142f402b
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Mar 4 04:00:24 2009 -0800

    code changes in the usage of inode_ctx_get and inode_ctx_put after their implementation is changed to hold inode->lock.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c8340e70f881dbb95d5238e588a7e985f6f04816
Author: Amar Tumballi <amar@gluster.com>
Date:   Tue Mar 3 20:13:45 2009 -0800

    Change to fix the build problems with bison 1.28 (in RHEL 4.6)
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1b51e542b9aa7996e2753a7686c7743ffc8ecefd
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Tue Mar 3 20:10:47 2009 +0530

    inode_ctx_t locks added
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 5ed5ea9bffe018512edc6babff18fd4d44bcdd70
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 2 15:47:37 2009 -0800

    create fuse thread after setvolume cbk happens, not only in case of success
    
    This patch fixes the 'hang' effect when client protocol fails to authenticate
    to servers (it may be problem with volume file, or server process would have
    not started yet).
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 130ae0dee7f1ed1292c32df52276833a9fa187b2
Author: Amar Tumballi <amar@gluster.com>
Date:   Mon Mar 2 09:16:45 2009 -0800

    changes in patchset and repo version
    
    noticed that if anyone pulls from git repo, the version says 'tla' and
    patchset also shows tla's patch.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit da71d1359c1335997595935dbaa07c5747231861
Author: Harshavardhana <harsha@zresearch.com>
Date:   Sun Mar 1 05:35:18 2009 -0800

    Added proper handling for the init scripts for (Debian, Ubuntu, SuSE, Redhat), SuSE init script also added.
    
    * Init scripts added for Debian, Redhat, SuSE distribution, each are installed
      by checking each distribution specific.
    
    Tested on
    1. Debian, Ubuntu.
    2. Redhat, CentOS.
    3. OpenSUSE.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b29a555c0be1c0db47c290d61f8c4dfe1e6fecbf
Author: Harshavardhana <harsha@zresearch.com>
Date:   Fri Feb 27 05:03:50 2009 -0800

    now user-guide.info is built only when "makeinfo" found
    
    user-guide info is built only when "makeinfo" found
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 7d7610007aeb3e31e9d51996a2234659de792a25
Author: Bharat Shetty Barkur <bharat.shetty@gmail.com>
Date:   Mon Mar 2 14:31:39 2009 -0500

    Fixed small error regarding the poll_out variable
    
    Changed the poll_in variable to poll_out variable, so that the logging is relevant to the case of invalid poll_out value.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit fd524dda532a05cb2485935212d1a66f4130256c
Author: Harshavardhana <harsha@zresearch.com>
Date:   Sat Feb 28 01:49:40 2009 -0800

    Fix solaris server segfault in recent "rc3" release.
    
    typecasting from uint64_t directly over pl_inode structure segfaults
    are all the calls from posix-locks.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b6bf3b8d6efb995d4ca7b91ff41709c57753d632
Author: Harshavardhana <harsha@zresearch.com>
Date:   Fri Feb 27 10:23:45 2009 -0800

    CALLOC changed to calloc in rdd.c and several other cleanup and moved rdd.c into more appropriate "benchmarking" directory.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 24f80a408cbf5214664efe12466929d50575c963
Author: Harshavardhana <harsha@zresearch.com>
Date:   Fri Feb 27 10:23:29 2009 -0800

    Removed unncessary EXTRA_DIST entries and updated benchmarking directory
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b2db5d966f210be72250fb87e513d187d3de7fdd
Author: Harshavardhana <harsha@zresearch.com>
Date:   Fri Feb 27 10:23:08 2009 -0800

    Added /etc/init.d/glusterfsd for rpmbuilds
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3aff44fab8ba7a109bd691b8675dbfd9842237a3
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Fri Feb 27 22:35:25 2009 +0530

    check for fd ctx set in changelog_needed_post_op for flush() in afr
    
    Earlier the check was in afr_flush(), which caused race conditions
    with writev()
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1e5ac91d05e89356ac63fb07cc09bed7a979289f
Author: krishna <krishna@guest-laptop>
Date:   Fri Feb 27 03:31:13 2009 -0800

    send a lookup on root as soon as we get CHILD_UP to fuse.
    
    send a lookup on root as soon as we get CHILD_UP to fuse. This fixes the
    case where some of the fuse versions do not send a lookup on the root
    directory when one of the "sub-dir" or "sub-file" is accessed just after mount.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8462dd88ad3531837ebfccd17a083467faa40227
Author: Amar Tumballi <amar@gluster.com>
Date:   Thu Feb 26 08:09:25 2009 -0800

    volumefile modification awareness to make sure there are no inconsistencies.
    
    Complete (including feature to properly umount) in my sense.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit da9664587d414ba703c46839e3a4831ad3784a19
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Feb 27 10:34:03 2009 +0530

    Skip self-heal when subvolumes are down
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 596b48e14e5797deca35915edb047471d7c15a00
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Feb 27 02:50:48 2009 +0530

    fixing warnings in previous patch (typecasting pointer to long)

commit 0601a2d6631983cbce39982dfcbecae23a4fa629
Merge: 2dbcb3c b4ff0d5
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Fri Feb 27 02:39:49 2009 +0530

    Merge branch 'master' of ssh://avati@git.sv.gnu.org/srv/git/gluster
    
    Conflicts:
    	xlators/features/locks/src/common.c

commit 2dbcb3c79338dc4f4c45c21e4bf62e61e455ae19
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Fri Feb 27 02:14:15 2009 +0530

    reverting nested locks in posix-locks for inodelk
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b4ff0d5c88b886dbe841cdcfdb71ac936522f9c3
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Fri Feb 27 02:14:15 2009 +0530

    reverting nested locks in posix-locks for inodelk
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f097e77ffb386dc73e3639af4a9cd57df0d3d40d
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Fri Feb 27 00:36:23 2009 +0530

    moved dht_hashfn_tea() to libglusterfs/hashfn.c as gf_dm_hashfn() (dm - davies-meyer).
    
    moved dht_hashfn_tea() to libglusterfs/src/hashfn.c as gf_dm_hashfn().
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 3d8bc3cbafa84a46e43e46f69d3e7d617d746012
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Feb 26 21:14:23 2009 +0530

    updated copyright header to extend copyright upto 2009
    
    updated copyright header to include 2009.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6fb7cda0a92b333e9c3861eb35f6f9ae3a1c03a2
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Feb 26 20:47:16 2009 +0530

    removed unnecessary README.git file
    
    removed README.git file
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d3a318973c9613cfef8b1a14256fb5178e417fb0
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Feb 26 20:36:50 2009 +0530

    fd->lock added to protect transactions for accessing and modifying fd->_ctx.
    
    fd->_ctx access and modifications are now protected by fd->lock.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 431617ef19244272797106f2356ef31591e9c7b9
Author: krishna <krishna@guest-laptop>
Date:   Thu Feb 26 06:11:48 2009 -0800

    Layout is sorted on volume names before forming the layout ranges. But when anomalies are to be detected layout is sorted based on "start" of the range (done in the selfheal during lookup).
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit c445012fa990be5dbc0ccbace04187484ccd92f3
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Thu Feb 26 17:51:47 2009 +0530

    protect fd_ctx get/set in afr_transaction and afr.c with locks
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 523d23b94c21cf5cfdfd087409371d9d2dcf25a4
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Thu Feb 26 17:13:25 2009 +0530

    Unset fd_ctx in afr_flush if it is set
    
    If fd_ctx is set, it means pending array needs to be decremented.
    However, flush might be called many times and it used to lead
    to multiple decrements. Fix is to unset fd_ctx on the first flush
    received
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b5377787903109dd5aea408e7b3a8e772b2be4f5
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Feb 26 13:38:33 2009 +0530

    __inode_unlink() should not be sent a NULL inode.
    
    unlink_inode might be NULL in inode_unlink() under the following circumstances:
    1. 'inode' got forget() and was unhashed.
    2. 'inode' was replaced by a new inode object and the new object got forget() or was pruned out of the inode table.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 417dfa48df166bfcd3f8a6da56c189de6e7a6aff
Author: Krishna Srinivas <krishna@zresearch.com>
Date:   Thu Feb 19 12:39:04 2009 -0800

    DHT clean up. Lot of selfheal code is not applicable to newly created directory. Newly created directory will use only relavant part of DHT selfheal code - only for xattr application.
    
    DHT clean up. Lot of selfheal code is not applicable to newly created directory. Newly created directory will use only relavant part of DHT selfheal
    code - only for xattr application.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 029913bbd62ed7e3c3f436afe92ad6bca9dc642c
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Wed Feb 25 00:47:43 2009 -0800

    change MALLOC to malloc
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 6609b1d37bd0254ec0eb068758862a0bb0e78515
Author: Krishna Srinivas <krishna@zresearch.com>
Date:   Tue Feb 24 06:55:39 2009 -0800

    DHT selfheal fix during lookup - create missing directories.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 1d556afdf8bf5459a1ea1a27ed5638d440439666
Author: Krishna Srinivas <krishna@zresearch.com>
Date:   Tue Feb 24 06:53:21 2009 -0800

    Ping timer does not timeout in case there is any activity (cbks) from the server side.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8479df9809107f20df31afb332b8fb6a1931b861
Author: Krishna Srinivas <krishna@zresearch.com>
Date:   Tue Feb 24 06:52:55 2009 -0800

    per frame time out - i.e individual frames are unwound instead of the transport point itself being disconnected. timeout is configured using "transport-timeout".
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit ab7fe2987fb4e2c2bd3158682fbb8c1977a049de
Author: Raghavendra G <raghavendra@zresearch.com>
Date:   Tue Feb 24 02:42:41 2009 -0800

    backtick support enhancement
    
    - text within backtick can span multiple lines
      - check exit status of command after execution
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit d47eb5d681b79b32b838505b6e22c4ab627ba934
Author: Anand V. Avati <avati@gluster.com>
Date:   Mon Feb 23 17:18:53 2009 +0530

    DHT TEA hashfn bugfix
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit f264f69ae96ade536dc6f5b8c1ce2579839d6222
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Mon Feb 23 19:36:26 2009 +0530

    Deleted xattr caching code from posix in anticipation of the xattr-cache translator.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8b1762971f8d18f73fa64a967c4cd2baa13d07fc
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Mon Feb 23 05:48:14 2009 -0800

    RE-SEND: Add braces around critical sections.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a3ed4474de9db5bda606b374f3d8cb1cdbf8a9fb
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Mon Feb 23 02:33:11 2009 -0800

    added lock_notify and lock_fnotify FOPs to everywhere necessary in libglusterfs/*
    
    fixed indentation and resubmitting
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 80066c23da120621f26d83d631e204ab2943d181
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Sun Feb 22 11:29:05 2009 +0530

    posix_releasedir flush fds from xattrcache.
    
    It would have entered cache in setdents.
    
    Proposed fix for: http://zresearch.com/pipermail/gluster-users/2009-February/001621.html
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 8b99865bb1db5e349cfdacc795ca2160a32604e1
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Sat Feb 21 15:27:03 2009 +0530

    removed to 'option cache-size <size>' in example volfiles for io-threads.
    
    io-threads translator does not take 'cache-size' option now. so removed all
    references to 'cache-size' option for performance/io-threads.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit bcd1e26a95ab75f3431be8e71d93eae9b7b6cbf8
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Fri Feb 20 18:09:02 2009 -0800

    default volume file option enhanced in server-protocolg
    
    Noticed that with current codebase, there is no proper method to have a default volume filename to choose in getspec() without printing a *lot* of warning messages. This patch tries to have a proper 'default' behavior.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 869df6de6429bd556215a2a555883cabaa4dca80
Author: Amar Tumballi <amar@gluster.com>
Date:   Sat Feb 21 13:50:01 2009 -0800

    change to make round robin dns work for getspec()
    
    Noticed that if I have just 'socket' and not the address-family, the
    round robin dns for '-s' option doesn't work. Changing it to 'tcp'
    works.
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a7b514ab8ec879a67e5a290743b4be6f0b58de1d
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu Feb 19 04:59:29 2009 -0800

    command line and mount/fuse now use float attr/entry timeouts
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit a2131aeafa94d671b0121631922d823c8a7ab988
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu Feb 19 04:59:06 2009 -0800

    attritbute and entry timeout values under volume now support float/double values
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit b5e0ee918fdff566e45bb255130b9efa6b8fb7b0
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu Feb 19 10:34:28 2009 -0800

    new function gf_string2double for float/double values
    
    fixed warning
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit 9679f8db65de29a40f622c12c2cc538d70b052b2
Author: Harshavardhana <harsha@zresearch.com>
Date:   Thu Feb 19 10:26:17 2009 -0800

    new functions dict_{get,set}_double for float/double value
    
    fixed warning
    
    Signed-off-by: Anand V. Avati <avati@amp.gluster.com>

commit e9ac5f587763b48acc19268ce57e6bfd886a0561
Author: Amar Tumballi <amar@del.gluster.com>
Date:   Fri Feb 20 09:37:13 2009 -0800

    fix to remove ''input' defined but not used' warning in building glusterfs
    
    needed to complete the build scripts without warnings
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 99a1cac632b4325afb95cb7c183721c0a90925d7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Feb 19 05:21:47 2009 -0800

    Reduce iothreads requests queue lock granularity.
    
    iot_queue() and iot_dequeue() functions were using a io-threads
    translator-wide lock which would be contended for by every worker
    thread waiting for IO requests.
    
    This patch reduces the granularity by turning the
    lock into a per-worker lock.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 57957c59cd2925540769ae9cb58029b0125e4ae7
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Feb 19 05:20:41 2009 -0800

    Remove conf->cache_size checks
    
    Since we're not dependent on this io-thread internal state(i.e.
    cache_size and current_size) to rate limit requests, we can remove
    these two data members and code that checks for these.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 6a250d9087014551c5085a534248982b195f819f
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Feb 19 05:25:44 2009 -0800

    Remove dead code.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 91df2dbcb10813d17053f715ae40a50b7499f4bc
Author: Basavanagowda Kanur <gowda@gluster.com>
Date:   Thu Feb 19 19:38:57 2009 +0530

    cluster/ha to handle EBADFD for fd based operations as transport disconnected.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit ed1d91986cdaf0240b4e6a8c920f17b7f2d6d57b
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Thu Feb 19 04:26:47 2009 -0800

    warn on ERANGE error for lgetxattr in posix
    
    (amended to fit in 80 columns)
    
    ERANGE is usually caused by the user reducing the number of AFR's
    children but continues to use the old backend.
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 1c701badce280d8de92a5314881824725deec1e6
Author: Shehjar Tikoo <shehjart@zresearch.com>
Date:   Thu Feb 19 02:26:40 2009 -0800

    Fix the order of CALLOC() args
    
    Fix the order of  CALLOC arguments.
    
    Signed-off-by: Shehjar Tikoo <shehjart@zresearch.com>
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 0bb3a56f246082967f7a89a7ea51638babf514d1
Author: Anand V. Avati <avati@amp.gluster.com>
Date:   Thu Feb 19 02:04:17 2009 -0800

    updated commit.sh
    
    changed commit.sh for git usage
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 9a4bba3a7ad86681abc9d022fd6677f668fdf062
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Thu Feb 19 00:18:28 2009 -0800

    added lock-ahead translator design document
    
    Design document for the lock-ahead translator
    
    Vikas
    
    Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

commit 77adf4cd648dce41f89469dd185deec6b6b53a0b
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Wed Feb 18 17:36:07 2009 +0530

    Added all files

commit f3b2e6580e5663292ee113c741343c8a43ee133f
Author: Vikas Gorur <vikas@zresearch.com>
Date:   Wed Feb 18 17:01:30 2009 +0530

    Initial import
